kbutti
1 year agoMicrosoft Employee
Status:
New
Workspaces cannot be associated to multiple Deployment pipelines
Currently we cannot associate one workspace to multiple deployment pipelines. If We have two workspaces with different sets of code and want to deploy to one Workspace that holds all code. It is not possible to create two deployment pipelines and deploy code from two workspaces into one. Use case: We have architecture where common/orchestration code sites in one workspace and deploy the code to any team's workspaces that want to utilize our orchestration code. With current product limitation, we cannot have multiple deployment pipelines created for each team and have common code workspace assigned to each pipeline.
1 Comment
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
Programmatic point-of-failure recovery for Fabric pipelines
The Fabric monitoring UI already supports Rerun → rerun from failed activity. That capability is only reachable by a human clicking in the portal. Please make point-of-failure recovery available to a...EversonElias5 hours agoRegular VisitorNew7Views1like0CommentsEnable Managed Private Endpoints Support for Microsoft Fabric Capacities Below F64
Managed Private Endpoints in Microsoft Fabric are currently supported only on F64 and higher capacities. Customers using lower capacities, such as F8, cannot establish private connectivity to Azure s...v-tsindhu6 hours agoMicrosoft EmployeeNew8Views0likes0CommentsAccessibility bug: Notebook cell text becomes invisible under Windows 11 High Contrast mode
Any text written inside a Fabric notebook is invisible when Wndows High contrast mode is enables. This applies to cell text only (not the UI). In addition, auto-complete windows are not respecting t...abigb8 hours agoNew MemberNew3Views0likes0Comments