From e0d9ebd87028be384b00c15bc71d9ea6b963ef00 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Tue, 2 Apr 2019 12:45:15 -0700 Subject: [PATCH] Per bug 3122150, added a warning. --- .../mdm/win32-and-centennial-app-policy-configuration.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/client-management/mdm/win32-and-centennial-app-policy-configuration.md b/windows/client-management/mdm/win32-and-centennial-app-policy-configuration.md index eb942f3643..543252e8f2 100644 --- a/windows/client-management/mdm/win32-and-centennial-app-policy-configuration.md +++ b/windows/client-management/mdm/win32-and-centennial-app-policy-configuration.md @@ -47,6 +47,9 @@ When the ADMX policies are imported, the registry keys to which each policy is w - software\policies\microsoft\vba\security\ - software\microsoft\onedrive +> [!Warning] +> Some operating system components have built in functionality to check devices for domain membership. MDM enforces the configured policy values only if the devices are domain joined, otherwise it does not. However, you can still import ADMX files and set ADMX-backed policies regardless of whether the device is domain joined or non-domain joined. + ## Ingesting an app ADMX file The following ADMX file example shows how to ingest a Win32 or Desktop Bridge app ADMX file and set policies from the file. The ADMX file defines eight policies.