Microsoft 365 GSA Degradation Persists for Some UK and Germany Users

Microsoft says traffic optimizations initially reduced errors but did not fully resolve a GSA degradation affecting some users in Germany and the UK.

Reader ratingRate this article

Loading reader rating…

Privacy-conscious voting uses a signed random browser identifier and a short-lived network hash; the rating tables contain no raw IP-address column.

Editorial illustration of a secure cloud access gateway linking service nodes across the United Kingdom and Germany during a connectivity degradation.
Original AI-generated editorial illustration of a secure cloud access gateway during a regional service degradation; not a Microsoft status screenshot or incident photograph.

Microsoft 365 service update

Microsoft says some Global Secure Access users in Germany and the United Kingdom may be unable to reach multiple Microsoft 365 services.[1]

Reporting cutoff: 2026-10-13T14:38:03Z (10:38:03 a.m. EDT). This is a changing incident; check current Microsoft service health before acting.

Status at cutoff

Service degradation
Initial error reduction; issue ongoing[1]

Reported scope

Some GSA users in Germany and the UK[1]

Services listed

Outlook, OneDrive, SharePoint, Teams and Windows 365 Cloud PCs[1]

Scope matters: Microsoft’s public notice does not describe a worldwide Microsoft 365 outage. It limits the reported impact to some users in Germany and the United Kingdom who access the listed services through Global Secure Access.[1]

What Microsoft reported

The potentially affected services include Outlook, Outlook on the web, OneDrive, SharePoint Online, Microsoft Teams and Windows 365 Cloud PCs.[1]

Microsoft attributes the disruption to a section of Global Secure Access infrastructure performing below acceptable thresholds. At the cutoff, Microsoft said deployed traffic optimizations had initially reduced errors but had not fully resolved the issue; troubleshooting for additional mitigation continued, and the incident still carried a “Service degradation” status.[1]

Who is most likely to notice it

The public scope points to organizations with affected staff, branches, travelers or managed devices in Germany or the United Kingdom whose Microsoft 365 traffic uses Global Secure Access. The notice does not establish impact to ordinary Florida-only Microsoft 365 access or to every Microsoft 365 customer.[1]

Global Secure Access traffic-forwarding profiles determine which traffic an organization sends through the service; Microsoft says the Microsoft traffic profile can include Teams, SharePoint Online, Exchange Online and other Microsoft applications.[2]

Practical checks for administrators

Practical guidance: verify the incident against Microsoft’s public status page and your tenant Service health before treating endpoint troubleshooting as the primary response.[1]

  1. Confirm the cohort. Determine whether the affected user is in Germany or the UK and whether the connection is actually using GSA.[1][2]
  2. Check more than Outlook. Test only the business workflows you normally monitor across Teams, OneDrive, SharePoint and Windows 365, because Microsoft listed multiple services.[1]
  3. Avoid weakening security controls. Do not disable GSA, Conditional Access or other protections solely because of this public notice. Routing or policy changes should follow normal authorization and change control.[1][2]
  4. Use approved continuity channels. If work is urgent, use the organization’s existing alternate communication or file-access process and reconcile work after recovery.[1]
  5. Watch for closure. An initial error reduction is not the same as a resolved incident; wait for Microsoft’s current status and test the affected workflow again.[1]

What remains unknown

Microsoft’s public record did not provide an affected-user count or percentage, a restoration estimate, a tenant list, or a customer-side workaround at this cutoff.[1]

The reviewed notice did not identify a cyberattack or data breach. That is not proof that Microsoft has completed a security investigation; it is only the limit of the public incident record reviewed here.[1]

Bottom line

If your organization routes Microsoft 365 traffic through Global Secure Access in Germany or the United Kingdom, check current Microsoft service health, confirm the affected cohort and use approved continuity procedures. For most Treasure Coast readers without that routing and geography, this public notice does not establish direct impact.[1]

Sources

  1. Microsoft public service-health API: Global Secure Access degradation — accessed 2026-10-13 at 14:42:25 UTC.
  2. Microsoft Learn: Global Secure Access traffic-forwarding profiles — accessed during candidate preparation.

Browse Articles

Latest Articles