Is Templafy down?

Microsoft reported that, starting at 09:36 UTC on 8 June 2026, it identified an incident affecting the Azure OpenAI Service in multiple regions. Further updates will be posted here soon.

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

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

# 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.

We have identified an issue that affects a subset of customers and are working towards a resolution. Further updates will be posted here soon.

The engineers have identified the root cause and are working towards a fix.

The incident has been successfully mitigated, and our team is actively monitoring the situation to ensure ongoing stability and performance. We are observing the systems to prevent any further disruptions.

The incident has been resolved, and further information will be provided in a postmortem shortly. We apologize for the impact to affected customers.

**Investigation** On April 1, 2026, a subset of customers began reporting issues when attempting to open or generate documents through app connectors. As a result, an incident was created at 10:58 AM CET. The engineering team investigated and identified two main issues. Some links from external systems were not directing users to the correct documents, and users encountered errors when accessing certain templates in filtered folders. Further analysis showed that recent changes introduced as part of the new user experience caused inconsistencies in how required data was passed between systems. This resulted in missing information needed to correctly locate and load documents. **Mitigation** Following identification of the issues, the engineering team prioritized restoring functionality. Work began shortly after detection by correcting external link routing and ensuring required data was available before documents were loaded. Temporary mitigation steps were applied to stabilize access while a full fix was prepared. Additional connector flows were also reviewed, including known variations such as the Stuf app connector. **Resolution** The issue was resolved at 5:40 PM CET on April 1, 2026, when fixes were deployed to restore document generation through app connectors. The implemented changes ensured that all required information was consistently available during the document creation process. After deployment, users were able to successfully generate documents and access templates without errors. The solution was validated across affected environments. **Post-Incident Actions** * Feature flag implementations will include options to exclude specific tenants during rollout * Test coverage will be expanded for app connectors, document access, and integration scenarios **Impact and Scope** This incident affected a subset of customers using app connectors within the new end-user experience. Impacted users experienced failures when opening or generating documents, particularly when accessing templates through filtered folders or external links. We sincerely apologize for the disruption caused by this incident. Maintaining a reliable and seamless experience is our highest priority, and we are taking steps to improve our release processes and testing coverage moving forward.

We have identified an issue that affects a subset of customers and are working towards a resolution. Further updates will be posted here soon.

The incident has been successfully mitigated, and our team is actively monitoring the situation to ensure ongoing stability and performance. We are observing the systems to prevent any further disruptions.

The incident has been resolved, and further information will be provided in a postmortem shortly. We apologize for the impact to affected customers.

**Investigation** On March 31, 2026, at 12:02 PM CET, an issue began affecting access to Templafy for some customers hosted in West Europe \(Production 0\). The issue was detected at 12:09 PM CET through system alerts. The engineering team quickly began investigating and identified that part of the underlying Azure infrastructure supporting the service was not responding as expected. This resulted in temporary access issues for some users. **Mitigation** At 12:41 PM CET, the engineering team took steps to isolate the affected portion of the Azure infrastructure to prevent further impact. Traffic was redirected away from the affected area, allowing the platform to continue operating using healthy resources.  From a user perspective, service was effectively restored at this point, and customers were able to access Templafy as expected. The team continued to closely monitor the system to ensure stability. **Resolution** The affected infrastructure was safely removed from service, and all systems were confirmed to be operating normally. This step reflects full backend recovery and validation, with no additional user impact observed after mitigation. **Post-Incident Actions** We are continuing to review this incident in collaboration with Microsoft Azure to better understand the underlying cause of the infrastructure disruption and to reduce the likelihood of recurrence. **Impact and Scope** This incident affected a subset of customers hosted in West Europe \(Production 0\), who experienced temporary difficulty accessing Templafy between 12:02 PM CET and 12:41 PM CET on March 31, 2026. The root cause was identified as an issue within Azure-managed infrastructure.