mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #3525] [Feature Request]: Add Standard to disable self service purchase for Microsoft 365 Copilot #1587
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#1587
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 @cwilliams3491 on GitHub (Jan 29, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3525
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.
New standard request.
Enabling Copilot without the proper Purview set up can be a security issue. Many MSP's do not have these set up for every client. Being able to control when Copilot is enabled would limit this exposure.
PowerShell commands you would normally use to achieve above request
Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -Productid "CFQ7TTC0MM8R" -Enabled $false
Reference: https://blog.icewolf.ch/archive/2024/09/30/disable-self-service-purchase-for-microsoft-365-copilot/
@KelvinTegelaar commented on GitHub (Jan 29, 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