Control 2.8: Encryption (Data in Transit and at Rest) — Troubleshooting
Use this guide to diagnose scoped encryption evidence. Do not convert a connector setting, Microsoft Graph notification property, TCP test, or client protocol preference into a claim about every Microsoft 365 data flow.
Common issues
Issue 1: Customer Key onboarding validation fails
- Symptoms: The Customer Key Onboarding Service reports a failed
ValidationResult, orFailedValidationscontains subscription, recovery, key, or permission errors. - Likely causes: The request reused one subscription, named a vault/HSM outside the declared subscription, used an ineligible subscription, lacks Azure Key Vault 90-day recovery/purge protection or the required Managed HSM recovery settings, has an expired/unsupported key, or lacks required Microsoft 365 application access.
- Resolution:
- Confirm two distinct paid Azure subscription IDs are supplied to the request.
- Select each subscription explicitly with
Set-AzContextand verify the vault/HSM resides in that subscription. - For Azure Key Vault, verify 90-day soft-delete retention and purge protection. For Managed HSM, verify purge protection and the configured recovery or soft-delete retention settings.
- Verify the key is appropriate for the selected Customer Key configuration, is not expired, and permits required operations.
- Review
$request.FailedValidations, remediate the stated item, and rerunValidate; do not useEnableuntil validation succeeds.
Issue 2: Multi-workload DEP state is not healthy after onboarding
- Symptoms:
Get-M365DataAtRestEncryptionPolicyorGet-M365DataAtRestEncryptionPolicyAssignmentreports an unexpected state or the tenant assignment does not match the approved Copilot workload. - Likely causes: Key access, multi-workload DEP assignment, key-expiry, onboarding-scenario, or rotation-process error.
- Resolution:
- Export both multi-workload commands with the property-preserving procedure in PowerShell Setup, including all returned property names and values.
- Verify the tenant-level multi-workload DEP (
MDEP) policy and assignment are both present and match the approved workload.Get-DataEncryptionPolicyis Exchange-mailbox DEP evidence only and cannot prove Copilot coverage. - Verify both paired keys/vaults/HSMs remain accessible and have not expired.
- Review the change and key-rotation records before changing a policy.
- Escalate through Microsoft support if the service state remains unresolved after configuration review.
Issue 3: Copilot does not summarize an encrypted item
- Symptoms: Copilot provides a link, an incomplete response, or a message indicating it cannot use an encrypted item.
- Likely causes: The requesting user has VIEW but not EXTRACT, the source is an unopened user-defined-permissions item, a label blocks connected experiences, the source/surface has a documented limitation, or the item is DKE-protected.
- Resolution:
- Check the requesting user’s effective EXTRACT (Copy) right, not just the label template.
- Remember that OWNER includes EXTRACT and that the person applying encryption is the Rights Management owner.
- Test whether the item is open in an Office app, directly referenced where supported, or protected with user-defined permissions.
- For Edge, check whether Edge DLP is deployed before assuming EXTRACT alone controls active-tab behavior.
- Identify whether the source is an external plugin or Graph connector; sensitivity labels/encryption for those external sources are not generally recognized by Microsoft Copilot Chat.
- If the item is DKE-protected, treat the Copilot exclusion as expected behavior.
Issue 4: A handshake shows TLS 1.2 instead of TLS 1.3
- Symptoms: The negotiated TLS evidence records TLS 1.2.
- Likely causes: TLS 1.3 is rolling out by Microsoft 365 application/service and is also client/network dependent. The observed endpoint or path may legitimately negotiate TLS 1.2.
- Resolution:
- Preserve the raw handshake output and endpoint/client/network scope.
- Confirm the result is TLS 1.2 or higher.
- Compare the endpoint to Microsoft’s current service-specific TLS documentation; do not claim TLS 1.3 is universal or unavailable based on one sample.
- Check managed client, proxy, TLS-inspection, and endpoint-inventory changes before escalating.
Issue 5: A legacy TLS finding appears for SMTP AUTH
- Symptoms:
AllowLegacyTLSClientsis enabled or an SMTP AUTH client is configured forsmtp-legacy.office365.com. - Likely causes: A legacy device/application has an approved or unreviewed exception.
- Resolution:
- Inventory the mailbox, device/application, owner, and business reason.
- Confirm the exception is limited to SMTP AUTH and not presented as a general Microsoft 365 TLS posture.
- Upgrade or replace the client to support TLS 1.2+ and remove the opt-in setting when no longer needed.
- Record any service-specific availability limitation from the current Microsoft documentation; do not generalize the exception beyond the commercial-cloud scope.
Issue 6: Connector evidence conflicts with endpoint handshake evidence
- Symptoms: An Exchange connector is configured for forced/mutual TLS but a sampled HTTPS endpoint reports a different protocol/cipher expectation.
- Likely causes: The items cover different transports and scopes. Connector settings cover designated Exchange mail flow; an HTTPS handshake captures one client-to-service endpoint connection.
- Resolution:
- Keep the evidence records separate.
- Label each record with its path and scope.
- Correct only the relevant connector or endpoint configuration; do not use either item as a substitute for the other.
Diagnostic checklist
- Review the Microsoft 365 encryption service boundary and applicable Service Trust Portal artifact.
- Run the negotiated TLS handshake procedure for the approved endpoint set.
- Export Exchange connector and SMTP AUTH exception settings only when those paths exist.
- Review Customer Key onboarding/DEP state and the paired Azure Key Vault/Managed HSM configuration when deployed.
- Run the sensitivity-label/DKE test matrix with effective user rights and source/surface exceptions.
Escalation
| Severity | Condition | Escalation path |
|---|---|---|
| Low | Documentation or scoped evidence question | Security/GRC owner |
| Medium | Missing handshake, connector, or sensitivity-label evidence | Security Operations and control owner |
| High | Unapproved SMTP AUTH legacy TLS exception or failed Customer Key validation | Security Operations, Exchange/Azure owner, and change authority |
| Critical | Customer Key/key-access issue that could disrupt protected data access | CISO, Microsoft support/TAM, and IT Operations |
Related resources
- Portal Walkthrough — scoped manual evidence.
- PowerShell Setup — handshake, connector, and Customer Key procedures.
- Verification & Testing — expected outcomes and evidence matrix.
- Back to Control 2.8.