You cannot migrate the server components or anything from MBAM to ConfigMgr or integration as such. If you want to use the bitlocker function using native ConfigMgr, then you can follow the docs https://learn.microsoft.com/en-us/mem/configmgr/protect/deploy-use/bitlocker/deploy-management-agent to configure the bitlocker policy and start creating the policy to the collection. In short the following steps would do for you.
- Check if any GPO related to the MBAM created? if so, unlink it.
- Configure the bitlocker in ConfigMgr and deploy the bitlocker policy to the collection.
- You dont have to remove/uninstall the existing MBAM client from the devices, as Configmgr uses or update the client to the latest during the bitlocker policy deployment.
- On existing clients that are encrypted, once they receive the policy from Configmgr and if the encryption algorithm what is configured in ConfigMgr matches with drive encryption, client simply escrow the keys to Configmgr site. If any mismatch in the algorithm, device report as non-compliant and you will need to decrypt before device is follow configmgr policy to encrypt again.
- On newer clients, they will anyway follow the Configmgr policy for bitlocker.
Thanks,
Eswar
www.eskonr.com