[GH-ISSUE #2566] Cannot apply Device Management policies to AllDevices #1297

New issue

Closed

opened 2026-03-02 13:43:04 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 13:43:04 +03:00

Owner

Originally created by @RustyBarrel on GitHub (Jun 19, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2566

Description

When applying policy templates to a tenant, we cannot use the option AllDevices. The following error message is given:
Could not assign policy to AllDevices. Policy ID is b132ebc1-5fa1-4105-8fb4-0c3c209cc035. Error: Resource not found for the segment 'configurationPolicies'.
Successfully added policy for Customerxxx.onmicrosoft.com

Environment data

Non-sponsored instance, I think.
Frontend version 5.8.5
Backend version 5.8.5
Tried Tenant Cache clear: False
Tried Token cache clear: false

Originally created by @RustyBarrel on GitHub (Jun 19, 2024). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2566 ### Description When applying policy templates to a tenant, we cannot use the option AllDevices. The following error message is given: Could not assign policy to AllDevices. Policy ID is b132ebc1-5fa1-4105-8fb4-0c3c209cc035. Error: Resource not found for the segment 'configurationPolicies'. Successfully added policy for Customerxxx.onmicrosoft.com ### Environment data ```PowerShell Non-sponsored instance, I think. Frontend version 5.8.5 Backend version 5.8.5 Tried Tenant Cache clear: False Tried Token cache clear: false ```

kerem

2026-03-02 13:43:04 +03:00

closed this issue
added the
bug

unconfirmed-by-user
labels

kerem commented

2026-03-02 13:43:05 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jun 19, 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!".

@github-actions[bot] commented on GitHub (Jun 19, 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!".

kerem commented

2026-03-02 13:43:05 +03:00

Author

Owner

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

Fixed in dev

@KelvinTegelaar commented on GitHub (Jun 20, 2024): Fixed in dev

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#1297

No description provided.

Rows
Columns