mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #1482] [Feature Request]: Add the ability to choose security groups to pages that allow for All users/All devices choices #813
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#813
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 @LoldenCode on GitHub (Apr 13, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1482
Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole.
We have ran into the case of wanting to address specific pilot groups when deploying MDM policies, such as Application Deployment or Microsoft Defender for Enterprise deployments. At the time of writing, the choices that exist are "None", "All users", "All devices", or "All users and devices". Because we are lazy sysadmins (let's be honest, who isn't) who are aiming to keep our techs working out of a single portal instead of diving into Azure after building the policy, my org is hoping that we can have groups queried and/or cached at the time of page load.
PowerShell commands you would normally use to achieve above request
No response
@github-actions[bot] commented on GitHub (Apr 13, 2023):
Thank you for creating a feature request!
Your current priority is set to "No Priority". No Priority Feature requests automatically get closed in two days if a contributor does not accept the FR.
If you are a sponsor you can request an upgrade of priority. To upgrade the priority type "I would like to upgrade the priority".
If you want this feature to be integrated you can always do this yourself by checking out our contributions guide at https://cipp.app/docs/dev/. Contributors to the CIPP project reserve the right to close feature requests at will.
If you'd like this feature request to be assigned to you, please comment "I would like to work on this please!".
@github-actions[bot] commented on GitHub (Apr 23, 2023):
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://cipp.app/GettingStarted/Contributions/ . Please notify the team if you are working on this yourself.
@github-actions[bot] commented on GitHub (May 8, 2023):
This issue was closed because it has been stalled for 14 days with no activity.