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

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.

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.

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