Closed ricmestre closed 2 weeks ago
I patched the resource to send '@odata.type' set to #microsoft.graph.androidDeviceOwnerUserFacingMessage in the CIM instance and I see it being sent in the request but it still fails.
The problem is really with these 3 properties, if I remove them from the request being sent the resource is deployed without issues so not sure exactly what the issue is.
@ricmestre Do you want me to take a look at it?
@FabienTschanz Thank you Fabien, I think I got it, LocalizedMessages must always be sent in those requests even if they're null.
I'll raise a PR with the fix.
Alright 👍
Description of the issue
IntuneDeviceConfigurationPolicyAndroidDeviceOwner can define the properties DetailedHelpText, DeviceOwnerLockScreenMessage or ShortHelpText, which are a CIM instance of type MSFT_MicrosoftGraphandroiddeviceowneruserfacingmessage, but if they are in the configuration then when trying to deploy the policy it fails with Request is invalid.
It looks like the problem is being caused by the CIM instance being sent without the @odata.type which should be set to #microsoft.graph.androidDeviceOwnerUserFacingMessage
Microsoft 365 DSC Version
1.24.1113.1
Which workloads are affected
Intune
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version