What does HRESULT 0x80550002 (EAS_E_POLICY_COMPLIANT_WITH_ACTIONS) mean?

EAS_E_POLICY_COMPLIANT_WITH_ACTIONS

EAS_E_POLICY_COMPLIANT_WITH_ACTIONS — 0x80550002

This code places the first failure in EAS compliance requiring user action. Operationally, Windows can meet the requested policy, but one or more explicit user/system actions are still required before the device becomes compliant.

Meaning in the subsystem

This differs from an unenforceable policy: the platform has a path to compliance, but it is not yet complete.

Minimum useful evidence

• Per-policy EasComplianceResults values and the exact pending actions
• Account types affected, current password/sign-in/encryption state, and policy source
• Whether ApplyAsync can initiate the change or only inform the user
• Time when policy was evaluated versus when the user completed action

Isolate the responsible condition

• Call CheckCompliance before and after the documented action.
• Apply one policy at a time in a lab account to identify the action owner.
• Verify the final state after sign-out/restart where the policy requires it.

Avoid the common misdiagnosis

Read the comparison results in this order:

Regression proof

Apply the smallest change that addresses the first rejected condition: Present the precise required action, preserve account recovery access, and re-evaluate rather than assuming the action succeeded.

Close the incident only when all per-policy results become compliant after the action and regress to the expected state when the control condition is restored.

Technical references

Use these sources for the formal contract, then combine them with evidence from the returning application or service for this condition:

• Microsoft Open Specifications: HRESULT values.
• Microsoft: Exchange ActiveSync Policy Engine overview.
• Microsoft: EasClientSecurityPolicy.
• Microsoft: CheckCompliance.