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/certificates-profile-scep.md
+23-5Lines changed: 23 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,11 +57,26 @@ Devices that run Android Enterprise might require a PIN before SCEP can provisio
57
57
58
58
SCEP certificate profiles for the *Fully Managed, Dedicated, and Corporate-Owned Work Profile* profile have the following limitations:
59
59
60
-
1. Under Monitoring, certificate reporting isn't available for Device Owner SCEP certificate profiles.
60
+
1. Under Monitoring, certificate reporting isn't available for **Device Owner** SCEP certificate profiles.
61
+
1. You can't use Intune to revoke certificates that were provisioned by SCEP certificate profiles for **Device Owner**. You can manage revocation through an external process or directly with the certification authority.
62
+
1. For Android Enterprise dedicated devices, SCEP certificate profiles are supported for Wi-Fi network configuration, VPN, and authentication. SCEP certificate profiles on Android Enterprise dedicated devices aren't supported for app authentication.
61
63
62
-
2. You can't use Intune to revoke certificates that were provisioned by SCEP certificate profiles for Device Owners. You can manage revocation through an external process or directly with the certification authority.
64
+
For **Android (AOSP)**, the following limitations apply:
63
65
64
-
3. For Android Enterprise dedicated devices, SCEP certificate profiles are supported for Wi-Fi network configuration, VPN, and authentication. SCEP certificate profiles on Android Enterprise dedicated devices aren't supported for app authentication.
66
+
1. Under Monitoring, certificate reporting isn't available for **Device Owner** SCEP certificate profiles.
67
+
1. You can't use Intune to revoke certificates that were provisioned by SCEP certificate profiles for **Device Owners**. You can manage revocation through an external process or directly with the certification authority.
68
+
1. SCEP certificate profiles are supported for Wi-Fi network configuration. VPN configuration profile support is not available. A future update may include support for VPN configuration profiles.
69
+
1. The following 3 variables are not available for use on Android (AOSP) SCEP certificate profiles. Support for these variables will come in a future update.
70
+
- onPremisesSamAccountName
71
+
- OnPrem_Distinguished_Name
72
+
- Department
73
+
74
+
> [!NOTE]
75
+
> **Device Owner** is equivalent to Corporate Owned devices. The following are considered as Device Owner:
76
+
> - Android Enterprise - Fully Managed, Dedicated, and Corporate-Owned Work Profile
77
+
> - Android AOSP
78
+
> - User-affinity
79
+
> - User-less
65
80
66
81
4. Select **Create**.
67
82
@@ -75,7 +90,7 @@ Devices that run Android Enterprise might require a PIN before SCEP can provisio
75
90
76
91
-**Certificate type**:
77
92
78
-
*(Applies to: Android, Android Enterprise, iOS/iPadOS, macOS, Windows 8.1, and Windows 10/11)*
93
+
*(Applies to: Android, Android Enterprise, Android (AOSP), iOS/iPadOS, macOS, Windows 8.1, and Windows 10/11)*
79
94
80
95
Select a type depending on how you'll use the certificate profile:
81
96
@@ -259,9 +274,12 @@ Devices that run Android Enterprise might require a PIN before SCEP can provisio
259
274
260
275
-**Hash algorithm**:
261
276
262
-
*(Applies to Android, Android enterprise, Windows 8.1, and Windows 10/11)*
277
+
*(Applies to Android, Android (AOSP), Android enterprise, Windows 8.1, and Windows 10/11)*
263
278
264
279
Select one of the available hash algorithm types to use with this certificate. Select the strongest level of security that the connecting devices support.
280
+
281
+
NOTE: Android AOSP and Android Enterprise devices will select the strongest algorithm supported - SHA-1 will be ignored, and SHA-2 will be used instead.
0 commit comments