Live status of all services Advisory

Users may have been unable to sign into the OneNote Web Clipper

Microsoft 365 suite MO1447619

Users may have been unable to sign into the OneNote Web Clipper.

Status
Service degradation
Feature
Company or User Administration
Region
Not specified (all regions)
Started
Jul 24, 2026, 10:06 CEST
Duration
84 days 18 h
Last update
Aug 6, 2026, 13:38 CEST

More info

Users may have received an error when attempting to sign into the OneNote Web Clipper.

Scope of impact

Your organization was affected by this event, and any users attempting to sign in to OneNote Web Clipper were impacted.

Root cause

A recent maintenance update intended to remove unnecessary components from the service inadvertently removed a required authentication component, resulting in impact.

Next steps: - We're reviewing our service maintenance procedures and validation processes to help prevent this problem from happening again.

This is the final update for the event.

Final status

We've completed the deployment of the fix, and service monitoring indicates that the impact has now been resolved.

Timeline

Every update Microsoft posted for this issue, newest first.

  1. Aug 6, 2026, 13:37 CEST

    We've completed the deployment of the fix, and service monitoring indicates that the impact has now been resolved.

  2. Aug 6, 2026, 12:20 CEST

    We've completed the deployment of our fix to the majority of the affected environments and anticipate that most users will no longer be affected by the issue. We expect deployment to complete in the remaining affected infrastructure by our next scheduled update.

  3. Aug 6, 2026, 07:11 CEST

    We've completed validations on the new fix and have initiated its deployment. We're monitoring as it progresses to establish a completion timeline.

  4. Aug 5, 2026, 22:38 CEST

    We've completed the deployment of our fix to our internal testing environment; however, the fix did not resolve the issue as expected. We've prepared another fix which is being deployed to our testing environment. Once complete, we'll perform validations and confirm if we see impact remediation, after which we'll confirm a timeline for deployment to the affected environment.

  5. Aug 5, 2026, 15:55 CEST

    We've confirmed that the deployment is progressing as expected and anticipate sharing a completion timeline by our next scheduled update.

  6. Aug 5, 2026, 05:22 CEST

    We've identified that the deployment of the fix is taking longer than initially anticipated, but we're monitoring its progress closely to ensure the deployment completes without encountering any complications.

  7. Aug 5, 2026, 02:52 CEST

    We've completed creating the code fix, and we've initiated deployment to the imapcted environment. We expect the deployment will be complete and the issue resolved by our next scheduled update.

  8. Aug 5, 2026, 00:32 CEST

    We've identified that a recent maintenance action meant to remove unneeded code from the service has mistakenly removed the authentication HTML, preventing users from signing into the OneNote Web Clipper. We're creating a code fix that will add this authentication HTML back into the service and remediate impact.

  9. Aug 5, 2026, 00:09 CEST

    We're investigating a potential issue with the OneNote Web Clipper and checking for impact to your organization. We'll provide an update within 30 minutes.

When Microsoft 365 goes down

The live overview shows the current state of every Microsoft 365 service, refreshed every minute from Microsoft Graph.

Live status of all services Subscribe to incidents in LEXOJ

To see whether your own tenant is affected, check Service health in the Microsoft 365 admin center. Only a backup outside Microsoft protects against data loss, and only a tested break-glass account against locked-out admins. We set up both in fixed-scope sprints.

Source: Microsoft Graph, Service Communications API. This is the view of a Swiss Microsoft 365 tenant: services not licensed there are missing, and individual issues may affect your tenant differently. Microsoft names the region only in the issue text. The Switzerland view shows issues for Switzerland, for Europe in general and those without a region, but not issues that only name other countries such as Germany or the UK. This page is not provided by Microsoft.