Ross Smith IV To clarify, it is not viable for us to allow un-managed contacts via the Outlook App contact export (option 1). To even get this to work you need to have an iCloud account enabled, so immediately you are in a data loss position, even if limiting the data fields that can be exported.
The fallback is then the EAS profile as described in your article, which has two issues. Firstly, it would be preferable (for us) on Corporate Owned devices to apply the MDM 'Account Restriction' with a block setting. This has the effect of locking out the EAS account under iOS Settings - when the configuration is deployed the user cannot enter credentials. The only way around this is using SCEP for authentication as far as I can see which is a lot of overhead unless there is a requirement elsewhere. The 2nd issue is one of usability - the user has to enter credentials twice upon password resets / token expiry etc.
So, if Caller-ID were available using Apple CallKit capability through the Outlook App, it would require much less management and a deliver a better user experience as we would have less concerns about opening up the rest of the devices for personal usage. In my opinion! 