Collaboration workloadsIntermediate24 min read

What Does Hub site Mean?

Reviewed byJohnson Ajibi· Senior Network & Security Engineer · MSc IT Security

This page mentions older exam versions. See the Current Exam Context and Legacy Exam Context sections below for the updated mapping.

On This Page

Quick Definition

A hub site is a SharePoint feature that links multiple related sites together. It creates a central place for information, branding, and navigation. This helps people find content across different teams or departments. Think of it as a main office that connects several smaller branch offices.

Common Commands & Configuration

Register-SPOHubSite -Site https://yourtenant.sharepoint.com/sites/HubSiteName -Permissions $null

Registers a modern communication site as a hub site. The -Permissions parameter can be set to a group or $null to allow all users to associate sites.

Set-SPOHubSite -Identity https://yourtenant.sharepoint.com/sites/HubSiteName -HideNameInNavigation $true

Hides the hub site name from the navigation bar on associated sites, which can create a cleaner look.

Get-SPOHubSite

Lists all hub sites in the tenant with their properties, including the number of associated sites.

Get-SPOHubSiteChildSite -Identity https://yourtenant.sharepoint.com/sites/HubSiteName

Returns all sites associated with a specific hub site.

Remove-SPOHubSite -Identity https://yourtenant.sharepoint.com/sites/HubSiteName

Unregisters a site as a hub site, causing all associated sites to become standalone again.

Must Know for Exams

Hub sites are a common topic in several general IT certification exams that cover Microsoft 365, particularly the MS-100 (Microsoft 365 Identity and Services), MS-101 (Microsoft 365 Mobility and Security), and the SharePoint-specific exams such as the MCSE Productivity or the newer certification paths. While hub sites are not a core objective for basic entry-level IT certifications like CompTIA A+ or Network+, they become highly relevant once you move into cloud collaboration and administration. In the MS-100 exam, for example, planners and administrators need to know how to plan a hub site architecture for an organization with specific requirements, such as regional offices or functional departments. Questions may ask you to identify the correct steps to enable a hub site, the maximum number of associated sites, or how to configure site designs to automate hub association.

In the MS-101 exam, the focus shifts to security and compliance. You might see scenarios where a hub site is used to manage information barriers or data classification. For example, you might need to know that hub sites do not automatically inherit permissions from the parent hub, so each associated site must still have its own access controls. This is a common trick in exam questions, where a learner assumes that associating a site with a hub also grants the hub admin access to that site. That is incorrect, and the exam will test that nuance. Questions often appear in the planning section of the exam, where you must recommend whether to create a new hub site or associate an existing site to an existing hub. You must weigh the business need for centralized governance against the need for independent site identity.

Question types include scenario-based multiple choice, drag-and-drop ordering of steps, and yes/no decisions. For example, a question might describe a company with four departments that each have their own SharePoint site, and the business wants unified navigation and search but each department needs to maintain its own unique permissions. The correct answer is to create a hub site and associate all four department sites. Another question might ask about the impact on search: after associating a site with a hub, what happens to search results? The correct answer is that search scopes expand to include the hub and all associated sites. Understanding these technical details directly affects your exam score. Therefore, it is essential not just to know what a hub site is, but to understand its limitations, management methods, and relationship to other SharePoint features like site collections, search, and permissions.

Simple Meaning

Imagine you work for a large company that has many different departments: Sales, Marketing, Engineering, and Human Resources. Each department has its own website within the company's internal system. Without any organization, you would have to bookmark each department's site separately, and you might miss important announcements from other teams.

A hub site is like building a central town square that connects all these department buildings. From this square, you can see a directory of all the departments, a shared calendar of company events, and a common set of signs and colors that make everything feel like one unified community. When the Marketing team updates their site, that update can automatically appear in the news feed of the hub site, so everyone in the company stays informed.

The hub site also allows you to search across all connected sites at once, instead of searching each department separately. In technical terms, a hub site is a SharePoint site that has been designated as a hub, allowing other sites to associate with it. Once associated, those sites inherit the hub's navigation, branding, and security policies.

This simplifies management because instead of updating each site individually, you can make changes at the hub level and they propagate to all connected sites. A hub site is not just a collection of links; it is a structural relationship that creates a more cohesive and manageable digital workspace.

Full Technical Definition

