API Management: Developer Portal Not Responding – Recurrence Issue

Quentin PAUTRAT 0 Reputation points
2026-10-30T18:09:32.5333333+00:00

Problem description

I am experiencing an issue with the managed developer portal for my Azure API Management service. The portal has become unresponsive, and I am not receiving any response when accessing it, including static assets like /favicon.ico. The problem started around October 30, 2026, at approximately 10:34 UTC, and persists to this day.

Environment

Azure API Management, Managed Developer Portal, region not specified in case information

What I've already tried

I have reviewed the case details and diagnostic information provided. I have not tried any troubleshooting steps myself yet.

Current status

Hello,

The issue is not resolved and we need further assistance. Please assign this case to a support engineer: your last reply is an automated summary that does not answer our question.

The developer portal of wkm-apim-globalv2-eun1-prd has been unavailable since 2026-10-30 10:34 UTC and is used by our partners in production. Without findings or an estimated time from your side by 18:00 UTC today, we will disable and re-enable the developer portal to restore the service, as during the July incident (2607240050002030).

We still expect an RCA for this recurrence, including the comparison with the July event, based on the timestamps and HAR capture already provided.

Best regards, Quentin

Azure API Management
Azure API Management

An Azure service that provides a hybrid, multi-cloud management platform for APIs.


1 answer

Sort by: Most helpful
  1. Hemant Bharadwaj 90 Reputation points Microsoft Employee
    2026-10-31T06:59:33.72+00:00

    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:

    1. Confirm APIM service health and regional service status at the same timestamps.
    2. If business impact is ongoing, use APIM's publish/reset path for the managed portal and recheck from multiple networks.
    3. Capture one failing request end-to-end (URL, UTC time, status/timeout behavior, client IP) and attach it to the support case.
    4. 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.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.