Support API-Based / Non-Interactive Authentication for Salesforce Connectors in Power BI & Fabric
Salesforce supports API-based access through Connected Apps and API-enabled accounts, allowing integrations to authenticate without user interaction. However, the Power BI/Fabric Salesforce connector currently requires interactive UI-based sign-in and MFA tied to an individual user. This creates challenges for enterprise support and deployment processes: Global support teams cannot manage Salesforce-connected reports if authentication is tied to one person's MFA. Report and semantic model promotion between environments can require re-authentication by a specific user. Support and operational processes become dependent on individual employees rather than managed service identities. User absence, role changes, or employee departures can disrupt support activities. Please add support for API-based, non-interactive authentication methods such as Salesforce Connected Apps, OAuth JWT Bearer Flow, Client Credentials Flow, or service principal-style authentication. This would allow organizations to use Salesforce API authentication instead of UI-based authentication and remove the dependency on an individual's MFA credentials.Governance on Preview Features and new GA
In short words, hereby we call for community to vote the crucial enterprise governance and administration towards features with significant cost, performance, security, compliance, or operational impact Persist Feature-Level Governance Controls After GA Tenant-wide "Preview Features Disabled by Default" Governance Mode To make it more clearer for you, please refer below detailed description: As outlined in the Microsoft documentation (Azure Infrastructure Lifecycle FAQ), we fully understand that preview features do not carry SLAs and are not intended for production workloads. Consequently, usually enterprise policy is to restrict user's access to these features until they undergo internal review and approval. To support this governance model, is it feasible to ensure that all preview features released to specific tenant are disabled by default? We have observed that several preview features are automatically enabled upon release. For instance, the tenant setting "Users can share Power BI visuals as Loop components (preview)" was set to "Enabled for the entire organization" by default. Furthermore, we noticed that once a feature reaches General Availability (GA), the dedicated tenant settings previously used to restrict its usage are sometimes removed (e.g., Operation Agent, IQ Plan). This leaves us with no straightforward way to manage these features at the tenant level. Our Recommendation: For features that carry high risks—such as significant cost implications, performance impacts, or compliance concerns—we strongly suggest maintaining tenant-level restriction capabilities, even after GA and ahead of the upcoming Policy Management rollout.Governance on Preview Features and new GA
In short words, hereby we call for community to vote the crucial enterprise governance and administration towards features with significant cost, performance, security, compliance, or operational impact Persist Feature-Level Governance Controls After GA Tenant-wide "Preview Features Disabled by Default" Governance Mode To make it more clearer for you, please refer below detailed description: As outlined in the Microsoft documentation (Azure Infrastructure Lifecycle FAQ), we fully understand that preview features do not carry SLAs and are not intended for production workloads. Consequently, usually enterprise policy is to restrict user's access to these features until they undergo internal review and approval. To support this governance model, is it feasible to ensure that all preview features released to specific tenant are disabled by default? We have observed that several preview features are automatically enabled upon release. For instance, the tenant setting "Users can share Power BI visuals as Loop components (preview)" was set to "Enabled for the entire organization" by default. Furthermore, we noticed that once a feature reaches General Availability (GA), the dedicated tenant settings previously used to restrict its usage are sometimes removed (e.g., Operation Agent, IQ Plan). This leaves us with no straightforward way to manage these features at the tenant level. Our Recommendation: For features that carry high risks—such as significant cost implications, performance impacts, or compliance concerns—we strongly suggest maintaining tenant-level restriction capabilities, even after GA and ahead of the upcoming Policy Management rollout. We look forward to your guidance on this matter.
Allow multi-column conditions /output in Power BI Activator rules (Power BI visual-based alerts)
Description: When I create an Activator alert from a Power BI report visual, the rule can only evaluate the single column or measure it was created from, and the alert can only reference that same value. This blocks common governance and monitoring scenarios. Example scenario: I wanted an alert for Dev workspaces that sit on a billable (Premium/Fabric) capacity. That needs a condition on both Workspace Name (contains “Dev”) and Capacity/Billing type (not blank). Activator can’t combine the two in one rule, so I had to build the alert in Power Automate with a DAX query instead. Limitations: A condition can use only one column or measure, with no AND/OR across several attributes. The alert message or action can include only that same column. I can’t add related details like workspace name, dataset link, or owner. There’s no way to run a DAX query as the rule logic. Requested improvements: Conditions across multiple columns/measures (AND/OR). Selectable output fields, so the Teams or email action can include several columns, and dynamic links. Optionally, the ability to define the trigger with a DAX query, as the Power Automate “Run a query against a dataset” action does. Impact: Without this, governance and monitoring alerts need a separate Power Automate flow, which is harder to build and maintain than a native Activator rule.
New Monitoring Hub
Enjoying the new monitoring hub and the insights it brings. However, I have a few suggestions Display Start Time and Current Duration When clicking on Workspace, take me to the Workspace - like the Legacy Hub Remove the Pagination, we have a very busy capacity that we need to monitor Alerts for any running job that exceeds a time threshold, eg send email to admins where any refresh is taking longer than 60 minutes
Schedule pipeline as Service Principal
It would be beneficial to be able to specify an anonymous sp or user account while creating a schedule to run a pipeline directly in the Fabric GUI. This is currently only possible via the rest api and an external scheduler. Ti would be nioce to have run as sp , enterprise app or user option.
Rule to force only HC Sessions while working with interactive notebooks
As a Fabric Platform Admin, I would like to force users of specific workspaces to only be allowed to spin-up and use High Concurrency (HQ) Sessions while working interactively with notebooks. This can help with best capacity utilization and faster notebook startups.User Interface customization - HomePage & Help and support
Hi, 1st idea: It would be great if administrators could customize the Fabric/Power BI Home page. Today, users can choose between three predefined layouts (Copilot, Simplified, and Expanded). Allowing administrators to create and publish a custom layout for all users, with embedded report pages, visuals, quick-access buttons, and other tailored content, could significantly improve the user experience and adoption of the platform. 2nd idea: It would be great if administrators could customize the Help & Support menu by adding their own entries, renaming existing ones, and changing their order. This would make it easier to promote organization-specific documentation, support contacts, training resources, and other important links directly within the Fabric/Power BI experience.
Org apps - Cannot be arranged in folders and do not stay hidden
Currently, Organizational Apps (Org Apps) are displayed in the standard Apps section of the Get Apps experience, alongside regular workspace apps. For organizations managing large-scale Power BI deployments, this creates navigation and discoverability challenges. **Current Behavior:** Org Apps appear mixed with regular apps in a single list, making it difficult for end-users to distinguish and locate organizational-level content, especially in environments with dozens of apps. **Requested Behavior:** Add the ability to display Organizational Apps in a separate, dedicated section within the Get Apps experience (similar to how Featured and Recommended apps are organized separately). This would: - Improve discoverability for org-level content - Create clear visual separation between user-scoped and organization-scoped apps - Enhance the app navigation experience at scale **Business Impact:** Organizations deploying large numbers of apps (particularly during migrations and multi-tenant rollouts with 100+ apps) would benefit significantly from dedicated Org Apps visibility. This is especially valuable for external-facing platforms serving multiple client organizations, where organizational apps serve as the primary content distribution mechanism. **Suggested Implementation:** Add a new collapsible "Organizational Apps" section in the Get Apps experience that displays all Org Apps separately from regular workspace-published apps. Admins should have the option to control this visibility via tenant or workspace settings. **Workaround:** Currently unavailable.
