Skip to content

Commit 59083e8

Browse files
authored
Merge pull request #6636 from Brenduns/quick-fix
Clarifying a sentance based on customer feedback
2 parents e12765e + e43a4cc commit 59083e8

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ After you’ve deployed custom compliance settings and devices have reported bac
5252

5353
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).
5454

55-
Devices that are not Azure AD joined or hybrid Azure AD-joined are evaluated as not applicable.
55+
Devices that are not Azure AD joined or are not hybrid Azure AD-joined are evaluated as not applicable.
5656

5757
- **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.
5858

0 commit comments

Comments
 (0)