Last Updated: August 8, 2022
ISSUE
The week of June 13, 2022, an update was deployed to an internal service management tool that introduced an unplanned change to the IP address range that negatively impacted a limited number of Microsoft 365 customers. The negative impact to affected customers was a loss of network connectivity to some Microsoft 365 applications.
This update should have had no visible impact on customers or any user experience. However, when this networking-related update was committed, a required command was not executed and, as a result, an unintended change to the IP address ranges used by Microsoft 365 was introduced.
Customers who had configured their firewalls to disallow IP addresses and ranges introduced in this Office update experienced connectivity issues.
STATUS: FIXED
A fix has been deployed to correct the IP ranges (52.108.0.0/14) associated with the *.officeapps.live.com endpoint in the DF, SIP and US datacenters. This won't impact the mitigation steps that customers have put in place.
You can revert to your original configuration, but test to confirm.
On Monday, July 25, 2022, work was started to correct the IP ranges in WW datacenters with a completion date of July 26, 2022.
The following IP addresses are no longer used as a workaround. Please update the allow list, as required, for your environment.
|
IP Addresses that no longer need MSAIfExistsAccess |
|
20.213.119.23 |
|
20.206.125.32 |
|
40.69.152.149 |
|
137.135.67.105 |
|
23.102.122.93 |
|
20.111.54.6 |
|
20.219.197.157 |
|
20.222.106.13 |
|
20.89.234.40 |
|
20.214.169.104 |
|
20.223.136.135 |
|
20.225.216.27 |
|
20.212.224.194 |
|
20.108.14.61 |
|
20.126.65.153 |
|
20.237.179.133 |
|
20.236.58.81 |
|
52.109.112.118 |
|
52.109.108.53 |
|
52.109.68.46 |
|
52.109.8.40 |
|
52.109.12.232 |
|
52.109.6.45 |
|
52.109.56.46 |
|
52.109.132.63 |
|
52.109.52.77 |
|
52.109.44.8 |
|
52.109.76.69 |
|
52.109.20.76 |
|
52.109.124.127 |
|
52.109.28.64 |
|
52.109.24.54 |
|
52.109.2.1 |
|
52.109.88.178 |
Our systems have multiple layers of safeguards in place to ensure that the Microsoft 365 services we operate for our customers are reliable and secure. To ensure this issue does not recur, we are reviewing, and will continue to review, automated test cases to guard against this type of issue in the future.
More Resources
Ask the experts
Connect with experts, discuss the latest news, updates, and best practices, and read our blog.
Get help in the community
Ask a question and find solutions from Support Agents, MVPs, Engineers, and other Office users.
Suggest a new feature
We love reading your suggestions and feedback! Share your thoughts. We're listening.
