Forum Discussion
Puzzling BitLocker Status
- Mmm, I would start to make sure those other compatible tpm startup are blocked as shown here
https://call4cloud.nl/2021/02/b-for-bitlocker/
These articles suggest the "catastrophic failure" is a result of malformed XML or URLs too long within the XML. By any chance did you provide a long Recovery Key URL? It should've generated the XML for you in this case via the portal, but could possibly delete and recreate the policies to trigger a regeneration of new XML?
Auto Mount Team Sites with Intune
Another possibility from your information suggests it was failing to update the CSP setting. Is it possible you have a GPO or something else in place which defines the BitLocker policy which could be causing a conflict?
All that being said, if it is succeeding in getting all the recovery key info stored to Azure AD, you could possibly just ignore the error. I've seen the portal show this "stuck" error state because it couldn't properly apply on the first try, but even though it later succeeds, the state never updates. Possibly this is a portal bug.
Please like or mark this thread as answered if it's helpful, thanks!