Skip to content

Commit 28471c5

Browse files
committed
Edits for 12573421, limitations for partner managed devcies for actions for noncompliance
1 parent 869ec3e commit 28471c5

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

memdocs/intune/protect/quickstart-send-notification.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ ms.collection: M365-identity-device-management
3434
In this quickstart, you'll use Microsoft Intune to send an email notification to the members of your workforce that have noncompliant devices.
3535

3636
> [!NOTE]
37-
> The remote action to send an email notification is not supported on macOS devices that are managed by Jamf Pro.
37+
> The remote action to send an email notification is not supported on devices that are managed by a [device compliance partner](../protect/device-compliance-partners.md).
3838
3939
By default, when Intune detects a device that isn't compliant, Intune immediately marks the device as noncompliant. Azure Active Directory (Azure AD) [Conditional Access](/azure/active-directory/active-directory-conditional-access-azure-portal) then blocks the device. When a device isn't compliant, Intune allows you to add actions for noncompliance, which gives you flexibility to decide what to do. For example, you can give users a grace period to be compliant before blocking noncompliant devices.
4040

0 commit comments

Comments
 (0)