Outlook for iOS + Caller Identification

Regular Contributor

Hey folks,

 

i'm struggling at this for years, as you can see in my previus post from 2020.

Let me shorten this:

 

Scenario

  • We have iOS Devices with Outlook for iOS installed.
  • The users have many contacts in their EXO Mailboxes
  • When a user gets a call from one of his contacts, the phone number is presented instead of the name (no Caller identification)

Approaches

  • I already know this MS articles belonging to Contact Sync.
    • So i've learned that this leads to a running contact sync without the need of an icloud Account. The contacts could be written directly between Outlook for iOS and the native contacts app. (Better than nothing :xd: )
  • The Problem is, that if contact sync is in use ANY App could see these contacts. (Including Whatsapp, etc...)
  • Because of GDPR this is a no-brainer.
  • Many other solutions are using Apple Call-Kit, so that the incoming call is identified (name is shown) just without any need of contacts to be present in the native contact app.


I didn't found anything belonging Call-Kit or any other possible solution for this issue, yet.

 

There MUST be any better solutions except syncronizing all the contacts, isn't it?

ANY Answer is highly appreciated. (At least the positive ones :xd:)

 

Regards,

Patrick!

4 Replies

@Ross Smith IV 

I've seen that you posted in a comment in 2019 that there is no current plan to support CallKit.

There were many other threads back in the days where users were talking about caller identification. (example). I've already read the whole posts and comments on this. :sad:

Any ideas, how european customers can handle this properly?

Hi @PatrickF11 

 

Confirming your findings!

As you/articles explained this is a limitation, it cannot be done without dual syncing.

 

You have only way to achieve a workaround to the issue which creating a native app profile and then sync contacts only. (Exchange ActiveSync). 

Moe

 

@Moe_Kinani Thanks for your thoughts.

This approach is not acceptable, because we're using Conditonal Access Rules only allowing Exchange via Outlook (only via app protected apps). But we deliberately don't want to change that. :xd:

 

Are there any, more positive, solutions for me? :D

Yup, I understand. Most companies use this CA policy!

Moe