Forum Discussion
MicrosoftMigrating to the new web services based publishing for Office 365 IP Addresses and URLs
MicrosoftHi Deleted, yes, when you get the /changes data, you should also get the /endpoints data. You can lookup those other fields in /endpoints using the EndpointSetId attribute. Are you asking this question because you are retrieving the /changes data in some way that makes linking to an endpoint set difficult? What script language or client are you using?
Paul
Paul,
I agree with Bryan, It would be useful to have the serviceArea in the changes web method as if the disposition is "remove" then the endpointset may not exist in the current endpoint list.
eg. change id 141 has endpointset 23 which does not exist in the endpoint list. There are also others - change ids (146, 151, 162, 167). - Suppose it depends on when the endpoint set is removed but would be useful to know what serviceArea the change was when looking back in the history.
Paul,
Just to confirm how to determine future updates.
If current version is 2018083000. For future updates. eg new url will be added on 01/10/2018, will entries appear in the changes web method for 2018093000 sometime before 01/10?
- PaulAndrew
Hi Ian Williams, we create the version number from the date when public publishing is done. The effectiveDate attribute in the changes web method for add operations is the date that the engineering team who owns the endpoint said that the service was or will be live.
Can you share a scenario where the serviceArea is needed in the changes web method? If you have the previous version, then this isn't necessary as you can just look it up. If you don't have the previous version, then the changes are of no use.
Regards,
Paul