Templafy Status Page

Sep 29, 2026 · resolved Sep 29

# Investigation On September 29, 2026, at approximately 12:03 PM CET, an upstream Microsoft Azure platform issue began affecting services supporting Document Agents. Customers experienced Document Agents not responding as expected. Requests to the supporting Microsoft services experienced intermittent failures, increased latency, and HTTP 5XX errors. The investigation identified an upstream Microsoft Azure platform issue affecting Azure OpenAI Service, Foundry Agent Service, Foundry Models, and Cognitive Services. The disruption primarily affected services hosted in Sweden Central, with regional impact also observed in Spain Central. As the investigation progressed, the engineering team monitored updates from Microsoft and validated Document Agent functionality internally to determine when the dependent services had recovered. # Mitigation The engineering team continued monitoring the affected Azure services while Microsoft worked to restore the impacted platform components. At approximately 8:54 PM CET on September 29, 2026, Microsoft implemented remediation for the underlying platform issue. Following this change, our engineering team began monitoring service recovery and performed internal tests of Document Agents to confirm that requests were completing successfully. The team maintained an observation period to ensure that service health remained stable before closing the incident. # Resolution Following Microsoft's remediation, the affected Azure services recovered and Document Agent functionality returned to normal. The engineering team confirmed through monitoring and internal testing that Document Agents were responding successfully and that the previously observed request failures had subsided. The incident was resolved at 9:03 PM CET on September 29, 2026, after service stability had been confirmed. # Impact and Scope The incident affected Document Agents for customers served by the following production clusters: * West Europe \(Production 0\) * West Europe \(Production 1\) * West Europe \(Production 5\) Document Agents depend on Azure OpenAI Service to function. Affected customers could experience Document Agents not responding, intermittent request failures, or increased latency. The customer impact was caused by the Microsoft Azure platform disruption affecting the supporting services in Sweden Central. No data loss was identified as part of this incident. # Post-Incident Actions This incident was caused by an upstream Microsoft Azure platform issue. Document Agents depend on Microsoft services, and recovery during this incident depended on Microsoft's remediation. We are reviewing options to improve resilience against regional failures affecting these critical cloud dependencies. In particular, we will evaluate additional regional failover capabilities for the services supporting Document Agents so that workloads can be redirected when an underlying Azure region becomes unavailable or degraded. These measures may help reduce customer impact from future disruptions, while Document Agents remain dependent on the availability of the supporting Microsoft services.

Sep 8, 2026 · resolved Sep 9

## Investigation A small number of users across two tenants reported issues when using **Find Template** and **Update Document** in the VSTO add-in. The engineering team investigated the reported behavior and reviewed the available client-side diagnostic information. The issue could not be reproduced in our internal environments, and the investigation found no indication of a broader service degradation, back-end issue, or change affecting the VSTO add-in generally. The available diagnostics indicated that the affected clients encountered a failure while initializing a local web component used by the add-in. Find Template was the initial functionality affected, which could subsequently affect other functionality such as Update Document. Based on the investigation and the very limited number of affected users, we determined that this was **not a service-wide incident**, but an isolated client-side issue affecting specific user environments. ## Mitigation The engineering and support teams worked with the affected customers to collect diagnostic information and investigate potential environmental factors. Updating the VSTO add-in was also evaluated as part of the troubleshooting process. This did not consistently resolve the reported behavior, further indicating that the issue was not associated with a specific VSTO release. As the issue was isolated to a small number of users and could not be reproduced in our environments, troubleshooting focused on the affected local environments rather than making changes to the production service. ## Resolution The investigation did not identify a definitive root cause. However, the available evidence indicated that the behavior was specific to the affected client environments rather than a broader issue with the Templafy service. Potential contributing factors included the state of locally installed components, the local Microsoft Office environment, or recent environmental updates. None of these factors independently reproduced the behavior during our investigation. As no broader service impact was identified, the event was determined **not to constitute a production incident**. The reported behavior continues to be tracked through our standard product investigation and escalation processes. ## Impact and Scope The reported issue had a **very limited scope**, affecting only a small number of users across two tenants. There was no evidence of an impact to other tenants, a production cluster, the Templafy back-end services, or the broader VSTO user base. The investigation therefore concluded that the reports represented isolated client-side behavior rather than a wider service incident. We sincerely apologize for the disruption experienced by the affected users. Maintaining a reliable and seamless experience remains a high priority, and we will continue investigating these isolated reports and monitoring for any evidence of a broader pattern.

Aug 14, 2026 · resolved Aug 14

