mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #2029] [Feature Request]: Scan tenants for already enabled standards #1038
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#1038
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 @robm82 on GitHub (Jan 18, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2029
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.
It would be great if there was an option to scan a tenant in the Edit Standards screen to obtain whether some of the standards have already been enabled or configured. In doing this, you then know what the customer or a previous MSP has configured, and you can review what is already in place before overwriting them with the standards that you want to set. I'm not sure how easy this would be to implement, but I think it would need to have a set of PowerShell scripts that gets the status of the configuration and displays it correctly within the CIPP portal.
PowerShell commands you would normally use to achieve above request
No response
@KelvinTegelaar commented on GitHub (Jan 18, 2024):
Thats what the alert report features are for. You set them to report, discover their state using bpa and decide how to continue.