[GH-ISSUE #2541] Deploy Intune policy with custom group failed #1282

Closed
opened 2026-03-02 13:42:58 +03:00 by kerem · 3 comments
Owner

Originally created by @rootadmin1 on GitHub (Jun 11, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2541

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
Originally created by @rootadmin1 on GitHub (Jun 11, 2024). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2541 ### 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 ```PowerShell Non-sponsored 5.8.0 5.8.0 true true ```
kerem 2026-03-02 13:42:58 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Jun 11, 2024):

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!".

<!-- gh-comment-id:2160360302 --> @github-actions[bot] commented on GitHub (Jun 11, 2024): 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!".
Author
Owner

@rootadmin1 commented on GitHub (Jun 11, 2024):

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

<!-- gh-comment-id:2160363596 --> @rootadmin1 commented on GitHub (Jun 11, 2024): I confirm that I have checked the documentation thoroughly and believe this to be an actual bug
Author
Owner

@KelvinTegelaar commented on GitHub (Jun 11, 2024):

Support issue, not a bug.

<!-- gh-comment-id:2160469756 --> @KelvinTegelaar commented on GitHub (Jun 11, 2024): Support issue, not a bug.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#1282
No description provided.