Merge pull request #27736 from MicrosoftDocs/main

Published main to live, Wednesday 10:30 AM PT, 02/19

Author: padmagit77

copilot/release-notes.md

@@ -35,7 +35,8 @@ CDNs help keep Microsoft 365 fast and reliable for end users. Cloud services lik
 
 A CDN is a geographically distributed network consisting of proxy and file servers in datacenters connected by high-speed backbone networks. CDNs are used to reduce latency and load times for a specified set of files and objects in a web site or service. A CDN may have many thousands of endpoints for optimal servicing of incoming requests from any location.
 
-CDNs are commonly used to provide faster downloads of generic content for a web site or service such as JavaScript files, icons and images, and can also provide private access to user content such as files in SharePoint document libraries, streaming media files, and custom code.
+CDNs are commonly used to provide faster downloads of generic content for a web site or service such as JavaScript files, icons and images.
+
 
 CDNs are used by most enterprise cloud services. Cloud services like Microsoft 365 have millions of customers downloading a mix of proprietary content (such as emails) and generic content (such as icons) at one time. It's more efficient to put images everyone uses, like icons, as close to the user's computer as possible. It isn't practical for every cloud service to build CDN datacenters that store this generic content in every metropolitan area, or even in every major Internet hub around the world, so some of these CDNs are shared.
 
@@ -56,15 +57,13 @@ The built-in Microsoft 365 Content Delivery Network (CDN) allows Microsoft 365 a
 > [!NOTE]
 > The Microsoft 365 CDN is only available to tenants in the **Production** (worldwide) cloud. Tenants in the US Government, China and Germany clouds do not currently support the Microsoft 365 CDN.
 
-The Microsoft 365 CDN is composed of multiple CDNs that allow you to host static assets in multiple locations, or _origins_, and serve them from global high-speed networks. Depending on the kind of content you want to host in the Microsoft 365 CDN, you can add **public** origins, **private** origins or both.
+The Microsoft 365 CDN is composed of multiple CDNs that allow you to host static assets in multiple locations, or _origins_, and serve them from global high-speed networks. 
 
 ![Microsoft 365 CDN conceptual diagram.](../media/O365-CDN/o365-cdn-flow-transparent.svg "Microsoft 365 CDN conceptual diagram")
 
 Content in **public** origins within the Microsoft 365 CDN is accessible anonymously, and can be accessed by anyone who has URLs to hosted assets. Because access to content in public origins is anonymous, you should only use them to cache non-sensitive generic content such as JavaScript files, scripts, icons and images. The Microsoft 365 CDN is used by default for downloading generic resource assets like the Microsoft 365 client applications from a public origin.
 
-**Private** origins within the Microsoft 365 CDN provide private access to user content such as SharePoint document libraries, sites and proprietary images. Access to content in private origins is secured with dynamically generated tokens so it can only be accessed by users with permissions to the original document library or storage location. Private origins in the Microsoft 365 CDN can only be used for SharePoint content, and you can only access assets through redirection from your SharePoint tenant.
-
-The Microsoft 365 CDN service is included as part of your SharePoint subscription.
+The Microsoft 365 CDN service is included as part of your SharePoint Online subscription.
 
 For more information about how to use the Microsoft 365 CDN, see [Use the Microsoft 365 content delivery network with SharePoint](use-microsoft-365-cdn-with-spo.md).
 
@@ -105,12 +104,8 @@ Regardless of what CDN you configure for your Microsoft 365 tenant, the basic da
 
 1. Your client (a browser or Office client application) requests data from Microsoft 365.
 
-2. Microsoft 365 either returns the data directly to your client or, if the data is part of a set of content hosted by the CDN, redirects your client to the CDN URL.
-
-    a. If the data is already cached in a _public_ origin, your client downloads the data directly from the nearest CDN location to your client.
-
-    b. If the data is already cached in a _private_ origin, the CDN service checks your Microsoft 365 user account's permissions on the origin. If you have permissions, SharePoint dynamically generates a custom URL composed of the path to the asset in the CDN and two access tokens, and returns the custom URL to your client. Your client then downloads the data directly from the nearest CDN location to your client using the custom URL.
-
+2. Microsoft 365 either returns the data directly to your client or, if the data is part of a set of content hosted by the CDN, redirects your client to the CDN URL. If the data is already cached in a _public_ origin, your client downloads the data directly from the nearest CDN location to your client.
+    
 3. If the data isn't cached at the CDN, the CDN node requests the data from Microsoft 365 and then caches the data for time after your client downloads the data.
 
 The CDN figures out the closest datacenter to the user's browser and, using redirection, downloads the requested data from there. CDN redirection is quick, and can save users a lot of download time.
