As a large enterprise managing thousands of Power BI gateway connections across multiple clusters, we frequently encounter a significant operational challenge due to the current 1,000 connection limit per cluster. This limitation necessitates the manual recreation of data sources and rebinding of datasets when exceeding capacity, leading to a time-consuming and error-prone administrative process.
We request a feature that enables Power BI administrators to seamlessly reassign existing data sources between gateway clusters. This functionality should be accessible via a user-friendly dropdown or bulk operation within the Power BI Service or Admin Center, eliminating the need to recreate connections from scratch on a new cluster.
1 Comment
luke-novacekHelper I
Voted - today the only way out of a full cluster is recreating connections on another one and rebinding everything.
Until this ships, the other lever is making room: Fabric's connection recency (preview) records when each connection's credentials were last used. GatewayLens, a free, open-source console I built, turns that into a list per cluster of what has not been used for 120 days, with the owners to ask, before anything is deleted - and it writes a backup before any delete. GatewayLens on GitHub
