Guide SharePoint Intranet · Chapter 7

    Intranet cost: which levers move the bill.

    SharePoint is part of every Microsoft 365 plan, storage is measured, and Copilot features, document processing and backup run on meters of their own.

    As of: October 2026 · Editor: Marcel Haas

    • Microsoft 365 plans
    • Storage quota
    • Pay-as-you-go billing
    • Copilot licence
    • Microsoft 365 Archive
    • SharePoint Embedded

    Cost levers

    Which meter, which lever.

    For every meter that moves the bill: what drives it and which lever you hold. Mechanics without figures; the amounts are in the proposal.

    1. 01

      Microsoft 365 plan per person

      What moves the meter: The number of people and the plan tier: SharePoint Online is in every plan; the tiers differ in the Purview functions, in Entra ID and in the ceiling on people, frontline plans cover employees without a desk.

      Your lever: Choose the plan by role, not by name: whoever only reads needs less than the editors; the comparison page walks through the check.

    2. 02

      Tenant storage quota

      What moves the meter: The base quota plus the share per licence against everything that fills sites: versions, Teams files, Loop workspaces, migrated project files; beyond that add-on storage in packs through the admin center.

      Your lever: Version limits per library, the scan before buying more, completed projects to the archive; add-on storage last.

    3. 03

      Microsoft 365 Archive

      What moves the meter: The archived volume on the cold storage tier and the reactivations; archived sites no longer take active quota.

      Your lever: Policies for inactive sites that archive at the end; only what stays for retention reasons and nobody opens any more.

    4. 04

      Document processing and eSignature

      What moves the meter: Processed receipts, pages opened up by text recognition and signature requests through the Azure subscription; until December 2026 a monthly no-charge allowance per tenant.

      Your lever: A pilot in one library with a budget and an alert; text recognition across a whole collection as a step of its own.

    5. 05

      Copilot licence per person

      What moves the meter: The number of licences; each brings Copilot in SharePoint, autofill columns, the creation of site agents and Copilot Search, the first in the tenant also the governance functions of SharePoint Advanced Management.

      Your lever: Editors and site owners first, further roles after the pilot by the usage report.

    6. 06

      Copilot Credits and agents by consumption

      What moves the meter: Large-scale work by Copilot in SharePoint, such as reviewing whole libraries, and the use of site agents by people without a licence through the Azure resource.

      Your lever: One agent per site with chosen sources, a budget on the Azure resource, read the usage after the first month.

    7. 07

      SharePoint Advanced Management Plan 1

      What moves the meter: The add-on per person for the functions that do not come with the first Copilot licence, such as restricted site creation by apps.

      Your lever: Start with the functions of the Copilot licence; Plan 1 only when a named function is missing.

    8. 08

      Microsoft 365 Backup

      What moves the meter: The protected volume of sites, OneDrive accounts and mailboxes and the recovery window of the policy, by consumption through the Azure subscription; the MOUNT10 backup by contract.

      Your lever: Protect the intranet sites and the libraries with evidence, choose the window per site class, practise the restore.

    9. 09

      SharePoint Embedded

      What moves the meter: Containers of business applications by storage and access through the Azure subscription; Loop workspaces count towards the organisation's storage quota.

      Your lever: Know which application creates containers; a Cloud Policy for Loop workspaces; look up the limits per container before deployment.

    10. 10

      Guests and external identities

      What moves the meter: External people who actually access in a month, counted by Entra; guests need no licence of your plan.

      Your lever: Guests per project site with an expiry date, shared channels for partner organisations, the owners' attestation removes whoever no longer takes part.

    11. 11

      People: migration, editors, operations

      What moves the meter: Inventory and waves of the migration, the hours of the editors and the site owners, champions in the first weeks, training and the support after the handover.

      Your lever: One division first, champions, a handover after which your editors and site owners carry on; the work stands in the proposal with roles and scope.

    As of October 2026, derived from the dated facts of this chapter. Storage units, the billing of Archive and eSignature after the allowance, the limits of SharePoint Embedded and the counting of external identities name the mechanism; we check them on the vendor's page before every proposal. The amounts are in the proposal and in the dated cost articles, never on this page.

    01

    SharePoint is in every plan, the differences sit next to it.

    At a fiduciary firm with Business licences the intranet runs on the same foundation as at a hospital with Enterprise plans: home site, news, audiences, libraries, search and the SharePoint app in Teams belong to every plan that includes SharePoint Online, and an intranet needs no additional software for them. The differences sit in the neighbours. Business plans have a ceiling on the number of people per tenant; Business Premium and the Enterprise plans bring Entra ID P1 for the naming rule and the expiry of groups, and the top Enterprise tier the Purview functions for auto-labelling, records and the review before deletion. For employees without a desk there are frontline plans, with which they read news and directives on the phone. Teams Enterprise, since April 2026 with features from Teams Premium, carries the town hall at the launch. Which plan fits which role is a question of tasks and not of names; the licence comparison page walks through that check, and the amounts are in the proposal with a date.

    02

    Storage is one pool for the whole tenant.

    In the SharePoint admin center a gauge shows how full the tenant's storage is: a base quota per organisation plus a share per licensed person, used jointly by every site, communication sites and team sites, the sites behind Teams channels and the Loop workspaces in SharePoint Embedded. OneDrive counts separately per person. What fills the pool is rarely the news: it is versions of drawings and presentations, project files from the migration and libraries whose owners have left the company. Once the pool is full, administration books add-on storage in packs through the Microsoft 365 admin center, billed on an ongoing basis. Before it comes to that, we check the version limits per library, the storage reports and the findings of the scan, and completed projects move with Microsoft 365 Archive to a cold storage tier that no longer takes active quota but has a meter of its own. The sites stay findable and come back with all their rights when someone needs them.

    03

    Pay-as-you-go services bill through an Azure subscription.

    Document processing for Microsoft 365, formerly Syntex, requires no licence per person: your administration connects the tenant to an Azure subscription, and every processed receipt, every page made searchable by text recognition and every signature request from SharePoint eSignature appears on that bill. Until December 2026 a monthly no-charge allowance applies per tenant, on which a pilot in the intake library runs without the meter being noticed; after that every unit counts. How eSignature is billed after the allowance we check on the vendor's page before every pilot. The agents on sites take the same route: creating one needs a Copilot licence, people without a licence can use it once pay-as-you-go billing through an Azure resource is set up, and large-scale work by Copilot in SharePoint, such as reviewing whole libraries, runs in Copilot Credits. In the Azure portal we set a budget with an alert for each of these meters before the first division starts.

    04

    A Copilot licence brings more than Copilot.

    The head of communications is the first person in the tenant to receive a Microsoft Copilot licence, and with it more changes than her own desk: Copilot in SharePoint drafts pages and summaries for her, she creates autofill columns that from then on fill every new file, for colleagues without a licence too, she builds the agent of the directives site, and in the Copilot app she searches with Copilot Search over the same index that everyone else keeps using by keyword. For administration the same first licence unlocks the governance functions of SharePoint Advanced Management: oversharing reports, policies for inactive sites, site access reviews and Restricted Content Discovery; some functions stay with the Plan 1 add-on. The Copilot Dashboard in Viva Insights can be read without a licence of one's own. For an intranet this means: the first licences belong to the editors and the site owners, not to every reader; whoever only reads has search, news and the site agents through pay-as-you-go billing.

    05

    SharePoint Embedded and guests have meters of their own.

    The Loop workspace in the project team's channel, the notes from Copilot Pages and the containers of a business application that stores its documents in SharePoint live in SharePoint Embedded: containers without a site, managed by your tenant and filled by an application through the Graph API. Loop workspaces count towards the organisation's storage quota; containers of third-party applications bill by consumption through an Azure subscription, with limits of their own per container, which we look up on the vendor's page before an application is deployed. Guests take up no licence of your plan: a partner who works on the project signs in with her own account through Entra ID. Entra counts external identities by the people who actually access in a month; whether and from which number that is charged to your Azure subscription we check on the vendor's page before the first partner portal. That is why guest access ends after a set period, and the owners' attestation removes whoever no longer takes part.

    06

    Storage Monster shows what fills the storage before you buy more.

    Storage Monster, the scan by CNEXT, only reads SharePoint and OneDrive: as a Cloud Scan through an app registration with read permissions in the Graph API or as a local scan with PowerShell, and it stores metadata, not content. The findings show which sites and libraries have long been untouched, which files carry several times their size as version history, where duplicate candidates sit and which file names look like credentials. The owners decide what stays, against your retention rules; the clean-up needs write permissions that your IT grants separately, an approval per measure and a log of every change. Scheduled scans, budgets per site and an alert on unusual growth keep an eye on the pool afterwards, owners receive their findings by email, and for service providers there is operation across several tenants. The price is in the proposal.

    07

    People cost more than licences, and their work has a name.

    The largest item in the bill for an intranet is on no licence list: it is people's hours. A migration needs an inventory, a target structure, waves with a pilot and a cutover day on which someone reconciles the exceptions; an editorial model needs editors in every division who plan news, look through pages before their review date and keep the look together; site owners review access and attest their sites; champions answer the questions in their own team in the first weeks; and after the handover there has to be a place that takes in incidents and sorts the changes from the message center. We name this work in the proposal as work, with roles and scope, so that division heads make the time available before the launch date is set. What of it stays with you and what we take on is in the chapters on migration and on rollout and operations.

    What you decide.

    Book add-on storage, limit versions or archive?

    Options

    1. 1Add-on storage in packs through the admin center
    2. 2Version limits per library and a clean-up by findings
    3. 3Completed projects to the cold tier with Microsoft 365 Archive

    Our recommendation: The scan and the version limits first, because they show what fills the pool and empty it without loss: versions above the limit, orphaned libraries, duplicates from the migration. Then the archive for completed projects that have to stay for retention reasons but nobody opens any more; they no longer take active quota and stay findable. Add-on storage last, for what is actively used and growing, and with a look at the report that says how fast.

    What we advise against: Booking add-on storage before anyone knows what fills the pool: the packs keep running, and the versions of the 2019 construction drawings grow along with them.

    Switch on document processing pay-as-you-go now or wait?

    Options

    1. 1Switch on now, with the allowance until December 2026 and a budget in Azure
    2. 2One pilot library only, the rest waits for the decision
    3. 3Wait until a division proves the need

    Our recommendation: Switch it on for a bounded pilot, usually the intake library with invoices or the contracts, with an Azure resource, a budget with an alert and a look at the bill after the first month. The allowance makes the pilot cheap, and the figures afterwards belong in the decision on which libraries follow. Text recognition across a whole migrated collection is a step of its own with a budget of its own, not a side effect of the pilot.

    What we advise against: Switching document processing on for the whole tenant and running a migrated collection through text recognition without a budget: the bill arrives with the first month after the allowance.

    Copilot licences for everyone, by role, or first for editors and site owners?

    Options

    1. 1One licence for every employee
    2. 2Licences by role, after a pilot
    3. 3Editors and site owners first, agents for everyone through pay-as-you-go billing

    Our recommendation: Editors and site owners first: they write with Copilot in SharePoint, create autofill columns and build the agents, and the first licence unlocks the governance functions for administration. Everyone else uses the site agents through pay-as-you-go billing and keyword search. Licences by role follow after the pilot, when the usage report shows which roles work daily with mail, documents and meetings. For an intranet alone, a licence for everyone is rarely the first step.

    What we advise against: Licensing every employee so that the intranet has Copilot: whoever only reads news does not need the licence, and the site agent answers them without it.

    SharePoint Advanced Management: Copilot licence enough, add Plan 1, or nothing?

    Options

    1. 1The functions that come with the first Copilot licence
    2. 2The Plan 1 add-on for the functions that stay with the add-on
    3. 3None for now, with the admin center's reports

    Our recommendation: Start with the functions that come with the first Copilot licence in the tenant: oversharing reports, policies for inactive sites, site access reviews, Restricted Content Discovery. That is enough for the preparation for Copilot and for the lifecycle of the sites. Plan 1 comes when a named function is missing, such as restricted site creation by apps, and then stands in the proposal by name. Without either, the admin center's reports and PowerShell remain, which is enough for a few sites.

    What we advise against: Booking Plan 1 for the whole tenant before a single function is missing that the Copilot licence does not already provide.

    Status and sources.

    As of: October 2026

    • As of 15 July 2026

      Until December 2026 a monthly no-charge allowance for document processing.

      Tenants that have set up pay-as-you-go billing receive, according to the allowance page, a monthly allowance per tenant until December 2026 for eSignature, autofill columns, prebuilt models and text recognition. The eSignature overview page still says June 2026; we check the current state before every pilot.

      Source: Microsoft Learn: Included capacity for document processing services
    • As of 31 August 2026

      Microsoft 365 Archive archives sites and individual files.

      Archived sites and files move to a cold storage tier within SharePoint and no longer count against the active storage quota. They stay findable through search, Content Search and eDiscovery, and a site keeps all its metadata and permissions when reactivated. Some apps cannot open archived files yet, such as Word and PowerPoint for the web; a reactivated file cannot be archived again for 120 days.

      Source: Microsoft Learn: Overview of Microsoft 365 Archive
    • 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
    • As of 18 August 2026

      Site agents: created with a Copilot licence, also used on a usage basis.

      Creating an agent for a site requires a Microsoft Copilot licence and the right to add files to the site. People without a licence can use it as soon as your organisation has set up pay-as-you-go billing through an Azure resource. The agents need no activation; they are available on every site a person has permissions for.

      Source: Microsoft Learn: Get started with agents in SharePoint
    • As of 11 September 2025

      SharePoint eSignature is available in Switzerland too.

      Microsoft offers eSignature worldwide through the Microsoft 365 public cloud, with the exception of Indonesia. The signatures are simple electronic signatures under eIDAS; external signers access the document as guests through Entra ID. Every step appears in the Microsoft Purview audit log, and signature requests can be tracked in the Approvals app in Teams.

      Source: Microsoft Learn: Overview of eSignature
    • As of 17 June 2026

      Loop workspaces in channels live in SharePoint Embedded.

      A shared Loop workspace in a Teams channel stores its content in its own SharePoint Embedded container, while Loop components in channel posts sit in the channel folder of the team's site. Both count towards your organisation's storage quota. Creating workspaces is controlled by a Cloud Policy, Loop components in chats and channels by a tenant-wide setting.

      Source: Microsoft Learn: Manage Loop in your organization
    • Since 1 April 2026

      Teams Enterprise includes features previously reserved for Teams Premium.

      Since 1 April 2026 some features from Teams Premium are included in Teams Enterprise; organisers with Teams Enterprise can run events with up to 10,000 view-only attendees. Teams Premium keeps advanced meeting protection, the Queues app, branding and the intelligence features.

      Source: Microsoft Learn: Plan for Teams events

    Frequently asked questions.

    Which items join the plan when we build an intranet?

    For the home site, news, audiences, libraries and search, none: they belong to every plan with SharePoint Online. What can join are add-on storage once the tenant's pool is full, the pay-as-you-go services through an Azure subscription, that is document processing, eSignature, Microsoft 365 Archive, Microsoft 365 Backup and the use of agents by people without a licence, Copilot licences for editors and site owners, and the SharePoint Advanced Management Plan 1 add-on if one of its functions is missing. The largest item remains the work: migration, editorial work, training and operations.

    What happens when the tenant's storage is full?

    Administration sees it coming in the SharePoint admin center, with the gauge of used storage and the reports per site. Once the pool is full, no new files can be saved in the sites until space is freed or add-on storage is booked. That is why we set version limits before the pool is full, check the findings of the scan and move completed projects to the archive; add-on storage is the last lever, not the first.

    Does document processing keep running when the allowance ends?

    Yes, on the same meter in the Azure subscription, then for every unit. The services do not switch off, the bill changes. That is why we set a budget with an alert in the Azure portal, read the bill after the first month together with the division and decide per library which processing is worth its price. Text recognition across a whole collection remains a step of its own with a budget of its own.

    Do all employees need a Copilot licence for the site agent to answer?

    No. The licence is needed by whoever creates the agent, usually a site owner or someone from the editorial team. Everyone who may see the site can use it once your organisation has set up pay-as-you-go billing through an Azure resource; the use then counts there. What a person without a licence does not have are Copilot in SharePoint for their own writing, Copilot Search and the creation of autofill columns; news, pages, documents and keyword search they have as before.

    Which meters end up on the Azure bill?

    Everything billed by consumption: document processing with eSignature, the use of site agents by people without a Copilot licence, Microsoft 365 Archive for archived content, Microsoft 365 Backup for the protected volume, the SharePoint Embedded containers a business application creates, and the external identities once Entra counts them above the base. The licences per person and the add-on storage, by contrast, are on the Microsoft 365 bill. A budget per meter with an alert is part of the setup.

    Does an archived site still cost storage?

    It no longer takes active storage quota, but it runs on the meter of Microsoft 365 Archive, which bills by archived volume. The site stays findable through search, Content Search and eDiscovery, and on reactivation metadata and permissions come back with it; a reactivated file cannot be archived again until a waiting period has passed. For projects nobody opens any more but which have to stay for retention reasons, this is the cheaper place than the active pool.

    How is Storage Monster billed?

    With a proposal by scope: which sites and OneDrive accounts are in the scan, whether the Cloud Scan through the Graph API or the local scan with PowerShell runs, and whether scheduled scans with budgets and growth alerts are added. The scan only reads; the clean-up needs write permissions that your IT grants separately, and every measure is approved and logged. What the clean-up frees up in storage is shown by the findings for your tenant, not by a promise in advance.

    Next chapter · Chapter 8

    Governance: how sites and data stay under control.

    How do sites and data stay under our control over the years?