diff --git a/content/manuals/desktop/setup/install/windows-install.md b/content/manuals/desktop/setup/install/windows-install.md
index 0d3ee78e8bf..7ef8d012e84 100644
--- a/content/manuals/desktop/setup/install/windows-install.md
+++ b/content/manuals/desktop/setup/install/windows-install.md
@@ -202,6 +202,12 @@ If using all-users installation and your administrator account is different to y
 $ net localgroup docker-users <user> /add
 ```
 
+> [!WARNING]
+>
+> Membership in `docker-users` grants access to the Docker daemon socket, which is equivalent to granting administrative privileges on the host. Only add users who require access to Windows containers or Hyper-V VM management. For Linux containers using the WSL 2 backend, this group membership is not required. See [Protect the Docker daemon socket](/manuals/engine/security/protect-access.md) for more information.
+
+If you're deploying via MDM (such as Intune) and the `docker-users` group isn't populated automatically, see [Why isn't the `docker-users` group populated when the MSI is installed with Intune or another MDM solution?](/manuals/enterprise/enterprise-deployment/faq.md#why-isnt-the-docker-users-group-populated-when-the-msi-is-installed-with-intune-or-another-mdm-solution).
+
 See the [Installer flags](#installer-flags) section to see what flags the `install` command accepts.
 
 > [!NOTE]
diff --git a/content/manuals/enterprise/enterprise-deployment/faq.md b/content/manuals/enterprise/enterprise-deployment/faq.md
index 526ccc3ae11..156a631f115 100644
--- a/content/manuals/enterprise/enterprise-deployment/faq.md
+++ b/content/manuals/enterprise/enterprise-deployment/faq.md
@@ -67,6 +67,10 @@ As a workaround, you can create a script that runs in the context of the user ac
 
 The script would be responsible for ensuring the `docker-users` group exists and populating it with the correct user.
 
+> [!WARNING]
+>
+> Membership in `docker-users` grants access to the Docker daemon socket, which is equivalent to granting administrative privileges on the host. Only add users who require access to Windows containers or Hyper-V VM management. For Linux containers using the WSL 2 backend, this group membership is not required. See [Protect the Docker daemon socket](/manuals/engine/security/protect-access.md) for further information.
+
 Here's an example script that creates the `docker-users` group if needed and adds the current user to it (requirements may vary depending on environment):
 
 ```powershell