How to Fix Defender for Cloud Apps Blocking Intune-Compliant Devices
Question details
Users are experiencing unexpected download blocks because Defender for Cloud Apps is incorrectly classifying Intune-compliant devices as unmanaged.

- Product
- Microsoft Defender for Cloud Apps, Intune
- Device & OS
- not provided
- Scenario
- Accessing SaaS applications like Salesforce through Conditional Access App Control session policies.
- Observed behavior
- Conditional Access policies block file downloads because fully compliant devices are misidentified as unmanaged due to incomplete identity-provider integration.
Ensure you have administrative access to your Microsoft Defender for Cloud Apps and Microsoft Entra ID portals. You will also need access to your MDM environment to deploy or verify user certificate profiles.
Install the Required Identity Provider Certificate
When using an external identity provider like Okta, deploying the correct certificate to the user profile ensures Defender accurately identifies managed devices.
Defender for Cloud Apps relies on correct identity provider integration to assess device status. If a required certificate is missing in the user profile context, the device appears unmanaged to the session policy, triggering restrictive block actions on downloads.
Navigate to your mobile device management (MDM) solution, such as Microsoft Intune, and initiate the creation of a new Trusted Certificate profile.
Upload the specific root or intermediate certificate provided by your identity provider (e.g., Okta) into the configuration profile.
Configure the deployment settings to install the certificate specifically under the User Profile rather than the system or machine store. Defender for Cloud Apps user-session mapping relies on this exact context.
Push the configuration to the affected endpoints and force a manual device sync to apply the new certificate immediately.
Have the affected user sign out, clear their browser cache, sign back in to the SaaS application (like Salesforce), and attempt a file download to verify the block has been lifted.

Verify Defender and Intune Integration Settings
Ensure that Microsoft Defender for Cloud Apps is properly synced with Microsoft Intune to receive accurate device compliance states.
Need a Lightweight, Secure Office Suite? Try WPS Office
While managing complex enterprise environments and device compliance policies, you might find enterprise licensing overhead overwhelming for basic productivity needs. WPS Office provides a free, lightweight, and highly compatible alternative to Microsoft Office, perfect for teams that need to create and edit documents securely and efficiently.
- 1. Download the installer: Go to the official WPS website and download the free installation package for your operating system.
- 2. Install the software: Run the installer and follow the simple on-screen instructions to complete the setup in minutes.
- 3. Open your documents: Launch WPS Office and directly open your existing Microsoft Office files (.docx, .xlsx, .pptx) with full formatting retention.

Frequently Asked Questions
Why does Defender for Cloud Apps label my fully Intune-compliant device as unmanaged?
This misidentification typically occurs when the device lacks the proper client certificate required by a third-party identity provider (like Okta), or if the synchronization between Microsoft Intune and Defender for Cloud Apps is incomplete or failing.
How do I test if my Conditional Access App Control session policy is evaluating correctly?
Ask a user on a managed device to access the protected application (e.g., Salesforce) and attempt to download a file. Review the Cloud Apps portal logs to see the device tags being passed and verify whether the policy is triggering a block or allow action based on compliance.
Does the identity provider certificate need to be in the machine store or user profile?
For Defender for Cloud Apps to correctly identify user-session mappings with providers like Okta, the certificate generally needs to be deployed and installed in the specific user profile context rather than the system or machine store.




