Postmortem: # Investigation

On June 8, 2026, at 10:01 AM CET, the engineering team became aware of delays and intermittent failures affecting AI-powered functionality within Document Agents, including outline preparation and document generation.

The engineering team determined that the disruption originated from an incident affecting Microsoft Azure OpenAI Services across multiple regions. As Azure OpenAI is a dependency for AI Assistant functionality, increased latency and timeout rates in the external service impacted the processing of AI requests.

While the platform continued to accept requests, slower response times caused a buildup of pending AI requests. As a result, some users experienced delays when generating outlines and documents, and in some cases workflows appeared stalled while requests were being processed.

Mitigation

Following identification of the underlying cause, the engineering team focused on reducing delays and restoring normal processing capacity.

The engineering team promptly implemented mitigation measures to reduce the impact of the Azure OpenAI service degradation and restore normal processing of AI requests. In parallel, Microsoft worked to restore normal Azure OpenAI service performance.

These actions helped stabilize the service and reduce the impact on users while the external service disruption was being resolved.

Resolution

The issue was resolved at 5:00 PM CET on June 8, 2026.

Following Microsoft's remediation of the Azure OpenAI service disruption and the mitigation measures implemented by the engineering team, AI request processing returned to normal levels.

After resolution, users were once again able to generate outlines and documents through Document Agents without abnormal delays or failures. The engineering team validated that service performance had returned to expected operating levels before closing the incident.

Post-Incident Actions

To improve resilience and visibility into similar situations, the following actions have been identified:

• Implement additional monitoring and alerting for AI service latency and timeout rates.
• Add alerts for unusual increases in pending AI requests and processing delays.
• Review scaling and recovery procedures to ensure faster response to external service disruptions.
• Continue evaluating opportunities to improve the resilience of AI-powered functionality.

Impact and Scope

This incident affected AI-powered functionality used by AI Assistant and Document Agents between 9:45 AM CET and 5:00 PM CET on June 8, 2026.

A subset of users experienced delayed responses, failed AI requests, or workflows that appeared stuck while outlines or documents were being generated. The impact was caused by increased latency and timeout rates in Microsoft Azure OpenAI Services.

We sincerely apologize for the disruption caused by this issue. Maintaining a reliable and seamless experience is our highest priority. We remain committed to delivering a dependable and high-quality service experience.

Resolved: The incident has been resolved, and further information will be provided in a postmortem shortly.

Monitoring: At 13:45 UTC on 08 June 2026, Microsoft confirmed that the platform issue affecting Azure OpenAI Service across multiple regions had been mitigated.

Identified: Microsoft reported that, starting at 09:45 CET on 8 June 2026, it identified an incident affecting the Azure OpenAI Service in multiple regions.

Further updates will be posted here soon.