mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #4623] [Feature Request]: Ability to Delete SharePoint Sites #2136
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#2136
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 @HappyEarthDay on GitHub (Sep 10, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4623
Originally assigned to: @Zacgoose on GitHub.
Please confirm:
Problem Statement
Currently, engineers must log in to the SharePoint GDAP portal to delete old or unused SharePoint sites. This creates inefficiency, adds extra steps, and forces them to leave the CIPP platform. Having the ability to delete SharePoint sites directly in CIPP would streamline tenant cleanup and reduce reliance on external portals.
Benefits for MSPs
Value or Importance
This feature is valuable because tenant hygiene is critical for security, performance, and compliance. Old SharePoint sites often contain stale or sensitive data that should be removed to reduce risk. While not strictly critical, the ability to delete sites directly within CIPP makes the platform more complete and keeps all management tasks in one place. This adds notable value for MSPs managing multiple tenants at scale.
PowerShell Commands (Optional)
No response
@Zacgoose commented on GitHub (Sep 13, 2025):
I would like to work on this please
@Zacgoose commented on GitHub (Sep 13, 2025):
I would like to work on this please!
@github-actions[bot] commented on GitHub (Sep 13, 2025):
Great! I assigned you (@Zacgoose) to the issue. Have fun working on it!
@KelvinTegelaar commented on GitHub (Sep 14, 2025):
added in dev