@@ -127,7 +122,7 @@ The CDNs in use by Microsoft 365 are always subject to change and in many cases
 
 |CDN  |Company  |Usage  |Link  |
 |---------|---------|---------|---------|
-|Microsoft 365 CDN     |Microsoft Azure         |Generic assets in public origins, SharePoint user content in private origins         |[Microsoft Azure CDN](/azure/frontdoor/)         |
+|Microsoft 365 CDN     |Microsoft Azure         |Generic assets in public origins         |[Microsoft Azure CDN](/azure/frontdoor/)         |
 |Azure CDN     |Microsoft         |Custom code, SharePoint Framework solutions         |[Microsoft Azure CDN](/azure/frontdoor/)         |
 |Microsoft Ajax CDN (read only)     |Microsoft         |Common libraries for Ajax, jQuery, ASP.NET, Bootstrap, Knockout.js etc.         |[Microsoft Ajax CDN](/aspnet/ajax/cdn/overview)         |
 
@@ -164,7 +159,7 @@ For in-depth information about privacy and data protection for Microsoft 365 CDN
 
 ## How can I secure my network with all these 3rd party services?
 
-Using an extensive set of partner services allows Microsoft 365 to scale and meet availability requirements and enhance the user experience when using Microsoft 365. The 3rd party services Microsoft 365 leverages include both certificate revocation lists; such as crl.microsoft.com or sa.symcb.com, and CDNs; such as r3.res.outlook.com. Every CDN FQDN generated by Microsoft 365 is a custom FQDN for Microsoft 365. If you're sent to a FQDN at the request of Microsoft 365, you can be assured that the CDN provider controls the FQDN and the underlying content at that location.
+Using an extensive set of partner services allows Microsoft 365 to scale and meet availability requirements and enhance the user experience when using Microsoft 365. The 3rd party services Microsoft 365 leverages include both certificate revocation lists; such as crl.microsoft.com or sa.symcb.com, and CDNs; such as r3.res.outlook.com. Every CDN FQDN generated by Microsoft 365 is a custom FQDN for Microsoft 365. If you're sent to an FQDN at the request of Microsoft 365, you can be assured that the CDN provider controls the FQDN and the underlying content at that location.
 
 For customers that want to segregate requests destined for a Microsoft 365 datacenter from requests that are destined for a 3rd party, we've written up guidance on [Managing Microsoft 365 endpoints](https://support.office.com/article/99cab9d4-ef59-4207-9f2b-3728eb46bf9a).
 

microsoft-365/enterprise/content-delivery-networks.md

@@ -26,15 +26,12 @@ description: "Office 365 Content Delivery Network (CDN) Quickstart"
 
 # Office 365 Content Delivery Network (CDN) Quickstart
 
-You can use the built-in **Office 365 Content Delivery Network (CDN)** to host static assets (images, JavaScript, Stylesheets, WOFF files) to provide better performance for your SharePoint pages. The Office 365 CDN improves performance by caching static assets closer to the browsers requesting them, which helps to speed up downloads and reduce latency. Also, the Office 365 CDN uses the HTTP/2 protocol for improved compression and HTTP pipelining. The Office 365 CDN service is included as part of your SharePoint subscription.
+You can use the built-in **Office 365 Content Delivery Network (CDN)** to host static assets (images, JavaScript, Style sheets, WOFF files) to provide better performance for your SharePoint pages. The Office 365 CDN improves performance by caching static assets closer to the browsers requesting them, which helps to speed up downloads and reduce latency. Also, the Office 365 CDN uses the HTTP/2 protocol for improved compression and HTTP pipelining. The Office 365 CDN service is included as part of your SharePoint subscription.
 
 For more detailed information, see [Use the Office 365 Content Delivery Network (CDN) with SharePoint](use-microsoft-365-cdn-with-spo.md).
 
