Allow Workspace Identities as an authentication method for Fabric SQL Databases
Currently the only method of authentication in Fabric pipeline connections to Fabric SQL databases is using OAUTH2, meaning that the credentials of a specific user need to be used (with all the attendant issues around user/credential expiry). By allowing the option of workspace identity for authentication, no user creds would be needed. Obviously correct access controls would need to be defined, but that's standard SQL Server maintenance.
Notify Subscription Owners About Invalid Email Recipients in Power BI
Power BI should automatically notify subscription owners whenever one or more recipient email addresses are invalid or undeliverable. Currently, report subscriptions may silently fail for specific recipients without providing clear feedback to the person who created and manages the subscription. A notification should identify which email addresses could not receive the subscription and explain the reason, such as an invalid address, deleted user account, or external recipient restriction. This would allow subscription owners to quickly update the recipient list instead of assuming that reports are being delivered successfully. Providing proactive notifications for failed deliveries would improve reliability, reduce support requests, and ensure that important reports reach their intended audience. It would also enhance the overall user experience by making subscription management more transparent and easier to maintain.
Workday HR
I would love to have the ability to do reporting against Workday. We leverage it as our global HR platform. It has some really good reporting but it would be nice to have the ability but it would be great to be able to share reporting with SharePoint and Power BI so that we can surface non sensitive data up in dashboards.Unable to Create a Warehouse Connection Without an Existing Warehouse in a New Fabric Tenant
We encountered this issue while attempting to create a Warehouse connection in a newly provisioned, clean Fabric tenant. As a workaround, we created a temporary (dummy) Warehouse within a workspace. Only after the Warehouse existed were we able to successfully create the Warehouse connection. Notably, the Warehouse connection itself does not appear to contain any direct reference to a specific Warehouse. Despite this, the platform requires at least one Warehouse to exist in the tenant before a Warehouse connection can be created. This behavior differs from that of a Lakehouse connection, which can be created successfully in a clean tenant without any existing Lakehouse resources. The difference in behavior between Warehouse and Lakehouse connections appears inconsistent and unexpected. More importantly, this behavior introduces challenges for continuous deployment scenarios. To deploy a Warehouse and other Fabric objects which depend on Warehouse into a workspace in a clean Fabric tenant, a Warehouse connection must first be present. However, creating the Warehouse connection requires an existing Warehouse, resulting in a circular dependency. As a result, the deployment process requires the following workaround: Create a temporary (dummy) Warehouse in a dummy workspace. Create the required Warehouse connection. Delete the temporary Warehouse and workspace. Deploy the actual Warehouse, notebooks, pipelines, and other dependent artifacts. This additional setup is unnecessary and complicates automated deployment processes. We recommend removing this dependency so that a Warehouse connection can be created independently of any existing Warehouse resources, similar to the current behavior of Lakehouse connections. This would eliminate the circular dependency, improve consistency across connection types, and better support continuous deployment and infrastructure automation scenarios.
Can we support Workspace ID authentication when using a gateway connection?
Currently, Workspace ID authentication is only available for cloud connections. We would like to request support for Workspace ID authentication when using gateway connections as well. <document :Authenticate with workspace identity> ---- ・You can create connections with workspace-identity-based authentication in the Manage Gateways and Connections experience for a cloud connection. ・Workspace-Identity-based authentication is currently not supported for gateway connections. ----Export datasets from Microsoft Data Connect App to Fabric Lakehouse correctly
Data from the Microsoft Data Connect App can be extracted using the Microsoft365 connector. Only the Microsoft365 connector can be used in Fabric data pipeline copy activity. But then a lakehouse Table can only be selected as source. Lakehouse Files can not be selected as source. A Fabric notebook can't be used in combination with the Microsoft365 connector. When trying to export datasets from Microsoft Data Connect App to a Fabric Lakehouse (using Fabric data pipeline + copy activity), not all columns are correctly filled with data. Especially date columns and some text columns (when there are emtpy values) are not correctly exported (all NULL values). Certainly in these datasets the errors occur: BasicDataSet_v0.OneDriveSyncHealth_v0, BasicDataSet_v0.OneDriveSyncHealth_v1, BasicDataSet_v0.OneDriveSyncErrors_v0, BasicDataSet_v0.OneDriveSyncErrors_v1 Fixing these export issues improves the adoption of Microsoft Data Connect App with Fabric
