[GH-ISSUE #4461] [Bug]: #2043

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

Originally created by @gh-van-hulten-com on GitHub (Jul 23, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4461

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

I am noticing an issue where deploying a policy template through the "Standards template"-feature does not give me the option to enter or fill the variables used in the policy.

For example, I see this behaviour with the "Win - OIB - SC - Microsoft OneDrive - D - Configuration - v3.2" template

Deploying through the "Apply" policy feature allows you to enter the variable:

Image

Where deploying the policy through the "Standards Template" does not allow you to enter variables (something I don't expect since this policy should be slightly different for every tenant.

Image

I expect the %OrganisationId% in the policy to be dynamically updated with the organization's tenant-id but applying the policy does not replace any variables resulting in incorrect policies:

Image

Environment Type

Non-sponsored user

Front End Version

8.2.1

Back End Version

8.2.2

Relevant Logs / Stack Trace


Originally created by @gh-van-hulten-com on GitHub (Jul 23, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4461 ### 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 I am noticing an issue where deploying a policy template through the "Standards template"-feature does not give me the option to enter or fill the variables used in the policy. For example, I see this behaviour with the "Win - OIB - SC - Microsoft OneDrive - D - Configuration - v3.2" template Deploying through the "Apply" policy feature allows you to enter the variable: <img width="1222" height="607" alt="Image" src="https://github.com/user-attachments/assets/8bafb9bd-928f-42a9-95c9-a6ff4763d7f0" /> Where deploying the policy through the "Standards Template" does not allow you to enter variables (something I don't expect since this policy should be slightly different for every tenant. <img width="682" height="509" alt="Image" src="https://github.com/user-attachments/assets/551d78ac-5208-4bb2-8348-6d91b9886e0c" /> I expect the %OrganisationId% in the policy to be dynamically updated with the organization's tenant-id but applying the policy does not replace any variables resulting in incorrect policies: <img width="1109" height="294" alt="Image" src="https://github.com/user-attachments/assets/f6fe635c-c5d2-485f-8893-b460a83905cb" /> ### Environment Type Non-sponsored user ### Front End Version 8.2.1 ### Back End Version 8.2.2 ### Relevant Logs / Stack Trace ```plaintext ```
Author
Owner

@github-actions[bot] commented on GitHub (Jul 23, 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!

<!-- gh-comment-id:3106894783 --> @github-actions[bot] commented on GitHub (Jul 23, 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!
Author
Owner

@KelvinTegelaar commented on GitHub (Jul 23, 2025):

!support

<!-- gh-comment-id:3106896483 --> @KelvinTegelaar commented on GitHub (Jul 23, 2025): !support
Author
Owner

@github-actions[bot] commented on GitHub (Jul 23, 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

<!-- gh-comment-id:3106896835 --> @github-actions[bot] commented on GitHub (Jul 23, 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**
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#2043
No description provided.