Release notes for Microsoft Intune
|Applies to: Intune in the classic portal|
|Looking for documentation about the Intune Azure portal preview? Go here.|
Microsoft Intune is an integrated, cloud-based client management solution that provides tools, reports, and upgrade licenses to the latest version of Windows. It also helps keep your computers up-to-date and secure. In addition, Intune lets you manage mobile devices on the network either through Exchange ActiveSync or directly through Intune. The following release notes describe important information and known issues in Microsoft Intune.
Android users can’t send email when conditional access for Exchange Online is implemented
Issue: Users running Samsung Android 5.1.1 and later on their devices can't send email when conditional access for Exchange Online has been set up. Samsung acknowledges that the issue is in its built-in email client in Android 5.1.1 and later, and is investigating a fix.
Workaround 1: Advise users to use the Outlook app for Android.
Workaround 2: To let affected users send email, you can follow these steps:
- Put each affected user in a security group in the “exempted groups” section of the conditional access policy for Exchange Online.
- Let the user temporarily sync email on the built-in email client.
- Remove the affected user from the exempted group, and confirm that the user can now send email.
Microsoft will continue to work closely with Samsung on a fix or additional workarounds.
Changing resource access profiles between groups for iOS and Android might fail
Issue: When you change email or Simple Certificate Enrollment Protocol (SCEP) resource access profiles between groups, the profiles might conflict and fail. For example, let’s say that you have an existing email profile that points to an on-premises Exchange server, targeted to Group A. Then, you create a new email profile that points to Exchange Online, targeted to Group B. When you move users from Group A to Group B, devices will keep the on-premises Exchange email profile and try to install the Exchange Online email profile that is targeted to Group B.
At this point, one of the following occurs:
- If email profiles A and B are identical, the device rejects email profile B because email profile B already contains email profile A.
- If email profile A is different from email profile B, as mentioned in the example, the device ends up with two email profiles.
The host name and the attribute used for user name are checked to distinguish one email profile from another.
In both cases, the resource access profile (email profile) was not removed from the device in order to prevent the unintentional removal of a user’s access to email or the client's SCEP certificate.
When you enroll a Windows 8.1 device that must authenticate to a proxy server, the enrollment process fails with no visible cause
Issue: When you enroll a Windows 8.1 device and the device must authenticate to a proxy server during the enrollment process, the enrollment fails if the device has not cached the proxy server credentials. When the credentials for the proxy server are not cached on the device, the enrollment process must wait for the user to enter the credentials. But, the prompt to provide the proxy server credentials does not appear during the enrollment process. The result is that the enrollment process cannot authenticate to the proxy server. No visible indication of this failure is presented to the user.
Workaround: For Windows 8.1 devices that must enroll on a network that requires use of an authenticated proxy server, set up and save the credentials for the proxy server prior to enrollment of the device. To set up and save the credentials on a Windows 8.1 device:
- On the Windows 8.1 device, open Internet Explorer.
- When you're prompted for the proxy server credentials, enter the credentials and then choose the option Remember my credentials.
- Enroll the device.
Windows Phone 8.1 devices fail to enroll with Microsoft Intune when device authentication is enabled in AD FS
Issue: When you enroll a Windows Phone 8.1 device, enrollment fails if the optional setting for device authentication is enabled as part of the global authentication policy in Active Directory Federation Services (AD FS).
Workaround: Disable device authentication on the AD FS server by unchecking Enable device authentication in Edit Global Authentication Policy. For more information, see Configuring Authentication Policies.
Microsoft Intune App Wrapping Tool for Android has no built-in uninstall capability
Issue: The Microsoft App Wrapping Tool for Android does not have built-in functionality for uninstalling the tool.
Workaround: Browse to the location where you installed the tool, and delete the directory. The default installation location is: C:\Program Files (x86)\Microsoft Intune Mobile Application Management\Android\App Wrapping Tool. For more about the app wrapping tool, see Prepare Android apps for management with App Wrapping Tool.
Remote assistance is not available on computers that run Windows 8 or Windows 8.1
Issue: In this release, the remote assistance feature is not available on computers that run Windows 8 or Windows 8.1.
Alert notifications for recipients that are automatically added might not work
Issue: If recipients are automatically added to an alert notification, they might not always receive a notification.
Workaround: To make sure that recipients will receive message notifications, you should manually add recipients to alert notifications.
Language support in the Azure portal
The Azure portal supports these languages: Chinese (Simplified), Chinese (Traditional), Czech, Dutch, English, German, Hungarian, Italian, Japanese, Portuguese (Brazil), Portuguese (Portugal), Russian, Spanish, English, French, Korean, Polish, Swedish, Turkish.
The Intune Admin Console and the user-facing mobile experiences support Danish, Greek, Finnish, Norwegian, and Romanian, in addition to all the languages that the Azure portal supports.