License Gone, Flow Dead? The 14-Day Deadline

Someone leaves the company, a license expires, an admin cleans up the assignments, and a flow that had been running reliably suddenly shows a yellow warning. For many teams, that's the first moment they realize how tightly a Power Automate flow is tied to its owner's license. What many don't know: the flow doesn't die immediately. Microsoft builds in a 14-day grace period before a flow without a valid license is automatically deactivated. This period is your window to act, not the moment of disaster.

In this article, we explain exactly when the 14-day deadline kicks in, what happens technically during this time, and how you, as the person responsible for Power Automate flows, should react during the offboarding process before the deadline expires.

Two scenarios, one and the same countdown

According to the official Power Automate licensing FAQ from Microsoft there are two situations that trigger exactly the same process:

• The flow owner leaves the organization. Their account is deactivated or deleted, and with it the flow loses its valid license basis.
• The flow owner loses their premium license, even though the flow uses premium connectors or other paid features, for example because an admin revokes the license for cost reasons or a license change happens within the team.

In both cases, according to Microsoft, the same thing happens: the flow is downgraded to a lower performance level, all flow owners are notified, and the flow is deactivated in 14 days if no action is taken. The wording is nearly identical for both scenarios, which shows: for Power Automate, ultimately all that matters is whether a valid license is still attached to the flow, not why it's missing.

What happens technically during the 14 days

The process isn't a sudden stop, but a staged response.

• Immediately after license loss: The flow technically keeps running but is downgraded to a lower performance tier. Actions are processed more slowly, similar to throttling caused by action limits.
• Notification: All listed flow owners and co-owners receive a message that the flow will be deactivated without action.
• Day 14: Without a countermeasure, Power Automate automatically deactivates the flow. It can be reactivated at any time afterward, as soon as the license issue is resolved, but it then runs into the same deadline again if the underlying problem hasn't been fixed.

Important to know: the 14-day rule is not a one-off case for Power Automate. According to the Overview of duration and retention limits the same deadline also applies to flows that are continuously throttled because they exceed their action limits, as well as to flows whose triggers or actions fail continuously for 14 days. Microsoft apparently uses 14 days as a fixed grace window before a flow is classified as no longer operational and automatically deactivated.

What you can concretely do within the 14 days

You have several options in this window, depending on how the flow is built.

• Change owner (solution-aware flow): For a solution-aware flow, you enter a new owner directly under Details, Edit. The previous and the new owner then become co-owners. According to the Guide to changing the flow owner it can take up to seven days for the new license to take effect. Anyone who wants to switch immediately can then edit the flow and save it again, which forces the takeover.
• Assign a process license: A Power Automate process license is attached to the flow itself instead of to a person. Once assigned, it no longer matters whether the original owner is still with the company or holds a premium license.
• Export and import for non-solution flows: A flow without a solution connection can't be directly rewritten, since the owner is part of its identity. A co-owner exports the flow and imports it again, which technically creates a new flow under their own account and their own license.
• Finding orphaned flows in the admin center: If no one is listed as a valid owner anymore, you can find such orphaned flows according to the Guide to handling orphaned flows via the Power Platform admin center under Resources, Flows, recognizable by an empty Owner column. From there you can directly assign a new co-owner; for larger environments this can also be done in bulk via PowerShell.
• Service principal as owner: For business-critical flows, switching to a service principal owner is worthwhile. A service principal is not a human account and never leaves the company, permanently eliminating the offboarding risk for this flow.

Offboarding checklist for Power Automate owners

So that the 14-day deadline never becomes an unpleasant surprise, it's worth building in a fixed step in the offboarding process.

• Before deactivating any account, check which flows run with the affected person as owner or co-owner.
• Switch critical flows to a service principal or a process license early on, instead of tying them to a single person.
• After a license change in the team, briefly check in the admin center whether affected flows are still marked as premium flows and have a valid license behind them.
• Keep an eye on the flow owners' email inboxes, since the 14-day warning lands exactly there and is easy to miss in everyday work.

Anyone running Power Automate flows in their company shouldn't leave this deadline to chance. With clear responsibilities for owner changes and licenses, you stay in control of your digital workforce, even when something changes within the team. NordFlux supports you with Power Automate consulting at a fixed price, from license strategy to stable operation.

Frequently asked questions

Is a flow immediately and irrevocably deleted after 14 days?

No. The flow is deactivated but remains fully preserved. As soon as the license issue is resolved, for example through a new process license or a new owner, the flow can be switched back on at any time.

Does the 14-day deadline count from the termination date or from the account deactivation?

The countdown starts as soon as the flow no longer has a valid license basis, i.e. technically with the deactivation of the account or the revocation of the premium license, not with the employment termination date.

Is a free Microsoft 365 license enough to keep the flow running?

That depends on the flow. If it only uses standard connectors, a license without a premium add-on is enough. As soon as a premium connector or a process license feature is involved, the owner still needs a matching premium or process license.

Can I extend the 14-day deadline?

It can't be extended directly. However, you can reset the underlying counter by editing the flow and saving it again while you obtain a matching license in parallel.

Does the 14-day rule also apply to flows without premium connectors?

No, this specific rule doesn't apply to pure standard flows with a valid, active license. It applies to flows that either use premium features without a valid license or whose owner has left the organization.