Forum Discussion
Migrating to the new web services based publishing for Office 365 IP Addresses and URLs
I'm trying to understand the meaning of the following which is:
The ip set "13.70.151.216/32" (along with several others) appears in the results of the https://endpoints.office.com/changes/worldwide/0000000000?clientrequestid=b10c5ed1-bad1-445f-b386-b919946339a7 multiple times as a "remove ips" "remove" disposition type of update associated with a "urls" of "*.dc.trouter.io" in one update and associated with a "urls" of [*.skype.com","*.teams.microsoft.com", and "teams.microsoft.com"] in a second "remove ips" "remove" disposition type of update and in a 3rd "remove ips" type of "change" disposition update but associated with no urls . In all three updates, the "previous expressroute" state is listed as "true" but the "current expressroute" state is "false".
This is compared to the endpoints list (https://endpoints.office.com/endpoints/Worldwide?ClientRequestId=b10c5ed1-bad1-445f-b386-b919946339a7 ) where i still see that ip listed multiple times in the endpoints list with ExpressRoute=true and i also see it listed in the following places (https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges?redirectSourcePath=%252fen-gb%252farticle%252fOffice-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2#bkmk_sfb_ip ) , https://support.office.com/en-us/o365ip/rss and https://support.content.office.net/en-us/static/O365IPAddresses.xml .
Do the updates in the changes results mean that the ip set is 1) no longer serviced by Express Route and 2) no longer associated with the urls mentioned but still used by o365 services but not via ER and are the sites i listed that seem to still indicate that the ip set is both express routeable and associated with the urls mentioned just not in sync because they are being deprecated ?
Can you please clarify the intent of the updates mentioned (just search for 13.70.151.216/32 to see all the ones i was referencing) ?
Thanks
Hi John Tullo,
The /changes output faithfully describes each and every change in the output of the /endpoints web method.
We're working on adding an additional field to the /changes output that will identify the severity of each change. Note that this IP Address is still part of Office 365 and none of these changes should be applied to a firewall as a removal. We would have some kind of change severity that indicates duplicate removal only.
Here's more detail on those three change sets for IP 13.70.151.216.
Change Set ID 141 - this is deleting endpoint set 23 entirely. It was removed as it was a duplicate of another endpoint set ID 25. The other endpoint set is still published.
Change Set ID 152 - this is a change to endpoint set 69. We changed it to ExpressRoute not supported and removed all of the IP Addresses. This endpoint set is telemetry and is in the Default category which we recommend directing to a default Internet egress proxy server. This is an operation that does not require IP Addresses.
Change Set ID 167 - this is deleting endpoint set 24 entirely. It was also removed as a duplicate. This one is a duplicate of endpoint set ID 12.
Regards,
Paul
- John TulloSep 18, 2018Copper ContributorThanks Paul. That clears up my confusion.