Is Templafy down?

We have identified an issue that affects a subset of customers and are working towards a resolution. Some customers might experience issues in using the find template and update document functionality in the Word VSTO Add-ins. 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.

We have identified an issue that affects a subset of customers and are working towards a resolution. Users could encounter issues when updating Word documents using VSTO add-ins. Further updates will be posted here soon.

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

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

Customers using West Europe (Production 0) may have experienced errors or delays while loading the application. 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 **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.