Guide SharePoint Intranet · Reference

    Intranet terms, explained with SharePoint and Teams.

    Every entry from audience to version says what a building block does, how it is protected and where it lives in SharePoint or Teams, and leads to the right chapter.

    As of: October 2026 · Editor: Marcel Haas

    Terms

    From A to Z.

    Search by name, product or keyword, or jump to a letter. Every entry leads to the chapter that goes deeper.

    80 terms in this selection

    Chapter 8 · Governance and security

    Admin roles

    SharePoint, Teams and group administration are split by task, and the roles are activated for a limited time through Privileged Identity Management. The change history report shows who changed which site or tenant setting and when.

    Security: None of these roles is permanently active. Anyone activating a role gives a reason, and the activation is recorded in the Entra ID audit log.

    Where it runs: Roles in Microsoft Entra ID with Privileged Identity Management, change history in SharePoint Advanced Management.

    Exampleroles/m365-governance.yaml
    SharePoint Administrator: sites, sharing, policies
    Teams Administrator:      Teams policies, templates
    Groups Administrator:     groups, naming, expiry
    Global Reader:            review with no change rights
    PIM:                      time-limited, with reason
    Change history report:    site and tenant settings
    • Entra ID
    • Privileged Identity Management
    • SharePoint Advanced Management
    Chapter 4 · Documents and knowledge

    Approval path

    Power Automate offers approvals where everyone must approve, where the first response counts, ones with custom response options, and sequential approval person by person. A rejection ends the path, the comment goes to the author, and she revises the same file. The path then starts again with the new version.

    Security: Every request links to exactly the version under review. If the file changes afterwards, the flow resets the status, and the approval does not carry over to the new version.

    Where it runs: Approvals connector in Power Automate with the actions Start and wait for an approval, or Create an approval and Wait for an approval.

    Exampleflows/vertragsfreigabe.approval
    action:       Start and wait for an approval
    approvalType: Sequential approval
    assignedTo:
      - legal@muster-ag.ch
      - executive-board@muster-ag.ch
    itemLink:     LV-2026-114.docx, version 2.0
    requestor:    procurement@muster-ag.ch
    • Power Automate
    • Approvals-Connector
    • Dataverse
    Chapter 3 · Content and editorial work

    Audience

    Communications publishes the new shift rule, and only the staff of the two plants see it: the editors pick groups from Entra ID as the audience, and news web parts, navigation links, dashboard cards of the Teams app and whole pages then show only to those groups. Anyone outside the group does not see the entry but can still open it through a link. The audience steers attention; the permission protects the content.

    Security: Audiences are not access control: confidential content sits on a site with its own permissions and a sensitivity label. The groups are maintained by IT or the HR system, not by the editors.

    Where it runs: Audience targeting in the pages library, the news web part, the navigation and the SharePoint app in Teams, with Microsoft 365 groups or security groups from Entra ID.

    • Zielgruppenadressierung
    • SharePoint News
    • Microsoft Entra ID
    • Navigation
    Chapter 8 · Governance and security

    Audit trail

    Version history shows every version with author, date and comment, the approval log every decision. For questions beyond the document, such as who deleted or restored a file, IT searches the Microsoft Purview audit. For the audit we set up views the auditor opens on her own.

    Security: How long the audit keeps records depends on the licence: Audit (Standard) keeps them for 180 days. Version history stays with the document for as long as the library keeps it.

    Where it runs: Version history in SharePoint Online, audit in Microsoft Purview, read views for auditors as a library view of their own.

    Exampleaudit/qm-search.yaml
    audit_search:            # Microsoft Purview
      workloads:  [SharePoint]
      activities: [FileModified, FileDeleted,
                   FileRestored, FileVersionRecycled]
      file_folder_site: /sites/QM/QM-Documents
      date_range: 2026-01-01 – 2026-09-30
    • Microsoft Purview Audit
    • Version history
    • SharePoint Online
    Chapter 3 · Content and editorial work

    Authoring with Copilot

    Authors have Copilot create a page, a news draft, a list or a new library from a document. They adjust text and structure and publish themselves. New content thus comes from reviewed material, and approval stays with your editorial team.

    Security: Copilot drafts only from files the author may open. Publishing goes through your site's page approval, like any other page.

    Where it runs: Copilot in SharePoint with Create pages with AI, page approval through the Site Pages library.

    ExampleSitePages, Entwurf
    source:   Seeblick project brief.docx
    draft:    news "Seeblick construction starts"
    template: project news
    status:   draft, not published
    approval: page approval by communications
    • Copilot in SharePoint
    • SharePoint News
    • Seitenfreigabe
    Chapter 8 · Governance and security

    Auto-labelling

    An auto-apply policy searches by library, content type, keywords or sensitive information and assigns the matching label. In simulation mode we see beforehand which documents it would hit, and we sharpen the query until the selection is right. Microsoft allows up to seven days for the labels to be applied.

    Security: An auto-apply policy never replaces a label that is already on the document. Records receive their label only through rules your specialists have signed off.

    Where it runs: Auto-apply retention label policies in Microsoft Purview, with E5 or an add-on such as Microsoft Purview Suite.

    Examplepurview/auto-apply/supplier-receipts.yaml
    policy: Auto-supplier-receipts
    label:  Supplier receipt
    mode:   simulation, then turn on
    query: >
      ParentLink:"https://muster.sharepoint.com/
      sites/Finance/Receipts"
      AND RefinableString12:SupplierReceipt
    • Microsoft Purview
    • Auto-apply labels
    • KQL
    • Trainable classifiers
    Chapter 4 · Documents and knowledge

    Autofill columns

    Copilot in SharePoint reads up to 20 files in a library and suggests columns with an instruction, such as customer, document type or expiry date. Once saved, every newly uploaded file gets its values, even if the uploader has no Copilot licence. The library processes existing files on selection.

    Security: Autofill does not read encrypted files. Processing currently covers English-language files, so we test every column with your files in your languages before it goes live.

    Where it runs: Autofill columns in Copilot in SharePoint, for text, number, date, choice, currency and managed metadata; Microsoft recommends no more than 10 columns per library.

    ExampleBibliothek Offerten, Autofill-Spalten
    column:      Supplier       (managed metadata)
    instruction: Name of the supplier issuing the quote,
                 matched to term set Suppliers.
    column:      Valid until    (date and time)
    instruction: Date until which the quote is valid.
                 Leave empty if no date is stated.
    • Copilot in SharePoint
    • Autofill
    • Terminologiespeicher
    Chapter 8 · Governance and security

    Backup

    Day to day, employees restore overwritten versions and deleted files themselves. Against mass deletion or encryption by malware, a backup outside the library helps. For this we use Microsoft 365 Backup or the data backup of our partner MOUNT10 in Switzerland.

    Security: A separate role manages the backup, apart from the site owners. A restore is logged and rehearsed with you before it is needed.

    Where it runs: Microsoft 365 Backup for SharePoint and OneDrive, or the Microsoft 365 backup from MOUNT10.

    • Microsoft 365 Backup
    • MOUNT10
    Chapter 4 · Documents and knowledge

    Bookmarks

    A bookmark links a URL to keywords, spelling variants and target groups. Acronyms explain your organisation's abbreviations, such as BG for building permit application. Your search owners maintain both, and both appear in SharePoint, on Microsoft365.com and in the Copilot app.

    Security: A bookmark shows only title and link; whether someone may open the target depends on the target's permissions. Through groups it appears only for the people it is meant for.

    Where it runs: Bookmarks and acronyms in Microsoft Search, maintained in the Microsoft 365 admin center, valid for Microsoft Search and Copilot Search.

    ExampleLesezeichen, Microsoft 365 Admin Center
    bookmark: Building permit template
    url:      /sites/Bau/Vorlagen/Baugesuch.docx
    keywords: Baugesuch, building permit, BG
    reserved: building permit template
    groups:   construction, project management
    acronym:  BG = Baugesuch (building permit)
    • Microsoft Search
    • Copilot Search
    • Microsoft 365 Admin Center
    Chapter 9 · Rollout and operations

    Champions

    In every division there is one person who knows the new intranet before launch, answers the team's questions and tells the project what does not work in daily use. Champions are named by their division, get the training first and meet with the editors and IT regularly during the first months. After launch they remain the first point of contact and carry new features such as agents on sites into their division.

    Security: Champions get no admin rights; they work with the same permissions as their division and report what needs rights or rules.

    Where it runs: A team in Microsoft Teams for the champions, material from Microsoft Adoption, training as a learning portal in the intranet.

    • Champions
    • Einführung
    • Schulung
    • Microsoft Adoption
    Chapter 4 · Documents and knowledge

    Channel agent

    In the channel the agent answers questions on project status, creates tasks with due dates in Planner and drafts status reports. It stores the report as a Loop file in the channel folder, and a responsible person approves it before it appears in the channel. The status is then in the channel, also for everyone who was away for a week.

    Security: The agent does not use files the person asking may not open. In the preview it does not yet support private channels or channels with external participants.

    Where it runs: Channel Agent in Microsoft Teams, in public preview, with tasks in Planner and reports as Loop files.

    ExampleChannel Agent, Kanal Allgemein
    channel:   Project Seeblick / General
    knowledge: posts, channel files, meetings
    report:    Status week 42.loop, channel folder
    approval:  project manager before posting
    tasks:     Planner, plan "Seeblick"
    excluded:  private channels, shared with externals
    • Microsoft Teams
    • Channel Agent
    • Planner
    • Loop
    Chapter 2 · Structure and navigation

    Channels

    Standard channels are visible to every team member, private channels only to those invited, for quotes and fees for example. A shared channel admits people from a partner firm, who see only that one strand. Private and shared channels each have a SharePoint site of their own.

    Security: Private channels and their files stay invisible to the rest of the team. Teams policies control who may create a private or shared channel.

    Where it runs: Standard, private and shared channels in Microsoft Teams, policies in the Teams admin center.

    Exampletemplates/hochbau-kanaele.yaml
    team: P-2026-114 Musterdorf school
    channels:
      - General      standard
      - Planning     standard
      - Delivery     standard
      - Quotes       private   # own site
      - Structural   shared    # with partner firm
    • Microsoft Teams
    • SharePoint Online
    Chapter 4 · Documents and knowledge

    Content approval

    The library keeps major and minor versions: 3.0 is current, 3.1 and 3.2 are drafts. With content approval only an approved major version becomes visible to everyone, and draft item security shows minor versions only to editors and approvers. Every version stays in the version history with date, person and comment.

    Security: For readers, a link to the document always opens the last approved version. Seeing a draft requires edit or approve permissions in the library.

    Where it runs: Versioning settings, content approval and draft item security of a SharePoint library.

    Examplelibraries/qm-documents.yaml
    library: QM-Documents
    EnableVersioning:       true
    EnableMinorVersions:    true
    EnableModeration:       true   # content approval
    DraftVersionVisibility: Approver
    ForceCheckout:          true
    • SharePoint Online
    • Version history
    • Content approval
    Chapter 4 · Documents and knowledge

    Content type

    A content type such as expert report brings required columns, a template and, if needed, a retention label. We maintain it once in the content type gallery and publish it to every site that needs it. From the moment it is saved, every document carries the metadata it is filtered and found by.

    Security: Only people you designate for the document store change the content type. The published version applies alike in every site.

    Where it runs: Content type gallery in the SharePoint admin center, published to sites and libraries.

    Examplecontenttypes/gutachten.yaml
    contentType: Expert report
    parent:      Document
    columns:
      customer:      Managed metadata, required
      projectNumber: Text, required
      phase:         Managed metadata, required
      status:        Draft | Approved
    template:    ExpertReport.dotx
    • SharePoint Online
    • Content types
    • SharePoint admin center
    Chapter 4 · Documents and knowledge

    Copilot connectors for search

    Synced connectors bring content from Confluence, a file share or a business system into the Microsoft Graph index, with the source's permissions per item. Federated connectors query the source live through the Model Context Protocol, with no indexing. Microsoft lists more than 100 prebuilt connectors, and for systems of your own we build one.

    Security: Only people with access in the source see a synced item; for this we map the source's groups to identities in Entra ID. The connector reaches the external system through a service account of its own with read rights.

    Where it runs: Copilot connectors in the Microsoft 365 admin center, custom connectors through the Microsoft Graph connectors API.

    Exampleconnectors/projektsystem.yaml
    connector: project system (custom connector)
    mode:      synced, Microsoft Graph index
    acl:       from the source, per item
    crawl:     full weekly, incremental hourly
    vertical:  Projects, result type Plan
    labels:    title, url, lastModifiedDateTime
    • Copilot-Connectors
    • Microsoft Graph
    • Confluence
    • MCP
    Chapter 4 · Documents and knowledge

    Copilot in SharePoint

    Since the end of September 2026 Copilot in SharePoint has been rolling out generally: it summarises documents, drafts pages and answers questions with the permissions of the person asking. Everyday features come with the Copilot licence; "Advanced work" uses Copilot Credits and needs a spending policy. From 1 November 2026, Site AI settings and Restricted Content Discovery control where Copilot appears.

    Security: Copilot sees only what the person may open, and so it finds everything shared too widely. Before a broad start we clean up sharing with the SharePoint Advanced Management reports.

    Where it runs: Copilot in SharePoint with a Microsoft Copilot licence, Copilot Credits for Advanced work, Site AI settings and Restricted Content Discovery in the SharePoint admin center.

    Examplecopilot-in-sharepoint.txt
    Copilot in SharePoint     generally from 2026-09-30
    Everyday features         Microsoft Copilot licence
    Advanced work             Copilot Credits
    Spending policy           Microsoft 365 admin center
    Control until 2026-11-01  PowerShell from the preview
    Control afterwards        Site AI settings, RCD
    • Copilot in SharePoint
    • Copilot Credits
    • Site AI settings
    • Restricted Content Discovery
    Chapter 7 · Licences and cost

    Copilot licence in SharePoint

    With a Microsoft Copilot licence a person creates pages, sites and libraries from a description, asks Copilot in SharePoint and builds agents on sites; Copilot in SharePoint has been generally available since 30 September 2026 (as of 25 September 2026). Large-scale work such as reviewing whole libraries is billed in Copilot Credits, and as soon as one licence sits in the tenant, the governance reports of SharePoint Advanced Management become available (as of 30 June 2026). People without a licence use agents through pay-as-you-go billing.

    Security: The licence changes nothing about rights: Copilot answers only from content the person may open. Before the first licence, owners clean up wide sharing so that Copilot does not surface what nobody looked for before.

    Where it runs: A Microsoft Copilot licence per person, Copilot Credits for advanced work, site AI settings and reports in the SharePoint admin center.

    • Microsoft Copilot
    • Copilot Credits
    • SharePoint Advanced Management
    • Agenten in SharePoint
    Chapter 8 · Governance and security

    Creation and naming rule

    Every new Microsoft 365 group receives a prefix from the department of the person who creates it, and blocked words such as CEO or Payroll are off limits. A security group controls who may create teams; everyone else submits a request with a template.

    Security: The naming policy and blocked words apply to everyone except certain admin roles. Even the address book shows from the name what a group belongs to.

    Where it runs: Group naming policy and restricted group creation in Microsoft Entra ID, requiring Entra ID P1.

    Exampleentra/group-unified-settings.txt
    # Entra ID, group settings Group.Unified
    PrefixSuffixNamingRequirement: T-[Department]-[GroupName]
    CustomBlockedWordsList:        CEO,Lohn,Payroll
    EnableGroupCreation:           false
    GroupCreationAllowedGroupId:   <ID team creators>
    • Entra ID
    • Microsoft 365 Groups
    • Microsoft Teams
    Chapter 6 · Migration

    Cutover

    We set the window with you. The last run carries over the latest changes, then the old area goes read-only. Test cases with real content check opening, versions, search and permissions.

    Security: Read-only prevents work continuing in the old area and two versions emerging. Rollback to the old area is in the plan.

    Where it runs: Cutover checklist and test plan (template to download), read-only through the file server's NTFS permissions.

    ExampleUmstellungscheckliste und Testplan.docx
    [x] Run 2 with changes completed
    [x] Old area F:\Projekte\Bau set to read-only
    [x] Test: open project folder, check version
    [x] Test: search for project number 24-117
    [x] Test: apprentice role can only read
    [ ] Inventory comparison accepted
    • Migration Manager
    • SharePoint Online
    • Windows Server
    Chapter 8 · Governance and security

    Data location Switzerland

    For a tenant located in Switzerland the data of SharePoint, OneDrive, Exchange and Teams rests in the data centres in Geneva and Zurich (as of 1 April 2026); which Purview services the data residency commitment covers is listed by Microsoft per service (as of February 2026). Processing and support can take place outside, within the EU Data Boundary, which includes Switzerland as an EFTA country. For the data protection officer that means: the location of the files is documented, the rest is in the contract.

    Security: Data location replaces neither a permission nor a label; it answers only the question of where the files rest. For personal data in services outside the commitment you record the decision in writing.

    Where it runs: The tenant's data location in the Microsoft 365 admin center under organisation profile, the commitment per service in the Microsoft 365 data residency documentation.

    • Datenresidenz
    • Genf und Zürich
    • Microsoft Purview
    • EU-Datengrenze
    Chapter 8 · Governance and security

    Disposition review

    When a period ends, the named reviewers receive an email and see the affected documents in the Purview portal. They approve deletion, extend the period or assign a different label, in up to five consecutive stages. Deleted records remain provable in the overview.

    Security: Only named reviewers see the content under review, and every decision is in the audit log with person and date. After the final approval Microsoft deletes permanently.

    Where it runs: Disposition review in Microsoft Purview Records Management, with E5 or a Purview add-on.

    Examplepurview/disposition/supplier-receipt.yaml
    end_action: disposition_review
    stages:
      - Finance:  head-finance@muster-ag.ch
      - Audit:    grp-internal-audit
    auto_approve: off
    proof: list of disposed records in the portal
    • Microsoft Purview
    • Disposition review
    • Audit log
    Chapter 4 · Documents and knowledge

    Document ID

    The Document ID service gives every file a fixed number with your organisation's prefix. A link with this number leads to the file even after it moves within the site. References in minutes, contracts and tickets stay valid when folders are rearranged.

    Security: The link opens the file only for people who may see it anyway. The number itself reveals nothing about the content.

    Where it runs: Document ID service as a site collection feature in SharePoint Online.

    Examplesites/projekte/dokument-id.yaml
    service:  Document ID, site collection feature
    prefix:   MUSTER
    example:  MUSTER-1452365871-23
    link:     /sites/Projekte/_layouts/15/
              DocIdRedir.aspx?ID=MUSTER-1452365871-23
    • SharePoint Online
    • Document ID
    Chapter 4 · Documents and knowledge

    Document processing

    A prebuilt model for invoices runs on the intake library and fills receipt number, receipt date, supplier and amount into columns. Contracts have a model of their own, and text recognition makes scanned pages searchable. Whatever the model reads with low confidence is flagged in a column for review.

    Security: Processing runs in the Microsoft 365 tenant, and the columns inherit the library's permissions. A person confirms amount and supplier before the receipt enters the approval workflow.

    Where it runs: Document processing for Microsoft 365 with prebuilt models, autofill columns and text recognition, billed pay-as-you-go.

    Examplemodels/invoice-prebuilt.yaml
    model:   Invoice processing (prebuilt)
    library: /sites/Finance/Intake
    extract:
      InvoiceId    -> ReceiptNumber
      InvoiceDate  -> ReceiptDate
      VendorName   -> Supplier
      InvoiceTotal -> Amount
    billing: pay-as-you-go via Azure subscription
    • Document processing
    • Prebuilt models
    • Autofill columns
    • OCR
    Chapter 4 · Documents and knowledge

    Document set

    A project, a contract or a person becomes a document set with shared metadata and access of its own. Shared columns such as customer and project number pass automatically to every document in the set. A workflow creates the set at project start or when someone joins.

    Security: We grant separate access on the whole set, so all documents of a case stay equally protected.

    Where it runs: Document set content type in SharePoint, created through Power Automate.

    Exampledocsets/p-2026-114.yaml
    set:         P-2026-114 Musterdorf school
    contentType: Project set
    shared:      [customer, projectNumber]
    allowed:     [Expert report, Quote, Minutes]
    access:      Building project team
    created:     Power Automate, at project start
    • SharePoint Online
    • Document sets
    • Power Automate
    Chapter 3 · Content and editorial work

    Editorial model

    An editorial lead in communications, one editor per division and a plan that records who publishes what and when: the editorial model makes sure the intranet still shows something new every week in its second year. The division editors write news and maintain the pages of their division, the editorial lead approves, sets priorities and sees in page analytics what is read. Once a year every page owner reviews her pages against the review date.

    Security: Editors are members of their site, not owners; ownership stays with two named people per site, and the approval separates writing from publishing.

    Where it runs: Roles as groups in Entra ID, the editorial plan as a list in SharePoint or in Planner, page analytics on every page, approval through Power Automate.

    • Redaktionsplan
    • Bereichsredaktion
    • Seitenanalyse
    • Prüfdatum
    Chapter 2 · Structure and navigation

    Files in channels

    Behind every channel is a folder in the team site's document library, created with the project type's folder structure. Word, Excel and PowerPoint open the same version for everyone, and several people write at once. The library is also available in File Explorer and in SharePoint.

    Security: Permissions follow membership of the team or channel. We set sharing links to specific people by default, so nothing leaves the organisation unnoticed.

    Where it runs: SharePoint document library of the team site, sync through OneDrive.

    Exampletemplates/hochbau-ordner.txt
    Planning/
      01 Preliminary design/
      02 Design/
      03 Tender/
    Delivery/
      04 Construction/
      05 Acceptance/
    • SharePoint Online
    • OneDrive
    • Microsoft Teams
    Chapter 1 · Overview

    Home site

    On the home site, search reaches across the whole intranet, its news counts as official company news, and global navigation in the app bar follows employees onto every site. Behind it, hubs group the sites of HR, finance or a plant with shared navigation, a shared design and a search scope of their own. When a department moves to another area, you assign its site to another hub, and every address stays the same.

    Security: A hub changes no permissions: what rolls up on the hub is visible only to people who may open the source. Links to closed sites are shown by audience to their members only.

    Where it runs: Home site, hubs and hub-to-hub associations are set up in the SharePoint admin center, site associations also through PowerShell.

    Examplehubs.ps1
    # Assign the Thun plant site to the Plants hub
    Add-SPOHubSiteAssociation `
      -Site https://muster.sharepoint.com/sites/thun `
      -HubSite https://muster.sharepoint.com/sites/werke
    # Associate the Plants hub with the Intranet hub
    # in the admin center: search then spans both.
    • SharePoint home site
    • Hub sites
    • SharePoint app bar
    Chapter 8 · Governance and security

    Inactive sites

    The policy measures activity across SharePoint, Teams, Exchange and Viva Engage and asks the owners once a site passes the threshold. With no reply it sets the site to read-only and archives it after a set period with Microsoft 365 Archive. Nothing is deleted.

    Security: An archived site stays under retention and remains findable in eDiscovery. SharePoint administration can reactivate it.

    Where it runs: Inactive site policy in SharePoint Advanced Management, archiving with Microsoft 365 Archive.

    Examplesam/inactive-site-policy.yaml
    policy:   Inactive project sites
    type:     Inactive site policy
    inactive: 12 months (SharePoint, Teams, Exchange)
    notify:   owners, reply right in Outlook
    action:   read-only, then archive
    archive:  Microsoft 365 Archive
    mode:     active, report after every run
    • SharePoint Advanced Management
    • Microsoft 365 Archive
    • Outlook
    Chapter 6 · Migration

    Inventory

    The sheet has one row per folder or site, filled from the scans with size, last change and owner. Your owners fill in the decision, target and wave columns. The last columns stay free for the inventory comparison after the transfer.

    Security: The inventory reads metadata and permissions and no document content. We check licences and storage in the target before the first step.

    Where it runs: Inventory and mapping (template to download) as an Excel sheet, filled from Migration Manager or SharePoint Migration Tool scans.

    ExampleBestandsaufnahme und Zuordnung.xlsx
    Source       Owner     Decision      Target    Wave
    F:\Projekte  PL Bau    carry over    Projects  Pilot
    F:\Finanzen  CFO       carry over    Finance   2
    F:\Archiv    MD        archive       Archive   -
    F:\Scan_alt  -         leave behind  -         -
    • Microsoft Excel
    • Migration Manager
    • SharePoint Migration Tool
    • SharePoint Checker
    Chapter 5 · Permissions and sharing

    Label for sites

    The label on a team or site sets privacy, guest access, external sharing and access from unmanaged devices. The owner picks it at creation, and a site labelled confidential can no longer be opened to the outside by accident. The documents inside do not inherit the label automatically.

    Security: The label sets the site's sharing level, and a Purview policy decides which labels are on offer. Every change of label is recorded in the audit log.

    Where it runs: Sensitivity labels in Microsoft Purview Information Protection, enabled for groups and sites, enforced in Teams, SharePoint and Entra ID.

    Examplepurview/label-confidential-project.yaml
    label:   Confidential - Project
    scope:   groups and sites
    privacy:            Private
    guests:             not allowed
    externalSharing:    people in the organisation only
    unmanagedDevices:   browser only, no download
    defaultSharingLink: specific people
    • Microsoft Purview
    • Sensitivity labels
    • SharePoint Online
    • Microsoft Teams
    Chapter 5 · Permissions and sharing

    Label on the document

    The payroll report carries the label «Confidential, HR»: the document is encrypted, only the HR group can open it, and a watermark shows the level. The label travels with the file, into an email or onto a USB stick, and stays when the file leaves the site. A policy can apply it automatically, for instance when a document contains social security numbers.

    Security: Whether Copilot may quote from a labelled document follows the label's extract right; without it, Copilot does not read the document. The label of a site and the label of the document are two different things: the site governs guests and sharing, the document its content.

    Where it runs: Sensitivity labels in Microsoft Purview Information Protection, applied in Word, Excel, PowerPoint and Outlook and to files in SharePoint and OneDrive, automatically through policies.

    • Microsoft Purview
    • Vertraulichkeitsbezeichnungen
    • Verschlüsselung
    • Extrahieren
    Chapter 6 · Migration

    Legacy system

    The cutover plan sets the sequence for each legacy system, each step with a responsible person: for a file server read-only and archive, for a SharePoint Server backup, shutdown and return of licences. Archive and shutdown begin once the inventory comparison is accepted.

    Security: A system without security updates stays on the network only as long as needed. The archive gets the retention your rules require.

    Where it runs: Archive in SharePoint Online or on storage of your choice, backup of the SharePoint Server before shutdown.

    ExampleUmstellungsplan, Altsystem
    File server        read-only, archive, off
    SharePoint Server  backup, shutdown, licences
    SP Server 2016/19  unsupported since 14 Jul 2026
    responsible        Head of IT, Muster AG
    • SharePoint Server
    • SharePoint Online
    • Windows Server
    Chapter 4 · Documents and knowledge

    Library

    Project files, customer dossiers or policies each sit in a library of their own, with the permissions of the team that needs them. Views group the same collection by customer, project or year. With a Copilot licence, Copilot in SharePoint suggests columns at creation that new documents fill in themselves.

    Security: We set permissions on the library or document set, and single files keep the inherited permissions. That keeps it traceable who sees what.

    Where it runs: SharePoint document library, creation with Copilot in SharePoint switched on by default for licensed people.

    Examplesites/projekte/bibliothek.yaml
    library: Building projects
    contentTypes: [Expert report, Quote, Minutes]
    views:
      - By customer        grouped: customer
      - By phase           grouped: phase
      - My drafts          status = Draft, me
    • SharePoint Online
    • Copilot in SharePoint
    Chapter 2 · Structure and navigation

    Loop workspace

    In a channel, the team's Microsoft 365 group decides who writes in the workspace. For projects across departments a workspace of its own is created in the Loop app, with owners you appoint. Every shared workspace has its own container, which counts toward the tenant's storage quota.

    Security: There is no user recycle bin for deleted workspaces; IT restores them with the admin tools. If all owners are gone, IT appoints new ones.

    Where it runs: Loop workspaces in the Loop app and in Teams channels, each as a container in SharePoint Embedded, managed in the SharePoint admin center.

    ExampleSharePoint admin center / Containers
    workspace: Trade fair 2027
    type:      Loop app, shared
    owners:    m.brunner, s.weber
    members:   Marketing, Inside sales
    container: /contentstorage/CSP_6f1c.../
    label:     Internal
    pages:     Booth concept, Budget, Decision log
    • Loop app
    • Microsoft Teams
    • SharePoint Embedded
    • Microsoft 365 Groups
    Chapter 7 · Licences and cost

    Microsoft 365 Archive

    Inactive sites and, if you wish, single files move to Microsoft 365 Archive, a cold storage tier inside SharePoint that uses no active quota. Search, Content Search and eDiscovery still find the content. On reactivation a site keeps all metadata and permissions.

    Security: Retention policies and records still apply in the archive. Whole sites are reactivated by SharePoint admins, and a reactivated file can be archived again only after 120 days.

    Where it runs: Microsoft 365 Archive in the SharePoint admin center and through PowerShell, billed pay-as-you-go.

    Exampleops/archive-project.ps1
    # Project closed, owners informed
    Set-SPOSiteArchiveState `
      -Identity https://muster.sharepoint.com/sites/P-2021-07 `
      -ArchiveState Archived
    
    Get-SPOSite -Identity .../sites/P-2021-07 |
      Select Url, ArchiveStatus
    • Microsoft 365 Archive
    • SharePoint Online
    • eDiscovery
    Chapter 1 · Overview

    Microsoft 365 group

    Creating a team creates a Microsoft 365 group, and with it come a group mailbox for the calendar and a SharePoint site for the files. Entra ID manages membership and ownership, through dynamic groups by department if you wish. That is why we plan names, expiration policy and templates together with the group.

    Security: Inactive teams surface through the expiration policy, and the owners renew them or let them lapse. A deleted team can be restored for 30 days.

    Where it runs: Microsoft Teams on Microsoft 365 groups in Entra ID, with Exchange Online for the calendar and SharePoint Online for files; expiration policies and dynamic groups require Entra ID P1.

    Exampleteams/prj-werkhalle.yaml
    team:     PRJ-Werkhalle
    group:    Microsoft 365 (Unified)
    mailbox:  prj-werkhalle@muster.ch   # calendar
    site:     /sites/PRJ-Werkhalle      # files
    owners:   at least 2
    expiry:   365 days, renewed by owners
    template: Construction project
    • Microsoft Teams
    • Microsoft 365 Groups
    • Exchange Online
    • SharePoint Online
    Chapter 6 · Migration

    Migration Manager and SPMT

    File servers as well as Google Drive, Box, Dropbox and Egnyte go through Migration Manager, SharePoint Server through the SharePoint Migration Tool. Confluence is not on Microsoft's list and moves through the wiki's interface. A first run transfers the inventory, a second one the changes since the first, so your team keeps working until cutover.

    Security: Migration Manager agents run on machines in your network and sign in with an account your IT grants rights for the migration and withdraws them from afterwards. Versions, authors and modification dates move along.

    Where it runs: Migration Manager in the SharePoint admin center and the SharePoint Migration Tool; SharePoint Server 2016 and 2019 have been out of support since 14 July 2026.

    ExampleMigrationsplan, Werkzeuge
    Source              Tool
    File server         Migration Manager
    Google Drive, Box   Migration Manager
    SharePoint Server   SharePoint Migration Tool
    Confluence          the wiki's interface
    Run 1 inventory, run 2 changes since run 1
    • Migration Manager
    • SharePoint Migration Tool
    • SharePoint Online
    • OneDrive
    Chapter 2 · Structure and navigation

    Multilingual sites

    The working-time directive appears in German, French and Italian, and every person sees the version in the language of their profile. On a multilingual communication site the editors create the page in the default language, SharePoint creates one copy per target language and notifies the assigned translators; navigation, site title and footer carry their own translations. When the original changes, every language version receives a notice that it needs updating.

    Security: Every language version is a page of its own with the same approval path; translators need edit rights on the site. The language comes from the profile in Entra ID or from the browser setting.

    Where it runs: The multilingual feature in the settings of a communication site in SharePoint Online, page translation in the site pages library, navigation translated per language.

    • Mehrsprachige Kommunikationssites
    • Seitenübersetzung
    • Übersetzer
    • Profilsprache
    Chapter 2 · Structure and navigation

    Navigation

    An employee at the Thun plant finds the expense directive through the home site menu, through the hub navigation of her plant or through the app bar that follows her onto every site. Three levels carry the route: the global navigation of the home site, the hub navigation and the menu of the individual site; a mega menu arranges many entries in columns. Every entry can be targeted to an audience, so production sees other links than administration.

    Security: Navigation changes no rights: a link to a closed site leads nowhere for people without access. Editing the navigation needs owner rights on the home site or the hub, and the change applies to everyone at once.

    Where it runs: Global navigation and app bar of the home site, hub navigation on the hub, site navigation and mega menu on communication sites, audiences from Entra ID.

    • Globale Navigation
    • Hub-Navigation
    • Mega-Menü
    • SharePoint App Bar
    Chapter 3 · Content and editorial work

    News

    The communications team writes a news post on the home site or a hub and picks groups from Entra ID as the audience, such as the staff of one plant. The news web parts on the home site, the hubs and in the Teams app then show it to that group. Page analytics then show how many people read the post, through which channel and what share of the audience it reached.

    Security: Audiences control what someone is shown; confidential content is secured through the site's permissions and labels. When the audience changes, the post is republished.

    Where it runs: Audiences are switched on in the pages library and in the news web part, extended news analytics require a Viva Suite or Viva Communications and Communities licence.

    Examplenews/neue-schichtregel.yaml
    news:      New shift rule from November
    site:      Plants hub
    audiences: [SG-Plant-Thun, SG-Plant-Biel]
    approval:  page approval, communications
    share:     home site, Teams app, email
    analytics: viewers, channels, audience view rate
    • SharePoint News
    • Audience targeting
    • Microsoft Entra ID
    • Page analytics
    Chapter 2 · Structure and navigation

    OneDrive

    Drafts and notes start in OneDrive. Once a document is meant for the team or should stay when someone leaves, it moves to the team or project library. Sync shows both in File Explorer, and Desktop, Documents and Pictures are backed up through OneDrive.

    Security: After someone leaves, a OneDrive is kept only for an adjustable period, 30 days by default. That is why everything the team needs belongs in a library in good time.

    Where it runs: OneDrive with Known Folder Move, retention after departure in the SharePoint admin center.

    Exampledocs/ablageregel.txt
    OneDrive:    drafts and notes, just me
    Library:     everything for the team or to keep
    Leaving:     OneDrive kept 30 days, manager
                 gets access
    Folders:     Desktop, Documents, Pictures backed up
    • OneDrive
    • Known Folder Move
    • SharePoint admin center
    Chapter 8 · Governance and security

    Owner attestation

    Even an active site may have outlived its purpose. Attestation explicitly asks owners whether the site is still needed and whether members and guests are right. For groups, the Entra ID expiration policy lets active groups renew themselves.

    Security: The group expiration policy deletes a group that is not renewed, restorable for 30 days. We switch it on only once ownership and retention are settled.

    Where it runs: Site attestation policy in SharePoint Advanced Management, Microsoft 365 group expiration policy in Entra ID with Entra ID P1.

    Examplesam/site-attestation-policy.yaml
    policy:   Attestation of confidential sites
    type:     Site attestation policy
    scope:    label "Confidential - Project"
    interval: 12 months
    ask:      purpose, members, guests, sharing
    no_reply: read-only after three reminders
    groups:   expire after 365 days, renew on activity
    • SharePoint Advanced Management
    • Entra ID
    • Microsoft 365 Groups
    Chapter 8 · Governance and security

    Ownership

    An ownership policy finds sites that drop below the minimum and keeps asking until someone steps in. When a team loses its last owner, Microsoft 365 asks the most active members whether they will take over. Before the first active run, a simulation shows which sites would be affected.

    Security: Notifications arrive as Outlook Actionable Messages and are answered right in the email. Every acceptance is recorded in the audit log.

    Where it runs: Site ownership policy in SharePoint Advanced Management and the ownerless group policy in the Microsoft 365 admin center.

    Examplesam/site-ownership-policy.yaml
    policy:     At least two owners
    type:       Site ownership policy
    scope:      team sites, communication sites
    min_owners: 2 (owners or site admins)
    mode:       simulation, then active
    notify:     owners, area leads
    ownerless:  ask active members by email
    • SharePoint Advanced Management
    • Microsoft 365 Groups
    • Outlook
    Chapter 3 · Content and editorial work

    Page approval

    The editor of the finance division writes the news post on the annual accounts and sends it for approval; the head of communications sees the request in Teams, reads the draft and approves, and only then does the post appear for its audience. The approval runs as a flow on the site pages library, so the draft stays invisible to readers. A review date per page reminds the owner after a year whether the content still holds.

    Security: Approvers sit in a group, not as individual names in the flow, and every approval is recorded with person and time in the page's version history. Without approval the page stays a draft that only editors see.

    Where it runs: Page approval through Power Automate on the site pages library, responses in the Teams Approvals app, the review date as a column of the library with a scheduled flow.

    • Power Automate
    • Websiteseiten
    • Approvals-App
    • Prüfdatum
    Chapter 3 · Content and editorial work

    Pages and web parts

    Every page is made of sections with web parts for news, highlighted content, quick links, events, people or documents. The web parts pull content from their own site, from all sites in a hub or from selected sources, so the HR page shows new directives on its own. Multilingual pages carry the same page in German, French and English.

    Security: Web parts only show content the reader may open. With page approval, only what someone has checked appears on the home site.

    Where it runs: Pages and web parts are part of modern SharePoint sites, page approval runs on Power Automate, and we build custom web parts with the SharePoint Framework.

    Examplehome/news-webpart.yaml
    webpart:  News
    layout:   Top story
    source:   all sites in the Plants hub
    audience: audience targeting on
    order:    organisation news first
    approval: page approval before publishing
    • SharePoint pages
    • Web parts
    • Power Automate
    • SharePoint Framework
    Chapter 5 · Permissions and sharing

    Partners in the workspace

    Whoever works across the whole project joins the team as a guest. A partner firm that follows a single strand works in the shared channel with its own account. For that, both organisations set up B2B direct connect in their cross-tenant access settings.

    Security: Guest accounts cannot be added to a shared channel, and external participants see only that channel's files. Conditional Access applies to guests and to people joining through B2B direct connect too.

    Where it runs: Guest access and B2B direct connect in Microsoft Entra ID, shared channels in Teams.

    Exampleentra/cross-tenant-partner.yaml
    crossTenantAccess:
      partner: ingenieurbuero-beispiel.ch
      b2bDirectConnect:
        inbound:  allow   # group Project partners
        outbound: allow
      sharedChannels: [Structural]
    guestsInTeam: false  # Confidential label
    • Entra ID
    • B2B direct connect
    • Microsoft Teams
    • Conditional Access
    Chapter 7 · Licences and cost

    Pay-as-you-go billing

    Document processing, eSignature, Microsoft 365 Archive, Microsoft 365 Backup and agents for people without a Copilot licence run on a meter: an Azure subscription is linked to the tenant, and every processed page, every signature and every archived volume appears on the Azure invoice. For document processing a monthly no-charge allowance applies until December 2026 (as of 15 July 2026). What the meter costs is in Microsoft's price list; which levers move it, in the licences and cost chapter.

    Security: Without a budget alert in the Azure subscription nobody notices when a model processes a whole library overnight; a budget with an alert and a monthly look at the cost analysis are part of operations.

    Where it runs: Pay-as-you-go billing through an Azure subscription, set up in the Microsoft 365 admin center under Setup, costs in Azure cost analysis.

    • Azure-Abonnement
    • Dokumentverarbeitung
    • eSignature
    • Microsoft 365 Archive
    Chapter 5 · Permissions and sharing

    Permissions

    The HR site has three default groups, owners, members and visitors, and each one contains a group from Entra ID, not an individual person. Libraries and folders inherit these rights; anyone who breaks inheritance for a folder creates an exception that nobody can explain two years later. So the rule is: grant rights at the site, solve exceptions with sites of their own, avoid direct permissions to people.

    Security: The site permission reports show where inheritance is broken and where «Everyone except external users» appears; the site access review lets owners clean it up themselves. Copilot and agents see exactly what the person asking may see.

    Where it runs: Permission levels and SharePoint groups per site in SharePoint Online, filled with Microsoft 365 groups and security groups from Entra ID, reports in SharePoint Advanced Management.

    • Berechtigungsstufen
    • SharePoint-Gruppen
    • Microsoft Entra ID
    • Vererbung
    Chapter 6 · Migration

    Permissions mapping

    For each folder with its own rights, the old individual shares sit next to the group that replaces them. Shares that went further than needed we flag for a decision. After the transfer one test person per role signs in and checks what they see.

    Security: Every removed or narrowed share is signed off by the area's owner. Afterwards your IT or the owner maintains group membership.

    Where it runs: Security and Microsoft 365 groups in Microsoft Entra ID, used in the SharePoint site permissions.

    Exampleberechtigungen-zuordnung.csv
    old:   F:\Projekte\Bau  individual shares, 23 people
    new:   Projects-Construction-Edit  Entra group
           Projects-Read               Entra group
    too wide: "Everyone" on F:\Projekte\Alt, removed
    Test:  site manager role, apprentice role
    • Entra ID
    • SharePoint Online
    • Microsoft 365 Groups
    Chapter 1 · Overview

    Profile card

    Standard fields such as phone, job title, department and office location appear as soon as they are filled. We switch on fields such as cost centre or division where they help your team, plus custom attributes with labels in your languages. Changes appear in Outlook, Teams and SharePoint within 24 hours.

    Security: Only someone with the People Administrator or Global Administrator role switches on profile card fields. Hiding a field removes it from the card and leaves the attribute in Entra ID.

    Where it runs: Profile card in Microsoft 365, customised in the Microsoft 365 admin center or through the profileCardProperties API in Microsoft Graph.

    Examplegraph/profilecard-sprachen.http
    POST /v1.0/admin/people/profileCardProperties
    {
      "directoryPropertyName": "CustomAttribute1",
      "isVisible": true,
      "annotations": [{ "displayName": "Languages",
        "localizations": [{ "languageTag": "de-CH",
          "displayName": "Sprachen" }] }]
    }
    • Profile card
    • Microsoft Graph
    • Outlook
    • Microsoft Teams
    Chapter 9 · Rollout and operations

    Query analytics

    The report lists frequent terms, searches with no result and searches with no click, for Microsoft365.com, the SharePoint home page and SharePoint sites. Your search owners go through it regularly, and every gap gets an action: a bookmark, a corrected detail or a missing document.

    Security: The report hides terms searched by five or fewer people. It shows terms and counts, no names.

    Where it runs: Microsoft Search usage reports in the Microsoft 365 admin center; the list of searches with no result is in the classic view.

    ExampleAbfrageanalyse, September 2026
    Term             Searches  Results  Action
    bg formular        41        0      acronym BG
    spesen 2026        37        12     bookmark
    brandschutz        22        3      profile field
    parkplatz          18        0      page missing
    • Microsoft Search
    • Nutzungsberichte
    • Microsoft 365 Admin Center
    Chapter 4 · Documents and knowledge

    Records

    The label declares the receipt a record: content and deletion are locked, and every unlock and lock creates a version. We use regulatory records, where even administrators can no longer remove the label, only where a regulation requires it. The record stays in its place and in search.

    Security: A deletion attempt fails for everyone, site owners and SharePoint admins included. For a regulatory record, retention can only be extended.

    Where it runs: Records and regulatory records in Microsoft Purview Records Management, the lock enforced in SharePoint Online.

    ExampleKB-2026-04711.pdf / Details
    item:    KB-2026-04711.pdf
    label:   Supplier receipt
    status:  record, locked
    content: not editable
    delete:  blocked until period ends
    version: 2.0 (locked on 2026-11-03)
    • Records Management
    • SharePoint Online
    • Preservation Hold Library
    Chapter 5 · Permissions and sharing

    Restricted Content Discovery

    Restricted Content Discovery takes a site out of organisation-wide search and Copilot and hides the AI entry points on the site, including creating agents. Permissions stay unchanged, and people with access still open the content directly. Your data protection team decides with IT which sites stay restricted.

    Security: Every change to Restricted Content Discovery appears in the Microsoft Purview audit log with its justification. On large sites the change takes time to apply everywhere.

    Where it runs: Restricted Content Discovery from SharePoint Advanced Management, available with a Microsoft Copilot licence, in the SharePoint admin center or through PowerShell.

    Examplerestricted-content-discovery.ps1
    Set-SPOSite -Identity `
      https://muster.sharepoint.com/sites/GL `
      -RestrictContentOrgWideSearch $true
    Set-SPOTenant `
      -DelegateRestrictedContentDiscoverabilityManagement `
      $true   # site admins manage it, with justification
    • SharePoint Advanced Management
    • Microsoft Purview
    • Entra ID
    Chapter 8 · Governance and security

    Retention

    When the quality team withdraws a document, the workflow moves it to the site's archive and assigns a retention label from Microsoft Purview. The label declares it a record: content and deletion are locked until the period ends. At the end, quality management decides whether it is deleted.

    Security: Nobody can edit or delete a record, site owners included. We use regulatory records only where a regulation requires the irreversible lock.

    Where it runs: Retention labels and records in Microsoft Purview Records Management; records and disposition review require E5 or a Purview add-on.

    Examplepurview/qm-retention-label.yaml
    label:      QM-Document-Withdrawn
    retain:     period per quality manual
    start:      when_labeled
    mark_as:    record
    end_action: disposition_review
    reviewers:  grp-qm-management
    • Microsoft Purview
    • Records Management
    • Retention labels
    Chapter 4 · Documents and knowledge

    Search index

    Microsoft 365 continuously crawls new and changed content and stores it in the index with its permissions. Microsoft Search, Copilot Search and Copilot Chat use the same index, so every improvement works everywhere. Owners take libraries that should not appear in search out of it in the settings.

    Security: For every item the index stores who may open it, and every query shows only those results. Taking a library out of search hides it from results; the permissions stay.

    Where it runs: Microsoft 365 search index and Microsoft Graph, settings per library and site in SharePoint Online.

    ExampleBibliotheks- und Site-Einstellungen
    Library:  /sites/Projects/Archive-2018
    Setting:  Show in search results = No
    Site:     /sites/Projects
    Setting:  Reindex site after schema change
    Effect:   on the next crawl
    • Microsoft Search
    • Microsoft Graph
    • SharePoint Online
    Chapter 4 · Documents and knowledge

    Search verticals

    Every vertical has its own KQL query and its own filters, on the home page for the whole organisation or on a single site. Result types give items from a connector a layout of their own. The Projects vertical thus shows documents from SharePoint and plans from the project system side by side.

    Security: A vertical is a view on the index and grants no additional access. Site owners maintain site-level verticals themselves.

    Where it runs: Verticals, result types and filters in Microsoft Search, for the organisation in the Microsoft 365 admin center, for single sites in the site settings.

    ExampleReiter Projekte, Microsoft 365 Admin Center
    vertical: Projects
    level:    organisation
    query:    ContentType:ProjectDocument
              OR Source:ProjectSystem
    filters:
      - Phase       (RefinableString02)
      - Validity    (RefinableString01)
      - Modified    (LastModifiedTime)
    • Microsoft Search
    • KQL
    • Ergebnistypen
    Chapter 5 · Permissions and sharing

    Security-trimmed search

    Search shows only what the searching person may open, in SharePoint and in connected systems alike. If a site is shared too broadly, search reveals it first; so we review sharing before expanding search. Sites under review are temporarily taken out of organisation-wide search and Copilot with Restricted Content Discovery.

    Security: Restricted Content Discovery changes no permissions and does not apply to searches within the site. Turning it on and off appears in the Microsoft Purview audit log.

    Where it runs: Permissions in SharePoint and Entra ID, Restricted Content Discovery from SharePoint Advanced Management, available with a Microsoft Copilot licence.

    Examplerestricted-content-discovery.ps1
    # Exclude the site while it is under review
    Set-SPOSite -Identity `
      https://muster.sharepoint.com/sites/Ausschreibung `
      -RestrictContentOrgWideSearch $true
    # permissions stay unchanged
    • SharePoint Advanced Management
    • Entra ID
    • Microsoft Purview
    Chapter 8 · Governance and security

    SharePoint admin center

    In the SharePoint admin center IT sees every site with owners, storage, label and last activity, sets the home site and hubs, the tenant's sharing settings and the rules for versions, and runs the reports and policies of SharePoint Advanced Management. Recurring settings for many sites run through the SharePoint Online Management Shell or PnP PowerShell so that they are reproducible. The SharePoint Admin Agent answers governance questions in chat (as of 9 October 2026).

    Security: The SharePoint administrator role is activated through Privileged Identity Management for the duration of the task, and every change is in the Purview audit log.

    Where it runs: The SharePoint admin center in Microsoft 365, SharePoint Online Management Shell and PnP PowerShell, roles from Entra ID.

    • SharePoint Admin Center
    • Aktive Sites
    • SharePoint Online Management Shell
    • PnP PowerShell
    Chapter 5 · Permissions and sharing

    SharePoint Advanced Management

    The data access governance reports list sites with many people holding access, items shared with "Everyone except external users" and the spread of sensitivity labels. Reports on which apps and which agents access sites come on top. Sites that stand out go to their owners directly as a site access review.

    Security: The reports show metadata such as names and paths, never file contents. For sites that should stay out of Copilot for now, we set Restricted Content Discovery.

    Where it runs: SharePoint Advanced Management: the features for Copilot readiness are unlocked once one Microsoft Copilot licence is assigned in the tenant, and the full scope comes with the SharePoint Advanced Management Plan 1 add-on.

    ExampleSharePoint admin center, Reports
    Report                          shows
    Permission state                sites with broad access
    Everyone except external users   shared items
    Sensitivity labels              spread per site
    App insights                    apps with site access
    Agent access insights           agents and their sites
    -> site access review to the owners
    • SharePoint Advanced Management
    • DAG reports
    • Restricted Content Discovery
    Chapter 1 · Overview

    SharePoint app in Teams

    In Teams the intranet opens with dashboard, news and resources, on the desktop and on the phone. The dashboard shows cards for the shift plan, the payslip or the next training, so the intranet also reaches the people on the production floor. It is built on the home site, and the app takes over its news, navigation and branding.

    Security: The app runs on SharePoint, Teams and Entra ID and inherits their permissions. Dashboard cards, resources and news can be targeted to audiences.

    Where it runs: The SharePoint app in Teams is created from the home site in the SharePoint admin center; several experiences for different audiences require a Viva licence for every employee.

    Examplesharepoint-app-in-teams.yaml
    experience: Muster AG
    home_site:  https://muster.sharepoint.com
    dashboard:
      - Shift plan (card)
      - Payslip (card, audience: plants)
    resources:  global navigation from the app bar
    news:       home site, hubs, followed sites
    branding:   Muster AG logo and colours
    • SharePoint app in Teams
    • Microsoft Teams
    • Adaptive Cards
    Chapter 6 · Migration

    SharePoint Designer workflows

    The leave approval built in SharePoint Designer in 2015 ran on the SharePoint 2013 workflow platform; in SharePoint Online Microsoft switched that platform off on 2 April 2026, and such workflows have not started since. Before a migration every workflow goes into the inventory with its trigger, participants and status, and is rebuilt in Power Automate or with SharePoint Approvals. SharePoint Server follows a timetable of its own.

    Security: A rebuilt workflow runs in a solution with connection references and a service account, not under the name of the person who built it; approvers sit in groups.

    Where it runs: The 2013 workflow platform is switched off in SharePoint Online; the successors are cloud flows in Power Automate with the SharePoint connector and SharePoint Approvals from our catalogue.

    • SharePoint 2013 Workflows
    • SharePoint Designer
    • Power Automate
    • SharePoint Approvals
    Chapter 4 · Documents and knowledge

    SharePoint eSignature

    With SharePoint eSignature the signature request starts right on the document, to people in-house and to external signers who access it as guests through Entra ID. The signed version lands back in the library next to the approved one. Where your specialists require a higher signature level, we connect Adobe Sign or DocuSign.

    Security: SharePoint eSignature creates simple electronic signatures under eIDAS, and every step appears in the Microsoft Purview audit log. Your specialists decide which level a document needs.

    Where it runs: SharePoint eSignature with pay-as-you-go billing, signature requests also trackable in the Approvals app; Adobe Sign and DocuSign with their own licence.

    Exampleesignature-request.yaml
    signature_request:
      document: LV-2026-114.pdf
      signers:
        - head.procurement@muster-ag.ch
        - sales@example-supplier.ch    # guest
      level:    simple electronic signature
      billing:  pay-as-you-go, Azure subscription
    • SharePoint eSignature
    • Entra ID B2B
    • Adobe Sign
    • DocuSign
    Chapter 3 · Content and editorial work

    SharePoint Framework (SPFx)

    An SPFx web part runs in the context of the signed-in person directly on the page and shows, for example, the open quotes from the ERP on the sales home page. The same package appears as a tab in Teams or a card in Viva Connections with no code change. For solutions from the old add-in model, SPFx is the path Microsoft carries forward.

    Security: New packages reach the sites only through the tenant app catalog. IT approves the API permissions a package requests in the SharePoint admin center.

    Where it runs: SharePoint Framework deployed through the app catalog, usable in SharePoint, Teams and Viva Connections; SharePoint Copilot Apps built on SPFx are in preview.

    Exampleconfig/package-solution.json
    "solution": {
      "name": "muster-quotes-webpart",
      "version": "1.4.0.0",
      "skipFeatureDeployment": true,
      "webApiPermissionRequests": [
        { "resource": "Microsoft Graph",
          "scope": "Sites.Read.All" } ]
    }
    • SharePoint Framework
    • App catalog
    • Viva Connections
    • Microsoft Teams
    Chapter 2 · Structure and navigation

    SharePoint list

    The register of company cars, the list of open audits or the sign-ups for a training live in a list with columns, views and a form, edited in the browser, in Teams or in the Microsoft Lists app. A column of type person, date or choice turns a table into records that filters, grouping and conditional formatting can evaluate. Once the list needs relationships between tables or outgrows one site, Dataverse is the next place.

    Security: A list inherits the permissions of its site; entries with personal data belong on a site with tight access, and versioning records every change. Item-level rights are given only by exception, because they break the overview.

    Where it runs: Lists in SharePoint Online and Microsoft Lists, with rules, forms from Power Apps and flows from Power Automate; Dataverse for larger data models.

    • Microsoft Lists
    • Ansichten
    • Regeln
    • Power Apps
    Chapter 6 · Migration

    SharePoint Server Subscription Edition

    Anyone who keeps SharePoint in their own data centre runs the Subscription Edition: a version without a year in its name that receives feature updates on an ongoing basis, most recently 26H1 with Document Intelligence and the modern people card for every farm (as of 9 May 2026), and security updates in between. Support for SharePoint Server 2016 and 2019 ended on 14 July 2026; anyone still working there moves to SharePoint Online or to the Subscription Edition.

    Security: A farm in your own building needs patch windows, backup, certificates and a connection to Entra ID for sign-in; Copilot and the cloud agents reach its content only through a connector.

    Where it runs: SharePoint Server Subscription Edition on Windows Server, updates through the farm's update center; online or server as the decision in the migration chapter.

    • SharePoint Server
    • Subscription Edition
    • Funktionsupdate
    • Patching
    Chapter 5 · Permissions and sharing

    Sharing settings

    The tenant setting sets the ceiling, and each site may be equally open or tighter, from "Anyone with the link" to "Only people in your organisation". The default link when sharing targets specific people, and access for externals expires after a fixed period. We set these levels once per type of site and write them into the template.

    Security: Who may invite guests and how they sign in is also governed by the external collaboration settings in Entra ID. Every change to sharing settings is recorded in the audit log.

    Where it runs: Sharing settings in the SharePoint admin center and with SharePoint Online PowerShell, per tenant, per site and for OneDrive.

    Examplesharing/tenant-and-site.ps1
    Set-SPOTenant `
      -SharingCapability ExternalUserSharingOnly `
      -DefaultSharingLinkType Direct `
      -ExternalUserExpirationRequired $true `
      -ExternalUserExpireInDays 90
    Set-SPOSite -Identity $offerten `
      -SharingCapability ExistingExternalUserSharingOnly
    • SharePoint admin center
    • External sharing
    • Entra B2B
    Chapter 5 · Permissions and sharing

    Site access review

    The site permissions report shows sites open to all employees, very many people or guests. From the report administration starts a site access review, and owners see the most broadly shared items first. Sensitive sites stay excluded from search and Copilot until the clean-up is done.

    Security: Restricted Content Discovery changes no permissions: anyone who recently worked with a file still finds it. Copilot then answers from what a person is meant to see.

    Where it runs: Data access governance reports, site access review and Restricted Content Discovery in SharePoint Advanced Management.

    Examplecopilot-readiness.ps1
    # 1. Data access governance: Site permissions
    # 2. Sites with "Everyone except external users"
    #    -> site access review for the owners
    # 3. Exclude sensitive sites until cleaned up:
    Set-SPOSite https://muster.sharepoint.com/sites/hr `
      -RestrictContentOrgWideSearch $true
    • SharePoint Advanced Management
    • Microsoft Copilot
    • Restricted Content Discovery
    Chapter 4 · Documents and knowledge

    Site agent

    A site, a library or selected pages and files become an agent with a name, a purpose, behaviour and starter prompts. The owners set it as the site's default agent and share it by link, including into a Teams chat. The agent is a file in the library, with versions like any document.

    Security: The agent answers with the permissions of the person asking; it does not use a file that person may not open. Permissions on its file govern who may edit the agent.

    Where it runs: Agents in SharePoint; creating one needs a Microsoft Copilot licence, using one also works without a licence through pay-as-you-go billing with an Azure resource.

    ExampleProjekt-Agent Seeblick.agent
    agent:    Seeblick project agent
    file:     Seeblick project agent.agent
    sources:  /sites/Seeblick/Documents, /SitePages
    purpose:  questions on quotes, dates, plans
    behavior: answer with source, else refer to the PM
    starter:  Which quotes are still open?
    status:   default agent of the site
    • Agenten in SharePoint
    • Copilot in SharePoint
    • SharePoint Online
    Chapter 2 · Structure and navigation

    Sites and hubs

    A team site belongs to a Microsoft 365 group and so to a team in Teams; a communication site informs many readers with no group behind it. A hub gives the sites of one area shared navigation, design and search, while permissions stay per site. We build new sites from a template so each one starts the same way.

    Security: Every site has its own owners and permissions, inside a hub too. Who may create new sites and teams is set in the admin center.

    Where it runs: SharePoint Online with team, communication and hub sites, provisioned with PnP PowerShell and site templates.

    Exampleprovisioning/offerten.ps1
    New-PnPSite -Type CommunicationSite `
      -Title "Sales quotes" `
      -Url https://muster.sharepoint.com/sites/offerten
    Connect-PnPOnline -Url $offerten -Interactive
    Invoke-PnPSiteTemplate -Path .\templates\quotes.xml
    # template: library, content type, home page
    • SharePoint Online
    • Hub sites
    • Microsoft 365 Groups
    • PnP PowerShell
    Chapter 1 · Overview

    Skills (People Skills)

    Employees maintain their skills in the profile editor, or they come from the HR system. People Skills shows them on the profile card and in SharePoint people search. Custom attributes on the profile card stay invisible to search, which is why we carry expertise as skills.

    Security: Suggested skills appear only once the person confirms them. With People Skills switched on, the profile card shows only skills from People Skills, while those from the HR connector stay in search and Copilot Chat.

    Where it runs: People Skills, included with Microsoft 365 E3 or E5; AI suggestions require Microsoft Copilot or a Viva plan.

    Exampleprofile/skills-sandra.yaml
    person: sandra.beispiel@muster-ag.ch
    skills:
      - Fire protection         confirmed
      - Bern building law       confirmed
      - Revit                   suggested
    source: People Skills, profile editor
    • People Skills
    • Microsoft Copilot
    • Viva
    Chapter 1 · Overview

    Storage locations in Microsoft 365

    With OneDrive every person has a personal site, every team in Teams its team site, and private and shared channels one each of their own. Loop workspaces sit in SharePoint Embedded containers, and we use the same technology for custom applications when files should stay in the customer's tenant. The same Purview rules apply to all these places.

    Security: SharePoint Embedded containers are reachable only through their own application and Microsoft Graph. eDiscovery, retention, DLP and labels from Purview apply there as in any site.

    Where it runs: SharePoint Online, OneDrive and Teams sites in the tenant; SharePoint Embedded does not count against tenant storage and is billed by consumption through an Azure subscription.

    Examplestorage-map.txt
    Place                  Storage
    OneDrive               personal site
    Team, standard channel team site
    Private channel        own site
    Shared channel         own site (TEAMCHANNEL#1)
    Loop workspace         SharePoint Embedded
    Custom application     SharePoint Embedded
    • OneDrive
    • Microsoft Teams
    • SharePoint Embedded
    • Microsoft Graph
    Chapter 7 · Licences and cost

    Storage quota

    In the admin center the storage gauge shows that the tenant's pool is nearly full, and at the top of the list sits the site of a 2019 construction project with countless versions per drawing. Every site, team and Loop workspace shares this pool; it grows with the number of licences, OneDrive counts separately per person, and add-on storage can be purchased. Per site you set limits and see how much is used; version limits, the archive and a scan with Storage Monster empty the pool again.

    Security: Freeing storage means deleting: versions above the limit are gone for good after the clean-up, so every clean-up goes through an approval by the owners and is logged.

    Where it runs: Storage per tenant and per site in the SharePoint admin center, add-on storage through the Microsoft 365 admin center, version limits per tenant or library, analysis with Storage Monster by CNEXT.

    • Tenant-Speicher
    • Zusatzspeicher
    • Versionslimits
    • Storage Monster
    Chapter 6 · Migration

    Target structure

    Deep folder trees become sites with libraries, and metadata such as project number or document type organises the documents. Your owners decide the structure before the first file moves. Your team carries it on after handover.

    Security: In the target structure permissions sit on sites and groups. Individual shares on deep folders are planned only as justified exceptions.

    Where it runs: SharePoint Online with sites, libraries and content types, linked through a hub site and reachable from Microsoft Teams.

    ExampleMigrationsplan, Zielstruktur
    Site Projects    one library per project
      Metadata       project number, phase, doc type
      Groups         Projects-Read, Projects-Edit
    Site Finance     own permissions
    Hub              Muster AG intranet
    • SharePoint Online
    • Microsoft Teams
    • Hub Sites
    Chapter 3 · Content and editorial work

    Team pages and communities

    A welcome page per department or location introduces manager, buddy and team with the People web part. News about new colleagues is open for comments. In Viva Engage communities specialists talk across departments, and storylines appear in Teams too.

    Security: The pages show people through their profile card, so with the same approved fields. Communities in Teams run as a public preview and can be switched off in the Teams admin center.

    Where it runs: SharePoint pages with People and News web parts, audiences from Entra groups, communities and storylines in Viva Engage and Teams.

    Examplesites/willkommen-thun.yaml
    page:       Welcome to Thun
    audience:   Thun location
    web parts:
      - People:    manager, buddy, building team
      - News:      New here
      - Community: Project leads (Viva Engage)
    • SharePoint Online
    • Viva Engage
    • Microsoft Teams
    Chapter 4 · Documents and knowledge

    Term store

    Values such as customer, project phase or document type are defined once in the term store and apply in every library. Because everyone picks the same term, filters, views and search work across the whole collection. Synonyms lead to the same term, even when someone types an abbreviation.

    Security: A closed term set accepts only values the responsible person creates. That way no variants of the same customer appear.

    Where it runs: Managed metadata in the term store of the SharePoint admin center, columns of type managed metadata.

    Exampletermstore/muster-ag.yaml
    group: Muster AG
    termSet: Customers            # closed
      - Musterdorf municipality (synonym: Musterdorf)
      - Beispiel Immobilien AG
    termSet: Project phases
      - Preliminary design
      - Design
      - Acceptance
    • Managed Metadata
    • Term store
    • Microsoft Search
    Chapter 9 · Rollout and operations

    Usage reports

    After launch, page analytics show per page and news post how many people read it, through which channel and what share of the audience was reached; site usage in the admin center shows visits and active sites per month, and the query analytics of search show what people searched for without finding anything. From these three sources come the quarterly report to the management and the list of pages nobody reads any more. Names do not appear in the usage reports by default (as of 28 August 2026).

    Security: Reports with names are personal data: anonymisation stays switched on, and who reads the reports is written in the directive.

    Where it runs: Page analytics in SharePoint, usage reports in the Microsoft 365 admin center, query analytics of Microsoft Search, extended news analytics with a Viva licence.

    • Seitenanalyse
    • Nutzungsberichte
    • Microsoft 365 Admin Center
    • Abfrageanalyse
    Chapter 4 · Documents and knowledge

    Versions

    Where drafts come before approval, we work with major and minor versions and content approval. We set the version limit per library, automatic or manual, matched to recovery and storage. The version report and Storage Monster show beforehand which files take up a lot of version history.

    Security: Versions above the limit are deleted permanently, bypassing the recycle bin. Limits do not apply to content under a retention policy or an eDiscovery hold.

    Where it runs: Version settings per organisation, site or library in SharePoint, analysis with CNEXT's Storage Monster.

    Examplesites/projekte/versionen.yaml
    library:     Building projects
    versions:    major and minor
    approval:    yes   # drafts for editors only
    limit:       manual, 500 major versions
    expiry:      none
    beforehand:  version storage report
    • SharePoint Online
    • Storage Monster
    • Microsoft Purview
    Chapter 3 · Content and editorial work

    Viva Engage

    Under the news post on the new location, employees discuss in the «Thun plant» community, the management replies in its storyline, and a question from production gets an answer from maintenance within hours. Viva Engage carries these conversations: communities per topic or location, storylines per person, questions with a marked best answer. In the intranet the conversations appear through the Engage web part on the page of the respective community.

    Security: Communities can be open or private; posts are subject to retention and eDiscovery in Purview like Teams messages. Who moderates a community and what gets reported is settled by communications before the start.

    Where it runs: Viva Engage in Microsoft 365 and as an app in Teams, the Engage web part on SharePoint pages; in Teams, storylines are available and communities are in preview (as of 3 June 2026).

    • Viva Engage
    • Communities
    • Storyline
    • Microsoft Teams
    Chapter 6 · Migration

    Wave plan

    One area with real content goes first and shows what arrives and what does not. The waves then follow in the order your owners set. For every wave, communication, cutover and rollback are in the same document.

    Security: Areas with particularly sensitive data such as HR move only once their groups and labels have been checked in the target.

    Where it runs: Migration plan (template to download) as a Word document with sources, target structure, waves, communication, cutover and rollback.

    ExampleMigrationsplan.docx
    Pilot    Construction projects, real content
    Wave 1   other projects, quality
    Wave 2   finance, HR
    Wave 3   Access databases to Dataverse
    Rollback old area stays readable until acceptance
    • Microsoft Word
    • SharePoint Online
    • Dataverse

    Reference

    Agree on a useful next step

    Tell us about your current workflow, the systems involved and the result you need. In our first conversation we map your needs to the layers of the guide.