Azure Document Intelligence in Foundry Tools
An Azure service that turns documents into usable data. Previously known as Azure Form Recognizer.
Document Intelligence Service – Slowdown & Internal Server Errors in East US Region
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 40%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVS%3C/text%3E%3C/svg%3E)
Venkatesan, Sadhana [JJCUS NON-J&J]
0
Reputation points
We have a Document Intelligence service deployed in East US region and are observing slowdowns and intermittent internal server errors on the following dates: September 17, 18, 19, 23, and today (during daytime hours especially).
Could anyone please confirm:
- If these issues were specific to the East US region, or
- If they also affected other regions running Document Intelligence during the same timeframe?
Want to validate whether this is a regional incident or a broader service-level issue.
Azure Document Intelligence in Foundry Tools
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous2025-09-24T17:38:44.1066667+00:00 Hello Venkatesan, Sadhana [JJCUS NON-J&J]
The Document Intelligence service deployed in the East US region experienced confirmed slowdowns and intermittent internal server errors on September 17, 18, 19, 23, and 24, as validated by internal emails and user reports. On September 17, an outage was acknowledged and resolved later that day. On September 18, users reported missing custom classification models, likely due to a regional outage. On September 23, the service and studio were down for approximately four hours.
These incidents were not isolated to East US alone—similar issues were observed in West US 2 and West Europe, and a global networking disruption affecting multiple regions was reported around the same period. Azure status history also shows a platform issue in East US 2 on September 10, which may have contributed to cascading effects. Disaster recovery strategies discussed internally, such as routing traffic via Azure Front Door, further confirm that regional failures are a known risk. Therefore, the evidence suggests this was not just a regional incident but part of a broader service-level impact.
Hope it helps!
Thank you
-
Anonymous
2025-09-29T17:02:16.5633333+00:00 -
Anonymous
2025-09-30T23:13:29.6033333+00:00 Hello Venkatesan, Sadhana [JJCUS NON-J&J]
Just following up to see if you had a chance to review the above response.
Thank you!
Sign in to comment
Sign in to answer