This still doesn't rule out Powershell. In fact, it is exactly why I use Powershell: automate tasks so that regardless of size and growth my workload stays the same after implementation.moordoom wrote: ↑Jan 27, 2022 10:13 pm Yea, this PowerShell works fine if you have a couple of these, those of us that have several hundred, not so much.
5b did change it to a Warning instead of a Fail, but is it backing it up or passing over it?
I am on 5d now with the 5d cumulative applied and get the 'warnings' now and a new Error for some now -
1/27/2022 3:01:31 PM :: Failed to process site: https://mytenant-my.sharepoint.com/pers ... n-name_com. Cannot contact site at the specified URL https://mytenant-my.sharepoint.com/pers ... n-name_com. Access to this Web site has been blocked. Please contact the administrator to resolve this problem.
Does anyone know of a tool to cleanup these 'orphaned' sites?
Create a Powershell-script that
1) Searches for sites where LockState is "NoAccess" (if I remember correctly, can probably find it here on the forum)
2) Exclude sites from your job(s) / change LockState to Unlock or ReadOnly / delete site like 4thandBailey showed you.
Run said script as a scheduled task before your scheduled job, Bob's your uncle.