Forum Discussion
Office 365 public CDN feature does not appears
Hello everyone!
VesaJuvonen can you help me with that please?
I was trying to enable the CDN in Office 365 following this post
http://dev.office.com/blogs/office-365-public-cdn-developer-preview-release
But I was unable to get the following features
PublicCdnEnabled : False
PublicCdnAllowedFileTypes : CSS,EOT,GIF,ICO,JPEG,JPG,JS,MAP,PNG,SVG,TTF,WOFF
PublicCdnOrigins : {}
CDN feature is available world wide and even though it would not be for some reason enabled in your tenant, that would not be visible from the PS CmdLet outputs - You'd still see the properties as long as you are running right version of the PowerShell cmdlet's.
So - this indicates more that you are using older version of the SharePoint Online Cmdlets which do not have the latest tenant APIs available. You can fix this simply by removing older version of the PowerShell cmdlets and then reinstall them from https://www.microsoft.com/en-us/download/details.aspx?id=35588.
There's few edge scenarios which could potentially cause challenges for you as well, which depends on your installation model. If you have for example installed tenant assembly using SharePoint Online SDK msi and have not refreshed that - it could cause challenges - or if you have manually registered older version of tenant assembly to GAC.
So - what I'd do is to remove existing SharePoint Online PowerShell and msi packages - then install latest version of the SPO PowerShell. That will install needed assemblies for PowerShell and no seperate msi's are needed.
3 Replies
- VesaJuvonen
Microsoft
CDN feature is available world wide and even though it would not be for some reason enabled in your tenant, that would not be visible from the PS CmdLet outputs - You'd still see the properties as long as you are running right version of the PowerShell cmdlet's.
So - this indicates more that you are using older version of the SharePoint Online Cmdlets which do not have the latest tenant APIs available. You can fix this simply by removing older version of the PowerShell cmdlets and then reinstall them from https://www.microsoft.com/en-us/download/details.aspx?id=35588.
There's few edge scenarios which could potentially cause challenges for you as well, which depends on your installation model. If you have for example installed tenant assembly using SharePoint Online SDK msi and have not refreshed that - it could cause challenges - or if you have manually registered older version of tenant assembly to GAC.
So - what I'd do is to remove existing SharePoint Online PowerShell and msi packages - then install latest version of the SPO PowerShell. That will install needed assemblies for PowerShell and no seperate msi's are needed.
- Thanks Vesa, It works
