Secure by default with Microsoft Purview, step by step.

Labelling projects slow down over three things: agreeing the label set, worrying that encryption will break people’s work, and waiting for manual or automatic labelling to catch up. Microsoft’s Purview engineering team publishes a different model. Label everything Confidential by default, let SharePoint sites set the label for their files, and train people to change the label when they need to share.

This page takes that model through the four steps Microsoft Learn sets out, with the label set it recommends and its engineers’ notes. It is for the Purview administrator planning the rollout. Microsoft’s planning guide allows about a week for step 1.

Protect by default, then teach the exceptions.

In the usual approach, people decide when to protect a file. Here everything starts protected, and people decide when to share. Microsoft sums it up as training users to manage exceptions instead of when to protect.1

01 Protect the default label

  • One default for everyone. Confidential\All employees opens for anyone in the organisation and no one else. You choose where it is the default: in Office apps, in SharePoint sites, or both.1, 2
  • Sites set the label. A SharePoint library’s default label applies to new and edited files saved there, so each site can have its own default.21
  • DLP holds the line. A DLP rule blocks external sharing and Anyone links for the default label. Encryption, if you add it, stays with the file wherever it goes.2, 24
  • Auto-labelling only raises. In this model, auto-labelling is kept for content that needs more protection than the default, such as credentials.1, 3

02 Train people to manage exceptions

  • Sharing is the exception. People change the label when they need to share, for example to General for a trusted partner. Site labels keep those changes rare.2
  • DLP checks what is shared. Sensitive information types and classifiers catch sensitive content in files someone has relabelled to share.5
  • Insider Risk watches downgrades. Insider Risk Management can alert when people lower labels, then download or send that content out.3
  • Copilot keeps the label. When Microsoft 365 Copilot creates content from labelled files, the new content takes the highest-priority label among them, where supported.26

You decide how much protection the default carries at each point. Microsoft gives this as an example of a measured start:1

  1. SharePoint defaults to Confidential\All employees without encryption, and DLP stops it being shared externally. Everything else defaults to General.
  2. The default extends to every file in the Office apps, and emails inherit the label of the files attached to them.
  3. Encryption is added to Confidential\All employees.

Eight labels, named for how they protect.

Start with four labels, and give the two sensitive ones three sublabels each. Microsoft recommends this set for most organisations; if you already have labels, adapt them to it.2

Labels

  • Public. Unrestricted data meant for the public, such as released source code and announced financials. Share it freely.
  • General. Business data not meant for the public, such as daily work. You can share it internally and with trusted partners.
  • Confidential. Sensitive business data that matters to your organisation’s goals. Limited distribution.
  • Highly Confidential. Your most critical data. Share it only with named recipients.

Sublabels of Confidential and Highly Confidential

  • \All employees. Anyone in the organisation can open it.
  • \Specific People. Only the people the author names can open it.
  • \Internal exception. Anyone inside can open it, but it can’t be shared outside. It carries no encryption, for the processes and add-ins that break when files are encrypted.

Sources 2

If people keep personal content on managed devices, add a Personal or Non-business label at the lowest priority, with no protection.2

Recommended labels and settings 2, 3

LabelDefault or auto-labellingEncryptionDLP limits
PublicNoneNoneNone. Files and email only.
GeneralDefault for email, and the label for sites shared with partnersNoneBlock Anyone links
Confidential\All employeesDefault for documents and sitesEveryone in the organisation, Co-Author. Can be added later.Block Anyone links, block external
Confidential\Specific PeopleNoneUsers assign permissions: Encrypt-Only in Outlook, a prompt in Word, Excel and PowerPointBlock Anyone links
Confidential\Internal exceptionNoneNoneBlock Anyone links, block external
Highly Confidential\All employeesAuto-labelling, in the apps and at restEveryone in the organisation, Co-AuthorBlock Anyone links, block external
Highly Confidential\Specific PeopleRecommended in the apps for credentialsUsers assign permissions: Do Not Forward in Outlook, a prompt in Word, Excel and PowerPointBlock Anyone links, block external
Highly Confidential\Internal exceptionNoneNoneBlock Anyone links, block external

Every label except Public covers files, email and sites, and meetings where your licences allow. The Confidential and Highly Confidential labels add a footer, for example “Classified as Confidential”.2

For sites, use the labels to set privacy to Private and the default sharing link to People in your organization. Private sites with organisation-wide links keep collaboration open but reduce the chance of content turning up in search and Copilot for people who were never meant to find it. For more protection, make Specific people the default link; Microsoft’s deck does this for the Internal exception and Highly Confidential labels.2, 18

A DLP policy can also keep Microsoft 365 Copilot, Copilot Chat and Cowork from using files and emails that carry the labels you choose, such as Highly Confidential. Those items can still appear in the citations of a response.27

Labels where users assign permissions, such as the Specific People labels, can also keep Copilot from using a file’s content, and Copilot agents can’t read those files.26

Four steps, from new files to data outside Microsoft 365.

Microsoft’s blueprint sets out the model in four columns, which Microsoft Learn publishes as four steps. Each has four activities, one outcome and an effort. The sections after it take the steps one at a time.1, 2

