Monitor device encryption with Intune
The Microsoft Intune encryption report is a centralized location to view details about the encryption status of your managed devices. View details about a device’s encryption status and find options to manage device recovery keys. The recovery key options that are available depend on the type of device you're viewing.
To find the report, Sign in to the Intune and go to Device Configuration, and then under Monitor, select Encryption report.
View encryption details
The encryption report shows common details across the supported devices you manage. The following sections provide details about the information that Intune presents in the report.
The encryption report supports reporting on devices that run the following operating system versions:
- macOS 10.13 or later
- Windows version 1607 or later
The Encryption report pane displays a list of the devices you manage with high-level details about those devices. You can select a device from the list to drill-in and view additional details from the devices Device encryption status pane.
Device name - The name of the device.
OS – The device platform, such as Windows or macOS.
OS version – The version of Windows or macOS on the device.
TPM version (Applies to Windows 10 only) – The version of the Trusted Platform Module (TPM) chip on the Windows 10 device.
Encryption readiness – An evaluation of the devices readiness to support an applicable encryption technology, like BitLocker or FileVault encryption. Devices are identified as:
Ready: The device can be encrypted by using MDM policy, which requires the device meets the following requirements:
For macOS devices:
- MacOS version 10.13 or later
For Windows 10 devices:
- Version 1703 or later, of Business, Enterprise, Education, or version 1809 or later of Pro
- The device must have a TPM chip
For more information, see the BitLocker configuration service provider (CSP) in the Windows documentation.
Not ready: The device doesn't have full encryption capabilities, but still supports encryption. For example, a Windows device might be encrypted manually by a user, or through Group Policy that can be set to allow encrypting without a TPM.
Not applicable: There isn't enough information to classify this device.
Encryption status – Whether the OS drive is encrypted.
User Principle Name - The primary user of the device.
Device encryption status
When you select a device from the Encryption report, Intune displays the Device encryption status pane. This pane provides the following details:
Device name – The name of the device you're viewing.
Encryption readiness - An evaluation of the devices readiness to support encryption through the MDM policy.
For example: When a Windows 10 device has a readiness of Not ready, it might still support encryption. To have the Ready designation, the Windows 10 device must have a TPM chip. TPM chips aren't required to support encryption. (See Encryption readiness in the preceding section for more details.)
Encryption status - Whether the OS drive is encrypted. It can take up to 24 hours for Intune to report on a device’s encryption status or a change to that status.
Profiles – A list of the Device configuration profiles that apply to this device and are configured with the following values:
- Profile type = Endpoint protection
- Settings > FileVault > FileVault = Enable
- Profile type = Endpoint protection
- Settings > Windows Encryption > Encrypt devices = Required
You can use the list of profiles to identify individual policies for review should the Profile state summary indicate problems.
Profile state summary – A summary of the profiles that apply to this device. The summary represents the least favorable condition across the applicable profiles. For example, if only one out of several applicable profiles results in an error, the Profile state summary will display Error.
Status details – Advanced details about the device’s encryption state.
For Windows 10 devices, Intune only shows Status details for devices that run the Windows 10 April 2019 Update or later.
This field displays information for each applicable error that can be detected. You can use this information to understand why a device might not be encryption ready.
The following are examples of the status details Intune can report:
The recovery key hasn't been retrieved and stored yet. Most likely, the device hasn't been unlocked, or it hasn't checked in.
Consider: This result doesn't necessarily represent an error condition but a temporary state that could be because of timing on the device where escrow for recovery keys must be set up before the encryption request is sent to the device. This status might also indicate the device remains locked or hasn’t checked in with Intune recently. Finally, because FileVault encryption doesn’t start until a device is plugged in (charging), it’s possible for a user to receive a recovery key for a device that isn't yet encrypted.
The user is deferring encryption or is currently in the process of encryption.
Consider: Either the user hasn't yet logged out after receiving the encryption request, which is necessary before FileVault can encrypt the device, or the user has manually decrypted the device. Intune can't prevent a user from decrypting their device.
The device is already encrypted. Device user must decrypt the device to continue.
Consider: Intune can’t set up FileVault on a device that is already encrypted. Instead, the user needs to manually decrypt their device before it can be managed by a device configuration policy and Intune.
FileVault needs the user to approve their management profile in MacOS Catalina and higher.
Consider: Beginning with MacOS version 10.15 (Catalina), user approved enrollment settings can result in the requirement that users manually approve FileVault encryption. For more information, see User Approved enrollment in the Intune documentation.
Consider: One possible cause for an unknown status is that the device is locked and Intune can’t start the escrow or encryption process. After the device is unlocked, progress can continue.
The BitLocker policy requires user consent to launch the BitLocker Drive Encryption Wizard to start encryption of the OS volume but the user didn't consent.
The encryption method of the OS volume doesn't match the BitLocker policy.
The policy BitLocker requires a TPM protector to protect the OS volume, but a TPM isn't used.
The BitLocker policy requires a TPM-only protector for the OS volume, but TPM protection isn't used.
The BitLocker policy requires TPM+PIN protection for the OS volume, but a TPM+PIN protector isn't used.
The BitLocker policy requires TPM+startup key protection for the OS volume, but a TPM+startup key protector isn't used.
The BitLocker policy requires TPM+PIN+startup key protection for the OS volume, but a TPM+PIN+startup key protector isn't used.
The OS volume is unprotected.
Recovery key backup failed.
A fixed drive is unprotected.
The encryption method of the fixed drive doesn't match the BitLocker policy.
To encrypt drives, the BitLocker policy requires either the user to sign in as an Administrator or, if the device is joined to Azure AD, the AllowStandardUserEncryption policy must be set to 1.
Windows Recovery Environment (WinRE) isn't configured.
A TPM isn't available for BitLocker, either because it isn't present, it's been made unavailable in the Registry, or the OS is on a removable drive.
The TPM isn't ready for BitLocker.
The network isn't available, which is required for recovery key backup.
Export report details
While viewing the Encryption report pane, you can select Export to create a .csv file download of the report details. This report includes the high-level details from the Encryption report pane and Device encryption status details for each device you manage.
This report can be of use in identifying problems for groups of devices. For example, you might use the report to identify a list of macOS devices that all report FileVault is already enabled by the user, which indicates devices that must be manually decrypted before Intune can manage their FileVault settings.
FileVault recovery keys
When Intune first encrypts a macOS device with FileVault, a personal recovery key is created. Upon encryption, the device displays the personal key a single time to the end-user.
For managed devices, Intune can escrow a copy of the personal recovery key. Escrow of keys enables Intune administrators to rotate keys to help protect devices, and users to recover a lost or rotated personal recovery key.
Intune supports multiple options to rotate and recover personal recovery keys. One reason to rotate a key is if the current personal key is lost thought to be at risk.
Devices that are encrypted by users, and not by Intune, cannot be managed by Intune. This means that Intune can't escrow the personal recovery of these devices, nor manage the rotation of the recovery key. Before Intune can manage FileVault and recovery keys for the device, the user must decrypt their device, and then let Intune encrypt the device.
Rotate recovery keys
Automatic rotation: As an admin, you can configure the FileVault setting Personal recovery key rotation to automatically generate new recovery key’s periodically. When a new key is generated for a device, the key isn’t displayed to the user. Instead, the user must get the key either from an admin, or by using the company portal app.
Manual rotation: As an admin, you can view information for a device that you manage with Intune and that’s is encrypted with FileVault. You can then choose to manually rotate that the recovery key for corporate devices. You can’t rotate recovery keys for personal devices.
To rotate a recovery key:
Sign in to Intune, go to Devices and then under Manage, select All devices.
From the list of devices, select the device that is encrypted and for which you want to rotate its key. Then under Monitor, select Recovery keys.
On the Recovery keys pane, select Rotate FileVault recovery key.
The next time the device checks in with Intune, the personal key is rotated. When needed, the new key can be obtained by the end-user through the company portal.
Recover recovery keys
Administrator: Administrators can't view personal recovery keys for devices that are encrypted with FileVault.
End-user: End-users use the Company Portal website from any device to view the current personal recovery key for any of their managed devices. You can't view recovery keys from the Company Portal app.
To view a recovery key:
Sign in to the Intune Company Portal website from any device.
In the portal, go to Devices and select the macOS device that is encrypted with FileVault.
Select Get recovery key. The current recovery key is displayed.
On an iPhone, you must select the three dots before the Get recovery key option appears.
BitLocker recovery keys
Intune provides access to the Azure AD blade for BitLocker so you can view BitLocker Key IDs and recovery keys for your Windows 10 devices, from within the Intune portal. To be accessible, the device must have its keys escrowed to Azure AD.
Sign in to Intune, go to Devices and then under Manage, select All devices.
Select a device from the list, and then under Monitor, select Recovery keys.
When keys are available in Azure AD, the following information is available:
- BitLocker Key ID
- BitLocker Recovery Key
- Drive Type
When keys aren't in Azure AD, Intune will display No BitLocker key found for this device.
Information for BitLocker is obtained using the BitLocker configuration service provider (CSP). BitLocker CSP is supported on Windows 10 version 1703 and later, and for Windows 10 Pro version 1809 and later.
Create a device compliance policy.
Učitavanje povratnih informacija...