Exchange Updates & Release Notes
15 updates curated from 1 source by the Releasebot Team. Last updated: Nov 22, 2026
- Nov 18, 2026
- Date parsed from source:Nov 18, 2026
- First seen by Releasebot:Nov 22, 2026
Sending From Email Aliases – General Availability
Exchange releases Sending from Aliases for Exchange Online, now generally available. Users can send and reply from mailbox aliases in supported Outlook clients, while admins can enable the feature tenant-wide and manage domain-level sending restrictions.
Today we are announcing the General Availability (GA) of Sending from Aliases for Exchange Online. This was a highly requested feature that now empowers users to send emails from any alias (proxy address) associated with their mailbox, not just their primary SMTP address. Read on to learn how it works, how to enable it, and what’s next. What Is Sending From Aliases? Sending from Aliases allows Exchange Online users to send emails using any of their configured aliases or proxy (or secondary) SMTP addresses. Previously, aliases could only receive mail, and all outgoing messages used the primary SMTP address of the mailbox. Workarounds like shared mailboxes or distribution groups were used in the absence of native alias sending support. With the Sending From Aliases feature, which until now has been in Public Preview, users can: Send from any alias directly using Outlook clients. Reply from aliases when an email was addressed to it. Select which aliases to display in supported clients. How Does It Work? Admin Setup Enable at the tenant level via PowerShell: Set-OrganizationConfig -SendFromAliasEnabled $True Or use the Exchange Admin Center: Go to Settings → Mail Flow → Turn On Sending from Aliases. Aliases for users are managed in the M365 Admin Center. Admin who wishes to block a domain from being able to send can set the domain as Receive Only in the M365 Admin Center. It might take up to 60 minutes for this change to take effect in your tenant. User Experience Outlook on the Web Go to Settings → Compose to view and select aliases Outlook Desktop (Windows/Mac) Use the From field dropdown or enter the alias manually Outlook Mobile Tap the From field to select from available aliases Replies automatically use the alias the message was sent to. Aliases are given to users for various reasons. If, for whatever reason, a user should not receive or send messages using a given alias, it is possible to set the entire domain to Send-only or Receive-only. To set a domain to Send-only or Receive-only, use the SendingFromDomainDisabled or SendingToDomainDisabled parameter of Set-Accepteddomain cmdlet from Exchange Online Powershell. For example, if you want to prevent users from sending emails using their onmicrosoft.com address, run the following command: Set-Accepteddomain contoso.onmicrosoft.com -SendingFromDomainDisabled $true More nuanced restrictions would need to be implemented with mail flow rules or organizational policies that users should follow. Known Gaps or Behavior Changes There are certain features that rely on the email address used to send or receive messages. Rules set up that do not account for aliases such as journaling or routing rules, may not work as expected. Other features may work with the mailbox identity and be unable to differentiate between aliases used. This feature is for Exchange Online-hosted mailboxes only. Messages to and from on-premises can be subject to rewriting the aliases on those servers. In Hybrid scenarios, when email is sent from on-premises to Exchange Online, email is sent to user’s mail.contoso.onmicrosoft.com address. With send-as-alias feature enabled, this address is preserved and not resolved to user’s primary address. This can cause issues like OOF response coming from user’s mail.contoso.onmicrosoft.com address instead of the email address representing user’s actual email domain name (contoso.com). Please raise a DCR with the Outlook team if your organization would like autoreply messages to avoid using mail.contoso.onmicrosoft.com addresses. For shared mailbox, send from alias feature works only with OWA when delegate opens it using “Open another mailbox” option. For Outlook client, send from alias feature is not supported for shared mailbox at all. Various types of rules in Exchange Online may look for specific email addresses and not match aliases, resulting in the rule not acting on a subset of messages from a given mailbox. Features with rules include hygiene, journaling, and mail flow rules. Message Trace queries using a primary SMTP address return results that do not include messages sent using an alias. To trace messages sent to or from an alias, you need to use the alias in your query. This is less of a known issue and more about highlighting the change to existing behavior. Some companies have set up Outlook clients with aliases or display names that differ from the user’s primary email address and display name stored on the mailbox. Different email addresses or display names may appear on messages when the feature is enabled. When the sending from aliases feature is enabled, it may cause a change in behavior for what shows up in sent messages’ From field. Future Enhancements While the GA release delivers the core functionality, we still plan to expand the feature set in future updates. GA is a major milestone for this important feature, and we want to show our commitment to supporting it and customers who choose to use it with this announcement. Additional functionality we’re investigating (but not necessarily committing to) includes: Display names per alias Additional filtering or default controls Calendar support Follow up communications will announce which features we plan to work on and deliver post-GA. Next Steps Admins who have not done so already can review and enable the feature for your organization using the guidance above. Please raise support tickets if you uncover any issues that you discover and are not called out in the Known Gaps section. This feature was a significant shift from the previous behavior of Exchange Online and edge cases may still exist. Monitor for announcements on future enhancements to the feature. Exchange Online Team
Original source - Nov 17, 2026
- Date parsed from source:Nov 17, 2026
- First seen by Releasebot:Nov 22, 2026
Reject Direct Send now Generally Available in Exchange Online
Exchange Online makes Reject Direct Send generally available worldwide, helping admins block unauthenticated messages that spoof their accepted domains. The Change Optics Report is also generally available, and the protection is rolling out by default for new tenants.
In April 2025, we introduced the Reject Direct Send setting in Public Preview to give Exchange Online admins a way to block unauthenticated Direct Send traffic that uses their own domains. Today, we’re pleased to announce that Reject Direct Send is now Generally Available for Exchange Online worldwide tenants. Thank you to everyone who enabled the setting during Public Preview and shared feedback through the blog comments, the feedback mailbox, support and our MVP community. Your feedback shaped the improvements we made ahead of GA, including the Change Optics Report, which is now also Generally Available. Customers have already embraced the setting: more than 70,000 organizations have enabled Reject Direct Send to add an extra layer of protection to the organizations. What is Direct Send? Direct Send is a method used to send email directly to an Exchange Online organization’s hosted mailboxes from on-premises devices, applications or third-party cloud services using the organization’s own accepted domain. It requires no authentication, as it mimics anonymous inbound mail from the internet apart from the sender domain. Many organizations have no need for it, which makes it an unnecessary avenue for spoofing their own domains. For more background, see Direct Send vs sending directly to an Exchange Online tenant. What does Reject Direct Send do? When enabled, Reject Direct Send blocks messages sent to your organization anonymously using an address in one of your accepted domains. Key points: Only the P1 MAIL FROM (envelope sender) address is evaluated. The P2 From header is not checked. “Anonymous” means the message is not attributed to any mail flow connector. Subdomains are included if the accepted domain has “Accept mail for all subdomains” enabled (MatchSubDomains = True). It works regardless of where your MX record points. It is one layer of protection. Spoofing of domains you don’t own is not Direct Send and continues to be handled by existing anti-spoofing protections. Rejected messages receive the following response: 550 5.7.68 TenantInboundAttribution; Direct Send not allowed for this organization from unauthorized sources What’s changed since Public Preview Visibility of Direct Send traffic: The Change Optics Report in the Exchange admin center (Reports > Mail flow > Change Optics Report) shows example Direct Send messages received by your organization in the DRS (Direct Send traffic) scenario, so you can identify legitimate senders before you enable the setting. The report is now Generally Available. See The Change Optics Report is now Generally Available in Exchange Online | Microsoft Community Hub. Azure Communication Services: The known issue affecting Azure Communication Services (ACS) Email has been resolved. Clarified documentation: FAQs covering subdomains, required permissions, connector attribution and third-party MX scenarios. Secure by default for new tenants As shared during Public Preview, we plan to enable Reject Direct Send by default for new Exchange Online tenants, without the option to disable it, as part of our commitment to making organizations secure by default. This is being rolled out at the time of publishing. Before you enable Reject Direct Send as an existing tenant Review the DRS scenario in the Change Optics Report to find the devices, applications and services sending Direct Send traffic to your organization. Your domains’ SPF records are another good place to start. For each legitimate sender, create a partner inbound connector that matches its TLS certificate (recommended) or its sending IP addresses. See Configure mail flow using connectors in Exchange Online[https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/use-connectors-to-configure-mail-flow/use-connectors-to-configure-mail-flow]. Confirm that messages from each partner are attributed to the connector, for example by running: Get-MessageTraceV2 -MessageId "<message ID>" | Get-MessageTraceDetailV2 | Format-List How to enable the setting The setting remains opt-in and off by default for existing tenants. An admin with the Organization Configuration role can enable it with: Set-OrganizationConfig -RejectDirectSend $true Changes propagate across the service within 30 minutes. To check the current value: Get-OrganizationConfig | Format-List RejectDirectSend Known issue: third-party forwarding without SRS If someone in your organization sends a message to a third party who forwards it back to your organization, and the third party’s email provider does not support Sender Rewriting Scheme (SRS), the message returns with your original sender address. These messages already fail SPF today; with Reject Direct Send enabled and no partner connector in place, they will be rejected. Availability Reject Direct Send is Generally Available for Exchange Online tenants in the worldwide environment. It is not currently available for GCC High and DoD environments. Microsoft 365 Messaging Team
Original source All of your release notes in one feed
Join Releasebot and get updates from Microsoft and hundreds of other software products.
- Nov 10, 2026
- Date parsed from source:Nov 10, 2026
- First seen by Releasebot:Nov 22, 2026
Released: November 2026 Exchange Server Security Updates
Exchange releases November 2026 security updates for Exchange Server Subscription Edition RTM, addressing reported and internally found vulnerabilities. The update guidance also covers resolving instability linked to October Windows Server updates and advises Exchange 2016 and 2019 users to upgrade.
Microsoft has released Security Updates (SUs) for vulnerabilities found in: Exchange Server Subscription Edition (SE) SUs are available for the following specific versions of Exchange Server: Exchange SE RTM The November 2026 SUs address vulnerabilities responsibly reported to Microsoft by security partners and found through Microsoft’s internal processes. These vulnerabilities affect Exchange Server. Exchange Online customers are already protected from the vulnerabilities addressed by these SUs and do not need to take any action other than updating any Exchange servers or Exchange Management tools workstations in their environment. More details about specific CVEs can be found in the Security Update Guide (filter on ‘Server Software’ under Product Family for Exchange SE). Looking for Exchange 2016 and 2019 information? Exchange Server 2016 and 2019 are no longer tested for vulnerabilities and there are no updates released. If you are using those versions of Exchange, you should consider them permanently vulnerable and should upgrade your organization immediately. Issues resolved Exchange servers may become unstable after installation of October 2026 Windows updates | Microsoft Community Hub – to address the issue where any version of Exchange might be impacted by instability after installation of Windows Server October 2026 updates, please install November 2026 updates for Windows Server. Customers who have created the registry key to address the issue in October can leave the registry key in place, but the key is not required once November 2026 Windows Server updates are installed. It does not matter in which order November 2026 Exchange Server vs. Windows Server updates are installed. Update installation The following update paths are available: Inventory your Exchange Servers to determine which updates are needed using the Exchange Server Health Checker script. Running this script will tell you if any of your Exchange Servers are behind on updates (CUs, SUs, or manual actions). After setup is completed, please reboot the server and check that all Exchange services have started properly. If some services are in a disabled state, that indicates that something interrupted installation of the update. Please see the Workaround 1 in this article. If you encounter errors during or after installation of Exchange Server, run the SetupAssist script. If something does not work properly after updates, see Repair failed installations of Exchange Cumulative and Security updates. Also please see File version error when you try to install Exchange Server updates. FAQs Our organization is in Hybrid mode with Exchange Online. Do we need to do anything? Exchange Online is already protected, but this SU needs to be installed on your Exchange servers, even if they are used only for management purposes. If you change the auth certificate after installing an SU, you should re-run the Hybrid Configuration Wizard. The last SU/HU we installed is a few months old. Do we need to install all SUs in order to install the latest one? SUs are cumulative. If you are running a CU supported by the SU, you do not need to install all SUs or HUs in sequential order; simply install the latest SU. Please see this blog post for more information. Do we need to install SUs on all Exchange Servers within our organization? What about ‘Management Tools only’ machines? Our recommendation is to install SUs on all Exchange Servers and all servers and workstations running the Exchange Management Tools to ensure compatibility between management tools clients and servers. If you are trying to update the Exchange Management Tools in the environment with no running Exchange servers, please see this. We installed an Exchange SU or HU update and are running Windows Server 2025. How do we uninstall updates as they are not listed on Windows Server 2025? We do not recommend uninstalling Security Updates. But see Can't view or uninstall Exchange security or hotfix updates in Control Panel on Windows Server 2025 | Microsoft Support. Our organization still uses Exchange 2016 or 2019. After October 2026, we see no updates or vulnerabilities mentioned for those versions. Are they not vulnerable? Exchange 2016 and 2019 are out of support, and the Period 2 ESU program ended. Exchange Server 2016 and 2019 are no longer tested for vulnerabilities and there are no updates released. If you are using those versions of Exchange, you should consider them permanently vulnerable and should upgrade your organization immediately. Documentation may not be fully available at the time this post is published. This post might receive future updates; they will be listed here (if available). The Exchange Server Team
Original source - Nov 9, 2026
- Date parsed from source:Nov 9, 2026
- First seen by Releasebot:Nov 22, 2026
Now available: OAuth authentication for on-premises Exchange mailbox migrations to Microsoft 365
Exchange now supports OAuth authentication for Microsoft 365 mailbox migrations to and from on-premises environments, offering an optional alternative to Basic authentication for hybrid and non-hybrid organizations. Availability is limited to specified Microsoft 365 and Exchange Server versions.
We are happy to announce that Microsoft 365 Mailbox Replication Service (MRS) now supports OAuth as an authentication method when migrating mailboxes between Microsoft 365 and an on-premises Exchange environment. OAuth offers a secure alternative to using the Basic authentication credentials (username and password) of a privileged on-premises Active Directory user. Until now, MRS has not allowed customers to authenticate with OAuth for these migrations. Once OAuth for MRS is configured, tenant administrators can create an OAuth migration endpoint and use it in migration batches or in onboarding and offboarding move jobs. You can use this method in both hybrid and non-hybrid organizations. OAuth for mailbox migration is available: In Microsoft 365 multi-tenant (WW) environments only. We will have news about availability in other cloud environments over next several months. For on-premises organizations running the October 2026 or newer version of Exchange Server Subscription Edition (SE) or Exchange Server 2019 CU15 with the latest ESU (October 2026). OAuth is an optional alternative to Basic authentication, not a replacement. No action is required, and your existing migration endpoints and in-progress migrations are not affected. For step-by-step instructions, see Create migration endpoints with OAuth authentication | Microsoft Learn. Exchange Online Migration Team
Original source - Oct 26, 2026
- Date parsed from source:Oct 26, 2026
- First seen by Releasebot:Nov 22, 2026
EWS Deprecation Is Here – What This Means To You
Exchange begins enforcing EWS deprecation in its worldwide cloud, requiring tenants that keep EWS enabled to specify permitted apps in EWSAllowedAppIDs. Microsoft has started warning and disabling EWS for some tenants, with existing enabled tenants protected from changes until April 2027.
The deprecation of EWS in Exchange Online starts today. This is a multi-step process, years in the making, and this post has lots of important information. We will keep this post updated if we have new information to add. The first change, as previously announced, starting early October 2026, means setting EWSEnabled to True will no longer be sufficient on its own to keep EWS working in the tenant: an AppID allow list (EWSAllowedAppIDs) will be required to specify apps that you want to permit access to EWS. What happens next Customer tenants in our multi-tenant (WW) cloud EWSEnabled state EWSAllowedAppIDs state When True Null We populated EWSAllowedAppIDs for all such tenants on October 10-11. After October 11, any tenant admin who sets EWSEnabled = True, must populate EWSAllowedAppIDs by themselves. If the tenant is already set to EWSEnabled = True, Microsoft will not make changes to EWS availability until April 2027. Null Null Tenants will get a 7-day warning in Message Center to tell them we will populate their EWSAllowedAppIDs (based on 60-day usage) and then set EWSEnabled = False. This process has now started. If EWS gets disabled, tenant admins can temporarily re-enable it by following Exchange Online EWS application stopped working? Do this. | Microsoft Community Hub. False (Any) EWS is already disabled by tenant admin; Microsoft will make no changes. Multi-tenant WW cloud now requires the presence of EWSAllowedAppIDs if EWSEnabled = True. Customer tenants in our Sovereign cloud environments Stay tuned for more detailed timeline. Other Important Information Changing Related EWS Settings Please remember that: Changes to EWSAllowedAppIDs take 24 hours to take effect Changes to EWSEnabled take typically under 1 hour (but can be up to 4 hours) EWSAllowList property does not need to be configured and/or changed (it is not related to EWS deprecation). Please review this blog if unclear. If EWS gets disabled by Microsoft, only the tenant admin can re-enable it (Microsoft cannot do this). Step-by-step process is described in Exchange Online EWS application stopped working? Do this. | Microsoft Community Hub. Microsoft Applications EWS Use We know customers are still seeing traffic from some Microsoft applications. These applications (if they show up in the EWS usage report) still need to be added to the EWSAllowedAppIDs list to keep working. The latest on each of these: Outlook for Windows: Customers should be on latest builds (August 2026 build 16.0.20430.20092 or higher). If customers see problems with EWS disabled, it may be due to customer forced configuration (see this example). We recommend testing to determine if blocking EWS for the Office client AppID is possible in your tenant, without impact. Microsoft successfully disabled EWS internally over a year ago. Outlook for Mac: Please update to the latest builds and switch to the new Outlook for Mac. If you are already using new Outlook, then this change will not affect you. If you still need to use Classic Outlook, ensure the “Microsoft Office” AppID is in your EWSAllowedAppIDs list. Excel Power Query: Please see https://aka.ms/xlewsretirement. PowerBI: we will provide an update soon. Exchange Server / Exchange hybrid: please see Impact of Exchange Online EWS Deprecation on Hybrid Rich Coexistence and Cross-org Sharing | Microsoft Community Hub. Updates to this blog post: 10/26/2026: Added a note that clarifies that if the tenant is already set to EWSEnabled = True, Microsoft will not make EWS changes until April 2027. 10/21/2026: Updated the post to reflect that EWS disablements have been started and linked to the reference on how to re-enable it. 10/15/2026: Updated the table with next steps for WW tenants and reorganized the information for readability. 10/2/2026: Mentioned that EWSEnabled settings can have some variability in how quickly they apply (to account for a few occurances we have seen). The Exchange Team
Original source Similar to Exchange with recent updates:
- Google Workspace updates69 release notes · Latest Nov 20, 2026
- Asana updates17 release notes · Latest Feb 1, 2026
- ChatGPT updates256 release notes · Latest Nov 20, 2026
- OpenAI Models updates55 release notes · Latest Nov 18, 2026
- Gemini updates479 release notes · Latest Nov 20, 2026
- Gemini API updates160 release notes · Latest Nov 19, 2026
- Oct 21, 2026
- Date parsed from source:Oct 21, 2026
- First seen by Releasebot:Nov 22, 2026
Exchange Online EWS application stopped working? Do this.
Exchange is progressing with the retirement of Exchange Web Services in Exchange Online. Tenant administrators can temporarily re-enable EWS for affected apps, but that option ends in April 2027, so customers should move to application versions that no longer rely on the protocol.
As we have been announcing, Exchange Web Services (EWS) protocol is being turned off in Exchange Online. This protocol is used by various applications such as: Apple Mail / Calendar on macOS Classic Outlook on macOS Different Outlook desktop add-ins Outdated versions of Outlook Desktop on Windows Various other applications such as backup applications that our customers purchase from various software vendors Such applications might give you various errors when EWS is turned off, from repeatedly asking for username or password, to giving you a clear error that EWS protocol is not available. Retirement of this protocol is now in progress, you can see our progress in this post. If your EWS applications stopped working, do this Please note that Microsoft support cannot perform these steps for you. Only the tenant administrator can follow these steps and re-enable EWS. Check your tenant Message Center posts. Use the Search field to look for a post with a subject of “Action may be required: EWS will be disabled in your tenant in 7 days” or “EWS has been disabled in your tenant”. This will tell you when EWS was turned off in your tenant. If you do find a post saying that Microsoft turned off EWS in your tenant, you have two options: Option 1 (easiest): Use Microsoft 365 admin center Baseline Security Mode Go to the Microsoft 365 admin center, Baseline security mode page: https://admin.cloud.microsoft/#/baselinesecuritymode Find the “Block access to Exchange Web Services” line and click on it: Uncheck (de-select) the “Block your entire organization from using EWS” checkbox (1) and then press the “Apply change” (2) button: Now check (select) the same “Block your entire organization from using EWS” checkbox (3) and then again press the “Apply change” (4) button: You have now re-enabled EWS in your tenant. The setting change usually takes less than an hour to start working (and your EWS applications will just start working again). But note that this can take up to 4 hours in rare cases. It might be a bit confusing that while you have checked / selected the “Block” setting, the underlying setting on your tenant is now actually set to allow EWS (EWSEnabled = True) with a specific app(s) in the EWS allow list. To learn which EWS applications are in the allow list to use EWS in your tenant, see the Scope Summary section (5). Apps that are listed / excluded are the ones that are excluded from being blocked. Option 2 (more control): Use Exchange Online PowerShell Install Exchange Online PowerShell module and then, connect to Exchange Online PowerShell. Paste the following command into your connected PowerShell window: Get-OrganizationConfig | Fl EWSEnabled If the answer is “EwsEnabled : False” then EWS is disabled – this is your problem Paste the following command into the PowerShell window: Set-OrganizationConfig -EWSEnabled $true You have now re-enabled EWS in your tenant. The setting usually takes less than an hour to start working (and your EWS applications will just start working again). But note that this can take up to 4 hours in rare cases to start working. Finding out which EWS applications are allowed in your tenant Using the Baseline security mode: see the Scope Summary as shown in the above screenshot and use Exclude specific apps to modify the list. Using the Exchange Online PowerShell: paste the following command into the Exchange Online PowerShell window: Get-OrganizationConfig -RetrieveEwsOperationAccessPolicy | Fl EwsAllowedAppIDs This will result in a list of EWS applications that Microsoft has detected were in use within last 60 days in your tenant. We already added them to “EwsAllowedAppIDs” – which is an “allow list” for EWS applications. You do not need to modify this list if everything is working properly once you re-enabled EWS by using previous steps. You can add additional apps to this list. Read more here. Modifications to applications in the allow list take 24 hours to take effect. The steps above will work only temporarily (until April 2027) We are now in the first stage of EWS disablement, where customers are still able to re-enable EWS. Re-enabling EWS will stop working in April 2027. The long-term solution is to update your applications to the application versions that do not use EWS. You must contact your application vendor to get the updated application version, or if you created the application yourself, you must change the code to not use EWS anymore. EWS will not be an option that your client applications can use after April 2027. The EWS Deprecation Team
Original source - Oct 19, 2026
- Date parsed from source:Oct 19, 2026
- First seen by Releasebot:Nov 22, 2026
The Change Optics Report is now Generally Available in Exchange Online
Exchange now offers the Change Optics Report for Exchange Online worldwide tenants, giving administrators sample message data and traffic trends to investigate potentially affected mail flow and prepare for service changes. The report includes onmicrosoft.com external traffic and Direct Send scenarios.
Change management is an important part of how we improve Exchange Online. Some changes to the service can affect existing mail flow, and the key to minimizing disruption is giving administrators the visibility they need to identify affected traffic and take action before those changes arrive. Earlier this year, we released the Change Optics Report into Public Preview (Change Optics Report released into Public Preview to showcase messages impacted by future changes | Microsoft Community Hub). Today, we're pleased to announce that the Change Optics Report is now generally available for Exchange Online worldwide tenants. Thank you to everyone who tried the report during Public Preview and provided feedback. That feedback helped us improve the experience before General Availability (GA). What is the Change Optics Report? When we announce changes that could affect the sending or delivery of certain messages, the Change Optics Report provides a central place for administrators to identify potentially affected traffic. The report displays a sample set of messages from your organization that match the characteristics expected to be affected by a particular change. Administrators can use these samples to begin an investigation, determine where remediation might be required, and monitor progress as affected traffic is reduced ahead of the change. Scenarios available at GA The Change Optics Report currently includes two scenarios: Onmicrosoft.com external traffic (OMC) This scenario identifies messages being sent externally using onmicrosoft.com addresses. Throttling of this traffic has now rolled out, so organizations that continue to see this usage should investigate and move appropriate sending scenarios to a custom domain. For more information, see Limiting Onmicrosoft Domain Usage for Sending Emails. Direct Send traffic (DRS) This scenario identifies Direct Send messages received by your tenant. Organizations planning to use the Reject Direct Send setting can use the report to identify legitimate Direct Send traffic and ensure those senders are appropriately handled before enabling the setting. For more information, see Introducing more control over Direct Send in Exchange Online. As additional Exchange Online changes are introduced, we plan to add scenarios to the Change Optics Report where additional visibility can help administrators prepare. What's changed since Public Preview? Customer feedback during Public Preview helped us improve the report before GA including clearer report and scenario descriptions, filtering noisy message types like journaling reports, and displaying the P1 envelope sender address used for onmicrosoft.com enforcement. Using the Change Optics Report You can find the report in the Exchange admin center under: Reports > Mail flow > Change Optics Report The report contains two main pages: Summary The Summary page displays message-volume trends for the scenarios being tracked. This makes it possible to monitor potentially affected traffic and see whether remediation is reducing that traffic over time. Details The Details page displays example messages for the selected scenario and provides the main message properties needed to begin an investigation. The table can be exported, and Message Trace can be used when additional information about an individual message is required. The Export function currently exports data loaded into the table rather than all data for the selected time range. We have plans to enhance the Export functionality but not ETA to report yet. Remember that Change Optics provides samples of affected messages. It should be used to identify sending patterns and scenarios requiring investigation rather than as an exhaustive message trace. Availability The Change Optics Report is generally available to Exchange Online tenants in the worldwide environment. It is not currently available in GCC, GCC High, DoD, or other sovereign cloud environments. We will continue expanding the Change Optics framework as new scenarios arise where giving administrators early visibility can help reduce the impact of future service changes. As always, let us know what you think in the comments below. The Exchange Online Messaging Team
Original source - Oct 17, 2026
- Date parsed from source:Oct 17, 2026
- First seen by Releasebot:Nov 22, 2026
Released: October 2026 Exchange Server Security Updates
Exchange releases October 2026 security updates for Subscription Edition and eligible Exchange 2016 and 2019 deployments, addressing vulnerabilities and fixing calendar and ContentEngine issues. This is the final month of Period 2 ESU updates for Exchange 2016 and 2019, with future updates limited to Subscription Edition.
Update October 16, 2026: For more information related to installation of October 2026 updates for Windows Server and the possible impact on Exchange Server, please see Exchange servers may become unstable after installation of October 2026 Windows updates | Microsoft Community Hub. Microsoft has released Security Updates (SUs) for vulnerabilities found in: Exchange Server Subscription Edition (SE) Exchange Server 2019 Exchange Server 2016 SUs are available for the following specific versions of Exchange Server: Exchange SE RTM Exchange Server 2019 CU14 and CU15 (to access, organization must be enrolled into the Period 2 ESU program) Exchange Server 2016 CU23 (to access, organization must be enrolled into the Period 2 ESU program) The October 2026 SUs address vulnerabilities responsibly reported to Microsoft by security partners and found through Microsoft’s internal processes. These vulnerabilities affect Exchange Server. Exchange Online customers are already protected from the vulnerabilities addressed by these SUs and do not need to take any action other than updating any Exchange servers or Exchange Management tools workstations in their environment. More details about specific CVEs can be found in the Security Update Guide (filter on ‘Server Software’ under Product Family for Exchange SE and ‘ESU’ under Product Family for Exchange 2016 and 2019). Exchange 2016 and 2019 Period 2 ESU program ends Exchange Server 2016 and 2019 are out of support for a full year now. October 2026 is the last month when customers who enrolled in the Period 2 Extended Security Update (ESU) program are eligible to receive newly released Exchange Server 2016 and 2019 security updates. After October 2026: Updates will be released for Exchange Subscription Edition (SE) only. Our update announcements and any CVEs released by MSRC will stop mentioning Exchange 2016 and 2019. This does not mean that those versions are not vulnerable to future security issues. We will stop testing Exchange 2016 and 2019 for vulnerabilities. For a limited time, the ability to purchase Period 2 ESU will remain in effect, but that will only get you current with security updates through this October 2026 release. Please continue upgrading your organizations to Exchange SE. Issues resolved in this release Published calendar (.ics) returns HTTP 500 for calendar applications | Microsoft Support ContentEngine deadlock because of missing Korean WordBreaker rule files | Microsoft Support Update installation The following update paths are available: Inventory your Exchange Servers to determine which updates are needed using the Exchange Server Health Checker script. Running this script will tell you if any of your Exchange Servers are behind on updates (CUs, SUs, or manual actions). Install the latest CU. Use the Exchange Update Wizard to choose your current CU and your target CU to get directions. After setup is completed, please reboot the server and check that all Exchange services have started properly. If some services are in a disabled state, that indicates that something interrupted installation of the update. Please see the Workaround 1 in this article. If you encounter errors during or after installation of Exchange Server, run the SetupAssist script. If something does not work properly after updates, see Repair failed installations of Exchange Cumulative and Security updates. Also please see File version error when you try to install Exchange Server updates. FAQs Our organization is in Hybrid mode with Exchange Online. Do we need to do anything? Exchange Online is already protected, but this SU needs to be installed on your Exchange servers, even if they are used only for management purposes. If you change the auth certificate after installing an SU, you should re-run the Hybrid Configuration Wizard. The last SU/HU we installed is a few months old. Do we need to install all SUs in order to install the latest one? SUs are cumulative. If you are running a CU supported by the SU, you do not need to install all SUs or HUs in sequential order; simply install the latest SU. Please see this blog post for more information. Do we need to install SUs on all Exchange Servers within our organization? What about ‘Management Tools only’ machines? Our recommendation is to install SUs on all Exchange Servers and all servers and workstations running the Exchange Management Tools to ensure compatibility between management tools clients and servers. If you are trying to update the Exchange Management Tools in the environment with no running Exchange servers, please see this. We installed an Exchange SU or HU update and are running Windows Server 2025. How do we uninstall updates as they are not listed on Windows Server 2025? We do not recommend uninstalling Security Updates. But see Can't view or uninstall Exchange security or hotfix updates in Control Panel on Windows Server 2025 | Microsoft Support. Our organization does not have the Exchange 2016 and 2019 Period 2 ESU. How can we get current Exchange 2016 or 2019 updates? Since Exchange 2016 and 2019 are now out of support, only customers who have enrolled into the Period 2 ESU program (which is valid between May and October 2026) can obtain Exchange 2016 or 2019 updates released after May 2026. For all other customers still running Exchange 2016 or 2019, we recommend that you upgrade your organization to Exchange SE as soon as possible. Documentation may not be fully available at the time this post is published. Updates to this blog post: October 16, 2026: Updated the banner to link to a post discussing steps you can take if your Exchange servers were impacted by this: Exchange servers may become unstable after installation of October 2026 Windows updates | Microsoft Community Hub. October 15, 2026: Added a banner mentioning that October 2026 Windows Server updates migth create issues on Exchange Servers (no installation of October 2026 Exchange SU updates is required). This post might receive future updates; they will be listed here (if available). The Exchange Server Team
Original source - Oct 2, 2026
- Date parsed from source:Oct 2, 2026
- First seen by Releasebot:Nov 22, 2026
Released: September 2026 V2 Exchange Server Security Updates
Exchange releases September 2026 V2 security updates for Exchange Server SE, 2019, and 2016, adding a fix for CVE-2026-96940. The updates also resolve hybrid mailbox issues, while known calendar and Korean-language issues remain for a future update.
Microsoft has released Security Updates (SUs) for vulnerabilities found in: Exchange Server Subscription Edition (SE) Exchange Server 2019 Exchange Server 2016 SUs are available for the following specific versions of Exchange Server: Exchange SE RTM Exchange Server 2019 CU14 and CU15 (to access, organization must be enrolled into the Period 2 ESU program) Exchange Server 2016 CU23 (to access, organization must be enrolled into the Period 2 ESU program) The September 2026 V2 SUs address vulnerabilities responsibly reported to Microsoft by security partners and found through Microsoft’s internal processes. The difference between the original September 2026 Security Update release and this V2 release is an addition of CVE-2026-96940. Please see the download KB article for more information. These vulnerabilities affect Exchange Server. Exchange Online customers are already protected from the vulnerabilities addressed by these SUs and do not need to take any action other than updating any Exchange servers or Exchange Management tools workstations in their environment. More details about specific CVEs can be found in the Security Update Guide (filter on ‘Server Software’ under Product Family for Exchange SE and ‘ESU’ under Product Family for Exchange 2016 and 2019). Exchange 2016 and 2019 updates are available only under the Period 2 ESU program Exchange Server 2016 and 2019 are out of support. Only customers who enrolled in the Period 2 Extended Security Update (ESU) program are eligible to receive Exchange Server 2016 and 2019 security updates released between May and October 2026. If you are not part of the Period 2 ESU program, migrate to Exchange Server Subscription Edition (SE) to keep receiving the latest security updates. If you have already purchased the Period 2 ESU and need information on accessing the latest Security Updates, please contact us by sending an email to [email protected]. Known issues with this release Published calendar (.ics) returns HTTP 500 for calendar applications | Microsoft Support – to be resolved in a future update ContentEngine deadlock because of missing Korean WordBreaker rule files | Microsoft Support – an issue impacting customers with emails in Korean language, to be addressed in a future update Issues resolved in this release Wrapper messages appear in shared mailbox inbox in hybrid environments | Microsoft Support Availability (free/busy) fails for delegated mailboxes in Exchange hybrid deployments using Graph API only | Microsoft Support Update installation The following update paths are available: Inventory your Exchange Servers to determine which updates are needed using the Exchange Server Health Checker script. Running this script will tell you if any of your Exchange Servers are behind on updates (CUs, SUs, or manual actions). Install the latest CU. Use the Exchange Update Wizard to choose your current CU and your target CU to get directions. After setup is completed, please reboot the server and check that all Exchange services have started properly. If some services are in a disabled state, that indicates that something interrupted installation of the update. Please see the Workaround 1 in this article. If you encounter errors during or after installation of Exchange Server, run the SetupAssist script. If something does not work properly after updates, see Repair failed installations of Exchange Cumulative and Security updates. Also please see File version error when you try to install Exchange Server updates. FAQs Our organization is in Hybrid mode with Exchange Online. Do we need to do anything? Exchange Online is already protected, but this SU needs to be installed on your Exchange servers, even if they are used only for management purposes. If you change the auth certificate after installing an SU, you should re-run the Hybrid Configuration Wizard. The last SU/HU we installed is a few months old. Do we need to install all SUs in order to install the latest one? SUs are cumulative. If you are running a CU supported by the SU, you do not need to install all SUs or HUs in sequential order; simply install the latest SU. Please see this blog post for more information. Do we need to install SUs on all Exchange Servers within our organization? What about ‘Management Tools only’ machines? Our recommendation is to install SUs on all Exchange Servers and all servers and workstations running the Exchange Management Tools to ensure compatibility between management tools clients and servers. If you are trying to update the Exchange Management Tools in the environment with no running Exchange servers, please see this. We installed an Exchange SU or HU update and are running Windows Server 2025. How do we uninstall updates as they are not listed on Windows Server 2025? We do not recommend uninstalling Security Updates. But see Can't view or uninstall Exchange security or hotfix updates in Control Panel on Windows Server 2025 | Microsoft Support. Our organization does not have the Exchange 2016 and 2019 Period 2 ESU. How can we get current Exchange 2016 or 2019 updates? Since Exchange 2016 and 2019 are now out of support, only customers who have enrolled into the Period 2 ESU program (which is valid between May and October 2026) can obtain Exchange 2016 or 2019 updates released after May 2026. For all other customers still running Exchange 2016 or 2019, we recommend that you upgrade your organization to Exchange SE as soon as possible. The release sequence of this specific update was a bit strange. Why is this? This specific update, which adds CVE-2026-96940, was published ahead of its intended schedule. We recommend that customers review the deployment guidance and apply the update at the earliest opportunity. We identified the vulnerability internally and are not aware of active exploitation. For information about additional updates, customers should refer to our established security update channels. Documentation may not be fully available at the time this post is published. This post might receive future updates; they will be listed here (if available). The Exchange Server Team
Original source - Oct 1, 2026
- Date parsed from source:Oct 1, 2026
- First seen by Releasebot:Nov 22, 2026
Action Required: Upgrade ExchangeOnlineManagement PowerShell Module to Version 3.10.1 or Newer
Exchange strengthens PowerShell authentication with security enhancements in module 3.10.1 and later, and plans stricter sign-in enforcement in March 2027. Microsoft recommends upgrading older versions to avoid future connectivity issues.
We have introduced security enhancements to Exchange Online PowerShell authentication in ExchangeOnlineManagement module version 3.10.1 and newer. These enhancements strengthen the authentication flow and provide additional protection against emerging threats. Customers using a version earlier than 3.10.1 should upgrade to version 3.10.1 or later. Exchange Online authentication will increasingly rely on the security enhancements available in these versions, and older module versions may not support future authentication requirements. Customers already using version 3.10.1 or later do not need to take any additional action beyond keeping the module up to date. Microsoft recommends upgrading as soon as possible to benefit from the latest security, reliability, and performance improvements and to prevent any future PowerShell connectivity issues. What is Changing Microsoft plans to begin enforcement of more strict logon requirements for Exchange Online PowerShell module on 31st March 2027. After the enforcement: ExchangeOnlineManagement versions older than 3.10.1 may experience authentication failures in certain interactive authentication scenarios. ExchangeOnlineManagement version 3.10.1 and later will continue to function normally. Upgrading the ExchangeOnlineManagement module to versions 3.10.1 (or newer) is the only thing you need to do. No other changes are required. Who May Be Affected You may be affected if you are: Running ExchangeOnlineManagement versions earlier than 3.10.1. Using PowerShell 7. Using interactive authentication with Web Account Manager (WAM) disabled. You may not be affected if you are using: ExchangeOnlineManagement version 3.10.1 or later. Certificate-Based Authentication (CBA). WAM-based authentication. Windows PowerShell 5.x. Regardless of your current scenario, Microsoft recommends upgrading to ExchangeOnlineManagement version 3.10.1 or later to stay aligned with current and future Exchange Online requirements. To verify the currently installed version: Get-Module ExchangeOnlineManagement -ListAvailable The latest version of the ExchangeOnlineManagement module is available from the PowerShell Gallery: ExchangeOnlineManagement PowerShell Module Frequently Asked Questions We are already using ExchangeOnlineManagement version 3.10.1 or later. Do we need to do anything? No additional action is required for this change if you are already running ExchangeOnlineManagement version 3.10.1 or later. Continue keeping the module up to date to receive the latest security, reliability, and performance improvements. Will our existing scripts be affected if I use Certificate-Based Authentication (CBA)? No. Scripts and automation that use CBA are not expected to be affected by this enforcement because they do not use interactive authentication. However, Microsoft recommends upgrading to ExchangeOnlineManagement version 3.10.1 or later to stay current with the latest security and reliability improvements. Does this change require us to enable WAM? No. This change does not require customers to enable WAM. Do we need to upgrade to the newer module if our current authentication scenario is not affected? Yes. Microsoft recommends that all customers upgrade to ExchangeOnlineManagement version 3.10.1 or later, regardless of their current authentication scenario. While some scenarios may not be affected by the initial enforcement, upgrading helps ensure compatibility with current and future Exchange Online authentication requirements. Exchange Online Manageability Team
Original source - Sep 24, 2026
- Date parsed from source:Sep 24, 2026
- First seen by Releasebot:Nov 22, 2026
Released: September 2026 Exchange Server Security Updates
Exchange releases September 2026 security updates for Exchange Server SE, 2019, and 2016, addressing reported and internally identified vulnerabilities. The update also fixes shared-mailbox wrapper messages and a Hybrid Free/Busy time-zone issue, while noting two known issues for future updates.
Microsoft has released Security Updates (SUs) for vulnerabilities found in: Exchange Server Subscription Edition (SE) Exchange Server 2019 Exchange Server 2016 SUs are available for the following specific versions of Exchange Server: Exchange SE RTM Exchange Server 2019 CU14 and CU15 (to access, organization must be enrolled into the Period 2 ESU program) Exchange Server 2016 CU23 (to access, organization must be enrolled into the Period 2 ESU program) The September 2026 SUs address vulnerabilities responsibly reported to Microsoft by security partners and found through Microsoft’s internal processes. These vulnerabilities affect Exchange Server. Exchange Online customers are already protected from the vulnerabilities addressed by these SUs and do not need to take any action other than updating any Exchange servers or Exchange Management tools workstations in their environment. More details about specific CVEs can be found in the Security Update Guide (filter on ‘Server Software’ under Product Family for Exchange SE and ‘ESU’ under Product Family for Exchange 2016 and 2019). Exchange 2016 and 2019 updates are available only under the Period 2 ESU program Exchange Server 2016 and 2019 are out of support. Only customers who enrolled in the Period 2 Extended Security Update (ESU) program are eligible to receive Exchange Server 2016 and 2019 security updates released between May and October 2026. If you are not part of the Period 2 ESU program, migrate to Exchange Server Subscription Edition (SE) to keep receiving the latest security updates. If you have already purchased the Period 2 ESU and need information on accessing the latest Security Updates, please contact us by sending an email to [email protected]. Known issues with this release Published calendar (.ics) returns HTTP 500 for calendar applications | Microsoft Support – to be resolved in a future update ContentEngine deadlock because of missing Korean WordBreaker rule files | Microsoft Support – an issue impacting customers with emails in Korean language, to be addressed in a future update Issues resolved in this release Wrapper messages appear in shared mailbox inbox in hybrid environments | Microsoft Support Hybrid Free/Busy over MS Graph drops the requester timezone | Microsoft Support Update installation The following update paths are available: Inventory your Exchange Servers to determine which updates are needed using the Exchange Server Health Checker script. Running this script will tell you if any of your Exchange Servers are behind on updates (CUs, SUs, or manual actions). Install the latest CU. Use the Exchange Update Wizard to choose your current CU and your target CU to get directions. After setup is completed, please reboot the server and check that all Exchange services have started properly. If some services are in a disabled state, that indicates that something interrupted installation of the update. Please see the Workaround 1 in this article. If you encounter errors during or after installation of Exchange Server, run the SetupAssist script. If something does not work properly after updates, see Repair failed installations of Exchange Cumulative and Security updates. Also please see File version error when you try to install Exchange Server updates. FAQs Our organization is in Hybrid mode with Exchange Online. Do we need to do anything? Exchange Online is already protected, but this SU needs to be installed on your Exchange servers, even if they are used only for management purposes. If you change the auth certificate after installing an SU, you should re-run the Hybrid Configuration Wizard. The last SU/HU we installed is a few months old. Do we need to install all SUs in order to install the latest one? SUs are cumulative. If you are running a CU supported by the SU, you do not need to install all SUs or HUs in sequential order; simply install the latest SU. Please see this blog post for more information. Do we need to install SUs on all Exchange Servers within our organization? What about ‘Management Tools only’ machines? Our recommendation is to install SUs on all Exchange Servers and all servers and workstations running the Exchange Management Tools to ensure compatibility between management tools clients and servers. If you are trying to update the Exchange Management Tools in the environment with no running Exchange servers, please see this. We installed an Exchange SU or HU update and are running Windows Server 2025. How do we uninstall updates as they are not listed on Windows Server 2025? We do not recommend uninstalling Security Updates. But see Can't view or uninstall Exchange security or hotfix updates in Control Panel on Windows Server 2025 | Microsoft Support. Our organization does not have the Exchange 2016 and 2019 Period 2 ESU. How can we get current Exchange 2016 or 2019 updates? Since Exchange 2016 and 2019 are now out of support, only customers who have enrolled into the Period 2 ESU program (which is valid between May and October 2026) can obtain Exchange 2016 or 2019 updates released after May 2026. For all other customers still running Exchange 2016 or 2019, we recommend that you upgrade your organization to Exchange SE as soon as possible. Documentation may not be fully available at the time this post is published. Updates to this blog post: Sep 24, 2026: Added a new known issue (content index issue when emails in Korean are present) Sep 8, 2026: Corrected one of issues addressed to the free/busy time zone issue over Graph This post might receive future updates; they will be listed here (if available). The Exchange Server Team
Original source - Sep 8, 2026
- Date parsed from source:Sep 8, 2026
- First seen by Releasebot:Nov 22, 2026
Exchange Server AD FS Modern Authentication: Expanded Outlook client support
Exchange expands AD FS Modern Authentication support to Outlook for iOS and Android, enabling access to mailboxes in supported pure on-premises deployments. Updated guidance brings supported client and operating system requirements together.
We are pleased to announce expanded Outlook client support for Exchange Server AD FS Modern Authentication. In our previous update, we announced broad Outlook for Windows/Mac support and support for the native Mail app on iOS and macOS. We are now extending this support to Outlook for iOS and Outlook for Android. Outlook for iOS and Outlook for Android can now use AD FS Modern Authentication to access mailboxes in supported pure on-premises Exchange Server deployments. Deployment context: AD FS Modern Authentication is intended for pure on-premises Exchange organizations that don't use Microsoft Entra ID or an Exchange hybrid configuration. Exchange hybrid organizations should continue to use Hybrid Modern Authentication (HMA) with Microsoft Entra ID. Supported clients at a glance Client Supported release or OS Administrator action Outlook for Windows Supported Microsoft 365 Apps channels and supported perpetual releases; Windows 11 22H2 or later Install the required Windows update, trust the AD FS service URLs, and enable Exchange on-premises Modern Auth in Outlook. Outlook for Mac Outlook for Mac in Microsoft 365, build 16.106 or later; macOS Sequoia or later Use Exchange Server Subscription Edition with the December 2025 or later Security Update, and configure ADFSAuthorizedURLs. Outlook for iOS Latest supported Outlook and iOS versions Follow the Exchange and AD FS configuration guidance. Outlook for Android Latest supported Outlook and Android versions Follow the Exchange and AD FS configuration guidance. Native Mail app for iOS and macOS iOS 17.6.1 or later; macOS Sequoia or later Configure the documented native client application and permissions in the AD FS Outlook application group. Updated documentation We have updated the deployment documentation to make the supported-client requirements easier to review: A new summary brings all supported clients and operating-system requirements together. Outlook for Windows build, Windows update, registry, and AD FS trusted-domain requirements are grouped under the Windows client. Outlook for Mac requirements include the ADFSAuthorizedURLs Terminal configuration, a multiple-namespace example, and the equivalent Mobile Device Management settings. Learn more For complete prerequisites and configuration steps, see Enable Modern Auth in Exchange Server on-premises. For background on the earlier client expansion, see Update on Exchange Server ADFS Modern Authentication support. The Exchange Server Team
Original source - Sep 4, 2026
- Date parsed from source:Sep 4, 2026
- First seen by Releasebot:Nov 22, 2026
Take control of your EWSAllowedAppIDs list before EWS access changes
Exchange is updating how EWSAllowedAppIDs is applied during the EWS retirement rollout. Starting October 2026, Microsoft will preserve customer-managed lists and may populate missing lists from recent usage, while urging organizations to review access and move applications to Microsoft Graph.
As we prepare for the final phase of Exchange Web Services retirement, we are refining how EWSAllowedAppIDs setting (which you can use to define your EWS AppID allow list) will be applied. Our goal is to protect customers from unexpected disruption while keeping control of the allow list with each tenant administrator. We strongly recommend that every customer review EWS usage and configure EWSAllowedAppIDs themselves. If an administrator has already configured EWSAllowedAppIDs, Microsoft will not overwrite or change the list. The customer-managed list remains authoritative. What happens during rollout Beginning October 1, 2026, Microsoft will start enabling the updated behavior as outlined in previous blog post. With this logic change, if the customer has EWSEnabled set to True, EWS will require an Allowed AppID list. The timing will depend on when the change reaches that tenant's environment. If organization has: EWSEnabled = True - Microsoft will ensure that each tenant has an EWSAllowedAppIDs list. If the customer has not created a list, Microsoft will populate one to reduce the risk of an outage when the cloud environment logic changes (and AppID allow list becomes required when EWSEnabled = True). The list will be based on the previous 60 days of usage, and so it may miss applications that run infrequently, and it may include apps you no longer want to have access. This will happen shortly before the logic change takes place. EWSEnabled = Null - Microsoft will only populate EWSAllowedAppIDs, if the customer has not already done so. This will happen a few days before changing EWSEnabled to False during the per-tenant rollout of that setting. This means that tenants that did not change EWSEnabled property from Null could have no AppID allow list defined until later in October. Customers that still require EWS should act now: configure EWSAllowedAppIDs to include only the applications that must continue using EWS, then set EWSEnabled to True. Continue planning to move applications from EWS to Microsoft Graph before EWS is retired. By controlling your own EWSAllowedAppIDs values, you can ensure that only applications that you really want to have EWS access after October rollouts start can still use EWS. The Exchange Team
Original source - Sep 2, 2026
- Date parsed from source:Sep 2, 2026
- First seen by Releasebot:Nov 22, 2026
Exchange 2016/2019: Throttling and Blocking up to the Final Public Update Baseline
Exchange will raise the minimum update level for Exchange 2016 and 2019 servers using on-premises connectors to send mail to Exchange Online, requiring the October 2025 update starting in September 2026. Older servers may be throttled or blocked.
Several years ago, we announced Throttling and Blocking Email from Persistently Vulnerable Exchange Servers to Exchange Online. Since then, we have been periodically updating the “oldest acceptable version” as we keep releasing more security updates for Exchange Server. So far, these changes have been implemented silently. But, today, we are announcing that starting in the second week of September 2026, we will raise the oldest allowed version for Exchange 2016 or Exchange 2019 servers that connect to Exchange Online over an inbound connector type of OnPremises to at least the last available public update version, released in October 2025. This update level was released almost a year ago, and all organizations should have updated to it, since. A very important implication of this change: After going into effect, the oldest Exchange Server version allowed to send email to Exchange Online over the inbound OnPremises connector will be Exchange with October 2025 updates. The next time we update the oldest allowed Exchange Server version for sending email to Exchange Online, the required version of Exchange Server 2016 or Exchange Server 2019 will be newer than any publicly available update. When the next adjustment happens (we estimate in several months), only customers who were enrolled into our ESU program and customers who migrated to Exchange SE will have the required update versions to not be throttled or blocked when sending email to Exchange Online. As a reminder, throttling and blocking of email from persistently vulnerable Exchange servers to Exchange Online: Applies to servers that connect to Exchange Online over an inbound connector type of OnPremises. DOES NOT apply to servers that send email to Exchange Online in other ways (different types of connectors etc.) DOES NOT (currently) apply to “all servers in your organization”, but only to servers that connect to Exchange Online over an inbound connector type of OnPremises. This might change in the future. Finally, we wanted to be clear that the fact that the “oldest version to avoid throttling and blocking in Exchange Online” is always older than the latest version available does not mean that we consider versions older than the latest security update “safe to use”. Anything older than the latest is vulnerable to everything we have fixed/released/announced since that older version. Especially in this calendar year, we have been releasing many security updates for Exchange Server and it is likely that we will continue to do so for the foreseeable future. With a rapidly changing security landscape, no organization should consider it safe to run their organization's business email on an outdated version of Exchange Server. Please see Exchange Server update FAQ. Additional reading: How to pause throttling and blocking of out-of-date on-premises Exchange Servers. The Exchange Server Team
Original source - Aug 19, 2026
- Date parsed from source:Aug 19, 2026
- First seen by Releasebot:Nov 22, 2026
Understanding the new 100 GB mailbox entitlement for Microsoft 365 Business suites
Exchange expands eligible Microsoft 365 Business Basic, Standard, and Premium primary mailboxes from 50 GB to 100 GB through an added storage service plan. Custom mailbox quotas remain unchanged, and the increase does not add archive capabilities.
Microsoft 365 Business Basic, Business Standard, and Business Premium now include an additional 50 GB of primary email storage for eligible users. This brings the supported primary mailbox entitlement from 50 GB to a maximum of 100 GB. We wanted to talk about this change, so Exchange Online administrators understand how this mailbox size increase is delivered. We will focus only on mailbox size in this post. What changed for the Business suites Microsoft announced an additional 50 GB of email storage for Microsoft 365 Business Basic, Business Standard, and Business Premium as part of the 2026 Microsoft 365 packaging updates. The packaging changes are rolling out June - September 2026, with customers receiving advance notice through Message Center before the changes became available in their tenant. The additional storage changes the effective primary mailbox size for eligible Business suite users from 50 GB to 100 GB. The affected commercial product suites are: Microsoft 365 Business Basic Microsoft 365 Business Standard Microsoft 365 Business Premium After the rollout, all users that had the appropriate licenses assigned will have received a new service plan and the corresponding mailbox quota increase. Please note: this mailbox size increase applies only to the above-mentioned suite licenses; there can still be licenses (such as standalone Exchange Online Plan 1) that have the maximum mailbox size set at 50 GB. The supported quota outcome The additional storage establishes a maximum effective quota of 100 GB for the eligible Business suite scenario. A user whose highest applicable Exchange mailbox plan is the Business suite plan receives an effective 100 GB quota when the storage add-on is present. A user who also has an Enterprise or standalone Exchange license that already provides a 100 GB mailbox remains entitled to 100 GB. A user who has multiple licenses assigned, which contain multiple Exchange service plans (this is known as Concurrent Licensing), will be granted the maximum quota provided by a single product – the quotas are not additive across products. For example, a user with one of the Business Suite and a separate Enterprise license containing Exchange Online Plan 2, will still be entitled to 100 GB. The quota increase for the Business suites affects the base mailbox size only. It does not provide archive capabilities. How the additional quota is implemented The Business suite provides the total storage through a combination of service plans: The Business suite Exchange plan is represented by BPOS_S_STANDARD, which grants 50 GB of storage. The additional entitlement is represented by the EXCHANGE_STORAGE_50GB service plan, which adds +50 GB, increasing the total quota to 100 GB. Both plans must be enabled for the user to have the full 100 GB. In your Microsoft 365 admin center, this will look like the following – there is a “standard” license and there is an add-on: Custom mailbox quotas are preserved If an administrator has configured a custom mailbox quota, the additional storage logic does not overwrite that setting. Likewise, removing the add-on does not replace a later administrator-defined custom value. This protects deliberate tenant-level mailbox management choices. For example, if an administrator configured the mailbox for user with a Business suite from the original default of 50 GB down to 20 GB, the user’s quota will remain at 20 GB even after the additional service plan is assigned to them. Reviewing the user’s licenses and service plans In the Microsoft 365 admin center, open Users > Active users, select the user, and review Licenses and apps. Confirm that the user has an eligible Microsoft 365 Business suite and that its included services are enabled. The Billing > Licenses page can also show whether the product was assigned directly or through group-based licensing. Microsoft Graph PowerShell can provide a more detailed service-plan view. The following example retrieves the assigned license details and searches for the storage service plan: $licenses = Get-MgUserLicenseDetail -UserId [email protected] $licenses.ServicePlans | Where-Object ServicePlanName -eq "EXCHANGE_STORAGE_50GB" | Select-Object ServicePlanName, ProvisioningStatus Review the effective Exchange mailbox quota Exchange Online PowerShell shows the quota values that Exchange presents for the mailbox. For example: Get-Mailbox -Identity [email protected] | Format-List IssueWarningQuota, ProhibitSendQuota, ProhibitSendReceiveQuota, UseDatabaseQuotaDefaults For an eligible Business suite user with the additional storage service plan and no custom quota, the effective maximum mailbox quota should be 100 GB. Common license and quota scenarios Business suite with the +50 GB storage add-on: user’s effective primary mailbox maximum is 100 GB. Business suite without the +50 GB storage add-on: base Business mailbox quota continues to apply until the additional service plan is provisioned (should happen automatically). Business suite plus an Enterprise or standalone plan that already grants 100 GB: effective maximum remains 100 GB because Exchange uses the highest applicable entitlement rather than adding the quotas. Business suite plus a lower Exchange capability (for example, F3 license): Business plan remains the highest capability, so the add-on can raise the effective maximum to 100 GB. Custom quota: administrator-defined values remain in effect and are not replaced by the automatic +50 GB boost. +50 GB add-on explicitly removed: for a mailbox using default plan quotas, Exchange returns to the applicable plan default. A custom value set by an administrator remains custom. Rollout and license propagation The additional storage is represented through licensing data, so the service plan must be assigned and processed before Exchange can return the higher effective quota. During broad service-plan rollout or backfill operations, users in the same organization may not all reflect the change at the same time. It is possible that some of your users received additional 50 GB mailbox size increase while others did not – you should expect that this gets resolved automatically if users are licensed by one of affected business suite licenses. Administrators should not remove and reassign an Exchange license solely to force a quota refresh unless Microsoft Support specifically directs that action. Removing a product license removes access to its services and starts the applicable data-retention lifecycle. Please keep using your normal license-assignment processes. Exchange Online Team
Original source
Curated by the Releasebot team
Releasebot is an aggregator of official product update announcements from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.