Purview secure by default blueprint: Foundational, Managed, Optimized, Strategic
Blueprint · Microsoft Purview product engineering, via Microsoft Learn Secure by default with Microsoft Purview. The blueprint names its columns Foundational (step 1), Managed (step 2), Optimized (step 3) and Strategic (step 4). Its efforts are Microsoft’s planning guide, not a commitment.

The blueprint as a table

StepActivitiesOutcomeEffort
Step 1 · Start with default labelingStart with default labels and protection at file and site level. Turn on data security prerequisites and advanced analytics. Train users on managing exceptions. Turn on DLP for labelled content.Microsoft 365 new and updated content protected1 week
Step 2 · Address files with the highest sensitivityManually configure priority sites’ default library labelling. Auto-labelling for credentials and contextual conditions. Turn on DLP for content that is not labelled. Turn on Adaptive Protection and data leak behavioural rules.Microsoft 365 priority content protected2 weeks
Step 3 · Expand protection to your entire Microsoft 365 data estateAuto-label sensitive files on clients (low thresholds). Simulate auto-labelling sensitive files at rest. Reduce false positives with advanced classifiers. Automate and improve Microsoft 365 protection to historical and in-use data.Microsoft 365 historical content protected2-week iterations
Step 4 · Operate, expand, and retroactive actionsOperational review of user labelling behaviours. Iterate with new labelling scenarios. Set up accountability chain and lifecycle management. Extend protection to Azure SQL and non-Microsoft 365 storage.Protection beyond Microsoft 365Situational

Label everything new, and keep it inside.

Outcome
Microsoft 365 new and updated content protected
Effort
1 week

