Teams Incoming Webhook to Workflows Migration Checklist
Microsoft has been retiring Office 365 connectors in Teams, including the classic incoming webhook that many ERP alert jobs, monitoring tools and scripts still post to. This checklist walks through finding every sender and moving it to a Workflows based webhook without losing alerts.
0 of 31 items complete
11 critical items still open - these are the highest-risk gaps.
1. Inventory
2. Build replacements
3. Payload and behaviour
4. Security and governance
5. Cutover
Tick each item as done. Items marked critical block go-live; a migration with unticked critical items should not replace the old webhook yet.
Migration support
Optional help inventorying and migrating your ERP alerts to Teams Workflows.
Optional. The tool and every export work without this. No spam.
How to use this checklist
Start with the inventory group, because the main risk is a forgotten sender that silently stops posting when the old connector is switched off. Work through the groups in order, and keep the critical items for last review before cutover. Export the completed list as evidence for change control.
- Assign an owner to each webhook before changing it.
- Keep a copy of the old payload next to the new one.
- Migrate one sender at a time rather than all at once.
What changes technically
The old incoming webhook accepted a MessageCard or a simple JSON body at a connector URL. The Workflows replacement uses a Power Automate flow with an HTTP request trigger and a Teams action that posts a message or card. Payloads commonly need to be Adaptive Cards inside an attachments array. The URL, authentication model and failure behaviour are different, so test each sender rather than assuming a drop-in swap.
Worked example
An ERP job posts a low stock alert every morning to a purchasing channel through an old webhook. You create a workflow with a webhook trigger, paste the new URL into the job's configuration, change the body from MessageCard to an Adaptive Card envelope, and test with a sample. You set the job owner and a shared service account as workflow owners, and add an email alert if the flow fails.
Common mistakes
The usual failure is building the workflow under one person's account and losing the alert when that person leaves. Another is committing the new URL to a code repository. A third is forgetting that tenant DLP policy can block the HTTP trigger until an administrator allows it.
Frequently Asked Questions
Why do Teams incoming webhooks need migrating?
Microsoft has announced the retirement of Office 365 connectors in Teams, which includes the classic incoming webhook. Senders that still post to those URLs will stop working once retirement is enforced in your tenant, so they need a supported replacement.
What replaces the Teams incoming webhook?
The recommended replacement is a Workflow built in Power Automate, usually from the template that posts to a channel or chat when a webhook request is received. It gives you a new HTTP endpoint you point your sender at.
Do I need to change my payload format?
Often yes. Legacy MessageCard payloads are not the target format. Plan to send Adaptive Cards in the envelope the workflow expects, and test it with a sample before switching production senders.
Is the new webhook URL secret?
Treat it as one. Anyone with the URL can trigger the flow and post to the channel, so store it in a secret manager, avoid chat and screenshots, and rotate it if it leaks.
If your ERP and monitoring alerts need a reliable, owned path into Teams, Netray can help design and test the replacement integration.
Related Tools
Teams Webhook Rate Limit Queue Drain Time Calculator
Calculate how long a burst of alerts takes to drain through a rate limited Teams endpoint, including retries after throttling responses.
Developer ToolsMessaging Integration Go Live Readiness Checklist
A launch checklist for ERP to WhatsApp, Teams or Slack integrations covering consent, throughput, failure handling, monitoring and support.
Developer ToolsWebhook Signature Verification Code Generator
Generates an Express.js webhook endpoint with the Meta GET verification handshake and constant time HMAC SHA256 signature checks.
Compliance & ContractsMessaging Integration Risk Register Worksheet
A scored risk register pre-filled with typical WhatsApp, Teams and ERP chat integration risks. Edit, score and export to Excel.
More Microsoft Dynamics tools
See all- D365 F&O Manufacturing Data Entities Reference
- D365 F&O OData URL Builder
- D365 Production Order Status Reference
- D365 Data Management Import Worksheet Template
- D365 Batch Job Checklist
- D365 Security Role Design Worksheet
- D365 Master Planning Setup Checklist
- D365 One Version Update Test Checklist
- D365 Finance and Supply Chain Functional Design Document Template
Keep exploring
Free tools
- Business Central Data Migration Field Mapping WorksheetMap every legacy source field to a Business Central table and field, record the transformation rule and volume, and see how much data is ready to load.
- Incoming Inspection ChecklistA practical receiving inspection checklist covering documents, packaging, identification, visual and dimensional checks, certificates and disposition.
- Teams Adaptive Card JSON Generator for ApprovalsCreates an Adaptive Card approval message with a fact set, comment input and Approve and Reject actions, wrapped for a Teams webhook or Workflows post.
ERP fixes and how-tos
- Event-Driven ERP Integration: Architecture That Holds UpHow to publish ERP changes as events: native event sources, CDC and the outbox pattern, with idempotency, ordering and failure handling for CTOs.
- ERP Cloud Migration: The Risks a CTO Should Score FirstThe real risks in moving an ERP to the cloud: customisations, integrations, data volume, cutover, latency, licensing and exit. How a CTO scores and mitigates them.
Guides
- Setting Up Webhooks and Event Notifications in SyteLineConfigure SyteLine webhooks and event notifications using ION Connect and BOD triggers. Build event-driven integrations for CloudSuite Industrial workflows.
- How to Configure SyteLine Webhook NotificationsLearn how to configure webhook notifications in SyteLine CloudSuite Industrial. Set up event-driven HTTP callbacks for order changes, inventory alerts, and workflow triggers.
- ERP Data Migration Strategy GuidePlan a successful ERP data migration with a phased strategy covering extraction, transformation, loading, and validation. Reduce migration risk by 80%.
AI on your ERP
- AI-assisted data migration for ERP implementationsAI speeds ERP data migration by profiling legacy data, proposing field mappings, and flagging cleansing issues before cutover, with a human validating every rule.
- Is Your ERP Ready for AI? A Readiness Assessment ChecklistIs your ERP actually ready for AI? A practical checklist covering master data quality, access and permissions, GPU sizing, and governance before you fund a pilot.
Integrations
- How to add Microsoft Teams alerts and approvals to Business CentralAdd Teams approvals, adaptive card alerts and bots to Dynamics 365 Business Central using the Teams app, workflows, Power Automate and Entra ID.
- How to add Microsoft Teams to KatanaConnect Katana to Microsoft Teams with webhooks, adaptive cards and Entra ID so approvals and production alerts land where your office team already works.