Office 365 endpoints web service preview detailed changes on 7/6/2018

%3CLINGO-SUB%20id%3D%22lingo-sub-212886%22%20slang%3D%22en-US%22%3EOffice%20365%20endpoints%20web%20service%20preview%20detailed%20changes%20on%207%2F6%2F2018%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-212886%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20first%20released%20the%20Office%20365%20endpoints%20web%20services%20preview%20on%204%2F2%2F2018.%20As%20described%20in%20the%20broader%20post%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fipurlblog%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%2C%20the%20update%20on%207%2F6%2F2018%20has%20the%20following%20changes%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EAdded%20a%20new%20category%20element%20to%20the%20%2Fendpoints%20web%20method%3C%2FLI%3E%0A%3CLI%3EMerged%20the%20DefaultTcpPorts%2C%20AllowTcpPorts%2C%20and%20OptimizeTcpPorts%20elements%20into%20tcpPorts%3C%2FLI%3E%0A%3CLI%3EMerged%20the%20DefaultUdpPorts%2C%20AllowUdpPorts%2C%20and%20OptimizeUdpPorts%20elements%20into%20udpPorts%3C%2FLI%3E%0A%3CLI%3EMerged%20the%20DefaultUrls%2C%20AllowUrls%2C%20and%20OptimizeUrls%20elements%20into%20urls%3C%2FLI%3E%0A%3CLI%3ERenumbered%20the%20endpoint%20sets%20to%20remove%20gaps%20caused%20during%20development%3C%2FLI%3E%0A%3CLI%3EReset%20the%20%2Fchanges%20web%20method%20output%20to%20be%20changes%20since%20June%2030.%20This%20means%20it%20is%20blank%20in%20July%202018%3C%2FLI%3E%0A%3CLI%3EFinalized%20the%20initial%20categories%20for%20each%20endpoint%20set%3C%2FLI%3E%0A%3CLI%3ERemoved%20O365%20from%20service%20instance%20names%20across%20the%20web%20methods%3C%2FLI%3E%0A%3CLI%3ERenamed%20optionalImpact%20element%20to%20notes%20in%20the%20%2Fendpoints%20web%20method%20and%20added%20a%20required%20Boolean%20element%3C%2FLI%3E%0A%3CLI%3EAdded%20a%20NoIPv6%20parameter%20to%20the%20%2Fendpoints%20web%20method%3C%2FLI%3E%0A%3CLI%3EUpdated%20the%20sample%20PowerShell%20and%20Python%20scripts%3C%2FLI%3E%0A%3CLI%3EAdded%20IP%20Address%20ranges%20to%20all%20endpoint%20sets%20instead%20of%20having%20separate%20IP%20Address%20only%20endpoint%20sets.%20This%20means%20that%20IP%20Addresses%20can%20be%20seen%20to%20be%20duplicated%20across%20endpoint%20sets%2C%20but%20they%20are%20always%20covering%20the%20URLs%20in%26nbsp%3Beach%20endpoint%20set.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3ERelease%20timeline%20from%20now%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EWe%20aren%E2%80%99t%20going%20to%20change%20the%20data%20schema%20or%20data%20outside%20of%20change%20control%3C%2FLI%3E%0A%3CLI%3EWe%20are%20already%20using%20the%20new%20web%20services%20for%20some%20Microsoft%20internal%20processes%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EPlease%20start%20developing%20against%20the%20new%20web%20services%20now%3C%2FLI%3E%0A%3CLI%3EWe%20have%20a%20little%20more%20work%20to%20do%20before%20we%20can%20offer%20GA%20level%20support%3C%2FLI%3E%0A%3CLI%3EWe%20will%20provide%20GA%20support%20prior%20to%20the%20current%20XML%20format%20data%20becoming%20unavailable%20on%20October%202%3CSUP%3End%3C%2FSUP%3E%202018%3C%2FLI%3E%0A%3CLI%3EThe%20RSS%20and%20HTML%20format%20outputs%20may%20update%20before%20October%202%3CSUP%3End%3C%2FSUP%3E%2C%202018%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EThe%20user%20guide%20for%20the%20web%20services%20can%20be%20found%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fmanaging-office-365-endpoints-99cab9d4-ef59-4207-9f2b-3728eb46bf9a%23webservice%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%20Please%20also%20read%20about%20the%20new%20endpoint%20categories%20%3CSPAN%3E%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fpnc%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%3C%2FSPAN%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20for%20all%20of%20the%20feedback%20on%20our%20previous%20preview.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Microsoft

We first released the Office 365 endpoints web services preview on 4/2/2018. As described in the broader post here, the update on 7/6/2018 has the following changes:

  • Added a new category element to the /endpoints web method
  • Merged the DefaultTcpPorts, AllowTcpPorts, and OptimizeTcpPorts elements into tcpPorts
  • Merged the DefaultUdpPorts, AllowUdpPorts, and OptimizeUdpPorts elements into udpPorts
  • Merged the DefaultUrls, AllowUrls, and OptimizeUrls elements into urls
  • Renumbered the endpoint sets to remove gaps caused during development
  • Reset the /changes web method output to be changes since June 30. This means it is blank in July 2018
  • Finalized the initial categories for each endpoint set
  • Removed O365 from service instance names across the web methods
  • Renamed optionalImpact element to notes in the /endpoints web method and added a required Boolean element
  • Added a NoIPv6 parameter to the /endpoints web method
  • Updated the sample PowerShell and Python scripts
  • Added IP Address ranges to all endpoint sets instead of having separate IP Address only endpoint sets. This means that IP Addresses can be seen to be duplicated across endpoint sets, but they are always covering the URLs in each endpoint set.

Release timeline from now:

  • We aren’t going to change the data schema or data outside of change control
  • We are already using the new web services for some Microsoft internal processes 
  • Please start developing against the new web services now
  • We have a little more work to do before we can offer GA level support
  • We will provide GA support prior to the current XML format data becoming unavailable on October 2nd 2018
  • The RSS and HTML format outputs may update before October 2nd, 2018

The user guide for the web services can be found here. Please also read about the new endpoint categories here.

 

Thanks for all of the feedback on our previous preview.

0 Replies