Preserve the OEMConfig schema context when investigating a changed setting

Source facts

Intune synchronizes the latest OEMConfig app from Google Play and does not retain older app or schema versions. The OEM controls the schema; Intune exposes it without validating or changing the schema itself. Microsoft directs schema errors and version conflicts to the OEM. The OEMConfig app, rather than Intune’s MDM agent, applies the device settings. Microsoft Learn.

Applicability

Use this investigation for Intune-enrolled Android Enterprise devices with a matching supported OEMConfig app. Confirm the particular manufacturer and application before interpreting a setting or contacting its support owner.

DSE recommendation

Capture the app and schema context with each approved configuration change. Retain the configured JSON and the OEM documentation used to interpret it. When behavior changes, compare the device’s actual app version and setting values with that record. Describe the affected property and expected behavior to the OEM instead of assuming Intune holds a previous schema ready for rollback. Keep any proposed app or policy change subject to the device owner’s change process.

Verification

On a representative approved device, inspect the effective property and its per-setting deployment result, then test the actual device behavior. Distinguish a saved profile from a correct OEM-defined value. If a schema or version problem remains, retain the smallest reproducible configuration and the observed app context for escalation. Do not invent an older schema or publish an untested configuration as a supported recovery path.

Official references

Microsoft Learn: Use OEMConfig on Android Enterprise devices in Microsoft Intune.