-> [!CAUTION]
-> As images are now automatically managed in a SharePoint service-managed Private CDN, the manually configured Private CDN is in the process of being deprecated. This means that customers no longer need to configure private CDN. The recommended practice remains unchanged as images will be hosted via the service-managed Private CDN automatically and Public CDN will continue to be available for all other file types, like CSS and JS.  Any customers using Private CDN for file types other than images, will need to move those files into Public CDN. Public CDN is recommended for these file types, to enhance performance.
-
 >[!NOTE]
->The Office 365 CDN is only available to tenants in the production (worldwide) cloud. Tenants in the US Government, China and Germany clouds do not currently support the Office 365 CDN.
+>The Office 365 CDN is only available to tenants in the production (worldwide) cloud. Tenants in the US Government, China and Germany clouds don't currently support the Office 365 CDN.
 
 ## Use the Page Diagnostics for SharePoint tool to identify items not in CDN
 
@@ -47,22 +44,20 @@ When you run the Page Diagnostics for SharePoint tool on a SharePoint in Microso
 ![Page diagnostics.](../media/page-diagnostics-for-spo/pagediag-results-general.PNG)
 
 >[!NOTE]
->The Page Diagnostics tool only works for SharePoint in Microsoft 365, and cannot be used on a SharePoint system page.
+>The Page Diagnostics tool only works for SharePoint in Microsoft 365, and can't be used on a SharePoint system page.
 
 ## CDN Overview
 
 The Office 365 CDN is designed to optimize performance for users by distributing frequently accessed objects like images and JavaScript files over a high-speed global network, reducing page load time and providing access to hosted objects as close as possible to the user. The CDN fetches your assets from a location called an _origin_. An origin can be a SharePoint site, document library, or folder that is accessible by a URL.
 
-The Office 365 CDN is separated into two basic types:
-
-- **Public CDN** is designed to be used for JS (JavaScript), CSS (StyleSheets), Web Font File (WOFF, WOFF2) and nonproprietary images like company logos.
-- **Private CDN** is designed to be used for images (PNG, JPG, JPEG, etc.).
+The Office 365 CDN supports:
 
-You can choose to have both public or private origins for your organization. Most organizations will choose to implement a combination of the two. Both public and private options provide similar performance gains, but each has unique attributes and advantages. For more information about public and private CDN origins, see [Choose whether each origin should be public or private](use-microsoft-365-cdn-with-spo.md#CDNOriginChoosePublicPrivate).
+- **Public CDN**, which is designed to be used for JS (JavaScript), CSS (Style Sheets), Web Font File (WOFF, WOFF2) and non-proprietary images like company logos.
 
-## How to enable Public and Private CDN with the default configuration
+You can choose public origins for your organization [Choose public origins](use-microsoft-365-cdn-with-spo.md).
 
-Before you make changes to the tenant CDN settings, you should verify that it meets compliance, security, and privacy policies of your organization.
+## How to enable Public CDN with the default configuration
+Before you make changes to the tenant CDN settings, you should verify that it meets compliance, security and privacy policies of your organization.
 
 For more detailed configuration settings, or if you have already enabled CDN and want to add additional locations (origins), see the section [Set up and configure the Office 365 CDN by using the SharePoint Management Shell](use-microsoft-365-cdn-with-spo.md#set-up-and-configure-the-office-365-cdn-by-using-the-sharepoint-online-management-shell)
 
@@ -72,16 +67,12 @@ Connect to your tenant using the SharePoint Management Shell:
 Connect-SPOService -Url https://<YourTenantName>-admin.sharepoint.com
 ```
 
-To enable your organization to use both public and private origins with the default configuration, type the following command:
+To enable your organization to use  public origin with the default configuration, type the following command:
 
 ```PowerShell
-Set-SPOTenantCdnEnabled -CdnType Both -Enable $true
+Set-SPOTenantCdnEnabled -CdnType Public -Enable $true
 ```
 
-Output of these cmdlets should look like the following:
-
-![Output of Set-SPOTenantCdnEnabled.](../media/O365-CDN/o365-cdn-enable-output.png)
-
 ## See also
 
 [Use the Page Diagnostics tool for SharePoint](./page-diagnostics-for-spo.md)