A hub site is a specific SharePoint communication site that has been elevated to serve as a central aggregation point for a collection of related sites, known as associated sites. From a technical perspective, the hub site feature is built on top of SharePoint's site architecture and leverages several underlying components and protocols. The hub site itself is defined at the tenant level in Microsoft 365, and its creation and management are governed by SharePoint Online administration. The core functionality relies on the SharePoint REST API and the SharePoint Client Side Object Model (CSOM) to establish and maintain the association between the hub and its connected sites.

When a site is associated with a hub, a one-to-many relationship is established. The hub site publishes its navigation structure, theme, and logo to all associated sites. This is achieved through a background synchronization process. When a user navigates to any associated site, the browser first loads the site’s content, then fetches the hub data from the hub site via server-side calls. This data includes the global navigation tree, which appears as a top navigation bar on all associated sites. The hub also provides a consolidated search experience. When a user performs a search from an associated site, the search results are scoped to include content from the hub and all other sites connected to that hub. This is made possible by SharePoint's search index, which is aware of hub associations and can deliver federated results.

From an IT implementation standpoint, configuring a hub site involves several steps. First, an administrator must enable the hub site feature on a communication site using PowerShell or the SharePoint admin center. There is a limit on the number of hub sites per tenant, which is 2,000 per tenant. Each hub site can have up to 50,000 associated sites, but performance considerations often lead to lower practical limits. The administrator sets permissions for who can associate sites with the hub. Once a hub is ready, site owners or administrators can connect their sites to the hub through the site settings. The association is recorded in the site’s metadata, and the hub GUID is stored in the site’s property bag. The hub site also supports content rollout through the use of site designs and site scripts. Site designs allow administrators to apply standardized templates, themes, and navigation to new sites as they are created or associated. This provides a powerful mechanism for enforcing governance and consistency across an organization’s digital estate.

Security and compliance considerations also come into play. While the hub aggregates navigation and search, it does not override existing site permissions. Each associated site retains its own permission sets. However, the hub site can surface content from associated sites through web parts and news rollups, which are subject to the viewing user's permissions. This means a user may see a link or headline from another site but cannot access the underlying content without proper permissions. For exam purposes, it is critical to understand that hub sites are a logical organization structure, not a security boundary. In exam scenarios, you might be asked to identify the correct way to set up a hub site for a specific business need, such as unifying intranet content for a global corporation. The correct answer often involves creating a hub site and associating child sites, while ensuring that permissions are managed at the individual site level.

Real-Life Example

Think of a large public library system in a city. The main downtown library is the hub site. It has a central information desk, a grand calendar of events, and a consistent color scheme and signage.

Around the city, there are several branch libraries, each serving its own neighborhood. Before the hub concept, each branch had its own website, its own event calendar, and its own way of listing books. If you wanted to find a book, you had to check each branch's site separately.

The decorations and signage at each branch might be different, making it confusing to know which library system you were in. With a hub site approach, the main library creates a unified digital presence. Each branch site now shares the main library's navigation bar, so you can always see links to other branches.

The main library's calendar automatically shows events from all branches. If a new policy is announced at the main library, such as a new late fee structure, that announcement appears as a news post on every branch site. Visitors can search across all branches from the main library's search box.

In this analogy, the main library is the hub site, and each branch is an associated site. The shared branding, navigation, and search are the technical benefits. IT professionals would recognize how this maps to a SharePoint hub site, where a single top-level site controls the look and feel for many child sites, reducing administrative overhead and creating a seamless user experience.

Why This Term Matters

In a practical IT environment, especially one that uses Microsoft 365 and SharePoint, hub sites are a critical tool for information architecture and user experience. Without hub sites, an organization with many teams and departments would end up with a disconnected collection of SharePoint sites. Users would have to remember multiple URLs, log in to different places, and miss important cross-team updates. This leads to inefficiency, duplicated work, and poor communication. Hub sites solve this by providing a single, consistent way to navigate the digital workspace. For IT administrators, the value is immense because they can manage branding, navigation, and content rollup from one place. Security is simplified because permissions are still independently managed, but the hub provides a clear governance point for site creation and association.

From a business perspective, hub sites improve productivity. Employees spend less time searching for information and more time doing their work. They stay informed about company news and events through centralized news feeds. The consistent navigation reduces confusion and training time for new hires. For IT professionals studying for general IT certifications, understanding hub sites is essential because these concepts are part of the modern digital workplace. Many exam questions test the ability to plan and implement a hub site architecture for a given business requirement. Knowing how hub sites relate to site collections, permission inheritance, and search scoping is key. It also impacts compliance and information governance, because hub sites can be used to enforce retention policies or content types across a set of sites. Hub sites matter because they are a foundational element of modern SharePoint intranets, and they directly affect user satisfaction, administrative efficiency, and organizational communication.

