APIM instances stuck in InternalServerError after subscription reactivation (Correlation ID: f2f752ae-e351-45e2-808f-7f9a472e6433)

Enos Chou 0 Reputation points
2026-11-19T05:14:20.2266667+00:00

Hello Microsoft Support / Moderators,

Our two Developer-tier Azure API Management instances (located in Southeast Asia) were previously suspended due to an overdue invoice.

  • We have paid the invoice on 2026-11-19, and both Microsoft Azure Sponsorship subscriptions are now Active / Enabled.
  • The Activity Log confirms ACTIVATE SUSPENDED API MANAGEMENT SERVICE completed at 2026-11-19T02:26:00Z, and az apim show shows provisioningState: Succeeded.
  • However, over 2 hours later, both instances are still completely unusable. Running az apim api list returns: (InternalServerError) Request processing failed due to internal error.
  • In the Azure Portal, clicking on APIs shows: Error when trying to connect to "Create a new API" endpoint.

Diagnostics Details:

  • Correlation ID: f2f752ae-e351-45e2-808f-7f9a472e6433
  • Timestamp: 2026-11-19T02:37:48.639Z
  • Region: Southeast Asia

Since we are on a Basic Support Plan, our billing/subscription ticket (2611190060000966) was auto-closed by AI. Could a Microsoft Moderator please help initiate an internal backend mitigation/support ticket to restore the management plane of these two APIM instances? I can provide the Subscription IDs and resource names via Private Message. Thank you!

Azure API Management
Azure API Management

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

0 comments No comments

1 answer

Sort by: Oldest
  1. Enos Chou 0 Reputation points
    2026-11-19T23:49:12.39+00:00

    Update: The backend synchronization has completed after several hours and both APIM instances are now working properly. Closing this thread. Thank you!

    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.