You have until October 2018 to plan for this change. Again, hopefully some PowerShell enthusiasts will solve this problem for the community. Without the RSS feed, we need to create our own script or tool to poll the REST web service, detect changes, and send our preferred notification. RSS is also simple to consume in a feed reader, convert to an email notification, or send to a channel in Teams. Whether the feed was used for automation, or merely as a notification, it is handy to have something provided by Microsoft to let us know when changes have occurred. Hopefully some PowerShell enthusiasts will develop a script to generate a user friendly document from the data, and share that with the community. It’s the type of document that people can sit together and discuss as they go through it. The support document is the only human-readable source of this data that Microsoft provides. Unfortunately, we lose two good things in the process.
![sonicwall virtual office url sonicwall virtual office url](https://duo.com/assets/img/documentation/sonicwallsra/portal-settings-host_2x.png)
The REST web service should provide a better and more flexible experience for vendors and anybody who writes their own custom scripts to consume the data. Overall, this change makes sense from the perspective of automation. The sample script polls for changes since the last time you ran the script, saving results in a temp file to detect when changes have occurred. Microsoft provides a sample script in PowerShell and Python on this page (scroll down near the bottom) which you can use as a starter. PowerShell cmdlets such as Invoke-WebRequest, Invoke-RestMethod, and ConvertFrom-Json are useful for that purpose. You can of course write your own PowerShell scripts, or use another coding language, to make use of the JSON data. So it’s expected that those vendors will simply adjust to the new JSON format. Many vendors have this capability for the existing XML file, and can automated updates using the RSS feed as well. It’s intended for consumption by automation processes, or by firewall and network management tools that can ingest the data and automatically configure the appropriate rules. But that isn’t the purpose of the JSON feed.
![sonicwall virtual office url sonicwall virtual office url](https://www.godaddy.com/garage/wp-content/uploads/2015/05/dell-vpn-portal-page-settings.jpg)
The JSON data is, naturally, quite unreadable. The CSV file is the most human readable, but is not as friendly as the current support document. The REST web service returns data in either CSV or JSON format. A list of the latest changes for each instance.
#Sonicwall virtual office url full#
A full list of the current configuration recommendations for each instance.
#Sonicwall virtual office url update#
![sonicwall virtual office url sonicwall virtual office url](https://www.wikidsystems.com/static/media/uploads/images/support/wikid-support-center/how-to/sonicwall1.jpg)
Customers who do not limit outbound client connectivity have little need for this information. Previously, and until October 2018, Microsoft has maintained a support document listing the URLs, IP address ranges, and ports that are required or optional for Office 365 connectivity.