This step makes new and unlabelled documents Confidential\All employees and every email General, and stops Confidential\All employees files leaving the organisation. Files people already labelled keep their labels, and nothing is relabelled in bulk yet. Do the tasks in order: the switches in tasks 2 to 5 have to be on before people see the labels.2, 6

  1. Create the eight labels

    Solutions › Information Protection › Sensitivity labels › Create a label

    Create Public, General, Confidential and Highly Confidential, then the three sublabels under each of the last two. Use the names, encryption and settings in the label table in section 02. How you build the two tiers depends on your tenant’s label scheme.2, 8

    On the modern scheme, used by recently created tenants and tenants with no labels yet, Confidential and Highly Confidential are label groups. Select + Create, then Label group. Then select each group, ... for Actions, and Create label in group for its three sublabels.6, 8

    On the classic scheme, they are parent labels. Select each one, ... for Actions, then Create sublabel. Never make a parent label a default or an auto-labelling target, because it can’t be applied.6, 8

    Give General and the six sublabels the scopes Files & other data assets, Emails and Groups & sites, and Meetings if your licences cover it. Add the footer marking to the six sublabels, for example “Classified as Confidential”. A label group or parent label needs neither, as it can’t be applied by itself.2, 6, 9

    List them from least sensitive at the top to most sensitive at the bottom. The further down the list, the higher the label’s priority, and priority decides which label wins when two apply.6

    Purview label scope page with the Groups & sites scope outlined
    The label wizard’s scope page. Groups & sites appears once labels for sites are turned on in task 4; come back and add it then. Screenshot · Microsoft Learn, Use sensitivity labels to protect collaborative workspaces (groups and sites)

    Check The Sensitivity labels page lists the eight labels, with the sublabels under Confidential and Highly Confidential.8

  2. Turn on labels for files in SharePoint and OneDrive

    Solutions › Information Protection › Sensitivity labels › Turn on now

    Signed in as a Global Administrator, select Turn on now in the banner on the Sensitivity labels page. Without this, SharePoint and OneDrive can’t read encrypted files, so co-authoring, search, eDiscovery and DLP stop working for them. Allow about 15 minutes for the change to take effect.12

    A SharePoint Administrator can do the same in SharePoint Online PowerShell with Set-SPOTenant -EnableAIPIntegration $true. Multi-Geo tenants have to use PowerShell.12

    For PDF support, go to Auto-labeling policies under Policies and select the Protect PDFs with Auto-labeling banner if it shows. Or run Set-SPOTenant -EnableSensitivityLabelforPDF $true in SharePoint Online Management Shell 16.0.24211.12000 or later. Labels don’t support signed PDFs.12

    Purview sensitivity labels banner to turn on encrypted Office online files
    The banner on the Sensitivity labels page that turns the setting on. Screenshot · Microsoft Learn, Enable sensitivity labels for files in SharePoint and OneDrive
  3. Turn on co-authoring for labelled files

    Settings › Solution settings › Information Protection › Co-authoring for files with sensitivity labels

    Read the prerequisites on the page, select Turn on co-authoring for files with sensitivity labels, then Apply. Allow 24 hours before you rely on it.14

    Purview setting to turn on co-authoring for files with sensitivity labels
    The tenant setting. It needs at least the Information Protection Admin or DLP Compliance Management role. Screenshot · Microsoft Learn, Enable co-authoring for encrypted documents

    Watch out

    Co-authoring changes where Office files keep their label information. Once on, it can only be turned off with PowerShell, and label information for unencrypted files is lost when you do. Before you turn it on, check that Office meets the minimum versions and that every app, script and tool that reads labels supports the new format.14

  4. Turn on labels for sites and groups

    Site labels use Microsoft Entra. An Entra administrator follows “Enable sensitivity label support in PowerShell” in Microsoft’s Entra article. In short: Connect-MgGraph -Scopes "Directory.ReadWrite.All", find the group settings with Get-MgBetaDirectorySetting, then set EnableMIPLabels to True with Update-MgBetaDirectorySetting. If the tenant has no group settings yet, the article shows how to create them first.13, 15

    Then, in Security & Compliance PowerShell signed in as a Global Administrator, run Execute-AzureAdLabelSync to sync your labels to Entra.13

    Go back to each label except Public and add the Groups & sites scope from task 1.6

    Check In the SharePoint admin center, select a site in Active sites, then Policies and Edit beside Sensitivity. Admin centers list every label, published or not, so your labels with the Groups & sites scope show here.13

  5. Turn on the remaining prerequisites

    The model relies on these settings. Check each one, and turn on any that are off:2

    1. Mark new files as sensitive by default, so guests can’t open a new file until DLP has scanned it: Set-SPOTenant -MarkNewFilesSensitiveByDefault BlockExternalSharing.16
    2. SharePoint and OneDrive integration with Microsoft Entra B2B needs nothing from you: it is always on in commercial tenants. SharePoint’s one-time passcodes are being retired, so external people without a guest account lose access to files shared with them through Specific people links. Use the audit log to find people who still sign in with a passcode, then create guest accounts for them or share again.17
    3. Auditing, which auto-labelling simulation depends on.22
    4. DLP analytics, which is in preview. A Global Administrator or Compliance Administrator turns it on from the Data loss prevention Overview page, and its first recommendations take seven days.2, 36
    5. Insider Risk Management analytics, whose first scan can take up to 48 hours, and its indicators (the user activities Insider Risk looks for). Step 2 then has data to start from.2, 37

    Leave the label mismatch email on, so site owners hear when someone saves a more sensitive file into their site. Set-SPOTenant -LabelMismatchEmailHelpLink adds your help page to the email.2, 13

    Check In SharePoint Online PowerShell, (Get-SPOTenant).BlockSendLabelMismatchEmail returns False.13

    Watch out

    With new files marked sensitive by default, guests can’t open any new file in a location that no DLP policy covers. Run that cmdlet only once task 9’s DLP policy covers SharePoint and OneDrive. It can take up to 60 minutes to take effect.16

  6. Publish the labels and set the defaults

    Solutions › Information Protection › Publishing policies › Publish label

    Publish all eight labels, to a few test users first and then to everyone. In the policy settings:2, 8, 12

    • Set Confidential\All employees as the default label for documents, and for groups and sites.2, 6
    • Set General as the default label for email, and turn on label inheritance from email attachments.2, 11
    • Require people to give a reason when they lower or remove a label.6
    • Add the address of your help page as the custom help link.6

    For the measured start in section 01, default the Office apps to General instead. Set Confidential\All employees only as SharePoint library defaults until you are ready to widen it.1

    Office Sensitivity menu listing labels with a Learn More link highlighted
    The custom help link appears as Learn More under the labels. Screenshot · Microsoft Learn, Learn about sensitivity labels

    Why General on email lets people keep working normally, while each attachment carries its own protection.2

    Check Allow up to 24 hours for the policy to reach the apps. A new Word document then opens as Confidential\All employees, and Word, Excel and PowerPoint for the web show the Sensitivity button. A new SharePoint site offers your labels under Sensitivity in its advanced settings.6, 12, 13

    Watch out

    New labels take time to reach SharePoint and OneDrive, especially ones that encrypt. Publish to a few test users, wait at least an hour, then check the labels there and create a test site with a site label. Wait at least a day before you add everyone.12, 13

  7. Set site privacy and sharing links

    In each site label, set privacy to Private. If many of your sites are Public today, move them to Private and rely on organisation-wide links instead.2, 13

    The default sharing link has no setting in the portal. Set it on each site label in Security & Compliance PowerShell, for example Set-Label -Identity {label GUID} -AdvancedSettings @{DefaultSharingScope="Organization"}. The label’s scope must include Groups & sites.18

    Then apply the labels to existing sites in the SharePoint admin center: Active sites, select the site, Policies, then Edit beside Sensitivity. Or leave that to site owners in step 2.13

    SharePoint site header showing its Confidential sensitivity label
    A labelled site shows its privacy and label under the site name. Screenshot · Microsoft Learn, Use sensitivity labels to protect collaborative workspaces (groups and sites)
    SharePoint Send link dialog defaulting to people in the organisation, can edit
    A default sharing link of People in your organization, as people see it when they select Share. Screenshot · Microsoft Learn, Use sensitivity labels to configure the default sharing link type for sites and documents in SharePoint and OneDrive

    Why A Private site with organisation-wide links collaborates as freely as a Public one, but its content is less likely to surface in search and Copilot for everyone.2

    Watch out

    A site label’s privacy setting replaces the site’s own and locks it. Label a Public site with a Private label and only its members can reach it. Check membership before you label existing sites.13

  8. Train people on exceptions

    Teach the exceptions, not the labels. Explain why everything is now Confidential and how site labels set the label on files. Show how to change a label to work with a trusted partner, and whether to share from OneDrive or a SharePoint site. Cover what to do when an add-in stops working with encryption, and that lowering a label asks for a reason.2

    Microsoft’s three examples are a good script. John checks a file, finds it isn’t confidential, changes it to General and shares it. Jane works with a partner in a SharePoint site labelled General, so every file there can be shared, and she is told if a Confidential file lands in it. Jack’s Excel add-in fails with encryption, so he uses Confidential\Internal exception.2

    Office Justification Required dialog for removing or lowering a label
    What people see when they lower a label, once the policy asks for a reason. Screenshot · Microsoft Learn, Learn about sensitivity labels

    Watch out

    Label order decides what applies. If General sits below Confidential\All employees and the Office apps default to Confidential\All employees, a SharePoint library default of General doesn’t apply. A higher-priority Internal exception label also skips the reason prompt. On the modern scheme, moving between sublabels in one label group asks for no reason either. Check your label order before you publish.2

  9. Turn on DLP for labelled content

    Solutions › Data loss prevention › Policies › Create policy

    Create a custom policy for Exchange, SharePoint and OneDrive. In each rule, add the condition Content contains, then Sensitivity labels, and pick the labels.19, 33

    For Confidential\All employees, block sharing with anyone with the link and with people outside the organisation. Use the DLP limits column in the label table for the other labels. Run the policy in simulation first, then turn it on.2, 33

    Content that is already shared and matches a rule raises alerts, and people see policy tips.2

    Microsoft’s lightweight guide to mitigate data leakage turns a similar rule on at once, for speed in a small tenant. This model simulates first.33, 44

    Purview DLP rule Content contains condition offering Sensitivity labels
    Adding sensitivity labels as a DLP condition. Screenshot · Microsoft Learn, Use sensitivity labels as conditions in DLP policies

