Skip to content

Commit ad78840

Browse files
authored
Adding section on Used space vs full disk encryption
Based on testing results from Daisuke Takabe and Sanesh Vig, adding details regarding used space only vs full disk encryption, including multiple screenshots.
1 parent 969a83a commit ad78840

1 file changed

Lines changed: 39 additions & 1 deletion

File tree

memdocs/intune/protect/encrypt-devices.md

Lines changed: 39 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -149,6 +149,44 @@ Depending on the type of policy that you use to silently enable BitLocker, confi
149149
> [!TIP]
150150
> While the setting labels and options in the following two policy types are different from each other, they both apply the same configuration to Windows encryption CSPs that manage BitLocker on Windows devices.
151151
152+
### Full disk vs Used Space only encryption
153+
154+
Three settings determine whether an OS drive will be encrypted using used space only or full disk encryption:
155+
- Whether the hardware of the device is [modern standby](/windows-hardware/design/device-experiences/modern-standby) capable
156+
- Whether silent enablement has been configured for BitLocker
157+
- ('Warning for other disk encryption' = Block or 'Hide prompt about third-party encryption' = Yes)
158+
- Configuration of the [SystemDrivesEncryptionType](/windows/client-management/mdm/bitlocker-csp)
159+
- (Enforce drive encryption type on operating system drives)
160+
161+
Assuming that SystemDrivesEncryptionType has not been configured, the following is the expected behaviour. When silent enablement is configured on a modern standby device, the OS drive will be encrypted using used space only encryption. When silent enablement is configured on a device which is not capable of modern standby, the OS drive will be encrypted using full disk encryption. The result is the same whether you are using an [Endpoint Security disk encryption policy for BitLocker](/mem/intune/protect/encrypt-devices#create-an-endpoint-security-policy-for-bitlocker) or a [Device Configuration profile for endpoint protection for BitLocker](/mem/intune/protect/encrypt-devices#create-an-endpoint-security-policy-for-bitlocker). If a different end state is required, the encryption type can be controlled by configuring the SystemDrivesEncryptionType using settings catalog as shown below.
162+
163+
To verify whether the hardware is modern standby capable, run the following command from a command prompt:
164+
165+
```console
166+
powercfg /a
167+
```
168+
If the device supports modern standby, it will show that Standby (S0 Low Power Idle) Network Connected is available
169+
170+
![Docs_BL_PowerCfg_Surface_S0_Possible](https://user-images.githubusercontent.com/44718379/152707579-06d14ccb-02ac-4b98-aad5-d91b0ebeca74.png)
171+
172+
If the device does not support modern standby, such as a virtual machine, it will show that Standby (S0 Low Power Idle) Network Connected is not supported
173+
174+
![Docs_BL_PowerCfg_VM_noS0Possible](https://user-images.githubusercontent.com/44718379/152707599-22c37cb0-dd2c-4f52-9262-e61ee67ff905.png)
175+
176+
To verify the encryption type, run the following command from an elevated (admin) command prompt:
177+
178+
```console
179+
manage-bde -status c:
180+
```
181+
The 'Conversion Status' field will reflect the encryption type as either Used Space Only encrypted or Fully Encrypted.
182+
183+
![Docs_BL_UsedSpaceOnly](https://user-images.githubusercontent.com/44718379/152707629-2b32e169-d1c8-4ca6-8532-3caf32a7af00.png)
184+
![Docs_BL_FullyEncrypted](https://user-images.githubusercontent.com/44718379/152707640-5dc2f2df-aaeb-43fc-8714-3e2c35420aed.png)
185+
186+
To change the disk encryption type between full disk encryption and used space only encryption, leverage the'Enforce drive encryption type on operating system drives' setting within settings catalog.
187+
188+
![Docs_BL_SettingsCatalog_Control_Encryption](https://user-images.githubusercontent.com/44718379/152707736-48d83500-5f60-4ff5-be85-f600fcdf57f6.png)
189+
152190
#### TPM startup PIN or key
153191

154192
A device **must not require** use of a startup PIN or startup key.
@@ -252,4 +290,4 @@ For information about BitLocker deployments and requirements, see the [BitLocker
252290
- [Manage FileVault policy](../protect/encrypt-devices-filevault.md)
253291
- [Monitor disk encryption](../protect/encryption-monitor.md)
254292
- [Troubleshooting BitLocker policy](/troubleshoot/mem/intune/troubleshoot-bitlocker-policies)
255-
- [Known issues for Enforcing BitLocker policies with Intune](/windows/security/information-protection/bitlocker/ts-bitlocker-intune-issues)
293+
- [Known issues for Enforcing BitLocker policies with Intune](/windows/security/information-protection/bitlocker/ts-bitlocker-intune-issues)

0 commit comments

Comments
 (0)