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/enrollment/android-move-device-admin-work-profile.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ When users see that they're out of compliance for this reason, they can tap **Re
45
45
-[Set Android Enterprise personally-owned work profile enrollment](android-work-profile-enroll.md) for the group of users who are moving to personally-owned work profile.
46
46
- Consider increasing your user device limits. When unenrolling devices from device administrator management, device records might not be immediately removed. To provide cushion during this period, you might need to increase device limit capacity. This increase is so that the users can enroll into personally-owned work profile management.
47
47
-[Configure Azure Active Directory device settings](/azure/active-directory/devices/device-management-azure-portal#configure-device-settings) for Maximum number of devices per user.
48
-
- Adjust the [Intune device limit restrictions](enrollment-restrictions-set.md#create-a-device-limit-restriction) by setting the Device limit.
48
+
- Adjust the [Intune device limit restrictions](create-device-limit-restrictions.md) by setting the device limit.
Copy file name to clipboardExpand all lines: memdocs/intune/enrollment/create-device-limit-restrictions.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,18 +72,18 @@ Microsoft Intune provides one default policy for device limit restrictions. You
72
72
8. Choose **Select groups to include** and then use the search box to find groups that you want to include in this restriction. The restriction applies only to groups to which it's assigned. If you don't assign a restriction to at least one group, it won't have any effect. Then choose **Select**.
73
73

74
74
9. Select **Next** to go to the **Review + create** page.
75
-
10. Select **Create** to create the restriction. The new restriction appears in your list of restrictions and is given a higher priority than the default policy. For information about changing the priority level, see [Change restriction priority](enrollment-restrictions-set.md#change-restriction-priority)(in this article).
75
+
10. Select **Create** to create the restriction. The new restriction appears in your list of restrictions and is given a higher priority than the default policy. For information about changing the priority level, see [Change restriction priority](create-device-limit-restrictions.md#change-restriction-priority)(in this article).
76
76
77
77
## Edit enrollment restrictions
78
78
79
-
Edits are applied to new enrollments and do not affect devices that are already enrolled.
79
+
Edits are applied to new enrollments and don't affect devices that are already enrolled.
80
80
81
81
1. Go to **Enrollment device limit restrictions** to bring up the list of your policies.
82
82
2. Select the name of the policy you want to change.
83
83
3. Select **Properties**.
84
84
4. Select **Edit**.
85
85
5. Make your changes and select **Review + save**.
Use the device platform enrollment restrictions in Microsoft Intune to block personally owned devices from enrolling, and to block devices by device platform and OS version.
46
+
Use the device platform enrollment restrictions in Microsoft Intune to block personally owned devices from enrolling, and to block devices by device platform and OS version. An enrollment restriction policy is required to apply enrollment restrictions. You can create a new Intune device platform restriction policy in the Microsoft Endpoint Manager admin center or use the default policy that's already available.
47
47
48
-
You can create a new Intune device platform restriction policy in the Microsoft Endpoint Manager admin center or use the default policy that's already available. You have one default policy for platform restrictions, and you can edit and customize it as needed.
49
-
50
-
You can have up to 25 device platform restriction policies. Intune applies the default policy to all user and userless enrollments until you assign a higher-priority policy.
48
+
You can have up to 25 device platform restriction policies.
51
49
52
50
This article describes the device platform restrictions supported in Microsoft Intune and how to configure them from the Microsoft Endpoint Manager admin center.
53
51
@@ -57,81 +55,6 @@ Microsoft Intune provides one default policy for device platform restrictions. Y
57
55
## Available restrictions
58
56
This section describes the restrictions you can configure in a device platform-enrollment restriction policy.
59
57
60
-
### Device platform
61
-
This restriction blocks devices running on specific platforms from enrolling. You can restrict devices running the following platforms:
62
-
63
-
* Android device administrator
64
-
* Android Enterprise work profile
65
-
* iOS/iPadOS
66
-
* macOS
67
-
* Windows
68
-
69
-
In groups where both Android platforms are allowed, devices that support work profile will enroll with a work profile. Devices that don't support work profile will enroll on the Android device administrator platform. Neither work profile nor device administrator enrollment will work until you complete all prerequisites for Android enrollment.
70
-
71
-
Since Intune supports two Android platforms, it's important to understand how platform restrictions work when used with version restrictions:
72
-
* If you allow both platforms for the same group, and then refine it for specific and non-overlapping versions, devices are sent through the Android enrollment flow that's picked for their version.
73
-
* If you allow both platforms, but block the same versions, devices running blocked versions cannot enroll. Users on these devices are sent through the Android device administrator enrollment flow before they are blocked and prompted to sign out.
74
-
75
-
### OS version
76
-
This restriction enforces your maximum and minimum OS version requirements. Devices running earlier or later OS versions are not allowed to enroll. This type of restriction works with the following operating systems:
77
-
78
-
* Android device administrator\*
79
-
* Android Enterprise work profile\*
80
-
* iOS/iPadOS\*
81
-
* Windows
82
-
83
-
\* Version restrictions are supported on these platforms for devices enrolled via Intune Company Portal only.
84
-
85
-
### Personally-owned devices
86
-
This restriction helps prevent device users from accidentally enrolling their personal devices, and applies to devices running:
87
-
88
-
* Android
89
-
* iOS/iPad OS
90
-
* macOS
91
-
* Windows
92
-
93
-
#### Blocking personal Android devices
94
-
By default, until you manually make changes in the admin center, your Android Enterprise work profile device settings and Android device administrator device settings are the same.
95
-
96
-
If you block Android Enterprise work profile enrollment on personal devices, only corporate-owned devices can enroll with [personally-owned work profiles](../apps/android-deployment-scenarios-app-protection-work-profiles.md#android-enterprise-personally-owned-work-profiles).
97
-
98
-
99
-
#### Blocking personal iOS/iPadOS devices
100
-
By default, Intune classifies iOS/iPadOS devices as personally-owned. To be classified as corporate-owned, an iOS/iPadOS device must fulfill one of the following conditions:
101
-
-[Registered with a serial number or IMEI](corporate-identifiers-add.md).
102
-
- Enrolled by using Automated Device Enrollment (formerly Device Enrollment Program).
103
-
104
-
> [!NOTE]
105
-
> An iOS User Enrollment profile overrides an enrollment restriction policy. For more information, see [Set up iOS/iPadOS and iPadOS User Enrollment (preview)](ios-user-enrollment.md).
106
-
107
-
#### Blocking personal Macs
108
-
By default, Intune classifies macOS devices as personally-owned. To be classified as corporate-owned, a Mac must fulfill one of the following conditions:
109
-
-[Registered with a serial number](corporate-identifiers-add.md).
110
-
- Enrolled by using Automated Device Enrollment (formerly Device Enrollment Program).
111
-
112
-
#### Blocking personal Windows devices
113
-
If you block personally owned Windows devices from enrollment, Intune checks to make sure that each new Windows enrollment request has been authorized for corporate enrollment. Unauthorized enrollments are blocked.
114
-
115
-
The following enrollment methods are authorized for corporate enrollment:
116
-
- The enrolling user is using a [device enrollment manager account](device-enrollment-manager-enroll.md).
117
-
- The device enrolls through [Windows Autopilot](../../autopilot/enrollment-autopilot.md).
118
-
- The device is registered with Windows Autopilot but isn't an MDM enrollment only option from Windows Settings.
119
-
- The device enrolls through a [bulk provisioning package](windows-bulk-enroll.md).
120
-
- The device enrolls through GPO, or [automatic enrollment from Configuration Manager for co-management](/configmgr/comanage/quickstart-paths#bkmk_path1).
121
-
122
-
> [!NOTE]
123
-
> Since a co-managed device enrolls in the Microsoft Intune service based on its Azure AD device token, and not a user token, only the default Intune enrollment restriction will apply to it.
124
-
125
-
Intune marks devices going through the following types of enrollments as corporate-owned. But Intune blocks devices enrolling since they don't offer the Intune administrator per-device control, they are blocked:
126
-
-[Automatic MDM enrollment](windows-enroll.md#enable-windows-automatic-enrollment) with [Azure Active Directory join during Windows setup](/azure/active-directory/device-management-azuread-joined-devices-frx)\*.
127
-
-[Automatic MDM enrollment](windows-enroll.md#enable-windows-automatic-enrollment) with [Azure Active Directory join from Windows Settings](/azure/active-directory/user-help/user-help-register-device-on-network)\*.
128
-
129
-
Intune also blocks personal devices using these enrollment methods:
130
-
-[Automatic MDM enrollment](windows-enroll.md#enable-windows-automatic-enrollment) with [Add Work Account from Windows Settings](/azure/active-directory/user-help/user-help-join-device-on-network)\*.
131
-
-[MDM enrollment only](/windows/client-management/mdm/mdm-enrollment-of-windows-devices#connecting-personally-owned-devices-bring-your-own-device) option from Windows Settings.
132
-
133
-
\* These won't be blocked if registered with Autopilot.
134
-
135
58
## Create a device platform restriction
136
59
137
60
1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
@@ -167,7 +90,7 @@ Intune also blocks personal devices using these enrollment methods:
167
90
168
91
10. Select **Next**.
169
92
11. On the **Assignments** page, select **Add groups** and then use the search box to find and select groups. To assign the restriction to all device users, select **Add all users**. If you don't assign a restriction to at least one group, the restriction won't take effect.
170
-
12. Optionally, after you assign groups, select **Edit filter** to restrict the policy assignment further with filters. Filters are available for macOS, iOS, and Windows policies. For more information, see [Apply assignment filters](enrollment-restrictions-set.md#apply-assignment-filters) (in this article).
93
+
12. Optionally, after you assign groups, select **Edit filter** to restrict the policy assignment further with filters. Filters are available for macOS, iOS, and Windows policies. For more information, see [Apply assignment filters](create-device-platform-restrictions.md#apply-assignment-filters) (in this article).
171
94
13. Select **Next**.
172
95
14. Review your policy, and then select **Create** to create it.
173
96
@@ -180,15 +103,15 @@ You can use assignment filters to include and exclude additional devices from ce
180
103
For example, you can use a filter to allow personal Windows devices to enroll while blocking devices that run a specific operating system SKU. To achieve this outcome, apply a preconfigured filter to your enrollment restriction assignments. The filter needs to have the `operatingSystemSKU` property in its rules. Example steps:
181
104
182
105
1. Create a platform enrollment restriction policy for Windows.
183
-
2. In the platform settings, select the option that allows personally-owned devices to enroll.
106
+
2. In the platform settings, select the option that allows personal devices to enroll.
184
107
3. In the assignments settings, select the groups you want to assign.
185
108
4. Select **Edit filter** and then apply your preconfigured filter that contains the `operatingSystemSKU` property. The applied property blocks devices running Windows 10 Home edition.
186
109
187
110
For more information about creating filters, see [Create a filter](../fundamentals/filters.md).
188
111
189
112
### Supported filter properties
190
113
191
-
Enrollment restrictions support fewer filter properties than other group-targeted policies. This is because devices are not yet enrolled, so Intune doesn't have the device info to support all properties. You'll see the limited selection of properties when you:
114
+
Enrollment restrictions support fewer filter properties than other group-targeted policies. This is because devices aren't yet enrolled, so Intune doesn't have the device info to support all properties. You'll see the limited selection of properties when you:
192
115
193
116
* Configure a device platform restriction policy for Apple and Windows devices.
194
117
* Configure an enrollment status page (ESP) policy for Windows.
@@ -209,7 +132,7 @@ The following filter properties are always available to use with enrollment poli
209
132
* Ownership
210
133
* Enrollment profile name
211
134
212
-
For more information about these properties, see [device properties](../fundamentals/filters-device-properties.md#device-properties). Filters cannot be used with Android enrollment restrictions.
135
+
For more information about these properties, see [device properties](../fundamentals/filters-device-properties.md#device-properties). Filters can't be used with Android enrollment restrictions.
213
136
214
137
## Edit enrollment restrictions
215
138
@@ -220,7 +143,7 @@ Edits are applied to new enrollments and do not affect devices that are already
220
143
3. Select **Properties**.
221
144
4. Select **Edit**
222
145
5. Make your changes and select **Review + save**.
Copy file name to clipboardExpand all lines: memdocs/intune/enrollment/device-enrollment.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -186,4 +186,4 @@ The MDM certificate renews automatically as long as enrolled devices are communi
186
186
187
187
## Next steps
188
188
189
-
You can adjust the settings in Intune to restrict specific platforms from enrolling. For more information, see [Create a device platform restriction](enrollment-restrictions-set.md#create-a-device-platform-restriction).
189
+
You can adjust the settings in Intune to restrict specific platforms from enrolling. For more information, see [Create a device platform restriction](create-device-platform-restrictions.md).
Copy file name to clipboardExpand all lines: memdocs/intune/enrollment/device-limit-intune-azure.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
---
2
2
# required metadata
3
3
4
-
title: Understand between Intune and Azure device limit restrictions
5
-
titleSuffix:
6
-
description: Understand the differences between Intune's device limit restrictions and Azure AD's delimit restrictions.
4
+
title: Understand Intune and Azure AD device limit restrictions
5
+
titleSuffix:Microsoft Intune
6
+
description: Learn the differences between Intune device limit restrictions and Azure AD's delimit restrictions.
7
7
keywords:
8
8
author: Lenewsad
9
9
ms.author: lanewsad
@@ -31,7 +31,7 @@ ms.collection:
31
31
- highpri
32
32
---
33
33
34
-
# Understand Intune and Azure AD's device limit restrictions
34
+
# Understand Intune and Azure AD device limit restrictions
35
35
36
36
**Applies to**
37
37
- Android
@@ -48,7 +48,7 @@ This article clarifies when these limits are applied based on your configuration
48
48
49
49
## Intune device limit restrictions
50
50
51
-
Intune device limit restrictions set the maximum number of devices that a user can control (maximum setting is 15). To set this **Device limit**, go to [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Devices** > **Enrollment restrictions**. For more information, see [Create a device limit restriction](enrollment-restrictions-set.md#create-a-device-limit-restriction)
51
+
Intune device limit restrictions set the maximum number of devices that a user can control (maximum setting is 15). To set this **Device limit**, go to [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Devices** > **Enrollment restrictions**. For more information, see [Create a device limit restriction](create-device-limit-restrictions.md).
52
52
53
53
## Azure device limit restriction
54
54
@@ -128,5 +128,4 @@ For the device limit restriction in Azure, the **Maximum number of devices per u
128
128
## Next steps
129
129
130
130
-[Create a device limit restriction in Azure.](/azure/active-directory/devices/device-management-azure-portal#configure-device-settings)
131
-
-[Configure device settings in Azure.](enrollment-restrictions-set.md#create-a-device-limit-restriction)
132
131
-[Learn more about registration and domain joined.](/azure/active-directory/devices/overview#getting-devices-in-azure-ad)
0 commit comments