The user is prompted to install the Microsoft Authenticator app. The file should be encrypted and unable to be opened outside the managed app. You can validate it by attempting to open the 'corporate' file outside of the managed app. Therefore, Intune encrypts 'corporate' data before sharing it outside the app. Intune app protection policy can't control the iOS/iPadOS share extension without managing the device. The user can use the iOS/iPadOS share extension to open work or school data in unmanaged apps, even with the data transfer policy set to Managed apps only or No apps. They often indicate an error was made by the IT administrator or a bug with the app protection policy. These messages and dialogs do not indicate an error or bug.Įrror messages and dialogs on iOS, Error messages and dialogs on Android: Error messages and dialogs a user might see on apps that have an Intune app protection policy. They are not actual issues, but may be perceived as bugs or errors.Ĭommon usage dialogs: Usage dialogs a user might see in apps that have an Intune app protection policy. It provides an explanation and solution, when available, for user issues in the following categories:Ĭommon usage scenarios: A user might experience these scenarios on apps that have an Intune app protection policy. Obviously the user executing this script should be able to modify the registry.This article provides solutions to common user issues and error messages related to Intune app protection policies. If you have to modify this for a large number of users then perhaps a user logon script to address this would be a better approach reg delete 'HKEY_CURRENT_USER/Software/IM Providers' /v DefaultIMApp reg add 'HEY_CURRENT_USER/Software/IM Providers' /v DefaultIMApp /t Reg_sz /d Lync Restart Outlook and presence will be shown. I found the offending registry key HKCU/Software/IM ProvidersĬhange the DefaultIMApp String Value from Cisco Jabber or whatever it is to Lync

In order to resolve this I needed to change this. This is read by Outlook 2013 to determine presence. It turns out that it was a user profile issue where the Cisco Jabber whether it was installed or not had been set as the Default IM App Provider. I also found that each of these users had Cisco Jabber installed, or had been installed at one point. It turned out that the users affected were part of the Cisco Voice team. I concluded that it must be a common issue with the local machines rather than the Lync server so I began to try and find the common link between each affected user. When investigating this I found that all users had the exact same version of Office 2013 with the same updates but some users were seeing presence just fine. When installing Lync the other day I came across an issue where certain users could not view presence status of users in Outlook 2013.

Microsoft outlook presence unknown