Removing (incorrect) TIP regarding silent enablement & Endpoint Security

Green TIP referring to BitLocker silent enablement not being possible with an Endpoint Security policy is incorrect. Both an Endpoint Security profile and a Device Configuration profile can achieve BitLocker silent enablement if the correct settings (now correted in this same doc) are used. We have tested both profiles and they allow a standard user to BitLocker encrypt the OS disk silently. Removing TIP as it appears to be technically incorrect.

Author: rogersoMS

memdocs/intune/protect/encrypt-devices.md

@@ -73,9 +73,6 @@ Use one of the following procedures to create the policy type you prefer.
 
 4. On the **Configuration settings** page, configure settings for BitLocker to meet your business needs.  
 
-   > [!TIP]
-   > If you want to enable BitLocker silently, you must use a Endpoint protection template as part of a device configuration profile and not an Endpoint security policy. See [Silently enable BitLocker on devices](#silently-enable-bitlocker-on-devices) in this article for additional prerequisites and the specific setting configurations you must use.
-
    Select **Next**.
 
 5. On the **Scope (Tags)** page, choose **Select scope tags** to open the Select tags pane to assign scope tags to the profile.
@@ -252,4 +249,4 @@ For information about BitLocker deployments and requirements, see the [BitLocker
 - [Manage FileVault policy](../protect/encrypt-devices-filevault.md)  
 - [Monitor disk encryption](../protect/encryption-monitor.md)
 - [Troubleshooting BitLocker policy](/troubleshoot/mem/intune/troubleshoot-bitlocker-policies)
-- [Known issues for Enforcing BitLocker policies with Intune](/windows/security/information-protection/bitlocker/ts-bitlocker-intune-issues)
+- [Known issues for Enforcing BitLocker policies with Intune](/windows/security/information-protection/bitlocker/ts-bitlocker-intune-issues)