Guide SharePoint Intranet · Chapter 8

    Governance: how sites and data stay under control.

    Every site has owners, a name and an end, labels and retention take effect in Purview, data rests in Geneva and Zurich, and a backup brings back what was deleted.

    As of: October 2026 · Editor: Marcel Haas

    • Site lifecycle
    • SharePoint Advanced Management
    • Purview retention
    • Data location Switzerland
    • Microsoft 365 Backup
    • Admin roles
    01

    Every site is created by rule and has two owners.

    The procurement department of an industrial company starts a project and needs a site. Who may create it is controlled by a security group in Entra; everyone else submits a request that creates a site from a template with label, navigation and standard libraries and writes one row into the site register: purpose, division, owners, label, next review date. The naming rule puts the division's prefix in front of the name, the same in Teams, SharePoint, Outlook and the address book, and blocked words stay out. Every site has two owners from the start; the ownership policy finds sites that drop below that and keeps asking until someone steps in, and when a team loses its last owner, Microsoft 365 asks the most active members whether they will take over. Which kind of site a piece of content gets, communication site or team site, hub or channel, was settled in the chapter on structure and navigation; this chapter is about the rule by which it is created and the person who is accountable for it.

    02

    Inactive sites move to the archive, not to the recycle bin.

    One year after the project ended, nobody has opened the procurement site any more. The inactive site policy measures activity across SharePoint, Teams, Exchange and Viva Engage, writes the owners an email they answer directly in Outlook, and with no reply it sets the site to read-only and archives it after a set period with Microsoft 365 Archive; nothing is deleted, and an archived site stays under retention and findable in eDiscovery. Owners of active sites with a confidential label attest them on a fixed rhythm: purpose, members, guests, sharing. For Microsoft 365 groups the expiration policy from Entra lets active groups renew themselves; it deletes a group that is not renewed, restorable for a set period, which is why we switch it on only once ownership and retention are settled. Every policy runs first as a simulation with a report, so that your IT sees which sites it would hit before an email goes out. An archived team follows the same logic: channels, files and chats stay readable, the site becomes read-only for members.

    03

    Retention and records follow your periods, Purview enforces them.

    Which document type stays for how long is written in your retention schedule, by your specialists and not by IT. Purview enforces it: a retention policy on sites, teams and OneDrive keeps a copy even when someone deletes, and deletes at the end of the period; a retention label per document type comes from the content type, by hand or from a policy that labels by sensitive information, keywords and properties, with a simulation that shows beforehand which content it hits, and which never replaces a label already applied. At the end of the period a named person decides on deletion, in several stages, and disposed records remain provable. What has to stay unchanged becomes a record, as the chapter on documents and knowledge shows. Loop workspaces, Teams chats and meeting notes belong in the same schedule; Purview covers them, with gaps we know per content type before a period applies there. The retention schedule is also the place where data protection enters its deletion periods, so that policy and concept say the same thing.

    04

    DLP and the FADP: rules your data protection officer formulates.

    A clerk accidentally shares a list of AHV numbers through a link for everyone in the organisation: a DLP policy in Purview recognises the numbers as sensitive information, shows her a policy tip, blocks the share to the outside and reports the incident to the named function. The same rules apply to Copilot, which does not summarise sensitive content where the policy says so. We start in audit mode, read the matches with your data protection officer and only then switch to blocking, so that nobody gets stuck on a rule that misreads a form. The Swiss data protection act touches the intranet in several places, and at each of them your data protection officer asks the question, not we: does the people directory with photo, role and phone number belong in the register of processing activities, and what of it do guests see? How long do the comments and reactions of a person who leaves the company stay? Which usage data do the editors evaluate, and who sees it? When does a guest's access end? The legal assessment stays with your specialists; we deliver the setting that implements their answer, and the evidence in the tenant.

    05

    Data rests in Geneva and Zurich, with limits for Purview.

    Your tenant is in Switzerland: for SharePoint and OneDrive, Exchange Online, Teams and Microsoft Copilot the commitment for data at rest in the datacenters in Geneva and Zurich applies by default. For the SharePoint app in Teams, the web apps and Purview it applies only with the Advanced Data Residency add-on, and even then it covers Audit, retention, data loss prevention with the rules for Copilot, information barriers and information protection in Purview, but not eDiscovery and insider risk. Whoever writes "data in Switzerland" in the data protection concept therefore adds for which services and for which state: at rest, not in processing. Where Copilot and Foundry process, within the EU Data Boundary or in Switzerland North, is answered by the data boundaries chapter of the Microsoft AI/SI guide. For an intranet whose content is news, directives and directories the commitment is usually enough; for personnel files and patient data your data protection officer decides whether the add-on is added, and the chapter on permissions and sharing shows how that content gets rooms of its own.

    06

    A backup brings back what versions and the recycle bin do not hold.

    In everyday work employees retrieve overwritten versions and deleted files from the version history and the recycle bin themselves, and a retention policy keeps a copy on top. Against a mass deletion, encrypting malware or a script that empties the wrong library, a backup outside the library is needed. Microsoft 365 Backup protects SharePoint sites, OneDrive accounts and mailboxes in the tenant, bills by consumption through an Azure subscription and restores individual files and folders or whole sites to a point in time, with a recovery window the policy chooses. Our partner MOUNT10 backs up Microsoft 365 in Switzerland, apart from the tenant and under its own contract, which counts for organisations that require a copy outside the vendor's cloud. The backup is managed by a role of its own, separate from the owners of the sites, every restore is logged, and we practise it with you before it is needed.

    07

    Admin roles are separated, reports show the state.

    SharePoint, Teams and group administration are separated by task, and the roles are activated for a limited time through Privileged Identity Management, with a reason and an entry in the Entra audit log; Global Reader reviews without changing anything. In the SharePoint admin center you see the active sites with storage, owners and label, the data access governance reports show sites open to all employees, sharing links and the change history of the settings, and from the reports start the site access reviews the chapter on permissions and sharing describes. The SharePoint Admin Agent answers these questions in chat, which sites are shared too widely or hardly used and which agents access them most often, and suggests next steps; it needs an administrator role of its own. A quarterly meeting with IT, data protection and communications reads these reports together and records which policy is adjusted; whoever hands operations to us gets the same meeting in the contract.

    What you decide.

    Who creates sites and teams: everyone, the division leads or IT?

    Options

    1. 1All employees, with a naming rule and a label
    2. 2The division leads from a security group, everyone else by request with a template
    3. 3IT only, on application

    Our recommendation: The division leads from a security group, because they know which work a site needs, and everyone else through a request that creates a site from a template with label, navigation, standard libraries and a register entry; IT checks the requests that fall outside the template. Letting everyone create works with a naming rule and a mandatory label in small organisations where every site is known anyway. The rule stands in the site register, and the simulation of the policies shows after a quarter whether it has held.

    What we advise against: Every site only through IT on application: the project waits, and the work begins in a person's OneDrive, where no label, no ownership and no retention take effect.

    Inactive sites: delete, archive or keep read-only?

    Options

    1. 1Delete after a period, with restore from the recycle bin
    2. 2Set to read-only and archive with Microsoft 365 Archive
    3. 3Keep read-only, without an archive

    Our recommendation: Set to read-only and archive after a period, through the inactive site policy, after the owners have been asked: the site no longer takes active quota, stays under retention and findable in eDiscovery and comes back with all its rights when someone needs it. Deletion runs through retention: when the period of the policy or the label ends and the named person approves the deletion. Read-only without an archive suits sites that are still read, such as withdrawn directives.

    What we advise against: Switching on the group expiration policy before ownership and retention are settled: it deletes groups that are not renewed, and the restore runs against a deadline.

    Backup: Microsoft 365 Backup, MOUNT10 or both?

    Options

    1. 1Microsoft 365 Backup in the tenant, by consumption
    2. 2The MOUNT10 backup in Switzerland, outside the tenant
    3. 3Both, with separate tasks

    Our recommendation: Microsoft 365 Backup for the fast restore in the tenant, individual files and folders up to the whole site, with a recovery window per site class, because it sits where the owners work. The MOUNT10 backup where a requirement or a management decision demands a copy outside the vendor's cloud, with its own contract and its own role. Both when both apply, with the split of which backup covers which case; what is neither case stays with versions, recycle bin and retention.

    What we advise against: Relying on version history and the recycle bin for libraries with evidence: against a script that empties the wrong library or encrypting malware, neither holds.

    Buy Advanced Data Residency or stay with the default commitment?

    Options

    1. 1The default commitment for data at rest in Geneva and Zurich
    2. 2The Advanced Data Residency add-on for Purview, the web apps and the SharePoint app in Teams
    3. 3The add-on only for the services that carry personal data

    Our recommendation: The default commitment for an intranet with news, directives and directories: for SharePoint and OneDrive, Teams and Copilot it applies without an add-on. The add-on when your data protection officer requires that the protection mechanisms in Purview, Audit, retention, data loss prevention, information protection, rest in Switzerland too, or when personnel files and patient data run through the SharePoint app in Teams. In every case the concept states which services the commitment covers and that eDiscovery and insider risk are not among them.

    What we advise against: Booking the add-on as general reassurance without naming in the concept which services it covers and which it does not: the commitment is then read as larger than it is.

    Status and sources.

    As of: October 2026

    • As of 1 April 2026

      Swiss tenants: data at rest in Geneva and Zurich.

      Switzerland is a local region geography of Microsoft 365 with datacenters in Geneva and Zurich. For Exchange Online, SharePoint and OneDrive, Teams and Microsoft Copilot the data residency commitment for data at rest applies by default; for Defender for Office 365 Plan 1, the web apps, the SharePoint app in Teams and Purview only with the Advanced Data Residency add-on.

      Source: Microsoft Learn: Data residency for Microsoft 365
    • As of February 2026

      Which Purview services the data residency commitment covers.

      With Advanced Data Residency the commitment applies to Audit, retention, data loss prevention including the rules for Copilot, information barriers and information protection with sensitivity labels and message encryption. Other Purview services such as eDiscovery and insider risk are not covered.

      Source: Microsoft Learn: Data residency for Microsoft Purview
    • As of 1 July 2026

      Site policies end in read-only and archive.

      The policies for ownership, inactivity and attestation run as a one-off simulation with a report or in active mode with recurring notifications that owners answer directly in Outlook. If no reply comes, the policy can set the site to read-only and archive it with Microsoft 365 Archive after a set period. No site is deleted directly.

      Source: Microsoft Learn: SharePoint site lifecycle management
    • As of 26 February 2026

      Apply retention labels automatically, simulate first.

      A policy applies retention labels based on sensitive information, keywords and searchable properties, or trainable classifiers; it never replaces a label that is already applied. For information types and queries, a simulation mode shows in advance which content would match. Labels can take up to seven days to be applied, and classifiers only cover SharePoint and OneDrive content from the last six months.

      Source: Microsoft Learn: Automatically apply a retention label
    • As of 22 July 2026

      Up to five review stages before deletion.

      A retention label can trigger a review at the end of the retention period: the named people receive an email, see the content and approve deletion, extend the period or apply a different label. Up to five stages can run one after another, optionally with auto-approval after 7 to 365 days. After the final approval, content is permanently deleted within 15 days, and disposed records remain documented in the overview.

      Source: Microsoft Learn: Disposition of content
    • As of 21 September 2026

      Microsoft 365 Backup: restore of individual files and folders, recovery windows up to two years.

      Microsoft 365 Backup protects SharePoint sites, OneDrive accounts and Exchange mailboxes and is billed on consumption through an Azure subscription, not per user. Since September 2026 individual files and folders can be restored, and policies can choose recovery windows from three months to two years.

      Source: Microsoft Learn: What's new in Microsoft 365 Backup
    • As of 9 October 2026

      The SharePoint Admin Agent answers governance questions in chat.

      The agent is part of SharePoint Advanced Management and runs in the Copilot app, in Teams and in the admin center. Administrators ask, for example, which sites are overshared, which see little use or which agents access your sites and OneDrive storage most often; it gathers the reports and suggests next steps. It requires a dedicated administrator role for it in Entra ID.

      Source: Microsoft Learn: SharePoint Admin Agent overview

    Frequently asked questions.

    Does Microsoft 365 Archive delete content after a period?

    No. The archive is a cold storage tier within SharePoint: the site no longer takes active quota, stays findable through search, Content Search and eDiscovery and keeps metadata, permissions and retention. Only what your retention policy or label deletes at the end of its period is deleted, after the review by the named person. The inactive site policy archives; it deletes no site directly.

    Who brings an archived site back?

    SharePoint administration, from the list of archived sites in the admin center; an owner asks for it, usually through a ticket. The site comes back with all its metadata and permissions, and the members carry on as before. Some apps cannot open archived files yet, and a reactivated file cannot be archived again until a waiting period has passed; that is why we reactivate a site as a whole when a division needs it again, and not individual files for a quick look.

    Are version history and the recycle bin enough as a backup?

    For everyday work, yes: an overwritten version comes back from the version history, a deleted file from the recycle bin, and a retention policy keeps a copy even when someone empties the recycle bin. Against a mass deletion, encrypting malware or a script that hits the wrong library they are not enough, because they sit in the same tenant and under the same rights. For that there is Microsoft 365 Backup with a recovery window per policy, or the MOUNT10 backup outside the tenant.

    Does the Swiss data location also apply to the SharePoint app in Teams?

    For the content itself, yes: news, pages and documents live in SharePoint, and for them the commitment for data at rest in Geneva and Zurich applies by default. For the app in Teams as a service, as for the web apps and Purview, the commitment applies according to Microsoft only with the Advanced Data Residency add-on. Whether that makes a difference for your intranet depends on what runs through it; for news and directives usually not, for personal data your data protection officer decides.

    What happens to the documents when someone deletes a site whose retention policy is still running?

    The policy holds on to the content: a site under a retention policy cannot simply be removed while the policy applies; administration first has to take it out of the policy, and that step is in the Purview audit log. Deleted files from a site under retention stay in the preservation hold library until the period ends and are findable through eDiscovery. That is why we put the policies on sites before the first library is filled.

    Which details about the intranet belong in the register of processing activities?

    Your data protection officer decides; we deliver the technical description for it. Typical entries are the people directory with photo, role and phone number, with its source in Entra or the HR system, the fields and the circle that sees it; the usage evaluation with granularity, purpose and retention of the figures; and guest access with the data guests see and the period after which it ends. For every entry, storage location, retention and access are in the setting we hand over.

    What is the difference between owner attestation and the site access review?

    Attestation asks the owners on a fixed rhythm whether the site is still needed and whether purpose, members, guests and sharing are right; with no reply the site goes read-only. The site access review is started by administration from the reports on sharing and permissions for individual sites, and the owners see the most widely permissioned items first and adjust them. One keeps the estate healthy, the other cleans up a finding; the owners do both themselves, and both are in the audit log.

    Next chapter · Chapter 9

    Who does what, so that the intranet stays alive.

    Who does what, so that the intranet stays alive?