mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #4461] [Bug]: #2043
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#2043
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
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:
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.
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:
Environment Type
Non-sponsored user
Front End Version
8.2.1
Back End Version
8.2.2
Relevant Logs / Stack Trace
@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:
Thank you for helping us maintain the project!
@KelvinTegelaar commented on GitHub (Jul 23, 2025):
!support
@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