Announcing: Office 365 endpoint categories and Office 365 IP Address and URL web service

Copper Contributor

Nov 05, 2018

I don't understand this either: the effective date rarely appears to be in the future and when it is, it's only by 1 day. Most of the time, it's in the past.

When the old RSS feed was still being updated, there were examples where the effective date on the feed was 30 days in the future but at the same time, according to the REST service it was the same day/in the past.

For example - RSS feed - note publish date is 01 Aug, effective date was 1st September:

<item>
<description>
Adding a URL; 1/[Effective 9/1/2018. Required: Office 365 Video and Microsoft Stream. ExpressRoute: No. amsglob0cdnstream12.azureedge.net]. Notes: Adding URL.
</description>
<guid>05dfb303-bfd5-4029-be71-07efa204cfc4</guid>
<link>http://aka.ms/o365endpoints</link>
<pubDate>Wed, 01 Aug 2018 08:52:55 GMT</pubDate>
<title>Office 365 Video and Microsoft Stream</title>
</item>

This appears to be the JSON equivalent from the REST service:

  {
    "id": 11,
    "endpointSetId": 42,
    "disposition": "Change",
    "version": "2018073000",
    "add": {
      "effectiveDate": "20180726",
      "urls": [
        "amsglob0cdnstream12.azureedge.net"
      ]
    }
  },

For 'add' entries we're currently ignoring effective date and just assuming it's publish date + 30days because we have nothing else to go on that makes any sense.

Regards

Steve

Blog Post

Announcing: Office 365 endpoint categories and Office 365 IP Address and URL web service