Walk into almost any 100 to 500 person company in the Carolinas and ask to see the intranet. In Charlotte it might be a finance firm with 140 SharePoint sites. In Greenville it might be a healthcare practice group with a site per clinic. In the Triad it might be a manufacturer with a site per plant, plus a few dozen project sites nobody remembers creating. The pattern is the same: lots of sites, no structure connecting them, and employees who default to asking a coworker instead of searching.
SharePoint hub sites are Microsoft’s answer to that problem. They are also one of the most misunderstood features in Microsoft 365. Done well, hubs give you a flat, flexible intranet that survives reorganizations. Done poorly, they become another layer of navigation nobody uses.
And in 2026 there is a new reason to get them right. AI tools like Microsoft 365 Copilot and SharePoint agents work best when content is organized into clear, well-scoped areas. Hub structure is one of the strongest signals you can give them.
What a hub site actually does
A hub site is a regular SharePoint communication or team site that an administrator registers as a hub. Other sites then associate with it. Once associated, those sites gain:
- Shared navigation. A hub navigation bar appears across the top of every associated site, so users can move between related sites without hunting for links.
- A consistent theme. Associated sites pick up the hub’s look, which signals to employees that they are still inside the same area.
- Rolled-up content. News, events, and documents from associated sites can be surfaced on the hub home page with web parts.
- Scoped search. Searching from a hub returns results from the hub and its associated sites, which is far more relevant than a tenant-wide search.
What a hub does not do is just as important. Associating a site with a hub does not move content, does not change the site’s URL, and does not change its permissions unless you choose to sync hub visitors. Each site keeps its own owners and its own security. That separation is the whole point.
Why hubs replaced subsites
Older SharePoint intranets were built as deep trees of subsites. HR under Corporate, Benefits under HR, Open Enrollment under Benefits. The problem was that the tree locked in today’s org chart. When HR moved under a new Chief People Officer, or a division was sold, the structure had to be rebuilt and permissions inherited down the tree came along for the ride.
Modern SharePoint is flat. Every team or function gets its own site collection, and hubs provide the grouping on top. If a department moves, you change its hub association in a few clicks. Nothing breaks, no URLs change, and no permissions get reshuffled. For mid-market companies going through growth, acquisitions, or restructuring, which describes a lot of businesses in the Charlotte and Research Triangle markets right now, that flexibility matters.
If you are still running subsites from a SharePoint 2013 or 2016 migration, flattening them into separate sites and grouping them with hubs is usually the first step of an intranet modernization. Our post on SharePoint information architecture before site creation covers the planning that should come before you create anything.
How many hubs does a mid-market company need?
Fewer than you think. Microsoft allows up to 2,000 hub sites per tenant, but that is a technical ceiling, not a target. For a company of 100 to 500 people, the right number is usually between three and eight.
A useful starting structure:
- A home site or company hub. Company news, leadership updates, policies, and links to everything else. This is the front door.
- Functional hubs. One each for the major internal service areas employees go looking for: HR and People, Finance, IT, Operations. Each department’s sites associate here.
- A business unit or location hub, only if needed. A multi-site manufacturer in the Piedmont or a healthcare group with clinics across Eastern NC may want a hub per region or division. A single-location professional services firm probably does not.
- A projects or clients hub, if your work is project-based. Engineering, construction, and consulting firms often benefit from grouping project sites so search and rollups work across them.
The test for every proposed hub is simple: will an employee think of this as a place they go? If the answer is no, it should be a site, not a hub.
Hub to hub association
SharePoint lets you associate a hub with another hub, creating a hierarchy for search and navigation up to three levels deep. For example, a Plant Operations hub can associate with a broader Operations hub, so a search from Operations includes plant content.
Use this sparingly. Hub to hub association is helpful for large divisions, but it is easy to recreate the old subsite tree in a new form. For most mid-market companies, one level of hubs under a home site is enough.
Planning decisions to make before you register a hub
Who owns it. Every hub needs a named business owner, not just an IT administrator. The owner decides what belongs in the hub navigation, approves new associations, and keeps rollup content current. Without one, hubs decay in about a year.
Who can associate sites. By default, only people with permission can associate a site to a hub. Restrict association rights to the hub owners and IT. Otherwise you will find project sites from three years ago associated with your HR hub.
Navigation design. Hub navigation supports multiple levels of links. Keep it to what people actually use, ideally fewer than ten top-level items. Link to associated sites and to the most-used pages inside them, and label links in the language employees use, not the name of the department on the org chart.
Permissions sync. Hubs offer an option to sync hub visitors to associated sites. This is convenient for broadly shared content such as policies, but it should be a deliberate choice per hub. Never turn it on for a hub that includes sensitive sites like Finance or HR case management. We cover the broader permission picture in SharePoint permissions: inheritance done right.
Naming and URLs. Pick a naming convention before the first hub is created. Hub names show in navigation and search, and renaming later confuses users.
Why hub structure matters more in the AI era
Here is the part that changed in the last two years. When a Carolina business turns on Microsoft 365 Copilot, employees start asking questions in plain language: “What is our PTO carryover policy?” or “Summarize the latest safety bulletins for the Kinston plant.” Copilot answers by retrieving content the user has permission to see, using the same Microsoft Graph and semantic index that power search.
A clean hub structure helps in three concrete ways:
- Better retrieval. When policy content lives in an HR site associated with an HR hub, with consistent page titles and metadata, the right document is much easier for both search and Copilot to find than when copies are scattered across team sites and OneDrive folders.
- Scoped agents. SharePoint agents can be grounded on specific sites and libraries. A hub structure gives you natural boundaries for building an HR agent, an IT help agent, or a safety procedures agent that only answers from approved sources.
- Cleaner governance. Hubs make it easier to see which sites belong to which area, who owns them, and which ones hold sensitive content. That is exactly the inventory you need before restricting AI access with tools like Restricted Content Discovery or sensitivity labels.
The companies we see getting real value from Copilot in the Carolinas are not the ones with the most licenses. They are the ones who organized their content first. Hubs are one of the cheapest, fastest ways to do that. For a broader look at what Copilot can and cannot do today, see AI in Microsoft 365: real features versus marketing.
Common mistakes to avoid
- Making every department a hub. If Facilities has one site, it does not need a hub. Associate it with Operations.
- Using hubs as a security boundary. Hubs group sites. Permissions still live on each site. Plan security at the site level.
- Building the hub before the content. An empty hub with a nice theme is not an intranet. Migrate and clean up the key content first, then launch the hub.
- Copying the org chart. Structure hubs around what employees look for, not who reports to whom. Org charts change. Employee questions mostly do not.
- No lifecycle for associated sites. Project sites should be archived or disassociated when projects close, or hub search and rollups fill with stale content that also confuses AI tools.
A practical rollout sequence
- Inventory existing sites. Export the site list from the SharePoint admin center, note owners and last activity, and flag sites to archive.
- Draft the hub map. Three to eight hubs, each with a named owner and a one-sentence purpose.
- Create or choose hub sites. Usually communication sites. Build the home page and navigation.
- Register hubs and set association permissions. Restrict who can associate sites.
- Associate sites in waves. Start with the most-used areas, such as HR and IT, so employees see value quickly.
- Tune search and Copilot readiness. Review titles, metadata, and permissions on high-traffic content, and remove duplicates.
- Review quarterly. Hub owners check navigation, rollups, and new associations. Add a hubs section to your SharePoint governance plan.
For most mid-market companies, this takes four to eight weeks with a focused team, and the hardest part is usually agreeing on the hub map, not the technical work.
The bottom line
Hub sites are not glamorous, but they are one of the highest-leverage improvements a mid-market company can make in SharePoint. They make the intranet navigable, they absorb reorganizations without rework, and they give AI tools the structure they need to return useful answers instead of noise. For Carolina businesses planning a Copilot rollout in the next year, a hub strategy belongs on the list before the licenses are purchased.
Devsoft Solutions is a Greenville, NC Microsoft Partner that designs and builds SharePoint intranets, hub structures, and Copilot readiness programs for businesses across North and South Carolina. If your SharePoint has grown into a maze of disconnected sites, get in touch and we will help you map a structure that works.