This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(92.8, 81%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJE%3C/text%3E%3C/svg%3E)
Since March 6 11:30 CET I cannot access Azure Document Intelligence Studio.
The request to https://documentintelligence.ai.azure.com/studio/ hangs or returns error
An Azure service that turns documents into usable data. Previously known as Azure Form Recognizer.
![](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(105.60000000000001, 57.00000000000001%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECW%3C/text%3E%3C/svg%3E)
Same issue - it either stays in a loading state until the browser times out and gives a 499 error, or occasionally I get a 504 error.
Noticed the issue 2 hours ago, but all Azure status pages show no faults.
Azure Document Studio is still unavailable for over 2 hours and Azure status reports no issue.
I reported the issue to Azure Support, many users are facing the same issue and they are actively trying to resolve soon.
@José Enrique De Fabriziis Chris Walton Thanks for reporting the issue. This is currently a known issue effecting all users of DI portal. The team is currently investigating and working to restore the portal. We will post an update here as soon as we hear from the team. Thanks again!!
Informed by Azure support that the engineering team has now applied a mitigation towards resolving this behaviour.
Azure Document Studio is available now.
Answer accepted by question author
Thanks @José Enrique De Fabriziis for the updates. I can confirm now that this issue is now mitigated, the team is still monitoring the incident for any failures. Thanks!!
If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.