search

KelvinTegelaar / CIPP

CIPP is a M365 multitenant management solution
https://cyberdrain.com / https://cipp.app
GNU Affero General Public License v3.0
758 stars 4.42k forks source link

Deploy Intune policy with custom group failed #2541

Closed rootadmin1 closed 3 weeks ago

rootadmin1 commented 3 weeks ago

Description

When we try to deploy a policy to Intune with a the assignment AllDevices it fails with the following error. "Could not assign policy to AllDevices. Policy ID is 7fac75cd-e9ed-4e00-adc4-e48a6812652b. Error: Resource not found for the segment 'deviceConfigurations'."

Also when we are using a custom group we get the same error.

I found this on the internet about the issue.

I had the same issue. Intune support eventually confirmed that the /deviceManagement/deviceConfigurations/{deviceConfigurationId}/microsoft.graph.windowsUpdateForBusinessConfiguration/deviceUpdateStates endpoint won't be supported anymore.

I worked round my issue by using the generic deviceManagement/deviceConfigurations/{deviceConfigurationId}/deviceStatuses endpoint instead. This won't give you the current feature / quality versions of the devices (although that is available elsewhere) but it does return a compliance status for each device.

Environment data

Non-sponsored
5.8.0
5.8.0
true
true
github-actions[bot] commented 3 weeks ago

Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/ If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug."

Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

rootadmin1 commented 3 weeks ago

I confirm that I have checked the documentation thoroughly and believe this to be an actual bug

KelvinTegelaar commented 3 weeks ago

Support issue, not a bug.