azure.management.com -> byRequest service time out while other services are fine

Question

• At 2025-03-04 00:06 UTC we received an error from the management.azure.com, byRequest API service with the following query:

GET https://management.azure.com/subscriptions/mySubscription/resourceGroups/myResourceGroup/providers/Microsoft.ApiManagement/service/myApimService/reports/byRequest?api-version=2022-08-01&$filter=timestamp%20ge%20datetime%272025-03-03T22%3A55%3A00Z%27%20and%20timestamp%20le%20datetime%272025-03-03T23%3A55%3A00Z%27&$top=20000&$skip=0"

Status code: 422

Error message:

{

"error": {

    "code": "Timeout",

    "message": "Call to Management API oagapimanagement-pd.management.azure-api.net:3443 timed out for the service deployed in a Virtual Network. Make sure to follow guidance at https://aka.ms/apim-vnet-common-issues for Inbound connectivity to Management endpoint. Check 'ApiManagement Control Plane - inbound' connectivity at https://aka.ms/apimnetworkstatus.",

    "details": null,

    "innerError": null

}
}

• Since then, we've been unable to make a single successful request without this error for this byRequest service.

We tried:

• Different api-version parameters
• Light queries with $top=1 and querying into a future timestamp
• Other service calls we tried - for example, bySubscription or byUser - were successful
• Other environments for the same service also seem fine
• We haven't deployed any network changes.

Any idea why this single endpoint fails for this single service? Any help is appreciated.

Answer 1

Hello RedasK ,
Welcome to Microsoft Q&A Platform.

The error you're encountering is due to connectivity issues between your API Management (APIM) instance and the management API when deployed in a Virtual Network (VNet). To resolve it, ensure that your VNet is correctly configured with no network security group (NSG) or firewall rules blocking traffic on port 3443. Review the guidance on inbound connectivity to the management endpoint and check the APIM network status for any known outages. Verify DNS resolution, routing, and VNet peering to ensure proper communication.

If the issue persist, could you please provide the Resource ID of the Azure API Management? This will allow us to check the logs from our end to better understand the root cause of the issue and to provide an appropriate solution.