Forum Discussion
Remove a Sharepoint Site on Preservation Hold
- Oct 16, 2016
UPDATE
I was able to fix the problem by creating a new policy with the same sharepoint sites of the original policy, and then removing the original policy. This seems to indicate that the problem lie with the policy itself.
It's very possible that I still have other policies that would be affected by this problem, but with a relatively easy fix I'm not too worried about it. If I run in to the situation again I'll be able to deal with it.
Also, a big shout out to the Compliance and Security support team, who so far have been great to deal with. Thanks!
It does take some time, did you check the DistributionStatus of the policy?
Looking deeper, it appears that the site will not actually remove from the policy. I have tried removing via the Admin Center and PowerShell, and each change results in a redistribution of the policy, but does not remove the site. Another bug?
- VasilMichevOct 12, 2016MVP
It does look like a bug, let me try to repro...
- VasilMichevOct 12, 2016MVP
Seems to be working fine for me:
[16:02:13][O365]# Get-CRetentionCompliancePolicy "test spo" | fl SharePointLocation SharePointLocation : {Pesho} [16:03:50][O365]# Get-CRetentionCompliancePolicy "test spo" | Set-CRetentionCompliancePolicy -RemoveSharePointLocation "https://xxxx-my.sharepoint.com/personal/pesho_xxx_xxx" [16:03:58][O365]# Get-CRetentionCompliancePolicy "test spo" | fl SharePointLocation SharePointLocation : {}
And I can confirm that the same shows after the distribution completed.
P.S. clearing out the last site should enable preservation for *all* sites instead if I remember correctly, but for the sake of testing this I guess it's good enough. Still, if you have a single site left to remove in your case, you might want to add another one first.
- Matt McNabbOct 12, 2016Iron Contributor
I'm not seeing the same result at all. After running Set-CRetentionCompliancePolicy -RemoveSharepointLocation, I can see that the desired site is still in the collection.
Our policies in general contain 100 sites, as this is the maximum allowed per policy. Once we reach that upper limit, a new policy is created and new personal sites are added to this. I am only attempting to remove one site from a policy that contains 100 sites, and it simply won't remove and no errors are returned.
I've put in a service request to see if this is a bug in our infrastructure. Thanks!