Analysis: Bulk delete functionality for orphaned connection references #10620
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue requests ability to delete orphaned connection references directly from the list view instead of navigating through "Manage Connection" → wait for fetch → delete for each item.
Analysis Deliverable
Comprehensive technical analysis document (
ANALYSIS_ORPHANED_CONNECTION_BULK_DELETE.md) covering:Feasibility: ✅ Confirmed feasible. Existing
HELPER - Delete Connectionflow andadmin_ConnectionReferenceIdentityentity provide required infrastructure.Architecture: Proposes new orchestration flow for bulk operations + Canvas app UI enhancements (multi-select, command bar, progress indicators). Estimated 9-13 hours implementation.
Implementation approach:
HELPER - Bulk Delete Connectionsflow with concurrency controls and granular error handlingRisk mitigation: API rate limiting (concurrency=5), permission validation, partial failure handling, accidental deletion prevention via confirmation.
Consolidation: Issue is part of [CoE Starter Kit - Feature]: FEATURE TITLE Enhancement: Centralized Management for Orphaned Components (Apps, Flows, Connection References) #10319 (Centralized Management for Orphaned Components). Analysis recommends implementing as part of that broader initiative for consistency across Apps/Flows/Connections.
Context
Per issue comments, this request consolidates into #10319. Analysis serves as blueprint for implementation within that larger effort.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.