One of my Client has a mysterious error on there tenant since sometime in July.

No one in the entire tenant can edit any pages on any of the sites in SharePoint, not even if we create new sites. It’s not a permission issue and it happens to Users and administrators alike. 

The Edit button is clickable, but as soon as you click on it, it says that you can’t edit the page. 

We have found a workaround, where we can go into the site pages library and in Versioning settings, we specify force checkout when editing. With this setting on it works to edit pages again. I could apply this settings to alla sites in the tenant rather easy with PowerShell, but when a user creates a new site, which they do, this setting won’t be applied there. So I rather have a better fix for this.

When I click the edit page I get a network request to startCoAuth. The Collaboration on SharePoint pages has started rolling out in July so my guess is that this is something that could have gone wrong in this tenant when rolling out this feature. 

Anyone else seen this problem?

​One of my Client has a mysterious error on there tenant since sometime in July. No one in the entire tenant can edit any pages on any of the sites in SharePoint, not even if we create new sites. It’s not a permission issue and it happens to Users and administrators alike.  The Edit button is clickable, but as soon as you click on it, it says that you can’t edit the page.   We have found a workaround, where we can go into the site pages library and in Versioning settings, we specify force checkout when editing. With this setting on it works to edit pages again. I could apply this settings to alla sites in the tenant rather easy with PowerShell, but when a user creates a new site, which they do, this setting won’t be applied there. So I rather have a better fix for this. When I click the edit page I get a network request to startCoAuth. The Collaboration on SharePoint pages has started rolling out in July so my guess is that this is something that could have gone wrong in this tenant when rolling out this feature.  Anyone else seen this problem?     Read More

​