Overview

The modern enterprise intranet built on SharePoint and Viva Connections serves as: the digital front door (company news, announcements, and organizational updates — the first thing employees see when they open their browser or Teams), the tool hub (quick links to: HR self-service, IT support, expense reporting, time tracking, and department-specific applications — one click from the intranet to any business tool), the knowledge center (policies, procedures, training materials, and organizational knowledge — searchable, current, and governed), and the social layer (Yammer/Viva Engage communities, employee recognition, and organizational announcements that build: culture and connection in hybrid/remote work environments). The intranet succeeds when: employees visit daily because it saves them time. It fails when: employees avoid it because the content is stale, the search doesn't work, and the navigation is confusing. The difference between success and failure is: content governance (every page has an owner who keeps it current), information architecture (content is organized logically and searchable), and personalization (each employee sees content relevant to their role, location, and department).

The intranet isn't a website project — it's an employee experience project. Technology is 30% of success. Content strategy (what gets published, by whom, how often) is 40%. Governance (keeping content current and relevant) is 30%. Skip any of the three, and the intranet becomes another abandoned internal website.

Architecture

Modern intranet architecture on SharePoint: home site (the organization's main intranet page — set as the SharePoint home site and surfaced in Teams via Viva Connections. Content: company news, leadership messages, quick links, and personalized content cards), hub sites (department-level intranets: HR Hub, IT Hub, Operations Hub — each with: department news, resources, and team links. Hub navigation provides: consistent experience across all department sites), communication sites (specific content areas: Company Policies, Benefits Center, Learning Hub, Project Showcase — each owned by a content team, each with: editorial calendar and review cycle), Viva Connections (the intranet in Teams — employees access intranet content without leaving Teams. Dashboard cards: personalized shortcuts, targeted news, and task notifications), and Copilot integration (employees ask: "what's the travel expense policy?" → Copilot searches intranet content and returns: the relevant policy page with a summary).

Content Strategy

Content that keeps employees coming back: company news (published 2-3x/week: leadership updates, project milestones, customer wins, and organizational changes — each with: headline, summary, and link to full article. Authored by: communications team), department news (published weekly per department: team updates, process changes, and resource announcements — authored by: department content owners), evergreen content (policies, procedures, benefits guides, and training materials — reviewed quarterly by content owners, with: last-reviewed date visible to users. Content older than 6 months without review: flagged for owner attention), targeted content (audience targeting: content shown to specific groups. New employees: onboarding resources. Managers: management tools and policies. Engineers: technical resources and lab access. Each role sees: relevant content without information overload), and interactive content (quick polls, feedback forms, event RSVPs — engagement mechanisms that make the intranet interactive, not just informational). Editorial calendar: 12-month plan showing: what content publishes when, who creates it, who reviews it, and what the target audience is.

Personalization

Personalization makes the intranet relevant: audience targeting (SharePoint audience targeting shows content to: specific M365 groups, departments, locations, or job roles. The finance team sees: finance news and tools. The manufacturing team sees: production schedules and safety alerts. Everyone sees: company-wide news and policies), Viva Connections dashboard (personalized cards: "Your upcoming trainings," "Your pending approvals," "Your team's news" — dynamic content based on the user's profile, role, and activity), search personalization (search results weighted by: the user's department, recent activity, and colleagues' behavior — "travel policy" returns: the current travel policy for the user's country, not a list of 15 travel policies from different entities), and multilingual (for global organizations: intranet content published in: the organization's primary languages. Machine translation for: content not manually translated. Users set: their preferred language — intranet displays: content in their language where available).

Governance

Intranet governance prevents content decay: content ownership (every page, every section, every resource has: a named owner responsible for: accuracy, freshness, and relevance. The owner receives: quarterly review reminders. Pages without owner review in 6 months: flagged in the governance dashboard), editorial board (monthly: communications team + department content owners review: upcoming content plan, stale content flagged for update, and new content requests. Quarterly: intranet analytics review — what's popular, what's unused, what's searched but not found), publication workflow (news articles: draft → editor review → approval → publish. Policy pages: draft → SME review → legal review → approval → publish. Updates to published content: change request → review → approval → update with version history), quality standards (every page includes: clear title, summary, owner, last-reviewed date, and relevant metadata. Images: compressed and alt-tagged. Links: validated quarterly — broken links flagged and fixed), and measurement (monthly: unique visitors, page views, search queries, and content engagement. Quarterly: user satisfaction survey. Pages with: declining traffic → content owner notified for refresh. Pages with: zero traffic for 90 days → review for retirement).

Measurement

MetricTargetMeasurement
Daily active users60%+ of employeesSharePoint analytics
Content freshness90%+ pages reviewed in last 6 monthsContent audit report
Search successUnder 5% abandoned searchesSearch analytics
User satisfaction4+ out of 5Quarterly survey
Mobile usage30%+ of total trafficViva Connections analytics

Implementation

1

Month 1-2: Design

Information architecture, content audit (what exists, what's missing, what's stale), design system (colors, templates, layouts), and content owner assignments.

2

Month 3-4: Build

Home site, hub sites, initial content pages, Viva Connections dashboard, and search configuration. Content migration from legacy intranet.

3

Month 5-6: Launch

Pilot with 100-200 users → feedback → refinement → full launch. Content owner training. Editorial calendar activated. Governance dashboard deployed.

Intranet Technology Comparison

PlatformBest ForStrengthLimitation
SharePoint + VivaMicrosoft-centric orgsM365 integration, Copilot, Teams deliveryDesign flexibility limited
StaffbaseFrontline-heavy orgsMobile-first, employee commsLimited document management
SimpplrEmployee experience focusAI-powered personalizationLess Microsoft integration
LumAppsGoogle Workspace orgsGoogle integrationNo M365 native integration
Custom (headless CMS)Design-driven orgsFull design controlNo M365 integration, high build cost

For Microsoft-centric organizations (M365, Teams, D365): SharePoint + Viva Connections is the clear choice — native integration with: Teams (intranet in Teams), Copilot (AI-powered search and content), and the entire M365 suite eliminates: the integration cost and user friction of a separate intranet platform. For organizations with: 50%+ frontline workers without M365 licenses: Staffbase or Simpplr may provide better: mobile reach and employee communication capabilities.

Intranet Content Governance: The Operating Model

The intranet content operating model: centralized editorial (the communications team manages: company-level news, executive communications, and organizational announcements. They maintain: brand consistency, editorial calendar, and publication quality), federated department content (each department has: 1-2 content contributors who publish: department news, team updates, and resources. Contributors are: trained on SharePoint modern pages, follow brand guidelines, and: participate in the monthly content review), content lifecycle (new content: editorial review → publish → quarterly freshness review → annual archive assessment. Each page includes: visible "last reviewed" date — employees trust content they can verify is current), and metrics-driven optimization (monthly analytics: top pages (invest more in these topics), declining pages (refresh or retire), search queries with no results (content gaps to fill), and bounce rate (pages that don't answer the user's question — redesign or restructure)). The operating model requires: 0.5-1 FTE for communications/editorial + 2-4 hours/month per department content contributor. This modest investment sustains: an intranet that 60%+ of employees visit daily — because the content is: current, relevant, and personalized.

Intranet for Hybrid and Remote Work

The hybrid workplace makes the intranet more critical — not less: the office intranet (in an office, information spreads through: hallway conversations, whiteboard sessions, and overhearing the team next door. These informal channels: don't exist for remote workers), the hybrid intranet (must provide: everything the office provides informally — company pulse (what's happening today?), team visibility (who's working on what?), social connection (celebrations, milestones, watercooler conversations), and tool access (one-click to every system from anywhere)), Viva Connections in Teams (the intranet delivered in Teams — where remote workers already spend their day. No separate browser tab, no separate login — the intranet lives: inside the tool they use most), asynchronous communication (news and announcements consumed on: the employee's schedule — not in: a live all-hands that remote workers in different timezones can't attend. The intranet is the permanent record of: every announcement, every policy change, and every organizational update — accessible anytime, anywhere), and digital culture (the intranet replaces: the physical office as the cultural anchor. Employee spotlights, team celebrations, and organizational values — published on the intranet, visible to: every employee regardless of location). For organizations with 30%+ remote workers: the intranet isn't optional — it's the only channel that reaches everyone consistently.

Modern Intranet Technology Stack

ComponentTechnologyPurpose
Content PlatformSharePoint OnlinePages, news, document libraries
CommunicationViva ConnectionsIntranet in Teams, mobile access
Employee ExperienceViva Engage (Yammer)Communities, social features
LearningViva LearningTraining content aggregation
InsightsViva InsightsWork patterns, wellbeing
Search & AIMicrosoft Search + CopilotUnified search, natural language Q&A
CustomizationSPFx web partsCustom components when needed

The modern intranet is not just SharePoint — it's an employee experience platform combining: SharePoint (content), Viva (engagement, learning, insights), Teams (communication), and Copilot (AI). This integrated approach means: the intranet isn't a separate destination employees must visit — it's embedded in the tools they already use (Teams, Outlook, mobile). Adoption improves because: the intranet comes to the employee instead of requiring the employee to go to the intranet.

Intranet Content Strategy

Content that drives daily intranet visits: must-visit content (information employees need regularly: PTO balance, pay stubs, expense submission, IT requests — self-service functions that replace: emailing HR or calling the help desk), need-to-know content (company news, policy updates, organizational changes — pushed to employees via: Viva Connections feed, Teams notifications, and email digest), want-to-know content (thought leadership, industry news, employee spotlights, event information — engaging content that builds: culture and community), and reference content (policies, procedures, templates, guides — well-organized, searchable, and current — the content that employees search for when they need an answer). Content ratio: 40% must-visit (drives daily use), 30% need-to-know (drives weekly visits), 20% reference (drives search traffic), 10% want-to-know (drives engagement and culture). The mistake: building an intranet that's 80% want-to-know (company news and employee spotlights) and 20% everything else — this creates: a nice-looking newsletter that nobody visits daily.

Intranet Launch Strategy

Launching the intranet to maximum adoption: soft launch (week 1-2) (launch to: 50-100 pilot users across departments. Collect: feedback on navigation, content findability, and mobile experience. Fix: critical issues before full launch), executive announcement (week 3) (CEO sends: company-wide announcement with: what the new intranet is, why it matters, and a personal endorsement. The CEO's endorsement matters: more than any training session), department rollout (week 3-4) (each department's content live, department leads send: specific communications about their department's intranet content and how it helps their team), training sessions (week 3-4) (30-minute sessions per: content creators (how to publish), site owners (how to govern), and all employees (how to find and use content). Sessions recorded for: future reference and new hire onboarding), gamification (month 1-2) (intranet scavenger hunt: "find these 5 items on the intranet and enter to win." Leaderboard for: department content engagement. Weekly prize for: most-clicked news article author — creating: initial engagement momentum), and feedback loop (ongoing) (visible "feedback" button on every page: "Was this helpful? What's missing?" Feedback reviewed weekly. Visible improvements based on feedback: demonstrate that the intranet team listens and acts — building trust and sustained engagement).

The Xylity Approach

We build SharePoint intranets with the employee-experience methodology — information architecture that makes content findable, content strategy that keeps it current, personalization that makes it relevant, and governance that prevents decay. Our Power Platform specialists deliver intranets that 60%+ of employees visit daily — because the intranet saves them time, keeps them informed, and connects them to every tool they need.

Continue building your understanding with these related resources from our consulting practice.

An Intranet 60% of Employees Visit Daily

Information architecture, content strategy, personalization, governance. SharePoint intranet that employees actually use — because it saves them time.

Start Your Intranet Project →