Forum Discussion
Feedback on Office 365 IP/URL Web Services Preview
We have previously asked Microsoft premier support team in japan to confirm the new Web service, however we couldn’t receive support because the new Web service is in preview now.
They informed us that this page is possible to accept questions or feedback.
Therefore, we got to post some questions here.
First of all, will you stop publishing the current HTML, XML, and RSS format of data as scheduled on October 2nd?
If the current HTML, XML, and RSS format of data will be stopped as scheduled on October 2nd, it is difficult to respond to the new Web service currently because the published information is so insufficient.
Could you please answer below questions?
--------------------------------------------------
1. About service area
--------------------------------------------------
a. XML file (Current method)
<Available over Internet & ExpressRoute circuits>:
shared services | authentication | Office Online | Exchange Online | Exchange Online Protection | Skype for Business Online | Microsoft Teams | SharePoint Online and OneDrive | OneNote | Dynamics CRM IP | Dynamics CRM URI | Power BI
<Available over Internet circuits only>:
Office 365 Video and Microsoft Stream | Yammer | Sway | Planner | Office Clients | Microsoft Intune | Microsoft PowerApps | Microsoft Flow
b. Web service (New method)
The service area that this is part of : Common, Exchange, SharePoint, Skype.
*Question
There is something we would like to confirm.
For example:
-The new Web service “Exchange” contains “Exchange Online, Exchange Online Protection” of current item.
-The new Web service “Skype” contains “Skype for Business Online” of current item.
-The new Web service “SharePoint” contains “SharePoint Online and OneDrive” of current item.
-The new Web service “Common” contains the other items.
How the each service area of the current item will be applied in the service area of the new item, please inform us in more detail.
--------------------------------------------------
2. About the effect of three categories (Optimize, Allow, and Default)
--------------------------------------------------
We are aware that the current XML File and the tables with Office 365 URLs and IP address range in the HTML page will be replaced with the new Web service.
a. XML file
https://support.content.office.net/en-us/static/O365IPAddresses.xml
b. Web service
https://endpoints.office.com/endpoints/worldwide?clientrequestid=b10c5ed1-bad1-445f-b386-b919946339a...
This URL of new Web service is posted in [Web service] - [For the data on the Office 365 URLs and IP address ranges page for firewalls and proxy servers] section.
https://support.office.com/en-us/article/99cab9d4-ef59-4207-9f2b-3728eb46bf9a
There are three categories (Optimize, Allow, and Default) in a downloaded file from the above new Web service URL.
However, we can’t find three categories (Optimize, Allow, and Default) in the current XML file.
*Question
At present, we have allowed all the Office 365 URLs and IP address range provided by the current XML file to the firewalls/proxy servers.
When the current XML file will be replaced with the new Web service in future, do we need to change something in allow the setting of firewalls/proxy servers about three categories (Optimize, Allow, and Default)?
Otherwise, in the same way as now, would it be OK for firewalls/proxy servers to allow all Office 365 URLs and IP address range in the new Web service without regard for three categories (Optimize, Allow, and Default)?
Kyounghwan Lee here are answers to your questions:
>> First of all, will you stop publishing the current HTML, XML, and RSS format of
>> data as scheduled on October 2nd?
Yes.
>> How the each service area of the current item will be applied in the service area
>> of the new item, please inform us in more detail.
This reduction in the service areas is intended to simplify network connectivity work required for Office 365. It also avoids support issues related to unpublished dependencies between services.
Old XML Product New JSON ServiceArea
WAC Common
Sway Common
Planner Common
ProPlus Common
Ex-Fed Deprecated
Yammer Common
Teams Skype
OfficeiPad Common
OfficeMobile Common
RCA Deprecated
OneNote Common
EXO Exchange
SPO SharePoint
Office365Video Common
LYO Skype
Identity Common
CRLs Common
o365 Common
EOP Exchange
>> When the current XML file will be replaced with the new Web service in future,
>> do we need to change something in allow the setting of firewalls/proxy servers
>> about three categories (Optimize, Allow, and Default)?
The only change that you are required to do is to start taking changes from the web services instead of from the XML/RSS published data. All future changes to Office 365 network endpoints will be advertised through the web services.
>> Otherwise, in the same way as now, would it be OK for firewalls/proxy servers
>> to allow all Office 365 URLs and IP address range in the new Web service without
>> regard for three categories (Optimize, Allow, and Default)?
The new categories make firewall, proxy server, and other network perimeter device configuration simpler. In particular, the default category can be directed to the default Internet egress location with any other employee web browser traffic. However, you can simply permit connectivity and bypass for all Office 365 network traffic and disregard the categories. Please review details of the new categories at http://aka.ms/pnc
Regards,
Paul
- Kyounghwan LeeJul 31, 2018Copper Contributor
I really appreciate all the advice you gave me on how to update new Web service.
>>The only change that you are required to do is to start taking changes from the >>web services instead of from the XML/RSS published data.
Simply, I understand that the XML/ RSS data that has been published so far will be switched to new Web service.
I understand that I can permit connectivity and bypass for all Office 365 network traffic and disregard the categories (Optimize, Allow, and Default).
As for the factors you pointed out, we will certainly correspond them when we update the next new Web service.
Regards,
Kyounghwan Lee