| Previous | Next |
| E_MBN_SMS_MEMORY_FULL | EAS_E_POLICY_COMPLIANT_WITH_ACTIONS |
EAS_E_POLICY_NOT_MANAGED_BY_OS
EAS_E_POLICY_NOT_MANAGED_BY_OS identifies this condition: the caller asked Windows to evaluate an EAS policy that the operating system does not manage through this policy engine.
Where the failure sits
Unsupported policy ownership is not device noncompliance; Windows is saying this engine cannot decide/enforce that requirement.
Facts to collect first
- Individual EAS property being evaluated and its MS-ASPROV name
- Windows build, account type, and EasClientSecurityPolicy values set by the app
- CheckCompliance result for every policy rather than one aggregate status
- Whether the requirement belongs to Exchange/server, app, MDM, or another authority
Change one variable at a time
- Evaluate only the documented OS-managed policy subset.
- Compare CheckCompliance with the property omitted.
- Test the same server policy through the intended management authority.
Verification after correction
The corrective action should be narrow: Route the requirement to the correct authority or report it as not OS-managed instead of pretending Windows enforced it.
Close the incident only when the app maps each server policy to a documented evaluator and never grants compliance when evaluation is unavailable.
Technical references
Looking for a different code? Search another status or error code.