We can use a network, local, or HTTP path for the UpdatePath Office 365 proplus. UNC path is perfectly fine for desktop users but incase of  laptop users who are not in office network UNC path not accessible. So planning to test with local CDN(http site) so that if users in office or client location update not impact.

For laptop users we can host a local CDN network, which is accessible from outside of  office network as well. Can someone suggest how to configure CDN(content delivery network) for our client systems. Similar like Microsoft has for publicly for all.

We can use a network, local, or HTTP path for the UpdatePath Office 365 proplus. UNC path is perfectly fine for desktop users but incase of  laptop users who are not in office network UNC path not accessible. So planning to test with local CDN(http site) so that if users in office or client location update not impact.

For laptop users we can host a local CDN network, which is accessible from outside of  office network as well. Can someone suggest how to configure CDN(content delivery network) for our client systems. Similar like Microsoft has for publicly for all.

• Moved by Roope Astala - MSFTMicrosoft employee Friday, June 19, 2015 2:03 PM This question is related Office 365, not Azure ML
• Merged by George.Zhao CHNMicrosoft contingent staff, Moderator 1 hour 36 minutes ago same topic

We can use a network, local, or HTTP path for the UpdatePath Office 365 proplus. UNC path is perfectly fine for desktop users but incase of  laptop users who are not in office network UNC path not accessible. So planning to test with local CDN(http site) so that if users in office or client location update not impact.

For laptop users we can host a local CDN network, which is accessible from outside of  office network as well. Can someone suggest how to configure CDN(content delivery network) for our client systems. Similar like Microsoft has for publicly for all.

• Moved by Roope Astala - MSFTMicrosoft employee Friday, June 19, 2015 2:03 PM This question is related Office 365, not Azure ML
• Merged by George.Zhao CHNMicrosoft contingent staff, Moderator Tuesday, June 23, 2015 5:52 AM same topic

Hi Harry,

Based on your description, please post your issue to Office 365 forum so that you can get more professional information and help about Office 365:

https://community.office365.com/en-us/f/

The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.

Hope its helpful.

Regards,

George Zhao
TechNet Community Support

You can use Group Policy to configure the Update Source Location:
http://blogs.technet.com/b/odsupport/archive/2014/04/28/new-group-policies-introduced-with-the-april-2014-update-of-office-2013-click-to-run.aspx

e.g.: for computers located in the corporate network, use this to configure the update source as your on-premises repository, and, for computers which are located outside your corporate network, leave the defaults in place/configure for MSFT CDN.

Or perhaps another alternative might be this: if you have content-caching appliances/services available within your corporate network/DMZ/edge, those content-caches could serve the MSFT CDN content efficiently to your corporate computers (in this case, all of your computers could be configured as default for MSFT CDN. This would mean that laptops which may come-and-go could "automatically" reach the most effective/efficient "copy" of the MSFT content)

Another alternative might be to consider some "clever" internal DNS/proxy logic, again this would allow you to leave the computers configured for MSFT CDN default and allow your network/DNS/proxy to resolve "internal" requests to your on-premises repository.

[just a few thoughts...]