How It Appears in Exam Questions

Exam questions about hub sites typically appear in three main patterns: scenario-based design, configuration steps, and troubleshooting. In a scenario-based design question, you are given a business requirement such as a global company needing to organize its intranet for different regions. You will be asked to choose the best approach from a list of options. For instance, one option might be to create a single hub site for all regions, another might be to create a hub site per region, and another might be to use a team site for each region without a hub. The correct answer usually involves creating multiple hub sites, each representing a region, and then associating regional site collections to the respective hub. The trick is to recognize that hub sites are ideal for grouping related sites, but you should not mix unrelated groups in one hub.

Configuration step questions ask you to order the steps required to create a hub site and associate a child site. A typical sequence is: 1) Create a communication site, 2) Register the site as a hub site via PowerShell or admin center, 3) Set permissions to allow site association, 4) On the child site settings, connect to the hub site, 5) Verify the hub navigation appears. These questions often test your knowledge of the correct PowerShell cmdlet, such as Register-SPOHubSite. You need to know that the cmdlet comes from the SharePoint Online Management Shell. Another configuration nuance: you can only register a communication site or modern team site as a hub site. Classic team sites cannot be hubs.

Troubleshooting questions present a broken scenario. For example, a user reports that the navigation bar from the hub site is not showing up on their associated site. The possible causes might include: the site is not properly associated, the user does not have permissions to see the hub navigation, the hub site itself is not accessible, or there is a synchronization delay. The correct answer could be that the site association requires approval, or that the hub site URL was changed after association. Another common troubleshooting point: a user cannot see content from other associated sites in the search results. The fix involves ensuring the user has at least read access to those sites, because search results respect security trimming. The exam will expect you to identify that permissions are independent of hub association.

There are also questions that test your understanding of limits. For instance, how many hub sites can a tenant have? Answer: 2,000. How many sites can associate to one hub? Up to 50,000, but performance may degrade beyond 2,000. These numbers are directly testable. Finally, some questions ask about the difference between a hub site and a site collection. The key is that a hub site is a logical grouping of site collections across the tenant, while a site collection is a strict administrative and security boundary. Hub sites cross site collection boundaries for navigation and search, but not for permissions.

Practise Hub site Questions

Test your understanding with exam-style practice questions.

Practise

Example Scenario

You are the IT administrator for a medium-sized company called EcoTech Solutions. The company has three main departments: Sales, Research, and Support. Each department currently has its own separate SharePoint site, but employees have to bookmark three different websites.

The CEO wants a unified intranet experience where everyone can see company news and navigate between department sites easily. The departments also want to keep their own specific documents and permissions, because Sales data should not be visible to the Support team. You decide to implement a hub site.

You create a new communication site called EcoTech Central as the hub. Using PowerShell, you register EcoTech Central as a hub site. You then go into the settings of the Sales, Research, and Support sites, and under the Hub site section, you enter the URL of EcoTech Central and click Join.

After a few minutes, the sales team member logs in and sees that the top navigation bar now shows links to Research and Support, plus a home link back to EcoTech Central. The company news that you posted on EcoTech Central also appears on the Sales site's news web part. A support technician searches for a product manual; the search results include documents from both Support and Research sites, even though the tech only browsed to the Support site.

This works because the hub site expands the search scope. Later, a manager worries that associating a site to the hub will give the hub admin access to their private documents. You explain that this is not the case, because permissions are still managed independently on each site.

The hub only affects navigation, branding, and search. This scenario demonstrates the correct implementation and the key benefits of hub sites: unified navigation, shared news, expanded search, and independent permissions.

Common Mistakes

Thinking that associating a site with a hub automatically gives the hub site admin access to the associated site.

Hub sites do not inherit permissions. Each site retains its own security settings. The hub only provides navigation, branding, and search aggregation.

Always remember that permissions are separate from hub association. If you need admin access to an associated site, you must add yourself to that site's permissions separately.

Assuming that all types of SharePoint sites can be registered as hub sites.

Only modern communication sites and modern team sites can be hub sites. Classic team sites and publishing sites cannot be registered as hubs.

