Skip to content

Updating cdn documentation. #13791

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: public
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions microsoft-365/enterprise/office-365-cdn-quickstart.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,8 @@ The Office 365 CDN supports:
- **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.

You can choose public origins for your organization [Choose public origins](use-microsoft-365-cdn-with-spo.md).
>[!NOTE]
>By default, no customer content is added to public CDN unless explicitly specified. Microsoft will never enable anonymous access to any customer contents.

## 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.
Expand Down
7 changes: 5 additions & 2 deletions microsoft-365/enterprise/use-microsoft-365-cdn-with-spo.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ Once you're done with setup, you can [Manage the Office 365 CDN](use-microsoft-3
- Configuring CDN policies
- If necessary, disabling the CDN

Finally, see [Using your CDN assets](use-microsoft-365-cdn-with-spo.md#using-your-cdn-assets) to learn about accessing your CDN assets from both public and private origins.
Finally, see [Using your CDN assets](use-microsoft-365-cdn-with-spo.md#using-your-cdn-assets) to learn about accessing your CDN assets from public origins.

See [Troubleshooting the Office 365 CDN](use-microsoft-365-cdn-with-spo.md#CDNTroubleshooting) for guidance on resolving common issues.

Expand Down Expand Up @@ -428,6 +428,9 @@ Set-PnPTenantCdnEnabled -CdnType Public -Enable $true

For more information about this cmdlet, see [Set-PnPTenantCdnEnabled](https://pnp.github.io/powershell/cmdlets/Set-PnPTenantCdnEnabled.html).

> [!NOTE]
> Management of the configuraion of Private CDN is deprecated. Public CDN is the recommended approach for full management capabilities. Items that are already added to private CDN are still retrievable, but its configuration cannot be modified.

<a name="Office365CDNforPnPPoshFileType"> </a>

### Change the list of file types to include in the Office 365 CDN (Optional)
Expand Down Expand Up @@ -787,7 +790,7 @@ m365 spo cdn set --type Public --enabled false

Now that you enabled the CDN and configured origins and policies, you can begin using your CDN assets.

This section helps you understand how to use CDN URLs in your SharePoint pages and content so that SharePoint redirects requests for assets in both public and private origins to the CDN.
This section helps you understand how to use CDN URLs in your SharePoint pages and content so that SharePoint redirects requests for assets in public origins to the CDN.

- [Updating links to CDN assets](use-microsoft-365-cdn-with-spo.md#updating-links-to-cdn-assets)
- [Using assets in public origins](use-microsoft-365-cdn-with-spo.md#using-assets-in-public-origins)
Expand Down