From ed128b2718c967e696d75dc5cf081e80fc00b196 Mon Sep 17 00:00:00 2001
From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com>
Date: Thu, 12 Oct 2023 19:07:04 -0400
Subject: [PATCH] updates

---
 .../data-protection/bitlocker/configure.md               | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/windows/security/operating-system-security/data-protection/bitlocker/configure.md b/windows/security/operating-system-security/data-protection/bitlocker/configure.md
index bf69b79637..f6f2c34b2d 100644
--- a/windows/security/operating-system-security/data-protection/bitlocker/configure.md
+++ b/windows/security/operating-system-security/data-protection/bitlocker/configure.md
@@ -13,15 +13,6 @@ To configure BitLocker, you can use one of the following options:
 - Group policy (GPO): this option can be used for devices that are joined to an Active Directory domain and aren't managed by a device management solution. Group policy can also be used for devices that aren't joined to an Active Directory domain, using the local group policy editor
 - Microsoft Configuration Manager: this option can be used for devices that are managed by Microsoft Configuration Manager using the BitLocker management agent
 
-The following table describes the options to configure BitLocker, depending on the device's join type:
-
-| Join type | CSP | GPO | Configuration Manager |
-|-|-| - |-|
-| *Microsoft Entra joined* | ✅ | ❌ | ✅ |
-| *Microsoft Entra registered* | ✅ | ❌ | ❌ |
-| *Microsoft Entra hybrid joined* | ✅ | ✅ | ✅ |
-| *Active Directory joined* | ❌ | ✅ | ✅ |
-
 > [!NOTE]
 > Windows Server doesn't support the configuration of BitLocker using CSP or Microsoft Configuration Manager. Use GPO instead.