Done when New documents open as Confidential\All employees and emails default to General. A new site is Private with People in your organization as its default link, and a test share of a Confidential\All employees file to an outside address is blocked.

Next Pick your priority sites for step 2.

Reach the files that matter most first.

Outcome
Microsoft 365 priority content protected
Effort
2 weeks

Step 1 protects what people create from now on. This step reaches files that already exist, starting with the sites that hold the most sensitive ones.3

  1. Choose the priority sites

    Solutions › Information Protection › Explorers › Data explorer

    Start with the sites everyone knows matter, such as leadership team sites. Add the sites that content explorer (classic) or data explorer shows holding many sensitive documents, and any your reports single out. Both explorers are Purview’s views of where sensitive and labelled files sit. If files already default to Confidential\All employees, focus on sites that need a higher label.3, 39, 40

    Seeing the items themselves needs the Content Explorer List viewer role group on top of an admin role, and seeing what is in them needs Content Explorer Content viewer. Data explorer has equivalent role groups.39, 40

  2. Label each site and its libraries

    SharePoint admin center › Active sites › {site} › Policies › Sensitivity › Edit

    Put a sensitivity label on the site, then set a default label on each document library in its Library settings. Site owners can do both; a SharePoint Administrator can set the site label from the Active sites page.3, 13, 21

    A library’s default label applies to files when they are uploaded, created or edited there. It never replaces a label someone chose by hand.21

    Check In Active sites, add the Sensitivity column to see each site’s label.13

    Watch out

    A library default can’t be a label that prompts people for permissions in Word, Excel and PowerPoint, one whose access expires, or one that uses Double Key Encryption. So the Specific People labels can’t be library defaults; Confidential\All employees can.21

  3. Label the files already there

    Solutions › Information Protection › Policies › Auto-labeling policies

    A library default doesn’t touch files already at rest. Create an auto-labelling policy scoped to these sites, with the condition File extension is set to docx, xlsx, pptx and pdf, applying the site’s label. A policy applies one label, so create one policy for each site label.2, 3, 21, 22

    Or use the policy type that applies each library’s default label to its existing files. It reads no content, just the library setting. You can have one such policy, naming up to 10 specific sites. When those are labelled, edit the policy to name the next 10.22

    Run the policy in simulation, review what it would label, then turn it on. Turning it on needs Compliance Administrator or Compliance Data Administrator.22

    The wizard can also turn the policy on by itself after 7 days in simulation, and the option may already be ticked. Clear it if you want to review the results before anything is labelled.22

    Purview auto-labelling policy locations: Exchange, SharePoint sites, OneDrive
    Scope the policy to the priority sites. Screenshot · Microsoft Learn, Automatically apply a sensitivity label to Microsoft 365 data
    Purview auto-labelling policy in simulation mode, turns on after 7 days
    Every auto-labelling policy runs in simulation before it labels anything. Screenshot · Microsoft Learn, Automatically apply a sensitivity label to Microsoft 365 data

    Check After you turn the policy on, its details page lists the files it labelled.22

  4. Auto-label credentials

    Solutions › Information Protection › Sensitivity labels › {label} › Edit label › Auto-labeling for files and emails

    Attackers value credentials above everything else, so label them wherever they appear. In the Highly Confidential\Specific People label, turn on auto-labelling for the All credentials sensitive information type, for the Office apps. Choose to recommend the label to the user, not to apply it.3, 22

    A label where users assign permissions can be recommended, but applied automatically only for its Do Not Forward and Encrypt-Only options in Outlook.24

    For files at rest, create an auto-labelling policy with the same condition that applies Highly Confidential\All employees.3

    Purview label auto-labelling for files and emails on, Content contains condition
    Auto-labelling in the Office apps is set on the label itself. Screenshot · Microsoft Learn, Automatically apply a sensitivity label to Microsoft 365 data
    Word policy tip recommending a sensitivity label for credit card numbers
    Microsoft’s example of a recommended label in Word, with the content that triggered it. Learn’s example recommends Confidential\All Employees; here it would be Highly Confidential\Specific People. Screenshot · Microsoft Learn, Automatically apply a sensitivity label to Microsoft 365 data

    Why Service-side auto-labelling in SharePoint and OneDrive can only apply an encrypting label that assigns permissions now, which the Specific People labels don’t.22

  5. Block unlabelled files from leaving devices

    Settings › Device onboarding › Devices

    Onboard the devices first. Devices already onboarded to Microsoft Defender for Endpoint appear in the list and need no more steps.34, 38

    Then add a DLP rule with the condition Content is not labeled, scoped to Office and PDF file types, for devices and Exchange. On devices, block actions such as upload to cloud services. People then have to open and label a file before they can upload it to a website.3, 20

  6. Turn on Adaptive Protection

    Insider Risk Management › Adaptive protection › Dashboard › Quick setup

    Insider Risk Management can alert when people lower labels and then download, disguise or send out that content. Adaptive Protection feeds each person’s risk level into DLP. A rule can just audit when most people share a General file, and block the same share for someone flagged as high risk.3, 23

    Quick setup creates a Data leaks insider risk policy and its risk levels, and two DLP policies in test mode. It also creates a Conditional Access policy in report-only mode and a data lifecycle management policy, both from integrations in preview.23

    Setup can take up to 72 hours; don’t turn it off before it finishes. A scoped Purview admin can’t run it. Test the policies, then add the Adaptive Protection condition to your existing DLP rules where it fits.3, 23

