Document Intelligence Studio, file processing to export data stoped working

Hi ,

Thanks for reaching out to Microsoft Q&A.

Custom model is stuck at “Analyzing…” and no output is generated, even in production workflows that were previously working.

1. Check Azure Service Health

Go to the Azure Status Portal and check:

Cognitive Services (especially Form Recognizer / Document Intelligence) in your region.

• Look at the “Health history” tab for your subscription's region (West Europe, East US).

There have been incidents in the past where form recognizer endpoints failed intermittently due to backend service issues.

2. Try the Following Quick Checks

While waiting or checking with Azure Support, do a quick validation:

Switch to a different region endpoint (if available) to test model behavior.

Create a new project in Document Intelligence Studio and test the same document.

Check if free-tier endpoints (F0) behave the same as paid ones (S0).

Use the REST API or Azure SDKs to test the same document outside the Studio UI (to eliminate UI issues).

3. Raise a Support Ticket Immediately

Since it is affecting production:

• Go to Azure Portal -> Help + Support -> New Support Request
• Select:
  • Service: Cognitive Services -> Document Intelligence (Form Recognizer)
  Problem Type: Custom Model Inference Failure
  • Severity: A - Critical Impact (since this is a production workflow)

Provide:

Region

Model ID

Timestamp of when the issue started

Sample file (you already have: SATELEC ORDER JUIN 2025.pdf)

Screenshot (the one you shared)

4. Alternative Short Term Fix (if urgent):

If downtime is unacceptable:

Export your model using Azure Form Recognizer Studio (if available) and try deploying it in a different region.

Test built-in pre-trained models if they suffice temporarily for OCR/Invoice.

• Consider offloading to Azure AI Vision for OCR only workloads temporarily.

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.

hi there! thanks for posting this on q&a, really appreciate it ))

for microsoft's doc intelligence studio specifically, check the service status page first, sometimes azure services have hiccups. the doc intelligence team posts updates there when things go sideways. here's the link https://azure.status.microsoft/en-us/status if that's all green, try redeploying ur model. sometimes the processing endpoints get stuck. just go to ur model in azure portal, hit redeploy, and give it 5 mins to wake up. Peek at ur activity logs in azure. might show if there's permission changes or quota issues that popped up overnight. u can find these under monitoring > activity log in ur resource group.

this might help in other tools too, when extraction dies suddenly, its often either service outages (always check status pages first), expired credentials (azure keys rotate sometimes), or resource limits getting hit (those pesky api quotas)).

did u change any network settings recently? azure's doc intelligence needs proper outbound access. if someone tightened firewall rules, that could explain why its failing now when it worked before.

try processing just one simple test document through the studio interface. if that works but ur production flow fails, then we know its not the service itself but something in ur integration. saves tons of debugging time )

keep us posted if these steps help

rgds,

Alex

Hi OUADAH Djilali

If your Document Intelligence model is stuck while testing, We tried to reproduce the issue on our end but was able to access the Document Intelligence service without any issues.

Kindly refer below screenshot:

This might be an intermittent issue, possibly caused by a temporary network or server-side problem.

Please try again after some time. Additionally, clearing your browser's cache and cookies or using a different browser may help resolve the problem.

Thank You.

Hello, Thank you everyone for your help,

I got feedback this evening it seems that the service is available now, hopfully it's just a passive issue, we just transit to this solution last week in a paid licence so I was a bit worried.

It seems to have been fully resolved.

Have a great day,

Best regards,

Djilali.