Office 365 Connector URL converter and migration helper

Microsoft retired Office 365 Connectors on March 31, 2026. Every webhook URL on webhook.office.com stopped accepting requests overnight. This converter takes your old connector URL, parses it client-side, and generates a tailored Power Automate Workflow migration plan — including a ready-to-paste Adaptive Card v1.5 payload and a verification checklist.

Targeting: office 365 connector url converter · Last updated 2026-05-02

Contents

Try the converter Why your old webhook stopped working Connector URL vs Workflow URL Migration overview After the migration

Skip the manual setup

PullNotifier installs from Microsoft AppSource in 5 minutes — no YAML, no Power Automate flows.

Step-by-step

Open the Workflows app in Microsoft Teams

In Microsoft Teams, open the Workflows app (replaces the legacy Connectors UI). Sign in with the account that previously managed the Office 365 Connector.

Create a new flow with the webhook trigger

Choose New flow → "Post to a channel when a webhook request is received". This is the closest equivalent to the retired incoming webhook connector.

Pick the destination team and channel

Select the same Microsoft Teams team and channel that previously had the Office 365 Connector configured, so notifications continue to land with the same audience.

Save the flow and copy the new Workflow URL

After saving, the flow surfaces a fresh HTTPS URL on logic.azure.com. Copy this — it is the modern replacement for the retired webhook.office.com URL.

Update the source app and verify

Replace the old Office 365 Connector URL anywhere it appears (GitHub repo Settings → Webhooks, GitHub Actions YAML, custom integrations) with the new Workflow URL. Send a test event and confirm the adaptive card appears in the destination channel.

Try the converter

Paste your old webhook.office.com URL below. The tool parses it entirely in your browser — nothing is sent to a server, logged, or stored — and returns a personalised migration plan.

1. Paste your old Office 365 Connector URL

Everything is parsed in your browser. Nothing is sent to a server, logged, or stored.

Why your old webhook stopped working

On March 31, 2026, Microsoft retired Office 365 Connectors. Webhook URLs of the formhttps://{tenant}.webhook.office.com/...no longer accept incoming requests. Microsoft cited security, scalability, and flexibility concerns — connectors had no per-flow access control, no run history, and no first-class identity model.

The retirement was silent: the URLs simply stopped delivering, and there was no deprecation error. Most teams discovered the breakage when expected GitHub PR notifications never appeared in Microsoft Teams. If your channel went quiet around April 2026, this is almost certainly why.

Connector URL vs Power Automate Workflow URL

Old Office 365 Connector URL: hosted on{tenant}.webhook.office.comwith a path containing /webhookb2/, two GUIDs joined by @, and an /IncomingWebhook/ suffix. Retired on March 31, 2026. No longer accepts requests.
New Power Automate Workflow URL: hosted onprod-NN.westus.logic.azure.comwith a path of /workflows/{guid}/triggers/manual/.... Generated when you save a Workflow with the "when a webhook request is received" trigger. Active and supported.
Payload format difference: O365 Connector accepted MessageCard JSON. Workflow URLs accept arbitrary JSON, but the recommended path is to format the payload as an Adaptive Card v1.5 inside the Workflow itself (using a Compose step) before posting to Microsoft Teams.

Migration overview

Each migrated channel takes about 30 minutes end-to-end: 10 minutes building the Workflow, 5 minutes copying the new URL into your source app, 10 minutes designing or pasting the Adaptive Card, and 5 minutes verifying. If you have many channels, this scales linearly — 10 connectors becomes a half-day of work. The converter above generates the per-URL migration plan; the Step-by-step section below summarises the same plan for SEO and HowTo schema.

After the migration

Run a test PR through each migrated webhook and confirm the adaptive card renders.
Remove the old Office 365 Connector configuration from each Microsoft Teams channel (Channel → Manage channel → Connectors → Configured).
Delete the old webhook.office.com webhook from each GitHub repo (Settings → Webhooks).
Document the new Workflow URLs in your team's runbook so the next engineer can reason about them.
If you have many repos and channels, consider a managed alternative — see PullNotifier's AppSource listing, which replaces the entire DIY Workflow stack with a single install.

Frequently asked

When did Office 365 Connectors retire?

Microsoft retired Office 365 Connectors on March 31, 2026. From that date forward, URLs of the form https://{tenant}.webhook.office.com/... no longer accept incoming requests. The shutdown was silent — old URLs do not return a deprecation error, they simply stop delivering messages.

What is the difference between a connector URL and a Power Automate Workflow URL?

Connector URLs are hosted on webhook.office.com with paths like /webhookb2/{guid}@{guid}/IncomingWebhook/.../{secret}. Workflow URLs are hosted on logic.azure.com (e.g. prod-NN.westus.logic.azure.com) with paths like /workflows/{guid}/triggers/manual/.... Connectors are retired; Workflows are the supported replacement.

Why doesn't my old webhook deliver anymore?

Office 365 Connectors retired on March 31, 2026. Microsoft removed the endpoints that accepted incoming HTTPS POSTs to webhook.office.com URLs. There is no deprecation grace period and no error response — POST requests either time out or return a generic failure. The fix is to recreate the integration as a Power Automate Workflow.

Can I keep the old adaptive card JSON or do I need to rewrite it?

Adaptive Card v1.0–v1.5 JSON is largely portable. The structural fields (TextBlock, FactSet, Action.OpenUrl) work identically. You will need to rewrap the payload — the connector accepted the card directly, while a Power Automate Workflow expects either a "Compose Adaptive Card" step or a JSON envelope with attachments. The converter above provides a ready-to-paste v1.5 template you can adapt.

Does this tool send any data anywhere?

No. All URL parsing happens in your browser via a regex match. Nothing is sent to a server, nothing is logged, and nothing is stored — neither the connector URL you paste, nor the parsed tenant or GUIDs, nor the verification checkbox state. You can verify this by viewing the page source or running it offline.

What if I don't want to build a Workflow?

You can install a managed service like PullNotifier from Microsoft AppSource. It replaces the connector with a hosted GitHub-to-Teams integration in about 5 minutes — no Workflow to build, no adaptive card to maintain, and built-in features like smart filtering, user mentions, and daily digests that the DIY path does not provide.

Do I need a Microsoft 365 license to create a Workflow?

Yes — the Workflows app is part of Microsoft 365 and requires a license that includes Power Automate seeded plan capabilities. Most Microsoft 365 Business and Enterprise plans (E1, E3, E5, Business Standard, Business Premium) include the seeded plan needed for the "post to a channel when a webhook is received" trigger. If your account does not see the Workflows app in Microsoft Teams, your administrator may have disabled it.

What about my GitHub Actions YAML?

If you used a GitHub Actions step to POST to webhook.office.com (a common pattern with curl or actions like jdcargile/ms-teams-notification), you need to update the secret/variable that holds the URL to the new Workflow URL. The body format may also need to change from MessageCard to plain JSON that the Workflow expects (or wrap it in a Compose Adaptive Card step inside the Workflow).