A practical guide for business and IT leaders planning, modernizing, or rescuing their Microsoft 365 intranet.
Most organizations that roll out a SharePoint intranet do not have an adoption problem on day one. They have one within six months. Employees visit the homepage a few times, fail to find what they need, and quietly stop going back. Announcements go unread. Policies stay buried. HR documents are requested by email because nobody knows where to look online.
This is not a SharePoint problem. It is a planning and ownership problem. SharePoint has the architecture, the integration depth, and the flexibility to support a modern, functional intranet. The question is not whether SharePoint can do it, but whether the organization is willing to treat the intranet as a business communication and knowledge-sharing platform rather than an IT deployment. According to McKinsey & Company research, employees spend an average of 1.8 hours every day, 9.3 hours per week, searching and gathering information, underscoring how critical a well-structured intranet is to daily productivity.
This blog covers why so many intranets stall after launch, what employees actually expect from one, and how to plan and build a SharePoint intranet people return to as part of their daily work.
The pattern is familiar. An organization decides it needs a better way to share information internally. SharePoint is already part of the Microsoft 365 subscription, so IT spins up a site, migrates some documents, adds a few announcements, and calls it the intranet. Leadership gets a demo. The link goes out in a company email. Usage trails off within weeks.
The failure is rarely technical. It is structural. Here is what goes wrong most often:
• The intranet is built as a document dump, not a destination. When employees land on a page and see nothing but folders and links to files, they do not come back.
• Navigation is designed around the org chart, not around what people actually look for. Employees do not think in terms of department names when they need something; they think in terms of tasks.
• No one owns the content. When pages are never updated, employees learn not to trust the intranet for up-to-date information and instead go back to email threads and direct messages.
• Search does not surface the right results. Without proper metadata and content tagging, SharePoint search returns too much irrelevant content, which feels worse than no search at all.
• The intranet was not built around employee input. When the people using the platform were not consulted during design, the result often reflects what IT or management wanted to publish rather than what employees need to find.
A SharePoint intranet only works when it is treated as a business communication and knowledge-sharing platform, not as a file storage migration project. Gallup data shows that only 13% of employees strongly agree that their organization's leadership communicates effectively with the rest of the organization — a gap that a well-designed intranet is uniquely positioned to close.
One of the most important distinctions in intranet planning is understanding the difference between a document library and an intranet. SharePoint can do both, and that flexibility is a strength, but it also creates confusion about what the intranet is supposed to be. A document repository is where files live. An intranet is where people go to understand what is happening in the organization, find resources relevant to their role, and navigate to the tools they use every day. Think of the difference between a filing cabinet and a company lobby. Both are useful. They serve different purposes.
A well-designed SharePoint intranet typically brings together. For a deeper look at how to get more value from the platform, see how to effectively use SharePoint to transform your business:
• Company-wide news, announcements, and leadership updates on a central homepage
• Department pages with role-relevant resources, not just document folders
• HR and operations content: policies, benefits information, onboarding guides, forms, and FAQs
• A knowledge base or resource hub that employees can actually search
• Quick links to tools employees use daily: Teams, Outlook, HR systems, project tools
• People directories and org charts
• Recognition content, upcoming events, and internal communications
The documents are still there. They are organized within the right section, tagged with the right metadata, and findable through search. But the intranet itself is designed around people and tasks, not around folders.
Expectations for internal digital tools have shifted. Employees who use modern consumer apps and SaaS products at work expect similar clarity and responsiveness from their intranet. A cluttered homepage with stale announcements from two years ago does not meet that bar.
When employees describe a useful intranet, they typically point to four things:
They can find what they need without clicking through multiple layers of menus or remembering a specific site URL. Navigation is structured around categories people naturally think in — not department names or internal project codes.
Policies are up to date. Announcements are relevant to their team or role. When the intranet becomes the place where accurate information lives, employees start using it. When outdated content remains visible, they stop trusting it.
A significant portion of employees in many industries access internal tools on phones or tablets, particularly in field services, healthcare, retail, and logistics. A SharePoint intranet that renders poorly on mobile loses that audience immediately. SharePoint's modern experience is responsive by default, but navigation and content layout still need to be designed with mobile use in mind.
Employees should not have to leave the intranet to get to the tools they use most. Integrating Microsoft Teams channels, Outlook updates, OneDrive documents, and Power Automate workflows, where relevant, means the intranet becomes a hub rather than a detour. Microsoft Viva Connections can extend this further by surfacing intranet content directly in MS-Teams, where many employees already spend most of their day. Calance's Microsoft 365 services cover the full integration between SharePoint, Teams, and the broader Microsoft 365 ecosystem.
Before any SharePoint site is created, the leadership team and key stakeholders need to answer a more fundamental question: what is this intranet supposed to accomplish?
The answer varies by organization. For a company managing rapid headcount growth, the intranet might be most valuable as a hub for onboarding and HR resources. For a distributed organization, it may be the central channel for leadership communications. For a company with complex compliance requirements, it may be the system of record for policies and procedure documentation.
Defining the business purpose upfront shapes everything that follows: what content to prioritize, how to structure navigation, which departments need dedicated pages, and what success looks like after launch.
Useful questions to work through with stakeholders before building:
• What are the top three things employees should be able to find in under two minutes?
• What content currently causes the most confusion or repeated questions to HR and IT?
• What tools do employees use most, and should the intranet surface links to them?
• Who will own each section of the intranet, and how often will content be reviewed?
• What does a new employee need from the intranet in their first week?
These answers should drive design decisions, not the other way around.
SharePoint's modern architecture provides organizations with a flexible framework for building intranets that scale across departments and geographies. Understanding how the components work together is essential before building. For a comprehensive reference on custom SharePoint development services and architecture best practices, Calance has published an in-depth expert guide on the subject.
A hub site is the organizing layer of a SharePoint intranet. It connects related sites, provides shared navigation, and allows news to roll up from multiple associated sites into a single location. Most organizations have one primary hub site for their company-wide intranet and may create additional hubs for major departments or regions.
Communication sites are designed for broad, one-to-many publishing. The company homepage is typically a communication site. Department-level pages, HR portals, and internal communications pages are also well suited to this format. They are visually oriented and built for reading and browsing.
Team sites are designed for collaboration within a specific group. They connect directly to a Microsoft 365 Group, giving the team access to shared document libraries, a OneNote notebook, a Teams channel, and a shared calendar. Team sites are not typically part of the public-facing intranet; they are workspaces for internal collaboration by a smaller team or group.
Navigation is where intranets most commonly break down. The structure should reflect how employees think about finding things, not how the organization is structured internally. A flat, task-oriented navigation with clear labels like HR & Benefits, Policies, Tools & Systems, News, and Departments performs better than a menu that mirrors the reporting hierarchy.
Test navigation assumptions early. Ask a sample of employees to describe where they would go to find specific things. If the answers are inconsistent or uncertain, the navigation needs work before launch.
The following framework covers the decisions most organizations need to make before SharePoint configuration begins. Use it as a working checklist with your stakeholders.
|
Planning Area |
Key Decision |
Who Should Own It |
|
Business Purpose |
What is the intranet for? Comms, HR, knowledge base, onboarding? |
Leadership, HR, Internal Comms |
|
Information Architecture |
Hub site structure, site hierarchy, and navigation labels |
IT, intranet project lead |
|
Content Ownership |
Who owns each section, and how often is content reviewed? |
Department heads, HR, Comms |
|
Search & Metadata |
What tags and content types will be used? How will search be configured? |
IT, SharePoint admin |
|
Permissions & Security |
Who can view, edit, and publish on each site? |
IT, HR, Legal |
|
Microsoft 365 Integration |
Which tools will the intranet surface? Teams, Viva, Power Automate? |
IT, Microsoft 365 admin |
|
Governance |
Site creation policy, content review cadence, and archiving rules |
IT, Legal, Comms |
|
Launch & Adoption |
How will employees be introduced to the intranet? |
HR, Comms, IT |
Content is the single biggest reason intranets succeed or fail after launch. A beautifully designed site with outdated or irrelevant content fails just as surely as a poorly designed one.
The most useful intranet content falls into a few clear categories. At the company level, employees expect to find leadership news, organizational announcements, the company calendar, and links to essential tools. At the department level, they want role-specific resources. HR team members want quick access to benefits enrollment guides; operations teams want process documentation; sales teams want product collateral and competitive information.
Common content that should be accounted for in the intranet plan:
• HR resources: benefits guides, leave policies, onboarding documents, and employee forms
• Company policies: code of conduct, IT acceptable use, expense policies, and compliance requirements
• Department pages: team-level resources, contacts, announcements, and project links
• Knowledge base: how-to guides, internal FAQs, process documentation, and training resources
• Leadership updates: video messages, blog posts, or news items from senior leadership
• Tools and quick links: direct links to the systems and information employees use every day
For each section, the plan should identify a content owner, a named individual, or a team responsible for keeping that section accurate. Without content ownership, no governance model holds up over time.
SharePoint has a capable search engine, but its effectiveness depends almost entirely on how content is structured and tagged. A common mistake is to rely on filename search alone, which works when employees know exactly what they are looking for but fails completely when they are browsing or using general terms.
Metadata, the descriptive tags assigned to documents and pages, is what makes SharePoint search genuinely useful. When a policy document is tagged with its department, document type, effective date, and audience, it surfaces correctly when employees search for related terms rather than the exact filename.
For most intranets, a few metadata fields go a long way: content type (policy, guide, form, announcement), department, audience (all staff, managers, specific teams), and status (current, under review, archived). These tags also make it possible to build filtered views, news rollups, and audience-targeted content without manual intervention.
Microsoft Search, which spans SharePoint, Teams, Outlook, and OneDrive, also benefits from this structure. When content is well-tagged and properly published, employees searching from any Microsoft 365 entry point can find intranet content without having to know where it lives.
Permissions in SharePoint can be managed at the site, library, or individual item level. For intranet purposes, the cleanest approach is to keep permissions as simple as possible; site-level access controls are far easier to manage than item-level exceptions scattered across dozens of libraries.
A typical intranet uses three permission tiers:
• Visitors (read-only): most employees for most content
• Members (contributors): department owners and content editors who can publish and update pages
• Owners (full control): SharePoint admins and intranet administrators
Sensitive content, executive compensation documents, pre-announcement communications, and HR case files should reside on separate, tightly controlled sites rather than be buried within the main intranet with item-level restrictions. Mixing sensitive and public content on the same site creates both a security risk and a maintenance headache.
Governance also covers who can create new sites. Without a clear provisioning process, SharePoint environments tend to sprawl; dozens of team sites appear with no consistent naming, no connection to the hub, and no content owners. Establishing a simple site creation policy (a request process, a naming convention, and a default permission structure) prevents this accumulation before it starts.
One of the more underused capabilities of the modern SharePoint intranet is audience targeting, the ability to surface different content to different groups of employees based on their department, role, location, or Microsoft 365 group membership.
Audience targeting means a nurse in a healthcare organization sees content from the clinical operations team, while a finance manager sees announcements from the CFO's office. Both land on the same intranet homepage, but the news, quick links, and department highlights each employee sees are relevant to their work.
This is particularly valuable for organizations with diverse workforce populations; frontline workers, knowledge workers, remote teams, and field staff all have different information needs. SharePoint's audience targeting works in combination with metadata and Microsoft Entra ID group membership, and it does not require custom development.
Microsoft Viva Connections extends this personalization into Teams, surfacing intranet news, announcements, and tools within the employee's Microsoft Teams environment, meeting them where they already spend their day. To stay ahead of emerging capabilities, see Calance's guide to AI in SharePoint transforming team collaboration, which covers how AI features are reshaping content delivery and search on the modern SharePoint intranet.
Even a well-designed intranet does not adopt itself. Employees need to know it exists, understand why it is useful, and experience early value before they build a habit of returning to it.
Change management for an intranet launch typically involves three phases:
Involve employees early. Run focus groups or surveys to understand what they want from the intranet. Share previews with department representatives. Build anticipation by communicating what is coming and what problem it solves.
Make the launch visible. A company-wide announcement from leadership carries more weight than an IT email. Consider a short walkthrough video, a live demonstration at an all-hands meeting, or a simple visual guide to key sections. Make it clear where employees should go with questions or feedback.
Track usage and respond to it. SharePoint provides site usage analytics, page views, unique visitors, popular content, and device breakdown. Use these metrics to understand what employees are actually using and what sections need more attention. Set up a regular review cadence: monthly for the first quarter, then quarterly.
Intranet champions, employees in each department who are enthusiastic about the platform and can answer peer questions, accelerate adoption more than any formal training program. Identifying and empowering these people early pays dividends for months after launch. Launch is not the finish line. An intranet that is not actively maintained regresses to an outdated repository within twelve months.
The intranet is a living platform. Content gets outdated. Business priorities shift. New departments form, and existing teams reorganize. The navigation that made sense at launch may need adjustment once real usage patterns emerge.
A basic ongoing maintenance structure covers four areas:
• Content reviews: department owners review and refresh their pages on a set schedule, quarterly for most content, annually for policies
• Architecture reviews: revisit navigation and hub structure at least once per year to reflect organizational changes
• Governance audits: check for orphaned sites, unused libraries, and permission drift every six months
• Platform updates: Microsoft regularly releases new SharePoint features, web parts, integration options, and Viva capabilities that may improve the intranet without major reconstruction
Organizations with dedicated Microsoft 365 administrators can handle much of this internally. Those without that internal capacity often find it more practical to work with a SharePoint support partner on an ongoing basis rather than treating the intranet as a one-time project.
Before going live, verify each of the following:
✓ Business purpose and success criteria are documented and agreed upon
✓ Hub site, communication sites, and team site structure are planned and built
✓ Primary navigation reflects employee tasks, not internal org structure
✓ Each major content section has a named owner and a review schedule
✓ Metadata and content types are configured for search
✓ Permissions are set at the site level with a clear access control model
✓ Sensitive content is housed on appropriately restricted sites
✓ Mobile experience has been tested on at least two device types
✓ Microsoft 365 integration points (Teams, Viva, OneDrive) are configured
✓ Audience targeting is applied to homepage news and quick links where relevant
✓ Analytics are enabled, and a review cadence is in place
✓ Launch communications and champion network are ready
Some organizations have the internal capacity to plan, build, and maintain a SharePoint intranet on their own. Many do not - particularly mid-market companies where the Microsoft 365 admin team is stretched across multiple priorities, or enterprise teams where the intranet spans dozens of departments and multiple geographies.
Common signs that outside expertise would accelerate the project:
• The organization has an existing SharePoint intranet that employees have stopped using, and there is no clear plan to fix it
• The Microsoft 365 team can manage the platform but lacks intranet information architecture or UX experience
● The project scope involves migrating content from an older SharePoint version, a legacy intranet, or a file server. Calance's step-by-step SharePoint migration guide covers how to approach migrations from older SharePoint environments with precision.
• There are integration requirements involving Teams, Viva, Power Automate, or third-party systems
• Leadership wants the intranet live within a defined timeline and cannot afford a prolonged internal build
Calance works with organizations on exactly these challenges, from intranet discovery and architecture planning through site build, content migration, governance setup, and ongoing SharePoint consulting services. The scope of the engagement varies by organization: some need a full intranet build from scratch, while others need a targeted modernization of an existing environment. Either way, the approach starts with understanding what the organization needs the intranet to do before any configuration begins.
The organizations with intranets that employees actually use are not the ones that spent the most on custom development or third-party overlays. They are the ones who treated the intranet as a business problem, spent time understanding what employees needed, planned the architecture before building it, kept content ownership clear, and continued to manage the platform after launch.
SharePoint provides a strong foundation for all of this. It is already part of most Microsoft 365 subscriptions. It connects naturally to Teams, Outlook, OneDrive, and the broader Microsoft ecosystem. And it scales from a 20-person company with a single hub site to an enterprise with hundreds of teams and department sites organized across regional hubs. For a full overview of what Calance can offer, visit our SharePoint consulting services solutions page.
The platform is capable. The work is in planning, governance, and ongoing ownership. That is where the difference between an intranet that gets used and one that gets abandoned is actually made. If your organization is planning a new intranet or looking to modernize an existing one, Calance's SharePoint Intranet Services team is available to help you structure the right approach for your environment and your employees.