Guide SharePoint Intranet · Chapter 1

    The intranet in Microsoft 365 at a glance.

    The home site lives in SharePoint and opens in Teams, news reaches every person by audience, and documents and search run in the same tenant as the work itself.

    As of: October 2026 · Editor: Marcel Haas

    • SharePoint Online
    • SharePoint app in Teams
    • Microsoft Search
    • Viva Engage
    • Entra ID
    • Microsoft Purview

    Stack map

    The map of the intranet.

    For every block: what it does, who uses and maintains it, how it is bought, where it runs and which chapter goes deeper.

    • SharePoint
    • Teams and Viva
    • Across Microsoft 365

    Entry

    SharePoint

    Home site

    The front door of the intranet: organisation news, global navigation in the app bar, search across every hub.

    Who uses and maintains it
    Every employee; maintained by the communications team
    How it is bought
    In SharePoint Online, part of the common Microsoft 365 plans
    Where it runs
    SharePoint Online in your tenant
    Teams and Viva

    SharePoint app in Teams

    Shows dashboard, news and resources of the home site in Teams, on the desktop and on the phone; the former Viva Connections.

    Who uses and maintains it
    Every employee, with or without a desk
    How it is bought
    With the home site; several experiences for different audiences need a Viva licence
    Where it runs
    Teams, on the home site
    SharePoint

    Hub sites

    Bundle the sites of a division with shared navigation, design and search scope; permissions stay per site.

    Who uses and maintains it
    Divisions, locations and plants
    How it is bought
    In SharePoint Online
    Where it runs
    SharePoint Online

    Content

    SharePoint

    News

    Posts with audiences from Entra groups, page approval before publishing, reader counts afterwards.

    Who uses and maintains it
    Communications team and divisional editors
    How it is bought
    In SharePoint Online; advanced news analytics with Viva
    Where it runs
    Communication sites and hubs
    SharePoint

    Pages

    Assemble directives, events, people and documents from web parts, one version per national language.

    Who uses and maintains it
    Editors and site owners
    How it is bought
    In SharePoint Online; custom web parts with the SharePoint Framework
    Where it runs
    Modern sites
    SharePoint

    Documents and libraries

    Directives, regulations and forms with version, owner and review date; OneDrive for drafts.

    Who uses and maintains it
    Everyone who files documents; an owner per library
    How it is bought
    Storage pool per tenant, additional storage as an add-on
    Where it runs
    SharePoint Online and OneDrive
    Across Microsoft 365

    Lists

    Small structured data such as requests, dates or registers, with forms and views.

    Who uses and maintains it
    Business teams
    How it is bought
    In SharePoint Online and Microsoft Lists
    Where it runs
    Your sites

    Knowledge

    Across Microsoft 365

    Microsoft Search

    Finds pages, documents and people with the rights of the person searching; verticals and bookmarks steer the results.

    Who uses and maintains it
    Every employee
    How it is bought
    In Microsoft 365
    Where it runs
    Microsoft 365
    Across Microsoft 365

    People and profile card

    Responsibilities, deputies, locations and teams from Entra ID, on every card and in every search.

    Who uses and maintains it
    Everyone; maintained by HR and IT
    How it is bought
    In Microsoft 365; custom fields through Microsoft Graph
    Where it runs
    Entra ID and Microsoft 365
    Across Microsoft 365

    Copilot and agents in SharePoint

    Answers from intranet content with sources, drafting pages and sites, agents per site for selected sources.

    Who uses and maintains it
    Employees with a Copilot licence
    How it is bought
    Everyday features in the Copilot licence, advanced work through Copilot Credits
    Where it runs
    Your tenant, with the rights of the person asking
    Teams and Viva

    Viva Engage and Loop

    Conversation and questions in communities, Loop for working pages that travel along into Teams and Outlook.

    Who uses and maintains it
    Teams and communities
    How it is bought
    Viva Engage in Microsoft 365, Loop in the common plans
    Where it runs
    Teams; Loop workspaces in SharePoint Embedded

    Foundation

    Across Microsoft 365

    Entra ID and groups

    One identity per person, groups for access and audiences, guests through B2B, Conditional Access.

    Who uses and maintains it
    Your IT
    How it is bought
    In Microsoft 365; naming and expiry policies for groups with Entra ID P1
    Where it runs
    Your tenant
    Across Microsoft 365

    Purview

    Sensitivity labels for sites and documents, retention, loss prevention, audit.

    Who uses and maintains it
    Your IT and your data protection officer
    How it is bought
    In the Microsoft 365 plans, some features with E5 or an add-on
    Where it runs
    Your tenant
    SharePoint

    Admin center and Advanced Management

    Home site, hubs, sharing levels, policies for ownership and inactive sites, sharing reports, site access reviews.

    Who uses and maintains it
    Your IT
    How it is bought
    Admin center included; Advanced Management with one Copilot licence or as an add-on
    Where it runs
    Your tenant
    01

    The front door is where the work begins.

    Tuesday morning, start of shift in Biel: the shift lead opens Teams on her phone, and the SharePoint app shows her the news on the new parking rule, the shift plan as a card and the directive behind it. The same start page opens at the desk in the browser as the home site, with organisation news, the global navigation in the app bar and a search across the whole intranet. Behind it, hub sites bundle the sites of a division, a location or a plant with shared navigation, shared design and their own search scope; when a department moves, its site changes hub and every address stays the same. The Teams app is the former Viva Connections under a new name, and it takes over news, navigation and branding from the home site.

    02

    News, pages and documents are the content, audiences distribute it.

    The communications team writes a news post on the plants hub and picks the Entra groups of Thun and Biel as its audience; the news web parts on the home site, the hubs and the Teams app show the post to exactly these employees, and everyone else keeps seeing what is meant for them. Pages assemble the intranet from web parts, for highlighted content, quick links, events, people and documents, one version per national language. Communication sites carry information for many readers, team sites the working documents of one team with its Microsoft 365 group behind it. Directives, regulations and forms sit in libraries with a version, an owner and a review date; drafts stay in OneDrive until they are published, and small structured data such as requests or registers sits in lists.

    03

    Search, people and Copilot turn content into knowledge.

    A week later an employee searches for the shift rule: in the Directives vertical the new directive sits at the top, in the News vertical the post about it, and a bookmark brings the right form to the top for the term expenses. Search filters every result by the rights of the person searching. Whoever points at a name sees the profile card with role, department, location and deputy from Entra ID. Copilot in SharePoint answers the question when the new shift rule applies from the post and the directive, cites both as sources and sees only what the person may open herself; site owners build agents from it for selected sites and libraries, such as an HR agent for directives and regulations. Viva Engage carries the conversation in communities, Loop the working pages that travel along into Teams and Outlook.

    04

    The foundation belongs to your IT: groups, labels, admin center.

    Beneath all the content sits what your IT runs anyway. Groups in Entra ID carry permissions and audiences, guests join through B2B, Conditional Access decides from which devices. Sensitivity labels from Purview set privacy, guest access and external sharing per site, retention policies decide how long a version stays. Home site, hubs and sharing levels are created in the SharePoint admin center; SharePoint Advanced Management adds policies for ownership and inactive sites, reports on sharing and site access reviews, unlocked as soon as one person in the tenant holds a Copilot licence. This layer stays in place when you rebuild content, and it decides what Copilot and agents may read later.

    05

    Editors, site owners, IT and data protection share the work.

    The communications team owns the start page and the organisation news and runs the editorial plan; every divisional editorial team maintains its own pages, news and directives. Site owners, at least two per site, decide on members, guests and sharing and confirm them regularly. Your IT runs the foundation: groups, labels, admin center, reports. The data protection officer approves guests, labels and the people directory. The following chapters go deeper per role, from structure through editorial work and documents to permissions, migration, cost, governance and operations.

    What you decide.

    Where does the intranet start for your employees: in Teams, in the browser or on the phone?

    Options

    1. 1In Teams with the SharePoint app, the browser as the second way in
    2. 2In the browser on the home site, the Teams app follows later
    3. 3Both from day one, on the same home site

    Our recommendation: Both from day one, because the SharePoint app in Teams runs on the home site anyway and asks for no second set of content. An organisation whose workforce works in a plant, in care or in sales without a desk sets up the dashboard of the Teams app first, with shift plan, payslip and training, because that is where the intranet reaches these employees on the phone. An organisation that mostly works at a desk starts with the home site in the browser and switches the app on in Teams once the navigation stands.

    What we advise against: An intranet that lives only in the browser while the work happens in Teams: the news then never reaches part of the workforce.

    How many sites does the build start with?

    Options

    1. 1One home site and one division whose editors are ready
    2. 2Home site plus one hub per directorate, all at once
    3. 3The old intranet rebuilt page by page as sites

    Our recommendation: With the home site and one division whose editors are ready and bring real news, directives and contacts. Template, navigation and audiences take shape there, and every further division adopts them afterwards. Hubs come when a division has several sites that need shared navigation and their own search scope, such as a plant with quality, maintenance and logistics.

    What we advise against: Rebuilding the old intranet page by page. What your owners do not mark as current goes to the archive, and the new structure follows how people work today.

    Who owns the overview of the intranet?

    Options

    1. 1Your IT owns the foundation, the divisions own their content
    2. 2The communications team owns start page, news and editorial plan, IT the foundation
    3. 3A partner maintains the overview with you

    Our recommendation: The communications team owns the start page, the organisation news and the editorial plan, every division its sites with two named owners, your IT the foundation of groups, labels and admin center, and the data protection officer approves guests and labels. Every site carries its owner, every document an accountable person and a review date. We maintain the overview with you for as long as you want, and hand it over so that your editors and your IT carry it on.

    What we advise against: An intranet that belongs to IT alone. Content stays current only when the people responsible maintain it themselves.

    Status and sources.

    As of: October 2026

    • As of 25 September 2026

      Viva Connections is now the SharePoint app in Teams.

      The home page in Teams continues to run on the SharePoint home site, now under the name SharePoint app in Teams. Administrators create home sites directly in the SharePoint admin center, and the Announcements web part no longer needs an extra Viva licence. The change rolled out from May to the end of June 2026.

      Source: Microsoft Learn: Home site updates
    • As of 25 September 2026

      Copilot in SharePoint is generally available from 30 September 2026.

      Copilot answers questions from SharePoint content and creates pages, sites, files and simple approvals. Everyday use is included in the Microsoft Copilot licence; large-scale work such as reviewing whole libraries is billed in Copilot Credits.

      Source: Microsoft Learn: Get started with Copilot in SharePoint
    • As of 30 June 2026

      SharePoint Advanced Management with a single Copilot licence.

      As soon as one person in the tenant holds a Microsoft Copilot licence, oversharing reports, policies for inactive sites, restricted content discovery and site access reviews become available. Some features still need the SharePoint Advanced Management Plan 1 add-on.

      Source: Microsoft Learn: SharePoint Advanced Management prerequisites

    Frequently asked questions.

    Do we need additional software for the intranet?

    No. SharePoint Online and the SharePoint app in Teams are part of the common Microsoft 365 plans, as are search, the profile card and Viva Engage in its basic form. A check of your plan is only worthwhile if you want features from the Viva suite, SharePoint Advanced Management beyond what the Copilot licence unlocks, or Copilot itself; what applies to your plan is covered in the chapter on licences and cost.

    What is the difference between a communication site and a team site?

    The communication site informs many readers without a group behind it: start page, divisional pages, directives, news. The team site belongs to a Microsoft 365 group and therefore to a team in Teams; that is where the working documents, channels and Planner of one team live. Intranet pages point to team sites, but only members see their content. Which content belongs where is covered in the chapter on structure and navigation.

    Where do the documents linked from the intranet live?

    In libraries of the site they belong to: directives in the library of the communication site of the division, working documents in the team site, personal drafts in OneDrive. A link in the intranet points to that place, and the permission of the library decides who opens the document. We avoid copies in the intranet so that search finds one current version.

    Does the intranet reach employees without a desk?

    Yes, through the SharePoint app in Teams on the phone. The dashboard shows cards for the shift plan, the payslip or the next training, news appears by audience, and the sign-in is the same as at the desk. Every person needs an account in Entra ID; how frontline licences and devices fit in, we clarify for your plan.

    What does Copilot do in the intranet that search does not?

    Search returns results, Copilot writes an answer from the results and cites the sources. Both see only what the person asking may open. Copilot in SharePoint also drafts pages, sites and simple approvals, and site owners build agents for selected sources. Everyday features come with the Copilot licence, large-scale work such as reviewing whole libraries is billed in Copilot Credits.

    Who decides which news appears on the start page?

    The communications team, through page approval: a divisional editor writes the post on their hub, the head of communications checks text, audience and links and approves. The news web part of the home site pulls the post from the hub and shows it to the chosen audience. Page analytics then show how many people read it and through which channel.

    Next chapter · Chapter 2

    How hubs, sites and Teams structure an intranet.

    Where in the intranet does which content live, and how does a person find the way?