Modifying 3 x BitLocker settings for silent enablement

Testing (Daisuke) revealed that while 3 x 'Not Configured' did succeed with silent enablement, it resulted in a reporting failure. Changing to 3 x blocked achieved silent enablement with successful reporting and no errors.

Author: rogersoMS

memdocs/cloud-native-windows-endpoints.md

@@ -432,9 +432,9 @@ These settings can be enabled in the [Microsoft Endpoint Manager admin center](h
 - BitLocker system drive policy: **Configure**
   - Startup authentication required: **Yes**
   - Compatible TPM startup: **Required**
-  - Compatible TPM startup PIN: **Not configured**
-  - Compatible TPM startup key: **Not configured**
-  - Compatible TPM startup key and PIN: **Not configured**
+  - Compatible TPM startup PIN: **Blocked**
+  - Compatible TPM startup key: **Blocked**
+  - Compatible TPM startup key and PIN: **Blocked**
   - Disable BitLocker on devices where TPM is incompatible: **Not configured**
   - Enable preboot recovery message and url: **Not configured**
 - System drive recovery: **Configure**