Merge pull request #2334 from pelarsen/patch-14

Update compliance-use-custom-settings.md

Author: ktoliver

memdocs/intune/protect/compliance-use-custom-settings.md

@@ -48,7 +48,11 @@ After you’ve deployed custom compliance settings and devices have reported bac
 
 ## Prerequisites
 
-- **Azure Active Directory (Azure AD) joined** – Devices that are not Azure AD joined are evaluated as not applicable.
+- **Azure Active Directory (Azure AD) joined** devices, *including* hybrid Azure AD-joined devices. 
+
+  Hybrid Azure AD-joined devices are devices that are joined to Azure AD and also joined to on-premises Active Directory. For more information, see [Plan your hybrid Azure AD join implementation](/azure/active-directory/devices/hybrid-azuread-join-plan).
+  
+  Devices that are not Azure AD joined or hybrid Azure AD-joined are evaluated as not applicable.
 
 - **PowerShell discovery script** - This is a script that you create that runs on a device to discover the custom settings defined in your JSON file and returns the configuration value of those settings to Intune. You’ll upload your script to the Microsoft Endpoint Manager admin center before you create a compliance policy and then select the script you want to use when creating a policy.
 
@@ -133,4 +137,4 @@ Policies support the use of a single PowerShell script. However, each script sup
 
 - [Create a JSON for custom compliance](../protect/compliance-custom-json.md)
 - [Create a PowerShell script for discovery of custom compliance settings](../protect/compliance-custom-script.md)
-- [Create a compliance policy](../protect/create-compliance-policy.md)
+- [Create a compliance policy](../protect/create-compliance-policy.md)