check before: 2024-10-16
Product:
Exchange, Purview Data Loss Prevention
Platform:
Online, World tenant
Status:
Change type:
Admin impact, Feature update, Updated message, User impact
Links:
Details:
Summary:
IPv6 will be enabled for Exchange Online Accepted Domains starting October 16, 2024, to meet local regulations and enhance security. Organizations should update allow-lists and consider IP version matching for email connectors. Opt-out options and management commands are available if needed.
Details:
Updated October 8, 2024: We have updated the content. Thank you for your patience.
Starting October 16, 2024, we're gradually enabling IPv6 for all customer Accepted Domains that use Exchange Online for inbound mail. Microsoft is modernizing Exchange Online so our customers can easily meet their local regulations as well as benefit from the enhanced security and performance offered by IPv6.
More information on IPv6 support for Microsoft 365 services can be found at: IPv6 support in Microsoft 365 services
[When this will happen:]
October 16, 2024 (previously October 1, 2024)
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
Created:
2024-07-26
updated:
2024-10-11
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS How does it affect me
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
summary for non-techies**
Microsoft is enabling IPv6 for Accepted Domains in Exchange Online starting October 16, 2024, requiring organizations to update their network settings to accommodate both IPv4 and IPv6 addresses, with an option to opt out if necessary.
Direct effects for Operations**
Email Connectivity Issues
If organizations do not update their allow-lists to include IPv6 endpoints, users may experience email delivery failures or delays.
- roles: IT Administrator, Email Administrator
- references: https://learn.microsoft.com/microsoft-365/enterprise/ipv6-support?view=o365-worldwide
Data Loss Prevention Policy Failures
Existing Data Loss Prevention policies that rely on SenderIPRanges may fail if domains are not opted out of IPv6, leading to potential data breaches.
- roles: Compliance Officer, IT Security Manager
- references: https://learn.microsoft.com/microsoft-365/enterprise/ipv6-support?view=o365-worldwide
Increased Support Tickets
Users may report issues related to email access and connectivity, leading to an increase in support tickets and user frustration.
- roles: Help Desk Technician, IT Support Specialist
- references: https://learn.microsoft.com/microsoft-365/enterprise/ipv6-support?view=o365-worldwide
Configuration Management Challenges
Without proper preparation, IT teams may face challenges in managing and configuring IPv6 settings, leading to misconfigurations.
- roles: Network Administrator, System Administrator
- references: https://learn.microsoft.com/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide
Service Disruption for DNSSEC-enabled Domains
DNSSEC-enabled domains may face issues with IPv6 enablement, potentially disrupting email services if not managed correctly.
- roles: DNS Administrator, Network Engineer
- references: https://learn.microsoft.com/powershell/module/exchange/disable-ipv6foraccepteddomain?view=exchange-ps
Configutation Options**
XXXXXXX ... paid membership only
Opportunities**
XXXXXXX ... free basic plan only
Potentional Risks**
XXXXXXX ... paid membership only
IT Security**
XXXXXXX ... paid membership only
explanation for non-techies**
XXXXXXX ... free basic plan only
** AI generated content. This information must be reviewed before use.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
change history
| Date | Property | old | new |
| 2024-10-11 | MC Messages | Updated September 26, 2024: We have updated the content. Thank you for your patience.
Starting October 16, 2024, we're gradually enabling IPv6 for all customer Accepted Domains that use Exchange Online for inbound mail. Microsoft is modernizing Exchange Online so our customers can easily meet their local regulations as well as benefit from the enhanced security and performance offered by IPv6. More information on IPv6 support for Microsoft 365 services can be found at: IPv6 support in Microsoft 365 services [When this will happen:] October 16, 2024 (previously October 1, 2024) | Updated October 8, 2024: We have updated the content. Thank you for your patience.
Starting October 16, 2024, we're gradually enabling IPv6 for all customer Accepted Domains that use Exchange Online for inbound mail. Microsoft is modernizing Exchange Online so our customers can easily meet their local regulations as well as benefit from the enhanced security and performance offered by IPv6. More information on IPv6 support for Microsoft 365 services can be found at: IPv6 support in Microsoft 365 services [When this will happen:] October 16, 2024 (previously October 1, 2024) |
| 2024-10-11 | MC Last Updated | 09/27/2024 02:05:38 | 2024-10-11T00:27:04Z |
| 2024-10-11 | MC prepare | To take advantage of IPv6 connectivity, please make sure that you and your partner's update network allow-lists to allow Exchange Online IPv6 endpoints in the same way it allow-lists IPv4.
The Exchange Online IPv6 endpoints can be found here: Microsoft 365 URLs and IP address ranges. To opt a domain out of inbound IPv6 so traffic flowing to the domain remains IPv4-only, please use Disable-IPv6ForAcceptedDomain -Domain for each domain you want to opt out of IPv6 (Disable-IPv6ForAcceptedDomain (ExchangePowerShell) | Microsoft Learn). IPv6 enablement may impact the source IP type used by Senders when connecting to Exchange Online, as the source and destination IP versions must match. For any IP Address-based Inbound connectors in Exchange Online that are referencing IPv4 addresses, you need to either: Keep the sending server as IPv4. Coordinate with the Sender so the Sender keeps connecting to your domain(s) via IPv4 or Opt your domain(s) out of IPv6 Change the IP based connector to certificate domain based connector. This applies to both OnPremises type (From: Your organization's email server, To: Office 365) and Partner Type connectors (From: Partner organization, To: Office 365). Update: If you are using any Exchange Transport Rules or Data Loss Prevention policies which rely on the SenderIPRanges predicate, you need to opt out all your domains from IPv6. You can manage IPv6 for your Exchange Online Accepted Domains using the commands Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain. Currently, you can check the status of your Accepted Domains with the Get-IPv6StatusForAcceptedDomain command. While some customers have already enabled IPv6, most will see it as disabled until October 16th. After October 16, once IPv6 is enabled for your tenant, if you haven't explicitly set the IPv6 status for your Accepted Domains, the Get-IPv6StatusForAcceptedDomain command will reflect the new default behavior (enabled). IMPORTANT: To ensure your preferred settings are applied, please use the Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain commands before October 16th, after which IPv6 will be enabled by default if you haven't explicitly set it. https://learn.microsoft.com/microsoft-365/enterprise/ipv6-support?view=o365-worldwide https://learn.microsoft.com/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide https://learn.microsoft.com/powershell/module/exchange/disable-ipv6foraccepteddomain?view=exchange-ps | To take advantage of IPv6 connectivity, please make sure that you and your partner's update network allow-lists to allow Exchange Online IPv6 endpoints in the same way it allow-lists IPv4.
The Exchange Online IPv6 endpoints can be found here: Microsoft 365 URLs and IP address ranges. To opt a domain out of inbound IPv6 so traffic flowing to the domain remains IPv4-only, please use Disable-IPv6ForAcceptedDomain -Domain for each domain you want to opt out of IPv6 (Disable-IPv6ForAcceptedDomain (ExchangePowerShell) | Microsoft Learn). IPv6 enablement may impact the source IP type used by Senders when connecting to Exchange Online, as the source and destination IP versions must match. For any IP Address-based Inbound connectors in Exchange Online that are referencing IPv4 addresses, you need to either: Keep the sending server as IPv4. Coordinate with the Sender so the Sender keeps connecting to your domain(s) via IPv4 or Opt your domain(s) out of IPv6 Change the IP based connector to certificate domain based connector. This applies to both OnPremises type (From: Your organization's email server, To: Office 365) and Partner Type connectors (From: Partner organization, To: Office 365). Update: If you are using any Exchange Transport Rules or Data Loss Prevention policies which rely on the SenderIPRanges predicate, you need to opt out all your domains from IPv6. You can manage IPv6 for your Exchange Online Accepted Domains using the commands Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain. Currently, you can check the status of your Accepted Domains with the Get-IPv6StatusForAcceptedDomain command. While some customers have already enabled IPv6, most will see it as disabled until October 16th. After October 16, once IPv6 is enabled for your tenant, if you haven't explicitly set the IPv6 status for your Accepted Domains, the Get-IPv6StatusForAcceptedDomain command will reflect the new default behavior (enabled). IMPORTANT: To ensure your preferred settings are applied, please use the Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain commands before October 16th, after which IPv6 will be enabled by default if you haven't explicitly set it. If you have enabled DNSSEC for mail flow, you may have issues executing the Get-IPv6StatusForAcceptedDomain cmdlet for the DNSSEC-enabled domain. We are rolling out the fix now. Please ensure to run Disable-IPv6ForAcceptedDomain to opt out of the IPv6 enablement if you need to opt a DNSSEC-enabled domain out of the IPv6 by default rollout. The IPv6 rollout will not affect DNSSEC-enabled domains until after Nov 18th. https://learn.microsoft.com/microsoft-365/enterprise/ipv6-support?view=o365-worldwide https://learn.microsoft.com/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide https://learn.microsoft.com/powershell/module/exchange/disable-ipv6foraccepteddomain?view=exchange-ps |
| 2024-10-11 | MC Summary | IPv6 will be enabled for Exchange Online Accepted Domains starting October 16, 2024, allowing for enhanced security and performance. Organizations should update allow-lists and consider opting out if necessary. Details and preparation steps are provided in the message. | IPv6 will be enabled for Exchange Online Accepted Domains starting October 16, 2024, to meet local regulations and enhance security. Organizations should update allow-lists and consider IP version matching for email connectors. Opt-out options and management commands are available if needed. |
| 2024-09-27 | MC Messages | Updated September 19, 2024: We have updated the content. Thank you for your patience.
Starting October 16, 2024, we're gradually enabling IPv6 for all customer Accepted Domains that use Exchange Online for inbound mail. Microsoft is modernizing Exchange Online so our customers can easily meet their local regulations as well as benefit from the enhanced security and performance offered by IPv6. More information on IPv6 support for Microsoft 365 services can be found at: IPv6 support in Microsoft 365 services [When this will happen:] October 16, 2024 (previously October 1, 2024) | Updated September 26, 2024: We have updated the content. Thank you for your patience.
Starting October 16, 2024, we're gradually enabling IPv6 for all customer Accepted Domains that use Exchange Online for inbound mail. Microsoft is modernizing Exchange Online so our customers can easily meet their local regulations as well as benefit from the enhanced security and performance offered by IPv6. More information on IPv6 support for Microsoft 365 services can be found at: IPv6 support in Microsoft 365 services [When this will happen:] October 16, 2024 (previously October 1, 2024) |
| 2024-09-27 | MC Last Updated | 09/20/2024 02:22:37 | 2024-09-27T02:05:38Z |
| 2024-09-27 | MC prepare | To take advantage of IPv6 connectivity, please make sure that you and your partner's update network allow-lists to allow Exchange Online IPv6 endpoints in the same way it allow-lists IPv4.
The Exchange Online IPv6 endpoints can be found here: Microsoft 365 URLs and IP address ranges. To opt a domain out of inbound IPv6 so traffic flowing to the domain remains IPv4-only, please use Disable-IPv6ForAcceptedDomain -Domain for each domain you want to opt out of IPv6 (Disable-IPv6ForAcceptedDomain (ExchangePowerShell) | Microsoft Learn). IPv6 enablement may impact the source IP type used by Senders when connecting to Exchange Online, as the source and destination IP versions must match. For any IP Address-based Inbound connectors in Exchange Online that are referencing IPv4 addresses, you need to either: Keep the sending server as IPv4. Coordinate with the Sender so the Sender keeps connecting to your domain(s) via IPv4 or Opt your domain(s) out of IPv6 Change the IP based connector to certificate domain based connector. This applies to both OnPremises type (From: Your organization's email server, To: Office 365) and Partner Type connectors (From: Partner organization, To: Office 365). You can manage IPv6 for your Exchange Online Accepted Domains using the commands Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain. Currently, you can check the status of your Accepted Domains with the Get-IPv6StatusForAcceptedDomain command. While some customers have already enabled IPv6, most will see it as disabled until October 16th. After October 16, once IPv6 is enabled for your tenant, if you haven't explicitly set the IPv6 status for your Accepted Domains, the Get-IPv6StatusForAcceptedDomain command will reflect the new default behavior (enabled). IMPORTANT: To ensure your preferred settings are applied, please use the Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain commands before October 16th, after which IPv6 will be enabled by default if you haven't explicitly set it. https://learn.microsoft.com/microsoft-365/enterprise/ipv6-support?view=o365-worldwide https://learn.microsoft.com/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide https://learn.microsoft.com/powershell/module/exchange/disable-ipv6foraccepteddomain?view=exchange-ps | To take advantage of IPv6 connectivity, please make sure that you and your partner's update network allow-lists to allow Exchange Online IPv6 endpoints in the same way it allow-lists IPv4.
The Exchange Online IPv6 endpoints can be found here: Microsoft 365 URLs and IP address ranges. To opt a domain out of inbound IPv6 so traffic flowing to the domain remains IPv4-only, please use Disable-IPv6ForAcceptedDomain -Domain for each domain you want to opt out of IPv6 (Disable-IPv6ForAcceptedDomain (ExchangePowerShell) | Microsoft Learn). IPv6 enablement may impact the source IP type used by Senders when connecting to Exchange Online, as the source and destination IP versions must match. For any IP Address-based Inbound connectors in Exchange Online that are referencing IPv4 addresses, you need to either: Keep the sending server as IPv4. Coordinate with the Sender so the Sender keeps connecting to your domain(s) via IPv4 or Opt your domain(s) out of IPv6 Change the IP based connector to certificate domain based connector. This applies to both OnPremises type (From: Your organization's email server, To: Office 365) and Partner Type connectors (From: Partner organization, To: Office 365). Update: If you are using any Exchange Transport Rules or Data Loss Prevention policies which rely on the SenderIPRanges predicate, you need to opt out all your domains from IPv6. You can manage IPv6 for your Exchange Online Accepted Domains using the commands Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain. Currently, you can check the status of your Accepted Domains with the Get-IPv6StatusForAcceptedDomain command. While some customers have already enabled IPv6, most will see it as disabled until October 16th. After October 16, once IPv6 is enabled for your tenant, if you haven't explicitly set the IPv6 status for your Accepted Domains, the Get-IPv6StatusForAcceptedDomain command will reflect the new default behavior (enabled). IMPORTANT: To ensure your preferred settings are applied, please use the Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain commands before October 16th, after which IPv6 will be enabled by default if you haven't explicitly set it. https://learn.microsoft.com/microsoft-365/enterprise/ipv6-support?view=o365-worldwide https://learn.microsoft.com/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide https://learn.microsoft.com/powershell/module/exchange/disable-ipv6foraccepteddomain?view=exchange-ps |
| 2024-09-27 | MC Summary | IPv6 will be enabled for Exchange Online Accepted Domains starting October 16, 2024, allowing compliance with local regulations and improved security. Organizations should update allow-lists and consider IP connectivity impacts. Opt-out instructions and more information are provided. | IPv6 will be enabled for Exchange Online Accepted Domains starting October 16, 2024, allowing for enhanced security and performance. Organizations should update allow-lists and consider opting out if necessary. Details and preparation steps are provided in the message. |
| 2024-09-20 | MC Messages | Updated September 17, 2024: We have updated the timing of this change and provided additional information to prepare for the change. Thank you for your patience.
Starting October 16, 2024, we're gradually enabling IPv6 for all customer Accepted Domains that use Exchange Online for inbound mail. Microsoft is modernizing Exchange Online so our customers can easily meet their local regulations as well as benefit from the enhanced security and performance offered by IPv6. More information on IPv6 support for Microsoft 365 services can be found at: IPv6 support in Microsoft 365 services [When this will happen:] October 16, 2024 (previously October 1, 2024) | Updated September 19, 2024: We have updated the content. Thank you for your patience.
Starting October 16, 2024, we're gradually enabling IPv6 for all customer Accepted Domains that use Exchange Online for inbound mail. Microsoft is modernizing Exchange Online so our customers can easily meet their local regulations as well as benefit from the enhanced security and performance offered by IPv6. More information on IPv6 support for Microsoft 365 services can be found at: IPv6 support in Microsoft 365 services [When this will happen:] October 16, 2024 (previously October 1, 2024) |
| 2024-09-20 | MC Last Updated | 09/17/2024 22:33:26 | 2024-09-20T02:22:37Z |
| 2024-09-20 | MC prepare | To take advantage of IPv6 connectivity, please make sure that you and your partner's update network allow-lists to allow Exchange Online IPv6 endpoints in the same way it allow-lists IPv4.
The Exchange Online IPv6 endpoints can be found here: Microsoft 365 URLs and IP address ranges. To opt a domain out of inbound IPv6 so traffic flowing to the domain remains IPv4-only, please use Disable-IPv6ForAcceptedDomain -Domain for each domain you want to opt out of IPv6 (Disable-IPv6ForAcceptedDomain (ExchangePowerShell) | Microsoft Learn). IPv6 enablement may impact the source IP type used by Senders when connecting to Exchange Online, as the source and destination IP versions must match. For any IP Address-based Inbound connectors in Exchange Online that are referencing IPv4 addresses, you need to either: Keep the sending server as IPv4. Coordinate with the Sender so the Sender keeps connecting to your domain(s) via IPv4 or Opt your domain(s) out of IPv6 Change the IP based connector to certificate domain based connector. This applies to both OnPremises type (From: Your organization's email server, To: Office 365) and Partner Type connectors (From: Partner organization, To: Office 365). You can manage IPv6 for your Exchange Online Accepted Domains using the commands Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain. Currently, you can check the status of your Accepted Domains with the Get-IPv6StatusForAcceptedDomain command. While some customers have already enabled IPv6, most will see it as disabled until October 16th. After October 16, once IPv6 is enabled for your tenant, if you haven't explicitly set the IPv6 status for your Accepted Domains, the Get-IPv6StatusForAcceptedDomain command will reflect the new default behavior (enabled). IMPORTANT: To ensure your preferred settings are applied, please use the Enable-IPv6StatusForAcceptedDomain or Disable-IPv6StatusForAcceptedDomain commands before October 16th, after which IPv6 will be enabled by default if you haven't explicitly set it. https://learn.microsoft.com/microsoft-365/enterprise/ipv6-support?view=o365-worldwide https://learn.microsoft.com/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide https://learn.microsoft.com/powershell/module/exchange/disable-ipv6foraccepteddomain?view=exchange-ps | To take advantage of IPv6 connectivity, please make sure that you and your partner's update network allow-lists to allow Exchange Online IPv6 endpoints in the same way it allow-lists IPv4.
The Exchange Online IPv6 endpoints can be found here: Microsoft 365 URLs and IP address ranges. To opt a domain out of inbound IPv6 so traffic flowing to the domain remains IPv4-only, please use Disable-IPv6ForAcceptedDomain -Domain for each domain you want to opt out of IPv6 (Disable-IPv6ForAcceptedDomain (ExchangePowerShell) | Microsoft Learn). IPv6 enablement may impact the source IP type used by Senders when connecting to Exchange Online, as the source and destination IP versions must match. For any IP Address-based Inbound connectors in Exchange Online that are referencing IPv4 addresses, you need to either: Keep the sending server as IPv4. Coordinate with the Sender so the Sender keeps connecting to your domain(s) via IPv4 or Opt your domain(s) out of IPv6 Change the IP based connector to certificate domain based connector. This applies to both OnPremises type (From: Your organization's email server, To: Office 365) and Partner Type connectors (From: Partner organization, To: Office 365). You can manage IPv6 for your Exchange Online Accepted Domains using the commands Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain. Currently, you can check the status of your Accepted Domains with the Get-IPv6StatusForAcceptedDomain command. While some customers have already enabled IPv6, most will see it as disabled until October 16th. After October 16, once IPv6 is enabled for your tenant, if you haven't explicitly set the IPv6 status for your Accepted Domains, the Get-IPv6StatusForAcceptedDomain command will reflect the new default behavior (enabled). IMPORTANT: To ensure your preferred settings are applied, please use the Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain commands before October 16th, after which IPv6 will be enabled by default if you haven't explicitly set it. https://learn.microsoft.com/microsoft-365/enterprise/ipv6-support?view=o365-worldwide https://learn.microsoft.com/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide https://learn.microsoft.com/powershell/module/exchange/disable-ipv6foraccepteddomain?view=exchange-ps |
| 2024-09-18 | MC prepare | To take advantage of IPv6 connectivity, please make sure that your network allow-lists allow Exchange Online IPv6 endpoints in the same way it allow-lists IPv4.
The Exchange Online IPv6 endpoints can be found here: Microsoft 365 URLs and IP address ranges. We understand customers have unique situations and may require their own timeline for IPv6 enablement. For customers who need to remain IPv4-Only, we will update this post in September with details on how to opt-out of IPv6 for your Accepted Domains. With this change, please note that traffic moved to IPv6 will have more stringent authentication requirements, as described here Support for anonymous inbound email over IPv6 If you expect this change to cause any issues for your organization, please reach out via your regular support channels. https://aka.ms/m365endpoints https://learn.microsoft.com/defender-office-365/mail-flow-about#support-for-anonymous-inbound-email-over-ipv6 https://learn.microsoft.com/microsoft-365/enterprise/ipv6-support?view=o365-worldwide | To take advantage of IPv6 connectivity, please make sure that you and your partner's update network allow-lists to allow Exchange Online IPv6 endpoints in the same way it allow-lists IPv4.
The Exchange Online IPv6 endpoints can be found here: Microsoft 365 URLs and IP address ranges. To opt a domain out of inbound IPv6 so traffic flowing to the domain remains IPv4-only, please use Disable-IPv6ForAcceptedDomain -Domain for each domain you want to opt out of IPv6 (Disable-IPv6ForAcceptedDomain (ExchangePowerShell) | Microsoft Learn). IPv6 enablement may impact the source IP type used by Senders when connecting to Exchange Online, as the source and destination IP versions must match. For any IP Address-based Inbound connectors in Exchange Online that are referencing IPv4 addresses, you need to either: Keep the sending server as IPv4. Coordinate with the Sender so the Sender keeps connecting to your domain(s) via IPv4 or Opt your domain(s) out of IPv6 Change the IP based connector to certificate domain based connector. This applies to both OnPremises type (From: Your organization's email server, To: Office 365) and Partner Type connectors (From: Partner organization, To: Office 365). You can manage IPv6 for your Exchange Online Accepted Domains using the commands Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain. Currently, you can check the status of your Accepted Domains with the Get-IPv6StatusForAcceptedDomain command. While some customers have already enabled IPv6, most will see it as disabled until October 16th. After October 16, once IPv6 is enabled for your tenant, if you haven't explicitly set the IPv6 status for your Accepted Domains, the Get-IPv6StatusForAcceptedDomain command will reflect the new default behavior (enabled). IMPORTANT: To ensure your preferred settings are applied, please use the Enable-IPv6StatusForAcceptedDomain or Disable-IPv6StatusForAcceptedDomain commands before October 16th, after which IPv6 will be enabled by default if you haven't explicitly set it. https://learn.microsoft.com/microsoft-365/enterprise/ipv6-support?view=o365-worldwide https://learn.microsoft.com/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide https://learn.microsoft.com/powershell/module/exchange/disable-ipv6foraccepteddomain?view=exchange-ps |
| 2024-09-18 | MC Summary | Starting October 1, 2024, Microsoft will enable IPv6 for Accepted Domains in Exchange Online, enhancing security and performance. Organizations should update network allow-lists to include Exchange Online IPv6 endpoints. Opt-out details will be provided in September for those needing to remain IPv4-Only. | IPv6 will be enabled for Exchange Online Accepted Domains starting October 16, 2024, allowing compliance with local regulations and improved security. Organizations should update allow-lists and consider IP connectivity impacts. Opt-out instructions and more information are provided. |
| 2024-09-18 | MC Last Updated | 07/26/2024 00:50:53 | 2024-09-17T22:33:26Z |
| 2024-09-18 | MC Messages | Starting October 1st, 2024, we're gradually enabling IPv6 for all customer Accepted Domains that use Exchange Online for inbound mail. Microsoft is modernizing Exchange Online so our customers can easily meet their local regulations as well as benefit from the enhanced security and performance offered by IPv6.
More information on IPv6 support for Microsoft 365 services can be found at: IPv6 support in Microsoft 365 services [When this will happen:] October 1, 2024 | Updated September 17, 2024: We have updated the timing of this change and provided additional information to prepare for the change. Thank you for your patience.
Starting October 16, 2024, we're gradually enabling IPv6 for all customer Accepted Domains that use Exchange Online for inbound mail. Microsoft is modernizing Exchange Online so our customers can easily meet their local regulations as well as benefit from the enhanced security and performance offered by IPv6. More information on IPv6 support for Microsoft 365 services can be found at: IPv6 support in Microsoft 365 services [When this will happen:] October 16, 2024 (previously October 1, 2024) |
| 2024-09-18 | MC Title | Announcing IPv6 Enablement for Accepted Domains | (Updated) Announcing IPv6 Enablement for Accepted Domains |
| 2024-09-18 | MC MessageTagNames | Feature update, User impact, Admin impact | Updated message, Feature update, User impact, Admin impact |
Last updated 3 weeks ago
