Resolved - Support Tip: Occasionally occurring with iOS MAM and Office apps
We had a few cases on this recently and after investigation, decided to share this known issue that affects sign in on iOS Mobile Application Management (MAM, also known as APP). It does not impact the majority of users, but for the one that it does impact, it prompts for sign in when an Office app is opened. Office has a fix in their backlog; in the interim, read this post for a way to clear it up if you have a user running into this scenario.Known issue with “Rename device” setting for Windows 10 devices in the Intune console
Updated 01/25/21 - You can now rename a co-managed device that is Azure AD joined. The “Rename device” setting is currently disabled for Hybrid Azure AD joined devices. Intune Engineering is continuing to work with our Windows and Azure Active Directory teams to investigate this feature and restore it’s functionality within Intune. Stay tuned to this blog for any future updates regarding this feature. We’ve discovered an issue with a new feature that was recently released in the console. If you manage Windows 10 devices, you may have seen a new “Rename device” setting in the console to rename an enrolled Windows 10 device. We’ve found that the renaming flow using this setting might not complete on Windows devices that are joined to on premises Active Directory, including Hybrid Azure AD joined devices. This setting has now been temporarily disabled for Hybrid Azure AD joined devices to prevent device login errors. Here’s the current experience in the Intune console. When you go to Devices > All Devices and choose a Windows device, you will see an option to rename the device. On renaming the device, the new name is reflected in the Intune console and in Azure AD. However, we’ve seen some cases where the new device name is not reflected in the on premises Active Directory. This can result in login errors where a user may be able to log on to their device initially but may experience single sign-on (SSO) errors when they try to login again after a password change. Engineering is still working to understand the cause and remediation. We've temporarily disabled this setting in the console for Hybrid Azure AD joined devices and Azure AD joined co-managed devices (you can now rename a co-managed device that is Azure AD joined) until we have a fix for this issue. Stay tuned to this post for more information as we investigate. Blog post updates: 5/17/19 - This post previously shared that the impact was limited to Hybrid Azure AD joined devices. We've since updated the post to include Azure AD co-managed devices. 8/7/19 - We’ve received reports from customers around this issue. Engineering is still continuing to restore this feature within the console. 1/17/20 - We've followed up with the team, and they are continuing to work with the respective teams on this feature. 12/30/20 - Updated post on current investigation status. 01/25/21 - Updated post that can now rename a co-managed device that is Azure AD joined.
