Plan for BitLocker management

Applies to: Configuration Manager (current branch)

Starting in version 1910, use Configuration Manager to manage BitLocker Drive Encryption (BDE) for on-premises Windows clients, which are joined to Active Directory. It provides full BitLocker lifecycle management that can replace the use of Microsoft BitLocker Administration and Monitoring (MBAM).


Configuration Manager doesn't enable this optional feature by default. You must enable this feature before using it. For more information, see Enable optional features from updates.

For more general information on BitLocker, see BitLocker overview.


To manage encryption on co-managed Windows 10 devices using the Microsoft Endpoint Manager cloud service, switch the Endpoint Protection workload to Intune. For more information on using Intune, see Windows Encryption.


Configuration Manager provides the following management capabilities for BitLocker Drive Encryption:

Client deployment

Deploy the BitLocker client to managed Windows devices running Windows 10 or Windows 8.1

Manage encryption policies

  • For example: choose drive encryption and cipher strength, configure user exemption policy, fixed data drive encryption settings.

  • Determine the algorithms with which to encrypt the device, and the disks that you target for encryption.

  • Force users to get compliant with new security policies before using the device.

  • Customize your organization's security profile on a per device basis.

  • When a user unlocks the OS drive, specify whether to unlock only an OS drive or all attached drives.

Compliance reports

Built-in reports for:

  • Encryption status per volume or per device
  • The primary user of the device
  • Compliance status
  • Reasons for non-compliance

Administration and monitoring website

Allow other personas in your organization outside of the Configuration Manager console to help with key recovery, including key rotation and other BitLocker-related support. For example, help desk administrators can help users with key recovery.

User self-service portal

Let users help themselves with a single-use key for unlocking a BitLocker encrypted device. Once this key is used, it generates a new key for the device.


  • Azure Active Directory-joined, workgroup clients, or clients in untrusted domains aren't supported. The client currently needs to be joined to on-premises Active Directory. This configuration is to authenticate with the recovery service to escrow keys.

  • To create a BitLocker management policy, you need the Full Administrator role in Configuration Manager.

  • The BitLocker recovery service requires HTTPS to encrypt the recovery keys across the network from the Configuration Manager client to the management point. There are two options:

    • HTTPS-enable the IIS website on the management point that hosts the recovery service. This option only applies to Configuration Manager version 2002.

    • Configure the management point for HTTPS. This option applies to Configuration Manager versions 1910 or 2002.

    For more information, see Encrypt recovery data.

  • Although the BitLocker recovery service installs on a management point that uses a database replica, clients can't escrow recovery keys. Then BitLocker won't encrypt the drive. To use the recovery service, you need at least one management point not in a replica configuration. Disable the BitLocker recovery service on any management point with a database replica.

  • To use the BitLocker management reports, install the reporting services point site system role. For more information, see Configure reporting.


    For the Recovery Audit Report to work from the administration and monitoring website, only use a reporting services point at the primary site.

  • To use the self-service portal or the administration and monitoring website, you need a Windows server running IIS. You can reuse a Configuration Manager site system, or use a standalone web server that has connectivity to the site database server. Use a supported OS version for site system servers.


    Only install the self-service portal and the administration and monitoring website with a primary site database. In a hierarchy, install these websites for each primary site.

  • On the web server that will host the self-service portal, install Microsoft ASP.NET MVC 4.0 and .NET Framework 3.5 feature before staring the install process. Other required Windows server roles and features will be installed automatically during the portal installation process.

  • The user account that runs the portal installer script needs SQL Server sysadmin rights on the site database server. During the setup process, the script sets login, user, and SQL Server role rights for the web server machine account. You can remove this user account from the sysadmin role after you complete setup of the self-service portal and the administration and monitoring website.

  • BitLocker Management is not supported on virtual machines (VMs) or on server OSes. For this reason some features may not work as expected on virtual machines or on server OSes. For example on virtual machines BitLocker Management will not start the encryption on fixed drives of virtual machines. Additionally fixed drives in virtual machines may show as compliant even though they are not encrypted.


By default, the Enable BitLocker task sequence step only encrypts used space on the drive. BitLocker management uses full disk encryption. Configure this task sequence step to enable the option to Use full disk encryption. For more information, see Task sequence steps - Enable BitLocker.

Next steps

Encrypt recovery data (an optional prerequisite before deploying policy for the first time)

Deploy BitLocker management client