In my Power BI tenant, Azure Maps visual does not allow binding polygon geometries from the data model (GeoJSON/Shape), only Reference Layers are available. This prevents interactive filtering and cross-highlighting of custom polygons (e.g. municipal management zones – CGM). Other tenants and demo videos (2024) show “Add data / Upload data” options which are not present in my tenant, despite having the latest Power BI Desktop and being Tenant Admin. Request: - Enable Data Layer support for polygon geometries in Azure Maps - Or clarify tenant/region limitations officially Contact barcielasebastian@gmail.com ... View more

i have seen deployment pipelines gets failed if we try to deploy rename the existing object and deploy.    example one pipeline name "PL_Test" and  you deployed from Dev to QA workspace . what if you rename the similar object on Dev from "PL_Test" to "PL_Test_New". what will happen if we deploy to QA workspace. as per my understanding this fail.  ... View more

When looking at the settings for the connection it would be helpful if you could see the entire "Data source path".  Currently this URI value is truncated which when dealing with Azure Databricks which makes it difficult to idenfity which warehouse is being used as that comes at the end of the path. ... View more

It would be good if tenant admins had the ability to control what settings individual capacities have, to monitor them via an API, and to track changes as well. Similar to how tenant settings are handled. ... View more

When working with Matrix visual (and others as well) I can't rename it in Selection pane without same name being propagated as visual's Title (when the Title option is ON). Can we go away from that?   I want to use particular name convention for elements on the canvas so I have my Selection pane clean and tidy. And I want to have particular titles for the consumers of the report. ... View more

The underlying architecture of data warehouse within Microsoft Fabric is Delta/parquet ,but coming from a relational database world ,when we create primary key it is always enforced and helps maintains the consistency in the database /datamart .But Fabric warehouses does not enforce primary key which needs to be addressed . ... View more

dHi Power BI team, I’d like to propose a small but meaningful improvement to the Model View interface — one that would help modellers avoid incorrect assumptions and improve clarity for both new and experienced users. In Power BI, many column, table, and relationship properties fall into two very different categories: Binding properties These affect the VertiPaq engine, storage, compression, and model validity. Examples: data type, relationship cardinality, cross-filter direction. Metadata properties These describe intent, assist AI/Q&A, or improve documentation and usability, but do not enforce constraints. Examples: description, synonyms, display folder, “Is nullable”, key column, row label. The challenge is that the interface currently presents both categories in the same visual style, using the same terminology that in other systems (especially SQL) implies strict enforcement. This can lead to incorrect assumptions, especially for users with a relational modelling background. A small UI distinction — even something as simple as grouping, icons, or a visual separator — would make it immediately clear which properties are enforced by the engine and which are descriptive metadata. This would help: prevent misunderstandings for SQL‑trained users reduce cognitive friction when learning the model view clarify the role of semantic metadata in AI‑assisted features improve the teaching and onboarding experience for new modellers Power BI’s modelling layer is incredibly powerful, and this distinction would make it even more intuitive and transparent. Personal note: I only discovered this distinction after a long discussion with CoPilot while writing a course. Someone coming from an SQL background, in a normal work situation, might see something like “Is nullable: true/false” and naturally assume it’s an enforced constraint. Power BI’s job is to report on data in the best shape we can get it into — not to enforce transactional rules — but the UI wording makes it very easy to assume otherwise. A clearer separation of metadata vs binding properties would help users understand what Power BI is actually doing versus what it’s simply describing. Kind regards, John ... View more

I want to deploy a series of workspaces and assign these new workspaces to different domains/subdomains via API REST API, I was trying to use the Domains - List Domains - REST API (Core) | Microsoft Learn interface to get all my domains and either extract the Domain Id or return a message saying that I cannot find the specified domain, but here's the issue, you need to be member of the Fabric Administrator role just to get a list of domains, that's WAY TO much privilege to perform this operation, therefore, the idea is to either have more granular RBAC permission over Fabric (e.g. Fabric Contributor, Fabric Reader) and expose Fabric API permissions (e.g. Application permission Fabric > Read.Domains.All) for Service Principals.  ... View more

We have the need to allow users to use the include/exclude portion of a visual.  But there is no easy way for them to get back to the top without resetting all filters, which has some different fuctionality in the dashboard that we built.   Hoping to get some kind of "undo last action" type of button or "include all" that will bring everything back and remove that filter, without exposing the filter pane to everyone. ... View more

