Major incident

Box: [Medium] Issues with Box Edit and Microsoft Office Online

Affected: Microsoft Office Integration, Box Edit / Tools

Current status of Box: Operational — live Box status

Timeline

1. Jul 16, 2026, 21:30 UTC
   investigating
   Box is investigating reports of a momentary issue with Box Edit / Microsoft Office Online. Affected services are subject to change as the investigation continues.
2. Jul 16, 2026, 21:30 UTC
   investigating
   We are continuing to investigate this issue.
3. Jul 16, 2026, 21:45 UTC
   identified
   Our team has identified the underlying cause of this issue and is working to take remediating steps.
4. Jul 16, 2026, 21:47 UTC
   monitoring
   Our team has taken steps to remediate this issue and is seeing improvement for the Microsoft Online service and Box Edit.
5. Jul 16, 2026, 21:48 UTC
   resolved
   After further monitoring, this incident is now considered resolved. Microsoft Office Online and Box Edit has been restored to full functionality.
6. Jul 31, 2026, 01:21 UTC
   postmortem
   We recently addressed issues affecting Open With integrations within Box. We would like to take this opportunity to further explain these issues and the steps we have taken to prevent them from reoccurring. Between 1:00 PM PDT and 2:40 PM PDT on July 16, 2026, some customers may have been unable to open or edit files using any Open With integration in the Box web application. During this period, affected files may have appeared unavailable or grayed out, and users may have encountered permission-related errors when launching an integration. Microsoft Office workflows, including Office Online in the browser and desktop editing through Box Edit, were among those impacted. The issue occurred after a recent service update unintentionally changed how integration workflows were handled, causing the product to return an empty set of available integration actions for affected files. We resolved the issue by reverting the service to the previously deployed version, after which service metrics and customer confirmations recovered. In addition, we are taking steps to reduce reoccurrence by improving testing, monitoring, and release practices for integration paths. # Analysis This incident highlighted opportunities to improve end-to-end testing for integration workflows and our automated detection process. The failure mode returned an empty action list rather than hard errors, which kept broad service-level signals near baseline and made the impact visible primarily through customer reports. # Corrective Actions Box has initiated the following corrective actions: * Expanded lower-environment end-to-end tests to validate Open With / Office Online behaviors after changes to integration-related code. * Added targeted monitoring and alerting for integration action and permission-check failures so regressions surface automatically. * Documented and formalized release and rollback runbooks for integration-related changes, including clear validation and rollback steps to reduce time-to-recovery. We are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter. Sincerely, The Box Team

Updates as published by Box (original).