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
Set up enrollment notifications in Microsoft Intune to notify employees of newly-enrolled devices. You can create a custom message for employees and include information in the notification about how to report an unrecognized device.
39
+
Set up enrollment notifications in Microsoft Intune to notify employees of newlyenrolled devices. You can create a custom message for employees and include information in the notification about how to report an unrecognized device.
40
40
41
41
Intune delivers enrollment notifications via email or push notification. You can apply your tenant's branding and customization settings to email notifications.
42
42
@@ -50,7 +50,7 @@ Enrollment notifications work on devices running:
50
50
This article describes how to create enrollment notifications in the Microsoft Endpoint Manager admin center.
51
51
52
52
## Example
53
-
The following example image shows what the enrollment notification looks like to the device user.
53
+
The following example image shows what an enrollment notification looks like to a device user.
54
54
55
55
> [!div class="mx-imgBorder"]
56
56
> 
@@ -117,7 +117,9 @@ Email notifications appear in the user's inbox. Push notifications appear in the
117
117
***Show Company portal website link**: Flip the switch **On** to show a link to the Company Portal website. The tenant value is automatically populated.
118
118
8. Select **Next**.
119
119
9. Optionally, assign a scope tag, like `US-NC IT Team` or `JohnGlenn_ITDepartment`, to limit management of the notification to specific IT groups. Then select **Next**.
120
-
10. In **Assignments**, select the users or groups that will receive your profile. You can also apply assignment filters, which are available for Windows and Apple devices.
120
+
10. In **Assignments**, select the users or groups receiving the notification.
121
+
122
+
Optionally, you can apply assignment filters. For more information about using filters on enrollment policies like this one, see [Supported filter properties](../enrollment/create-device-platform-restrictions.md#supported-filter-properties). Assignment filters are available for Windows and Apple enrollments.
121
123
11. Select **Next**.
122
124
12. In **Review + create**, review the notification details, and then select **Create**.
### New app types for Microsoft Endpoint Manager<!-- 7210233 -->
70
-
As an admin, you will be able to create and assign two new types of Intune apps:
71
-
-**iOS/iPadOS web clip**
72
-
-**Windows web link**
73
-
74
-
These new app types work in a similar way to the existing **web link** application type, however they apply only for their specific platform, whereas web link applications apply across all platforms. With these new app types, you can assign to groups and also use assignment filters to limit the scope of assignment. You will find this functionality in [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), by selecting **Apps** > **All Apps** > **Add**.
75
-
76
-
### Ending support for Windows 8.1<!-- 14740233 -->
77
-
Microsoft Intune will be ending support on October 21, 2022 for devices running Windows 8.1. After that date, technical assistance and automatic updates that help protect your devices running Windows 8.1 will no longer be available. Additionally, because the sideloading scenario for line-of-business apps is only applicable to Windows 8.1 devices, Intune will no longer support Windows 8.1 sideloading. Sideloading is installing, and then running or testing an app that isn't certified by the Microsoft Store. In Windows 10/11, "sideloading" is simply setting a device config policy to include "Trusted app installation". For more information, see [Plan for Change: Ending support for Windows 8.1](../fundamentals/whats-new.md#plan-for-change-ending-support-for-windows-81-).
### Support for Locate device on Android Enterprise corporate owned fully managed and Android Enterprise corporate owned work profile devices<!-- 12391424 -->
### Intune moving to support iOS/iPadOS 14 and higher later this year<!-- 14778947 -->
95
-
Later this year, Apple is expected to release iOS/iPadOS 16. Due to this expected release, Microsoft Intune and the Intune Company Portal will require iOS/iPadOS 14 and higher shortly after the release of iOS/iPad 16. For related information, see [Supported operating systems and browsers in Intune](../fundamentals/supported-devices-browsers.md).
96
-
97
-
### Intune moving to support macOS 11.6 and higher later this year<!-- 14766663 -->
98
-
With Apple's expected release of macOS 13 Ventura later this year, Microsoft Intune, the Company Portal app, and the Intune MDM agent will be moving to support macOS 11.6 (Big Sur) and later. For related information, see [Supported operating systems and browsers in Intune](../fundamentals/supported-devices-browsers.md).
@@ -108,55 +88,6 @@ Windows Autopilot diagnostics will automatically capture diagnostics about Windo
108
88
109
89
## Device configuration
110
90
111
-
### New settings available in the iOS/iPadOS and macOS Settings Catalog<!-- 15349701 -->
112
-
The [Settings Catalog](../configuration/settings-catalog.md) lists all the settings you can configure in a device policy, and all in one place. There are new settings are available in the Settings Catalog. In [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), you'll be able to find these settings by selecting **Devices** > **Configuration profiles** > **Create profile** > **iOS/iPadOS** or **macOS** for platform > **Settings catalog** for profile type.
113
-
114
-
New settings include:
115
-
116
-
**Accounts > LDAP**:
117
-
118
-
- LDAP Account Description
119
-
- LDAP Account Host Name
120
-
- LDAP Account Password
121
-
- LDAP Account Use SSL
122
-
- LDAP Account User Name
123
-
- LDAP Search Settings
124
-
125
-
Applies to:
126
-
- iOS/iPadOS
127
-
- macOS
128
-
129
-
The following settings are also in Settings Catalog. Previously, they were only available in Templates:
130
-
131
-
**Privacy > Privacy Preferences Policy Control**:
132
-
133
-
- Accessibility
134
-
- Address Book
135
-
- Apple Events
136
-
- Calendar
137
-
- Camera
138
-
- File Provider Presence
139
-
- Listen Event
140
-
- Media Library
141
-
- Microphone
142
-
- Photos
143
-
- Post Event
144
-
- Reminders
145
-
- Screen Capture
146
-
- Speech Recognition
147
-
- System Policy All Files
148
-
- System Policy Desktop Folder
149
-
- System Policy Documents Folder
150
-
- System Policy Downloads Folder
151
-
- System Policy Network Volumes
152
-
- System Policy Removable Volumes
153
-
- System Policy Sys Admin Files
154
-
155
-
Applies to:
156
-
- macOS
157
-
158
-
For more information about configuring Settings Catalog profiles in Intune, see [Create a policy using settings catalog](../configuration/settings-catalog.md).
159
-
160
91
### Filter app and group policy assignments using Windows 11 SE operating system SKUs<!-- 10588651 -->
161
92
When you assign an app or policy, you can filter the assignment using different device properties, such as device manufacturer, operating system SKU, and more.
162
93
@@ -169,41 +100,6 @@ For more information on filters and the device properties you can currently use,
169
100
Applies to:
170
101
- Windows 11 SE
171
102
172
-
### New lock screen message when adding custom support information to Android Enterprise devices<!-- 13158348 -->
173
-
On Android Enterprise devices, you can create a device restrictions configuration profile that shows a custom support message on the devices. You'll be able to configure this in [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) by selecting **Devices** > **Configuration profiles** > **Create profile** > **Android Enterprise** > **Fully managed, dedicated, and corporate-owned work profile** for platform > **Device restrictions** for profile type > **Custom support information**.
174
-
175
-
There will be a new setting you can configure:
176
-
-**Lock screen message**: Add a message that's shown on the device lock screen.
177
-
178
-
When you configure the **Lock screen message**, you can also use the following device tokens to show device-specific information:
179
-
180
-
-`{{AADDeviceId}}`: Azure AD device ID
181
-
-`{{AccountId}}`: Intune tenant ID or account ID
182
-
-`{{DeviceId}}`: Intune device ID
183
-
-`{{DeviceName}}`: Intune device name
184
-
-`{{domain}}`: Domain name
185
-
-`{{EASID}}`: Exchange Active Sync ID
186
-
-`{{IMEI}}`: IMEI of the device
187
-
-`{{mail}}`: Email address of the user
188
-
-`{{MEID}}`: MEID of the device
189
-
-`{{partialUPN}}`: UPN prefix before the @ symbol
190
-
-`{{SerialNumber}}`: Device serial number
191
-
-`{{SerialNumberLast4Digits}}`: Last 4 digits of the device serial number
192
-
-`{{UserId}}`: Intune user ID
193
-
-`{{UserName}}`: User name
194
-
-`{{userPrincipalName}}`: UPN of the user
195
-
196
-
> [!NOTE]
197
-
> Variables aren't validated in the UI and are case sensitive. As a result, you may see profiles saved with incorrect input. For example, if you enter `{{DeviceID}}`, instead of `{{deviceid}}` or `{{DEVICEID}}`, then the literal string is shown instead of the device's unique ID. Be sure to enter the correct information. All lowercase or all uppercase variables are supported, but not a mix.
198
-
199
-
To see a list of settings you can currently configure, go to [Android Enterprise device settings to allow or restrict features using Intune](../configuration/device-restrictions-android-for-work.md).
### New password complexity requirements for Android Enterprise 12+ personally owned devices with a work profile<!-- 12436068 -->
208
104
On Android Enterprise 11 and older personally owned devices with a work profile, you can set the **Required password type** and a **Minimum password length** in device configuration profiles and compliance policies.
209
105
@@ -231,30 +127,10 @@ Applies to:
231
127
- Android 12.0 and newer
232
128
- Android Enterprise personally owned devices with a work profile
233
129
234
-
### Filter on the user scope or device scope in the Settings Catalog for Windows devices<!-- 13949975 -->
235
-
When you create a Settings Catalog policy, you can use **Add settings** > **Add filter** to filter settings based on the Windows OS edition (**Devices** > **Configuration profiles** > **Create profile** > **Windows 10 and later** for platform > **Settings Catalog (preview)** for profile type).
236
-
237
-
When you **Add filter**, you'll be able to filter on the settings by user scope or device scope.
238
-
239
-
For more information, go to [Use the settings catalog to configure settings: Device scope vs. user scope settings](../configuration/settings-catalog.md#device-scope-vs-user-scope-settings)
### Trend Micro – new Mobile Threat Defense (MTD) partner<!--11017779 -->
250
-
You’ll soon be able to use Trend Micro as an integrated Mobile Threat Defense (MTD) partner with Intune. To connect Trend Micro, you’ll configure the Trend Micro MTD connector in the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) at **Tenant administration** > **Connectors and tokens** > **Mobile Threat Defense**.
251
-
252
-
With Trend Micro as a MTD partner, you’ll be able to control mobile device access to your organization’s resources using conditional access that’s based on risk assessment.
253
-
254
-
Applies to:
255
-
- Android Enterprise
256
-
- iOS/iPadOS
257
-
258
134
### Reusable groups of settings for Microsoft Defender Firewall Rules<!-- 5653346, 6009541 -->
259
135
You’ll soon be able to add reusable groups of settings to your profiles for Microsoft Defender Firewall Rules. The reusable groups are collections of remote IP addresses and FQDNs that you define one time and can then use with one or more firewall rule profiles. You’ll no longer need to reconfigure the same group of IP addresses in each individual profile that might require them.
Copy file name to clipboardExpand all lines: memdocs/intune/protect/certificate-connector-overview.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ keywords:
7
7
author: brenduns
8
8
ms.author: brenduns
9
9
manager: dougeby
10
-
ms.date: 08/03/2022
10
+
ms.date: 09/21/2022
11
11
ms.topic: how-to
12
12
ms.service: microsoft-intune
13
13
ms.subservice: protect
@@ -384,6 +384,12 @@ New updates for the connector can take a week or more to become available for ea
384
384
> [!IMPORTANT]
385
385
> Starting April 2022, certificate connectors earlier than version **6.2101.13.0** will be deprecated and will show a status of *Error*. Starting August 2022, these connector versions **won't** be able to revoke certificates. Starting September 2022, these connector versions **won't** be able to issue certificates. This includes both the [PFX Certificate Connector for Microsoft Intune](../protect/certificate-connectors.md#pfx-certificate-connector-release-history) and [Microsoft Intune Connector](../protect/certificate-connectors.md#microsoft-intune-connector-release-history), which on July 29, 2021 were replaced by the *Certificate Connector for Microsoft Intune* (as detailed in this article).
386
386
387
+
### September 21, 2202
388
+
389
+
Version **6.2206.122.0** - Changes in this release:
390
+
391
+
- Improved telemetry in addition to bug fixes and performance improvements
392
+
387
393
### June 30, 2022
388
394
389
395
Version **6.2205.201.0** - Changes in this release:
@@ -434,6 +440,7 @@ This update includes:
434
440
- Additional logging for Digicert PKCS requests
435
441
- Enhancement to cryptography operations made during handling of PKCS requests
436
442
443
+
<!-- archived update details that are over one year old:
437
444
### August 16, 2021
438
445
439
446
Version **6.2108.18.0**. This update includes:
@@ -447,6 +454,7 @@ Version **6.2107.45.0** - The Certificate Connector for Microsoft Intune is rele
447
454
448
455
This connector is a unified connector in that it includes the capabilities of both the *PFX Certificate Connector for Microsoft Intune* and *Microsoft Intune Connector*, which it replaces. With this release, the previous connectors remain supported, but are no longer developed nor available for download. Plan to replace existing installations of the individual with installations of this new unified connector.
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