mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #3908] [Feature Request]: JIT Admin templates #1749
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#1749
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 @TargetCrafter on GitHub (Apr 2, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3908
Originally assigned to: @Zacgoose on GitHub.
Please confirm:
Problem Statement
When i create a JIT admin, i want to include and exclude this from certain CA policies by default. I know what UPN etc to use for the dynamics groups, but my colleagues not necessarily.
Benefits for MSPs
Create JIT admin's that can be excluded and included in CA policies using dynamic groups automatically.
Value or Importance
This is very important to increase the security of JIT Admins.
PowerShell Commands (Optional)
No response
@github-actions[bot] commented on GitHub (Apr 12, 2025):
This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.
@github-actions[bot] commented on GitHub (Apr 20, 2025):
This issue was closed because it has been stalled for 14 days with no activity.
@github-actions[bot] commented on GitHub (Apr 26, 2025):
This issue was closed because it has been stalled for 14 days with no activity.
@TargetCrafter commented on GitHub (Sep 30, 2025):
Any update on the progress of this?
@m365mgmtprd commented on GitHub (Oct 2, 2025):
We’re also very interested in seeing this feature added.
@github-actions[bot] commented on GitHub (Oct 12, 2025):
This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.
@github-actions[bot] commented on GitHub (Oct 18, 2025):
This issue was closed because it has been stalled for 14 days with no activity.
@redanthrax commented on GitHub (Oct 20, 2025):
@github-actions[bot] commented on GitHub (Oct 30, 2025):
This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.
@github-actions[bot] commented on GitHub (Nov 5, 2025):
This issue was closed because it has been stalled for 14 days with no activity.
@mruiterhype commented on GitHub (Nov 25, 2025):
It’d be great if we could also add a max timeframe option to JIT admin templates, so users can’t set durations beyond that limit. https://github.com/KelvinTegelaar/CIPP/issues/4854
@Zacgoose commented on GitHub (Dec 15, 2025):
I would like to work on this please!
@github-actions[bot] commented on GitHub (Dec 15, 2025):
Great! I assigned you (@Zacgoose) to the issue. Have fun working on it!
@Zacgoose commented on GitHub (Jan 13, 2026):
I will also be addressing https://github.com/KelvinTegelaar/CIPP/issues/4854 at the same time