There must be a way if we download the power BI desktop and be able to publish the report in the workspace where it creates the semantic model for us to repurpose. Helps To minimize Fabric configuration and refresh issues, the Live Connection report should be deployed to the same workspace as the semantic model. Live‑connected reports do not benefit from duplication across workspaces and are tightly coupled to the source model’s security and connection settings. ... View more

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. ... View more

Description Current behavior In Microsoft Fabric, workspace retention and recovery settings are configured at the tenant level through the Fabric Admin Portal. The retention period for deleted collaborative workspaces can be configured between 7 to 90 days. This configuration applies uniformly across all workspaces in the organization. There is currently no supported capability to define different retention policies per workspace or per capacity (based on the available documentation and admin settings scope). Additionally: Personal workspaces (“My workspace”) have a fixed 30-day retention period that cannot be modified. Problem statement This tenant-wide configuration introduces limitations for organizations with diverse governance, compliance, and operational requirements. Examples: Some workspaces (e.g., production or regulated environments) require longer retention periods for compliance or auditing. Other workspaces (e.g., dev/test environments) may require shorter retention periods to optimize cost and lifecycle management. Large enterprises operating multiple business units or environments cannot apply differentiated policies aligned with their governance models. Impact Lack of flexibility in governance and compliance enforcement Increased operational overhead (manual processes or workaround strategies) Difficulty aligning Fabric retention behavior with enterprise data lifecycle policies Potential risk of either: Data being deleted too soon, or Data being retained longer than necessary Suggested improvement Provide the ability to configure retention policies at a more granular level, such as: Workspace-level retention configuration Capacity-level retention configuration Priority-based or tag-based retention policies (e.g., Prod vs Dev) This would enable: More flexible governance models Better alignment with enterprise compliance requirements Improved lifecycle management of Fabric assets ... View more

  Hello Fabric Product Team, I would like to highlight a key limitation in the current Microsoft Fabric Notebooks experience regarding code modularity and reusability. Currently, the “builtin” resources folder is scoped to each notebook, meaning that Python modules placed in one notebook’s “builtin” directory are not accessible to other notebooks in the workspace. As a result, any reusable Python code (utility functions, connectors, etc.) must be manually copied into the “builtin” folder of every notebook that needs it. This approach goes against best practices like DRY (Don’t Repeat Yourself) and creates significant maintenance, versioning, and collaboration issues for data engineering teams, especially on large-scale projects. Request: Please consider introducing a “shared” Python resources folder or a workspace-level global modules directory, allowing all notebooks in a workspace to import and reuse common Python scripts (.py files) without duplication. This enhancement would dramatically improve code maintainability, encourage reuse, and align Fabric with other leading data platforms that support shared library mechanisms. Thank you for your attention. Best regards, Marc P.  ... View more

The ai.translate supports specifying the output language, but the input language can only be inferred, which is prone to errors. It would be nice to have the option to also specify the input language. It could also support a list of input languages for the cases where a column might contain multiple languages. This could help the AI better detect the input language(s) and improve accuracy. ... View more

I started working with version control and encountered the following error while loading a report from a historical commit. "There's a problem with the definition content in your Power BI Project. Column ‘X’ in Table ‘TableX’ contains a duplicate value ‘’ and this is not allowed for columns on the one side of a many-to-one relationship or for columns that are used as the primary key of a table. The current operation was canceled because another operation in the transaction failed" Using version control doesn’t make sense with errors like this. The historical commit contained a different table layout that joined to the fact table via a different column, which made sense and worked in the previous version. In the latest commit, I made changes—the table was restructured in Power Query, and the join is now performed via a different column. The model has been changed. After closing the report and setting the checkout to the historical commit, the report does not open and returns an error, as it was unable to recreate the model and connections saved in the historical commit.   ... View more

When using scorecards in my organization a common use case is to track KPI trends that don't have a due date.  For example sales revenue doesn't have a due date because we aren't planning to go out of business.   Having the ability to turn off due dates or leave them blank for individual KPIs would cause less user confusion.   We finde we either need to maintain the due date, set the due date out to a year we figure "I will be retired or dead by then", or we just tell people to ignore it and have to explain that every time we have a new hire.   I would go as far as to say most scorecard items in organizations I work with don't have due dates. ... View more

In Power BI Desktop, there is currently no built‑in feature to automatically select a related value in one slicer based on the selection made in another slicer. There is no native capability in Power BI Desktop for one slicer to automatically set the selected value of another slicer. Example: A one‑to‑one relationship between State and State_Capital where selecting State should auto‑select its capital. This requires either: Slicer‑to‑slicer binding DAX‑driven slicer default selection Or interaction‑based auto‑selection logic Currently, filtering alone does not solve this scenario. Power BI currently allows slicers to filter each other but does not allow automatic selection of a related slicer value. Example: Selecting State should automatically select its corresponding State Capital in another slicer. This would improve guided analytics and reduce unnecessary user interaction. ... View more

Would be great to be able to use Workspace Identity to authenticate Copy Job connections. Much more preferable than using Org Account Authoirzation when calling Copy Jobs in a pipeline.  ... View more

Ability to browse a report as another user by admin indstead og browsing the model, add an ability on the reports ... View more

Problem statement: Fabric Data Factory copy activity error messages when sink is lakehouse are very generic. Example: Failure happened on 'Sink' side. 'Type=Microsoft.Data.DeltaLake.MetadataChangedException,Message=conflicting metadata change,Source=Microsoft.DataTransfer.ClientLibrary,'   If we could gain better visibility on what is the column causing the issue or stack trace to expose a bit more technicalities it would be easier to investigate FDF errors - potentially we wouldn't also need to engage Fabric support team for root cause analysis. We would like to see error messages which are detailed to the same extent as in Azure Data Factory. ... View more

Just add a little 'refresh' icon that's crossed out when you disable a query in powerquery with the "Include in report refresh" option. I had a report where one of the tables unknowingly did not refresh for months, leading to some frustrations. Just a simple visual (like when you disable a query loading) would help quite a lot. ... View more

As described here, Solved: Re: Plan module (used to be powertable), single se... - Microsoft Fabric Community I have found an issue with the sorting columns in the plan/powertable module. In a SKU:F8 North Europe, we have master_data_table for our employees, enriched with multiple lookups from other tables. When sorting by a column the plan/powertable module fails to render the field data. ... View more

Having the ability to run python code outside of the notebook environment (like we can for pyspark jobs) could be a real win for efficiency and modularity. It would allow users to package robust, unit-tested code and deploy it to the fabric environment where it could run as a cost-effective single-node job. Databricks has an implementation for this, and it would be really nice to see something similar come to Fabric. Notebooks are great for ad-hoc or exploratory stuff, but building something robust in them feels like shoving a peg into a wrong-shaped hole. They are (nearly) impossible to unit test, so you often end up creating libraries which allow you to package transformations in a way that can be tested, then your notebooks end up being essentially thin wrappers around a bunch of external code. I think the most obvious example for this is the number of Fabric DBT implementations that essentially involve installing DBT core into a notebook and running it there (I know there is DBT jobs coming, but this is beside the point). This is a symptom of a larger need for this type of hosting/execution of code within the environment. Yes, you could host the code on a vm external to Fabric but that goes against the ethos of a unified data platform. Offering something like this would be a great way to increase the flexibility and extensibility of the platform. The implementation can be fairly barebones and developer forward, aiming to provide maximum flexibility and extensibility. Basically a way to run python scripts/CLI tools on the Fabric capacity.    ... View more

  File name creation format should restrict me from using any special characters other that hyphen as later on it throws a validation error for my pipelines. It is just a small suggestion not a big idea!  ... View more

Description: Currently, export format settings for paginated reports can only be controlled at the tenant level or security group level via admin portal settings. There is no way to restrict export formats (e.g., allow only PDF) on a per-report or per-workspace basis.   Business Scenario: For compliance and audit purposes, some reports must be exported only in specific formats (e.g., PDF only). With the current design, disabling Excel export applies to all paginated reports in the tenant, which is too broad and impacts other use cases.   Requested Feature: Please add the ability to configure allowed export formats at the report level or at minimum at the workspace level, so that specific reports can be locked to PDF-only export for audit/compliance purposes. ... View more

Summary Currently, Microsoft Fabric Lakehouses store data in OneLake, logically centralized by region and capacity. However, there is no Microsoft-supported mechanism to transfer or migrate Lakehouse data across tenants, even when both tenants are owned or controlled by the same organization. This idea proposes a Microsoft-managed, support-driven cross-tenant transfer capability, where access to both tenants can be validated and a secure migration can be performed. Problem Statement Many organizations operate multiple Microsoft Entra tenants due to: Mergers and acquisitions Regional or regulatory separation Divestments or tenant consolidations Managed services and partner-led implementations Today, moving Fabric Lakehouses or OneLake data between tenants requires manual, unsupported, or fragile workarounds, such as: Exporting and re-ingesting data Custom pipelines with duplicated storage costs Breaking lineage and governance metadata Additionally: Governance objects (lineage, shortcuts, permissions) are lost Support cannot officially validate or assist with cross-tenant migrations Large datasets make re-ingestion slow, risky, and expensive Proposed Solution Enable a Microsoft-supported cross-tenant OneLake transfer process, initiated via a support ticket or controlled workflow, with the following characteristics: Validation of administrative access to both source and target tenants Same-region or approved cross-region transfers Secure, audited data movement at the OneLake level Optional inclusion of: Lakehouse metadata Directory structure Table definitions Shortcuts and references (where applicable) This could be implemented as: A Microsoft Support-assisted operation A Fabric Admin or Tenant-level migration workflow Or a future Fabric-managed migration service Business Value Reduces risk and cost for tenant consolidation projects Enables cleaner M&A and divestment scenarios Preserves governance, lineage, and Fabric-native structures Avoids data duplication and unnecessary storage costs Aligns with OneLake’s vision as a unified, logical data lake Who Would Benefit Enterprises with multiple Entra tenants Partners and MSPs managing Fabric for multiple customers Organizations with M&A activity Regulated industries needing structured tenant separation Additional Notes This feature would not need to be self-service initially. A controlled, support-driven process would already deliver significant value while maintaining security, auditing, and governance guarantees. ... View more

Currently, Power BI/Fabric supports email notifications only for refresh failures, but there is no capability to alert users when refresh operations run for an extended duration or get stuck in progress, which can delay issue detection and impact business reporting. This lack of proactive visibility creates challenges in monitoring large-scale workloads, especially in scenarios involving Dataflow Gen2, pipelines, or semantic models where refreshes may remain locked or inactive for long periods without failure notification.    Proposed Feature: We request the introduction of proactive email notifications for long-running or stuck refresh operations based on configurable duration thresholds, along with the ability to define custom timeout limits at dataset/dataflow/pipeline level. This enhancement would enable early detection, improved operational monitoring, and the option to take automated actions such as alerting, retrying, or canceling refreshes, thereby improving reliability and capacity management ... View more