Done when Priority sites carry a site label and library defaults, their existing Office and PDF files are labelled, credentials are auto-labelled, and devices refuse to upload unlabelled files.

Next Plan the first round of step 3.

Label the rest of Microsoft 365, in rounds.

Outcome
Microsoft 365 historical content protected
Effort
2-week iterations

Work through the rest of the estate in rounds; Microsoft’s planning guide allows about two weeks each. In this step, auto-labelling is only for content that needs more than the default label.4

  1. Recommend labels in the Office apps

    Solutions › Information Protection › Sensitivity labels › {label} › Edit label › Auto-labeling for files and emails

    Pick the sensitive information types (Purview’s built-in detectors for data such as card numbers) that matter for your industry from the 300 or more built in. Recommend a label when a file holds a few matches, and apply it automatically when it holds many or a trainable classifier matches. Microsoft’s example thresholds are 1 to 9 matches to recommend and 10 or more to apply.4

    People can accept a recommendation or report it as wrong, which tells you where a rule is too eager.3

    Word policy tip saying a sensitivity label was applied automatically
    Microsoft’s example of a label applied automatically in Word. Learn’s example applies Confidential\All Employees; in this model the rule would apply a Highly Confidential label. Screenshot · Microsoft Learn, Automatically apply a sensitivity label to Microsoft 365 data

    Why With Confidential\All employees as the default, these rules only ever need to reach Highly Confidential, which keeps them simple.4

  2. Simulate labelling at rest

    Solutions › Information Protection › Policies › Auto-labeling policies

    Service-side auto-labelling labels files at rest in SharePoint and OneDrive. Run each policy in simulation first. A simulation can match up to 20,000,000 files; above that you can’t turn the policy on until you narrow it. A tenant can label up to 500,000 files a day, with up to 100 policies, each naming up to 1,000 sites.4, 22

    At rest you can use conditions the apps can’t: content is shared, file extension, document name, document property, size, and who created it. Use them to go first where it matters, such as files built on a template with a set property, or files created by the leadership team.4

    To finish, label Office and PDF files in batches of sites, each to match its site’s label. Start with the more sensitive sites and end with the General ones. Then add Highly Confidential rules at higher thresholds than you use in the apps.4

    We recommend giving each batch’s site owners a date in advance, so the labels they find are expected.4

    Check Open the policy and select View details to see the simulation’s matched files before you turn it on.22

  3. Cut false positives

    Built-in types such as personal or health information match patterns and keywords without context, so they misfire. To tighten them:4

    • Raise the confidence level and the match count.4
    • Require two types together (AND) rather than either (OR).4
    • Copy a built-in type into a custom one and tune it, using several narrow patterns rather than one wide one, and whole-word matches.4
    • Add trainable classifiers, exact data match or document fingerprinting.4

    A trainable classifier paired with a type narrows matches, for example credit card numbers in documents the Financial information classifier recognises. Exact data match checks a match against a hashed copy of your own records. Document fingerprinting recognises your standard forms, and is used in DLP rather than auto-labelling.4

    We recommend reviewing each simulation’s matched files for false positives, and tuning the rule, before you widen a policy to more sites.4, 22

    Purview SIT conditions, each with a confidence level and instance count
    Confidence level and instance count are set per type, in the condition. Screenshot · Microsoft Learn, Automatically apply a sensitivity label to Microsoft 365 data

    Check Office app auto-labelling can now use exact data match types, as long as the label also names at least one type that doesn’t use exact data match.22

  4. Label the sites that are left

    By now the defaults stop new unlabelled sites and files appearing. For the rest, use the approach that fits your risk:4

    • Ask site owners. Tell them to label their site and its libraries by a date, and that sites still unlabelled then get a default.4
    • Script it. Find unlabelled sites in the SharePoint admin center (Active sites, with the Sensitivity column added) or with Microsoft Graph, and set the site label and library default to Confidential\All employees.4, 13
    • Let DLP carry it. Leave old sites as they are and rely on DLP for unlabelled content while they age out.4
    • Follow the site labels. Note when each site gets its label, and add newly labelled sites to your service-side auto-labelling policies.4

    In SharePoint Online PowerShell, Set-SPOSite -Identity {site URL} -SensitivityLabel {label GUID} labels a site. There is no SharePoint Online cmdlet for a library default: set it in the library’s settings, or in a script through the SharePoint REST API property DefaultSensitivityLabelForLibrary.4, 13

