Windows Custom Configuration XML payload fails for AllowCamera CSPSolved

Hey @juan_garcia,

For Windows Custom Configuration, the data type must match what the Microsoft CSP expects for that specific setting. Windows MDM does not accept arbitrary XML for every CSP setting.

For the camera restriction, the AllowCamera policy expects an integer value, not a string, Boolean tag, or XML block such as .

Use the following configuration instead:

• OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Camera/AllowCamera
• Data type: Integer
• Value: 0

The value meanings are:

• 0 – disables the camera
• 1 – enables/allows the camera

If this is configured as a Hexnode Windows Custom Configuration payload, select the Integer data type and enter 0 as the value. Do not upload this particular setting as a String/XML payload.

Best Regards,
Isabel Lora
Hexnode UEM

That explains the warning. I was trying to convert the existing custom configurations into XML and used something like this inside the payload:

<Format>chr<\Format> with <Data><![CDATA[<Enabled/>]]></Data>`

Even when I moved it to a fresh policy, the camera restriction still didn’t apply.

That payload fails because AllowCamera is not a String/XML policy. It expects an integer, so sending a character/string payload makes Windows reject or ignore the configuration.

If you are using SyncML XML directly, the format still needs to be integer-based, for example:

<Format xmlns=”syncml:metinf”>int</Format>

and the data should be:

<Data>0</Data>

However, when deploying through Hexnode Custom Configuration, the simpler and recommended method for this CSP is to create the payload using the built-in data type fields:

• Data type: Integer
• Value: 0

Use the XML upload option only for CSP settings that explicitly require a String/XML payload.

Best Regards,
Isabel Lora
Hexnode UEM