Azure DevOps Services Transitioning to New IP Addresses

As noted in the Azure DevOps Blog, we continue transitioning to new IP addresses over the coming weeks. Customers with protected networks must update their firewall allowlists to ensure uninterrupted access to Azure DevOps Services. Refer to the blog for connectivity guidance: [Update to Azure DevOps Allowed IP addresses](https://devblogs.microsoft.com/devops/update-to-ado-allowed-ip-addresses/)

As previously shared in the Azure DevOps Blog ([Update to Azure DevOps Allowed IP addresses](https://devblogs.microsoft.com/devops/update-to-ado-allowed-ip-addresses/)), we have initiated the process of transitioning to new IP Addresses.

This change will slowly rollout over the next few weeks. To ensure uninterrupted access to Azure DevOps Services, customers using protected networks who have not done so already, must update their firewall allowlists with the new set of IP addresses.

If you are experiencing connectivity issues, please refer to the guidance previously published on the Azure DevOps Blog:
- [Server Name Indication (SNI) Now Mandatory for Azure DevOps Services](https://devblogs.microsoft.com/devops/sni-mandatory-for-azdo-services/)
- [Update to Azure DevOps Allowed IP addresses](https://devblogs.microsoft.com/devops/update-to-ado-allowed-ip-addresses/)