**Investigation** The incident began at 11:19 AM CET on August 12, 2026, following the promotion of Office VSTO add-ins version 7.3.220 to the stable release channel. The issue was detected at 10:25 PM CET on August 13, 2026, after customers reported that Microsoft Word could close unexpectedly when using the **Update Document with templates containing images.** The engineering team investigated the reported behavior and identified that a change introduced in version 7.3.220 affected the processing of newly inserted images within document headers during an update. Under certain document and Word view conditions, header content could not be processed reliably, causing the document update to fail or, in some cases, Word to close unexpectedly. **Mitigation** Following the investigation, the engineering team removed version 7.3.220 from the stable release channel to prevent further users from receiving the affected version. The team restored version 7.3.217 as the stable release, providing users with the previously validated version while the behavior introduced in 7.3.220 was addressed. **Resolution** The incident was resolved at 5:08 PM CET on August 14, 2026, by reverting the stable release to version 7.3.217. This removed the affected behavior from the stable release channel and restored the **Update Document** functionality to its expected operation. The engineering team verified the mitigation and confirmed that the product was functioning as expected following the rollback. **Post-Incident Actions** We are strengthening our release validation to reduce the likelihood of similar issues reaching the stable release channel. These improvements include additional manual validation when introducing new plugin versions and more robust dependency validation when updated plugin components are consumed by other Office components. We are also expanding automated coverage, with a particular focus on integration testing for document update scenarios and interactions with Microsoft Office applications. Impact and Scope The incident affected multiple tenants using version 7.3.220 of the Office VSTO add-ins. Users could encounter failures or unexpected Word application closures when using the **Update Document** functionality, temporarily obstructing affected document workflows. We sincerely apologize for the disruption caused by this incident. Maintaining a reliable and stable experience is a high priority for us, and we are strengthening our testing and release validation processes to help prevent similar issues in the future. We remain committed to delivering a dependable service to our customers.

Jun 24, 2026 · resolved Jun 24

**Investigation** On **June 24, 2026**, 2:54 PM CET the engineering team identified an issue affecting the gateway infrastructure responsible for routing customer traffic. As a result, some requests were directed to service instances that were no longer available, causing intermittent request failures. The investigation determined that the gateway controller responsible for managing traffic routing did not consistently refresh its routing configuration following infrastructure changes, such as deployments or platform scaling events. This caused outdated routing information to remain active on some gateway instances, resulting in traffic being sent to endpoints that were no longer serving requests. The issue affected both **West Europe \(Production 0\)** and **West Europe \(Production 5\)** during separate deployment activities. **Mitigation** The engineering team immediately initiated mitigation by restarting the gateway instances responsible for traffic routing. Restarting these components forced the routing configuration to refresh, allowing traffic to be directed to the correct service instances. The mitigation successfully restored normal traffic routing for: * **West Europe \(Production 0\):** 2:54 PM CET – 3:08 PM CET * **West Europe \(Production 5\):** 3:22 PM CET – 3:42 PM CET Following the incident, the engineering team worked closely with the gateway vendor to investigate the observed behavior and evaluate long-term remediation options. **Resolution** The issue was resolved after the affected gateway instances were restarted and the routing configuration was successfully refreshed. As an additional precaution, the gateway component was subsequently downgraded to a previously proven stable version while the investigation with the vendor continues. **Post-Incident Actions** The engineering team completed a detailed review of the incident together with the gateway vendor to better understand the observed behavior. To reduce the likelihood of similar incidents, we have: * Reverted to a stable gateway controller version while the vendor continues its investigation. * Increased monitoring of gateway configuration synchronization during deployments and scaling events. * Continued collaboration with the vendor to validate future gateway releases before production rollout. **Impact and Scope** The incident affected a subset of customer requests hosted in the following production clusters: * **West Europe \(Production 0\):** June 24, 2026, from **2:54 PM CET** until **3:08 PM CET** * **West Europe \(Production 5\):** June 24, 2026, from **3:22 PM CET** until **3:42 PM CET** During these periods, some requests failed because traffic was temporarily routed to service instances that were no longer available. Once the gateway configuration was refreshed, normal service resumed. We sincerely apologize for the disruption caused by this incident. Providing a reliable and dependable service remains our highest priority, and we are continuing to work closely with our technology partners while strengthening our deployment and monitoring processes to help prevent similar issues in the future.

Jun 8, 2026 · resolved Jun 8

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

Is Templafy down right now?

No — Templafy is up. All systems operational as of Oct 12, 4:53 AM UTC.

What is Templafy's current status?

Templafy: All Systems Operational. Alert24 checks Templafy's status page continuously and can notify you the moment it changes.

How do I get alerted when Templafy goes down?

Alert24 monitors Templafy and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.