Guide SharePoint Intranet · Chapter 9

    Who does what, so that the intranet stays alive.

    Champions carry the launch into the divisions, an editorial team keeps news and pages current, site owners review access, and reports show what is read.

    As of: October 2026 · Editor: Marcel Haas

    • Champions
    • Communication calendar
    • Training by role
    • Editorial meeting
    • Usage reports
    • Support & Operations
    01

    Before the launch stand one goal per division and one data rule for all.

    The production floor of a food manufacturer wants shift plans and directives on the phone so that the notice board can go; the HR department wants forms and contacts in one place. Sentences like these, one per division, are the adoption plan: which tasks will run in the intranet from now on and how the division head will notice it in everyday work. One person from the management team backs the launch and says so in the first news post. With your data protection office and, where there is one, the staff representation we set the data rule beforehand: which usage data is evaluated at which granularity, per division and never per person, who sees the figures and how long they are kept. The rule stands before the first report is pulled, and it applies to the editors as to IT. What the divisions want to achieve also decides what the editors start with on the switch date: for production it is the shift plans, not the mission statement page.

    02

    Champions carry the launch into the divisions.

    In every division or at every location one person starts ahead of the others: she knows the home site, knows where the directives live and answers her colleagues' questions in the division's channel or at the screen during the break, not by ticket. Champions have a role description, time their managers explicitly make available, a channel of their own among themselves and a fixed exchange with the project lead, in which feedback from the divisions turns into measures: a missing link, a term search does not know, an audience a message did not reach. The right champions are rarely the most technically skilled; they are the people their colleagues ask anyway. After the launch the network stays and accompanies the further divisions, which we no longer accompany ourselves; the handover is done when a champion brings a new division to the start without us.

    03

    The launch is a date, with communication before and after.

    The communication calendar sets who sends which message to whom and when: the announcement by the management team, the preview for the champions, the invitation to the training, the message on the switch date with what changes, and the reminder afterwards with the most frequent questions. On the switch date the SharePoint app in Teams opens the new home site for everyone, a town hall in Teams shows it to the divisions, and the old intranet shows only one page with the link before it goes off, as the chapter on migration describes. In the first weeks champions and editors sit down weekly, read the questions from the channels and the searches without results and fix what is missing: a directive without an audience, a term that needs a bookmark, a page too long for the phone. What nobody finds in this time, nobody finds later either; which is why the first weeks belong to the project and not to operations.

    04

    Training happens by role, on real tasks.

    The editors learn on their own news: create a post with an audience, build a page from the template, start the approval, set the review date, read the page's statistics. Site owners learn to manage members and guests, to close a site access review, to attest their site and to create a library with columns. Everyone else learns in short units within the division where the home site sits in Teams, how the search for directives and people works and what the intranet looks like on the phone; with Copilot licences a prompt-a-thon is added, in which the division practises on tasks of its own. Quick guides and videos from every session land on the learning site, a site of the intranet that your champions keep maintaining. Microsoft provides material for the rollout, a Success Kit, a Launch Day kit and a scenario library by industry and role; we take from it what fits your divisions and translate it into your terms.

    05

    After the launch the editorial meeting takes over.

    Once a month the editors sit down together: the editorial calendar for the coming weeks, the pages whose review date is due, the news hardly anyone opened, and the terms that stay without results in search. Every page has a person in charge and a review date, and a list shows the editors what is due; whoever no longer needs a page withdraws it, and it moves to the site's archive. Site owners have duties of their own: the access review when the report triggers it, the attestation of their site on the fixed rhythm, guests who leave after the project ends. Once a year communications, IT and the division heads check structure and navigation against the areas of work: which hubs have grown, which site has outlived its purpose, which terms in the mega menu nobody understands any more? The chapter on structure and navigation has the questions for that; the yearly round asks them again and records what changes.

    06

    Reports show what is read and what is not found.

    The usage reports in the Microsoft 365 admin center show how many people use SharePoint, Teams and the home site, over periods you choose; the names of people, groups and sites are concealed by default, and whoever shows them changes an organisation setting that is recorded in the audit log. The site analytics of a site show the editors which news is read and which pages are skipped; the query analytics in the admin center list searches without results and searches that were abandoned, and every gap becomes a bookmark, an acronym, a column or a share. With Copilot licences in the tenant, the Copilot Dashboard in Viva Insights shows whether the editors actually use Copilot in SharePoint, with no licence needed for those viewing it. The usage tracker sums this up per division and shows where the rollout is holding and where a second session helps. The data rule from the beginning decides what is in these reports and who reads them.

    07

    After the handover an operation remains, and the next step is called agents.

    After the handover everyday work sits with your editors, your site owners and your IT; what remains are incidents, changes and the questions nobody in the organisation can answer. Our Support & Operations team takes them in through a portal, with agreed response times, keeps the operations manual current and reads the message center in which Microsoft announces changes, assesses each one for your intranet and tells the editors beforehand what will change. A quarterly meeting brings tickets, storage, licences and the reports from the chapter on governance and security to one table. The next step comes from the questions in the channels: if the editors answer the same questions about directives every day, the site gets an agent with chosen sources; a project team gets, with the Channel Agent, an agent in its channel that knows posts, files and meetings, assigns tasks and files status reports, currently in preview. How agents take shape beyond the intranet and who accompanies them in operation is in the Microsoft AI/SI guide.

    What you decide.

    Launch for everyone on one date or division by division?

    Options

    1. 1Everything for everyone on one date
    2. 2Division by division, with a pilot division first
    3. 3The home site for everyone on the date, the divisions' content in waves

    Our recommendation: The home site with news, directory and search for everyone on one date, because it is the reason a person opens the intranet, and the divisions' content in waves, starting with the division whose editors are ready and whose goal is clearest. Every wave has its champion, its training and its message in the communication calendar. A single date for everything demands that every editorial team is finished on the same day; division by division without a shared home site leaves the others waiting until it is their turn.

    What we advise against: Launching all divisions on the same day with half-filled sites: the first search finds placeholders, and the second search never happens.

    Who trains: in groups on your own content, through the learning site or through the champions?

    Options

    1. 1Small groups on their own news, pages and sites
    2. 2The learning site with quick guides and videos for everyone
    3. 3The champions in the division, with the learning site as the reference

    Our recommendation: Editors and site owners in small groups on their own content, because afterwards they have to be able to do something only they do; everyone else in short units in the division through the champions, with the learning site as the reference afterwards. The learning site alone reaches those who search; the champions reach those who would not ask. A prompt-a-thon adds to the units where Copilot licences have been assigned.

    What we advise against: One webinar for all employees with a recording on the learning site and nothing else: the editors do not learn their approval, and production does not see its shift plans.

    Evaluate usage per division, per person or not at all?

    Options

    1. 1Per division, with concealed names and a minimum group size
    2. 2Per person, to approach the stragglers
    3. 3Not at all, the champions' feedback is enough

    Our recommendation: Per division, with concealed names, a minimum group size and a data rule your data protection office has approved. That way the project lead sees where the rollout is holding and where a second session helps, without any person being judged. The champions' feedback comes on top but does not replace the figures, because it does not reach the quiet ones. A per-person evaluation serves no purpose in a rollout that a conversation in the division does not serve better.

    What we advise against: Showing names to find employees who do not open the intranet: the setting is in the audit log, and the trust in the reports is gone.

    Operations in-house, with a support contract or mixed?

    Options

    1. 1Everything in-house: editors, site owners and IT
    2. 2A support contract for incidents, changes and the message center
    3. 3Mixed: editors and ownership in-house, technology under the contract

    Our recommendation: Editors and site ownership always stay in-house, because they know your content and your divisions. Incidents, changes from the message center, policies and restores go into a contract when your IT is small or SharePoint is not its focus; they stay in-house when one person has the time and the roles for them. Mixed is the most common case: your IT runs Entra and the devices, the contract covers SharePoint, Teams and the policies, and a quarterly meeting keeps both sides together.

    What we advise against: No named place for incidents after the handover: the first question about a missing document lands with the editor, who cannot solve it.

    Status and sources.

    As of: October 2026

    • As of 28 August 2026

      Usage reports conceal names by default.

      The usage reports in the Microsoft 365 admin center show use of Teams, SharePoint, OneDrive, Copilot, Copilot Chat and agents over 7, 30, 90 or 180 days. User, group and site names are concealed by default; showing them means changing an organisation setting, and that change is recorded in the Microsoft Purview audit log.

      Source: Microsoft Learn: Usage reports in the Microsoft 365 admin center
    • As of 4 June 2026

      Query analytics shows searches with no result.

      In the Microsoft 365 admin center, query analytics compares searches with no result against searches where people clicked or abandoned, and lists the most frequent terms. The list of top no-result searches now appears only in the old view. It covers Microsoft365.com, the SharePoint start page and SharePoint sites; terms used by five or fewer people stay hidden.

      Source: Microsoft Learn: Microsoft Search usage report, queries
    • As of 29 September 2026

      Viewing the Copilot Dashboard needs no extra licence.

      The Microsoft Copilot Dashboard in Viva Insights is available to Microsoft 365 customers with a business or enterprise subscription, with no paid Viva Insights or Copilot licence needed to view it. From one Copilot licence in the tenant it shows adoption and impact, including Copilot Chat; from 50 Copilot licences it adds agent insights, benchmarks, surveys and views for managers. Groups below the minimum group size are not shown.

      Source: Microsoft Learn: Microsoft Copilot Dashboard
    • As of 24 March 2026

      Microsoft Adoption provides material for the Copilot rollout.

      Microsoft's Copilot adoption and onboarding guide points to the Microsoft Adoption site: a Success Kit for user enablement and technical readiness, a Launch Day kit for the start, a scenario library with success measures by industry and role, and instructor-led QuickStart training sessions.

      Source: Microsoft Learn: Copilot adoption and onboarding guide
    • As of 15 April 2026

      Message center: major changes at least 30 days in advance.

      Microsoft announces changes to Microsoft 365 in the admin center's message center, grouped into plan for change, stay informed and prevent or fix issues. Major updates come with at least 30 days' notice. Anyone who reads and assesses the message center does not experience retirements and new defaults as a surprise.

      Source: Microsoft Learn: Message center
    • As of 18 August 2026

      Channel Agent: one agent per Teams channel, in preview.

      In the public preview, a channel gets its own agent that uses posts, files in the channel's site and meetings as knowledge, answers questions, assigns tasks and stores status reports as a Loop file in the channel folder. It does not use files the person asking cannot open. Private channels and channels with external users are not supported yet.

      Source: Microsoft Learn: Set up Channel Agent in Microsoft Teams

    Frequently asked questions.

    What happens to the champions network after the launch?

    It stays. The champions keep their channel, their role description and the fixed exchange with the function that owns the intranet, usually communications. They bring the next divisions to the start, collect the feedback for the editorial meeting and are the first to explain a change from the message center in their division. Whoever gives up the role hands it to a successor from their own division; the project lead keeps the list.

    Do we need a town hall in Teams for the launch?

    Not necessarily, but it helps: a person from the management team shows the home site, the champions show the directives and the search, and the questions from the chat land straight with the editors. For organisations that work in shifts, a recording on the learning site replaces the event for everyone who cannot attend; whether your Teams plan allows events of the size you need is in the chapter on licences and cost. The message on the home site on the switch date is needed in every case.

    Which reports show whether the intranet is read?

    The usage reports in the Microsoft 365 admin center for SharePoint, Teams and the home site, with concealed names; the site analytics of every site, which show the editors which news is opened and which pages are skipped; the query analytics for searches without results; and, with Copilot licences, the Copilot Dashboard in Viva Insights. Which of these are evaluated per division and who sees them is set by the data rule your data protection office approved before the launch.

    What do we do with a search that returns nothing?

    Every gap gets a measure, and the editorial meeting goes through the list: a term the organisation uses differently from the page becomes a bookmark or an acronym; a document nobody can find gets a column or lands in the right library; content that is missing goes on the editorial calendar; and a directive only part of the organisation finds usually has a share that is too narrow. Query analytics shows the most frequent terms; the champions know the rest from the channels.

    How often do the editors meet after the launch?

    Weekly with the champions in the first weeks, then once a month: editorial calendar, review dates due, unread news, searches without results. On top of that comes the big round once a year with IT and the division heads on structure and navigation. Whoever chairs the meeting owns the intranet as a product, usually communications; IT attends when a policy or a change from the message center is on the list.

    When is the right moment for the first agent on a site?

    When the editors keep answering the same questions about one library, the sharing of that site has been reviewed and the valid versions sit apart from the outdated ones. Then the site owner builds an agent from chosen sources with a Copilot licence, tests it with an authorised and an unauthorised account and shares it into the division's channel; everyone can use it once pay-as-you-go billing is set up. How the agent takes shape is in the chapter on documents and knowledge.

    Who looks after incidents after the handover?

    A named place that is written in the operations manual: your IT or our Support & Operations team with portal, response times and a quarterly meeting. Questions about content stay with the editors and the site owners, questions about use with the champions, and whatever goes beyond that, a flow that has stopped, a site that does not load, a change by Microsoft, goes as a ticket to the place that holds the contract. This split is settled before the handover, not at the first incident.

    To the guide

    SharePoint intranets explained, from Teams to the archive.

    The guide shows what home site, news, documents and search do in Microsoft 365, who maintains what and what your IT decides, with date and source.