Skip to main content
Sprawlsight
Sign inFree self-assessment
Menu

Copilot policy gaps: labels, DLP and Conditional Access

By The Sprawlsight team · · 9 min read

purviewdlppolicy

In short

Microsoft 365 Copilot can use anything its user can access. Sensitivity labels and Microsoft Purview data loss prevention (DLP) narrow that, and Conditional Access controls who gets in. The usual gaps are unlabeled files, DLP rules for labels nobody applies, report-only Conditional Access policies and growing exclusions. Check Conditional Access against CISA's SCuBA baseline, and check label coverage in Purview.

Most tenants getting ready for Microsoft 365 Copilot already have policies: a few sensitivity labels, a data loss prevention (DLP) policy for credit card numbers, a dozen Conditional Access policies. The problem is rarely a missing policy. It's the distance between what the policies say and what they enforce.

What is policy sprawl?

Policy sprawl is the build-up of overlapping, stale, report-only or exception-heavy policies that look like coverage but leave gaps. It happens one reasonable change at a time: a label for one project, a DLP rule cloned for a test, a Conditional Access exclusion for a traveling executive that nobody removed.

Copilot only returns content the signed-in user can already access, but it makes every gap faster to find: a buried, overshared file is now one prompt away. If broad access is your bigger problem, start with SharePoint oversharing.

How do sensitivity labels limit what Copilot can use?

Sensitivity labels limit Copilot through encryption and through DLP. When a label applies encryption, Copilot returns content only to a user who has both the VIEW and EXTRACT usage rights (permissions the encryption grants: VIEW opens the file, EXTRACT allows copying its content). With VIEW but not EXTRACT, Copilot won't summarize the file; it can only link to it. A label without encryption is a tag. Copilot displays it, and new content can inherit the highest-priority label, but nothing is withheld from Copilot Chat unless a DLP policy acts on it. The advanced label setting BlockContentAnalysisServices keeps a label's content from Copilot only in Word, Excel, PowerPoint and Outlook. Microsoft covers the details in its considerations for Microsoft 365 Copilot.

Too many labels

Microsoft notes that effectiveness drops noticeably when people have more than five main labels or more than five sublabels per main label (Learn about sensitivity labels). Big taxonomies get applied inconsistently, which makes label-based DLP unreliable. Keep a short list, such as Public, General, Confidential and Highly Confidential, and decide in writing which labels should keep content out of Copilot.

No default labeling

Unlabeled content is invisible to label-based DLP. Two defaults help:

  • A default label in a label policy applies to new documents and emails, and to unlabeled documents people open in a supported Office app. It never overrides an existing label and doesn't touch files nobody opens. Microsoft advises against an encrypting label as the default for documents.
  • A default label for a SharePoint document library applies to new and edited files in that library. It doesn't label existing files until someone edits them (Configure a default sensitivity label for a SharePoint document library).

Library defaults need sensitivity labels enabled for Office files in SharePoint and OneDrive: (Get-SPOTenant).EnableAIPIntegration should return True.

Container labels mistaken for file labels

A label on a team, Microsoft 365 group or SharePoint site controls container settings such as privacy, guest access and external sharing. Items inside don't inherit it (Use sensitivity labels to protect collaborative workspaces). A Confidential site can hold hundreds of unlabeled files, and Copilot treats each file by its own label. Pair container labels with library defaults where it matters.

How does Purview DLP keep labeled content out of Copilot?

Purview DLP keeps labeled content out of Copilot with a rule in the Microsoft 365 Copilot and Copilot Chat policy location. The rule pairs the condition Content contains > Sensitivity labels with the action Prevent Copilot from processing content. Copilot then won't use files and emails with those labels, even when the user has access (Learn about DLP for Microsoft 365 Copilot).

As of September 2026, these details matter when you audit it:

  • Coverage. The rule covers stored files and files open in Word, Excel and PowerPoint, and Copilot features in those apps turn off for a blocked file. Emails sent on or after January 1, 2025 are covered; calendar invites aren't.
  • Citations still appear. Copilot can still cite a blocked item; it just doesn't use the content.
  • One condition type per rule. Label conditions and sensitive information type (a pattern such as a credit card number) conditions need separate rules.
  • Changes take time. Updates can take up to four hours to reach Copilot. Run simulation mode first.
  • Licensing. Microsoft's Purview service description lists the file-and-email restriction for E5-level plans such as Microsoft 365 E5, not Business or E3 plans. The rule for sensitive prompts, still in preview, is listed for all Copilot users.

The most common gap is a DLP-for-Copilot policy that names a label almost nobody applies. Check how many files carry the label before you count it as coverage.

Where do Conditional Access policies usually leave gaps?

Conditional Access usually leaves gaps in three places: policies stuck in report-only, exclusions that grew, and baseline policies that don't cover every user and every app. Copilot acts as the signed-in user, so every Conditional Access gap is also a Copilot gap. Microsoft notes that access tokens are issued by default when no policy condition triggers an access control (Plan a Conditional Access deployment). A gap isn't a soft failure. It's an allow.

  • Report-only policies. Report-only mode logs what a policy would do but never prompts for multifactor authentication (MFA) or blocks anyone. A policy still in report-only months later is a gap with a reassuring name.
  • Exclusions that grew. Microsoft recommends excluding emergency access accounts and needed service accounts, using groups rather than named users. Lists still grow. With Microsoft Entra ID P2 or Microsoft Entra ID Governance, access reviews can confirm each excluded user still belongs there.
  • MFA not required for all users on all cloud apps. Microsoft recommends a baseline policy for all users and all resources, with no app exclusions, that requires MFA (Require MFA for all users). Policies scoped to a list of apps miss anything added later.
  • Legacy authentication not blocked. Legacy protocols can't do MFA. Block them with a policy for all users and all resources that selects the Exchange ActiveSync clients and Other clients conditions (Block legacy authentication). For SharePoint, (Get-SPOTenant).LegacyAuthProtocolsEnabled should return False.
  • Idle browser sessions stay signed in. This is a session setting, not a Conditional Access policy. Microsoft recommends the org-wide idle session timeout in the Microsoft 365 admin center (Settings > Org settings > Security & privacy). It overrides the older SharePoint idle session sign-out, which you can still check with Get-SPOBrowserIdleSignOut. Neither signs out users who chose Stay signed in, so consider hiding that option. Limiting the timeout to unmanaged devices needs Microsoft Entra ID P1 and a Conditional Access policy.

Sprawlsight's free snapshot checks related settings: ENTRA-002 (MFA is required for all users on all cloud apps), SPO-005 (Legacy authentication to SharePoint is blocked) and SPO-006 (Idle browser sessions sign out automatically). The Conditional Access gap analyzer workbook finds sign-ins no policy touched; it needs Microsoft Entra ID P1 and a Log Analytics workspace.

How do you measure your policies against a public baseline?

Run CISA's free ScubaGear tool, which compares your tenant with the secure configuration baselines from CISA's Secure Cloud Business Applications (SCuBA) project, then review the policy logic behind each result. The baselines cover Microsoft Entra ID, Exchange Online, SharePoint, Microsoft Teams, Power Platform, Power BI and a security suite, but not sensitivity labels or DLP for Copilot. SCuBA's DLP policy asks you to block personal data such as credit card and Social Security numbers, so measure label coverage and the Copilot DLP rule against Microsoft's guidance instead. One caution: CISA notes that ScubaGear checks only the Conditional Access conditions each baseline policy names, so an overly narrow policy can pass and still leave gaps.

How do you consolidate policies without breaking access?

Consolidate in five steps, and test each merged or changed policy in report-only or with the What If tool before you enforce it.

  1. Inventory every policy. List labels and label policies, DLP policies with their locations and mode, and Conditional Access policies with their state. Include policies that are off: the limit of 240 Conditional Access policies per tenant counts them too.
  2. Name and own each policy. Conditional Access policies have no built-in owner attribute, so Microsoft suggests putting the owner in the name and keeping a register. Do the same for DLP rules and labels.
  3. Remove duplicates and dead policies. Merge Conditional Access policies that apply the same control to the same users, and keep emergency access accounts excluded from every merged policy. Retire DLP rules for labels nobody uses. Delete policies that are off and no longer needed; deleted Conditional Access policies can be restored for 30 days.
  4. Move report-only to on with a plan. Review each policy's results in the sign-in logs or policy impact view, set a date, tell users, and switch it on. If it shouldn't be enforced, turn it off and record why.
  5. Shrink exclusions. Replace named users with an exclusion group, remove anyone without a current reason, and schedule a review.

