You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: memdocs/intune/protect/create-compliance-policy.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ To use device compliance policies, be sure you:
61
61
62
62
- Enroll devices in Intune (required to see the compliance status)
63
63
64
-
- Enroll devices to one user, or enroll without a primary user. Single devices cannot be enrolled to multiple users.
64
+
- Enroll devices to one user, or enroll without a primary user. Single devices can't be enrolled to multiple users.
65
65
66
66
In addition to compliance settings that are built in to Intune, the following platforms support adding custom compliance settings to compliance policies:
67
67
@@ -83,7 +83,7 @@ For more information about using custom compliance settings, including supported
83
83
-*Android (AOSP)*
84
84
-*Android Enterprise*
85
85
-*iOS/iPadOS*
86
-
- Linux - Ubuntu Desktop, version 20.04 LTS and 22.04 LTS)
86
+
-*Linux* - (Ubuntu Desktop, version 20.04 LTS and 22.04 LTS)
87
87
-*macOS*
88
88
-*Windows 8.1 and later*
89
89
-*Windows 10 and later*
@@ -105,11 +105,12 @@ For more information about using custom compliance settings, including supported
For Linux, the profile type uses the Settings catalog instead of templates. Expand each available citatory and select the settings you want to include in your policy. Examples of Linux settings categories include:
113
+
**For Linux**, the profile type uses settings from the Settings catalog. Expand each available category and select the settings you want to include in your policy. Examples of Linux settings categories include:
113
114
114
115
- Allowed Distributions
115
116
- Custom Compliance
@@ -125,7 +126,7 @@ For more information about using custom compliance settings, including supported
125
126
>
126
127
> - Linux - Ubuntu Desktop, version 20.04 LTS and 22.04 LTS
127
128
> - Windows 10/11
128
-
> Before you can add custom settings to a policy, you must have uploaded a detection script to Intune, and have ready a JSON file that defines the settings you want to use for compliance. See [Custom compliance settings](../protect/compliance-use-custom-settings.md) for more information.
129
+
> Before you can add custom settings to a policy, you must have uploaded a detection script to Intune, and have ready a JSON file that defines the settings you want to use for compliance. See [Custom compliance settings](../protect/compliance-use-custom-settings.md).
129
130
130
131
On the **Compliance settings** page, expand the **Custom Compliance** category:
Copy file name to clipboardExpand all lines: memdocs/intune/protect/device-compliance-get-started.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,7 +94,7 @@ Compliance policy settings include the following settings:
94
94
95
95
By default, the period is set to 30 days. You can configure a period from 1 to 120 days.
96
96
97
-
You can view details about device compliance to the validity period setting. Sign in to [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) and go to **Devices** > **Monitor** > **Setting compliance**. This setting has a name of **Is active** in the *Setting* column. For more information about this and related compliance status views, see [Monitor device compliance](compliance-policy-monitor.md).
97
+
You can view details about a devices compliance to the validity period setting. Sign in to [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) and go to **Devices** > **Monitor** > **Setting compliance**. This setting has a name of **Is active** in the *Setting* column. For more information about this and related compliance status views, see [Monitor device compliance](compliance-policy-monitor.md).
98
98
99
99
## Device compliance policies
100
100
@@ -128,6 +128,7 @@ The following subjects link to dedicated articles for different aspects of devic
-[Android Open Source Project (AOSP)](compliance-policy-create-android-aosp.md)
130
130
-[iOS](compliance-policy-create-ios.md)
131
+
- Linux - Support includes [Custom Compliance](../protect/compliance-use-custom-settings.md) and limited settings from the settings catalog for *Allowed Distributions*, *Device Encryptions*, and *Password Policy*.
131
132
-[macOS](compliance-policy-create-mac-os.md)
132
133
-[Windows Holographic for Business](compliance-policy-create-windows.md#windows-holographic-for-business)
133
134
-[Windows 8.1 and later](compliance-policy-create-windows-8-1.md)
0 commit comments