Sherweb incident
Update: Resolved - Cumulus Microsoft 365 License Management
Sherweb experienced a major incident on July 16, 2026 affecting General and General and 1 more component, lasting 7d 5h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 16, 2026, 11:39 AM UTC
We are currently investigating an issue impacting Cumulus Microsoft 365 License Management . Impact Level: Investigating Current Progress: Our engineering team has been mobilized and is actively investigating the problem to determine the root cause and restore service. Next update: We will provide an update within 60 minutes.
- resolved Jul 16, 2026, 12:03 PM UTC
The issue affecting Cumulus Microsoft 365 License Management has been resolved, and all services are now operating normally. Impact Level: Resolved Latest Update: Our team successfully applied configuration changes at 11:57am EDT , and we have verified that system stability has returned. Next Steps: We are conducting a thorough Root Cause Analysis (RCA) to understand why this happened and to implement safeguards preventing it from occurring again. We will share the post-incident report with you by the 23rd of July 2026 . If you are still experiencing service-related issues, please contact our support team for further assistance.
- resolved Jul 23, 2026, 04:55 PM UTC
Below is the post-incident report for the service disruption on July 16th, including what happened, the cause, and the steps taken to prevent recurrence. Executive Summary Date of Incident: July 16, 2026 Duration of Outage: 54 minutes (11:06 AM – 12:00 PM EDT) Maximum Impact Level: Partial Outage Services Impacted: Cumulus Client Impact: Customers were unable to access the Manage M365 functionality in Cumulus. As a result, Microsoft 365 user and license management actions could not be performed through Cumulus during the incident. Users attempting to access the service received HTTP 401 Unauthorized errors. Technical Root Cause The disruption was caused by an authentication configuration issue affecting communication between integrated platform components. As a result, requests to access the Manage M365 functionality could not be successfully authenticated, causing customers to receive authorization errors when attempting to manage Microsoft 365 users and licenses through Cumulus. Service was restored after the affected configuration was corrected and validated. Resolution Timeline All times are in EDT. 11:06 AM: Monitoring and customer reports indicated that users were unable to access the Manage M365 functionality in Cumulus. 11:20 AM: The issue was escalated for investigation, and engineering teams began troubleshooting the affected service and validating recent changes. 12:00 PM: The authentication configuration was corrected, service functionality was validated, and full access to Manage M365 was restored. The incident was marked as resolved. Preventative Measures To prevent a recurrence of this specific issue, we are taking the following actions: Improve release validation procedures to better identify dependencies that could affect service availability. Enhance our communication processes to provide earlier notice of service-impacting changes and improve transparency. If you are still experiencing service-related issues, please contact our support team for further assistance.