Skip to content

Commit ab36229

Browse files
authored
Merge pull request #8456 from Erikre/erikre-wn2209-15468520
erikre-wn2209-15468520
2 parents 1a3a173 + ad38c3f commit ab36229

1 file changed

Lines changed: 190 additions & 1 deletion

File tree

memdocs/intune/fundamentals/whats-new.md

Lines changed: 190 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords:
77
author: Erikre
88
ms.author: erikre
99
manager: dougeby
10-
ms.date: 09/20/2022
10+
ms.date: 09/21/2022
1111
ms.topic: conceptual
1212
ms.service: microsoft-intune
1313
ms.subservice: fundamentals
@@ -59,8 +59,197 @@ You can use RSS to be notified when this page is updated. For more information,
5959
### Monitor and troubleshoot
6060
### Role-based access control
6161
### Scripts
62+
### Tenant administration
6263
-->
6364

65+
## Week of September 19, 2022 (Service release 2209)
66+
67+
### App management
68+
69+
#### 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+
### Device management
77+
78+
#### Microsoft Intune will be ending support for Windows 8.1<!-- 14740233 -->
79+
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-).
80+
81+
#### Group member count visible in assignments<!-- 13434676 -->
82+
When assigning policies in the admin center, you can now see the number of users and devices in a group. Having both counts will help you pinpoint the right group and understand the impact the assignment has before you apply it.
83+
84+
### Device configuration
85+
86+
#### New lock screen message when adding custom support information to Android Enterprise devices<!-- 13158348 -->
87+
On Android Enterprise devices, you can create a device restrictions configuration profile that shows a custom support message on the devices (**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**).
88+
89+
There's a new setting you can configure:
90+
- **Lock screen message**: Add a message that's shown on the device lock screen.
91+
92+
When you configure the **Lock screen message**, you can also use the following device tokens to show device-specific information:
93+
- `{{AADDeviceId}}`: Azure AD device ID
94+
- `{{AccountId}}`: Intune tenant ID or account ID
95+
- `{{DeviceId}}`: Intune device ID
96+
- `{{DeviceName}}`: Intune device name
97+
- `{{domain}}`: Domain name
98+
- `{{EASID}}`: Exchange Active Sync ID
99+
- `{{IMEI}}`: IMEI of the device
100+
- `{{mail}}`: Email address of the user
101+
- `{{MEID}}`: MEID of the device
102+
- `{{partialUPN}}`: UPN prefix before the `@` symbol
103+
- `{{SerialNumber}}`: Device serial number
104+
- `{{SerialNumberLast4Digits}}`: Last four digits of the device serial number
105+
- `{{UserId}}`: Intune user ID
106+
- `{{UserName}}`: User name
107+
- `{{userPrincipalName}}`: UPN of the user
108+
109+
> [!NOTE]
110+
> 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.
111+
112+
For more information on this setting, go to [Android Enterprise device settings to allow or restrict features using Intune](../configuration/device-restrictions-android-for-work.md#custom-support-information).
113+
114+
Applies to:
115+
- Android 7.0 and newer
116+
- Android Enterprise corporate owned fully managed
117+
- Android Enterprise corporate owned dedicated devices
118+
- Android Enterprise corporate owned work profile
119+
120+
#### Filter on the user scope or device scope in the Settings Catalog for Windows devices<!-- 13949975 -->
121+
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).
122+
123+
When you **Add filter**, you can also filter on the settings by user scope or device scope.
124+
125+
For more information on the settings catalog, go to [Use the settings catalog to configure settings on Windows, iOS/iPadOS and macOS devices](../configuration/settings-catalog.md).
126+
127+
Applies to:
128+
- Windows 10
129+
- Windows 11
130+
131+
#### Android Open Source Project (AOSP) platform is generally available<!-- 15027949 -->
132+
Microsoft Intune management of corporate-owned devices that run on the Android Open Source Project (AOSP) platform is now generally available (GA). This includes the full suite of capabilities that have been made available as part of the public preview.
133+
134+
Currently, Microsoft Intune only supports the new Android (AOSP) management option for RealWear devices.
135+
- [Deployment guide: Manage Android devices in Microsoft Intune](deployment-guide-platform-android.md)
136+
- [Deployment guide: Enroll Android devices in Microsoft Intune](deployment-guide-enrollment-android.md)
137+
138+
Applies to:
139+
- Android Open Source Project (AOSP)
140+
141+
#### Device Firmware Configuration Interface (DFCI) now supports Acer devices<!-- 15240661 -->
142+
For Windows 10/11 devices, you can create a DFCI profile to manage UEFI (BIOS) settings (**Devices** > **Configuration profiles** > **Create profile** > **Windows 10 and later** for platform > **Templates** > **Device Firmware Configuration Interface** for profile type).
143+
144+
New Acer devices running Windows 10/11 will be enabled for DFCI starting Fall 2022. So, admins can create DFCI profiles to manage the BIOS and then deploy the profiles to these Acer devices.
145+
146+
Contact your device vendor or device manufacturer to ensure you get eligible devices.
147+
148+
For more information about DFCI profiles in Intune, go to [Use Device Firmware Configuration Interface (DFCI) profiles on Windows devices in Microsoft Intune](../configuration/device-firmware-configuration-interface-windows.md).
149+
150+
Applies to:
151+
- Windows 10
152+
- Windows 11
153+
154+
#### New settings available in the iOS/iPadOS and macOS Settings Catalog<!-- 15349701 -->
155+
The [Settings Catalog](../configuration/settings-catalog.md) lists all the settings you can configure in a device policy, and all in one place.
156+
157+
There are new settings available in the Settings Catalog. In the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), you can see these settings at **Devices** > **Configuration profiles** > **Create profile** > **iOS/iPadOS** or **macOS** for platform > **Settings catalog** for profile type.
158+
159+
New settings include:
160+
161+
**Accounts > LDAP**:
162+
163+
- LDAP Account Description
164+
- LDAP Account Host Name
165+
- LDAP Account Password
166+
- LDAP Account Use SSL
167+
- LDAP Account User Name
168+
- LDAP Search Settings
169+
170+
Applies to:
171+
- iOS/iPadOS
172+
- macOS
173+
174+
The following settings are also in Settings Catalog. Previously, they were only available in Templates:
175+
176+
**Privacy > Privacy Preferences Policy Control**:
177+
178+
- Accessibility
179+
- Address Book
180+
- Apple Events
181+
- Calendar
182+
- Camera
183+
- File Provider Presence
184+
- Listen Event
185+
- Media Library
186+
- Microphone
187+
- Photos
188+
- Post Event
189+
- Reminders
190+
- Screen Capture
191+
- Speech Recognition
192+
- System Policy All Files
193+
- System Policy Desktop Folder
194+
- System Policy Documents Folder
195+
- System Policy Downloads Folder
196+
- System Policy Network Volumes
197+
- System Policy Removable Volumes
198+
- System Policy Sys Admin Files
199+
200+
Applies to:
201+
202+
- macOS
203+
204+
For more information about configuring Settings Catalog profiles in Intune, see [Create a policy using settings catalog](../configuration/settings-catalog.md).
205+
206+
### Device enrollment
207+
208+
#### Set up enrollment notifications (public preview)<!-- 9283605 -->
209+
Enrollment notifications inform device users, via email or push notification, when a new device has been enrolled in Microsoft Intune. You can use enrollment notifications for security purposes to notify users and help them report devices enrolled in error, or for communicating to employees during the hiring or onboarding process. Enrollment notifications are available to try now in public preview for Windows, Apple, and Android devices. This feature is only supported with user-driven enrollment methods.
210+
211+
### Device security
212+
213+
#### Assign compliance policies to the All devices group<!-- 2213410 -->
214+
The **All devices** option is now available for [compliance policy](../protect/create-compliance-policy.md) assignments. With this option you can assign a compliance policy to all enrolled devices in your organization that match the policy's platform, without needing to create an Azure Active Directory group that contains all devices.
215+
216+
When you include the *All devices* group you can then exclude individual groups of devices to further refine the assignment scope.
217+
218+
#### Trend Micro – New mobile threat defense partner<!-- 11017779 -->
219+
You can now use [Trend Micro Mobile Security](../protect/trend-micro-mobile-threat-defense-connector.md) as an integrated mobile threat defense (MTD) partner with Intune. By configuring the Trend MTD connector in Intune, you can control mobile device access to corporate resources using conditional access that's based on risk assessment.
220+
221+
For more information, see:
222+
- [Mobile threat defense integration with Intune](../protect/mobile-threat-defense.md)
223+
- [Trend Micro Mobile Security documentation](https://docs.trendmicro.com/en-us/enterprise/trend-micro-vision-one/mobile-security/getting-started-with_003.aspx)
224+
225+
#### Grace period status visible on Intune Company Portal website<!-- 15025900 -->
226+
The Intune Company Portal website now shows a grace period status to account for devices that don't meet compliance requirements but are still within their given grace period. Users are shown the date by which they need to become compliant and the instructions for how to become compliant. If they don't update their device by the given date, their status changes to noncompliant. For more information about setting grace periods, see [Configure compliance policies with actions for noncompliance](../protect/actions-for-noncompliance.md#available-actions-for-noncompliance).
227+
228+
### Intune apps
229+
230+
#### Newly available protected apps for Intune<!-- 15007580, 15235927 -->
231+
The following protected apps are now available for Microsoft Intune:
232+
- RingCentral for Intune by RingCentral, Inc.
233+
- MangoApps, Work from Anywhere by MangoSpring, Inc.
234+
235+
For more information about protected apps, see [Microsoft Intune protected apps](../apps/apps-supported-intune-apps.md).
236+
237+
### Tenant administration
238+
239+
#### Access policies for Multiple Administrator Approval in public preview<!--9348867 -->
240+
In public preview, you can use Intune *access policies* to require that a second Administrator Approval account be used to approve a change before the change is applied. This capability is known as multiple Administrator Approval (MAA).
241+
242+
You create an access policy to protect a type of resource, like App deployments. Each access policy also includes a group of users who are *approvers* for the changes protected by the policy. When a resource like an app deployment configuration is protected by an access policy, any changes that are made to the deployment, including creating, deleting or modifying an existing deployment won't apply until a member of the approvers group for that access policy reviews and approves that change.
243+
244+
Approvers can also reject requests, and both the individual requesting a change and the approver can provide notes about the change, or why it was approved or rejected.
245+
246+
Access policies are supported for the following resources:
247+
248+
- **Apps** – Applies to [app deployments](../apps/apps-add.md), but doesn't apply to app protection policies.
249+
- **Scripts** – Applies to deploying scripts to devices that run [macOS](../apps/macos-shell-scripts.md) or [Windows](../apps/intune-management-extension.md).
250+
251+
For more information, see [Use Access policies to require multiple administrative approval](../fundamentals/multi-admin-approval.md).
252+
64253
## Week of September 12, 2022
65254

66255
### Device management

0 commit comments

Comments
 (0)