You are completely right to suspect permissions are not the issue here. A 502 (Bad Gateway) error means the Power Apps client sent a valid request, but an intermediate server or API gateway received an invalid response (or a timeout) from the backend service.
Since permissions haven't changed and users previously had access, here are the most likely technical culprits and how to isolate them:
Likely Root Causes
Transient Platform Degradation
Microsoft infrastructure or specific regional Azure nodes may be experiencing temporary latency or an outage. When backend microservices take too long to respond, the API gateway cuts the connection and drops a 502 error.
On-Premises Data Gateway Failure
If your app connects to an on-premises data source (like local SQL Server or file shares), a 502 frequently means the On-Premises Data Gateway service is offline, restarting, or overwhelmed by requests.
Connector or API Timeouts
If the app utilizes custom connectors, Power Automate flows triggered on app load, or heavy Dataverse plug-ins, any backend timeout or unhandled exception in those external services will bubble up as a 502 error to the user.
Recommended Troubleshooting Steps
Step 1: Check Platform Health
- Ask a tenant administrator to check the Microsoft 365 Admin Center -> Health -> Service Health for any active Power Apps or Dataverse advisories.
- You can also monitor the public Microsoft 365 Status Twitter/X account for real-time cloud infrastructure alerts.
Step 2: Open the App in Studio (Edit Mode)
Have an maker/developer open the app in edit mode:
- Look at the Data pane to see if any connectors display an exclamation mark or connection error.
- Explicitly click the three dots next to each data source and hit Refresh. If a 502 is going to happen, it will usually trigger right here during manual refresh, pinpointing exactly which data source is broken.
Step 3: Clear Client-Side Cache
Have impacted users try running the app in an Incognito/Private window or a completely different browser. If the 502 was caused by a momentary glitch that has since passed, the browser may still be caching the error state.
Step 4: Isolate the Environment
Have a user test a different app located within that same Power Platform environment.
- If all apps fail with a 502, it is an environment-level or cloud-capacity issue.
- If only this app fails, look closely at the specific on-start formulas or data connections unique to this app.
If the problem persists across multiple users for more than an hour and no on-premises gateways are down, it is highly recommended to open an urgent support ticket via the Power Platform Admin Center so Microsoft can inspect the underlying server logs.
Let us know if this is affecting a specific geographic region or all users globally!
✅ If one of the responses here solved your issue, please mark it as Accepted so others facing the same problem can benefit as well.
👍 If this or any other reply here helped you, feel free to give it a Like. It helps others and is always appreciated.
Share
Report
All responses (
Answers (
2,191
