The fact that both Content Understanding Studio and the List Analyzers API are failing is useful evidence because both depend on the same underlying Content Understanding service. Microsoft documents that Studio and the REST API use the same Content Understanding service and resource.
I would check the following before assuming a regional outage:
- Verify the resource endpoint and API version. The documented List Analyzers operation is:
GET {endpoint}/contentunderstanding/analyzers?api-version=2025-11-01
The API requires either an Ocp-Apim-Subscription-Key or Microsoft Entra authentication.
Test the same request outside Studio using the resource endpoint. If the API also fails with the same HTTP status/error, this makes a browser/Studio-only issue less likely.
Check the Azure resource's region and whether Content Understanding is supported there. Studio requires a Microsoft Foundry resource in a supported region.
Try the current Content Understanding Studio experience rather than an older Foundry experience. Microsoft states that Foundry (classic) was deprecated on July 15, 2026; Content Understanding Studio and Foundry (new) are the supported experiences.
If the List Analyzers request is returning a 5xx/server-side error rather than 401/403/404, and Studio is failing at the same time, this is worth escalating to Microsoft as a possible service-side issue. The apim-request-id you provided is especially useful for Microsoft to trace the failed request.
I would include the following in the support request:
Content Understanding resource ID and region
Exact UTC timestamps of several failed attempts
HTTP status code and response body from GET /contentunderstanding/analyzers
API version used
The apim-request-id: 694f050b-7e53-4d34-8c86-997cb519fd31
Whether another Content Understanding resource in the same region shows the same behavior, if available
I would not conclude from the absence of a Service Health incident alone that the service is healthy; a resource-specific or regional backend problem may require Microsoft service telemetry to confirm. Avoid posting subscription IDs, API keys, or other credentials publicly.The fact that both Content Understanding Studio and the List Analyzers API are failing is useful evidence because both depend on the same underlying Content Understanding service. Microsoft documents that Studio and the REST API use the same Content Understanding service and resource.
I would check the following before assuming a regional outage:
Verify the resource endpoint and API version. The documented List Analyzers operation is:
GET {endpoint}/contentunderstanding/analyzers?api-version=2025-11-01
The API requires either an Ocp-Apim-Subscription-Key or Microsoft Entra authentication.
Test the same request outside Studio using the resource endpoint. If the API also fails with the same HTTP status/error, this makes a browser/Studio-only issue less likely.
Check the Azure resource's region and whether Content Understanding is supported there. Studio requires a Microsoft Foundry resource in a supported region.
Try the current Content Understanding Studio experience rather than an older Foundry experience. Microsoft states that Foundry (classic) was deprecated on July 15, 2026; Content Understanding Studio and Foundry (new) are the supported experiences.
If the List Analyzers request is returning a 5xx/server-side error rather than 401/403/404, and Studio is failing at the same time, this is worth escalating to Microsoft as a possible service-side issue. The apim-request-id you provided is especially useful for Microsoft to trace the failed request.
I would include the following in the support request:
Content Understanding resource ID and region
Exact UTC timestamps of several failed attempts
HTTP status code and response body from GET /contentunderstanding/analyzers
API version used
The apim-request-id: 694f050b-7e53-4d34-8c86-997cb519fd31
Whether another Content Understanding resource in the same region shows the same behavior, if available
I would not conclude from the absence of a Service Health incident alone that the service is healthy; a resource-specific or regional backend problem may require Microsoft service telemetry to confirm. Avoid posting subscription IDs, API keys, or other credentials publicly.