Adobe App and Website Not Loading Sign-In on Intune-Managed Devices

Question

Hello Adobe Community,All of our computers are managed in Microsoft Intune. Here’s what we are seeing:A newly enrolled computer that is compliant with policies is not affected.On all other Intune-managed computers, the issue occurs.This problem started about 3 weeks ago.Our Intune policies have not changed since they were created over a year ago.Issue Description:Neither the Adobe app nor the Adobe website ever reach the sign-in step.In the app, an Adobe server error appears right away.On the website, the sign-in page never loads—it only shows the error screen I attached in my support request.This happens before credentials are entered, so it’s not tied to user login.Environment / What I’ve Checked:All affected devices are enrolled and actively managed in Intune.Firewall / Defender for Endpoint policies are applied, but none appear to block Adobe.Conditional Access or compliance policies: none that restrict Adobe services.The issue occurs on multiple devices.Other users don’t have Adobe accounts, but when testing, their devices also fail to reach the sign-in page.All affected devices show as compliant in Intune.No proxy servers or external firewalls are in place that would interfere with Adobe connectivity.What’s Been Done:We have already contacted Microsoft support and Adobe support.No resolution yet. If anyone has experienced a similar Intune-related Adobe sign-in issue—or has ideas on next steps—I’d greatly appreciate your guidance.Thank you.

Tariq Dar · Answer

Hi @fq@xiente,

Thanks for reaching out and for the detailed breakdown — that’s very helpful. From what you’ve described, it looks less like a user credential issue and more like a connectivity or policy enforcement conflict between Intune-managed devices and Adobe’s sign-in services.

A couple of things you could check/test while this is being worked on with Microsoft and Adobe support:

1. Network / Endpoint restrictions

Even though no new Intune policies were applied, Defender for Endpoint or firewall baselines may have silently updated in the past three weeks. To confirm, try temporarily excluding *.adobe.com and Acrobat Web domains. Adobe’s full allowlist of required endpoints is here: Adobe Network Endpoints.

2. Compare new vs. existing Intune devices

Since newly enrolled devices work fine, try running a policy comparison in Intune (Device → Compare policies) to spot subtle differences. Sometimes a previously “grandfathered” device is subject to an older baseline that hasn’t been refreshed.

3. TLS / Certificates

Adobe sign-in requires modern TLS settings. Double-check that older devices haven’t had certificate trust updates blocked by policy. Clearing cached certificates and updating root certs might help.

4. Testing with different channels

If possible, test sign-in via a non-Intune device on the same network. If that works, you’ll know the block is related to Intune/device policy, not your ISP or external firewall.

5. Log collection

On affected devices, gather the Adobe Acrobat/CC Desktop App logs (%localappdata%\Adobe\OOBE\opm_db on Windows) and compare them with logs from a working device. Errors in PDApp.log or DLM.log may show which endpoint is being blocked.

Since you’ve already involved Adobe and Microsoft support, I’d recommend sharing this working vs. non-working device comparison with them — that difference is likely the key.

Best regards,
Tariq | Adobe Community Team

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded