From 51c6d0ab7132bb58ee5e6bf05d319376f62507f5 Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Thu, 19 Jul 2018 16:55:57 -0700 Subject: [PATCH] revised intro --- .../bitlocker/bitlocker-management-for-enterprises.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/information-protection/bitlocker/bitlocker-management-for-enterprises.md b/windows/security/information-protection/bitlocker/bitlocker-management-for-enterprises.md index 916d00346b..6626eee6e9 100644 --- a/windows/security/information-protection/bitlocker/bitlocker-management-for-enterprises.md +++ b/windows/security/information-protection/bitlocker/bitlocker-management-for-enterprises.md @@ -29,7 +29,7 @@ Enterprises can use [Microsoft BitLocker Administration and Management (MBAM)](h BitLocker recovery keys can be managed from Azure AD thereafter. The MBAM database does not need to be migrated. -
+Enterprises that choose to continue managing BitLocker on-premises after MBAM support ends can use the [BitLocker WMI provider class](https://msdn.microsoft.com/library/windows/desktop/aa376483) to create a custom management solution. ## Managing devices joined to Azure Active Directory