Customer Lockbox should be turned on for the tenant
This check looks at whether Customer Lockbox is enabled in the Microsoft 365 organization settings. The safe setting is on, so a Microsoft support engineer needs your explicit approval before reaching your content during a support case.
Why it matters
Sometimes a Microsoft engineer has to look at tenant content to resolve a support case. Without Customer Lockbox that access can happen under Microsoft's internal approval process alone. With it enabled, the request is sent to your own approvers, and the engineer gets access only after one of them says yes. That keeps the final decision about your data with your organization, and every request leaves a trail you can review in the audit log.
This is a Level 2 setting that needs the matching licence, which Microsoft documents as Microsoft 365 E5 or an equivalent compliance add-on. If you do not hold that licence, the check is a reminder of the option, not something you can switch on today.
Source: Microsoft Learn, Customer Lockbox in Microsoft 365.
How to check it yourself
In the Microsoft 365 admin center, open Settings, then Org settings, then the Security & privacy tab, and select Customer lockbox. The box to require approval should be ticked.
To read the same value from PowerShell, connect to Exchange Online and run this read-only command. It changes nothing.
Connect-ExchangeOnline
Get-OrganizationConfig | Select-Object CustomerLockboxEnabledA value of True means the setting is on. Try it on a test tenant first if you have one.
How to fix it
Portal: in the same Customer lockbox pane, tick Require approval for all data access requests and save. You need a role that can change organization settings, such as Global Administrator.
Script: the command below turns the setting on. You run it yourself with your own admin account; ConfigCobra never changes your tenant, it only reads it and suggests the fix.
Set-OrganizationConfig -CustomerLockboxEnabled $trueAfterwards, decide who in your team will approve requests so that a support case is not left waiting for someone who is away.
What changes when you fix it
Day-to-day users notice nothing. The people affected are your administrators and Microsoft support. When an engineer needs to get into tenant content, an approval request reaches the designated approvers, and the work waits until someone grants or refuses it. Support cases that need such access can therefore take longer if nobody responds promptly.
Nothing else in the tenant is blocked or reconfigured. Plan who approves requests, make sure those people know what an approval request looks like, and review the resulting audit entries from time to time.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Microsoft 365 Foundations v7.0.0 | 1.3.6 | E5 Level 2 |
More checks in Microsoft 365 admin center
- The password expiration policy should be set to never expireCIS 1.3.1
- Idle session timeout for unmanaged devices should be three hours or lessCIS 1.3.2
- External calendar sharing should be turned offCIS 1.3.3
- User-owned apps and services should be restrictedCIS 1.3.4
- Internal phishing protection for Microsoft Forms should be enabledCIS 1.3.5
Go further
- Microsoft 365 admin center15 controls in this section
- CIS Microsoft 365 Foundations v7.0.0160 controls
- CIS Microsoft 365 Foundations checklistEvery control in one list, as CSV
- RemediationSee what a fix changes in your tenant before you apply it, then use the generated script
- Monitoring & DriftScheduled scans, drift detection and email alerts when a control regresses
Check this on your Microsoft 365
ConfigCobra runs this check with every other control of the CIS Microsoft 365 Foundations Benchmark, read-only.