mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #3839] [Feature Request]: Standards to Add #1711
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#1711
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 @konstantinrudi on GitHub (Mar 23, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3839
Originally assigned to: @Zacgoose on GitHub.
Please confirm:
Problem Statement
Dear Team,
we would love to have this settings added to the standards:
Azure AD (EntraID):
Users -> Settings:
-> There is already a lot of the other settings from the Page (Disable M365 Tenant creation by users and Disable App creation by users). This is just missing currently.
Benefits for MSPs
Value or Importance
PowerShell Commands (Optional)
No response
@konstantinrudi commented on GitHub (Mar 23, 2025):
The exact wording of the setting is this:
"Restrict access to Microsoft Entra admin center"
@Zacgoose commented on GitHub (Mar 24, 2025):
that would be nice :)
@github-actions[bot] commented on GitHub (Mar 24, 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 ensures 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 slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP.
While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "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
@konstantinrudi commented on GitHub (Mar 24, 2025):
@KelvinTegelaar did you implement it :)?
@KelvinTegelaar commented on GitHub (Mar 24, 2025):
Please read the message the bot posted. It seems like you're not a sponsor and as such you cant make feature requests.
@konstantinrudi commented on GitHub (Mar 24, 2025):
@KelvinTegelaar
Yes we are!
Transaction ID: ch_3R441wEQsq43iHhX1b22oDSZ
Date: 18 Mar 2025 10:34AM PDT
Im just using the my account not our company one :)
@konstantinrudi commented on GitHub (Mar 26, 2025):
Please re open issue @KelvinTegelaar :)
@Zacgoose commented on GitHub (May 6, 2025):
I would like to work on this please!
@github-actions[bot] commented on GitHub (May 6, 2025):
Great! I assigned you (@Zacgoose) to the issue. Have fun working on it!
@kris6673 commented on GitHub (May 12, 2025):
IIRC this is still hidden behind an internal MS API that we cant access through Graph
@Zacgoose commented on GitHub (May 14, 2025):
correct, this is not possible to do from what I can see in the docs, come back to this in 6 months ™
@KelvinTegelaar commented on GitHub (May 15, 2025):
Closed for now, with sadness.