Share via

Is there an outage for Azure AI Doc Intelligence Studio?

Ian Hartle 20 Reputation points
2026-04-21T13:46:52.1133333+00:00

Over the past week myself and my team have been having intermittent problems with Doc Intelligence Studio. We are able to login fine but upon opening a Custom Extraction Model project we get the error below. Does anyone know of any work arounds or solutions for this?

User's image

Azure Document Intelligence in Foundry Tools
0 comments

Answer accepted by question author

  1. SRILAKSHMI C 18,225 Reputation points Microsoft External Staff Moderator
    2026-04-25T09:43:53.32+00:00

    Hello @Ian Hartle

    Thank you for reaching out Microsoft Q&A.

    Based on the behavior you described, this does not currently appear to indicate a widespread Azure AI Document Intelligence service outage. Since you are able to sign in successfully and the issue occurs specifically when opening a Custom Extraction Model project, the problem is more likely related to intermittent connectivity between Document Intelligence Studio and your underlying resource, or to resource-specific networking or access configuration.

    The error message shown "Failed to access Document Intelligence" typically means that the Studio frontend authenticated successfully but was unable to complete a request to the Document Intelligence service.

    Recommended Troubleshooting Steps

    1. Verify Service Health

    First, confirm there are no active service incidents affecting your region:

    • Check the Azure Status page.
    • Review Service Health in the Azure portal for any advisories or incidents related to Azure AI services in your region.

    If no incidents are reported, the issue is likely isolated to your resource, configuration, or network path.

    2. Confirm Resource Health

    In the Azure portal:

    • Navigate to your Azure AI Document Intelligence resource.
    • Verify that the resource is in a healthy and available state.
    • Ensure the resource has not been disabled, deleted, or placed into a restricted state.

    3. Review Networking Configuration

    This is one of the most common causes of this issue.

    Under your Document Intelligence resource's Networking blade, verify:

    • Public network access is enabled, if you intend to use Document Intelligence Studio over the public internet.
    • If firewall rules are enabled, ensure your client IP is allowed.
    • If the resource is configured for private endpoint access only, Document Intelligence Studio may not be able to connect unless proper private network routing is in place.

    If you are behind a corporate firewall or proxy, test from an alternate network such as a home network or mobile hotspot to rule out local network restrictions.

    4. Verify Permissions

    Ensure your account has sufficient access to the resource.

    At a minimum, confirm that your user account or security group has one of the following roles:

    • Cognitive Services Contributor
    • Contributor
    • Owner

    If your project relies on linked storage accounts, also ensure the appropriate permissions are assigned there.

    5. Clear Browser State

    Because Document Intelligence Studio is browser-based, cached credentials or stale session data can sometimes cause intermittent issues.

    Please try:

    • Signing out completely
    • Closing all browser tabs
    • Reopening the Studio in an InPrivate/Incognito session
    • Testing in a different browser

    This issue is typically caused by one of the following:

    • Temporary backend connectivity issues
    • Browser session or cache problems
    • Resource networking restrictions
    • Insufficient permissions
    • Private endpoint or firewall configuration

    Please refer this Azure Status page https://azure.status.microsoft/status

    I Hope this helps. Do let me know if you have any further queries.

    Thank you!

    Was this answer helpful?

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-04-21T13:47:14.36+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error shown in the screenshot indicates that Document Intelligence Studio cannot reach the underlying Document Intelligence resource, but it does not by itself confirm a service-wide outage.

    Use these steps to narrow down and work around the issue:

    1. Check for regional outages
      • Go to the Azure status page and verify whether there is any active incident for Azure Document Intelligence in the region where the resource is deployed. This confirms or rules out a service-side outage for that region.
      • Also review Azure Service Health in the Azure portal for subscription-specific incidents or advisories affecting Document Intelligence.
    2. Verify the Document Intelligence resource behind the Studio project
      • If opening a specific custom project fails, confirm that the bound Document Intelligence resource still exists in the same subscription, resource group, and region and has not been deleted or moved. If it was removed or moved, either:
        • Re-create the Document Intelligence resource with the same name, subscription, and resource group, or
        • Create a new custom project in Studio that points to the current Document Intelligence resource and the same storage account.
    3. Check authentication and permissions
      • If local (key-based) authentication has been disabled on the Document Intelligence resource, ensure that the signed-in principal has the required Azure role assignments to access the resource and operations. Missing roles can cause PermissionDenied or similar access failures when Studio tries to open or use a project.
      • Likewise, verify that the storage account used by the project allows access (no missing roles, and no restrictive firewall/VNet rules that block Studio from reaching the blobs). Misconfigured storage permissions can surface as authorization errors when opening custom projects.
    4. Validate browser/network conditions
      • Confirm that the browser and network allow outbound access to the Document Intelligence endpoint and that no corporate proxy, firewall, or content filter is blocking requests from Studio.
      • If sign-in issues appear (for example, InteractionRequiredAuthError), ensure that non-Microsoft cookies are not blocked in the browser, as this can prevent Studio from authenticating and sending requests correctly.
    5. If latency or timeouts persist
      • For intermittent or long-running hangs when Studio sends analyze or training requests, first confirm there is no ongoing regional incident as in step 1.
      • If the issue persists without any status-page incident, collect details such as model name, version, subscription ID, resource ID, timestamps, and request IDs and contact the Document Intelligence team via the documented support channels so the backend can be investigated.

    These checks help distinguish between a true regional outage and configuration or connectivity problems specific to the resource, storage account, or environment.

    References:

    Was this answer helpful?

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.