This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
Additionally, there are new tenant settings for the Azure Maps visual, which require administrators to take action to ensure seamless integration and continued support. For a comprehensive look at these updates and further enhancements, we invite you to read on for more details in the following sections.
Power_BI_June_2025_Feature_Summary
Version number: v: 2.144.679.0
Date published: 6/9/2025
Power BI is turning 10! Come celebrate with us!
The Microsoft Fabric Community Conference is back x2! Join us in Vienna and Atlanta!
Secure Collaboration on Sensitive Data in Power BI Desktop
Updates to visual calculations (Preview)
Sparklines (Generally Available)
Updates to numeric range and field parameters (Preview)
New Tenant Settings for Azure Maps Visual (Action Required)
Support for mapping South Korean locations
Support for adding paginated reports to org apps (Preview)
Use Copilot on reports in org apps (Preview)
Power Query editing in the web for import models (Preview)
Expanded support for write operations via External tools
Connect to Vertica database with the user-installed ODBC driver (Generally Available)
QuickBooks Online (Beta) connector under deprecation
Connect to PostgreSQL database without manual driver installation
Org apps are now available in Power BI mobile! (Preview)
Power BI Project (PBIP) public JSON schemas
Drill Down Waterfall PRO by ZoomCharts
Revenue Filter by JTA – a Data Scientist’s Visualization Tool
Decomposition Tree – All Expanding
Join us for the #PBI10 DataViz contest, expert-led sessions to prepare for PL-300 with discount exam vouchers, and more to mark this milestone.
Don’t miss out. Register here and use code MSCATL for a $200 discount on top of current Super Early Bird pricing!
Don’t want to wait until March? Join us at FabCon Vienna from September 15-18, 2025.
Register and use save €200 with code FABCOMM.
Let’s break it down.
What are sensitivity labels, and why should you care?
You can set sensitivity labels to classify your Power BI files—for confidential or internal use only. Once applied, you gain the following benefits:
What’s been done so far?
To open a PBIX file, you either have to be the label issuer or have one of the following usage rights.
These usage rights grant elevated permission, as they grant permission to change the sensitivity label. Because Power BI and Office apps use the same label policies, compliance admins may prefer not to grant these usage rights for highly confidential labels.
This might block you from collaborating with your colleagues when you’re sharing or downloading Power BI reports and trying to open them in the desktop app.
What’s new?
With this upcoming update, working with protected Power BI files is smoother than ever:
Seamless collaboration with protected files
Now, more users in your organization can:
What is still restricted?
To maintain protection and policy enforcement, a few limits still apply when working with labeled files:
These safeguards help prevent accidental leaks and unauthorized distribution.
How to get started
To take advantage of this update, here’s what needs to be in place:
1. Ensure users have the correct usage rights on the sensitivity label
The Microsoft Purview compliance admin should assign the following usage rights:
Note: These rights are a subset of the built-in ‘editor’ (previously named ‘co-author’) permission preset in the Microsoft Purview compliance center.
2. Enable information Protection in the Power BI Admin Portal
Power BI admins must ensure the Information Protection feature is enabled.
That’s it—no tenant switches or preview feature toggles in desktop required.
Power BI Desktop now makes it simpler and safer to collaborate on sensitive data. With the new encryption update, you get:
To learn more, refer to the visual calculations documentation.
Create visual calculations faster with parameter pickers
It is now even easier and faster to write visual calculations thanks to the parameter pickers. When you load a template or use one of the functions exclusive to visual calculations, the parameter pickers for all required parameters with defined options will appear.
A_screenshot_of_a_computer_AI-generated_content_may_be_incorrect
Then it’s just a matter of selecting the value you want from the drop down and you’re done. A couple of clicks is all that is needed. This makes creating visual calculations a breeze, demonstrated in the screenshot example:
A_screenshot_of_a_computer_AI-generated_content_may_be_incorrect
Of course, the colored highlights between the formula bar and the visual matrix will match:
A_screenshot_of_a_computer_AI-generated_content_may_be_incorrect If you still want to type or make more advanced changes you can do that still! Simply change the value and the parameter picker will disappear. As soon as you enter a valid value, the parameter picker will reappear.
Note that the parameter pickers right now are only available for required parameters on functions that are exclusive to visual calculations (and select other functions) that have a defined list of options. Required parameters that can take any text, or numerical value will not get a parameter picker, and neither will many DAX functions.
Visual calculations are more resilient to changes in the visual
If you previously created a visual calculation with an axis reference, such as COLUMNS, and then changed visual types resulting in the absence of COLUMNS, the visual calculation would produce an error and the visual would return an error. Starting with this release, a reference to a non-existent axis is permissible and will be ignored.
Additionally, if you write RUNNINGSUM([Sales Amount], COLUMNS) on a bar chart (which does not have a COLUMNS axis), the result will simply equal the value of Sales Amount:
A_screenshot_of_a_computer_AI-generated_content_may_be_incorrect
We often change visual types to find the best way to present your data. Visual calculations should now work without breaking due to invalid axis references, making them easier to use. For instance, here's the same visual calculation on a card (which has no real axis):
Power_BI_June_2025_Feature_Summary
The visual calculation did not produce an error, even though it referred to an axis that was not present. An axis that is not present is simply ignored.
Easily create calculations in Explore
This month, we added visual calculations to Explore. With Explore, it’s easy to perform quick and powerful data analysis. Visual calculations do the same but for calculations, so bringing the two experiences together made a lot of sense and makes Explore even more effective. Once you have opened your data in Explore, you can create a visual calculation from either the matrix or the visual by selecting ‘New visual calculation’:
A_screenshot_of_a_computer_AI-generated_content_may_be_incorrect
This opens the visual calculations edit mode which should feel familiar to you. Here you can enter your visual calculation just like you are used to doing in reports. The same tools are available, including the highlights, templates and parameter pickers:
A_screenshot_of_a_calculator_AI-generated_content_may_be_incorrect
After adding the visual calculation, the other visual will show the visual calculation as well (depending on the visual type):
Power_BI_June_2025_Feature_Summary
If the other visual is unable to display data after the addition of the visual calculation, it will enter an error state. In such cases, you may either remove the visual calculation or modify the visual type.
Visual calculations in Explore make exploring data even easier and more powerful.
For new sparklines, calculation group selections will be applied to the individual values on the sparkline by default. If you change the setting to ‘Entire sparkline’, the calculation group will be evaluated over all the points on the sparkline. Existing sparklines will remain unchanged, and calculation group selections will continue to apply to the entire sparkline unless you change their configuration.
An example of this in practice is a measure that calculates the Sum of Gross Sales by totaling the Gross Sales.
Sum of Gross Sales = SUM( financials[Gross Sales] )
IsBigSales = IF ( 'financials'[Sum of Gross Sales] >= BigSalesSize[BigSalesSize Value], TRUE, FALSE )
| Calculation Item Name | Expression | Description |
| Actual | Actual = SELECTEDMEASURE() | Show value always |
| Actual For BigSales Only | Actual For Big Sales Only = IF( [IsBigSales], SELECTEDMEASURE(), BLANK() ) | Show value for big sales, otherwise return blank |
| Percentage Of Grand Total | Percentage Of Grand Total = DIVIDE( SELECTEDMEASURE(), CALCULATE( SELECTEDMEASURE(), ALLSELECTED() ) ) | Returns the percentage of the grand total |
A_screenshot_of_a_computer_AI-generated_content_may_be_incorrect
The sparkline that shows Sum of Gross Sales by Month Number is set to the default behavior of applying the sparkline to Individual Values:
A_screenshot_of_a_computer_AI-generated_content_may_be_incorrect
When switching the calculation group to 'Actual for Big Sales Only' using the slicer, it will evaluate each value on the sparkline. Therefore, it will display only values for months and brand combinations exceeding the 1,000,000 BigSalesSize cutoff. To enhance clarity, I have included a matrix that displays Gross Sales by Month and Product, utilizing conditional formatting to emphasize values above the cutoff. The highlighted values correspond with those on the sparkline:
A_screenshot_of_a_computer_AI-generated_content_may_be_incorrect
Let's set the sparkline to apply the calculation group to the entire sparkline. Now all sparklines appear because the calculation evaluates the total values without considering the X-axis (Month Number). Since each Product's Gross Sales exceed the cutoff point, all sparklines display. If we raise the cutoff to 3,000,000, some sparklines will disappear. I added a matrix with conditional formatting below to illustrate this behavior:
A_screenshot_of_a_computer_AI-generated_content_may_be_incorrect
The Sum of Gross Sales exceeds the cutoff for almost all Products, except Carretera and Montana. Consequently, it's not displayed in the matrix or as a sparkline for these products. Sparklines appear normally for other Product/Country combinations. 'Show items with no data' is enabled to display brands where the sparkline and Sum of Gross Sales return BLANK(); otherwise, those brands would be hidden.
It is important to recognize that applying a calculation group item, which performs an arithmetic operation, to a sparkline set to ‘Apply to entire sparkline’ is not supported. To illustrate this, I will change the calculation group to Percent of Grand Total (which indeed performs an arithmetic operation using DIVIDE). As a result, the visual showing the sparkline will show an error and prompt you to set the sparkline to 'Individual values' to display it correctly again:
Power_BI_June_2025_Feature_Summary
Pressing Convert or setting the sparkline to ‘Individual values' again will make the visual show again:
Power_BI_June_2025_Feature_Summary
Calculation groups and sparklines are a powerful combination! For more information about sparklines and calculation groups refer to the documentation.
A_screenshot_of_a_computer_AI-generated_content_may_be_incorrect
Additionally, this month we are enhancing accessibility to field parameters generated by UI. A button has been added in the model view within Desktop:
Power_BI_June_2025_Feature_Summary
You will also find a button when editing a semantic model in the Power BI service.
A_screenshot_of_a_computer_AI-generated_content_may_be_incorrect
Together, these changes make numeric range and field parameters just that little bit more powerful! More is coming soon, so stay tuned. In the meantime, learn more about field parameters and numeric range parameters in the documentation.
Historically, enabling Azure Maps required an admin opt-in due to reliance on third-party services for geocoding, which introduced compliance complexities around data leaving your tenant’s region. That’s now changing.
What’s new?
After work in recent years, the Power BI Azure Maps visual no longer requires sub processors for geocoding and guarantees EU and US customers’ data resides within the US and Europe geographic boundaries.
To support a wider range of customer needs, we’re also introducing granular tenant settings that let you:
Power_BI_June_2025_Feature_Summary
The state of the tenant settings, outlined in the table below, will be dependent on whether you’ve enabled the previous Azure Maps setting or not.
| Setting Name | Description | Default State |
| Users can use the Azure Maps visual. | When this setting is on, users will be able to create and view the Azure Map visual.
Note: This does not control whether data is able to leave your region/compliance boundary for mapping purposes. |
On by default, except for existing tenants that have explicitly turned Azure Maps off |
| Data sent to Azure Maps can be processed outside your tenant's geographic region, compliance boundary, or national cloud instance. | Azure Maps services are currently not available in all regions and geographies. With this setting on, data sent to Azure Maps can be processed in a region where the service is available, which might be outside your tenant's geographic region, compliance boundary, or national cloud instance. | Off by default, except for existing tenants that have turned Azure Maps on |
| Data sent to Azure Maps can be processed by Microsoft Online Services Sub processors. | Some Azure Maps visual services, including the selection tool, may require mapping capabilities provided in part by Microsoft Online Services sub processors. This setting will control the availability of these features. | Off by default, except for existing tenants that have turned Azure Maps on |
To support these new capabilities, your organization must be on the April release of Power BI Desktop or later. If you’re on an older version, the Azure Maps visual will no longer work in your reports.
Additionally, customers outside the US and EU will need to explicitly enable a new tenant setting: Data sent to Azure Maps can be processed outside your tenant’s geographic region, compliance boundary or national cloud instance’ to allow Azure Maps mapping features to work as expected. If the visual is not enabled, the users in your organization will see this error message.
A_screenshot_of_a_computer_AI-generated_content_may_be_incorrect
This change will roll out to the various regions over the coming weeks, so if you still see just a single Azure Maps tenant setting, check back in over the coming week. In the meantime, check out the documentation for detailed guidance.
To enable this functionality, you must turn on all three Azure Maps tenant settings, as Azure Maps depends on a mapping sub processor to provide geolocation support in South Korea:
Support for South Korea launching noon
While we can now support geocoding location data for South Korea for users in all our currently supported regions, South Korea itself is still currently unsupported. That said, we’re actively working to also enable Azure Maps support for South Korea within its geo-boundaries. Stay tuned for future updates as we work toward making the Power BI Azure Maps visual available in the South Korea.
Power_BI_June_2025_Feature_Summary
Unlike workspace apps and unique to org apps (preview), the org app will propagate access to the paginated report AND the underlying semantic model that informs the paginated report. Your org app consumers can then view the paginated report from the org app. To learn more about Get started with org apps (preview), refer to the documentation.
Power_BI_June_2025_Feature_Summary
Screenshot_of_a_demo_org_app_with_an_report_loaded_in_the_content_area_and_the_C
Learn more about the preview of org apps and Copilot for reports.
Once available, this update will unlock a major enhancement to the existing preview experience for data model editing in the Service : the ability to make changes using Power Query for existing import models directly in the browser.
This means you'll be able to use Power Query in the web to:
Get data
Add new import tables to your existing semantic models directly on the web using the familiar Power Query ‘Get Data’ experience. Simply select ‘Get data’ from the Home tab of the ribbon to choose your connector and bring in new data to your semantic model.
Power_BI_June_2025_Feature_Summary
Transform data/Edit queries
Shape your data with the full Power Query editor, now available on the web. Select ‘Transform data’ from the Home tab of the ribbon to launch the rich, modern Power Query user interface.
Power_BI_June_2025_Feature_Summary
Refresh
Refresh both schema and data right from the web editing experience. Simply select ‘Refresh’ from the ‘Home’ tab while editing your semantic model.
For more details on the subject, refer to the documentation. Please continue to submit your feedback directly in the comments of this blog post or in the feedback forum.
Previously, some write operations were restricted, blocking external tools from altering tables, columns, or query expressions, with changes reverted to the next Power BI Desktop refresh. Now, you can use external tools for any write operation on your semantic model.
Learn more about supported changes from external tools in the documentation.
Along with this update, note starting June 2025, connecting to Vertica database without on-premises data gateway (cloud connections) will no longer be supported and will result in an error. If you have such workload, please change to use the on-premises data gateway and install the Vertica ODBC driver.
To learn more, refer to the Vertica database connector documentation.
For additional information about org app, please visit Get started with org apps (preview). More details about org apps in Power BI mobile can be found at Using org apps (preview).
Power_BI_June_2025_Feature_Summary
A_screenshot_of_a_computer_AI-generated_content_may_be_incorrect
The schema URL is publicly accessible, allowing users to understand all available properties and their meanings through the file's evolution. Additionally, it provides built-in IntelliSense and validation when editing with code editors like Visual Studio Code. To learn more, see PBIP Json file schemas.
Main features:
A_screenshot_of_a_graph_AI-generated_content_may_be_incorrect
A_screenshot_of_a_graph_AI-generated_content_may_be_incorrect
Key Features:
Overview
Revenue Filter is a custom Power BI designed to give report users a more intuitive and flexible way to filter data based on revenue columns. Instead of using the traditional slider slicer, users can apply Excel-style filtering logic directly within their reports.
This visual allows you to select from multiple comparison types - greater than, less than, equals, between and more - via a simple dropdown, then enter the value to filter by. This makes it easy for anyone viewing the report to understand the exact filter being applied briefly.
Whether you're a business analyst, data scientists, or finance professional, this tool enhances your ability to quickly explore revenue data without clutter or confusion.
Key Features:
1. Now you can add a target field to perform comparisons against primary measures.
A_diagram_of_a_graph_AI-generated_content_may_be_incorrect
2. You can add images to each node. Images should be stored as base64 type.
Power_BI_June_2025_Feature_Summary
3. The visual now supports vertical orientation.
A_screenshot_of_a_computer_AI-generated_content_may_be_incorrect
Resources
We hope that you enjoy the update! If you installed Power BI Desktop from the Microsoft Store, please leave us a review.
As always, keep voting on Ideas to help us determine what to build next. We are looking forward to hearing from you!
Power_BI_June_2025_Feature_Summary
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.