We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Was running MasterScript-SPE.ps1, running into this error on each Device Compliance Policy
Response content: {"error":{"code":"BadRequest","message":"Invalid OData type specified: \"microsoft.graph.#microsoft.graph.exclusionGroupAssignmentTarget\"","innerError":{"date":"2021-11-19T19:27:57","request-id":"3f0e46b6-a2b4-4863-a0b7-fd46c1c4d0cd","client-request-id":"3f0e46b6-a2b4-4863-a0b7-fd46c1c4d0cd"}}} Add-DeviceCompliancePolicyAssignment : Request to https://graph.microsoft.com/v1.0/deviceManagement/deviceCompliancePolicies/a47b7f6c-4839-499e-a28b-50be9940b832/assign failed with HTTP Status BadRequest Bad Request At C:\users\adelino\downloads\securedworkstation-master\securedworkstation-master\SPE\Import-SPE-DeviceCompliancePolici es.ps1:625 char:13 + Add-DeviceCompliancePolicyAssignment -ComplianceAssignmen ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Add-DeviceCompliancePolicyAssignment
I was able to get it working by
old: "@odata.type": "#microsoft.graph.$Assignment", fixed: "@odata.type": "$Assignment",
The text was updated successfully, but these errors were encountered:
Thanks for the feedback - will work with the team to resolve
Sorry, something went wrong.
No branches or pull requests
Was running MasterScript-SPE.ps1, running into this error on each Device Compliance Policy
I was able to get it working by
old: "@odata.type": "#microsoft.graph.$Assignment",
fixed: "@odata.type": "$Assignment",
The text was updated successfully, but these errors were encountered: