SC-401 — Frequently Asked Questions

No, Microsoft Purview includes built-in sensitive info types for credit card numbers. You can use these directly in your auto-labeling policy without creating a custom one.

The requirement specifies that documents with credit card numbers must be 'labeled'. Labeling applies sensitivity settings (encryption/access restrictions), whereas retention applies how long data is kept. These are distinct features in Purview.

The scanner relies on specific service authentication mechanisms that are incompatible with interactive MFA prompts required by most passwordless methods.

No, User1 is an interactive tester using the client normally, so they should retain MFA for maximum security as per standard policy.

Security Reader lacks the specific permission to read the UnifiedAuditLogIngestionEnabled setting in Exchange Online, which DSPM for AI uses to report auditing status.

No, it is the least privilege option for this task because it only grants read-only access to Exchange Online configuration, which is necessary to check the audit log status.

Proximity is measured in characters between the primary and secondary elements. The default threshold is usually 15 characters.

No. If the regex explicitly requires 22 digits (e.g., \d{22}), it will not match a string with only 12 digits.

500,000 refers to eDiscovery limits for total locations or exports, not the item count per location in data risk assessments.

Yes, the 200,000 items per location limit applies to both default and custom data risk assessments.

No. Built-in SITs provided by Microsoft cannot be copied or modified. You must create a new custom SIT from scratch if you need to adjust detection logic for these standards.

A custom SIT is one created by your organization's admins. It typically has a unique name or includes your tenant domain in the publisher field, distinguishing it from Microsoft's global definitions.

Yes, if the rule conditions are met by the sender or the message content, the rule applies to the message as it is processed for delivery to each member.

It evaluates the sender's current group memberships. If the sender belongs to the specified group, the rule condition is satisfied, regardless of the recipient.

Microsoft Purview restricts mixing Teams messaging locations (chats/channels) with productivity locations (Exchange/SharePoint) in a single static retention policy.

Yes, Teams channel messages can be included in the same retention policy as Exchange mailboxes, SharePoint sites, and Microsoft 365 Groups.