Done when Every site has a label, libraries have defaults, older Office and PDF files carry their site’s label, and Highly Confidential rules run at rest.

Next Hand the steady state to operations in step 4.

Review on a schedule, and widen the model.

Outcome
Protection beyond Microsoft 365
Effort
Situational

Review labelling on a schedule, and extend the model to the cases the first three steps left out. This step has no end date.5

  1. Review labelling regularly

    SharePoint admin center › Reports › Data access governance

    • Unlabelled sites and teams. Find them in the SharePoint admin center’s Active sites list or with Microsoft Graph, then contact the owners or fix them.5, 13
    • Site and library mismatches. Find sites whose library default doesn’t match the site label, the same way.5
    • Where labelled files sit. The data access governance report for sensitivity labels lists the SharePoint sites holding the most files with a label you choose. It covers SharePoint only, not OneDrive, and only labels scoped to files. A report can take up to 24 hours.35
    • Unprotected labels. Use DLP with sensitive information types to catch sensitive content under General or Internal exception when someone tries to share it.5
    • Risky people. Review Insider Risk Management alerts and its audit log, tune the policies, and tighten Adaptive Protection.5
    SharePoint admin center sensitivity label report with one label selected
    The data access governance report for a label, from SharePoint Advanced Management. Screenshot · Microsoft Learn, Data access governance reports: sensitivity label snapshot report
  2. Add the scenarios you skipped

    • Trusted partners or several tenants. Labels whose encryption admits more than one domain, at Confidential, Highly Confidential or both.5
    • Tented projects. For a merger or similar, a label encrypted for one security group and published only to that group. Unpublish it when the project ends; the files stay protected. Microsoft’s engineering notes suggest keeping these project labels under 15.5
    • Employees, vendors and regions. Separate labels for full-time staff, vendors, offshore teams or countries, published only to the people who need them. Keep what anyone sees to five groups of five labels.5
    • File shares and SharePoint Server. Set the right defaults in SharePoint Online, migrate the content so it is labelled on upload, and use the information protection scanner for what stays on premises.5, 32
    • Your own keys. Bring Your Own Key and Double Key Encryption meet specific regulatory needs and are outside this model. Double Key Encryption limits several collaboration features.5
  3. Make site owners accountable

    SharePoint admin center › Policies › Site lifecycle management

    Collaboration in SharePoint makes site owners responsible for what their sites share. Microsoft recommends these controls, most of them from SharePoint Advanced Management:5

    • At least two owners on every site, found and fixed with site ownership policies.28
    • Inactive site policies, which ask owners whether a site is still used and can then make it read-only or archive it.28
    • Regular site attestation by owners.5, 28
    • Reports on content shared with everyone except external users, followed up with owners.5
    • Site access reviews for sites with heavy sharing or access.29
    SharePoint Advanced Management site lifecycle management policies
    The three lifecycle policies, each opened to create a policy. Screenshot · Microsoft Learn, SharePoint site lifecycle management
  4. Extend labels beyond Microsoft 365

    Labels can reach files in Azure Data Lake and Azure Files and columns in Azure SQL Database through the Microsoft Purview Data Map. This is in preview.30

    Protection policies, also in preview, then restrict access to labelled data in Azure Blob Storage, Azure Data Lake Storage Gen2 and Microsoft Fabric. They need Microsoft 365 E5 and pay-as-you-go billing.31

Done when Labelling deviations are reviewed on a schedule, every site has accountable owners, and the scenarios you deferred have labels of their own.

Next Have LensIQ check your rollout against this model.

What Microsoft’s engineers add.

The appendix to Microsoft’s deck answers the usual objections and gives rules for the label schema, for sites and for training. Where Microsoft Learn is newer, the notes below follow it.

