MC1485116: Exchange Online enforces EWSAllowedAppIDs requirement on October 10
Microsoft confirmed that Windows Server security updates released on October 13, 2026, cause significant email disruptions across on-premises Exchange Server installations. The updates block webmail access and leave messages undelivered on systems running Exchange Server 2016, Exchange Server 2019, and Exchange Server Subscription Edition. Microsoft published a specific workaround for the issue and advised administrators against uninstalling the problematic updates. This software malfunction compounds administrative strain alongside ongoing enforcement of the EWSAllowedAppIDs requirement for Exchange Online users managing Microsoft 365 work accounts and Mac email synchronization.
Listen to Live Briefing
Real-time synthesized voice briefing Β· Live Feeds Desk
- β Microsoft confirmed that Windows Server security updates released on October 13, 2026, can disrupt Exchange Server email services by blocking webmail access and leaving messages undelivered.
- β The update issues affect some on-premises systems running Exchange Server 2016, Exchange Server 2019, and Exchange Server Subscription Edition.
- β Microsoft has published a workaround and advises administrators not to uninstall the security updates.
What changed
Microsoft confirmed that Windows Server security updates released on October 13, 2026, cause OWA sign-in and mail delivery failures on certain on-premises Exchange servers.
Live updates
-
October Windows Updates Disruption Impacts Exchange Servers
Microsoft confirmed that Windows Server security updates released on October 13, 2026, cause significant email disruptions across on-premises Exchange Server installations. The updates block webmail access and leave messages undelivered on systems running Exchange Server 2016, Exchange Server 2019, and Exchange Server Subscription Edition. Microsoft published a specific workaround for the issue and advised administrators against uninstalling the problematic updates. This software malfunction compounds administrative strain alongside ongoing enforcement of the EWSAllowedAppIDs requirement for Exchange Online users managing Microsoft 365 work accounts and Mac email synchronization.
Why it matters
These server failures compound administrative workloads as IT teams simultaneously adapt to the EWSAllowedAppIDs enforcement policy that began on October 10. Microsoft previously announced that Exchange Web Services will be permanently removed on April 1, 2027. Administrators must whitelist third-party tools to prevent service interruptions.
What is confirmed
- Microsoft confirmed that Windows Server security updates released on October 13, 2026, can disrupt Exchange Server email services by blocking webmail access and leaving messages undelivered.
- The update issues affect some on-premises systems running Exchange Server 2016, Exchange Server 2019, and Exchange Server Subscription Edition.
- Microsoft has published a workaround and advises administrators not to uninstall the security updates.
What to watch next
- Microsoft release of a permanent patch for the October Windows Server update issues
- Further administrative guidance regarding the April 1, 2027 EWS removal date
confidence 100%Sources used for this update (4)
- cybersecuritynews.com β Microsoft Confirms October Windows Updates Can Break Exchange ...
- techcommunity.microsoft.com β Exchange servers may become unstable after installation of ...
- itdeadlineradar.com β IT Deadline Radar
- www.bleepingcomputer.com β Microsoft: October Windows Server updates break Exchange sign ...
-
Exchange Online Enforces EWSAllowedAppIDs Requirement
Microsoft Exchange Online has started enforcing the EWSAllowedAppIDs requirement, blocking unlisted applications from using Exchange Web Services. Administrators must whitelist third-party tools to prevent service disruptions for Microsoft 365 work accounts and Mac email synchronization. This change follows multiple schedule adjustments, with a permanent removal date for EWS scheduled for April 1, 2027.
Why it matters
The enforcement of EWSAllowedAppIDs is a significant change for organizations using Exchange Online, as it affects how third-party applications interact with Exchange Web Services. This change is part of Microsoft's plan to retire EWS and transition to newer APIs. Administrators must take action to ensure continued functionality for critical applications.
What is confirmed
- Exchange Online enforces the EWSAllowedAppIDs requirement as Microsoft eliminates the older EWSEnabled fallback and starts blocking unlisted applications.
- Administrators must whitelist third-party tools to prevent service disruptions for Microsoft 365 work accounts and Mac email synchronization.
- The permanent removal date for EWS is scheduled for April 1, 2027.
- Inventory EWS apps with the usage report, build the EWSAllowedAppIDs allow list and set EWSEnabled to keep critical apps running until April 2027.
What to watch next
- Microsoft's EWS retirement timeline and any further adjustments
- Adoption rates of EWSAllowedAppIDs by organizations
- Impact on third-party applications and services
confidence 90%Sources used for this update (6)
- www.mlive.com β Best online casino bonus offers & promo codes in Michigan 2026
- www.epifive.com β EWS Retirement: Set EWSAllowedAppIDs in Exchange Online
- technologymatch.com β Microsoft EWS Retirement in Exchange Online: What to Do ...
- changepilot.cloud β Microsoft EWS Retirement: Key Dates and What to Do Next
- dailysecurityreview.com β Microsoft Exchange Online Outage Impacts Outlook Web Users
- techcommunity.microsoft.com β Tag:"administration" | Microsoft Community Hub
-
Exchange Online Enforces EWSAllowedAppIDs Policy
Exchange Online enforces the EWSAllowedAppIDs requirement as Microsoft eliminates the older EWSEnabled fallback and starts blocking unlisted applications. Administrators must whitelist third-party tools to prevent service disruptions for Microsoft 365 work accounts and Mac email synchronization. Automated population of the allow list relies on prior traffic data, but IT teams are required to build explicit lists. This deadline follows multiple schedule adjustments by Microsoft, including initial plans to turn off Exchange Web Services for unconfigured tenants before a permanent removal date scheduled for April 1, 2027.
Why it matters
Microsoft implements stricter access controls for Exchange Web Services to secure cloud environments against unauthorized application traffic. Tenants that retain an enabled status alongside an empty allowed-application list face immediate blocking of unvetted software. Administrators must audit tenant configurations to maintain email client functionality across enterprise environments.
What is confirmed
- Exchange Online enforced the EWSAllowedAppIDs requirement on October 10.
- Tenants with an enabled EWS status and an empty allowed-application list stop permitting all applications and begin blocking access.
What to watch next
- Reports of widespread application outages following the October 10 enforcement date.
- Official Microsoft guidance regarding tenants failing to configure explicit allow lists prior to the April 2027 permanent removal date.
confidence 100%Sources used for this update (6)
- www.cbssports.com β Best betting sites for October 2026: Top online sportsbooks reviewed
- borncity.com β MC1485116: Exchange Online erzwingt EWSAllowedAppIDs bis 10 ...
- learn.microsoft.com β Control access to EWS in Exchange | Microsoft Learn
- techcommunity.microsoft.com β Tag:"exchange online" in "Exchange Team Blog" | Microsoft ...
- everywan.com β Your Exchange Online backup hangs on a single text field
- mailboxinsights.com β Exchange Online EWS Retirement: What Breaks And What To Do
-
Exchange Online Enforces EWSAllowedAppIDs Requirement on October 10
Exchange Online enforces the EWSAllowedAppIDs requirement on October 10, following adjustments to Microsoft implementation timelines. Microsoft originally planned to turn off Exchange Web Services on October 1 for tenants that had not configured settings, leading to a permanent removal date of April 1, 2027. Following the initial milestone date, Microsoft posted message MC1485116 on October 2. Administrators must whitelist third-party applications to prevent service disruptions for Microsoft 365 work accounts and Mac email synchronization, as the older EWSEnabled=True fallback is eliminated. While automated population of the allow list utilizes prior traffic data, teams must build explicit lists.
Why it matters
This enforcement shift alters how administrators manage application access within Microsoft Exchange Online. The policy changes affect third-party tools and mail clients reliant on Exchange Web Services. Understanding the exact timeline shifts helps IT teams avoid unexpected outages.
What is confirmed
- Exchange Web Services enforcement takes effect on October 10.
- Microsoft posted message MC1485116 on October 2.
What to watch next
- Observation of tenant service disruptions following the October 10 enforcement date.
- Additional guidance from Microsoft regarding the April 1, 2027 permanent removal.
confidence 100%Sources used for this update (3)
- www.pennlive.com β Best PA online casino bonus offers & no-deposit codes for July 2026
- www.pennlive.com β Best PA online casinos: Top new Pennsylvania casino sites August 2026
- emailexpert.com β Microsoftβs EWS switch-off did not start on 1 October. It ...
-
Exchange Online Enforces EWSAllowAppIDs on October 10
Microsoft is ending the EWSEnabled=True fallback within Exchange Online, requiring administrators to whitelist applications by October 10 or face disruptions with third-party tools. This enforcement impacts Microsoft 365 work accounts and Mac email synchronization. Administrators must inventory applications utilizing Exchange Web Services and construct an explicit allow list. While Microsoft plans to auto-populate portions of the list between October 8 and October 9 using traffic from the prior 60 days, teams are advised to build their own lists to prevent blind spots and service interruptions.
Why it matters
Exchange Web Services is entering its final stage before Microsoft removes access, creating potential syncing failures for users relying on Apple Mail and other third-party clients. Apple is actively planning a fix to address the incoming disruption to Mac email. Organizations must manually verify tenant states and register required application IDs to maintain uninterrupted connectivity.
What is confirmed
- Exchange Online will enforce the EWSAllowedAppIDs requirement on October 10.
- Microsoft is retiring its EWSEnabled=True fallback in Exchange Online.
- Microsoft plans to fill the allow list on October 8 and October 9 from 60 days of activity.
- The change threatens to disrupt third-party tools and Mac email synchronization for Microsoft 365 work accounts.
Still unconfirmed
- Apple is planning a fix to counter the Microsoft Exchange shutdown affecting Mac email.
What to watch next
- Execution of the October 8 to October 9 auto-population by Microsoft
- Final enforcement of the EWSAllowedAppIDs requirement on October 10
- Release of any software updates from Apple to address Mac email syncing
confidence 95%Sources used for this update (9)
- Neowin β MC1485116: Exchange Online enforces EWSAllowedAppIDs requirement on October 10
- AppleInsider β Apple plans fix as Microsoft's Exchange shutdown disrupts Mac email
- MacRumors β Microsoft 365 Work Accounts May Stop Syncing in Apple Mail
- Auburn University β Upcoming changes to Microsoft 365 email access
- The Register β Exchange Web Services enters the final stretch before Microsoft pulls access
- www.si.com β Best Betting Sites Canada for October 2026: Expert Tested and Ranked
- 9to5windows.com β Exchange Online Will Enforce the EWSAllowedAppIDs Requirement ...
- www.tun.lat β Exchange Online Enforces the EWS Allow List on October 10 ...
- trustlist.uk β Exchange Online: apps using EWS must be on an allow list from ...
Community Sentiment: How do you assess this situation?
Voice your perspective Β· Real-time aggregated sentiment from the Live Feeds community