Jul 23 2017 06:51 PM
As of yesterday, I noticed that new communication sites I created had NoScript enabled by default. This was not the case a few weeks ago when I wrote this post:
Furthermore, I was not able to disable NoScript on new communication sites by running this cmdlet, the way I would disable NoScript on a modern team site:
Set-SPOSite https://djsp.sharepoint.com/sites/comm -DenyAddAndCustomizePages 0
I confirmed this cmdlet still works for newly created modern team sites, but on communication sites I get the following error:
Set-SPOSite : SPOTenantSiteCollectionProvider::SetSiteProperties - Site https://djsp.sharepoint.com/sites/comm not found in Grid, but TAPS_Sites_UseSharePoint flight in ONReverting to GM-based set-sposite (old) behavior for now
At line:1 char:1
+ Set-SPOSite https://djsp.sharepoint.com/sites/comm -DenyAddAndCustomi ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Set-SPOSite], ServerException
+ FullyQualifiedErrorId : Microsoft.SharePoint.Client.ServerException,Microsoft.Online.SharePoint.PowerShell.SetSite
Thanks in advance for any insight you can provide!
Jul 26 2017 04:28 AM
I got the same issue when running this command: https://techcommunity.microsoft.com/t5/SharePoint/Error-when-running-Set-SPOSite-for-new-Community-s...
In general Set-SPOSite doesn't seem to work with the new Communication site.
In another thread on the Tech Community I saw an Microsoft employee was investigating this behaviour:
https://techcommunity.microsoft.com/t5/SharePoint/Anonymous-Sharing-not-working-with-Communication-s...
Jul 26 2017 04:36 AM
Jul 31 2017 12:36 AM
I am also keeping an eye on those threads. So I will post an update if I come across a solution.
Aug 01 2017 10:59 AM
Aug 03 2017 12:48 AM
Thanks Danny, good to hear they have created a fix.
Aug 02 2018 06:46 AM
Still having this issue with Communication sites, did some of you saw it rolled out?
Aug 02 2018 08:01 AM
@Sebastien Gagne, just tried the Set-SPOSite cmdlet with version 16.0.7723.0 of SharePoint Online Management Shell and I am not getting an error anymore when using the -DenyAddAndCustomizePages parameter. So it should be fixed now.
Have you tried downloading the latest SharePoint PowerShell module?
https://www.microsoft.com/en-us/download/details.aspx?id=35588
Aug 02 2018 10:34 AM