Troubleshooting: Anonymous access on a public SharePoint site collection failing

Ah, everyone’s favorite, classic topic! Debugging SharePoint On-Premises configuration issues is the best thing since sliced bread, right? This post is about allowing/enabling Anonymous Access to a site collection – a simple configuration, that “simply works” like once every ten times you try it.


A lot of different ways to hit your head on this one. In any case, your on-premises SharePoint doesn’t allow anonymous access to a site where you are trying to allow it. Most typically, they’ll just encounter 401 error when accessing the site, or they might be missing some of the content or styles, resulting in partially broken site.


Usually incorrect configuration or non-published resources. Multiple reasons can cause this, though, I’ll describe some of them below with the solutions.


A lot of things to check – let’s go through all of the most typical issues here! Continue reading

Don’t remove the root site of your classic SharePoint Site Collection!

A quick heads-up – if you remove the root site of your classic SharePoint Site Collection, that site’s going to be troublesome to deal with. Whereas you can always restore a normal site from the site collection recycle bin, the root site you can’t. You actually can’t access the recycle bin after removing the root site, nor can you make magic happen with PowerShell commandlets anymore.

Site Collection Recycle Bin – where you could access it, if you still had your site!

The Recycle Bin would be located at a url like this: https://<yoursite>/_layouts/15/AdminRecycleBin.aspx, but after the site is removed, it won’t be there. 

If you actually just wanted to get rid of your site collection by removing the site (see below), you’re out of luck again. Even that didn’t happen, as you now still have the site collection, just without any sites in it. You can’t even reuse the url for anything, as it’s still reserved for your site collection! Continue reading