Common delays and how to get past them

  • A complex taxonomy. Use the recommended labels, named for how they protect rather than for regulations.2
  • Encryption breaking apps and collaboration. Keep email on General and set SharePoint to Confidential\All employees with encryption. People can move a file to General, or to Internal exception for an add-in, with DLP and Insider Risk watching. Share with partners from a SharePoint site labelled General.2, 3
  • Waiting for perfect auto-labelling. Begin with defaults, which cover everything new or edited from today. Then add auto-labelling for credentials and regulated data, and then contextual conditions for older content.2, 3, 4
  • Site owners changing labels. Set up a chain of accountability and use audit and reporting to find the changes.2
  • Tented projects. For small, confidential project teams such as a merger team, use labels encrypted for the project group and published only to it.5

Do

  • Use names that mean something to people and say how the label protects.2
  • Keep to five by five: up to five top-level labels, each with up to five sublabels. Microsoft now builds this with label groups in place of parent labels.2, 6
  • Label every SharePoint site and team, set library defaults, and let files take their label from the site.2, 21
  • Make encrypted Confidential\All employees the default for what people save in SharePoint.2
  • Keep unencrypted labels for where encryption gets in the way, and cover them with DLP and Insider Risk policies.2
  • Turn on label inheritance from email attachments.2

Don’t

  • Mix terms such as Confidential, Restricted and Internal in one set.2
  • Wait for auto-labelling to be perfect before improving the defaults.1
  • Wait until every exception, such as a tented project, has a label.5

Sites at scale

  • Every site needs a label. Find the ones without, and fix them in the SharePoint admin center or through Microsoft Graph.4, 13
  • Make sites Private and use organisation-wide links, a balance between privacy and collaboration.2
  • Use auto-labelling for older content and for exceptions that sensitive information types catch, not as the main way files get labelled.4
  • Use contextual conditions such as file type or document properties to label older content Confidential\All employees.3

Training

  • Why the organisation moved to secure by default.2
  • How to change a label when a file has to go outside.2
  • Where to get help, and where to report problems the new protection causes. Microsoft’s engineers suggest having the support desk ready before launch.
  • A “learn more” page on a SharePoint communication site, linked from the label policy.6
  • Microsoft’s engineers also suggest early emails to raise awareness, and a rollout department by department, learning from each wave before the next.

What customers ask first.

Does this replace crawl, walk, run?

No. It is an alternative way to deploy labelling at scale. Review it against your own requirements and adapt it.1

Do the default labels have to be encrypted?

No, or not for everyone. Encryption protects a file wherever it goes, but DLP on the default label, and on unlabelled content, already stops those files being shared externally. Microsoft’s measured start begins without encryption.1

Can we start without encryption and add it later?

Yes. When you add encryption to a label, files in SharePoint and OneDrive pick it up the next time they are opened. That needs labels turned on for Office files there. Elsewhere, files labelled before the change stay unencrypted until the label is removed and applied again.24

Do we have to relabel what we already have?

No. A DLP policy can stop files under your old labels from being shared externally, so people change the label first if they need to share. If you won’t use the old labels again, remove them from your label policies.8, 19

Removing a label from a policy hides it from people. It doesn’t take the label off files that already have it.8

Where Microsoft’s guidance has moved on.

Microsoft’s deck, and in places its Learn guide, have been overtaken by newer Learn articles. This page follows the newer article where they differ:

  • Entra B2B. Learn’s step 1 still lists turning on SharePoint and OneDrive integration with Microsoft Entra B2B. In commercial tenants it is now always on, and SharePoint’s one-time passcodes are being retired.2, 17
  • Content explorer. Learn’s step 2 finds priority sites with content explorer, now content explorer (classic). Data explorer is the newer view.3, 39, 40
  • Credentials. The deck sends All credentials to Highly Confidential\Specific People. Learn splits it: Specific People in the Office apps, Highly Confidential\All employees at rest.3
  • Auto-labelling targets. The deck makes Highly Confidential\All employees optional and Highly Confidential\Specific People an auto-labelling target. Learn makes Highly Confidential\All employees the target, and keeps Specific People for credentials in the Office apps only.2, 22
  • Who the All employees labels admit. The deck says full-time employees. Learn’s labels admit everyone in the organisation as Co-Author, and Learn treats a staff and vendor split as a later scenario.2, 5
  • Site privacy. The deck’s table gives Private for every Confidential and Highly Confidential label. Learn’s table allows Private or Public, and recommends Private in its text.2
  • Site label to library default. The deck announces a feature to link the two. Learn still sets them separately. What has shipped is an auto-labelling policy that applies library defaults to existing files.3, 22
  • Adding encryption later. The deck says labelled content isn’t updated. On Learn, SharePoint and OneDrive files pick up the new encryption when next opened.24
  • Tenant default. In the deck’s notes the tenant default is General. Learn defaults documents to Confidential\All employees and only email to General, with a General default in the apps as the alternative.2, 4
  • SharePoint Advanced Management. The feature the deck lists as coming to preview is now “extend permissions to downloaded documents”. Its own article no longer calls it a preview, but the article on library default labels still does. It needs an E5-level licence with SharePoint Advanced Management.9, 21, 25
  • Tented projects. The deck uses labels where users assign permissions. Learn’s guide encrypts the label for a security group instead.5
  • Parent labels. Label groups are replacing parent labels. Five by five still applies.6
  • Exact data match. Learn’s step 3 says it isn’t available to auto-labelling. Office app auto-labelling can now use it, alongside at least one other type.4, 22
  • Beyond Microsoft 365. Still in preview. Protection policies now list Azure Blob Storage, Azure Data Lake Storage Gen2 and Microsoft Fabric, and need pay-as-you-go billing.30, 31
  • Copilot. The deck says responses carry the highest sensitivity label. On Learn, it is the highest-priority label, where supported. DLP for Copilot now also covers Copilot Chat and Cowork.26, 27

