Skip to content

Commit 58cf7e0

Browse files
authored
Update compliance-use-custom-settings.md
I have talked to our DEV and HAADJ is support, but not documented.
1 parent 6dea6df commit 58cf7e0

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

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

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,9 @@ After you’ve deployed custom compliance settings and devices have reported bac
4848

4949
## Prerequisites
5050

51-
- **Azure Active Directory (Azure AD) joined** – Devices that are not Azure AD joined are evaluated as not applicable.
51+
- **Azure Active Directory (Azure AD) joined**, including:
52+
- Hybrid Azure AD-joined: Devices joined to Azure Active Directory (AAD), and also joined to on-premises Active Directory (AD). See [Plan your hybrid Azure Active Directory join implementation](/azure/active-directory/devices/hybrid-azuread-join-plan) for guidance.
53+
– Devices that are not Azure AD joined or Hybrid Azure AD-joined are evaluated as not applicable.
5254

5355
- **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.
5456

@@ -133,4 +135,4 @@ Policies support the use of a single PowerShell script. However, each script sup
133135

134136
- [Create a JSON for custom compliance](../protect/compliance-custom-json.md)
135137
- [Create a PowerShell script for discovery of custom compliance settings](../protect/compliance-custom-script.md)
136-
- [Create a compliance policy](../protect/create-compliance-policy.md)
138+
- [Create a compliance policy](../protect/create-compliance-policy.md)

0 commit comments

Comments
 (0)