An Azure service that provides a hybrid, multi-cloud management platform for APIs.
Given the portal and static assets are both unresponsive, this looks like a managed Developer Portal availability issue rather than an API-level policy/config issue.
Recommended immediate actions:
- Confirm APIM service health and regional service status at the same timestamps.
- If business impact is ongoing, use APIM's publish/reset path for the managed portal and recheck from multiple networks.
- Capture one failing request end-to-end (URL, UTC time, status/timeout behavior, client IP) and attach it to the support case.
- Keep the current support case active and request explicit RCA linkage to the prior July incident, since this appears recurrent.
What to include for faster backend triage:
- APIM service name and region
- exact outage start time (UTC)
- failing static asset URL(s)
- HAR trace / correlation headers if available
Docs:
https://learn.microsoft.com/azure/api-management/developer-portal-overview
https://learn.microsoft.com/azure/api-management/api-management-howto-developer-portal
https://learn.microsoft.com/azure/api-management/troubleshoot
If you find this answer helpful, please upvote it. If this resolves your issue, please mark it as the accepted answer so that it can help others in the community.