Hub site architecture
Design around business units, not individual teams. Hub sites give a navigable architecture with rolled-up navigation, search and branding across associated sites. Limit hub sites to a handful — too many hubs recreate the sprawl you are trying to avoid.
Sharing controls
Set tenant-level external sharing to "Existing guests" or "New and existing guests" rather than "Anyone" links for most tenants. Use site-level policies to tighten further on sensitive sites. Expire external sharing links after a defined window so forgotten access does not linger.
- Tenant default: existing guests only, anonymous links time-boxed
- Site-level: stricter on HR, Finance and legal sites
- Review sharing reports monthly for stale external access
Lifecycle and storage governance
Inactive sites accumulate cost and risk. Use Microsoft 365 group expiration policies to auto-renew or expire Teams and group-connected sites. Monitor OneDrive storage and set quotas that match business need, not the default.
Lessons learned
- Plan hub architecture around business units, not projects
- Time-box anonymous sharing links by default
- Enable group expiration to retire inactive sites
- Train site owners — governance is a people problem, not just a config one
Written by
Jamshed Alam
Global MSP & IT Infrastructure Consultant with 20 years across Exchange, Microsoft 365, Azure, security and automation. Available for project and contract work worldwide.