starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 16:26:09 +03:00

[GH-ISSUE #3978] [Bug]: Cannot Set Conditional Access Policy on standards on "Do not change State" #1788

New issue

Closed

opened 2026-03-02 13:47:06 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 13:47:06 +03:00

Owner

Originally created by @georgy007chacko on GitHub (Apr 17, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3978

Required confirmations before submitting

I can reproduce this issue on the latest released versions of both CIPP and CIPP-API.
I have searched existing issues (both open and closed) to avoid duplicates.
I am not requesting general support; this is an actual bug report.

Issue Description

Hi Team,
We cannot set Conditional Access Policy on standards on "Do not change State". Even if we set it to do not change state, its turning on the policy on the tenant

Environment Type

Front End Version

7.5.1

Back End Version

7.5.1

Relevant Logs / Stack Trace

Originally created by @georgy007chacko on GitHub (Apr 17, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3978 ### Required confirmations before submitting - [x] **I can reproduce this issue on the latest released versions** of both CIPP and CIPP-API. - [x] **I have searched existing issues** (both open and closed) to avoid duplicates. - [x] I am **not** requesting general support; this is an actual bug report. ### Issue Description Hi Team, We cannot set Conditional Access Policy on standards on "Do not change State". Even if we set it to do not change state, its turning on the policy on the tenant ### Environment Type Sponsored (paying) user ### Front End Version 7.5.1 ### Back End Version 7.5.1 ### Relevant Logs / Stack Trace ```plaintext ```

kerem

2026-03-02 13:47:06 +03:00

closed this issue
added the
bug

unconfirmed-by-user

not-assigned
labels

kerem commented

2026-03-02 13:47:07 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 17, 2025):

Thank you for reporting a potential bug. If you would like to work on this bug, please comment:

I would like to work on this please!

Thank you for helping us maintain the project!

@github-actions[bot] commented on GitHub (Apr 17, 2025): Thank you for reporting a potential bug. If you would like to work on this bug, please comment: > I would like to work on this please! Thank you for helping us maintain the project!

kerem commented

2026-03-02 13:47:07 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Apr 27, 2025):

!support

@KelvinTegelaar commented on GitHub (Apr 27, 2025): !support

kerem commented

2026-03-02 13:47:07 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 27, 2025):

Hello,

Thank you for reaching out! This report has been classified as a support request rather than a bug or feature request. To keep our development process focused, support requests are limited to paying users. This policy allows us to prioritize resources for those actively supporting CIPP, helping us maintain high-quality development and support.

Sponsors can contact our helpdesk directly via email for assistance with any issues or questions. For non-sponsor support, please refer to our documentation and community discussions—many questions have been answered there.

Did you get this notification in error? Reply with a screenshot of your sponsorship payment, and we’ll gladly reopen the request.

Thank you for your understanding,
The CIPP Team

@github-actions[bot] commented on GitHub (Apr 27, 2025): Hello, Thank you for reaching out! This report has been classified as a **support request** rather than a bug or feature request. To keep our development process focused, support requests are limited to paying users. This policy allows us to prioritize resources for those actively supporting CIPP, helping us maintain high-quality development and support. Sponsors can contact our helpdesk directly via email for assistance with any issues or questions. For non-sponsor support, please refer to our documentation and community discussions—many questions have been answered there. **Did you get this notification in error?** Reply with a screenshot of your sponsorship payment, and we’ll gladly reopen the request. _Thank you for your understanding,_ **The CIPP Team**

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

No description provided.

Rows
Columns