Parameterize Dataflow Gen2 data source connection
Allow the Dataflow Gen2 data source connection GUID to be parameterized and stored in a Variable Library. This would allow the same Dataflow to use different connections depending on the workspace/environment, without modifying the Dataflow itself. Hypothetical example: Variable Library: SourceConnectionGuid = 01234567-89ab-cdef-0123-456789abcdef The Dataflow references this variable for its data source connection. In another workspace, the same Dataflow could use: Variable Library: SourceConnectionGuid = fedcba98-7654-3210-fedc-ba9876543210 This would make it much easier to use the same Dataflow across personal feature workspaces, test, and production while keeping the appropriate connection for each environment.
Hubspot Connector For Fabric
Having an out of the box connector to Hubspot would be very useful for customers using this CRM as this would encourage them to drop data to Fabric instead of using Hubspot as a data platform. At the moment the only way of extracting data from hubspot is to use a hardcoded token in API Call.
Informix support for Incremental Load
Microsoft Fabric Copy Job connector support matrix for Informix connector supports Full Load operations, but it does not currently support Incremental Load (watermark-based) operations Because Fabric Data Factory Copy Jobs don't yet support incremental/delta copy for IBM Informix, we've had to build a custom pipeline (rather than using a native Delta Copy Job) to approximate delta loads from our Informix/Pronto ERP data. This pipeline-based approach consumes considerably more Capacity Units than a native delta copy job would and may not fit sustainably within our Fabric capacity. If it doesn't, we'll be forced back to daily full copy jobs — a significant regression from the hourly delta refresh our legacy SSIS job was able to achieve. The CU cost of running delta via a pipeline (versus a native Copy Job) means the refresh cadence we can sustain is at risk of dropping from hourly to daily. In practice this means data that previously updated every hour now risks sitting stale for most of the day, with no clear way to restore that cadence without native incremental support for Informix. Requesting to add Informix to support Incremental Load as it is crucial part of the operation sustainability and efficiency.
Allow sharing of Office 365 Email (Outlook) cloud connections in Manage connections and gateways
The Problem When creating an Office 365 Email (Microsoft Outlook) cloud connection in Manage connections and gateways, it is impossible to share the connection with other users or security groups. Attempting to do so via Manage users results in: "Sharing this connection type is prohibited for security reasons." This occurs regardless of the authentication method used: both Organizational account (OAuth 2.0) and Service Principal authentication are blocked from sharing. The tenant admin toggle "Blocking shareable cloud connections" has no effect on this restriction — it is enforced at the connector type level. Why This Is a Problem Teams cannot collaborate on shared pipelines. If a Fabric pipeline uses an Outlook activity to send email notifications, only the connection owner can run it. Other team members must each create their own connection, even when using the same Service Principal credentials. Service Principal connections should be shareable. Unlike OAuth user tokens, a Service Principal has no personal identity to protect. The security justification for blocking sharing does not apply to SP-authenticated connections. There is no documentation. Microsoft does not publish a list of which connector types are blocked from sharing, making it impossible for teams to plan their architecture around this limitation. The error message provides no guidance on alternatives. Unnecessary admin overhead. For teams of 10+ users, manually creating identical connections per person is error-prone and creates a maintenance burden for credential rotation. Proposed Solution Allow sharing of Service Principal-authenticated Office 365 Email connections. There is no security risk: the credentials belong to an app registration, not a user. The admin already controls access via Entra ID and Exchange application access policies. If OAuth connections must remain unshareable, document it clearly. Publish a list of which connector types cannot be shared and why, so teams can make informed architectural decisions. Current Workarounds (All Suboptimal) Workaround Drawback Each user creates their own SP connection with shared credentials Manual setup per user, secret distribution risk, maintenance burden during rotation Use Web activity with Graph API instead of Outlook connector Loses native connector experience, requires custom token management Use Power Automate as intermediary Adds external dependency, additional tooling, latency Impact Any organization using Fabric pipelines with email notifications is affected. This is especially painful for enterprise teams with shared pipelines, automated alerting, and centralized data operations.
Semantic Model 'Make Changes to this Model'
The link or action item to make changes to the importing Semantic Model is to obscure. Nobody looks down in bottom right corner of the Power BI Desktop window unless they want to resize the current view. Please find a better way to present this notification.Improve Connection Discovery and Reuse Across Fabric Experiences
Description: Enhance the Fabric UI experience by displaying all available and accessible connections in a consistent drop-down list across Dataflow Gen2, Notebooks, and other Fabric workloads. This would allow users to easily discover and reuse existing connections instead of recreating them, resulting in a more intuitive and streamlined onboarding experience. Requested Enhancement: Enable Dataflow Gen2 and Notebooks to discover and reuse existing Fabric-managed Snowflake connections that a user owns or has permission to use, similar to the connection reuse experience available in other Fabric workloads. Current Challenges: Dataflow Gen2 - Existing Snowflake connections can only be reused when both the Snowflake server name and warehouse are entered exactly as defined in the connection. - This dependency is not intuitive and prevents users from easily discovering and selecting reusable connections. Notebooks - Snowflake connections are only available if the "Allow code-first artifacts such as Notebooks to access this connection" option was enabled during connection creation. - This setting cannot be modified for existing connections, requiring users to recreate connections solely to enable Notebook access. Benefits: Simplifies connection management and improves user experience. Reduces duplicate connection creation and accelerates onboarding to Fabric.
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.