When planning a hub site, create a new communication site or ensure you are using a modern team site. Avoid using classic templates.

Believing that a site can be associated with more than one hub site at a time.

A SharePoint site can only be associated with one hub site. If you want to be part of multiple groups, you need to restructure your hub architecture (e.g., use a single hub for related content).

Check the association status of a site before attempting to join another hub. If you need multi-hub benefits, consider using a hierarchical structure or a separate metadata tagging system.

Assuming that hub site navigation will appear immediately for all users.

Propagation of hub navigation and branding can take some time, especially in large tenants. Caching in the browser may delay the new navigation from appearing.

After association, wait a few minutes and then refresh the browser cache. If it still doesn't appear, use the SharePoint admin center to verify the association status.

Thinking that a hub site can be deleted without affecting associated sites.

Deleting a hub site will remove the association for all connected sites. They will lose the hub navigation, branding, and search scope. The sites themselves are not deleted, but they become standalone sites.

Before deleting a hub site, either disassociate all sites or designate a new hub site to take its place to avoid disruption.

Exam Trap — Don't Get Fooled

{"trap":"A question presents a scenario where a company wants to enforce a consistent set of permissions across all department sites. The solution offered is to create a hub site and associate all department sites to it, assuming the hub permissions will flow down.","why_learners_choose_it":"Learners often confuse hub sites with site collections or group hierarchies where permissions can be inherited.

They incorrectly believe that the hub acts as a parent security boundary.","how_to_avoid_it":"Understand that hub sites are purely a logical grouping for navigation and search. Permissions are not inherited from the hub.

For consistent permissions across multiple sites, you must either manage each site individually or use Azure Active Directory groups to assign permissions through a consistent membership structure."

Commonly Confused With

Hub sitevsSite collection

A site collection is a strict administrative boundary that includes a top-level site and its subsites. Permissions and configurations can be inherited within a site collection. A hub site, on the other hand, connects multiple site collections together without creating a parent-child permission hierarchy.

Think of site collections as individual buildings with their own security gates. Hub sites are like a central plaza that provides a common directory and signs, but each building still has its own guards.

Hub sitevsTeam site

A team site is a collaborative workspace for a group, often connected to Microsoft 365 groups. A hub site is a special type of communication site that organizes other sites. While a team site can be associated to a hub, a team site itself is not typically a hub unless specifically registered as one.

A team site is like a project room where a team works. A hub site is like the main lobby of the office that points to all project rooms.

Communication sites are designed to broadcast information to a wide audience, often with a single author or small group of editors. A hub site is a role that a communication site (or modern team site) can take on. Not every communication site is a hub, but every hub is a communication site (or modern team site).

A communication site is a bulletin board. A hub site is a bulletin board that also organizes and links to other bulletin boards.

Step-by-Step Breakdown

1

Create a Communication Site

First, you need a modern communication site to act as the hub. This site will be the central location for navigation, branding, and news. The site name should reflect the grouping it represents (e.g., Sales Hub).

2

Register the Site as a Hub Site

Using the SharePoint admin center or PowerShell (Register-SPOHubSite), you designate the communication site as a hub site. This action elevates the site's role and enables it to accept associations from other sites.

3

Configure Permissions for Association

In the hub site settings, you define which users or groups can associate sites with this hub. This prevents unauthorized sites from joining. By default, only site owners can request association, but you can open it to all users.

4

Associate a Child Site to the Hub

Navigate to the site you want to connect (e.g., the Sales department site). Go to Site settings, Hub site settings, and enter the hub site URL. Click Join. The site will send a request to the hub.

5

Verify the Association

After association, the child site should display the hub's top navigation bar. You can also check the hub site to see the list of associated sites. Verify that branding and search scope are functioning correctly.

6

Manage Content Rollup

Add web parts to the hub site, such as news, events, or highlighted content, that will pull data from associated sites. This creates a centralized dashboard of activities across the group.

Practical Mini-Lesson

To truly understand hub sites, you need to know how they fit into a broader SharePoint and Microsoft 365 governance strategy. When you create a hub site, you are not just setting up a website; you are defining a logical boundary for collaboration and communication. In practice, an IT professional will first assess the organization’s structure. For instance, a multinational company might have separate hub sites for each region: North America, Europe, and Asia. Each regional hub then contains department sites like Sales, Marketing, and HR for that region. This hierarchical approach helps manage the scale of content and keeps search relevant to the region.

When configuring a hub site, you must pay attention to the site design and site script capabilities. A site design can be created that automatically associates a new site with a specific hub. This is powerful for onboarding new teams. For example, when a new project team is created, a site design can trigger creation of a communication site and immediately associate it to the Projects hub, applying a consistent theme and navigation. This reduces manual effort and ensures compliance with corporate standards.

One common practical issue is managing the hub site’s navigation. The hub navigation is managed on the hub site itself, and it propagates to all associated sites. If you have too many links, the navigation becomes cluttered. Best practice is to keep the navigation limited to top-level groupings and use the hub news feed to communicate specific updates. Also, the hub site itself can become a bottleneck if it is not properly maintained. If the hub site is taken offline for maintenance, associated sites cannot fetch navigation or search scope data, which may cause delays or errors for users.

Security is another practical consideration. Even though the hub does not override permissions, you may want to limit who can create hub sites. You can create a hub site naming policy to ensure consistency. Another important feature is the ability to change a site’s association. If a site is incorrectly associated, you can unjoin it from the hub and join it to a different one. This process is straightforward but may temporarily disrupt navigation on that site. Finally, performance tuning is critical. With thousands of associated sites, the hub's search and navigation performance can degrade. In such cases, you might need to split into multiple hubs. The exam will not expect you to know performance tuning in depth, but being aware of limits helps you choose the right architecture. Practice by creating a test environment and associating several sites, then observe how changes at the hub level propagate. Professionals often use the SharePoint PnP PowerShell module to automate hub site management, which is an advanced skill but not required for entry-level exams.

Troubleshooting Clues

Symptom: Hub navigation not appearing on associated site

Symptom: Search results do not include content from other associated sites

Symptom: Hub site nonfunctional after renaming

Symptom: Cannot associate a site to a hub

Memory Tip

Think HUB = Homes Unite But (permissions are) Separate.

Covered in These Exams

Current Exam Context

Current exam versions that test this topic — use these objectives when studying.

Legacy Exam Context

Older materials may mention these exam versions, but learners should use the current objectives for their target exam.

MS-100MS-102(current version)
MS-101MS-102(current version)

Related Glossary Terms

Quick Knowledge Check

1.What is the main purpose of a SharePoint hub site?

2.A user can associate a site to how many hub sites at once?

3.What happens to the permissions of a site when it is associated with a hub site?

Frequently Asked Questions

Can I have multiple hub sites in one tenant?

Yes, a tenant can have up to 2,000 hub sites. Each hub site serves a different group of related sites.

Does associating a site to a hub site change its URL?

No, the site's URL remains unchanged. Only the navigation and branding are inherited from the hub.

Can a classic SharePoint site be a hub site?

No, only modern communication sites and modern team sites can be registered as hub sites. Classic sites are not supported.

What happens if I delete the hub site?

All associated sites will lose their hub navigation, branding, and search scope. They become standalone sites but are not deleted.

How do I remove a site from a hub?

In the site settings, go to the Hub site section and choose to disassociate from the hub. This can also be done via PowerShell.

Can I change which site is the hub without losing associations?

No, you must unregister the original hub and then re-associate all sites to a new hub. This can be disruptive, so plan carefully.

Summary

A hub site is a powerful SharePoint feature that allows organizations to group related sites together under a centralized navigation, branding, and search experience. It does not alter the security or permissions of the associated sites, which is a critical distinction for exam success. The practical implementation involves creating a modern communication site, registering it as a hub, and then connecting child sites. There are limits to remember, like a maximum of 2,000 hub sites per tenant and 50,000 associated sites per hub.

For IT certification exams, understanding hub sites is most relevant for Microsoft 365 administration exams such as MS-100 and MS-101. Questions often focus on scenario-based planning, configuration steps, and troubleshooting common association problems. Common mistakes include confusing permissions with navigation, thinking a site can belong to multiple hubs, and assuming all site types can be hubs. The exam trap to avoid is believing that the hub site acts as a security parent.

In practice, hub sites improve user experience and reduce administrative overhead by enabling consistent branding and search across large digital workspaces. IT professionals should be comfortable with PowerShell commands for managing hub sites and should plan their hub architecture carefully based on organizational needs. Remember the key takeaway: hub sites organize, they do not secure. Keeping this principle in mind will help you answer exam questions correctly and implement solutions effectively in the real world.