What are the most common Copilot policy gaps?

The most common gaps are labels nobody applies, DLP rules aimed at those labels, report-only policies and growing exclusions.

Policy area Common gap How to check
Sensitivity labels Too many labels; most files unlabeled Purview label list and labeling reports
Default labeling No policy or library default Default label in each label policy and each library
Container labels Assumed to label files inside Site label versus the library's Sensitivity column
DLP for Copilot Missing, or targets labels nobody applies DLP policies for the Copilot location; simulation results
Report-only policies Left in report-only for months Conditional Access policy list by state
Exclusions Named users added over time Each policy's Exclude settings; access reviews
MFA (ENTRA-002) Not all users or all resources An MFA policy for All users and All resources
Legacy authentication Not blocked for all users and resources Legacy client block policy; LegacyAuthProtocolsEnabled for SharePoint (SPO-005)
Idle sessions (SPO-006) Browser sessions never time out Idle session timeout in org settings; Get-SPOBrowserIdleSignOut

How often should you review policies?

Review policy changes monthly and the whole set quarterly, plus after big changes such as a wider Copilot rollout. Conditional Access changes appear in Entra ID > Monitoring & health > Audit logs: filter Service to Conditional Access and open Modified Properties to compare old and new versions. Audit data is kept for 30 days by default, so send it to Log Analytics or a storage account for longer history (Troubleshoot Conditional Access policy changes).

Sprawlsight measures this area as Policy Sprawl, which answers "Where do your policies leave gaps?" by checking DLP, sensitivity labels and Conditional Access, and measuring them against CISA's SCuBA baseline where it applies. The full assessment adds weekly scans and shows what changed between them.

For the step-by-step clean-up, get the Policy sprawl field guide. For access through nested groups and app consent, see the Microsoft 365 permissions audit. Earlier in the journey? Start with Copilot readiness.

Frequently asked questions

What is policy sprawl?

Policy sprawl is the build-up of overlapping, stale, report-only or exception-heavy policies across sensitivity labels, DLP and Conditional Access. Each policy looks like coverage, but together they leave gaps that are hard to see. Copilot makes those gaps matter because it can surface anything a user can reach.

Does a sensitivity label alone stop Copilot from using a file?

Usually only when the label applies encryption that Copilot can't use for that person: the user lacks the EXTRACT usage right, the label uses Double Key Encryption, or (for unopened files in SharePoint and OneDrive) it uses user-defined permissions. Without EXTRACT, Copilot can link to the file but won't summarize it. A label without encryption is a tag, so to keep labeled content out of Copilot responses you add a Purview DLP policy for the Microsoft 365 Copilot and Copilot Chat location.

Does DLP for Copilot scan files uploaded into a prompt?

No. Microsoft documents that DLP can't scan the contents of files uploaded directly into a Copilot prompt; it checks only the text typed into the prompt. Labeled files and emails in Microsoft 365 are covered by the label-based rule instead.

How many Conditional Access policies is too many?

Microsoft sets a hard limit of 240 Conditional Access policies per tenant, and it counts policies that are on, off or in report-only. The practical limit is much lower: if you can't say what each policy does and who owns it, you have too many.

Is SCuBA a Microsoft baseline?

No. SCuBA (Secure Cloud Business Applications) is a project of CISA, the US Cybersecurity and Infrastructure Security Agency, that publishes secure configuration baselines for Microsoft 365. Any organization can use them, and CISA's free ScubaGear tool checks a Microsoft 365 tenant against them.

Related reading

· 8 min read

Fix SharePoint oversharing before Microsoft 365 Copilot

Find and fix SharePoint and OneDrive oversharing before Microsoft 365 Copilot surfaces it: sharing defaults, Anyone links, org-wide access and site reviews.

sharepointonedriveoversharingcopilot