msftuser1
Microsoft Employee
5 months agoStatus:
New
Include TenantID when Managed Private Endpoint request is send from Fabric to other azure resources
Currently when a user create a managed private endpoint from a Fabric workspace to another azure resource, only the workspace name is included in the name. As Fabric can send MPE requests to any tenant, it would be ideal to include the Fabric Tenant Information as well along with workspace ID. This would help the target resource to make sure the request came in from one of their tenants during the MPE approval process.
No CommentsBe the first to comment
Recent ideas
Let Workspace Admins manage Fabric Policies
For example, allow a Workspace Admin to grant other identities the Contributor role, while also granting them higher privileges in certain areas, e.g. List Workspace role permissions (without resha...frithjof_v7 hours agoCommunity ChampionNew35Views0likes2CommentsEnforcing Fabric Items naming standard policy
A standardized naming framework through centralized management for Fabric items similar to one in SQL Server Policy Based Management that enforces naming standards and naming conventions compliance d...ayamas8 hours agoRegular VisitorNew104Views0likes1CommentRun OnDemand Fabric Data Pipeline with Runtime Parameters using REST API
Currently, Microsoft Fabric Data Pipelines can be triggered on demand, but there is no native capability to pass runtime parameter values when initiating a pipeline execution through REST APIs. This ...singhs810 hours agoNew MemberNew41Views2likes2CommentsAPI support for bulk migration from PBIR-Legacy to PBIR
Provide a supported API or automated method to bulk-convert Power BI reports from PBIR-Legacy to PBIR. The conversion should preserve existing report IDs, workspaces, semantic-model connections, and...v-dugumarrir110 hours agoMicrosoft EmployeeNew25Views8likes0Comments