Skip to content
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

Unable to disable NoScript on communication sites #744

1 of 4 tasks
dannyjessee opened this issue Jul 26, 2017 · 3 comments
1 of 4 tasks

Unable to disable NoScript on communication sites #744

dannyjessee opened this issue Jul 26, 2017 · 3 comments


Copy link

dannyjessee commented Jul 26, 2017


  • Question
  • Typo
  • Bug
  • Additional article idea

Expected or Desired Behavior

Earlier this month (last verified on July 1), when new communication sites were created they had NoScript disabled by default (DenyAddAndCustomizePages = Disabled). As of July 22 (and still right now), not only are newly created communication sites NoScript sites (DenyAddAndCustomizePages = Enabled), but I am unable to disable NoScript the way I am still able to successfully disable it for newly created modern team sites. See error details in Observed Behavior section below.

Observed Behavior

When calling Set-SPOSite [Site URL] -DenyAddAndCustomizePages 0, I get the following error on communication sites (NOTE: this still works as expected to disable NoScript on new modern team sites):

PS C:\WINDOWS\system32> Set-SPOSite -DenyAddAndCustomizePages 0
Set-SPOSite : SPOTenantSiteCollectionProvider::SetSiteProperties - Site 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 -DenyAddAndCustomi ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-SPOSite], ServerException
    + FullyQualifiedErrorId : Microsoft.SharePoint.Client.ServerException,Microsoft.Online.SharePoint.PowerShell.SetSi

Steps to Reproduce

Create a new communication site and attempt to disable NoScript using the PowerShell cmdlet above in the SharePoint Online Management Shell. Note that this cmdlet still successfully disables NoScript for a new modern team site.

Copy link
Contributor Author

A contributor on Tech Community pointed out some threads to me where others are having similar issues performing tasks unrelated to what I have posted above, but also using the Set-SPOSite cmdlet on communication sites. It is possible that the issue lies there rather than just the my specific issue:

Error when running Set-SPOSite for new Community site

Anonymous Sharing not working with Communication sites

Copy link

@dannyjessee - thank you for your feedback, a fix has been made so you should be able to use Set-SPOSite on a communications site soon, the fix is currently rolling out.

Copy link

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues

@SharePoint SharePoint locked as resolved and limited conversation to collaborators Jan 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
None yet

No branches or pull requests

3 participants