SharePoint Intranet Portal Design Built on Hub Sites
We architect SharePoint Online intranets around the hub-and-spoke site model, wire in Viva Connections as the single mobile and desktop entry point, and configure audience targeting so a new hire in Karachi and a regional manager in Chicago see two different homepages built from the same platform.
Most SharePoint intranets fail for a structural reason
We design the hub site and its taxonomy first, associate every team, department, and project site to that hub through SharePoint's native hub-site model, then layer the home site, mega menu, and Viva Connections dashboard on top. Add a new site six months later and it inherits the same navigation, theme, and search scope automatically, instead of becoming an orphaned page nobody can find.
- Hub-and-spoke site structure with one home site associated to department, regional, and project sites
- Global mega menu navigation synced across all hub-associated sites
- Audience targeting driven by Entra ID security groups and SharePoint metadata
- Viva Connections as the single mobile and desktop entry point
Core Capabilities & Use Cases
Portal architecture, personalization, content intelligence, governance, and custom development patterns built around the same platform.
Integration & Architecture
A SharePoint intranet does not operate as a standalone site. It sits inside the Microsoft 365 stack, and the design decisions account for how it connects to the rest of it.
Entra ID
Identity backbone for conditional access, MFA requirements, and audience targeting groups so intranet access follows the same rules as email and Teams.
Microsoft Viva
Connections for the dashboard experience, Engage for leadership discussions, Amplify for coordinated publishing, and Insights for adoption analytics.
Microsoft Teams
Viva Connections shows up as a native app, and SharePoint pages can be pinned as tabs so the intranet appears where employees already work.
Power Platform
Power Automate handles provisioning and approval flows, Power Apps supports structured forms, and Power BI dashboards embed directly on intranet pages.
Microsoft Purview
Sensitivity labels, DLP policies, and retention rules are applied at the library and site level and enforced consistently across departments.
Microsoft 365 Copilot and Syntex
Copilot supports drafting and summarizing intranet content while Syntex applies classification models trained on your document types.
Azure
Functions and Logic Apps handle complex provisioning workflows and Application Insights captures telemetry for custom SPFx components.
Phased Implementation
The phased approach covers discovery and audit, architecture and design, build and migrate, and launch so you see a working hub and navigation structure before full rollout completes.
Discovery & Audit
Define scope across site templates, languages, and legacy content before architecture work starts.
Architecture & Design
Design hub site architecture, navigation structure, page templates, and governance rules.
Build & Migrate
Implement the intranet build, migrate content, configure integrations, and validate search and targeting.
Launch & Optimize
Launch with adoption tracking, governance reviews, and ongoing SPFx or Power Automate support.
Enterprise Business Benefits
Enterprise outcomes across productivity, security posture, automation efficiency, and user adoption.
Productivity
Search stops being the bottleneck when Syntex classification and managed metadata put documents into a structure the search index can actually use, instead of employees relying on memory for which SharePoint site a file lives in.
Security Posture
Centralizing intranet content behind Entra ID conditional access and Purview sensitivity labels means access control lives in one identity system instead of being managed site by site.
Automation Efficiency
Site provisioning, permission assignment, and content lifecycle policies that used to require a SharePoint administrator's manual attention run through Power Automate and Graph API templates instead.
User Adoption
Audience-targeted content, a mobile-ready Viva Connections dashboard, and search that returns the right document are what separate a portal employees check daily from one that quietly stops getting visits after launch week.
Why Choose Al Rafay Consulting
We've built this kind of information architecture across 500+ SharePoint engagements over 15 years, including environments managing 50 million-plus documents, without a lost migration.
- Hub-first architecture delivered before page-level redesign
- Audience-targeted intranet design integrated with Viva Connections and Teams
- Search, metadata, governance, and automation implemented as one operating model
- 500+ engagements, 15+ years, and 50M+ documents managed without a lost migration
Frequently Asked Questions
How long does a SharePoint intranet portal design engagement take?
Timeline depends on scope, primarily how many site templates, languages, and legacy sites need migrating, but the phased approach (discovery and audit, architecture and design, build and migrate, launch) means you see a working hub site and navigation structure well before the full rollout finishes.
Do you handle content strategy, or just the technical build?
Both. Information architecture, page templates, and governance rules are part of the design phase, not an afterthought bolted on after development. A portal with strong technical architecture and no content plan behind it still fails to get used.
Does the intranet integrate with Teams and Viva, or is it a separate destination?
It's built to live inside the stack you already use. Viva Connections puts the dashboard inside Teams and mobile, and content targeting, search, and identity all run through the same Entra ID and Microsoft Graph layer as the rest of Microsoft 365.
What happens after launch?
Adoption tracking through Viva Insights, governance reviews, and ongoing SPFx or Power Automate support are available as follow-on engagements, since the sites and workflows that made sense at launch usually need adjustment once real usage data comes in.
Ready to Redesign Your SharePoint Intranet?
We'll audit what you have, map the hub structure it should have been built on, and show you what a working version looks like before you commit to the full build.