#Outlook contact groups on ios device android

Likewise, if the user performs any contact management within Outlook for iOS, those changes propagate to the native iOS Contacts app through ActiveSync synchronization. Contacts synchronize back into the userвЂ™s Exchange mailbox via the ActiveSync protocol and synchronize into Outlook for iOS over the Microsoft sync technology.

The user can use the native iOS Contacts app for all contact management, if they desire.

As these changes are driven by IT, end users do not need to take any action other than entering their credentials for the managed EAS profile. With the above changes, Contacts for the userвЂ™s account synchronize into the native iOS Contacts app via the managed EAS profile. For more information on recommended approaches to deploying Outlook general app configuration, see.

Note: A managed apps ACP requires the assigned users to have an App Protection Policy.

#Outlook contact groups on ios device android

Using the general instructions in Deploying Outlook for iOS and Android app configuration settings, configure and deploy an Outlook managed apps App Configuration Policy to your enrolled user base that (at a minimum) disables Save Contacts and prevents the user from enabling the setting: Users will be forced to enter their credentials and the profile changes wonвЂ™t take effect until authentication is complete. Note: Changing an existing EAS profile with these new settings results in a new profile being pushed to the device. This managed EAS profile forces OAuth as the authentication method, only allows Contacts synchronization, and prevents the user from changing what data types are synchronized. Using the general instructions in Add e-mail settings for iOS devices in Microsoft Intune, configure and deploy the below managed EAS profile to your enrolled user base: Once Outlook for iOS contact synchronization is disabled, the duplicates are removed. Note: Due to app configuration delivery timing, some users may experience duplicate contacts in the native iOS Contacts app. For more information, see Managed Exchange ActiveSync Profile improvements introduced in iOS13/iPadOS. This is because the managed EAS profile recommendation utilizes functionality only available in iOS 13+ / iPadOS. However, this approach should not be performed until all user devices are upgraded to iOS 13+ or iPadOS. Deploy an Outlook App Configuration Policy (ACP) that disables Save Contacts.

Deploy a managed Exchange ActiveSync (EAS) profile for contact synchronization.

Organizations can adopt this approach by deploying the following policies: This approach results in two synchronization paths вЂ“ Outlook leverages the native Microsoft sync technology for synchronizing data within Outlook, and ActiveSync is leveraged by iOS to synchronize the contacts. With this contact synchronization model in place, users no longer need to leverage Outlook for iOSвЂ™s contact export synchronization process.

On enrolled devices, users can leverage an Exchange ActiveSync profile that only synchronizes contacts. However, with the Managed Exchange ActiveSync Profile improvements introduced in iOS13/iPadOS, organizations now have an additional capability to configure how users can manage contacts on mobile devices. Unfortunately, these issues are not something that Outlook for iOS can solve as weвЂ™re completely dependent on the operating system to provide a supported mechanism for bi-directional synchronization and for delivering managed contacts.

On enrolled devices, the exported Outlook contacts are considered unmanaged and are accessible to unmanaged, personal apps.

On enrolled devices, in order to leverage OutlookвЂ™s contact export process, several changes to device restrictions are required, as documented in Support Tip: Enabling Outlook iOS Contact Sync with iOS12 MDM Controls.

Contact changes within the native iOS Contacts app donвЂ™t get synchronized back to the appropriate Outlook account, which may lead to data loss when OutlookвЂ™s contact export process is triggered as the exported contacts get overwritten.

The lack of a two-way synchronization mechanism means that users must remember to manage (create, edit, or delete) contacts from within Outlook and not the native iOS Contacts app.

We recognize that there are limitations and/or concerns with our contact export process, such as: This functionality enables Caller-ID, iMessage, and FaceTime integration for usersвЂ™ Outlook contacts. As many of you know, Outlook for iOS supports a one-way contact export process whereby contacts from within Outlook can be exported into the native iOS Contacts app.