The good news is that you can apply this policy even to devices that you are not managing with an MDM profile. This to possibly limit the damage in case of a data leak, and on the other hand, keep it workable for the end user. Sometimes companies are also worried about syncing contacts from the Managed Outlook application to the native unsecured Contacts application, this partly because they are afraid of data leaks and the fact that other non-managed applications can have access to the contacts that are synced to the native unsecured Contacts application.įortunately, with a separate App Config policy, you can force Contact Sync for the end user, so users don’t have to call the support desk anymore, and you can limit the Contact fields that may be synchronized to the native Contacts application, for example only name and phone number and block all other information from syncing. Most of the time, this end user will call the support desk for it which causes quite a load on that department after such an implementation. Within an App Protection policy you can Allow contact sync with the native contacts application so users can see who’s calling again, but it’s still a manual step the end user has to do. This has everything to do with the fact that contacts are now in a “isolated/secured app container” and not accessible by other non-managed / secured applications. After companies apply Mobile Application Management (MAM) / App Protection Policies to their employees’ mobile devices, and forced them to use the Managed Outlook app instead of the native mail application, one of the most frequently asked questions are “how can I see who’s calling me?” and “where are my contacts? I don’t see them in my native contacts app”.

Are my contacts on outlook private