Adobe Reader iOS app with Intune MAM-WE policy issue "This seems to be taking longer than usual"

We're having the same problem. Is there are chance that this was resolved? basically we just want PDF files stored in Onedrive>Adobe Acrobat and not deep integration of OneDrive>Adobe Acrobat. Looks like Intune MAM policies are not deployed in Adobe Acrobat app, toggle for Intune App Protection is disabled, if you try to enable it asks for consent however we don't want to give these consent due to security controls and privacy. is there a way to enable this pdf opening from OneDrive without giving much consent to Adobe App in Enterprise App?

I've closely followed this thread and would like to update with some information I discovered.  I have this working temporarily but seems to break after adobe updates its app (about once a month).  I have found that it will then start the loop of protecting the app .  In order for me to get it working again.  i close the app then I delete the app from my ipad.  (note that if you do not delete it first it will not work) next I reinstall it from the intune company portal.  Once I do this app opens as normal and i try and access one drive.  It prompts for credetial and pops up authenticator app on ipad which i then choose the microsoft account.  At this point it restarts adobe app and I have to go throught the process again and the app protection policy applies and i am good for another month or so depending on update frequency.   

Hope this serves as a temp fix for you all and can give Microsoft or Adobe insight to the overall problem.

We have the same issue, being unable to use Adobe Reader on 20.000 devices.

Calling Adobe Reader mobile app Intune compatible hardly seems realistic when requiring data exemption setup, device registration, XML configuration, enrolling the app and possibly exclude it from a range of CA policies. Maybe if the app wasn't free, this issue would have been resolved in the first year or two. But we're still waiting!

After doing a lot more testing and looking at EntraID sign in logs, I think that an important distinction to make here is the way that we associate the "work account" with Adobe Reader that I think is likely the cause of this.

When signing into the app, we sign in with an Adobe account.

Even though that account is using my corporate email address (and uses SSO, meaning it prompts for MFA), this is still an Adobe account and not a "work" account that is linked to the App, and so our App Protection policy does not kick in by simply logging into the application.

It is when trying to link OneDrive for Business to the app where we are running into the issue.

This is because it isn't until that time (as soon as we log in to OneDrive for Businss) the "work" account is linked to the application.

But the application itself is still not signed into using the "work" account and so the App Protection Policy is getting confused (making assumptions here).

If the above is true, then I think this will result in Adobe Reader not being able to work with Microsoft App Protection policies at all, unless Adobe makes the application itself an SSO app.

Hi @Ed Collins,

Hope you are doing well. Sorry for your experience with Acrobat Reader Mobile.

Have you checked the steps and workflow to deploy Reader Mobile using Intune: Intune Deployments — Acrobat Mobile App Deployment

If you have followed the steps, please share a few pieces of information for better investigation:

1. The app version of Acrobat Reader Mobile you are trying to deploy;

2. The OS [Android/iOS] nad its version;

3. A screen recording of the issue you experience.

Look forward to hearing from you.

-Souvik