Microsoft Configuration Manager
GeneralUsing the MBAM Agent to escrow BitLocker recovery keys generates excessive policies in Configuration Manager version 2103
In brief
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
What Intune admins need to know
No administrator action is required.
This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
Using the MBAM Agent to escrow BitLocker recovery keys generates excessive policies in Configuration Manager, version 2103
@@ -2,10 +2,10 @@ title: Using the MBAM Agent to escrow BitLocker recovery keys generates excessive policies in Configuration Manager version 2103 description: Update for Invoke-MbamClientDeployment.ps1 script issue in Configuration Manager 2103 ms.date: 07/26/2021-ms.subservice: core-infrastructure+ms.subservice: core-infra ms.topic: reference ms.collection: tier3-ms.service: microsoft-endpoint-configuration-manager+ms.service: configuration-manager --- # Using the MBAM Agent to escrow BitLocker recovery keys generates excessive policies in Configuration Manager, version 2103