starred/CIPP

Fork 0

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

[GH-ISSUE #3235] [Feature Request]: Improve conditional access documentation #1533

New issue

Closed

opened 2026-03-02 13:45:00 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 13:45:00 +03:00

Owner

Originally created by @fortresstelecom on GitHub (Jan 14, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3235

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.

setup/gdap/conditionalaccess.md

Step 3 is not very clear on how to create the conditional access policy correctly

Create a new policy and include the CIPP user. Enforce Azure Multi-factor Authentication for each logon (set sign in frequency under session to every time) and for all cloud applications, do not add any exclusions or trusted locations.

If you have trusted locations under the classic MFA portal you must always remove those.

Suggested steps: (Needs reviewed)

Click "New Policy"
Click "0 users and groups selected", click "Select users and groups", click "Users and groups" checkbox. Type in your CIPP Account name, click it to select and click "Select"
??
Under Session, click "0 controls selected", check "Sign-in frequency" and click the "Every time" radio box and finalize with "Select"
At the bottom of the screen, make sure to change from "Report-only" to "On" and click "Save"

PowerShell commands you would normally use to achieve above request

No response

Originally created by @fortresstelecom on GitHub (Jan 14, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3235 ### 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. setup/gdap/conditionalaccess.md Step 3 is not very clear on how to create the conditional access policy correctly ``` Create a new policy and include the CIPP user. Enforce Azure Multi-factor Authentication for each logon (set sign in frequency under session to every time) and for all cloud applications, do not add any exclusions or trusted locations. If you have trusted locations under the classic MFA portal you must always remove those. ``` Suggested steps: (Needs reviewed) 1. Click "New Policy" 2. Click "0 users and groups selected", click "Select users and groups", click "Users and groups" checkbox. Type in your CIPP Account name, click it to select and click "Select" 3. ?? 4. Under Session, click "0 controls selected", check "Sign-in frequency" and click the "Every time" radio box and finalize with "Select" 5. At the bottom of the screen, make sure to change from "Report-only" to "On" and click "Save" ### PowerShell commands you would normally use to achieve above request _No response_

kerem

2026-03-02 13:45:00 +03:00

closed this issue
added the
enhancement

no-priority
labels

kerem commented

2026-03-02 13:45:01 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Jan 14, 2025):

Hello,

Thank you for your interest in improving CIPP! To keep our development process focused and manageable, feature requests are limited to paying users. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensure we can sustain our development and support.

When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that would slow down updates and stretch resources thin, ultimately impacting the quality and sustainability of CIPP.

While we’ve closed this request, we appreciate your input, and you’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer yourself, feel free to create a PR that includes your feature request or type "I'd like to work on this!" to assign the issue to yourself.

Did you get this notification in error? Reply with a screenshot of your sponsorship payment and we'll reopen the issue.

Thank you for understanding,
The CIPP Team

@KelvinTegelaar commented on GitHub (Jan 14, 2025): Hello, Thank you for your interest in improving CIPP! To keep our development process focused and manageable, feature requests are limited to paying users. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensure we can sustain our development and support. When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that would slow down updates and stretch resources thin, ultimately impacting the quality and sustainability of CIPP. While we’ve closed this request, we appreciate your input, and you’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer yourself, feel free to create a PR that includes your feature request or type "I'd like to work on this!" to assign the issue to yourself. Did you get this notification in error? Reply with a screenshot of your sponsorship payment and we'll reopen the issue. Thank you for understanding, The CIPP Team

kerem referenced this issue

2026-03-02 13:57:38 +03:00

[PR #1533] [MERGED] Added Azure & Sharepoint portals to dashboard #3284

kerem referenced this issue

2026-03-02 13:57:39 +03:00

[PR #1536] [MERGED] Dev to release #3285

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

No description provided.

Rows
Columns