starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 08:16:01 +03:00

[GH-ISSUE #2920] [Feature Request]: Deploy 'Enable MFA Allow' by Group #1447

New issue

Closed

opened 2026-03-02 13:44:15 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 13:44:15 +03:00

Owner

Originally created by @mcabreralvl2 on GitHub (Oct 4, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2920

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.

Deploy 'Enable MFA Allow' by Group

Currently, administrators can only apply "Enable MFA Allow" settings broadly across the tenant. There is a need for more granular control to apply these settings by group, which allows for targeted security enforcement and gradual rollout within an organization.

Add functionality within CIPP to enable "Enable MFA Allow" based on specific groups rather than at the tenant-wide level. This would provide flexibility to administrators to apply MFA policies in stages or to specific subsets of users, such as high-security roles, departments, or pilot groups.

Manual application of MFA settings through Azure AD per group, which is time-consuming and does not benefit from the streamlined automation and management that CIPP offers.

The ability to apply MFA policies by group within CIPP will improve security management and allow for better customization of user access policies based on organizational needs. It can also help MSPs better align with client security policies and requirements.

PowerShell commands you would normally use to achieve above request

No response

Originally created by @mcabreralvl2 on GitHub (Oct 4, 2024). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2920 ### 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. Deploy 'Enable MFA Allow' by Group Currently, administrators can only apply "Enable MFA Allow" settings broadly across the tenant. There is a need for more granular control to apply these settings by group, which allows for targeted security enforcement and gradual rollout within an organization. Add functionality within CIPP to enable "Enable MFA Allow" based on specific groups rather than at the tenant-wide level. This would provide flexibility to administrators to apply MFA policies in stages or to specific subsets of users, such as high-security roles, departments, or pilot groups. Manual application of MFA settings through Azure AD per group, which is time-consuming and does not benefit from the streamlined automation and management that CIPP offers. The ability to apply MFA policies by group within CIPP will improve security management and allow for better customization of user access policies based on organizational needs. It can also help MSPs better align with client security policies and requirements. ### PowerShell commands you would normally use to achieve above request _No response_

kerem

2026-03-02 13:44:15 +03:00

closed this issue
added the
enhancement

no-priority
labels

kerem commented

2026-03-02 13:44:17 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Oct 4, 2024):

Only sponsors are allowed to create feature request, and even then this would not be a feature request we entertain; MSPs would use this to decrease the security of tenants, not improve. All your users require MFA, no exceptions.

@KelvinTegelaar commented on GitHub (Oct 4, 2024): Only sponsors are allowed to create feature request, and even then this would not be a feature request we entertain; MSPs would use this to decrease the security of tenants, not improve. All your users require MFA, no exceptions.

kerem commented

2026-03-02 13:44:17 +03:00

Author

Owner

@JudgeDreddKLC commented on GitHub (Oct 5, 2024):

@KelvinTegelaar Manny works for RYC, please re-open. Thanks.

@JudgeDreddKLC commented on GitHub (Oct 5, 2024): @KelvinTegelaar Manny works for RYC, please re-open. Thanks.

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#1447

No description provided.

Rows
Columns