Hi, I've noticed that T-SQL language of a warehouse doesn't support the recursive CTEs. It'a real pity! A such feature is more useful and comfortable one in several scenarios, f.e. to navigate an hierarchy. I hope it will be implemented as soon as possible. Thanks ... View more

A common way to compare data from different time series together is to overlap them, for instance: two separate growing seasons. While the data can be plotted this way, the date always displays the year. So even if I compare 2024, 2023, and 2022. The year value from once of those series, or a reference year for chart purposes, still appears. The way it should work is to allow the year to be turned off and only display months, such as Jan, Apr, Jul, Oct.    See this thread for a discussion of the issue:  Re: X-axis label formatting not responding in a Li... - Microsoft Fabric Community   Here is the best way I've found to deal with it for now. The alterate which shows months would have Apr 2000, Jul 2000, Oct 2000 on the X-axis as labels, since 2000 is the reference year for aligning the data.   ... View more

Hello,   I've regularly noticed that end users initially fail to see the gray scrollbar; especially, in tabular grids. It would be exceedingly helpful for scrollbars to be customizable.   By making them larger it would be readily apparent that more data exists for the user(s) to scroll through. In addition, allowing developers in the desktop to change the color of the scrollbar would help users more easily interact with such visualizations (specifically tabular grids/table visualization).   For end users, unfamiliar with Powerbi this customization would make the table visualizations' scrollable data more intuitive and allow for swifter interaction with such visualizations.   Unfortunately, at the moment, the gray scrollbars do not capture the eyes of end users interacting with dashboards until further inspection.   Thank you in advance! -Sue ... View more

Currently, Power BI does not allow embedding reports from other workspaces within an Org App using the “Embed linked content into app” option. When attempting to do so, the following message appears: This page contains content not provided by Microsoft. Web content could contain code with security or privacy risks. This forces the use of the “Open link in new browser tab” option, which negatively impacts the user experience and breaks integrated navigation. Proposal: Enable the ability to embed reports from different workspaces (if the user has the appropriate permissions), while ensuring security and governance. This would allow: Centralizing content in a single application. Improving productivity and reducing clicks. Providing a smoother and more professional experience. Key benefits: better user experience, increased efficiency, stronger governance, and scalability for corporate apps. If this improvement would benefit you as well, please vote for this idea and share it with your team. The more votes, the higher the chances Microsoft will implement it! ... View more

Currently, when a user who created Microsoft Fabric items leaves the organization, administrators must manually take ownership of those items. This process is time-consuming and inefficient. It would be highly beneficial to have a REST API or a programmatic solution that enables bulk takeover of all Microsoft Fabric items associated with departed users. ... View more

Many organisations have to work with large volumes of publicly available data includign large repositories of parquet files on AWS S3 Buckets with no option or support for clients requiring an access key to be specified.   Please enable anonymous access support for public source like S3 buckets for use with shortcuts, this could make a huge difference for research and science organisations.     ... View more

Marketplace custom visuals fail to render data when dynamic, model-based RLS (user-to-branch mapping via relationships) is applied. Simple/static RLS works correctly, and native Power BI visuals display the same data properly under dynamic RLS. This confirms the model and DAX are valid. This appears to be a compatibility issue between marketplace custom visuals and dynamic RLS in Power BI Service. Expected behavior: Custom visuals should fully respect dynamic RLS, the same way native visuals do. ... View more

On Workspace we don't get Edit Source option to Edit/Modify our query   ... View more

Please add an endpoint to the Job Scheduler API where we can get a list of all failed runs.   The response from this endpoint should, by default, include all failed runs across all workspaces that the caller has access to, and include all item types.   The caller must specify a startTime and an endTime in the request, to only search for failed runs within that time interval.   Optionally, to narrow down the search further, the caller can specify: workspace IDs (list of IDs) item types (list of item types) item IDs (list of item IDs) The default should be to include all. ... View more

パイプラインの各アクティビティにおいて説明文を記載します。 この時、一旦パイプラインを保存して再度開いた後に日本語を説明文に入力⇒変換を何度か行っていると文末に勝手にフォーカスが移動します。この件は既にサポートに連絡済みで現在は仕様なのでこちらに記載してくれと言われました。大変使いづらいので修正して頂けますと幸いです。どうぞ宜しくお願い致します。 ... View more