Power Platform cuts off old Azure DevOps connections by 30 November

Power Platform cuts off old Azure DevOps connections by 30 November

15 October 2026: Microsoft has started removing the legacy app registration that Azure DevOps connections in Power Platform used before 1 September 2024, and says the removal will be complete by 30 November 2026. Any Power Automate flow, canvas app or Copilot Studio agent still running on one of those older connections will then fail to authenticate and stop working.

Not yet independently verified. Read through the mc.merill.net archive of the Message Center post, not in a tenant admin centre, and we found no separate Microsoft documentation page for the change. We will add one when Microsoft publishes it. We will update this when it can be confirmed, and remove this note.

The notice, MC1508508, was posted to the Microsoft 365 Message Center on 15 October under Power Platform and Microsoft Copilot (Power Platform), tagged with both user impact and admin impact. Microsoft sent it to tenants where it "identified that an app, flow, or agent in your environment utilizes a connection" of this kind, so a tenant that received it has at least one affected resource.

Why connections from before September 2024 break

A Power Platform connection stores the sign-in that a flow, app or agent uses to reach another service. Connections to the Azure DevOps connector created before 1 September 2024 authenticate through an older app registration. Connections made since then use the current method and are not affected. The fix is therefore not a setting but a new connection: Microsoft gives no way to convert an old one in place.

The removal has already begun. Microsoft does not say whether connections will fail gradually or all at once, only that the process ends by 30 November.

The four steps Microsoft asks for

Microsoft's instructions are short:

1. Identify every Azure DevOps connection in each environment created before 1 September 2024.
2. Create a new Azure DevOps connection and complete the consent prompt.
3. Point every flow, canvas app or agent that used the old connection at the new one.
4. Delete the old connection once nothing references it.

Where the work tends to pile up

Connections belong to the person who created them, and the resources that use them run under that sign-in. In a tenant where flows were built by staff who have since moved on, finding an owner who can complete the consent prompt for the right Azure DevOps organisation is often the slow part, and it has to be done per environment. Flows that update work items or trigger pipelines from tickets or approvals are the ones most likely to fail quietly, since nobody watches them run.

We list Microsoft Power Automate and Azure DevOps Services, and our low-code development platform category lists 11 products, including Retool and Airtable.

Sources

• Microsoft 365 Message Center MC1508508 (archive copy): Power Platform, recreate connections made to the Azure DevOps connector prior to September 2024, 15 October 2026