You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to try out this resource I created one manually through Intune admin portal, I then was able to export it (see blueprint below) and then tried to update the policy through M365DSC by changing samplesharing and the name of the policy itself which actually worked.
What doesn't work is actually creating new ones, this is because the blueprint contains Assignments, as soon as I tried to create a new policy it fails with "[]: The request is invalid" and event viewer log points exactly to the problem being caused by updating Assignments, this is most likely also caused by Graph API having changed how to make assignments in the policies as mentioned by @William-Francillette in #3892. At the moment I cannot verify this is the case so I'm raising a new issue, if it's caused by the same problem then this can be closed as duplicate but please mention that in the parent issue that IntuneEndpointDetectionAndResponsePolicyWindows10 doesn't work also.
Error updating data:
{ Response status code does not indicate success: BadRequest (Bad Request). } \ at Update-DeviceConfigurationPolicyAssignment, C:\Program Files\WindowsPowerShell\Modules\Microsoft365DSC\1.23.1108.3\modules\M365DSCDRGUtil.psm1: line 1164
\ at Set-TargetResource, C:\Program Files\WindowsPowerShell\Modules\Microsoft365DSC\1.23.1108.3\DscResources\MSFT_IntuneEndpointDetectionAndResponsePolicyWindows10\MSFT_IntuneEndpointDetectionAndResponsePolicyWindows10.psm1: line 305
Removing Assignments from the blueprint doesn't help, in that case it fails with the following:
Cannot bind argument to parameter 'ComplexObject' because it is null.
+ CategoryInfo : InvalidData: (:) [], CimException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Convert-M365DSCDRGComplexTypeToHashtable+ PSComputerName : localhost
@William-Francillette Hi, this one seems to be related to #3892 and #3921, but at least on this one it looks like it fails to create the policy even if I remove the Assignments property from the blueprint or directly from the MOF and it still fails at Update-DeviceConfigurationPolicyAssignment. Should I close this issue and report it under #3921 ?
Error updating data:
{ Response status code does not indicate success: BadRequest (Bad Request). } \ at Update-DeviceConfigurationPolicyAssignment, C:\Program Files\WindowsPowerShell\Modules\Microsoft365DSC\1.23.1122.1\modules\M365DSCDRGUtil.psm1: line 1164
\ at Set-TargetResource, C:\Program Files\WindowsPowerShell\Modules\Microsoft365DSC\1.23.1122.1\DscResources\MSFT_IntuneEndpointDetectionAndResponsePolicyWindows10\MSFT_IntuneEndpointDetectionAndResponsePolicyWindows10.psm1: line 305
Description of the issue
In order to try out this resource I created one manually through Intune admin portal, I then was able to export it (see blueprint below) and then tried to update the policy through M365DSC by changing samplesharing and the name of the policy itself which actually worked.
What doesn't work is actually creating new ones, this is because the blueprint contains Assignments, as soon as I tried to create a new policy it fails with "[]: The request is invalid" and event viewer log points exactly to the problem being caused by updating Assignments, this is most likely also caused by Graph API having changed how to make assignments in the policies as mentioned by @William-Francillette in #3892. At the moment I cannot verify this is the case so I'm raising a new issue, if it's caused by the same problem then this can be closed as duplicate but please mention that in the parent issue that IntuneEndpointDetectionAndResponsePolicyWindows10 doesn't work also.
Removing Assignments from the blueprint doesn't help, in that case it fails with the following:
Microsoft 365 DSC Version
1.23.1108.3
Which workloads are affected
other
The DSC configuration
Verbose logs showing the problem
No response
Environment Information + PowerShell Version
No response
The text was updated successfully, but these errors were encountered: