SharePoint Hub Sites vs Tenant Architecture — Enterprise IA (2026)
Enterprise SharePoint information architecture. 2,000-hub tenant limit, cascading navigation, permission inheritance clarifications, and hub-first vs site-first decision framework.
Last updated July 14, 2026 by Errin O'Connor, Founder & Chief AI Architect, EPC Group
SharePoint hub sites unify navigation, branding, and search across up to 2,000 associated sites per hub (tenants can register up to 2,000 hubs). Hub association is NAV/BRAND/SEARCH only — NOT permissions. Use hub sites when 20+ sites need unified UX; use flat tenant architecture when fewer sites or single-team ownership. Common mistakes: over-hubbing, under-associating, assuming hub permissions cascade, no lifecycle governance. Enterprise pattern: Home site (Viva Connections) → 5-15 top-level hubs → 50-500 associated sites. Full hub IA rollout typically 3-6 months for 500-2,000 site tenants.
Key Facts
- 2026 limits: 2,000 hubs per tenant × 2,000 associated sites per hub
- Hub association ≠ permissions — associated sites keep their own permission model (governance implication: pair with SharePoint Advanced Management / Premium)
- Hub-of-hubs supported (parent hub → child hubs → associated sites) — only ONE level of nesting
- Enterprise pattern: 5-15 top-level hubs mapping to business units/geographies
- Hub nav supports 3 levels of dropdown depth (mega menu style)
- Home site (Viva Connections) is separate from hubs — global nav parent, not a hub itself
- EPC Group has designed hub architecture for 6,500+ SharePoint implementations since 1997
SharePoint Hub Sites vs Tenant Architecture FAQ
What is a SharePoint hub site and how does it work?
A SharePoint hub site is a top-level site that aggregates related communication and team sites into a unified navigation + branding + search experience. Technical mechanics: (1) Any modern SharePoint site (Team, Communication, or root of a hub) can be REGISTERED as a hub via Admin Center or PowerShell. (2) Once registered, other sites can be ASSOCIATED with the hub — up to 2,000 associated sites per hub in 2026 (was 1,000 in 2023, raised twice). (3) Association is a soft link — the associated site inherits the hub's top-navigation bar, theme, logo, and hub-wide search scope. The associated site keeps its own permissions, content, and admin. (4) A single tenant can register up to 2,000 hubs. Total hub-associated site capacity: 2,000 × 2,000 = 4 million associated relationships (though tenant SharePoint capacity caps out at 2 million sites first). Design implication: hub sites are the primary tool for enterprise SharePoint information architecture in 2026.
When should I use hub sites vs a flat tenant architecture?
Use hub sites when: (1) You have 20+ SharePoint sites across the tenant and need consistent branding + navigation across a business unit, geography, or function. (2) You want unified search across a group of related sites without moving content. (3) You need to enforce cascading design (theme, logo, top nav) across a set of sites managed by different owners. (4) Cross-site rollup web parts (news, events, highlighted content) need to aggregate content from associated sites into a hub landing page. Use FLAT tenant architecture when: (1) You have fewer than 20 SharePoint sites total. (2) All sites are managed by a single team and share consistent branding via a tenant-wide design already. (3) You have strict permission-isolation requirements (though hub-associated sites keep their own permissions, some enterprises prefer flat for audit clarity). (4) You expect fewer than 2 associated sites per proposed hub — the overhead of hub registration + management exceeds the benefit. Rule of thumb: 500+ site enterprises always need hubs; 100-500 site enterprises usually benefit; <100 sites often work flat.
What is the maximum number of hub sites and associated sites in 2026?
Current 2026 limits (increased from 2023 baselines): (1) 2,000 registered hub sites per tenant (was 100 in early 2020, 2,000 by end of 2023). (2) 2,000 associated sites per hub (was 1,000 in 2023). (3) Total tenant SharePoint site count cap: 2 million sites per tenant (unchanged). (4) A single site can be associated with only ONE hub at a time — no multi-hub association. (5) A hub can be part of a HUB-OF-HUBS hierarchy (parent hub → child hubs → associated sites) but only ONE level of nesting is supported. Practical implication: for tenants with 500-5,000 SharePoint sites, hub architecture is well within limits. For tenants pushing 20,000+ sites (rare), hub design requires careful modeling to stay within the 2,000-associated-sites-per-hub cap. Enterprise SharePoint IA typically results in 5-50 hubs at organizational scale.
How does hub navigation interact with site-level navigation and mega menus?
Four navigation layers stack: (1) Global navigation (SharePoint app bar) — tenant-wide, appears on every SharePoint page, managed via SharePoint Admin Center. (2) Hub navigation — appears BELOW global nav on every site associated with the hub, managed by the hub site owner. Supports mega menu style with 3 levels of dropdown depth. Rendered as the "hub bar" across the top of associated sites. (3) Site-level navigation — the site's own left nav (Team sites) or top nav (Communication sites), managed by the site owner. (4) Page-level navigation — inline links + Quick Links web parts. Design pattern: use global nav for tenant-wide targets (Home, IT Help, HR, Company Directory); use hub nav for business-unit-wide targets (Finance sub-departments, geographic regions); use site nav for site-specific content. Common mistake: putting site-specific links in hub nav creates visual clutter across all associated sites and requires hub-owner approval to change. Governance rule: hub nav should be stable enough that it changes less than once per quarter.
What are the permission and access-governance implications of hub sites?
Critical clarifications: (1) Hub sites do NOT inherit or cascade permissions to associated sites. Each associated site keeps its own permission model. This is a common misunderstanding — hub association is a NAVIGATION + BRANDING + SEARCH construct, not a permission construct. (2) Hub-scoped SEARCH does surface content from associated sites the user has access to (based on the associated site's own permissions). Users see only content they're permitted to view. (3) Hub site OWNERS can register/unregister sites but cannot see content in associated sites unless separately granted permissions on those sites. (4) SHARING settings (external sharing, guest access) are managed per-site, not per-hub. Hub-wide sharing policy must be enforced via tenant-level policy or SharePoint Advanced Management (Premium). (5) Sensitivity labels applied at the site level cascade to files in that site but do not follow hub association. Governance implication: hub sites are useful for user-experience unification but do NOT solve governance requirements — deploy SharePoint Advanced Management (Premium) alongside for permission auditing, oversharing detection, and access governance.
How does SharePoint hub architecture interact with Microsoft Teams and Viva Connections?
Three interaction patterns: (1) Microsoft Teams — every Team creates a backing SharePoint Team site. These sites can be associated with a hub, inheriting the hub's branding + top nav when viewed in the SharePoint web experience. Teams client shows the SharePoint content but not the hub nav (Teams has its own left-rail navigation). Design pattern: create a hub per business unit; associate every Team-created SharePoint site with the appropriate hub for consistent SharePoint-web-experience navigation while Teams users continue to navigate via Teams. (2) Viva Connections — Viva Connections' HOME experience surfaces the tenant's "home site" (a designated Communication site) with a global nav bar. Home site + hub sites work together: home site is the tenant landing page; hub sites are business-unit landing pages. Viva Connections dashboard cards can source from any SharePoint site the user has access to, including hub-associated ones. (3) Viva Engage — Viva Engage communities are separate from SharePoint hubs; they do NOT link automatically. Cross-linking is a manual navigation-web-part exercise. Enterprise pattern: Home site (Viva Connections) → 5-15 top-level hubs (business unit / geography) → 50-500 associated sites (departments, projects, teams). This structure aligns SharePoint IA with the modern Microsoft 365 employee experience.
What are the 5 most common SharePoint hub architecture mistakes and how to avoid them?
Five common mistakes: (1) Over-hubbing — registering every business unit as a top-level hub instead of using parent-child hub hierarchy. Result: flat 30-50 hub list with no visual hierarchy. Fix: use hub-of-hubs where hierarchy exists (Finance parent hub → Accounting/AP/Treasury child hubs). (2) Under-associating — creating a hub but only associating 2-3 sites. Overhead exceeds benefit. Fix: hub only when 5+ associated sites are expected, otherwise use flat sites with tenant-level design. (3) Hub-wide nav clutter — putting site-specific links in hub nav; hub nav should be 5-9 top-level items maximum. Fix: enforce hub nav governance with quarterly review + site nav for site-specific links. (4) Assuming hub = permission model — associating sites with hub and expecting hub permissions to cascade. Result: security holes when hub owners assume they control associated-site access. Fix: document explicitly that hub is nav/brand/search only; deploy SAM (Premium) for actual access governance. (5) No hub retirement policy — hubs accumulate over 3-5 years and become stale. Fix: implement hub lifecycle policy (annual owner review, inactive-hub deregistration, hub-of-hubs consolidation) as part of tenant SharePoint governance framework.
How should I plan enterprise SharePoint IA — hub-first or site-first?
HUB-FIRST for enterprises with 100+ existing sites. Five-step planning: (1) INVENTORY — enumerate all existing SharePoint sites via SharePoint Admin Center or PowerShell (Get-SPOSite). Group by function, business unit, or geography. (2) ORGANIZATIONAL MODEL — map SharePoint hub structure to org chart. Typical: 5-15 top-level hubs (business units) + optional 1 level of child hubs for large functions. (3) HOME SITE DECISION — designate a home site (Viva Connections landing page) representing tenant/company; this becomes global nav parent. (4) HUB REGISTRATION — register hubs top-down; configure hub navigation with 5-9 top-level items each; establish theme + logo. (5) SITE ASSOCIATION MIGRATION — for each existing site, decide hub association or flat. Migrate 20-50 sites/week. Communicate change management via hub owner announcements. Full enterprise hub IA rollout typically takes 3-6 months for 500-2,000 site tenants. EPC Group has built hub architectures for 6,500+ SharePoint implementations since 1997; the pattern is stable across financial services, healthcare, government, and manufacturing.
Get a SharePoint IA Assessment
EPC Group runs a 4-week fixed-fee enterprise SharePoint hub architecture assessment for tenants with 100+ sites. Call (888) 381-9725.
Phone
(888) 381-9725Business Hours
Monday-Friday, 8 AM - 7 PM CT
Quick Response Guarantee
We respond to all inquiries within one business day