SOLVED

Problems in Office 365 Url IP Web services?

Microsoft

According to https://endpoints.office.com/version?clientrequestid=52ef93d7-b835-42bc-a019-e40ffceb6635, the latest version for the worldwide instance is 2022072800. Together with the changes for 2022062900 there should be 50 new IPs, more than 35 Urls added and 21 attributes changed since 2022060100 (see https://endpoints.office.com/version/worldwide?allversions=true&format=rss&clientrequestid=52ef93d7-...).

But in fact the webservice still delivers the same endpoints as the one from beginning of June.

And https://endpoints.office.com/changes/worldwide/0000000000?clientrequestid=52ef93d7-b835-42bc-a019-e4... doesn't show any changes since 2022060100, either.

In the past the information returned by these web services used to be consistent, but currently it is rather confusing.

Can someone please explain what is going on here?

Thank you, Matthias

2 Replies
best response confirmed by Christian Heim (Microsoft)
Solution

Hi @Matthias_Glubrecht

 

What is going on is we have some other network endpoint data which you don't see and it was getting counted. We've changed the behavior from the 2022082800 version so that we will only count the ones you can see and the count should be as expected. This also means we wont bump the version number if there are no endpoint changes that you can see.

 

This issue of the unexpected counting was only in the /version/ API and you can rely on the /endpoint/ and /changes/ APIs for all versions.

 

Hope that helps.

 

Regards,

Paul

 

Hi @Paul Andrew,

thank you for the clarification! And yes, it definitely helps :smile:

Kind regards,

Matthias

 

1 best response

Accepted Solutions
best response confirmed by Christian Heim (Microsoft)
Solution

Hi @Matthias_Glubrecht

 

What is going on is we have some other network endpoint data which you don't see and it was getting counted. We've changed the behavior from the 2022082800 version so that we will only count the ones you can see and the count should be as expected. This also means we wont bump the version number if there are no endpoint changes that you can see.

 

This issue of the unexpected counting was only in the /version/ API and you can rely on the /endpoint/ and /changes/ APIs for all versions.

 

Hope that helps.

 

Regards,

Paul

 

View solution in original post