Forum Discussion
Migrating to the new web services based publishing for Office 365 IP Addresses and URLs
Thanks Paul
Lets say i want to get FQDN's and IP's for a single application say "YAMMER".
Documentation states - "notes - For optional endpoints, this text describes Office 365 functionality that will be missing if IP addresses or URLs in this endpoint set cannot be accessed at the network layer. Omitted if blank."
Old XML had a product called "YAMMER" and FQDN's and IP's specific to YAMMER.
now for the achieving same effect Can i rely on notes field part of endpoints and extract FQDN's and IP's for "YAMMER" ?
And Can i assume the notes will be updated and maintained just like IPS's and FQDN's ?
jaffer.jobs jaffer.jobs wrote:
Lets say i want to get FQDN's and IP's for a single application say "YAMMER".
Documentation states - "notes - For optional endpoints, this text describes Office 365 functionality that will be missing if IP addresses or URLs in this endpoint set cannot be accessed at the network layer. Omitted if blank."
Old XML had a product called "YAMMER" and FQDN's and IP's specific to YAMMER.
now for the achieving same effect Can i rely on notes field part of endpoints and extract FQDN's and IP's for "YAMMER" ?
And Can i assume the notes will be updated and maintained just like IPS's and FQDN's ?
We only support selective blocking of Office 365 network traffic by the ServiceArea attribute in the web service output. The previous listed products in the XML file are not supported for selective network blocking. You can read above in this article about how the old products are mapped to ServiceAreas. Separately, the notes field is provided for any Required: false endpoint sets to identify what Office 365 functionality would be missing if this endpoint set is blocked. The notes field doesn't follow any specific schema, doesn't group endpoint sets, and doesn't have an update or maintenance policy.
Regards,
Paul