SharePoint Online: Complete Administration Guide
🏗️ Site Types: Team Sites vs Communication Sites
| Aspect | Team Site | Communication Site |
|---|---|---|
| Purpose | Collaboration within a group or team | Broadcasting content to a wide audience |
| Backed by | Microsoft 365 Group (Entra ID) | No M365 Group — SharePoint-only |
| Default permissions | Owners, Members, Visitors via M365 Group | Site owner manages permissions directly |
| Typical use | Project teams, departments, Microsoft Teams | Company intranet, HR portal, announcements |
| Created by | Users (if allowed) or Teams creation | Site admins or authorised users |
💡 Key Point
Every Microsoft Team automatically creates a SharePoint team site behind it. Channel files are stored in that site’s document library — one folder per standard channel. Deleting a Team also deletes its SharePoint site (after a soft-delete period).
🔗 Hub Sites
💡 What Hub Sites Do
A hub site is a SharePoint site registered as the root of a collection of associated sites. Hub association lets you roll up news and search results across all associated sites, apply consistent navigation and branding centrally, and surface content from child sites in the hub home page. Only SharePoint Administrators can register a site as a hub. Sites can be associated with (and disassociated from) a hub without losing their own settings. A site can only be associated with one hub at a time, but hubs themselves can be nested by associating a hub site to a parent hub.
🚫 Controlling External Sharing
The Four Sharing Levels
| Level | What It Allows |
|---|---|
| Anyone | Shareable links that work without sign-in (anonymous). Most permissive. |
| New and existing guests | External users must authenticate (sign in or verify with a one-time passcode) |
| Existing guests only | Only guests already in your Entra ID directory can be shared with |
| Only people in your organisation | No external sharing at all. Most restrictive. |
⚠️ Critical Rule — Tenant vs Site Level
Site-level sharing can only be equal to or more restrictive than the tenant level — never more permissive. If the tenant is set to “New and existing guests”, a site cannot be opened to “Anyone”. To restrict a specific site, set its level lower than the tenant level.
Connect-SPOService -Url https://yourtenant-admin.sharepoint.com # Block external sharing on a single site Set-SPOSite -Identity https://yourtenant.sharepoint.com/sites/Finance -SharingCapability Disabled # Allow only authenticated guests at tenant level Set-SPOTenant -SharingCapability ExternalUserSharingOnly # Restrict to specific external domains (allow list) Set-SPOTenant -SharingDomainRestrictionMode AllowList -SharingAllowedDomainList "partner1.com partner2.com" # Block specific domains (block list) Set-SPOTenant -SharingDomainRestrictionMode BlockList -SharingBlockedDomainList "competitor.com"
👥 SharePoint Permission Model
💡 Default Permission Groups
- Owners — Full Control. Can manage settings, permissions, and all content.
- Members — Edit. Can add, edit, and delete content in the site.
- Visitors — Read. Can view content only, cannot edit.
Broken Permission Inheritance
⚠️ The Most Common Permission Trap
By default, all lists, libraries, folders, and items inherit permissions from the site. If inheritance is broken on a library or folder (via “Stop Inheriting Permissions”), that item gets its own independent permission set. A user may have site-level access but be blocked at a library where inheritance is broken — or vice versa. This is the most common cause of unexpected SharePoint access issues and the first thing to check when permissions look correct at the site level but access is still denied.
Connect-PnPOnline -Url https://yourtenant.sharepoint.com/sites/Finance -Interactive # Check a specific user's permissions on a site Get-PnPUserEffectivePermissions -Site https://yourtenant.sharepoint.com/sites/Finance -User user@domain.com # Check if a list/library has broken permission inheritance Get-PnPList -Identity "Documents" | Get-PnPProperty -Property HasUniqueRoleAssignments
💻 Restricting Access from Unmanaged Devices
💡 Conditional Access Integration
SharePoint Online integrates with Entra ID Conditional Access to restrict access from devices that are not Entra ID joined or Intune-compliant. In the SharePoint admin center → Policies → Access control → Unmanaged devices, you can choose: Allow full access, Allow limited, web-only access (no download/sync/print), or Block access entirely from unmanaged devices. This creates a corresponding Entra ID Conditional Access policy automatically. This is a common scenario in interviews about protecting corporate data on personal devices.
🔄 Site Lifecycle Management
💡 Microsoft 365 Group Expiry
Group-connected team sites (and their backing Teams) can be governed with an Entra ID group expiry policy. When configured, M365 group owners receive expiry notifications and must renew the group — or it (and its associated SharePoint site, Team, mailbox, and Planner) is automatically deleted after a grace period. Administrators can also set retention policies on SharePoint in Microsoft Purview to ensure content is preserved even after site deletion.
⚠️ Deleted Site Recovery
- Deleted sites go to the SharePoint Deleted Sites container for 93 days
- Restore via SharePoint admin center → Deleted sites, or via PowerShell:
Restore-SPODeletedSite - After 93 days, permanent deletion — no recovery without third-party backup
🛠️ Troubleshooting SharePoint Access Issues
Use Check Permissions
Site Settings → Site permissions → Check Permissions. Enter the user’s name to see exactly what access they have and through which group, role, or sharing link. This is always the first step.
Check Group Membership
For group-connected sites, verify the user is a Member or Owner of the backing Microsoft 365 Group in Entra ID. Group changes can take a few minutes to propagate to SharePoint.
Look for Broken Inheritance
Navigate to the specific library, folder, or file the user can’t access. Check Library/List Settings → Permissions → whether the item inherits from the parent or has unique permissions.
Rule Out Policies
Conditional access (unmanaged device restriction), sensitivity label-based access blocks, and site-level sharing settings can deny access even when permissions are correctly assigned. Check SharePoint admin center → Access control and the site’s sharing settings.
💡 Best Practices & Recommendations
- Manage permissions through the Microsoft 365 Group — avoid item-level permission inheritance breaks wherever possible, as they become unmanageable at scale
- Set default sharing links to “People with existing access” or “Specific people” rather than “Anyone” at the tenant level
- Use hub sites to unify navigation, branding, and search across related department sites instead of deeply nested subsite structures
- Enable Purview retention policies on SharePoint before you need them — data recovery options depend entirely on what’s been configured in advance
- Use domain allow/block lists for partner collaboration rather than fully opening external sharing tenant-wide
- Review guest access quarterly using Entra ID access reviews to remove stale external users
🎓 Common Interview Questions
Set-SPOSite -Identity <SiteURL> -SharingCapability Disabled. The site setting overrides the tenant setting for that site only, and can be more restrictive but never more permissive than the tenant level.Set-SPOTenant -SharingDomainRestrictionMode AllowList -SharingAllowedDomainList "partner1.com partner2.com".📚 References & Further Reading
- 🔗 External sharing overview in SharePoint and OneDrive — Microsoft Learn
- 🔗 Planning your SharePoint hub sites — Microsoft Learn
- 🔗 Set up a SharePoint hub site — Microsoft Learn
- 🔗 Control access from unmanaged devices — Microsoft Learn