About this blueprint.

Secure by default is one of Microsoft’s Purview deployment models, recommended by its Purview product engineering team. Microsoft publishes it as a four-step guide on Microsoft Learn (aka.ms/PurviewDeploymentModels/SecureByDefault), and this page follows Learn’s steps and their titles. The deck, version 1.0, is on the Microsoft Download Center and in Microsoft’s public purview repository on GitHub under the MIT licence.

The blueprint image is Microsoft’s own, from Microsoft Learn, unchanged. The label table and each step’s tasks are LensIQ’s rewording of Microsoft’s deck and guide, checked against the Microsoft Learn articles listed below. This page is not legal advice.

Licence for Microsoft’s deck

MIT License

Copyright (c) Microsoft Corporation.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE

Where each step comes from.

  1. 1 Microsoft Learn Introduction to ‘secure by default’ with Microsoft Purview
  2. 2 Microsoft Learn Step 1: Start with default labeling
  3. 3 Microsoft Learn Step 2: Address files with the highest sensitivity
  4. 4 Microsoft Learn Step 3: Expand protection to your entire Microsoft 365 data estate
  5. 5 Microsoft Learn Step 4: Operate, expand, and retroactive actions
  6. 6 Microsoft Learn Learn about sensitivity labels
  7. 7 Microsoft Learn Get started with sensitivity labels
  8. 8 Microsoft Learn Create and publish sensitivity labels
  9. 9 Microsoft Learn Microsoft Purview service description
  10. 10 Microsoft Learn Get started with Insider Risk Management
  11. 11 Microsoft Learn Manage Sensitivity Labels in Office Apps
  12. 12 Microsoft Learn Enable sensitivity labels for files in SharePoint and OneDrive
  13. 13 Microsoft Learn Use sensitivity labels to protect collaborative workspaces (groups and sites)
  14. 14 Microsoft Learn Enable co-authoring for encrypted documents
  15. 15 Microsoft Learn Assign sensitivity labels to Microsoft 365 groups in Microsoft Entra ID
  16. 16 Microsoft Learn Prevent guest access to files while DLP rules are applied
  17. 17 Microsoft Learn Microsoft Entra B2B integration for SharePoint & OneDrive
  18. 18 Microsoft Learn Use sensitivity labels to configure the default sharing link type for sites and documents in SharePoint and OneDrive
  19. 19 Microsoft Learn Use sensitivity labels as conditions in DLP policies
  20. 20 Microsoft Learn Data Loss Prevention policy reference
  21. 21 Microsoft Learn Configure a default sensitivity label for a SharePoint document library
  22. 22 Microsoft Learn Automatically apply a sensitivity label to Microsoft 365 data
  23. 23 Microsoft Learn Help dynamically mitigate risks with Adaptive Protection
  24. 24 Microsoft Learn Apply encryption using sensitivity labels
  25. 25 Microsoft Learn Configure SharePoint with a sensitivity label to extend permissions to downloaded documents
  26. 26 Microsoft Learn How data is protected and audited in Microsoft 365 and Microsoft Copilot
  27. 27 Microsoft Learn Learn about using Microsoft Purview Data Loss Prevention to protect interactions with Microsoft 365 Copilot, Copilot Chat, and Cowork
  28. 28 Microsoft Learn SharePoint site lifecycle management
  29. 29 Microsoft Learn Initiate site access reviews for Data access governance reports
  30. 30 Microsoft Learn Learn about sensitivity labels in Data Map (preview)
  31. 31 Microsoft Learn Get started with protection policies (preview)
  32. 32 Microsoft Learn Learn about the information protection scanner
  33. 33 Microsoft Learn Create and deploy a data loss prevention policy
  34. 34 Microsoft Learn Get started with endpoint data loss prevention
  35. 35 Microsoft Learn Data access governance reports: sensitivity label snapshot report
  36. 36 Microsoft Learn Get started with data loss prevention analytics
  37. 37 Microsoft Learn Enable analytics in Insider Risk Management
  38. 38 Microsoft Learn Onboard Windows devices into Microsoft 365 overview
  39. 39 Microsoft Learn Get started with Content Explorer (classic)
  40. 40 Microsoft Learn Get started with data explorer
  41. 41 Microsoft Learn Prerequisites for SharePoint Advanced Management
  42. 42 Microsoft Learn SharePoint Advanced Management features in Microsoft Copilot licenses
  43. 43 Microsoft Learn Prepare for Microsoft Copilot by comparing E3, E5, and E7 license features
  44. 44 Microsoft Learn Step 1: Establish foundational data security

Have your labelling checked against this model.

LensIQ reviews your labels, defaults, DLP rules and site settings against secure by default, and tells you which step you have really reached.