Thanks for the clarification — that’s very helpful!
What you’re describing sounds like a grace period or trial expiration, and possibly a licensing policy change that affected both environments on the same day.
Here's what likely happened:
Why it worked for months:
-
When a user runs an app with premium connectors (like SQL or custom APIs), and doesn't have a proper license, Microsoft may allow limited access for a trial or evaluation period (usually 30 days, but sometimes extended silently for internal use/testing).
-
Also, when a flow or app is triggered by a service account, the run may initially succeed because it's using that service account's connection — but this is no longer supported for end-user access without proper licensing.
Microsoft changed how strictly licenses are enforced — in many tenants this started being more noticeable around early 2025, which could explain why both environments failed at once.
Bottom line:
Even if a connection is created by a service account:
-
End users still need a license to run apps using premium connectors.
-
Sharing or importing doesn’t transfer the license.
-
Grace periods can expire simultaneously for all users if they started around the same time (e.g., at first testing/deployment).
What to do:
Check if any users had trial licenses or if the app relied on connection owner permissions — both can fail silently once grace expires.
You’ll likely need to assign Power Apps Per App or Per User plans to your end users now to restore access.
If this solved your problem, please mark it as Solved to help others find the solution faster.
If you found it helpful, consider giving it a Like to support each other in this community!
Thanks, and happy building!
