-
Notifications
You must be signed in to change notification settings - Fork 37
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
SharePoint Online Site Policy #203
Comments
Have a look at https://github.com/PowershellScripts/SharePointOnline-ScriptSamples/tree/develop/Site%20Management/Site%20Policy/RemovePolicy I wrote that one for you It is still in the testing phase, so please let me know what you think and how it is working for you |
@PowershellScripts Thanks for this.. but I am getting error with this script. |
That's good feedback. I'm guessing it comes from the fact that you published the content type from the content type hub. Let me try to simulate that and I will see what can be done. |
@Abhijeet1719 What do you get when you try |
@PowershellScripts I tried below command but same error... |
@PowershellScripts -------Script--------- #Reading CSV foreach ($row in $CSVData)
} #Apply Site Policy for a Site collection
} |
@PowershellScripts HI Do u have update for me? Thanks.... |
@PowershellScripts
I have created site policy in content type hub and trying to apply site policy to site collection using powershell but its not applying. I am able to activate at site collection level but not able to apply it. I tried it with another approach i.e applied it manually and then remove it and after that I tried with powershell it worked...bt I want to applied it without manually activating and de activating.
Can anyone please suggest?
Also, Our tenancy has multiple site collections and webs, and all have a Site Policy applied. I've now been asked to remove the policy from all sites. Doing it manually is not an option.
Is there a CSOM or PnP command or snippet I can execute via PowerShell that will allow me to remove a Site Policy from a site?
The text was updated successfully, but these errors were encountered: