Contents

Power BI Desktop
Overview
What is Power BI Desktop?
Quickstarts
Connect to data
Tutorials
Shape and combine multiple data sources
Importing and analyzing data from a Web Page using Power BI Desktop
Analyzing sales data from Excel and an OData feed
Create your own measures in Power BI Desktop
Create calculated columns in Power BI Desktop
Facebook analytics using Power BI Desktop
Dynamic row level security with Analysis Services tabular model
Samples
Samples for Power BI
Using the sample content packs
Customer Profitability sample: Take a tour
IT Spend Analysis sample: Take a tour
Human Resources sample: Take a tour
Opportunity Analysis sample: Take a tour
Procurement Analysis sample: Take a tour
Retail Analysis sample: Take a tour
Sales and Marketing sample: Take a tour
Supplier Quality Analysis sample: Take a tour
Download the Financial Sample workbook
Concepts
What's new in the latest Power BI Desktop update?
Modeling view in Power BI Desktop (Preview)
Aggregations in Power BI Desktop (Preview)
 Composite models in Power BI Desktop
Many-to-many relationships in Power BI Desktop (Preview)
Storage mode in Power BI Desktop (Preview)
Bidirectional cross-filtering in Power BI Desktop
Power BI and DirectQuery
Data sources supported by DirectQuery
Power BI data source prerequisites
Default member in multidimensional models in Power BI
Custom visuals FAQ
How to
Get Power BI Desktop
Getting started guide for Power BI Desktop
Common query tasks in Power BI Desktop
Create and manage relationships in Power BI Desktop
Data view in Power BI Desktop
Query overview in Power BI Desktop
DAX basics in Power BI Desktop
Relationship view in Power BI Desktop
Report view in Power BI Desktop
Connect to multiple data sources in Power BI Desktop
Publish from Power BI Desktop
Part I, Add visualizations to a Power BI report
Part 2, Add visualizations to a Power BI report
Customize visualization title, background, and legend
Show items with no data in Power BI
Connect to data
Data sources in Power BI Desktop
Connect to a Web page by example (preview)
Connect to datasets in the Power BI service
Import Excel workbooks into Power BI Desktop
Connect to data using generic interfaces
Connect to a PDF file
Connect to Adobe Analytics
Connect to an Oracle database
Running Python scripts in Power BI Desktop
Using Python in Power Query Editor
Use an external Python IDE with Power BI
Create Power BI visuals using Python
Running R scripts in Power BI Desktop
Using R in Query Editor
Use an external R IDE with Power BI
Supported R packages
Enter data directly into Power BI Desktop
Connect to Excel in Power BI Desktop
Analysis Services multidimensional data in Power BI Desktop
Connect to CSV files in Power BI Desktop
Connect to a Google BigQuery database in Power BI Desktop
Connect to an Impala database in Power BI Desktop
Connect to an OData feed in Power BI Desktop
Connect to an Amazon Redshift database in Power BI Desktop
Connect to a Web page from Power BI Desktop
Connect to a Snowflake computing warehouse in Power BI Desktop
Connect to Azure Consumption Insights data
Use SAP HANA in Power BI Desktop
Analysis Services tabular data in Power BI Desktop
Use DirectQuery in Power BI Desktop
DirectQuery for Oracle and Teradata databases
DirectQuery and SAP Business Warehouse (BW)
DirectQuery and SAP HANA
Assume referential integrity setting in Power BI Desktop
Use the SAP BW connector in Power BI Desktop (Preview)
Use OneDrive for Business links in Power BI Desktop
Third-party service: Facebook connector for Power BI Desktop
Third-party service: Google Analytics connector for Power BI Desktop
 Project Online: connect to data through Power BI Desktop
Transform and shape data
Use Shape Maps in Power BI Desktop (Preview)
Combine binaries
Model your data
Data categorization in Power BI Desktop
Tag a barcode field for the mobile apps
Set geographic filtering for the mobile apps
Calculated columns in Power BI Desktop
Calculated tables in Power BI Desktop
Measures in Power BI Desktop
Edit Q&A linguistic schema
Import and display KPIs (Preview)
Create reports
Visual elements for reports
Create tooltips based on report pages
Export to PDF and print reports
Q&A in Power BI Desktop
Analytics pane in Power BI Desktop
Using insights to explain increases and decreases
Using insights to find where distribution is different in charts
Bookmarks in Power BI
Use Report themes
Try the new filter experience
Use Quick Measures
Using What if parameters
Use drillthrough
Use a relative date slicer and filter
Use grouping and binning
Create Power BI visuals using R
Use R-powered custom visuals
Use gridlines and snap-to-grid
 Page display settings in a Power BI report
Add a column from an example
Add a custom column
Create responsive visuals in Power BI
Use inline hierarchy labels in Power BI Desktop (Preview)
Use the numeric range slicer
Create a slicer you can resize
Create custom answer cards for Cortana
Row-level security
Customizing tooltips
Text boxes and shapes in reports
Add a hyperlink to a text box
Hyperlinks in tables
Conditional table formatting
Sort by column in Power BI Desktop
Create reports optimized for mobile apps
Use See Data and See Records
Tips for creating reports
Visualizations
Visualizations in Power BI
Visualization best practices
Change the type of visualization in a report
Data point limits by visual type
Show the data used to create the visual
Getting started with color formatting and axis properties
Tips and tricks for color formatting
Copy and paste a visualization
Export the data used to create the visualization
Move, resize, and pop out a visualization in a report
Change how visuals interact in a report
Tips and tricks for Power BI map visualizations
Customize X-axis and Y-axis properties
 ArcGIS maps
Basic area chart
Cards (big number tiles) in Power BI
Combo chart in Power BI
Doughnut charts in Power BI
Filled maps (Choropleths) in Power BI
Funnel charts in Power BI
Key influencers charts in Power BI
High density line sampling
KPI Visuals
Matrix visual
Create advanced analytics and visualizations using R scripts in Power BI
Radial gauge charts in Power BI
Ribbon charts
Scatter charts in Power BI
High density scatter charts
Slicers in Power BI
Tables in Power BI
Treemaps in Power BI
Waterfall charts in Power BI
Create dynamic reference lines
Troubleshoot
Resolve issues importing Access Databases and Excel spreadsheets in Power BI
Desktop and Power Query
Resolve issues when starting Power BI Desktop
Reference
Data types in Power BI Desktop
Formula editor shortcuts for Power BI Desktop
Power BI Desktop privacy levels
Connector extensibility in Power BI
Resources
Power BI Desktop videos
Previous monthly updates to Power BI Desktop
 Power BI Desktop Send a Smile privacy statement
Accessibility in Power BI reports
Manage the Power BI Desktop sign-in form
Power BI service
Overview
What is Power BI?
Comparing Power BI Desktop and the service
Tutorials
Get started with Power BI
Connect to a GitHub sample
Using Cognitive Services in Power BI
Machine Learning integration with Power BI
Build a Machine Learning model with Power BI (Preview)
Concepts
What's new in the Power BI service
Basic concepts
Basic concepts for designers
Kinds of data in Power BI
Tour the report editor
Workflow in Power BI
Organizing your work
Ways to share your work
Keeping data fresh
Monitoring usage
Licensing
Self-service sign-up
Licensing in your organization
Features by license type
More concepts
10 tips for getting help
Power BI support options
Licensing special cases
 Extended Pro Trial activation
Power BI for US Government
FAQ for Germany Cloud customers
Other
Microsoft Flow and Power BI
Get started with third-party apps
How to
Get data from files
Getting data from files
From Excel to stunning report
Get data from Excel workbook files
Get data from Power BI Desktop files
Edit parameters
Get data from comma separated value (.csv) files
Real-time streaming in Power BI
Publish to Power BI from Excel
Reduce the size of an Excel workbook
Get data from databases
Azure and Power BI
Power BI and Azure egress
Azure SQL Data Warehouse with DirectQuery
Azure SQL Database with DirectQuery
SQL Server Analysis Services live data in Power BI
Refresh data
Configure scheduled refresh
Refresh a dataset from a Power BI Desktop file - local
Refresh a dataset from a Power BI Desktop file - cloud
Refresh a dataset from an Excel workbook - local
Refresh a dataset from an Excel workbook - cloud
Refresh a dataset created from a .csv file on OneDrive
Troubleshooting refresh scenarios
Dashboards
 Intro to dashboards
Dashboard tiles
Create a dashboard from a report
Create a copy of a dashboard
Pin a tile to a dashboard from a report
Pin a tile from one dashboard to another
Pin a tile to a dashboard from Excel
Pin a tile to a dashboard from Q&A
Pin an entire report page to a dashboard
Data alerts in Power BI service
Add an image, text box, video, or code to a dashboard
Edit a tile
Tips for designing a great dashboard
Create a phone view of a dashboard
Create a QR code for a tile
Add an image to a dashboard
Dashboard data classification
Dashboard themes
Reports
Create a report from a dataset
About filters and highlighting in reports
Add a filter to a report
Save a report in Power BI
Interact with a report in Editing View
Analyze in Excel
Tips and tricks for creating reports
Work with aggregates in the service
Usage metrics for reports
Create a QR code for a report
Export a report to Power BI Desktop (Preview)
Filter a report using parameters in the URL
Best practices for building fast and reliable reports
Ask questions of your data
Get started with Power BI Q&A
Use Q&A to create visuals and reports
Make your data work well with Q&A
Create featured questions for Q&A
Visualization types in Q&A
Use Q&A with live connections
Intro to Cortana for Power BI
Enable Cortana for Power BI
Quick Insights in Power BI
Optimize your data for Quick Insights
Collaborate in Power BI
Create app workspaces
Create the new workspaces (preview)
Create and share apps
Manage data storage in workspaces
Connect to files on your group's OneDrive
Collaborate in your group workspace
Manage your group in Power BI and Office 365
Publish and share your work
Share dashboards and reports
Share a filtered report
Subscribe yourself and others
Embed report in SharePoint Online
Embed report in a secure portal or website
Publish from Power BI to the web
Share a dashboard that links to an Excel workbook on OneDrive
Power BI publisher for Excel
Self-service data prep
Self-service data prep with dataflows
Create and use dataflows
Computed entities with Power BI Premium
 Connect to data sources with dataflows
Using dataflows with on-premises data sources
Link entities between dataflows
Using incremental refresh with dataflows
Developer resources for dataflows
Connect to dataflows in Power BI Desktop
Dataflows and Azure Data Lake integration (Preview)
Connect Azure Data Lake Storage Gen2 for dataflow storage (Preview)
Configure workspace dataflow settings (Preview)
Add a CDM folder to Power BI as a dataflow (Preview)
Integrate Machine Learning in Power BI (Preview)
Use Cognitive Services in Power BI (Preview)
Automated Machine Learning in Power BI (Preview)
Paginated reports in Power BI
What are paginated reports? (Preview)
Paginated reports FAQ (Preview)
Create a paginated report and upload it (Preview)
Get around Report Design View (Preview)
Enter data directly in a paginated report (Preview)
Create an embedded data source (Preview)
Create an embedded dataset (Preview)
Create parameters (Preview)
Publish a paginated report (Preview)
View a paginated report (Preview)
Interact with parameters (Preview)
Template apps
Template apps overview
Create template apps
Tips for creating template apps
Install & distribute template apps
Troubleshoot
Forgot your password for Power BI?
 Capturing additional diagnostic information for Power BI
Alternate email address for Power BI
How to use the same account login for Power BI and Azure
Office 365 dedicated - known issues
Troubleshoot Cortana
Troubleshooting analyze in Excel
Troubleshooting the on-premises data gateway
Troubleshooting Power BI gateway - personal
Troubleshooting unsupported data source for refresh
Troubleshooting scheduled refresh for Azure SQL Databases
Error: We couldn't find any data in your Excel workbook
Troubleshooting tile errors
How to refresh your Xero content pack credentials if refresh failed
Can't sign in
Other tasks
Rename content within Power BI
Enroll your US Government organization
Delete almost anything in Power BI
Connect to services
Acumatica
Acumatica
Adobe Analytics
Alpine Metrics Sales Predictions
appFigures
Application Insights
AT Internet Bridge
Azure Audit Logs
Azure Mobile Engagement
Microsoft Azure Consumption Insights
Azure Search
Circuit ID
ClickDimensions
comScore Digital Analytix
GitHub
Google Analytics
Insightly
IntelliBoard
Lithium
MailChimp
Mandrill
Marketo
Microsoft Dynamics AX
Microsoft Dynamics CRM
Microsoft Dynamics NAV
Office365Mon
Planview Enterprise
Prevedere
Project Online
Projectplace
QuickBooks Online
Salesforce
SendGrid
ServiceNow Incidents
Smartsheet
SparkPost
SQL Database Auditing
SQL Sentry
Stripe
SweetIQ
Troux
Twilio
tyGraph
UserVoice
VMob
 Webtrends
Windows Dev Center
Xero
Zendesk
Ziosk
Zuora
Organizational content packs
Intro to organizational content packs
Create and publish a content pack
Copy, refresh, get access to content packs
Manage, update, delete content packs
Remove a connection to a content pack
Resources
Videos
Webinars
Supported languages and countries/regions
Whitepapers
Whitepapers overview
Power BI security whitepaper
Power BI premium deployment
Distribute Power BI externally using Azure Active Directory B2B
Power BI for developers
What can developers do with Power BI
Embedded Analytics
Overview
What is embedding with Power BI
What is Power BI Embedded in Azure
Quickstarts
Manage capacities in Azure
Create a capacity in Azure
Create a capacity using Multi-Geo in Azure
Scale a capacity in Azure
 Pause and start a capacity in Azure
Tutorials
Embed content for customers
Embed content for your organization
Embed content for national clouds
Concepts
Performance best practices
Service principal
Row-level security
Manage multi-tenants
Azure diagnostic logging for Power BI Embedded
Embedding FAQ
Power BI permissions
How to
Embed from an app
Create an Azure Active Directory tenant
Register an application
Get an Azure AD access token
Embedding Q&A
Manage capacities in Azure
Create a capacity in Azure
Create a capacity using Multi-Geo in Azure
Scale a capacity in Azure
Pause and start a capacity in Azure
Troubleshoot your embedded application
Migrate from Workspace Collections
How to migrate from Power BI Workspace Collections
Migration tool
Migration code snippets
Reference
APIs
Azure Resource Management REST APIs
 Power BI REST APIs
Power BI REST API Reference
.NET SDK Download
Embed custom layouts into an app
Resources
Dev Center
Embedding setup tool
JavaScript Playground Sample
Power BI JavaScript wiki
JavaScript Git Repo
Power BI C# Git Repo
Samples
Power BI community
Stack Overflow
Custom Visuals
Overview
Custom visuals in Power BI
Tutorials
Developing a Power BI custom visual
Adding formatting options
Concepts
Custom visuals for organizations in Power BI
Guidelines for Power BI visuals
Custom visuals FAQ
Using Capabilities
Data View Mappings
Objects and Properties
Advanced Edit Mode
Migrating to versioned API guide
How to
Get a custom visual certified
Publish custom visuals to AppSource
 Use R-powered custom visuals in Power BI
Troubleshoot
Troubleshoot developing custom visuals
Reference
APIs
Resources
Dev Center
Samples
Custom Visuals Git Repo
Automation
Overview
What can I do with the Power BI API?
Tutorials
Push data into a dataset
Register an app with Azure AD
Get an authentication access token
Create a dataset
Get a dataset to add rows
Add rows to a table
Concepts
Automatic retention policy for real-time data
Push data
Power BI REST API limitations
Dataset properties
Data model versioning
How to
Configure credentials
Encrypt credentials
Reference
REST APIs
Power BI REST API Reference
Complete code listing
 Resources
Dev Center
Power BI C# Git Repo
.NET SDK Download
Power BI Report Server
Overview
What is Power BI Report Server?
Compare Power BI Report Server and the service
Tutorials
Explore Power BI Report Server in a VM
Concepts
What's new
Change log
Support timeline
Hardware and software requirements
Browser support
Administrator overview
Report server basics
Power BI report scheduled refresh
Power BI report data sources
Paginated report data sources
Subscriptions
Using the mobile app
Troubleshoot scheduled refresh
Report server for developers
Report server for developers
Report Viewer control
Develop extensions
Embed reports
How to
Install Power BI Desktop
Report server basics
 Create a Power BI report for a report server
Manage content in the report server
Row-level security (RLS) in the report server
Create a paginated report for a report server
Enter data directly in a paginated report
Work with KPIs
Access shared datasets as OData feeds
Configure scheduled refresh
Add comments to a report
Report server for admins
Install a report server
Find your product key
Upgrade a report server
Migrate a report server
Configure Kerberos to use Power BI reports
Configure mobile app access remotely
Host Excel workbooks
Reference
REST API
WMI
SOAP APIs
URL Access
Extensions
Resources
Capacity planning whitepaper
Gateways
Overview
What are Power BI gateways?
Tutorials
Connect to SQL Server data
Concepts
Guidance for deploying a data gateway
 On-premises data gateway FAQ
How to
Install gateways
Manage gateways
Manage your enterprise data source - Analysis Services
Manage your enterprise data source - SAP HANA
Manage your enterprise data source - SQL
Manage your data source - Oracle
Manage your enterprise data source - import/scheduled refresh
Merge on-premises and cloud data sources
Enable single sign-on (SSO)
Single sign-on (SSO) - overview
Single sign-on (SSO) - Kerberos
Single sign-on (SSO) - Kerberos - resource-based
Single sign-on (SSO) - SAML
Configuring proxy settings
High availability clusters for on-premises data gateway
On-premises data gateway
On-premises data gateway - in-depth
On-premises data gateway (personal mode)
Custom Connectors
Troubleshooting the on-premises data gateway
Administration
Overview
What is Power BI administration?
Concepts
Power BI Premium
What is Power BI Premium?
Premium capacity memory use, optimization
Purchase Power BI Premium
Monitor capacities with the app
Monitor capacities in the Admin portal
 Configure workloads
Restart a Premium capacity
Support for large datasets
Incremental refresh
Multi-Geo support
Connect to datasets with client applications and tools
Power BI Premium FAQ
Administration role in Office 365
Frequently asked questions (FAQ)
High availability and failover FAQ
How to
Licensing and sign-up
Licensing for your organization
Purchase Power BI Pro
Sign up with an Office 365 Trial
Add Power BI with an Office 365 partner
Using the admin portal
Where is my tenant located?
Find users that have signed in
Auditing Power BI
Track service health
Closing your Power BI account
Power BI and ExpressRoute
Using Azure AD B2B
Row-level security with Power BI
Power BI archived workspace
Configure mobile apps with Intune
Reference
PowerShell, REST APIs, and .NET SDK
Power BI cmdlets for PowerShell
Service URL reference
Resources
Power BI governance and deployment approaches
Power BI security
 What is Power BI Desktop?
1/14/2019 • 4 minutes to read • Edit Online

Power BI Desktop is a free application you can install on your local computer that lets you connect to,
transform, and visualize your data. With Power BI Desktop, you can connect to multiple different sources of
data, and combine them (often called modeling) into a data model that lets you build visuals, and collections of
visuals you can share as reports, with other people inside your organization. Most users who work on Business
Intelligence projects use Power BI Desktop to create reports, and then use the Power BI service to share
their reports with others.

The most common uses for Power BI Desktop are the following:
Connect to data
Transform and clean that data, to create a data model
Create visuals, such as charts or graphs, that provide visual representations of the data
Create reports that are collections of visuals, on one or more report pages
Share reports with others using the Power BI service
People most often responsible for such tasks are often considered data analysts (sometimes just referred to as
analysts) or Business Intelligence professionals (often referred to as report creators). However, many people
who don't consider themselves an analyst or a report creator use Power BI Desktop to create compelling
reports, or to pull data from various sources and build data models, which they can share with their coworkers
and organizations.
With Power BI Desktop you can create complex and visually rich reports, using data from multiple sources, all
in one report that you can share with others in your organization.

Connect to data
To get started with Power BI Desktop, the first step is to connect to data. There are many different data
sources you can connect to from Power BI Desktop. To connect to data, simply select the Home ribbon, then
select Get Data > More. The following image shows the Get Data window that appears, showing the many
categories to which Power BI Desktop can connect.

When you select a data type, you're prompted for information, such as the URL and credentials, necessary for
Power BI Desktop to connect to the data source on your behalf.
Once you connect to one or more data sources, you may want to transform the data so it's useful for you.

Transform and clean data, create a model

In Power BI Desktop, you can clean and transform data using the built-in Query Editor. With Query Editor
you can make changes to your data, such as changing a data type, removing columns, or combining data from
multiple sources. It's a little bit like sculpting - you can start with a large block of clay (or data), then shave
pieces off or add others as needed, until the shape of the data is how you want it.
Each step you take in transforming data (such as rename a table, transform a data type, or delete columns) is
recorded by Query Editor, and each time this query connects to the data source those steps are carried out so
that the data is always shaped the way you specified.
The following image shows the Query Settings pane for a query that has been shaped, and turned into a
model.

Once your data is how you want it, you can create visuals.
Create visuals
Once you have a data model, you can drag fields onto the report canvas to create visuals. A visual is a graphic
representation of the data in your model. The following visual shows a simple column chart.

There are many different types of visuals to choose from in Power BI Desktop. To create or change a visual, just
select the visual icon from the Visualizations pane. If you have a visual selected on the report canvas, the
selected visual changes to the type you selected. If no visual is selected, a new visual is created based on your
selection.

Create reports
More often, you'll want to create a collection of visuals that show various aspects of the data you have used to
create your model in Power BI Desktop. A collection of visuals, in one Power BI Desktop file, is called a report.
A report can have one or more pages, just like an Excel file can have one or more worksheets. In the following
image you see the first page of a Power BI Desktop report, named Overview (you can see the tab near the
bottom of the image). In this report, there are ten pages.
Share reports
Once a report is ready to share with others, you can Publish the report to the Power BI service, and make it
available to anyone in your organization who has a Power BI license. To publish a Power BI Desktop report, you
select the Publish button from the Home ribbon in Power BI Desktop.

Once you select Publish, Power BI Desktop connects you to the Power BI service using your Power BI
account, and then prompts you to select where in the Power BI service you would like to share the report, such
as your workspace, a team workspace, or some other location in the Power BI service. You must have a Power
BI license to share reports to the Power BI service.

Next steps
To get started with Power BI Desktop, the first thing you need is to download and install the application.
There are two ways to get Power BI Desktop:
Download Power BI Desktop from the web
Get Power BI Desktop from the Windows Store
 Quickstart: Connect to data in Power BI Desktop
1/21/2019 • 2 minutes to read • Edit Online

In this quickstart, you connect to data using Power BI Desktop, which is the first step in building data models and
creating reports.

If you're not signed up for Power BI, sign up for a free trial before you begin.

Prerequisites
To complete the steps in this article, you need the following:
Download and install Power BI Desktop, which is a free application that runs on your local computer. You can
download Power BI Desktop directly, or you can get it from the Microsoft Store.
Download this sample Excel workbook, and create a folder called C:\PBID -qs where you can store the Excel file.
Subsequent steps in this quickstart assume that is the file location for the downloaded Excel workbook.

Launch Power BI Desktop

Once you install Power BI Desktop, launch the application so it's running on your local computer. You're
presented with a blank canvas, which is where you create visuals and reports from data to which you connect.
Connect to data
With Power BI Desktop you can connect to many different types of data. You can connect to basic data sources
such as a Microsoft Excel file, and you can connect to online services that contain all sorts of data such as
Salesforce, Microsoft Dynamics, Azure Blob Storage, and many more.
To connect to data, from the Home ribbon select Get Data.

The Get Data window appears, where you can choose from the many different data sources to which Power BI
Desktop can connect. In this quickstart we use the Excel workbook that you downloaded, described in the
Prerequisites section at the beginning of this article.
Since this is an Excel file, we select Excel from the Get Data window, then select the Connect button.
We're prompted to provide the location of the Excel file to which we want to connect. The downloaded file is called
Financial Sample so we select that file, and then select Open.

Power BI Desktop then loads the workbook and reads its contents, and shows you the available data in the file
using the Navigator window, where you can choose which data you would like to load into Power BI Desktop. You
select the tables by marking the checkboxes beside each table you want to import. In this case, we'll import both
available tables.

Once you've made your selections, select Load to import the data into Power BI Desktop.

View data in the Fields pane

Once you've loaded the tables, the Fields pane shows you the data. You can expand each table by selecting the
triangle beside its name. In the following image, the financials table is expanded, showing each of its fields.
And that's it! You've connected to data in Power BI Desktop, loaded that data, and now you can see all the
available fields within those tables.

Next steps
There are all sorts of things you can do with Power BI Desktop once you've connected to data, such as creating
visuals and reports. Take a look at the following resource to get you going:
Getting Started Guide for Power BI Desktop
 Tutorial: Shape and combine data in Power BI
Desktop
1/14/2019 • 15 minutes to read • Edit Online

With Power BI Desktop, you can connect to many different types of data sources, then shape the data to meet
your needs, enabling you to create visual reports that you can share with others. Shaping data means
transforming the data – such as renaming columns or tables, changing text to numbers, removing rows, setting
the first row as headers, and so on. Combining data means connecting to two or more data sources, shaping
them as needed, then consolidating them into one useful query.
In this tutorial, you'll learn to:
Shape data using Query Editor
Connect to a data source
Connect to another data source
Combine those data sources, and create a data model to use in reports
This tutorial demonstrates how to shape a query using Power BI Desktop, highlighting some of the most
common tasks. The query used here is described in more detail, including how to create the query from
scratch, in Getting Started with Power BI Desktop.
It’s useful to know that the Query Editor in Power BI Desktop makes ample use of right-click menus, as well
as the ribbon. Most of what you can select in the Transform ribbon is also available by right-clicking an item
(such as a column) and choosing from the menu that appears.

Shape data
When you shape data in the Query Editor, you’re providing step-by-step instructions (that Query Editor carries
out for you) to adjust the data as Query Editor loads and presents it. The original data source is not affected;
only this particular view of the data is adjusted, or shaped.
The steps you specify (such as rename a table, transform a data type, or delete columns) are recorded by Query
Editor, and each time this query connects to the data source those steps are carried out so that the data is
always shaped the way you specify. This process occurs whenever you use the Query Editor feature of Power BI
Desktop, or for anyone who uses your shared query, such as on the Power BI service. Those steps are
captured, sequentially, in the Query Settings pane, under Applied Steps.
The following image shows the Query Settings pane for a query that has been shaped – we’ll go through
each of those steps in the next few paragraphs.
Using the retirement data from Getting Started with Power BI Desktop, which we found by connecting to a
Web data source, let’s shape that data to fit our needs.
For starters, let's add a custom column to calculate rank based on all data being equal factors and compare this
to the existing column Rank. Here's the Add Column ribbon, with an arrow pointing toward the Custom
Column button, which lets you add a custom column.

In the Custom Column dialog, in New column name, enter New Rank, and in Custom column formula,
enter the following:

([Cost of living] + [Weather] + [Health care quality] + [Crime] + [Tax] + [Culture] + [Senior] + [#"Well-
being"]) / 8

Make sure the status message reads 'No syntax errors have been detected.' and click OK.
To keep column data consistent, lets transform the new column values to whole numbers. Just right-click the
column header, and select Change Type > Whole Number to change them.
If you need to choose more than one column, first select a column then hold down SHIFT, select additional
adjacent columns, and then right-click a column header to change all selected columns. You can also use the
CTRL key to choose non-adjacent columns.
You can also transform column data types from the Transform ribbon. Here’s the Transform ribbon, with an
arrow pointing toward the Data Type button, which lets you transform the current data type to another.

Note that in Query Settings, the Applied Steps reflect any shaping steps applied to the data. If I want to
remove any step from the shaping process, I simply select the X to the left of the step. In the following image,
Applied Steps reflects the steps so far: connecting to the website ( Source); selecting the table (Navigation);
and while loading the table, Query Editor automatically changed text-based number columns from Text to
Whole Number (Changed Type). The last two steps show our previous actions with Added Custom and
Changed Type1.

Before we can work with this query, we need to make a few changes to get its data where we want it:
Adjust the rankings by removing a column - we have decided Cost of living is a non-factor in our results.
After removing this column, we find the issue that the data remains unchanged, though it's easy to fix using
Power BI Desktop, and doing so demonstrates a cool feature of Applied Steps in Query.
Fix a few errors – since we removed a column, we need to readjust our calculations in the New Rank
column. This involves changing a formula.
Sort the data - based on the New Rank and Rank columns.
Replace data - we will highlight how to replace a specific value and the need of inserting an Applied Step.
Change the table name – that Table 0 is not a useful descriptor, but changing it is simple.
To remove the Cost of living column, simply select the column and choose the Home tab from the ribbon,
then Remove Columns as shown in the following figure.
Notice the New Rank values have not changed; this is due to the ordering of the steps. Since Query Editor
records the steps sequentially, yet independently of each other, you can move each Applied Step up or down
in the sequence. Just right-click any step, and Query Editor provides a menu that lets you do the following:
Rename, Delete, Delete Until End (remove the current step, and all subsequent steps too), Move Up, or
Move Down. Go ahead and move up the last step Removed Columns to just above the Added Custom step.

Next, select the Added Custom step. Notice the data now shows Error which we will need to address.
There are a few ways to get more information about each error. You can select the cell (without clicking on the
word Error), or click the word Error directly. If you select the cell without clicking directly on the word Error,
Query Editor displays the error information on the bottom of the window.

If you click the word Error directly, Query creates an Applied Step in the Query Settings pane and displays
information about the error. We do not want to go this route, so select Cancel.
To fix the errors, select the New Rank column, then display the column's data formula by opening the View
ribbon and selecting the Formula Bar checkbox.
Now you can remove the Cost of living parameter and decrement the divisor, by changing the formula to the
following:

Table.AddColumn(#"Removed Columns", "New Rank", each ([Weather] + [Health care quality] + [Crime] + [Tax] +
[Culture] + [Senior] + [#"Well-being"]) / 7)

Select the green checkmark to the left of the formula box or press Enter, and the data should be replaced by
revised values and the Added Custom step should now complete with no errors.

NOTE
You can also Remove Errors (using the ribbon or the right-click menu), which removes any rows that have errors. In this
case it would’ve removed all the rows from our data, and we didn’t want to do that – we like all our data, and want to
keep it in the table.

Now we need to sort the data based on the New Rank column. First select the last applied step, Changed
Type1 to get to the most recent data. Then, select drop-down located next to the New Rank column header
and select Sort Ascending.
Notice the data is now sorted according to New Rank. However, if you look in the Rank column, you will
notice the data is not sorted properly in cases where the New Rank value is a tie. To fix this, select the New
Rank column and change the formula in the Formula Bar to the following:

= Table.Sort(#"Changed Type1",{{"New Rank", Order.Ascending},{"Rank", Order.Ascending}})

Select the green checkmark to the left of the formula box or press Enter, and the rows should now be ordered
in accordance with both New Rank and Rank.
In addition, you can select an Applied Step anywhere in the list, and continue shaping the data at that point in
the sequence. Query Editor will automatically insert a new step directly after the currently selected Applied
Step. Let's give that a try.
First, select the Applied Step prior to adding the custom column; this would be the Removed Columns step.
Here we will replace the value of the Weather ranking in Arizona. Right-click the appropriate cell that contains
Arizona's Weather ranking and select Replace Values... from the menu that appears. Note which Applied Step
is currently selected (the step prior to the Added Custom step).
Since we're inserting a step, Query Editor warns us about the danger of doing so - subsequent steps could
cause the query to break. We need to be careful, and thoughtful! Since this is a tutorial, and we're highlighting a
really cool feature of Query Editor to demonstrate how you can create, delete, insert, and reorder steps, we'll
push ahead and select Insert.

Change the value to 51 and the data for Arizona is replaced. When you create a new Applied Step, Query
Editor names it based on the action - in this case, Replaced Value. When you have more than one step with
the same name in your query, Query Editor adds a number (in sequence) to each subsequent Applied Step to
differentiate between them.
Now select the last Applied Step, Sorted Rows, and notice the data has changed regarding Arizona's new
ranking. This is because we inserted the Replaced Value step in the right place, before the Added Custom step.
Okay that was a little involved, but it was a good example of how powerful and versatile Query Editor can be.
Lastly, we want to change the name of that table to something descriptive. When we get to creating reports, it’s
especially useful to have descriptive table names, especially when we connect to multiple data sources, and
they’re all listed in the Fields pane of the Report view.
Changing the table name is easy: in the Query Settings pane, under Properties, simply type in the new name
of the table, as shown in the following image, and hit Enter. Let’s call this table RetirementStats.
Okay, we’ve shaped that data to the extent we need to. Next let’s connect to another data source, and combine
data.

Combine data
That data about various states is interesting, and will be useful for building additional analysis efforts and
queries. But there’s one problem: most data out there uses a two-letter abbreviation for state codes, not the full
name of the state. We need some way to associate state names with their abbreviations.
We’re in luck: there’s another public data source that does just that, but it needs a fair amount of shaping
before we can connect it to our retirement table. Here’s the Web resource for state abbreviations:
http://en.wikipedia.org/wiki/List_of_U.S._state_abbreviations
From the Home ribbon in Query Editor, we select New Source > Web and type the address, select Connect,
and the Navigator shows what it found on that Web page.
We select Codes and abbreviations... because that includes the data we want, but it’s going to take quite a bit
of shaping to pare that table’s data down to what we want.

TIP
Is there a faster or easier way to accomplish the steps below? Yes, we could create a relationship between the two tables,
and shape the data based on that relationship. The following steps are still good to learn for working with tables, just
know that relationships can help you quickly use data from multiple tables.

To get this data into shape, we take the following steps:

Remove the top row – it's a result of the way that Web page’s table was created, and we don’t need it. From
the Home ribbon, select Reduce Rows > Remove Rows > Remove Top Rows.
The Remove Top Rows window appears, letting you specify how many rows you want to remove.

NOTE
If Power BI accidentally imports the table headers as a row in your data table, you can select Use First Row As Headers
from the Home tab, or from the Transform tab in the ribbon, to fix your table.

Remove the bottom 26 rows – they’re all the territories, which we don’t need to include. From the Home
ribbon, select Reduce Rows > Remove Rows > Remove Bottom Rows.

Since the RetirementStats table doesn't have information for Washington DC, we need to filter it from our
list. Select the drop-down arrow beside the Region Status column, then clear the checkbox beside Federal
district.
 Remove a few unneeded columns – we only need the mapping of state to its official two-letter abbreviation,
so we can remove the following columns: Column1, Column3, Column4, and then Column6 through
Column11. First select Column1, then hold down the CTRL key and select the other columns to be
removed (this lets you select multiple, non-contiguous columns). From the Home tab on the ribbon, select
Remove Columns > Remove Columns.

NOTE
This is a good time to point out that the sequence of applied steps in Query Editor is important, and can affect how the
data is shaped. It’s also important to consider how one step may impact another subsequent step; if you remove a step
from the Applied Steps, subsequent steps may not behave as originally intended, because of the impact of the query’s
sequence of steps.

NOTE
When you resize the Query Editor window to make the width smaller, some ribbon items are condensed to make the
best use of visible space. When you increase the width of the Query Editor window, the ribbon items expand to make the
most use of the increased ribbon area.
 Rename the columns, and the table itself – as usual, there are a few ways to rename a column; first select the
column, then either select Rename from the Transform tab on the ribbon, or right-click and select
Rename… from the menu that appears. The following image has arrows pointing to both options; you only
need to choose one.

Let’s rename them to State Name and State Code. To rename the table, just type the name into the Name box
in the Query Settings pane. Let’s call this table StateCodes.
Now that we’ve shaped the StateCodes table the way we want, let’s combine these two tables, or queries, into
one; since the tables we now have are a result of the queries we applied to the data, they’re often referred to as
queries.
There are two primary ways of combining queries – merging and appending.
When you have one or more columns that you’d like to add to another query, you merge the queries. When
you have additional rows of data that you’d like to add to an existing query, you append the query.
In this case, we want to merge queries. To get started, from the left pane of Query Editor we select the query
into which we want the other query to merge, which in this case is RetirementStats. Then select Combine >
Merge Queries from the Home tab on the ribbon.
You may be prompted to set the privacy levels, to ensure the data is combined without including or transferring
data you didn't want transferred.
Next the Merge window appears, prompting us to select which table we’d like merged into the selected table,
and then, the matching columns to use for the merge. Select State from the RetirementStats table (query), then
select the StateCodes query (easy in this case, since there’s only one other query – when you connect to many
data sources, there are many queries to choose from). When we select the correct matching columns – State
from RetirementStats, and State Name from StateCodes – the Merge window looks like the following, and the
OK button is enabled.

A NewColumn is created at the end of the query, which is the contents of the table (query) that was merged
with the existing query. All columns from the merged query are condensed into the NewColumn, but you can
select to Expand the table, and include whichever columns you want.
To Expand the merged table, and select which columns to include, select the expand icon ( ). The Expand
window appears.

In this case, we only want the State Code column, so we select only that column and then select OK. We clear
the checkbox from Use original column name as prefix because we don’t need or want that; if we leave that
selected, the merged column would be named NewColumn.State Code (the original column name, or
NewColumn, then a dot, then the name of the column being brought into the query).
 NOTE
Want to play around with how to bring in that NewColumn table? You can experiment a bit, and if you don’t like the
results, just delete that step from the Applied Steps list in the Query Settings pane; your query returns to the state
prior to applying that Expand step. It’s like a free do-over, which you can do as many times as you like until the expand
process looks the way you want it.

We now have a single query (table) that combined two data sources, each of which has been shaped to meet
our needs. This query can serve as a basis for lots of additional, interesting data connections – such as housing
cost statistics, demographics, or job opportunities in any state.
To apply changes and close Query Editor, select Close & Apply from the Home ribbon tab. The transformed
dataset appears in Power BI Desktop, ready to be used for creating reports.

Next steps
There are all sorts of things you can do with Power BI Desktop. For more information on its capabilities, check
out the following resources:
What is Power BI Desktop?
Query Overview with Power BI Desktop
Data Sources in Power BI Desktop
Connect to Data in Power BI Desktop
Common Query Tasks in Power BI Desktop
 Tutorial: Analyze web page data using Power BI
Desktop
1/14/2019 • 7 minutes to read • Edit Online

As a long-time soccer fan, you want to report on the UEFA European Championship (Euro Cup) winners over the
years. With Power BI Desktop, you can import this data from a web page into a report and create visualizations
that show the data. In this tutorial, you learn how to use Power BI Desktop to:
Connect to a web data source and navigate across its available tables,
Shape and transform data in the Power Query Editor,
Name a query and import it into a Power BI Desktop report, and
Create and customize a map and a pie chart visualization.

Connect to a web data source

You can get the UEFA winners data from the Results table on the UEFA European Football Championship
Wikipedia page at http://en.wikipedia.org/wiki/UEFA_European_Football_Championship.

Note that Web connections are only established using basic authentication. Web sites requiring authentication may
not work properly with the Web connector.
To import the data:
1. In the Power BI Desktop Home ribbon tab, drop down the arrow next to Get Data, and then select Web.
 NOTE
You can also select the Get Data item itself, or select Get Data from the Power BI Get started dialog, then select
Web from the All or Other section of the Get Data dialog box, and then select Connect.

2. In the From Web dialog box, paste the URL

http://en.wikipedia.org/wiki/UEFA_European_Football_Championship into the URL text box, and then select
OK.

After connecting to the Wikipedia web page, the Power BI Navigator dialog box shows a list of available
tables on the page. You can select any of the table names to preview its data. The Results[edit] table has the
data you want, although it is not exactly in the shape you want. You will reshape and clean up the data before
loading it into your report.
 NOTE
The Preview pane shows the most recent table selected, but all selected tables will load into the Power Query
Editor when you select Edit or Load.

3. Select the Results[edit] table in the Navigator list, and then select Edit.
A preview of the table opens in the Power Query Editor, where you can apply transformations to clean up
the data.

Shape data in Power Query Editor

You want to make the data easier to scan by displaying only the years and the countries that won. You can use the
Power Query Editor to perform these data shaping and cleansing steps.
First, remove all the columns except Year and Final Winners from the table.
1. In the Power Query Editor grid, select the Year and Final Winners columns (hold down the Ctrl key to
select multiple items).
2. Right-click and select Remove Other Columns from the dropdown, or select Remove Columns >
Remove Other Columns from the Manage Columns group in the Home ribbon tab, to remove all other
columns from the table.

or

Next, remove the extra word Details from the Year column cells.
1. Select the Year column.
2. Right-click, and select Replace Values from the dropdown, or select Replace Values from the Transform
group in the Home tab of the ribbon (also found in the Any Column group in the Transform tab).
 or

3. In the Replace Values dialog box, type Details in the Value To Find text box, leave the Replace With text
box empty, and then select OK to delete the word "Details" from the Year entries.

Some Year cells only contain the word "Year" rather than year values. You can filter the Year column to only display
rows that do not contain the word "Year".
1. Select the filter drop-down arrow on the Year column.
2. In the drop-down, scroll down and clear the checkbox next to the Year option, and then select OK, to remove
the rows that only have the word "Year" in the Year column.
Now that you have cleaned up the data in the Year column, you can work on the Final Winner column. Since you
are only looking at the final winners data now, you can rename this column to Country. To rename the column:
1. Double-click or tap and hold in the Final Winner column header, or
Right-click the Final Winners column header, and select Rename from the dropdown, or
Select the Final Winners column and select Rename from the Any Column group in the Transform
tab of the ribbon.

or
2. Type Country in the header and press Enter to rename the column.
You also want to filter out rows like "2020" that have null values in the Country column. You could use the filter
menu as you did with the Year values, or you can:
1. Right-click on the Country cell in the 2020 row, which has the value null.
2. Select Text Filters > Does not Equal in the context menu to remove any rows that contain that cell's value.

Import the query into Report View

Now that you've shaped the data the way you want, you're ready to name your query "Euro Cup Winners" and
import it into your report.
1. In the Query Settings pane, in the Name text box, type Euro Cup Winners, and then press Enter.

2. Select Close & Apply > Close & Apply from the Home tab of the ribbon.

The query loads into the Power BI Desktop Report View, where you can see it in the Fields pane.
 TIP
You can always get back to the Power Query Editor to edit and refine your query by:
Selecting the More options ellipsis (...) next to Euro Cup Winners in the Fields pane, and selecting Edit Query from the
dropdown, or
Selecting Edit Queries > Edit Queries in the External data group of the Home ribbon tab in Report view.

Create a visualization
To create a visualization based on your data:
1. Select the Country field in the Fields pane, or drag it to the report canvas. Power BI Desktop recognizes the
data as country names, and automatically creates a Map visualization.

2. Enlarge the map by dragging the handles in the corners so all the winning country names are visible.
3. The map shows identical data points for every country that won a Euro Cup tournament. To make the size of
each data point reflect how often the country has won, drag the Year field to Drag data fields here under
Size in the lower part of the Visualizations pane. The field automatically changes to a Count of Year
measure, and the map visualization now shows larger data points for countries that have won more
tournaments.

Customize the visualization

As you can see, it is very easy to create visualizations based on your data. It's also easy to customize your
visualizations to better present the data in ways that you want.
Format the map
You can change the appearance of a visualization by selecting it and then selecting the Format (paint roller) icon in
the Visualizations pane. For example, the "Germany" data point(s) in your visualization could be misleading,
because West Germany won two tournaments and Germany won one, and the map superimposes the two points
rather than separating or adding them together. You can color these two points differently to highlight this. You can
also give the map a more descriptive and attractive title.
1. With the visualization selected, select the Format icon, and then select Data colors to expand the data color
options.

2. Turn Show All to On, and then select the dropdown next to West Germany and choose a yellow color.

3. Select Title to expand the title options, and in the Title text field, type Euro Cup Winners in place of the
current title.
4. Change Font color to red, Text size to 12, and Font family to Segoe (Bold).
Your map visualization now looks like this:

Change the visualization type

You can change the type of a visualization by selecting it and then selecting a different icon at the top of the
Visualization pane. For example, your map visualization is missing the data for the Soviet Union and
Czechoslovakia, because those countries no longer exist on the world map. Another type of visualization like a
treemap or pie chart may be more accurate, because it shows all the values.
To change the map to a pie chart, select the map and then select the Pie chart icon in the Visualization pane.
 TIP
You can use the Data colors formatting options to make "Germany" and "West Germany" the same color.
To group the countries with the most wins together on the pie chart, select the ellipsis ( ...) at the upper right of the
visualization, and then select Sort by Count of Year from the dropdown.

Power BI Desktop provides a seamless end-to-end experience, from getting data from a wide range of data sources
and shaping it to meet your analysis needs, to visualizing this data in rich and interactive ways. Once your report is
ready, you can upload it to Power BI and create dashboards based on it, which you can share with other Power BI
users.

See also
Read other Power BI Desktop tutorials
Watch Power BI Desktop videos
Visit the Power BI Forum
Read the Power BI Blog
 Tutorial: Combine sales data from Excel and an
OData feed
1/14/2019 • 11 minutes to read • Edit Online

It's common to have data spread across multiple data sources, such as product information in one database and
sales information in another. With Power BI Desktop, you can combine data from different sources to create
interesting, compelling data analyses and visualizations.
In this tutorial, you learn how to combine data from two data sources: an Excel workbook that includes product
information, and an OData feed that contains orders data. After you import each dataset and perform
transformation and aggregation steps, you use data from both sources to produce a sales analysis report with
interactive visualizations. These techniques can also be applied to SQL Server queries, CSV files, and any other
data sources in Power BI Desktop.

NOTE
In Power BI Desktop, there are often a few ways to accomplish a task. For example, many ribbon selections are also available
by using a right-click or More options menu on a column or cell. Several alternate methods are described in the steps below.

Import the product data from Excel

First, import the product data from the Excel Products.xlsx workbook into Power BI Desktop.
1. Download the Products.xlsx Excel workbook, and save it as Products.xlsx.
2. Select the dropdown arrow next to Get Data in the Home tab of the Power BI Desktop ribbon, and then
select Excel from the Most Common dropdown.
 NOTE
You can also select the Get Data item itself, or select Get Data from the Power BI Get started dialog, then select
Excel or File > Excel in the Get Data dialog box, and then select Connect.

3. In the Open dialog box, navigate to and select the Products.xlsx file, and then select Open.
4. In the Navigator pane, select the Products table and then select Edit.

A preview of the table opens in the Power Query Editor, where you can apply transformations to clean up the
data.

NOTE
You can also open the Power Query Editor by selecting Edit Queries > Edit Queries from the Home ribbon in Power BI
Desktop, or by right-clicking or choosing More options next to any query in Report View, and selecting Edit Query.

Clean up the products columns

Your combined report will only use the ProductID, ProductName, QuantityPerUnit, and UnitsInStock
columns from the Excel workbook, so you can remove the other columns.
1. In Power Query Editor, select the ProductID, ProductName, QuantityPerUnit, and UnitsInStock
columns (use Ctrl+Click to select more than one column, or Shift+Click to select columns that are next to
each other).
2. Right-click any of the selected headers and select Remove Other Columns from the dropdown, to remove
all except the selected columns from the table. You can also select Remove Columns > Remove Other
Columns from the Manage Columns group in the Home ribbon tab.

Import the order data from an OData feed

Next, import the order data from the sample Northwind sales system OData feed.
1. In Power Query Editor, select New Source and then select OData feed from the Most Common
dropdown.
2. In the OData Feed dialog box, paste the URL for the Northwind OData feed,
http://services.odata.org/V3/Northwind/Northwind.svc/ , and select OK.

3. In the Navigator pane, select the Orders table, and then select OK to load the data into Power Query
Editor.

NOTE
In Navigator, you can select any table name, without selecting the checkbox, to see a preview.

Expand the order data

When you connect to data sources that have multiple tables, such as relational databases or the Northwind OData
feed, you can use references between tables to build up your queries. The Orders table contains references to
several related tables. You can add the ProductID, UnitPrice, and Quantity columns from the related
Order_Details table into the subject (Orders) table by using the Expand operation.
1. Scroll to the right in the Orders table until you can see the Order_Details column. Note that instead of data,
 it contains references to another table.

2. Select the Expand icon ( ) in the Order_Details column header.

3. In the Expand drop-down:
a. Select (Select All Columns) to clear all columns.
b. Select ProductID, UnitPrice, and Quantity, and then select OK.

After you expand the Order_Details table, the Order_Details column is replaced by the three new columns from
the nested table, and there are new rows in the table for the added data from each order.

Create a custom calculated column

Power Query Editor lets you create calculations and custom fields to enrich your data. You will create a custom
column that calculates the total price for each line item in an order by multiplying the unit price by item quantity.
1. In the Add Column ribbon tab of Power Query Editor, select Custom Column.
2. In the Custom Column dialog box, type LineTotal in the New column name field.
3. In the Custom column formula field after the = , enter [Order_Details.UnitPrice] *
[Order_Details.Quantity]. (You can also select the field names from the Available columns scroll box and
select << Insert, instead of typing them.)
4. Select OK.

The new LineTotal field appears as the last column in the Orders table.

Set the data type for the new field

When Power Query Editor connects to data, it determines the best data type for each field and displays the data
accordingly. You can see the data types assigned to fields by the icons in the headers, or under Data Type in the
Transform group of the Home ribbon tab.
Your new LineTotal column has a data type of Any, but its values are currency. To assign a data type, right-click the
LineTotal column header, select Change Data Type from the dropdown, and then select Fixed decimal number.
 NOTE
You can also select the LineTotal column, then select the dropdown arrow next to Data Type in the Transform area of the
Home ribbon tab, and then select Fixed decimal number.

Clean up the orders columns

To make your model easier to work with in reports, you can delete, rename, and reorder some of the columns.
Your report will only use the OrderDate, ShipCity, ShipCountry, Order_Details.ProductID,
Order_Details.UnitPrice, and Order_Details.Quantity columns. You can select these columns and use Remove
Other Columns as you did with the Excel data, or you can select all the columns except those listed, right-click on
one of the selected columns, and select Remove Columns to remove them all.
You can make the Order_Details.ProductID, Order_Details.UnitPrice and Order_Details.Quantity columns
easier to identify by removing the Order_Details. prefixes from the column names. To rename the columns to
ProductID, UnitPrice and Quantity, respectively:
1. Double-click or tap and hold each column header, or right-click the column header and select Rename from the
dropdown.
2. Delete the Order_Details. prefix from each name, and then press Enter.
Finally, to make the LineTotal column easier to access, drag and drop it to the left, just to the right of the
ShipCountry column.
Review the query steps
As you shaped and transformed data in the Power Query Editor, each step was recorded in the Applied Steps area
of the Query Settings pane on the right side of Power Query Editor. You can step back through the Applied Steps
to review the changes you made, and edit, delete, or rearrange them if necessary (although this can be risky,
because changing preceding steps can break later steps).
Select each of your queries in the Queries list on the left side of Power Query Editor, and review the Applied
Steps in Query Settings. After applying the previous data transformations, the Applied Steps for your two queries
should look like the following:

TIP
Underlying the Applied Steps are formulas written in the Power Query Language, also known as the M language. To see
and edit the formulas, select Advanced Editor in the Query group of the Home tab of the ribbon.

Import the transformed queries

When you are satisfied with your transformed data, select Close & Apply > Close & Apply in the Close group of
the Home ribbon tab, to import the data into Power BI Desktop Report View.
Once the data is loaded, the queries appear in the Fields list in the Power BI Desktop Report View .

Manage the relationship between the datasets

Power BI Desktop does not require you to combine queries to report on them. However, you can use the
relationships between datasets, based on fields they have in common, to extend and enrich your reports. Power BI
Desktop may detect relationships automatically, or you can create them in the Power BI Desktop Manage
Relationships dialog. For more details about relationships in Power BI Desktop, see Create and manage
relationships.
The Orders and Products datasets in this tutorial share a common ProductID field, so there is a relationship
between them based on that column.
1. In Power BI Desktop Report View, select Manage Relationships in the Relationships area of the Home
ribbon tab.

2. In the Manage Relationships dialog, note that Power BI Desktop has already detected and listed an active
relationship between the Products and Orders tables. To view the relationship, select Edit.
 The Edit Relationship dialog opens, showing details about the relationship.

3. Power BI Desktop has autodetected the relationship correctly, so you can select Cancel and then Close to
exit the relationship dialogs.
You can also view and manage the relationships between your queries by selecting the Relationship view at the
left side of the Power BI Desktop window. Double-click the arrow on the line connecting the two queries to open
the Edit Relationship dialog and view or change the relationship.

To get back to Report View from Relationships View, select the Report View icon.

Create visualizations using your data

In Power BI Desktop Report View, you can create a variety of visualizations to gain insights from your data. You can
build reports with multiple pages, and each page can have multiple visuals. You and others can interact with your
visualizations to help analyze and understand your data. For more information about viewing and editing reports
in Power BI Service (your site), see Edit a Report.
You can use both of your data sets, and the relationship between them, to help visualize and analyze your sales
data.
First, create a stacked column chart that uses fields from both queries to show the quantity of each product
ordered.
1. Select the Quantity field from Orders in the Fields pane at the right, or drag it onto a blank space on the
canvas. This creates a stacked column chart showing the total quantity of all products ordered.
2. Select ProductName from Products in the Fields pane, or drag it onto the chart, to show the quantity of
each product ordered.
3. To sort the products by most to least ordered, select the More options ellipsis (...) at the upper right of the
 visualization, and then select Sort By Quantity.
4. Use the handles at the corners of the chart to enlarge it so more product names are visible.

Next, create a chart showing order dollar amounts ( LineTotal) over time (OrderDate).
1. With nothing selected on the canvas, select LineTotal from Orders in the Fields pane, or drag it to a blank
space on the canvas. The stacked column chart shows the total dollar amount of all orders.
2. With the chart selected, select OrderDate from Orders, or drag it onto the chart. The chart now shows line
totals for each order date.
3. Resize the visualization by dragging the corners to be able to see more data.

TIP
If you only see Years on the chart (only three data points), drop down the arrow next to OrderDate in the Axis field
of the Visualizations pane, and select OrderDate instead of Date Hierarchy.

Finally, create a map visualization showing order amounts from each country.
1. With nothing selected on the canvas, select ShipCountry from Orders in the Fields pane, or drag it to a
blank space on the canvas. Power BI Desktop detects that the data is country names, and automatically
creates a map visualization, with a data point for each country that had orders.
2. To make the sizes of the data points reflect the order amounts for each country, drag the LineTotal field
onto the map (or drag it to Drag data fields here under Size, in the bottom half of the Visualizations
pane). The sizes of the circles on the map now reflect the dollar amounts of the orders from each country.
Interact with your report visuals to analyze further
Power BI Desktop lets you uncover further trends by interacting with visuals that cross-highlight and filter each
other. For more information, see Filtering and Highlighting in Reports.
Because of the relationship between your queries, interactions with one visualization will affect all the other
visualizations on the page.
On the map visualization, select the circle centered in Canada. Note that the other two visualizations filter to
highlight the line totals and order quantities just for Canada.
If you select one of the products in the Quantity by ProductName chart, the map and the date chart filter to
reflect the data for that product, and if you select one of the dates in the LineTotal by OrderDate chart, the map
and the product chart filter to show the data for that date.

TIP
To deselect a selection, select it again, or select one of the other visualizations.

Complete the sales analysis report

Your completed report combines data from the Products.xlsx Excel file and the Northwind OData feed in visuals
that help analyze order information for different countries, timeframes, and products. When your report is ready,
you can upload it to Power BI service to share it with other Power BI users.

Next steps
Read other Power BI Desktop tutorials
Watch Power BI Desktop videos
Visit the Power BI Forum
Read the Power BI Blog
 Tutorial: Create your own measures in Power BI
Desktop
1/14/2019 • 10 minutes to read • Edit Online

You can create some of the most powerful data analysis solutions in Power BI Desktop by using measures.
Measures help you by performing calculations on your data as you interact with your reports. This tutorial will
guide you through understanding measures and creating your own basic measures in Power BI Desktop.
Prerequisites
This tutorial is intended for Power BI users already familiar with using Power BI Desktop to create more
advanced models. You should already be familiar with using Get Data and Query Editor to import data,
working with multiple related tables, and adding fields to the Report Canvas. If you’re new to Power BI
Desktop, be sure to check out Getting Started with Power BI Desktop.
Download the Contoso Sales Sample for Power BI Desktop file, which includes online sales data from the
fictitious company Contoso, Inc. This data was imported from a database, so you won’t be able to connect
to the datasource or view it in Query Editor. Extract the file on your own computer, and then open it in
Power BI Desktop.

Understand measures
Measures are most often created for you automatically. In the Contoso Sales Sample file, select the checkbox next
to the SalesAmount field in the Sales table in the Fields well, or drag SalesAmount onto the report canvas. A
new column chart visualization appears, showing the sum total of all values in the SalesAmount column of the
Sales table.

Any field that appears in the Fields well with a sigma icon is numeric, and its values can be aggregated. Rather
than showing a table with all two million rows of SalesAmount values, Power BI Desktop detected a numeric
datatype and automatically created and calculated a measure to aggregate the data. Sum is the default
aggregation for a numeric datatype, but you can easily apply different aggregations like average or count.
Understanding aggregations is fundamental to understanding measures, because every measure performs some
type of aggregation.
To change the chart aggregation to average, in the Value area of the Visualizations pane, click the down arrow
next to SalesAmount and select Average. The visualization changes to an average of all sales values in the
SalesAmount field.

You can change the type of aggregation depending on the result you want, but not all types of aggregation apply
to every numeric datatype. For example, for the SalesAmount field, Sum and Average make sense. Minimum and
Maximum have their place as well. But Count won’t really make much sense for the SalesAmount field, because
while its values are numeric, they’re really currency.
Values calculated from measures change in response to your interactions with your report. For example, dragging
the RegionCountryName field from the Geography table to your chart shows the average sales amounts for
each country.

When the result of a measure changes because of an interaction with your report, you have affected your
measure’s context. Every time you interact with your report visualizations, you are changing the context in which a
measure calculates and displays its results.

Create and use your own measures

In most cases, Power BI automatically calculates and returns values according to the types of fields and
aggregations you choose, but in some cases you might want to create your own measures to perform more
complex, unique calculations. With Power BI Desktop, you can create your own measures with the Data Analysis
Expressions (DAX) formula language.
DAX formulas use many of the same functions, operators, and syntax as Excel formulas. However, DAX functions
are designed to work with relational data and perform more dynamic calculations as you interact with your
reports. There are over 200 DAX functions that do everything from simple aggregations like sum and average to
more complex statistical and filtering functions. There are many resources to help you learn more about DAX.
After you've finished this tutorial, be sure to see DAX basics in Power BI Desktop.
When you create your own measure, it's added to the Fields list for the table you select and is called a model
measure. Some advantages of model measures are that you can name them whatever you want, making them
more identifiable; you can use them as arguments in other DAX expressions; and you can make them perform
complex calculations very quickly.

TIP
Starting with the February 2018 release of Power BI Desktop, many common calculations are available as quick measures,
which write the DAX formulas for you based on your inputs to a dialog box. These quick, powerful calculations are also great
for learning DAX or seeding your own customized measures. To create or explore quick measures, select New quick
measure in a table's More options list or under Calculations in the Home tab of the ribbon. See Use quick measures for
more about creating and using quick measures.

Create a measure
You want to analyze your net sales by subtracting discounts and returns from total sales amounts. For whatever
context exists in your visualization, you need a measure that subtracts the sum of DiscountAmount and
ReturnAmount from the sum of SalesAmount. There's no field for Net Sales in the Fields list, but you have the
building blocks to create your own measure to calculate net sales.
1. Right-click the Sales table in the Fields well, or hover over the table and select the More options ellipsis
(...), and then select New Measure. This will save your new measure in the Sales table, where it will be
easier to find.

You can also create a new measure by selecting New Measure in the Calculations group on the Home tab
of the Power BI Desktop ribbon.
 TIP
When you create a measure from the ribbon, it could be created in any of the tables, but it will be easier to find if
you create it where you plan to use it. In this case, select the Sales table first to make it active, and then select New
Measure.

The formula bar appears along the top of the Report canvas, where you can rename your measure and
enter a DAX formula.

2. By default, a new measure is simply named Measure. If you don’t rename it, additional new measures will
be named Measure 2, Measure 3, and so on. You want your measures to be more identifiable, so highlight
Measure in the formula bar, and then type Net Sales.
3. Now you can begin entering your formula. After the equals sign, start to type Sum. As you type, a drop-
down suggestion list appears, showing all the DAX functions beginning with the letters you type. Scroll
down if necessary to select SUM from the list, and then press Enter.

An opening parenthesis appears, along with another drop-down suggestion list of all of the available
columns you can pass to the SUM function.
 Expressions always appear between opening and closing parentheses. Your expression will contain a single
argument to pass to the SUM function: the SalesAmount column. Begin typing "SalesAmount" until only
one value is left in the list: Sales(SalesAmount). The column name preceded by the table name is called the
fully-qualified name of the column. Fully-qualified column names make your formulas easier to read.

4. Select Sales[SalesAmount], and then type a closing parenthesis.

TIP
Syntax errors are most often caused by a missing or misplaced closing parenthesis.

5. To subtract the other two columns:

a. After the closing parenthesis for the first expression, type a space, a minus operator (-), and another
space.
b. Enter another SUM function, and start typing "DiscountAmount" until you can choose the
Sales[DiscountAmount] column as the argument. Add a closing parenthesis.
c. Type a space, another minus operator, space, another SUM function with Sales[ReturnAmount] as the
argument, and a closing parenthesis.

6. Press Enter or click the checkmark in the formula bar to complete and validate the formula. The validated
measure is now ready to use in the Field list for the Sales table.

If you run out of room for entering a formula or want it to be on separate lines, select the down chevron on the
right side of the formula bar to open up more space.
You can separate parts of your formula on different lines by pressing Alt-Enter, or move things over by using
Tab.

Use your measure in the report

Now you can add your Net Sales measure to the report canvas, and calculate net sales for whatever other fields
you add to the report. To look at net sales by country:
1. Select the Net Sales measure from the Sales table, or drag it onto the report canvas.
2. Select the RegionCountryName field from the Geography table, or drag it into the chart.

To see the difference between net sales and total sales by country, select the SalesAmount field or drag it into the
chart.
The chart now uses two measures: SalesAmount, which was summed automatically, and the Net Sales measure
you created. Each measure was calculated in the context of another field, RegionCountryName.
Use your measure with a slicer
You can add a slicer to further filter net sales and sales amounts by calendar year.
1. Click a blank area next to the chart, then in Visualizations, select the Table visualization. This creates a
blank table visualization on the report canvas.

2. Drag the Year field from the Calendar table into the new blank table visualization. Because Year is a
numeric field, Power BI Desktop sums up its values, but that doesn’t make much sense as an aggregation.

3. In Values in the Visualizations pane, select the down arrow next to Year, and then select Don't
summarize. The table now lists individual years.
4. Select the Slicer icon in the Visualizations pane to convert the table into a slicer.

5. Select any value in the Year slicer to filter the Net Sales and Sales Amount by Country chart
accordingly. The Net Sales and SalesAmount measures recalculate and display results in the context of the
selected Year field.

Use your measure in another measure

You want to find out which products have the highest net sales amount per unit sold, so you need a measure that
divides net sales by the quantity of units sold. You can create a new measure that divides the result of your Net
Sales measure by the sum of Sales[SalesQuantity].
1. Create a new measure named Net Sales per Unit in the Sales table.
2. In the formula bar, begin typing Net Sales. The suggestion list will show what you can add. Select [Net
Sales].

You can also reference measures by just typing an opening bracket ([). The suggestion list will show only
 measures to add to your formula.

3. Enter a space, a divide operator (/), another space, a SUM function, and then type Quantity. The
suggestion list shows all the columns with Quantity in the name. Select Sales[SalesQuantity], type the
closing parenthesis, and press ENTER or select the checkmark to validate your formula. The formula should
look like this:
Net Sales per Unit = [Net Sales] / SUM(Sales[SalesQuantity])

4. Select the Net Sales per Unit measure from the Sales table, or drag it onto a blank area in the report
canvas. The chart shows the net sales amount per unit over all products sold, which is not very informative.

5. For a different look, change the chart visualization type to Treemap.

6. Select the Product Category field, or drag it into the treemap or into the Group field of the Visualizations
pane. Now you have some good info!
7. Try removing the ProductCategory field, and dragging the ProductName field into the chart instead.

Ok, now we're just playing, but you have to admit that's cool! Experiment with other ways to filter and format the
visualization.

What you've learned

Measures give you a lot of power to get the insights you want from your data. You've learned how to create
measures by using the formula bar, name them whatever makes most sense, and find and select the right formula
elements by using the DAX suggestion lists. You've also been introduced to context, where the results of
calculations in measures change according to other fields or other expressions in your formula.

Next steps
To learn more about Power BI Desktop quick measures, which provide many common measure calculations
for you, see Use quick measures to easily perform common and powerful calculations.
If you want to take a deeper dive into DAX formulas and create some more advanced measures, see DAX
basics in Power BI Desktop. This article focuses on fundamental concepts in DAX, such as syntax, functions,
and a more thorough understanding of context.
Be sure to add the Data Analysis Expressions (DAX) Reference to your favorites. This is where you'll find
detailed info on DAX syntax, operators, and the over 200 DAX functions.
 Tutorial: Create calculated columns in Power BI
Desktop
1/14/2019 • 7 minutes to read • Edit Online

Sometimes the data you’re analyzing doesn’t contain a particular field you need to get the results you’re after. This
is where calculated columns come in. Calculated columns use Data Analysis Expressions (DAX) formulas to define
a column’s values, anything from putting together text values from a couple of different columns to calculating a
numeric value from other values. For example, let’s say your data has City and State fields, but you want a single
Location field that has both, like "Miami, FL". This is precisely what calculated columns are for.
Calculated columns are similar to measures in that both are based on DAX formulas, but they differ in how they
are used. You often use measures in a visualization's Values area, to calculate results based on other fields. You use
calculated columns as new Fields in the rows, axes, legends, and group areas of visualizations.
This tutorial will guide you through understanding and creating some calculated columns and using them in report
visualizations in Power BI Desktop.
Prerequisites
This tutorial is intended for Power BI users already familiar with using Power BI Desktop to create more
advanced models. You should already know how to use Get Data and the Power Query Editor to import
data, work with multiple related tables, and add fields to the Report canvas. If you’re new to Power BI
Desktop, be sure to check out Getting Started with Power BI Desktop.
The tutorial uses the Contoso Sales Sample for Power BI Desktop, the same sample used for the Create
your own measures in Power BI Desktop tutorial. This sales data from the fictitious company Contoso, Inc.
was imported from a database, so you won’t be able to connect to the data source or view it in the Power
Query Editor. Download and extract the file on your own computer, and then open it in Power BI Desktop.

Create a calculated column with values from related tables

In your Sales Report, you want to display product categories and subcategories as single values, like "Cell phones –
Accessories", "Cell phones – Smartphones & PDAs", and so on. There's no field in the Fields list that gives you that
data, but there is a ProductCategory field and a ProductSubcategory field, each in its own table. You can create
a calculated column that combines values from these two columns. DAX formulas can leverage the full power of
the model you already have, including relationships between different tables that already exist.

1. Select the More options ellipsis (...), or right-click, on the ProductSubcategory table in the Fields list, and
 then select New Column. This creates your new column in the ProductSubcategory table.

The formula bar appears along the top of the Report canvas, ready for you to name your column and enter a
DAX formula.

2. By default, a new calculated column is simply named Column. If you don’t rename it, additional new
columns will named Column 2, Column 3, and so on. You want your column to be more identifiable, so
since the Column name is already highlighted in the formula bar, rename it by typing
ProductFullCategory, and then type an equals (=) sign.
3. You want the values in your new column to start with the ProductCategory name. Because this column is in
a different but related table, you can use the RELATED function to help you get it.
After the equals sign, type r. A dropdown suggestion list shows all of the DAX functions beginning with the
letter R. Selecting each function shows a description of its effect. As you type, the suggestion list scales
closer to the function you need. Select RELATED, and then press Enter.
 An opening parenthesis appears, along with another suggestion list of the related columns you can pass to
the RELATED function, with descriptions and details on expected parameters.

4. You want the ProductCategory column from the ProductCategory table. Select
ProductCategory[ProductCategory], press Enter, and then type a closing parenthesis.

TIP
Syntax errors are most often caused by a missing or misplaced closing parenthesis, although sometimes Power BI
Desktop will add it for you.

5. You want dashes and spaces to separate the ProductCategories and ProductSubcategories in the new
values, so after the closing parenthesis of the first expression, type a space, ampersand (& ), double-quote
("), space, dash (-), another space, another double-quote, and another ampersand. Your formula should now
look like this:
ProductFullCategory = RELATED(ProductCategory[ProductCategory]) & " - " &
 TIP
If you need more room, select the down chevron on the right side of the formula bar to expand the formula editor. In
the editor, press Alt + Enter to move down a line, and Tab to move things over.

6. Enter an opening bracket ([), and then select the [ProductSubcategory] column to finish the formula.

You didn’t need to use another RELATED function to call the ProductSubcategory table in the second
expression, because you are creating the calculated column in this table. You can enter
[ProductSubcategory] with the table name prefix (fully-qualified) or without (non-qualified).
7. Complete the formula by pressing Enter or selecting the checkmark in the formula bar. The formula
validates, and the ProductFullCategory column name appears in the ProductSubcategory table in the
Fields list.

NOTE
In Power BI Desktop, calculated columns get a special icon in the field list, showing that they contain formulas. In the
Power BI service (your Power BI site), there’s no way to change formulas, so calculated columns don't have icons.

Use your new column in a report

Now you can use your new ProductFullCategory column to look at SalesAmount by ProductFullCategory.
1. Select or drag the ProductFullCategory column from the ProductSubcategory table onto the Report
canvas to create a table showing all ProductFullCategory names.
2. Select or drag the SalesAmount field from the Sales table into the table to show the Sales Amount for
each Product Full Category.

Create a calculated column that uses an IF function

The Contoso Sales Sample contains sales data for both active and inactive stores. You want to ensure that Active
store sales are clearly separated from Inactive store sales in your report by creating an Active StoreName field. In
the new Active StoreName calculated column, each Active store will appear with the store's full name, while
inactive stores will be grouped together under "Inactive".
Fortunately, the Stores table has a column named Status, with values of "On" for active stores and "Off" for
inactive stores, which we can use to create values for our new Active StoreName column. Your DAX formula will
use the logical IF function to test each store's Status and return a particular value depending on the result. If a
store's Status is "On", the formula will return the store's name. If it’s "Off", the formula will assign an Active
StoreName of "Inactive".
1. Create a new calculated column in the Stores table and name it Active StoreName in the formula bar.
2. After the = sign, begin typing IF. The suggestion list will show what you can add. Select IF.

3. The first argument for IF is a logical test of whether a store's Status is "On". Type an opening bracket [ ,
which lists columns from the Stores table, and select [Status].

4. Right after [Status], type ="On", and then type a comma (,) to end the argument. The tooltip suggests that
you now need to add a value to return when the result is TRUE.

5. If the store's status is "On", you want to show the store’s name. Type an opening bracket ([) and select the
[StoreName] column, and then type another comma. The tooltip now indicates that you need to add a
value to return when the result is FALSE.

6. You want the value to be Inactive, so type "Inactive", and then complete the formula by pressing Enter or
selecting the checkmark in the formula bar. The formula validates, and the new column's name appears in
the Stores table in the Fields list.
7. You can use your new Active StoreName column in visualizations just like any other field. To show
SalesAmounts by Active StoreName, select the Active StoreName field or drag it onto the canvas, and
then select the SalesAmount field or drag it into the table. In this table, active stores appear individually by
name, but inactive stores are grouped together at the end as Inactive.

What you've learned

Calculated columns can enrich your data and provide easier insights. You've learned how to create calculated
columns in the field list and formula bar, use suggestion lists and tooltips to help construct your formulas, call DAX
functions like RELATED and IF with the appropriate arguments, and use your calculated columns in report
visualizations.

Next steps
If you want to take a deeper dive into DAX formulas and create calculated columns with more advanced formulas,
see DAX Basics in Power BI Desktop. This article focuses on fundamental concepts in DAX, such as syntax,
functions, and a more thorough understanding of context.
Be sure to add the Data Analysis Expressions (DAX) Reference to your favorites. This is where you'll find detailed
info on DAX syntax, operators, and the over 200 DAX functions.
 Tutorial: Facebook analytics using Power BI Desktop
2/13/2019 • 9 minutes to read • Edit Online

In this tutorial you learn how to import data from Facebook and use it in Power BI Desktop. You'll connect and
import data from the Power BI Facebook page, apply transformations to the imported data, and use the data in
report visualizations.

Connect to a Facebook page

This tutorial uses data from the Microsoft Power BI Facebook page (https://www.facebook.com/microsoftbi). You
don't need any special credentials to connect and import data from this page except for a personal Facebook
account.
1. Open Power BI Desktop and select Get data in the Getting Started dialog, or in the Home ribbon tab,
select Get Data and then select More....
2. In the Get Data dialog, select Facebook from the Online Services group, and then select Connect.

A dialog appears to alert you to the risks of using a third-party service.

3. Select Continue. The Facebook dialog box appears.
4. Type or paste the page name microsoftbi into the Username text box, select Posts from the Connection
dropdown, and then select OK.

5. When prompted for credentials, sign in to your Facebook account, and allow Power BI access through your
account.

After connecting to the Power BI Facebook page, you see a preview of the page's Posts data.
Shape and transform the imported data
You want to see and show which posts have the most comments over time, but you notice in the Posts data
preview that the created_time data is hard to read and understand, and there is no comments data at all. You need
to perform some shaping and cleansing of the data to pull the most out of it. You can use the Power BI Desktop
Power Query Editor to edit the data, before or after importing it into Power BI Desktop.
Split the date/time column
First, separate the date and time values in the created_time column to be more readable.
1. In the Facebook data preview, select Edit.
 The Power BI Desktop Power Query Editor opens in a new window and displays the data preview from
the Power BI Facebook page.

2. Select the created_time column. Note that it is currently a Text data type, denoted by an ABC icon in the
column header. Right-click the header and select Split Column > By Delimiter in the dropdown, or select
Split Column > By Delimiter under Transform in the Home tab of the ribbon.

3. In the Split column by delimiter dialog, select Custom from the dropdown, enter T (the character that
starts the time part of the created_time values) in the input field, and select OK.
 The column splits into two columns that contain the strings before and after the T delimiter and are named
created_time.1 and created_time.2, respectively. Note that Power BI has automatically detected and
changed the data types to Date for the first column and Time for the second column, and formatted the
date and time values to be more readable.
4. Rename the columns by double-clicking each column header, or selecting each column and then selecting
Rename in the Any Column Group of the Transform tab in the ribbon, and typing new column headers
created_date and created_time, respectively.

Expand the nested column

Now that the date and time data are the way you want them, you'll expose comments data by expanding a nested
column.
1. Select the object_link column and then select the icon to open the Expand/Aggregate dialog. Select
connections, and then select OK.
 The column heading changes to object_link.connections.
2. Again select the icon at the top of the object_link.connections column, select comments, and then
select OK. The column heading changes to object_link.connections.comments.
3. Select the icon at the top of the object_link.connections.comments column, and this time select
Aggregate instead of Expand in the dialog box. Select # Count of id, and then select OK.

The column now displays the number of comments for each message.
4. Rename the Count of object_link.connections.comments.id column to Number of comments.
5. Select the down arrow next to the Number of comments header and select Sort Descending to see the
Posts sorted from most to fewest comments.

Review query steps

As you shaped and transformed data in the Power Query Editor, each step was recorded in the Applied Steps
area of the Query Settings pane at the right side of the Power Query Editor window. You can step back through
the Applied Steps to see exactly what changes you made, and edit, delete, or rearrange them if necessary (although
this can be risky, because changing preceding steps can break later steps).
After applying the data transformations so far, your Applied Steps should look like the following:
 TIP
Underlying the Applied Steps are formulas written in the Power Query Language, also known as the M language. To see
and edit the formulas, select Advanced Editor in the Query group of the Home tab of the ribbon.

Import the transformed data

When you are satisfied with the data, select Close & Apply > Close & Apply in the Home tab of the ribbon to
import it into Power BI Desktop.

A dialog displays the progress of loading the data into the Power BI Desktop data model.

Once the data is loaded, it appears in the Report view as a new Query in the Fields list.
Use the data in report visualizations
Now that you have imported data from the Facebook page, you can quickly and easily gain insights about your
data by using visualizations. Creating a visualization is easy; just select a field or drag it from the Fields list onto
the report canvas.
Create a bar chart
1. In Power BI Desktop Report view, select message from the field list, or drag it onto the canvas. A table
showing all post messages appears on the canvas.

2. With that table selected, also select Number of comments from the Fields list, or drag it into the table.
3. Select the Stacked bar chart icon in the Visualizations pane. The table changes to a bar chart showing the
number of comments per post.
4. Select the ellipsis (...) in the upper right of the visualization, and then select Sort by Number of comments
to sort the table by descending number of comments.

5. Note that the most comments were associated with Blank messages (these posts may have been stories,
links, videos, or other non-text content). To filter out the Blank row, select message (all) under Filters at the
bottom of the Visualizations pane, select Select All, and then select Blank to deselect it. The Filters entry
changes to message is not (Blank), and the Blank row disappears from the chart visualization.

Format the chart

The visualization is getting more interesting, but you can't see much of the post text in the chart. To show more of
the post text:
1. Using the handles on the chart visualization, resize the chart to be as large as possible.
2. With the chart selected, select the Format icon (paint roller) in the Visualizations pane.
3. Select the down arrow next to Y -axis, and drag the slider next to Maximum size all the way to the right
(50%).
4. Also reduce the Text size to 10 to fit more text.

The chart now shows more of the post content.

The X axis (number of comments) of the chart does not show exact values, and looks lost at the bottom of the
chart. You decide to use data labels instead.
1. Select the Format icon, and then select the slider next to X-axis to turn it Off.
2. Select the slider next to Data labels to turn them On. Now the chart shows the exact number of comments
for each post.

Edit the data type

That's better, but the data labels all have a .0 decimal place, which is distracting and misleading, since Number of
posts must be a whole number. You need to change the data type of the Number of posts column to Whole
Number.
1. To edit the data type, right-click Query1 in the Fields list, or hover over it and select the More options
ellipsis (...), and then select Edit Query. You can also select Edit Queries from the External data area of
the Home tab in the ribbon, and then select Edit Queries from the dropdown. The Power BI Desktop
Power Query Editor opens in a separate window.

2. In the Power Query Editor, select the Number of comments column, and change the data type to Whole
Number by either:
Selecting the 1.2 icon next to the Number of comments column header, and selecting Whole number
from the dropdown, or
Right-clicking the column header and selecting Change type > Whole Number, or
Selecting Data type: Decimal Number in the Transform group of the Home tab, or the Any Column
group of the Transform tab, and selecting Whole Number.
The icon in the column header changes to 123, denoting a Whole Number data type.
3. Select Close & Apply, or just Apply to apply the changes while keeping the Power Query Editor window
open. Once the changes load, the data labels on the chart become whole numbers.

Create a date slicer

You want to visualize the number of comments on posts over time. You can create a slicer visualization to filter the
chart data to different time frames.
1. Click a blank area of the canvas, and then select the Slicer icon in the Visualizations pane. A blank slicer
visualization appears.
2. Select the created_date field from the Fields list, or drag it into the new slicer. The slicer changes to a date
range slider, based on the field's Date data type.

3. Move the slider handles to select different date ranges, and note how the chart data filters accordingly. You
can also select the date fields in the slicer and type in specific dates, or choose them from a calendar popup.

Format the visualizations

You decide to give the chart a more descriptive and attractive title.
1. With the chart selected, select the Format icon, and select the dropdown arrow to expand Title.
2. Change the Title text to Comments per post.
3. Select the dropdown arrow next to Font color, and select a green color to match the green bars of the
visualization.
4. Increase the Text size to 10, and change the Font family to Segoe (Bold).
Experiment with other formatting options and settings to change the appearance of your visualizations.

Create more visualizations

As you can see, it's easy to customize visualizations in your report to present the data in ways that you want. For
example, try using the imported Facebook data to create this line chart showing number of comments over time.
Power BI Desktop provides a seamless end-to-end experience, from getting data from a wide range of data sources
and shaping it to meet your analysis needs, to visualizing this data in rich and interactive ways. When your report is
ready, you can upload it to Power BI service and create dashboards based on it, which you can share with other
Power BI users.

Next steps
Read other Power BI Desktop tutorials
Watch Power BI Desktop videos
Visit the Power BI Forum
Read the Power BI Blog
 Dynamic row level security with Analysis services
tabular model
1/14/2019 • 8 minutes to read • Edit Online

This tutorial demonstrates the steps necessary to implement row level security within your Analysis Services
Tabular Model, and shows how to use it in a Power BI report. The steps in this tutorial are designed to let you
follow along and learn the steps necessary by completing on a sample dataset.
During this tutorial, the following steps are described in detail, helping you understand what you need to do to
implement dynamic row level security with Analysis Services tabular model:
Create a new security table in the AdventureworksDW2012 database
Build the tabular model with necessary fact and dimension tables
Define the roles and permissions for the users
Deploy the model to an Analysis Services tabular instance
Use Power BI Desktop to build a report that displays the data corresponding to the user accessing the report
Deploy the report to Power BI service
Create a new dashboard based on the report, and finally,
Share the dashboard with your coworkers
To follow the steps in this tutorial you need the AdventureworksDW2012 database, which you can download
from the repository.

Task 1: Create the user security table and define data relationship
There are many published articles describing how to define row level dynamic security with SQL Server Analysis
Services (SSAS ) tabular model. For our sample, we follow the article Implement Dynamic Security by Using Row
Filters. The following steps walk you through the first task in this tutorial:
1. For our sample, we're using AdventureworksDW2012 relational database. In that database, create the
DimUserSecurity table, as shown in the following image. For this sample, we're using SQL Server
Management Studio (SSMS ) to create the table.

2. Once the table is created and saved, we need to create the relationship between the DimUserSecurity
table's SalesTerritoryID column and DimSalesTerritory table's SalesTerritoryKey column, as shown in
the following image. This can be done from SSMS by right-clicking on the DimUserSecurity table, and
selecting Design. Then select Table Designer -> Relationships... from the menu.
3. Save the table, then add few rows of user information in to the table by again right clicking on the
DimUserSecurity table and then selecting Edit Top 200 Rows. Once you’ve added those users, the rows of
the DimUserSecurity table look like they do in the following image:

We’ll come back to these users in upcoming tasks.

4. Next we do an inner join with the DimSalesTerritory table, which shows the region details associated with
the user. The following code performs the inner join, and the image that follows shows how the table
appears once the inner join is successful.

select b.SalesTerritoryCountry, b.SalesTerritoryRegion, a.EmployeeID, a.FirstName, a.LastName,

a.UserName from [dbo].[DimUserSecurity] as a join [dbo].[DimSalesTerritory] as b on a.
[SalesTerritoryID] = b.[SalesTerritoryKey]

5. Notice that the above image shows information such as which user is responsible for which sales region.
That data is displayed because of the relationship that we created in Step 2. Also, note that the user Jon
Doe is part of the Australia sales region. We’ll revisit John Doe in upcoming steps and tasks.

Task 2: Create the tabular model with facts and dimension tables
1. Once your relational data warehouse is in place, it’s time to define your tabular model. The model can be
created using SQL Server Data Tools (SSDT). To get more information about how to define a tabular
model, please refer to Create a New Tabular Model Project.
2. Import all the necessary tables into the model as shown below.

3. Once you’ve imported the necessary tables, you need to define a role called SalesTerritoryUsers with
Read permission. This can be achieved by clicking on the Model menu in SQL Server Data Tools, and then
clicking Roles. In the Role Manager dialog box, click New.
4. Under Members tab in the Role Manager, add the users that we defined in the DimUserSecurity table in
Task 1 - step 3.
5. Next, add the proper functions for both DimSalesTerritory and DimUserSecurity tables, as shown below
under Row Filters tab.

6. In this step, we use the LOOKUPVALUE function to return values for a column in which the Windows user
name is the same as the user name returned by the USERNAME function. Queries can then be restricted
where the values returned by LOOKUPVALUE match values in the same or related table. In the DAX Filter
column, type the following formula:

=DimSalesTerritory[SalesTerritoryKey]=LOOKUPVALUE(DimUserSecurity[SalesTerritoryID],
DimUserSecurity[UserName], USERNAME(), DimUserSecurity[SalesTerritoryID],
DimSalesTerritory[SalesTerritoryKey])

In this formula, the LOOKUPVALUE function returns all values for the
DimUserSecurity[SalesTerritoryID ] column, where the DimUserSecurity[UserName] is the same as
the current logged on Windows user name, and DimUserSecurity[SalesTerritoryID ] is the same as the
DimSalesTerritory[SalesTerritoryKey].

IMPORTANT
Be aware that the DAX function USERELATIONSHIP is not supported when using row level security.

The set of Sales SalesTerritoryKey's returned by LOOKUPVALUE is then used to restrict the rows shown in
the DimSalesTerritory. Only rows where the SalesTerritoryKey for the row is in the set of IDs returned by
the LOOKUPVALUE function are displayed.
7. For the DimUserSecurity table, in the DAX Filter column, type the following formula:
 =FALSE()

This formula specifies that all columns resolve to the false Boolean condition; therefore, no columns for the
DimUserSecurity table can be queried.
8. Now we need to process and deploy the model. You can refer to the Deploy article for assistance in
deploying the model.

Task 3: Adding Data Sources within your On-premises data gateway

1. Once your tabular model is deployed and ready for consumption, you need to add a data source connection
to your on-premises Analysis Services tabular server within your Power BI portal.
2. To allow the Power BI service access to your on-premises analysis service, you need to have an On-
premises data gateway installed and configured in your environment.
3. Once the gateway is correctly configured, you need to create a data source connection for your Analysis
Services tabular instance. This article will help you with adding a data source within the Power BI portal.

4. With the previous step complete, the gateway is configured and ready to interact with your on-premises
Analysis Services data source.

Task 4: Creating report based on analysis services tabular model using

Power BI desktop
1. Launch Power BI Desktop and select Get Data > Database.
2. From the list of data sources, select the SQL Server Analysis Services Database and select Connect.
3. Fill in your Analysis Services tabular instance details and select Connect Live. Select OK. With Power BI,
dynamic security works only with Live connection.

4. You'll see that the model that was deployed is in the Analysis Services instance. Select the respective
model and select OK.
5. Power BI Desktop now displays all the available fields, to the right of the canvas in the Fields pane.
6. In the Fields pane on the right, select the SalesAmount measure from the FactInternetSales table and the
SalesTerritoryRegion dimension from the SalesTerritory table.
7. We’ll keep this report simple, so right now we won’t add any more columns. To have a more meaningful
representation of the data, we'll change the visualization to Donut chart.

8. Once your report is ready, you can directly publish it to the Power BI portal. From the Home ribbon in
Power BI Desktop, select Publish.

Task 5: Creating and sharing a dashboard

1. You’ve created the report and clicked Publish in Power BI Desktop, so the report is published to the
Power BI service. Now that it’s in the service, our model security scenario can be demonstrated by using
the example we created in the previous steps.
In his role, Sales Manager - Sumit can see data from all the different sales regions. So he creates this
report (the report created in the previous task steps) and publishes it to the Power BI service.
Once he publishes the report, he creates a dashboard in the Power BI service called TabularDynamicSec
based on that report. In the following image, notice that the Sales Manager (Sumit) is able to see the data
corresponding to all the sales region.
2. Now Sumit shares the dashboard with his colleague, Jon Doe, who is responsible for sales in the Australia
region.

3. When Jon Doe logs in to the Power BI service and views the shared dashboard that Sumit created, Jon Doe
should see only the sales from his region for which he is responsible. So Jon Doe logs in, accesses the
dashboard that Sumit shared with him, and Jon Doe sees only the sales from the Australia region.
4. Congratulations! The dynamic row level security that was defined in the on-premises Analysis Services
tabular model has been successfully reflected and observed in the Power BI service. Power BI uses the
effectiveusername property to send the current Power BI user credential to the on-premises data source
to run the queries.

Task 6: Understanding what happens behind the scenes

1. This task assumes you're familiar with SQL Profiler, since you need to capture a SQL Server profiler trace
on your on-premises SSAS tabular instance.
2. The session gets initialized as soon as the user (Jon Doe, in this case) accesses the dashboard in the Power
BI service. You can see that the salesterritoryusers role takes an immediate effect with the effective user
name as [email protected]

<PropertyList><Catalog>DefinedSalesTabular</Catalog><Timeout>600</Timeout><Content>SchemaData</Content>
<Format>Tabular</Format><AxisFormat>TupleFormat</AxisFormat><BeginRange>-1</BeginRange><EndRange>-
1</EndRange><ShowHiddenCubes>false</ShowHiddenCubes><VisualMode>0</VisualMode>
<DbpropMsmdFlattened2>true</DbpropMsmdFlattened2><SspropInitAppName>PowerBI</SspropInitAppName>
<SecuredCellValue>0</SecuredCellValue><ImpactAnalysis>false</ImpactAnalysis>
<SQLQueryMode>Calculated</SQLQueryMode><ClientProcessID>6408</ClientProcessID><Cube>Model</Cube>
<ReturnCellProperties>true</ReturnCellProperties><CommitTimeout>0</CommitTimeout>
<ForceCommitTimeout>0</ForceCommitTimeout><ExecutionMode>Execute</ExecutionMode>
<RealTimeOlap>false</RealTimeOlap><MdxMissingMemberMode>Default</MdxMissingMemberMode>
<DisablePrefetchFacts>false</DisablePrefetchFacts><UpdateIsolationLevel>2</UpdateIsolationLevel>
<DbpropMsmdOptimizeResponse>0</DbpropMsmdOptimizeResponse><ResponseEncoding>Default</ResponseEncoding>
<DirectQueryMode>Default</DirectQueryMode><DbpropMsmdActivityID>4ea2a372-dd2f-4edd-a8ca-
1b909b4165b5</DbpropMsmdActivityID><DbpropMsmdRequestID>2313cf77-b881-015d-e6da-
eda9846d42db</DbpropMsmdRequestID><LocaleIdentifier>1033</LocaleIdentifier>
<EffectiveUserName>[email protected]</EffectiveUserName></PropertyList>

3. Based on the effective user name request, Analysis Services converts the request to the actual
moonneo\jondoe credential after querying the local Active Directory. Once Analysis Services gets the
actual credential from Active Directory, then based on the access and permissions the user has for the data,
Analysis Services returns only the data for which he or she has permission.
4. If more activity occurs with the dashboard, for example, if Jon Doe goes from the dashboard to the
underlying report, with SQL Profiler you would see a specific query coming back to the Analysis Services
tabular model as a DAX query.
5. You can also see below the DAX query that is getting executed to populate the data for the report.

EVALUATE
ROW(
"SumEmployeeKey", CALCULATE(SUM(Employee[EmployeeKey]))
)

<PropertyList xmlns="urn:schemas-microsoft-com:xml-analysis">``
<Catalog>DefinedSalesTabular</Catalog>
<Cube>Model</Cube>
<SspropInitAppName>PowerBI</SspropInitAppName>
<EffectiveUserName>[email protected]</EffectiveUserName>
<LocaleIdentifier>1033</LocaleIdentifier>
<ClientProcessID>6408</ClientProcessID>
<Format>Tabular</Format>
<Content>SchemaData</Content>
<Timeout>600</Timeout>
<DbpropMsmdRequestID>8510d758-f07b-a025-8fb3-a0540189ff79</DbpropMsmdRequestID>
<DbPropMsmdActivityID>f2dbe8a3-ef51-4d70-a879-5f02a502b2c3</DbPropMsmdActivityID>
<ReturnCellProperties>true</ReturnCellProperties>
<DbpropMsmdFlattened2>true</DbpropMsmdFlattened2>
<DbpropMsmdActivityID>f2dbe8a3-ef51-4d70-a879-5f02a502b2c3</DbpropMsmdActivityID>
</PropertyList>

Considerations
There are a few considerations to keep in mind when working with row level security, SSAS, and Power BI:
1. On-premises row level security with Power BI is only available with Live Connection.
2. Any changes in the data after processing the model would be immediately available for the users (who are
accessing the report with Live Connection) from the Power BI service.
 What sample data is available to use with Power BI?
1/14/2019 • 11 minutes to read • Edit Online

Say you're new to Power BI and want to try it out but don't have any data. Or maybe you have a dataset, but
because you don't understand (yet) how Power BI works, you worry that you might somehow damage your
dataset?
No need to stress out! obviEnce (www.obvience.com) and Microsoft have created samples for you to use until
you feel more comfortable with Power BI. The data is anonymized and represents different industries: finance,
HR, sales, and more. And as you read through our online documentation you'll discover tutorials and examples
that use these same samples which means that you'll be able to follow along.

Each of these samples is available in several formats: as a content pack, as an individual Excel workbook, and as
a .pbix file. If you don't know what these things are, or how to get your hands on them -- don't worry. We'll
explain it all later in this article. And for each sample we've created a tour which is a type of article that tells the
story behind the sample and walks you through different scenarios. One scenario might be answering questions
for your manager, another might be looking for competitive insights, or creating reports and dashboards to
share, or explaining a business shift.
But before we get started, please read through these legal guidelines for using the samples. When you're done
we'll introduce the samples and show you how to use them.

Usage guidelines for the Power BI sample Excel workbooks

Please read this information before using the Power BI samples.
©2015 Microsoft Corporation. All rights reserved. The documents and workbooks are provided "as-is."
Information and views expressed in the workbooks, including URL and other Internet Web site references, may
change without notice. You bear the risk of using it. Some examples are for illustration only and are fictitious. No
real association is intended or inferred. Microsoft makes no warranties, express or implied, with respect to the
information provided here.
The workbooks do not provide you with any legal rights to any intellectual property in any Microsoft product.
You may copy and use this workbook for your internal, reference purposes.
The workbooks and related data are provided by obviEnce. www.obvience.com
ObviEnce is an ISV and an Intellectual Property (IP ) Incubator focused on Microsoft Business Intelligence.
ObviEnce works closely with Microsoft to develop best practices and thought leadership for jump-starting and
deploying Microsoft Business Intelligence solutions.
The workbooks and data are property of obviEnce, LLC and have been shared solely for the purpose of
demonstrating Power BI functionality with industry sample data.
Any uses of the workbooks and/or data must include the above attribution (that is also on the Info worksheet
included with each workbook). The workbook and any visualizations must be accompanied by the following
copyright notice: obviEnce ©.
By clicking any of the links below to download the Excel workbook files or .pbix files, you are agreeing to the
terms above.

Available samples
Eight samples are available for you to use. Each one represents a different industry.

Customer Profitability sample

Take a tour of the Customer Profitability sample
This industry sample analyzes a CFO's key metrics for her executives, products, and customers. You can
investigate what factors impact the company's profitability.

Human Resources sample

Take a tour of the HR sample
This industry sample focuses on the hiring strategy for a company by analyzing new hires, active employees,
and employees who've left. By exploring the data, you can find trends in voluntary separations and biases in the
hiring strategy.

IT Spend Analysis sample

Take a tour of the IT Spend Analysis sample
In this industry sample we analyze the planned vs. actual costs of the IT department of a company. This
comparison helps us understand how well the company planned for the year and investigate areas with huge
deviations from the plan. The company in this example goes through a yearly planning cycle, and then quarterly
it produces a new Latest Estimate (LE ) to help analyze changes in IT spend over the fiscal year.

Opportunity Analysis sample

Take a tour of the Opportunity Analysis sample
This industry sample explores a software company's sales channel. Sales managers monitor their direct and
partner sales channels by tracking opportunities and revenue by region, deal size, and channel.

Procurement Analysis sample

Take a tour of the Procurement Analysis sample
This industry sample analyzes a CFO's key metrics for her executives, products, and customers. You can
investigate what factors impact the company's profitability

Retail Analysis sample

Take a tour of the Retail Analysis sample
This industry sample analyzes retail sales data of items sold across multiple stores and districts. The metrics
compare this year's performance to last year's in these areas: sales, units, gross margin, and variance, as well as
new store analysis.

Sales and Marketing sample

Take a tour of the Sales and Marketing sample
This industry sample analyzes a manufacturing company, VanArsdel Ltd. It allows the Chief Marketing Officer to
watch the industry and the market share for VanArsdel. By exploring the sample, you can find the company's
market share, product volume, sales, and sentiment.

Supplier Quality sample

Take a tour of the Supplier Quality sample
This industry sample focuses on one of the typical supply chain challenges — supplier quality analysis. Two
primary metrics are at play in this analysis: total number of defects and the total downtime that these defects
caused. This sample has two main objectives: understand who the best and worst suppliers are, with respect to
quality, and identify which plants do a better job finding and rejecting defects, to minimize downtime.
Now you know what's available. Time to learn how to get ahold of these samples.

How to get the samples

As you read above, the samples are available in several formats: content packs, Excel workbooks, and .pbix files.
We'll describe how to use each of these, starting with content packs.

The Power BI samples as content packs

Content packs are the only sample format that is available from within Power BI; you don't have to leave Power
BI to find them. A content pack is essentially a bundle of one or more dashboard, dataset, and report that
someone creates and that can be used with Power BI service. People create content packs to share with
colleagues. Each of the Power BI sample content packs contains a dataset, report, and dashboard. Content packs
are not available for Power BI Desktop. If you'd like to learn more about content packs, read Intro to content
packs in Power BI.
Get and open a sample content pack in Power BI service
1. Open Power BI service (app.powerbi.com) and log in.
2. In the bottom left corner select Get data.

3. On the Get Data page that appears, select the Samples icon.

4. Select one of the samples to open a description of that sample. Then choose Connect.
5. Power BI imports the content pack and adds a new dashboard, report, and dataset to your current
workspace. The new content is marked with a yellow asterisk. Use the samples to take Power BI for a test
run.

Now that you have data, you're on your way. Try out some of our tutorials using the sample content packs or just
open Power BI service and explore.

The Power BI samples as Excel files

Each of the sample content packs is also available as an Excel workbook. The Excel workbooks are designed to
be used with Power BI service.
1. Download the files individually using the links below, or download a zip file of all the sample files. If
you're an advanced user, you might want to download the Excel workbooks to explore or edit the data
models.
Retail Analysis Sample
Supplier Quality Analysis Sample
Human Resources Sample
Customer Profitability Sample
Opportunity Tracking Sample
IT Spend Analysis Sample
Procurement Analysis Sample
Sales and Marketing Sample
2. Save the downloaded file. Where you save the file makes a difference.

Local - If you save your file to a local drive on your computer or another location in your
organization, from Power BI, you can import your file into Power BI. Your file will actually remain on
your local drive, so the whole file isn’t really imported into Power BI. What really happens is a new
dataset is created in your Power BI site and data, and in some cases the data model, are loaded into
the dataset. If your file has any reports, those will appear in your Power BI site under Reports.

OneDrive - Business – If you have OneDrive for Business and you sign into it with the same
account you sign into Power BI with, this is by-far the most effective way to keep your work in Excel,
Power BI, or a .CSV file in-sync with your dataset, reports, and dashboards in Power BI. Because both
Power BI and OneDrive are in the cloud, Power BI connects to your file on OneDrive about every
hour. If any changes are found, your dataset, reports, and dashboards are automatically updated in
Power BI.

OneDrive - Personal – If you save your files to your own OneDrive account, you’ll get many
 of the same benefits as you would with OneDrive for Business. The biggest difference is when you
first connect to your file (using Get Data > Files > OneDrive – Personal) you’ll need to sign in to your
OneDrive with your Microsoft account, which is usually different from what you use to sign in to
Power BI. When signing in with your OneDrive with your Microsoft account, be sure to select the Keep
me signed in option. This way, Power BI will be able to connect to your file about every hour and make
sure your dataset in Power BI is in-sync.

SharePoint Team -Sites Saving your Power BI files to SharePoint – Team Sites is much the
same as saving to OneDrive for Business. The biggest difference is how you connect to the file from
Power BI. You can specify a URL or connect to the root folder.
3. Open Power BI service (app.powerbi.com) and log in.

TIP
At this point you may want to create a new dashboard and name it after the file you plan on importing.
Otherwise, when you import the Excel dataset, Power BI won't create a new dashboard named after the sample
but instead will add a tile to the dashboard that you currently have open. Selecting that tile will take you to the
dataset's report. This isn't a major big deal as you can always create a new dashboard later, but starting with a new
dashboard saves you a step or two.

4. In the bottom left corner select Get data.

5. On the Get Data page that appears, select Files > Get.

6. Navigate to the location where you downloaded and saved the sample.

7. Select the file, in this case Procurement Analysis Sample.xlsx which was saved on OneDrive for
Business, and choose Connect.
 8. Choose whether to import the data or to bring the workbook into Power BI and see it exactly as it is in
Excel online.

9. If you select Import, Power BI imports the sample workbook and adds it as a new dataset named
Procurement Analysis Sample. If the workbook has any Power View sheets, tables or ranges, or a data
model, Power BI also creates a report (with the same name). And if you don't already have a dashboard
open, Power BI creates a new dashboard. (If you had a dashboard open when you clicked Get Data,
you'll see a new blank tile on that dashboard. Clicking that tile will take you to the report for the dataset
you just added). The new content is named after the sample and is marked with a yellow asterisk.
10. When the Your dataset is ready! screen appears, select View dataset or Get Quick Insights or simply
use your Power BI left navbar to locate and open the associated report or dashboard.

(Optional) Take a look at the Excel samples from inside Excel itself
Want to understand how the data in an Excel workbook gets converted to Power BI datasets and reports?
Opening the Excel samples in Excel and exploring the worksheets provides some of the answers.
When you first open a sample workbook in Excel, you may see two warnings. The first says the workbook
is in Protected View. Select Enable Editing. The second may say that the workbook has external data
connections. Select Enable Content.
 Each workbook contains several sheets. Because these Excel samples all have at least one Power View
sheet with visualizations, when you import the Excel file into Power BI you'll end up with a dataset and a
report.
You may need to enable the Power View add-in.
So where's the actual data? It's in the Power Pivot data model. To see the data, on the PowerPivot tab,
select Manage Data Model.
Don't see the PowerPivot tab? Enable the Power Pivot add-in.
The Info tab provides information about obviEnce, the company that created the sample.

The Power BI samples as .pbix files

Each of the sample content packs is also available as Power BI .pbix file. The .pbix files are designed to be used
with Power BI Desktop.
1. Download the files individually using the links below. Selecting these links saves the file automatically to
your Downloads folder.
Retail Analysis Sample PBIX
Supplier Quality Analysis Sample PBIX
Human Resources Sample PBIX
Customer Profitability Sample PBIX
Opportunity Tracking Sample PBIX
IT Spend Analysis Sample PBIX
Procurement Analysis Sample PBIX
Sales and Marketing Sample PBIX
2. From Power BI Desktop, select File > Open and navigate to the location where you saved the sample
.pbix.

3. Select the .pbix file to open it in Power BI Desktop.

Next steps
Power BI basic concepts
Tutorial: Connect to the Power BI samples
Data sources for Power BI
More questions? Try the Power BI Community
 Connect to the samples in the Power BI service
1/14/2019 • 5 minutes to read • Edit Online

This tutorial teaches how to:

Import a sample content pack, add it to Power BI service, and open the contents. A content pack is a type of
sample where the dataset is bundled with a dashboard and report.
Open a sample .pbix file in Power BI Desktop.
If you'd like more background first, we recommend starting with the article Sample datasets for Power BI. In that
article you'll learn all about the samples; how to get them, where to save them, how to use them, and some of the
stories each sample can tell. Then, when you have a grasp of the basics, come back to this Tutorial.

Prerequisites
The samples are available for Power BI service and Power BI Desktop. To follow along, we'll be using the Retail
analysis sample.
The Retail Analysis sample content pack used in this tutorial consists of a dashboard, report, and dataset. To
familiarize yourself with this particular content pack and its scenario, you may want to take a tour of the Retail
Analysis sample before you begin.

Samples and Power BI service

1. Open and sign in to Power BI Service (app.powerbi.com).
2. Select Get Data at the bottom of the left navigation pane. If you don't see Get Data, expand the nav pane
by selecting .

3. Select Samples.

4. Select the Retail Analysis Sample, and choose Connect.

What exactly was imported?
With the sample content packs, when you select Connect, Power BI is actually bringing in a copy of that content
pack and storing it for you in the cloud. Because the person who created the content pack included a dataset, a
report, and a dashboard -- that's what you get when you click Connect.
1. Power BI creates the new dashboard and lists it on your Dashboards tab. The yellow asterisk lets you know
it's new.

2. Open the Reports tab. Here you'll see a new report named Retail Analysis Sample.

And check out the Datasets tab. There's a new dataset as well.
Explore your new content
Now explore the dashboard, dataset, and report on your own. There are many different ways to navigate to your
dashboards, reports, and datasets, and just one of those many ways is described below.

TIP
Want a little hand-holding first? Try the Tour of the Retail Analysis sample for a step-by-step walkthrough of this sample.

1. Navigate back to your Dashboards tab and select the Retail Analysis Sample dashboard to open it.

2. The dashboard opens. It has a variety of visualization tiles.

3. Select one of the tiles to open the underlying report. In this example, we'll select the area chart (outlined in
pink in the previous image). The report opens to the page that contains that area chart.
 NOTE
If the tile had been created using Power BI Q&A, the Q&A page would've opened instead. If the tile was pinned from
Excel, Excel Online would've opened inside of Power BI.

4. Back on your Datasets tab, you have several options for exploring your dataset. You won't be able to open
it and see all the rows and columns (as you can in Power BI Desktop or Excel). When someone shares a
content pack with colleagues, they typically want to share the insights, not give their colleagues direct
access to the data. But that doesn't mean you can't explore the dataset.

One way of exploring the dataset is by creating your own visualizations and reports from scratch.
Select the chart icon to open the dataset in report editing mode.
 Another way of exploring the dataset is to run Quick Insights. Select the ellipses (...) and choose Get
insights. When the insights are ready, select View insights.

Samples and Power BI Desktop

When you first open the sample PBIX file, is displays in Report view where you can explore, create, and modify any
number of report pages with visualizations. Report view provides pretty much the same design experience as a
report’s Editing view in the Power BI service. You can move visualizations around, copy and paste, merge, etc.
The difference between them is when using Power BI Desktop, you can work with your queries and model your
data to make sure your data supports the best insights in your reports. You can then save your Power BI Desktop
file wherever you like, whether it's your local drive or to the cloud.
1. Open the Retail Analysis sample .pbix file in Power BI Desktop.

2. The file opens in Report view. Notice the 4 tabs at the bottom of the report editor? That means that there
are 4 pages in this report, and the "New Stores" page is currently selected.
 .
3. For a deep dive into the report editor, see Take a tour of the report editor

What exactly was imported?

When you open the sample PBIX file in Desktop, Power BI is actually bringing in a copy of that data and storing it
for you in the cloud. From Desktop you have access to the report and the underlying dataset. When the data is
loaded, Power BI Desktop will attempt to find and create relationships for you.

1. Switch to Data view by selecting the table icon .

Data View helps you inspect, explore, and understand data in your Power BI Desktop model. It's different
from how you view tables, columns, and data in Query Editor. With Data View, you’re looking at your data
after it has been loaded into the model.
When you’re modeling your data, sometimes you want to see what’s actually in a table or column without
creating a visual on the report canvas, often right down to the row level. This is especially true when you’re
creating measures and calculated columns, or you need to identify a data type or data category.

2. Switch to Relationships view by selecting the icon .

Relationship view shows all of the tables, columns, and relationships in your model. From here you can
view, change, and create relationships.

Explore your new content

Now explore the dataset, relationships, and report on your own. For help getting started, visit the Desktop Getting
Started Guide.

Next steps
Power BI basic concepts
Samples for Power BI service
Data sources for Power BI
More questions? Try the Power BI Community
 Customer Profitability sample for Power BI: Take a
tour
2/13/2019 • 9 minutes to read • Edit Online

Overview of the Customer Profitability sample

The “Customer Profitability Sample” content pack contains a dashboard, report, and dataset for a company that
manufactures marketing materials. This dashboard was created by a CFO to see key metrics about her 5 business
unit managers (aka executives), products, customers, and gross margins (GM ). At a glance she can see what factors
are impacting profitability.

This sample is part of a series that illustrates how you can use Power BI with business-oriented data, reports and
dashboards. This is real data from obviEnce (www.obvience.com) that has been anonymized. The data is available
in several formats: content pack/app, Excel workbook, or .pbix Power BI Desktop file. See Sample datasets.

Prerequisites
Want to follow along? This tutorial uses Power BI service and the "Customer Profitability" sample content pack.
Because the report experiences are so similar, you can also follow along using Power BI Desktop and the sample
PBIX file. Instructions for connecting to the content pack and the PBIX file are below.
Get the content pack for this sample
1. Open the Power BI service (app.powerbi.com) and log in.
2. In the bottom left corner select Get data.
3. On the Get Data page that appears, select the Samples icon.

4. Select the Customer Profitability Sample, then choose Connect.

5. Power BI imports the content pack and adds a new dashboard, report, and dataset to your current
workspace. The new content is marked with a yellow asterisk. Use the samples to take Power BI for a test
run.

Get the .pbix file for this sample

Alternatively, you can download the sample as a .pbix file, which is designed for use with Power BI Desktop.
Customer Profitability Sample
Get the Excel workbook for this sample
If you want to dig into the datasource for this sample, it's also available as an (Excel workbook). The workbook
contains Power View sheets that you can view and modify. To see the raw data, select Power Pivot > Manage.

What is our dashboard telling us?

Under My Workspace, find the dashboard for the Customer Profitability sample:
Company-wide dashboard tiles
1. Open the dashboard in Power BI service. The dashboard tiles give our CFO a view of the high-level
company metrics important to her. When she sees something interesting, she can select a tile to dig into the
data.
2. Review the tiles on the left side of the dashboard.
 Our company gross margin is 42.5%.
We have 80 customers.
We sell 5 different products.
We had our lowest revenue variance% to budget in February, followed by our highest in March.
Most of our revenue comes from the East and North regions. Gross margin has never exceeded budget, with
ER -0 and MA-0 requiring some further investigation.
Total revenue for the year is close to budget.
Manager-specific dashboard tiles
The tiles on the right side of the dashboard provide a team scorecard. The CFO needs to keep track of her
managers and these tiles give her a high level overview of profit – using GM%. If the GM% trend is unexpected for
any manager, then she can investigate further.
 All executives, except Carlos, have already exceeded their target sales. But Carlos' actual sales are the highest.
Annelie’s GM% is the lowest, but we see a steady increase since March.
Valery, on the other hand, has seen her GM% drop significantly.
And Andrew had a volatile year.

Explore the dashboard's underlying data

This dashboard has tiles that link to a report and to an Excel workbook.
Open the Excel Online data source
Two tiles on this dashboard, "Target vs Actual" and "Year Over Year Revenue Growth" were pinned from an Excel
workbook. So when you select either of these tiles, Power BI opens the data source -- in this case, Excel Online.
1. Select either of the tiles that were pinned from Excel. Excel Online opens within Power BI service.
2. Notice that the workbook has 3 tabs's worth of data. Open "Revenue".
3. Let's look into why Carlos hasn't hit his target yet.
a. From the "Executive" slider, select Carlos Grilo.
b. The first PivotTable tells us that Carlos' revenue for his top Product, Primus, is down 152% from last year.
And the YoY chart shows that for most months he's below budget.

4. Continue exploring, and if you find something interesting, select Pin from the upper-right corner to
pin it to a dashboard.
5. Use your browser's back arrow to return to the dashboard.
Open the underlying Power BI report
The majority of the tiles on the Customer Profitability sample dashboard were pinned from the underlying
Customer Profitability sample report.
1. Select one of these tiles to open the report in Reading view.
2. The report has 3 pages. Each tab at the bottom of the report represents a page.

"Team Scorecard" focuses on the performance of the 5 managers and their "books of business."
"Industry Margin Analysis" provides a way to analyze our profitability compared to what's going on in
our entire industry.
"Executive Scorecard" provides a view of each of our managers formatted for viewing in Cortana.
Team Scorecard page
Let’s look at two of the team members in detail and see what insights can be gained. In the slicer on the left, select
Andrew's name to filter the report page to display only data about Andrew.
For a quick KPI, look at Andrew’s Revenue Status - he is green. He’s performing well.
The “Revenue Var % to Budget by Month” Area chart shows that except for a dip in February, Andrew is doing
pretty well overall. His dominant region is East and he handles 49 customers and 5 (out of 7) products. His
GM% isn’t the highest or lowest.
The “RevenueTY and Revenue Var % to Budget by Month” shows a steady even profit story.But when you filter
by clicking on the square for Central in the region treemap, you discover that Andrew has revenue only in
March and only in Indiana. Is this intentional or is this something that needs looking into?
Now on to Valery. In the slicer, select Valery’s name to filter the report page to display only data about her.

Notice the red KPI for RevenueTY Status. This definitely needs further investigation.
Her revenue variance also paints a worrying picture – she is not meeting her revenue margins.
 Valery has only 9 customers, handles only 2 products and works almost-exclusively with customers in the north.
This specialization could explain wide fluctuations in her metrics.
Selecting the North square in the treemap shows that Valery’s gross margin in the North is consistent with her
overall margin.
Selecting the other Region squares tells an interesting story: her GM% ranges from 23% to 79% and her
revenue numbers, in all regions except North, are extremely seasonal.
Continue digging to find out why Valery’s area is not performing well. Look at regions, the other business units,
and the next page in the report – “Industry Margin Analysis.”
Industry Margin Analysis
This report page provides a different slice of the data. It looks at gross margin for the entire industry, broken down
by segment. The CFO uses this page to compare company and business unit metrics to industry metrics to help
her explain trends and profitability. You might wonder why the “Gross Margin by Month and Executive Name” area
chart is on this page, since it is team-specific. Having it here lets us filter the page by business unit manager.

How does profitability vary by industry? How do the products and customers break down by industry? Select one
or more industries from the top left. (Start from the CPG industry) To clear the filter, select the eraser icon.
On the bubble chart, the CFO looks for the largest bubbles since these are the ones that have the biggest impact
on revenue. Filtering the page by manager by clicking on their names in the area chart makes it easy to see each
manager’s impact by industry segment.
Andrew's area of influence spans many different industry segments with widely varying GM% (most on the
positive side) and Var%.
Annelie's chart is similar, except that she concentrates on only a handful of industry segments with a focus on
the Federal segment and a focus on Gladius product.
Carlos has a clear focus on the Services segment, with good profit. He's greatly improved variance % for the
High Tech segment and a new segment for him, Industrial, performed exceptionally well compared to budget.
Tina works with a handful of segments and has the highest GM%, but the mostly small size of her bubbles
shows that her impact on the company's bottom line is minimal.
Valery, who is responsible for only one product, works in only 5 industry segments. Her industry influence is
seasonal, but always produces a large bubble, indicating a significant impact on the company’s bottom line.
Does industry explain her negative performance?
Executive Scorecard
This page is formatted as an Answer Card for Cortana. To learn more, see create Answer Cards for Cortana

Dig into the data by asking questions with Q&A

For our analysis, it would be helpful to determine which industry generates the most revenue for Valery. Let’s use
Q&A.
1. Open the report in Editing view by selecting Edit report. Editing view is only available if you "own" the
report; this is sometimes referred to as creator mode. If, instead, this report had been shared with you, you
wouldn't be able to open it in Editing view.
2. From the top menubar, select Ask a question to open the Q&A question box.

3. Type total revenue by industry for Valery. Notice how the visualization updates as you type the question.

Distribution is the biggest revenue area for Valery.

Dig deeper by adding filters
Let's take a look at the Distribution industry.
1. Open the "Industry Margin Analysis" report page.
2. Without selecting any visualizations on the report page, expand the filter pane on the right (if it isn't already
expanded). The Filters pane should display only Page level filters.
3. Locate the filter for Industry and select the arrow to expand the list. Let's add a page filter for the
Distribution industry. First, clear all selections by clearing the Select All checkbox. Then select only
Distribution.

4. The "Gross margin by Month and Executive Name" area chart tells us that only Valery and Tina have
customers in this industry and Valery only worked with this industry from June to November.
5. Select Tina and then Valery in the "Gross Margin by Month and Executive" area chart legend. Notice Tina's
portion of "Total Revenue by Product" is really small compared to Valery.
6. To see actual revenue, use Q&A to ask total revenue by executive for distribution by scenario.
 We can similarly explore other industries and even add customers to our visuals to understand causes for
Valery's performance.
This is a safe environment to play in. You can always choose not to save your changes. But if you do save them, you
can always go to Get Data for a new copy of this sample.
You can also download just the dataset (Excel workbook) for this sample.

Next steps: Connect to your data

We hope this tour has shown how Power BI dashboards, Q&A, and reports can provide insights into customer
data. Now it is your turn — connect to your own data. With Power BI you can connect to a wide variety of data
sources. Learn more about getting started with Power BI.
Back to Samples in Power BI
 IT Spend Analysis sample for Power BI: Take a tour
2/13/2019 • 5 minutes to read • Edit Online

Overview of the IT Spend Analysis sample

The IT Spend Analysis content pack (dashboard, report, and dataset) analyze the planned vs. actual costs of an IT
department. This comparison helps us understand how well the company planned for the year and investigate
areas with huge deviations from the plan. The company in this example goes through a yearly planning cycle, and
then quarterly it produces a new Latest Estimate (LE ) to help analyze changes in IT spend over the fiscal year.

This sample is part of a series that illustrates how you can use Power BI with business-oriented data, reports and
dashboards. This is real data from obviEnce (http://obvience.com/) that has been anonymized.

Prerequisites
Before you can use the sample, you must first download it as a content pack, .pbix file, or Excel workbook.
Get the content pack for this sample
1. Open the Power BI service (app.powerbi.com) and log in.
2. In the bottom left corner select Get data.

3. On the Get Data page that appears, select the Samples icon.

4. Select the IT Spend Analysis Sample, then choose Connect.

5. Power BI imports the content pack and adds a new dashboard, report, and dataset to your current
workspace. The new content is marked with a yellow asterisk.

Get the .pbix file for this sample

Alternatively, you can download the sample as a .pbix file, which is designed for use with Power BI Desktop.
IT Spend Analysis Sample
Get the Excel workbook for this sample
You can also download just the dataset (Excel workbook) for this sample. The workbook contains Power View
sheets that you can view and modify. To see the raw data select Power Pivot > Manage.

The IT Spend Analysis Sample dashboard

The two numbers tiles on the dashboard, the Var Plan % and Variance Latest Estimate % Quarter 3, give us an
overview of how well we are doing against plan and against the Latest Qtr estimate (LE3 = Latest Estimate
Quarter 3). Overall we are about 6% off the plan. Let’s explore the cause of this variance – when, where, and which
category?

“YTD IT Spend Trend Analysis” page

Selecting the Var Plan % by Sales Region dashboard tile takes you to the “IT Spend Trend Analysis” page of the
IT Spend Analysis Sample report. We see at a glance that we have positive variance in US and Europe and
negative variance in Canada, Latin America, and Australia. US had about 6% +LE variance and Australia has about
7% -LE variance.

But just looking at this chart and drawing conclusions can be misleading. We need to look at actual dollar amounts
to put things in perspective.
1. Select Aus and NZ in the Var Plan % by Sales Region chart, and observe Var Plan by IT Area chart.

2. Now select USA. You get the idea — Australia is a really small part of our overall spend as compared to US.
So we narrowed it down to the USA, now what? Let’s explore which category in the USA is causing the
variance.

Ask questions of the data

1. Select IT Spend Analysis Sample in the top navigation bar to return to the Dashboards.
2. In the question box, type “show IT areas, var plan % and var le3 % bar chart”.

In the first IT area, Infrastructure, the percentage has changed drastically between the initial variance plan
and the variance plan latest estimate.

“YTD Spend by Cost Elements” page

Go back to the dashboard and look at the Var Plan %, Var LE3% dashboard tile.
Infrastructure jumps out with huge positive variance to plan.
1. Click this tile to go to the “YTD Spend by Cost Elements” page of the IT Spend Analysis Sample report.
2. Click the Infrastructure bar in the “Var Plan % and Var LE3 % by IT Area” chart in the lower left, and
observe the variance to plan in the "Var Plan % by Sales Region" to the left.

3. Click the name of each Cost Element Group in the slicer to find the cost element with a large variance.
4. With Other selected, click Infrastructure in the IT Area and click the sub areas in the IT Sub Area slicer to
find the sub area with the largest variance.
We see a huge variance in Networking.
Apparently the company decided to give its employees phone services as a benefit but this move was not
planned for.

“Plan Variance Analysis” page

Still in the report, click the "Plan Variance Analysis" tab on the bottom of the report to go to page 3 of the report.
In the “Var Plan, and Var Plan % by Business Area” combo chart on the left, click the Infrastructure column to
highlight infrastructure values in the rest of the page.
Notice on the “Var plan% by Month and Business Area” chart that infrastructure started to have a positive variance
around February and then it keeps increasing. Also, notice how the variance to plan value for infrastructure varies
by country, compared to the value for all business areas. Use the “IT Area” and “IT Sub Areas” slicers on the right
to filter the values in the rest of the page rather than highlighting them. Click the different IT Areas on the right to
explore the data in another way. You can also click IT Sub Areas and see the variance at that level.

Edit the report

Click Edit Report in the upper-left corner and explore in Editing View.
See how the pages are made – the fields in each chart, filters on the pages
Add pages and charts based on the same data
Change the visualization type for each chart
Pin them to your dashboard
This is a safe environment to play in. You can always choose not to save your changes. But if you do save them,
you can always go to Get Data for a new copy of this sample.

Next steps: Connect to your data

We hope this tour has shown how Power BI dashboards, Q&A, and reports can provide insights into IT spend
data. Now it is your turn — connect to your own data. With Power BI you can connect to a wide variety of data
sources. Learn more about getting started with Power BI.
 Human Resources sample for Power BI: Take a tour
2/13/2019 • 6 minutes to read • Edit Online

Overview of the Human Resources sample

The HR department has the same reporting model across different companies, even when they differ by industry
or size. This sample looks at new hires, active employees, and employees who left and tries to uncover any trends
in the hiring strategy. Our main objectives are to understand:
Who we hire
Biases in our hiring strategy
Trends in voluntary separations

This sample is part of a series that illustrates how you can use Power BI with business-oriented data, reports, and
dashboards. This is real data from obviEnce (www.obvience.com) that has been anonymized. The data is available
in several formats: content pack/app, Excel workbook, or .pbix Power BI Desktop file. To learn more, see Sample
datasets.

Prerequisites
Before you can use the sample, you must first download it as a content pack, pbix file, or Excel workbook.
Get the content pack for this sample
1. Open the Power BI service (app.powerbi.com) and log in.
2. In the bottom left corner select Get data.

3. On the Get Data page that appears, select the Samples icon.
4. Select the Human Resources Sample, then choose Connect.

5. Power BI imports the content pack and adds a new dashboard, report, and dataset to your current
workspace. The new content is marked with a yellow asterisk.

Get the .pbix file for this sample

Alternatively, you can download the sample as a .pbix file, which is designed for use with Power BI Desktop.
Human Resources Sample PBIX
Get the Excel workbook for this sample
You can also download just the dataset (Excel workbook) for this sample. The workbook contains Power View
sheets that you can view and modify. To see the raw data select Power Pivot > Manage.

New hires
Let’s explore new hires first.
1. In your workspace, select the Dashboards tab, and open the Human Resources dashboard.
2. On the dashboard, select the New Hire Count, New Hires Same Period Last Year, Actives YoY %
Change By Month tile.
 The Human Resources Sample report opens to the New Hires page.

Notice the following:

The New Hire Count, New Hires SPLY and Actives YoY % Change by Month combo chart shows we
hired more people every month this year compared to last year significantly more people in some months.
In the combo chart New Hire Count and Active Employee Count by Region and Ethnicity, notice we’re
hiring fewer people in the East region.
The New Hires YoY Var by Age Group waterfall chart shows we’re hiring mainly younger people. This may
be due to the mainly part-time nature of the jobs.
The New Hire Count by Gender pie chart shows a pretty even split.
Can you find more insights; for example, a region where the gender split is not even? Select different age groups
and genders in the charts to explore the relationships between age, gender, region, and ethnicity group.
Select the name of the dashboard from the top navbar to return to the dashboard.
Compare current active and former employees
Let’s explore data for current active employees and employees who no longer work for the company.
On the dashboard, select the Active Employee Count by Age Group tile.

The Human Resources Sample report opens to the Active Employees vs. Separations page.

Items of interest:
Combo charts on the left show year-over-year change for active employees and separates. We have more
actives this year due to rapid hiring, but also more separates than last year.
In August we had more separates compared to other months. Select the different age groups, genders, or
regions to see if you can find any outliers.
Looking at the pie charts, we notice we have a pretty even split in our active employees by gender and age
groups. Select different age groups to see the gender split differs by age. Do we have an even split by gender in
every age group?

Reasons for separation

Let’s look at the report in Editing View. Select Edit report in the upper-left corner.
Change the pie charts to show Separates data instead of Actives.
1. Select the Active Employee Count by Age Group pie chart.
2. In Fields, select the arrow next to Employees to expand the Employees table. Clear the check box next to
Active Employee Count to remove that field.
3. Select the check box next to Separation Count in the Employees table to add it to the Values box in the
field well.
4. Back on the report canvas, select the Voluntary bar in the Separation Count by Separation Reason bar
chart. This highlights those who left voluntarily in the other visuals in the report.
5. Click the 50+ slice of the Separation Count by Age Group pie chart.
Look at the Separations by Reason line chart in the lower-right corner. This chart is filtered to show
voluntary separations.

Notice the trend in the 50+ age group? During the latter part of the year more employees over age 50 are
leaving voluntarily. This would be an area to investigate further with more data.
6. You can follow the same steps for the Active Employee Count by Gender pie chart too, changing it to
separations instead of active employees. Look at the voluntary separation data by gender to see if you find
any other insights.
7. Click Power BI in the top navigation bar to return to the dashboard. You can save the changes you’ve made
to the report or not.

Bad hires
The last area to explore is bad hires. Bad hires are defined as employees who didn’t last for more than 60 days.
We’re hiring rapidly. Are we hiring good candidates?
1. Select the Bad Hires as % of Actives by Age Group dashboard tile. This opens the report to page 3, “Bad
Hires”.
2. Select the Northwest check box in the Region slicer on the left and the Male slice in the Bad Hire Count by
Gender donut chart. Look at other charts on the “Bad Hires” page. More male bad hires than females and
lot of Group A bad hires.

3. Looking at the Bad Hires by Gender donut chart and clicking through the Region slicer we notice that
East is the only region with more female than male bad hires.
4. Select the name of the dashboard from the top navbar to return to the dashboard.

Asking a question in the Q&A box

The Q&A question box is where you type a question using natural language. Q&A recognizes the words you type
and figures out where in your dataset to find the answer.
1. Click in the Q&A question box. Notice before you even start typing, the Q&A box contains suggestions:
2. You can pick one of those suggestions, or type: show age group, gender and bad hires SPLY where
region is east.

Notice most of the female bad hires are under 30.

This is a safe environment to play in. You can always choose not to save your changes. If you do save them, you
can always go to Get Data for a new copy of this sample.

Next steps: Connect to your data

We hope this tour has shown how Power BI dashboards, Q&A, and reports can provide insights into human
resources data. Now it is your turn — connect to your own data. With Power BI you can connect to a wide variety
of data sources. Learn more about getting started with Power BI.
 Opportunity Analysis sample for Power BI: Take a
tour
1/14/2019 • 5 minutes to read • Edit Online

Overview of the Opportunity Analysis sample

The Opportunity Analysis Sample contains a dashboard (and associated report) for a software company that
has 2 sales channels: direct and partner. The Sales Manager created this dashboard to track opportunities and
revenue by region, deal size, and channel.
The Sales Manager relies on two measures of revenue:
Revenue – this is a salesperson’s estimate of what he believes the revenue will be.
Factored Revenue – this is calculated as Revenue X Probability% and is generally accepted as being a
more-accurate predictor of actual sales revenue. Probability is determined by the deal’s current Sales Stage.
Lead – 10%
Qualify – 20%
Solution – 40%
Proposal – 60%
Finalize – 80%

This sample is part of a series that illustrates how you can use Power BI with business-oriented data, reports and
dashboards. This is real data from obviEnce (www.obvience.com) that has been anonymized.
Prerequisites
Before you can use the sample, you must first download it as a content pack, .pbix file, or Excel workbook.
Get the content pack for this sample
1. Open the Power BI service (app.powerbi.com) and log in.
2. In the bottom left corner select Get data.

3. On the Get Data page that appears, select the Samples icon.

4. Select the Opportunity Analysis Sample, then choose Connect.

5. Power BI imports the content pack and adds a new dashboard, report, and dataset to your current
workspace. The new content is marked with a yellow asterisk.

Get the .pbix file for this sample

Alternatively, you can download the sample as a .pbix file, which is designed for use with Power BI Desktop.
Opportunity Analysis Sample
Get the Excel workbook for this sample
You can also download just the dataset (Excel workbook) for this sample. The workbook contains Power View
sheets that you can view and modify. To see the raw data select Power Pivot > Manage.

What is our dashboard telling us?

Our Sales Manager has created a dashboard to track those metrics most important to her. When she sees
something interesting, she can select a tile to dig into the data.
1. Company revenue is $2 billion and factored revenue is $461 million.
2. Opportunity count and revenue follow a familiar funnel pattern, with totals decreasing each subsequent stage.
3. Most of our opportunities are in the East region.
4. The large opportunities generate more revenue than the medium or small opportunities.
5. Partner large deals generate more revenue: $8M on average versus $6M for direst sales.
Since the effort to land a deal is the same whether the deal is classified as large, medium, or small; our company
should dig into the data to learn more about large opportunities.
Select the Opportunity Count by Partner Driven and Sales Stage tile to open page 1 of the report.

Explore the pages in the report

Page 1 of our report is titled “Opportunity Count Overview.”

East is our biggest region in terms of opportunity counts.

On the pie chart, select each region one at a time to filter the page. For each region, partners are pursuing
significantly more large opportunities.
The Opportunity Count by Partner Driven and Opportunity Size column chart clearly shows that most of the
large opportunities are partner-driven and more of the small and medium opportunities are not partner-driven.
Select each Sales Stage in the bar chart in the bottom left to see the difference in regional count and notice that
even though East is our biggest region in terms of counts, in the Solution, Proposal and Finalize stages all 3
regions have comparable counts. This means we close a higher percent of deals in Central and West.
Page 2 of our report is titled “Revenue Overview.”
This page takes a similar look at the data but using a revenue perspective instead of count.
 East is our biggest region not only in opportunity count but in revenue also.
Filtering by Partner driven (select Yes in the legend in the top right) reveals revenue of $1.5B and $294M.
Compare this to $644B and $166M for non-partner driven revenue.
Average revenue for large accounts is larger (8M ) if the opportunity is partner driven as compared to 6M for
non-partner driven business.
For partner driven business, average revenue for large opportunities is almost double that of medium sized
opportunities (4M ).
Average revenue for small and medium businesses is comparable for both partner driven and non-partner
driven business.
Clearly our partners are doing a better job selling to customers. It might make sense to funnel more deals through
our partners.
Page 3 of our report is titled "Region Stage Counts"
This page looks at similar data but breaks it down by region and stage.

Filtering by East (select East in the pie chart) reveals that the opportunities in the east are split almost equal
between partner driven and non-partner driven.
Large opportunities are most common in the central region, small opportunities are most common in the east
region, and medium opportunities are most common in the west region.
Page 4 of our report is titled “Upcoming Opportunities”
Again, we’re looking at similar factors, but this time from a date/time perspective.
Our CFO uses this page to manage workload. By looking at the revenue opportunities by sales stage and month,
she can plan appropriately.
Average revenue for the Finalize stage is the highest. Closing these deals is a top priority.
Filtering by month (by selecting the month name in the left slicer) shows that January has a high proportion of
large deals in the Finalize stage with factored revenue of $75M. February, on the other hand, has mostly
medium deals in Solution and Proposal stage.
In general, the factored revenue numbers fluctuate based on sales stage, number of opportunities, and deal
size. Add filters (using the filter pane on the right) for these factors to discover further insights.
This is a safe environment to play in. You can always choose not to save your changes. But if you do save them,
you can always go to Get Data for a new copy of this sample.

Next steps: Connect to your data

We hope this tour has shown how Power BI dashboards, Q&A, and reports can provide insights into opportunity
tracking data. Now it’s your turn — connect to your own data. With Power BI you can connect to a wide variety of
data sources. Learn more about getting started with Power BI.
Download samples
 Procurement Analysis sample for Power BI: Take a
tour
1/14/2019 • 4 minutes to read • Edit Online

Overview of the Procurement Analysis sample

This industry sample dashboard and underlying report analyze a manufacturing company’s spending on vendors
by category and location. In the sample, we explore these areas:
Who the top vendors are
What categories we spend most on
Which vendors give us the highest discount and when
This sample is part of a series that illustrates how you can use Power BI with business-oriented data, reports and
dashboards. This is real data from obviEnce (www.obvience.com) that has been anonymized.

Prerequisites
Before you can use the sample, you must first download it as a content pack, .pbix file, or Excel workbook.
Get the content pack for this sample
1. Open the Power BI service (app.powerbi.com) and log in.
2. In the bottom left corner select Get data.
3. On the Get Data page that appears, select the Samples icon.

4. Select the Procurement Analysis Sample, then choose Connect.

5. Power BI imports the content pack and adds a new dashboard, report, and dataset to your current
workspace. The new content is marked with a yellow asterisk.

Get the .pbix file for this sample

Alternatively, you can download the sample as a .pbix file, which is designed for use with Power BI Desktop.
Procurement Analysis Sample
Get the Excel workbook for this sample
You can also download just the dataset (Excel workbook) for this sample. The workbook contains Power View
sheets that you can view and modify. To see the raw data select Power Pivot > Manage.

Spending trends
Let’s first look for trends in spending by category and location.
1. From your workspace, open the Dashboards tab and select the Procurement Analysis dashboard.
2. Select the dashboard tile Total Invoice by Country/Region. It opens to the "Spend Overview" page of the
“Procurement Analysis Sample” report.
Notice a few things:
In the Total Invoice by Month and Category line chart: The Direct category has pretty consistent spending,
Logistics has a peak in December, and Other has a spike in February.
In the Total Invoice by Country/Region map: Most of our spending is in the USA.
In the Total Invoice by Sub Category column chart: Hardware and Indirect Goods & Services are the
biggest spend categories.
In the Total Invoice by Tier bar chart: Most of our business is done with our Tier 1 (top 10) vendors. This helps
in managing vendor relationships better.

Spending in Mexico
Let’s explore the spending areas in Mexico.
1. In the pie chart, select the Mexico bubble in the map. Notice that in the “Total Invoice by Sub Category”
column chart, most of it is in the Indirect Goods & Services sub category.

2. Drill down into the Indirect Goods & Services column:

Select the drill-down arrow in the upper-right corner of the chart.

 Select the Indirect Goods & Services column.
By far the biggest spend in this category overall is Sales & Marketing.
Select Mexico in the map again.
The biggest spend in this category in Mexico is Maintenance & Repair.

3. Select the up arrow on the upper-left corner of the chart to drill back up .
4. Select the arrow again to turn drill down off.
5. Select Power BI in the top navigation bar to return to your workspace.

Evaluate different cities

We can use highlighting to evaluate different cities.
1. Select the dashboard tile Total Invoice, Discount % By Month. The report opens to the “Discount
Analysis” page.
2. Select the different cities in the Total Invoice by City treemap, to see how they compare. Almost all of
Miami’s invoices are from Tier 1 vendors.
Vendor discounts
Let’s also explore the discounts available from vendors, and the time periods when we get most discounts.

Specifically, these questions:

Are discounts different month by month, or are discounts the same every month?
Do some cities get more discounts than others?
Discount by month
Looking at the Total Invoice and Discount % by Month combo chart, we see that February is the busiest
month, and September the least busy month. Now look at the discount percent during these months. Note that
when volume goes up, the discount shrinks, and when volume is low, the discount goes up. The more we need the
discount, the worse deal we get.

Discount by city
Another area to explore is discount by city. Select each city in the treemap and see how the other charts change.
St. Louis, MO had a big spike in total invoice in February and a big dip in discount savings in April.
Mexico City, Mexico has the highest discount % (11.05%) and Atlanta, GA has the smallest (0.08%).
Edit the report
Select Edit report in the upper-left corner and explore in Editing View.
See how the pages are made
Add pages and charts based on the same data
Change the visualization type for a chart – for example, change the treemap to a donut chart
Pin them to your dashboard
This is a safe environment to play in. You can always choose not to save your changes. If you do save them, you
can always go to Get Data for a new copy of this sample.

Next steps: Connect to your data

We hope this tour has shown how Power BI dashboards and reports can provide insights into procurement data.
Now it’s your turn connect to your own data. With Power BI you can connect to a wide variety of data sources.
Learn more about getting started with Power BI.
 Retail Analysis sample for Power BI: Take a tour
1/14/2019 • 4 minutes to read • Edit Online

This industry sample dashboard and underlying report analyze retail sales data of items sold across multiple
stores and districts. The metrics compare this year’s performance to last year’s in these areas: sales, units, gross
margin, and variance, as well as new store analysis. This is real data from obviEnce (www.obvience.com) that has
been anonymized.

Prerequisites
Before you can use the sample, you must first download it as a content pack, .pbix file, or Excel workbook.
Get the content pack for this sample
1. Open the Power BI service (app.powerbi.com) and log in.
2. In the bottom left corner select Get data.

3. On the Get Data page that appears, select the Samples icon.

4. Select the Retail Analysis Sample, then choose Connect.

5. Power BI imports the content pack and adds a new dashboard, report, and dataset to your current
workspace. The new content is marked with a yellow asterisk.

Get the .pbix file for this sample

Alternatively, you can download the sample as a .pbix file, which is designed for use with Power BI Desktop.
Retail Analysis Sample
Get the Excel workbook for this sample
You can also download just the dataset (Excel workbook) for this sample. The workbook contains Power View
sheets that you can view and modify. To see the raw data select Power Pivot > Manage.

Start on the dashboard and open the report

1. On the dashboard, select the "Total Stores" tile:

This takes you to the "Store Sales Overview" page in the report. You see we have 104 total stores, 10 of
them new. We have two chains, Fashions Direct and Lindseys. Fashions Direct stores are larger on average.
2. In the pie chart, select Fashions Direct.
 Notice the result in the bubble chart:

FD -01 district has the highest Average Sales per Square Foot, FD -02 has the lowest Variance in Sales
compared to last year, FD -03 and FD -04 are worst performers overall.
3. Select individual bubbles or other charts to see cross highlighting, revealing the impact of your selections.
4. To return to the dashboard, select its name from the top navbar (breadcrumbs).

5. On the dashboard, select the tile that has "This Year’s Sales."

This is equivalent to typing "This year sales" in the question box.

You see this screen:
Review a tile created with Power BI Q&A
Let’s get more specific.
1. Add “this year sales by district” onto the question. Observe the result: It automatically put the answer in a
bar chart and suggests other phrases:
2. Now change the question to “this year sales by zip and chain”.
Notice how it answers the question as you type with the appropriate charts.
3. Play around with more questions and see what kind of results you get.
4. When you’re ready, return to the dashboard.

Dive deeper into the data

Now let's explore on a more detailed level, looking at the districts' performances.
1. On the dashboard, select the tile comparing this year's sales to last year’s.
 Notice the large variability on Variance % to last year, with Jan, Apr, and Jul being particularly bad months.

Let’s see if we can narrow down where the issues might be.
2. Select the bubble chart, and choose 020-Mens.

Observe the men's category wasn't as severely affected in April as the business overall, but January and
July were still problem months.
3. Now, select the 010-Womens’ bubble.
 Notice the women's category performed much worse than business overall across all months, and much
worse in almost every month compared to the previous year.
4. Select the bubble again to clear the filter.

Try out the slicer

Let’s look at how specific districts are doing.
1. Select Allan Guinot in the slicer on the top left.

Note that Allan’s district outperformed Last Year in March and June.
2. Now, while Allan is still selected, select the Women’s bubble.
 Note that for the Women’s category, his district never met last year’s volume.
3. Explore the other district managers and categories – what other insights can you find?
4. When you are ready – return to the dashboard.

What is our data telling us about sales growth this year?

The last area we want to explore is our growth – new stores opened this year.
1. Select the 'Stores Opened This Year’ tile.

As evident from the tile – more Fashions Direct stores than Lindseys stores opened this year.
2. Observe the 'Sales Per Sq Ft by Name' chart:

There is quite a bit of difference in Average Sales per SQF across the new stores.
3. Click on the Fashions Direct legend item in the top right chart. Notice, even for the same chain, the best
store (Winchester Fashions Direct) significantly outperforms the worst store (Cincinnati 2 Fashions Direct)
$21.22 vs $12.86 respectively.

4. Click Winchester Fashions Direct in the slicer and observe the line chart. The first sales numbers were
reported in February.
5. Click on Cincinnati 2 Fashions Direct in the slicer and you will see in the line chart that it was opened in
June and it seems to be the worst performing store.
6. As before, explore by clicking on other bars, lines and bubbles throughout the charts and see what insights
you can discover.
This is a safe environment to play in. You can always choose not to save your changes. But if you do save them,
you can always go to Get Data for a new copy of this sample.

Connect to your data

We hope this tour has shown how Power BI dashboards, Q&A, and reports can provide insights into retail data.
Now it’s your turn — connect to your own data. With Power BI you can connect to a wide variety of data sources.
Learn more about getting started with Power BI.

Next steps
Download the Retail Analysis sample content pack
Download a zip file of all the sample files
Download the Excel workbook for this Power BI sample
Get data (for Power BI)
Power BI - Basic Concepts
More questions? Try the Power BI Community
 Sales and Marketing sample for Power BI: Take a tour
1/14/2019 • 7 minutes to read • Edit Online

Overview of the Sales and Marketing sample

The Sales and Marketing Sample contains a dashboard and report for a fictitious manufacturing company
named VanArsdel Ltd. This dashboard was created by the VanArsdel Chief Marketing Officer (CMO ) to keep an
eye on the industry and his company’s market share, product volume, sales, and sentiment.
VanArsdel has many competitors but is the market leader in its industry. The CMO wants to increase market share
and discover growth opportunities. But, for some reason, VanArsdel’s market share has started to decline, with
significant dips in June.
This sample is part of a series that illustrates how you can use Power BI with business-oriented data, reports and
dashboards. This is real data from obviEnce (www.obvience.com) that has been anonymized.

Prerequisites
Before you can use the sample, you must first download it as a content pack, .pbix, or Excel workbook.
Get the content pack for this sample
1. Open the Power BI service (app.powerbi.com) and log in.
2. In the bottom left corner select Get data.
3. On the Get Data page that appears, select the Samples icon.

4. Select the Sales and Marketing Sample, then choose Connect.

5. Power BI imports the content pack and adds a new dashboard, report, and dataset to your current
workspace. The new content is marked with a yellow asterisk.

Get the .pbix file for this sample

Alternatively, you can download the sample as a .pbix file, which is designed for use with Power BI Desktop.
Sales and Marketing Sample
Get the Excel workbook for this sample
You can also download just the dataset (Excel workbook) for this sample. The workbook contains Power View
sheets that you can view and modify. To see the raw data select Power Pivot > Manage.

What is our dashboard telling us?

Let’s start our tour at the dashboard and look at the tiles the CMO has chosen to pin. We see information about
our market share, sales, and sentiment. And we see that data broken down by region, time, and competition.
The number tiles down the left column show industry sales volume this past year (50K), market share (32.86%),
sales volume (16K), sentiment score (68), sentiment gap (4), and total units sold (1M ).
The top line chart shows how our market share fluctuates over time. Our market share really drops in June.
Also, our R12M (Rolling 12 Months) share which was increasing for a while, is starting to stall.
Our biggest competitor is Aliqui (evident in the middle column chart tile.)
Most of our business is in the East and Central regions.
The line chart at the bottom shows that our dip in June is not seasonal – none of our competitors show the
same trend.
The two “Total Units” tiles show units sold, by segment and by region/manufacturer. The largest market
segment for our industry are Productivity and Convenience.
Use Q&A to dig a little deeper
Which segments drive our sales? Does it match the industry trend?
1. Select the “Total Units Overall by Segment” tile which will open Q&A.
2. Type for VanArsdel at the end of the existing query. Q&A interprets the question and displays an updated
chart with the answer. Our product volume comes from Convenience and Moderation.

3. Our share in the Moderation and Convenience categories is very high; these are the segments where we
compete.
4. Navigate back to the dashboard by selecting the dashboard name in the top navbar (breadcrumbs).
What does total unit market share look like for category (versus region )?
1. Notice the “Total Units YTD by Manufacturer, Region” tile. I wonder how the total unit market share looks
by category?
2. In the question box at the top of the dashboard, type the question total units by manufacturer and
category for 2014 as a treemap. Notice how the visualization updates as you type the question.

3. To compare the findings, pin the chart to your dashboard. Very interesting; in 2014 VanArsdel only sold
 products that fall into the Urban category.
4. Navigate back to the dashboard.
Dashboards are also an entry point into reports. If a tile was created from an underlying report, clicking that tile
opens the report.
On our dashboard, the R12M (Rolling 12 Months) line shows that our market share is no longer increasing over
time, it’s even declining a bit. And why do we have a big market share dip in June? To investigate further, click this
visualization to open the underlying report.
Our report has 4 pages
Page 1 of our report focuses on VanArsdel’s market share.

1. Look at the “Total Units by Month and isVanArsdel” column chart at the bottom. The black column
represents VanArsdel (our products) and green is our competition. The drop in June 2014 that VanArsdel
experienced is not experienced by the competition.
2. The “Total Category Volume by Segment” bar chart in the middle on the right, is filtered to show
VanArsdel’s top 2 segments. Take a look at how this filter was created:
a. Expand the Filters pane on the right.
b. Click to select the visualization.
c. Under Visual Level Filters, notice that Segment is filtered to include only Convenience and
Moderation.
d. Modify the filter by selecting Segment to expand that section and then checking Productivity to add that
segment as well.
3. In “Total Units by Month and isVanArsdel”, select the black “Yes” in the legend to cross-filter the page by
VanArsdel. Notice that we don’t compete in the Productivity segment.
4. Select the black “Yes” again to remove the filter.
5. Take a look at the line chart. It shows our monthly market share and 12 month rolling market shares. Rolling
12 months data help in smoothing out monthly fluctuations and shows the long term trends. Select
Convenience and then Moderation in the bar chart to see how much fluctuation in market share there is for
each segment. The Moderation segment shows much more fluctuation in market share than the
Convenience segment.
We’re still looking to find out why our market share dipped so low in June. Let’s check Sentiment.
Page 3 of our report focuses on Sentiment.
Tweets, Facebook, blogs, articles, etc. contribute to sentiment which is shown in the two line charts. The sentiment
chart in the top left shows that sentiment for our products were pretty much neutral up until February. Then a big
drop started in February and bottomed out in June. What happened to cause this drop in sentiment? We need to
look at external sources. In February, several articles and blog posts rated VanArsdel’s customer service the worst
in the industry. This bad press had a direct correlation to customer sentiment and sales. VanArsdel worked hard to
improve customer service and customers and the industry took note. In July positive sentiment started to rise and
then reached an all-time high in the 60s. This uptick in sentiment can be seen reflected in “Total Units by Month”
on pages 1 and 3. Perhaps this partially explains our market share dips for June?
Sentiment gap would be another area to explore: which districts have the highest sentiment gap, how can
management capitalize on this, and discover ways to replicate it in other districts.
Page 2 of our report focuses on YTD Category Trend

Of all the companies in this category, VanArsdel is the largest and our biggest competitors are Natura, Aliqui,
and Pirium. We’ll keep our eyes on them.
Aliqui is growing, but product volume compared to us is still low.
The treemap shows VanArsdel in green. In the East, customers prefer our competition, in Central we’re doing
OK, and our share in the East is our lowest.
Geography has an impact on units sold. East is the dominant region for most manufacturers and VanArsdel has
 a strong presence in the Central region as well.
On the chart “Total Units YTD Var % by Month and Manufacturer” in the bottom right– we have positive
variance and that is a good sign, we are doing better than last year but so is another competitor, Aliqui.
Page 4 of our report focuses on competitive product analysis.

The bottom left chart shows all the category segments except for VanArsdel’s two strongest segments. Filtering
by category by clicking on the bars helps identify potential expansion areas for VanArsdel. The Extreme and
Productivity segments are growing faster than others.
But we don’t compete in these segments. If we want to move into these areas, we can use our data to see which
segments are popular in which regions. We can further investigate questions like which region is growing faster
and who would be our biggest competitor in that segment.
Remember our market share dip in June? June is a huge month for the Productivity segment – a segment we
don’t compete in at all. This could help explain our market share dip in June.
By filtering the visualizations by VanArsdel, by segment, by month, and by region, we can discover growth
opportunities for VanArsdel.
This is a safe environment to play in. You can always choose not to save your changes. But if you do save them, you
can always go to Get Data for a new copy of this sample.

Next steps: Connect to your data

We hope this tour has shown how Power BI dashboards, Q&A, and reports can provide insights into sales and
marketing data. Now it’s your turn — connect to your own data. With Power BI you can connect to a wide variety
of data sources. Learn more about getting started with Power BI.
 Supplier Quality Analysis sample for Power BI: Take a
tour
1/14/2019 • 6 minutes to read • Edit Online

A brief overview of the Supplier Quality Analysis sample

This industry sample dashboard and underlying report focus on one of the typical supply chain challenges —
supplier quality analysis. Two primary metrics are at play in this analysis: total number of defects and the total
downtime that these defects caused. This sample has two main objectives:
Understand who the best and worst suppliers are, with respect to quality
Identify which plants do a better job finding and rejecting defects, to minimize downtime

This sample is part of a series that illustrates how you can use Power BI with business-oriented data, reports, and
dashboards. This is real data from obviEnce (www.obvience.com) that has been anonymized.

Prerequisites
Before you can use the sample, you must first download it as a content pack, .pbix file, or Excel workbook.
Get the content pack for this sample
1. Open the Power BI service (app.powerbi.com) and log in.
2. In the bottom left corner select Get data.

3. On the Get Data page that appears, select the Samples icon.
4. Select the Supplier Quality Analysis Sample, then choose Connect.

5. Power BI imports the content pack and adds a new dashboard, report, and dataset to your current
workspace. The new content is marked with a yellow asterisk.

Get the .pbix file for this sample

Alternatively, you can download the sample as a .pbix file, which is designed for use with Power BI Desktop.
Supplier Quality Analysis Sample PBIX
Get the Excel workbook for this sample
You can also download just the dataset (Excel workbook) for this sample. The workbook contains Power View
sheets that you can view and modify. To see the raw data select Power Pivot > Manage.

Downtime caused by defective materials

Let’s analyze the downtime caused by defective materials and see which vendors are responsible.
1. On the dashboard, select the Total Defect Quantity number tile or the Total Downtime Minutes
number tile.
 The “Supplier Quality Analysis Sample” report opens to the “Downtime Analysis” page. Notice we have
33M total defective pieces, and the total downtime caused by these defective pieces is 77K minutes. Some
materials have fewer defective pieces but they can cause a huge delay resulting in larger downtime. Let’s
explore them on the report page.
2. Looking at the Total Downtime Minutes line in the Defects and Downtime (min) by Material Type
combo chart, we see corrugate materials cause the most downtime.
3. Select the Corrugate column in the same combo chart to see which plants are impacted most by this defect
and which vendor is responsible.

4. Select individual plants in the map to see which vendor or material is responsible for the downtime at that
plant.
Which are the worst suppliers?
We want to find the worst eight suppliers and determine what percentage of the downtime they are responsible
for creating. We can do this by changing the Downtime (min) by Vendor area chart to a treemap.
1. On page 3 of the report, “Downtime Analysis,” select Edit Report in the upper-left corner.
2. Select the Downtime (min) by Vendor area chart, and in the Visualizations pane select Treemap.

The treemap automatically puts the Vendor field as the Group.

 From this tree map, we can see the top eight vendors are the eight blocks on the left of the tree map. We
can also see they account for about 50% of all downtime minutes.
3. Select Supplier Quality Analysis Sample in the top navigation bar to go back to the dashboard.
Comparing plants
Now let’s explore which plant does a better job managing defective material, resulting in less downtime.
1. Select the Total Defect Reports by Plant, Defect Type map tile.
The report opens to the “Supplier Quality” page.

2. In the map legend, select the Impact circle.

Notice in the bubble chart that Logistics is the most troubled category – it’s the largest in terms of total
defect quantity, total defect reports, and total downtime minutes. Let’s explore this category more.
3. Select the Logistics bubble in the bubble chart and observe the plants in Springfield, IL and Naperville, IL.
Naperville seems to be doing a much better job of managing defective supplies as it has a high number of
rejects and few impacts, compared to Springfield’s large number for impacts.

4. Select Supplier Quality Analysis Sample in the top navigation bar to return to your active workspace.

Which material type is best managed?

The best managed material type is the one with lowest downtime or no impact, regardless of defect quantity.
In the dashboard, look at the Total Defect Quantity by Material Type, Defect Type tile.

Notice that Raw Materials have a lot of total defects, but most of the defects are either rejected or have no impact.
Let’s verify that raw materials don’t cause a lot of downtime, despite high defect quantity.
In the dashboard, look at the Total Defect Qty, Total Downtime Minutes by Material Type tile.
Apparently raw materials are well managed: they have more defects, but lower total downtime minutes.
Compare defects to downtime by year
1. Select the Total Defect Reports by Plant, Defect Type map tile to open the report to the first report
page, Supplier Quality.
2. Notice that Defect Qty is higher in 2014 than in 2013.

3. Do more defects translate into more downtime? We can ask questions in the Q&A box to find out.
4. Select Supplier Quality Analysis Sample in the top navigation bar to go back to the dashboard.
5. Since we know Raw Materials have the highest number of defects, in the question box, type “show material
types, year and total defect qty”.
There were many more raw materials defects in 2014 than in 2013.
6. Now change the question to “show material types, year and total downtime minutes”.

Raw materials downtime was about the same in 2013 and 2014, even though there were many more raw
materials defects in 2014.
It turns out more raw materials defects in 2014 didn’t lead to much more raw materials downtime in 2014.
Compare defects to downtime month to month
Let’s look at another dashboard tile related to total defective quantity.

1. Select the back arrow in the upper-left corner above the question box to get back to the dashboard.
Looking more closely at the Total Defect Quantity by Month, Year tile shows that the first half of 2014
had a similar number of defects as 2013, but in the second half of 2014, the number of defects jumped
significantly.
 Let’s see if this increase in defect quantity led to an equal increase in downtime minutes.
2. In the question box, type “total downtime minutes by month and year as a line chart”.

We do see a jump in downtime minutes during June and Oct, but other than that, the jump in the number of
defects didn’t result in significantly more downtime. This shows we’re managing defects well.
3. To pin this chart to your dashboard, select the pin icon to the right of the question box.
4. To explore the outlier months, check out the downtime minutes during Oct by material type, plant location,
category, etc. by asking questions such as "total downtime minutes in October by plant".

5. Select the back arrow in the upper-left corner above the question box to get back to the dashboard.
This is a safe environment to play in. You can always choose not to save your changes. But if you do save them,
you can always go to Get Data for a new copy of this sample.

Next steps: Connect to your data

We hope this tour has shown how Power BI dashboards, Q&A, and reports can provide insights into supplier
quality data. Now it’s your turn — connect to your own data. With Power BI you can connect to a wide variety of
data sources. Learn more about getting started with Power BI.
 Download the Financial Sample workbook for Power
BI
1/14/2019 • 2 minutes to read • Edit Online

Need some data to try with Power BI service? We have a simple Excel workbook of sample financial data available
for download. Here's how to download it:
Financial sample Excel workbook: download the sample directly.
This workbook has one table of data of sales and profit data by market segment and country/region.
Next steps
Get Data
How to import Excel data
Other data you can try with Power BI -- Sample datasets and content packs
More questions? Try the Power BI Community
 What's new in the latest Power BI Desktop update?
3/29/2019 • 2 minutes to read • Edit Online

March 2019 Update (2.67.5404.581)

Our March updates are packed full of compelling and useful updates, and we hope these improvements make you
feel as lucky as finding a four-leaf clover.
You can now download the latest version of Power BI Desktop. If you're running Windows 10, you can also get
Power BI Desktop from the Windows Store. The monthly versions are the same even though the version
numbering may differ between the two, regardless of which way you install Power BI Desktop. See this article
for more information.
The links beside each update mean the following:
[video] excerpts play in a new browser tab, when the feature is being discussed.
Some features have an [article] that provides more detail.
Most features are explained in the monthly update [blog] post.
Lastly, some features are self-explanatory and don't need and article or video.
You can also watch the Latest Updates video from the beginning, right inside this article, by clicking on the play
icon on the video image found below the list of updates.
The following updates are new to Power BI Desktop this month:
Reporting
Single select slicer [video] [blog]
Heat map support for Bing maps [video] [blog]
Cross-highlight by axis labels [video] [blog]
Default tooltip formatting [video] [blog]
Static web URL support for buttons, shapes and images [video] [blog]
Filter pane improvements [video] [blog]
Page alignment options [video] [blog]
Selection pane improvements [video] [blog]
Formatting updates for maps [video] [blog]
Accessible visual interaction [video] [blog]
Analytics
Q&A recommendations for improving results [video] [blog]
Show dates as a hierarchy now generally available [video] [blog]
Modeling
New modeling view now generally available [video] [blog]
New DAX functions [video] [blog]
Custom visuals
New certified custom visuals setting in the admin portal [video] [blog]
Two new custom visuals [video] [blog]
Data connectivity
 PDF connector now supports tables spanning multiple pages (preview ) [video] [blog]
Intelligent Plant's Industrial App Store connector [video] [blog]
Azure Cost Management connector [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video channel describes and shows each of these updates. You can also see the videos from the blog
post.
https://www.youtube.com/embed/rBPGH6eYlT0

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

More videos
Like learning about Power BI through videos and other engaging content? Check out the following collection of
video sources and content.
Power BI channel - Power BI on YouTube
Guy in a Cube channel - fresh videos on Power BI features and capabilities
Guided Learning for Power BI - a sequential learning tour of Power BI, in bite-size pieces

Previous months' updates

Looking for previous months' updates? You can find them in the Power BI Desktop Monthly Updates archive
article.
 Modeling view in Power BI Desktop (preview)
2/13/2019 • 2 minutes to read • Edit Online

With the Modeling view in Power BI Desktop, you can view and work with complex datasets that contain many
tables. With Modeling view, you can do the following:

Enabling the Modeling view preview feature

The modeling view feature is in preview and must be enabled in Power BI Desktop. To enable Modeling view,
select File > Options and Settings > Options > Preview Features, then select the Modeling view checkbox as
shown in the following image.

You'll be prompted that you need to restart Power BI Desktop for the preview feature to be enabled.
Using Modeling view
To access Modeling view, select the Modeling view icon found on the left side of Power BI Desktop, as shown in
the following image.

Creating separate diagrams

With Modeling view, you can create diagrams of your model that contain only a subset of the tables in your model.
This can help provide a clearer view into the tables you want to work with, and make working with complex
datasets easier. To create a new diagram with only a subset of the tables, click the + sign next to the All tables tab
along the bottom of the Power BI Desktop window.

You can then drag a table from the Fields list onto the diagram surface. Right click the table, and then select Add
related tables from the menu that appears.
When you do, tables that are related to the original table are displayed in the new diagram. The following image
shows how related tables are displayed after selecting the Add related tables menu option.

Setting common properties

You can select multiple objects at once in Modeling view by holding down the CTRL key and clicking multiple
tables. When you select multiple tables they become highlighted in Modeling view. When multiple tables are
highlighted, changes applied in the Properties pane apply to all selected tables.
For example, you could change the storage mode for multiple tables in your diagram view by holding down the
CTRL key, selecting tables, then changing the storage mode setting in the Properties pane.
Next steps
The following articles describe more about data models, and also describe DirectQuery in detail.
Aggregations in Power BI Desktop (Preview )
Composite models in Power BI Desktop (Preview )
Storage Mode in Power BI Desktop (Preview )
Many-to-many relationships in Power BI Desktop (Preview )
DirectQuery articles:
Using DirectQuery in Power BI
Data sources supported by DirectQuery in Power BI
 Aggregations in Power BI Desktop (Preview)
1/14/2019 • 13 minutes to read • Edit Online

Using aggregations in Power BI enables interactive analysis over big data in ways that previously weren't
possible. Aggregations can dramatically reduce the cost of unlocking large datasets for decision making.

The following list provides advantages to using aggregations:

Query performance over big data - as users interact with visuals on Power BI reports, DAX queries are
submitted to the dataset. Boost query speeds by caching data at the aggregated level, using a fraction of the
resources required at the detail level. Unlock big data in a way that would otherwise be impossible.
Data refresh optimization - reduce cache sizes and refresh times by caching data at the aggregated level.
Speed up the time to make data available for users.
Achieve balanced architectures - allow the Power BI in-memory cache to handle aggregated queries, which
it does effectively. Limit queries sent to the data source in DirectQuery mode, helping stay within concurrency
limits. Queries that do get through tend to be filtered, transactional-level queries, which data warehouses and
big-data systems normally handle well.
Table -level storage
Table-level storage is normally used with the aggregations feature. See the storage mode in Power BI Desktop
article for more information.
Data source types
Aggregations are used with data sources representing dimensional models, such as a data warehouses, data
marts, and Hadoop-based big-data sources. This article describes typical modeling differences in Power BI for
each type of data source.
All Power BI Import and (non-multidimensional) DirectQuery sources work with aggregations.

Enabling the aggregations preview feature

The aggregations feature is in Preview, and must be enabled in Power BI Desktop. To enable aggregations,
select File > Options and Settings > Options > Preview Features, then select the composite models and the
Manage aggregations checkboxes.

You'll need to restart Power BI Desktop for the feature to be enabled.

Aggregations based on relationships

Aggregations based on relationships are typically used with dimensional models. Power BI datasets that source
from data warehouses and data marts resemble star/snowflake schemas with relationships between dimension
tables and fact tables.
Consider the following model, which is from a single data source. Let’s say all the tables are using DirectQuery to
start with. The Sales fact table contains billions of rows. Setting the storage mode of Sales to Import for caching
would consume considerable memory and management overhead.

Instead, we create the Sales Agg table as an aggregation table. It's at a higher granularity than Sales, so it'll
contain far fewer rows. The number of rows should equal the sum of SalesAmount grouped by CustomerKey,
DateKey, and ProductSubcategoryKey. Instead of billions, it might be millions of rows, which are much easier
to manage.
Let's assume that the following dimension tables are the most commonly used for the queries with high business
value. They're the tables that can filter Sales Agg using one-to -many (or many-to -one) relationships.
Geography
Customer
Date
Product Subcategory
Product Category
The following image shows this model.
 NOTE
The Sales Agg table is just another table, so it has the flexibility of being loaded in a variety of ways. For example,
aggregation can be performed in the source database using ETL/ELT processes, or by the M expression for the table. It can
use Import storage mode with or without incremental refresh in Power BI Premium, or it can be DirectQuery and optimized
for fast queries using columnstore indexes. This flexibility enables balanced architectures that spread query load to avoid
bottlenecks.

Storage mode
Let's continue with the example we're using. We set the storage mode of Sales Agg to Import to speed up
queries.

When we do so, the following dialog appears, letting us know that the related dimension tables can be set to
storage mode Dual.
Setting them to Dual allows the related dimension tables to act as either Import or DirectQuery depending on the
subquery.
Queries that aggregate metrics from the Sales Agg table, which is Import, and group by attribute(s) from the
related Dual tables can be returned from the in-memory cache.
Queries that aggregate metrics in the Sales table, which is DirectQuery, and group by attribute(s) from the
related Dual tables can be returned in DirectQuery mode. The query logic including the group by operation will
be passed down to the source database.
For more information on the Dual storage mode, see the storage mode article.
Strong vs. weak relationships
Aggregations hits based on relationships require strong relationships.
Strong relationships include the following combinations where both tables are from a single source.

TABLE ON THE *MANY SIDES TABLE ON THE 1 SIDE

Dual Dual

Import Import or Dual

DirectQuery DirectQuery or Dual

The only case where a cross-source relationship is considered strong is if both tables are Import. Many-to-many
relationships are always considered weak.
For cross-source aggregation hits that don't depend on relationships, see section below on aggregations based on
group-by columns.
Aggregation table is hidden
The Sales Agg table is hidden. Aggregation tables should always be hidden from consumers of the dataset.
Consumers and queries refer to the detail table, not the aggregation table; they don't even need to know the
aggregation table exists.
Manage aggregations dialog
Next we define the aggregations. Select the Manage aggregations context menu for the Sales Agg table, by
right-clicking on the table.

The Manage aggregations dialog is displayed. It shows a row for each column in the Sales Agg table, where we
can specify the aggregation behavior. Queries submitted to the Power BI dataset that refers to the Sales table are
internally redirected to the Sales Agg table. Consumers of the dataset don't need to know the Sales Agg table
even exists.
The following table shows the aggregations for the Sales Agg table.

Summarization function
The Summarization drop-down offers the following values for selection.
Count
GroupBy
Max
Min
Sum
Count table rows
Validations
The following notable validations are enforced by the dialog:
The detail column selected must have the same datatype as the aggregation column except for the Count and
Count table rows summarization functions. Count and Count table rows are only offered for integer
 aggregation columns, and don't require a matching datatype.
Chained aggregations covering three or more tables aren't allowed. For example, it is not possible to set up
aggregations on Table A referring to Table B that has aggregations referring to Table C.
Duplicate aggregations where two entries use the same summarization function and refer to the same detail
table/column aren't allowed.
During this public preview for aggregations, the following validations are also enforced. We intend to remove
these validations upon releasing for general availability.
Aggregations cannot be used with row -level security (RLS ). Public preview limitation.
Detail table must be DirectQuery, not Import. Public preview limitation.
Most such validations are enforced by disabling dropdown values and showing explanatory text in the tooltip, as
shown in the following image.

Group by columns
In this example, the three GroupBy entries are optional; they do not affect aggregation behavior (except for the
DISTINCTCOUNT example query, shown in the upcoming image). They are included primarily for readability
purposes. Without these GroupBy entries, the aggregations would still get hit based on the relationships. This is
different behavior from using aggregations without relationships, which is covered by the big data example that
follows later in this article.
Detecting whether aggregations are hit or missed by queries
For more information about how to detect whether queries are returned from the in-memory cache (storage
engine), or DirectQuery (pushed to the data source) using SQL Profiler, see the storage mode article. That process
can also be used to detect whether aggregations are being hit, too.
Additionally, the following extended event is provided in SQL Profiler.

Query Processing\Aggregate Table Rewrite Query

The following JSON snippet shows an example of the output of the event when an aggregation is used.
matchingResult shows that an aggregation was used for the subquery.
dataRequest shows the group-by column(s) and aggregated column(s) used by the subquery.
mapping shows the columns in the aggregation table that were mapped to.
Query examples
The following query hits the aggregation, because columns in the Date table are at the granularity that can hit the
aggregation. The Sum aggregation for SalesAmount will be used.

The following query doesn't hit the aggregation. Despite requesting the sum of SalesAmount, it's performing a
group by operation on a column in the Product table, which is not at the granularity that can hit the aggregation.
If you observe the relationships in the model, a product subcategory can have multiple Product rows; the query
wouldn't be able to determine which product to aggregate to. In this case, the query reverts to DirectQuery and
submits a SQL query to the data source.
Aggregations aren't just for simple calculations that perform a straightforward sum. Complex calculations can also
benefit. Conceptually, a complex calculation is broken down into subqueries for each SUM, MIN, MAX and
COUNT, and each subquery is evaluated to determine if the aggregation can be hit. This logic doesn't hold true in
all cases due to query-plan optimization, but in general it should apply. The following example hits the
aggregation:

The COUNTROWS function can benefit from aggregations. The following query hits the aggregation because
there is a Count table rows aggregation defined for the Sales table.

The AVERAGE function can benefit from aggregations. The following query hits the aggregation because
AVERAGE internally gets folded to a SUM divided by a COUNT. Since the UnitPrice column has aggregations
defined for both SUM and COUNT, the aggregation is hit.

In some cases, the DISTINCTCOUNT function can benefit from aggregations. The following query hits the
aggregation because there is a GroupBy entry for CustomerKey, which maintains the distinctness of
CustomerKey in the aggregation table. This technique is still subject to the performance threshold where over
approximately two to five million distinct values can affect query performance. However, it can be useful in
scenarios where there are billions of rows in the detail table and two to five million distinct values in the column. In
this case, the distinct count can perform faster than scanning the table with billions of rows, even if it were cached
into memory.
Aggregations based on group-by columns
Hadoop-based big data models have different characteristics than dimensional models. To avoid joins between
large tables, they often don't rely on relationships. Instead, dimension attributes are often denormalized to fact
tables. Such big data models can be unlocked for interactive analysis using aggregations based on group-by
columns.
The following table contains the Movement numeric column to be aggregated. All other columns are attributes to
group by. It contains IoT data and a massive number of rows. The storage mode is DirectQuery. Queries on the
data source that aggregate across the whole dataset are slow because of the sheer volume.

To enable interactive analysis on this dataset, we add an aggregation table that groups by most of the attributes
but excludes the high cardinality attributes like longitude and latitude. This dramatically reduces the number of
rows, and is small enough to comfortably fit into an in-memory cache. The storage mode of Driver Activity Agg
is Import.
Next, we define the aggregation mappings in the Manage aggregations dialog. It displays a row for each column
in the Driver Activity Agg table, where we can specify the aggregation behavior.
The following table shows the aggregations for the Driver Activity Agg table.

Group by columns
In this example, the GroupBy entries are not optional; without them the aggregations wouldn't get hit. This is
different behavior to using aggregations based on relationships, which is covered by the dimensional model
example provided previously in this article.
Query examples
The following query hits the aggregation because the Activity Date column is covered by the aggregation table.
The Count table rows aggregation is used by the COUNTROWS function.

Especially for models that contain filter attributes in fact tables, it's a good idea to use Count table rows
aggregations. Power BI may submit queries to the dataset using COUNTROWS in cases where it is not explicitly
requested by the user. For example, the filter dialog shows the count of rows for each value.

Aggregation precedence
Aggregation precedence allows multiple aggregation tables to be considered by a single subquery.
Consider the following example. It's a composite model containing multiple DirectQuery sources.
The Driver Activity Agg2 Import table is at a high granularity because the group-by attributes are few and
low cardinality. The number of rows could be as low as thousands, so it can easily fit into an in-memory cache.
These attributes happen to be used by a high-profile executive dashboard, so queries referring to them should
be as fast as possible.
The Driver Activity Agg table is an intermediate aggregation table in DirectQuery mode. It contains over a
billion rows and is optimized at the source using columnstore indexes.
The Driver Activity table is DirectQuery and contains over a trillion rows of IoT data sourced from a big-data
system. It serves drillthrough queries to view individual IoT readings in controlled filter contexts.
The memory footprint of this model is relatively small, but it unlocks a huge dataset. It represents a balanced
architecture because it spreads the query load across components of the architecture utilizing them based on their
strengths.
The Manage aggregations dialog for Driver Activity Agg2 shows the Precedence field is 10, which is higher
than that of Driver Activity Agg, which means it will be considered first by queries using aggregations.
Subqueries that are not at the granularity that can be answered by Driver Activity Agg2 will consider Driver
Activity Agg instead. Detail queries that cannot be answered by either aggregation table will be directed to
Driver Activity.
The table specified in the Detail Table column is Driver Activity, not Driver Activity Agg because chained
aggregations are not allowed (see validations earlier in this article).
The following table shows the aggregations for the Driver Activity Agg2 table.

Aggregations based on group-by columns combined with relationships

You can even combine the two techniques for aggregations described earlier in this article. Aggregations based
on relationships may require the denormalized dimension tables be split into multiple tables. If this is costly or
impractical for certain dimension tables, the necessary attributes can be replicated in the aggregation table for
certain dimension(s) and relationships used for others.
The following model replicates Month, Quarter, Semester, and Year in the Sales Agg table. There is no
relationship between Sales Agg and the Date table. There are relationships to Customer and Product
Subcategory. The storage mode of Sales Agg is Import.
The following table shows the entries set in the Manage aggregations dialog for the Sales Agg table. The
GroupBy entries where Date is the detail table are mandatory to hit aggregations for queries that group by the
Date attributes. As in the previous example, the GroupBy entries for CustomerKey and ProductSubcategoryKey do
not affect aggregation hits because of the presence of relationships (again with the exception of
DISTINCTCOUNT).

Note: This model requires that the Date table be in DirectQuery mode to fill in the manage aggregations
dialog, because it is a detail table. This is a Preview limitation that we intend to remove for General Availability.

Query examples
The following query hits the aggregation because CalendarMonth is covered by the aggregation table, and
CategoryName is accessible via one-to-many relationships. The Sum aggregation for SalesAmount is used.
The following query doesn't hit the aggregation because CalendarDay is not covered by the aggregation table.

The following time-intelligence query will not hit the aggregation because the DATESYTD function generates a
table of CalendarDay values, which is not covered by the aggregation table.

Caches should be kept in sync

Aggregations that combine DirectQuery and Import and/or Dual storage mode may return different data if the
in-memory cache is not kept in sync with the source data. Query execution won't attempt to mask data issues by,
for example, filtering DirectQuery results to match cached values. These features are performance optimizations
and should be used only in ways that do not compromise your ability to meet business requirements. It's your
responsibility to know your data flows, so please design accordingly. There are established techniques to handle
such issues at the source, if necessary.

Next steps
The following articles describe more about composite models, and also describe DirectQuery in detail.
Composite models in Power BI Desktop (Preview )
Many-to-many relationships in Power BI Desktop (Preview )
Storage Mode in Power BI Desktop (Preview )
DirectQuery articles:
Using DirectQuery in Power BI
Data sources supported by DirectQuery in Power BI
 Use composite models in Power BI Desktop
1/14/2019 • 11 minutes to read • Edit Online

Previously in Power BI Desktop, when you used a DirectQuery in a report, no other data connections—whether
DirectQuery or Import—were allowed for that report. With composite models, that restriction is removed. A
report can seamlessly include data connections from more than one DirectQuery or Import data connection, in
any combination you choose.

The composite models capability in Power BI Desktop consists of three related features:
Composite models: Allows a report to have multiple data connections, including DirectQuery
connections or Import, in any combination. This article describes composite models in detail.
Many-to-many relationships: With composite models, you can establish many-to -many relationships
between tables. This approach removes requirements for unique values in tables. It also removes previous
workarounds, such as introducing new tables only to establish relationships. For more information, see
Many-to-many relationships in Power BI Desktop (preview ).
Storage mode: You can now specify which visuals require a query to back-end data sources. Visuals that
don't require a query are imported even if they're based on DirectQuery. This feature helps improve
performance and reduce back-end load. Previously, even simple visuals such as slicers initiated queries
that were sent to back-end sources. For more information, see Storage mode in Power BI Desktop
(preview ).

Use composite models

With composite models, you can connect to a variety of data sources when you use Power BI Desktop or the
Power BI service. You can make those data connections in a couple of ways:
By importing data to Power BI, which is the most common way to get data.
By connecting directly to data in its original source repository by using DirectQuery. To learn more about
DirectQuery, see Use DirectQuery in Power BI.
When you use DirectQuery, composite models makes it possible to create a Power BI model (such as a single
.pbix Power BI Desktop file) that does either or both of the following:
Combines data from one or more DirectQuery sources.
 Combines data from DirectQuery sources and Import data.
For example, by using composite models, you can build a model that combines the following types of data:
Sales data from an enterprise data warehouse.
Sales-target data from a departmental SQL Server database.
Data that's imported from a spreadsheet.
A model that combines data from more than one DirectQuery source or that combines DirectQuery with Import
data is called a composite model.

NOTE
Beginning with the October 2018 release of Power BI Desktop, you can publish composite models to the Power BI service.
For scheduled refresh and dashboard tile refresh, composite models in the Power BI service behave in the same way as
Import models.

You can create relationships between tables as you always have, even when those tables come from different
sources, with the following restriction: any relationships that are cross-source must be defined as having a
cardinality of many-to -many, regardless of their actual cardinality. The behavior of such relationships is then the
same as normal for many-to -many relationships, as described in Many-to-many relationships in Power BI
Desktop (preview ).

NOTE
Within the context of composite models, all imported tables are effectively a single source, regardless of the actual
underlying data source from which they are imported.

Example of a composite model

For an example of a composite model, consider a report that has connected to a corporate data warehouse in
SQL Server by using DirectQuery. In this instance, the data warehouse contains Sales by Country, Quarter, and
Bike (Product) data, as shown in the following image:

At this point, you could build simple visuals by using fields from this source. For example, the following image
shows total sales by ProductName, for a selected quarter.
But what if you have data in an Office Excel spreadsheet about the product manager who's assigned to each
product, along with the marketing priority? If you want to view Sales Amount by Product Manager, it might not
be possible to add this local data to the corporate data warehouse. Or it might take months at best.
It might be possible to import that sales data from the data warehouse, instead of using DirectQuery. And the
sales data could then be combined with the data that you imported from the spreadsheet. However, that
approach is unreasonable, for the reasons that lead to using DirectQuery in the first place. The reasons could
include:
Some combination of the security rules enforced in the underlying source.
The need to be able to view the latest data.
The sheer scale of the data.
Here's where composite models come in. Composite models let you connect to the data warehouse by using
DirectQuery and then use GetData for additional sources. In this example, we first establish the DirectQuery
connection to the corporate data warehouse. We use GetData, choose Excel, and then navigate to the
spreadsheet that contains our local data. Finally, we import the spreadsheet that contains the Product Names, the
assigned Sales Manager, and the Priority.
In the Fields list, you can see two tables: the original Bike table from SQL Server and a new ProductManagers
table. The new table contains the data that's imported from Excel.
Similarly, in the Relationship view in Power BI Desktop, we now see an additional table called
ProductManagers.

We now need to relate these tables to the other tables in the model. As always, we create a relationship between
the Bike table from SQL Server and the imported ProductManagers table. That is, the relationship is between
Bike[ProductName] and ProductManagers[ProductName]. As discussed earlier, all relationships that go across
source must have the default many-to -many cardinality.

Now that we've established this relationship, it's displayed in the Relationship view in Power BI Desktop, as we
would expect.

We can now create visuals by using any of the fields in the Fields list. This approach seamlessly blends data from
multiple sources. For example, the total SalesAmount for each Product Manager is displayed in the following
image:
The following example displays a common case of a dimension table—such as Product or Customer—that's
extended with some extra data imported from somewhere else. It's also possible to have tables use DirectQuery
to connect to various sources. To continue with our example, imagine that Sales Targets per Country and Period
are stored in a separate departmental database. As usual, you can use GetData to connect to that data, as shown
in the following image:
As we did earlier, we can create relationships between the new table and other tables in the model and then
create visuals that combine the table data. Let's look again at the Relationships view, where we've established
the new relationships:

The next image is based on the new data and relationships we created. The visual at the lower left shows total
Sales Amount versus Target, and the variance calculation shows the difference. The Sales Amount and Target
data come from two different SQL Server databases.
Set the storage mode
Each table in a composite model has a storage mode that indicates whether the table is based on DirectQuery or
Import. The storage mode can be viewed and modified in the Property pane. To display the storage mode, right-
click a table in the Fields list, and then select Properties. The following image shows the storage mode for the
SalesTargets table.

The storage mode can also be viewed on the tooltip for each table.
For any Power BI Desktop file (a .pbix file) that contains some tables from DirectQuery and some Import tables,
the status bar displays a storage mode called Mixed. You can click that term in the status bar and easily switch all
tables to Import.
For more information about storage mode, see Storage mode in Power BI Desktop (preview ).

Calculated tables
You can add calculated tables to a model that uses DirectQuery. The Data Analysis Expressions (DAX) that define
the calculated table can reference either imported or DirectQuery tables or a combination of the two.
Calculated tables are always imported, and their data is refreshed when you refresh the tables. If a calculated
table refers to a DirectQuery table, visuals that refer to the DirectQuery table always show the latest values in the
underlying source. Alternatively, visuals that refer to the calculated table show the values at the time when the
calculated table was last refreshed.

Security implications
Composite models have some security implications. A query sent to one data source can include data values that
have been retrieved from another source. In the earlier example, the visual that shows Sales Amount by Product
Manager sends a SQL query to the Sales relational database. That SQL query might contain the names of
Product Managers and their associated Products.

Consequently, information that's stored in the spreadsheet is now included in a query that's sent to the relational
database. If this information is confidential, you should consider the security implications. In particular, consider
the following points:
Any administrator of the database who can view traces or audit logs could view this information, even
 without permissions to the data in its original source. In this example, the administrator would need
permissions to the Excel file.
The encryption settings for each source should be considered. You want to avoid retrieving information
from one source via an encrypted connection and then inadvertently including it in a query that's sent to
another source via an unencrypted connection.
To allow confirmation that you have considered any security implications, Power BI Desktop displays a warning
message when you create a composite model.
For similar reasons, be careful when you open a Power BI Desktop file that's sent from an untrusted source. If the
file contains composite models, information that someone retrieves from one source by using the credentials of
the user who opens the file would be sent to another data source as part of the query. The information could be
viewed by the malicious author of the Power BI Desktop file. Therefore, when you initially open a Power BI
Desktop file that contains multiple sources, Power BI Desktop displays a warning. The warning is similar to the
one that's displayed when you open a file that contains native SQL queries.

Performance implications
When you use DirectQuery, you should always consider performance, primarily to ensure that the back-end
source has sufficient resources to provide a good experience for users. A good experience means that the visuals
refresh in five seconds or less. You should also follow the performance advice in the Use DirectQuery in Power BI
article.
Using composite models adds additional performance considerations. A single visual can result in sending
queries to multiple sources, which often passes the results from one query across to a second source. This
situation can result in the following forms of execution:
A SQL query that includes a large number of literal values: For example, a visual that requests total
Sales Amount for a set of selected Product Managers would first need to find which Products were
managed by those product managers. This sequence must happen before the visual sends a SQL query
that includes all of the product IDs in a WHERE clause.
A SQL query that queries at a lower level of granularity, with the data then being aggregated
locally: As the number of Products that meet the filter criteria on Product Manager grows large, it can
become inefficient or unfeasible to include all products in a WHERE clause. Instead, you can query the
relational source at the lower level of Product and then aggregate the results locally. If the cardinality of
Products exceeds a limit of 1 million, the query fails.
Multiple SQL queries, one per group by value: When the aggregation uses DistinctCount and is
grouped by a column from another source, and if the external source does not support efficient passing of
many literal values that define the grouping, it's necessary to send one SQL query per group by value.
For example, a visual that requests a distinct count of CustomerAccountNumber (from the SQL Server
table) by Product Manager (imported from the spreadsheet) would need to pass in the details from the
Product Managers table in the query that's sent to SQL Server. Over other sources (Redshift, for
example), this action is unfeasible. Instead, there would be one SQL query sent per Sales Manager—up to
some practical limit, at which point the query would fail.
Each of these cases has its own implications on performance, and the exact details vary for each data source.
Although the cardinality of the columns used in the relationship that joins the two sources remains low (a few
thousand), performance should not be affected. As this cardinality grows, you should pay more attention to the
impact on the resulting performance. Apply this guidance as a good rule of thumb.
Additionally, the use of many-to -many relationships means that separate queries must be sent to the underlying
source for each total or subtotal level, rather than aggregating the detailed values locally. A simple table visual
with totals would send two SQL queries, rather than one.

Limitations and considerations

This release of composite models presents a few limitations.
The following Live Connect (multi-dimensional) sources can't be used with composite models:
SAP HANA
SAP Business Warehouse
SQL Server Analysis Services
Power BI datasets
Azure Analysis Services
When you connect to these multi-dimensional sources by using DirectQuery, you can't connect to another
DirectQuery source or combine it with Import data.
The existing limitations of DirectQuery still apply when you use composite models. Many of these limitations are
now per table, depending upon the storage mode of the table. For example, a calculated column on an Import
table can refer to other tables, but a calculated column on a DirectQuery table can still refer only to columns on
the same table. Other limitations apply to the model as a whole, if any of the tables within the model are
DirectQuery. For example, the QuickInsights and Q&A features aren't available on a model if any of the tables
within it has a storage mode of DirectQuery.

Next steps
For more information about composite models and DirectQuery, see the following articles:
Many-to-many relationships in Power BI Desktop (preview )
Storage mode in Power BI Desktop (preview )
Use DirectQuery in Power BI
Data sources supported by DirectQuery in Power BI
 Relationships with a many-many cardinality in Power
BI Desktop
2/13/2019 • 8 minutes to read • Edit Online

With the relationships with a many-many cardinality feature in Power BI Desktop, you can join tables that use a
cardinality of Many to Many. You can more easily and intuitively create data models that contain two or more
data sources. The relationships with a many-many cardinality feature is part of the larger composite models
capabilities in Power BI Desktop.

The relationships with a many-many cardinality capability in Power BI Desktop is one of three related features:
Composite models: Allows a report to have two or more data connections, including DirectQuery
connections or Import, in any combination. For more information, see Composite models in Power BI
Desktop (preview ).
Relationships with a many-many cardinality: With composite models, you can establish relationships
with a many-many cardinality between tables. This approach removes requirements for unique values in
tables. It also removes previous workarounds, such as introducing new tables only to establish
relationships. The feature is described further in this article.
Storage mode: You can now specify which visuals require a query to back-end data sources. Visuals that
don't require a query are imported even if they're based on DirectQuery. This feature helps improve
performance and reduce back-end load. Previously, even simple visuals such as slicers began queries that
 were sent to back-end sources. For more information, see Storage mode in Power BI Desktop (preview ).

What relationships with a many-many cardinality solves

Before the relationships with a many-many cardinality feature became available, the relationship between two
tables was defined in Power BI. At least one of the table columns involved in the relationship had to contain
unique values. Often, though, no columns contained unique values.
For example, two tables might have had a column labeled Country, but the values of Country weren't unique in
either table. To join such tables, it was necessary to create a workaround. One such workaround might be to
introduce into the model additional tables with the necessary unique values. With the relationships with a many-
many cardinality feature, you can join such tables directly by using a relationship with a cardinality of Many to-
Many.

Use relationships with a many-many cardinality

When you define a relationship between two tables in Power BI, you must define the cardinality of the
relationship. For example, the relationship between ProductSales and Product—using columns
ProductSales[ProductCode] and Product[ProductCode]—would be defined as Many-1. We define the
relationship in this way because there are many sales for each product, and the column in the Product table
(ProductCode) is unique. When you define a relationship cardinality as Many-1, 1 -Many, or 1 -1, Power BI
validates it to help ensure that the cardinality that you select matches the actual data.
For example, take a look at the simple model in the following image:

Now, imagine that the Product table displays just two rows, as shown:

Also imagine that the Sales table has just four rows, including a row for a product C. Because of a referential
integrity error, the product C row doesn't exist in the Product table.

The ProductName and Price (from the Product table), along with the total Qty for each product (from the
ProductSales table), would be displayed as shown:
As you can see in the preceding image, there's blank ProductName row that's associated with sales for product C.
This blank row accounts for the following:
Any rows in the ProductSales table for which no corresponding row exists in the Product table. There's a
referential integrity issue, as we see for product C in this example.
Any rows in the ProductSales table for which the foreign key column is null.
For these reasons, the blank row in both cases accounts for sales where the ProductName and Price are
unknown.
It sometimes happens that the tables are joined by two columns, yet neither column is unique. For example,
consider the following two tables:
The Sales table displays sales data by State, and each row contains the sales amount for the type of sale in
that state. The states include CA, WA, and TX.

The CityData table displays data on cities, including the population and state (including CA, WA, and New
York).

Although there's a column for State in both tables and it's reasonable to want to report on both total sales by
state and total population of each state, a problem exists: the State column isn't unique in either table.

The previous workaround

In earlier Power BI Desktop versions than the July 2018 release, users couldn't create a direct relationship
between these tables. A common workaround was to do the following:
Create a third table that contains only the unique State IDs. The table could be any or all of the following:
 A calculated table (defined by using Data Analysis Expressions [DAX]).
A table based on a query that's defined in Query Editor, which could display the unique IDs drawn
from one of the tables.
The combined full set.
Relate the two original tables to that new table by using common Many-1 relationships.
You could either leave the workaround table visible or hide it so that it doesn't appear in the Fields list. If you
hide the table, the Many-1 relationships would commonly be set to filter in both directions, and you could use the
State field from either table. The subsequent cross filtering would propagate to the other table. That approach is
shown in the following image:

A visual that displays State (from the CityData table), along with total Population and total Sales, would then
appear as follows:

NOTE
Because the state from the CityData table is used in this workaround, only the states in that table are listed and, therefore,
TX is excluded. Also, unlike Many-1 relationships, while the total row includes all Sales (including those of TX), the details do
not include a blank row covering such mismatched rows. Similarly, there would be no blank row covering Sales for which
there's a null value for the State.

If you also add City to that visual, although the population per City is known, the Sales shown for City simply
repeats the Sales for the corresponding State. This is normally the case when the grouping in a column is
unrelated to some aggregate measure, as shown in the following image:
If we define the new Sales table as the combination of all States in this workaround and we make it visible in the
Fields list, the same visual would display both State (on the new table) and the total Population and total Sales,
as shown in the following image:

As you can see, TX—with Sales data but unknown Population data—and New York—with known Population
data but no Sales data—would be included. This workaround isn't optimal, and it has many issues. With the
creation of the relationships with a many-many cardinality, the resulting issues are addressed as described in the
next section.

Use relationships with a many-many cardinality instead of the

workaround
As of the July 2018 version of Power BI Desktop, you can directly relate tables, such as the ones we described
earlier, without having to resort to similar workarounds. It's now possible to set the relationship cardinality to
Many to Many. This setting indicates that neither table contains unique values. For such relationships, you can
still control which table filters the other table, or apply bi-directional filtering where each table filters the other.
In Power BI Desktop, the cardinality defaults to Many to Many when it determines that neither table contains
unique values for the columns in the relationship. In such cases, a warning is displayed to confirm that
relationship-setting is your intended behavior and not the unintended effect of a data issue.
For example, when you create a relationship directly between CityData and Sales—where filters should flow
from CityData to Sales—Power BI Desktop displays the Edit relationship window as shown in the following
image:
The resulting Relationship view would then display the direct, many-to-many relationship between the two
tables. The tables' appearance in the Fields list, and their subsequent behavior when the visuals are created, is
similar to when we applied the workaround. In the workaround, the extra table that displays the distinct State
data isn't made visible. For example, as described in the preceding section, a visual showing State, Population,
and Sales data would be displayed as follows:

The major differences between relationships with a many-many cardinality and the more typical Many-1
relationships are as follows:
The values shown don't include a blank row that accounts for mismatched rows in the other table. Nor do
the values account for rows where the column used in the relationship in the other table is null.
It isn't possible to use the RELATED() function, because more than one row could be related.
Using the ALL() function on a table doesn't remove filters that are applied to other, related tables by a
many-to-many relationship. In the preceding example, a measure that's defined as shown in the following
script would not remove filters on columns in the related CityData table:
 A visual showing State, Sales, and Sales total data would result in the following:

With the preceding differences in mind, make sure that the calculations that use ALL(\<Table>) , such as % of
grand total, are returning the intended results.

Limitations and considerations

There are a few limitations for this release of relationships with a many-many cardinality and composite models.
The following Live Connect (multi-dimensional) sources can't be used with composite models:
SAP HANA
SAP Business Warehouse
SQL Server Analysis Services
Power BI datasets
Azure Analysis Services
When you connect to these multi-dimensional sources by using DirectQuery, you can't connect to another
DirectQuery source or combine it with imported data.
The existing limitations of using DirectQuery still apply when you use relationships with a many-many
cardinality. Many of these limitations are now per table, depending upon the storage mode of the table. For
example, a calculated column on an imported table can refer to other tables, but a calculated column on a
DirectQuery table can still refer only to columns on the same table. Other limitations apply to the model as a
whole if any of the tables within the model are DirectQuery. For example, the QuickInsights and Q&A features
are unavailable on a model if any of the tables within it has a storage mode of DirectQuery.

Next steps
For more information about composite models and DirectQuery, see the following articles:
Composite models in Power BI Desktop (preview )
Storage mode in Power BI Desktop (preview )
Use DirectQuery in Power BI Desktop
Data sources supported by DirectQuery in Power BI Desktop
 Storage mode in Power BI Desktop
3/6/2019 • 8 minutes to read • Edit Online

In Microsoft Power BI Desktop, you can specify the storage mode of tables. Storage mode lets you control
whether Power BI Desktop caches table data in-memory for reports.

Setting the storage mode provides many advantages. You can set storage mode for each table individually in
your model. This action enables a single dataset, which provides the following benefits:
Query performance: As users interact with visuals in Power BI reports, Data Analysis Expressions
(DAX) queries are submitted to the dataset. Caching data into memory by properly setting the storage
mode can boost the query performance and interactivity of your reports.
Large datasets: Tables that aren't cached don't consume memory for caching purposes. You can enable
interactive analysis over large datasets that are too big or expensive to completely cache into memory.
You can choose which tables are worth caching, and which aren't.
Data refresh optimization: Tables that aren't cached don't need to be refreshed. You can reduce refresh
times by caching only the data that's necessary to meet your service level agreements and your business
requirements.
Near-real time requirements: Tables with near-real time requirements might benefit from not being
cached, to reduce data latency.
Writeback: Writeback enables business users to explore what-if scenarios by changing cell values.
Custom applications can apply changes to the data source. Tables that aren't cached can display changes
immediately, which allows instant analysis of the effects.
The storage mode setting in Power BI Desktop is one of three related features:
Composite models: Allows a report to have two or more data connections, including DirectQuery
connections or Import, in any combination. For more information, see Composite models in Power BI
Desktop.
Many-to-many relationships: With composite models, you can establish many-to -many relationships
 between tables. Many-to -many relationships removes requirements for unique values in tables. It also
removes prior workarounds, such as introducing new tables only to establish relationships. For more
information, see Many-to-many relationships in Power BI Desktop.
Storage mode: You can now specify which visuals require a query to back-end data sources. Visuals that
don't require a query are imported even if they're based on DirectQuery. This feature helps improve
performance and reduce back-end load. Previously, even simple visuals, such as slicers, initiated queries
that were sent to back-end sources. Storage mode is described further in this article.

Use the storage mode property

Storage mode is a property that you can set on each table in your model. To set the storage mode, in the Fields
pane, right-click the table whose properties you want to set, and then select Properties.

The current property is displayed in the Storage mode drop-down list in the table's Field properties pane. You
can view the current storage mode or modify it there.
There are three values for storage mode:
Import: When the value is set to Import, imported tables are cached. Queries submitted to the Power BI
dataset that return data from Import tables can be fulfilled only from cached data.
DirectQuery: With this setting, DirectQuery tables aren't cached. Queries that you submit to the Power
BI dataset - for example, Data Analysis Expressions (DAX) queries - and that return data from
DirectQuery tables can be fulfilled only by executing on-demand queries to the data source. Queries that
you submit to the data source use the query language for that data source - for example, SQL.
Dual: Dual tables can act as either cached or not cached, depending on the context of the query that's
submitted to the Power BI dataset. In some cases, you fulfill queries from cached data. In other cases, you
fulfill queries by executing an on-demand query to the data source.
Changing a table to Import is an irreversible operation. This property can't be changed back to either
DirectQuery or Dual.

Constraints on DirectQuery and Dual tables

Dual tables have the same functional constraints as DirectQuery tables. These constraints include limited M
transformations and restricted DAX functions in calculated columns. For more information, see Implications of
using DirectQuery.

Propagation of Dual
Consider the following simple model, where all the tables are from a single source that supports Import and
DirectQuery.
Let’s say all tables in this model are DirectQuery to begin with. If we then change the storage mode of the
SurveyResponse table to Import, the following warning window is displayed:

The dimension tables (Customer, Geography and Date) may be set to Dual to reduce the number of weak
relationships in the dataset, and improve performance. Weak relationships normally involve at least one
DirectQuery table where join logic cannot be pushed to the source systems. The fact that Dual tables can act as
either DirectQuery or Import helps avoid this.
The propagation logic is designed to help with models that contain many tables. Let’s say you have a model
with 50 tables and only certain fact (transactional) tables need to be cached. The logic in Power BI Desktop
calculates the minimum set of dimension tables that must be set to Dual, so you don’t have to.
The propagation logic traverses only to the one side of 1-to-many relationships.

Storage mode usage example

Let's continue with the example from the previous section, and imagine applying the following storage mode
property settings:
 TABLE STORAGE MODE

Sales DirectQuery

SurveyResponse Import

Date Dual

Customer Dual

Geography Dual

Setting these storage mode properties results in the following behaviors, assuming that the Sales table has
significant data volume.
Power BI Desktop caches dimension tables - Date, Customer, and Geography - so load times of initial
reports should be fast when they retrieve slicer values to display.
By not caching the Sales table, Power BI Desktop provides the following results:
Data-refresh times are improved, and memory consumption is reduced.
Report queries that are based on the Sales table run in DirectQuery mode. These queries might take
longer but are closer to real-time because no caching latency is introduced.
Report queries that are based on the SurveyResponse table are returned from the in-memory cache and,
therefore, should be relatively fast.

Queries that hit or miss the cache

By connecting SQL Profiler to the diagnostics port for Power BI Desktop, you can see which queries hit or miss
the in-memory cache by performing a trace that's based on the following events:
Queries Events\Query Begin
Query Processing\Vertipaq SE Query Begin
Query Processing\DirectQuery Begin
For each Query Begin event, check other events with the same ActivityID. For example, if there is no
DirectQuery Begin event, but there is a Vertipaq SE Query Begin event, the query is answered from the cache.
Queries that refer to Dual mode tables return data from the cache, if possible; otherwise, they revert to
DirectQuery.
Continuing the previous example, the following query refers only to a column from the Date table, which is in
Dual mode. Therefore, the query should hit the cache.

The following query refers only to a column from the Sales table, which is in DirectQuery mode. Therefore, it
should not hit the cache.

The following query is interesting because it combines both columns. This query doesn't hit the cache. You
might initially expect it to retrieve CalendarYear values from the cache and SalesAmount values from the source
and then combine the results, but this approach is less efficient than submitting the SUM/GROUP BY operation
to the source system. If the operation is pushed down to the source, the number of rows returned will likely be
far less.

NOTE
This behavior is different from many-to-many relationships in Power BI Desktop when cached and non-cached tables are
combined.

Caches should be kept in sync

The queries displayed in the previous section show that Dual tables sometimes hit the cache and sometimes
don't. As a result, if the cache is out of date, different values can be returned. Query execution will not attempt to
mask data issues by, for example, filtering DirectQuery results to match cached values. It is your responsibility to
know your data flows, and you should design accordingly. There are established techniques to handle such cases
at the source, if necessary.
The Dual storage mode is a performance optimization. It should be used only in ways that don't compromise
the ability to meet business requirements. For alternative behavior, consider using the techniques described in
the Many-to-many relationships in Power BI Desktop article.

Data view
If at least one table in the dataset has its storage mode set to either Import or Dual, the Data view tab is
displayed.

When they are selected in Data view, the Dual and Import tables show cached data. DirectQuery tables don't
show data, and a message is displayed that states that DirectQuery tables cannot be shown.

Limitations and considerations

There are a few limitations for this release of storage mode and its correlation with composite models.
The following Live Connect (multi-dimensional) sources cannot be used with composite models:
SAP HANA
SAP Business Warehouse
SQL Server Analysis Services
Power BI datasets
Azure Analysis Services
When you connect to those multi-dimensional sources by using DirectQuery, you can neither connect to
another DirectQuery source nor combine it with imported data.
The existing limitations of using DirectQuery still apply when you use composite models. Many of those
limitations are now per table, depending upon the storage mode of the table. For example, a calculated column
on an imported table can refer to other tables, but a calculated column on a DirectQuery table is still restricted
to refer only to columns on the same table. Other limitations apply to the model as a whole, if any of the tables
within the model are DirectQuery. For example, the QuickInsights and Q&A features are not available on a
model if any of the tables within it has a storage mode of DirectQuery.

Next steps
For more information about composite models and DirectQuery, see the following articles:
Composite models in Power BI Desktop
Many-to-many relationships in Power BI Desktop
Use DirectQuery in Power BI
Data sources supported by DirectQuery in Power BI
 Bidirectional cross-filtering using DirectQuery in
Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

When filtering tables to create the appropriate view of data, report creators (and data modelers) face challenges
when determining how filtering is applied to a report; the filter context of a table was held on one side of the
relationship, but not the other, often requiring complex DAX formulas to get the desired results.
With bidirectional cross-filtering, report creators (and data modelers) now have more control over how filters are
applied when working with related tables, enabling those filters to be applied on both sides of a table relationship.
This is accomplished by having the filter context propagated to a second related table on the other side of a table
relationship.

Detailed whitepaper for bidirectional cross-filtering

A detailed whitepaper is available that explains bidirectional cross-filtering in Power BI Desktop (the whitepaper
also covers SQL Server Analysis Services 2016, both have the same behavior).
Download the Bidirectional cross-filtering for Power BI Desktop whitepaper

Enabling bidirectional cross-filtering for DirectQuery

To enable cross-filtering, in the Edit Relationship dialog for a relationship, the following must be selected:
The Cross filter direction must be set to Both
The Apply security filter in both directions must also be selected
 NOTE
When creating cross filtering DAX formulas in Power BI Desktop, use UserPrincipalName (which is often the same as a user's
login, such as [email protected]) instead of UserName. As such, you may need to create a related table that maps
UserName (or EmployeeID, for example) to UserPrincipalName.

For more information, and for examples of how bidirectional cross-filtering works, check out the whitepaper
mentioned earlier in this article.
 Using DirectQuery in Power BI
2/13/2019 • 44 minutes to read • Edit Online

You can connect to all sorts of different data sources when using Power BI Desktop or the Power BI service,
and make those data connections in different ways. You can import data to Power BI, which is the most
common way to get data, or connect directly to data in its original source repository, which is known as
DirectQuery. This article describes DirectQuery and its capabilities:
Different connectivity options for DirectQuery
Guidance for when you should consider using DirectQuery rather than import
Drawbacks of using DirectQuery
Best practice for using DirectQuery
In short, the best practice for using import versus DirectQuery is the following:
You should import data to Power BI wherever possible. Import takes advantage of the high-performance
query engine of Power BI, and provides a highly interactive and fully featured experience over your data.
If your goals can't be met by importing data, then consider using DirectQuery. For example, if the data is
changing frequently and reports must reflect the latest data, DirectQuery may be best. However, using
DirectQuery is generally only feasible when the underlying data source can provide interactive queries (less
than 5 seconds) for the typical aggregate query, and is able to handle the query load that will be generated.
Additionally, the list of limitations that accompany use of DirectQuery should be considered carefully.
The set of capabilities offered by Power BI for both connectivity modes – import and DirectQuery - will evolve
over time. This will include providing more flexibility when using imported data, such that import can be used
in more cases, as well as eliminating some of the drawbacks of using DirectQuery. Regardless of
improvements, when using DirectQuery the performance of the underlying data source will always remain a
major consideration. If that underlying data source is slow, then using DirectQuery for that source will remain
unfeasible.
This topic covers DirectQuery with Power BI, and not SQL Server Analysis Services. DirectQuery is also a
feature of SQL Server Analysis Services, and many of the details described below apply to its use, though
there are also important differences. For information about using DirectQuery with SQL Server Analysis
Services, see the whitepaper that details DirectQuery in SQL Server Analysis Services 2016.
This article focuses on the recommended workflow for DirectQuery, where the report is created in Power BI
Desktop, but also covers connecting directly in the Power BI service.

Power BI connectivity modes

Power BI connects to a large number of varied data sources, encompassing:
Online services (Salesforce, Dynamics 365, others)
Databases (SQL Server, Access, Amazon Redshift, others)
Simple files (Excel, JSON, others)
Other data sources (Spark, Web sites, Microsoft Exchange, others)
For these sources, it's usually possible to import the data to Power BI. For some, it is also possible to connect
using DirectQuery. The exact set of sources that support DirectQuery is described in the Data Sources
supported by DirectQuery article. More sources will be DirectQuery enabled in the future, focusing primarily
on sources that can be expected to deliver good interactive query performance.
SQL Server Analysis Services is a special case. When connecting to SQL Server Analysis Services, you can
choose to import the data, or use a live connection. Using a live connection is similar to DirectQuery, in that no
data is imported, and the underlying data source is always queried to refresh a visual, but a live connection is
different in many other regards, so a different term (live versus DirectQuery) is used.
These three options for connecting to data – import, DirectQuery, and live connection – are explained in
detail in the following sections.
Import connections
When using Get Data in Power BI Desktop to connect to a data source like SQL Server, and you choose
Import, the behavior of that connection is as follows:
During the initial Get Data experience, the set of tables selected each define a query that will return a set of
data (those queries can be edited prior to loading the data, for example to apply filters, or aggregate the
data, or join different tables).
Upon load, all of the data defined by those queries will be imported into the Power BI cache.
Upon building a visual within Power BI Desktop, the imported data will be queried. The Power BI store
ensures the query will be fast, hence all changes to the visual will be reflected immediately.
Any changes to the underlying data will not be reflected in any visuals. It is necessary to Refresh, whereupon
the data will be re-imported.
Upon publishing the report (the .pbix file) to the Power BI service, a dataset is created and uploaded to the
Power BI service. The imported data is included with that dataset. It is then possible to set up scheduled
refresh of that data, for example, to re-import the data every day. Depending upon the location of the
original data source, it might be necessary to configure an On-premises data gateway.
When opening an existing report in the Power BI service, or authoring a new report, the imported data is
queried again, ensuring interactivity.
Visuals, or entire report pages, can be pinned as dashboard tiles. The tiles will be automatically refreshed
whenever the underlying dataset is refreshed.
DirectQuery connections
When using Get Data in Power BI Desktop to connect to a data source, and you choose DirectQuery, the
behavior of that connection is as follows:
During the initial Get Data experience, the source is selected. For relational sources, this means a set of
tables are selected and each still define a query that logically returns a set of data. For multidimensional
sources, like SAP BW, only the source is selected.
However, upon load, no data will actually be imported into the Power BI store. Instead, upon building a
visual within Power BI Desktop, queries will be sent to the underlying data source to retrieve the
necessary data. The time then taken to refresh the visual will depend on the performance of the underlying
data source.
Any changes to the underlying data will not be immediately reflected in any existing visuals. It is still
necessary to Refresh, whereupon the necessary queries will be resent for each visual, and the visual
updated as necessary.
Upon publishing the report to the Power BI service, it will again result in a Dataset in the Power BI service,
just as for import. However, no data is included with that dataset.
When opening an existing report in the Power BI service, or authoring a new one, the underlying data
source is again queried to retrieve the necessary data. Depending upon the location of the original data
source, it might be necessary to configure an On-premises data gateway, just as is needed for Import mode
if the data is refreshed.
Visuals, or entire report pages, can be pinned as Dashboard tiles. To ensure that opening a dashboard will
be fast, the tiles are automatically refreshed on a schedule (for example, every hour). The frequency of this
refresh can be controlled, to reflect how frequently the data is changing, and how important it is to see the
 latest data. Thus, when opening a dashboard, the tiles will reflect the data as of the time of the last refresh,
and not necessarily the very latest changes made to the underlying source. An open dashboard can always
be Refreshed to ensure it is up-to-date.
Live connections
When connecting to SQL Server Analysis Services (SSAS ), there is an option to either import data from, or
connect live to, the selected data model. If you select import, then you define a query against that external
SSAS source, and the data is imported as normal. If you select to connect live then there is no query defined,
and the entire external model is shown in the field list. If you select DirectQuery, as visuals are built, queries
are sent to the external SSAS source. However, unlike DirectQuery, there is no sense in which a new model is
being created; in other words, it's not possible to define new calculated columns, hierarchies, relationships, and
so on. Instead you are simply connecting directly to the external SSAS model.
The situation described in the previous paragraph applies to connecting to the following sources as well, except
that there is no option to import the data:
Power BI datasets (for example, when connecting to a Power BI dataset that has previously been created
and published to the service, to author a new report over it)
Common Data Services
The behavior of reports over SSAS, upon publishing to the Power BI service, is similar to DirectQuery
reports in the following ways:
When opening an existing report in the Power BI service or authoring a new report, the underlying SSAS
source is queried (possibly requiring an On-premises data gateway)
Dashboard tiles are automatically refreshed on a schedule (such as every hour, or whatever frequency is
defined)
However, there are also important differences, including that for live connections the identity of the user
opening the report will always be passed to the underlying SSAS source.
With these comparisons out of the way, let's focus solely on DirectQuery for the rest of this article.

When is DirectQuery useful?

The following table describes scenarios where connecting with DirectQuery could be especially useful,
including cases where leaving the data in the original source would be considered beneficial. The description
includes a discussion about whether the specified scenario is available in Power BI.

LIMITATION DESCRIPTION

Data is changing frequently, and near ‘real-time’ reporting is Models with Imported data can be refreshed at most once
needed per hour. Hence, if the data is continually changing, and it is
necessary for reports to show the latest data, then using
Import with scheduled refresh might simply not meet those
needs. Note also that it is also possible to stream data
directly into Power BI, though there are limits on the data
volumes supported for this case.

Using DirectQuery, by contrast, means that opening or

refreshing a report or dashboard will always show the latest
data in the source. Additionally, the dashboard tiles can be
updated more frequently (as often as every 15 mins).
LIMITATION DESCRIPTION

Data is very large If the data is very large, then it certainly would not be
feasible to import it all. DirectQuery, by contrast, requires
no large transfer of data, as it is queried in place.

However, large data might also imply that the performance

of the queries against that underlying source are too slow
(as discussed in Implications of using DirectQuery section,
later in this article). And of course it is not always necessary
to import the full detailed data. Instead the data can be pre-
aggregated during import (and Query Editor makes it easy
to do exactly this). In the extreme, it would be possible to
import exactly the aggregate data needed for each visual.
So while DirectQuery is the simplest approach to large data,
you should always keep in mind that importing aggregate
data might offer a solution if the underlying source is too
slow.

Security rules are defined in the underlying source When the data is imported, Power BI will connect to the
data source using the current user's credentials (from Power
BI Desktop), or the credentials defined as part of configuring
scheduled refresh (from the Power BI service). Thus, in
publishing and sharing such a report, care must be taken to
only share with users allowed to see the same data, or to
define Row Level Security as part of the dataset.

Ideally, because DirectQuery always queries the underlying

source, this would allow any security in that underlying
source to be applied. However, today Power BI will always
connect to the underlying source using the same credentials
as would be used for Import.

Thus, until Power BI allows for the identity of the report

consumer to pass through to the underlying source,
DirectQuery offers no advantages with regard to data
source security.

Data sovereignty restrictions apply Some organizations have policies around data sovereignty,
meaning that data cannot leave the organization premises.
A solution based on import would clearly present issues. By
contrast, with DirectQuery that data remains in the
underlying source.

However, it should be noted that even with DirectQuery,

some caches of data at the visual level are retained in the
Power BI service (due to scheduled refresh of tiles).
 LIMITATION DESCRIPTION

Underlying data source is an OLAP source, containing If the underlying data source contains measures (such as
measures SAP HANA or SAP Business Warehouse), then importing the
data brings other issues. It means that the data imported is
at a particular level of aggregation, as defined by the query.
For example, measures TotalSales by Class, Year, and City.
Then if a visual is built asking for data at a higher level
aggregate (such as TotalSales by Year), it is further
aggregating the aggregate value. This is fine for additive
measures (such as Sum, Min), but it's an issue for non-
additive measures (such as Average, DistinctCount).

To make it easy to get the correct aggregate data (as

needed for the particular visual) directly from the source, it
would be necessary to send queries per visual, as in
DirectQuery.

When connecting to SAP Business Warehouse (BW),

choosing DirectQuery allows for this treatment of measures.
Support for SAP BW is covered further in DirectQuery and
SAP BW.

However, currently DirectQuery over SAP HANA treats it the

same as a relational source, and hence provides similar
behavior to import. This is covered further in DirectQuery
and SAP HANA.

So in summary, given the current capabilities of DirectQuery in Power BI, the scenarios where it offers benefits
are the following:
Data is changing frequently, and near ‘real-time’ reporting is needed
Handling very large data, without the need to pre-aggregate
Data sovereignty restrictions apply
The source is a multidimensional source containing measures (such as SAP BW )
The details in the previous list relate to the use of Power BI alone. There is always the option of instead using
an external SQL Server Analysis Services (or Azure Analysis Services) model to import data, and then using
Power BI to connect to that model. While that approach would require additional skills, it does provide greater
flexibility. For example, much larger volumes of data can be imported, and there is no restriction on how
frequently the data can be refreshed.

Implications of using DirectQuery

Use of DirectQuery does have potentially negative implications, as detailed in this section. Some of those
limitations are slightly different depending upon the exact source that is being used. This will be called out
where applicable, and separate topics cover those sources that are substantially different.
Performance and load on the underlying source
When using DirectQuery, the overall experience depends very much on the performance of the underlying
data source. If refreshing each visual (for example, after changing a slicer value) takes a few seconds (<5 s) then
the experience would be reasonable, yet might still feel sluggish compared to the immediate response we are
used to when importing the data to Power BI. If instead the slowness of the source means that individual
visuals take longer than that (tens of seconds), then the experience becomes extremely poor, possibly even to
the point of queries timing out.
Along with the performance of the underlying source, careful consideration should be paid to the load that will
be placed upon it (that of course then often impacts the performance). As discussed further below, each user
that opens a shared report, and each dashboard tile that is periodically refreshed, will be sending at least one
query per visual to the underlying source. This fact requires that the source be able to handle such a query
load, while still maintaining reasonable performance.
Limited to a single source
When importing data, it is possible to combine data from multiple sources into a single model, for example, to
easily join some data from a corporate SQL Server database with some local data maintained in an Excel file.
This is not possible when using DirectQuery. When selecting DirectQuery for a source, it will then only be
possible to use data from that single source (such as a single SQL Server database).
Limited data transformations
Similarly, there are limitations in the data transformations that can be applied within Query Editor. With
imported data, a sophisticated set of transformations can easily be applied to clean and re-shape the data
before using it to create visuals (such as parsing JSON documents, or pivoting data from a column to a row
orientated form). Those transformations are more limited in DirectQuery. First, when connecting to an OLAP
source like SAP Business Warehouse, no transformations can be defined at all, and the entire external ‘model’
is taken from the source. For relational sources, like SQL Server, it is still possible to define a set of
transformations per query, but those transformations are limited for performance reasons. Any such
transformation will need to be applied on every query to the underlying source, rather than once on data
refresh, so they are limited to those transformations that can reasonably be translated into a single native
query. If you use a transformation that is too complex, then you will receive an error that either it must be
deleted, or the model switched to Import mode.
Additionally, the query that results from the Get Data dialog or Query Editor will be used in a subselect
within the queries generated and sent to retrieve the necessary data for a visual. Thus the query defined in
Query Editor must be valid within this context. In particular, this means it is not possible to use a query using
Common Table Expressions, nor one that invokes Stored Procedures.
Modeling limitations
The term modeling in this context means the act of refining and enriching the raw data, as part of authoring a
report using it. Examples include:
Defining relationships between tables
Adding new calculations (calculated columns and measures)
Renaming and hiding columns and measures
Defining hierarchies
Defining the formatting, default summarization and sort order for a column
Grouping or clustering values
When using DirectQuery, many of these model enrichments can still be made, and certainly there is still the
principle that the raw data is being enriched, so as to improve later consumption. However, there are some
modeling capabilities that are not available, or are limited, when using DirectQuery. The limitations are
generally applied to avoid performance issues. The set of limitations that are common to all DirectQuery
sources are listed in the following bulleted list. Additional limitations might apply to individual sources, as
described in Data source specific details found near the end of this article.
No built-in date hierarchy: When importing data, then by default every date/datetime column will
also have a built-in date hierarchy available by default. For example, if importing a table of sales orders
including a column OrderDate, then upon using OrderDate in a visual, it will be possible to choose the
appropriate level (Year, Month, Day) to use. This built-in date hierarchy is not available when using
DirectQuery mode. Note however that if there is a Date table available in the underlying source (as is
common in many data warehouses) then the DAX Time Intelligence functions can be used as normal.
Limitations in calculated columns: Calculated columns are limited to being intra-row, as in, they can
only refer to values of other columns of the same table, without the use of any aggregate functions.
Additionally, the DAX scalar functions (such as LEFT()) that are allowed, will be limited to those which
can simply be pushed to the underlying source, hence will vary depending upon the exact capabilities of
the source. Functions that are not supported will not be listed in autocomplete when authoring the DAX
for a calculated column, and would result in an error if used.
No support for parent-child DAX functions: When in DirectQuery model, it is not possible to use the
family of DAX PATH() functions, that generally handle Parent-Child structures (such as chart of accounts,
or employee hierarchies).
Limitations (by default) for measures: By default, the DAX functions and expressions that can be
used in measures are restricted. Again, autocomplete will restrict the functions listed, and an error will
occur if an invalid function or expression is used. The reason is simply to ensure that, by default,
measures are restricted to simple measures that are unlikely by themselves to cause any performance
issues. Advanced users can choose to bypass this limitation by selecting File > Options and settings >
Options and then DirectQuery, then selecting the option Allow unrestricted measures in DirectQuery
mode. When that option is selected, any DAX expression that is valid for a measure can be used. Users
must be aware, however, that some expressions that perform well when the data is imported may result
in slow queries to the backend source when in DirectQuery mode.
For example, by default:
It would be possible to author a measure that simply summed the sales amount:

SalesAmount = SUMX(Web_Sales, [ws_sales_price]* [ws_quantity])

It would not be possible to author a measure that then averaged that SalesAmount over all
of the Items:

AverageItemSalesAmount = AVERAGEX('Item', [SalesAmount])

The reason is that such a measure could result in poor performance if there were a large number
of items.
Calculated tables are not supported: The ability to define a calculated table using a DAX expression
is not supported in DirectQuery mode.
Relationship filtering is limited to a single direction: When using DirectQuery, it is not possible to
set the Cross Filter direction on a relationship to “Both”. For example, with the three tables below, it
would not be possible to build a visual showing each Customer[Gender], and the number of
Product[Category] bought by each. Use of such bi-directional filtering is described in this detailed
whitepaper (the paper presents examples in the context of SQL Server Analysis Services, but the
fundamental points apply equally to Power BI).

Again, the limitation is imposed due to the performance implications. One particularly important
 application of this is when defining Row Level Security as part of the report, as a common pattern is to
have a many-many relationship between the users and the entities they are allowed access to, and use of
bi-directional filtering is necessary to enforce this. However, use of bi-directional filtering for
DirectQuery models should be used judiciously, with careful attention paid to any detrimental impact on
performance.
No Clustering: When using DirectQuery, it is not possible to use the Clustering capability, to
automatically find groups
Reporting limitations
Almost all reporting capabilities are supported for DirectQuery models. As such, so long as the underlying
source offers a suitable level of performance, the same set of visualizations can be used. However, there are
some important limitations in some of the other capabilities offered in the Power BI service after a report is
published, as described in the following bullets:
Quick Insights is not supported: Power BI Quick Insights searches different subsets of your dataset while
applying a set of sophisticated algorithms to discover potentially interesting insights. Given the need for
very high-performance queries, this capability is not available on datasets using DirectQuery.
Q&A is not supported: Power BI Q&A enables you to explore your data using intuitive, natural language
capabilities and receive answers in the form of charts and graphs. However, it is currently not supported on
datasets using DirectQuery.
Using Explore in Excel will likely result in poorer performance: It is possible to explore your data by
using the “Explore in Excel” capability on a dataset. This will allow Pivot Tables and Pivot Charts to be
created in Excel. While this capability is supported on datasets using DirectQuery, the performance is
generally slower than creating visuals in Power BI, and therefore if the use of Excel is important for your
scenarios, this should be accounted for in your decision to use DirectQuery.
Security
As discussed earlier in this article, a report using DirectQuery will always use the same fixed credentials to
connect to the underlying data source, after publish to the Power BI service. Again, note this refers specifically
to DirectQuery, not to live connections to SQL Server Analysis Services, which is different in this respect.
Hence immediately after publish of a DirectQuery report, it is necessary to configure the credentials of the user
that will be used. Until this is done, opening the report on the Power BI service would result in an error.
Once the user credentials are provided, then those credentials will be used, irrespective of the user who opens
the report. In this regard, it is exactly like imported data, in that every user will see the same data, unless Row
Level Security has been defined as part of the report. Hence the same attention must be paid to sharing the
report, if there are any security rules defined in the underlying source.
Behavior in the Power BI service
This section describes the behavior of a DirectQuery report in the Power BI service, primarily so as to be
able to understand the degree of load that will be placed on the back-end data source, given the number of
users that the report and dashboard will be shared with, the complexity of the report, and whether Row Level
Security has been defined in the report.
Reports – opening, interacting with, editing
When a report is opened, then all the visuals on the currently visible page will refresh. Each visual will generally
require at least one query to the underlying data source. Some visuals might require more than one query (for
example, if it showed aggregate values from two different fact tables, or contained a more complex measure, or
contained totals of a non-additive measure like Count Distinct). Moving to a new page will result in those
visuals being refreshed, resulting in a new set of queries to the underlying source.
Every user interaction on the report might result in visuals being refreshed. For example, selecting a different
value on a slicer will require sending a new set of queries to refresh all of the affected visuals. The same is true
for clicking on a visual to cross-highlight other visuals, or changing a filter.
Similarly of course, editing a new report will require queries to be sent for each step on the path to produce the
final desired visual.
There is some caching of results, so that the refresh of a visual will be instantaneous if the exact same results
have recently been obtained. Such caches are not shared across users, if there is any Row Level Security
defined as part of the report.
Dashboard Refresh
Individual visuals, or entire pages, can be pinned to dashboard as tiles. Tiles based on DirectQuery datasets
are then refreshed automatically according to a schedule, resulting in queries being sent to the backend data
source. By default, this occurs every hour, but can be configured as part of Dataset settings to be between
weekly, and every 15 minutes.
If no Row Level Security is defined in the model, this means that each tile would be refreshed once, and the
results shared across all users. If Row Level Security is defined, then there can be a large multiplier effect –
each tile requires separate queries per user to be sent to the underlying source.
Hence a dashboard with ten tiles, shared with 100 users, created on a dataset using DirectQuery with Row
Level Security, and configured to refresh every 15 minutes, would result in at least 1000 queries being sent
every 15 minutes to the back-end source.
Hence careful consideration must be paid to the use of Row Level Security, and the configuring of the refresh
schedule.
Timeouts
A timeout of four minutes is applied to individual queries in the Power BI service, and queries taking longer
than that will simply fail. As stressed earlier, it is recommended that DirectQuery be used for sources that
provide near interactive query performance, so this limit is intended to prevent issues from overly long
execution times.
Other implications
Some other general implications of using DirectQuery are the following:
If data is changing, it is necessary to Refresh to ensure the latest data is shown: Given the use of
caches, there is no guarantee that the visual is always showing the latest data. For example, a visual
might show the transactions in the last day. Then due to a slicer being changed, it might refresh to show
the transactions for the last two days, including some very recent, newly arrived transactions. Returning
the slicer to its original value would result in it again showing the cached value previously obtained, that
would not include the newly arrived transaction seen before.
Selecting Refresh will clear any caches, and refresh all the visuals on the page to show the latest data.
If data is changing, there is no guarantee of consistency between visuals: Different visuals,
whether on the same page or on different pages, might be refreshed at different times. Thus if the data
in the underlying source is changing, there is no guarantee that each visual will be showing the data at
the exact same point of time. Indeed, given that sometimes more than one query is required for a single
visual (for example, to obtain the details and the totals) then consistency even within a single visual is
not guaranteed. To guarantee this would require the overhead of refreshing all visuals whenever any
visual refreshed, in tandem with the use of costly features like Snapshot Isolation in the underlying data
source.
This issue can be mitigated to a large extent by again selecting Refresh, to refresh all of the visuals on
the page. And it should be noted that even if using Import mode, there is a similar problem of
guaranteeing consistency if importing data from more than one table.
Refresh in Power BI Desktop is needed to reflect any metadata changes: After a report is
published, Refresh will simply refresh the visuals in the report. If the schema of the underlying source
 has changed, then those changes are not automatically applied to change the available fields in the field
list. Thus if tables or columns have been removed from the underlying source, it might result in query
failure upon refresh. Opening the report in Power BI Desktop, and choosing Refresh, will update the
fields in the model to reflect the changes.
Limit of one million rows returned on any query: There is a fixed limit of one million rows placed
on the number of rows that can be returned in any single query to the underlying source. This generally
has no practical implications, and visuals themselves aren’t going to display that many points. However,
the limit can occur in cases where Power BI is not fully optimizing the queries sent, and there is some
intermediate result being requested that exceeds the limit. It can also occur whilst building a visual, on
the path to a more reasonable final state. For example, including Customer and TotalSalesQuantity
would hit this limit if there were more than 1m customers, until some filter were applied.
The error that would be returned would be “The resultset of a query to external data source has
exceeded the maximum allowed size of '1000000' rows.”
Cannot change from import to DirectQuery mode: While it's possible to switch a model from
DirectQuery mode to use import mode, this means all the necessary data must be imported. It is also
not possible to switch back (primarily due to the set of features not supported in DirectQuery mode).
DirectQuery models over multidimensional sources like SAP BW, also cannot be switched from
DirectQuery to import, due to the completely different treatment of external measures.

DirectQuery in the Power BI service

All sources are supported from Power BI Desktop. Some sources are also available directly from within the
Power BI service. For example, it is possible for a business user to use Power BI to connect to their data in
Salesforce, and immediately get a dashboard, without use of Power BI Desktop.
Only two of the DirectQuery enabled-sources are available directly in the service:
Spark
Azure SQL Data Warehouse
However, it is recommended that any use of DirectQuery over those two sources start within Power BI
Desktop. The reason is that when the connection is initially made in the Power BI service, many key
limitations will apply, meaning that while the start point was easy (starting in the Power BI service), there are
limitations on enhancing the resulting report any further (for example, it's not possible then to create any
calculations, or use many analytical features, or even refresh the metadata to reflect any changes to the
underlying schema).

Guidance for using DirectQuery successfully

If you're going to use DirectQuery, then this section provides you with some high-level guidance on how to
ensure success. The guidance in this section is derived from the implications of using DirectQuery that have
been described in this article.
Backend data source performance
You should validate that simple visuals will be able to refresh in a reasonable time, which should be within 5
seconds to have a reasonable interactive experience. Certainly if visuals are taking longer than 30 seconds, then
it's highly likely that further issues will occur following publication of the report, which will make the solution
unworkable.
If queries are slow, then the first point of investigation is to examine the queries being sent to the underlying
source, and the reason for the query performance being observed. This article doesn't cover the wide range of
database optimization best practices across the full set of potential underlying sources, but it does apply to the
standard database practices that apply to most situations:
 Relationships based on integer columns generally perform better than joins on columns of other data types
The appropriate indexes should be created, which generally means the use of column store indexes in those
sources that support them (for example, SQL Server).
Any necessary statistics in the source should be updated
Model Design Guidance
When defining the model, consider doing the following:
Avoid complex queries in Query Editor. The query that's defined in the Query Editor will be
translated into a single SQL query, which will then be included in the subselect of every query sent to
that table. If that query is complex, it might result in performance issues on every query sent. The actual
SQL query for a set of steps can be obtained by selecting the last step in Query Editor, and choosing
View Native Query from the context menu.
Keep measures simple. At least initially, it is recommended to limit measures to simple aggregates.
Then if the measures perform in a satisfactory manner, more complex measures can be defined, but
paying attention to the performance for each.
Avoid relationships on calculated columns. This is relevant to databases where it is necessary to
perform multi-column joins. Power BI today does not allow a relationship to be based on multiple
columns as the FK/PK. The common workaround is to concatenate the columns together using a
calculated column, and base the join on that. While this workaround is reasonable for imported data, in
the case of DirectQuery it results in a join on an expression, that commonly prevents use of any
indexes, and leads to poor performance. The only workaround is to actually materialize the multiple
columns into a single column in the underlying database.
Avoid relationships on uniqueidentifier columns. Power BI does not natively support a datatype of
uniqueidentifier. Hence defining a relationship between columns of type uniqueidentifier column will
result in a query with a join involving a Cast. Again, this commonly leads to poor performance. Until this
case is specifically optimized, the only workaround is to materialize columns of an alternative type in the
underlying database.
Hide the to column on relationships. The to column on relationships (commonly the primary key on
the to table) should be hidden, so that it does not appear in the field list, and therefore cannot be used in
visuals. Often the columns on which relationships are based are in fact system columns (for example,
surrogate keys in a data warehouse) and hiding such columns is good practice anyway. If the column
does have meaning, then introduce a calculated column that is visible, and that has a simple expression
of being equal to the primary key. For example:

ProductKey_PK (Destination of a relationship, hidden)

ProductKey (= [ProductKey_PK], visible)
ProductName
...

The reason for doing this is simply to avoid a performance issue that can occur otherwise if a visual
includes the primary key column.
Examine all uses of calculated columns and data type changes. Use of these capabilities are not
necessarily harmful, they result in the queries sent to the underlying source containing expressions
rather than simple references to columns, that again might result in indexes not being used.
Avoid use of the (preview) bi-directional cross filtering on relationships.
Experiment with setting Assume referential integrity. The Assume Referential Integrity setting on
relationships enables queries to use INNER JOIN statements rather than OUTER JOIN. This generally
 improves query performance, though it does depend on the specifics of the data source.
Do not use the relative data filtering in Query Editor. It's possible to define relative date filtering in
Query Editor. For example, to filter to the rows where the date is in the last 14 days.

However, this will be translated into a filter based on the fixed date, as at the time the query was
authored. This can be seen from viewing the native query.

This is almost certainly not what was wanted. To ensure the filter is applied based upon the date as at
the time the report is executed then instead apply the filter in the report as a Report Filter. Currently this
would be done by creating a calculated column calculating the number of days ago (using the DAX
DATE () function), and then using that calculated column in a filter.
Report Design Guidance
When creating a report using a DirectQuery connection, adhere to the following guidance:
Consider use of Query Reduction options: Power BI provides options in the report to send fewer
queries, and to disable certain interactions that would result in a poor experience if the resulting queries
take a long time to execute. To access these options in Power BI Desktop, go to File > Options and
settings > Options and select Query reduction.
Checking box selections on the Query reduction let you disable cross-highlighting throughout your
entire report. You can also show an Apply button to slicers and/or filter selections, which lets you then
make many slicer and filter selections before applying them, which results in no queries being sent until
you select the Apply button on the slicer. Your selections can then be used to filter the data.
These options will apply to your report while you interact with it in Power BI Desktop, as well as when
your users consume the report in the Power BI service.
Apply filters first: Always apply any applicable filters at the start of building a visual. For example,
rather than drag in the TotalSalesAmount, and ProductName, then filter to a particular year, apply the
filter on Year at the very start. This is because each step of building a visual will send a query, and whilst
it is possible to then make another change before the first query has completed, this still leaves
unnecessary load on the underlying source. By applying filters early, it generally makes those
intermediate queries less costly. Also, failing to apply filters early can result in hitting the 1m row limit
above.
Limit the number of visuals on a page: When a page is opened (or some page level slicer or filter
changed) then all of the visuals on a page are refreshed. There is also a limit on the number of queries
that are sent in parallel, hence as the number of visuals increases, some of the visuals will be refreshed
in a serial manner, increasing the time taken to refresh the entire page. For this reason it's recommended
to limit the number of visuals on a single page, and instead have more, simpler pages.
Consider switching off interaction between visuals: By default, visualizations on a report page can
be used to cross-filter and cross-highlight the other visualizations on the page. For example, having
selected “1999” on the pie chart, the column chart is cross highlighted to show the sales by category for
“1999”.
 In DirectQuery such cross-filtering and cross-highlighting require queries to be submitted to the
underlying source, so the interaction should be switched off if the time taken to respond to users'
selections would be unreasonably long. However, this interaction can be switched off, either for the
entire report (as described above for Query reduction options), or on a case-by-case basis as described
in this article.
In addition to the above list of suggestions, note that each of the following reporting capabilities can cause
performance issues:
Measure filters: Visuals containing measures (or aggregates of columns) can contain filters in those
measures. For example, the visual below shows SalesAmount by Category, but only including those
Categories with more than 20M of sales.

This will result in two queries being sent to the underlying source:
The first query will retrieve the Categories meeting the condition (Sales > 20M )
The second query will then retrieve the necessary data for the visual, including the Categories that
met the condition in the WHERE clause.
This generally performs just fine if there are hundreds or thousands of categories, as in this example.
Performance can degrade if the number of categories is much larger (and indeed, the query will fail if
there were more than a million categories meeting the condition, due to the one million row limit
discussed earlier).
 TopN filters: Advanced filters can be defined to filter on only the Top (or Bottom) N values ranked by
some measure, for example, to only include the Top 10 Categories in the visual above. This will again
result in two queries being sent to the underlying source. However, the first query will return all
categories from the underlying source, and then the TopN are determined based on the returned results.
Depending on the cardinality of the column involved, this can lead to performance issues (or query
failures due to the 1m row limit).
Median: Generally, any aggregation (Sum, Count Distinct, so on) is pushed to the underlying source.
However, this is not true for Median, as this aggregate is generally not supported by the underlying
source. In such cases, the detail data is retrieved from the underlying source, and the Median calculated
from the returned results. This is reasonable when the median is to be calculated over a relatively small
number of results, but performance issues (or query failures due to the 1m row limit) will occur if the
cardinality is large. For example, Median Country Population might be reasonable, but Median Sales
Price might not be.
Advanced text filters (‘contains’ and similar): When filtering on a text column, the advanced filtering
allows filters like ‘contains’ and ‘begins with’ and so on. These filters can certainly result in degraded
performance for some data sources. In particular, the default ‘contains’ filter should not be used if what
is really required is an exact match (‘is’ or ‘is not’). Although the results might be the same, depending
on the actual data, the performance might be drastically different due to the use of indexes.
Multi select slicers: By default, slicers only allow a single selection to be made. Allowing multi selection
in filters can cause some performance issues, because as the user selects a set of items in the slicer (for
example, the ten products they are interested in), then each new selection will result in queries being
sent to the backend source. Whilst the user can select the next item prior to the query completing, this
does result in extra load on the underlying source.
Consider switching off totals on visuals: By default, tables and matrices display totals and subtotals.
In many cases, separate queries must be sent to the underlying source to obtain the values for such
totals. This applies whenever using DistinctCount aggregation, or in all cases when using DirectQuery
over SAP BW or SAP HANA. Such totals should be switched off (by using the Format pane) if not
required.
Maximum number of connections option for DirectQuery
You can set the maximum number of connections DirectQuery opens for each underlying data source, and
thereby control the number of queries concurrently sent to each data source.
The default maximum number of concurrent connections DirectQuery opens is then. You can change this for
the current file in Power BI Desktop by going to File > Options and Settings > Options, then in the
Current File section in the left pane, select DirectQuery.
The setting is only enabled when there's at least one DirectQuery source in the current report. The value
applies to all DirectQuery sources, and to any new DirectQuery sources added to the same report.
Increasing the maximum connections value ensures more queries (up to the maximum number specified)
can be sent to the underlying data source, which is useful when numerous visuals are on a single page, or
many users access a report at the same time. Once the maximum number of connections is reached, further
queries are queued until a connection becomes available. Increasing this limit does result in more load on the
underlying source, so the setting isn't guaranteed to improve overall performance.
Once a report is published, the maximum number of concurrent queries sent to the underlying data source
also depend upon fixed limits, which depend on the target environment to which the report is published.
Different environments (such as Power BI, Power BI Premium, or Power BI Report Server) each can impose
different limits.
Diagnosing performance issues
This section describes how to diagnose performance issues, or how to get more detailed information to allow
the reports to be optimized.
It's strongly recommended that any diagnosis of performance issues starts in Power BI Desktop, rather than
in the Power BI service. It's commonly the case that performance issues are simply based on the level of
performance of the underlying source, and these are more easily identified and diagnosed in the much more
isolated environment of Power BI Desktop, and initially eliminates certain components (such as the Power BI
gateway). Only if the performance issues are found to not be present with Power BI Desktop should
investigation focus on the specifics of the report in the Power BI service.
Similarly, it is recommended to first try to isolate any issues to an individual visual, rather than many visuals on
a page.
So, let's say those steps (in the previous paragraphs in this section) have been taken - we now have a single
visual on a page in Power BI Desktop that is still sluggish. To determine the queries that are sent to the
underlying source by Power BI Desktop, it's possible to view traces/diagnostic information that might be
emitted by that source. Such traces might also contain useful information about the details of how the query
was executed, and how it can be improved.
Further, even in the absence of such traces from the source, it's possible to view the queries sent by Power BI,
along with their execution times, as described next.
Determining the queries sent by Power BI Desktop
By default, Power BI Desktop logs events during a given session to a trace file called
FlightRecorderCurrent.trc.
For some DirectQuery sources, this log includes all queries sent to the underlying data source (the remaining
DirectQuery sources will be included in the future). The sources that send queries to the log are the following:
SQL Server
Azure SQL Database
Azure SQL Data warehouse
Oracle
Teradata
SAP HANA
The trace file can be found in the AppData folder for the current user:

\<User>\AppData\Local\Microsoft\Power BI Desktop\AnalysisServicesWorkspaces

Here's an easy way to get to this folder: In Power BI Desktop select File > Options and settings > Options,
and then select Diagnostics. The following dialog window appears:
When you select the Open traces folder link, under Diagnostic Options, the following folder opens:

\<User>\AppData\Local\Microsoft\Power BI Desktop\Traces

Navigating to that folder's parent folder displays the folder containing AnalysisServicesWorkspaces, which will
contain one workspace subfolder for every open instance of Power BI Desktop. These subfolders are named
with an integer suffix, such as AnalysisServicesWorkspace2058279583.
Inside that folder is a \Data subfolder that contains the trace file FlightRecorderCurrent.trc for the current
Power BI session. The corresponding workspace folder is deleted when the associated Power BI Desktop
session ends.
The trace files can be read using the SQL Server Profiler tool, which is available as a free download as part of
SQL Server Management Studio. You can get that from this location.
Once you download and install SQL Server Management Studio, run SQL Server Profiler.
To open the trace file, take the following steps:
1. In SQL Server Profiler, select File > Open > Trace file
2. Enter the path to the trace file for the currently open Power BI session, such as:

C:\Users\<user>\AppData\Local\Microsoft\Power BI
Desktop\AnalysisServicesWorkspaces\AnalysisServicesWorkspace2058279583\Data

3. Open FlightRecorderCurrent.trc
All events from the current session are displayed. An annotated example is shown below, which highlights
groups of events. Each group has the following:
A Query Begin and Query End event, which represent the start and end of a DAX query generated by the UI
(for example, from a visual, or from populating a list of values in the filter UI)
One or more pairs of DirectQuery Begin and DirectQuery End events, which represent a query sent to the
underlying data source, as part of evaluating the DAX query.
Note that multiple DAX queries can be executed in parallel, so events from different groups can be interleaved.
The value of the ActivityID can be used to determine which events belong to the same group.
Other columns of interest are the following:
TextData: The textual detail of the event. For “Query Begin/End” events this will be the DAX query. For
“DirectQuery Begin/End” events this will be the SQL query sent to the underlying source. The TextData for
the currently selected event is also displayed in the region at the bottom.
EndTime: When the event completed.
Duration: The duration, in milliseconds, taken to execute the DAX or SQL query.
Error: Indicates if an error occurred (in which case the event is also displayed in red).
In the image above, some of the less interesting columns have been narrowed, to allow the interesting columns
to be seen more easily.
The recommended approach to capturing a trace to help diagnose a potential performance issue is the
following:
Open a single Power BI Desktop session (to avoid the confusion of multiple workspace folders)
Perform the set of actions of interest in Power BI Desktop. Include a few additional actions beyond that, to
ensure that the events of interest are flushed into the trace file.
Open SQL Server Profiler and examine the trace, as described earlier. Remember that the trace file will be
deleted upon closing Power BI Desktop. Also, further actions in Power BI Desktop will not immediately
appear – the trace file should be closed and re-opened to see the new events.
Keep individual sessions reasonably small (10 seconds of actions, not hundreds) to make it easier to
interpret the trace file (and because there is a limit on the size of the trace file, thus for long sessions there is
a chance of early events being dropped).
Understanding the form of query sent by Power BI Desktop
The general format of queries created and sent by Power BI Desktop use subselects for each of the tables
referenced, where the subselect is as defined by the query defined in Query Editor. For example, assume the
following TPC -DS tables in SQL Server:
Consider the following query:

That query results in the following visual:

Refreshing that visual will result in the SQL query shown below the next paragraph. As you can tell, there are
three subselects for Web Sales, Item, and Date_dim, that each return all the columns on the respective table,
even though only four columns are actually referenced by the visual. These queries in the subselects (they're
shaded) are exactly the result of the queries defined in Query editor. Use of subselects in this manner has not
been found to impact performance, for the data sources so far supported for DirectQuery. Data sources like
SQL Server simply optimize away the references to the other columns.
One reason Power BI employs this pattern is because the SQL query used can be provided directly by the
analyst, so it's used "as provided", without an attempt to rewrite it.
Next steps
This article describes aspects of DirectQuery that are common across all data sources. There are certain
details that are specific to individual sources. See the following articles covering specific sources:
DirectQuery and SAP HANA
DirectQuery and SAP BW
For more information about DirectQuery, check out the following resources:
Data Sources supported by DirectQuery
 Data sources supported by DirectQuery in Power BI
2/25/2019 • 2 minutes to read • Edit Online

Power BI Desktop and the Power BI service have many data sources to which you can connect and get
access to data. This article describes which data sources for Power BI support the connection method known as
DirectQuery. For more information about DirectQuery, see DirectQuery in Power BI.
The following data sources support DirectQuery in Power BI:
Amazon Redshift
Azure HDInsight Spark (Beta)
Azure SQL Database
Azure SQL Data Warehouse
Google BigQuery (Beta)
IBM DB2 database
IBM Netezza (Beta)
Impala (version 2.x)
Oracle Database (version 12 and above)
SAP Business Warehouse Application Server
SAP Business Warehouse Message Server (Beta)
SAP HANA
Snowflake
Spark (Beta) (version 0.9 and above)
SQL Server
Teradata Database
Vertica (Beta)
Data sources that have (Beta) or (Preview) after their name are subject to change, and are not supported for
production use. They might also not be supported after publishing a report to the Power BI service, which
means that opening a published report or exploring the dataset can result in an error.
The only difference between (Beta) and (Preview) data sources is that (Preview) sources must be enabled as
a Preview feature before they become available for use. To enable a (Preview) data connector, in Power BI
Desktop go to File > Options and Settings > Options, and then select Preview features.

NOTE
DirectQuery queries to SQL Server require authentication using current Windows authentication credentials or database
credentials to establish access. Alternate credentials are not supported.

On-premises gateway requirements

The following table specifies whether an On-premises data gateway is required to connect to the specified
data source, after publishing a report to the Power BI service.

SOURCE GATEWAY REQUIRED?

SQL Server Yes

 SOURCE GATEWAY REQUIRED?

Azure SQL Database No

Azure SQL Data Warehouse No

SAP HANA Yes

Oracle Database Yes

Teradata Database Yes

Amazon Redshift No

Impala (version 2.x) Yes

Snowflake Yes

Spark (beta), version 0.9 and later Yes

Azure HDInsight Spark (Beta) No

IBM Netezza Yes

SAP Business Warehouse Application Server Yes

SAP Business Warehouse Message Server Not yet supported in the Power BI service

Google BigQuery No

Next steps
For more information about DirectQuery, check out the following resources:
DirectQuery in Power BI
DirectQuery and SAP HANA
DirectQuery and SAP BW
On-premises data gateway
 Power BI Data Source Prerequisites
1/14/2019 • 2 minutes to read • Edit Online

For each data provider, Power BI supports a specific provider version on objects. For more information about data
sources available to Power BI, see Data Sources. The following table describes these requirements.

MINIMUM
PROVIDER MINIMUM DATA SUPPORTED DATA
DATA SOURCE PROVIDER VERSION SOURCE VERSION SOURCE OBJECTS DOWNLOAD LINK

SQL Server ADO.net (built .NET Framework SQL Server Tables/Views, Included in .NET
into .Net 3.5 (only) 2005+ Scalar functions, Framework 3.5 or
Framework) Table functions above

Access Microsoft Access ACE 2010 SP1 No restriction Tables/Views Download link
Database Engine
(ACE)

Excel (.xls files Microsoft Access ACE 2010 SP1 No restriction Tables, Sheets Download link
only) (see note 1) Database Engine
(ACE)

Oracle (see note ODP.NET ODAC 11.2 9.x+ Tables/Views Download link
2) Release 5
(11.2.0.3.20)

System.Data.Orac .NET Framework 9.x+ Tables/Views Included in .NET

leClient (Built in 3.5 Framework 3.5 or
.NET Framework) above

IBM DB2 ADO.Net client 10.1 9.1+ Tables/Views Download link

from IBM (part of
the IBM data
server driver
package)

MySQL Connector/Net 6.6.5 5.1 Tables/Views, Download link

Scalar functions

PostgreSQL NPGSQL 2.0.12 7.4 Tables/Views Download link

ADO.NET
provider

Teradata .NET Data 14+ 12+ Tables/Views Download link

Provider for
Teradata

SAP Sybase SQL iAnywhere.Data.S 16+ 16+ Tables/Views Download link

Anywhere QLAnywhere for
.NET 3.5
NOTE
Excel files that have an .xlsx extension do not require a separate provider installation.

NOTE
The Oracle providers also require Oracle client software (version 8.1.7+).
 Default member in multidimensional models in Power
BI
1/14/2019 • 4 minutes to read • Edit Online

You can connect to multidimensional models in Power BI, and create reports that visualize all sorts of data within
the model. When working with multidimensional models, Power BI applies rules to how it processes data, based on
which column is defined as the default member.
When working with multidimensional models, Power BI handles data from the model based on where the column
that contains the DefaultMember is used. The DefaultMember attribute is set in CSDL (Conceptual Schema
Definition Language) for a particular column in a multidimensional model. You can learn more about the default
member in its attribute properties article. When a DAX query is executed, the default member specified in the
model is applied automatically.
This article described how Power BI behaves under various circumstances when working with multidimensional
models, based on where the default member is found.

Working with filter cards

When creating a filter card on a field with a default member, the default member field value is selected
automatically in the filter card. The result is that all visuals that are affected by the filter card retain their default
models in the database. The values in such filter cards reflect that default member.
If the default member is removed, de-selecting the value clears it for all visuals to which the filter card applies, and
the values displayed do not reflect the default member.
For example, imagine we have a Currency column that has a default member set to USD:
In this example case, if we have a card that shows Total Sales, the value will have the default member applied
and we see sales that correspond to "USD".
If we drag Currency to the filter card pane, we see USD as the default value selected. The value of Total Sales
remains the same, since the default member is applied.
However, if we deselect the USD value from the filter card, the default member for Currency is cleared, and now
Total Sales reflects all currencies.
Consequently, when we select another value in the filter card (let's say we select EURO ), along the default
member, the Total Sales reflects the filter Currency IN {USD, EURO }.

Grouping behavior
In Power BI, whenever you group a visual on a column that has a default member, Power BI clears the default
member for that column and its attribute relationship path. This ensures the visual displays all values, rather than
just the default values.

Attribute relationship paths (ARPs)

Attribute relationship paths (ARPs) provide default members with powerful capabilities, but also introduce a
certain amount of complexity. When ARPs are encounter, Power BI follows the path of ARPs to clear additional
default members for other columns, to provide consistent, and precise handling of data for visuals.
Let's look at an example to clarify the behavior. Consider the following configuration of ARPs:
Now let's imagine the following default members are set for these columns:
City > Seattle
State > WA
Country > US
Population > Large
Now let's examine what happens when each of the columns is used in Power BI. When visuals group on the
following columns, here are the results:
City - Power BI displays all the cities by clearing all the default members for City, State, Country but
preserves the default member for Population; Power BI cleared the entire ARP for City.

NOTE
Population is not in the ARP path of City, it is solely related to State and thus Power BI doesn't clear it.

State - Power BI displays all the States by clearing all default members for City, State, Country and
Population.
Country - Power BI displays all the countries by clearing all default members for City, State and Country, but
preserves the default member for Population.
City and State - Power BI clears all default members for all columns.
Groups displayed in the visual have their entire ARP path cleared.
If a group is not displayed in the visual, but is part of the ARP path of another grouped-on column, the following
applies:
Not all branches of the ARP path are cleared automatically.
That group is still filtered by that uncleared default member.
Slicers and filter cards
When working with slicers or filter cards, the following behavior occurs:
When a slicer or filter card is loaded with data, Power BI groups on the column in the visual, so the display
behavior is the same as described in the previous section.
Since slicers and filter cards are often used to interact with other visuals, the logic of clearing default members for
the affected visuals occurs as explained in the following table.
For this table, we use the same example data used earlier in this article:
The following rules apply for how Power BI behaves in these circumstances.
Power BI clears a default member for a given column if:
Power BI groups on that column
Power BI groups on a column related to that column (anywhere in the ARP, up or down)
Power BI filters on a column that is in the ARP (up or down)
The column has a filter card with ALL state
The column has a filter card with any value selected (Power BI receives a filter for the column)
Power BI does not clear a default member for a given column if:
The column has a filter card with default state, and Power BI is groupings on a column in its ARP.
The column is above another column in the ARP, and Power BI has a filter card for that other column in default
state.

Next steps
This article described the behavior of Power BI when working with default members in multidimensional models.
You might also be interested in the following articles:
Show items with no data in Power BI
Data sources in Power BI Desktop
 Frequently asked questions about Power BI custom
visuals
3/14/2019 • 7 minutes to read • Edit Online

Organizational custom visuals

How can the admin manage the organizational custom visuals?
In the Admin portal, under the "Organizational custom visuals" tab, the admin can see and manage all the
organizational custom visuals in the enterprise: add, disable, enable, and delete. There's no need to share those
visuals by emails or shared folder anymore! Once deployed into the organizational repository, users in the
organization can easily find them, and import the organizational custom visuals into their reports directly from
Power BI Desktop or Service. The organizational custom visuals can be found from the built-in store (in desktop
and service) under the MY ORGANIZATION tab. Once the admin uploads a new organizational custom visual’s
version, everyone in the organization gets the same updated version. Report authors don't need to delete the visual
in their reports to get the new version of these visuals as all reports using these visuals are automatically updated!
The update mechanism is similar to the marketplace visuals.
If an admin uploads a custom visual from the public marketplace to the organization store, is it automatically
updated once a vendor updates the visual in the public marketplace?
No, there's no automatic update from the public marketplace. It's the Admin's responsibility to update the
organizational custom visuals' version.
Is there a way to disable the organizational store?
No, users always see the "MY ORGANIZATION" tab from the Power BI desktop and service. Admin can disable or
delete all organizational custom visuals from the admin portal and the organizational store is empty.
If the administrator disables custom visuals from the Admin portal (Tenant settings) do users still have access to
the organizational custom visuals?
Yes, if the admin disables the custom visuals from the admin portal, it doesn’t affect the organizational store. Some
organizations disable custom visuals and enable only hand-picked visuals that were imported and uploaded by the
Power BI administrator to the organizational store. Disabling the custom visuals from the Admin portal isn't
enforced in Power BI Desktop. Desktop users can still add and use custom visuals from the public marketplace in
their reports. However, those public custom visuals stop rendering once published to the Power BI Service and
issue an appropriate error. When using the Power BI service, you aren't able to import custom visuals from the
public marketplace. Only visuals from the organizational store can be imported because the custom visuals setting
in the admin portal is enforced in the Power BI service.
Why does the organizational store and organizational custom visuals make a great enterprise solution?
Everyone gets the same visual version, which is controlled by the Power BI administrator. Once the admin
updates the visual's version in the admin portal, all the users in the organization get the updated version
automatically.
No need to share visual files by email or shared folders anymore! One place, visible to all members who are
logged-in.
Security and supportability, new versions of organizational custom visuals are updated automatically in all
reports similar to marketplace visuals.
Users in the organization using the organizational custom visuals needs to be logged-in to see and use the
organizational custom visuals, which are a security element for organization.
 Admins can control which custom visuals to be available in the organization.
Admins can enable/disable visuals for testing from the admin portal. Better security enforcement as those
visuals will be allowed for organizational members only.

Certified custom visuals

What are certified custom visuals?
Certified custom visuals are visuals in the marketplace that meet certain specified code requirements and testing by
the Power BI team. The tests performed are designed to check that the visual does not access external services or
resources. However, Microsoft isn't the author of third-party custom visuals, and we advise customers to contact
the author directly to verify the functionality of such visual.
What tests are done during the certification process?
The certification process tests include but are not limited to: Code reviews, static code analysis, data leakage, data
fuzzing, penetration testing, access XSS testing, malicious data injection, input validation and functional testing.
Do you certify visuals every submission?
Yes. Every time a new version of certified visual is submitted to the Marketplace, the visual’s version update goes
under the same certification checks.
Note for developers: if you are submitting a version update of certified visual, you do not need to send a separate
email as first time certification request. Certification of version update happens automatically, and any violations
that cause a rejection are sent an email to explain what things need to be fixed.
Is it possible that a certified visual stops being certified with a new update?
No, this is not possible. A certified visual can’t be uncertified with a new update. The update is rejected.
Do I need to share my code in public repository if I am submitting to the certification process?
No, you don’t need to share your code publicly. However, you need to give us read permissions to check the visuals
code. E.g. private repository in GitHub.
Do we have to publish the visual in the Marketplace to certify it?
Yes. Publishing the visual to Marketplace first is an obligatory requirement for certification. To certify a custom
visual, it should be in our servers. We cannot certify private visuals.
How long does it take to certify my visual?
For updated version it may take up to 2 weeks. For a new submission (first-time certification) it may take up to 3
weeks.
Does the Certification process ensure that no data leakage occurs?
The tests performed are designed to check that the visual does not access external services or resources. However,
Microsoft is not the author of third-party custom visuals, and we advise customers to contact the author directly to
verify the functionality of such visual.
Are uncertified custom visuals safe to use?
Uncertified custom visuals do not necessarily mean unsafe visuals. Some visuals aren't certified because they don’t
comply with one or more of the certification requirements. For example, connecting to an external service like map
visuals, or visuals using commercial libraries.

Visuals with additional purchases

What is a visual with additional purchases?
A visual with additional purchases issimilar toin-app purchase(IAP )adds-in in the marketplace, these adds-in have a
pricetag Additional purchase may be required.
IAP custom visuals are free, downloadable custom visuals - users pay nothing to download those custom visuals
from the marketplace. IAP visuals offer optional in-app purchases for advanced features.
What's the benefit to developers?
IAP custom visuals inAppSource, will be discoverable to the many daily visitors, bringing valuable traffic, and
increased awareness for your IAP custom visuals and to you as the developer.
If until recently you managed those visuals through your website, now you can submit them to AppSource. Which
will increase the level of discoverability and visibility of the IAP visuals inside the Power BI community.
Visuals in the AppSource enjoy a Direct feedback channel from your customers who are using the IAP custom
visual, through the reviews and ratings system in the store.
Once the IAP visual was approved by the AppSource validation team, you may also submit those visuals for
certification. It is an optional process.
Once the visual is certified, IAP custom visuals can beexported to PowerPointand displayed in the emails received
when a usersubscribes to report pages. So today by submitting IAP visuals to the marketplace, IAP custom visuals
can also be certified and support extra feature set.
Do IAP visuals need to be certified?
Certification process is optional. It is up to the developer to decide whether to certify their IAP custom visuals or
not same with free visuals.
What is changing in the submission process?
The IAP custom visuals submission process to the marketplace, is same process as for free visuals. It happens
through the seller dashboard.The only change to the submission process is that developers will need to state in the
developer notes in the seller dashboard:“Visual with in-app purchase”. You’ll also need to providea license
key/token, if necessary to validate the paid/advanced features.
There will be no new option in the seller dashboard: free with in-app purchases, you will need to submit your IAP
visuals as free.
In addition, let users know what to expect by providing in your store long description whichfeatures are freeand
whichfeatures require additional purchasesto operate.
What should I do beforesubmittingmy IAP custom visual?
Ifyou’reworking on an IAP custom visual or already have one, make sure that itcomplies to theguidelines.
Ifyou have a logo in the custom visual, make sureit complies to the logo guidelines (color, location, size, and action
triggering).
You can also find,in the guidelines,best practicenotes.

NOTE
All free visuals should keep same free features previously offered. You may add optional advanced paid features on top of the
old free features. We recommend to submit the IAP visuals with the advanced features as new visuals and not to update the
old free ones.

Can I get my IAP custom visual certified?

Yes, same with free visuals. Once your IAP custom visual is approved by the AppSource team, you can submit your
visual to thecertification process.
To certify your visual, it should comply with the certificationrequirements, forexamplethe visual cannot access
external services for licenses validation.
Recall certification is an optional process, it's up to you to decide if you want your IAP visual to be certified.

Additional questions
How to get support?
Feel free to contact the custom visuals support team:*[email protected]*with any questions, comments,
or issues you have.

Next steps
For more information, visit Troubleshooting your Power BI custom visuals.
 Get Power BI Desktop
2/13/2019 • 6 minutes to read • Edit Online

Power BI Desktop lets you build advanced queries, models, and reports that visualize data. With Power BI
Desktop, you can build data models, create reports, and share your work by publishing to the Power BI service.
Power BI Desktop is a free download.
You can get Power BI Desktop in two ways, each of which is described in the following sections:
Download directly (an MSI package you download and install on your computer)
Install as an app from the Microsoft Store
Either approach will get the latest version of Power BI Desktop onto your computer, but there are a few
differences worth noting, which are described in the following sections.

Download Power BI Desktop

To download the most recent version of Power BI Desktop, you can select the download icon from the upper
right corner of the Power BI service, and select Power BI Desktop.

You can also download the latest version of Power BI Desktop from the following download page:
Power BI Desktop download (both 32- and 64-bit versions).

Regardless of which way you choose to download, once Power BI Desktop is downloaded you're prompted to
run the installation file:

Power BI Desktop is installed as an application, and runs on your desktop.

 NOTE
Installing the downloaded (MSI) version, and the Microsoft Store version of Power BI Desktop on the same computer
(sometimes referred to as a side-by-side installation) is not supported.

Install as an app from the Microsoft Store

You can also get Power BI Desktop from the Microsoft Store, using the following link:
Install Power BI Desktop from the Microsoft Store

There are a few advantages to getting Power BI Desktop from the Microsoft Store:
Automatic updates - Windows downloads the latest version automatically in the background as soon as it's
available, so your version will always be up to date.
Smaller downloads - The Microsoft Store ensures only components that have changed in each update are
downloaded to your machine, resulting in smaller downloads for each update.
Admin privilege is not required - when you download the MSI directly and install, you must be an
administrator for the installation to complete successfully. When you get Power BI Desktop from the
Microsoft Store, admin privilege is not required.
IT roll-out enabled - the Microsoft Store version can more easily be deployed, or rolled -out, to everyone in
your organization, and can make Power BI Desktop available through the Microsoft Store for Business.
Language detection - the Microsoft Store version includes all supported languages, and checks which
languages is being used on the computer each time it is launched. This also affects the localization of models
created in Power BI Desktop; for example, built-in date hierarchies will match the language that Power BI
 Desktop was using when the .pbix file was created.
There are a few consideration and limitations for installing Power BI Desktop from the Microsoft Store, which
include the following:
If you use the SAP connector, you may need to move your SAP driver files to the Windows\System32 folder.
Installing Power BI Desktop from the Microsoft Store doesn't copy user settings from the MSI version. You
might have to reconnect to your recent datasources and re-enter your data source credentials.

NOTE
Installing the downloaded (MSI) version, and the Microsoft Store version of Power BI Desktop on the same computer
(sometimes referred to as a side-by-side installation) is not supported. You should manually uninstall Power BI Desktop
before downloading it from the Microsoft Store

NOTE
The Power BI Report Server version of Power BI Desktop is a separate and different installation from the versions
discussed in this article. For information about the Report Server version of Power BI Desktop, see Create a Power BI
report for Power BI Report Server.

Using Power BI Desktop

When you launch Power BI Desktop, a Welcome screen is displayed.

If this is your first time using Power BI Desktop (if the installation is not an upgrade), you'll be prompted to fill
out a form and answer a few questions, or sign in to the Power BI service before you'll be able to proceed.
From there, you can begin creating data models or reports, then share them with others on the Power BI service.
Check out the More information links at the end of this article for links to guides that can help you get started
using Power BI Desktop.

Minimum requirements
The following list provides the minimum requirements to run Power BI Desktop:
 Windows 7 / Windows Server 2008 R2, or later
.NET 4.5
Internet Explorer 9 or later
Memory (RAM ): At least 1 GB available, 1.5 GB or more recommended.
Display: At least 1440x900 or 1600x900 (16:9) recommended. Lower resolutions such as 1024x768 or
1280x800 are not recommended, as certain controls (such as closing the startup screen) display beyond those
resolutions.
Windows Display settings: If your display settings are set to change the size of text, apps, and other items
to more than 100%, you may not be able to see certain dialogs that must be closed or responded to in order
to proceed using Power BI Desktop. If you encounter this issue, check your Display settings by going to
Settings > System > Display in Windows, and use the slider to return display settings to 100%.
CPU: 1 gigahertz (GHz) or faster x86- or x64-bit processor recommended.

Considerations and Limitations

We always want your experience with Power BI Desktop to be great. There may be occasions when you run into
an issue with Power BI Desktop, so this section contains solutions or suggestions to address issues that might
arise.
Issues when using previous releases of Power BI Desktop
Some users encounter an error similar to the following when using an outdated version of Power BI Desktop:

"We weren't able to restore the saved database to the model"

Updating to the current version of Power BI Desktop usually solves this issue.
Disabling notifications
We recommend updating to the most recent version of Power BI Desktop to take advantage of advances in
features, performance, stability, and other improvements. Some organizations may not want users to update to
each new version. You can disable notifications by modifying the registry with the following steps:
1. Using the Registry Editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Power BI
Desktop
2. Create a new entry there with the following settings: REG_DWORD : DisableUpdateNotification
3. Set the value of that new entry to 1.
You'll need to restart your computer for the change to take effect.
Power BI Desktop loads with a partial screen
In certain circumstances, including certain screen resolution configurations, some users may see Power BI
Desktop render content with large black areas. This is generally a result of recent operating system updates that
affect how items are rendered, rather than a direct result of how Power BI Desktop presents content. Regardless,
large black areas are not as compelling as great visuals, so to address this issue, take the following steps:
1. Press the Start key and type the world blurry into the search bar that appears.
2. In the dialog that appears, select the option: Let Windows fix apps that are blurry.
3. Restart Power BI Desktop.
This issue may resolve after subsequent Windows updates are released.

Next steps
Once you get Power BI Desktop installed, the following content can help you get up and running quickly:
What is Power BI Desktop?
Query Overview with Power BI Desktop
Data Sources in Power BI Desktop
Connect to Data in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Common Query Tasks in Power BI Desktop
 Getting started with Power BI Desktop
1/14/2019 • 18 minutes to read • Edit Online

Welcome to the Power BI Desktop Getting Started Guide. This short tour of Power BI Desktop gets you
acquainted with how it works, demonstrates what it can do, and accelerates your ability to build robust data
models — along with amazing reports — that amplify your business intelligence efforts.
Prefer to watch instead of read? Feel free to take a look at our getting started video. And if you want to follow
along with the video with matching sample data, you can download this sample Excel workbook.

Power BI Desktop lets you create a collection of queries, data connections, and reports that can easily be shared
with others. Power BI Desktop integrates proven Microsoft technologies – the powerful Query engine, data
modeling, and visualizations – and works seamlessly with the online Power BI service.
With the combination of Power BI Desktop (where analysts and others can create powerful data connections,
models and reports) and the Power BI service (where Power BI Desktop reports can be shared so users can
view and interact with them), new insights from the world of data are easier to model, build, share, and extend.
Data analysts will find Power BI Desktop a powerful, flexible, and a highly accessible tool to connect with and
shape the world of data, build robust models, and craft well-structured reports.

How to use this guide

You can use this guide in a couple of ways – scan it for a quick overview, or read through each section for a
strong understanding of how Power BI Desktop works.
If you’re in a hurry you can do a visual sweep of this guide in just a couple minutes, and come away with a good
sense of how Power BI Desktop operates, and how to use it. Most of this guide consists of screens that visually
show how Power BI Desktop works.
For a more thorough understanding you can read through each section, perform the steps, and walk away with
your own Power BI Desktop file that’s ready to post onto the Power BI service, and share with others.

NOTE
There is also a separate and specialized version of Power BI called Power BI Report Server, which is for customers who
need their data and reporting to remain on-premises. For use with that specialized version, there's also a separate and
specialized version of Power BI Desktop called Power BI Desktop for Power BI Report Server, which works only with
the Report Server version of Power BI. This article describes the standard Power BI Desktop.

How Power BI Desktop works

With Power BI Desktop, you connect to data (usually multiple data sources), shape that data (with queries that
build insightful, compelling data models), and use that model to create reports (which others can leverage, build
upon, and share).
When the steps are completed to your satisfaction – connect, shape, and report – you can save that work in
Power BI Desktop file format, which is the .pbix extension. Power BI Desktop files can be shared like any other
file, but the most compelling way to share Power BI Desktop files is to upload them (share them) on the Power
BI service.
Power BI Desktop centralizes, simplifies, and streamlines what can otherwise be a scattered, disconnected, and
arduous process of designing and creating business intelligence repositories and reports.
Ready to give it a try? Let’s get started.

Install and run Power BI Desktop

You can download Power BI Desktop from the Power BI service, by selecting the gear icon, then select Power
BI Desktop.

Power BI Desktop is installed as an application, and runs on your desktop.

When you run Power BI Desktop, a Welcome screen is displayed.

You can Get Data, see Recent Sources, or Open Other Reports directly from the Welcome screen (from the
links in the left pane). If you close the screen (select the x in the top right corner), the Report view of Power BI
Desktop is displayed.
There are three views in Power BI Desktop: Report view, Data view, and Relationships view. Power BI Desktop
also includes Query Editor, which opens in a separate window. In Query Editor, you can build queries and
transform data, then load that refined data model into Power BI Desktop, and create reports.
The following screen shows the three view icons along the left of Power BI Desktop: Report, Data, and
Relationships, from top to bottom. The currently displayed view is indicated by the yellow bar along the left. In
this case, Report view is currently displayed. You can change views by selecting any of those three icons.

With Power BI Desktop installed you’re ready to connect to data, shape data, and build reports (usually in that
order). In the next few sections, we take a tour through each in turn.

Connect to data
With Power BI Desktop installed, you’re ready to connect to the ever expanding world of data. There are all sorts
of data sources available in the Query window. The following image shows how to connect to data, by selecting
the Home ribbon, then Get Data > More.
For this quick tour, we'll connect to a couple different Web data sources.
Imagine you’re retiring – you want to live where there’s lots of sunshine, preferable taxes, and good health care –
or perhaps you’re a data analyst, and you want that information to help your customers. For example, perhaps
you want to help your sunglasses retailer target sales where the sun shines most frequently.
Either way, the following Web resource has interesting data about those topics, and more:
http://www.bankrate.com/finance/retirement/best-places-retire-how -state-ranks.aspx
Select Get Data > Web and paste the address.

When you select OK, the Query functionality of Power BI Desktop goes to work. Query contacts the Web
resource, and the Navigator window returns what it found on that Web page. In this case, it found a table (Table
0) and the overall Web Document. We’re interested in the table, so we select it from the list. The Navigator
window displays a preview.
At this point we can edit the query before loading the table, by selecting Edit from the bottom of the window, or
we can load the table.
When we select Edit, Query Editor launches and a representative view of the table is presented. The Query
Settings pane is displayed (if it’s not, you can select View from the ribbon, then Show > Query Settings to
display the Query Settings pane). Here’s what that looks like.
For more information about connecting to data, see Connect to Data in Power BI Desktop.
In the next section, we adjust the data so it meets our needs. The process of adjusting connected data is called
shaping data.

Shape and combine data

Now that we’ve connected to a data source, we need to adjust the data to meet our needs. Sometimes adjusting
means transforming the data – such as renaming columns or tables, changing text to numbers, removing rows,
setting the first row as headers, and so on.
The Query editor in Power BI Desktop makes ample use of right-click menus, in addition to having tasks
available on the ribbon. Most of what you can select in the Transform ribbon is also available by right-clicking
an item (such as a column) and choosing from the menu that appears.

Shape data
When you shape data in the Query Editor, you’re providing step-by-step instructions (that Query Editor
carries out for you) to adjust the data as Query Editor loads and presents it. The original data source is not
affected; only this particular view of the data is adjusted, or shaped.
The steps you specify (such as rename a table, transform a data type, or delete columns) are recorded by Query
Editor, and each time this query connects to the data source those steps are carried out so that the data is
always shaped the way you specify. This process occurs whenever you use the query in Power BI Desktop, or for
anyone who uses your shared query, such as in the Power BI service. Those steps are captured, sequentially, in
the Query Settings pane under Applied Steps.
The following image shows the Query Settings pane for a query that has been shaped – we’ll go through each
of those steps in the next few paragraphs.
Let’s get back to our retirement data, which we found by connecting to a Web data source, and shape that data
to fit our needs.
For starters, most ratings were brought into Query Editor as whole numbers, but not all of them (one column
contained text and numbers, so it wasn't automatically converted). We need the data to be numbers. No problem
– just right-click the column header, and select Change Type > Whole Number to change the data type. If we
needed to choose more than one column, we could first select a column then hold down SHIFT, select additional
adjacent columns, and then right-click a column header to change all selected columns. You can also use CTRL
to select non-adjacent columns.
You can also change, or transform, those columns from text to header by using the Transform ribbon. Here’s the
Transform ribbon, with an arrow pointing toward the Data Type button, which lets you transform the current
data type to another.

Note that in Query Settings, the Applied Steps reflect the changes that were made. If I want to remove any
step from the shaping process, I simply select that step, and then select the X to the left of the step.
We need to make a few more changes to get the query where we want it:
Remove the first column – we don’t need it, it just includes redundant rows that say “Check out how your
state ranks for retirement” which is an artifact of this being a Web based table
Fix a few Errors – on the Web page, one column had text mixed in with the numbers (some states tied in one
category). That works well in the website, but not for our data analysis. It's easy (in this case) to fix, and shows
some cool features and capabilities of Query Editor and its Applied Steps
Change the Table Name – that Table 0 is not a useful descriptor, but changing it simple
Each of these steps is demonstrated in Shape and Combine Data in Power BI Desktop. Feel free to check
out that page, or keep going in this document to see what you would do next. The next section picks up after the
changes above are applied.

Combine data
That data about various states is interesting, and will be useful for building additional analysis efforts and
queries. But there’s one problem: most data out there uses a two-letter abbreviation for state codes, not the full
name of the state. We need some way to associate state names with their abbreviations.
We’re in luck: there’s another public data source that does just that, but it needs a fair amount of shaping before
we can connect it to our retirement table. Here’s the Web resource for state abbreviations:
http://en.wikipedia.org/wiki/List_of_U.S._state_abbreviations
From the Home ribbon in Query Editor, we select Get Data > Web and type the address, select OK, and the
Navigator window shows what it found on that Web page.
We select Table[edit] because it includes the data we want, but it’s going to take quite a bit of shaping to pare
that table’s data down. Each of these steps is also demonstrated in Shape and Combine Data in Power BI
Desktop. To summarize those steps, here's what we do:
We select Edit, then:
Remove the top two rows – they’re a result of the way that Web page’s table was created, and we don’t need
them.
Remove the bottom 26 rows – they’re all the territories, which we don’t need to include.
Filter out Washington DC – the retirement stats table doesn't include DC, so we'll exclude it from our list.
Remove a few unneeded columns – we only need the mapping of state to its official two-letter abbreviation,
so we can remove the other columns.
Use the first row as headers – since we removed the top three rows, the current top row is the header we
want.

NOTE
This is a good time to point out that the sequence of applied steps in Query Editor is important, and can affect
how the data is shaped. It’s also important to consider how one step may impact another subsequent step; if you
remove a step from the Applied Steps, subsequent steps may not behave as originally intended, because of the
impact of the query’s sequence of steps.

Rename the columns, and the table itself – as usual, there are a couple ways to rename a column, you can
choose whichever you prefer.
With the StateCodes table shaped, we can combine these two tables, or queries, into one; since the tables we
now have are a result of the queries we applied to the data, they’re often referred to as queries.
There are two primary ways of combining queries – merging and appending.
When you have one or more columns that you’d like to add to another query, you merge the queries. When you
have additional rows of data that you’d like to add to an existing query, you append the query.
In this case we want to merge queries. To get started, we select the query into which we want the other query to
merge, then select Merge Queries from the Home tab on the ribbon.

The Merge window appears, prompting us to select which table we’d like merged into the selected table, and
then, the matching columns to use for the merge. Select State from the RetirementStats table (query), then select
the StateCodes query (easy in this case, since there’s only one other query – when you connect to many data
sources, there are many queries to choose from). When we select the correct matching columns – State from
RetirementStats, and State Name from StateCodes – the Merge window looks like the following, and the OK
button is enabled.
A NewColumn is created at the end of the query, which is the contents of the table (query) that was merged
with the existing query. All columns from the merged query are condensed into the NewColumn, but you can
select to Expand the table, and include whichever columns you want. To expand the merged table, and select
which columns to include, select the expand icon ( ). The Expand window appears.
In this case, we only want the State Code column, so we select only that column and then select OK. We clear the
checkbox from Use original column name as prefix because we don’t need or want that; if we leave that
selected, the merged column would be named NewColumn.State Code (the original column name, or
NewColumn, then a dot, then the name of the column being brought into the query).

NOTE
Want to play around with how to bring in that NewColumn table? You can experiment a bit, and if you don’t like the
results, just delete that step from the Applied Steps list in the Query Settings pane; your query returns to the state
prior to applying that Expand step. It’s like a free do-over, which you can do as many times as you like until the expand
process looks the way you want it.

We now have a single query (table) that combined two data sources, each of which has been shaped to meet our
needs. This query can serve as a basis for lots of additional, interesting data connections – such as housing cost
statistics, demographics, or job opportunities in any state.
For a more complete description of each of these shape and combine data steps, see Shape and Combine Data
in Power BI Desktop.
For now, we have enough data to create a few interesting reports, all within Power BI Desktop. Since this is a
milestone let’s save this Power BI Desktop file – we’ll call it Getting Started with Power BI Desktop. To apply
the changes in Query Editor and load them into Power BI Desktop, select Close & Apply from the Home
ribbon.
Build reports
Additional changes can be made after the table is loaded, and you can reload a model to apply any changes you
make. But for now this will do. In Power BI Desktop Report view, you can begin to build reports.
The Report view has five main areas:
1. The ribbon, which displays common tasks associated with reports and visualizations
2. The Report view, or canvas, where visualizations are created and arranged
3. The Pages tab area along the bottom, which lets you select or add a report page
4. The Visualizations pane, where you can change visualizations, customize colors or axes, apply filters,
drag fields, and more
5. The Fields pane, where query elements and filters can be dragged onto the Report view, or dragged to
the Filters area of the Visualizations pane
The Visualizations and Fields pane can be collapsed by selecting the small arrow along the edge, providing
more space in the Report view to build cool visualizations. When modifying visualizations, you'll also see these
arrows pointing up or down, which means you can expand or collapse that section, accordingly.

To create a visualization, just drag a field from the Fields list onto the Report view. In this case, let’s drag the
State field from RetirementStats, and see what happens.

Look at that... Power BI Desktop automatically created a map-based visualization, because it recognized that the
State field contained geolocation data.
Notice that in the Visualizations pane, I can select different types of visualizations, and in the area below those
icons, I can drag fields to different areas to apply a Legend, or otherwise modify the visualization.

Let’s fast-forward a bit, and see what the Report view looks like after a handful of visualizations have been
added, as well as a few new Report pages. For more information about reports, see Report View in Power BI
Desktop.
The first Report page provides a perspective of the data based on Overall rank. When we select one of the
visualizations, the Fields and Filters pane shows which fields are selected, and the structure of the visualization
(which fields are applied to the Shared Axis, Column Values, and Line Values).
There are six Pages in this Report, each visualizing certain elements of our data.
1. The first page, shown above, shows all states based on Overall rank.
2. The second page focuses on the top ten states based on Overall rank.
3. For the third page, the best 10 states for cost of living (and associated data) are visualized.
4. Weather is the focus of the fourth page, filtered to the 15 sunniest states.
5. On the fifth page, Community well-being is charted and visualized for the top 15 states.
6. Lastly, crime statistics are visualized, showing the best (and well, the last) ten states.
Here’s what the cost of living-focused Report page looks like.

There are all sorts of interesting reports and visualizations you can create.

Share your work

Now that we have a Power BI Desktop report that’s reasonably complete, we can share it with others on the
Power BI service. There are a few ways to share your work in Power BI Desktop. You can publish to the Power
BI service, you can upload the .pbix file directly from the Power BI service, or you can save the .pbix file and send
it like any other file.
First, let's look at publishing to the Power BI service directly from Power BI Desktop. On the Home ribbon,
select Publish.
You may be prompted to sign in to Power BI.

When you've signed in and the publish process is complete, you see the following dialog.

When you sign in to Power BI, you'll see Power BI Desktop file you just loaded in the Dashboards, Reports, and
Datasets sections of the service.
Another way to share your work is to load it from within the Power BI service. The following link brings up the
Power BI service in a browser:
https://app.powerbi.com

Select Get Data to start the process of loading your Power BI Desktop report.
The Get Data page appears, from which you can select where to get your data from. In this case, we select Get
from the Files box.

The Files view appears. In this case, we select Local File.

When you select the file, Power BI uploads the file.

Once the file is uploaded, you can select the file from the Reports in the left pane of the Power BI service.
The Power BI service displays the first page of the report. Along the bottom of the page, you can select any tab
to display that page of the report.

You can make changes to a report in the Power BI service by selecting Edit Report from the top of the report
canvas.
To save your report, select File > Save As from the service. There are all sorts of interesting visuals you can
create in the Power BI service from your report, which you can pin to a dashboard. To learn about dashboards
in the Power BI service, see Tips for designing a great dashboard.

Once saved, select the Share icon on the main page.

From here, you can send an email to colleagues with whom you’d like to share the dashboard.
For more information about creating, sharing, and modifying dashboards, see Share a dashboard.
There are all sorts of compelling data-related mash-ups and visualizations you can do with Power BI Desktop,
and with the Power BI service. Check out the next section for more information.

Diagnostics
Power BI desktop supports connecting to a diagnostics port. The diagnostic port allows for other tools to
connect to and perform traces for diagnostic purposes. Making any changes to the model is not supported!
Changes to the model may lead to corruption and data loss.

Next steps
There are all sorts of things you can do with Power BI Desktop. For more information on its capabilities, check
out the following resources:
Query Overview with Power BI Desktop
Data Sources in Power BI Desktop
Connect to Data in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Common Query Tasks in Power BI Desktop
 Common query tasks in Power BI Desktop
2/13/2019 • 8 minutes to read • Edit Online

When working in the Query Editor window of Power BI Desktop, there are a handful of commonly used tasks.
This document demonstrates those common tasks, and provides links for additional information.
The common query tasks demonstrated here are the following:
Connect to data
Shape and combine data
Group rows
Pivot columns
Create custom columns
Query formulas
We’ll use a few data connections to complete these tasks. The data is available for you to download or connect to,
in case you want to step through these tasks yourself.
The first data connection is an Excel workbook, which you can download from this link. The other is a Web
resource (which is also used in other Power BI Desktop help content) which can be accessed from here:
http://www.bankrate.com/finance/retirement/best-places-retire-how -state-ranks.aspx
The steps necessary to connect to both of those data sources is where the common Query tasks begin.

Connect to data
To connect to data in Power BI Desktop, select the Get Data button from the Home tab on the ribbon. Power BI
Desktop presents a menu with the most common data sources. For a complete list of data sources to which
Power BI Desktop can connect, select the More... button at the bottom of the menu. For more information, see
Data Sources in Power BI Desktop.
To start with, select Excel and navigate to the workbook, then select it. Query inspects the workbook, then
presents the data it found in the Navigator window.
You can select Edit to adjust, or shape, the data before loading it into Power BI Desktop. Editing a query before
loading is especially useful when working with large data sets that you intend to pare down before loading. We
want to do that, so we select Edit.
Connecting to different types of data is just as easy. We also want to connect to a Web resource. Select Get Data
> More... and then select Other > Web.

The From Web window appears, where you can type in the URL of the Web page.

Select OK, and like before, Power BI Desktop inspects the workbook and presents the data it finds in the
Navigator window.
Other data connections are similar. If authentication is required to make a data connection, Power BI Desktop
prompts you for the appropriate credentials.
For a step-by-step demonstration of connecting to data in Power BI Desktop, see Connect to Data in Power BI
Desktop.

Shape and combine data

You can easily shape and combine data with Query Editor. This section includes a few examples of how you can
shape data. For a more complete demonstration of shaping and combining data, see Shape and Combine Data
with Power BI Desktop.
In the previous section we connected to two sets of data – an Excel workbook, and a Web resource. Once loaded
in Query Editor we see the following, with the query from the Web page selected (taken from the available
queries listed in the Queries pane, on the left side of the Query Editor window ).

When you shape data, you transform a data source into the form and format that meets your needs. In this case,
we don’t need that first column, titled Header, so we’ll remove it.
In Query Editor, many commands can be found in the ribbon, and in a context-sensitive right-click menu. For
example, when you right-click on the Header column, the menu that appears lets you remove the column. You
could also select the column and then select the Remove Columns button from the ribbon.
There are many other ways you could shape the data in this query; you could remove any number of rows from
the top, or from the bottom; you could add columns, split columns, replace values, and perform other shaping
tasks to direct Query Editor to get the data how you want it.

Group rows
In Query Editor, you can group the values in multiple rows into a single value. This can be useful when
summarizing the number of products offered, the total sales, or the count of students.
In this example, we group rows in an education enrollment data set. The data is from an Excel workbook, and has
been shaped in Query Editor to get just the columns we need, rename the table, and perform a few other
transforms.
Let’s find out how many Agencies (this includes school districts, and other education agencies such as regional
service districts, and so on) each state has. We select the State Abbr column then select the Group By button in
the Transform tab or the Home tab of the ribbon (Group By is available in both tabs).
The Group By… window appears. When Query Editor groups rows, it creates a new column into which it places
the Group By results. You can adjust the Group By operation in the following ways:
1. Group by – this is the column to be grouped; Query Editor chooses the selected column, but you can change it
in this window to be any column in the table.
2. New column name – Query Editor suggests a name for the new column, based on the operation it applies to
the column being grouped, but you can name the new column anything you want.
3. Operation – here you specify the operation that Query Editor applies.
4. Add grouping and Add aggregation – these options appear after selecting the Advanced option. You can
perform grouping operations (Group By actions) on multiple columns, and perform multiple aggregations, all
within the Group By window, and all in one operation. Query Editor creates a new column (based on your
selections in this window ) that operates on multiple columns.
Select the Add grouping or Add aggregation button to add more groupings or aggregations to a Group By
operation. You can remove a grouping or aggregation by selecting the ... icon and selecting Delete, so go ahead
and try it and see what it looks like.

When we select OK, Query performs the Group By operation, and returns the results. Whew, look at that – Ohio,
Texas, Illinois, and California now each have over a thousand agencies!

And with Query Editor, you can always remove the last shaping operation by selecting the X next to the step just
completed. So go ahead and experiment, redo the step if you don’t like the results, until Query Editor shapes
your data just the way you want it.

Pivot columns
With Power BI Desktop, you can pivot columns, and create a table that contains aggregated values for each
unique value in a column. For example, if you need to know how many different products you have in each
product category, you can quickly create a table the does precisely that.
Let’s look at an example. The following Products table has been shaped to only show each unique product (by
name), and which category each product falls under. To create a new table that shows a count of products for
each category (based on the CategoryName column), select the column, then select Pivot Column from the
Transform tab on the ribbon.
The Pivot Column window appears, letting you know which column’s values will be used to create new columns
(1), and when you expand Advanced options (2), you can select the function that will be applied to the
aggregated values (3).

When you select OK, Query displays the table according to the transform instructions provided in the Pivot
Column window.
Create custom columns
In Query Editor you can create custom formulas that operate on multiple columns in your table, then place the
results of such formulas into a new (custom) column. Query Editor makes it easy to create custom columns.
In Query Editor, select Custom Column from the Add Column tab on the ribbon.

The following window appears. In the following example, we create a custom column called Percent ELL that
calculates the percentage of total students that are English Language Learners (ELL ).
Like any other applied step in Query Editor, if the new custom column doesn’t provide the data you’re looking
for, you can simply delete the step from the Applied Steps section of the Query Settings pane by selecting the
X next to the Added Custom step.

Query formulas
You can edit the steps that Query Editor generates, and you can create custom formulas to get precise control
over connecting to and shaping your data. Whenever Query Editor performs an action on data, the formula
associated with the action is displayed in the Formula Bar. To view the Formula Bar, select the checkbox next to
Formula Bar in the View tab of the ribbon.
Query Editor keeps all applied steps for each query as text that you can view or modify. You can view or modify
the text for any query using the Advanced Editor, which is displayed when you select Advanced Editor from
the View tab of the ribbon.

Here's a look at the Advanced Editor, with the query steps associated with the USA_StudentEnrollment
query displayed. These steps are created in the Power Query Formula Language, often referred to as M. For
information, see Learn about Power Query formulas. To view the language specification itself, see Microsoft
Power Query for Excel Formula Language Specification.
Power BI Desktop provides an extensive set of formula categories. For more information, and a complete
reference of all Query Editor formulas, visit Power Query Formula Categories.
The formula categories for Query Editor are the following:
Number
Constants
Information
Conversion and formatting
Format
Rounding
Operations
Random
Trigonometry
Bytes
Text
Information
Text comparisons
Extraction
Modification
Membership
Transformations
Logical
Date
Time
DateTime
DateTimeZone
Duration
Record
Information
Transformations
 Selection
Serialization
List
Information
Selection
Transformation
Membership
Set operations
Ordering
Averages
Addition
Numerics
Generators
Table
Table construction
Conversions
Information
Row operations
Column operations
Membership
Values
Arithmetic operations
Parameter Types
Metadata
Accessing data
URI
Binary formats
Reading numbers
Binary
Lines
Expression
Function
Error
Comparer
Splitter
Combiner
Replacer
Type

Next steps
There are all sorts of things you can do with Power BI Desktop. For more information on its capabilities, check
out the following resources:
What is Power BI Desktop?
Query Overview with Power BI Desktop
Data Sources in Power BI Desktop
Connect to Data in Power BI Desktop
Shape and Combine Data with Power BI Desktop
 Create and manage relationships in Power BI
Desktop
2/13/2019 • 16 minutes to read • Edit Online

When you import multiple tables, chances are you’re going to do some analysis using data from all those tables.
Relationships between those tables are necessary in order to accurately calculate results and display the correct
information in your reports. Power BI Desktop makes creating those relationships easy. In-fact, in most cases you
won’t have to do anything, the Autodetect feature can do it for you. However, in some cases you might have to
create relationships yourself, or you might need to make some changes to a relationship. Either way, it’s important
to understand relationships in Power BI Desktop and how to create and edit them.

Autodetect during load

If you query two or more tables at the same time, when the data is loaded, Power BI Desktop will attempt to find
and create relationships for you. Cardinality, Cross filter direction, and Active properties are automatically set.
Power BI Desktop looks at column names in the tables you are querying to determine if there are any potential
relationships. If there are, those relationships are created automatically. If Power BI Desktop cannot determine
with a high-level of confidence there is a match, it will not automatically create the relationship. You can still use
the Manage Relationships dialog to create or edit relationships.

Create a relationship by using Autodetect

On the Home tab, click Manage Relationships > AutoDetect.

Create a relationship manually

1. On the Home tab, click Manage Relationships > New.
2. In the Create Relationship dialog, in the first table drop-down list, select a table, and then select the column
you want to use in the relationship.
3. In the to second table drop-down list, select the other table you want in the relationship, then select the other
column you want to use, and then click OK.

By default, Power BI Desktop will automatically configure the Cardinality (direction), Cross filter direction, and
Active properties for your new relationship; however, you can change these if necessary. To learn more, see the
Understanding additional options section later in this article.
Note that you'll see an error that states One of the columns must have unique values if none of the tables selected
for the relationship has unique values. At least one table in a relationship must have a distinct, unique list of key
values, which is a common requirement for all relational database technologies.
If you encounter that error, there are a couple ways to fix the issue:
Use "Remove Duplicate Rows" to create a column with unique values. The drawback to this approach is that
you will lose information when duplicate rows are removed, and often a key (row ) is duplicated for good
reason.
Add an intermediary table made of the list of distinct key values to the model, which will then be linked to both
original columns in the relationship.
For more detailed information, see the blog post that discusses this in detail.

Edit a relationship
1. On the Home tab, click Manage Relationships.
2. In the Manage Relationships dialog, select the relationship, then click Edit.
Configure additional options
When you create or edit a relationship, you can configure additional options. By default, additional options are
automatically configured based on a best guess. This can be different for each relationship based on the data in
the columns.

Cardinality
Many to One (*:1) - This is the most common, default type. This means the column in one table can have more
than one instance of a value, and the other related table, often know as the Lookup table, has only one instance of
a value.
One to One (1:1) - This means the column in one table has only one instance of a particular value, and the other
related table has only one instance of a particular value.
Many-to-many relationships: With composite models, you can establish many-to-many relationships between
tables. This approach removes requirements for unique values in tables. It also removes previous workarounds,
such as introducing new tables only to establish relationships. For more detailed information, see Relationships
with a many-many cardinality.
See the Understanding additional options section later in this article for more details about when to change
cardinality.

Cross filter direction

Both - This is the most common, default direction. This means for filtering purposes, both tables are treated as if
they're a single table. This works well with a single table that has a number of lookup tables that surround it. An
example is a Sales actuals table with a lookup table for department. This is often called a Star schema
configuration (a central table with several lookup tables.) However, if you have two or more tables that also have
lookup tables (with some in common) then you wouldn't want to use the Both setting. To continue the previous
example, in this case, you also have a budget sales table that records target budget for each department. And, the
department table is connected to both the sales and the budget table. Avoid the Both setting for this kind of
configuration.
Single - This means that filtering choices in connected tables work on the table where values are being
aggregated. If you import a Power Pivot in Excel 2013 or earlier data model, all relationships will have a single
direction.
See the Understanding additional options section later in this article for more details about when to change cross
filter direction.

Make this relationship active

When checked, this means the relationship serves as the active, default relationship. In cases where there is more
than one relationship between two tables, the active relationship provides a way for Power BI Desktop to
automatically create visualizations that include both tables.
See the Understanding additional options section later in this article for more details about when to make a
particular relationship active.

Understanding relationships
Once you have connected two tables together with a relationship, you can work with the data in both tables as if
they were a single table, freeing you from having to worry about relationship details, or flattening those tables into
a single table before importing them. In many situations, Power BI Desktop can automatically create relationships
for you, so creating those relationships yourself might not even be needed. However, if Power BI Desktop can’t
determine with a high-degree of certainty that a relationship between two tables should exist, it will not
automatically create the relationship. In that case, you will need to create the relationship.
Let’s do a little tutorial, to better show you how relationships work in Power BI Desktop.

TIP
You can complete this lesson yourself. Copy the ProjectHours table below into an Excel worksheet, select all of the cells, click
INSERT > Table. In the Create Table dialog, just click OK. Then in Table Name, type ProjectHours. Do the same for the
CompanyProject table. You can then import the data by using Get Data in Power BI Desktop. Select your workbook and
tables as a data source.

This first table, ProjectHours, is a record of work tickets that record the number of hours a person has worked on a
particular project.
ProjectHours

TICKET SUBMITTEDBY HOURS PROJECT DATESUBMIT

1001 Brewer, Alan 22 Blue 1/1/2013

1002 Brewer, Alan 26 Red 2/1/2013

1003 Ito, Shu 34 Yellow 12/4/2012

1004 Brewer, Alan 13 Orange 1/2/2012

1005 Bowen, Eli 29 Purple 10/1/2013

1006 Bento, Nuno 35 Green 2/1/2013

1007 Hamilton, David 10 Yellow 10/1/2013

1008 Han, Mu 28 Orange 1/2/2012

1009 Ito, Shu 22 Purple 2/1/2013

1010 Bowen, Eli 28 Green 10/1/2013

1011 Bowen, Eli 9 Blue 10/15/2013

This second table, CompanyProject, is a list of projects with an assigned priority, A, B, or C.

CompanyProject

PROJNAME PRIORITY

Blue A

Red B

Green C

Yellow C
 PROJNAME PRIORITY

Purple B

Orange C

Notice that each table has a project column. Each is named slightly different, but the values look like they’re the
same. That’s important, and we’ll get back to it in a little bit.
Now that we have our two tables imported into a model, let’s create a report. The first thing we want to get is the
number of hours submitted by project priority, so we select Priority and Hours from Fields.

If we look at our table in the Report canvas, you’ll see the number of hours is 256.00 for each project, and it’s also
the total. Clearly this isn’t correct. Why? It’s because we can’t calculate a sum total of values from one table (Hours
in the Project table), sliced by values in another table (Priority in the CompanyProject table) without a relationship
between these two tables.
So, let’s create a relationship between these two tables.
Remember those columns we saw in both tables with a project name, but with values that look alike? We’re going
to use these two columns to create a relationship between our tables.
Why these columns? Well, if we look at the Project column in the ProjectHours table, we see values like Blue, Red,
Yellow, Orange, and so on. In fact, we see several rows that have the same value. In-effect, we have many color
values for Project.
If we look at the ProjName column in the CompanyProject table, we see there’s only one of each of the color
values for project. Each color value in this table is unique, and that’s important, because we can create a
relationship between these two tables. In this case, a many-to-one relationship. In a many-to-one relationship, at
least one column in one of the tables must contain unique values. There are some additional options for some
relationships, and we’ll look at those later, but for now, let’s create a relationship between the Project columns in
each of our two tables.
To create the new relationship
1. Click Manage Relationships.
2. In Manage Relationships, click New. This opens the Create Relationship dialog, where we can select the
tables, columns, and any additional settings we want for our relationship.
3. In the first table, select ProjectHours, then select the Project column. This is the many side of our relationship.
4. In the second table, select CompanyProject, then select the ProjName column. This is the one side of our
relationship.
5. Go ahead and click OK in both the Create Relationship dialog and the Manage Relationships dialog.
In the interest of full disclosure, you really just created this relationship the hard way. You could've just clicked on
the Autodetect button in the Manage Relationships dialog. In fact, Autodetect would have already done it for you
when you loaded the data if both columns had the same name. But, what’s the challenge in that?
Now, let’s look at the table in our Report canvas again.

Now that looks a whole lot better, doesn’t it?

When we sum up hours by Priority, Power BI Desktop will look for every instance of the unique color values in the
CompanyProject lookup table, and then look for every instance of each of those values in the CompanyProject
table, and calculate a sum total for each unique value.
That was pretty easy, in fact, with Autodetect, you might not even have to do this much.

Understanding additional options

When a relationship is created, either with Autodetect or one you create manually, Power BI Desktop will
automatically configure additional options based on the data in your tables. You can configure these additional
relationship properties located in the lowest portion of the Create/Edit relationship dialog.

As we said, these are usually set automatically and you won’t need to mess with them; however, there are several
situations where you might want to configure these options yourself.

Future updates to the data require a different cardinality

Normally, Power BI Desktop can automatically determine the best cardinality for the relationship. If you do need
to override the automatic setting, because you know the data will change in the future, you can select it in the
Cardinality control. Let’s look at an example where we need to select a different cardinality.
The CompanyProjectPriority table below is a list of all company projects and their priority. The ProjectBudget
table is the set of projects for which budget has been approved.
ProjectBudget

APPROVED PROJECTS BUDGETALLOCATION ALLOCATIONDATE

Blue 40,000 12/1/2012

Red 100,000 12/1/2012

Green 50,000 12/1/2012

CompanyProjectPriority

PROJECT PRIORITY

Blue A

Red B

Green C

Yellow C

Purple B

Orange C

If we create a relationship between the Project column in the CompanyProjectPriority table and ApprovedProjects
column in the ProjectBudget table, like this:
Cardinality is automatically set to One-to-One (1:1), and cross filtering to be Both (as shown). This is because to
Power BI Desktop, the best combination of the two tables really looks like this:

PROJECT PRIORITY BUDGETALLOCATION ALLOCATIONDATE

Blue A 40,000 12/1/2012

Red B 100,000 12/1/2012

Green C 50,000 12/1/2012

Yellow C

Purple B

Orange C

There is a one-to-one relationship between our two tables because there are no repeating values in the combined
table’s Project column. The Project column is unique, because each value occurs only once, so, the rows from the
two tables can be combined directly without any duplication.
But, let’s say you know the data will change the next time you refresh it. A refreshed version of the ProjectBudget
table now has additional rows for Blue and Red:
ProjectBudget
 APPROVED PROJECTS BUDGETALLOCATION ALLOCATIONDATE

Blue 40,000 12/1/2012

Red 100,000 12/1/2012

Green 50,000 12/1/2012

Blue 80,000 6/1/2013

Red 90,000 6/1/2013

This means the best combination of the two tables now really looks like this:

PROJECT PRIORITY BUDGETALLOCATION ALLOCATIONDATE

Blue A 40,000 12/1/2012

Red B 100,000 12/1/2012

Green C 50,000 12/1/2012

Yellow C

Purple B

Orange C

Blue A 80000 6/1/2013

Red B 90000 6/1/2013

In this new combined table, the Project column has repeating values. The two original tables won’t have a one-to-
one relationship once the table is refreshed. In this case, because we know those future updates will cause the
Project column to have duplicates, we want to set the Cardinality to be Many-to-One (*:1), with the Many on the
ProjectBudget side and the One on the CompanyProjectPriority side.

Adjusting cross filter direction for a complex set of tables and

relationships
For most relationships, the cross filter direction is set to ‘Both’. There are, however, some more uncommon
circumstances where you might need to set this different from the default, like if you’re importing a model from
an older version of Power Pivot, where every relationship is set to a single direction.
The Both setting enables Power BI Desktop to treat all aspects of connected tables as if they are a single table.
There are some situations, however, where Power BI Desktop cannot set a relationship’s cross filter direction to
‘Both’ and also keep an unambiguous set of defaults available for reporting purposes. If a relationship cross filter
direction isn't set to Both, then it’s usually because it would create ambiguity. If the default cross filter setting isn’t
working for you, try setting it to a particular table or Both.
Single direction cross filtering works for many situations. In fact, if you’ve imported a model from Power Pivot in
Excel 2013 or earlier, all of the relationships will be set to single direction. Single direction means that filtering
choices in connected tables work on the table where aggregation work is happening. Sometimes, understanding
cross filtering can be a little difficult, so let’s look at an example.

With single direction cross filtering, if you create a report that summarizes the project hours, you can then choose
to summarize (or filter) by CompanyProject, Priority or CompanyEmployee, City. If however, you want to count
the number of employees per projects (a less common question), it won’t work. You’ll get a column of values that
are all the same. In the example below, both relationships cross filtering direction is set to a single direction –
towards the ProjectHours table:

Filter specification will flow from CompanyProject to CompanyEmployee (as shown in the image below ) but, it
won’t flow up to CompanyEmployee. However, if you set the cross filtering direction to Both it will work. The Both
setting allows the filter specification to flow up to Employee.
With the cross filtering direction set to Both, our report now appears correct:

Cross filtering both directions works well for a pattern of table relationships that look like the pattern above. This
is most commonly called a star schema, like this:

Cross filtering direction does not work well with a more general pattern often found in databases, like in this
diagram:
If you have a table pattern like this, with loops, then cross filtering can create an ambiguous set of relationships.
For instance, if you sum up a field from TableX and then choose to filter by a field on TableY, then it’s not clear how
the filter should travel, through the top table or the bottom table. A common example of this kind of pattern is
with TableX as a Sales table with actuals data and for TableY to be budget data. Then, the tables in the middle are
lookup tables that both tables use, such as Division or Region.
Just like with active/inactive relationships, Power BI Desktop won’t allow a relationship to be set as Both if it will
create ambiguity in reports. There are several different ways you can deal with this and here are the two most
common:
Delete or mark relationships as inactive to reduce ambiguity. Then you might be able to set a relationship cross
filtering as Both.
Bring in a table twice (with a different name the second time) to eliminate loops. This makes the pattern of
relationships like a star schema. With a star schema, all of the relationships can be set to Both.

Wrong active relationship

When Power BI Desktop automatically creates relationships, it sometimes encounters more than one relationship
between two tables. When this happens only one of the relationships is set to be active. The active relationship
serves as the default relationship so that when you choose fields from two different tables, Power BI Desktop can
automatically create a visualization for you. However, in some cases the automatically selected relationship can be
wrong. You can use the Manage Relationships dialog to set a relationship as active or inactive, or you can set the
active relationship in the Edit relationship dialog.
To ensure there’s a default relationship, Power BI Desktop only allows a single active relationship between two
tables at a given time. So, you must first set the current relationship as inactive and then set the relationship you
want to be active.
Let’s look at an example. This first table is ProjectTickets, and the next table is EmployeeRole.
ProjectTickets

TICKET OPENEDBY SUBMITTEDBY HOURS PROJECT DATESUBMIT

1001 Perham, Tom Brewer, Alan 22 Blue 1/1/2013

1002 Roman, Daniel Brewer, Alan 26 Red 2/1/2013

1003 Roth, Daniel Ito, Shu 34 Yellow 12/4/2012

 TICKET OPENEDBY SUBMITTEDBY HOURS PROJECT DATESUBMIT

1004 Perham, Tom Brewer, Alan 13 Orange 1/2/2012

1005 Roman, Daniel Bowen, Eli 29 Purple 10/1/2013

1006 Roth, Daniel Bento, Nuno 35 Green 2/1/2013

1007 Roth, Daniel Hamilton, David 10 Yellow 10/1/2013

1008 Perham, Tom Han, Mu 28 Orange 1/2/2012

1009 Roman, Daniel Ito, Shu 22 Purple 2/1/2013

1010 Roth, Daniel Bowen, Eli 28 Green 10/1/2013

1011 Perham, Tom Bowen, Eli 9 Blue 10/15/2013

EmployeeRole

EMPLOYEE ROLE

Bento, Nuno Project Manager

Bowen, Eli Project Lead

Brewer, Alan Project Manager

Hamilton, David Project Lead

Han, Mu Project Lead

Ito, Shu Project Lead

Perham, Tom Project Sponsor

Roman, Daniel Project Sponsor

Roth, Daniel Project Sponsor

There are actually two relationships here. One is between SubmittedBy in the ProjectTickets table and Employee
in the EmployeeRole table, and the other is between OpenedBy in the ProjectTickets table and Employee in the
EmployeeRole table.
If we add both relationships to the model (OpenedBy first), then the Manage Relationships dialog will show that
OpenedBy is active:

Now, if we create a report that uses Role and Employee fields from EmployeeRole, and the Hours field from
ProjectTickets in a table visualization in the Report canvas, we’ll see only project sponsors because they’re the only
ones that opened a project ticket.

We can change the active relationship and get SubmittedBy instead of OpenedBy. In Manage Relationships, we
uncheck the ProjectTickets(OpenedBy) to EmployeeRole(Employee) relationship, and then we check the Project
Tickets(SubmittedBy) to EmployeeRole(Employee) relationship.

See all of your relationships in Relationship View

Sometimes your model has multiple tables and complex relationships between them. Relationship View in Power
BI Desktop shows all of the relationships in your model, their direction, and cardinality in an easy to understand
and customizable diagram. To learn more, see Relationship View in Power BI Desktop.
 Data View in Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

Data View helps you inspect, explore, and understand data in your Power BI Desktop model. It's different from
how you view tables, columns, and data in Query Editor. With Data View, you’re looking at your data after it has
been loaded into the model.
When you’re modeling your data, sometimes you want to see what’s actually in a table or column without creating
a visual on the report canvas, often right down to the row level. This is especially useful when you’re creating
measures and calculated columns, or you need to identify a data type or data category.
Let’s take a closer look at some of the elements found in Data View.

1. Data View icon – Select this icon to enter Data View.

2. Data Grid – This shows the selected table and all columns and rows in it. Columns hidden from Report
View are greyed out. You can right-click on a column for options.
3. Modeling ribbon – Here you can manage relationships, create calculations, change data type, format, data
category for a column.
4. Formula bar – Enter DAX formulas for Measures and Calculated columns.
5. Search – Search for a table or column in your model.
6. Fields list – Select a table or column to view in the data grid.

Filtering in Data View

You can also filter and sort data in Data View. Each column shows an icon that identifies the sort direction (if
applied).

You can filter individual values, or use advanced filtering based on the data in the column.

NOTE
When a Power BI model is created in a different culture than your current user interface (for example, the model was created
in US English and you are viewing it in Spanish), the search box will not appear in the Data View user interface for anything
other than text fields.
 Query overview in Power BI Desktop
1/14/2019 • 6 minutes to read • Edit Online

With Power BI Desktop you can connect to the world of data, create compelling and foundational reports, and
share your efforts with others – who can then build on your work, and expand their business intelligence
efforts.
Power BI Desktop has three views:
Report view – where you use queries you create to build compelling visualizations, arranged as you want
them to appear, and with multiple pages, that you can share with others
Data view – see the data in your report in data model format, where you can add measures, create new
columns, and manage relationships
Relationships view – get a graphical representation of the relationships that have been established in your
data model, and manage or modify them as needed.
These views are accessed by selecting one of the three icons along the left side of Power BI Desktop. In the
following image, Report view is selected, indicated by the yellow band beside the icon.

Power BI Desktop also comes with Query Editor, where you can connect to one or many data sources, shape
and transform the data to meet your needs, then load that model into Power BI Desktop.
This document provides an overview of the work with data in the Query Editor. There's more to learn, of
course, so at the end of this document you’ll find links to detailed guidance about supported data types,
connecting to data, shaping data, creating relationships, and how to get started.
But first, let’s see get acquainted with Query Editor.

The Query Editor

To get to Query Editor, select Edit Queries from the Home tab of Power BI Desktop.
With no data connections, Query Editor appears as a blank pane, ready for data.

Once a query is loaded, Query Editor view becomes more interesting. If we connect to the following Web data
source, Query Editor loads information about the data, which you can then begin to shape.
http://www.bankrate.com/finance/retirement/best-places-retire-how -state-ranks.aspx
Here’s how Query Editor appears once a data connection is established:
1. In the ribbon, many buttons are now active to interact with the data in the query
2. In the left pane, queries are listed and available for selection, viewing, and shaping
3. In the center pane, data from the selected query is displayed and available for shaping
4. The Query Settings window appears, listing the query’s properties and applied steps
We’ll look at each of these four areas – the ribbon, the queries pane, the data view, and the Query Settings pane
– in the following sections.

The query ribbon

The ribbon in Query Editor consists of four tabs – Home, Transform, Add Column, and View.
The Home tab contains the common query tasks, including the first step in any query, which is Get Data. The
following image shows the Home ribbon.

To connect to data and begin the query building process, select the Get Data button. A menu appears,
providing the most common data sources.
For more information about available data sources, see Data Sources. For information about connecting to
data, including examples and steps, see Connect to Data.
The Transform tab provides access to common data transformation tasks, such as adding or removing
columns, changing data types, splitting columns, and other data-driven tasks. The following image shows the
Transform tab.

For more information about transforming data, including examples, see Combine and Shape Data.
The Add Column tab provides additional tasks associated with adding a column, formatting column data, and
adding custom columns. The following image shows the Add Column tab.

The View tab on the ribbon is used to toggle whether certain panes or windows are displayed. It’s also used to
display the Advanced Editor. The following image shows the View tab.

It’s useful to know that many of the tasks available from the ribbon are also available by right-clicking a column,
or other data, in the center pane.

The left pane

The left pane displays the number of active queries, as well as the name of the query. When you select a query
from the left pane, its data is displayed in the center pane, where you can shape and transform the data to meet
your needs. The following image shows the left pane with multiple queries.

The center (data) pane

In the center pane, or Data pane, data from the selected query is displayed. This is where much of the work of
the Query view is accomplished.
In the following image, the Web data connection established earlier is displayed, the Overall score column is
selected, and its header is right-clicked to show the available menu items. Notice that many of these right-click
menu items are the same as buttons in the ribbon tabs.
When you select a right-click menu item (or a ribbon button), Query applies the step to the data, and saves it as
part of the query itself. The steps are recorded in the Query Settings pane in sequential order, as described in
the next section.

The query settings pane

The Query Settings pane is where all steps associated with a query are displayed. For example, in the
following image, the Applied Steps section of the Query Settings pane reflects the fact that we just changed
the type of the Overall score column.
As additional shaping steps are applied to the query, they are captured in the Applied Steps section.
It’s important to know that the underlying data is not changed; rather, Query Editor adjusts and shapes its view
of the data, and any interaction with the underlying data occurs based on Query Editor’s shaped and modified
view of that data.
In the Query Settings pane, you can rename steps, delete steps, or reorder the steps as you see fit. To do so,
right-click the step in the Applied Steps section, and choose from the menu that appears. All query steps are
carried out in the order they appear in the Applied Steps pane.
The Advanced Editor
If you want to see the code that Query Editor is creating with each step, or want to create your own shaping
code, you can use the Advanced Editor. To launch the advanced editor, select View from the ribbon, then
select Advanced Editor. A window appears, showing the existing query code.

You can directly edit the code in the Advanced Editor window. To close the window, select the Done or Cancel
button.

Saving your work

When your query is where you want it, you can have Query Editor apply the changes to the data model into
Power BI Desktop, and close Query Editor. To do that, select Close & Apply from Query Editor's File menu.
As progress is made, Power BI Desktop provides a dialog to display its status.

Once you have your query where you want it, or if you just want to make sure your work is saved, Power BI
Desktop can save your work in the form of a .pbix file.
To save your work, select File > Save (or File > Save As), as shown in the following image.
Next steps
There are all sorts of things you can do with Power BI Desktop. For more information on its capabilities, check
out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Connect to Data in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Common Query Tasks in Power BI Desktop
 DAX basics in Power BI Desktop
1/14/2019 • 14 minutes to read • Edit Online

This article is for users new to Power BI Desktop. It’s meant to give you a quick and easy introduction on how you
can use Data Analysis Expressions (DAX) to solve a number of basic calculation and data analysis problems. We’ll
go over some conceptual information, a series of tasks you can complete, and a few quizzes to test what you’ve
learned. After completing this article, you should have a good understanding of the most important fundamental
concepts in DAX.

What is DAX?
DAX is a collection of functions, operators, and constants that can be used in a formula, or expression, to calculate
and return one or more values. Stated more simply, DAX helps you create new information from data already in
your model.

Why is DAX so important?

It’s quite easy to create a new Power BI Desktop file and import some data into it. You can even create reports
that show valuable insights without using any DAX formulas at all. But, what if you need to analyze growth
percentage across product categories and for different date ranges? Or, you need to calculate year-over-year
growth compared to market trends? DAX formulas provide this capability and many other important capabilities
as well. Learning how to create effective DAX formulas will help you get the most out of your data. When you get
the information you need, you can begin to solve real business problems that affect your bottom line. This is the
power in Power BI, and DAX will help you get there.

Prerequisites
You might already be familiar with creating formulas in Microsoft Excel. That knowledge will be helpful in
understanding DAX, but even if you have no experience with Excel formulas, the concepts described here will help
you get started creating DAX formulas and solving real-world BI problems right away.
We’re going to focus on understanding DAX formulas used in calculations, more specifically, in measures and
calculated columns. You should already be familiar with Power BI Desktop, importing data, adding fields to a
report, and you should also be familiar with fundamental concepts of Measures and Calculated columns.
Example Workbook
The best way to learn DAX is to create some basic formulas, use it with some actual data, and see the results for
yourself. The examples and tasks here use the Contoso Sales Sample for Power BI Desktop Preview file. This is
the same sample file used in the Tutorial: Create your own measures in Power BI Desktop article. Here is the
sample file to download.

Let's begin!
We will frame our understanding of DAX around three fundamental concepts: Syntax, Functions, and Context. Of
course, there are other important concepts in DAX, but understanding these three concepts will provide the best
foundation on which to build your DAX skills.
Syntax
Before you create your own formulas, let’s take a look at DAX formula syntax. Syntax includes the various
elements that make up a formula, or more simply, how the formula is written. For example, let’s look at a simple
DAX formula for a measure.

This formula includes the following syntax elements:

A. The measure name Total Sales.
B. The equals sign operator (=) indicates the beginning of the formula. When calculated, it will return a result.
C. The DAX function SUM adds up all of the numbers in the Sales[SalesAmount] column. You’ll learn more
about functions later.
D. Parenthesis () surround an expression containing one or more arguments. All functions require at least one
argument. An argument passes a value to a function.
E. The referenced table Sales.
F. The referenced column [SalesAmount] in the Sales table. With this argument, the SUM function knows on
which column to aggregate a SUM.
When trying to understand a DAX formula, it is often helpful to break down each of the elements into a language
you think and speak every day. For example, you can read this formula as:

For the measure named Total Sales, calculate (=) the SUM of values in the [SalesAmount ] column in the
Sales table.

When added to a report, this measure calculates and returns values by summing up sales amounts for each of the
other fields we include, for example, Cell Phones in the USA.
You might be thinking ‘Isn’t this measure doing the same thing as if I were to just add the SalesAmount field to
my report?’ Well, yes. But, there’s a good reason to create our own measure that sums up values from the
SalesAmount field: We can use it as an argument in other formulas. This may seem a little confusing now, but as
your DAX formula skills grow, knowing this will make your formulas and your model more efficient. In fact, you’ll
see the Total Sales measure showing up as an argument in other formulas later on.
Let’s go over a few more things about this formula. In particular, we introduced a function, SUM. Functions are
pre-written formulas that make it easier to do complex calculations and manipulations with numbers, dates, time,
text, and more. You will learn more about functions later.
You also see the column [SalesAmount] was preceded by the table Sales in which the column belongs. This is
known as a fully qualified column name in that it includes the column name preceded by the table name.
Columns referenced in the same table do not require the table name be included in the formula. This can make
long formulas that reference many columns shorter and easier to read. However, it's good practice to include the
table name in your measure formulas, even when in the same table.

NOTE
If a table name contains spaces, reserved keywords, or disallowed characters, you’ll need to enclose the table name in single
quotation marks. You’ll also need to enclose table names in quotation marks if the name contains any characters outside
the ANSI alphanumeric character range, regardless of whether your locale supports the character set or not.
It’s important your formulas have the correct syntax. In most cases, if the syntax is not correct, a syntax error will
be returned. In other cases, the syntax may be correct, but the values returned might not be what you are
expecting. The DAX editor in Power BI Desktop includes a suggestions feature, used to create syntactically correct
formulas by helping you select the correct elements.
Let’s create a simple formula. This task will help you further understand formula syntax and how the suggestions
feature in the formula bar can help you.
Task: Create a measure formula
To complete this task, you’ll need to open the Contoso Sales Sample Power BI Desktop file.
1. In Report view, in the field list, right-click on the Sales table, and then click New Measure.
2. In the formula bar, replace Measure by typing a new measure name, Previous Quarter Sales.
3. After the equals sign, type the first few letters CAL, and then double-click the function you want to use. In
this formula, you want to use the CALCULATE function.
You’ll use the CALCULATE function to filter the amounts we want to sum by an argument we pass to the
CALCULATE function. This is what’s referred to as nesting functions. The CALCULATE function has at least
two arguments. The first is the expression to be evaluated, and the second is a filter.
4. After the opening parenthesis ( for the CALCULATE function, type SUM followed by another opening
parenthesis (. Now we need to pass an argument to the SUM function.
5. Begin typing Sal, and then select Sales[SalesAmount], followed by a closing parenthesis ). This is the
first expression argument for our CALCULATE function.
6. Type a comma (,) followed by a space to specify the first filter, and then type PREVIOUSQUARTER. This
will be our filter.
You’ll use the PREVIOUSQUARTER time intelligence function to filter SUM results by the previous
quarter.
7. After the opening parenthesis ( for the PREVIOUSQUARTER function, type Calendar[DateKey].
The PREVIOUSQUARTER function has one argument, a column containing a contiguous range of dates.
In our case, that's the DateKey column in the Calendar table.
8. Make sure both the arguments being passed to the PREVIOUSQUARTER function and the CALCULATE
function are closed by typing two closing parenthesis )).
Your formula should now look like this:
Previous Quarter Sales = CALCULATE (SUM (Sales[SalesAmount]),
PREVIOUSQUARTER(Calendar[DateKey]))
9. Click the checkmark in the formula bar or press Enter to validate the formula and add it to the model.
You did it! You just created a measure using DAX, and not an easy one at that. What this formula will do is
calculate the total sales for the previous quarter, depending on the filters applied in a report. For example, if we
put SalesAmount and our new Previous Quarter Sales measure in a chart, and then added Year and
QuarterOfYear as Slicers, we’d get something like this:
You were just introduced to several important aspects of DAX formulas. First, this formula included two functions.
Notice PREVIOUSQUARTER, a time intelligence function, is nested as an argument passed to CALCULATE, a
filter function. DAX formulas can contain up to 64 nested functions. It’s unlikely a formula would ever contain so
many nested functions. In fact, such a formula would be very difficult to create and debug, and it probably
wouldn’t be very fast either.
In this formula, you also used filters. Filters narrow down what will be calculated. In this case, you selected one
filter as an argument, which is actually the result of another function. You will learn more about filters later.
Finally, you used the CALCULATE function. This is one of the most powerful functions in DAX. As you author
models and create more complex formulas, you will likely use this function many times. Discussing the
CALCULATE function is outside the scope of this article, but as your knowledge of DAX grows, pay special
attention to this one.
Syntax QuickQuiz
1. What does this button on the formula bar do?

2. What always surrounds a column name in a DAX formula?

Answers are provided at the end of this article.
Functions
Functions are predefined formulas that perform calculations by using specific values, called arguments, in a
particular order or structure. Arguments can be other functions, another formula, expression, column references,
numbers, text, logical values such as TRUE or FALSE, or constants.
DAX includes the following categories of functions: Date and Time, Time Intelligence, Information, Logical,
Mathematical, Statistical, Text, Parent/Child, and Other functions. If you’re familiar with functions in Excel
formulas, many of the functions in DAX will appear similar to you; however, DAX functions are unique in the
following ways:
A DAX function always references a complete column or a table. If you want to use only particular values
from a table or column, you can add filters to the formula.
If you need to customize calculations on a row -by-row basis, DAX provides functions that let you use the
current row value or a related value as a kind of argument, to perform calculations that vary by context.
You will learn more about context later.
DAX includes many functions that return a table rather than a value. The table is not displayed, but is used
to provide input to other functions. For example, you can retrieve a table and then count the distinct values
 in it, or calculate dynamic sums across filtered tables or columns.
DAX includes a variety of time intelligence functions. These functions let you define or select date ranges,
and perform dynamic calculations based on them. For example, you can compare sums across parallel
periods.
Excel has a very popular function, VLOOKUP. DAX functions don’t take a cell or cell range as a reference
like VLOOKUP does in Excel. DAX functions take a column or a table as a reference. Keep in mind, in
Power BI Desktop, you’re working with a relational data model. Looking up values in another table is really
quite easy, and in most cases you don’t need to create any formula at all.
As you can see, functions in DAX can help you create very powerful formulas. We really only touched on
the basics of functions. As your DAX skills grow, you'll create formulas using many different functions. One
of the best places to learn details about each of the DAX functions is in the DAX Function Reference.
Functions QuickQuiz
1. What does a function always reference?
2. Can a formula contain more than one function?
3. What category of functions would you use to concatenate two text strings into one string?
Answers are provided at the end of this article.
Context
Context is one of the most important DAX concepts to understand. There are two types of context in DAX; row
context and filter context. We’ll first look at row context.
Row context
Row context is most easily thought of as the current row. It applies whenever a formula has a function that applies
filters to identify a single row in a table. The function will inherently apply a row context for each row of the table
over which it is filtering. This type of row context most often applies to measures.
Filter context
Filter context is a little more difficult to understand than row context. You can most easily think of filter context as:
One or more filters applied in a calculation that determines a result or value.
Filter context doesn’t exist in-place of row context; rather, it applies in addition to row context. For example, to
further narrow down the values to include in a calculation, you can apply a filter context, which not only specifies
the row context, but also specifies only a particular value (filter) in that row context.
Filter context is easily seen in your reports. For example, when you add TotalCost to a visualization, and then add
Year and Region, you are defining a filter context that selects a subset of data based on a given year and region.
Why is filter context so important to DAX? Because while filter context can most easily be applied by adding fields
to a visualization, filter context can also be applied in a DAX formula by defining a filter using functions such as
ALL, RELATED, FILTER, CALCULATE, by relationships, and by other measures and columns. For example, let’s
look at the following formula in a measure named Store Sales:

To better understand this formula, we can break it down, much like with other formulas.
This formula includes the following syntax elements:
A. The measure name Store Sales.
B. The equals sign operator (=) indicates the beginning of the formula.
C. The CALCULATE function evaluates an expression, as an argument, in a context that is modified by the
specified filters.
D. Parenthesis () surround an expression containing one or more arguments.
E. A measure [Total Sales] in the same table as an expression. The Total Sales measure has the formula:
=SUM (Sales[SalesAmount]).
F. A comma (,) separates the first expression argument from the filter argument.
G. The fully qualified referenced column, Channel[ChannelName]. This is our row context. Each row in this
column specifies a channel: Store, Online, etc.
H. The particular value, Store as a filter. This is our filter context.
This formula ensures only sales values defined by the Total Sales measure are calculated only for rows in the
Channel[ChannelName] column with the value “Store”, as a filter.
As you can imagine, being able to define filter context within a formula has immense and powerful capabilities.
Being able to reference only a particular value in a related table is just one such example. Don’t worry if you do
not completely understand context right away. As you create your own formulas, you will better understand
context and why it’s so important in DAX.
Context QuickQuiz
1. What are the two types of context?
2. What is filter context?
3. What is row context?
Answers are provided at the end of this article.

Summary
Now that you have a basic understanding of the most important concepts in DAX, you can begin creating DAX
formulas for measures on your own. DAX can indeed be a little tricky to learn, but there are many resources
available to you. After reading through this article and experimenting with a few of your own formulas, you can
learn more about other DAX concepts and formulas that can help you solve your own business problems. There
are many DAX resources available to you; most important is the Data Analysis Expressions (DAX) Reference.
DAX has been around for several years in other Microsoft BI tools such as Power Pivot and Analysis Services
Tabular models, so there’s a lot of great information out there. You can find more information in books,
whitepapers, and blogs from both Microsoft and leading BI professionals. The DAX Resource Center Wiki on
TechNet is also a great place to start.
QuickQuiz answers
Syntax:
1. Validates and enters the measure into the model.
2. Brackets [].
Functions:
1. A table and a column.
2. Yes. A formula can contain up to 64 nested functions.
3. Text functions.
Context:
1. Row context and filter context.
2. One or more filters in a calculation that determines a single value.
3. The current row.
 Relationship View in Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

Relationship View shows all of the tables, columns, and relationships in your model. This can be especially
helpful when your model has complex relationships between many tables.
Let’s take a look.

A. Relationship View icon – Click to show your model in Relationship View

B. Relationship – You can hover your cursor over a relationship to show the columns used. Double-click on a
relationship to open it in the Edit Relationship dialog box.
In the figure above, you can see the Stores table has a StoreKey column that’s related to the Sales table, which also
has a StoreKey column. We see it’s a Many to One (*:1) relationship, and the icon in the middle of the line shows
the Cross filter direction set to Both. The arrow on the icon shows the direction of the filter context flow.
To learn more about relationships, see Create and manage relationships in Power BI Desktop.
 Report View in Power BI Desktop
1/14/2019 • 4 minutes to read • Edit Online

If you’ve been working with Power BI, you know how easy it is to create reports providing dynamic perspectives
and insights into your data. Power BI also has more advanced features in Power BI Desktop. With Power BI
Desktop, you can create advanced queries, mashup data from multiple sources, create relationships between
tables, and more.
Power BI Desktop includes Report View, where you can create any number of report pages with visualizations.
Report View in provides pretty much the same design experience as a report’s Editing View in the Power BI
service. You can move visualizations around, copy and paste, merge, and so on.
The difference between them is when using Power BI Desktop, you can work with your queries and model your
data to make sure your data supports the best insights in your reports. You can then save your Power BI Desktop
file wherever you like, whether it's your local drive or to the cloud.

Let's take a look!

When you first load data in Power BI Desktop, you’ll see Report View with a blank canvas.

You can switch between Report View, Data View, and Relationship View by selecting the icons in the left-hand
navigation bar:

Once you’ve added some data, you can add fields to a new visualization in the canvas.
To change the type of visualization, you can select it from the Visualization group in the ribbon or you can right-
click and select a different type from the Change visualization type icon.

TIP
Be sure to experiment with different visualization types. It’s important your visualization convey information in your data
clearly.

A report will have at least one blank page to start. Pages appear in the navigator pane just to the left of the canvas.
You can add all sorts of visualizations to a page, but it's important not to overdo it. Too many visualizations on a
page will make it look busy and difficult to find the right information. You can add new pages to your report. Just
click New Page on the ribbon.
To delete a page, click the X on the page's tab at the bottom of the Report View.

NOTE
Reports and visualizations can’t be pinned to a dashboard from Power BI Desktop. To do that, you’ll need to Publish from
Power BI Desktop to your Power BI site.

Copy and paste between reports

You can easily take a visual from one Power BI Desktop report, and paste it into another report. Simply use the
CTRL+C keyboard shortcut to copy your report visual, then in the other Power BI Desktop report, use CTRL+V
to paste the visual into the other report. You can select one visual at a time, or you can select all visuals on a page
to copy, then paste into the destination Power BI Desktop report.
The ability to copy and paste visuals is useful for people who build and updates multiple reports frequently. When
copying between files, settings and formatting that have been explicitly set in the formatting pane will carry
forward, while visual elements relying on a theme or the default settings automatically update to match the theme
of the destination report. So when you get a visual formatted and looking just the way you want, you can copy and
paste that visual into new reports and preserve all that good formatting work.

If the fields in your model are different, you’ll see an error on the visual and a warning about which fields don’t
exist. The error is similar to the experience you see when you delete a field in the model that a visual is using. To
correct the error, just replace the broken fields with the fields you want to use from the model in the report to
which you pasted the visual. If you're using a custom visual, you must also import that custom visual to the
destination report.
Hide report pages
When you create a report, you can also hide pages from a report. This might be useful if you need to create
underlying data or visuals in a report, but you don't want those pages to be visible to others, such as when you
create tables or supporting visuals that are used in other report pages. There are many other creative reasons you
might want to create a report page, then hide it from a report you want to publish.
Hiding a report page is easy. Simply right-click on the report page tab, and select Hide from the menu that
appears.

There are a few considerations to keep in mind when hiding a report page:
You can still see a hidden report view when in Power BI Desktop, even though the page's title is grayed
out. In the following image, Page 4 is hidden.

You cannot see a hidden report page when viewing the report in the Power BI service.
Hiding a report page is not a security measure. The page can still be accessed by users, and its content is
still accessible using drill-through, and other methods.
When a page is hidden, when in View Mode, no view -mode navigation arrows are shown.
 Connect to data in Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

With Power BI Desktop, you can easily connect to the ever expanding world of data. If you don’t have Power BI
Desktop, you can download and install it.
There are all sorts of data sources available in Power BI Desktop. The following image shows how to connect to
data, by selecting the File ribbon, then Get Data > More.

Example of connecting to data

For this example, we'll connect to a Web data source.
Imagine you’re retiring – you want to live where there’s lots of sunshine, preferable taxes, and good health care.
Or… perhaps you’re a data analyst, and you want that information to help your customers – as in, help your
raincoat manufacturing client target sales where it rains a lot.
Either way, you find a Web resource that has interesting data about those topics, and more:
http://www.bankrate.com/finance/retirement/best-places-retire-how -state-ranks.aspx
You select Get Data > Web and type the address.
When you select OK, the Query functionality of Power BI Desktop goes to work. Power BI Desktop contacts the
Web resource, and the Navigator window returns the results of what it found on that Web page. In this case, it
found a table (Table 0) and the overall Document. We’re interested in the table, so we select it from the list. The
Navigator window displays a preview.

At this point we can edit the query before loading the table, by selecting Edit from the bottom of the window, or
we can load the table.
If we select Edit, the table is loaded and Query Editor is launched. The Query Settings pane is displayed (if it’s
not, you can select View from the ribbon, then Show > Query Settings to display the Query Settings pane).
Here’s what that looks like.
All those scores are text rather than numbers, and we need them to be numbers. No problem – just right-click
the column header, and select Change Type > Whole Number to change them. To choose more than one
column, first select a column then hold down SHIFT, select additional adjacent columns, and then right-click a
column header to change all selected columns. Use CTRL to choose columns that are not adjacent.
In Query Settings, the Applied Steps will reflect any changes that were made. As you make additional
changes to the data, Query Editor will record those changes in the Applied Steps section, which you can adjust,
revisit, rearrange, or delete as necessary.

Additional changes to the table can still be made after it’s loaded, but for now this will do. When we're done we
select Close & Apply from the Home ribbon, and Power BI Desktop applies our changes and closes Query
Editor.

With the data model loaded, in Report view in Power BI Desktop, we can begin creating visualizations by
dragging fields onto the canvas.
Of course, this is a simple model with a single data connection; most Power BI Desktop reports will have
connections to different data sources, shaped to meet your needs, with relationships that produce a rich data
model.

Next steps
There are all sorts of things you can do with Power BI Desktop. For more information on its capabilities, check
out the following resources:
What is Power BI Desktop?
Query Overview with Power BI Desktop
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Common Query Tasks in Power BI Desktop
Want to give us feedback? Great – use the Submit an Idea menu item in Power BI Desktop or visit Community
Feedback. We look forward to hearing from you!
 Publish from Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

When you publish a Power BI Desktop file to the Power BI service, the data in the model and any reports you
created in Report view are published to your Power BI workspace. You’ll see a new dataset with the same name,
and any reports in your Workspace navigator.
Publishing from Power BI Desktop has the same effect as using Get Data in Power BI to connect to and upload
a Power BI Desktop file.

NOTE
Any changes you make to the report in Power BI, for example, add, delete, or change visualizations in reports, will not be
saved back to the original Power BI Desktop file.

To publish a Power BI Desktop dataset and reports

1. In Power BI Desktop > File > Publish > Publish to Power BI or click Publish on the ribbon.

2. Sign in to Power BI.

3. Select the destination.

When complete, you receive a link to your report. Click the link to open the report in your Power BI site.
Re-publish or replace a dataset published from Power BI Desktop
When you publish a Power BI Desktop file, the dataset and any reports you created in Power BI Desktop are
uploaded to your Power BI site. When you re-publish your Power BI Desktop file, the dataset in your Power BI
site will be replaced with the updated dataset from the Power BI Desktop file.
This is all pretty straightforward, but there are a few things you should know:
If you already have two or more datasets in Power BI with the same name as the Power BI Desktop file,
publish could fail. Make sure you have only one dataset in Power BI with the same name. You can also rename
the file and publish, creating a new dataset with same name as the file.
If you rename or delete a column or measure, any visualizations you already have in Power BI with that field
could be broken.
Power BI ignores some format changes of existing columns. For example, if you change a column’s format
from 0.25 to 25%.
If you have a refresh schedule configured for your existing dataset in Power BI and you add new data sources
to your file and then re-publish, you’ll have to sign into them in Manage Data Sources prior to the next
scheduled refresh.
 Part I, Add visualizations to a Power BI report
1/14/2019 • 2 minutes to read • Edit Online

This article gives a quick introduction to creating a visualization in a report using either Power BI service or Power
BI Desktop. For more-advanced content, please see Part II. Watch Amanda demonstrate a few different ways to
create, edit, and format visuals on the report canvas. Then try it out yourself using the Sales and Marketing sample
to create your own report.
https://www.youtube.com/embed/IkJda4O7oGs

Open a report and add a new page

1. Open a report in Editing View. This tutorial uses the Sales and Marketing sample.
2. If the Fields pane isn't visible, select the arrow icon to open it.

3. Add a blank page to the report.

Add visualizations to the report

1. Create a visualization by selecting a field from the Fields pane.
Start with a numeric field like SalesFact > Sales $. Power BI creates a column chart with a single column.

Or, start with a category field, such as Name or Product: Power BI creates a Table and adds that field to
the Values well.
 Or, start with a geography field, such as Geo > City. Power BI and Bing Maps create a map visualization.

2. Create a visualization and then change its type. Select Product > Category and then Product > Count of
Product to add them both to the Values well.

3. Change the visualization to a column chart by selecting the column chart icon.

4. When you create visualizations in your report, you can pin them to your dashboard. To pin the visualization,
select the pin icon .
Next steps
Continue on to Part 2: Add visualizations to a Power BI report
Interact with the visualizations in the report.
Do even more with visualizations.
Save your report.
 Part 2, Add visualizations to a Power BI report
1/14/2019 • 2 minutes to read • Edit Online

In Part 1, you created a basic visualization by selecting checkboxes next to field names. In Part 2 you'll learn how to
use drag-and-drop and make full use of the Fields and Visualizations panes to create and modify visualizations.
Prerequisites
Part 1
Power BI Desktop - visualizations can be added to reports using Power BI service or Power BI Desktop. This
tutorial uses Power BI Desktop.
Retail Analysis sample

Create a new visualization

In this tutorial we'll dig into our Retail Analysis dataset and create a few key visualizations.
Open a report and add a new blank page.
1. Open the Retail Analysis sample .PBIX file in Power BI Desktop.

2. Add a new page by selecting the yellow plus icon at the bottom of the canvas.
Add a visualization that looks at this year's sales compared to last year.
1. From the Sales table, select This Year Sales > Value and Last Year Sales. Power BI creates a column
chart. This is somewhat interesting, and you want to dig deeper. What do the sales look like by month?
2. From the Time table, drag FiscalMonth into the Axis area.

3. Change the visualization to an Area chart. There are many visualization types to choose from - see
descriptions of each, tips for best practices, and tutorials for help deciding which type to use. From the
Visualizations pane, select the Area chart icon .
4. Sort the visualization by selecting the ellipses and choosing Sort by FiscalMonth.
5. Resize the visualization by selecting the visualization, grabbing one of the outline circles and dragging.
Make it wide enough to eliminate the scrollbar and small enough to give us enough room to add another
visualization.

6. Save the report.

Add a map visualization that looks at sales by location
1. From the Store table, select Territory. Power BI recognizes that Territory is a location, and creates a map
visualization.
2. Drag Total Stores into the Size area.

3. Add a legend. To see the data by store name, drag Chain into the Legend area.

Next steps
More about Visualizations in Power BI reports.
More questions? Try the Power BI Community
 Customize visualization titles, legends, and
backgrounds
1/14/2019 • 3 minutes to read • Edit Online

In this tutorial you'll learn a few different ways to customize your visualizations. There are so many options for
customizing your visualizations, the best way to learn about them all is by exploring the Formatting pane (select
the paintroller icon). To get you started, this article shows you how to customize a visualization title, legend, and
background.
Not all visualizations can be customized, see the complete list.
Watch Amanda customize visualizations in her report (fast-forward to 4:50 in the video). Then follow the
instructions below the video to try it out yourself with your own data.
https://www.youtube.com/embed/IkJda4O7oGs
Prerequisites
Power BI service or Power BI Desktop
Retail Analysis sample

Customize visualization titles in reports

To follow along, sign into Power BI service (app.powerbi.com) and open the Retail Analysis Sample report in
Editing View.

NOTE
When you pin a visualization to a dashboard, it becomes a dashboard tile. The tiles themselves can also be customized with
new titles and subtitles, hyperlinks, and resized.

1. Navigate to the "New Stores" page of the report and select the "Open Store Count by Open Month..."
column chart.
2. In the Visualizations pane, select the paintroller icon to reveal the formatting options. and select Title to
expand that section.
3. Turn Title on and off by selecting the On (or Off) slider. For now, leave it On.

4. Change Title Text by typing Store count by month opened in the text field.
5. Change Font color to orange and Background Color to yellow.
Select the dropdown and choose a color from the Theme Colors, Recent Colors, or Custom color.
Select the dropdown to close the color window.

You can always revert to the default colors by selecting Revert to default in the color window.
6. Increase the text size to 12.
7. The last customization we'll make to the chart title is to align it in the center of the visualization. The title
position defaults to left-aligned.

At this point in the tutorial, your column chart title should look like something like this:
 To revert all the title customization we've done so far, select Revert To Default, at the bottom of the Title
customization pane.

Customize visualization backgrounds

With the same column chart selected, expand the Background options.
1. Turn the background on and off by selecting the On (or Off) slider. For now, leave it On.
2. Change the background color to 74% grey.
Select the dropdown and choose a grey color from the Theme Colors, Recent Colors, or Custom
color.
Change Transparency to 74%.

To revert all the title background customization we've done so far, select Revert To Default, at the bottom
of the Background customization pane.

Customize visualization legends

1. Open the Overview report page and select the "Total Sales Variance by FiscalMonth and District Manager"
chart.
2. In the Visualization tab, select the paintbrush icon to open the formatting pane.
3. Expand Legend options.
4. Turn the legend on and off by selecting the On (or Off) slider. For now, leave it On.
5. Move the legend to the left side of the visualization.
6. Add a legend title by toggling Title to On and, in the Legend name field, typing Managers.

To revert all the legend customization we've done so far, select Revert To Default, at the bottom of the
Legend customization pane.

Visualization types that can be customized

VISUALIZATION TITLE BACKGROUND LEGEND

area yes yes yes

bar yes yes yes

card yes yes n/a

multi row card yes yes n/a

column yes yes yes

combo yes yes yes

donut yes yes yes

filled map yes yes yes

 VISUALIZATION TITLE BACKGROUND LEGEND

funnel yes yes n/a

gauge yes yes n/a

kpi yes yes n/a

line yes yes yes

map yes yes yes

matrix yes yes n/a

pie yes yes yes

scatter yes yes yes

slicer yes yes n/a

table yes yes n/a

textbox no yes n/a

treemap yes yes yes

waterfall yes yes yes

Next steps
Customize X-axis and Y -axis
Customize colors and axis properties
Power BI - Basic Concepts
More questions? Try the Power BI Community
 Show items with no data in Power BI
1/14/2019 • 5 minutes to read • Edit Online

Power BI lets you visualize all sorts of data from various sources. When creating a visual, Power BI only shows
relevant data when creating a visual to properly manage how data is presented and displayed. Power BI
determines which data is relevant based on the configuration of the visual, and the underlying data model. This
article describes how Power BI behaves when determining relevant data, with examples that illustrate how
determinations are made.

Determining relevant data

To get started understanding how Power BI determines which data is relevant to display, let's consider a table as a
simple example. Using the model represented in the samples section, found at the end of this article, consider
building a table with the following settings:
1. Groups from the same table: Product[Color ] - Product[Size]

PRODUCT[COLOR] PRODUCT[SIZE]

Blue Large
 PRODUCT[COLOR] PRODUCT[SIZE]

Blue Medium

Blue Small

Red Large

In this example, Power BI displays the combinations of [Color-Size] that exist in the table [Product].
Now let's look at a different combination:
2. Groups from different but directly related tables and a measure: ProductStyle[Finish] - Product[Color ] -
Sum (Sales[Quantity ])

PRODUCTSTYLE[FINISH] PRODUCT[COLOR] [SUMQUANTITY]

Gloss Blue 10

Matte Blue 15

In this example, Power BI displays only combinations that exist. For example, it will not display ("None" + "Blue")
or ("Matte" + "Red") because those combinations do not exist in the model. The condition that determines which
combinations exist is the value for Sum (Sales[Quantity ]) not being blank.
Let's look at a different case:
3. Groups from different but related tables and no measure: ProductStyle[Finish] - Product[Color ]

PRODUCTSTYLE[FINISH] PRODUCT[COLOR]

Gloss Blue

Gloss Red

Matte Blue

Since there is no explicit measure and the two tables are directly related, Power BI attempts to inject a measure to
constrain the combinations that result. In this case, Power BI injects a CALCULATE (COUNTROWS ('Product' ))
measure, which should not be blank, since Product is the table that is common to both tables.
As such, Power BI displays the combinations that do have entries in the Product table, which excludes the
combinations of ("None" + "Blue") and ("Matte" + "Red").
4. Groups from different and unrelated tables
The sample model doesn't have this combination, but if there were groups from different and unrelated tables,
Power BI would not be able to relate two columns. The result would be a crossjoin of all the values of each column.
In that situation, Power BI issues an error of type unconstrained join, because such cross joins are expensive to
compute in the database, and do not provide very much information to a user.
Showing items with no data
The previous section described how Power BI determines which data is relevant to display. But there may be times
when you want to show items with no data.
The Show items with no data feature enables you to do exactly that - include data rows and columns that don't
contain measure data (blank measure values).
To enable the Show items with no data feature select a visual, then in the Fields well, right-click the field and
select Show items with no data from the menu that appears, as shown in the following image:
The Show items with no data feature does not have effect in the following circumstances:
There's no measure added to the visual, and the grouping columns come from the same table
Groups are unrelated; Power BI doesn't run queries for visuals that have unrelated groups
The measure is unrelated to any of the groups; this is because the measure will never be blank for only some
group combinations
There's a user-defined measure filter that excludes blank measures - for example: SalesAmount > 0
How Show items with no data works
The most interesting use cases of Show items with no data are when measures are present. Let's look at the
situation when the groups are from the same table, or can be related through a path in the model. For example,
ProductStyle is directly related to Product and indirectly related to Sales, ProductStyle and ProductCategory can be
related through the Product table, and so on.
Let's look at a couple interesting cases, and compare when Show items with no data is off and then on.
1. Grouping columns from the same table: Product[Color ] - Product[Size] - Sum (Sales[Quantity ])
How it appears with Show items with no data feature off:

PRODUCT[COLOR] PRODUCT[SIZE] [SUMQUANTITY]

Blue Medium 15

Blue Small 10
How it appears with Show items with no data feature on:

PRODUCT[COLOR] PRODUCT[SIZE] [SUMQUANTITY]

Blue Large

Blue Medium 15

Blue Small 10

Red Large

Notice how two new combinations showed up with the feature turned on: Blue - Large and Red - Large. Both of
those entries have no corresponding Quantity in the Sales table. However, they show up in the Product table.
2. Grouping columns from related tables: ProductStyle[Finish] - Product[Color ] - Sum (Sales[Quantity ])
How it appears with Show items with no data feature off:

PRODUCTSTYLE[FINISH] PRODUCT[COLOR] [SUMQUANTITY]

Gloss Blue 10

Matte Blue 15

How it appears with Show items with no data feature on:

PRODUCTSTYLE[FINISH] PRODUCT[COLOR] [SUMQUANTITY]

Gloss Blue 10

Gloss Red

Matte Blue 15

None

Notice how (Gloss-Red ) and (None, blank) appeared as combinations. Here is the reason they appeared:
Power BI first considered ProductStyle[Finish] and selected all the values to display - this resulted in Gloss,
Matte, None.
Using each of these values, Power BI selected all the corresponding Product[Color ] entries
Since None does not correspond to any Product[Color ], a blank appears for that value
It's important to note that the mechanism of selecting values for the columns is order-dependent, and can be
thought of as a Left outer join operation between tables. If the order of the columns is changed, the results will
change as well.
Let's look at an example of changing the order, and how it impacts results. This is the same as item 2 in this section,
with the ordering changed.
Product[Color] - ProductStyle[Finish] - Sum (Sales[Quantity])
How it appears with Show items with no data feature on:
 PRODUCT[COLOR] PRODUCTSTYLE[FINISH] [SUMQUANTITY]

Blue Gloss 10

Blue Matte 15

Red Gloss

In this case, notice how ProductStyle[Finish]=None does not appear in the table. This is because, in this case,
Power BI first selected all the Color values in the Product table. Then for each color, Power BI selected the
corresponding Finish values that contained data. Since None does not show up in any combination of Color, it is
not selected.

Example data model

This section shows the sample data model used in the examples in this article.
Model:

Data:

PRODUCT[PRODU PRODUCT[PRODU PRODUCT[CATEGO PRODUCT[STYLEID

CTID] CTNAME] PRODUCT[COLOR] PRODUCT[SIZE] RYID] ]

1 Prod1 Blue Small 1 1

2 Prod2 Blue Medium 2 2

3 Prod3 Red Large 1 1

4 Prod4 Blue Large 2 2

 PRODUCTCATEGORY[CATEGORYID] PRODUCTCATEGORY[CATEGORYNAME]

1 Phone

2 Camera

3 TV

PRODUCTSTYLE[STYLEID] PRODUCTSTYLE[FINISH] PRODUCTSTYLE[POLISHED]

1 Gloss Yes

2 Matte No

3 None No

SALES[SALEID] SALES[PRODUCTID] SALES[DATE] SALES[QUANTITY]

1 1 1/1/2012 0:00 10

2 2 1/1/2013 0:00 15

Next steps
This article described how you can enable the Show items with no data feature in Power BI. You might also be
interested in the following articles:
Default member in multidimensional models in Power BI
 Data sources in Power BI Desktop
2/13/2019 • 4 minutes to read • Edit Online

With Power BI Desktop, you can connect to data from many different sources. A full list of available data
sources is at the bottom of this page.
To connect to data, select Get Data from the Home ribbon. Selecting the down arrow, or the Get Data
text on the button, shows the Most Common data types menu shown in the following image:

Selecting More… from the Most Common menu displays the Get Data window. You can also bring up
the Get Data window (and bypass the Most Common menu) by selecting the Get Data icon button
directly.
 NOTE
The Power BI team is continually expanding the data sources available to Power BI Desktop and the Power BI
service. As such, you'll often see early versions of work-in-progress data sources marked as Beta or Preview. Any
data source marked as Beta or Preview has limited support and functionality, and should not be used in
production environments.

Data Sources
Data types are organized in the following categories:
All
File
Database
Power BI
Azure
Online Services
Other
The All category includes all data connection types from all categories.
The File category provides the following data connections:
Excel
Text/CSV
XML
JSON
Folder
PDF (Beta)
 SharePoint Folder
The following image shows the Get Data window for File.

The Database category provides the following data connections:

SQL Server Database
Access Database
SQL Server Analysis Services Database
Oracle Database
IBM DB2 Database
IBM Informix database (Beta)
IBM Netezza
MySQL Database
PostgreSQL Database
Sybase Database
Teradata Database
SAP HANA Database
SAP Business Warehouse Application Server
SAP Business Warehouse Message Server
Amazon Redshift
Impala
Google BigQuery
Vertica
 Snowflake
Essbase (Beta)
Dremio
Exasol
MarkLogic (Beta)
AtScale cubes (Beta)
BI Connector
Jethro (Beta)
Kyligence Enterprise (Beta)

NOTE
Some database connectors require that you enable them by selecting File > Options and settings > Options
then selecting Preview Features and enabling the connector. If you don't see some of the connectors mentioned
above and want to use them, check your Preview Features settings. Also note that any data source marked as
Beta or Preview has limited support and functionality, and should not be used in production environments.

The following image shows the Get Data window for Database.

The Power BI category provides the following data connections:

Power BI datasets
Power BI dataflows (Beta)
The following image shows the Get Data window for Power BI.

The Azure category provides the following data connections:

Azure SQL Database
Azure SQL Data Warehouse
Azure Analysis Services database
Azure Blob Storage
Azure Table Storage
Azure Cosmos DB (Beta)
Azure Data Lake Storage
Azure HDInsight (HDFS )
Azure HDInsight Spark
HDInsight Interactive Query
Azure Data Explorer (Beta)
The following image shows the Get Data window for Azure.
The Online Services category provides the following data connections:
SharePoint Online List
Microsoft Exchange Online
Dynamics 365 (online)
Dynamics NAV
Dynamics 365 Business Central
Dynamics 365 Business Central (on-premises)
Common Data Service for Apps (Beta)
Microsoft Azure Consumption Insights (Beta)
Azure DevOps (Beta)
Azure DevOps Server (Beta)
Salesforce Objects
Salesforce Reports
Google Analytics
Adobe Analytics
appFigures (Beta)
Data.World - Get Dataset (Beta)
Facebook
GitHub (Beta)
MailChimp (Beta)
Marketo (Beta)
 Mixpanel (Beta)
Planview Enterprise One - PRM (Beta)
Planview Projectplace (Beta)
QuickBooks Online (Beta)
Smartsheet
SparkPost (Beta)
Stripe (Beta)
SweetIQ (Beta)
Planview Enterprise One - CMT (Beta)
Twilio (Beta)
tyGraph (Beta)
Webtrends (Beta)
Zendesk (Beta)
TeamDesk (Beta)
Emigo Data Source (Beta)
Microsoft Graph Security (Beta)
The following image shows the Get Data window for Online Services.

The Other category provides the following data connections:

Web
SharePoint List
OData Feed
 Active Directory
Microsoft Exchange
Hadoop File (HDFS )
Spark
R Script
Python script
ODBC
OLE DB
Workforce Dimensions (Beta)
Denado
Paxata (Beta)
SurveyMonkey (Beta)
QubolePresto (Beta)
Quick Base (Beta)
Blank Query
The following image shows the Get Data window for Other.

NOTE
At this time, it's not possible to connect to custom data sources secured using Azure Active Directory.
Connecting to a Data Source
To connect to a data source, select the data source from the Get Data window and select Connect. In the
following image, Web is selected from the Other data connection category.

A connection window is displayed, specific to the type of data connection. If credentials are required,
you’ll be prompted to provide them. The following image shows a URL being entered to connect to a
Web data source.

When the URL or resource connection information is entered, select OK. Power BI Desktop makes the
connection to the data source, and presents the available data sources in the Navigator.
You can either load the data by selecting the Load button at the bottom of the Navigator pane, or edit
the query before loading data by selecting the Edit button.
That’s all there is to connecting to data sources in Power BI Desktop! Try connecting to data from our
growing list of data sources, and check back often - we continue to add to this list all the time.

Next steps
There are all sorts of things you can do with Power BI Desktop. For more information on its capabilities,
check out the following resources:
What is Power BI Desktop?
Query Overview with Power BI Desktop
Data Types in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Common Query Tasks in Power BI Desktop
 Get data from a Web page by providing an example
1/14/2019 • 2 minutes to read • Edit Online

Getting data from a web page lets users easily extract data from web pages, and import that data into Power BI
Desktop. Often however, data on Web pages aren't in tidy tables that are easy to extract, so getting data from such
pages - even if it's structured and consistent - can be challenging.
There is a solution. With the Get Data from Web by example feature, you can essentially show Power BI
Desktop which data you want to extract by providing one or more examples within the connector dialog, and it
will gather other data on the page that match your examples. With this solution you can extract all sorts of data
from Web pages, including data found in tables and other non-table data.

Using Get Data from Web by example

To use Get Data from Web by example, select Get Data from the Home ribbon menu. In the window that
appears, select Other from the categories in the left pane, and then select Web.
From there, enter the URL of the Web page from which you'd like to extract data. In this article we'll use the
Microsoft Store Web page, and show how this connector works.
If you want to follow along, you can use the Microsoft Store URL that we use in this article:

https://www.microsoft.com/store/top-paid/games/xbox?category=classics

When you select OK, you're taken to the Navigator dialog where any auto-detected tables from the Web page are
presented. In the case shown in the image below, no tables were found, but there is a button on the bottom of the
page called Extract table using examples that lets you provide examples.
Selecting the Extract table using examples presents an interactive window where you can preview the content
of the Web page, and enter sample values of the data you would like to extract.
In this example, we'll extract the Name and Price for each of the games on the page. We can do that by specifying a
couple of examples from the page for each column, as shown in the following image. As those examples are typed
in, Power Query (which is the underlying technology that extracts the data from the Web page) is able to extract
data that fits the pattern of example entries using smart data extraction algorithms.
 Note: Value suggestions only include values less than or equal to 128 characters in length.

Once we're happy with the data extracted from the Web page, we select OK to go to Query Editor, where we can
apply more transformations or shape the data, such as combining this data with other data our sources.
From there, you can create visuals or otherwise use the Web page data when creating your Power BI Desktop
reports.

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources,
check out the following resources:
Add columny by example
Connect to a Web page
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Connect to CSV files in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to datasets in the Power BI service from
Power BI Desktop
1/14/2019 • 7 minutes to read • Edit Online

You can establish a live connection to a shared dataset in the Power BI service, and create many different reports
from the same dataset. This means you can create your perfect data model in Power BI Desktop, publish it to the
Power BI service, then you and others can create multiple different reports (in separate .pbix files) from that same,
common data model. This feature is called Power BI service Live connection.

There are all sorts of benefits of this feature, including best practices, which we’ll discuss during this article. There
are also a few considerations and limitations, so please make sure you read through those - they're found at the
end of this article.

Using a Power BI service live connection for report lifecycle

management
One challenge with the popularity of Power BI is the proliferation of reports, dashboards, and their underlying data
models. Here's why: it's easy to create compelling reports in Power BI Desktop, then share (publish) those
reports in the Power BI service, and to create great dashboards from those datasets. Since so many people were
doing so, often using the same (or nearly the same) datasets, knowing which report was based on which dataset -
and how fresh each dataset might be - became a challenge. The Power BI service Live Connection addresses
that challenge, and makes creating, sharing, and expanding upon common-dataset reports and dashboards easier
and consistent.
Create a dataset everyone can use, then share it
Let's say Anna (a business analyst) is on your team, and she's great at creating good data models (often called
datasets). With Anna's expertise, she can create a dataset and report, and then share that report in the Power BI
service.
Everyone loves her report, and her dataset, and that's where the trouble would begin - everyone on her team
would attempt to create their own version of that dataset, then share their own reports with the team. All of the
sudden there was a multitude of reports (from different datasets) in your team's workspace in the Power BI
service. Which was the most recent? Were the datasets the same, or only almost? What were the differences? With
the Power BI service Live Connection feature, all that can change for the better. In the next section, we see how
others can use Anna's published dataset for their own reports, and enable everyone to use the same solid, vetted,
published dataset to build their unique reports.
Connect to a Power BI service dataset using a live connection
Once Anna creates her report (and creates the dataset it's based upon), she publishes it to the Power BI service, it
shows up in her team's workspace in the Power BI service. Now it's available for everyone in her workspace to see
and use.
To learn more about workspaces, see app workspaces.
Other members of her workspace can now establish a live connection to Anna's shared data model (using the
Power BI service live connection feature), and create their own unique reports, from her original dataset.
In the following image, you see how Anna creates one Power BI Desktop report, and publishes it (which includes
its data model) to the Power BI service. Then others in her workspace can connect to her data model using the
Power BI service live connection, and create their own unique reports based on her dataset.
 NOTE
Datasets are only shared in one workspace. To establish a Power BI service live connection, the dataset to which you connect
must be in a shared workspace of which you are a member.

Step-by-step for using the Power BI service live connection

Now that we know how useful the Power BI service live connection is, and how you can use it as a best practice
approach to report lifecycle management, let's walk through the steps that get us from Anna's great report (and
dataset) to a shared dataset that teammates in her Power BI workspace can use.
Publish a Power BI report and dataset
The first step in managing the report lifecycle using a Power BI service live connection is to have a report (and
dataset) that teammates want to use. So Anna must first publish her report from Power BI Desktop. She does
this by selecting Publish from the Home ribbon in Power BI Desktop.

If she isn't signed in to her Power BI service account, she's prompted to do so.

From there, she can choose the workspace destination to which the report and dataset will be published.
Remember, only members who have access to the workspace where a report is published can access its dataset
using a Power BI service live connection.
The publishing process begins, and Power BI Desktop shows the progress.

Once complete, Power BI Desktop shows you success, and provides a couple links to get you to the report itself
in the Power BI service, and a link to get Quick Insights on the report.

Next, let's see how other teammates who have access to the workspace where the report (and dataset) were
published can connect to the dataset and build our own reports.
Establish a Power BI service live connection to the published dataset
To establish a connection to the published report, and create your own report based on the published dataset,
select Get Data from the Home ribbon in Power BI Desktop, and select Power BI service. You can also select it
from Get Data > Online Services > Power BI service.
If you're not signed in to Power BI, you'll be prompted to do so. Once logged in, you're presented with a window
that shows which workspaces you're a member of, and you can select which workspace contains the dataset to
which you want to establish a Power BI service live connection.
The number in brackets beside the workspace shows how many shared datasets are available in that workgroup,
and selecting the triangle to the left expands the workspace, allowing you to select the shared dataset.
There are a few items to note from the previous Power BI service live connection window:
You can search for a shared dataset, but the search results are limited to the expanded items, and won't include
any workspaces that you have not expanded.
You can expand more than one workspace to expand your search.
When you select Load from the window, you establish a live connection to the selected dataset, which means the
data you see (the fields, and their values) are loaded into Power BI Desktop in real time.

Now you (and others) can create and share custom reports, all from the same dataset. This is a great way to have
one knowledgeable person create a well-formed dataset (such as what Anna does), and allow many teammates use
that shared dataset to create their own reports.

NOTE
When you create reports based on dataset using a live connection to the Power BI service, you can only publish that
report to the same Power BI service workspace that contains the dataset being used.

Limitations and considerations

When using the Power BI service live connection, there are a few limitations and considerations to keep in
mind.
Read-only members of a workspace cannot connect to datasets from Power BI Desktop.
Only users who are part of the same Power BI service workspace can connect to a published dataset using the
Power BI service live connection. Users can (and often do) belong to more than one workspace.
Since this is a live connection, left-navigation and modeling are disabled, similar to the behavior when
connected to SQL Server Analysis Services.
Since this is a live connection, RLS (row - and role-level security), OneDrive for Business, and other such
connection behaviors are enforced, just as they are when connected to SQL Server Analysis Services.
When selecting which dataset to connect to in the Power BI service, the search box only applies to workspaces
that have been expanded.
If the owner modifies the original shared .pbix file, the dataset and report that is shared in the Power BI
service is overwritten.
Members of a workspace cannot replace the originally shared report. Attempts to do so result in a warning that
prompts you to rename the file, and publish.
If you delete the shared dataset in the Power BI service, then other Power BI Desktop (.pbix files) will no
longer work properly or display their visuals.
For Content Packs, you must first create a copy of a content pack before using it as a basis for sharing a .pbix
report and dataset to the Power BI service.
For Content Packs from My Organization, once copied, you cannot replace the report created on the service
and/or a report created as part of copying a Content Pack with a live connection. Attempts to do so result in a
warning that prompts you to rename the file, and publish. In this situation, you can only replace published live
connected reports.
When you create a report based on dataset using a live connection to the Power BI service, you can only
publish that report to the same Power BI service workspace that contains the dataset being used.
Deleting a shared dataset in the Power BI service means you can no longer access that dataset from Power BI
Desktop.
 Import Excel workbooks into Power BI Desktop
1/14/2019 • 5 minutes to read • Edit Online

With Power BI Desktop, you can easily import Excel workbooks that contain Power Query queries, Power Pivot
models, and Power View worksheets into Power BI Desktop. Reports and visualizations are automatically created
based on the Excel workbook, and once imported, you can continue to improve and refine those reports using
Power BI Desktop, using the existing features and new features released with each Power BI Desktop monthly
update.
In the future, the plan is to provide additional communication between Excel and Power BI Desktop (such as
import/export); this current ability to import workbooks into Power BI Desktop lets existing Excel users get started
with Power BI Desktop.

How do I import an Excel workbook?

To import a workbook, from Power BI Desktop select File -> Import -> Excel Workbook Contents.

A window appears, letting you select the workbook to import. There is currently no limitation on the size or
number of objects in the workbook, but larger workbooks take longer for Power BI Desktop to analyze and
import.
 NOTE
To load or import Excel files from shared OneDrive for Business folders or from Office 365 group folders, use the URL of
the Excel file, and input it into the Web data source in Power BI Desktop. There are a few steps you need to follow to
properly format the OneDrive for Business URL, so check out Use OneDrive for Business links in Power BI Desktop for
more information and the correct series of steps.

Once a workbook is selected, Power BI Desktop analyzes the workbook and converts it into a Power BI Desktop
file (.pbix). This action is a one-time event; once the Power BI Desktop file is created with these steps, the Power BI
Desktop file has no dependence on the original Excel workbook, and can be modified or changed (and saved, and
shared) without affecting the original workbook.

Once the import is finished, a Summary page is displayed that describes the items that were converted, and also
lists any items that were not able to be imported.

When you select Close, the report is loaded in Power BI Desktop. The following image shows Power BI Desktop
after an Excel workbook was imported: Power BI Desktop automatically loaded the report based on the workbook
contents.
Now that the workbook is imported, you can continue working on the report – such as creating new visualizations,
adding data, or creating new report pages – using any of the features and capabilities included in Power BI
Desktop.

Which workbook elements are imported?

Power BI Desktop can import the following elements, commonly referred to as objects, in Excel.

OBJECT IN EXCEL WORKBOOK FINAL RESULT IN POWER BI DESKTOP FILE

Power Query queries All Power Query queries from Excel are converted to queries
in Power BI Desktop. If there were Query Groups defined in
the Excel Workbook, the same organization will be replicated
in Power BI Desktop. All queries are loaded unless they were
set to “Only Create Connection” in Excel. The Load behavior
can be customized from the Properties dialog in the Home
tab of Query Editor in Power BI Desktop.

Power Pivot External Data Connections All Power Pivot External Data Connections will be converted
to queries in Power BI Desktop.
 OBJECT IN EXCEL WORKBOOK FINAL RESULT IN POWER BI DESKTOP FILE

Linked Tables or Current Workbook tables If there is a worksheet table in Excel linked to the Data Model,
or linked to a query (by using From Table or the
Excel.CurrentWorkbook() function in M), the following options
are presented:
1. Import the table to the Power BI Desktop file. This
table is a one-time snapshot of the data, after which
you cannot edit the data in the table in Power BI
Desktop. There is a size limitation of 1 million
characters (total, combining all column headers and
cells) for tables created using this option.
2. Keep a connection to the original workbook.
Alternatively, you can keep a connection to the original
Excel Workbook and Power BI Desktop retrieves the
latest content in this table with each refresh, just like
any other query created against an Excel workbook in
Power BI Desktop.

Data Model Calculated Columns, Measures, KPIs, Data These Data Model objects are converted to the equivalent
Categories, and Relationships objects in Power BI Desktop. Note there are certain Data
Categories that are not available in Power BI Desktop, such as
Image. In these cases, the Data Category information will be
reset for the columns in question.

Power View Worksheets A new report page is created for each Power View worksheet
in Excel. The name and order of these report pages match the
original Excel workbook.

Are there any limitations to importing a workbook?

There are a few limitations to importing a workbook into Power BI Desktop, which is the following list:
External Connections to Analysis Services Tabular Models: In Excel 2013, it is possible to create a
connection to SQL Server Analysis Services Tabular models and create Power View reports on top of these
models without the need to import the data. This type of connection is currently not supported as part of
importing Excel Workbooks into Power BI Desktop. As a workaround, you must recreate these external
connections in Power BI Desktop.
Hierarchies: This type of Data Model object is currently not supported in Power BI Desktop. As such,
hierarchies are skipped as part of importing an Excel Workbook into Power BI Desktop.
Binary data columns: This type of Data Model column is currently not supported in Power BI Desktop. Binary
Data columns are removed from the resulting table in Power BI Desktop.
Unsupported Power View elements: There are a few features in Power View that are not available in Power
BI Desktop, such as Themes or certain types of visualizations (Scatter Chart with Play Axis, Drill-Down
behaviors, etc.). These unsupported visualizations result in Unsupported Visualization messages on their
corresponding locations in the Power BI Desktop report, which you can delete or reconfigure as needed.
Named Ranges using From Table in Power Query, or using Excel.CurrentWorkbook in M: Importing this
named range data into Power BI Desktop is not currently supported, but it is a planned update for Power BI
Desktop. Currently, these named ranges are loaded into Power BI Desktop as a connection to the external Excel
workbook.
PowerPivot to SSRS: PowerPivot external connections to SQL Server Reporting Services (SSRS ) are not
currently supported, since that data source is not currently available in Power BI Desktop.
 Connect to data using generic interfaces in Power BI
Desktop
2/13/2019 • 4 minutes to read • Edit Online

You can connect to a multitude of different data sources in Power BI Desktop, using built-in data connectors that
range from Access databases to Zendesk resources, as shown in the Get Data window. You can also connect to
all sorts of other data sources to further expand your connectivity options, by using the generic interfaces (such as
ODBC or REST APIs) built into Power BI Desktop.

Power BI Desktop data interfaces

Power BI Desktop includes an ever-growing collection of data connectors that are built to connect to a specific
data source. For example, the SharePoint List data connector provides specific fields and supporting information
during the connection sequence that are designed for SharePoint Lists, which is the case with other data sources
found in the window that appears when you select Get Data > More... (shown in the previous image).
In addition, Power BI Desktop lets you connect to data sources that aren't identified in the Get Data lists, by
using one of the following generic data interfaces:
ODBC
OLE DB
 OData
REST APIs
R Scripts
By providing the appropriate parameters in the connection windows that these generic interfaces provide, the
world of data sources you can access and use in Power BI Desktop grows significantly.
In the following sections, you can find lists of data sources that can be accessed by these generic interfaces.
Can't find the data source you wanted to use with Power BI Desktop? Submit your idea to the Power BI team's
list of ideas and requests.

Data sources accessible through ODBC

The ODBC connector in Power BI Desktop lets you import data from any third-party ODBC driver simply by
specifying a Data Source Name (DSN ) or a connection string. As an option, you can also specify a SQL
statement to execute against the ODBC driver.

The following list details a few examples of data sources to which Power BI Desktop can connect by using the
generic ODBC interface.

POWER BI DESKTOP GENERIC CONNECTOR EX TERNAL DATA SOURCE LINK FOR MORE INFORMATION

ODBC Cassandra Cassandra ODBC driver

ODBC Couchbase DB Couchbase and Power BI

ODBC DynamoDB DynamoDB ODBC driver

ODBC Google BigQuery BigQuery ODBC driver

ODBC Hbase Hbase ODBC driver

 POWER BI DESKTOP GENERIC CONNECTOR EX TERNAL DATA SOURCE LINK FOR MORE INFORMATION

ODBC Hive Hive ODBC driver

ODBC IBM Netezza IBM Netezza information

ODBC Presto Presto ODBC driver

ODBC Project Online Project Online article

ODBC Progress OpenEdge Progress OpenEdge ODBC driver blog

post

Data sources accessible through OLE DB

The OLE DB connector in Power BI Desktop lets you import data from any third-party OLE DB driver simply by
specifying a connection string. As an option, you can also specify a SQL statement to execute against the OLE DB
driver.

The following list details a few examples of the data sources to which Power BI Desktop can connect by using the
generic OLE DB interface.

POWER BI DESKTOP GENERIC CONNECTOR EX TERNAL DATA SOURCE LINK FOR MORE INFORMATION

OLE DB SAS OLE DB SAS provider for OLE DB

OLE DB Sybase OLE DB Sybase provider for OLE DB

Data sources accessible through OData

The OData connector in Power BI Desktop lets you import data from any OData URL simply by typing in or
pasting the OData URL. You can add multiple URL parts by typing or pasting those links in the text boxes
provided in the OData Feed window.

The following list details a few examples of the data sources to which Power BI Desktop can connect by using the
generic OData interface.

POWER BI DESKTOP GENERIC CONNECTOR EX TERNAL DATA SOURCE LINK FOR MORE INFORMATION

OData Coming soon Check back soon for OData data

sources

Data sources accessible through REST APIs

You can connect to data sources using the REST APIs and thereby use data from all sorts of data sources that
support REST.

The following list details a few examples of the data sources to which Power BI Desktop can connect by using the
generic REST APIs interface.
 POWER BI DESKTOP GENERIC CONNECTOR EX TERNAL DATA SOURCE LINK FOR MORE INFORMATION

REST APIs Couchbase DB Couchbase REST API information

Data sources accessible through R Script

You can use R scripts to access data sources, and use that data in Power BI Desktop.

The following list details a few examples of the data sources to which Power BI Desktop can connect by using the
generic R scripts interface.

POWER BI DESKTOP GENERIC CONNECTOR EX TERNAL DATA SOURCE LINK FOR MORE INFORMATION

R Script SAS Files R script guidance from CRAN

R Script SPSS Files R script guidance from CRAN

R Script R Statistical Files R script guidance from CRAN

Next steps
There are all sorts of data sources you can connect to using Power BI Desktop. For more information on data
sources, check out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to a PDF file in Power BI Desktop (Preview)
1/14/2019 • 2 minutes to read • Edit Online

In Power BI Desktop, you can connect to a PDF file and use the included data from the file, just like any other data
source in Power BI Desktop.

The following sections describe how to connect to a PDF file, select data, and bring that data into Power BI
Desktop.

Enable the PDF connector

The PDF connector is in preview for Power BI Desktop, and must be enabled. To enable the PDF connector, select
File > Options and Settings > Options > Preview features, then select the checkbox beside Get data from
PDF files.
You'll need to restart Power BI Desktop after you make the selection.
When you first use the PDF (beta) connector, you'll be warned that the PDF connector is still under development,
and may change in the future. Select Continue to use the connector.
We always recommend upgrading to the most recent release of Power BI Desktop, which you can get from a link
in get Power BI Desktop.

Connect to a PDF file

To connect to a PDF file select Get Data from the Home ribbon in Power BI Desktop. Select File from the
categories on the left, and you see PDF (beta).
You're prompted to provide the location of the PDF file you want to use. Once you provide the file location and the
PDF file loads, a Navigator window appears and displays the data available from the file, from which you can
select one or multiple elements to import and use in Power BI Desktop.
Selecting a checkbox next to discovered elements in the PDF file displays them in the right pane. When you're
ready to import, select the Load button to bring the data into Power BI Desktop.
Beginning with the November 2018 release of Power BI Desktop, you can specify the Start page and End Page
as optional parameters for your PDF connection. You can also specify these parameters in the M formula
language, using the following format:
Pdf.Tables(File.Contents("c:\sample.pdf"), [StartPage=10, EndPage=11])

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources,
check out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to Adobe Analytics in Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

In Power BI Desktop, you can connect to Adobe Analytics and use the underlying data just like any other data
source in Power BI Desktop.

Connect to Adobe Analytics data

To connect to Adobe Analytics data, select Get Data from the Home ribbon in Power BI Desktop. Select Online
Services from the categories on the left, and you see Adobe Analytics connector.
In the Adobe Analytics window that appears, select the Sign in button, and provide your credentials to sign in to
your Adobe Analytics account. The Adobe sign in window appears, as shown in the following image.
When prompted, put in your username and password. Once the connection is established, you can preview and
select multiple dimensions and measures within the Power BI Navigator dialog to create a single tabular output.
You can also provide any necessary input parameters required for the selected items.

You can Load the selected table, which brings the entire table into Power BI Desktop, or you can Edit the query,
which opens Query Editor so you can filter and refine the set of data you want to use, and then load that refined
set of data into Power BI Desktop.
Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources,
check out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to an Oracle database
2/26/2019 • 2 minutes to read • Edit Online

In order to connect to an Oracle database with Power BI Desktop, the correct Oracle client software must be
installed on the computer running Power BI Desktop. Which Oracle client software you use depends on which
version of Power BI Desktop you have installed - the 32-bit version or the 64-bit version.
Supported versions: Oracle 9 and later, Oracle client software 8.1.7 and later.

Determining which version of Power BI Desktop is installed

To determine which version of Power BI Desktop is installed, select File > Help > About then check the Version:
line. In the following image, a 64-bit version of Power BI Desktop is installed:

Installing the Oracle client

For 32-bit versions of Power BI Desktop, use the following link to download and install the 32-bit Oracle client:
32-bit Oracle Data Access Components (ODAC ) with Oracle Developer Tools for Visual Studio (12.1.0.2.4)
For 64-bit versions of Power BI Desktop, use the following link to download and install the 64-bit Oracle client:
64-bit ODAC 12c Release 4 (12.1.0.2.4) for Windows x64

Connect to an Oracle database

Once the matching Oracle client driver is installed, you can connect to an Oracle database. To make the connection,
take the following steps:
1. From the Get Data window, select Database > Oracle Database
2. In the Oracle Database dialog that appears, provide the name of the server, and select Connect. If a SID is
required, you can specify that using the format: ServerName/SID, where SID is the unique name of the
database. If the ServerName/SID format doesn't work, try using ServerName/ServiceName, where
ServiceName is the alias used when connecting.

TIP
If you're having trouble connecting in this step, try using the following format in the Server Name field:
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=host_name)(PORT=port_num))(CONNECT_DATA=
(SERVICE_NAME=service_name)))

3. If you want to import data using a native database query, you can put your query in the SQL Statement
 box, available by expanding the Advanced options section of the Oracle Database dialog.

4. Once your Oracle database information is entered into the Oracle Database dialog (including any optional
information such as a SID or a native database query), select OK to connect.
5. If the Oracle database requires database user credentials, input those credentials in the dialog when
prompted.

Troubleshooting
If you downloaded Power BI Desktop from the Microsoft Store, you might be unable to connect to Oracle
databases because of an Oracle driver issue. If you encounter this issue, the error message returned is "Object
reference not set". To address the issue, do one of the following:
Download Power BI Desktop from https://powerbi.microsoft.com/desktop instead.
If you want to use the version from the Microsoft Store: on your local computer, copy oraons.dll from
12.X.X\client_X into 12.X.X\client_X\bin. The X represents version and directory numbers.
 Run Python scripts in Power BI Desktop
2/13/2019 • 2 minutes to read • Edit Online

You can run Python scripts directly in Power BI Desktop, and import the resulting datasets into a Power BI
Desktop data model.

Install Python
To run Python scripts in Power BI Desktop, you need to install Python on your local machine. You can download
and install Python for free from many locations, including the Official Python download page, and the Anaconda.
The current release of Python scripting in Power BI Desktop supports Unicode characters as well as spaces (empty
characters) in the installation path.
Install Required Python Packages
The Power BI Python integration requires two Python packages to be installed (Pandas and Matplotlib). Using the
pip command line tool, install the following two packages,

pip install pandas

pip install matplotlib

Run Python scripts

With just a few steps in Power BI Desktop, you can run Python scripts and create a data model, from which you
can create reports, and share them on the Power BI service.
Prepare a Python script
To run a Python script in Power BI Desktop, create the script in your local Python development environment, and
make sure it runs successfully.
To run the script in Power BI Desktop, make sure the script runs successfully in a new and unmodified workspace.
This means that all packages and dependencies must be explicitly loaded and run.
When preparing and running a Python script in Power BI Desktop, there are a few limitations:
Only Pandas data frames are imported, so make sure the data you want to import to Power BI is represented in
a data frame
Any Python script that runs longer than 30 minutes times out
Interactive calls in the Python script, such as waiting for user input, halts the script’s execution
When setting the working directory within the Python script, you must define a full path to the working
directory, rather than a relative path
Nested tables (table of tables) are currently not supported
Run your Python script and import data
1. In Power BI Desktop, the Python Script data connector is found in Get Data. To run your Python Script,
select Get Data > More..., then select Other > Python script as shown in the following image:
2. If Python is installed on your local machine, the latest installed version is selected as your Python engine.
Simply copy your script into the script window and select OK.

3. If Python is not installed, is not identified, or if there are multiple installations on your local machine,
warning will be displayed.
 Python installation settings are centrally located in the Python Scripting section of the Options dialog. To
specify your Python installation settings, select File > Options and settings and then Options > Python
scripting. If multiple installations of Python are available, a drop-down menu appears that allows you to
select which installation to use. You can also select Other and give custom path.

4. Select OK to run the Python Script. When the script runs successfully, you can then choose the resulting
data frames to add to the Power BI model.
Refresh
You can refresh a Python script in Power BI Desktop. When you refresh a Python script, Power BI Desktop runs the
Python script again in the Power BI Desktop environment.

Next steps
Take a look at the following additional information about Python in Power BI.
Create Python Visuals in Power BI Desktop
Use an external Python IDE with Power BI
 Using Python in Query Editor
2/13/2019 • 4 minutes to read • Edit Online

You can use Python, a programming language widely used by statisticians, data scientists, and data analysts, in the
Power BI Desktop Query Editor. This integration of Python into Query Editor lets you perform data cleansing
using Python, and perform advanced data shaping and analytics in datasets, including completion of missing data,
predictions, and clustering, just to name a few. Python is a powerful language, and can be used in Query Editor to
prepare your data model and create reports.

Installing Python
To use Python in Power BI Desktop's Query Editor, you need to install Python on your local machine. You can
download and install Python for free from many locations, including the Official Python download page, and the
Anaconda.

Using Python in Query Editor

To show how to use Python in Query Editor, take this example from a stock market dataset, based on a .CSV file
that you can download from here and follow along. The steps for this example are the following:
1. First, load your data into Power BI Desktop. In this example, load the EuStockMarkets_NA.csv file and
select Get Data > CSV from the Home ribbon in Power BI Desktop.

2. Select the file and select Open, and the CSV is displayed in the CSV file dialog.
3. Once the data is loaded, you'll see it in the Fields pane in Power BI Desktop.

4. Open Query Editor by selecting Edit Queries from the Home tab in Power BI Desktop.
5. In the Transform tab, select Run Python Script and the Run Python Script editor appears (shown in the
next step). Notice that rows 15 and 20 suffer from missing data, as do other rows you can't see in the
following image. The steps below show how Python can (and will) complete those rows for you.

6. For this example, enter the following script code:

import pandas as pd
completedData = dataset.fillna(method='backfill', inplace=False)
dataset["completedValues"] = completedData["SMI missing values"]

NOTE
You'll need to have the pandas library installed in your Python environment for the previous script code to work
properly. To install pandas, run the following command in your Python installation: | > pip install pandas

When put into the Run Python Script dialog, the code looks like the following:
7. After selecting OK, Query Editor displays a warning about data privacy.

8. For the Python scripts to work properly in the Power BI service, all data sources need to be set to public. For
more information about privacy settings and their implications, see Privacy Levels.

Notice a new column in the Fields pane called completedValues. Notice there are a few missing data
 elements, such as on row 15 and 18. Take a look at how Python handles that in the next section.
With just five lines of Python script, Query Editor filled in the missing values with a predictive model.

Creating visuals from Python script data

Now we can create a visual to see how the Python script code using the pandas library completed the missing
values, as shown in the following image:

Once that visual is complete, and any other visuals you might want to create using Power BI Desktop, you can
save the Power BI Desktop file (which saves as a .pbix file) and then use the data model, including the Python
scripts that are part of it, in the Power BI service.

NOTE
Want to see a completed .pbix file with these steps completed? You're in luck - you can download the completed Power BI
Desktop file used in these examples right here.

Once you've uploaded the .pbix file to the Power BI service, a couple more steps are necessary to enable data
refresh (in the service) and to enable visuals to be updated in the service (the data needs access to Python for
visuals to be updated). The additional steps are the following:
Enable scheduled refresh for the dataset - to enable scheduled refresh for the workbook that contains your
dataset with Python scripts, see Configuring scheduled refresh, which also includes information about Personal
Gateway.
Install the Personal Gateway - you need a Personal Gateway installed on the machine where the file is
located, and where Python is installed; the Power BI service must access that workbook and re-render any
updated visuals. You can get more information on how to install and configure Personal Gateway.

Limitations
There are some limitations to queries that include Python scripts created in Query Editor:
All Python data source settings must be set to Public, and all other steps in a query created in Query Editor
must also be public. To get to data source settings, in Power BI Desktop select File > Options and
settings > Data source settings.
 From the Data Source Settings dialog, select the data source(s) and then select Edit Permissions... and
ensure that the Privacy Level is set to Public.

To enable scheduled refresh of your Python visuals or dataset, you need to enable Scheduled refresh and
have a Personal Gateway installed on the computer that houses the workbook and the Python installation.
For more information on both, see the previous section in this article, which provides links to learn more
about each.
Nested tables (table of tables) are currently not supported
There are all sorts of things you can do with Python and custom queries, so explore and shape your data just the
way you want it to appear.
 Use an external Python IDE with Power BI
1/14/2019 • 4 minutes to read • Edit Online

With Power BI Desktop, you can use your external Python IDE (Integrated Development Environment) to create
and refine Python scripts, then use those scripts in Power BI.

Enable an external Python IDE

You can launch your external Python IDE from Power BI Desktop and have your data automatically imported
and displayed in the Python IDE. From there, you can modify the script in that external Python IDE, then paste it
back into Power BI Desktop to create Power BI visuals and reports.
You can specify which Python IDE you would like to use, and have it launch automatically from within Power BI
Desktop.
Requirements
To use this feature, you need to install a Python IDE on your local computer. Power BI Desktop does not include,
deploy, or install the Python engine, so you must separately install Python on your local computer. You can choose
which Python IDE to use, with the following options:
You can install your favorite Python IDE, many of which are available for free, such as the Visual Studio
Code download page.
 Power BI Desktop also supports Visual Studio.
You can also install a different Python IDE and have Power BI Desktop launch that Python IDE by doing
one of the following:
You can associate .PY files with the external IDE you want Power BI Desktop to launch.
You can specify the .exe that Power BI Desktop should launch by selecting Other from the Python
Script Options section of the Options dialog. You can bring up the Options dialog by going to File
> Options and settings > Options.

If you have multiple Python IDEs installed, you can specify which will be launched by selecting it from the Detected
Python IDEs drop-down in the Options dialog.
By default, Power BI Desktop will launch Visual Studio Code as the external Python IDE if it's installed on your
local computer; if Visual Studio Code is not installed and you have Visual Studio, that will be launched instead.
If neither of those Python IDEs is installed, the application associated with .PY files is launched.
And if no .PY file association exists, it's possible to specify a path to a custom IDE in the Browse to your preferred
Python IDE section of the Options dialog. You can also launch a different Python IDE by selecting the Settings
gear icon beside the Launch Python IDE arrow icon, in Power BI Desktop.

Launch a Python IDE from Power BI Desktop

To launch a Python IDE from Power BI Desktop, take the following steps:
1. Load data into Power BI Desktop.
2. Select some fields from the Fields pane that you want to work with. If you haven't enabled script visuals yet,
 you'll be prompted to do so.

3. When script visuals are enabled, you can select a Python visual from the Visualizations pane, which
creates a blank Python visual that's ready to display the results of your script. The Python script editor
pane also appears.

4. Now you can select the fields you want to use in your Python script. When you select a field, the Python
script editor field automatically creates script code based on the field or fields you select. You can either
create (or paste) your Python script directly in the Python script editor pane, or you can leave it empty.
 NOTE
The default aggregation type for Python visuals is do not summarize.

5. You can now launch your Python IDE directly from Power BI Desktop. Select the Launch Python IDE
button, found on the right side of the Python script editor title bar, as shown below.

6. Your specified Python IDE is launched by Power BI Desktop, as shown in the following image (in this image,
Visual Studio Code is the default Python IDE ).
 NOTE
Power BI Desktop adds the first three lines of the script so it can import your data from Power BI Desktop once
you run the script.

7. Any script you created in the Python script editor pane of Power BI Desktop appears starting in line 4
in your Python IDE. At this point, you can create your Python script in the Python IDE. Once your Python
script is complete in your Python IDE, you need to copy and paste it back into the Python script editor
pane in Power BI Desktop, excluding the first three lines of the script that Power BI Desktop
automatically generated. Do not copy the first three lines of script back into Power BI Desktop, those lines
were only used to import your data to your Python IDE from Power BI Desktop.
Known limitations
Launching a Python IDE directly from Power BI Desktop has a few limitations:
Automatically exporting your script from your Python IDE into Power BI Desktop is not supported.

Next steps
Take a look at the following additional information about Python in Power BI.
Running Python Scripts in Power BI Desktop
Create Power BI visuals using Python
 Create Power BI visuals using Python
1/14/2019 • 5 minutes to read • Edit Online

With Power BI Desktop, you can use Python to visualize your data.

Install Python
Power BI Desktop does not include, deploy, or install the Python engine. To run Python scripts in Power BI
Desktop, you must separately install Python on your local computer. You can download and install Python for
free from many locations, including the Official Python download page, and the Anaconda. The current release of
Python scripting in Power BI Desktop supports Unicode characters as well as spaces (empty characters) in the
installation path.

Enable Python visuals

To enable Python visuals, select File > Options and settings > Options and in the Options page that appears,
make sure your local Python installation is specified in the Python Scripting section of the Options window, as
shown in the following image. In the following image, the path local installation of Python is C:\Python27 and
that path is explicitly provided in the text box. Make sure the path it displays properly reflects the local Python
installation you want Power BI Desktop to use.

Once you specify your Python installation, you’re ready to begin creating Python visuals.
Create Python visuals in Power BI Desktop
1. Select the Python Visual icon in the Visualization pane, as shown in the following image, to add a
Python visual.

When you add a Python visual to a report, Power BI Desktop does the following:
A placeholder Python visual image appears on the report canvas.
The Python script editor appears along the bottom of the center pane.

2. Next, add fields you want to consume in your Python script to the Values section in the Fields well, just as
you would with any other Power BI Desktop visual.
Only fields that have been added to the Fields well are available to your Python script. You can add new
fields or remove unneeded fields from the Fields well while working on your Python script in the Power BI
Desktop Python script editor. Power BI Desktop automatically detects which fields you have added or
removed.

NOTE
The default aggregation type for Python visuals is do not summarize.

3. Now you can use the data you selected to create a plot.
As you select fields, the Python script editor generates supporting Python script binding code based on
your selections in the gray section along the top of the editor pane. As you select or remove additional
fields, supporting code in the Python script editor is automatically generated or removed accordingly.
In the example shown in the following image, three fields were selected: hp, gear, and drat. As a result of
those selections, the Python script editor generated the following binding code:
 A dataframe called dataset was created
That dataframe is comprised of the different fields selected by the user
The default aggregation is do not summarize
Similar to table visuals, fields are grouped and duplicate rows only appear once

TIP
In certain cases, you may not want automatic grouping to occur, or you may want all rows to appear, including
duplicates. In that case, you can add an index field to your dataset that causes all rows to be considered unique and
which prevents grouping.

The generated dataframe is called a dataset, and you can access selected columns by their respective
names. For example, access the gear field by writing dataset["gear"] in your Python script.
4. With the dataframe automatically generated by the fields you selected, you’re ready to write a Python script
that results in plotting to the Python default device. When the script is complete, select Run from the
Python script editor title bar (Run is on the right side of the title bar).
When you select Run, Power BI Desktop identifies the plot and presents it on the canvas. Since the
process is executed on your local Python installation, make sure the required packages are installed.
Power BI Desktop replots the visual when any of the following events occur:
When you select Run from the Python script editor title bar
Whenever a data change occurs, due to data refresh, filtering, or highlighting
The following image shows an example of the correlation plot code, and it plots the correlations between
attributes of different types of cars.
5. To get a larger view of the visualizations, you can minimize the Python script editor. And, of course, like
other visuals in Power BI Desktop, you can cross filter the correlation plot by selecting only sport cars in
the donut visual (the round visual on the right, in the above example image).

6. You can also modify the Python script to customize the visual, and take advantage of the power of Python
by adding parameters to the plotting command.
The original plotting command was the following:
plt.matshow (dataset.corr('pearson'))
With a few changes in the Python script, the command is now the following:
plt.matshow (dataset.corr('kendall'))
As a result, the Python visual now plots using Kendall Tau correlation coefficient, as shown in the following
image.

When executing a Python script that results in an error, the Python visual is not plotted and an error
message is displayed on the canvas. For details on the error, select See details from the Python visual error
on the canvas.
 Python scripts security: Python visuals are created from Python scripts, which could contain code
with security or privacy risks. When attempting to view or interact with an Python visual for the first
time, a user is presented with a security warning message. Only enable Python visuals if you trust the
author and source, or after you review and understand the Python script.

Known limitations
Python visuals in Power BI Desktop has a few limitations:
Data size limitations – data used by the Python visual for plotting is limited to 150,000 rows. If more than
150,000 rows are selected, only the top 150,000 rows are used and a message is displayed on the image.
Calculation time limitation – if a Python visual calculation exceeds five minutes the execution times out,
resulting in an error.
Relationships – as with other Power BI Desktop visuals, if data fields from different tables with no defined
relationship between them are selected, an error occurs.
Python visuals are refreshed upon data updates, filtering, and highlighting. However, the image itself is not
interactive and cannot be the source of cross-filtering.
Python visuals respond to highlighting other visuals, but you cannot click on elements in the Python visual in
order to cross filter other elements.
Only plots that are plotted to the Python default display device are displayed correctly on the canvas. Avoid
explicitly using a different Python display device.

Next steps
Take a look at the following additional information about Python in Power BI.
Running Python Scripts in Power BI Desktop
Use an external Python IDE with Power BI
 Run R scripts in Power BI Desktop
1/14/2019 • 3 minutes to read • Edit Online

You can run R scripts directly in Power BI Desktop, and import the resulting datasets into a Power BI Desktop
data model.

Install R
To run R scripts in Power BI Desktop, you need to install R on your local machine. You can download and install R
for free from many locations, including the Revolution Open download page, and the CRAN Repository. The
current release of R scripting in Power BI Desktop supports Unicode characters as well as spaces (empty
characters) in the installation path.

Run R scripts
With just a few steps in Power BI Desktop, you can run R scripts and create a data model, from which you can
create reports, and share them on the Power BI service. R scripting in Power BI Desktop now supports number
formats that contain decimals (.) and commas (,).
Prepare an R script
To run an R script in Power BI Desktop, create the script in your local R development environment, and make sure
it runs successfully.
To run the script in Power BI Desktop, make sure the script runs successfully in a new and unmodified workspace.
This means that all packages and dependencies must be explicitly loaded and run. You can use source() to run
dependent scripts.
When preparing and running an R script in Power BI Desktop, there are a few limitations:
Only data frames are imported, so make sure the data you want to import to Power BI is represented in a data
frame
Columns that are typed as Complex and Vector are not imported, and are replaced with error values in the
created table
Values that are N/A are translated to NULL values in Power BI Desktop
Any R script that runs longer than 30 minutes times out
Interactive calls in the R script, such as waiting for user input, halts the script’s execution
When setting the working directory within the R script, you must define a full path to the working directory,
rather than a relative path
Run your R script and import data
1. In Power BI Desktop, the R Script data connector is found in Get Data. To run your R Script, select Get
Data > More..., then select Other > R script as shown in the following image:
2. If R is installed on your local machine, the latest installed version is selected as your R engine. Simply copy
your script into the script window and select OK.

3. If R is not installed, is not identified, or if there are multiple installations on your local machine, expand R
Installation Settings to display installation options, or to select which installation you want to run the R
script.
 If R is installed and is not identified, you can explicitly provide its location in the text box provided when you
expand R Installation Settings. In the above image, the path C:\Program Files\R\R -3.2.0 is explicitly
provided in the text box.
R installation settings are centrally located in the R Scripting section of the Options dialog. To specify your
R installation settings, select File > Options and settings and then Options > R scripting. If multiple
installations of R are available, a drop-down menu appears that allows you to select which installation to
use.

4. Select OK to run the R Script. When the script runs successfully, you can then choose the resulting data
frames to add to the Power BI model.
Refresh
You can refresh an R script in Power BI Desktop. When you refresh an R script, Power BI Desktop runs the R script
again in the Power BI Desktop environment.

Next steps
Take a look at the following additional information about R in Power BI.
Create R Visuals in Power BI Desktop
Use an external R IDE with Power BI
 Using R in Query Editor
2/13/2019 • 4 minutes to read • Edit Online

You can use R, a programming language widely used by statisticians, data scientists, and data analysts, in the
Power BI Desktop Query Editor. This integration of R into Query Editor lets you perform data cleansing using R,
and perform advanced data shaping and analytics in datasets, including completion of missing data, predictions,
and clustering, just to name a few. R is a powerful language, and can be used in Query Editor to prepare your data
model and create reports.

Installing R
To use R in Power BI Desktop's Query Editor, you need to install R on your local machine. You can download and
install R for free from many locations, including the Revolution Open download page, and the CRAN Repository.

Using R in Query Editor

To show how to use R in Query Editor, take this example from a stock market dataset, based on a .CSV file that
you can download from here and follow along. The steps for this example are the following:
1. First, load your data into Power BI Desktop. In this example, load the EuStockMarkets_NA.csv file and
select Get Data > CSV from the Home ribbon in Power BI Desktop.

2. Select the file and select Open, and the CSV is displayed in the CSV file dialog.
3. Once the data is loaded, you'll see it in the Fields pane in Power BI Desktop.

4. Open Query Editor by selecting Edit Queries from the Home tab in Power BI Desktop.
5. In the Transform tab, select Run R Script and the Run R Script editor appears (shown in the next step).
Notice that rows 15 and 20 suffer from missing data, as do other rows you can't see in the following image.
The steps below show how R can (and will) complete those rows for you.

6. For this example, enter the following script code:

library(mice)
tempData <- mice(dataset,m=1,maxit=50,meth='pmm',seed=100)
completedData <- complete(tempData,1)
output <- dataset
output$completedValues <- completedData$"SMI missing values"

NOTE
You'll need to have the mice library installed in your R environment for the previous script code to work properly. To
install mice, run the following command in your R installation: | > install.packages('mice')

When put into the Run R Script dialog, the code looks like the following:
7. After selecting OK, Query Editor displays a warning about data privacy.

8. For the R scripts to work properly in the Power BI service, all data sources need to be set to public. For more
information about privacy settings and their implications, see Privacy Levels.

Notice a new column in the Fields pane called completedValues. Notice there are a few missing data
elements, such as on row 15 and 18. Take a look at how R handles that in the next section.
With just five lines of R script, Query Editor filled in the missing values with a predictive model.
Creating visuals from R script data
Now we can create a visual to see how the R script code using the mice library completed the missing values, as
shown in the following image:

Once that visual is complete, and any other visuals you might want to create using Power BI Desktop, you can
save the Power BI Desktop file (which saves as a .pbix file) and then use the data model, including the R scripts
that are part of it, in the Power BI service.

NOTE
Want to see a completed .pbix file with these steps completed? You're in luck - you can download the completed Power BI
Desktop file used in these examples right here.

Once you've uploaded the .pbix file to the Power BI service, a couple more steps are necessary to enable data
refresh (in the service) and to enable visuals to be updated in the service (the data needs access to R for visuals to
be updated). The additional steps are the following:
Enable scheduled refresh for the dataset - to enable scheduled refresh for the workbook that contains your
dataset with R scripts, see Configuring scheduled refresh, which also includes information about Personal
Gateway.
Install the Personal Gateway - you need a Personal Gateway installed on the machine where the file is
located, and where R is installed; the Power BI service must access that workbook and re-render any updated
visuals. You can get more information on how to install and configure Personal Gateway.

Limitations
There are some limitations to queries that include R scripts created in Query Editor:
All R data source settings must be set to Public, and all other steps in a query created in Query Editor must
also be public. To get to data source settings, in Power BI Desktop select File > Options and settings >
Data source settings.
 From the Data Source Settings dialog, select the data source(s) and then select Edit Permissions... and
ensure that the Privacy Level is set to Public.

To enable scheduled refresh of your R visuals or dataset, you need to enable Scheduled refresh and have a
Personal Gateway installed on the computer that houses the workbook and the R installation. For more
information on both, see the previous section in this article, which provides links to learn more about each.
There are all sorts of things you can do with R and custom queries, so explore and shape your data just the way
you want it to appear.
 Use an external R IDE with Power BI
1/14/2019 • 4 minutes to read • Edit Online

With Power BI Desktop, you can use your external R IDE (Integrated Development Environment) to create and
refine R scripts, then use those scripts in Power BI.

Enable an external R IDE

Previously, you had to use the R script editor in Power BI Desktop to create and run R scripts. With this release,
you can launch your external R IDE from Power BI Desktop and have your data automatically imported and
displayed in the R IDE. From there, you can modify the script in that external R IDE, then paste it back into Power
BI Desktop to create Power BI visuals and reports.
Beginning with the September 2016 release of Power BI Desktop (version 2.39.4526.362), you can specify which
R IDE you would like to use, and have it launch automatically from within Power BI Desktop.
Requirements
To use this feature, you need to install an R IDE on your local computer. Power BI Desktop does not include,
deploy, or install the R engine, so you must separately install R on your local computer. You can choose which R
IDE to use, with the following options:
You can install your favorite R IDE, many of which are available for free, such as the Revolution Open
download page, and the CRAN Repository.
Power BI Desktop also supports R Studio and Visual Studio 2015 with R Tools for Visual Studio editors.
 You can also install a different R IDE and have Power BI Desktop launch that R IDE by doing one of the
following:
You can associate .R files with the external IDE you want Power BI Desktop to launch.
You can specify the .exe that Power BI Desktop should launch by selecting Other from the R Script
Options section of the Options dialog. You can bring up the Options dialog by going to File >
Options and settings > Options.

If you have multiple R IDEs installed, you can specify which will be launched by selecting it from the Detected R
IDEs drop-down in the Options dialog.
By default, Power BI Desktop will launch R Studio as the external R IDE if it's installed on your local computer; if
R Studio is not installed and you have Visual Studio 2015 with R Tools for Visual Studio, that will be launched
instead. If neither of those R IDEs is installed, the application associated with .R files is launched.
And if no .R file association exists, it's possible to specify a path to a custom IDE in the Browse to your preferred R
IDE section of the Options dialog. You can also launch a different R IDE by selecting the Settings gear icon
beside the Launch R IDE arrow icon, in Power BI Desktop.

Launch an R IDE from Power BI Desktop

To launch an R IDE from Power BI Desktop, take the following steps:
1. Load data into Power BI Desktop.
2. Select some fields from the Fields pane that you want to work with. If you haven't enabled script visuals
yet, you'll be prompted to do so.
3. When script visuals are enabled, you can select an R visual from the Visualizations pane, which creates a
blank R visual that's ready to display the results of your script. The R script editor pane also appears.

4. Now you can select the fields you want to use in your R script. When you select a field, the R script editor
field automatically creates script code based on the field or fields you select. You can either create (or paste)
your R script directly in the R script editor pane, or you can leave it empty.
 NOTE
The default aggregation type for R visuals is do not summarize.

5. You can now launch your R IDE directly from Power BI Desktop. Select the Launch R IDE button, found
on the right side of the R script editor title bar, as shown below.

6. Your specified R IDE is launched by Power BI Desktop, as shown in the following image (in this image,
RStudio is the default R IDE ).
 NOTE
Power BI Desktop adds the first three lines of the script so it can import your data from Power BI Desktop once
you run the script.

7. Any script you created in the R script editor pane of Power BI Desktop appears starting in line 4 in your
R IDE. At this point, you can create your R script in the R IDE. Once your R script is complete in your R IDE,
you need to copy and paste it back into the R script editor pane in Power BI Desktop, excluding the first
three lines of the script that Power BI Desktop automatically generated. Do not copy the first three lines of
script back into Power BI Desktop, those lines were only used to import your data to your R IDE from
Power BI Desktop.
Known limitations
Launching an R IDE directly from Power BI Desktop has a few limitations:
Automatically exporting your script from your R IDE into Power BI Desktop is not supported.
R Client editor (RGui.exe) is not supported, because the editor itself does not support opening files.

Next steps
Take a look at the following additional information about R in Power BI.
Running R Scripts in Power BI Desktop
Create Power BI visuals using R
 R packages in the Power BI service
1/14/2019 • 15 minutes to read • Edit Online

You can use the powerful R programming language to create visuals in the Power BI service. Many R packages are
supported in the Power BI service (and more are being supported all the time), and some packages are not.
The following sections provide an alphabetical table of which R packages are supported in Power BI, and which
are not. For more information about R in Power BI, see the R visuals article.

Request support for a new R package

Supported R packages for the Power BI service are found in the following section, titled Supported Packages. If
you would like to request support of an R package not found in that list, you can send an email with your request
to the R in Power BI Feedback Team.

Requirements and Limitations of R packages

There are a handful of requirements and limitations for R packages:
The Power BI service, for the most part, supports R packages with free and open-source software licenses
such as GPL -2, GPL -3, MIT+, and so on.
The Power BI service supports packages published in CRAN. The service does not support private or
custom R packages. Users are encouraged to make their private packages available on CRAN prior to
requesting the package be available in the Power BI service.
The Power BI Desktop has two variations for R packages:
For R visuals, you can install any package, including custom R packages
For Custom R visuals, only public CRAN packages are supported for auto-installation of the packages
For security and privacy reasons, R packages that provide client-server queries over the World-Wide Web
(such as RgoogleMaps) in the service, are not supported. Networking is blocked for such attempts. See the
following section for a list of supported and unsupported R packages.
The approval process for including a new R package has a tree of dependencies; some dependencies
required to be installed in the service cannot be supported.

R packages that are supported in Power BI

The following table shows which packages are supported in the Power BI service.

PACKAGE VERSION LINK

abc 2.1 https://cran.r-

project.org/web/packages/abc/index.ht
ml

abc.data 1 https://cran.r-
project.org/web/packages/abc.data/inde
x.html
PACKAGE VERSION LINK

abind 1.4-5 https://cran.r-

project.org/web/packages/abind/index.h
tml

abind tensor polyclip (>= 1.5-0)

acepack 1.4.1 https://cran.r-

project.org/web/packages/acepack/inde
x.html

actuar 2.1-1 https://cran.r-

project.org/web/packages/actuar/index.
html

ade4 1.7-6 https://cran.r-

project.org/web/packages/ade4/index.ht
ml

AdMit 2.1.3 https://cran.r-

project.org/web/packages/AdMit/index.
html

AER 1.2-5 https://cran.r-

project.org/web/packages/AER/index.ht
ml

alluvial 0.1-2 https://cran.r-

project.org/web/packages/alluvial/index.
html

andrews 1 https://cran.r-
project.org/web/packages/andrews/inde
x.html

aod 1.3 https://cran.r-

project.org/web/packages/aod/index.ht
ml

apcluster 1.4.4 https://cran.r-

project.org/web/packages/apcluster/ind
ex.html

ape 4.1 https://cran.r-

project.org/web/packages/ape/index.ht
ml

aplpack 1.3.0 https://cran.r-

project.org/web/packages/aplpack/index
.html

approximator 1.2-6 https://cran.r-

project.org/web/packages/approximator
/index.html
PACKAGE VERSION LINK

arm 1.9-3 https://cran.r-

project.org/web/packages/arm/index.ht
ml

arules 1.5-2 https://cran.r-

project.org/web/packages/arules/index.
html

arulesViz 1.2-1 https://cran.r-

project.org/web/packages/arulesViz/ind
ex.html

ash 1.0-15 https://cran.r-

project.org/web/packages/ash/index.ht
ml

assertthat 0.2.0 https://cran.r-

project.org/web/packages/assertthat/in
dex.html

AzureML 0.2.14 https://cran.r-

project.org/web/packages/AzureML/ind
ex.html

BaBooN 0.2-0 https://cran.r-

project.org/web/packages/BaBooN/inde
x.html

BACCO 2.0-9 https://cran.r-

project.org/web/packages/BACCO/index
.html

backports 1.1.0 https://cran.r-

project.org/web/packages/backports/in
dex.html

BaM 1.0.1 https://cran.r-

project.org/web/packages/BaM/index.ht
ml

BAS 1.4.6 https://cran.r-

project.org/web/packages/BAS/index.ht
ml

base 3.4.1 NA

base64 2 https://cran.r-
project.org/web/packages/base64/index
.html

base64enc miniCRAN uuid

base64enc 0.1-3 https://cran.r-

project.org/web/packages/base64enc/in
dex.html
PACKAGE VERSION LINK

base64enc htmltools htmlwidgets (>= 0.9)

BayesDA 2012.04-1 https://cran.r-

project.org/web/packages/BayesDA/ind
ex.html

BayesFactor 0.9.12-2 https://cran.r-

project.org/web/packages/BayesFactor/i
ndex.html

bayesGARCH 2.1.3 https://cran.r-

project.org/web/packages/bayesGARCH
/index.html

bayesm 3.1-0.1 https://cran.r-

project.org/web/packages/bayesm/inde
x.html

bayesmix 0.7-4 https://cran.r-

project.org/web/packages/bayesmix/ind
ex.html

bayesQR 2.3 https://cran.r-

project.org/web/packages/bayesQR/ind
ex.html

bayesSurv 3 https://cran.r-
project.org/web/packages/bayesSurv/in
dex.html

Bayesthresh 2.0.1 https://cran.r-

project.org/web/packages/Bayesthresh/i
ndex.html

BayesTree 0.3-1.4 https://cran.r-

project.org/web/packages/BayesTree/in
dex.html

BayesValidate 0 https://cran.r-
project.org/web/packages/BayesValidate
/index.html

BayesX 0.2-9 https://cran.r-

project.org/web/packages/BayesX/index.
html

BayHaz 0.1-3 https://cran.r-

project.org/web/packages/BayHaz/index
.html

bbemkr 2 https://cran.r-
project.org/web/packages/bbemkr/inde
x.html
PACKAGE VERSION LINK

BCBCSF 1.0-1 https://cran.r-

project.org/web/packages/BCBCSF/inde
x.html

BCE 2.1 https://cran.r-

project.org/web/packages/BCE/index.ht
ml

bclust 1.5 https://cran.r-

project.org/web/packages/bclust/index.
html

bcp 4.0.0 https://cran.r-

project.org/web/packages/bcp/index.ht
ml

beanplot 1.2 https://cran.r-

project.org/web/packages/beanplot/ind
ex.html

beeswarm 0.2.3 https://cran.r-

project.org/web/packages/beeswarm/in
dex.html

benford.analysis 0.1.4.1 https://cran.r-

project.org/web/packages/benford.analy
sis/index.html

BenfordTests 1.2.0 https://cran.r-

project.org/web/packages/BenfordTests/
index.html

bfp 0.0-35 https://cran.r-

project.org/web/packages/bfp/index.ht
ml

BH 1.62.0-1 https://cran.r-
project.org/web/packages/BH/index.htm
l

bindr 0.1 https://cran.r-

project.org/web/packages/bindr/index.h
tml

bindrcpp 0.2 https://cran.r-

project.org/web/packages/bindrcpp/ind
ex.html

binom 1.1-1 https://cran.r-

project.org/web/packages/binom/index.
html

bisoreg 1.4 https://cran.r-

project.org/web/packages/bisoreg/index
.html
PACKAGE VERSION LINK

bit 1.1-12 https://cran.r-

project.org/web/packages/bit/index.htm
l

bit64 0.9-7 https://cran.r-

project.org/web/packages/bit64/index.h
tml

bitops 1.0-6 https://cran.r-

project.org/web/packages/bitops/index.
html

blob 1.1.0 https://cran.r-

project.org/web/packages/blob/index.ht
ml

BLR 1.4 https://cran.r-

project.org/web/packages/BLR/index.ht
ml

BMA 3.18.7 https://cran.r-

project.org/web/packages/BMA/index.ht
ml

Bmix 0.6 https://cran.r-

project.org/web/packages/Bmix/index.ht
ml

BMS 0.3.4 https://cran.r-

project.org/web/packages/BMS/index.ht
ml

bnlearn 4.2 https://cran.r-

project.org/web/packages/bnlearn/index
.html

boa 1.1.8-2 https://cran.r-

project.org/web/packages/boa/index.ht
ml

boot 1.3-19 https://cran.r-

project.org/web/packages/boot/index.ht
ml

boot 1.3-20 https://cran.r-

project.org/web/packages/boot/index.ht
ml

bootstrap 2017.2 https://cran.r-

project.org/web/packages/bootstrap/in
dex.html

Boruta 5.2.0 https://cran.r-

project.org/web/packages/Boruta/index.
html
PACKAGE VERSION LINK

bqtl 1.0-32 https://cran.r-

project.org/web/packages/bqtl/index.ht
ml

BradleyTerry2 1.0-6 https://cran.r-

project.org/web/packages/BradleyTerry2
/index.html

brew 1.0-6 https://cran.r-

project.org/web/packages/brew/index.ht
ml

brglm 0.6.1 https://cran.r-

project.org/web/packages/brglm/index.
html

broom 0.4.2 https://cran.r-

project.org/web/packages/broom/index.
html

broom dplyr tidyr (>= 0.6.0)

bspec 1.5 https://cran.r-

project.org/web/packages/bspec/index.h
tml

bspmma 0.1-1 https://cran.r-

project.org/web/packages/bspmma/ind
ex.html

bupaR 0.3.0 https://cran.r-

project.org/web/packages/bupaR/index.
html

BVS 4.12.1 https://cran.r-

project.org/web/packages/BVS/index.ht
ml

C50 0.1.0-24 https://cran.r-

project.org/web/packages/C50/index.ht
ml

Cairo 1.5-9 https://cran.r-

project.org/web/packages/Cairo/index.h
tml

cairoDevice 2.24 https://cran.r-

project.org/web/packages/cairoDevice/i
ndex.html

cairoDevice NA CRAN

calibrate 1.7.2 https://cran.r-

project.org/web/packages/calibrate/inde
x.html
PACKAGE VERSION LINK

calibrator 1.2-6 https://cran.r-

project.org/web/packages/calibrator/ind
ex.html

car 2.1-5 https://cran.r-

project.org/web/packages/car/index.htm
l

caret 6.0-76 https://cran.r-

project.org/web/packages/caret/index.ht
ml

catnet 1.15.0 https://cran.r-

project.org/web/packages/catnet/index.
html

caTools 1.17.1 https://cran.r-

project.org/web/packages/caTools/index
.html

cclust 0.6-21 https://cran.r-

project.org/web/packages/cclust/index.h
tml

cellranger 1.1.0 https://cran.r-

project.org/web/packages/cellranger/ind
ex.html

checkmate 1.8.3 https://cran.r-

project.org/web/packages/checkmate/in
dex.html

checkmate htmlwidgets CRAN

checkpoint 0.4.0 346

choroplethrMaps 1.0.1 https://cran.r-

project.org/web/packages/choroplethr
Maps/index.html

chron 2.3-50 https://cran.r-

project.org/web/packages/chron/index.h
tml

circlize 0.4.1 https://cran.r-

project.org/web/packages/circlize/index.
html

Ckmeans.1d.dp 4.2.1 https://cran.r-

project.org/web/packages/Ckmeans.1d.
dp/index.html

class 7.3-14 https://cran.r-

project.org/web/packages/class/index.ht
ml
PACKAGE VERSION LINK

class 7.3-14 https://cran.r-

project.org/web/packages/class/index.ht
ml

classInt 0.1-24 https://cran.r-

project.org/web/packages/classInt/index
.html

ClickClust 1.1.5 https://cran.r-

project.org/web/packages/ClickClust/ind
ex.html

clickstream 1.2.1 https://cran.r-

project.org/web/packages/clickstream/in
dex.html

clue 0.3-53 https://cran.r-

project.org/web/packages/clue/index.ht
ml

cluster 2.0.6 https://cran.r-

project.org/web/packages/cluster/index.
html

cluster 2.0.6 https://cran.r-

project.org/web/packages/cluster/index.
html

cluster CRAN NA

clv 0.3-2.1 https://cran.r-

project.org/web/packages/clv/index.htm
l

cmprsk 2.2-7 https://cran.r-

project.org/web/packages/cmprsk/index
.html

coda 0.19-1 https://cran.r-

project.org/web/packages/coda/index.ht
ml

codetools 0.2-15 https://cran.r-

project.org/web/packages/codetools/ind
ex.html

codetools 0.2-15 https://cran.r-

project.org/web/packages/codetools/ind
ex.html

coefplot 1.2.4 https://cran.r-

project.org/web/packages/coefplot/inde
x.html
PACKAGE VERSION LINK

coin 1.2-1 https://cran.r-

project.org/web/packages/coin/index.ht
ml

colorRamps 2.3 https://cran.r-

project.org/web/packages/colorRamps/i
ndex.html

colorspace methods grid

colorspace 1.3-2 https://cran.r-

project.org/web/packages/colorspace/in
dex.html

colorspace parallel ggplot2 (>= 2.0.0)

combinat 0.0-8 https://cran.r-

project.org/web/packages/combinat/ind
ex.html

compiler 3.4.1 NA

compositions 1.40-1 https://cran.r-

project.org/web/packages/compositions
/index.html

CORElearn 1.50.3 https://cran.r-

project.org/web/packages/CORElearn/in
dex.html

corpcor 1.6.9 https://cran.r-

project.org/web/packages/corpcor/index
.html

corrgram 1.12 https://cran.r-

project.org/web/packages/corrgram/ind
ex.html

corrplot 0.77 https://cran.r-

project.org/web/packages/corrplot/inde
x.html

covr 3.0.0 https://cran.r-

project.org/web/packages/covr/index.ht
ml

cowplot 0.8.0 https://cran.r-

project.org/web/packages/cowplot/inde
x.html

crayon 1.3.2 https://cran.r-

project.org/web/packages/crayon/index.
html
PACKAGE VERSION LINK

crosstalk 1.0.0 https://cran.r-

project.org/web/packages/crosstalk/ind
ex.html

cslogistic 0.1-3 https://cran.r-

project.org/web/packages/cslogistic/ind
ex.html

cts 1.0-21 https://cran.r-

project.org/web/packages/cts/index.htm
l

ctv 0.8-2 https://cran.r-

project.org/web/packages/ctv/index.htm
l

cubature 1.3-11 https://cran.r-

project.org/web/packages/cubature/ind
ex.html

curl 2.6 https://cran.r-

project.org/web/packages/curl/index.ht
ml

curl 3 https://cran.r-
project.org/web/packages/curl/index.ht
ml

cvTools 0.3.2 https://cran.r-

project.org/web/packages/cvTools/index
.html

d3heatmap 0.6.1.1 https://cran.r-

project.org/web/packages/d3heatmap/i
ndex.html

d3Network 0.5.2.1 https://cran.r-

project.org/web/packages/d3Network/i
ndex.html

data.table plyr Rsolnp

data.table 1.10.4 https://cran.r-

project.org/web/packages/data.table/in
dex.html

data.table zoo grid

data.tree 0.7.0 https://cran.r-

project.org/web/packages/data.tree/ind
ex.html

datasets 3.4.1 NA
PACKAGE VERSION LINK

date 1.2-37 https://cran.r-

project.org/web/packages/date/index.ht
ml

DBI 0.7 https://cran.r-

project.org/web/packages/DBI/index.ht
ml

dbscan 1.1-1 https://cran.r-

project.org/web/packages/dbscan/index.
html

dclone 2.1-2 https://cran.r-

project.org/web/packages/dclone/index.
html

deal 1.2-37 https://cran.r-

project.org/web/packages/deal/index.ht
ml

deepnet 0.2 https://cran.r-

project.org/web/packages/deepnet/inde
x.html

deldir 0.1-14 https://cran.r-

project.org/web/packages/deldir/index.h
tml

dendextend 1.5.2 https://cran.r-

project.org/web/packages/dendextend/i
ndex.html

DEoptimR 1.0-8 https://cran.r-

project.org/web/packages/DEoptimR/in
dex.html

deployrRserve 9.0.0 209

descr 1.1.3 https://cran.r-

project.org/web/packages/descr/index.h
tml

deSolve 1.2 https://cran.r-

project.org/web/packages/deSolve/inde
x.html

devtools 1.13.3 https://cran.r-

project.org/web/packages/devtools/inde
x.html

DiagrammeR 0.9.0 https://cran.r-

project.org/web/packages/DiagrammeR
/index.html
PACKAGE VERSION LINK

dichromat 2.0-0 https://cran.r-

project.org/web/packages/dichromat/in
dex.html

digest 0.6.12 https://cran.r-

project.org/web/packages/digest/index.
html

digest NA CRAN

diptest 0.75-7 https://cran.r-

project.org/web/packages/diptest/index.
html

distrom 0.3-3 https://cran.r-

project.org/web/packages/distrom/inde
x.html

dlm 1.1-4 https://cran.r-

project.org/web/packages/dlm/index.ht
ml

DMwR 0.4.1 https://cran.r-

project.org/web/packages/DMwR/index.
html

doParallel 1.0.10 https://cran.r-

project.org/web/packages/doParallel/ind
ex.html

doSNOW 1.0.14 https://cran.r-

project.org/web/packages/doSNOW/ind
ex.html

dotCall64 0.9-04 https://cran.r-

project.org/web/packages/dotCall64/ind
ex.html

downloader 0.4 https://cran.r-

project.org/web/packages/downloader/i
ndex.html

dplyr 0.7.2 https://cran.r-

project.org/web/packages/dplyr/index.h
tml

DPpackage 1.1-6 https://cran.r-

project.org/web/packages/DPpackage/i
ndex.html

dse 2015.12-1 https://cran.r-

project.org/web/packages/dse/index.ht
ml
PACKAGE VERSION LINK

DT 0.2 https://cran.r-
project.org/web/packages/DT/index.htm
l

dtw 1.18-1 https://cran.r-

project.org/web/packages/dtw/index.ht
ml

dygraphs 1.1.1.4 https://cran.r-

project.org/web/packages/dygraphs/ind
ex.html

dynlm 0.3-5 https://cran.r-

project.org/web/packages/dynlm/index.
html

e1071 1.6-8 https://cran.r-

project.org/web/packages/e1071/index.
html

earth 4.5.1 https://cran.r-

project.org/web/packages/earth/index.h
tml

EbayesThresh 1.3.2 https://cran.r-

project.org/web/packages/EbayesThresh
/index.html

ebdbNet 1.2.5 https://cran.r-

project.org/web/packages/ebdbNet/ind
ex.html

effects 3.1-2 https://cran.r-

project.org/web/packages/effects/index.
html

ellipse 0.3-8 https://cran.r-

project.org/web/packages/ellipse/index.
html

emulator 1.2-15 https://cran.r-

project.org/web/packages/emulator/ind
ex.html

energy 1.7-0 https://cran.r-

project.org/web/packages/energy/index.
html

ensembleBMA 5.1.4 https://cran.r-

project.org/web/packages/ensembleBM
A/index.html

entropy 1.2.1 https://cran.r-

project.org/web/packages/entropy/inde
x.html
PACKAGE VERSION LINK

estimability 1.2 https://cran.r-

project.org/web/packages/estimability/i
ndex.html

eulerr 2.0.0 https://cran.r-

project.org/web/packages/eulerr/index.h
tml

EvalEst 2015.4-2 https://cran.r-

project.org/web/packages/EvalEst/index.
html

EvalEst (>= 2006.1-1) setRNG (>= 2004.4-1) tframe (>= 2011.3-1)

evaluate 0.10.1 https://cran.r-

project.org/web/packages/evaluate/inde
x.html

evd 2.3-2 https://cran.r-

project.org/web/packages/evd/index.ht
ml

evdbayes 1.1-1 https://cran.r-

project.org/web/packages/evdbayes/ind
ex.html

exactLoglinTest 1.4.2 https://cran.r-

project.org/web/packages/exactLoglinTe
st/index.html

exactRankTests 0.8-29 https://cran.r-

project.org/web/packages/exactRankTes
ts/index.html

expint 0.1-4 https://cran.r-

project.org/web/packages/expint/index.
html

expm 0.999-2 https://cran.r-

project.org/web/packages/expm/index.h
tml

extraDistr 1.8.7 https://cran.r-

project.org/web/packages/extraDistr/ind
ex.html

extremevalues 2.3.2 https://cran.r-

project.org/web/packages/extremevalue
s/index.html

FactoMineR 1.36 https://cran.r-

project.org/web/packages/FactoMineR/i
ndex.html
PACKAGE VERSION LINK

factorQR 0.1-4 https://cran.r-

project.org/web/packages/factorQR/ind
ex.html

faoutlier 0.7.2 https://cran.r-

project.org/web/packages/faoutlier/inde
x.html

fastmatch 1.1-0 https://cran.r-

project.org/web/packages/fastmatch/in
dex.html

fBasics 3011.87 https://cran.r-

project.org/web/packages/fBasics/index.
html

fdrtool 1.2.15 https://cran.r-

project.org/web/packages/fdrtool/index.
html

fields 9 https://cran.r-
project.org/web/packages/fields/index.h
tml

filehash 2.4-1 https://cran.r-

project.org/web/packages/filehash/index
.html

fitdistrplus 1.0-9 https://cran.r-

project.org/web/packages/fitdistrplus/in
dex.html

flashClust 1.01-2 https://cran.r-

project.org/web/packages/flashClust/ind
ex.html

flexclust 1.3-4 https://cran.r-

project.org/web/packages/flexclust/inde
x.html

flexmix 2.3-14 https://cran.r-

project.org/web/packages/flexmix/index.
html

FME 1.3.5 https://cran.r-

project.org/web/packages/FME/index.ht
ml

fmsb 0.6.1 https://cran.r-

project.org/web/packages/fmsb/index.ht
ml

FNN 1.1 https://cran.r-

project.org/web/packages/FNN/index.ht
ml
PACKAGE VERSION LINK

fontBitstreamVera 0.1.1 https://cran.r-

project.org/web/packages/fontBitstream
Vera/index.html

fontLiberation 0.1.0 https://cran.r-

project.org/web/packages/fontLiberatio
n/index.html

fontquiver 0.2.1 https://cran.r-

project.org/web/packages/fontquiver/in
dex.html

forcats 0.2.0 https://cran.r-

project.org/web/packages/forcats/index.
html

foreach 1.4.4 NA

foreach 1.4.3 https://cran.r-

project.org/web/packages/foreach/index
.html

foreach (>= 1.4.3) ggplot2 (>= 2.2.0) reshape2 (>= 1.4.2)

forecast 8.1 https://cran.r-

project.org/web/packages/forecast/inde
x.html

forecastHybrid 1.0.8 https://cran.r-

project.org/web/packages/forecastHybri
d/index.html

foreign 0.8-67 https://cran.r-

project.org/web/packages/foreign/index.
html

foreign 0.8-69 https://cran.r-

project.org/web/packages/foreign/index.
html

formatR 1.5 https://cran.r-

project.org/web/packages/formatR/inde
x.html

formattable 0.2.0.1 https://cran.r-

project.org/web/packages/formattable/i
ndex.html

Formula 1.2-2 https://cran.r-

project.org/web/packages/Formula/inde
x.html

fpc 2.1-10 https://cran.r-

project.org/web/packages/fpc/index.htm
l
PACKAGE VERSION LINK

fracdiff 1.4-2 https://cran.r-

project.org/web/packages/fracdiff/index.
html

fTrading 3010.78 https://cran.r-

project.org/web/packages/fTrading/inde
x.html

futile.logger 1.4.3 https://cran.r-

project.org/web/packages/futile.logger/i
ndex.html

futile.options 1.0.0 https://cran.r-

project.org/web/packages/futile.options
/index.html

gam 1.14-4 https://cran.r-

project.org/web/packages/gam/index.ht
ml

gamlr 1.13-3 https://cran.r-

project.org/web/packages/gamlr/index.h
tml

gamlss 5.0-4 https://cran.r-

project.org/web/packages/gamlss/index.
html

gamlss.data 5.0-0 https://cran.r-

project.org/web/packages/gamlss.data/i
ndex.html

gamlss.data (>= 5.0-0) gamlss.dist (>= 4.3.1) nlme

gamlss.dist 5.0-3 https://cran.r-

project.org/web/packages/gamlss.dist/in
dex.html

gbm 2.1.3 https://cran.r-

project.org/web/packages/gbm/index.ht
ml

gclus 1.3.1 https://cran.r-

project.org/web/packages/gclus/index.h
tml

gdata 2.18.0 https://cran.r-

project.org/web/packages/gdata/index.h
tml

gdtools 0.1.4 https://cran.r-

project.org/web/packages/gdtools/index
.html
PACKAGE VERSION LINK

gee 4.13-19 https://cran.r-

project.org/web/packages/gee/index.ht
ml

genalg 0.2.0 https://cran.r-

project.org/web/packages/genalg/index.
html

genetics 1.3.8.1 https://cran.r-

project.org/web/packages/genetics/inde
x.html

geoR 1.7-5.2 https://cran.r-

project.org/web/packages/geoR/index.h
tml

geoRglm 0.9-8 https://cran.r-

project.org/web/packages/geoRglm/ind
ex.html

geosphere 1.5-5 https://cran.r-

project.org/web/packages/geosphere/in
dex.html

geosphere digest scales

GGally 1.3.2 https://cran.r-

project.org/web/packages/GGally/index.
html

ggdendro 0.1-20 https://cran.r-

project.org/web/packages/ggdendro/in
dex.html

ggeffects (>= 0.2.0) ggplot2 (>= 2.2.1) knitr

ggforce 0.1.1 https://cran.r-

project.org/web/packages/ggforce/index
.html

ggfortify 0.4.1 https://cran.r-

project.org/web/packages/ggfortify/inde
x.html

ggjoy 0.4.0 https://cran.r-

project.org/web/packages/ggjoy/index.h
tml

ggm 2.3 https://cran.r-

project.org/web/packages/ggm/index.ht
ml

ggmap 2.6.1 https://cran.r-

project.org/web/packages/ggmap/index.
html
PACKAGE VERSION LINK

ggmcmc 1.1 https://cran.r-

project.org/web/packages/ggmcmc/inde
x.html

ggplot2 CRAN NA

ggplot2 2.2.1 https://cran.r-

project.org/web/packages/ggplot2/inde
x.html

ggplot2 reshape2 CRAN

ggplot2 glasso huge

ggplot2 (>= 2.0.0) CRAN

ggplot2 (>= 2.2.0) XML yaml

ggplot2movies 0.0.1 https://cran.r-

project.org/web/packages/ggplot2movi
es/index.html

ggpmisc 0.2.16 https://cran.r-

project.org/web/packages/ggpmisc/inde
x.html

ggpubr 0.1.5 https://cran.r-

project.org/web/packages/ggpubr/index
.html

ggrepel 0.6.5 https://cran.r-

project.org/web/packages/ggrepel/index
.html

ggridges 0.4.1 https://cran.r-

project.org/web/packages/ggridges/ind
ex.html

ggsci 2.8 https://cran.r-

project.org/web/packages/ggsci/index.h
tml

ggsignif 0.4.0 https://cran.r-

project.org/web/packages/ggsignif/inde
x.html

ggtern 2.2.1 https://cran.r-

project.org/web/packages/ggtern/index.
html

ggthemes 3.4.0 https://cran.r-

project.org/web/packages/ggthemes/in
dex.html
PACKAGE VERSION LINK

gistr 0.4.0 https://cran.r-

project.org/web/packages/gistr/index.ht
ml

git2r 0.19.0 https://cran.r-

project.org/web/packages/git2r/index.ht
ml

glasso 1.8 https://cran.r-

project.org/web/packages/glasso/index.
html

glmmBUGS 2.4.0 https://cran.r-

project.org/web/packages/glmmBUGS/i
ndex.html

glmnet 2.0-10 https://cran.r-

project.org/web/packages/glmnet/index.
html

GlobalOptions 0.0.12 https://cran.r-

project.org/web/packages/GlobalOption
s/index.html

glue 1.1.1 https://cran.r-

project.org/web/packages/glue/index.ht
ml

gmodels 2.16.2 https://cran.r-

project.org/web/packages/gmodels/inde
x.html

gmp 0.5-13.1 https://cran.r-

project.org/web/packages/gmp/index.ht
ml

gnm 1.0-8 https://cran.r-

project.org/web/packages/gnm/index.ht
ml

goftest 1.1-1 https://cran.r-

project.org/web/packages/goftest/index.
html

googleVis 0.6.2 https://cran.r-

project.org/web/packages/googleVis/in
dex.html

GPArotation 2014.11-1 https://cran.r-

project.org/web/packages/GPArotation/
index.html

gplots 3.0.1 https://cran.r-

project.org/web/packages/gplots/index.
html
PACKAGE VERSION LINK

gplots registry methods

graphics 3.4.1 NA

graphics grDevices party (>= 1.1-0)

graphics CRAN NA

grDevices 3.4.1 NA

grDevices methods utils

grDevices CRAN NA

grDevices htmlwidgets (>= 0.6) purrr (>= 0.2.0)

grDevices stats CRAN

grid 3.4.1 NA

grid lattice ggplot2

gridBase 0.4-7 https://cran.r-

project.org/web/packages/gridBase/inde
x.html

gridBase colorspace RColorBrewer

gridExtra 2.2.1 https://cran.r-

project.org/web/packages/gridExtra/ind
ex.html

gridExtra Matrix glue

gridExtra (>= 2.0.0) graphics reshape2

growcurves 0.2.4.1 https://cran.r-

project.org/web/packages/growcurves/i
ndex.html

grpreg 3.1-2 https://cran.r-

project.org/web/packages/grpreg/index.
html

gss 2.1-7 https://cran.r-

project.org/web/packages/gss/index.ht
ml

gstat 1.1-5 https://cran.r-

project.org/web/packages/gstat/index.h
tml
PACKAGE VERSION LINK

gsubfn 0.6-6 https://cran.r-

project.org/web/packages/gsubfn/index.
html

gtable 0.2.0 https://cran.r-

project.org/web/packages/gtable/index.
html

gtable grid gridExtra

gtools 3.5.0 https://cran.r-

project.org/web/packages/gtools/index.
html

gWidgets 0.0-54 https://cran.r-

project.org/web/packages/gWidgets/ind
ex.html

gWidgetsRGtk2 0.0-84 https://cran.r-

project.org/web/packages/gWidgetsRGt
k2/index.html

gWidgetstcltk 0.0-55 https://cran.r-

project.org/web/packages/gWidgetstclt
k/index.html

haplo.stats 1.7.7 https://cran.r-

project.org/web/packages/haplo.stats/in
dex.html

hash 2.2.6 https://cran.r-

project.org/web/packages/hash/index.ht
ml

haven 1.1.0 https://cran.r-

project.org/web/packages/haven/index.
html

hbsae 1 https://cran.r-
project.org/web/packages/hbsae/index.
html

hdrcde 3.1 https://cran.r-

project.org/web/packages/hdrcde/index.
html

heavy 0.38.1 https://cran.r-

project.org/web/packages/heavy/index.
html

hexbin 1.27.1 https://cran.r-

project.org/web/packages/hexbin/index.
html

hexbin Rcpp grDevices

PACKAGE VERSION LINK

hflights 0.1 https://cran.r-

project.org/web/packages/hflights/index
.html

HH 3.1-34 https://cran.r-
project.org/web/packages/HH/index.ht
ml

HI 0.4 https://cran.r-
project.org/web/packages/HI/index.html

highcharter 0.5.0 https://cran.r-

project.org/web/packages/highcharter/i
ndex.html

highr 0.6 https://cran.r-

project.org/web/packages/highr/index.h
tml

HistData 0.8-1 https://cran.r-

project.org/web/packages/HistData/ind
ex.html

Hmisc 4.0-3 https://cran.r-

project.org/web/packages/Hmisc/index.
html

hms 0.3 https://cran.r-

project.org/web/packages/hms/index.ht
ml

HSAUR 1.3-8 https://cran.r-

project.org/web/packages/HSAUR/index
.html

htmlTable 1.9 https://cran.r-

project.org/web/packages/htmlTable/ind
ex.html

htmltools jsonlite igraph

htmltools base64enc CRAN

htmltools 0.3.6 https://cran.r-

project.org/web/packages/htmltools/ind
ex.html

htmlwidgets 0.9 https://cran.r-

project.org/web/packages/htmlwidgets/i
ndex.html

httpuv 1.3.5 https://cran.r-

project.org/web/packages/httpuv/index.
html
PACKAGE VERSION LINK

httr 1.2.1 https://cran.r-

project.org/web/packages/httr/index.ht
ml

huge 1.2.7 https://cran.r-

project.org/web/packages/huge/index.h
tml

hunspell 2.7 https://cran.r-

project.org/web/packages/hunspell/inde
x.html

IBrokers 0.9-12 https://cran.r-

project.org/web/packages/IBrokers/inde
x.html

ifultools 2.0-4 https://cran.r-

project.org/web/packages/ifultools/inde
x.html

igraph 1.1.2 https://cran.r-

project.org/web/packages/igraph/index.
html

igraph CRAN NA

igraph jpeg png

igraph methods RColorBrewer

influenceR 0.1.0 https://cran.r-

project.org/web/packages/influenceR/in
dex.html

influenceR (>= 0.1.0) magrittr (>= 1.5) RColorBrewer (>=

inline 0.3.14 https://cran.r-

project.org/web/packages/inline/index.h
tml

intervals 0.15.1 https://cran.r-

project.org/web/packages/intervals/inde
x.html

ipred 0.9-6 https://cran.r-

project.org/web/packages/ipred/index.h
tml

irlba 2.2.1 https://cran.r-

project.org/web/packages/irlba/index.ht
ml

irr 0.84 https://cran.r-

project.org/web/packages/irr/index.html
PACKAGE VERSION LINK

iterators 1.0.8 https://cran.r-

project.org/web/packages/iterators/inde
x.html

iterators 1.0.8 https://cran.r-

project.org/web/packages/iterators/inde
x.html

janeaustenr 0.1.5 https://cran.r-

project.org/web/packages/janeaustenr/i
ndex.html

janeaustenr purrr (>= 0.1.1) methods

janitor 0.3.0 https://cran.r-

project.org/web/packages/janitor/index.
html

jpeg 0.1-8 https://cran.r-

project.org/web/packages/jpeg/index.ht
ml

jsonlite 1.4 https://cran.r-

project.org/web/packages/jsonlite/index.
html

jsonlite 1.5 https://cran.r-

project.org/web/packages/jsonlite/index.
html

jsonlite CRAN NA

kernlab 0.9-25 https://cran.r-

project.org/web/packages/kernlab/index
.html

KernSmooth 2.23-15 https://cran.r-

project.org/web/packages/KernSmooth/
index.html

KernSmooth 2.23-15 https://cran.r-

project.org/web/packages/KernSmooth/
index.html

KFKSDS 1.6 https://cran.r-

project.org/web/packages/KFKSDS/inde
x.html

kinship2 1.6.4 https://cran.r-

project.org/web/packages/kinship2/inde
x.html

kknn 1.3.1 https://cran.r-

project.org/web/packages/kknn/index.ht
ml
PACKAGE VERSION LINK

klaR 0.6-12 https://cran.r-

project.org/web/packages/klaR/index.ht
ml

km.ci 0.5-2 https://cran.r-

project.org/web/packages/km.ci/index.h
tml

KMsurv 0.1-5 https://cran.r-

project.org/web/packages/KMsurv/inde
x.html

knitr rmarkdown dplyr

knitr 1.16 https://cran.r-

project.org/web/packages/knitr/index.ht
ml

knitr jsonlite (>= 0.9.20) shiny

labeling 0.3 https://cran.r-

project.org/web/packages/labeling/inde
x.html

laeken 0.4.6 https://cran.r-

project.org/web/packages/laeken/index.
html

Lahman 5.0-0 https://cran.r-

project.org/web/packages/Lahman/inde
x.html

lambda.r 1.1.9 https://cran.r-

project.org/web/packages/lambda.r/ind
ex.html

lars 1.2 https://cran.r-

project.org/web/packages/lars/index.ht
ml

latex2exp 0.4.0 https://cran.r-

project.org/web/packages/latex2exp/ind
ex.html

lattice 0.20-35 https://cran.r-

project.org/web/packages/lattice/index.
html

lattice 0.20-35 https://cran.r-

project.org/web/packages/lattice/index.
html

latticeExtra 0.6-28 https://cran.r-

project.org/web/packages/latticeExtra/in
dex.html
PACKAGE VERSION LINK

latticeExtra lubridate cluster

lava 1.5 https://cran.r-

project.org/web/packages/lava/index.ht
ml

lavaan 0.5-23.1097 https://cran.r-

project.org/web/packages/lavaan/index.
html

lazyeval 0.2.0 https://cran.r-

project.org/web/packages/lazyeval/inde
x.html

lazyeval pryr magrittr

leaflet 1.1.0 https://cran.r-

project.org/web/packages/leaflet/index.
html

leaflet.esri 0.2 https://cran.r-

project.org/web/packages/leaflet.esri/in
dex.html

leaflet.extras 0.2 https://cran.r-

project.org/web/packages/leaflet.extras/i
ndex.html

leaps 3 https://cran.r-
project.org/web/packages/leaps/index.h
tml

LearnBayes 2.15 https://cran.r-

project.org/web/packages/LearnBayes/i
ndex.html

LiblineaR 2.10-8 https://cran.r-

project.org/web/packages/LiblineaR/ind
ex.html

LICORS 0.2.0 https://cran.r-

project.org/web/packages/LICORS/index
.html

limSolve 1.5.5.2 https://cran.r-

project.org/web/packages/limSolve/inde
x.html

linprog 0.9-2 https://cran.r-

project.org/web/packages/linprog/index.
html

lme4 1.1-13 https://cran.r-

project.org/web/packages/lme4/index.ht
ml
PACKAGE VERSION LINK

lmm 1 https://cran.r-
project.org/web/packages/lmm/index.ht
ml

lmtest 0.9-35 https://cran.r-

project.org/web/packages/lmtest/index.
html

locfit 1.5-9.1 https://cran.r-

project.org/web/packages/locfit/index.ht
ml

locpol 0.6-0 https://cran.r-

project.org/web/packages/locpol/index.
html

LogicReg 1.5.9 https://cran.r-

project.org/web/packages/LogicReg/ind
ex.html

lpSolve 5.6.13 https://cran.r-

project.org/web/packages/lpSolve/index.
html

lsa 0.73.1 https://cran.r-

project.org/web/packages/lsa/index.htm
l

lsmeans 2.26-3 https://cran.r-

project.org/web/packages/lsmeans/inde
x.html

lubridate 1.6.0 https://cran.r-

project.org/web/packages/lubridate/ind
ex.html

lubridate magrittr modelr

magic 1.5-6 https://cran.r-

project.org/web/packages/magic/index.
html

magick 1.5 https://cran.r-

project.org/web/packages/magick/index.
html

magrittr 1.5 https://cran.r-

project.org/web/packages/magrittr/inde
x.html

magrittr psych purrr

magrittr methods rmarkdown

PACKAGE VERSION LINK

MAPA 2.0.2 https://cran.r-

project.org/web/packages/MAPA/index.
html

mapdata 2.2-6 https://cran.r-

project.org/web/packages/mapdata/ind
ex.html

mapproj 1.2-5 https://cran.r-

project.org/web/packages/mapproj/inde
x.html

maps 3.2.0 https://cran.r-

project.org/web/packages/maps/index.h
tml

maptools 0.9-2 https://cran.r-

project.org/web/packages/maptools/ind
ex.html

maptools httr uuid

maptree 1.4-7 https://cran.r-

project.org/web/packages/maptree/inde
x.html

marima 2.2 https://cran.r-

project.org/web/packages/marima/index
.html

markdown methods png

markdown 0.8 https://cran.r-

project.org/web/packages/markdown/in
dex.html

MASS 7.3-47 https://cran.r-

project.org/web/packages/MASS/index.
html

MASS 7.3-47 https://cran.r-

project.org/web/packages/MASS/index.
html

MASS stats gmodels

MasterBayes 2.55 https://cran.r-

project.org/web/packages/MasterBayes/
index.html

Matrix 1.2-10 https://cran.r-

project.org/web/packages/Matrix/index.
html
PACKAGE VERSION LINK

Matrix 1.2-10 https://cran.r-

project.org/web/packages/Matrix/index.
html

matrixcalc coda NA

matrixcalc 1.0-3 https://cran.r-

project.org/web/packages/matrixcalc/in
dex.html

MatrixModels Rcpp (>= 0.11.2) methods

MatrixModels 0.4-1 https://cran.r-

project.org/web/packages/MatrixModel
s/index.html

maxent 1.3.3.1 https://cran.r-

project.org/web/packages/maxent/index
.html

maxent glmnet tau

maxLik 1.3-4 https://cran.r-

project.org/web/packages/maxLik/index.
html

maxstat 0.7-25 https://cran.r-

project.org/web/packages/maxstat/inde
x.html

mboost 2.8-1 https://cran.r-

project.org/web/packages/mboost/inde
x.html

mclust 5.3 https://cran.r-

project.org/web/packages/mclust/index.
html

mclust Rcpp sROC

mcmc 0.9-5 https://cran.r-

project.org/web/packages/mcmc/index.
html

MCMCglmm 2.24 https://cran.r-

project.org/web/packages/MCMCglmm
/index.html

mda 0.4-9 https://cran.r-

project.org/web/packages/mda/index.ht
ml

memoise 1.1.0 https://cran.r-

project.org/web/packages/memoise/ind
ex.html
PACKAGE VERSION LINK

methods 3.4.1 NA

methods utils grDevices

methods pkgconfig rlang (>= 0.1)

methods stats utils

methods scales CRAN

methods Rcpp CRAN

methods CRAN NA

metricsgraphics 0.9.0 https://cran.r-

project.org/web/packages/metricsgraphi
cs/index.html

mgcv 1.8-17 https://cran.r-

project.org/web/packages/mgcv/index.h
tml

mgcv 1.8-18 https://cran.r-

project.org/web/packages/mgcv/index.h
tml

mi 1 https://cran.r-
project.org/web/packages/mi/index.html

mice 2.3 https://cran.r-

project.org/web/packages/mice/index.ht
ml

microbenchmark 1.4-2.1 https://cran.r-

project.org/web/packages/microbenchm
ark/index.html

MicrosoftR 3.4.1.0081 NA

mime 0.5 https://cran.r-

project.org/web/packages/mime/index.h
tml

miniCRAN 0.2.10 https://cran.r-

project.org/web/packages/miniCRAN/in
dex.html

miniUI 0.1.1 https://cran.r-

project.org/web/packages/miniUI/index.
html
PACKAGE VERSION LINK

minpack.lm 1.2-1 https://cran.r-

project.org/web/packages/minpack.lm/i
ndex.html

minqa 1.2.4 https://cran.r-

project.org/web/packages/minqa/index.
html

mirt 1.25 https://cran.r-

project.org/web/packages/mirt/index.ht
ml

misc3d 0.8-4 https://cran.r-

project.org/web/packages/misc3d/index.
html

miscTools 0.6-22 https://cran.r-

project.org/web/packages/miscTools/ind
ex.html

mitools 2.3 https://cran.r-

project.org/web/packages/mitools/index
.html

mixtools 1.1.0 https://cran.r-

project.org/web/packages/mixtools/inde
x.html

mlbench 2.1-1 https://cran.r-

project.org/web/packages/mlbench/inde
x.html

mlogitBMA 0.1-6 https://cran.r-

project.org/web/packages/mlogitBMA/i
ndex.html

mnormt 1.5-5 https://cran.r-

project.org/web/packages/mnormt/inde
x.html

MNP 3.0-2 https://cran.r-

project.org/web/packages/MNP/index.h
tml

ModelMetrics 1.1.0 https://cran.r-

project.org/web/packages/ModelMetric
s/index.html

modelr 0.1.1 https://cran.r-

project.org/web/packages/modelr/index.
html

modeltools 0.2-21 https://cran.r-

project.org/web/packages/modeltools/i
ndex.html
PACKAGE VERSION LINK

modeltools (>= 0.2-21) strucchange survival (>= 2.37-7)

mombf 1.9.5 https://cran.r-

project.org/web/packages/mombf/index
.html

monomvn 1.9-7 https://cran.r-

project.org/web/packages/monomvn/in
dex.html

monreg 0.1.3 https://cran.r-

project.org/web/packages/monreg/inde
x.html

mosaic 1.0.0 https://cran.r-

project.org/web/packages/mosaic/index.
html

mosaicData mosaicCore ggplot2

mosaicData 0.14.0 https://cran.r-

project.org/web/packages/mosaicData/i
ndex.html

MSBVAR 0.9-3 https://cran.r-

project.org/web/packages/MSBVAR/ind
ex.html

msm 1.6.4 https://cran.r-

project.org/web/packages/msm/index.ht
ml

multcomp 1.4-6 https://cran.r-

project.org/web/packages/multcomp/in
dex.html

multcomp htmlTable htmltools

multicool 0.1-10 https://cran.r-

project.org/web/packages/multicool/ind
ex.html

munsell 0.4.3 https://cran.r-

project.org/web/packages/munsell/inde
x.html

mvoutlier 2.0.8 https://cran.r-

project.org/web/packages/mvoutlier/ind
ex.html

mvtnorm robustbase kernlab

mvtnorm xtable (>= 1.8-2) CRAN

PACKAGE VERSION LINK

mvtnorm 1.0-6 https://cran.r-

project.org/web/packages/mvtnorm/ind
ex.html

NbClust 3 https://cran.r-
project.org/web/packages/NbClust/inde
x.html

ncvreg 3.9-1 https://cran.r-

project.org/web/packages/ncvreg/index.
html

network 1.13.0 https://cran.r-

project.org/web/packages/network/inde
x.html

networkD3 0.4 https://cran.r-

project.org/web/packages/networkD3/i
ndex.html

neuralnet 1.33 https://cran.r-

project.org/web/packages/neuralnet/ind
ex.html

nlme 3.1-131 https://cran.r-

project.org/web/packages/nlme/index.ht
ml

nlme 3.1-131 https://cran.r-

project.org/web/packages/nlme/index.ht
ml

nlme rpart spatstat.utils (>= 1.6-0)

nloptr 1.0.4 https://cran.r-

project.org/web/packages/nloptr/index.
html

NLP 0.1-10 https://cran.r-

project.org/web/packages/NLP/index.ht
ml

NMF 0.20.6 https://cran.r-

project.org/web/packages/NMF/index.ht
ml

nnet 7.3-12 https://cran.r-

project.org/web/packages/nnet/index.ht
ml

nnet stats stats4

nnet 7.3-12 https://cran.r-

project.org/web/packages/nnet/index.ht
ml
PACKAGE VERSION LINK

nnls 1.4 https://cran.r-

project.org/web/packages/nnls/index.ht
ml

nortest 1.0-4 https://cran.r-

project.org/web/packages/nortest/index
.html

nortest e1071 scales

numbers 0.6-6 https://cran.r-

project.org/web/packages/numbers/ind
ex.html

numDeriv 2016.8-1 https://cran.r-

project.org/web/packages/numDeriv/in
dex.html

openair 2.1-5 https://cran.r-

project.org/web/packages/openair/index
.html

openssl 0.9.6 https://cran.r-

project.org/web/packages/openssl/index
.html

OutlierDC 0.3-0 https://cran.r-

project.org/web/packages/OutlierDC/in
dex.html

OutlierDM 1.1.1 https://cran.r-

project.org/web/packages/OutlierDM/in
dex.html

outliers 0.14 https://cran.r-

project.org/web/packages/outliers/index
.html

pacbpred 0.92.2 https://cran.r-

project.org/web/packages/pacbpred/ind
ex.html

parallel utils NA

parallel 3.4.1 NA

parallel CRAN NA

partitions 1.9-19 https://cran.r-

project.org/web/packages/partitions/ind
ex.html

party 1.2-3 https://cran.r-

project.org/web/packages/party/index.h
tml
PACKAGE VERSION LINK

partykit 1.1-1 https://cran.r-

project.org/web/packages/partykit/inde
x.html

PAWL 0.5 https://cran.r-

project.org/web/packages/PAWL/index.
html

pbapply 1.3-3 https://cran.r-

project.org/web/packages/pbapply/inde
x.html

pbivnorm quadprog numDeriv

pbivnorm 0.6.0 https://cran.r-

project.org/web/packages/pbivnorm/ind
ex.html

pbkrtest 0.4-7 https://cran.r-

project.org/web/packages/pbkrtest/inde
x.html

PCAmixdata 3.1 https://cran.r-

project.org/web/packages/PCAmixdata/i
ndex.html

pcaPP 1.9-72 https://cran.r-

project.org/web/packages/pcaPP/index.
html

pdc 1.0.3 https://cran.r-

project.org/web/packages/pdc/index.ht
ml

PerformanceAnalytics 1.4.3541 https://cran.r-

project.org/web/packages/Performance
Analytics/index.html

permute 0.9-4 https://cran.r-

project.org/web/packages/permute/inde
x.html

pheatmap 1.0.8 https://cran.r-

project.org/web/packages/pheatmap/in
dex.html

pixmap 0.4-11 https://cran.r-

project.org/web/packages/pixmap/index
.html
PACKAGE VERSION LINK

pkgconfig 2.0.1 https://cran.r-

project.org/web/packages/pkgconfig/in
dex.html

pkgconfig Rcpp (>= 0.12.7) CRAN

pkgmaker 0.22 https://cran.r-

project.org/web/packages/pkgmaker/in
dex.html

platetools 0.0.2 https://cran.r-

project.org/web/packages/platetools/in
dex.html

plot3D 1.1 https://cran.r-

project.org/web/packages/plot3D/index.
html

plotly 4.7.1 https://cran.r-

project.org/web/packages/plotly/index.h
tml

plotmo 3.3.4 https://cran.r-

project.org/web/packages/plotmo/index
.html

plotrix 3.6-5 https://cran.r-

project.org/web/packages/plotrix/index.
html

pls 2.6-0 https://cran.r-

project.org/web/packages/pls/index.htm
l

plyr 1.8.4 https://cran.r-

project.org/web/packages/plyr/index.ht
ml

png 0.1-7 https://cran.r-

project.org/web/packages/png/index.ht
ml

png 0.1-7 https://cran.r-

project.org/web/packages/png/index.ht
ml

polspline 1.1.12 https://cran.r-

project.org/web/packages/polspline/ind
ex.html

polyclip 1.6-1 https://cran.r-

project.org/web/packages/polyclip/index
.html
PACKAGE VERSION LINK

polynom 1.3-9 https://cran.r-

project.org/web/packages/polynom/ind
ex.html

ppcor 1.1 https://cran.r-

project.org/web/packages/ppcor/index.h
tml

prabclus 2.2-6 https://cran.r-

project.org/web/packages/prabclus/inde
x.html

pracma 2.0.7 https://cran.r-

project.org/web/packages/pracma/index
.html

praise 1.0.0 https://cran.r-

project.org/web/packages/praise/index.
html

predmixcor 1.1-1 https://cran.r-

project.org/web/packages/predmixcor/i
ndex.html

PresenceAbsence 1.1.9 https://cran.r-

project.org/web/packages/PresenceAbs
ence/index.html

pROC 1.10.0 https://cran.r-

project.org/web/packages/pROC/index.
html

prodlim 1.6.1 https://cran.r-

project.org/web/packages/prodlim/inde
x.html

profdpm 3.3 https://cran.r-

project.org/web/packages/profdpm/ind
ex.html

profileModel 0.5-9 https://cran.r-

project.org/web/packages/profileModel/
index.html

prophet 0.2 https://cran.r-

project.org/web/packages/prophet/inde
x.html

proto utils lattice

proto 1.0.0 https://cran.r-

project.org/web/packages/proto/index.h
tml
PACKAGE VERSION LINK

proxy 0.4-17 https://cran.r-

project.org/web/packages/proxy/index.h
tml

pryr 0.1.2 https://cran.r-

project.org/web/packages/pryr/index.ht
ml

pscl 1.4.9 https://cran.r-

project.org/web/packages/pscl/index.ht
ml

psych 1.7.5 https://cran.r-

project.org/web/packages/psych/index.h
tml

purrr data.table CRAN

purrr 0.2.3 https://cran.r-

project.org/web/packages/purrr/index.h
tml

pwr rlang sandwich (>= 2.3-4)

qap 0.1-1 https://cran.r-

project.org/web/packages/qap/index.ht
ml

qcc 2.7 https://cran.r-

project.org/web/packages/qcc/index.ht
ml

qdapDictionaries 1.0.6 https://cran.r-

project.org/web/packages/qdapDictiona
ries/index.html

qdapRegex 0.7.2 https://cran.r-

project.org/web/packages/qdapRegex/in
dex.html

qdapTools 1.3.3 https://cran.r-

project.org/web/packages/qdapTools/in
dex.html

qgraph 1.4.3 https://cran.r-

project.org/web/packages/qgraph/index
.html

qicharts 0.5.5 https://cran.r-

project.org/web/packages/qicharts/inde
x.html

quadprog 1.5-5 https://cran.r-

project.org/web/packages/quadprog/in
dex.html
PACKAGE VERSION LINK

qualityTools 1.55 https://cran.r-

project.org/web/packages/qualityTools/i
ndex.html

quanteda 1.0.0 https://cran.r-

project.org/web/packages/quanteda/ind
ex.html

quantmod 0.4-10 https://cran.r-

project.org/web/packages/quantmod/in
dex.html

quantreg 5.33 https://cran.r-

project.org/web/packages/quantreg/ind
ex.html

qvcalc 0.9-0 https://cran.r-

project.org/web/packages/qvcalc/index.
html

R(>= 3.0.0)

R.matlab 3.6.1 https://cran.r-

project.org/web/packages/R.matlab/ind
ex.html

R.methodsS3 1.7.1 https://cran.r-

project.org/web/packages/R.methodsS3
/index.html

R.oo 1.21.0 https://cran.r-

project.org/web/packages/R.oo/index.ht
ml

R.utils 2.5.0 https://cran.r-

project.org/web/packages/R.utils/index.
html

R.utils (>= 2.3.0) CRAN NA

R2HTML 2.3.2 https://cran.r-

project.org/web/packages/R2HTML/ind
ex.html

R2jags 0.5-7 https://cran.r-

project.org/web/packages/R2jags/index.
html

R2OpenBUGS 3.2-3.2 https://cran.r-

project.org/web/packages/R2OpenBUG
S/index.html

R2WinBUGS parallel stats

PACKAGE VERSION LINK

R2WinBUGS 2.1-21 https://cran.r-

project.org/web/packages/R2WinBUGS/i
ndex.html

R6 2.2.0 https://cran.r-
project.org/web/packages/R6/index.htm
l

R6 2.2.2 https://cran.r-
project.org/web/packages/R6/index.htm
l

ramps 0.6-14 https://cran.r-

project.org/web/packages/ramps/index.
html

RandomFields 3.1.50 https://cran.r-

project.org/web/packages/RandomField
s/index.html

RandomFieldsUtils 0.3.25 https://cran.r-

project.org/web/packages/RandomField
sUtils/index.html

randomForest 4.6-12 https://cran.r-

project.org/web/packages/randomFores
t/index.html

ranger 0.8.0 https://cran.r-

project.org/web/packages/ranger/index.
html

rappdirs 0.3.1 https://cran.r-

project.org/web/packages/rappdirs/inde
x.html

RArcInfo 0.4-12 https://cran.r-

project.org/web/packages/RArcInfo/inde
x.html

raster 2.5-8 https://cran.r-

project.org/web/packages/raster/index.h
tml

rattle 4.1.0 https://cran.r-

project.org/web/packages/rattle/index.h
tml

rbenchmark 1.0.0 https://cran.r-

project.org/web/packages/rbenchmark/i
ndex.html

Rblpapi 0.3.6 https://cran.r-

project.org/web/packages/Rblpapi/index
.html
PACKAGE VERSION LINK

rbokeh 0.5.0 https://cran.r-

project.org/web/packages/rbokeh/index.
html

rbugs 0.5-9 https://cran.r-

project.org/web/packages/rbugs/index.h
tml

RColorBrewer dplyr tibble

RColorBrewer 1.1-2 https://cran.r-

project.org/web/packages/RColorBrewer
/index.html

Rcpp CRAN NA

Rcpp 0.12.12 https://cran.r-

project.org/web/packages/Rcpp/index.ht
ml

Rcpp shiny svglite (>= 1.2.0)

RcppArmadillo 0.7.900.2.0 https://cran.r-

project.org/web/packages/RcppArmadill
o/index.html

rcppbugs 0.1.4.2 https://cran.r-

project.org/web/packages/rcppbugs/ind
ex.html

RcppEigen 0.3.3.3.0 https://cran.r-

project.org/web/packages/RcppEigen/in
dex.html

RcppExamples 0.1.8 https://cran.r-

project.org/web/packages/RcppExample
s/index.html

RcppParallel 4.3.20 https://cran.r-

project.org/web/packages/RcppParallel/i
ndex.html

RCurl 1.95-4.8 https://cran.r-

project.org/web/packages/RCurl/index.h
tml

readr methods utils

readr 1.1.1 https://cran.r-

project.org/web/packages/readr/index.h
tml

readxl 1.0.0 https://cran.r-

project.org/web/packages/readxl/index.
html
PACKAGE VERSION LINK

Redmonder 0.2.0 https://cran.r-

project.org/web/packages/Redmonder/i
ndex.html

registry 0.3 https://cran.r-

project.org/web/packages/registry/index
.html

relaimpo 2.2-2 https://cran.r-

project.org/web/packages/relaimpo/ind
ex.html

relimp 1.0-5 https://cran.r-

project.org/web/packages/relimp/index.
html

rematch 1.0.1 https://cran.r-

project.org/web/packages/rematch/inde
x.html

Renext 3.1-0 https://cran.r-

project.org/web/packages/Renext/index.
html

reports 0.1.4 https://cran.r-

project.org/web/packages/reports/index
.html

reshape 0.8.6 https://cran.r-

project.org/web/packages/reshape/inde
x.html

reshape2 stats stats4

reshape2 scales (>= 0.4.1) stats

reshape2 1.4.2 https://cran.r-

project.org/web/packages/reshape2/ind
ex.html

RevoIOQ 8.0.8 NA

RevoMods 11.0.0 NA

RevoUtils 10.0.6 NA

RevoUtilsMath 10.0.1 NA
PACKAGE VERSION LINK

rex 1.1.1 https://cran.r-

project.org/web/packages/rex/index.htm
l

rFerns 2.0.2 https://cran.r-

project.org/web/packages/rFerns/index.
html

rgdal 1.2-15 https://cran.r-

project.org/web/packages/rgdal/index.h
tml

rgeos 0.3-23 https://cran.r-

project.org/web/packages/rgeos/index.h
tml

rgexf 0.15.3 https://cran.r-

project.org/web/packages/rgexf/index.ht
ml

rgl 0.98.1 https://cran.r-

project.org/web/packages/rgl/index.htm
l

RgoogleMaps 1.4.1 https://cran.r-

project.org/web/packages/RgoogleMap
s/index.html

RGraphics 2.0-14 https://cran.r-

project.org/web/packages/RGraphics/in
dex.html

RGtk2 2.20.33 https://cran.r-

project.org/web/packages/RGtk2/index.
html

RInside 0.2.14 https://cran.r-

project.org/web/packages/RInside/index
.html

RJaCGH 2.0.4 https://cran.r-

project.org/web/packages/RJaCGH/inde
x.html

rjags 4-6 https://cran.r-

project.org/web/packages/rjags/index.ht
ml

rjson 0.2.15 https://cran.r-

project.org/web/packages/rjson/index.ht
ml

RJSONIO 1.3-0 https://cran.r-

project.org/web/packages/RJSONIO/ind
ex.html
PACKAGE VERSION LINK

rlang 0.1.2 https://cran.r-

project.org/web/packages/rlang/index.h
tml

rlang scales sjlabelled (>= 1.0.1)

rlecuyer 0.3-4 https://cran.r-

project.org/web/packages/rlecuyer/inde
x.html

rlist 0.4.6.1 https://cran.r-

project.org/web/packages/rlist/index.ht
ml

rmarkdown 1.6 https://cran.r-

project.org/web/packages/rmarkdown/i
ndex.html

Rmpfr 0.6-1 https://cran.r-

project.org/web/packages/Rmpfr/index.
html

rms 5.1-1 https://cran.r-

project.org/web/packages/rms/index.ht
ml

RMySQL 0.10.12 https://cran.r-

project.org/web/packages/RMySQL/ind
ex.html

rngtools 1.2.4 https://cran.r-

project.org/web/packages/rngtools/inde
x.html

rngtools (>= 1.2.3) cluster graphics

robCompositions 2.0.5 https://cran.r-

project.org/web/packages/robCompositi
ons/index.html

robustbase 0.92-7 https://cran.r-

project.org/web/packages/robustbase/i
ndex.html

ROCR 1.0-7 https://cran.r-

project.org/web/packages/ROCR/index.
html

RODBC 1.3-15 https://cran.r-

project.org/web/packages/RODBC/index
.html

RODBC 1.3-15 https://cran.r-

project.org/web/packages/RODBC/index
.html
PACKAGE VERSION LINK

Rook 1.1-1 https://cran.r-

project.org/web/packages/Rook/index.h
tml

rootSolve 1.7 https://cran.r-

project.org/web/packages/rootSolve/ind
ex.html

roxygen2 6.0.1 https://cran.r-

project.org/web/packages/roxygen2/ind
ex.html

rpart 4.1-11 https://cran.r-

project.org/web/packages/rpart/index.ht
ml

rpart.plot 2.1.2 https://cran.r-

project.org/web/packages/rpart.plot/ind
ex.html

rpivotTable 0.2.0 https://cran.r-

project.org/web/packages/rpivotTable/in
dex.html

rprojroot methods stringr (>= 1.2.0)

rprojroot 1.2 https://cran.r-

project.org/web/packages/rprojroot/ind
ex.html

rrcov 1.4-3 https://cran.r-

project.org/web/packages/rrcov/index.h
tml

rscproxy 2.0-5 https://cran.r-

project.org/web/packages/rscproxy/inde
x.html

rsdmx 0.5-9 https://cran.r-

project.org/web/packages/rsdmx/index.
html

RSGHB 1.1.2 https://cran.r-

project.org/web/packages/RSGHB/index.
html

RSiteCatalyst 1.4.13 https://cran.r-

project.org/web/packages/RSiteCatalyst
/index.html

RSNNS 0.4-9 https://cran.r-

project.org/web/packages/RSNNS/index.
html
PACKAGE VERSION LINK

Rsolnp 1.16 https://cran.r-

project.org/web/packages/Rsolnp/index.
html

RSQLite 2 https://cran.r-
project.org/web/packages/RSQLite/inde
x.html

rstan 2.16.2 https://cran.r-

project.org/web/packages/rstan/index.h
tml

rstudioapi 0.6 https://cran.r-

project.org/web/packages/rstudioapi/in
dex.html

RTextTools 1.4.2 https://cran.r-

project.org/web/packages/RTextTools/in
dex.html

RUnit 0.4.26 https://cran.r-

project.org/web/packages/RUnit/index.h
tml

RUnit 0.4.31 https://cran.r-

project.org/web/packages/RUnit/index.h
tml

runjags 2.0.4-2 https://cran.r-

project.org/web/packages/runjags/index
.html

Runuran 0.23.0 https://cran.r-

project.org/web/packages/Runuran/inde
x.html

rvest 0.3.2 https://cran.r-

project.org/web/packages/rvest/index.ht
ml

rworldmap 1.3-6 https://cran.r-

project.org/web/packages/rworldmap/in
dex.html

rworldxtra 1.01 https://cran.r-

project.org/web/packages/rworldxtra/in
dex.html

SampleSizeMeans 1.1 https://cran.r-

project.org/web/packages/SampleSizeM
eans/index.html

SampleSizeProportions 1 https://cran.r-
project.org/web/packages/SampleSizePr
oportions/index.html
PACKAGE VERSION LINK

sandwich 2.4-0 https://cran.r-

project.org/web/packages/sandwich/ind
ex.html

sas7bdat 0.5 https://cran.r-

project.org/web/packages/sas7bdat/ind
ex.html

sbgcop 0.975 https://cran.r-

project.org/web/packages/sbgcop/index
.html

scales 0.4.1 https://cran.r-

project.org/web/packages/scales/index.h
tml

scales CRAN NA

scales utils Matrix

scatterplot3d 0.3-40 https://cran.r-

project.org/web/packages/scatterplot3d
/index.html

sciplot 1.1-1 https://cran.r-

project.org/web/packages/sciplot/index.
html

segmented 0.5-2.1 https://cran.r-

project.org/web/packages/segmented/i
ndex.html

selectr 0.3-1 https://cran.r-

project.org/web/packages/selectr/index.
html

sem 3.1-9 https://cran.r-

project.org/web/packages/sem/index.ht
ml

seriation 1.2-2 https://cran.r-

project.org/web/packages/seriation/inde
x.html

setRNG 2013.9-1 https://cran.r-

project.org/web/packages/setRNG/index
.html

setRNG (>= 2004.4-1) CRAN NA

sf 0.5-5 https://cran.r-
project.org/web/packages/sf/index.html
PACKAGE VERSION LINK

sfsmisc 1.1-1 https://cran.r-

project.org/web/packages/sfsmisc/index.
html

sgeostat 1.0-27 https://cran.r-

project.org/web/packages/sgeostat/inde
x.html

shape 1.4.2 https://cran.r-

project.org/web/packages/shape/index.
html

shapefiles 0.7 https://cran.r-

project.org/web/packages/shapefiles/ind
ex.html

shiny 1.0.3 https://cran.r-

project.org/web/packages/shiny/index.h
tml

showtext 0.4-6 https://cran.r-

project.org/web/packages/showtext/ind
ex.html

showtextdb 1 https://cran.r-
project.org/web/packages/showtextdb/i
ndex.html

SIS 0.8-4 https://cran.r-

project.org/web/packages/SIS/index.htm
l

SixSigma 0.9-4 https://cran.r-

project.org/web/packages/SixSigma/ind
ex.html

sjmisc 2.6.0 https://cran.r-

project.org/web/packages/sjmisc/index.
html

sjPlot 2.3.2 https://cran.r-

project.org/web/packages/sjPlot/index.h
tml

sjstats 0.10.3 https://cran.r-

project.org/web/packages/sjstats/index.
html

sjstats (>= 0.10.3) tibble (>= 1.3.3) tidyr (>= 0.6.1)

skmeans 0.2-10 https://cran.r-

project.org/web/packages/skmeans/ind
ex.html
PACKAGE VERSION LINK

slam 0.1-40 https://cran.r-

project.org/web/packages/slam/index.ht
ml

sm 2.2-5.4 https://cran.r-
project.org/web/packages/sm/index.htm
l

smoothSurv 1.6 https://cran.r-

project.org/web/packages/smoothSurv/i
ndex.html

sna 2.4 https://cran.r-

project.org/web/packages/sna/index.ht
ml

snow 0.4-2 https://cran.r-

project.org/web/packages/snow/index.h
tml

SnowballC 0.5.1 https://cran.r-

project.org/web/packages/SnowballC/in
dex.html

snowFT 1.6-0 https://cran.r-

project.org/web/packages/snowFT/index
.html

sp 1.2-5 https://cran.r-
project.org/web/packages/sp/index.html

spacetime 1.2-0 https://cran.r-

project.org/web/packages/spacetime/in
dex.html

spacetime (>= 1.0-0) FNN CRAN

spacyr 0.9.3 https://cran.r-

project.org/web/packages/spacyr/index.
html

spam 2.1-1 https://cran.r-

project.org/web/packages/spam/index.h
tml

SparseM 1.77 https://cran.r-

project.org/web/packages/SparseM/ind
ex.html

spatial 7.3-11 https://cran.r-

project.org/web/packages/spatial/index.
html
PACKAGE VERSION LINK

spatial 7.3-11 https://cran.r-

project.org/web/packages/spatial/index.
html

spatstat 1.51-0 https://cran.r-

project.org/web/packages/spatstat/inde
x.html

spBayes 0.4-1 https://cran.r-

project.org/web/packages/spBayes/inde
x.html

spdep 0.6-13 https://cran.r-

project.org/web/packages/spdep/index.
html

spikeslab 1.1.5 https://cran.r-

project.org/web/packages/spikeslab/ind
ex.html

splancs 2.01-40 https://cran.r-

project.org/web/packages/splancs/index
.html

splines 3.4.1 NA

spls 2.2-1 https://cran.r-

project.org/web/packages/spls/index.ht
ml

splus2R 1.2-2 https://cran.r-

project.org/web/packages/splus2R/inde
x.html

spTimer 2.0-1 https://cran.r-

project.org/web/packages/spTimer/inde
x.html

sqldf 0.4-11 https://cran.r-

project.org/web/packages/sqldf/index.ht
ml

sROC 0.1-2 https://cran.r-

project.org/web/packages/sROC/index.h
tml

stabledist 0.7-1 https://cran.r-

project.org/web/packages/stabledist/ind
ex.html

stabs 0.6-3 https://cran.r-

project.org/web/packages/stabs/index.h
tml
PACKAGE VERSION LINK

StanHeaders 2.16.0-1 https://cran.r-

project.org/web/packages/StanHeaders/
index.html

statmod 1.4.30 https://cran.r-

project.org/web/packages/statmod/inde
x.html

statnet.common 4.0.0 https://cran.r-

project.org/web/packages/statnet.com
mon/index.html

stats 3.4.1 NA

stats utils CRAN

stats survival utils

stats4 3.4.1 NA

stepPlr 0.92 https://cran.r-

project.org/web/packages/stepPlr/index.
html

stochvol 1.3.2 https://cran.r-

project.org/web/packages/stochvol/inde
x.html

stopwords CRAN NA

stopwords 0.9.0 https://cran.r-

project.org/web/packages/stopwords/in
dex.html

stringdist 0.9.4.6 https://cran.r-

project.org/web/packages/stringdist/ind
ex.html

stringdist (>= 0.9.4) stringr (>= 1.2.0) tibble (>= 1.3.3)

stringi CRAN NA

stringi 1.1.5 https://cran.r-

project.org/web/packages/stringi/index.
html

stringr CRAN NA

stringr 1.2.0 https://cran.r-

project.org/web/packages/stringr/index.
html
PACKAGE VERSION LINK

strucchange 1.5-1 https://cran.r-

project.org/web/packages/strucchange/i
ndex.html

stsm 1.9 https://cran.r-

project.org/web/packages/stsm/index.ht
ml

stsm.class 1.3 https://cran.r-

project.org/web/packages/stsm.class/in
dex.html

SuppDists 1.1-9.4 https://cran.r-

project.org/web/packages/SuppDists/in
dex.html

survey 3.32-1 https://cran.r-

project.org/web/packages/survey/index.
html

survival 2.41-3 https://cran.r-

project.org/web/packages/survival/index
.html

survival 2.41-3 https://cran.r-

project.org/web/packages/survival/index
.html

survival stats broom

survminer 0.4.0 https://cran.r-

project.org/web/packages/survminer/in
dex.html

survMisc 0.5.4 https://cran.r-

project.org/web/packages/survMisc/ind
ex.html

svglite 1.2.1 https://cran.r-

project.org/web/packages/svglite/index.
html

svmpath 0.955 https://cran.r-

project.org/web/packages/svmpath/ind
ex.html

svUnit 0.7-12 https://cran.r-

project.org/web/packages/svUnit/index.
html

sysfonts 0.6 https://cran.r-

project.org/web/packages/sysfonts/inde
x.html
PACKAGE VERSION LINK

tau 0.0-19 https://cran.r-

project.org/web/packages/tau/index.ht
ml

tcltk 3.4.1 NA

tcltk2 1.2-11 https://cran.r-

project.org/web/packages/tcltk2/index.h
tml

TeachingDemos 2.1 https://cran.r-

project.org/web/packages/TeachingDem
os/index.html

tensor 1.5 https://cran.r-

project.org/web/packages/tensor/index.
html

tensorA 0.36 https://cran.r-

project.org/web/packages/tensorA/inde
x.html

testthat 1.0.2 https://cran.r-

project.org/web/packages/testthat/inde
x.html

textcat 1.0-5 https://cran.r-

project.org/web/packages/textcat/index.
html

textir 2.0-4 https://cran.r-

project.org/web/packages/textir/index.h
tml

tfplot 2015.12-1 https://cran.r-

project.org/web/packages/tfplot/index.h
tml

tframe 2015.12-1 https://cran.r-

project.org/web/packages/tframe/index.
html

tgp 2.4-14 https://cran.r-

project.org/web/packages/tgp/index.ht
ml

TH.data 1.0-8 https://cran.r-

project.org/web/packages/TH.data/inde
x.html

TH.data (>= 1.0-2) sandwich (>= 2.3-0) codetools

threejs 0.2.2 https://cran.r-

project.org/web/packages/threejs/index.
html
PACKAGE VERSION LINK

tibble CRAN NA

tibble 1.3.3 https://cran.r-

project.org/web/packages/tibble/index.h
tml

tibble rvest tidyr

tibble (>= 1.1) stringr broom

tibble (>= 1.3.1) utils CRAN

tidycensus 0.3.1 https://cran.r-

project.org/web/packages/tidycensus/in
dex.html

tidyr rappdirs readr

tidyr 0.6.3 https://cran.r-

project.org/web/packages/tidyr/index.ht
ml

tidyr (>= 0.6.2) CRAN NA

tidytext 0.1.4 https://cran.r-

project.org/web/packages/tidytext/index
.html

tidyverse 1.1.1 https://cran.r-

project.org/web/packages/tidyverse/ind
ex.html

tiff 0.1-5 https://cran.r-

project.org/web/packages/tiff/index.htm
l

tigris 0.5.3 https://cran.r-

project.org/web/packages/tigris/index.ht
ml

timeDate 3012.1 https://cran.r-

project.org/web/packages/timeDate/ind
ex.html

timeDate (>= 2150.95) NA CRAN

timeSeries 3022.101.2 https://cran.r-

project.org/web/packages/timeSeries/in
dex.html

timevis 0.4 https://cran.r-

project.org/web/packages/timevis/index.
html
PACKAGE VERSION LINK

tm 0.7-1 https://cran.r-
project.org/web/packages/tm/index.htm
l

tokenizers 0.1.4 https://cran.r-

project.org/web/packages/tokenizers/in
dex.html

tools 3.4.1 NA

topicmodels 0.2-6 https://cran.r-

project.org/web/packages/topicmodels/i
ndex.html

TraMineR 2.0-7 https://cran.r-

project.org/web/packages/TraMineR/ind
ex.html

translations 3.4.1 NA

tree 1.0-37 https://cran.r-

project.org/web/packages/tree/index.ht
ml

treemap 2.4-2 https://cran.r-

project.org/web/packages/treemap/inde
x.html

trimcluster 0.1-2 https://cran.r-

project.org/web/packages/trimcluster/in
dex.html

truncnorm 1.0-7 https://cran.r-

project.org/web/packages/truncnorm/in
dex.html

TSA 1.01 https://cran.r-

project.org/web/packages/TSA/index.ht
ml

tseries 0.10-42 https://cran.r-

project.org/web/packages/tseries/index.
html

tsfa 2014.10-1 https://cran.r-

project.org/web/packages/tsfa/index.ht
ml

tsintermittent 1.9 https://cran.r-

project.org/web/packages/tsintermitten
t/index.html

tsoutliers 0.6-6 https://cran.r-

project.org/web/packages/tsoutliers/ind
ex.html
PACKAGE VERSION LINK

TSP 1.1-5 https://cran.r-

project.org/web/packages/TSP/index.ht
ml

TTR 0.23-2 https://cran.r-

project.org/web/packages/TTR/index.ht
ml

tweenr 0.1.5 https://cran.r-

project.org/web/packages/tweenr/index.
html

twitteR 1.1.9 https://cran.r-

project.org/web/packages/twitteR/index.
html

udunits2 0.13 https://cran.r-

project.org/web/packages/udunits2/ind
ex.html

units 0.4-6 https://cran.r-

project.org/web/packages/units/index.ht
ml

UpSetR 1.3.3 https://cran.r-

project.org/web/packages/UpSetR/index
.html

urca 1.3-0 https://cran.r-

project.org/web/packages/urca/index.ht
ml

useful 1.2.3 https://cran.r-

project.org/web/packages/useful/index.
html

UsingR 2.0-5 https://cran.r-

project.org/web/packages/UsingR/index.
html

utils NA NA

utils 3.4.1 NA

utils stats graphics

uuid 0.1-2 https://cran.r-

project.org/web/packages/uuid/index.ht
ml

vars 1.5-2 https://cran.r-

project.org/web/packages/vars/index.ht
ml
PACKAGE VERSION LINK

vcd 1.4-3 https://cran.r-

project.org/web/packages/vcd/index.ht
ml

vcd MASS nnet

vdiffr 0.2.1 https://cran.r-

project.org/web/packages/vdiffr/index.h
tml

vegan 2.4-3 https://cran.r-

project.org/web/packages/vegan/index.
html

VennDiagram 1.6.17 https://cran.r-

project.org/web/packages/VennDiagra
m/index.html

VGAM 1.0-4 https://cran.r-

project.org/web/packages/VGAM/index.
html

VIF 1 https://cran.r-
project.org/web/packages/VIF/index.ht
ml

VIM 4.7.0 https://cran.r-

project.org/web/packages/VIM/index.ht
ml

vioplot 0.2 153

viridis 0.4.0 https://cran.r-

project.org/web/packages/viridis/index.h
tml

viridisLite 0.2.0 https://cran.r-

project.org/web/packages/viridisLite/ind
ex.html

visNetwork 2.0.1 https://cran.r-

project.org/web/packages/visNetwork/i
ndex.html

webutils 0.6 https://cran.r-

project.org/web/packages/webutils/inde
x.html

weights 0.85 https://cran.r-

project.org/web/packages/weights/inde
x.html

whisker viridis CRAN

whisker digest rstudioapi (>= 0.2.0)

PACKAGE VERSION LINK

whisker 0.3-2 https://cran.r-

project.org/web/packages/whisker/index
.html

withr 2.0.0 https://cran.r-

project.org/web/packages/withr/index.h
tml

wmtsa 2.0-2 https://cran.r-

project.org/web/packages/wmtsa/index.
html

wordcloud 2.5 https://cran.r-

project.org/web/packages/wordcloud/in
dex.html

wordcloud2 0.2.0 https://cran.r-

project.org/web/packages/wordcloud2/i
ndex.html

xgboost 0.6-4 https://cran.r-

project.org/web/packages/xgboost/inde
x.html

XML 3.98-1.9 https://cran.r-

project.org/web/packages/XML/index.ht
ml

xml2 1.1.1 https://cran.r-

project.org/web/packages/xml2/index.ht
ml

xtable digest htmltools (>= 0.3.5)

xtable 1.8-2 https://cran.r-

project.org/web/packages/xtable/index.
html

xts 0.10-0 https://cran.r-

project.org/web/packages/xts/index.htm
l

xts (>= 0.10-0) zoo (>= 1.8-0) broom (>= 0.4.2)

yaml methods tools

yaml 2.1.14 https://cran.r-

project.org/web/packages/yaml/index.ht
ml

yarrr 0.1.5 https://cran.r-

project.org/web/packages/yarrr/index.ht
ml
 PACKAGE VERSION LINK

zic 0.9 https://cran.r-

project.org/web/packages/zic/index.html

zipfR 0.6-6 https://cran.r-

project.org/web/packages/zipfR/index.ht
ml

zoo timeDate CRAN

zoo 1.8-0 https://cran.r-

project.org/web/packages/zoo/index.ht
ml

R scripts that are not supported in Power BI

The following table shows which packages are not supported in the Power BI service.

PACKAGE REQUEST DATE REASON

RgoogleMaps 10/05/2016 Networking is blocked

mailR 10/03/2016 Networking is blocked

RevoScaleR 8/30/2016 ships only with Microsoft R Server

Next steps
For more information about R in Power BI, take a look at the following articles:
Creating R visuals in the Power BI service
Create Power BI visuals using R
Running R scripts in Power BI Desktop
Using R in Query Editor
 Enter data directly into Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

With Power BI Desktop, you can enter data directly and use that data in your reports and visualizations. For
example, you can copy portions of a workbook or web page, then paste it into Power BI Desktop.
To enter data directly, select Enter Data from the Home ribbon.

Power BI Desktop may attempt to make minor transformations on the data, if appropriate, just like it does when
you load data from any source. For example, in the following case it promoted the first row of data to headers.

If you want to shape the data you entered (or pasted), you can select the Edit button to bring up Query Editor,
where you can shape and transform the data before bringing it into Power BI Desktop. Or you can select the
Load button to import the data as it appears.
When you select Load, Power BI Desktop creates a new table from your data, and makes it available in the
Fields pane. In the following image, Power BI Desktop shows my new table, called Table1 by default, and the
two fields within that table that were created.

And that’s it – it’s that easy to enter data into Power BI Desktop.
You’re now ready to use the data in Power BI Desktop to create visuals, reports, or interact with any other data
you might want to connect with and import, such as Excel workbooks, databases, or any other data source.

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources,
check out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Connect to CSV files in Power BI Desktop
 Connect to Excel in Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

Connecting to an Excel workbook from Power BI Desktop is straightforward, and this article walks you through
the steps.
In Power BI Desktop, select Get Data > Excel from the Home ribbon.

Select your workbook from the Open dialog that appears.

Power BI Desktop presents the tables on other data elements from the workbook in the Navigator window.
When you select a table in the left pane, a preview of the data appears in the right pane.

You can select the Load button to import the data, or if you want to edit the data using Query Editor before
bringing it into Power BI Desktop, select the Edit button.
When you load the data, Power BI Desktop displays the Load window and displays the activity associated with
loading the data.

When complete, Power BI Desktop displays the tables and fields it imported from your Excel workbook in the
Fields pane, on the right side of the Desktop.
And that’s it!
You’re now ready to use the imported data from your Excel workbook in Power BI Desktop to create visuals,
reports, or interact with any other data you might want to connect with and import, such as other Excel
workbooks, databases, or any other data source.

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources,
check out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to CSV files in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to SSAS Multidimensional Models in Power
BI Desktop
2/13/2019 • 5 minutes to read • Edit Online

With Power BI Desktop, you can access SSAS Multidimensional models, commonly referred to as SSAS MD.
To connect to an SSAS MD database, select Get Data > Database > SQL Server Analysis Services Database
as shown in the following image:

SSAS Multidimensional models in Live connection mode are supported in both the Power BI service and in
Power BI Desktop. You can also publish and upload reports that use SSAS Multidimensional models in Live
mode to the Power BI service.

Capabilities and features of SSAS MD

The following sections describe features and capabilities of Power BI and SSAS MD connections.
Tabular metadata of multidimensional models
The following table shows the correspondence between multidimensional objects and the tabular metadata that's
returned to Power BI Desktop. Power BI queries the model for tabular metadata, and based on the returned
metadata, runs appropriate DAX queries against Analysis Services when you create a visualization such as a table,
matrix, chart, or slicer.
 BISM-MULTIDIMENTIONAL OBJECT TABULAR METADATA

Cube Model

Cube dimension Table

Dimension attributes (Keys), Name Columns

Measure group Table

Measure Measure

Measures without associated Measure Group Within table called Measures

Measure group -> Cube dimension relationship Relationship

Perspective Perspective

KPI KPI

User/Parent-Child hierarchies Hierarchies

Measures, measure groups, and KPIs

Measure groups in a multidimensional cube are exposed in Power BI as tables with the ∑ sign beside them in the
Fields pane. Calculated measures that don't have an associated measure group are grouped under a special table
called Measures in the tabular metadata.
In a multidimensional model, you can define a set of measures or KPIs in a cube to be located within a Display
folder, which can help simplify complex models. Power BI recognizes Display folders in tabular metadata, and
shows measures and KPIs within the Display folders. KPIs in multidimensional databases support Value, Goal,
Status Graphic, and Trend Graphic.
Dimension attribute type
Multidimensional models also support associating dimension attributes with specific dimension attribute types.
For example, a Geography dimension where the City, State-Province, Country, and Postal Code dimension
attributes have appropriate geography types associated with them are exposed in the tabular metadata. Power BI
recognizes the metadata, enabling you to create map visualizations. You'll recognize these associations by the map
icon next to element in the Field pane in Power BI.
Power BI can also render images when you provide a field containing URLs (Uniform Resource Locator) of the
images. You can specify these fields as ImageURL type in SQL Server Data Tools (or subsequently in Power BI),
and its type information is provided to Power BI in the tabular metadata. Power BI can then retrieve those images
from the URL, and display them in visuals.
Parent-child hierarchies
Multidimensional models support Parent-child hierarchies, which are presented as a hierarchy in the tabular
metadata. Each level of the Parent-child hierarchy is exposed as a hidden column in the tabular metadata. The key
attribute of the Parent-child dimension is not exposed in the tabular metadata.
Dimension calculated members
Multidimensional models support creation of various types of calculated members. The two most common types
of calculated members are the following:
 Calculated members on attribute hierarchies and not sibling of All
Calculated members on user hierarchies
Multidimensional models expose calculated members on attribute hierarchies as values of a column. There are a
few additional options and constraints while exposing this type of calculated member:
Dimension attribute can have an optional UnknownMember
An attribute containing calculated members cannot be the key attribute of the dimension, unless it is the only
attribute of the dimension
An attribute containing calculated members cannot be a parent-child attribute
The calculated members of user hierarchies are not exposed in Power BI. Rather, you will be able to connect to a
cube containing calculated members on user hierarchies, but you won't be able to see calculated members if they
do not meet the constraints mentioned in the previous bulleted list.
Security
Multidimensional models support dimension and cell level security by way of Roles. When you connect to a cube
with Power BI, you are authenticated and evaluated for appropriate permissions. When a user has dimension
security applied, the respective dimension members are not seen by the user in Power BI. However, when a user
has a cell security permission defined, where certain cells are restricted, then that user cannot connect to the cube
using Power BI.

Considerations and Limitations

There are certain limitations to using SSAS MD:
Servers must be running SQL Server 2012 SP1 CU4 or later versions of Analysis Services for the Power BI
Desktop SSAS MD connector to work properly
Actions and Named Sets are not exposed to Power BI, but you can still connect to cubes that also contain
Actions or Named sets and create visuals and reports.
You may encounter an issue where Power BI displays metadata for an SSAS model, but you're unable to
retrieve data from the model. This can occur when you have the 32-bit version of the MSOLAP provider
installed on your system, and do not have the 64-bit version. Installing the 64-bit version may resolve the issue.
You can't create 'report level' measures when authoring a report that is connected live to an SSAS
multidimensional model. The only measures that are available are those defined in the MD model.

Supported Features of SSAS MD in Power BI Desktop

The following features of SSAS MD are supported in Power BI Desktop:
Consumption of the following elements are supported in this release of SSAS MD (you can get more
information about these features):
Display folders
KPI Trends
Default Members
Dimension Attributes
Dimension Calculated Members (must be a single real member when the dimension has more than one
attribute, it cannot be the key attribute of the dimension unless it is the only attribute, and it cannot be a
parent-child attribute)
Dimension Attribute types
Hierarchies
Measures (with or without Measure groups)
Measures as Variant
 KPIs
ImageUrls
Dimension security

Troubleshooting
The following list describes all known issues when connecting to SQL Server Analysis Services (SSAS ).
Error : Couldn't load model schema - This error usually occurs when the user connecting to Analysis
Services does not have access to database/cube.
 Connect to CSV files in Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

Connecting to a comma-separated value (CSV ) file from Power BI Desktop is a lot like connecting to an Excel
workbook. Both are easy, and this article steps you through how to connect to any CSV file to which you have
access.
To start with, from Power BI Desktop select Get Data > CSV from the Home ribbon.

Select your CSV file from the Open dialog that appears.
When you select Open, Power BI Desktop accesses the file and determines certain file attributes, such as the file
origin, delimiter type, and how many rows should be used to detect the data types in the file.
These file attributes and options are shown in the drop-down selections at the top of the CSV import dialog
window, shown below. You can change any of these detected settings manually, by choosing another option from
any of the drop-down selectors.

When you’re satisfied with the selections, you can select Load to import the file into Power BI Desktop, or you can
select Edit to open Query Editor and further shape or transform the data before importing it.
Once you load the data into Power BI Desktop, you see the table and its columns (which are presented as Fields in
Power BI Desktop) in the Fields pane, along the right of the Report view in Power BI Desktop.
That’s all you have to do – the data from your CSV file is now in Power BI Desktop.
You can use that data in Power BI Desktop to create visuals, reports, or interact with any other data you might
want to connect with and import, such as Excel workbooks, databases, or any other data source.

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources,
check out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to a Google BigQuery database in Power BI
Desktop
1/14/2019 • 2 minutes to read • Edit Online

In Power BI Desktop, you can connect to a Google BigQuery database and use the underlying data just like any
other data source in Power BI Desktop.

Connect to Google BigQuery

To connect to a Google BigQuery database select Get Data from the Home ribbon in Power BI Desktop. Select
Database from the categories on the left, and you see Google BigQuery.

In the Google BigQuery window that appears, sign in to your Google BigQuery account and select Connect.
When you're signed in, you see the following window indicated you've been authenticated.

Once you successfully connect, a Navigator window appears and displays the data available on the server, from
which you can select one or multiple elements to import and use in Power BI Desktop.
Considerations and Limitations
There are a few limits and considerations to keep in mind with the Google BigQuery connector:
The Google BigQuery connector is available in Power BI Desktop and in the Power BI service. In the Power BI
service, the connector can be accessed using the Cloud-to-Cloud connection from Power BI to Google
BigQuery.
You can use Power BI with the Google BigQuery Billing Project. By default, Power BI uses the first project from
the list returned for the user. To customize the behavior of the Billing Project when using it with Power BI, take the
following steps:
Specifying the following option in the underlying M in the Source step, which can be customized by using
Power Query Editor in Power BI Desktop:
Source = GoogleBigQuery.Database([BillingProject="Include-Billing-Project-Id-Here"])

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources,
check out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to an Impala database in Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

In Power BI Desktop, you can connect to an Impala database and use the underlying data just like you can with
any other data source in Power BI Desktop.

Connect to an Impala database

To connect to an Impala database, take the following steps:
1. Select Get Data from the Home ribbon in Power BI Desktop.
2. Select Database from the categories on the left. Then you see Impala.

3. In the Impala window that appears, type or paste the name of your Impala server into the box. Then select
OK. You can Import data directly into Power BI or you can use DirectQuery. Learn more about using
DirectQuery.
4. When prompted, enter your credentials or connect anonymously. The Impala connector supports
Anonymous, Basic (user name + password), and Windows authentication.

NOTE
After you put in your user name and password for a particular Impala server, Power BI Desktop uses those same
credentials in subsequent connection attempts. You can modify those credentials by going to File > Options and
settings > Data source settings.

5. After you connect, a Navigator window appears and displays the data that's available on the server.
Choose elements from this data to import and use in Power BI Desktop.
Considerations and limitations
There are a few limitations and considerations to keep in mind with the Impala connector:
The Impala connector is supported on the on-premises data gateway, using any of the three supported
authentication mechanisms.

Next steps
There are many different data sources that you can connect to by using Power BI Desktop. For more information
about data sources, check out the following resources:
What is Power BI Desktop?
Data sources in Power BI Desktop
Shape and combine data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to OData feeds in Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

In Power BI Desktop, you can connect to an OData feed and use the underlying data just like any other data
source in Power BI Desktop.
To connect to an OData feed, select Get Data > OData Feed from the Home ribbon in Power BI Desktop.

In the OData Feed window that appears, type or paste your OData feed URL into the box, and select OK.

Power BI Desktop connects to the OData feed, and displays the available tables and other data elements in the
Navigator window. When you select an element, the right pane of the Navigator window displays a preview of
the data. You can select as many tables as you want to import. The Navigator window shows a preview of the
currently selected table.
You can choose the Edit button, which launches Query Editor, where you can shape and transform the data from
the OData feed before importing it into Power BI Desktop. Or you can select the Load button, and import all of the
data elements you selected in the left pane.
When we select Load, Power BI Desktop imports the selected items, and displays a Load window of the import
progress.

Once complete, Power BI Desktop makes the selected tables and other data elements available in the Fields pane,
found on the right side of the Reports view in Power BI Desktop.
And that’s it!
You’re now ready to use the imported data from the OData feed in Power BI Desktop to create visuals, reports, or
interact with any other data you might want to connect with and import, such as other Excel workbooks, databases,
or any other data source.

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources,
check out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to Amazon Redshift in Power BI Desktop
2/13/2019 • 2 minutes to read • Edit Online

In Power BI Desktop, you can connect to an Amazon Redshift database and use the underlying data just like
any other data source in Power BI Desktop.

Connect to an Amazon Redshift database

To connect to an Amazon Redshift database, select Get Data from the Home ribbon in Power BI Desktop. Select
Database from the categories on the left, and you see Amazon Redshift.

In the Amazon Redshift window that appears, type or paste the name of your Amazon Redshift server and
database into the box. As part of the Server field, users can specify a port in the following format: ServerURL:Port
When prompted, put in your username and password. You should use the server name that precisely matches the
SSL certificate to avoid errors.

Once you successfully connect, a Navigator window appears and displays the data available on the server, from
which you can select one or multiple elements to import and use in Power BI Desktop.

Once you make selections from the Navigator window, you can either Load or Edit the data.
 If you choose to Load data, you'll be prompted to use either Import or DirectQuery mode to load the data. For
more information, check out this article that explains DirectQuery.
If you select to Edit the data, Query Editor appears where you can apply all sorts of transformations and filters
to the data, many of which are applied to the underlying Amazon Redshift database itself (if supported).

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources,
check out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to a web page from Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

You can connect to a web page, and import its data into Power BI Desktop, to use in your visuals and in your data
models.
In Power BI Desktop, select Get Data > Web from the Home ribbon.

A dialog appears, asking for the URL of the web page from which you want to import data.

Once you’ve typed in (or pasted) the URL, select OK. Power BI Desktop connects to that page, then presents the
page’s available data in the Navigator window. When you select one of the available data elements, such as a
table of the entire page, the Navigator window displays a preview of that data on the right side of the window.
You can choose the Edit button, which launches Query Editor, where you can shape and transform the data on
that Web page before importing it into Power BI Desktop. Or you can select the Load button, and import all of the
data elements you selected in the left pane.
When we select Load, Power BI Desktop imports the selected items, and makes them available in the Fields pane,
found on the right side of the Reports view in Power BI Desktop.
That’s all there is to connecting to a web page and bringing its data into Power BI Desktop.
From there, you can drag those fields onto the Report canvas and create all the visualizations you want. You can
also use the data from that Web page just like you would any other data – you can shape it, you can create
relationships between it and other data sources in your model, and otherwise do what you’d like to create the
Power BI report you want.
To see connecting to a Web page in more depth and action, take a look at the Power BI Desktop Getting Started
Guide.

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources,
check out the following resources:
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Connect to CSV files in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to Snowflake in Power BI Desktop
2/13/2019 • 2 minutes to read • Edit Online

In Power BI Desktop, you can connect to a Snowflake computing warehouse and use the underlying data just like
any other data source in Power BI Desktop.

NOTE
You also must install the Snowflake ODBC driver on computers that use the Snowflake connector, using the architecture
that matches the installation of Power BI Desktop, either 32-bit or 64-bit. Just follow the following link and download the
appropriate Snowflake ODBC driver.

Connect to a Snowflake computing warehouse

To connect to a Snowflake computing warehouse, select Get Data from the Home ribbon in Power BI Desktop.
Select Database from the categories on the left, and you see Snowflake.

In the Snowflake window that appears, type or paste the name of your Snowflake computing warehouse into the
box and select OK. Note that you can choose to Import data directly into Power BI, or you can use DirectQuery.
You can learn more about using DirectQuery.
When prompted, put in your username and password.

NOTE
Once you put in your username and password for a particular Snowflake server, Power BI Desktop uses those same
credentials in subsequent connection attempts. You can modify those credentials by going to File > Options and settings >
Data source settings.

Once you successfully connect, a Navigator window appears and displays the data available on the server, from
which you can select one or multiple elements to import and use in Power BI Desktop.
You can Load the selected table, which brings the entire table into Power BI Desktop, or you can Edit the query,
which opens Query Editor so you can filter and refine the set of data you want to use, and then load that refined
set of data into Power BI Desktop.

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources,
check out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Analyze Azure cost and usage data in Power BI
desktop
3/4/2019 • 11 minutes to read • Edit Online

Power BI desktop can connect to Azure and get in-depth data about your organization's Azure service usage. With
it, you can create custom reports and measures to better understand and analyze your Azure spend.
Power BI currently supports connecting to Enterprise Agreement and Customer Agreement billing accounts.
Enterprise Agreement users should connect with the Azure Consumption Insights connector. Customer agreement
account users should connect with the Azure Cost Management connector.

Connect with Azure Consumption Insights

Azure Consumption Insights allows you to connect to Azure Enterprise Agreement billing accounts.
In this section, you will learn how to connect get the data you need, how to migrate fr om using the Azure
Enterprise Connector, and you'll find a mapping of usage details columns available in the ACI (Azure Consumption
Insights) API.
To successfully connect using the Azure Consumption Insights connector, you need to have access to the
Enterprise features within the Azure portal.
To connect using the Azure Consumption Insights connector, select Get Data from the Home ribbon in Power
BI Desktop. Select Online Services from the categories on the left, and you see Microsoft Azure
Consumption Insights (Beta). Select Connect.
In the dialog that appears, provide your Enrollment Number.

You can get your enrollment number from the Azure Enterprise Portal, in the location shown in the
following image:
 This version of the connector only supports enterprise enrollments from https://ea.azure.com. China
enrollments are not currently supported.
Next, provide your Access key to connect.

Your Access key for enrollment can be found on the Azure Enterprise Portal.

Once you provide your Access key and select Connect, a Navigator window appears and shows the nine tables
available to you:
 Budgets: Provides budget details to view actual costs or usage against existing budget targets.
MarketPlace: Provides usage-based Azure Marketplace charges.
PriceSheets: Provides applicable rates by meter for an enrollment.
RICharges: Provides charges associated to your Reserved Instances over the last 24 months.
RIRecommendations_Single: Provides Reserved Instance purchase recommendations based on your usage
trends on a single subscription over the last 7, 30 or 60 days.
RIRecommendations_Shared: Provides Reserved Instance purchase recommendations based on your usage
trends across all your subscriptions over the last 7, 30 or 60 days.
RIUsage: Provides consumption details for your existing Reserved Instances over the last month.
Summaries: Provides a monthly summary across balances, new purchases, Azure Marketplace service charges,
adjustments, and overage charges.
UsageDetails: Provides a breakdown of consumed quantities and estimated charges for an enrollment.
You can select a checkbox beside any table to see a preview. You can select one or more tables by checking the box
beside their name, then select Load.

NOTE
The Summary and PriceSheet tables are only available for the enrollment-level API Key. Also, the data in these tables has, by
default, the current month's data for Usage and PriceSheet. The Summary and MarketPlace tables are not constrained to the
current month.

When you select Load the data is loaded into Power BI Desktop.
Once the data you selected is loaded, the tables and fields you selected can be seen in the Fields pane.

Using Azure Consumption Insights

To use the Azure Consumption Insights connector, you need to have access to the Enterprise features within the
Azure portal.
Once you successfully load data using the Azure Consumption Insights connector, you can create your own
custom measures and columns using Query Editor, and you can create visuals, reports, and dashboards that you
can share in the Power BI service.
Azure also includes a collection of sample custom queries that you can retrieve using a blank query. To do so, in the
Home ribbon of Power BI Desktop, select the drop down arrow in Get Data and then select Blank Query. You
can also do this in Query Editor by right-clicking in the Queries pane along the left, and selecting New Query >
Blank Query from the menu that appears.
In the Formula bar, type the following:
 = MicrosoftAzureConsumptionInsights.Contents

A collection of samples appear, as shown in the following image:

When working with reports and creating queries, use the following:
To define the number of months starting from the current date, use numberOfMonth
Use a value between one and 36 to represent the number of months, from the current date, you want to
import. We recommend getting no more than 12 months of data to avoid thresholds with import
constraints and the volume of data allowed for queries in Power BI.
To define a period of months in a historical time window, use startBillingDataWindow and
endBillingDataWindow
Do not use numberOfMonth together with startBillingDataWindow or endBillingDataWindow

Migrating from the Azure Enterprise Connector

Some customers created visuals using the Azure Enterprise Connector (Beta ), which will eventually be
discontinued, and is being replaced by the Azure Consumption Insights connector. The Azure Consumption
Insights connector has features and enhancements that include the following:
Additional data sources available for Balance Summary and Marketplace Purchases
New and advanced parameters, such as startBillingDataWindow and endBillingDataWindow
Better performance and responsiveness
To help customers transition to the newer Azure Consumption Insights connector, and to preserve the work
they've done in creating custom dashboards or reports, the following steps show how to move to the new
connector.
Step 1: Connect to Azure using the new connector
The first step is to connect using the Azure Consumption Insights connector, which was described earlier in this
article in detail. In this step, select Get Data > Blank Query from the Home ribbon in Power BI Desktop.
Step 2: Use the Advanced Editor to create a query
In Query Editor, select Advanced Editor from the Query section of the Home ribbon. In the Advanced Editor
window that appears, enter the following query:
 let
enrollmentNumber = "100",
optionalParameters = [ numberOfMonth = 6, dataType="DetailCharges" ],
data = MicrosoftAzureConsumptionInsights.Contents(enrollmentNumber, optionalParameters)
in
data

Of course, you'll need to replace the value of enrollmentNumber with your own enrollment number, which you can
get from the Azure Enterprise Portal. The numberOfMonth parameter is how many months of data you want
going back, from the current data. Use zero (0) for the current month.
Once you select Done in the Advanced Editor window, the preview refreshes and you'll see data from the
specified month range in the table. Select Close & Apply and return.
Step 3: Move measures and custom columns to the new report
Next you'll need to move any custom columns or measures you created into the new details table. Here are the
steps.
1. Open Notepad (or another text editor).
2. Select the measure you want to move, copy the text from the Formula field, and place it in Notepad.

3. Rename Query1 to the original details table name.

4. Create new measures and custom columns in your table by right-clicking on your table, and choosing New
Measure, then cut and paste your stored measures and columns until they're all done.
Step 4: Re -link tables that had relationships
Many dashboards have additional tables that are used for lookup or filtering, such as date tables or tables used for
custom projects. Reestablishing those relationships resolves most remaining issues. Here's how to do it.
In the Modeling tab in Power BI Desktop, select Manage Relationships to bring up a window that lets
you manage relationships within the model. Re-link your tables, as needed.

Step 5: Verify your visuals, and adjust field formatting as needed

Once you get this far, most of your original visuals, tables, and drill-downs should be working as expected.
However, there may be some minor tweaks necessary for formatting, to get things looking just how you want
them. Take a bit of time to look over each of your dashboards and visuals, to ensure they look how you want them.

Using the Azure Consumption and Insights (ACI) API to get

consumption data
Azure also provides the Azure Consumption and Insights (ACI ) API. You can create your own custom solutions
to gathering, reporting, and visualizing Azure consumption information using the ACI API.
Mapping names and usage details between the portal, the connector, and the API
The columns and names of details in the Azure Portal are similar in the API and the connector, but they're not
always identical. To help clarify, the following table provides a mapping between the API, the connector, and
columns you see in the Azure Portal. Also indicated is whether the column is obsolete. For more information and
definitions of these terms, take a look at the Azure billing data dictionary.

ACI CONNECTOR / OBSOLETE / PRESENT FOR

CONTENTPACK COLUMNNAME ACI API COLUMN NAME EA COLUMN NAME BACKWARD COMPATIBILITY

AccountName accountName Account Name No

AccountId accountId Yes

ACI CONNECTOR / OBSOLETE / PRESENT FOR
CONTENTPACK COLUMNNAME ACI API COLUMN NAME EA COLUMN NAME BACKWARD COMPATIBILITY

AcccountOwnerId accountOwnerEmail AccountOwnerId No

AdditionalInfo additionalInfo AdditionalInfo No

AdditionalInfold Yes

Consumed Quantity consumedQuantity Consumed Quantity No

Consumed Service consumedService Consumed Service No

ConsumedServiceId consumedServiceId Yes

Cost cost ExtendedCost No

Cost Center costCenter Cost Center No

Date date Date No

Day Day No

DepartmentName departmentName Department Name No

DepartmentID departmentId Yes

Instance ID Yes

InstanceId instanceId Instance ID No

Location Yes

Meter Category meterCategory Meter Category No

Meter ID Yes

Meter Name meterName Meter Name No

Meter Region meterRegion Meter Region No

Meter Sub-Category meterSubCategory Meter Sub-Category No

MeterId meterId Meter ID No

Month Month No

Product product Product No

ProductId productId Yes

Resource Group resourceGroup Resource Group No

 ACI CONNECTOR / OBSOLETE / PRESENT FOR
CONTENTPACK COLUMNNAME ACI API COLUMN NAME EA COLUMN NAME BACKWARD COMPATIBILITY

Resource Location resourceLocation Resource Location No

ResourceGroupId Yes

ResourceLocationId resourceLocationId Yes

ResourceRate resourceRate ResourceRate No

ServiceAdministratorId serviceAdministratorId ServiceAdministratorId No

ServiceInfo1 serviceInfo1 ServiceInfo1 No

ServiceInfo1Id Yes

ServiceInfo2 serviceInfo2 ServiceInfo2 No

ServiceInfo2Id Yes

Store Service Identifier storeServiceIdentifier Store Service Identifier No

StoreServiceIdentifierId Yes

Subscription Name subscriptionName Subscription Name No

Tags tags Tags No

TagsId Yes

Unit Of Measure unitOfMeasure Unit Of Measure No

Year Year No

SubscriptionId subscriptionId SubscriptionId Yes

SubscriptionGuid subscriptionGuid SubscriptionGuid No

Connect with Azure Cost Management

In this section, you'll learn how to connect to your Customer Agreement billing account.
To connect using the Azure Cost Management connector, select Get Data from the Home ribbon in Power BI
Desktop. Select Azure fromfrom the categories on the left, and you see Azure Cost Management (Beta). Select
Connect.
In the dialog that appears, input your billing profile ID.

You can get your billing profile ID from the Azure portal. Navigate to Cost Management + Billing, select your
billing account, and then select Biling profiles in the sidebar. Select your billing profile and select Properties in
the sidebar. Copy your billing profile ID.
You'll be prompted to log in with your Azure email and password. Once you authenticate, you'll be shown a
Navigator window with the twelve tables available to you:
Billing events: Provides event log of new invoices, credit purchases, and more.
Budgets: Provides budget details to view actual costs or usage against existing budget targets.
Charges: Provides a month-level summary of Azure usage, market place charges, and charges billed separately.
Credit lots: Provides Azure credit lot purchase details for the provided billing profile.
Credit summary: Provides credit summary for provided billing profile.
Marketplace: Provides usage-based Azure Marketplace charges.
Pricesheets: Provides applicable rates by meter for the provided billing profile.
RI charges: Provides charges associated to your Reserved Instances over the last 24 months.
RI recommendations (single): Provides Reserved Instance purchase recommendations based on your usage
trends on a single subscription over the last 7, 30 or 60 days.
RI recommendations (shared): Provides Reserved Instance purchase recommendations based on your usage
trends across all your subscriptions over the last 7, 30 or 60 days.
RI usage: Provides consumption details for your existing Reserved Instances over the last month.
Usage details: Provides a breakdown of consumed quantities and estimated charges for the given billing
profile id.
You can select a checkbox next to any table to see a preview. You can select one or more tables by checking the box
beside their name and selecting Load.
When you select Load the data is loaded into Power BI Desktop.

Once the data you selected is loaded, the tables and fields you selected can be seen in the Fields pane.
Writing custom queries
If you want to customize the number of months, change the api version, or do more advanced logic on the
returned data, you can create a custom M query.
Go to the Home ribbon of Power BI Desktop, select the dropdown in Get Data and then select Blank Query.
You can also do this in Query Editor by right-clicking in the Queries pane along the left, and selecting New
Query > Blank Menu from the menu that appears.
In the Formula bar, type the following, replacing billingProfileId with your actual ID, and "charges" with any
valid table name (list above).
 let
Source = AzureCostManagement.Tables(billingProfileId, [ numberOfMonths = 3 ]),
charges = Source{[Key="charges"]}[Data]
in
charges

In addition to modifying the numberOfMonths to any value between 1 and 36, you can also provide:
apiVersion to customize which version of the API the query will call.
lookbackWindow , for RI recommendations (single or shared), to modify the window in which to generate
recommendations from (valid options: 7, 30, or 60 days)

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources,
check out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Use SAP HANA in Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

With Power BI Desktop, you can now access SAP HANA databases. To use SAP HANA, the SAP HANA ODBC
driver must be installed on the local client computer in order for the Power BI Desktop SAP HANA data
connection to work properly. You can download the SAP HANA ODBC driver from the SAP Software Download
Center. From there, search for the SAP HANA CLIENT for Windows computers. Since the SAP Software
Download Center changes its structure frequently, more specific guidance for navigating that site is not available.
To connect to a SAP HANA database, select Get Data > Database > SAP HANA Database as shown in the
following image:

When connecting to a SAP HANA database, specify the server name and the port in the format server:port - the
following image shows an example with a server named ServerXYZ and port 30015.
In this release SAP HANA in DirectQuery mode is supported in Power BI Desktop and the Power BI service, and
you can publish and upload reports that use SAP HANA in DirectQuery mode to the Power BI service. You can
also publish and upload reports to the Power BI Service when not using SAP HANA in DirectQuery mode.

Supported features for SAP HANA

This release has many capabilities for SAP HANA, as shown in the following list:
The Power BI connector for SAP HANA uses the SAP ODBC driver, to provide the best user experience
SAP HANA supports both DirectQuery and Import options
Power BI supports HANA information models (such as Analytic and Calc views) and has optimized navigation
With SAP HANA, you can also use the direct SQL feature to connect to Row and Column Tables
Includes Optimized Navigation for HANA Models
Power BI supports SAP HANA Variables and Input parameters

Limitations of SAP HANA

There are also a few limitations to using SAP HANA, shown below:
NVARCHAR strings are truncated to maximum length of 4000 Unicode characters
SMALLDECIMAL is not supported
VARBINARY is not supported
Valid Dates are between 1899/12/30 and 9999/12/31

Next steps
For more information about DirectQuery, check out the following resources:
DirectQuery and SAP HANA
DirectQuery in Power BI
Data Sources supported by DirectQuery
 Using Analysis Services Tabular data in Power BI
Desktop
2/13/2019 • 5 minutes to read • Edit Online

With Power BI Desktop, there are two ways you can connect to and get data from your SQL Server Analysis
Services Tabular models: Explore by using a live connection or Select items and import into Power BI Desktop.
Let’s take a closer look.
Explore by using a live connection – When using a live connection, items in your Tabular model or perspective,
like tables, columns, and measures appear in your Power BI Desktop Fields list. You can use Power BI Desktop’s
advanced visualization and report tools to explore your Tabular model in new, highly interactive ways.
When connecting live, no data from the Tabular model is imported into Power BI Desktop. Each time you interact
with a visualization, Power BI Desktop queries the Tabular model and calculates the results you see. You’re always
looking at the latest data that is available in the Tabular model, either from the last processing time, or from Direct
Query tables available in the Tabular Model.
Keep in-mind, that Tabular models are highly secure. Items that appear in Power BI Desktop depend on your
permissions for the Tabular model you’re connected to.
When you’ve created dynamic reports in Power BI Desktop, you can share them by publishing to your Power BI
site. When you publish a Power BI Desktop file with a live connection to a Tabular model to your Power BI site, an
On-premises data gateway must be installed and configured by an administrator. To learn more, see On-premises
data gateway.
Select items and import into Power BI Desktop – When you connect with this option, you can select items like
tables, columns, and measures in your Tabular model or perspective and load them into a Power BI Desktop model.
You can use Power BI Desktop’s advanced Query Editor to further shape what you want. You can use Power BI
Desktop’s modeling features to further model the data. No live connection between Power BI Desktop and the
Tabular model is maintained. You can then explore your Power BI Desktop model offline or publish to your Power
BI site.

To connect to a Tabular model

1. In Power BI Desktop, on the Home tab, click Get Data.

2. Click SQL Server Analysis Services Database, then click Connect.

3. Enter the Server name and select a connection mode.

4. This step depends on the connection mode you selected:

If you’re connecting live, in Navigator, select a Tabular model or perspective.
 If you chose Select items and get data, in Navigator, select a Tabular model or perspective. You can further
select only particular tables or columns to load. To shape your data before loading, click Edit to open Query
Editor. When you’re ready, click Load to import the data into Power BI Desktop.

Frequently Asked Questions

Question: Do I need an On-premises data gateway?
Answer: It depends. If you use Power BI Desktop to connect live to a Tabular model, but have no intention on
publishing to your Power BI site, you do not need a gateway. On the other hand, if you do intend on publishing to
your Power BI site, a data gateway is necessary to ensure secure communication between the Power BI service and
your on-premises Analysis Services server. Be sure to talk to your Analysis Services server administrator before
installing a data gateway.
If you choose select items and get data, you’re importing Tabular model data right into your Power BI Desktop file,
so no gateway is necessary.
Question: What’s the difference between connecting live to a Tabular model from the Power BI service versus
connecting live from Power BI Desktop?
Answer: When connecting live to a Tabular model from your site in the Power BI service to an Analysis Services
database on-premises in your organization, an On-premises data gateway is required to secure communications
between them. When connecting live to a Tabular model from Power BI Desktop, a gateway is not required
because both Power BI Desktop and the Analysis Services server you’re connecting to are both running on-
premises in your organization. However, if you publish your Power BI Desktop file to your Power BI site, a gateway
is required.
Question: If I created a live connection, can I connect to another data source in the same Power BI Desktop file?
Answer: No. You cannot explore live data and connect to another type of data source in the same file. If you’ve
already imported data or connected to a different data source in a Power BI Desktop file, you’ll need to create a
new file to explore live.
Question: If I created a live connection, can I edit the model or query in Power BI Desktop?
Answer: You can create report level measures in the Power BI Desktop, but all other query and modeling features
are disabled when exploring live data.
Question: If I created a live connection, is it secure?
Answer: Yes. Your current Windows credentials are used to connect to the Analysis Services server. You cannot use
Basic or stored credentials in either the Power BI service or Power BI Desktop when exploring live.
Question: In Navigator, I see a model and a perspective. What’s the difference?
Answer: A perspective is a particular view of a Tabular model. It might include only particular tables, columns, or
measures depending on a unique data analysis need. A Tabular model always contains at least one perspective,
which could include everything in the model. If you’re unsure which you should select, check with your
administrator.

To change the server name after initial connection

Once you create a Power BI Desktop file with an explore live connection, there might be some cases where you
want to switch the connection to a different server. For example, if you created your Power BI Desktop file when
connecting to a development server, and before publishing to the Power BI service, you want to switch the
connection to production server.
1. Select Edit Queries from the Ribbon.

2. Enter the new server name.

Troubleshooting
The following list describes all known issues when connecting to SQL Server Analysis Services (SSAS ) or Azure
Analysis Services.
Error : Couldn't load model schema - This error usually occurs when the user connecting to Analysis
Services does not have access to database/model.
 Use DirectQuery in Power BI Desktop
3/6/2019 • 7 minutes to read • Edit Online

With Power BI Desktop, when you connect to your data source, it is always possible to import a copy of the
data into the Power BI Desktop. For some data sources, an alternative approach is available: connect directly to
the data source using DirectQuery.

Supported Data Sources

For a full listing of data sources that support DirectQuery, see Data sources supported by DirectQuery.

How to Connect using DirectQuery

When you use Get Data to connect to a data source supported by DirectQuery, the connection window lets you
select how you want to connect.

The differences between selecting Import and DirectQuery are the following:
Import – the selected tables and columns are imported into Power BI Desktop. As you create or interact with a
visualization, Power BI Desktop uses the imported data. You must refresh the data, which imports the full data
set again, to see any changes that occurred to the underlying data since the initial import or the most recent
refresh.
DirectQuery – no data is imported or copied into Power BI Desktop. For relational sources, the selected tables
and columns appear in the Fields list. For multi-dimensional sources like SAP Business Warehouse, the
dimensions and measures of the selected cube appear in the Fields list. As you create or interact with a
visualization, Power BI Desktop queries the underlying data source, which means you’re always viewing current
data.
Many data modeling and data transformations are available when using DirectQuery, though with some
limitations. When creating or interacting with a visualization, the underlying source must be queried and the time
necessary to refresh the visualization is dependent on the performance of the underlying data source. When the
data necessary to service the request has recently been requested, Power BI Desktop uses recent data to reduce
the time required to display the visualization. Selecting Refresh from the Home ribbon will ensure all
visualizations are refreshed with current data.
The Power BI and DirectQuery article describes DirectQuery in detail. Also, see the following sections for more
information about benefits, limitations, and important considerations when using DirectQuery.

Benefits of using DirectQuery

There are a few benefits to using DirectQuery:
DirectQuery lets you build visualizations over very large datasets, where it would otherwise be unfeasible to
first import all of the data with pre-aggregation
Underlying data changes can require a refresh of data, and for some reports, the need to display current data
can require large data transfers, making re-importing data unfeasible. By contrast, DirectQuery reports
always use current data
The 1-GB dataset limitation does not apply to DirectQuery

Limitations of DirectQuery
There are currently a few limitations to using DirectQuery:
All tables must come from a single database, unless using composite models
If the Query Editor query is overly complex, an error will occur. To remedy the error you must either delete
the problematic step in Query Editor, or Import the data instead of using DirectQuery. For multi-
dimensional sources like SAP Business Warehouse, there is no Query Editor
Relationship filtering is limited to a single direction, rather than both directions (though it is possible to enable
cross filtering in both directions for DirectQuery as a Preview feature). For multi-dimensional sources like
SAP Business Warehouse, there are no relationships defined in the model
Time intelligence capabilities are not available in DirectQuery. For example, special treatment of date
columns (year, quarter, month, day, so on) is not supported in DirectQuery mode.
By default, limitations are placed on DAX expressions allowed in measures; see the following paragraph (after
this bulleted list) for more information
There is a one-million-row limit for returning data when using DirectQuery. The limit does not affect
aggregations or calculations used to create the dataset returned using DirectQuery, only the rows returned.
For example, you can aggregate 10 million rows with your query that runs on the data source, and accurately
return the results of that aggregation to Power BI using DirectQuery as long as the data returned to Power
BI is less than 1 million rows. If more than 1 million rows would be returned from DirectQuery, Power BI
returns an error.
To ensure that queries sent to the underlying data source have acceptable performance, limitations are imposed
on measures by default. Advanced users can choose to bypass this limitation by selecting File > Options and
settings > Options and then DirectQuery, then selecting the option Allow unrestricted measures in
DirectQuery mode. When that option is selected, any DAX expression that is valid for a measure can be used.
Users must be aware, however, that some expressions that perform very well when the data is imported may
result in very slow queries to the backend source when in DirectQuery mode.

Important considerations when using DirectQuery

The following three points should be taken into consideration when using DirectQuery:
Performance and load - All DirectQuery requests are sent to the source database, so the time required
to refresh a visual is dependent on how long that back-end source takes to respond with the results from
the query (or queries). The recommended response time (with requested data being returned) for using
DirectQuery for visuals is five seconds or less, with a maximum recommended results response time of
30 seconds. Any longer, and the experience of a user consuming the report becomes unacceptably poor. In
addition, once a report is published to the Power BI service, any query that takes longer than a few
 minutes will time out, and the user will receive an error.
Load on the source database should also be considered, based on the number of Power BI users who will
consume the published report. Using Row Level Security (RLS ) can have a significant impact as well; a
non-RLS dashboard tile shared by multiple users results in a single query to the database, but using RLS
on a dashboard tile usually means the refresh of a tile requires one query per user, thus significantly
increasing load on the source database and potentially impacting performance.
Power BI creates queries that are as efficient as possible. Under certain situations however, the generated
query may not be efficient enough to avoid refresh that would fail. One example of this situation is when a
generated query would retrieve an excessively large number of rows (more than 1 million) from the back-
end data source, in which case the following error occurs:

The resultset of a query to external data source has exceeded

the maximum allowed size of '1000000' rows.

This situation can occur with a simple chart that includes a very high cardinality column, with the
aggregation option set to Don’t Summarize. The visual needs to only have columns with a cardinality
below 1 million, or must have appropriate filters applied.
Security - All users who consume a published report connect to the back-end data source using the
credentials entered after publication to the Power BI service. This is the same situation as data that is
imported: all users see the same data, irrespective of any security rules defined in the backend source.
Customers who want per-user security implemented with DirectQuery sources should use RLS. Learn
more about RLS.
Supported features - Not all features in Power BI Desktop are supported in DirectQuery mode, or
have some limitations. In addition, there are some capabilities in the Power BI service (such as Quick
Insights) that are not available for datasets using DirectQuery. As such, the limitation of such features
when using DirectQuery should be taken into consideration when determining whether to use
DirectQuery.

Publish to the Power BI service

Reports created using DirectQuery can be published to the Power BI Service.
If the data source used does not need the On-premises data gateway (Azure SQL Database, Azure SQL
Data Warehouse, or Redshift), credentials must be provided before the published report will be displayed in
the Power BI Service.
You can provide credentials by selecting the Settings gear icon in Power BI, then select Settings.
Power BI displays the Settings window. From there, select the Datasets tab and choose the dataset that uses
DirectQuery, and select Edit credentials.

Until credentials are supplied, opening a published report or exploring a dataset created with a DirectQuery
connection to such data sources results in an error.
For data sources other than Azure SQL Database, Azure SQL Data Warehouse and Redshift that use
DirectQuery, an On-premises data gateway must be installed and the data source must be registered to
establish a data connection. You can learn more about On-premises data gateway.

Next steps
For more information about DirectQuery, check out the following resources:
DirectQuery in Power BI
Data sources supported by DirectQuery
DirectQuery and SAP BW
DirectQuery and SAP HANA
On-premises data gateway
 DirectQuery for Oracle and Teradata Databases
1/14/2019 • 2 minutes to read • Edit Online

Please see DirectQuery Data Sources for information about data sources and DirectQuery.
 DirectQuery and SAP Business Warehouse (BW)
1/14/2019 • 9 minutes to read • Edit Online

You can connect to SAP Business Warehouse (BW ) data sources directly using DirectQuery. Given the
OLAP/multidimensional nature of SAP BW, there are many important differences between DirectQuery over
SAP BW versus relational sources like SQL Server. These differences are summarized as follows:
In DirectQuery over relational sources there are a set of queries (as defined in the Get Data or Query
Editor dialog) that logically define the data that is available in the field list. This is not the case when
connecting to an OLAP source such as SAP BW. Instead, when connecting to the SAP server using Get Data,
just the Infocube or BEx Query is selected. Then all the Key Figures and dimensions of the selected
Infocube/BEx Query will be available in the field list.
Similarly, there is no Query Editor when connecting to SAP BW. The data source settings (for example,
server name) can be changed by selecting Edit Queries > Data source settings. The settings for any
Parameters can be changed by selecting Edit Queries > Manage Parameters.
Given the unique nature of OLAP sources, there are additional restrictions (for both modeling and
visualizations) that apply, in addition to the normal restrictions imposed for DirectQuery. These restrictions
are described later in this article.
In addition, it is extremely important to understand that there are many features of SAP BW that are not
supported in Power BI, and that because of the nature of the public interface to SAP BW, there are important
cases where the results seen through Power BI will not match those seen when using an SAP tool. These
limitations are described later in this article. These limitations and behavior differences should be carefully
reviewed, to ensure that the results seen through Power BI, as returned by the SAP public interface, are
interpreted correctly.

NOTE
The ability to use DirectQuery over SAP BW was in preview until the March 2018 update to Power BI Desktop. During the
preview, feedback and suggested improvements prompted a change that impacts reports that were created using that
preview version. Now that General Availability (GA) of DirectQuery over SAP BW has released, you must discard any
existing (preview-based) reports using DirectQuery over SAP BW that were created with the pre-GA version. In reports
created with the pre-GA version of DirectQuery over SAP BW, errors will occur with those pre-GA reports upon invoking
Refresh, as a result of attempting to refresh the metadata with any changes to the underlying SAP BW cube. Please re-
create those reports from a blank report, using the GA version of DirectQuery over SAP BW.

Additional Modeling Restrictions

The primary additional modeling restrictions when connecting to SAP BW using DirectQuery in Power BI are the
following:
No support for calculated columns: The ability to create calculated columns is disabled. This also means
that Grouping and Clustering, which create calculated columns, are not available.
Additional limitations for measures: There are additional limitations imposed on the DAX expressions that
can be used in measures, to reflect the level of support offered by SAP BW.
No support for defining relationships: The relationships are inherent in the external SAP source, and
additional relationships cannot be defined in the model.
No Data View: The Data View normally displays the detail level data in the tables. Given the nature of
OLAP sources like SAP BW, this view is not available over SAP BW.
 Column and measure details are fixed: The list of columns and measures seen in the field list are fixed by
the underlying source, and cannot be modified. For example, it is not possible to delete a column, nor change
its datatype (it can, however, be renamed).
Additional limitations in DAX: There are additional limitations on the DAX that can be used in measure
definitions, to reflect limitations in the source. For example, it is not possible to use an aggregate function over
a table.

Additional Visualization Restrictions

The primary additional restrictions in visualizations when connecting to SAP BW using DirectQuery in Power BI
are the following:
No aggregation of columns: It is not possible to change the aggregation for a column on a visual; it is
always Do Not Summarize
Measure filtering is disabled: Measure filtering is disabled to reflect the support offered by SAP BW.
Multi-select and include/exclude: The ability to multi-select data points on a visual is disabled if the points
represent values from more than one column. For example, given a bar chart showing Sales by Country, with
Category on the Legend, it would not be possible to select the point for (USA, Bikes) and (France, Clothes).
Similarly, it would not be possible to select the point for (USA, Bikes) and exclude it from the visual. Both
limitations are imposed to reflect the support offered by SAP BW.

Support for SAP BW features

The following table lists all SAP BW features that are not fully supported, or will behave differently when using
Power BI.

FEATURE DESCRIPTION

Local calculations Local calculations defined in a BEx Query will change the
numbers as displayed through tools like BEx Analyzer.
However, they are not reflected in the numbers returned
from SAP, through the public MDX interface.

As such, the numbers seen in a Power BI visual will not

necessarily match those for a corresponding visual in an
SAP tool.

For example, when connecting to a query cube from a BEx

query that sets the aggregation to be Cumulated (i.e.
running sum), Power BI would get back the base numbers,
ignoring that setting. An analyst could certainly then apply a
running sum calculation locally in Power BI, but would need
to exercise caution in how the numbers are interpreted if this
is not done.
FEATURE DESCRIPTION

Aggregations In some cases (particularly when dealing with multiple

currencies), the aggregate numbers returned by the SAP
public interface do not match those shown by SAP tools.

As such, the numbers seen in a Power BI visual will not

necessarily match those for a corresponding visual in an
SAP tool.

For example, totals over different currencies would show as

"*" in BEx Analyzer, but the total would get returned by the
SAP public interface, without any information that such an
aggregate number is meaningless. Thus the number
(aggregating, say, $, EUR, and AUD) would get displayed by
Power BI.

Currency formatting Any currency formatting (for example, $2,300 or 4000 AUD)
is not reflected in Power BI.

Units of measure Units of measure (for example, 230 KG) are not reflected in
Power BI.

Key versus text (short, medium, long) For an SAP BW characteristic like CostCenter, the field list will
show a single column Cost Center. Using that column will
display the default text. By showing hidden fields, it will also
be possible to see the unique name column (that returns the
unique name assigned by SAP BW, and is the basis of
uniqueness).

The key and other text fields are not available.

Multiple hierarchies of a characteristic In SAP, a characteristic can have multiple hierarchies. Then in
tools like BEx Analyzer, when a characteristic is included in a
query, the user can select the hierarchy to use.

In Power BI, the various hierarchies can be seen in the field

list as different hierarchies on the same dimension. However,
selecting multiple levels from two different hierarchies on the
same dimension will result in empty data being returned by
SAP.

Treatment of ragged hierarchies

FEATURE DESCRIPTION

Scaling factor/reverse sign In SAP, a key figure can have a scaling factor (for example,
1000) defined as a formatting option, meaning that all
display will be scaled by that factor.

It can similarly have a property set that reverses the sign.

Use of such a key figure in Power BI (in a visual, or as part of
a calculation) will result in the unscaled number being used
(and the sign is not reversed). The underlying scaling factor is
not available. In Power BI visuals, the scale units shown on
the axis (K,M,B) can be controlled as part of the visual
formatting.

Hierarchies where levels appear/disappear dynamically Initially when connecting to SAP BW, the information on the
levels of a hierarchy will be retrieved, resulting in a set of
fields in the field list. This is cached, and if the set of levels
changes, then the set of fields do not change until Refresh is
invoked.

This is only possible in Power BI Desktop. Such Refresh to

reflect changes to the levels cannot be invoked in the Power
BI service after Publish.

Default filter A BEx query can include Default Filters, which will be applied
automatically by SAP BEx Analyzer. These are not exposed,
and hence the equivalent usage in Power BI will not apply the
same filters by default.

Hidden Key figures A BEx query can control visibility of Key Figures, and those
that are hidden will not appear in SAP BEx Analyzer. This is
not reflected through the public API, and hence such hidden
key figures will still appear in the field list. However, they can
then be hidden within Power BI.

Numeric formatting Any numeric formatting (number of decimal positions,

decimal point, etc.) will not automatically be reflected in
Power BI. However, it is possible to then control such
formatting within Power BI.

Hierarchy versioning SAP BW allows different versions of a hierarchy to be

maintained, for example, the cost center hierarchy in 2007
versus 2008. Only the latest version will be available in Power
BI, as information on versions is not exposed by the public
API.

Time dependent hierarchies When using Power BI, time dependent hierarchies are
evaluated at the current date.

Currency conversion SAP BW supports currency conversion, based on rates held in

the cube. Such capabilities are not exposed by the public API,
and are therefore not available in Power BI.

Sort Order The sort order (by Text, or by Key) for a characteristic can be
defined in SAP. This sort order is not reflected in Power BI.
For example, months might appear as “April”, “Aug”, and so
on.

It is not possible to change this sort order in Power BI.

 FEATURE DESCRIPTION

Technical names In Get Data, the characteristic/measure names (descriptions)

and technical names can both be seen. The field list will
contain just the characteristic/measure names (descriptions).

Attributes It is not possible to access the attributes of a characteristic

within Power BI.

End user language setting The locale used to connect to SAP BW is set as part of the
connection details, and does not reflect the locale of the final
report consumer.

Text Variables SAP BW allows field names to contain placeholders for

variables (for example, "$YEAR$ Actuals") that would then get
replaced by the selected value. For example, the field appears
as "2016 Actuals" in BEx tools, if the year 2016 were selected
for the variable.

The column name in Power BI will not be changed depending

on the variable value, and therefore would appear as
"$YEAR$ Actuals". However, the column name can then be
changed in Power BI.

Customer Exit Variables Customer Exit variables are not exposed by the public API,
and are therefore not supported by Power BI.

Characteristic Structures Any Characteristic structures in the underlying SAP BW

source will result in an ‘explosion’ of measures being exposed
in Power BI. For example, with two measures Sales and Costs,
and a characteristic structure containing Budget and Actual,
four measures will be exposed: Sales.Budget, Sales.Actual,
Costs.Budget, Costs.Actual.

Next steps
For more information about DirectQuery, check out the following resources:
DirectQuery in Power BI
Data Sources supported by DirectQuery
DirectQuery and SAP HANA
 DirectQuery and SAP HANA
1/14/2019 • 12 minutes to read • Edit Online

You can connect to SAP HANA data sources directly using DirectQuery. There are two options when
connecting to SAP HANA:
Treat SAP HANA as a multi-dimensional source (default): In this case, the behavior will be similar
to when Power BI connects to other multi-dimensional sources like SAP Business Warehouse, or
Analysis Services. When connecting to SAP HANA using this setting, a single analytic or calculation view
is selected, and all the measures, hierarchies and attributes of that view will be available in the field list.
As visuals are created, the aggregate data will always be retrieved from SAP HANA. This is the
recommended approach, and is the default for new DirectQuery reports over SAP HANA.
Treat SAP HANA as a relational source: In this case, Power BI treats SAP HANA as a relational
source. This offers greater flexibility, but care must be taken to ensure that measures are aggregated as
expected, and to avoid performance issues.
The approach used to connect is determined by a global tool option, which is set by selecting File > Options
and settings and then Options > DirectQuery, then selecting the option Treat SAP HANA as a relational
source, as shown in the following image.

The option to treat SAP HANA as a relational source controls the approach used for any new report using
DirectQuery over SAP HANA. It has no effect on any existing SAP HANA connections in the current report, nor
on connections in any other reports that are opened. So if the option is currently unchecked, then upon adding a
new connection to SAP HANA using Get Data, that connection will be made treating SAP HANA as a multi-
dimensional source. However, if a different report is opened that also connects to SAP HANA, then that report
will continue to behave according to the option that was set at the time it was created. This means that any
reports connecting to SAP HANA that were created prior to February 2018 will continue to treat SAP HANA as
a relational source.
The two approaches constitute very different behavior, and it's not possible to switch an existing report from
one approach to the other.
Let's look at more detail about each of these two approaches, in turn.

Treat SAP HANA as a multi-dimensional source (default)

All new connections to SAP HANA use this connection method by default, treating SAP HANA as a multi-
dimensional source. In order to treat a connection to SAP HANA as a relational source, you must select File >
Options and settings > Options, then check the box under Direct Query > Treat SAP HANA as a
relational source. While this feature is in Preview, reports created using the multi-dimensional approach
cannot be published to the Power BI service, and doing so will result in errors when the report is opened within
the Power BI service.
When connecting to SAP HANA as a multi-dimensional source, the following applies:
In the Get Data Navigator, a single SAP HANA view can be selected. It is not possible to select
individual measures or attributes. There is no query defined at the time of connecting, which is different
from importing data or when using DirectQuery while treating SAP HANA as a relational source. This
also means that it's not possible to directly use a SAP HANA SQL query when selecting this connection
method.
All the measures, hierarchies, and attributes of the selected view will be displayed in the field list.
As a measure is used in a visual, SAP HANA will be queried to retrieve the measure value at the level of
aggregation necessary for the visual. So when dealing with non-additive measures (counters, ratios, and
so on) all aggregations are performed by SAP HANA, and no further aggregation is performed by Power
BI.
To ensure the correct aggregate values can always be obtained from SAP HANA, certain restrictions
must be imposed. For example, it's not possible to add calculated columns, or to combine data from
multiple SAP HANA views within the same report.
Treating SAP HANA as a multi-dimensional source does not offer the greater flexibility provided by the
alternative relational approach, but it is simpler, and ensures correct aggregate values when dealing with more
complex SAP HANA measures, and generally results in higher performance.
The Field list will include all measures, attributes, and hierarchies from the SAP HANA view. Note the following
behaviors that apply when using this connection method:
Any attribute that is included in at least one hierarchy will be hidden by default. However, they can be
seen if required by selecting View hidden from the context menu on the field list. From the same
context menu they can be made visible, if required.
In SAP HANA, an attribute can be defined to use another attribute as its label. For example, Product
(with values 1,2,3, and so on) could use ProductName (with values Bike,Shirt,Gloves, and so on) as its
label. In this case, a single field Product will be shown in the field list, whose values will be the labels
Bike, Shirt, Gloves, and so on, but which will be sorted by, and with uniqueness determined by, the key
values 1,2,3. A hidden column Product.Key is also created, allowing access to the underlying key values
if required.
Any variables defined in the underlying SAP HANA view will be displayed at the time of connecting, and the
necessary values can be entered. Those values can subsequently be changed by selecting Edit Queries from
the ribbon, and then Manage Parameters from the drop down menu displayed.
The modeling operations allowed are more restrictive than in the general case when using DirectQuery, given
the need to ensure that correct aggregate data can always be obtained from SAP HANA. However, it's still
possible to make many additions and changes, including defining measures, renaming and hiding fields, and
defining display formats. All such changes will be preserved on refresh, and any non-conflicting changes made
to the SAP HANA view will be applied.
Additional Modeling Restrictions
The primary additional modeling restrictions when connecting to SAP HANA using DirectQuery (treat as multi-
dimensional source) are the following:
No support for calculated columns: The ability to create calculated columns is disabled. This also means
that Grouping and Clustering, which create calculated columns, are not available.
Additional limitations for measures: There are additional limitations imposed on the DAX expressions
that can be used in measures, to reflect the level of support offered by SAP HANA.
No support for defining relationships: Only a single view can be queried within a report, and as such,
there's no support for defining relationships.
No Data View: The Data View normally displays the detail level data in the tables. Given the nature of
OLAP sources such as SAP HANA, this view is not available over SAP HANA.
Column and measure details are fixed: The list of columns and measures seen in the field list are fixed by
the underlying source, and cannot be modified. For example, it's not possible to delete a column, nor change
its datatype (it can, however, be renamed).
Additional limitations in DAX: There are additional limitations on the DAX that can be used in measure
definitions, to reflect limitations in the source. For example, it's not possible to use an aggregate function
over a table.
Additional Visualization Restrictions
There are restrictions in visuals when connecting to SAP HANA using DirectQuery (treat as multi-dimensional
source):
No aggregation of columns: It's not possible to change the aggregation for a column on a visual, and it is
always Do Not Summarize.

Treat SAP HANA as a relational source

When choosing to connect to SAP HANA as a relational source, some additional flexibility becomes available.
For example, you can create calculated columns, include data from multiple SAP HANA views, and create
relationships between the resulting tables. However, when using SAP HANA in this manner, it's important to
understand certain aspects of how connections are treated, to ensure the following:
The results are as expected, when the SAP HANA view contains non-additive measures (for example, distinct
counts, or averages, rather than simple sums).
The resulting queries are efficient
It's useful to start by clarifying the behavior of a relational source such as SQL Server, when the query defined
in Get Data or Query Editor performs an aggregation. In the example that follows, a query defined in Query
Editor returns the average price by ProductID.
If the data is being imported into Power BI (versus using DirectQuery), the following would result:
The data is imported at the level of aggregation defined by the query created in Query Editor. For example,
average price by product. This results in a table with the two columns ProductID and AveragePrice that can
be used in visuals.
In a visual, any subsequent aggregation (such as Sum, Average, Min, others) is performed over that imported
data. For example, including AveragePrice on a visual will use the Sum aggregate by default, and would
return the sum over the AveragePrice for each ProductID – which in this example case would be 13.67. The
same applies to any alternative aggregate function (such as Min, Average, so on) used on the visual. For
example, Average of AveragePrice returns the average of 6.66, 4 and 3, which equates to 4.56, and not the
average of Price on the 6 records in the underlying table, which is 5.17.
If DirectQuery (over that same relational source) is being used instead of Import, the same semantics apply
and the results would be exactly the same:
Given the same query, logically exactly the same data is presented to the reporting layer – even though
the data is not actually imported.
In a visual, any subsequent aggregation (Sum, Average, Min, others) is again performed over that logical
table from the query. And again, a visual containing Average of AveragePrice returns the same 4.56.
Now let's consider SAP HANA, when the connection is treated as a relational source. Power BI can work with
both Analytic Views and Calculation Views in SAP HANA, both of which can contain measures. Yet today the
approach for SAP HANA follows the same principles as described previously in this section: the query defined
in Get Data or Query Editor will determine the data available, and then any subsequent aggregation in a
visual is over that data, and the same applies for both Import and DirectQuery.
However, given the nature of SAP HANA, the query defined in the initial Get Data dialog or Query Editor is
always an aggregate query, and generally will include measures where the actual aggregation that will be used
is defined by the SAP HANA view.
The equivalent of the SQL Server example above is that there is a SAP HANA view containing ID, ProductID,
DepotID, and measures including AveragePrice, defined in the view as Average of Price.
If, in the Get Data experience, the selections made were for ProductID and the AveragePrice measure, then
that is defining a query over the view, requesting that aggregate data (in the earlier example, for simplicity
pseudo-SQL is used that doesn’t match the exact syntax of SAP HANA SQL ). Then any further aggregations
defined in a visual are further aggregating the results of such a query. Again, as described above for SQL
Server, this applies both for the Import and DirectQuery case. Note that in the DirectQuery case, the query from
Get Data or Query Editor will be used in a subselect within a single query sent to SAP HANA, and thus it is
not actually the case that all the data would be read in, prior to aggregating further.
All of these considerations and behaviors necessitate the following important considerations when using
DirectQuery over SAP HANA:
Attention must be paid to any further aggregation performed in visuals, whenever the measure in SAP
HANA is non-additive (for example, not a simple Sum, Min, or Max).
In Get Data or Query Editor, only the required columns should be included to retrieve the necessary
data, reflecting the fact that the result will be a query, that must be a reasonable query that can be sent to
SAP HANA. For example, if dozens of columns were selected, with the thought that they might be
needed on subsequent visuals, then even for DirectQuery a simple visual will mean the aggregate query
used in the subselect will contain those dozens of columns, which will generally perform very poorly.
Let's look at an example. In the following example, selecting five columns (CalendarQuarter, Color,
LastName, ProductLine, SalesOrderNumber) in the Get Data dialog, along with the measure
OrderQuantity, will mean that later creating a simple visual containing the Min OrderQuantity will result in the
following SQL query to SAP HANA. The shaded is the subselect, containing the query from Get Data / Query
Editor. If this subselect gives a very high cardinality result, then the resulting SAP HANA performance will
likely be poor.

Because of this behavior, we recommend the items selected in Get Data or Query Editor be limited to those
items that are needed, while still resulting in a reasonable query for SAP HANA.

Best Practices
For both approaches to connecting to SAP HANA, recommendations for using DirectQuery also apply to SAP
HANA, particularly those related to ensuring good performance. These recommendations are described in
detail in the article using DirectQuery in Power BI.

Limitations
The following list describes all SAP HANA features that are not fully supported, or features that behave
differently when using Power BI.
Parent Child Hierarchies - Parent child hierarchies will not be visible in Power BI. This is because Power BI
accesses SAP HANA using the SQL interface, and parent child hierarchies cannot be fully accessed via SQL.
Other hierarchy metadata - The basic structure of hierarchies is displayed in Power BI, however some
hierarchy metadata (such as controlling the behavior of ragged hierarchies) will have no effect. Again, this is
due to the limitations imposed by the SQL interface.
Connection using SSL - You cannot connect to SAP HANA instances configured to use SSL.
Support for Attribute views - Power BI can connect to Analytic and Calculation views, but cannot connect
directly to Attribute views.
Support for Catalog objects - Power BI cannot connect to Catalog objects.
Change to Variables after publish - You cannot change the values for any SAP HANA variables directly in
the Power BI service, after the report is published.

Known issues
The following list describes all known issues when connecting to SAP HANA (DirectQuery) using Power BI.
SAP HANA issue when query for Counters, and other measures - Incorrect data is returned from
SAP HANA if connecting to an Analytical View, and a Counter measure and some other ratio measure,
are included in the same visual. This is covered by SAP Note 2128928 (Unexpected results when query a
Calculated Column and a Counter). The ratio measure will be incorrect in this case.
Multiple Power BI columns from single SAP HANA column - For some calculation views, where a
SAP HANA column is used in more than one hierarchy, SAP HANA exposes this as two separate
attributes. This results in two columns being created in Power BI. Those columns are hidden by default,
however, and all queries involving the hierarchies, or the columns directly, behave correctly.

Next steps
For more information about DirectQuery, check out the following resources:
DirectQuery in Power BI
Data sources supported by DirectQuery
DirectQuery and SAP BW
On-premises data gateway
 Assume referential integrity settings in Power BI
Desktop
1/14/2019 • 2 minutes to read • Edit Online

When connecting to a data source using DirectQuery, you can use the Assume Referential Integrity selection
to enable running more efficient queries against your data source. This feature has a few requirements of the
underlying data, and it is only available when using DirectQuery.
Setting Assume referential integrity enables queries on the data source to use INNER JOIN statements rather
than OUTER JOIN, which improves query efficiency.

Requirements for using Assume referential integrity

This is an advanced setting, and is only enabled when connecting to data using DirectQuery. The following
requirements are necessary for Assume referential integrity to work properly:
Data in the From column in the relationship is never Null or blank
For each value in the From column, there is a corresponding value in the To column
In this context, the From column is the Many in a One-to -Many relationship, or it is the column in the first table in
a One-to -One relationship.

Example of using Assume referential integrity

The following example demonstrates how Assume referential integrity behaves when used in data connections.
The example connects to a data source that includes an Orders table, a Products table, and a Depots table.
1. In the following image that shows the Orders table and the Products table, note that referential integrity
 exists between Orders[ProductID ] and Products[ProductID ]. The [ProductID ] column in the Orders
table is never Null, and every value also appears in the Products table. As such, Assume Referential
Integrity should be set to get more efficient queries (using this setting does not change the values shown in
visuals).

2. In the next image, notice that no referential integrity exists between Orders[DepotID ] and
Depots[DepotID ], because the DepotID is Null for some Orders. As such, Assume Referential Integrity
should not be set.

3. Finally, no referential integrity exists between Orders[CustomerID ] and Customers[CustID ] in the

following tables; the CustomerID contains some values (in this case, CustX) that do not exist in the
Customers table. As such, Assume Referential Integrity should not be set.

Setting Assume referential integrity

To enable this feature, select the checkbox next to Assume Referential Integrity as shown in the following image.
When selected, the setting is validated against the data to ensure there are no Null or mismatched rows. However,
for cases with a very large number of values, the validation is not a guarantee that there are no referential integrity
issues.
In addition, the validation occurs at the time of editing the relationship, and does not reflect any subsequent
changes to the data.

What happens if you incorrectly set Assume referential integrity?

If you set Assume Referential Integrity when there are referential integrity issues in the data, this will not result
in errors. However, it will result in apparent inconsistencies in the data. For example, in the case of the relationship
to the Depots table described above, it would result in the following:
A visual showing the total Order Qty would show a value of 40
A visual showing the total Order Qty by Depot City would show a total value of only 30, because it would not
include Order ID 1, where DepotID is Null.

Next steps
Learn more about DirectQuery
Get more information about Relationships in Power BI
Learn more about Relationship View in Power BI Desktop.
 Use the SAP BW Connector in Power BI Desktop
2/15/2019 • 10 minutes to read • Edit Online

With Power BI Desktop, you can access SAP Business Warehouse (BW ) data.
For information about how SAP customers can benefit from connecting Power BI to their existing SAP Business
Warehouse (BW ) systems, see the Power BI and SAP BW whitepaper. For details about using DirectQuery with
SAP BW, see the article DirectQuery and SAP Business Warehouse (BW ).
Starting with the June 2018 release of Power BI Desktop (and generally available with the October 2018
release), you can use the SAP BW connector with an implementation that has significant improvements in
performance and capabilities. This updated version of the SAP BW connector was developed by Microsoft and is
called Implementation 2.0. You can select either version 1 (v1) of the SAP BW Connector, or the
Implementation 2.0 SAP Connector. The following sections describe the installation of each version, in turn.
You can choose one or the other connector when connecting to SAP BW from Power BI Desktop.
We suggest you use the Implementation 2.0 SAP Connector whenever possible.

Installation of version 1 of the SAP BW Connector

We recommend using the Implementation 2.0 SAP Connector whenever possible (see instructions in the
following section). This section describes installation of version 1 of the SAP BW Connector, which you can
install by taking the following installation steps:
1. Install the SAP NetWeaver library on your local machine. You can get the SAP Netweaver library from
your SAP administrator, or directly from the SAP Software Download Center. Since the SAP Software
Download Center changes its structure frequently, more specific guidance for navigating that site is not
available. The SAP NetWeaver library is usually included also in the SAP Client Tools installation.
You may be able to search for SAP Note #1025361 to get the download location for the most recent
version. Make sure the architecture for the SAP NetWeaver library (32-bit or 64-bit) matches your Power
BI Desktop installation, then install all files included in the SAP NetWeaver RFC SDK according to the
SAP Note.
2. The Get Data dialog includes an entry for SAP Business Warehouse Application Server and SAP
Business Warehouse Message Server in the Database category.
Installation of Implementation 2.0 SAP Connector
Implementation 2.0 of the SAP Connector requires the SAP .NET Connector 3.0. You can download the SAP
.NET Connector 3.0 from SAP’s website using the following link:
SAP .NET Connector 3.0
Access to the download requires a valid S -user. Customers are encouraged to contact their SAP Basis team to get
the SAP .NET Connector 3.0.
The connector comes in 32-bit and 64-bit versions, and users must choose the version that matches their Power BI
Desktop installation. At the time of this writing, the website lists two versions (for .NET 4.0 framework):
SAP Connector for Microsoft .NET 3.0.20.0 for Windows 32-bit (x86) as zip file (6.896 KB ), January 16, 2018
SAP Connector for Microsoft .NET 3.0.20.0 for Windows 64-bit (x64) as zip file (7.180 KB ), January 16, 2018
When installing, in the Optional setup steps window, make sure you select the Install assemblies to GAC option
as shown in the following image.
 NOTE
The first version of SAP BW implementation required Netweaver DLLs; if you're using Implementation 2.0 of the SAP
Connector, and not using the first version, the Netweaver DLLs are not required.

Version 1 SAP BW Connector features

The version 1 SAP BW Connector in Power BI Desktop let you import data from your SAP Business
Warehouse Server cubes, or use DirectQuery.
To learn more about the SAP BW connector and how to use it with DirectQuery, take a look at the DirectQuery
and SAP Business Warehouse (BW ) article.
When connecting, you must specify a Server, System Number, and Client ID to establish the connection.

You can also specify two additional Advanced options: Language code, and a custom MDX statement to run
against the specified server.
If no MDX statement was specified you are presented with the Navigator window, which displays the list of cubes
available in the server, with the option to drill down and select items from the available cubes, including
dimensions and measures. Power BI exposes queries and cubes exposed by the BW Open Analysis Interface
OLAP BAPIs.
When you select one or more items from the server, a preview of the output table is created, based on their
selection.
The Navigator window also provides a few Display Options that allow you to do the following:
Display Only Selected Items versus All Items (default view): This option is useful for verifying the final set
of items selected. An alternative approach to viewing this is to select the Column Names in the Preview area.
Enable Data Previews (default behavior): You can also control whether data previews should be displayed
in this dialog. Disabling data previews reduces the amount of server calls, since it no longer requests data for
the previews.
Technical Names: SAP BW supports the notion of technical names for objects within a cube. Technical names
allow a cube owner to expose user friendly names for cube objects, as opposed to only exposing the physical
names for those objects in the cube.

After selecting all necessary objects in the Navigator, you can decide what to do next, by selecting one of the
following buttons on the bottom of the Navigator window:
Selecting Load triggers loading the entire set of rows for the output table into the Power BI Desktop data
model, then takes you to Report view where you can begin visualizing the data or making further
modifications using the Data or Relationships views.
Selecting Edit brings up Query Editor, where you can perform additional data transformation and filtering
steps before the entire set of rows is brought into the Power BI Desktop data model.
In addition to importing data from SAP BW cubes, remember that you can also import data from a wide range of
other data sources in Power BI Desktop, and then you can combine them into a single report. This presents all
sorts of interesting scenarios for reporting and analytics on top of SAP BW data.

Using Implementation 2.0 SAP BW Connector

You must create a new connection to use Implementation 2.0 of the SAP BW Connector. To create a new
connection, take the following steps.
1. From the Get Data window, select either SAP Business Warehouse Application Server or SAP
Business Warehouse Message Server.
2. You're presented with the new connection dialog, which allows selection of the implementation. Selecting
 Implementation 2.0, as shown in the following image, enables the Execution mode, Batch size and Enable
characteristic structures options.

3. Select OK, and subsequently, the Navigator experience is the same as described in the earlier section for
the version 1 SAP BW Connector.
New options for Implementation 2.0
Implementation 2.0 supports the following options:
1. ExecutionMode - Specifies the MDX interface used to execute queries on the server. Valid options are the
following:

a. SapBusinessWarehouseExecutionMode.BasXml
b. SapBusinessWarehouseExecutionMode.BasXmlGzip
c. SapBusinessWarehouseExecutionMode.DataStream

The default value for this option is SapBusinessWarehouseExecutionMode.BasXmlGzip.

 Using SapBusinessWarehouseExecutionMode.BasXmlGzip may improve performance when experiencing
high latency for large datasets.
2. BatchSize - Specifies the maximum number of rows that will be retrieved at a time when executing an
MDX statement. A small number of rows will translate into more calls to the server while retrieving a large
dataset. A large number of rows may improve performance, but could cause memory issues on the SAP
BW server. The default value is 50000 rows.
3. EnableStructures - A logical value indicating whether characteristic structures are recognized. The default
value for this option is false. Affects the list of objects available for selection. Not supported in Native query
mode.
The ScaleMeasures option has been deprecated in this implementation. The behavior is now the same as setting
ScaleMeasures = false, that is always showing unscaled values.
Additional improvements for Implementation 2.0
The following bulleted list describes some of the additional improvements that come with the new
implementation:
Improved performance
Ability to retrieve several million rows of data, and fine tuning through the batch size parameter.
Ability to switch execution modes.
Support for compressed mode. Especially beneficial for high latency connections or large datasets.
Improved detection of Date variables
[Experimental] Expose Date (ABAP type DATS ) and Time (ABAP type TIMS ) dimensions as dates and times
respectively, instead of text values.
Better exception handling. Errors that occur in BAPI calls are now surfaced.
Column folding in BasXml and BasXmlGzip modes. For example, if the generated MDX query retrieves 40
columns but the current selection only needs 10, this request will be passed onto the server to retrieve a
smaller dataset.
Changing existing reports to use Implementation 2.0
Changing existing reports to use Implementation 2.0 is only possible in Import mode, and requires the
following manual steps.
1. Open an existing report, select Edit Queries in the ribbon, and then select the SAP Business Warehouse
query you would like to update.
2. Right-click the query and select Advanced Editor.
3. In the Advanced Editor change the SapBusinessWarehouse.Cubes call as follows:
a. Determine whether the query already contains an option record, such as what's shown in the following
example:

b. If so, add the Implementation 2.0 option, and remove the ScaleMeasures option, if present, as shown:
 c. If the query does not already include an options record, just add it. For example, if it has the following:

d. Just change it to:

4. Every effort has been made to make Implementation 2.0 of the SAP BW Connector compatible with
version 1 of the SAP BW Connector. However, there may be some differences due to the different SAP BW
MDX execution modes being used. To resolve any discrepancies, try switching between execution modes.

Troubleshooting
This section provides troubleshooting situations (and solutions) for working with th SAP BW connector.
1. Numeric data from SAP BW returns decimal points instead of commas. For example, 1,000,000 is returned
as 1.000.000.
SAP BW returns decimal data with either a , (comma) or a . (dot) as the decimal separator. To specify which
of those SAP BW should use for the decimal separator, the driver used by Power BI Desktop makes a call
to BAPI_USER_GET_DETAIL. This call returns a structure called DEFAULTS, which has a field called
DCPFM that stores Decimal Format Notation. It takes one of the following three values:

‘ ‘ (space) = Decimal point is comma: N.NNN,NN

'X' = Decimal point is period: N,NNN.NN
'Y' = Decimal point is N NNN NNN,NN

Customers who have reported this issue found that the call to BAPI_USER_GET_DETAIL is failing for a
particular user (the user who is showing the incorrect data), with an error message similar to the following:

You are not authorized to display users in group TI:

<item>
<TYPE>E</TYPE>
<ID>01</ID>
<NUMBER>512</NUMBER>
<MESSAGE>You are not authorized to display users in group TI</MESSAGE>
<LOG_NO/>
<LOG_MSG_NO>000000</LOG_MSG_NO>
<MESSAGE_V1>TI</MESSAGE_V1>
<MESSAGE_V2/>
<MESSAGE_V3/>
<MESSAGE_V4/>
<PARAMETER/>
<ROW>0</ROW>
<FIELD>BNAME</FIELD>
<SYSTEM>CLNTPW1400</SYSTEM>
</item>
 To solve this error, users must ask their SAP admin to grant the SAPBW user being used in Power BI the
right to execute BAPI_USER_GET_DETAIL. It’s also worth verifying that the user has the required DCPFM
value, as described earlier in this troubleshooting solution.
2. Connectivity for SAP BEx queries
You can perform BEx queries in Power BI Desktop by enabling a specific property, as shown in the
following image:

3. The Navigator window does not display a data preview and instead provides an object reference not set to
an instance of an object error message.
SAP users need access to specific BAPI function modules to get metadata and retrieve data from SAP BW's
InfoProviders. These include:
BAPI_MDPROVIDER_GET_CATALOGS
BAPI_MDPROVIDER_GET_CUBES
BAPI_MDPROVIDER_GET_DIMENSIONS
BAPI_MDPROVIDER_GET_HIERARCHYS
BAPI_MDPROVIDER_GET_LEVELS
BAPI_MDPROVIDER_GET_MEASURES
BAPI_MDPROVIDER_GET_MEMBERS
BAPI_MDPROVIDER_GET_VARIABLES
BAPI_IOBJ_GETDETAIL
To solve this issue, verify that the user has access to the various MDPROVIDER modules as well as
BAPI_IOBJ_GETDETAIL. To further troubleshoot this or similar issues, select Enable tracing on the
Diagnostics window within Power BI Desktop's Options. Attempt to retrieve data from SAP BW while
 tracing is active, and examine the trace file for more detail.

SAP BW Connection support

The following table details the current support for SAP BW.

PRODUCT MODE AUTHENTICATION CONNECTOR SNC LIBRARY SUPPORTED

Power BI Any User / password Application N/A Yes

Desktop Server

Power BI Any Windows Application sapcrypto + Yes

Desktop Server gsskrb5/gx64krb
5

Power BI Any Windows via Application sapcrypto + Yes

Desktop impersonation Server gsskrb5/gx64krb
5

Power BI Any User / password Message Server N/A Yes

Desktop

Power BI Any Windows Message Server sapcrypto + Yes

Desktop gsskrb5/gx64krb
5

Power BI Any Windows via Message Server sapcrypto + Yes

Desktop impersonation gsskrb5/gx64krb
5

Power BI Import Same as Power BI

Gateway Desktop

Power BI DirectQuery User / password Application N/A Yes

Gateway Server

Power BI DirectQuery Windows via Application sapcrypto + Yes

Gateway impersonation Server gsskrb5/gx64krb
(fixed user, no 5
SSO)

Power BI DirectQuery Use SSO via Application only with Yes

Gateway Kerberos for Server gsskrb5/gx64krb
DirectQuery 5
queries option

Power BI DirectQuery User / password Message Server N/A Yes

Gateway

Power BI DirectQuery Windows via Message Server sapcrypto + Yes

Gateway impersonation gsskrb5/gx64krb
(fixed user, no 5
SSO)
 PRODUCT MODE AUTHENTICATION CONNECTOR SNC LIBRARY SUPPORTED

Power BI DirectQuery Use SSO via Message Server sapcrypto + No

Gateway Kerberos for gsskrb5/gx64krb
DirectQuery 5
queries option

Next steps
For more information about SAP and DirectQuery, check out the following resources:
DirectQuery and SAP HANA
DirectQuery and SAP Business Warehouse (BW )
DirectQuery in Power BI
Data Sources supported by DirectQuery
Power BI and SAP BW whitepaper
 Use OneDrive for Business links in Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

Many people have Excel workbooks stored on their OneDrive for Business drive that would be great for use with
Power BI Desktop. With Power BI Desktop, you can use online links for Excel files stored in OneDrive for
Business to create reports and visuals. You can use a OneDrive for Business group account, or your individual
OneDrive for Business account.
Getting an online link from OneDrive for Business does require a few specific steps. The following sections
explain those steps, which let you share the file link among groups, across different machines, and with your
coworkers.

Get a link from Excel, starting in the browser

1. Navigate to your OneDrive for Business location using a browser. Right-click the file you want to use, and
select Open in Excel.

NOTE
Your browser interface might not look exactly like the following image. There are many ways to select Open in Excel
for files in your OneDrive for Business browser interface. You can use any option that allows you to open the file in
Excel.

2. In Excel, select File > Info and select the link above the Protect Workbook button. Select Copy link to
clipboard (your version might say Copy path to clipboard).
Use the link in Power BI Desktop
In Power BI Desktop, you can use the link you just copied to the clipboard. Take the following steps:
1. In Power BI Desktop, select Get Data > Web.

2. Paste the link into the From Web dialog (do not select OK yet).
3. Notice the ?web=1 string at the end of the link - you must remove that portion of the Web URL string
before selecting OK, in order for Power BI Desktop to properly navigate to your file.
4. If Power BI Desktop prompts you for credentials, choose either Windows (for on-premises SharePoint
sites) or Organizational Account (for Office 365 or OneDrive for Business sites).

A Navigator window appears, allowing you to select from the list of tables, sheets, and ranges found in the Excel
workbook. From there, you can use the OneDrive for Business file just like any other Excel file, and create reports
and use it in datasets like you would with any other data source.

NOTE
To use a OneDrive for Business file as a data source in the Power BI service, with Service Refresh enabled for that file,
make sure you select OAuth2 as the Authentication method when configuring your refresh settings. Otherwise, you may
encounter an error (such as Failed to update data source credentials) when you attempt to connect or to refresh. Selecting
OAuth2 as the authentication method remedies that credentials error.
 Facebook connector for Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

The Facebook connector in Power BI Desktop relies on the Facebook Graph API. As such, features and availability
may vary over time.
You can see a tutorial about the Facebook Connector for Power BI Desktop.
Facebook expired v1.0 of its Graph API on April 30th 2015. Power BI uses the Graph API behind the scenes for the
Facebook connector, allowing you to connect to your data and analyze it.
Queries that were built before April 30th 2015 may no longer work or return less data. Subsequent to April 30th
2015, Power BI leverages v2.8 in all calls to the Facebook API. If your query was built prior to April 30, 2015 and
you have not used it since, you’ll likely need to authenticate again, to approve the new set of permissions that we’ll
ask for.
Although we attempt to release updates in accordance with any changes, the API may change in a way that affects
the results of the queries we generate. In some cases, certain queries may no longer be supported. Due to this
dependency we cannot guarantee the results of your queries when using this connector.
More details on the change in the Facebook API are available here.
 Google Analytics connector for Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

NOTE
The Google Analytics content pack and the connector in Power BI Desktop rely on the Google Analytics Core Reporting API.
As such, features and availability may vary over time.

You can connect to Google Analytics data using the Google Analytics connector. To connect, follow these steps:
1. In Power BI Desktop, select Get Data from the Home ribbon tab.
2. In the Get Data window, select Online Services from the categories in the left pane.
3. Select Google Analytics from the selections in the right pane.
4. At the bottom of the window, select Connect.
You're prompted with a dialog that explains that the connector is a Third-Party Service, and warns about how
features and availability may change over time, and other clarifications.

When you select Continue, you're prompted to sign in to Google Analytics.

When you enter your credentials, you're prompted that Power BI would like to have offline access. This is how you
use Power BI Desktop to access your Google Analytics data.
Once you accept, Power BI Desktop shows that you're currently signed in.

Select Connect, and your Google Analytics data is connected to Power BI Desktop, and loads the data.

Changes to the API

Although we attempt to release updates in accordance with any changes, the API may change in a way that affects
the results of the queries we generate. In some cases, certain queries may no longer be supported. Due to this
dependency we cannot guarantee the results of your queries when using this connector.
More details on changes to the Google Analytics API can be found in their changelog.
 Project Online: connect to data through Power BI
Desktop
1/14/2019 • 2 minutes to read • Edit Online

You can connect to data in Project Online through Power BI Desktop.

Step 1: Download Power BI Desktop

1. Download Power BI Desktop, then run the installer to get Power BI Desktop on your computer.

Step 2: Connect to Project Online with OData

1. Open Power BI Desktop.
2. On the Welcome screen, select Get Data.
3. Choose OData feed and select Connect.
4. Enter the address for your OData feed in the URL box, and then click OK.
If the address for your Project Web App site resembles https://<tenantname>.sharepoint.com/sites/pwa,
the address you’ll enter for your OData Feed is
https://<tenantname>.sharepoint.com/sites/pwa/_api/Projectdata.
For our example, we’re using https://contoso.sharepoint.com/sites/pwa/default.aspx
5. Power BI Desktop will prompt you to authenticate with your Office 365 account. Select Organizational
account and then enter your credentials.

Please note that the account you use to connect to the OData feed must have at least Portfolio Viewer access to the
Project Web App site.
From here, you can choose which tables you would like to connect to and build a query. Want an idea of how to get
started? The following blog post shows how to build a burndown chart from your Project Online data. The blog
post refers to using Power Query to connect to Project Online, but this applies to Power BI Desktop as well.
Creating burndown charts for Project using Power Pivot and Power Query
 Shape Maps in Power BI Desktop (Preview)
1/14/2019 • 10 minutes to read • Edit Online

Create a Shape Map visual to compare regions on a map using color. Unlike the Map visual, Shape Map can't
show precise geographical locations of data points on a map. Instead, its main purpose is to show relative
comparisons of regions on a map by coloring them differently.
Shape Map visuals are based on ESRI/TopoJSON maps, which have the compelling ability to use custom maps
that you can create. Examples of custom maps are:geographical, seating arrangements, floor plans, and others. The
ability to use custom maps is not available in this Preview release of Shape Map.

Creating Shape Maps

You can test the Shape Map control with the maps that are shipping with this Preview release, or you can use
your own custom map as long as it meets the requirements outlined in the following section called Use Custom
Maps.
The Shape Map visual is in Preview, and must be enabled in Power BI Desktop. To enable Shape Map, select
File > Options and Settings > Options > Preview Features, then select the Shape Map Visual checkbox.
You'll need to restart Power BI Desktop after you make the selection.

Once Shape Map is enabled, click the Shape Map control from the Visualizations pane.
Power BI Desktop creates an empty Shape Map visual design canvas.

Take the following steps to create a Shape Map:

1. In the Fields pane, drag a data field that has the region names (or abbreviations) onto the Location bucket,
and a data measure field into the Color saturation bucket (you won't see a map yet).

NOTE
See the section titled Getting Map Data, below, for information on how to quickly get map data to test Shape Map.
2. In the Format settings pane, expand Shape, and select from the Standard Maps drop-down to show your
data. At this point, the rendering appears, as shown in the following image.
 NOTE
In the Region Keys section at the end of this article is a collection of tables that have map regions keys you can use
to test the Shape Map visual.

3. You can then modify the map projection and zooming settings, as well as the colors of data points, from the
Format settings pane. You can also modify zoom settings. For example, you can change colors, set
maximums and minimums, and so on.

4. You can also add a category data column to the Legend bucket, and classify the map regions based on
categories.

Use custom maps

You can use custom maps with Shape Map as long as they are in the TopoJSON format. If your map is in
another format, you can use online tools such as Map Shaper to convert your shapefiles or your GeoJSON maps
into the TopoJSON format.
To use your TopoJSON map file, add a ShapeMap visual to your report and add some data to the Location and
Color saturation buckets. Then, in the Visualizations pane with the Format section selected (shown as (1) in the
following image), expand the Shape section and select + Add Map.
Sample Custom Map
The Offices of the United States Attorneys release an annual fiscal report on their litigation and caseload data. All
of their reports can be found in the link below,
https://www.justice.gov/usao/resources/annual-statistical-reports
Since states can be divided into multiple districts, we have to use a custom shape map. By importing the
TopoJSON map of the U.S. judicial districts into Power BI Desktop, we can then visualize the annual fiscal
district attorney data. The image below shows an example of this map.
You can do interesting things with the individual state maps as well, and show more detail based on the districts it
contains.

If you’d like to experiment with this dataset and visualization, you can download the original PBIX file that was
used to generate this report using the following link.
Custom shape map demo .PBIX file

Getting map data

To quickly get data into a model so you can test Shape Map, you can copy one of the tables at the end of this
article, then select Enter Data from the Home ribbon.

If your data has multiple columns, you will need to use an editor like Excel to paste the data, then copy each data
column separately. You can then paste the data into Power BI Desktop. The top row is automatically identified as a
header.

You can enter a new column simply by typing a new column name (in the blank column to the right), then add
values in each cell, just like you can do in Excel. When finished, select Load and the table is added to the data
model for Power BI Desktop.
 NOTE
When working with countries or regions, use the three-letter abbreviation to ensure that geocoding works properly in map
visualizations. Do not use two-letter abbreviations, as some countries or regions may not be properly recognized.
If you only have two-letter abbreviations, check out this external blog post for steps on how to associate your two-letter
country/region abbreviations with three-letter country/region abbreviations.

Preview behavior and requirements

There are a few considerations and requirements for this Preview release of Shape Map:
The Shape Map visual is in Preview, and must be enabled in Power BI Desktop. To enable Shape Map, select
File > Options and Settings > Options > Preview Features, then select the Shape Map Visual checkbox.
Currently, you must also have the Color saturation bucket set in order for the Legend classification to work
properly.
The final release version of Shape Map will have a user interface that shows the map keys of the currently
selected map (there is no date set for final release, and Shape Map is still in Preview ). In this Preview release,
you can reference the map region keys in the tables found in the following Region Keys section of this article.
The Shape Map visual will plot up to a maximum of 1,000 data points.

Region keys
Use the following Region Keys in this Preview release to test Shape Map.
Australia: States
ID ABBR ISO NAME POSTAL

au-wa WA AU-WA Western Australia WA

au-vic Vic AU-VIC Victoria VIC

au-tas Tas AU-TAS Tasmania TAS

au-sa SA AU-SA South Australia SA

au-qld Qld AU-QLD Queensland QLD

au-nt NT AU-NT Northern Territory NT

au-nsw NSW AU-NSW New South Wales NSW

au-act ACT AU-ACT Australian Capital ACT

Territory

Austria: States
ID ISO NAME NAME-EN POSTAL

at-wi AT-9 Wien Vienna WI

at-vo AT-8 Vorarlberg Vorarlberg VO

 ID ISO NAME NAME-EN POSTAL

at-tr AT-7 Tirol Tyrol TR

at-st AT-6 Steiermark Styria ST

at-sz AT-5 Salzburg Salzburg SZ

at-oo AT-4 Oberösterreich Upper Austria OO

at-no AT-3 Niederösterreich Lower Austria NO

at-ka AT-2 Kärnten Carinthia KA

at-bu AT-1 Burgenland Burgenland BU

Brazil: States
ID

Tocantins

Pernambuco

Goias

Sergipe

Sao Paulo

Santa Catarina

Roraima

Rondonia

Rio Grande do Sul

Rio Grande do Norte

Rio de Janeiro

Piaui

Parana

Paraiba

Para

Minas Gerais
 ID

Mato Grosso

Maranhao

Mato Grosso do Sul

Distrito Federal

Ceara

Espirito Santo

Bahia

Amazonas

Amapa

Alagoas

Acre

Litigated Zone 1

Litigated Zone 2

Litigated Zone 3

Litigated Zone 4

Canada: Provinces
ID ISO NAME POSTAL

ca-nu CA-NU Nunavut NU

ca-nt CA-NT Northwest Territories NT

ca-yt CA-YT Yukon YT

ca-sk CA-SK Saskatchewan SK

ca-qc CA-QC Quebec QC

ca-pe CA-PE Prince Edward Island PE

ca-on CA-ON Ontario ON

ca-ns CA-NS Nova Scotia NS

 ID ISO NAME POSTAL

ca-nl CA-NL Newfoundland and Labrador NL

ca-nb CA-NB New Brunswick NB

ca-mb CA-MB Manitoba MB

ca-bc CA-BC British Columbia BC

ca-ab CA-AB Alberta AB

France: Regions
ID NAME NAME-EN

Alsace Alsace Alsace

Rhone-Alpes Rhône-Alpes Rhone-Alpes

Provence-Alpes-Cote d'Azur Provence-Alpes-Côte d'Azur Provence-Alpes-Cote d'Azur

Poitou-Charentes Poitou-Charentes Poitou-Charentes

Picardie Picardie Picardy

Pays de la Loire Pays de la Loire Pays de la Loire

Nord-Pas-de-Calais Nord-Pas-de-Calais Nord-Pas-de-Calais

Midi-Pyrenees Midi-Pyrénées Midi-Pyrenees

Lorraine Lorraine Lorraine

Limousin Limousin Limousin

Languedoc-Roussillon Languedoc-Roussillon Languedoc-Roussillon

Ile-del-France Île-de-France Ile-de-France

Haute-Normandie Haute-Normandie Upper Normandy

Franche-Comte Franche-Comté Franche-Comte

Corse Corse Corsica

Champagne-Ardenne Champagne-Ardenne Champagne-Ardenne

Centre-Val de Loire Centre-Val de Loire Centre-Val de Loire

Bretagne Bretagne Brittany

 ID NAME NAME-EN

Bourgogne Bourgogne Burgundy

Basse-Normandie Basse-Normandie Lower Normandy

Auvergne Auvergne Auvergne

Aquitaine Aquitaine Aquitaine

Germany: States
ID ISO NAME NAME-EN POSTAL

de-be DE-BE Berlin Berlin BE

de-th DE-TH Thüringen Thuringia TH

de-st DE-ST Sachsen-Anhalt Saxony-Anhalt ST

de-sn DE-SN Sachsen Saxony SN

de-mv DE-MV Mecklenburg- Mecklenburg- MV

Vorpommern Vorpommern

de-bb DE-BB Brandenburg Brandenburg BB

de-sh DE-SH Schleswig-Holstein Schleswig-Holstein SH

de-sl DE-SL Saarland Saarland SL

de-rp DE-RP Rheinland-Pfalz Rhineland-Palatinate RP

de-nw DE-NW Nordrhein-Westfalen North Rhine- NW

Westphalia

de-ni DE-NI Niedersachsen Lower Saxony NI

de-he DE-HE Hessen Hesse HE

de-hh DE-HH Hamburg Hamburg HH

de-hb DE-HB Bremen Bremen HB

de-by DE-BY Bayern Bavaria BY

de-bw DE-BW Baden-Württemberg Baden-Wurttemberg BW

Ireland: Counties
ID

Wicklow
 ID

Wexford

Westmeath

Waterford

Sligo

Tipperary

Roscommon

Offaly

Monaghan

Meath

Mayo

Louth

Longford

Limerick

Leitrim

Laoighis

Kilkenny

Kildare

Kerry

Galway

Dublin

Donegal

Cork

Clare

Cavan

Carlow

Italy: Regions
 ID ISO NAME NAME-EN POSTAL

it-vn IT-34 Veneto Veneto VN

it-vd IT-23 Valle d'Aosta Aosta Valley VD

it-um IT-55 Umbria Umbria UM

it-tt IT-32 Trentino-Alto Adige Trentino-South Tyrol TT

it-tc IT-52 Toscana Tuscany TC

it-sc IT-82 Sicilia Sicily SC

it-sd IT-88 Sardegna Sardinia SD

it-pm IT-21 Piemonte Piedmont PM

it-ml IT-67 Molise Molise ML

it-mh IT-57 Marche Marche MH

it-lm IT-25 Lombardia Lombardy LM

it-lg IT-42 Liguria Liguria LG

it-lz IT-62 Lazio Lazio LZ

it-fv IT-36 Friuli-Venezia Giulia Friuli-Venezia Giulia FV

it-er IT-45 Emilia-Romagna Emilia-Romagna ER

it-cm IT-72 Campania Campania CM

it-lb IT-78 Calabria Calabria LB

it-bc IT-77 Basilicata Basilicata BC

it-pu IT-75 Apulia Puglia PU

it-ab IT-65 Abruzzo Abruzzo AB

Mexico: States
ID ABREVIATURA ISO NAME NAME-EN POSTAL

mx-zac Zac. MX-ZAC Zacatecas Zacatecas ZA

mx-yuc Yuc. MX-YUC Yucatán Yucatan YU

mx-ver Ver. MX-VER Veracruz Veracruz VE

ID ABREVIATURA ISO NAME NAME-EN POSTAL

mx-tla Tlax. MX-TLA Tlaxcala Tlaxcala TL

mx-tam Tamps. MX-TAM Tamaulipas Tamaulipas TM

mx-tab Tab. MX-TAB Tabasco Tabasco TB

mx-son Son. MX-SON Sonora Sonora SO

mx-sin Sin. MX-SIN Sinaloa Sinaloa SI

mx-slp S.L.P. MX-SLP San Luis Potosí San Luis Potosi SL

mx-roo Q.R. MX-ROO Quintana Roo Quintana Roo QR

mx-que Qro. MX-QUE Querétaro Queretaro QE

mx-pue Pue. MX-PUE Puebla Puebla PU

mx-oax Oax. MX-OAX Oaxaca Oaxaca OA

mx-nle N.L. MX-NLE Nuevo León Nuevo Leon NL

mx-nay Nay. MX-NAY Nayarit Nayarit NA

mx-mor Mor. MX-MOR Morelos Morelos MR

mx-mic Mich. MX-MIC Michoacán Michoacan MC

mx-mex Méx. MX-MEX Estado de México Mexico State MX

mx-jal Jal. MX-JAL Jalisco Jalisco JA

mx-hid Hgo. MX-HID Hidalgo Hidalgo HI

mx-gro Gro. MX-GRO Guerrero Guerrero GR

mx-gua Gto. MX-GUA Guanajuato Guanajuato GT

mx-dur Dgo. MX-DUR Durango Durango DU

mx-dif Col. MX-DIF Ciudad de Mexico City DF

México

mx-col Coah. MX-COL Colima Colima CL

mx-coa Chis. MX-COA Coahuila Coahuila CA

mx-chh Chih. MX-CHH Chihuahua Chihuahua CH

mx-chp CDMX. MX-CHP Chiapas Chiapas CP

 ID ABREVIATURA ISO NAME NAME-EN POSTAL

mx-cam Camp. MX-CAM Campeche Campeche CM

mx-bcs B.C.S. MX-BCS Baja California Baja California BS

Sur Sur

mx-bcn B.C. MX-BCN Baja California Baja California BN

mx-agu Ags. MX-AGU Aguascalientes Aguascalientes AG

Netherlands: Provinces
ID ISO NAME NAME-EN

nl-zh NL-ZH Zuid-Holland South Holland

nl-ze NL-ZE Zeeland Zeeland

nl-ut NL-UT Utrecht Utrecht

nl-ov NL-OV Overijssel Overijssel

nl-nh NL-NH Noord-Holland North Holland

nl-nb NL-NB Noord-Brabant North Brabant

nl-li NL-LI Limburg Limburg

nl-gr NL-GR Groningen Groningen

nl-ge NL-GE Gelderland Gelderland

nl-fr NL-FR Fryslân Friesland

nl-fl NL-FL Flevoland Flevoland

nl-dr NL-DR Drenthe Drenthe

UK: Countries
ID ISO NAME

gb-wls GB-WLS Wales

gb-sct GB-SCT Scotland

gb-nir GB-NIR Northern Ireland

gb-eng GB-ENG England

USA: States
ID NAME POSTAL

us-mi Michigan MI

us-ak Alaska AK

us-hi Hawaii HI

us-fl Florida FL

us-la Louisiana LA

us-ar Arkansas AR

us-sc South Carolina SC

us-ga Georgia GA

us-ms Mississippi MS

us-al Alabama AL

us-nm New Mexico NM

us-tx Texas TX

us-tn Tennessee TN

us-nc North Carolina NC

us-ok Oklahoma OK

us-az Arizona AZ

us-mo Missouri MO

us-va Virginia VA

us-ks Kansas KS

us-ky Kentucky KY

us-co Colorado CO

us-md Maryland MD

us-wv West Virginia WV

us-de Delaware DE

us-dc District of Columbia DC

ID NAME POSTAL

us-il Illinois IL

us-oh Ohio OH

us-ca California CA

us-ut Utah UT

us-nv Nevada NV

us-in Indiana IN

us-nj New Jersey NJ

us-ri Rhode Island RI

us-ct Connecticut CT

us-pa Pennsylvania PA

us-ny New York NY

us-ne Nebraska NE

us-ma Massachusetts MA

us-ia Iowa IA

us-nh New Hampshire NH

us-or Oregon OR

us-mn Minnesota MN

us-vt Vermont VT

us-id Idaho ID

us-wi Wisconsin WI

us-wy Wyoming WY

us-sd South Dakota SD

us-nd North Dakota ND

us-me Maine ME

us-mt Montana MT
 ID NAME POSTAL

us-wa Washington WA

Next steps
Matrix visual in Power BI
Visualization types in Power BI
 Combine files (binaries) in Power BI Desktop
2/13/2019 • 2 minutes to read • Edit Online

One powerful approach to importing data into Power BI Desktop is to combine multiple files, which have the
same schema, into a single logical table. With the November 2016 release of Power BI Desktop (and subsequent
releases), this convenient and popular approach has been made more convenient and more expansive, as described
in this article.
To start the process of combining files from the same folder, select Get Data > File > Folder.

Previous combine files (binaries) behavior

Prior to the November 2016 release of Power BI Desktop, this functionality was called Combine Binaries, and
you could combine certain file types with the combine binaries transform, but there were limitations:
Transformations were not considered for each individual file before the files were combined into a single table.
As such, you often had to combine files, then filter out header values by filtering rows as part of the edit
process.
The Combine binaries transform only worked for text or CSV files, and didn't work on other supported file
formats such as Excel workbooks, JSON files, and others.
Customers asked for more intuitive operation of the combine binaries operation, so the transform was enhanced
and renamed combine files.

Current combine files behavior

Power BI Desktop now handles the combine files (binaries) more effectively. You start by selecting combine
files, either from the Home ribbon tab in Query Editor, or from the column itself.

The combine files transform now behaves as follows:

The combine files transform analyzes each input file, and determines the correct file format to use, such as
text or Excel workbook or JSON file.
The transform allows you to select a specific object from the first file, for example, an Excel workbook, to
extract.

The combine files then automatically performs the following queries:

Creates an example query that performs all the required extraction steps in a single file.
 Creates a function query that parameterizes the file/binary input to the exemplar query. The exemplar
query and the function query are linked, so that changes to the exemplar query are reflected in the
function query.
Applies the function query to the original query with input binaries (for example, the Folder query) so
it applies the function query for binary inputs on each row, then expands the resulting data extraction
as top-level columns.

With the new behavior of combine files, you can easily combine all files within a given folder as long as they have
the same file type and structure (such as the same columns).
In addition, you can easily apply additional transformation or extraction steps by modifying the automatically
created exemplar query, without having to worry about modifying or creating additional function query steps. Any
changes to the exemplar query are automatically generated in the linked function query.

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources,
check out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to CSV files in Power BI Desktop
Enter data directly into Power BI Desktop
 Data categorization in Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

In Power BI Desktop, you can specify the Data Category for a column so Power BI Desktop knows how it should
treat its values when in a visualization.
When Power BI Desktop imports data, not only does it get the data itself, it also gets information such as the table
and column names, whether it’s a primary key, etc. With that information, Power BI Desktop makes some
assumptions about how to give you a good default experience when creating a visualization.
Here’s an example: When Power BI Desktop detects a column has numeric values, you’ll probably want to
aggregate it in some way, so it’s placed in the Values area. Or, for a column with date time values, it assumes you’ll
probably use it as a time hierarchy axis on a line chart.
But, there are some cases that are a bit more challenging, like geography. Consider the following table from an
Excel worksheet:

Should Power BI Desktop treat the codes in the GeoCode column as an abbreviation for a Country or a US State?
It’s not clear because a code like this can mean either one. For instance, AL can mean Alabama or Albania, AR can
mean Arkansas or Argentina, or CA can mean California or Canada. It makes a difference when we go to chart our
GeoCode field on a map. Should Power BI Desktop show a picture of the world with countries highlighted or a
picture of the United States with states highlighted? You can specify a Data Category for data just like this. Data
categorization further refines the information Power BI Desktop can use to provide the best visualizations.
To specify a Data Category
1. In Report View or Data View, in the Fields list, select the field you want to be sorted by a different
categorization.
2. On the ribbon, in the Modeling tab, click on the Data Category: drop down list. This shows the list of
possible data categories you can choose for your column. Some selections might be disabled if they won’t
work with the current data type of your column. For example, if a column is a binary data type, Power BI
Desktop won’t let you choose geographic data categories.
And that’s it! Any behavior that normally accrues to a visual will now work automatically.
You might also be interested in learning about geographic filtering for Power BI mobile apps.
 Tag barcodes in Power BI Desktop for the mobile
apps
1/14/2019 • 2 minutes to read • Edit Online

In Power BI Desktop, you can categorize data in a column, so Power BI Desktop knows how to treat values in
visuals in a report. You can also categorize a column as Barcode. When you or your colleagues scan a barcode on
a product with the Power BI app on the iPhone, you see any report that includes that barcode. When you open the
report in the mobile app, Power BI automatically filters the report to data related to that barcode.
1. In Power BI Desktop, switch to Data View.
2. Select a column with barcode data. See the list of supported barcode formats below.
3. On the Modeling tab, select Data Category > Barcode.

4. In Report view, add this field to the visuals you want filtered by the barcode.
5. Save the report and publish it to the Power BI service.
Now when you open the scanner on the Power BI app for iPhone and scan a barcode, you see this report in the list
of reports. When you open the report, its visuals are filtered by the product barcode you scanned.

Supported barcode formats

These are the barcodes Power BI recognizes if you can tag them in a Power BI report:
UPCECode
Code39Code
A39Mod43Code
EAN13Code
EAN8Code
93Code
128Code
PDF417Code
Interleaved2of5Code
ITF14Code
Next steps
Scan a barcode from the Power BI app on your iPhone
Issues with scanning barcodes on an iPhone
Data categorization in Power BI Desktop
Questions? Try asking the Power BI Community
 Set geographic filters in Power BI Desktop for the
mobile apps
1/14/2019 • 2 minutes to read • Edit Online

In Power BI Desktop, you can categorize geographical data for a column, so Power BI Desktop knows how to treat
values in visuals in a report. As an added benefit, when you or your colleagues view that report in the Power BI
mobile apps, Power BI automatically provides geographical filters that match where you are.
For example, say you're a sales manager traveling to meet customers, and you'd like to quickly filter the total sales
and revenue for the specific customer you're planning to visit. You want to break out the data for your current
location, whether by state, city, or an actual address. Later, if you have time left, you'd like to visit other customers
located nearby. You can filter the report by your location to find those customers.

NOTE
You can only filter by location in the mobile app if the geographic names in the report are in English for example, "New York
City" or "Germany".

Identify geographic data in your report

1. In Power BI Desktop, switch to Data View .
2. Select a column with geographic data for example, a City column.

3. On the Modeling tab, select Data Category, then the correct category in this example, City.
4. Continue setting geographic data categories for any other fields in the model.

NOTE
You can set multiple columns for each data category in a model, but if you do the model can't filter for geography in
the Power BI mobile app. To use geographic filtering in the mobile apps, set only one column for each data category
for example, only one City column, one State or Province column, and one Country column.

Create visuals with your geographic data

1. Switch to Report view , and create visuals that use the geographic fields in your data.

In this example, the model also contains a calculated column that brings city and state together in one
column. Read about creating calculated columns in Power BI Desktop.
2. Publish the report to the Power BI service.

View the report in Power BI mobile app

1. Open the report in any of the Power BI mobile apps.
2. If you're in a geographic location with data in the report, you can filter it automatically to your location.

Read more about filtering a report by location in the Power BI mobile apps.

Next steps
Data categorization in Power BI Desktop
Questions? Try asking the Power BI Community
 Using calculated columns in Power BI Desktop
1/14/2019 • 3 minutes to read • Edit Online

With calculated columns, you can add new data to a table already in your model. But instead of querying and
loading values into your new column from a data source, you create a Data Analysis Expressions (DAX) formula
that defines the column’s values. In Power BI Desktop, calculated columns are created by using the New Column
feature in Report View.
Unlike custom columns created as part of a query by using Add Custom Column in Query Editor, calculated
columns created in Report View or Data View are based on data you’ve already loaded into the model. For
example, you might choose to concatenate values from two different columns in two different but related tables,
perform addition, or extract substrings.
Calculated columns you create appear in the Fields list just like any other field, but they’ll have a special icon
showing its values are the result of a formula. You can name your columns whatever you want, and add them to a
report visualization just like other fields.

Calculated columns calculate results by using Data Analysis Expressions (DAX), a formula language meant to work
with relational data like in Power BI Desktop. DAX includes a library of over 200 functions, operators, and
constructs, providing immense flexibility in creating formulas to calculate results for just about any data analysis
need. To learn more about DAX, see the Learn more section at the end of this article.
DAX formulas are similar to Excel formulas. In fact, DAX has many of the same functions as Excel. DAX functions,
however, are meant to work over data interactively sliced or filtered in a report, like in Power BI Desktop. Unlike
Excel, where you can have a different formula for each row in a table, when you create a DAX formula for a new
column, it will calculate a result for every row in the table. Column values are recalculated as necessary, like when
the underlying data is refreshed and values have changed.

Let’s look at an example

Jeff is a shipping manager at Contoso. He wants to create a report showing the number of shipments to different
cities. He has a Geography table with separate fields for city and state. But, Jeff wants his reports to show City,
State as a single value on the same row. Right now, Jeff’s Geography table doesn’t have the field he wants.
But with a calculated column, Jeff can simply put together, or concatenate, the cities from the City column with the
states from the State column.
Jeff right clicks on the Geography table and then clicks New Column. He then enters the following DAX formula
into the formula bar:

This formula simply creates a new column named CityState, and for each row in the Geography table, it takes
values from the City column, adds a comma and a space, and then concatenates values from the State column.
Now Jeff has the field he wants.

He can add it to his report canvas along with the number of shipments. Very quickly and with minimal effort, Jeff
now has a City, State field he can add to just about any type of visualization. Jeff sees that when he creates a map
visualization, Power BI Desktop even knows how to read the City, State values in his new column.

Learn more
We’ve only provided a quick introduction to calculated columns here. Be sure to see the Tutorial: Create calculated
columns in Power BI Desktop tutorial, where you can download a sample file and get step-by-step lessons on how
to create more columns.
To learn more about DAX, see DAX basics in Power BI Desktop.
To learn more about columns you create as part of a query, see the Create custom columns section in Common
query tasks in Power BI Desktop.
 Using calculated tables in Power BI Desktop
2/13/2019 • 2 minutes to read • Edit Online

With calculated tables, you can add a new table to the model. But instead of querying and loading values into your
new table's columns from a data source, you create a Data Analysis Expressions (DAX) formula that defines the
table’s values. In Power BI Desktop, calculated tables are created by using the New Table feature in Report View or
Data View.
Most of the time, you import data into your model from an external data source. However, calculated tables
provide certain advantages. Calculated tables are generally best for intermediate calculations and data you want
stored as part of the model rather than calculated on the fly or as part of a query.
Unlike tables created as part of a query, calculated tables created in Report View or Data View are based on data
you’ve already loaded into the model. For example, you might choose to union or cross join two tables.
Just like normal tables, calculated tables can have relationships with other tables. The columns in your calculated
table have data types, formatting, and can belong to a data category. You can name your columns whatever you
want, and add them to a report visualization just like other fields. Calculated tables are re-calculated if any of the
tables it pulls data from are refreshed or updated in any way.
Calculated tables calculate results by using Data Analysis Expressions (DAX), a formula language meant to work
with relational data like in Power BI Desktop. DAX includes a library of over 200 functions, operators, and
constructs, providing immense flexibility in creating formulas to calculate results for just about any data analysis
need.

Let’s look at an example

Jeff, a project manager at Contoso, has a table with employees in the Northwest and another table with employees
in the Southwest. Jeff wants to put the two tables together into a single table.
NorthwestEmployees

SouthwestEmployees

Putting these two tables together with a calculated table is quite easy. While Jeff can create a calculated table in
either Report View or Data View, it’s a bit easier to do it in Data View because he can immediately see his new
calculated table.
In Data View, on the Modeling tab, Jeff clicks New Table. A formula bar appears.
Jeff then enters the following formula:

A new table named Western Region Employees is created.

Jeff’s new Western Region Employees table appears just like any other table in the Fields list. He can create
relationships to other tables, add calculated columns and measures, and add any of its fields to reports just like any
other table.

Functions for calculated tables

Calculated tables can be defined by any DAX expression that returns a table, including a simple reference to
another table. For example:

You can use calculated tables with DAX to solve many analytical problems. We’ve only provided a quick
introduction to calculated tables here. As you start working with calculated tables, here are some of the more
common DAX table functions you might find useful:
DISTINCT
VALUES
CROSSJOIN
UNION
NATURALINNERJOIN
NATURALLEFTOUTERJOIN
INTERSECT
CALENDAR
CALENDARAUTO
See the DAX Function Reference for these and other table returning DAX functions.
 Measures in Power BI Desktop
2/13/2019 • 3 minutes to read • Edit Online

Power BI Desktop helps you create insights into your data with just a few clicks. But sometimes that data just
doesn’t include everything you need to answer some of your most important questions. Measures can help you
get there.
Measures are used in some of the most common data analyses. For example sums, averages, minimum or
maximum values, counts, or more advanced calculations you create yourself using a DAX formula. The calculated
results of measures are always changing in response to your interaction with your reports, allowing for fast and
dynamic ad-hoc data exploration. Let’s take a closer look.

Understanding measures
In Power BI Desktop, measures are created and used in Report View or Data View. Measures you create
yourself appear in the Fields list with a calculator icon. You can name measures whatever you want, and add them
to a new or existing visualization just like any other field.

NOTE
You might also be interested in quick measures, which are ready-made measures you can select from dialog boxes. They're
a good way to quickly create measures, and also a good way to learn DAX syntax, since their automatically created DAX
formulas are available to review. Check out the article: quick measures.

Data Analysis Expressions

Measures calculate a result from an expression formula. When you create your own measures, you’ll use the Data
Analysis Expressions (DAX) formula language. DAX includes a library of over 200 functions, operators, and
constructs. Its library provides immense flexibility in creating measures to calculate results for just about any data
analysis need.
DAX formulas are a lot like Excel formulas. DAX even has many of the same functions as Excel, such like DATE,
SUM, and LEFT. But, DAX’s functions are meant to work with relational data like we have in Power BI Desktop.
Let’s look at an example
Jan is a sales manager at Contoso. She’s been asked to provide reseller sales projections over the next fiscal year.
Jan decides to base the estimates on last year’s sales amounts, with a six percent annual increase resulting from
various promotions that are scheduled over the next six months.
To report the estimates, Jan imports last year’s sales data into Power BI Desktop. She finds the SalesAmount field
in the Reseller Sales table. Because the imported data only contains sales amounts for last year, Jan renames the
SalesAmount field to Last Years Sales. Jan then drag Last Years Sales onto the report canvas. It appears in a chart
visualization as single value that is the sum of all reseller sales from last year.
Jan notices that even though she did not specify a calculation herself, one has been provided automatically. Power
BI Desktop created its own measure by summing up all of the values in Last Years Sales.
But, Jan needs a measure to calculate sales projections for the coming year, which will be based on last year’s sales
multiplied by 1.06 to account for the expected 6 percent increase in business. For this calculation, she’ll create her
own measure. Using the New Measure feature, she creates a new measure, then enters the following DAX
formula:

Projected Sales = SUM('Sales'[Last Years Sales])*1.06

Jan then drags her new Projected Sales measure into the chart.

Quickly and with minimal effort, Jan now has a measure to calculate projected sales. Jan can further analyze her
projections by filtering on specific resellers or by adding other fields to her report.

Data categories for measures

You can also pick data categories for measures.
Among other things, this enables you to use measures to dynamically create URLs, and mark the data category as
a Web URL.
You could create tables that display the measures as Web URLs, and be able to click on the URL that's created
based on your selection. This is especially useful when you want to link to other Power BI reports with URL filter
parameters.

Learn more
We’ve only provided you with a quick introduction to measures here, but there’s a lot more to help you learn how
to create your own. Be sure to see the Tutorial: Create your own measures in Power BI Desktop, where you can
download a sample file and get step-by-step lessons on how to create more measures.
To dive a little deeper into DAX, be sure to check out DAX basics in Power BI Desktop. The Data Analysis
Expressions Reference provides detailed articles on each of the functions, syntax, operators, and naming
conventions. DAX has been around for several years in Power Pivot in Excel and SQL Server Analysis Services, so
there are many other great resources available, too. Be sure to check out the DAX Resource Center Wiki, where
influential members of the BI community share their knowledge of DAX.
 Edit Q&A linguistic schema and add phrasings in
Power BI Desktop
1/14/2019 • 16 minutes to read • Edit Online

Using common phrases and natural language to ask questions of your data is powerful. Even more powerful is
when your data answers, which is what Q&A in Power BI lets you do. When you ask Power BI Q&A a question, it
makes a best effort to answer correctly.
But for even better Q&A interactions, there are ways to improve the answers -- one way is by editing the linguistic
schema.
It allstarts with your enterprise data. The better the data model, the easier it will be for users to get quality
answers.One way to improve the model is to add a linguistic schema that defines and categorizes terminology and
relationships between table and column names in your dataset. Power BI Desktop is where you manage your
linguistic schemas.

What is a linguistic schema

A linguistic schema describes terms and phrases that Q&A should understand for objects within a dataset,
including parts of speech, synonyms, and phrasings that relate to that dataset. When you import or connect to a
dataset, Power BI creates a linguistic schema based on the structure of the dataset. When you ask Q&A a question,
it looks for matches and relationships in the data to figure out the intention of your question. For example, it looks
for nouns, verbs, adjectives, phrasings, and other elements. And it looks for relationships, such as which columns
are objects of a verb.
You're probably familiar with parts of speech (if not, see below ), but phrasings may be a new term for you. A
phrasing is how you talk about (or “phrase”) the relationships between things. For example, to describe the
relationship between customers and products, you might say “customers buy products”. Or to describe the
relationship between customers and ages, you might say “ages indicate how old customers are”. Or to describe the
relationship between customers and phone numbers, you might simply say “customers have phone numbers”.
These phrasings come in a variety of shapes and sizes. Some correspond directly with relationships in the data
model. Some relate columns with their containing tables. Others relate multiple tables and columns together in
complex relationships. In all cases, they describe how things are related using everyday terms.
Linguistic schemas are saved in a YAML format. This format is related to the popular JSON format but provides a
more flexible and easier-to-read syntax. Linguistic schemas can be edited, exported, and imported into Power BI
Desktop.

Prerequisites
If you haven't already read the article on improving your data model for Q&A, you may want to read that
article first. It includes numerous tips for designing and improving your data model and an important
section on adding synonyms.
There are two sides to Q&A. The first side is the preparation, or "modeling." The second side is asking
questions and exploring the data, or "consuming."In some companies, employees known as Data Modelers
or IT Admins may be the ones to assemble the datasets, create the data models, and publish the datasets to
Power BI. While a second set of employees may be the ones to "consume" the data online. In other
companies, these roles may be combined.
 This topic is for the data modelers. The people who take a dataset and optimize it to provide the best
possible Q&A results.
Sample .yaml and .pbix files
YAML file editor, we recommend Visual Studio Code
Set up an editor for YAML files
We recommend using Visual Studio Code to edit linguistic schema YAML files. Visual Studio Code includes out-of-
the-box support for YAML files and can be extended to specifically validate the Power BI linguistic schema format.
1. Install Visual Studio Code.
2. Select the sample linguistic schema that you saved earlier: YAML file (SummerOlympics.lsdl.yaml).
3. Select Visual Studio Code and Always use this app to open .yaml files.

4. In Visual Studio Code, install the YAML Support by Red Hat extension.
a. Select the Extensions tab (last one on the left) or CTRL+SHIFT+X.

b. Search for "yaml" and select YAML Support by Red Hat in the list.
c. Select Install > Reload.
Working with linguistic schemas
Linguistic schemas can be edited, imported, and exported in Relationship view in Power BI Desktop. One way to
edit a linguistic schema is to add synonyms to the Synonyms pane. You don't have to open the YAML file.

The other way to edit a linguistic schema is to export and edit the YAML file directly. When you edit a linguistic
schema YAML file, you tag columns in the table as different grammatical elements, and define words that a
colleague might use to phrase a question. For instance, you state the columns that are the subject and the object of
the verb. You add alternative words that colleagues can use to refer to tables, columns, and measures in your
model.

Before you can edit a linguistic schema, you must open (export) it from Power BI Desktop. Saving the YAML file
back to the same location is considered importing. But you can also import other YAML files instead. If, for
instance, you have a similar dataset and you've already put in a lot of work adding parts of speech, identifying
relationships, creating phrasings, and creating synonyms.
Q&A uses all this information together with any enhancements that you make to provide a better answer, auto
completion, and summary of the questions.

Edit a linguistic schema

When you first export your linguistic schema from Power BI Desktop, most or all of the content in the file will be
automatically generated by the Q&A engine. These generated entities, words (synonyms), relationships, and
phrasings are designated with a State: Generated tag and are included in the file mostly for informational
purposes but can be a useful starting point for your own changes.

NOTE
The sample YAML file included with this tutorial does not contain State:Generated or State:Deleted tags since it has been
specially-prepared for this tutorial. To see these tags, open an unedited .pbix file in Relationship view and export the linguistic
schema.

When you import your linguistic schema file back into Power BI Desktop, anything that is marked State:
Generated is ignored (and later regenerated) so if you’d like to make a change to some generated content, make
sure to remove the corresponding State: Generated tag as well. Similarly, if you want to remove some generated
content, you’ll need to change the State: Generated tag to State: Deleted so that it won’t be regenerated when
you import your linguistic schema file.
1. Open the dataset in Power BI Desktop Relationship view.
2. Select the Modeling tab and choose Export linguistic schema.
3. Select Visual Code (or another editor).
4. Make your edits and save the YAML file.
5. From Power BI Desktop, select Relationship view > Modeling tab > Linguistic Schema > Import
linguistic schema.
6. Navigate to the location where you saved the edited YAML file and select it. A Success message lets you
know that the linguistic schema YAML file was successfully imported.
Add phrasings to the linguistic schema
A phrasing is how you talk about (or “phrase”) the relationships between things. For example, to describe the
relationship between customers and products, you might say “customers buy products”. Or to describe the
relationship between customers and ages, you might say “ages indicate how old customers are”. Or to describe the
relationship between athletes and medals, you could say “athletes win medals”.
These phrasings come in a variety of shapes and sizes. Some correspond directly with relationships in the semantic
model. Some relate columns with their containing tables. Others relate multiple tables and columns together in
complex relationships. In all cases, they describe how things are related using everyday terms.

Where do phrasings come from?

Power BI adds many simple phrasings to the linguistic schema automatically, based on the structure of the model
and some guesses based on column names. For example:
Most columns will be related to their containing table with a simple phrasing like “products have descriptions”.
Model relationships result in default phrasings for both directions of the relationship like “orders have products”
and “products have orders”.
Some model relationships can, based on their column names, get a more complex default phrasing like “orders
are shipped to cities”.
Your users will talk about things in plenty of ways that Q&A can’t guess, however. For those phrasings, you may
want to add your own phrasings manually.

Why should I add phrasings?

The first reason for adding a phrasing is to define a new term. For example, if you want to be able to ask “list the
oldest customers”, you must first teach Q&A what you mean by “old”. You would do so by adding a phrasing like
“ages indicate how old customers are”.
The second reason for adding a phrasing is to resolve ambiguity. Basic keyword search only goes so far when
words have more than one meaning. For example, “flights to Chicago” isn't the same as “flights from Chicago”. But
Q&A won’t know which one you mean unless you add the phrasings “flights are from departure cities” and “flights
are to arrival cities”. Similarly, Q&A will only understand the distinction between “cars that John sold to Mary” and
“cars that John bought from Mary” after you add the phrasings “customers buy cars from employees” and
“employees sell customers cars”.
The final reason for adding a phrasing is to improve restatements. Rather than Q&A echoing back to you “Show
the customers and their products”, it would be clearer if it said “Show the customers and the products they bought”
or “Show the customers and the products they reviewed”, depending on how it understood the question. Adding
custom phrasings allows restatements to be more explicit and unambiguous.

What kinds of phrasings are there?

To understand the different types of phrasings, you’re first going to need to remember a couple of basic grammar
terms:
 A noun is a person, place, or thing.
Examples: car, teenager, Marty, flux capacitor
A verb is an action or state of being.
Examples: hatch, burst, devour, eject
An adjective is a descriptive word that modifies a noun.
Examples: powerful, magical, golden, stolen
A preposition is a word used before a noun to relate it to a previous noun, verb, or adjective
Examples: of, for, near, from
An attribute is a quality or feature of something.
A name is a word or set of words by which a person, animal, place, or ting is known or referred to.

Attribute phrasings
Attribute phrasings are the workhorse of Q&A, used when one thing is acting as an attribute of another thing.
They’re simple and straightforward, and perform most of the heavy lifting when you haven't defined a subtler,
more detailed phrasing. Attribute phrasings are described using the basic verb “have” (“products have categories”
and "host countries have host cities"). They also automatically allow questions with the prepositions “of” and “for”
(“categories of products”, “orders for products”) and possessive (“John’s orders”). Attribute phrasings are used in
these kinds of questions:
Which customers have orders?
List host cities by country ascending
Show orders that have chai
List customers with orders
What is the category of each product?
Count Robert King's orders
Power BI generates the overwhelming majority of attribute phrasings needed in your model, based on
table/column containment and model relationships. Typically, you don’t need to create them yourself. Here's an
example of how an attribute phrasing looks inside of the linguistic schema:

product_has_category:
Binding: {Table: Products}
Phrasings:
- Attribute: {Subject: product, Object: product.category}

Name Phrasings
Name phrasings are helpful if your data model has a table that contains named objects - like athlete names and
customer names. For example, a “product names are names of products” phrasing is essential for being able to use
product names in questions. Name phrasing also enables “named” as a verb (for example, “List customers named
John Smith”). However, it's most important when used in combination with other phrasings, to allow a name value
to be used to refer to a particular table row. For example, in “Customers that bought chai”, Q&A can tell the value
“chai” refers to the whole row of the product table, rather than just a value in the product name column. Name
phrasings are used in these kinds of questions:
Which employees are named Robert King
Who is named Ernst Handel
Fernand De Montigny's sports
Count of athletes named Mary
What did Robert King buy?
Assuming you used a sensible naming convention for name columns in your model (for example, “Name” or
“ProductName” rather than “PrdNm”), Power BI generates most of the name phrasings needed in your model
automatically, so you usually don’t need to create them yourself.
Here's an example of how a name phrasing looks inside of the linguistic schema:

employee_has_name:
Binding: {Table: Employees}
Phrasings:
- Name:
Subject: employee
Name: employee.name

Adjective Phrasings
Adjective phrasings define new adjectives used describe things in your model. For example, “happy customers are
customers where rating > 6” phrasing is needed to ask questions like “list the happy customers in Des Moines”.
There are several forms of adjective phrasings, for use in different situations.
Simple adjective phrasings define a new adjective based on a condition, such as “discontinued products are
products where status = D”. Simple adjective phrasings are used in these kinds of questions:
Which products are discontinued?
List the discontinued products
List the gold medalists
Products that are backordered
Here's an example of how a simple adjective phrasing looks inside of the linguistic schema:
product_is_discontinued:

Binding: {Table: Products}

Conditions:
- Target: product.discontinued
Operator: Equals
Value: true
Phrasings:
- Adjective:
Subject: product
Adjectives: [discontinued]

Measurement adjective phrasings define a new adjective based on a numeric value that indicates the extent to
which the adjective applies, such as “lengths indicate how long rivers are” and "small countryregions have small
land areas". Measurement adjective phrasings are used in these kinds of questions:
List the long rivers
Which rivers are the longest?
List the smallest countryregions that won gold in basketball
How long is the Rio Grande?
Here's an example of how a measurement adjective phrasing looks inside of the linguistic schema:
river_has_length:
 Binding: {Table: Rivers}
Phrasings:
- Adjective:
Subject: river
Adjectives: [long]
Antonyms: [short]
Measurement: river.length

Dynamic adjective phrasings define a set of new adjectives based on values in a column in the model, such as
“colors describe products” and "events have event genders". Dynamic adjective phrasings are used in these kinds of
questions:
List the red products
Which products are green?
Show skating events for females
Count issues that are active
Here's an example of how a dynamic adjective phrasing looks inside of the linguistic schema: product_has_color:

Binding: {Table: Products}

Phrasings:
- DynamicAdjective:
Subject: product
Adjective: product.color

Noun phrasings
Noun phrasings define new nouns that describe subsets of things in your model. They often include some type of
model-specific measurement or condition. For example, for our Olympics model we might want to add phrasings
that distinguish champions from medalists, ball sports from water sports, teams versus individuals, age categories
of athletes (teens, adults, seniors) , etc. For our movie database, we might want to add noun phrasings for “flops are
movies where net profit < 0” so that we can ask questions like “count the flops by year”. There are two forms of
noun phrasings, for use in different situations.
Simple noun phrasings define a new noun based on a condition, such as “contractors are employees where full time
= false” and "champion is athlete where count of medals >5". Simple noun phrasings are used in these kinds of
questions:
Which employees are contractors?
Count the contractors in Portland
How many champions in 2016
Here's an example of how a simple noun phrasing looks inside of the linguistic schema: employee_is_contractor:

Binding: {Table: Employees}

Conditions:
- Target: employee.full_time
Operator: Equals
Value: false
Phrasings:
- Noun:
Subject: employee
Nouns: [contractor]

Dynamic noun phrasings define a set of new nouns based on values in a column in the model, such as “jobs define
subsets of employees”. Dynamic noun phrasings are used in these kinds of questions:
 List the cashiers in Chicago
Which employees are baristas?
List the referees in 1992
Here's an example of how a dynamic noun phrasing looks inside of the linguistic schema: employee_has_job:

Binding: {Table: Employees}

Phrasings:
- DynamicNoun:
Subject: employee
Noun: employee.job

Preposition phrasings
Preposition phrasings are used to describe how things in your model are related via prepositions. For example, a
“cities are in countries” phrasing improves understanding of questions like “count the cities in Washington”. Some
preposition phrasings are created automatically when a column is recognized as a geographical entity. Preposition
phrasings are used in these kinds of questions:
Count the customers in New York
List the books about linguistics
Which city is John Galt in?
How many books are by Stephen Pinker?
Here's an example of how a preposition phrasing looks inside of the linguistic schema: customers_are_in_cities:

Binding: {Table: Customers}

Phrasings:
- Preposition:
Subject: customer
Prepositions: [in]
Object: customer.city

Verb Phrasings
Verb phrasings are used to describe how things in your model are related via verbs. For example, a “customers buy
products” phrasing improves understanding of questions like “who bought cheese?” and “what did John buy?”
Verb phrasings are the most flexible of all of the types of phrasings, often relating more than two things to each
other, such as in “employees sell customers products”. Verb phrasings are used in these kinds of questions:
Who sold what to whom?
Which employee sold chai to John?
How many customers were sold chai by Mary?
List the products that Mary sold to John.
Which discontinued products were sold to Chicago customers by Boston employees?
Verb phrasings can also contain prepositional phrases, thereby adding to their flexibility, such as in “athletes win
medals at competitions” or “customers are given refunds for products”. Verb phrasings with prepositional phrases
are used in these kinds of questions:
How many athletes won a gold medal at the Visa Championships?
Which customers were given a refund for cheese?
At which competition did Danell Leyva win a bronze medal?
Some verb phrasings are created automatically when a column is recognized as containing both a verb and a
preposition.
Here's an example of how a verb phrasing looks inside of the linguistic schema:
customers_buy_products_from_salespeople:

Binding: {Table: Orders}

Phrasings:
- Verb:
Subject: customer
Verbs: [buy, purchase]
Object: product
PrepositionalPhrases:
- Prepositions: [from]
Object: salesperson

Relationships with multiple phrasings

Frequently, a single relationship can be described in more than one way. In this case, a single relationship can have
more than one phrasing. It's common for the relationship between a table entity and a column entity to have both
an attribute phrasing and another phrasing. For example, in the relationship between customer and customer
name, you will want both an attribute phrasing (for example, “customers have names”) and a name phrasing (for
example, “customer names are the names of customers”) so you can ask both types of questions.
Here's an example of how a relationship with two phrasings looks inside of the linguistic schema:
customer_has_name:

Binding: {Table: Customers}

Phrasings:
- Attribute: {Subject: customer, Object: customer.name}
- Name:
Subject: customer
Object: customer.name

Another example would be adding the alternate phrasing “employees sell customers products” to the “customers
buy products from employees” relationship. Note that you do not need to add variations like “employees sell
products to customers” or “products are sold to customers by employees”, since the “by” and “to” variations of
the subject and indirect object are inferred automatically by Q&A.

Considerations and troubleshooting

If you make a change to a .lsdl.yaml file that does not conform to the linguistic schema format, you would now see
validation squiggles to indicate issues:

More questions? Try the Power BI Community

 Import and display KPIs in Power BI
1/14/2019 • 2 minutes to read • Edit Online

With Power BI Desktop, you can import and display KPIs in tables, matrices, and cards.
Follow these steps to import and display KPIs.
1. Start with an Excel workbook that has a Power Pivot model and KPIs. This exercise uses a workbook named
KPIs.
2. Import the Excel workbook into Power BI, using File -> Import -> Excel workbook contents. You can also
learn how to import workbooks.
3. After import into Power BI, your KPI will appear in the Fields pane, marked with the icon. To use a KPI in
your report, be sure to expand its contents, exposing the Value, Goal, and Status fields.

4. Imported KPIs are best used in standard visualization types, such as the Table type. Power BI also includes
the KPI visualization type, which should only be used to create new KPIs.
That's all there is to it. You can use KPIs to highlight trends, progress, or other important indicators.
 Use visual elements to enhance Power BI reports
2/13/2019 • 4 minutes to read • Edit Online

With Power BI Desktop you can use visual elements, such as wallpaper and improved visual headers for
visualizations, to enhance the appearance of your reports.

Beginning with the July 2018 release of Power BI Desktop, you can put enhancements to use in your reports and
make your analytics and reports even more appealing than before. The enhancements discussed in this article
include the following:
Apply wallpaper to your reports so your background can enhance or highlight elements of the story you want
to tell with your data
Use improved visual headers for individual visualizations to create perfectly aligned visuals on your report
canvas.
The following sections describe how to use these enhancements, and how to apply them to your reports.

Using wallpaper in Power BI reports

You can format the gray area outside your report page using wallpaper. The following image has an arrow that
clarifies where the wallpaper area applies.
You can either set wallpaper on a per-report-page basis, or have the same wallpaper for every page in your report.
To set your wallpaper, tap or click the Formatting icon when no visual is selected in your report and the
Wallpaper card appears in the pane.
You can choose a color to apply as wallpaper by selecting the Color dropdown, or you can select the Add Image
button to select an image to apply as wallpaper. You can also apply transparency to your wallpaper, whether it's a
color or an image, using the Transparency slider.
It's useful to keep in mind the following definitions that pertain to wallpaper:
The gray area outside of your report area is the wallpaper area
The area in the canvas where you can place visuals is referred to as the report page, and in the Format pane
can be modified using the Page background dropdown.
The report page is always in the foreground (when compared to the wallpaper), while the wallpaper is behind it
and the furthest-back element on the report page. When you apply transparency to the page, the visuals in your
report also have the transparency applied, allowing your wallpaper to be visible in the background through your
visuals.
For all new reports, the default settings are the following:
The report page is set to white and its transparency is set to 100%
The wallpaper is set to white and its transparency is set to 0%
When you set your page background to greater than 50% transparency, a dotted border appears while you are
creating or editing your report, to show you the boundary of the report canvas border.
It's important to note that the dotted boundary only shows up when editing your report, and does not appear for
people who are viewing your published report, such as when it's viewed in the Power BI service.

NOTE
If you use dark-colored backgrounds for wallpaper and set text color to white or very light, be mindful that the Export to
PDF feature does not include wallpaper, so any exports with white fonts will be nearly invisible in the exported PDF file. See
export to PDF for more information on Export to PDF.

Using improved visual headers in Power BI reports

Beginning with the July 2018 release of Power BI Desktop, the headers for visuals in reports have been
significantly improved. The primary improvements are that the header has been detached from the visual so its
position can be adjusted based on your preference of layout and positioning, and the header now appears within
the visual itself instead of floating above it.
By default, the header appears inside the visual aligned with the title. In the following image, you can see the
header (the pin icon, the expand icon, and the ellipses icon) within the visual and aligned to the right, along the
same horizontal position as the visual's title.

If your visual doesn't have a title, the header floats above the top of the visual aligned to the right, as shown in the
following image.

If your visual is positioned all the way to the top of your report, the visual header instead snaps to the bottom of
the visual.

Each visual also has a card in the Formatting section of the Visualizations pane called Visual header. In that
card you can adjust all sorts of characteristics of the visual header
 NOTE
The visibility of toggles do not affect your report when you are authoring or editing the report. You must publish the report
and view it in reading mode to see the effect. This behavior ensures that the many options provided in visual headers are
important during editing, especially warning icons that alert you to issues while editing.

For reports that only appear in the Power BI service, you can adjust the use of visual headers by going to My
Workspace > Reports and then selecting the Settings icon. There you see settings for the report for which you
selected Settings and you can adjust the settings from there, as shown in the following image.
Enabling improved visual headers for existing reports
The new visual header is the default behavior for all new reports. For existing reports, you need to enable this
behavior in Power BI Desktop by going to File > Options and settings > Options and then in the Report
settings section, enable the Use the modern visual header with updated styling options checkbox.
Next steps
For more information about Power BI Desktop, and how to get started, check out the following articles.
What is Power BI Desktop?
Query Overview with Power BI Desktop
Data Sources in Power BI Desktop
Connect to Data in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Common Query Tasks in Power BI Desktop
 Create tooltips based on report pages in Power BI
Desktop
2/13/2019 • 6 minutes to read • Edit Online

You can create visually rich report tooltips that appear when you hover over visuals, based on report pages you
create in Power BI Desktop. By creating a report page that serves as your tooltip, your custom tooltips can
include visuals, images, and any other collection of items you create in the report page.

You can create as many tooltip pages as you want. Each tooltip page can be associated with one or more fields in
your report, so that when you hover over a visual that includes the selected field, the tooltip you created on your
tooltip page appears when you hover over the visual, filtered by the datapoint over which your mouse is hovering.
There are all sorts of interesting things you can do with report tooltips. Let's take a look at how to create tooltips
and what you must do to configure them.

Create a report tooltip page

To get started, create a new report page by clicking the + button, found along the bottom of the Power BI
Desktop canvas, in the page tabs area. The button is located beside the last page in the report.
Your tooltip can be any size, but keep in mind that tooltips hover over the report canvas, so you might want to keep
them reasonably small. In the Format pane in the Page Size card, you can see a new page size template called
Tooltip. This provides a report page canvas size that's ready for your tooltip.

By default, Power BI Desktop fits your report canvas to the available space on the page. Often that's good, but
not in the case of tooltips. To get a better sense and view of what your tooltip will look like when you're done, you
can change the Page View to actual size.
To do that, select the View tab from the ribbon. From there, select Page View > Actual Size, as shown in the
following image.
You can also name the report page so its purpose is clear. Just select the Page Information card in the Format
pane, then type the name into the Name field you find there. In the following image the tooltip report name is
Tooltip 1, but feel free to name yours something more inspired.

From there, you can create whatever visuals you would like to show up in your tooltip. In the following image,
there are two cards and one clustered bar chart on the tooltip page, along with a background color for the page
itself, and backgrounds for each of the visuals, to give it the look we wanted.
There are more steps to complete before your tooltip report page is ready to work as a tooltip. You need to
configure the tooltip page in a few ways, as described in the next section.

Configure your tooltip report page

Once you have the tooltip report page created, you need to configure the page in order for Power BI Desktop to
register it as a tooltip, and to ensure it appears in over the right visuals.
To begin with, you need to turn the Tooltip slider to On, in the Page Information card, to make the page a tooltip.
Once that slider is set to on, you specify the fields for which you want the report tooltip to appear. For visuals in the
report that include the field you specify, the tooltip will appear. You specify which field or fields apply by dragging
them into the Tooltip fields bucket, found in the Fields section of the Visualizations pane. In the following
image, the SalesAmount field has been dragged into the Tooltips fields bucket.
You can include both categorical and numerical fields in the Tooltips fields bucket, including measures.
Once completed, the tooltip report page you created will be used as a tooltip in visuals in the report that use any
fields you placed into the Tooltips fields bucket, replacing the default Power BI tooltip.

Manually setting a report tooltip

In addition to creating a tooltip that automatically appears when hovering over a visual that contains the specified
field, you can manually set a tooltip.
Any visual that supports report tooltips now has a Tooltip card in its Formatting pane.
To set a tooltip manually, select the visual for which you want to specify the manual tooltip, then in the
Visualizations pane, select the Format section and expand the Tooltip card.
Then, in the Page dropdown, select the tooltip page you want to use for the selected visual. Note that only report
pages that are specified as Tooltip pages show up in the dialog.

Being able to manually set a tooltip has many uses. You can set a blank page for a tooltip, and thereby override the
default Power BI tooltip selection. Another use is when you don't want the tooltip that is automatically selected by
Power BI to be the tooltip. For example, if you have a visual that includes two fields, and both of those fields have
an associated tooltip, Power BI selects only one to show. You might not want that to be the case, so you could
manually select which tooltip should be displayed.

Reverting to default tooltips

If you create a manual tooltip for a visual but decide you want the default tooltip instead, you can always return to
the default tooltip that Power BI provides. To do so, when a visual is selected and the Tooltip card is expanded, just
select Auto from the Page dropdown to go back to the default.

Custom report tooltips and line charts

There are a few considerations to keep in mind when your report tooltips are interacting with line chart visuals,
and with visuals when cross-highlighting.
Report tooltips and line charts
When a report tooltip is displayed for a line chart, only one tooltip for all lines in the chart is displayed. This is
similar to the default tooltip behavior for line charts, which also displays only one tooltip.
This is because the field in the legend does not get passed through as a filter for the tooltip. In the following image,
the tooltip being displayed is showing all units sold on that day across all three classes displayed in the report
tooltip (in this example, Deluxe, Economy, and Regular).

Report tooltips and cross-highlighting

When a visual is being cross-highlighted in a report, report tooltips always show the cross-highlighted data, even if
you're hovering over the faded section of the data point. In the following image, the mouse is hovering over the
faded section of the bar graph (the section that is not highlighted), but the report tooltip still shows data for the
highlighted portion of that datapoint (the highlighted data).
Limitations and considerations
There are a few limitations and considerations for tooltips to keep in mind.
Beginning with the December 2018 release of Power BI Desktop, Button visuals also support tooltips.
Report tooltips are not supported when viewing reports in mobile apps.
Report tooltips are not supported for custom visuals.
Clusters are not currently supported as fields that can be shown in report tooltips.
When choosing a field to be shown for report tooltips, when using a field versus a category, visuals that contain
that field will only show the specified tooltip when summarization with the selected field matches.

Next steps
For more information about features that are similar or interact with report tooltips, take a look at the following
articles:
Use drillthrough in Power BI Desktop
Display a dashboard tile or report visual in Focus mode
 Export reports to PDF from Power BI Desktop
3/6/2019 • 2 minutes to read • Edit Online

In Power BI Desktop or the Power BI service, you can export reports to a PDF file, and thereby easily share or
print your reports from that PDF.

The process of exporting your report from Power BI Desktop to a PDF, so that you can print the PDF or share
that PDF document with others, is straightforward. Simply select File > Export to PDF from Power BI Desktop.
The Export to PDF process will export all visible pages in the report, with each report page exporting to a single
page in the PDF. Report pages that are currently not visible, such as any tooltips or hidden pages, are not exported
to the PDF file.

When you select File > Export to PDF the export is initiated, and a dialog appears that shows the export process
is underway. The dialog remains on the screen until the export process completes. During the export process, all
interaction with the report being exported is disabled. The only way to interact with the report is to wait until the
export process completes, or to cancel the export.
When the export completes, the PDF is loaded into the default PDF viewer on the computer.

Considerations and limitations

There are a few considerations to keep in mind with the Export to PDF feature:
The feature does export custom visuals, but it does not export any wallpaper you may have applied to the
report.
Since wallpaper is not exported to the PDF, you should pay special attention to reports that use dark wallpaper. If
the text in your report is light or white, to have it stand out against your dark wallpaper, it will be difficult to read or
unreadable in the export to PDF process since the wallpaper will not be exported with the rest of the report.

Next steps
There are all sorts of interesting visual elements and features in Power BI Desktop. For more information in
information, check out the following resources:
Use visual elements to enhance Power BI reports
What is Power BI Desktop?
 Use Q&A in Power BI Desktop for natural language
queries
4/1/2019 • 10 minutes to read • Edit Online

Using common phrases and natural language to ask questions of your data is powerful. Even more powerful is
when your data answers, which is what Q&A in Power BI Desktop lets you do.
To enable Q&A to successfully interpret the large collection of questions it's capable of responding to, Q&A must
make assumptions about the model. If the structure of your model doesn't meet one or more of these
assumptions, you'll need to adjust your model. Those adjustments for Q&A are the same best-practice
optimizations for any model in Power BI, regardless whether you use Q&A.

NOTE
Q&A is only available when working with a model that contains imported data or to Live connections to SSAS. DirectQuery
models are not supported.
Q&A requires the following C runtime update if you're using a version of Windows prior to Windows 10. You can try
installing important updates from Windows Update or manually install the required component from Microsoft
(KB2999226). https://support.microsoft.com/help/2999226/update-for-universal-c-runtime-in-windows

In the following sections, we describe how to adjust your model so it works well with Q&A in Power BI.

Add missing relationships

If your model is missing relationships between tables, neither Power BI reports nor Q&A can interpret how to join
those tables if you ask a question about them. Relationships are the cornerstone of a good model. For example,
you cannot ask for the “total sales for Seattle customers” if the relationship between the orders table and the
customers table is missing. The following images show you examples of a model that needs work, and a model
that is ready for Q&A.
Needs work

Ready for Q&A

Rename tables and columns
The choice of tables and columns is important for Q&A. For example, say you have a table named
CustomerSummary that contains a list of your customers. You would need to ask questions like “List the customer
summaries in Chicago” rather than “List the customers in Chicago”.
While Q&A can do some basic word breaking and detection of plurals, Q&A assumes that your table and column
names accurately reflect their content.
Consider another example. Imagine you have a table named Headcount that contains first and last names and
employee numbers. You have another table named Employees that contains employee numbers, job numbers, and
start dates. People familiar with the model might understand this structure. Someone else who asks “count the
employees” is going to get a count of the rows from the “Employees” table. This result is probably not what they
had in mind, because it’s a count of every job each employee has ever had. It would be better to rename those
tables to truly reflect what they contain.
Needs work

Ready for Q&A

Fix incorrect data types

Imported data can have incorrect data types. In particular, date and number columns that are imported as strings
aren't interpreted by Q&A as dates and numbers. Make sure you select the correct data type in your Power BI
model.
Mark year and identifier columns as Don't Summarize
Power BI aggressively aggregates numeric columns by default, so questions like “total sales by year” can
sometimes result in a grand total of sales alongside a grand total of years. If you have specific columns where you
don't want Power BI to exhibit this behavior, set the Summarize By property on the column to Don’t
Summarize. Be mindful of year, month, day, and ID columns, as those columns are the most frequent problems.
Other columns that aren’t sensible to sum, such as age, could also benefit from setting Summarize By to Don’t
Summarize or to Average. You'll find this setting in the Modeling tab.

Choose a Data Category for each date and geography column

The Data Category provides additional semantic knowledge about the content of a column beyond its data type.
For example, an integer column might be marked as a Zip Code, a string column might be marked as a City,
Country, Region, and so on. This information is used by Q&A in two important ways: For visualization selection
and for language biases.
First, Q&A uses the Data Category information to help make choices about what kind of visual display to use.
For example, it recognizes that columns with date or time Data Categories are typically a good choice for the
horizontal axis of a line chart or the play axis of a bubble chart. And it assumes that results containing columns
with geographical Data Categories may look good on a map.
Second, Q&A makes some educated guesses about how users are likely to talk about date and geography
columns, to help it understand certain types of questions. For example, the “when” in “When was John Smith
hired?” is almost certain to map to a date column, and the “Brown” in “Count customers in Brown” is more likely
to be a city than a hair color.

Choose a Sort By Column for relevant columns

The Sort By Column property allows sorting on one column to automatically sort by a different column instead.
For example, when you ask “sort customers by shirt size”, you probably want your Shirt Size column to sort by the
underlying size number (XS, S, M, L, XL ) rather than alphabetically (L, M, S, XL, XS ).
Normalize your model
Rest assured that we’re not suggesting you need to reshape your entire model. However, certain structures are so
difficult that Q&A doesn't handle them well. If you perform some basic normalization of the structure of your
model, the usability of Power BI reports will increase significantly, as will the accuracy of Q&A results.
Follow this general rule: Each unique “thing” the user talks about should be represented by exactly one model
object (table or column). So, if your users talk about customers, there should be one customer object. And, if your
users talk about sales, there should be one sales object. Sounds simple, doesn't it? Depending on the shape of the
data you’re starting with, it can be. There are rich data shaping capabilities available in Query Editor if you need
them, while many of the more straightforward transformations can happen simply using calculations in the Power
BI model.
The following sections contain some common transformations you might need to perform.
Create new tables for multi-column entities
If you have multiple columns that act as a single distinct unit within a larger table, those columns should be split
out into their own table. For example, say you have a Contact Name, Contact Title, and Contact Phone column
within your Companies table. A better design would be to have a separate Contacts table to contain the Name,
Title, and Phone, and a link back to the Companies table. That makes it easier to ask questions about contacts
independently of questions about companies for which they are the contact, and improves display flexibility.
Needs work

Ready for Q&A

Pivot to eliminate property bags

If you have property bags in your model, they should be restructured to have a single column per property.
Property bags, while convenient for managing large numbers of properties, suffer from a number of inherent
limitations that neither Power BI reports nor Q&A are designed to work around.
For example, consider a CustomerDemographics table with CustomerID, Property, and Value columns, where each
row represents a different property of the customer (for examples, age, marital status, city, etc). By overloading the
meaning of the Value column based on the content of the Property column, it becomes impossible for Q&A to
interpret most queries that reference it. A simple question such as “show the age of each customer” might happen
to work, since it could be interpreted as “show the customers and customer demographics where property is age”.
However, the structure of the model simply doesn’t support slightly more complex questions like “average age of
customers in Chicago.” While users who directly author Power BI reports can sometimes find clever ways to get
the data they are looking for, Q&A only works when each column has only a single meaning.
Needs work

Ready for Q&A

Union to eliminate partitioning

If you've partitioned your data across multiple tables, or have pivoted values across multiple columns, a number of
common operations will be difficult or impossible for your users to achieve. Consider first a typical table
partitioning: a Sales2000 -2010 table and a Sales2011 -2020 table. If all of your important reports are restricted to
a specific decade, you could probably leave it this way for Power BI reports. However, the flexibility of Q&A will
lead your users to expect answers to questions like “total sales by year.” For this query to work, you need to union
the data into a single Power BI model table.
Similarly, consider a typical pivoted value column: a BookTour table containing Author, Book, City1, City2, and
City3 columns. With a structure like this, even simple questions like “count books by city” cannot be interpreted
correctly. For this query to work, create a separate BookTourCities table, which unions the city values into a single
column.
Needs work

Ready for Q&A

Split formatted columns
If the source from which you're importing your data contains formatted columns, Power BI reports (and Q&A) will
not reach inside the column to parse its contents. So if you have, for example, a Full Address column that contains
the address, city, and country, you should also split it into Address, City, and Country columns so your users can
query against them individually.
Needs work

Ready for Q&A

Similarly, if you have any full name columns for a person, you’ll want to add First Name and Last Name
columns, just in case someone wants to ask questions using partial names.
Create new tables for multi-value columns
Also a similar situation, if the source from which you're importing your data contains multi-value columns, Power
BI reports (and Q&A) will not reach inside the column to parse out the contents. So, if you have, for example, a
Composer column that contains the names of multiple composers for a song, you should split it into multiple rows
in a separate Composers table.
Needs work

Ready for Q&A

Denormalize to eliminate inactive relationships
The one exception to the “normalization is better” rule occurs when there is more than one path to get from one
table to another. For example, say you have a Flights table with both SourceCityID and DestinationCityID columns,
each of which are related to the Cities table. One of those relationships will have to be marked as inactive. Since
Q&A can only use active relationships, you can't ask questions about either source or destination, depending on
which you chose. If you instead denormalize the city name columns into the Flights table, you can ask questions
like: “list the flights for tomorrow with a source city of Seattle and a destination city of San Francisco.”
Needs work

Ready for Q&A

Add synonyms to tables and columns

This step applies specifically to Q&A (and not to Power BI reports in general). Users often have a variety of terms
they use to refer to the same thing, such as total sales, net sales, total net sales. Power BI’s model allows these
synonyms to be added to tables and columns within the model.
This step can be important. Even with straightforward table and column names, users of Q&A ask questions using
the vocabulary that first comes to them, and are not choosing from a predefined list of columns. The more sensible
synonyms you can add, the better your users' experience will be with your report. To add Synonyms, in
Relationships view, select the Synonyms button in the ribbon, as shown in the following image.

The Synonyms field appears on the right side of Power BI Desktop, where you can add your synonyms, as
showing in the following image.

Be careful when adding synonyms, since adding the same synonym to more than one column or table will
introduce ambiguity. Q&A utilizes context where possible to choose between ambiguous synonyms, but not all
questions have sufficient context. For example, when your user asks “count the customers”, if you have three things
with the synonym “customer” in your model, they might not get the answer they are looking for. In these cases,
make sure the primary synonym is unique, as that is what is used in the restatement. It can alert the user to the
ambiguity (for example, a restatement of “show the number of archived customer records”), hinting they might
want to ask it differently.

Next steps
For more information about features that are in Power BI Desktop, take a look at the following articles:
Use drillthrough in Power BI Desktop
Display a dashboard tile or report visual in Focus mode
 Using the Analytics pane in Power BI Desktop
2/13/2019 • 4 minutes to read • Edit Online

With the Analytics pane in Power BI Desktop, you can add dynamic reference lines to visuals, and provide focus
for important trends or insights. The Analytics pane is found in the Visualizations area of Power BI Desktop.

NOTE
The Analytics pane only appears when you select a visual on the Power BI Desktop canvas.

Search within the Analytics pane

Beginning with the February 2018 release of Power BI Desktop (version 2.55.5010.201 or later), you can search
within the Analytics pane, which is a sub-section of the Visualizations pane. As shown in the image below,
search box appears when the Analytics pane is selected.
Using the Analytics pane
With the Analytics pane, you can create the following types of dynamic reference lines (not all lines are available
for all visual types):
X-Axis constant line
Y -Axis constant line
Min line
Max line
Average line
Median line
Percentile line
The following sections show how you can use the Analytics pane and dynamic reference lines in your
visualizations.
To view the available dynamic reference lines for a visual, follow these steps:
1. Select or create a visual, then select the Analytics icon from the Visualizations section.
2. Select the down arrow for the type of line you want to create to expand its options. In this case, we'll select
Average Line.
3. To create a new line, select + Add. You can then specify a name for the line by double-clicking the text box,
then typing in your name.
You have all sorts of options for your line, such as selecting its color, transparency, style and position
(relative to the visual's data elements), and whether to include the label. And importantly, you can select
which Measure in the visual you want your line to be based upon by selecting the Measure drop-down,
which is automatically populated with data elements from the visual. In this case, we'll select Weather as
the measure, label it Average Weather, and customize a few of the other options as shown below.
4. If you want to have a data label appear, move the Data label slider on. When you do so, you get a whole
host of additional options for your data label, as shown in the following image.
5. Notice the number that appears next to the Average line item in the Analytics pane. That tells you how
many dynamic lines you currently have on your visual, and of which type. If we add a Max line for Cost of
Living, you can see that the Analytics pane shows that we now also have a Max line dynamic reference
line applied to this visual.
If the visual you've selected can't have dynamic reference lines applied to it (in this case, a Map visual), you'll see
the following when you select the Analytics pane.

There are all sorts of interesting insights you can highlight by creating dynamic reference lines with the Analytics
pane.
We're planning more features and capabilities, including expanding which visuals can have dynamic reference
lines applied to them, so check back often for what's new.

Apply Forecasting
You can use the Forecast feature by selecting a visual, then expanding the Forecast section of the Analytics
pane. You can specify many inputs to modify the forecast, such as the Forecast length, the Confidence interval, and
others. The following image shows a basic line visual with forecasting applied, but you can use your imagination
(and play around with the forecasting feature) to see how it can apply to your models.

Limitations
The ability to use dynamic reference lines is based on the type of visual being used. The following list shows which
dynamic lines are currently available for which visuals:
Full use of dynamic lines are available on the following visuals:
Area chart
Line chart
Scatter chart
Clustered Column chart
Clustered Bar chart
The following visuals can use only a constant line from the Analytics pane:
Stacked Area
Stacked Bar
Stacked Column
100% Stacked Bar
100% Stacked Column
For the following visuals, a trend line is currently the only option:
Non-stacked Line
 Clustered Column chart
Lastly, non-Cartesian visuals cannot currently apply dynamic lines from the Analytics pane, such as:
Matrix
Pie chart
Donut
Table
The percentile line is only available when using imported data in Power BI Desktop or when connected live to a
model on a server running Analysis Service 2016 or later, Azure Analysis Services, or a dataset on the Power
BI service.

Next steps
There are all sorts of things you can do with Power BI Desktop. For more information on its capabilities, check out
the following resources:
What's New in Power BI Desktop
Download Power BI Desktop
What is Power BI Desktop?
Query Overview with Power BI Desktop
Data Types in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Common Query Tasks in Power BI Desktop
 Use insights in Power BI Desktop to explain increases
and decreases seen in visuals (Preview)
2/26/2019 • 7 minutes to read • Edit Online

Often in visuals, you see a large increase and then a sharp drop in values, and wonder about the cause of such
fluctuations. With insights in Power BI Desktop you can learn the cause with just a few clicks.
For example, consider the following visual that shows Sales Amount by Year and Quarter. A large decrease in sales
occurs in 2014, with sales dropping sharply between Qtr 1 and Qtr 2. In such cases you can explore the data, to
help explain the change that occurred.

You can tell Power BI Desktop to explain increases or decreases in charts, see distribution factors in charts, and
get fast, automated, insightful analysis about your data. Simply right-click on a data point, and select Analyze >
Explain the decrease (or increase, if the previous bar was lower), or Analyze > Find where this distribution is
different and insight is delivered to you in an easy-to-use window.
The insights feature is contextual, and is based on the immediately previous data point - such as the previous bar,
or column.

NOTE
This feature is in preview, and is subject to change. The insight feature is enabled and on by default (you don't need to check
a Preview box to enable it) beginning with the September 2017 version of Power BI Desktop.

Using insights
To use insights to explain increases or decreases seen on charts, just right-click on any data point in a bar or line
chart, and select Analyze > Explain the increase (or Explain the decrease, since all insights are based on the
change from the previous data point).
Power BI Desktop then runs its machine learning algorithms over the data, and populates a window with a visual
and a description that describes which categories most influenced the increase or decrease. By default, insights are
provided as a waterfall visual, as shown in the following image.

By selecting the small icons at the bottom of the waterfall visual, you can choose to have insights display a scatter
chart, stacked column chart, or a ribbon chart.
The thumbs up and thumbs down icons at the top of the page are provided so you can provide feedback about the
visual and the feature. Doing so provides feedback, but it does not currently train the algorithm to influence the
results returned next time you use the feature.
And importantly, the + button at the top of the visual lets you add the selected visual to your report, just as if you
created the visual manually. You can then format or otherwise adjust the added visual just as you would to any
other visual on your report. You can only add a selected insight visual when you're editing a report in Power BI
Desktop.
You can use insights when your report is in reading or editing mode, making it versatile for both analyzing data,
and for creating visuals you can easily add to your reports.

Details of the results returned

The details returned by insights are intended to highlight what was different between the two time periods, to help
you understand the change between them.
For example, if Sales increased by 55% overall from Qtr 3 to Qtr 4, and that is equally true for every Category of
product (sales of Computer increased by 55%, and of Audio, and so on), and also true for every country, and for
every type of customer, then there is little that can be identified in the data to help explain the change. However,
that situation is generally not the case, and we might typically find differences in what occurred, such that among
the categories, Computers and Home Appliances grew by a much larger 63% percentage, while TV and Audio
grew by only 23%, and therefore Computers and Home Appliances contributed a larger amount of the total for Qtr
4 than they had for Qtr 3. Given this example, a reasonable explanation of the increase would be: particularly
strong sales for Computers and TV and Audio.
So the algorithm is not simply returning the values that account for the biggest amount of the change. For
example, if the vast majority (98%) of sales came from the USA, then it would commonly be the case that the vast
majority of the increase was also in the USA. Yet unless the USA or other countries had a significant change to
their relative contribution to the total, Country would not be considered interesting in this context.
Simplistically, the algorithm can be thought of as taking all the other columns in the model, and calculating the
breakdown by that column for the before and after time periods, determining how much change occurred in that
breakdown, and then returning those columns with the biggest change. For example, Category was selected in the
example above, as the contribution made by TV and Video fell 7% from 33% to 26%, while the contribution from
Home Appliances grew from nothing to over 6%.
For each column returned, there are four visuals that can be displayed. Three of those visuals are intended to
highlight the change in contribution between the two periods. For example, for the explanation of the increase from
Qtr 2 to Qtr 3.
The scatter plot
The scatter plot visual shows the value of the measure in the first period (on the x-axis) against the value of the
measure in the second period (on the y-axis), for each value of the column (Category in this case). Thus as shown
in the following image, any data points are in the green region if the value increased, and in the red region if they
decreased.
The dotted line shows the best fit, and as such, data points above this line increased by more than the overall trend,
and those below it by less.

Note that data items whose value was blank in either period will not appear on the scatter plot (for example, Home
Appliances in this case)
The 100% stacked column chart
The 100% stacked column chart visual shows the value of the measure before and after, by the selected column,
shown as a 100% stacked column. This allows side-by-side comparison of the contribution before and after. The
tooltips show the actual contribution for the selected value.

The ribbon chart

The ribbon chart visual showsalso the value of the measure before and after. It's particularly useful in showing the
changes in contributions when these were such that the ordering of contributors changed (for example, if
Computers were the number one contributor before, but then fell to number three).
The waterfall chart
The fourth visual is a waterfall chart, showing the main actual increases or decreases between the periods. This
visual clearly shows the actual changes, but does not alone indicate the changes to the level of contribution that
actually highlight why the column was chosen as being interesting.

When ranking the column as to which have the largest differences in the relative contributions, the following is
considered:
The cardinality is factored in, as a difference is less statistically significant, and less interesting, when a
column has a large cardinality.
Differences for those categories where the original values were very high or very close to zero are weighted
higher than others. For example, if a Category only contributed 1% of sales, and this changed to 6%, that is
more statistically significant, and therefore considered more interesting, than a Category whose contribution
changed from 50% to 55%.
Various heuristics are employed to select the most meaningful results, for example by considering other
relationships between the data.
After examining different columns, those that show the biggest change to relative contribution are chosen and
output. For each, the values which had the most significant change to contribution are called out in the description.
In addition, the values that had the largest actual increases and decreases are also called out.

Considerations and limitations

Since these insights are based on the change from the previous data point, they aren't available when you select
the first data point in a visual.
The following list is the collection of currently unsupported scenarios for explain the increase/decrease:
TopN filters
Include/exclude filters
Measure filters
Non-numeric measures
Use of "Show value as"
Filtered measures - filtered measures are visual level calculations with a specific filter applied (for example, Total
Sales for France), and are used on some of the visuals created by the insights feature
Categorical columns on X-axis unless it defines a sort by column that is scalar. If using a hierarchy, then every
column in the active hierarchy has to match this condition
In addition, the following model types and data sources are currently not supported for insights:
DirectQuery
Live connect
On-premises Reporting Services
Embedding

Next steps
For more information about Power BI Desktop, and how to get started, check out the following articles.
What is Power BI Desktop?
Query Overview with Power BI Desktop
Data Sources in Power BI Desktop
Connect to Data in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Common Query Tasks in Power BI Desktop
 Use insights in Power BI Desktop to find where a
distribution is different (Preview)
2/13/2019 • 8 minutes to read • Edit Online

Often in visuals, you see a data point, and wonder about whether distribution would be the same for different
categories. With insights in Power BI Desktop you can find out with just a few clicks.
Consider the following visual, which shows Total Sales by Country. As the chart shows, most sales come from the
United States, accounting for 57% of all sales with lessor contributions coming from the other countries. It's often
interesting in such cases to explore whether that same distribution would be seen for different sub-populations. For
example, is this the same for all years, all sales channels, and all categories of products? While you could apply
different filters and compare the results visually, doing so can be time consuming and error prone.

You can tell Power BI Desktop to find where a distribution is different, and get fast, automated, insightful analysis
about your data. Simply right-click on a data point, and select Analyze > Find where the distribution is
different, and insight is delivered to you in an easy-to-use window.
In this example, the automated analysis quickly shows that for Touring Bikes, the proportion of sales in the United
States and Canada are lower, while the proportion coming from the other countries is higher.

NOTE
This feature is in preview, and is subject to change. The insight feature is enabled and on by default (you don't need to check
a Preview box to enable it) beginning with the September 2017 version of Power BI Desktop.

Using insights
To use insights to find where distributions seen on charts are different, just right-click on any data point (or on the
visual as a whole), and select Analyze > Find where the distribution is different.

Power BI Desktop then runs its machine learning algorithms over the data, and populates a window with a visual
and a description that describes which categories (columns), and which values of those columns, result in the most
significantly different distribution. Insights are provided as a column chart, as shown in the following image.
The values with the selected filter applied are shown using the normal default color. The overall values, as seen on
the original starting visual, are shown in grey for easy comparison. Up to three different filters might be included
(Touring Bikes, Mountain Bikes, Road Bikes in this example) and different filters can be chosen by clicking on them
(or using ctrl-click to select multiple).
For simple additive measures, like Total Sales in this example, the comparison is based on the relative, rather than
absolute, values. Hence while the sales for Touring Bikes is certainly lower than overall sales for all categories, by
default the visual uses a dual axis to allow the comparison between the proportion of sales across different
countries, for Touring Bikes versus all categories of bikes. Switching the toggle below the visual allows the two
values to be displayed in the same axis, allowing the absolute values to easily be compared (as shown in the
following image).

The descriptive text also gives some indication of the level of importance that might be attached to a filter value, by
given the number of records that match the filter. So in this example, you can see that while the distribution for
Touring Bikes might be significantly different, they account for only 16.6% of records.
The thumbs up and thumbs down icons at the top of the page are provided so you can provide feedback about the
visual and the feature. Doing so provides feedback, but it does not currently train the algorithm to influence the
results returned next time you use the feature.
And importantly, the + button at the top of the visual lets you add the selected visual to your report, just as if you
created the visual manually. You can then format or otherwise adjust the added visual just as you would to any
other visual on your report. You can only add a selected insight visual when you're editing a report in Power BI
Desktop.
You can use insights when your report is in reading or editing mode, making it versatile for both analyzing data,
and for creating visuals you can easily add to your reports.

Details of the returned results

You can think of the algorithm as taking all the other columns in the model, and for all of the values of those
columns, applying them as filters to the original visual, and finding which of those filter values produces the most
different result from the original.
Of course, you likely wonder what different means. For example, say that the overall split of sales between the USA
and Canada was the following:

COUNTRY SALES ($M)

USA 15

Canada 5

Then for a particular category of product “Road Bike) the split of sales might be:

COUNTRY SALES ($M)

USA 3

Canada 1

While the numbers are different in each of those tables, the relative values between USA and Canada are identical
(75% and 25% overall, and for Road Bikes). Because of that, these are not considered different. For simple additive
measures like this, the algorithm is therefore looking for differences in the relative value.
By contrast consider a measure like margin, that is calculated as Profit/Cost, and say that the overall margins for
the USA and Canada were the following

COUNTRY MARGIN (%)

USA 15

Canada 5

Then for a particular category of product “Road Bike) the split of sales might be:

COUNTRY MARGIN (%)

USA 3
 COUNTRY MARGIN (%)

Canada 1

Given the nature of such measures, this is considered interestingly different. So for non-additive measures such as
this margin example, the algorithm is looking for differences in the absolute value.
The visuals displayed are thus intended to clearly show the differences found between the overall distribution (as
seen in the original visual) and the value with the particular filter applied.
So for additive measures, like Sales in the previous example, a column and line chart is used, where the use of a
dual axis with appropriate scaling such that the relative values can easily be compared. The columns show the value
with the filter applied, and the line shows the overall value (with the column axis being on the left, and the line axis
on the right, as normal). The line is shown using a stepped style, with a dashed line, filled with grey, For the
previous example, if the column axis maximum value is 4, and the line axis maximum value is 20, then it would
allow easy comparison of the relative values between USA and Canada for the filtered and overall values.
Similarly, for non-additive measures like Margin in the previous example, a column and line chart is used, where
the use of a single axis means the absolute values can easily be compared. Again the line (filled with grey) shows
the overall value. Whether comparing actual or relative numbers, the determination of the degree to which two
distributions are different is not simply a matter of calculating the difference in the values. For example:
The size of the population is factored in, as a difference is less statistically significant and less interesting
when it applies to a smaller proportion of the overall population. As an example, the distribution of sales
across countries might be very different for some particular product, this would not be considered
interesting if there were thousands of products, and hence that particular product accounted for only a small
percentage of the overall sales.
Differences for those categories where the original values were very high or very close to zero are weighted
higher than others. For example, if a country overall contributes only 1% of sales, but for some particular
type of product contributes 6%, that is more statistically significant, and therefore considered more
interesting, than a country whose contribution changed from 50% to 55%.
Various heuristics are employed to select the most meaningful results, for example by considering other
relationships between the data.
After examining different columns, and the values for each of those columns, the set of values that give the biggest
differences are chosen. For ease of understanding, these are then output grouped by column, with the column
whose values give the biggest difference listed first. Up to three values are shown per column, but less might be
shown either if there were less than three values that have a large effect, or if some values are much more
impactful than others.
It is not necessarily the case that all of the columns in the model will be examined in the time available, so it is not
guaranteed that the most impactful columns and values are displayed. However, various heuristics are employed to
ensure that the most likely columns are examined first. For example, say that after examining all the columns, it is
determined that the following columns/values have the biggest impact on the distribution, from most impact to
least:

Subcategory = Touring Bikes

Channel = Direct
Subcategory = Mountain Bikes
Subcategory = Road Bikes
Subcategory = Kids Bikes
Channel = Store

These would get output in column order, as follows:

 Subcategory: Touring Bikes, Mountain Bikes, Road Bikes (only three listed, with the text including “...amongst
others” to indicate that more than three have a significant impact)

Channel = Direct (only Direct listed, if it’s level of impact was much greater than Store)

Considerations and limitations

The following list is the collection of currently unsupported scenarios for insights:
TopN filters
Measure filters
Non-numeric measures
Use of "Show value as"
Filtered measures - filtered measures are visual level calculations with a specific filter applied (for example, Total
Sales for France), and are used on some of the visuals created by the insights feature
In addition, the following model types and data sources are currently not supported for insights:
DirectQuery
Live connect
On-premises Reporting Services
Embedding

Next steps
For more information about Power BI Desktop, and how to get started, check out the following articles.
What is Power BI Desktop?
Query Overview with Power BI Desktop
Data Sources in Power BI Desktop
Connect to Data in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Common Query Tasks in Power BI Desktop
 Use bookmarks to share insights and build stories in
Power BI
2/26/2019 • 9 minutes to read • Edit Online

Using bookmarks in Power BI help you capture the currently configured view of a report page, including filtering
and the state of visuals, and later let you go back to that state by simply selecting the saved bookmark.
You can also create a collection of bookmarks, arrange them in the order you want, and subsequently step through
each bookmark in a presentation to highlight a series of insights, or the story you want to tell with your visuals and
reports.

There are many uses for bookmarking. You can use them to keep track of your own progress in creating reports
(bookmarks are easy to add, delete, and rename) and you can create bookmarks to build a PowerPoint-like
presentation that steps through bookmarks in order, thereby telling a story with your report. There may be other
uses, too, based on how you think bookmarks could best be used.

TIP
For information about using Personal Bookmarks in the Power BI service, take a look at the blog announcement of the
Personal Bookmarks feature.

Enable the bookmarks preview (versions prior to March 2018)

Beginning with the March 2018 version of Power BI Desktop, bookmarks are generally available.
We always suggest you upgrade to the most recent release. But, if your version of Power BI Desktop is before that
release, you can try the bookmarks feature beginning with the October 2017 release of Power BI Desktop, and
for bookmark-enabled reports, in the Power BI service as well. To enable the preview feature, select File >
Options and Settings > Options > Preview Features, then select the checkbox beside Bookmarks.

You'll need to restart Power BI Desktop after you make the selection to enable the preview version of bookmarks.

Using bookmarks
To use bookmarks, select the View ribbon, then select the box for Bookmarks Pane.

When you create a bookmark, the following elements are saved with the bookmark:
The current page
Filters
 Slicers, including slicer type (for example, dropdown or list) and slicer state
Visual selection state (such as cross-highlight filters)
Sort order
Drill location
Visibility (of an object, using the Selection pane)
The focus or Spotlight modes of any visible object
Configure a report page the way you want it to appear in the bookmark. Once your report page and visuals are
arranged how you want them, select Add from the Bookmarks pane to add a bookmark.

Power BI Desktop creates a bookmark and gives it a generic name. You can easily rename, delete, or update a
bookmark by selecting the ellipses next to the bookmark's name, then selecting an action from the menu that
appears.
Once you have a bookmark, you can display it by simply clicking on the bookmark in the Bookmarks pane.
You can also select whether each bookmark will apply data properties, such as filters and slicers, the display
properties such as spotlight and its visibility, and page changes that presents the page that was visible when the
bookmark was added. These capabilities are useful when you use bookmarks to switch between report views or
selections of visuals - in which case you would likely want to turn data properties off, so filters aren't reset when
users switch views by selecting a bookmark.
To make such changes select the ellipses next to the bookmark's name, as shown in the previous image, then select
or unselect the check marks next to Data, Display, and other controls.

Arranging bookmarks
As you create bookmarks, you might find that the order in which you create them isn't necessarily the same order
you'd like to present them to your audience. No problem, you can easily rearrange the order of bookmarks.
In the Bookmarks pane, simply drag-and-drop bookmarks to change their order, as shown in the following image.
The yellow bar between bookmarks designates where the dragged bookmark will be placed.

The order of your bookmarks can become important when you use the View feature of bookmarks, as described
in the next section.

Bookmarks as a slide show

When you have a collection of bookmarks you would like to present, in order, you can select View from the
Bookmarks pane to begin a slideshow.
When in View mode, there are a few features to notice:
1. The name of the bookmark appears in the bookmark title bar, which appears at the bottom of the canvas.
2. The bookmark title bar has arrows that let you move to the next or previous bookmark.
3. You can exit View mode by selecting Exit from the Bookmarks pane or by selecting the X found in the
bookmark title bar.
When you're in View mode, you can close the Bookmarks pane (by clicking the X on that pane) to provide more
space for your presentation. And, while in View mode, all visuals are interactive and available for cross-
highlighting, just as they would otherwise be when interacting with them.

Visibility - using the Selection pane

With the release of bookmarks, the new Selection pane is also introduced. The Selection pane provides a list of
all objects on the current page and allows you to select the object and specify whether a given object is visible.

You can select an object using the Selection pane. Also, you can toggle whether the object is currently visible by
clicking the eye icon to the right of the visual.
When a bookmark is added, the visible status of each object is also saved based on its setting in the Selection
pane.
It's important to note that slicers continue to filter a report page, regardless of whether they are visible. As such,
you can create many different bookmarks, with different slicer settings, and make a single report page appear very
different (and highlight different insights) in various bookmarks.

Bookmarks for shapes and images

You can also link shapes and images to bookmarks. With this feature, when you click on an object, it will show the
bookmark associated with that object. This can be especially useful when working with buttons; you can learn more
by reading the article about using buttons in Power BI.
To assign a bookmark to an object, select the object, then expand the Action section from the Format Shape
pane, as shown in the following image.
Once you turn the Action slider to On you can select whether the object is a back button, a bookmark, or a Q&A
command. If you select bookmark, you can then select which of your bookmarks the object is linked to.
There are all sorts of interesting things you can do with object-linked bookmarking. You can create a visual table of
contents on your report page, or you can provide different views (such as visual types) of the same information,
just by clicking on an object.
When you are in editing mode you can use ctrl+click to follow the link, and when not in edit mode, simply click the
object to follow the link.

Bookmark groups
Beginning with the August 2018 release of Power BI Desktop, you can create and use bookmark groups. A
bookmark group is a collection of bookmarks that you specify, which can be shown and organized as a group.
To create a bookmark group, hold down the CTRL key and select the bookmarks you want to include in the group,
then click the ellipses beside any of the selected bookmarks, and select Group from the menu that appears.
Power BI Desktop automatically names the group Group 1. Fortunately, you can just double-click on the name
and rename it to whatever you want.

With any bookmark group, clicking on the bookmark group's name only expands or collapses the group of
bookmarks, and does not represent a bookmark by itself.
When using the View feature of bookmarks, the following applies:
If the selected bookmark is in a group when you select View from bookmarks, only the bookmarks in that
group are shown in the viewing session.
If the selected bookmark is not in a group, or is on the top level (such as the name of a bookmark group),
then all bookmarks for the entire report are played, including bookmarks in any group.
To ungroup bookmarks, just select any bookmark in a group, click the ellipses, and then select Ungroup from the
menu that appears.
Note that selecting Ungroup for any bookmark from a group takes all bookmarks out of the group (it deletes the
group, but not the bookmarks themselves). So to remove a single bookmark from a group, you need to Ungroup
any member from that group, which deletes the grouping, then select the members you want in the new group
(using CTRL and clicking each bookmark), and select Group again.

Using Spotlight
Another feature released with bookmarks is Spotlight. With Spotlight you can draw attention to a specific chart,
for example, when presenting your bookmarks in View mode.
Let's compare Spotlight to focus mode to see how they differ.
1. In focus mode, you can have one visual fill the entire canvas by selecting the focus mode icon.
2. Using Spotlight, you can highlight one visual in its original size, by making all other visuals on the page fade to
near transparency.
When the visual in the previous image has its focus icon clicked, the page looks like the following:

In contrast, when Spotlight is selected from the visual's ellipses menu, the page looks like what you seen here:
If either mode is selected when a bookmark is added, that mode (focus or Spotlight) is retained in the bookmark.

Bookmarks in the Power BI service

When you publish a report to the Power BI service with at least one bookmark, you can view and interact with
those bookmarks in the Power BI service. When bookmarks are available in a report, you can select View >
Selection pane or View > Bookmarks pane to show each of those panes.

In the Power BI service the Bookmarks pane operates just as it does in Power BI Desktop, including the ability
to select View to show your bookmarks in order, like a slide show.
Note that you must use the gray bookmark title bar to navigate through the bookmarks, and not the black arrows
(the black arrows move you through report pages, not bookmarks).

Limitations and considerations

In this release of the bookmarks, there are a few limitations and considerations to keep in mind.
 Most custom visuals should work well with bookmarking. If you run into trouble with bookmarking and a
custom visual, contact the creator of that custom visual and ask them to add support for bookmarks to their
visual.
If you add a visual on a report page after creating a bookmark, the visual will be displayed in its default state.
This also means that if you introduce a slicer into a page where you previously created bookmarks, the slicer
will behave in its default state.
Moving around visuals after a bookmark has been created will be reflected in the bookmark.

Next steps
For more information about features that are similar or interact with bookmarks, take a look at the following
articles:
Use drillthrough in Power BI Desktop
Display a dashboard tile or report visual in Focus mode
 Use Report Themes in Power BI Desktop
2/13/2019 • 34 minutes to read • Edit Online

With Report Themes you can apply a color theme to your entire report, such as corporate colors, seasonal
coloring, or other color themes. When you apply a Report Theme, all visuals in your report use the colors from
your selected theme. A few exceptions apply, and they're described later in this article.

When you apply a Report Theme, you need a JSON file that uses a basic structure. You can then import this
JSON file into Power BI Desktop and apply it to your report. The JSON file structure, and the process of
importing it, are quick and easy (just a few button clicks).
Starting with the September 2017 version of Power BI Desktop, you can define even more report theme
elements by using a JSON file. You can also customize and standardize nearly all elements. To customize, you use
the JSON file, which you manually adjust in the Formatting pane. The goal with the September 2017 release
(and later) is to give you full control over how your reports look and feel, to a granular level.
Enable Report themes
Starting with the August 2018 version of Power BI Desktop, report theming is generally available and doesn't
need to be enabled.
If you're using an earlier version of Power BI Desktop, you can enable it as a preview feature by taking the
following steps:
1. Select File > Options and Settings > Options > Preview Features.
2. Next, select the check box next to Custom Report Themes.
You'll need to restart Power BI Desktop after you make the selection.
We always recommend that you upgrade to the most recent version of Power BI Desktop, which you can get
from a link in Get Power BI Desktop.

How Report Themes work

To apply a Report Theme to a Power BI Desktop report, select from among the available built-in report themes or
import a custom theme.

BUILT-IN REPORT THEME DEFAULT COLOR SEQUENCE

Default

City park

Classroom

Colorblind safe

Electric

High contrast

Sunset

Twilight
To select from available built-in report themes, select Switch Theme button from the Home ribbon, then select
one of the included themes from the drop-down menu.

Your report theme is applied to the report, and you're ready to go.
Importing Report Themes
To import a custom Report Theme, select the Switch Theme button from the Home ribbon. Then select Import
Theme from the drop-down menu.
A window appears that lets you browse to the location of the JSON theme file. Power BI Desktop looks for JSON
files because JSON is the Power BI Report Theme file type. In the following image, a handful of holiday theme
files are available. We'll choose a holiday theme for March.

When the theme file has loaded successfully, Power BI Desktop lets you know.
Now that we've imported a theme file, let's take a look at the simple and straightforward JSON file structure.

Structure of a Report Theme JSON file

When opened in an editor, the basic JSON file that we selected in the previous section (the St Patrick's Day.json
file), looks like the following screenshot:

That JSON file has the following required lines:

name: The theme name, which is the only required field.
dataColors: The list of hex code color codes to use for data in Power BI Desktop visuals. The list can have
as many or as few colors as you want.
background, foreground, and tableAccent: The colors that should be applied in various types of visuals.
foreground applies to textbox text, KPI goal text, multi-row card text, card value text, gauge callout text,
vertical slicer element text, and table and matrix total and values text.
background applies to button fill and combo chart label background. How these colors are used
depends on the specific visual style that's applied.
table and matrix visuals apply these styles by default.
To apply a style to a table or matrix visual, take the following steps:
1. Select the visual.
2. Then, in the Visualizations pane, select the Format section.
3. Expand Matrix style, and then select a style from the Style drop-down.
Following is the text of the St Patrick's Day.json file that you can use to create your own JSON file:

{
"name": "St Patricks Day",
"dataColors": ["#568410", "#3A6108", "#70A322", "#915203", "#D79A12", "#bb7711", "#114400",
"#aacc66"],
"background":"#FFFFFF",
"foreground": "#3A6108",
"tableAccent": "#568410"
}

From there, you can enter your own color hex code for your selected colors.
Starting with the September 2017 version of Power BI Desktop, the JSON file can be much more elaborate. In
the JSON file, you define only the formatting that you want to adjust, and anything that's not specified in your
JSON file simply reverts to the Power BI default settings.
The advantages of creating a JSON file are many. For example, you can specify that all charts use a font size of 12,
or that certain visuals use a particular font family. Or you can turn off data labels for specific chart types.
When you use a granular JSON file, you can create a theme file that standardizes your charts and reports, making
it easy for your organization's reports to be consistent.
For information about the format of the detailed JSON file, see the Report theme JSON file format section
later in this article.

How Report Theme colors stick to your reports

When you publish your report to the Power BI service, your Report Theme colors stay with it.
The Data colors section of the Format panel reflects your Report Theme. For example, after we apply the
multitude of green and brown colors from the St. Patrick's Day theme, we select a visual. Then we go to Format
> Data colors and see the following information:

See all that green? That's because those colors were part of the Report Theme that we imported and applied.
Situations when Report Theme colors won't stick to your reports
Let's say you apply a custom color set (or individual color) to a particular data point in a visual. When you apply a
Report Theme, it will not override that customized data point color.
Maybe you also want to manually set the color of a data point color by using the Theme colors section. The colors
will not be updated when you apply a new Report Theme. If you want to get your default colors back, so they'll
update when you apply a new Report Theme, select Revert to default in the Theme colors palette.
Also, many Custom Visuals won't apply to Report Themes.

Report Theme files you can use right now

Want to get started with Report Themes? Here are a few ready-made Report Theme JSON files that you can
download and import into your Power BI Desktop report. We've also included an image of the Report Theme
that's applied to the report in this article.
The theme used in the blog post that announced the first release of Report Themes, called waveform.json.

The theme that's easier to read for the visually impaired than the default color theme. It's called
ColorblindSafe-Longer.json.
A group of Power View themes wrapped in a zip file, including one called Apothecary.json, which is shown
below.

Lastly, here's the Valentine's Day theme.

Rather than give you a download, we've provided the code for the Valentine's day JSON file:

{
"name": "Valentine's Day",
"dataColors": ["#990011", "#cc1144", "#ee7799", "#eebbcc", "#cc4477", "#cc5555", "#882222",
"#A30E33"],
"background":"#FFFFFF",
"foreground": "#ee7799",
"tableAccent": "#990011"
}

Report Themes can make your Power BI Desktop reports a colorful reflection of you, your organization, or even
the current season or holiday.
Here are a few more report themes you can use as starting points:
Sunflower-twilight
Plum
Autumn
High contrast

Report theme JSON file format

The basic JSON file has five required lines:
name: The theme name, which is the only required field.
dataColors: The list of hex code color codes to use for data in Power BI Desktop visuals. The list can have as
many or as few colors as you want.
background, foreground, and tableAccent: The colors that should be applied in various types of visuals.
The foreground applies to textbox text, KPI goal text, multi-row card text, card value text, gauge callout text,
vertical slicer element text, and table and matrix total and values text. The background applies to button fill
and combo chart label background. How these colors are used depends on the specific visual style that's
applied. The table and matrix visuals apply these styles by default.
To create an extended-format JSON file, with more detailed and granular control over formatting, you also need
to add a visualStyles section to the JSON file. You nest the formatting specifics in the visualStyles section. The
visualStyles section looks similar to the following format:

visualStyles: {
visualName: {
styleName: {
cardName: [{
propertyName: propertyValue
}]
}
}
}

For the visualName and cardName sections, use a specific visual and cardName. Use an asterisk ("*") if you
want that setting to apply to all visuals or cards that have a property for a specific visual. You can also use the
asterisk ("*") when you want to apply a setting globally in your report, such as a font size or specific font family for
the visuals.

NOTE
You only need to specify the formatting elements you want to adjust. Any formatting elements that are not included in the
JSON file simply revert to their default values and settings.

JSON file element definitions

The tables in this section define visual names (visualName), card names (cardName), and the enumerations that
are necessary to create your JSON file.
When you're using dateTime, the date must be an ISO date in single quotes, with datetime at the beginning.
Following is an example:

“datetime’2011-10-05T14:48:00.000Z’”

Booleans are either true or false. Strings must be in double quotes, as in "this is a string".

VISUALNAME

areaChart

barChart

basicShape

card

clusteredBarChart

clusteredColumnChart

columnChart

comboChart

donutChart
 VISUALNAME

filledMap

funnel

gauge

hundredPercentStackedBarChart

hundredPercentStackedColumnChart

image

kpi

lineChart

lineClusteredColumnComboChart

lineStackedColumnComboChart

map

multiRowCard

pieChart

pivotTable

ribbonChart

scatterChart

shapeMap

slicer

stackedAreaChart

tableEx

treemap

waterfallChart

The following table defines cardName values. The first value in each cell is the JSON file term. The second value
is the name of the card as seen in the Power BI Desktop user interface.

CARDNAME

axis: Gauge axis

CARDNAME

breakdown: Breakdown

bubbles: Bubbles

calloutValue: Callout Value

card: Card

cardTitle: Card Title

categoryAxis: X-Axis

categoryLabels: Category labels

columnFormatting: Field formatting

columnHeaders: Column headers

dataLabels: Data labels

fill: Fill

fillPoint: Fill point

forecast: Forecast

general: General

goals: Goals

grid: Grid

header: Header

imageScaling: Scaling

indicator: Indicator

items: Items

labels: Data labels

legend: Legend

lineStyles: Shapes

mapControls: Map controls

mapStyles: Map styles

 CARDNAME

numericInputStyle: Numeric inputs

percentBarLabel: Conversion Rate Label

plotArea: Plot Area

plotAreaShading: Symmetry shading

ratioLine: Ratio line

referenceLine: Constant Line

ribbonChart: Ribbons

rotation: Rotation

rowHeaders: Row headers

selection: Selection Controls

sentimentColors: Sentiment colors

shape: Shape

slider: Slider

status: Color coding

subTotals: Subtotals

target: Target

total: Grand total

trend: Trend Line

trendline: Trend axis

valueAxis: Y-Axis

values: Values

wordWrap: Word wrap

xAxisReferenceLine: X-Axis Constant Line

y1AxisReferenceLine: Constant Line

zoom: Zoom

Properties within each card

The following section defines the properties within each card:

"general":
"responsive": {
"type": [
"bool"
],
"displayName": [
"(Preview) Responsive"
],
"description": [
"The visual will adapt to size changes"
]
}
"legend": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"position": {
"type": [
"enumeration"
],
"displayName": [
"Position"
],
"description": [
"Select the location for the legend"
]
},
"showTitle": {
"type": [
"bool"
],
"displayName": [
"Title"
],
"description": [
"Display a title for legend symbols"
]
},
"labelColor": {
"type": [
"fill"
],
"displayName": [
"Color"
]
},
"fontFamily": {
"type": [
"formatting"
],
"displayName": [
"Font family"
]
},
"fontSize": {
"type": [
"formatting"
],
"displayName": [
"Text Size"
]
 ]
}
},
"categoryAxis": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"axisScale": {
"type": [
"enumeration"
],
"displayName": [
"Scale type"
]
},
"start": {
"type": [
"numeric",
"dateTime"
],
"displayName": [
"Start"
],
"description": [
"Enter a starting value (optional)"
]
},
"end": {
"type": [
"numeric",
"dateTime"
],
"displayName": [
"End"
],
"description": [
"Enter an ending value (optional)"
]
},
"axisType": {
"type": [
"enumeration"
],
"displayName": [
"Type"
]
},
"showAxisTitle": {
"type": [
"bool"
],
"displayName": [
"Title"
],
"description": [
"Title for the X-axis",
"Title for the Y-axis"
]
},
"axisStyle": {
"type": [
"enumeration"
],
"displayName": [
"Style"
 "Style"
]
},
"labelColor": {
"type": [
"fill"
],
"displayName": [
"Color"
]
},
"fontFamily": {
"type": [
"formatting"
],
"displayName": [
"Font family"
]
},
"fontSize": {
"type": [
"formatting"
],
"displayName": [
"Text Size"
]
},
"labelDisplayUnits": {
"type": [
"formatting"
],
"displayName": [
"Display units"
],
"description": [
"Select the units (millions, billions, etc.)"
]
},
"labelPrecision": {
"type": [
"numeric"
],
"displayName": [
"Value decimal places"
],
"description": [
"Select the number of decimal places to display for the values"
]
},
"concatenateLabels": {
"type": [
"bool"
],
"displayName": [
"Concatenate labels"
],
"description": [
"Always concatenate levels of the hierarchy instead of drawing the hierarchy."
]
},
"preferredCategoryWidth": {
"type": [
"numeric"
],
"displayName": [
"Minimum category width"
]
},
"titleColor": {
"type": [
 "type": [
"fill"
],
"displayName": [
"Title color"
]
},
"titleFontFamily": {
"type": [
"formatting"
],
"displayName": [
"Font family"
]
},
"titleFontSize": {
"type": [
"formatting"
],
"displayName": [
"Title text size"
]
},
"position": {
"type": [
"enumeration"
],
"displayName": [
"Position"
],
"description": [
"Select left or right"
]
},
"color": {
"type": [
"fill"
],
"displayName": [
"Color"
],
"description": [
"Select color for data labels"
]
},
"duration": {
"type": [
"numeric"
]
}
},
"valueAxis": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"position": {
"type": [
"enumeration"
],
"displayName": [
"Position"
],
"description": [
"Select left or right"
]
 ]
},
"axisScale": {
"type": [
"enumeration"
],
"displayName": [
"Scale type"
]
},
"start": {
"type": [
"numeric",
"dateTime"
],
"displayName": [
"Start"
],
"description": [
"Enter a starting value (optional)"
]
},
"end": {
"type": [
"numeric",
"dateTime"
],
"displayName": [
"End"
],
"description": [
"Enter an ending value (optional)"
]
},
"showAxisTitle": {
"type": [
"bool"
],
"displayName": [
"Title"
],
"description": [
"Title for the Y-axis",
"Title for the X-axis"
]
},
"axisStyle": {
"type": [
"enumeration"
],
"displayName": [
"Style"
]
},
"labelColor": {
"type": [
"fill"
],
"displayName": [
"Color"
]
},
"fontFamily": {
"type": [
"formatting"
],
"displayName": [
"Font family"
]
},
"fontSize": {
"type": [
"formatting"
],
"displayName": [
"Text Size"
]
},
"labelDisplayUnits": {
"type": [
"formatting"
],
"displayName": [
"Display units"
],
"description": [
"Select the units (millions, billions, etc.)"
]
},
"labelPrecision": {
"type": [
"numeric"
],
"displayName": [
"Value decimal places"
],
"description": [
"Select the number of decimal places to display for the values"
]
},
"titleColor": {
"type": [
"fill"
],
"displayName": [
"Title color"
]
},
"titleFontFamily": {
"type": [
"formatting"
],
"displayName": [
"Font family"
]
},
"titleFontSize": {
"type": [
"formatting"
],
"displayName": [
"Title text size"
]
},
"axisLabel": {
"type": [
"none"
],
"displayName": [
"Y-Axis (Column)"
]
},
"secShow": {
"type": [
"bool"
],
"displayName": [
"Show secondary"
 ]
},
"alignZeros": {
"type": [
"bool"
],
"displayName": [
"Align zeros"
],
"description": [
"Align the zero tick marks for both value axes"
]
},
"secAxisLabel": {
"type": [
"none"
],
"displayName": [
"Y-Axis (Line)"
]
},
"secPosition": {
"type": [
"enumeration"
],
"displayName": [
"Position"
],
"description": [
"Select left or right"
]
},
"secAxisScale": {
"type": [
"enumeration"
],
"displayName": [
"Scale type"
]
},
"secStart": {
"type": [
"numeric"
],
"displayName": [
"Start"
],
"description": [
"Enter a starting value (optional)"
]
},
"secEnd": {
"type": [
"numeric"
],
"displayName": [
"End"
],
"description": [
"Enter an ending value (optional)"
]
},
"secShowAxisTitle": {
"type": [
"bool"
],
"displayName": [
"Title"
],
 ],
"description": [
"Title for the Y-axis"
]
},
"secAxisStyle": {
"type": [
"enumeration"
],
"displayName": [
"Style"
]
},
"secLabelColor": {
"type": [
"fill"
],
"displayName": [
"Color"
]
},
"secFontFamily": {
"type": [
"formatting"
],
"displayName": [
"Font family"
]
},
"secFontSize": {
"type": [
"formatting"
],
"displayName": [
"Text Size"
]
},
"secLabelDisplayUnits": {
"type": [
"formatting"
],
"displayName": [
"Display units"
],
"description": [
"Select the units (millions, billions, etc.)"
]
},
"secLabelPrecision": {
"type": [
"numeric"
],
"displayName": [
"Value decimal places"
],
"description": [
"Select the number of decimal places to display for the values"
]
},
"secTitleColor": {
"type": [
"fill"
],
"displayName": [
"Title color"
]
},
"secTitleFontFamily": {
"type": [
"formatting"
 "formatting"
],
"displayName": [
"Font family"
]
},
"secTitleFontSize": {
"type": [
"formatting"
],
"displayName": [
"Title text size"
]
}
},
"dataPoint": {
"defaultColor": {
"type": [
"fill"
],
"displayName": [
"Default color",
"Default Column Color"
]
},
"fill": {
"type": [
"fill"
],
"displayName": [
"Fill"
]
},
"defaultCategoryColor": {
"type": [
"fill"
],
"displayName": [
"Default color",
"Default Column Color"
]
},
"showAllDataPoints": {
"type": [
"bool"
],
"displayName": [
"Show all"
]
}
},
"labels": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"showSeries": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"color": {
"type": [
 "type": [
"fill"
],
"displayName": [
"Color"
],
"description": [
"Select color for data labels"
]
},
"labelDisplayUnits": {
"type": [
"formatting"
],
"displayName": [
"Display units"
],
"description": [
"Select the units (millions, billions, etc.)"
]
},
"labelPrecision": {
"type": [
"numeric"
],
"displayName": [
"Value decimal places"
],
"description": [
"Select the number of decimal places to display for the values"
]
},
"showAll": {
"type": [
"bool"
],
"displayName": [
"Customize series"
]
},
"fontSize": {
"type": [
"formatting"
],
"displayName": [
"Text Size"
]
},
"fontFamily": {
"type": [
"formatting"
],
"displayName": [
"Font family"
]
},
"labelDensity": {
"type": [
"formatting"
],
"displayName": [
"Label density"
]
},
"labelOrientation": {
"type": [
"enumeration"
],
"displayName": [
"Orientation"
 "Orientation"
]
},
"labelPosition": {
"type": [
"enumeration"
],
"displayName": [
"Position"
]
},
"percentageLabelPrecision": {
"type": [
"numeric"
],
"displayName": [
"% decimal places"
],
"description": [
"Select the number of decimal places to display for the percentages"
]
},
"labelStyle": {
"type": [
"enumeration"
],
"displayName": [
"Label style"
]
}
},
"lineStyles": {
"strokeWidth": {
"type": [
"numeric"
],
"displayName": [
"Stroke width"
]
},
"strokeLineJoin": {
"type": [
"enumeration"
],
"displayName": [
"Join type"
]
},
"lineStyle": {
"type": [
"enumeration"
],
"displayName": [
"Line style"
]
},
"showMarker": {
"type": [
"bool"
],
"displayName": [
"Show marker"
]
},
"markerShape": {
"type": [
"enumeration"
],
"displayName": [
"Marker shape"
 "Marker shape"
]
},
"markerSize": {
"type": [
"numeric"
],
"displayName": [
"Marker size"
]
},
"markerColor": {
"type": [
"fill"
],
"displayName": [
"Marker color"
]
},
"showSeries": {
"type": [
"bool"
],
"displayName": [
"Customize series",
"Show"
]
},
"shadeArea": {
"type": [
"bool"
],
"displayName": [
"Shade area"
]
}
},
"plotArea": {
"transparency": {
"type": [
"numeric"
],
"displayName": [
"Transparency"
],
"description": [
"Set transparency for background color"
]
}
},
"trend": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"displayName": {
"type": [
"text"
],
"displayName": [
"Name"
],
"description": [
"Set trend line name"
]
 },
"lineColor": {
"type": [
"fill"
],
"displayName": [
"Color"
],
"description": [
"Set trend line color"
]
},
"transparency": {
"type": [
"numeric"
],
"displayName": [
"Transparency"
],
"description": [
"Set transparency for trend line color"
]
},
"style": {
"type": [
"enumeration"
],
"displayName": [
"Style"
],
"description": [
"Set trend line style"
]
},
"combineSeries": {
"type": [
"bool"
],
"displayName": [
"Combine Series"
],
"description": [
"Show one trend line per series or combine"
]
}
},
"y1AxisReferenceLine": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"value": {
"type": [
"numeric"
],
"displayName": [
"Value"
],
"description": [
"Set reference line numeric value"
]
},
"lineColor": {
"type": [
"fill"
 "fill"
],
"displayName": [
"Color"
],
"description": [
"Set reference line color"
]
},
"transparency": {
"type": [
"numeric"
],
"displayName": [
"Transparency"
],
"description": [
"Set transparency for reference line color"
]
},
"style": {
"type": [
"enumeration"
],
"displayName": [
"Line style"
]
},
"position": {
"type": [
"enumeration"
],
"displayName": [
"Position"
],
"description": [
"Arrange relative to chart data points"
]
},
"dataLabelShow": {
"type": [
"bool"
],
"displayName": [
"Data label"
],
"description": [
"Display a data label for the reference line"
]
},
"dataLabelColor": {
"type": [
"fill"
],
"displayName": [
"Color"
],
"description": [
"Set the reference line data label color"
]
},
"dataLabelDecimalPoints": {
"type": [
"numeric"
],
"displayName": [
"Decimal Places"
]
},
"dataLabelHorizontalPosition": {
 "dataLabelHorizontalPosition": {
"type": [
"enumeration"
],
"displayName": [
"Horizontal Position"
],
"description": [
"Set the horizontal position for the reference line data label"
]
},
"dataLabelVerticalPosition": {
"type": [
"enumeration"
],
"displayName": [
"Vertical Position"
],
"description": [
"Set the vertical position for the reference line data label"
]
},
"dataLabelDisplayUnits": {
"type": [
"formatting"
],
"displayName": [
"Display units"
],
"description": [
"Select the units (millions, billions, etc.)"
]
}
},
"referenceLine": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"displayName": {
"type": [
"text"
],
"displayName": [
"Name"
],
"description": [
"Set reference line name"
]
},
"value": {
"type": [
"numeric"
],
"displayName": [
"Value"
],
"description": [
"Set reference line numeric value"
]
},
"lineColor": {
"type": [
"fill"
],
"displayName": [
 "displayName": [
"Color"
],
"description": [
"Set reference line color"
]
},
"transparency": {
"type": [
"numeric"
],
"displayName": [
"Transparency"
],
"description": [
"Set transparency for reference line color"
]
},
"style": {
"type": [
"enumeration"
],
"displayName": [
"Line style"
]
},
"position": {
"type": [
"enumeration"
],
"displayName": [
"Position"
],
"description": [
"Arrange relative to chart data points"
]
},
"dataLabelShow": {
"type": [
"bool"
],
"displayName": [
"Data label"
],
"description": [
"Display a data label for the reference line"
]
},
"dataLabelColor": {
"type": [
"fill"
],
"displayName": [
"Color"
],
"description": [
"Set the reference line data label color"
]
},
"dataLabelDecimalPoints": {
"type": [
"numeric"
],
"displayName": [
"Decimal Places"
]
},
"dataLabelHorizontalPosition": {
"type": [
"enumeration"
 "enumeration"
],
"displayName": [
"Horizontal Position"
],
"description": [
"Set the horizontal position for the reference line data label"
]
},
"dataLabelVerticalPosition": {
"type": [
"enumeration"
],
"displayName": [
"Vertical Position"
],
"description": [
"Set the vertical position for the reference line data label"
]
},
"dataLabelDisplayUnits": {
"type": [
"formatting"
],
"displayName": [
"Display units"
],
"description": [
"Select the units (millions, billions, etc.)"
]
}
},
"line": {
"lineColor": {
"type": [
"fill"
],
"displayName": [
"Line color"
]
},
"transparency": {
"type": [
"numeric"
],
"displayName": [
"Transparency"
],
"description": [
"Set transparency for background color"
]
},
"weight": {
"type": [
"numeric"
],
"displayName": [
"Weight"
]
},
"roundEdge": {
"type": [
"numeric"
],
"displayName": [
"Round edges"
]
}
},
"fill": {
"fill": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"fillColor": {
"type": [
"fill"
],
"displayName": [
"Fill color"
]
},
"transparency": {
"type": [
"numeric"
],
"displayName": [
"Transparency"
],
"description": [
"Set transparency for background color"
]
}
},
"rotation": {
"angle": {
"type": [
"numeric"
],
"displayName": [
"Rotation"
]
}
},
"categoryLabels": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"color": {
"type": [
"fill"
],
"displayName": [
"Color"
],
"description": [
"Select color for data labels"
]
},
"fontSize": {
"type": [
"formatting"
],
"displayName": [
"Text Size"
]
},
"fontFamily": {
"type": [
 "formatting"
],
"displayName": [
"Font family"
]
}
},
"wordWrap": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
}
},
"dataLabels": {
"color": {
"type": [
"fill"
],
"displayName": [
"Color"
],
"description": [
"Select color for data labels"
]
},
"fontSize": {
"type": [
"formatting"
],
"displayName": [
"Text Size"
]
},
"fontFamily": {
"type": [
"formatting"
],
"displayName": [
"Font family"
]
}
},
"cardTitle": {
"color": {
"type": [
"fill"
],
"displayName": [
"Color"
],
"description": [
"Select color for data labels"
]
},
"fontSize": {
"type": [
"formatting"
],
"displayName": [
"Text Size"
]
},
"fontFamily": {
"type": [
"formatting"
 ],
"displayName": [
"Font family"
]
}
},
"card": {
"outline": {
"type": [
"enumeration"
],
"displayName": [
"Outline"
]
},
"outlineColor": {
"type": [
"fill"
],
"displayName": [
"Outline color"
],
"description": [
"Color of the outline"
]
},
"outlineWeight": {
"type": [
"numeric"
],
"displayName": [
"Outline weight"
],
"description": [
"Thickness of the outline in pixels"
]
},
"barShow": {
"type": [
"bool"
],
"displayName": [
"Show bar"
],
"description": [
"Display a bar to the left side of the card as an accent"
]
},
"barColor": {
"type": [
"fill"
],
"displayName": [
"Bar color"
]
},
"barWeight": {
"type": [
"numeric"
],
"displayName": [
"Bar thickness"
],
"description": [
"Thickness of the bar in pixels"
]
},
"cardPadding": {
"type": [
 "type": [
"numeric"
],
"displayName": [
"Padding"
],
"description": [
"Background"
]
},
"cardBackground": {
"type": [
"fill"
],
"displayName": [
"Background"
]
}
},
"percentBarLabel": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"color": {
"type": [
"fill"
],
"displayName": [
"Color"
],
"description": [
"Select color for data labels"
]
},
"fontSize": {
"type": [
"formatting"
],
"displayName": [
"Text Size"
]
},
"fontFamily": {
"type": [
"formatting"
],
"displayName": [
"Font family"
]
}
},
"axis": {
"min": {
"type": [
"numeric"
],
"displayName": [
"Min"
]
},
"max": {
"type": [
"numeric"
],
"displayName": [
 "displayName": [
"Max"
]
},
"target": {
"type": [
"numeric"
],
"displayName": [
"Target"
]
}
},
"target": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"color": {
"type": [
"fill"
],
"displayName": [
"Color"
],
"description": [
"Select color for data labels"
]
},
"labelDisplayUnits": {
"type": [
"formatting"
],
"displayName": [
"Display units"
],
"description": [
"Select the units (millions, billions, etc.)"
]
},
"labelPrecision": {
"type": [
"numeric"
],
"displayName": [
"Value decimal places"
],
"description": [
"Select the number of decimal places to display for the values"
]
},
"fontSize": {
"type": [
"formatting"
],
"displayName": [
"Text Size"
]
},
"fontFamily": {
"type": [
"formatting"
],
"displayName": [
"Font family"
]
 ]
}
},
"calloutValue": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"color": {
"type": [
"fill"
],
"displayName": [
"Color"
],
"description": [
"Select color for data labels"
]
},
"labelDisplayUnits": {
"type": [
"formatting"
],
"displayName": [
"Display units"
],
"description": [
"Select the units (millions, billions, etc.)"
]
},
"labelPrecision": {
"type": [
"numeric"
],
"displayName": [
"Value decimal places"
],
"description": [
"Select the number of decimal places to display for the values"
]
}
},
"forecast": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"displayName": {
"type": [
"text"
],
"displayName": [
"Name"
],
"description": [
"Set forecast name"
]
},
"confidenceBandStyle": {
"type": [
"enumeration"
],
 ],
"displayName": [
"Confidence band style"
],
"description": [
"Set forecast confidence band style"
]
},
"lineColor": {
"type": [
"fill"
],
"displayName": [
"Color"
],
"description": [
"Set forecast line color"
]
},
"transparency": {
"type": [
"numeric"
],
"displayName": [
"Transparency"
],
"description": [
"Set transparency for background color"
]
},
"style": {
"type": [
"enumeration"
],
"displayName": [
"Line style"
]
},
"transform": {
"type": [
"queryTransform"
]
}
},
"bubbles": {
"bubbleSize": {
"type": [
"formatting"
],
"displayName": [
"Size"
]
}
},
"mapControls": {
"autoZoom": {
"type": [
"bool"
],
"displayName": [
"Auto zoom"
]
},
"zoomLevel": {
"type": [
"numeric"
]
},
"centerLatitude": {
 "type": [
"numeric"
]
},
"centerLongitude": {
"type": [
"numeric"
]
}
},
"mapStyles": {
"mapTheme": {
"type": [
"enumeration"
],
"displayName": [
"Theme"
]
}
},
"shape": {
"map": {
"type": [
"geoJson"
]
},
"projectionEnum": {
"type": [
"enumeration"
],
"displayName": [
"Projection"
],
"description": [
"Projection"
]
}
},
"zoom": {
"autoZoom": {
"type": [
"bool"
],
"displayName": [
"Auto zoom"
],
"description": [
"Zoom in on shapes with available data"
]
},
"selectionZoom": {
"type": [
"bool"
],
"displayName": [
"Selection zoom"
],
"description": [
"Zoom in on selected shapes"
]
},
"manualZoom": {
"type": [
"bool"
],
"displayName": [
"Manual zoom"
],
"description": [
 "Allow user to zoom and pan"
]
}
},
"xAxisReferenceLine": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"value": {
"type": [
"numeric"
],
"displayName": [
"Value"
],
"description": [
"Set reference line numeric value"
]
},
"lineColor": {
"type": [
"fill"
],
"displayName": [
"Color"
],
"description": [
"Set reference line color"
]
},
"transparency": {
"type": [
"numeric"
],
"displayName": [
"Transparency"
],
"description": [
"Set transparency for reference line color"
]
},
"style": {
"type": [
"enumeration"
],
"displayName": [
"Line style"
]
},
"position": {
"type": [
"enumeration"
],
"displayName": [
"Position"
],
"description": [
"Arrange relative to chart data points"
]
},
"dataLabelShow": {
"type": [
"bool"
],
 ],
"displayName": [
"Data label"
],
"description": [
"Display a data label for the reference line"
]
},
"dataLabelColor": {
"type": [
"fill"
],
"displayName": [
"Color"
],
"description": [
"Set the reference line data label color"
]
},
"dataLabelDecimalPoints": {
"type": [
"numeric"
],
"displayName": [
"Decimal Places"
]
},
"dataLabelHorizontalPosition": {
"type": [
"enumeration"
],
"displayName": [
"Horizontal Position"
],
"description": [
"Set the horizontal position for the reference line data label"
]
},
"dataLabelVerticalPosition": {
"type": [
"enumeration"
],
"displayName": [
"Vertical Position"
],
"description": [
"Set the vertical position for the reference line data label"
]
},
"dataLabelDisplayUnits": {
"type": [
"formatting"
],
"displayName": [
"Display units"
],
"description": [
"Select the units (millions, billions, etc.)"
]
}
},
"fillPoint": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
}
 }
},
"colorByCategory": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
}
},
"plotAreaShading": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"upperShadingColor": {
"type": [
"fill"
],
"displayName": [
"Upper shading"
],
"description": [
"Shading color of the upper region"
]
},
"lowerShadingColor": {
"type": [
"fill"
],
"displayName": [
"Lower shading"
],
"description": [
"Shading color of the lower region"
]
},
"transparency": {
"type": [
"numeric"
],
"displayName": [
"Transparency"
],
"description": [
"Set transparency for background color"
]
}
},
"ratioLine": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"lineColor": {
"type": [
"fill"
],
"displayName": [
"Color"
 "Color"
],
"description": [
"Set reference line color"
]
},
"transparency": {
"type": [
"numeric"
],
"displayName": [
"Transparency"
],
"description": [
"Set transparency for line color"
]
},
"style": {
"type": [
"enumeration"
],
"displayName": [
"Line style"
]
}
},
"grid": {
"outlineColor": {
"type": [
"fill"
],
"displayName": [
"Outline color"
],
"description": [
"Color of the outline"
]
},
"outlineWeight": {
"type": [
"numeric"
],
"displayName": [
"Outline weight"
],
"description": [
"Thickness of the outline in pixels"
]
},
"gridVertical": {
"type": [
"bool"
],
"displayName": [
"Vert grid"
],
"description": [
"Show/Hide the vertical gridlines"
]
},
"gridVerticalColor": {
"type": [
"fill"
],
"displayName": [
"Vert grid color"
],
"description": [
"Color for the vertical gridlines"
]
 ]
},
"gridVerticalWeight": {
"type": [
"numeric"
],
"displayName": [
"Vert grid thickness"
],
"description": [
"Thickness of the vertical gridlines in pixels"
]
},
"gridHorizontal": {
"type": [
"bool"
],
"displayName": [
"Horiz grid"
],
"description": [
"Show/Hide the horizontal gridlines"
]
},
"gridHorizontalColor": {
"type": [
"fill"
],
"displayName": [
"Horiz grid color"
],
"description": [
"Color for the horizontal gridlines"
]
},
"gridHorizontalWeight": {
"type": [
"numeric"
],
"displayName": [
"Horiz grid thickness"
],
"description": [
"Thickness of the horizontal gridlines in pixels"
]
},
"rowPadding": {
"type": [
"numeric"
],
"displayName": [
"Row padding"
],
"description": [
"Padding in pixels applied to top and bottom of every row"
]
},
"imageHeight": {
"type": [
"numeric"
],
"displayName": [
"Image height"
],
"description": [
"The height of images in pixels"
]
},
"textSize": {
"type": [
 "type": [
"numeric"
],
"displayName": [
"Text Size"
]
}
},
"columnHeaders": {
"outline": {
"type": [
"enumeration"
],
"displayName": [
"Outline"
]
},
"fontColor": {
"type": [
"fill"
],
"displayName": [
"Font color"
],
"description": [
"Font color of the cells"
]
},
"backColor": {
"type": [
"fill"
],
"displayName": [
"Background color"
],
"description": [
"Background color of the cells"
]
},
"wordWrap": {
"type": [
"bool"
],
"displayName": [
"Word wrap"
]
},
"fontFamily": {
"type": [
"formatting"
],
"displayName": [
"Font family"
]
},
"fontSize": {
"type": [
"formatting"
],
"displayName": [
"Text Size"
]
},
"autoSizeColumnWidth": {
"type": [
"bool"
],
"displayName": [
"Auto-size column width"
 ]
},
"urlIcon": {
"type": [
"bool"
],
"displayName": [
"URL icon"
],
"description": [
"Show an icon instead of the full URL"
]
}
},
"values": {
"outline": {
"type": [
"enumeration"
],
"displayName": [
"Outline"
]
},
"backColor": {
"type": [
"fill"
],
"displayName": [
"Color scales"
]
},
"fontColorPrimary": {
"type": [
"fill"
],
"displayName": [
"Font color"
],
"description": [
"Font color of the odd rows"
]
},
"backColorPrimary": {
"type": [
"fill"
],
"displayName": [
"Background color"
],
"description": [
"Background color of the odd rows"
]
},
"fontColorSecondary": {
"type": [
"fill"
],
"displayName": [
"Alternate font color"
],
"description": [
"Font color of the even rows"
]
},
"backColorSecondary": {
"type": [
"fill"
],
"displayName": [
 "displayName": [
"Alternate background color"
],
"description": [
"Background color of the even rows"
]
},
"urlIcon": {
"type": [
"bool"
],
"displayName": [
"URL icon"
],
"description": [
"Show an icon instead of the full URL"
]
},
"fontFamily": {
"type": [
"formatting"
],
"displayName": [
"Font family"
]
},
"fontSize": {
"type": [
"formatting"
],
"displayName": [
"Text Size"
]
},
"wordWrap": {
"type": [
"bool"
],
"displayName": [
"Word wrap"
]
},
"bandedRowHeaders": {
"type": [
"bool"
],
"displayName": [
"Banded row style"
],
"description": [
"Apply banded row style to the last level of the row group headers, using the colors of the
values."
]
},
"valuesOnRow": {
"type": [
"bool"
],
"displayName": [
"Show on rows"
],
"description": [
"Show values in row groups rather than columns"
]
}
},
"total": {
"outline": {
"type": [
"enumeration"
 "enumeration"
],
"displayName": [
"Outline"
]
},
"fontColor": {
"type": [
"fill"
],
"displayName": [
"Font color"
],
"description": [
"Font color of the cells"
]
},
"backColor": {
"type": [
"fill"
],
"displayName": [
"Background color"
],
"description": [
"Background color of the cells"
]
},
"applyToHeaders": {
"type": [
"bool"
],
"displayName": [
"Apply to labels"
]
},
"totals": {
"type": [
"bool"
],
"displayName": [
"Totals"
]
},
"fontFamily": {
"type": [
"formatting"
],
"displayName": [
"Font family"
]
},
"fontSize": {
"type": [
"formatting"
],
"displayName": [
"Text Size"
]
}
},
"columnFormatting": {
"fontColor": {
"type": [
"fill"
],
"displayName": [
"Font color"
],
"description": [
 "description": [
"Font color of the cells"
]
},
"backColor": {
"type": [
"fill"
],
"displayName": [
"Background color"
],
"description": [
"Background color of the cells"
]
},
"styleHeader": {
"type": [
"bool"
],
"displayName": [
"Color header"
]
},
"styleValues": {
"type": [
"bool"
],
"displayName": [
"Color values"
]
},
"styleTotal": {
"type": [
"bool"
],
"displayName": [
"Color total"
]
},
"styleSubtotals": {
"type": [
"bool"
],
"displayName": [
"Color subtotals"
]
}
},
"rowHeaders": {
"outline": {
"type": [
"enumeration"
],
"displayName": [
"Outline"
]
},
"fontColor": {
"type": [
"fill"
],
"displayName": [
"Font color"
],
"description": [
"Font color of the cells"
]
},
"backColor": {
"type": [
 "type": [
"fill"
],
"displayName": [
"Background color"
],
"description": [
"Background color of the cells"
]
},
"wordWrap": {
"type": [
"bool"
],
"displayName": [
"Word wrap"
]
},
"fontFamily": {
"type": [
"formatting"
],
"displayName": [
"Font family"
]
},
"fontSize": {
"type": [
"formatting"
],
"displayName": [
"Text Size"
]
},
"stepped": {
"type": [
"bool"
],
"displayName": [
"Stepped layout"
],
"description": [
"Render row headers with stepped layout"
]
},
"steppedLayoutIndentation": {
"type": [
"numeric"
],
"displayName": [
"Stepped layout indentation"
],
"description": [
"Set the indentation, in pixels, applied to row headers"
]
},
"urlIcon": {
"type": [
"bool"
],
"displayName": [
"URL icon"
],
"description": [
"Show an icon instead of the full URL"
]
}
},
"subTotals": {
"outline": {
"outline": {
"type": [
"enumeration"
],
"displayName": [
"Outline"
]
},
"fontColor": {
"type": [
"fill"
],
"displayName": [
"Font color"
],
"description": [
"Font color of the cells"
]
},
"backColor": {
"type": [
"fill"
],
"displayName": [
"Background color"
],
"description": [
"Background color of the cells"
]
},
"fontFamily": {
"type": [
"formatting"
],
"displayName": [
"Font family"
]
},
"fontSize": {
"type": [
"formatting"
],
"displayName": [
"Text Size"
]
},
"rowSubtotals": {
"type": [
"bool"
],
"displayName": [
"Total row"
]
},
"columnSubtotals": {
"type": [
"bool"
],
"displayName": [
"Total column"
]
},
"applyToHeaders": {
"type": [
"bool"
],
"displayName": [
"Apply to labels"
]
 }
},
"selection": {
"selectAllCheckboxEnabled": {
"type": [
"bool"
],
"displayName": [
"Select All"
]
},
"singleSelect": {
"type": [
"bool"
],
"displayName": [
"Single Select"
]
}
},
"header": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"fontColor": {
"type": [
"fill"
],
"displayName": [
"Font color"
],
"description": [
"Font color of the cells"
]
},
"background": {
"type": [
"fill"
],
"displayName": [
"Background"
]
},
"outline": {
"type": [
"enumeration"
],
"displayName": [
"Outline"
]
},
"textSize": {
"type": [
"numeric"
],
"displayName": [
"Text Size"
]
},
"fontFamily": {
"type": [
"formatting"
],
"displayName": [
 "Font family"
]
}
},
"items": {
"fontColor": {
"type": [
"fill"
],
"displayName": [
"Font color"
],
"description": [
"Font color of the cells"
]
},
"background": {
"type": [
"fill"
],
"displayName": [
"Background"
]
},
"outline": {
"type": [
"enumeration"
],
"displayName": [
"Outline"
]
},
"textSize": {
"type": [
"numeric"
],
"displayName": [
"Text Size"
]
},
"fontFamily": {
"type": [
"formatting"
],
"displayName": [
"Font family"
]
}
},
"numericInputStyle": {
"fontColor": {
"type": [
"fill"
],
"displayName": [
"Font color"
],
"description": [
"Font color of the cells"
]
},
"textSize": {
"type": [
"numeric"
],
"displayName": [
"Text Size"
]
},
 },
"fontFamily": {
"type": [
"formatting"
],
"displayName": [
"Font family"
]
},
"background": {
"type": [
"fill"
],
"displayName": [
"Background"
]
}
},
"slider": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
},
"color": {
"type": [
"fill"
],
"displayName": [
"Color"
]
}
},
"dateRange": {
"includeToday": {
"type": [
"bool"
],
"displayName": [
"Include today"
]
}
},
"sentimentColors": {
"increaseFill": {
"type": [
"fill"
],
"displayName": [
"Increase"
]
},
"decreaseFill": {
"type": [
"fill"
],
"displayName": [
"Decrease"
]
},
"totalFill": {
"type": [
"fill"
],
"displayName": [
"Total"
]
 ]
},
"otherFill": {
"type": [
"fill"
],
"displayName": [
"Other"
]
}
},
"breakdown": {
"maxBreakdowns": {
"type": [
"integer"
],
"displayName": [
"Max breakdowns"
],
"description": [
"The number of individual breakdowns to show (rest grouped into Other)"
]
}
},
"indicator": {
"indicatorDisplayUnits": {
"type": [
"formatting"
],
"displayName": [
"Display units"
],
"description": [
"Select the units (millions, billions, etc.)"
]
},
"indicatorPrecision": {
"type": [
"numeric"
],
"displayName": [
"Value decimal places"
],
"description": [
"Select the number of decimal places to display for the values"
]
},
"kpiFormat": {
"type": [
"text"
],
"displayName": [
"Format"
]
}
},
"trendline": {
"show": {
"type": [
"bool"
],
"displayName": [
"Show"
]
}
},
"goals": {
"showGoal": {
"type": [
"bool"
 "bool"
],
"displayName": [
"Goal"
]
},
"showDistance": {
"type": [
"bool"
],
"displayName": [
"Distance"
]
}
},
"status": {
"direction": {
"type": [
"enumeration"
],
"displayName": [
"Direction"
]
},
"goodColor": {
"type": [
"fill"
],
"displayName": [
"Good Color"
]
},
"neutralColor": {
"type": [
"fill"
],
"displayName": [
"Neutral Color"
]
},
"badColor": {
"type": [
"fill"
],
"displayName": [
"Bad Color"
]
}
}

Enumerations in the JSON file

The following section defines the enumerations that you can use in the JSON file.

{
"legend": {
"position": [
{
"value": "Top",
"displayName": "Top"
},
{
"value": "Bottom",
"displayName": "Bottom"
},
{
"value": "Left",
"displayName": "Left"
 "displayName": "Left"
},
{
"value": "Right",
"displayName": "Right"
},
{
"value": "TopCenter",
"displayName": "Top Center"
},
{
"value": "BottomCenter",
"displayName": "Bottom Center"
},
{
"value": "LeftCenter",
"displayName": "Left Center"
},
{
"value": "RightCenter",
"displayName": "Right center"
}
],
"legendMarkerRendering": [
{
"value": "markerOnly",
"displayName": "Markers only"
},
{
"value": "lineAndMarker",
"displayName": "Line and markers"
},
{
"value": "lineOnly",
"displayName": "Line only"
}
]
},
"categoryAxis": {
"axisScale": [
{
"value": "linear",
"displayName": "Linear"
},
{
"value": "log",
"displayName": "Log"
}
],
"axisType": [
{
"value": "Scalar",
"displayName": "Continuous"
},
{
"value": "Categorical",
"displayName": "Categorical"
}
],
"axisStyle": [
{
"value": "showTitleOnly",
"displayName": "Show title only"
},
{
"value": "showUnitOnly",
"displayName": "Show unit only"
},
{
"value": "showBoth",
 "value": "showBoth",
"displayName": "Show both"
}
],
"gridlineStyle": [
{
"value": "dashed",
"displayName": "Dashed"
},
{
"value": "solid",
"displayName": "Solid"
},
{
"value": "dotted",
"displayName": "Dotted"
}
],
"position": [
{
"value": "Left",
"displayName": "Left"
},
{
"value": "Right",
"displayName": "Right"
}
]
},
"valueAxis": {
"position": [
{
"value": "Left",
"displayName": "Left"
},
{
"value": "Right",
"displayName": "Right"
}
],
"axisScale": [
{
"value": "linear",
"displayName": "Linear"
},
{
"value": "log",
"displayName": "Log"
}
],
"axisStyle": [
{
"value": "showTitleOnly",
"displayName": "Show title only"
},
{
"value": "showUnitOnly",
"displayName": "Show unit only"
},
{
"value": "showBoth",
"displayName": "Show both"
}
],
"gridlineStyle": [
{
"value": "dashed",
"displayName": "Dashed"
},
{
 {
"value": "solid",
"displayName": "Solid"
},
{
"value": "dotted",
"displayName": "Dotted"
}
],
"secPosition": [
{
"value": "Left",
"displayName": "Left"
},
{
"value": "Right",
"displayName": "Right"
}
],
"secAxisScale": [
{
"value": "linear",
"displayName": "Linear"
},
{
"value": "log",
"displayName": "Log"
}
],
"secAxisStyle": [
{
"value": "showTitleOnly",
"displayName": "Show title only"
},
{
"value": "showUnitOnly",
"displayName": "Show unit only"
},
{
"value": "showBoth",
"displayName": "Show both"
}
]
},
"lineStyles": {
"strokeLineJoin": [
{
"value": "miter",
"displayName": "Miter"
},
{
"value": "round",
"displayName": "Round"
},
{
"value": "bevel",
"displayName": "Bevel"
}
],
"lineStyle": [
{
"value": "dashed",
"displayName": "Dashed"
},
{
"value": "solid",
"displayName": "Solid"
},
{
"value": "dotted",
 "value": "dotted",
"displayName": "Dotted"
}
],
"markerShape": [
{
"value": "circle",
"displayName": "●"
},
{
"value": "square",
"displayName": "■"
},
{
"value": "diamond",
"displayName": "◆"
},
{
"value": "triangle",
"displayName": "▲"
},
{
"value": "x",
"displayName": "☓"
},
{
"value": "shortDash",
"displayName": " -"
},
{
"value": "longDash",
"displayName": "—"
},
{
"value": "plus",
"displayName": "+"
}
]
},
"trend": {
"style": [
{
"value": "dashed",
"displayName": "Dashed"
},
{
"value": "solid",
"displayName": "Solid"
},
{
"value": "dotted",
"displayName": "Dotted"
}
]
},
"y1AxisReferenceLine": {
"style": [
{
"value": "dashed",
"displayName": "Dashed"
},
{
"value": "solid",
"displayName": "Solid"
},
{
"value": "dotted",
"displayName": "Dotted"
}
],
 ],
"position": [
{
"value": "back",
"displayName": "Behind"
},
{
"value": "front",
"displayName": "In Front"
}
],
"dataLabelText": [
{
"value": "Value",
"displayName": "Value"
},
{
"value": "Name",
"displayName": "Name"
},
{
"value": "ValueAndName",
"displayName": "Name and Value"
}
],
"dataLabelHorizontalPosition": [
{
"value": "left",
"displayName": "Left"
},
{
"value": "right",
"displayName": "Right"
}
],
"dataLabelVerticalPosition": [
{
"value": "above",
"displayName": "Above"
},
{
"value": "under",
"displayName": "Under"
}
]
},
"referenceLine": {
"style": [
{
"value": "dashed",
"displayName": "Dashed"
},
{
"value": "solid",
"displayName": "Solid"
},
{
"value": "dotted",
"displayName": "Dotted"
}
],
"position": [
{
"value": "back",
"displayName": "Behind"
},
{
"value": "front",
"displayName": "In Front"
 }
],
"dataLabelText": [
{
"value": "Value",
"displayName": "Value"
},
{
"value": "Name",
"displayName": "Name"
},
{
"value": "ValueAndName",
"displayName": "Name and Value"
}
],
"dataLabelHorizontalPosition": [
{
"value": "left",
"displayName": "Left"
},
{
"value": "right",
"displayName": "Right"
}
],
"dataLabelVerticalPosition": [
{
"value": "above",
"displayName": "Above"
},
{
"value": "under",
"displayName": "Under"
}
]
},
"labels": {
"labelOrientation": [
{
"value": "vertical",
"displayName": "Vertical"
},
{
"value": "horizontal",
"displayName": "Horizontal"
}
],
"labelPosition": [
{
"value": "Auto",
"displayName": "Auto"
},
{
"value": "InsideEnd",
"displayName": "Inside End"
},
{
"value": "OutsideEnd",
"displayName": "Outside End"
},
{
"value": "InsideCenter",
"displayName": "Inside Center"
},
{
"value": "InsideBase",
"displayName": "Inside Base"
}
 }
],
"labelStyle": [
{
"value": "Category",
"displayName": "Category"
},
{
"value": "Data",
"displayName": "Data value"
},
{
"value": "Percent of total",
"displayName": "Percent of total"
},
{
"value": "Both",
"displayName": "Category, data value"
},
{
"value": "Category, percent of total",
"displayName": "Category, percent of total"
},
{
"value": "Data value, percent of total",
"displayName": "Data value, percent of total"
},
{
"value": "Category, data value, percent of total",
"displayName": "All detail labels"
}
]
},
"card": {
"outline": [
{
"value": "None",
"displayName": "None"
},
{
"value": "BottomOnly",
"displayName": "Bottom only"
},
{
"value": "TopOnly",
"displayName": "Top only"
},
{
"value": "LeftOnly",
"displayName": "Left only"
},
{
"value": "RightOnly",
"displayName": "Right only"
},
{
"value": "TopBottom",
"displayName": "Top + bottom"
},
{
"value": "LeftRight",
"displayName": "Left + right"
},
{
"value": "Frame",
"displayName": "Frame"
}
]
},
"imageScaling": {
"imageScaling": {
"imageScalingType": [
{
"value": "Normal",
"displayName": "Normal"
},
{
"value": "Fit",
"displayName": "Fit"
},
{
"value": "Fill",
"displayName": "Fill"
}
]
},
"forecast": {
"confidenceBandStyle": [
{
"value": "fill",
"displayName": "Fill"
},
{
"value": "line",
"displayName": "Line"
},
{
"value": "none",
"displayName": "None"
}
],
"style": [
{
"value": "dashed",
"displayName": "Dashed"
},
{
"value": "solid",
"displayName": "Solid"
},
{
"value": "dotted",
"displayName": "Dotted"
}
]
},
"mapStyles": {
"mapTheme": [
{
"value": "aerial",
"displayName": "Aerial"
},
{
"value": "canvasDark",
"displayName": "Dark"
},
{
"value": "canvasLight",
"displayName": "Light"
},
{
"value": "grayscale",
"displayName": "Grayscale"
},
{
"value": "road",
"displayName": "Road"
}
]
},
},
"shape": {
"projectionEnum": [
{
"value": "albersUsa",
"displayName": "Albers USA"
},
{
"value": "equirectangular",
"displayName": "Equirectangular"
},
{
"value": "mercator",
"displayName": "Mercator"
},
{
"value": "orthographic",
"displayName": "Orthographic"
}
]
},
"xAxisReferenceLine": {
"style": [
{
"value": "dashed",
"displayName": "Dashed"
},
{
"value": "solid",
"displayName": "Solid"
},
{
"value": "dotted",
"displayName": "Dotted"
}
],
"position": [
{
"value": "back",
"displayName": "Behind"
},
{
"value": "front",
"displayName": "In Front"
}
],
"dataLabelText": [
{
"value": "Value",
"displayName": "Value"
},
{
"value": "Name",
"displayName": "Name"
},
{
"value": "ValueAndName",
"displayName": "Name and Value"
}
],
"dataLabelHorizontalPosition": [
{
"value": "left",
"displayName": "Left"
},
{
"value": "right",
"displayName": "Right"
}
],
],
"dataLabelVerticalPosition": [
{
"value": "above",
"displayName": "Above"
},
{
"value": "under",
"displayName": "Under"
}
]
},
"ratioLine": {
"style": [
{
"value": "dashed",
"displayName": "Dashed"
},
{
"value": "solid",
"displayName": "Solid"
},
{
"value": "dotted",
"displayName": "Dotted"
}
]
},
"columnHeaders": {
"outline": [
{
"value": "None",
"displayName": "None"
},
{
"value": "BottomOnly",
"displayName": "Bottom only"
},
{
"value": "TopOnly",
"displayName": "Top only"
},
{
"value": "LeftOnly",
"displayName": "Left only"
},
{
"value": "RightOnly",
"displayName": "Right only"
},
{
"value": "TopBottom",
"displayName": "Top + bottom"
},
{
"value": "LeftRight",
"displayName": "Left + right"
},
{
"value": "Frame",
"displayName": "Frame"
}
]
},
"values": {
"outline": [
{
"value": "None",
"displayName": "None"
},
 },
{
"value": "BottomOnly",
"displayName": "Bottom only"
},
{
"value": "TopOnly",
"displayName": "Top only"
},
{
"value": "LeftOnly",
"displayName": "Left only"
},
{
"value": "RightOnly",
"displayName": "Right only"
},
{
"value": "TopBottom",
"displayName": "Top + bottom"
},
{
"value": "LeftRight",
"displayName": "Left + right"
},
{
"value": "Frame",
"displayName": "Frame"
}
]
},
"total": {
"outline": [
{
"value": "None",
"displayName": "None"
},
{
"value": "BottomOnly",
"displayName": "Bottom only"
},
{
"value": "TopOnly",
"displayName": "Top only"
},
{
"value": "LeftOnly",
"displayName": "Left only"
},
{
"value": "RightOnly",
"displayName": "Right only"
},
{
"value": "TopBottom",
"displayName": "Top + bottom"
},
{
"value": "LeftRight",
"displayName": "Left + right"
},
{
"value": "Frame",
"displayName": "Frame"
}
]
},
"rowHeaders": {
"outline": [
 {
"value": "None",
"displayName": "None"
},
{
"value": "BottomOnly",
"displayName": "Bottom only"
},
{
"value": "TopOnly",
"displayName": "Top only"
},
{
"value": "LeftOnly",
"displayName": "Left only"
},
{
"value": "RightOnly",
"displayName": "Right only"
},
{
"value": "TopBottom",
"displayName": "Top + bottom"
},
{
"value": "LeftRight",
"displayName": "Left + right"
},
{
"value": "Frame",
"displayName": "Frame"
}
]
},
"subTotals": {
"outline": [
{
"value": "None",
"displayName": "None"
},
{
"value": "BottomOnly",
"displayName": "Bottom only"
},
{
"value": "TopOnly",
"displayName": "Top only"
},
{
"value": "LeftOnly",
"displayName": "Left only"
},
{
"value": "RightOnly",
"displayName": "Right only"
},
{
"value": "TopBottom",
"displayName": "Top + bottom"
},
{
"value": "LeftRight",
"displayName": "Left + right"
},
{
"value": "Frame",
"displayName": "Frame"
}
],
"rowSubtotalsPosition": [
{
"value": "Top",
"displayName": "Top"
},
{
"value": "Bottom",
"displayName": "Bottom"
}
]
},
"general": {
"orientation": [
{
"value": "vertical",
"displayName": "Vertical"
},
{
"value": "horizontal",
"displayName": "Horizontal"
}
]
},
"data": {
"relativeRange": [
{
"value": "Last",
"displayName": "Last"
},
{
"value": "Next",
"displayName": "Next"
},
{
"value": "This",
"displayName": "This"
}
],
"relativePeriod": [
{
"value": "None",
"displayName": "Select"
},
{
"value": "Days",
"displayName": "Days"
},
{
"value": "Weeks",
"displayName": "Weeks"
},
{
"value": "Calendar Weeks",
"displayName": "Weeks (Calendar)"
},
{
"value": "Months",
"displayName": "Months"
},
{
"value": "Calendar Months",
"displayName": "Months (Calendar)"
},
{
"value": "Years",
"displayName": "Years"
},
{
"value": "Calendar Years",
 "value": "Calendar Years",
"displayName": "Years (Calendar)"
}
],
"mode": [
{
"value": "Between",
"displayName": "Between"
},
{
"value": "Before",
"displayName": "Before"
},
{
"value": "After",
"displayName": "After"
},
{
"value": "Basic",
"displayName": "List"
},
{
"value": "Dropdown",
"displayName": "Dropdown"
},
{
"value": "Relative",
"displayName": "Relative"
},
{
"value": "Single",
"displayName": "Single Value"
}
]
},
"header": {
"outline": [
{
"value": "None",
"displayName": "None"
},
{
"value": "BottomOnly",
"displayName": "Bottom only"
},
{
"value": "TopOnly",
"displayName": "Top only"
},
{
"value": "LeftOnly",
"displayName": "Left only"
},
{
"value": "RightOnly",
"displayName": "Right only"
},
{
"value": "TopBottom",
"displayName": "Top + bottom"
},
{
"value": "LeftRight",
"displayName": "Left + right"
},
{
"value": "Frame",
"displayName": "Frame"
}
]
 ]
},
"items": {
"outline": [
{
"value": "None",
"displayName": "None"
},
{
"value": "BottomOnly",
"displayName": "Bottom only"
},
{
"value": "TopOnly",
"displayName": "Top only"
},
{
"value": "LeftOnly",
"displayName": "Left only"
},
{
"value": "RightOnly",
"displayName": "Right only"
},
{
"value": "TopBottom",
"displayName": "Top + bottom"
},
{
"value": "LeftRight",
"displayName": "Left + right"
},
{
"value": "Frame",
"displayName": "Frame"
}
]
},
"status": {
"direction": [
{
"value": "Positive",
"displayName": "High is good"
},
{
"value": "Negative",
"displayName": "Low is good"
}
]
}
}
 The new filter experience in Power BI reports
(Preview)
2/14/2019 • 5 minutes to read • Edit Online

This article spells out the new filter experience: Filters in Power BI are getting new functionality and a new design.
When you design reports in Power BI Desktop or in the Power BI service, you can make the Filters pane to look
like and act with the whole report. In the new experience, the old Filters pane acts as a filter editing pane, and the
new Filter pane is the only one your report consumers see.

NOTE
The new filter experience is in preview. New builds may override formatting you've already set.

As a report designer, here's what you can do with the new filters:
Show a read-only view of filters in the visual header, so consumers know exactly what filters or slicers are
affecting a given visual.
Format and customize the filter pane so that it feels part of your report.
Define whether the Filters pane is open or collapsed by default when a consumer opens the report.
Hide the entire filter pane or specific filters that you don’t want report consumers to see.
Control and even bookmark the visibility, open, and collapsed state of the new filter pane.
Lock filters that you don’t want consumers to edit.

Turn on the new filter experience

You enable the new experience in Power BI Desktop. Then you can modify filters there or in the Power BI service
(https://app.powerbi.com). Because this new filter experience is in Preview, you must first enable it in Power BI
Desktop. If you start by creating a report in the Power BI service, it can't have the new filters.
Turn on new filters for all new reports
1. In Power BI Desktop, select File > Options and Settings > Options > Preview Features, then select the
New filter experience checkbox.
2. Restart Power BI Desktop to see the new filter experience in all new reports.
After you restart Power BI Desktop, it's enabled by default for all new reports you create.
Turn on new filters for an existing report
You can also enable the new filters for existing reports.
1. In Power BI Desktop in an existing report, select File > Options and Settings > Options
2. Under Report settings, select Enable the updated filter pane, and show filters in the visual header for
this report.

Build the new filter pane

After you enable the new filter pane, you see it to the right of the report page, formatted by default based on your
current report settings. The old filter pane now acts as the filter editing pane. The new filter pane shows you what
your report consumers will see when you publish your report. You can update existing filters in the new pane, but
you use the older filter pane to configure which filters to include.
1. First decide if you want your report consumers to see the filter pane. If you want them to see it, select the
eye icon next to Filters.
2. To start building your new filter pane, drag fields of interest into the filter editing pane either as visual, page,
or report level filters. You see them in the new Filters pane.

When you add a visual to a report canvas, Power BI automatically adds a filter for each field in the visual. Power BI
doesn't add those automatic filters to the read-only filter pane. You have to select the eye icon to add them
explicitly.
Lock or hide filters
You can lock or hide individual filter cards. If you lock a filter, your report consumers can see but not change it. If
you hide it, they can't even see it. Hiding filter cards is typically useful if you need to hide data cleanup filters that
exclude nulls or unexpected values.
In the filter editing pane, select or clear the Lock filter or Hide filter icons in a filter card.

As you turn these settings on and off in the filter editing pane, you see the changes reflected in the new filter pane.
Hidden filters don't show up in the filter pop-up for a visual.
You can also configure your filter pane state to flow with your report bookmarks. The pane’s open, close, and
visibility state are all bookmarkable.

Format the new Filters pane

A big part of this new experience is that you can now format the filter pane to match the look and feel of your
report. You can format the filter pane differently for each page in the report. Here are elements you can format:
Background color
Background transparency
Filter pane border on or off
Filter pane border color
Filter pane title and header font, color, and text size
You can also format these elements for filter cards, depending on if they're applied (set to something) or available
(cleared):
Background color
Background transparency
Border: on or off
Border color
Font, color, and text size
Input box color
Set the format for the Filters pane and cards
1. In the report, click the report itself, or the background ( wallpaper), then in the Visualizations pane, select
Format. You see options for formatting the report page, the wallpaper, and also the Filter pane and Filter
cards.

2. Expand Filter pane to set color for the background, icon, and left border, to complement the report page.
3. Expand Filter cards to set the Available and Applied color and border. If you make available and applied
cards different colors, it's obvious which filters are applied.
View filters for a visual in Reading mode
In Reading mode, hover over the filter icon for a visual to see a pop-up with all the filters, slicers, and so on,
affecting that visual. The formatting of the pop-up is the same as the filter pane formatting.

Here are the types of filters this view shows:

Basic filters
Slicers
Cross-highlighting
 Cross-filtering
Advanced filters
Top N filters
Relative Date filters
Sync-slicers
Include/Exclude filters
Filters passed through a URL

Coming soon
In coming months we plan to incorporate the following improvements:
Ability to change the order of filter cards
Single filter pane experience for report creators
More formatting options
Give the new filter experience a try. Provide us your feedback for this feature and how we can continue to improve
this experience.

Next steps
How to use report filters
Filters and highlighting in reports
Interact with filters and highlighting in report Reading View
Change how report visuals cross-filter and cross-highlight each other
More questions? Try the Power BI Community
 Use Quick measures to easily perform common and
powerful calculations
1/14/2019 • 7 minutes to read • Edit Online

You can use Quick measures to quickly and easily perform common, powerful calculations. A Quick measure
runs a set of DAX commands behind the scenes (you don’t have to write the DAX – it’s done for you) based on
input you provide in a dialog box, then presents the results for you to use in your report. Best of all, you can see
the DAX that’s executed by the Quick measure and jump-start or expand your own DAX knowledge.

You create Quick measures by right-clicking a field in the Fields well, then selecting Quick measures from the
menu that appears. You can also right-click any value in the Values pane of an existing visual (such as the Values
field in a Bar chart visual). There are many available categories of calculations and ways to modify each
calculation to fit your needs.
Quick measures now generally available
Beginning with the February 2018 release of Power BI Desktop, quick measures are generally available (no
longer in preview ). If you're using a previous release of Power BI Desktop, you can try Quick measures feature
beginning with the April 2017 release of Power BI Desktop by selecting File > Options and Settings >
Options > Preview Features, then select the checkbox beside Quick measures.
You'll need to restart Power BI Desktop after you make the selection.

Using Quick measures

To create a Quick measure, right-click on a field (any field) in the Fields well in Power BI Desktop and select
Quick measure from the menu that appears.
When using SQL Server Analysis Services (SSAS ) live connections, some Quick measures are available. Power
BI Desktop displays only the collection of Quick measures that are supported for the version of SSAS to which
the connection is made. So, if you are connected to a SSAS live data source, and you do not see certain Quick
measures in the list, it's because the SSAS version to which you are connected does not support the DAX
measure used to implement that Quick measure.
When selected from the right-click menu, the following Quick measures window appears, allowing you to select
the calculation you want and the fields against which you want the calculation to be run.
When you select the drop-down menu, you're presented with the long list of available Quick measures.
There are five distinct groups of Quick measure calculation types, each with a collection of calculations. Those
groups and calculations are the following:
Aggregate per category
Average per category
Variance per category
Max per category
Min per category
Weighted average per category
Filters
Filtered value
Difference from filtered value
Percentage difference from filtered value
Sales from new categories
Time intelligence
Year-to-date total
Quarter-to-date total
Month-to-date total
Year-over-year change
Quarter-over-quarter change
 Month-over-month change
Rolling average
Totals
Running total
Total for category (filters applied)
Total for category (filters not applied)
Mathematical operations
Addition
Subtraction
Multiplication
Division
Percentage difference
Correlation coefficient
Text
Star rating
Concatenated list of values
We anticipate adding to these calculations, want to hear from you about which Quick measures you'd like to see,
and if you have ideas (including underlying DAX formulas) for Quick measures that you'd like to submit for
consideration. More on that at the end of this article.

Example of Quick measures

Let's take a look at an example of these Quick measures in action.
The following Matrix visual shows a table of sales for various electronics products. It's a basic table that includes
the total for each category.

When we right-click the Values field well and select Quick measures, we can select Average per category as the
Calculation, then select Sum of SalesAmount as the Base value, then specify SalesAmount by dragging that field
from the Fields box on the right pane, into the Category section on the left.

When we select OK, we see a few interesting things occur, as shown in the image following this list:
1. The Matrix visual now has a new column that shows our calculation (in this case, Average SalesAmount
within SalesAmount).
2. A new measure has been created and is available in the Fields well, and it's highlighted (Power BI puts a
yellow box is around it). This measure is available to any other visual in the report, not just the visual for which
it was originally created.
3. The DAX formula that was created for the Quick measure is displayed in the Formula bar.

To start with the first item, notice that the Quick measure was applied to the visual. There's a new column and
associated value, both of which are based on the Quick measure that was created.
Second, the Quick measure shows up in the Fields well of the data model, and can be used like any other field in
the model, for any other visual. In the following image, a quick bar chart visual was created by using the new field
created by the Quick measure.

Let's head to the next section to discuss that third item, DAX formulas.

Learn DAX using Quick measures

Another great advantage of the Quick measures feature is that it directly shows you the DAX formula that was
created to implement the measure. In the following image, we've selected the measure that was created by the
Quick measure (it's now in the Fields well, so we just have to click it). When we do so, the Formula bar appears,
showing the DAX formula that Power BI created to implement the measure.
This is nice by itself, since it shows you the formula behind the measure. But, more importantly, perhaps, it lets
you use Quick measures to see how the underlying DAX formulas should be created.
Imagine you need to do a year-over-year calculation, but you're not quite sure how to structure the DAX formula
(or, you have no idea where to start!). Instead of banging your head on the desk, you could create a Quick
measure using the Year over year change calculation and see what happens. As in, create the Quick measure
and see how it appears in your visual, see how the DAX formula worked, then make changes either directly to the
DAX, or create another measure until the calculations meet your needs or expectations.
It's like having a quick teacher that immediately responds to your what-if questions by a few clicks. You can
always delete those measures from your model if you don't like them - that's as easy as right-clicking the measure
and selecting delete.

And, once you do have the measure perfected, you can rename it however you'd like, using the same right-click
menu.

Limitations and considerations

There are a few limitations and considerations to keep in mind.
Quick measures are only available if you can modify the model, which isn't the case when you're working
with some Live connections (SSAS tabular live connections are supported, as previously explained).
The measure that's added to the Fields well can be used with any visual in the report.
You can always see the DAX associated with a Quick measure by selecting the created measure in the Fields
well, then looking at the formula in the Formula bar.
You can't create time intelligence quick measures when working in DirectQuery mode. The DAX functions used
in these quick measures have performance implications when translated into the T-SQL statements that get
sent to your data source.

WARNING
Quick measures currently only generate DAX statements with commas for argument separators. If your version of Power
BI Desktop is localized to a language that uses commas as decimal separators, quick measures will not operate properly.

Time intelligence and Quick measures

Beginning with the October 2017 update to Power BI Desktop, you can use your own custom date tables with
time intelligence Quick measures. If you're using an external tabular model then ensure that when the model
was built, that primary date column in that table was marked as a Date table, as described in this article. If you're
importing your own date table then make sure to mark it as a date table, as described in this article
Additional information and examples
We anticipate providing examples and guidance for each of the Quick measures calculations, so please check
back soon for updates on that focused article.
Have an idea for a Quick measure that isn't already provided? Great! Check out this page and submit your ideas
(and DAX formula) for the Quick measure you'd like to see in Power BI Desktop, and we'll consider adding it to
the provided list of Quick measures in a future release.
 Create and use a What if parameter to visualize
variables in Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

Starting with the August 2018 release of Power BI Desktop, you can create What if variables for your reports,
interact with the variable as a slicer, and visualize and quantify different key values in your reports.

The What if parameter is on the Modeling tab in Power BI Desktop. When you select it, a dialog appears where
you can configure the parameter.

Creating a What if parameter

To create a What if parameter, select the What if button from the Modeling tab in Power BI Desktop. In the
following image, we've created a parameter called Discount percentage and set its data type to Decimal number.
The Minimum value is zero, the Maximum is 0.50 (fifty percent). We've also set the Increment to 0.05, or five
percent. That's how much the parameter will adjust when interacted with in a report.
 NOTE
For decimal numbers, make sure you precede it with a zero, as in 0.50 versus just .50. Otherwise, the number won't validate
and the OK button will not be selectable.

For your convenience, the Add slicer to this page checkbox automatically puts a slicer with your What if
parameter onto the current report page.

In addition to creating the parameter, creating a What if parameter also creates a measure, which you can use to
visualize the current value of the What if parameter.
It's important and useful to note that once you create a What if parameter, both the parameter and the measure
become part of your model. So, they're available throughout the report and can be used on other report pages.
And, since they're part of the model, you can delete the slicer from the report page, or if you want it back, just grab
the What if parameter from the Fields list and drag it onto the canvas (then change the visual to a slicer) to easily
get the parameter back into your report.

Using a What if parameter

Let's create a simple example of using a What if parameter. We created the What if parameter in the previous
section, now we'll put it to use by creating a new measure whose value adjusts with the slider. To accomplish this,
we create a new measure.
The new measure is simply going to be the total sales amount, with the discount rate applied. You can create
complex and interesting measures, of course, that let the consumers of your reports visualize the variable of your
What if parameter. For example, you could create a report that let sales people see their compensation if they meet
certain sales goals or percentages, or see the affect of increased sales to deeper discounts.
Once we type the measure formula into the formula bar, and name it Sales after Discount, we see its result:

Then, we create a column visual with OrderDate on the axis, and both SalesAmount and the just-created measure,
Sales after Discount as the values.

Then, as we move the slider, we see that the Sales after Discount column reflects the discounted sales amount.
And, that's all there is to it. You can use What if parameters in all sorts of situations, to enable the consumers of
reports to interact with different scenarios that you create in your reports.
 Use drillthrough in Power BI Desktop
1/14/2019 • 3 minutes to read • Edit Online

With drillthrough in Power BI Desktop, you can create a page in your report that focuses on a specific entity
such as a supplier, customer, or manufacturer. Users can right-click on a data point in other report pages. Then
they can drill through to the focused page to get details that are filtered to that context.

Using drillthrough
1. To use drillthrough, create a report page that has the visuals you want for the type of entity that you're
going to provide drillthrough for.
For example, let's say you want to provide drillthrough for manufacturers. Then you might create a
drillthrough page with visuals that show total sales, total units shipped, sales by category, sales by region,
and so on. That way, when you drill through to that page, the visuals will be specific to the manufacturer
you selected.
2. Then, on that drillthrough page, in the Fields section of the Visualizations pane, drag the field for which
you want to enable drillthrough into the Drillthrough filters well.

When you add a field to the Drillthrough filters well, Power BI Desktop automatically creates a back
button visual. That visual becomes a button in published reports. Users who are consuming your report in
the Power BI service can use this button to get back to the report page from which they came.

Use your own image for a back button

Because the back button is an image, you can replace the image of that visual with any image you want. It will still
operate as a back button so that report consumers can go back to their original page. To use your own image for a
back button, take the following steps:
1. On the Home tab, select Image. Then locate your image, and place it on the drillthrough page.
2. Select your new image on the drillthrough page. Under the Format Image section, set the Link slider to
On, and then set the Type to Back. Your image now functions as a back button.
 Now users can right-click a data point in your report and get a context menu that supports drillthrough to
that page.

When report consumers choose to drill through, the page is filtered to show information about the data
point on which they right-clicked. For example, lets say they right-clicked on a data point about Contoso (a
manufacturer), and selected to drill through. The drillthrough page they go to is filtered to Contoso.

Pass all filters in drillthrough

Beginning with the May 2018 version of Power BI Desktop, you can pass all applied filters to the drillthrough
window. For example, you can select only a certain category of products and the visuals filtered to that category,
and then select drillthrough. You might be interested in what that drillthrough would look like with all those filters
applied.
To keep all applied filters, in the Drillthrough section of the Visualizations pane, set the Pass all filters toggle to
on.
In versions of Power BI Desktop that were released before May 2018, the behavior is the same as having this
toggle set to off.
When you then drill through on a visual, you can see which filters were applied as a result of the source visual
having temporary filters applied. In the drillthrough window, those transient filters are shown in italics.
You could do this with tooltips pages, but that would be an odd experience because the tooltip wouldn't appear to
be working properly. For this reason, so doing so with tooltips isn't recommended.

Add a measure to drillthrough

Besides passing all filters to the drillthrough window, you can also add a measure or a summarized numeric
column to the drillthrough area. Drag the drillthrough field to the drillthrough card to apply it.

When you add a measure or summarized numeric column, you can drill through to the page when the field is
used in the Value area of a visual.
That's all there is to using drillthrough in your reports. It's a great way to get an expanded view of the entity
information that you selected for your drillthrough filter.

Next steps
You might also be interested in the following articles:
Using slicers Power BI Desktop
 Use a relative date slicer and filter in Power BI
Desktop
1/14/2019 • 2 minutes to read • Edit Online

With the relative date slicer or relative date filter, you can apply time-based filters to any date column in your
data model. For example, you can use the relative date slicer to show only sales data that's happened within the
last thirty days (or month, calendar months, and so on). And, when you refresh the data, the relative time period
automatically applies the appropriate relative date constraint.

Using the relative date range slicer

You can use the relative date slicer just like any other slicer. Simply create a slicer visual for your report and then
select a date value for the Field value. In the following image, the OrderDate field is selected.
Select the carat in the upper-right corner of the relative date slicer and a menu appears.

For the relative date slicer, select Relative.

You can then select the settings. For the first drop-down in the relative date slicer, you have the following choices:
Last
Next
This
These selections are shown in the following image.
The next (middle) setting in the relative date slicer lets you type in a number to define the relative date range.
The third setting lets you pick the date measurement. You have the following choices:
Days
Weeks
Weeks (Calendar)
Months
Months (Calendar)
Years
Years (Calendar)
These selections are shown in the following image.

If you select Months from that list, and input 2 in the middle setting, the following would happen: if today is July
20th, the data included in visuals constrained by the slicer would show data for the previous two months, starting
on May 20th and going through July 20th (today's date).
In comparison, if you selected Months (Calendar ), the visuals constrained would show data from May 1st through
June 30th (the last two complete calendar months).
Using the relative date range filter
You can also create a relative date range filter for your report page or your entire report. To do so, simply drag a
date field into the Page level filters or the Report level filters areas in the Field pane, as shown in the following
image.

Once there, you can modify the relative date range in a similar fashion to how the relative date slicer is
customized. Select Relative date filtering from the Filter Type drop-down.

Once Relative date filtering is selected, you see three sections to modify, including a middle numeric box, just like
the slicer.

And, that's all there is to using these relative date constraints in your reports.

Limitations and considerations

The following limitations and considerations currently apply to the relative date range slicer and filter.
Data models in Power BI do not include time zone information. The models can store times, but there's no
indication of the time zone they're in.
The slicer and filter are always based on the time in UTC, so if you configure a filter in a report and send it to a
colleague in a different time zone, you'll both see the same data. However, if you aren't in the UTC time zone,
you might see data for a different time offset than you expect.
Data captured in a local time zone can be converted to UTC using the Query Editor.
 Use grouping and binning in Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

When Power BI Desktop creates visuals, it aggregates your data into chunks (or groups) based on values found
in the underlying data. Often that's fine, but there may be times when you want to refine how those chunks are
presented. For example, you might want to place three categories of products in one larger category (one group).
Or, you might want to see sales figures put into bin-sizes of 1,000,000 dollars, instead of evenly-divided, 923,983
dollars.
In Power BI Desktop, you can Group data points to help you more clearly view, analyze, and explore data and
trends in your visuals. You can also define the Bin size, often called binning, to put values into equally sized groups
that better enable you to visualized data in ways that are meaningful.

Using grouping
To use grouping, select two or more elements on a visual by using Ctrl+click to multi-select elements. Then, right-
click one of the multi-select elements and select Group from the menu that appears.

Once created, the group is added to the Legend bucket for the visual and it also appears in the Fields list.
Once you have a group, you can easily edit the members of that group by right-clicking the field from the Legend
bucket, or from the Fields list, and selecting Edit Groups.

In the Groups window that appears, you can create new groups or modify existing groups. You can also rename
any group by double-clicking on the group title in the Groups and members box and typing a new name.
There are all sorts of things you can do with groups. You can add items from the Ungrouped values list into a
new group or into one of the existing groups. To create a new group, select two or more items (using Ctrl+click)
from the Ungrouped values box, and then click the Group button below that box.
You can add an ungrouped value into an existing group: just select the Ungrouped value, then select the existing
group to which you want to add it, and click the Group button. To remove an item from a group, select it from the
Groups and members box and then click Ungroup. You can also select whether ungrouped categories should be
placed into the Other group, or should remain ungrouped.

NOTE
You can create groups for any field in the Fields well, without having to multi-select from an existing visual. Just right-click
the field, and select New Group from the menu that appears.

Using binning
You can set the bin size for numerical and time fields in Power BI Desktop. You can use binning to right-size the
data that Power BI Desktop displays.
To apply a bin size, right-click a Field and select New Group.
From the Groups window, set the Bin size to the size you want.
When you select OK, you'll notice that a new field appears in the Fields pane with (bins) appended. You can then
drag that field onto the canvas to use the bin size in a visual.

To see binning in action, take a look at this video.

And that's all there is to using grouping and binning to ensure the visuals in your reports show your data just the
way you want them to.
 Create Power BI visuals using R
1/14/2019 • 6 minutes to read • Edit Online

With Power BI Desktop, you can use R to visualize your data.

Install R
Power BI Desktop does not include, deploy, or install the R engine. To run R scripts in Power BI Desktop, you
must separately install R on your local computer. You can download and install R for free from many locations,
including the Revolution Open download page, and the CRAN Repository. The current release of R scripting in
Power BI Desktop supports Unicode characters as well as spaces (empty characters) in the installation path.

Enable R visuals
To enable R visuals, select File > Options and settings > Options and in the Options page that appears, make
sure your local R installation is specified in the R Scripting section of the Options window, as shown in the
following image. In the following image, the path local installation of R is C:\Program Files\R\R-3.2.0 and that
path is explicitly provided in the text box. Make sure the path it displays properly reflects the local R installation
you want Power BI Desktop to use.

Once you specify your R installation, you’re ready to begin creating R visuals.
Create R visuals in Power BI Desktop
1. Select the R Visual icon in the Visualization pane, as shown in the following image, to add an R visual.

When you add an R visual to a report, Power BI Desktop does the following:
A placeholder R visual image appears on the report canvas.
The R script editor appears along the bottom of the center pane.

2. Next, add fields you want to consume in your R script to the Values section in the Fields well, just as you
would with any other Power BI Desktop visual.
Only fields that have been added to the Fields well are available to your R script. You can add new fields or
remove unneeded fields from the Fields well while working on your R script in the Power BI Desktop R
script editor. Power BI Desktop automatically detects which fields you have added or removed.

NOTE
The default aggregation type for R visuals is do not summarize.

3. Now you can use the data you selected to create a plot.
As you select fields, the R script editor generates supporting R script binding code based on your
selections in the gray section along the top of the editor pane. As you select or remove additional fields,
supporting code in the R script editor is automatically generated or removed accordingly.
In the example shown in the following image, three fields were selected: hp, gear, and drat. As a result of
 those selections, the R script editor generated the following binding code:
A dataframe called dataset was created
That dataframe is comprised of the different fields selected by the user
The default aggregation is do not summarize
Similar to table visuals, fields are grouped and duplicate rows only appear once

TIP
In certain cases, you may not want automatic grouping to occur, or you may want all rows to appear, including
duplicates. In that case, you can add an index field to your dataset that causes all rows to be considered unique and
which prevents grouping.

The generated dataframe is called a dataset, and you can access selected columns by their respective
names. For example, access the gear field by writing dataset$gear in your R script. For fields with spaces or
special characters, use single quotes.
4. With the dataframe automatically generated by the fields you selected, you’re ready to write a R script that
results in plotting to the R default device. When the script is complete, select Run from the R script editor
title bar (Run is on the right side of the title bar).
When you select Run, Power BI Desktop identifies the plot and presents it on the canvas. Since the
process is executed on your local R installation, make sure the required packages are installed.
Power BI Desktop replots the visual when any of the following events occur:
When you select Run from the R script editor title bar
Whenever a data change occurs, due to data refresh, filtering, or highlighting
The following image shows an example of the correlation plot code, and it plots the correlations
between attributes of different types of cars.
5. To get a larger view of the visualizations, you can minimize the R script editor. And, of course, like other
visuals in Power BI Desktop, you can cross filter the correlation plot by selecting only sport cars in the
donut visual (the round visual on the right, in the above example image).

6. You can also modify the R script to customize the visual, and take advantage of the power of R by adding
parameters to the plotting command.
The original plotting command was the following:
corrplot(M, method = "color", tl.cex=0.6, tl.srt = 45, tl.col = "black")
With a few changes in the R script, the command is now the following:
corrplot(M, method = "circle", tl.cex=0.6, tl.srt = 45, tl.col = "black", type= "upper", order="hclust")
As a result, the R visual now plots circles, only considers at the upper half, and reorders the matrix to
cluster correlated attributes, as shown in the following image.
 When executing a R script that results in an error, the R visual is not plotted and an error message is
displayed on the canvas. For details on the error, select See details from the R visual error on the canvas.

R scripts security: R visuals are created from R scripts, which could contain code with security or
privacy risks. When attempting to view or interact with an R visual for the first time, a user is presented
with a security warning message. Only enable R visuals if you trust the author and source, or after you
review and understand the R script.

Known limitations
R visuals in Power BI Desktop has a few limitations:
Data size limitations – data used by the R visual for plotting is limited to 150,000 rows. If more than 150,000
rows are selected, only the top 150,000 rows are used and a message is displayed on the image.
Calculation time limitation – if an R visual calculation exceeds five minutes the execution times out, resulting in
an error.
Relationships – as with other Power BI Desktop visuals, if data fields from different tables with no defined
relationship between them are selected, an error occurs.
R visuals are refreshed upon data updates, filtering, and highlighting. However, the image itself is not
interactive and cannot be the source of cross-filtering.
R visuals respond to highlighting other visuals, but you cannot click on elements in the R visual in order to
cross filter other elements.
Only plots that are plotted to the R default display device are displayed correctly on the canvas. Avoid explicitly
using a different R display device.
 In this release, RRO installations are not automatically identified by the 32-bit version of Power BI Desktop, so
you must manually provide the path to the R installation directory in Options and settings > Options > R
Scripting.

Next steps
Take a look at the following additional information about R in Power BI.
Running R Scripts in Power BI Desktop
Use an external R IDE with Power BI
 Use R-powered custom visuals in Power BI
3/8/2019 • 5 minutes to read • Edit Online

In Power BI Desktop and the Power BI service, you can use R -powered custom visuals without any knowledge
of R and without any R scripting. This enables you to harness the analytic and visual power of R visuals, and R
scripts, without learning R or doing any programming yourself.
To use R -powered custom visuals, you first select and download the R custom visual you're interested in using from
the AppSource gallery of custom visuals for Power BI.

The following sections describe how to select, load, and use R -powered visuals in Power BI Desktop.

Use R custom visuals

To use R -powered custom visuals, download each visual from the custom visuals library, then use the visual like
any other type of visual in Power BI Desktop. There are two ways to get custom visuals: you can download them
from the online AppSource site, or browse and get them from within Power BI Desktop.
Get custom visuals from AppSource
Following are the steps to browse and select visuals from the online AppSource site:
1. Navigate to the Power BI visuals library, found at https://appsource.microsoft.com. Select the Power BI apps
checkbox under Refine by product, then select the See all link.
2. On the Power BI visuals library page, select Power BI visuals from the list of Add-ins in the left pane.

3. Select the visual you're interested in using from the gallery, and you're taken to a page that describes the
visual. Select the Get it now button to download.

NOTE
For authoring in Power BI Desktop, you need to have R installed on your local machine. But, when users want to
view an R-powered visual in the Power BI service they do not need R installed locally.
 You do not need to install R to use R -powered custom visuals in the Power BI service, however, if you want
to use R -powered custom visuals in Power BI Desktop you must install R on the local machine. You can
download R from the following locations:
CRAN
MRO
4. Once the visual is downloaded (which is like downloading any file from your browser), go to Power BI
Desktop and click the ellipsis (...) in the Visualizations pane, and select Import from file.

5. You're warned about importing a custom visual, as shown in the following image:
6. Navigate to where the visual file was saved, then select the file. Power BI Desktop custom visualizations
have the .pbiviz extension.

7. When you return to Power BI Desktop, you can see the new visual type in the Visualizations pane.

8. When you import the new visual (or open a report that contains an R -powered custom visual), Power BI
Desktop installs the required R packages.
9. From there, you can add data to the visual just as you would any other Power BI Desktop visual. When
complete, you can see your finished visual on the canvas. In the following visual, the Forecasting R -
powered visual was used with United Nations (UN ) birth rate projections (the visual on the left).

Like any other Power BI Desktop visual, you can publish this report with its R -powered visuals to the
Power BI service and share it with others.
Check the library often, since new visuals are being added all the time.
Get custom visuals from within Power BI Desktop
1. You can also get custom visuals from within Power BI Desktop. In Power BI Desktop click the ellipsis (the
...) in the Visualizations pane, and select Import from marketplace.
2. When you do so, the Power BI Visuals dialog appears, where you can scroll through the available custom
visuals and select what you would like. You can search by name, select a category, or just scroll through the
available visuals. When you're ready, just select Add to add the custom visual to Power BI Desktop.

Contribute R-powered custom visuals

If you create your own R visuals for use in your reports, you can share those visuals with the world by contributing
your custom visual to the custom visuals gallery. Contributions are made through GitHub, and the process is
outlined in the following location:
Contributing to the R -powered custom visuals gallery

Troubleshoot R-powered custom visuals

R -powered custom visuals have certain dependencies that must be met for the visuals to work properly. When R -
powered custom visuals don't run or load properly, the problem is usually one of the following:
The R engine is missing
Errors in the R script on which the visual is based
R packages are missing or out of date
The following section describes troubleshooting steps you can take to help address trouble you might run into.
Missing or outdated R packages
When attempting to install an R -powered custom visual, you can run into errors when there are missing or
outdated R packages; this is due to one of the following reasons:
The R installation is incompatible with the R package
The firewall, anti-virus software, or proxy settings are preventing R from connecting to the Internet
The Internet connection is slow or there's an Internet connection problem
The Power BI team is actively working on mitigating these issues before they reach you and the next Power BI
Desktop will incorporate updates to address these problems. Until then, you can take one or more of the following
steps to mitigate the issues:
1. Remove the custom visual, then install it again. This initiates a reinstallation of the R packages.
2. If your installation of R is not current, upgrade your R installation, then remove and reinstall the custom
visual as described in the previous step.
Supported R versions are listed in the description of each R -powered custom visual, as shown in the
following image.
 NOTE
You can keep the original R installation and only associate Power BI Desktop with the current version you install. Go
to File > Options and settings > Options > R scripting.

3. Install R packages manually, using any R console. The steps for this approach follow:
a. Download the R -powered visual installation script and save that file to a local drive.
b. From the R console, run the following:

source(“C:/Users/david/Downloads/ScriptInstallPackagesForForecastWithWorkarounds.R”)

Typical default installation locations are the following:

c:\Program Files\R\R-3.3.x\bin\x64\Rterm.exe (for CRAN-R)

c:\Program Files\R\R-3.3.x\bin\x64\Rgui.exe (for CRAN-R)
c:\Program Files\R\R-3.3.x\bin\R.exe (for CRAN-R)
c:\Program Files\Microsoft\MRO-3.3.x\bin\R.exe (for MRO)
c:\Program Files\Microsoft\MRO-3.3.x\bin\x64\Rgui.exe (for MRO)
c:\Program Files\RStudio\bin\rstudio.exe (for RStudio)

4. If the previous steps don't work, try the following:

a. Use R Studio and follow the step outlined in 3.b. above (run the script line from the R console).
b. If the previous step doesn't work, change Tools > Global Options > Packages in R Studio, and enable
the checkbox for Use Internet Explorer library/proxy for HTTP, then repeat step 3.b. from the above
steps.

Next steps
Take a look at the following additional information about R in Power BI.
Power BI custom visuals gallery
Running R Scripts in Power BI Desktop
Create R visuals in Power BI Desktop
Use an external R IDE with Power BI
 Use gridlines and snap-to-grid in Power BI Desktop
reports
1/14/2019 • 3 minutes to read • Edit Online

The Power BI Desktop report canvas provides gridlines that let you neatly align visuals on a report page and use
snap-to-grid functionality so the visuals in your report look clean, aligned, and evenly spaced.
In Power BI Desktop, you can also adjust the z-order (bring forward, send backward) of objects on a report and
align or evenly distribute selected visuals on the canvas.

Enabling gridlines and snap-to-grid

To enable gridlines and snap-to-grid, select the View ribbon, then enable the checkboxes for Show gridlines and
Snap objects to grid. You can select one or both options; they operate independently.
 NOTE
If Show gridlines and Snap objects to grid are disabled, connect to any data source and they become enabled.

Using gridlines
Gridlines are visible guides that help you align your visuals. When you're trying to determine whether two (or
more) visuals are aligned horizontally or vertically, use the gridlines to determine whether their borders align.
Use Ctrl+Click to select more than one visual at a time, which displays all selected visuals' borders and shows
whether the visuals are properly aligned.
Using gridlines inside visuals
In Power BI there are also gridlines inside visuals that provide visible guides for comparing data points and values.
Beginning with the September 2017 release of Power BI Desktop, you can now manage the gridlines within
visuals using the X-Axis or Y -Axis card (as appropriate based on visual type), found in the Format section of the
Visualizations pane. You can manage the following elements of gridlines within a visual:
Turn gridlines on or off
Change the color of gridlines
Adjust the stroke (the width) of gridlines
Select the line style of the gridlines in the visual, such as solid, dashed, or dotted
Modifying certain elements of gridlines can be especially useful in reports where dark backgrounds are used for
visuals. The following image shows the Gridlines section in the Y -Axis card.
Using snap-to-grid
When you enable Snap objects to grid, all visuals on the Power BI Desktop canvas that you move (or resize)
are automatically aligned to the nearest grid axis, making it much easier to ensure two or more visuals align to the
same horizontal or vertical location or size.

And, that's all there is to using gridlines and snap-to-grid to ensure the visuals in your reports are neatly aligned.
Using z-order, align, and distribute
You can manage the front-to-back order of visuals in a report, often referred to as the z-order of elements. This
feature lets you overlap visuals in any way you want, then adjust the front-to-back order of each. You set the order
of your visuals using the Bring Forward and Send Backward buttons, found in the Arrange section of Format
ribbon. The Format ribbon appears as soon as you select one or more visuals on the page.

The Format ribbon lets you align your visuals in many different ways, which ensures your visuals appear on the
page in the alignment that looks and works best.

The Align button aligns a selected visual to the edge (or center) of the report canvas, as shown in the following
image.
When two or more visuals are selected, they are aligned together and use the existing aligned boundary of the
visuals for their alignment. For example, if you select two visuals and choose the Align Left option, the visuals
then align to the left-most boundary of all selected visuals.

You can also distribute your visuals evenly across the report canvas, either vertically or horizontally. Just use the
Distribute button from the Format ribbon.
With a few selections from these gridlines, alignment, and distribution tools, your reports will look just how you
want them to.
 Page display settings in a Power BI report
1/14/2019 • 2 minutes to read • Edit Online

We understand it is critical to keep your report layout pixel perfect. Sometimes, it can be challenging, because you
and your colleagues view those reports on screens with different aspect ratios and sizes.
The default display view is Fit to page and the default display size is 16:9. If you want to lock in a different aspect
ratio, or want to fit your report in a different way, there are two tools to help you: Page View settings and Page
Size settings.
https://www.youtube.com/embed/5tg-OXzxe2g

Where to find Page view settings in Power BI service and Power BI

Desktop
Page view settings are available in both Power BI service and Power BI Desktop but the interface is a little different.
The two sections below explain where you can find View settings in each Power BI tool.
In Power BI Desktop
In Report view, select the View tab to open Page view settings as well as phone layout settings.

In Power BI service (app.powerbi.com)

In Power BI service, open a report and select View from the upper left menubar.

Page View settings are available in both Reading view and Editing view. In Editing View, a report owner can assign
page view settings to individual report pages, and those settings are saved with the report. When colleagues open
that report in Reading view, they see the report pages display using the owner's settings. In Reading view
colleagues can change some of the Page view settings, but the changes are not saved when they exit the report.

Page view settings

The first set of Page view settings control the display of your report page relative to the browser window. Choose
between:
Fit to Page (default): contents are scaled to best fit the page
Fit to Width: contents are scaled to fit within the width of the page
Actual Size: contents are displayed at full size
The second set of Page view settings control the positioning of objects on the report canvas
Show gridlines: turn on gridlines to help you position objects on the report canvas
Snap to grid: use with Show gridlines to precisely position and align objects on the report canvas
Lock objects: lock all objects on the canvas so that they cannot be moved or resized
Selection pane: the Selection pane lists all objects on the canvas and you can decide which to show and
which to hide

Page Size settings

Page Size settings are only available for report owners. In Power BI service (app.powerbi.com), this means being
able to open the report in Editing view. These settings control the display ratio and actual size (in pixels) of the
report canvas.
4:3 ratio
16:9 ratio (default)
Cortana
Letter
 Custom (height and width in pixels)

Next Steps
Learn how to use Page view and Page size settings in your own Power BI reports.
Read more about reports in Power B
Power BI - Basic Concepts
More questions? Try the Power BI Community
 Add a column from an example in Power BI Desktop
1/14/2019 • 5 minutes to read • Edit Online

Starting with the April 2017 release of Power BI Desktop, you can add new columns of data to your model using
Query Editor by simply providing one or more sample values for your new column. You can create a new column
example from a current selection or provide input based on all (or selected) columns in a given table.

This approach helps you quickly and easily create new columns and is great for the following situations:
You know the data result you want in your new column, but you're not sure which transformation (or collection
of transformations) will get you there.
You already know which transformations you need, but you're not sure where to click or select in the UI to
make them happen.
You know all about the transformations you need using a Custom Column expression in M, but one (or more)
of those expressions aren't available to click or add in the UI.
Using the add column from example feature is easy and straightforward. In the next few sections, we see just
how easy it is.

Use Query Editor to add a new column from examples

To create a new column from an example, launch Query Editor. You can do this by selecting Edit Queries from
the Home ribbon in Power BI Desktop.
To get data from a web page, go to the Home tab, click Get Data > Web, then paste the URL into the dialog that
appears. This article uses data from a Wikipedia article. You can click the following link to get the data for yourself
and follow along:
List of states and territories of the United States
Once Query Editor is launched and you have some data loaded, you can get started adding a column from
examples. To add a new column, in Query Editor select the Add Column tab on the ribbon and select Column
from Examples. If you choose the drop-down, you can select either From All Columns (the default, if you just
select the button instead of the drop-down) or select From Selection. In this article, we'll walk through selecting
From All Columns.

The Add Column From Examples pane

Once you make a selection to add a new column from examples, a new pane appears that shows the columns in
the current table (you may need to scroll to see them all). The new Column1 is also shown to the right, which is
the column that Power BI Desktop creates based on your examples. Below the new Column1 header, there are
blank cells where you can type your examples that Power BI uses to create rules and transformations to match
your example.
Notice that this is an Applied Step in the Query Settings pane. As always, Query Editor will record your
transformation steps and apply them to the query, in order.

This is called the Add Columns From Examples pane, and it consists of four primary areas:
1. The Command bar that includes a brief description of the feature or the transformation.
2. The Send Feedback option to help Power BI improve this feature.
3. The OK and Cancel buttons, which let you commit your transformations and add the column or cancel.
4. The new column area, where you can type your sample values in any of the rows (to provide Power BI with
your example), relating to other columns in that row.

As you type your example in the new column, Power BI gives you a preview of how the column it's creating will
look, based on the transformations it detects. For example, if you type Alabama in the first row, it corresponds to
the Alabama value in the first column of the table. As soon as you press Enter, Power BI fills in the column based
on that value.
But, then say you go to the row that includes Massachusetts[E ] and delete that last [E ] portion (because you don't
want it anymore). Power BI detects the change and uses the example to create a transformation. Notice the
explanation of the transform in the upper-middle pane.
As you continue to provide examples, Query Editor adds to the transformations. When you're satisfied, you can
select OK to commit your changes.

See Add Column from Examples in action

Want to see this working? The following video shows this feature being put to use, using the data source provided
earlier in this example. Take a look and follow along for yourself!
https://www.youtube.com/embed/-ykbVW9wQfw

Considerations and limitations

There are many transformations that are available when using Add column from Examples, but not every
transformation is included. The following list provides all of the supported transformations.
Reference
Reference to a specific column (including trim, clean, and case transformations)
Text transformations
Combine (supports combination of literal strings and entire column values)
Replace
Length
Extract
First Characters
Last Characters
Range
Text before Delimiter
Text after Delimiter
Text between Delimiters
Length
The following supported text transformations are available beginning with the November 2017 release
of Power BI Desktop:
Remove Characters
 Keep Characters

NOTE
All Text transformations take into account the potential need to trim, clean, or apply a case transformation to the column
value.

Date transformations
Day
Day of Week
Day of Week Name
Day of Year
Month
Month Name
Quarter of Year
Week of Month
Week of Year
Year
Age
Start of Year
End of Year
Start of Month
End of Month
Start of Quarter
Days in Month
End of Quarter
Start of Week
End of Week
Day of Month
Start of Day
End of Day
Time transformations
Hour
Minute
Second
To Local Time

NOTE
All Date and Time transformations take into account the potential need to convert the column value to Date or Time or
DateTime.

Number transformations
Absolute Value
Arccosine
Arcsine
 Arctangent
Convert to Number
Cosine
Cube
Divide
Exponent
Factorial
Integer Divide
Is Even
Is Odd
Ln
Base-10 Logarithm
Modulo
Multiply
Round Down
Round Up
Sign
Sin
Square Root
Square
Subtract
Sum
Tangent
The following supported number transformation is available beginning with the November 2017 release
of Power BI Desktop:
Bucketing/Ranges
General
Conditional Column
 Add a custom column in Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

You can easily add a new custom column of data to your model using Query Editor in Power BI Desktop. You
can create and rename your custom column using easy buttons to create M formulas that define your custom
column. The M formula has a comprehensive function reference content set.

Creating a custom column is another Applied Step to the query you create in Query Editor, which means it can
be changed, moved earlier or later, or modified at any time.

Use Query Editor to add a new custom column

To create a new custom column, launch Query Editor. You can do this by selecting Edit Queries from the Home
ribbon in Power BI Desktop.
Once Query Editor is launched and you have some data loaded, you can add a custom column by selecting the
Add Column tab on the ribbon, and then selecting Custom Column.

The Add Custom Column window appears, which is described in the following section.

The Add Custom Column window

In the Add Custom Column window, you see the list of available fields in the pane on the right, the name of your
custom column on the top (you can rename it just by typing a new name in that text box), and the M formula that
you create (or write) based on inserting fields from the right, adding operators, and otherwise building the formula
on which your new custom column is defined.
Create formulas for your custom column
You can select a field from the Available columns: list on the right, and select << Insert to add them to the
custom column formula. You can simply double-click on a column in the list to add it, too.
As you type the formula and build your column, in the bottom of the window, you'll see an indicator telling you, in
real time (as you type), whether any syntax errors are detected. If all is good, you'll see a green checkmark.

But, if you have some sort of error in your syntax, you get a yellow warning icon, along with the error detected, and
a link that puts the cursor (in your formula) where the error is detected.
When you select OK, your custom column is added to the model, and the Added Custom step is added to your
query's Applied Steps.

If you double-click the Added Custom step in the Applied Steps pane, the Add Custom Column window
appears again, with the custom column formula you created already loaded, and ready for you to modify if
necessary.

Using the Advanced Editor for Custom Columns

You can also create a custom column (and modify any step of your query, for that matter) using the Advanced
Editor. In Query Editor select the View tab and then select Advanced Editor to display the Advanced Editor.
The Advanced Editor gives you full control over your query.

Next steps
There are other ways to create a custom column, including creating a column based on examples you provide to
Query Editor. See the following article for more information on creating custom columns from examples:
Add a column from an example in Power BI Desktop
Introduction to M formula language
M function reference
 Optimize a Power BI visual for any size
1/14/2019 • 2 minutes to read • Edit Online

By default, when you create a new report, the visuals are responsive: They change dynamically to display the
maximum amount of data and insight, no matter the screen size. For older reports, you can set their visuals to
resize dynamically, too.
As a visual changes size, Power BI prioritizes the data view, for example removing padding and moving the legend
to the top of the visual automatically, so the visual remains informative even as it gets smaller. Responsiveness is
especially useful in visuals in the Power BI mobile app on phones.

Any visual with X and Y axes, and slicers, can resize responsively.

Turn on responsiveness in Power BI Desktop

1. In an older report in Power BI Desktop, on the View tab, make sure you're in Desktop Layout.
2. Select a visual, and in the Visualizations pane select the Format section.
3. Expand General > slide Responsive to On.

Now when you create a report optimized for the phone and add this visual, it will resize gracefully.

Turn on responsiveness in the Power BI service

You can turn on responsiveness for a visual in an older report in the Power BI service. You need to be able to edit
the report.
1. In a report in the Power BI service ( https://powerbi.com), select Edit Report.
2. Select a visual, and in the Visualizations pane select the Format section.
3. Expand General > slide Responsive to On.
 Now when you create a phone view of this report and add this visual, it will resize gracefully.

Next steps
Create reports optimized for the Power BI phone apps
View Power BI reports optimized for your phone
More questions? Try asking the Power BI Community
 Use inline hierarchy labels in Power BI Desktop
1/14/2019 • 3 minutes to read • Edit Online

Power BI Desktop supports the use of inline hierarchy labels, which is the first of two features intended to
enhance hierarchical drilling. The second feature, which is currently in development, is the ability to use nested
hierarchy labels (stay tuned for that - our updates happen frequently).

How inline hierarchy labels work

With inline hierarchy labels, you can see hierarchy labels as you expand visuals using the Expand All feature. One
great benefit to seeing these hierarchy labels is that you can also choose to sort by these different hierarchy labels
as you expand your hierarchical data.
Using the built-in Expand feature (without sorting by hierarchy labels)
Before we see inline hierarchy labels in action, let's review the default Expand to next level feature behavior.
Doing so will help us understand (and appreciate) how useful inline hierarchy labels can be.
The following image shows a bar chart visual for annual sales. When you right-click on a bar, you can choose
Expand to next level.

NOTE
As an alternative to right-clicking on a bar, you can select the Expand button on the top left of the visualization.

Once Expand to next level is selected, the visual expands the date hierarchy from Year to Quarter, as shown in
the following image.

Notice that the Year and Quarter labels are shown inline together - this labeling scheme continues as you Expand
All down to the bottom of the hierarchy.

This is how the built-in Date hierarchy, associated with fields that have a date/time data type, behaves. Let's head
to the next section, and see how the new inline hierarchy labels feature is different.
Using inline hierarchy labels
Now let's look at a different chart - using data that has informal hierarchies. In the following visual, we have a bar
chart with Quantity, using ProductName as the axis. In this data, ProductName and ShipCountry form an
informal hierarchy. From here, you can again select Expand to next level to drill down into the hierarchy.
Selecting Expand to next level shows the next level with the inline display of hierarchy labels. By default, inline
hierarchies are sorted by the measure value – in this case, Quantity. With inline hierarchy labels enabled, you can
choose to sort this data by the hierarchy too, by selecting the ellipsis in the upper right corner (the ...), then
selecting Sort by ProductName ShipCountry as shown in the following image.

Once ShipCountry is selected, the data is sorted based on the informal hierarchy selection, as shown in the
following image.
 NOTE
The inline hierarchy label feature doesn't yet allow for the built-in time hierarchy to be sorted by value; it's only sorted by
hierarchy order.

Troubleshooting
It's possible for your visuals to get stuck in an expanded inline hierarchy level state. In some cases, you might find
that some of your visuals are stuck in the mode where they were expanded, in which case drilling up doesn't work.
This can happen if you happened to take the following steps (the fix for this is below these steps):
Steps that might get your visuals stuck in an expanded state:
1. You enable the inline hierarchy label feature
2. You create some visuals with hierarchies
3. Then you Expand All and save your file
4. You then disable the inline hierarchy label feature, and restart Power BI Desktop
5. Then you re-open your file
If you happen to take those steps, and your visuals are stuck in expanded mode, you can do the following to
troubleshoot them:
1. Re-enable the inline hierarchy label feature, then restart Power BI Desktop
2. Re-open your file, and drill back up to top of your affected visual(s)
3. Save your file
4. Disable the inline hierarchy label feature, then restart Power BI Desktop
5. Re-open your file
Alternatively, you can just delete your visual and recreate it.
 Use the numeric range slicer in Power BI Desktop
1/14/2019 • 3 minutes to read • Edit Online

With the numeric range slicer, you can apply all sorts of filters to any numeric column in your data model. You
can choose to filter between numbers, less than or equal to a number, or greater than or equal to a number.
While this may sound straightforward, it's a very powerful way to filter your data.

Using the numeric range slicer

You can use the numeric range slicer just like any other slicer. Simply create a slicer visual for your report, and
then select a numeric value for the Field value. In the following image, the LineTotal field is selected.
Select the down-arrow link in the upper-right corner of the numeric range slicer and a menu appears.

For the numeric range, you can select from the following three selections:
Between
Less than or equal to
Greater than or equal to
When you select Between from the menu, a slider appears and you can filter for numeric values that fall between
the numbers. In addition to using the slider bar itself, you can click in either box and type in the values. This is
convenient when you want to slice on specific numbers, yet the granularity of moving the slicer bar makes it
difficult to land exactly on that number.
In the following image, the report page is filtered for LineTotal values that range between 2500.00 and 6000.00.
When we select Less than or equal to, the left (lower value) handle of the slider bar disappears, and we can
adjust only the upper bound of the slider bar. In the following image, we set the slider bar maximum to 5928.19.

Lastly, if we select Greater than or equal to, then the right (highest value) slider bar handle disappears, and we
can adjust the lower value, as seen in the following image. Now only items with a LineTotal greater than or equal
to 4902.99 are displayed in the visuals on the report page.
Snap to whole numbers with the numeric range slicer
A numeric range slicer will snap to whole numbers if the data type of the underlying field is Whole Number. This
lets your slicer to cleanly align who whole numbers. Decimal Number type fields let you enter or select fractions
of a number. The formatting applied in the textbox matches the formatting set on the field, even though you can
type in or select more precise numbers.

Display formatting with the date range slicer

When using a slicer to display or set a range of dates, the format of the date is always displayed using the Short
Date format, based on the user's browser or operating system locale. This is the display format regardless of the
data type settings for the underlying data or model.
For example, you could have a long date format for the underlying data type (such as dddd, MMMM d, yyyy which
would format a date in other visuals or circumstances as Wednesday, March 14, 2001), but in the date range slicer
that date would be displayed in the slicer as 03/14/2001.
Displaying the Short Date format in the slicer ensures the length of the string stays consistent and compact
within the slicer.

Limitations and considerations

The following limitations and considerations currently apply to the numeric range slicer:
The numeric range slicer currently filters every underlying row in the data, not any aggregated value. For
example, if a Sales Amount field is used, each transaction based on Sales Amount would be filtered upon, not
the sum of Sales Amount for each data point of a visual.
It does not currently work with Measures.
You can type any number into the textboxes on a numeric slicer, even if it is outside the range of values in the
underlying column. This lets you set up filters if you know the data may change in future.
 Create a responsive slicer you can resize in Power BI
1/14/2019 • 2 minutes to read • Edit Online

Responsive slicers resize to fit any space on your report. With responsive slicers, you can resize them to different
sizes and shapes, from horizontal to square to vertical, and the values in the slicer rearrange themselves as you do.
In Power BI Desktop and in the Power BI service, you can make horizontal slicers and date/range slicers
responsive. Date/range slicers also have improved touch areas so it’s easier to change them with a fingertip. You
can make responsive slicers as small or as large as you want; they also resize automatically to fit well on reports in
the Power BI service and also in the Power BI mobile apps.

Create a slicer
The first step to creating a dynamic slicer is to create a basic slicer.

1. Select the Slicer icon in the Visualizations pane.

2. Drag the field you want to filter on to Field.
Convert to a horizontal slicer
1. With the slicer selected, in the Visualizations pane select the Format tab.
2. Expand the General section, then for Orientation, select Horizontal.

3. You'll probably want to make it wider, to show more values.

Make it responsive and experiment with it
This step is easy.
1. Right under Orientation in the General section of the Format tab, slide Responsive to On.

2. Now you can play with it. Drag the corners to make it short, tall, wide, and narrow. If you make it small
enough, it becomes just a filter icon.

Add it to a phone report layout

In Power BI Desktop, you can create a phone layout for each page of a report. If a page has a phone layout, it
displays on a mobile phone in portrait view. Otherwise, you need to view it in landscape view.
1. On the View menu, select Phone Layout.

2. Drag all the visuals you want in the phone report to the grid. When you drag the responsive slicer, make it
 the size you want -- in this case, just a filter icon.

Read more about creating reports optimized for the Power BI mobile apps.

Make a time or range slicer responsive

You can follow the same steps to make a time or range slicer responsive. After you set Responsive to On, you
notice a few things:
Visuals optimize the order of input boxes depending on the size allowed on the canvas.
Data-element display is optimized to make the slicer as usable as possible, based on the size it’s allowed on the
canvas.
New round handlebars on the sliders optimize touch interactions.
When a visual becomes too small to be useful, it becomes an icon representing the visual type in its place. To
interact with it, just double-tap to open it in focus mode. This saves valuable space on the report page without
losing the functionality.

Next steps
Slicers in the Power BI service
More questions? Try asking the Power BI Community
 Use Power BI service or Power BI Desktop to create
a custom Answer Page for Cortana
1/14/2019 • 3 minutes to read • Edit Online

Use the full capabilities of Power BI to create special report pages, called Cortana answer pages (and sometimes
called Cortana answer cards) designed specifically to answer Cortana questions.

IMPORTANT
If you are trying out the Cortana and Power BI dashboard preview, you can skip the rest of this article. There are no setup
requirements for Cortana to be able to search your Power BI dashboards.

Before you begin

You have four documents that guide you through setting up and using Cortana for Power BI. If you haven't
already, start by reading article one. Article two is especially important because it describes some steps you'll
need to take before you can begin using Cortana answer pages.
Article 1: Learn how Cortana and Power BI work together
Article 2: For searching Power BI reports: Enable the Cortana - Power BI - Windows integration
Article 3: This article
Article 4: Troubleshoot issues
Create a Cortana answer page designed specifically for Cortana
A Cortana answer page in a report is sized specifically for Cortana so that Cortana can display it in-screen as an
answer to a question. To create an answer page for Cortana:
1. We recommend starting with a blank report page.
2. In the Visualizations pane, select the paint roller icon and choose Page Size > Type > Cortana.

3. Create a visual or a set of visuals that you want to appear in Cortana in response to a particular question
(or set of questions).

NOTE
At the moment, Cortana answer pages don't support images having static images shown in them. You can include images
in table or matrix visuals that are dynamically pulled in based on a URL in your data.

4. Ensure that all visuals fit within the page borders. Optionally, modify display settings, data labels, colors,
and backgrounds.
5. Name the page and add alternate names. Cortana uses these names when it searches for results. In the
Visualizations pane, select the paintbrush icon and choose Page Information. Enable Q&A for this
visual by moving the slider to On.

TIP
To improve results, avoid using words that are also column names.

6. Optionally, if your report has page level filters, you may want to set Require single selection. Cortana
will only display this report as an answer if one, and only one, of the filter items is specified in the question.
 Require single selection can be found at the bottom of the Filters pane.

NOTE
You don't have to set Require single selection to ask Cortana to display a report with page level filters. For
example “show sales for Charlotte Lindseys” will display the answer page regardless of the Require Single Selection
setting.

For example, if you ask Cortana:

"show sales by store name," this answer page does not appear because you did not include any of
the items in the required page level filter.
"show sales for Cary Lindseys and Charlotte Lindseys," this answer page does not appear because
you specified more than one item from the required page level filter.
"show sales for Charlotte Lindseys," this answer page appears.
= "show sales" this answer page does not appear because you didn't include any of the items in the
required page level filter.

IMPORTANT
Before your Cortana answer page can be accessed by Cortana, you will need to Enable the dataset for Cortana.

How does Cortana order the results?

Results with high scoring answers (such as a complete match of a specified page name) appear first as a best
match in Cortana. Multiple best matches can appear if there are multiple Cortana answer pages in Power BI.
Medium or lower-scoring answers, such as answers not based on the name of an answer page or a question with
words not understood by Power BI, are listed as links below best matches in Cortana.

NOTE
When a new dataset or custom Cortana answer page is added to Power BI and enabled for Cortana, it can take up to 30
minutes for results to begin appearing in Cortana. Logging in and out of Windows 10, or otherwise restarting the Cortana
process in Windows 10, will cause new content to appear immediately.
Next steps
Using Cortana with Power BI
Still can't get Cortana to work with Power BI? Try the Cortana troubleshooter.
More questions? Try the Power BI Community
 Row-level security (RLS) with Power BI Desktop
1/23/2019 • 4 minutes to read • Edit Online

Row -level security (RLS ) with Power BI Desktop restricts data access for given users. Filters restrict data at the row
level. You can define filters within roles.
You can now configure RLS for data models imported into Power BI with Power BI Desktop. You can also
configure RLS on datasets that are using DirectQuery, such as SQL Server. Previously, you were only able to
implement RLS within on-premises Analysis Services models outside of Power BI. For Analysis Services live
connections, you configure Row -level security on the on-premises model. The security option does not show up
for live connection datasets.

IMPORTANT
If you defined roles and rules within the Power BI service, you will need to recreate those roles within Power BI Desktop and
publish the report to the service.

Learn more about options for RLS within the Power BI Service.

Define roles and rules in Power BI Desktop

You can define roles and rules within Power BI Desktop. When you publish to Power BI, it also publishes the role
definitions.
To define security roles, follow these steps.
1. Import data into your Power BI Desktop report, or configure a DirectQuery connection.

NOTE
You can't define roles within Power BI Desktop for Analysis Services live connections. You need to do that within the
Analysis Services model.

2. Select the Modeling tab.

3. Select Manage Roles.

4. Select Create.
5. Provide a name for the role.
6. Select the table that you want to apply a DAX rule.
7. Enter the DAX expressions. This expression should return a true or false. For example: [Entity ID ] = “Value”.

NOTE
You can use username() within this expression. Be aware that username() has the format of DOMAIN\username
within Power BI Desktop. Within the Power BI service and Power BI Report Server, it's in the format of the user's User
Principal Name (UPN). Alternatively, you can use userprincipalname(), which always returns the user in the format of
their user principal name, [email protected].

8. After you have created the DAX expression, you can select the check above the expression box to validate
the expression.

9. Select Save.
You can't assign users to a role within Power BI Desktop. You assign them in the Power BI service. You can enable
dynamic security within Power BI Desktop by making use of the username() or userprincipalname() DAX functions
and having the proper relationships configured.

Validate the roles within Power BI Desktop

After you've created your roles, test the results of the roles within Power BI Desktop.
1. Select View As Roles.
 In View as roles, you see the roles you've created.

2. Select a role you created > OK to apply that role. The report renders the data relevant for that role.
3. You can also select Other user and supply a given user. It's best to supply the User Principal Name (UPN )
as that's what the Power BI service and Power BI Report Server use.

4. Select OK and the report renders based on what that user can see.
Within Power BI Desktop, Other user only displays different results if you're using dynamic security based on
your DAX expressions.

Limitations
Following is a list of the current limitations for row -level security on cloud models.
If you previously defined roles and rules in the Power BI service, you must re-create them in Power BI
Desktop.
You can define RLS only on the datasets created with Power BI Desktop. If you want to enable RLS for
datasets created with Excel, you must convert your files into Power BI Desktop (PBIX) files first. Learn more
Only ETL and DirectQuery connections are supported. Live connections to Analysis Services are handled in
the on-premises model.
Cortana is not supported with RLS at this time.

Known issues
There is a known issue where you'll get an error message if you try to publish a previously published report from
Power BI Desktop. The scenario is as follows.
1. Anna has a dataset that is published to the Power BI service and has configured RLS.
2. Anna updates the report in Power BI Desktop and republishes.
3. Anna receives an error.
Workaround: Republish the Power BI Desktop file from the Power BI service until this issue is resolved. You can
do that by selecting Get Data > Files.

FAQ
Question: What if I had previously created roles and rules for a dataset in the Power BI service? Will they still
work if I do nothing?
Answer: No. Visuals will not render properly. You will have to re-create the roles and rules within Power BI
Desktop and then publish to the Power BI service.
Question: Can I create these roles for Analysis Services data sources?
Answer: You can if you imported the data into Power BI Desktop. If you are using a live connection, you will not
be able to configure RLS within the Power BI service. This is defined within the Analysis Services model on-
premises.
Question: Can I use RLS to limit the columns or measures accessible by my users?
Answer: No. If a user has access to a particular row of data, they can see all the columns of data for that row.
Question: Does RLS let me hide detailed data but give access to data summarized in visuals?
Answer: No, you secure individual rows of data but users can always see either the details or the summarized
data.

Next steps
Row -level security (RLS ) with the Power BI service
More questions? Try asking the Power BI Community
 Customizing Tooltips in Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

Tooltips are an elegant way of providing more contextual information and detail to data points on a visual. The
following image shows a tooltip applied to a chart in Power BI Desktop.

When a visualization is created, the default tooltip displays the data point's value and category. There are many
instances when being able to customize the tooltip information would be useful, and would provide additional
context and information for users viewing the visual. Custom tooltips enable you to specify additional data points
that display as part of the tooltip.

How to customize tooltips

To create a customized tooltip, in the Fields well of the Visualizations pane, simply drag a field into the Tooltips
bucket, shown in the following image. In the following image, two fields have been placed into the Tooltips bucket.
Once tooltips are added to the field well, hovering over a data point on the visualization shows the values for those
fields in the tooltip.
Customizing tooltips with aggregation or Quick Calcs
You can further customize a tooltip by selecting an aggregation function or a Quick Calc by selecting the arrow
beside the field in the Tooltips bucket, and selecting from the available options.

There are many ways to customize Tooltips, using any field available in your dataset, to convey quick information
and insights to users viewing your dashboards or reports.
 Text boxes and shapes Power BI reports
1/18/2019 • 2 minutes to read • Edit Online

Text boxes and shapes can be added to reports using Power BI service and Power BI Desktop. In both cases, you
must have editing permissions for the report. If a report has been shared with you in Power BI service, you will not
have editing permissions.
Watch Will use Power BI Desktop to add static images to a report, and then follow the steps below to try it out
yourself using Power BI service instead.

https://www.youtube.com/embed/_3q6VEBhGew

Add a text box to a report

1. Open a report in Editing view.
2. Place your cursor in any blank area on the report canvas and select Text Box.

3. Type your text into the text box and, optionally, format font, color, and text alignment.

4. To position the text box, select the grey area at the top and drag. And to resize the text box, select and drag
any of the outline handles.
5. With the text box still selected, add additional formatting in the VISUALIZATIONS pane. In this example
we've formatted the background and border. You can also create an exact size and position for a text box.

6. To close the text box, select any blank space on the report canvas.

7. Select the pin icon to pin the text box to a dashboard.

Add a shape to a report

1. Place your cursor anywhere on the report canvas and select Shapes.

2. From the dropdown, select a shape to add it to your report canvas. Let's add an arrow to direct attention to
 the bubble with the highest total sales variance.
In the Format shape pane, customize your shape. In this example we've created a red arrow with a dark red
border, rotated 90 degrees.

3. To position the shape, select the grey area at the top and drag. And to resize the shape, select and drag any
of the outline handles. As with the text box, you can also create an exact size and position for a shape.

NOTE: Shapes cannot be pinned to a dashboard, except as one of the visuals when you pin a live page.

Next steps
Add a hyperlink to a text box
Power BI - Basic Concepts
More questions? Try the Power BI Community
 Add a hyperlink to a text box in a report
1/18/2019 • 2 minutes to read • Edit Online

You can add text boxes to reports, pin them to dashboards from reports, and add them directly to dashboards.
Wherever the text box is, you can always add a hyperlink to it.

NOTE: For information on hyperlinks in Power BI tables and matrixes, see Hyperlinks in tables. For
information on adding text boxes to your dashboard, see Add a tile directly from the dashboard .

https://www.youtube.com/embed/_3q6VEBhGew#t=0m55s

To add a hyperlink to a text box in a report

1. Create a text box and add some text.
2. Select existing text, or add new text to use as a hyperlink.

3. Select the hyperlink icon .

4. Type or paste the URL in the hyperlink field, and select Done.

5. Test the link.

Place your cursor anywhere in the highlighted text to display the URL.

Select the URL to open the page in a new browser window.

To remove the hyperlink but leave the text

1. In the text box, select the hyperlink to highlight it,
2. Choose Remove.

Next steps
Text boxes in Power BI reports
More questions? Try the Power BI Community
 Add hyperlinks to a table
1/18/2019 • 3 minutes to read • Edit Online

This topic teaches you how to use Power BI Desktop to create hyperlinks. Then use either Desktop or Power BI
service to add those hyperlinks to your report tables and matrixes.

NOTE
Hyperlinks in tiles on dashboards and text boxes on dashboards can be created on-the-fly using Power BI service. Hyperlinks
in text boxes in reports can be created on-the-fly using Power BI service and Power BI Desktop.

To create a hyperlink in a table or matrix using Power BI Desktop

Hyperlinks in tables and matrixes can be created in Power BI Desktop, but not from Power BI Service. Hyperlinks
can also be created in Excel Power Pivot before the workbook is imported into Power BI. Both methods are
described below.

Create a table or matrix hyperlink in Power BI Desktop

The procedure for adding a hyperlink depends on whether you've imported the data or connected to it using
DirectQuery. Both scenarios are described below.
For data imported into Power BI
1. If the hyperlink doesn't already exist as a field in your dataset, use Desktop to add it as a custom column.
2. In Data view, select the column and in the Modeling tab choose the dropdown for Data Category.
3. Select Web URL.
4. Switch to Report view and create a table or matrix using the field categorized as a Web URL. The hyperlinks
will be blue and underlined.

NOTE
The URLS must start with http:// , https:// or www.

5. If you don't want to display a long URL in a table, you can display a hyperlink icon instead. Note that
you can't display icons in matrixes.
Select the chart to make it active.
Select the paint roller icon to open the Formatting tab.
Expand Values, locate URL icon, and turn it to On.
6. (Optional) Publish the report from Desktop to Power BI service and open the report in Power BI service.
The hyperlinks will work there as well.
For data connected with DirectQuery
You can't create a new column in DirectQuery mode. But if your data already contains URLs, you can turn them
into hyperlinks.
1. In Report view, create a table using a field that contains URLs.
2. Select the column, and in the Modeling tab, choose the dropdown for Data Category.
3. Select Web URL. The hyperlinks will be blue and underlined.
4. (Optional) Publish the report from Desktop to Power BI service and open the report in Power BI service. The
hyperlinks will work there as well.

Create a table or matrix hyperlink in Excel Power Pivot

Another way to add hyperlinks to your Power BI tables and matrixes is to create the hyperlinks in the dataset
before you import/connect to that dataset from Power BI. This example uses an Excel workbook.
1. Open the workbook in Excel.
2. Select the PowerPivot tab and then choose Manage.

3. When PowerPivot opens, select the Advanced tab.

4. Place your cursor in the column that contains the URLs that you'd like to turn into hyperlinks in Power BI
tables.

NOTE
The URLS must start with http:// , https:// or www.

5. In the Reporting Properties group, select the Data Category dropdown and choose Web URL.

6. From the Power BI service or Power BI Desktop, connect to or import this workbook.
7. Create a table visualization that includes the URL field.
Considerations and troubleshooting
Q: Can I use a custom URL as a hyperlink in a table or matrix?
A: No. You can use a link icon. If you need custom text for your hyperlinks and your list of URLs is short, consider
using a text box instead.

Next steps
Visualizations in Power BI reports
Power BI - Basic Concepts
More questions? Try the Power BI Community
 Conditional formatting in tables
1/14/2019 • 3 minutes to read • Edit Online

With conditional formatting for tables, you can specify customized cell colors based on cell values, or based on
other values or fields, including using gradient colors. You can also display cell values with data bars.
To access conditional formatting, in the Fields well of the Visualizations pane in Power BI Desktop, select the
down-arrow beside the value in the Values well that you want to format (or right-click the field). You can only
manage conditional formatting for fields in the Values area of the Fields well.

The following sections describe each of these conditional formatting options. One or more options can be
combined in a single table column.

NOTE
When applied to a table, conditional formatting overrides any custom table styles applied to the conditionally formatted cells.

To remove conditional formatting from a visualization, just right-click the field again, select Remove conditional
formatting and then the type of formatting to remove.
Background color scales
Selecting Conditional formatting and then Background color scales brings up the following dialog.

You can select a field from your data model to base the colors on, by setting Color based on to that field. In
addition, you can specify the aggregation type for the selected field with the Summarization value. The field to be
colored is specified in the Apply color to field, so you can keep track. You can apply conditional formatting to text
and date fields, as long as you choose a numeric value as the basis of the formatting.
To use discrete color values for given value ranges, select Color by rules. To use a color spectrum, leave Color by
rules unchecked.

Color by rules
When you select Color by rules, you can enter one or more value ranges, each with a set color. Each value range
starts with an If value condition, an and value condition, and a color.
Table cells with values in each range are filled with the given color. There are three rules in the following figure.

The example table now looks like this:

Color minimum to maximum

You can configure the Minimum and Maximum values and their colors. If you select the Diverging box, you can
configure an optional Center value as well.
The example table now looks like this:

Font color scales

Selecting Conditional formatting and then Font color scales brings up the following dialog. This dialog is
similar to the Background color scales dialog, but changes the font color rather than the cell background color.
The example table now looks like this:

Data bars
Selecting Conditional formatting and then Data bars brings up the following dialog.
By default, the Show bar only option is unchecked, and so the table cell shows both the bar and the actual value.

If the Show bar only option is checked, the table cell only shows the bar.
Color formatting by field value
You can use a measure or a column that specifics a color, either using a text value or a hex code, to apply that color
to the background of font color of a table or matrix visual. You can also create custom logic for a given field, and
have that logic apply the desired color to the font or background.
For example, in the following table there is a color associated with each product model.

To format that cell based on its field value, select the Conditional formatting dialog by right-clicking the Color
column for that visual, and in this case, select Background color from the menu.
In the dialog that appears, select Field value in the Format by drop down area, as shown in the following image.

You can repeat that process for the font color, and the result in the visual will be a solid color in the color column,
as shown in the following screen.

You could also create a DAX calculation based on business logic, that outputs different hex codes based on
conditions you prefer. This is generally easier than creating multiple rules in the conditional formatting dialog.
Consider the ColorKPI field in the following sample image.
You could then set the field value for Background color in the following way.

And you could then get results like the following matrix.

There are many more variations you could create, just by using your imagination and a bit of DAX.

Next steps
For more information, see the following article:
Tips and tricks for color formatting in Power BI
 Sort by column in Power BI Desktop
1/14/2019 • 4 minutes to read • Edit Online

In Power BI Desktop and the Power BI service, you can change how a visual looks by sorting it by different data
fields. By changing how you sort a visual, you can highlight the information you want to convey, and ensure the
visual reflects that trend (or emphasis).
Whether you're using numeric data (such as sales figures) or text data (such as state names), you can sort your
visualizations as desired, and make them look like you want them to. Power BI provides lots of flexibility for
sorting, and quick menus for you to use. On any visual, select the ellipses menu (...) and then select the field by
which you want to sort, as shown in the following image.

More depth, and an example

Let's take an example that has more depth, and see how it works in Power BI Desktop.
The following visualization shows costs, quantities, and amounts by manufacturer name. Here's the visualization as
it looks before we do any further sorting.
The visual is currently sorted by SalesQuantity - we can tell that by matching the color of the ascending bars to
the legend, but there's a better way to determine the current sort column: the ellipses menu (...) in the upper right
corner of the visual. When we select the ellipses, we see the following:

The current sorting field is SalesQuantity, indicated by the facts that Sort By SalesQuantity is in bold and
has a yellow bar.
The current sorting direction is smallest to largest, as shown by the little icon A/Z (A above Z ) and a down
arrow.
We'll look at the sorting field and direction independently in the next two sections.

Selecting which column to use for sorting

You noticed the yellow bar beside Sort By SalesQuantity in the More Options menu, which indicates that the
visual is sorted by the SalesQuantity column. Sorting by another column is easy - just select the ellipses to show
the ellipsis menu, then select another column.
In the following image, we selected DiscountAmount as the column by which we want to sort. That column
happens to be one of the lines on the visual, rather than one of the bars. Here's what it looks like after we select
Sort By DiscountAmount.

Notice how the visual has changed. The values now are ordered from highest DiscountAmount value, in this visual
Fabrikam Inc., down to Northwind Traders which has the lowest value.
But what if we want to sort ascending, instead of descending? The next section shows just how easy that is.

Selecting the sort order - smallest to largest, largest to smallest

When we take a closer look at the Options menu from the previous image, we see that the icon next to Sort By
DiscountAmount shows Z/A (Z above A). Take a look:

When Z/A is displayed, it means the visual is being sorted by the selected column in order of greatest value to
smallest value. Want to change that? No problem - just tap or click that Z/A icon, and it changes the sort order to
A/Z and sorts the visual (based on the selected column) from smallest to greatest value.
Here's our same visual, this time after tapping the Z/A icon on the Sort By DiscountAmount menu item to
change its ordering. Notice that Northwind Traders is now the first manufacturer listed, and Fabrikam Inc. is the
last - the opposite sorting from before.
You can sort by any column included in the visual - we could easily select SalesQuantity as the column by which
we want to sort, with Sort By SalesQuantity, to show the manufacturers with the most sales first, and still retain
the other columns in the visual however they happen to apply to that manufacturer. Here's a look at the visual with
those settings.

Sort using the Sort by Column button

There's another way to sort your data, and that's by using the Sort by Column button in the Modeling ribbon.
This approach to sorting requires that you select a column from the Fields pane, and then select the Sort by
Column button to choose how (by which column) you want to sort your visual. You have to select the column
(field) you want to sort from the Fields pane in order to enable the Sort by Column button - otherwise the button
is inactive.
Let's look at a common example: you have data from each month of the year, and you want to sort it based on
chronological order. The following steps show you how.
1. First, notice that when the visual is selected but no column is selected in the Fields pane, the Sort by
Column button is inactive (grayed out).

2. When we select the column by which we want to sort, in the Fields pane, the Sort by Column button
becomes active.
3. Now, with the visual selected, we can select MonthOfYear, instead of the default (MonthName), and the
visual now sorts in the order we want: by the month of the year.

And that's it. Remember that you must select a column in the Fields pane for the Sort by Column button to
become active.

Getting back to default column for sorting

You can sort by any column you'd like, but there may be times when you want the visual to return to its default
sorting column. No problem. For a visual that has a sort column selected (a selected sort column has a yellow bar
beside it in the ellipsis menu, as we learned), simply open the More Options menu and select that column again,
and the visualization returns to its default sort column.
For example, here's our previous chart:

When we go back to the menu and select SalesQuantity again, the visual defaults to being ordered alphabetically
by Manufacturer, as shown in the following image.

With so many options for sorting your visuals, creating just the chart or image you want is easy.
 Create reports optimized for the Power BI mobile
apps
3/18/2019 • 4 minutes to read • Edit Online

You can improve the experience of viewing your reports in the mobile apps on a phone or tablet. Create a portrait
layout of a report, specifically for phones and tablets. In Power BI Desktop and in the Power BI service, you adapt
your report by rearranging and resizing visuals in a portrait layout for an optimal experience. You don't have to
include all of them. Plus you can create responsive visuals and responsive slicers that resize well for viewing on a
phone. Also, if you add filters to your report, those filters show up automatically in the optimized report. Your
report readers can see them and filter the report with them.

Lay out a portrait version of a report page

After you create a report, you can optimize it for phones and tablets.
1. In Report View in Power BI Desktop, on the View tab, select Phone Layout.
 In the Power BI service, select Edit Report > Mobile Layout.
You see a blank canvas shaped like a phone. All of the visuals on the original report page are listed in the
Visualizations pane on the right.
2. To add a visual to the phone layout, drag it from the Visualizations pane to the phone canvas.
Phone reports use a grid layout. As you drag visuals to the mobile canvas, they snap to that grid.

You can add some or all the master report page visuals to the phone report page. You can add each visual
only once.
3. You can resize your visuals on the grid, as you would for tiles on dashboards and mobile dashboards.
The phone report grid scales across phones of different sizes, so your report looks good on small- and
large-screen phones.
Optimize a visual for any size
You can set the visuals in your dashboard or report to be responsive. They can change dynamically to display the
maximum amount of data and insight, no matter the screen size.
As a visual changes size, Power BI prioritizes the data view. For example, it can remove padding and move the
legend to the top of the visual automatically, so the visual remains informative even as it gets smaller.
You choose whether to turn on responsiveness for each visual. Read more about optimizing visuals.

Considerations when creating phone report layouts

For reports with multiple pages, you can optimize all the pages or only a few.
If you've defined a background color for a report page, the phone report will have the same background color.
You can’t modify formatting settings for just the phone. Formatting is consistent between master and mobile
layouts. For example, font sizes will be the same.
To change a visual, such as changing its formatting, dataset, filters, or any other attribute, return to the regular
report authoring mode.
Power BI provides default titles and page names for phone reports in the mobile app. If you’ve created text
visuals for titles and page names in your report, consider not adding them to your phone reports.

Remove a visual from the phone layout

To remove a visual, click the X in the top-right of the visual on the phone canvas, or select it and press
Delete.
Removing the visual here only removes it from the phone layout canvas. The visual and the original report
aren't affected.
Enhance slicers to work well in phone reports
Slicers offer on-canvas filtering of report data. When designing slicers in the regular report authoring mode, you
can modify some slicer settings to make them more usable in phone reports:
Decide if report readers can select only one or more than one item.
Put a box around the slicer to make the report easier to scan.
Make the slicer vertical, horizontal, or responsive.
If you make the slicer responsive, as you change its size and shape it shows more or fewer options. It can be tall,
short, wide, or narrow. If you make it small enough, it becomes just a filter icon on the report page.

Read more about creating responsive slicers.

Publish a phone report

To publish the phone version of a report, you publish the main report from Power BI Desktop to the Power
BI service, and the phone version publishes at the same time.
Read more about sharing and permissions in Power BI.

View optimized and unoptimized reports on a phone or tablet

In the mobile apps on phones, Power BI automatically detects optimized and unoptimized phone reports. If a
phone-optimized report exists, the Power BI phone app automatically opens the report in phone report mode.
If a phone-optimized report doesn’t exist, the report opens in the unoptimized, landscape view.
When in a phone report, changing the phone’s orientation to landscape will open the report in the unoptimized
view with the original report layout, whether the report is optimized or not.
If you only optimize some pages, readers will see a message in portrait view, indicating the report is available in
landscape.

Report readers can turn their phones or tablets sideways to see the page in landscape mode. Read more about
interacting with Power BI reports optimized for portrait mode.

Next steps
Create a phone view of a dashboard in Power BI
View Power BI reports optimized for your phone
Create responsive visuals optimized for any size
More questions? Try asking the Power BI Community
 Use See Data and See Records in Power BI Desktop
2/13/2019 • 2 minutes to read • Edit Online

In Power BI Desktop you can drill into the details of a visualization, and see textual representations of the
underlying data or the individual data records for the selected visual. These features are sometimes referred to as
click-through, drill-through, or drill-through to details.
You can use See Data to view a textual version of the values used by the selected visualization, or use See
Records to view all the data for one selected record or data point.

IMPORTANT
See Data and See Records support only the following visualization types:
Bar chart
Column chart
Donut chart
Filled map
Funnel
Map
Pie chart
Treemap

Use See Data in Power BI Desktop

See Data shows you the data underlying a visualization. See Data appears in the Data/Drill tab in the Visual
Tools section of the ribbon when a visualization is selected.

You can also see the data by right-clicking on a visualization, and then selecting Show Data from the menu that
appears; or by selecting the More options ellipsis (...) in the upper-right corner of a visualization, and then
selecting Show Data.
 NOTE
You must be hovering over a data point in the visual for the right-click menu to be available.

When you select See Data or Show Data, the Power BI Desktop canvas displays both the visual and the textual
representation of the data. In the horizontal view, the visual is displayed on the top half of the canvas, and the data
is shown on the bottom half.
You can toggle between the horizontal view and a vertical view by selecting the icon in the upper-right corner of
the canvas.

To get back to the report, select < Back to Report in the upper-left corner of the canvas.
Use See Records in Power BI Desktop
You can also focus on one data record in a visualization, and drill into the data behind it. To use See Records, select
a visualization, then select See Records in the Data/Drill tab in the Visual Tools section of the ribbon, and then
select a data point or row on the visualization.

NOTE
If the See Records button in the ribbon is disabled and grayed-out, it means the selected visualization does not support
See Records.

You can also right-click a data element and select See Records from the menu that appears.
When you select See Records for a data element, the Power BI Desktop canvas displays all the data associated
with the selected element.

To get back to the report, select < Back to Report in the upper-left corner of the canvas.

NOTE
See Records has the following limitations:
You can't change the data in the See Records view and save it back to the report.
You can't use See Records when your visual uses a calculated measure.
You can't use See Records when you are connected to a live multidimensional (MD) model.

Next steps
There are all sorts of report formatting and data management features in Power BI Desktop. Check out the
following resources for a few examples:
Use grouping and binning in Power BI Desktop
Use gridlines, snap-to-grid, z-order, alignment and distribution in Power BI Desktop reports
 Tips and tricks for creating reports in Power BI
Desktop
2/13/2019 • 14 minutes to read • Edit Online

To get the most out of your data, sometimes you need a little extra help. We’ve put together some tips & tricks you
can use when creating reports in the Microsoft Power BI Desktop and in Microsoft Excel 2016, or Excel 2013 Pro-
Plus editions with the Power Pivot add-in enabled and Power Query installed and enabled.

Learning to use the Query Editor

Query Editor in Power BI Desktop is similar to the Power Query add-in capability in Excel 2013. While there are
several helpful articles in Power BI Support, you might also want to review the Power Query documentation on
support.office.com to get started.
You can get additional information from the Power Query Resource Center.
You can also view the Formula Reference.

Data types in Query Editor

When using Query Editor in Power BI Desktop to load data, we do a best guess data type detection. When using
formulas, sometimes data type settings on columns are not preserved. You should check the data type of columns
are correct after doing the following operations: Load data initially to the query tab, First Row as Header, Add
column, Group by, Merge, Append, and before pressing loading the data for the first time.
One key thing to remember: italics in the data grid do not mean the data type is correctly set, it just means the data
is not considered as Text.

Reference queries in the Query Editor

In Query Editor's navigator in Power BI Desktop, when you right click one of the queries, an option for "Reference"
is available. This is useful for the following reason:
When you use files as the data source for a query, the absolute path to the file is stored in the query. When
sharing or moving Power BI Desktop file or Excel workbook, you'll save time when you update the paths by
updating it just once rather than the paths.
By default all queries load to either an Excel worksheet or the data model (or both). Some queries are intermediary
steps and not intended for end-users. When referencing queries as mentioned above, this is often the case. You can
control query loading behavior by right clicking the query in the navigator and toggling the "Enable Load" option.
When "Enable Load" does not have a checkmark next to it, the query is still be available in the query tab and you
can use it with other queries. It is especially useful in combination with Merge, Append, and Reference transforms.
However since the query results are not loaded to the data model, the query will not clutter your reports field list
or your data model.

Scatter charts need a point identifier

Taking an example of a simple table of Temperatures and the Time the reading was taken. If you plot this directly
on a scatter chart, Power BI aggregates all the values into a single point. To show individual data points you'll to
add a field to the Details bucket in the field well. A simple way to do this in Power BI Desktop is on the query tab by
using the "Add index column" option on the "Add Column" ribbon.
Reference lines in your report
You can use a calculated column in Power BI Desktop to define a reference line. Identify the table and column on
which you want to create a reference line. Select "New Column" in the ribbon and, in the formula bar, type the
following formula:

Target Value = 100

This calculated column will return the value 100 regardless of where it is used. Your new column will show up in
the Field List. Add the Target Value calculated column to a line chart to show how any series relates to that specific
reference line.

Sort by another column

When you use a categorical (string) value in Power BI for chart axes or in a slicer or filter, the default order is
alphabetical. If you need to override this order, for example for things like days of the week or months, then you can
tell Power BI Desktop to sort by a different column.To learn more, see Sort by Column in Power BI Desktop.

Building maps more easily with hints to Bing

Power BI integrates with Bing to provide default map coordinates (a process called geo-coding) so it's easier for
you to create maps. Bing uses some algorithms and hints to try to get the right location, but it's a best guess. To
increase the likelihood of correct geo-coding, you can use the following tips:
When you create a map, you're often looking to plot countries, states, and cities. In Power BI Desktop, if you name
columns after the geographic designation it will help Bing guess what you're looking to display. For example, if you
have a field of US state names such as "California" and "Washington", Bing might return the location of
Washington, DC instead of Washington State for the word "Washington". Naming the column "State" will improve
the geocoding. The same goes for columns named "Country" and "City".
Some designations are ambiguous when considered in the context of multiple countries/regions. In some cases
what one country/region considers a 'state' is treated as a 'province' or a 'county' or some other designation. You
can increase the accuracy of geo-coding by building columns that append multiple fields together and use those for
plotting data locations. An example would be instead of passing only "Wiltshire", you can pass "Wiltshire, England"
to get a more accurate geo-coding result.
You can always provide specific latitude and longitude locations in Power BI service or Desktop. When you do this,
you'll also need to pass a Location field, otherwise the data is aggregated by default, so the location of the latitude
and longitude may not match what you expected.

Categorizing geographic fields to hint Bing's geocoding

Another way to ensure fields are correctly geocoded is by setting the Data Category on the data fields. In Power BI
Desktop, select the desired table, go to the Advanced ribbon and then set the Data Category to Address, City,
Continent, Country/Region, Country, Postal Code, State or Province. These data categories help Bing to correctly
encode the data. To learn more, see Data categorization in Power BI Desktop.

Better geocoding with more specific locations

Sometimes, even setting the data categories for mapping is insufficient. Build a more specific location like a street
address using the Query Editor in Power BI Desktop. Use the Add Column feature to build a custom column. Then
build the desired location as follows:
 = [Field1] & " " & [Field2]

Then use this resulting field in the map visualizations. This is very useful for building street addresses from
shipping address fields that are common in data sets. One note is that the concatenation only works with text fields.
If needed, convert the street number to a text data type before using it to build an address.

Histograms in the query stage

There are several ways to build histograms in Power BI Desktop, we'll start with the simplest and go from there:
Simplest Histograms - Determine which query has the field you want to build a histogram on. Use the "Reference"
option for the query to create a new query and name it "FieldName Histogram". Use the "Group by" option in the
"Transform" ribbon and select the "count rows" aggregate. Ensure the data type is a number for the resulting
aggregate column. Then visualize this data on the reports page. This is fast and easy to build, but doesn't work well
if you have many data points and does not allow brushing across visuals.
Defining buckets to build a histogram - Determine which query has the field you want to build a histogram on. Use
the "Reference" option for the query to create a new query and name it "FieldName". Now define the buckets with
a rule. Use the Add Custom Column option on the Add Column ribbon and build a custom rule. A simple
bucketing rule might look like this:

if([FieldName] \< 2) then "\<2 min" else

if([FieldName] \< 5) then "\<5 min" else
if([FieldName] \< 10) then "\<10 min" else
if([FieldName] \< 30) then "\<30 min" else
"longer")

Ensure the data type is a number for the resulting aggregate column. Now you can use the group by technique
described in Simplest Histogram to achieve the histogram. This option handles more data points but still does not
help with brushing.
Defining a histogram that supports brushing - Brushing is when visuals are linked together so that when a user
selects a data point in one visual other visuals on the report page highlight or filter data points related to the
selected data point. Since we're manipulating data at query time, we will need to create a relationship between
tables and ensure we know which detail item relates to the bucket in the histogram and vice-versa.
Start the process by using the "Reference" option on the query that has the field you want to build a histogram on.
Name the new query "Buckets". For this example let's call the original query "Details". Next remove all columns
except the column you'll use as the bucket for the histogram. Now use the "Remove Duplicates" feature in query,
it's on the right click menu when you select the column, so the remaining values are the unique values in the
column. If you have decimal numbers you can first use the tip for defining buckets to build a histogram to get a
manageable set of buckets. Now, check the data shown in the query preview. If you see blank values or null you'll
need to fix those up before creating a relationship. See "Creating a relationship if my data has null or blank values".
Using this approach can be problematic due to the need to sort. To get the buckets to sort correctly, see "Sorting
order: make categories appear in the order I want".

NOTE
It's useful to think about the sort order before building any visuals.

Next step in the process is to define a relationship between the "Buckets" and "Details" queries on the buckets
column. In Power BI Desktop, click Manage Relationships in the ribbon. Create a relationsship where Buckets is
in the left table and Details in on the right table and select the field you're using for the histogram.
Last step is to create the histogram. Drag the Bucket field from the "Buckets" table. Remove the default field from
the resulting column chart. Now from the "Details" table drag the histogram field into the same visual. In the field
well, change the default aggregate to Count. The result is the histogram. If you create another visual like a treemap
from the Details table, select a data point in treemap to see the histogram highlight and show the histogram for the
selected data point relative to the trend for the entire data set.

Histograms
In Power BI Desktop, you can use a calculated field to define a Histogram. Identify the table and column on which
you want to create a histogram. In the calculation area, type the following formula:

Frequency:=COUNTROWS (<Column Name>)

Save your changes and return to your report. Add the <Column Name> and the Frequency to a table then convert
to a bar chart. Ensure the <Column Name> is on the x-axis and the calculated field Frequency is on the y-axis.

Tips and tricks for creating relationships in Power BI Desktop

Often when loading detail data sets from multiple sources, issues like null values, blank values, or duplicate values
prevent you from creating relationships.
Let's look at an example:
If we load data sets from of active customer support requests and another data set of work items that have
schemas as follows:

CustomerInicdents: {IncidentID, CustomerName, IssueName, OpenedDate, Status} WorkItems: {WorkItemID,

IncidentID, WorkItemName, OpenedDate, Status, CustomerName }

When we want to track all incidents and workitems that relate to a specific a CustomerName we cannot simply
create a relationship between these two data sets. Some WorkItems may not be related to a CustomerName, so
that field would be blank or NULL. There might be multiple records in WorkItems and CustomerIncidents for any
given CustomerName.
Creating relationships in Power BI Desktop when the data has null or blank values
Often data sets contain columns with null or blank values. This can cause problems when trying to use
relationships. You have essentially two options for addressing the issues. You can remove the rows that have null or
blank values. You can do this using either the filter feature in the query tab or if you're merging queries, select the
"keep only matching rows" option. Alternatively, you can replace the null or blank values with values that work in
relationships, typically strings like "NULL" and "(Blank)". There's no right approach here - Filtering out rows at the
query stage removes rows and can affect summary statistics and calculations. The latter approach preserves that
data rows but can make unrelated rows appear related in the model leading to miscalculations. If you adopt the
latter solution ensure you use filters at the View/Chart where appropriate to ensure you're getting accurate results.
Most importantly, evaluate which rows are kept/removed and understand overall impact on the analysis..
Creating relationships in Power BI Desktop when the data has duplicate values
Often when loading detailed data sets from multiple sources, duplicate data values prevent you from creating
relationships. You can overcome this by creating a dimension table with the unique values from both data sets.
Let's look at an example:
If we load data sets from of active customer support requests and another data set of work items that have
schemas as follows:

CustomerInicdents: {IncidentID, CustomerName, IssueName, OpenedDate, Status} WorkItems: {WorkItemID,

 IncidentID, WorkItemName, OpenedDate, Status, CustomerName }

When we want to track all incidents and workitems that relate to a specific CustomerName we cannot simply
create a relationship between these two data sets. Some WorkItems may not be related to a CustomerName, so
that field would be blank or NULL. If you have any blank values or null in the CustomerNames table, you might
still not be able to create a relationship - see Creating relationships if my data has null or blank values. There might
be multiple WorkItems and CustomerIncidents for a single CustomerName.
To create a relationship in this case, we need to create a logical data set of all the CustomerNames across the two
data sets. In the Query tab, you can use the following sequence to create the logical data set:
1. Duplicate both queries, naming the first Temp and the second CustomerNames.
2. In each query, remove all columns except the CustomerName column
3. In each query, use Remove Duplicate.
4. In the CustomerNames query, select the Append option in the ribbon, select the query Temp.
5. In the CustomerNames query, select Remove Duplicates.
Now you have a dimension table that you can use to relate to CustomerIncidents and WorkItems that contains all
the values of each.

Patterns to jump start your use of the Query Editor

Query Editor is very powerful in how it can manipulate data to shape and clean it so it is ready to be visualized or
modeled. There are a few patterns you should be aware of.
Temporary columns can be deleted after computing a result
Often you need to build a calculation in Power BI Desktop that transforms data from multiple columns into single
new column. This can be complex. One easy way to overcome the problem is do decompose the operation into
steps. Start by duplicating the initial columns. Then build the steps a temporary columns. Then create the a column
for the final result. You can then delete the temporary columns so the final data set is not cluttered. This is possible
because the query tab executes steps in order.
Duplicate or Reference queries followed by merge to original query
Sometimes it's useful to compute summary statistics for a data set. The easy way to do this is to duplicate or
reference the query in the query tab. Then use Group by to compute the summary statistics. Summary statistics
help you normalize the data in the original data so they're more comparable as in . This is especially useful for
comparing individual values to the whole. To do this go to the original query, and select the merge option. Then
merge the data from the summary statistics query matching on the appropriate identifiers. Now you're ready to
normalize the data as needed for your analysis.

Using DAX for the first time

DAX is the calculations formula language in Power BI Desktop. It's optimized for BI analytics. It's a little different
than what you might be familiar with if you've only used a SQL like query language. There are very good resources
online and in literature for learning DAX.
Learn DAX Basics in Power BI Desktop
Data Analysis Expressions (DAX) Reference
DAX Resource Center
 Visualizations in Power BI reports
1/14/2019 • 2 minutes to read • Edit Online

Visualizations (aka visuals) display insights that have been discovered in the data. A Power BI report might have
a single page with one visual or it might have pages full of visuals. In Power BI service, visuals can be pinned
from reports to dashboards.
It's important to make the distinction between report creators and report consumers If you are the person
building or modifying the report, then you are a creator. Creators have edit permissions to the report and its
underlying dataset. In Power BI Desktop, this means you can open the dataset in Data view and create visuals in
Report view. In Power BI service, this means you can open the dataset or report in the report editor in Editing
view. If a report or dashboard has been shared with you , you are a report consumer. You'll be able to view and
interact with the report and its visuals but you won't be able to save changes.
There are many different visual types available directly from the Power BI VISUALIZATIONS pane.

And for even more choices, visit the Microsoft AppSource community site to find and download custom visuals
provided by Microsoft and the community.
https://www.youtube.com/embed/SYk_gWrtKvM?list=PL1N57mwBHtN0JFoKSR0n-tBkUJHeMP2cP
If you're new to Power BI, or need a refresher, use the links below to learn the basics of Power BI visualizations.
Alternately, use our Table of Contents (along the left side of this article) to find even more helpful information.

Add a visualization in Power BI

Create visualizations on the pages of your reports. Browse the list of available visualizations and available
visualization tutorials.

Upload a custom visualization and use it in Power BI

Add a custom visualization that you created yourself or that you found in the Microsoft AppSource community
site. Feeling creative? Dig into our source code and use our developer tools to create a new visualization type
and share it with the community. To learn more about developing a custom visual, visit Developing a Power BI
custom visual.

Change the visualization type

Try changing the type of visualization to see which works best with your data.

Pin the visualization

In Power BI service, when you have the visualization the way you want it, you can pin it to a dashboard as a tile.
If you change the visualization being used in the report after you pin it, the tile on the dashboard doesn't change
-- if it was a line chart, it stays a line chart, even if you changed it to a Doughnut chart in the report.

Next steps
Visualization types in Power BI
Custom visuals
 Best design practices for reports and visuals
1/14/2019 • 47 minutes to read • Edit Online

We’ve released a new and improved navigation and content experience for Power BI, and we’re in the process of
updating all of our documentation. The information and screenshots on this page may not match what you see on
your screen. For more information see Navigating Power BI service.

Introduction
This paper provides best practices for designing reports in Power BI. Starting with planning, it discusses principles
of design that you can apply to your reports and to the pages and individual visuals that make up that report.
Many of these best practices apply to dashboard design as well.
We hope this paper will be a jumping-off point for you and that you’ll apply what you learn to your own reports
and visualizations and that you’ll continue the conversation on community.powerbi.com. BI report design and
visualization usage is a hot topic right now and there are many thought leaders, bloggers, and websites that look at
this topic in breadth and depth (we’ve listed a few at the end).

NOTE
The recommendations made in this white paper are guidelines for you to apply when and where it makes sense. For every
principle we describe below, there are usually valid reasons to “break the rule.”

We are overwhelmed by information, not because there is too much, but because we don't know how to tame it. --
Stephen Few

A look at the landscape and terminology

In Power BI, a report can have one or more report pages and all the pages together are collectively referred to as
the report. The basic elements of the report are visuals (aka visualizations), standalone images, and text boxes.
From the individual data points, to the report elements, to the report page itself, there are innumerable formatting
options.
We’ll start at the report planning stage, continue on to basic report design principles, then discuss visual design
principles, and finish with a discussion of best practices for individual visual types.
In-depth guidance and instructions for creating and using Power BI reports is available at powerbi.com > Learn.

Before you build your first visualization…focus on requirements

Creating a report starts before you build your first visual because a good report needs planning. Know what data
you have to work with and write down the requirements for the report. Ask yourself “What is the business need,
how is this data going to be used, and by whom?” A key question is “what decisions does the reader want to be
able to make based on this report?”
The answer to those questions will drive your design. Every report tells a story. Make sure that story matches the
business need. It may be tempting to add visuals that show dramatic insights, but if those insights don’t match the
business need, then the report won’t be useful – and in fact your users might be distracted by those visuals. Also,
you may find that the information needed to make that decision cannot be gleaned from this data. Can this report
be used to measure what is needed?
Reports can be used to monitor, uncover, track, predict, measure, manage, test, and more. If, for example, the
business need is a sales report that measures performance, then you might design a report that looks at current
sales, compares it to previous sales, compares to competitors, and includes some KPIs that trigger alerts. Perhaps
readers can drill down into the sales numbers to see store closures or supply chain issues that may be impacting
sales. Another drill down might be the ability to look at sales by store, region, product, season, and more.
Know the customers for the report and design a report that uses familiar terminology and provides data at a level
of detail and complexity on par with the customers’ level of knowledge. Have more than one type of customer?
One size doesn’t always fit all; design separate report pages based on expertise and be sure to label each page
clearly so customers can self-identify. Another option is to use slicers so customers can tailor the page to fit them.
Involve the customer in the planning stage and avoid the mistake of building what you think they need. Be
prepared to start over and to iterate.
Once you’ve identified the business need, the customers, and the metrics you’d like to include, the next step is to
pick the right visuals to tell the story and present those visuals in the most-effective way possible. That covers a lot
of ground, and we’ll start with some basic principles of report design.

Principles of report design

A report page has limited space and one of the hardest things is to fit all the elements you want into that space –
and still have that information be easily understood. And don’t underplay the value of “pretty.” The key is to find
the balance between pretty and useful.
Let’s take a look at layout, clarity, and aesthetics.
Layout - the report canvas
The report canvas has a finite amount of space. If you can’t fit all the elements on a single report page, break the
report up into pages. A report page can be tailored to a specific audience (e.g., HR, IT, Sales, SLT), or to a specific
business question (e.g., How are defects impacting our downtime?, What is our Marketing campaign’s impact on
Sentiment?) or as a progressive story (e.g. first page as overview or attention-grabbing “hook”, 2nd page continues
the data story, 3rd page dives deeper into the story, etc.). If your entire report fits on a single page, great. If it
doesn’t, create separate report pages that logically chunk the content. And don’t forget to give the pages
meaningful and helpful names.
Think about filling an art gallery. You wouldn’t put 50 pieces of artwork into a small room, fill it with chairs and
paint each wall a different color. As the curator, you’d choose just pieces that have a common theme, lay them out
around the room with plenty of space for visitors to move and think, and place informational cards that describes
what they’re looking at. And there’s a reason most modern galleries have plain walls! For this article, we’ll start
with a report example that needs a lot of work. As we apply our best practices and principles of design, our report
will improve.
Figure 1: This ugly report page needs a lot of work
The example above has many space-related (layout) design issues that we’ll discuss below:
alignment, order, and use of proximity
poor use of space and sorting
clutter
Alignment, order, and proximity
The layout of your report elements impacts comprehension and guides the reader through the report page. How
you place and position elements tells a story. The story might be “start here and then look here” or “these 3
elements are related to each other.”
In most cultures, people scan from left to right and top to bottom. Position the most important element in the
top left corner of your report. And organize the rest of the visuals in a way that leads to logical navigation and
comprehension of the information.
Position elements that require the reader to make a choice to the left of the visualizations the choice will impact:
slicers, for example.
Position related elements close to each other; proximity implies the elements are related.
Another way to convey relationships is to add a border or color background around related elements.
Conversely, add a divider to distinguish between different sections of a report.
Use white space to visually chunk sections of the report page.
Fill the report page. If you find that you have a lot of extra white space, make your visualizations larger or make
the canvas smaller.
Be intentional with sizing your report elements. Don’t let space availability dictate the size of a visualization.
Make important elements larger than the others or add a visual element like an arrow to draw attention.
Align the elements on the report page, either symmetrically or intentionally asymmetrically.
Let’s take a closer look at alignment.
Alignment
Alignment doesn’t mean that the different components need to be the same size or that you must have the same
number of components on each row of the report. It just means that there is a structure to the page that aids in
navigation and readability.
We can see in our updated report below that the report components are now aligned on the left and right edges
and each report row is aligned horizontally and vertically as well. Our slicers are to the left of the visuals they
impact.
Figure 2: Our ugly report example improved with layout edits
Power BI includes tools to help you align your visuals. In Power BI Desktop, with multiple visuals selected, you can
use the Align and Distribute options on the Visuals ribbon tab to match up the position of visuals.

Figure 3: Align visuals in Power BI Desktop

In Power BI online and Power BI Desktop, you also have precise control over the size and position of visuals
through the General tab on the formatting pane for all visuals:
Figure 4: Set exact position for your visual
In our example report page (Figure 2), the 2 cards and large border are aligned on the X Position at 200.
Fit to the space
Make the best use of the space you have. If you know how the report will be viewed/displayed, design with that in
mind. Reduce empty space to fill the canvas. Do all you can to eliminate the need for scrollbars on individual
visuals. Fill the space without making the visuals seem cramped.
A d j u st t h e p a g e si z e

By reducing the page size, individual elements become larger relative to the overall page. Do this by deselecting
any visuals on the page and using the Page Size tab in the formatting pane.
Here is a report page using page size 4:3 and then using 16:9. Notice how the layout suits 16:9 so much better.
There is even enough room to remove the scrollbar from the second visual.

Figure 5a: The report at 4:3 page size

Figure 5b: The report at 16:9 page size ratio
Will your report be viewed 4:3, 16:9 or another ratio? On small screens or huge screens? Or on all possible screen
ratios and sizes? Design with this in mind.
Our example report page seems a bit cramped. With no visual selected, open the formatting pane by selecting the
paintroller icon. Expand Page Size and change Height to 900.

Figure 6: Increase page height

Reduce clutter
A cluttered report page will be hard to understand at-a-glance and may be so overwhelming that readers won’t
even try. Get rid of all report elements that aren’t necessary. Don’t add bells-and-whistles that don’t help
comprehension or navigation. Your report page needs to convey the information as clearly and quickly and
cohesively as it can.
Edward Tufte calls it “data to ink ratio” in his book The Visual Display of Quantitative Information. Basically,
remove anything that isn’t essential.
The clutter you remove will increase the whitespace on your report page and give you more real estate for
applying the best practices we learned about above in the “Alignment, order, and proximity” section.
Here our example is already looking better. We’ve removed lots of clutter and added shapes to group elements
together. The background image is gone, the unnecessary arrow shape and text box are gone, one visual has been
moved to another page in the report, etc. We’ve also lengthened the page size to increase white (yellow?) space.
Figure 7: Our ugly report example de-cluttered
Tell a story at a glance
The overall test should be that somebody without any prior knowledge can quickly understand the report without
any explanation from anybody. With a quick glance, readers should be able to quickly see what the page is about
and what each chart/table is about.
When readers look at your report, their eyes should be drawn to the element you want them to look at first and
their eyes will then continue left-right-top-down. Change this behavior by adding visual cues like text box labels,
shapes, borders, size, and color.
Text boxes
Sometimes the titles on visualizations aren’t enough to tell the story. Add text boxes to communicate with the
people viewing your reports. Text boxes can describe the report page, a grouping of visuals, or describe an
individual visual. They can explain results or better-define a visual, components in the visual, or relationships
between visuals. Text boxes can be used to draw attention based on different criteria called out in the text box.
In Power BI service, from the top menubar, select Text Box. (In Power BI Desktop, select Text Box from the Insert
area of the ribbon.)

Figure 8: Add a text box

Type in the empty box and then use the controls at the bottom to set font face, size, alignment, and more. Use the
handles to resize the box.
Figure 9: Format the text box
But don’t overdo it! Too much text on a report is distracting and detracting from the visuals. If you find that your
report page requires a ton of text to make it understandable, then start over. Can you pick a different visual that
tells a better story on its own? Can you tweak the visual’s native titles to make it more intelligible?
Text
Create a text style guide and apply it to all pages of your report. Pick just a few font faces, text sizes, and colors.
Apply this style guide to not only textual elements but to the font choices you make within your visualizations (see
Titles and labels that are part of the visualizations, below ). Set rules for when you’ll use bold, italics, increased font
size, certain colors, and more. Try to avoid using all capitalization or underlining.
Shapes
Shapes too can aid navigation and comprehension. Use shapes to group related information together, highlight
important data, and use arrows to direct the eye. Shapes help readers understand where to start and how to
interpret your report. In design terms, this is often referred to as contrast.

Figure 10a: Shapes in Power BI service

Figure 10b: Shapes in Power BI Desktop
What does our example page look like now? Figure 11 shows a cleaner, less cluttered page with a consistent use of
text faces, fonts, and colors. Our page title in the top-left corner tells us what the page is all about.

Figure 11: Our report example with text guidelines applied and title added
In our example, a report page title was added in the top left corner; the first place readers look. Font size is 28 and
font is Segoe Bold to help it stand out from the rest of the page. Our text style guide calls for no backgrounds,
black titles, legends, and labels and that was applied to all visuals on the page, where possible (the Combo chart
axes and labels are not editable). Additionally:
Cards: Category label set to Off, Title turned On and set to 12pt black centered.
Visual titles: if turned On, set to 12pt and left-aligned.
Slicers: Header set to Off, Title turned On. Leave Items > Text grey and 10pt.
Scatter and column charts: black font for X and Y axes and X and Y axes titles, if used.
Color
Use color for consistency. We’ll talk more about color in Principles of visual design, below. But here we’re referring
to being deliberate in your selection of color so that it doesn’t detract from your readers being able to quickly
understand your report. Too many bright colors barrage the senses. This section is more what not to do with color.
Backgrounds
When setting backgrounds for report pages, choose colors that don’t overshadow the report, clash with other
colors on the page, or generally hurt the eyes. Realize that some colors have inherent meaning. For example, in the
US, red in a report is typically interpreted as “bad”.

Figure 12: Set report background

You’re not creating a work of art, but a functional report. Choose a color that improves the readability and
prominence of the report elements.
A study on the use of color and visualizations within Web pages found that higher contrast between colors
increases the speed of comprehension (The effect of text and background colour on visual search of Web pages
and Determining Users’ Perception of Web Page Visual Complexity and Aesthetic Characteristics.)
We’ve applied some color best practices to our example report (Figure 20 and 21) below. The most-notable was
that we changed the background color to black. The yellow was too bright and strained our eyes. Also, on the
“Count of athlete name by year and class” chart, the yellow portion of the bars disappeared into the yellow
background. Using a black (or white) background gives us maximum contrast and makes the visuals the focus of
attention.
Here are the additional steps we took to improve the example report:
Page title
When we changed the background to black, our title disappeared because the text box field only allows black font.
To fix this, add a text box title instead. With the text box selected, erase the text and in the Visualizations tab, select
Title and turn it On. Select the arrow to expand the Title options, type Summer Olympic Games into the Title
Text field and select white Font color.

Figure 13: Add a page title

Cards
For the card visuals, open the formatting pane (paint roller icon) and turn Background On. Select white with a
transparency of 0%. Then turn Title On, select Font color white and Background color black.
Slicers
Up to this point the two slicers had different formatting, which doesn't make design sense. For both slicers, change
the background color to aqua. Aqua is a good choice because it is part of the page’s color palette – you can see it in
the filled map, tree map, and column chart.

Figure 14: Change slicer background color

Add a thin white border.

Figure 15: Add a border to the slicer

The grey font is hard to see against the aqua, so change the Items color to white.

Figure 16: Change slicer font color

And, finally, under Title, change Font color to white and add a black Background color.
Figure 17: Format slicer title
Rectangle shape
The rectangle too has disappeared into the black background. To fix this, select the shape and in the Format shape
pane, turn Background On.

Figure 18: Format the shape

Column charts, bubble chart, filled map, and tree map
Add a white background to the remaining visuals on the report page. From the formatting pane, expand the Line
option and set the Line Color to white and Weight to 3.

Figure 19: Add a white background to remaining visualizations

Figure 20: Report example with color best practices applied (black background)

Figure 21: Report example with color best practices applied (white background)  
Aesthetics
Much of what we would consider aesthetics has already been discussed above: things like alignment, color, font
choices, clutter. But there are a few more best practices for report design worth discussing and these deal with the
overall appearance of the report.
Remember that the function of your report is to meet a business need; not to be pretty. But some level of beauty is
required, especially when it comes to first impressions. Nashville consultant Tony Bodoh explains "Emotion fires a
half-second before logic can kick in." Readers will first react at an emotional level to your report page, before they
take more time to dig deeper. If your page looks disorganized, confusing, unprofessional…your reader may never
discover the powerful story it tells.
TDI blogger and TechTarget industry analyst Wayne Eckerson has a great analogy. Designing a report is like
decorating a room. Over time you purchase a vase, a sofa, end table, a painting. Separately you like all of these
elements. But although each individual selection makes sense, collectively the objects clash or compete for
attention.
Concentrate on:
Creating a common theme or look for your report, and apply it to all pages of the report
Using standalone images and other graphics to support and not detract from the real story
And applying all the best practices we discussed up to this point in the article.

Principles of visual design

We’ve looked at the principles of report design; how to organize the report elements in a way that makes the
report easy to quickly grasp. Now we’ll look at design principles for visuals themselves. And, in the next section,
we’ll dig down into individual visuals and discuss best practices for some of the more commonly-used types.
In this section, we’re going to leave our example report page alone for a while and look at other examples. After
we’ve gone through the principles of visual design, we’ll return to our example report page and apply what we’ve
learned (with step-by-step instructions).
Planning – choose the right visual
Just as it’s important to plan out your report before you start building, each visual also requires planning. Ask
yourself “what story am I trying to tell with this visual?” And then figure out which visual type will tell the story
best. You could show progress through a sales cycle as a bar chart but wouldn’t a waterfall or funnel chart tell it
better? For help with this, read the last section of this paper “Visual types and best practices” which describes best
practices for some of the more-common types. Don’t be surprised if the first visual type you pick doesn’t end up
being your best option. Try more than one visual type to see which one makes the point best.
Understand the difference between categorical and quantitative data and know which visual types work best with
what type of data. Quantitative data is often referred to as measures and it’s typically numeric. Categorical data is
often referred to as dimensions and can be classified. This is discussed in more depth in “Choose the right
measure”, below.
Avoid the temptation to use fancy or more-complex visual types just to make your report look more impressive.
What you want is the most-simple option for conveying your story. Horizontal bar charts and simple line charts
can convey information quickly. They are familiar and comfortable and most readers can interpret them easily. An
added advantage is that most people read left-to-right and top-to-bottom and these two chart types can therefore
be scanned and comprehended quickly.
Does your visual require scrolling to tell the story? Avoid scrolling if you can. Try applying filters and making use of
hierarchies/drilldown, and if those don’t eliminate the scrollbar, consider choosing a different visual type. If you
can’t escape scrolling, horizontal scrolling is tolerated better than vertical scrolling.
Even when you choose the absolutely-best visual for the story, you might still need help telling the story. That’s
where labels, titles, menus, color, and size come in. We’ll discuss these design elements later in the section titled
“Design elements”.
Choose the right measure
Is the story your visual telling compelling? Does it matter? Don’t build visuals for the sake of building visuals.
Maybe you thought the data would tell an interesting story, but it doesn’t. Don’t be afraid to start over and look for
a more-interesting story. Or, maybe the story is there but it needs to be measured in a different way.
For example, say you want to measure the success of your sales managers. What measure would you use to do
this? Would you measure that best by looking at total sales or total profit, growth over previous year or
performance against a target goal? Salesperson Sally might have the largest profit, and if you showed total profit
by salesperson in a bar chart, she would look like a rockstar compared to the other salespeople. But if Sally has a
high cost of sales (travel expenses, shipping costs, manufacturing costs, etc.), simply looking at sales doesn’t tell the
best story.
Reflect reality/don’t distort reality
It’s possible to build a visual that distorts the truth. There’s a website where data enthusiasts share “bad” visuals.
And the common theme in the comments is disappointment in the company that created and distributed that
visual. It sends the message that they can’t be trusted.
So create visuals that don’t intentionally distort reality and that aren’t manipulated to tell the story you want them
to tell. Here is an example:

Figure 22: Distorted reality chart

In this example, it appears as if there is a big difference between the 4 companies, and that CorpB is way more
successful than the other 3. But notice that the X axis doesn’t start at zero and that the differences between the
companies is likely within the margin of error. Here’s the same data with an X axis that does start at zero.

Figure 23: Realistic chart

Readers expect and often assume the X axis is starting at zero. If you decide to not start at zero, do so in a way that
doesn’t distort the results and consider adding a visual cue or text box to point out the deviation from the norm.
Design elements
Once you’ve selected a type and measure and created the visual, it’s time to fine-tune the display for maximum
effectiveness. This section covers:
Layout, space, and size
Text elements: labels, annotations, menus, titles
Sorting
Visual interaction
Color
Tweaking visuals for best use of space
If you’re trying to fit multiple charts into a report, maximizing your data-ink ratio will help make the story in your
data stand out. As mentioned above, Edward Tufte coined ‘data-ink’ ratio: the goal is remove as many marks from
a chart as possible without impairing a reader’s ability to interpret the data.
In the first set of charts below, there are redundant axis labels (Jan 2014, Apr 2014 etc.) and titles (“by Date”). The
titles for each chart also require dedicated horizontal space across each chart. By removing the chart titles and
turning on individual axis labels we remove some ink and have better use of the overall space. We can remove the
axis labels for the top two charts to further reduce ink and use more of the space for data.
If there were particular time periods that you wanted to call out, you could draw lines or rectangles behind all the
charts to help draw the eye up and down to aid comparisons.

Figure 24: Before

Figure 25: After

To turn axis titles on and off
Select the visual to make it active and open the Formatting pane. Expand the options for the X-axis or Y -axis and
drag the slider for Title on or off.
Figure 26: Turn axis titles on and off
To turn axis labels on and off
Select the visual to make it active and open the Formatting pane. Next to X-Axis and Y -Axis are sliders. Drag the
slider to turn axis labels on or off.

Figure 27: Turn axis labels on and off

TIP
One scenario where you might turn Y-axis labels off would be if you had Data labels turned on.

To remove visual titles

Select the visual to make it active and open the Formatting pane. Set the slider for Title to Off.

Figure 28: Remove titles from visuals

Consider how your readers will be viewing the report and ensure your visuals and text are large enough and dark
enough to be read. If you have a proportionally-larger visual on the page, readers may assume it’s the most
important. Put enough space between the visuals that your report doesn’t look cluttered and confusing. Align your
visuals to help direct the eyes of your readers.
To resize a visual
Select the visual to make it active. Grab and drag one of the handles to adjust the size.
Figure 29: Resize visual
To move a visual
Select the visual to make it active. Select and hold the gripper bar at the top middle of the visual and drag the
visual to its new location.

Figure 30: Move a visual

Titles and labels that are part of the visualizations
Ensure titles and labels are readable and self-explanatory. Text in titles and labels must be an optimal size with
colors that stand out (such as black instead of the default grey). Remember our style guide (see "Text" above)?
Limit the number of colors and sizes -- too many different font sizes and colors make the page look busy and
confusing. Consider using the same font color and size for the title of all visuals on a report page and choose the
same alignment for all titles on a report page.
The formatting pane
For each of the formatting adjustments listed below, select the paint roller icon to open the Formatting pane.

Figure 31: Open the Formatting pane

Then select the visual element to adjust and make sure it is set to On. Examples of visual elements are: X-Axis, Y -
Axis, Title, Data labels, and Legend. The example below shows the Title element.
Figure 32: Format a visual title
Set the text size
Text size can be adjusted for titles and data labels, but not for X or Y axes or legends. For data labels specifically,
play with the Display units and number of Decimal Places until you find the optimal level of detail for
displaying on your report.
Set the text alignment
The choices for title alignment are left, right, and center. Choose one and apply that same setting to all visuals on
the page.
Set the text position
Text position can be adjusted for some Y axes and for the legend. Whichever you choose, do the same for the other
Y axes and any other legend on the page.
Set the title and label length
Adjust the length of titles, axes titles, data labels, and legends. If you decide to display any of these elements,
adjusting the length (along with text size) ensures that nothing is truncated. For Title and Legend, the setting is
Title Text and this is where you type in the actual title that will appear on the visual. For X-Axis and Y -Axis, the
setting is Style and you select from a dropdown. For Data labels, the settings are Display and Decimal. Use the
Display dropdown to select the units of measurement: millions, thousands, none, auto, etc. Use the Decimal field
to tell Power BI how many decimal places to display.
Set the text color
Text color can be adjusted for titles, axes, and data labels.
Titles and labels that are not part of the visualizations
Earlier in this paper we discussed adding text boxes to report pages. Sometimes the titles on visualizations aren’t
enough to tell the story. Add text boxes to communicate additional information to the readers of your reports.
To keep your report page from looking too confusing or too busy, be consistent in your use of text box fonts, sizes,
colors, and alignment. To make an adjustment to the text in a text box, select the text box to reveal the formatting
menu.
Figure 33: Format the font used in a text box
Sorting
A really simple opportunity to provide faster insight is to set the sorting of visuals. For example, sorting bar charts
in descending or ascending order based on the value in the bars enables you to quickly show significant
incremental information without using more real estate.
To sort a chart, select the ellipses (…) in the top right of the chart, select Sort and choose the field you want to sort
by and the direction. For more information, see Change how a visual is sorted.
Chart interaction and interplay
One of the most compelling feature of Power BI is the ability to edit the way charts interact with each other. By
default, charts are cross-highlighted: when you select a data point, the related data of other charts light up and the
unrelated data dims. You can override this behavior to use any chart as a true filter which saves you real estate on
your page. To do this, select Visual Interactions from the menubar.

Figure 34: Visual interactions

Then, for each visual on the page, decide whether you want the selected visual to filter, highlight, or do nothing.
Not all visuals can be highlighted, and for those the highlight control won't be available. For more information, see
Visual interactions in Power BI.

TIP
For readers who’re new to Power BI, this ability to click and interact with reports may not be instantly obvious. Add text
boxes to help them understand what they can click on to find more insights.

The use of color in visuals

Earlier in this paper we talked about the importance of having a plan for how you’re going to use color across a
report. This section will have some overlap but primarily applies to how you use color in individual visuals. And the
same principles apply: use color to tie the report together, add emphasis to important data, and to improve the
reader’s comprehension of the visual. Too many different colors is distracting and makes it difficult for the reader
to know where to look. Don’t sacrifice comprehension for beauty. Only add color if it improves comprehension.

TIP
Know your audience and any inherent color rules. For example, in the United States, green typically means “good” and red
typically means “not good”.

This topic is broken down to cover:

1. Data color
2. Data label color
3. Color for categorical values
4. Color for numerical values
Use colors to highlight interesting data
The simplest way to use color is by changing one or more data point’s color to call attention to it. In this example,
the color changes when the Olympic games moved from a 4-year cycle to a 2-year cycle of alternating Summer
and Winter games.

Figure 35: Use color to tell a story

You can change data point colors from the Data colors tab in the formatting pane. To customize each data point
individually, make sure Show all is set to On.

Figure 36: Set data point colors

 NOTE
Power BI applies a default theme to your report visuals. The theme colors have been chosen to provide variety and contrast.
To divert from the default theme palette, select Custom color.

Figure 37: Choose a custom color

In Power BI Desktop, you can even highlight outliers or a section of a line by using a second series:

Figure 38: Using Desktop to plot outliers

Here, values in the ‘Outliers’ series only exist where the average August temperature drops below 60. This was
done by creating a DAX calculated column using this formula:
Outliers = if(Editions[Temp]<60, Editions[Temp], BLANK())
In our example, there were 3 outliers: 1952, 1956, and 2000.
Colors for labels and titles
As you explore all the formatting options available to you, you’ll find many different places to add color to titles
and legends. For example, you can change the color of data labels and axes titles. Proceed with caution. Generally,
you want to use a single color for all visual titles. As with all the guidelines in this paper, there are always situations
and reasons to “break the rules”, but if you do decide to break the rules, do it for a good reason.
Colors for categorical values
Charts with a series typically have a categorical value in the legend. For example, each color in the legend below
represents a different category of Country/Region.
Figure 39: Default colors applied
The colors Power BI uses by default were chosen to provide a good color separation between categorical values so
they are easy to distinguish. Sometimes people change these colors to match their corporate scheme etc. but it can
lead to problems.

Figure 40: Color applied as hues of a single color

By sticking to a single hue and varying the intensity of the color, this visual has introduced a false sense of ordering
between the categories. It implies the darker bubbles are higher or lower on some scale than the lighter hues.
Other than alphabetical, there’s normally no inherent order in this sort of categorical value. To change the default
colors, open the Formatting pane, and select Data colors.
Colors for numerical values
For fields that do have some inherent order and numerical value, you can also color data points by the value. This
can be helpful to show the spread of values across the data, and also allow for two variables to be shown on a
single chart. For example this chart makes it clear that although China has the highest medal count, Japan and
Thailand have participated in more Olympic games.

Figure 41: Color data points by the value

To create this chart, add a value to the Color saturation field and then adjust those colors in the Formatting pane.
Figure 42: Add a color saturation field

Figure 43: Adjust the colors used for saturation

Color can also be used to emphasize variance around a central value. For example, coloring positive values green
and negative values red. Be aware of cultural differences when assigning colors to positive or negative values; not
all cultures use red for bad and green for good!

Figure 44: Color to emphasize variance around central value  

Principles of visual design – applied to example report page
Now let’s take the visual principles discussed above and apply them to our sample report.
Before
Figure 45: Our example report (before)
After

Figure 46: Our example report (after)

What did we do?
1. Slicer: removed blanks from the slicers by adding a page level filter and selecting only gold, silver, bronze.
Changed Selection Controls to Off for Single Select and Select All.
2. Bubble: there are so many items in the legend that they scroll off the screen. Removed the legend and turned
on Category labels instead. Customers can hover over the bubbles to see the details. Shortened the title and
removed “by countryregion” since that seems self-evident. Turned axes labels On for both to make the chart
easier to understand.
3. Filled map: changed the Data colors to make it stand out more. Turned Diverging on and set the Minimum
to pink and the Maximum to red.
4. Tree map: removed filter which was set for only USA. Set the Data labels to 1 decimal place. The visual was
using the Class field which isn’t very useful since it will almost always be 33% (Gold/Silver/Bronze). Selected a
different more-interesting field, gender. Changed Aquatics to blue and Athletics to grey for design.
5. Top bar chart: shortened the title, removed data labels, turned legend title off. Changed word order of title to
match the chart below.
6. Bottom bar chart: sorted by year ascending to match chart above. Changed colors to match class. Changed title.
Turned off legend for more space for data. Turned on data labels which won't show up in the report (because
the visual is too small for the labels to be readable) but will show when the visual is opened in Focus mode.
Learn about Focus mode. Added Count of Event (Distinct) to Tooltips so now when you hover over a stacked
column, the tooltips also tell you how many events were contested that year.
7. Visual Interactions: turned off interactions for both cards since I always want them to show total games and
sports.

Visual types and best practices

Power BI provides many visual types natively. To these, add the custom visuals available from Microsoft and from
the Power BI community and total visual options become too numerous to document here. But let’s look at some
of the most-used native visual types.
Line charts

Line charts are a powerful way to look at data over time. Looking at data in tables doesn’t really take advantage of
the speed in which our eyes spot peaks, valleys, cycles, and patterns.
The example below shows the trends in the number of medals awarded and the number of athletes winning those
medals.

Figure 47: Line charts

Best practices
When people look at line charts, the first thing they see is the shape of the curve. This means that you need
to have an x-axis that makes the curve meaningful such a time or distribution categories. If you put
categorical fields like product or geography on the x-axis, the line chart will not be interesting as the shape
of the curve would provide no meaningful information.
If you choose to place multiple charts above and below each other like this, to make it easier to compare
across series, line up the X-axis. Use filters to make sure that the same range of values is shown. For
example, if you’re looking at date ranges, ensure they are the same date ranges. For example, 1896 to 2012
on both charts.
Make full use of the space. If it makes sense for your data, set the start and end points for the Y -axis to
eliminate empty space at the top and bottom of your chart and to focus in on the actual data points. To do
this, select the paint roller icon to open the Formatting pane. Expand the Y -Axis area and set the Start and
End points.

Figure 48: Set the start and end points

Another reason to explicitly set the Start and End points is if you’re comparing two or more charts on the
same page using the same Y -axis field. For example, if you’re looking at cumulative event counts, and the
United Kingdom has counts that range from 1 to 70 and Australia has counts that range from 1 to 12, the 2
line charts will display very different Y -axes (Figure x). This makes it difficult to compare at a glance. Instead,
set the charts to use the same Y -axis range (Figure x).

Figure 49:Line charts with different y-axes

 Figure 50:Line charts with matching y-axes
For more information, see:
Customize the X and Y axes
Line charts and irregular intervals
Line charts 101
Bar/Column Charts

If line charts are the standard for looking at data over time, bar charts are the standard for looking at a specific
value across different categories. If you sort the bars based on the number, you will instantly see the top values and
distribution. Horizontal bar charts work well with long-ish labels.
Figure 51: Horizontal bar chart
Best practices
Display data labels for values. This makes it easier to identify specific values. To do this, open the Formatting
pane, and set Data labels to On.
 Figure 52: Turn on data labels
The bar chart above is really useful to compare one measure against many at a single point in time.
While the line chart above showed us the trend over time, the bar chart shows us the trend for a single
category at a specific point in time. At a glance, our bar chart shows us Spain has one of the worst
unemployment rates in the world, at 25%.
When an entire Bar/Column chart doesn’t fit into the allotted space, Power BI adds scrollbars. When
possible, and if it makes sense, structure the visual and report to show the entire chart so the reader gets an
overview of the entire distribution. Unfortunately this is not possible in our example given the significant
number of countries around the world.
One way to limit the values included is to use a filter. For example, add a Visual level filter that shows the
country only if unemployment rate is above 20%.
Bar/Column charts can be drilled down (and back up again). This is a great way to pack more information
into a visual without taking up more real estate. The example below has a hierarchy for Regions >
Countries. Double-clicking a region bar drills down to the countries that make up that region. For more
information on drill, see Drill down in a visualization.

Figure 53: Drill down

For more details on Bar and Column charts:
Bar charts 101
Data Visualization Catalogue: Bar Chart
Data Visualization Catalogue: Multi-set Bar Chart
Stacked Bar/Column Charts

Add another dimension to your bar/column charts by stacking different categories within the bar or column. Now
the chart conveys information about one overall trend (based on height/length) but also shows the influence of the
categories on that trend. The chart below shows the overall growth of Top soccer team revenue above 6 billion in
2014.

Figure 54: Stacked column chart

This stacked column chart shows us that total revenue is growing over time and that the Commercial and the
Broadcasting categories are increasing steadily over time – contributing to overall revenue increase. But this chart
doesn’t make it easy to compare the impact each of the 3 categories has on each other. For example, how does the
growth of Commercial compare to the growth of Broadcasting or Match Day? A better choice for this data, or a
companion visual for this data, would be a line chart.

Figure 55: Convert to a line chart

In this line chart it is easier to see how commercial revenue has grown the most followed by broadcast and match
day.
Best practices
 As with columns/bars, you have the option of horizontal or vertical display. Horizontal is a better choice if
you have long labels and vertical if you have time series data.
Avoid stacked Bar/Column charts if you want to show trends and other patterns of change over time. Other
charts, like Line charts, do a much better job.
You can also have the distribution based on total volume or as a % of total.
As Few noted it is difficult to compare the segments of a stacked bar. If the segments were arranged side-
by-side and all grew upwards from the same baseline, it would be easy to compare their heights, but when
stacked upon one another, the task becomes hard. Plus, although it’s fairly easy to see how (revenue)
changed from month to month it is quite difficult to see how (revenue) in the other (categories) changed.
100% Stacked charts are a good choice when using percentages that add up to 100. In the example below,
we see the category distribution by team. The percentages are relative and allows us to, at a glance, see
patterns. For example, Everton’s revenue comes primarily from Broadcasting (over 70%) while PSG only
derives 20% of its revenue from Broadcasting. The choice of a horizontal display makes it easier to fit the
team labels and to see the impact of revenue type.

Figure 56: Horizontal stacked chart

For more information on stacked charts:
Data Visualization Catalogue: Stacked bar graphs
When are 100% stacked bar graphs useful?
Combo Bar/Column Charts

In Power BI, you can combine column and line charts into a combo chart. The choices are: Line and Stacked
Column chart and Line and Clustered Column chart. Save valuable canvas space by combining two separate
visuals into one.
The two screenshots below show a before and after. The first page has two separate visuals: a Column chart
showing population over time and a Line chart showing GDP over time. These charts are a good candidate for a
Combo chart because they have the same X-Axis (year) and values (2002 through 2012). Why not combine them
to compare these 2 trends on a single visual? Combining these 2 charts lets you make a quicker comparison of the
data.
The new report page has a single visual: a line and stacked column chart. We could’ve just as easily created a line
and clustered column chart. It’s now easier to look for a relationship between the two trends. We can see that up
until 2008, population and GDP followed a similar trend. But starting in 2009, as population growth flattened,
GDP was more volatile.

Figure 57: As two separate charts

Figure 58: As a single combo chart

Best practices
Combo charts work best when both visuals have at least one axis in common.
Watch your axes! Is your Combo chart easy to read and interpret? Or does it use dissimilar ranges and values? For
example, if the scale of the column chart’s Y -Axis is much smaller than the scale of the line chart’s Y -Axis, your
combo chart won’t be meaningful. For example, notice the third line (aqua color) way down at the bottom.
Figure 59: An unsuccessful line chart
So too, your combo chart won’t be meaningful if your column chart and line chart use 2 different measures and
you don’t create dual axes. For example, dollars versus percent. Be sure to include both axes to help the reader
understand the chart and consider adding axes labels as well.
To do this, open the Formatting pane, expand Y -Axis and set Show Secondary to On (if it isn’t already on). This
setting is sometimes difficult to find; expand Y -Axis (Column) and scroll down until you see Show secondary.
Also, set the Y -Axis (Column) Title to On and set the Y -Axis (Line) Title to On.

Figure 60: Show secondary axis

Figure 61: Create a combo chart instead

Take advantage of dual axes. It’s a great way to compare multiple measures with different value ranges. And it’s
a great way to illustrate the correlation between two measures in one visual.
For more information:
Combo chart in Power BI
The danger of dual-scaled Axes in visuals
Scatter Chart

Sometimes we have many variables that we want to see together, and a scatter chart can be a very useful way to
get an overall picture. Scatter charts display relationships between 2 (Scatter) or 3 (Bubble) quantitative measures.
A scatter chart always has two value axes to show one set of numerical data along a horizontal axis and another set
of numerical values along a vertical axis. The chart displays points at the intersection of an x and y numerical value,
combining these values into single data points. These data points may be distributed evenly or unevenly across the
horizontal axis, depending on the data.
A bubble chart replaces the data points with bubbles, with the bubble size representing an additional dimension of
the data.
The bubble chart below looks at South America and compares GDP per capita (Y -Axis) sum of GDP (X-Axis) and
population by South American country. The size of the bubbles represents total population for that country. Brazil
has the largest population (bubble size) and the largest share of South America’s GDP (it is farthest along on the
X-Axis). But notice that GDP per capita for Uruguay, Chile, and Argentina is higher than Brazil (farther up on the Y -
Axis).

Figure 62: South America GDP and population as a bubble chart

If you add a play axis, you can pretend you are Hans Rosling and tell the story over time
(https://www.youtube.com/watch?v=PbaDBJWCeD4). To add a play axis, drag a datetime field into the Play Axis
well.
Best practices
Scatter and Bubble charts are great storytellers. But they are not as useful when trying to explore data. This is
what Stephen Few points out in the paragraph below The strength of this approach is when it’s used to tell a
story. When Rosling narrates what’s happening in the chart as the bubbles move around and change in value,
 pointing to what he wants us to see, the information comes alive. Animated bubble charts, however, are much
less effective for exploring and making sense of data on our own. I doubt that Rosling uses this method to
discover the stories, but only to tell them once they’re known. We can’t attend more than one bubble at once as
they’re moving around, so we’re forced to run the animation over and over to try to get a sense of what’s going
on. We can add trails to selected bubbles, which make it possible to review the full path these bubble have
taken, but if trails are used for more than a few bubbles the chart will quickly become too cluttered. Essentially,
what I’m pointing out is that this is not the best way to display this information for exploration and analysis.
Add X and Y axes labels to help tell the story. Especially with bubble charts, there are many components at play
and labels help readers understand the visual.
Add data labels to make the visual easier to interpret. Especially with bubble charts, when you have many items
in the Legend, it may be difficult to distinguish between similar colors. In the visual above, the legend colors for
Suriname, Columbia, and Ecuador are very similar.
Did you create a scatter chart and see only one data point that aggregates all the values on the X and Y axes?
Or, your chart aggregates all the values along a single horizontal or vertical line? To fix this, add a field to the
Details area to tell Power BI how to group the values. The field must be unique for each point you want to plot.
For help, refer to the Power BI scatter and bubble chart tutorial.
Tree Map Charts

Tree maps can be very useful for giving a good overview of the relative size of different components that make up
a whole -- especially when you can group them by categories. Any time I try to understand a new business, having
a tree map of the main components can be very useful in knowing the overall distribution.
In the first chart below, you can see right away that Brazil makes up approximately half of South America’s GDP
and that Venezuela and Argentina are roughly the same size.
If you want to have broader context and still have an idea of the impact of the top contributing countries, you can
create visual hierarchies with category members (countries) nested inside regions. The second tree map gives us
an idea, first and foremost, of the relative size of the regions and then, within each region, we can see which
individual countries contribute the most. We see that there are three massive regions (Europe, Asia & North
America) and within those we can easily see the top countries/regions.
The main limitation of a tree map is the limited ability to compare the different rectangles beyond the top ones. It
is a good chart for an overview but column and bar chart are probably a better choice to have more precise idea of
the relative size of different components.   For example, the first tree map gives a broad indication of the order of
the GDP size, but it’s hard to identify specific differences between countries, particularly the smaller unlabeled
boxes. For this data, where a single grouping is compared, a bar or column chart might be a better choice.
Figure 63: South America GDP comparison as a tree map
Here we’ve added another level of data, region, and we can see the overall contribution to GDP by regions, as well
as the relative impact within the regions. Beware that doing this with non-summative measure (such as averages)
that the sum of the details might not represent the actual value at the aggregate level.

Figure 64: GDP by region and country as a tree map

For more information on tree maps, feel free to click on links below.
Treemaps overview
Data Visualization Catalogue: Tree maps
Other charts
Pie or Donut Charts
In general, bar/column/line charts will serve most purposes. It’s well understood that pie and donut charts are
difficult for humans to interpret correctly, and in fact can often distort data. Avoid them where possible. Stephen
Few has an excellent write up on the history and dangers in [Save the Pies for Dessert]
(www.percetualedge.com/articles/08-21-07.pdf
He does explain the one time where pie charts can be useful, when comparing part-to-whole relationships. But
even this is rarely significantly-better than, say, a 100% stacked bar chart.
Another fun article (and animation) about pie charts can be found on the Darkhorse Analytics site.
Radial Gauges & KPIs

Radial gauges seem like a good visual for indicating performance against a target, and they are very popular in
executive dashboards. However, they suffer in two main ways. As with pie charts, it’s difficult to interpret the angle
of the shaded area compared to the full 180 degree arc or target line. It also uses a lot of space to show a single
metric.
A good alternative is a simple KPI visual

KPIs show the value, status, goal, variance from the goal and trend in the same amount of space. The green
coloring turns red if the target isn’t being met and can be yellow if some intermediate target is hit. It’s much
simpler to read and interpret than the gauge.
For more information, see:
Radial gauge charts in Power BI
KPIs in Power BI

Conclusion
Now it’s time for you to put these best practices to the test. Keep in touch and share your own best practices. Don’t
agree with our recommendations or found a great reason to “break the rules?” We’d love to hear about those as
well.
Book recommendations
There are many good books available today to help teams bone up on visual design techniques. Stephen Few’s
Information Dashboard Design book is a must-read. He delves into greater detail in two other books, Show Me the
Numbers and Now You See It. Few and others have drawn inspiration from Edward R. Tufte, whose book The
Visual Display of Quantitative Information is considered a classic in the field. Tufte has also written Visual
Explanations, Envisioning Information, and Beautiful Evidence. Andy Kirk’s new book Data Visualization: A
Handbook for Data Driven Design is another great option. Some other authors who have been recommended are:
Lachlan James, William McKnight, and Boris Evelson (Forrester), Darkhorse Analytics.
More questions? Try the Power BI Community
 Change the type of visualization in a Power BI report
1/14/2019 • 2 minutes to read • Edit Online

Try different types of visualizations in Power BI service and Power BI Desktop to see which one illustrates your
data best.
1. Open a report that already has at least one visualization.
2. Select a visualization to make it active. An active visualization has handles and a border.
3. In the Visualizations pane, select the new visualization type.

.
4. (Optional) Pin your visualization to your dashboard as a tile.
If you change the visualization type in the report after you pinned it to your dashboard, the dashboard tile does
not automatically update. So, if you pinned the visualization as a line chart and then, in the report, changed it to a
bar chart, the already-pinned version of this data will remain a line chart. Pin the bar chart to see it too on the
dashboard.
Next steps
More about Visualizations in Power BI reports
Power BI - Basic Concepts
More questions? Try the Power BI Community
 Data point limits and strategies by visual type
1/30/2019 • 5 minutes to read • Edit Online

When rendering a visual in Power BI, the visualization must be quick and accurate. That requires underlying
algorithms configured for each visual type. Visuals in Power BI must be flexible enough to handle different sizes of
datasets. Some datasets have only a handful of data points, while other datasets have petabytes of data points. This
article explains the strategies used by Power BI to render visualizations.

Data reduction strategies

Every visual employs one or more data reduction strategies in order to handle the potentially large volumes of data
being analyzed. Even a simple table employs a strategy to avoid loading the entire dataset to the client. The
reduction strategy being used varies by visual type. Each visual selects from the supported data reduction
strategies as part of generating the data request sent to the server.
Each visual controls the parameters on those strategies to influence the overall amount of data.

Strategies
For each strategy, there are defaults based on the shape and type of data being visualized. But the defaults can be
overridden, in the Power BI Formatting pane, to provide the right user experience.
Data Windowing (Segmentation): Allow users to scroll through the data in a visual by progressively loading
fragments of the overall dataset.
TopN: Show only the first N items
Simple Sample: Show the first, last, and N evenly distributed items in between.
BottomN: Show only the last N items. Useful for monitoring frequently updated data.
High-density sampling - An improved sampling algorithm that better respects outliers and/or the shape of a
curve.
Binned line sampling - Sample data points based on outliers in bins across an axis
Overlapping points sampling - Sample data points based on overlapping values to preserve outliers

Statistics
Certain models can provide statistics about the number of values for certain columns. When such information is
present, we leverage that information to provide better balancing across multiple hierarchies, if a visual does not
explicitly override the count of values for a strategy.
For more information, see What's new in Analysis Services

Dynamic limits
In addition to the strategies above, visuals with two hierarchies of grouping columns (axis and legend, or category
and series) use one additional strategy called dynamic limits. Dynamic limits are designed to better balance data
points.
Dynamic limits provide a better selection of points for sparse data than static limits would. For example, a visual
could be configured to select 100 categories and 10 series with a total of 1000 points. But the actual data has 50
categories and 20 series. At query runtime, dynamic limits selects all 20 series to fill up the 1000 points requested.
Dynamic limits are automatically applied when the server is capable as detailed below:
 In Power BI Desktop with On-premises SSAS version 2016 or higher leveraging the SuperDax capabilities
of the server
In Desktop and Power BI service when using an imported model, Direct Query, live connect to the service,
or live connect to AS PaaS.
In Power BI Service, when connecting through an on-premises gateway to on-premises SSAS, we cannot
use dynamic limits. The on-premises gateway does not fully support the dynamic limits strategy that returns
a different structure of result sets from the on-premises SSAS.

Strategies and data point limits by visual type

Area chart
See How line sampling works
Bar/column chart
When in categorical mode
Categories: Virtualization by using Window of 500 rows at a time
Series: Top 60
When in scalar mode (this could use dynamic limits)
Max points: 10,000
Categories: Sample of 500 values
Series: Top 20 values
Card (multirow)
Values: Virtualization by using Window of 200 rows at a time
Combo chart
Uses the same strategies as column chart. Notice that the line in the combo chart does not use the high density
algorithm that the line chart uses.
Custom visuals
Can get up to 30,000 but it is up to the visual authors to indicate what strategies to use
Doughnut
Max points: 3,500
Group: Top 500
Details: Top 20
Filled map choropleth
The filled map can use statistics or dynamic limits. Power BI tries to use reduction in the following order: dynamic
limits, statistics, and lastly configuration.
Max points: 10000
Categories: Top 500
Series (when both X and Y are present): Top 20
Funnel
Max points: 3,500
Categories: Top 3,500
KPI
Trend axis
Bottom 3,500
Line chart
See How line sampling works
Line chart, high density
See High density sampling
Map
Max points: 3,500
Depending on the configuration, a map can have:
Location: Top 3,500
Location, Size: Top 3,500
Location, Latitude and Longitude aggregates (+/-Size): Top 3,500
Latitude, Longitude: see High density scatter
Latitude, Longitude, Size: Top 3,500
Legend, Latitude, Longitude: see High density scatter
Legend, Latitude, Longitude, Size: Top 233 legends, Top 15 latitude and longitude (this could use statistics or
dynamic limits)
Location, Legend, Latitude Longitude as aggregates (+/-Size): Top 233 locations, Top 15 legends (this could use
statistics or dynamic limits)
Matrix
Rows: Virtualization by using Window of 500 rows at a time
Columns: Top 100 grouping columns
Values: multiple values do not count against the data reduction
Radial gauge
No reduction strategy
Slicer
Values: Virtualization by using Window of 200 rows at a time
Scatter chart (high density)
See High density scatter
Pie
Max points: 3,500
Group: Top 500
Details: Top 20
R & Python visuals
Limited to 150,000 rows. If more than 150,000 rows are selected, only the top 150,000 rows are used
Ribbon chart
When in categorical mode
Categories: Virtualization (data windowing) by using Window of 500 rows at a time
Series: Top 60
When in scalar mode (this could use dynamic limits)
Max points: 10,000
Categories: Sample of 500 values
Series: Top 20 values
Shape map
The filled map can use statistics or dynamic limits.
Max points: 10,000
Categories: Top 500
Series (when both X and Y are present): Top 20
Table
Values: Virtualization (data windowing) by using Window of 500 rows at a time
Tree map (this could use statistics or dynamic limits)
Max points: 3,500
Group: Top 500
Details: Top 20
Waterfall chart
When there is only the category bucket
Max points: 3,500
Category only - top 3,500
When both category and breakdown are present
Category: Virtualization (data windowing) by using Window of 30 rows at a time
Breakdown - Top 200 values

Next steps
Visualization types
 Show the data that was used to create the
visualization
1/14/2019 • 2 minutes to read • Edit Online

Show data
A Power BI visualization is constructed using data from your datasets. If you're interested in seeing behind-the-
scenes, Power BI lets you display the data that is being used to create the visual. When you select Show Data,
Power BI displays the data below (or next to) the visualization.
You can also export the data that is being used to create the visualization as an .xlsx or .csv file and view it in Excel.
For more information, see Export data from Power BI visualizations.

NOTE
Show Data and Export Data are both available in Power BI service and Power BI Desktop. However, Power BI Desktop
provides one additional layer of detail; Show Records displays the actual rows from the dataset.

Using Show Data in Power BI service

1. In Power BI service, open a report in Reading view or Editing view, and select a visual. In Power BI Desktop,
open Report view.
2. To display the data behind the visual, select Explore > Show data.

3. By default, the data displays below the visual.

4. To change the orientation, select vertical layout from the top-right corner of the visualization.

5. To export the data to a .csv file, select the ellipses and choose Export data.

For more information on exporting the data to Excel, see Export data from Power BI visualizations.
6. To hide the data, de-select Explore > show data.

Next steps
Export data from Power BI visualizations
Visualizations in Power BI reports
Power BI reports
More questions? Try the Power BI Community
 Getting started with color formatting and axis
properties
1/14/2019 • 3 minutes to read • Edit Online

In Power BI, you can change the color of data series, data points, and even the background of visualizations. You
can also change how the x-axis and y-axis are presented, providing you with full control of how your dashboards
and reports appear.
To get started, select a Report from the My Workspace pane. Then from the top menu area, select Edit Report.

When you’re editing a report and you have a visualization selected, the Visualizations pane appears which lets
you add or change visualizations. Directly below the available visualizations are three icons: the Fields icon (a
stack of bars), the Format icon (a roller brush), and the Analytics icon (a magnifying glass). In the image below
the Fields icon is selected, indicated by a yellow bar below the icon.

When you select Format, the area below the icon displays the color and axis customizations available for the
currently selected visualization.
You can customize many elements of each visualization:
Legend
X-axis
Y -axis
Data colors
Data labels
Shapes
Plot area
Title
Background
Lock aspect
Border

NOTE
You won’t see all these elements with each visualization type. The visualization you select will affect which customizations are
available; for example, you won’t see an X-Axis if you have a pie chart selected because pie charts don’t have an X-axis.

Also note that if you don’t have any visualization selected, Filters appears in place of the icons, which lets you
apply filters to all visualizations on the page.
Let’s show a couple examples: one working with colors, the other changing the properties of an axis. From there,
you should be ready to customize colors, axes, and labels all day long.

Working with colors

Let’s walk through the steps necessary to customize colors on a chart.
1. I select a Clustered Column Chart from the report canvas.
2. Next, I choose the Format icon to show the available customizations.
3. Then I select the small down arrow to the left of the Data Colors customization. This will show how I can
customize the Data Colors, with options that are specific to the visualization I’ve selected.
4. Data Colors expands downward to show its available customizations.

Let’s make some changes. I can select the down arrow next to the color to make changes on each available data
series. I’ll make Cost of living yellow, Weather I’ll turn orange, and Community well-being will be green. The
following screen shows me at the last step, changing Cost of living.
The changes are shown in the image below. Wow, that’s a bright chart. Here are a few useful elements to note
about working with colors. The numbers in the following list are also shown on the following screen, indicating
where these useful elements can be accessed or changed.
1. Don’t like the colors? No problem, just select Revert to default and your selection reverts to the default
settings. You can do that for one color, or for the entire visualization.
2. Want a color you don’t see in the palette? Just select Custom color, and choose from the spectrum.
Not crazy about the change you just made? Use CTRL+Z to undo , just like you’re used to doing.

Changing axis properties

It’s often useful to modify the X-axis or the Y -axis. Similar to working with colors, you can modify an axis by
selecting the down-arrow icon to the left of the axis you want to change, as shown in the following image.
If you want to collapse the X-Axis options, just select the up arrow icon beside X-Axis.
You can remove the X-axis labels entirely, by toggling the radio button beside X-Axis. You can also choose
whether to turn axis titles on or off by selecting the radio button next to Title.
There are all sorts of colors to choose from, and many more customizations you can apply to your Power BI
reports and dashboards.

NOTE
These color, axis, and related customizations available when the Format icon is selected are also available in Power BI
Desktop.

Setting color from text values

Beginning with the August 2018 Power BI Desktop update, you can set colors by the text value, or hex code, for
a given report element. For more information, please see conditional formatting in tables.

Next steps
For more information, see the following article:
Tips and tricks for color formatting in Power BI
Conditional formatting in tables
 Tips and tricks for color formatting in Power BI
2/13/2019 • 5 minutes to read • Edit Online

Power BI provides many different ways to customize your dashboards and reports. This article details a collection
of tips that can make your Power BI visualizations more compelling, interesting, and customized to your needs.
The following tips are provided. Have another great tip? Great! Send it our way and we’ll see about adding it to
this list.
Change the color of a single data point
Base the colors of a chart on a numeric value
Base the color of data points on a field value
Customize colors used in the color scale
Use diverging color scales
How to undo in Power BI
To make any changes, you must be editing a report. Open the report and select Edit Report from the top menu
area, as shown in the following image.

When the Visualizations pane appears along the right side of the Report canvas, you’re ready to start
customizing. If the pane does not appear, select the arrow, from the top right corner, to open it.
Change the color of a single data point
Sometimes you want to highlight one particular data point. Perhaps it’s sales figures for the launch of a new
product, or increased quality scores after launching a new program. With Power BI, you can highlight a particular
data point by changing its color.
The following visualization ranks units sold by product segment.

Now imagine you want to call out the Convenience segment to show how well this brand new segment is
performing, by using color. Here are the steps:
Expand the Data Colors section and turn the slider On for Show all. This displays the colors for each data
element in the visualization. When you hover over the data points, scrolling is enabled so you can modify any of
the data points.

Set Convenience to orange.

Once selected, the Convenience data point is a nice shade of orange, and certainly stands out.
Even if you change visualization types, then return, Power BI remembers your selection and keeps Convenience
orange.
You can change the color of a data point for one, several, or all data elements in the visualization. Perhaps you
want your visual to mimic your corporate colors.

There are all sorts of things you can do with colors. In the next section, we take a look at gradients.

Base the colors of a chart on a numeric value

Charts often benefit from dynamically setting color based on the numeric value of a field. By doing this, you could
show a different value than what’s used to for the size of a bar, and show two values on a single graph. Or you can
use this to highlight data points over (or under) a certain value – perhaps highlighting areas of low profitability.
The following sections demonstrate different ways to base color on a numeric value.
Base the color of data points on a value
To change color based on a value, drag the field you want to base color on into the Color Saturation area in the
Fields pane. In the following image, %Market Share SPLY YTD has been dragged into Color Saturation.

And on the Formatting pane, under Data colors, determine how the value of %Market Share SPLY YTD will
change the color and shading in your column chart. In this example, lower %Market Share will be lighter blue and
higher values will be darker blue.

As can see that, although we've sold more units of both Productivity and Extreme (their columns are higher),
Moderation has a larger %Market Share SPLY YTD (its column has more color saturation).
Customize the colors used in the color scale
You can customize colors used in the color scale, too. By default, the lowest value in your data is mapped to the
least saturated color, and the highest value to the most saturated color. In the image above, we used a blue
gradient.
Expand Data Colors and you see a gradient of colors used for visualizing your data. The color range is shown in a
gradient bar that displays the spectrum between Minimum and Maximum color values, with the Minimum
value color on the left, and Maximum value color to the right.

To change the scale to use a different range of colors, select the color drop-down beside Minimum or Maximum,
and select a color. The following image shows the Maximum color changed to black, and the gradient bar shows
the new color spectrum between Minimum and Maximum.
You can also change the way the values map to these colors. In the following image, the colors for Minimum and
Maximum are set to orange and green, respectively.
In this first image, notice how the bars in the chart reflect the gradient shown in the bar; the highest value is green,
the lowest is orange, and each bar between is colored with a shade of the spectrum between green and orange.

Now, let’s see what happens if we provide numeric values in the Minimum and Maximum value boxes, which
are below the Minimum and Maximum color selectors (shown in the following image). Let’s set Minimum to
20,000,000, and set Maximum to 20,000,001.
By setting those values, gradient is no longer applied to values on the chart that are below Minimum or above
Maximum; any bar with a value over Maximum value is colored green, and any bar with a value under
Minimum value is colored red.
Use diverging color scales
Sometimes your data may have a naturally diverging scale. For example, a temperate range has a natural center at
freezing point, and a profitability score has a natural mid-point (zero).
To use diverging color scales, slide the Diverging slider to On. When Diverging is turned on, an additional color
selector and value box, both called Center, appear, as shown in the following image.

When the Diverging slider is on, you can set the colors for Minimum, Maximum and Center separately. In the
following image, Center is set to one, so bars with values above one are a gradient shade of green, and bars below
one are shades of red.

How to undo in Power BI

Like many other Microsoft services and software, Power BI provides an easy way to undo your last command. For
example, let’s say you change the color of a data point, or a series of data points, and you don’t like the color when
it appears in the visualization. You don’t recall exactly which color it was before, but you know you want that color
back!
To undo your last action, or the last few actions, all you have to do is:
Type CTRL+Z

Feedback
Do you have a tip you’d like to share? Please send it our way, and we’ll see about including it here.

NOTE
These color, axis, and related customizations, available when the Format icon is selected, are also available in Power BI
Desktop.

Next steps
Getting started with color formatting and axis properties
 Copy and paste a visualization in Power BI service
and Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

Copying and pasting a visualization requires edit permissions to the report. In Power BI service, this means
opening the report in Editing View.
1. Open a report that has at least one visualization.
2. Select the visualization and use Ctrl +C to copy, and Ctrl +V to paste.

Next steps
More about Visualizations in Power BI reports
More questions? Try the Power BI Community
 Export data from visualizations
1/23/2019 • 7 minutes to read • Edit Online

If you'd like to see the data that is used to create a visualization, you can display that data in Power BI or export
that data to Excel as an .xlsx or .csv file. The option to export the data requires a Pro or Premium license and edit
permissions to the dataset and report.
Watch Will export the data from one of the visualizations in his report, save it as an .xlsx file, and open it in Excel.
Then follow the step-by-step instructions below the video to try it out yourself.
https://www.youtube.com/embed/KjheMTGjDXw

From a visualization on a Power BI dashboard

1. Select the ellipses in the top right corner of the visualization.

2. Choose the Export data icon.

3. The data is exported to a .csv file. If the visual is filtered, then the downloaded data will also be filtered.
4. Your browser will prompt you to save the file. Once saved, open the .csv file in Excel.
From a visualization in a report
To follow along, open the Procurement analysis sample report in Editing view. Add a new blank report page. Then
follow the steps below to add an aggregation and a visualization-level filter.
1. Create a new column chart. From the Fields pane, select Location > City and Invoice > Discount
Percent. You may have to move Discount Percent into the Value well.

2. Change the aggregation for Discount Percent from Count to Average. In the Value well, select the arrow
to the right of Discount Percent (it may say Count of Discount Percent), and choose Average.

3. Add a filter to City to remove Atlanta.

 Now we're ready to try out both options for exporting data.
4. Select the ellipses in the top right corner of the visualization. Choose Export data.

5. In Power BI online, if your visualization has an aggregate (one example would be if you changed Count to
average, sum or minimum), you'll have two options: Summarized data and Underlying data. In Power
BI Desktop, you'll only have the option for Summarized data. For help understanding aggregates, see

Aggregates in Power BI.

6. Select Summarized data > Export and choose either .xlsx or .csv. Power BI exports the data. If you have
applied filters to the visualization, the exported data will export as filtered. When you select Export, your
browser prompts you to save the file. Once saved, open the file in Excel.
Summarized data: select this option if you want to export data for what you see in that visual. This type of
export shows you only the data (columns and measures) that you chose to create the visual. If the visual
has an aggregate, you'll export aggregated data. For example, if you have a bar chart showing 4 bars, you
will get 4 rows of data. Summarized data is available as .xlsx and .csv.
In this example, our Excel export shows one total for each city. Since we filtered out Atlanta, it is not
included in the results. The first row of our spreadsheet shows the filters that were used when extracting
the data from Power BI.
7. Now try selecting Underlying data > Export and choosing .xlsx. Power BI exports the data. If you had
applied filters to the visualization, the exported data will export as filtered. When you select Export, your
browser prompts you to save the file. Once saved, open the file in Excel.

WARNING
Exporting underlying data allows users to see all the detailed data -- every column in the data. Power BI service
administrators can turn this off for their organization. If you are a dataset owner, you can set proprietary columns to
"hidden" so that they don't show up in the Field list in Desktop or Power BI service.

Underlying data: select this option if you want to see the data in the visual and additional data from the
model (see chart below for details). If your visualization has an aggregate, selecting Underlying data
removes the aggregate. When you select Export, the data is exported to an .xlsx file and your browser
prompts you to save the file. Once saved, open the file in Excel.
In this example, our Excel export shows one row for every single City row in our dataset, and the discount
percent for that single entry. In other words, the data is flattened and not aggregated. The first row of our
spreadsheet shows the filters that were used when extracting the data from Power BI.

Export underlying data details

What you see when you select Underlying data can vary. Understanding these details may require the help of
your Admin or IT department. In Power BI Desktop or service, in the reporting view, a measure displays in the
Fields list with a calculator icon . Measures are created in Power BI Desktop not Power BI service.

VISUAL CONTAINS WHAT YOU'LL SEE IN EXPORT

Aggregates the first aggregate and non-hidden data from the entire table
for that aggregate

Aggregates related data - if the visual uses data from other data tables
that are related to the data table that contains the aggregate
(as long as that relationship is *:1 or 1:1)
 VISUAL CONTAINS WHAT YOU'LL SEE IN EXPORT

Measures All measures in the visual and all measures from any data
table containing a measure used in the visual

Measures All non-hidden data from tables that contain that measure (as
long as that relationship is *:1 or 1:1)

Measures All data from all tables that are related to table(s) containing
the measures via a chain of *:1 of 1:1)

Measures only All non-hidden columns from all related tables (in order to
expand the measure)

Measures only Summarized data for any duplicate rows for model measures.

Set the export options

Power BI report designers control the types of data export options that are available for their consumers. The
choices are:
Allow export of only summarized data (this is the default for new reports)
Allow exporting of summarized and underlying data(this was the default prior to October 2018)
Don't allow exporting of any data

IMPORTANT
We recommend that report designers revisit old reports and manually reset the export option as needed.

1. To set these options, start in Power BI Desktop.

2. From the upper left corner, select File > Options and Settings > Options.
3. Under Current file select Report settings.
4. Make your selection from the Export data dropdown.
You can also update this setting in Power BI service.
It is important to note that if the Power BI admin portal settings conflict with the report settings for export data,
the admin settings will override the export data settings.

Limitations and considerations

The maximum number of rows that can be exported from Power BI Desktop and Power BI service to
.csv is 30,000.
The maximum number of rows that can be exported to .xlsx is 150,000.
Export using Underlying data will not work if the data source is an Analysis Services live connection and
the version is older than 2016 and the tables in the model do not have a unique key.
Export using Underlying data will not work if the Show items with no data option is enabled for the
visualization being exported.
When using DirectQuery, the maximum amount of data that can be exported is 16 MB. This may result in
exporting less than the maximum number of rows, especially if there are many columns, data that is
difficult to compress, and other factors that increase file size and decrease number of rows exported.
If the visual uses data from more than one data table, and no relationship exists for those tables in the data
model, only data for the first table is exported.
Custom visuals and R visuals, are not currently supported.
 Export data is not available for users outside of your organization who are using a dashboard that has been
shared with them.
In Power BI, a field (column) can be renamed by double-clicking the field and typing a new name. This new
name is referred to as an alias. It is possible that a Power BI report can end up with duplicate field names
but Excel does not allow duplicates. So when the data is exported to Excel, the field aliases revert to their
original field (column) names.
If there is unicode character in the .csv file, the text in Excel may not display properly. Although, opening it
in Notepad will work fine. Examples of unicode characters are currency symbols and foreign words. The
workaround for this is to import the csv into Excel, instead of opening the csv directly. To do this:
1. Open Excel
2. From the Data tab, select Get external data > From text.
Power BI admins have the ability to disable the export of data.
More questions? Try asking the Power BI Community
 Move and resize a visualization in a report in Power
BI service and Power BI Desktop
2/13/2019 • 2 minutes to read • Edit Online

Only report creators and owners can move and resize visualizations. In Power BI service (app.powerbi.com) this
means opening the report in Editing view.

Open the report

In Power BI, open a report that has at least one visualization, or create a new visualization.

Move the visualization

Select (left-click) any area of the visualization and drag to the new location.

Resize the visualization

Select the visualization to display the border and click and drag the dark frame handles to resize.

Select Focus mode to see more detail.

Hover over the visualization and select the Focus mode icon.

Next steps
Resize a visualization on a dashboard
More questions? Try the Power BI Community
 Change how visuals interact in a Power BI report
2/19/2019 • 2 minutes to read • Edit Online

If you have edit permissions for a report, you can use Visual interactions to change how visualizations on a
report page impact each other.
By default, visualizations on a report page can be used to cross-filter and cross-highlight the other visualizations
on the page. For example, selecting a state on a map visualization highlights the column chart and filters the line
chart to display only data that applies to that one state. See About filtering and highlighting. And if you have a
visualization that supports drilling, by default, drilling one visualization has no impact on the other visualizations
on the report page. But both of these default behaviors can be overridden, and interactions set, on a per-
visualization basis.
This article shows you how to use Visual interactions in Power BI service Editing view and in Power BI Desktop.
If a report has been shared with you, you will not be able to change the Visual interactions settings.

NOTE
The terms cross-filter and cross-highlight are used to distinguish the behavior described here from what happens when you
use the Filters pane to filter and highlight visualizations.

https://www.youtube.com/embed/N_xYsCbyHPw?list=PL1N57mwBHtN0JFoKSR0n-tBkUJHeMP2cP
1. Select a visualization to make it active.
2. Display the Visual Interactions options.
In Power BI service, select the dropdown from the report menubar.

In Desktop, select Format > Interactions.

3. To turn on the visualization interaction controls, select Edit interactions. Power BI adds cross-filter and
cross-highlight icons to all of the other visualizations on the report page.
4. Determine what impact the selected visualization should have on the others. And, optionally, repeat for all
other visualizations on the report page.

If it should cross-filter the visualization, select the filter icon .

If it should cross-highlight the visualization, select the highlight icon .

If it should have no impact, select the no impact icon .

5. To turn on drilling controls, select Drilling filters other visuals. Now when you drill down (and up) in a
visualization, the other visualizations on the report page change to reflect your current drilling selection.
 Tips and Tricks for Power BI Map visualizations
2/28/2019 • 6 minutes to read • Edit Online

Power BI integrates with Bing Maps to provide default map coordinates (a process called geo-coding) so you can
create maps. Together they use algorithms to identify the correct location, but sometimes it's a best guess. If Power
BI tries, but can't create the map visualization on its own, it enlists the help of Bing Maps.
You, or your administrator, may need to update your firewall to allow access to the URLs Bing uses for geocoding.
Those URLs are:
https://dev.virtualearth.net/REST/V1/Locations
https://platform.bing.com/geo/spatial/v1/public/Geodata
https://www.bing.com/api/maps/mapcontrol
To increase the likelihood of correct geo-coding, use the following tips. The first set of tips is for you to use if you
have access to the dataset itself. The second set of tips is things you can do in Power BI if you don't have access to
the dataset. And the final set is a list of URLs

What is sent to Bing Maps?

Power BI service and Power BI Desktop send Bing the geo data it needs to create the map visualization. This may
include the data in the Location, Latitude, and Longitude buckets and geo fields in any of the Report level,
Page level, or Visual level filter buckets. Exactly what is sent varies by map type. To learn more, see Bing Maps
privacy.
For maps (bubble maps), if latitude and longitude are provided, then no data is sent to Bing. Otherwise, any
data in the Location (and filter) buckets is sent to Bing.
Filled maps require a field in the Location bucket; even if latitude and longitude are provided. Whatever
data is in the Location, Latitude, or Longitude bucket is sent to Bing.
In the example below, the field Vendor is being used for geo-coding, so all vendor data is sent to Bing. Data
from the Size and Color saturation buckets is not sent to Bing.

In this second example below, the field Territory is being used for geo-coding, so all territory data is sent to
Bing. Data from the Legend and Color saturation buckets is not sent to Bing.
In the dataset: tips to improve the underlying dataset
If you have access to the dataset that is being used to create the map visualization, there are a few things you can
do to increase the likelihood of correct geo-coding.
1. Categorize geographic fields in Power BI Desktop
In Power BI Desktop, you can ensure fields are correctly geo-coded by setting the Data Category on the data
fields. Select the desired table, go to the Advanced ribbon and then set the Data Category to Address, City,
Continent, Country/Region, County, Postal Code, State or Province. These data categories help Bing
correctly encode the date. To learn more, see Data categorization in Power BI Desktop. If you are live connecting to
SQL Server Analysis Services, you will need to set the data categorization outside of Power BI using SQL Server
Data Tools (SSDT).
2. Use more than one location column.
Sometimes, even setting the data categories for mapping isn't enough for Bing to correctly guess your intent.
Some designations are ambiguous because the location exists in multiple countries or regions. For example,
there's a Southampton in England, Pennsylvania, and New York.
Power BI uses Bing's unstructured URL template service to get the latitude and longitude coordinates based on a
set of address values for any country. If your data doesn't contain enough location data, add those columns and
categorize them appropriately.
For example, if you only have a City column, Bing may have a hard time geo-coding. Add additional geo columns
to make the location unambiguous. Sometimes all it takes is adding one more location column to the dataset - in
this case state/province. And don't forget to categorize it properly, see #1 above.
Make sure when each field only has the specific information tied to the categorization. For example, your City
location field should be Southampton, not Southampton, New York. And Address location fields should be 1
Microsoft Way and not 1 Microsoft Way, Redmond, WA.
3. Use specific Latitude and Longitude
Add latitude and longitude values to your dataset. This removes any ambiguity and returns results more quickly.
Latitude and Longitude fields must be in Decimal Number format, which you can set in the data model.
https://www.youtube.com/embed/ajTPGNpthcg
4. Use Place category for columns with full location information
While we encourage you to use geo-hierarchies in your maps, if you must use a single location column with full
geographical information, you can set the data categorization to Place. For example, if the data in your column is
full addresses, such as 1 Microsoft Way, Redmond Washington 98052, this generalized data category will work
best with Bing.

In Power BI: tips to get better results when using map visualizations
1. Use latitude and longitude fields (if they exist)
In Power BI, if the dataset you are using has fields for longitude and latitude -- use them! Power BI has special
buckets to help make the map data unambiguous. Just drag the field that contains your latitude data into the
Visualizations > Latitude area. And do the same for your longitude data. When you do this, you also need to fill
the Location field when creating your visualizations. Otherwise, the data is aggregated by default, so for example,
the latitude and longitude would be paired at the state level, not the city level.

Use geo-hierarchies so you can drill down to different "levels" of

location
When your dataset already has different levels of location data, you and your colleagues can use Power BI to
create geo -hierarchies. To do this, drag more than one field into the Location bucket. Used together in this way,
the fields become a geo-hierarchy. In the example below we have added geo fields for: Country/Region, State, and
City. In Power BI you and your colleagues can drill up and down using this geo-hierarchy.
When drilling with geo-hierarchies, it is important to know how each drill button works and what gets sent to Bing
Maps.
The drill button on the far right, called Drill Mode , allows you to select a map Location and drill down into
that specific location one level at a time. For example, if you turn Drill Down on and click North America, you
move down in the hierarchy to the next level -- states in North America. For geo-coding, Power BI sends Bing
Maps country and state data for North America only.
On the left there are 2 other drill options. The first option, , drills to the next level of the hierarchy for all
locations at once. For example, if you are currently looking at countries and then use this option to move to the
next level, states, Power BI displays state data for all countries. For geo-coding, Power BI sends Bing Maps state
data (no country data) for all locations. This option is useful if each level of your hierarchy is unrelated to the
level above it.
The second option, , is similar to Drill Down, except that you don't need to click on the map. It expands
down to the next level of the hierarchy remembering the current level’s context. For example, if you are
currently looking at countries and select this icon, you move down in the hierarchy to the next level -- states.
For geo-coding, Power BI sends data for each state and its corresponding country to help Bing Maps geocode
more accurately. In most maps, you will use either this option or the Drill Down option on the far right, so you
can send Bing as much information as possible to get accurate location information.

Next steps
Drill down in a Power BI visualization
Power Bi visualizations
More questions? Try the Power BI Community
 Customize X-axis and Y-axis properties
2/13/2019 • 4 minutes to read • Edit Online

In this tutorial you'll learn many different ways to customize the X-axis and Y -axis of your visuals. Not all visuals
have axes or can be customized; Pie charts, for example, don't have axes. And customization options vary from
visual to visual, too many options to cover in a single article. So we'll take a look at some of the most-used axes
customizations and get you comfortable using the visual formatting tab in the Power BI report canvas.

NOTE
This page applies to both Power BI service and Power BI Desktop. These customizations, which are available when the

Format (the paint roller icon ) is selected, are also available in Power BI Desktop.

Watch Amanda customize her X and Y axes and demonstrate the various ways to control concatenation when
using drill-up and drill-down. Then follow the step-by-step instructions below the video to try it out yourself using
the Retail Analysis sample.
https://www.youtube.com/embed/9DeAKM4SNJM

Customizing visualization X-axes in reports

Create a stacked chart visualization
Sign in to the Power BI service and open the Retail Analysis Sample report in Editing View. To follow along,
connect to the Retail Analysis sample.
1. Create a new column chart that shows this year's sales and last year's sales value by fiscal month.
2. Convert it to a Stacked column chart.

Customize the X axis

1. In the Visualizations and Filters pane, select Format (the paint roller icon ) to reveal the
 customization options.
2. Expand the X-Axis options.

3. Turn the X-axis on and off by selecting the On (or Off) slider. For now, leave it On. One reason you might
want to turn off the X-axis is to save space for more data.

4. Format the text color, size, and font. In this example we've set text Color to black, Text Size to 14, and Font
to Arial Black.
5. Turn the X-axis Title On and display the name of the X axis -- in this case, FiscalMonth.
6. Format the title text color, size, and font. In this example we've set Title color to orange, changed Axis title
to Fiscal Month, and set Title text size to 21.
7. To sort by FiscalMonth, select the ellipses (...) in the top-right corner of the chart and select Sort By
FiscalMonth.
After all these customizations, your column chart should look something like this:
To revert all the X-axis customization you've done so far, select Revert To Default at the bottom of the X-axis
customization pane.

Customize the Y axis

1. Expand the Y -Axis options.

2. Turn the Y -axis on and off by selecting the On (or Off) slider. For now, leave it On. One reason you might
want to turn off the Y -axis is to save space for more data.

3. Move the Y -Axis Position to the right.

4. Format the text color, size, and font. In this example we've set text Color to black, Text Size to 14, and Font
to Arial Black.
5. Keep Display units set to Millions and Value decimal places to zero.
6. For this visualization, having a Y -axis title doesn't improve the visual, so leave Title turned Off.
7. Let's make the gridlines stand out by changing the Color to a dark grey and increasing Stroke to 2.
After all these customizations, your column chart should look something like this:
Customizing visualizations with dual Y-axes
First you'll create a Combo chart that looks at the impact store count has on sales. This is the same chart that is
created in the Combo chart Tutorial. Then you'll format the dual Y -axes.
Create a chart with two Y -axes
1. Create a new line chart that tracks Sales > Gross Margin last year % by Time > FiscalMonth.
2. Sort the visual by month by selecting the ellipses (...) and choosing Sort by Month

[NOTE ]: For help sorting by month, see sorting by other criteria

In January GM% was 35%, peaked at 45% in April, dropped in July and peaked again in August. Will we see
a similar pattern in sales last year and this year?
3. Add This Year Sales > Value and Last Year Sales to the line chart. The scale of GM% Last Year (the blue
line running along the 0M% gridline) is much smaller than the scale of Sales which makes it difficult to
compare. And the Y -Axis label percentages are ridiculous.
4. To make the visual easier to read and interpret, convert the line chart to a Line and Stacked Column chart.

5. Drag Gross Margin Last Year % from Column Values into Line Values. What we have now is the
stacked column chart we created above plus a line chart. (Optionally, use what you learned above to format
the axes font color and size.)
Power BI creates two axes, thus allowing the datasets to be scaled differently; the left measures dollars and
the right measures percentage.

Format the secondary Y -axis

1. In the Visualizations pane, select the paint roller icon to display the formatting options.
2. Expand the Y -Axis options by selecting the down arrow.
3. Scroll through the list until you find the options for Show secondary. Toggle Show Secondary from Off
to On.
4. (Optional) Customize the two axes. If you switch Position for either the column axis or the line axis, then
the two axes switch sides.
Add titles to both axes
With a visualization this complicated, it helps to add axes titles. Titles help your colleagues understand the story
your visualization is telling.
1. Toggle Title to On for Y -Axis (Column) and the Y -Axis (Line).
2. Set Style to Show title only.
3. Your Combo chart now displays dual axes, both with titles.

For more information, see Tips and tricks for color formatting, labeling, and axis properties.

Considerations and troubleshooting

If the X-axis is categorized by the report owner as a date type, the Type option will display and you can select
between continuous or categorical.

Next steps
More about Visualizations in Power BI reports
Customize titles, backgrounds, and legends
Customize colors and axis properties
Power BI - Basic Concepts
More questions? Try the Power BI Community
 ArcGIS maps in Power BI service and Power BI
Desktop by Esri
2/11/2019 • 11 minutes to read • Edit Online

This tutorial is written from the point of view of a person creating an ArcGIS map. Once a creator shares an
ArcGIS map with a colleague, that colleague can view and interact with the map but not save changes. To learn
more about viewing an ArcGIS map, see Interacting with ArcGIS maps.
The combination of ArcGIS maps and Power BI takes mapping beyond the presentation of points on a map to a
whole new level. Choose from base maps, location types, themes, symbol styles, and reference layers to create
gorgeous informative map visualizations. The combination of authoritative data layers on a map with spatial
analysis conveys a deeper understanding of the data in your visualization.
While you cannot create an ArcGIS maps on a mobile device, you can view and interact with it. See Interacting
with ArcGIS maps.

TIP
GIS stands for Geographic Information Systems.

The example below uses a dark gray canvas to show regional sales as a heatmap against a demographic layer of
2016 median disposable income. As you'll see as you read on, using ArcGIS maps offers almost limitless enhanced
mapping capability, demographic data, and even-more compelling map visualizations so you can tell your best
story.

TIP
Visit esri's page on Power BI to see many examples and read testimonials. And then see esri's ArcGIS Maps for Power BI
Getting Started page.

User consent
ArcGIS Maps for Power BI is provided by Esri (www.esri.com). Your use of ArcGIS Maps for Power BI is subject by
Esri's terms and privacy policy. Power BI users wishing to use the ArcGIS Maps for Power BI visuals, need to
accept the consent dialog.
Resources
Terms
Privacy Policy
ArcGIS Maps for Power BI product page

Enable ArcGIS map

ArcGIS maps are currently available in Power BI service, Power BI Desktop, and Power BI mobile. This article
provides instructions for the service and for Desktop.
Enable the ArcGIS map in Power BI service (app.powerbi.com)
This tutorial uses the Retail Analysis sample. To enable ArcGIS Maps for Power BI:
1. From the top right section of the menubar, select the cog icon and open Settings

2. Select the ArcGIS Maps for Power BI checkbox. You'll need to restart Power BI after you make the
selection.

3. Open a report in Editing view and select the ArcGIS Maps for Power BI icon from the Visualizations pane.

4. Power BI adds an empty ArcGIS map template to the report canvas.

Create an ArcGIS map visual
Watch Will create a few different ArcGIS map visualizations and then use the steps below to try it out yourself
using the Retail Analysis sample.
https://www.youtube.com/embed/EKVvOZmxg9s
1. From the Fields pane, drag a data field to the Location or Latitude and/or Longitude buckets. In this
example we're using Store > City.

NOTE
ArcGIS Maps for Power BI will automatically detect if the fields you've selected are best viewed as a shape or a point
on a map. You can adjust the default in the settings (see below).

2. Convert the visualization to an ArcGIS map by selecting the template from the Visualizations pane .
3. From the Fields pane, drag a measure to the Size bucket to adjust how the data is shown. In this example
we're using Sales > Last Year Sales.
Settings and formatting for ArcGIS maps
To access ArcGIS Maps for Power BI formatting features:
1. Access additional features by selecting the ellipsis in the top right corner of the visualization and choosing
Edit.

The available features display across the top of the visualization. Each feature, when selected, opens a task
pane that provides detailed options.

NOTE
For more information about the settings and features, see Detailed documentation below.

2. To return to the report, select Back to Report from the top-left corner of your report canvas.

Detailed documentation
Esri provides comprehensive documentation on the feature set of ArcGIS Maps for Power BI.
Features overview
Base Maps
Four base maps are provided: Dark Gray Canvas, Light Gray Canvas, OpenStreetMap, and Streets. Streets is
ArcGIS's standard base map.
To apply a base map select it in the task pane.

Location type
ArgGIS Maps for Power BI automatically detects the best way to show data on the map. It selects from Points or
Boundaries. The Location type options allow you to fine tune these selections.

Boundaries will only work if your data contains standard geographic values. Esri automatically figures out the
shape to show on the map. Standard geographic values include countries, provinces, zip codes, etc. But just like
with GeoCoding, Power BI may not detect the field should be a boundary by default, or it may not have a
boundary for your data.
Map theme
Four map themes are provided. Location Only and Size themes are automatically chosen based on the fields you
bind to the location and added to the Size bucket in the Power BI Fields pane. We're currently using Size, so let's
change to Heat map.
 THEME DESCRIPTION

Location Only Plots data points or filled boundaries on the map based on
the settings in Location Type.

Heat Map Plots an intensity plot of data on the map.

Size Plots data points on the map based that are sized based on
the value in the size bucket in the fields pane.

Clustering Plot the count of data points in regions on the map.

Symbol style
Symbol styles enable you to fine tune how data is presented on the map. Symbol styles are context sensitive based
on the selected Location type and Map theme. The example below shows Location type set to Size and several
adjustments to transparency, style and size.

Pins
Call attention to points on your map by adding pins.
1. Select the Pins tab.
2. Type keywords (such as addresses, places, and point of interest), in the search box and select from the
dropdown. A symbol appears on the map, and the map automatically zooms to the location. Search results
are saved as location cards in the Pins pane. You can save up to 10 location cards.
3. Power BI adds a pin to that location and you can change the color of the pin.

4. Add and delete pins.

Drive time
The Drive time pane lets you select a location and then determine what other map features are within a specified
radius or driving time.

1. Select the Drive time tab and choose the single or multi select tool. Single select the pin for Washington
 D.C.

TIP
It's easier to select a location if you zoom in on the map (using the + icon).

2. Let's say you're flying into Washington D.C. for a few days and want to figure out which stores are within a
reasonable driving distance. Change Search area to Radius and Distance to 50 miles and select OK.

3. The radius is shown in purple. Select any location to display its details. Optionally, format the radius by
changing color and outline.

Reference Layer
Reference layer - Demographics
ArcGIS Maps for Power BI provides a selection of demographic layers that help contextualize data from Power BI.
1. Select the Reference layer tab and choose Demographics.
2. Each layer listed has a checkbox. Add a checkmark to add that layer to the map. In this example we've added
average household income.

3. Each layer is interactive as well. Just as you can hover over a bubble to see the details, you can click a
shaded area on the map to see the details.

Reference layer - ArcGIS

ArcGIS Online provides the ability for organizations to publish public web maps. Additionally, Esri provides a
curated set of web maps through Living Atlas. In the ArcGIS tab, you can search all public web maps or Living
Atlas maps, and add them to the map as reference layers.
1. Select the Reference layer tab and choose ArcGIS.
2. Enter search terms and then select a map layer. In this example we've chosen USA Congressional districts.
3. To see the details, select a shaded area to open the Select from reference layer: Use the reference layer
selection tool to selection boundaries or objects on the reference layer.

Selecting Data points

ArcGIS Maps for Power BI allows three selection modes.
Change the selection mode using switch:

Select individual data points.

Draws a rectangle on the map and selects the contained data points.

Allows boundaries or polygons within reference layers to be used to select contained data points.

NOTE
A maximum of 250 data points can be selected at a time.

Getting help
Esri provides comprehensive documentation on the feature set of ArcGIS Maps for Power BI.
You can ask questions, find the latest information, report issues, and find answers on the Power BI community
thread related to ArcGIS Maps for Power BI.
If you have a suggestion for an improvement, please submit it to Power BI's ideas list.
Managing use of ArcGIS Maps for Power BI within your organization
Power BI provides the ability for users, tenant administrators, and IT administrators to manage whether to use
ArcGIS Maps for Power BI.
User options In Power BI Desktop, users can stop using ArcGIS Maps for Power BI by disabling it on the security
tab in Options. When disabled, ArcGIS Maps will not load by default.

In Power BI service, users can stop using ArcGIS Maps for Power BI by disabling it on the ArcGIS Maps for Power
BI tab in user Settings. When disabled, ArcGIS Maps will not load by default.
Tenant admin options In PowerBI.com, tenant administrators can prevent all tenant users from using ArcGIS
Maps for Power BI by disabling. When this happens, Power BI will no longer see the ArcGIS Maps for Power BI
icon in the visualizations pane.

IT Administrator options Power BI Desktop supports using Group Policy to disable ArcGIS Maps for Power BI
across an organization's deployed computers.

ATTRIBUTE VALUE

key Software\Policies\Microsoft\Power BI Desktop</td>

valueName EnableArcGISMaps

A value of 1 (decimal) enables ArcGIS Maps for Power BI.

A value of 0 (decimal) disable ArcGIS Maps for Power BI.

Considerations and Limitations

ArcGIS Maps for Power BI is available in the following services and applications:

SERVICE/APP AVAILABILITY

Power BI Desktop Yes

Power BI service (PowerBI.com) Yes

Power BI mobile applications Yes

Power BI publish to web No

Power BI Embedded No

Power BI service embedding (PowerBI.com) No

In services or applications where ArcGIS Maps for Power BI is not available, the visualization will show as an
empty visual with the Power BI logo.
When geocoding street addresses, only the first 1500 addresses are geocoded. Geocoding place names or
countries is not subject to the 1500 address limit.
How do ArcGIS Maps for Power BI work together? ArcGIS Maps for Power BI is provided by Esri
(www.esri.com). Your use of ArcGIS Maps for Power BI is subject by Esri's terms and privacy policy. Power BI
users wishing to use the ArcGIS Maps for Power BI visuals, need to accept the consent dialog (see User Consent
for details). Using Esri’s ArcGIS Maps for Power BI is subject to Esri’s Terms and Privacy Policy, which are also
linked to from the consent dialog. Each user must consent prior to using ArcGIS Maps for Power BI for the first
time. Once the user accepts the consent, data bound to the visual is sent to Esri’s services at least for geocoding,
meaning transforming location information into latitude and longitude information that can be represented in a
map. You should assume any data bound to the data visualization can be sent to Esri’s services. Esri provides
services like base maps, spatial analytics, geocoding, etc. The ArcGIS Maps for Power BI visual interacts with these
services using an SSL connection protected by a certificate provided and maintained by Esri. Additional
information about ArcGIS Maps for Power BI can be obtained from Esri’s ArcGIS Maps for Power BI product
page.
When a user signs up for a Plus subscription offered by Esri through ArcGIS Maps for Power BI, they are entering
into an direct relationship with Esri. Power BI does not send personal information about the user to Esri. The user
signs in to and trusts an Esri provided AAD application using their own AAD identity. By doing so, the user is
sharing their personal information directly with Esri. Once the user adds Plus content to an ArcGIS Maps for
Power BI visual, other Power BI users also need a Plus subscription from Esri to view or edit that content.
For technical detailed questions about how Esri’s ArcGIS Maps for Power BI works, reach out to Esri through their
support site.
Is there any charge for using ArcGIS Maps for Power BI?
The ArcGIS Map for Power BI is available to all Power BI users at no additional cost. It is a component provided by
Esri and your use is subject to the terms and privacy policy provided by Esri as noted earlier in this article.
I'm getting an error message in Power BI Desktop about my cache being full
This is a bug that is being addressed. In the meantime, to clear your cache, please try to delete files at this location:
C:\Users\AppData\Local\Microsoft\Power BI Desktop\CEF and then restart Power BI.
Does ArcGIS Maps for Power BI support Esri Shapefiles?
ArcGIS Maps for Power BI automatically detects standard boundaries like countries/regions, states/provinces, and
zip/postal codes. If you need to provide your own shapes you can do so using the Shape Maps for Power BI
Desktop (Preview ).
Can I view my ArcGIS maps offline?
No, Power BI needs network connectivity to display the maps.
Can I connect to my ArcGIS Online account from Power BI?
Not yet. Vote for this idea and we'll send you an email when we start working on this feature.

Next steps
Interacting with an ArcGIS map that has been shared with you
Blog post announcing availability of ArcGIS maps for Power BI
More questions? Try asking the Power BI Community
 Basic Area chart
1/14/2019 • 2 minutes to read • Edit Online

The basic area chart (aka layered area chart.) is based on the line chart. The area between axis and line is filled with
colors to indicate volume.
Area charts emphasize the magnitude of change over time, and can be used to draw attention to the total value
across a trend. For example, data that represents profit over time can be plotted in an area chart to emphasize the
total profit.

When to use a basic area chart

Basic area charts are a great choice:
to see and compare the volume trend across time series
for individual series representing a physically countable set
Prerequisites
Power BI service
Retail Analysis sample
To follow along, sign in to Power BI and select Get Data > Samples > Retail Analysis Sample > Connect and
choose Go to dashboard.

Create a basic area chart

1. From the "Retail Analysis Sample" dashboard, select the Total Stores tile to open the "Retail Analysis
Sample" report.
2. Select Edit Report to open the report in Editing View.
3. Add a new report page by selecting the yellow plus icon (+) at the bottom of the report.
4. Create an area chart that displays this year's sales and last year's sales by month.
a. From the FIELDS pane, select Sales > Last Year Sales, and This Year Sales > Value.
 b. Convert the chart to a basic area chart by selecting the Area chart icon from the Visualizations pane.

c. Select Time > Month to add it to the Axis well.

d. To display the chart by month, select the ellipses (top right corner of the visual) and choose Sort by
month. To change the sort order, select the ellipses again and select either Sort ascending or Sort
descending.

Highlighting and cross-filtering

For information about using the Filters pane, see Add a filter to a report.
To highlight one particular area in your chart, select that area or its top border. Unlike other visualization types, if
there are other visualizations on the same page, highlighting a basic area charts does not cross-filter the other
visualizations on the report page. However, area charts are a target for cross-filtering triggered by other
visualizations on the report page.
1. Try it out by selecting your area chart and copying it to another report page (CTRL -C and CTRL -V ).
2. Select one of the shaded areas and then the other shaded area. You'll notice no impact on the other
visualizations on the page.
3. Now select an element on one of the other visualizations on the page, like a column chart bar or a month on
a line chart. Notice the impact on the area chart -- it gets filtered.

To learn more, see Visual interactions in reports

Considerations and troubleshooting

Make the report more accessible for people with disabilities
Basic area charts are not effective for comparing the values due to the occlusion on the layered areas. Power BI
uses transparency to indicate the overlap of areas. However, it only works well with two or three different areas.
When you need to compare trend to more than three measures, try using line charts. When you need to
compare volume to more than three measures, try using treemap.

Next step
Reports in Power BI
 Card visualizations
1/30/2019 • 3 minutes to read • Edit Online

Sometimes a single number is the most important thing you want to track in your Power BI dashboard or report,
such as total sales, market share year over year, or total opportunities. This type of visualization is called a Card. As
with almost all of the native Power BI visualizations, Cards can be created using the report editor or Q&A.

Create a card using the report editor

These instructions use the Retail Analysis Sample. To follow along, download the sample for Power BI service
(app.powerbi.com) or Power BI Desktop.
1. Start on a blank report page and select the Store > Open store count field. If you're using Power BI
service, you'll need to open the report in Editing View.
Power BI creates a column chart with the one number.

2. In the Visualizations pane, select the Card icon.

3. Hover over the card and select the pin icon to add the visualization to the dashboard.
4. Pin the tile to an existing dashboard or to a new dashboard.
Existing dashboard: select the name of the dashboard from the dropdown.
New dashboard: type the name of the new dashboard.
5. Select Pin.
A Success message (near the top right corner) lets you know the visualization was added, as a tile, to your
dashboard.

6. Select Go to dashboard. There, you can edit and move the pinned visualization.

Create a card from the Q&A question box

The Q&A question box is the easiest way to make a Card. The Q&A question box is available in Power BI service
from a dashboard or report and in Desktop report view. The steps below describe creating a Card from a Power BI
service dashboard. If you'd like to create a card using Q&A in Power BI Desktop, follow these instructions for the
Q&A preview for Desktop reports.
1. Create a dashboard and get data. This example uses the Opportunity Analysis sample.
2. At the top of your dashboard, start typing what you want to know about your data in the question box.

TIP
From a Power BI service report, in Editing view, select Ask a question from the top menubar. From a Power BI Desktop
report, find some open space in a report and double-click to open a question box.

3. For example, type "number of opportunities" in the question box.

 The question box helps you with suggestions and restatements, and finally displays the total number.

4. Select the pin icon in the upper-right corner to add the card to a dashboard.

5. Pin the card, as a tile, to an existing dashboard or to a new dashboard.

Existing dashboard: select the name of the dashboard from the dropdown. Your choices will be limited to
only those dashboards withing the current workspace.
New dashboard: type the name of the new dashboard and it will be added to your current workspace.
6. Select Pin.
A Success message (near the upper right corner) lets you know the visualization was added, as a tile, to
your dashboard.

7. Select Go to dashboard to see the new tile. There, you can rename, resize, add a hyperlink, and reposition
the tile, and more on your dashboard.
Considerations and troubleshooting
If you do not see a question box at all, contact your system or tenant administrator.
If you are using Desktop and double-clicking empty space in a report doesn't open Q&A, you may need to
enable it. Select File > Options and Settings > Options > Preview features > Q&A and restart Desktop.

Format a card
You have many options for changing labels, text, color and more. The best way to learn is to create a card and then
explore the Formatting pane. Here are just a few of the formatting options available.
1. Start by selecting the paintroller icon to open the Formatting pane.

2. Expand Data label and change the color, size, and font family. If you had thousands of stores, you could use
Display units to show the number of stores by thousands and control the decimal places as well. For
example, 125.8K instead of 125,832.00.
3. Expand Category label and change the color and size.
4. Expand Background and move the slider to On. Now you can change the background color and
transparency.

5. Continue to explore the formatting options until your card is exactly how you'd like it.

Next steps
Combo charts in Power BI
Visualization types in Power BI
 Combo Chart in Power BI
1/14/2019 • 3 minutes to read • Edit Online

In Power BI, a combo chart is a single visualization that combines a line chart and a column chart. Combining the
2 charts into one lets you make a quicker comparison of the data.
Combo charts can have one or two Y axes.

When to use a Combo Chart

Combo charts are a great choice:
when you have a line chart and a column chart with the same X axis.
to compare multiple measures with different value ranges.
to illustrate the correlation between two measures in one visualization.
to check whether one measure meet the target which is defined by another measure
to conserve canvas space.
Prerequisites
Combo charts are available in Power BI service and Power BI Desktop. This tutorial uses Power BI service to
create a Combo chart. To follow along, open Power BI service and connect to the "Retail Analysis" sample
instructions below ).

Create a basic, single-axis, Combo Chart

Watch Will create a combo chart using the Sales and Marketing sample.
https://www.youtube.com/embed/lnv66cTZ5ho?list=PL1N57mwBHtN0JFoKSR0n-tBkUJHeMP2cP
To create your own combo chart, sign in to Power BI service and select Get Data > Samples > Retail Analysis
Sample > Connect >Go to dashboard.
1. From the "Retail Analysis Sample" dashboard, select the Total Stores tile to open the "Retail Analysis
Sample" report.
2. Select Edit Report to open the report in Editing View.
3. Add a new report page.
4. Create a column chart that displays this year's sales and gross margin by month.
a. From the Fields pane, select Sales > This Year Sales > Value.
b. Drag Sales > Gross Margin This Year to the Value well.
c. Select Time > FiscalMonth to add it to the Axis well.
5. Select the ellipsis (...) in the upper-right corner of the visualization, and select Sort by > FiscalMonth. To
change the sort order, select the ellipsis again and choose either Sort ascending or Sort descending.
6. Convert the column chart to a combo chart. There are two combo charts available: Line and stacked
column and Line and clustered column. With the column chart selected, from the Visualizations pane
select the Line and clustered column chart.

7. From the Fields pane, drag Sales > Last Year Sales to the Line Values bucket.

Your combo chart should look something like this:

Create a combo chart with two axes

In this task, we'll compare gross margin and sales.
1. Create a new line chart that tracks Gross Margin last year % by Month. Select the ellipsis to sort it by
Month and Ascending.
In January GM% was 35%, peaked at 45% in April, dropped in July and peaked again in August. Will we
see a similar pattern in sales last year and this year?
2. Add This Year Sales > Value and Last Year Sales to the line chart. The scale of Gross Margin Last Year
% is much smaller than the scale of Sales which makes it difficult to compare.

3. To make the visual easier to read and interpret, convert the line chart to a Line and Stacked Column chart.

4. Drag Gross Margin Last Year % from Column Values into Line Values. Power BI creates two axes, thus
allowing the datasets to be scaled differently; the left measures sales dollars and the right measures
percentage. And we see the answer to our question; yes, we do see a similar pattern.
Add titles to the axes
1. Select the paint roller icon to open the Formatting pane.
2. Select the down arrow to expand the Y -axis options.
3. For Y -Axis (Column), set Position to Left, set Title to On, Style to Show title only, and Display as
Millions.

4. Under Y -Axis (Column), scroll down and ensure that Show Secondary is set to On. This displays options
for formatting the line chart portion of the combo chart.
5. For Y -Axis (Line), leave Position as Right, turn Title to On, and set Style to Show title only.
Your combo chart now displays dual axes, both with titles.

6. Optionally, modify the text font, size, and color and set other formatting options to improve the display and
readability of the chart.
From here you might want to:
Add the combo chart as a dashboard tile.
Save the report.
Make the report more accessible for people with disabilities.

Cross-highlighting and cross-filtering

Highlighting a column or line in a combo chart cross-highlights and cross-filters the other visualizations on the
report page... and vice versa. Use visual interactions to change this default behavior.

Next steps
Doughnut charts in Power BI
Visualization types in Power BI
 Doughnut charts in Power BI
1/14/2019 • 2 minutes to read • Edit Online

A doughnut chart is similar to a pie chart in that it shows the relationship of parts to a whole. The only difference is
that the center is blank and allows space for a label or icon.

Create a doughnut chart

These instructions use the Retail Analysis Sample to create a doughnut chart that displays this year's sales by
category. To follow along, download the sample for Power BI service or Power BI Desktop.
1. Start on a blank report page. If you're using Power BI service, make sure you open the report in Editing
View.
2. From the Fields pane, select Sales > Last Year Sales.

3. From the Visualizations pane, select the icon for doughnut chart to convert your bar chart to a
doughnut chart. If Last Year Sales is not in the Values area, drag it there.

4. Select Item > Category to add it to the Legend area.

5. Optionally, adjust the size and color of the chart's text.

Considerations and troubleshooting

The sum of the doughnut chart values must add up to 100%.
Too many categories make it difficult to read and interpret.
Doughnut charts are best used to compare a particular section to the whole, rather than comparing individual
sections with each other.
Next steps
Funnel charts in Power BI
Visualization types in Power BI
 Filled maps (choropleths) in Power BI
2/13/2019 • 4 minutes to read • Edit Online

A filled map uses shading or tinting or patterns to display how a value differs in proportion across a geography or
region. Quickly display these relative differences with shading that ranges from light (less-frequent/lower) to dark
(more-frequent/more).

What is sent to Bing

Power BI integrates with Bing to provide default map coordinates (a process called geo-coding). When you create a
map visualization in Power BI service or Power BI Desktop, the data in the Location, Latitude, and Longitude
buckets (that is being used to create that visualization) is sent to Bing.
You, or your administrator, may need to update your firewall to allow access to the URLs Bing uses for geocoding.
Those URLs are:
https://dev.virtualearth.net/REST/V1/Locations
https://platform.bing.com/geo/spatial/v1/public/Geodata
https://www.bing.com/api/maps/mapcontrol
For more information about the data being sent to Bing, and for tips to increase your geo-coding success, see Tips
and tricks for map visualizations.

When to use a filled map

Filled maps are a great choice:
to display quantitative information on a map.
to show spatial patterns and relationships.
when your data is standardized.
when working with socioeconomic data.
when defined regions are important.
to get an overview of the distribution across the geographic locations.
Prerequisites
Power BI service or Power BI Desktop
Sales and Marketing Sample
To follow along, the tutorial uses Power BI service, not Power BI Desktop.

Create a basic filled map

In this video, Kim creates a basic map and converts it to a filled map.
https://www.youtube.com/embed/ajTPGNpthcg
Get data and add a new blank page to the report
1. To create your own filled map, download the Sales and Marketing sample by signing in to Power BI and
selecting Get Data > Samples > Sales and Marketing > Connect.
2. When the success message appears, close it and select the Reports tab. Then choose Sales and Marketing
Sample to open the report.

3. Power BI opens the report. Select Edit report to open the report in Editing View.
4. Add a new page by selecting the yellow plus sign at the bottom of the report canvas.

Create a filled map

1. From the Fields pane, select the Geo > State field.

2. Convert the chart to a filled map. Notice that State is now in the Location well. Bing Maps uses the field in
the Location well to create the map. The location can be a variety of valid locations: countries, states,
counties, cities, zip codes or other postal codes etc. Bing Maps provides filled map shapes for locations
around the world. Without a valid entry in the Location well, Power BI cannot create the filled map.
3. Filter the map to display only the continental United States.
a. At the bottom of the Visualizations pane, look for the Filters area.
b. Hover over State and click the expand chevron

c. Place a check mark next to All and remove the check mark next to AK.

4. Select SalesFact > Sentiment to add it to the Color saturation well. The field in the Color saturation
well controls the map shading.

5. The filled map is shaded in green and red, with red representing the lower sentiment numbers and green
representing the higher, more-positive sentiment. Here I've highlighted the state of Wyoming (WY ) and see
that Sentiment is very good, 74.

6. Save the report.

Adjust the color formatting

Power BI gives you plenty of control over the appearance of your filled map.
1. Select the paintroller icon to open the Formatting pane.

2. Select Data colors to display color options.

3. Set the Minimum and Maximum colors to yellow and blue. And add Minimum and Maximum values, based
on your data. Play around with these controls until you get the look you want.

Highlighting and cross-filtering

For information about using the Filters pane, see Add a filter to a report.
Highlighting a location in a filled Map cross-filters the other visualizations on the report page... and vice versa.
1. To follow along, first save this report by selecting File > Save.
2. Copy the filled map using CTRL -C.
3. From the bottom of the report canvas, select the Sentiment tab to open the Sentiment report page.
4. Move and resize the visualizations on the page to make some room, then CTRL -V paste the filled map from
the previous report.

5. On the filled map, select a state. This highlights the other visualizations on the page. Selecting Texas, for
example, shows me that Sentiment is 74, Texas is in the Central District #23.

6. Select a data point on the VanArsdel - Sentiment by Month line chart. This filters the filled map to show
Sentiment data for VanArsdel and not their competition.
Considerations and troubleshooting
Map data can be ambiguous. For example, there's a Paris, France, but there's also a Paris, Texas. Your geographic
data is probably stored in separate columns – a column for city names, a column for state or province names, etc. –
so Bing may not be able to tell which Paris is which. If your dataset already contains latitude and longitude data,
Power BI has special fields to help make the map data unambiguous. Just drag the field that contains your latitude
data into the Visualizations > Latitude area. And do the same for your longitude data.
If you have permissions to edit the dataset in Power BI Desktop, watch this video for help addressing map
ambiguity.
https://www.youtube.com/embed/Co2z9b-s_yM
If you do not have access to latitude and longitude data, follow these instructions to update your dataset.
For more help with Map visualizations, see Tips and tricks for map visualizations.

Next steps
Shape map
Visualization types in Power BI
 Funnel charts
1/14/2019 • 3 minutes to read • Edit Online

A funnel chart helps you visualize a linear process that has sequential connected stages. For example, a sales
funnel that tracks customers through stages: Lead > Qualified Lead > Prospect > Contract > Close. At a glance,
the shape of the funnel conveys the health of the process you're tracking.
Each funnel stage represents a percentage of the total. So, in most cases, a funnel chart is shaped like a funnel --
with the first stage being the largest, and each subsequent stage smaller than its predecessor. A pear-shaped
funnel is also useful -- it can identify a problem in the process. But typically, the first stage, the "intake" stage, is the
largest.

When to use a funnel chart

Funnel charts are a great choice:
when the data is sequential and moves through at least 4 stages.
when the number of "items" in the first stage is expected to be greater than the number in the final stage.
to calculate potential (revenue/sales/deals/etc.) by stages.
to calculate and track conversion and retention rates.
to reveal bottlenecks in a linear process.
to track a shopping cart workflow.
to track the progress and success of click-through advertising/marketing campaigns.

Working with funnel charts

Funnel charts:
Can be pinned from reports and from Q&A.
Can be sorted.
Support multiples.
Can be highlighted and cross-filtered by other visualizations on the same report page.
Can be used to highlight and cross-filter other visualizations on the same report page.

Create a basic funnel chart

Watch this video to see Will create a Funnel chart using the Sales and Marketing sample.
https://www.youtube.com/embed/qKRZPBnaUXM
Now create your own funnel chart that shows the number of opportunities we have in each of our sales stages.
These instructions use the Opportunity Analysis Sample. To follow along, download the sample for Power BI
service (app.powerbi.com) or Power BI Desktop.
1. Start on a blank report page and select the SalesStage > Sales Stage field. If you're using Power BI
service, make sure you open the report in Editing View.

2. Convert the chart to a funnel. Notice that Sales Stage is in the Group well.
3. From the Fields pane, select Fact > Opportunity Count.

4. Hovering over a bar displays a wealth of information.

The name of the stage
Number of opportunities currently in this stage
Overall conversion rate (% of Lead)
Stage-to-stage (aka Drop Rate) which is the % of the previous stage (in this case, Proposal
Stage/Solution Stage)

5. Add the Funnel as a dashboard tile.

6. Save the report.
Highlighting and cross-filtering
For information about using the Filters pane, see Add a filter to a report.
Highlighting a bar in a funnel cross-filters the other visualizations on the report page... and vice versa. To follow
along, add a few more visuals to the report page that contains the funnel chart.
1. On the funnel, select the Proposal bar. This cross-highlights the other visualizations on the page. Use CTRL
to multi-select.

2. To set preferences for how visuals cross-highlight and cross-filter each other, see Visual interactions in
Power BI

Create a funnel chart using Q&A

Open the Opportunity Analysis Sample dashboard, or any other dashboard that has at least one visualization
pinned from the Opportunity Analysis Sample dataset. When you type a question in Q&A, Power BI searches for
answers in all the datasets that are associated with (have tiles pinned to) the selected dashboard. For more
information see, Power BI - basic concepts.
1. On the Opportunity Analysis Sample dashboard, begin typing your question in the Q&A question box.

2. Be sure to add "as funnel" so Power BI knows which visualization type you'd prefer.

Next steps
Gauges in Power BI
Visualization types in Power BI
 Key influencers visualization
3/5/2019 • 18 minutes to read • Edit Online

The key influencers visual helps you understand the factors that drive a metric you are interested in. It analyzes
your data, ranks the factors that matter, and displays them as key influencers. For example, you're interested in
figuring out what influences employee turnover (churn). One factor may be employment contract length and
another may be employee age.

When to use key influencers?

The key influencer visual is a great choice:
To see which factors impact the metric being analyzed.
To contrast the relative importance of these factors. For example, do short-term contracts have more impact
on churn than long-term contracts?

Key influencer requirements

The metric you are analyzing must be a categorical field.

Features of the key influencer visual

1. Tabs - select a tab to switch between views. Key influencers shows you the top contributors to the selected
metric value. Top segments shows you the top segments that contribute to the selected metric value. A
segment is made up of a combination of values. For example, one segment may be consumers who have
been customers for at least twenty years and live in the west region.
2. Dropdown - value of the metric being investigated. In this example we're looking at the metric rating and
the value we've selected is low.
3. Restatement - helps us interpret the visual in the left pane.
4. Left pane - the left pane contains one visual. In this case, the left pane shows us a list of the top key
influencers.
5. Restatement - helps us interpret the visual in the right pane.
6. Right pane - the right pane contains one visual. In this case, the column chart displays all the values for the
key influencer, Theme that is selected in the left pane. The specific value (Usability) from the left pane is
in green and all the other values for Theme are in black.
7. Average line - the average is calculated for all the other possible values for Theme except usability. So the
calculation applies to all the values in black. It tells us what percentage of the other Themes gave us a low
rating. In other words, when a rating is given by a customer, that customer also describes the reason or
theme for the rating. Some themes are usability, speed, security, etc. Theme is Usability is the second
highest key influencer for a low rating, according to our visual in the left pane. If we average all the other
themes, and their contribution to a rating of low, we get the result seen here in red. Of all the other themes
given, only 11.35% of those are higher than usability.
8. Checkbox - only show values that are influencers.

Create a key influencers visual

Watch this video to learn how to create a key influencers visual and then follow the steps below to create one
yourself.
https://www.youtube.com/embed/fDb5zZ3xmxU
Our Product Manager wants to figure out which factors lead customers to leave negative reviews about our cloud
service. To follow along, open the Customer Feedback PBIX file in Power BI Desktop. You can also download the
Customer Feedback Excel file for Power BI service or Power BI Desktop.

NOTE
The Customer Feedback dataset is based on [Moro et al., 2014] S. Moro, P. Cortez and P. Rita. A Data-Driven Approach to
Predict the Success of Bank Telemarketing. Decision Support Systems, Elsevier, 62:22-31, June 2014

1. Open the report and select the key influencers icon.

2. Drag the metric you want to investigate into the Analyze field. The Analyze field supports categorical
(non-continuous) variables only. Since we are interested in looking at what drives a customer rating of our
 service to be Low, we select Customer Table > Rating.
3. Next, drag fields that you think could influence Rating into the Explain By well. You can drag in as many
fields as you’d like. In this case, we are starting out with:
Country-Region
Role in Org
Subscription Type
Company Size
Theme
4. Since we're interested in negative ratings, select Low in the dropdown for What influences Rating to be.

The analysis runs on the table level of the field being analyzed. In this case, we are interested in the Rating metric,
which is defined at a customer level (each customer has either given a high score or low score). All our explanatory
factors have to be defined at the customer level for the visual to make use of them.
In the example above, all of our explanatory factors have either a one-to-one or many-to-one relationship with our
metric. For example, each score has exactly one theme associated with it (what was the main theme of the
customer review ). Similarly, customers come from one country, have one membership type and one role in their
organization. Our explanatory factors are therefore already attributes of a customer and no transformations are
needed – the visual can make immediate use of them.
Later on in the tutorial we will look at more complex examples where we have one-to-many relationships. In those
cases, the columns have to first be aggregated down to the customer level before the analysis can be run.
Measures and aggregates used as explanatory factors are also evaluated at the table level of the Analyze metric
and we will see some examples later in this article.

Interpreting categorical key influencers

Let's take a look at our key influencers for low ratings.
Top single factor influencing likelihood of a low rating
In our organization, we have three roles: consumers, administrators, and publishers. We see that being a consumer
is the top factor contributing to a low rating.

More precisely, our consumers are 2.57x more likely to give us a negative score. The key influencer chart lists Role
in Org is consumer first in the list on the left. By selecting Role in Org is consumer, Power BI shows us
additional details on the pane to the right -- the comparative impact of each role on likelihood of a low rating.
14.93% of consumers give a low score
On average, all other roles give a low score 5.78% of the time
Consumers are therefore 2.57x more likely to give a low score compared to all other roles (difference between
green bar and red dotted line)
Second single factor influencing likelihood of a low rating
The key influencers visual is able to compare and rank factors from many different variables. Our second influencer
has nothing to do with Role in Org. Select the second influencer in the list; Theme is usability.
Here we see that the second most important factor is related to the theme of the customer’s review. Customers
who commented about the usability of the product were 2.21x more likely to give a low score compared to
customers who commented on other themes, such as reliability, design, or speed.
You can see between the visuals that the average (red dotted line) has changed from 5.78% to 11.34%. The average
is dynamic as it is based on the average of all other values. In the case of the first influencer, the average excluded
the customer role whilst in the case of the second, it excluded the usability theme.
Ticking the box at the bottom of the visual will result in the visual filtering to only the influential values (in this case
roles that drive a low score). We therefore go from looking at 12 themes to the four Power BI has identified as
driving low ratings.

Interacting with other visuals

Every time a user clicks on a slicer, filter, or other visual on the canvas, the Key influencers visual reruns its analysis
on the new portion of data. For example, let’s drag Company Size into the report and use it as a slicer. We want to
see if the key influencers for our enterprise customers (company size is larger than 50,000) are different than the
general population.
Selecting >50,000 reruns the analysis and we can see that the influencers have changed. For large enterprise
customers, the top influencer for low ratings have a Theme related to security. We may want to investigate
further, to see if there are specific security features our large customers are unhappy about.

Interpreting continuous key influencers

So far we have used the visual to explore how different categorical fields influence low ratings. It is also possible to
have continuous factors (for example, age, height, price) go into ‘Explain by’. Let’s look at what happens if we drop
‘Tenure’ from the Customer table into ‘Explain by’. Tenure depicts how long the customer has been using the
service.
We find that as Tenure increases, the likelihood of receiving a lower rating also increases. This trend suggests that
our longer term customers are in fact more likely to give a negative score, which is an interesting insight and one I
may want to follow up on later.
The visualization tells us that every time tenure goes up by 13.44 months, on average the likelihood of a low rating
increases by 1.23x. In this case, 13.44 months depict the standard deviation of tenure. So the insight we receive
looks at how increasing tenure by a standard amount (the standard deviation of tenure) impacts the likelihood of
receiving a low rating.
The scatterplot on the right-hand side plots the average % of low ratings for each value of tenure and includes a
trend line to highlight the slope.
Interpreting measures/aggregate as key influencers
Finally, users are also able to use measures and aggregates as explanatory factors inside their analysis. For
example, we may want to see what impact the count of customer support tickets or the average duration of an
open ticket has on the score we receive.
In this case, we want to see if the number of support tickets a customer has influences the score they give us. We
are going to bring in the support ticket ID from the Support Ticket table. Since a customer can have multiple
support tickets, we need to aggregate the ID to the customer level. This aggregation is important, because we are
running the analysis on the customer level and so all drivers need to be defined at that level of granularity.
We are going to look at the count of IDs (so each customer row will have a count of support tickets associated with
them). In this case we see that as the count of support tickets increase, the likelihood of the rating being low goes
up 5.51x. The right-hand side visual shows us the average number of support tickets by different Rating values
(evaluated at the customer level).
Interpreting the results: top segments
Whilst the ‘Key influencers’ tab allows users to assess each factor individually, users can switch over to ‘Top
segments’ to see how a combination of factors impacts the metric they are analyzing.
Top segments initially show an overview of all the segments that have been discovered by Power BI. In the
example below we can see that six segments have been found. These segments are ranked by the % of low ratings
within the segment. We see that segment 1, for example, has 74.3% customer ratings that are lows. The higher the
bubble, the higher the proportion of low ratings. The size of the bubble of the other hand represents how many
customers are within the segment.
Selecting a bubble drills into the details of that segment. If we select Segment 1 for example, we find that it is made
up of relatively established customer (have been with us for over 29 months) that have a high number of support
tickets (greater than 4). Finally, they are not publishers (so they are either consumers or administrators).
In this group, 74.3% have given a low rating. The average customer gives a low rating 11.7% of the time so this
segment has a significantly larger proportion of low ratings (63 percentage points higher). We also find segment 1
contains approximately 2.2% of the data so it represents an addressable portion of the population.

Considerations and troubleshooting

What are the limitations for preview?
The Key influencers visual is currently in public preview, and there are several limitations users should be aware of.
Functionality that is currently not available includes:
Analyzing metrics that are aggregates/measures
Consuming the visual in Power BI Embedded
Consuming the visual on Power BI mobile apps
RLS support
Direct Query support
Live Connection support
I am seeing an error that no influencers/segments have been found. Why is that?
This error occurs when you have included fields in Explain by but no influencers have been found.
You included the metric you were analyzing in both ‘Analyze’ and ‘Explain by’ (you should remove it from
Explain by)
Your explanatory fields have too many categories with few observations. This makes it hard for the visualization
to determine which factors are influencers as it’s hard to generalize things based on a handful of observations
Your explanatory factors have a sufficient number of observations to make generalizations but the visualization
did not find any meaningful correlations to report back on
I see an error that the metric I am analyzing does not have enough data to run the analysis on. Why is
that?

The visualization works by looking at patterns in the data for one group (for example, customers who gave low
ratings) compared to other groups (for example, customers who gave high ratings). If the data in your model has
very few observations, it is hard to find patterns. If the visualization doesn’t have enough data to find meaningful
influencers it will indicate more data is needed to run the analysis. We recommend having at least 100
observations for the selected state (customers churning) and at least 10 observations for the states you are using
for comparison (customers not churning).
I am seeing an error that a field in ‘Explain by’ is not uniquely related to the table containing the metric
I am analyzing. Why is that?
The analysis runs on the table level of the field being analyzed. For example, if you are analyzing customer
feedback for your service you might have a table which tells you whether a customer gave a high rating or a low
rating. In this case, your analysis would be running at the customer table level.
If you have a related table that is defined at a more granular level than the table that contains your metric, you will
hit this error. Let’s illustrate this through an example:
You are analyzing what drives customers to give low ratings of your service
You are interested in seeing if the device on which the customer is consuming your service influence the
 reviews they give
A customer can consume the service in multiple different ways
In the example below, customer 10000000 uses both a browser and tablet to interact with the service

If you try to use the device column as an explanatory factor you will see the following error:

This is because device is not defined at the customer level – one customer can consume the service on multiple
devices. For the visualization to find patterns, the device needs to become an attribute of the customer. In this case I
have several solutions depending on my understanding of the business:
I can change the summarization of device to, for example, count if I believe the number of devices could have an
impact on the score a customer gives
I can pivot the device column to see if consuming the service on a specific device influences a customer’s rating
In this example I pivoted my data to create new columns for ‘browser, ‘mobile and ‘tablet. I can now use these in
‘Explain by’. We find that all devices turn out to be influencers with the browser having the largest impact on
customer score.
More precisely, customers who do not use the browser to consume the service are 3.79x more likely to give a low
score than those who do. We see lower down in the list that in the case of mobile the inverse is true. Customers
who use the mobile app are more likely to give a low score than those who don’t.
I see a warning that measures were not included in my analysis. Why is that?

The analysis runs on the table level of the field being analyzed. If you are analyzing customer churn you might have
a table which tells you whether a customer churned or not. In this case, your analysis would be running at the
customer table level.
Measures and aggregates are by default analyzed at that table level. If we had a measure for ‘Average monthly
spending’ that would be analyzed at the customer table level.
If the customer table does not have a unique identifier, we are not able to evaluate the measure and it is ignored by
the analysis. In order to avoid this, ensure the table with your metric (in this case the customer table) has a unique
identifier (for example, customer ID ). It’s also very easy to add an index column using Power Query.
I see a warning that the metric I am analyzing has more than 10 unique values and that this may impact
the quality of my analysis. Why is that?
The AI visualization is optimized for analyzing categories (for example, Churn is ‘Yes’ or ‘No’, Customer
Satisfaction is ‘High’, ‘Medium’ or ‘Low’ etc.) Increasing the number of categories to analyze means we have fewer
observations per category which makes it harder for the visualization to find patterns in the data.
In order to find stronger influencers, we recommend grouping similar values into a single unit. For example, if you
have a metric for price, it is likely you will obtain better results by grouping similar prices into something like
‘High’, ‘Medium’, ‘Low’ buckets, vs. using individual price points.
There are factors in my data that look like they should be key influencers but they are not. How can that
happen?
In the example below we see that customers who are consumers drive low ratings (14.93% ratings are low ).
Interestingly, the administrator role also has a high proportion of low ratings (13.42%) but is not considered an
influencer.
The reason behind this is the visualization also takes into consideration the number of datapoints when finding
influencers. In the example below we have over 29,000 consumers and 10 times fewer administrators (about
2,900). Furthermore, only 390 of them gave a low rating. The visual therefore doesn’t have enough data to
determine whether it has truly found a patter with administrator ratings of if it’s just a chance finding.

How do you calculate key influencers?

Behind the scenes, the AI visualization uses ML.NET to run a logistic regression to calculate the key influencers. A
logistic regression is a statistical model that compares different groups to each other. If we were looking at what
drives low ratings, the logistic regression would look at how customers who gave a low score differ from those
who gave a high score. If we had multiple categories (high score, neutral score, low score) we would look at how
those who gave a low rating differ from customers who did not give a low rating (how do they differ from those
who gave a high rating OR a neutral rating).
The logistic regression searches for patterns in the data, looking for how for customers who gave a low rating
might differ from those that gave a high rating. It might find, for example, that customers who have more support
tickets give a much higher % of low ratings than those who have few or no support tickets.
The logistic regression also takes into consideration how many datapoints are present. If for example customers
who play an admin role give proportionally more negative scores but there are only a handful of administrators, it
will not be considered an influential factor. This is because there are not enough datapoints available to infer a
pattern. A statistical test (Wald test) is used to determine whether a factor is considered an influencer. The visual
uses a p-value of 0.05 to determine the threshold.
How do you calculate segments?
Behind the scenes the AI Visualization uses ML.NET to run a decision tree to find interesting subgroups. The
objective of the decision tree is to end up with a subgroup of datapoints that is relatively high in the metric we are
interested in (for example, customers who gave a low rating).
The decision tree takes each explanatory factor and tries to reason which factor will give it the best ‘split’. For
example, if we filter the data to include only large enterprise customers, will that separate out customers who gave
us a high rating vs. low rating? Or perhaps it will be better if we filter the data to include only customers who
commented about security?
Once the decision tree does a split it takes that subgroup of data (for example, customers who commented on
security) and tries to figure out what would be the next best split just for that data. After each split it also takes into
consideration whether it has enough datapoints for this to be a representative group to infer a pattern from or
whether it could just be an anomaly in the data, and therefore not a real segment. (Another statistical test is applied
to check for the statistical significance of the split condition, with p-value of 0.05).
Once the decision tree finishes running, it takes all the splits (security comments, large enterprise) and creates
Power BI filters. This combination of filters is packaged up as a segment in the visual.
Why do certain factors become influencers/stop being influencers as I drag more fields into ‘Explain
By’?
The visualization evaluates all explanatory factors together. This means that whilst by itself a factor might be an
influencer, when taken into consideration with other factors it might not. Imagine we were analyzing what drives a
house price to be high with bedrooms and house size as explanatory factors:
By itself, more bedrooms may be a driver for house prices to be high
Including house size in the analysis means we now look at what happens to bedrooms whilst keeping house
size constant
If we fix house size at 1500 sq. ft, it is unlikely that continuously increasing the number of bedrooms will
dramatically increase the house price Bedrooms might not be as important of a factor as it was before house
size was considered.

Next steps
Combo charts in Power BI
Visualization types in Power BI
 High density line sampling in Power BI
1/14/2019 • 8 minutes to read • Edit Online

Beginning with the June 2017 release of the Power BI Desktop and updates to the Power BI service, a new
sampling algorithm is available that improves visuals that sample high-density data. For example, you might
create a line chart from your retail stores’ sales results, each store having more than ten thousand sales receipts
each year. A line chart of such sales information would sample data (select a meaningful representation of that
data, to illustrate how sales varies over time) from the data for each store, and create a multi-series line chart that
thereby represents the underlying data. This is common practice in visualizing high-density data. Power BI
Desktop has improved its sampling of high-density data, the details of which are described in this article.

NOTE
The High Density Sampling algorithm described in this article is available in both Power BI Desktop and the Power BI
service.

How high density line sampling works

Previously, Power BI selected a collection of sample data points in the full range of underlying data in a
deterministic fashion. For example, for high-density data on a visual spanning one calendar year, there might be
350 sample data points displayed in the visual, each of which was selected to ensure the full range of data (the
overall series of underlying data) was represented in the visual. To help understand how this happens, imagine
plotting a stock price over a one-year period,and selecting 365 data points to create a line chart visual (that's one
data point for each day).
In that situation, there are many values for a stock price within each day. Of course, there is a daily high and low,
but those could occur at any time during the day when the stock market is open. For high-density line sampling, if
the underlying data sample was taken at 10:30 AM and 12:00 PM each day, you would get a representative
snapshot of the underlying data (the price at 10:30 AM and 12:00 PM ), but it might not capture the actual high and
low of the stock price for that representative data point (that day). In that situation – and others – the sampling is
representative of the underlying data, but it doesn’t always capture important points, which in this case, would be
daily stock price highs and lows.
By definition, high-density data is sampled to create visualizations reasonably quickly that are responsive to
interactivity. Too many data points on a visual can bog it down, and can detract from the visibility of trends. So,
how the data is sampled is what drives the creation of the sampling algorithm to provide the best visualization
experience. In Power BI Desktop, the algorithm is now improved to provide the best combination of
responsiveness, representation, and clear preservation of important points in each time slice.

How the new line sampling algorithm works

The new algorithm for high-density line sampling is available for line chart and area chart visuals with a
continuous x-axis.
For a high-density visual, Power BI intelligently slices your data into high resolution chunks, and then picks
important points to represent each chunk. That process of slicing high resolution data is specifically tuned to
ensure that the resulting chart is visually indistinguishable from rendering all of the underlying data points, but
much faster and more interactive.
Minimum and maximum values for high density line visuals
For any given visualization, the following visual limitations apply:
3,500 is the maximum number of data points displayed on most visuals, regardless of the number of
underlying data points or series (see the exceptions in the following bullet list). As such, if you have 10
series with 350 data points each, the visual has reached its maximum overall data points limit. If you have
one series, it may have up to 3,500 data points if the new algorithm deems that the best sampling for the
underlying data.
There is a maximum of 60 series for any visual. If you have more than 60 series, break up the data and
create multiple visuals with 60 or fewer series each. It's good practice to use a slicer to show only segments
of the data (only certain series). For example, if you're displaying all subcategories in the legend, you could
use a slicer to filter by the overall category on the same report page.
The maximum number of data limits is higher for the following visual types, which are exceptions to the 3,500 data
point limit:
150,000 data points maximum for R visuals.
30,000 data points for custom visuals.
10,000 data points for scatter charts (scatter charts default to 3,500)
3,500 for all other visuals
These parameters ensure that visuals in Power BI Desktop render very quickly, are responsive to interaction with
users, and do not result in undue computational overhead on the computer rendering the visual.
Evaluating representative data points for high density line visuals
When the number of underlying data points exceeds the maximum data points that can be represented in the
visual, a process called binning begins, which chunks the underlying data into groups called bins, and then
iteratively refines those bins.
The algorithm creates as many bins as possible to create the greatest granularity for the visual. Within each bin,
the algorithm finds the minimum and maximum data value, to ensure that important and significant values (for
example, outliers) are captured and displayed in the visual. Based on the results of the binning and subsequent
evaluation of the data by Power BI, the minimum resolution for the x-axis for the visual is determined – to ensure
maximum granularity for the visual.
As mentioned previously, the minimum granularity for each series is 350 points, the maximum is 3,500 for most
visuals, with the exceptions listed in the previous paragraphs.
Each bin is represented by two data points, which become the bin's representative data points in the visual. The
data points are simply the high and low value for that bin, and by selecting the high and low, the binning process
ensures any important high value, or significant low value, is captured and rendered in the visual.
If that sounds like a lot of analysis to ensure the occasional outlier is captured and properly displayed in the visual,
you are correct, but that’s the exact reason for the new algorithm and binning process.

Tooltips and high density line sampling

It’s important to note that this binning process, which results in the minimum and maximum value in a given bin
being captured and displayed, may affect how tooltips display data when you hover over the data points. To
explain how and why this occurs, let’s revisit our example about stock prices.
Let’s say you’re creating a visual based on stock price and you're comparing two different stocks, both of which are
using High Density Sampling. The underlying data for each series has lots of data points (maybe you capture
the stock price each second of the day). The high-density line sampling algorithm performs binning for each series
independently of the other.
Now let's say that the first stock jumps up in price at 12:02, then quickly comes back down ten seconds later. That’s
an important data point. When binning occurs for that stock, the high at 12:02 will be a representative data point
for that bin.
But, for the second stock, 12:02 was neither a high nor a low in the bin that included that time. Maybe the high and
low for the bin that includes 12:02 occurred three minutes later. In that situation, when the line chart is created and
you hover over 12:02, you will see a value in the tooltip for the first stock (because it jumped at 12:02 and that
value was selected as that bin's high data point), but you will not see any value in the tooltip at 12:02 for the
second stock. That's because the second stock had neither a high, nor a low, for the bin that included 12:02. So,
there's no data to show for the second stock at 12:02, and thus, no tooltip data is displayed.
This situation will happen frequently with tooltips. The high and low values for a given bin might not match
perfectly with the evenly scaled x-axis value points, and as such the tooltip will not display the value.

How to turn on high density line sampling

By default, the new algorithm is turned on. To change this setting, go to the Formatting pane, in the General
card, and along the bottom, you see a toggle slider called High Density Sampling. To turn it off, slide it to Off.
Considerations and limitations
The new algorithm for high-density line sampling is an important improvement to Power BI, but there are a few
considerations you need to know when working with high-density values and data.
Because of increased granularity and the binning process, Tooltips may only show a value if the
representative data is aligned with your cursor. See the Tooltips and high density line sampling section in
this article for more information.
When the size of an overall data source is too big, the new algorithm eliminates series (legend elements) to
accommodate the data import maximum constraint.
In this situation, the new algorithm orders legend series alphabetically, starts down the list of legend
elements in alphabetical order until the data import maximum is reached, and does not import
additional series.
When an underlying data set has more than 60 series (the maximum number of series, as described earlier),
the new algorithm orders the series alphabetically, and eliminates series beyond the 60th alphabetically-
ordered series.
If the values in the data are not of type numeric or date/time, Power BI will not use the new algorithm, and
will revert to the previous (non-high-density sampling) algorithm.
The Show items with no data setting is not supported with the new algorithm.
The new algorithm is not supported when using a live connection to a model hosted in SQL Server
 Analysis Services (version 2016 or earlier). It is supported in models hosted in Power BI or Azure Analysis
Services.

Next steps
For information about high-density sampling in scatter charts, see the following article.
High Density Sampling in Power BI scatter charts
 KPI visuals
1/30/2019 • 2 minutes to read • Edit Online

A Key Performance Indicator (KPI) is a visual cue that communicates the amount of progress made toward a
measurable goal. For more information about KPIs, see Microsoft Developer Network.
If you're not signed up for Power BI, sign up for a free trial before you begin.

Prerequisites
Power BI Desktop - it's free!
The Retail Analysis sample PBIX file

When to use a KPI

KPIs are a great choice:
to measure progress (what am I ahead or behind on?)
to measure distance to a goal (how far ahead or behind am I?)

KPI requirements
A Key Performance Indicator (KPI) is based on a specific measure and is designed to help you evaluate the current
value and status of a metric against a defined target. Therefore, a KPI visual requires a base measure that evaluates
to a value and a target measure or value, and a threshold or goal.
Currently, a KPI dataset needs to contain goal values for a KPI. If your dataset doesn't contain one, you can create
goals by adding an Excel sheet with goals to your data model or PBIX file.

How to create a KPI

To follow along, open the Retail Analysis .PBIX file in Power BI Desktop. We'll create a KPI that measures the
progress we've made toward a sales goal.
Or watch Will show you how to create single metric visuals: gauges, cards, and KPIs.
https://www.youtube.com/embed/xmja6EpqaO0?list=PL1N57mwBHtN0JFoKSR0n-tBkUJHeMP2cP
1. Open the report in Report view and select the yellow tab to add a new page.
2. From the Fields pane, select Sales > Total Units This Year. This will be the indicator.
3. Add Time > FiscalMonth. This will be represent the trend.
4. IMPORTANT: Sort the chart by FiscalMonth. Once you convert the visualization to a KPI, there is no
option to sort.
5. Convert the visual to a KPI by selecting the KPI icon from the Visualization pane.

6. Add a goal. Add last years sales as the goal. Drag Total Units Last Year to the Target goals field.

7. Optionally, format the KPI by selecting the paint roller icon to open the Formatting pane.
Indicator - controls the indicator’s display units and decimal places.
Trend axis - when set to On, the trend axis is displayed as the background of the KPI visual.
Goals - when set to On, the visual displays the goal and the distance from the goal as a percentage.
Color coding > Direction - some KPIs are considered better for higher values and some are
considered better for lower values. For example, earnings versus wait time. Typically a higher value of
earnings is better versus a higher value of wait time. Select high is better and, optionally, change the
color settings.
KPIs are also available in Power BI service and on your mobile devices – keeping you always connected to your
businesses heartbeat.

Considerations and troubleshooting

 If your KPI doesn't look like the one above, it may be because you need to sort by fiscalmonth. Since KPIs don't
have a sort option, you'll need to sort by fiscalmonth before you convert your visualization to a KPI.

Next steps
Basic maps in Power BI
Visualization types in Power BI
 Use the Matrix visual in Power BI
1/14/2019 • 8 minutes to read • Edit Online

With the Matrix visual feature, you can create matrix visuals (sometimes also referred to as tables) in Power BI
Desktop and Power BI service reports and cross-highlight elements within the matrix with other visuals. In
addition, you can select rows, columns, and even individual cells and cross-highlight. Individual cells and multiple
cell selections can by copied and pasted into other applications. Lastly, to make better use of layout space, the
matrix visual supports a stepped layout.

There are many features associated with the matrix, and we'll go through them in the following sections of this
article.

Report themes
Both matrix and table visuals reflect styling (including colors) from the applied Report Theme. These may not be
the colors you expect for your matrix visual, which you can change in your Report Theme configuration. For more
information, see Use Report Themes in Power BI Desktop for more information about themes.

Understanding how Power BI calculates totals

Before jumping into how to use the Matrix visual, it's important to understand how Power BI calculates total and
subtotal values in tables and matrices. For total and subtotal rows, the measure is evaluated over all rows in the
underlying data – it is not just a simple addition of the values in the visible or displayed rows. This means you can
end up with different values in the total row than you might expect.
Take a look at the following Matrix visuals.
In this example, each row in the Matrix visual farthest to the right is showing the Amount for each
salesperson/date combination. However, since a salesperson shows up against multiple dates, the numbers can
appear more than once. Thus, the accurate total from the underlying data, and a simple addition of the visible
values, do not equate. This is a common pattern when the value you’re summing is on the ‘one’ side of a one-to-
many relationship.
When looking at total and subtotals, remember that those values are based on the underlying data, and not solely
based on the visible values.

Using drill down with the Matrix visual

With the Matrix visual, you can do all sorts of interesting drill down activities that weren't available before. This
includes the ability to drill down using rows, columns, and even into individual sections and cells. Let's take a look
at how each of these works.
Drill down on row headers
In the Visualizations pane, when you add multiple fields to the Rows section of the Fields well, you enable drill
down on the rows of the matrix visual. This is similar to creating a hierarchy, which then allows you to drill down
(and then back up) through that hierarchy, and analyze the data at each level.
In the following image, the Rows section contains Category and SubCategory, creating a grouping (or hierarchy)
in the rows that we can drill through.
When the visual has grouping created in the Rows section, the visual itself displays the drill and expand icons in
the top-left corner of the visual.

Similar to the drill and expand behavior in other visuals, selecting those buttons lets us drill down (or back up)
through the hierarchy. In this case, we can drill down from Category to SubCategory, as shown in the following
image, where the drill down one level icon (the pitchfork) has been selected.

In addition to using those icons, you can right-click on any of those row headers and drill down by selecting from
the menu that appears.
Notice there are a few options from the menu that appears, which generate different results:
Selecting Drill Down expands the matrix for that row level, excluding all other row headings except the row
header that was right-clicked. In the following image, Computers was right-clicked, and Drill Down was selected.
Notice that other top-level rows no longer appear in the matrix. This way to drill is a useful feature, and becomes
especially cool when we get to the cross-highlighting section.

You can click the Drill up icon to get back to the previous top-level view. If you then select Show Next Level
from the right-click menu, you get an alphabetical listing of all the next-level items (in this case, the SubCategory
field), without the higher-level hierarchy categorization.
When you click on the Drill up icon in the upper-left corner to have the matrix show all top-level categories, then
right-click again and select Expand to next level, you see the following visual.

You can also use the Include and Exclude menu items to keep (or remove, respectively) the right-clicked row
(and any subcategories) from the matrix.
Drill down on column headers
Similar to the ability to drill down on Rows, you can also drill down on Columns. In the following image, you can
see that there are two fields in the Columns field well, creating a hierarchy similar to what we used for the rows
earlier in this article. In the Columns field well, we have Class and Color.
In the Matrix visual, when we right-click a column, we see the option to drill down. In the following image, we
right-click on Deluxe and select Drill Down.

When you select Drill Down, the next level of the column hierarchy for Deluxe displays, which in this case is
Color.
The rest of the right-click menu items work on columns in the same way they do for rows (see the previous
section, Drill down on row headers). You can Show Next Level, Expand to next level, Include, or Exclude
your columns just as you can with rows.

NOTE
The drill down and drill up icons in the upper-left of the matrix visual only apply to rows. In order to drill down on columns,
you must use the right-click menu.

Stepped layout with matrix visuals

The Matrix visual automatically indents subcategories in a hierarchy beneath each parent, which is called a
Stepped layout.
In the original version of the matrix visual, subcategories were shown in an entirely different column, taking up
much more space in the visual. The following image shows the table in original Matrix visual; notice the
subcategories in a separate column.

In the following image, you see a Matrix visual, with Stepped layout in action. Notice the category Computers
has its subcategories (Computers Accessories, Desktops, Laptops, Monitors, and so on) slightly indented,
providing a cleaner and much more condensed visual.
You can easily adjust the stepped layout settings. With the Matrix visual selected, in the Format section (the paint
roller icon) of the Visualizations pane, expand the Row headers section. You have two options: the Stepped
layout toggle (which turns it on or off), and the Stepped layout indentation (specifies the indentation amount,
in pixels).

If you turn off Stepped layout, the subcategories are shown in another column rather than indented beneath the
parent category.

Subtotals with matrix visuals

You can turn subtotals on or off in matrix visuals, for both rows and columns. In the following image, you can see
that the row subtotals are set to on.
In the Format section of the Visualizations pane, expand the Subtotals card, and turn the Row subtotals slider
to Off. When you do so, the subtotals are not shown.

The same process applies for column subtotals.

Cross-highlighting with matrix visuals

With the Matrix visual, you can select any elements in the matrix as the basis for cross-highlighting. Select a
column in a Matrix and that column is highlighted, as are any other visuals on the report page. This type of cross-
highlighting has been a common feature of other visuals and data point selections, so now the Matrix visual
offers the same function.
In addition, using Ctrl+Click also works for cross-highlighting. For example, in the following image a collection of
subcategories were selected from the Matrix visual. Notice how items that weren't selected from the visual are
grayed out, and how the other visuals on the page reflect the selections made in the Matrix visual.
Copying values from Power BI for use in other applications
Your matrix or table may have content that you'd like to use in other applications, like Dynamics CRM, Excel, and
even other Power BI reports. With the Power BI right-click, you can copy a single cell or a selection of cells onto
your clipboard, and paste into the other application.

To copy the value of a single cell, select the cell, right-click, and choose Copy value. With the unformatted
cell value on your clipboard, you can now paste it into another application.

To copy more than a single cell, select a range of cells or use CTRL to select one or more cells. The copy will
include the column and row headers.
Shading and font colors with matrix visuals
With the Matrix visual, you can apply Conditional formatting (colors and shading) to the background of cells
within the matrix, and you can apply conditional formatting to the text and values themselves.
To apply conditional formatting, you can do either of the following when a matrix visual is selected:
In the Fields pane, right-click the Field, and select Conditional formatting from the menu.

Or, in the Format pane, expand the Conditional formatting card and for either Background color
scales or Font color scales, turn the slider to On. Turning on either option displays a link for Advanced
controls, which lets you customize the colors and values for the color formatting.
Either approach achieves the same result. Selecting Advanced controls displays the following dialog, which lets
you make adjustments:

Next steps
Scatter and bubble charts in Power BI
Visualization types in Power BI
 Creating R visuals in the Power BI service
2/19/2019 • 6 minutes to read • Edit Online

The Power BI service supports viewing and interacting with visuals created with R scripts. Visuals created with R
scripts, commonly called R visuals, can present advanced data shaping and analytics such as forecasting, using the
rich analytics and visualization power of R.

NOTE
The R programming language is among the most widely used programming languages by statisticians, data scientists, and
business analysts. The R language has an open source community that offers over 7,000 add-on packages, as well as widely
used R User Groups. The version of R deployed in the Power BI service is Revolution R Open 3.2.2.

The following image shows a Power BI dashboard with a collection of R visuals used for advanced analytics.

R visuals are created in a Power BI Desktop report, like the report shown in the following image.
Once the report is created in Power BI Desktop, you can publish the report containing one or more R visuals to
the Power BI service. R visuals currently can only be created in Power BI Desktop, and then published to Power
BI service. For more information on creating R visuals, see Create Power BI visuals using R (Power BI Desktop).
Note that in the service not all of the R packages are supported. See supported packages at the end of this article
for the list of packages currently supported in the Power BI service.
You can download this sample Power BI Desktop file (.pbix file) that contains a few R visuals to see how this works,
and to experiment.
R visuals that are created in Power BI Desktop, and then published to the Power BI service, for the most part
behave like any other visual in the Power BI service; you can interact, filter, slice, and pin them to a dashboard, or
share them with others. For more information about sharing dashboards and visuals, see share a dashboard with
colleagues and others. One difference from other visuals is that R visuals cannot show tool tips and cannot be
used to filter other visuals.
As you can see in the following image, R visuals in the Power BI service, either in dashboards or reports, largely
appear and behave like any other visual, and users don't need to be aware of the underlying R script that created
the visual.

R scripts security
R visuals are created from R scripts, which could potentially contain code with security or privacy risks.
These risks mainly exist in the authoring phase when the script author run the script on their own computer.
The Power BI service applies a sandbox technology to protect users and the service from security risks.
This sandbox approach imposes some restrictions on the R scripts running in the Power BI service, such as
accessing the Internet, or accessing to other resources that are not required to create the R visual.

R scripts error experience

When an R script encounters an error, the R visual is not plotted and an error message is displayed. For details on
the error, select See details from the R visual error on the canvas, as shown in the following image.

As another example, the following image shows the error message that appears when an R script failed to run
properly due to a missing R package in Azure.

Licensing
R visuals require a Power BI Pro license to render in reports, refresh, filter and cross-filter. For more information
about Power BI Pro licenses, and how they differ from free licenses, see Power BI Pro content - what is it?
Free users of Power BI can only consume tiles shared with them in Premium workspaces. See purchasing Power
BI Pro for more information.
The following table describes R visuals capabilities based on licensing.

CREATE PBI SERVICE

AUTHOR R VISUALS IN REPORTS WITH R VIEW R VISUALS IN VIEW R TILES IN
POWER BI DESKTOP VISUALS REPORTS DASHBOARDS

Guest (Power BI Not relevant Not relevant Not supported Not relevant
embedded)

Unmanaged tenant Supported Not supported Not supported Supported (B2B

(domain not verified) scenario)
 CREATE PBI SERVICE
AUTHOR R VISUALS IN REPORTS WITH R VIEW R VISUALS IN VIEW R TILES IN
POWER BI DESKTOP VISUALS REPORTS DASHBOARDS

Managed tenant Supported Not supported Supported in Supported

with free license Premium capacity
only

Managed tenant Supported Supported Supported Supported

with Pro license

Known Limitations
R visuals in the Power BI service have a few limitations:
R visuals support is limited to the packages identified on the following page . There currently is no support
for custom packages.
Data size limitations – data used by the R visual for plotting is limited to 150,000 rows. If more than
150,000 rows are selected, only the top 150,000 rows are used and a message is displayed on the image.
Calculation time limitation – if an R visual calculation exceeds 60 seconds the script times out, resulting in
an error.
R visuals are refreshed upon data updates, filtering, and highlighting. However, the image itself is not
interactive and does not support tool tips.
R visuals respond to highlighting other visuals, but you cannot click on elements in the R visual in order to
cross filter other elements.
R visuals are currently not supported for the Time data type. Please use Date/Time instead.
R Visuals do not display when using Publish to web.
R visuals currently do not print with dashboard and reports printing
R visuals are currently not supported in the DirectQuery mode of Analysis Services
Chinese, Japanese and Korean fonts require all of the additional following steps to work properly in the
Power BI service:
First, install the R package showtext and all of its dependencies. You can do this by running the
following script:

*install.packages("showtext")*

Next, add the following line at the beginning of the R script:

powerbi_rEnableShowTextForCJKLanguages = 1

Overview of R packages
R packages are collections of R functions, data, and compiled code that are combined in a well-defined format.
When R is installed, it comes with a standard set of packages, and other packages are available for download and
installation. Once installed, an R packages must be loaded into the session to be used. The primary source of free
R packages is CRAN, the Comprehensive R Archive Network.
Power BI Desktop can use any type of R packages without limitation. You can install R packages for use in
Power BI Desktop on your own (using the RStudio IDE, for example).
R visuals in the Power BI service are supported by the packages found in the Supported Packages section
found in this article. If you don't find a package you're interested in among the supported packages list, you can
request the support of the package. See R packages in the Power BI service for information on how to request
support.
Requirements and Limitations of R packages
There are a handful of requirements and limitations for R packages:
The Power BI service, for the most part, supports R packages with free and open-source software licenses
such as GPL -2, GPL -3, MIT+, and so on.
The Power BI service supports packages published in CRAN. The service does not support private or
custom R packages. We encourage users to make their private packages available on CRAN prior to
requesting the package be available in the Power BI service.
For Power BI Desktop has two variations for R packages:
For R visuals, you can install any package, including custom R packages
For Custom R visuals, only public CRAN packages are supported for auto-installation of the packages
For security and privacy reasons, we currently don't support R packages that provide client-server queries
over the World-Wide Web (such as RgoogleMaps) in the service. Networking is blocked for such attempts.
See R packages in the Power BI service for a list of supported and unsupported R packages.
The approval process for including a new R package has a tree of dependencies; some dependencies
required to be installed in the service cannot be supported.
Supported Packages:
For a long list of supported R packages (and the short list of unsupported packages) please see the following
article:
R packages in the Power BI service
 Radial gauge charts in Power BI
1/14/2019 • 3 minutes to read • Edit Online

A radial gauge chart has a circular arc and displays a single value that measures progress toward a goal/KPI. The
goal, or target value, is represented by the line (needle). Progress toward that goal is represented by the shading.
And the value that represents that progress is shown in bold inside the arc. All possible values are spread evenly
along the arc, from the minimum (left-most value) to the maximum (right-most value).
In the example below, we are a car retailer, tracking our Sales team's average sales per month. Our goal is 140 and
represented by the black needle. The minimum possible average sales is 0 and we've set the maximum as 200. The
blue shading shows that we're currently averaging approximately 120 sales this month. Luckily, we still have
another week to reach our goal.

When to use a radial gauge

Radial gauges are a great choice to:
show progress toward a goal.
represent a percentile measure, like a KPI.
show the health of a single measure.
display information that can be quickly scanned and understood.
Prerequisites
Power BI service or Power BI Desktop
Financial sample Excel workbook: download the sample directly.

Create a basic radial gauge

These instructions use Power BI service. To follow along, sign in to Power BI and open the Excel Financial Sample
file.
Or watch Will show you how to create single metric visuals: gauges, cards, and KPIs.
https://www.youtube.com/embed/xmja6EpqaO0?list=PL1N57mwBHtN0JFoKSR0n-tBkUJHeMP2cP
Step 1: Open the Financial Sample Excel file
1. Download the sample Financial Excel file if you haven't already. Remember where you saved it.
2. Open the file in Power BI service by selecting Get Data > Files and browsing to the location where you
saved the file. Select Import. The Financial Sample is added to your workspace as a dataset.
3. From the Dataset content list, select Financial Sample to open it in Explore mode.
Step 2: Create a gauge to track Gross Sales
1. In the Fields pane, select Gross Sales.

2. Change the aggregation to Average.

3. Select the gauge icon to convert the Column Chart to a gauge.

By default, Power BI creates a Gauge chart where the current value (in this case, Average of Gross Sales) is
assumed to be at the halfway point on the gauge. Since the Average Gross Sales is $182.76K, the start
value (Minimum) is set to 0 and the end value (Maximum) is set to double the current value.
Step 3: Set a target value
1. Drag COGS to the Target value well.
2. Change the aggregation to Average. Power BI adds a needle to represent our target value of $145.48K.
Notice that we've exceeded our target.

NOTE
You can also manually enter a target value. See "Use formatting options to manually set Minimum, Maximum, and
Target values" below.

Step 4: Set a maximum value

In Step 2, Power BI used the Value field to automatically set minimum (start) and maximum (end). But what if you
want to set your own maximum value? Let's say that instead of using double the current value as the maximum
possible value, you want to set it to the highest Gross Sales number in your dataset?
1. Drag Gross Sales from the Fields list to the Maximum Value well.
2. Change the aggregation to Maximum.
 The gauge is redrawn with a new end value, 1.21 million in gross sales.

Step 5: Save your report

1. Save the report.
2. Add the gauge chart as a dashboard tile.

Use formatting options to manually set Minimum, Maximum, and

Target values
1. Remove Max of Gross Sales from the Maximum value well.
2. Open the formatting pane by selecting the paint roller icon.

3. Expand the Gauge axis and enter values for Min and Max.
4. Remove the current target value by removing the checkmark next to COGS.

5. When the Target field appears under Gauge axis, enter a value.

6. Optionally, continue formatting your gauge chart.

Next step
Gauges in Power BI
Visualization types in Power BI
 Use ribbon charts in Power BI
1/30/2019 • 2 minutes to read • Edit Online

You can use ribbon charts to visualize data, and quickly discover which data category has the highest rank (largest
value). Ribbon charts are effective at showing rank change, with the highest range (value) always displayed on top
for each time period.

Create a ribbon chart

To follow along, open the Retail analysis sample report.
1. To create a ribbon chart, select Ribbon chart from the Visualizations panel.

Ribbon charts connect a category of data over the visualized time continuum using ribbons, enabling you to
see how a given category ranks throughout the span of the chart's x-axis (usually the timeline).
2. Select fields for Axis, Legend, and Value. In this example, we've selected: Date, Category, and This year
sales.

Since the dataset contains data for only one year, we removed the Year field from the Axis well.
3. The ribbon chart shows rank for every-other month. Notice how rank changes across time. For example, the
Home category moves from third to fourth and back to third again. The Juniors category moves from third
to fifth in July.

Format a ribbon chart

When you create a ribbon chart, you have formatting options available in the Format section of the
Visualizations pane. The formatting options for ribbon charts are similar to those for a stacked column chart, with
additional formatting options that are specific to the ribbons.
These formatting options for ribbon charts let you make adjustments.
Spacing lets you adjust how much space appears between ribbons. The number is the percentage of the
column's maximum height.
Match series color allows you to match the color of the ribbons with the series color. When set to off, ribbons
are gray.
Transparency specifies how transparent the ribbons are, with the default set to 30.
Border lets you place a dark border on the top and bottom of the ribbons. By default, borders are off.
Since the ribbon chart does not have y-axis labels, you may want to add data labels. From the Formatting pane,
select Data labels.

Set formatting options for your data labels. In this example, we've set the text color to white, the decimal places to
zero, and display units to thousands.

Next steps
Scatter charts and bubble charts in Power BI
Visualization types in Power BI
 Scatter charts, bubble charts, and dot plot charts in
Power BI
1/14/2019 • 4 minutes to read • Edit Online

A scatter chart always has two value axes to show one set of numerical data along a horizontal axis and another
set of numerical values along a vertical axis. The chart displays points at the intersection of an x and y numerical
value, combining these values into single data points. These data points may be distributed evenly or unevenly
across the horizontal axis, depending on the data.
A bubble chart replaces data points with bubbles, with the bubble size representing an additional dimension of the
data.

A dot plot chart is similar to a bubble chart and scatter chart except that you can plot numerical or categorical data
along the X axis.

You can set the number of data points, up to a maximum of 10,000.

When to use a scatter chart or bubble chart

Scatter charts are a great choice:
to show relationships between 2 (scatter) or 3 (bubble) numerical values.
to plot two groups of numbers as one series of xy coordinates.
instead of a line chart when you want to change the scale of the horizontal axis
to turn the horizontal axis into a logarithmic scale.
to display worksheet data that includes pairs or grouped sets of values. In a scatter chart, you can adjust the
independent scales of the axes to reveal more information about the grouped values.
to show patterns in large sets of data, for example by showing linear or non-linear trends, clusters, and outliers.
to compare large numbers of data points without regard to time. The more data that you include in a scatter
chart, the better the comparisons that you can make.
Bubble charts are a great choice:
if your data has 3 data series that each contain a set of values.
to present financial data. Different bubble sizes are useful to visually emphasize specific values.
to use with quadrants.
Dot plot charts are a great choice in place of a scatter or bubble:
if you want to include categorical data along the X axis

Create a scatter chart

Watch this video to see Will create a scatter chart and then follow the steps below to create one yourself.
https://www.youtube.com/embed/PVcfPoVE3Ys?list=PL1N57mwBHtN0JFoKSR0n-tBkUJHeMP2cP
These instructions use the Retail Analysis Sample. To follow along, download the sample for Power BI service
(app.powerbi.com) or Power BI Desktop.
1. Open the report in Editing view and select the yellow plus icon to create a blank report page.
2. From the Fields pane, select the following fields:
Sales > Sales Per Sq Ft
Sales > Total Sales Variance %
District > District

If you're using Power BI service, make sure you open the report in Editing View.
3. Convert to a scatter chart. In the Visualization pane, select the Scatter chart icon.
 .
4. Drag District from Details to Legend. This displays a scatter chart that plots Total Sales Variance %
along the Y axis, and plots Sales Per Square Feet along the X axis. The data point colors represent
districts:

Now let's add a third dimension.

Create a bubble chart

1. From the Fields pane, drag Sales > This Year Sales > Value to the Size area. The data points expand to
volumes proportionate with the sales value.

2. Hover over a bubble. The size of the bubble reflects the value of This Year Sales.
3. To set the number of data points to show in your bubble chart, in the Formatting section of the
Visualizations pane, expand the General card and adjust the Data Volume. You can set the max data
volume to any number up to 10,000. As you get into the higher numbers, we suggest testing first to ensure
good performance.

Because more data points can mean a longer loading time, if you do choose to publish reports with limits at
the higher end of the scale, make sure to test out your reports across the web and mobile as well to ensure
performance matches your users' expectations.
4. You can format the visualization colors, labels, titles, background, and more. To improve accessibility,
consider adding marker shapes to each line. Using a different Marker shape for each line makes it easier for
report consumers to differentiate lines (or areas) from each other. To select the marker shape, expand the
Shapes card, then select a marker shape.
 You can also change the marker shape to diamond, triangle, or square:

Create a dot plot

To create a dot plot, replace the numerical X axis field with a categorical field.
From the X Axis pane, remove Sales per sq ft and replace it with District > DM.

Considerations and Troubleshooting

Your scatter chart has only one data point
Does your scatter chart have only one data point that aggregates all the values on the X and Y axes? Or maybe it
aggregates all the values along a single horizontal or vertical line?

Add a field to the Details area to tell Power BI how to group the values. The field must be unique for each point
you want to plot; like a simple row number or ID field.
Or if you don’t have that in your data, create a field that concatenates your X and Y values together into something
unique per point:

To create a new field, use the Power BI Desktop Query Editor to add an Index Column to your dataset. Then add
this column to the Details area of your visualization.

Next steps
High density scatter charts
Visualization types in Power BI
 High-density sampling in Power BI scatter charts
1/14/2019 • 5 minutes to read • Edit Online

Beginning with the September 2017 release of the Power BI Desktop and updates to the Power BI service, a
new sampling algorithm is available that improves how scatter charts represent high-density data.
For example, you might create a scatter chart from your organization's sales activity, each store having tens of
thousands of data points each year. A scatter chart of such information would sample data (select a meaningful
representation of that data to illustrate how sales occurred over time) from the available data, and create a scatter
chart that represents the underlying data. This is common practice in high-density scatter charts. Power BI has
improved its sampling of high-density data, the details of which are described in this article.

NOTE
The High-density Sampling algorithm described in this article is available in the scatter charts for both Power BI Desktop
and the Power BI service.

How high-density scatter charts work

Previously, Power BI selected a collection of sample data points in the full range of underlying data in a
deterministic fashion to create a scatter chart. Specifically, Power BI would select the first and last rows of data in
the scatter chart series, then would divide the remaining rows evenly so that 3,500 data points total would be
plotted on the scatter chart. For example, if the sample had 35,000 rows, the first and last rows would be selected
for plotting, then every tenth row would also be plotted (35,000 / 10 = every tenth row = 3,500 data points). Also
previously, null values or points that could not be plotted (such as text values) in data series weren't shown, and
thus, were not considered when generating the visual. With such sampling, the perceived density of the scatter
chart was also based on the representative data points, so the implied visual density was a circumstance of the
sampled points, not the full collection of the underlying data.
When you enable High-density Sampling, Power BI implements an algorithm that eliminates overlapping
points, and ensures that the points on the visual can be reached when interacting with the visual. The algorithm
also ensures that all points in the data set are represented in the visual, providing context to the meaning of
selected points, rather than just plotting a representative sample.
By definition, high-density data is sampled to create visualizations reasonably quickly that are responsive to
interactivity. Too many data points on a visual can bog it down, and can detract from the visibility of trends. So,
how the data is sampled is what drives the creation of the sampling algorithm to provide the best visualization
experience and ensure that all data is represented. In Power BI, the algorithm is now improved to provide the best
combination of responsiveness, representation, and clear preservation of important points in the overall data set.

NOTE
Scatter charts using the High-density Sampling algorithm are best plotted on square visuals, as with all scatter charts.

How the new scatter chart sampling algorithm works

The new algorithm for High-density Sampling for scatter charts employs methods that capture and represent
the underlying data more effectively and eliminates overlapping points. It does this by starting with a small radius
for each data point (the visual circle size for a given point on the visualization). It then increases the radius of all
data points; when two (or more) data points overlap, a single circle (of the increased radius size) represents those
overlapped data points. The algorithm continues to increase the radius of data points, until that radius value
results in a reasonable number of data points - 3,500 - being displayed in the scatter chart.
The methods in this algorithm ensure that outliers are represented in the resulting visual. The algorithm respects
scale when determining overlap, too, such that exponential scales are visualized with fidelity to the underlying
visualized points.
The algorithm also preserves the overall shape of the scatter chart.

NOTE
When using the High-density Sampling algorithm for scatter charts, accurate distribution of the data is the goal, and
implied visual density is not the goal. For example, you might see a scatter chart with lots of circles that overlap (density) in a
certain area, and imagine many data points must be clustered there; since the High-density Sampling algorithm can use
one circle to represent many data points, such implied visual density (or "clustering") will not show up. To get more detail in
a given area, you can use slicers to zoom in.

In addition, data points that cannot be plotted (such as nulls or text values) are ignored, so another value that can
be plotted is selected, further ensuring the true shape of the scatter chart is maintained.
When the standard algorithm for scatter charts is used
There are circumstances under which High-density Sampling cannot be applied to a scatter chart and the
original algorithm is used. Those circumstances are the following:
If you right-click a value under Details and set it to Show items with no data from the menu, the scatter
chart will revert to the original algorithm.
Any values in the Play axis will result in the scatter chart reverting to the original algorithm.
If both X and Y axes are missing on a scatter chart, the chart reverts to the original algorithm.
Using a Ratio line in the Analytics pane results in the chart reverting to the original algorithm.
How to turn on high-density sampling for a scatter chart
To turn on High-density Sampling, select a scatter chart, go to the Formatting pane, expand the General card,
and near the bottom of that card, slide the High-density Sampling toggle slider to On.
 NOTE
Once the slider is turned on, Power BI will attempt to use the High-density Sampling algorithm whenever possible. When
the algorithm cannot be used (for example, you place a value in the Play axis), the slider stays in the On position even
though the chart has reverted to the standard algorithm. If you then remove a value from the Play axis (or conditions
change to enable use of the high-density sampling algorithm), the chart will automatically use high-density sampling for
that chart because the feature is active.

NOTE
Data points are grouped or selected by the index. Having a legend does not affect sampling for the algorithm, it only affects
the ordering of the visual.

Considerations and limitations

The high-density sampling algorithm is an important improvement to Power BI, but there are a few
considerations to know when working with high-density values and scatter charts.
The High-density Sampling algorithm only works with live connections to Power BI service-based models,
imported models, or DirectQuery.

Next steps
For more information about high-density sampling in other charts, see the following article.
High-density line sampling in Power BI
 Slicers in Power BI
1/14/2019 • 10 minutes to read • Edit Online

You want your report readers to be able to look at overall sales metrics, but also highlight performance for
individual District Managers and different time frames. You could create separate reports or comparative charts, or
you could use slicers. A slicer is an alternate way of filtering that narrows the portion of the dataset shown in the
other visualizations in a report.
This tutorial uses the free Retail Analysis Sample to walk you through creating, formatting, and using list and date
range slicers. Have fun discovering ways to format and use slicers.

When to use a slicer

Slicers are a great choice when you want to:
Display commonly-used or important filters on the report canvas for easier access.
Make it easier to see the current filtered state without having to open a drop-down list.
Filter by columns that are unneeded and hidden in the data tables.
Create more focused reports by putting slicers next to important visuals.
Power BI slicers have the following limitations:
Slicers do not support input fields.
Slicers cannot be pinned to a dashboard.
Drilldown is not supported for slicers.
Slicers do not support visual level filters.

Create slicers
To create a new slicer, you can select the slicer icon and then select the data field to filter on (or drag it to the Fields
box in the Visualizations pane), or you can select or drag the data field first to create a visualization, and then
select the slicer icon to turn the visualization into a slicer. Different data types create different types of slicers, with
different effects and options.
The first time you change a report, the button for Reset to default lights up. This is a reminder that you've made a
change to the original report settings. If you navigate away from the report, that change is saved (persists). When
you return to the report you don't have to re-slice the report. However, if you'd like to reset the report to the
author's default settings, select the Reset to default button from the top menubar.

NOTE
If your Reset to default button remains disabled, it either means the report author has disabled the feature for the report
or the report contains a custom visual. Simply hover over the button to read the tooltip for an explanation.

To create a new slicer to filter data by District Manager

1. In Power BI Desktop or Power BI service, open the Retail Analysis Sample. (In Power BI service, select Edit
Report at upper left.)

2. On the Overview page, with nothing selected on the canvas, select the Slicer icon in the
Visualizations pane to create a new slicer.
3. With the new slicer selected, select District Manager under District in the Fields pane to populate the
slicer. The new slicer is a list with selection boxes before the names.

4. Resize and drag the slicer and other elements on the canvas to make room for the slicer. Note that the slicer
items are cut off if you resize the slicer too small.
5. Select names on the slicer and note the effects on the other visualizations on the page. Select names again
to deselect them, and hold down the Ctrl key to select more than one name. Selecting all names has the
same effect as selecting none.

TIP
List slicer items are sorted in ascending alphanumerical order by default. To reverse the sort order to descending, select the
ellipsis (...) in the top right corner of the slicer and choose Sort by District Manager in the drop-down list.

To create a new slicer to filter data by date range

1. With nothing selected on the canvas, drop down Time in the Fields pane, and drag Month (or Date in
Power BI service) to the Values box in the Visualizations pane to create a new visualization.
2. With the new visualization selected, select the Slicer icon to convert the new visualization to a slicer. This
slicer is a slider control with the date range populated.
3. Resize and drag the slicer and other elements on the canvas to make room for the slicer. Note that the slider
resizes with the slicer size, but it disappears and the dates are cut off if you resize the slicer too small.
4. Select different date ranges with the slider, or select a date field to type in a value or pop up a calendar for
more precise selection. Note the effects on the other visualizations on the page.

NOTE
Numeric and date/time data types produce range slider slicers by default. Starting with the February 2018 Power BI
update, whole number data type range sliders now snap to whole number values rather than showing decimal
places.

TIP
Although the Month data field produces a Between range slider slicer type by default, you can change it to other slicer
types and selection options. To change the slicer type, with the slicer selected, hover over the upper-right area of the slicer,
drop down the carat that appears, and choose one of the other options, such as List or Before. Note how the slicer
appearance and selection options change.

For more about creating date and numeric range slicers, watch the following video and see Use the numeric range
slicer in Power BI Desktop.
https://www.youtube.com/embed/zIZPA0UrJyA

Control which page visuals are affected by slicers

By default, slicers on report pages affect all the other visualizations on that page, including each other. As you
choose values in the list and date sliders you just created, note the effects on the other visualizations. The filtered
data is an intersection of the values selected in both slicers.
You can use Visual interactions to exclude some page visualizations from being affected by others. On the
Overview page, the "Total Sales Variance by FiscalMonth and District Manager" chart shows overall comparative
data for District Managers by Month, which you want to keep visible at all times. You can use Visual interactions
to keep slicer selections from filtering this chart.
1. With the District Manager slicer selected:
In Power BI Desktop, select the Format menu under Visual Tools and select Edit interactions.
In Power BI service, drop down Visual interactions from the menu bar and turn on Edit interactions.
Filter controls appear above all the other visuals on the page. Initially, all the Filter icons are
 selected.
2. Select the None icon above the Total Sales Variance by FiscalMonth and District Manager chart to
make the slicer stop filtering it.
3. Select the Month slicer, and again select the None icon above the Total Sales Variance by FiscalMonth
and District Manager chart to make this slicer stop filtering it. Now, as you select names and date ranges
in the slicers, the Total Sales Variance by FiscalMonth and District Manager chart is unchanged.
See Visual interactions in a Power BI report for more information about editing interactions.

Sync and use slicers on other pages

Starting with the February 2018 Power BI update, you can sync a slicer and use it on any or all pages in a report.
In the current report, the District Monthly Sales page also has a District Manager slicer, but it is not synced
with the one you created on the Overview page (the two slicers can have different item selections). The New
Stores page has only a Store Name slicer. You can sync your new District Manager slicer to these pages, so that
slicer selections on any page affect visualizations on all three pages.
1. On the View menu, select Sync slicers in Power BI Desktop (or turn on Sync slicers pane in Power BI
service). The Sync Slicers pane appears.
2. On the Overview page, select the District Manager slicer. Note that the District Monthly Sales page is
already selected in the Visible column, because there is also a District Manager slicer on that page, but it is
not selected in the Sync column.

3. In the Sync column, select the New Stores page and the District Monthly Sales page to sync the
Overview slicer to those pages.
4. In the Visible column, select the New Stores page and leave the District Monthly Sales page selected.
5. Observe the effects of syncing the slicer and making it visible on the other pages. On the District Monthly
Sales page, the District Manager slicer now shows the same selections as the one on the Overview page.
On the New Stores page, the selections in the District Manager slicer affect the selections that are
available in the Store Name slicer.

TIP
Although the slicer initially appears on the synced pages at the same size and position as on the original page, you
can move, resize, and format synced slicers on the various pages independently.

NOTE
If you sync a slicer to a page but do not make it visible on that page, slicer selections made on the other pages still filter the
data on the page.
Format slicers
Different formatting options are available depending on the slicer type. By using Horizontal orientation,
Responsive layout, and Item coloring, you can produce buttons or tiles rather than standard list items, and make
slicer items resize to fit different screen sizes and layouts.
1. With the District Manager slicer selected on any page, in the Visualizations pane, select the Format icon
to display the formatting controls.

2. Select the drop-down arrows next to each category to display and edit the options.
General options
1. Select red under Outline color and change Outline weight to "2". This sets the color and thickness of the
header and item outlines or underlines, when enabled.
2. Under Orientation, Vertical is the default. Select Horizontal to produce a slicer with horizontally
arranged tiles or buttons, and scroll arrows to access items that do not fit in the slicer.
3. Turn on Responsive layout to change the size and arrangement of slicer items according to viewscreen and
slicer size. For list slicers, responsive layout is only available in horizontal orientation, and prevents items
from being cut off on small screens. For range slider slicers, responsive formatting changes the style of the
slider and provides more flexible resizing. Both types of slicers become filter icons at very small sizes.

NOTE
Responsive layout changes may override specific heading and item formatting that you set.

4. Set the slicer position and size with numeric precision under X Position, Y Position, Width, and Height,
or move and resize the slicer directly on the canvas. Experiment with different item sizes and arrangements,
and note how the responsive formatting changes accordingly.

See Create a responsive slicer you can resize in Power BI for more about horizontal orientation and responsive
layout.
Selection Controls options (list slicers only)
1. Show Select All is Off by default. Turn it to On to add a Select All item to the slicer that selects or
deselects all items when toggled. When all items are selected, clicking or tapping one item deselects it,
allowing an "is-not"-type filter.

2. Single Select is On by default. Clicking or tapping each item selects it, and holding down the Ctrl key
while clicking or tapping selects multiple items. Turn Single Select to Off to allow selecting multiple items
without holding down the Ctrl key. Clicking or tapping each item again deselects it.
Header options
The Header is On by default, showing the data field name at the top of the slicer.
1. Format the header text to make the Font color red, Text size 14 pt, and Font family Arial Black.
2. Under Outline, choose Bottom only to produce an underline with the size and color that you set under
General options.
Item options (list slicers only)
1. Format item text and background to make the Font color black, Background light red, Text size 10 pt,
and Font family Arial.
2. Under Outline, choose Frame to draw a border around each item with the size and color you set under
General options.
 TIP
With Orientation > Horizontal, deselected items show the chosen text and background colors, while selected
items use the system default, usually black background with white text.
With Orientation > Vertical, items always show the set colors, and selection boxes are always black when
selected.

Date/numeric inputs and Slider options (range slider slicers only)

Date/numeric input options are the same as the Item options for list slicers, except there is no Outline or
underline.
Slider options allow you to set the color of the range slider, or turn the slider to Off, leaving only the numeric
inputs.
Other formatting options
The other formatting options are off by default. When turned On:
Title: Adds and formats a title (in addition to and independent of the header) at the top of the slicer.
Background: Adds a background color to the overall slicer and sets its transparency.
Lock aspect: Retains the shape of the slicer if it is resized.
Border: Adds a 1-pixel border around the slicer and sets its color. (This slicer border is separate from and
unaffected by the General Outline settings.)

Next steps
Visualization types in Power BI
Tables in Power BI
 Tables in Power BI reports and dashboards
2/13/2019 • 5 minutes to read • Edit Online

A table is a grid that contains related data in a logical series of rows and columns. It may also contain headers and
a row for totals. Tables work well with quantitative comparisons where you are looking at many values for a single
category. For example, this table displays 5 different measures for Category.

Create tables in reports and cross-highlight elements within the table with other visuals on the same report page.
In addition, you can select rows, columns, and even individual cells and cross-highlight. Individual cells and
multiple cell selections can by copied and pasted into other applications.

When to use a table

Tables are a great choice:
to see and compare detailed data and exact values (instead of visual representations)
to display data in a tabular format
to display numerical data by categories

NOTE
If a table has too many values, consider converting it to a matrix and/or using drilldown. The maximum data points a table
will display is 3,500.

Prerequisites
Power BI service or Power BI Desktop
Retail Analysis sample

Create a table
We'll create the table pictured above to display sales values by item category. To follow along, sign in to Power BI
service and select Get Data > Samples > Retail Analysis Sample > Connect and choose Go to dashboard.
Creating a visualization requires edit permissions to the dataset and report. Luckily, the Power BI samples are all
editable. If a report has been shared with you, you won't be able to create visualizations in reports.
1. From the left navpane, select Workspaces >My workspace.
2. Select the Datasets tab, and scroll down to the Retail Analysis Sample dataset you just added. Select the
Create report icon.
3. In the report editor, select Item > Category. Power BI automatically creates a table that lists all the
categories.

4. Select Sales > Average Unit Price and Sales > Last Year Sales and Sales > This Year Sales and choose
all 3 options (Value, Goal, Status).
5. In the Visualizations pane, locate the Values well and drag-and-drop the values until the order of your chart
columns matches the first image on this page. Your Values well should look like this.

6. Pin the table to the dashboard by selecting the pin icon

Format the table

There are many ways to format a table and we'll only cover a few of them here. A great way to learn about the
other formatting options is to open the Formatting pane (paint roller icon ) and explore.
Try formatting the table grid. Here we've added a blue vertical grid, added space to the rows, increased the
outline and text size a bit.
For the column headers we changed the background color, added an outline, and increased the font size.
 You can even apply formatting to individual columns and column headers. Start by expanding Field
formatting and selecting the column to format from the dropdown. Depending on the column values, Field
formatting lets you set things like: display units, font color, number of decimal places, background,
alignment, and more. Once you've adjusted the settings, decide whether to apply those settings to the
header and totals row as well.

And after some additional formatting, here is our final table. Since there are so many formatting options,
the best way to learn is to start with the default formatting, open the Formatting pane , and start
exploring.

Conditional formatting
One type of formatting is referred to as conditional formatting and is applied to fields in the Values well of the
Visualizations pane in Power BI service or Desktop.
With conditional formatting for tables, you can specify customized cell background colors and font colors based on
cell values, including using gradient colors.
1. In the Visualizations pane in Power BI service or Desktop, select the down-arrow beside the value in the
Values well that you want to format (or right-click the field). You can only manage conditional formatting
for fields in the Values area of the Fields well.
2. Select Background color scales. In the dialog that appears, you can configure the color, as well as the
Minimum and Maximum values. If you select the Diverging box, you can configure an optional Center
value as well.

Let's apply some custom formatting to our Average Unit Price values. Select Diverging, add some colors,
and choose OK.

3. Add a new field to the table that has both positive and negative values. Select Sales > Total Sales
Variance.

4. Add data bar conditional formatting by selecting the down-arrow beside Total Sales Variance and
choosing Conditional formatting > Data bars.
5. In the dialog that appears, set colors for Positive bar, Negative bar, place a checkmark next to Show bar
only, and make any other changes you'd like.

When you select OK, data bars replace the numerical values in the table making it easier to scan.

6. To remove conditional formatting from a visualization, just right-click the field again, and select Remove
Conditional Formatting.

TIP
Conditional formatting is also available from the Formatting pane (paintroller icon). Select the value to format and then set
Color scales or Data bars to On to apply the default settings or, to customize the settings, select Advanced controls.

Copy values from Power BI tables for use in other applications

Your table or matrix may have content that you'd like to use in other applications, like Dynamics CRM, Excel, and
even other Power BI reports. With the Power BI right-click, you can copy a single cell or a selection of cells onto
your clipboard, and paste into the other application.
To copy the value of a single cell, select the cell, right-click, and choose Copy value. With the unformatted
cell value on your clipboard, you can now paste it into another application.
 To copy more than a single cell, select a range of cells or use CTRL to select one or more cells. The copy will
include the column and row headers.

The copy includes the column and row headers.

Adjust the column width of a table

Sometimes Power BI will truncate a column heading in a report and on a dashboard. To show the entire column
name, hover over the space to the right of the heading to reveal the double arrows, select and drag.

Considerations and troubleshooting

When applying column formatting, you can only choose one alignment option per column: Auto, Left, Center,
Right. Usually, a column contains all text or all numbers, and not a mix. But in cases where a column contains
both numbers and text, Auto will align left for text and right for numbers. This behavior supports languages
where you read left-to-right.
Next steps
Treemaps in Power BI
Visualization types in Power BI
 Treemaps in Power BI
2/13/2019 • 3 minutes to read • Edit Online

Treemaps display hierarchical data as a set of nested rectangles. Each level of the hierarchy is represented by a
colored rectangle (often called a "branch") containing other rectangles ("leaves"). The space inside each rectangle is
allocated based on the value being measured. And the rectangles are arranged in size from top left (largest) to
bottom right (smallest).

For example, if I'm analyzing my sales, I might have top-level rectangles, also called branches, for the clothing
categories: Urban, Rural, Youth, and Mix. My category rectangles would be split into smaller rectangles, also
called leaves, for the clothing manufacturers within that category. And these smaller rectangles would be sized and
shaded based on the number sold.
In the Urban branch above, lots of Maximus clothing was sold, less Natura and Fama , and few Leo . So, the
Urban branch of my Treemap would have:
the largest rectangle for Maximus in the top left corner
slightly smaller rectangles for Natura and Fama
lots of other rectangles for all the other clothing sold, and
a tiny rectangle for Leo .
And I could compare the number of items sold across the other clothing categories by comparing the size and
shading of each leaf node; larger and darker rectangles mean higher value.

When to use a treemap

Treemaps are a great choice:
to display large amounts of hierarchical data.
when a bar chart can't effectively handle the large number of values.
to show the proportions between each part and the whole.
to show the pattern of the distribution of the measure across each level of categories in the hierarchy.
to show attributes using size and color coding.
to spot patterns, outliers, most-important contributors, and exceptions.
Prerequisites
Power BI service or Power BI Desktop
Retail Analysis sample

Create a basic treemap

Want to watch someone else create a treemap first? Skip to 2:10 in this video to watch Amanda create a treemap.
https://www.youtube.com/embed/IkJda4O7oGs
Or, create your own treemap. These instructions use the Retail Analysis Sample. To follow along, sign in to Power
BI service and select Get Data > Samples > Retail Analysis Sample > Connect > Go to dashboard. Creating
visualizations in a report requires edit permissions to the dataset and report. Luckily, the Power BI samples are
editable. But you can't add visualizations to a report that someone has shared with you.
1. Select the "Total stores" tile to open the Retail Analysis sample report.
2. Open Editing View and select the Sales > Last Years Sales measure.

3. Convert the chart to a treemap.

4. Drag Item > Category to the Group well. Power BI creates a treemap where the size of the rectangles is
based on total sales and the color represents the category. In essence you've created a hierarchy that
visually describes the relative size of total sales by category. The Men's category has the highest sales and
the Hosiery category has the lowest.
5. Drag Store > Chain to the Details well to complete your treemap. You can now compare last year's sales
by category and chain.

NOTE
Color Saturation and Details cannot be used at the same time.

6. Hover over a Chain area to reveal the tooltip for that portion of the Category. For example, hovering over
Fashions Direct in the 090-Home rectangle reveals the tooltip for Fashion Direct's portion of the Home
category.

7. Add the treemap as a dashboard tile (pin the visual).

8. Save the report.

Highlighting and cross-filtering

For information about using the Filters pane, see Add a filter to a report.
Highlighting a Category or Detail in a treemap cross-highlights and cross-filters the other visualizations on the
report page... and vice versa. To follow along, either add some visuals to this report page or copy the treemap to
one of the other non-blank pages in this report.
1. On the treemap, select either a Category or a Chain within a Category. This cross-highlights the other
visualizations on the page. Selecting 050-Shoes, for example, shows me that last year's sales for shoes was
$3,640,471 with $2,174,185 of that coming from Fashions Direct.

2. In the Last Year Sales by Chain pie chart, selecting the Fashions Direct slice, cross-filters the treemap.

3. To manage how charts cross-highlight and cross-filter each other, see Visualization interactions in a Power
 BI report

Next steps
Waterfall charts in Power BI
Visualization types in Power BI
 Waterfall charts in Power BI
2/13/2019 • 2 minutes to read • Edit Online

A waterfall chart shows a running total as values are added or subtracted. It's useful for understanding how an
initial value (for example, net income) is affected by a series of positive and negative changes.
The columns are color coded so you can quickly tell increases and decreases. The initial and the final value
columns often start on the horizontal axis, while the intermediate values are floating columns. Because of this
"look", waterfall charts are also called bridge charts.
https://www.youtube.com/embed/qKRZPBnaUXM

When to use a waterfall chart

Waterfall charts are a great choice:
when you have changes for the measure across time series or different categories
to audit the major changes contributing to the total value
to plot your company's annual profit by showing various sources of revenue and arrive at the total profit (or
loss).
to illustrate the beginning and the ending headcount for your company in a year
to visualize how much money you make and spend each month, and the running balance for your account.

Create a waterfall chart

We'll create a waterfall chart that displays sales variance (estimated sales versus actual sales) by month. To follow
along, sign in to Power BI and select Get Data > Samples > Retail Analysis Sample.
1. Select the Datasets tab and scroll to the new "Retail Analysis Sample" dataset. Select the Create report
icon to open the dataset in report editing view.

2. From the Fields pane, select Sales > Total Sales Variance.
3. Convert the chart to a Waterfall. If Total Sales Variance isn't in the Y Axis area, drag it there.

4. Select Time > FiscalMonth to add it to the Category well.

5. Sort the waterfall chart chronologically. From the top-right corner of the chart, select the ellipses (...) and
choose FiscalMonth.

6. Dig in a little more to see what's contributing most to the changes month to month. Drag Store > Territory
to the Breakdown bucket.
7. By default, Power BI adds the top 5 contributors to increases or decreases by month. But we're only
interested in the top 2 contributors. In the Formatting pane, select Breakdown and set Maximum to 2.

A quick review reveals that the territories of Ohio and Pennsylvania are the biggest contributors to
movement, negative and positive, in our waterfall chart.

8. This is an interesting finding. Do Ohio and Pennsylvania have such a significant impact because sales in
these 2 territories are much higher than the other territories? We can check that. Create a map that looks at
this year sales value and last year sales by territory.

Our map supports our theory. It shows that these 2 territories had the highest value of sales last year
(bubble size) and this year (bubble shading).

Highlighting and cross-filtering

For information about using the Filters pane, see Add a filter to a report.
Highlighting a column in a waterfall chart cross-filters the other visualizations on the report page... and vice versa.
However, the Total column does not trigger highlighting or respond to cross-filtering.

Next steps
Visual interactions
Visualization types in Power BI
 Create dynamic reference lines for visuals in the
Power BI service
2/13/2019 • 2 minutes to read • Edit Online

With the Analytics pane in Power BI service, you can add dynamic reference lines to visualizations, and provide
focus for important trends or insights.

NOTE
The Analytics pane only appears when you select a visual on the report canvas.

Use the Analytics pane

With the Analytics pane, you can create the following types of dynamic reference lines (not all lines are available
for all visual types):
X-Axis constant line
Y -Axis constant line
Min line
Max line
Average line
Median line
Percentile line
To view the available dynamic reference lines for a visual, follow these steps:

1. Select or create a visual, then select the Analytics icon from the Visualizations pane.
2. Select the down arrow for the type of line you want to create to expand its options. In this case, we'll select
Average Line.

3. To create a new line, select + Add and decide the measure that will be used to create the line. The Measure
dropdown is automatically populated with available data from the selected visualization. Let's use Open
store count.
4. You have all sorts of options for your line, such as color, transparency, style, and position (relative to the
visual's data elements). If you want to label the line, give it a title and then move the Data label slider to On.
In this case, we'll title the line Avg # Open Stores, and customize a few of the other options as shown below.
5. Notice the number that appears next to the Average line item in the Analytics pane. That tells you how
many dynamic lines you currently have on your visual, and of which type. If we add a Constant line as a
store count goal of 9, you can see that the Analytics pane shows that we now also have a Constant line
reference line applied to this visual.

There are all sorts of interesting insights you can highlight by creating dynamic reference lines with the Analytics
pane.

Considerations and troubleshooting

If the visual you've selected can't have dynamic reference lines applied to it (in this case, a Map visual), you'll see
the following when you select the Analytics pane.

The ability to use dynamic reference lines is based on the type of visual being used. The following list shows which
dynamic lines are currently available for which visuals:
Full use of dynamic lines are available on the following visuals:
Area chart
Line chart
Scatter chart
Clustered Column chart
Clustered Bar chart
The following visuals can use only a constant line from the Analytics pane:
Stacked Area
Stacked Bar
Stacked Column
100% Stacked Bar
 100% Stacked Column
For the following visuals, a trend line is currently the only option:
Non-stacked Line
Clustered Column chart
Lastly, non-Cartesian visuals cannot currently apply dynamic lines from the Analytics pane, such as:
Matrix
Pie chart
Donut
Table

Next steps
Analytics pane in Power BI Desktop
More questions? Try the Power BI Community
 Resolve issues importing Access and .XLS files in
Power BI Desktop
1/14/2019 • 3 minutes to read • Edit Online

In Power BI Desktop, both Access databases and early versions of Excel workbooks (.XLS files of type Excel
97-2003) use the Access Database Engine. There are three common situations that can prevent the Access
Database Engine from working properly:

Situation 1: No Access Database Engine Installed

When the Power BI Desktop error message indicates the Access Database Engine is not installed, you must install
the Access Database Engine version, either 32-bit or 64-bit, that matches your Power BI Desktop version. You can
install the Access Database Engine from the downloads page.

NOTE
If the installed Access Database Engine bit version is different from your Microsoft Office installation's bit version, Office
applications will not be able to use the Access Database Engine.

Situation 2: The Access Database Engine bit version (32-bit or 64-bit) is

different from your Power BI Desktop bit version
This situation often occurs when the installed version of Microsoft Office is 32-bit, and the version of Power BI
Desktop installed is 64-bit. The opposite can occur as well, and the bit-version mismatch with occur in either case
(if you're using an Office 365 subscription, see Situation 3 for a different issue and resolution). Any of the
following solutions can remedy this bit-version mismatch error:
1. Change the version of Power BI Desktop to match the bit-version of your Microsoft Office installation. To
change the bit-version of Power BI Desktop, uninstall Power BI Desktop, and then install the version of
Power BI Desktop that matches your Office installation. To select a version of Power BI Desktop, on the
download page for desktop select Advanced download options.

On the download page that appears, choose your language and then select the Download button. On the
screen that appears, select the checkbox beside PBIDesktop.msi for the 32-bit version, or
PBIDesktop_x64.msi for the 64-bit version. In the following screen, the 64-bit version is selected.
 NOTE
When using the 32-bit version of Power BI Desktop, when creating very large data models you might experience out-
of-memory issues.

2. Change the version of Microsoft Office to match the bit-version of your Power BI Desktop installation. To
change the bit-version of Microsoft Office, uninstall Office, and then install the version of Office that
matches your Power BI Desktop installation.
3. If the error occurred when attempting to open an .XLS file (an Excel 97-2003 workbook), you can avoid
using the Access Database Engine by opening the .XLS file in Excel, and saving it as an XLSX file.
4. If the previous three solutions are not feasible, it is possible to install both versions of the Access Database
Engine, but this is not a recommended workaround. Installing both versions will resolve this issue for Power
Query for Excel and Power BI Desktop, but will introduce errors and issues for any application that
automatically (by default) uses the bit-version of the Access Database Engine that was installed first. To
install both bit-versions of the Access Database Engine, download both versions, then run each of them
using the /passive switch. For example:

c:\users\joe\downloads\AccessDatabaseEngine.exe /passive

c:\users\joe\downloads\AccessDatabaseEngine_x64.exe /passive

Situation 3: Trouble using Access or .XLS files with an Office 365

subscription
If you are using an Office 365 subscription, whether Office 2013 or Office 2016, the Access Database Engine
provider is registered in a virtual registry location that is only accessible to Office processes. As a result, the
Mashup Engine (which is responsible for running non-Office 365 Excel and Power BI Desktop), which is not an
Office process, cannot use the Access Database Engine provider.
To remedy this situation, you can download and install the Access Database Engine redistributable that matches the
bit version of your Power BI Desktop installation (see earlier sections for more information about bit-versions).

Other situations that cause import issues

We strive to cover as many issues that occur with Access or .XLS files as possible. If you encounter an issue that
isn't covered in this article, please submit a question about the issue to Power BI Support. We regularly look at
issues that may be affecting many customers, and include them in our articles.
 Resolve Issues when Power BI Desktop will not launch
2/13/2019 • 3 minutes to read • Edit Online

In Power BI Desktop, users who installed and are running previous versions of the Power BI On-premises data
gateway can be blocked from launching Power BI Desktop, due to administrative policy restrictions that the Power
BI on-premises gateway placed on named pipes on the local machine.

Resolve issues with the On-premises data gateway and Power BI

Desktop
There are three options to resolve the issue associated with the On-premises data gateway, and enable Power BI
Desktop to launch:
Resolution 1: Install the latest version of Power BI On-premises data gateway
The latest version of the Power BI On-premises data gateway does not place named pipe restrictions on the local
machine, and allows Power BI Desktop to launch properly. If you need to continue using Power BI On-premises
data gateway, this is the recommended resolution. You can download the latest version of Power BI On-premises
data gateway from this location. Note that the link is a direct download link to the installation executable.
Resolution 2: Uninstall or stop the Power BI On-premises data gateway Windows service
If you no longer need the Power BI On-premises data gateway, you can uninstall it, or you can stop the Power BI
On-premises data gateway Windows service, which removes the policy restriction, and allows Power BI Desktop to
launch.
Resolution 3: Run Power BI Desktop with administrator privilege
Alternatively, you can successfully launch Power BI Desktop as administrator, which also allows Power BI Desktop
to successfully launch. It is still recommended that you install the latest version of Power BI On-premises data
gateway, as described earlier in this article.
It's important to note that Power BI Desktop is engineered as a multiprocess architecture, and several of these
processes communicate using Windows named pipes. There may be other processes that interfere with those
named pipes. The most common reason for such interference is security, including situations where antivirus
software or firewalls might be blocking the pipes or redirecting traffic to a specific port. Launching Power BI
Desktop with administrator privilege may resolve that issue. If launching with administrator privilege isn't possible,
contact your administrator to determine which security rules are getting applied that prevent named pipes from
properly communicating, and whitelist Power BI Desktop and its respective subprocesses.

Resolve issues when connecting to SQL Server

If you encounter an error message similar to the following, when connecting to a SQL Server database, you can
often resolve the issue by launching Power BI Desktop as an administrator, and then making the SQL Server
connection:

"An error happened while reading data from the provider: 'Could not load file or assembly
'System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxxx' or one of its
dependencies. Either a required impersonation level was not provided, or the provided impersonation level is
invalid. (Exception from HRESULT: 0x80070542)'"

After launching as an administrator and establishing the connection, the required DLLs are registered properly.
After that, launching Power BI Desktop as an administrator isn't necessary.
Help with other issues when launching Power BI Desktop
We strive to cover as many issues that occur with Power BI Desktop as possible. We regularly look at issues that
may be affecting many customers, and include them in our articles.
If the issue with launching Power BI Desktop is not associated with the On-premises data gateway, or when the
previous resolutions don't work, you can submit a support incident to Power BI support
(https://support.powerbi.com) to help identify and solve your issue.
For other issues you may encounter in the future with Power BI Desktop (we hope there are none, or very few ), it
is helpful to turn on tracing and gather log files, to better isolate and identify the issue. To turn on tracing, select
File > Options and settings > Options and then select Diagnostics, then check Enable tracing under
Diagnostic Options. We realize that Power BI Desktop must be running to set this option, which is more helpful
for future issues associated with launching Power BI Desktop.
 Data types in Power BI Desktop
2/13/2019 • 9 minutes to read • Edit Online

This article describes data types supported in Power BI Desktop and Data Analysis Expressions (DAX).
When you load data into Power BI Desktop, it will attempt to convert the data type of the source column into a
data type that better supports more efficient storage, calculations, and data visualization. For example, if a column
of values you import from Excel has no fractional values, Power BI Desktop will convert the entire column of data
to a Whole Number data type, which is better suited for storing integers.
This concept is important because some DAX functions have special data type requirements. While in many cases
DAX will implicitly convert a data type for you, there are some cases where it will not. For instance, if a DAX
function requires a Date data type and the data type for your column is Text, the DAX function will not work
correctly. So, it’s both important and useful to get the correct data type for a column. Implicit conversions are
described later in this article.

Determine and specify a column’s data type

In Power BI Desktop, you can determine and specify a column’s data type in the Query Editor, or in Data View or
Report View:
Data types in Query Editor

Data types in Data View or Report View

The Data Type drop down in Query Editor has two data types not currently present in Data or Report View:
Date/Time/Timezone and Duration. When a column with these data types is loaded into the model and viewed
in Data or Report view, a column with a Date/Time/Timezone data type will be converted into a Date/Time, and a
column with a Duration data type is converted into a Decimal Number.
Number types
Power BI Desktop supports three number types:
Decimal Number – Represents a 64 bit (eight-byte) floating point number. It’s the most common number type
and corresponds to numbers as you usually think of them. Although designed to handle numbers with fractional
values, it also handles whole numbers. The Decimal Number type can handle negative values from -1.79E +308
through -2.23E -308, 0, and positive values from 2.23E -308 through 1.79E + 308. For example, numbers like 34,
34.01, and 34.000367063 are valid decimal numbers. The largest value that can be represented in a Decimal
Number type is 15 digits long. The decimal separator can occur anywhere in the number. The Decimal Number
type corresponds to how Excel stores its numbers.
Fixed Decimal Number – Has a fixed location for the decimal separator. The decimal separator always has four
digits to its right and allows for 19 digits of significance. The largest value it can represent is
922,337,203,685,477.5807 (positive or negative). The Fixed Decimal Number type is useful in cases where
rounding might introduce errors. When you work with many numbers that have small fractional values, they can
sometimes accumulate and force a number to be slightly off. Since the values past the four digits to the right of
decimal separator are truncated, the Fixed Decimal type can help you avoid these kinds of errors. If you’re familiar
with SQL Server, this data type corresponds to SQL Server’s Decimal (19,4), or the Currency Data type in Power
Pivot.
Whole Number – Represents a 64 bit (eight-byte) integer value. Because it’s an integer, it has no digits to the
right of the decimal place. It allows for 19 digits; positive or negative whole numbers between -
9,223,372,036,854,775,808 (-2^63) and 9,223,372,036,854,775,807 (2^63-1). It can represent the largest possible
number of the various numeric data types. As with the Fixed Decimal type, the Whole Number type can be useful
in cases where you need to control rounding.

NOTE
The Power BI Desktop data model supports 64 bit integer values, but the largest number the visuals can safely express is
9,007,199,254,740,991 (2^53-1) due to JavaScript limitations. If you work with numbers in your data model above this, you
can reduce the size through calculations before adding them to a visual

Date/time types
Power BI Desktop supports five Date/Time data types in Query View and three in the Report View and model.
Both Date/Time/Timezone and Duration are converted during load into the model.
Date/Time – Represents both a date and time value. Underneath the covers, the Date/Time value is stored as a
Decimal Number Type. So you can actually convert between the two. The time portion of a date is stored as a
fraction to whole multiples of 1/300 seconds (3.33 ms). Dates between years 1900 and 9999 are supported.
Date – Represents just a Date (no time portion). When converted into the model, a Date is the same as a
Date/Time value with zero for the fractional value.
Time – Represents just Time (no Date portion). When converted into the model, a Time value is the same as a
Date/Time value with no digits to the left of the decimal place.
Date/Time/Timezone – Represents a UTC Date/Time. Currently, it’s converted into Date/Time when loaded into
the model.
Duration – Represents a length of time. It’s converted into a Decimal Number Type when loaded into the model.
As a Decimal Number type it can be added or subtracted from a Date/Time field with correct results. As a Decimal
Number type, you can easily use it in visualizations that show magnitude.
Text type
Text - A Unicode character data string. Can be strings, numbers, or dates represented in a text format. Maximum
string length is 268,435,456 Unicode characters (256 mega characters) or 536,870,912 bytes.
True/false type
True/False – A Boolean value of either a True or False.
Blanks/nulls type
Blank - Is a data type in DAX that represents and replaces SQL nulls. You can create a blank by using the BLANK
function, and test for blanks by using the ISBLANK logical function.
Table data type
DAX uses a table data type in many functions, such as aggregations and time intelligence calculations. Some
functions require a reference to a table; other functions return a table that can then be used as input to other
functions. In some functions that require a table as input, you can specify an expression that evaluates to a table;
for some functions, a reference to a base table is required. For information about the requirements of specific
functions, see DAX Function Reference.

Implicit and explicit data type conversion in DAX formulas

Each DAX function has specific requirements as to the types of data that are used as inputs and outputs. For
example, some functions require integers for some arguments and dates for others; other functions require text or
tables.
If the data in the column you specify as an argument is incompatible with the data type required by the function,
DAX in many cases will return an error. However, wherever possible DAX will attempt to implicitly convert the data
to the required data type. For example:
You can type a date as a string, and DAX will parse the string and attempt to cast it as one of the Windows date
and time formats.
You can add TRUE + 1 and get the result 2, because TRUE is implicitly converted to the number 1 and the
operation 1+1 is performed.
If you add values in two columns, and one value happens to be represented as text ("12") and the other as a
number (12), DAX implicitly converts the string to a number and then does the addition for a numeric result.
The following expression returns 44: = "22" + 22.
If you attempt to concatenate two numbers, Excel will present them as strings and then concatenate. The
following expression returns "1234": = 12 & 34.
Table of implicit data conversions
The type of conversion that is performed is determined by the operator, which casts the values it requires before
performing the requested operation. These tables list the operators, and indicate the conversion that is performed
on each data type in the column when it is paired with the data type in the intersecting row.

NOTE
Text data types are not included in these tables. When a number is represented as in a text format, in some cases Power BI
will attempt to determine the number type and represent it as a number.

Addition (+)

OPERATOR(+) INTEGER CURRENCY REAL DATE/TIME

INTEGER INTEGER CURRENCY REAL Date/time

 OPERATOR(+) INTEGER CURRENCY REAL DATE/TIME

CURRENCY CURRENCY CURRENCY REAL Date/time

REAL REAL REAL REAL Date/time

Date/time Date/time Date/time Date/time Date/time

For example, if a real number is used in an addition operation in combination with currency data, both values are
converted to REAL, and the result is returned as REAL.
Subtraction (-)
In the following table, the row header is the minuend (left side) and the column header is the subtrahend (right
side).

OPERATOR(-) INTEGER CURRENCY REAL DATE/TIME

INTEGER INTEGER CURRENCY REAL REAL

CURRENCY CURRENCY CURRENCY REAL REAL

REAL REAL REAL REAL REAL

Date/time Date/time Date/time Date/time Date/time

For example, if a date is used in a subtraction operation with any other data type, both values are converted to
dates, and the return value is also a date.

NOTE
Data models also support the unary operator, - (negative), but this operator does not change the data type of the operand.

Multiplication (*)

OPERATOR(*) INTEGER CURRENCY REAL DATE/TIME

INTEGER INTEGER CURRENCY REAL INTEGER

CURRENCY CURRENCY REAL CURRENCY CURRENCY

REAL REAL CURRENCY REAL REAL

For example, if an integer is combined with a real number in a multiplication operation, both numbers are
converted to real numbers, and the return value is also REAL.
Division (/)
In the following table, the row header is the numerator and the column header is the denominator.

OPERATOR(/)
(ROW/COLUMN) INTEGER CURRENCY REAL DATE/TIME

INTEGER REAL CURRENCY REAL REAL

 OPERATOR(/)
(ROW/COLUMN) INTEGER CURRENCY REAL DATE/TIME

CURRENCY CURRENCY REAL CURRENCY REAL

REAL REAL REAL REAL REAL

Date/time REAL REAL REAL REAL

For example, if an integer is combined with a currency value in a division operation, both values are converted to
real numbers, and the result is also a real number.
Comparison operators
In comparison expressions, Boolean values are considered greater than string values and string values are
considered greater than numeric or date/time values; numbers and date/time values are considered to have the
same rank. No implicit conversions are performed for Boolean or string values; BLANK or a blank value is
converted to 0/""/false depending on the data type of the other compared value.
The following DAX expressions illustrate this behavior:
=IF (FALSE ()>"true","Expression is true", "Expression is false"), returns "Expression is true"
=IF ("12">12,"Expression is true", "Expression is false"), returns "Expression is true"
=IF ("12"=12,"Expression is true", "Expression is false"), returns "Expression is false"
Conversions are performed implicitly for numeric or date/time types as described in the following table:

COMPARISON
OPERATOR INTEGER CURRENCY REAL DATE/TIME

INTEGER INTEGER CURRENCY REAL REAL

CURRENCY CURRENCY CURRENCY REAL REAL

REAL REAL REAL REAL REAL

Date/time REAL REAL REAL Date/Time

Handling blanks, empty strings, and zero values

In DAX, a null, blank value, empty cell, or a missing value is all represented by the same new value type, a BLANK.
You can also generate blanks by using the BLANK function, or test for blanks by using the ISBLANK function.
How blanks are handled in operations such as addition or concatenation depends on the individual function. The
following table summarizes the differences between DAX and Microsoft Excel formulas, in the way that blanks are
handled.

EXPRESSION DAX EXCEL

BLANK + BLANK BLANK 0(zero)

BLANK + 5 5 5

BLANK * 5 BLANK 0(zero)

EXPRESSION DAX EXCEL

5/BLANK Infinity Error

0/BLANK NaN Error

BLANK/BLANK BLANK Error

FALSE OR BLANK FALSE FALSE

FALSE AND BLANK FALSE FALSE

TRUE OR BLANK TRUE TRUE

TRUE AND BLANK FALSE TRUE

BLANK OR BLANK BLANK Error

BLANK AND BLANK BLANK Error

 Formula editor in Power BI Desktop
1/14/2019 • 2 minutes to read • Edit Online

Beginning with the October 2018 Power BI Desktop release, the formula editor (often referred to as the DAX
editor) includes robust editing and shortcut enhancements to make authoring and editing formulas easier and
more intuitive.

Using the formula editor

You can use the following keyboard shortcuts to increase your productivity and to streamline creating formulas in
the formula editor.

KEYBOARD COMMAND RESULT

Ctrl+C Copy line (empty selection)

Ctrl+G Go to line…

Ctrl+I Select current line

Ctrl+M Toggle Tab moves focus

Ctrl+U Undo last cursor operation

Ctrl+X Cut line (empty selection)

Ctrl+Enter Insert line below

Ctrl+Shift+Enter Insert line above

Ctrl+Shift+\ Jump to matching bracket

Ctrl+Shift+K Delete line

Ctrl+] / [ Indent/outdent line

Ctrl+Home Go to beginning of file

Ctrl+End Go to end of file

Ctrl+↑ / ↓ Scroll line up/down

Ctrl+Shift+Alt + (arrow key) Column (box) selection

Ctrl+Shift+Alt +PgUp/PgDn Column (box) selection page up/down

Ctrl+Shift+L Select all occurrences of current selection

Ctrl+Alt+ ↑ / ↓ Insert cursor above / below

 KEYBOARD COMMAND RESULT

Ctrl+F2 Select all occurrences of current word

Shift+Alt + (drag mouse) Column (box) selection

Shift+Alt + ↓ / ↑ Copy line up/down

Shift+Alt+→ Expand selection

Shift+Alt+← Shrink selection

Shift+Alt+I Insert cursor at end of each line selected

Alt+ ↑ / ↓ Move line up/down

Alt+PgUp / PgDn Scroll page up/down

Alt+Click Insert cursor

Home / End Go to beginning/end of line

Next steps
The following articles provide more information about formulas and DAX in Power BI Desktop.
DAX basics in Power BI Desktop
Learn DAX for Power BI
DAX reference
 Power BI Desktop privacy levels
1/14/2019 • 3 minutes to read • Edit Online

In Power BI Desktop, privacy levels specify an isolation level that defines the degree that one data source will be
isolated from other data sources. Although a restrictive isolation level blocks information from being exchanged
between data sources, it may reduce functionality and impact performance.
The Privacy Levels setting, found in File > Options and settings > Options and then Current File > Privacy
determines whether Power BI Desktop uses your Privacy Level settings while combining data. This dialog includes
a link to Power BI Desktop documentation about Privacy Levels and Privacy Levels (this article).

Configure a privacy level

With privacy level settings, you can specify an isolation level that defines the degree that one data source must be
isolated from other data sources.

SETTING DESCRIPTION EXAMPLE DATA SOURCES

Private data source A Private data source contains Facebook data, a text file containing
sensitive or confidential information, stock awards, or a workbook containing
and the visibility of the data source may employee review information.
be restricted to authorized users. A
private data source is completely
isolated from other data sources.
 SETTING DESCRIPTION EXAMPLE DATA SOURCES

Organizational data source An Organizational data source limits A Microsoft Word document on an
the visibility of a data source to a intranet SharePoint site with
trusted group of people. An permissions enabled for a trusted
Organizational data source is isolated group.
from all Public data sources, but is
visible to other Organizational data
sources.

Public data source A Public data source gives everyone Free data from the Microsoft Azure
visibility to the data contained in the Marketplace, data from a Wikipedia
data source. Only files, internet data page, or a local file containing data
sources, or workbook data can be copied from a public web page.
marked Public.

Configure privacy level settings

The Privacy settings dialog for each data source is found in File > Options and settings > Data source
settings.
To configure a data source privacy level, select the data source, then select Edit. The Data Source Settings dialog
appears, from which you can select the appropriate privacy level from the drop-down menu at the bottom of the
dialog, as shown in the following image.

Cau t i on

You should configure a data source containing highly sensitive or confidential data as Private.

Configure Privacy Levels

Privacy Levels is a setting that is set to Combine data according to your Privacy Level settings for each
source by default, which means that Privacy Levels is not enabled.
 SETTING DESCRIPTION

Combine data according to your Privacy Level settings Privacy level settings are used to determine the level of
for each source (on, and the default setting) isolation between data sources when combining data.

Ignore the Privacy levels and potentially improve Privacy levels are not considered when combining data,
performance (off) however, performance and functionality of the data may
increase.

Security Note: Enabling Privacy Levels by selecting Ignore the Privacy levels and potentially improve
performance in the Privacy Levels dialog could expose sensitive or confidential data to an unauthorized
person. Do not enable Privacy Levels unless you are confident that the data source does not contain sensitive
or confidential data.

Cau t i on

The Ignore the Privacy levels and potentially improve performance does not work in the Power BI service.
As such, Power BI Desktop reports with this setting enabled, which are then published to the Power BI service, do
not reflect this behavior when used in the service.
Configure Privacy Levels
In Power BI Desktop or in Query Editor, select File > Options and settings > Options and then Current File >
Privacy.
a. When Combine data according to your Privacy Level settings for each source is selected, data will be
combined according to your Privacy Levels setting. Merging data across Privacy isolation zones will result in some
data buffering.
b. When Ignore the Privacy levels and potentially improve performance is selected, the data will be
combined ignoring your Privacy Levels which could reveal sensitive or confidential data to an unauthorized user.
The setting may improve performance and functionality.

Security Note: Selecting Ignore the Privacy levels and potentially improve performance may improve
performance; however, Power BI Desktop cannot ensure the privacy of data merged into the Power BI Desktop
file.
 Connector extensibility in Power BI
1/14/2019 • 2 minutes to read • Edit Online

In Power BI, customers and developers can extend the data sources to which they can connect in many ways, such
as using existing connectors and generic data sources (such as ODBC, OData, Oledb, Web, CSV, XML, JSON ). In
addition to those data sources, developers can create data extensions referred to as Custom Connectors, and
certify a connector to make them become Certified Connectors.
Currently, the ability to use Custom Connectors is enabled using a feature switch. Before we move this feature
from beta to general availability, we've added a menu that allows you to securely control the level of custom code
you want to allow to run on your system: all custom connectors, or only connectors that are certified and
distributed by Microsoft in the Get Data dialogue.

Custom connectors
Custom Connectors can include a wide range of possibilities ranging from small APIs that are critical to your
business, to large industry specific services that Microsoft hasn't released a connector for. Many connectors are
distributed by the vendor themselves, and if you have need for a specific data connector, you should contact a
vendor.
To use a Custom Connector, put them in the [Documents]\Power BI Desktop\Custom Connectors folder, and
adjust the security settings as described in the following section.
You don't need to adjust security settings to use Certified Connectors.

Data extension security

To change data extension security settings, in Power BI Desktop select File > Options and Settings > Options
> Security.
Under Data Extensions you can select from two levels of security:
(Recommended) Only allow certified extensions to load
(Not Recommended) Allow any extension to load without warning

If you plan on using Custom Connectors or connectors that you or a third party have developed and distribute,
you must select "(Not Recommended) Allow any extension to load without warning". We don't recommend
that security setting unless you absolutely trust your Custom Connectors, since code in there can handle
credentials (including sending them over HTTP ) and ignore privacy levels.
At the "(Recommended)" security setting, if there are custom connectors on your system, an error is displayed
describing the connectors that can't load due to security.
To resolve the error and use those connectors, you must change your security settings to the "(Not
Recommended)" setting as described earlier, and restart Power BI Desktop.

Certified connectors
A limited subset of data extensions are considered Certified, and such certified connectors are available using the
Get Data dialogue, but the responsible party for maintenance and support is still the third-party developer who
created the connector. While Microsoft distributes these connectors, we are not responsible for their performance
or continued functionality.
If you would like a custom connector to be certified, have your vendor contact [email protected].
 Power BI Desktop videos
1/14/2019 • 2 minutes to read • Edit Online

We have a YouTube channel for Power BI!

The following list describes all available videos about Power BI Desktop. Select any of the links below to view the
associated video.
High-level overview of Power BI Desktop, from getting data and building a report to uploading this report
to Power BI so it can be refreshed and shared with other users.
https://www.youtube.com/embed/Qgam9M8I0xA
Learn how to build stunning reports using Power BI Desktop.
https://www.youtube.com/embed/IMAsitQ2cAc
Understand how to import, reshape and transform data using Query Editor in the Power BI Desktop.
https://www.youtube.com/embed/ByIUx-HmQbw
 Previous monthly updates to Power BI Desktop
3/29/2019 • 66 minutes to read • Edit Online

This article describes previous updates to Power BI Desktop. For the most current month's release, check out
Power BI Desktop latest updates.
You can always download the latest version of Power BI Desktop. If you're running Windows 10, you can also get
Power BI Desktop from the Windows Store. The monthly versions are the same even though the version
numbering may differ between the two, regardless of which way you install Power BI Desktop. See this article for
more information.
The links beside each update mean the following:
[video] excerpts play in a new browser tab, when the feature is being discussed.
Some features have an [article] that provides more detail.
Most features are explained in the monthly update [blog] post.
Lastly, some features are self-explanatory and don't need an article or video.
You can also watch the Latest Updates video from the beginning, right inside this article, by clicking on the play
icon on the video image found below the list of updates.
The following sections describe previous months' updates to Power BI Desktop.

February 2019 Update (2.66.5376.1681)

Our February updates made customers swoon and love all our new data connectors, features, and analytics
enhancements. Just like a box of chocolates, you never know what you get... but with this February update, all
changes were sweet and downright delicious.
You can download the latest version of Power BI Desktop. If you're running Windows 10, you can also get Power
BI Desktop from the Windows Store. The monthly versions are the same even though the version numbering
may differ between the two, regardless of which way you install Power BI Desktop. See this article for more
information.
The links beside each update mean the following:
[video] excerpts play in a new browser tab, when the feature is being discussed.
Some features have an [article] that provides more detail.
Most features are explained in the monthly update [blog] post.
Lastly, some features are self-explanatory and don't need and article or video.
You can also watch the Latest Updates video from the beginning, right inside this article, by clicking on the play
icon on the video image found below the list of updates.
The following updates are new to Power BI Desktop this month:
Reporting
Updates to the new filter pane (preview ) [video] [blog]
Cross-highlight on a single point in line charts [video] [blog]
Word wrap on titles [video] [blog]
Update default visual interaction to cross-filter [video] [blog]
Rounded corners for visual borders [video] [blog]
Analytics
Key influencers visual (preview ) [video] [blog]
Insights questions in Q&A [video] [blog]
Auto-generated suggested questions for Q&A explorer [video] [blog]
Improved Python & R script editor [video] [blog]
Custom visuals
Ten new custom visuals, new custom visuals feature [video] [blog]
Data connectivity
Microsoft Graph Security [video] [blog]
Guidanz' BI Connector for OBIEE [video] [blog]
MarkLogic [video] [blog]
Kronos Workforce Dimensions [video] [blog]
SurveyMonkey [video] [blog]
Qubole Presto [video] [blog]
Quick Base [video] [blog]
Sagra Emigo [video] [blog]
Other
Improved Live connect and DirectQuery error messages [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video channel describes and shows each of these updates. You can also see the videos from the blog
post.
https://www.youtube.com/embed/dMD25wfElLg

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

You can also download previous versions of Power BI Desktop if your organization requires it. We always
recommend that you use the most recent version of Power BI Desktop, rather than a previous version. All previous
versions have the following limitations:
Previous releases of Power BI Desktop are not being serviced - you should always use the most recent release
for the latest features and updates.
It may not be possible to open files created or saved in newer releases of Power BI Desktop with previous
versions of Power BI Desktop.
If you receive a warning when loading a report saved in a newer release of Power BI Desktop, then save that
report in the previous version, you lose any information related to new features.
We only archive the English versions of Power BI Desktop.
Select the following links to download this earlier version:
 February 2019 version of Power BI Desktop - 32-bit
February 2019 version of Power BI Desktop - 64-bit

January 2019 Update

There was no Power BI Desktop release in January 2019 - we were all busy having a happy holiday, spending time
with friends and family.

December 2018 Update (2.65.5313.621)

Our December updates made sugar plums dance in our customers' heads, or at least created compelling data-
driven visuals of said sugar plums.
You can now download the latest version of Power BI Desktop. If you're running Windows 10, you can also get
Power BI Desktop from the Windows Store. The monthly versions are the same even though the version
numbering may differ between the two, regardless of which way you install Power BI Desktop. See this article for
more information.
The links beside each update mean the following:
[video] excerpts play in a new browser tab, when the feature is being discussed.
Some features have an [article] that provides more detail.
Most features are explained in the monthly update [blog] post.
Lastly, some features are self-explanatory and don't need an article or video.
You can also watch the Latest Updates video from the beginning, right inside this article, by clicking on the play
icon on the video image found below the list of updates.
The following updates are new to Power BI Desktop this month:
Reporting
Smart guides for aligning objects on a page [video] [article] [blog]
ArcGIS Maps for Power BI updates [video] [article] [blog]
Fields list accessibility support [video] [article] [blog]
Set tab order for objects on a page [video] [article] [blog]
Tooltips for button visuals [video] [article] [blog]
Updated icons for Visual interactions [video] [article] [blog]
Analytics
Live connect support for Q&A (preview ) [video] [blog]
Modeling
DAX formula bar updates [video] [article] [blog]
Data view accessibility support [video] [article] [blog]
Custom visuals
One new custom visual [video] [blog]
Data connectivity
AtScale connector (Beta) [video] [blog]
Oracle Essbase connector (Beta) [video] [article] [blog]
Data preparation
Fuzzy merge - support for Top N best matches [video] [blog]
Other
High contrast support for all panes and report footer [video] [article] [blog]
Updated keyboard shortcut dialog [video] [article] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video channel describes and shows each of these updates. You can also see the videos from the blog
post.
https://www.youtube.com/embed/AHNlkjRFdYI

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

You can also download previous versions of Power BI Desktop if your organization requires it. We always
recommend that you use the most recent version of Power BI Desktop, rather than a previous version. All previous
versions have the following limitations:
Previous releases of Power BI Desktop are not being serviced - you should always use the most recent release
for the latest features and updates.
It may not be possible to open files created or saved in newer releases of Power BI Desktop with previous
versions of Power BI Desktop.
If you receive a warning when loading a report saved in a newer release of Power BI Desktop, then save that
report in the previous version, you lose any information related to new features.
We only archive the English versions of Power BI Desktop.
Select the following links to download this earlier version:
December 2018 version of Power BI Desktop - 32-bit
December 2018 version of Power BI Desktop - 64-bit

November 2018 Update (2.64.5285.582)

Our November updates were a bountiful harvest of new features and functionality. So you could sit down with
your family of data and analytics enthusiasts, pass the potatoes, and dig in to our feast of updates.
The following updates are new to Power BI Desktop in November:
Reporting
Expand and collapse matrix row headers [video] [article] [blog]
Copy and paste between Desktop files [video] [article] [blog]
Updated filtering experience (preview ) [video] [article] [blog]
Report accessibility improvements [video] [article] [blog]
Analytics
Color saturation on visuals upgraded to use conditional formatting [video] [blog]
Follow -up questions in the Q&A explorer [video] [blog]
Modeling
New modeling view (preview ) [video] [article] [blog]
Composite models now generally available [video] [article] [blog]
Modeling accessibility improvements [video] [article] [blog]
New DAX functions [video] [blog]
Custom visuals
Five new custom visuals [video] [blog]
Data connectivity
Azure Developer Operations Server connector [video] [blog]
PDF Connector support for Start Page and End Page parameters [video] [article] [blog]
Improved Azure Consumption Insights connector [video] [article] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video channel describes and shows each of these updates. You can also see the videos from the blog
post.
https://www.youtube.com/embed/1xsXXoyTxfk?controls=0

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

You can also download previous versions of Power BI Desktop if your organization requires it. We always
recommend that you use the most recent version of Power BI Desktop, rather than a previous version. All previous
versions have the following limitations:
Previous releases of Power BI Desktop are not being serviced - you should always use the most recent release
for the latest features and updates.
It may not be possible to open files created or saved in newer releases of Power BI Desktop with previous
versions of Power BI Desktop.
If you receive a warning when loading a report saved in a newer release of Power BI Desktop, then save that
report in the previous version, you lose any information related to new features.
We only archive the English versions of Power BI Desktop.
Select the following links to download this earlier version:
November 2018 version of Power BI Desktop - 32-bit
November 2018 version of Power BI Desktop - 64-bit

October 2018 Update (2.63.3272.40262)

Our October updates were spooky-good, frighteningly helpful, and sweeter than an orange bucket full of candy.
The following updates were new to Power BI Desktop in October:
Reporting
Search in filter cards [video] [article] [blog]
Accessibility improvements for authoring experiences [video] [article] [blog]
Performance improvements for ArcGIS Map [video] [blog]
Modeling
DAX editor improvements [video] [article] [blog]
Analytics
Composite models and aggregation support in the Power BI service (preview ) [video] [article - aggregations]
[article - composite models] [blog]
Explain the increase for non-additive measures [video] [blog]
Custom visuals
Five new custom visuals [video] [blog]
Data connectivity
Web by Example connector now generally available [video] [article] [blog]
SAP BW connector implementation v2 now generally available [video] [article] [blog]
SAP BW Message Server Connector now generally available [video] [blog]
Vertica connector now generally available [video] [blog]
Dynamics NAV and Dynamics 365 business Central connectors now generally available [video] [blog]
New Dynamics 365 business Central On-premises connector [video] [blog]
Data preparation
Data Profiling in Power Query Editor (preview ) [video] [blog]
Fuzzy Matching options for Merge Queries (preview ) [video] [blog]
Other areas
Control export data options for reports [video] [blog]
Transport layer security settings [video] [article] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video channel describes and shows each of these updates. You can also see the videos from the blog
post.
https://www.youtube.com/embed/cT3L2VzgBRU

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

You can also download previous versions of Power BI Desktop if your organization requires it. We always
recommend that you use the most recent version of Power BI Desktop, rather than a previous version. All previous
versions have the following limitations:
 Previous releases of Power BI Desktop are not being serviced - you should always use the most recent release
for the latest features and updates.
It may not be possible to open files created or saved in newer releases of Power BI Desktop with previous
versions of Power BI Desktop.
If you receive a warning when loading a report saved in a newer release of Power BI Desktop, then save that
report in the previous version, you lose any information related to new features.
We only archive the English versions of Power BI Desktop.
Select the following links to download this earlier version:
October 2018 version of Power BI Desktop - 32-bit
October 2018 version of Power BI Desktop - 64-bit

September 2018 Update (2.62.5222.582)

Our September updates were like settling in to an exciting new classroom. Hopefully you found these updates as
useful as a handful of just-sharpened No. 2 pencils.
The following updates were new to Power BI Desktop this month:
Reporting
Dot plot layout support in scatter charts [video] [article] [blog]
Copy value and selection from table and matrix visuals [video] [blog]
Built-in report theme options [video] [article] [blog]
Report page tooltips generally available, new Card support [video] [article] [blog]
Accessibility improvements for analytics and formatting pane support [video] [blog]
Analytics
Aggregations (preview ) [video] [article] [blog]
Custom visuals
Five new custom visuals [video] [blog]
Data connectivity
PDF file connector (preview ) [video] [article] [blog]
SAP BW connector - support for measure properties [video] [blog]
Dataflows connector (beta) [article] [blog]
Data preparation
M Intellisense [video] [blog]
Add column from examples - support for text padding [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/Rzw2WyI09kY
 NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

You can also download previous versions of Power BI Desktop if your organization requires it. We always
recommend that you use the most recent version of Power BI Desktop, rather than a previous version. All previous
versions have the following limitations:
Previous releases of Power BI Desktop are not being serviced - you should always use the most recent release
for the latest features and updates.
It may not be possible to open files created or saved in newer releases of Power BI Desktop with previous
versions of Power BI Desktop.
If you receive a warning when loading a report saved in a newer release of Power BI Desktop, then save that
report in the previous version, you lose any information related to new features.
We only archive the English versions of Power BI Desktop.
Select the following links to download this earlier version:
September 2018 version of Power BI Desktop - 32-bit
September 2018 version of Power BI Desktop - 64-bit

August 2018 Update (2.61.5192.321)

Our August updates were august in their own right, and followed quickly on the heels of July's big releases.
Hopefully you found these updates like a sunny day on the beach; dip your toes in, we think you'll find these
updates feel just right.
The following updates were new to Power BI Desktop in August:
Modeling
Data categories for measures [video] [article] [blog]
Statistical DAX functions [video] [blog]
Reporting
Export to PDF, and print your reports [video] [article] [blog]
Create bookmark groups [video] [article] [blog]
Theming is generally available [video] [article] [blog]
Slicer restatement [video] [blog]
Analytics
Conditional formatting by values [video] [article] [blog]
Python integration [video] [blog]
Q&A improvements [video] [blog]
Custom visuals
Five new custom visuals [video] [blog]
Data connectivity
Spark connector generally available [video] [blog]
 NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/dgv5HhHxxe8

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

You can also download previous versions of Power BI Desktop if your organization requires it. We always
recommend that you use the most recent version of Power BI Desktop, rather than a previous version. All previous
versions have the following limitations:
Previous releases of Power BI Desktop are not being serviced - you should always use the most recent release
for the latest features and updates.
It may not be possible to open files created or saved in newer releases of Power BI Desktop with previous
versions of Power BI Desktop.
If you receive a warning when loading a report saved in a newer release of Power BI Desktop, then save that
report in the previous version, you lose any information related to new features.
We only archive the English versions of Power BI Desktop.
Select the following links to download this earlier version:
August 2018 version of Power BI Desktop - 32-bit
August 2018 version of Power BI Desktop - 64-bit

July 2018 Update (2.60.5169.3201)

July's big updates were worthy of a fireworks show in their own right, with long-requested data and reporting
features that launch your visuals sky-high, and burst with arcing displays of colorful insights.
The following updates were new to Power BI Desktop in July:
Modeling
Composite models (Preview ) [video] [article] [blog]
Many-to-many relationships (Preview ) (associated with composite models) [video] [article] [blog]
Storage mode (Preview ) (associated with composite models) [video] [article] [blog]
Reporting
New visual header with more flexibility and formatting [video] [article] [blog]
Wallpaper formatting [video] [article] [blog]
Theming update - more visual and page control (Preview ) [video] [blog]
Tooltips for table and matrix [video] [blog]
Turn tooltips off for visuals [video] [blog]
Slicer accessibility [video] [blog]
Formatting pane improvements [video] [blog]
 Stepped line support for line and combo charts [video] [blog]
Turn off combo chart data labels for individual series [video] [blog]
Sorting experience improvement [video] [blog]
Analytics
Distribution factor insights [video] [blog]
Custom visuals
Power BI certified category [video] [blog]
Disabling specific organizational visuals [video] [blog]
Four new custom visuals [video] [blog]
Data connectivity
IBM DB2 DirectQuery connector (Preview ) [video] [blog]
Improvements to Web By Example connector [video] [article] [blog]
SAP HANA - default values for variables in Variable Input experience [video] [article] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/Mtig3rmIUe0

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

June 2018 Update (2.59.5135.101)

The sun was shining on June's updates, with features and improvements that warmed up your reports and let you
bask in the insights they provided.
The following updates were new to Power BI Desktop in June:
Reporting
High contrast support for reports [video] [article] [blog]
Donut radius control [video] [blog]
Pie and donut detail labels position control [video] [blog]
Format data labels separately for each measure in a combo chart [video] [blog]
Longer phone reports [video] [blog]
Custom visuals
Two new custom visuals [video] [blog]
Modeling
Filtering and sorting in data view [video] [article] [blog]
Improved locale filtering [video] [blog]
Data connectivity
SAP BusinessWarehouse connector improvements (new driver and improved performance, plus improved
support for hierarchy variables) [video] [article] [blog]
Spark connector now supports Windows Authentication [video] [blog]
OData V4 connector enhancements [video] [blog]
ODBC connector improvements (folding support for Top Rows, ability to filter navigation by DSN catalog)
[video] [blog]
Other
National cloud selector [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/4VpGtWSrssE

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

May 2018 Update (2.58.5103.281)

May's updates were a blooming collection of features and improvements that we hope spread sunshine on your
reports, and made them blossom with beautiful insights.
The following updates were new to Power BI Desktop in May:
Reporting
Conditional formatting by a different field [video] [blog]
Advanced slicer syncing [video] [blog]
Log axis improvements [video] [blog]
Data label options for funnel chart [video] [blog]
Set line stroke width to zero [video] [blog]
Analytics
Measure drillthrough [video] [article] [blog]
Power BI Premium
Incremental refresh (preview ) [video] [article] [blog]
Custom visuals
Many new custom visuals [video] [blog]
Data connectivity
New From Web connector - by example data extraction (preview ) [video] [article] [blog]
Common Data Service for Apps connector (beta) [video] [blog]
 Azure KustoDB connector (beta) [video] [blog]
Google BigQuery and Azure HDInsight Spark connectors now generally available [video] [blog]
Adobe Analytics connector update - support for multiple domain logins (preview ) [video] [blog]
Visual Studio Team Services connector update - analytics views support [video] [blog]
OLE DB connector update - support for alternate Windows credentials [video] [blog]
SAP BW DirectQuery connector update - improved technical name support [video] [blog]
Data preparation
Improvements to Add Column from Examples [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/-_GMCE1TLvQ

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

April 2018 Update (2.57.5068.501)

We're not fooling about how happy we were with April's updates to Power BI Desktop. We showered the
updates across a handful of areas, and hope they help you grow your future reports with amazing, beautiful
visuals.
The following updates were new to Power BI Desktop in April:
Reporting
Q&A Explorer [video] [blog]
Buttons to trigger actions [video] [article] [blog]
Combo chart line styles [video] [blog]
Improved default sort for visuals [video] [blog]
Numeric slicer now generally available [video] [blog]
Analytics
Update your linguistic schema [video] [article] [blog]
New DAX function: COMBINEVALUES () [video] [blog]
Custom visuals
Organizational visuals now generally available [video] [article] [blog]
Many new custom visuals [video] [blog]
Data connectivity
Adobe Analytics connector now generally available [video] [article] [blog]
SAP HANA connector improvement: Port selection [video] [article] [blog]
Dynamics 365 Business Central connector [video] [article] [blog]
 NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/W_Nb73Od_AI

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

March 2018 Update ()

We were feeling lucky as a four-leaf clover about March's updates to Power BI Desktop. The following updates
were new to Power BI Desktop in March:
Reporting
Report page tooltips [video] [blog]
Bookmarking is now generally available [video] [article] [blog]
Display units and precision control for Table and Matrix columns [video] [article] [blog]
Turn off the visual header in Reading mode for a report [video] [blog]
Improved default visual placement [video] [blog]
Custom visuals
Many new custom visuals [video] [article] [blog]
Data connectivity
Visual Studio Team Services connector improvements [video] [article] [blog]
SAP HANA connector enhancements [video] [article] [blog]
DirectQuery multidimensional support is now generally available
SSL certificate validation support
SAP BW DirectQuery now generally available [video] [article] [blog]
Azure Analysis Services connector now generally available [video] [article] [blog]
Other
Improved error reporting [video] [article] [blog]
View previous errors you've encountered [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/kuI6MMzDh34
 NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

February 2018 Update (2.55.5010.521)

Our hearts were full of love for the updates to Power BI Desktop in February, and we hope you found them just
as sweet as a box of chocolates.
The links beside each update mean the following:
[video] excerpts play in a new browser tab, when the feature is being discussed.
Some features have an [article] that provides more detail.
Most features are explained in the monthly update [blog] post.
Lastly, some features are self-explanatory and don't need and article or video.
You can also watch the Latest Updates video for this month from the beginning, right inside this article, by
clicking on the play icon on the video image found below the list of updates.
The following updates were new to Power BI Desktop in February 2018:
Reporting
Multi-select data points across multiple pages [video] [article] [blog]
Sync slicers across multiple pages of a report [video] [article] [blog]
Numeric range slicer improvement - whole number snapping (Preview ) [video] [article] [blog]
Faster geocoding for Bing maps (web Preview ) - up to 6x faster [video] [blog]
Overflow data labels for bar and column charts visuals [video] [blog]
Search the Formatting and Analytics panes [video] [article] [blog]
Custom visuals
Organization custom visuals (Preview ) [video] [article] [blog]
Analytics
Set a custom date table [video] [article] [blog]
Quick measures are now generally available [video] [article] [blog]
Data connectivity
Improvements to DirectQuery over SAP HANA (Preview ) [video] [article] [blog]
Other
DirectQuery performance improvements [video] [article] [blog]
Open and save performance improvements [video] [blog]
Show items with no data improvements [video] [blog]
Persistent filters control for upcoming Power BI service feature [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/KeVB5RwMzJo

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

January 2018 Update (2.54.4970.761)

We rang in the new year with a collection of updates to Power BI Desktop, and our new year's resolution is to
keep them coming.
The links beside each update mean the following:
[video] excerpts play in a new browser tab, when the feature is being discussed.
Some features have an [article] that provides more detail.
Most features are explained in the monthly update [blog] post.
Lastly, some features are self-explanatory and don't need and article or video.
You can also watch the Latest Updates video for this month from the beginning, right inside this article, by
clicking on the play icon on the video image found below the list of updates.
The following updates were new to Power BI Desktop in January:
Reporting
Show and hide pages [video] [blog]
Control data label background color for Cartesian and maps visuals [video] [blog]
Increase the area used for axis labels in charts [video] [blog]
Bar / column padding control [video] [blog]
Show dates as a hierarchy (preview ) [video] [blog]
Add an anchor date for a relative date slicer [video] [blog]
Top N selection in Q&A [blog]
Many new custom visuals [video] [blog]
Analytics
Correlation coefficient quick measure [blog]
Data connectivity
Support for Azure Active Directory authentication for Azure SQL Database and Data Warehouse connectors
[video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/W8Pp5wuCXJw
 NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

December 2017 Update (2.53.4954.481)

December brought a Ho-Ho-Whole lot of updates to Power BI Desktop, chock full of features gifts for all
business intelligence minded kids (and adults) to enjoy.
The links beside each update mean the following:
[video] excerpts play in a new browser tab, when the feature is being discussed.
Some features have an [article] that provides more detail.
Most features are explained in the monthly update [blog] post.
Lastly, some features are self-explanatory and don't need and article or video.
You can also watch the Latest Updates video from the beginning, right inside this article, by clicking on the play
icon on the video image found below the list of updates.
The following updates were new to Power BI Desktop in December:
Reporting
Q&A for report creation [video] [blog]
Cross-highlighting for bookmarks [video] [blog]
More bookmark flexibility [video] [blog]
Field properties pane and field descriptions [video] [blog]
Scatter visual from x- and y-axis groupings [video] [blog]
High density sampling for maps based on latitude and longitude [video] [blog]
Responsive slicers [video] [blog]
Recently released custom visuals [video] [blog]
Analytics
Drill filters other visuals [video] [blog]
Data connectivity
Adobe Analytics connector [video] [blog]
HDInsight Interactive Query connector [video] [blog]
Data.World connector [video] [blog]
SAP BW connector improvements [video] [blog]
IBM Netezza connector now generally available [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/ZPU8B -1BxjI
 NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

November 2017 Update (2.52.4921.202)

November brought a whole harvest worth of updates to Power BI Desktop.
The links beside each update mean the following:
[video] excerpts play in a new browser tab, when the feature is being discussed.
Some features have an [article] that provides more detail.
Most features are explained in the monthly update [blog] post.
Lastly, some features are self-explanatory and don't need and article or video.
You can also watch the Latest Updates video from the beginning, right inside this article, by clicking on the play
icon on the video image found below the list of updates.
The following updates were new to Power BI Desktop in November:
Reporting
Rule-based conditional formatting for Table and Matrix visuals [video] [blog]
Cell alignment for Table and Matrix visuals [video] [blog]
Control visual ordering through the selection pane [video] [blog]
Lock objects on your report [video] [blog]
Esri Plus Subscription is available for ArcGIS Maps for Power BI [video] [blog]
Report options for slow data sources [video] [blog]
Filtering performance improvements [video] [blog]
Recently released custom visuals [video] [blog]
Analytics
Cell-level formatting for multidimensional AS models for multi-row card [video] [blog]
Data connectivity
Impala connector - support for Windows Authentication [video] [blog]
Other
Query editing - Add Column from Example improvements [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/sI3yRjdnJ7w
 NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

October 2017 Update (2.51.4885.543)

October brought a frighteningly compelling group of useful updates to Power BI Desktop.
The links beside each update mean the following:
[video] excerpts play in a new browser tab, when the feature is being discussed.
Some features have an [article] that provides more detail.
Most features are explained in the monthly update [blog] post.
Lastly, some features are self-explanatory and don't need and article or video.
You can also watch the Latest Updates video from the beginning, right inside this article, by clicking on the play
icon on the video image found below the list of updates.
The following updates are new to Power BI Desktop this month:
Reporting:
Bookmarking (preview ) [video] [blog] [article]
Selection pane and visual display controls [video] [blog] [article]
Bookmark links for shapes and images [video] [blog] [article]
Spotlight [video] [blog] [article]
Scatter and Bubble markers [video] [blog] [article]
Increase the number of data points displayed in Scatter visuals [video] [blog]
Analytics:
Quick measures for SSAS live connections [video] [blog] [article]
Sales from new customers quick measure [video] [blog] [article]
Cell-level formatting for multi-dimensional Analysis Services (AS ) models [video] [blog]
Data Connectivity:
Vertica connector (beta) [video] [blog] [article]
SAP BW connector - support for additional member properties [video] [blog]
Other:
Get Power BI Desktop from the Windows Store [video] [blog] [article]
Improved access to help content [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/jksjtR8GnBE
 NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

September 2017 Update (2.50.4859.502)

The following updates are new to Power BI Desktop in September:
Report View:
Drillthrough to another report page [video] [blog] [article]
Ribbon chart [video] [blog] [article]
Insights about Explain the increase / Explain the decrease [video] [blog] [article]
Theming preview update - chart style controls [video] [blog] [article]
Accessibility improvements [video] [blog] [article]
Accessible See data [video] [blog] [article]
Keyboard shortcut helper dialog [video] [blog] [article]
High density scatter chart sampling [video] [blog] [article]
Gridline style control [video] [blog] [article]
New custom visuals [video] [blog]
Calendar by Tallan [video] [blog]
Enlighten Aquarium [video] [blog]
Visio visual (preview ) [video] [blog]
Impact bubble chart [video] [blog]
Data Connectivity:
Azure Consumption Insights connector [video] [blog] [article]
Improvements to the Dynamics 365 for Financials connector [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/moTQJlnClJw

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

August 2017 Update (2.49.4831.222)

The following updates were new to Power BI Desktop in August:
Report View:
Show values on rows for matrix [video] [blog]
 Color scales on font colors for table and matrix [video] [blog]
Custom subtotal settings per level of matrix [video] [blog]
Line styles and legend options [video] [blog]
Scatter chart performance improvements [video] [blog]
New custom visuals [video] [blog]
Dot Plot by MAQ Software [video] [blog]
Power KPI [video] [blog]
Funnel plot [video] [blog]
Beyondsoft Calendar [video] [blog]
Analytics & Modeling:
What if parameters [video] [blog]
New scatter chart analytics features [video] [blog]
Symmetry shading [video] [blog]
Ratio lines [video] [blog]
New quick measure: weighted average [video] [blog]
Data Connectivity:
Live connect to the Power BI service is generally available [video] [blog]
Google BigQuery connector (beta) [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/ND8U0yXroaQ

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

July 2017 Update (2.48.4792.321)

The following updates were new to Power BI Desktop in July:
Report View:
New table & matrix visuals are now generally available [video] [blog]
Renaming fields in visuals [video] [blog]
Custom visuals store integration [video] [blog]
Relative date filters [video] [blog]
Responsive layout for visuals (preview ) [video] [blog]
New waterfall chart option - breakdown [video] [blog]
Custom visual updates [video] [blog]
Drill down Choropleth [video] [blog]
Drill down Cartogram [video] [blog]
 Drill down Player [video] [blog]
Certified custom visuals [blog]
Analytics & Modeling:
Quick measures from the community [video] [blog]
Star rating [video] [blog]
Concatenated list of values [video] [blog]
Bidirectional cross filtering for DirectQuery is now generally available [video] [blog]
Data Connectivity:
Snowflake connector general availability [video] [blog]
Query Editing:
Add Column from Examples enhancements [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post references in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/4X96ow7FnSY

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

June 2017 Update (2.47.4766.542)

The following updates were new to Power BI Desktop in June:
Report View:
Data bars for new table and matrix visuals (Preview ) [video] [blog]
Markers on line, area, and combo visuals (Preview ) [video] [blog]
Visual font family setting [video] [blog]
Horizontal image slicer [video] [blog]
Combo chart formatting updates [video] [blog]
Bing maps improvements [video] [article] [blog]
High density line sampling [video] [article] [blog]
Accessible reports [video] [article] [blog]
Data Connectivity:
Custom Data Connectors support [video] [blog]
Power BI service Live Connect to on-premises and push streaming datasets [video] [blog]
Impala connector is now generally available [video] [blog]
Amazon Redshift connector is now generally available [video] [blog]
SAP BW connector - DirectQuery support [video] [blog]
IBM Netezza connector (beta) [video] [blog]
Query Editing:
Add Column from Examples enhancements [video] [article] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post referenced in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/YlNVE5dgcSI

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

May 2017 Update (2.46.4732.461)

The following updates were new to Power BI Desktop in May:
Report View:
Relative date slicer (Preview ) [video] [blog]
New table visual (Preview ) [video] [blog]
Combo chart data label enhancements [video] [blog]
More URL support in table and matrix visuals [video] [blog]
mailto links in textbox [video] [blog]
Analytics:
Report level measures for live connections to Analysis Services tabular models and Power BI service datasets
[video] [blog]
Two new quick measures (Preview ) [video] [blog]
Bin by count [video] [blog]
Data Connectivity:
Combine files - ability to reference First File as example [video] [blog]
New data connectors:
Dynamics 365 for Customer Insights [video] [blog]
Query Editing:
Two new transforms:
Extract text before/after/between delimiters [video] [blog]
Unpivot only selected columns [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post referenced in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/CKISVNHcHVA

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

April 2017 Update (2.45.4704.442)

The following updates were new to Power BI Desktop in April 2017:
Report View:
Rename axis titles [video] [blog]
New matrix visual enhancements: column sorting, column resizing, and word wrap (Preview ) [video] [article]
[blog]
Analytics:
Quick measures [video] [blog] [in-depth blog] [article]
Show value as [video] [blog]
Q&A in Spanish (Preview ) [video] [blog]
Data Connectivity:
Connect to datasets in the Power BI service (Preview ) [video] [article] [blog]
New or enhanced data connectors:
Redshift Connector: beta support, and Publish to Power BI service [video] [blog]
SAP HANA and BW: enhancements to parameter input experience [video] [blog]
Query Editing:
Add Column from Example [video] [article] [blog] [another blog]
Split column (by delimiter/number of characters) into rows [video] [blog]
Group by: basic mode [video] [blog]
Go to column [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post referenced in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/AWMaIaI8G2Y

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

March 2017 Update (2.44.4675.422)

The following updates were new to Power BI Desktop in March 2017:
Report View:
New matrix visual (Preview ) [video] [article] [blog]
Numeric range slicer (Preview ) [video] [article] [blog]
Data labels on pie and donut visuals - percent of total [video] [blog]
Cross-highlight using multiple series [video] [blog]
Textbox - ability to choose font color [video] [blog]
Report theming (Preview ) [video] [article] [blog]
Analytics:
Clustering - now generally available [video] [blog]
Data Connectivity:
New or enhanced data connectors [video]:
Azure Analysis Services database (Beta) [blog]
Azure Data Lake Store - now generally available [blog]
DB2 connector - option to specify package collection [video] [blog]
Combine binaries - specify a sample file to use [video] [blog]
Query Editing improvements
Split column by delimiter - automatic detection of delimiter character [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post referenced in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/CaRTON3lJqw

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

February 2017 Update (2.43.4647.541)

The following updates were new to Power BI Desktop in February:
Report View:
Word wrap on matrix row headers [video] [blog]
X- and Y -axis font size control [video] [blog]
Cartesian chart minimum category width [video] [blog]
Line chart line thickness and join type controls [video] [blog]
Analytics:
Two new Quick Calcs: Percent of row total, and percent of column total [video] [blog]
Data Connectivity:
 New or enhanced data connectors [video]:
ODBC and OLE DB connectors - support for Select related tables [blog]
Enhanced Folder connector - support for combining binaries from the Preview dialog [video] [blog]
Unified Text and CSV connectors [video] [blog]
New - PowerApps Common Data Service connector [blog]
Query Editing improvements
Quickly change a column's data type and locale with the new Using locale option in the Column headers type
menu [video] [blog]
Easily insert steps into existing queries, using the new Insert Step After option [video] [blog]
Other improvements
Solutions Templates and Partner Showcase quick access [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post referenced in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/mn75-LOPxMA

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

January 2017 Update (2.42.4611.482)

The following updates are new to Power BI Desktop in January:
Report View:
Table and matrix conditional formatting improvement - blank formatting [video] [blog]
New aggregations for string and dateTime columns [video] [blog]
Table header word wrap [video] [blog]
General Availability (GA) of Phone reports [video] [blog]
Data Connectors:
New or enhanced data connectors [video]:
Visual Studio Team Services connector (Beta) [video] [blog]
Enhanced SQL Server connector - support for SQL Failover option [video] [blog]
Query Editing improvements
New transform: extract values from a nested list [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.
Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post referenced in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/C1-f0T8vZ7M

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

November 2016 Update (2.41.4581.301)

The following updates were new to Power BI Desktop in November:
Report View:
Hierarchical axis [video] [blog]
Axis label and title color control [video] [blog]
Matrix conditional formatting [video] [blog]
Table and matrix column formatting [video] [blog]
Drop-down slicer [video] [blog]
Mobile reports scrolling [video] [blog]
Analytics
Clustering (preview ) [video] [blog]
Forecasting (now in the Power BI service) [blog]
Groups (now on the ribbon) [video] [blog]
Data Connectors:
New data connectors [video]:
Spark DirectQuery [video] [blog]
OData connector improvements [video] [blog]
Enhanced combine binaries experience [video] [blog]
Azure Analysis Services [video] [blog]
Query Editing improvements
Improved function authoring experience [video] [blog]
Support for percentage data type [video] [blog]
Added Maximize and Restore buttons in Navigator and Query Dependencies [video] [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post referenced in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/kERJ_WOLuLk
 NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

October 2016 Update (2.40.4554.361)

The following updates were new to Power BI Desktop in October:
Report View:
Improved date axis range formatting [video]
Date slicer [blog] [video]
Report gridlines and snap to grid (Preview ) [article] [blog] [video]
Data label improvements [blog] [video]
Map formatting options [blog] [video]
Improved date axis range formatting [blog]
Analytics
Grouping [blog] [video]
Binning [blog] [video]
Top-N filter [blog] [video]
Include/exclude data points [blog] [video]
R -powered custom visuals[blog]
Data Connectors:
New data connectors [video]:
Microsoft Dynamics 365 for Financials (Beta) [blog]
OLE DB [blog]
Mixpanel [blog]
Query Editing improvements
Support for table parameters in the Invoke Function dialog [blog] [video]
Other improvements
Diagnostics information in the About dialog [blog] [video]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post referenced in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/UXEYSvgvMaQ

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.
September 2016 Update (2.39.4526.362)
The following updates were new to Power BI Desktop in September:
Report View:
ArcGIS Maps for Power BI (Preview ) [blog] [video]
Mobile report layout (Preview ) [blog] [video]
Updated drill behavior [article] [blog] [video]
Analytics
Forecasting (Preview ) [article] [blog] [video]
Use your own R IDE [blog] [video]
Data Connectors:
New data connectors:
Snowflake connector DirectQuery support [blog]
ProjectPlace connector [article] [blog]
Improvements to existing connectors:
Oracle connector - improved Navigator previews performance [blog]
OData connector - support for Select Related Tables option [blog]
SAP Business Warehouse and SAP HANA connectors - enhancements to parameter input interface
[article] [blog]
Web connector - support for specifying HTTP request headers within the dialog [blog] [video]
Query Editor improvements:
Query Dependencies view [blog] [video]
Show Errors experience [blog]
Query Editor ribbon support for scalar values [blog]
Add function invocation column [blog]
Expand & Aggregate columns - support for Load More values [blog]
New transform - convert Table Column to a list [blog]
Key boarding - support for smart typing in drop-down menus [blog]
Other improvements
In-product links to the Power BI Community [blog] [video]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post referenced in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/pcUr6E8g_KI

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.
August 2016 Update (2.38.4491.282)
August introduced a full harvest of new features for Power BI Desktop:
[video] excerpts play in a new browser tab, when the feature is being discussed.
Some features have an [article] that provides more detail.
Most features are explained in the monthly update [blog] post.
Lastly, some features are self-explanatory and don't need and article or video.
You can also watch the Latest Updates video from the beginning, right inside this article, by clicking on the play
icon on the video image found below the list of updates.
The following updates are new to Power BI Desktop this month:
Report View:
Drill down (or back up) on line charts [blog] [video]
Continuous axis for the Date axis [blog] [video]
General availability of Inline Hierarchies [article] [blog] [video]
Predefined matrix styles (similar to table formatting in Excel) [blog] [video]
Reorder fields, in charts and tooltips [blog] [video]
Color formatting for KPI visuals [blog] [video]
Analytics (New!)
The all-new Analytics pane [article] [blog] [video]
Dynamic reference lines [blog] [video]
Data Connectors:
New data connectors:
Snowflake connector (Preview ) [blog]
Improvements to existing connectors:
Impala connector - DirectQuery support [article] [blog]
Web connector - Web page previews [blog] [video]
General availability for the SAP Business Warehouse connector [article] [blog]
Query Editor improvements:
Option to Merge/Append as New Query [blog] [video]
Other improvements
Auto-recover Desktop files [blog] [video]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features (this is the same blog post referenced in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/0VvG7Eqoke8
 NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

July 2016 Update (2.37.4464.321)

You can always download the latest version of Power BI Desktop.
July brought another great collection of new features and highly anticipated data connectors to Power BI Desktop.
The following enhancements were new to Power BI Desktop in July:
Report View:
Predefined table styles [blog] [video]
Shape Maps update - use custom maps [article] [blog] [video]
Data Connectors:
New data connectors:
Amazon Redshift [article] [blog]
Impala [article] [blog]
Improvements to existing connectors:
Web connector - support for specifying a connection timeout [blog]
CSV and Text - support for fixed-width delimited files [blog]
Improvements and changes to the SAP Business Warehouse connector [article] [blog]
Query Editor improvements:
Use R script in Query Editor [article] [blog]
Query parameter enhancements:
List query output as allowed values for a parameter [blog]
Overwrite existing user-defined functions [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these features (this is the same blog post referenced in the list above).
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/g8ccfjffWmw

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

June 2016 Update (2.36.4434.362)

You can always download the latest version of Power BI Desktop.
June provided a shining collection of interesting updates for Power BI Desktop.
Report View:
New visual - Shape Maps [video] [article]
Searchable slicers [video] [blog]
Configurable line chart labels [video] [blog]
New sign-in entry points [video] [blog]
Data Access:
Row Level Security [blog] [article]
Data Connectors:
New data connector: [blog]
Azure Enterprise
Enhanced SAP BW and HANA connectors: [blog]
Allow multi-select of values for Variables/Parameters
Support for Hierarchies in SAP BW
Enhanced OData connector - imports Open Type columns [blog]
Enhanced Access DB connector - button to Select Related Tables in Navigator dialog [blog]
Data Connectors:
Templates - option to Load or Edit [blog]
Query parameter enhancements: [blog]
Option to always allow Parameter specification
Create new parameter directly in context
Option to generate Step Names in English [blog]
Descriptions for Query Steps [video] [blog]
New Data Transformations: [blog]
Extract Week Day and Month Name from a DateTime column
Merging dates and Times into a DateTime column
Extract Time.Start/End of Hour/Minute/Second

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features.
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/sZsL2l6oS4A

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

May 2016 Update (2.35.4399.381)

You can always download the latest version of Power BI Desktop.
May brought another large collection of compelling updates for Power BI Desktop:
Report View:
Customizable tooltips [video] [article]
Conditional formatting in tables [video] [article]
Publish to Pyramid server [blog]
Scrolling loads more data in charts [video] [blog]
Keyboard nudging for visuals [blog]
Analytics
Quick Calcs - % of grand total [blog]
Data Connectivity:
New data connectors: [blog]
Informix
comScore Digital Analytix
Troux
Planview Enterprise
Improved DB2 connector [blog]
Text/CSV connector exposes editable settings in preview dialog [blog]
Improved relational database connectors with Display Schema information
Data Source Settings enhancements [blog]
Advanced Filter Rows dialog mode [blog]
Inline Input controls for Function invocation within Query Editor [blog]
Query Parameters: [blog]
Ability to convert queries to parameters (and vice versa)
Support for URL parameterization and multi-part URLs in Web connector
Support for parameterization in Conditional Columns dialog
Ability to Save As a Power BI Template [blog]
Support for reordering Query Steps using drag-and-drop [blog]
Date picker support in Conditional Columns dialog input Date fields [blog]
New context menu entry to create new queries from the Queries pane [blog]

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features.
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/KnDs4amt9-c

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

April 2016 Update (2.34.4372.322)

You can always download the latest version of Power BI Desktop.
In April, we showered our great Power BI customers with another collection of compelling updates for Power BI
Desktop. The following enhancements are new to Power BI Desktop this month:
Report View:
Additional styles on a table, matrix, and multi-row card
Trend lines on single visuals
New drill action - See Records
Map auto-zoom during drill/filter
In-line hierarchy labels for expanded view (Preview - see the article)
Data Modeling:
Modeling operations are no longer blocked while visuals are refreshing
Time Intelligence with built-in date hierarchy fields (Preview )
Data model synonyms
Data Connectivity:
Query Parameters
Power BI Template files
New Online Services category in Get Data dialog
New Connectors:
SharePoint Folder
Webtrends
SparkPost
tyGraph
Conditional Columns
DirectQuery - Specify DirectQuery vs. Import mode in data source dialogs
Column type indicator in Query Editor preview column headers
Reorder Queries and Query Groups using Drag & Drop gestures
Query Management menu in the ribbon

NOTE
You can also check out all the data sources available to Power BI Desktop; our list is always growing, so check back often.

Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features.
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/7IFZTYJR3Gk

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

March 2016 Update (2.33.4337.281)

You can now download the latest version of Power BI Desktop.
March brings all sorts of renewal and freshness, including another round of Power BI Desktop additions. The
following enhancements are new to Power BI Desktop this month:
Report View:
Publish reports to a Group Space in the Power BI service
Reports with KPI trends now respect Do Not Summarize model settings from SSAS MD
Data Point warnings are now non-intrusive
Data Modeling:
You can now change the data type of a column when using DirectQuery mode
Ability to assume Referential Integrity on relationships (for those imported, and created) in DirectQuery
DirectQuery for Oracle and Teradata is now part of Power BI Desktop (no long a preview feature)
Data Connectivity:
A new SAP BW Connector (preview feature)
Support for Command Timeout in the user interface (UI)
There's a setting available to disable Privacy Level prompts at the machine level (including a registry key)
Query Group Management enhancements:
Expand/Collapse All
Retain Query Group expansion state
New Transformations:
Remove Blanks using the Column Filter menu
Convert Duration values to Years
Keep Duplicates
Support for whitespace and line feeds in Query Editor preview
Include hints for sample input values in the Change Type with Locale dialog
Enhancements to the Navigator window:
Add schema information to navigation hierarchy for ODBC sources
Ability to disable preview from Navigator
Technical name support
Load: Auto-step to disambiguate conflicting column names (case-insensitive comparison)
You can now rename queries directly from the Queries pane
Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features.
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/eAayYDF9QzY

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

February 2016 Update (2.32.4307.362)

You can now download the latest version of Power BI Desktop.
We're leaping ahead with more updates this month! February brings 29 days to the month (it's a leap year), and
with it, 29 improvements to this monthly update of Power BI Desktop. The following enhancements are new to
Power BI Desktop this month:
Report View:
See Data Behind a Visual (including Export Data to CSV )
 Map improvements - plot map with latitude/longitude only
KPI consumption release support (including navigation hierarchy support and KPI trend for SSAS MD )
SSAS Exploration Mode: Support for Display folders in the Fields pane
Ribbon layout improvements: Contextual ribbon tab for Report Tools
New KPI visual
Get reports opened to the same page that was visible when they were saved
Edit Query option in table context menu in the Fields pane (Report & Data views)
Duplicate Page from the ribbon
Data Modeling:
Ability to define hierarchies
Performance Improvement: Table & Column rename optimizations
Data Connectivity:
DirectQuery support for Oracle and Teradata databases
DirectQuery - support for creating Calculated Columns
Support for publishing Analysis Services Live reports
JSON File connector
SQL Sentry connector
Support for jagged CSV files
Exchange Connector - OAuth support
SharePoint List Connector - URL validation
Database Connectors - ability to disable Navigation Columns in Query previews (Performance optimization)
Web Connector - fine-grained scoping of Credentials
Enter Data dialog UX enhancements
SAP HANA - Support for single sign-on with Windows Authentication (Power BI Desktop only)
SAP HANA - Support for Field labels
Alphabetical sort of columns in Choose Columns builder
Improved performance of renaming/removing/reordering columns
Virtualized Preview in Query Editor
Visual indicator for unloaded queries in Query Editor
1-click Percentage transform
Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features.
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/J5gZ65Wexh4

NOTE
You might also be interested in learning what's new in the Power BI service, and also check out what's new in the mobile
apps for Power BI.

January 2016 Update (2.31.4280.361)

You can now download the latest version of Power BI Desktop.
Ring in the new year with another collection of improvements and enhancements to Power BI Desktop. The
following enhancements are new to Power BI Desktop this month:
Report View:
Add borders to a visual
Add an image background to a visual
Data Connectivity:
DirectQuery: you can now create measures when using DirectQuery mode
You can now refresh data for individual tables from the Field List (in Report view and Data view ), rather than
(and in addition to) just being able to refresh all from the ribbon
General Availability (GA) for SQL Server Analysis Services Multidimensional models Exploration mode (no
longer a preview feature)
Enhancements to hierarchy support
General Availability (GA) for the SAP HANA connector (no longer a preview feature)
Ability to append multiple tables within a single Append operation
Option to disable data previews to download in the background (performance optimization)
Other Improvements:
Support for Internet Explorer 9 (IE9) browser
Performance improvements for report rendering, cross-highlighting, and otherwise
Improvements to R integration in Power BI Desktop
Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features.
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/ek8dwi33-24

December 2015 Update (2.30.4246.181)

December is a month for giving, and the Power BI team is following suit with more updates, features, and more
functionality in this month's Power BI Desktop update. The following enhancements are new to Power BI Desktop
this month:
Report Authoring:
Formatting Pane and Ribbon:
Format data labels per category services
Change the number of decimal places shown in visuals
Change text size in visuals
Ability to layout visuals accurately: alignment, distribute, size, position
Set styles across multiple visuals through Format Painter
Optimized Home ribbon layout
Enhancements to Visualizations:
Visual cue for sort state in Table visual
New visual: Stacked Area chart
Smart tooltips for Area and Line charts on hover
Ability to create reference line/region for a Cartesian visual
Improved data labels for Pie and Scatter charts
R Visuals integration in Power BI Desktop (Preview feature)
Suggested table-to-table relationships when trying to create visuals involving two tables which are not
related
Data Modeling:
Relationships View
Zooming slider
Fit Zoom to screen
Reset layout
Ability to zoom in CTRL+(mouse selection range)
Data Connectivity:
SSAS Multidimensional support - hierarchies support
Stripe Connector
Smartsheet Connector
Enter Data: paste or enter data to create a table
DirectQuery improvements: support for all data types of T-SQL and SAP HANA, resulting in performance
improvements
ODBC Connector: support for selecting User/System DSNs
CSV Connector: ability to specify Column Delimiter in the Source dialog
Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features.
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/iW5VH8iIyfE

November 2015 Update (2.29.4217.221)

You can now download the latest version of Power BI Desktop.
Another month, another big collection of new features and improvements for Power BI Desktop. Improvements
range from new data connectors to new modeling capabilities. Here are 26 new features and improvements:
Report Authoring:
Play Axis for Scatter Chart
Horizontal Slicers
Slicer Selection Behaviors (single vs. multi-select)
Control Z -order
Background Colors for Slides
Interactions between Visuals - Subview (tile by)
Duplicate Pages
Support for KPIs and Images in Tables, Matrices and Cards
Better Tooltips on Area Charts & Line Charts
Ability to change Text size in Cards & Tables/Matrix
Improved tooltips and labels in Field Well and Formatting panes
Ability to see Categories with no data
Improved Default Sort behaviors for visuals
Ability to control Axis Scale display units
Visuals Refresh Optimizations when applying basic modeling operations
Data Modeling:
Basic Automatic Date Features
Data Connectivity:
 SSAS Multidimensional support
SAP Hana
R Script
DirectQuery for SQL Server, Azure SQL Database and Azure SQL Data Warehouse
Azure Data Lake
Marketo
Data Transformations:
Improved Function Invocation experience
Option to set Credentials at Server vs. Database level
Add Prefix/Suffix to a Text column
Other Improvements:
New Documentation Website, now also including localized content
Want more information about these updates? Take a look at the blog post, where you can get more detailed
information about each of these new features.
The following video describes and shows each of these updates. You can also see the video from the blog post.
https://www.youtube.com/embed/ErHvpkyQjSg

October 2015 Update (2.28.4190.122)

October brings another large collection of updates to Power BI Desktop:
Report Authoring:
Custom Visualizations
Insert Visual from the Ribbon
Improved Default Sorting
Tooltips & Data Labels on Funnel Charts
Slicer Improvements:
Ability to Sort items
Ability to change Font Size
Additional Formatting Options for Gauges
Data Point Label layout improvements
KPI Consumption (Preview Feature)
Data Modeling:
Semi-Select support for DAX formulas in Data view
Data Connectivity:
Azure Document DB connector
Mailchimp connector
DirectQuery for SQL Server and Azure SQL Database (Preview Feature)
Data Transformations:
Filter by "not earliest/latest date"
Filter by "is in previous N minutes/hours/seconds"
Copy/Paste Queries between Power BI Desktop and Excel
Support for Special Characters in Split Column
Refresh Previews in Merge Queries dialog
 Monospaced font for Query Editor Preview
Other Improvements:
Refresh Single Table (vs. All) from Report & Data Views
Option to enable Preview features
In-Product Ratings experience
You can view a video of all these updates, too.
https://www.youtube.com/embed/Jbocn1ZNkxM
For more information, check out the blog announcement that describes more details about each update.

September 2015 Update (2.27.4163.351)

The following massive collection of 44 features has been added to this update:
Report Authoring
Report-level filters
Drill Up/Down for column and scatter charts
New Page Size and Page View options
Support for inserting Shapes in the Report canvas
Fields pane improvements
Search Box to make it easier to find fields by name
"Expand/Collapse All" to improve navigation when there are multiple tables in the Fields pane
Field well cardinality support, drag-replace for buckets with 1 item
Additional Data Labels formatting options
Chart Cartesian Axis Improvements:
X-Axis label direction (horizontal / diagonal)
Support for Logarithmic & Linear scales for values in Y -axis
Display Text for hyperlinks in text boxes
Improvements to existing visualizations: Table, Matrix, Slicer, Scatter Chart, Single Cards, Combo
Charts and Gauges
Support for displaying Color Saturation values in tooltips
Ability to resize images and apply additional formatting options
Data Modeling
Calculated Tables.
Relationships view:
Create relationships via drag/drop between two tables in the diagram.
Delete relationships in relationship view by selecting and hitting the Delete key.
Rename/delete tables and columns
Data view:
Copy Table contents to clipboard.
Field Summarization:
Support for additional operations in the Fields pane: median, standard deviation, and variance
Default summarization: Users can now customize the default summarization operation for any given
field in their model
Data Connectivity
Support for on-premises Spark distributions
 Support for SharePoint lists from non-English sites
Exchange connector - Enhanced support, now allowing connections to multiple mailboxes
Excel Workbook Connector - Automatic Column Type detection when importing .XLS files
"Select Related Tables" option when connecting to database sources
Enhanced Active Directory connector credentials, allowing alternate Windows Credentials
Improved Function Invocation experience when loading functions from a data source (such as a database)
"Import Excel Workbook Contents" feature released last month now also supports external connections to
Analysis Services tabular models
New option to "Delete All" entries in the Data Source Settings dialog
Option to "Enable Relationship Import during Refresh operations"
Data Transformations and Query Editor Improvements
Copy to clipboard (available for cells/columns/tables)
Filter date columns by earliest/latest date (dynamic filter)
Extract min/max date/time value from a column
Replace Values - Provision for specifying special characters
"Detect Column Types" option to trigger type detection on demand
"Refresh All Previews" to refresh all Query Editor previews with a single click
Performance Improvements:
Choose Columns dialog: Faster user experience for dealing with wide tables
Auto-filter & Expand/Aggregate popups: Faster for large number of values/fields
The following video covers these features in more detail.
https://www.youtube.com/embed/Jm44dLXdarQ
For more information about this update, check out the blog announcement that describes more details about each
update.

August 2015 Update (2.26.4128.403)

The following features have been added to this update:
Overall Improvements:
Import Excel Power BI artifacts (Data Model, Queries, Power View ) into a new Power BI Desktop file
HDInsight Spark connector
Azure SQL Data Warehouse connector
Support for custom MDX/DAQ queries when importing data from SSAS
Live Analysis Services Connections: ability to change the database from Edit Queries dialog
Navigator dialog improvements:
Resizable Navigator dialog
Ability to multi-select items in Navigator (CTRL+click, SHIFT+click, etc.)
Query Editor improvements:
Query Group creation/deletion improvements (multi-select, etc.)
Ability to Split Query (i.e., refactor common base steps into a new query)
Query Icons to reflect type of query in Queries navigator pane
Data Modeling improvements:
Resizing of columns in Data View
Moving Measures from one table to another
Take a look at the following video for more details about this update:
https://www.youtube.com/embed/2v7LUD7MJaw

July 2015 Update (2.25.4095.554)

The following features have been added in this update:
New Data Connectors: appFigures, Quickbooks Online, Zendesk, GitHub, Twilio, and SweetIQ.
New Transformations: Extract First/Last/Range of characters from a Text Column; Option to specify Join
Type in the Merge Queries dialog; Ability to customize Quote Style in Split Column by Delimiter dialog.
Report Authoring Improvements: New visualizations (Area Chart, Waterfall, Donut & Matrix); New visual
formatting and customization options (labels, titles, background, legend, colors, etc.); Insert Textbox and
Picture in your report; Support for hyperlinks in reports and report tables; Undo/Redo actions.
Direct Report Exploration over Analysis Services Tabular Models.
Data Modeling: New Data View & Relationships views.
Publish reports to PowerBI.com, directly from Power BI Desktop.
Support for opening Recent Files in Start Page and "File -> Open" menu.
Support for Exchange UPN Credentials in the Exchange connector.
In addition to all these new features, we're also making Power BI Desktop available in 42 different languages.
Get the full list of languages and install the one you want from our official download page.
Take a look at the following video for more details:
https://www.youtube.com/embed/JCaCcdMnsyM

May 2015 Update (2.23.4036.161)

The following features have been added in this update:
Modeling Features
Calculated Columns
Data Categorization
Sort By Another Column
Improved DAX Formula Editor: Function Help and Prototype
Get Data & Query
New ODBC Tables connector (Beta)
Improved to the Excel Workbook connector: better column type inference and faster load for data
previews
New Text Column Filters - Does Not Begin With and Does Not End With
 Enhanced Privacy Levels dialog
Take a look at the following video for details:
https://www.youtube.com/embed/LS0zMfup1pQ

April 2015 Update (2.22.4009.122)

You can now download the latest version of Power BI Desktop.
The following features have been added in this update:
Modeling Features
Initial support for DAX Measures
New DAX functions
Data Types & Formatting options in Report view
Rename & Delete fields in Report view
Get Data & Query
OData V4 support
Support for Custom ADFS Authentication Services
Updated Facebook connector due to Facebook API changes
Unified Options dialog
Option to disable Native Database query prompts
Support for Fixed Decimal Number type
Alternate Windows Credentials
Remove Blank Rows
Median Operation available for Group By and Aggregate Column
Convert DateTimeZone value to Local Time
Performance Improvements
Faster load of medium & large datasets by about 20%
Improved time to open an existing PBIX file by about 50%
You can watch the following video for details:
https://www.youtube.com/embed/FuL8agVKrcg

March 2015 Update (2.21.3975.261)

The following features have been added in this update:
Google Analytics connector
Additional operators for date filtering in Query view
Automatic Model Relationship Detection
 Enhanced Add Relationship dialog
Report Pages Re-ordering (drag & drop)
~40-50% Performance Improvement filling database tables without filters/transforms
Lots of bug fixes
You can watch the following video for more details:
https://www.youtube.com/embed/xJTcGro08TI

February 2015 Update (2.20.3945.102)

The following features have been added or improved in this update:
Performance improvements
Dynamics CRM Online connector

NOTE
Currently, only URLs within the crm.microsoft.com domain are accepted by this dialog. This does not include non-
production tenants. We'll fix this issue in our March update. The temporary workaround is to connect to this feed
using "From OData".*

Navigator Dialog improvements

Better preview experience for multi-dimensional sources (Analysis Services and SAP BusinessObjects)
Show Selected Items option
Improved Search capabilities in the Navigator tree
New Transformations
Age and Subtract operations for Date/Time columns
Aggregate Columns: Option to disable new columns' prefix
Field List improvements
Expand/Collapse tables
Hide/Unhide fields
Optimized layout (spacing, margins, and fonts)
Report Pages Navigation - Key boarding support
Lots of bug fixes
https://www.youtube.com/embed/-bZFeS1S1wU
January 2015 Update (2.19.3923.101)
This month we've made a number of improvements and bug fixes under the covers. Please try out the new version
and continue to send us feedback if you find any issues!
 Power BI Desktop Send a Smile Privacy Statement
1/14/2019 • 3 minutes to read • Edit Online

Beginning with the March 2018 version of Power BI Desktop, error reporting uses the Windows Error Reporting
platform rather than the Send a Smile or Send a Frown functionality. You can get more information about the
Windows Error Reporting platform in the Windows Privacy blog.

For versions of Power BI Desktop prior to March 2018

At Microsoft, we are working hard to protect your privacy, while delivering products that bring you the
performance, power, and convenience you want. This Privacy Statement explains many of the data collection and
use practices of Microsoft Power BI Desktop Feedback Send a Smile. It doesn’t apply to other online or offline
Microsoft sites, products, or services.
Except as otherwise described in this statement, Send a Smile doesn’t send personal information to Microsoft.
Information that is sent to Microsoft isn’t shared outside of Microsoft and its controlled subsidiaries and affiliates
without your permission.
Send a Smile to Power BI Desktop allows you to send an email address with your feedback. This email address is
used to contact you if Microsoft needs further information or clarification on your request. You don’t have to
register your email address with Microsoft to use Send a Smile.
Send a Smile to Power BI Desktop allows you to send feedback to Microsoft and, if you want, include screenshots
showing the specific compliment or concern you have. Although Send a Smile doesn’t intentionally collect
personally identifiable information, it is possible that such information might be captured in the feedback or
screenshots you provide. Microsoft doesn’t use this information to identify you.
Send a Smile automatically collects some information about your system configuration, standard computer
information, and basic information about how you use Microsoft products. This information is sent when you
choose to send feedback.
Send a Smile generally collects information about:
System configuration, such as the operating system version and architecture that you use (32-bit vs. 64-bit).
Standard computer information, such as the Power BI Desktop, Internet Explorer version and CLR version that
you are using.
Power BI Desktop program usage, such as File Package Info (Document Locale, Fast Combine
Enabled/Disabled state), Enabled and Disabled Preview Features, DirectQuery vs. Import mode, current
Working Set and Peak Virtual Memory used in the current session.
The personal information we collect from you is used by Microsoft and its controlled subsidiaries and affiliates to
provide the services or carry out the transactions you requested or authorized, and it might also be used to request
additional information on:
Feedback you provide about the product or service you are using
To provide critical updates and notifications regarding the software
To improve the product or service, for example, bug and survey form inquiries
Except as described in this statement, personal information you provide isn’t transferred to third parties without
your consent. We occasionally hire other companies to provide limited services on our behalf, such as:
Packaging, sending and delivering purchases, and other mailings
 Answering customer questions about products or services
Processing event registration
Performing statistical analysis of our services
We only provide those companies with the personal information they need to deliver the service, and they are
prohibited from using that information for any other purpose.
Microsoft might access or disclose information about you, including the content of your communications, to:
Comply with the law or respond to lawful requests or legal process
Protect the rights or property of Microsoft or our customers, including the enforcement of our agreements or
policies governing your use of the services
Act on a good faith belief that such access or disclosure is necessary to protect the personal safety of Microsoft
employees, customers, or the public
Information collected by or sent to Microsoft by Send a Smile might be stored and processed in the United States
or any other country in which Microsoft or its affiliates, subsidiaries, or service providers maintain facilities.
Microsoft abides by the Safe Harbor Framework as set forth by the United States Department of Commerce
regarding the collection, use, and retention of data from the European Union.

Security of your information

Microsoft is committed to helping protect the security of your personal information. We use a variety of security
technologies and procedures to help protect your personal information from unauthorized access, use, or
disclosure.

Changes to this Privacy Statement

Microsoft might occasionally update this Privacy Statement. The last updated date at the top of the Privacy
Statement is updated with every revision. We encourage you to periodically review this Privacy Statement to be
informed of how Microsoft is helping to protect your information.
 Accessibility in Power BI Desktop reports
3/20/2019 • 8 minutes to read • Edit Online

Power BI has features that enable people with disabilities to more easily consume and interact with Power BI
reports. These features include the ability to consume a report using the keyboard or a screen reader, tabbing to
focus on various objects on a page, and thoughtful use of markers in visualizations.

Consuming a Power BI Desktop report with a keyboard or screen

reader
Beginning with the September 2017 release of Power BI Desktop, you can press the ? key to show a window
that describes the accessibility keyboard shortcuts available in Power BI Desktop.
With the accessibility enhancements, you can consume a Power BI report with a keyboard or a screen reader
with the following techniques:
When viewing a report, generally you should have scan mode off.
You can switch focus between the report page tabs, or objects on a given report page, using Ctrl+F6.
When focus is on report page tabs, use the Tab or Arrow keys to move focus from one report page to the
next. The title of the report page, and whether it's currently selected, is read out by the screen reader. To load
the report page currently under focus, use the Enter or Space key.
When focus is on a loaded report page, use the Tab key to shift focus to each object on the page, which
includes all textboxes, images, shapes, and charts. The screen reader reads the type of object, the object's title
(if it has one), and a description of that object if it's provided by the report author.

As you navigate between visuals you can press Alt+Shift+F10 to move focus to the visual header, which
contains various options including sorting, exporting the data behind the chart, and Focus mode.
You can press Alt+Shift+F11 to present an accessible version of the Show data window. This lets you explore
the data used in the visual in an HTML table, using the same keyboard shortcuts you normally use with your
screen reader.

NOTE
The Show data feature is only accessible to a screen reader through this keyboard shortcut. If you open Show data
through the option in the visual header, it will not be accessible to a screen reader. When using Show data, turn on scan
mode to take advantage of all the hot keys your screen reader provides.

Beginning with the July 2018 release of Power BI Desktop, slicers also have accessibility functionality built in.
When you select a slicer, to adjust the value of a slicer use CTRL+right arrow (control plus the right arrow key)
to move through the various controls within the slicer. For example, when you initially press CTRL+right arrow
the focus is on the eraser, and pressing the SPACE bar is equivalent to clicking the eraser button, which erases
all values on the slicer.
You can move through the controls in a slicer by pressing the TAB key. Pressing the TAB key when on the eraser
moves to the drop-down button. Another TAB then moves to the first slicer value (if there are multiple values
for the slicer, such as a range).

These accessibility additions were created to let users fully consume Power BI reports using a screen reader and
keyboard navigation.

Tips for creating accessible reports

The following tips can help you create Power BI Desktop reports that are more accessible.
General tips for accessible reports
For Line, Area, and Combo visuals, as well as for Scatter and Bubble visuals, turn markers on, and use
a different Marker shape for each line.
To turn Markers on, select the Format section in the Visualizations pane, expand the Shapes
section, then scroll down to find the Markers toggle and turn it to On.
Then, select the name of each line (or area, if using an Area chart) from the drop-down box in that
Shapes section. Below the drop-down, you can then adjust many aspects of the marker used for the
selected line, including its shape, color, and size.

Using a different Marker shape for each line makes it easier for report consumers to differentiate
lines (or areas) from each other.
As a follow on to the previous bullet, don't rely on color to convey information. In addition to using
shapes on line and scatter charts, don't rely on conditional formatting to provide insights in tables and
matrices.
Pick an intentional sort order for each visual on your report. When screen reader users navigate the data
behind the chart, it picks up the same sort order as the visual.
Select a theme that is high contrast and color blind friendly from the theme gallery, and import it using
the Theming preview feature.
For every object on a report, provide Alt Text. Doing so ensures that consumers of your report
understand what you are trying to communicate with a visual, even if they cannot see the visual, image,
shape, or textbox. You can provide Alt Text for any object on a Power BI Desktop report by selecting the
object (such as a visual, shape, and so on) and in the Visualizations pane, select the Format section,
expand General, scroll to the bottom, and fill in the Alt Text textbox.

Make sure your reports have sufficient contrast between text and any background colors. There are
several tools such as Color Contrast Analyser you can use to check your report colors.
Use text sizes and fonts that are easily readable. Small text size, or fonts that might be difficult to read,
are unhelpful for accessibility.
Include a title, axis labels, and data labels in all visuals.
 Use meaningful titles for all report pages.
Avoid decorative shapes and images in your report if possible, as they are included in the tab order of
the report. If you need to include decorative objects in your report, update the object's alt text to let
screen reader users know that it is for decoration.
Arranging items in Field buckets
Beginning with the October 2018 release of Power BI Desktop, the Fields well can be navigated with a
keyboard and interacts with screen readers.
To improve the process of creating reports with screen readers, a context menu is available to allow moving
fields in the well up or down in the Fields list, or moving the field to other wells, such as Legend or Value or
others.

High contrast support for reports

When you use high contrast modes in Windows, those settings and the palette you select are also applied to
reports in Power BI Desktop.
Power BI Desktop automatically detects which high contrast theme is being used in Windows, and applies
those settings to your reports. Those high contrast colors follow the report when published to the Power BI
service, or elsewhere.
The Power BI service also attempts to detect the high contrast settings selected for Windows, but how effective
and accurate that detection is depends on the browser being used for the Power BI service. If you want to set
the theme manually in the Power BI service, you can select View > High contrast colors and then select the
theme you would like to apply to the report.

When in Power BI Desktop, notice that some areas such as the Visualizations and Fields fields do not reflect
the selection of high contrast Windows color schemes.

Considerations and limitations

There are a few known issues and limitations with the accessibility features, described in the following list:
When using screen readers with Power BI Desktop, you'll have the best experience if you open your screen
reader of choice prior to opening any files in Power BI Desktop.
If you are using Narrator, there are some limitations around navigating Show data as an HTML table.

Keyboard Shortcuts
Keyboard shortcuts are helpful for moving around in Power BI reports using a keyboard. The following tables
describe the shortcuts available in a Power BI report. In addition to using these keyboard shortcuts in Power BI
Desktop, these shortcuts work in the following experiences as well:
Q&A Explorer dialog
Getting Started dialog
File menu and About dialog
Warning bar
File Restore dialog
Frowns dialog
In our continued effort to improve accessibility, the previous list of experiences also support screen readers and
high contrast settings.
Frequently used shortcuts
TO DO THIS PRESS

Move focus between sections Ctrl + F6

Move focus forward in section Tab

Move focus backward in section Shift + Tab

Select or de-select an object Enter or Space

Multi-select objects Ctrl + Space

On visual
TO DO THIS PRESS

Move focus to visual menu Alt + Shift + F10

Show data Alt + Shift +F11

Enter a visual Ctrl + Right arrow

Enter a layer Enter

Exit a layer or visual Esc

Select or unselect data point Enter or Space

Multi-select Ctrl + Enter or Ctrl + Space

Right click Windows keyboard: Windows context key + F10. The

Windows context key is between the Left Alt key and
the Left Arrow Key
Other keyboard: Shift + F10

Clear selection Ctrl + Shift + C

Pane Navigation
 TO DO THIS PRESS

Multi-select Ctrl + Space

Collapse a single table Left arrow key

Expand a single table Right arrow key

Collapse all tables Alt + Shift + 1

Expand all tables Alt + Shift + 9

Open a context menu Windows keyboard: Windows context key + F10. The
Windows context key is between the Left Alt key and
the Left Arrow Key
Other keyboard: Shift + F10

Slicer
TO DO THIS PRESS

Interact with a slicer Ctrl + Right arrow key

Selection Pane
TO DO THIS PRESS

Activate selection pane F6

Move an object up in the layering Ctrl + Shift + F

Move an object down in the layering Ctrl + Shift + B

Hide / show (toggle) an object Ctrl + Shift + S

DAX Editor
TO DO THIS PRESS

Move line up / down Alt + Up arrow key / Down arrow key

Copy line up / down Shift + Alt + Up arrow key / Down arrow key

Insert line below Ctrl + Enter

Insert line above Ctrl + Shift + Enter

Jump to matching bracket Ctrl + Shift + \

Indent / outdent line Ctrl + ] / [

Insert cursor Alt + Click

 TO DO THIS PRESS

Select current line Ctrl + I

Select all occurrences of current selection Ctrl + Shift + L

Select all occurrences of current word Ctrl + F2

Enter Data
TO DO THIS PRESS

Exit editable grid Ctrl + Tab

Next steps
Use Report Themes in Power BI Desktop (Preview )
 How administrators can manage the Power BI
Desktop sign-in form
2/26/2019 • 2 minutes to read • Edit Online

The first time Power BI Desktop is launched, a sign-in form is displayed. Information can be filled in, or sign in to
Power BI to continue. Administrators manage this form by using a registry key.

Administrators use the following registry key to disable the sign-in form. This can also be pushed to an entire
organization by using global policies.

Key: HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Microsoft Power BI Desktop

valueName: ShowLeadGenDialog

A value of 0 will disable the dialog.

More questions? Try asking the Power BI Community
 What is Power BI?
2/8/2019 • 3 minutes to read • Edit Online

Power BI is a collection of software services, apps, and connectors that work together to turn your unrelated
sources of data into coherent, visually immersive, and interactive insights. Your data may be an Excel
spreadsheet, or a collection of cloud-based and on-premises hybrid data warehouses. Power BI lets you easily
connect to your data sources, visualize and discover what’s important, and share that with anyone or everyone
you want.

Power BI can be simple and fast – capable of creating quick insights from an Excel spreadsheet or a local
database. But Power BI is also robust and enterprise-grade, ready for extensive modeling and real-time
analytics, as well as custom development. So it can be your personal report and visualization tool. It can also
serve as the analytics and decision engine for group projects, divisions, or entire corporations.

The parts of Power BI

Power BI consists of a Windows desktop application called Power BI Desktop, an online SaaS (Software as a
Service) service called the Power BI service, and Power BI mobile apps for Windows, iOS, and Android
devices.

These three elements – Power BI Desktop, the service, and mobile apps – are designed to let people create,
share, and consume business insights in the way that serves them, or their role, most effectively.
A fourth element, Power BI Report Server, allows you to publish Power BI reports to an on-premises report
server, after creating them in Power BI Desktop. Read more about Power BI Report Server.
How Power BI matches your role
How you use Power BI may depend on your role in a project or on a team. And other people, in other roles,
might use Power BI differently, which is fine.
For example, you might primarily use the Power BI service. But your number-crunching, business-report-
creating coworker might make extensive use of Power BI Desktop to create reports, then publish those
reports to the Power BI service, where you can view them. Another coworker, in sales, might mainly use her
Power BI phone app to monitor progress on her sales quotas, and to drill into new sales lead details.
If you're a developer, you might use Power BI APIs to push data into datasets or to embed dashboards and
reports into your own custom applications. Have an idea for a new visual? Build it yourself and share it with
others.
You also might use each element of Power BI at different times, depending on what you’re trying to achieve
or your role for a given project.
Perhaps you use Power BI Desktop to create reports for your own team about customer engagement
statistics. Perhaps you also view inventory and manufacturing progress in a real-time dashboard in the
service. How you use Power BI can be based on which feature or service of Power BI is the best tool for your
situation. Each part of Power BI is available to you, which is why it’s so flexible and compelling.
Explore documents that pertain to your role:
Power BI for designers
Power BI for consumers
Power BI for developers
Power BI for administrators

The flow of work in Power BI

A common flow of work in Power BI begins by connecting to data sources and building a report in Power BI
Desktop. You then publish that report from Power BI Desktop to the Power BI service, and share it so end
users in the service and mobile devices can view and interact with the report. This workflow is common, and
shows how the three main Power BI elements complement one another.
Here's a detailed comparison of Power BI Desktop and the Power BI service.
But what if you're not ready to move to the cloud, and want to keep your reports behind a corporate firewall?
Read on.

On-premises reporting with Power BI Report Server

Create, deploy, and manage Power BI, mobile and paginated reports on premises with the range of ready-to-
use tools and services that Power BI Report Server provides.
Power BI Report Server is a solution that you deploy behind your firewall and then deliver your reports to the
right users in different ways, whether that’s viewing them in a web browser, on a mobile device, or as an email.
And because Power BI Report Server is compatible with Power BI in the cloud, you can move to the cloud
when you're ready.
Read more about Power BI Report Server.

Next steps
Sign in, get some data, and learn your way around Power BI service
Tutorial: Get started with the Power BI service Quickstart: Connect to data in Power BI Desktop
 Comparing Power BI Desktop and the Power BI
service
1/14/2019 • 2 minutes to read • Edit Online

In a Venn diagram comparing Power BI Desktop and the Power BI service, the area in the middle would show how
the two overlap. Some tasks you can do in either Power BI Desktop or the service. But on the two sides of the Venn
diagram, the application and the service each have unique features.

Power BI Desktop is a complete data analysis and report creation tool. When you install the free application on
your local computer, you can connect to many different sources of data, and combine them (often called modeling)
into a data model. The Power BI Desktop getting started guide walks through the process.
The Power BI service is a cloud-based, online service for light report editing and collaboration for teams and
corporations. You can connect to data sources in the Power BI service, too, but modeling is limited.
Most report designers who work on business intelligence projects use Power BI Desktop to create reports, and
then use the Power BI service to share their reports with others.

Report editing
In both the application and the service, you can build and edit reports. A report can have one or many pages, with
visuals and collections of visuals. You can add bookmarks, buttons, filters, and drillthrough, to enhance navigation
in your reports.
The report editors in Power BI Desktop and in the service are similar. They're made up of three sections:
1. The top navigation bars, different in Power BI Desktop and the service
2. The report canvas
3. The Fields, Visualizations, and Filters panes
This video shows the report editor in Power BI Desktop.
https://www.youtube.com/embed/IkJda4O7oGs

Collaborating in the Power BI service

After you've created your reports, you can save them to a workspace in the Power BI service, where you and your
colleagues collaborate. You build dashboards on top of those reports. Then you share those dashboards and
reports with report consumers inside and outside your organization. Your report consumers view them in the
Power BI service in Reading view, not Editing view. They don't have access all the features available to report
creators.

Next steps
What is Power BI Desktop?
Create a report in the Power BI service
Basic concepts for report designers
More questions? Try the Power BI Community
 Tutorial: Get started with the Power BI service
(app.powerbi.com)
1/28/2019 • 6 minutes to read • Edit Online

This tutorial helps you get started with the Power BI service. For an understanding of how the Power BI
service fits in with the other Power BI offerings, we highly recommend that you start by reading What is
Power BI.

In this tutorial, you complete the following steps:

Find other getting started content for the Power BI service
Sign in to your Power BI online account, or sign up, if you don't have one yet
Open the Power BI service
Get some data and open it in report view
Use that data to create visualizations and save as a report
Create a dashboard by pinning tiles from the report
Add another visualization to your dashboard using the Q&A natural language tool
Clean up resources by deleting the dataset, report, and dashboard

Sign up for the Power BI service

If you're not signed up for Power BI, sign up for a free Power BI Pro trial before you begin.
If you already have an account, open a browser and type app.powerbi.com to open the Power BI service.

If you're looking for help with Power BI Desktop, see Get started with Power BI Desktop. If you're looking for
help with Power BI mobile, see Power BI apps for mobile devices.
 TIP
Prefer a free self-paced training course instead? Enroll in our Analyzing and Visualizing Data course on EdX.

Visit our playlist on YouTube. A good video to start with is Introduction to the Power BI service:

https://www.youtube.com/embed/B2vd4MQrz4M

What is the Power BI service?

The Microsoft Power BI service is sometimes referred to as Power BI online or app.powerbi.com. Power BI
helps you stay up-to-date with the information that matters to you. With the Power BI service, dashboards
help you keep a finger on the pulse of your business. Your dashboards display tiles that you can click to open
reports for exploring further. Connect to multiple datasets to bring all of the relevant data together in one
place. Need help understanding the building blocks that make up Power BI? See Power BI - Basic Concepts.
If you have important data in Excel or CSV files, you can create a Power BI dashboard to stay informed
anywhere and share insights with others. Do you have a subscription to a SaaS application like Salesforce?
Get a head start by connecting to Salesforce to automatically create a dashboard from that data, or check out
all the other SaaS apps you can connect to. If you are part of an organization, see if any apps have been
published for you.
Read about all the other ways to get data for Power BI.

Step 1: Get data

Here's an example of getting data from a CSV file. Want to follow along with this tutorial? Download this
sample CSV file.
1. Sign in to Power BI. Don’t have an account? No worries, you can sign up for a free trial.
2. Power BI opens in your browser. Select Get Data at the bottom of the left navigation bar.

3. Select Files.

4. Browse to the file on your computer, and choose Open. If you saved it in OneDrive for Business, select
that option. If you saved it locally, select Local file.
5. For this tutorial, we're going to select Import to add the Excel file as a dataset that we can then use to
create reports and dashboards. If you select Upload, the entire Excel workbook is uploaded to Power
BI where you can open and edit it in Excel online.

6. When your dataset is ready, select View dataset to open it in the report editor.

Since we haven't yet created any visualizations, the report canvas will be blank.
7. Take a look at the top menubar and notice that there is an option for Reading view. Since you have an
option for Reading view, that means you are currently in Editing view.

While in Editing view you can create and modify your reports, because you are the owner of the
report; you are a creator. When you share your report with colleagues, they'll only be able to interact
with the report in Reading view; they are consumers. Learn more about Reading view and Editing view.
A great way to get familiar with the report editor is to take a tour

Step 2: Start exploring your dataset

Now that you've connected to data, start exploring. When you've found something interesting, you can create
a dashboard to monitor it and see how it changes over time. Let's see how that works.
1. In the report editor, we'll use the Fields pane on the right side of the page to build a visualization.
Select the checkbox beside Gross Sales and Date.
2. Power BI analyzes the data and creates a visualization. If you selected Date first, you'll see a table. If
you selected Gross Sales first, you'll see a chart. Switch to a different way of displaying your data.
Let's see this data as a line chart. Select the line chart icon (also known as a template) from the
Visualizations pane.

3. This chart looks interesting, so let's pin it to a dashboard. Hover over the visualization and select the
Pin icon. When you pin this visualization, it is stored on your dashboard and kept up-to-date so you
can track the latest value at a glance.
4. Because this report is new, you'll be prompted to save it before you can pin a visualization to a
dashboard. Give your report a name (for example, Sales over time) and select Save and Continue.

5. Let's pin the line chart to new dashboard and name it "Financial sample for tutorial".

6. Select Pin.
A Success message (near the top-right corner) lets you know the visualization was added, as a tile, to
your dashboard.

7. Select Go to dashboard to see the line chart pinned, as a tile, to your brand new dashboard. Make
your dashboard even better by adding more visualization tiles and renaming, resizing, linking, and
repositioning tiles.

Select the new tile on your dashboard to return to the report anytime. Power BI returns you to the
report editor in Reading view. To switch back to Editing view, select Edit report from the top menubar.
Once in Editing view, continue exploring and pinning tiles.
Step 3: Continue the exploration with Q&A (natural language
querying)
1. For a quick exploration of your data, try asking a question in the Q&A box. The Q&A question box is
located at the top of your dashboard (Ask a question about your data) and in the top menubar in
your report (Ask a question). For example, try typing "what segment had the most revenue".

2. Q&A searches for an answer and presents it in the form of a visualization. Select the pin icon to
show this visualization on your dashboard too.
3. Pin the visualization to the "Financial Sample for tutorial" dashboard.

4. Return to your dashboard where you'll see the new tile.

Clean up resources
Now that you've finished the tutorial, you can delete the dataset, report, and dashboard.
1. In the left navigation bar, select My Workspace.
2. Select the Datasets tab and locate the dataset you imported for this tutorial.
3. Select the ellipses (...) > Delete.

Deleting the dataset will also delete the report and the dashboard.

Next steps
Ready to try more? Here are some great ways to explore Power BI.
Connect to the online services you use
 Tutorial: Connect to a GitHub sample with Power BI
2/13/2019 • 2 minutes to read • Edit Online

In this tutorial, you connect to real data in the GitHub service with Power BI, and Power BI automatically creates
dashboards and reports. You connect to the Power BI content public repository (also known as a repo) and see
information: How many people contribute to the Power BI public content? Who contributes the most? Which day of
the week has the most contributions? And answers to other questions.

In this tutorial, you complete the following steps:

Sign up for a GitHub account, if you don't have one yet
Sign in to your Power BI account, or sign up, if you don't have one yet
Open the Power BI service
Find the GitHub app
Enter the information for the Power BI public GitHub repo
View the dashboard and report with GitHub data
Clean up resources by deleting the app
If you're not signed up for Power BI, sign up for a free trial before you begin.

Prerequisites
To complete this tutorial, you need a GitHub account, if you don't already have one.
Sign up for a GitHub account

How to connect
1. Sign in to the Power BI service ( http://powerbi.com).
2. In the left navigation pane, select Apps, then Get apps.
3. Select Apps, type github in the search box > Get it now.

4. Enter the repository name and repository owner of the repo. The URL for this repo is
https://github.com/MicrosoftDocs/powerbi-docs, so Repository Owner is MicrosoftDocs, and
Repository is powerbi-docs.
 5. Enter the GitHub credentials you created. Power BI might skip this step if you're already signed in to GitHub
in your browser.
6. For Authentication Method, select oAuth2 > Sign In.
7. Follow the Github authentication screens. Grant Power BI permission to the GitHub data.
Now Power BI can connect with GitHub and connect to the data. The data is refreshed once a day.
8. After Power BI imports the data, you see the new GitHub tile.

9. Select the global navigation icon to minimize the left navigation, so you have more room.

10. Select the GitHub tile from step 8.

The GitHub dashboard opens. This is live data, so the values you see may be different.
 Ask a question
11. Put your cursor in Ask a question about your data, then select pull requests.

12. Type by month.

 Power BI creates a bar chart showing the number of pull requests per month.
13. Select Exit Q&A.

View the GitHub report

1. In the GitHub dashboard, select the combo column-and-line chart Pull Requests by Month to open the
related report.

2. Select a user name in the Total pull requests by user chart, and see, as in this example, that they had more
average hours than the total average for March.
3. Select the Punch Card tab to view the next page in the report.

Apparently Tuesdays at 3 pm is the most common time and day of the week for commits, when people
check in their work.

Clean up resources
Now that you've finished the tutorial, you can delete the GitHub app.
1. In the left navigation bar, select Apps.
2. Hover over the GitHub tile and select the Delete garbage can.
Next steps
In this tutorial, you've connected to a GitHub public repo and gotten data, which Power BI has formatted in a
dashboard and report. You've answered some questions about the data by exploring the dashboard and report.
Now you can learn more about connecting to other services, such as Salesforce, Microsoft Dynamics, and Google
Analytics.
Connect to the online services you use
 Tutorial: Use Cognitive Services in Power BI
3/13/2019 • 5 minutes to read • Edit Online

Power BI provides access to a set of functions from Azure Cognitive Services to enrich your data in the self-service
data prep for Dataflows. The services that are supported today are Sentiment Analysis, Key Phrase Extraction,
Language Detection, and Image Tagging. The transformations are executed on the Power BI service and do not
require an Azure Cognitive Services subscription. This feature requires Power BI Premium.
Cognitive Services transforms are supported in the Self-Service Data Prep for Dataflows. Use the step-by-step
examples for text analytics and image tagging below to get started.
In this tutorial, you learn how to:
Import data into a dataflow
Score sentiment and extract key phrases of a text column in a dataflow
Connect to the results from Power BI Desktop

Prerequisites
To complete this tutorial, you need the following:
A Power BI account. If you're not signed up for Power BI, sign up for a free trial before you begin.
Access to a Power BI Premium capacity with the AI workload enabled. This workload will be turned off by
default during preview. If you are in on a Premium capacity and AI Insights are not showing up, contact your
Premium capacity admin to enable the AI workload in the admin portal.

Text analytics
Follow the steps in this section to complete the text analytics portion of the tutorial.
Step 1: Apply sentiment scoring in Power BI Service
To get started, navigate to a Power BI workspace with Premium capacity and create a new dataflow using the
Create button in the upper right of the screen.

The dataflow dialog shows you the options for creating a new dataflow, select Add new entities. Next, choose
Text/CSV from the menu of data sources.
Paste this URL into the URL field:
https://pbiaitutorials.blob.core.windows.net/textanalytics/FabrikamComments.csv and click Next.

In the upper ribbon, select Transform Table and then choose Use first row as headers. The data is now ready to
use for text analytics, and we can use Sentiment Scoring and Key Phrase Extraction on the customer comments
column.
In Power Query Editor, select AI Insights
Expand the Cognitive Services folder and select the function you would like to use. This example is scoring the
sentiment of the comment column, but you can follow the same steps to try out Language Detection and Key
Phrase Extraction.

Once a function is selected, the required and optional fields will show. To score the sentiment of the example
reviews, select the reviews column as text input. Culture info is an optional input and requires an ISO format. For
example, enter 'en' if you want the text to be treated as English. When the field is left blank, Power BI will first
detect the language of the input value before scoring the sentiment.
Now select Invoke to run the function. A new column with the sentiment score for each row is added to the table.
You can go back to AI insights to extract key phrases of the review text in the same way.
Once you are finished with the transformations, change the query name to 'Customer comments' and select
Done.

Next, Save the dataflow and name it Fabrikam. Select the Refresh Now button that pops up after saving the
dataflow.
Once the dataflow is saved and refreshed, you can use it in a Power BI report.
Step 2: Connect from Power BI Desktop
Open Power BI Desktop. In the Home ribbon, select Get Data.
Navigate to the Power BI dataflows (Beta) in the Power BI section and select Connect.
As this is a preview feature, the connector will ask you to accept the preview conditions. After accepting these, sign
in with your organization account.

Select the dataflow you have just created. Navigate to the Customer comments table and click Load.
Now the data is loaded you can start building a report.

Image tagging
Navigate to a Power BI workspace with Premium capacity. Create a new dataflow using the Create button in the
upper right of the screen.

Select Add new entities.

Once you are asked to choose a data source, select Blank query.

Copy the query below in the query editor and click next. You can replace the URL paths below with other images
or add more rows. The Web.Contents function imports the image URL as binary. If you have a data source with
images stored as binary, you can also use that directly.

let
Source = Table.FromRows({
{ Web.Contents("https://images.pexels.com/photos/87452/flowers-background-butterflies-beautiful-87452.jpeg")
},
{ Web.Contents("https://upload.wikimedia.org/wikipedia/commons/5/53/Colosseum_in_Rome%2C_Italy_-
_April_2007.jpg") }}, { "Image" })
in
Source
When prompted for credentials, select anonymous.

You see the following image.

You're prompted for credentials for each individual web page.
Select AI Insights in the query editor.

Next, sign in with your organizational account.

Select the Tag Images function, enter [Binary ] in the column field and en in the culture info field.

NOTE
You currently cannot pick a column using a dropdown, which will be resolved as soon as possible during the private preview.

In the function editor, remove the quotation marks around the column name.
 NOTE
Removing the quotation marks is a temporary workaround, which will be resolved as soon as possible during preview.

The function returns a record with both the tags in comma-separated format and as a json record. Select the
expand-button to add one or both as columns to the table.

Select Done and save the dataflow. Once you have refreshed the dataflow one, you can connect to it from Power
BI Desktop using the Dataflows connectors. (See steps on page 5 of this document).

Clean up resources
When no longer needed, delete the query by right-clicking the query name in the Power Query editor and
selecting Delete.

Next steps
In this tutorial, you applied sentiment scoring and image tagging functions on a Power BI dataflow. To learn more
about Cognitive Services in Power BI, read the following articles.
Cognitive Services in Azure
Get started with self-service data prep on dataflows
Learn more about Power BI Premium
You might also be interested in the following articles.
Tutorial: Invoke a Machine Learning Studio model in Power BI (Preview )
Azure Machine Learning integration in Power BI (Preview )
Cognitive Services in Power BI (Preview )
 Tutorial: Invoke a Machine Learning Studio model in Power BI
(Preview)
3/25/2019 • 7 minutes to read • Edit Online

In this tutorial, we walk through the experience of incorporating insights from an Azure Machine Learning Studio model into Power BI.
This tutorial includes guidance for granting a Power BI user access to an Azure ML model, creating a dataflow, and applying the insights
from the Azure ML model to your dataflow. It also references the quickstart guide for creating an Azure ML model if you don't already have
a model.
The tutorial takes you through the following steps:
Create and publish an Azure Machine Learning model
Grant access to a Power BI user to use the model
Create a dataflow
Apply insights from the Azure ML model to the dataflow

Create and publish an Azure ML model

Follow the instructions at Walkthrough Step 1: Create a Machine Learning Studio workspace to create a Machine Learning workspace.
You can use these steps with any Azure ML model or dataset you already have. If you don't have a published model, you can create a model
in minutes by referring to Create your first data science experiment in Azure Machine Learning Studio, which sets up an Azure ML model
for Automobile Price Prediction.
Follow the steps at Deploy an Azure Machine Learning Studio web service to publish the Azure ML model as a web service.

Grant a Power BI user access

To access an Azure ML model from Power BI, you must have Read access to the Azure subscription and the resource group and Read
access to the Azure Machine Learning Studio web service for Machine Learning Studio models. For Azure Machine Learning service
model, you need Read access to the Machine Learning service workspace.
The following steps assume you are the coadministrator for the Azure subscription and resource group to which the model was published.
Sign in to the Azure portal, and navigate to the Subscriptions page, which you can find using the All Services list in the left navigation
menu.

Select the Azure subscription that you used for publishing the model, and select Access Control (IAM ). Next select Add role
assignment, then select the Reader role, and select the Power BI user. Select Save when you're done. The following image shows these
selections.

Then repeat the steps above to grant Contributor role access to the Power BI user for the specific Machine Learning web service to which
the Azure ML model has been deployed.

Create a dataflow
Get data for creating the dataflow
Sign in to the Power BI service with the user credentials for whom you granted access to the Azure ML model in the previous step.
This step assumes you have the data you want to score with your Azure ML model in CSV format. If you used the Automobile Pricing
Experiment to create the model in the Machine Learning studio, the dataset for is shared in the following link:
Azure Learning Studio sample model
Create a dataflow
To create the entities in your dataflow, sign in to the Power BI service and navigate to a workspace on your dedicated capacity that has the
AI preview enabled.
If you don't already have a workspace, you can create one by selecting Workspaces in the left menu, and then select Create app
workspace in the panel at the bottom. This opens a panel to enter the workspace details. Enter a workspace name, and then select Save.
After the workspace has been created, you can select Skip in the bottom right of the Welcome screen.

Select the Dataflows (preview) tab, and then select the Create button at the top right of the workspace, and then select Dataflow.
Select Add new entities, which launches Power Query Editor in the browser.

Select Text/CSV File as a data source.

In the next screen, you're prompted to connect to a data source. Paste the link to the data you used to create your Azure ML model. If you
used the Automotive Pricing data, you can paste the following link into the File path or URL box and then Next.
https://raw.githubusercontent.com/santoshc1/PowerBI AI samples/master/Tutorial\_MLStudio\_model\_integration/Automobile%20price%20data%20\_Raw\_.csv

Power Query Editor shows a preview of the data from the CSV file. Select Transform Table from the command ribbon and then select Use
first row as headers. This adds the Promoted headers query step into the Applied steps pane on the right. You can also rename the
query to a friendlier name, such as Automobile Pricing using the pane on the right.
Our source dataset has unknown values set to '?'. To clean this, we can replace '?' with '0' to avoid errors later for simplicity. To do this,
select the columns normalized-losses, bore, stroke, compression-ratio, horsepower, peak-rpm and price by clicking on their name in the
column headers, then click on 'Transform columns' and select 'Replace values'. Replace '?' with '0'.

All the columns in the table from a Text/CSV source are treated as text columns. Next, we need to change the numeric columns to their
correct data types. You can do this in Power Query by clicking on the data type symbol in the column header. Change the columns to the
below types:
Whole number: symboling, normalized-losses, curb-weight, engine-size, horsepower, peak-rpm, city-mpg, highway-mpg, price
Decimal number: wheel-base, length, width, height, bore, stroke, compression-ratio
Select Done to close Power Query Editor. This will show the entities list with the Automobile Pricing data we added. Select Save in the top
right corner, provide a name for the dataflow, and then select Save.

Refresh the dataflow

Saving the dataflow displays a notification that your dataflow was saved. Select Refresh now to ingest data from the source into the
dataflow.
Select Close in the upper right corner and wait for the dataflow refresh to complete.
You can also refresh your dataflow using the Actions commands. The dataflow displays the timestamp when the refresh is completed.

Apply insights from your Azure ML model

To access the Azure ML model for Automobile Price Prediction, you can edit the Automobile Pricing entity for which we want to add the
predicted price.
Selecting the Edit icon opens Power Query Editor for the entities in your dataflow.

Select the AI Insights button in the ribbon, and then select the Azure Machine Learning Models folder from the left navigation menu.
The Azure ML models to which you've been granted access are listed as Power Query functions with a prefix AzureML. When you click on
the function corresponding to the AutomobilePricePrediction model, the parameters for the model's web service are listed as function
parameters.
To invoke an Azure ML model, you can specify any of the selected entity's columns as an input from the drop-down. You can also specify a
constant value to be used as an input by toggling the column icon to the left of the input dialog. When a column name that matches one of
the function parameter names, then the column is automatically suggested as an input. If the column name doesn't match, you can select it
from the drop-down.
In the case of the Automobile Pricing Prediction model, the input parameters are:
make
body-style
wheel-base
engine-size
horsepower
 peak-rpm
highway-mpg
In our case, since our table matches the original dataset used to train the model, all the parameters have the correct columns already
selected.

Select Invoke to view the preview of the Azure ML model's output as a new column in the entity table. You'll also see the model invocation
as an applied step for the query.
The output of the model is shown as a record in the output column. You can expand the column to produce individual output parameters in
separate columns. In our case, we're only interested in the Scored Labels which contains the predicted price of the automobile. So we
deselect the rest, and select OK.

The resulting Scored Labels column has the price prediction from the Azure ML model.
Once you save your dataflow, the Azure ML model will be automatically invoked when the dataflow is refreshed for any new or updated
rows in the entity table.

Clean up resources
If you no longer need the Azure resources you created using this article, delete them to avoid incurring any charges. You can also delete the
dataflows you created, if you no longer require them.

Next steps
In this tutorial, you created a simple experiment using Azure Machine Learning Studio using a simple dataset using these steps:
Create and publish an Azure Machine Learning model
Grant access to a Power BI user to use the model
Create a dataflow
Apply insights from the Azure ML model to the dataflow
For more information about Azure Machine Learning integration in Power BI, see Azure Machine Learning integration in Power BI
(Preview ).
 Tutorial: Build a Machine Learning model in Power BI
(Preview)
3/29/2019 • 9 minutes to read • Edit Online

In this tutorial article, you use Automated Machine Learning to create and apply a binary prediction model in
Power BI. The tutorial includes guidance for creating a Power BI dataflow, and using the entities defined in the
dataflow to train and validate a machine learning model directly in Power BI. We then use that model for scoring to
generate predictions.
First, you'll create a Binary Prediction machine learning model, to predict the purchase intent of online shoppers
based on a set of their online session attributes. A benchmark machine learning dataset is used for this exercise.
Once a model is trained, Power BI will automatically generate a validation report explaining the model results. You
can then review the validation report and apply the model to your data for scoring.
This tutorial consists of following steps:
Create a dataflow with the input data
Create and train a machine learning model
Review the model validation report
Apply the model to a dataflow entity
Using the scored output from the model in a Power BI report

Create a dataflow with the input data

The first part of this tutorial is to create a dataflow with input data. That process takes a few steps, as shown in the
following sections, beginning with getting data.
Get data
The first step in creating a dataflow is to have your data sources ready. In our case, we use a machine learning
dataset from a set of online sessions, some of which culminated in a purchase. The dataset contains a set of
attributes about these sessions, which we'll use for training our model.
You can download the dataset from the UC Irvine website. We also have this available, for the purpose of this
tutorial, from the following link: online_shoppers_intention.csv.
Create the entities
To create the entities in your dataflow, sign in to the Power BI service and navigate to a workspace on your
dedicated capacity that has the AI preview enabled.
If you don't already have a workspace, you can create one by selecting Workspaces in the left navigation menu in
the Power BI service, and select Create app workspace at the bottom of the panel that appears. This opens a
panel on the right to enter the workspace details. Enter a workspace name and select Advanced. Confirm that the
workspace uses Dedicated Capacity using the radio button, and that it's assigned to a dedicated capacity instance
that has the AI preview turned on. Then select Save.
Once the workspace is created, you can select Skip in the bottom right of the Welcome screen, as shown in the
following image.

Select the Dataflows (preview) tab. Select the Create button at the top right of the workspace, and then select
Dataflow.
Select Add new entities. This launches a Power Query editor in the browser.

Select Text/CSV File as a data source, shown in the following image.

In the Connect to a data source that appears next, paste the following link to the online_shoppers_intention.csv
into the File path or URL box, and then select Next.
https://raw.githubusercontent.com/santoshc1/PowerBI-AI-
samples/master/Tutorial_AutomatedML/online_shoppers_intention.csv

The Power Query Editor shows a preview of the data from the CSV file. Select Transform Table in the command
ribbon and then select Use first row as headers from the menu that appears. This adds the Promoted headers
query step into the Applied steps section on the right of the screen. You can rename the query to a friendlier
name by changing the value in the Name box found in the right pane. For example, you could change the Query
name to Online Visitor.
Some of the attribute data types in this dataset are numeric or Boolean, though these may be interpreted as strings
by Power Query. Select the attribute type icon at the top of each column header to change the columns listed
below to the following types:
Decimal number: Administrative_Duration; Informational_Duration; ProductRelated_Duration; BounceRates;
ExitRates; PageValues; SpecialDay
True/False: Weekend; Revenue

The Binary Prediction model we will train requires a Boolean field as a label identifying the outcomes from the
past observations. In this dataset, the Revenue attribute indicates purchase, and this attribute is already available as
a Boolean. So, we don't need to add a calculated column for the label. In other datasets, you may have to transform
existing label attributes into a Boolean column.
Select the Done button to close Power Query Editor. This shows the entities list with the Online Visitors data we
added. Select Save in the top-right corner, provide a name for the dataflow, and then select Save on the dialog, as
shown in the following image.
Refresh the dataflow
Saving the dataflow results in a notification being displayed, stating that your dataflow has been saved. Select
Refresh now to ingest the data from the source into the dataflow.

Select Close in the upper right corner and wait for the dataflow refresh to complete.
You can also refresh your dataflow by using the Actions commands. The dataflow shows the timestamp when the
refresh has been completed.
Create and train a machine learning model
Select the dataflow after the refresh has been completed. To add a machine learning model, Select the Apply ML
model button in the Actions list for the base entity that contains your training data and label information, and
then select Add a machine learning model.

The first step for creating our machine learning model is to identify the historical data including the label field that
you want to predict. The model will be created by learning from this data.
In the case of the dataset we're using, this is the Revenue field. Select Revenue as the 'Historical outcome field'
value and then select Next.
Next, we must select the type of machine learning model to create. Power BI analyzes the values in the historical
outcome field that you've identified and suggests the types of machine learning models that can be created to
predict that field.
In this case, since we're predicting a binary outcome of whether a user will make a purchase or not, select Binary
Prediction for the model type, and then select Next.

Next, Power BI does a preliminary scan of the data and suggests the inputs that the model could use. You have the
option to customize the input fields used for the model. In our curated dataset, to select all the fields, select the
checkbox next to the entity name. Select Next to accept the inputs.
In the final step, we must provide a name for our model, as well as the friendly labels for the outcomes to be used
in the automatically generated report that will summarize the results of the model validation. Next we have to
name the model Purchase Intent Prediction, and the true and false labels as Purchase and No -Purchase. Then
select Save.

Our machine learning model is now ready for training. Select Refresh Now to start training the model.
The training process will begin by sampling and normalizing your historical data and splitting your dataset into two
new entities Purchase Intent Prediction Training Data and Purchase Intent Prediction Testing Data.
Depending on the size of the dataset, the training process can take anywhere from a few minutes to a couple of
hours. At this point, you can see the model in the Machine learning models tab of the dataflow. The Ready status
indicates that the model has been queued for training or is under training.

While the model is training, you won't be able to view or edit the dataflow. You can confirm that the model is being
trained and validated through the status of the dataflow. This appears as a data refresh in progress in the
Dataflows tab of the workspace.
Once the model training is completed, the dataflow displays an updated refresh time. You can confirm that the
model is trained, by navigating to the Machine learning models tab in the dataflow. The model you created
should show status as Trained and the Last Trained time should now be updated.

Review the model validation report

To review the model validation report, in the Machine learning models, s elect the View performance report
and apply model button in the Actions column for the model. This report describes how your machine learning
model is likely to perform.
In the Model Performance page of the report, select Key Influencers to view the top predictors for your model.
You can select one of the predictors to see how the outcome distribution associated with that predictor.
You can use the Probability Threshold slicer on the Model Performance page to examine its influence on the
Precision and Recall for the model.

The other pages of the report describe the statistical performance metrics for the model.
The report also includes a Training Details page that describes the different iterations that were run, how features
were extracted from the inputs, and the hyperparameters for the final model used.

Apply the model to a dataflow entity

Select the Apply model button at the top of the report to invoke this model when the dataflow is refreshed. In the
Apply dialog, you can specify the target entity that has the source data to which the model should be applied.
When prompted, you must Refresh the dataflow to preview the results of your model.
Applying the model will create a new entity, with the suffix enriched <model_name> appended to the entity to
which you applied the model. In our case, applying the model to the OnlineShoppers entity will create
OnlineShoppers enriched Purchase Intent Prediction, which includes the predicted output from the model.
Applying a Binary Prediction model adds three columns with predicted outcome, probability score, and the top
record-specific influencers for the prediction, each prefixed with the column name specified.

Due to a known issue, the scored output columns in the enriched entity are only accessible from Power BI Desktop.
To preview these in the service, you must use a special preview entity.
Once the dataflow refresh is completed, you can select the OnlineShoppers enriched Purchase Intent
Prediction Preview entity to view the results.
Using the scored output from the model in a Power BI report
To use the scored output from your machine learning model, you can connect to your dataflow from the Power BI
desktop, using the Dataflows connector. The OnlineShoppers enriched Purchase Intent Prediction entity can
now be used to incorporate the predictions from your model in Power BI reports.

Next steps
In this tutorial, you created and applied a binary prediction model in Power BI using these steps:
Create a dataflow with the input data
Create and train a machine learning model
Review the model validation report
Apply the model to a dataflow entity
Using the scored output from the model in a Power BI report
For more information about Machine Learning automation in Power BI, see Automated Machine Learning in
Power BI (Preview ).
 3/26/2019 • 33 minutes to read • Edit Online

What's new in the Power BI service

Check this page for known issues and recently released features in the Power BI Service. For related
"What's New" information, see:
What's new in business intelligence October ‘18 release notes from the Microsoft Business
Applications Group: The latest updates to our business applications.
What's new in Power BI Desktop
What's new in the mobile apps for Power BI
Power BI team blog
Also, check out the YouTube channels for information about "What's new" and features.
Microsoft Power BI (YouTube)
Guy in a Cube (YouTube)

March 2019
General Availability of Multi-Geo for Power BI Premium.
Editing and managing Power BI content support for Azure B2B.

Previous months (2019)

February 2019
Workloads and active dataset size metrics in Capacity Monitoring app.
Export to PDF for Power BI reports.
On-demand e-mail subcriptions.
Bulk operations in the Admin Portal.
Filtered export for PPT and PDF.
Help and support settings in the Admin Portal.
Data lineage experience for dataflows.
Certified custom visuals setting in the Admin Portal.
January 2019
Embedding secure Power BI reports in internal portals or websites.
Updates to dataflows editor with new connectors, and support for native SQL queries and Power
Query Online transformations.
Personal bookmarks in the Power BI service.
Time-based scheduling with e-mail subscriptions.

2018
December 2018
AI-powered recommended apps in Power BI Home.
Workspace management in the Admin Portal.
 Preview of Power BI Dataflows and Azure Data Lake Storage Gen2 Integration in dataflows.
Power BI solution templates became open source.
November 2018
Power BI data prep available with dataflows public preview.
Public preview of paginated reports in Power BI Premium.
Data size and count of datasets in memory in the Capacity Monitoring app.
October 2018
Aggregations[desktop-aggregations.md] in the Power BI service.
Power BI expanded to three new regions: Central India, Australia East, and Central US (Iowa).
Export to PowerPoint made generally available.
September 2018
Dashboard commenting in the Power BI service.
Public preivew of Power BI Home and Global Search.
Abiliy to monitoring queries in the Capacity Monitoring app.
August 2018
Capacity Monitoring app for Power BI Premium.
Power BI Report URL filter improvements.
July 2018
Custom visuals support for persistent filters.
APIs and PowerShell Cmdlets for Power BI administrators.
Multi-Geo support for Power BI Premium.
June 2018
Sharing reports with filters and slicers.
New and improved user interface for gateway connections and setting up datasets.
May 2018
Theme dashboards in the Power BI service.
Incremental refresh with Premium.
Request access workflow for Power BI Apps.
Get Data updates to make it easier for users to find Power BI Apps.
Settings to turn on and off Persistent filters in the Power BI service.
Azure B2B invite workflow improvements for reports.
April 2018
Power BI Whitepaper on data protection
Power BI Service audit logs turned-on by default for Office 365 tenant.
March 2018
Persistent filters in the Power BI Service.
Share content with users using their personal e-mail accounts. Extension of Azure Active Directory
B2B.
February 2018
Automatically install Power BI Apps for end users.
P4 and P5 capacities on Power BI Premium
Preview of Organizational custom visuals.
January 2018
Share and favorite Power BI reports.
OAuth2 and DirectQuery Single Sign-on Support (SSO ) for Azure SQL Database and Data
Warehouse.
In-region auditing: audit logs will now be stored in the same Office 365 region as their tenant.
GA of SharePoint Online Power BI report web part.
Admin control to turn off viewing custom visuals for all users in a tenant.
Scheduled refresh support for Azure Analysis Services (AAS ).

Previous months (2017)

October and November 2017
Selective publish of content with Power BI Apps.
External user distribution with Azure Active Directory B2B.
AI-powered app recommendations.
Dashboard on-tile UI updates.
E -mail subscriptions support for apps.
Granular admin control for publish to web.
September 2017
In Premium capacity, share dashboards to users who don't have a Power BI Pro license.
Allocate capacities to suit your business needs with v-core pooling.
Instantly scale-up or scale-down capacities with one click.
PubNub block to easily push data into REST APIs
Improved load performance for usage metrics.
August 2017
Know your audience with per-user usage metrics.
Get started with Power BI service apps for online services.
Connect to IBM Netezza with the On-premises data gateway through both import and DirectQuery
connectivity modes.
Dynamic RLS now supported for Power BI Embedded.
Advanced filtering API now added for the 1.7 release of custom visuals API.
July 2017
Support for email subscriptions on dashboards.
Inspect and diagnose why the loading time is poor for dashboards using the Performance Inspector.
Snowflake and SAP BusinessWarehouse DirectQuery now supported for On-premises data gateway.
New APIs to manage data refresh in Power BI service.
June 2017
Power BI Premium made generally available.
Multiple API improvements to automate scheduled refresh, clone and rebind reports, update gateway
bindings, and much, much more
Relative links in Power BI apps from dashboard tiles to other dashboards and reports.
Impala connector generally available on Power BI Desktop.
Extend visual capabilities of Power BI with interactive R custom visuals.
April and May 2017
Measure and magnify your impact with usage metrics for dashboard and report creators.
 Connect to PostgreSQL with the On-premises data gateway.
Power BI SharePoint Web Part made available for all users.
Connect Power BI to any data source using the Data Connector SDK.
Navigate to reports with multiple URL filter parameters.
Preview: Use Power BI Apps to widely distribute your dashboards and reports to large audiences.
March 2017
Fine-tune how Power BI used in your organization with granular admin controls.
Get more done in less time with the View Related Content pane.
Improved troubleshooting messages for DAX queries.
Exercise more control over your datasets with custom cache refresh schedules.
Connect to Amazon Redshift.
Browse Power BI custom visuals in the Office Store.
Preview: Subscribe to report pages to stay on top of your data.
Use the Azure AD Content Pack to learn more about how your employees and partners are using
Azure AD.
February 2017
Navigation Preview improvements – more easily switch between workspaces, and take action on
content within the current workspace.
Embed Power BI dashboards into your custom application.
Preview: Integrate Power BI reports in SharePoint Online.
January 2017
Administer Power BI using the Power BI admin role.
Power BI audit logs in the Office 365 auditing portal are globally available.
Version 1.4 of developer tools and custom visuals APIs released.
Real-time streaming feature set released to general availability.
Push data to Power BI using Microsoft Flow without writing a line of code.
Preview: Subscribe to report pages to stay on top of your data.
Use the Azure AD Content Pack to learn more about how your employees and partners are using
Azure AD.

2016
November 2016
Preview: Try out the new navigation for the Power BI service, powerbi.com
Preview: Export a Power BI report to PowerPoint.
Preview: Download Power BI reports (PBIX files) from the Power BI service so you can edit them in
Power BI Desktop.
Create a liquid fill gauge, a circle gauge that represents a percentage value with animated liquid
waves.
Explore your Jira project-management data with this Power BI content pack
Explore your Insightcentr data with this Power BI content pack
Create infographics quickly with the infographic designer custom visual
Private preview: Azure Stream Analytics outputs Power BI streaming datasets, with which you can
create streaming tiles.
Preview: Add ESRI ArcGIS Maps Visualizations to your reports and dashboards
October 2016
 Take advantage of Power BI integration with the new Microsoft Teams.
Design R visualizations in Power BI without understanding R.
Preview: With Azure Analysis Services, BI professionals can create BI semantic models based on data
that resides in the cloud or on premises, to provide business users with a simplified view of their data.
The new Power BI Service Administrator Role can be assigned to users who should have access to the
Power BI Admin Portal but not other Office 365 administrative access.
Explore your MYOB Advanced data with Power BI.
How a non-administrator can review the Power BI audit log
Display text columns as ToolTips.
July 2016
RLS graduates from preview
Row Level Security (RLS ) lets you restrict data access based on who is accessing it. Recently we
streamlined the process of configuring RLS by exposing roles and rules in Power BI Desktop. Today,
we are happy to announce that RLS is now generally available for all Power BI Pro users.
Data classification
You can now tag your dashboards with classifications defined by your company's IT department,
raising awareness of those viewing your dashboards about what level of security should be used.
Analyze your on -premises data in Excel
Analyze in Excel feature has expanded to support on-premises datasets. We establish a secure and
direct connection to your on-premises dataset that enables you to analyze it in Excel. We also
introduced a setting for admins to turn off the Analyze in Excel feature for on-premises sources.
For all the details, visit the Power BI team blog
June 2016
Quick Insights
Quick Insights work with Complex Filters: We are happy to announce that Quick Insights scoped to a
single tile now understand complex filters.
For all the details, visit the Power BI Team blog
May 2016
Get Data
File size limit increase to 1 GB: We increased the file size limit for both Excel workbooks and Power BI
Desktop files to 1 GB.
Find SSAS servers set up with the Enterprise gateway and other gateway updates: Now when you set
up an Enterprise gateway, users in your company will be able to access these servers in the Power BI
service through the Get Data page. We also added support for refreshing datasets that include data
from SAP Business Warehouse Server using the gateway and creating UPN mapping rules when you
are using Analysis Services with the gateway.
Row -level security (RLS )
Azure Active Directory (AAD ) group support: Users can now assign AAD groups (security groups and
distribution lists) to a role. This makes it easier to assign roles to a large group of users at once.
Test your RLS roles with reports backed by the data with RLS in place: We added a feature to our RLS
preview that lets you test your dataset as a specific role. This will make sure the role works as you
expect before any users get their hands on your dashboard.
 Define and apply RLS to cloud models based on direct queries: You can now create and apply RLS
rules for direct query data sources.
Dashboards
Favorite dashboards: To help you reach the dashboards you go to most, we added a way to favorite
those dashboard and make them easily accessible from all your workspaces.
Analyze in Excel
Improved download experience: Easily download updates to the Analyze in Excel feature through a
new dialog experience.
Support for RLS: Once you set up RLS, the rules you apply to the data now flow through when a user
analyzes the data in Excel.
Improved error messaging for on-premises Analysis Services databases: Previously, if you selected
Analyze in Excel for an unsupported data source, you wouldn't get an error message until after you
downloaded the ODC file and tried to connect to Power BI. Now as soon as you select Analyze in
Excel for a data source we don't support, you'll see a message letting you know we don't yet support
that data source.
For all the details, visit the Power BI Team blog
Power BI Q&A support for SQL Server 2016 Analysis Services tabular models: We are pleased to
announce improvements to the Power BI Q&A user experience and the start of the public preview for
Power BI Q&A for enterprise gateway connected data sources - starting with support for SQL Server
2016 Analysis Services tabular models. For all the details, see the blog post
Local File Support for Excel Reports: You can now upload your Excel files from your local drive or
other storage services and use that Excel Report just as you would in Excel Online with the added
benefits of Power BI. For all the details, see the blog post
April 28, 2016
Quick Insights on Dashboard Tiles: When viewing a tile in Focus mode, click Get Insights to search the
tile and its related data for correlations, outliers, trends, seasonality, change points in trends, and major
factors automatically, within seconds.
For all the details, visit the Power BI Team blog
April 26, 2016
Narratives for Power BI: As you interact with your data and visualizations, this custom visual
dynamically delivers insights in narrative form, just like you'd expect an analyst would write. This
visual is fueled by Narrative Science Quill.
For all the details, visit the Power BI Team blog
April 16, 2016
Microsoft Trust Center: Power BI joined the Microsoft Trust Center, a single source for documenting
compliance certifications for Microsoft products. Power BI's certifications include ISO 27001, ISO
27018, EU Model Clauses, HIPAA BAA, and UK G -Cloud.
For all the details, visit the Power BI Team blog
April 14, 2016
Enterprise
ExpressRoute: use to establish a private, managed connection to Power BI.
 Content pack support for RLS (Preview ): If RLS is defined for those dashboards and reports that are
distributed as part of a content pack, then the security rules will be respected for those content packs.
Dashboards
Vimeo video tile: From the dashboard, add a tile that contains an embedded Vimeo player.
Analyze in Excel
Analyze in Excel available to all users: the ability to access your Power BI data models in Excel has
been extended to all users, regardless of the license they're assigned.
Improved multi-user account experience: if you have more than 1 Power BI user account, it's now
easier to sign-in.
For all the details, visit the Power BI Team blog
March 31, 2016 Lots of updates announced at the Microsoft Data Insights Summit.
Dashboards
Featured dashboard: makes it easier to reach the dashboard you care about most.
Filter dashboard list: show all, show content you created, show content shared with you.
Enterprise features
Admin usage reporting: added a usage report to the Power BI admin center.
Row -level security: this is a Preview feature that allows you to set permissions on Power BI datasets.
Disable exporting data: users in your tenant will no longer be able to export tile and visual data to a
.csv file.
Q&A
Auto complete for "is": Q&A will suggest values if you type column name followed by "is".
Mobile
KPIs on your Apple watch: monitor your KPI and card tiles without having to open Power BI app.
Excel
Analyze in Excel: connect your Power BI data model to Excel and do your analysis inside of Excel
instead of Power BI.
Other
Power BI in Australia: now anyone in Australia, individual or through an organization, can go to
powerbi.microsoft.com and sign up for Power BI.
Language settings: override the automatic language detection and set the language for Power BI.
For all the details, visit the Power BI Team blog
March 11, 2016
This month we made some updates to dashboards, Quick Insights, and Q&A.
Dashboards
Full Screen mode: print without having to exit Full Screen mode first
Full Screen mode: expand your tiles to fill the entire canvas and remove excess white space by
selecting Fit to Width
 Use Tile Flow to automatically align your tiles to the top left corner of the canvas.
Quick Insights
The Trend and Correlaction insights now have trend lines to make it easier to see patterns in the data.
Q&A
You can now specify Gauge and Area charts in Q&A
Improved auto-complete for Q&A - as soon as you type just a few characters, Q&A begins auto
completing and suggesting visuals for you.
For all the details, visit the Power BI Team blog
February 10, 2016
Today we released a long list of top-requested features. Read the blog post.
Sharing
Share with users outside your organization
Request access to a dashboard
Admin Portal
Easy user management with a link to the Microsoft 365 admin center
Ability to disable publish to web
Prevent users from publishing content packs to the entire org
Ability to disable sharing content to external users
Quick Insights
Quick Insights when you publish Power BI Desktop files
Dashboard
Add Web content to your dashboard (via Widget)
Add video content to your dashboard (via Widget)
Zoom on dashboards
Connectivity
Connect to files on your team SharePoint site through a URL
For all the details, visit the Power BI Team blog
January 28, 2016
Updates to reports and visualizations:
Add borders to visuals
Add background images to pages and Cartesian chart plot areas
Performance Improvements for report rendering, cross-highlight, etc.
Regardless of the browser version being used, a significant Performance improvement can be noticed
by users when loading reports, switching between pages, cross-highlighting data across visuals, etc.
with this new update.
January 6, 2016
The Power BI team has been busy over the holiday break. For all the details, visit the Power BI Team blog
Dashboards
Export tile data
Add an image or text box widget to dashboards
Print dashboards
Refresh time on tiles
Tooltips on dashboard tiles
Collaboration
Shared dashboard notification
Contact owner of a shared or organizational dashboard
Reports
Print current report page
Export report visual data
Connectivity
Connect to files on SharePoint team sites
Excel Reports
Open Excel reports in Excel desktop
Pin Excel charts
Format improvements for Excel tiles
Other
Power BI in Brazil
Hebrew and Arabic support
For all the details, visit the Power BI Team blog

2015
December 16, 2015
Lots of updates this week, most apply to Power BI Desktop but several significant updates to report
authoring and visualizations as well. The Power BI Team Blog contains full descriptions and even a video
describing the updates.
Download Power BI Desktop
Updates to the report authoring formatting pane and ribbon:
1. Format data labels per category series
2. Change number of decimal places showed in visuals
3. Change text size in visuals
4. Ability to lay out visuals accurately: alignment, distribute, size, position (requires Power BI
Desktop for authoring)
5. Set styles across multiple visuals through Format Painter (requires Power BI Desktop for
authoring)
Enhancements to visualizations:
 1. visuals cue for sort state in Table visual
2. new visual: Stacked Area chart
3. smart tooltips for Area and Line charts on hover
4. ability to create Reference line/region for a Cartesian visual
5. improved data labels for pie and scatter chart
R visuals integration in Desktop (Preview feature)
Desktop will suggest table to table relationships when trying to create 2 tables which are not
related.
Desktop optimized Home ribbon layout.
Desktop data modeling updates in Relationships View:
1. zooming slider
2. fit zoom to
3. reset layout
4. ability to zoom in using Ctrl-Mouse selection rectangle
Desktop data connectivity enhancements
1. SSAS Multidimensional support - Hierarchies support (Preview Feature)
2. Stripe Connector
3. Smartsheet Connector
4. “Enter Data”: Paste or enter data to create a table
5. DirectQuery Improvements: Support for all data types of T-SQL and SAP HANA, resulting in
Performance improvements.
6. ODBC Connector: Support for selecting User/System DSNs
7. CSV Connector: Ability to specify Column Delimiter in the Source dialog
For all the details, including a video demonstrating many of these updates, visit the Power BI Blog.
December 10, 2015
Pin report pages to dashboard
Refresh dashboard tiles
Use images in slicers
Change interactions between report visuals
For all the details, visit the Power BI Blog.
December 8, 2015
QR codes in Power BI
December 3, 2015
Automatically discover trends and uncover patterns in a dataset with Quick Insights: video or article
Visualize your VMob data in Power BI
Power BI integration with Cortana
Preview of Power BI gateway for enterprise
Introducting a new content pack: Search Analytics from Bing on Power BI dashboards
New Developer-focused enhancements: Two new APIs and easier app registration
November 24, 2015
 Pin Excel ranges to dashboards
Chromeless full screen mode for dashboards and reports
Know where your data is stored
Improved loading of on-premises reports
Share dashboards directly to another user's workspace
Improved Google Analytics connector experience
Close your power bi account
For all the details, visit the Power BI Blog
November 18, 2015
Create a duplicate dashboard
Freely position dashboard tiles
Improved navigation for full screen view
Better experience when inviting peers from your organization to Power BI groups
Improved error messages for tiles
For all the details, visit the Power BI Blog
November 11, 2015
New site for Power BI documentation, localized
Improved load time for reports
Update organizational content packs with report-only changes
Power BI health status in Microsoft 365 admin center
KPIs and images in tables, matrices, and cards
For all the details, visit the Power BI Blog
November 3, 2015
Guided Power BI purchase experience.
Individuals can buy Power BI Pro.
Duplicate report page.
For all the details, visit the Power BI Blog
October 28, 2015
Share dashboards with Active Directory Security groups
People picker
Sharing with a large number of email addresses
Collapse navigation pane through an URL parameterized
For all the details, visit the Power BI Blog
October 20, 2015
Read-only members in Power BI groups
Featured questions in Q&A
Full screen pop-out mode for report visualizations
For all the details, visit the Power BI blog
October 13, 2015
 Full screen mode to display your dashboards and reports on big screen TVs
'Fit to screen’ support in full screen mode to display your entire dashboard in the available space
In-focus mode to get more details on dashboard tiles
Ability to view last update time for each tile
Ability to view the source for each tile
Planview Enterprise is an end-to-end portfolio and resource management solution that connects
strategy to execution, improving decision-making across the enterprise. The Planview Enterprise
content pack for Power BI allows you to visualize your resource and work management data in an
entirely new way. Simply sign in with your credentials and begin to interactively explore your portfolio
investment spend, budget status, and how well your projects align with strategic priorities.
View our blog and online documentation to learn more.
October 6, 2015
With Power BI Q&A, you can explore your data using simple, intuitive questions and receive answers
in the form of interactive charts and graphs. With this release, we have added a feature to help you get
started with Power BI Q&A, even when you do not know anything about the data. To get started with
this, navigate to any dashboard and click the “How to ask” link near the Q&A question box. Power BI
presents you with a number of suggestions based on your data.
Two weeks ago, we introduced support for inserting shapes into the report canvas in Power BI
Desktop. This week, we are happy to announce that you can now add shapes to your report canvas
when you are authoring and/or editing reports in the Power BI web app.
We have added the option to turn off email notification when you share a dashboard. Simply uncheck
the “Send email notification to recipients” check box in the Power BI share dialog. You will be
presented with a URL – copy and share this URL to your colleagues to give them access to the
dashboard.
Microsoft Dynamics NAV is a business management solution for small to medium organizations. It
offers customers a full solution for their business with greater control over their financials and
business processes. The Power BI content pack provides out-of-box reports for Dynamics NAV users,
such as sales and profit, opportunities pipeline, profitability and more. These metrics are organized on
a dashboard that can be fully customized, allowing you to easily connect and immediately start
exploring your data.
Check out the blog and online documentation for more information.
September 29, 2015
With this week’s service update, when creating new reports you can now choose from multiple page
sizes as well as define your own page size. This controls the size and aspect ratio of each page in the
report.
We added additional visual formatting support for images and bubble charts. You can lock the aspect
while resizing images to avoid image distortion and scatter chart bubbles can be configured to be
filled or not.
Today, Power BI will send sharing invites to an alternate email address. When a dashboard is shared
with you, we will send the sharing invite link both to your original email address and to your alternate
email address (if you have it configured).
Power BI is available to all customers including those on the Dedicated on Multitenant (DonMT) O365
architecture. You will be using Power BI as a shared service in multi-tenant mode. In most cases, you
can register for Power BI by following the simple self-service-signup process – just enter your work
email address, enter your name and password to get started. If you are the tenant administrator, you
can assign licenses to your users using the instructions here.
Azure Audit Logs allows you to view control-plane operational logs in your Azure subscription. The
 Power BI Azure Audit Logs content pack can help you easily analyze and visualize the wealth of
information contained in these logs. The content pack allows you to connect to your data and begin to
discover insights with the out-of-the box dashboard and reports. Read our blog and online
documentationfor more information.
Learn more in our blog.
September 22, 2015
Have more flexibility on your dashboard to customize your dashboards with additional tile sizes,
ranging from 1x1 to 5x5.
You can now share (and un-share) a dashboard from your group space exactly the way you would do
it in your own space. Once colleagues accept your sharing invitation, the shared dashboard (and their
associated reports) will be added in their own space with read-only permission.
We added 5 additional industry related samples to Power BI: Customer Profitability, Human
Resources, Opportunity Analysis, Procurement Analysis, and Sales and Marketing Sample.
Stripe is an advanced payment platform for online businesses. From start-ups to Fortune 500
companies, thousands of businesses use Stripe to accept payments in over 130 currencies, from
anyone in the world. By connecting Power BI with your existing Stripe account, you’ll be able to use
the Power BI Stripe content pack to monitor, explore, and visualize your Stripe activity.
Learn more in our blog.
September 15, 2015
You can now choose which dashboard you want to pin your visual to! You can choose the target
dashboard from your existing dashboards, or even create a new dashboard and pin the visual to it in
one shot.
Additionally, you can control your visual colors in the dashboard. If your report is using a different
theme from the dashboard theme, you can control whether the visual retains current theme, or uses
the default dashboard theme to achieve consistency across visuals from various sources.
You can now simply pin the tile from one dashboard to another, the same way you would pin a report
visual to a dashboard.
If your 60-day Power BI Pro trial period is close to expiration, you can contact us to request an
extension to your trial. If approved, your trial will be extended for another 60 days.
comScore Digital Analytix is an online solution that provides insights into your user base through the
best of analytics and audience demographics. With the Power BI comScore content pack, you can
quickly connect and begin gaining insights into your web analytics data. This content pack includes an
out-of-the box dashboard, a set of reports, and a curated data set to help you explore and drill into
your data. Learn more about the content pack in our blog and help topic.
September 8, 2015
Friendly Hyperlinks now allow you to provide links for your users without needing to display the
entire URL in the textbox.
Drill Support has been added to Power BI Reports. You can create a Drill path that enables users to
navigate from one level of data to related data.
Two new Industry Related Samples, It Spend Analysis and Supplier Quality Analysis, have been added
under the samples section of the Get Data experience. These samples are great examples of how you
can use your data to create insightful reports and dashboards.
We have a new content pack for tyGraph, which allows you to easily gain deeper insights into your
Yammer data. The content pack includes a dashboard, a set of reports and a curated dataset to explore
and provide insights such as the Measure of Active Engagement (The MAE Score) and content
consumption metrics such as File Views and File Downloads. Learn more on our blog and help topic.
September 1, 2015
Webtrends helps companies make sense of their customer data to drive digital marketing success.
Users have the ability to observe, analyze and deliver insights on the visitor journey across web, social,
mobile and SharePoint channels. With the release of the Webtrends content pack, users will now have
the ability to use Power BI to monitor, analyze, and visualize their Webtrends analytics data. The
Webtrends content pack for Power BI help page has more information.
Getting started with Q&A is even simpler. The moment you put your cursor inside the Q&A text box,
we instantly display a list of questions and key metrics that are relevant to your data. In the drop
down, by default, you will see the questions for tiles already pinned to the dashboard as well as an
entry for each table you have in your dataset.
The dynamic canvas size we display by default renders all our report items with optimal dimensions
for the browser window size. If you want to lock in the aspect ratio, or want to fit your report in a
different way, we now support another three options for you:Fit to Page, Fit to Width, and Actual Size.
We also Increased the limit on the number of datasets and reports you can have. You can now have up
to 200 datasets and 200 reports for each dataset in your Power BI account.
August 25, 2015
Now you can use Power BI to monitor, explore and visualize your Adobe Analytics data. With an out-
of-box content pack, you can connect and discover insights from your data immediately. To learn
more, visit the Adobe Analytics content pack for Power BI help page.
August 18, 2015
Azure Mobile Engagement is an app analytics service that allows developers to track their
application’s performance helping them increase retention and app usage. Using the Power BI Azure
Mobile Engagement content pack you can quickly connect to an out-of-box dashboard, a set of
reports and a curated data set, and instantly get insights into how well your app is doing. Please see
the Azure Mobile Engagement content pack for Power BI help page for more information.
August 11, 2015
Mandrill is an email infrastructure service developed by MailChimp that lets you analyze your email
campaigns from a wide variety of information. With the Power BI Mandrill content pack, you can
quickly connect to your Mandrill data and immediately gain insights into your newsletter or marketing
campaign. For additional details on how to get started, please see the Mandrill content pack for Power
BI help page.
August 4, 2015
Power BI now offers Circuit ID users the ability to track and monitor all their Circuit ID cloud
communications services, empowering them to make the right business decisions. For additional
details on how to get started, please see the Circuit ID content pack for Power BI help page.
Today we’ve released an enhancement to the Share Dashboard feature to make it even easier to use. If
your organization uses Office 365 for email, you can now share to an email distribution group just the
same way you would send an email in Outlook. Just enter the address of the distribution group and
click Share. All members of the distribution group will receive an email invitation to view the
dashboard.
July 28, 2015
We’re excited to announce that this week’s update to Power BI now offers database performance
tracking with the SQL Sentry content pack. This content pack includes a dashboard and reports that
help you monitor the SQL Server deployments you track using the SQL Sentry Cloud. For additional
details on how to get started, please see the SQL Sentry content pack for Power BI help page.
July 24, 2015
We're excited to announce our "general availability" (GA) release of Power BI. Sign up today for Power
BI Pro. As part of the GA release, we are offering some great new features:
A new visualization and report creation experience: The new reporting canvas has a larger selection of
visualizations, more control over formatting of titles, legends, axes, colors, backgrounds, and more.
Power BI groups: groups offer a powerful collaborative experience built on Office 365 groups.
Organizational content packs: Power BI makes creating dashboards and reports extremely simple, and
now users can publish this content to the organizational content gallery.
Bring in whole Excel files: You can bring any Excel workbook stored on OneDrive for Business into
Power BI and view the entire workbook, exactly as you would in Excel Online.
Bring in CSV files: Just like Excel or Power BI Desktop file, a comma-separated values text (CSV ) file
can also be a dataset for your Power BI dashboards and reports.
Replace Excel, Power BI Desktop, and CSV files: you can upload an updated version of a file to Power
BI and it will replace the existing dataset. All the reports and dashboards that are connected to this
dataset now automatically use the new version.
We’re excited to announce that this week’s update to Power BI now offers work item tracking in the
Visual Studio Online content pack. This update includes a new dashboard, report and an updated data
set offering insights on your work items in addition to important metrics about your Git repository,
pull requests, and version control content included in the initial version. For additional details on how
to get started, please see the Visual Studio Online content pack for Power BI help page.
July 14, 2015
Acumatica Cloud ERP delivers a suite of fully integrated business management applications such as
Financials, Distribution, CRM and Project Accounting, powered by a robust and flexible platform. With
the Power BI Acumatica content pack, you can quickly connect and immediately gain insights into
your opportunity data. This content includes an out-of-box dashboard, a set of reports and a curated
dataset to explore and provide details such as your total won opportunities by date. Read more here.
Azure HDInsight now offers a fully managed Spark service. This capability allows for scenarios such
as iterative machine learning and interactive data analysis. Power BI allows you to directly connect to
the data in Spark on HDInsight offering simple and live exploration. Read our help doc for more
information.
Office 365 navigation and application launcher integration. With a single click, you can now navigate
to all of your Office 365 applications.
Specifying a custom URL that users navigate to when they click a tile. You now have the ability to
control exactly where users go: a specific report, another dashboard, an SSRS report, or an external
website.
Visibility and management of the storage you are consuming in Power BI
Configuring the visual and fields displayed in Q&A
July 7, 2015
One of the most awaited and requested feature is now available in Power BI. Starting today, in Power
BI you can refresh datasets connecting to your on-premises sources such as SQL Server. You can
refresh a dataset that has been created from a Power BI Designer file or an Excel workbook with data
imported into the workbook using Power Query or Power Pivot.
June 30, 2015
We released a new Power BI UserVoice content pack that can help you monitor and visualize your
UserVoice data and immediately gain insights into it with the ready-to-use dashboard and report.
June 23, 2015
 Power BI Desktop files can be refreshed (scheduled refresh & refresh now ) when uploaded to the
Power BI service.
We are releasing the biggest visual change to Power BI since December: a cleaner and simpler
experience to Get Data. When you click on Get Data, you are now presented a single screen with a set
of categories to choose from. This will make it even easier to find the content that matters to you.
Azure SQL Data Warehouse offers elastic scale and massive parallel processing. With the limited
public preview announced today, Power BI allows you to directly connect to the data stored in your
Azure SQL Data Warehouse offering simple and dynamic exploration. After creating a connection to
your data warehouse, queries are generated in real time and sent back to the source as you explore
the data. This removes the need to create and upload a custom data model and offers interactive
exploration of your data.
June 16, 2015
SweetIQ lets you to easily track your local listings by providing location and review data from your
local search ecosystem. Power BI allows you to analyze and monitor that data, by offering out of box
content built from your SweetIQ data. For additional details on how to get started, please see the
SweetIQ content pack for Power BI help page.
June 9, 2015
Power BI allows you to monitor and explore that data using the MailChimp APIs, offering a set of out-
of-box content for your analytics. The dashboard, reports and dataset curated for the MailChimp
scenario allow you to easily access data such as Top Campaigns of Total Opens by Day of Week. For
additional details on how to get started, please see the MailChimp content pack for Power BI
documentation.
June 2, 2015
Now tracking important statistics about your apps is easy with Power BI and the appFigures content
pack. For additional details on how to connect and get started, see the documentation for appFigures
content pack for Power BI.
May 28, 2015
Get quick insights into your QuickBooks Online account data using our content pack. For additional
details on how to connect and get started, see the QuickBooks Online content pack for Power BI
documentation.
May 13, 2015
With the latest update to Power BI, you can connect to the data logged by SQL Database Auditing
with a set of out of box reports and a customized dashboard. This content pack makes it easy to find
suspicious events, unusual activity, and trends, based on a dataset that has been created for your
reporting. Learn more in the blog post and documentation.
You can connect directly to data stored in your Azure SQL Database. We dynamically generate and
send down queries to the source, allowing you to create interactive reports directly over your
database. You can read the blog post and documentation for more information.
May 7, 2015
We updated our look to a new modern design, a look that is fresh and distinctive while keeping your
focus on what matters: your data and your insights.
April 28, 2015
Power BI is now available in 44 languages. Read our blog post to see the full list.
April 23, 2015
You can now visualize and explore your Microsoft Dynamics Marketing data with our new content
pack! You can read our blog post for more information.
April 15, 2015
You can now visualize and explore your Google Analytics data with our new content pack! With the
Google Analytics content pack you will get a dashboard, report and dataset that allow you to gain
insights into the usage of your site in the last 6 months. You can read our blog post and
documentation for more information.
You can now pin all cards expect those containing KPIs and Images from Q&A and reports
You can now use cards in Q&A by using the phrase 'as card' at the end of your query
March 31, 2015
GitHub dashboards have new visuals that focus on community building, improved calculations, and
improved layout
SendGrid dashboards have new visuals and a new layout to help you find better insights
You can now use treemaps in Q&A by using the phrase 'as treemap' at the end of your query
You can now pin treemaps from Q&A and reports
Lots of bug fixes!
February 25, 2015
Bug fixes and improvements to user experience and reliability.
January 26, 2015
Service usability and reliability has been improved through various bug fixes.

2014
December 11, 2014
Reliability of refresh with OneDrive has been improved. Some situations where workbooks were not
refreshing from OneDrive have been resolved.

Next steps
What is Power BI?
More questions? Try asking the Power BI Community
 Basic concepts for designers in the Power BI service
2/8/2019 • 12 minutes to read • Edit Online

The aim of this article is to orient you to the Power BI service: what the different elements are, how they work
together, and how you can work with them. You may get more out of it if you've already signed up for the Power
BI service and added some data. As a designer, your typical workflow is usually to start by creating reports in
Power BI Desktop. Then you publish them to the Power BI service, where you can continue modifying them. You
also create the dashboards based on your reports in the Power BI service.
For this article, if you don't have your own reports yet try installing a Power BI sample content pack.

When you open the Power BI service in a browser, you start at your Home screen. Here are the elements you may
see:
1. Navigation pane (left nav)
2. Office 365 app launcher
3. Power BI home button
4. Icon buttons, including settings, help, and feedback
5. Search box
6. Tiles from a favorite dashboard
7. Favorite and frequent dashboards and reports
Your end users for your reports and dashboards have the same start experience in the Power BI service in a
browser.
We'll dig into these features later, but first let's review some Power BI concepts. Or you might want to watch this
video first. In the video, Will reviews the basic concepts and gives a tour of the Power BI service.
https://www.youtube.com/embed/B2vd4MQrz4M

Power BI concepts
The 4 major building blocks of Power BI are: dashboards, reports, workbooks, and datasets. And they're all
organized into workspaces. It's important to understand workspaces before we dig into the four building blocks,
so let's start there.

Workspaces
Workspaces are containers for dashboards, reports, workbooks, and datasets in Power BI. There are two types of
workspaces: My workspace and app workspaces. So what is an app? A Power BI app is a collection of dashboards
and reports built to deliver key metrics to the Power BI end users for your organization. Apps are interactive but
end users can't edit them.
My workspace is the personal workspace for any Power BI customer to work with your own content. Only you
have access to your My workspace. You can share dashboards and reports from your My Workspace. If you
want to collaborate on dashboards and reports, or create an app, then you want to work in an app workspace.
App workspaces are used to collaborate and share content with colleagues. They are also the places where you
create, publish, and manage apps for your organization. Think of them as staging areas and containers for the
content that will make up a Power BI app. You can add colleagues to your app workspaces and collaborate on
dashboards, reports, workbooks, and datasets. All app workspace members need Power BI Pro licenses, but
app consumers (the colleagues who have access to the apps) don't necessarily need Pro licenses.
To learn more, start with Ways to share dashboards your work.
Now, on to the Power BI building blocks. You can't have dashboards or reports without data (well, you can have
empty dashboards and empty reports, but they're not useful until they have data), so let's start with datasets.

Datasets
A dataset is a collection of data that you import or connect to. Power BI lets you connect to and import all sorts of
datasets and bring all of it together in one place.
Datasets are associated with workspaces and a single dataset can be part of many workspaces. When you open a
workspace, the associated datasets are listed under the Datasets tab. Each listed dataset represents a single
source of data, for example, an Excel workbook on OneDrive, or an on-premises SSAS tabular dataset, or a
Salesforce dataset. There are many different data sources supported, and we’re adding new ones all the time. See
the list of dataset types that can be used with Power BI.
In the example below, I've selected the "Sales and marketing" app workspace and clicked the tab for Datasets.
ONE dataset...
can be used over and over in one or in many workspaces.
can be used in many different reports.
Visualizations from that one dataset can display on many different dashboards.

To connect to or import a dataset, select Get Data at the bottom of the left navigation. Follow the instructions to
connect to or import the specific source and add the dataset to the active workspace. New datasets are marked
with a yellow asterisk. The work you do in Power BI doesn't change the underlying dataset.
If you're part of an app workspace, datasets added by one workspace member are available to the other
workspace members.
Datasets can be refreshed, renamed, explored, and removed. Use a dataset to create a report from scratch or by
running quick insights. To see which reports and dashboards are already using a dataset, select View related. To
explore a dataset, select it. What you're actually doing is opening the dataset in the report editor where you can
really start digging into the data and creating visualizations. So, let's move on to the next topic -- reports.
Dig deeper
What is Power BI Premium?
Get data for Power BI
Sample datasets for Power BI

Reports
A Power BI report is one or more pages of visualizations such as line charts, maps, and treemaps. Visualizations
are also called visuals. All of the visualizations in a report come from a single dataset. Reports can be created
from scratch within Power BI, can be imported with dashboards that colleagues share with you, or can be created
when you connect to datasets from Excel, Power BI Desktop, databases, SaaS applications, and apps. For example,
when you connect to an Excel workbook that contains Power View sheets, Power BI creates a report based on
those sheets. And when you connect to an SaaS application, Power BI imports a pre-built report.
There are two modes to view and interact with reports: Reading view and Editing view. Only the person who
created the report, coowners, and those granted permissions, have access to all of the exploring, designing,
building, and sharing capabilities of Editing View for that report. The people they share the report with can
explore and interact with the report in Reading View.
When you open a workspace, the associated reports are listed under the Reports tab. Each listed report
represents one or more pages of visualizations based on only one of the underlying datasets. To open a report,
select it.
When you open an app, you'll be presented with a dashboard. To access an underlying report, select a dashboard
tile (more on tiles later) that was pinned from a report. Keep in mind that not all tiles are pinned from reports, so
you may have to click a few tiles to find a report.
By default, the report opens in Reading view. Just select Edit report to open it in Editing view (if you have the
necessary permissions).
In the example below, I've selected the "Sales and marketing" app workspace and clicked the tab for Reports.

ONE report...
is contained in a single workspace.
can be associated with multiple dashboards within that workspace (tiles pinned from that one report can
appear on multiple dashboards).
can be created using data from one dataset. (the slight exception to this is that Power BI Desktop can
combine more than one dataset into a single report and that report can be imported into Power BI).

Dig deeper
Reports in Power BI service and Power BI Desktop
Reports in Power BI mobile apps

Dashboards
A dashboard is something you create in the Power BI service or something a colleague creates in the Power
BI service and shares with you. It is a single canvas that contains zero or more tiles and widgets. Each tile pinned
from a report or from Q&A displays a single visualization that was created from a dataset and pinned to the
dashboard. Entire report pages can also be pinned to a dashboard as a single tile. There are many ways to add
tiles to your dashboard; too many to be covered in this overview topic. To learn more, see Dashboard tiles in
Power BI.
Why do people create dashboards? Here are just some of the reasons:
to see, in one glance, all the information needed to make decisions.
to monitor the most-important information about your business.
to ensure all colleagues are on the same page, viewing and using the same information.
to monitor the health of a business or product or business unit or marketing campaign, etc.
to create a personalized view of a larger dashboard -- all the metrics that matter to you.
When you open a workspace, the associated dashboards are listed under the Dashboards tab. To open a
dashboard, select it. When you open an app, you'll be presented with a dashboard. Each dashboard represents a
customized view of some subset of the underlying dataset(s). If you own the dashboard, you'll also have edit
access to the underlying dataset(s) and reports. If the dashboard was shared with you, you'll be able to interact
with the dashboard and any underlying reports, but will not be able to save any changes.
There are many different ways that you, or a colleague, can share a dashboard. Power BI Pro is required for
sharing a dashboard and may be required for viewing a shared dashboard.
ONE dashboard...
is associated with a single workspace
can display visualizations from many different datasets
can display visualizations from many different reports
can display visualizations pinned from other tools (for example, Excel)

Dig deeper
Create a new blank dashboard and then get some data .
Duplicate a dashboard
Create a phone view of a dashboard

Workbooks
Workbooks are a special type of dataset. If you've read the Datasets section above, you know almost all you need
to know about workbooks. But you may be wondering why sometimes Power BI classifies an Excel workbook as a
Dataset and other times as a Workbook.
When you use Get data with Excel files, you have the option to Import or Connect to the file. When you choose
Connect, your workbook will appear in Power BI just like it would in Excel Online. But, unlike Excel Online, you’ll
have some great features to help you pin elements from your worksheets right to your dashboards.
You can’t edit your workbook in Power BI. But if you need to make some changes, you can click Edit, and then
choose to edit your workbook in Excel Online or open it in Excel on your computer. Any changes you make are
saved to the workbook on OneDrive.
Dig deeper
 Get data from Excel workbook files
Publish to Power BI from Excel

A dashboard in My Workspace
We've covered workspaces and building blocks. Let's bring it together and review the pieces that make up the
dashboard experience in the Power BI service.

1. Navigation pane (left nav)

Use the navigation pane to locate and move between your workspaces and the Power BI building blocks:
dashboards, reports, workbooks, and datasets.

Select Get Data to add datasets, reports, and dashboards to Power BI.

Expand and collapse the navigation pane with this icon .

Open or manage your favorite content by selecting Favorites.
View and open your most-recently visited content by selecting Recent
View, open, or delete an app by selecting Apps.
Did a colleague share content with you? Select Shared with me to search and sort that content to find what
you need.
 Display and open your workspaces by selecting Workspaces.
Single-click these elements:
an icon or heading to open in content view
a right arrow (>) to open a flyout menu for Favorites, Recent, and Workspaces.
a chevron icon to display the My Workspace scrollable list of dashboards, reports, workbooks, and datasets.
2. Canvas
Because we've opened a dashboard, the canvas area displays visualization tiles. If for example, we had opened the
report editor, the canvas area would display a report page.
Dashboards are composed of tiles. Tiles are created in report Editing view, Q&A, other dashboards, and can be
pinned from Excel, SSRS, and more. A special type of tile called a widget is added directly onto the dashboard.
The tiles that appear on a dashboard were specifically put there by a report creator/owner. The act of adding a tile
to a dashboard is called pinning.

For more information, see Dashboards (above).

3. Q&A question box
One way to explore your data is to ask a question and let Power BI Q&A give you an answer, in the form of a
visualization. Q&A can be used to add content to a dashboard or report.
Q&A looks for an answer in the dataset(s) connected to the dashboard. A connected dataset is one that has at
least one tile pinned to that dashboard.

As soon as you start to type your question, Q&A takes you to the Q&A page. As you type, Q&A helps you ask the
right question and find the best answer with rephrasings, autofill, suggestions, and more. When you have a
visualization (answer) you like, pin it to your dashboard. For more information, see Q&A in Power BI.
4. Icon buttons
The icons in the upper right corner are your resource for settings, notifications, downloads, getting help, and
providing feedback to the Power BI team. Select the double arrow to open the dashboard in Full screen mode.

5. Dashboard title (navigation path aka breadcrumbs)

It's not always easy to figure out which workspace and dashboard are active, so Power BI creates a navigation
path for you. In this example, we see the workspace (My workspace) and the dashboard title (Retail Analysis
Sample). If we opened a report, the name of the report would be appended to the end of the navigation path.
Each section of the path is an active hyperlink.
Notice the "C" icon after the dashboard title. This dashboard has a data classification tag of "confidential." The tag
identifies the sensitivity and security level of the data. If your Admin has turned on data classification, every
dashboard will have a default tag set. Dashboard owners should change the tag to match their dashboard's
proper security level.

6. Office 365 app launcher

With the app launcher, all your Office 365 apps are easily available with one click. From here, you can quickly
launch your email, documents, calendar, and more.

7. Power BI home
Selecting Power BI brings you back to your Power BI home.

8. Labeled icon buttons

This area of the screen contains additional options for interacting with the content (in this case, with the
dashboard). Besides the labeled icons you can see, selecting the ellipses reveals options for duplicating, printing,
refreshing the dashboard and more.

Next steps
What is Power BI?
Power BI videos
Report editor - take a tour
More questions? Try asking the Power BI Community
 Data sources for the Power BI service
1/24/2019 • 9 minutes to read • Edit Online

Data is at the heart of Power BI. Whenever you're exploring data, creating charts and dashboards, asking
questions with Q&A, all of those visualizations and answers you see are really getting their underlying
data from a dataset. But where does that dataset come from? Well, from a data source.
In this article, we're going to go over the different types of data sources you can connect to from the
Power BI service. Keep in-mind, there are many other types of data sources you can get data from, too.
But those sources might require first using Power BI Desktop or Excel's advanced data query and
modeling features. We'll go into more about that later. For now, let's look at the different types of data
sources you can connect to right from your Power BI service site.
You can get data from any of these data sources in Power BI by clicking My Workspace > Get Data.

Files

Excel (.xlsx, .xlsm) - Excel is unique in that a workbook can have both data you've entered into worksheets
yourself, and you can query and load data from external data sources by using Power Query (Get &
Transform in Excel 2016) or Power Pivot. You can import data that is in tables in worksheets (the data
must be in a table), or import data that is loaded into a data model. To learn more, see Get data from Excel.
Power BI Desktop (.pbix) - You can use Power BI Desktop to query and load data from external data
sources, extend your data model with measures and relationships, and create reports. You can import
your Power BI Desktop file into your Power BI site. Power BI Desktop is best for more advanced users
who have a good understanding of their data sources, data query and transformation, and data modeling
concepts. To learn more, see Connect to data in Power BI Desktop.
Comma-Separated Value (.csv) - Files are simple text files with rows of data. Each row can contain one
or more values, each separated by a comma. For example, a .csv containing name and address data can
have a number of rows where each row has values for first name, last name, street address, city, state, and
so on. You cannot import data into a .csv file, but many applications, like Excel, can save simple table data
as a .csv file.
For other file types like XML Table (.xml) or text (.txt) files, you can use Get & Transform to query,
transform, and load that data into an Excel or Power BI Desktop file first. You can then import the Excel or
Power BI Desktop file into Power BI.
Where you store your files makes a significant difference, too. OneDrive for Business provides the
greatest amount of flexibility and integration with Power BI. If you keep your files on your local drive,
that's ok, but if you need to refresh your data, a few extra steps are involved. More details are provided in
the linked articles.

Content packs

Content packs contain all of the data and reports you need already prepared for you. In Power BI, there
are two types of content packs; those from services like Google Analytics, Marketo, or Salesforce, and
those created and shared by other users in your organization.
Services - There are literally dozens of services with content packs for Power BI, and more are being
added all the time. Most services require you to have an account. To learn more, see Connect to services.
Organizational - If you and other users in your organization have a Power BI Pro account, you can
create, share, and use content packs. To learn more, see Organizational content packs.

Databases

Databases in the Cloud - From the Power BI service, you can connect live to Azure SQL Database,
Azure SQL Data Warehouse, Spark on Azure HD Insight, and SQL Server Analysis Services using
DirectQuery. Connections from Power BI to these databases are live, that is, when you've connected to
say an Azure SQL Database, and you begin exploring its data by creating reports in Power BI, anytime
you slice your data or add another field to a visualization, a query is made right to the database. To learn
more, see Azure and Power BI.
Databases on-premises - From the Power BI service, you can connect directly to SQL Server Analysis
Services Tabular model databases. A Power BI Enterprise gateway is required. If you're unsure how to
connect to your organization's tabular model database, check with your administrator or IT department.
To learn more, see SQL Server Analysis Tabular data in Power BI.
For other types of databases in your organization, you'll need to first use Power BI Desktop or Excel to
connect to, query, and load data into a data model. You can then import your file into Power BI where a
dataset is created. If you configure scheduled refresh, Power BI will use connection information from the
file along with refresh settings you configure to connect directly to the datasource and query for updates.
Those updates are then loaded into the dataset in Power BI. To learn more, see Connect to data in Power
BI Desktop.

What if my data comes from a different source?

There are literally hundreds of different data sources you can use with Power BI. But regardless of where
you get your data from, that data has to be in a format the Power BI service can use to create reports and
dashboards, answer questions with Q & A, and so on.
Some data sources already have their data in a format ready for the Power BI service, like content packs
from service providers like Google Analytics, and Twilio. SQL Server Analysis Services Tabular model
databases are ready, too. And you can connect live to databases in the cloud like Azure SQL Database and
Spark on HDInsight.
In other cases, it might be necessary to query and load the data you want into a file. For example, let's say
you have logistics data in a data warehouse database on a server in your organization. In the Power BI
service, you cannot connect directly to that database and begin exploring its data (unless it is a tabular
model database). You can, however, use Power BI Desktop or Excel to query and load that logistics data
into a data model you then save as a file. You can then import that file into Power BI where a dataset is
created.
You're probably thinking -But that logistics data on that database changes every day. How do I make sure
my dataset in Power BI is refreshed?- Connection information from the Power BI Desktop or Excel file is
imported into the dataset along with the data. If you configure scheduled refresh or do a manual refresh
on the dataset, Power BI will use the connection information from the dataset, along with a couple other
settings, to connect directly to the database, query for updates, and load those updates into the dataset. A
Power BI gateway will likely be required to secure any data transfer between your on-premises server and
Power BI. Any visualizations in reports and dashboards are refreshed automatically.
You see, just because you cannot connect to your data source right from the Power BI service doesn't
mean you can't get that data into Power BI. It just might take a few more steps and maybe some help
from your IT department. See Data sources in Power BI Desktop to learn more.

Some more details

You'll see the terms dataset and data source used a lot in Power BI. They are often use synonymously, but
they really are two different things, although they are related.
A dataset is automatically created in Power BI when you use Get Data to connect to and import data
from a content pack, file, or you connect to a live data source. A dataset contains information about the
data source, data source credentials, and in many cases, a subset of data copied from the data source. In
most cases, when you create visualizations in reports and dashboards, you're looking at data in the
dataset.
A data source is where the data in a dataset really comes from. For example, an online service like Google
Analytics or QuickBooks, a database in the cloud like Azure SQL Database, or a database or file on a local
computer or server in your own organization.
Data refresh
If you save your files on your local drive, or a drive somewhere in your organization, a Power BI gateway
might be required in-order to refresh the dataset in Power BI. And, the computer where the file is saved
must be on when a refresh happens. You can also re-import your file, or use Publish from Excel or Power
BI Desktop, but those are not automated processes.
If you save your files on OneDrive for Business or SharePoint - Team Sites, and then connect to or import
them into Power BI, your dataset, reports, and dashboard will always be up-to-date. Because both
OneDrive and Power BI are in the cloud, Power BI can connect directly to your saved file, about once
every hour, and check for updates. If any are found, the dataset and any visualizations are refreshed
automatically.
Content packs from services are automatically updated. In most cases, once a day. You can manually
refresh, but whether or not you'll see any updated data will depend on the service provider. Content packs
from others in your organization will depend on the data sources used and how the person who created
the content pack setup refresh.
Azure SQL Database, Azure SQL Data Warehouse, and Spark on Azure HDInsight are unique in that they
are data sources in the Cloud. Because the Power BI service is also in the cloud, Power BI can connect to
them live, using DirectQuery. What you see in Power BI is always in-sync and there's no need to set up
refresh.
SQL Server Analysis Services is unique in that when you connect to it from Power BI, it's a live connection
just like an Azure database in the cloud, but the database itself is on a server in your organization. This
type of connection requires a Power BI gateway, which is usually configured by an IT department.
Data refresh is a super important part of Power BI, and much too deep to cover here. If you want to get a
thorough understanding, be sure to check out Data Refresh in Power BI.

Considerations and Limitations

For all data sources used in the Power BI service, the following considerations and limitations apply. There
are other limitations that apply to specific features, but the following list applies to the Power BI service
overall:
Dataset size limit - there is a 1 GB limit for each dataset in the Power BI service.
Row limit - the maximum number of rows in your dataset (when not using DirectQuery) is 2 billion,
with three of those rows reserved (resulting in a usable maximum of 1,999,999,997 rows); the
maximum number of rows when using DirectQuery is 1 million rows.
Column limit - the maximum number of columns allowed in a dataset, across all tables in the dataset,
is 16,000 columns. This applies to the Power BI service and to datasets used in Power BI Desktop.
Power BI uses an internal row number column per table included in the dataset, which means the
maximum number of columns is 16,000 minus one for each table used in the dataset.
 Tour the report editor in Power BI
2/8/2019 • 6 minutes to read • Edit Online

The report editor in the Power BI service and the report editor in Power BI Desktop are similar. Typically you start
by creating reports in Power BI Desktop. Then you publish them to the Power BI service, where you can continue
modifying them. The Power BI service is also where you create the dashboards based on your reports.
After you create your dashboards and reports, you distribute them to your report consumers. Depending on how
you share them, your end users may be able to interact with them in Reading view in the Power BI service, but
not edit them. Read more about what report consumers can do in the Power BI service.
This video shows the report editor in Power BI Desktop. This article shows the report editor in the Power BI
service.
https://www.youtube.com/embed/IkJda4O7oGs
In the Power BI service, the report editor is only available in Editing View. To open a report in Editing view, you
must be a report owner or creator, or be a contributor to the app workspace that houses the report.
The Power BI report editor has three sections:
1. Fields, Visualizations, and Filters panes
2. top navigation bars
3. report canvas

1. The report editor panes

Three panes are visible when you first open a report: Visualizations, Filters, and Fields. The panes on the left side,
Visualizations and Filters, control what your visualizations look like -- type, colors, filtering, formatting. And the
pane on the right side, Fields, manages the underlying data being used in the visualizations.
The content displayed in the report editor varies by selections you make in the report canvas. For example, when
you select an individual visual:

The top of the Visualization pane identifies the type of

visual in use; in this example, a Clustered column
chart.

The bottom of the Visualization pane (you may have

to scroll down) displays the fields being used in the
visual. This chart is using FiscalMonth,
DistrictManager, and Total Sales Variance.

The Filters pane (you may have to scroll down)

displays any filters that have been applied.

The Fields pane lists the tables available and, if you

expand a table's name, the fields that make up that
table. Yellow font lets you know that at least one field
from that table is being used in the visualization.

To display the formatting pane, for the selected

visualization, select the paint roller icon.

To display the Analytics pane, select the

magnifying glass icon.

The Visualizations pane

Here is where you select a visualization type. The small pictures are called templates. In the image above, the
Clustered bar chart is selected. If you don't select a visualization type first, but instead start building a
visualization by selecting fields, Power BI will pick the visualization type for you. You can keep Power BI's
selection, or change the type by selecting a different template. Switch as many times as you need to find the
visualization type that best represents your data.
Manage the fields in your visual

The buckets (sometimes called wells) shown in this pane vary depending on what type of visualization you have
selected. For example, if you've selected a bar chart, you'll see buckets for: Values, Axis, and Legend. When you
select a field, or drag it onto the canvas, Power BI adds that field to one of the buckets. You can also drag fields
from the Fields list directly into the buckets. Some buckets are limited to certain types of data. For example,
Values won't accept non-numeric fields. So if you drag an employeename field into the Values bucket, Power
BI changes it to count of employeename.
Remove a field
To remove a field from the visualization, select the X to the right of the field name.

For more information, see Add visualizations to a Power BI report

Format your visuals
Select the paint roller icon to display the Format pane. The options available depend on the type of visualization
selected.
The formatting possibilities are almost endless. To learn more, explore on your own, or visit these articles:
Customizing visualization title, background, and legend
Color formatting
Customizing X-axis and Y -axis properties
Add analytics to your visualizations
Select the magnifying glass icon to display the Analytics pane. The options available depend on the type of
visualization selected.

With the Analytics pane in the Power BI service, you can add dynamic reference lines to visualizations, and
provide focus for important trends or insights. To learn more, see Analytics pane in the Power BI service or
Analytics pane in Power BI Desktop.

The Filters pane

Use the Filters pane to view, set, and modify persistent filters to your reports at the page, report, drillthrough, and
visual-level. Yes, you can do ad-hoc filtering on report pages and visuals by selecting elements of the visuals or by
using tools like slicers, but by using the Filters pane the state of the filters is saved with the report.
The Filters pane has one other powerful feature - the ability to filter using a field that is not already being used
in one of the visuals in your report. Let me explain. When you create a report page, Power BI automatically
adds all the fields you use in your visualizations to the Visual level filters area of the Filters pane. But, if you want
to set a visual, page, drillthrough, or report filter using a field that is not currently used in a visualization, just drag
it to one of the Filters buckets.

For more information, see Add a filter to a report.

A new filter experience is currently in preview. In the new filters, you can format them to look like the report itself.
You can also lock filters or hide them from your report consumers.

Read more about the new filter experience.

The Fields pane

The Fields pane displays the tables and fields that exist in your data and are available for you to use to create
visualizations.

Drag a field onto the page to start a new visualization.

You can also drag a field onto an existing visualization
to add the field to that visualization.

When you add a checkmark next to a field, Power BI

adds that field to the active (or new) visualization. And
it also decides which bucket to place that field into.
For example, should the field be used a legend, axis, or
value? Power BI makes a best-guess and you can
move it from that bucket to another if necessary.

Either way, each selected field is added to the

Visualizations pane in the report editor.

NOTE: If you're using Power BI Desktop, you'll also have options to show/hide fields, add calculations etc.
What do the field icons mean?
∑ Aggregates An aggregate is a numeric value that will be summed or averaged, for example. Aggregates are
imported with the data (defined in the data model your report is based on). For more information, see
Aggregates in Power BI reports.

Calculated measures (also called calculated fields)

Each calculated field has its own hard-coded formula. You can’t change the calculation, for example, if it’s a sum, it
can only be a sum. For more information, read Understanding measures
Unique fields
Fields with this icon were imported from Excel and are set to show all values, even if they have duplicates. For
example, your data might have two records for people named 'John Smith', and each will be treated as unique --
they won't be summed.

Geography fields
Location fields can be used to create map visualizations.
Hierarchy
Select the arrow to reveal the fields that make up the hierarchy.

2. The top navigation bar

The actions available from the top navigation bar are numerous; with new actions being added all the time. For
information about a particular action, use the Power BI Documentation Table of Contents or Search box.

3. The report canvas

The report canvas is where your work displays. When you use the Fields, Filters, and Visualizations panes to
create visuals, they are built and displayed on your report canvas. Each tab at the bottom of the canvas represents
a page in the report. Select a tab to open that page.

Next steps
Create a report
More about reports in the Power BI service, Power BI Desktop, and Power BI mobile apps.
Basic concepts for Power BI designers
More questions? Try the Power BI Community
 Organize work in the new workspaces (preview) in
Power BI
1/14/2019 • 6 minutes to read • Edit Online

Workspaces are places to collaborate with colleagues to create collections of dashboards and reports. Then you
can bundle those collections into apps and distribute them to your whole organization or to specific people or
groups. Power BI is introducing a new workspace experience as a preview.

With the new workspaces preview, you can now:

Assign workspace roles to user groups: security groups, distribution lists, Office 365 groups, and individuals.
Create a workspace in Power BI without creating an Office 365 group.
Use more granular workspaces roles for more flexible permissions management in a workspace.
Read about how to create one of the new workspaces.
When you create one of the new workspaces, you're not creating an underlying, associated Office 365 group. All
the workspace administration is in Power BI, not in Office 365. You can still add an Office 365 group to the
workspace to continue managing user access to content through Office 365 groups. However, you can additionally
use security groups, distribution lists, and add individuals directly within Power BI, giving you a flexible way to
manage workspace access. Because workspace administration is now in Power BI, Power BI admins decide who in
an organization can create workspaces. In Workspace settings in the admin portal, admins can allow everybody
or nobody in an organization to create workspaces. They can also limit creation to members of specific security
groups.

Read more about the Power BI admin portal.

Roll out new workspaces
During the preview period, old and new workspaces can coexist side by side, and you can create either. When the
preview for new workspaces ends and they're generally available, old workspaces can still exist for a time. You
won't be able to create them, and you'll need to prepare to migrate your workspaces to the new workspaces
infrastructure. Don’t worry, you'll have several months to complete migration.

Roles in the new workspaces

You add user groups or individuals to the new workspaces as members, contributors, or admins. Everyone in a
user group gets the role you’ve defined. If an individual is in several user groups, they get highest level of
permission provided by the role.
Everyone you add to a workspace needs a Power BI Pro license. In the workspace, these users can all collaborate
on dashboards and reports that you plan to publish to a wider audience, or even to your entire organization. If you
want to distribute content to others inside your organization, you can assign Power BI Pro licenses to those users
or place the workspace in a Power BI Premium capacity.
Roles let you manage who can do what in a workspace, so teams can collaborate. New workspaces allow you to
assign roles to individuals, and to user groups: security groups, Office 365 groups, and distribution lists.
When you assign roles to a user group, the individuals in the group have access to content. If you nest user groups,
all the contained users have permission. A user who's in several user groups with different roles gets the highest
level of permission granted them.
The new workspaces offer three roles: admins, members, and contributors.
Admins can:
Update and delete the workspace.
Add/remove people, including other admins.
Do everything members can do.
Members can:
Add members or others with lower permissions.
Publish and update an app.
Share an item or share an app.
Allow others to reshare items.
Do everything contributors can do.
Contributors can:
Create, edit, and delete content in the workspace.
Publish reports to the workspace, delete content.
Can’t give new people access to content. They can’t share new content, but can share with someone with whom
the workspace, item, or app is already shared.
Can’t modify the members of the group.
We’re building Request Access workflows throughout the service so users who don’t have access can request it.
Request Access workflows currently exist for dashboards, reports, and apps.

Convert old workspaces to new workspaces

During the preview period, you can't automatically convert your old workspaces to new ones. You can however
create a new workspace and publish your content to the new location.
When the new workspaces are generally available (GA), you can opt in to migrate the old ones automatically. At
some point after GA, you'll have to migrate them.

How are the new workspaces different from current workspaces?

With the new workspaces, we're redesigning some features. Here are the changes you can expect to be permanent
along with the preview.
Creating workspaces won't create corresponding entities in Office 365 like current workspaces do. (You can still
add an Office 365 group to your workspace by assigning it a role).
In current workspaces, you can add only individuals to the members and admin lists. In the new workspaces,
you can add multiple AD security groups, distribution lists, or Office 365 groups to these lists to allow for easier
user management.
You can create an organizational content pack from a current workspace. You can't create one from the new
workspaces.
You can consume an organizational content pack from a current workspace. You can’t consume one from the
new workspaces.
During the preview period, some features aren't enabled yet for new workspaces. See the next section, Planned
new workspace features, for details.

Limitations and considerations

Limitations to be aware of:
Workspaces can contain a maximum of 1,000 datasets, or 1,000 reports per dataset.
A person with a Power BI Pro license can be a member of a maximum 250 workspaces.

Planned new workspace preview features

As we launch the preview, we're still developing some other new workspace preview features, but they aren't
available yet:
No Leave workspace button.
Usage metrics aren't supported yet.
How Premium works: You can assign and create workspaces in a Premium capacity, but to move a workspace
between capacities, go to the workspace’s settings.
SharePoint web part embedding isn't supported yet.
No OneDrive button for Office 365 groups in Get Data/Files.

Workspace features that work differently

Some features work differently from current workspaces in the new workspaces. These differences are intentional,
based on feedback we’ve received from customers, and will enable a more flexible approach to collaboration with
workspaces:
Members can or can't reshare: replaced by the Contributor role
Read-only workspaces: Instead of granting users read-only access to a workspace, you'll assign users to a
forthcoming Viewer role, which allows similar read-only access to the content in a workspace.

Known issues
Because this feature is a preview, there are some limitations that you should be aware of. The following issues are
known, and fixes are under development:
 Free users or user groups added as recipients of subscriptions to emails may not receive the emails, though
they should. The issue occurs when one of the new workspaces is in a Premium capacity, but the My Workspace
of the user creating the subscription isn't in a Premium capacity. If the My Workspace is in a Premium capacity,
then free users and user groups will receive the emails.
After a workspace is moved from a Premium capacity to shared capacity, in some cases, free users and user
groups will continue to receive emails, though they shouldn't. The issue occurs when the My Workspace of the
user creating the subscription is in a Premium capacity.

Next steps
Create the new workspaces (preview ) in Power BI
Create the current workspaces
Install and use apps in Power BI
Questions? Try asking the Power BI Community
 Ways to share your work in Power BI
1/14/2019 • 6 minutes to read • Edit Online

You've created dashboards and reports. Maybe you collaborated on them with your coworkers, too. Now you
want others to have access to them. What's the best way to distribute them?
In this article, we compare these options for collaborating and sharing in Power BI:
Collaborating with coworkers to create meaningful reports and dashboards in workspaces.
Bundling those dashboards and reports into apps and publishing them to a larger group or your whole
organization.
Sharing dashboards or reports with a few people, from the service or the Power BI mobile apps.
Printing reports.
Embed reports in secure portals or public websites.
No matter which option you choose, to share a dashboard you need a Power BI Pro license, or the content needs
to be in a Premium capacity. License requirements vary for the colleagues who view your dashboards, depending
on the option you choose. The following sections spell out details.

Apps in the Power BI service

Collaborate with coworkers in a workspace

When teams work together, they need access to the same documents so they can quickly collaborate. Workspaces
in Power BI provide the place where teams come together to share the ownership and management of
dashboards, reports, datasets, and workbooks that matter to them. Sometimes Power BI users organize their
workspaces based on organizational structures, other times they create them for specific projects. Still other
organizations use several workspaces to store different versions of reports or dashboards they use.
Workspaces provide roles that determine what permissions your coworkers have. You can use those roles to
determine who can manage the entire workspace, or provide content into it.
Some users naturally put content in their My Workspace and share it out. Workspaces are better for collaboration
than My Workspace because they provide co-ownership of content. You and your entire team can easily make
updates or give others access. My Workspace is best used by individuals for one-off or personal content.
Let’s imagine you have a finished dashboard you need to share with your colleagues. What's the best way to give
them access to the dashboard? The answer depends on a number of factors. If a specific colleague needs to own
the dashboard and keep it up-to-date, or needs access to all the content in the workspace, it may be best to add
them to the workspace. If your colleague just needs to see that dashboard and not all the content in the
workspace, you again can choose from a set of alternatives. If the dashboard is part of a bigger set of content you
need to distribute to many colleagues, then publishing an app is likely the best choice. However, if the colleague
just needs that one dashboard, then sharing the dashboard could be the best path forward.
Read more about creating workspaces.
Did you know? Power BI is previewing a new workspace experience. Read Create the new workspaces (preview )
to see how workspaces will change in the future.

Distribute data and insights by creating an app

Say you want to distribute your dashboard to a broad audience. You and your coworkers have created a
workspace, then created and refined dashboards, reports, and datasets in the workspace. Now you select the
dashboards and reports you want and publish them as an app either to a group or to your whole organization.

Apps are easy to find and install in the Power BI service ( https://powerbi.com). You can send your business users
a direct link to the app, or they can search for it in AppSource. If your Power BI administrator gives you
permissions, you can install an app automatically in your coworkers' Power BI accounts. Read more about
publishing your apps.
After they install an app, they can view it in their browser or mobile device.
For your users to view your app, either they need to have a Power BI Pro license, too, or the app needs to be
stored in a Power BI Premium capacity. Read What is Power BI Premium? for details.
You can publish apps to those outside your organization, too. They can view and interact with the app content, but
can’t share it with others.

Share dashboards and reports

Let's say you've finalized a dashboard and a report in your own My Workspace or in a workspace and you want a
few other people to have access to it. One way to get it to them is to share it.

You need a Power BI Pro license to share your content, and those you share it with do too, or the content needs to
be in a workspace in a Premium capacity. When you share a dashboard or report, recipients can view it and
interact with it, but can't edit it. They see the same data that you see in the dashboard and reports unless row -
level security (RLS ) is applied to the underlying dataset. The coworkers you share it with can share with their
coworkers, if you allow them to.
You can share with people outside your organization, too. They can view and interact with the dashboard or
report too, but can't share it.
More about sharing dashboards and reports from the Power BI service. You can also add a filter to a link and
share a filtered view of your report.

Annotate and share from the Power BI mobile apps

In the Power BI mobile apps for iOS and Android devices, you can annotate a tile, report, or visual and then share
it with anyone via email.
You're sharing a snapshot of the tile, report, or visual, and your recipients see it exactly as it was when you sent
the mail. The mail also contains a link to the dashboard or report. If they have a Power BI Pro license, or the
content is in a Premium capacity, and you've shared the object with them already, they can open it. You can send
snapshots of tiles to anyone not just coworkers in the same email domain.
More about annotating and sharing tiles, reports, and visuals from the iOS and Android mobile apps.
You can also share a snapshot of a tile from the Power BI app for Windows 10 devices.

Print or save as PDF or other static file

You can print or save as PDF (or other static file format) an entire dashboard, dashboard tile, report page, or
visualization from the Power BI service. Reports can only be printed one page at a time -- you can't print the
entire report at once. More about printing or saving as a static file.

Embed reports in secure portals or public websites

You can embed Power BI reports in portals or websites where your users expect to see them.
The Embed in SharePoint Online and the Embed option in the Power BI service allows you to embed reports
for your internal users securely. The Embed in SharePoint Online option works with the Power BI web part for
SharePoint Online and provides a single sign-on experience with control over how the report is embedded. The
Embed option works with any portal or website that supports embedding content using a URL or an iFrame.
Whichever option you choose, they both ensure that all permissions and data security are enforced before a user
can see content. The person viewing the report needs the appropriate license. More about Embed in SharePoint
Online and the Embed option in Power BI.
With Publish to web, you can publish Power BI reports to the whole Internet by embedding interactive
visualizations in blog posts, websites, social media, and other online communications on any device. Anyone on
the Internet can view your reports, and you have no control over who can see what you've published. They don't
need a Power BI license. Publishing to the web is available only for reports that you can edit. You can't publish
reports to the web if they're shared with you or if they're in an app. More about publishing to the web.

WARNING
Use Publish to web only to share content publicly, not for internal sharing.

Next steps
Share dashboards with coworkers and others
Create and publish an app in Power BI
Embed report in a secure portal or website
Have feedback? Go to the Power BI Community site with your suggestions.
More questions? Try the Power BI Community
 Data refresh in Power BI
2/26/2019 • 17 minutes to read • Edit Online

Making sure you’re always getting the latest data is often critical in making the right decisions. You’ve probably
already used Get Data in Power BI to connect to and upload some data, created some reports and a dashboard.
Now, you want to make sure your data really is the latest and greatest.
In many cases, you don’t need to do anything at all. Some data, like from a Salesforce or Marketo content pack is
automatically refreshed for you. If your connection makes use of a live connection or DirectQuery, the data will
be update to date. But, in other cases, like with an Excel workbook or Power BI Desktop file that connects to an
external online or on-premises data source, you’ll need to refresh manually or setup a refresh schedule so Power
BI can refresh the data in your reports and dashboards for you.
This article, along with a few others, are meant to help you understand how data refresh in Power BI really
works, whether or not you need to setup a refresh schedule, and what needs to be in-place to refresh your data
successfully.

Understanding data refresh

Before setting up refresh, it’s important to understand what it is you’re refreshing and where you’re getting your
data.
A data source is where the data you explore in your reports and dashboards really comes from; for example, an
online service like Google Analytics or QuickBooks, a database in the cloud like Azure SQL Database, or a
database or file on a local computer or server in your own organization. These are all data sources. The type of
data source determines how data from it is refreshed. We’ll go into refresh for each type of data source a little
later in the What can be refreshed? section.
A dataset is automatically created in Power BI when you use Get Data to connect to and upload data from a
content pack, file, or you connect to a live data source. In Power BI Desktop and Excel 2016, you can also publish
your file right to the Power BI service, which is just like using Get Data.
In each case, a dataset is created and appears in the My Workspace, or Group, containers in the Power BI service.
When you select the ellipse (...) for a dataset, you can explore the data in a report, edit settings, and setup
refresh.

A dataset can get data from one or more data sources. For example, you can use Power BI Desktop to get data
from a SQL Database in your organization, and get other data from an OData feed online. Then, when you
publish the file to Power BI, a single dataset is created, but it will have data sources for both the SQL Database
and the OData feed.
A dataset contains information about the data sources, data source credentials, and in most cases, a sub-set of
data copied from the data source. When you create visualizations in reports and dashboards, you’re looking at
data in the dataset, or in the case of a live connection like Azure SQL Database, the dataset defines the data you
see right from the data source. For a live connection to Analysis Services, the dataset definition comes from
Analysis Services directly.

When you refresh data, you are updating the data in the dataset that is stored in Power BI from your data
source. This refresh is a full refresh and not incremental.

Whenever you refresh data in a dataset, whether by using Refresh Now or by setting up a refresh schedule,
Power BI uses information in the dataset to connect to the data sources defined for it, query for updated data,
and then loads the updated data into the dataset. Any visualizations in your reports or dashboards based on the
data are updated automatically.
Before we go any further, there’s something else that's very important to understand:

Regardless of how often you refresh the dataset, or how often you look at live data, it is the data at the data
source that must be up -to -date first.

Most organizations process their data once a day, usually in the evening. If you schedule refresh for a dataset
created from a Power BI Desktop file that connects to an on-premises database, and your IT department runs
processing on that SQL database once in the evening, then you only need to setup scheduled refresh to run
once-a-day. For example, after processing on the database happens, but before you come into work. Of course,
this isn’t always the case. Power BI provides many ways to connect to data sources that are updated frequently
or even real-time.

Types of refresh
There are four main types of refresh that happen within Power BI. Package refresh, model/data refresh, tile
refresh and visual container refresh.
Package refresh
This synchronizes your Power BI Desktop, or Excel, file between the Power BI service and OneDrive, or
SharePoint Online. This does not pull data from the original data source. The dataset in Power BI will only be
updated with what is in the file within OneDrive, or SharePoint Online.

Model/data refresh
This is referring to refreshing the dataset, within the Power BI service, with data from the original data source.
This is done by either using scheduled refresh, or refresh now. This requires a gateway for on-premises data
sources.
Tile refresh
Tile refresh updates the cache for tile visuals, on the dashboard, once data changes. This happens about every
fifteen minutes. You can also force a tile refresh by selecting the ellipsis (...) in the upper right of a dashboard
and selecting Refresh dashboard tiles.
For details around common tile refresh errors, see Troubleshooting tile errors.
Visual container refresh
Refreshing the visual container updates the cached report visuals, within a report, once the data changes.

What can be refreshed?

In Power BI, you’ll typically use Get Data to import data from a file on a local drive, OneDrive or SharePoint
Online, publish a report from Power BI Desktop, or connect directly to a database in the cloud in your own
organization. Just about any data in Power BI can be refreshed, but whether or not you need to depends on how
your dataset was created from and the data sources it connects to. Let’s look at how each of these refresh data.
Before we go further, here are some important definitions to understand:
Automatic refresh - This means no user configuration is necessary in order for the dataset to be refreshed on a
regular basis. Data refresh settings are configured for you by Power BI. For online service providers, refresh
usually occurs once-a-day. For files loaded from OneDrive, automatic refresh occurs about every hour for data
that does not come from an external data source. While you can configure different schedule refresh settings and
manually refresh, you probably don’t need to.
User configured manual or scheduled refresh – This means you can manually refresh a dataset by using
Refresh Now or setup a refresh schedule by using Schedule Refresh in a dataset’s settings. This type of refresh is
required for Power BI Desktop files and Excel workbooks that connect to external online and on-premises data
sources.

NOTE
When you configure a time for scheduled refresh, there can be a delay of up to one hour before it begins.

Live/DirectQuery – This means there is a live connection between Power BI and the data source. For on-
premises data sources, Admins will need to have a data source configured within an enterprise gateway, but user
interaction may not be needed.

NOTE
To enhance performance, dashboards with data connected using DirectQuery are automatically updated. You can also
manually refresh a tile at any time, by using the More menu on the tile.

Local files and files on OneDrive or SharePoint Online

Data refresh is supported for Power BI Desktop files and Excel workbooks that connect to external online or on-
premises data sources. This will only refresh the data for the dataset within the Power BI service. It will not
update your local file.
Keeping your files on OneDrive, or SharePoint Online, and connecting to them from Power BI, provides a great
amount of flexibility. But with all that flexibility, it also makes it one of the most challenging to understand.
Scheduled refresh for files stored in OneDrive, or SharePoint Online, are different from package refresh. You can
learn more in the Types of refresh section.
Power BI Desktop file
USER CONFIGURED MANUAL
DATA SOURCE AUTOMATIC REFRESH OR SCHEDULED REFRESH GATEWAY REQUIRED

Get Data (on the ribbon) is No Yes No (see below)

used to connect to and
query data from any listed
online data source.

Get Data is used to connect Yes No Yes

to and explore a live
Analysis Services database.

Get Data is used to connect Yes No Yes

to and explore a supported
on-premises DirectQuery
data source.

Get Data is used to connect Yes Yes No

to and query data from an
Azure SQL Database, Azure
SQL Data Warehouse, Azure
HDInsight Spark.

Get Data is used to connect No Yes Yes

to and query data from any
listed on-premises data
source except for Hadoop
file (HDFS) and Microsoft
Exchange.

NOTE
If you are using the Web.Page function, you do need a gateway if you have republished the dataset or your report after
November 18th, 2016.

For details, see Refresh a dataset created from a Power BI Desktop file on OneDrive.
Excel workbook
USER CONFIGURED MANUAL
DATA SOURCE AUTOMATIC REFRESH OR SCHEDULED REFRESH GATEWAY REQUIRED

Tables of data in a Yes, hourly Manual only No

worksheet not loaded into (OneDrive/SharePoint (OneDrive/SharePoint
the Excel data model. Online only) Online only)

Tables of data in a Yes, hourly Manual only No

worksheet linked to a table (OneDrive/SharePoint (OneDrive/SharePoint
in the Excel data model Online only) Online only)
(linked tables).
 USER CONFIGURED MANUAL
DATA SOURCE AUTOMATIC REFRESH OR SCHEDULED REFRESH GATEWAY REQUIRED

Power Query* is used to No Yes No

connect to and query data
from any listed online data
source and load data into
the Excel data model.

Power Query* is used to No Yes Yes

connect to and query data
from any listed on-premises
data source except for
Hadoop file (HDFS) and
Microsoft Exchange and
load data into the Excel data
model.

Power Pivot is used to No Yes No

connect to and query data
from any listed online data
source and load data into
the Excel data model.

Power Pivot is used to No Yes Yes

connect to and query data
from any listed on-premises
data source and load data
into the Excel data model.

* Power Query is known as Get & Transform Data in Excel 2016.

For more detailed information, see Refresh a dataset created from an Excel workbook on OneDrive.
Comma separated value (.csv) file on OneDrive or SharePoint Online
USER CONFIGURED MANUAL
DATA SOURCE AUTOMATIC REFRESH OR SCHEDULED REFRESH GATEWAY REQUIRED

Simple comma separated Yes, hourly Manual only No

value

For more detailed information, see Refresh a dataset created from a comma separated value (.csv) file on
OneDrive.

Content packs
There are two types of content packs in Power BI:
Content packs from online services: like Adobe Analytics, SalesForce, and Dynamics CRM Online. Datasets
created from online services are refreshed automatically once a day. While it’s probably not necessary, you can
manually refresh or setup a refresh schedule. Because online services are in the cloud, a gateway is not required.
Organizational content packs: created and shared by users in your own organization. Content pack
consumers cannot setup a refresh schedule or manually refresh. Only the content pack creator can setup refresh
for the datasets in the content pack. Refresh settings are inherited with the dataset.
Content packs from online services
 USER CONFIGURED MANUAL
DATA SOURCE AUTOMATIC REFRESH OR SCHEDULED REFRESH GATEWAY REQUIRED

Online services in Get Data Yes Yes No

> Services

Organizational content packs

Refresh capabilities for a dataset included within an organization content pack depends on the dataset. See
information above in relation to local files, OneDrive or SharePoint Online.
To learn more, see Introduction to organizational content packs.

Live connections and DirectQuery to on-premises data sources

With the On-premises data gateway, you can issue queries from Power BI to your on-premises data sources.
When you interact with a visualization, queries are sent from Power BI directly to the database. Updated data is
then returned and visualizations are updated. Because there is a direct connection between Power BI and the
database, there is no need to schedule refresh.
When connecting to a SQL Service Analysis Services (SSAS ) data source using a Live connection, unlike
DirectQuery, the Live connection to a SSAS source can run against the cache, even upon loading a report. This
behavior improves load performance for the report. You can request the latest data from the SSAS data source
by using the refresh button. Owners of SSAS data sources can configure the scheduled cache refresh frequency
for the dataset to ensure reports are as up to date as they require.
When you configure a data source with the On-premises data gateway, you can use that data source as the
scheduled refresh option. This would be instead of using the personal gateway.

NOTE
If your dataset is configured for a live or DirectQuery connection, datasets are refreshed approximately each hour or when
interaction with the data occurs. You can manually adjust the refresh frequency in the Scheduled cache refresh option in
the Power BI service.

USER CONFIGURED MANUAL

DATA SOURCE LIVE/DIRECTQUERY OR SCHEDULED REFRESH GATEWAY REQUIRED

Analysis Services Tabular Yes Yes Yes

Analysis Services Yes Yes Yes

Multidimensional

SQL Server Yes Yes Yes

SAP HANA Yes Yes Yes

Oracle Yes Yes Yes

Teradata Yes Yes Yes

To learn more, see On-premises data gateway

Databases in the cloud

With DirectQuery, there is a direct connection between Power BI and the database in the cloud. When you
interact with a visualization, queries are sent from Power BI directly to the database. Updated data is then
returned and visualizations are updated. And, because both the Power BI service and the data source are in the
cloud, there is no need for a Personal Gateway.
If there is no user interaction in a visualization, data is refreshed automatically approximately every hour. You can
change that refresh frequency using the Scheduled cache refresh option, and set the refresh frequency.
To set the frequency, select the gear icon in the upper right corner of the Power BI service, then select Settings.

The Settings page appears, where you can select the dataset for which you want to adjust the frequency. On that
page, select the Datasets tab along the top.

Select the dataset, and in the right pane you'll see a collection of options for that dataset. For the
DirectQuery/Live connection, you can set the refresh frequency from 15 minutes to weekly using the associated
drop-down menu, as shown in the following image.
 USER CONFIGURED MANUAL
DATA SOURCE LIVE/DIRECTQUERY OR SCHEDULED REFRESH GATEWAY REQUIRED

SQL Azure Data Warehouse Yes Yes No

Spark on HDInsight Yes Yes No

To learn more, see Azure and Power BI.

Real-time dashboards
Real-time dashboards use the Microsoft Power BI REST API, or Microsoft Stream Analytics, to make sure the
data is up-to-date. Since real time dashboards do not require users to configure refresh, they are outside the
scope of this article.

USER CONFIGURED MANUAL

DATA SOURCE AUTOMATIC OR SCHEDULED REFRESH GATEWAY REQUIRED

Custom apps developed Yes, live streaming No No

with the Power BI Rest API
or Microsoft Stream
Analytics

Configure scheduled refresh

To learn how to configure scheduled refresh, see Configure scheduled refresh

Common data refresh scenarios

Sometimes the best way to learn about data refresh in Power BI is to look at examples. Here are some of the
more common data refresh scenarios:
Excel workbook with tables of data
You have an Excel workbook with several tables of data, but none of them are loaded into the Excel data model.
You use Get Data to upload the workbook file from your local drive into Power BI, and create a dashboard. But,
now you’ve made some changes to a couple of the workbook’s tables on your local drive, and you want to
update your dashboard in Power BI with the new data.
Unfortunately, refresh is not supported in this scenario. In order to refresh the dataset for your dashboard, you
will have to re-upload the workbook. However, there’s a really great solution: Put your workbook file on
OneDrive, or SharePoint Online!
When you connect to a file on OneDrive, or SharePoint Online, your reports and dashboards will show data as it
is in the file. In this case, your Excel workbook. Power BI automatically checks the file, about every hour, for
updates. If you make changes to the workbook (stored in OneDrive or SharePoint Online), those changes are
reflected in your dashboard and reports within an hour. You don’t need to setup refresh at all. However, if you
need to see your updates in Power BI immediately, you can manually refresh the dataset by using Refresh Now.
To learn more, see Excel data in Power BI, or Refresh a dataset created from an Excel workbook on OneDrive.
Excel workbook connects to a SQL database in your company
Let’s say you have an Excel workbook named SalesReport.xlsx on your local computer. Power Query in Excel was
used to connect to a SQL database on a server in your company and query for sales data that is loaded into the
data model. Each morning, you open the workbook and hit Refresh to update your PivotTables.
Now you want to explore your sales data in Power BI, so you use Get Data to connect to and upload the
SalesReport.xlsx workbook from your local drive.
In this case, you can manually refresh the data in the SalesReport.xlsx dataset or setup a refresh schedule.
Because the data really comes from the SQL database in your company, you’ll need to download and install a
gateway. Once you’ve installed and configured the gateway, you’ll need to go into the SalesReport dataset’s
settings and sign in to the data source; but you’ll only have to do this once. You can then setup a refresh schedule
so Power BI automatically connects to the SQL database and gets updated data. Your reports and dashboards
will also be updated automatically.

NOTE
This will only update the data within the dataset in the Power BI service. Your local file will not be updated as part of the
refresh.

To learn more, see Excel data in Power BI, Power BI Gateway - Personal, On-premises data gateway, Refresh a
dataset created from an Excel workbook on a local drive.
Power BI Desktop file with data from an OData feed
In this case, you use Get Data in Power BI Desktop to connect to and import census data from an OData feed.
You create several reports in Power BI Desktop, then name the file WACensus and save it on a share in your
company. You then publish the file to the Power BI service.
In this case, you can manually refresh the data in the WACensus dataset or setup a refresh schedule. Because the
data in the data source comes from an OData feed online, you do not need to install a gateway, but you will need
to go into the WACensus dataset’s settings and sign in to the OData data source. You can then setup a refresh
schedule so Power BI automatically connects to the OData feed and gets updated data. Your reports and
dashboards will also be updated automatically.
To learn more, see Publish from Power BI Desktop, Refresh a dataset created from a Power BI Desktop file on a
local drive, Refresh a dataset created from a Power BI Desktop file on OneDrive.
Shared content pack from another user in your organization
You’ve connected to an organizational content pack. It includes a dashboard, several reports, and a dataset.
In this scenario, you cannot setup refresh for the dataset. The data analyst who created the content pack is
responsible for making sure the dataset is refreshed, depending on the data sources used.
If your dashboards and reports from the content pack aren’t updating, you’ll want to talk to the data analyst who
created the content pack.
To learn more, see Introduction to organizational content packs, Work with organizational content packs.
Content pack from an online service provider like Salesforce
In Power BI you used Get Data to connect to and import your data from an online service provider like
Salesforce. Well, not much to do here. Your Salesforce data set is automatically scheduled to refresh once a day.
Like most online service providers, Salesforce updates data once a day, usually at night. You can manually
refresh your Salesforce dataset, or setup a refresh schedule, but it’s not necessary because Power BI will
automatically refresh the dataset and your reports and dashboards will be updated too.
To learn more, see Salesforce content pack for Power BI.

Troubleshooting
When things go wrong, it’s usually because Power BI can’t sign into data sources, or the dataset connects to an
on-premises data source and the gateway is offline. Make sure Power BI can sign into data sources. If a
password you use to sign into a data source changes, or Power BI gets signed out from a data source, be sure to
try signing into your data sources again in Data Source Credentials.
For more information about troubleshooting, see Tools for troubleshooting refresh issues and Troubleshooting
refresh scenarios.

Next steps
Tools for troubleshooting refresh issues
Troubleshooting refresh scenarios
Power BI Gateway - Personal
On-premises data gateway
More questions? Try asking the Power BI Community
 Monitor usage metrics for Power BI dashboards and
reports
3/18/2019 • 11 minutes to read • Edit Online

If you create dashboards and reports, usage metrics help you understand their impact. When you run either
dashboard usage metrics or report usage metrics, you discover how those dashboards and reports are being used
throughout your organization; what is being used, by whom, and for what purpose.

NOTE
Usage metrics track usage of reports that are embedded in SharePoint Online. However, usage metrics don't track embedding
of dashboards and reports via the “user owns credentials” or “app owns credentials” flow. Usage metrics also don't track
usage of reports embedding via publish to web.

These usage metrics reports are read-only. However, you can personalize a usage metrics report by using "Save
as." This creates a brand new dataset and converts the read-only report to a full-featured Power BI report that you
can edit. Not only does the personalized report contain metrics for the selected dashboard or report, but by
removing the default filter, you now have access to usage metrics for all dashboards or all reports in the selected
workspace. And you can even see the names of your end users.

Why are usage metrics important to me?

Knowing how your content is being used helps you demonstrate your impact and prioritize your efforts. Your usage
metrics may show that one of your reports is used daily by a huge segment of the organization and it may show
that a dashboard you created isn't being viewed at all. This type of feedback is invaluable in guiding your work
efforts.
Running usage metrics reports is only available in Power BI service. However, if you save a usage metrics report or
pin it to a dashboard, you can open and interact with that report on mobile devices.
Prerequisites
 The usage metrics feature captures usage information from all users, regardless of the license they're assigned.
However, a Power BI Pro license is required to run and access the usage metrics data.
Usage metrics are provided on dashboards or reports in the selected workspace. To access usage metrics for a
particular dashboard or report, you must:
• Have edit access to that dashboard or report • Have a Pro license

About the Usage Metrics report

When you select Usage metrics or the icon , Power BI generates a pre-built report with usage metrics for that
content for the last 90 days. The report looks similar to the Power BI reports you're already familiar with, but it's
designed to be informational -- not interactive. You’ll be able to slice based on how your end users received access,
whether they were accessing via the web or mobile app, etc. As your dashboards and reports evolve, so too will the
usage metrics report, which updates every day with new data.
Usage metrics reports won't show up in Recent, Workspaces, Favorites, or other content lists. They cannot be
added to an app. If you pin a tile from a usage metrics report to a dashboard, that dashboard cannot be added to an
app or content pack.
To dig down into the report data, or to build your own reports against the dataset, use Save as (see Save the Usage
Metrics report as a full-featured Power BI report).

Open a Usage Metrics report for a dashboard or report

1. Start in the workspace that contains the dashboard or report.
2. From either the workspace content list or from the dashboard or report itself, select the icon for Usage
metrics .

3. The first time you do this, Power BI creates the usage metrics report and lets you know when it's ready.
4. To open the results, select View usage metrics.
Usage metrics are a powerful ally as you work to deploy and maintain Power BI dashboards and reports.
Wondering which pages of your report are most useful, and which ones you should phase out? Slice by
Report page to find out. Wondering if you should build a mobile layout for your dashboard? Slice by
Platforms to discover how many users are accessing your content via the mobile apps vs. via web browser.
5. Optionally, hover over a visualization and select the pin icon to add the visualization to a dashboard. Or,
from the top menubar, select Pin Live Page to add the entire page to a dashboard. From the dashboard you
can monitor the usage metrics more-easily or share them with others.

NOTE
If you pin a tile from a usage metrics report to a dashboard, that dashboard cannot be added to an app or content
pack.

Which metrics are reported?

METRIC DASHBOARD REPORT DESCRIPTION

Distribution method slicer yes yes How users got access to the
content. There are 3 possible
methods: users can access
the dashboard or report by
being members of an app
workspace, by having the
content shared with them, or
by installing a content
pack/app. Note that views
through an app are counted
as "content pack."

Platforms slicer yes yes Was the dashboard or

report accessed via the
Power BI service
(powerbi.com) or a mobile
device? Mobile includes all
our iOS, Android, and
Windows apps.

Report page slicer no yes If the report has more than

1 page, slice the report by
the page(s) that was viewed.
If you see a list option for
"Blank," that means a report
page was recently added
(within 24 hours the actual
name of the new page
appears in the slicer list)
and/or report pages have
been deleted. "Blank"
captures these types of
situations.
 METRIC DASHBOARD REPORT DESCRIPTION

Views per day yes yes Total number of views per

day - a view is defined as a
user loading a report page
or dashboard.

Unique viewers per day yes yes Number of different users

who viewed the dashboard
or report (based on the AAD
user account).

Views per user yes yes Number of views in the past

90 days, broken down by
individual users.

Shares per day yes no Number of times the

dashboard was shared with
another user or group.

Total views yes yes Number of views in the past

90 days.

Total viewers yes yes Number of unique viewers in

the past 90 days.

Total shares yes no Number of times the

dashboard or report was
shared in the past 90 days.

Total in organization yes yes Count of all dashboards or

reports in the entire
organization which had at
least one view in the past 90
days. Used to calculate rank.

Rank: Total views yes yes For total views of all

dashboards or reports in the
organization over the past
90 days, where does this
dashboard or report rank.

Rank: Total shares yes no For total shares of all

dashboards in the
organization over the past
90 days, where does this
dashboard or report rank.

Dashboard Usage Metrics report

Report Usage Metrics report

Save the Usage Metrics report as a full-featured Power BI report

(personalize)

Use Save as to convert the usage metrics report to a full-featured Power BI report that can be customized and
shared. Once you’ve created a personalized copy, you’ll get full access to the underlying dataset, allowing you to
customize the usage metrics report to your specific needs. You can even use Power BI Desktop to build custom
usage metrics reports using the live connection to Power BI service feature.
Better yet, the underlying dataset includes the usage details for all dashboards or reports in the workspace. This
opens up yet another world of possibilities. You could, for example, create a report which compares all dashboards
in your workspace based on usage. Or, you could create a usage metrics dashboard for your Power BI app by
aggregating usage across all the content distributed within that app. See remove the Page level filter below.
What is created when using "Save as"?
When Power BI creates the full-featured report, it also creates a new dataset made up of all the dashboards or
all the reports contained in the current workspace that have been accessed in the last 90 days. For example,
say you have a workspace named "Sales" and it contains three dashboards and two reports, and you create a usage
metrics report on the "Northeast" dashboard. And then you use Save as to personalize and convert it to a full-
featured report. The dataset for that new report contains the usage metrics not only for that one dashboard named
"Northeast" but for all three dashboards in the "Sales" workspace. By default, the report displays data for the
"Northeast" dashboard and you'll need to remove a filter (single click) to display data for all three dashboards.
Create a copy of the usage report using "Save as"
When you create a copy using "Save as" (personalize), Power BI converts the read-only pre-built report to a full-
featured report. At first glance, it looks exactly the same. However, you can now open the report in Editing view,
add new visualizations, filters, and pages, modify or delete existing visualizations, and so much more. Power BI
saves the brand new report and dataset in the current workspace. In the example below, the current workspace is
mihart.
1. From the pre-built usage metrics report, select File > Save As. Power BI converts the usage metrics report
into a full-featured Power BI report. This is called a personalized usage metrics report. The personalized
usage report and dataset are saved in the current workspace which is named *mihart.

2. Open the report in Editing view and interact with it as you would with any other Power BI report. For
example, add new pages and build new visualizations, add filters, format the fonts and colors, etc.

3. Alternately, start with the new dataset and build a report from scratch.
4. The new report is saved in the current workspace (mihart) and also added to the Recent content list.

Remove the filter to see all the usage metrics data in the workspace
To see the metrics for all the dashboards or for all the reports in the workspace, you'll have to remove a filter. By
default, the personalized report is filtered to display metrics for only the dashboard or report that was used to
create it.
If, for example, you used the dashboard named "European sales" to create this new personalized report, only usage
data from the "European sales" dashboard displays. To remove the filter, and enable data from all the dashboards in
that workspace:
1. Open the personalized report in Editing view.

2. In the Filters pane, locate the Report level filters bucket and remove the filter by selecting the "x".

Now your personalized report displays metrics for the entire workspace.
Admin controls for usage metrics - for Power BI administrators
Usage metrics reports are a feature that the Power BI or Office 365 administrator can turn on or off. Administrators
have granular control over which users have access to usage metrics; they are On by default for all users in the
organization.
1. Open the Admin portal by selecting the gear icon in the top-right-corner of Power BI service and choosing
Admin portal.

2. From the Admin portal, select Tenant settings and choose Usage metrics for content creators.

3. Enable (or disable) usage metrics and select Apply.

By default, per-user data is enabled for usage metrics, and content creator account information is included in the
metrics report. If you don’t want to include this information for some or all users, disable the feature for specified
security groups or for an entire organization. Account information then shows in the report as Unnamed.
When disabling usage metrics for their entire organization, admins can use the delete all existing usage metrics
content option to delete all existing reports and dashboard tiles that were built using the usage metrics reports
and datasets. This option removes all access to usage metrics data for all users in the organization who may already
be using it. Be careful, because deleting existing usage metrics content is irreversible.

Usage metrics in national clouds

Power BI is available in separate national clouds. These clouds offer the same levels of security, privacy, compliance
and transparency as the global version of Power BI, combined with a unique model for local regulations on service
delivery, data residency, access, and control. Due to this unique model for local regulations, usage metrics are not
available in national clouds. For more information, see national clouds.

Considerations and limitations

It's important to understand that differences that can occur when comparing usage metrics and audit logs, and why.
Audit logs are collected using data from the Power BI service, and Usage metrics are collected on the client.
Because of that difference, aggregate counts of activities in audit logs may not always match usage metrics, because
of the following:
Usage metrics may sometimes undercount activities due to inconsistent network connections, ad blockers, or
other issues that can disrupt sending the events from the client.
Certain types of views are not included in usage metrics, as described earlier in this article.
Usage metrics may sometimes overcount activities, in situations where the client refreshes without the need for
a request being sent back to the Power BI service.

Frequently asked questions

In addition to potential differences between usage metrics and audit logs, the following questions and answers
about usage metrics may be helpful for users and administrators:
Q: I can't run usage metrics on a dashboard or report
A: You can only see usage metrics for content you own or have permissions to edit.
Q: Do usage metrics capture views from embedded dashboards and reports?
A: Usage metrics currently does not support capturing usage for embedded dashboards, reports, and the publish
to web flow. In those cases, we recommend using existing web analytics platforms to track usage for the hosting
app or portal.
Q: I can't run usage metrics on any content at all.
A1: Admins can turn off this feature for their organization. Contact your Admin to see if this is the case.
A2: Usage metrics is a Power BI Pro feature.
Q: The data doesn't seem up-to-date. For example, distribution methods don't show up, report pages are missing,
etc.
A: It can take up to 24 hours for data to update.
Q: There are four reports in the workspace but the usage metrics report only displays three.
A: The usage metrics report only includes reports (or dashboards) that have been accessed in the past 90 days. If a
report (or dashboard) does not show up, likely it hasn't been used in more than 90 days.

Next steps
Favorite a dashboard
More questions? Try the Power BI Community
 Signing up for Power BI as an individual
1/14/2019 • 4 minutes to read • Edit Online

Power BI can be your personal report and visualization tool, and can also serve as the analytics and decision
engine behind group projects, divisions, or entire corporations. This article explains how to sign up for a Power
BI trial as an individual. If you're a Power BI administrator, see Power BI licensing in your organization.

Supported email addresses

Before you start the sign-up process, it's important to understand the types of email addresses that you can use
in Power BI:
Power BI requires that you use a work or school email address to sign up. You cannot sign up using email
addresses provided by consumer email services or telecommunication providers. This includes
outlook.com, hotmail.com, gmail.com and others.
After you sign up, you can invite guest users to see your Power BI content with any email address,
including personal accounts.
You can sign-up for Power BI with .gov or .mil addresses, but this requires a different process. For more
information, see Enroll your US Government organization in the Power BI service.

Sign up for a trial

Follow these steps to sign up for a Power BI Pro trial. See the next section, Trial expiration, to understand your
options when this trial expires.
1. Go to the sign-up page in Power BI.
2. Enter your email address then select Sign up.
3. If you get a message like the following, choose an option to receive a verification code, then continue to
the next step in this procedure.

If you get a message like the following, complete the steps to sign in and use Power BI.

4. Enter the code that you received then select Sign up.

5. Check your email for a message like the following.

6. On the next screen, enter your information and the verification code from the email. Select a region,
review the policies that are linked from this screen, then select Start.

7. You're then taken to https://app.powerbi.com, and you can begin using Power BI.
Trial expiration
When your Power BI pro trial expires, your license is changed to a Power BI (free) license. When this happens,
you no longer have access to features that require a Power BI Pro license. For more information, see Features
by license type.
If a Power BI (free) license is sufficient, no action is required. If you want to take advantage of Power BI Pro
features, contact your IT administrator about purchasing a Power BI Pro license.

Troubleshooting the sign-up process

In most cases, you can sign up for Power BI by following the process just described. That said, there are issues
that can prevent you from signing up. We cover these issues and workarounds in the following table.

SYMPTOM / ERROR MESSAGE CAUSE AND WORKAROUND

Personal email addresses (e.g. [email protected]) You Power BI does not support email addresses provided by
receive a message like the following during signup: consumer email services or telecommunications providers.

You entered a personal email address: Please enter your To complete signup, try again using an email address
work email address so we can securely store your assigned by your work or school.
company's data.
If you still can't sign up and are willing to complete a more
or advanced setup process, you can register for a new Office
365 trial subscription and use that email address to sign up.
That looks like a personal email address. Enter your work
address so we can connect you with others in your You can also have an existing user invite you as a guest.
company. And don’t worry. We won’t share your address
with anyone.
 SYMPTOM / ERROR MESSAGE CAUSE AND WORKAROUND

Self-service signup disabled You receive a message like Your organization’s IT administrator has disabled self-service
the following during signup: signup for Power BI.

We can't finish signing you up. Your IT department has To complete signup, contact your IT administrator and ask
turned off signup for Microsoft Power BI. Contact them to them to follow the instructions to enable sign-up.
complete signup.
You may also experience this problem if you signed up for
or Office 365 through a partner.

That looks like a personal email address. Enter your work

address so we can connect you with others in your
company. And don’t worry. We won’t share your address
with anyone.

Email address is not an Office 365 ID You receive a Your organization uses IDs to sign in to Office 365 and other
message like the following during signup: Microsoft services that are different than your email address.
For example, your email address might be
We can't find you at contoso.com. Do you use a different ID [email protected] but your ID is
at work or school? [email protected].

Try signing in with that, and if it doesn't work, contact your To complete signup, use the ID that your organization has
IT department. assigned to for signing in to Office 365 or other Microsoft
services. If you don't know what this is, contact your IT
administrator.

If you still can't sign up and are willing to complete a more

advanced setup process, you can register for a new Office
365 trial subscription and use that email address to sign up.

Next steps
Purchasing Power BI Pro
Power BI Service agreement for individual users
More questions? Try asking the Power BI Community
 Power BI licensing in your organization
3/22/2019 • 5 minutes to read • Edit Online

In the Power BI service, users have defined capabilities based on two types of licenses:
Per-user - Power BI Pro licensing and free licensing. A Power BI Pro license enables access to all content
and capabilities in the Power BI service, including the ability to share content and collaborate with other Pro
users. Only Pro users can publish to and consume content from app workspaces, share dashboards, and
subscribe to dashboards and reports. A free license enables access to some of the features of the Power BI
service. For more information, see Per-user license type comparison.
Capacity-based - Power BI Premium licensing. Premium provides dedicated capacity to deliver more
consistent performance and support larger data volumes in Power BI. For individual users, Premium also
enables widespread distribution of content by Pro users without requiring Pro licenses for recipients who
view the content. For more information, see What is Power BI Premium?.
This article focuses on per-user licensing from an administrator perspective.

Manage Power BI Pro licenses

As an administrator, you can purchase and assign Power BI Pro licenses; and you can sign up for a Power BI Pro
trial for your organization. Individuals can also sign up for a Power BI Pro trial.
Purchasing Power BI Pro
You purchase Power BI Pro licenses through Microsoft Office 365 or through a certified Microsoft partner. After
you purchase the licenses, you assign them to individual users. For more information, see Purchase and assign
Power BI Pro licenses.
Power BI Pro trial for individuals
Individuals in your organization can sign up for a Power BI Pro trial. For more information, see Signing up for
Power BI as an individual.
Users who take advantage of the in-product Power BI Pro trial do not appear in the Microsoft 365 admin center as
Power BI Pro Trial users (they appear as Power BI free users). They do, however, show up as Power BI Pro Trial
users in the manage storage page in Power BI.
Power BI Pro trial for organizations
If you want to acquire and deploy Power BI trial licenses to multiple users in your organization without users
accepting trial terms individually, sign up for a Power BI Pro trial for your organization.
Keep the following in mind before you follow the steps to sign up:
To sign up, you must be a member of the Global administrator or Billing administrator role in Office
365.
There is a limit of one organizational trial per tenant. This means that if someone has already applied the
Power BI Pro Trial to your tenant, you cannot do it again. If you need assistance with this, contact Office 365
Billing support.
1. Navigate to the Microsoft 365 admin center.
2. On the left navigation pane, select Billing then Subscriptions.
3. On the right side, select Add subscriptions.

4. Under Other Plans, hover over the ellipsis (. . .) for Power BI Pro and select Start free trial.
5. On the order confirmation screen, select Try now.
6. On the order receipt, select Continue.
Now you can assign licenses in Office 365.

Manage Power BI free licenses

Users within your organization can gain access to Power BI free licenses in two different ways:
You can assign a Power BI license to them within the Microsoft 365 admin center.
If a user signs up for a Power BI Pro trial and the trial expires, they are assigned a free license.
Requesting and assigning free licenses
If you plan to manage license requests and assignments centrally, first check whether you already have the
unlimited Power BI (free) license block.
This block of licenses is available after the first time someone signs up for Power BI as an individual. During that
process, this license block is attached to your organization, and a license is assigned to the user who is signing up.
1. In the Microsoft 365 admin center, under Billing > Licenses, check for unlimited.

2. If the block is available, you can now assign licenses in Office 365. If the block isn't available, you have two
choices:
Have a member of your organization sign up individually, which triggers the creation of the unlimited
block.
 Go to the next procedure, where you can sign up for a fixed number of licenses.
If the unlimited Power BI (free) license block isn't available and you don't want to do an individual sign up, follow
this procedure.
1. Navigate to the Microsoft 365 admin center.
2. On the left navigation pane, select Billing > Subscriptions.
3. On the right side, select Add subscriptions +.
4. Under Other Plans, hover over the ellipsis (. . .) for Power BI (free) and select Buy now.

5. Enter the number of licenses you want to add and select Check out now or Add to cart.
6. Enter the required information in the check out flow.
There is no purchase when using this approach, although you will need to either enter your credit card
information for billing, or choose to be invoiced.
7. You can now assign licenses in Office 365.
8. If you decide later that you want to add more licenses, you can go back to Add subscriptions, and select
Change license quantity for Power BI (free).

Enable or disable individual user sign up in Azure Active Directory

As an administrator, you can choose to enable or disable individual user sign ups through Azure Active Directory
(AAD ). This section of the article shows you how to manage sign ups with PowerShell commands. For more
information about Azure PowerShell, see Overview of Azure PowerShell.
The AAD setting that controls sign up is AllowAdHocSubscriptions. In most tenants, this is set to true, which
means it is enabled. If you acquired Power BI through a partner, this might be set to false, which means it is
disabled. If you change the setting from true to false, new users in your organization are blocked from signing up
individually. Users that signed up for Power BI prior to the setting change retain their licenses.
1. Sign into Azure Active Directory using your Office 365 credentials. The first line of the following PowerShell
script prompts you for your credentials. The second line connects to Azure Active Directory.

$msolcred = get-credential
connect-msolservice -credential $msolcred

2. Once you are signed in, run the following command to see how your tenant is currently configured.

Get-MsolCompanyInformation | fl AllowAdHocSubscriptions

3. Run the following command to enable ($true) or disable ($false) AllowAdHocSubscriptions.

Set-MsolCompanySettings -AllowAdHocSubscriptions $true

NOTE
The AllowAdHocSubscriptions flag is used to control several user capabilities in your organization, including the ability for
users to sign up for the Azure Rights Management Service. Changing this flag affects all of these capabilities.

Next steps
Self-service sign up for Power BI
Purchase and assign Power BI Pro licenses
More questions? Try asking the Power BI Community
 Power BI service features by license type
1/14/2019 • 2 minutes to read • Edit Online

In the Power BI service, users have defined capabilities based on two types of licenses:
Per-user - Power BI Pro licensing and free licensing. A Power BI Pro license enables access to all content
and capabilities in the Power BI service, including the ability to share content and collaborate with other
Pro users. Only Pro users can publish to and consume content from app workspaces, share dashboards,
and subscribe to dashboards and reports. A free license enables access to some of the features of the
Power BI service. For more information, see Per-user license type comparison.
Capacity-based - Power BI Premium licensing. Premium provides dedicated capacity to deliver more
consistent performance and support larger data volumes in Power BI. For individual users, Premium also
enables widespread distribution of content by Pro users without requiring Pro licenses for recipients who
view the content. For more information, see What is Power BI Premium?.

Per-user license type comparison

Here is a list of features supported by per-user license type.

FREE PRO

Connect to 70+ data sources

Publish to Web

Export to PowerPoint, Excel, CSV

Enterprise distribution

Apps

Email subscriptions

Embed APIs and controls

Collaboration

Peer-to-peer sharing

App workspaces

Analyze in Excel, analyze in Power BI

Desktop

Next steps
If you are interested in learning more about Power BI Premium, see What is Power BI Premium?.
To get started with Power BI by signing up, see Signing up for Power BI as an individual.
More questions? Try asking the Power BI Community
 10 tips for getting help with your Power BI questions
1/14/2019 • 3 minutes to read • Edit Online

Do you ever get frustrated using Power BI, or struggle because you can't get answers to your Power BI questions
when you need them -- i.e. "just-in-time"?
Here are 10 tips that Power BI experts (including people who work on the product at Microsoft) commonly follow
to find answers to their Power BI questions.

1 Use a search engine

Experts who need answers for Power BI often use search. Want to find a DAX formula for a common business
calculation? You can find this on the internet. Bookmark where you find the best answers. Create a folder for
yourself on tips and answers you find.

2 Check the Power BI documentation

The Power BI team is continually updating and improving the Power BI documentation and training. You can find
great content including recordings of webinars, white papers, guided learning, and links to blog posts on all the
latest features.

3 Read the Power BI blog for the latest news

The Power BI team explains all the new features in their regular Power BI blog posts. Find out what's new in
everything from Power BI Desktop to the Power BI mobile apps. Make a habit of returning often to see what's new:
Take a few minutes each week to scan the blogs. You never know when you'll benefit from that bit of information
you noticed months ago.

4 Try Twitter
Lots of Power BI customers and experts are on Twitter. Ask your question in a tweet. Add the hashtags #powerbi
and #powerbihelp so the people who know will see your tweet.

5 Watch videos on YouTube

Do videos fit your learning style better? Power BI has two sets you'll be interested in:
A good place to start is the Analyze and Visualize data with Power BI playlist.
Then try the Power BI channel for a much bigger selection.
If you have more experience with Power BI, the Guy in a Cube YouTube channel might be a better fit for you.

6 Attend training
The training options available to you are nearly endless, from in-person lab training to short videos.
Guided learning on the Power BI site.
Free Power BI webinars, live and on-demand, on the Power BI site.
You can find additional options online, such as:
edX.org offers a free course, Analyzing and Visualizing Data with Power BI.
 Lynda.com offers has courses such as Power BI Pro Essential Training.
Look for in-person "Dashboard in a Day" training sessions.

7 Ask or search in the Power BI community

Ask questions and find answers in the Power BI community. BI experts around the world are active in the
community. Make sure to benefit from their knowledge by using this resource.

8 Join or create a Power BI user group

Join a Power BI user group and ask your group for help in answering your questions. Or you start your own user
group and create a community of people who help each other out, focused on your needs: in your area, for your
data, in your time zone.

9 Check the service status

If you're having an issue with the service, it may be that the service itself is having issues. Check the Support page
for any reports.

10 Just try it
If all else fails, the final tip is to observe the system. Often, people ask what capabilities Power BI has. You can often
answer this type of question by going into the Power BI service or Power BI Desktop, looking at the options in the
user interface, and then trying to use them.
For example, say you're wondering if you can share dashboards with a security group. To answer that question, go
to the sharing dialog box and try adding a security group. Either way, you'll have your answer after this test.

Next steps
What is Power BI?
Try asking the Power BI Community
Still have an issue? Please visit the Power BI support page
 Power BI Pro and Power BI Premium support options
3/26/2019 • 3 minutes to read • Edit Online

This article describes the support options that are available for customers of Power BI Pro and Power BI Premium.

BREAK-FIX PROACTIVE SERVICE LEVEL

TECHNICAL CONSULTING AND (TIME TO INITIAL SUPPORT
SUPPORT OPTION SUPPORT BILLING SUPPORT TRAINING ENGAGEMENT) CHANNEL

Community X None, Power BI

support: Web engagement is Community
forums for users provided on a
to get peer-to- best-effort basis.
peer support,
guidance, and
best practices
with answers
provided by a
global
community of
Power BI experts
and Microsoft
employees.

Power BI Pro X One business Power BI Support

end user day. Site
support: Basic
technical support
for end users
creating and
consuming
content in Power
BI.

Power BI X One business day Power BI Support

Premium admin or one hour, Site
support: depending on OR
Technical support severity of case.* Microsoft 365
for administrators admin center
deploying and OR
operating Power Phone
BI Premium
capacities.
 BREAK-FIX PROACTIVE SERVICE LEVEL
TECHNICAL CONSULTING AND (TIME TO INITIAL SUPPORT
SUPPORT OPTION SUPPORT BILLING SUPPORT TRAINING ENGAGEMENT) CHANNEL

Power BI admin X X One business day Microsoft 365

support: or one hour, admin center
Technical and depending on OR
billing support severity of case.* Phone
for administrators
of Power BI
deployments at
their
organizations. To
use this option,
you must be an
Azure Active
Directory
Company
Administrator,
Office 365 Global
Administrator,
Office 365 Service
Administrator, or
a Power BI
Service
Administrator.

Microsoft X X X Various, Technical Account

Premier depending on Manager
support: An offering and OR
enterprise-grade severity of case.* Microsoft 365
approach to admin center
support, with
account
management, the
option for on-site
support, and
proactive services
such as training
and data model
performance
optimization.

* A one-hour SLA is available only through Sev A cases, which require justification of immediate, direct business
impact from work stoppage in existing production reporting.

Power BI benefits for Microsoft Premier support

With Microsoft Premier support, you get the following additional benefits:
Account management
Option for on-site support
Health check, risk assessments, and reviews
Training and workshops
Developer support
As a Power BI customer, you can also take advantage of the following offerings for proactive support hours:
Power BI Assessment, a proactive service delivered by a Microsoft accredited engineer to diagnose
 potential issues and performance with your Power BI environment. The engineer will provide valuable
guidance on recommended practices to improve the health and performance of your Power BI environment.
At the end of this engagement, you will receive a comprehensive Power BI report with results of the
assessment, a detailed best practices guidance deck, and a summary report tailored to your environment.
Activate Business Analytics with Power BI Work side-by-side with a Microsoft Premier Field Engineer
(PFE ) over 3 days, developing a proof-of-concept in Power BI, with the objective of improving one of the
following options:
Automating a detailed report that requires a significant amount of effort to maintain and distribute.
Update a report with compelling visualizations or different types of interactivity.
Help you drive Power BI adoption by setting up key components. Typical engagements cover use-cases
that will provide a quick-win to the organization, or a starting point for more complex scenarios or even
bootstrap your environment for Power BI adoption.
WorkshopPLUS - Data AI: Business Analytics with Power BI This workshop, typically delivered by a
Microsoft PFE, is a great introduction to Power BI, making it an excellent starting point for adoption or for
ramping up your workforce. It will provide you with a complete overview of Power BI functionality and
capabilities. It will cover both Power BI Desktop and Online tools. You will learn in detail how to transform
data, build a model, build calculations and reports and then best practices around sharing and governing
that content in the cloud service. You can also expect a significant amount of demonstrations and
laboratories, that will give you the possibility of experimenting and seeing the technology in action.
WorkshopPLUS - Data AI: Advanced Data Analytics with Power BI This course will provide you the
knowledge to understand and implement the key principles about the aspects of Data modeling in Power BI
using tools such as Power BI Desktop and accompanying the cloud service for publishing and consumption
of BI Assets. This course would then cover the basics of report development, embedded analytics in Power
BI to embed the content into custom applications, Real time dashboarding and advanced analytics involving
data science and development in Power BI.
Contact your Microsoft Technical Account Manager for details. If you don't already have a Microsoft Premier
support contract, learn more at Premier support.
 Extended Pro Trial activation
1/14/2019 • 4 minutes to read • Edit Online

IMPORTANT
The Extended Pro Trial is no longer available. To sign up for a free trial (if eligible), see Signing up for Power BI as an individual.
To purchase Power BI Pro, see Purchase and assign Power BI Pro licenses.

As part of the May 3, 2017 Power BI Premium announcement, Microsoft communicated changes to the free Power
BI service effective June 1,2017. These changes included extending access to all data sources, higher workspace
storage limits, and higher refresh and streaming rates, making those features equivalent to Power BI Pro.
Also announced was that sharing and collaboration features would be exclusive to Power BI Pro users, including
peer-to-peer dashboard sharing, group workspaces (now called app workspaces), export to PowerPoint, and
analyze in Excel with Power BI apps. Export to CSV/Excel and PowerPoint were identified in the May 3
communication as a capability limited to Power BI Pro. However, after receiving feedback from the broad user
community, the strategy evolved, and we made the capability available to users of the free service as well.
Beginning June 1, 2017 existing users of the Free service who were active users on or before May 2, 2017 were
eligible for a free, 12-month extended trial of Power BI Pro. The offer enabled users to take advantage of the full
capabilities of Power BI Pro for a year as a sign of appreciation to the community and to provide users with time to
adjust to the changes.
On June 1, 2017 eligible users received a notification when they signed into the service letting them know the
changes had gone into effect with a prompt to register for the Extended Power BI Pro trial offer. A user’s IT admin
dis not control the related in-product notifications, nor did the IT admin have the ability to register for the extended
Power BI Pro trial on behalf of a user. Each eligible user must have individually taken action to complete this
process.
Users could opt to register for the offer at any time during the 12-month period, but the Extended Pro trial
concluded on May 31, 2018 regardless of when users accepted the offer. At that time users had the option to
purchase Power BI Pro or be converted to the free version of Power BI, without the sharing and collaboration
capabilities, if they elected not to take action and purchase Power BI Pro.
No changes were made to Power BI Pro at the time. Power BI Pro users were not impacted and did not receive
notifications when they signed into the service on June 1, 2017 or after. Users who declined the extended Power BI
Pro trial offer or were ineligible for the offer could continue using the free version of Power BI without the sharing
and collaboration capabilities. They could register at any time for a standard 60-day Power BI Pro trial by visiting
the Power BI website.

Eligibility for Extended Pro Trial

Your account must have met the following requirements in order to be eligible for the Extended Pro Trial offer.
Power BI Free users active between May 3, 2016 and May 2, 2017 were eligible for an Extended Pro Trial.
Users that had previously used or were currently on the 60 -day in-product Pro trial were still eligible for the
Extended Pro Trial.
 NOTE
Users that had licenses assigned from the Power BI Pro or Power BI Pro Trial subscriptions, within Office 365, were excluded
from this offer.

Frequently asked questions

What happens to new users who signed up after May 3, 2017?
Users who signed up to Power BI Free on or after May 3, 2017 are not eligible for the Extended Pro Trial. However,
they are eligible for the standard 60-day Pro Trial.
How do I find out who in my organization is eligible for the Extended Pro Trial?
While there is not a direct way to discover this, you can view the Azure Active Directory (Azure AD ) Integrated
Applications report for Power BI to see who are active users within your organization within the last 30 days. This
may give you an idea of who may be eligible. For more information, see Find Power BI users that have signed in.
Those active users in the eligibility period, and who are on free licenses, receive the pop-up notification.

NOTE
The Azure AD report does not indicate if a user has a free or Pro license within Power BI. It only reports which users have
signed in to Power BI and when they signed in. If a user is listed in this report, it does not necessarily mean that they are
eligible for the Extended Pro Trial.

Can admins restrict a user from activating the Extended Pro Trial?
No. Admins do not have a way to restrict users from activating the Extended Pro Trial or the in-service 60-day trial
of Power BI Pro.

Next steps
Extended Pro Trial offer terms and conditions
Power BI Service agreement for individual users
Power BI Premium announcement
Find Power BI users that have signed in
More questions? Try asking the Power BI Community
 Power BI for US Government customers
3/26/2019 • 5 minutes to read • Edit Online

The Power BI service has a version available for United States Government customers as part of the Office 365
US Government Community subscriptions. The Power BI service version discussed in this article is specifically
designed for US Government customers, and is separate and different from the commercial version of the Power
BI service.

The following sections describe the features available to the US Government version of the Power BI service,
clarifies some of the limitations, lists Frequently Asked Questions (FAQ ) and answers (including how to sign up),
and provides links for more information.

Features of Power BI US Government

It's important to note that Power BI US Government is only available as a Pro license, and is not available as a
Free license. Certain features of the Power BI service are available in the Power BI US Government version of
the service.
The following features are available to Power BI US Government customers, as they apply to Pro license
functionality:
Create and view dashboards and reports
Data capacity limits
Scheduled data refresh
Refreshable team dashboards
Active Directory groups for sharing and managing access control
Import data and reports from Excel, CSV, and Power BI Desktop files
Data Management Gateway
All data is encrypted in both Azure SQL and Blob Storage for Power BI
Connect to services with content packs

Connectivity between Government and global Azure Cloud services

Azure is distributed among multiple clouds. Be default, tenants are allowed to open firewall rules to a cloud-
specific instance, but cross-cloud networking is different and requires opening specific firewall rules to
communicate between services. If you are a Power BI customer and you have existing SQL instances in the public
cloud which you need to access, you must open specific firewall rules in SQL to the Azure Government Cloud IP
space, for the following datacenters:
USGov Iowa
USGov Virginia
 USGov Texas
USGov Arizona
In the public cloud the IP spaces are available, but for the government cloud, you must open an Azure Support
ticket to request the IP ranges for the above listed datacenters.

Limitations of Power BI US Government

Some of the features that are available in the commercial version of the Power BI service are not available in the
Power BI service for US Government customers. The Power BI team is actively working on making these
features available to US Government customers, and will update this article when these features become available.
Embed in SharePoint Online - it is not possible to embed content in SharePoint Online using the Power BI
web part. However, secure embed does work using the Embed web part. You must add app.powerbigov.us to
the exception list, which can be achieved by following the instructions in the Allow or restrict the ability to
embed content on SharePoint pages article.
Power BI US Government is only available as a Pro license. Any references to Power BI (Free) licenses in an
admin portal (or as users) are running in a commercial Power BI service cloud.
Auditing - auditing is now available through the Office 365 Security and Compliance portal, as of June 2018.
Power BI content in Cortana - Power BI results will not show up in Cortana search results, which includes
results for your Power BI content (dashboards, reports, apps) as well as results that show Cortana-optimized
report pages for specific keywords.
External user sharing - sharing is allowed within a Power BI tenant, and as of June 2018, sharing is also
allowed with users outside of your Power BI tenant. See distribute Power BI content to external guest users
with Azure AD B2B.
Usage metrics for dashboards and reports - usage metrics are not available for reports and dashboards.
Customers can use audit log data to get usage information for content in their organization.
Dataflows - Dataflows are not available.
If you have Power BI Free licenses assigned to your account, those accounts are running in a commercial version
of the Power BI service, and are not part of the Power BI US Government offering. For those Free accounts, you
may encounter the following issues:
Gateway, Mobile, and Desktop can’t authenticate
You cannot access Azure commercial data sources
PBIX files must be manually uploaded from commercial
Power BI mobile apps are not available
To resolve issues, please contact your account representative.

Frequently Asked Questions (FAQ) for the US Government version of

the Power BI service
The following questions (and answers) are provided to help you quickly get information you need about the
service.
Question: How do I migrate my commercial Power BI data to the Power BI service for US Government?
Answer: Your admin must create a new instance of Power BI under a separate, US Government-specific
subscription. You can then replicate your commercial data in the Power BI service for US Government, remove
your commercial license, and associate your existing domain to the new US Government-specific service.
Question: Why can't I connect to a specific content pack?
Answer: You need to ensure your subscription is enabled before connecting to that content pack.
Question: I'm interested in getting Power BI for my US Government organization. How do I get started?
Answer: Signing up (often called onboarding) might differ based on your existing license and subscription. See
the Sign Up for Power BI US Government article for more information.
Question: Is the URL for connecting to Power BI for US Government different than the commercial Power BI
URL?
Answer: Yes, the URLs are different. The following table shows each URL:

COMMERCIAL VERSION URL US GOVERNMENT VERSION URL

https://app.powerbi.com/ https://app.powerbigov.us

Question: My account is provisioned in more than one national cloud. When using Power BI Desktop, how do I
select which cloud to connect to?
Answer: Beginning with the July 2018 release of Power BI Desktop, you can choose which cloud you want to
use when signing in to Power BI Desktop.

Next steps
There are all sorts of things you can do with Power BI. For more information and learning, including an article that
shows you how to sign up for the service, check out the following resources:
Sign up for Power BI for US Government
Power BI US Government Demo
Guided Learning for Power BI
Get started with the Power BI service
What is Power BI Desktop?
 Frequently Asked Questions for Power BI for
Germany Cloud customers
1/14/2019 • 3 minutes to read • Edit Online

The Power BI service has a version available for European Union/European Free Trade Agreement (EU/EFTA)
customers, often referred to as Microsoft Cloud Deutschland (MCD ). The Power BI service version discussed in
this article is specific to EU/EFTA customers, and is separate and different from the commercial version of the
Power BI service, or Power BI services provided to government customers.

Questions and answers

The following questions and answers provide important information for Power BI Pro Service in Microsoft Cloud
Deutschland (MCD ), which is the Power BI service cloud specifically provided for EU/EFTA customers.
1. What is the Power BI service for Germany Cloud?
The Power BI service for EU/EFTA customers, also referred to as Microsoft Cloud Deutschland (MCD ), is an
EU/EFTA compliant cloud with the Power BI service delivered from German datacenters. All customer data
in the Power BI service for EU/EFTA cloud is stored at rest in Germany with T-Systems working as the
independent German data trustee, and with physical and logical access to data controlled by German law.
The Power BI service for EU/EFTA cloud requires a distinct and separate account from the commercial
version of the Power BI service. Learn more about Microsoft Cloud Deutschland here.
2. Where can I find pricing and sign up information for the Power BI Germany Cloud?
You can find lots of information on the Power BI Germany Cloud home page, including pricing information.
On that page you can also find a link to sign up for Power BI Pro service 30-Day trial with 25 user licenses.
As part of trial sign up, you have an option to purchase or add additional licenses as needed. We also offer
Enterprise Agreement (EA), Government, and non-profit pricing. Please reach to your Microsoft customer
representative for more details.
3. I have a Germany Cloud tenant as part of Azure Germany and/or Office 365 Germany
 subscriptions. Can I use the existing tenant to sign up for Power BI Germany?
Yes. As part of the sign up process, you'll have an option to login with an existing Germany Cloud tenant
administrator account, and add the Power BI Pro service licenses to your existing tenant in the Germany
Cloud. Please note that Germany Cloud tenants and user accounts are different from the Power BI service
for Germany cloud.
4. Is there a free service in the Power BI service for Germany cloud?
No. We don't offer free license versions in the Power BI service for Germany cloud. However, we encourage
you to sign up for Power BI free offering in our public cloud if your business needs are met with the Power
BI free offering.
5. Can I use Power BI Desktop, Power BI Mobile, On-premises data gateway and Publisher for Excel
with the Power BI service for Germany cloud?
Yes. We've updated our Power BI client products to seamlessly work with the Power BI service for Germany
cloud. Please login with your Power BI service for Germany cloud account to start using the same client
products with Power BI service for Germany cloud. You can download the latest version of client products
from the following locations:
Power BI Desktop
Power BI Mobile
On-premises data gateway
Power BI Publisher for Excel
6. Are there any feature limitations of the Power BI service for Germany cloud?
The following service features are currently not available in Power BI service for Germany cloud:
Publish to Web
ArcGIS maps by Esri
Power BI Embedded (separate metered ISV licensing, will be offered through Microsoft Azure Germany
in the future)
7. Where can I find the Power BI service for Germany cloud specific configuration information for
use and integration in my applications?
We updated our SaaS Embedding developer samples with Germany and other Power BI clouds specific
configuration information. Please look at the Cloud Configs folder in samples for cloud specific
configuration end points. The following table lists various configuration end points for the Power BI service
for Germany cloud (and Public Cloud for cross-reference).

POWER BI SERVICE FOR GERMANY CLOUD EQUIVALENT URL IN PUBLIC CLOUD (FOR
ENDPOINT NAME AND/OR USAGE URL CROSS-REFERENCE)

Home Page, Sign Up and Sign In https://powerbi.microsoft.com/power- https://powerbi.microsoft.com/

bi-germany/

Power BI Service direct sign in https://app.powerbi.de/? https://app.powerbi.com/?

noSignUpCheck=1 noSignUpCheck=1

Service API https://api.powerbi.de/ https://api.powerbi.com/

Office Portal for user license https://portal.office.de/ https://portal.office.com/

management, service health status and
support requests by administrators
 POWER BI SERVICE FOR GERMANY CLOUD EQUIVALENT URL IN PUBLIC CLOUD (FOR
ENDPOINT NAME AND/OR USAGE URL CROSS-REFERENCE)

AAD Authority Uri https://login.microsoftonline.de/commo https://login.microsoftonline.com/comm

n/oauth2/authorize/ on/oauth2/authorize/

Power BI Service Resource Uri https://analysis.cloudapi.de/powerbi/api https://analysis.windows.net/powerbi/ap

i

Custom Visuals Library https://app.powerbi.de/visuals/ https://app.powerbi.com/visuals/

Register an Application for Power BI https://app.powerbi.de/apps https://app.powerbi.com/apps

(For Embedded)

Azure Portal (For Embedded) https://portal.microsoftazure.de/ https://portal.azure.com/

Community https://community.powerbi.com/ https://community.powerbi.com/

Next steps
There are all sorts of things you can do with Power BI. For more information and learning, including an article that
shows you how to sign up for the service, check out the following resources:
Guided Learning for Power BI
Get started with the Power BI service
What is Power BI Desktop?
 Microsoft Flow and Power BI
1/30/2019 • 3 minutes to read • Edit Online

Microsoft Flow is a SaaS offering for automating workflows across the growing number of applications and SaaS
services that business users rely on. With Flow you can automate tasks by integrating your favorite apps and
services (including Power BI) to get notifications, synchronize files, collect data, and more. Repetitive tasks become
easy with workflow automation.
Get started using Flow now.
Watch Sirui create a Flow that sends a detailed email to colleagues when a Power BI alert is triggered. Then follow
the step-by-step instructions below the video to try it out yourself.
https://www.youtube.com/embed/YhmNstC39Mw

Create a flow that is triggered by a Power BI data alert

Prerequisites
This tutorial will show you how to create two different flows; one from a template and one from scratch. To follow
along, create a data alert in Power BI, create a free Slack account, and sign up for Microsoft Flow (it's free!).

Create a flow that uses Power BI - from a template

In this task we'll use a template to create a simple flow that is triggered by a Power BI data alert (notification).
1. Sign in to Microsoft Flow (flow.microsoft.com).
2. Select My flows.

3. Select Create from template.

4. Use the Search box to find Power BI templates and select Send an e-mail to any audience when a
Power BI data alert is triggered > Continue.
Build the flow
This template has one trigger (Power BI data alert for new Olympic medals for Ireland) and one action (send an
email). As you select a field, Flow displays dynamic content that you can include. In this example we'll included the
tile value and the tile URL in the message body.

1. From the trigger dropdown, select a Power BI data alert. Select New medal for Ireland. To learn how to
create an alert, see Data alerts in Power BI.

2. Enter one or more valid email addresses and then select Edit (shown below ) or Add dynamic content.
3. Flow creates a title and message for you which you can keep or modify. All the values you set when you
created the alert in Power BI are available for your use -- just place your cursor and select from the gray
highlighted area.

4. For example, if you created an alert title in Power BI of We won another medal, you can select Alert title
to add that text to your email Subject field.

And, you can accept the default Email body or create your own. The example above contains a few
modifications to the message.
5. When you're done, select Create flow or Save flow. The flow is created and evaluated. Flow lets you know
if it finds errors.
6. If errors are found, select Edit flow to fix them, otherwise, select Done to run the new flow.
7. When the data alert is triggered, an email will be sent to the addresses you indicated.

Create a Flow that uses Power BI - from scratch (blank)

In this task we'll create a simple flow from scratch that is triggered by a Power BI data alert (notification).
1. Sign in to Microsoft Flow.
2. Select My flows > Create from blank.

3. Use the Search box to find a Power BI trigger and select Power BI - when a data driven alert is
triggered.
Build your flow
1. From the dropdown, select the name of your alert. To learn how to create an alert, see Data alerts in Power
BI.

2. Select New step > Add an action.

3. Search for Outlook and select Create event.

4. Fill in the event fields. As you select a field, Flow displays dynamic content that you can include.

5. Select Create flow when done. Flow saves and evaluates the flow. If there are no errors, select Done to run
this flow. The new flow is added to your My flows page.

6. When the flow is triggered by your Power BI data alert, you'll receive an Outlook event notification similar
to this one.

Next steps
Get started with Microsoft Flow
Set data alerts in Power BI service
Set data alerts on your iPhone
Set data alerts in the Power BI mobile app for Windows 10
More questions? Try the Power BI Community
 Get started with third party apps
1/14/2019 • 2 minutes to read • Edit Online

With Power BI, you can use an app built by a company or individual other than Microsoft. For example, you might
use a third party app which integrates Power BI tiles into a custom built web application. When you use a third
party app, you will be asked to grant that application certain permissions to your Power BI account and resources.
It is important that you only grant permissions to applications that you know and trust. Permissions to an
application can be revoked at any time. See Revoke third party app permissions.
Here are the types of access an application can request.

Power BI App permissions

View all Dashboards
This permission gives an application the ability to view all dashboards you have access to. This includes
dashboards that you own, have gotten from content packs, and have been shared to you and are in
groups that you belong to. The application cannot make any modifications to the dashboard. Among
other things, this permission can be used by an application to embed your dashboard content into its
experiences.
View all Reports
This permission gives an application the ability to view all reports you have access to. This includes
reports that you own, have gotten from content packs, and are in groups that you belong to. Part of
viewing the report, means that the application can also see the data within it. The application cannot
make any modifications to the reports themselves. Among other things, this permission can be used by
an application to embed your report content into its experiences.
View all Datasets
This permission gives an application the ability to list all datasets that you have access to. This includes
datasets that you own, have gotten from content packs, and are in groups that you belong to. An
application can see the names of all your datasets as well as their structure including table and column
names. This permission gives rights to read the data in a dataset. The permission does not give the
application rights to add or make changes to a dataset.
Read and Write all Datasets
This permission gives an application the ability to list all datasets that you have access to. This includes
datasets that you own, have gotten from content packs, and are in groups that you belong to. An
application can see the names of all your datasets as well as their structure including table and column
names. This permission gives rights to read and write the data in a dataset. The application can also
create new datasets, or make modifications to existing ones. This is commonly used by an application to
send to data directly to Power BI.
View user's Groups
This permission gives the application the ability to list all groups that you are a member of. It can use this
permission along with some of the other permissions listed to view or update content for that particular
group. The application cannot make modifications to the group itself.

Revoke third party app permissions

You revoke permissions for a third party app by going to the Office 365 My Apps site.
On the Office 365 My apps site, here's how to revoke third party permissions:
1. Go to Office 365 My Apps site.
2. On the My apps page, locate the third party app.
3. Hover over the app tile, click the (...) button, and click Remove.
 Get data from files for Power BI
1/14/2019 • 3 minutes to read • Edit Online

In Power BI, you can connect to or import data and reports from three types of files.
Microsoft Excel (.xlsx or .xlsm)
Power BI Desktop (.pbix)
Comma Separated Value (.csv)

What does get data from a file really mean?

In Power BI the data you explore comes from a dataset. But in order to have a dataset, you first need to get some
data. For this article, we're going to focus on getting data from files.
To better understand the importance of datasets, and how we get data for them, let’s look at an automobile. Take a
seat in your car and look at the dashboard. That’s a lot like sitting in front of your computer looking at a
dashboard in Power BI. The dashboard shows you all the things your car is doing; how fast the engine is revving,
temperature, what gear you’re in, your speed, etc.
In Power BI, a dataset is like the engine in your car. The dataset provides the data, metrics, and information that’s
displayed in your Power BI dashboard. Of course your engine, or dataset, needs fuel, and in Power BI, that fuel is
data. Your car has a fuel tank that provides gas to the engine. Much the same in Power BI, you need a fuel tank
that has data you can feed to your dataset. In our case, that fuel tank is a Power BI Desktop file, an Excel workbook
file, or a .CSV file.
We can even take it one step further. A fuel tank in a car has to be filled with gas. The gas for our Power BI
Desktop, Excel, or .CSV file is data from another data source. We get data from another data source and put it into
an Excel, Power BI Desktop, or .CSV file. If it's an Excel workbook or .CSV file, we can manually enter rows of data.
Or, we can connect to an external data source to query and load data into our file. Once we have a file with some
data, we can get it into Power BI as a dataset.

NOTE
Data in Excel workbooks must be in a table, or in the data model, to be imported by Power BI.

Where your file is saved makes a difference

Local - If you save your file to a local drive on your computer or another location in your organization, from
Power BI, you can import your file into Power BI. Your file will actually remain on your local drive, so the whole file
isn’t really imported into Power BI. What really happens is a new dataset is created in your Power BI site and data,
and in some cases the data model, are loaded into the dataset. If your file has any reports, those will appear in
your Power BI site under Reports.
OneDrive - Business – If you have OneDrive for Business and you sign into it with the same account you sign
into Power BI with, this is by-far the most effective way to keep your work in Excel Power BI Desktop, or a .CSV
file and your dataset, reports, and dashboards in Power BI in-sync. Because both Power BI and OneDrive are in
the cloud, Power BI connects to your file on OneDrive about every hour. If any changes are found, your dataset,
reports, and dashboards are automatically updated in Power BI.
OneDrive - Personal – If you save your files to your own OneDrive account, you’ll get many of the same benefits
as you would with OneDrive for Business. The biggest difference is when you first connect to your file (using Get
Data > Files > OneDrive – Personal) you’ll need to sign in to your OneDrive with your Microsoft account, which is
usually different from what you use to sign in to Power BI. When signing in with your OneDrive with your
Microsoft account, be sure to select the Keep me signed in option. This way, Power BI will be able to connect to
your file about every hour and make sure your dataset in Power BI is in-sync.
SharePoint Team -Sites – Saving your Power BI Desktop files to SharePoint – Team Sites is much the same as
saving to OneDrive for Business. The biggest difference is how you connect to the file from Power BI. You can
specify a URL or connect to the root folder.

Ready to get started?

See the following articles to learn more about getting your file into Power BI.
Get data from Excel workbook files
Get data from Power BI Desktop files
Get data from Comma Separated Value files
 From Excel workbook to stunning report in no time
1/14/2019 • 3 minutes to read • Edit Online

Your manager wants to see a report on your latest sales figures combined with your last campaign impressions by
the end of the day. But the latest data resides on various third party systems and on files in your laptop. In the past
it’s taken hours to create visuals and format a report. You’re beginning to feel anxious.
No worries. With Power BI, you can create a stunning report in no time.
In this example, we’ll upload an Excel file from a local system, create a new report, and share it with colleagues—all
from within Power BI.

Prepare your data

Let’s take a simple Excel file as an example. Before you can load your Excel file into Power BI, you must organize
your data in a flat table. This means that each column contains the same data type--for example, text, date, number,
or currency. You should have a header row, but there should not be any column or row that displays totals.

Next, format your data as a table. In Excel, on the Home tab, in the Styles group, select Format as Table. Select a
table style to apply to your worksheet. Your Excel worksheet is now ready to load into Power BI.

Upload your Excel file into Power BI

Power BI connects to many data sources, including Excel files that live on your computer. To get started, sign in to
Power BI service. If you haven’t signed up, you can do so for free.
You want to create a new dashboard. Open My workspace and select the + Create icon.
Select Dashboard, enter a name, and select Create. The new dashboard displays -- with no data.

At the bottom of the left navigation pane, select Get Data. On the Get Data page, under Import or Connect to
Data, in the Files box, select Get.

On the Files page, select Local File. Navigate to the Excel workbook file on your computer and select it to load into
Power BI. Select Import.

NOTE: To follow along with the rest of this tutorial, use the Financial sample workbook.

Build your report

After Power BI imports your Excel file, start building your report. When the Your dataset is ready message
appears, select View dataset. Power BI opens in Editing view and displays the report canvas. On the right side are
the Visualizations, Filters, and Fields panes.
Notice that your Excel workbook table data appears in the Fields pane. Under the name of the table, Power BI lists
the column headings as individual fields.

Now you can begin to create visualizations. Your manager wants to see profit over time. In the Fields pane, drag
Profit to the report canvas. Power BI displays a bar chart by default. Next, drag Date to the report canvas. Power
BI updates the bar chart to show profit by date.

TIP: If your chart doesn't look like you expected, check your aggregations. For example, in the Value well, right
click the field you just added and make sure the data is being aggregated the way you'd like it to be. In this
example, we're using Sum.

Your manager wants to know which countries are the most profitable. Impress her with a map visualization. Select
a blank area on your canvas, and from the Fields pane, simply drag over the Country and then Profit fields. Power
BI creates a map visual with bubbles representing the relative profit of each location.
What about displaying a visual showing sales by product and market segment? Easy. In the Fields pane, select the
checkboxes next to the Sales, Product and Segment fields. Power BI creates a bar chart instantly. Change the type
of chart by choosing one of the icons in the Visualizations menu. For instance, change it to a Stacked Bar chart. To
sort the chart, select the ellipses (...) > Sort by.

Pin all of your visuals to your Dashboard. You’re ready to share it with your colleagues.
Share your dashboard
You want to share your dashboard with your manager, Paula. You can share your dashboard and underlying report
with any colleague who has a Power BI account. They can interact with your report, but cannot save changes.
To share your report, at the top of the dashboard, select Share.

Power BI displays the Share Dashboard page. In the top area, enter the email addresses of the recipients. Add a
message in the field below. To allow recipients to share your dashboard with others, select Allow recipients to
share your dashboard. Select Share.
Next steps
Get started with Power BI service
Get started with Power BI Desktop
Power BI - Basic Concepts
More questions? Try the Power BI Community
 Get data from Excel workbook files
2/26/2019 • 8 minutes to read • Edit Online

Microsoft Excel is one of the most widely used business applications around. It’s also one of the most common
ways to get your data into Power BI.

What types of workbooks does Power BI support?

Power BI supports importing or connecting to workbooks created in Excel 2007 and later. Workbooks must be
saved as .xlsx or .xlsm file type and be under 1 GB. Some features described in this article are only available in
later versions of Excel.
Workbooks with ranges or tables of data
If your workbook has simple worksheets with ranges of data, to get the most out of your data in Power BI, be
sure to format those ranges as tables. This way, when creating reports in Power BI, you’ll see named tables and
columns in the Fields pane, making it much easier to visualize your data.
Workbooks with data models
Workbooks can contain a data model with one or more tables of data loaded into it by using linked tables,
Power Query (Get & Transform in Excel 2016), or Power Pivot. Power BI supports all data model properties
such as relationships, measures, hierarchies, and KPIs.

NOTE
Workbooks with data models cannot be shared across Power BI tenants. For example, a user who logs in to Power BI
using a contoso.com account cannot share an Excel workbook with a user who logs in using a Power BI login account
from woodgrovebank.com.

Workbooks with connections to external data sources

If you use Excel to connect to an external data source, once your workbook is in Power BI, you can create reports
and dashboards based on data from that connected data source. You can also setup Scheduled Refresh to
automatically connect right to the data source and get updates. You’ll no longer need to refresh manually from
the Data ribbon in Excel. Any visualizations in reports and tiles in dashboards based on data from that data
source are updated automatically. To learn more, see Data refresh in Power BI.
Workbooks with Power View sheets, PivotTables and charts
How your PowerView sheets and PivotTables and charts appear, or not appear, in Power BI depends on where
your workbook file is saved and how you choose to get it into Power BI. We'll go into this more below.

Data types
Power BI supports the following data types: Whole Number, Decimal Number, Currency, Date, True/False, Text.
Marking data as specific data types in Excel will improve the Power BI experience.

Prepare your workbook for Power BI

Watch this helpful video to learn more about how to make sure your Excel workbooks are ready for Power BI.
https://www.youtube.com/embed/l2wy4XgQIu0

Where your workbook file is saved makes a difference

Local - If you save your workbook file to a local drive on your computer or another location in your
organization, from Power BI you can load your file into Power BI. Your file will actually remain on your local
drive, so the whole file isn’t really imported into Power BI. What really happens is a new dataset is created in
Power BI and data and the data model (if any) from the workbook are loaded into the dataset. If your workbook
has any Power View sheets, those will appear in your Power BI site under Reports. Excel 2016 also has the
Publish feature (under the File menu). Using Publish is effectively the same as using Get Data > Files >
Local File from Power BI, but is often easier to update your dataset in Power BI if you’re regularly making
changes to the workbook.
OneDrive - Business – If you have OneDrive for Business and you sign into it with the same account you sign
into Power BI with, this is by-far the most effective way to keep your work in Excel and your dataset, reports, and
dashboards in Power BI in-sync. Because both Power BI and OneDrive are in the cloud, Power BI connects to
your workbook file on OneDrive about every hour. If any changes are found, your dataset, reports, and
dashboards are automatically updated in Power BI. Just like if you saved your workbook to a local drive, you can
also use Publish to update your dataset and reports in Power BI immediately; otherwise Power BI will
automatically synchronize, usually within an hour.
OneDrive - Personal – If you save your workbook files to your own OneDrive account, you’ll get many of the
same benefits as you would with OneDrive for Business. The biggest difference is when you first connect to
your file (using Get Data > Files > OneDrive – Personal) you’ll need to sign in to your OneDrive with your
Microsoft account, which is usually different from what you use to sign in to Power BI. When signing in with
your OneDrive with your Microsoft account, be sure to select the Keep me signed in option. This way, Power BI
will be able to connect to your workbook file about every hour and make sure your dataset and reports in Power
BI are in-sync.
SharePoint Team -Sites – Saving your Power BI Desktop files to SharePoint – Team Sites is much the same as
saving to OneDrive for Business. The biggest difference is how you connect to the file from Power BI. You can
specify a URL or connect to the root folder.

One Excel workbook – two ways to use it

If you save your workbook files to OneDrive, you'll have a couple of ways you can explore your data in Power
BI
Import Excel data into Power BI
When you choose Import, any supported data in tables and/or a data model are imported into a new dataset in
Power BI. If you have any Power View sheets, those will be re-created in Power BI as reports.
You can continue editing your workbook. When your changes are saved, they’ll be synchronized with the dataset
in Power BI, usually within about an hour. If you need more immediate gratification, you can just click Publish
again, and your changes are exported right then and there. Any visualizations you have in reports and
dashboards will be updated, too.
Choose this option if you’ve used Get & Transform data or Power Pivot to load data into a data model, or if your
workbook has Power View sheets with visualizations you want to see in Power BI.
In Excel 2016, you can also use Publish > Export. It's pretty much the same thing. To learn more, see Publish to
Power BI from Excel 2016.
Connect, manage and view Excel in Power BI
When you choose Connect, your workbook will appear in Power BI just like it would in Excel Online. But, unlike
Excel Online, you’ll have some great features to help you pin elements from your worksheets right to your
dashboards.
You can’t edit your workbook in Power BI. But if you need to make some changes, you can click Edit, and then
choose to edit your workbook in Excel Online or open it in Excel on your computer. Any changes you make are
saved to the workbook on OneDrive.
When choosing this way, Power BI will create a corresponding dataset for the connected workbook. You can use
this dataset to create a Power BI report if needed. Your workbook will also appear in your Power BI workspace
navigation pane under Reports. Connected workbooks have a special Excel icon.
Choose this option if you only have data in worksheets, or you have ranges, PivotTables and charts you want to
pin to dashboards.
In Excel 2016, you can also use Publish > Upload. It's pretty much the same thing. To learn more, see Publish to
Power BI from Excel 2016.

Import or connect to an Excel workbook from Power BI

1. In Power BI, in the navigation pane, click Get Data.

2. In Files, click Get.

3. Find your file.

4. If your workbook file is on OneDrive or SharePoint - Team Sites, choose Import or Connect.

Local Excel workbooks

You can also use a local Excel file and upload it into Power BI. Simply select Local File from the previous menu,
then navigate to where you have your Excel workbooks saved.

Once selected, choose to Upload your file into Power BI.

Once your workbook is uploaded, you get a notification that the workbook is ready.

Once the workbook is ready, you can find it in the Reports section of Power BI.
Publish from Excel 2016 to your Power BI site
Using the Publish to Power BI feature in Excel 2016 is effectively the same as using Get Data in Power BI to
import or connect to your file. We won't go into the details here, but you can see Publish to Power BI from Excel
2016 to learn more.

Troubleshooting
Workbook file too big? Check out Reduce the size of an Excel workbook to view it in Power BI.
Currently, when you choose Import, Power BI only imports data that is part of a named table or a data model.
As a result, if the workbook contains no named tables, Power View sheets, or Excel data models, you might see
this error: "We couldn't find any data in your Excel workbook". This article explains how to fix your
workbook and re-import it.

Next steps
Explore your data - Once you get data and reports from your file into Power BI, it's time to explore. Just right-
click the new dataset and then click Explore. If you chose to connect to a workbook file on OneDrive in step 4,
your workbook will appear in Reports. When you click on it, it will open in Power BI, just as it would if it were in
Excel Online.
Schedule refresh - If your Excel workbook file connects to external data sources, or you imported from a local
drive, you can setup scheduled refresh to make sure your dataset or report is always up-to-date. In most cases,
setting up scheduled refresh is quite easy to do, but going into the details is outside the scope of this article. See
Data refresh in Power BI to learn more.
Publish to Power BI from Excel 2016
Power BI publisher for Excel
Data refresh in Power BI
 Get data from Power BI Desktop files
1/14/2019 • 3 minutes to read • Edit Online

Power BI Desktop makes business intelligence and reporting easy. Whether you're connecting to a many
different data sources, querying and transforming data, modeling your data, and creating powerful and dynamic
reports, Power BI Desktop makes business intelligence tasks intuitive and fast. If you're not familiar with Power
BI Desktop, check out Getting started with Power BI Desktop.
Once you bring data into Power BI Desktop and create a few reports, it’s time to get your saved file into the
Power BI service.

Where your file is saved makes a difference

Local - If you save your file to a local drive on your computer or another location in your organization, you can
import your file or you can publish from Power BI Desktop to get its data and reports into Power BI. Your file will
actually remain on your local drive, so the whole file isn’t really moved into Power BI. What really happens is a new
dataset is created in Power BI and data and the data model from the Power BI Desktop file are loaded into the
dataset. If your file has any reports, those will appear in your Power BI site under Reports.
OneDrive - Business – If you have OneDrive for Business and you sign into it with the same account you sign
into Power BI with, this is by-far the most effective way to keep your work in Power BI Desktop and your dataset,
reports, and dashboards in Power BI in-sync. Because both Power BI and OneDrive are in the cloud, Power BI
connects to your file on OneDrive about every hour. If any changes are found, your dataset, reports, and
dashboards are automatically updated in Power BI.
OneDrive - Personal – If you save your files to your own OneDrive account, you’ll get many of the same benefits
as you would with OneDrive for Business. The biggest difference is when you first connect to your file (using Get
Data > Files > OneDrive – Personal) you’ll need to sign in to your OneDrive with your Microsoft account, which is
usually different from what you use to sign in to Power BI. When signing in with your OneDrive with your
Microsoft account, be sure to select the Keep me signed in option. This way, Power BI will be able to connect to
your file about every hour and make sure your dataset in Power BI is in-sync.
SharePoint Team -Sites – Saving your Power BI Desktop files to SharePoint – Team Sites is much the same as
saving to OneDrive for Business. The biggest difference is how you connect to the file from Power BI. You can
specify a URL or connect to the root folder.

Import or connect to a Power BI Desktop file from Power BI

IMPORTANT
The maximum file size you can import into Power BI is 1 gigabyte.

1. In Power BI, in the navigator pane, click ** Get Data**.

2. In Files, click Get.

3. Find your file. Power BI Desktop files have a .PBIX extension.

Publish a file from Power BI Desktop to your Power BI site

Using Publish from Power BI Desktop is effectively the same as using Get Data in Power BI to import your file
from a local drive or connecting to it on OneDrive. Here’s the quick how to, but you can see Publish from Power BI
Desktop to learn more.
1. In Power BI Desktop, click File > Publish > Publish to Power BI, or click Publish on the ribbon.

2. Sign in to Power BI. You'll only need to do this the first time.
When complete, you'll get a link to open your report in your Power BI site.

Next steps
Explore your data - Once you get data and reports from your file into Power BI, it's time to explore. If your file
already has reports in it, they'll appear in the navigator pane in Reports. If your file just had data, you can create
new reports; just right-click the new dataset and then click Explore.
Refresh external data sources - If your Power BI Desktop file connects to external data sources, you can setup
scheduled refresh to make sure your dataset is always up-to-date. In most cases, setting up scheduled refresh is
quite easy to do, but going into the details is outside the scope of this article. See Data refresh in Power BI to learn
more.
 Edit parameter settings in the Power BI service
1/14/2019 • 2 minutes to read • Edit Online

Report creators add query parameters to reports in Power BI Desktop. Parameters allow them to make parts of
reports depend on one or more parameter values. For example, a report creator may create a parameter that
restricts the data to a single country/region, or a parameter that defines acceptable formats for fields like dates,
time, and text.

Review and edit parameters in Power BI service

As a report creator, you define parameters in Desktop. When you publish that report to Power BI service, the
parameter settings and selections travel with it. You can review and edit some parameter settings in the Power BI
service -- not parameters that restrict the available data, but parameters that define and describe acceptable values.

1. In Power BI service, select the cog icon to open Settings.

2. Select the tab for Datasets and highlight a dataset in the list.

3. Expand Parameters. If the selected dataset has no parameters, you'll see a message with a link to Learn
more about query parameters. But if the dataset does have parameters, expanding the Parameters heading
will reveal those parameters.
 Review the parameter settings and make changes if needed. Greyed out fields aren't editable.

Next steps
An ad-hoc way to add simple parameters is by modifying the URL.
 Get data from Comma Separated Value (.CSV) files
1/14/2019 • 2 minutes to read • Edit Online

Comma separated value files, often known as a .CSV, are simple text files with rows of data where each value is
separated by a comma. These types of files can contain very large amounts of data within a relatively small file size,
making them an ideal data source for Power BI. You can download a sample .CSV file here.
If you have a .CSV, it’s time to get it into your Power BI site as a dataset where you can begin exploring your data,
create some dashboards, and share your insights with others.

TIP
Many organizations output a .CSV with updated data each day. To make sure your dataset in Power BI stays in-sync with
your updated file, be sure the file is saved to OneDrive with the same name.

Where your file is saved makes a difference

Local - If you save your .CSV file to a local drive on your computer or another location in your organization, from
Power BI you can import your file into Power BI. Your file will actually remain on your local drive, so the whole file
isn’t really imported into Power BI. What really happens is a new dataset is created in Power BI and data from the
.CSV file is loaded into the dataset.
OneDrive - Business – If you have OneDrive for Business and you sign into it with the same account you sign
into Power BI with, this is by-far the most effective way to keep your .CSV file and your dataset, reports, and
dashboards in Power BI in-sync. Because both Power BI and OneDrive are in the cloud, Power BI connects to your
file on OneDrive about every hour. If any changes are found, your dataset, reports, and dashboards are
automatically updated in Power BI.
OneDrive - Personal – If you save your files to your own OneDrive account, you’ll get many of the same benefits
as you would with OneDrive for Business. The biggest difference is when you first connect to your file (using Get
Data > Files > OneDrive – Personal) you’ll need to sign in to your OneDrive with your Microsoft account, which is
usually different from what you use to sign in to Power BI. When signing into your OneDrive with your Microsoft
account, be sure to select the Keep me signed in option. This way, Power BI will be able to connect to your file
about every hour and make sure your dataset in Power BI is in-sync.
SharePoint Team -Sites – Saving your Power BI Desktop files to SharePoint – Team Sites is much the same as
saving to OneDrive for Business. The biggest difference is how you connect to the file from Power BI. You can
specify a URL or connect to the root folder.

Import or connect to a .CSV file

IMPORTANT
The maximum file size you can import into Power BI is 1 gigabyte.

1. In Power BI, in the navigator pane, click Get Data.

2. In Files, click Get.

3. Find your file.

Next steps
Explore your data - Once you get data from your file into Power BI, it's time to explore. Just right-click the new
dataset and then click Explore.
Schedule refresh - If your file is saved to a local drive, you can setup scheduled refresh so your dataset and
reports in Power BI stay up-to-date. To learn more, see Data refresh in Power BI. If your file is saved to OneDrive,
Power BI will automatically synchronize with it about every hour.
 Real-time streaming in Power BI
1/14/2019 • 14 minutes to read • Edit Online

With Power BI real-time streaming, you can stream data and update dashboards in real-time. Any visual or
dashboard that can be created in Power BI can also be created to display and update real-time data and visuals.
The devices and sources of streaming data can be factory sensors, social media sources, service usage metrics, and
anything else from which time-sensitive data can be collected or transmitted.

This article shows you how to set up real-time streaming dataset in Power BI. But before we get to that, it's
important to understand the types of real-time datasets that are designed to display in tiles (and dashboards), and
how those datasets differ.

Types of real-time datasets

There are three types of real-time datasets which are designed for display on real-time dashboards:
Push dataset
Streaming dataset
PubNub streaming dataset
First let's understand how these datasets differ from one another (this section), then we discuss how to push data
into those each of these datasets.
Push dataset
With a push dataset, data is pushed into the Power BI service. When the dataset is created, the Power BI service
automatically creates a new database in the service to store the data. Since there is an underlying database that
continues to store the data as it comes in, reports can be created with the data. These reports and their visuals are
just like any other report visuals, which means you can use all of Power BI’s report building features to create
visuals, including custom visuals, data alerts, pinned dashboard tiles, and more.
Once a report is creating using the push dataset, any of its visuals can be pinned to a dashboard. On that
dashboard, visuals update in real-time whenever the data is updated. Within the service, the dashboard is
triggering a tile refresh every time new data is received.
There are two considerations to note about pinned tiles from a push dataset:
Pinning an entire report using the pin live page option will not result in the data automatically being updated.
Once a visual is pinned to a dashboard, you can use Q&A to ask questions of the push dataset in natural
language. Once you make a Q&A query, you can pin the resulting visual back to the dashboard, and that
dashboard will also update in real-time.
Streaming dataset
With a streaming dataset, data is also pushed into the Power BI service, with an important difference: Power BI
only stores the data into a temporary cache, which quickly expires. The temporary cache is only used to display
visuals which have some transient sense of history, such as a line chart that has a time window of one hour.
With a streaming dataset, there is no underlying database, so you cannot build report visuals using the data that
flows in from the stream. As such, you cannot make use of report functionality such as filtering, custom visuals, and
other report functions.
The only way to visualize a streaming dataset is to add a tile and use the streaming dataset as a custom
streaming data data source. The custom streaming tiles that are based on a streaming dataset are optimized for
quickly displaying real-time data. There is very little latency between when the data is pushed into the Power BI
service and when the visual is updated, since there’s no need for the data to be entered into or read from a
database.
In practice, streaming datasets and their accompanying streaming visuals are best used in situations when it is
critical to minimize the latency between when data is pushed and when it is visualized. In addition, it's best practice
to have the data pushed in a format that can be visualized as-is, without any additional aggregations. Examples of
data that's ready as-is include temperatures, and pre-calculated averages.
PubNub streaming dataset
With a PubNub streaming dataset, the Power BI web client uses the PubNub SDK to read an existing PubNub
data stream, and no data is stored by the Power BI service.
As with the streaming dataset, with the PubNub streaming dataset there is no underlying database in Power
BI, so you cannot build report visuals against the data that flows in, and cannot take advantage of report
functionality such as filtering, custom visuals, and so on. As such, the PubNub streaming dataset can also only
be visualized by adding a tile to the dashboard, and configuring a PubNub data stream as the source.
Tiles based on a PubNub streaming dataset are optimized for quickly displaying real-time data. Since Power BI
is directly connected to the PubNub data stream, there is very little latency between when the data is pushed into
the Power BI service and when the visual is updated.
Streaming dataset matrix
The following table (or matrix, if you like) describes the three types of datasets for real-time streaming, and lists
capabilities and limitations of each.
 NOTE
See this article for information on Push limits on how much data can be pushed in.

Pushing data to datasets

The previous section described the three primary types of real-time datasets you can use in real-time streaming,
and how they differ. This section describes how to create and push data into those datasets.
There are three primary ways you can push data into a dataset:
Using the Power BI REST APIs
Using the Streaming Dataset UI
Using Azure Stream Analytics
Let's take a look at each of those approaches in turn.
Using Power BI REST APIs to push data
Power BI REST APIs can be used to create and send data to push datasets and to and streaming datasets. When
you create a dataset using Power BI REST APIs, the defaultMode flag specifies whether the dataset is push or
streaming. If no defaultMode flag is set, the dataset defaults to a push dataset.
If the defaultMode value is set to pushStreaming, the dataset is both a push and streaming dataset, providing the
benefits of both dataset types.

NOTE
When using datasets with the defaultMode flag set to pushStreaming, if a request exceeds the 15Kb size restriction for a
streaming dataset, but is less than the 16MB size restriction of a push dataset, the request will succeed and the data will be
updated in the push dataset. However, any streaming tiles will temporarily fail.

Once a dataset is created, use the REST APIs to push data using the PostRows API.
All requests to REST APIs are secured using Azure AD OAuth.
Using the Streaming Dataset UI to push data
In the Power BI service, you can create a dataset by selecting the API approach as shown in the following image.

When creating the new streaming dataset, you can select to enable Historic data analysis as shown below, which
has a significant impact.
When Historic data analysis is disabled (it is disabled by default), you create a streaming dataset as described
earlier in this article. When Historic data analysis is enabled, the dataset created becomes both a streaming
dataset and a push dataset. This is equivalent to using the Power BI REST APIs to create a dataset with its
defaultMode set to pushStreaming, as described earlier in this article.

NOTE
For streaming datasets created using the Power BI service UI, as described in the previous paragraph, Azure AD
authentication is not required. In such datasets, the dataset owner receives a URL with a rowkey, which authorizes the
requestor to push data into the dataset with out using an Azure AD OAuth bearer token. Take now, however, that the Azure
AD (AAD) approach still works to push data into the dataset.

Using Azure Stream Analytics to push data

You can add Power BI as an output within Azure Stream Analytics (ASA), and then visualize those data streams
in the Power BI service in real time. This section describes technical details about how that process occurs.
Azure Stream Analytics uses the Power BI REST APIs to create its output data stream to Power BI, with
defaultMode set to pushStreaming (see earlier sections in this article for information on defaultMode), which
results in a dataset that can take advantage of both push and streaming. During creation of the dataset, Azure
Stream Analytics also sets the *retentionPolicy flag to basicFIFO; with that setting, the database supporting its
push dataset stores 200,000 rows, and after that limit is reached, rows are dropped in a first-in first-out (FIFO )
fashion.
Cau t i on

If your Azure Stream Analytics query results in very rapid output to Power BI (for example, once or twice per
second), Azure Stream Analytics will begin batching those outputs into a single request. This may cause the request
size to exceed the streaming tile limit. In that case, as mentioned in previous sections, streaming tiles will fail to
render. In such cases, the best practice is to slow the rate of data output to Power BI; for example, instead of a
maximum value every second, set it to a maximum over 10 seconds.

Set up your real-time streaming dataset in Power BI

Now that we've covered the three primary types of datasets for real-time streaming, and the three primary ways
you can push data into a dataset, let's get your real-time streaming dataset working in Power BI.
To get started with real-time streaming, you need to choose one of the two ways that streaming data can be
consumed in Power BI:
tiles with visuals from streaming data
datasets created from streaming data that persist in Power BI
With either option, you'll need to set up Streaming data in Power BI. To do this, in your dashboard (either an
existing dashboard, or a new one) select Add a tile and then select Custom streaming data.

If you don't have streaming data set up yet, don't worry - you can select manage data to get started.
On this page, you can input the endpoint of your streaming dataset if you already have one created (into the text
box). If you don't have a streaming dataset yet, select the plus icon ( + ) in the upper right corner to see the
available options to create a streaming dataset.

When you click on the + icon, you see two options:

The next section describes these options, and goes into more detail about how to create a streaming tile or how to
create a dataset from the streaming data source, which you can then use later to build reports.

Create your streaming dataset with the option you like best
There are two ways to create a real-time streaming data feed that can be consumed and visualized by Power BI:
Power BI REST API using a real-time streaming endpoint
PubNub
The next sections look at each option in turn.
Using the POWER BI REST API
Power BI REST API - Recent improvements to the Power BI REST API are designed to make real-time streaming
easier for developers. When you select API from the New streaming dataset window, you're presented with
entries to provide that enable Power BI to connect to and use your endpoint:

If you want Power BI to store the data that's sent through this data stream, enable Historic data analysis and you'll
be able to do reporting and analysis on the collected data stream. You can also learn more about the API.
Once you successfully create your data stream, you're provided with a REST API URL endpoint, which your
application can call using POST requests to push your data to Power BI streaming data dataset you created.
When making POST requests, you should ensure the request body matches the sample JSON provided by the
Power BI user interface. For example, wrap your JSON objects in an array.
Using PubNub
With the integration of PubNub streaming with Power BI, you can use your low -latency PubNub data streams
(or create new ones) and use them in Power BI. When you select PubNub and then select Next, you see the
following window:
 WARNING
PubNub channels can be secured by using a PubNub Access Manager (PAM) authentication key. This key will be shared with
all users who have access to the dashboard. You can learn more about PubNub access control.

PubNub data streams are often high volume, and are not always suitable in their original form for storage and
historical analysis. To use Power BI for historical analysis of PubNub data, you'll have to aggregate the raw
PubNub stream and send it to Power BI. One way to do that is with Azure Stream Analytics.

Example of using real time streaming in Power BI

Here's a quick example of how real time streaming in Power BI works. You can follow along with this sample to see
for yourself the value of real time streaming.
In this sample, we use a publicly available stream from PubNub. Here are the steps:
1. In the Power BI service, select a dashboard (or create a new one) and select Add tile > Custom
Streaming Data and then select the Next button.
2. If you don't have and streaming data sources yet, select the manage data link (just above the Next button),
then select + Add streaming data from the link in the upper-right of the window. Select PubNub and then
select Next.
3. Create a name for your dataset, then paste in the following values into the window that appears, then select
Next:
Subscribe key:

sub-c-5f1b7c8e-fbee-11e3-aa40-02ee2ddab7fe

Channel:

pubnub-sensor-network
4. In the following window, just select the defaults (which are automatically populated), then select Create.
5. Back in your Power BI workspace, create a new dashboard and then add a tile (see above for steps, if you
need them). This time when you create a tile and select Custom Streaming Data, you have a streaming
data set to work with. Go ahead and play around with it. Adding the number fields to line charts, and then
adding other tiles, you can get a real time dashboard that looks like the following:
Give it a try, and play around with the sample dataset. Then go create your own datasets, and stream live data to
Power BI.

Questions and answers

Here are some common questions about real-time streaming in Power BI, and answers.
Can I use filters on push dataset? How about streaming dataset?
Unfortunately, streaming datasets do not support filtering. For push datasets, you can create a report, filter the
report, and then pin the filtered visuals to a dashboard. However, there is no way to change the filter on the visual
once it's on the dashboard.
Separately, you can pin the live report tile to the dashboard, in which case you can change the filters. However, live
report tiles will not update in real-time as data is pushed in – you'll have to manually update the visual by using the
refresh dashboard tiles option in the More menu.
When applying filters to push datasets with DateTime fields with millisecond precision, equivalence operators are
not supported. However, operators such as greater than (>) or less than (<) do operate properly.
How do I see the latest value on a push dataset? How about streaming dataset?
Streaming datasets are designed for displaying the latest data. You can use the Card streaming visual to easily see
latest numeric values. Unfortunately, the card does not support data of type DateTime or Text. For push datasets,
assuming you have a timestamp in the schema, you can try creating a report visual with the last N filter.
Can I connect to push or streaming datasets in Power BI Desktop?
Unfortunately, this is not available at this time.
Given the previous question, how can I do any modeling on real-time datasets?
Modeling is not possible on a streaming dataset, since the data is not stored permanently. For a push dataset, you
can use the update dataset/table REST APIs to add measures and relationships.
How can I clear all the values on a push dataset? How about streaming dataset?
On a push dataset, you can use the delete rows REST API call. There is currently no way to clear data from a
streaming dataset, though the data will clear itself after an hour.
I set up an Azure Stream Analytics output to Power BI, but I don’t see it appearing in Power BI – what’s wrong?
Here’s a checklist you can use to troubleshoot the issue:
1. Restart the Azure Stream Analytics job (jobs created before the streaming GA release will require a restart)
2. Try reauthorizing your Power BI connection in Azure Stream Analytics
3. Which workspace did you specify in the Azure Stream Analytics output? In the Power BI service, are you
checking in that (same) workspace?
4. Does the Azure Stream Analytics query explicitly output to the Power BI output? (using the INTO keyword)
5. Does the Azure Stream Analytics job have data flowing through it? The dataset will only get created when there
is data being transmitted.
6. Can you look into the Azure Stream Analytics logs to see if there are any warnings or errors?

Next steps
Here are a few links you might find useful when working with real-time streaming in Power BI:
Overview of the Power BI REST API with real-time data
Azure Stream Analytics
 Publish to Power BI from Excel 2016
1/14/2019 • 4 minutes to read • Edit Online

With Excel 2016, you can publish your Excel workbooks right to your Power BI site, where you can create highly
interactive reports and dashboards based on your workbook’s data. You can then share your insights with others
in your organization.
Before we go any further, there are few things to keep in mind:
Before you can publish to Power BI, your workbook must be saved to OneDrive for Business.
The account you use to sign in to Office, OneDrive for Business, and Power BI must be the same account.
You cannot publish an empty workbook or a workbook that doesn’t have any Power BI supported content.
You cannot publish encrypted or password protected workbooks, or workbooks with Information Protection
Management.
Publishing to Power BI requires modern authentication be enabled (default). If disabled, the Publish option is
not available from the File menu.

To publish your Excel workbook

In Excel, select File > Publish.
Local file publishing
Starting in the February 2017 update, Excel 2016 supports publishing of local Excel files. They do not need to be
saved to OneDrive for Business or SharePoint Online.

IMPORTANT
Only Excel 2016 with an Office 365 subscription will see the experience to publish with local files. Excel 2016 standalone
installation will still have the "Publish" only behavior which requires the excel workbook be saved to OneDrive for Business
or SharePoint Online.

When you select Publish, you will be able to select the workspace you want to publish to. This can be your
personal or group workspace that you have access to.

you’ll get two options on how to get your workbook into Power BI.
Once published, it is kept as a copy in Power BI, separate from the local file. If you want to update the file in Power
BI, you need to publish the updated version again. You can refresh the data and set scheduled refresh on the
workbook or the dataset in Power BI.
Publishing from Excel Standalone
If your workbook isn’t already saved to OneDrive, you’ll need to save it there first. Select Save to Cloud and
choose a location in OneDrive for Business.

Once your workbook is saved to OneDrive, when you select Publish, you’ll get two options on how to get your
workbook into Power BI.
Upload your workbook to Power BI
When you choose this option, your workbook will appear in Power BI just like it would in Excel Online. But, unlike
Excel Online, you’ll have some great features to help you pin elements from your worksheets to dashboards.
You can’t edit your workbook in when open in Power BI, but if you need to make some changes, you can select
Edit, and then choose to edit your workbook in Excel Online or open it in Excel on your computer. Any changes
you make are saved to the workbook on OneDrive.
When you upload, no dataset is created in Power BI. Your workbook will appear in Reports, in your workspace
navigation pane. Workbooks uploaded to Power BI have a special Excel icon, identifying them as Excel workbooks
that have been uploaded.
Choose this option if you only have data in worksheets, or you have PivotTables and Charts you want to see in
Power BI. Using Upload from Publish to Power BI in Excel is pretty much the same as using Get Data > File >
OneDrive for Business > Connect, Manage and View Excel in Power BI from Power BI in your browser.
Export workbook data to Power BI
When you choose this option, any supported data in tables and/or a data model are exported into a new dataset
in Power BI. If you have any Power View sheets, those will be re-created in Power BI as reports.
You can continue editing your workbook. When your changes are saved, they’ll be synchronized with the dataset
in Power BI, usually within about an hour. If you need more immediate gratification, you can just select Publish
again, and your changes are exported right then and there. Any visualizations you have in reports and dashboards
will be updated, too.
Choose this option if you’ve used Get & Transform data or Power Pivot to load data into a data model, or if your
workbook has Power View sheets with visualizations you want to see in Power BI.
Using Export from Publish to Power BI in Excel is pretty much the same as using Get Data > File > OneDrive for
Business > Export Excel data into Power BI from Power BI in your browser.

Publishing
When you choose either option, Excel will sign in to Power BI with your current account, and then publish your
workbook to your Power BI site. Keep an eye on the status bar in Excel. It shows how things are going.
When complete, you can go to Power BI right from Excel.

Next steps
Excel data in Power BI
More questions? Try the Power BI Community
 Reduce the size of an Excel workbook to view it in
Power BI
1/14/2019 • 2 minutes to read • Edit Online

You can upload any Excel workbook smaller than 1 GB to Power BI. An Excel workbook can have two parts: a Data
Model, and the rest of the report—the core worksheet contents. If the report meets the following size limits, you
can save it to OneDrive for Business, connect to it from Power BI, and view it in Excel Online:
The workbook as a whole can be up to 1 GB.
The core worksheet contents can be up to 30 MB.

What makes core worksheet contents larger than 30 MB

Here are some elements that can make the core worksheet contents larger than 30 MB:
Images.
Shaded cells. Remove a cell shading format.
Colored worksheets. Remove a sheet background.
Text boxes.
Clip art.
Consider removing these elements, if possible.
If the report has a Data Model, you have some other options:
Remove data from Excel worksheets, and store it in the Data Model instead. See “Remove data from
worksheets” below for details.
Create a memory-efficient Data Model to reduce the overall size of the report.
To make any of these changes, you need to edit the workbook in Excel.
Read more about file size limits for Excel workbooks in SharePoint Online.

Remove data from worksheets

If you import data into Excel from the Power Query tab or the Excel Data tab, the workbook might have the same
data in an Excel table and in the Data Model. Large tables in Excel worksheets may make the core worksheet
contents more than 30 MB. Removing the table in Excel and keeping the data in the Data Model can greatly reduce
the core worksheet contents of the report.
When you import data into Excel, follow these tips:
In Power Query: Clear the Load to worksheet box.
The data is imported only into the Data Model, with no data in Excel worksheets.
From the Excel Data tab, if you previously checked Table in the import wizard: Go to Existing
Connections > click the connection > Only create connection. Delete the original table or tables created
during the initial import.
From the Excel Data tab: don’t check Table in the Import Data box.
Workbook Size Optimizer
If your workbook contains a data model, you can run the workbook size optimizer to reduce the size of your
workbook. Download Workbook Size Optimizer.

Related info
Create a memory-efficient Data Model
Use OneDrive for Business links in Power BI Desktop
 Azure and Power BI
1/30/2019 • 3 minutes to read • Edit Online

With Azure services and Power BI, you can turn your data processing efforts into analytics and reports that
provide real-time insights into your business. Whether your data processing is cloud-based or on-premises,
straightforward, or complex, single-sourced or massively scaled, warehoused, or real-time, Azure and Power BI
have the built-in connectivity and integration to bring your business intelligence efforts to life.

Power BI has a multitude of Azure connections available, and the business intelligence solutions you can create
with those services are as unique as your business. You can connect as few as one Azure data source, or a handful,
then shape and refine your data to build customized reports.

Azure SQL Database and Power BI

You can start with a straightforward connection to an Azure SQL Database, and create reports to monitor the
progress of your business. Using the Power BI Desktop, you can create reports that identify trends and key
performance indicators that move your business forward.

There's plenty more information for you to learn about Azure SQL Database.

Transform, shape, and merge your cloud data

Do you have more complex data, and all sorts of sources? No problem. With Power BI Desktop and Azure
services, connections are just a tap of the Get Data dialog away. Within the same Query you can connect to your
Azure SQL Database, your Azure HDInsight data source, and your Azure Blob Storage (or Azure Table
Storage), then select only the subsets within each that you need, and refine it from there.
You can create different reports for different audiences too, using the same data connections and even the same
Query. Just build a new report page, refine your visualizations for each audience, and watch it keep the business in
the know.

For more information, take a look at the following resources:

Azure SQL Database
Azure HDInsight
Azure Storage (Blob storage and Table storage)

Get complex (and ahead) using Azure Services and Power BI

You can expand as much as you need with Azure and Power BI. Harness multi-source data processing, make use of
massive real-time systems, use Stream Analyticsand Event Hubs, and coalesce your varied SaaS services into
business intelligence reports that give your business an edge.
Context insights with Power BI Embedded analytics
Embed stunning, interactive data visualizations in applications, websites, portals, and more, to take advantage of
your business data. With Power BI Embedded as a resource in Azure, you can easily embed interactive reports and
dashboards, so your users can enjoy consistent, high-fidelity experiences across devices. Power BI used with
embedding analytics is to help you through your journey from Data -> Knowledge -> Insights -> Actions.
Furthermore, you can extend the value of Power BI and Azure also by embedding analytics in your organization's
internal applications and portals.
There's lots of information about Power BI APIs in the Power BI Developer Portal.
For more information, see What can developers do with Power BI?.

Embed your Power BI data within your app

Embed stunning, interactive data visualizations in applications, websites, portals, and more, to showcase your
business data in context. Using Power BI Embedded in Azure, you can easily embed interactive reports and
dashboards, so your users can enjoy consistent, high-fidelity experiences across devices.

What could you do with Azure and Power BI?

There are all sorts of scenarios where Azure and Power BI can be combined - the possibilities and opportunities
are as unique as your business. For more information about Azure services, check out this overview page, which
describes Data Analytics Scenarios using Azure, and learn how to transform your data sources into intelligence
that drives your business ahead.
 Power BI and Azure egress
1/14/2019 • 2 minutes to read • Edit Online

When using Power BI with Azure data sources, you can avoid Azure egress charges by making sure your Power BI
tenant is in the same region as your Azure data sources.
When your Power BI tenant is deployed in the same Azure region as you deploy your data sources, you do not
incur egress charges for scheduled refresh and DirectQuery interactions.

Determining where your Power BI tenant is located

To find out where your Power BI tenant is located, see the where is my Power BI tenant located article.
For Power BI Premium Multi-Geo customers, if your Power BI tenant is not in the optimal location for some of
your Azure-based data sources, you can deploy Power BI Premium Multi-Geo in the desired Azure region and
benefit from having your Power BI tenant and Azure data sources in the same Azure region.

Next steps
For more information about Power BI Premium or Multi-Geo, take a look at the following resources:
What is Microsoft Power BI Premium?
How to purchase Power BI Premium
Multi-Geo support for Power BI Premium (Preview )
Where is my Power BI tenant located?
Power BI Premium FAQ
 Azure SQL Data Warehouse with DirectQuery
1/14/2019 • 3 minutes to read • Edit Online

Azure SQL Data Warehouse with DirectQuery allows you to create dynamic reports based on data and metrics you
already have in Azure SQL Data Warehouse. With DirectQuery, queries are sent back to your Azure SQL Data
Warehouse in real time as you explore the data. Real-time queries, combined with the scale of SQL Data
Warehouse enables users to create dynamic reports in minutes against terabytes of data. In addition, the
introduction of the Open in Power BI button allows users to directly connect Power BI to their SQL Data
Warehouse without having to manually specify the information.
When using the SQL Data Warehouse connector:
Specify the fully qualified server name when connecting (see below for details)
Ensure firewall rules for the server are configured to "Allow access to Azure services"
Every action such as selecting a column or adding a filter will directly query the data warehouse
Tiles are set to refresh approximately every 15 minutes and refresh does not need to be scheduled. Refresh can
be adjusted in the Advanced settings when you connect.
Q&A isn't available for DirectQuery datasets
schema changes aren't picked up automatically
These restrictions and notes may change as we continue to improve the experiences. The steps to connect are
detailed below.

Using the 'Open in Power BI' button

IMPORTANT
We have been improving our connectivity to Azure SQL Data Warehouse. For the best experience to connect to your Azure
SQL Data Warehouse data source, use Power BI Desktop. Once you've built your model and report, you can publish it to the
Power BI service. The direct connector for Azure SQL Data Warehouse in the Power BI service is now deprecated.

The easiest way to move between your SQL Data Warehouse and Power BI is with the Open in Power BI button
within the Azure portal. This button allows you to seamlessly begin creating new dashboards in Power BI.
1. To get started, navigate to your SQL Data Warehouse instance in the Azure portal. Note that SQL Data
Warehouse only have a presence in the Azure Preview portal at this time.
2. Click the Open in Power BI button

3. If we aren't able to sign you in directly or if you do not have a Power BI account, you'll need to sign in.
4. You'll be directed to the SQL Data Warehouse connection page, with the information from your SQL Data
Warehouse pre-populated. Enter your credentials and hit connect to create a connection.

Connecting through Power BI

SQL Data Warehouse is also listed on the Power BI Get Data page.
1. Select Get Data at the bottom of the left navigation pane.

2. Within Databases, select Get.

3. Select SQL Data Warehouse > Connect.

4. Enter the necessary information to connect. The Finding Parameters section below shows where this data
can be located in your Azure Portal.
 NOTE
The username will be a user that is defined in your Azure SQL Data Warehouse instance.

5. Drill into the dataset by selecting the new tile or the newly created dataset, indicated by the asterisk. This
dataset will have the same name as your database.

6. You can explore all of the tables and columns. Selecting a column will send a query back to the source,
dynamically creating your visual. Filters will also be translated into queries back to your data warehouse.
These visuals can be saved in a new report and pinned back to your dashboard.
Finding Parameter Values
Your fully qualified server name and database name can be found in the Azure portal. Note that SQL Data
Warehouse only have a presence in the Azure Preview portal at this time.

NOTE
If your Power BI tenant is in the same region as the Azure SQL Data Warehouse there will be no egress charges. You can find
where your Power BI tenant is located using these instructions.

Next steps
What is Power BI?
Get Data for Power BI
Azure SQL Data Warehouse
More questions? Try the Power BI Community
 Azure SQL Database with DirectQuery
1/14/2019 • 2 minutes to read • Edit Online

Learn how you can connect directly to Azure SQL Database and create reports that use live data. You can keep
your data at the source and not in Power BI.
With DirectQuery, queries are sent back to your Azure SQL Database as you explore the data in the report view.
This experience is suggested for users who are familiar with the databases and entities they connect to.
Notes:
Specify the fully qualified server name when connecting (see below for more details)
Ensure firewall rules for the database are configured to "Allow access to Azure services"
Every action such as selecting a column or adding a filter will send a query back to the database
Tiles are refreshed every hour (refresh does not need to be scheduled). This can be adjusted in the Advanced
settings when you connect.
Q&A is not available for DirectQuery datasets
Schema changes are not picked up automatically
These restrictions and notes may change as we continue to improve the experiences. The steps to connect are
detailed below.

IMPORTANT
We have been improving our connectivity to Azure SQL Database. For the best experience to connect to your Azure SQL
Database data source, use Power BI Desktop. Once you've built your model and report, you can publish it to the Power BI
service. The direct connector for Azure SQL Database in the Power BI service is now deprecated.

Power BI Desktop and DirectQuery

In order to connect to Azure SQL Database using DirectQuery, you will need to use Power BI Desktop. This
approach provides additional flexibility and capabilities. Reports created using Power BI Desktop can then be
published to the Power BI service. You can learn more about how to connect to Azure SQL Database using
DirectQuery within Power BI Desktop.

Single sign-on
After you publish an Azure SQL DirectQuery dataset to the service, you can enable single sign-on (SSO ) via Azure
Active Directory (Azure AD ) OAuth2 for your end users.
To enable SSO, go to settings for the dataset, open the Data Sources tab, and check the SSO box.
When the SSO option is enabled and your users access reports built atop the data source, Power BI sends their
authenticated Azure AD credentials in the queries to the Azure SQL database. This enables Power BI to respect the
security settings that are configured at the data source level.
The SSO option takes affect across all datasets that use this data source. It does not affect the authentication
method used for import scenarios.

NOTE
Azure Multi-Factor Authentication (MFA) is not supported. Users who want to use SSO with Azure SQL DirectQuery must be
exempted from MFA.

Finding Parameter Values

Your fully qualified server name and database name can be found in the Azure Portal.
Next steps
Use DirectQuery in Power BI Desktop
What is Power BI?
Get Data for Power BI
More questions? Try the Power BI Community
 SQL Server Analysis Services live data in Power BI
2/13/2019 • 2 minutes to read • Edit Online

In Power BI, there are two ways you can connect to a live SQL Server Analysis Services server. In Get data, you
can connect to a SQL Server Analysis Services server, or you can connect to a Power BI Desktop file, or Excel
workbook, that already connects to an Analysis Services server. As a best practice, Microsoft strongly recommends
using Power BI Desktop because of the richness of the toolset and the ability to maintain a backup copy of the
Power BI Desktop file locally.

IMPORTANT
In order to connect to a live Analysis Services server, an On-premises data gateway must be installed and configured by
an administrator. For more information, see On-premises data gateway.
When you use the gateway, your data remains on-premises. The reports you create based on that data are saved in the
Power BI service.
Q&A natural language querying is in preview for Analysis Services live connections.

To connect to a model from Get data

1. In My Workspace, select Get data. You can also change to a group workspace, if one is available.

2. Select Databases & More.

3. Select SQL Server Analysis Services > Connect.

4. Select a server. If you don't see any servers listed here, it means either a gateway, and data source, are not
configured, or your account is not listed in the Users tab of the data source, in the gateway. Check with your
administrator.
5. Select the model you want to connect to. This could be either Tabular or Multidimensional.
After you connect to the model, it will appear in your Power BI site in My Workspace/Datasets. If you were
switched to a group workspace, then the dataset will appear within the group.

Dashboard tiles
If you pin visuals from a report to the dashboard, the pinned tiles are automatically refreshed every 10 minutes. If
the data in your on-premises Analysis Services server is updated, the tiles will get auto-updated after 10 minutes.

Common Issues
Cannot load the model schema error - This error occurs when the user connecting to SSAS does not have
access to the SSAS database, cube and model.

Next steps
On-premises data gateway
Manage Analysis Services data sources
Troubleshooting the On-premises data gateway
More questions? Try the Power BI Community
 Configuring scheduled refresh
1/14/2019 • 4 minutes to read • Edit Online

NOTE
After two months of inactivity, scheduled refresh on your dataset is paused. See the Schedule refresh section later in this
article for more information.

If your dataset supports scheduled refresh, by using Refresh Now and Schedule Refresh, there are a few
requirements and settings important for refresh to be successful. These are Gateway connection, Data
Source Credentials, and Schedule Refresh. Let’s take a closer look at each.
This will describe the options available for both the Power BI Gateway – Personal and the On-premises data
gateway.
To get to the schedule refresh screen, you can do the following.
1. Select the ellipsis (...) next to a dataset listed under Datasets.
2. Select Schedule Refresh.

Gateway connection
You will see different options here depending on whether you have a personal, or enterprise, gateway online and
available.
If no gateway is available, you will see Gateway settings disabled. You will also see a message indicating how
to install the personal gateway.
If you have a personal gateway configured, it will be available to select, if it is online. It will show offline if it is not
available.

You can also select the enterprise gateway if one is available for you. You will only see an enterprise gateway
available if your account is listed in the Users tab of the data source configured for a given gateway.

Data source credentials

Power BI Gateway - Personal
If you are using the personal gateway to refresh data, you will need to supply the credentials used to connect to
the back end data source. If you connected to a content pack, from an online service, the credentials you entered
to connect will be carried over for scheduled refresh.

You’re only required to sign in to data sources the first time you use refresh on that dataset. Once entered, those
credentials are retained with the dataset.

NOTE
For some authentication methods, if the password you use to sign into a data source expires or is changed, you'll need to
change it for the data source in Data Source Credentials too.

When things go wrong, the problem usually has something to do with either the gateway being offline because
it could not sign in to Windows and start the service, or Power BI could not sign in to the data sources in order
to query for updated data. If refresh fails, check the dataset’s settings. If the gateway service is offline, Gateway
Status is where you’ll see the error. If Power BI cannot sign into the data sources, you’ll see an error in Data
Source Credentials.
On-premises data gateway
If you are using the On-premises data gateway to refresh data, you do not need to supply credentials as they are
defined for the data source by the gateway administrator.

NOTE
When connecting to on-premises SharePoint for data refresh, Power BI supports only Anonymous, Basic, and Windows
(NTLM/Kerberos ) authentication mechanisms. Power BI does not support ADFS or any Forms-Based Authentication
mechanisms for data refresh of on-premises SharePoint data sources.

Schedule refresh
The scheduled refresh section is where you define the frequency and time slots to refresh the dataset. Some data
sources do not require a gateway present in order to be available to configure. Others will require a gateway.
You must set the Keep your data up to date slider to Yes in order to configure the settings.

NOTE
The Power BI service targets initiating the refresh of your data within 15 minutes of your scheduled refresh time.
 NOTE
After two months of inactivity, scheduled refresh on your dataset is paused. A dataset is considered inactive when no user
has visited any dashboard or report built on the dataset. At that time, the dataset owner is sent an email indicating the
scheduled refresh is paused, and the refresh schedule for the dataset is displayed as disabled. To resume scheduled
refresh, simply revisit any dashboard or report built on the dataset.

What’s supported?
Certain datasets are supported against different gateways for scheduled refresh. Here is a reference to
understand what is available.
Power BI Gateway - Personal
Power BI Desktop
All online data sources shown in Power BI Desktop’s Get Data and Query Editor.
All on-premises data sources shown in Power BI Desktop’s Get Data and Query Editor except for Hadoop file
(HDFS ) and Microsoft Exchange.

Excel

NOTE
In Excel 2016, and later, Power Query is now listed on the Data section of the ribbon, under Get & Transform data.

All online data sources shown in Power Query.

All on-premises data sources shown in Power Query except for Hadoop file (HDFS ) and Microsoft Exchange.
All online data sources shown in Power Pivot.*
All on-premises data sources shown in Power Pivot except for Hadoop file (HDFS ) and Microsoft Exchange.
On-premises data gateway
DATA SOURCE

Analysis Services Tabular

Analysis Services Multidimensional

SQL Server

SAP HANA

Oracle

Teradata

File

Folder

SharePoint list (on-premises)

 DATA SOURCE

Web

OData

IBM DB2

MySQL

Sybase

SAP BW

IBM Informix Database

ODBC

Troubleshooting
Sometimes refreshing data may not go as expected. Typically this will be an issue connected with a gateway.
Take a look at the gateway troubleshooting articles for tools and known issues.
Troubleshooting the On-premises data gateway
Troubleshooting the Power BI Gateway - Personal

Next steps
Data refresh in Power BI
Power BI Gateway - Personal
On-premises data gateway
Troubleshooting the On-premises data gateway
Troubleshooting the Power BI Gateway - Personal
More questions? Try asking the Power BI Community
 Refresh a dataset created from a Power BI Desktop
file on a local drive
1/14/2019 • 2 minutes to read • Edit Online

What’s supported?
In Power BI, Refresh Now and Schedule Refresh is supported for datasets created from Power BI Desktop files
imported from a local drive where Get Data/Query Editor is used to connect to and load data from any of the
following data sources:
Power BI Gateway - Personal
All online data sources shown in Power BI Desktop’s Get Data and Query Editor.
All on-premises data sources shown in Power BI Desktop’s Get Data and Query Editor except for Hadoop file
(HDFS ) and Microsoft Exchange.
On-premises data gateway
DATA SOURCE

Analysis Services Tabular

Analysis Services Multidimensional

SQL Server

SAP HANA

Oracle

Teradata

File

Folder

SharePoint list (on-premises)

Web

OData

IBM DB2

MySQL

Sybase

SAP BW
 DATA SOURCE

IBM Informix Database

ODBC

NOTE
A gateway must be installed and running in order for Power BI to connect to on-premises data sources and refresh the
dataset.

You can perform a one-time, manual refresh right in Power BI Desktop by selecting Refresh on the Home ribbon.
When you select Refresh here, the data in the file’s model is refreshed with updated data from the original data
source. This kind of refresh, entirely from within the Power BI Desktop application itself, is different from manual
or scheduled refresh in Power BI, and it’s important to understand the distinction.

When you import your Power BI Desktop file from a local drive, data, along with other information about the
model is loaded into a dataset in the Power BI service. In the Power BI service, not Power BI Desktop, you want to
refresh data in the dataset because that is what your reports, in the Power BI service, are based on. Because the
data sources are external, you can manually refresh the dataset by using Refresh now or you can setup a refresh
schedule by using Schedule Refresh.
When you refresh the dataset, Power BI does not connect to the file on the local drive to query for updated data. It
uses information in the dataset to connect directly to the data sources to query for updated data it then loads into
the dataset.

NOTE
Refreshed data in the dataset is not synchronized back to the file on the local drive.

How do I schedule refresh?

When you setup a refresh schedule, Power BI will connect directly to the data sources using connection
information and credentials in the dataset to query for updated data, then load the updated data into the dataset.
Any visualizations in reports and dashboards based on that dataset in the Power BI service are also updated.
For details on how to setup schedule refresh, see Configure Schedule Refresh.

When things go wrong

When things go wrong, it’s usually because Power BI can’t sign into data sources, or if the dataset connects to an
on-premises data source, the gateway is offline. Make sure Power BI can sign into data sources. If a password you
use to sign into a data source changes, or Power BI gets signed out from a data source, be sure to try signing into
your data sources again in Data Source Credentials.
Be sure to leave the Send refresh failure notification email to me checked. You’ll want to know right away if a
scheduled refresh fails.

Troubleshooting
Sometimes refreshing data may not go as expected. Typically this will be an issue connected with a gateway. Take a
look at the gateway troubleshooting articles for tools and known issues.
Troubleshooting the On-premises data gateway
Troubleshooting the Power BI Gateway - Personal
More questions? Try asking the Power BI Community
 Refresh a dataset stored on OneDrive or SharePoint
Online
1/14/2019 • 4 minutes to read • Edit Online

Importing files from OneDrive, or SharePoint Online, into the Power BI service is a great way to make sure the
work you’re doing in Power BI Desktop stays in sync with the Power BI service.

Advantages of storing a Power BI Desktop file on OneDrive or

SharePoint Online
When you store a Power BI Desktop file on OneDrive or SharePoint Online, any data you’ve loaded into your
file’s model is imported into the dataset, and any reports you’ve created in the file are loaded into Reports in the
Power BI serviced. When you make changes to your file on OneDrive or SharePoint Online, such as adding new
measures, changing column names, or editing visualizations, once you save the file those changes will be updated
in the Power BI service too, usually within about an hour.
You can perform a one-time, manual refresh right in Power BI Desktop by selecting Refresh on the Home ribbon.
When you select Refresh here, the data in the file’s model is refreshed with updated data from the original data
source. This kind of refresh, entirely from within the Power BI Desktop application itself, is different from manual
or scheduled refresh in Power BI, and it’s important to understand the distinction.

When you import your Power BI Desktop file from OneDrive, or SharePoint Online, data, along with other
information about the model is loaded into a dataset in Power BI. In the Power BI service, not Power BI Desktop,
you want to refresh data in the dataset because that is what your reports, in the Power BI service, are based on.
Because the data sources are external, you can manually refresh the dataset by using Refresh now or you can
setup a refresh schedule by using Schedule Refresh.
When you refresh the dataset, Power BI does not connect to the file on OneDrive, or SharePoint Online, to query
for updated data. It uses information in the dataset to connect directly to the data sources to query for updated
data it then loads into the dataset. This refreshed data in the dataset is not synchronized back to the file on
OneDrive, or SharePoint Online.

What’s supported?
In Power BI, Refresh Now and Schedule Refresh is supported for datasets created from Power BI Desktop files
imported from a local drive where Get Data/Query Editor is used to connect to and load data from any of the
following data sources:
Power BI Gateway - Personal
All online data sources shown in Power BI Desktop’s Get Data and Query Editor.
All on-premises data sources shown in Power BI Desktop’s Get Data and Query Editor except for Hadoop file
(HDFS ) and Microsoft Exchange.
On-premises data gateway
DATA SOURCE

Analysis Services Tabular

Analysis Services Multidimensional

SQL Server

SAP HANA

Oracle

Teradata

File

Folder

SharePoint list (on-premises)

Web

OData

IBM DB2

MySQL

Sybase

SAP BW

IBM Informix Database

ODBC

NOTE
A gateway must be installed and running in order for Power BI to connect to on-premises data sources and refresh the
dataset.

OneDrive or OneDrive for Business. What’s the difference?

If you have both a personal OneDrive and OneDrive for Business, it’s recommended you keep any files you want
to import into Power BI in OneDrive for Business. Here’s why: You likely use two different accounts to sign into
them.
Connecting to OneDrive for Business in Power BI is typically seamless because the same account you use to sign
into Power BI with is often the same account used to sign into OneDrive for Business. But, with personal
OneDrive, you likely sign in with a different Microsoft account.
When you sign in with your Microsoft account, be sure to select Keep me signed in. Power BI can then synchronize
any updates you make in the file in Power BI Desktop with datasets in Power BI

If you make changes to your file on OneDrive that cannot be synchronized with the dataset or reports in Power BI,
because your Microsoft account credentials might have changed, you’ll need to connect to and import your file
again from your personal OneDrive.

How do I schedule refresh?

When you setup a refresh schedule, Power BI will connect directly to the data sources using connection
information and credentials in the dataset to query for updated data, then load the updated data into the dataset.
Any visualizations in reports and dashboards based on that dataset in the Power BI service are also updated.
For details on how to setup schedule refresh, see Configure Schedule Refresh.

When things go wrong

When things go wrong, it’s usually because Power BI can’t sign into data sources, or if the dataset connects to an
on-premises data source, the gateway is offline. Make sure Power BI can sign into data sources. If a password you
use to sign into a data source changes, or Power BI gets signed out from a data source, be sure to try signing into
your data sources again in Data Source Credentials.
If you’re making changes to the Power BI Desktop file on OneDrive and saving, and those changes aren’t being
reflected in Power BI within an hour or so, it could be because Power BI cannot connect to your OneDrive. Try
connecting to the file on OneDrive again. If you’re prompted to sign in, make sure you select Keep me signed in.
Because Power BI was not able to connect to your OneDrive to synchronize with the file, you’ll need to import
your file again.
Be sure to leave the Send refresh failure notification email to me checked. You’ll want to know right away if a
scheduled refresh fails.

Troubleshooting
Sometimes refreshing data may not go as expected. Typically this will be an issue connected with a gateway. Take a
look at the gateway troubleshooting articles for tools and known issues.
Troubleshooting the On-premises data gateway
Troubleshooting the Power BI Gateway - Personal
More questions? Try asking the Power BI Community
 Refresh a dataset created from an Excel workbook on
a local drive
1/14/2019 • 3 minutes to read • Edit Online

What’s supported?
In Power BI, Refresh Now and Schedule Refresh is supported for datasets created from Excel workbooks imported
from a local drive where Power Query (Get & Transform data in Excel 2016) or Power Pivot is used to connect to
any of the following data sources and load data into the Excel data model:
Power BI Gateway - Personal
All online data sources shown in Power Query.
All on-premises data sources shown in Power Query except for Hadoop file (HDFS ) and Microsoft Exchange.
All online data sources shown in Power Pivot.*
All on-premises data sources shown in Power Pivot except for Hadoop file (HDFS ) and Microsoft Exchange.
On-premises data gateway
DATA SOURCE

Analysis Services Tabular

Analysis Services Multidimensional

SQL Server

SAP HANA

Oracle

Teradata

File

Folder

SharePoint list (on-premises)

Web

OData

IBM DB2

MySQL

Sybase
 DATA SOURCE

SAP BW

IBM Informix Database

ODBC

Notes:
A gateway must be installed and running in order for Power BI to connect to on-premises data sources and
refresh the dataset.
When using Excel 2013, make sure you’ve updated Power Query to the latest version.
Refresh is not supported for Excel workbooks imported from a local drive where data exists only in
worksheets or linked tables. Refresh is supported for worksheet data if it is stored and imported from
OneDrive. To learn more, see Refresh a dataset created from an Excel workbook on OneDrive, or
SharePoint Online.
When you refresh a dataset created from an Excel workbook imported from a local drive, only the data
queried from data sources is refreshed. If you change the structure of the data model in Excel or Power
Pivot; for example, create a new measure or change the name of a column, those changes will not be copied
to the dataset. If you make such changes, you’ll need to re-upload or re-publish the workbook. If you expect
to make regular changes to the structure of your workbook and you want those to be reflected in the
dataset in Power BI without having to re-upload, consider putting your workbook on OneDrive. Power BI
automatically refreshes both the structure and worksheet data from workbooks stored and imported from
OneDrive.

How do I make sure data is loaded to the Excel data model?

When you use Power Query (Get & Transform data in Excel 2016) to connect to a data source, you have several
options where to load the data. To make sure you load data into the data model, you must select the Add this data
to the Data Model option in the Load To dialog box.

NOTE
The images here show Excel 2016.

In Navigator, click Load To…

Or, If you click Edit in Navigator, you’ll open the Query Editor. There you can click Close & Load To….

Then in Load To, make sure you select Add this data to the Data Model.
What if I use Get External Data in Power Pivot?
No problem. Whenever you use Power Pivot to connect to and query data from an on-premises or online data
source, the data is automatically loaded to the data model.

How do I schedule refresh?

When you setup a refresh schedule, Power BI will connect directly to the data sources using connection
information and credentials in the dataset to query for updated data, then load the updated data into the dataset.
Any visualizations in reports and dashboards based on that dataset in the Power BI service are also updated.
For details on how to setup schedule refresh, see Configure Schedule Refresh.

When things go wrong

When things go wrong, it’s usually because Power BI can’t sign into data sources, or if the dataset connects to an
on-premises data source, the gateway is offline. Make sure Power BI can sign into data sources. If a password you
use to sign into a data source changes, or Power BI gets signed out from a data source, be sure to try signing into
your data sources again in Data Source Credentials.
Be sure to leave the Send refresh failure notification email to me checked. You’ll want to know right away if a
scheduled refresh fails.

IMPORTANT
Refresh is not supported for OData feeds connected to and queried from Power Pivot. When using an OData feed as a data
source, use Power Query.

Troubleshooting
Sometimes refreshing data may not go as expected. Typically this will be an issue connected with a gateway. Take a
look at the gateway troubleshooting articles for tools and known issues.
Troubleshooting the On-premises data gateway
Troubleshooting the Power BI Gateway - Personal

Next steps
More questions? Try the Power BI Community
 Refresh a dataset created from an Excel workbook on
OneDrive, or SharePoint Online
1/14/2019 • 6 minutes to read • Edit Online

You can import Excel workbooks that are stored on your local machine, or in cloud storage such as OneDrive for
Business or SharePoint Online. We will look at the advantages of using cloud storage for your excel files. For more
information on how to import Excel files into Power BI, see Get data from Excel workbook files.

What are the advantages?

Importing files from OneDrive, or SharePoint Online, is a great way to make sure the work you’re doing in Excel
stays in-sync with the Power BI service. Any data you’ve loaded into your file’s model is imported into the dataset
and any reports you’ve created in the file are loaded into Reports in Power BI. If you make changes to your file on
OneDrive, or SharePoint Online, like add new measures, change column names, or edit visualizations, once you
save, those changes will be updated in Power BI too, usually within about an hour.
When you import an Excel workbook from your personal OneDrive, any data in the workbook, like tables in
worksheets and/or data that is loaded into the Excel data model and the structure of the data model, are imported
into a new dataset in Power BI. Any Power View visualizations are re-created in Reports. Power BI automatically
connects to the workbook on OneDrive, or SharePoint Online, about every hour to check for updates. If the
workbook has changed, Power BI will refresh the dataset and reports in the Power BI service.
You can refresh on the dataset in the Power BI service. When you manually refresh, or schedule refresh, on the
dataset, Power BI connects directly to the external data sources to query for updated data it then loads into the
dataset. Refreshing a dataset from within Power BI does not refresh the data in the workbook on OneDrive, or
SharePoint Online.

What’s supported?
In Power BI, Refresh Now and Schedule Refresh is supported for datasets created from Power BI Desktop files
imported from a local drive where Get Data/Query Editor is used to connect to and load data from any of the
following data sources:
Power BI Gateway - Personal
All online data sources shown in Power BI Desktop’s Get Data and Query Editor.
All on-premises data sources shown in Power BI Desktop’s Get Data and Query Editor except for Hadoop file
(HDFS ) and Microsoft Exchange.
On-premises data gateway
DATA SOURCE

Analysis Services Tabular

Analysis Services Multidimensional

SQL Server

SAP HANA
 DATA SOURCE

Oracle

Teradata

File

Folder

SharePoint list (on-premises)

Web

OData

IBM DB2

MySQL

Sybase

SAP BW

IBM Informix Database

ODBC

NOTE
A gateway must be installed and running in order for Power BI to connect to on-premises data sources and refresh the
dataset.

OneDrive or OneDrive for Business. What’s the difference?

If you have both a personal OneDrive and OneDrive for Business, it’s recommended you keep any files you want
to import into Power BI in OneDrive for Business. Here’s why: You likely use two different accounts to sign into
them.
Connecting to OneDrive for Business in Power BI is typically seamless because the same account you use to sign
into Power BI with is often the same account used to sign into OneDrive for Business. But, with personal
OneDrive, you likely sign in with a different Microsoft account.
When you sign in with your Microsoft account, be sure to select Keep me signed in. Power BI can then synchronize
any updates you make in the file in Power BI Desktop with datasets in Power BI
If you make changes to your file on OneDrive that cannot be synchronized with the dataset or reports in Power BI,
because your Microsoft account credentials might have changed, you’ll need to connect to and import your file
again from your personal OneDrive.

Options for connecting to Excel file

When you connect to an Excel workbook in OneDrive for Business, or SharePoint Online, you’ll have two options
on how to get what’s in your workbook into Power BI.
Import Excel data into Power BI – When you import an Excel workbook from your OneDrive for Business, or
SharePoint Online, it works as described above.
Connect, Manage, and View Excel in Power BI – When using this option, you create a connection from Power
BI right to your workbook on OneDrive for Business, or SharePoint Online.
When you connect to an Excel workbook this way, a dataset is not created in Power BI. However, the workbook
will appear in the Power BI service under Reports with an Excel icon next to the name. Unlike with Excel Online,
when you connect to your workbook from Power BI, if your workbook has connections to external data sources
that load data into the Excel data model, you can setup a refresh schedule.
When you setup a refresh schedule this way, the only difference is refreshed data goes into the workbook’s data
model on OneDrive, or SharePoint Online, rather than a dataset in Power BI.

How do I make sure data is loaded to the Excel data model?

When you use Power Query (Get & Transform data in Excel 2016) to connect to a data source, you have several
options where to load the data. To make sure you load data into the data model, you must select the Add this
data to the Data Model option in the Load To dialog box.

NOTE
The images here show Excel 2016.

In Navigator, click Load To…

Or, If you click Edit in Navigator, you’ll open the Query Editor. There you can click Close & Load To….
Then in Load To, make sure you select Add this data to the Data Model.

What if I use Get External Data in Power Pivot?

No problem. Whenever you use Power Pivot to connect to and query data from an on-premises or online data
source, the data is automatically loaded to the data model.

How do I schedule refresh?

When you setup a refresh schedule, Power BI will connect directly to the data sources using connection
information and credentials in the dataset to query for updated data, then load the updated data into the dataset.
Any visualizations in reports and dashboards based on that dataset in the Power BI service are also updated.
For details on how to setup schedule refresh, see Configure Schedule Refresh.

When things go wrong

When things go wrong, it’s usually because Power BI can’t sign into data sources, or if the dataset connects to an
on-premises data source, the gateway is offline. Make sure Power BI can sign into data sources. If a password you
use to sign into a data source changes, or Power BI gets signed out from a data source, be sure to try signing into
your data sources again in Data Source Credentials.
Be sure to leave the Send refresh failure notification email to me checked. You’ll want to know right away if a
scheduled refresh fails.

Important notes
* Refresh is not supported for OData feeds connected to and queried from Power Pivot. When using an OData
feed as a data source, use Power Query.

Troubleshooting
Sometimes refreshing data may not go as expected. Typically this will be an issue connected with a gateway. Take
a look at the gateway troubleshooting articles for tools and known issues.
Troubleshooting the On-premises data gateway
Troubleshooting the Power BI Gateway - Personal
More questions? Try the Power BI Community
 Refresh a dataset created from a .CSV file on
OneDrive or SharePoint Online
1/14/2019 • 2 minutes to read • Edit Online

What are the advantages?

When you connect to a .csv file on OneDrive or SharePoint Online, a dataset is created in Power BI. Data from the
.csv file is then imported into the dataset in Power BI. Power BI then automatically connects to the file and
refreshes any changes with the dataset in Power BI. If you edit the .csv file in OneDrive, or SharePoint Online, once
you save, those changes will appear in Power BI, usually within about an hour. Any visualizations in Power BI based
on the dataset are automatically updated too.
If your files are in a shared folder on OneDrive for Business, or SharePoint Online, other users can work on the
same file. Once saved, any changes made are automatically updated in Power BI, usually within an hour.
Many organizations run processes that automatically query databases for data that is then saved to a .csv file each
day. If the file is stored on OneDrive, or SharePoint Online, and the same file is overwritten each day, as opposed
to a new file with a different name being created each day, you can connect to that file in Power BI. Your dataset
that connects to the file will be synchronized soon after the file on OneDrive, or SharePoint Online, is updated. Any
visualizations based on the dataset are automatically updated too.

What’s supported?
Comma separated value files are simple text files, so connections to external data sources and reports are not
supported. You cannot schedule refresh on a dataset created from a comma delimited file. However, when the file
is on OneDrive, or SharePoint Online, Power BI will synchronize any changes to the file with the dataset
automatically about every hour.

OneDrive or OneDrive for Business. What’s the difference?

If you have both a personal OneDrive and OneDrive for Business, it’s recommended you keep any files you want
to connect to in Power BI on OneDrive for Business. Here’s why: You likely use two different accounts to sign into
them.
Connecting to OneDrive for Business in Power BI is typically seamless because the same account you use to sign
into Power BI with is often the same account used to sign into OneDrive for Business. But, with personal OneDrive,
you likely sign in with a different Microsoft account.
When you sign into your Microsoft account, be sure to select Keep me signed in. Power BI can then synchronize
any updates with datasets in Power BI
If you make changes to your .csv file on OneDrive that cannot be synchronized with the dataset in Power BI
because your Microsoft account credentials might have changed, you’ll need to connect to the file and import it
again from your personal OneDrive.

When things go wrong

If data in the .csv file on OneDrive is changing and those changes aren’t being reflected in Power BI, it’s most likely
because Power BI cannot connect to your OneDrive. Try connecting to the file and importing it again. If you’re
prompted to sign in, make sure you select Keep me signed in.

Next steps
Tools for troubleshooting refresh issues Troubleshooting refresh scenarios
More questions? Try asking the Power BI Community
 Troubleshooting refresh scenarios
1/14/2019 • 3 minutes to read • Edit Online

Here you can find information regarding different scenarios you may face when refreshing data within the Power
BI service.

NOTE
If you encounter a scenario that is not listed below, and it is causing you issues, you can ask for further assistance on the
community site, or you can create a support ticket.

Refresh using Web connector doesn't work properly

If you have a web connector script that's using the Web.Page function, and you have updated your dataset or
report after November 18th, 2016, you need to use a gateway in order for refresh to work properly.

Unsupported data source for refresh

When configuring a dataset, you may get an error indicating the dataset uses an unsupported data source for
refresh. For details, see Troubleshooting unsupported data source for refresh

Dashboard doesn't reflect changes after refresh

Please wait about 10-15 minutes for refresh to be reflected in the dashboard tiles. If it is still not showing up, re-
pin the visualization to the dashboard.

GatewayNotReachable when setting credentials

You may encounter GatewayNotReachable when trying to set credentials for a data source. This could be the
result of an outdated gateway. Install the latest gateway and try again.

Processing Error: The following system error occurred: Type Mismatch

This could be an issue with your M script within your Power BI Desktop file or Excel Workbook. It could also be
due to an out of date Power BI Desktop version.

Tile refresh errors

For a list of errors you may encounter with dashboard tiles, and explanations, see Troubleshooting tile errors.

Refresh fails when updating data from sources that use AAD OAuth
The Azure Active Director (AAD ) OAuth token, used by many different data sources, expires in approximately one
hour. You can run into situations where loading data takes longer than the token expiration (more than one hour),
since the Power BI service waits for up to two hours when loading data. In that situation, the data loading process
can fail with a credentials error.
Data sources that use AAD OAuth include Microsoft Dynamics CRM Online, SharePoint Online (SPO ), and
others. If you’re connecting to such data sources, and get a credentials failure when loading data takes more than
an hour, this may be the reason.
Microsoft is investigating a solution that allows the data loading process to refresh the token and continue.
However, if your Dynamics CRM Online or SharePoint Online instance (or other AAD OAuth data source) is so
large that it could run into the two-hour data-load threshold, you may experience a data load timeout from the
Power BI service as well.
Also note that, for refresh to work properly, when connecting to a SharePoint Online data source using AAD
OAuth, you must use the same account that you use to sign in to the Power BI service.

Uncompressed data limits for refresh

The maximum size for datasets imported into the Power BI service is 1 GB. These datasets are heavily
compressed to ensure high performance. In addition, in shared capacity, the service places a limit on the amount
of uncompressed data that is processed during refresh to 10 GB. This limit accounts for the compression, and
therefore is much higher than 1 GB. Datasets in Power BI Premium are not subject to this limit. If refresh in the
Power BI service fails for this reason, please reduce the amount of data being imported to Power BI and try again.

Scheduled refresh timeout

Scheduled refresh for imported datasets timeout after two hours. This timeout is increased to five hours for
datasets in Premium workspaces. If you are encountering this limit, you can consider reducing the size or
complexity of your dataset, or consider breaking the dataset into smaller pieces.

Access to the resource is forbidden

This error could occur because of expired cached credentials. Clear your internet browser cache by going signing
into Power BI and going to https://app.powerbi.com?alwaysPromptForContentProviderCreds=true. This forces an
update of your credentials.

Data refresh failure because of password change or expired credentials

Data refresh could also fail due to expired cached credential. Clear your internet browser cache by going signing
into Power BI and going to https://app.powerbi.com?alwaysPromptForContentProviderCreds=true. This forces an
update of your credentials.

Next steps
Data Refresh
Troubleshooting the On-premises data gateway
Troubleshooting the Power BI Gateway - Personal
More questions? Try asking the Power BI Community
 Intro to dashboards for Power BI designers
1/14/2019 • 2 minutes to read • Edit Online

A Power BI dashboard is a single page, often called a canvas, that tells a story through visualizations. Because it is
limited to one page, a well-designed dashboard contains only the highlights of that story. Readers can view related
reports for the details.

Dashboards are a feature of the Power BI service. They're not available in Power BI Desktop. You can't create
dashboards on mobile devices but you can view and share them there.

Dashboard basics
The visualizations you see on the dashboard are called tiles. You pin tiles to a dashboard from reports. If you're
new to Power BI, you can get a good foundation by reading Power BI basic concepts.

IMPORTANT
You need a Power BI Pro license to create dashboards.

The visualizations on a dashboard come from reports and each report is based on a dataset. One way to think of a
dashboard is as an entryway to the underlying reports and datasets. Selecting a visualization takes you to the
report (and dataset) that it's based on.
Advantages of dashboards
Dashboards are a wonderful way to monitor your business and see all of your most important metrics at a glance.
The visualizations on a dashboard may come from one underlying dataset or many, and from one underlying
report or many. A dashboard combines on-premises and cloud data, providing a consolidated view regardless of
where the data lives.
A dashboard isn't just a pretty picture. It's highly interactive and the tiles update as the underlying data changes.

Dashboards versus reports

Reports and dashboards seem similar because they're both canvases filled with visualizations. But there are major
differences.

CAPABILITY DASHBOARDS REPORTS

Pages One page One or more pages

Data sources One or more reports and one or more A single dataset per report
datasets per dashboard

Available in Power BI Desktop No Can build and view reports in Power BI

Desktop

Subscribe Can subscribe to a dashboard Can subscribe to report pages

Filtering Can't filter or slice Many different ways to filter, highlight,

and slice

Featured Can set one dashboard as your Can't create a featured report
"featured" dashboard

Favorite Can set dashboards as favorites Can set reports as favorites

Set alerts Available for dashboard tiles in certain Not available from reports
circumstances

Natural language queries (Q&A) Available in dashboards Available in reports

 CAPABILITY DASHBOARDS REPORTS

Can see underlying dataset tables and No. Can export data but can't see tables Yes. Can see dataset tables and fields
fields and fields in the dashboard itself. and values.

Next steps
Get comfortable with dashboards by taking a tour of one of our sample dashboards.
Learn about dashboard tiles.
Want to track an individual dashboard tile and receive an email when it reaches a certain threshold? Create
alerts on tiles.
Learn how to use Power BI Q&A to ask a question about your data and get the answer in the form of a
visualization.
 Intro to dashboard tiles for Power BI designers
2/13/2019 • 3 minutes to read • Edit Online

A tile is a snapshot of your data, pinned to the dashboard. A tile can be created from a report, dataset, dashboard,
the Q&A box, Excel, SQL Server Reporting Services (SSRS ) reports, and more. This screenshot shows many
different tiles pinned to a dashboard.

Dashboards and dashboard tiles are a feature of Power BI service, not Power BI Desktop. You can't create
dashboards on mobile devices but you can view and share them there.
Besides pinning, you can create standalone tiles directly on the dashboard using Add tile. Standalone tiles include:
text boxes, images, videos, streaming data, and web content.
Need help understanding the building blocks that make up Power BI? See Power BI - Basic Concepts.

NOTE
If the original visualization used to create the tile changes, the tile doesn't change. For example, if you pinned a line chart
from a report and then you changed the line chart to a bar chart, the dashboard tile continues to show a line chart. The
data refreshes, but the visualization type does not.

Pin a tile from...

There are many different ways to add (pin) a tile to a dashboard. Tiles can be pinned from:
Power BI Q&A
a report
another dashboard
Excel workbook on OneDrive for Business
Power BI Publisher for Excel
Quick Insights
Reporting Services
And standalone tiles for images, text boxes, videos, streaming data, and web content can be created directly on
the dashboard using Add tile.
Interacting with tiles on a dashboard
Move and resize a tile
Grab a tile and move it around on the dashboard. Hover and select the handle to resize the tile.
Hover over a tile to change the appearance and behavior
1. Hover over the tile to display the ellipses.

2. Select the ellipses to open the tile action menu.

From here you can:

Open the report that was used to create this tile

Open the worksheet that was used to create this tile

View in focus mode

Export the data used in the tile

Edit title and subtitle, add a hyperlink

Run insights

Pin the tile to another dashboard

Remove the tile

3. To close the action menu, select a blank area in the canvas.
Select (click) a tile
When you select a tile, what happens next depends on how you created the tile. Also, if it has a custom link,
selecting the tile takes you to that link. Otherwise, selecting the tile takes you to the report, Excel Online
workbook, on-premises Reporting Services report, or Q&A question that was used to create the tile.

NOTE
The exception to this is video tiles created directly on the dashboard using Add tile. Selecting a video tile (that was created
this way) causes the video to play right there on the dashboard.

Considerations and troubleshooting

If the report that was used to create the visualization was not saved, then selecting the tile produces no action.
If the tile was created from a workbook in Excel Online, you need at least Read permissions for that workbook.
Otherwise, selecting the tile won't open the workbook in Excel Online.
Say you create a tile directly on the dashboard using Add tile and set a custom hyperlink for it. If so, when
you select the title, subtitle, or tile opens that URL. Otherwise, by default, when you select a tiles created
directly on the dashboard for an image, web code, or text box, nothing happens.
If you don't have permission to the report within Reporting Services, selecting a tile created from a Reporting
Services report takes you to a page indicating you don't have access (rsAccessDenied).
If you don't have access to the network where the Reporting Services server is located, selecting a tile created
from Reporting Services takes you to a page that indicates it can't locate the server (HTTP 404). Your device
needs network access to the report server to view the report.
If the original visualization used to create the tile changes, the tile doesn't change. For example, if you pin a
line chart from a report and then you change the line chart to a bar chart, the dashboard tile continues to
show a line chart. The data refreshes, but the visualization type does not.

Next steps
Create a Card (big number tile) for your dashboard
Dashboards in Power BI
Data refresh
Power BI - Basic Concepts
Export a tile to Power Point
Pin Reporting Services items to Power BI Dashboards
More questions? Try the Power BI Community
 Create a Power BI dashboard from a report
1/14/2019 • 4 minutes to read • Edit Online

You've read Dashboards in Power BI, and now you want to create your own. There are many different ways to
create a dashboard - from a report, from scratch, from a dataset, by duplicating an existing dashboard, and more.
It can seem overwhelming when you're first getting started, so we'll start by creating a quick and easy dashboard
by pinning visualizations from a report that's already been built. Once you complete this quickstart, you'll have a
good understanding of the relationship between dashboards and reports, opening Editing view in the report
editor, pinning tiles, and navigating between a dashboard and a report. Then use the links in the Table of Contents
on the left or the Next steps at the bottom to move on to more-advanced topics.

Who can create a dashboard?

Creating a dashboard is a creator feature and requires edit permissions to the report. Edit permissions are
available to report creators and to those colleagues the creator grants access. For example, if David creates a
report in workspaceABC and then adds you as a member of that workspace, you and David will both have edit
permissions. On the other hand, if a report has been shared with you directly or as part of a Power BI app (you are
consuming the report), you won't be able to pin tiles to a dashboard.

NOTE: Dashboards are a feature of Power BI service, not Power BI Desktop. Dashboards can't be created in
Power BI mobile, but they can be viewed and shared.

Video: Create a dashboard by pinning visuals and images from a report

Watch Amanda create a new dashboard by pinning visualizations from a report. Then follow the steps below the
video to try it out yourself, using the Procurement Analysis sample.
https://www.youtube.com/embed/lJKgWnvl6bQ
Prerequisites
To follow along, you'll need to download the "Procurement Analysis" sample Excel workbook and open it in Power
BI service (app.powerbi.com).

Import a dataset with a report

We'll import one of the Power BI sample datasets and use it to create our new dashboard. The sample we'll use is
an Excel workbook with two PowerView sheets. When Power BI imports the workbook it will add a dataset and
also a report to your workspace. The report is automatically created from the PowerView sheets.
1. Select this link to download and save the Procurement Analysis sample Excel file. We recommend saving it
 in your OneDrive for Business.
2. Open Power BI service in your browser (app.powerbi.com).
3. Select My Workspace.
4. From the left nav, select Get Data.

5. Select Files.

6. Navigate to the location where you saved the Procurement Analysis sample Excel file. Select it and choose
Connect.

7. For this exercise, select Import.

8. When the Success message appears, select the x to close it.

Open the report and pin some tiles to a dashboard
1. Staying in the same workspace, select the Reports tab. The newly-imported report displays with a yellow
asterisk. Select the report name to open it.

2. The report opens in Reading view. Notice it has two tabs at the bottom: Discount Analysis and Spend
Overview. Each tab represents a page of the report. Select Edit report to open the report in Editing view.

3. Hover over a visualization to reveal the options available. To add a visualization to a dashboard, select the
pin icon.

4. Since we're creating a new dashboard, select the option for New dashboard and give it a name.
5. When you select Pin, Power BI creates the new dashboard in the current workspace. When the Pinned to
dashboard message appears, select Go to dashboard. If you're prompted to save the report, choose Save.

6. Power BI opens the new dashboard and there is one tile - the visualization you just pinned.

7. To return to the report, select the tile. Pin a few more tiles to the new dashboard. This time when the Pin to
dashboard window displays, select Existing dashboard.

Pin an entire report page to the dashboard

Instead of pinning one visual at a time, you can pin an entire report page as a live tile. Let's do it.
1. In the report editor, select the Spend Overview tab to open the 2nd page of the report.

2. You want all of these visuals on your dashboard. In the upper-right corner of the menubar, select Pin live
page. On a dashboard, live page tiles update each time the page is refreshed.
3. When the Pin to dashboard window displays, select Existing dashboard.

4. When the Success message appears, select Go to dashboard. There you'll see the tiles you pinned from
the report. In the example below, we've pinned 2 tiles from page 1 of the report and one live tile that is page
2 of the report.

Congratulations on creating your first dashboard! Now that you have a dashboard, there's so much more you can
do with it. Try one of the suggested Next steps below, or start playing and exploring on your own.

Next steps
Resize and move tiles
All about dashboard tiles
Share your dashboard by creating an app
Power BI - Basic Concepts
 Tips for designing a great dashboard
More questions? Try the Power BI Community
 Create a copy of a dashboard in Power BI service
1/14/2019 • 2 minutes to read • Edit Online

There are many different reasons to make a copy of a dashboard. Maybe you want to make changes and test its
performance against the original; or create slightly different versions to distribute by colleague, region, or team.
Perhaps a colleague admires your dashboard design and wants to use it for reporting out to her managers.
Another reason would be if you have a new database with the same data structure and data types and want to
reuse the dashboard you've already created -- this too can be done but would require some work in Power BI
Desktop.
Dashboards are created (and copied) using Power BI service and can be viewed in Power BI mobile and Power BI
Embedded. Dashboards are not available in Power BI Desktop.
To make a copy of a dashboard, you must be the dashboard creator. Dashboards that have been shared with you
as an app cannot be duplicated.
1. Open the dashboard.
2. From the top-right corner, select the ellipses (...) and choose Duplicate dashboard.

3. Give the dashboard a name and select Duplicate.

4. The new dashboard is saved in the same workspace as the original.

5. Open the new dashboard and edit as needed. Here are some things you might want to do next:
a. Move, rename, resize or even delete tiles.
b. Edit tile details and hyperlinks by selecting the tile ellipses (...) and choosing Edit details.
c. Add new tiles from the dashboard menubar (Add tile)
d. Pin new tiles from Q&A or from reports.
e. Rename the dashboard, turn Q&A on or off, and set the tile flow from the dashboard Settings pane.
(select the dashboard ellipses (...) dropdown and choose Settings)
f. Share your dashboard directly with colleagues or as part of a Power BI app.

Next steps
Tips for designing a great dashboard
More questions? Try the Power BI Community
 Pin a tile to a Power BI dashboard from a report
1/14/2019 • 2 minutes to read • Edit Online

Pinning tiles from a report

One way to add a new dashboard tile is from within a Power BI report. In fact, you can add many new tiles from
a report. Each of these tiles, when clicked, is a link back into the report.
And entire report pages can be pinned to a dashboard. This is also known as pinning a live tile. Live because you
can interact with the tile on the dashboard and because, unlike individual visualization tiles, changes made in the
report are synced with the dashboard. Read more about this below.
You can't pin tiles from reports that have been shared with you or from Power BI Desktop.

TIP: Some visualizations use background images. Pinning may not work if the background image is too
large. Try reducing the image size or using image compression.

Pin a tile from a report

Watch Amanda create a dashboard by pinning visuals and images from a Power BI report.
https://www.youtube.com/embed/lJKgWnvl6bQ
Now create your own dashboard using one of the Power BI sample reports.

1. Hover over the visualization you want to pin, and select the pin icon. Power BI opens the Pin to
dashboard screen.

2. Decide whether to pin to an existing dashboard or new dashboard.

Existing dashboard: select the name of the dashboard from the dropdown. Dashboards that have been
shared with you will not appear in the dropdown.
New dashboard: type the name of the new dashboard.
3. In some cases, the item you are pinning may have a theme already applied. For example, visuals pinned
from an Excel workbook. If so, select which theme to apply to the tile.
4. Select Pin.
A Success message (near the top right corner) lets you know the visualization was added, as a tile, to your
 dashboard.

5. From the navigation pane, select the dashboard with the new tile. Select the tile to jump back into the
report. Or, edit the tile display and behavior.

Pin an entire report page

Another option is to pin an entire report page to a dashboard. This is an easy way to pin more than one
visualization at a time. Also, when you pin an entire page, the tiles are live; you can interact with them right there
on the dashboard. And changes you make to any of the visualizations back in the report editor, like adding a filter
or changing the fields used in the chart, are reflected in the dashboard tile as well.
For more information, see Pin an entire report page

Next steps
Dashboards in Power BI
Dashboard tiles in Power BI
Reports in Power BI
Data refresh in Power BI
Power BI Basic Concepts
More questions? Try the Power BI Community
 Pin a tile from one dashboard to another dashboard
2/13/2019 • 2 minutes to read • Edit Online

One way to add a new dashboard tile is by copying it from another dashboard. Each of these tiles, when clicked, is
a link back to where it was created -- either in Q&A or a report.

NOTE
You cannot pin tiles from shared dashboards.

Pin a tile to another dashboard

1. Get data. This example uses the IT Spend Analysis sample.
2. Open a dashboard.
3. Hover over the tile you want to pin, select the ellipses (...) and choose Pin tile.

4. Pin the tile to an existing dashboard or to a new dashboard.

Existing dashboard: select the name of the dashboard from the dropdown.
New dashboard: type the name of the new dashboard.

5. Select Pin. A Success message (near the top right corner) lets you know the visualization was added, as a
tile, to the selected dashboard.
6. Select Go to dashboard to see the pinned tile. There, you can rename, resize, link, and move the pinned
visualization.

Next steps
Tiles in Power BI
Dashboards in Power BI
More questions? Try the Power BI Community
 Pin a tile to a Power BI dashboard from Excel
2/13/2019 • 3 minutes to read • Edit Online

Before you can pin a tile from your Excel workbook, you'll connect that workbook to Power BI service
(app.powerbi.com). Connecting a workbook essentially brings a linked read-only version of that workbook into
Power BI service and allows you to pin ranges to dashboards. You can even pin an entire worksheet to a
dashboard.
If a workbook has been shared with you, you'll have the ability to view the tiles pinned by the owner, but not create
any dashboard tiles yourself.
For in-depth information about how Excel and Power BI work together, see Get data from Excel workbook files.
Watch Will demonstrate several ways to import data from, and connect to, Excel workbooks.
https://www.youtube.com/embed/l8JoB7w0zJA

Connect your Excel workbook from OneDrive for Business to Power BI

When you choose Connect, your workbook will appear in Power BI just like it would in Excel Online. But, unlike
Excel Online, you’ll have some great features to help you pin elements from your worksheets right to your
dashboards.
You can’t edit your workbook in Power BI. But if you need to make some changes, you can select the pencil icon
from the Workbooks tab of your workspace, and then choose to edit your workbook in Excel Online or open it in
Excel on your computer. Any changes you make are saved to the workbook on OneDrive.
1. Upload your workbook to your OneDrive for Business.
2. From Power BI, connect to that workbook by selecting Get Data > Files > OneDrive - Business and
nagivating to the location where you saved the Excel file. Select the file and choose Connect > Connect.

3. In Power BI, the workbook is added to the Workbooks tab of your workspace. The icon indicates this is
an Excel workbook and a yellow asterisk indicates it's new.
4. Open the workbook in Power BI by selecting the workbook name.
Changes you make to the workbook in Power BI are not saved and do not affect the original workbook on
OneDrive for Business. If you sort, filter, or change values in Power BI, those changes cannot be saved or
pinned. If you need to make changes that will be saved, select Edit from the upper-right corner to open it
for editing in Excel Online or Excel. Changes made this way may take a few minutes to update the tiles on
the dashboards.

Pin a range of cells to a dashboard

One way to add a new dashboard tile is from within an Excel workbook in Power BI. Ranges can be pinned from
Excel workbooks that have been saved in your OneDrive for Business or another group-shared document library.
The ranges can contain data, charts, tables, PivotTables, PivotCharts, and other Excel parts.
1. Highlight the cells that you'd like to pin to a dashboard.

2. Select the pin icon.

3. Pin the tile to an existing dashboard or to a new dashboard.
Existing dashboard: select the name of the dashboard from the dropdown.
New dashboard: type the name of the new dashboard.
4. Select Pin. A Success message (near the top right corner) lets you know the range was added, as a tile, to
your dashboard.

5. Select Go to dashboard. From here you can rename, resize, link, and move the pinned visualization. By
default, selecting the pinned tile opens the workbook in Power BI.

Pin an entire table or PivotTable to a dashboard

Follow the steps above except instead of selecting a range of cells, select an entire table or PivotTable.
To pin a table, select the entire range of the table and be sure to include the headers. To pin a PivotTable, be sure to
include every visible part of the PivotTable, including filters if used.

A tile created from a table or PivotTable will show the entire table. If you add/remove/filter rows or columns in the
original workbook, they will also be added/removed/filtered in the tile.

View the workbook linked to the tile

Selecting a workbook tile opens the linked workbook in Power BI. Since the workbook file is located on the
owner’s OneDrive for Business, viewing the workbook requires you have Read permissions for the workbook. If
you do not have permission, you will receive an error message.
Considerations and troubleshooting
Unsupported features: Power BI uses Excel Services to retrieve the workbook tiles. Therefore, since some features
from Excel are not supported in Excel Services REST API, they will not be seen on tiles in Power BI. For example:
Sparklines, icon set conditional formatting, and time slicers. For a full list of unsupported features see
Unsupported Features in Excel Services REST API

Next steps
Share a dashboard that has links to an Excel workbook
Get data from Excel workbooks
More questions? Try the Power BI Community
 Pin a tile to a dashboard from Q&A
1/14/2019 • 2 minutes to read • Edit Online

How to pin a tile from Q&A

Q&A is the Power BI ad hoc reporting tool. Need to find a particular insight? Ask a question about your data, and
receive an answer in the form of a visualization.
In this How -to, we'll use Power BI service (app.powerbi.com) to open a dashboard, ask a question using natural
language to create a visualization, and pin that visualization to a dashboard. Dashboards are not available in
Power BI Desktop. For information on using Q&A with other Power BI tools and content, see the Power BI Q&A
overview.
To follow along, open the Retail Analysis sample dashboard.
1. Open a dashboard that has at least one tile pinned from a report. When you ask a question, Power BI looks
for the answer in any dataset that has a tile pinned to that dashboard. To learn more, see get data.
2. In the question box at the top of your dashboard, start typing what you want to know about your data.

3. For example, as you type "last year sales by month and territory"...

the question box gives you suggestions.

4. To add the chart to your dashboard as a tile, select the pin on the top-right side of the canvas. If the
dashboard has been shared with you, you won't be able to pin any visualizations.
5. Pin the tile to an existing dashboard or to a new dashboard.

Existing dashboard: select the name of the dashboard from the dropdown. Your choices will be limited to
only those dashboards within the current workspace.
 New dashboard: type the name of the new dashboard and it will be added to your current workspace.
6. Select Pin.
A success message (near the top-right corner) lets you know the visualization was added, as a tile, to your
dashboard.

7. Select Go to dashboard to see the new tile. There, you can rename, resize, add a hyperlink, reposition the
tile, and more on your dashboard.

Considerations and troubleshooting

When you start typing a question, Q&A immediately begins searching for the best answer from all datasets
associated with the current dashboard. The "current dashboard" is the dashboard listed in the top
navigation bar. For example, this question is being asked in the Retail Analysis Sample dashboard that is
part of the mihart app workspace.

How does Q&A know which datasets to use? Q&A has access to all datasets that have at least one
visualization pinned to that dashboard.
Don't see the question box? Check with your Power BI administrator. The administrator has the ability to
disable Q&A.

Next steps
Rename, resize, add a hyperlink, reposition the tile, and more
Display your dashboard tile in Focus mode
Back to Q&A in Power BI
More questions? Try the Power BI Community
 Pin an entire report page, as a live tile, to a Power BI
dashboard
1/14/2019 • 2 minutes to read • Edit Online

Another way to add a new dashboard tile is by pinning an entire report page. This is an easy way to pin more than
one visualization at a time. Also, when you pin an entire page, the tiles are live; you can interact with them right
there on the dashboard. And changes you make to any of the visualizations back in the report editor, like adding a
filter or changing the fields used in the chart, are reflected in the dashboard tile as well.
Pinning live tiles from reports to dashboards is only available in Power BI service (app.powerbi.com).

NOTE
You can't pin tiles from reports that are shared with you.

Pin a report page

Watch Amanda pin a live report page to a dashboard and then follow the step-by-step instructions below the
video to try it yourself.
https://www.youtube.com/embed/EzhfBpPboPA
1. Open a report in Editing view.
2. With no visualizations selected, from the menubar, select Pin Live Page.

3. Pin the tile to an existing dashboard or to a new dashboard. Notice the highlighted text: Pin live page
enables changes to reports to appear in the dashboard tile when the page is refreshed.
Existing dashboard: select the name of the dashboard from the dropdown. Dashboards that have
been shared with you will not appear in the dropdown.
New dashboard: type the name of the new dashboard.
4. Select Pin live. A Success message (near the top right corner) lets you know the page was added, as a tile,
to your dashboard.

Open the dashboard to see the pinned live tile

1. From the navigation pane, select the dashboard with the new live tile. There, you can do things like rename,
resize, link, and move the pinned report page.
2. Interact with the live tile. In the screenshot below, selecting a bar on the column chart has cross-filtered and
cross-highlighted the other visualizations on the tile.

Next steps
Dashboards in Power BI
More questions? Try the Power BI Community
 Data alerts in Power BI service
1/14/2019 • 3 minutes to read • Edit Online

Set alerts to notify you when data in your dashboards changes beyond limits you set.
You can set alerts on tiles if you have a Power BI Pro license, or if a dashboard has been shared with you from a
Premium capacity. Alerts can only be set on tiles pinned from report visuals, and only on gauges, KPIs and cards.
Alerts can be set on visuals created from streaming datasets that have been pinned from a report to a dashboard,
but cannot be set on streaming tiles created directly on the dashboard using Add tile > Custom streaming
data.
Only you can see the alerts you set, even if you share your dashboard. Data alerts are fully synchronized across
platforms; set and view data alerts in the Power BI mobile apps and in the Power BI service. They are not
available for Power BI Desktop. Alerts can even be automated and integrated with Microsoft Flow - try it out
yourself.

WARNING
Data-driven alert notifications provide information about your data. If you view your Power BI data on a mobile device and
that device gets stolen, we recommend using the Power BI service to turn off all data-driven alert rules.

Set data alerts in Power BI service

Watch Amanda add some alerts to tiles on her dashboard. Then follow the step-by-step instructions below the
video to try it out yourself.
https://www.youtube.com/embed/JbL2-HJ8clE
This example uses a card tile from the Retail Analysis sample dashboard.
1. Start on a dashboard. From a dashboard gauge, KPI, or card tile, select the ellipses.

2. Select the bell icon to add one or more alerts for Total stores.
3. To start, select + Add alert rule, ensure the slider is set to On, and give your alert a title. Titles help you
easily recognize your alerts.
4. Scroll down and enter the alert details. In this example we'll create an alert that notifies us once a day if the
number of total stores goes above 100. Alerts will appear in our Notification center. And we'll have Power
BI send us an email as well.

5. Select Save.

Receiving alerts
When the data being tracked reaches one of the thresholds you've set, several things will happen. First, Power BI
checks to see if it's been more than an hour or more than 24 hours (depending on the option you selected) since
the last alert was sent. As long as the data is past the threshold, you'll get an alert.
Next, Power BI sends an alert to your notification center and, optionally, in email. Each alert contains a direct link
to your data. Select the link to see the relevant tile where you can explore, share, and learn more.
1. If you've set the alert to send you an email, you'll find something like this in your Inbox.
2. Power BI adds a message to your Notification center and adds a new alert icon to the applicable tile.

3. Open your Notification center to see the alert details.

NOTE
Alerts only work on data that is refreshed. When data refreshes, Power BI looks to see if an alert is set for that data.
If the data has reached an alert threshold, an alert is triggered.

Managing alerts
There are many ways to manage your alerts: From the dashboard tile itself, from the Power BI Settings menu, on
an individual tile in the Power BI mobile app on the iPhone or in the Power BI mobile app for Windows 10.
From the tile itself
1. If you need to change or remove an alert for a tile, re-open the Manage alerts window by selecting the
bell icon . All the alerts that you've set for that tile are displayed.

.
2. To modify an alert, select the arrow to the left of the alert name.

.
3. To delete an alert, select the trashcan to the right of the alert name.

From the Power BI settings menu

1. Select the gear icon from the Power BI menubar.

.
2. Under Settings select Alerts.

3. From here you can turn alerts on and off, open the Manage alerts window to make changes, or delete the
alert.

Tips and troubleshooting

Alerts are currently not supported for Bing tiles, or card tiles with date/time measures.
 Alerts only work with numeric data types.
Alerts only work on data that is refreshed. They do not work on static data.
Alerts will only work on streaming datasets if you build a KPI/card/gauge report visual and then pin that visual
to the dashboard.

Next steps
Create a Microsoft Flow that includes a data alert
Set data alerts on your mobile device
What is Power BI?
More questions? Try asking the Power BI Community
 Add image, text, video, and more to your dashboard
2/13/2019 • 4 minutes to read • Edit Online

https://www.youtube.com/embed/e2PD8m1Q0vU

Add tile
The Add tile control lets you directly add an image, text box, video, streaming data, or web code to your
dashboard.
1. Select Add tile from the top menu bar. Depending on space limitations, you may see only the plus
sign.

2. Select which type of tile to add: Image, Text box, Video, Web content, or Custom streaming data.

Add an image
Say you want your company logo on your dashboard, or some other image. You'll need to save the image file
online and link to it. Make sure special credentials aren't required to access the image file. For example, OneDrive
and SharePoint require authentication, so images stored there can't be added to a dashboard this way.
1. Select Image > Next.
2. Add image information to the Add image tile window.
 to display a title above the image, select Display title and subtitle and type a title and/or subtitle.
enter the image URL
to make the tile a hyperlink, select Set custom link and enter the URL. When colleagues click this
image or title, they'll be taken to this URL.
Select Apply. On the dashboard, resize and move the image as needed.

Add a text box or dashboard heading

1. Select Text box > Next.

NOTE: To add a dashboard heading, type your heading in the text box and increase the font.
2. Format the text box:
to display a title above the text box, select Display title and subtitle and type a title and/or
subtitle.
enter and format content for the text box.
Optionally, set a custom link for the title. A custom link can be an external site or a dashboard or
report in your workspace. However, in this example we've added hyperlinks within the text box
itself, so will leave Set custom link unchecked.

3. Select Apply. On the dashboard, resize and move the text box as needed.

Add a video
When you add a YouTube or Vimeo video tile to your dashboard, the video plays right on your dashboard.
1. Select Video > Next.
2. Add video information to the Add video tile pane.

to display a title and subtitle at the top of the video tile, select Display title and subtitle and type a
title and/or subtitle. In this example, we'll add a subtitle and then turn it into a hyperlink back to the
entire playlist on YouTube.
enter the URL for the video
Add a hyperlink for the title and subtitle. Perhaps after your colleagues watch the embedded video
you'd like them to view the entire playlist on YouTube -- add a link to your playlist here.
Select Apply. On the dashboard, resize and move the video tile as needed.

3. Select the video tile to play the video.

4. Select the subtitle to visit the playlist on YouTube.

Add streaming data

https://www.youtube.com/embed/kOuINwgkEkQ

Add web content

Paste or type in any HTML content. Power BI adds it, as a tile, to your dashboard. Enter the embed code by hand
or copy/paste from sites such as Twitter, YouTube, embed.ly, and more.
1. Select Web content > Next.
2. Add information to the Add web content tile pane.

to display a title above the tile, select Display title and subtitle and type a title and/or subtitle.
enter the embed code. In this example we're copying and pasting a Twitter feed.
3. Select Apply. On the dashboard, resize and move the web content tile as needed.

Tips for embedding web content

 For iframes, use a secure source. If you enter your iframe embed code and get a blank tile, check to see if
you're using http for the iframe source. If so, change it to https.

<iframe src="https://xyz.com">

Edit width and height information. This embed code embeds a video and sets the video player to 560 x
315 pixels. This size will not change as you resize the tile.

<iframe width="560" height="315"

src="https://www.youtube.com/embed/Cle_rKBpZ28" frameborder="0"
allowfullscreen></iframe>

If you'd like the player to resize to fit the tile size, set width and height to 100%.

<iframe width="100%" height="100%"

src="https://www.youtube.com/embed/Cle_rKBpZ28" frameborder="0"
allowfullscreen></iframe>

This code embeds a tweet and retains, as separate links on the dashboard, links for the AFK podcast,
@GuyInACube's Twitter page, Follow, #analytics, reply, retweet, and like. Selecting the tile itself
takes you to the podcast on Twitter.

<blockquote class="twitter-tweet" data-partner="tweetdeck">

<p lang="en" dir="ltr">Listen to
<a href="https://twitter.com/GuyInACube">@GuyInACube</a> talk to
us about making videos about Microsoft Business Intelligence
platform
<a href="https://t.co/TmRgalz7tv">https://t.co/TmRgalz7tv </a>
<a href="https://twitter.com/hashtag/analytics?src=hash">
#analytics</a></p>&mdash; AFTK Podcast (@aftkpodcast) <a
href="https://twitter.com/aftkpodcast/status/693465456531771392">
January 30, 2016</a></blockquote> <script async src="//platform.twitter.com/widgets.js" charset="utf-
8"></script>

Edit a tile
To make changes to a tile...
1. Hover over the top right corner of the tile and select the ellipses.

2. Select the edit icon to re-open the Tile details pane and make changes.
Considerations and troubleshooting
To make it easier to move the tile on your dashboard, add a title and/or subtitle.
If you'd like to embed some content from a website, but the website doesn't give you embed code to copy and
paste, check out embed.ly for help generating the embed code.

Next steps
Dashboard tiles
More questions? Try the Power BI Community.
 Edit or remove a dashboard tile
1/14/2019 • 3 minutes to read • Edit Online

Dashboard owners versus dashboard consumers

When you create or own a dashboard, you have many options for changing the look and default
behavior of the tiles on that dashboard. Use the settings and strategies below to design the dashboard
consuming experience for your colleagues. Will selecting a tile open the underlying report, a custom
URL, or a different dashboard? Maybe you'll add a tile that displays a video or streaming data? And you
might even want to create a tile that has interactive slicers. As a creator you have many options.
https://www.youtube.com/embed/lJKgWnvl6bQ
This article covers the following.
Create a visualization and pin it to a dashboard
Move a tile
Resize a tile
Rename a tile
Add a hyperlink to a tile
Pin a tile to a different dashboard
Delete a tile

TIP
To change the visualization shown on the tile itself, delete the tile and add a new dashboard tile.

Prerequisites
To follow along, open Power BI service (not Power BI Desktop) and download the IT Spend Analysis
sample. When the "Success" message appears, select Go to dashboard

Create a new visualization and pin it to the dashboard

1. From the IT Spend Analysis dashboard, select the "Amount" tile to open the report.

2. Open the report in Editing view by selecting Edit report from the top menubar.
3. Add a new report page by selecting the plus sign (+) at the bottom of the report.

4. From the FIELDS pane, select Fact > Amount and Business Area > Business Area.
5. From the VISUALIZATIONS pane, select the Donut chart icon to convert the visualization to a
Donut chart.

6. Select the pin icon and pin the Donut chart to the IT Spend Analysis sample dashboard.

7. When the "Success"message appears, select Go to dashboard. You will be prompted to save
your changes. Select Save.

Move the tile

On the dashboard, locate the new tile. Select and hold the tile to drag it to a new location on the
dashboard canvas.

Resize the tile

You can make tiles many different sizes -- from 1x1 tile units up to 5x5. Select and drag the handle (in
the bottom right corner) to resize the tile.
The ellipses (...) menu
1. Select the ellipses (...) in the upper-right corner of the tile.

2. Hover over the "Account" tile and select the ellipses to display the options. The options available
will vary by tile type. For example, the options available for a live tile are different from options
available for a standard visualization tile. Also, if a dashboard has been shared with you (you are
not the owner), you will have fewer options.

3. Select Edit details to open the "Tile details" window.

Change the title and default behavior of the tile. For example, you may decide that when a
consumer selects a tile, instead of opening the report that was used to create that tile, a new
dashboard displays instead.
Rename the tile
At the top of the "Tile details" window, change Title to Amount spent.
Change the default hyperlink
By default, selecting a tile usually takes you to the report where the tile was created or to Q&A (if the
tile was created in Q&A). To link to a webpage, another dashboard or report (in the same workspace),
an SSRS report, or other online content - add a custom link.
1. Under the Functionality heading, select Set custom link.
2. Select Link to a dashboard or report in the current workspace and then select from the
dropdown. In this example I've selected the Human Resources sample dashboard. If you don't
have this sample already in your workspace, you can add it and come back to this step, or you
can select a different dashboard.

3. Select Apply.
4. The new title displays on the tile. And, when you select the tile, Power BI opens the Human
Resources dashboard.

Pin the tile to a different dashboard

1. From the ellipses dropdown menu, select Pin tile .
2. Decide whether to pin a duplicate of this tile to an existing dashboard or to a new dashboard.
3. Select Pin.
Delete the tile
1. To permanently remove a tile from a dashboard, select Delete tile from the ellipses
dropdown menu.
2. Deleting a tile does not delete the underlying visualization. Open the underlying report by
selecting the "Amount" tile. Open the last page in your report to see that the original visualization
has not been deleted from the report.

Next steps
Dashboard tiles in Power BI
Dashboards in Power BI
Power BI - Basic Concepts
More questions? Try the Power BI Community
 Tips for designing a great Power BI dashboard
1/14/2019 • 4 minutes to read • Edit Online

Now that you've created a dashboard and added some tiles, think about how to make your dashboard not just
pretty, but also functional. In general, that means making the most important information stand out, and making it
clean and uncluttered.
Here are a few tips.

TIP
Many of the design principles for reports apply to dashboards as well. Read our whitepaper Best design principles for
reports and visualizations.

Watch the Dashboard Makeover webinar

See Microsoft Principal Program Manager and Power BI dashboard expert Marc Reguera conduct dashboard
makeovers.

Consider your audience

What are the key metrics that will help them make decisions? How will the dashboard be used? What learned or
cultural assumptions may affect design choices? What information does your audience need to be successful?
Keep in mind that the dashboard is an overview, a single place to monitor the current state of the data. The
dashboard is based on underlying reports and datasets, and those can contain loads of details. Your readers can
drill into the reports from your dashboard. So don't put the detail on the dashboard unless that's what your
readers need to monitor.
Where is the dashboard going to be displayed? If it will be on a large monitor, you can put more content on it. If
readers will view it on their tablets, then fewer tiles will be more readable.

Tell a story and keep it to one screen

Because dashboards are meant to show important information at a glance, having all the tiles on one screen is
best. Can you avoid scroll bars on your dashboard?
Is the dashboard too cluttered? Remove all but essential information that can be easily read and interpreted.

Make use of full screen mode

Display your dashboard in full screen without distractions.

Make the most important information biggest

If the text and visualizations on your dashboard are all the same size, your readers will have a hard time focusing
on what's most important. For example, card visualizations are a good way to display an important number
prominently:
But be sure to provide context.
Read about creating a tile with just a number.

Put the most important information in the upper corner

Most people read from top to bottom, so put the highest level of detail at the top and show more detail as you
move in the direction the audience uses for reading (left-to-right, right-to-left).

Use the right visualization for the data and format it for easy reading
Avoid visualization variety for the sake of variety. Visualizations should paint a picture and be easy to "read" and
interpret. For some data and visualizations, a simple graphic visualization is enough. But other data may call for a
more-complex visualization - be sure to make use of titles and labels and other customization to help the reader.
Choose appropriate data visualizations. Be careful using charts that distort reality i.e. 3-D charts. Keep in mind
that it is difficult for the human brain to interpret circular shapes. Pie charts, donut charts, gauges and other
circular chart types may look pretty but they are not a data visualization best practice.
Be consistent with chart scales on axes, chart dimension ordering and also the colors used for dimension
values within charts.
Be sure to encode quantitative data nicely. Don’t exceed three or four numerals when displaying numbers.
Display measures to one or two numerals left of the decimal point and scale for thousands or millions i.e. 3.4
million not 3,400,000.
Don’t mix levels of precision and time. Make sure that time frames are well understood. Don’t have one chart
that has last month next to filtered charts from a specific month of the year.
Don’t mix big and small measures on the same scale, such as on a line or bar chart. For example one measure
can be in the millions and the other measure in the thousands. With such a large scale, it would be difficult to
see the differences of the measure that is in the thousands. If you need to mix, choose a visualization that
allows the use of a second axis.
Don’t clutter your charts with data labels that are not needed. The values in bar charts are usually well
understood without displaying the actual number.
Pay attention to how charts are sorted. If you want to draw attention to the highest or lowest number, sort by
the measure. If you want people to be able to quickly find a particular category within many other categories,
sort by the axis.
Pie charts are best if they have fewer than eight categories. Because you can't compare values side by side, it’s
harder to compare values in a pie chart than in bar and column charts. Pie charts can be good for viewing part-
to-whole relationships rather than for comparing the parts. And Gauge charts are great for displaying the
current status in the context of a goal.
For more visualization-specific guidance, see Visualization types in Power BI.

Learning More about Best Practice Dashboard Design

To master the art of excellent dashboard design, consider learning basic Gestalt Principles of visual perception and
how to clearly communicate actionable information in context. Luckily, there is a plethora of resources already
widely available and sprinkled within our blogs. A few of our favorite books include:
 Information Dashboard Design by Stephen Few
Show Me the Numbers by Stephen Few
Now You See It by Stephen Few
Envisioning Information by Edward Tufte
Advanced Presentations by Design by Andrew Abela

Next steps
Create a dashboard from a report
Power BI - Basic Concepts
More questions? Try the Power BI Community
 Create a view of a Power BI dashboard optimized for
mobile phones
1/14/2019 • 2 minutes to read • Edit Online

When you view dashboards in the Power BI mobile app on a phone, you notice the dashboard tiles are laid out
one after another, all the same size. In the Power BI service, you can create a customized view of any dashboard
that you own, specifically for phones.
When you turn the phone sideways, then you see the dashboard as it's laid out in the service, not as you designed
it for the phone.

NOTE
As you edit the phone view, anyone viewing the dashboard on a phone can see the changes you make in real time. For
example, if you unpin all tiles on the dashboard phone view, the dashboard on the phone will suddenly have no tiles.

Create a phone view of a dashboard

1. In the Power BI service, open a dashboard.
2. Select the arrow next to Web view in the upper-right corner > select Phone view.

If you aren't the dashboard owner, you won't see this option.
 The phone dashboard edit view opens. Here you can unpin, resize, and rearrange tiles to fit the phone view.
The web version of the dashboard doesn't change.
3. Select a tile to drag, resize, or unpin it. You notice the other tiles move out of the way as you drag a tile.

The unpinned tiles go in the Unpinned tiles pane, where they stay unless you add them back.
4. If you change your mind, select Reset tiles to put them back in the size and order they were before.

Just opening Phone Edit view in the Power BI service slightly changes the size and shape of the tiles on a
phone. So to return the dashboard to its exact state before you opened it in Phone Edit view, select Reset
tiles.
5. When you're satisfied with the phone dashboard layout, select the arrow next to Phone view in the upper-
right corner > select Web view.
Power BI saves the phone layout automatically.

Next steps
Create reports optimized for the Power BI phone apps
Create responsive visuals optimized for any size
More questions? Try asking the Power BI Community
 Create a QR code for a tile in Power BI to use in the
mobile apps
1/14/2019 • 2 minutes to read • Edit Online

QR codes in Power BI can connect anything in the real world directly to related BI information no navigation or
search needed.
You can create a QR code in the Power BI service for tiles in any dashboard, even in dashboards you can't edit.
Then place the QR code in a key location. For example, you could paste it in an email, or print it out and paste it in a
specific location.
Colleagues you've shared the dashboard with can scan the QR code for access to the tile, right from their mobile
device. They can use either the QR code scanner located in the Power BI app, or any other QR scanner installed on
their device.

Create a QR code for a tile

1. Open a dashboard in the Power BI service.

2. Select the ellipsis (...) in the top-right corner of the tile and select Focus mode .
3. Select the ellipsis (...) in the top-right corner and select Generate QR code.

4. A dialog box with the QR code appears.

5. From here you can scan the QR code or download and save it so you can:
Add it to an email or other document, or
Print it and place it in a specific location.

Print the QR code

Power BI generates the QR code as a JPG file, ready to print.
1. Select Download, then open the JPG file on a computer connected to a printer.

TIP
The JPG file has the same name as the tile. For example, "Opportunity Count - by Month, Sales Stage.jpg".

2. Print the file at 100% or “actual size”.

3. Cut out the QR code and glue it to a place relevant to the tile.

Next steps
Connect to Power BI data from the real world with the mobile apps
Scan a Power BI QR code from your mobile device
Create a QR code for a report
Questions? Try asking the Power BI Community
 Add an image to a Power BI dashboard
1/14/2019 • 2 minutes to read • Edit Online

There are several ways to add a standalone image to a dashboard: one way is to pin an image from a report to a
dashboard and another way is to add it directly onto the dashboard using Add tile. For more information, visit
these articles:
Add dashboard tiles directly from a Power BI dashboard.
Pin images from a Power BI report.
 Dashboard data classification
1/14/2019 • 3 minutes to read • Edit Online

Every dashboard is different, and depending on the data source you are connecting to, you will likely find that you
and the colleagues you share with will need to take different precautions depending on the sensitivity of the data.
Some dashboards should never be shared with those outside your company or printed out, while others can be
shared freely. By using dashboard data classification, you will be able to raise awareness with those viewing your
dashboards about what level of security should be used. You can tag your dashboards with classifications defined
by your company’s IT department, so everyone viewing the content will have the same level of understanding
around the sensitivity of the data.

Data classification tags

Data classification tags show up next to the dashboard name, letting anyone viewing it know the level of security
that should be applied to the dashboard and the data it contains.

It will also show up next to the dashboard tile in your Favorites list.
When you hover over the tag, you will see the full name of the classification.

Admins can also set an URL for a tag to provide additional information.

NOTE
Depending the classification settings set by your admin, some classification types may not show as a tag on the dashboard. If
you are a dashboard owner, you can always check your dashboard classification type under the dashboard settings.

Setting a dashboard’s classification

If data classification is turned on for your company, all dashboards start out with a default classification type, but as
a dashboard owner, you can change the classification to match your dashboards security level.
To change the classification type, do the following.
1. Go to the dashboard settings by selecting the ellipsis next to the dashboard name and select Settings.

2. Under Dashboard settings, you will be able to see the current classification for your dashboard and use the
drop down to change the classification type.
3. Select Apply when finished.
After you apply the change, anyone you shared with will see the update the next time they reload the dashboard.

Working with data classification tags as an admin

Data classification is set up by the global admin for your organization. To turn data classification on, do the
following.
1. Select the Settings gear and select Admin Portal.

2. Switch Data classification for dashboards and reports to on within the Tenant settings tab.
Once turned on, you will be presented with a form to create the various classifications in your organization.

Each classification has a name and a shorthand which will appear on the dashboard. For each classification, you
can decide if the shorthand tag will appear on the dashboard or not by selecting Show tag. If you decide not to
show the classification type on the dashboard, the owner will still be able to see the type by checking the
dashboard settings. Additionally, you can optionally add a URL that contains more information about your
organization’s classification guidelines and usage requirements.
The last thing you need to decide is which classification type will be the default.
Once you fill in the form with your classification types, select Apply to save the changes.

At this point, all dashboards will be assigned the default classification, and dashboard owners will now be able to
update the classification type to the one appropriate for her content. You can return here in the future to add or
remove classification types or change the default.

NOTE
There are a few important things to remember when you come back to make changes:
If you turn data classification off, none of the tags are remembered. You will need to start over if you decide to turn it
back on later.
If you remove a classification type, any dashboards assigned the removed classification type will be assigned back to the
default until the owner goes and sets it again.
If you change the default, all dashboards that weren’t already assigned a classification type by the owner will change to
the new default.
 Use Dashboard Themes in Power BI service
1/14/2019 • 2 minutes to read • Edit Online

With Dashboard Themes you can apply a color theme to your entire dashboard, such as corporate colors,
seasonal coloring, or any other color theme you might want to apply. When you apply a Dashboard Theme, all
visuals on your dashboard use the colors from your selected theme (a few exceptions apply, described later in this
article).

Changing the colors of the report visuals on the dashboard will not affect the visuals in the report. Also, when you
pin tiles from a report that already has a report theme applied, you'll have the choice to keep the current theme or
use the dashboard theme.

Prerequisites
To follow along, open the Sales and Marketing sample dashboard.

How Dashboard Themes work

To get started, open a dashboard that you created (or have edit permission) and want to customize. Select the
ellipsis (...), and choose Dashboard theme.
In the dashboard pane that appears, select one of the pre-built themes. In the example below, we've selected Dark.

Create a custom theme

The default theme for Power BI dashboards is Light. If you want to customize the colors or create your own
theme, select Custom in the drop-down.
Use the custom options to create your own dashboard theme. If adding a background image, we recommend that
your image be at least 1920x1080 resolution. To use an image as a background, upload the image to a public
website, copy the URL, and paste it into the Image URL field.
Using JSON themes
Another way to create a custom theme is to upload a JSON file that has settings for all the colors you'd like to use
for your dashboard. In Power BI Desktop, report creators use JSON files to create themes for reports. These same
JSON files can be uploaded for dashboards or you can find and upload JSON files from the Theme gallery page in
the Power BI Community

You can also save your custom theme as a JSON file and then share it with other dashboard creators.
Use a theme from the Theme Gallery
Like the built-in and custom options, when the theme is uploaded, the colors will automatically be applied to all
tiles on the dashboard.
1. Hover over a theme and choose View report.

2. Scroll down and find the link to the JSON file. Select the download icon and save the file.

3. Back in Power BI service, in the Custom Dashboard theme window, select Upload JSON theme.

4. Navigate to the location where you saved the JSON theme file and select Open.
5. On the Dashboard theme page, select Save. The new theme is applied to your dashboard.

Considerations and limitations

If your report is using a different theme from the dashboard theme, you can control whether the visual
retains current theme, or uses the dashboard theme to achieve consistency across visuals from various
sources. When pinning a tile to a dashboard, to keep the report theme, select Keep current theme. The
visual, on the dashboard, will retain the report theme, including transparency settings.
The only time you'll see Tile Theming options is if you created the report in Power BI Desktop, added a
report theme, and then published the report to Power BI service.

Try re-pinning the tile and selecting Use dashboard theme.

Dashboard themes cannot be applied to pinned live report pages, iframe tiles, SSRS tiles, workbook tiles, or
images.
Dashboard themes can be viewed on mobile devices but creating a dashboard theme can only be done in
Power BI service.
Dashboard custom themes only work with tiles pinned from reports.
 Create a new report in Power BI service by importing
a dataset
2/13/2019 • 2 minutes to read • Edit Online

You've read Reports in Power BI and now you want to create your own. There are many different ways to create a
report, and in this article we'll start by creating a very basic report from an Excel dataset using Power BI service.
Once you understand the basics of creating a report, the Next steps at the bottom will direct you to more-
advanced report topics.

Prerequisites
Power BI service (for creating reports using Power BI Desktop, see Desktop report view )
Retail Analysis sample dataset

Import the dataset

This method of creating a report starts with a dataset and a blank report canvas. To follow along, download the
Retail Analysis sample Excel dataset and save it to OneDrive for Business (preferred) or locally.
1. We'll create the report in a Power BI service workspace, so select an existing workspace or create a new
one.

2. From the bottom of the left navpane, select Get data.

3. Select Files and navigate to the location where you saved the Retail Analysis sample.

4. For this exercise, select Import.

5. Once the dataset is imported, select View dataset.

6. Viewing a dataset actually opens the report editor. You'll see a blank canvas and the report editing tools.

TIP: If you're unfamiliar with the report editing canvas, or need a refresher, Take a tour of the report editor
 before continuing.

Add a Radial Gauge to the report

Now that our dataset is imported, let's start answering some questions. Our Chief Marketing Officer (CMO )
wants to know how close we are to meeting this year's sales goals. A Gauge is a good visualization choice for
displaying this type of information.
1. In the Fields pane, select Sales > This Year Sales > Value.

2. Convert the visual to a Gauge by selecting the Gauge template from the Visualizations pane.

3. Drag Sales > This Year Sales > Goal to the Target value well. Looks like we're very close to our goal.
4. Now would be a good time to save your report.

Add an area chart and slicer to the report

Our CMO has some additional questions for us to answer. She'd like to know how sales this year compare to last
year. And, she'd like to see the findings by district.
1. First, let's make some room on our canvas. Select the Gauge and move it into the top-right corner. Then
grab and drag one of the corners and make it smaller.
2. Deselect the gauge. In the Fields pane, select Sales > This Year Sales > Value and select Sales > Last
Year Sales.

3. Convert the visual to an Area chart by selecting the Area chart template from the Visualizations
pane.
4. Select Time > Period to add it to the Axis well.

5. To sort the visualization by time period, select the ellipses and choose Sort by Period.

6. Now let's add the slicer. Select an empty area on the canvas and choose the Slicer template. This adds
an empty slicer to our canvas.

7. From the Fields pane, select District > District. Move and resize the slicer.

8. Use the slicer to look for patterns and insights by District.

Continue exploring your data and adding visualizations. When you find especially interesting insights, pin them to
a dashboard.

Next steps
Learn how to pin visualizations to a dashboard
More questions? Try the Power BI Community
 About filters and highlighting in Power BI reports
1/14/2019 • 4 minutes to read • Edit Online

This article introduces you to filtering and highlighting in Power BI service. The experience is almost exactly the
same in Power BI Desktop. Filters remove all but the data you want to focus on. Highlighting is not filtering. It
doesn't remove data, but instead highlights a subset of the visible data; the unhighlighted data remains visible
but dimmed.
There are many different ways you can filter and highlight reports in Power BI. Putting all of that information in
one article would get confusing, so we've broken it into these sections:
Introduction to filters and highlighting (the article you're reading now )
The ways you can create and use filters in Editing view in reports. When you have editing permissions for a
report, you can create, modify, and delete filters in reports.
The ways you can filter and highlight in a report shared with you, in report Reading view. What you can do is
more limited, but you still have a wide range of filtering and highlighting options.
A detailed tour of the filter and highlighting controls available in Editing view including an in-depth look at
types of filters (e.g., date and time, numeric, text) and the difference between basic and advanced options.
After you've learned how filters and highlighting work by default, learn how to change the way visualizations
on a page filter and highlight each other

Intro to the Filters pane

You can apply filters in the Filters pane or by making selections in slicers directly on the report itself. The Filters
pane shows the tables and fields used in the report and the filters that have been applied, if any.

There are four types of filters.

page filter applies to all the visuals on the report page
visual filter applies to a single visual on a report page. You only see visual level filters if you've selected a
visual on the report canvas.
report filter applies to all pages in the report
drillthrough filter applies to a single entity in a report
You can search in page, visual, and report filters, in Reading or Editing view, to find and select the value you want.
If the filter has the word All next to it, that means all the values in the field are included in the filter. For example,
Chain(All) in the screenshot below means this report page includes data about all the store chains. On the other
hand, the report-level filter FiscalYear is 2013 or 2014 tells us that the report only includes data for the fiscal
years of 2013 and 2014.

Filters in Reading or Editing view

There are two modes for interacting with reports: Reading view and Editing view. The filtering capabilities
available to you depend on which mode you're in.
In Editing view, you can add report, page, drillthrough, and visual filters. When you save the report, the filters
are saved with the report, even if you open it in a mobile app. People looking at the report in Reading view
can interact with the filters you added, but can't add new filters.
In Reading view, you can interact with any filters that already exist in the report, and save the selections you
make. You can't add new filters.
Filters in Reading view
If you only have access to a report in Reading view, the Filters pane looks similar to this:

So this page of the report has six page-level filters and one report-level filter.
Each visual can have filters for all the fields in the visual, and a report author may add more. In the image below,
the bubble chart has six filters.
In Reading view, explore the data by modifying the existing filters. The changes you make are saved with the
report, even if you open the report in a mobile app. Learn how when you take a tour of the report Filters pane
When you exit the report, your filters are saved. To undo your filtering and return to the default filtering, slicing,
drill, and sorting set by the report author, select Reset to default from the top menubar.

Filters in Editing view

When you have owner permissions for a report and open it in Editing view, you see that Filters is just one of
several editing panes available.

As in Reading view, we see this page of the report has six page-level filters and one report-level filter. And by
selecting the bubble chart, we'd see it has six visual level filters applied.
We can do more with filters and highlighting in Editing view. Mainly, we can add new filters. Learn how to Add a
filter to a report and much more.

Ad-hoc highlighting
Select a field on the report canvas to highlight the other visuals on the page. Select any empty space in the same
visual to remove it. This type of highlighting is a fun way to quickly explore data impacts. To fine-tune how this
type of cross-highlighting works, see Visual interactions.
Next steps
Add a filter to a report (in Editing view )
Take a tour of report filters
Change how report visuals cross-filter and cross-highlight each other
More questions? Try the Power BI Community
 Add a filter to a report in Editing view
1/14/2019 • 6 minutes to read • Edit Online

This article explains how to add a page filter, visualization filter, report filter, or drillthrough filter to a report in
Power BI. The examples in this article are in the Power BI service. The steps are almost identical in Power BI
Desktop.
Did you know? Power BI has a new filter experience, currently in preview. Read more about the new filter
experience in Power BI reports.

Filters in Editing view or Reading view

You can interact with reports in two different views: Reading view and Editing view. The filtering capabilities
available to you depend on which view you're in. Read all about filters and highlighting in Power BI reports for
details.
This article describes how to create filters in report Editing view. For more information on filters in Reading
view, see interacting with filters in report Reading view.

Filter types in the Filters pane

Whether you're using Desktop or Power BI service, the Filters pane displays along the right side of the report
canvas. If you don't see the Filters pane, select the ">" icon from the upper-right corner to expand it.
There are four types of filters: page filter, visual filter, drillthrough filter, and report filter.

Because filters persist, when you navigate away from the report Power BI retains the filter, slicer, and other data
view changes that you've made. So you can pick up where you left off when you return to the report. If you don't
want your filter changes to persist, select Reset to default from the top menubar.

Add a filter to a visual

You can add a filter to a specific visual in two different ways (aka, a "visual filter").
Filter a field that is already being used by the visualization.
Identify a field that is not already being used by the visualization, and add that field directly to the Visual
 level filters bucket.
By the way, this procedure uses the Retail Analysis sample, if you'd like to download it and follow along.
Download the Retail Analysis sample.
Filter the fields in the visual
1. Open your report in Editing view.

2. Open the Visualizations and Filters pane and the Fields pane (if they're not already open).

3. Select a visual to make it active. All the fields being used by the visual are in the Fields pane and also
listed in the Filters pane, under the Visual level filters heading.

4. At this point, we'll add a filter to a field already being used by the visualization.
 Scroll down to the Visual level filters area and select the arrow to expand the field you'd like to filter. In
this example, we'll filter StoreNumberName.

Set either Basic, Advanced, or Top N filtering controls. In this example, we'll search in Basic filtering for
cha and select those five stores.

The visual changes to reflect the new filter. If you save your report with the filter, report readers will see
the visual filtered to begin with, and can interact with the filter in Reading view, selecting or clearing
values.

Filter with a field that's not in the visual

Now let's add a new field to our visualization as a visual-level filter.
1. From the Fields pane, select the field you want to add as a new visual-level filter, and drag it into the
Visual level filters area. In this example, we'll drag District Manager into the Visual level filters
bucket, search for an, and select those three managers.
 Notice District Manager is not added to the visualization itself. The visualization is still composed of
StoreNumberName as the Axis and This Year Sales as the Value.

And the visualization itself is now filtered to show only those managers' sales this year for the specified
stores.

If you save your report with this filter, report readers can interact with the District Manager filter in
Reading view, selecting or clearing values.

Add a filter to an entire page

You can also add a filter to an entire page (a page-view filter)
1. Open your report in Editing view.
2. Open the Visualizations and Filters pane and the Fields pane (if they're not already open).
3. From the Fields pane, select the field you want to add as a new page-level filter, and drag it into the Page
level filters area.
4. Select the values you want to filter and set either Basic or Advanced filtering controls.
All the visualization on the page, impacted by this filter, are redrawn to reflect the change.

If you save your report with the filter, report readers can interact with the filter in Reading view, selecting
or clearing values.

Add a drillthrough filter

With drillthrough in Power BI service and Power BI Desktop, you can create a destination report page that
focuses on a specific entity - such as a supplier, or customer, or manufacturer. Now, from the other report pages,
users can right-click on a data point for that entity and drillthrough to the focused page.
Create a drillthrough filter
To follow along, open the Customer Profitability sample in Editing view. Let's say that you want a page that
focuses on Executive business areas.
1. Add a new page to the report and name it Team Executive. This page will be the drillthrough
destination.
2. Add visualizations that track key metrics for the team executives' business areas.
3. Add Executive > Executive Name to the Drillthrough filters well.

Notice that Power BI adds a back arrow to the report page. Selecting the back arrow returns users to the
 originating report page -- the page they were on when they opted to drillthrough. The back arrow only
works in Reading view.

Use the drillthrough filter

Let's see how the drillthrough filter works.
1. Start on the Team Scorecard report page.
2. Let's say you're Andrew Ma and you want to see the Team Executive report page filtered to just your data.
From the top-left area chart, right click any green data point to open the Drillthrough menu option.

3. Select Drillthrough > Team Executive to drillthrough to the report page named Team Executive. The
page is filtered to show information about the data point from which you right-clicked; in this case
Andrew Ma. Only the field that is in the Drillthrough filters well gets passed through to the drillthrough
report page.

Add a filter to an entire report (aka Report filter)

1. Open your report in Editing view.
2. Open the Visualizations and Filters pane and the Fields pane (if they're not already open).
3. From the Fields pane, select the field you want to add as a new report-level filter, and drag it into the
Report level filters area.
4. Select the values you want to filter.
The visuals on the active page, and on all pages in the report, change to reflect the new filter. If you save
your report with the filter, report readers can interact with the filter in Reading view, selecting or clearing
values.
5. Select the back arrow to return to the previous report page.

Considerations and troubleshooting

There are situations where your visual-level filter and page-level filter may return different results. For
example, when you add a visual-level filter, Power BI filters on the aggregated results. The default
aggregation is Sum, but you can change the aggregation type.
 Then, when you add a page-level filter, Power BI filters without aggregating. It doesn't aggregate because
a page can have many visuals, each of which can utilize different aggregation types. So the filter is applied
on each data row.
If you do not see the Fields pane, make sure you're in report Editing view
If you've made lots of changes to the filters and want to return to the report author default settings, select
Reset to default from the top menubar.

Next steps
Take a tour of the report Filters pane
Filters and highlighting in reports
Interact with filters and highlighting in report Reading view
Change how report visuals cross-filter and cross-highlight each other
More questions? Try the Power BI Community
 Save a report in Power BI service and Power BI
Desktop
1/14/2019 • 2 minutes to read • Edit Online

After you make changes to a report in Power BI, you can save it, save it with a new name, or just close it without
saving your changes. Say you open the report, create a visualization, and pin it to your dashboard. If you close it
now without saving your changes, the tile remains on the dashboard, but the visualization isn't saved in the
report. When you click that tile on the dashboard, the report opens, but the visualization doesn't exist in the
report.

TIP
Pay attention to which workspace is active so you can find the saved report. The report is saved to the active workspace.

To save a report:
1. If you attempt to navigate away from a report, and the report has changes, Power BI will display a prompt.

2. Another way to save the report is to select FILE > Save or Save As. If you are in Reading view you will
only see the option to Save As.

3. If this is a new report (Save), or a new version of an existing report (Save as), give it a descriptive name.
The report will be added to the active workspace.

Next steps
Read more about reports in Power BI
Power BI - Basic Concepts
More questions? Try the Power BI Community
 Interact with a report in Editing view in Power BI
service
1/14/2019 • 2 minutes to read • Edit Online

Reports can be created and edited in Power BI service and Power BI Desktop. In Power BI service, reports can
be created and edited in Editing view. And in Power BI Desktop, reports can be created and edited in Report
view. This article covers Editing view in Power BI service.
Power BI service has two different modes for interacting with reports -- Reading view for report consumers
and Editing view for report owners and creators. A Power BI Pro license is required for sharing reports as well
as for editing reports created by others. If you don't have a Pro license, you'll still be able to create reports, but
you won't be able to share them.
In report Editing view, you have lots of flexibility in both exploring and designing a report. All the Reading view
functionality is available -- plus lots more. Editing view is only available to the person who created the report or
to colleagues who co-own a report as a member or admin of an app workspace.

Functionality only available in Editing view

Take a look at the list of topics under the Reports header in the Table of Contents to the left. It's a long list and
many of the topics cover functionality only available if you have editing permissions for a report. To help you
navigate the Table of Contents, Editing view is required for the following:
Creating, editing, renaming, sharing, and deleting reports.
Adding, renaming, rearranging, and deleting report pages.
Formatting reports.
Adding visualizations, text boxes, and shapes to a report.
Adding visual-level, page-level, and report-level filters and setting visual interactions.
Creating refresh schedules.
Q&A - asking questions in reports
Showing data used to create the visualization
Setting up drillthrough
Duplicating a report page

Considerations and troubleshooting

A Power BI Pro license is required to edit reports created by others as well as to share your reports with others.
If you don't have a Pro license, you'll still be able to create reports, but you won't be able to share them.

Next steps
Back to Reading view and Editing view in Power BI service
More questions? Try the Power BI Community
 Analyze in Excel
3/28/2019 • 5 minutes to read • Edit Online

There are times when you may want to use Excel to view and interact with a dataset that you have Power BI. With
Analyze in Excel, you can do just that, and access PivotTable, chart, and slicer features in Excel based on the
dataset that exists in Power BI.

Requirements
There are a few requirements for using Analyze in Excel:
Analyze in Excel is supported for Microsoft Excel 2010 SP1 and later.
Excel PivotTables do not support drag-and-drop aggregation of numeric fields. Your dataset in Power BI must
have pre-defined measures.
Some organizations may have Group Policy rules that prevent installing the required Analyze in Excel
updates to Excel. If you’re unable to install the updates, check with your administrator.
Analyze in Excel requires that the dataset be in Power BI Premium or that the user have a Power BI Pro
license. To learn more about the differences in functionality between license types, take a look at Power BI
features by license type.
Users can connect to datasets through Analyze in Excel if they have read permission on the underyling dataset.
A user could have this in several ways, such as being a member of the workspace containing the dataset,
having a report or dashboard shared to them that uses the dataset, or having permission to an app that
contains the dataset.

How does it work?

When you select Analyze in Excel from the ellipses menu (the ...) associated with a dataset or report in Power
BI, Power BI creates an .ODC file and downloads it from the browser to your computer.

When you open the file in Excel, an empty PivotTable and Fields list appears with the tables, fields, and measures
from the Power BI dataset. You can create PivotTables, charts, and analyze that dataset just as you would work
with a local dataset in Excel.
The .ODC file has an MSOLAP connection string that connects to your dataset in Power BI. When you analyze or
work with the data, Excel queries that dataset in Power BI and returns the results to Excel. If that dataset connects
to a live data source using DirectQuery, Power BI queries the data source and returns the result to Excel.
Analyze in Excel is very useful for datasets and reports that connect to Analysis Services Tabular or
Multidimensional databases, or from Power BI Desktop files or Excel workbooks with data models that have
model measures created using Data Analysis Expressions (DAX).

Get started with Analyze in Excel

In Power BI, select the ellipses menu beside a report or dataset (the ... beside the report or dataset name), and
from the menu that appears, select Analyze in Excel.

Install Excel updates

When you first use Analyze in Excel, you need to install updates to the Excel libraries. You’ll be prompted to
download and run Excel updates (this initiates installation of the SQL_AS_OLEDDB.msi Windows installer
package). This package installs Microsoft AS OLE DB Provider for SQL Server 2016 RC0 (Preview).

NOTE
Be sure to check Don’t show this again in the Install Excel updates dialog. You only need to install the update once.

If you do need to install the Excel updates for Analyze in Excel again, you can download the update from the
Download icon in Power BI, as shown in the following image.

Sign in to Power BI
Although you’re signed in to Power BI in your browser, the first time you open a new .ODC file in Excel you may
be asked to sign in to Power BI with your Power BI account. This authenticates the connection from Excel to Power
BI.
Users with multiple Power BI accounts
Some users have multiple Power BI accounts, and those users may encounter a situation where they're logged
into Power BI with one account, but the account that has access to the dataset being used in Analyze in Excel is a
different account. In those situations, you may get a Forbidden error or a sign-in failure when attempting to
access a dataset that's being used in an Analyze in Excel workbook.
You'll be provided an opportunity to sign in again, at which time you can sign in with the Power BI account that
has access to the dataset being accessed by Analyze in Excel. You can also select Profile from the Power BI
ribbon tab in Excel, which identifies which account you're currently logged in with, and provides a link that lets you
sign out (and subsequently, sign in with a different account).

Enable data connections

In order to analyze your Power BI data in Excel, you are prompted to verify the file name and path for the .odc file,
and then select Enable.

NOTE
Administrators for Power BI tenants can use the Power BI Admin Portal to disable the use of Analyze in Excel with on-
premises datasets housed in Analysis Services (AS) databases. When that option is disabled, Analyze in Excel is disabled for
AS databases, but continues to be available for use with other datasets.

Analyze away
Now that Excel has opened and you have an empty PivotTable, you're ready to do all sorts of analysis with your
Power BI dataset. Just as with other local workbooks, with Analyze with Excel you can create PivotTables, charts,
add data from other sources, and so on. And of course, you can create different worksheets with all sorts of views
into your data.
 NOTE
It's important to know that using Analyze in Excel exposes all detail-level data to any users with permission to the dataset.

Save
You can save this Power BI dataset connected workbook just like any other workbook. However, you cannot
publish or import the workbook back into Power BI because you can only publish or import workbooks into
Power BI that have data in tables, or that have a data model. Since the new workbook simply has a connection to
the dataset in Power BI, publishing or importing it into Power BI would be going in circles!

Share
Once your workbook is saved, you can share it with other Power BI users in your organization.
When a user with whom you’ve shared your workbook opens the workbook, they’ll see your PivotTables and data
as they appeared when the workbook was last saved, which may not be the latest version of the data. To get the
latest data, users must use the Refresh button on the Data ribbon. And since the workbook is connecting to a
dataset in Power BI, users attempting to refresh the workbook must sign into Power BI and install the Excel
updates the first time they attempt to update using this method.
Since users will need to refresh the dataset, and refresh for external connections is not supported in Excel Online,
it’s recommended that users open the workbook in the desktop version of Excel on their computer.

Troubleshooting
There may be times when using Analyze in Excel that you get an unexpected result, or the feature doesn't work as
you expected. This page provides solutions for common issues when using Analyze in Excel
 Tips and tricks for creating reports in Power BI
Desktop and Power BI service
2/13/2019 • 18 minutes to read • Edit Online

To get the most out of your data, sometimes you need a little extra help. We’ve put together some tips & tricks you
can use when creating reports in the Microsoft Power BI Desktop, Power BI service, and in Microsoft Excel 2016,
or Excel 2013 Pro-Plus editions with the Power Pivot add-in enabled and Power Query installed and enabled.

Power BI Desktop
Learning to use the Query Editor
Query Editor in Power BI Desktop is similar to the Power Query add-in capability in Excel 2013. While there are
several helpful articles in Power BI Support, you might also want to review the Power Query documentation on
support.office.com to get started.
You can get additional information from the Power Query Resource Center.
You can also view the Formula Reference.
Data types in Query Editor
When using Query Editor in Power BI Desktop to load data, we do a best guess data type detection. When using
formulas, sometimes data type settings on columns are not preserved. You should check the data type of columns
are correct after doing the following operations: Load data initially to the query tab, First Row as Header, Add
column, Group by, Merge, Append, and before pressing loading the data for the first time.
One key thing to remember: italics in the data grid do not mean the data type is correctly set, it just means the data
is not considered as Text.
Reference queries in the Query Editor
In Query Editor's navigator in Power BI Desktop, when you right click one of the queries, an option for "Reference"
is available. This is useful for the following reason:
When you use files as the data source for a query, the absolute path to the file is stored in the query. When
sharing or moving Power BI Desktop file or Excel workbook, you'll save time when you update the paths by
updating it just once rather than the paths.
By default all queries load to either an Excel worksheet or the data model (or both). Some queries are intermediary
steps and not intended for end-users. When referencing queries as mentioned above, this is often the case. You can
control query loading behavior by right clicking the query in the navigator and toggling the "Enable Load" option.
When "Enable Load" does not have a checkmark next to it, the query is still be available in the query tab and you
can use it with other queries. It is especially useful in combination with Merge, Append, and Reference transforms.
However since the query results are not loaded to the data model, the query will not clutter your reports field list
or your data model.
Scatter charts need a point identifier
Taking an example of a simple table of Temperatures and the Time the reading was taken. If you plot this directly
on a scatter chart, Power BI aggregates all the values into a single point. To show individual data points you'll to
add a field to the Details bucket in the field well. A simple way to do this in Power BI Desktop is on the query tab by
using the "Add index column" option on the "Add Column" ribbon.
Reference lines in your report
You can use a calculated column in Power BI Desktop to define a reference line. Identify the table and column on
which you want to create a reference line. Select "New Column" in the ribbon and, in the formula bar, type the
following formula:

Target Value = 100

This calculated column will return the value 100 regardless of where it is used. Your new column will show up in
the Field List. Add the Target Value calculated column to a line chart to show how any series relates to that specific
reference line.
Sort by another column
When you use a categorical (string) value in Power BI for chart axes or in a slicer or filter, the default order is
alphabetical. If you need to override this order, for example for things like days of the week or months, then you can
tell Power BI Desktop to sort by a different column.To learn more, see Sort by Column in Power BI Desktop.
Building maps more easily with hints to Bing
Power BI integrates with Bing to provide default map coordinates (a process called geo-coding) so it's easier for
you to create maps. Bing uses some algorithms and hints to try to get the right location, but it's a best guess. To
increase the likelihood of correct geo-coding, you can use the following tips:
When you create a map, you're often looking to plot countries, states, and cities. In Power BI Desktop, if you name
columns after the geographic designation it will help Bing guess what you're looking to display. For example, if you
have a field of US state names such as "California" and "Washington", Bing might return the location of
Washington, DC instead of Washington State for the word "Washington". Naming the column "State" will improve
the geocoding. The same goes for columns named "Country" and "City".
Some designations are ambiguous when considered in the context of multiple countries/regions. In some cases
what one country/region considers a 'state' is treated as a 'province' or a 'county' or some other designation. You
can increase the accuracy of geo-coding by building columns that append multiple fields together and use those for
plotting data locations. An example would be instead of passing only "Wiltshire", you can pass "Wiltshire, England"
to get a more accurate geo-coding result.
You can always provide specific latitude and longitude locations in Power BI service or Desktop. When you do this,
you'll also need to pass a Location field, otherwise the data is aggregated by default, so the location of the latitude
and longitude may not match what you expected.
Categorizing geographic fields to hint Bing's geocoding
Another way to ensure fields are correctly geocoded is by setting the Data Category on the data fields. In Power BI
Desktop, select the desired table, go to the Advanced ribbon and then set the Data Category to Address, City,
Continent, Country/Region, Country, Postal Code, State or Province. These data categories help Bing to correctly
encode the data. To learn more, see Data categorization in Power BI Desktop.
Better geocoding with more specific locations
Sometimes, even setting the data categories for mapping is insufficient. Build a more specific location like a street
address using the Query Editor in Power BI Desktop. Use the Add Column feature to build a custom column. Then
build the desired location as follows:

= [Field1] & " " & [Field2]

Then use this resulting field in the map visualizations. This is very useful for building street addresses from
shipping address fields that are common in data sets. One note is that the concatenation only works with text fields.
If needed, convert the street number to a text data type before using it to build an address.
Histograms in the query stage
There are several ways to build histograms in Power BI Desktop, we'll start with the simplest and go from there:
Simplest Histograms - Determine which query has the field you want to build a histogram on. Use the "Reference"
option for the query to create a new query and name it "FieldName Histogram". Use the "Group by" option in the
"Transform" ribbon and select the "count rows" aggregate. Ensure the data type is a number for the resulting
aggregate column. Then visualize this data on the reports page. This is fast and easy to build, but doesn't work well
if you have many data points and does not allow brushing across visuals.
Defining buckets to build a histogram - Determine which query has the field you want to build a histogram on. Use
the "Reference" option for the query to create a new query and name it "FieldName". Now define the buckets with
a rule. Use the Add Custom Column option on the Add Column ribbon and build a custom rule. A simple
bucketing rule might look like this:

if([FieldName] \< 2) then "\<2 min" else

if([FieldName] \< 5) then "\<5 min" else
if([FieldName] \< 10) then "\<10 min" else
if([FieldName] \< 30) then "\<30 min" else
"longer")

Ensure the data type is a number for the resulting aggregate column. Now you can use the group by technique
described in Simplest Histogram to achieve the histogram. This option handles more data points but still does not
help with brushing.
Defining a histogram that supports brushing - Brushing is when visuals are linked together so that when a user
selects a data point in one visual other visuals on the report page highlight or filter data points related to the
selected data point. Since we're manipulating data at query time, we will need to create a relationship between
tables and ensure we know which detail item relates to the bucket in the histogram and vice-versa.
Start the process by using the "Reference" option on the query that has the field you want to build a histogram on.
Name the new query "Buckets". For this example let's call the original query "Details". Next remove all columns
except the column you'll use as the bucket for the histogram. Now use the "Remove Duplicates" feature in query,
it's on the right click menu when you select the column, so the remaining values are the unique values in the
column. If you have decimal numbers you can first use the tip for defining buckets to build a histogram to get a
manageable set of buckets. Now, check the data shown in the query preview. If you see blank values or null you'll
need to fix those up before creating a relationship. See "Creating a relationship if my data has null or blank values".
Using this approach can be problematic due to the need to sort. To get the buckets to sort correctly, see "Sorting
order: make categories appear in the order I want".

NOTE
It's useful to think about the sort order before building any visuals.

Next step in the process is to define a relationship between the "Buckets" and "Details" queries on the buckets
column. In Power BI Desktop, click Manage Relationships in the ribbon. Create a relationsship where Buckets is
in the left table and Details in on the right table and select the field you're using for the histogram.
Last step is to create the histogram. Drag the Bucket field from the "Buckets" table. Remove the default field from
the resulting column chart. Now from the "Details" table drag the histogram field into the same visual. In the field
well, change the default aggregate to Count. The result is the histogram. If you create another visual like a treemap
from the Details table, select a data point in treemap to see the histogram highlight and show the histogram for the
selected data point relative to the trend for the entire dataset.
Histograms
In Power BI Desktop, you can use a calculated field to define a Histogram. Identify the table and column on which
you want to create a histogram. In the calculation area, type the following formula:
 Frequency:=COUNTROWS (<Column Name>)

Save your changes and return to your report. Add the <Column Name> and the Frequency to a table then convert
to a bar chart. Ensure the <Column Name> is on the x-axis and the calculated field Frequency is on the y-axis.
Tips and tricks for creating relationships in Power BI Desktop
Often when loading detail data sets from multiple sources, issues like null values, blank values, or duplicate values
prevent you from creating relationships.
Let's look at an example:
If we load data sets from of active customer support requests and another dataset of work items that have schemas
as follows:

CustomerInicdents: {IncidentID, CustomerName, IssueName, OpenedDate, Status} WorkItems: {WorkItemID,

IncidentID, WorkItemName, OpenedDate, Status, CustomerName }

When we want to track all incidents and workitems that relate to a specific a CustomerName we cannot simply
create a relationship between these two datasets. Some WorkItems may not be related to a CustomerName, so
that field would be blank or NULL. There might be multiple records in WorkItems and CustomerIncidents for any
given CustomerName.
Creating relationships in Power BI Desktop when the data has null or blank values
Often data sets contain columns with null or blank values. This can cause problems when trying to use
relationships. You have essentially two options for addressing the issues. You can remove the rows that have null or
blank values. You can do this using either the filter feature in the query tab or if you're merging queries, select the
"keep only matching rows" option. Alternatively, you can replace the null or blank values with values that work in
relationships, typically strings like "NULL" and "(Blank)". There's no right approach here - Filtering out rows at the
query stage removes rows and can affect summary statistics and calculations. The latter approach preserves that
data rows but can make unrelated rows appear related in the model leading to miscalculations. If you adopt the
latter solution ensure you use filters at the View/Chart where appropriate to ensure you're getting accurate results.
Most importantly, evaluate which rows are kept/removed and understand overall impact on the analysis..
Creating relationships in Power BI Desktop when the data has duplicate values
Often when loading detailed datasets from multiple sources, duplicate data values prevent you from creating
relationships. You can overcome this by creating a dimension table with the unique values from both data sets.
Let's look at an example:
If we load datasets from of active customer support requests and another dataset of work items that have schemas
as follows:

CustomerInicdents: {IncidentID, CustomerName, IssueName, OpenedDate, Status} WorkItems: {WorkItemID,

IncidentID, WorkItemName, OpenedDate, Status, CustomerName }

When we want to track all incidents and workitems that relate to a specific CustomerName we cannot simply
create a relationship between these two data sets. Some WorkItems may not be related to a CustomerName, so
that field would be blank or NULL. If you have any blank values or null in the CustomerNames table, you might
still not be able to create a relationship - see Creating relationships if my data has null or blank values. There might
be multiple WorkItems and CustomerIncidents for a single CustomerName.
To create a relationship in this case, we need to create a logical dataset of all the CustomerNames across the two
datasets. In the Query tab, you can use the following sequence to create the logical dataset:
1. Duplicate both queries, naming the first Temp and the second CustomerNames.
2. In each query, remove all columns except the CustomerName column
3. In each query, use Remove Duplicate.
4. In the CustomerNames query, select the Append option in the ribbon, select the query Temp.
5. In the CustomerNames query, select Remove Duplicates.
Now you have a dimension table that you can use to relate to CustomerIncidents and WorkItems that contains all
the values of each.
Patterns to jump start your use of the Query Editor
Query Editor is very powerful in how it can manipulate data to shape and clean it so it is ready to be visualized or
modeled. There are a few patterns you should be aware of.
Temporary columns can be deleted after computing a result
Often you need to build a calculation in Power BI Desktop that transforms data from multiple columns into single
new column. This can be complex. One easy way to overcome the problem is do decompose the operation into
steps. Start by duplicating the initial columns. Then build the steps a temporary columns. Then create the a column
for the final result. You can then delete the temporary columns so the final dataset is not cluttered. This is possible
because the query tab executes steps in order.
Duplicate or Reference queries followed by merge to original query
Sometimes it's useful to compute summary statistics for a dataset. The easy way to do this is to duplicate or
reference the query in the query tab. Then use Group by to compute the summary statistics. Summary statistics
help you normalize the data in the original data so they're more comparable as in . This is especially useful for
comparing individual values to the whole. To do this go to the original query, and select the merge option. Then
merge the data from the summary statistics query matching on the appropriate identifiers. Now you're ready to
normalize the data as needed for your analysis.
Using DAX for the first time
DAX is the calculations formula language in Power BI Desktop. It's optimized for BI analytics. It's a little different
than what you might be familiar with if you've only used a SQL like query language. There are very good resources
online and in literature for learning DAX.
Learn DAX Basics in Power BI Desktop
Data Analysis Expressions (DAX) Reference
DAX Resource Center

Power BI service and Power BI Desktop

Read the whitepaper: Principles for designing Power BI reports
This paper provides best practices for designing reports in Power BI. Starting with planning, it discusses principles
of design that you can apply to your reports and to the pages and individual visuals that make up that report. Many
of these best practices apply to dashboard design as well.
Read and/or watch "How to design visually stunning reports (and dashboards) in Power BI"
Community member Miguel Myers is a Data Scientist as well as a Graphic Designer.

Read the blog

 Watch the webinar
Consider your audience
What are the key metrics that will help them make decisions? How will the report be used? What learned or
cultural assumptions may affect design choices? What information does your audience need to be successful?
Where is the report going to be displayed? If it will be on a large monitor, you can put more content on it. If readers
will view it on their tablets, then fewer visualizations will be more readable.
Tell a story and keep it to one screen
Each report page should tell a story at a glance. Can you avoid scroll bars on your pages? Is the report too
cluttered or too busy? Remove all but essential information that can be easily read and interpreted.
Make the most important information biggest
If the text and visualizations on your report page are all the same size, your readers will have a hard time focusing
on what's most important. For example, card visualizations are a good way to display an important number
prominently:

But be sure to provide context

Use features such as textboxes and tooltips to add context to your visualizations.
Put the most important information in the upper corner
Most people read from top to bottom, so put the highest level of detail at the top and show more detail as you
move in the direction the audience uses for reading (left-to-right, right-to-left).
Use the right visualization for the data and format it for easy reading
Avoid visualization variety for the sake of variety. Visualizations should paint a picture and be easy to "read" and
interpret. For some data and visualizations, a simple graphic visualization is enough. But other data may call for a
more-complex visualization - be sure to make use of titles and labels and other customization to help the reader.
Be careful using charts that distort reality i.e. 3-D charts and charts that don't start at zero. Keep in mind that it
is more difficult for the human brain to interpret circular shapes. Pie charts, donut charts, gauges and other
circular chart types may look pretty but perhaps there's a different visual you can use instead?
Be consistent with chart scales on axes, chart dimension ordering and also the colors used for dimension values
within charts.
Be sure to encode quantitative data nicely. Don’t exceed three or four numerals when displaying numbers.
Display measures to one or two numerals left of the decimal point and scale for thousands or millions i.e. 3.4
million not 3,400,000.
Try to avoid mixing levels of precision and time. Make sure that time frames are well understood. Don’t have
one chart that has last month next to filtered charts from a specific month of the year.
Also try to avoid mixing big and small measures on the same scale, such as on a line or bar chart. For example
one measure can be in the millions and the other measure in the thousands. With such a large scale, it would be
difficult to see the differences of the measure that is in the thousands. If you need to mix, choose a visualization,
like a combo chart, that allows the use of a second axis.
Avoid cluttering your charts with data labels that are not needed. The values in bar charts, if large enough, are
usually well understood without displaying the actual number.
Pay attention to how charts are sorted. If you want to draw attention to the highest or lowest number, sort by
the measure. If you want people to be able to quickly find a particular category within many other categories,
 sort by the axis.
Pie charts are best if they have fewer than eight categories. Because you can't compare values side by side, it’s
harder to compare values in a pie chart than in bar and column charts. Pie charts can be good for viewing part-
to-whole relationships rather than for comparing the parts. And Gauge charts are great for displaying the
current status in the context of a goal.
For more visualization-specific guidance, see Visualization types in Power BI.
Learn more about Best Practice Dashboard Design
A few of our favorite books include:
Storytelling with Data by Cole Nussbaumer Knafic
Data points by Nathan Yau
The truthful Art by Alberto Cairo
Now You See It by Stephen Few
Envisioning Information by Edward Tufte
Advanced Presentations Design by Andrew Abela

Next steps
Power BI - Basic Concepts
Reports in Power BI
More questions? Try the Power BI Community
 Work with aggregates (sum, average, etc.) in the
Power BI service
1/14/2019 • 7 minutes to read • Edit Online

What is an aggregate?
Sometimes you want to mathematically combine values in your data. The mathematical operation could be sum,
average, maximum, count, etc. When you combine values in your data, it is called aggregating. The result of that
mathematical operation is an aggregate.
When Power BI service and Power BI Desktop create visualizations, they may aggregate your data. Often the
aggregate is just what you need, but other times you may want to aggregate the values in a different way. For
example, a sum versus an average. There are several different ways to manage and change the aggregate being
used in a visualization.
First, let's take a look at data types because the type of data determines how, and if, it can be aggregated.

Types of data
Most datasets have more than one type of data. At the most basic level, the data is either numeric or it is not.
Numeric data can be aggregated using a sum, average, count, minimum, variance, and much more. Even textual
data, often called categorical data, can be aggregated. If you try to aggregate a categorical field (by placing it in a
numeric only bucket like Values or Tooltips), Power BI will count the occurrences of each category or count the
distinct occurrences of each category. And special types of data, like dates, have a few of their own aggregate
options: earliest, latest, first, and last.
In the example below:
Units Sold and Manufacturing Price are columns that contain numeric data
Segment, Country, Product, Month, and Month Name contain categorical data

When creating a visualization in Power BI, numeric fields will be aggregated (the default is sum) over some
categorical field. For example, "Units Sold by Product, "Units Sold by Month" and "Manufacturing Price by
Segment. Some numeric fields are referred to as measures. It's easy to identify measures in the Power BI report
editor -- measures are shown with the ∑ symbol in the Fields list. For more information, see The report editor...
take a tour.
Why don't aggregates work the way I want them to?
Working with aggregates in Power BI service can be confusing; maybe you have a numeric field and Power BI
won't let you change the aggregation. Or maybe you have a field, like a year, and you don't want to aggregate it,
you just want to count the number of occurrences.
Most often, the source of the problem is how the field was defined in the dataset. Maybe the field is defined as text
and that explains why it can't be summed or averaged. Unfortunately, only the dataset owner can change the way
a field is categorized. So if you have owner permissions to the dataset, either in Desktop or the program that was
used to create the dataset (for example, Excel), you can fix this problem. Otherwise, you'll need to contact the
dataset owner for help.
To help you navigate the confusion, we have a special section at the end of this article called Considerations and
troubleshooting. If you don't find your answer there, post your question on the Power BI Community forum for
a quick response directly from the Power BI team.

Change how a numeric field is aggregated

Say you have a chart that sums the units sold for different products, but you'd rather have the average.
1. Create a chart that uses a category and a measure. In this example, we're using Units Sold by Product. By
default, Power BI creates a chart that sums the units sold (measure in the Value well) for each product
(category in the Axis well).

2. In the Visualizations pane, right-click the measure, and select the aggregate type you need. In this case,
we're selecting Average. If you don't see the aggregation you need, see "Considerations and
troubleshooting" below.
 NOTE
The options available in the dropdown will vary depending on 1) the field selected and 2) the way that field was
categorized by the dataset owner.

3. Your visualization is now using aggregated by average.

Ways to aggregate your data

Some of the options that may be available for aggregating a field:
Do Not Summarize. With this option chosen, each value in that field is treated separately and not
summarized. Use this option if you have a numeric ID column that shouldn't be summed.
Sum. Adds all the values in that field up.
Average. Takes an arithmetic mean of the values.
Minimum. Shows the smallest value.
Maximum. Shows the largest value.
Count (Not Blanks). Counts the number of values in that field that are not blank.
Count (Distinct). Counts the number of different values in that field.
Standard deviation.
Variance.
Median. Shows the median (middle) value. This value has the same number of items above and below. If there
are two medians, Power BI averages them.
For example, this data:
 COUNTRY AMOUNT

USA 100

UK 150

Canada 100

Germany 125

France

Japan 125

Australia 150

Would give the following results:

Do Not Summarize: Each value is shown separately
Sum: 750
Average: 125
Maximum: 150
Minimum: 100
Count (Not Blanks): 6
Count (Distinct): 4
Standard deviation: 20.4124145...
Variance: 416.666...
Median: 125

Create an aggregate using a category (text) field

You can also aggregate a non-numeric field. For example, if you have a product name field, you can add it as a
value and then set it to Count, Distinct count, First, or Last.
1. In this example, we've dragged the Product field into the Values well. The Values well is typically used for
numeric fields. Power BI recognizes that this field is a text field, sets the aggregate to Do not summarize,
and presents us with a single-column table.

2. If we change the aggregation from the default Do not summarize to Count (Distinct), Power BI counts
the number of different products. In this case, there are 4.
3. And if we change the aggregation to Count, Power BI counts the total number. In this case, there are 7
entries for Product.

4. By dragging the same field (in this case Product) into the Values well, and leaving the default aggregation
Do not summarize, Power BI breaks down the count by product.

Considerations and Troubleshooting

Q: Why don't I have a Do not summarize option?
A: The field you've selected is likely a calculated measure or advanced measure created in Excel or Power BI
Desktop. Each calculated measure has its own hard-coded formula. You can’t change the aggregation being used.
For example, if it’s a sum, it can only be a sum. In the Fields list, calculated measures are shown with the calculator
symbol.
Q: My field is numeric, why are my only choices Count and Distinct count?
A1: The likely explanation is that the dataset owner has, accidentally or intentionally, not classified the field as a
number. For example, if a dataset has a year field, the dataset owner may categorize that as text because it is more
likely that the year field will be counted (for example, number of people born in 1974) and not that it will be
summed or averaged. If you are the owner, you can open the dataset in Power BI Desktop and use the Modeling
tab to change the data type.
A2: If the field has a calculator icon, that means it's a calculated measure and each calculated measure has its own
hard-coded formula that can only be changed by a dataset owner. The calculation being used may be a simple
aggregation like an average or sum, but it may also be something more complicated like a "percent of contribution
to parent category" or "running total since start of the year". Power BI isn't going to sum or average the results but
will instead just recalculate (using the hard-coded formula) for each data point.
A3: Another possibility is that you've dropped the field into a bucket that only allows categorical values. In that
case, your only options will be count and distinct count.
A4: And a third possibility is that you're using the field for an axis. On a bar chart axis, for example, Power BI
shows one bar for each distinct value -- it doesn't aggregate the field values at all.
 NOTE
The exception to this rule is scatter charts, which require aggregated values for the X and Y axes.

Q: Why can't I aggregate text fields for SQL Server Analysis Services (SSAS ) data sources?
A: Live connections to SSAS multidimensional models don't allow any client-side aggregations, including first,
last, avg, min, max, and sum.
Q: I have a scatter chart and I want my field to not aggregate. How?
A: Add the field to the Details bucket and not to the X or Y axes buckets.
Q: When I add a numeric field to a visualization, most of them default to sum but some default to average or
count or some other aggregation. Why isn't the default aggregation always the same?
A: Dataset owners have the option to set the default summarization for each field. If you are a dataset owner,
change the default summarization in the Modeling tab of Power BI Desktop.
Q: I'm a dataset owner and I want to ensure that a field is never aggregated.
A: In Power BI Desktop, in the Modeling tab, set Data type to Text.
Q: I do not see Do not summarize as an option in my dropdown.
A: Try removing the field and adding it back in.
More questions? Try the Power BI Community
 Monitor usage metrics for Power BI dashboards and
reports
3/18/2019 • 11 minutes to read • Edit Online

If you create dashboards and reports, usage metrics help you understand their impact. When you run either
dashboard usage metrics or report usage metrics, you discover how those dashboards and reports are being used
throughout your organization; what is being used, by whom, and for what purpose.

NOTE
Usage metrics track usage of reports that are embedded in SharePoint Online. However, usage metrics don't track
embedding of dashboards and reports via the “user owns credentials” or “app owns credentials” flow. Usage metrics also
don't track usage of reports embedding via publish to web.

These usage metrics reports are read-only. However, you can personalize a usage metrics report by using "Save
as." This creates a brand new dataset and converts the read-only report to a full-featured Power BI report that you
can edit. Not only does the personalized report contain metrics for the selected dashboard or report, but by
removing the default filter, you now have access to usage metrics for all dashboards or all reports in the selected
workspace. And you can even see the names of your end users.

Why are usage metrics important to me?

Knowing how your content is being used helps you demonstrate your impact and prioritize your efforts. Your
usage metrics may show that one of your reports is used daily by a huge segment of the organization and it may
show that a dashboard you created isn't being viewed at all. This type of feedback is invaluable in guiding your
work efforts.
Running usage metrics reports is only available in Power BI service. However, if you save a usage metrics report
or pin it to a dashboard, you can open and interact with that report on mobile devices.
Prerequisites
 The usage metrics feature captures usage information from all users, regardless of the license they're assigned.
However, a Power BI Pro license is required to run and access the usage metrics data.
Usage metrics are provided on dashboards or reports in the selected workspace. To access usage metrics for a
particular dashboard or report, you must:
• Have edit access to that dashboard or report • Have a Pro license

About the Usage Metrics report

When you select Usage metrics or the icon , Power BI generates a pre-built report with usage metrics for
that content for the last 90 days. The report looks similar to the Power BI reports you're already familiar with, but
it's designed to be informational -- not interactive. You’ll be able to slice based on how your end users received
access, whether they were accessing via the web or mobile app, etc. As your dashboards and reports evolve, so
too will the usage metrics report, which updates every day with new data.
Usage metrics reports won't show up in Recent, Workspaces, Favorites, or other content lists. They cannot be
added to an app. If you pin a tile from a usage metrics report to a dashboard, that dashboard cannot be added to
an app or content pack.
To dig down into the report data, or to build your own reports against the dataset, use Save as (see Save the
Usage Metrics report as a full-featured Power BI report).

Open a Usage Metrics report for a dashboard or report

1. Start in the workspace that contains the dashboard or report.
2. From either the workspace content list or from the dashboard or report itself, select the icon for Usage
metrics .

3. The first time you do this, Power BI creates the usage metrics report and lets you know when it's ready.
4. To open the results, select View usage metrics.
Usage metrics are a powerful ally as you work to deploy and maintain Power BI dashboards and reports.
Wondering which pages of your report are most useful, and which ones you should phase out? Slice by
Report page to find out. Wondering if you should build a mobile layout for your dashboard? Slice by
Platforms to discover how many users are accessing your content via the mobile apps vs. via web browser.
5. Optionally, hover over a visualization and select the pin icon to add the visualization to a dashboard. Or,
from the top menubar, select Pin Live Page to add the entire page to a dashboard. From the dashboard
you can monitor the usage metrics more-easily or share them with others.

NOTE
If you pin a tile from a usage metrics report to a dashboard, that dashboard cannot be added to an app or content
pack.

Which metrics are reported?

METRIC DASHBOARD REPORT DESCRIPTION

Distribution method slicer yes yes How users got access to the
content. There are 3 possible
methods: users can access
the dashboard or report by
being members of an app
workspace, by having the
content shared with them,
or by installing a content
pack/app. Note that views
through an app are counted
as "content pack."

Platforms slicer yes yes Was the dashboard or

report accessed via the
Power BI service
(powerbi.com) or a mobile
device? Mobile includes all
our iOS, Android, and
Windows apps.

Report page slicer no yes If the report has more than

1 page, slice the report by
the page(s) that was viewed.
If you see a list option for
"Blank," that means a report
page was recently added
(within 24 hours the actual
name of the new page
appears in the slicer list)
and/or report pages have
been deleted. "Blank"
captures these types of
situations.
 METRIC DASHBOARD REPORT DESCRIPTION

Views per day yes yes Total number of views per

day - a view is defined as a
user loading a report page
or dashboard.

Unique viewers per day yes yes Number of different users

who viewed the dashboard
or report (based on the AAD
user account).

Views per user yes yes Number of views in the past

90 days, broken down by
individual users.

Shares per day yes no Number of times the

dashboard was shared with
another user or group.

Total views yes yes Number of views in the past

90 days.

Total viewers yes yes Number of unique viewers in

the past 90 days.

Total shares yes no Number of times the

dashboard or report was
shared in the past 90 days.

Total in organization yes yes Count of all dashboards or

reports in the entire
organization which had at
least one view in the past 90
days. Used to calculate rank.

Rank: Total views yes yes For total views of all

dashboards or reports in the
organization over the past
90 days, where does this
dashboard or report rank.

Rank: Total shares yes no For total shares of all

dashboards in the
organization over the past
90 days, where does this
dashboard or report rank.

Dashboard Usage Metrics report

Report Usage Metrics report

Save the Usage Metrics report as a full-featured Power BI report

(personalize)

Use Save as to convert the usage metrics report to a full-featured Power BI report that can be customized and
shared. Once you’ve created a personalized copy, you’ll get full access to the underlying dataset, allowing you to
customize the usage metrics report to your specific needs. You can even use Power BI Desktop to build custom
usage metrics reports using the live connection to Power BI service feature.
Better yet, the underlying dataset includes the usage details for all dashboards or reports in the workspace. This
opens up yet another world of possibilities. You could, for example, create a report which compares all dashboards
in your workspace based on usage. Or, you could create a usage metrics dashboard for your Power BI app by
aggregating usage across all the content distributed within that app. See remove the Page level filter below.
What is created when using "Save as"?
When Power BI creates the full-featured report, it also creates a new dataset made up of all the dashboards or
all the reports contained in the current workspace that have been accessed in the last 90 days. For example,
say you have a workspace named "Sales" and it contains three dashboards and two reports, and you create a
usage metrics report on the "Northeast" dashboard. And then you use Save as to personalize and convert it to a
full-featured report. The dataset for that new report contains the usage metrics not only for that one dashboard
named "Northeast" but for all three dashboards in the "Sales" workspace. By default, the report displays data for
the "Northeast" dashboard and you'll need to remove a filter (single click) to display data for all three dashboards.
Create a copy of the usage report using "Save as"
When you create a copy using "Save as" (personalize), Power BI converts the read-only pre-built report to a full-
featured report. At first glance, it looks exactly the same. However, you can now open the report in Editing view,
add new visualizations, filters, and pages, modify or delete existing visualizations, and so much more. Power BI
saves the brand new report and dataset in the current workspace. In the example below, the current workspace is
mihart.
1. From the pre-built usage metrics report, select File > Save As. Power BI converts the usage metrics report
into a full-featured Power BI report. This is called a personalized usage metrics report. The personalized
usage report and dataset are saved in the current workspace which is named *mihart.

2. Open the report in Editing view and interact with it as you would with any other Power BI report. For
example, add new pages and build new visualizations, add filters, format the fonts and colors, etc.

3. Alternately, start with the new dataset and build a report from scratch.
4. The new report is saved in the current workspace (mihart) and also added to the Recent content list.

Remove the filter to see all the usage metrics data in the workspace
To see the metrics for all the dashboards or for all the reports in the workspace, you'll have to remove a filter. By
default, the personalized report is filtered to display metrics for only the dashboard or report that was used to
create it.
If, for example, you used the dashboard named "European sales" to create this new personalized report, only
usage data from the "European sales" dashboard displays. To remove the filter, and enable data from all the
dashboards in that workspace:
1. Open the personalized report in Editing view.

2. In the Filters pane, locate the Report level filters bucket and remove the filter by selecting the "x".

Now your personalized report displays metrics for the entire workspace.
Admin controls for usage metrics - for Power BI administrators
Usage metrics reports are a feature that the Power BI or Office 365 administrator can turn on or off.
Administrators have granular control over which users have access to usage metrics; they are On by default for all
users in the organization.
1. Open the Admin portal by selecting the gear icon in the top-right-corner of Power BI service and choosing
Admin portal.

2. From the Admin portal, select Tenant settings and choose Usage metrics for content creators.

3. Enable (or disable) usage metrics and select Apply.

By default, per-user data is enabled for usage metrics, and content creator account information is included in the
metrics report. If you don’t want to include this information for some or all users, disable the feature for specified
security groups or for an entire organization. Account information then shows in the report as Unnamed.
When disabling usage metrics for their entire organization, admins can use the delete all existing usage
metrics content option to delete all existing reports and dashboard tiles that were built using the usage metrics
reports and datasets. This option removes all access to usage metrics data for all users in the organization who
may already be using it. Be careful, because deleting existing usage metrics content is irreversible.

Usage metrics in national clouds

Power BI is available in separate national clouds. These clouds offer the same levels of security, privacy,
compliance and transparency as the global version of Power BI, combined with a unique model for local
regulations on service delivery, data residency, access, and control. Due to this unique model for local regulations,
usage metrics are not available in national clouds. For more information, see national clouds.

Considerations and limitations

It's important to understand that differences that can occur when comparing usage metrics and audit logs, and
why. Audit logs are collected using data from the Power BI service, and Usage metrics are collected on the client.
Because of that difference, aggregate counts of activities in audit logs may not always match usage metrics,
because of the following:
Usage metrics may sometimes undercount activities due to inconsistent network connections, ad blockers, or
other issues that can disrupt sending the events from the client.
Certain types of views are not included in usage metrics, as described earlier in this article.
Usage metrics may sometimes overcount activities, in situations where the client refreshes without the need
for a request being sent back to the Power BI service.

Frequently asked questions

In addition to potential differences between usage metrics and audit logs, the following questions and answers
about usage metrics may be helpful for users and administrators:
Q: I can't run usage metrics on a dashboard or report
A: You can only see usage metrics for content you own or have permissions to edit.
Q: Do usage metrics capture views from embedded dashboards and reports?
A: Usage metrics currently does not support capturing usage for embedded dashboards, reports, and the publish
to web flow. In those cases, we recommend using existing web analytics platforms to track usage for the hosting
app or portal.
Q: I can't run usage metrics on any content at all.
A1: Admins can turn off this feature for their organization. Contact your Admin to see if this is the case.
A2: Usage metrics is a Power BI Pro feature.
Q: The data doesn't seem up-to-date. For example, distribution methods don't show up, report pages are missing,
etc.
A: It can take up to 24 hours for data to update.
Q: There are four reports in the workspace but the usage metrics report only displays three.
A: The usage metrics report only includes reports (or dashboards) that have been accessed in the past 90 days. If
a report (or dashboard) does not show up, likely it hasn't been used in more than 90 days.

Next steps
Favorite a dashboard
More questions? Try the Power BI Community
 Create a QR code for a report in Power BI to use in
the mobile apps
1/14/2019 • 2 minutes to read • Edit Online

QR codes in Power BI can connect anything in the real world directly to related BI information no navigation or
search needed.
You can create a QR code in the Power BI service for any report, even for a report you can't edit. Then you place
the QR code in a key location. For example, you could paste it in an email, or print it out and paste it in a specific
location.
Colleagues you've shared the report with can scan the QR code for access to the report, right from their mobile
device. They can use either the QR code scanner located in the Power BI app, or any other QR scanner installed on
their device. They can also scan a report QR code with the Power BI for Mixed Reality app.

Create a QR code for a report

1. Open a report in the Power BI service.
2. Select the ellipsis (...) in the top-right corner and select Generate QR code.

3. A dialog box with the QR code appears.

4. From here you can scan the QR code or download and save it so you can:
Add it to an email or other document, or
Print it and place it in a specific location.

Print the QR code

Power BI generates the QR code as a JPG file, ready to print.
1. Select Download, then open the JPG file on a computer connected to a printer.
 The JPG file has the same name as the tile. For example, "Sales and Marketing Sample.jpg".
2. Print the file at 100% or “actual size”.
3. Cut out the QR code along its edge and glue it to a place relevant to the report.

Next steps
Connect to Power BI data from the real world with the mobile apps
Scan a Power BI QR code from your mobile device
Create a QR code for a tile
Questions? Try asking the Power BI Community
 Export a report from Power BI service to Desktop
(Preview)
1/14/2019 • 2 minutes to read • Edit Online

In Power BI Desktop, you can export (also referred to as download) a report to Power BI service by saving the
report and selecting Publish. You can also export in the other direction as well, and download a report from Power
BI service to Desktop. The extension for files being exported, in either direction, is .pbix.
There are a few limitations and considerations to keep in mind, which are discussed later in this article.

Download the report as a .pbix

To download the .pbix file, follow these steps:
1. In Power BI service, open the report you want to download in Editing view.
2. From the menubar, select File > Download report.

NOTE
The report must have been created using Power BI Desktop after November 23, 2016 - and updated since then - to
be able to download the report. If it hasn't, the Download Report menu option in Power BI service is grayed out.

3. While the .pbix file is being created, a status banner displays the progress. When the file is ready, you'll be
asked to open or save the .pbix file. The name of the file matches the title of the report.

You now have the option of opening the .pbix file in either Power BI service (app.powerbi.com) or Power BI
Desktop.
4. To immediately open the report in Desktop, select Open. To save the file to a specific location, select Save >
Save-As. If you haven't already, install Power BI Desktop.
When you open the report in Desktop, you may see a warning message letting you know that some features
available in the Power BI service report may not be available in Desktop.
5. The report editor in Desktop looks very much like the report editor in Power BI service.

Considerations and troubleshooting

There are a few important considerations and limitations associated with downloading (exporting) a .pbix file from
Power BI service.
To download the file, you must have edit access to the report
The report must have been created using Power BI Desktop and been published to the Power BI service, or
the .pbix must have been uploaded to the service.
Reports must be published or updated after November 23, 2016. Reports published prior to then are not
downloadable.
This feature will not work with reports originally created in the Power BI service, including content packs.
You should always be using the latest version of Power BI Desktop when opening downloaded files.
Downloaded .pbix files may not open in non-current versions of Power BI Desktop.
If your administrator has turned off the ability to export data, this feature will not be visible in the Power BI
service.
Dataset with incremental refresh can't be downloaded to a .pbix file.

Next steps
View the Guy in a Cube one-minute video about this feature:
https://www.youtube.com/embed/ymWqU5jiUl0
Also, here are some additional articles that can help you learn to use Power BI service:
Reports in Power BI
Power BI - Basic Concepts
Once you get Power BI Desktop installed, the following content can help you get up and running quickly:
Getting Started with Power BI Desktop
More questions? Try the Power BI Community
 Filter a report using query string parameters in the
URL
2/1/2019 • 6 minutes to read • Edit Online

When you open a report in Power BI service, each page of the report has its own unique URL. To filter that report
page, you could use the Filters pane on the report canvas. Or you could add query string parameters to the URL
to pre-filter the report. Perhaps you have a report you'd like to show colleagues and you want to pre-filter it for
them. One way to filter it is to start with the default URL for the report, add the filter parameters to the URL, and
then email them the entire new URL.

Uses for query string parameters

Say you're working in Power BI Desktop. You want to create a report that has links to other Power BI reports, but
you want to show only some of the information in the other reports. First, filter the reports using query string
parameters and save the URLs. Next, create a table in Desktop with these new report URLs. Then publish and
share the report.
Another use for query string parameters is for someone creating an advanced Power BI solution. Using DAX, she
creates a report that generates a filtered report URL dynamically based on the selection her customer makes in
the current report. When customers select the URL, they see only the intended information.

Query string parameter syntax for filtering

With parameters, you can filter the report for one or more values, even if those values contain spaces or special
characters. The basic syntax is fairly straightforward; start with the report URL, add a question mark, and then
add your filter syntax.
URL?filter=Table/Field eq 'value'

Table and Field names are case-sensitive, value isn't.

 Fields that are hidden from report view can still be filtered.
Reports in apps
If you want to add a URL filter to a report in an app, the formatting is a little different. Links to reports in an app
have a query parameter (ctid) that gets added to the URL. Query parameters need to be separated by an
ampersand (&). So you need to append the query with “&filter=” (after the ctid parameter) instead of “?filter=”.
Like this example:
app.powerbi.com/groups/me/apps/app -id/reports/report-id/ReportSection?ctid=ctid&filter=Table/Field eq
'value'
Field types
Field type can be a number, datetime, or string and the type used must match the type set in the dataset. For
example, specifying a table column of type "string" won't work if you're looking for a datetime or numeric value in
a dataset column set as a date, such as Table/StringColumn eq 1.
Strings must be enclosed with single quotes - 'manager name'.
Numbers require no special formatting
Dates and times must be enclosed with single quotes. In OData v3 they must be preceded by the word
datetime, but datetime isn’t needed in OData v4.
If it's still confusing, continue reading and we'll break it down.

Filter on a field
Let’s assume that the URL to our report is the following.

And we see in our map visualization (above) that we have stores in North Carolina.

NOTE
This example is based on the Retail Analysis sample.

To filter the report to show data only for stores in "NC" (North Carolina), append the URL with the following;
?filter=Store/Territory eq 'NC'

NOTE
NC is a value stored in the Territory field of the Store table.

Our report is filtered for North Carolina; all the visualizations on the report page show data for only North
Carolina.
Filter on multiple fields
You can also filter on multiple fields by adding additional parameters to your URL. Let's go back to our original
filter parameter.

?filter=Store/Territory eq 'NC'

To filter on additional fields, add an 'and' and another field in the same format as above. Here is an example.

?filter=Store/Territory eq 'NC' and Store/Chain eq 'Fashions Direct'

https://www.youtube.com/embed/0sDGKxOaC8w?showinfo=0

Operators
Power BI supports many operators in addition to 'and'. The table below lists those operators along with the
content type they support.

OPERATOR DEFINITION STRING NUMBER DATE EXAMPLE

and and yes yes yes product/price le

200 and price gt
3.5

eq equals yes yes yes Address/City eq

'Redmond'

ne not equal yes yes yes Address/City ne

'London'

ge greater than or no yes yes product/price ge

equal 10

gt greater than no yes yes product/price gt

20
 OPERATOR DEFINITION STRING NUMBER DATE EXAMPLE

le less than or no yes yes product/price le

equal 100

lt less than no yes yes product/price lt

20

in** including yes yes yes Student/Age in

(27, 29)

** When using in, the values to the right of in can be a comma-separated list enclosed in parentheses, or a single
expression that returns a collection.
Numeric data types
A Power BI URL filter can include numbers in the following formats.

NUMBER TYPE EXAMPLE

integer 5

long 5 L or 5 l

double 5.5 or 55e-1 or 0.55e+1 or 5D or 5d or 0.5e1D or 0.5e1d or

5.5D or 5.5d or 55e-1D or 55e-1d

decimal 5 M or 5 m or 5.5 M or 5.5 m

float 5 F or 5 f or 0.5e1 F or 0.5e-1 d

Date data types

Power BI supports both OData V3 and V4 for Date and DateTimeOffset data types. Dates are represented
using the EDM format (2019-02-12T00:00:00), so when you specify a date as YYYY -MM -DD, Power BI interprets
it as YYYY -MM -DDT00:00:00.
Why does this distinction matter? Let's say you create a query string parameter Table/Date gt 2018-08-03. Will
the results include August 3, 2018 or start with August 4, 2018? Since Power BI translates your query to
Table/Date gt 2018-08-03T00:00:00, your results include any dates that have a non-zero time part since those
dates would be greater than 2018-08-03T00:00:00.

Special characters in URL filters

Special characters and spaces require some additional formatting. When your query contains spaces, dashes, or
other non-ASCII characters, prefix those special characters with an escape code starting with an underscore and
an X (_x), then the four-digit Unicode, then another underscore. If the Unicode is fewer than four characters, you
need to pad it with zeroes. Here are some examples.

IDENTIFIER UNICODE CODING FOR POWER BI

Table Name Space is 0x20 Table_x0020_Name

Column@Number @ is 0x40 Column_x0040_Number

 IDENTIFIER UNICODE CODING FOR POWER BI

[Column] [ is 0x0058 ] is 0x0050 _x0058_Column_x0050

Column+Plus + is 0x2B Column_x002B_Plus

Table_x0020_Name/Column_x002B_Plus eq 3

Table_x0020_Special/x005B_Column_x0020_Brackets_x005D eq '[C ]'

Use DAX to filter on multiple values

Another way to filter on multiple fields is by creating a calculated column that concatenates two fields to a single
value. Then you can filter on that value.
For example, we have two fields: Territory and Chain. In Power BI Desktop, create a new Calculated column
(Field) called TerritoryChain. Remember that the Field name can't have any spaces. Here is the DAX formula for
that column.
TerritoryChain = [Territory] & " - " & [Chain]
Publish the report to Power BI service and then use the URL query string to filter to display data for only
Lindseys stores in NC.

https://app.powerbi.com/groups/me/reports/8d6e300b-696f-498e-b611-41ae03366851/ReportSection3?
filter=Store/TerritoryChain eq 'NC – Lindseys'

Pin a tile from a filtered report

Once you've filtered the report using query string parameters, you can pin visualizations from that report to your
dashboard. The tile on the dashboard displays the filtered data and selecting that dashboard tile opens the report
that was used to create it. However, the filtering you did using the URL isn't saved with the report. When you
select the dashboard tile, the report opens in its unfiltered state. Thus, the data displayed in the dashboard tile
doesn't match the data displayed in the report visualization.
This discrepancy is helpful when you want to see different results; filtered on the dashboard and unfiltered in the
report.

Considerations and troubleshooting

There are a couple of things to be aware of when using the query string parameters.
When using the in operator, the values to the right of in must be a comma-separated list enclosed in
parentheses.
 In Power BI Report Server, you can pass report parameters by including them in a report URL. These URL
parameters aren't prefixed because they're passed directly to the report processing engine.
Query string filtering doesn't work with Publish to web.
Embed with report web part in SharePoint Online doesn't support URL filters.
The long data type is (2^53-1) due to Javascript limitations.
Report URL filters have a 10-expression limit (10 filters connected by AND ).

Next steps
Pin a visualization to a dashboard
Sign up for a free trial
More questions? Try asking the Power BI Community
 Power BI performance best practices
1/14/2019 • 9 minutes to read • Edit Online

This article offers guidance for building fast and reliable reports in Power BI.

Use filters to limit report visuals to display only what’s needed

The more data that a visual needs to display, the slower that visual will be to load. While this principle seems
obvious, it can be easy to forget. For example: suppose you have a large dataset. Atop of that, you build a report
with a table of the table. End users use slicers on the page to get to the rows they wanted – typically they’re only
interested in a few dozen rows.
A common mistake is to have the default view of the table be unfiltered - that is, all 100M+ rows. The data for
these rows must be loaded into memory and uncompressed at every refresh. This created huge memory loads.
The solution: reduce the max number of items that the table displayed using the “Top N” filter. The max item can be
much larger than what users would need, for example, 10,000. As a result, the end-user experience was unchanged,
but memory utilization of the report dropped multiple orders of magnitude, and performance improved
accordingly.
A similar approach to the above is suggested for all visuals on your reports. Ask yourself, is all the data in this
visual needed? Are there ways to filter down the amount of data shown in the visual with minimal impact to the
end-user experience? Note that tables in particular can be expensive.

Limit visuals on report pages

The above principle applies equally to the number of visuals on a particular report. It's highly recommended you
limit the number of visuals on a particular report to only what is necessary. Drill-through pages are a great way to
provide additional details without jamming more visuals into the report.

Optimize your model

Some best practices:
Tables or columns that are unused should be removed if possible.
Avoid distinct counts on fields with high cardinality – that is, millions of distinct values.
Take steps to avoid fields with unnecessary precision and high cardinality. For example, you could split highly
unique datetime values into separate columns – for example, month, year, date, etc. Or, where possible, use
rounding on high-precision fields to decrease cardinality – (for example, 13.29889 -> 13.3).
Use integers instead of strings, where possible.
Be wary of DAX functions, which need to test every row in a table – for example, RANKX – in the worst case,
these functions can exponentially increase run-time and memory requirements given linear increases in table
size.
When connecting to data sources via DirectQuery, consider indexing columns that are commonly filtered or
sliced again – this will greatly improve report responsiveness.
For more guidance on optimizing data sources for DirectQuery, see DirectQuery in SQL Server 2016 Analysis
Services.

DirectQuery and Live connection: understand underlying data source

performance
In the DirectQuery or live connection case, when users visit a Power BI report, Power BI sends queries in real time
to the underlying data source. Once the data source returns with the query data, then the report is rendered. As a
result, your report performance in these cases depends largely on the performance of the underlying data source.
In these cases, it will be important to understand the performance of your underlying data source. Different data
sources will have different tools for understanding query performance. For example, SQL Server and Azure SQL
provide the Query Store, which captures a history of queries and their runtime statistics.
As a rule of thumb, when deploying Power BI reports built on DirectQuery and live connection, try out what your
end users will do in Power BI Desktop. If the report is slow to load in Power BI Desktop, it will almost certainly be
slow to load in the service for your end users.

DirectQuery best practices

The following section describes general best practices for connecting via DirectQuery.
DB design guidance
Push calculated columns and measures to the source where possible – the closer they are to the source, the
higher the likelihood of performance.
Optimize! Understand the execution plans for your queries, add indices for commonly filtered columns, etc.
Modeling guidance
Start in the Power BI Desktop.
Avoid complex queries in Query Editor.
Do not use relative date filtering in the Query Editor.
Keep measures simple initially, and add complexity incrementally.
Avoid relationships on calculated columns and unique identifier columns.
Try setting “Assume Referential Integrity” on relationships – in many cases, this can significantly improve query
performance.
General
Apply filters first.
Consider switching off interaction between visuals – this will reduce the query load when users cross-highlight.
Limit the number of visuals and the data per visuals, as described above.
Enabling row -level security can result in substantial changes in performance. Be sure to test the different row -
level security roles that your users will assume.
There are query-level time-outs enforced by the service to ensure that long-running queries cannot monopolize
system resources. Queries that take longer than 225 seconds will time out and result in a visual-level error.

Understand dashboards and query caches

Visuals pinned to dashboards are served by the query cache when the dashboard is loaded. Conversely, when
visiting a report, the queries are made on-the-fly to the data source – either the Power BI service (in the case of
import) or the data source that you specify (in the case of DirectQuery or live connection).

NOTE
When you pin live report tiles a dashboard, they are not served from the query cache – instead, they behave like reports,
and make queries to back-end cores on the fly.

As the name suggests, retrieving the data from the query cache provides better and more consistent performance
than relying on the data source. One way to take advantage of this functionality is to have dashboards be the first
landing page for your users. Pin often used and highly requested visuals to the dashboards. In this way,
dashboards become a valuable “first line of defense”, which provide consistent performance with less load on the
capacity. Users can still click through to the report to dig into the details.
For DirectQuery and live connection, this query cache is updated on a periodic basis by querying the data source.
By default, this happens every hour, though it can be configured in dataset settings. Each query cache update will
send queries to the underlying data source to update the cache. The number of queries generated depends on the
number of visuals pinned to dashboards relying on that data source. Notice that if row -level security is enabled,
queries are generated for each different security context. For example, if you have two different roles that your
users fall into, with two different views of the data, then during query cache refresh, two sets of queries are
generated.

Understand custom visual performance

Be sure to put each custom visual through its paces to ensure high performance. Poorly optimized custom visuals
can negatively affect the performance of the entire report.

Deep-dive into query performance with SQL Profiler and Power BI

Desktop
For a deeper dive into which visuals are taking up the most time and resources, you can connect SQL Profiler to
Power BI Desktop to get all full view of query performance.

NOTE
Power BI desktop supports connecting to a diagnostics port. The diagnostic port allows for other tools to connect to and
perform traces for diagnostic purposes. Making any changes to the model is not supported! Changes to the model may
lead to corruption and data loss.

Instructions as follows:
1. Install SQL Server Profiler and run Power BI Desktop
SQL Server Profiler is available as part of SQL Server Management Studio.
2. Determine the port being used by Power BI Desktop
Run the command prompt or PowerShell with administrator privileges, and use netstat to find the port that
Power BI Desktop is using for analysis:
> netstat -b -n

The output should be a list of applications and their open ports, for example:
TCP [::1]:55786 [::1]:55830 ESTABLISHED

[msmdsrv.exe]
Look for the port used by msmdsrv.exe, and write it for later use. In this case, you use port 55786.
3. Connect SQL Server Profiler to Power BI Desktop
Start SQL Server Profiler from the Start menu
File > New Trace
Server Type: Analysis Services
Server name: localhost:[port number found above]
 At the next screen, select Run
Now the SQL Profiler is live, and actively profiling the queries that Power BI Desktop is sending.
As queries are executed, you can see their respective durations and CPU times – using this information,
you can determine which queries are the bottlenecks.
Through the SQL Profiler, you can identify the queries, which are taking up the longest CPU time, which in turn
are likely the performance bottlenecks. The visuals, which execute those queries should be a focal point of
continued optimization.

Gateway best practices

The On-premises data gateway is a great tool for connecting the Power BI service with your on-premises data. At
the same time, with poor planning, it can also become a bottleneck for report performance. This is especially true
for DirectQuery/live connection datasets, where all queries and query responses pass through the gateway. The
following are some best practices for ensuring highly performant gateways:
Use the Enterprise mode, as opposed to the personal mode.
Recommended hardware specs for the gateway – eight CPU cores, 16-GB RAM.
Set up monitoring – set up performance monitoring on the gateway machine understand whether the
gateway is becoming overloaded and becoming a bottleneck. For more information, see Troubleshooting the
On-premises data gateway.
Scale up or scale out – if the gateway is indeed becoming a bottleneck, then consider scaling up (that is,
moving the gateway to a more powerful machine with more CPU and RAM ) or scaling out (for example,
splitting out datasets onto different gateways).
Separate import vs. DirectQuery – if scaling out, consider separating the gateways responsible for import vs.
those responsible for DirectQuery.

Network latency
Network latency can impact report performance by increasing the time required for requests to reach the Power BI
service, and for responses to be delivered. Tenants in Power BI are assigned a specific region. You can view your
tenant’s “home” region by navigating to powerbi.com, selecting?** in the top right and then About Power BI.
When users from a tenant access the Power BI service, their requests are always routed to this region. Once the
requests reach the Power BI service, the service may then send additional requests – for example, to the underlying
data source or the gateway – which are also subject to network latency.
Tools such as Azure Speed Test can provide an indication of network latency between the client and the Azure
region. In general, to minimize the impact of network latency, strive to keep data sources, gateways, and your
Power BI cluster as close as possible. If network latency is an issue, you can try locating gateways and data sources
closer to your Power BI cluster by placing them on virtual machines.
To further improve network latency, consider using Azure ExpressRoute, which is able of creating faster, more
reliable network connections between your clients and Azure datacenters.

Next steps
Planning a Power BI Enterprise Deployment, with all-around guidance on large-scale Power BI deployments
DirectQuery in SQL Server 2016 Analysis Services
[YouTube] Building Fast and Reliable Reports in Power BI
[YouTube] Power BI Enterprise Deployments
 Get started with Power BI Q&A
1/14/2019 • 2 minutes to read • Edit Online

Sometimes the fastest way to get an answer from your data is to ask a question using natural language. In this
quickstart we'll look at two different ways of creating the same visualization: first, building it in a report and,
second, asking a question with Q&A. We'll use Power BI service, but the process is almost identical using Power BI
Desktop.
To follow along, you must use a report that you can edit, so we'll use one of the samples available with Power BI.

Create a visual in the report editor

1. From your Power BI workspace, select Get Data > Samples > Retail Analysis Sample > Connect.
2. The dashboard contains an area chart tile for "Last Year Sales and This Year Sales." Select this tile. If this tile
was created with Q&A, selecting the tile will open Q&A. But this tile was created in a report, so the report
opens to the page that contains this visualization.

3. Open the report in Editing View by selecting Edit Report. If you aren't the owner of a report, you don't
have the option to open the report in Editing view.

4. Select the area chart and review the settings in the Fields pane. The report creator built this chart by
selecting these three values (Time > FiscalMonth, Sales > This Year Sales, Sales >Last Year Sales
>Value) and organizing them in the Axis and Values wells.
Create the same visual with Q&A
How would we go about creating this same line chart using Q&A?

1. Navigate back to the Retail Analysis Sample dashboard.

2. Using natural language, type something like this question into the question box:
what were this year sales and last year sales by month as area chart
As you type your question, Q&A picks the best visualization to display your answer; and the visualization
changes dynamically as you modify the question. Also, Q&A helps you format your question with
suggestions, autocomplete, and spelling corrections.
When you finish typing your question, the result is the exact same chart that we saw in the report. But
creating it this way was much faster!
3. Similar to working with reports, within Q&A you have access to the Visualizations, Filters, and Fields panes.
Open these panes to further explore and modify your visual.

4. To pin the chart to your dashboard, select the pin icon .

Next steps
Q&A in Power BI
Make your data work well with Q&A in Power BI
More questions? Try the Power BI Community
 Tutorial: How to use Q&A to create visualizations and
build reports
1/14/2019 • 5 minutes to read • Edit Online

The Q&A overview introduced you to Power BI Q&A and made the distinction between consumers (have
dashboards and reports shared with them) and creators (own the underlying reports and datasets). The first part
of this tutorial is designed primarily for people consuming dashboards using Power BI service. And the second
part is designed for people creating reports using either Power BI service or Power BI Desktop. Q&A and Power
BI mobile and Q&A with Power BI Embedded are covered in separate articles.
Q&A is interactive and even fun, and, more often than not, one question will lead to many others as the
visualizations reveal interesting paths to pursue. Watch Amanda demonstrate using Q&A to create visualizations,
dig into those visuals, and pin them to dashboards.
https://www.youtube.com/embed/qMf7OLJfCz8?list=PL1N57mwBHtN0JFoKSR0n-tBkUJHeMP2cP

Part 1: Use Q&A on a dashboard in Power BI service

(app.powerbi.com)
A dashboard contains tiles pinned from one or more datasets, so you can ask questions about any of the data
contained in any of those datasets. To see what reports and datasets were used to create the dashboard, select
View related from the menubar.

The Q&A question box is located in the upper-left corner of your dashboard, and this is where you type your
question using natural language. Q&A recognizes the words you type and figures out where (which dataset) to
find the answer. Q&A also helps you form your question with auto-completion, restatement, and other textual and
visual aids.

The answer to your question is displayed as an interactive visualization and updates as you modify the question.
1. Open a dashboard and place your cursor in the question box. Even before you start typing, Q&A displays a
new screen with suggestions to help you form your question. You'll see the names of the tables in the
underlying dataset(s) and may even see complete questions listed if the dataset owner has created featured
 questions,

You can always choose one of these questions as a starting point and continue to refine the question to find
the specific answer you are looking for. Or, use a table name to help you word a new question.
2. Select from the dataset options or begin typing your own question and select from the dropdown
suggestions.

3. As you type a question, Q&A picks the best visualization to display your answer; and the visualization
changes dynamically as you modify the question.
4. When you type a question, Power BI looks for the best answer using any dataset that has a tile on that
dashboard. If all the tiles are from datasetA, then your answer will come from datasetA. If there are tiles
from datasetA and datasetB, then Q&A will search for the best answer from those 2 datasets.

TIP
So be careful, if you only have one tile from datasetA and you remove it from your dashboard, Q&A will no longer
have access to datasetA.

5. When you're happy with the result, pin the visualization to a dashboard by selecting the pin icon in the top
right corner. If the dashboard has been shared with you, or is part of an app, you won't be able to pin.

Part 2: Use Q&A in a report in Power BI service or Power BI Desktop

Use Q&A to explore your dataset and to add visualizations to the report and to dashboards. A report is based on a
single dataset and may be completely blank or contain pages full of visualizations. But just because a report is
blank, doesn't mean there isn't any data for you to explore -- the dataset is linked to the report and is waiting for
you to explore and create visualizations. To see which dataset is being used to create a report, open the report in
Power BI service Reading view and select View related from the menubar.
In order to use Q&A in reports, you must have edit permissions for the report and underlying dataset. In the Q&A
Overview topic we referred to this as a creator scenario. So if you are, instead, consuming a report that has been
shared with you, Q&A will not be available.
1. Open a report in Editing view (Power BI service) or Report view (Power BI Desktop) and select Ask a
question from the menubar.
Desktop

Service

2. A Q&A question box displays on your report canvas. In the example below, the question box displays on
top of another visualization. This is fine, but it might be better to add a blank page to the report before
asking a question.

3. Place your cursor in the question box. As you type, Q&A displays suggestions to help you form your
question.
4. As you type a question, Q&A picks the best visualization to display your answer; and the visualization
changes dynamically as you modify the question.

5. When you have the visualization you like, select ENTER. To save the visualization with the report, select File
> Save.
6. Interact with the new visualization. It doesn't matter how you created the visualization -- all the same
interactivity, formatting, and features are available.

If you've created the visualization in Power BI service, you can even pin it to a dashboard.

Tell Q&A which visualization to use.

With Q&A, not only can you ask your data to speak for itself, you can tell Power BI how to display the answer. Just
add "as a " to the end of your question. For example, "show inventory volume by plant as a map" and "show total
inventory as a card". Try it for yourself.

Considerations and troubleshooting

If you've connected to a dataset using a live connection or gateway, Q&A needs to be enabled for that
dataset.
You've opened a report and don't see the Q&A option. If you're using Power BI service, make sure the
report is open in Editing view. If you can't open Editing view it means you don't have edit permissions for
that report and won't be able to use Q&A with that specific report.

Next steps
Back to Q&A in Power BI
Tutorial: Use Q&A with the Retail Sales sample
Tips for asking questions in Q&A
Prepare a workbook for Q&A
Prepare an on-premises dataset for Q&A Pin a tile to the dashboard from Q&A
 How to make your Excel data work well with Q&A in
Power BI
1/30/2019 • 2 minutes to read • Edit Online

If you are a person who creates data models or builds Excel workbooks that will be used with Power BI, read on...
In Power BI, Q&A can search structured data and choose the right visualization for your question -- that's what
makes it a compelling tool to use.
Q&A can work on any uploaded Excel file that has tables, ranges, or contains a PowerPivot model, but the more
optimizations and data cleaning you do, the more robust Q&A performance is. If you plan on sharing reports and
dashboards based on your dataset, you'll want your colleagues to have an easy time asking questions and getting
quality answers.
How Q&A works with Excel
Q&A has a set of core natural language understanding abilities that work across your data. It has context-
dependent keyword search for your Excel table, column, and calculated field names. It also has built-in knowledge
for how to filter, sort, aggregate, group, and display data.
For example, in an Excel table named “Sales”, with columns “Product”, “Month”, “Units Sold”, “Gross Sales”, and
“Profit”, you could ask questions about any of those entities. You could ask to show sales, total profit by month,
sort products by units sold, and many others. Read more about the kinds of questions you can ask, and
visualization types you can specify in a Q&A query.
Prepare an Excel dataset for Q&A
Q&A relies on the names of tables, columns, and calculated fields to answer data-specific questions, meaning what
you call entities in your workbook is important!
Here are some tips for making the most of Q&A in your workbook.
Make sure your data is in an Excel table. Here's how to create an Excel table.
Make sure the names of your tables, columns, and calculated field make sense in natural speech.
For example, if you have a table with sales data, call the table “Sales”. Column names like “Year”, “Product”,
“Sales Rep”, and “Amount” will work well with Q&A.
If your workbook has a Power Pivot data model, you can do even more optimizations. Read more about
Demystifying Power BI Q&A part 2 from our in-house team of natural language experts.
Open the dataset in Power BI Desktop and create new columns, create calculated measures, concatenate
fields to create unique values, classify data by type (e.g., dates, strings, geography, images, URLs), and more.

Next steps
Back to Q&A in Power BI
Prepare on-premises datasets for Q&A
Q&A quickstart
Get data (for Power BI)
More questions? Try the Power BI Community
 Create featured questions for Power BI Q&A
1/14/2019 • 2 minutes to read • Edit Online

If you own a dataset, you can add your own featured questions to that dataset. And Power BI Q&A will show those
questions to colleagues who use (consume) your dataset. Featured questions give your colleagues ideas about the
types of questions they can ask about the dataset. The featured questions you add are up to you -- add popular
questions, questions that display interesting results, or questions that may be hard to phrase.
Watch Will add some featured questions to Power BI Q&A and then use those featured questions to explore his
dataset. Then follow the step-by-step instructions below the video to try it out yourself.
https://www.youtube.com/embed/E1mIAyEXuF4

NOTE
Q&A featured questions are available for use in the Microsoft Power BI app for iOS on iPads, iPhones, and iPod Touch
devices and Power BI Desktop Q&A Preview. But creating the questions is only available in Power BI service
(app.powerbi.com).

This article uses the Retail Analysis Sales sample.

1. On the dashboard, select the Q&A question box. Notice that Q&A is already being helpful by displaying a
list of terms that appear in the dataset.
2. To add to this list, select the gear icon in the top right corner of Power BI.

3. Select Settings > Datasets > Retail Analysis sample > Featured Q&A Questions.
4. Select Add a question.

5. Type your question in the text box and select Apply. Optionally, add another question by selecting Add a
question.
6. Navigate back to the Power BI dashboard for Retail Analysis Sample, and place your cursor in the Q&A
question box.

7. The new featured question, Sales by territory as a map, is first in the list. Select it.
8. The answer displays as a filled map visualization.

Next steps
Q&A in Power BI
Tutorial: Introduction to Power BI Q&A
Power BI - Basic Concepts
More questions? Try the Power BI Community
 Visualization types in Power BI
2/21/2019 • 3 minutes to read • Edit Online

Power BI visualizations
We'll be adding new visualizations, stay tuned!
And check out the Microsoft AppSource , where you'll find a growing list of custom visuals you can
download and use in your own dashboards and reports. Feeling creative? Learn how to create and add your
own visuals to this community site.

List of visualizations available in Power BI

All of these visualizations can be added to Power BI reports, specified in Q&A, and pinned to dashboards.
Area charts: Basic (Layered) and Stacked

TIP
The Basic Area chart is based on the line chart with the area between the axis and line filled in.

For more information, see Basic Area chart.

Bar and column charts

TIP
Bar charts are the standard for looking at a specific value across different categories.
Cards: Multi row

Cards: Single number

For more information, see Create a Card (big number tile).

Combo charts

TIP
A Combo chart combines a column chart and a line chart. Choose from Line and Stacked Column and Line and
Clustered Column.

For more information, see Combo charts in Power BI.

Doughnut charts

TIP
Doughnut charts are similar to Pie charts. They show the relationship of parts to a whole.

For more information, see Doughnut charts in Power BI.

Funnel charts
 TIP
Funnels help visualize a process that has stages and items flow sequentially from one stage to the next. Use a funnel
when there is a sequential flow between stages, such as a sales process that starts with leads and ends with purchase
fulfillment.

For more information, see Funnel Charts in Power BI.

Gauge charts

TIP
Displays current status in the context of a goal.

For more information, see Gauge Charts in Power BI.

Key influencers chart

A key influencer chart displays the major contributors to a selected result or value.
For more information, see Key influencer charts in Power BI
KPIs
 TIP
Displays progress toward a measurable goal.

For more information, see KPIs in Power BI.

Line charts

TIP
Emphasize the overall shape of an entire series of values, usually over time.

Maps: Basic maps

TIP
Used to associate both categorical and quantitative information with spatial locations.

For more information, see Tips and tricks for map visuals.
Maps: ArcGIS maps

For more information, see ArcGIS maps in Power BI.

Maps: Filled maps (Choropleth)
 TIP
The more intense the color, the larger the value.

For more information, see Filled Maps in Power BI.

Maps: Shape maps

TIP
Compares regions by color.

For more information, see Shape Maps in Power BI.

Matrix

For more information, see Matrix visuals in Power BI.

Pie charts
Pie charts show the relationship of parts to a whole.
Ribbon chart

Ribbon charts show which data category has the highest rank (largest value). Ribbon charts are effective at
showing rank change, with the highest range (value) always displayed on top for each time period.
Scatter and Bubble charts

TIP
Display relationships between 2 (scatter) or 3 (bubble) quantitative measures -- whether or not, in which order, etc.

For more information, see Scatter charts in Power BI.

Scatter-high density
 TIP
Too many data points on a visual can bog it down, so a sophisticated sampling algorithm is used to ensure the
accuracy of the visualization.

For more information, see High Density Scatter charts in Power BI.
Slicers

For more information, see Slicers in Power BI.

Standalone images

For more information, see Add an image widget to a dashboard.

Tables

TIP
Work well with quantitative comparisons among items where there are many categories.

For more information, see Working with tables in Power BI.

Treemaps
For more information, see Treemaps in Power BI.

TIP
Are charts of colored rectangles, with size representing value. They can be hierarchical, with rectangles nested within
the main rectangles.

Waterfall charts

TIP
Waterfall charts show a running total as values are added or subtracted.

For more information, see Waterfall charts in Power BI.

Tell Q&A which visualization to use

When typing natural language queries with Power BI Q&A, you can specify the visualization type in your
query. For example:
"sales by state as a treemap"

Next steps
Visualizations in Power BI reports
The right visual reference from sqlbi.com
 Enable Q&A for live connections in Power BI
1/14/2019 • 3 minutes to read • Edit Online

What is On-premises data gateway? What is a live connection?

Datasets in Power BI can be imported into Power BI or you can create a live connection to them. Live connection
datasets are often referred to as "on-premises". The live connections are managed using a gateway and data and
inquiries are sent back and forth using live queries.

Q&A for On-premises data gateway datasets

If you'd like to use Q&A with datasets you access through a gateway, you'll need to enable them first.
Once enabled, Power BI creates an index of your data source and uploads a subset of that data to Power BI to
enable asking questions. It may take several minutes to create the initial index and Power BI maintains and
updates the index automatically as your data changes. Using Q&A with these datasets behaves the same as with
data published to Power BI. The full set of features available in the Q&A experience is supported in both cases,
including using the data source with Cortana.
As you ask questions in Power BI, Q&A determines the best visual to construct or report sheet to use to answer
your question using an index of your dataset. After determining the best potential answer, Q&A uses DirectQuery
to fetch live data from the data source via the gateway to populate charts and graphs. This ensures Power BI Q&A
results always show the most up-to-date data directly from the underlying data source.
Since Power BI Q&A uses the text and schema values from your data source to determine how to query the
underlying model for answers, searches for specific new or deleted text values (such as asking for a customer
name related to a newly added text record) rely on the index being up-to-date with the latest values. Power BI
automatically keeps the text and schema index up to date within a 60 minute window of changes.
For more information, see:
What is the On-premises data gateway?
Introduction to Power BI Q&A

Enable Q&A
Once you have the data gateway set up, connect to your data from Power BI. Either create a dashboard using your
on-premises data, or upload a .pbix file that uses on-premises data. You may also already have on-premises data
in dashboards, reports, and datasets that have been shared with you.

1. In the upper-right corner of Power BI, select the cog icon and choose Settings.
2. Select datasets and choose the dataset to enable for Q&A.

3. Expand Q&A and Cortana, select the checkbox for Turn on Q&A for this dataset and choose Apply.

What data is cached and how is privacy protected?

When you enable Q&A for your on-premises data, a subset of your data is cached in the service. This is done to
ensure that Q&A works with a reasonable performance. Power BI excludes values longer than 24 characters from
caching. The cache is deleted within a few hours when you disable Q&A by unchecking Turn on Q&A for this
dataset, or when you delete your dataset.

Considerations and troubleshooting

During the Preview phase of this feature, there are several limitations:
Initially the feature is only available for SQL Server 2016 Analysis Services Tabular data sources. The feature is
optimized to work with tabular data. The Q&A experience is not yet supported for multi-dimensional.
Additional data sources supported by the On-premises data gateway will be rolled out over time.
Full support for row level security defined in SQL Server Analysis Services is not available initially in the
public preview. While asking questions in Q&A, the “auto-complete” of questions while typing can show string
values a user does not have access to. However, RLS defined in the model is respected for report and chart
visuals so no underlying numerical data can be exposed. Options to control this behavior will be released in
coming updates.
Object level security (OLS ) is not supported. Q&A does not respect object level security and can reveal table
or column names to users who don't have access to them. You should enable RLS to ensure data values are
secured appropriately as well.
Live connections are only supported with the On-premises data gateway. As a result, this cannot be used with
the personal gateway.

Next steps
On-premises data gateway
Manage your data source - Analysis Services
Power BI - Basic Concepts
Power BI Q&A Overview
More questions? Try asking the Power BI Community
 Quickly find and view your Power BI data using
Cortana for Power BI
1/31/2019 • 5 minutes to read • Edit Online

Use Cortana across your Windows 10 devices to get instant answers to your important business questions. By
integrating with Power BI, Cortana can retrieve key information directly from Power BI dashboards and reports.
All it takes is Windows 10 November 2015 version or later, Cortana, Power BI, and access to at least one dataset.

Preview the new Cortana dashboard search experience for Windows 10

For a while now you've been able to use Cortana to retrieve certain types of report pages . Now we've added a
new experience -- the ability to also retrieve dashboards. Try it out and please send us feedback at Power BI
Ideas. Eventually the new experience will be extended to include Cortana search for reports as well. One of the key
benefits of the new experience is that you don't need to do anything special to set it up -- no enabling Cortana or
configuring Windows 10. It just works.

NOTE
If it doesn't "just work," see the Troubleshooting article for help.

The underlying technology is using Microsoft Azure Search Service. This search service provides extra capabilities
such as smart ranking, error correction, and auto complete.
Both Cortana experiences will exist side-by-side.

Cortana for Power BI documentation

We have four documents that guide you through setting up and using Cortana for Power BI. This series of articles
will take you through the steps to
Article 1 (this article): understand how Cortana and Power BI work together
Article 2: search Power BI reports: Enable the Cortana - Power BI - Windows integration
Article 3: search Power BI reports: create special Cortana answer cards
Article 4: Troubleshoot issues

How do Cortana and Power BI work together?

When you use Cortana to ask a question, Power BI can be one of the places Cortana looks for answers. In Power
BI, Cortana can find rich data-driven answers from Power BI reports (that contain a special type of report page
called a Cortana answer card) and from Power BI dashboards.
If Cortana finds a match, it displays the name of the dashboard or report page right there in your Cortana screen.
The dashboard or report page can be opened in Power BI. Report pages can also be explored right in Cortana -
they're interactive.
Cortana and Dashboards (the new experience)
Cortana can find answers in dashboards that you own and dashboards that have been shared with you. Ask
Cortana questions using titles, keywords, owner names, workspace names, app names, and more.
Your question must have at least two words for Cortana to find an answer. So if you search on a dashboard with a
one-word name (Marketing) add the word "show" or "Power BI" or the owner name to your question, as in "show
Marketing" and "michele hart sample".
If your dashboard title is more than one word, Cortana only returns that dashboard if your search matches at least
two of the words or one of the words plus the owner name. For a dashboard named "Customer Profitability
Sample":
"show me customer" will not return a Power BI dashboard result.
"utterances such as "show me customer profitability", "customer p", "customer s", "profitability sample",
"michele hart sample", "show customer profitability sample", and "show me customer p" will return a Power
BI result.
Adding the word "powerbi" counts as one of the two required words, so "powerbi sample" will return a
Power BI result.

Cortana and Reports

Cortana can find answers in reports that have pages designed specifically for display by Cortana. Just ask
questions using the title or keywords from one of these specialty report pages.
The underlying technology for reports is using Microsoft's Power BI Q&A.
When you ask a question in Cortana, Power BI answers from report pages designed specifically for Cortana.
Potential answers are determined by Cortana on the fly directly from the Cortana answer cards already created in
Power BI. To further explore an answer, open a result in Power BI.

NOTE
Before Cortana can look for answers in your Power BI reports, you'll need to enable this feature using the Power BI service
and set up Windows to communicate with Power BI.

Using Cortana to get answers from Power BI

1. Start in Cortana. There are many different ways to open Cortana: select the Cortana icon in the taskbar
(pictured below ), use voice commands, or tap the search icon on your Windows mobile device.

2. Once Cortana is ready, type or speak your question into the Cortana search bar. Cortana displays the
available results. If there is a Power BI dashboard that matches the question, it shows up under Best match
or Power BI.

NOTE
At the current time, only English is supported.

3. Select the dashboard to open it in Cortana.

 You can change the layout by editing the phone view of the dashboard.
4. From Cortana, you also have the options to open the dashboard in Power BI service or Power Bi mobile.
Open the dashboard in Power BI service by selecting Open on web.

5. Now let's use Cortana to search for a report. We'll need to know of a report that has a page with a Cortana
answer card . In this example, a report named "Cortana-New -Stores" has a Cortana answer card page
named "cortana stores".
Type or speak your question into the Cortana search bar. Cortana displays the available results. If there is a
Power BI report page that matches the question, it shows up under Best match or Power BI. And in this
example the .pbix file (and backup) that I used to create the answer card also displays -- under Documents.
6. Select the Cortana stores report page to display it in the Cortana window.

Remember, an answer card is a special type of Power BI report page that was created by a dataset owner.
For more information, see Create a Cortana answer card.
7. But that's not all. Interact with the visualizations on the answer card as you would in Power BI.
For example, select an element on one visualization to cross-filter and highlight the other
visualizations on the answer card.
 Or, use natural language to filter the results instead. For example, ask "Cortana stores for Lindseys"
and see the card filtered to only show data for the Lindseys chain.

8. Continue exploring. Scroll to the bottom of the Cortana window and select Open in Power BI.
9. The report page opens in Power BI.

Considerations and troubleshooting

Cortana will not have access to any Cortana cards that have not been enabled for Power BI.
Still can't get Cortana to work with Power BI? Try the Cortana troubleshooter.
Cortana for Power BI is currently only available in English.
Cortana for Power BI is only available on Windows mobile devices.
More questions? Try the Power BI Community. Feedback? Send feedback to Power BI Ideas.

Next steps
Enable the Cortana - Power BI - Windows integration for reports
 Enable Cortana to access Power BI reports (and their
underlying datasets)
2/13/2019 • 3 minutes to read • Edit Online

You've read the Introduction to Cortana and Power BI (if not, you might want to read that first and then come
back). And now you want to try it out yourself. Before you can ask natural language questions in Cortana and
find answers from data stored in Power BI reports, there are a few requirements. Specifically, you'll need to do
the following.

NOTE
If you are trying out the Cortana and Power BI dashboard preview, you can skip the rest of this article. There are no setup
requirements for Cortana to be able to search your Power BI dashboards.

In Power BI service
enable one or more datasets for Cortana (reports are built on top of datasets, so Cortana needs access to
those datasets)
In Microsoft Windows
Check that you are running Windows 10 version 1511 or later
Make sure that Power BI and Windows can "talk" to each other. This means connecting your account to
Windows.

Use Power BI service to enable Cortana to access report pages in

Power BI
Enabling reports in Power BI to be accessed by Cortana is a simple process. In fact all you have to do is enable
the report's underlying dataset by selecting “Enable Cortana to access this dataset”. After that, any user who has
access to the dataset in Power BI, via regular Power BI sharing, apps, and content pack features, will be able to
get answers from the report in Cortana in Windows 10.
You'll need to sign in to Power BI service (not Power BI Desktop) and repeat these steps for each dataset that you
want Cortana to be able to access.
1. Determine which dataset(s) to enable. From the report content list, select the report you'd like Cortana to
access and choose the View related icon .
2. The dataset associated with this report is Contoso Sales.

3. To the right of the dataset name, select the ellipses (...) > Settings.

4. Select Q&A and Cortana > Allow Cortana to access this dataset > Apply.

In this example, we're enabling Cortana on the Contoso Sales dataset.

NOTE
When a new dataset or Cortana answer card is added to Power BI and enabled for Cortana, it can take up to 30
minutes for results to begin appearing. Logging in and out of Windows 10, or otherwise restarting the Cortana
process in Windows 10, will allow new content to appear immediately.
If you enable a dataset for Cortana, and that dataset is part of a content pack or app you own, you will need to re-
publish for your colleagues to also be able to use it with Cortana.

Add your Power BI credentials to Windows

You'll need to be running Windows 10 version 1511 or higher.
1. Determine which Windows 10 version you are running. Open Settings.
 Then select System > About. Towards the bottom of the screen you'll see Windows specifications >
Version
If you have Windows 10 version 1511 (Windows 10 November 2015 Update) up until 1607, add your
work or school account and Microsoft account (complete steps 2 and 3 below ).
If you have Windows 10 version 1607 (Windows 10 July 2016 update) or later, add your work or
school account (complete only step 2 below ).
2. Add your work or school account for Cortana.
Open Settings > Accounts.

Scroll to the bottom and select Add a work or school account. Or, from the Accounts page
select Access work or school >Connect.

Cortana will use this work or school account to check Power BI for potential answers to your questions in
Cortana.

Next steps
Create Cortana answer cards in Power BI
Troubleshoot Cortana and Power BI integration issues
More questions? Try the Power BI Community
 Generate data insights automatically with Power BI
1/14/2019 • 2 minutes to read • Edit Online

Have a new dataset and not quite sure where to start? Need to build a dashboard quickly? Want to look for
insights you may have missed?
Run quick insights to generate interesting interactive visualizations based on your data. Quick insights can be run
on an entire dataset (quick insights) or on a specific dashboard tile (scoped insights). You can even run insights on
an insight!

NOTE
Insights doesn't work with DirectQuery - it only works with data uploaded to Power BI.

The insights feature is built on a growing set of advanced analytical algorithms developed in conjunction with
Microsoft Research that we’ll continue to use to allow more people to find insights in their data in new and
intuitive ways.

Run quick insights on a dataset

Watch Amanda run quick insights on a dataset, open an insight in Focus mode, pin one of these insights as a tile
on her dashboard, and then get insights for a dashboard tile.
https://www.youtube.com/embed/et_MLSL2sA8
Now it's your turn. Explore insights using the Supplier Quality Analysis sample.
1. From the Datasets tab, select the ellipses (...) and choose Get insights.

2. Power BI uses various algorithms to search for trends in your dataset.

3. Within seconds, your insights are ready. Select View insights to display visualizations.

NOTE
Some datasets can't generate insights because the data isn't statistically significant. To learn more, see Optimize your
data for insights.

4. The visualizations display in a special Quick Insights canvas with up to 32 separate insight cards. Each
card has a chart or graph plus a short description.

Interact with the insight cards

1. Hover over a card and select the pin icon to add the visualization to a dashboard.
2. Hover over a card, select the ellipses (...) and choose View insights. This opens the insight fullscreen.
3. In Focus mode you can:
Filter the visualizations. To display the filters, in the top right corner, select the arrow to expand the

Filters pane.

Pin the insight card to a dashboard by selecting the pin icon or Pin visual.
Run insights on the card itself. This is often referred to as scoped insights. In the top-right corner,
select the lightbulb icon or Get insights.

The insight displays on the left and new cards, based solely on the data in that single insight, display
along the right.
4. To return to the original insights canvas, in the top-left corner, select Exit Focus mode.

Run insights on a dashboard tile

Instead of searching for insights against an entire dataset, narrow your search to the data used to create a single
dashboard tile. This too is often referred to as scoped insights.
1. Open a dashboard.
2. Hover over a tile. select the ellipses (...), and choose View insights. The tile opens in Focus mode with the
insights cards displayed along the right.

3. Does one insight pique your interest? Select that insight card to dig further. The selected insight appears on
the left and new insight cards, based solely on the data in that single insight, display along the right.
4. Continue digging into your data, and when you find an interesting insight, pin it to your dashboard by
selecting Pin visual from the top-right corner.
Next steps
If you own a dataset, optimize it for Quick Insights
Learn about the types of Quick Insights available
More questions? Try the Power BI Community
 Optimize your data for Power BI Quick Insights
2/13/2019 • 2 minutes to read • Edit Online

Want to improve quick insights results? If you are a dataset owner, try these:
Hide or unhide columns in your dataset. Power BI quick insights doesn't search hidden columns. So hide
duplicate or unnecessary columns and unhide interesting columns.
Use a mix of data types such as names, times, dates, and numbers.
Avoid (or hide) columns with duplicate information. This takes valuable time away from searching for
meaningful patterns. For example, one column with state names spelled out and another column with state
name abbreviations.
Do you get an error message stating that your data isn't statistically significant? This can happen with models
that are very simple, or that don't have much data, or that don't have date or numeric columns.
Next steps
Power BI quick insights
More questions? Try the Power BI Community
 Create workspaces with your colleagues in Power BI
1/14/2019 • 5 minutes to read • Edit Online

In Power BI, you can create workspaces, places to collaborate with colleagues to create and refine collections of
dashboards and reports. Then you bundle the collection together into apps that you can distribute to your whole
organization or to specific people or groups.

When you create a workspace, you're creating an underlying, associated Office 365 group. All the workspace
administration is in Office 365. You can add colleagues to these workspaces as members or admins. In the
workspace, you can all collaborate on dashboards, reports, and other articles that you plan to publish to a wider
audience. Everyone you add to an app workspace needs a Power BI Pro license.
Did you know? Power BI is previewing a new workspace experience. Read Organize work in the new
workspaces (preview ) for details about the new workspaces.

Video: Apps and app workspaces

https://www.youtube.com/embed/Ey5pyrr7Lk8?showinfo=0

Create an app workspace based on an Office 365 group

When you create an app workspace, it’s built on an Office 365 group.
1. Start by creating the workspace. Select Workspaces > Create app workspace.
 This will be the place to put content that you and your colleagues collaborate on.
2. Give the workspace a name. If the corresponding Workspace ID isn't available, edit it to come up with a
unique ID.
This will be the name of the app, too.

3. You have a few options to set. If you choose Public, anyone in your organization can see what’s in the
workspace. Private, on the other hand, means only members of the workspace can see its contents.

You can't change the Public/Private setting after you've created the group.
4. You can also choose if members can edit or have view-only access.

Only add people to the app workspace so they can edit the content. If they're only going to view the
content, don't add them to the workspace. You can include them when you publish the app.
5. Add email addresses of people you want to have access to the workspace, and select Add. You can’t add
group aliases, just individuals.
6. Decide whether each person is a member or an admin.

Admins can edit the workspace itself, including adding other members. Members can edit the content in
the workspace, unless they have view -only access. Both admins and members can publish the app.
7. Select Save.
Power BI creates the workspace and opens it. It appears in the list of workspaces you’re a member of. Because
you’re an admin, you can select the ellipsis (…) to go back and make changes to it, adding new members or
changing their permissions.

When you first create it, you may need to wait an hour or so for the workspace to propagate to Office 365.
Add an image to your Office 365 app workspace (optional)
By default, Power BI creates a little colored circle for your app, with the app's initials. But maybe you want to
customize it with an image. To add an image, you need an Exchange Online license.
1. Select Workspaces, select the ellipsis (...) next to the name of the workspace, then Members.

The Office 365 Outlook account for the workspace opens in a new browser window.
2. When you hover over the colored circle in the upper left, it turns into a pencil icon. Select it.
3. Select the pencil icon again, and find the image you want to use.

4. Select Save.

The image replaces the colored circle in the Office 365 Outlook window.
 In a few minutes, it will appear in the app in Power BI, too.

Add content to your app workspace

After you've created an app workspace, it's time to add content to it. It's just like adding content to your My
Workspace, except the other people in the workspace can see and work on it, too. A big difference is that when
you get done, you can publish the content as an app. When you view content in the content list of an app
workspace, the app workspace name is listed as the owner.
Connect to third-party services in app workspaces
Apps are provided for all the third-party services Power BI supports, making it easy for you to get data from the
services you use, such as Microsoft Dynamics CRM, Salesforce, or Google Analytics. You can publish
organizational apps to give your users the data they need.
In the current workspaces, you can also connect using organizational content packs, and third-party content
packs such as Microsoft Dynamics CRM, Salesforce, or Google Analytics. Consider migrating your
organizational content packs to apps.

Distribute an app
When the content is ready, you choose which dashboards and reports you want to publish, and then you publish
it as an app. Your coworkers can get your apps in a few different ways. You can install them automatically in your
coworkers' Power BI accounts if your Power BI administrator gives you permission. Otherwise, they can find and
install your apps from Microsoft AppSource, or you can send them a direct link. They get updates automatically
and you can control how frequently the data refreshes. See Publish apps with dashboards and reports in Power
BI for details.

Power BI apps FAQ

How are apps different from organizational content packs?
Apps are the evolution of organizational content packs. If you have organizational content packs already, they'll
continue to work side by side with apps. Apps and content packs have a few major differences.
 After business users install a content pack, it loses its grouped identity: it's just a list of dashboards and
reports interspersed with other dashboards and reports. Apps, on the other hand, maintain their grouping
and identity even after installation. This grouping makes it easy for business users to continue to navigate to
them over time.
You can create multiple content packs from any workspace, but an app has a 1:1 relationship with its
workspace.
Over time we plan to deprecate organizational content packs, so we recommend you create apps from now
on.
With the new workspace experience preview, we're taking the first steps towards deprecating organizational
content packs. You can't consume or create them in preview workspaces.
See How are the new app workspaces different from existing app workspaces? to compare the two.

Next steps
Install and use apps in Power BI
Create the new workspaces (preview )
Questions? Try asking the Power BI Community
 Create the new workspaces (preview) in Power BI
1/14/2019 • 3 minutes to read • Edit Online

Power BI is introducing a new workspace experience as a preview. Workspaces are still places to collaborate
with colleagues to create collections of dashboards and reports, which you can bundle into apps and distribute
to your whole organization or to specific people or groups.

With the new workspaces preview, you can now:

Assign workspace roles to user groups: security groups, distribution lists, Office 365 groups, and
individuals.
Create a workspace in Power BI without creating an Office 365 group.
Use more granular workspaces roles for more flexible permissions management in a workspace.
For more background, see the new workspaces (preview ) article.

Create one of the new app workspaces

1. Start by creating the app workspace. Select Workspaces > Create app workspace.

2. In Preview improved workspaces, select Try now.

3. Give the workspace a name. If the name isn't available, edit it to come up with a unique ID.
The app will have the same name as the workspace.
4. Add an image, if you want. The file size has to be less than 45 KB.

5. Select Save.
Here in the Welcome screen for your new workspace, you can add data.
6. For example, select Samples > Customer Profitability Sample.
Now in the workspace content list, you see New workspaces preview. Because you're an admin, you
also see a new action, Access.

7. Select Access.
8. Add security groups, distribution lists, Office 365 groups, or individuals to these workspaces as
members, contributors, or admins. See Roles in the new workspaces for an explanation of the different
roles.
 9. Select Add > Close.
10. Power BI creates the workspace and opens it. You see it in the list of workspaces you’re a member of.
Because you’re an admin, you can select the ellipsis (…) to go back and make changes to workspace
settings, adding new members, or changing their permissions.

Add content to your app workspace

After you've created an app workspace of the new style, it's time to add content to it. Adding content is similar
in the new and old style workspaces, with one exception. While in either app workspace, you can upload or
connect to files, just as you would in your own My Workspace. In the new workspaces, you can't connect to
organizational content packs, or third-party content packs such as Microsoft Dynamics CRM, Salesforce, or
Google Analytics. In the current workspaces, you can connect to content packs.
When you view content in the content list of an app workspace, the app workspace name is listed as the owner.
Connecting to third-party services in new workspaces (preview)
In the new workspaces experience, we're making a change to focus on apps. Apps for third-party services make
it easy for users to get data from the services they use, such as Microsoft Dynamics CRM, Salesforce, or
Google Analytics. Organizational apps give your users the internal data they need. We plan to add capabilities
to organizational apps so users can customize the content they find within the apps. That capability will remove
the need for content packs.
With the new workspaces preview, you can't create or consume organizational content packs. Instead you can
use the apps provided to connect to third-party services, or ask your internal teams to provide apps for any
content packs you’re currently using.

Distribute an app
When the content is ready, you choose which dashboards and reports you want to publish, and then you
publish it as an app. You can create one app from each workspace. Your coworkers can get your app in a few
different ways. You can install it automatically in your coworkers' Power BI accounts if your Power BI
administrator gives you permission. Otherwise, they can find and install your app from Microsoft AppSource,
or you can send them a direct link. They get updates automatically and you can control how frequently the data
refreshes. See Publish apps with dashboards and reports in Power BI for details.

Convert old app workspaces to new app workspaces

During the preview period, you can't automatically convert your old app workspaces to new ones. You can
however create a new app workspace and publish your content to the new location.
When the new workspaces are generally available (GA), you can opt in to migrate the old ones automatically.
At some point after GA, you'll have to migrate them.

Next steps
Read about organizing work in the new workspaces (preview ) in Power BI
Create the current workspaces
Install and use apps in Power BI
Questions? Try asking the Power BI Community
 Publish apps with dashboards and reports in
Power BI
3/13/2019 • 6 minutes to read • Edit Online

In Power BI, you can publish apps with collections of related dashboards and reports. You create apps in app
workspaces, where you can collaborate on Power BI content with your colleagues. Then you can publish the
finished apps to large groups of people in your organization. Read more about creating app workspaces.

Your business users often need multiple Power BI dashboards and reports to run their business. With Power
BI apps, you can create collections of dashboards and reports and publish these apps to your whole
organization or to specific people or groups. For you as a report creator or admin, apps make it easier to
manage permissions on these collections.
Business users get your apps in a few different ways. If the Power BI administrator gives you permission, you
can install apps automatically in your coworkers' Power BI accounts. Otherwise, they can install your apps
from Microsoft AppSource, or you can send them a direct link. They can easily find and return to your
content because it’s all in one place. They can’t modify the contents of the app, but they can interact with it
either in the Power BI service, or one of the mobile apps -– filtering, highlighting, and sorting the data
themselves. They get updates automatically and you can control how frequently the data refreshes. Read
more about the app experience for business users.
Did you know? Power BI is previewing a new workspace experience. Read Create the new workspaces
(preview ) to see how workspaces will change in the future.

Apps and organizational content packs

Apps are the evolution of organizational content packs. Content packs aren't available in the new workspace
experiences preview. After the new workspace experience is generally available, you won't be able to use
content packs in newly created workspaces. If you haven't already, start migrating your content packs to
apps.

Video: Apps and app workspaces

https://www.youtube.com/embed/Ey5pyrr7Lk8?showinfo=0

Licenses for apps

Each member of an app workspace needs a Power BI Pro license. For app users, there are two options.
 Option 1: All business users need Power BI Pro licenses to view your app.
Option 2: If your app resides in a Power BI Premium capacity, free users in your organization can view
app content. Read What is Power BI Premium? for details.

Publish your app

When the dashboards and reports in your workspace are ready, you choose which dashboards and reports
you want to publish, then you publish them as an app. You can send a direct link to that wider audience, or
they can find your app from the Apps tab by going to Download and explore more apps from
AppSource.
1. In the workspace list view, decide which dashboards and reports you want to include in the app.

If you choose not to publish a report, you see a warning next to the report and its related dashboard.
You can still publish the app, but the related dashboard will be missing the tiles from that report.

2. Select the Publish app button in the upper right to start the process of sharing all the content in that
workspace.

3. On Details, fill in the description to help people find the app. You can set a background color to
personalize it.
4. On Content, you see the content that’s going to be published as part of the app – everything that
you've selected in that workspace. You can also set the app landing page – the dashboard or report
people will see first when they go to your app. You can choose None. Then they’ll land on a list of all
the content in the app.

5. On Access, decide who has access to the app: either everyone in your organization, specific people,
Active Directory security groups. If you have permissions, you can decide to install the app
automatically for the recipients. A Power BI admin can enable this setting in the Power BI Admin
Portal. Read more automatically installing an app.

6. When you select Finish, you see a message confirming it’s ready to publish. In the success dialog box,
you can copy the URL that’s a direct link to this app and send it to the people you’ve shared it with.
Read more about the app experience for business users.

Change your published app

After you publish your app, you may want to change or update it. It’s easy to update it if you’re an admin or
member of the app workspace, or a contributor in a new app workspace.
1. Open the app workspace that corresponds to the app.

2. Open the dashboard or the report. You see that you can make any changes you want.
The app workspace is your staging area, so your changes aren't live in the app until you publish again.
This lets you make changes without affecting the published apps.
3. Go back to the app workspace list of contents and select Update app.

4. Update Details, Content, and Access, if you need to, then select Update app.
The people you’ve published the app to automatically see the updated version of the app.

Automatically install apps for end users

Apps deliver data that your end users need to do their jobs. If an admin gives you permissions, you can
automatically install apps for end users, making it easier to distribute the right apps to the right people or
groups. Your app will appear automatically in your end users' Apps content list rather than them having to
find it from Microsoft AppSource, or following an installation link. This makes it easier for you to roll out
standard Power BI content to your users.
How to install an app automatically for end users
Once the admin has assigned you permissions, you have a new option to install the app automatically.
When you check the box and select Finish (or Update app, for existing apps), the app is pushed to all users
or groups defined in the Permissions section of the app on the Access tab.

How users get the apps that were pushed to them

After you push an app, it shows up in the Apps list automatically. You can curate the apps that specific users
or job roles in your organization need to have at their fingertips.
Considerations for automatically installing apps
Here are things to keep in mind when pushing apps to end users:
Installing an app automatically to users can take time. Most apps will install immediately for users, but
pushing apps can take time. It depends on the number of items in the app and the number of people
given access. We recommend pushing apps during off hours with plenty of time before users need
them. Verify with several users before sending broad communication about the apps' availability.
Refresh your browser. Before seeing the pushed app in the Apps list, the user may need to refresh, or
close and reopen their browser.
If the user doesn’t immediately see the app in the Apps list, they should refresh or close and reopen
their browser.
Try not to overwhelm users. Be careful not to push too may apps so your users perceive the pre-
installed apps are useful to them. It’s best to control who can push apps to end users to coordinate
timing. You can establish a point of contact for getting apps in your organization pushed to end users.
Guest users who have not accepted an invite won't get apps automatically installed for them.

Unpublish an app
Any member of an app workspace can unpublish the app.

NOTE
When you unpublish an app, app users lose their customizations. This means that any personal bookmarks,
comments, or subscriptions associated with content in the app are lost. Only unpublish an app if you need to remove
it.

In an app workspace, select the ellipsis (...) in the upper-right corner > Unpublish app.

This action uninstalls the app for everyone you've published it to, and they no longer have access to it. It
doesn't delete the app workspace or its contents.

Next steps
Create an app workspace
Install and use apps in Power BI
Power BI apps for external services
Power BI Admin Portal
Questions? Try asking the Power BI Community
 Manage data storage in Power BI workspaces
1/14/2019 • 3 minutes to read • Edit Online

Learn how you can manage data storage in your individual or app workspace to make sure you can continue to
publish reports and datasets.
Users and app workspaces have their own data capacities:
All users have a maximum 10 GB of data storage.
Users with a Power BI Pro license can create app workspaces, with a maximum 10 GB of data storage each.
An app workspace in a Premium capacity doesn't count toward the storage of a Power BI Pro user.
At the tenant level, total usage can’t exceed 10 GB per Pro user across all Pro users and app workspaces in the
tenant.
Read about other features of the Power BI pricing model.
Included in your data storage are your own datasets and Excel reports, and those items that someone has shared
with you. Datasets are any of the data sources you’ve uploaded or connected to. These data sources include Power
BI Desktop files and Excel workbooks you’re using. The following are also included in your data capacity.
Excel ranges pinned to dashboard.
Reporting Services on-premises visualizations pinned to a Power BI dashboard.
Uploaded images.
The size of a dashboard that you share varies depending on what is pinned to it. For example, if you pin items from
two reports that are part of two different datasets, the size includes both datasets.

Manage items you own

See how much data storage you’re using in your Power BI account, and manage your account.
1. To manage your own storage, go to My Workspace on the left navigation pane.
2. Select the gear icon in the upper-right corner > Manage personal storage.
The top bar shows how much of your storage limit you’ve used.

The datasets and reports are separated onto two tabs:

Owned by Me: You’ve uploaded these reports and datasets to your Power BI account, including service
datasets such as Salesforce and Dynamics CRM.
Owned by Others: Others have shared these reports and datasets with you.

3. To delete a dataset or report, select the trash can icon .

Keep in mind that you or someone else may have reports and dashboards based on a dataset. If you delete the
dataset, those reports and dashboards won’t work anymore.

Manage your app workspace

1. Select the arrow next to Workspaces > select the name of the app workspace.

2. Select the gear icon in the upper-right corner > Manage group storage.
The top bar shows how much of the group’s storage limit is used.
 The datasets and reports are separated onto two tabs:
Owned by Us: You or someone else has uploaded these reports and datasets to the group’s Power BI
account, including service datasets such as Salesforce and Dynamics CRM. Owned by Others: Others have
shared these reports and datasets with your group.

3. To delete a dataset or report, select the trash can icon .

NOTE
Any member, with edit permissions, of an app workspace has permissions to delete datasets and reports from the
app workspace.

Keep in mind that you or someone else in the group may have reports and dashboards based on a dataset. If you
delete the dataset, those reports and dashboards won’t work anymore.

Dataset limits
There is a 1 GB limit, per dataset, that is imported into Power BI. If you have chosen to keep the Excel experience,
instead of importing the data, the limit is 250 MB for the dataset.

What happens when you reach a limit

When you reach the data capacity limit of what you can do, you see prompts within the service.

When you select the gear icon , you see a red bar indicating you are over your data capacity limit.

This limit also is indicated within Manage personal storage.

When you try to perform an action that will reach one of the limits, you see a message you are over the limit. You
can manage your storage to reduce your storage amount and get past the limit.

More questions? Try asking the Power BI Community

 Connect to files stored in OneDrive for your Power BI
app workspace
1/11/2019 • 2 minutes to read • Edit Online

After you've created an app workspace in Power BI, you can store your Excel, CSV, and Power BI Desktop files on
the OneDrive for Business for your Power BI app workspace. You can continue updating the files you store in
OneDrive, and those updates are automatically reflected in the Power BI reports and dashboards based on the files.

NOTE
The new workspace experience preview will change the relationship between Power BI workspaces and Office 365 groups. You
won't automatically be creating an Office 365 group every time you create one of the new workspaces. Read about creating
the new workspaces (preview)

Adding files to your app workspace is a two-step process:

1. First you upload files to the OneDrive for Business for your app workspace.
2. Then you connect to those files from Power BI.

NOTE
App workspaces are only available with Power BI Pro.

1 Upload files to the OneDrive for Business for your app workspace
1. In the Power BI service, select the arrow next to Workspaces > select the ellipsis ( … ) next to your workspace
name.

2. Select Files to open the OneDrive for Business for your app workspace on Office 365.
 NOTE
If you don't see Files on the app workspace menu, select Members to open the OneDrive for Business for your app
workspace. There, select Files. Office 365 sets up a OneDrive storage location for your app's group workspace files.
This process may take some time.

3. Here, you can upload your files to the OneDrive for Business for your app workspace. Select Upload, and
navigate to your files.

2 Import Excel files as datasets or as Excel Online workbooks

Now that your files are in the OneDrive for Business for your app workspace, you have a choice. You can:
Import the data from the Excel workbook as a dataset, and use the data to build reports and dashboards you
can view in a web browser and on mobile devices.
Or connect to a whole Excel workbook in Power BI and display it exactly as it appears in Excel Online.
Import or connect to the files in your app workspace
1. In Power BI, switch to the app workspace, so the app workspace name is in the top-left corner.
2. Select Get Data at the bottom of the left navigation pane.

3. In the Files box, select Get.

4. Select OneDrive - Your App Workspace Name.

5. Select the file you want > Connect.
This is the point where you decide whether to import the data from the Excel workbook, or connect to the
whole Excel workbooks.
6. Select Import or Connect.

7. If you select Import, then the workbook appears on the Datasets tab.

If you select Connect, then the workbook is on the Workbooks tab.

Next steps
Create apps and app workspaces in Power BI
Import data from Excel workbooks
Connect to whole Excel workbooks
More questions? Try the Power BI Community
Feedback? Visit Power BI Ideas
 Collaborate in your Power BI app workspace
3/18/2019 • 2 minutes to read • Edit Online

Power BI app workspaces are great places to collaborate with your colleagues on dashboards, reports, and
datasets to create apps. Collaboration doesn’t end with workspaces in Power BI. Office 365 offers other group
services such as sharing files on OneDrive for Business, conversations in Exchange, shared calendar and tasks, and
so on. Read more about groups in Office 365.

NOTE
The new workspace experience preview will change the relationship between Power BI workspaces and Office 365 groups.
You won't automatically be creating an Office 365 group every time you create one of the new workspaces. Read about
creating the new workspaces (preview)

App workspaces are only available with a Power BI Pro license.

Collaborate on Power BI Desktop files in your app workspace

After you create a Power BI Desktop file, if you publish it to your Power BI app workspace, then everyone in your
workspace can collaborate on it.
1. In Power BI Desktop, select Publish on the Home ribbon, then in the Select a destination box, select
your app workspace.

2. In the Power BI service, select the arrow next to Workspaces > select your app workspace.
3. Select the Reports tab, then select your report.

From here, it's like any other report in Power BI. You and others in your app workspace can modify the
report and save tiles to a dashboard of your choosing.

Collaborate in Office 365

Collaborating in Office 365 starts from the app workspace in Power BI.
1. In the Power BI service, select the arrow next to Workspaces > select the ellipsis ( … ) next to your workspace
name.
2. From this menu, you can collaborate with your group in a few ways:
Have a group conversation in Office 365.
Schedule an event on the app's group workspace calendar.
The first time you go to your app's group workspace in Office 365, it may take some time. Give it 15 to 30
minutes, then refresh your browser.

Have a group conversation in Office 365

1. Select the ellipsis (…) next to your app workspace name > Conversations.

The email and conversation site for your app's group workspace opens in Outlook for Office 365.
2. Read more about group conversations in Outlook for Office 365.

Schedule an event on the app's group workspace calendar

1. Select the ellipsis (… ) next to your app workspace name > Calendar.

This opens the calendar for your app's group workspace in Outlook for Office 365.

2. Read more about group calendars in Outlook in Office 365.

Manage an app workspace
If you’re owner or admin for an app workspace, you can also add or remove workspace members. Read more
about managing your Power BI app workspace.

Next steps
Create apps and app workspaces in Power BI
More questions? Try the Power BI Community
Feedback? Visit Power BI Ideas
 Manage your app workspace in Power BI and Office
365
1/14/2019 • 2 minutes to read • Edit Online

As creator or admin of an app workspace in Power BI or in Office 365, you manage some aspects of the
workspace in Power BI. Other aspects you manage in Office 365.

NOTE
The new workspace experience preview will change the relationship between Power BI workspaces and Office 365 groups.
You won't automatically be creating an Office 365 group every time you create one of the new workspaces. Read about
creating the new workspaces (preview)

In Power BI you can:

Add or remove app workspace members, including making a workspace member an admin.
Edit the app workspace name.
Delete the app workspace.
In Office 365 you can:
Add or remove your app workspace's group members, including making a member an admin.
Edit the group name, image, description, and other settings.
See the group email address.
Delete the group.
You need a Power BI Pro license to be an admin or member of an app workspace. Your app users need a Power BI
Pro license, too, unless your app workspace is in a Power BI Premium capacity. Read What is Power BI Premium?
for details.

Edit your app workspace in Power BI

1. In the Power BI service, select the arrow next to Workspaces > select the ellipsis (… ) next to your
workspace name > Edit workspace.
 NOTE
You only see Edit workspace if you’re an app workspace admin.

2. Here you can rename, add or remove members, or delete the app workspace.

3. Select Save or Cancel.

Edit Power BI app workspace properties in Office 365

1. In the Power BI service, select the arrow next to Workspaces > select the ellipsis (… ) next to your
workspace name > Members.
 This opens the Outlook for Office 365 group view of your app workspace.
You may need to sign into your corporate account.
2. Tap the ellipsis (… ) next to a member's name to make the member an admin or delete the member from the
app workspace.

Add an image and set other workspace properties in the Office 365
group
When you distribute your app from the app workspace, the image you add here will be the image for your app.
See the Add an image to your app section of the article Create the new workspaces.
1. In the Outlook for Office 365 view of your app workspace, select the group image to edit group workspace
properties.

2. You can edit the name, description, and language, add an image, and set other properties here.
3. Select Save or Discard.

Next steps
Publish apps with dashboards and reports in Power BI
More questions? Try the Power BI Community
 Share your Power BI dashboards and reports with
coworkers and others
3/18/2019 • 7 minutes to read • Edit Online

Sharing is a good way to give a few people access to your dashboards and reports. Power BI also offers several
other ways to collaborate and distribute dashboards and reports.

With sharing, whether you share content inside or outside your organization, you need a Power BI Pro license.
Your recipients also need Power BI Pro licenses, or the content needs to be in a Premium capacity.
You can share dashboards and reports from most places in the Power BI service: your Favorites, Recent, Shared
with me (if the owner allows it), My Workspace, or other workspaces. When you share a dashboard or report,
those you share it with can view it and interact with it, but can't edit it. They see the same data that you see in the
dashboard or report, unless row -level security (RLS ) is applied. The coworkers you share with can also share
with their coworkers, if you allow them to. The people outside your organization can view and interact with the
dashboard or report too, but can't share it.
You can also share a dashboard from any of the Power BI mobile apps. You can share dashboards from the
Power BI service and the Power BI mobile apps, but not from Power BI Desktop.

Video: Share a dashboard

Watch Amanda share her dashboard with colleagues inside and outside her company. Then follow the step-by-
step instructions below the video to try it out yourself.
https://www.youtube.com/embed/0tUwn8DHo3s?list=PL1N57mwBHtN0JFoKSR0n-tBkUJHeMP2cP

Share a dashboard or report

1. In a list of dashboards or reports, or in an open dashboard or report, select Share .
2. In the top box, enter the full email addresses for individuals, distribution groups, or security groups. You
can't share with dynamic distribution lists.
You can share with people whose addresses are outside your organization, but you'll see a warning.
 NOTE
The input box supports at most 100 users or groups. You can share multiple times or share with a user group if
you need to share with large numbers of users.

3. Add a message if you want. It's optional.

4. To let your coworkers share your content with others, check Allow recipients to share your
dashboard/report.
Allowing others to share is called resharing. If you let them, they can reshare from the Power BI service
and the mobile apps, or forward the email invitation to others in your organization. The invitation expires
after one month. People outside your organization can't reshare. As the owner of the content, you can turn
off resharing, or revoke resharing on an individual basis. See Stop sharing or stop others from sharing,
below.
5. Select Share.

Power BI sends an email invitation to the individuals but not to groups, with a link to the shared content.
 You see a Success notification.
When recipients in your organization click the link, Power BI adds the dashboard or report to their
Shared with me list page. They can select your name to see all the content you've shared with them.

When recipients outside your organization click the link, they see the dashboard or report, but not in the
usual Power BI portal. For more information, see Share a dashboard or report with people outside your
organization below.

Who has access to a dashboard or report you shared?

Sometimes you need to see the people you've shared with, and see who they've shared it with.

1. In the list of dashboards and report, or in the dashboard or report itself, select Share .
2. In the Share dashboard/report dialog box, select Access.

People outside your organization are listed as Guest.

Stop sharing or stop others from sharing

Only the dashboard or report owner can turn resharing on and off.
If you haven't sent the sharing invitation yet
Clear the Allow recipients to share your dashboard/report check box at the bottom of the invitation
before you send it.
If you've already shared the dashboard or report
1. In the list of dashboards and reports, or in the dashboard or report itself, select Share .
2. In the Share dashboard/report dialog box, select Access.

3. Select the ellipsis (...) next to Read and reshare and select:

Read to keep that person from sharing with anyone else.

Remove access to keep that person from seeing the shared content at all.
4. In the Remove access dialog box, decide if you want to remove access to related content, too, such as
reports and datasets. If you remove items with a warning icon , it's best to remove related content
because it won't display properly.
Share a dashboard or report with people outside your organization
When you share with people outside your organization, they get an email with a link to the shared dashboard or
report, and they have to sign in to Power BI to see it. If they don't have a Power BI Pro license, they can sign up
for a license after clicking the link.
After they sign in, they see the shared dashboard or report in its own browser window without the left
navigation pane, not in their usual Power BI portal. They have to bookmark the link to access this dashboard or
report in the future.
They can't edit any content in this dashboard or report. They can interact with the charts and change filters or
slicers in the report, but can't save their changes.
Only your direct recipients can see the shared dashboard or report. For example, if you sent the email to
[email protected], only Vicki can see the dashboard. No-one else can see that dashboard, even if they have the
link, and Vicki has to use the same email address to access that dashboard. If she signs up with any other email
address, she won't have access to the dashboard either.
People outside your organization can't see any data at all if role- or row -level security is implemented on on-
premises Analysis Services tabular models.
If you send a link from a Power BI mobile app to people outside your organization, when they click the link the
dashboard opens in a browser, not in the Power BI mobile app.
If the guest users is enabled using the Allow external guest users to edit and manage content in the organization
the default consumption only experience will not apply to them. Learn more

Limitations and considerations

Things to keep in mind about sharing dashboards and reports:
 In general, you and your colleagues see the same data in the dashboard or report. Thus, if you have
permissions to see more data than they do, they'll be able to see all your data in the dashboard or report.
However, if row -level security (RLS ) is applied to the dataset underlying a dashboard or report, then the
credentials of every person are used to determine which data they can access.
Everyone you share your dashboard with can see it and interact with the related reports in Reading View.
They can't create reports or save changes to existing reports.
No one can see or download the dataset, but they can access the dataset directly using the Analyze in Excel
feature. An admin can restrict people’s ability to use Analyze in Excel by restricting the ability for everyone in
a group. However, the restriction is for everyone in that group for every workspace the group belongs to.
Everyone can manually refresh the data.
If you use Office 365 for email, you can share with members of a distribution group by entering the email
address associated with the distribution group.
Coworkers who have the same email domain as you, and coworkers whose domain is different but registered
within the same tenant, can share the dashboard with others. For example, say the domains contoso.com and
contoso2.com are registered in the same tenant. If your email address is [email protected], then both
[email protected] and [email protected] can share, as long as you gave them permission to share.
If your coworkers already have access to a specific dashboard or report, you can send a direct link just by
copying the URL when you're on the dashboard or report. For example:
https://powerbi.com/dashboards/g12466b5-a452-4e55-8634-xxxxxxxxxxxx
Likewise if your coworkers already have access to a specific dashboard, you can send a direct link to the
underlying report.
You can share with at most 100 users or groups in a single share action. However, you can give more than
500 users access to an item. To do this, either can share multiple times specifying the users individually, or
share with a user group that contains all the users.

Troubleshoot sharing
My dashboard recipients see a lock icon in a tile or a "Permission required" message
The people you share with may see a locked tile in a dashboard, or a "Permission required" message when they
try to view a report.

If so, you need to grant them permission to the underlying dataset. Here's how.
1. Go to the Datasets tab in your content list.
2. Select the ellipsis (...) next to the dataset > Manage permissions.
3. Select Add user.

4. Enter the full email addresses for individuals, distribution groups, or security groups. You can't share with
dynamic distribution lists.
5. Select Add.
I can't share a dashboard or report
To share a dashboard or report, you need permission to reshare the underlying content -- any related reports
and datasets. If you see a message saying you can't share, ask the report author to give you re-share permission
for those reports and datasets.

Next steps
Have feedback? Go to the Power BI Community site with your suggestions.
How should I collaborate on and share dashboards and reports?
Share a filtered Power BI report
Questions? Try the Power BI Community.
 Share a filtered Power BI report with your coworkers
1/14/2019 • 2 minutes to read • Edit Online

Sharing is a good way to give a few people access to your dashboards and reports. Power BI also offers several
other ways to collaborate and distribute your reports.
With sharing, you and your recipients need a Power BI Pro license, or the content needs to be in a Premium
capacity.
You can share a report with coworkers in the same email domain as you, from most places in the Power BI
service: your Favorites, Recent, Shared with me (if the owner allows it), My Workspace, or other workspaces.
When you share a report, those coworkers you share it with can view it and interact with it, but can't edit it. They
see the same data that you see in the report, unless row -level security (RLS ) is applied.
What if you want to share a filtered version of a report? Maybe a report that only shows data for a specific city or
salesperson or year. Try creating a custom URL. The report will be filtered when recipients first open it. They can
remove the filter by modifying the URL.

Filter and share a report

1. Open the report in Editing view, apply the filter, and save the report.
In this example, we're filtering the Retail Analysis sample to show only values where Territory equals NC.

2. Add the following to the end of the report page URL:

?filter=tablename/fieldname eq value
The field must be of type string. The tablename or fieldname values can't contain spaces.
In our example, the name of the table is Store, the name of the field is Territory, and the value we want to
filter on is NC:
?filter=Store/Territory eq 'NC'

Your browser adds special characters to represent slashes, spaces, and apostrophes, so you end up with:
app.powerbi.com/groups/me/reports/010ae9ad-a9ab-4904-a7a1-xxxxxxxxxxxx/ReportSection2?
 filter=Store%252FTerritory%20eq%20%27NC%27
3. Share the report, but clear the Send email notification to recipients check box.

4. Send the link with the filter that you created earlier.

Next steps
Have feedback? Go to the Power BI Community site with your suggestions.
How should I collaborate on and share dashboards and reports?
Share a dashboard
More questions? Try the Power BI Community.
 Subscribe yourself and others to a report or
dashboard in the Power BI service
3/20/2019 • 7 minutes to read • Edit Online

You can subscribe yourself and your colleagues to the report pages and dashboards that matter most to you, and
Power BI emails a snapshot to your inbox. You tell Power BI how often you want to receive the emails: daily,
weekly, or once a day after the initial data refresh. If you choose daily or weekly, you can choose the time(s) you'd
like to have the subscription run. In all, you can set up to 24 different subscriptions per day, for every report page
and dashboard.

You can only create subscriptions in the Power BI service. You receive an email with a snapshot of the report page
or dashboard, with a link to open the report or dashboard. On mobile devices with Power BI apps installed,
selecting this link launches the Power BI app, instead of opening the report or dashboard in the Power BI web site.

Requirements
Creating a subscription is a Power BI Pro feature.
You don't need edit permissions to the content (dashboard or report) to create a subscription for yourself, but
you must have edit permissions to create one for someone else.
As of January 2019, you no longer must have dataset refresh set up to run a subscription. It runs independent
of any scheduled refreshes you have set up.

Subscribe to a dashboard or a report page

Whether you're subscribing to a dashboard or report, the process is similar. The same button allows you to
subscribe to Power BI service dashboards and reports.
 .
1. Open the dashboard or report.
2. From the top menu bar, select Subscribe or select the envelope icon .

3. Use the yellow slider to turn the subscription on and off. Setting the slider to Off doesn't delete the
subscription. To delete the subscription, select the trashcan icon.
4. Your email is already in the Subscribe box. You can add other email addresses to the subscription as well,
but only in the same domain. If the report or dashboard is hosted in Premium capacity, you can subscribe
other individual email addresses and group aliases. If the report or dashboard isn't hosted in Premium
capacity, you can subscribe other individuals, but they too must have Power BI Pro licenses. See
Considerations and troubleshooting below for details.
5. Fill in the email Subject and Message details.
6. Select a Frequency for your subscription: Daily, Weekly, or After Data Refresh (Daily). To receive the
subscription email only on certain days, select Weekly and select the days you'd like to receive it. For
example, if you'd like to receive the subscription email only on weekdays, select Weekly and uncheck the
boxes for Sat and Sun.
7. If you choose Daily or Weekly, you can also choose a Scheduled Time for the subscription. You have it
run on the hour, or at 15, 30, or 45 minutes past. Select morning (AM ) or afternoon/evening (PM ). You can
also specify the time zone.
8. By default, the start date for your subscription is the date you create it. You have the option to select an end
date. If you don't set an end date, the end date is automatically one year after the start date. You can change
it to any date in the future (up to the year 9999) at any time before the subscription ends. When a
subscription reaches an end date, it stops until you re-enable it. You'll receive notification(s) before the
scheduled end date to ask if you'd like to extend it.
In the screenshot below, notice that when you subscribe to a report, you're actually subscribing to a report
page. To subscribe to more than one page in a report, select Add another subscription and select a
different page.
9. Select Save and close. Those subscribed receive an email and snapshot of the dashboard or report page
for the frequency and time you selected. In all, you may create up to 24 subscriptions per report or
dashboard, and can provide unique recipients, times, and frequencies for each subscription. All
subscriptions set to After Data Refresh for your dashboard or report will still only send an email after the
first scheduled refresh.

TIP
Want to send the email from a subscription right away or on-demand at any time? Select Run Now for the
subscriptions for the dashboard or report you want to send. You'll see a notification that an e-mail is on its way to
everyone for that particular subscription. You may do this as often as you'd like. It doesn't count against your limit of
24 scheduled subscription runs per day per report or dashboard. Note this does NOT trigger a data refresh of the
underlying dataset.

Email languages
The email and snapshot use the language set in Power BI settings (see Supported languages and countries/regions
for Power BI). If no language is defined, Power BI uses the language according to the locale setting in your current
browser. To see or set your language preference, select the cog icon > Settings > General > Language.

Manage your subscriptions

Only the person who created the subscription can manage it. There are two paths to the screen for managing your
subscriptions. The first is by selecting Manage all subscriptions from the Subscribe to emails dialog (see
screenshots below step 4 above). The second is by selecting the Power BI cog icon from the top menubar and
choosing Settings.

The particular subscriptions displayed depend on which workspace is currently active. To see all of your
subscriptions at once for all workspaces, be sure that My Workspace is active. For help understanding
workspaces, see Workspaces in Power BI.

A subscription ends if the Pro license expires, the owner deletes the dashboard or report, or the user account used
to create the subscription is deleted.

Considerations and troubleshooting

 Dashboards with over 25 pinned tiles, or 4 pinned live report pages, may not render fully in subscription e-
mails sent to users. Subscriptions to dashboards over these number of tiles will not be blocked, however, they
will be considered unsupported if you encounter issues and should be modified accordingly to fall within a
supported range.
When setting up your e-mail subscriptions, please keep in mind there is a delay between when the subscription
job is started, and the exact time the e-mail is sent. To minimize the delay between the between when the job
starts and the subsequent e-mail is sent, it is recommended you set up a different time for your scheduled data
refresh than when your e-mail subscription is scheduled to run.
For dashboard email subscriptions, if any tiles have row level security (RLS ) applied, those tiles don't display.
For report email subscriptions, if the dataset uses RLS, you can't be able to create a subscription.
Report page subscriptions are tied to the name of the report page. If you subscribe to a report page and then
rename it, you have to re-create your subscription.
Your organization may configure certain settings in Azure Active Directory that limit the ability to use email
subscriptions in Power BI. These limitations include, but aren't limited to, having multi-factor authentication or
IP range restrictions when accessing resources.
Currently, email subscriptions for reports/dashboards using live connection datasets aren't supported when
subscribing users other than yourself.
Email subscriptions don't support most custom visuals. The one exception is those custom visuals that have
been certified.
Email subscriptions don't support R -powered custom visuals at this time.
If any dashboard tiles have row level security (RLS ) applied, those tiles don't display.
You can't subscribe other users to a report that has row level security (RLS ) applied.
Email subscriptions are sent with the report's default filter and slicer states. Any changes to the defaults that
you make after subscribing don't show up in the email.
For dashboards subscriptions specifically, certain types of tiles aren't yet supported. These include: streaming
tiles, video tiles, custom web content tiles.
If you share a dashboard with a colleague outside of your tenant, you can't also create a subscription for that
colleague. So if you are [email protected], you can share with [email protected], but you can't yet subscribe
[email protected] and they can't subscribe to shared content.
Power BI automatically pauses refresh on datasets associated with dashboards and reports that haven't been
visited in more than two months. However, if you add a subscription to a dashboard or report, it doesn't pause
even if it goes unvisited.
If you aren't receiving the subscription emails, ensure that your User Principal Name (UPN ) can receive emails.
The Power BI team is working on relaxing this requirement, so stay tuned.
If your dashboard or report is in Premium capacity, you can use group email aliases for subscriptions, instead
of subscribing colleagues one email address at a time. The aliases are based on the current active directory.

Next steps
More questions? Try asking the Power BI Community
Read the blog post
 Embed with report web part in SharePoint Online
3/25/2019 • 5 minutes to read • Edit Online

With Power BI's new report web part for SharePoint Online, you can easily embed interactive Power BI reports in
SharePoint Online pages.
When using the new Embed in SharePoint Online option, the embedded reports are fully secure so you can
easily create secure internal portals.

Requirements
There are a few requirements in order for Embed in SharePoint Online reports to work.
You need a Power BI Pro license or a Power BI Premium capacity (EM or P SKU ) with a Power BI license.
The Power BI web part for SharePoint Online requires Modern Pages.

Embed your report

In order to embed your report into SharePoint Online, you first need to get the URL for the report and then use
that URL with the new Power BI web part within SharePoint Online.
Get a URL to your report
1. View the report within the Power BI service.
2. Select the File menu item.
3. Select Embed in SharePoint Online.

4. Copy URL from dialog.

Add the Power BI report to a SharePoint Online page
1. Open the desired page in SharePoint Online and select Edit.

Or, create a new modern site page by selecting + New within SharePoint Online.

2. Select + and select the Power BI web part.

3. Select Add report.

4. Paste the report URL into the property pane. This report URL is the URL you copied from the steps above.
The report loads automatically.

5. Select Publish to make the change visible to your SharePoint Online users.
Grant access to reports
Embedding a report in SharePoint Online does not automatically give users permission to view the report. The
permissions to view the report are set within the Power BI service.

IMPORTANT
Make sure to review who can see the report within the Power BI service and grant access to those not listed.

There are two ways to provide access to the report within the Power BI service. If you are using an Office 365
Group to build your SharePoint Online team site, you list the user as a member of the app workspace within
the Power BI service and the SharePoint page. For more information, see how to manage an app workspace.
Alternatively, you can share a report directly with users by embedding the report within an app. There are a few
steps to follow for embedding a report within an app.
1. The author of the app is a Pro user.
2. The author creates a report in an app workspace. To share with Power BI free users, the app workspace
needs to be set as a Premium workspace.
3. The author publishes the app then installs it. The author needs to make sure to install the app to have
access to the report URL that is used to embed in SharePoint Online.
4. Now all end users need to install the app too. However, you can set the app to be preinstalled for end users
by using the Install app automatically feature, which can be enabled in the Power BI admin portal.
 5. The author opens the app and goes to the report.
6. The author copies the embed report URL from the report installed by the app. Do Not use the original
report URL from the app workspace.
7. Create a new team site in SharePoint Online.
8. Add the report URL copied from step 6 to the Power BI web part.
9. Add all end users and/or groups who are going to consume the data on the SharePoint Online page and in
the Power BI app you created.

NOTE
Users or groups need access to both the SharePoint Online page and the report in the Power BI app to see
the report on the SharePoint page.

10. Now the end user can go to the team site in SharePoint Online and view the reports on the page.

Multi-factor authentication
If your Power BI environment requires you to sign in using multi-factor authentication, you may be asked to sign
in with a security device to verify your identity. This occurs if you did not sign in to SharePoint Online using multi-
factor authentication but your Power BI environment requires an account validated by a security device.

NOTE
Multi-factor authentication is not yet supported with Azure Active Directory 2.0. Users receive a message saying error. If the
user signs in again to SharePoint Online using their security device, they may be able to view the report.

Web part settings

Below is a description of the settings that can be adjusted for the Power BI web part for SharePoint Online.
 PROPERTY DESCRIPTION

Page name Sets the default page that is shown by the web part. Select a
value from the drop-down. If no pages are displayed, either
your report has one page, or the URL you pasted contains a
page name. Remove the report section from the URL to select
a specific page.

Display Option to adjust how the report is fit within the SharePoint
Online page.

Show Navigation Pane Shows or hides the page navigation pane.

Show Filter Pane Shows or hides the filter pane.

Reports that do not load

Your report may not load within the Power BI web part and may show the following message.
This content isn't available.
There are two common reasons for this message.
1. You do not have access to the report.
2. The report was deleted.
Contact the owner of the SharePoint Online page to help you resolve the issue.

Licensing
Users viewing a report in SharePoint need either a Power BI Pro license or the content needs to be in a
workspace that's in a Power BI Premium capacity (EM or P SKU ).

Known issues and limitations

Error: "An error occurred, please try logging out and back in and then revisiting this page. Correlation ID:
undefined, http response status: 400, server error code 10001, message: Missing refresh token"
If you receive this error, try one of the troubleshooting steps below.
1. Sign out of SharePoint and sign back in. Be sure to close all browser windows before signing back in.
2. If your user account requires multi-factor authentication (MFA), ensure you sign in to SharePoint
using your multi-factor authentication device (phone app, smart card, etc.)
3. Azure B2B Guest users accounts are not supported. Users see the Power BI logo that shows the part
is loading, but it doesn't show the report.
Power BI does not support the same localized languages that SharePoint Online does. As a result, you may
not see proper localization within the embedded report.
You may encounter issues if using Internet Explorer 10. You can look at the browsers support for Power BI
and for Office 365.
The Power BI web part is not available for national clouds.
The classic SharePoint Server is not supported with this web part.
URL filters are not supported with the SPO web part.

Next steps
Allow or prevent creation of modern site pages by end users
Create and distribute an app in Power BI
 Share a dashboard with colleagues and others
What is Power BI Premium?
Embed report in a secure portal or website
More questions? Try asking the Power BI Community
 Embed a report in a secure portal or website
1/14/2019 • 4 minutes to read • Edit Online

The new secure Embed option for reports in Power BI enables users to easily and securely embed reports in
internal web portals, whether cloud-based or hosted on-premises, such as SharePoint 2019. Reports
embedded in this way respect all item permissions and data security through row -level security (RLS ). The feature
is designed to allow no-code embedding into any portal that accepts a URL or iFrame to embed.
The Embed option also supports URL Filters and URL settings. The Embed option allows you to integrate with
portals using a low -code approach that requires basic HTML and JavaScript knowledge.

How to Embed Power BI reports into portals

1. The new Embed option is available on the File menu for reports in the Power BI service.

2. Select the Embed option to open a dialog that provides a link and an iFrame that is used to embed the
report securely.
3. After you embed your URL in your web portal, or if you open the URL directly, the user is authenticated
before given access to the report. Below, the user has not signed-in to Power BI in the browser session.
When they press Sign-In, a new browser window or tab may need to open. Check for pop-up blockers if
you don't get prompted to sign in.

4. After the user has signed in, the report opens, showing the data and allowing users to navigate between
pages and to set filters. The report is shown only to users who have permission to view the report in Power
BI. All row -level security (RLS ) rules are also applied. Lastly, the user needs to be correctly licensed – either
they need a Power BI Pro license, or the report must be in a workspace that is in a Power BI Premium
capacity. The user needs to sign in each time they open a new browser window, but after they’ve signed in
once other reports load automatically.
5. When using the iFrame option, it's best to edit the HTML provided to specify the desired height and width
to fit into your portal’s web page.

Granting access to reports

The Embed option doesn't automatically permit users to view the report. The permissions to view the report are
set within the Power BI service.
To provide access to the report within the Power BI service, you can share the report with the users who require
access to the embedded report. If you're using an Office 365 Group, you can list the user as a member of the app
workspace within the Power BI service. For more information, see how to manage an app workspace.

Licensing
Users viewing the embedded report need either a Power BI Pro license or the content needs to be in a workspace
that's in a Power BI Premium capacity (EM or P SKU ).

Customize your embed experience using URL settings

The embed URL supports several input settings that help you customize your user experience. If you’re using the
iFrame provided, make sure you update the URL in the iFrame’s src settings.

PROPERTY DESCRIPTION
 PROPERTY DESCRIPTION

pageName You can use the

pageName query
string parameter to
set which page of the
report to open. The
pageName value
corresponds to the
end of the report
URL when viewing a
report in the Power
BI service, as shown
below.

URL Filters You can use URL

Filters in the embed
URL you received
from the Power BI UI
to filter the content
of the embed. This
way you can build
low-code integrations
with only basic HTML
and JavaScript
experience.

Set which page opens when the report is embedded

The value provided in the pageName setting corresponds to the end of the report URL when viewing a report in
the Power BI service.
1. Open the report from the Power BI service in your web browser, and then copy the URL from the address
bar.

2. Append the pageName setting to the URL.

Filter report content using URL filters

For some advanced features, you can URL Filters to build more experiences using the report. For example, the
URL below filters the report to show data for the Energy industry.
Using the combination of pageName and URL Filters can be powerful. You can build experiences using basic
HTML and JavaScript.
For example, here’s how you can add a button to an HTML page:

<button class="textLarge" onclick='show("ReportSection", "Energy");' style="display: inline-block;">Show

Energy</button>

When pressed, the button calls a function to update the iFrame with an updated URL, which includes the filter for
the Energy industry.
 function show(pageName, filterValue)

var newUrl = baseUrl + "&pageName=" + pageName;

if(null != filterValue && "" != filterValue)

newUrl += "&$filter=Industries/Industry eq '" + filterValue + "'";

//Assumes there’s an iFrame on the page with id=”iFrame”

var report = document.getElementById("iFrame")

report.src = newUrl;

You can add as many buttons as you’d like to create a low -code custom experience.

Considerations and limitations

Doesn't support external guest users with Azure business to business (B2B ).
Secure embed works for reports published to the Power BI service.
The user needs to sign-in to view the report whenever they open a new browser window.
Some browsers require you to refresh the page after sign-in, especially when using InPrivate or Incognito
modes.
To achieve a single sign-on experience, use the Embed in SharePoint Online option, or build a custom
integration using the user owns data approach. Learn more about user owns data.
The automatic authentication capability provided with the Embed option doesn't work with the Power BI
JavaScript API. For the Power BI JavaScript API, use the user owns data approach to embedding. Learn
more about user owns data.

Next steps
Ways to share your work
URL filters
SharePoint Online report web part
Publish to Web
 Publish to web from Power BI
1/14/2019 • 9 minutes to read • Edit Online

With Power BI Publish to web, you can easily embed interactive Power BI visualizations online, such as in blog
posts, websites, through emails or social media, on any device.
You can also easily edit, update, refresh, or unshare your published visuals.

WARNING
When you use Publish to web, the report or visual you publish can be viewed by anyone on the Internet. There is no
authentication used when viewing these reports. Only use Publish to web with reports and data that the anyone on the
Internet (unauthenticated members of the public) should be able to see. This includes detail level data that is aggregated in
your reports. Before publishing this report, ensure you have the right to share the data and visualizations publicly. Do not
publish confidential or proprietary information. If in doubt, check your organization's policies before publishing.

NOTE
To embed your content securely in an internal portal or website, use the Embed or Embed in SharePoint Online options.
This ensures all permissions and data security is enforced when your users are viewing your internal data.

How to use Publish to Web

Publish to web is available on reports in your personal or group workspaces that you can edit. You cannot use
Publish to web with reports that were shared with you, or reports that rely on row level security to secure the
data. See the Limitations section below for a complete list of cases where Publish to web isn't supported.
Review the Warning earlier in this article before using Publish to web.
You can watch how this feature works in the following short video. Then, follow the steps below to try it yourself.
https://www.youtube.com/embed/UF9QtqE7s4Y
The following steps describe how to use Publish to web.
1. On a report in your workspace that you can edit, select File > Publish to web.

2. Review the content on the dialog, and select Create embed code as shown in the following dialog.
3. Review the warning, shown in the following dialog, and confirm that the data is okay to embed in a public
website. If so, select Publish.

4. A dialog appears that provides a link that can be sent in email, embedded in code (such as an iFrame), or
that you can paste directly into your web page or blog.
5. If you’ve previously created an embed code for the report, the embed code quickly appears. You can only
create one embed code for each report.

Tips and Tricks for View modes

When you embed content within a blog post, you typically need to fit it within a specific size of the screen. You
can also adjust the height and the width in the iFrame tag as needed, but you may also need to ensure your
report fits within the given area of the iFrame, so you also need to set an appropriate View Mode when editing
the report.
The following table provides guidance about the View Mode, and how it will appear when embedded.

VIEW MODE HOW IT LOOKS WHEN EMBEDDED

 VIEW MODE HOW IT LOOKS WHEN EMBEDDED

Fit to page will respect the page height and width of your
report. If you set your page to 'Dynamic' ratios like 16:9 or
4:3 your content will scale to fit within the iFrame, you
provided. When embedded in an iFrame, using Fit to page
can result in letterboxing, where a gray background is
shown in areas of the iFrame after the content as scaled to fit
within the iFrame. To minimize letterboxing, set your iFrame
height/width appropriately.

Actual size will ensure the report preserves its size as set on
the report page. This can result in scrollbars being present in
your iFrame. Set the iFrame height and width to avoid the
scrollbars.

Fit to width ensures the content fits within the horizontal

area for your iFrame. A border will still be shown, but the
content will scale to use all the horizontal space available.

Tips and tricks for iFrame height and width

The embed code you receive after you Publish to web will look like the following:

You can edit the width and height manually to ensure it's precisely how you want it to fit onto the page into
which you're embedding it.
To achieve a more perfect fit, you can try adding 56 pixels to the height dimension of the iFrame. This
accommodates the current size of the bottom bar. If your report page uses the Dynamic size, the table below
provides some sizes you can use to achieve a fit without letterboxing.

RATIO SIZE DIMENSION (WIDTH X HEIGHT)

16:9 Small 640 x 416 px

16:9 Medium 800 x 506 px

16:9 Large 960 x 596 px

4:3 Small 640 x 536 px

4:3 Medium 800 x 656 px

4:3 Large 960 x 776 px

Managing embed codes

Once you create a Publish to web embed code, you can manage the codes you create from the Settings menu
of the Power BI service. Managing embed codes includes the ability to remove the destination visual or report
for a code (rendering the embed code unusable), or getting the embed code again.
1. To manage your Publish to web embed codes, open the Settings gear and select Manage embed
codes.

2. The list of embed codes you’ve created appears, as shown in the following image.

3. For each Publish to web embed code in the list, you can either retrieve the embed code, or delete the
embed code and thus make any links to that report or visual no longer work.

4. If you select Delete, you’re asked if you’re sure you want to delete the embed code.
Updates to reports, and data refresh
After you create your Publish to web embed code and share it, the report is updated with any changes you
make. However, it’s important to know that it can take a while for update to be visible to your users. Updates to a
report or visual take approximately one hour to be reflected in Publish to web embed codes.
When you initially use Publish to web to get an embed code, the embed code link is immediately active and can
be viewed by anyone who opens the link. After the initial Publish to web action, subsequent updates to reports
or visuals to which a Publish to web link points can take approximately one hour to be visible to your users.
To learn more, see the How it works section later in this article. If you need your updates to be immediately
available, you can delete the embed code and create a new one.

Data refresh
Data refreshes are automatically reflected in your embedded report or visual. It can take approximately 1 hour
for refreshed data to be visible from embed codes. You can disable automatic refresh by selecting don't refresh
on the schedule for the dataset used by the report.

Custom visuals
Custom visuals are supported in Publish to web. When you use Publish to web, users with whom you share
your published visual do not need to enable custom visuals to view the report.

Limitations
Publish to web is supported for the vast majority of data sources and reports in the Power BI service, however,
the following are not currently supported or available with Publish to web:
Reports using row level security.
Reports using any Live Connection data source, including Analysis Services Tabular hosted on-premises,
Analysis Services Multidimensional, and Azure Analysis Services.
Reports shared to you directly or through an organizational content pack.
Reports in a group in which you are not an edit member.
"R" Visuals are not currently supported in Publish to web reports.
Exporting Data from visuals in a report, which has been published to the web
ArcGIS Maps for Power BI visuals
Reports containing report-level DAX measures
Single sign-on data query models
Secure confidential or proprietary information
The automatic authentication capability provided with the Embed option doesn't work with the Power BI
JavaScript API. For the Power BI JavaScript API, use the user owns data approach to embedding. Learn more
 about user owns data.

Tenant setting
Power BI administrators can enable or disable the publish to web feature. They may also restrict access to
specific groups. Your ability to create an embed code changes based on this setting.

ENABLED FOR ENTIRE DISABLED FOR ENTIRE

FEATURE ORGANIZATION ORGANIZATION SPECIFIC SECURITY GROUPS

Publish to web under Enabled for all Not visible for all Only visible for authorized
report's File menu. users or groups.

Manage embed codes Enabled for all Enabled for all Enabled for all
under Settings
* Delete option only for
authorized users or groups.
* Get codes enabled for all.

Embed codes within admin Status will reflect one of the Status will display Disabled Status will reflect one of the
portal following: following:
* Active * Active
* Not supported * Not supported
* Blocked * Blocked

If a user is not authorized

based on the tenant setting,
status will display as
infringed.

Existing published reports All enabled All disabled Reports continue to render
for all.

Understanding the embed code status column

When viewing the Manage embed codes page for your Publish to web embed codes, a status column is
provided. Embed codes are active by default, but you may encounter any of the states listed below.

STATUS DESCRIPTION

Active The report is available for Internet users to view and interact
with.

Blocked The content of the report violates the Power BI Terms of

Service. It has been blocked by Microsoft. Contact support if
you believe the content was blocked in error.

Not supported The report's data set is using row level security, or another
unsupported configuration. See the Limitations section for a
complete list.

Infringed The embed code is outside of the defined tenant policy. This
typically occurs when an embed code was created and then
the publish to web tenant setting was changed to exclude
the user that owns the embed code. If the tenant setting is
disabled, or the user is no longer allowed to create embed
codes, existing embed codes will show the status of
Infringed.
 STATUS DESCRIPTION

How to report a concern with Publish to web content

To report a concern related to Publish to web content embedded in a website or blog, use the Flag icon in the
bottom bar, shown in the following image. You’ll be asked to send an email to Microsoft explaining the concern.
Microsoft will evaluate the content based on the Power BI Terms of Service, and take appropriate action.
To report a concern, select the flag icon in the bottom bar of the Publish to web report you see.

Licensing and Pricing

You need to be a Microsoft Power BI user to use Publish to web. The consumers of your report (the readers,
viewers) do not need to be Power BI users.

How it works (technical details)

When you create an embed code using Publish to web, the report is made visible to users on the Internet. It’s
publicly available so you can expect viewers to easily share the report through social media in the future. As
users view the report, either by opening the direct public URL or viewing it embedded in a web page or blog,
Power BI caches the report definition and the results of the queries required to view the report. This approach
ensures the report can be viewed by thousands of concurrent users without any impact on performance.
The cache is long-lived, so if you update the report definition (for example, if you change its View mode) or
refresh the report data, it can take approximately one hour before changes are reflected in the version of the
report viewed by your users. It is therefore recommended that you stage your work ahead of time, and create
the Publish to web embed code only when you’re satisfied with the settings.

Next steps
SharePoint Online report web part
Embed report in a secure portal or website
More questions? Try the Power BI Community
 Share a Power BI dashboard that links to an Excel file
in OneDrive
1/14/2019 • 2 minutes to read • Edit Online

In Power BI, you can connect to Excel workbooks on OneDrive for Business and pin tiles to a dashboard from that
workbook. When you share that dashboard, or create a content pack that includes that dashboard:
Your colleagues can view the tiles without needing permissions for the workbook itself. So you can create a
content pack and know that your colleagues can see the tiles created from the Excel workbook on OneDrive.
Clicking the tile opens the workbook inside of Power BI. The workbook will only open if your colleagues have at
least read permissions to the workbook on OneDrive for Business.

Share a dashboard that contains workbook tiles

To share a dashboard that links back to an Excel workbook on OneDrive for Business, see Share a dashboard. The
difference is that you have the option to modify the permissions for the linked Excel workbook before sharing.

1. Enter the email addresses for your colleagues.

2. To enable your colleagues to view the Excel workbook from Power BI, select Go to OneDrive for Business to
set workbook permissions.
3. On OneDrive, modify the permissions as needed.
4. Select Share.

NOTE
Your colleagues won't be able to pin additional tiles from that workbook, or make changes to the Excel workbook from Power
BI.
Create an organizational content pack with a dashboard that contains
workbook tiles
When you publish a content pack you give access to individual colleagues or groups. When you publish a content
pack that contains workbook links, you'll have the option to modify the permissions for the linked Excel workbook
before publishing.
1. In the Create content pack screen, enter email addresses, give the content pack a title and description, and
upload an image.
2. Select the dashboard and/or report that is linked to the Excel workbook on OneDrive for Business.

3. Select Go to OneDrive for Business to set workbook permissions.

4. On OneDrive, modify the permissions as needed.
5. Select Publish.

Share a dashboard from a Power BI workspace

Sharing a dashboard from a Power BI workspace is similar to sharing a dashboard from your own workspace,
except that the files are located in an Office 365 workspace site, instead of your private OneDrive for Business.
Modify the permissions for the Excel workbook before sharing the dashboard with people outside the workspace.
Next steps
Pin a tile to a Power BI dashboard from Excel
Power BI Basic Concepts
More questions? Try the Power BI Community
 Power BI publisher for Excel
1/14/2019 • 7 minutes to read • Edit Online

With Microsoft Power BI publisher for Excel, you can take snapshots of your most important insights in Excel,
like PivotTables, charts, and ranges and pin them to dashboards in Power BI.

What can you pin? Just about anything in an Excel worksheet. You can select a range of cells from a simple sheet
or table, a PivotTable or PivotChart, illustrations and images, text.
What you can't pin: you cannot pin 3D Maps or visualizations in Power View sheets. There are also some elements
you can pin, but it wouldn't make much sense to, like a Slicer or Timeline filter.
When you pin an element from Excel, a new tile is added to a new or existing dashboard in Power BI. The new tile
is a snapshot, so it's not dynamic but you can still update it. For example, if you make a change to a PivotTable or
chart you've already pinned, the dashboard tile in Power BI isn't updated automatically, but you can still update
your pinned elements by using Pin Manager. You'll learn more about Pin Manager in the following sections.

Download and install

Power BI publisher for Excel is an add-in you can download and install on desktop versions of Microsoft Excel
2007 and later.
Download Power BI publisher for Excel
Once you have the publisher installed, you'll see a new Power BI ribbon in Excel, where you can sign in (or sign
out) of Power BI, pin elements to dashboards, and manage elements you've already pinned.
The Power BI publisher for Excel add-in is enabled by default, but if for some reason you don't see the Power BI
ribbon tab in Excel, you'll need to enable it. Click File > Options > Add-ins > COM Add-ins. Select Microsoft
Power BI Publisher for Excel.

Pin a range to a dashboard

You can select any range of cells from your worksheet, and pin a snapshot of that range to an existing or a new
dashboard in Power BI. You can pin the same snapshot to multiple dashboards, too.
To begin, you need to make sure you're signed in to Power BI.
1. Select Profile from the Power BI ribbon tab in Excel. If you're already signed in to Power BI, you'll see a
dialog that shows which account you're currently signed in with. If that's the account you want to use, great
- go to the next set of steps to pin your range. Select Sign out if you want to use a different Power BI
account. If you're not signed in, go to the next step (Step 2).

2. If you're not signed in, select the Sign In link that appears when you select Profile from the Power BI
ribbon tab in Excel, in the Connect to Power BI dialog type in the email address of the Power BI account
you want to use, then select Sign In.
Once you're signed in, follow these steps to pin a range to a dashboard:
1. In Excel, select the Power BI ribbon tab to see the Pin ribbon button.
2. Select a range from your Excel workbook.
3. Click the Pin button from the Power BI ribbon to show the Pin to dashboard dialog. If you're not already
signed into Power BI, you'll be prompted to do so. Select a workspace from the Workspace dropdown list.
If you want to pin to your own dashboard, verify My Workspace is selected. If you want to pin to a
dashboard in a group workspace, select the group from the drop-down list.
4. Choose whether you want to pin to an existing dashboard or create a new dashboard.
5. Click Okay to pin your selection to the dashboard.
6. In Pin to dashboard, select an existing dashboard in the workspace or create a new one, and then click the
Ok button.
Pin a Chart to a dashboard
Just click on the chart, and then click Pin .

Manage pinned elements

With Pin Manager, you can update (refresh) a pinned element's associated tile in Power BI. You can also remove
the pin between an element you've already pinned to dashboards in Power BI.
To update tiles in your dashboard, in Pin Manager select one or more elements and then select Update.
To remove the mapping between a pinned element in Excel and the associated tile in a dashboard, remove
Remove. When you select Remove, you're not removing the element from your worksheet in Excel or deleting
the associated tile in the dashboard. You are removing the pin, or mapping, between them. The removed element
will no longer appear in Pin Manager. If you pin the element again, it will appear as a new tile.
To remove a pinned element (a tile) from a dashboard, you'll need to do that in Power BI. In the tile you want to

delete, select the Open menu icon and then select Delete tile .

Connect to data in Power BI

Beginning with the July 2016 release of Power BI publisher for Excel (including the current release, linked to
above), you can connect directly to data in the Power BI service and analyze that data in Excel using PivotTables
and PivotCharts. This features makes it easy to use Power BI data and Excel together to analyze data that's most
important to you.
Improvements include the following:
Any drivers required to connect to data in Power BI are automatically updated with each release - no need to
install or manage those drivers yourself.
You no longer need to download .odc files to create the connections - Power BI publisher for Excel creates
the connections automatically when you select which report or dataset you want to use.
Now you can create multiple connections and PivotTables in the same workbook
Errors are improved and specific to Power BI publisher for Excel, rather than using default Excel messages
How to connect to Power BI data in Excel
To connect to Power BI data using Power BI publisher for Excel, follow these easy steps:
1. Make sure you're signed in to Power BI. The steps describing how to sign in (or to sign in with a different
account) are provided earlier in this article.
2. Once you're signed in to Power BI with the account you want to use, select Connect to Data from the
 Power BI ribbon tab in Excel.

3. Excel connects to Power BI using an HTTPS connection and presents the Connect to data in Power BI
dialog, where you can select the workspace from which you want to select your data (1, in the image below ),
which type of data you want to connect to, either a report or a dataset (2), and a drop down (3) that allows
you to select which available report or dataset to which to connect.

4. When you make your choices and select Connect from the Connect to data in Power BI dialog, Excel
prepares a PivotTable and displays the PivotTable Fields pane, where you can select fields from your
connected Power BI data, and create tables or charts that help you analyze the data.
If you don't have any data in Power BI, Excel detects that and offers to create sample data for you to connect to and
try.

There are a few things to consider in this release of Power BI publisher for Excel:
Shared data - Data that has been shared with you, but isn't directly visible to you in Power BI, is not available
in Connect to Data.
SSAS on-premises - If the dataset you select originates from an on-premises SQL Server Analysis Services
(SSAS ) and the dataset in Power BI uses DirectQuery to access the data, Power BI publisher for Excel
connects to that data through the on-premises network connection, and does not go through Power BI to
connect to that data. As such, any user trying to connect to such datasets must be connected to the on-premises
network, and is authenticated for access to that data using the authentication method employed by the Analysis
 Services instance where the data is stored.
Required drivers - Power BI publisher for Excel installs all the necessary drivers for this feature to work,
and does so automatically. Among those automatically installed drivers is the Excel OLE DB driver for Analysis
Services; if that driver is removed by the user (or for any other reason), the connection to Power BI data will not
work.
Dataset must have measures - The dataset must have model measures defined in order for Excel to treat the
measures as values in PivotTables, and to correctly analyze the data. Learn more about measures.
Support for Groups - Datasets shared with people outside the specified group are not supported, and cannot
be connected to.
Free versus Pro subscriptions - Activities associated with groups are not supported for free users of Power
BI, and thus won't see any datasets or reports shared with a group in their own workspace.
Shared reports or datasets - Reports or datasets that were shared with you cannot be connected to.
Using Tables instead of Data models - Datasets and reports that are created by importing only tables from
Excel (without a data model) are not supported at this time, and cannot be connected to.
Once you've created compelling charts or other visuals such as a range of data, you can easily pin those to a
dashboard in Power BI, as described earlier in this article.

Related Articles
There are many ways to use Excel and Power BI together, and get the best out of both. Take a look at the following
articles for more information.
Analyze in Excel
Analyze in Excel troubleshooting
 Self-service data prep in Power BI
4/1/2019 • 7 minutes to read • Edit Online

As data volume continues to grow, so does the challenge of wrangling that data into well-formed, actionable
information. We want data that’s ready for analytics, to populate visuals, reports, and dashboards, so we can
quickly turn our volumes of data into actionable insights. With self-service data prep for big data in Power BI,
you can go from data to Power BI insights with just a few clicks.

Power BI introduces dataflows to help organizations unify data from disparate sources and prepare it for
modeling. Analysts can easily create dataflows, using familiar, self-service tools. Dataflows are used to ingest,
transform, integrate, and enrich big data by defining data source connections, ETL logic, refresh schedules, and
more. In addition, the new model-driven calculation engine that's part of dataflows makes the process of data
preparation more manageable, more deterministic, and less cumbersome for data analysts and report creators
alike. Similar to how spreadsheets handle recalculations for all affected formulas, dataflows manage changes
for an entity or data element on your behalf, automating updates, and alleviating what used to be tedious and
time consuming logic checks for even a basic data refresh. With dataflows, tasks that once required data
scientists to oversee (and many hours or days to complete) can now be handled with a few clicks by analysts
and report creators.
Data is stored as entities in the Common Data Model in Azure Data Lake Storage Gen2. Dataflows are
created and managed in app workspaces by using the Power BI service.
Dataflows are designed to use the Common Data Model, a standardized, modular, extensible collection of
data schemas published by Microsoft that are designed to make it easier for you to build, use, and analyze data.
With this model, you can go from data sources to Power BI dashboards with nearly zero friction.
You can use dataflows to ingest data from a large and growing set of supported on-premises and cloud- based
data sources including Dynamics 365, Salesforce, Azure SQL Database, Excel, SharePoint, and more.
You can then map data to standard entities in the Common Data Model, modify and extend existing entities,
and create custom entities. Advanced users can create fully customized dataflows, using a self-service, low -
code/no-code, built-in Power Query authoring experience, similar to the Power Query experience that millions
of Power BI Desktop and Excel users already know.
Once you’ve created a dataflow, you can use Power BI Desktop and the Power BI service to create datasets,
reports, dashboards, and apps that leverage the power of the Common Data Model to drive deep insights into
your business activities.
Dataflow refresh scheduling is managed directly from the workspace in which your dataflow was created, just
like your datasets.

How dataflows work

Here are some examples of how dataflows can work for you:
Organizations can map their data to standard entities in the Common Data Model or create their own
custom entities. These entities can then be used as building blocks to create reports, dashboards, and
apps that work out of the box, and distribute them to users across their organization.
Using the extensive collection of Microsoft data connectors, organizations can connect their own data
sources to dataflows, using Power Query to map the data from its origin and bring it into Power BI. Once
that data is imported by a dataflow (and refreshed at a specified frequency), those dataflow entities may
be used in the Power BI Desktop application to create compelling reports and dashboards.

How to use dataflows

The previous section described a handful of ways dataflows can be used to quickly create powerful analytics in
Power BI. In this section, you get a tour of how quickly you can create insights using dataflows in an
organization, get a quick view into how BI Pros can create their own dataflows, and customize insights for their
own organization.

NOTE
You must have a paid Power BI account to use dataflows, such as a Power BI Pro or Power BI Premium account, but you
are not charged separately for using dataflows.

Extend the common data model for your business needs

For organizations that want to extend the Common Data Model (CDM ), dataflows enable business intelligence
professionals to customize the standard entities, or create new ones. This self-service approach to customizing
the data model can then be used with dataflows to build apps and Power BI dashboards that are tailored to an
organization.
Define dataflows programmatically
You might also want to develop your own programmatic solutions to create dataflows. With public APIs and
the capability to programmatically create custom dataflow definition files (model.json), you create a custom
solution that fits your organization’s unique data and analytics needs.
Public APIs allow developers simple and easy ways to interact with Power BI and dataflows.
Extend your capabilities with Azure
Azure Data Lake Storage Gen2 is included with every paid Power BI subscription (10 GB per user, 100 TB per
P1 node). So, you can easily get started with self-service data prep on Azure Data Lake.
Power BI can be configured to store dataflow data in your organization’s Azure Data Lake Storage Gen2
account. When Power BI is connected to your Azure subscription, data developers and data scientists can
leverage powerful Azure products such as Azure Machine Learning, Azure Databricks, Azure Data Factory, and
more.
Power BI can also connect to folders with schematized data in the Common Data Model format, which are
stored in your organization’s Azure Data Lake Storage account. These folders can be created by services such
as Azure data services. By connecting to these folders, analysts can work seamlessly with this data in Power BI.
For more information about Azure Data Lake Storage Gen2 and dataflows integration, including how to create
dataflows that reside in your organization's Azure Data Lake, see dataflows and Azure Data Lake integration
(Preview ).

Dataflow capabilities on Power BI Premium

For dataflow features and workloads to operate on a Power BI Premium subscription, the dataflow workload
for that Premium capacity must be turned on. The following table describes dataflow features and their
capacities when using a Power BI Pro account, and how that compares to using Power BI Premium.

DATAFLOW CAPABILITY POWER BI PRO POWER BI PREMIUM

Scheduled refresh 8 per day 48

Total Storage 10 GB/user 100 TB/node

Dataflow Authoring with Power Query + +

Online

Dataflow Management within Power + +

BI

Dataflows Data Connector in the + +

Power BI Desktop

Integration with Azure + +

Computed Entities (in-storage +

transformations via M)

New connectors + +

Dataflow incremental refresh +

Running on Power BI Premium +

capacity / Parallel execution of
transforms

Dataflow linked entities +

Standardized Schema / Built-In + +

Support for the Common Data Model

For more information about how to enable dataflows workloads on premium capacity, see the Configure
workloads in a Premium capacity. Dataflow workloads are not currently available in multi-geo capacities.

Summary of self-service data prep for big data in Power BI

As mentioned previously in this article, there are multiple scenarios and examples where dataflows can enable
you to get better control – and faster insights – from your business data. Using a standard data model (schema)
defined by the Common Data Model, dataflows can import your valuable business data, and have the data
ready for modeling and creation of BI insights in a very short period... in what used to take months, or longer, to
create.
By storing business data in the standardized format of the Common Data Model, your BI Pros (or
developers) can create apps that generate quick, easy, and automatic visuals and reports. Those include, but
aren’t limited to:
Mapping your data to standard entities in the Common Data Model to unify data and leverage the known
schema to drive out-of-the-box insights
Creating your own custom entities to unify data across your organization
Use and refresh external data as part of a dataflow, and enable import of that data to drive insights
Getting started with dataflows for developers

Next Steps
This article provided an overview of self service data prep for big data in Power BI, and the many ways you can
use it. The following articles go into more detail about common usage scenarios for dataflows.
Create and use dataflows in Power BI
Using computed entities on Power BI Premium
Using dataflows with on-premises data sources
Developer resources for Power BI dataflows
Dataflows and Azure Data Lake integration
For more information about Power Query and scheduled refresh, you can read these articles:
Query overview in Power BI Desktop
Configuring scheduled refresh
For more information about the Common Data Model, you can read its overview article:
Common Data Model - overview
 Creating and using dataflows in Power BI
4/1/2019 • 8 minutes to read • Edit Online

With advanced data preparation available in Power BI, you can create a collection of data called a dataflow,
which you can then use to connect with business data from various sources, clean the data, transform it, and then
load it to Power BI storage.
A dataflow is a collection of entities (entities are similar to tables) that are created and managed in app
workspaces in the Power BI service. You can add and edit entities in your dataflow, as well as manage data
refresh schedules, directly from the workspace in which your dataflow was created.
Once you create a dataflow, you can use Power BI Desktop and the Power BI service to create datasets,
reports, dashboards, and apps that are based on the data you put into Power BI dataflows, and thereby gain
insights into your business activities.

There are three primary steps to using a dataflow:

1. Author the dataflow, using Microsoft tools that are designed to make doing so straightforward
2. Schedule the refresh frequency of the data you want to bring into your dataflow
3. Build the dataset using your dataflow, using Power BI Desktop
In the following sections, we look at each of these steps and become familiar with the tools provided to complete
each step. Let’s get started.

Creating a dataflow
To create a dataflow, launch the Power BI service in a browser then select an app workspace (dataflows are not
available in my-workspace in the Power BI service) from the navigation pane on the left, as shown in the
following screen. You can also create a new workspace in which to create your new dataflow.
Once you’re in an app workspace area where you can create a dataflow, the + Create button appears in the
upper-right corner of the canvas. Select the + Create button, then select Dataflow from the drop-down list.
It's important to know that there is only one owner of any dataflow, which is the person who creates it. Only the
owner can edit the dataflow. All members of the app workspace who have read or write permissions to the app
workspace where the dataflow is created can connect to the dataflow from within Power BI Desktop, as
described later in this article.

From there, you add Entities, which we describe more in the next section.
Add Entities
An entity is a set of fields that are used to store data, much like a table within a database. In the following image,
you see the selection of data sources from which you can ingest data to Power BI.

When you select a data source, you’re prompted to provide the connection settings, including the account to use
when connecting to the data source, as shown in the following image.
Once connected, you can select which data to use for your entity. When you choose data and a source, Power BI
will subsequently reconnect to the data source in order to keep the data in your dataflow refreshed, at the
frequency you select later in the setup process.

Once you select the data for use in the entity, you can use dataflow editor to shape or transform that data into
the format necessary for use in your dataflow.
Using the dataflow editor
Once you select which data from your source to use for your entity, you can shape your data selection into a
form that works best for your entity, using a Power Query editing experience, similar to the Power Query
Editor in Power BI Desktop. You can learn more about Power Query (Power Query is incorporated into Power
BI Desktop as the Power Query Editor) in the Query overview article for Power BI Desktop.
If you want to see the code that Query Editor is creating with each step, or want to create your own shaping
code, you can use the Advanced Editor.

Dataflows and the Common Data Model (CDM )

Dataflows entities include new tools to easily map your business data to the Common Data Model (Microsoft’s
standardized schema), enrich it with Microsoft and third-party data, and gain simplified access to machine
learning. These new capabilities can be leveraged to provide intelligent and actionable insights into your
business data. Once you’ve completed any transformations in the Edit Queries step, you can map columns from
your data source tables to standard entity fields as defined by the Common Data Model. Standard entities have a
known schema defined by the common data model.
Get more information about this approach, and about the Common Data Model, from the what is the Common
Data Model article.
To leverage the Common Data Model with your dataflow, click on the Map to Standard transformation in the
Edit Queries dialog. In the Map Entities screen that appears, you can select the standard entity to which you
want to map.
When you map a source column to standard field, the following occurs:
1. The source column takes on the standard field name (the column is renamed if the names are different)
2. The sources column gets the standard field data type
To keep the Common Data Model standard entity, all standard fields that are not mapped get Null values.
All source columns that are not mapped remain as-is, to ensure that the result of the mapping is a standard
entity with custom fields.
Once you’ve completed your selections and your entity and its data settings are ready to save, you can select
Save from the menu. Note that you can create multiple entities by selecting the Add entities button, and that
you can Edit entities to refine the queries and entities you’ve created.

When you select Save, you're prompted to name your dataflow and provide a description.
When you’re ready and select the Save button, a window appears that lets you know your dataflow has been
created.

Great – now you’re ready for the next step, which is scheduling the refresh frequency of your data sources.

Schedule the refresh frequency

Once your dataflow has been saved, you’ll want to schedule the refresh frequency for each of your connected
data sources.
Power BI dataflows use the Power BI data refresh process to keep your data up to date. In the Power BI service,
in the app workspace section, there's a collection of areas where your information can be listed, including
dataflows, as shown in the following image.

The Dynamics dataflow entry in the previous image is the dataflow we created in the previous section. To
schedule refresh, select the Schedule refresh icon, under the Actions section, as shown in the following image.

When you select the Schedule refresh icon you’re taken to the Schedule refresh pane, which lets you set the
dataflow refresh frequency and time.
For more information about scheduling refresh, see the article about configuring scheduled refresh, which
describes the refresh behavior of Power BI datasets. Dataflows behave the same behavior as Power BI datasets
in terms of refresh settings.

Connect to your dataflow in Power BI Desktop

Once you’ve created your dataflow and you have scheduled the refresh frequency for each data source that will
populate the model, you’re ready for the third and final step, which is connecting to your dataflow from within
Power BI Desktop.
To connect to the dataflow, in Power BI Desktop select Get Data > Power BI > Power BI dataflows (Beta) as
shown in the following image.
From there, navigate to the app workspace where you saved your dataflow, select the dataflow and then select
the entities that you created from the list.
You can also use the search bar, near the top of the window, to quickly find the name of your dataflow or entities
from among many dataflow entities.
When you select the entity and then select the Load button, the entities appear in the Fields pane in Power BI
Desktop, and appear and behave just like tables from any other dataset.

Using dataflows stored in Azure Data Lake Storage Gen2

Some organizations may want to use their own storage for creation and management of dataflows. You can
integrate dataflows with Azure Data Lake Storage Gen2, if you follow the requirements and manage permissions
properly. Documentation of all the requirements for this approach can be found beginning with the overview
document, dataflows and Azure Data Lake integration (Preview ).

Troubleshooting data connections

There may be occasions when connecting to data sources for dataflows run into issues. This section provides
troubleshooting tips when such issues arise.
Salesforce connector - Using a trial account for Salesforce with dataflows results in a connection failure
with no information provided. To resolve this, use a production Salesforce account or a developer account
for testing.
SharePoint connector - Make sure you supply the root address of the SharePoint site, without any
 subfolders or documents. For example, use link similar to the following:
https://microsoft.sharepoint.com/teams/ObjectModel/
JSON File connector - Currently you can connect to a JSON file using basic authentication only.
Connecting to a JSON file by providing the credentials within the URL (for example,
https://XXXXX.blob.core.windows.net/path/file.json?sv=2019-01-
01&si=something&sr=c&sig=123456abcdefg... ) is not currently supported.
Azure SQL Data Warehouse - Dataflows do not currently support Azure Active Directory (AAD )
authentication for Azure SQL Data Warehouse. Use Basic authentication for this scenario.

Next Steps
This article described how you can create your own dataflow and create a dataset and report in Power BI
Desktop to take advantage of it. The following articles are useful for further information and scenarios when
using dataflows:
Self-service data prep with dataflows
Using computed entities on Power BI Premium
Using dataflows with on-premises data sources
Developer resources for Power BI dataflows
Dataflows and Azure Data Lake integration (Preview )
For more information about the Common Data Model, you can read its overview article:
Common Data Model - overview
Learn more about the Common Data Model schema and entities on GitHub
Related Power BI Desktop articles:
Connect to datasets in the Power BI service from Power BI Desktop
Query overview in Power BI Desktop
Related Power BI service articles:
Configuring scheduled refresh
 Using computed entities on Power BI Premium
4/1/2019 • 3 minutes to read • Edit Online

You can perform in-storage computations when using dataflows with a Power BI Premium subscription. This
lets you perform calculations on your existing dataflows, and return results that enable you to focus on report
creation and analytics.

To perform in-storage computations, you first must create the dataflow and bring data into that Power BI
dataflow storage. Once you have a dataflow that contains data, you can create computed entities, which are
entities that perform in-storage computations.
There are two ways you can connect dataflow data to Power BI:
Using self-service authoring of a dataflow
Using an external dataflow
The following sections describe how to create computed entities on your dataflow data.

How to create computed entities

Once you have a dataflow with a list of entities, you can perform calculations on those entities.
In the dataflow authoring tool in the Power BI service, select Edit entities, then right-click on the entity you want
to use as the basis for your computed entity and on which you want to perform calculations. In the context menu,
choose Reference.
For the entity to be eligible as a computed entity, the Enable load selection must be checked, as shown in the
following image. Right-click on the entity to display this context menu.
By selecting Enable load, you create a new entity for which its source is the referenced entity. The icon changes,
and shows the computed icon, as shown in the following image.

Any transformation you perform on this newly created entity will be run on the data that already resides in
Power BI dataflow storage. That means that the query will not run against the external data source from which
the data was imported (for example, the SQL database from which the data was pulled), but rather, is performed
on the data that resides in the dataflow storage.
Example use cases
What kind of transformations can be performed with computed entities? Any transformation that you usually
specify using the transformation user interface in Power BI, or the M editor, are all supported when performing
in-storage computation.
Consider the following example: you have an Account entity that contains the raw data for all the customers from
your Dynamics 365 subscription. You also have ServiceCalls raw data from the Service Center, with data from
the support calls that were performed from the different account in each day of the year.
Imagine you want to enrich the Account entity with data from the ServiceCalls.
First you would need to aggregate the data from the ServiceCalls to calculate the number of support calls that
were done for each account in the last year.

Next, you would want to merge the Account entity with the ServiceCallsAggregated entity to calculate the
enriched Account table.

And then you can see the results, shown as EnrichedAccount in the following image.
And that's it - the transformation is performed on the data in the dataflow that resides in your Power BI Premium
subscription, not on the source data.

Considerations and limitations

It's important to note that if you remove the workspace from Power BI Premium capacity, the associated
dataflow will no longer refresh.
When working with dataflows specifically created in an organization's Azure Data Lake Storage Gen2 account,
linked entities and computed entities only work properly when the entities reside in the same storage account.
For more information, see connect Azure Data Lake Storage Gen2 for dataflow storage (Preview ).
Linked entities are not available for dataflows that are created from Common Data Model (CDM ) folders. For
more information, see add a CDM folder to Power BI as a dataflow (Preview ).
As a best practice, when doing computations on data joined by on-premises and cloud data, create a new entity
to perform such computations. This provides a better experience than using an existing entity for computations,
such as an entity that is also querying data from both sources and doing in-lake transformations.

Next Steps
This article described computed entities and dataflows available in the Power BI service. Here are some more
articles that might be useful.
Self-service data prep with dataflows
Create and use dataflows in Power BI
Using dataflows with on-premises data sources
Developer resources for Power BI dataflows
Configure workspace dataflow settings (Preview )
Add a CDM folder to Power BI as a dataflow (Preview )
Connect Azure Data Lake Storage Gen2 for dataflow storage (Preview )
For more information about Power Query and scheduled refresh, you can read these articles:
Query overview in Power BI Desktop
Configuring scheduled refresh
For more information about the Common Data Model, you can read its overview article:
Common Data Model - overview
 Connect to data sources for Power BI dataflows
4/1/2019 • 4 minutes to read • Edit Online

With Power BI dataflows, you can connect to many different data sources to create new dataflows, or add new
entities to an existing dataflow.
This article lists the many available data sources for creating or adding to dataflows, and describes how to create
those dataflows using these data sources.
For an overview of how to create and use dataflows, see creating and using dataflows in Power BI.

Create a dataflow from a data source

To connect to data, from the Power BI service select the + Create menu item, then select dataflow from the
menu that appears. When selected, the following image appears in the canvas of the Power BI service.

If your dataflow already exists, you can add new entities to your dataflow by selecting Add entities, shown below,
or by selecting Get data in the dataflow authoring tool.
The following image shows the Get data button in the dataflow authoring tool.

Data sources for dataflows

You can view the available data sources by selecting Get Data from the dataflow authoring tool, which then
displays a dialog for selecting the categories and each data source, as shown in the following image.

Data sources for dataflows are organized into the following categories, which appear across the top of the Get
data dialog:
All categories
File
 Database
Power BI
Azure
Online Services
Other
The All categories category contains all data sources, from all categories.
The File category includes the following available data connections for dataflows:
Access
Excel
JSON
Text/CSV
XML
The Database category includes the following available data connections for dataflows:
IBM DB2 Database
MySQL Database
Oracle Database
PostgreSQL Database
SQL Server Database
Sybase Database
Teradata Database
Vertica
The Power BI category includes the following available data connections for dataflows:
Power BI dataflows
The Azure category includes the following available data connections for dataflows:
Azure Blobs
Azure Data Explorer
Azure SQL Data Warehouse
Azure SQL Database
Azure Tables
The Online Services includes the following available data connections for dataflows:
Amazon Redshift
Common Data Service for Apps
Microsoft Exchange Online
Salesforce Objects
Salesforce Reports
SharePoint Online List
Smartsheet
The Other category includes the following available data connections for dataflows:
Active Directory
OData
SharePoint List
 Web API
Web page
Blank table
Blank Query

Connecting to a data source

To connect to a data source, select the data source. We'll use one example to show how the process works, but each
data connection for dataflows is similar in process. Different connectors may require specific credentials or other
information, but the flow is similar. In our example, you see in the following image that Common Data Service
for Apps is selected from the Online services data connection category.

A connection window for the selected data connection is displayed. If credentials are required, you're prompted to
provide them. The following image shows a Server URL being entered to connect to a Common Data Service for
Apps server.

Once the Server URL or resource connection information is provided, select Sign in to enter the credentials to use
for the data access, then select Next.
Power Query Online initiates and establishes the connection to the data source, and then presents the available
tables from that data source in the Navigator window, shown in the following image.

You can select tables and data to load by selecting the checkbox next to each in the left pane. To load the data, select
OK from the bottom of the Navigator pane. A Power Query Online dialog appears, where you can edit queries
and perform any other transformation you want to perform on the selected data.

That's all there is to it. Other data sources have similar flows, and use Power Query Online to edit and transform
the data you bring into your dataflow.

Connecting to additional data sources

There are additional data connectors that are not shown in the Power BI dataflows user interface, but are
supported with a few additional steps.
You can take the following steps to create a connection to a connector that is not displayed in the user interface:
1. Open Power BI Desktop and select Get Data.
2. Open Power Query Editor in Power BI Desktop, then right-click on the relevant query and open the
Advanced Editor, as shown in the following image. From there, you can copy the M script that appears in
the Advanced Editor.
3. Open the Power BI dataflow, and select Get data for a blank query, as shown in the following image.

4. Paste the copied query into the blank query for the dataflow.

And then your script connects to the data source you specified.
The following list shows which connectors you can currently use by copying and pasting the M query into a blank
query:
SAP Business Warehouse
Azure analysis Services
Adobe Analytics
ODBC
OLE DB
Folder
SharePoint Online folder
SharePoint folder
Hadoop HDFS
Azure HDInsight (HDFS )
Hadoop file HDFS
Informix (beta)
That's all there is to connecting to data sources in Power BI dataflows.

Next Steps
This article showed which data sources you can connect to for dataflows. The following articles go into more detail
about common usage scenarios for dataflows.
Self-service data prep in Power BI
Create and use dataflows in Power BI
Using computed entities on Power BI Premium
Using dataflows with on-premises data sources
Developer resources for Power BI dataflows
Dataflows and Azure Data Lake integration (Preview )
For more information about Power Query and scheduled refresh, you can read these articles:
Query overview in Power BI Desktop
Configuring scheduled refresh
For more information about the Common Data Model, you can read its overview article:
Common Data Model - overview
 Using dataflows with on-premises data sources
4/1/2019 • 2 minutes to read • Edit Online

With dataflows, you can create a collection of data from various sources, clean the data, transform it, and then
load it to Power BI storage. When creating dataflow you may want to use on-premises data sources. This article
clarifies requirement associated with creating dataflows and how your Enterprise Gateway needs to be
configured to enabled those connections.

Configuring an Enterprise Gateway for use with dataflows

To use an on-premises data source in a dataflow, any user creating the dataflow must have an Enterprise
Gateway installed and configured. The user creating the dataflow also must be the Enterprise Gateway's
administrator in order to use that gateway for a dataflow.

NOTE
Dataflows are only supported using Enterprise Gateways.

Using an on-premises data source in a dataflow

When creating a dataflow, select an on-premises data source from the data sources list, as shown in the
following image.
Once you make your selection, you're prompted to provide the connection details for the Enterprise Gateway
that will be used to access the on-premises data. You must select the gateway itself, and provide credentials for
the selected gateway. Only gateways for which the user is an administrator appear in the drop-down list.

Monitoring your gateway

You can monitor your Enterprise Gateway for a dataflow in the same way you monitor gateways for a dataset.
In the dataflow’s settings screen in Power BI, you can monitor a dataflow’s gateway status and assign a gateway
to the dataflow, as shown in the following image.
Changing a gateway
You can change the Enterprise Gateway used for a given dataflow in two ways:
1. From the authoring tool – you can change the gateway assigned to all of your queries using the
dataflow authoring tool.

NOTE
The dataflow will try to find or create the required datasources using the new gateway. If it cannot do so, you will
not be able to change the gateway until all needed dataflows are available from the selected gateway.

2. From the settings screen - you can change the assigned gateway using the settings screen for the
dataflow in the Power BI service.
To learn more about Enterprise Gateways, see On-premises data gateway.

Considerations and limitations

There are a few known limitations to using Enterprise Gateways and dataflows:
Each dataflow may use only one gateway. As such, all queries should be configured using the same gateway.
Changing the gateway impact the entire dataflow.
If several gateways are needed, the best practice is to build several dataflows (one for each gateway) and use
the compute or entity reference capabilities to unify the data.
Dataflows are only supported using enterprise gateways. Personal gateways will not be available for selection
in the drop down lists and settings screens.

Next Steps
This article provided information about using on-premises data source for dataflows, and how to use and
configure gateways to access such data. The following articles may also be helpful
Self-service data prep with dataflows
Create and use dataflows in Power BI
Using computed entities on Power BI Premium
Developer resources for Power BI dataflows
For more information about Power Query and scheduled refresh, you can read these articles:
Query overview in Power BI Desktop
 Configuring scheduled refresh
For more information about the Common Data Model, you can read its overview article:
Common Data Model - overview
 Link entities between dataflows in Power BI
4/1/2019 • 4 minutes to read • Edit Online

With dataflows in Power BI, you can have a single organizational data storage source where business analysts can
prep and manage their data once, and then reuse it between different analytics apps in the organization.
When you link entities between dataflows, you can reuse entities that have already been ingested, cleansed and
transformed by other dataflows owned by others without the need to maintain that data. The linked entities simply
point to the entities in other dataflows, and do not copy or duplicate the data.

Linked entities are read only. If you want to create transformations for a linked entity, you must create a new
computed entity with a reference to the linked entity.

Linked entity availability

Linked entities require a Power BI Premium subscription to refresh. Linked entities are available in any dataflow on
a workspace that is hosted on Power BI Premium capacity. There are no limitations on the source dataflow.
Linked entities only work properly in new Power BI workspaces. You can learn more about new Power BI
workspaces. All linked dataflows must be located in new workspaces to work properly.
 NOTE
Entities differ based on whether they’re standard entities or computed entities. Standard entities (often simply referred to as
entities) query an external data source, such as a SQL database. Computed entities require Premium capacity on Power BI
and run their transformations on data that’s already in Power BI storage.
If your dataflow isn’t in a Premium capacity workspace, you can still reference a single query or combine two or more queries
as long as the transformations aren’t defined as in-storage transformations. Such references are considered standard entities.
To do so, turn off the Enable load option for the referenced queries to prevent the data from being materialized and from
being ingested into storage. From there, you can reference those Enable load = false queries, and set Enable load to On
only for the resulted queries that you want to materialize.

How to link entities between dataflows

There are a few ways to link entities between dataflows in Power BI. You can select Add linked entities from the
Dataflows authoring tool, as shown in the following image.

You can also select Add linked entities from the Add entities menu item in the Power BI service.
To link entities, you must sign in with your Power BI credentials.
A Navigator window opens and lets you choose a set of entities to which you can connect. The entities displayed
are entities for which you have permissions, across all workspaces in your Power BI tenant.
Once your linked entities are selected, they appear in the list of entities for your dataflow in the authoring tool, with
a special icon identifying them as Linked entities.
You can also view the source dataflow from the dataflow settings of your linked entity.

Refresh logic of linked entities

The default refresh logic of linked entities changes, based on whether the source dataflow resides in the same
workspace as the destination dataflow. The following sections describe the behavior of each.
Links between workspaces
Refresh for links from entities in different workspaces behave like an external data source. When the dataflow
refreshes, it takes the latest data for the entity from the source dataflow. If the source dataflow refreshes, it doesn’t
automatically impact the data in the destination dataflow.
Links in the same workspace
When refresh of the data for a source dataflow occurs, that event automatically triggers a refresh process for
dependent entities in all destination dataflows in the same workspace, including any calculated entities based on
them. All other entities in the destination dataflow are refreshed according to dataflow schedule. Entities that
depend on more than one source update their data whenever any of their sources updates successfully.
It's useful to note that the entire refresh process commits at once. Because of this, if the destination dataflow
refresh fails to refresh, the source dataflow will fail its refresh as well.

Permissions when viewing reports from dataflows

When creating a Power BI report that includes data based on a dataflow, users can see any linked entities only
when the user has access to the source dataflow.

Limitations and considerations

There are a few limitations to keep in mind when working with linked entities:
There is a maximum of five referencing hops
Cyclic dependencies of linked entities are not allowed
The dataflow must reside in a new Power BI workspace
A linked entity can't be joined with a regular entity that gets its data from an on-premises data source
Next Steps
The following articles may be useful as you create or work with dataflows.
Self-service data prep in Power BI
Create and use dataflows in Power BI
Using computed entities on Power BI Premium
Using dataflows with on-premises data sources
Developer resources for Power BI dataflows
For more information about Power Query and scheduled refresh, you can read these articles:
Query overview in Power BI Desktop
Configuring scheduled refresh
For more information about the Common Data Model, you can read its overview article:
Common Data Model - overview
 Using incremental refresh with Power BI dataflows
4/1/2019 • 8 minutes to read • Edit Online

With dataflows, you can bring large amounts of data into Power BI to create compelling reports and analytics. In
some cases, however, it's not practical to update a full copy of source data in each refresh. A good alternative is
incremental refresh, which provides the following benefits for dataflows:
Refresh occurs faster - only data that's changed needs to be refreshed. For example, refresh only the last five
days of a 10-year dataflow.
Refresh is more reliable - for example, it is not necessary to maintain long-running connections to volatile
source systems.
Resource consumption is reduced - less data to refresh reduces overall consumption of memory and other
resources.
Using incremental refresh for Power BI dataflows requires that the workspace where the dataflow resides be in
Premium capacity to run, and the data source ingested into the dataflow must have a datetime field on which
incremental refresh can filter.

Configuring incremental refresh for dataflows

A dataflow can contain many entities. Incremental refresh is set up at the entity level, allowing one dataflow to hold
both fully refreshed entities and incrementally refreshed entities.
To set up an incremental refreshed entity, start by configuring your entity as you would any other entity. To learn
more about dataflow set up, see Self-service data prep in Power BI.
Once the dataflow is created and saved, select the incremental refresh icon in the entity view, as shown in the
following image:
When you click the icon, the Incremental refresh settings window appears. When you toggle incremental refresh
to the On position, you can configure your incremental refresh.
The following list explains the settings in the Incremental refresh settings window.
1. Incremental refresh on/off toggle – this slider toggles incremental refresh policy on/off for the entity
2. Filter field drop down – selects the query field on which the entity should be filtered for increments. This
field only contains datetime fields. You cannot use incremental refresh if your entity doesn’t contain a
datetime field.
3. Store rows from the past – the following example helps explain the next few settings.
For this example, we define a refresh policy to store five years of data in total, and incrementally refresh 10
days of data. If the entity is refreshed daily, the following is carried out for each refresh operation:
Add a new day of data.
Refresh 10 days up to the current date.
Remove calendar years that are older than five years prior to the current date. For example, if the current
 date is January 1st 2019, the year 2013 is removed.
The first dataflow refresh may take a while to import all five years, but subsequent refreshes are likely to
complete in a small fraction of the initial refresh time.
4. Detect data changes - Incremental refresh of 10 days is much more efficient than full refresh of 5 years,
but we may be able to do even better. When you select the Detect data changes checkbox, you can select a
date/time column to identify and refresh only the days where the data has changed. This assumes such a
column exists in the source system, which is typically for auditing purposes. The maximum value of this
column is evaluated for each of the periods in the incremental range. If that data has not changed since the
last refresh, there is no need to refresh the period. In the example, this could further reduce the days
incrementally refreshed from 10 to perhaps two.

TIP
The current design requires that the column to detect data changes be persisted and cached into memory. You may want to
consider one of the following techniques to reduce cardinality and memory consumption:
Persist only the maximum value of this column at time of refresh, perhaps using a Power Query function.
Reduce the precision to a level that is acceptable given your refresh-frequency requirements.

5. Only refresh complete periods - imagine your refresh is scheduled to run at 4:00 AM every morning. If
data appears in the source system during those first four hours of that day, you may not want to account for
it. Some business metrics, such as barrels per day in the oil and gas industry, are not practical or sensible to
account for based on partial days.
Another example where only refreshing complete periods is appropriate is refreshing data from a financial
system. Imagine a financial system where data for the previous month is approved on the 12th calendar day
of the month. You could set the incremental range to 1 month and schedule the refresh to run on the 12th
day of the month. With this option checked, it would refresh January data (the most recent complete
monthly period) on February 12th.

NOTE
Dataflow incremental refresh determines dates according to the following logic: if a refresh is scheduled, incremental refresh
for dataflows uses the time-zone defined in the refresh policy. If no schedule for refreshing exists, incremental refresh uses the
time from the machine running the refresh.

The incremental refresh query

Once incremental refresh is configured, the dataflow automatically alters your query to include filter by date. You
can edit the auto-generated query using the Advanced Power Query Editor to fine-tune or customize your
refresh. Read more about incremental refresh and how it works in the following section.

Incremental refresh and linked versus computed entities

For linked entities, incremental refresh updates the source entity. Since linked entities are simply a pointer to the
original entity, incremental refresh has no impact on the linked entity. When the source entity refreshes according
to its defined refresh policy, any linked entity should assume the data in the source is refreshed.
Computed entities are based on queries running over a datastore, which may be another dataflow. As such,
computed entities behave in the same way as linked entities.
Since computed entities and linked entities behave similarly, the requirements and configuration steps are the
same for both. One difference is that for computed entities, in certain configurations, incremental refresh cannot
run in an optimized fashion due to the way partitions are built.

Changing between incremental and full refresh

Dataflows support changing refresh policy between incremental and full refresh. When a change occurs in either
direction (full to incremental, or incremental to full refresh), the change impacts the dataflow after the next refresh.
When moving a dataflow from full refresh to incremental, the new refresh logic updates the dataflow adhering to
the refresh window and increment as defined in the incremental refresh settings.
When moving a dataflow from incremental to full refresh, all data accumulated in incremental refresh is
overwritten by the policy defined in full refresh. You must approve this action.

Dataflow incremental refresh and datasets

Dataflow incremental refresh and dataset incremental refresh are designed to work in tandem. It's is acceptable
and supported to have an incrementally refreshing entity in a dataflow, fully loaded into a dataset, or a fully loaded
entity in dataflow incrementally loaded to a dataset.
Both approaches according to your specified definitions in the refresh settings. You can read more about
incremental refresh in incremental refresh in Power BI Premium.

Time zone support in incremental refresh

Dataflow incremental refresh is dependent on the time in which it is run. The filtering of the query is dependent on
the day it runs.
To accommodate those dependencies and to ensure data consistency, incremental refresh for dataflows
implements the following heuristic for refresh now scenarios:
In the case where a scheduled refresh is defined in the system – incremental refresh uses the timezone
settings from the schedule refresh. This ensures that whatever timezone the person refreshing the dataflow
is in, it will always be consistent with the system’s definition.
If no schedule refresh is defined, dataflows use the timezone of the refreshing user’s computer.
Incremental refresh may also be invoked using APIs. in this case, the API call may hold a timezone setting that is
used in the refresh. Using APIs can be helpful for testing and validation purposes.

Incremental refresh implementation details

Dataflows use partitioning for incremental refresh. Once XMLA-endpoints for Power BI Premium are available, the
partitions become visible. Incremental refresh in dataflows retains the minimum number of partitions to meet
refresh policy requirements. Old partitions that go out of range are dropped, maintaining a rolling window.
Partitions are opportunistically merged, reducing the total number of partitions required. This improves
compression and, in some cases, can improve query performance.
The examples in this section share the following refresh policy:
Store rows in the last 1 Quarter
Refresh rows in the last 10 Days
Detect data changes = False
Only refresh complete days = True
Merge partitions
In this example, day partitions are automatically merged to the month level once they go outside the incremental
range. Partitions in the incremental range need to be maintained at daily granularity to allow only those days to be
refreshed. The refresh operation with Run Date 12/11/2016 merges the days in November, because they fall
outside the incremental range.

Drop old partitions

Old partitions that fall outside the total range are removed. The refresh operation with Run Date 1/2/2017 drops
the partition for Q3 2016 because it falls outside the total range.

Recovery from prolonged failure

This example simulates how the system recovers gracefully from prolonged failure. Let's say refresh doesn't run
successfully because data source credentials expired, and the issue takes 13 days to resolve. The incremental range
is only 10 days.
The next successful refresh operation, with Run Date 1/15/2017, needs to backfill the missing 13 days and refresh
them. It also needs to refresh the previous 9 days because they were not refreshed on the normal schedule. In
other words, the incremental range is increased from 10 to 22 days.
The next refresh operation, with Run Date 1/16/2017, takes the opportunity to merge the days in December and
the months in the Q4 2016.
Next Steps
This article described incremental refresh for dataflows. Here are some more articles that might be useful.
Self-service data prep with dataflows
Create and use dataflows in Power BI
Using dataflows with on-premises data sources
Developer resources for Power BI dataflows
For more information about Power Query and scheduled refresh, you can read these articles:
Query overview in Power BI Desktop
Configuring scheduled refresh
For more information about the Common Data Model, you can read its overview article:
Common Data Model - overview
 Developer resources for Power BI dataflows
4/1/2019 • 2 minutes to read • Edit Online

There are many ways to use dataflows with no code, by creating or connecting to entities in the Power BI service
and connecting to them in Power BI Desktop. Many organizations want the flexibility to develop their own
solutions. This article provides information about the Power BI REST API and other developer resources.

Developer resources
The following developer resources are available for working with Power BI dataflows:

DATAFLOW RESOURCE DESCRIPTION

Power BI dataflow REST API Reference A complete reference guide to the dataflow REST API.

Next Steps
This article provided information about developer resources for dataflows. For more information about
dataflows, the following articles may be helpful:
Self-service data prep with dataflows
Create and use dataflows in Power BI
Using computed entities on Power BI Premium
Using dataflows with on-premises data sources
For information about CDM development and tutorial resources, see the following:
Common Data Model - overview
CDM folders
CDM model file definition
For more information about Power Query and scheduled refresh, you can read these articles:
Query overview in Power BI Desktop
Configuring scheduled refresh
 Connect to data created by Power BI dataflows in
Power BI Desktop (Beta)
1/14/2019 • 3 minutes to read • Edit Online

In Power BI Desktop, you can connect to data created by Power BI dataflows just like any other data source in
Power BI Desktop.

The Power BI dataflows (Beta) connector lets you connect to entities created by dataflows in the Power BI
service.

Considerations and limitations

To use this Beta version of the Power BI dataflows connector, you must be running the most recent version of
Power BI Desktop. You can always download Power BI Desktop and install it on your computer to ensure you
have the most recent version.
 NOTE
The previous version of the Power BI dataflows connector required that you download a .MEZ file and place it in a folder.
Current versions of Power BI Desktop include the Power BI dataflows connector, so that file is no longer required and can
cause conflicts with the included version of the connector. If you manually placed that .MEZ file into the folder, you must
delete that downloaded .MEZ file from your Documents > Power BI Desktop > Custom connectors folder to avoid
conflicts.

Desktop performance
Power BI Desktop runs locally on the computer on which it is installed. Ingestion performance of dataflows is
determined by a variety of factors. Those factors include the size of the data, your computer's CPU and RAM,
network bandwidth, distance form the data center, and other factors.
You can improve data ingestion performance for dataflows. For example, if the ingested data size is too large for
Power BI Desktop to manage on your computer, you can use linked and computed entities in dataflows to
aggregate the data (within dataflows) and ingest only the pre-prepared, aggregated data. In that manner, the
processing of large data is performed online in dataflows, rather than being performed locally in your running
instance of Power BI Desktop. That approach lets Power BI Desktop ingest smaller amounts of data, and keeps
the experience with dataflows responsive and quick.

Considerations and limitations

Most dataflows reside in the Power BI service tenant. However, Power BI Desktop users cannot access dataflows
that are stored in Azure Data Lake Storage Gen2 account, unless they are the owner of the dataflow, or they have
been explicitly authorized to the dataflow’s CDM folder. Consider the following situation:
1. Anna creates a new app workspace and configures it to store dataflows in the organization’s data lake.
2. Ben, who is also a member of the workspace Anna created, wants to use Power BI Desktop and the dataflow
connector to get data from the dataflow Anna created.
3. Ben receives an error because he was not added as an authorized user to the dataflow’s CDM folder in the
data lake.

To resolve this issue, Ben must be granted reader permissions to the CDM Folder and its files. You can learn more
about how to grant access to the CDM Folder in this article.

Next steps
There are all sorts of interesting things you can do with Power BI dataflows. For more information, check out the
following resources:
Self-service data prep with dataflows
Create and use dataflows in Power BI
Using computed entities on Power BI Premium (Preview )
Using dataflows with on-premises data sources (Preview )
Developer resources for Power BI dataflows (Preview )
For more information about integration with Azure Data Lake Storage Gen2, see the following articles:
Dataflows and Azure Data Lake integration (Preview )
Configure workspace dataflow settings (Preview )
Add a CDM folder to Power BI as a dataflow (Preview )
Connect Azure Data Lake Storage Gen2 for dataflow storage (Preview )
There are also articles about Power BI Desktop that you might find useful:
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Enter data directly into Power BI Desktop
 Dataflows and Azure Data Lake integration
(Preview)
4/1/2019 • 5 minutes to read • Edit Online

By default, data used with Power BI is stored in internal storage provided by Power BI. With the integration of
dataflows and Azure Data Lake Storage Gen2 (ADLS Gen2), you can store your dataflows in your organization's
Azure Data Lake Storage Gen2 account.

How CDM folders relate to dataflows

With dataflows, users and organizations can unify data from disparate sources, and prepare it for modeling.
With the Common Data Model (CDM ), organizations can use a data format that provides semantic consistency
across applications and deployments. And with Azure Data Lake Storage gen2 (ADLS Gen2), fine-grained access
and authorization control can be applied to data lakes in Azure. When combined, these elements provide
compelling centralized data, structured data, fine-grained access control, and semantic consistency for apps and
initiaties across the enterprise.
Data stored in CDM format provides semantic consistency across applications and deployments in an
organization. With CDM integration with ADLS Gen2, the same structural consistency and semantic meaning
can be applied to data stored in (ADLS Gen2) by using CDM folders that contain schematized data in standard
CDM format. The standardized metadata and self-describing data in an Azure Data Lake facilitate easy metadata
discovery, and interoperation between data producers and consumers such as Power BI, Azure Data Factory,
Azure Data Lake, Databricks and Azure Machine Learning (ML ).
Dataflows store their definition and data in CDM folders, in the following formats:
Model.json
The Model.json metadata description file contains semantic information about entity records and attributes,
and links to underlying data files. The existence of the model.json file indicates compliance with CDM
metadata format, and may include standard entities which have additional rich out-of-box semantic metadata
that applications can use.
Power BI also stores each data source information along with the query and transformations generated by
the Dataflow Editor experience in the Power BI service. Passwords to data sources are not stored in the model
file.
Data files
The data files are included in the CDM folder in well-defined structure and format (subfolders are optional, as
described later in this article) and referenced in the model.json file. Currently, data files must be in .csv format,
 but additional formats may be supported in subsequent updates.
The following diagram shows a sample CDM folder, created by a Power BI dataflow, that contains three entities:

The model.json or metadata file in the previous image would provide pointers to the entity data files throughout
the CDM folder.

Power BI organizes CDM folders in the data lake

With Power BI dataflows and its integration with ADLS Gen2, Power BI can produce data in a data lake. As a
data producer, Power BI must create a CDM folder for each dataflow containing the model.json file and its
associated data files. Power BI stores its data in isolation from other data producers in the data lake by using file
systems. You can read more about Azure Data Lake Storage Gen2 file system and hierarchical namespace in the
article that describes them.
Power BI uses subfolders for disambiguation, and to provide improved organization of data when presented in
the Power BI service. The folder naming and structure represent workspaces (Folders) and dataflows (CDM
Folders). The following diagram shows how a data lake shared by Power BI and other data producers may be
structured. Each service, in this case Dynamics 365, Dynamics for Finance and Operation, and Power BI, creates
and maintains their own filesystem. Depending on the experience in each service, subfolders are created to
better organize CDM folders within the file system.

Power BI protects data in the data lake

Power BI uses Active Directory OAuth Bearer tokens and POSIX ACLs functionality provided by Azure Data
Lake Storage Gen2. These features enable scoping Power BI's access to the file system it manages in the data
lake, and also scoping people's access only to dataflows or CDM folders that they create.
To create and manage CDM folders within the Power BI file system, read, write and execute permissions to the
file system is required. Each dataflow created in Power BI is stored in its own CDM folder, and the owner of the
dataflow is granted read-only access to the CDM folder and its contents. This approach protects the integrity of
the data Power BI generates, and provides administrators with the ability to monitor which users accessed the
CDM folder using audit logs.
Authorizing users or services for CDM folders
Sharing CDM folders with data consumers, such as users or services that need to read the data, is simplified
with Active Directory OAuth Bearer tokens and POSIX ACLs. Doing so provides administrators with the ability
to monitor who accessed the CDM folder. The only action required is to grant access to an Active Directory
object of your choice (such as a user group or service) to the CDM Folder. We recommend that all access to the
CDM folder, for any identity other than the data producer, be granted as read-only. Doing so protects the
integrity of the data that the producer generates.
To add CDM folders to Power BI, the user adding the CDM Folder should have Read Access ACLs on both CDM
folder itself and any files or folders within it. In addition, Execute Access ACLs on both CDM folder itself and any
folders within it. It is recommended you review both Access control lists on files and directory and Best practices
for using Azure Data Lake Storage Gen2 articles for more information.
Alternative forms of authorization
People or services outside of Power BI can also leverage alternatives forms of authorization these alternatives
permit holders of the key access to all resources in the account, full access to all resources in the lake, and cannot
be scoped to file systems or CDM Folders. Those alternatives may be simple ways to grant access, but they limit
the ability to share specific resources in the data lake, and do not provide users with auditing of who accessed
the storage. Full details of available authorization schemes are provided in the Access control in Azure Data Lake
Storage Gen2 article.

Next steps
This article provided an overview of the integration of Power BI dataflows, CDM folders, and Azure Data Lake
Storage Gen2. For additional information, take a look at the following articles:
For more information about dataflows, CDM, and Azure Data Lake Storage Gen2, take a look at the following
articles:
Configure workspace dataflow settings (Preview )
Add a CDM folder to Power BI as a dataflow (Preview )
Connect Azure Data Lake Storage Gen2 for dataflow storage (Preview )
For information about dataflows overall, check out these articles:
Create and use dataflows in Power BI
Using computed entities on Power BI Premium
Using dataflows with on-premises data sources
Developer resources for Power BI dataflows
For more information about Azure storage, you can read these articles:
Azure Storage security guide
Get started with github samples from Azure Data Services
For more information about the Common Data Model, you can read its overview article:
Common Data Model - overview
CDM folders
 CDM model file definition
And you can always try asking questions of the Power BI Community.
 Connect Azure Data Lake Storage Gen2 for dataflow
storage (Preview)
4/1/2019 • 9 minutes to read • Edit Online

You can configure Power BI workspaces to store dataflows in your organization’s Azure Data Lake Storage Gen2
account. This article describes the general steps necessary to do so, and provides guidance and best practices
along the way. There are some advantages to configuring workspaces to store dataflow definitions and datafiles
in your data lake, including the following:
Azure Data Lake Storage Gen2 provides an enormously scalable storage facility for data
Dataflow data and definition files can be leveraged by your IT department's developers to leverage Azure Data
and artificial intelligence (AI) services as demonstrated in the GitHub samples from Azure Data Services
Enables developers in your organization to integrate dataflow data into internal applications, and line-of-
business solutions, using developer resources for dataflows and Azure
To use Azure Data Lake Storage Gen2 for dataflows, you need the following:
Power BI tenant - at least one account in your Azure Active Directory (AAD ) tenant must have signed up for
Power BI
A Global Administrator account - this account is required to connect and configure Power BI to store the
dataflow definition, and data, in your Azure Data Lake Storage Gen2 account
An Azure subscription - you need an Azure subscription to use Azure Data Lake Storage Gen2
Resource group - use a resource group you already have, or you can create a new one
An Azure Storage account with Data Lake Storage Gen2 (Preview) feature enabled - to connect to
Azure Data Lake Storage Gen2, you need to sign up for its public preview

TIP
If you don't have an Azure subscription, create a free account before you begin.

Prepare your Azure Data Lake Storage Gen2 for Power BI

Before you can configure Power BI with an Azure Data Lake Storage Gen2 account, you must create and
configure a storage account. Let's take a look at the requirements for Power BI:
1. The storage account must be created in the same AAD tenant as your Power BI tenant.
2. The storage account must be created in the same region as your Power BI tenant. To determine where you
Power BI tenant is located, see where is my Power BI tenant located.
3. The storage account must have the Hierarchical Name Space feature enabled.
4. Power BI service must be granted a Reader role on the storage account.
5. A Filesystem named powerbi must be created.
6. Power BI services must be authorized to the powerbi filesystem you create.
The following sections walk through the steps necessary to configure your Azure Data Lake Storage Gen2
account in detail.
Create the storage account
Follow the steps in the Create an Azure Data Lake Storage Gen2 storage account article.
1. Make sure you select the same location as your Power BI tenant, and set your storage as StorageV2 (general
purpose v2)
2. Make sure you enable the hierarchical namespace feature
3. It is recommended to set replication setting to Read-access geo-redundant storage (RA -GRS )
Grant the Power BI service a reader role
Next, you need to grant the Power BI service a reader role in your created storage account. It's a built-in role, so
the steps are straightforward.
Follow the steps in Assign a built-in RBAC role.
In the Add role assignment window, select the Reader role to assign to the Power BI service. Then use search to
locate Power BI Service. The following image shows the Reader role assigned to the Power BI service.

NOTE
Allow at least 30 minutes for permission for propagate to Power BI from the portal. Any time you change permissions in
the portal, allow 30 minutes for those permissions to be reflected in Power BI.

Create a file system for Power BI

You must create a file system named powerbi before your storage account can be added to Power BI. There are
many ways to create such a file system, including using Azure Databricks, HDInsight, AZCopy, or Azure Storage
Explorer. This section shows you a straightforward way to create a file system using Azure Storage Explorer.
This step requires that you install Azure Storage Explorer version 1.6.2 or higher. To install Azure Storage Explorer
for Windows, Macintosh, or Linux, see Azure Storage Explorer.
1. Once you've successfully installed Azure Storage Explorer, On first launch, the Microsoft Azure Storage
Explorer - Connect window is shown. While Storage Explorer provides several ways to connect to storage
accounts, only one way is currently supported for the required setup.
2. In the left pane, locate and expand the storage account you created above.
3. Right-click Blob Containers, and - from the context menu - select Create Blob Container.

4. A text box will appear below the Blob Containers folder. Enter the name powerbi
5. Press Enter when done to create the blob container

In the next section, you grant the Power BI family of services full access to the file system you created.
Grant Power BI permissions to the file system
To grant permissions to the file system, you apply Access Control List (ACL ) settings that grant the Power BI
service access. The first step in doing so is obtaining the Power BI services identity in your tenant. You can view
your Azure Active Directory (AAD ) applications in the Enterprise apps section of the Azure portal.
To find your tenant applications, follow these steps:
1. In the Azure portal, select Azure Active Directory from the left navigation panel.
2. In the Azure Active Directory blade, select Enterprise applications.
3. From the Application Type drop-down menu, select All Applications and then select Apply. A sample
of your tenant applications appears, similar to the following image.

4. In the search bar, type Power and a collection of Object IDs for Power BI and Power Query applications
appear. You'll need all three values in the subsequent steps.
5. Select and copy both Object IDs for Power BI service and Power BI premium from the results of your
search. Be ready to paste those values in subsequent steps.
6. Next, use Azure Storage Explorer to navigate to the powerbi file system you created in the previous
section. Follow the instructions in Managing access section of Set file and directory level permissions using
Azure Storage explorer article.
7. For each of the two Power BI Object IDs collected in step 5, Assign Read, Write, Execute Access and
Default ACLs to your powerbi file system.

8. For the Power Query Online Object ID collected in step 4, Assign Write, Execute Access and Default
ACLs to your powerbi file system.
9. In addition, for the Other, Assign Execute Access and Default ACLs as well.
Connect your Azure Data Lake Storage Gen2 to Power BI
Once you've set up your Azure Data Lake Storage Gen2 account in the Azure portal, you connect it to Power BI in
the Power BI admin portal. You also manage Power BI dataflow storage in the Dataflow storage settings
section of the Power BI admin portal. For guidance on launching and basic use, see How to get to the admin
portal for detailed information.
You connect your Azure Data Lake Storage Gen2 account with the following steps:
1. Navigate to the Dataflow settings tab of the Power BI admin portal

2. Select the Connect your Azure Data Lake Storage Gen2 Preview button. The following window
appears.
3. Provide the Subscription ID of the Storage Account.
4. Provide the Resource Group name in which the storage account was created.
5. Provide the Storage Account name.
6. Select Connect.
Once those steps are successfully completed, your Azure Data Lake Storage Gen2 account is connected to Power
BI.

NOTE
To configure a connection to Azure Data Lake Storage Gen2 in the Power BI admin portal, you must have Global
Administrator permissions. However, Global Administrators cannot connect external storage in the admin portal.

Next you need to enable people in your organization to configure their workspaces, which enables them to use
this storage account for dataflow definition and data storage. Let's do that in the next section.

Allow admins to assign workspaces

By default, dataflow definition and data files are stored in the storage provided by Power BI. To access dataflow
files in your own storage account, workspace admins must first configure the workspace to allow assignment and
storage of dataflows in the new storage account. Before a workspace admin can configure dataflow storage
settings, the admin must be granted storage assignment permissions in the Power BI admin portal.
To grant storage assignment permissions, go to the Dataflow settings (Preview) tab in the Power BI admin
portal. There is a radio button to Allow workspace admins to assign workspaces to this storage account which
must be set to allow. Once you enable that slider, select the Apply button for the change to take effect.
That's it. The Power BI workspace admins can now assign workflows to the file system you created.

Considerations and limitations

This feature is a preview feature, and its behavior may change as it approaches release. There are a few
considerations and limitations to keep in mind when working with your dataflow storage:
Once a dataflow storage location is configured, it cannot be changed.
Only owners of a dataflow stored in Azure Data Lake Storage Gen2 can access its data by default. To authorize
additional people to the dataflows stored in Azure, you must add them to the dataflow’s CDM folder
Creating dataflows with linked entities is only possible when they are stored in the same storage account
On-premises data sources, in Power BI shared capacities, are not supported in dataflows stored in your
organization’s data lake
There are also a few known issues, as described in this section.
Power BI Desktop customers cannot access dataflows stored in an Azure Data Lake Storage Account unless
they are the owner of the dataflow, or have been authorized to the CDM folder in the lake. The scenario is as
follows:
1. Anna has created a new app workspace and configured it to store dataflows in the organization’s data lake.
2. Ben, who is also a member of the workspace Anna created, would like to leverage Power BI Desktop and the
dataflow connector to get data from the Dataflow Anna created.
3. Ben receives an error similar to the following image, because he was not authorized to the dataflow’s CDM
folder in the lake
Common questions and answers include the following:
Question: What if I had previously created dataflows in a workspace and would like to change their storage
location?
Answer: You cannot change the storage location of a dataflow after it was created.
Question: When can I change the dataflow storage location of a workspace?
Answer: Changing the dataflow storage location of a workspace is only allowed if the workspace does not
contain any dataflows.
Next steps
This article provided guidance on how to connect an Azure Data Lake Gen2 for dataflow storage. For additional
information, take a look at the following articles:
For more information about dataflows, CDM, and Azure Data Lake Storage Gen2, take a look at the following
articles:
Dataflows and Azure Data Lake integration (Preview )
Configure workspace dataflow settings (Preview )
Add a CDM folder to Power BI as a dataflow (Preview )
For information about dataflows overall, check out these articles:
Create and use dataflows in Power BI
Using computed entities on Power BI Premium
Using dataflows with on-premises data sources
Developer resources for Power BI dataflows
For more information about Azure storage, you can read these articles:
Azure Storage security guide
For more information about the Common Data Model, you can read its overview article:
Common Data Model - overview
CDM folders
CDM model file definition
And you can always try asking questions of the Power BI Community.
 Configure workspace dataflow settings (Preview)
4/1/2019 • 4 minutes to read • Edit Online

With Power BI and dataflows, you can store a workspace's dataflow definition file and data files in your Azure
Data Lake Storage Gen2 account. Workspaces administrators can configure Power BI to do so, and this article
walks through the steps necessary to get there.
Before you can configure a workspace’s dataflow storage location, your company's global administrator must
connect your organization’s storage account to Power BI, and enable storage assignment permissions to that
storage account. Connect Azure Data Lake Storage Gen2 for dataflow storage (Preview )
There are two ways to configure the workspace dataflow storage settings:
During creation of the workspace
By editing an existing workspace
We'll take a look at each in the following sections.

IMPORTANT
The workspace dataflow storage setting can only be changed if the workspace doesn't contain any dataflows. Also, this
feature is only available in the new workspace experience. You can learn more about new workspace in the Create the new
workspaces (preview) in Power BI article.

Create a new workspace, configure its dataflow storage

To create a new app workspace in the Power BI service, select Workspaces > Create app workspace.
In the Create an app workspace dialog, a yellow box may appear that's titled Preview improved workspaces. In
that area select Try now.

In the dialog that appears, you can give your new workspace a unique name. Don't select Save yet, since you
need to make advanced settings.

Next, expand the Advanced area of the Create an app workspace dialog, where you can turn on the Dataflow
storage (preview) setting.)
Select Save to create your new workspace. Any new dataflow created in this workspace now stores its definition
file (its Model.json file) and data in your organization's Azure Data Lake Storage Gen2 account.

Update dataflow storage for an existing workspace

Alternatively to creating a new workspace, you can update an existing workspace to store the definition file and
data in your organization's Azure Data Lake Storage Gen2 account. Remember that the dataflow sotrage setting
can only be changed if the workspace doesn't already contain a dataflow.
To edit an app workspace, select the elipsis (...) then select Edit workspace.

In the Edit workspace window that appears, expand Advanced, then turn the Dataflow storage (preview)
setting to On.
Then select Save, and any new dataflow created in that workspace stores its definition file and data in your
organization's Azure Data Lake Storage Gen2 account.

Get the URI of stored dataflow files

Once you create a dataflow in a workspace that's assigned to your organization’s Azure Data Lake account, you
can access its definition and data files directly. Their location is available in the Dataflow settings page. To get
there, follow these steps:
Select the ellipsis (...) next to a dataflow listed under Dataflows in the workspace. In the menu that appears,
select Settings.
In the information that's displayed, the dataflow's CDM foloder location appears under Dataflow Storage
location, as shown in the following image.

NOTE
Power BI configures the dataflow owner with reader permissions to the CDM folder where dataflow files are stored. Granting
access to other people or services to the dataflow storage location requires the owner of the storage account to grant
access in Azure.

Considerations and limitations

Certain dataflow features aren't supported when dataflow storage is in Azure Data Lake Storage Gen2:
Power BI Pro, Premium and Embedded workspaces:
The linked entities feature is only supported among workspaces in the same storage account
Workspace permissions do not apply to dataflows stored in Azure Data Lake Storage Gen2; only the owner of
 the dataflow can access it.
Otherwise, all data prep features are the same as for dataflows stored in Power BI storage
There are some additional considerations as well, described in the following list:
Once a dataflow storage location is configured, it cannot be changed.
Only the owner of a dataflow stored in Azure Data Lake Storage Gen2 can access its data.
On-premises data sources, in Power BI Shared capacities, are not supported in dataflows stored in your
organization’s Azure Data Lake Storage Gen2.
Power BI Desktop customers cannot access dataflows stored in Azure Data Lake Storage Gen2 account, unless
they are the owner of the dataflow. Consider the following situation:
1. Anna creates a new app workspace and configures it to store dataflows in the organization’s data lake.
2. Ben, who is also a member of the workspace Anna created, wants to use Power BI Desktop and the
dataflow connector to get data from the dataflow Anna created.
3. Ben receives an error because he was not added as an authorized user to the dataflow’s CDM folder in the
data lake.

Next steps
This article provided guidance on how to configure workspace storage for dataflows. For additional information,
take a look at the following articles:
For more information about dataflows, CDM, and Azure Data Lake Storage Gen2, take a look at the following
articles:
Dataflows and Azure Data Lake integration (Preview )
Add a CDM folder to Power BI as a dataflow (Preview )
Connect Azure Data Lake Storage Gen2 for dataflow storage (Preview )
For information about dataflows overall, check out these articles:
Create and use dataflows in Power BI
Using computed entities on Power BI Premium (Preview )
Using dataflows with on-premises data sources (Preview )
Developer resources for Power BI dataflows (Preview )
For more information about Azure storage, you can read these articles:
 Azure Storage security guide
Get started with github samples from Azure Data Services
For more information about the Common Data Model, you can read its overview article:
Common Data Model - overview
CDM folders
CDM model file definition
And you can always try asking questions of the Power BI Community.
 Add a CDM folder to Power BI as a dataflow
(Preview)
4/1/2019 • 4 minutes to read • Edit Online

In Power BI, you can add Common Data Model (CDM ) folders stored in your organization's Azure Data Lake
Store Gen2 as dataflows. And once you create a dataflow from a CDM folder, you can use Power BI Desktop
and the Power BI service to create datasets, reports, dashboards, and apps that are based on the data you put
into CDM folders.

There are a few requirements for creating dataflows from CDM folders, as the following list describes:
Creating dataflows from CDM folders is only available in the new workspace experience.
Adding a CDM folder to Power BI requires the user adding the folder to have authorization for the CDM
folder and its files.
You must be granted read and execute permissions, on all files and folders in the CDM folder, to add them to
Power BI.
The following sections describe how to create a dataflow from a CDM folder.

Create a dataflow from a CDM folder

To get started creating a dataflow from a CDM folder, launch the Power BI service and select an app
workspace from the left navigation pane. You can also create a new workspace, in which you can create your new
dataflow.
In the screen that appears, select to Create and attach as shown in the following image.

The screen that appears next lets you name your dataflow, provide a description of the dataflow, and provide the
path to the CDM folder in your organization's Azure Data Lake Gen2 account. Read the section in the article that
describes how to get your CDM folder path.
Once you've provided the information, select Create and attach to create the dataflow.
Dataflows from CDM folders are marked with external icon when displayed in Power BI. In the next section, we
describe differences between standard dataflows, and dataflows created from CDM folders.
Once permissions are properly set, as described previously in this article, you can connect to your dataflow in
Power BI Desktop.

Considerations and limitations

When working with permissions to a dataflow created from a CDM folder, the process is similar to external
datasources in Power BI. Permissions are managed at the data source, and not from within Power BI. Permissions
must be set appropriately on the data source itself, such as a dataflow created from a CDM folder, in order to
work properly with Power BI.
The following lists help clarify how dataflows from CDM folders operate with Power BI.
Power BI Pro, Premium and Embedded workspaces:
Dataflows from CDM folders cannot be edited
Permissions to read a dataflow created from a CDM folder is managed by the owner of the CDM folder, and
not by Power BI
Power BI Desktop:
Only users who are authorized to both the workspace in which the dataflow was created, and the CDM folder,
can access its data from the Power BI Dataflows connector
There are some additional considerations as well, described in the following list:
Creating dataflows from CDM folders is only available in the new workspace experience
Linked entities is not available for dataflows created from CDM folders
Power BI Desktop customers cannot access dataflows stored in Azure Data Lake Storage Gen2 account, unless
they are the owner of the dataflow, or they have been explicitly authorized to the dataflow’s CDM folder. Consider
the following situation:
1. Anna creates a new app workspace and configures it to store dataflows from a CDM folder.
2. Ben, who is also a member of the workspace Anna created, wants to use Power BI Desktop and the
dataflow connector to get data from the dataflow Anna created.
3. Ben receives an error because he was not added as an authorized user to the dataflow’s CDM folder in the
data lake.

To resolve this issue, Ben must be granted reader permissions to the CDM Folder and its files. You can learn more
about how to grant access to the CDM Folder in this article.

Next Steps
This article provided guidance on how to configure workspace storage for dataflows. For additional information,
take a look at the following articles:
For more information about dataflows, CDM, and Azure Data Lake Storage Gen2, take a look at the following
articles:
Dataflows and Azure Data Lake integration (Preview )
Configure workspace dataflow settings (Preview )
Connect Azure Data Lake Storage Gen2 for dataflow storage (Preview )
For information about dataflows overall, check out these articles:
Create and use dataflows in Power BI
Using computed entities on Power BI Premium
Using dataflows with on-premises data sources
Developer resources for Power BI dataflows
For more information about Azure storage, you can read these articles:
Azure Storage security guide
Configuring scheduled refresh
Get started with github samples from Azure Data Services
For more information about the Common Data Model, you can read its overview article:
Common Data Model - overview
 CDM folders
CDM model file definition
And you can always try asking questions of the Power BI Community.
 Azure Machine Learning integration in Power BI
(Preview)
4/1/2019 • 4 minutes to read • Edit Online

Numerous organizations use Machine Learning models for better insights and predictions about their business.
The ability to visualize and invoke insights from these models, in your reports and dashboards and other analytics,
can help disseminate these insights to the business users who need it the most. Power BI now makes it simple to
incorporate the insights from models hosted on the Azure Machine Learning service, using straightforward point-
and-click gestures.
To use this capability, a data scientist can simply grant access to the Azure ML model to the BI analyst using the
Azure portal. Then, at the start of each session, Power Query discovers all the Azure ML models to which the user
has access and exposes them as dynamic Power Query functions. The user can then invoke those functions by
accessing them from the ribbon in Power Query Editor, or by invoking the M function directly. Power BI also
automatically batches the access requests when invoking the Azure ML model for a set of rows to achieve better
performance.
This functionality is currently only supported for Power BI dataflows, and for Power Query online in the Power BI
service.
To learn more about dataflows, see Self-service data prep in Power BI.
To learn more about Azure Machine Learning, please see:
Overview: What is Azure Machine Learning service?
Quick Starts and Tutorials for Azure Machine Learning: Azure Machine Learning Documentation

Granting access to the Azure ML model to a Power BI user

To access an Azure ML model from Power BI, the user must have Read access to the Azure subscription. In
addition:
For Machine Learning Studio models, Read access to Machine Learning Studio web service
For Machine Learning Service models, Read access to the Machine Learning service workspace
The steps in this article describe how to grant a Power BI user access to a model hosted on the Azure ML service,
so they can access this model as a Power Query function. For further details, please see Manage access using
RBAC and the Azure portal.
1. Sign in to the Azure portal.
2. Go to the Subscriptions page. You can find the Subscriptions page through the All Services list in the
left navigation menu of the Azure portal.
3. Select your subscription.

4. Select Access Control (IAM ), and then select the Add button.

5. Select Reader as the Role. Select the Power BI user to whom you wish to grant access to the Azure ML
 model.

6. Select Save.
7. Repeat steps three through six to grant Reader access to the user for the specific Machine Learning Studio
web service, or the Machine Learning service workspace hosting the model.

Schema discovery for Machine Learning Service models

Data scientists primarily use Python to develop, and even deploy, their machine learning models for the Machine
Learning Service. Unlike the Machine Learning Studio, which helps automate the task of creating a schema file for
the model, in the case of the Machine Learning Service, the data scientist must explicitly generate the schema file
using Python.
This schema file must be included in the

Invoking the Azure ML model in Power BI

You can invoke any Azure ML model to which you have been granted access, directly from the Power Query
Editor in your dataflow. To access the Azure ML models, select the Edit button for the entity that you want to
enrich with insights from your Azure ML model, as shown in the following image.

Selecting the Edit button opens the Power Query Editor for the entities in your dataflow.
Select the AI Insights button in the ribbon, and then select the Azure Machine Learning Models folder from the
left navigation menu. All the Azure ML models to which you have access are listed here as Power Query functions.
Also, the input parameters for the Azure ML model are automatically mapped as parameters of the corresponding
Power Query function.
To invoke an Azure ML model, you can specify any of the selected entity's columns as an input from the drop-
down. You can also specify a constant value to be used as an input by toggling the column icon to the left of the
input dialog.

Select Invoke to view the preview of the Azure ML model's output as a new column in the entity table. You will
also see the model invocation as an applied step for the query.
If the model returns multiple output parameters, they are grouped together as a record in the output column. You
can expand the column to produce individual output parameters in separate columns.

Once you save your dataflow, the model is automatically invoked when the dataflow is refreshed, for any new or
updated rows in the entity table.

Next Steps
This article provided an overview of integrating Machine Learning into the Power BI service. The following
articles might also be interesting and useful.
Tutorial: Invoke a Machine Learning Studio model in Power BI (Preview )
Tutorial: Using Cognitive Services in Power BI
Cognitive Services in Power BI (Preview )
For more information about dataflows, you can read these articles:
Create and use dataflows in Power BI
Using computed entities on Power BI Premium
Using dataflows with on-premises data sources
Developer resources for Power BI dataflows
Dataflows and Azure Data Lake integration (Preview )
 Cognitive Services in Power BI (Preview)
4/1/2019 • 5 minutes to read • Edit Online

With the Cognitive Services in Power BI, you can apply different algorithms from Azure Cognitive Services to
enrich your data in the self-service data prep for Dataflows.
The services that are supported today are Sentiment Analysis, Key Phrase Extraction, Language Detection, and
Image Tagging. The transformations are executed on the Power BI Service and do not require an Azure Cognitive
Services subscription. This feature requires Power BI Premium.

Enabling AI features
Cognitive services are supported for Premium capacity nodes EM2, A2, or P1 and above. A separate AI workload
on the capacity is used to run cognitive services. During public preview, this workload is disabled by default.
Before using cognitive services in Power BI, the AI workload needs to be enabled in the capacity settings of the
admin portal. You can turn on the AI workload in the workloads section, and define the maximum amount of
memory you would like this workload to consume. The recommended memory limit is 20%. Exceeding this limit
causes the query to slow down.

Getting started with Cognitive Services in Power BI

Cognitive Services transforms are part of the Self-Service Data Prep for dataflows. To enrich your data with
Cognitive Services, start by editing a dataflow.
Select the AI Insights button in the top ribbon of Power Query Editor.

In the pop-up window, select the function you want to use and the data you want to transform. In this example, I'm
scoring the sentiment of a column that contains review text.
Cultureinfo is an optional input to specify the language of the text. This field is expecting an ISO code. You can
use a column as input for Cultureinfo, or a static field. In this example, the language is specified as English (en) for
the whole column. If you leave this field blank, Power BI automatically detects the language before applying the
function. Next, select Invoke.

After invoking the function, the result is added as a new column to the table. The transformation is also added as
an applied step in the query.
If the function returns multiple output fields, invoking the function adds a new column with a record of the
multiple output fields.
Use the expand option to add one or both values as columns to your data.

Available functions
This section describes the available functions in Cognitive Services in Power BI.
Detect Language
The language detection function evaluates text input, and for each field, returns the language name and ISO
identifier. This function is useful for data columns that collect arbitrary text, where language is unknown. The
function expects data in text format as input.
Text Analytics recognizes up to 120 languages. For more information, see supported languages.
Extract Key Phrases
The Key Phrase Extraction function evaluates unstructured text, and for each text field, returns a list of key
phrases. The function requires a text field as input, and accepts an optional input for Cultureinfo. (See the
Getting Started section earlier in this article).
Key phrase extraction works best when you give it bigger chunks of text to work on. This is opposite from
sentiment analysis, which performs better on smaller blocks of text. To get the best results from both operations,
consider restructuring the inputs accordingly.
Score Sentiment
The Score Sentiment function evaluates text input and returns a sentiment score for each document, ranging
from 0 (negative) to 1 (positive). This function is useful for detecting positive and negative sentiment in social
media, customer reviews, and discussion forums.
Text Analytics uses a machine learning classification algorithm to generate a sentiment score between 0 and 1.
Scores closer to 1 indicate positive sentiment, scores closer to 0 indicate negative sentiment. The model is pre-
trained with an extensive body of text with sentiment associations. Currently, it's not possible to provide your own
training data. The model uses a combination of techniques during text analysis, including text processing, part-of-
speech analysis, word placement, and word associations. For more information about the algorithm, see
Introducing Text Analytics.
Sentiment analysis is performed on the entire input field, as opposed to extracting sentiment for a particular entity
in the text. In practice, there's a tendency for scoring accuracy to improve when documents contain one or two
sentences rather than a large block of text. During an objectivity assessment phase, the model determines whether
an input field as a whole is objective or contains sentiment. An input field that is mostly objective does not
progress to the sentiment detection phrase, resulting in a .50 score, with no further processing. For input fields
continuing in the pipeline, the next phase generates a score above or below .50, depending on the degree of
sentiment detected in the input field.
Currently, Sentiment Analysis supports English, German, Spanish, and French. Other languages are in preview.
For more information, see Supported languages.
Tag Images
The Tag Images function returns tags based on more than 2,000 recognizable objects, living beings, scenery, and
actions. When tags are ambiguous or not common knowledge, the output provides 'hints' to clarify the meaning
of the tag in context of a known setting. Tags are not organized as a taxonomy and no inheritance hierarchies exist.
A collection of content tags forms the foundation for an image 'description' displayed as human readable
language formatted in complete sentences.
After uploading an image or specifying an image URL, Computer Vision algorithms output tags based on the
objects, living beings, and actions identified in the image. Tagging is not limited to the main subject, such as a
person in the foreground, but also includes the setting (indoor or outdoor), furniture, tools, plants, animals,
accessories, gadgets, and so on.
This function requires an image URL or abase-64 field as input. At this time, image tagging supports English,
Spanish, Japanese, Portuguese, and Simplified Chinese. For more information, see Supported languages.

Next Steps
This article provided an overview of using Cognitive Services with Power BI service. The following articles might
also be interesting and useful.
Tutorial: Invoke a Machine Learning Studio model in Power BI (Preview )
Azure Machine Learning integration in Power BI (Preview )
 Tutorial: Using Cognitive Services in Power BI
For more information about dataflows, you can read these articles:
Create and use dataflows in Power BI
Using computed entities on Power BI Premium
Using dataflows with on-premises data sources
Developer resources for Power BI dataflows
Dataflows and Azure Data Lake integration (Preview )
 Automated Machine Learning in Power BI (Preview)
4/1/2019 • 16 minutes to read • Edit Online

Automated machine learning (AutoML ) for dataflows enables business analysts to train, validate and invoke
Machine Learning models directly in Power BI. It includes a simple experience for creating a new ML model where
analysts can use their dataflows to specify the input data for training the model. The service automatically extracts
the most relevant features, selects an appropriate algorithm and tunes and validates the ML model. After a model
is trained, Power BI automatically generates a report that includes the results of validation that explains the
performance and results to analysts. The model can then be invoked on any new or updated data within the
dataflow.

Automated machine learning is available for dataflows that are hosted on Power BI Premium and Embedded
capacities only. In this preview, AutoML enables you to train machine learning models for Binary Prediction,
Classification, and Regression models.

Working with AutoML

Power BI dataflows offer self-serve data prep for big data. AutoML enables you to leverage your data prep effort
for building machine learning models, right within Power BI.
AutoML in Power BI enables data analysts to use dataflows to build machine learning models with a simplified
experience, using just Power BI skills. Most of the data science behind the creation of the ML models is automated
by Power BI, with guardrails to ensure that the model produced has good quality, and visibility to provide you with
full insight into the process used to create your ML model.
AutoML supports the creation of Binary Prediction, Classification, and Regression models for dataflows. These
are types of supervised machine learning models, which means that they learn from the known outcomes of past
observations to predict the outcomes of other observations. The input dataset for training an AutoML model is a
set of records that are labeled with the known outcomes.
AutoML in Power BI integrates automated ML from the Azure Machine Learning service to create your ML
models. However, you don't need an Azure subscription to use AutoML in Power BI. The process of training and
hosting the ML models is managed entirely by the Power BI service.
After an ML model is trained, AutoML automatically generates a Power BI report that explains the likely
performance of your ML model. AutoML emphasizes explainability, by highlighting the key influencers among
your inputs that influence the predictions returned by your model. The report also includes key metrics for the
model, depending on the ML model type.
Other pages of the generated report show the statistical summary of the model and the training details. The
statistical summary is of interest to users who would like to see the standard data science measures of
performance for the model. The training details summarize all the iterations that were run to create your model,
with the associated modeling parameters. It also describes how each input was used to create the ML model.
You can then apply your ML model to your data for scoring. When the dataflow is refreshed, the predictions from
your ML model are automatically applied to your data. Power BI also includes an individualized explanation for
each specific prediction score that the ML model produces.

Creating a machine learning model

This section describes how to create an AutoML learning model.
Data prep for creating an ML model
To create a machine learning model in Power BI, you must first create a dataflow for the data with the historical
outcome information, which is used for training the ML model. For details on configuring your dataflow, see Self-
service data prep in Power BI.
In the current release, Power BI uses data from only a single entity to train the ML model. So if your historical data
consists of multiple entities, you must manually join the data into a single dataflow entity. You should also add
calculated columns for any business metrics that may be strong predictors for the outcome you're trying to predict.
AutoML has specific data requirements for training a machine learning model. These requirements are described
in sections below, based on respective model types.
Configuring the ML model inputs
To create an AutoML model, select the ML icon in the Actions column of the dataflow entity with the historical
data, and select Add a machine learning model.

A simplified experience is launched, consisting of a wizard that guides you through the process of creating the ML
model. The wizard includes the following simple steps.
1. Select the entity with the historical outcome data, and the field for which you want a prediction
2. Choose a model type based on the type of prediction you'd like to see
3. Select the inputs you want the model to use as predictive signals
4. Name your model and save your configuration
The historical outcome field identifies the label attribute for training the ML model, shown in the following image.

When you specify the historical outcome field, AutoML analyzes the label data to identify the types of ML models
that can be trained for that data and suggests the most likely ML model type that can be trained.

NOTE
Some model types may not be supported for the data that you have selected.

AutoML also analyzes all the fields in the selected entity to suggest the inputs that can be used for training the ML
model. This process is approximate and is based on statistical analysis, so you should review the inputs used. Any
inputs that are dependent on the historical outcome field (or the label field) should not be used for training the ML
model, since they will affect its performance.
In the final step, you can name the model and save its settings.
At this stage, you are prompted to refresh the dataflow, which begins the training process for the ML model.
ML model training
Training of AutoML models is a part of the dataflow refresh. AutoML first prepares your data for training.
AutoML splits the historical data you provide into a training and testing datasets. The test dataset is a holdout set
that is used for validating the model performance after training. These are realized as Training and Testing
entities in the dataflow. AutoML uses cross-validation for the model validation.
Next, each input field is analyzed and imputation is applied, which replaces any missing values with substituted
values. A couple of different imputation strategies are used by AutoML. Then, any required sampling and
normalization are applied to your data.
AutoML applies several transformations are each selected input field based on its data type, and its statistical
properties. AutoML uses these transformations to extract features for use in training your ML model.
The training process for AutoML models consists of up to 50 iterations with different modeling algorithms and
hyperparameter settings to find the model with the best performance. The performance of each of these models is
assessed by validation with the holdout test dataset. During this training step, AutoML creates several pipelines for
training and validation of these iterations. The process of assessing the performance of the models can take time,
anywhere from several minutes to a couple of hours, depending on the size of your dataset and the dedicated
capacity resources available.
In some cases, the final model generated may use ensemble learning, where multiple models are used to deliver
better predictive performance.
AutoML model explainability
After the model has been trained, AutoML analyzes the relationship between the input features and the model
output. It assesses the magnitude and direction of change to the model output for the holdout test dataset for each
input feature. This is known as the feature importance.
AutoML model report
AutoML generates a Power BI report that summarizes the performance of the model during validation, along with
the global feature importance. The report summarizes the results from applying the ML model to the holdout test
data and comparing the predictions with the known outcome values.
You can review the model report to understand its performance. You can also validate that the key influencers of
the model align with the business insights about the known outcomes.
The charts and measures used to describe the model performance in the report depend on the model type. These
performance charts and measures are described in the following sections.
Additional pages in the report may describe statistical measures about the model from a data science perspective.
For instance, the Binary Prediction report includes a gain chart and the ROC curve for the model.
The reports also include a Training Details page that includes a description of how the model was trained, and
includes a chart describing the model performance over each of the iterations runs.
Another section on this page describes how the imputation method used for filling missing values for the input
fields, as well as how each input field was transformed to extract the features used in the model. It also includes the
parameters used by the final model.

If the model produced uses ensemble learning, then the Training Details page also includes a section describing
the weight of each constituent model in the ensemble, as well as its parameters.
Applying the AutoML model
If you're satisfied with the performance of the ML model created, you can apply it to new or updated data when
your dataflow is refreshed. You can do this from the model report, by selecting the Apply button in the top-right
corner.
To apply the ML model, you must specify the name of the entity to which it must be applied, and a prefix for the
columns that will be added to this entity for the model output. The default prefix for the column names is the
model name. The Apply function may include additional parameters specific to the model type.
Applying the ML model creates a new dataflow entity with the suffix enriched <model_name>. For instance, if
you apply the PurchaseIntent model to the OnlineShoppers entity, the output will generate the OnlineShoppers
enriched PurchaseIntent.
Currently, the output entity cannot be used to preview the ML model results in the Power Query editor. The output
columns always show null as the result. To view the results, a second output entity with the suffix enriched
<model_name> Preview is created when the model is applied.
You must refresh the dataflow, to preview the results in the Query Editor.
When you apply the model, AutoML always keeps your predictions up-to-date when the dataflow is refreshed.
AutoML also includes an individualized explanation for each row that it scores in the output entity.
To use the insights and predictions from the ML model in a Power BI report, you can connect to the output entity
from Power BI Desktop using the dataflows connector.

Binary Prediction Models

Binary Prediction models, more formally known as binary classification models, are used to classify a dataset
into two groups. They're used to predict events that can have a binary outcome, such as whether a sales
opportunity will convert, whether an account will churn, whether an invoice will be paid on time; whether a
transaction is fraudulent, and so on.
Since the outcome is binary, Power BI expects the label for a binary prediction model to be a Boolean, with known
outcomes being labeled true or false. For instance, in a sales opportunity conversion model, sales opportunities
that have been won are labeled true, those that have been lost are labeled false, and the open sales opportunities
are labeled null.
The output of a Binary Prediction model is a probability score, which identifies the likelihood that the outcome
corresponding to the label value being true will be achieved.
Training a Binary Prediction model
To create a Binary Prediction model, the input entity containing your training data must have a Boolean field as the
historical outcome field to identify the past known outcomes.
Pre-requisites:
A Boolean field must be used as the historical outcome field
A minimum of 50 rows of historical data is required for each class of outcomes
In general, if the past outcomes are identified by fields of a different data type, you can add a calculated column to
transform these into a Boolean using Power Query.
The process of creation for a Binary Prediction model follows the same steps as other AutoML models, described
in the section Configuring the ML model inputs above.
Binary Prediction model report
The Binary Prediction model produces as an output a probability that a record will achieve the outcome defined by
the Boolean label value as True. The report includes a slicer for the probability threshold, which influences how the
scores above and below the probability threshold are interpreted.
The report describes the performance of the model in terms of True Positives, False Positives, True Negatives and
False Negatives. True Positives and True Negatives are correctly predicted outcomes for the two classes in the
outcome data. False Positives are outcomes that had the actual Boolean label of value False but were predicted as
True. Conversely, False Negatives are outcomes where the actual Boolean label value was True but were predicted
as False.
Measures, such as Precision and Recall, describe the effect of the probability threshold on the predicted outcomes.
You can use the probability threshold slicer to select a threshold that achieves a balanced compromise between
Precision and Recall.

The Accuracy Report page of the model report includes the Cumulative Gains chart and the ROC curve for the
model. These are statistical measures of model performance. The reports include descriptions of the charts shown.
Applying a Binary Prediction model
To apply a Binary Prediction model, you must specify the entity with the data to which you want to apply the
predictions from the ML model. Other parameters include the output column name prefix and the probability
threshold for classifying the predicted outcome.

When a Binary Prediction model is applied, it adds three output columns to the enriched output entity. These are
the PredictionScore, PredictionOutcome and PredictionExplanation. The column names in the entity have
the prefix specified when the model is applied.
The PredictionOutcome column contains the predicted outcome label. Records with probabilities exceeding the
threshold are predicted as likely to achieve the outcome, and those below are predicted as unlikely to achieve the
outcome.
The PredictionExplanation column contains an explanation with the specific influence that the input features had
on the PredictionScore. This is a JSON formatted collection of weights of the input features for the prediction.

Classification models
Classification models are used to classify a dataset into multiple groups or classes. They're used to predict events
that can have one of multiple possible outcomes, such as whether a customer is likely to have a very high, high,
medium, or low Lifetime Value; whether the risk for default is High, Moderate, Low or Very Low; and so on.
The output of a Classification model is a probability score, which identifies the likelihood that a record will achieve
the criteria for a given class.
Training a Classification model
The input entity containing your training data for a Classification model must have a string or numeric field as the
historical outcome field, which identifies the past known outcomes.
Pre-requisites:
A minimum of 50 rows of historical data is required for each class of outcomes
The process of creation for a Classification model follows the same steps as other AutoML models, described in
the section Configuring the ML model inputs above.
Classification model report
The Classification model report is produced by applying the ML model to the holdout test data and comparing the
predicted class for a record with the actual known class.
The model report includes a chart that includes the breakdown of the correctly and incorrectly classified records
for each known class.

A further class-specific drilldown enables an analysis of how the predictions for a known class are distributed. This
includes the other classes in which records of that known class are likely to be misclassified.
The model explanation in the report also includes the top predictors for each class.
The Classification model report also includes a Training Details page similar to the pages for other model types, as
described in the section AutoML model report earlier in this article.
Applying a classification model
To apply a Classification ML model, you must specify the entity with the input data and the output column name
prefix.
When a Classification model is applied, it adds three output columns to the enriched output entity. These are the
PredictionScore, PredictionClass and PredictionExplanation. The column names in the entity have the prefix
specified when the model is applied.
The PredictionClass column contains the most likely predicted class for the record. The PredictionScore column
contains the list of probability scores for the record for each possible class.
The PredictionExplanation column contains an explanation with the specific influence that the input features had
on the PredictionScore. This is a JSON formatted collection of weights of the input features for the prediction.

Regression models
Regression models are used to predict a value, such as the revenue likely to be realized from a sales deal, the
lifetime value of an account, the amount of a receivable invoice that is likely to be paid, the date on which an
invoice may be paid, and so on.
The output of a Regression model is the predicted value.
Training a Regression model
The input entity containing the training data for a Regression model must have a numeric field as the historical
outcome field, which identifies the past known outcome values.
Pre-requisites:
A minimum of 100 rows of historical data is required for a Regression model
The process of creation for a Regression model follows the same steps as other AutoML models, described in the
section Configuring the ML model inputs above.
Regression model report
Like the other AutoML model reports, the Regression report is based on the results from applying the model to
the holdout test data.
The model report includes a chart that compares the predicted values to the actual value. In this chart, the distance
from the diagonal indicates the error in the prediction.
The residual error chart shows the distribution of the percentage of average error for different values in the
holdout test dataset. The horizontal axis represents the mean of the actual value for the group, with the size of the
bubble showing the frequency or count of values in that range. The vertical axis is the average residual error.

The Regression model report also includes a Training Details page like the reports for other model types, as
described in the section AutoML model report above.
Applying a regression model
To apply a Regression ML model, you must specify the entity with the input data and the output column name
prefix.

When a Regression model is applied, it adds two output columns to the enriched output entity. These are the
PredictionValue, and PredictionExplanation. The column names in the entity have the prefix specified when
the model is applied.
The PredictionValue column contains the predicted value for the record based on the input fields. The
PredictionExplanation column contains an explanation with the specific influence that the input features had on
the PredictionValue. This is a JSON formatted collection of weights of the input features.

Next steps
This article provided an overview of Automated Machine Learning for Dataflows in the Power BI service. The
following articles may also be useful.
Tutorial: Build a Machine Learning model in Power BI (Preview )
Tutorial: Using Cognitive Services in Power BI
Tutorial: Invoke a Machine Learning Studio model in Power BI (Preview )
Cognitive Services in Power BI (Preview )
Azure Machine Learning integration in Power BI (Preview )
For more information about dataflows, you can read these articles:
Create and use dataflows in Power BI
Using computed entities on Power BI Premium
Using dataflows with on-premises data sources
Developer resources for Power BI dataflows
Dataflows and Azure Data Lake integration (Preview )
 What are paginated reports in Power BI Premium?
(Preview)
2/28/2019 • 4 minutes to read • Edit Online

Paginated reports, long the standard report format in SQL Server Reporting Services, are now available in the
Power BI service. These reports can be printed or shared. They're called "paginated" because they're formatted to
fit well on a page. They display all the data in a table, even if the table spans multiple pages. They're sometimes
called "pixel perfect" because you can control their report page layout exactly. Paginated reports are based on the
RDL report technology in SQL Server Reporting Services. Report Builder is the standalone tool for authoring
paginated reports.
Paginated reports can have many pages. For example, this report has 563 pages. Each page is laid out exactly,
with one page per invoice and repeating headers and footers.

You can preview your report in Report Builder, then publish it to the Power BI service, http://app.powerbi.com.
You need a Power BI Pro license to publish a report to the service. You can publish and share paginated reports in
your My Workspace or in app workspaces, as long as the workspace is in a Power BI Premium capacity. Also, a
Power BI admin needs to enable paginated reports in the Power BI admin portal.

Create reports in Report Builder

Paginated reports have their own design tool, Report Builder. It's the same tool and the same version you'd use to
create paginated reports for Power BI Report Server or SQL Server Reporting Services (SSRS ). In fact, paginated
reports that you create for SSRS 2016 and 2017 or for Power BI Report Server on-premises, are compatible with
the Power BI service. The Power BI service maintains backwards compatibility so you can move your reports
forward, and you can upgrade any previous-version paginated reports. Not all report features are available at
launch. See Limitations and considerations in this article for details.

Report from a variety of data sources

A single paginated report can have a number of different data sources. It doesn't have an underlying data model,
unlike Power BI reports. For the initial release of paginated reports in the Power BI service, you create embedded
data sources and datasets in the report itself. For now, you can't use shared data sources or shared datasets. You
create reports in Report Builder on your local computer. If a report connects to on-premises data, after you
upload the report to the Power BI service, you need to create a gateway and redirect the data connection. Here
are the data sources you can connect to for the initial release:
Azure SQL Database and Data Warehouse
SQL Server via a gateway
SQL Server Analysis Services via a gateway
More data sources will be coming during the preview period.

Design your report

Create paginated reports with matrix, chart, and free -form layouts
Table reports work well for column-based data. Matrix reports, like cross-tab or PivotTable reports, are good for
summarized data. Chart reports present data in a graphical format, and free-form list reports can present almost
anything else, such as invoices.
You can start with one of the Report Builder wizards. The Table, Matrix, and Chart wizards walk you through
creating the embedded data source connection and embedded dataset. Then you drag and drop fields to create a
dataset query, select a layout and style, and customize your report.
With the Map wizard, you create reports that display aggregated data against a geographic or geometric
background. Map data can be spatial data from a Transact-SQL query or an Environmental Systems Research
Institute, Inc. (ESRI) shapefile. You can also add a Microsoft Bing map tile background.
Add more to your report
Modify your data by filtering, grouping, and sorting data, or by adding formulas or expressions. Add charts,
gauges, sparklines, and indicators to summarize data in a visual format. Use parameters and filters to filter data
for customized views. Embed or reference images and other resources, including external content.
Everything in a paginated report, from the report itself to every text box, image, table, and chart, has an array of
properties you can set to make the report look exactly as you want it.

Creating a report definition

When you design a paginated report, you're really creating a report definition. It doesn't contain the data. It
specifies where to get the data, which data to get, and how to display the data. When you run the report, the
report processor takes the report definition you've specified, retrieves the data, and combines it with the report
layout to generate the report. You upload the report definition to the Power BI service, http://app.powerbi.com,
either to your My Workspace or to a workspace shared with your colleagues. If the report data source is on
premises, after you upload the report, you redirect the data source connection to go through a gateway.

View your paginated report

You view your paginated report in the Power BI service in a browser, and also in the Power BI mobile apps. From
the Power BI service, you can export the report to a number of formats, such as HTML, MHTML, PDF, XML, CSV,
TIFF, Word, and Excel. You can also share it with others.

Limitations and considerations

Here are some other features that aren't supported in the initial release:
Pinning report pages or visuals to Power BI dashboards. You can still pin visualizations to a Power BI
dashboard from an on-premises paginated report on a Power BI Report Server or Reporting Services report
server. See Pin Reporting Services items to Power BI dashboards for more information.
Interactive features such as document maps and show/hide buttons.
Subreports and drillthrough reports.
Subscriptions.
Shared data sources and shared datasets.
Power BI datasets.
Visuals from Power BI reports.
Paginated reports in apps. You can share a paginated report from an app workspace, but you can't include it
when you publish the app from that workspace.

Next steps
Install Report Builder from the Microsoft Download Center
Tutorial: Create a paginated report
Enter data directly in a paginated report
 Paginated reports in Power BI: FAQ (Preview)
2/15/2019 • 8 minutes to read • Edit Online

This article answers frequently asked questions about paginated reports. These reports are highly formatted, pixel-
perfect output optimized for printing or PDF generation. They're called "paginated" because they're formatted to fit
well on multiple pages. Paginated reports are based on the RDL report technology in SQL Server Reporting
Services.
This article answers many common questions people have about paginated reports in Power BI Premium, and
about Report Builder, the standalone tool for authoring paginated reports. You need a Power BI Pro license to
publish a report to the service. You can publish and share paginated reports in your My Workspace or in app
workspaces, as long as the workspace is in a Power BI Premium capacity.

Administration
What size Premium capacity do I need for paginated reports?
The paginated reports workload is available on P1 – P3 SKUs for public preview. You may also use it for test/dev
scenarios with A4 – A6 SKUs.
What is the maximum memory threshold I can put for paginated reports in my capacity?
Currently, you may only reserve 50% of the memory for this workload.
How does user access work for paginated reports?
User access for paginated reports is the same as user access for all other content in the Power BI service
How do I turn on/off my paginated reports workload?
The capacity admin can enable or disable the paginated reports workload in the capacity admin portal page.
How can I monitor usage of paginated reports in my tenant?
The Office 365 audit logs detail usage of this report type under the following events:
View Power BI Report
Delete Power BI report
Create Power BI report
Downloaded Power BI report
The field ReportType has the value “PaginatedReport” to identify paginated as opposed to Power BI reports.
Also, the audit logs provide the following events for paginated reports:
Binded Power BI dataset to gateway
Discover Power BI Datasource
TakeOverDatasource
Can I monitor this workload through the Premium Capacity Monitoring App?
Yes, monitoring is available as a new tab with the same relevant details you have for your Power BI datasets.
Do I need a Pro license to create and publish paginated reports?
Yes. You can't upload reports to the workspace without a Pro license. You may download and try Report Builder
without the Pro license, but not publish the paginated reports you create.
What if I have a paginated report in a workspace and the paginated report workload is turned off?
You receive an error message, and you can't view your report until the workload is turned back on. You can still
delete the report from the workspace.
What is the default memory for each of the Premium SKUs supported for paginated reports?
Default memory in each Premium SKU for paginated reports:
P1/A4: 20% default; 10% minimum
P2/A5: 20% default; 5% minimum
P3/A6: 20% default; 2.5% minimum

General
When should I use a paginated report vs. a Power BI report?
Paginated reports are best for scenarios that require a highly formatted, pixel-perfect output optimized for printing
or PDF generation. A profit and loss statement is a good example of the type of report you would probably want to
create as a paginated report.
Power BI reports are optimized for exploration and interactivity. A sales report where different salespeople want to
slice the data in the same report for their specific region/industry/customer and see how the numbers change
would be best served by a Power BI report.
The documentation says Report Builder is the preferred authoring tool. Can I create paginated reports in SQL
Server Data Tools for Power BI?
Yes, but the Power BI service only allows you to upload a single item at a time, so many of the scenarios authors
use with SQL Server Data Tools (SSDT) aren’t yet supported. See the full list of unsupported features available
later in this FAQ.
What version(s) of Report Builder do you support?
Use the latest version of SQL Server 2016 Report Builder to author and publish your reports to the Power BI
service. Install Report Builder from the Microsoft Download Center.
How do I move existing reports I have saved in SQL Server Reporting Services to Power BI?
You need to download the report from the server, then upload it to Power BI through the portal. There is no
migration tool available at this time, but we’re looking at creating one after we’ve finished public preview and
gotten the right level of feature parity between the products.
Can I open reports and publish directly to the service?
At this point, no. We'll add support for opening reports and publishing them directly to the service from Report
Builder at some point, like you can with Power BI Desktop.
What paginated report features in SSRS aren’t yet supported in Power BI?
Currently, paginated reports don’t support the following items:
Shared data sources
Shared datasets
Subreports
Click-through and drill-through actions
Linked reports
Bookmarks
Bing map layers
Custom fonts
You get an error message if you try to upload a file that has an unsupported feature in the Power BI service, other
than toggle/sort.
What data sources do you support currently for paginated reports?
We support Azure SQL Database, SQL Server and both SQL Server Analysis Services (SSAS ) tabular (DAX) and
multidimensional (MDX) models using the on-premises Gateway.
When accessing SSAS through the Gateway, the user whose credentials are stored needs elevated permissions in
SSAS to work through the Gateway.
What authentication methods do you support?
Currently you need to store a user name and password with the data source in the portal or gateway. Additional
authentication methods to support things like row -level security are coming later in the preview.
Can I use a Power BI dataset as a data source for my paginated report?
Not yet, but this support is planned soon.
Can I use stored procedures through the Gateway?
You can use a stored procedure through the Gateway, but you may see issues in certain scenarios if stored
procedure has parameters.
What export formats are available for my report in the Power BI service?
You can export to Microsoft Excel, Microsoft Word, Microsoft PowerPoint, PDF, .CSV, XML, and MHTML.
Can I print paginated reports?
Yes, printing is available for Paginated Reports, including a new and improved print preview experience.
Are e -mail subscriptions available yet for paginated reports?
No, e-mail subscriptions are coming soon, however.
What features from SSRS will you be supporting in the Power BI service?
Our plan is to provide feature parity for most scenarios, but certain things about SSRS and Power BI may not
make sense to try to change to fit existing SSRS patterns. For example, the different permission models in Power
BI can't be mapped back to SSRS. We will be looking for feedback from customers and partners to make those
types of decisions.
Can I run custom code in my report?
Yes, we support the ability to run code in your reports as you can in SSRS.
Does this mean SSRS is going away?
Not at all. This new offering offers customers a cloud-based option for their paginated reports.
Can I use Power BI embedded to embed my paginated reports into an app I’m hosting?
We plan to support this scenario with the existing Power BI APIs, but we don’t yet have a timeframe on when this
scenario will be available.
Can I drill through from a Power BI report to a paginated report?
Not yet, but we absolutely plan to support this scenario.
Can I share my paginated report content through a Power BI app?
Currently you can share individual paginated reports with other users through the sharing action in the portal or
via the toolbar. We don’t yet support sharing in an app, but expect to soon.
Will other report-specific features in Power BI, like pinning to report tiles to dashboards, work with paginated
reports?
We plan to have the reports support the same major scenarios in the service as much as possible. Ideally, though
the tool to author them is different, from a consumer perspective it’s just another report in their list in the portal.
They don’t care how it was created, they can accomplish what they need to. A good example of this feature parity is
the planned comment support. Though the feature itself may work slightly differently for each report type, you’ll
be able to use comments for both.
Are you planning to create a new authoring tool for paginated reports in the Power BI service? We can’t do
everything we need to with Report Builder today.
We are still looking at different options here for the best tooling story for paginated reports in Power BI.
Is a migration tool planned so SSRS customers can move their existing reports and assets to Power BI?
We're evaluating options here to allow content to be moved to Power BI in an automated way, but this won't be
available until after GA.
Will I ever be able to create both paginated reports and Power BI reports in a single authoring tool?
Potentially. We're currently looking at ways to enable this scenario, or if we simply distribute the authoring tools
together as a single BI suite vs. having individual downloads/branding.
Is there a report viewer control for paginated reports in the Power BI service?
No, a report viewer control isn’t available currently.
Can you search for paginated reports from the new Home experience in the Power BI service?
No, you can't currently search for your paginated reports from Home. You do see them, however, in the other parts
of the new Home experience.

Next steps
Install Report Builder from the Microsoft Download Center
Tutorial: Create a paginated report
 Tutorial: Create a paginated report and upload it to
the Power BI service (Preview)
2/15/2019 • 9 minutes to read • Edit Online

In this tutorial, you connect to a sample Azure SQL database. Then you use a wizard in Report Builder to create a
paginated report with a table that wraps to multiple pages. Then you upload the paginated report to a workspace
in a Premium capacity in the Power BI service. Paginated reports in the Power BI service are currently in preview.

Here are the steps you complete in this tutorial:

Create an Azure sample database.
Create a matrix in Report Builder with the help of a wizard.
Format the report with title, page numbers, and column headings on each page.
Format the currency.
Upload the report to the Power BI service.
If you don't have an Azure subscription, create a free account before you begin.

Prerequisites
Here are the prerequisites for creating the paginated report:
Install Report Builder from the Microsoft Download Center.
 Follow the quickstart Create an Azure SQL database sample in the Azure portal. Copy and save the value in
the Server name box on the Overview tab. Remember the user name and password you created in Azure.
Here are the prerequisites for uploading your paginated report to the Power BI service:
You need a Power BI Pro license.
Your need an app workspace on the service in a Power BI Premium capacity. It has a diamond icon next to
the workspace name.

Create the matrix with a wizard

1. Start Report Builder from your computer.
The Getting Started dialog box opens.

2. In the left pane, verify that New Report is selected, and in the right pane, select Table or Matrix Wizard.
3. In the Choose a dataset page, select Create a dataset > Next.

4. In the Choose a connection to a data source page, select New.

 The Data Source Properties dialog box opens.
5. You can name a data source anything you want, using characters and underscores. For this tutorial, in the
Name box, type MyAzureDataSource.
6. In the Select connection type box, select Microsoft Azure SQL Database.
7. Select Build next to the Connection string box.

8. In Azure: Go back to the Azure portal and select SQL databases.

9. Select the Azure SQL database you created in the quickstart "Create an Azure SQL database sample in the
Azure portal" in the Prerequisites section of this article.
10. On the Overview tab, copy the value in the Server name box.
11. In Report Builder: In the Connection Properties dialog box, under Server name paste the server name
you copied.
12. For Log on to the server, make sure Use SQL Server Authentication is selected, then type the user
name and password you created in Azure for the sample database.
13. Under Connect to a database, select the drop-down arrow and select the database name you created in
Azure.

14. Select Test Connection. You see the Test results message that Test connection succeeded.
15. Select OK > OK.
Now in the Connection string box, Report Builder displays the connection string you just created.

16. Select OK.

17. In the Choose a connection to a data source page, you see "(in this Report)" under the data source
connection you just created. Select that data source > Next.

18. Type the same user name and password in the box.
19. In the Design a query page, expand SalesLT, expand Tables, and select these tables:
Address
Customer
Product
ProductCategory
SalesOrderDetail
SalesOrderHeader
Because Relationships > Auto Detect is selected, Report Builder detects the relationships between these
tables.
20. Select Run Query. Report Builder displays the Query results.

21. Select Next.

22. In the Choose a dataset page, choose the dataset you just created > Next.

23. In the Arrange fields page, drag these fields from the Available fields box to the Row groups box:
CompanyName
SalesOrderNumber
Product_Name
24. Drag these fields from the Available fields box to the Values box:
OrderQty
UnitPrice
LineTotal
Report Builder automatically made the fields in the Values box sums.
25. In the Choose the layout page, keep all the default settings, but clear Expand/collapse groups. In
general, the expand/collapse groups feature is great, but this time you want the table to wrap to multiple
pages.
26. Select Next > Finish. The table is displayed on the design surface.

What you've created

Let's pause for a moment to look at the results of the wizard.

1. In the Report Data pane, you see the embedded Azure data source and the embedded dataset based on it,
both of which you created.
2. The design surface is about 6 inches wide. On the design surface, you see the matrix, displaying column
headings and placeholder values. The matrix has six columns and appears to be only five rows tall.
3. Order Qty, Unit Price, and Line Total are all sums, and each row group has a subtotal.
You still don't see actual data values. You need to run the report to see them.
4. In the Properties pane, the selected matrix is called Tablix1. A tablix in Report Builder is a data region that
displays data in rows and columns. It can be either a table or a matrix.
5. In the Grouping pane, you see the three row groups you created in the wizard:
CompanyName
Sales Order
Product Name
This matrix doesn't have any column groups.
Run the report
To see the actual values, you need to run the report.
1. Select Run in the Home toolbar.
Now you see the values. The matrix has many more rows than you saw in Design view! Note that Report
Builder says it's page 1 of 2?. Report Builder loads the report as quickly as possible, so it only retrieves
enough data for a few pages at a time. The question mark indicates that Report Builder hasn't loaded all the
data yet.

2. Select Print Layout. The report will be in this format when you print it. Report Builder now knows the
report has 33 pages, and has automatically added a date and time stamp in the footer.

Format the report

Now you have a report with a matrix that wraps to 33 pages. Let's add some other features and improve how it
looks. You can run the report after every step, if you want to see how it's coming along.
On the Run tab of the Ribbon, select Design, so you can continue modifying it.
Set page width
Typically a paginated report is formatted for printing, and a typical page is 8 1/2 X 11 inches.
1. Drag the ruler to make the design surface 7 inches wide. The default margins are 1 inch on each side, so the
side margins need to be narrower.
2. Click in the gray area around the design surface to show the Report properties.
If you don’t see the Properties pane, click the View tab > Properties.
3. Expand Margins and change Left and Right from 1in to 0.75in.

Add a report title

1. Select the words Click to add title at the top of the page, then type Sales by Company.
2. Select the title text, and in the Properties pane under Font, change Color to Blue.
Add a page number
You noticed the report has a date and time stamp in the footer. You can add a page number to the footer, too.
1. At the bottom of the design surface, you see [&ExecutionTime] on the right in the footer.
2. In the Report Data pane, expand the Built-in Fields folder. Drag Page Number to the left side of the footer,
at the same height as [&ExecutionTime].
3. Drag the right side of the [&PageNumber] box to make it square.
4. On the Insert tab, select Text Box.
5. Click to the right of [&PageNumber], type "of", then make the text box square.
6. Drag Overall Total Pages to the footer, to the right of "of", then drag its right side to make it square, too.
Make the table wider
Now you can make the matrix wide enough to fill the width of the page, and make the text columns wider so the
names don't scroll as much.
1. Select the matrix, then select the Company Name column.
2. Hover over the gray bar at the top of the matrix at the right edge of the Company Name column. Drag to
the right, until the column ends at 1 3/8 inches.

3. Drag the right edge of Product name until the column ends at 3 3/4 inches.
Now the matrix is almost as wide as the print area.
Format the currency
If you noticed when you ran the report, the dollar amounts aren't formatted as currency yet.
1. Select the upper-left [Sum(OrderQty)] cell, hold down the Shift key, and select lower-right [Sum(LineTotal)]
cell.
2. On the Home tab, select the dollar sign ($) currency symbol, then select the arrow next to Placeholder
styles > Sample Values.

Now you can see the values are formatted as currency.

Add column headers on each page

One more formatting improvement before publishing the report to the Power BI service: making the column
headers show up on each page in the report.
1. In the far-right end of the top bar in the Grouping pane, select the drop-down arrow > Advanced Mode.

2. Select the top Static bar in the Row Groups. You see that the Company Name cell in the matrix is selected.

3. In the Properties pane, you're looking at the properties for Tablix Member. Set KeepWithGroup to
After and RepeatOnNewPage to True.
 It's time to run the report and see how it looks now.
4. Select Run on the Home tab.
5. Select Print Layout, if it's not already selected. Now the report has 29 pages. Scroll through a few pages.
You see the currency is formatted, the columns have headings on every page, and the report has a footer
with page numbers and date and time stamp on every page.
6. Save the report to your computer.

Upload the report to the service

Now that you've created this paginated report, it's time to upload it to the Power BI service.
1. In the Power BI service ( http://app.powerbi.com) in the left navigation, select Workspaces > Create app
workspace.
2. Name your workspace Azure AW, or other unique name. You're the only member for now.
3. Select the arrow next to Advanced and turn on Dedicated capacity.

If you can't turn it on, you need to ask your Power BI admin to give you permission to add the workspace to
the dedicated Premium capacity.
4. Choose an available dedicated capacity for this workspace, if necessary > Save.

If the workspace isn't in a Premium capacity, when you try to upload your report you see the message,
"Unable to upload paginated report." Contact your Power BI administrator to move the workspace.
5. In your new workspace, select Get Data.
6. In the Files box > Get.
 7. Select Local File, navigate to where you saved the file > Open.
Power BI imports your file, and you see it under Reports on the App list page.

8. Select the report to view it.

9. If you get an error, you may need to reenter your credentials. Select the Manage icon.

10. Select Edit credentials and enter the credentials you used in Azure when you created the Azure database.

11. Now you can view your paginated report in the Power BI service.
Next steps
What are paginated reports in Power BI Premium? (Preview )
 Getting around in Report Design View for paginated
reports (Preview)
3/18/2019 • 5 minutes to read • Edit Online

Report Design View in Report Builder is the design space for creating paginated reports that you can publish to the
Power BI service. The design surface is at the center of Report Builder, with the ribbon and panes around it. The
design surface is where you add and organize your report items. This article explains the panes you use to add,
select, and organize your report resources, and change report item properties.

1. Report data pane

2. Report design surface
3. Parameters pane
4. Properties pane
5. Grouping pane
6. Current report status bar

1 Report Data pane

From the Report Data pane, you define the report data and report resources that you need for a report before you
design your report layout. For example, you can add data sources, datasets, calculated fields, report parameters,
and images to the Report Data pane.
After you add items to the Report Data pane, drag fields to report items on the design surface to control where
data appears in the report.

TIP
If you drag a field from the Report Data pane directly to the report design surface instead of placing it in a data region such
as a table or chart, when you run the report, you will see only the first value from the data in that field.
You can also drag built-in fields from the Report Data pane to the report design surface. When rendered, these
fields provide information about the report, such as the report name, the total number of pages in the report, and
the current page number.
Some things are automatically added to the Report Data pane when you add something to the report design
surface. For example, if you embed an image in your report, it will be added to the Images folder in the Report Data
pane.

NOTE
You can use the New button to add a new item to the Report Data pane. You can add multiple datasets from the same data
source or from other data sources to the report. To add a new dataset from the same data source, right-click a data source >
Add Dataset.

2 Report design surface

The Report Builder report design surface is the main work area for designing your reports. To place report items
such as data regions, subreports, text boxes, images, rectangles, and lines in your report, you add them from the
ribbon or the Report Part Gallery to the design surface. There, you can add groups, expressions, parameters, filters,
actions, visibility, and formatting to your report items.
You can also change the following:
The report body properties, such as border and fill color, by right-clicking the white area of the design
surface, outside any report items, and selecting Body Properties.
The header and footer properties, such as border and fill color, by right-clicking the white area of the design
surface in the header or footer area, outside any report items, and selecting Header Properties or Footer
Properties.
The properties of the report itself, such as page setup, by right-clicking the gray area around the design
surface and selecting Report Properties.
The properties of report items by right-clicking them and selecting Properties.
Design surface size and print area
The design surface size might be different from the page size print area you specify to print the report. Changing
the size of the design surface will not change the print area of your report. No matter what size you set for the print
area of your report, the full design area size does not change. For more information, see Rendering Behaviors.
To display the ruler, on the View tab, select the Ruler check box.

3 Parameters pane
With report parameters, you can control report data, connect related reports together, and vary report
presentation. The Parameters pane provides a flexible layout for the report parameters.
Read more about Report Parameters

4 Properties pane
Every item in a report, including data regions, images, text boxes, and the report body itself, has properties
associated with it. For example, the BorderColor property for a text box shows the color value of the text box's
border, and the PageSize property for the report shows the page size of the report.
These properties are displayed in the Properties pane. The properties in the pane change depending on the report
item that you select.
To see the Properties pane, on the View tab in the Show/Hide group > Properties.
Changing Property Values
In Report Builder, you can change the properties for report items several ways:
By selecting buttons and lists on the ribbon.
By changing settings within dialog boxes.
By changing property values within the Properties pane.
The most commonly used properties are available in the dialog boxes and on the ribbon.
Depending on the property, you can set a property value from a drop-down list, type the value, or select
<Expression> to create an expression.

Changing the Properties Pane View

By default, properties displayed in the Properties pane are organized into broad categories, such as Action, Border,
Fill, Font, and General. Each category has a set of properties associated with it. For example, the following
properties are listed in the Font category: Color, FontFamily, FontSize, FontStyle, FontWeight, LineHeight, and
TextDecoration. If you prefer, you can alphabetize all the properties listed in the pane. This removes the categories
and lists all the properties in alphabetical order, regardless of category.
The Properties pane has three buttons at the top of pane: Category, Alphabetize, and Property Page. Select the
Category and Alphabetize buttons to switch between the Properties pane views. Select the Property Pages button
to open the properties dialog box for a selected report item.

5 Grouping pane
Groups are used to organize your report data into a visual hierarchy and to calculate totals. You can view the row
and column groups within a data region on the design surface and also in the Grouping pane. The Grouping pane
has two panes: Row Groups and Column Groups. When you select a data region, the Grouping pane displays all
the groups within that data region as a hierarchical list: Child groups appear indented under their parent groups.
You can create groups by dragging fields from the Report Data pane and dropping them on the design surface or
in the Grouping pane. In the Grouping pane, you can add parent, adjacent, and child groups, change group
properties, and delete groups.
The Grouping pane is displayed by default but you can close it by clearing the Grouping pane check box on the
View tab. The Grouping pane is not available for the Chart or Gauge data regions.
For more information, see Grouping Pane and Understanding Groups.

6 Current report status bar

The current report status bar shows the name of the server the report is connected to, or it shows "No current
report server." You can select Connect to connect to a server.

Next steps
What are paginated reports in Power BI Premium? (Preview )
 Enter data directly in a paginated report in Report
Builder (Preview) - Power BI
2/15/2019 • 3 minutes to read • Edit Online

In this article, you learn about a feature in the new version of SQL Server 2016 Report Builder that lets you enter
data directly into an RDL report as an embedded dataset. This feature is similar to Power BI Desktop. You can type
the data directly in a dataset in your report, or paste it from another program like Microsoft Excel. After you've
created a dataset by entering data, you can use it just like you would any other embedded dataset you've created.
Plus you can add more than one table and use one as a filter for the other. This feature is especially useful for small,
static datasets you might need to use in your report, like report parameters.

Prerequisites
To enter data directly in a paginated report, install the new version of Report Builder from the Microsoft
Download Center.
To save your paginated report to the Power BI service, you need a Power BI Pro account and write access to a
workspace in a Power BI Premium capacity.
To save your paginated report to a report server, you need permissions to edit the RsReportServer.config file.

Get started
After you’ve downloaded and installed Report Builder, you follow the same workflow you use to add an embedded
data source and dataset to your report. In the following procedure, under Data Sources you see a new option:
Enter Data. You only need to set up this data source once in a report. After that, you can create multiple tables of
entered data as separate datasets, all using that single data source.
1. In the Report Data pane, select New > Dataset.

2. In the Dataset Properties dialog box, select Use a dataset embedded in my report.
3. Next to Data source, select New.
4. In the Data Source Properties dialog box, select Use a connection embedded in my report.
5. In the Select connection type box, select ENTER DATA > OK.

6. Back in the Dataset Properties dialog box, select Query Designer.

7. In the Query Designer pane, right-click and paste your data in the table.
 8. To set the column names, double-click each NewColumn and type the column name.

9. If the first row contains column headings from the original data, right-click and delete it.
10. By default, the data type for each column is String. To change the data type, right-click the column header >
Change Type, and set it to another data type, such as Date or Float.

11. When you’ve finished creating the table, select OK.

The query that’s generated is the same as you’d see with an XML data source. Under the covers, we’re using
XML as the data provider. We’ve repurposed it to enable this scenario as well.
12. In the Dataset Properties dialog box, select OK.
13. You see your data source and dataset in the Report Data pane.

You can use your dataset as the basis for data visualizations in your report. You can also add another dataset and
use the same data source for it.

Upload the paginated report to the Power BI service

Now that paginated reports are supported in the Power BI service in preview, you can upload your paginated
report to a Premium capacity. See Upload a paginated report for details.

Upload the paginated report to a report server

You can also upload your paginated report to a Power BI Report Server or SQL Server Reporting Services 2016 or
2017 report server. Before you do, you need to add the following item to your RsReportServer.config as an
additional data extension. Back up your RsReportServer.config file before you make the change, in case you run
into any issues.
 <Extension Name="ENTERDATA"
Type="Microsoft.ReportingServices.DataExtensions.XmlDPConnection,Microsoft.ReportingServices.DataExtensions">
<Configuration>
<ConfigName>ENTERDATA</ConfigName>
</Configuration>
</Extension>

After you've edited it, here's what the list of data providers in the config file should look like:

That’s it – you can now publish reports that use this new functionality to your report server.

Next steps
What are paginated reports in Power BI Premium? (Preview )
What is Power BI Report Server?
 Create an embedded data source for paginated
reports in the Power BI service (Preview)
2/15/2019 • 2 minutes to read • Edit Online

In this article, you learn how to create and modify an embedded data source for a paginated report in the Power BI
service. You define an embedded data source in a single report, and use it only in that report. Currently, paginated
reports published to the Power BI service need embedded datasets and embedded data sources, and can connect
to these data sources:
Azure SQL Database and Data Warehouse
SQL Server
SQL Server Analysis Services
Paginated reports connect to on-premises data sources by way of a gateway. You set up the gateway after you
publish the report to the Power BI service. Read more about Power BI gateways.

Create an embedded data source

1. Open Report Builder.
2. On the toolbar in the Report Data pane, select New > Data Source. The Data Source Properties dialog
box opens.

3. In the Name text box, type a name for the data source or accept the default.
4. Select Use a connection embedded in my report.
5. From the Select connection type list, select a data source type.
6. Specify a connection string by using one of these methods:
Type the connection string directly in the Connection string text box.
Select the expression (fx) button to create an expression that evaluates to a connection string. In the
Expression dialog box, type the expression in the Expression pane. Select OK.
Select Build to open the Connection Properties dialog box for the data source you chose in step 2.
 Fill in the fields in the Connection Properties dialog box as appropriate for the data source type.
Connection properties include the type of data source, the name of the data source, and the
credentials to use. After you specify values in this dialog box, select Test Connection to verify that
the data source is available and that the credentials you specified are correct.
7. Select Credentials.
Specify the credentials to use for this data source. The owner of the data source chooses the type of
credentials that are supported. For more information, see Specify Credential and Connection Information
for Report Data Sources.
8. Select OK.
The data source appears in the Report Data pane.

Next steps
Create an embedded dataset for a paginated report in the Power BI service
What are paginated reports in Power BI Premium? (Preview )
 Create an embedded dataset for a paginated report
in the Power BI service (Preview)
2/15/2019 • 2 minutes to read • Edit Online

In this article, you learn how to create an embedded dataset, based on an embedded data source, for a paginated
report in the Power BI service. Embedded datasets are contained in a single paginated report, for use in that
report. Currently, paginated reports published to the Power BI service need embedded datasets and embedded
data sources. You create the embedded data source and dataset in Report Builder, while you're creating your
report.
Before you can create the dataset, you need to create a data source. See Embedded data sources for paginated
reports in the Power BI service to learn how.

Create an embedded dataset

1. In the Report Data pane in Report Builder, select New > Dataset.
2. In the Query tab of the Dataset Properties dialog box, give the dataset a name. The embedded data
source is already in the Data source box, or you can select New to create a different embedded data
source.

3. Under Query type, select the type of command or query to use for the dataset.
Text runs a query to retrieve data from the database. It's the default and is used for most queries. Type a
query or import a pre-existing query by selecting Import. To build the query graphically, select Query
Designer. If you use the query designer to build a query, the text of the query will appear in this box.
Select the Expression (fx) button to use an expression to dynamically generate the query.
Table selects all the fields within a table. Enter the name of the table that you want to use as a dataset.
Stored Procedure runs a stored procedure by name.
4. In the Query Designer, you can see and interact with the tables and fields in the dataset, import a query, or
edit as text. You can also add filters and parameters here.
5. In the Query Designer, select Run Query to test it, then select OK.
6. Back in the Dataset Properties dialog box, in the Time out (in seconds) box, type the number of seconds
until the query times out. The default is 30 seconds. The value for Time out must be empty or greater than
zero. If it is empty, the query does not time out.
7. You can set other properties for the dataset on the other tabs:
Create calculated fields on the Fields tab.
Set advanced options on the Options tab.
Add or update Filters and Parameters on their respective tabs.
8. Select OK
The report opens in Report Design View. The data source, dataset, and dataset field collection appear in the
Report Data pane, and you can continue designing your paginated report.
Next steps
What are paginated reports in Power BI Premium? (Preview )
Tutorial: Create a paginated report and upload it to the Power BI service
Publish a paginated report to the Power BI service
 Create parameters for paginated reports in the Power
BI service (Preview)
2/15/2019 • 2 minutes to read • Edit Online

In this article, you learn how to create parameters for paginated reports in the Power BI service. A report
parameter provides a way to choose report data and vary the report presentation. You can provide a default value
and a list of available values, and your report readers can change the selection.
The following illustration shows Design view in Report Builder for a report with the parameters @BuyingGroup,
@Customer, @FromDate, and @ToDate.

1. The report parameters in the Report Data pane.

2. The table with one of the parameters in the dataset.
3. The Parameters pane. You can customize the layout of parameters in the parameters pane.
4. The parameters @FromDate and @ToDate have the data type DateTime. When viewing the report, you
can either type a date in the text box or choose a date in the calendar control.
5. One of the parameters in the Dataset Properties dialog box.

Create or edit a report parameter

1. Open your paginated report in Report Builder.
2. In the Report Data pane, right-click the Parameters node > Add Parameter. The Report Parameter
Properties dialog box opens.
3. In Name, type a name for the parameter or accept the default name.
4. In Prompt, type text to appear next to the parameter text box when the user runs the report.
5. In Data type, select the data type for the parameter value.
6. If the parameter can contain a blank value, select Allow blank value.
7. If the parameter can contain a null value, select Allow null value.
 8. To allow a user to select more than one value for the parameter, select Allow multiple values.
9. Set the visibility option.
To show the parameter on the toolbar at the top of the report, select Visible.
To hide the parameter so that it does not display on the toolbar, select Hidden.
To hide the parameter and protect it from being modified on the report server after the report is
published, select Internal. The report parameter can then only be viewed in the report definition. For
this option, you must set a default value or allow the parameter to accept a null value.
10. Select OK.

Next steps
See View parameters for paginated reports to see how the parameters look in the Power BI service.
For in-depth information about parameters in paginated reports, see the Report Parameters (Report Builder and
Report Designer) article in the SQL Server Reporting Services documentation
 Publish a paginated report to the Power BI service
(Preview)
3/18/2019 • 2 minutes to read • Edit Online

In this article, you learn about publishing a paginated report to the Power BI service by uploading it from your
local computer. You can upload paginated reports to your My Workspace or any other workspace, as long as the
workspace is in a Premium capacity. Look for the diamond icon next to the workspace name.
If your report data source is on premises, then you need to create a gateway after you upload the report.

Add a workspace to a Premium capacity

If the workspace doesn't have the diamond icon next to the name, you need to add the workspace to a
Premium capacity.
1. Select Workspaces, select the ellipsis (...) next to the workspace name, then select Edit workspace.

2. In the Edit workspace dialog box, expand Advanced, then slide Dedicated capacity to On.

You may not be able to change it. If not, then contact your Power BI Premium capacity admin to give you
 assignment rights to add your workspace to a Premium capacity.

Upload a paginated report

1. Create your paginated report in Report Builder and save it to your local computer.
2. Open the Power BI service in a browser and browse to the Premium workspace where you want to publish
the report. Note the diamond icon next to the name.
3. Select Get Data.

4. In the Files box, select Get.

5. Select Local file > browse to the paginated report > Open.
6. Select Continue > Edit credentials.

7. Configure your credentials > Sign in.

You see your report in the list of reports.

8. Select it to open it in the Power BI service. If it has parameters, you need to select them before you can view
the report.
Create a gateway
Just like any other Power BI report, if the report data source is on premises, then you need to create or connect to
a gateway to access the data.
1. Next to the report name, select Manage.

2. See the Power BI service article Install a gateway for details and next steps.
Gateway limitations
Currently gateways don't support multi-value parameters.

Next steps
View a paginated report in the Power BI service
What are paginated reports in Power BI Premium? (Preview )
 View a paginated report in the Power BI service
(Preview)
2/15/2019 • 2 minutes to read • Edit Online

In this article, you learn about viewing a paginated report to the Power BI service. Paginated reports are reports
created in Report Builder and uploaded to any workspace in a Premium capacity. Look for the diamond icon
next to the workspace name.

Paginated reports have a their own icon, .

You can also export paginated reports to a number of formats:
Microsoft Excel
Microsoft Word
Microsoft PowerPoint
PDF
Comma-separated values
XML
Web archive (.mhtml)

View a paginated report

1. Select the paginated report in the workspace.

2. If the report has parameters, as this one does, you may not see the report when you first open it. Select
parameters, then select View Report.
 You can also change the parameters at any time.
3. Page through the report by selecting the arrows at the top of the page, or by typing a page number in the
box.

4. Select Export to find a format to export your paginated reports.

Next steps
What are paginated reports in Power BI Premium? (Preview )
 View parameters for paginated reports in the Power
BI service (Preview)
2/15/2019 • 2 minutes to read • Edit Online

In this article, you learn how to interact with parameters for paginated reports in the Power BI service. A report
parameter provides a way to filter report data. Parameters offer a list of available values, and you can choose one
or many values. Sometimes parameters have a default value, and sometimes you have to choose a value before
you can see the report.
When you view a report that has parameters, the report viewer toolbar displays each parameter so you can
interactively specify values. The following illustration shows the parameter area for a report with parameters for
Buying Group, Location, a From Date, and a To Date.

Parameters pane in the Power BI service

1. Parameters pane The report viewer toolbar displays a prompt such as "Required" or a default value for
each parameter.
2. Invoices From / To Date parameters The two data parameters have default values. To change the date,
type a date in the text box or choose a date in the calendar.
3. Location parameter The Location parameter is set to allow you to select one, many, or all values.
4. View Report After you enter or change parameter values, click View Report to run the report.
5. Default values If all parameters have default values, the report runs automatically on first view. Some
parameters in this report didn't have default values, so you don't see the report until you select values.

Next steps
Create parameters for paginated reports in the Power BI service
 What are Power BI template apps? (preview)
2/13/2019 • 3 minutes to read • Edit Online

The new Power BI template apps enable Power BI partners to build Power BI apps with little or no coding, and
deploy them to any Power BI customer. This article is an overview of the Power BI template app program.
Template apps are a replacement for the current service content packs. As a Power BI partner, you create a set of
out-of-the-box content your customers, and publish it yourself.
You build template apps that allow your customers to connect and instantiate with their own accounts. As domain
experts, they can unlock the data in a way that's easily consumable by their business users.
You submit your partner-built template apps to the Cloud Partner Portal. The apps then become publicly available
in the Power BI App gallery (app.powerbi.com/getdata/services) and on Microsoft AppSource
(appsource.microsoft.com). Here's an example of the public template app experience.

Overview
The general process to develop and submit a template app involves several stages, some of which can involve
more than one activity at the same time.

POWER BI CLOUD PARTNER

STAGE DESKTOP POWER BI SERVICE PORTAL

One Build a data Create a Register as a

model and report workspace. partner
in a .pbix file Import .pbix file.
Create a
complementary
dashboard

Two Create a test

package and run
internal validation

Three Promote the test With your

package to preproduction
preproduction for package, create a
validation outside Power BI
your Power BI template app
tenant, and offer and start
submit it to the validation
AppSource process

Four Promote the Go live

preproduction
package to
production

Requirements
To create the template app, you need permissions to create one. See the Power BI admin portal, Template app
settings for details.
To publish a template app to the Power BI service and AppSource, you must meet the requirements for becoming
a Cloud Marketplace Publisher.

High-level steps
Here are the high-level steps.
1. Review the requirements to make sure you meet them.
2. Build a report in Power BI Desktop. Use parameters so you can save it as a file other people can use.
3. Create a workspace for your template app in your tenant on the Power BI service (app.powerbi.com).
4. Import your .pbix file and add content such as a dashboard to your app.
5. Create a test package to test the template app yourself within your organization.
6. Promote the test app to preproduction to submit the app for validation in AppSource, and to test outside
your own tenant.
7. Submitthe content to Cloud Partner Platform for publishing.
8. Make your offer goes 'Live' in AppSource, and move your app to production in Power BI.
9. Now you can start developing the next version in the same workspace, in preproduction.

Requirements
To create the template app, you need permissions to create one. See the Power BI admin portal, Template app
settings for details.
To publish a template app to the Power BI service and AppSource, you must meet the requirements for becoming
a Cloud Marketplace Publisher.

Tips
Make sure your app includes sample data to get everyone started in a click.
Carefully examine your application by installing it in your tenant and in a secondary tenant. Make sure
customers only see what you want them to see.
Use AppSource as your online store to host your application. This way everyone using Power BI can find your
app.
Consider offering more than one template app for separate unique scenarios.
Enable data customization, for example support custom connection and parameters configuration by the
installer.
See Tips for authoring template apps in Power BI (preview ) for more suggestions.

Support
For support during development, use https://powerbi.microsoft.com/support. We actively monitor and manage
this site. Customer incidents quickly find their way to the appropriate team.

Next steps
Create a template app
 Create a template app in Power BI (preview)
2/13/2019 • 5 minutes to read • Edit Online

The new Power BI template apps enable Power BI partners to build Power BI apps with little or no coding, and
deploy them to any Power BI customer. This article contains step-by-step instructions to create a Power BI
template app.
If you can create Power BI reports and dashboards, you can become a template app builder who builds and
packages analytical content into an app. You can then deploy your app to other Power BI tenants through any
available platform, such as AppSource, or by using it in your own web service. As a builder you can create a
protected analytics package for distribution.
Power BI tenant admins govern and control who in their organization can create template apps, and who can
install them. Those who are authorized can install your template app, then modify it and distribute it to the Power
BI consumers in their organization.

Prerequisites
Here are the requirements for building a template app:
A Power BI pro license
An installation of Power BI Desktop (optional)
Familiarity with the basic concepts of Power BI
Permissions to create a template app. See the Power BI admin portal, Template app settings for details.

Enable app developer mode

To create a template app you can distribute to other Power BI tenants, you need to be in App Developer mode.
Otherwise, you're just creating an app for Power BI consumers in your own organization.
1. Open the Power BI service in a browser.
2. Go to Settings > General > Developer > Enable template app development mode.

If you don't see that option, contact your Power BI admin to grant you permissions for template app
development in the admin portal.
3. Select Apply.

Create the template app workspace

To create a template app you can distribute to other Power BI tenants, you need to create it in one of the new app
workspaces.
1. In the Power BI service, select Workspaces > Create app workspace.

2. In Create an app workspace, in Preview improved workspaces, select Try now.

3. Enter a name, description (optional), and logo image (optional) for your app workspace.
4. Select Develop a template app.
5. Select Save.

Create the content in your template app

As with a regular Power BI app workspace, your next step is to create the contents in the workspace. In this
preview version of template apps, we support only up to one of each type: one dataset, one report, and one
dashboard.
Create your Power BI content in your app workspace.
If you're using parameters in Power Query, make sure they have well-defined type (for example, Text). The types
Any and Binary aren't supported.
Tips for authoring template apps in Power BI (preview ) has suggestions to consider when creating reports and
dashboards for your template app.

Create the test template app

Now that you have content in your workspace, you're ready to package it in a template app. The first step is to
create a test template app, accessible only from within your organization on your tenant.
1. In the template app workspace, select Create app.

Here, you fill in additional parameters for your template app, in four categories.
Branding
App name
Description
App logo (optional)
App color
Content
App landing page (optional): Define a report or dashboard to be the landing page of your app.
Control
Control several limitations and restrictions that your application users will have with the content of your
application. You can use this control to protect certain intellectual property your app might contain.
Access
In the test phase, decide which others in your organization can install and test your app.
Don't worry, you can always come back and change these settings later.
2. Select Create app.
You see a message that the test app is ready, with a link to copy and share with your app testers.

You've also done the first step of the release management process, which follows.

Manage the template app release

Before you release this template app publicly, you want to make sure it's ready to go. Power BI has created the
release management pane, where you can follow and inspect the full app release path. You can also trigger the
transition from stage to stage. The common stages are:
Generate test app: for testing only in your organization.
Promote the test package to pre-production stage: test outside of your organization.
Promote pre-production package to Production: production version.
Delete any package or start over from previous stage.
Let's go through the stages.
1. In the template app workspace, select Release Management.

2. Select Create app.

If you created the test app in Create the test template app above, the yellow dot next to Testing is
already filled and you don't need to select Create app here. If you do select it, you go back into the
template app creation process.
3. Select Get link.
4. To test the app installation experience, copy the link in the notification window and paste it in a new browser
window.
From here, you're following the same procedure your customers will follow. See Install and distribute
template apps in your organization for their version.
5. In the dialog box, select Install.
When installation succeeds, you see a notification that the new app is ready.
6. Select Go to app.
7. In Get started with your new app, you see your app as your customers will see it.
 8. Select Explore App to verify the test app with the sample data.
9. To make any changes, go back to the app in the original workspace. Update the test app until you're
satisfied.
10. When you're ready to promote your app to pre-production for further testing outside your tenant, go back
to the Release Management pane and select Promote app next to Testing.

11. Select Promote to confirm your choice.

12. Copy this new URL to share outside your tenant for testing. This link is also the one you submit to begin the
process of distributing your app on AppSource.
13. When your app is ready for production or sharing via AppSource, go back to the Release Management
pane and select Promote app next to Pre-production.
14. Select Promote to confirm your choice.
Now your app is in production, and ready for distribution.
To make your app widely available to thousands of Power BI users in the world, we encourage you to submit it to
AppSource. See the Power BI Application offer for details.

Update your app

Now that your app is in production, you can start over in the test phase, without disrupting the app in production.
1. In the Release management pane, select Create app.
2. Go back through the app creation process.
3. After you've set Branding, Content, Control, and Access, you again select Create app.
4. Select Close and go back to Release management.
You see you have two versions now: The version in production, plus a new version in testing.

Next steps
See how your customers interact with your template app in Install, customize, and distribute template apps in your
organization.
See the Power BI Application offer for details on distributing your app.
 Tips for authoring template apps in Power BI
(preview)
2/13/2019 • 5 minutes to read • Edit Online

When you're authoring your template app in Power BI, part of it is the logistics of creating the workspace, testing
it, and production. But the other important part is obviously authoring the report and the dashboard. We can
break down the authoring process into four main components. Working on these components helps you create the
best possible template app:
With queries, you connect and transform the data, and define parameters.
In the data model, you create relationships, measures, and Q&A improvements.
Report pages include visuals and filters to provide insights into your data.
Dashboards and tiles offer an overview of the insights included.
You may be familiar with each piece as existing Power BI features. When building a template app, there are
additional things to consider for each piece. See each section below for more details.

Queries
For template apps, queries developed in Power BI Desktop are used to connect to your data source and import
data. These queries are required to return a consistent schema and are supported for Scheduled Data refresh
(DirectQuery isn't supported).
Connect to your API
To get started, you need to connect to your API from Power BI Desktop to start building your queries.
You can use the Data Connectors that are available out of the box in Power BI Desktop to connect to your API. You
can use the Web Data Connector (Get Data -> Web) to connect to your Rest API or the OData connector (Get
Data -> OData feed) to connect to your OData feed. These connectors work out of the box only if your API
supports Basic Authentication.

NOTE
If your API uses any other authentication types, like OAuth 2.0 or Web API Key, then you need to develop your own Data
Connector to allow Power BI Desktop to successfully connect and authenticate to your API. For details on how to develop
your own Data Connector for your template app, check the Data Connectors documentation.

Consider the source

The queries define the data that's included in the data model. Depending on the size of your system, these queries
should also include filters to ensure your customers are dealing with a manageable size that fits your business
scenario.
Power BI template apps can execute multiple queries in parallel and for multiple users concurrently. Plan ahead
your throttling and concurrency strategy and ask us how to make your template app fault tolerant.
Schema enforcement
Ensure your queries are resilient to changes in your system, changes in schema on refresh can break the model. If
the source could return null or missing schema result for some queries, consider returning an empty table or a
meaningful custom error message.
Parameters
Parameters in Power BI Desktop allow your users to provide input values that customize the data retrieved by the
user. Think of the parameters up front to avoid rework after investing time to build detailed queries or reports.

NOTE
Template apps support all parameters except Any and Binary.

Additional query tips

Ensure all columns are typed appropriately.
Columns have informative names (see Q&A).
For shared logic, consider using functions or queries.
Privacy levels are currently not supported in the service. If you get a prompt about privacy levels, you may
need to rewrite the query to use relative paths.

Data models
A well-defined data model ensures your customers can easily and intuitively interact with the template app. Create
the data model in Power BI Desktop.

NOTE
You should do much of the basic modeling (typing, column names) in the queries.

Q&A
The modeling also affects how well Q&A can provide results for your customers. Ensure you add synonyms to
commonly used columns and you've properly named your columns in the queries.
Additional data model tips
Make sure you've:
Applied formatting to all value columns. Apply types in the query.
Applied formatting to all measures.
Set default summarization. Especially "Do Not Summarize", when applicable (for unique values, for example).
Set data category, when applicable.
Set relationships, as necessary.

Reports
The report pages offer additional insight into the data included in your template app. Use the pages of the reports
to answer the key business questions your template app is trying to address. Create the report using Power BI
Desktop.

NOTE
You can only include one report in a template app, so take advantage of the different pages to call out particular sections of
your scenario.

Additional report tips

Use more than one visual per page for cross-filtering.
Align the visuals carefully (no overlapping).
 Page is set to "4:3" or "16:9" mode for layout.
All of the aggregations presented make numeric sense (averages, unique values).
Slicing produces rational results.
Logo is present on at least the top report.
Elements are in the client's color scheme to the extent possible.

Dashboards
The dashboard is the main point of interaction with your template app for your customers. It should include an
overview of the content included, especially the important metrics for your business scenario.
To create a dashboard for your template app, just upload your PBIX through Get Data > Files or publish directly
from Power BI Desktop.

NOTE
template apps currently require a single report and dataset per template app. Do not pin content from multiple
reports/datasets onto the dashboard used in the template app.

Additional dashboard tips

Maintain the same theme when pinning so that the tiles on your dashboard are consistent.
Pin a logo to the theme so consumers know where the pack is from.
Suggested layout to work with most screen resolutions is 5-6 small tiles wide.
All dashboard tiles should have appropriate titles/subtitles.
Consider groupings in the dashboard for different scenarios, either vertically or horizontally.

Known limitations
FEATURE KNOWN LIMITATION

Contents: Datasets Exactly one dataset should be present. Only datasets built in
Power BI Desktop (.pbix files) are allowed.
Not supported: Datasets from other template apps, cross-
workspace datasets, paginated reports (.rdl files), Excel
workbooks

Contents: Reports Up to one report

Contents: Dashboards Up to one non-empty dashboard

Not supported: Real-time tiles (in other words, no support for
PushDataset or pubnub)

Contents: Dataflows Not supported: Dataflows

Contents from files Only PBIX files are allowed.

Not supported: .rdl files (paginated reports), Excel workbooks
 FEATURE KNOWN LIMITATION

Data sources Data sources supported for cloud Scheduled Data refresh are
allowed.
Not supported:
DirectQuery
Live connections (no Azure AS)
On-premises data sources (personal and enterprise gateways
aren’t supported)
Real time (no support for pushdataset)
Composite models

Dataset: cross-workspace No cross-workspace datasets are allowed

Content: Dashboards Real-time tiles aren’t allowed (in other words, no support for
PushDataset or pubnub)

Query parameters Not supported: Parameters of type "Any" or "Binary" type

block refresh operation for dataset

Custom visuals Only publicly available custom visuals are supported.

Organizational custom visuals not supported

Next steps
What are Power BI template apps? (preview )
 Install and distribute template apps in your
organization - Power BI (preview)
2/13/2019 • 2 minutes to read • Edit Online

The new Power BI template apps enable Power BI partners to build Power BI apps with little or no coding, and
deploy them to any Power BI customer. This article is for Power BI analysts. It explains how you install, customize,
and distribute a template app that a Power BI partner created. If you're interested in creating template apps to
distribute yourself, see Create a template app in Power BI.

When you install a template app that a Power BI partner has created, you can modify it to meet the needs of your
organization, and then distribute it to your colleagues as an app.

Prerequisites
Here are the requirements for installing, customizing, and distributing a template app:
A Power BI pro license
Familiarity with the basic concepts of Power BI
Valid installation link from the template app creator or AppSource.
Permissions to install template apps.

Install a template app

You may receive a link to a template app. Otherwise, you can search AppSource for one that interests you. Either
way, after you install it, you can modify it and distribute it to your own organization.
Search AppSource from a browser
In a browser, select this link to open AppSource filtered to Power BI apps:
https://appsource.microsoft.com/marketplace/apps?product=power-bi
Search AppSource from the Power BI service
1. In the left navigation pane in the Power BI service, select Apps > Get apps.
2. In AppSource, select Apps.

3. Browse or search for the app, then select Get it now.

4. In the dialog box, select Install.
If you have a Power BI Pro license, the app is installed with its associated app workspace. You customize the
app in the associated workspace.
When installation succeeds, you see a notification that your new app is ready.
5. Select Go to app.
6. In Get started with your new app, select one of three options:
 Explore app: Basic sample data exploration. Start here to get the look and feel of the app.
Connect data: Change the data source from the sample data to your own data source. You can redefine
dataset parameters and data source credentials. See Known limitations in the template apps tips article.
Go to workspace (most advanced option): you can make any changes allowed by the app builder.
Or skip this dialog box and access the associated workspace directly via Workspaces in the left navigation
pane.
7. Before you share it with your coworkers, you'll want to connect to your own data. You may also want to
modify the report or dashboard to make it work for your organization. You can also add other reports or
dashboards at this point.

Update and distribute the app

After you've updated the app for your organization, you're ready to publish it. The steps are the same as for
publishing any other app.
1. When you've finished customizing, in the workspace list view select Update app in the upper-right corner.

2. In Details, you can modify the description and background color.

3. In Content, you can select a landing page, either the dashboard or the report.

4. In Access, you give access either to selected users or to your whole organization.
5. Select Update app.
6. After it's successfully published, you can copy the link and share it with whomever you've given access to. If
you've shared it with them, they also see it on the My organization tab in AppSource.

Next steps
Create workspaces with your colleagues in Power BI
 Forgot your password for Power BI?
1/14/2019 • 2 minutes to read • Edit Online

If you've forgotten your password, you can use the following link to request a password reset.
https://passwordreset.microsoftonline.com
If you're told that your account is not enabled for password reset, you'll need to contact your Office 365
administrator. If you're using the free trial, the administrator is the first person in your organization who signed up.
If you are still having issues accessing your account you can try contacting the support team for password resets.
This is not the support number for the Power BI service!
1 -800 -642 -7676

NOTE
Please note, support is provided during the eastern standard time (EST) time zone. Support is provided during business hours
and currently only supported in English.

More questions? Try asking the Power BI Community

 Capturing additional diagnostic information
1/14/2019 • 2 minutes to read • Edit Online

Capturing Additional Diagnostic Information for Power BI

These instructions provide two potential options for manually collecting additional diagnostic information from the
Power BI web client. Only one of these options needs to be followed.

Network Capture - Edge & Internet Explorer

1. Browse to Power BI with Edge or Internet Explorer.
2. Open the Edge developer tools by pressing F12.
3. That will bring up the Developer Tools window:

4. Switch to the Network tab. It will list traffic it has already captured.

5. You can browse within the window and reproduce any problem you may be encountering. You can hide and
show the developer tools window at any time during the session by pressing F12.
6. To stop the capture, you can select the red square on the network tab of the developer tools area.
7. Select on the diskette icon to Export as HAR

8. Provide a file name and save the HAR file.

The HAR file will contain all the information about network requests between the browser window and
Power BI. This will include the activity IDs for each request, the precise timestamp for each request, and any
error information returned to the client. This trace will also contain the data used to populate the visuals
shown on the screen.
9. You can provide the HAR file to support for review.
More questions? Try asking the Power BI Community
 Using an alternate email address
1/30/2019 • 2 minutes to read • Edit Online

When you sign up for Power BI, you provide an email address. By default, Power BI uses this address to send you
updates about activity in the service. For example, when someone sends you a sharing invitation, it goes to this
address.
In some cases, you might want these emails delivered to an alternate email address rather than the one you signed
up with. This article explains how to specify an alternate address in Office 365 and in PowerShell. The article also
explains how an email address is resolved in Azure Active Directory (Azure AD ).

NOTE
Specifying an alternate address doesn't affect which email address Power BI uses for service updates, newsletters, and other
promotional communications. Those communications are always be sent to the email address you used when you signed up
for Power BI.

Use Office 365

To specify an alternate address in Office 365, follow these steps.
1. Open the Office 365 personal info page. If you are prompted to, sign in with the email address and
password you use for Power BI.
2. On the left menu, select Personal info.
3. In the Contact details section, select Edit.
If you cannot edit your details, this means your email address is managed by your Office 365 administrator.
Contact your administrator to update your email address.

4. In the Alternate email field, enter the email address you would like Power BI updates to be sent to.

Use PowerShell
To specify an alternate address in PowerShell, use the Set-AzureADUser command.
 Set-AzureADUser -ObjectId [email protected] -OtherMails "[email protected]"

Email address resolution in Azure AD

When capturing an Azure AD embed token for Power BI, you can use three different types of email:
The main email address that is associated with a user’s Azure AD account
The UserPrincipalName (UPN ) email address
The other email address array attribute
Power BI selects which email to use based on the following sequence:
1. If the mail attribute in the Azure AD user object is present, then Power BI uses that mail attribute for the
email address.
2. If the UPN email is not a *.onmicrosoft.com domain email address (the information after the "@" symbol),
then Power BI uses that mail attribute for the email address.
3. If the other email address array attribute in the Azure AD user object is present, then the first email in that
list (since there can be a list of emails in this attribute) is used.
4. If none of the above conditions are present, then the UPN address is used.
More questions? Try the Power BI Community
 Using the same account for Power BI and Azure
1/14/2019 • 2 minutes to read • Edit Online

If you are a user of both Power BI and Azure, you may want to use the same login for both services so that you
don't need to type in your password twice.
Power BI signs you in with your organizational account, associated with your work or school email address. Azure
signs you in with either a Microsoft Account or your organizational account.
If you want to use the same login for both Azure and Power BI, be sure to sign in to Azure with your organizational
account.
What if I already sign in to Azure with my Microsoft Account?
You can add your organizational account as a co-administrator in Azure. Here's how:
1. Sign in to the Azure Management Portal. If you are a user in multiple Azure directories, click Subscriptions and
then filter to view only the directory and subscriptions you want to edit.
2. In the navigation pane, click Settings, click Administrators, and then click Add.
3. Enter the email address associated with your organizational account.
4. Select the subscriptions you want to access with your organizational account and then click the check mark.
Next time you sign in to the Azure Management Portal, use your organizational email address.
More questions? Try the Power BI Community
 Office 365 dedicated customers - known issues
1/14/2019 • 2 minutes to read • Edit Online

Power BI is now supported for Office 365 Dedicated customers. If you are an O365 Dedicated customer, you can
sign in with an account from that tenant and use Power BI. There are two known issues currently.

Groups
When selecting Members or Calendar in the Group context menu, you will be redirected to the Mail app instead.
Files and Conversations work as expected.

iPhone App - sign in with vanity domain leads to error

When you sign in, on the iPhone app, using a login with a vanity domain, you may encounter an error.
Sign In error
An unexpected internal error occurred. Please try again.
To work around this issue, sign in with the email address listed when you click on the user icon within the Power BI
service instead of with the vanity domain.

More questions? Try the Power BI Community

 Troubleshoot Cortana for Power BI
2/13/2019 • 5 minutes to read • Edit Online

This article is part of a series. If you haven't already, we recommend reading the following three articles.
Article 1: Understand how Cortana and Power BI work together to search for Power BI dashboards and reports
Article 2: For searching reports: enable the Cortana - Power BI - Windows integration
Article 3: For searching reports: create special Cortana answer cards
If you're still having problems getting Cortana to integrate with Power BI, you've come to the right place. Follow
the steps below to diagnose and fix the problem.

Why doesn't Cortana find answers from my Power BI reports or

dashboards?
1. Do you have a Power BI account? If not, sign up for a free trial.
2. Is Cortana working? Do you see the Cortana icon in your taskbar?

When you select it, does Cortana open with a field in which you can type?
3. Did you use at least 2 words in your search? Cortana needs at least 2 word phrases to find answers in
Power BI. Try adding "show" to the beginning of your question.
4. If your dashboard has a title with more than one word, Cortana will only return that dashboard if your
search matches at least two of the words. For a dashboard named "Sales FY16":
"show sales" will not return a Power BI result.
"show me sales fy16", "sales fy16", "show sales fy16", and "show me sales f" will return a Power BI
result.
Adding the words "powerbi" counts as one of the 2 required words, so "powerbi sales" will return a
Power BI result.
5. Do you have access or edit permissions to any reports or dashboards? For reports, ensure the content you
are attempting to search has an answer card. For dashboards, ensure the content you are attempting to
search is in Shared with me, an app workspace, or My workspace. Use the troubleshooting tool for help
identifying the problem.
6. Are you using a mobile device? Currently we only support Power BI and Cortana integration on Windows
mobile devices.
7. Is Cortana configured for English? The current Cortana-Power BI integration only supports English. Open
Cortana and select the cog icon to display Settings. Scroll down to Cortana language and ensure it's set
to one of the English options.
 8. Do you have more than 100 reports enabled for Cortana? Cortana only searches up to 100 total. To ensure
that your report is included, move or copy it to your My Workspace because Cortana searches there first.
9. You might just need to give it some time. The first time you type a query the model might be cold. Wait a
few seconds so the data can be loaded into memory, and then try again.
10. For dashboards, it can take up to 24 hours for them to become accessible to Cortana.
11. For reports, when a new dataset or custom answer card is added to Power BI and enabled for Cortana it
can take up to 30 minutes for results to begin appearing in Cortana. Logging in and out of Windows 10, or
otherwise restarting the Cortana process in Windows 10, will allow new report content to appear
immediately.
12. Your Power BI Administrator can "opt out". Check with your admin to see if this is the case.

Reports only: why doesn't Cortana find answers from my Power BI

reports
1. If you're looking for answers in reports, do you have any reports with Cortana answer cards? Answer cards
are the only way Cortana can find answers in your Power BI reports. Learn how to create an answer card by
reading Create Cortana answer cards in Power BI service and Power BI Desktop.
2. Are your running Windows version 1511 or later? Find out by opening Windows Settings and selecting
System > About. If not, update your version of Windows.
3. Are your Windows and Power BI accounts connected? This can be confusing. Follow the instructions in Enable
Cortana for Power BI.
4. Have the underlying datasets been enabled for Cortana? Maybe a colleague has shared a dataset that she has
already enabled for Cortana. But, if not, learn how to enable datasets for Cortana yourself. It's quick and easy.

Dashboards only: why doesn't Cortana find answers from my Power BI

dashboards
1. Ensure that you are connected to your work account. Power BI needs this connection so that it can
authenticate your access permissions to data. To check that you are connected or if not, to connect your
work account, use the Windows search box to navigate to “Connect to work or school”.
2. Do you have access to Cortana? Select the Windows search box and provide Cortana access permissions
to your information.

Try the Cortana troubleshooting tool

Still having trouble? Now is a good time to run the Cortana troubleshooting tool and narrow down the possible
issues.
Having trouble retrieving answers from a report?
1. For reports, before running the troubleshooting tool, make sure to set the Page level filters on your
Cortana answer cards to Require single selection. For help doing this see Create Cortana answer cards.
2. Open the troubleshooting tool by adding "/cortana/test" to the end of your Power BI service URL. Your
URL should look similar to this:
app.powerbi.com/cortana/test
3. In the Utterance field, to troubleshoot reports, type the name of a Cortana answer card exactly as it
appears in the Power BI tab.
4. Sometimes, the first time you type something into the Utterance field, nothing happens. Think of it as
priming the system; you're letting the troubleshooting tool know that it's time to turn on. Cut and paste or
retype into the Utterance field again. In this example, the name of our answer card is Cortana stores.
Pasting or typing Cortana stores into the tool produces a single result that displays in the
Interpretations field. Click to see the answer card displayed in the Cortana window -- in this case,
Cortana stores.

Because we got a result, we now know that Cortana is enabled in Power BI. That narrows down the
problem to something on the Windows side or the Cortana language setting or having more than 100
datasets enabled for Cortana.
Having trouble retrieving answers from a dashboard?
Looking for a dashboard that has been shared with you? Open Power BI > Shared with me and locate the name
of the dashboard. Then type that name into the Utterances field.

Troubleshooting tool known issues

 If the tool doesn’t fetch the results the first time; instead paste the query into the Utterance text box.
The query must be 2 or more words, by design. If your query is too short, add the word "show".
Some query strings with prepositions might not work (e.g. sales by item). Try different query terms that don't
use prepositions and are meaningful/unique.
More questions? Try the Power BI Community
 Troubleshooting Analyze in Excel
1/14/2019 • 5 minutes to read • Edit Online

There may be times when using Analyze in Excel that you get an unexpected result, or the feature doesn't work as
you expected. This page provides solutions for common issues when using Analyze in Excel.

NOTE
There's a separate page dedicated to describing and enabling Analyze in Excel.
If you encounter a scenario that is not listed below, and it is causing you issues, you can ask for further assistance on the
community site, or you can create a support ticket.

This article contains the following troubleshooting sections:

Update Excel libraries for the OLE DB provider
Determining whether you need to update your Excel libraries
Connection cannot be made error
Forbidden error
No data models
Token expired error
Unable to access on-premises Analysis services
Can't drag anything to the PivotTable Values area (no measures)

Update Excel libraries for the OLE DB provider

To use Analyze in Excel, your computer must have a current AS OLE DB provider installed. This community post
is a great source to verify your installation of the OLE DB provider, or to download a recent version.
The Excel libraries need to match your version of Windows in terms of its bit-level. If you have 64-bit Windows
installed, you need to install the 64-bit OLE DB provider.
To download the latest Excel libraries, visit Power BI and select the down arrow in the upper right corner of the
Power BI service, then select Analyze in Excel updates.

In the dialog that appears, select Download (preview).

Determining whether you need to update your Excel libraries
You can download the most recent version of the Excel OLE DB provider libraries from the links in the previous
section. Once you download the appropriate OLD DB provider library and begin installation, checks are
performed against your current installed version.
If your Excel OLE DB provider client libraries are up to date, you'll be presented with a dialog that looks like the
following:

C:\Users\davidi\Desktop\powerbi-content-pr\articles\media\powerbi-desktop-troubleshooting-analyze-in-excel
Alternatively, if the new version you are installing is newer than the version on your computer, the following dialog
appears:

If you see the dialog prompting you to upgrade, you should continue with the installation to get the most recent
version of the OLE DB provider installed in your computer.

Connection cannot be made error

The primary cause for a connection cannot be made error is that your computer's OLE DB provider client libraries
are not current. For information about how to determine the correct update, and for download links, see Update
Excel libraries for the OLE DB provider earlier in this article.

Forbidden error
Some users have more than one Power BI account, and when Excel attempts to connect to Power BI using existing
credentials, it may use credentials that do not have access to the dataset or report you want to access.
When this occurs, you may receive an error titled Forbidden, which means you may be signed into Power BI with
credentials that do not have permissions to the dataset. After encountering the forbidden error, when prompted
to enter your credentials, use the credentials that have permission to access the dataset you're trying to use.
If you still run into errors, log into Power BI with the account that has permission, and verify that you can view and
access the dataset in Power BI that you're attempting to access in Excel.

No data models
If you encounter an error that states Can't find OLAP cube model, then the dataset you're trying to access has
no data model, and therefore cannot be analyzed in Excel.

Token expired error

If you receive a token expired error, it means you haven't recently used the Analyze in Excel feature on the
computer you're using. Simply re-enter your credentials, or reopen the file, and the error should go away.

Unable to access on-premises Analysis Services

If you're trying to access a dataset that has connections to on-premises Analysis Services data, you may receive an
error message. Analyze in Excel does support connecting to datasets and reports on on-premises Analysis
Services with a connection string, as long as your computer is on the same domain as the Analysis Services
server, and your account has access to that Analysis Services server.

Can't drag anything to the PivotTable Values area (no measures)

When Analyze in Excel connects to an external OLAP model (which is how Excel connects to Power BI), the
PivotTable requires measures to be defined in the external model, since all calculations are performed on the
server. This is different than when you work with a local data source (such as tables in Excel, or when you're
working with datasets in Power BI Desktop or the Power BI service), in which case the tabular model is
available locally, and you can use implicit measures, which are measures that are generated dynamically and are
not stored in the data model. In these cases, the behavior in Excel is different from the behavior in Power BI
Desktop or the Power BI service: there may be columns in the data that can be treated as measures in Power BI,
but can't be used as values (measures) in Excel.
To address this issue, you have a few options:
1. Create measures in your data model in Power BI Desktop, then publish the data model to the Power BI
service and access that published dataset from Excel.
2. Create measures in your data model from Excel PowerPivot.
3. If you imported data from an Excel workbook that had only tables (and no data model), then you can add the
tables to the data model, then follow the steps in option 2, directly above, to create measures in your data
model.
Once your measures are defined in the model in the Power BI service, you'll be able to use them in the Values
area in Excel PivotTables.

Next steps
Analyze in Excel
Tutorial: Create your own measures in Power BI Desktop
Measures in PowerPivot
Create a Measure in PowerPivot
Add worksheet data to a Data Model using a linked table
Differences between OLAP and non-OLAP PivotTables in Excel
 Troubleshooting the On-premises data gateway
2/13/2019 • 25 minutes to read • Edit Online

This article discusses some common issues when using the On-premises data gateway.

NOTE
If you encounter an issue that is not listed below, you can ask for further assistance in the following locations.
For Power BI, you can use the communities site or you can create a support ticket.
For PowerApps, you can use the communities site or you can create a support ticket.
For Microsoft Flow, you can use the communities site of you can create a support ticket.
For Logic Apps, you can submit a support ticket through the Azure portal.

Update to the latest version

A lot of issues can surface when the gateway version is out of date. It is a good general practice to make sure you
are on the latest version. If you haven't updated the gateway for a month, or longer, you may want to consider
installing the latest version of the gateway and see if you can reproduce the issue.

Common issues
Here are a few common issues and resolutions that have helped a number of customers in environments that
restrict internet access.
Authentication to proxy server
Your proxy may require authentication from a domain user account. By default, the gateway uses a Service SID for
the windows service log on user. Changing the log on user to a domain user can help with this. For more
information, see Changing the gateway service account to a domain user.
Your proxy only allows ports 80 and 443 traffic
Some proxies restrict traffic to only ports 80 and 443. By default, communication to Azure Service Bus will occur on
ports other than 443.
You can force the gateway to communicate with Azure Service Bus using HTTPS instead of direct TCP. You will
need to modify the Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file. Change the value from
AutoDetect to Https . This file is located, by default, at C:\Program Files\On-premises data gateway.

<setting name="ServiceBusSystemConnectivityModeString" serializeAs="String">

<value>Https</value>
</setting>

Installation
Error: Failed to add user to group. (-2147463168 PBIEgwService Performance Log Users )
You may receive this error if you are trying to install the gateway on a domain controller. Deploying on a domain
controller is not supported. You will need to deploy the gateway on a machine that is not a domain controller.
Installation fails
You may encounter installation failures if the anti-virus software on the installation machine is out of date. You can
either update the anti-virus installation, or disable anti-virus only for the duration of the gateway installation to
complete, then re-enable anti-virus.

Configuration
How to restart the gateway
The gateway runs as a Windows service, so you can start and stop it in a few ways. For example, you can open a
command prompt with elevated permissions on the machine where the gateway is running and then run either of
these commands:
To stop the service, run this command:

net stop PBIEgwService

To start the service, run this command:

net start PBIEgwService

Log file configuration

The gateway service logs are categorized into three buckets: information, error, and network. This categorization
provides a better troubleshooting experience that allows you to focus on a specific area, depending on the error or
issue. You can see the three categories in the following snippet from the gateway configuration file:
GatewayInfo.log,GatewayErrors.log,GatewayNetwork.log .

<system.diagnostics>
<trace autoflush="true" indentsize="4">
<listeners>
<remove name="Default" />
<add name="ApplicationFileTraceListener"

type="Microsoft.PowerBI.DataMovement.Pipeline.Common.Diagnostics.RotatableFilesManagerTraceListener,
Microsoft.PowerBI.DataMovement.Pipeline.Common"
initializeData="%LOCALAPPDATA%\Microsoft\On-premises data
gateway\,GatewayInfo.log,GatewayErrors.log,GatewayNetwork.log,20,50" />
</listeners>
</trace>
</system.diagnostics>

This file is located by default at: \Program Files\On-premises data

gateway\Microsoft.PowerBI.EnterpriseGateway.exe.config. To configure the number of log files to retain, change
the first number (20 in this example): GatewayInfo.log,GatewayErrors.log,GatewayNetwork.log,20,50 .
Error: Failed to create a gateway. Try again
All of the details are available, but the call to the Power BI service returned an error. The error and an activity id are
displayed. This could happen for different reasons. You can collect, and review, the logs, as mentioned below, to get
more details.
This could also be due to proxy configuration issues. The user interface does now allow for proxy configuration. You
can learn more about making proxy configuration changes
Error: Failed to update gateway details. Please try again
Information was received from the Power BI service to the gateway. The information was passed onto the local
windows service, but it failed to return. Alternatively, a symmetric key generation failed. The inner exception is
displayed under Show details. To get more details, you can collect and review the logs mentioned below.
Error: Power BI service reported local gateway as unreachable. Restart the gateway and try again
At the end of configuration, the Power BI service is called again to validate the gateway. The Power BI service does
not report the gateway as live. Restarting the windows service may allow the communication to be successful. You
can collect, and review, the logs, as mentioned below, to get more details.
Script error during sign into Power BI
You may receive a script error when signing into Power BI as part of the On-premises data gateway configuration.
Installing the following security update resolves the issue. This can be installed via Windows Update.
MS16-051: Security update for Internet Explorer: May 10, 2016 (KB 3154070)
Gateway configuration failed with a null reference exception
You may encounter an error similar to the following.

Failed to update gateway details. Please try again.

Error updating gateway configuration.

This includes a stack trace, and that stack trace may include the following message.

Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.CouldNotUpdateGatewayConfigurationException: Error
updating gateway configuration. ----> System.ArgumentNullException: Value cannot be null.
Parameter name: serviceSection

If you are upgrading from an older gateway, we preserve the config file. There may be a section that is missing.
When the gateway tries to read it, we can get the above null reference exception.
To correct this, do the following steps.
1. Uninstall the gateway.
2. Delete the following folder.

c:\Program Files\On-premises data gateway

3. Reinstall the gateway.

4. Optionally apply the recovery key to restore an existing gateway.

Support for TLS 1.2

By default, the On-premises data gateway uses Transport Layer Security (TLS ) 1.2 to communicate with the Power
BI service. To ensure all gateway traffic uses TLS 1.2, you might have to add or modify the following registry keys
on the machine running the gateway service:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]"SchUseStrongCrypto"=dword:00000001

NOTE
Adding or modifying these registry keys applies the change to all .NET applications. For information about registry changes
that affect TLS for other applications, see Transport Layer Security (TLS) registry settings.
Data sources
Error: Unable to Connect. Details: "Invalid connection credentials"
Within Show details, it displays the error message received from the data source. For SQL Server, you see
something like the following.

Login failed for user 'username'.

Verify that you have the correct username and password. Also, verify that those credentials can successfully connect
to the data source. Make sure the account being used matches the Authentication Method.
Error: Unable to Connect. Details: "Cannot connect to the database"
We were able to connect to the server, but not to the database supplied. Verify the name of the database, and that
the user credential as the proper permission to access that database.
Within Show details, it displays the error message received from the data source. For SQL Server, you see
something like the following.

Cannot open database "AdventureWorks" requested by the login. The login failed. Login failed for user
'username'.

Error: Unable to Connect. Details: "Unknown error in data gateway"

This error could occur for different reasons. Be sure to validate that you can connect to the data source from the
machine hosting the gateway. This could be the result of the server not being accessible.
Within Show details, you can see an error code of DM_GWPipeline_UnknownError.
You can also look in the Event Logs > Applications and Services Logs > On-premises data gateway Service
for more details.
Error: We encountered an error while trying to connect to . Details: "We reached the data gateway, but the
gateway can't access the on-premises data source."
We were unable to connect to the specified data source. Be sure to validate the information provided for that data
source.
Within Show details, you can see an error code of DM_GWPipeline_Gateway_DataSourceAccessError.
If the underlying error message is similar to the following, this means that the account you are using for the data
source is not a server admin for that Analysis Services instance. Learn more

The 'CONTOSO\account' value of the 'EffectiveUserName' XML for Analysis property is not valid.

If the underlying error message is similar to the following, it could mean that the service account for Analysis
Services may be missing the token-groups-global-and-universal (TGGAU ) directory attribute.

The username or password is incorrect.

Domains with Pre-Windows 2000 compatibility access have the TGGAU attribute enabled. However, most newly
created domains do not enable this attribute by default. You can read more about this here.
You can confirm this by doing the following.
1. Connect to the Analysis Services machine within SQL Server Management Studio. Within the Advanced
connection properties, include EffectiveUserName for the user in question and see if this reproduces the
 error.
2. You can use the dsacls Active Directory tool to validate whether the attribute is listed. This is a tool found on
a domain controller. You need to know what the distinguished domain name is for the account and pass that
to the tool.

dsacls "CN=John Doe,CN=UserAccounts,DC=contoso,DC=com"

You want to see something similar to the following in the results.

Allow BUILTIN\Windows Authorization Access Group

SPECIAL ACCESS for tokenGroupsGlobalAndUniversal
READ PROPERTY

To correct this issue, you need to enable TGGAU on the account used for the Analysis Services windows service.
Another possibility for username or password incorrect
This error could also be caused if the Analysis Services server is in a different domain than the users and there is
not a two-way trust established.
You need to work with your domain administrators to verify the trust relationship between domains.
Unable to see the data gateway data sources in the 'Get Data' experience for Analysis Services from the Power BI service
Make sure that your account is listed in the Users tab of the data source within the gateway configuration. If you
don't have access to the gateway check with the administrator of the gateway and ask them to verify. Only accounts
in the Users list can see the data source listed in the Analysis Services list.
Error: You don't have any gateway installed or configured for the data sources in this dataset
Ensure that you have added one or more data sources to the gateway, as described in Add a data source. If the
gateway doesn't appear in the admin portal under Manage gateways, try clearing your browser cache or signing
out of the service then signing back in.

Datasets
Error: There is not enough space for this row
This occurs if you have a single row greater than 4 MB in size. You need to determine what the row is from your
data source and attempt to filter it out or reduce the size for that row.
Error: The server name provided doesn't match the server name on the SQL Server SSL Certificate
This can occur when the certificate CN is for the servers fully qualified domain name (FQDN ), but you only
supplied the NetBIOS name for the server. This causes a mismatch for the certificate. To resolve this issue, you
need to make the server name within the gateway data source, and the PBIX file, to use the FQDN of the server.
I don't see the On-premises data gateway present when configuring scheduled refresh
This could be because of a few different scenarios.
1. The server and database name don't match between what was entered in Power BI Desktop and the data source
configured for the gateway. These need to be the same values. They are not case-sensitive.
2. Your account is not listed in the Users tab of the data source within the gateway configuration. You need to get
with the administrator of the gateway to be added to that list.
3. Your Power BI Desktop file has multiple data sources within it and not all of those data sources are configured
with the gateway. You need to have each data source defined with the gateway for the gateway to show up
within Scheduled Refresh.
Error: The received uncompressed data on the gateway client has exceeded the limit
The exact limitation is 10 GB of uncompressed data per table. If you are hitting this issue, there are good options to
optimize and avoid the issue. In particular, reducing the use of highly constant, long string values and instead using
a normalized key or removing the column (if not in use) helps.

Reports
Report could not access the data source because you do not have access to our data source via an On-premises
data gateway
This is usually caused by one of the following.
1. The data source information does not match what is in the underlying dataset. The server and database name
need to match between the data source defined for the On-premises data gateway and what you supply within
Power BI Desktop. If you use an IP Address in Power BI Desktop, the data source, for the On-premises data
gateway, needs to use an IP Address as well.
2. There is not a data source available on any gateway within your organization. You can configure the data source
on a new, or existing On-premises data gateway.
Error: Data source access error. Please contact the gateway administrator
If this report is making use of a live Analysis Services connection, you could be encountering an issue with a value
being passed to EffectiveUserName that is either not valid or doesn't have permissions on the Analysis Services
machine. Typically, an authentication issue is due to the fact that the value being passed for EffectiveUserName
doesn't match a local user principal name (UPN ).
To confirm this, you can do the following.
1. Find the effective username within the gateway logs.
2. Once you have the value being passed, validate that it is correct. If it is your user, you can use the following
command from a command prompt to see the UPN. The UPN looks like an email address.

whoami /upn

Optionally, you can see what Power BI gets from Azure Active Directory.
1. Browse to https://developer.microsoft.com/graph/graph-explorer.
2. Select Sign in in the upper right.
3. Run the following query. You see a rather large JSON response.

https://graph.windows.net/me?api-version=1.5

4. Look for userPrincipalName.

If your Azure Active Directory UPN doesn't match your local Active Directory UPN, you can use the Map
usernames feature to replace it with a valid value. Or you can work with either your tenant admin or local Active
Directory admin, to get your UPN changed.

Firewall or Proxy
For information on providing proxy information for your gateway, see Configuring proxy settings for the Power BI
gateways.
You can test to see if your firewall, or proxy, may be blocking connections by running Test-NetConnection from a
PowerShell prompt. This will test connectivity to the Azure Service Bus. This only tests network connectivity and
doesn't have anything to do with the cloud server service or the gateway. It helps to determine if your machine can
actually get out to the internet.

Test-NetConnection -ComputerName watchdog.servicebus.windows.net -Port 9350

NOTE
Test-NetConnection is only available on Windows Server 2012 R2 and later. It is also available on Windows 8.1 and later. On
earlier OS versions, you can use Telnet to test port connectivity.

The results should look similar to the following. The difference will be with TcpTestSucceeded. If
TcpTestSucceeded is not true, then you may be blocked by a firewall.

ComputerName : watchdog.servicebus.windows.net
RemoteAddress : 70.37.104.240
RemotePort : 5672
InterfaceAlias : vEthernet (Broadcom NetXtreme Gigabit Ethernet - Virtual Switch)
SourceAddress : 10.120.60.105
PingSucceeded : False
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded : True

If you want to be exhaustive, substitute the ComputerName and Port values with those listed for ports
The firewall may also be blocking the connections that the Azure Service Bus makes to the Azure data centers. If
that is the case, you will want to whitelist (unblock) the IP addresses for your region for those data centers. You can
get a list of Azure IP addresses here.
You can find the data center region you are in by doing the following:
1. Select the ? in the upper right of the Power BI service.
2. Select About Power BI.
3. Your data region is listed in Your data is stored in.

If you are still not getting anywhere, you could try getting a network trace using a tool like fiddler or netsh,
although these are advanced collection methods and you may need assistance in analyzing the collected data. You
can contact support for assistance.

Performance
https://www.youtube.com/embed/IJ_DJ30VNk4?showinfo=0
Performance Counters
There are a number of performance counters that can be used to gauge the activities for the gateway. These can be
helpful to understand if we have a large load of activity and may need to make a new gateway. These counters do
not reflect how long something takes.
These counters can be accessed through the Windows Performance Monitor tool.

There are general groupings of these counters.

COUNTER TYPE DESCRIPTION

ADO.NET This is used for any DirectQuery connection.

ADOMD This is used for Analysis Services 2014 and earlier.

OLEDB Certain data sources use this. This includes SAP HANA and
Analysis Service 2016 or later.

Mashup This includes any imported data source. If you are scheduling
refresh or doing an on-demand refresh, it goes through the
mashup engine.

Here is a listing of the available performance counters.

COUNTER DESCRIPTION

# of ADO.NET open connection executed / sec Number of ADO.NET open connection actions executed per
second (succeeded or failed).

# of ADO.NET open connection failed / sec Number of ADO.NET open connections actions failed per
second.

# of ADO.NET queries executed / sec Number of ADO.NET queries executed per second (succeeded
or failed).

# of ADO.NET queries failed / sec Number of ADO.NET failed queries executed per second.

# of ADOMD open connection executed / sec Number of ADOMD open connection actions executed per
second (succeeded or failed).

# of ADOMD open connection failed / sec Number of ADOMD open connection actions failed per
second.

# of ADOMD queries executed / sec Number of ADOMD queries executed per second (succeeded
or failed).
 COUNTER DESCRIPTION

# of ADOMD queries failed / sec Number of ADOMD failed queries executed per second.

# of all open connection executed / sec Number of open connection actions executed per second
(succeeded or failed).

# of all open connection failed / sec Number of failed open connection actions executed per
second.

# of all queries executed / sec Number of queries executed per second (succeeded or failed).

# of items in the ADO.NET connection pool Number of items in the ADO.NET connection pool.

# of items in the OLEDB connection pool Number of items in the OLEDB connection pool.

# of items in the Service Bus pool Number of items in the Service Bus pool.

# of Mashup open connection executed / sec Number of Mashup open connection actions executed per
second (succeeded or failed).

# of Mashup open connection failed / sec Number of Mashup open connection actions failed per second.

# of Mashup queries executed / sec Number of Mashup queries executed per second (succeeded
or failed).

# of Mashup queries failed / sec Number of Mashup failed queries executed per second

# of OLEDB multiple result set queries failed / sec Number of multiple result sets of OLEDB failed queries
executed per second.

# of OLEDB multiple result sets of queries executed / sec Number of OLEDB multiple result sets of queries executed per
second (succeeded or failed).

# of OLEDB open connection executed / sec Number of OLEDB open connection actions executed per
second (succeeded or failed).

# of OLEDB open connection failed / sec Number of OLEDB open connection actions failed per second.

# of OLEDB queries executed / sec Number of OLEDB multiple result sets of queries executed per
second (succeeded or failed).

# of OLEDB queries failed / sec Number of OLEDB multiple result sets of failed queries
executed per second.

# of OLEDB single result set queries executed / sec Number of OLEDB single result set queries executed per
second (succeeded or failed).

# of queries failed / sec Number of failed queries executed per second.

# of single result set OLEDB queries failed / sec Number of single result set OLEDB failed queries executed per
second.

Reviewing slow performing queries

You may find that response through the gateway is slow. This could be for DirectQuery queries or when refreshing
your imported dataset. You can enable additional logging to output queries and their timings to help understand
what is performing slow. When you find a long-running query, it may require additional modification on your data
source to tune query performance. For example, adjusting indexes for a SQL Server query.
You need to modify two configuration files to determine the duration of a query.
Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config
Within the Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file, change the EmitQueryTraces
value from False to True . This file is located, by default, at C:\Program Files\On-premises data gateway. Enabling
EmitQueryTraces begins to log queries that are sent from the gateway to a data source.

IMPORTANT
Enabling EmitQueryTraces could increase the log size significantly depending on gateway usage. Once you are done reviewing
the logs, you can need to set EmitQueryTraces to False. It is not recommended to leave this setting enabled long term.

<setting name="EmitQueryTraces" serializeAs="String">

<value>True</value>
</setting>

Example query entry

DM.EnterpriseGateway Information: 0 : 2016-09-15T16:09:27.2664967Z DM.EnterpriseGateway 4af2c279-1f91-4c33-

ae5e-b3c863946c41 d1c77e9e-3858-4b21-3e62-1b6eaf28b176 MGEQ c32f15e3-699c-4360-9e61-2cc03e8c8f4c
FF59BC20 [DM.GatewayCore] Executing query (timeout=224) "<pi>
SELECT
TOP (1000001) [t0].[ProductCategoryName],[t0].[FiscalYear],SUM([t0].[Amount])
AS [a0]
FROM
(
(select [$Table].[ProductCategoryName] as [ProductCategoryName],
[$Table].[ProductSubcategory] as [ProductSubcategory],
[$Table].[Product] as [Product],
[$Table].[CustomerKey] as [CustomerKey],
[$Table].[Region] as [Region],
[$Table].[Age] as [Age],
[$Table].[IncomeGroup] as [IncomeGroup],
[$Table].[CalendarYear] as [CalendarYear],
[$Table].[FiscalYear] as [FiscalYear],
[$Table].[Month] as [Month],
[$Table].[OrderNumber] as [OrderNumber],
[$Table].[LineNumber] as [LineNumber],
[$Table].[Quantity] as [Quantity],
[$Table].[Amount] as [Amount]
from [dbo].[V_CustomerOrders] as [$Table])
)
AS [t0]
GROUP BY [t0].[ProductCategoryName],[t0].[FiscalYear] </pi>"

Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.dll.config
Within the Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.dll.config file, change the TracingVerbosity
value from 4 to 5 . This file is located, by default, at C:\Program Files\On-premises data gateway. Changing this
setting begins to log verbose entries to the gateway log. This includes entries that show duration. You can also
enable verbose entries by enabling the "Additional Logging" button in the On-Premises Gateway application.
 IMPORTANT
Enabling TracingVerbosity to 5 could increase the log size significantly depending on gateway usage. Once you are done
reviewing the logs, you need to set TraceVerbosity to 4 . It is not recommended to leave this setting enabled long term.

<setting name="TracingVerbosity" serializeAs="String">

<value>5</value>
</setting>

Activity Types
ACTIVITY TYPE DESCRIPTION

MGEQ Queries executed over ADO.NET. This includes DirectQuery

data sources.

MGEO Queries executed over OLEDB. This includes SAP HANA and
Analysis Services 2016.

MGEM Queries executed from the Mashup engine. This is used with
imported datasets that use scheduled refresh or refresh on-
demand.

Determine the duration of a query

To determine the time it took to query the data source, you can do the following.
1. Open the gateway log.
2. Search for an Activity Type to find the query. An example of this would be MGEQ.
3. Make a note of the second GUID as this is the request id.
4. Continue to search for MGEQ until you find the FireActivityCompletedSuccessfullyEvent entry with the
duration. You can verify the entry has the same request id. Duration is in milliseconds.

DM.EnterpriseGateway Verbose: 0 : 2016-09-26T23:08:56.7940067Z DM.EnterpriseGateway baf40f21-2eb4-

4af1-9c59-0950ef11ec4a 5f99f566-106d-c8ac-c864-c0808c41a606 MGEQ 21f96cc4-7496-bfdd-748c-
b4915cb4b70c B8DFCF12 [DM.Pipeline.Common.TracingTelemetryService] Event:
FireActivityCompletedSuccessfullyEvent (duration=5004)

NOTE
FireActivityCompletedSuccessfullyEvent is a verbose entry. This entry is not logged unless TraceVerbosity is at level 5.

Firewall or Proxy
For information on providing proxy information for your gateway, see Configuring proxy settings for the Power BI
gateways.
You can test to see if your firewall, or proxy, may be blocking connections by running Test-NetConnection from a
PowerShell prompt. This tests connectivity to the Azure Service Bus. This only tests network connectivity and don't
have anything to do with the cloud server service or the gateway. It helps to determine if your machine can actually
get out to the internet.

Test-NetConnection -ComputerName watchdog.servicebus.windows.net -Port 9350

NOTE
Test-NetConnection is only available on Windows Server 2012 R2 and later. It is also available on Windows 8.1 and later. On
earlier OS versions, you can use Telnet to test port connectivity.

The results look similar to the following. The difference is with TcpTestSucceeded. If TcpTestSucceeded is not true,
then you may be blocked by a firewall.

ComputerName : watchdog.servicebus.windows.net
RemoteAddress : 70.37.104.240
RemotePort : 5672
InterfaceAlias : vEthernet (Broadcom NetXtreme Gigabit Ethernet - Virtual Switch)
SourceAddress : 10.120.60.105
PingSucceeded : False
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded : True

If you want to be exhaustive, substitute the ComputerName and Port values with those listed for ports
The firewall may also be blocking the connections that the Azure Service Bus makes to the Azure data centers. If
that is the case, you want to whitelist (unblock) the IP addresses for your region for those data centers. You can get
a list of Azure IP addresses here.
Network Ports Test
The network ports test is a tool to check if your gateway can access the correct ports for all remote servers that are
required by your gateway for transferring data. If the network ports test fails to connect to any of the ports, your
gateway may experience network issues. If you are currently experiencing network issues with your gateway, run a
network ports test to ensure that you have the optimal network environment.
Start a new test
To run a new network ports test, in theOn-premises data gatewayuser interface.

When executing the network ports test, your gateway retrieves a list of ports and servers from Azure Service Bus
and then it attempts to connect to all the servers and ports. When the Start new test link reappears, the network
ports test has finished executing.
Test results
A summary of the test can be seen below the Start new test link as Recent test results. The two results are
Completed (Succeeded) and Completed (Failed, see last test results). If the test succeeded, then your gateway
successfully connected to all the required ports. If the test failed, then your network environment may be blocking
these required ports and servers.
To view the results of the last completed test, select the Open last completed test results link, as seen below. The
test results open in Windows’ default text editor.
The test results list all the servers, ports, and IP addresses that are required by your gateway. If the test results
display Closed for any ports as shown below, ensure that your network environment is not blocking the connection.
You may need to contact your network administrator to open the required ports.
Kerberos
If the underlying database server and On-premises data gateway are not appropriately configured for Kerberos
Constrained Delegation, enable verbose logging on the gateway, and investigate based on the errors/traces in the
gateway’s log files as a starting point for troubleshooting.
ImpersonationLevel
The ImpersonationLevel is related to the SPN setup or the local policy setting.

[DataMovement.PipeLine.GatewayDataAccess] About to impersonate user DOMAIN\User (IsAuthenticated: True,

ImpersonationLevel: Identification)

Solution
Follow these steps to solve the issue:
1. Setup an SPN for the On-Premises Gateway
2. Setup constrained delegation in your Active Directory (AD )
FailedToImpersonateUserException: Failed to create windows identity for user userid
The FailedToImpersonateUserException happens if you are not able to impersonate on behalf of another user. This
could also happen if the account you are trying to impersonate is from another domain than the one the gateway
service domain is on (this is a limitation).
Solution
Verify that the configuration is correct as per the steps in the ImpersonationLevel section above
Ensure that the userid it's trying to impersonate is a valid AD Account
General error; 1033 error while parsing the protocol
You get the 1033 error when your external ID that is configured in SAP HANA is not matching the login if the user
is impersonated using the UPN ([email protected]). In the logs you see the “Original UPN '[email protected]'
replaced with a new UPN '[email protected]' at the top of the error logs as seen below.”

[DM.GatewayCore] SingleSignOn Required. Original UPN '[email protected]' replaced with new UPN
'[email protected].'

Solution
SAP HANA requires the impersonated user to use the sAMAccountName attribute in AD (user alias). If this
is not correct, you see the 1033 error.

In the logs you see the sAMAccountName (alias) and not the UPN, which is the alias followed by the domain
([email protected])

<setting name="ADUserNameReplacementProperty" serializeAs="String">

<value>sAMAccount</value>
</setting>
<setting name="ADServerPath" serializeAs="String">
<value />
</setting>
<setting name="CustomASDataSource" serializeAs="String">
<value />
</setting>
<setting name="ADUserNameLookupProperty" serializeAs="String">
<value>AADEmail</value>

[SAP AG ][LIBODBCHDB DLL ][HDBODBC ] Communication link failure;-10709 Connection failed (RTE:[-1]
Kerberos error. Major: "Miscellaneous failure [851968]", minor: "No credentials are available in the security
package
You get the -10709 Connection failed error message if your delegation is not configured correctly in AD.
Solution
Ensure you have the SAP Hana server on the delegation tab in AD for the gateway service account
Tools for troubleshooting
Collecting logs from the gateway configurator
There are several logs you can collect for the gateway, and you should always start with the logs. The simplest way
to collect logs after installing the gateway is through the user interface. In the On-premises data gateway user
interface, select Diagnostics and then select the Export logs link near the bottom of the page, as shown in the
following image.
Installer logs

%localappdata%\Temp\On-premises_data_gateway_*.log

Configuration logs

%localappdata%\Microsoft\On-premises Data Gateway\GatewayConfigurator*.log

On-premises data gateway service logs

C:\Users\PBIEgwService\AppData\Local\Microsoft\On-premises Data Gateway\Gateway*.log

Event Logs
The On-premises data gateway service event logs are present under Application and Services Logs.
Fiddler Trace
Fiddler is a free tool from Telerik that monitors HTTP traffic. You can see the back and forth with the Power BI
service from the client machine. This may show errors and other related information.

Refresh History
When using the gateway for a scheduled refresh, Refresh History can help you see what errors have occurred, as
well as provide useful data if you need to create a support request. You can view both scheduled, as well as on-
demand, refreshes. Here is how you can get to the Refresh History.
1. In the Power BI navigation pane, in Datasets, select a dataset > Open Menu > Schedule Refresh.

2. In Settings for... > Schedule Refresh, select Refresh History.

For additional information about troubleshooting refresh scenarios, take a look at the Troubleshooting Refresh
Scenarios article.

Next steps
Configuring proxy settings for the Power BI gateways
On-premises data gateway
On-premises data gateway - in-depth
Manage your data source - Analysis Services
Manage your data source - SAP HANA
Manage your data source - SQL Server
Manage your data source - Import/Scheduled refresh
More questions? Try the Power BI Community
 Troubleshooting Power BI Gateway - Personal
1/14/2019 • 7 minutes to read • Edit Online

The following goes through some common issues you may encounter when using the Power BI Gateway -
Personal.

NOTE
The current version of the gateway for personal use is the On-premises data gateway (personal). Please update your
installation to use that version.

Update to the latest version

A lot of issues can surface when the gateway version is out of date. It is a good general practice to make sure you
are on the latest version. If you haven't updated the gateway for a month, or longer, you may want to consider
installing the latest version of the gateway and see if you can reproduce the issue.

Installation
Personal gateway is 64bit - If your machine is 32bit, you will not be able to install the personal gateway. Your
operating system needs to be 64bit. You will need to install a 64bit version of Windows, or install the personal
gateway on a 64bit machine.
Personal gateway fails to install as a service even though you are a local administrator for the
computer - Installation can fail if the user is in the computer’s local Administrator group, but group policy does
not allow that username to log on as a service. At the moment, ensure the group policy allows a user to log on as
a service. We’re working on a fix for this issue. Learn more
Operation timed out - This is common if the computer (physical machine or VM ) on which you’re installing the
personal gateway has a single core processor. Close any applications and turn off any non-essential processes
and try installing again.
Data Management Gateway or Analysis Services Connector cannot be installed on the same computer
as personal gateway - If you already have an Analysis ServicesConnector or Data Management Gateway
installed, you must first uninstall the Connector or the gateway and then try installing the personal gateway.

NOTE
If you encounter an issue during installation, the setup logs could provide information to help you resolve the issue. See
Setup Logs for more information.

Proxy configuration You may encounter issues with configuring the personal gateway if your environment
needs the use of a proxy. To learn more about how to configure proxy information, see Configuring proxy
settings for the Power BI Gateways

Schedule refresh
Error: The credential stored in the cloud is missing.
You could get this error in Settings for <dataset> if you have a scheduled refresh and then uninstalled and re-
installed the personal gateway. When you uninstall a personal gateway, data source credentials for a dataset that
has been configured for refresh are removed from the Power BI service.
Solution: In Power BI, go to the refresh settings for a dataset. In Manage Data Sources, for any data source with
an error, click Edit credentials and sign in to the data source again.
Error: The credentials provided for the dataset are invalid. Please update the credentials through a
refresh or in the Data Source Settings dialog to continue.
Solution: If you get a credentials message, it could mean:
Make sure usernames and passwords used to sign into data sources are up to date. In Power BI, go to
refresh settings for the dataset. In Manage Data Sources, click Edit credentials to update the credentials
for the data source.
Mashups between a cloud source and an on-premises source, in a single query, will fail to refresh in the
personal gateway if one of the sources is using OAuth for authentication. An example of this is a mashup
between CRM Online and a local SQL Server. This will fail because CRM Online requires OAuth.
This is a known issue, and being looked at. To work around the problem, have a separate query for the
cloud source and the on-premises source and use a merge or append query to combine them.
Error: Unsupported data source.
Solution: If you get an unsupported data source message in Schedule Refresh settings, it could mean:
The data source is not currently supported for refresh in Power BI.
The Excel workbook does not contain a data model, only worksheet data. Power BI currently only supports
refresh if the uploaded Excel workbook contains a data model. When you import data using Power Query in
Excel, be sure to choose the option to Load data to data model. This ensures data is imported into a data
model.
Error: [Unable to combine data] <query part>/<…>/<…> is accessing data sources that have privacy
levels which cannot be used together. Please rebuild this data combination.
Solution: This error is due to the privacy level restrictions and the types of data sources you are using.
Error: Data source error: We cannot convert the value "[Table]" to type Table.
Solution: This error is due to the privacy level restrictions and the types of data sources you are using.
Error: There is not enough space for this row.
This will occur if you have a single row greater than 4 MB in size. You will need to determine what the row is
from your data source and attempt to filter it out or reduce the size for that row.

Data sources
Missing data provider – The personal gateway is 64-bit only. It requires a 64-bit version of the data providers
to be installed on the same computer where the personal gateway is installed. For example, if the data source in
the dataset is Microsoft Access, you must install the 64-bit ACE provider on the same computer where you
installed the personal gateway.

NOTE
If you have 32 bit Excel, you cannot install a 64-bit ACE provider on the same computer.

Windows authentication is not supported for Access database - Power BI currently only supports
anonymous for Access database. We are working on enabling Windows authentication for Access database.
Sign in error when entering credentials for a datasource - If you get an error similar to this when entering
Windows credentials for a data source, you might still be on an older version of the personal gateway. Install the
latest version of Power BI Gateway - Personal.

Error: Sign in error when selecting Windows authentication for a data source using ACE OLEDB - If you
get the following error when entering data source credentials for a data source using ACE OLEDB provider:

Power BI does not currently support Windows authentication for a data source using ACE OLEDB provider.
Solution: To work around this error, you can select Anonymous authentication. For legacy ACE OLEDB provider,
Anonymous credentials are equivalent to Windows credentials.

Tile refresh
If you are receiving an error with dashboard tiles refreshing, please refer to the following article.
Troubleshooting tile errors

Tools for troubleshooting

Refresh History
Refresh History can help you see what errors have occurred, as well as provide useful data if you should need
to create a support request. You can view both scheduled, as well as on demand, refreshes. Here is how you can
get to the Refresh History.
1. In the Power BI navigation pane, in Datasets, select a dataset > Open Menu > Schedule Refresh.

2. In Settings for... > Schedule Refresh, select Refresh History.

Event logs
There are several event logs that can provide information. The first two, Data Management Gateway and
PowerBIGateway, are present if you are an admin on the machine. If you are not an admin, and you are using
the Personal Gateway, you will see the log entries within the Application log.
The Data Management Gateway and PowerBIGateway logs are present under Application and Services
Logs.

Fiddler trace
Fiddler is a free tool from Telerik that monitors HTTP traffic. You can see the back and forth with the Power BI
service from the client machine. This may show errors and other related information.

Setup Logs
If the Personal Gateway, fails to install, you will see a link to show the setup log. This could show you details
about the failure. These are Windows Install logs, or also knows as MSI logs. They can be fairly complex and
hard to read. Typically the resulting error will be at the bottom, but determining the cause of the error is not
trivial. It could be a result of errors in a different log, or be a result of an error higher up in the log.

Alternatively, you can go to your Temp folder (%temp%) and look for files that start with Power_BI_.
 NOTE
Going to %temp% may take you to a subfolder of temp. The Power_BI_ files will be in the root of the temp directory. You
may need to go up a level or two.

Next steps
Configuring proxy settings for the Power BI Gateways
Data Refresh
Power BI Gateway - Personal
Troubleshooting tile errors
Troubleshooting the On-premises data gateway
More questions? Try the Power BI Community
 Troubleshooting unsupported data source for refresh
1/14/2019 • 2 minutes to read • Edit Online

You may see an error when trying to configured a dataset for scheduled refresh.

You cannot schedule refresh for this dataset because it gets data from sources that currently don’t
support refresh.

This happens when the data source you used, within Power BI Desktop, isn’t supported for refresh. You will need
to find the data source that you are using and compare that against the list of supported data sources at Refresh
data in Power BI.

Find the data source

If you aren’t sure what data source was used, you can find that using the following steps within Power BI Desktop.
1. In Power BI Desktop, make sure you are on the Report pane.

2. Select Edit Queries from the ribbon bar.

3. Select Advanced Editor.

4. Make note of the provider listed for the source. In this example, the provider is ActiveDirectory.

5. Compare the provider with the list of supported data sources found within Refresh data in Power BI. You will
find that Active Directory is not a supported data source for refresh.

Next steps
Data Refresh
Power BI Gateway - Personal
On-premises data gateway
Troubleshooting the On-premises data gateway
Troubleshooting the Power BI Gateway - Personal
More questions? Try asking the Power BI Community
 Troubleshooting scheduled refresh for Azure SQL
Databases in Power BI
1/14/2019 • 2 minutes to read • Edit Online

For detailed steps on setting up scheduled refresh, be sure to see Refresh data in Power BI.
While setting up scheduled refresh for Azure SQL Database, if you get an error with error code 400 during editing
the credentials, try the following to set up the appropriate firewall rule:
1. Log into your Azure management portal
2. Go to the Azure SQL server you are configuring refresh for
3. Turn on 'Windows Azure Services' in the allowed services section

More questions? Try the Power BI Community

 Error: We couldn't find any data in your Excel
workbook
1/14/2019 • 2 minutes to read • Edit Online

NOTE
This article applies to Excel 2007 and later.

When you import an Excel workbook into Power BI, you may see the following error:
Error: We couldn't find any data in your Excel workbook. Your data might not be formatted properly. You'll need to
edit your workbook in Excel and then import it again.

Quick solution
1. Edit your workbook in Excel.
2. Select the range of cells that contain your data. The first row should contain your column headers (the column
names).
3. Press Ctrl + T to create a table.
4. Save your workbook.
5. Return to Power BI and import your workbook again, or if you're working in Excel 2016 and you've saved your
workbook to OneDrive for Business, in Excel, click File > Publish.

Details
Cause
In Excel, you can create a table out of a range of cells, which makes it easier to sort, filter, and format data.
When you import an Excel workbook, Power BI looks for these tables and imports them into a dataset; if it doesn't
find any tables, you'll see this error message.
Solution
1. Open your workbook in Excel.

NOTE
The pictures here are of Excel 2013. If you're using a different version, things may look a little different, but the steps
are the same.
2. Select the range of cells that contain your data. The first row should contain your column headers (the
column names):

3. In the ribbon on the INSERT tab, click Table. (Or, as a shortcut, press Ctrl + T.)
4. You'll see the following dialog. Make sure My table has headers is checked, and select OK:

5. Now your data is formatted as a table:

6. Save your workbook.

7. Return to Power BI. Select Get Data at the bottom of the left navigation pane.
8. In the Files box, select Get.

9. Import your Excel workbook again. This time, the import should find the table and succeed.
If the import still fails, let us know by clicking **Community **in the help menu:
 Troubleshooting tile errors
2/11/2019 • 3 minutes to read • Edit Online

Below are the common errors you may encounter with tiles along with an explanation.

NOTE
If you encounter an error that is not listed below, and it is causing you issues, you can ask for further assistance on the
community site, or you can create a support ticket.

Errors
Power BI encountered an unexpected error while loading the model. Please try again later. or Couldn't
retrieve the data model. Please contact the dashboard owner to make sure the data sources and model
exist and are accessible.
We weren't able to access your data because the data source wasn't reachable. This issue could happen if the data
source was removed, renamed, moved, offline, or permissions have changed. Check that the source is still in the
location we are pointing to and you still have permission to access it. If that isn't the issue, the source may be slow.
Try again later during a time when the load on the source is smaller. If it is an on-premises source, the data source
owner may be able to provide more information.
You don’t have permission to view this tile or open the workbook.
Contact the dashboard owner to make sure the data sources and model exist and are accessible for your account.
Custom visuals have been disabled by your administrator.
Your Power BI administrator has disabled the usage of custom visuals for your organization or your security
group. You will not be able to use custom visuals from the Microsoft marketplace or import private visuals from a
file. You will be able to use only the pre-packed set of visuals.
Data shapes must contain at least one group or calculation that outputs data. Please contact the
dashboard owner.
We don't have any data to display because the query is empty. Try adding some fields from the field list to your
visual and repinning it.
Can't display the data because Power BI can't determine the relationship between two or more fields.
You are trying to use two or more fields from tables that are not related. You need to remove the unrelated fields
from the visual and then create a relationship between the tables. Once you have done this change, you can add
the fields back to the visual. This can be done in Power BI Desktop or Power Pivot for Excel. Learn more
The groups in the primary axis and the secondary axis overlap. Groups in the primary axis can't have
the same keys as groups in the secondary axis.
It is usually a transient issue. This will typically happen when you are moving groups from rows to columns. In this
case, the error should disappear when you finish moving all the groups. If you still see the message, try switching
fields between the rows and columns or the axis legend or removing fields from the visual.
This visual has exceeded the available resources. Try filtering to decrease the amount of data displayed.
Your visual has attempted to query too much data for us to complete the result with the available resources. Try
filtering the visual to reduce the amount of data in the result.
We are not able to identify the following fields: {0}. Please update the visual with fields that exist in the
dataset.
The field was likely deleted or renamed. You can remove the broken field from the visual, add a different field, and
repin it.
Couldn't retrieve the data for this visual. Please try again later.
This is usually a transient issue. If you try again later and you still see this message, contact support.

Contact support
If you are still having an issue, contact support to investigate further.

Next steps
Troubleshooting the On-premises data gateway
Troubleshooting Power BI Personal Gateway
More questions? Try the Power BI Community
 How to refresh your Xero content pack credentials if
refresh failed
1/14/2019 • 2 minutes to read • Edit Online

If you use the Xero Power BI content pack, you may have experienced some problems with the content pack’s daily
refresh due to a recent Power BI service incident.
You can see if your content pack refreshed successfully by checking the last refresh status for your Xero dataset as
shown in the screenshot below.

If you do see that refresh failed as shown above, please follow these steps to renew your content pack credentials.
1. Click the ellipsis (...) next to your Xero dataset, then click Schedule refresh. This opens the settings page for
the Xero content pack.

2. In the Settings for Xero page, select Data source credentials > Edit credentials.
3. Enter your organization’s name > Next.

4. Sign in with your Xero account.

5. Now that your credentials are updated, let’s make sure the refresh schedule is set to run daily. Check that by
clicking the ellipsis (...) next to your Xero dataset, then clicking Schedule refresh again.

6. You can also choose to refresh the dataset immediately. Click the ellipsis (...) next to your Xero dataset, then
click Refresh now.

If you are still having refresh issues, please don’t hesitate to reach out to us at http://support.powerbi.com
To learn more about the Xero content pack for Power BI, please visit the Xero content pack help page.
Next steps
More questions? Try the Power BI Community
 Troubleshooting sign-in issues for Power BI
3/13/2019 • 2 minutes to read • Edit Online

This article describes how to get support when you are experiencing Power BI sign-in issues.
The first action you need to take is to engage your organization's internal support team for assistance.
However, if you are a tenant admin for your organization and you still can't sign into Power BI, then continue with
the information below.

Engage the support team

First, try to create a support ticket through the Power BI support page.
If you are unable to go through the Power BI support page, then try to create a ticket via the Office 365 (O365)
support page.
If you're unable to create a ticket either through the Power BI support page or through O365, then try to contact
support via phone.
For customers in the United States (US ) and the rest of the Americas: +1-800-936-5800
For customers in Europe, the Middle East, and Asia (EMEA): +44-844-800-2400
For customers in India: +1-800-419-5666
Another option to contact Microsoft support for help is by purchasing Microsoft Premier support. If you know
your organization has purchased Microsoft Premier support and you still can't create a case from any Power BI or
O365 channel, then you can contact Premier support via phone.
For customers in the United States (US ) and the rest of the Americas: +1-800-936-3100
For customers in Europe, the Middle East, and Asia (EMEA): +44-844-800-8338
For customers in India: +1-800-425-5666

NOTE
It is helpful to provide additional diagnostic information at the time you engage support.

Power BI community
If you're unable to create a forum post on the community page, it's because the Power BI community forum also
requires you to sign in.

Next steps
Here are a few sites you can visit for additional Power BI support:
Power BI Microsoft docs
Creating Power BI Support Cases
 Rename almost anything in Power BI service
1/14/2019 • 2 minutes to read • Edit Online

This article teaches you how to rename a dashboard, report, report page, workbook, dataset, app, and workspace in
Power BI service.
Can I change the name?

CONTENT TYPE I'M THE AUTHOR OR CREATOR SHARED WITH ME

Dashboard in a workspace Yes No

Report in a workspace Yes No

Workbook in a workspace Yes No

Dataset in a workspace Yes No

App workspace Yes, if you are the owner or have Admin No

permissions

Published apps Not from the App screen, but the app No
name can be changed from the app
workspace and re-published with a new
name if you have Admin permissions

App content (dashboard, report, Not from the App screen, but the app's No
workbook, dataset) content can be renamed from the app
workspace and re-published with a new
name if you have Admin permissions

Content in Shared with me No No

Rename a dashboard, report, or workbook

1. Start in a workspace and select the Dashboards, Reports, or Workbooks tab. Hover over the item to

rename, and select the gear icon . If there is no gear icon, you do not have permissions to rename.
2. On the Settings page, type the new name and select Save.

Rename a dataset
1. Start in a workspace and select the Datasets tab.
2. Hover over the item to rename, select the ellipses (...), and choose Rename.

NOTE
The options in the dropdown will vary.

3. On the Settings page, type a new name and select Save.

Rename an App workspace

Anyone with Admin permissions can rename an app workspace.
1. Start in the workspace you'd like to rename.
2. In the top-right corner, select the ellipses (...) and choose Edit workspace. If you don't see this option, then
you don't have permissions to rename this workspace.
3. Type a new workspace name and select Save.

Rename a page in a report

Don't like the name of a page in your Power BI report? A new name is just a click away. Pages can be renamed in
report Editing view .
1. Open the report in Editing View.
2. Locate the report page tabs at the bottom of the Power BI window.

3. Open the report page that you'd like to rename by selecting the tab.
4. Double-click the name on the tab to highlight it.

5. Type a new report page name and select ENTER.

Considerations and troubleshooting

If the item to be renamed has been shared with you, or is part of a content pack, you won't see the gear icon
 and you won't have access to Settings.
On the Datasets tab, if you don't see the ellipses (...), expand your browser window.
More questions? Try the Power BI Community
 Enroll your US Government organization in the
Power BI service
1/30/2019 • 5 minutes to read • Edit Online

The Power BI service has a version available for United States Government customers as part of the Office 365
US Government Community subscriptions. The Power BI service version discussed in this article is specifically
designed for US Government customers, and is separate and different from the commercial version of the Power
BI service.
For more information about the Power BI service for US Government, including its features and limitations,
check out Power BI for United States Government customers - Overview.

NOTE
This article is intended for administrators who have authority to sign up their US Government organization for Power BI. If
you are an end-user, contact your administrator about getting a subscription to Power BI for US Government.

Select the right sign-up process for your US Government organization

Your US Government organization might be new to the Office Government Cloud, or might already have a
subscription. The following sections detail the sign-up steps based on where you are with the Office Government
Cloud and Power BI, and are different based on your existing subscription.
Once you have signed up for Power BI US Government some features may not work until your sales or support
representative completes your onboarding process. To find out about these features see the Power BI for United
States Government customers - Overview. To complete the onboarding process to enable these features, contact
your sales or support representative.
US Government organizations that are new Office Cloud customers
If your organization is a new Office Government Cloud customer, follow these steps:

NOTE
These steps should be performed by the portal administrator.

1. Go to https://products.office.com/government/office-365-web-services-for-government.

NOTE
If you don't want to sign up for Office Government Cloud at this time, please reach out to your sales representative.

2. Select Office G3 and complete the form for an Office trial

3. Once you are an Office Cloud customer continue on with the steps below for "Existing Office Government
Cloud customers"
Existing Office Government Cloud customers
If your organization is an existing Office Government Cloud customer, but you don't have a Power BI
subscription (Free or otherwise), follow these steps:

NOTE
These steps should be performed by the portal administrator.

1. Log in to your existing Office Government Cloud account and go to the admin portal
2. Select Billing.
3. Select Purchase Service.
4. Select the Power BI Pro Government Option and choose between Try and Buy Now
5. Complete your order
6. Assign users to the account.

7. Log in to the Power BI service for US Government customers at https://app.powerbigov.us

Additional Signup Information

The below is additional information for signing up for Power BI US Government in various licensing migration
cases.
Direct Power BI Trial to Pro Customer Onboarding
 Click and follow through the Billing > Purchase Service > Power BI Pro Gov and select purchase and not Trial
Fill in the necessary and get the licenses
Remove the Power BI Pro Trial or remove the old licenses and Assign the new ones to the users
Log in to https://app.powerbigov.us
Reseller Power BI Trial to Pro Customer Onboarding
Go to Billing > Subscriptions and select Power BI Pro for Government subscription. There you will see:
Available
Assigned
Assign to users links
If you still have the Trial assigned:
Click on Assigned under the Trial subscription and remove the users you want to add to paid
Go to the Paid subscription and assign those users
Whitelisting Instructions
Whitelisting is a process that the Power BI engineering team uses to move customers from the commercial cloud
environment into the secure, Government cloud environment. This ensures that features available in the US
Government cloud work as expected. All existing (or new ) US Government customers that purchase US
Government Power BI services for the first time must initiate the following whitelisting process. The process must
be done prior to setup or migration to US Government Power BI services.
To have your tenant whitelisted for the US Government cloud, contact the Microsoft account team for assistance
with whiteplisting. Note that only administrators can make this request. The process for whitelisting takes
approximately three weeks, during which the Power BI engineering team makes appropriate changes to ensure
your tenant operates properly in the US Government cloud.
Customers migrating from Power BI Free licenses to Power BI US Government (and by definition, migrating to
the associated Pro license features described earlier in this article) will encounter the issues described in the
following section of this article, until their tenant is whitelisted by the Power BI engineering team.
Mixed Free and Pro licenses in US Government tenants
If you have both Free and US Government Pro licenses in your tenant, both Free and (US Government) Pro
licenses remain present, but one or the other license types will not work properly. If your tenant successfully goes
through the whitelisting process, then the following occurs:
Any Free license users will no longer be able to log in to Power BI using Power BI Desktop, and will
experience functionality gaps described in the following section.
All clients assigned to US Government Pro licenses will work as expected, including use of gateways, Power BI
Desktop, and Mobile apps.
When using a mix of Free and Pro licenses in a US Government tenant, and going through the whitelisting
process, the following can be expected:
Before whitelisting:
Users with Free licenses are running in commercial cloud
Pro US Government licenses show up in the portal, and the administrator can assign those licenses to
users. Pro US Government users will not lose data from their Free licenses once the admin assigns a US
Government Pro license. The assigned users have access Power BI Pro features for US Government
customers, but the following bullet list functionality gaps will exist until the tenant is successfully
whitelisted:
Gateway, Mobile, and Power BI Desktop can’t authenticate
 You cannot access Azure commercial data sources
PBIX files must be manually uploaded from the commercial Power BI service
Power BI mobile apps are not available
After whitelisting:
Free users running in the commercial Power BI service can continue to run, but the they will stop
authenticating as expected.
Pro users running in the US Government cloud can use the Power BI for US Government customers
service as expected.
To identifying users in your tenant that are running the Free license of Power BI, administrators can run the
licensing report, after which Free license users show up as Power BI Standard.

Next steps
There are all sorts of things you can do with Power BI. For more information and learning, including an article that
shows you how to sign up for the service, check out the following resources:
Overview of Power BI for US Government
Guided Learning for Power BI
Get started with the Power BI service
What is Power BI Desktop?
 Delete almost anything in Power BI service
2/13/2019 • 4 minutes to read • Edit Online

This article teaches you how to delete a dashboard, report, workbook, dataset, app, visualization, and workspace in
Power BI service.

Delete a dashboard
Dashboards can be removed. Removing the dashboard does not delete the underlying dataset or any reports
associated with that dashboard.
If you are the owner of the dashboard, you can remove it. If you've shared the dashboard with colleagues,
removing the dashboard from your Power BI workspace will remove the dashboard from their Power BI
workspaces.
If a dashboard is shared with you and you no longer want to see it, you can remove it. Removing a dashboard
does not remove it from anyone else's Power BI workspace.
If a dashboard is part of an organizational content pack, the only way to remove it is to remove the associated
dataset.
To delete a dashboard
1. In your workspace, select the Dashboards tab.
2. Locate the dashboard to delete and select the Delete icon .

Delete a report
Don't worry, deleting a report does not delete the dataset that the report is based on. And any visualizations that
you pinned from the report are also safe -- they remain on the dashboard until you delete them individually.
To delete a report
1. In your workspace, select the Reports tab.
2. Locate the report to delete and select the Delete icon .
3. Confirm the deletion.

NOTE
If the report is part of a content pack, you will not be able to delete it using this method. See Remove your
connection to an organizational content pack.

Delete a workbook
Workbooks can be removed. However, removing a workbook also removes all reports and dashboard tiles that
contain data from this workbook.
If the workbook is stored on OneDrive for Business, deleting it from Power BI does not delete it from OneDrive.
To delete a workbook
1. In your workspace, select the Workbooks tab.

2. Locate the workbook to delete and select the Delete icon.

3. Confirm the deletion.

Delete a dataset
Datasets can be deleted. However, deleting a dataset also deletes all reports and dashboard tiles that contain data
from that dataset.
If a dataset is part of one or more organizational content packs, the only way to delete it is to remove it from the
content packs where it's being used, wait for it to be processed, and then try deleting it again.
To delete a dataset
1. In your workspace, select the Datasets tab.
2. Locate the dataset to delete and select the ellipses (...).

3. From the dropdown, select Delete.

4. Confirm the deletion.

Delete an app workspace

WARNING
When you create an app workspace, you create an Office 365 group. And when you delete an app workspace you delete that
Office365 group. What this means is that the group will also be deleted from other O365 products like SharePoint and
Microsoft Teams.

As the app workspace author, you can delete it. When you delete it, the associated app is also deleted for all group
members and removed from your AppSource if you had published the app to your entire organization. Deleting an
app workspace is different from leaving an app workspace.
To delete an app workspace - if you are an Admin
1. From the left nav, select Workspaces
2. Select the ellipses (...) to the right of the workspace to be deleted and choose Edit workspace.

3. In the Edit workspace window, select Delete workspace > Delete.

To remove an app workspace from your list

If you no longer want to be a member of an app workspace, you can leave it and it will be removed from your list.
Leaving a workspace leaves it in place for all other workspace members.

IMPORTANT
If you are the only Admin for the app workspace, Power BI will not allow you to leave.

1. Start in the app workspace you'd like to remove.

2. In the top-right corner, select the ellipses (...) and choose Leave workspace > Leave.
 NOTE
The options you see in the dropdown depend on whether you are an Admin or Member of that app workspace.

Delete or remove an App

Apps can be easily removed from your apps list page. But only an app Admin can permanently delete an app.
Remove an app from your app list page
Deleting an app from your app list page does not delete the app for other members.
1. In your left nav, select Apps to open the apps list page.

2. Hover over the app to delete, and select the Delete icon.

If you remove an app accidentally, you have several options for getting it back. You can ask the app creator
to re-send it, you can find the original email with the link to the app, you can check your Notifications center
to see if the notification for that app is still listed, or you can check your organization's AppSource.

Considerations and troubleshooting

This article covered how to delete the major building blocks of Power BI service. But there are more things that
you can delete in Power BI.
Remove your Featured dashboard
Remove (unfavorite) a dashboard
Delete a report page
Delete a dashboard tile
Delete a report visualization
More questions? Try the Power BI Community
 Connect to the services you use with Power BI
1/11/2019 • 2 minutes to read • Edit Online

You can connect to a number of services you use to run your business, such as Salesforce, Microsoft Dynamics,
and Google Analytics. Power BI starts by using your credentials to connect to the service, and then creates a
Power BI app with a dashboard and a set of Power BI reports that automatically show your data and provide
visual insights about your business.
Log in to Power BI to view all of the services you can connect to.

After you install the app, you can view the dashboard and reports in the Power BI service ( https://powerbi.com),
and in the Power BI mobile apps.

Get started
1. Select Apps in the left navigation pane > select Get apps in the upper-right corner.

2. In AppSource, select the Apps tab, and search for the service you want.

View the dashboard and reports

When the import is complete, the new app appears on the Apps page.
1. Select Apps in the left navigation pane > select the app.

2. You can ask a question by typing in the Q&A box, or click a tile to open the underlying report.
 You can filter and highlight the data in the report, but you can't save your changes.

What's included
After connecting to a service, you see a newly created app with a dashboard, reports, and dataset. The data from
the service is focused on a specific scenario and may not include all the information from the service. The data is
scheduled to refresh automatically once per day. You can control the schedule by selecting the dataset.
You can also use Power BI Desktop to connect to some services, such as Google Analytics, and create your own
customized dashboards and reports.
For more details on connecting to specific services, please refer to the individual help pages.

Troubleshooting
Empty tiles
While Power BI is first connecting to the service, you may see an empty set of tiles on your dashboard. If you still
see an empty dashboard after 2 hours, it's likely the connection failed. If you didn't see an error message with
information on correcting the issue, please file a support ticket.
Select the question mark icon (?) in the upper-right corner > Get help.
Missing information
The dashboard and reports include content from the service focused on a specific scenario and do not include all
the information from the service. If there's a specific metric that you're not seeing in the content pack, please add
an idea on the Power BI Support page.

Suggesting services
Do you use a service you'd like to suggest for a Power BI app? Go to the Power BI Support page and let us know.
Do you have a service you'd like to build an app for? Submit your nomination and select "Publish a Power BI
Content Pack" to get started.

Next steps
What are apps in Power BI?
Get data in Power BI
More questions? Try asking the Power BI Community
 Connect to Acumatica with Power BI
2/13/2019 • 2 minutes to read • Edit Online

The Power BI Acumatica content pack allows to you quickly gain insights into your opportunity data. Power BI
retrieves your data, including opportunities, accounts, and customers, then builds a default dashboard and related
reports based on that data.
Connect to the Acumatica content pack or read more about the Acumatica integration with Power BI.

NOTE
This content pack requires Acumatica v5.2 or higher.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Acumatica > Get.

4. Enter your Acumatica OData endpoint. An OData endpoint allows an external system to request data from
 Acumatica. Acumatica OData endpoint is formatted as follows and should us HTTPS:
https://[sitedomain]/odata/[companyname]

The Company Name is only required if you have a multi-company deployment. More information about
finding this parameter in your Acumatica account is included below.

5. For Authentication Method, select Basic. Enter your username and password from your Acumatica account,
then click Sign In.
6. After Power BI imports the data you will see a new dashboard, report, and dataset in the left navigation
pane. New items are marked with a yellow asterisk * which disappears once selected, choosing the
dashboard will show a similar layout to the one below:
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

System requirements
This content pack requires Acumatica v5.2 or higher, please confirm the version with your Acumatica admin.

Finding parameters
Acumatica OData Endpoint
The Acumatica OData endpoint is formatted as follows and should us HTTPS:

https://[sitedomain]/odata/[companyname]

The Application Site Domain can be found in your browser’s address bar when you’re signed into Acumatica. In
the example below, the site domain is https://pbi.acumatica.com so the OData endpoint to provide would be
https://pbi.acumatica.com/odata .

The Company Name is only required if you have a multi-company deployment. You can find this information from
your Acumatica sign in page.
Troubleshooting
If you’re not able to login, verify the Acumatica OData endpoint you provided is formatted correctly.

https://<application site domain>/odata/<company name>

If you're having trouble connecting, please confirm with your admin your version of Acumatica. This content pack
requires version 5.2 or later.

Next steps
Get started in Power BI
Get data in Power BI
 Connect to Adobe Analytics with Power BI
2/13/2019 • 4 minutes to read • Edit Online

Connecting to Adobe Analytics through Power BI starts by connecting to your Adobe Analytics Marketing Cloud
account. You get an app with a Power BI dashboard and a set of Power BI reports that provide insights about your
site traffic and user dimensions. The data is refreshed automatically once per day. You can interact with the
dashboard and reports, but you can't save changes.
Connect to Adobe Analytics or read more about the Adobe Analytics integration with Power BI.

How to connect
1. Select Apps in the left navigation pane > select Get apps in the upper-right corner.

2. In AppSource, select the Apps tab, and search for the service you want.

3. Select Adobe Analytics > Get.

4. Power BI connects to a specific Adobe Analytics Company and Report Suite ID (not the Report Suite name).
See details on finding those parameters below.

5. For Authentication Method, select oAuth2 > Sign In. When prompted, enter your Adobe Analytics
credentials.
6. Click Accept to allow Power BI to access your Adobe Analytics data.
7. After you approve, the import process begins automatically.

View the Adobe Analytics dashboard and reports

When the import is complete, the new app will appear on the Apps page.
1. Select Apps in the left navigation pane > select the app.

2. You can ask a question by typing in the Q&A box, or click a tile to open the underlying report.
What now?
Try asking a question in the Q&A box at the top of the dashboard.
Select a tile to open the underlying report.
You can filter and highlight the data in the report, but you can't save your changes.
Your dataset is scheduled to refresh daily. You can change the refresh schedule or try refreshing it on demand
using Refresh Now.

What's included
Power BI uses the Adobe Analytics Report API to define and run reports for the following tables:

TABLE NAME COLUMN DETAILS

Products elements= "product" (top 25)

metrics="cartadditions", "cartremovals", "carts", "cartviews",
"checkouts", "revenue", "units"

Browsers elements= "browser" (top 25)

metrics="bounces", "bouncerate", "visitors", "visits",
"uniquevisitors", "totaltimespent", "pageviews"

Pages elements= "page" (top 25)

metrics="cartadditions", "cartremovals", "carts", "cartviews",
"checkouts", "revenue", "units", "visits", "uniquevisitors",
"pageviews", "bounces", "bouncerate", "totaltimespent"

JavaScript Enabled elements= "javascriptenabled”, “browser” (top 25)

Mobile OS elements= "mobileos"(top 25)

metrics="bounces", "bouncerate", "visitors", "visits",
"uniquevisitors", "totaltimespent", "cartadditions",
"cartremovals", "checkouts", "revenue", "units", "pageviews"
 TABLE NAME COLUMN DETAILS

Search Engines Keywords elements= "searchengine" "searchenginekeyword"

metrics="bounces", "bouncerate", "visitors", "visits", "entries",
"uniquevisitors", "totaltimespent", "cartadditions",
"cartremovals", "carts", "cartviews", "checkouts", "revenue",
"units", "pageviews"

Search Engine to Products elements= "searchengine", "product"

metrics="bounces", "bouncerate", "visitors", "visits", "entries",
"uniquevisitors", "totaltimespent", "cartadditions",
"cartremovals", "carts", "cartviews", "checkouts", "revenue",
"units", "pageviews"

Referring Pages elements= "referrer" (top 15), “page" (top 10)

metrics="bounces", "bouncerate", "visitors", "visits", "entries",
"uniquevisitors", "totaltimespent", "cartadditions",
"cartremovals", "carts", "cartviews", "checkouts", "revenue",
"units", "pageviews"

Geocountry Pages elements= "geocountry" (Top 20), "page"

metrics="bounces", "bouncerate", "visitors", "visits", "entries",
"uniquevisitors", "totaltimespent", "cartadditions",
"cartremovals", "carts", "cartviews", "checkouts", "revenue",
"units", "pageviews"

Geocountry Product elements= "geocountry" (Top 20), "product"

metrics="bounces", "bouncerate", "visitors", "visits", "entries",
"uniquevisitors", "totaltimespent", "cartadditions",
"cartremovals", "carts", "cartviews", "checkouts", "revenue",
"units"

Country and Region Lookup elements= "geocountry" (Top 200)

metrics="bounces", "bouncerate", "visitors", "visits", "entries",
"uniquevisitors", "totaltimespent", "cartadditions",
"cartremovals", "carts", "cartviews", "checkouts", "revenue",
"units"

Language elements= "language", "browser" (Top 25)

metrics="bounces", "bouncerate", "visitors", "visits",
"uniquevisitors", "totaltimespent", "pageviews", "cartadditions",
"cartremovals", "checkouts", "carts", "cartviews"

Search Engines Look Up elements= "searchengine" (top 100)

metrics="bounces", "bouncerate", "visitors", "visits", "entries",
"uniquevisitors", "totaltimespent", "cartadditions",
"cartremovals", "carts", "cartviews", "checkouts", "revenue",
"units"

Browser Lookup elements= "browser" (top 25)

System requirements
Access to Adobe Analytics is required, including access to the correct parameters as described below.

Finding parameters
Company
The Company value can be found in the top right of your account once you're signed in. The value is case and
spacing sensitive. Enter it exactly as you see in your account.

Report Suite ID
The Suite ID is created when the Report Suite is created. You can contact your administrator to identify the ID
value. This is not the Report Suite name.
From Adobe documentation:

Troubleshooting
If you're seeing an error after providing your credentials indicating you do not have permissions, confirm with your
admin that you have access to the Adobe Analytics API. Also confirm the Adobe ID provided is linked to your
Marketing Cloud Organization (associated to an Adobe Analytics company).
If you've successfully passed the credentials screen before encountering an error, it's possible the reports are taking
too long to complete. A common error is in the form "Failed to get data from the Adobe Analytics report. Contents
included "referrer, page", approximate duration was xx seconds". Review the "What's included" section and
compare to the size of your Adobe instance. Unfortunately there isn't a way to work around this timeout today.
However, we're considering updates to better support larger instances, provide feedback to the Power BI team at
https://ideas.powerbi.com

Next steps
What are apps in Power BI?
Get data in Power BI
More questions? Try asking the Power BI Community
 Connect to Alpine Metrics Sales Predictions with
Power BI
1/4/2019 • 2 minutes to read • Edit Online

Alpine Metrics provides state of the art Predictive Sales Process Optimization in the cloud and on demand for sales
organizations large and small. The Alpine Metrics Sales Predictions content pack for Power BI includes metrics
such as potential and predicted sales and risks, allowing you deeper insight into the future of your business.
Connect to the Alpine Metrics Sales Predictions content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select AlpineMetrics Sales Predictions, then select Get.

4. Select OAuth 2 and then Sign In. When prompted, provide your AlpineMetrics credentials.
5. Once connected, a dashboard, report and dataset will automatically be loaded. When completed, the tiles
will update with data from your account.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The content pack includes data from the following tables:

- Account
- Business
- Country
- Industry
- Opportunity
- Person
- Prediction
- Prediction History
- Product
- Region

System requirements
An Alpine Metrics account with permissions to the above tables is required in order to instantiate this content pack.

Next steps
What is Power BI?
Power BI - Basic Concepts
 Connect to appFigures with Power BI
1/4/2019 • 2 minutes to read • Edit Online

Tracking important statistics about your apps is easy with Power BI and the appFigures content pack. Power BI
retrieves your data, including app sales, downloads, and ad statistics, then builds a default dashboard and related
reports based on that data.
Connect to the appFigures content pack or read more about the appFigures integration with Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select appFigures > Get.

4. For Authentication Method, select oAuth2 > Sign In. When prompted, enter your appFigures
credentials and follow the appFigures authentication process.
The first time you connect, Power BI prompts you to allow read-only access to your account. Select Allow
to begin the import process. This can take a few minutes depending on the volume of data in your account.
5. After Power BI imports the data you will see a new dashboard, report, and dataset in the left navigation
pane. New items are marked with a yellow asterisk *:

6. Select the appFigures dashboard. This is the default dashboard that Power BI creates to display your data.
You can modify this dashboard to display your data in any way you want.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The following data is available from appFigures in Power BI.

TABLE NAME DESCRIPTION

Countries This table provides country name information.

Dates This table contains dates from today back to the earliest
PublishDate of apps that are Active and Visible in your
appFigures account.

Events This table contains download, sales, and ad information for

each app, by country, on a daily basis. Note that both app and
in-app purchase information is all in this single table—you can
use the Type column to differentiate.

Inapps This table contains data about the different types of In-App
Purchases that are associated with Active, Visible apps on your
appFigures account.

Products This table contains data about the different apps that are
Active and Visible on your appFigures account.

Troubleshooting
If data from some of your apps is not showing up in Power BI, check to make sure that those apps are Visible and
Active on the apps tab of the appFigures site.

Next steps
Get started in Power BI
Get data in Power BI
 Connect to Application Insights with Power BI
1/4/2019 • 2 minutes to read • Edit Online

Use Power BI to create powerful custom dashboards from Application Insights telemetry. Envision your app
telemetry in new ways. Combine metrics from multiple apps or component services onto one dashboard. This first
release of the Power BI content pack for Application Insights includes widgets for common usage-related metrics
such as active users, page view, sessions, browser and OS version, and geographic distribution of users in a map.
Connect to the Application Insights content pack for Power BI.

NOTE
This integration method is now deprecated. To learn more about the preferred method of connecting Application Insights to
Power BI use the export analytic query functionality.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Application Insights > Get.

4. Provide the details of the application you want to connect to, including Application Insights Resource
Name, Resource Group, and Subscription ID. See Finding your Application Insights parameters below
for more details.

5. Select Sign In and follow the screens to connect.

6. The import process begins automatically. When complete, a notification is shown and a new dashboard,
report, and dataset appear in the Navigation Pane marked with an asterisk. Select the dashboard to view
your imported data.

What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The Application Insights content pack includes the following tables and metrics:
 ´´´
- ApplicationDetails
- UniqueUsersLast7Days
- UniqueUsersLast30Days
- UniqueUsersDailyLast30Days
- UniqueUsersByCountryLast7Days
- UniqueUsersByCountryLast30Days
- PageViewsDailyLast30Days
- SessionsLast7Days
- SessionsLast30Days
- PageViewsByBrowserVersionDailyLast30Days
- UniqueUsersByOperatingSystemLast7Days
- UniqueUsersByOperatingSystemLast30Days
- SessionsDailyLast30Days
- SessionsByCountryLast7Days
- SessionsByCountryLast30Days
- PageViewsByCountryDailyLast30Days
´´´

Finding parameters
Your Resource Name, Resource Group and Subscription ID can all be found in the Azure Portal. Selecting the
Name will open a detailed view and you can use the Essentials drop-down to find all the values you need.

Copy and paste these into the fields into Power BI:
Next steps
Get started in Power BI
Get data in Power BI
 Connect to AT Internet Bridge with Power BI
1/4/2019 • 2 minutes to read • Edit Online

AT Internet helps you to extract immediate value from your data using its unified digital analytics platform, the
Analytics Suite. The AT Internet Bridge content pack for Power BI includes data around visits, sources, localization
and devices for your site.
Connect to the AT Internet Bridge content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select AT Internet Bridge > Get.

4. Specify the AT Internet Website Number you'd like to connect to.

5. Select Basic as the Authentication Mechanism, provide your AT Internet username and password, and click
Sign In.

6. Click Connect to begin the import process. When complete, a new dashboard, report and model will appear
 in the Navigation Pane. Select the dashboard to view your imported data.

What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
This content pack contains data from the last 45 days in the following tables:

- Conversion
- Devices
- Localization
- Sources
- Global Visits

Next steps
What is Power BI?
Power BI - Basic Concepts
 Connect to Azure Audit Logs with Power BI
1/4/2019 • 2 minutes to read • Edit Online

With the Azure Audit Logs content pack you can analyze and visualize the information stored in the audit logs.
Power BI retrieves your data, builds an out-of-the box dashboard, and creates reports based on that data.
Connect to the Azure Audit Logs content pack or read more about the Azure Audit Logs integration with Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Azure Audit Logs > Get.

4. When prompted, enter your Azure Subscription Id. See details on finding your subscription ID below.
5. For Authentication Method, select oAuth2 > Sign In.

6. Enter your account credentials to finish the sign-in process.

7. Power BI will retrieve your Azure Audit Log data and create a ready-to-use dashboard and report.

What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

System requirements
The Azure Audit logs content pack requires access to Audit Logs in the Azure portal. More details here.

Finding parameters
There are two easy ways to find your Subscription Id.
1. From https://portal.azure.com -> Browse -> Subscriptions -> Subscription Id
2. From https://manage.windowsazure.com -> Settings -> Subscription Id
Your subscription Id will be long set of numbers and characters, similar to the example in Step #4 above.

Troubleshooting
If you're seeing a credentials error or an error trying to refresh due to invalid credentials, try deleting all instances
of the Azure Audit logs content pack and reconnecting.

Next steps
What is Power BI?
Power BI - Basic Concepts
 Connect to Azure Mobile Engagement with Power BI
1/4/2019 • 2 minutes to read • Edit Online

The Power BI Azure Mobile Engagement content pack allows to you quickly gain insights into your app data.
Connect to the Azure Mobile Engagement content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Azure Mobile Engagement > Get.

4. Specify your App Collection and App Name. This information can be found in your Azure Mobile
Engagement account.
5. For Authentication Method, provide your Key then click Sign In.

6. After Power BI imports the data you will see a new dashboard, report, and dataset in the left navigation
pane. New items are marked with a yellow asterisk * which disappears once selected:
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

Next steps
Get started in Power BI
Get data in Power BI
 Connect to Microsoft Azure Consumption Insights
with Power BI
1/4/2019 • 2 minutes to read • Edit Online

Explore and monitor your Microsoft Azure consumption data in Power BI with the Power BI content pack. The data
will be refreshed automatically once per day.
Connect to the Microsoft Azure Consumption Insights content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Microsoft Azure Consumption Insights > Get.

4. Provide the number months of data you want to import and your Azure Enterprise enrollment number. See
details on finding these parameters below.
5. Provide your Access key to connect. The key for your enrollment can be found in your Azure EA Portal.

6. The import process will begin automatically. When complete, a new dashboard, report and model will
appear in the Navigation Pane. Select the dashboard to view your imported data.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The Microsoft Azure Consumption Insights content pack includes monthly reporting data for the range of months
that you provide during the connection flow. The range is a moving window, so the dates included will update as
the dataset refreshes.

System Requirements
The content pack requires access to the Enterprise features within the Azure Portal.

Finding parameters
Power BI reporting is available for EA Direct, Partner and Indirect Customers who are able to view billing
information. Please read below for details about finding each of the values the connection flow expects.
Number of Months
This should be a number between 1-36 representing the number of months of data (from today) you'd like to
import.
Enrollment Number
 This is your Azure Enterprise enrollment number which can be found on the home screen of the Azure
Enterprise Portal under “Enrollment Detail”.

Access Key
Your key can be found in the Azure Enterprise portal, under "Download Usage" > "API Access Key"

Additional Help
For additional help setting up the Azure Enterprise Power BI Pack, log in to the Azure Enterprise Portal to view
the API Help File under “Help” and additional instructions under Reports -> Download Usage -> API Access
Key.

Next steps
Get started in Power BI
Get data in Power BI
 Connect to Azure Search with Power BI
1/4/2019 • 2 minutes to read • Edit Online

Azure Search Traffic Analytics allows you to monitor and understand the traffic to your Azure Search service. The
Azure Search content pack for Power BI provides detailed insights on your Search data, including Search, Indexing,
Service Stats and Latency from the last 30 days. More details can be found in the Azure blog post.
Connect to the Azure Search content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Azure Search > Get.

4. Provide the name of the table storage account your Azure Search analysis is stored.
5. Select Key as the Authentication Mechanism and provide your storage account key. Click Sign In and to
begin the loading process.

6. Once the loading is complete, a new dashboard, report and model will appear in the Navigation Pane. Select
the dashboard to view your imported data.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

System requirements
The Azure Search content pack requires Azure Search Traffic Analytics to be enabled on the account.

Troubleshooting
Ensure the storage account name is correctly provided along with the full access key. The storage account name
should correspond to the account configured with Azure Search Traffic Analytics.

Next steps
What is Power BI?
Power BI - Basic Concepts
 Connect to Circuit ID with Power BI
1/4/2019 • 2 minutes to read • Edit Online

Analyzing your communication data from Circuit ID is easy with Power BI. Power BI retrieves your data, then
builds a default dashboard and related reports based on that data. After you have created the connection, you can
explore your data and customize the dashboard to meet your needs. Data is automatically refreshed every day.
Connect to the Circuit ID content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Circuit ID > Get.

4. For Authentication Method, select Basic and provide your username and password. Then hit Sign In.

5. After Power BI imports the data you will see a new dashboard, report, and dataset in the left navigation
pane. New items are marked with a yellow asterisk.

What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

Next steps
What is Power BI?
Get Data for Power BI
 Connect to ClickDimensions with Power BI
1/4/2019 • 2 minutes to read • Edit Online

The ClickDimensions content pack for Power BI allows users to utilize ClickDimensions marketing data in Power
BI, giving management teams further insight into the success of their sales and marketing efforts. Visualize and
analyze email interactions, web visits and form submissions in Power BI dashboards and reports.
Connect to the ClickDimensions content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select ClickDimensions > Get.

4. Provide the location of your data center (US, EU or AU ) and select Next.
5. For Authentication Method, select Basic > Sign In. When prompted, enter your ClickDimensions
credentials. See details in finding those parameters below

6. After approving, the import process will begin automatically. When complete, a new dashboard, report and
model will appear in the Navigation Pane. Select the dashboard to view your imported data.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

System requirements
To connect to the Power BI content pack, you must provide the data center corresponding to your account and log
in with your ClickDimensions account. If you're unsure which data center to provide, please check with your admin.

Finding parameters
The Account Key is found within CRM Settings > ClickDimensions Settings. Copy the Account Key from within
ClickDimensions Settings and paste it into the User name field.
Copy the Power BI Token from within ClickDimensions Settings and paste it into the Password field. The Power BI
Token is found within CRM Settings > ClickDimensions Settings.

Next steps
Get started in Power BI
Get data in Power BI
 Connect to comScore Digital Analytix with Power BI
1/31/2019 • 2 minutes to read • Edit Online

Visual and explore your comScore Digital Analytix data in Power BI with the Power BI content pack. The data will
be refreshed automatically once per day.
Connect to the comScore content pack for Power BI.

NOTE
To connect to the content pack you need a comScore DAx user account and have comScore API access. More details below.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select comScore Digital Analytix > Get.

4. Provide the datacenter, comScore Client ID and Site you’d like to connect to. For more details on how to find
these values, please see Finding your comScore Parameters below.

5. Provide your comScore username and password to connect. See details on finding this value below.
6. The import process will begin automatically. When complete, a new dashboard, report and model will
appear in the Navigation Pane. Select the dashboard to view your imported data.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

System requirements
A comScore DAx user account and access to the comScore DAx API is required to connect. Please contact your
comScore DAx admin to confirm your account.

Finding parameters
Details on how to find each of your comScore parameters is below.
Data Center
The data center you connect to is determined by the URL you navigate to in comScore.

Client
The Client is the same one you provide when signing into comScore DAx.
Site
The comScore site determines which site you’d like to see the data from. You can find the list of sites from your
comScore account.

Next steps
Get started in Power BI
Get data in Power BI
 Connect to GitHub with Power BI
1/4/2019 • 3 minutes to read • Edit Online

The GitHub content pack for Power BI allows you to gain insights into a GitHub repository (also known as repo)
with data around contributions, issues, pull requests and active users.
Connect to the GitHub content pack or read more about the GitHub integration with Power BI.

NOTE
The content pack requires the GitHub account to have access to the repo. More details on requirements below.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select GitHub > Get.

4. Enter the repository name and repository owner of the repo. See details on finding these parameters below.
5. Enter your GitHub credentials (this step might be skipped if you are already signed in with your browser).
6. For Authentication Method, select oAuth2 > Sign In.
7. Follow the Github authentication screens. Grant the GitHub for Power BI content pack permission to the
GitHub data.

This connects Power BI with GitHub and allows Power BI to connect to the data. The data is refreshed once a
day.
8. After you connect to your repo, Power BI imports the data. You see a new GitHub dashboard, report, and
dataset in the left navigation pane. New items are marked with a yellow asterisk *.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The following data is available from GitHub in Power BI:

TABLE NAME DESCRIPTION

Contributions The contributions table gives the total additions, deletions and
commits authored by the contributor aggregated per week.
The top 100 contributors are included.

Issues List all issues for the selected repo and it contains calculations
like total and average time to close an issue, Total open issues,
Total closed issues. This table will be empty when there are no
issues in the repo.

Pull requests This table contains all the Pull Requests for the repo and who
pulled the request. It also contains calculations around how
many open, closed and total pull requests, how long it took to
pull the requests and how long the average pull request took.
This table will be empty when there are no issues in the repo.

Users This table provides a list of GitHub users or contributors who

have made contributions, filed issues or solved Pull requests
for the repo selected.

Milestones It has all the Milestones for the selected repo.

DateTable This tables contains dates from today and for years in the past
that allow you to analyze your GitHub data by date.
 TABLE NAME DESCRIPTION

ContributionPunchCard This table can be used as a contribution punch card for the
selected repo. It shows commits by day of week and hour of
day. This table is not connected to other tables in the model.

RepoDetails This table provides details for the repo selected.

System requirements
The GitHub account that has access to the repo.
Permission granted to the Power BI for GitHub app during first login. See details below on revoking access.
Sufficient API calls available to pull and refresh the data.
De -authorize Power BI
To de-authorize Power BI from being connected to your GitHub repo you can Revoke access in GitHub. For more
details see this GitHub help topic.

Finding parameters
You can determine the owner and repository by looking at the repository in GitHub itself:

The first part "Azure" is the owner and the second part "azure-sdk-for-php" is the repository itself. You see these
same two items in the URL of the repository:

<https://github.com/Azure/azure-sdk-for-php> .

Troubleshooting
If necessary, you can verify your GitHub credentials.
1. In another browser window, go to the GitHub web site and log in to GitHub. You can see you’re logged in, in the
upper-right corner of the GitHub site.
2. In GitHub, navigate to the URL of the repo you plan to access in Power BI. For example:
https://github.com/dotnet/corefx.
3. Back in Power BI, try connecting to GitHub. In the Configure GitHub dialog box, use the names of the repo and
repo owner for that same repo.

Next steps
What is Power BI?
Get data
 Connect to Google Analytics with Power BI
2/13/2019 • 2 minutes to read • Edit Online

Connecting to Google Analytics through Power BI starts by connecting to your Google Analytics account. You will
get a Power BI dashboard and a set of Power BI reports that provide insights about your site traffic and user
dimensions. You can interact with the dashboard and reports, but you can't save changes. The data will be
refreshed automatically once per day.
Connect to Google Analytics for Power BI. Read more about the Google Analytics integration with Power BI.
You can create customized dashboards and reports by starting from the Google Analytics connector in Power BI
Desktop. Just connect with your Google Analytics account and create your custom reports, which you can publish
to the Power BI service.

How to connect
1. Select Apps in the left navigation pane > select Get apps in the upper-right corner.

2. In AppSource, select the Apps tab, and search for the service you want.

3. Select Google Analytics > Get.

4. When prompted, enter your Google Analytics credentials. Select oAuth 2 as the Authentication Mechanism
and click Sign In. Follow the Google authentication flow, which may include 2-factor authentication if you
have it configured.

5. Click Accept to allow Power BI to access your Google Analytics data.

6. Power BI connects to a specific Google Analytics View. Select the account name, property name and view
name you’d like to connect to. This information can be found in your Google Analytics account, either in the
top left or on the Home tab. See details below.

7. Click Connect to begin the import process.

View the Google Analytics dashboard and reports

When the import is complete, the new app will appear on the Apps page.
1. Select Apps in the left navigation pane > select the app.
2. You can ask a question by typing in the Q&A box, or click a tile to open the underlying report.

What now?
Try asking a question in the Q&A box at the top of the dashboard.
Select a tile to open the underlying report.
You can filter and highlight the data in the report, but you can't save your changes.
Your dataset is scheduled to refresh daily. You can change the refresh schedule or try refreshing it on demand
using Refresh Now.

System requirements
To connect from Power BI, you need to have a Google Analytics account. Other Google accounts that do not have a
Google Analytics account connected to it will see an authentication error.
Troubleshooting
Credentials If you have multiple Google accounts, please use an incognito or an in-private browser window
during connection to ensure the correct account is used.
If you're getting an error indicating your credentials are invalid however you were able to sign into Google, please
confirm you have a Google Analytics account.
Parameters Unique names are currently required for the parameters. If you see an error indicating the value you
selected is duplicated, please select another value or change the names in Google Analytics to make them unique.
We're actively working to improve this.

NOTE
Parameters are case-sensitive. Enter them exactly as they appear in your Google Analytics account.

Still having issues? Open a support ticket to reach the Power BI team:
While in the Power BI app, select the question mark > Contact Support.
From the Power BI Support site (where you're reading this article), select Contact Support on the right side of
the page.

Next steps
What are apps in Power BI?
Get data in Power BI
More questions? Try asking the Power BI Community
 Connect to Insightly with Power BI
1/4/2019 • 2 minutes to read • Edit Online

Visualize and share your Insightly CRM data in Power BI with the Insightly content pack. Connect to Power BI
using your Insightly API key to view and build reports and dashboards from your CRM data. With Power BI, you
can analyze your data in new ways, create powerful graphs and charts, and display contacts, leads, and
organizations on a map.
Connect to the Insightly content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Insightly > Get.

4. Select Key as the Authentication type and provide your Insight API Key then select Sign In. See details on
finding this below.
5. After approving, the import process will begin automatically. When complete, a new dashboard, report and
model will appear in the Navigation Pane. Select the dashboard to view your imported data.

What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now
What's included
The content pack includes the following tables with fields from the corresponding records:

TABLES

Contacts Opportunities Pipeline Stages Task Complete Date

Custom Fields Opportunity Close Date Project Complete Date Tasks

Events Opportunity Forecast Date Projects Teams/Members

Leads Organizations Tags Users

Many tables and reports also include unique calculated fields, such as:
Tables with “grouped” opportunity forecast close dates, opportunity actual close dates, project completion dates,
and task completion dates for analysis by month, quarter, or year.
A weighted value field for opportunities (opportunity value * probability of winning).
Average and total duration fields for tasks, based on start and completed dates.
Reports with calculated fields for opportunity win rate (count of won/count of total opportunities) and win rate
value (value of won/value of total opportunities).

System requirements
An Insightly account with access to the Insightly API is required. Visibility permissions will be based on the API key
used to establish the connection to Power BI. Any Insightly records visible to you will also be visible in the Power BI
reports and dashboards that you share with others.

Finding parameters
API Key
To copy your API key from Insightly, select User Settings from the Insightly profile menu and scroll down. This
string of characters will be used to connect your data to Power BI.
Troubleshooting
Your data is imported via the Insightly API, which includes a daily limit based on your Insightly subscription plan
level. The limits are listed in the Rate Limiting/Throttling Requests section of our API documentation:
https://api.insight.ly/v2.2/Help#!/Overview/Introduction#ratelimit
The provided reports use default fields from Insightly and may not include your customizations. Edit the report to
view all the available fields.

Next steps
Get started in Power BI
Get data in Power BI
 Connect to IntelliBoard with Power BI
1/4/2019 • 2 minutes to read • Edit Online

IntelliBoard offers simplified access to your Moodle learning management system data through reporting services.
The IntelliBoard content pack for Power BI offers additional analytics, including metrics on your courses, registered
users, overall performance, and your LMS activity.
Connect to the IntelliBoard content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select IntelliBoard, then select Get.

4. Select OAuth 2 and then Sign In. When prompted, provide your IntelliBoard credentials.
5. Once connected, a dashboard, report and dataset will automatically be loaded. When completed, the tiles
will update with data from your IntelliBoard account.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The content pack includes data from the following tables:

- Activity
- Agents
- Auth
- Countries
- CoursesProgress
- Enrollments
- Lang
- Platform
- Totals
- UsersProgress

System requirements
An IntelliBoard account with permissions to the above tables is required in order to instantiate this content pack.

Next steps
What is Power BI?
Power BI - Basic Concepts
 Connect to Lithium with Power BI
1/4/2019 • 2 minutes to read • Edit Online

Lithium builds trusted relationships between the world's best brands and their customers, helping people get
answers and share their experiences. By connecting the Lithium content pack to Power BI, you can measure key
metrics about your online community to help drive sales, reduce service costs and increase loyalty.
Connect to the Lithium content pack for Power BI.

NOTE
The Power BI content pack uses the Lithium API. Excessive calls to the API may result in additional charges from Lithium,
please confirm with your Lithium administrator.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Lithium > Get.

4. Provide the URL of your Lithium community. It will be in the form of https://community.yoursite.com.

5. When prompted, enter your Lithium credentials. Select oAuth 2 as the Authentication Mechanism and click
Sign In and follow the Lithium authentication flow.
6. Once the login flow is completed the import process will begin. When complete, a new dashboard, report
and model will appear in the Navigation Pane. Select the dashboard to view your imported data.

What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
 While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

System requirements
The Lithium content pack requires a Lithium community v15.9 or greater. Please check with your Lithium admin to
confirm.

Next steps
What is Power BI?
Power BI - Basic Concepts
 Connect to MailChimp with Power BI
1/4/2019 • 2 minutes to read • Edit Online

The Power BI content pack pulls data from your MailChimp account and generates a dashboard, a set of reports
and a dataset to allow you to explore your data. Pull in analytics to create MailChimp dashboards and quickly
identify trends within your campaigns, reports, and individual subscribers. The data is set to refresh daily ensuring
the data you're monitoring is up to date.
Connect to the MailChimp content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select MailChimp > Get.

4. For Authentication Method, select oAuth2 > Sign In.

When prompted, enter your MailChimp credentials and follow the authentication process.
The first time you connect you will be prompted to allow Power BI read-only access to your account. Select
 Allow to begin the import process, which can take a few minutes depending on the volume of data in your
account.

5. After Power BI imports the data you will see a new dashboard, report, and dataset in the left navigation
pane. This is the default dashboard that Power BI created to display your data. You can modify this
dashboard to display your data in any way you want.

What now?
Try asking a question in the Q&A box at the top of the dashboard
 Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

Next steps
What is Power BI?
Power BI - Basic Concepts
 Connect to Mandrill with Power BI
1/4/2019 • 2 minutes to read • Edit Online

The Power BI content pack pulls data from your Mandrill account and generates a dashboard, a set of reports and
a dataset to allow you to explore your data. Use Mandrill's analytics to quickly gain insights into your newsletter or
marketing campaign. The data is set to refresh daily ensuring the data you're monitoring is up to date.
Connect to the Mandrill content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Mandrill > Get.

4. For Authentication Method, select Key and provide your API key. You can find the key on the Settings
 tab of the Mandrill dashboard. Select Sign In to begin the import process, which can take a few minutes
depending on the volume of data in your account.

5. After Power BI imports the data you will see a new dashboard, report, and dataset in the left navigation
pane. This is the default dashboard that Power BI created to display your data.

What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
 While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

Next steps
What is Power BI?
Power BI - Basic Concepts
 Connect to Marketo with Power BI
2/13/2019 • 3 minutes to read • Edit Online

The Power BI content pack for Marketo allows you to gain insights into your Marketo account with data around
Leads and their activities.Creating this connection retrieves your data and automatically provides a dashboard and
related reports based on that data.
Connect to the Marketo content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Marketo > Get.

4. Enter the Marketo REST endpoint supplied to you by Marketo or your Marketo admin, and select Next.
 Read more about the Marketo REST endpoint:
http://developers.marketo.com/documentation/rest/endpoint-url/ .
5. Using the Basic Authentication Method, enter the Client ID as the Username and the Client Secret as the
Password. Client ID and Client Secret are available in Marketo or from your marketo admin
(http://developers.marketo.com/documentation/rest/custom-service/ ).

This gives the Marketo for Power BI content pack access to your Marketo analytics data and allows you to
analyze the data in Power BI. The data is refreshed once a day.
6. Once connected to your Marketo account, a dashboard with all your data is loaded:
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The following data is available from Marketo in Power BI where the activity occurred between today and one year
ago:

TABLE NAME DESCRIPTION

EmailActivities Data about email sent to leads/contacts, with details about

devices, categories, bounced count and percentage, clicked
count and percentage, opened count and percentage, and
program name. The Email Activities as shown in Power BI is an
absolute email deliverability report, it does not apply any
additional logic to the data. You might see some different
results between the Marketo client and Power BI because of
this.

ProgramActivities Data on programs that have had a change a Status. This

includes details such as: Reason, Success, Program acquisition
count and percentage, and Program success count and
percentage.

WebPageActivities Data from user web page visits, including search agent, User
agent, web page and hour of day.

Datetable Dates from today and the past year. Allows you to analyze
your Marketo data by date.
 TABLE NAME DESCRIPTION

Leads Lead information like company, revenue size, number of

employees, country, industry, Lead score and Lead status. The
leads are retrieved based on their presence in the email,
program, and webpage activities data.

All dates are in UTC. Depending on which time zone your account is in, dates my vary (similar as is seen in the
Marketo client)

System requirements
The Marketo account you use for connecting has permission to access leads and activities.
Sufficient API calls available to connect to the data. Marketo has an API for each account. When the limit is
reached, you won't be able to load data into Power BI.
API Limit Details
Importing data from Marketo uses Marketo APIs. Every customer of Marketo has a total limit of 10,000 API calls
per day that are shared between all applications that use the Marketo APIs. You may use the APIs for other
integrations as well as the Power BI integration. For more information on the APIs see:
http://developers.marketo.com/documentation/rest/.
The amount of API calls Power BI makes to Marketo depends on the amount of data in your Marketo account.
Power BI imports all Leads and Activities for the last year. Here is an example of data from Marketo and the
amount of API calls that are used by Power BI when importing:

DATA TYPE NUMBER OF ROWS API CALLS

Leads information 15,000 50

Mail activities 150,000 1,000

Program activities 15,000 100

Web activities 150,000 1,000

Program changes 7,500 50

Total API Calls 2,200

Next steps
What is Power BI?
Get Data for Power BI
Power BI blog: Monitor and analyze your Marketo data with Power BI
 Connect to Microsoft Dynamics AX content pack with
Power BI
1/4/2019 • 2 minutes to read • Edit Online

Microsoft Dynamics AX has three Power BI content packs targeted at different business users. The Financial
Performance content pack, designed specifically for CFOs, provides access to insights about your organization’s
financial performance. The Retail Channel Performance content pack is targeted for channel managers focuses on
sales performance to predict trends and uncover insights by drawing directly from Retail & Commerce data. The
Cost Management is designed for COOs and CFOs and provides details on operation performance.
Connect to the Microsoft Dynamics AX Retail Channel Performance, the Financial Performance or the Cost
Management content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select one of the Dynamics AX content packs and choose Get.

4. Specify the URL of your Dynamics AX 7 environment. See details on finding those parameters below.

5. For Authentication Method, select oAuth2 > Sign In. When prompted, enter your Dynamics AX
credentials.
6. After approving, the import process will begin automatically. When complete, a new dashboard, report and
model will appear in the Navigation Pane. Select the dashboard to view your imported data.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The content pack uses the Dynamics AX 7 OData feed to import data related to Retail Channel, Financial, and Cost
Management performance respectively.

System requirements
This content pack requires a Dynamics AX 7 environment URL and the user should have access to the OData feed.

Finding parameters
The Dynamics AX 7 environment URL can be found in the browser when the user signs in. Just copy the URL of
the root Dynamics AX environment into the Power BI dialog.

Troubleshooting
The data may take some time to load depending on the size of your instance. If you're seeing empty reports within
Power BI, please confirm you have access to the OData tables required for the reports.

Next steps
Get started in Power BI
Get data in Power BI
 Connect to Microsoft Dynamics CRM with Power BI
1/4/2019 • 6 minutes to read • Edit Online

Microsoft Dynamics CRM Online for Power BI allows you to easily access and analyze your data. Power BI uses the
OData feed to create a descriptive model, with all the entities and measures needed such as Accounts, Activities,
Opportunities, Product, Leads, Users, and more. After you install the app, you can view the dashboard and reports
in the Power BI service (https://powerbi.com), and in the Power BI mobile apps.
Connect to Dynamics CRM Online Sales Manager or Service Manager. Read more about Dynamics CRM Online
integration with Power BI.
This connection requires Microsoft Dynamics CRM Online 2016 or later. More details on requirements below.

How to connect
1. Select Apps in the left navigation pane > select Get apps in the upper-right corner.

2. In AppSource, select the Apps tab, and search for the service you want.

3. Select Microsoft Dynamics CRM Sales Manager or Microsoft Dynamics CRM Service Manager and
click Connect.
4. Provide the Service URL associated with your account. This will be in the form
https://company.crm.dynamics.com , see more details below.

5. When prompted, provide your credentials (this step might be skipped if you're already signed in with your
browser). For Authentication Method, enter oAuth2 and click Sign In:
6. After connecting, you'll see a dashboard customized for a Sales Manager or Service Manager, populated
with your own data:

View the Microsoft Dynamics CRM dashboard and reports

When the import is complete, the new app will appear on the Apps page.
1. Select Apps in the left navigation pane > select the app.
2. You can ask a question by typing in the Q&A box, or click a tile to open the underlying report.
What now?
Try asking a question in the Q&A box at the top of the dashboard.
Select a tile to open the underlying report.
You can filter and highlight the data in the report, but you can't save your changes.
Your dataset is scheduled to refresh daily. You can change the refresh schedule or try refreshing it on demand
using Refresh Now.

What's included
The sections below detail what's included for the Sales Manager and Service Manager personas.
Data is limited based on the security role assigned to the Dynamics CRM Online user.
The dashboard and reports are meant to provide operational reporting on near term data with focus on a team or
group. Each query is limited to retrieve a maximum of 100K records from Dynamics CRM Online. If this limit is
exceeded because of high volume of data in your organization, provisioning will fail as data refresh Dynamics CRM
online will be terminated. If your account is too large, consider connecting through the Power BI Desktop to build a
custom solution.
Sales Manager
The dashboard and reports contain key metrics such as:
Won Revenue
Win Rate
Open Revenue
Lost revenue
Expected Revenue
Average Deal Size and more.
They also contain key charts such as:
Won and Lost Revenue Trend, Won Revenue Vs Estimated Revenue Trend
Won Revenue by various dimensions such as Industry, Region, Territory
Sales Leaders By Revenue, Activities,
 Top Accounts, Top Won/Lost Deals,
New Leads Trend, Sales Pipeline and more.
These metrics and charts help to understand your sales organization performance and analyze sales pipeline across
your sales team.
Following table lists the CRM entities available for this service and also gives details on the filters applied to each
of the entity records.

CRM ENTITY FILTERS APPLIED

Account All accounts, which have related opportunities that have been
modified in the last 365 days.

Activity All activities modified in the last 90 days

[modifiedon] > today - 90 days

Business Unit All business units, which are not disabled

[isdisabled] = false

Lead All leads modified in the last 180 days

[modifiedon] > today - 180 days

Opportunity All opportunities modified in last 365 days

[modifiedon] > today - 365 days

Opportunity Product All opportunity products modified in last 365 days

[modifiedon] > today - 365 days

Product All active products

[statecode] <> 1

Territory All territories

User All active users and not delegated admins

[isdisabled] = false and [accessmode] <> 4

Service Manager
These dashboard and reports contain key metrics such as:
CSAT Percentage
SLA Met percentage
Escalated Cases Percentage
Average Handling Time
Total Resolved Cases
Total Active Cases
Number of Times KB Article Used in cases and more.
They also contain key charts such as:
Case Volume Trends for Incoming Cases, Resolved Cases, Escalated Cases
Case Volume by various dimensions such as Origin, Location, Priority, Type
Leaders by CSAT percentage, SLA met percentage, Activities, Resolved cases
Most Used and Most viewed KB Articles and more.
These metrics and charts help to understand your support organization performance and analyze active cases
 workload across your service team and service queues.
Following table lists the CRM entities available for this service, as well as details on the filters applied to each of the
entity records.

CRM ENTITY FILTERS APPLIED

Account All accounts which have related cases that have been modified
in the last 90 days.

Activity All activities modified in the last 90 days

[modifiedon] > today - 90 days

Case All cases modified in the last 90 days

[modifiedon] > today - 90 days

Case Resolution Activity All case resolution activities modified in the last 90 days
[modifiedon] > today - 90 days

Contact All contacts, which have related cases that have been modified
in the last 90 days.

Knowledge Article All latest version of knowledge articles

[islatestversion] = true

Knowledge Article Incident All knowledge article incidents, which are modified in the last
90 days
[modifiedon] > today - 90 days

Queue All active queues

[statecode] = 0

Queue Item All case-related queue items created on the past 365 days
[createdon] > today - 365 days and
[objecttypecode] = 112

User All active users

[isdisabled] = false

System requirements
A valid Dynamics CRM Online 2016 or later instance (Power BI won't work with an on-premises CRM version).
If you do not have 2016 or later:
An administrator must enable the OData endpoint in the site settings.
An account with less than 100k records in any of the tables. Note if the account has access to more than 100k
records the import will fail.

Finding parameters
The address of the instance can be found in the URL bar of your browser. It typically has the format:
https://[instance_name].crm.dynamics.com .

Power BI only supports Dynamics CRM 2016 endpoints. The connection will not work with earlier versions of
CRM Online. Use Power BI Desktop to connect directly to your account.
Troubleshooting
If you're having trouble connecting, confirm:
you're providing the correct instance URL (check with your admin)
the instance is CRM Online 2016
the OData endpoint is enabled
Also, try connecting directly in Power BI Desktop, with the OData URL
https://[instance_name].crm.dynamics.com/api/data/v8.0/ .

If you confirm you have Dynamics CRM Online 2016 but you're still hitting issues connecting, contact your CRM
Admin to confirm you have all available updates.
If you do not have CRM Online 2016 or later, use the Power BI Desktop to connect directly to your account.
If you see an error "Data refresh failed as query exceeded the maximum limit of 100000 records," consider
connecting directly from the Power BI Desktop or leveraging the CRM solution template.

Next steps
What are apps in Power BI?
Get data in Power BI
More questions? Try asking the Power BI Community
 Connect to Microsoft Dynamics NAV with Power BI
1/4/2019 • 3 minutes to read • Edit Online

Getting insights into your Microsoft Dynamics NAV data is easy with Power BI. Power BI retrieves your data, both
Sales and Financial, then builds an app with a dashboard and reports based on that data. Power BI needs your
permissions to the tables where data is retrieved from, in this case sales and finance data. More details on
requirements below. After you install the app, you can view the dashboard and reports in the Power BI service
(https://powerbi.com), and in the Power BI mobile apps.
Connect to the Microsoft Dynamics NAV for Power BI or read more about the Dynamics NAV integration with
Power BI.

How to connect
1. Select Apps in the left navigation pane > select Get apps in the upper-right corner.

2. In AppSource, select the Apps tab, and search for the service you want.

3. Select Microsoft Dynamics NAV, then select Get.

4. When prompted, enter your Microsoft Dynamics NAV OData URL. The URL should match the following
pattern:
https://instance.navserver.com:7048/DynamicsNAV90_Instance1/OData/Company('CRONUS%20International%20Ltd.')

"instance.navserver.com" with your NAV Server name

"DynamicsNAV90_Instance1" with your NAV Server Instance name
"Company('CRONUS%20International%20Ltd.')" with your NAV Company name
An easy way to obtain this URL is in Dynamics NAV to go to Web Services, find the powerbifinance
web service and copy the OData URL, but leaving out the “/powerbifinance” from the URL string.
5. Select Basic and enter your Microsoft Dynamics NAV credentials.
You need admin credentials (or at least permissions to sales and finance data) for your Microsoft Dynamics
NAV account. Only Basic (Username and Password) authentication is currently supported.

6. Power BI will retrieve your Microsoft Dynamics NAV data and create a ready-to-use dashboard and report
for you.

View the dashboard and reports

When the import is complete, the new app will appear on the Apps page.
1. Select Apps in the left navigation pane > select the app.
2. You can ask a question by typing in the Q&A box, or click a tile to open the underlying report.
What now?
Try asking a question in the Q&A box at the top of the dashboard.
Select a tile to open the underlying report.
You can filter and highlight the data in the report, but you can't save your changes.
Your dataset is scheduled to refresh daily. You can change the refresh schedule or try refreshing it on demand
using Refresh Now.

What's included
The dashboard and reports contain data from the following tables (case sensitive):
ItemSalesAndProfit
ItemSalesByCustomer
powerbifinance
SalesDashboard
SalesOpportunities
SalesOrdersBySalesPerson
TopCustomerOverview

System requirements
To import your Microsoft Dynamics NAV data into Power BI, you need to have permissions to the sales and finance
data tables where data is retrieved from (listed above). The tables are also required to have some data, empty
tables will currently fail to import.

Troubleshooting
Power BI uses Microsoft Dynamics NAV's web services to retrieve your data. If you have a lot of data in your
Microsoft Dynamics NAV instance, a suggestion to minimize the impact on your web service usage is to change
the refresh frequency depending on your needs. Another suggestion is to have one admin create the app and share
it instead of having every admin create their own.
"Parameter validation failed, please make sure all parameters are valid"
If you see this error after typing your Microsoft Dynamics NAV URL. Make sure the following requirements are
satisfied:
The URL follows exactly this pattern:
https://instance.navserver.com:7048/DynamicsNAV90_Instance1/OData/Company('CRONUS%20International%20Ltd.')

"instance.navserver.com" with your NAV Server name

"DynamicsNAV90_Instance1" with your NAV Server Instance name
"Company('CRONUS%20International%20Ltd.')" with your NAV Company name
Make sure all the letters are lower case.
Make sure the URL is in 'https'.
Make sure there are no trailing forward slash at the end of the URL.
"Login failed"
If you get a "login failed" error after using your Microsoft Dynamics NAV credentials to login, then you may be
hitting one of the following issues:
The account you are using doesn't have permissions to retrieve the Microsoft Dynamics NAV data from your
account. Verify it is an admin account and try again.
The Dynamics NAV instance you're trying to connect to doesn't have a valid SSL certificate. In this case you'll
see a more detailed error message ("unable to establish trusted SSL relationship"). Note that self-signed certs
are not supported.
"Oops"
If you see an "Oops" error dialog after you pass the authentication dialog box, Power BI is running into an issue
while loading the data.
Verify the URL follows the pattern specified above. A common mistake is to specify:
https://instance.navserver.com:7048/DynamicsNAV90\_Instance1/OData

However, you need to include the 'Company('CRONUS%20International%20Ltd.')' section with your NAV
Company name:
https://instance.navserver.com:7048/DynamicsNAV90\_Instance1/OData/Company('CRONUS%20International%20Ltd.')

Next steps
What are apps in Power BI?
Get data in Power BI
More questions? Try asking the Power BI Community
 Connect to Office365Mon with Power BI
1/4/2019 • 2 minutes to read • Edit Online

Analyzing your Office 365 outages and health performance data is easy with Power BI and the Office365Mon
content pack. Power BI retrieves your data, including outages and health probes, then builds an out-of-box
dashboard and reports based on that data.
Connect to the Office365Mon content pack for Power BI.

NOTE
An Office365Mon admin account is required to connect and load the Power BI content pack.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Office365Mon > Get.

4. For Authentication Method, select oAuth2 > Sign In.

 When prompted, enter your Office365Mon admin credentials and follow the authentication process.

5. After Power BI imports the data you will see a new dashboard, report, and dataset in the left navigation
pane. New items are marked with a yellow asterisk *, select the Office365Mon entry.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

Troubleshooting
If you get a "login failed" error after using your Office365Mon subscription credentials to login, then the account
you are using doesn't have permissions to retrieve the Office365Mon data from your account. Verify it is an admin
account and try again.

Next steps
What is Power BI?
Get Data for Power BI
 Connect to Planview Enterprise with Power BI
1/4/2019 • 2 minutes to read • Edit Online

With the Planview Enterprise content pack, you can visualize your resource and work management data in entirely
new ways directly in Power BI. Use your Planview Enterprise sign-in credentials to interactively see your portfolio
investment spend, understand where you are over and under budget, and know how well your projects align with
your corporate strategic priorities. You can also extend the out-of-the box dashboard and reports to get the insights
that are most important to you.
Connect to the Planview Enterprise content pack in Power BI

NOTE
To import your Planview Enterprise data into Power BI, you must be a Planview Enterprise user with the Reporting Portal
Viewer feature enabled on your role. See additional requirements below.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. On the Power BI page, select Planview Enterprise, then select Get:

4. In the Planview Enterprise URL text box, enter the URL for the Planview Enterprise server you want to use.
In the Planview Enterprise Database text box, enter the name of the Planview Enterprise database, then click
Next.

5. On the Authentication Method list, select Basic if it is not already selected. Enter the Username and
Password for your account and select Sign In.
6. On the left pane, select Planview Enterprise from the list of dashboards.
Power BI imports Planview Enterprise data into the dashboard. Note that the data may take some time to
load.

What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now
System requirements
To import your Planview Enterprise data into Power BI, you must be a Planview Enterprise user with the Reporting
Portal Viewer feature enabled on your role. See additional requirements below.
This procedure assumes you have already signed in to the Microsoft Power BI home page with a Power BI account.
If you do not have a Power BI account, go to powerbi.com, and under Power BI - Cloud collaboration and
sharing, select Try free. Then click Get Data.

Next steps:
What is Power BI?
Get Data for Power BI
 Connect to Prevedere with Power BI
1/4/2019 • 2 minutes to read • Edit Online

Gain access to exclusive and critical financial information to confidently and proactively drive your business
forward.
Connect to the Prevedere content pack for Power BI.

NOTE
If you are not an existing Prevedere user, please use the sample key to try it out.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Prevedere and then Get.

4. For Authentication Method, select Key and enter your Prevedere API key.

5. Select Sign in to begin the import process. When complete, a new dashboard, report and model will appear
in the Navigation Pane. Select the dashboard to view your imported data.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The content pack gains insights on your retail forecasts, forecast models, leading indicators, and more.

System requirements
This content pack requires access to a Prevedere API key or the sample key (see below ).

Finding parameters
Existing customers can access their data using their API key. If you are not yet a customer, you can see a sample of
the data and analyses using the sample key.

Troubleshooting
The data may take some time to load depending on the size of your instance.

Next steps
Get started in Power BI
Get data in Power BI
 Connect to Project Online with Power BI
1/4/2019 • 2 minutes to read • Edit Online

Microsoft Project Online is a flexible online solution for project portfolio management (PPM ) and everyday work.
Project Online enables organizations to get started, prioritize project portfolio investments and deliver the
intended business value. The Project Online content pack for Power BI allows you to unlock insight from Project
Online to help manage projects, portfolios and resources.
Connect to the Project Online content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Microsoft Project Online > Get.

4. In the Project Web App URL text box, enter the URL for the Project Web Add (PWA) you want to connect
to and hit Next. Note this may differ from the example if you have a custom domain. In the PWA Site
Language text box, type the number that corresponds to your PWA site language. Type the single digit '1'
for English, '2' for French, '3' for German, '4' for Portuguese (Brazil), '5' for Portuguese (Portugal) and '6' for
Spanish.
5. For Authentication Method, select oAuth2 > Sign In. When prompted, enter your Project Online
credentials and follow the authentication process.

Note that you need to have Portfolio Viewer, Portfolio Manager or Administrator permissions for the Project Web
App you are connecting to.
6. You’ll see a notification indicating your data is loading. Depending on the size of your account this may take
some time. After Power BI imports the data you will see a new dashboard, 13 reports, and dataset in the left
navigation pane. This is the default dashboard that Power BI created to display your data. You can modify
this dashboard to display your data in any way you want.
7. Once your dashboard and reports are ready, go ahead and start exploring your Project Online data! The
Content Pack comes with 13 rich and detailed reports for the Portfolio Overview (6 report pages), Resource
Overview (5 report pages) and Project Status (2 report pages).
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now
Expand the Content Pack
Download the GitHub PBIT file to further customize and update the Content Pack

Next steps
Get started in Power BI
Get data in Power BI
 Connect to Projectplace by Planview with Power BI
1/4/2019 • 2 minutes to read • Edit Online

With the Projectplace by Planview content pack, you can visualize your collaborative project data in entirely new
ways directly in Power BI. Use your Projectplace sign-in credentials to interactively view key project statistics, find
out who your most active and productive team members are, and identify at-risk cards and activities across
projects in your Projectplace account. You can also extend the out-of-the box dashboard and reports to get the
insights that are most important to you.
Connect to the Projectplace content pack in Power BI

NOTE
To import your Projectplace data into Power BI, you must be a Projectplace user. See additional requirements below.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. On the Power BI page, select Projectplace by Planview, then select Get:

4. In the OData Feed URL text box, enter the URL for the Projectplace OData feed you want to use, as shown
in the following image:

5. On the Authentication Method list, select OAuth if it is not already selected. Hit Sign In and follow the login
flow.
6. On the left pane, select Projectplace from the list of dashboards. Power BI imports Projectplace data into
the dashboard. Note that the data may take some time to load.
The dashboard contains tiles that display data from your Projectplace database. The following image shows
an example of the default Projectplace dashboard in Power BI.

What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

System requirements
To import your Projectplace data into Power BI, you must be a Projectplace user. This procedure assumes you have
already signed in to the Microsoft Power BI home page with a Power BI account. If you do not have a Power BI
account, go to powerbi.com, and under Power BI - Cloud collaboration and sharing, select Try free. Then click
Get Data.

Next steps
What is Power BI?
Power BI - Basic Concepts
 Connect to QuickBooks Online with Power BI
1/4/2019 • 2 minutes to read • Edit Online

When you connect to your QuickBooks Online data from Power BI you immediately get a Power BI dashboard
and Power BI reports that provide insights about your business cash flow, profitability, customers, and more. Use
the dashboard and reports as they are, or customize them to highlight the information you care most about. The
data is refreshed automatically once a day.
Connect to the QuickBooks Online content pack for Power BI.

NOTE
To import your QuickBooks Online data into Power BI, you need to be an admin on your QuickBooks Online account and
sign in with your admin account credentials. You can't use this connector with QuickBooks Desktop software.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select QuickBooks Online, then select Get.

4. Select oAuth2 for Authentication Method and select Sign In.
5. When prompted, enter your QuickBooks Online credentials and follow the QuickBooks Online
authentication process. If you are already signed in to QuickBooks Online in your browser, you may not be
prompted for credentials.

NOTE
You need admin credentials for your QuickBooks Online account.

6. Select the company you would like to connect to Power BI in the next screen.

7. Select Authorize in the next screen to begin the import process. This can take a few minutes depending on
the size of your company data.

After Power BI imports the data, you see a new dashboard, report, and dataset in the left navigation pane.
New items are marked with a yellow asterisk *.
8. Select the QuickBooks Online dashboard. This is the dashboard Power BI created automatically to display
your imported data. You can modify this dashboard to display your data any way you want.

What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it
on demand using Refresh Now

Troubleshooting
“Oops! An error has occurred"
If you get this message after selecting Authorize:
“Oops! An error has occurred." Please close this window and try again.
The application has already been subscribed to by another user for this company. Please contact [admin email] to
make changes to this subscription.”

... this means another admin in your company has already connected to your company data with Power BI. Ask
that admin to share the dashboard with you. Currently, only one admin user can connect a particular QuickBooks
Online company dataset to Power BI. After Power BI creates the dashboard, the admin can shared it with multiple
colleagues on the same Power BI tenants.
"This app is not set up to allow connections from your country"
Currently Power BI only supports US editions of QuickBooks Online.

Next steps
What is Power BI?
Power BI - Basic Concepts
 Connect to Salesforce with Power BI
1/30/2019 • 2 minutes to read • Edit Online

With Power BI, you can easily connect to your Salesforce.com account. Creating this connection retrieves your data
and automatically provides a dashboard and related reports based on your data.
Connect to the Salesforce content pack for Power BI or read more about the Salesforce integration with Power BI.

How to Connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Click Salesforce and select Get.

4. Select Sign In to initiate the login flow.

5. When prompted, enter your Salesforce credentials. Click Allow so Power BI can access your basic
Salesforce information and data.

6. Configure what you'd like to import into Power BI using the dropdown option:
Dashboard
Select a predefined dashboard based on a persona (such as Sales Manager). These dashboards
bring in a specific set of standard data from Salesforce and will not include custom fields.
 Reports
Select one or more custom reports from your Salesforce account. These reports will match your
views in Salesforce and can include data from custom fields or objects.

If you don't see any reports, add or create them in your Salesforce account and try connecting again.
7. Click Connect to begin the import process. During the import you see a notification showing the import is
in progress. When the import is complete, you see a dashboard, report, and dataset for your Salesforce data
listed in the navigation pane on the left.
You can change this dashboard to display your data any way you want. You can ask questions with Q&A - Or click
a tile to open the underlying report and change the tiles in the dashboard.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard
Select a tile to open the underlying report
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

System requirements and considerations

Connected with a production Salesforce account that has API access enabled
Permission granted to the Power BI app during log-in
The account has sufficient API calls available to pull and refresh the data
A valid authentication token is required for refresh. Ensure you have 5 or less Salesforce data sets imported, as
Salesforce has a limit of 5 authentication tokens per application
The Salesforce Reports API has a restriction that supports up to 2,000 rows of data.

Troubleshooting
If you encounter any errors, please review the requirements above. Also note the ability to log in to a custom or
sandbox domain is not currently supported.
"Unable to connect to the remote server" message
If you get a message "Unable to connect to the remote server" when trying to connect to your Salesforce account,
see this solution on the Outsystems forum: Salesforce Connector Log In Error Message: Unable to connect to the
remote server

Next steps
What is Power BI?
Get Data
 Connect to SendGrid with Power BI
1/4/2019 • 2 minutes to read • Edit Online

The Power BI content pack for SendGrid allows you to extract insights and statistics from your SendGrid account.
Using the SendGrid content pack you can visualize your SendGrid statistics in a dashboard.
Connect to the SendGrid content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select the SendGrid content pack and click Get.

4. When prompted, provide your SendGrid user name and password. Select Sign In.
5. After Power BI imports the data, you see a new dashboard, report, and dataset in the left navigation pane,
populated with your email statistics for the past 90 days. New items are marked with a yellow asterisk *.

What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The following metrics are available in the SendGrid dashboard:
Overall email statistics - Requests, Delivered, Bounced, Spam Blocked, Spam Report, etc.
Email statistics by category
Email statistics by geography
Email statistics by ISP
Email statistics by device, client, browser
Next steps
What is Power BI?
Get Data
 Connect to ServiceNow with Power BI for incident
reporting
1/4/2019 • 2 minutes to read • Edit Online

ServiceNow offers multiple products and solutions including business, operations and IT management to improve
your business. This content pack includes multiple reports and insights on your open, recently resolved and
recently closed incidents.
Connect to the Power BI content pack for ServiceNow Incidents.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select ServiceNow Incidents > Get.

4. Provide the URL of your ServiceNow instance and the range of days/records to bring in. Note as soon as
one limit is hit the import will stop.
5. When prompted, enter your ServiceNow Basic credentials. Note single sign on is not supported today,
more details on the system requirements below.

6. Once the login flow is completed the import process will begin. When complete, a new dashboard, report
and model will appear in the Navigation Pane. Select the dashboard to view your imported data.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

System requirements
To connect you will need:
An account that can access yourorganization.service-now.com with Basic authentication (Single Sign-On is not
supported in this version)
The account must have rest_service role and read access to incident table

Troubleshooting
If you're hitting a credential error during load, please review the access requirements above. If you have the correct
permissions and are still hitting issues, please work with your ServiceNow admin to ensure you have any
additional permissions that may be required for your custom instance.
If you're seeing long load times, please review the number of incidents and number of days you specified during
connection and consider reducing it.

Next steps
What is Power BI?
Power BI - Basic Concepts
 Connect to Smartsheet with Power BI
1/4/2019 • 2 minutes to read • Edit Online

Smartsheet offers an easy platform for collaboration and file sharing. The Smartsheet content pack for Power BI
provides a dashboard, reports and dataset that shows an overview of your Smartsheet account. You can also use
the Power BI Desktop to connect directly to individual sheets in your account.
Connect to the Smartsheet content pack for Power BI.

NOTE
Smartsheet admin account is preferred to connect and load the Power BI content pack as it has additional access.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Smartsheet > Get.

4. For Authentication Method, select oAuth2 > Sign In.

 When prompted, enter your Smartsheet credentials and follow the authentication process.

5. After Power BI imports the data you will see a new dashboard, report, and dataset in the left navigation
pane. New items are marked with a yellow asterisk *, select the Smartsheet entry.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The Smartsheet content pack for Power BI includes an overview of your Smartsheet account, such as the number
of workspaces, reports and sheets you have, when they're modified etc. Admin users will also see some
information around the users in their system, such as top sheet creators.
To connect directly to individual sheets in your account, you can use the Smartsheet connector in the Power BI
Desktop.

Next steps:
What is Power BI?
Get Data for Power BI
 Connect to SparkPost with Power BI
1/4/2019 • 2 minutes to read • Edit Online

The Power BI content pack for SparkPost allows you to extract valuable datasets from your SparkPost account all
into one insightful dashboard. Using the SparkPost content pack you can visualize your overall email statistics,
including domains, campaigns, and engagement by ISP.
Connect to the SparkPost content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select the SparkPost content pack and click Get.

4. When prompted, provide your SparkPost API key and select Sign In. See details on finding this parameters
below.

5. Your data will start to load, depending on the size of you account this may take some time. After Power BI
imports the data, you’ll see the default dashboard, report, and dataset in the left navigation pane, populated
with your email statistics for the past 90 days. New items are marked with a yellow asterisk *.

What now?
Try asking a question in the Q&A box at the top of the dashboard
 Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The SparkPost content pack for Power BI includes information including unique clicks, accepted rates, bounce rates,
delayed rates, rejection rates and more.

Finding parameters
The content pack uses an API key to connect your SparkPost account to Power BI. You can find your API key in
your account under Account > API & SMTP (more details here). We suggest using an API key with permissions for
Message Events: Read-only and Metrics: Read-only
 SQL Database Auditing content pack for Power BI
1/4/2019 • 2 minutes to read • Edit Online

IMPORTANT
The SQL Database Auditing content pack has been deprecated, and is no longer available.

The Power BI content pack for Azure SQL Database Auditing allows you to understand your database activity and
gain insight into discrepancies and anomalies that could indicate business concerns or suspected security
violations.
Connect to the SQL Database Auditing content pack for Power BI.

NOTE
The content pack imports data from all tables that contain “AuditLogs” in their name and append it to a single data model
table named “AuditLogs”. The last 250k events will be included and the data will be refreshed daily.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select SQL Database Auditing > Get.

4. In the Connect to Sql Database Auditing window:
Enter the Azure Table Storage account name or URL where your logs are stored.
Enter the name of the SQL server that you are interested in. Enter “*” to load audit logs for all
servers.
Enter the name of the SQL database that you are interested in. Enter “*” to load audit logs for all
databases.
Enter the name of the Azure table that contains the logs you are interested. Enter “*” to load audit
logs from all tables that contain “AuditLogs” in their name.

IMPORTANT
For performance reasons it is advisable to always specify an explicit table name even if all audit logs are stored in a
single table.

Enter the start date of audit logs you are interested in. Enter “*” to load audit logs without a lower
time limit, or “1d” to load audit logs from the last day.
Enter the end date of audit logs you are interested in. Enter “*” to load audit logs without an upper
time limit.
5. For Authentication Method, select Key, enter your Account Key > Sign In.

6. After Power BI imports the data, you see a new dashboard, report, and dataset in the left navigation pane.
New items are marked with a yellow asterisk *.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

Next steps
Get data for Power BI What is Power BI?
 Connect to SQL Sentry with Power BI
1/4/2019 • 2 minutes to read • Edit Online

Analyzing your performance data collected by SQL Sentry is easy with Power BI. Power BI retrieves your data,
then builds a default dashboard and related reports based on that data.
Connect to the SQL Sentry content pack for Power BI.

NOTE
Access to a SQL Sentry account you use for connecting to http://cloud.sqlsentry.com and a Database ID you will monitor is
required to connect. Instructions for where to find the Database ID are below.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select SQL Sentry > Get.

4. Provide the Database ID of the database you’d like to monitor in Power BI. See more details on finding this
 below.

5. For Authentication Method, select oAuth2 > Sign In.

When prompted, enter your cloud.sqlsentry.com credentials and follow the SQL Sentry authentication
process.

The first time you connect, Power BI prompts you to allow read-only access to your account. Select Grant to
begin the import process. The import process can take a few minutes depending on the volume of data in
your account.

6. After Power BI imports the data you will see a new dashboard, report, and dataset in the left navigation
pane. New items are marked with a yellow asterisk *:
7. Select the SQL Sentry dashboard.
This is the default dashboard that Power BI creates to display your data. You can modify this dashboard to
display your data in any way you want.

What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The following data is available from SQL Sentry in Power BI :

TABLE NAME DESCRIPTION

Connection This table provides information about your SQL Sentry defined
connections.

Date This table contains dates from today back to the earliest date
from which performance data was collected and retained.

Downtime This table contains information related to your downtime and

uptime for each server that is monitored in your environment.

Memory Usage This table contains data about how much memory is available
or free in each of your servers.

Server This table contains records for each server in your

environment.
 TABLE NAME DESCRIPTION

Server Health This table contains data for all the events generated by
custom conditions in your environment, including severity and
count.

Finding Parameters
The Database ID can be found by logging into https://cloud.sqlsentry.com in a new web browser window. The
Database ID is listed on the main overview page:


The Database ID is also shown on the Database Details screen:


Troubleshooting
If data from some of your apps is not showing up in Power BI, check to make sure that you are using the correct
Database ID and that you have the authority to view the data.
If you are not the owner if the SQL Sentry database that is being synchronized to https://cloud.sqlsentry.com,
please contact your administrator to make sure you have rights to view the collected data.

Next steps
What is Power BI?
Get Data for Power BI
 Connect to Stripe with Power BI
1/4/2019 • 2 minutes to read • Edit Online

Visual and explore your Stripe data in Power BI with the Power BI content pack. The Power BI Stripe content pack
pulls in data about your Customers, Charges, Events and Invoices. The data includes the most recent ten thousand
events and five thousand charges over the last 30 days. The content will be refreshed automatically once per day at
a schedule you control.
Connect to the Stripe content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Stripe > Get.

4. Provide your Stripe API key to connect.

5. The import process will begin automatically. When complete, a new dashboard, report and model will
appear in the Navigation Pane, marked with an asterisk. Select the dashboard to view your imported data.

What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now
Next steps
What is Power BI?
Get Data for Power BI
 Connect to SweetIQ with Power BI
1/4/2019 • 2 minutes to read • Edit Online

The Power BI content pack pulls data from your SweetIQ account and generates set of out of box content allowing
you to easily explore your data. Use the SweetIQ content pack to analyze data about your locations, listings, ratings
and reviews. The data is set to refresh daily ensuring the data you're monitoring is up to date.
Connect to the SweetIQ content pack for Power BI.

How to connect
1. In the navigation pane on the left, click Get Data.

2. Select SweetIQ and click Get.

3. Provide your SweetIQ Client ID. This is typically an alpha-numeric value. For more details on finding this
value, see below.
4. Select Key authentication type and provide your Sweet IQ API Key. This is typically an alpha-numeric value.
For more details on finding this value, see below.

5. Power BI will start loading your data, which may take some time depending on the size of data in your
account. Once the load has completed, you'll see a new dashboard, report and dataset in the left navigation
pane.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

Finding parameters
The Client ID and API key for this content pack is not the same as your SweetIQ username and password.
Select a Client ID for one of the clients your account has access to. You can find the list of clients under "Client
Management" in your SweetIQ account.
Talk to your administrator for your API key, to access the data for specific client.

Next steps
What is Power BI?
Get Data for Power BI
 Connect to Troux for Power BI
1/4/2019 • 2 minutes to read • Edit Online

With the Troux content pack, you can visualize your Enterprise Architecture repository in entirely new ways directly
in Power BI. The content pack offers a set of insights on your business capabilities, the applications that deliver
those capabilities, and the technologies that support those applications that can be fully customized using Power
BI.
Connect to the Troux content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Troux > Get.

4. Specify your Troux OData URL. See details on finding those parameters below.

5. For Authentication Method, select Basic and provide your username and password (case sensitive), then
select Sign In.

6. After approving, the import process will begin automatically. When complete, a new dashboard, report and
model will appear in the Navigation Pane. Select the dashboard to view your imported data.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

System requirements
Access to the Troux OData feed and Troux 9.5.1 or higher is required.

Finding parameters
Your Customer Care team can provide your unique Troux OData feed URL to you

Troubleshooting
If you are seeing a timeout error after providing credentials, try connecting again.

Next steps
Get started in Power BI
Get data in Power BI
 Connect to Twilio with Power BI
1/4/2019 • 2 minutes to read • Edit Online

The Microsoft Twilio content pack for Power BI allows you to pull your data into Power BI and creates an out of box
Twilio dashboard and report that shows insights on your data. You can also create your custom reports and
dashboard on the dataset Power BI creates. The data will be refreshed once a day so you are always looking at the
latest data.
Connect to the Twilio content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Twilio > Get.

4. For Authentication Method, select oAuth2 > Sign In. When prompted provide your Twilio credentials
and authorize the Power BI application to access your data.
5. This will begin importing data from your Twilio account, and you will have your dashboard populated with
your calls and messages usage for the past 30 days.

What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now
What's included
The details for all calls and messages transactions for the last 30 days. You can do all sorts of analysis and
aggregation on this data.
A set of already aggregated stats that you may want to keep an eye on. This set includes:

All Time Calls Count

All Time Calls Duration
All Time Calls Price
All Time Messages Price
All Time Messages Count
All Time Count of Phone Numbers
All Time Price of Phone Numbers
All Time Twilio Client Calls Price
All Time Twilio Client Calls Duration
All Time Twilio Client Calls Count
All Time Total Price
All Time Inbound Calls Price
All Time Inbound Calls Duration
All Time Inbound Calls Count
All Time Outbound Calls Price
All Time Outbound Calls Duration
All Time Outbound Calls Count
This Month Calls Price
This Month Calls Duration
This Month Calls Count
This Month Messages Count
This Month Messages Price
This Month Count of Phone Numbers
This Month Price of Phone Numbers
This Month Twilio Client Calls Price
This Month Twilio Client Calls Duration
This Month Twilio Client Calls Count
This Month Total Price
This Month Inbound Calls Price
This Month Inbound Calls Duration
This Month Inbound Calls Count
This Month Outbound Calls Price
This Month Outbound Calls Duration
This Month Outbound Calls Count
This Month Inbound Messages Price
This Month Inbound Messages Count
This Month Outbound Messages Price
This Month Outbound Messages Count

Troubleshooting
If you have a very large amount of data in the past 30 days (hundreds of thousands of transactions), the data
retrieval step might fail. We are aware of the problem and working on solving it. Meanwhile, if you hit this issue
please use the support link at the top of your Power BI page to let us know and we'll contact you for further
investigations.

Next steps
Get started in Power BI
Get data in Power BI
 Connect to tyGraph with Power BI
1/4/2019 • 3 minutes to read • Edit Online

Visualize and explore your tyGraph data in Power BI with the Power BI content pack. Start by connecting to your
tyGraph account and loading the dashboard, reports and dataset. The out of box content includes insights such as
the Measure of Active Engagement (MAE score) and Top Contributors. Customize it further to highlight the
information you care most about. The data will be refreshed automatically according to a schedule that you set.
Connect to tyGraph for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select tyGraph > Get.

4. Specify the groups and time range you'd like to connect to, otherwise specify "All" to bring in all the data.
Note the date format that's expected (YYYY/MM/DD ). See details on finding the parameters below.

5. Provide your tyGraph key to connect. See details on finding this value below.
If you are a Yammer Verified Admin
Your API key is sent to you in an email when your tyGraph account is successfully created. If you can no
longer find your key, you can request a new one by sending an email to [email protected]. If you
do not yet have a tyGraph account, you can start a trial at http://www.tygraph.com/.
If you are not a Yammer Verified Admin
The tyGraph content pack requires a tyGraph account created by a Yammer verified administrator. Once
created, supplemental keys can be issued to users within the same organization. If your verified admin has
not yet created a tyGraph account, contact them to have them do so. If they have, you can request a key by
sending an email to [email protected].
6. After successful authentication, the import process will begin automatically. When complete, a new
dashboard, report and model will appear in the Navigation Pane. Select the dashboard to view your
imported data.

What now?
 Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

Finding parameters
You can bring in data on all the groups you have access to, or you can choose to specify a subset. You can also
create a subset of data by date. You can create multiple tyGraph dashboards to monitor specific sets of groups
and/or dates. Details on these parameters are below.
Groups
The tyGraph API can filter data by specific group ID. These are provided to the content pack in a comma separated
list.

Example: 2427647,946595,1154464

You can Identify the group ID for a particular group in Yammer by navigating to the feed for the group, and
examining the URL.

In the above example, the Yammer Group ID is 4054844

From Date
The From Date allows you to restrict the earliest value for the data returned. Only data created on or after this date
will be loaded into the content pack. The format of the From Date is YYYY/MM/DD.

Example: 2013/10/29

In the above example, all data from on or after October 29, 2013 will be loaded into the content pack.
To Date The To Date allows you to restrict the latest value for the data returned. It can be used in conjunction with
the From Date to load data from a range of dates. Only data created on or before this date will be loaded into the
content pack. The format of the To Date is YYYY/MM/DD.

Example: 2014/10/20

In the above example, all data from on or prior to October 20, 2014 will be loaded into the content pack.

Next steps
Get started in Power BI
Get data in Power BI
 Connect to UserVoice with Power BI
1/4/2019 • 2 minutes to read • Edit Online

Tracking and exploring your UserVoice data is easy with Power BI and the UserVoice content pack. Power BI
retrieves your data, including tickets, suggestions and satisfaction ratings, then builds an out-of-box dashboard and
reports based on that data.
Connect to the UserVoice content pack for Power BI.

NOTE
An admin account is required to connect to the Power BI content pack. The content pack also leverages the UserVoice API
and will contribute usage towards the UserVoice limits. More details below.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select UserVoice, then select Get.

4. When prompted, enter your UserVoice URL. The URL needs to follow the following pattern exactly
https://fabrikam.uservoice.com replacing "fabrikam" with your product or service name.

NOTE
There is no trailing slash at the end and the connection is in https.

5. When prompted, enter your UserVoice credentials and follow the UserVoice authentication process. If you
are already signed in to UserVoice in your browser, you may not be prompted for credentials. Grant the
Power BI application access to your data by clicking "Allow Access".

NOTE
You need admin credentials for your UserVoice account.

6. Power BI will retrieve your UserVoice data and create a ready-to-use dashboard and report for you. Power
BI will retrieve the following data: all your suggestions, all your open tickets, all tickets created in the last 30
days including closed ones and all the user satisfaction ratings.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

Troubleshooting
"Parameter validation failed, please make sure all parameters are valid"
If you see this error after typing your UserVoice URL. Make sure the following requirements are satisfied:
The URL follows exactly this pattern https://fabrikam.uservoice.com replacing "fabrikam" with your correct
UserVoice URL prefix.
Make sure all the letters are lower case.
Make sure the URL is in 'https'.
Make sure there are no trailing forward slash at the end of the URL.
"Login failed"
If you get a "login failed" error after using your UserVoice credentials to login, then the account you are using
doesn't have permissions to retrieve the UserVoice data from your account. Verify it is an admin account and try
again.
"Oops something went wrong"
If you get this error message while the data is being loaded, make sure your UserVoice account hasn't exceeded its
monthly APIs usage quota. If all looks good, try connecting again. If the problem persists, please contact Power BI
support at https://community.powerbi.com.
Other
The Power BI UserVoice content pack uses UserVoice's APIs to retrieve your data. Make sure you monitor your
API usage so that you don't exceed your limit. If you have a lot of data in your UserVoice account, a suggestion to
minimize the impact on your API usage is to change the refresh frequency from the current default which is once a
day to only refresh on weekdays or every other day depending on your needs. Another suggestion is to have one
admin create the content pack and share it with the rest of the team instead of having every admin in your
organization create their own putting extra unnecessary load on the APIs

Next steps
Get started in Power BI
Get data in Power BI
 Connect to VMob with Power BI
1/4/2019 • 2 minutes to read • Edit Online

Tracking and exploring your VMob data is easy with Power BI and the VMob content pack. Power BI will retrieve
the following data: User Statistics for all time and in the last 30 days, Retail KPI for the last 30 days and Campaign
Performance for the last 30 days.
Connect to the VMob content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select VMob > Get.

4. When prompted, enter your VMob URL and click on the Next button. This URL is provided by VMob
separately.

5. Choose Basic option in the Authentication method dropdown, enter your VMob username and password
and click on Sign In button.

6. The import process will begin automatically and Power BI will retrieve your VMob data to create a ready-to-
use dashboard and report for you.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

Next steps
Get started in Power BI
Get data in Power BI
 Connect to Webtrends with Power BI
1/4/2019 • 2 minutes to read • Edit Online

The Webtrends content pack for Power BI includes a variety of out of box metrics such total page views and visits
by traffic source. Visualizing your Webtrends data in Power BI starts by connecting to your Webtrends account.
You can use the dashboard and reports provided, or customize them to highlight the information you care most
about. The data will be refreshed automatically once per day.
Connect to the Webtrends content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Webtrends > Get.

4. The content pack connects to a specific Webtrends profile ID. See details on finding this parameter below.

5. Provide your Webtrends credentials to connect. Note that the username field expects your account and
username. See details below.

6. After approving, the import process will begin automatically. When complete, a new dashboard, report and
model will appear in the Navigation Pane. Select the dashboard to view your imported data.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The Webtrends content pack pulls data from the following reports:

REPORT NAME REPORT ID

Key Metrics

On-Site Searches 34awBVEP0P6

Exit Pages 7FshY8eP0P6

Next Pages CTd5rpeP0P6

Previous Pages aSdOeaUgnP6

Site Pages oOEWQj3sUo6

Onsite Ads Clickthroughs 41df19b6d9f

Cities aUuHskcP0P6

Countries JHWXJNcP0P6

Visitors xPcmTDDP0P6
 REPORT NAME REPORT ID

Visit Duration U5KAyqdP0P6

Search Phrases IKYEDxIP0P6

Traffic Sources JmttAoIP0P6

Search Engines yGz3gAGP0P6

Entry Pages i6LrkNVRUo6

NOTE
For SharePoint profiles, the metric names may be a little different than what's show in the Webtrends UI. The following
mapping is done to maintain consistency between SharePoint and Web profiles:

- Sessions = Visits
- New Users = New Visitors
- Views per Session = Page Views per Visit
- Avg Daily User Duration = Avg Time on Site per Visitor

System requirements
The content pack requires access to a Webtrends profile with the correct set of reports enabled.

Finding parameters
Your Webtrends Profile ID can be found in the URL after you've selected a profile:

Your credentials are the same as what you enter when you sign into Webtrends, however we expect your account
and username in the same line, separated by a backslash:
Troubleshooting
You may hit an issue while the content pack is loading, after you've provided your credentials. If you see the "Oops"
message during the loading, please review the troubleshooting suggestions below. If you're still having issues
please file a support ticket at https://support.powerbi.com
1. The correct Profile ID is being used, see the Finding Parameters for more details.
2. The user has access to the reports listed in the "What's included" section

Next steps
What is Power BI?
Power BI - Basic Concepts
 Connect to Windows Dev Center with Power BI
1/4/2019 • 2 minutes to read • Edit Online

Explore and monitor your Windows Dev Center app analytics data in Power BI with the Power BI content pack. The
data will be refreshed automatically once per day.
Connect to the Windows Dev Center content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Windows Dev Center > Get.

4. Enter the application ID of an app you own and click Next. See details on finding those parameters below.
5. For Authentication Method, select oAuth2 > Sign In. When prompted, enter your Azure Active
Directory credentials associated with your Windows Dev Center account (more details in System
Requirements).
6. After approving, the import process will begin automatically. When complete, a new dashboard, report and
model will appear in the Navigation Pane. Select the dashboard to view your imported data and choose a
tile to navigate to the underlying reports.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The Dev Center Power BI content pack includes analytics data for your app and IAP acquisitions, ratings, reviews
and app health. Data is limited to the last 3 months. and is a moving window, so the dates included will update as
the dataset refreshes.

System requirements
This content pack requires at least one at least one app published to the Windows Store and a Windows Dev
Center account (more details here).

Finding parameters
You can find the application ID for an app by going to the App identity page under App management.
The application ID is on the end of your URL for Windows 10 Store, https://www.microsoft.com/store/apps/
{applicationId}

Next steps
Get started in Power BI
Get data in Power BI
 Connect to Xero with Power BI
2/13/2019 • 3 minutes to read • Edit Online

Xero is easy to use online accounting software that’s designed specifically for small businesses. Create compelling
visualizations based on your Xero financials with this Power BI content pack. Your default dashboard includes
many small business metrics like cash position, revenue vs. expenses, profit loss trend, debtor days and return on
investment.
Connect to the Xero content pack for Power BI or learn more about the Xero and Power BI integration.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Xero > Get.

4. Enter a nickname for the organisation associated with your Xero account. Anything will do, this is mostly to
help users with multiple Xero organizations keep them all straight. See details on below.

5. For Authentication Method and select OAuth, when prompted sign into your Xero account and select the
organisation to connect to. Once the login completes, select Sign In to start the loading process.
6. After approving, the import process will begin automatically. When complete, a new dashboard, report and
model will appear in the Navigation Pane. Select the dashboard to view your imported data.

What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
 While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The content pack dashboard includes tiles and metrics that cover a variety of areas, with corresponding reports to
learn more:

AREA DASHBOARD TILES REPORT

Cash Daily cash flow Bank Accounts

Cash in
Cash out
Closing balance by account
Closing balance today

Customer Invoiced sales Customer

Invoiced sales by customer Inventory
Invoiced sales growth trend
Invoices due
Outstanding receivables
Overdue receivables

Supplier Billed purchases Suppliers

Billed purchases by supplier Inventory
Billed purchases growth trend
Bills due
Outstanding payables
Overdue payables

Inventory Monthly sales amount by product Inventory

Profit and loss Monthly profit and loss Profit and Loss
Net profit this fiscal year
Net profit this month
Top expense accounts

Balance sheet Total assets Balance Sheet

Total liabilities
Equity

Health Current ratio Health

Gross profit percentage Glossary and Technical Notes
Return on total assets
Total liabilities to equity ratio

The dataset also includes the following tables to customize your reports and dashboards:
Addresses
Alerts
Bank Statement Daily Balance
Bank Statements
Contacts
Expense Claims
Invoice Line Items
Invoices
 Items
Month End
Organisation
Trial Balance
Xero Accounts

System requirements
The following roles are required to access the Xero content pack: "Standard + Reports" or "Advisor".

Finding parameters
Provide a name for your organisation to track in Power BI. This allows you to connect to multiple different
organizations. Note that you cannot connect to the same organisation multiple times, as it will affect the scheduled
refresh.

Troubleshooting
Xero users must have the following roles to access the Xero content pack for Power BI: "Standard + Reports" or
"Advisor". The content pack relies on the user-based permissions to access reporting data through Power BI.
If you receieve a failure after loading for some time, verify how long it took to see that error message. Note that
the access token provided by Xero is only valid for 30min so accounts with more data than can be loaded in that
timeframe will fail. We're actively working to improve this.
During the load the tiles on the dashboard will be in a generic loading state. This is not expected to change until
the full load completes. If you receive a notification that your load completed but the tiles are still loading, try
refreshing the dashboard tiles using the ... in the top right of your dashboard.
If your content pack fails to refresh, please check if you have connected to the same organisation more than
once in Power BI. Xero only allows a single active connection to an organisation and you may see an error
indicating your credentials are invalid if you connect to the same one more than once.
For issues connecting the Xero content pack for Power BI like error messages or very slow load times, first clear
the cache / cookies and restart the browser, then reconnect to Power BI.
For other issues, please file a ticket at http://support.powerbi.com if the issue persists.

Next steps
Get started in Power BI
Get data in Power BI
 Connect to Zendesk with Power BI
1/4/2019 • 2 minutes to read • Edit Online

The Zendesk content pack offers a Power BI dashboard and a set of Power BI reports that provide insights about
your ticket volumes and agent performance. You can use the dashboard and reports provided, or customize them
to highlight the information you care most about. The data will be refreshed automatically once a day.
Connect to the Zendesk content pack or read more about the Zendesk integration with Power BI.

NOTE
A Zendesk Admin account is required to connect. More details on requirements below.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Zendesk > Get.

4. Provide the URL associated with your account. This will be in the form https://company.zendesk.com,
 see details on finding these parameters below.

5. When prompted, enter your Zendesk credentials. Select oAuth 2 as the Authentication Mechanism and click
Sign In. Follow the Zendesk authentication flow. (If you are already signed in to Zendesk in your browser,
you may not be prompted for credentials.)

NOTE
This content pack requires you connect with a Zendesk Admin account.

6. Click Allow to allow Power BI to access your Zendesk data.

7. Click Connect to begin the import process. After Power BI imports the data, you see a new dashboard,
report, and dataset in the left navigation pane. New items are marked with a yellow asterisk *.

What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now
What's included
The Power BI content pack includes data on the following:
Users (end users and agents)
Organizations
Groups
Tickets
There's also a set of measures that have been calculated, such as Average Wait Time and Tickets Solved in the Last
7 days. A full list is included in the content pack.

System requirements
A Zendesk Administrator account is required to access the Zendesk content pack. If you're an agent or an end user
and are interested in viewing your Zendesk data, please add a suggestion and review the Zendesk connector in the
Power BI Desktop.

Finding parameters
Your Zendesk URL will be the same as the URL you use to sign into your Zendesk account. If you're not sure of
your Zendesk URL, you can use the Zendesk login help.

Troubleshooting
If you are having issues connecting, please check your Zendesk URL and confirm you're using an Zendesk
administrator account.

Next steps
What is Power BI?
Get data
 Connect to Ziosk Survey Analytics with Power BI
1/4/2019 • 2 minutes to read • Edit Online

Ziosk Survey Analytics content pack for Power BI offers restaurants with Ziosk tablets unparalleled access to
insights provided by Ziosk survey data, including segmentation by day, location, employee, and more.
Connect to the Ziosk Survey Analytics content pack for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Ziosk Survey Analytics, then select Get.

4. Select OAuth 2 and then Sign In. When prompted, provide your Ziosk credentials.
5. Once connected, a dashboard, report and dataset will automatically be loaded. When completed, the tiles
will update with data from your Ziosk account.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The content pack includes data from the following tables:

- Alcohol Category
- Appetizer Category
- CommentKeywords
- Date
- Daypart
- Dessert Category
- FreeForm
- Kids Category
- Messages
- Premium Content Category
- Question
- Store
- Surveys
- Weekday

System requirements
A Ziosk account with permissions to the above tables is required in order to instantiate this content pack.

Next steps
What is Power BI?
Power BI - Basic Concepts
 Connect to Zuora with Power BI
1/4/2019 • 3 minutes to read • Edit Online

Zuora for Power BI allows you to visualize important revenue, billing, and subscription data. Use the default
dashboard and reports to analyze usage trends, track billings and payments, and monitor recurring revenue, or
customize them to meet your own unique dashboard and reporting needs.
Connect to the Zuora for Power BI.

How to connect
1. Select Get Data at the bottom of the left navigation pane.

2. In the Services box, select Get.

3. Select Zuora > Get.

4. Specify your Zuora URL. The URL is typically "https://www.zuora.com", see details on finding those
 parameters below.

5. For Authentication Method, select Basic and provide your username and password (case sensitive), then
select Sign In.

6. After approving, the import process will begin automatically. When complete, a new dashboard, report, and
model will appear in the Navigation Pane. Select the dashboard to view your imported data.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The content pack uses the Zuora AQUA API to pull in the following tables:

TABLES

Account InvoiceItemAdjustment Refund

AccountingCode Payment RevenueSchedule

AccountingPeriod PaymentMethod RevenueScheduleItem

BillTo Product Subscription

DateDim ProductRatePlan TaxationItem

Invoice ProductRatePlanCharge Usage

InvoiceAdjustment RatePlan

InvoiceItem RatePlanCharge

It also includes these calculated measures:

MEASURE DESCRIPTION PSEUDO-CALCULATION

Account: Payments Total payment amounts in a time SUM (Payment.Amount)

period, based on payment effective WHERE
date. Payment.EffectiveDate =<
TimePeriod.EndDate
AND Payment.EffectiveDate >=
TimePeriod.StartDate

Account: Refunds Total refund amounts in a time period, -1*SUM(Refund.Amount)

based on refund date. Amount is WHERE
reported as a negative number. Refund.RefundDate =<
TimePeriod.EndDate
AND Refund.RefundDate >=
TimePeriod.StartDate

Account: Net Payments Account Payments plus Account Account.Payments + Account.Refunds

Refunds in a time period.

Account: Active Accounts The count of accounts that were active COUNT (Account.AccountNumber)
in a time period. Subscriptions must WHERE
have started before (or on) time period Subscription.Status != "Expired"
start date. AND Subscription.Status != "Draft"
AND Subscription.SubscriptionStartDate
<= TimePeriod.StartDate
AND (Subscription.SubscriptionEndDate
> TimePeriod.StartDate
OR
Subscription.SubscriptionEndDate =
null) –evergreen subscription

Account: Average Recurring Revenue Gross MRR per active account in a time Gross MRR / Account.ActiveAccounts
period.

Account: Cancelled Subscriptions The count of accounts that cancelled a COUNT (Account.AccountNumber)
subscription in a time period. WHERE
Subscription.Status = "Cancelled"
AND Subscription.SubscriptionStartDate
<= TimePeriod.StartDate
AND Subscription.CancelledDate >=
TimePeriod.StartDate

Account: Payment Errors Total value of payment errors. SUM (Payment.Amount)

WHERE
Payment.Status = "Error"

Revenue Schedule Item: Recognized Total recognized revenue in an SUM (RevenueScheduleItem.Amount)

Revenue accounting period. WHERE
AccountingPeriod.StartDate =
TimePeriod.StartDate

Subscription: New Subscriptions Count of new subscriptions in a time COUNT (Subscription.ID)

period. WHERE
Subscription.Version = "1"
AND Subscription.CreatedDate <=
TimePeriod.EndDate
AND Subscription.CreatedDate >=
TimePeriod.StartDate
MEASURE DESCRIPTION PSEUDO-CALCULATION

Invoice: Invoice Items Total invoice item charge amounts in a SUM (InvoiceItem.ChargeAmount)
time period. WHERE
Invoice.Status = "Posted"
AND Invoice.InvoiceDate <=
TimePeriod.EndDate
AND Invoice.InvoiceDate >=
TimePeriod.StartDate

Invoice: Taxation Items Total taxation item tax amounts in a SUM (TaxationItem.TaxAmount)
time period. WHERE
Invoice.Status = "Posted"
AND Invoice.InvoiceDate <=
TimePeriod.EndDate
AND Invoice.InvoiceDate >=
TimePeriod.StartDate

Invoice: Invoice Item Adjustments Total invoice item adjustment amounts SUM (InvoiceItemAdjustment.Amount)
in a time period. WHERE
Invoice.Status = "Posted"
AND
InvoiceItemAdjustment.AdjustmentDate
<= TimePeriod.EndDate
AND
InvoiceItemAdjustment.AdjustmentDate
>= TimePeriod.StartDate

Invoice: Invoice Adjustments Total invoice adjustment amounts in a SUM (InvoiceAdjustment.Amount)

time period. WHERE
Invoice.Status = "Posted"
AND
InvoiceAdjustment.AdjustmentDate <=
TimePeriod.EndDate
AND
InvoiceAdjustment.AdjustmentDate >=
TimePeriod.StartDate

Invoice: Net Billings Sum of invoice items, taxation items, Invoice.InvoiceItems +

invoice item adjustments, and invoice Invoice.TaxationItems +
adjustments in a time period. Invoice.InvoiceItemAdjustments +
Invoice.InvoiceAdjustments

Invoice: Invoice Aging Balance Sum of posted invoice balances. SUM (Invoice.Balance)
WHERE
Invoice.Status = "Posted"

Invoice: Gross Billings Sum of invoice item charge amounts for SUM (InvoiceItem.ChargeAmount)
posted invoices in a time period. WHERE
Invoice.Status = "Posted"
AND Invoice.InvoiceDate <=
TimePeriod.EndDate
AND Invoice.InvoiceDate >=
TimePeriod.StartDate
 MEASURE DESCRIPTION PSEUDO-CALCULATION

Invoice: Total Adjustments Sum of processed invoice adjustments SUM (InvoiceAdjustment.Amount)

and invoice item adjustments associated WHERE
with posted invoices. Invoice.Status = "Posted"
AND InvoiceAdjustment.Status =
"Processed"
+
SUM (InvoiceItemAdjustment.Amount)
WHERE
Invoice.Status = "Posted"
AND invoiceItemAdjustment.Status =
"Processed"

Rate Plan Charge: Gross MRR Sum of monthly recurring revenue from SUM (RatePlanCharge.MRR)
subscriptions in a time period. WHERE
Subscription.Status != "Expired"
AND Subscription.Status != "Draft"
AND RatePlanCharge.EffectiveStartDate
<= TimePeriod.StartDate
AND RatePlanCharge.EffectiveEndDate
> TimePeriod.StartDate
OR RatePlanCharge.EffectiveEndDate =
null --evergreen subscription

System requirements
Access to the Zuora API is required.

Finding parameters
Provide the URL you typically sign into to access your Zuora data. The valid options are:
https://www.zuora.com
The URL corresponding to your service instance

Troubleshooting
The Zuora content pack pulls in many different aspects of your Zuora account. If you don't use certain features, you
may see corresponding tiles/reports empty. Contact Power BI Support if you have any issues loading.

Next steps
Get started in Power BI
Get data in Power BI
 Intro to organizational content packs in Power BI
1/23/2019 • 4 minutes to read • Edit Online

NOTE
You can't create organizational content packs or install them in the new workspace experiences preview. Now is a good
time to upgrade your content packs to apps, if you haven't started yet. Learn more about the new workspace experience.

Do you regularly distribute reports by email to your team? Try this instead: Package up your dashboards,
reports, Excel workbooks, and datasets and publish them to your team as an organizational content pack.
Content packs you create are easy for your team to find they are all in AppSource. Because they're part of
Power BI, they leverage all the features of Power BI, including interactive data exploration, new visuals, Q&A,
integration with other data sources, data refresh, and more.

Creating content packs is different from sharing dashboards or collaborating on them in an app workspace.
Read How should I collaborate on and share dashboards and reports? to decide on the best option for your
situation.
In AppSource, you can browse or search for content packs published to the entire organization, to distribution or
security groups, and to Office 365 groups you belong to. If you aren't a member of a specific group, you won't
see content packs shared with that group. All members of the group have the same read-only access to the
content pack data, reports, workbooks, and dashboards (unless it's a SQL Server Analysis Services (SSAS ) data
source, in which case your privileges are inherited with the data source).
The dashboards, reports, and Excel workbooks are read-only, but you can copy and use the dashboards and
reports as a starting point for creating your own personalized version of the content pack.

NOTE
Organizational content packs are only available when you and your colleagues have Power BI Pro licenses.

What is AppSource?
Publishing an organizational content pack adds it to AppSource. This centralized repository makes it easy for
members to browse and discover dashboards, reports, and datasets published for them.
To view AppSource, select Get Data > My Organization > Get.
The life cycle of an organizational content pack
Any Power BI Pro user can create, publish, and access organizational content packs. Only the content pack
creator can modify the workbook and dataset, schedule refresh, and delete it.
The lifecycle looks something like this:
1. In Power BI Pro, Nate creates a content pack and publishes it to the Marketing distribution group. The
refresh settings are inherited with the dataset and can only be changed by Nate.

NOTE
If Nate creates the content pack from within a Power BI app workspace he belongs to, then even if he leaves the
workspace, others in the Power BI workspace can take over ownership.

2. Nate sends mail to the distribution group, telling them about the new content pack.
3. In Power BI Pro, Jane, a member of the Marketing distribution group, searches for and connects to this
content pack in AppSource. She now has a read-only copy. She knows it's read-only because in the left
Navigation Pane, there is a sharing icon to the left of the dashboard name and report name. And when
she selects the dashboard, a lock icon lets Jane know she is looking at a content pack dashboard.
4. Say she decides to customize it. She now has her own copy of the dashboard and reports. Her work does
not affect the source, the original content pack, or other distribution group members. She is now working
on her own copy of the dashboard and report.
5. Nate makes updates to the dashboard and when it's ready, he publishes a new version of the content
pack.
Julio, another distribution group member, didn't customize the original content pack. The new changes
are automatically applied to his version of the content pack.
Jane did customize the content pack. She receives a notification that there's a new version. She can go
to AppSource and get the updated content pack without losing her personalized version. She'll now
have two versions: her personalized version and the updated content pack.
6. Say Nate changes the security settings. Julio and Jane no longer have access to the content. Or say
they're removed from the Marketing distribution group.
Julio didn't customize the original content pack, so the content is automatically removed.
Jane did customize the content pack. The next time she opens the dashboard all tiles from the original
content pack are gone, but tiles she pinned from other reports (that she still has permission to use) still
appear. The associated reports and dataset are no longer available (and don't appear in her left
navigation pane).
7. Or Nate deletes the content pack.
Julio didn't customize the original content pack, so the content is automatically removed.
Jane did customize the content pack. The next time she opens the dashboard all tiles from the original
content pack are gone, but tiles she pinned from other reports still appear. The associated reports and
dataset are no longer available (and don't appear in her left navigation pane).

Data security
All distribution group members have the same permissions to the data as the content pack creator. The one
exception to this is SQL Server Analysis Services (SSAS ) on-premises tabular datasets. Because the reports and
dashboards are connecting live to the on-premises SSAS model, the credentials of each individual distribution
group member are used to determine the data he or she can access.
Next steps
Create and publish an organizational content pack
Create and distribute an app in Power BI
Power BI - Basic Concepts
More questions? Try the Power BI Community
 Create and publish a Power BI organizational content
pack (tutorial)
1/14/2019 • 3 minutes to read • Edit Online

In this tutorial you create an organizational content pack, give access to a specific group, and publish it to your
organization's content pack library on Power BI.
Creating content packs is different from sharing dashboards or collaborating on them in a group. Read How
should I collaborate on and share dashboards and reports? to decide on the best option for your situation.
Creating an organizational content pack requires a Power BI Pro account for you and your colleagues.

NOTE
You can't create or install organizational content packs in the new workspace experiences preview. Now is a good time to
upgrade your content packs to apps, if you haven't started yet. Learn more about the new workspace experience.

Imagine you're the Release Manager at Contoso and you're getting ready for a new product launch. You've created
a dashboard with reports that you'd like to share with the other employees managing the launch. You want a way
to package up the dashboard and reports as a solution for your colleagues to use.
Want to follow along? In the Power BI service, go to Get Data > Samples > Opportunity Analysis Sample >
Connect to get your own copy.
1. In the left navigation pane, select the Opportunity Analysis Sample dashboard.
2. From the top navigation bar, select the cog icon > Create content pack.

3. In the Create Content Pack window, enter the following information.

Keep in mind that your organization's content pack library could end up with hundreds of content packs
published for the organization or for groups. Take time to give your content pack a meaningful name, to add
a good description, and to select the right audience. Use words that will make your content pack easy to find
via search.
a. Select Specific Groups and enter the full email addresses for individuals, Office 365 groups,
distribution groups, or security groups. For example:
 [email protected]; [email protected]
For this tutorial, try using your own or your group's email address.
b. Name the content pack Sales Opportunities.

TIP
Consider including the name of the dashboard in the name of the content pack. That way, your colleagues
will find the dashboard more easily after they connect to your content pack.

c. Recommended: Add a description. This helps coworkers more easily find the content packs that
they need. Besides a description, add keywords your coworkers might use to search for this content
pack. Include contact information in case your coworkers have a question or need help.
d. Upload an image or logo to make it easier for group members to find the content pack it's faster
to scan for an image than it is to find text. We used an image of the Opportunity Count 100% column
chart tile in the screen shot below.
e. Select the Opportunity Analysis Sample dashboard to add it to the content pack. Power BI
automatically adds the associated report and dataset. You can add others, if you want.

NOTE
Only the dashboards, reports, datasets, and workbooks that you can edit are listed. Thus, any that were
shared with you aren't in the list.

f. If you have Excel workbooks, you see them under Reports, with an Excel icon. You can add them to
the content pack, too.
 NOTE
If members of the group can't view the Excel workbook, you may need to share the workbook with them in
OneDrive for Business.

4. Select Publish to add the content pack to the group's organizational content pack library.
You see a success message when it publishes successfully.
5. When members of your group go to Get Data > My Organization, they tap in the search box and type
"Sales Opportunities".

6. They see your content pack.

TIP
The URL displayed in your browser is an unique address for this content pack. Want to tell your coworkers about this
new content pack? Paste the URL into an email.

7. They select Connect, and now they can view and work with your content pack.
Next steps
Intro to organizational content packs
Manage, update, and delete organizational content packs
Create a group in Power BI
What is OneDrive for Business?
More questions? Try the Power BI Community
 Organizational content packs: Copy, refresh, and get
access
3/7/2019 • 2 minutes to read • Edit Online

When an organizational content pack is published, all recipients see the same dashboard, reports, Excel
workbooks, datasets, and data (unless it's a SQL Server Analysis Services (SSAS ) data source). Only the content
pack creator can edit and republish the content pack. However, all recipients can save a copy of the content pack
that can live alongside the original.
Creating content packs is different from sharing dashboards or collaborating on them in a group. Read How
should I collaborate on and share dashboards and reports? to decide on the best option for your situation.

NOTE
You can't create or install organizational content packs in the new workspace experiences preview. Now is a good time to
upgrade your content packs to apps, if you haven't started yet. Learn more about the new workspace experience.

Create a copy of an organizational content pack

Create your own copy of the content pack, not visible to others.
1. Select the ellipsis (...) next to the content pack dashboard > Make a copy.

2. Select Save.
Now you have a copy that you can change. Nobody else will see changes you make.

NOTE
Previously, each time you installed a content pack or created a copy one, a new dataset would appear in the workspace
content list. A recent update simplified the experience to show just one item using the new referenced dataset icon:

Help! I can no longer access the content pack

This can happen for several reasons:
Membership changes: Content packs are published to email distribution groups, security groups, and Power
BI groups based on Office 365. If you are removed from the group, you will no longer have access to the
 content pack.
Distribution changes: The content pack creator changes the distribution. For example, if the content pack was
originally published to the entire organization but the creator republished it to a smaller audience, you may no
longer be included.
Security settings changes: If the dashboard and reports connect to on-premises SSAS data sources and
changes are made to the security settings, your permissions to that server may be revoked.

How are organizational content packs refreshed?

When the content pack is created, the refresh settings are inherited with the dataset. When you create a copy of
the content pack, the new version retains its link to the original dataset and its refresh schedule.
See Manage, update, and delete organizational content packs.

Next steps
Introduction to organizational content packs
Create a group in Power BI
More questions? Try the Power BI Community
 Manage, update, and delete organizational content
packs
1/14/2019 • 4 minutes to read • Edit Online

NOTE
You can't create organizational content packs or install them in the new workspace experiences preview. Now is a good time
to upgrade your content packs to apps, if you haven't started yet. Learn more about the new workspace experience.

You can package up and share your dashboards, reports, Excel workbooks, and datasets with your colleagues as
organizational content packs. Your colleagues can use them as-is, or they can create their own copies.
Creating content packs is different from sharing dashboards or collaborating on them in a group. Read How
should I collaborate on and share dashboards and reports? to decide on the best option for your situation.
You can only do some organizational content pack tasks if you're the content pack creator:
Republish.
Restrict or expand access to the content pack.
Set and change scheduled refresh.
Delete the content pack.

Modify and re-publish an organizational content pack

If you make changes to the original content pack dashboard, report, or Excel workbook, Power BI prompts you to
republish. Additionally, as the content pack creator, you can update any of the options you selected in the Create
Content Pack window when you were creating the original content pack.

Republish with new content

When you make and save a change to the dashboard that you included in a content pack, Power BI reminds you
to update it so others can see the changes. For example, if you pin a new tile or just change the name of the
dashboard.
1. Select View Content Packs in the message.

2. Or select the cog icon in the upper-right corner and select View Content Pack.
 Notice the warning icon . This lets you know that you've modified the content pack in some way and it
no longer matches what you published.
3. Select Edit.
4. Make any necessary changes in the Update Content Pack window and select Update. A Success
message appears.
For group members who haven't customized the content pack, the update is automatically applied.
Group members who have customized the content pack receive a notification that there is a new
version. They can go to AppSource and get the updated content pack without losing their personalized
version. They'll now have 2 versions: the personalized version and the updated content pack. In the
personalized version, all tiles from the original content pack will be gone. But tiles pinned from other
reports will still render. However, if the content pack owner deletes the dataset the content pack is based
on, then the whole report will be gone.

Update the audience: expand or restrict access

Another modification available to content pack creators is expanding and restricting access to the content pack.
Perhaps you published a content pack to a broad audience and you've decided to restrict access to a smaller
group.
1. Select the cog icon and choose View Content Packs.
2. Select Edit.
3. Make any necessary changes in the Update Content Pack window and select Update. For example,
delete the original distribution group in the Specific Groups field and replace it with a different
distribution group (that has fewer members).
A Success message appears.
For any coworker who isn't part of the new alias:
For group members who haven't customized the content pack, the dashboard and reports associated
with that content pack are no longer available and the content pack doesn't appear in the Navigation
Pane.
For group members who have customized the content pack, the next time they open the customized
dashboard, all tiles from the original content pack will be gone. But tiles pinned from other reports will
still render. The original content pack reports and dataset are no longer available, and the content pack
doesn't appear in the Navigation pane.
Refresh an organizational content pack
As the content pack creator, you can schedule refresh of the datasets. When you create and upload the content
pack, that refresh schedule is uploaded with the datasets. If you change the refresh schedule, you need to re-
publish the content pack (see above).

Delete an organizational content pack from AppSource

You can only delete a content pack from AppSource if you created it. If you've created an organizational content
pack in an app workspace, and then decide to delete that workspace, be sure to delete the content pack first. If you
delete the workspace without deleting the content pack first, you lose all access to those content packs and will
have to contact Microsoft Support for help.

TIP
You can delete your connection to a content pack you didn't create. That doesn't delete the content pack from AppSource.

1. To delete a content pack from AppSource, go to the app workspace where you created the content pack,
select the cog icon and choose View Content Packs.
2. Select Delete > Delete.
For group members who haven't customized the content pack, the dashboard and reports associated
with that content pack are automatically removed. They're no longer available, and the content pack
doesn't appear in the Navigation Pane.
For group members who have customized the content pack, the next time they open the customized
dashboard, all tiles from the original content pack will be gone. But tiles pinned from other reports will
still render. The original content pack reports and dataset are no longer available, and the content pack
doesn't appear in the Navigation pane.

Next steps
Introduction to organizational content packs
Create and distribute an app in Power BI
More questions? Try the Power BI Community
 Remove your connection to a Power BI
organizational content pack
1/14/2019 • 2 minutes to read • Edit Online

NOTE
You can't create organizational content packs or install them in the new workspace experiences preview. Now is a good time
to upgrade your content packs to apps, if you haven't started yet. Learn more about the new workspace experience.

A coworker created a content pack. You discovered it in AppSource and added it to your Power BI workspace.
Now you don't need it any longer. How do you remove it?
To remove a content pack, you remove its dataset.
In the left navigation pane, select the ellipsis to the right of the dataset and select Remove > Yes.

Removing the dataset also removes all associated reports and dashboards. However, removing your connection
to the content pack doesn't delete the content pack from your organization's AppSource. You can always return to
AppSource and add the content pack back to your workspace. You can only delete a content pack from AppSource
if you're the one who created it.

Next steps
Introduction to organizational content packs
Create and distribute an app in Power BI
Power BI basic concepts
More questions? Try the Power BI Community
 Power BI videos
1/14/2019 • 2 minutes to read • Edit Online

We have a YouTube channel for Power BI! You can visit our channel and, if you're new to Power BI a good place to
start is the Analyze and Visualize data with Power BI playlist.
Here are a few videos from that playlist to get you started.
Overview of Power BI service and Power BI Desktop.
https://www.youtube.com/embed/l2wy4XgQIu0
Collaborating and sharing.
https://www.youtube.com/embed/5DABLeJzQYM
Overview of Power BI mobile
https://www.youtube.com/embed/07uBWhaCo78
Power BI for developers
https://www.youtube.com/embed/47uXJW1GIUY

Watch some of our new uploads

Date slicer
Custom visualizations
Alerts in the Power BI service

More videos
Check out the following collection of sources and content for more videos.
Guided Learning for Power BI - a sequential learning tour of Power BI, in bite-size pieces
Guy in a Cube channel - fresh videos on Power BI features and capabilities

Next steps
What is Power BI?
More questions? Try asking the Power BI Community
 Power BI webinars
3/29/2019 • 4 minutes to read • Edit Online

Register for our upcoming live webinars or watch our recorded sessions on-demand.

Upcoming webinars
No webinars scheduled yet. Check back soon for more upcoming events.

Upcoming webinars from the Power BI community

Featured webinars
Get started with these popular on-demand webinars
Power BI and the Future of Modern and Enterprise BI
by Arun Ulag and Amir Netz
Register and watch now
Getting Started with Power BI
by Miguel Martinez
Register and watch now
Get Started with the Power BI Mobile App
by Maya Shenhav
Register and watch now
Learn to Navigate Your Way Through a Power BI Dashboard in 20 Minutes
by Miguel Martinez
Register and watch now
Strengthen Your Data Modeling Skills with Power BI
by Kasper de Jonge
Register and watch now
Microsoft Runs on Power BI – Financial Planning & Analysis Made Easy
by Cory Hrncirik and Miguel Martinez
Register and watch now
Supercharge Your Applications Using the Power BI JavaScript API
by Nimrod Shalit
Register and watch now
Power BI, Excel and Office 365: Optimize Your Enterprise Data
by Olaf Hubel and Miguel Martinez
Register and watch now
Simply Compelling — Tips for Better Visualization Design
by Miranda Li
Register and watch now

Browse the library of Power BI on-demand webinars from our community experts
On-Demand webinars
Watch recorded sessions at any time
Getting Started
Automate Day-to-Day Business Processes with Power BI, PowerApps, and Microsoft Flow
by Wim Coorevits and Enrique Plaza Garcia
Register and watch now
Power BI: Analytics Done Right
by Gohul Shanmugalingam
Register and watch now
Make Your Power BI Data Visual: Core Chart Types and How to Use Them
by Miranda Li
Register and watch now
How to Design Visually Stunning Power BI Reports
by Charles Sterling
Watch now
The Total Economic Impact of Microsoft Flow and PowerApps
by Jonathan Lipsitz and Enrique Plaza Garcia
Register and watch now
Better Together: 5 Benefits Excel Users Will Get From Using Power BI
by Carlos Otero and Miguel Martinez
Register and watch now
Learn about Power BI Embedded in 20 minutes
by Megan Asarrane and Colin Murphy
Register and watch now
Beyond the Spreadsheet
by Gohul Shanmugalingam
Register and watch now
Draw the right insights with Power BI and Visio
by Shakun Grover
Register and watch now
Transforming A Report From Good to GREAT!
by Reid Havens
Watch now
Partners
Achieving a Win-Win for Consumer Product Goods Manufacturers and Retailers
by Liz McCreesh from Thorogood
Register and watch now
Transform Customer Data into Retail Success with Power Bi
by Angad Soni from Hitachi Solutions
Register and watch now
Proven Healthcare Solutions to Improve Both Patient Outcomes and Profitability
by Stephen Cracknell and Stuart Macanliss from US Medical IT
Register and watch now
Boost Your BI with Location Intelligence
by Scott Ball from Esri and Enrique Plaza from Microsoft
Register and watch now
Applied Intelligence for Sales & Services
by Ed Bobrin from Avanade
Register and watch now
5 Habits of a Successful Trend Curator - Rohit Bhargava
by Rohit Bhargava from Non-Obvious
Register and watch now
Manufacturers: Your industry is going through a digital transformation - Maintain leadership by
leveraging analytics to maximize profitability
by Jon Thompson from Blue Margin and Jim Pastor from Elgin Fastener Group
Register and watch now
Visualize public or private datasets with the new Power BI and data.world connector
by Patrick McGarry and Miguel Martinez
Register and watch now
Community
Power BI Tricks, Tips and Tools from the owners of PowerBI.Tips
by Mike Carlo and Seth Bauer
Watch now
Storytelling with your data and Power BI
by Tristan Malherbe
Watch now
Practical DAX for Power BI
by Phil Seamark
Watch now
Developing with Power BI Embedding – The April 2018 Update
by Ted Pattison
Watch now
Power BI security deep dive
by Kasper de Jonge
Watch now
Ask a Partner: Developing Custom Visuals for Power BI
by Ted Pattison
Watch now
Advanced Topics
Advanced Analytics with Excel and Power BI
by Nagasaikiran Kambhampati and Miguel Martinez
Register to watch
Download the Advanced Analytics Starter Kit to follow along
Power BI adoption framework webinar series
by Manu Kanwarpal and Paul Henwood
Register and watch now - Part 1 - Adoption: Adopt a data-driven culture
Register and watch now - Part 2 - Governance: Govern your Power BI usage
Register and watch now - Part 3 - Service Management: Power BI Service Management Insights
Register and watch now - Part 4 - Security: Keeping your data secure with Power BI
Register and watch now - Part 5 - Rollout: Successfully rolling out Power BI
Office 365 Finance Pros Webinar Series
by Mark Traverso, Carlos Otero, Johnnie Thomas, Amanda Cofsky and Miguel Martinez
Learn tips, tricks & best practices to achieve more in your day-to-day work using Office 365.
Register and watch now
Be a Full Stack Power BI Jedi – A walkthrough of Power BI most advanced features through Star Wars
data
by Gil Raviv
Watch now
How to Implement a Successful Data Governance Strategy That Makes Your Organization More Secure
by Ajay Anandan
Register and watch now
Accelerating modern BI adoption with Power BI Premium
by Sirui Sun and Miguel Martinez
Register and watch now
What's new and exciting in Power BI Report Server
by Riccardo Muti, Chris Finlan and Chinmay Joshi
Register and watch now
How Microsoft does Power BI
by Kirkland Barrett
Register and watch now

See also
Power BI whitepapers
Microsoft Data Insights Summit 2017 on-demand sessions
What is Power BI?
Follow @MSPowerBI on Twitter
Subscribe to our YouTube channel
More questions? Try asking the Power BI Community
 Supported languages and countries/regions for
Power BI
3/18/2019 • 5 minutes to read • Edit Online

This article provides lists of supported languages and countries/regions for the Power BI service, Power BI
Desktop, and Power BI documentation.

Countries and regions where Power BI is available

For a list of countries and regions where Power BI is available, see the international availability list.

Languages for the Power BI service

The Power BI service (in the browser) is available in the following 44 languages:
Arabic
Basque - Basque
Bulgarian - Български
Catalan - català
Chinese (Simplified) - 中文(简体)
Chinese (Traditional) - 中文(繁體)
Croatian - hrvatski
Czech - čeština
Danish - dansk
Dutch - Nederlands
English - English
Estonian - eesti
Finnish - suomi
French - français
Galician - galego
German - Deutsch
Greek - Ελληνικά
Hebrew
Hindi -
Hungarian - magyar
Indonesian - Bahasa Indonesia
Italian - italiano
Japanese - 日本語
Kazakh - Қазақ
Korean - 한국어
Latvian - latviešu
Lithuanian - lietuvių
Malay - Bahasa Melayu
Norwegian (Bokmål) - norsk (bokmål)
Polish - Polski
 Portuguese (Brazil) - Português
Portuguese (Portugal) - português
Romanian - română
Russian - Русский
Serbian (Cyrillic) - српски
Serbian (Latin) - srpski
Slovak - slovenčina
Slovenian - slovenski
Spanish - español
Swedish - svenska
Thai - ไทย
Turkish - Türkçe
Ukrainian - українська
Vietnamese - Tiếng Việt
What's translated
Menus, buttons, messages, and other elements of the experience are translated into your language, making it
easier to navigate and interact with Power BI.
At this time, a few features are available in English only:
Dashboards and reports that Power BI creates for you when you connect to services such as Microsoft
Dynamics CRM, Google Analytics, Salesforce, and so on. (You can still create your own dashboards and reports
in your own language.)
Exploring your data with Q&A.
Stay tuned as we work to bring additional features to other languages.
Choose your language in the Power BI service
1. In the Power BI service, select the Settings icon > Settings.
2. On the General tab > Language.
3. Select your language > Apply.
Choose your language in the browser
Power BI detects your language based on the language preferences on your computer. The way you access and
change these preferences may vary depending on your operating system and browser. Here's how to access these
preferences from Internet Explorer and Google Chrome.
Internet Explorer (version 11)
1. Click the Tools button in the top-right corner of your browser window:

2. Click Internet Options.

3. In the Internet Options dialog, on the General tab under Appearance, click the Languages button.
Google Chrome (version 42)
1. Click the menu button in the top-right corner of your browser window:
2. Click Settings.
3. Click Show advanced settings.
4. Under Languages, click the Language and input settings button.
5. Click Add, select a language, and click OK.

The new language is at the end of the list.

6. Drag the new language to the top of the list, and click Display Google Chrome in this language.

You may need to close and reopen your browser to see the change.

Choose the language or locale of Power BI Desktop

You have two ways of getting Power BI Desktop: You can download it, or install it from the Windows Store.
When you install Power BI Desktop from the Windows Store, it installs all the languages and shows the
language that corresponds to the Windows default language.
When you download Power BI Desktop, you choose the language when you download it.
You can also choose a locale to be used when importing data for a specific report.
Choose a language for Power BI Desktop installed from the Windows Store
1. Install Power BI Desktop from the Windows Store.
2. To change the language, on your computer search for Windows Settings.
3. Select Time & language.
4. Select Region & language, select a language, and select Set as default.

The next time you start Power BI Desktop it will use the language you set as the default.
Choose a language when you download Power BI Desktop
The language you choose for Power BI Desktop affects the display format of numbers and dates in reports.
Select a language when you download Power BI Desktop.
To change the language in Power BI Desktop, go back to the download page and download it in a different
language.
Choose the locale for importing data into Power BI Desktop
Whether you download Power BI Desktop or install it from the Windows Store, you can choose a locale for a
specific report to be something other than the locale in your version of Power BI Desktop. This changes the way
data is interpreted when it’s imported from your data source, for example whether "3/4/2017" is interpreted as 3rd
April or March 4th.
1. In Power BI Desktop, go to File > Options and settings > Options.
2. Under Current file, select Regional Settings.
3. In the Locale for import box, select a different locale.
4. Select OK.
Choose the language for the model in Power BI Desktop
Besides setting the language for the Power BI Desktop application, you can also set the model language. The
model language affects chiefly two things:
How we compare and sort strings. For example, because Turkish has two of the letter i, depending on the
collation of your database, the two can end up in different orders when sorting.
The language Power BI Desktop uses when creating hidden date tables from date fields. For example, fields are
called Month/Monat/Mois, etc.

NOTE
Power BI’s model currently uses a locale that is not case-sensitive (or kana-sensitive) so “ABC” and “abc” will be treated as
equivalent. If “ABC” is loaded into the database first, other strings that differ only by case such as “Abc” won’t be loaded as a
separate value.

Here's how to set the model language.

1. In Power BI Desktop, go to File > Options and settings > Options.
2. Under Global, select Regional Settings.
3. In the Model language box, select a different language.
 NOTE
Once created, the language of a Power BI model can't be changed.

Languages for the help documentation

Help is localized in these 10 languages:
Chinese (Simplified) - 中文(简体)
Chinese (Traditional) - 中文(繁體)
French - français
German - Deutsch
Italian - italiano
Japanese - 日本語
Korean - 한국어
Portuguese (Brazil) - Português
Russian - Русский
Spanish - español

Next steps
Are you using one of the Power BI mobile apps? See Supported languages in the Power BI mobile apps for
details.
Questions? Try asking the Power BI Community.
Still have an issue? Please visit the Power BI support page.
 Whitepapers for Power BI
3/28/2019 • 2 minutes to read • Edit Online

Whitepapers allow you to explore Power BI topics at a deeper level. Here you can find a list of available
whitepapers for Power BI.

WHITEPAPER DESCRIPTION DATE

Power BI and Dataflows This whitepaper describes dataflows in November 2018

technical detail, and describes the
capabilities and initiatives behind
dataflow features and functionality.

Microsoft Power BI Premium Describes Power BI Premium, both as it October 2017

exists when launched and also how it
will evolve.

Power BI Premium Planning and This paper provides guidance and best March 2018
Deployment practices for planning and deploying
Premium capacity for well-defined
workloads.

Plan capacity for embedded analytics This paper provides guidance for the October 2017
with Power BI Premium app developer/ISV to determine the
most appropriate capacity for its
business.

Planning a Power BI Enterprise This technical whitepaper outlines July 2018

Deployment considerations for a well-performing
and secure organizational Power BI
deployment.

Capacity planning guidance for Power This paper aims to offer guidance on March 2018
BI Report Server capacity planning for Power BI Report
Server by sharing results of numerous
load test executions of various
workloads against a report server.

Security Provides a detailed explanation of March 2019

security within Power BI.

Distribute Power BI content to external This paper outlines how to distribute March 2018
guest users using Azure Active content to users outside the
Directory B2B organization using the integration of
Azure Active Directory Business-to-
business (AAD B2B).

Advanced Analytics with Power BI Describes the advanced analytics February 2017
capabilities of Power BI, including
predictive analytics, custom
visualizations, R integration, and data
analysis expressions.
 WHITEPAPER DESCRIPTION DATE

Best design practices for reports and Provides best practices for designing June 2018
visuals reports in Power BI.

Bidirectional filtering Explains bidirectional cross-filtering in July 2018

Power BI Desktop (the whitepaper also
covers SQL Server Analysis Services
2016, both have the same behavior).

DirectQuery in SQL Server 2016 For SQL Server 2016, DirectQuery was January 2017
Analysis Services redesigned for dramatically improved
speed and performance, however, it is
also now more complex to understand
and implement.

Power BI and SAP BW This document describes how SAP February 2018
customers can benefit from connecting
Power BI to their existing SAP Business
Warehouse (BW) systems.

Power BI Governance and Deployment Provides concepts, options and March 2016
Approaches suggestions for governance within the
Power BI ecosystem.

Securing the Tabular BI Semantic Model This paper introduces the security April 2016
model for tabular BI semantic and
Power BI. You will learn how to create
roles, implement dynamic security,
configure impersonation settings,
manage roles, and choose a method for
connecting to models that works in
your network security context.

Power BI and GDPR This link takes you to the list of April 2018
whitepapers on the Service Trust Portal,
including the Microsoft Power BI GDPR
whitepaper.

NOTE
If you’re interested in viewing or deleting personal data, please review Microsoft's guidance in the Windows Data Subject
Requests for the GDPR site. If you’re looking for general information about GDPR, see the GDPR section of the Service Trust
portal.

More questions? Try asking the Power BI Community

 Power BI security whitepaper
3/25/2019 • 36 minutes to read • Edit Online

Summary: Power BI is an online software service ( SaaS, or Software as a Service) offering from Microsoft that
lets you easily and quickly create self-service Business Intelligence dashboards, reports, datasets, and
visualizations. With Power BI, you can connect to many different data sources, combine and shape data from those
connections, then create reports and dashboards that can be shared with others.
Writer: David Iseminger
Technical Reviewers: Pedram Rezaei, Cristian Petculescu, Siva Harinath, Tod Manning, Haydn Richardson, Adam
Wilson, Ben Childs, Robert Bruckner, Sergei Gundorov, Kasper de Jonge
Applies to: Power BI SaaS, Power BI Desktop, Power BI Embedded, Power BI Premium

NOTE
You can save or print this whitepaper by selecting Print from your browser, then selecting Save as PDF.

Introduction
Power BI is an online software service ( SaaS, or Software as a Service) offering from Microsoft that lets you easily
and quickly create self-service Business Intelligence dashboards, reports, datasets, and visualizations. With Power
BI, you can connect to many different data sources, combine and shape data from those connections, then create
reports and dashboards that can be shared with others.
The Power BI service is governed by the Microsoft Online Services Terms, and the Microsoft Enterprise Privacy
Statement. For the location of data processing, refer to the Location of Data Processing terms in the Microsoft
Online Services Terms. For compliance information, the Microsoft Trust Center is the primary resource for Power
BI. The Power BI team is working hard to bring its customers the latest innovations and productivity. Power BI is
currently in Tier D of theOffice 365 Compliance Framework.
This article describes Power BI security by providing an explanation of the Power BI architecture, then explaining
how users authenticate to Power BI and data connections are established, and then describing how Power BI stores
and moves data through the service. The last section is dedicated to security-related questions, with answers
provided for each.

Power BI Architecture
The Power BI service is built on Azure, which is Microsoft's cloud computing platform. Power BI is currently
deployed in many datacenters around the world – there are many active deployments made available to customers
in the regions served by those datacenters, and an equal number of passive deployments that serve as backups for
each active deployment.
Each Power BI deployment consists of two clusters – a Web Front End (WFE ) cluster, and a Back-End cluster.
These two clusters are shown in the following image, and provide the backdrop for the rest of this article.
Power BI uses Azure Active Directory (AAD ) for account authentication and management. Power BI also uses the
Azure Traffic Manager (ATM ) to direct user traffic to the nearest datacenter, determined by the DNS record of
the client attempting to connect, for the authentication process and to download static content and files. Power BI
uses the Azure Content Delivery Network (CDN ) to efficiently distribute the necessary static content and files
to users based on geographical locale.
The WFE Cluster
The WFE cluster manages the initial connection and authentication process for Power BI, using AAD to
authenticate clients and provide tokens for subsequent client connections to the Power BI service.

When users attempt to connect to the Power BI service, the client's DNS service may communicate with the Azure
Traffic Manager to find the nearest datacenter with a Power BI deployment. For more information about this
process, see Performance traffic routing method for Azure Traffic Manager.
The WFE cluster nearest to the user manages the login and authentication sequence (described later in this article),
and provides an AAD token to the user once authentication is successful. The ASP.NET component within the WFE
cluster parses the request to determine which organization the user belongs to, and then consults the Power BI
Global Service. The Global Service is a single Azure Table shared among all worldwide WFE and Back-End
clusters that maps users and customer organizations to the datacenter that houses their Power BI tenant. The WFE
specifies to the browser which Back-End cluster houses the organization's tenant. Once a user is authenticated,
subsequent client interactions occur with the Back-End cluster directly, without the WFE being an intermediator for
those requests.
The Power BI Back-End Cluster
The Back-End cluster is how authenticated clients interact with the Power BI service. The Back-End cluster
manages visualizations, user dashboards, datasets, reports, data storage, data connections, data refresh, and other
aspects of interacting with the Power BI service.

The Gateway Role acts as a gateway between user requests and the Power BI service. Users do not interact
directly with any roles other than the Gateway Role.
Important: It is imperative to note that only Azure API Management (APIM ) and Gateway (GW ) roles are
accessible through the public Internet. They provide authentication, authorization, DDoS protection, Throttling,
Load Balancing, Routing, and other capabilities.
The dotted line in the Back-End cluster image, above, clarifies the boundary between the only two roles that are
accessible by users (left of the dotted line), and roles that are only accessible by the system. When an authenticated
user connects to the Power BI Service, the connection and any request by the client is accepted and managed by
the Gateway Role and Azure API Management, which then interacts on the user's behalf with the rest of the
Power BI Service. For example, when a client attempts to view a dashboard, the Gateway Role accepts that
request then separately sends a request to the Presentation Role to retrieve the data needed by the browser to
render the dashboard.
Power BI Premium
Power BI Premium offers a dedicated, provisioned, and partitioned service workspace for subscribers that need
dedicated resources for their Power BI activities. When a customer signs up for a Power BI Premium subscription,
the Premium capacity is created through the Azure Resource Manager. The rollout of that subscription assigns a
set of virtual machines commensurate with the subscription level, in the datacenter where their Power BI tenant is
hosted (with the exception of multi-geo environments, as described later in this document), initiated as an Azure
Service Fabric deployment.

Once created, all communication with the Premium cluster is routed through the Power BI Back-End cluster, where
a connection to the client's dedicated Power BI Premium subscription virtual machines is established.
Data Storage Architecture
Power BI uses two primary repositories for storing and managing data: data that is uploaded from users is typically
sent to Azure Blob storage, and all metadata as well as artifacts for the system itself are stored behind a firewall in
Azure SQL Database.
For example, when a user imports an Excel workbook into the Power BI service, an in-memory Analysis Services
tabular database is created, and the data is stored in-memory for up to one hour (or until memory pressure occurs
on the system). The data is also sent to Azure Blob storage.
Metadata about a user's Power BI subscription, such as dashboards, reports, recent data sources, workspaces,
organizational information, tenant information, and other metadata about the system is stored and updated in
Azure SQL Database. All information stored in Azure SQL Database is fully encrypted using Azure SQL's
Transparent Data Encryption (TDE ) technology. All data that is stored in Azure Blob storage is also encrypted. More
information about the process of loading, storing, and moving data is described in the Data Storage and
Movement section.

Tenant Creation
A tenant is a dedicated instance of the Azure AD service that an organization receives and owns when it signs up
for a Microsoft cloud service such as Azure, Microsoft Intune, Power BI, or Office 365. Each Azure AD tenant is
distinct and separate from other Azure AD tenants.
A tenant houses the users in a company and the information about them - their passwords, user profile data,
permissions, and so on. It also contains groups, applications, and other information pertaining to an organization
and its security. For more information, see What is an Azure AD tenant.
A Power BI tenant is created in the datacenter deemed closest to the country (or region) and state information
provided for the tenant in Azure Active Directory, which was provided when the Office 365 or Power BI service
was initially provisioned. The Power BI tenant does not move from that datacenter location today.
Multiple Geographies (Multi-geo )
Some organizations require a Power BI presence in multiple geographies, or regions, based on business needs. For
example, a business may have its Power BI tenant in the United States but may also do business in other
geographical areas, such as Australia, and need Power BI services and data to remain in that remote region.
Beginning in the second half of 2018, organizations with their tenant in one geography can also access Power BI
resources in another geography when properly provisioned. This feature is referred to as multi-geo for
convenience and reference throughout this document.
There are technical implications to keep in mind when operating in different geographies, which are clarified
throughout this document. Important considerations include the following:
A cached query stored in a remote region will stay in that region at rest, however other data in transit may go
back and forth between multiple geographies.
Reports in PBIX or XLSX files in a remote region that are published to Power BI sometimes result in a copy or
shadow copy being stored in Power BI's Azure Blob storage, and when that occurs the data is encrypted using
 Azure Storage Service Encryption (SSE ).
When moving data from one region to another in a multi-geo environment, garbage collection in the region
from which the data was moved occurs within 7 to 10 days, at which point the copy of data moved from the
original region will be destroyed.
The following image illustrates how the Power BI services provided in the remote region with a multi-geo
environment is routed through the Power BI Back-End cluster, where a connection to the client's remote Power BI
subscription virtual machine is established.

Datacenters and Locales

Power BI is offered in certain regions, based on where Power BI clusters are deployed in regional datacenters.
Microsoft plans to expand its Power BI infrastructure into additional datacenters.
The following links provide additional information about Azure datacenters.
Azure Regions – information about Azure's global presence and locations
Azure Services, by region – a complete listing of Azure services (both infrastructure services and platform
services) available from Microsoft in each region.
Currently, the Power BI service is available in specific regions, serviced by datacenters as described in the
[Microsoft Trust Center]((https://www.microsoft.com/TrustCenter/CloudServices/business-application-
platform/data-location). The following link shows a map of Power BI datacenters, you can hover over a region to
see the datacenters located there:
Power BI Datacenters
Microsoft also provides datacenters for sovereignties. For more information about Power BI service availability for
national clouds, see Power BI national clouds.
For more information on where your data is stored and how it is used, refer to the Microsoft Trust Center.
Commitments about the location of customer data at rest are specified in the Data Processing Terms of the
Microsoft Online Services Terms.

User Authentication
User authentication to the Power BI service consists of a series of requests, responses, and redirects between the
user's browser and the Power BI service or the Azure services used by Power BI. That sequence describes the
process of user authentication in Power BI. For more information about options for an organization's user
authentication models (sign-in models), see Choosing a sign-in model for Office 365.
Authentication Sequence
The user authentication sequence for the Power BI service occurs as described in the following steps, which are
illustrated in the following images.
1. A user initiates a connection to the Power BI service from a browser, either by typing in the Power BI
address in the address bar (such as https://app.powerbi.com) or by selecting Sign In from the Power BI
landing page (https://powerbi.microsoft.com). The connection is established using TLS 1.2 and HTTPS, and
all subsequent communication between the browser and the Power BI service uses HTTPS. The request is
sent to the Azure Traffic Manager.
2. The Azure Traffic Manager checks the user's DNS record to determine the nearest datacenter where
Power BI is deployed, and responds to the DNS with the IP address of the WFE cluster to which the user
should be sent.
3. WFE then redirects the user to Microsoft Online Services login page.

4. Once the user is authenticated, the login page redirects the user to the previously determined nearest Power
BI service WFE cluster.
5. The browser submits a cookie that was obtained from the successful login to Microsoft Online Services,
which is inspected by the ASP.NET service inside the WFE cluster.
6. The WFE cluster checks with the Azure Active Directory (AAD ) service to authenticate the user's Power
BI service subscription, and to obtain an AAD security token. When AAD returns successful authentication
of the user and returns an AAD security token, the WFE cluster consults the Power BI** Global Service,**
which maintains a list of tenants and their Power BI Back-End cluster locations, and determines which Power
BI service cluster contains the user's tenant. The WFE cluster then directs the user to the Power BI cluster
where its tenant resides, and returns a collection of items to the user's browser:
The AAD security token
Session information
The web address of the Back-End cluster the user can communicate and interact with
7. The user's browser then contacts the specified Azure CDN, or for some of the files the WFE, to download
the collection of specified common files necessary to enable the browser's interaction with the Power BI
service. The browser page then includes the AAD token, session information, the location of the associated
Back-End cluster, and the collection of files downloaded from the Azure CDN and WFE cluster, for the
duration of the Power BI service browser session.

Once those items are complete, the browser initiates contact with the specified Back-End cluster and the user's
interaction with the Power BI service commences. From that point forward, all calls to the Power BI service are
with the specified Back-End cluster, and all calls include the user's AAD token. The AAD token has a timeout of one
hour; the WFE refreshes the token periodically if a user's session remains open, in order to preserve access.

Data Storage and Movement

In the Power BI service, data is either at rest (data available to a Power BI user that is not currently being acted
upon), or it is in process (for example: queries being run, data connections and models being acted upon, data
and/or models being uploaded into the Power BI service, and other actions that users or the Power BI service may
take on data that is actively being accessed or updated). Data that is in process is referred to as data in process.
Data at rest in Power BI is encrypted. Data that is in transit, which means data being sent or received by the Power
BI service, is also encrypted.
The Power BI service also manages data differently based on whether the data is accessed with a DirectQuery, or
import. So there are two categories of user data for Power BI: data that is accessed by DirectQuery, and data which
is not accessed by DirectQuery.
A DirectQuery is a query for which a Power BI user's query has been translated from Microsoft's Data Analysis
Expressions (DAX) language – which is the language used by Power BI and other Microsoft products to create
queries – in the data source's native data language (such as T-SQL, or other native database languages). The data
associated with a DirectQuery is stored by reference only, which means source data is not stored in Power BI when
the DirectQuery is not active (except for visualization data used to display dashboards and reports, as described in
the Data in process (data movement) section, below ). Rather, references to DirectQuery data are stored which
allow access to that data when the DirectQuery is run. A DirectQuery contains all the necessary information to
execute the query, including the connection string and the credentials used to access the data sources, which allow
the DirectQuery to connect to the included data sources for automatic refresh. With a DirectQuery, underlying data
model information is incorporated into the DirectQuery.
A query for an import dataset consist of a collection of DAX queries that are not directly translated to the native
language of any underlying data source. Import queries do not include credentials for the underlying data, and the
underlying data is loaded into the Power BI service unless it is on-premises data accessed through a Power BI
Gateway, in which case the query only stores references to on-premises data.
The following table describes Power BI data based on the type of query being used. An X indicates the presence of
Power BI data when using the associated query type.

IMPORT DIRECTQUERY LIVE CONNECT

Schema X X

Row data X

Visuals data caching X X X

The distinction between a DirectQuery and other queries determines how the Power BI service handles the data at
rest, and whether the query itself is encrypted. The following sections describe data at rest and in movement, and
explain the encryption, location, and process for handling data.
Data at rest
When data is at rest, the Power BI service stores datasets, reports, and dashboard tiles in the manner described in
the following subsections. As mentioned earlier, data at rest in Power BI is encrypted. ETL stands for Extract,
Transform and Load in the following sections.
Encryption Keys
The encryption keys to Azure Blob keys are stored, encrypted, in Azure Key Vault.
The encryption keys for Azure SQL Database TDE technology is managed by Azure SQL itself.
The encryption key for Data Movement service and on-premises data gateway are stored:
In the on-premises data gateway on customer's infrastructure – for on-premises data sources
In the Data Movement Role – for cloud-based data sources
The Content Encryption Key (CEK) used to encrypt the Windows Azure Blob Storage is a randomly generated 256-
bit key. The algorithm that the CEK uses to encrypt the content is AES_CBC_256.
The Key Encryption Key (KEK) that is used to then encrypt the CEK is a pre-defined 256-bit key. The algorithm by
KEK to encrypt the CEK is A256KW.
Gateway encryption keys based on the recovery key never leave an on-premises infrastructure. Power BI cannot
access the encrypted on-premises credentials values, and cannot intercept those credentials; web clients encrypt
the credential with a public key that's associated with the specific gateway with which it is communicating.
For cloud-based data sources, the Data Movement Role encrypts encryption keys using Always Encrypted
methods. You can learn more about the Always Encrypted database feature.
Datasets
1. Metadata (tables, columns, measures, calculations, connection strings, etc.)
a. For Analysis Services on-premises nothing is stored in the service except for a reference to that database
stored encrypted in Azure SQL.
 b. All other metadata for ETL, DirectQuery, and Push Data is encrypted and stored in Azure Blob storage.
2. Credentials to the original data sources
a. Analysis Services on-premises – No credentials are needed and, therefore, no credentials are stored.
b. DirectQuery – This depends whether the model is created in the service directly in which case it is stored
in the connection string and encrypted in Azure Blob, or if the model is imported from Power BI Desktop in
which case the credentials are stored encrypted in Data Movement's Azure SQL Database. The encryption
key is stored on the machine running the Gateway on customer's infrastructure.
c. Pushed data – not applicable
d. ETL
For Salesforce or OneDrive – the refresh tokens are stored encrypted in the Azure SQL Database of
the Power BI service.
Otherwise:
If the dataset is set for refresh, the credentials are stored encrypted in Data Movement's Azure
SQL Database. The encryption key is stored on the machine running the Gateway on customer's
infrastructure.
If the dataset is not set for refresh, there are no credentials stored for the data sources
3. Data
a. Analysis Services on-premises, and DirectQuery – nothing is stored in the Power BI Service.
b. ETL – encrypted in Azure Blob storage, but all data currently in Azure Blob storage of the Power BI
service uses Azure Storage Service Encryption (SSE ), also known as server-side encryption. Multi-geo uses
SSE as well.
c. Push data v1 – stored encrypted in Azure Blob storage, but all data currently in Azure Blob storage in the
Power BI service uses Azure Storage Service Encryption (SSE ), also known as server-side encryption. Multi-
geo uses SSE as well.
d. Push data v2 – stored encrypted in Azure SQL.
Power BI uses the client-side encryption approach, using cipher block chaining (CBC ) mode with advanced
encryption standard (AES ), to encrypt its Azure Blob storage. You can learn more about client-side encryption.
Power BI provides data integrity monitoring in the following ways:
For data at rest in Azure SQL, Power BI uses dbcc, TDE, and constant page checksum as part of the native
offerings of SQL.
For data at rest in Azure Blob storage, Power BI uses client-side encryption and HTTPS to transfer data into
storage which includes integrity checks during the retrieval of the data. You can learn more about Azure
Blob storage security.
Reports
1. Metadata (report definition)
a. Reports can either be Excel for Office 365 reports, or Power BI reports. The following applies for metadata
based on the type of report:

a. Excel Report metadata is stored encrypted in SQL Azure. Metadata is also stored in Office 365.

b. Power BI reports are stored encrypted in Azure SQL database.

2. Static data
 Static data includes artifacts such as background images and custom visuals.
a. For reports created with Excel for Office 365, nothing is stored.
b. For Power BI reports, the static data is stored and is encrypted in Azure Blob storage.
3. Caches a. For reports created with Excel for Office 365, nothing is cached.
b. For Power BI reports, data for the visuals shown are cached encrypted in Azure SQL Database.
4. Original Power BI Desktop (.pbix) or Excel (.xlsx) files published to Power BI
Sometimes a copy or a shadow copy of the .xlsx or .pbix files are stored in Power BI's Azure Blob storage,
and when that occurs, the data is encrypted. All such reports stored in the Power BI service, in Azure Blob
storage, use Azure Storage Service Encryption (SSE ), also known as server-side encryption. Multi-geo uses
SSE as well.
Dashboards and Dashboard Tiles
1. Caches – The data needed by the visuals on the dashboard is usually cached and stored encrypted in Azure
SQL Database. Other tiles such as pinned visuals from Excel or SQL Server Reporting Services (SSRS ) are
stored in Azure Blob as images, and are also encrypted.
2. Static data – that includes artifacts such as background images and custom visuals that are stored,
encrypted, in Azure Blob storage.
Regardless of the encryption method used, Microsoft manages the key encryption on customers' behalf, in either a
secret store or in Azure Key Vault.
Data Transiently Stored on Non-Volatile Devices
The following describes data that is transiently stored on non-volatile devices.
Datasets
1. Metadata (tables, columns, measures, calculations, connection strings, etc.)
2. Some schema-related artifacts can be stored on the disk of the compute nodes for a limited period of time.
Some artifacts can also be stored in Azure REDIS Cache unencrypted for a limited period of time.
3. Credentials to the original data sources
a. Analysis Services on-premises – nothing is stored
b. DirectQuery – This depends whether the model is created in the service directly in which case it is stored
in the connection string, in encrypted format with the encryption key stored in clear text in the same place
(alongside the encrypted information); or if the model is imported from Power BI Desktop in which case the
credentials are not stored on non-volatile devices.
c. Pushed data – none (not applicable)
d. ETL – none (nothing stored on the compute node nor different than explained in the Data at Rest section,
above)
4. Data
Some data artifacts can be stored on the disk of the compute nodes for a limited period of time.
Data in process
Data is in process when it is actively being used or accessed by a user. For example, data is in process when a user
accesses a dataset, revises or modifies a dashboard or report, when refresh occurs, or other data access activities
that may occur. When any of those events occur and put data in process, the Data Role in the Power BI service
creates an in-memory Analysis Services (AS ) database and the dataset is loaded into that in-memory Analysis
Services database. Whether the dataset is based on a DirectQuery or not, data loaded in the AS database is
unencrypted to allow for access by the Data Role, and held in memory for further access until the Power BI
service no longer needs the dataset. For customers with a Power BI Premium subscription, Power BI creates an in-
memory Analysis Services (AS ) database in the customer's separately provisioned collection of Power BI virtual
machines.
Once data is acted upon, which includes initially loading data into Power BI, the Power BI service may cache the
visualization data in an encrypted Azure SQL Database, regardless of whether the dataset is based on a
DirectQuery.
To monitor data integrity for data in process, Power BI uses HTTPS, TCP/IP and TLS to ensure data is encrypted
and maintains integrity during the transport.

User Authentication to Data Sources

With each data source, a user establishes a connection based on his or her login, and accesses the data with those
credentials. Users can then create queries, dashboards, and reports based on the underlying data.
When a user shares queries, dashboards, reports, or any visualization, access to that data and those visualizations
is dependent on whether the underlying data sources support Role Level Security (RLS ).
If an underlying data source is capable of Power BI's** Role Level Security (RLS )**, the Power BI service will apply
that role level security, and users who do not have sufficient credentials to access the underlying data (which could
be a query used in a dashboard, report, or other data artifact) will not see data for which the user does not have
sufficient privileges. If a user's access to the underlying data is different from the user who created the dashboard
or report, the visualizations and other artifacts will only show data based on the level of access that user has to the
data.
If a data source does not apply RLS, then the Power BI login credentials are applied to the underlying data source,
or if other credentials are supplied during the connection, those supplied credentials are applied. When a user
loads data into the Power BI service from non-RLS data sources, the data is stored in Power BI as described in the
Data Storage and Movement section found in this document. For non-RLS data sources, when data is shared
with other users (such as through a dashboard or report) or a refresh of the data occurs, the original credentials are
used to access or display the data.

For a quick example to contrast RLS and non-RLS data sources, imagine Sam creates a report and a dashboard,
then shares them with Abby and Ralph. If the data sources used in the report and dashboard are from data sources
that do not support RLS, both Abby and Ralph will be able to see the data that Sam included in the dashboard
(which was uploaded into the Power BI service) and both Abby and Ralph can then interact with the data. In
contrast, if Sam creates a report and dashboard from data sources that do support RLS, then shares it with Abby
and Ralph, when Abby attempts to view the dashboard the following occurs:
1. Since the dashboard is from an RLS data source, the dashboard visualizations will briefly show a "loading"
message while the Power BI service queries the data source to retrieve the current dataset specified in the
connection string associated with the dashboard's underlying query.
2. The data is accessed and retrieved based on Abby's credentials and role, and only data for which Abby has
sufficient authorization is loaded into the dashboard and report.
3. The visualizations in the dashboard and report are displayed based on Abby's role level.
If Ralph were to access the shared dashboard or report, the same sequence occurs based on his role level.

Power BI and ExpressRoute

With Power BI and ExpressRoute, you can create a private network connection from your organization to Power BI
(or using an ISP's colocation facility), bypassing the Internet to better secure your sensitive Power BI data and
connections.
ExpressRoute is an Azure service that lets you create private connections between Azure datacenters (where Power
BI resides) and your on-premises infrastructure, or create private connections between Azure datacenters and your
colocation environment. For more information, please refer to the Power BI and ExpressRoute article.

Power BI Mobile
Power BI Mobile is a collection of apps designed for the three primary mobile platforms: Android, iOS, and
Windows Mobile. Security considerations for Power BI Mobile apps falls into two categories:
Device communication
The application and data on the device
For device communication, all Power BI Mobile applications communicate with the Power BI service, and use
the same connection and authentication sequences used by browsers, which are described in detail earlier in this
whitepaper. The iOS and Android Power BI mobile applications bring up a browser session within the application
itself, and the Windows mobile app brings up a broker to establish the communication channel with Power BI.
The following table lists support of certificate-based authentication (CBA) for Power BI Mobile based on mobile
device platform:

CBA SUPPORT IOS ANDROID WINDOWS

Power BI (sign in to service) supported supported Not supported

SSRS ADFS (connect to Not supported Supported Not supported

SSRS server)

Power BI Mobile apps actively communicate with the Power BI service. Telemetry is used to gather mobile app
usage statistics and similar data, which is transmitted to services that are used to monitor usage and activity; no
personal data is sent with telemetry data.
The Power BI application on the device stores data on the device that facilitates use of the app:
Azure Active Directory and refresh tokens are stored in a secure mechanism on the device, using industry-
standard security measures.
Data is cached in storage on the device, which is not directly encrypted by the application itself
Settings are also stored on the device unencrypted, but no actual user data is stored.
The data cache from Power BI Mobile remains on the device for two weeks, or until: the app is removed; the user
signs out of Power BI Mobile; or the user fails to sign in (such as a token expiration event, or password change).
The data cache includes dashboards and reports previously accessed from the Power BI Mobile app.
Power BI Mobile applications do not look at folders on the device.
All three platforms for which Power BI Mobile is available support Microsoft Intune, a software service that
provides mobile device and application management. With Intune enabled and configured, data on the mobile
device is encrypted, and the Power BI application itself cannot be installed on an SD card. You can learn more
about Microsoft Intune.

Power BI Security Questions and Answers

The following questions are common security questions and answers for Power BI. These are organized based on
when they were added to this whitepaper, to facilitate your ability to quickly find new questions and answers when
this paper is updated. The newest questions are added to the end of this list.
How do users connect to, and gain access to data sources while using Power BI?
Power BI credentials and domain credentials: Users sign in to Power BI using an email address; when a
user attempts to connect to a data resource, Power BI passes the Power BI login email address as
credentials. For domain-connected resources (either on-premises or cloud-based), the login email is
matched with a User Principal Name (UPN ) by the directory service to determine whether sufficient
credentials exist to allow access. For organizations that use work-based email addresses to sign in to Power
BI (the same email they use to login to work resources, such as [email protected]_), the mapping can
occur seamlessly; for organizations that did not use work-based email addresses (such as
[email protected]_), directory mapping must be established in order to allow access to on-
premises resources with Power BI login credentials.
SQL Server Analysis Services and Power BI: For organizations that use on-premises SQL Server
Analysis Services, Power BI offers the Power BI on-premises data gateway (which is a Gateway, as
referenced in previous sections). The Power BI on-premises data gateway can enforce role-level security on
data sources (RLS ). For more information on RLS, see User Authentication to Data Sources earlier in
this document. You can also read an in-depth article about Power BI Gateway.
In addition, organizations can use Kerberos for single sign-on (SSO ) and seamlessly connect from Power
BI to on-premises data sources such as SQL Server, SAP HANA, and Teradata. For more information, and
the specific configuration requirements, see Use Kerberos for SSO from Power BI to on-premises data
sources.
Non-domain connections: For data connections that are not domain-joined and not capable of Role Level
Security (RLS ), the user must provide credentials during the connection sequence, which Power BI then
passes to the data source to establish the connection. If permissions are sufficient, data is loaded from the
data source into the Power BI service.
How is data transferred to Power BI?
All data requested and transmitted by Power BI is encrypted in transit using HTTPS to connect from the data
source to the Power BI service. A secure connection is established with the data provider, and only once that
connection is established will data traverse the network.
How does Power BI cache report, dashboard, or model data, and is it secure?
When a data source is accessed, the Power BI service follows the process outlined in the Data Storage and
Movement section earlier in this document.
Do clients cache web page data locally?
When browser clients access Power BI, the Power BI web servers set the Cache-Control directive to no -store.
The no -store directive instructs browsers not to cache the web page being viewed by the user, and not to store
the web page in the client's cache folder.
What about role-based security, sharing reports or dashboards, and data connections? How does that
work in terms of data access, dashboard viewing, report access or refresh?
For non-Role Level Security (RLS ) enabled data sources, if a dashboard, report, or data model is shared
 with other users through Power BI, the data is then available for users with whom it is shared to view and
interact with. Power BI does not re-authenticate users against the original source of the data; once data is
uploaded into Power BI, the user who authenticated against the source data is responsible for managing
which other users and groups can view the data.
When data connections are made to an RLS -capable data source, such as an Analysis Services data source,
only dashboard data is cached in Power BI. Each time a report or dataset is viewed or accessed in Power BI
that uses data from the RLS -capable data source, the Power BI service accesses the data source to get data
based on the user's credentials, and if sufficient permissions exist, the data is loaded into the report or data
model for that user. If authentication fails, the user will see an error.
For more information, see the User Authentication to Data Sources section earlier in this document.
Our users connect to the same data sources all the time, some of which require credentials that differ
from their domain credentials. How can they avoid having to input these credentials each time they
make a data connection?
Power BI offers the Power BI Personal Gateway, which is a feature that lets users create credentials for multiple
different data sources, then automatically use those credentials when subsequently accessing each of those data
sources. For more information, see Power BI Personal Gateway.
How do Power BI Groups work?
Power BI Groups allow users to quickly and easily collaborate on the creation of dashboards, reports, and
data models within established teams. For example, if you have a Power BI Group that includes everyone in
your immediate team, you can easily collaborate with everyone on your team by selecting the Group from
within Power BI. Power BI Groups are equivalent to Office 365 Universal Groups (which you can learn
about, create, and manage), and use the same authentication mechanisms used in Azure Active Directory to
secure data. You can create groups in Power BI or create a Universal Group in Microsoft 365 admin center;
either has the same result for group creation in Power BI.
Note that data shared with Power BI Groups follows the same security consideration as any shared data in
Power BI. For non-RLS data sources Power BI does not re-authenticate users against the original source of
data, and once data is uploaded into Power BI, the user who authenticated against the source data is
responsible for managing which other users and groups can view the data. For more information, see the
User Authentication to Data Sources section earlier in this document.
You can get more information about Groups in Power BI.
Which ports are used by on-premises data gateway and personal gateway? Are there any domain names
that need to be allowed for connectivity purposes?
The detailed answer to this question is available at the following link: Power BI Gateway
When working with the on-premises data gateway, how are recovery keys used and where are they
stored? What about secure credential management?
During gateway installation and configuration, the administrator types in a gateway Recovery Key. That
Recovery Key is used to generate two sets of much stronger keys:
An RSA asymmetric key
An AES symmetric key
Those generated keys (RSA and AES ) are stored in a file located on the local machine. That file is also
encrypted. The contents of the file can only be decrypted by that particular Windows machine, and only by
that particular gateway service account.
When a user enters data source credentials in the Power BI service UI, the credentials are encrypted with
 the public key in the browser. The gateway re-encrypts the (already encrypted) credentials with an AES
symmetric key before the data is stored in Power BI. With this process, the Power BI service never has
access to the unencrypted data.
Which communication protocols are used by the on-premises data gateway, and how are they secured?
The gateway supports the following two communications protocols:
AMQP 1.0 – TCP + TLS: This protocol requires ports 443, 5671-5672, and 9350-9354 to be open
for outgoing communication. This protocol is preferred, since it has lower communication overhead.
HTTPS – WebSockets over HTTPS + TLS: This protocol uses port 443 only. The WebSocket is
initiated by a single HTTP CONNECT message. Once the channel is established, the communication
is essentially TCP+TLS. You can force the gateway to use this protocol by modifying a setting
described in the On-Premises Gateway article.
What is the role of Azure CDN in Power BI?
As mentioned previously, Power BI uses the Azure Content Delivery Network (CDN ) to efficiently
distribute the necessary static content and files to users based on geographical locale. To go into further
detail, the Power BI service uses multiple CDNs to efficiently distribute necessary static content and files to
users through the public Internet. These static files include product downloads (such as Power BI Desktop,
the on-premises data gateway, or Power BI apps from various independent service providers), browser
configuration files used to initiate and establish any subsequent connections with the Power BI service, as
well as the initial secure Power BI login page.
Based on information provided during an initial connection to the Power BI service, a user's browser
contacts the specified Azure CDN (or for some files, the WFE ) to download the collection of specified
common files necessary to enable the browser's interaction with the Power BI service. The browser page
then includes the AAD token, session information, the location of the associated Back-End cluster, and the
collection of files downloaded from the Azure CDN and WFE cluster, for the duration of the Power BI
service browser session.
For Custom Visuals, does Microsoft perform any security or privacy assessment of the custom visual
code prior to publishing items to the Gallery?
No. It is the customer's responsibility to review and determine whether custom visual code should be relied
upon. All custom visual code is operated in a sandbox environment, so that any errant code in a custom visual
does not adversely affect the rest of the Power BI service.
Are there other Power BI visuals that send information outside the customer network?
Yes. Bing Maps and ESRI visuals transmit data out of the Power BI service for visuals that use those services.
For more information, and detailed descriptions of out-of-Power-BI tenant traffic, see Power BI and
ExpressRoute.
What about data sovereignty? Can we provision tenants in data centers located in specific geographies,
to ensure data doesn't leave the country borders?
Some customers in certain geographies have an option to create a tenant in a national cloud, where data
storage and processing is kept separate from all other datacenters. National clouds have a slightly different
type of security, since a separate data trustee operates the national cloud Power BI service on behalf of
Microsoft.
Alternatively customers can also set up a tenant in a specific region, however, such tenants do not have a
separate data trustee from Microsoft. Pricing for national clouds is different from the generally available
commercial Power BI service. For more information about Power BI service availability for national clouds,
see Power BI national clouds.
How does Microsoft treat connections for customers who have Power BI Premium subscriptions? Are
those connections different than those established for the non-Premium Power BI service?
The connections established for customers with Power BI Premium subscriptions implement an Azure
Business-to-Business (B2B ) authorization process, using Azure Active Directory (AD ) to enable access control
and authorization. Power BI handles connections from Power BI Premium subscribers to Power BI Premium
resources just as it would any other Azure AD user.

Conclusion
The Power BI service architecture is based on two clusters – the Web Front End (WFE ) cluster and the Back-End
cluster. The WFE cluster is responsible for initial connection and authentication to the Power BI service, and once
authenticated, the Back End handles all subsequent user interactions. Power BI uses Azure Active Directory (AAD )
to store and manage user identities, and manages the storage of data and metadata using Azure Blob and Azure
SQL Database, respectively.
Data storage and data processing in Power BI differs based on whether data is accessed using a DirectQuery, and
is also dependent on whether data sources are in the cloud or on-premises. Power BI is also capable of enforcing
Role Level Security (RLS ) and interacts with Gateways that provide access to on-premises data.

Feedback and Suggestions

We appreciate your feedback. We're interested in hearing any suggestions you have for improvement, additions, or
clarifications to this whitepaper, or other content related to Power BI. Send your suggestions to
[email protected].

Additional Resources
For more information on Power BI, see the following resources.
Groups in Power BI
Getting Started with Power BI Desktop
Power BI Gateway
Power BI REST API - Overview
Power BI API reference
On-premises data gateway
Power BI and ExpressRoute
Power BI National Clouds
Power BI Premium
Use Kerberos for SSO from Power BI to on-premises data sources
 Deploying and Managing Power BI Premium
Capacities
3/22/2019 • 73 minutes to read • Edit Online

Summary: Power BI Premium provides more consistent performance, support for large data volumes, and the
flexibility of a unified self-service and enterprise BI platform for everyone in your organization. This level 300
technical whitepaper has been written specifically for Power BI administrators, and content authors and publishers.
It aims to help them understand the potential of Power BI Premium, and to explain how to design, deploy, monitor
and troubleshoot scalable solutions.
Author: Peter Myers (Data Platform MVP, and independent BI expert with Bitwise Solutions)
Technical Reviewers: Adam Saxton, Akshai Mirchandani, Bhavik Merchant, David Magar, Josh Caplan, Michael
Blythe, Nimrod Shalit, Olivier Matrat, Swati Gupta
Applies to: Power BI service, Power BI Premium and Azure Power BI Embedded capacities

NOTE
You can save or print this whitepaper by selecting Print from your browser, then selecting Save as PDF.

Introducing Power BI
Power BI is a business analytics service designed to deliver insights that enable fast, informed decisions. Since its
release in 2015 it has quickly become a popular service used to deliver solutions for the smallest of organizations
to the largest of enterprises.
It is made available in two ways: As a cloud service and as an on-premises reporting solution named Power BI
Report Server. [1]
Power BI as a cloud service is Software-as-a-Service (SaaS ) [ 2]. It represents a set of services and applications that
enable organizations to develop, deploy, manage, share solutions to monitor their business.
It is not the intention of this whitepaper to provide a comprehensive description of the Power BI service. Instead, it
focuses on topics relevant to the subject of Power BI Premium. For general information about Power BI, refer to
the comprehensive Power BI Documentation. For a more detailed explanation of the Power BI service with a focus
on achieving well-performing enterprise deployments, refer to the comprehensive Planning a Power BI Enterprise
Deployment whitepaper.
Within the context of this whitepaper's subject, this section introduces and describes capacities, Power BI content
types, model storage modes and licensing. An understanding of these topics is essential to successfully deploying
and managing Power BI Premium.
Capacities
Capacities are a core Power BI concept representing a set of resources (storage, processor and memory) used to
host and deliver Power BI content. Capacities are either shared or dedicated. A Shared Capacity is shared with
other Microsoft customers, while a Dedicated Capacity is fully committed to a single customer. Dedicated
capacities are introduced in the Premium Capacities topic.
In shared capacity, workloads run on computational resources shared with other customers. As the capacity must
share resources, limitations are imposed to ensure "fair play", such as the maximum model size (1 GB ) and
maximum daily refresh frequency (eight times per day).
Workspaces
Power BI workspaces reside within capacities and they represent security, collaboration and deployment
containers. Each Power BI user has a personal workspace known as My Workspace. Additional workspaces can
be created to enable collaboration and deployment, and these are known as App Workspaces. By default,
workspaces - including personal workspaces - are created in the shared capacity.
Power BI Content Types
To introduce Power BI Premium topics, it is important to start with a thorough discussion of Power BI architecture
including fundamental content types.
All Power BI content is stored and managed within workspaces which are containers for Power BI content. Each
Power BI user has their own personal workspace, but the general best practice is to create app workspaces. App
workspaces enable co-ownership of content and the ability to collaborate on content. They also provide the ability
to stage and distribute content to wide audiences as apps.
The following Power BI content is stored in workspaces:
Dataflows
Datasets
Workbooks
Reports
Dashboards
Dataflows
Power BI dataflows help organizations to unify data from disparate sources. They can be considered as data
prepared and staged for use in models, however they cannot be used directly as a source for reporting. They
leverage the extensive collection of Microsoft data connectors, enabling the ingestion of data from on-premises
and cloud-based data sources.
Dataflows can only be created and managed in app workspaces, and they are stored as entities in the Common
Data Model (CDM ) in Azure Data Lake Storage Gen2. Typically, they are scheduled to refresh on a recurring basis
to store up-to-date data.
For further information, refer to the Self-service data prep in Power BI (Preview ) document.
Datasets
Power BI datasets represent a source of data ready for reporting and visualization. There are many types of
datasets, created by:
Connecting to an existing data model which is not hosted in a Power BI capacity
Uploading a Power BI Desktop file that contains a model
Uploading an Excel workbook (containing one or more Excel tables and/or a workbook data model) or
uploading a Comma-Separated Value (CSV ) file
Using the Power BI service to create a push, streaming or hybrid streaming dataset
Except for streaming datasets [3], the dataset represents a data model which leverages the mature modeling
technologies of Analysis Services.
Note that in documentation, sometimes the terminologies datasets and models are interchangeable. Generally,
from a Power BI service perspective it is referred to as a dataset , and from a development perspective it is
referred to as a model. In the context of this whitepaper they mean much the same thing.
Ex t e r n a l l y - H o st e d M o d e l s

Connecting to an externally-hosted model involves installing the On-Premises Data Gateway to connect to SQL
Server Analysis Services, whether it is on-premises or VM -hosted Infrastructure-as-a-Service (IaaS ). Azure
Analysis Services does not require a gateway. This scenario often makes sense when existing model investments
exist, typically forming part of the Enterprise Data Warehouse (EDW ). It allows Power BI to perform a Live
Connection (LC ) to Analysis Services and does so by enforcing data permissions by using the identity of the
Power BI report user. For SQL Server Analysis Services, both multidimensional models (cubes) and tabular
models are supported. As shown in the following image, a Live Connection dataset passes queries to externally
hosted models.

P o w e r B I D e sk t o p - D e v e l o p e d M o d e l s

Power BI Desktop - a client application intended for Power BI development - can be used to develop a model
which is effectively an Analysis Services tabular model. Models can be developed by importing data from
dataflows, which can then be integrated with other data sources. While the specifics on how modeling can be
achieved is outside the scope of this whitepaper, it is important to understand that there are three different types -
or modes - of models that can be developed by using Power BI Desktop. These modes determine whether data is
imported into the model, or whether it remains in the data source. The three modes are: Import, DirectQuery, and
Composite. A complete discussion of each mode will be covered in the Model Storage Modes topic.
Externally-hosted models and models developed in Power BI desktop can enforce Row -Level Security (RLS ) to
limit the data that can be retrieved for a certain user. For example, users assigned to the Salespeople security
group can only view report data for the sales region(s) to which they are assigned. RLS roles can be dynamic or
static. Dynamic roles filter by the report user, while static roles apply the same filters for all users assigned to the
role.
Ex c e l W o r k b o o k M o d e l s

Creating datasets based on Excel workbooks or CSV files will result in the automatic creation of a model. Excel
tables and CSV data will be imported to create model tables, while an Excel workbook data model will be
transposed to create a Power BI model. In all cases, file data is imported into a model.
Distinctions, then, can be made about Power BI datasets that represent models:
They are either hosted in the Power BI service, or are externally hosted by Analysis Services
They can store imported data, or they can issue passthrough query requests to underlying data sources, or a
mix of both
Here is a summary of important facts about Power BI datasets that represent models:
SQL Server Analysis Services hosted models require a gateway to perform LC queries
Power BI-hosted models that import data
Must be fully loaded into memory so that they can be queried
Require refresh to keep data current, and must involve gateways when source data is not accessible
directly over the Internet
Power BI-hosted models that use DirectQuery (DQ ) storage mode require connectivity to the source data.
When the model is queried, Power BI issues queries to the source data to retrieve current data. This mode must
involve gateways when source data is not accessible directly over the Internet.
 Models may enforce RLS rules, enforcing filters to limit data access to certain users
To successfully deploy and manage Power BI Premium, it is important to understand where models are hosted,
their storage mode, any dependencies on gateways, size of imported data, and refresh type and frequency. These
can all have a significant impact on the Power BI Premium resources. In addition, the model design itself including
its data preparation queries and calculations can add to the mix of considerations.
It is also important to understand that Power BI-hosted import models can refresh according to schedule or be
triggered on-demand by a user in the Power BI service.
Designing optimized models is discussed later in this technical paper in the Optimizing Models topic.
Workbooks
Power BI workbooks are a Power BI content type [4]. They are Excel workbooks that have been uploaded to the
Power BI service, and should not be confused with uploaded Excel workbooks that create datasets (models). The
workbook content type represents a connection to a workbook, which could either be uploaded to the Power BI
service or remain in cloud storage on OneDrive or SharePoint Online.
It is important to understand that this content type is not available as a data source for Power BI data
visualizations. Instead, it can be opened as a workbook in the Power BI service by using Excel Online. The main
intention of this content type is to allow legacy Excel workbook reports to be accessible from within the Power BI
service, and to allow its data visualizations to be pinned to Power BI dashboards.
For further information, refer to the Get data from Excel workbook files document.
Reports
There are two types of reports: Power BI reports and paginated reports.
Power BI reports provide an interactive data visualization experiences which connects to only a single dataset.
Reports are often designed to encourage user participation allowing them to interact with an extraordinary array
of capabilities, including filtering, slicing, cross filtering and highlighting, drilling up, drilling down, drilling through,
Q&A natural language questioning, focusing, page navigation, spotlighting, viewing bookmarks, and more.
In the context of this whitepaper, it is important to understand how the Power BI architecture, Power BI report
design and user interactions can all impact on the Power BI service resources:
To load and interact with reports based on import models, the model must be fully loaded into memory
(whether hosted in the Power BI service or hosted externally)
Each report visual issues a query to retrieve data by querying the model
Generally, filter and slicer interactions involve querying the model. For example, changing a slicer selection will
- by default - require reloading each visual on the page [5]
Power BI reports do not guarantee displaying current data, and may require the user to refresh the report to
reload the report page and its visuals
Users can engage with the Q&A natural language feature to ask questions, providing the Power BI report
design permits it and the dataset represents a Power BI-hosted data import model or a LC dataset configured
to enable Q&A
Paginated reports allowing the publication and rendering of SQL Server Reporting Services (SSRS ) reports
(*.rdl format). As their name suggests, paginated reports are commonly used when requirements dictate a need
for printing to a fixed page size, or when there are variable lists of data that must be fully expanded. For example,
an invoice designed for multi-page rendering (rather than scrolling within a visual) and printing.
The two supported report types provide choice for report authors, allowing them to select the type based on
requirements and intended use. Generally, Power BI reports are ideal for interactive experiences allowing the user
to explore and discover insights from data, while paginated reports are better suited to parameter-driven page
layouts.
Regardless of report type, achieving responsive report load and data updates (when filters or parameters are
changed) is imperative to delivering a reliable and well-performing user experience.
Dashboards
Power BI dashboards are intended to deliver monitoring experiences and are conceptually very different from
Power BI reports. Dashboards are designed for display on a single pane of glass to express values and data
visualizations in tiles. Generally, dashboards offer fewer interaction experiences than Power BI reports, with some
dashboard designs expecting no interaction. For example, an unattended dashboard presented on a non-touch
screen in a server room. Another significant difference is that dashboards may present tiles that source data from
multiple datasets, while a Power BI report can only ever be based on a single dataset.
It is important to understand that a dashboard is designed to load quickly and to express the most current data
(known to the Power BI service) at all times. It achieves this by caching tile query results, and it does this for each
dashboard. In fact, it must do this for each user that has access to a dashboard that is based on models that
enforce dynamic RLS.
The Power BI service automatically updates dashboard query caches immediately after Power BI-hosted import
models are refreshed. In the case of LC and DQ models, the dataset owner has a degree of control over how often
the Power BI service updates the cache, which can be configured as frequently as every 15 minutes, or as
infrequently as once a week. Note that LC query cache updates will first query model metadata to determine
whether a model refresh has taken place since the last cache update, and it will not proceed to update the cache
when a refresh has not since occurred. This check is not possible for DQ models, and so cache updates will happen
whether the source data has changed or not.
Dashboard query cache updates based on DQ and LC models can significantly impact on both Power BI service
resources and external data sources. Consider a dashboard with 20 tiles, all based on an Azure Analysis Services
model that enforces dynamic RLS and that is refreshed every hour, and that this dashboard is shared with 100
users. If the dataset is configured to refresh every hour, this would result in at least 2000 (20 x 100) LC queries.
This could place an enormous load on the Power BI service and external data sources, and it could also exceed
limits imposed on available resources. Capacity resources and limits are described in the Capacity Nodes topic.
Users can interact with a dashboard in various ways, which require Power BI service resources. Specifically, they
can:
Trigger a refresh of dashboards tiles, which can result in an on-demand refresh of all related Power BI-hosted
data import models
Engage with the Q&A natural language feature to ask questions (providing the dashboard design permits it
and the dataset is a Power BI-hosted data import model or a LC dataset configured to enable Q&A)
Use the Quick Insights feature to have Power BI discover insights from an underlying dataset, and respond
with visuals that display and describe them (providing that the tile is based on a dataset that is Power BI-hosted
data import model)
Configure alerts on dashboard tiles, requiring the Power BI service to compare thresholds to tile values -
possibly as frequently as hourly - and to notify users when thresholds are exceeded (providing that the tile
displays a single numeric value and is based on a dataset that is Power BI-hosted data import model)
Model Storage Modes
Recall that Power BI Desktop allows developing a model in one of three modes. It is important to understand the
rationale for each data model storage mode and possible impacts on Power BI service resources. This section
introduces all three modes. These will be discussed in further detail later in this whitepaper in the Optimizing
Models topic.
Import Mode
Import mode is the most common mode used to develop models because of the extremely fast performance
associated with in-memory querying, the design flexibility available to modelers, and support for specific Power BI
service capabilities (Q&A, Quick Insights, etc.). It is the default mode when creating a new Power BI Desktop
solution.
It is important to understand that imported data is always stored to disk and must be fully loaded into memory to
be queried or refreshed. Once in memory, import models achieve blazingly fast query results. It is also important
to understand that there is no concept of an import model being partially loaded into memory.
When refreshed, data is compressed and optimized and then stored to disk by the VertiPaq storage engine. When
loaded from disk into memory, it is possible to see 10x compression, and so it is reasonable to expect that 10 GB
of source data can compress to about 1 GB in size. Storage size on disk can achieve a 20% reduction on top this.
[6 ]
Design flexibility can be achieved in three ways. Data modelers can:
Integrate data by caching data from multiple data sources - regardless of data source type and format
Leverage the entire set of Power Query Formula Language (informally referred to as M ) functions when
creating data preparation queries
Leverage the entire set of Data Analysis Expressions (DAX) functions when enhancing the model with business
logic, achieved with calculated columns, calculated tables and measures
As shown in the following image, an Import model can integrate data from any number of supported data source
types.

However, while there are compelling advantages associated with import models, there are disadvantages too:
The entire model must be loaded to memory before Power BI can query the model, which can place pressure
on available resources as the number and size of models grow
Model data is only as current as the latest refresh, and so import models need to be refreshed, preferably on a
scheduled basis
A full refresh will remove all data from all tables and reload it from the data source. This can be very expensive
in terms of time and resources for the Power BI service and the data source(s). Power BI does have support for
incremental refresh which can avoid truncating and reloading entire tables, and this is covered in the
Optimizing Power BI-Hosted Models topic.
From a Power BI service resource perspective, import models require:
Sufficient memory to load the model when it is queried or refreshed
 Processing resources and additional memory resources to refresh data
DirectQuery Mode
Models developed in DirectQuery (DQ ) mode do not import data. Instead, they consist only of metadata that
when queried issues native queries to the underlying data source.

There are two main reasons to consider developing a DQ model. The first reason is when data volumes are too
large - even when data reduction methods are applied - to load into a model or practically refresh. The second
reason is when reports and dashboards need to deliver "near real-time" data, beyond what can be achieved within
scheduled refresh limits (48 times a day for a dedicated capacity).
There are several advantages associated with DQ models:
Import model size limits do not apply
Models do not require refresh
Report users will see the latest data when interacting with report filters and slicers, and can refresh the entire
report to retrieve current data
Dashboard tiles, when based on DQ models, can update automatically as frequently as every 15 minutes
However, there are numerous disadvantages and limitations associated with DQ models:
The model must be based on a single supported data source, and therefore any data integration must already
be achieved in the data source. Supported data sources are relational and analytic systems, with support for
many popular data stores [7].
Performance can be slow, potentially negatively impacting on the Power BI service (queries can be very CPU -
intensive) and on the data source (which may not be optimized for analytic queries)
Power Query queries cannot be overly complex, and are limited to M expressions and functions that can be
transposed to native queries understood by the data source
DAX functions are limited to those that can be transposed to native queries understood by the data source, and
there is no support for calculated tables or built-in Time Intelligence capabilities
By default, model queries that require retrieval of more than one million rows will fail
Reports and dashboards with multiple visuals can display inconsistent results, especially when the data source
is volatile
Q&A and Quick Insights are not supported
From a Power BI service resource perspective, DQ models require:
Minimal memory to load the model (metadata only) when it is queried
Sometimes significant processor resources to generate and process queries sent to the data source
For further information, refer to the Use Direct Query in Power BI Desktop document.
Composite Mode
Models developed in Composite mode allow configuring the storing mode for individual model tables. It therefore
supports a mix of import and DQ tables. It also supports calculated tables (defined with DAX) and multiple DQ
data sources.
Table storage mode can be configured as Import, DirectQuery or Dual. A table configured as Dual storage mode is
both Import and DirectQuery, and this allows the Power BI service to determine the most efficient mode to use on
a query by query basis.

Composite models strive to deliver the best of Import and DirectQuery modes. When configured appropriately
they can combine high query performance of in-memory models with the ability to retrieve near real-time data
from data sources.
Data modelers who develop Composite models are likely to configure dimension-type tables in Import or Dual
storage mode and fact-type tables in DirectQuery mode. For example, consider a model with a Product
dimension-type table in Dual mode and a Sales fact-type table in DirectQuery mode. The Product table could be
efficiently and quickly queried from in-memory to render a report slicer. The Sales table could then be queried in
DirectQuery mode joined to the related Product table. The latter query could enable the generation of a single
efficient native query to join Product and Sales tables and filtering by the slicer values.
In general, the advantages and disadvantages, associated with each model mode can be considered to apply to
table storage mode in Composite models.
For further information, refer to the Use composite models in Power BI Desktop document.
Licensing
Power BI has three licenses:
Power BI Free
Power BI Pro
Power BI Premium
The Power BI Free license allows an individual to sign in to the Power BI service and work within their personal
workspace by publishing models and reports. It is important to understand that it is not possible to share Power BI
content by using this license. This license, as its name suggests, is free.
The Power BI Pro license allows an individual to create and collaborate within app workspaces and share and
distribute Power BI content. They can also configure refresh for their datasets to automatically keep data current,
including from on-premises data sources. In addition, they can audit and govern how data is accessed and used.
This license is required to receive shared content from others unless the user is associated with a Power BI
Premium dedicated capacity.
The Power BI Premium license is a tenant-level license, and it is discussed in the Introducing Power BI Premium
section.
For further information about Power BI licensing, refer to the Power BI Pricing page.

Introducing Power BI Premium

Power BI Premium delivers a unified self-service and enterprise BI platform with scale, dependable performance,
and predictable costs. It primarily achieves this by providing dedicated resources to run the Power BI service for
your organization.
In addition, Power BI Premium delivers many enterprise features:
Cost-effective content distribution, enabling the sharing of Power BI content to unlimited Power BI Free users,
including external users
Support for larger dataset sizes [8]
Higher refresh rates of dataflows and datasets (up to 48 times per day)
Incremental refresh of dataflows and datasets
Dataflow linked entities, and parallel execution of transforms
Paginated reports
Power BI Report Server, for on-premises reporting
Ability to embed content in apps on behalf of app users (PaaS )
Many of these features can be leveraged to deliver efficient and scalable enterprise solutions and are covered in
the Optimizing Premium Capacities section.
Subscriptions and Licensing
Power BI Premium is a tenant-level Office 365 subscription available in two SKU (Stock-Keeping Unit) families:
EM SKUs (EM1-EM3) for embedding, requiring a yearly commitment, billed monthly
P SKUs (P1-P3) for embedding and enterprise features, requiring a monthly or yearly commitment, billed
monthly, and includes a license to install Power BI Report Server on-premises
An alternative approach is to purchase an Azure Power BI Embedded subscription which has a single SKU family:
A SKUs (A1-A6) for embedding and capacity testing purposes only.
All SKUs deliver v-cores to create capacities [9], but the EM SKUs are restricted for smaller scale embedding.
While the focus of this whitepaper is on the P SKUs, much of what is discussed is also relevant also to the A SKUs.
In contrast to the Premium subscription SKUs, Azure SKUs require no time commitment and are billed hourly.
They deliver full elasticity enabling scale up, scale down, pause, resume and delete.
Azure Power BI Embedded is largely out of scope for this whitepaper, but it is discussed in the Testing Approaches
topic as a practical and economic option to test and measure workloads.
For further information about the Azure SKUs, refer to the Azure Power BI Embedded Documentation.
Power BI Premium subscriptions are purchased by administrators in the Microsoft 365 admin center. Specifically,
only Office 365 Global Administrators or Billing Administrators can purchase SKUs.
Once purchased, the tenant receives a corresponding number of v-cores to assign to capacities - this is known as
v-core pooling. For example, purchasing a P3 SKU provides the tenant with 32 v-cores.
For further information, refer to the How to purchase Power BI Premium document.
Premium Capacities
In contrast to a shared capacity where workloads run on computational resources shared with other customers, a
dedicated capacity is for exclusive use by an organization. It is isolated with dedicated computational resources
which provide dependable and consistent performance for hosted content.
The focus of this whitepaper is Premium capacity , meaning it is associated with any of the EM or P SKUs.
Capacity Nodes
As described in the Subscriptions and Licensing topic, there are two Power BI Premium SKU families: EM and P.
All Power BI Premium SKUs are available as capacity nodes, with each representing a set amount of resources
consisting of processor, memory and storage. In addition to resources, each SKU has operational limits on the
number of DirectQuery (DQ ) and Live Connection (LC ) connections per second and the number of parallel model
refreshes.
Processing is achieved by a set number of v-cores, divided equally between backend and frontend.
Backend v-cores are responsible for core Power BI functionality, including query processing, cache management,
running R services, model refresh, natural language processing (Q&A), and server-side rendering of reports and
images. Backend v-cores are assigned a fixed amount of memory which is primary used to host models which are
also referred to as active datasets.
Frontend v-cores are responsible for the web service, dashboard and report document management, access
rights management, scheduling, APIs, uploads and downloads, and generally for everything relating to the user
experiences.
Storage is set to 100 TB per capacity node.
The resources and limits of each Premium SKU (and equivalently sized A SKU ) are described in the following
table.

MODEL
CAPACITY TOTAL V- BACKEND V- FRONTEND V- DQ/LC (PER REFRESH
NODES CORES CORES RAM (GB) CORES SEC) PARALLELISM

EM1/A1 1 0.5 2.5 0.5 3.75 1

EM2/A2 2 1 5 1 7.5 2

EM3/A3 4 2 10 2 15 3

P1/A4 8 4 25 4 30 6

P2/A5 16 8 50 8 60 12

P3/A6 32 16 100 16 120 24

Capacity Workloads
Capacity workloads are services made available to users. By default, Premium and Azure capacities support only a
dataset workload associated with running Power BI queries which cannot be disabled.
Additional workloads can be enabled for paginated reports and dataflows. Each additional workload requires
configuring the maximum memory (as a percentage of total available memory) that can be used by the workload.
How Capacities Function
At all times, the Power BI service strives to make the best use of capacity resources while not exceeding limits
imposed on the capacity.
Capacity operations are classified as either interactive or background. Interactive operations include rendering
requests and responding to user interactions (filtering, Q&A querying, etc.). Generally, import model querying is
memory resource-intensive, while querying LC/DQ models is CPU -intensive. Background operations include
dataflow and import model refreshes, and dashboard query caching.
It is important to understand that interactive operations are always prioritized over background operations to
ensure the best possible user experience. If there are insufficient resources, background operations are added to a
queue for processing when resources free up. Background operations, like dataset refreshes, can be stopped mid-
process by the Power BI service and added to a queue.
Import models must be fully loaded into memory so that they can be queried or refreshed. The Power BI service
manages memory usage by using sophisticated algorithms to ensure maximum use of available memory, and can
achieve overcommitting the capacity: While it is possible for a capacity to store many import models (up to 100 TB
per Premium capacity), when their combined disk storage exceeds the supported memory (and additional
memory is required for querying and refresh), then they cannot all be loaded into memory at the same time.
Import models are therefore loaded into - and removed from - memory according to usage. An import model is
loaded when it is queried (interactive operation) and not yet in memory, or when it is to be refreshed (background
operation).
The removal of a model from memory is known as eviction , and it is an operation that Power BI can perform
quickly depending on the size of the models. If the capacity is not experiencing any memory pressure, models are
simply loaded into memory and remain there. [10] However, when insufficient memory is available to load a
model, the Power BI service will first need to free up memory. It frees up memory by detecting models that have
become inactive by seeking models which have not been used in the last three minutes [11], and then evicting
them. If there are no inactive models to evict, the Power BI service seeks to evict models loaded for background
operations. A last resort, after 30 seconds of failed attempts [11], is to fail the interactive operation. In this case, the
report user is gracefully notified of failure with a suggestion to try again shortly.
It is important to stress that dataset eviction is a normal and expected behavior. It strives to maximize memory
usage by loading and unloading models whose combined sizes can exceed available memory. This is by design,
and completely transparent to report users. High eviction rates do not necessarily mean the capacity is
insufficiently resourced. They can, however, become a concern if query or refresh responsiveness is suffering
because of high eviction rates.
Refreshes of import models are always memory intensive as models must be loaded into memory and additional
memory is required for the processing. A full refresh can use approximately double the amount of memory
required by the model. This ensures that the model can be queried even when being processed (queries are sent to
the existing model, until the refresh has completed, and the new model data is available). Note, incremental refresh
will require less memory and could complete faster, and so can substantially reduce pressure on capacity
resources. Refreshes can also be CPU -intensive for models, especially those with complex Power Query
transformations, or calculated tables/columns that are complex or are based on large tables.
Refreshes - like queries - require that the model be loaded into memory. If there is insufficient memory, the Power
BI service will attempt to evict inactive models, and if this is not possible (as all models are active), the refresh job
is queued. Refreshes are typically very CPU -intensive, even more so than queries. For this reason, there are
capacity limits on the number of concurrent refreshes, set to 1.5 x the number of backend v-cores, rounded up. If
there are too many concurrent refreshes, a scheduled refresh will be queued. When these situations occur, it takes
longer for the refresh to complete. Note that on-demand refreshes (triggered by a user request or API call) will
retry three times [11], and then fail if there are still not enough resources.

Managing Power BI Premium

Managing Power BI Premium involves purchasing subscriptions, and creating, managing and monitoring
Premium capacities.
Creating and Managing Capacities
The Capacity Settings page of the Power BI Admin Portal displays the number of v-cores purchased and
available (i.e. yet to be assigned to a capacity) and lists Premium capacities. The page allows Office 365 Global
Administrators or Power BI service administrators to create Premium capacities from available v-cores, or to
modify existing Premium capacities.
When creating a Premium capacity, the administrator is required to define:
Capacity name (unique within the tenant)
Capacity admin(s)
Capacity size
Region for data residency [12]
At least one Capacity Admin must be assigned. Users assigned as Capacity Admins can:
Assign workspaces to the capacity
Manage user permissions, to add additional Capacity Admins or users with assignment permissions (to enable
them to assign workspaces to the capacity)
Manage workloads, to configure maximum memory usage for paginated reports and dataflows workloads
Restart the capacity, to reset all operations in case of system overload [13]
Capacity Admins cannot access workspace content (unless explicitly assigned workspace permissions) and they do
not have access to all Power BI admin areas (unless explicitly assigned) such as usage metrics, audit logs or tenant
settings. Importantly, Capacity Admins do not have permissions to create new capacities or scale existing
capacities. Also, they are assigned on a per capacity-basis, ensuring that they can only view and manage capacities
to which they are assigned.
Capacity size must be selected from an available list of SKU options which is constrained by the number of
available v-cores in the pool. It is possible to create multiple capacities from the pool which could be sourced from
one or more purchased SKUs. For example, a P3 SKU (32 v-cores) could be used to create three capacities: one P2
(16 v-cores), and two P1 (2 x 8 v-cores). Improved performance and scale may be achieved by creating smaller
sized capacities, and this topic is discussed in the Optimizing Premium Capacities section. The following image
shows an example setup for the fictitious Contoso organization consisting of five Premium capacities (3 x P1, and
2 x P3) with each containing app workspaces, and several workspaces in shared capacity.

A Premium capacity can be assigned to a region other than the home region of the Power BI tenant, providing
administrative control over which datacenters (within defined geographic regions) Power BI content resides. [12]
Power BI service administrators and Office 365 Global Administrators can modify Premium capacities.
Specifically, they can:
Change the capacity size to scale up or scale down resources. However, it is not possible to downgrade a P SKU
to an EM SKU, or upgrade vice versa.
Add or remove Capacity Admins
Add or remove users that have assignment permissions
Add or remove additional workloads
Change regions
Assignment permissions are required to assign a workspace to a specific Premium capacity. The permissions can
be granted to the entire organization, specific users or groups.
By default, Premium capacities support workloads associated with running Power BI queries. It also supports two
additional workloads: Paginated Reports and Dataflows. Each workload requires configuring the maximum
memory (as a percentage of total available memory) that can be used by the workload. It is important to
understand that increasing maximum memory allocations can impact on the number of active models that can be
hosted, and the throughput of refreshes.
Memory is dynamically allocated to dataflows, but it is statically allocated to paginated reports. The reason for
statically allocating the maximum memory is that paginated reports run within a secured contained space of the
capacity. Care should be taken when setting paginated reports memory as it reduces available memory for loading
models.

EM3 P1 P2 P3

Paginated reports N/A 20% default; 10% 20% default; 5% 20% default; 2.5%
minimum minimum minimum

Dataflows 20% default; 8% 20% default; 4% 20% default; 2% 20% default; 1%

minimum minimum minimum minimum

Deleting a Premium capacity is possible and will not result in the deletion of its workspaces and content. Instead, it
will move any assigned workspaces to shared capacity. When the Premium capacity was created in a different
region, the workspace will be moved to shared capacity of the home region.
Assigning Workspaces to Capacities
Workspaces can be assigned to a Premium capacity in the Power BI Admin Portal or - for an app workspace - in
the Workspace pane.
Capacity Admins, as well as Office 365 Global Administrators or Power BI service administrators, can bulk assign
workspaces in the Power BI Admin Portal. Bulk assigned can apply to:
Workspaces by users : All workspaces owned by those users, including personal workspaces, are assigned
to the Premium capacity. This will include the re-assignment of workspaces when they are already assigned
to a different Premium capacity. In addition, the users are also assigned workspace assignment permissions.
Specific workspaces
The entire organization's workspaces : All workspaces, including personal workspaces, are assigned to
the Premium capacity. In addition, all current and future users are assigned workspace assignment
permissions. [14]
A workspace can be added to a Premium capacity by using the Workspace pane providing the user is both a
workspace admin and has assignment permissions.
Workspace admins can remove a workspace from a capacity (to shared capacity) without requiring assignment
permission. Removing workspaces from dedicated capacities effectively relocates the workspace to shared
capacity. Note that removing a workspace from a Premium capacity may have negative consequences resulting,
for example, in shared content becoming unavailable to Power BI Free licensed users, or the suspension of
scheduled refresh when they exceed the allowances supported by shared capacities.
In the Power BI service, a workspace assigned to a Premium capacity is easily identified by the diamond icon that
adorns the workspace name.

Monitoring Capacities
Monitoring Premium capacities provides administrators with an understanding of how the capacities are
performing. Capacities can be monitored by using the Power BI Admin Portal or the Power BI Premium
Capacity Metrics (Power BI) app.
Power BI Admin Portal
The Power BI Admin Portal allows monitoring of four summary tiles which report on loads placed on the
capacity resources. The four summary tiles are:
CPU : Number of times CPU exceeded 80% utilization
Memory Thrashing : Number of times exceeded 80%, representing memory pressure on the backend v-cores.
Specifically, it is a measure of how many times a dataset was evicted from memory due to memory pressure
and the demand for more active datasets.
Memory Usage : Average memory usage (in GB )
Direct Query : Number of times DQ and LC queries - measured per second - exceeded 80% of the limit
Tile values are calculated over an hourly time window to indicate how many hours in the past seven days
corresponded to the metric threshold. It is important to understand that exceeding a threshold is not necessarily a
dire situation, but possibly an indication of performance degradation.
By clicking on a summary tile, it is possible to clickthrough to a report to view the metric as a line chart over the
past seven days. The data presented in the chart is a summary of hourly results that can help you to determine a
general understanding of what was taking place at a specific hour.
The monitoring capabilities in the Power BI Admin Portal are basic and are designed to provide a quick
understanding of key system metrics. For more detailed monitoring, it is recommended that you use the Power BI
Premium Capacity Metrics app.
Power BI Premium Capacity Metrics App
The Power BI Premium Capacity Metrics app is a Power BI app available to Capacity Admins and is installed
like any other Power BI app [15]. It contains a dashboard and report.

When the app opens, the dashboard is loaded to present numerous tiles expressing an aggregated view over all
capacities of which the user is a Capacity Admin. The dashboard layout includes five main sections:
1. Overview : App version, number of capacities and workspaces
2. System Summary : Memory and CPU metrics
3. Dataset Summary : Number of datasets, DQ/LC, refresh and query metrics
4. Dataflow Summary : Number of dataflows, and dataset metrics
5. Paginated Report Summary : Refresh and view metrics
The underlying report (from which the dashboard tiles were pinned) can be accessed by clicking on any dashboard
tile. It provides a more detailed perspective of each of the dashboard sections and supports interactive filtering.
Filtering can be achieved by setting slicers by date range, capacity, workspace and workload (report, dataset,
dataflow ), and by selecting elements within report visuals to cross filter the report page. Cross filtering is a
powerful technique to narrow down to specific time periods, capacities, workspaces, datasets, etc. and can be very
helpful when performing root cause analysis.
The report consists of the following five pages:
1. Datasets : Displays detailed metrics on dataset health. Button selection reveals different perspectives:
Summary, Refreshes, Query Durations, Query Waits and Datasets
2. Paginated Reports : Displays detailed metrics on paginated report health
3. Dataflows : Displays detailed metrics on dataflow health
4. System : Displays overall capacity metrics, including memory and CPU utilization
5. Display Names and IDs : Displays names, IDs, and owners for capacities, workspaces and workloads
The reports pages include different perspectives accessible by clicking buttons. Report visuals allow monitoring
metrics over time to compare them against system resource usage.
This whitepaper will not describe each page and perspective. Instead, it lists the metrics available in the report
together with their purpose. The report presents many pages and visuals based on the following metrics, first by
resource, as shown in the following tables.
En t i t i e s (o f w h i c h t h e u se r i s a C a p a c i t y A d m i n )

METRIC DESCRIPTION

Capacities Number of capacities

Workspaces Number of workspaces in your capacities that are reporting

metrics over the past seven days

Datasets Number of datasets in all workspaces in your capacities

Dataflows Number of dataflows in all workspaces in your capacities

Paginated reports Number of paginated reports in all workspaces in your

capacities

Mem o r y

METRIC DESCRIPTION

Average memory Average memory usage over the past seven days (in GB)

Average memory by workloads: datasets, dataflows, Average memory usage over the past seven days (in GB) by
paginated reports workloads: datasets, dataflow, paginated reports

Highest utilization Maximum memory consumption (in GB) over the past seven
days, split into three-minute interval in 1-hour buckets

CPU

METRIC DESCRIPTION

High utilization count Number of times CPU exceeded 80% of the thresholds in the
past seven days, split into 3-minute intervals in 1-hour
buckets

DQ /LC c o n n ec t i o n s

METRIC DESCRIPTION

High utilization count Number of times DQ/LC connections exceeded 80% of the
thresholds in the past seven days, split into 3-minute intervals
in 1-hour buckets
The following tables show workload-related metrics.
D a t a se t r e fr e sh

METRIC DESCRIPTION

Refreshes Number of refreshes in the past seven days

Successful refreshes Number of successful refreshes in the past seven days

Failed refreshes Number of failed refreshes in the past seven days

Average refresh duration Average refresh duration in minutes in the past seven days

Maximum refresh duration The duration of the longest running refresh in minutes

Average wait time Average refresh wait time (lag between the scheduled time
and start time) in minutes [16]

Maximum wait time Maximum refresh wait time (lag between the scheduled time
and start time) in minutes

Refresh reliability Percentage of refreshes that completed by in the past seven

days

D a t a se t q u e r i e s

METRIC DESCRIPTION

Queries Number of queries run in the past seven days

Successful queries Number of successful queries run in the past seven days

Failed queries Number of failed queries run in the past seven days

Average query duration Average query duration (in ms) in the past seven daysCan be
used to determine hourly query distribution together with
memory consumption, split into 1-hour buckets

Maximum query duration Maximum query duration (in ms) in the past seven days

Query wait count Number of queries which experienced some wait time or last 7
days

Average query wait time Average query wait time (in ms) over the past seven daysCan
be used to determine hourly query wait time distribution
together with memory consumption, split into 1-hour buckets

Maximum query wait time Maximum query wait time (in ms) over the past seven days

D a t a se t l o a d s
 METRIC DESCRIPTION

Average dataset size Average size (in MB) of datasets in memory [ 17]

Active datasets loaded in memory Number of datasets loaded into memory per hour

Dataset evictions Number of datasets evicted due to memory pressure

Dataset eviction and memory consumption Number of datasets evicted from memory per hour

Active memory Active memory shows the total amount of memory that
cannot be evicted because it is in use. The difference between
the active memory and the total memory is the sum of the
memory consumed by datasets which are in memory but
have not been used in the last 3 minutes.

D a t a fl o w s

METRIC DESCRIPTION

Refreshes Number of dataflow refreshes in the past seven days

Average refresh duration Average dataflow refresh duration (in minutes) in the past
seven days

Maximum refresh duration Maximum dataflow refresh duration (in minutes) in the past
seven days

Average refresh wait time Average dataflow refresh wait time (lag between the
scheduled time and start time, in minutes)

Maximum refresh wait time Maximum dataflow refresh wait time (lag between the
scheduled time and start time, in minutes)

Refresh reliability Percentage of dataflow refreshes that completed in the past

seven days

Pagi n at ed r epo r t s

METRIC DESCRIPTION

Views Number of report views

Row count Number of rows of data in the report

Average retrieval Average data retrieval duration (in ms) in the past seven days

Average processing Average processing duration (in ms) in the past seven days

Average rendering Average rendering duration (in ms) in the past seven days

Average duration Average total time to process all phases of a report view (in
ms) in the past seven days
 METRIC DESCRIPTION

The app is likely to undergo frequent version updates. For up to date information, refer to the Monitor Power BI
Premium and Power BI Embedded capacities document.
Interpreting Metrics
Metrics should be monitored to establish a baseline understanding of resource usage and workload activity. If the
capacity becomes slow, it is important to understand which metrics to monitor, and the conclusions you can make.
Ideally, queries should complete within a second to deliver responsive experiences to report users and enable
higher query throughput. It is usually of lesser concern when background processes - including refreshes - take
longer times to complete.
In general, slow reports can be an indication of an over-heating capacity. When reports fail to load, this is an
indication of an over-heated capacity. In either situation, the root cause could be attributable to many factors,
including:
Failed queries certainly indicate memory pressure, and that a model could not be loaded into memory.
The Power BI service will attempt to load a model for 30 seconds before failing.
Excessive query wait times can be due to several reasons:
The need for the Power BI service to first evict model(s) and then load the to-be-queried model (recall
that higher dataset eviction rates alone are not an indication of capacity stress, unless accompanied by
long query wait times that indicate memory thrashing)
Model load times (especially the wait to load a large model into memory)
Long running queries
Too many LC\DQ connections (exceeding capacity limits)
CPU saturation
Complex report designs with an excessive number of visuals on a page (recall that each visual is a query)
Long query durations can indicate that model designs are not optimized, especially when multiple
datasets are active in a capacity, and just one dataset is producing long query durations. This suggests that
the capacity is sufficiently resourced, and that the in-question dataset is sub-optimal or just slow. Long
running queries can be problematic as they can block access to resources required by other processes.
Long refresh wait times indicate insufficient memory due to many active models consuming memory, or
that a problematic refresh is blocking other refreshes (exceeding parallel refresh limits).
A more detailed explanation of how to use the metrics is covered next in the Optimizing Premium Capacities
section.

Optimizing Premium Capacities

When Premium capacity performance issues arise, a common first approach is to optimize or tune already-
deployed solutions to restore acceptable response times. The overriding rationale is to avoid purchasing additional
Premium capacity unless it can be justified.
When additional Premium capacity is required, there are two options which will be discussed later in this section:
Scale up the Premium capacity
Add a new Premium capacity
Finally, testing approaches and Premium capacity sizing will conclude this section.
General Best Practices
When striving to achieve best utilization and performance there are some best practices which can be taken on
board as general recommendations. These include:
Using app workspaces instead of personal workspaces
Separating business critical and Self-Service BI (SSBI) into different capacities

If sharing content only with Power BI Pro users, there may be no need to store the content in a dedicated
capacity
Use dedicated capacities when looking to achieve a specific refresh time, or when specific features are
required, for example large datasets or paginated reporting
Addressing Common Questions
Optimizing Power BI Premium deployments is a complex topic involving an understanding of workload
requirements, available resources and their effective use.
This topic addresses seven common support questions, describing possible issues and explanations, and
information on how to identify and resolve them.
Why is the capacity slow, and what can I do?
There are many reasons that can contribute to a slow Premium capacity. This question requires further
information to understand what is meant by slow. Are reports slow to load? Or are they failing to load? Are report
visuals slow to load or update when users interact with the report? Are refreshes taking longer to complete than
expected, or previously experienced?
Having gained an understanding of the reason, you can then begin to investigate. Responses to the following six
questions will help you to address more specific issues.
What content is using up my capacity?
You can use the Power BI Premium Capacity Metrics app to filter by capacity, and review performance metrics
for workspace content. It is possible to review the performance metrics and resource usage by hour for the past
seven days for all content stored within a Premium capacity. This is often the first step to take when
troubleshooting a general concern about Premium capacity performance.
Key metrics to monitor include:
Average CPU and high utilization count
Average Memory and high utilization count, and memory usage for specific datasets, dataflows and paginated
reports
Active datasets loaded in memory
 Average and maximum query durations
Average query wait times
Average dataset and dataflow refresh times
Additionally, in the Power BI Premium Capacity Metrics App, active memory shows the total amount of memory
allocated to a report that cannot be evicted because it is in use in the last three minutes. A high spike in refresh
wait time could be correlated with a large and/or active dataset.
The "Top 5 by Average Duration" chart highlights the top five datasets, paginated reports and dataflows
consuming capacity resources. Content in the top five lists are candidates for investigation and possible
optimization.
Why are reports slow?
The following tables show possible issues and ways to identify and handle them.
I n su ffi c i e n t c a p a c i t y r e so u r c e s

POSSIBLE EXPLANATIONS HOW TO IDENTIFY HOW TO RESOLVE

High total active memory (model Monitor memory metrics [ 18], and Decrease model size, or convert to
cannot be evicted because it is in use in eviction counts [19] DirectQuery mode - see the Optimizing
the last three minutes) Models topic in this section

Multiple high spikes in query wait times Scale up the capacity

Multiple high spikes in refresh wait Assign the content to a different

times capacity

I n e ffi c i e n t r e p o r t d e si g n s

POSSIBLE EXPLANATIONS HOW TO IDENTIFY HOW TO RESOLVE

Report pages contain numerous visuals Review report designs Redesign reports with fewer visuals per
(interactive filtering can trigger at least page
one query per visual) Interview report users to understand
how they interact with the reports
Visuals retrieve more data than
necessary Monitor dataset query metrics [20]

D a t a se t sl o w (e sp e c i a l l y w h e n r e p o r t s h a v e p r e v i o u sl y p e r fo r m e d w e l l )

POSSIBLE EXPLANATIONS HOW TO IDENTIFY HOW TO RESOLVE

Increasingly large volumes of import Review model designs See the Optimizing Models topic in this
data section
Monitor gateway performance counters
Complex or inefficient calculation logic,
including RLS roles

Model not fully optimized

(DQ/LC) Gateway latency

Slow DQ source query response times

H i g h c o n c u r r e n t r e p o r t u sa g e
 POSSIBLE EXPLANATIONS HOW TO IDENTIFY HOW TO RESOLVE

High query wait times Monitor CPU utilization [21], query wait Scale up the capacity, or assign the
times, and DQ/LC utilization [22] content to a different capacity
CPU saturation metrics + Query durations – if
fluctuating can indicate concurrency Redesign reports with fewer visuals per
DQ/LC connection limits exceeded issues page

Why are reports not loading?

When reports fail to load it is a worst-case scenario, and a sure sign that the capacity has insufficient memory and
is over-heated. This can occur when all loaded models are being actively queried and so cannot be evicted, and any
refresh operations have been paused or delayed. The Power BI service will attempt to load the dataset for 30
seconds, and the user is gracefully notified of the failure with a suggestion to try again shortly.
Currently there is no metric to monitor for report loading failures. You can identify the potential for this issue by
monitoring system memory, specifically highest utilization and time of highest utilization. High dataset evictions
and long dataset refresh average wait time could suggest that this issue is occurring.
If this happens only very occasionally, this may not be considered a priority issue. Report users are informed that
the service is busy and that they should retry after a short time. If this happens too frequently, the issue can be
resolved by scaling up the Premium capacity or by assigning the content to a different capacity.
Capacity Admins (and Power BI service administrators) can monitor the Query Failures metric to determine
when this happens. They can also restart the capacity, resetting all operations in case of system overload.
Why are refreshes not starting on schedule?
Scheduled refresh start times are not guaranteed. Recall that the Power BI service will always prioritize interactive
operations over background operations. Refresh is a background operation that can occur when two conditions
are met:
There is sufficient memory
The number of supported concurrent refreshes for the Premium capacity is not exceeded
When the conditions are not met, the refresh is queued until the conditions are favorable.
For a full refresh, recall that at least double the current dataset memory size is required. If sufficient memory is not
available, then the refresh cannot commence until model eviction frees up memory - this means delays until one
or more datasets becomes inactive and can be evicted.
Recall that the supported number of maximum concurrent refreshes is set to 1.5 times the backend v-cores,
rounded up.
A scheduled refresh will fail when it cannot commence before the next scheduled refresh is due to commence. An
on-demand refresh triggered manually from the UI will attempt to run up to three times before failing.
Capacity Admins (and Power BI service administrators) can monitor the Average Refresh Wait Time (minutes)
metric to determine average lag between the scheduled time and the start of the operation.
While not usually an administrative priority, to influence on-time data refreshes, ensure that sufficient memory is
available. This may involve isolating datasets to capacities with known sufficient resources. It is also possible that
admins could coordinate with dataset owners to help stagger or reduce scheduled data refresh times to minimize
collisions. Note that it is not possible for an administrator to view the refresh queue, or to retrieve dataset
schedules.
Why are refreshes slow?
Refreshes can be slow - or perceived to be slow (as the previous common question addresses).
When the refresh is in fact slow, it can be due to several reasons:
 Insufficient CPU (refresh can be very CPU -intensive)
Insufficient memory, resulting in refresh pausing (which requires the refresh to start over when conditions are
favorable to recommence)
Non-capacity reasons, including data source system responsiveness, network latency, invalid permissions or
gateway throughput
Data volume - a good reason to configure incremental refresh, as discussed below
Capacity Admins (and Power BI service administrators) can monitor the Average Refresh Duration (minutes)
metric to determine a benchmark for comparison over time, and the Average Refresh Wait Time (minutes)
metrics to determine average lag between average lag between the scheduled time and the start of the operation.
Incremental refresh can significantly reduce data refresh duration, especially for large model tables. There are four
benefits associated with incremental refresh:
Refreshes are faster : Only a subset of a table needs loading, reducing CPU and memory usage, and
parallelism can be higher when refreshing multiple partitions
Refreshes occur only when required : Incremental refresh policies can be configured to load only when data
has changed
Refreshes are more reliable : Shorter running connections to volatile data source systems are less susceptible
to disconnection
Models remain trim : Incremental refresh policies can be configured to automatically remove history beyond
a sliding window of time
For further information, refer to the Incremental refresh in Power BI Premium document.
Why are data refreshes not completing?
When the data refresh commences but fails to complete, it can be due to several reasons:
Insufficient memory, even if there is only one model in the Premium capacity, i.e. the model size is very large
Non-capacity reasons, including data source system disconnection, invalid permissions or gateway error
Capacity Admins (and Power BI service administrators) can monitor the Refresh Failures due to out of
Memory metric.
Optimizing Models
Optimal model design is crucial to delivering an efficient and scalable solution. However, it is beyond the scope of
this whitepaper to provide a complete discussion. Instead, this section will provide key areas for consideration
when optimizing models.
Optimizing Power BI-Hosted Models
Optimizing models hosted in a Premium capacity can be achieved at the data source(s) and model layers.
Consider the optimization possibilities for an Import model:

At the data source layer:

 Relational data sources can be optimized to ensure the fastest possible refresh by pre-integrating data, applying
appropriate indexes, defining table partitions that align to incremental refresh periods, and materializing
calculations (in place of calculated model tables and columns) or adding calculation logic to views
Non-relational data sources can be pre-integrated with relational stores
Ensure that gateways have enough resources, preferably on dedicated machines, with sufficient network
bandwidth and in close proximity to the data sources
At the model layer:
Power Query query designs can minimize or remove complex transformations and especially those that merge
different data sources (data warehouses achieve this during their Extract-Transform-Load stage). Also, ensuring
that appropriate data source privacy levels are set, this can avoid requiring Power BI to load full results to
produce a combined result across queries.
The model structure determines the data to load and has a direct impact on the model size. It can be designed
to avoid loading unnecessary data by removing columns, removing rows (especially historic data) or by loading
summarized data (at the expense of loading detailed data). Dramatic size reduction can be achieved by
removing high cardinality columns (especially text columns) which do not store or compress very efficiently.
Model query performance can be improved by configuring single direction relationships unless there is a
compelling reason to allow bi-directional filtering. Consider also using the CROSSFILTER function instead of
bi-directional filtering.
Aggregation tables can achieve fast query responses by loading pre-summarized data, however this will
increase the size of the model and result in longer refresh times. Generally, aggregation tables should be
reserved for very large models or Composite model designs.
Calculated tables and columns increase the model size and result in longer refresh times. Generally, a smaller
storage size and faster refresh time can be achieved when the data is materialized or calculated in the data
source. If this is not possible, using Power Query custom columns can offer improved storage compression.
There may be opportunity to tune DAX expressions for measures and RLS rules, perhaps rewriting logic to
avoid expensive formulas
Incremental refresh can dramatically reduce refresh time and conserve memory and CPU. The incremental
refresh can also be configured to remove historic data keeping model sizes trim.
A model could be redesigned as two models when there are different and conflicting query patterns. For
example, some reports present high-level aggregates over all history, and can tolerate 24 hours' latency. Other
reports are concerned with today's data and need granular access to individual transactions. Rather than design
a single model to satisfy all reports, create two models optimized for each requirement.
Consider the optimization possibilities for a DirectQuery model. As the model issues query requests to the
underlying data source, data source optimization is critical to delivering responsive model queries.

At the data source layer:

The data source can be optimized to ensure the fastest possible querying by pre-integrating data (which is not
possible at the model layer), applying appropriate indexes, defining table partitions, materializing summarized
data (with indexed views), and minimizing the amount of calculation. The best experience is achieved when
passthrough queries need only filter and perform inner joins between indexed tables or views.
 Ensure that gateways have enough resources, preferably on dedicated machines, with sufficient network
bandwidth and in close proximity to the data source
At the model layer:
Power Query query designs should preferably apply no transformations - otherwise attempt to keep
transformations to an absolute minimum
Model query performance can be improved by configuring single direction relationships unless there is a
compelling reason to allow bi-directional filtering. Also, model relationships should be configured to assume
referential integrity is enforced (when this is the case) and will result in data source queries using more efficient
inner joins (instead of outer joins).
Avoid creating Power Query query custom columns or model calculated column - materialize these in the data
source, when possible
There may be opportunity to tune DAX expressions for measures and RLS rules, perhaps rewriting logic to
avoid expensive formulas
Consider the optimization possibilities for a Composite model. Recall that a Composite model enables a mix of
import and DirectQuery tables.

Generally, the optimization topics for Import and DirectQuery models apply to Composite model tables that
use these storage modes.
Typically, strive to achieve a balanced design by configuring dimension-type tables (representing business
entities) as Dual storage mode and fact-type tables (often large tables, representing operational facts) as
DirectQuery storage mode. Dual storage mode means both Import and DirectQuery storage modes, and this
allows the Power BI service to determine the most efficient storage mode to use when generating a native
query for passthrough.
Ensure that gateways have enough resources, preferably on dedicated machines, with sufficient network
bandwidth and in close proximity to the data sources
Aggregations tables configured as Import storage mode can deliver dramatic query performance
enhancements when used to summarize DirectQuery storage mode fact-type tables. In this case, aggregation
tables will increase the size of the model and increase refresh time, and often this is an acceptable tradeoff for
faster queries.
Optimizing Externally-Hosted Models
Many optimization possibilities discussed in the Optimizing Power BI-Hosted Models topic apply also to models
developed with Azure Analysis Services and SQL Server Analysis Services. Clear exceptions are certain features
which are not currently supported, including Composite models and aggregation tables.
An additional consideration for externally-hosted datasets is the database hosting in relation to the Power BI
service. For Azure Analysis Services, this means creating the Azure resource in the same region as the Power BI
tenant (home region). For SQL Server Analysis Services, for IaaS, this means hosting the VM in the same region,
and for on-premises, it means ensuring an efficient gateway setup.
As an aside, it may be of interest to note that Azure Analysis Services databases and SQL Server Analysis Services
tabular databases require that their models be loaded fully into memory and that they remain there at all times to
support querying. Like the Power BI service, there needs to be sufficient memory for refreshing if the model must
remain online during the refresh. Unlike the Power BI service, there is no concept that models are automatically
aged in and out of memory according to usage. Power BI Premium, therefore, offers a more efficient approach to
maximize model querying with lower memory usage.
Capacity Planning
The size of a Premium capacity determines its available memory and processor resources and limits imposed on
the capacity. The number of Premium capacities is also a consideration, as creating multiple Premium capacities
can help isolate workloads from each other. Note that storage is 100 TB per capacity node, and this is likely to be
more than sufficient for any workload.
Determining the size and number of Premium capacities can be challenging, especially for the initial capacities you
create. The first step when capacity sizing is to understand the average workload representing expected day-to-day
usage. It is important to understand that not all workloads are equal. For example - at one end of a spectrum - 100
concurrent users accessing a single report page that contains a single visual is easily achievable. Yet - at the other
end of the spectrum - 100 concurrent users accessing 100 different reports, each with 100 visuals on the report
page, is going to make very different demands of capacity resources.
Capacity Admins will therefore need to consider many factors specific to your environment, content and expected
usage. The overriding objective is to maximize capacity utilization while delivering consistent query times,
acceptable wait times, and eviction rates. Factors for consideration can include:
Model size and data characteristics : Import models must be fully loaded into memory to allow querying or
refreshing. LC/DQ datasets can require significant processor time and possibly significant memory to evaluate
complex measures or RLS rules. Memory and processor size, and LC/DQ query throughput are constrained by
the capacity size.
Concurrent active models : The concurrent querying of different import models will deliver best
responsiveness and performance when they remain in memory. There should be sufficient memory to host all
heavily-queried models, with additional memory to allow for their refresh.
Import model refresh : The refresh type (full or incremental), duration and complexity of Power Query
queries and calculated table/column logic can impact on memory and especially processor usage. Concurrent
refreshes are constrained by the capacity size (1.5 x backend v-cores, rounded up).
Concurrent queries : Many concurrent queries can result in unresponsive reports when processor or LC/DQ
connections exceeds the capacity limit. This is especially the case for report pages that include many visuals.
Dataflows and paginated reports: The capacity can be configured to support dataflows and paginated
reports, with each requiring a configurable maximum percentage of capacity memory. Memory is dynamically
allocated to dataflows, but it is statically allocated to paginated reports.
In addition to these factors, Capacity Admins can consider creating multiple capacities. Multiple capacities allow
for the isolation of workloads and can be configured to ensure priority workloads have guaranteed resources. For
example, two capacities can be created to separate business-critical workloads from self-service BI (SSBI)
workloads. The business-critical capacity can be used to isolate large corporate models providing them with
guaranteed resources, with authoring access granted only to the IT department. The SSBI capacity can be used to
host a growing number of smaller models, with access granted to business analysts. The SSBI capacity may at
times experience query or refresh waits that are tolerable.
Over time, Capacity Admins can balance workspaces across capacities by moving content between workspaces, or
workspaces between capacities, and by scaling capacities up or down. Generally, to host larger models you scale
up and for higher concurrency you scale out.
Recall that purchasing a license provides the tenant with v-cores. The purchase of a P3 subscription can be used to
create one, or up to four Premium capacities, i.e. 1 x P3, or 2 x P2, or 4 x P1. Also, before upsizing a P2 capacity to
a P3 capacity, consideration can be given to splitting the v-cores to create two P1 capacities.
Testing Approaches
Once a capacity size is decided, testing can be performed by creating a controlled environment. A practical and
economic option is to create an Azure (A SKUs) capacity, noting that a P1 capacity is the same size as an A4
capacity, with the P2 and P3 capacities the same size as the A5 and A6 capacities, respectively. Azure capacities can
be created quickly and are billed on an hourly basis. So, once testing is complete, they can be easily deleted to stop
accruing costs.
The test content can be added to the workspaces created on the Azure capacity, and then as a single user can run
reports to generate a realistic and representative workload of queries. If there are import models, a refresh for
each model should be performed also. Monitoring tools can then be used to review all metrics to understand
resource utilization.
It is important that the tests are repeatable: Tests should be run several times and they should deliver
approximately the same result each time. An average of these results can be used to extrapolate and estimate a
workload under true production conditions.
To generate a stress test, consider developing a load testing application to simulate a realistic workload. The
specifics of how to achieve this are outside the scope of this whitepaper. For further information including a code
sample, refer to the Load Testing Power BI Applications with Visual Studio Load Test webinar.

Exploring Real-World Scenarios

In this section, several real-world scenarios will be introduced to describe common issues or challenges, how to
identify them, and how to help resolve them:
Keeping datasets up to date
Identifying slow -responding datasets
Identifying causes for sporadically slow -responding datasets
Determining whether there is enough memory
Determining whether there is enough CPU
The steps, along with chart and table examples are from the Power BI Premium Capacity Metrics App (app)
that a Power BI administrator will have access to.
Keeping Datasets Up to Date
In this scenario, an investigation was triggered when users complained that report data sometimes appeared to be
old or "stale".
In the app, the admin interacts with the Refreshes visual, sorting datasets by the Max Wait Time statistics in
descending order. This helps them reveal the datasets that have the longest wait times, grouped by workspace
name.
In addition, in the Hourly Average Refresh Wait Times visual, they notice that the refresh wait times peak
consistently around 4PM each day.

There are several possible explanations for these results:

Too many refresh attempts could be taking place at the same time, exceeding the limits imposed by the
capacity node (six concurrent refreshes on a P1 with default memory allocation)
Datasets to be refreshed may be too large to fit into available memory (requiring at least 2x the memory
required for full refresh)
Inefficient Power Query logic may be resulting in a memory usage spike during dataset refresh. On a busy
capacity this can occasionally reach the physical limit, failing the refresh and potentially affecting other
report view operations on the capacity.
Frequently queried datasets that need to stay in memory may affect the ability of other datasets to refresh,
due to limited available memory
To help investigate this, the Power BI administrator can look for:
Low available memory at the time of data refresh, when available memory is less than 2x the size of the dataset
to be refreshed
Datasets that were not being refreshed and were not in memory prior to a refresh, yet which started to show
interactive traffic during heavy refresh times. To see which datasets were loaded into memory at any given time
a Power BI administrator can look at the datasets area of Datasets tab in the app and cross filter to a given
time by clicking on one of the bars in the Hourly Loaded Dataset Counts. A local spike (shown in the image
below ) indicates an hour when multiple datasets were loaded into memory, which may delay start of scheduled
refreshes
Increased dataset evictions taking place when data refreshes are scheduled to start, indicating there was high
memory pressure caused by serving too many different interactive reports prior to the time of refresh. The
Hourly Dataset Evictions and Memory Consumption visual can clearly indicate spikes in evictions.
The following image shows a local spike in loaded datasets, which suggests interactive querying delayed start of
refreshes. Selecting a time period in the Hourly Loaded Dataset Counts visual will cross filter the Dataset Sizes
visual.

The Power BI administrator can attempt to resolve the issue by taking steps to ensure that sufficient memory is
available for data refreshes to start by:
Contacting dataset owners and asking them to stagger and space out data refresh schedules
Reducing dataset query load by removing unnecessary dashboards or dashboard tiles, especially those that
enforce row -level security
Speeding up data refreshes by optimizing Power Query logic, model calculated columns or tables, reducing
dataset sizes, or configuring larger datasets to perform incremental data refresh
Identifying Slow-Responding Datasets
In this scenario, an investigation was triggered when users complained that certain reports took a long time to
open, and at times would hang.
In the app, the Power BI administrator can use the Query Durations visual to determine the worst performing
datasets by sorting datasets by descending Average Duration. This visual also shows dataset query counts, so
you can see how often the datasets are queried.

The Power BI administrator can refer to the Query Duration Distribution visual, which shows an overall
distribution of bucketed query performance (<= 30ms, 0-100ms, etc.) for the filtered time period. Generally,
queries that take one second or less are considered responsive by most users; queries that take longer tend to
create a perception of bad performance.
The Hourly Query Duration Distribution visual allows the Power BI administrator to identify one-hour periods
when the capacity performance could have been perceived as poor. The larger the bar segments that represent
query durations over one second, the larger the risk that users will perceive poor performance.
The visual is interactive, and when a segment of the bar is selected, the corresponding Query Durations table
visual on the report page is cross-filtered to show the datasets it represents. This cross-filtering allows the Power
BI administrator to easily identify which datasets are responding slowly.
The following image shows a visual filtered by Hourly Query Duration Distributions, focusing on the worst
performing datasets in one-hour buckets.

Once the poor performing dataset in a specific 1-hour timespan is identified, the Power BI administrator can
investigate whether poor performance is caused by an overloaded capacity, or due to a poorly designed dataset or
report. To achieve this, they can refer to the Query Wait Times visual, and sort datasets by descending average
query wait time. If a large percentage of queries are waiting, a high demand for the dataset is likely the cause of
the many query waits. If the average query wait time is substantial (> 100ms), it may be worth reviewing the
dataset and report to see if optimizations can be made. For example, perhaps fewer visuals on given report pages
or a DAX expression optimization.
There are several possible reasons for query wait time build up in datasets:
A sub-optimal model design, measure expressions, or even report design - all circumstances that can
contribute to long running queries that consume high levels of CPU. This forces new queries to wait until CPU
threads become available and can create a convoy effect (think traffic jam), commonly seen during peak
business hours. The Query Waits page will be the main resource to determine whether datasets have high
average query wait times.
A high number of concurrent capacity users (hundreds to thousands) consuming the same report or dataset.
Even well-designed datasets can perform badly beyond a concurrency threshold. This is usually indicated by a
single dataset showing a dramatically higher value for query counts than other datasets show (i.e. 300K queries
for one dataset compared to <30K queries for all other datasets). At some point the query waits for this dataset
will start to stagger, and this will be seen in the Query Durations visual.
Many disparate datasets queried concurrently, causing thrashing as datasets frequently cycle in and out of
memory. This results in users experiencing slow performance when the dataset is loaded into memory. To
confirm this, the Power BI administrator can refer to the Hourly Dataset Evictions and Memory
Consumption visual, which may indicate that a high number of datasets loaded into memory are being
repeatedly evicted.
Identifying Causes for Sporadically Slow-Responding Datasets
In this scenario, an investigation was triggered when users described that report visuals sometimes felt slow to
respond or could become unresponsive, but at other times they were acceptably responsive.
Within the app, the Query Durations section was used to find the culprit dataset in the following way:
In the Query Durations visual the admin filtered dataset by dataset (starting at the top datasets queried) and
examined the cross filtered bars in the Hourly Query Distributions visual.
When a single one-hour bar showed significant changes in the ratio between all query duration groups vs.
other one-hour bars for that dataset (i.e. the ratios between the colors changes drastically), it means this dataset
demonstrated a sporadic change in performance.
The one-hour bars showing an irregular portion of poor performing queries, indicated a timespan where that
dataset was impacted by a noisy neighbor effect, caused by other datasets' activities.
The image below shows one hour on January 30, where a significant setback in a dataset's performance occurred,
indicated by the size of the "(3,10s]" execution duration bucket. Clicking that one-hour bar reveals all the datasets
loaded into memory during that time, thus surfacing the candidate culprit datasets causing the noisy neighbor
effect.

Once a problematic timespan is identified (i.e. during Jan 30 in the image above) the Power BI administrator can
remove all dataset filters then filter only by that timespan to determine which datasets were actively queried
during this time. The culprit dataset for the noisy neighbor effect is usually either the top queried dataset or the
one with the longest average query duration.
A solution to this problem could be to distribute the culprit datasets over different workspaces on different
Premium capacities, or on shared capacity if the dataset size, consumption requirements, and data refresh patterns
are supported.
The reverse could be true as well. The Power BI administrator could identify times when a dataset query
performance drastically improves and then look for what disappeared. If certain information is missing at that
point, then that may help to point to the causing problem.
Determining Whether There is Enough Memory
To determine whether there is enough memory for the capacity to complete its workloads, the Power BI
administrator can refer to the Consumed Memory Percentages visual in the Datasets tab of the app. All (total)
memory represents the memory consumed by datasets loaded into memory, regardless of whether they are
actively queried or processed. Active memory represents the memory consumed by datasets that are being
actively processed.
In a healthy capacity the visual will look like this, showing a gap between All (total) and Active memory:

In a capacity experiencing memory pressure, the same visual will clearly show active memory and total memory
converging, meaning that it is impossible to load additional datasets into memory at that point in time. In this case,
the Power BI administrator can click Capacity Restart (in Advanced Options of the capacity settings area of the
admin portal). Restarting the capacity results in all datasets being flushed from memory and allowing them to
reload into memory as required (by queries or data refresh).
Determining Whether There is Enough CPU
In general, a capacity's average CPU utilization should remain below 80%. Exceeding this value means the capacity
is approaching CPU saturation.
Effects of CPU saturation are expressed by operations taking longer than they should due to the capacity
performing many CPU context switches as it attempts to process all operations. In a Premium capacity with a high
number of concurrent queries this is indicated by high query wait times. A consequence of high query wait times
is slower responsiveness than usual. The Power BI administrator can easily identify when the CPU is saturated by
viewing the Hourly Query Wait Time Distributions visual. Periodic peaks of query wait time counts indicate
potential CPU saturation.

A similar pattern can sometimes be detected in background operations if they contribute to CPU saturation. A
Power BI administrator can look for a periodic spike in refresh times for a specific dataset, which can indicate CPU
saturation at the time (probably due to other ongoing dataset refreshes and/or interactive queries). In this instance,
referring to the System view in the app may not necessarily reveal that the CPU is at 100%. The System view
displays hourly averages, but the CPU can become saturated for several minutes of heavy operations, which
shows up as spikes in wait times.
There are more nuances to seeing the effect of CPU saturation. While the number of queries that wait is
important, query wait time will always happen to some extent without causing discernable performance
degradation. Some datasets (with lengthier average query time, indicating complexity or size) are more prone to
the effects of CPU saturation than others. To easily identify these datasets, the Power BI administrator can look for
changes in the color composition of the bars in the Hourly Wait Time Distribution visual. After spotting an
outlier bar, they can look for the datasets that had query waits during that time and also look at the average query
wait time compared to average query duration. When these two metrics are of the same magnitude and the query
workload for the dataset is non-trivial, it is likely that the dataset is impacted by insufficient CPU.
This effect can be especially apparent when a dataset is consumed in short bursts of high frequency queries by
multiple users (i.e. in a training session), resulting in CPU saturation during each burst. In this case, significant
query wait times on this dataset can be experienced as well as impacting on other datasets in the capacity (noisy
neighbor effect).
In some cases, Power BI administrators can request that dataset owners create a less volatile query workload by
creating a dashboard (which queries periodically with any dataset refresh for cached tiles) instead of a report. This
can help prevent spikes when the dashboard is loaded. This solution may not always be possible for given
business requirements, however it can be an effective way to avoid CPU saturation, without making changing to
the dataset.

Conclusion
Power BI Premium provides more consistent performance, support for large data volumes, and the flexibility of a
unified self-service and enterprise BI platform for everyone in your organization. This level 300 technical
whitepaper has been written specifically for Power BI administrators, and content authors and publishers. It aims
to help them understand the potential of Power BI Premium, and to explain how to design, deploy, monitor and
troubleshoot scalable solutions.
To deploy and manage Power BI Premium capacities, administrators and model developers will require a very
good understanding of how capacities function, how they can be managed and monitored, and how models can be
optimized, in order to appropriately respond to performance issues and bottlenecks should they arise.

End notes
[1] This technical paper is concerned with Power BI Premium which is only supported by the Power BI cloud
service, and so Power BI Report Server is not in scope, except to state that the license required to install Power BI
Report Server is included with some Power BI Premium SKUs.
[2] Power BI as a cloud service when used to embed content on behalf of application users is Platform-as-a-
Service (PaaS ). This type of embedding can be achieved with different two products, one of which is Power BI
Premium.
[3] Push, streaming and hybrid datasets are not stored in Premium capacities, and are therefore not a
consideration when deploying, managing and monitoring Premium capacities.
[4] Excel workbooks as a Power BI content type are not stored in Premium capacities, and are therefore not a
consideration when deploying, managing or monitoring Premium capacities.
[5] Visuals can be configured to ignore slicer interactions. For further information, refer to the Visualization
interactions in a Power BI report document.
[6] The difference in size can be determined by comparing the Power BI Desktop file size with the Task Manager
memory using for the file.
[7] Support for Microsoft data sources include SQL Server, Azure Data Bricks, Azure HDInsight Spark (Beta),
Azure SQL Database and Azure SQL Data Warehouse. For information about additional sources, refer to the Data
sources supported by Direct Query in Power BI document.
[8] Power BI Premium supports uploading a Power BI Desktop (.pbix) file up to a maximum of 10 GB in size. Once
uploaded, a dataset can grow up to 12 GB in size as a result of refresh. Maximum upload size varies by SKU. For
further information, refer to the Power BI Premium support for large datasets document.
[9] SKUs with less than four v-cores do not run on dedicated infrastructure. This includes the EM1, EM2, A1 and
A2 SKUs.
[10] While rare, models may be unloaded from memory due to service operations.
[11] These timings are subject to change at any time.
[12] This is referred to as multi-geo, currently in preview. The rationale for a multi-geo deployment is typically for
corporate or government compliance, rather than performance and scale. Report and dashboard loading still
involves requests to the home region for metadata. For further information, refer to the Multi-Geo support for
Power BI Premium (Preview ) document.
[13] It is possible that users can cause performance issues by overloading the Power BI service with jobs, writing
overly complex queries, creating circular references, etc.
[14] The option to assign the entire organization's workspaces is not recommended, and a more targeted approach
is preferred. Generally, it is not best practice to use personal workspaces for production content.
[15] It is possible to monitor A SKUs in the app or in the Azure portal, but not in the Power BI Admin Portal. To
monitor A SKUs, refresh of the report will fail if app has not been added to the reader role of the resource. For
further information, refer to the Monitor Power BI Premium and Power BI Embedded capacities document.
[16] Refreshes can wait when there is not enough CPU or memory to start.
[17] The dataset size in memory can be larger than the size on disk by up to 20%.
[18] Average Memory Usage (GB ), and Highest Memory Consumption (GB )
[19] Dataset evictions
[20] Dataset Queries , Dataset Average Query Duration (ms), Dataset Wait Count, and Dataset Average Wait Time
(ms)
[21] CPU High Utilization Count and CPU Time of Highest Utilization (past seven days)
[22] DQ/LC High Utilization Count and DQ/LC Time of Highest Utilization (past seven days)
 Distribute Power BI content to external guest users
using Azure Active Directory B2B
3/22/2019 • 42 minutes to read • Edit Online

Summary: This is a technical whitepaper outlining how to distribute content to users outside the organization
using the integration of Azure Active Directory Business-to-business (Azure AD B2B ).
Writers: Lukasz Pawlowski, Kasper de Jonge
Technical Reviewers: Adam Wilson, Sheng Liu, Qian Liang, Sergei Gundorov, Jacob Grimm, Adam Saxton, Maya
Shenhav, Nimrod Shalit, Elisabeth Olson

NOTE
You can save or print this whitepaper by selecting Print from your browser, then selecting Save as PDF.

Introduction
Power BI gives organizations a 360-degree view of their business and empowers everyone in these organizations
to make intelligent decisions using data. Many of these organizations have strong and trusted relationships with
external partners, clients, and contractors. These organizations need to provide secure access to Power BI
dashboards and reports to users in these external partners.
Power BI integrates with Azure Active Directory Business-to-business (Azure AD B2B ) to allow secure distribution
of Power BI content to guest users outside the organization – while still maintaining control and governing access
to internal data.
This white paper covers the all the details you need to understand Power BI's integration with Azure Active
Directory B2B. We cover its most common use case, setup, licensing, and row level security.

NOTE
Throughout this white paper, we refer to Azure Active Directory as Azure AD and Azure Active Directory Business to Business
as Azure AD B2B.

Scenarios
Contoso is an automotive manufacturer and works with many diverse suppliers who provide it with all the
components, materials, and services necessary to run its manufacturing operations. Contoso wants to streamline
its supply chain logistics and plans to use Power BI to monitor key performance metrics of its supply chain.
Contoso wants to share with external supply chain partners analytics in a secure and manageable way.
Contoso can enable the following experiences for external users using Power BI and Azure AD B2B.
Ad hoc per item sharing
Contoso works with a supplier who builds radiators for Contoso's cars. Often, they need to optimize the reliability
of the radiators using data from all of Contoso's cars. An analyst at Contoso uses Power BI to share a radiator
reliability report with an Engineer at the supplier. The Engineer receives an email with a link to view the report.
As described above, this ad-hoc sharing is performed by business users on an as needed basis. The link sent by
Power BI to the external user is an Azure AD B2B invite link. When the external user opens the link, they are asked
to join Contoso's Azure AD organization as a Guest user. After the invite is accepted, the link opens the specific
report or dashboard. The Azure Active Directory admin delegates permission to invite external users to the
organization and chooses what those users can do once they accept the invite as described in the Governance
section of this document. The Contoso analyst can invite the Guest user only because the Azure AD administrator
allowed that action and the Power BI administrator allowed users to invite guests to view content in Power BI's
tenant settings.

1. The process starts with a Contoso internal user sharing a dashboard or a report with an external user. If the
external user is not already a guest in Contoso's Azure AD, they are invited. An email is sent to their email
address that includes an invite to Contoso's Azure AD
2. The recipient accepts the invite to Contoso's Azure AD and is added as a Guest user in Contoso's Azure AD.
3. The recipient is then redirected to the Power BI dashboard, report, or app, which are read-only for the user.
The process is considered ad-hoc since business users in Contoso perform the invite action as needed for their
business purposes. Each item shared is a single link the external user can access to view the content.
Once the external user has been invited to access Contoso resources, a shadow account may be created for them in
Contoso Azure AD and they do not need to be invited again. The first time they try to access a Contoso resource
like a Power BI dashboard, they go through a consent process, which redeems the invitation. If they do not
complete the consent, they cannot access any of Contoso's content. If they have trouble redeeming their invitation
via the original link provided, an Azure AD administrator can resent a specific invitation link for them to redeem.
Planned per item sharing
Contoso works with a subcontractor to perform reliability analysis of radiators. The subcontractor has a team of 10
people who need access to data in Contoso's Power BI environment. The Contoso Azure AD administrator is
involved to invite all the users and to handle any additions/changes as personnel at the subcontractor change. The
Azure AD administrator creates a security group for all the employees at the subcontractor. Using the security
group, Contoso's employees can easily manage access to reports and ensure all required subcontractor personnel
have access to all the required reports, dashboards, and Power BI apps. The Azure AD administrator can also avoid
being involved in the invitation process altogether by choosing to delegate invitation rights to a trusted employee
at Contoso or at the subcontractor to ensure timely personnel management.
Some organizations require more control over when external users are added, are inviting many users in an
external organization, or many external organizations. In these cases, planned sharing can be used to manage the
scale of sharing, to enforce organizational policies, and even to delegate rights to trusted individuals to invite and
manage external users. Azure AD B2B supports planned invites to be sent directly from the Azure portal by an IT
administrator, or through PowerShell using the invitation manager API where a set of users can be invited in one
action. Using the planned invites approach, the organization can control who can invite users and implement
approval processes. Advanced Azure AD capabilities like dynamic groups can make it easy to maintain security
group membership automatically.

1. The process stars with an IT administrator inviting the guest user either manually or through the API provided
by Azure Active Directory
2. The user accepts the invite to the organization.
3. Once the user has accepted the invitation, a user in Power BI can share a report or dashboard with the external
user, or a security group they are in. Just like with regular sharing in Power BI the external user receives an
email with the link to the item.
4. When the external user accesses the link, their authentication in their directory is passed to Contoso's Azure AD
and used to gain access to the Power BI content.
Ad hoc or planned sharing of Power BI Apps
Contoso has a set of reports and dashboards they need to share with one or more Suppliers. To ensure all required
external users have access to this content, it is packaged as a Power BI app. The external users are either added
directly to the app access list or through security groups. Someone at Contoso then sends the app URL to all the
external users, for example in an email. When the external users open the link, they see all the content in a single
easy to navigate experience.
Using a Power BI app makes it easy for Contoso to build a BI Portal for its suppliers. A single access list controls
access to all the required content reducing wasted time checking and setting item level permissions. Azure AD B2B
maintains security access using the Supplier's native identity so users don't need additional login credentials. If
using planned invites with security groups, access management to the app as personnel rotate into or out of the
project is simplified. Membership in security groups manually or by using dynamic groups, so that all external
users from a supplier are automatically added to the appropriate security group.
1. The process starts by the user being invited to Contoso's Azure AD organization through the Azure portal or
PowerShell
2. The user can be added to a user group in Azure AD. A static or dynamic user group can be used, but dynamic
groups help reduce manual work.
3. The external users are given access to the Power BI App through the user group. The app URL should be sent
directly to the external user or placed on a site they have access to. Power BI makes a best effort to send an
email with the app link to external users but when using user groups whose membership can change, Power BI
is not able to send to all external users managed through user groups.
4. When the external user accesses the Power BI app URL, they are authenticated by Contoso's Azure AD, the app
is installed for the user, and the user can see all the contained reports and dashboards within the app.
Apps also have a unique feature that allows app authors to install the application automatically for the user, so it is
available when the user logs in. This feature only installs automatically for external users who are already part of
Contoso's organization at the time the application is published or updated. Thus, it is best used with the planned
invites approach, and depends on the app being published or updated after the users are added to Contoso's
Azure AD. External users can always install the app using the app link.
Commenting and subscribing to content across organizations
As Contoso continues to work with its subcontractors or suppliers, the external Engineers need to work closely
with Contoso's analysts. Power BI provides several collaboration features that help users communicate about
content they can consume. Dashboard commenting (and soon Report commenting) allows users to discuss data
points they see and communicate with report authors to ask questions.
Currently, external guest users can participate in comments by leaving comments and reading the replies.
However, unlike internal users, guest users cannot be @mentioned and do not receive notifications that they've
received a comment. Guest users cannot use the subscriptions feature within Power BI at the time of writing. In an
upcoming release, those restrictions will be lifted and the Guest user will receive an email when a comment
@mentions them, or when a subscription is delivered to their email that contains a link to the content in Power BI.
Access content in the Power BI mobile apps
In an upcoming release, when Contoso's users share reports or dashboards with their external Guest counterparts,
Power BI will send an email notifying the Guest. When the guest user opens the link to the report or dashboard on
their mobile device, the content will open in the native Power BI mobile apps on their device, if they're installed.
The guest user will then be able to navigate between content shared with them in the external tenant, and back to
their own content from their home tenant.

NOTE
The guest user cannot open the Power BI mobile app and immediately navigate to the external tenant, they must start with
a link to an item in the external tenant. Common workarounds are described in the Distributing links to content in the Parent
organization's Power BI section later in this document.

Cross-organization editing and management of Power BI content

Contoso and its Suppliers and subcontractors work increasingly closely together. Often an analyst at the
subcontractor needs additional metrics or data visualizations to be added to a report Contoso has shared with
them. The data should reside in Contoso's Power BI tenant, but external users should be able to edit it, create new
content, and even distribute it to appropriate individuals.
Power BI provides an option that enables External guest users can edit and manage content in the
organization. By default, external users have a read-only consumption-oriented experience. However, this new
setting allows the Power BI admin to choose which external users can edit and manage content within their own
organization. Once allowed, the external user can edit reports, dashboards, publish or update apps, work in
workspaces, and connect to data they have permission to use.
This scenario is described in detail in the section Enabling external users to edit and manage content within Power
BI later in this document.

Organizational relationships using Power BI and Azure AD B2B

When all the users of Power BI are internal to the organization, there is no need to use Azure AD B2B. However,
once two or more organizations want to collaborate on data and insights, Power BI's support for Azure AD B2B
makes it easy and cost effective to do so.
Below are typically encountered organizational structures that are well suited for Azure AD B2B style cross-
organization collaboration in Power BI. Azure AD B2B works well in most cases, but in some situations the
Common alternative approaches covered at the end of this document are worth considering.
Case 1: Direct collaboration between organizations
Contoso's relationship with its radiator supplier is an example of direct collaboration between organizations. Since
there are relatively few users at Contoso and its supplier who need access to radiator reliability information, using
Azure AD B2B based external sharing is ideal. It is easy to use and simple to administer. This is also a common
pattern in consulting services where a consultant may need to build content for an organization.

Typically, this sharing occurs initially using Ad hoc per item sharing. However, as teams grow or relationships
deepen, the Planned per item sharing approach becomes the preferred method to reduce management overhead.
Additionally, the Ad hoc or planned sharing of Power BI Apps, Commenting and subscribing to content across
organizations, access to content in mobile apps can come into play as well, and cross-organization editing and
management of Power BI content. Importantly, if both organizations' users have Power BI Pro licenses in their
respective organizations, they can use those Pro licenses in each other's Power BI environments. This provides
advantageous licensing since the inviting organization may not need to pay for a Power BI Pro license for the
external users. This is discussed in more detail in the Licensing section later in this document.
Case 2: Parent and its subsidiaries or affiliates
Some organization structures are more complex, including partially or wholly owned subsidiaries, affiliated
companies, or managed service provider relationships. These organizations have a parent organization such as a
holding company, but the underlying organizations operate semi-autonomously, sometimes under different
regional requirements. This leads to each organization having its own Azure AD environment and separate Power
BI tenants.

In this structure, the parent organization typically needs to distribute standardized insights to its subsidiaries.
Typically, this sharing occurs using the Ad hoc or planned sharing of Power BI Apps approach as illustrated in the
following image, since it allows distribution of standardized authoritative content to broad audiences. In practice a
combination of all the Scenarios mentioned earlier in this document is used.
This follows the following process:
1. Users from each Subsidiary are invited to Contoso's Azure AD
2. Then the Power BI app is published to give these users access to the required data
3. Finally, the users open the app through a link they've been given to see the reports
Several important challenges are faced by organizations in this structure:
How to distribute links to content in the Parent organization's Power BI
How to allow subsidiary users to access data source hosted by the parent organization
Distributing links to content in the Parent organization's Power BI
Three approaches are commonly used to distribute links to the content. The first and most basic is to send the link
to the app to the required users or to place it in a SharePoint Online site from which it can be opened. Users can
then bookmark the link in their browsers for faster access to the data they need.
The second approach relies on the cross-organization editing and management of Power BI content capability. The
Parent organization allows users from the subsidiaries to access its Power BI and controls what they can access
through permission. This gives access to Power BI Home where the user from the subsidiary sees a
comprehensive list of content shared to them in the Parent organization's tenant. Then the URL to the Parent
organizations' Power BI environment is given to the users at the subsidiaries.
The final approach uses a Power BI app created within the Power BI tenant for each subsidiary. The Power BI app
includes a dashboard with tiles configured with the external link option. When the user presses the tile, they are
taken to the appropriate report, dashboard, or app in the parent organization's Power BI. This approach has the
added advantage that the app can be installed automatically for all users in the subsidiary and is available to them
whenever they sign in to their own Power BI environment. An added advantage of this approach is that it works
well with the Power BI mobile apps that can open the link natively. You can also combine this with the second
approach to enable easier switching between Power BI environments.
Allowing subsidiary users to access data sources hosted by the parent organization
Often analysts at a subsidiary need to create their own analytics using data supplied by the parent organization. In
this case, commonly cloud data sources are used to address the challenge.
The first approach leverages Azure Analysis Services to build an enterprise grade data warehouse that serves the
needs of Analysts across the parent and its subsidiaries as shown the following image. Contoso can host the data
and use capabilities like row level security to ensure users in each subsidiary can access only their data. Analysts at
each organization can access the data warehouse through Power BI Desktop and publish resulting analytics to
their respective Power BI tenants.

The second approach leverages Azure SQL Database to build a relational data warehouse to provide access to
data. This works similarly to the Azure Analysis Services approach, though some capabilities like row level security
may be harder to deploy and maintain across subsidiaries.
More sophisticated approaches are also possible, however the above are by far the most common.
Case 3: Shared environment across partners
Contoso may enter into a partnership with a competitor to jointly build a car on a shared assembly line, but to
distribute the vehicle under different brands or in different regions. This requires extensive collaboration and co-
ownership of data, intelligence, and analytics across organizations. This structure is also common in the consulting
services industry where a team of consultants may do project-based analytics for a client.

In practice, these structures are complex as shown in the following image, and require staff to maintain. To be
effective this structure relies on the cross-organization editing and management of Power BI content capability
since it allows organizations to reuse Power BI Pro licenses purchased for their respective Power BI tenants.

To establish a shared Power BI tenant, an Azure Active Directory needs to be created and at least one Power BI Pro
user account needs to be purchased for a user in that active directory. This user invites the required users to the
shared organization. Importantly, in this scenario, Contoso's users are treated as external users when they operate
within the Shared Organization's Power BI.
The process is as follows:
1. The Shared Organization is established as a new Azure Active Directory and at least one user account is created
in the new organization. That user should have a Power BI Pro license assigned to them.
2. This user then establishes a Power BI tenant and invites the required users from Contoso and the Partner
organization. The user also establishes any shared data assets like Azure Analysis Services. Contoso and the
Partner's users can access the shared organization's Power BI as guest users. If allowed to edit and manage
content in Power BI the external users can use Power BI home, use workspaces, upload, or edit content and
share reports. Typically, all shared assets are stored and accessed from the shared organization.
3. Depending on how the parties agree to collaborate, it is possible for each organization to develop their own
proprietary data and analytics using shared data warehouse assets. They can distribute those to their respective
internal users using their internal Power BI tenants.
Case 4: Distribution to hundreds or thousands of external partners
While Contoso created a radiator reliability report for one Supplier, now Contoso desires to create a set of
standardized reports for hundreds of Suppliers. This allows Contoso to ensure all suppliers have the analytics they
need to make improvements or to fix manufacturing defects.

When an organization needs to distribute standardized data and insights to many external users/organizations,
they can use the Ad hoc or planned sharing of Power BI Apps scenario to build a BI Portal quickly and without
extensive development costs. The process to build such a portal using a Power BI app is covered in the Case Study:
Building a BI Portal using Power BI + Azure AD B2B – Step-by-Step instructions later in this document.
A common variant of this case is when an organization is attempting to share insights with consumers, especially
when looking to use Azure B2C with Power BI. Power BI does not natively support Azure B2C. If you're evaluating
options for this case, consider using Alternative Option 2 in the Common alternative approaches the section later
in this document.

Case Study: Building a BI Portal using Power BI + Azure AD B2B –

Step-by-Step instructions
Power BI's integration with Azure AD B2B gives Contoso a seamless, hassle-free way to provide guest users with
secure access to its BI portal. Contoso can set this up with three steps:

1. Create BI portal in Power BI

The first task for Contoso is to create their BI portal in Power BI. Contoso's BI portal will consist of a
collection of purpose-built dashboards and reports that will be made available to many internal and guest
users. The recommended way for doing this in Power BI is to build a Power BI app. Learn more about apps
in Power BI.
Contoso's BI team creates an App workspace in Power BI

Other authors are added to the workspace

Content is created inside the workspace

 Now that the content is created in an app workspace, Contoso is ready to invite guest users in partner
organizations to consume this content.
2. Invite Guest Users
There are two ways for Contoso to invite guest users to its BI portal in Power BI:
Planned Invites
Ad hoc Invites
Planned Invites
In this approach, Contoso invites the guest users to its Azure AD ahead of time and then distributes Power
BI content to them. Contoso can invite guest users from the Azure portal or using PowerShell. Here are the
steps to invite guest users from the Azure portal:
Contoso's Azure AD administrator navigates to Azure portal > Azure Active Directory > Users and
groups > All users > New guest user
 Add an invitation message for the guest users and click Invite

NOTE
To invite guest users from the Azure portal, you need to an administrator for the Azure Active Directory of your
tenant.

If Contoso wants to invite many guest users, they can do so using PowerShell. Contoso's Azure AD
administrator stores the email addresses of all the guest users in a CSV file. Here are Azure Active Directory
B2B collaboration code and PowerShell samples and instructions.
After the invitation, guest users receive an email with the invitation link.
Once the guest user clicks the link, he/she can access content in the Contoso Azure AD tenant.

NOTE
It is possible to change the layout of the invitation email using the Azure AD branding feature as described here.

Ad hoc Invites
What if Contoso does not know all the guest users it wants to invite ahead of time? Or, what if the analyst in
Contoso who created the BI portal wants to distribute content to guest users herself? We also support this
scenario in Power BI with ad-hoc invites.
The analyst can just add the external users to the access list of the app when she is publishing it. The guest
user gets an invite and once they accept it, they are automatically redirected to the Power BI content.
 NOTE
Invites are needed only the first time an external user is invited to your organization.

3. Distribute Content
Now that Contoso's BI team has created the BI portal and invited guest users, they can distribute their
portal to their end users by giving guest users access to the app and publishing it. Power BI auto-completes
names of guest users who have been previously added to the Contoso tenant. Adhoc invitations to other
guest users can also be added at this point.

NOTE
If using Security groups to manage access to the app for external users, use the Planned Invites approach and share
the app link directly with each external user who must access it. Otherwise, the external user may not be able to
install or view content from within the app._

Guest users get an email with a link to the app.

On clicking this link, guest users are asked to authenticate with their own organization's identity.
 Once they are successfully authenticated, they are redirected to Contoso's BI app.

Guest users can subsequently get to Contoso's app by clicking the link in the email or bookmarking the link.
Contoso can also make it easier for guest users by adding this link to any existing extranet portal that the
guest users already use.
4. Next steps
Using a Power BI app and Azure AD B2B, Contoso was able to quickly create a BI Portal for its suppliers in a
no-code way. This greatly simplified distributing standardized analytics to all the suppliers who needed it.
 While the example showed how a single common report could be distributed among suppliers, Power BI
can go much further. To ensure each partner sees only data relevant to themselves, Row Level Security can
be added easily to the report and data model. The Data security for external partners section later in this
document describes this process in details.
Often individual reports and dashboards need to be embedded into an existing portal. This can also be
accomplished reusing many of the techniques shown in the example. However, in those situations it may be
easier to embed reports or dashboards directly from a workspace. The process for inviting and assigning
security permission to the require users remain the same.

Under the hood: How is Lucy from Supplier1 able to access Power BI
content from Contoso's tenant?
Now that we have seen how Contoso is able to seamlessly distribute Power BI content to guest users in partner
organizations, let's look at how this works under the hood.
When Contoso invited [email protected] to its directory, Azure AD creates a link between [email protected]
and the Contoso Azure AD tenant. This link lets Azure AD know that [email protected] can access content in
the Contoso tenant.
When Lucy tries to access Contoso's Power BI app, Azure AD verifies that Lucy can access the Contoso tenant and
then provides Power BI a token that indicates that Lucy is authenticated to access content in the Contoso tenant.
Power BI uses this token to authorize and ensure that Lucy has access to Contoso's Power BI app.

Power BI's integration with Azure AD B2B works with all business email addresses. If the user does not have an
Azure AD identity, they may be prompted to create one. The following image shows the detailed flow:
It is important to recognize that the Azure AD account will be used or created in the external party's Azure AD, this
will make it possible that Lucy can use her own username and password and her credentials will automatically stop
working in other tenants whenever she leaves the company when her organization also uses Azure AD.

Licensing
Contoso can choose one of three approaches to license guest users from its suppliers and partner organizations to
have access to Power BI content.

NOTE
The Azure AD B2B's free tier is enough to use Power BI with Azure AD B2B. Some advanced Azure AD B2B features like
dynamic groups require additional licensing. Please refer to the Azure AD B2B documentation for additional information:
https://docs.microsoft.com/azure/active-directory/b2b/licensing-guidance

Approach 1: Contoso uses Power BI Premium

With this approach, Contoso purchases Power BI Premium capacity and assigns its BI portal content to this
capacity. This allows guest users from partner organizations to access Contoso's Power BI app without any Power
BI license.
External users are also subject to the consumption only experiences offered to "Free" users in Power BI when
consuming content within Power BI Premium.
Contoso can also take advantage of other Power BI premium capabilities for its apps like increased refresh rates,
dedicated capacity, and large model sizes.

Approach 2: Contoso assigns Power BI Pro licenses to guest users

With this approach, Contoso assigns pro licenses to guest users from partner organizations – this can be done
from Contoso's Microsoft 365 admin center. This allows guest users from partner organizations to access
Contoso's Power BI app without purchasing a license themselves. This can be appropriate for sharing with external
users whose organization has not adopted Power BI yet.
 NOTE
Contoso's pro license applies to guest users only when they access content in the Contoso tenant. Pro licenses enable
access to content that is not in a Power BI Premium capacity. However, external users with a Pro license are restricted by
default to a consumption only experience. This can be change by using the approach described in the Enabling external
users to edit and manage content within Power BI section later in this document.

Approach 3: Guest users bring their own Power BI Pro license

With this approach, Supplier 1 assigns a Power BI Pro license to Lucy. She can then access Contoso's Power BI
app with this license. Since Lucy can use her Pro license from her own organization when accessing an external
Power BI environment, this approach is sometimes referred to as bring your own license (BYOL ). If both
organizations are using Power BI, this offers advantageous licensing for the overall analytics solution and
minimizes overhead of assigning licenses to external users.

NOTE
The pro license given to Lucy by Supplier 1 applies to any Power BI tenant where Lucy is a guest user. Pro licenses enable
access to content that is not in a Power BI Premium capacity. However, external users with a Pro license are restricted by
default to a consumption only experience. This can be change by using the approach described in the Enabling external
users to edit and manage content within Power BI section later in this document.
Data security for external partners
Commonly when working with multiple external suppliers, Contoso needs to ensure that each supplier sees data
only about its own products. User-based security and dynamic row level security make this easy to accomplish
with Power BI.
User-based security
One of the most powerful features of Power BI is Row Level Security. This feature allows Contoso to create a
single report and dataset but still apply different security rules for each user. For an in-depth explanation, see Row -
level security (RLS ).
Power BI's integration with Azure AD B2B allows Contoso to assign Row Level Security rules to guest users as
soon as they are invited to the Contoso tenant. As we have seen before, Contoso can add guest users through
either planned or ad-hoc invites. If Contoso wants to enforce row level security, it is strongly recommended to use
planned invites to add the guest users ahead of time and assigning them to the security roles before sharing the
content. If Contoso instead uses ad-hoc invites, there might be a short period of time where the guest users will
not be able to see any data.

NOTE
This delay in accessing data protected by RLS when using ad-hoc invites can lead to support requests to your IT team
because users will see either blank or broken looking reports/dashboards when opening a sharing link in the email they
receive. Therefore, it is strongly recommended to use planned invites in this scenario.**

Let's walk through this with an example.

As mentioned before, Contoso has suppliers around the globe, and they want to make sure that the users from
their supplier organizations get insights from data from just their territory. But users from Contoso can access all
the data. Instead of creating several different reports, Contoso creates a single report and filters the data based the
user viewing it.
To make sure Contoso can filter data based on who is connecting, two roles are created in Power BI desktop. One
to filter all the data from the SalesTerritory "Europe" and another for "North America".

Whenever roles are defined in the report, a user must be assigned to a specific role for them to get access to any
data. The assignment of roles happens inside the Power BI service ( Datasets > Security )
This opens a page where Contoso's BI team can see the two roles they created. Now Contoso's BI team can assign
users to the roles.

In the example Contoso is adding a user in a partner organization with email address
"[email protected]" to the Europe role:

When this gets resolved by Azure AD, Contoso can see the name show up in the window ready to be added:
Now when this user opens the app that was shared with him, he only sees a report with data from Europe:

Dynamic row level security

Another interesting topic is to see how dynamic row level security (RLS ) work with Azure AD B2B.
In short, Dynamic row level security works by filtering data in the model based on the username of the person
connecting to Power BI. Instead of adding multiple roles for groups of users, you define the users in the model. We
won't describe the pattern in detail here. Kasper de Jong offers a detailed write up on all the flavors of row level
security in Power BI Desktop Dynamic security cheat sheet, and in this whitepaper .
Let's look at a small example - Contoso has a simple report on sales by groups:
Now this report needs to be shared with two guest users and an internal user - the internal user can see
everything, but the guest users can only see the groups they have access to. This means we must filter the data
only for the guest users. To filter the data appropriately, Contoso uses the Dynamic RLS pattern as described in the
whitepaper and blog post. This means, Contoso adds the usernames to the data itself:

Then, Contoso creates the right data model that filters the data appropriately with the right relationships:
To filter the data automatically based on who is logged in, Contoso needs to create a role that passes in the user
who is connecting. In this case, Contoso creates two roles – the first is the "securityrole" that filters the Users table
with the current username of the user logged in to Power BI (this works even for Azure AD B2B guest users).

Contoso also creates another "AllRole" for its internal users who can see everything – this role does not have any
security predicate.
After uploading the Power BI desktop file to the service, Contoso can assign guest users to the "SecurityRole" and
internal users to the "AllRole"
Now, when the guest user now opens the report, he only sees sales from group A:
In the matrix to the right you can see the result of the USERNAME () and USERPRINCIPALNAME () function both
return the guest users email address.
Now the internal user gets to see all the data:

As you can see, Dynamic RLS works with both internal or guest users.

NOTE
This scenario also works when using a model in Azure Analysis Services. Usually your Azure Analysis Service is connected to
the same Azure AD as your Power BI - in that case, Azure Analysis Services also knows the guest users invited through Azure
AD B2B.

Connecting to on premises data sources

Power BI offers the capability for Contoso to leverage on premises data sources like SQL Server Analysis Services
or SQL Server directly thanks to the On-Premises data gateway. It is even possible to sign on to those data
sources with the same credentials as used with Power BI.

NOTE
When installing a gateway to connect to your Power BI tenant, you must use a user created within your tenant. External
users cannot install a gateway and connect it to your tenant._

For external users, this might be more complicated as the external users are usually not known to the on-premises
AD. Power BI offers a workaround for this by allowing Contoso administrators to map the external usernames to
internal usernames as described in Manage your data source - Analysis Services. For example,
[email protected] can be mapped to lucy_supplier1_com#[email protected].

This method is fine if Contoso only has a handful of users or if Contoso can map all the external users to a single
internal account. For more complex scenarios where each user needs their own credentials, there is a more
advanced approach that uses custom AD attributes to do the mapping as described in Manage your data source -
Analysis Services. This would allow the Contoso administrator to define a mapping for every user in your Azure
AD (also external B2B users). These attributes can be set through the AD object model using scripts or code so
Contoso can fully automate the mapping on invite or on a scheduled cadence.

Enabling external users to edit and manage content within Power BI

Contoso can allow external users to contribute content within the organization as described earlier in the cross-
organization editing and management of Power BI content section.
 NOTE
To edit and manage content within your organization's Power BI, the user must have a Power BI Pro license in a workspace
other than My workspace. Users can obtain Pro licenses as covered in the_ Licensing__section of this document.

The Power BI Admin Portal provides the allow external guest users to edit and manage content in the
organization setting in Tenant settings. By default, the setting is set to disabled, meaning external users get a
constrained read-only experience by default. The setting applies to users with UserType set to Guest in Azure AD.
The table below describes the behaviors users experience depending on their UserType and how the settings are
configured.

ALLOW EX TERNAL GUEST USERS TO EDIT

USER TYPE IN AZURE AD AND MANAGE CONTENT SETTING BEHAVIOR

Guest Disabled for the user (Default) Per item consumption only view. Allows
read-only access to reports,
dashboards, and apps when viewed
through a URL sent to the Guest user.
Power BI Mobile apps provide a read-
only view to the guest user.

Guest Enabled for the user The external user gets access to the full
Power BI experience, though some
features are not available to them. The
external user must log in to Power BI
using the Power BI Service URL with the
tenant information included. The user
gets the Home experience, a My
Workspace, and based on permissions
can browse, view, and create content.
Power BI Mobile apps provide a read-
only view to the guest user.

NOTE
External users in Azure AD can also be set to UserType Member. This is not currently supported in Power BI.

In the Power BI Admin portal, the setting is shown in the following image.
Guest users get the read-only default experience and which can edit and manage content. The default is Disabled,
meaning all Guest users have the read-only experience. The Power BI Admin can either enable the setting for all
Guest users in the organization or for specific security groups defined in Azure AD. In the following image, the
Contoso Power BI Admin created a security group in Azure AD to manage which external users can edit and
manage content in the Contoso tenant.
To help these users to log in to Power BI, provide them with the Tenant URL. To find the tenant URL, follow these
steps.
1. In the Power BI service, in the top menu, select help ( ? ) then About Power BI.
2. Look for the value next to Tenant URL. This is the tenant URL you can share with your guest users.

When using the Allow external guest users to edit and manage content in the organization, the specified guest
users get access to your organization's Power BI and see any content to which they have permission. They can
access Home, browse and contribute content to workspaces, install apps where they are on the access list, and have
a My workspace. They can create or be an Admin of workspaces that use the new workspace experience.

NOTE
When using this option make sure to review the governance section of this document since default Azure AD settings
prevent Guest users to use certain features like people pickers which can lead to a reduced experience.**

For guest users enabled through the Allow external guest users to edit and manage content in the organization
tenant setting, some experiences are not available to them. To update or publish reports, guest users need to use
the Power BI service web UI, including Get Data to upload Power BI Desktop files. The following experiences are
not supported:
Direct publishing from Power BI desktop to the Power BI service
Guest users cannot use Power BI desktop to connect to service datasets in the Power BI service
Classic workspaces tied to Office 365 Groups: Guest user cannot create or be Admins of these workspaces.
They can be members.
Sending ad-hoc invites is not supported for workspace access lists
Power BI Publisher for Excel is not supported for guest users
Guest users cannot install a Power BI Gateway and connect it to your organization
Guest users cannot install apps publish to the entire organization
Guest users cannot use, create, update, or install organizational content packs
Guest users cannot use Analyze in Excel
Guest users cannot be @mentioned in commenting ( this functionality will be added in an upcoming release )
Guest users cannot use subscriptions ( this functionality will be added in an upcoming release )
Guest users who use this capability should have a work or school account. Guest users using Personal accounts
experience more limitations due to sign-in restrictions.

Governance
Additional Azure AD Settings that affect experiences in Power BI related to Azure AD B2B
When using Azure AD B2B sharing, the Azure Active Directory administrator controls aspects of the external user's
experience. These are controlled on the External collaboration settings page within the Azure Active Directory
settings for your Tenant.
Details on the settings are available here:
https://docs.microsoft.com/azure/active-directory/b2b/delegate-invitations

NOTE
By default, the Guest users permissions are limited option is set to Yes, so Guest users within Power BI have limited
experiences especially surround sharing where people picker UIs do not work for those users. It is important to work with
your Azure AD administrator to set it to No, as shown below to ensure a good experience.**
Control guest invites
Power BI administrators can control external sharing just for Power BI by visiting the Power BI admin portal. But
tenant administrators can also control external sharing with various Azure AD policies. These policies allow tenant
administrators to
Turn off invitations by end users
Only admins and users in the Guest Inviter role can invite
Admins, the Guest Inviter role, and members can invite
All users, including guests, can invite
You can read more about these policies in Delegate invitations for Azure Active Directory B2B collaboration.
All Power BI actions by external users are also audited in our auditing portal.
Conditional Access policies for guest users
Contoso can enforce conditional access policies for guest users who access content from the Contoso tenant. You
can find detailed instructions in Conditional access for B2B collaboration users.

Common alternative approaches

While Azure AD B2B makes it easy to share data and reports across organizations, there are several other
approaches that are commonly used and may be superior in certain cases.
Alternative Option 1: Create duplicate identities for partner users
With this option, Contoso had to manually create duplicate identities for each partner user in the Contoso Tenant,
as shown in the following image. Then within Power BI, Contoso can share to the assigned identities the
appropriate reports, dashboards, or apps.

Reasons to choose this alternative:

Since the user's identity is controlled by your organization, any related service such as email, SharePoint, etc.
are also within the control of your organization. Your IT Administrators can reset passwords, disable access to
accounts, or audit activities in these services.
Users who use personal accounts for their business often are restricted from accessing certain services so may
need an organizational account.
Some services only work over your organization's users. For example, using Intune to manage content on the
personal/mobile devices of external users using Azure B2B may not be possible.
Reasons not to choose this alternative:
Users from partner organizations must remember two sets of credentials– one to access content from their
own organization and the other to access content from Contoso. This is a hassle for these guest users and many
guest users are confused by this experience.
Contoso must purchase and assign per-user licenses to these users. If a user needs to receive email or use
office applications, they need the appropriate licenses, including Power BI Pro to edit and share content in
Power BI.
Contoso might want to enforce more stringent authorization and governance policies for external users
compared to internal users. To achieve this, Contoso needs to create an in-house nomenclature for external
users and all Contoso users need to be educated about this nomenclature.
 When the user leaves their organization, they continue to have access to Contoso's resources until the Contoso
admin manually deletes their account
Contoso admins have to manage the identity for the guest, including creation, password resets, etc.
Alternative Option 2: Create a custom Power BI Embedded application using custom authentication
Another option for Contoso is to build its own custom embedded Power BI application with custom authentication
('App owns data'). While many organizations do not have the time or resources to create a custom application to
distribute Power BI content to their external partners, for some organizations this is the best approach and
deserves serious consideration.
Often, organizations have existing partner portals that centralize access to all organizational resources for partners,
provide isolation from internal organizational resources, and provide streamlined experiences for partners to
support many partners and their individual users.

In the example above, users from each supplier login to Contoso's Partner Portal that uses AAD as an identity
provider. It could use AAD B2B, Azure B2C, native identities, or federate with any number of other identity
providers. The user would log in and access a partner portal build using Azure Web App or a similar infrastructure.
Within the web app, Power BI reports are embedded from a Power BI Embedded deployment. The web app would
streamline access to the reports and any related services in a cohesive experience aimed to make it easy for
suppliers to interact with Contoso. This portal environment would be isolated from the Contoso internal AAD and
Contoso's internal Power BI environment to ensure suppliers could not access those resources. Typically, data
would be stored in a separate Partner data warehouse to ensure isolation of data as well. This isolation has benefits
since it limits the number of external users with direct access to your organization's data, limiting what data could
potentially be available to the external user, and limiting accidental sharing with external users.
Using Power BI Embedded, the portal can leverage advantageous licensing, using app token or the master user
plus premium capacity purchased in Azure model, which simplifies concerns about assigning licenses to end users,
and can scale up/down based on expected usage. The portal can offer an overall higher quality and consistent
experience since partners access a single portal designed with all of a Partner's needs in mind. Lastly, since Power
BI Embedded based solutions are typically designed to be multi-tenant, it makes it easier to ensure isolation
between partner organizations.
Reasons to choose this alternative:
Easier to manage as the number of partner organizations grows. Since partners are added to a separate
directory isolated from Contoso's internal AAD directory, it simplifies IT's governance duties and helps prevent
accidental sharing of internal data to external users.
Typical Partner Portals are highly branded experiences with consistent experiences across partners and
streamlined to meet the needs of typical partners. Contoso can therefore offer a better overall experience to
partners by integrating all required services into a single portal.
 Licensing costs for advanced scenarios like Editing content within the Power BI Embedded is covered by the
Azure purchased Power BI Premium, and does not require assignment of Power BI Pro licenses to those users.
Provides better isolation across partners if architected as a multi-tenant solution.
The Partner Portal often includes other tools for partner beyond Power BI reports, dashboards, and apps.
Reasons not to choose this alternative:
Significant effort is required to build, operate, and maintain such a portal making it a significant investment in
resources and time.
Time to solution is much longer than using B2B sharing since careful planning and execution across multiple
workstreams is required.
Where there are a smaller number of partners the effort required for this alternative is likely too high to justify.
Collaboration with ad-hoc sharing is the primary scenario faced by your organization.
The reports and dashboards are different for each partner. This alternative introduces management overhead
beyond just sharing directly with Partners.

FAQ
Can Contoso send an invitation that is automatically redeemed, so that the user is just "ready to go"? Or
does the user always have to click through to the redemption URL?
The end user must always click through the consent experience before they can access content.
If you will be inviting many guest users, we recommend that you delegate this from your core Azure AD admins by
adding a user to the guest inviter role in the resource organization. This user can invite other users in the partner
organization by using the sign-in UI, PowerShell scripts, or APIs. This reduces the administrative burden on your
Azure AD admins to invite or resent invites to users at the partner organization.
Can Contoso force multi-factor authentication for guest users if its partners don't have multi-factor
authentication?
Yes. For more information, see Conditional access for B2B collaboration users.
How does B2B collaboration work when the invited partner is using federation to add their own on-
premises authentication?
If the partner has an Azure AD tenant that is federated to the on-premises authentication infrastructure, on-
premises single sign-on (SSO ) is automatically achieved. If the partner doesn't have an Azure AD tenant, an Azure
AD account may be created for new users.
Can I invite guest users with consumer email accounts?
Inviting guest users with consumer email accounts is supported in Power BI. This includes domains such as
hotmail.com, outlook.com and gmail.com. However, those users may experience limitations beyond what users
with work or school accounts encounter.
 What can developers do with Power BI?
4/2/2019 • 2 minutes to read • Edit Online

Developers have different options trying to include Power BI content into applications. As a developer, you can use
these options include embedding with Power BI, custom visuals, and pushing data into Power BI.

Embedding Power BI content

The Power BI service (SaaS ) and the Power BI Embedded service in Azure (PaaS ) have APIs for embedding your
dashboards and reports. This feature means you can access the latest Power BI features – such as dashboards,
gateways, and app workspaces – when embedding your content.
You can go through the Embedding setup tool to quickly get started and download a sample application.
Choose the solution that is right for you:
Embedding for your customers provides the ability to embed dashboards and reports to users who don't
have an account for Power BI. Run the Embed for your customers solution.
Embedding for your organization allows you to extend the Power BI service. Run the Embed for your
organization solution.

To learn more about embedding with Power BI, see Embedding with Power BI.

Developing custom visuals

You can use custom visuals with Power BI to create a unique type of visual that’s tailored to you or your company.
Often these custom visuals are created by developers. They're built when the multitude of visuals that are included
with Power BI don’t quite meet your needs.
Custom visuals allow you to create your visuals for use within Power BI reports. Custom visuals are written in
TypeScript, which is a superset of JavaScript. TypeScript supports some advanced features and early access to
ES6/ES7 functionality. Visual styling is handled using cascading styles sheets (CSS ). For your convenience, we use
the Less pre-compiler, which supports some advanced features such as nesting, variables, conditions, loops, and
other features. If you don't want to use any of those features, you can write plain CSS in the less file.
To start learning more about custom visual development, see Developing a Power BI custom visual.

Using API automation

Power BI displays dashboards that are interactive, and can be created and updated from many different data
sources in real time. Using any programming language that supports REST calls, you can create apps that
integrate with a Power BI dashboard in real time. You can also integrate Power BI tiles and reports into apps.
Developers can also build their own data visualizations that can be used in interactive reports and dashboards.

To see some of the things you can do with the Power BI APIs, see What can developer do with the Power BI APIs?

Next steps
Embedding with Power BI
Developing a Power BI custom visual
What can developers do with the Power BI API?
Power BI Developer Center
 Embedded analytics with Power BI
4/2/2019 • 4 minutes to read • Edit Online

The Power BI service (SaaS ) and the Power BI Embedded service in Azure (PaaS ) have APIs for embedding your
dashboards and reports. This feature means you have a set of capabilities and access to the latest Power BI
features – such as dashboards, gateways, and app workspaces – when embedding your content.
You can go through the Embedding setup tool to quickly get started and download a sample application.
Choose the solution that is right for you:
Embedding for your organization allows you to extend the Power BI service. Run the Embed for your
organization solution.
Embedding for your customers provides the ability to embed dashboards and reports to users who don't have
an account for Power BI. Run the Embed for your customers solution.

Using APIs
There are two main scenarios when embedding Power BI content. Embedding for users in your organization (who
have licenses for Power BI) and embedding for your users and customers without them requiring to have Power
BI licenses. The Power BI REST API allows for both scenarios.
For customers and users without Power BI licenses, you can embed dashboards and reports into your custom
application, using the same API to either service your organization or your customers. Your customers see the
data that is managed by the application. Also, for Power BI users in your organization, they have the additional
options to view their data directly in Power BI or the context of the embedded application. You can take full
advantage of the JavaScript and REST APIs for your embedding needs.
To view a sample of how embedding works, see the JavaScript embed sample.

Embedding for your organization

Embedding for your organization allows you to extend the Power BI service. Embedding for your organization
requires that users of your application sign into the Power BI service when they want to view the content. Once
someone in your organization signs in, they only have access to dashboards and reports that they own or that
someone shared with them in the Power BI service.
Examples of embedding for your organization include internal applications, such as SharePoint Online, Microsoft
Teams integration (you must have Admin rights), and Microsoft Dynamics.
For embedding for your organization, see below:
Integrate a report into an app
Self-service capabilities, such as edit, save, and more, are available through the JavaScript API when embedding
for Power BI users.
You can go through the Embedding setup tool to embed for your organization to get started and download a
sample application that walks you through integrating a report for your organization.

Embedding for your customers

Embedding for your customers lets you embed dashboards and reports for users who don't have an account
for Power BI. Embedding for your customers is also known as Power BI Embedded.
Power BI Embedded is a Microsoft Azure service that lets independent software vendors (ISVs) and developers
quickly embed visuals, reports, and dashboards into an application through a capacity-based, hourly metered
model.

Power BI Embedded has benefits for an ISV, their developers, and customers. For example, an ISV can start
creating visuals for free with Power BI Desktop. ISVs can achieve faster time to market by minimizing visual
analytic development efforts and stand out among the competition with differentiated data experiences. ISVs also
can opt to charge a premium for the additional value created with embedded analytics.
With Power BI Embedded, your customers don't need to know anything about Power BI. You can use two
different methods to create an embedded application. One option is to use a Power BI Pro account. Another
option is to use service principal.
The Power BI Pro account acts as a master account for your application (think of this master account as a proxy
account). The Power BI Pro account allows you to generate embed tokens that provide access to dashboards and
reports within the Power BI service that are owned and managed by your application.
Service principal can embed Power BI content into an application using an app-only token. Service principal
allows you to generate embed tokens that provide access to dashboards and reports within the Power BI service
that are owned and managed by your application.
Developers using Power BI Embedded can spend time focused on building the core competency of their
application rather than spending time developing visuals and analytics. Developers can rapidly meet customer
report and dashboard demands and can embed easily with fully documented APIs and SDKs. By enabling easy-
to-navigate data exploration in apps, ISVs allow customers to make quick, data-driven decisions in context from
any device.

IMPORTANT
While embedding has a dependency on the Power BI service, there is not a dependency on Power BI for your customers.
They do not need to sign up for Power BI to view the embedded content in your application.

When you're ready to move to production, your app workspace must be assigned to a dedicated capacity. Power
BI Embedded in Microsoft Azure, offers dedicated capacities to use with your applications.
For details on how to embed, see How to embed Power BI content.

Next steps
You can now try to embed Power BI content into an application, or try to embed Power BI content for your
customers.
Embed for your organization
What is Power BI Embedded?
Embed for your customers
More questions? Try asking the Power BI Community
 What is Power BI Embedded in Azure?
2/6/2019 • 2 minutes to read • Edit Online

Power BI Embedded is intended to simplify how ISVs and developers use Power BI capabilities with embedded
analytics. Power BI Embedded simplifies Power BI capabilities by helping you quickly add stunning visuals,
reports, and dashboards to your apps. Similar to apps built on Microsoft Azure use services like Machine
Learning and IoT. By enabling easy-to-navigate data exploration in their apps, ISVs allow their customers to make
quick, informed decisions in context.

In May 2017, we announced the convergence of the Power BI and Power BI Embedded services. The
convergence delivered one API surface, a consistent set of capabilities and access to the latest features across
both services. Additionally, we introduced a capacity-based pricing model, simplifying how Power BI is
consumed.
With Power BI Embedded, ISVs and developers have added flexibility in how they embed intelligence in their
apps using the Power BI APIs. ISVs and developers can take advantage of minimized development efforts to
achieve faster time to market and differentiate themselves by infusing Microsoft’s world-class analytics engine in
their app. Equally, developers can spend time focusing on their solution to meet customer demands, instead of
developing visual analytics features. Additionally, Power BI Embedded enables you to work within the familiar
development environments – Visual Studio and Azure – you already use.
Do you have an existing app with embedded Power BI content using Power BI Premium? If you're an ISV or
developer delivering apps or an organization using them, no action is needed. You and your customers can
continue using these apps without interruption. If you have an existing app built on Power BI Workspace
Collections and are interested in taking advantage of the converged API surface and the new capacity-based
Azure SKUs, visit documentation for migration guidance.

Comparing Power BI Embedded with Power BI Premium

Power BI Embedded is for independent software vendors (ISVs) and for developers who build applications for
their customers. It can be used as a third-party business intelligence service that enables you to visualize
application data, rather than building that service yourself. Power BI Embedded is a platform-as-a-service (PaaS )
analytics solution, where developers can embed reports and dashboards into an application for their customers.
Power BI Premium is a software-as-a-service (SaaS ) analytics solution that gives your organization a single
view of their most critical business data.
Power BI Embedded is a pay-as-you-go feature, while Power BI Premium requires a monthly fee. You can view
this video to learn more about how they compare.

Easy-to-use tools
Power BI Embedded allows you to focus on what you do best: building great apps. You can manage and develop
with Power BI Embedded using tools and skills you already have.
The Azure portal: A web-based application for managing all Azure services
Visual Studio Code: a free, downloadable, open source, code editor for Windows, macOS, and Linux that
supports extensions
Power BI Desktop: a free, downloadable tool to create rich, interactive reports with visual analytics
Using the REST API, Power BI Embedded allows developing with any language.
Engage with the Power BI engineering team
Communities: Ask Power BI questions
Power BI Ideas: Request and vote for features
Reddit: Discuss Power BI

Next steps
See the pricing page for capacity node details.
To create a Power BI Embedded capacity, see Create Power BI Embedded capacity in the Azure portal
To begin embedding your Power BI content, see How to embed your Power BI dashboards, reports, and tiles.
 Create Power BI Embedded capacity in the Azure
portal
2/6/2019 • 2 minutes to read • Edit Online

This article walks through how to create a Power BI Embedded capacity in Microsoft Azure. Power BI Embedded
simplifies Power BI capabilities by helping you quickly add stunning visuals, reports, and dashboards to your apps.
If you don't have an Azure subscription, create a free account before you begin.

Before you begin

To complete this quickstart, you need:
Azure subscription: Visit Azure Free Trial to create an account.
Azure Active Directory: Your subscription must be associated with an Azure Active Directory (AAD ) tenant.
Also, you need to be signed in to Azure with an account in that tenant. Microsoft accounts aren't supported.
To learn more, see Authentication and user permissions.
Power BI tenant: At least one account in your AAD tenant must have signed up for Power BI.
Resource group: Use a resource group you already have or create a new one.

Create a capacity
1. Sign into the Azure portal.
2. In the search box, search for Power BI Embedded.
3. Within Power BI Embedded, select Create.
4. Fill in the required information and then select Create.
SETTING DESCRIPTION

Resource name A name to identify the capacity. The resource name is

displayed within the Power BI admin portal in addition to
the Azure portal.

Subscription The subscription you would like to create the capacity

against.

Resource group The resource group that contains this new capacity. Pick
from an existing resource group, or create another. For
more information, see Azure Resource Manager overview.

Power BI capacity administrator Power BI capacity administrators can view the capacity in
the Power BI admin portal and give assignment
permissions to other users. By default, the capacity
administrator is your account. The capacity administrator
must be within your Power BI tenant.
 SETTING DESCRIPTION

Location The location where Power BI is hosted for your tenant.

Your default location is your home region, but you can
change the location using Multi-Geo options.

Pricing tier Select the SKU (v-core count and memory size) that meets
your needs. For details, see Power BI Embedded pricing

You can navigate to All services > Power BI Embedded to see if your capacity is ready. Alternatively, you can
select Pin to dashboard from the notifications section or from within the blade, to navigate to your dashboard to
see your new capacity.

Next steps
To use your new Power BI Embedded capacity, browse to the Power BI admin portal to assign workspaces. For
more information, see Manage capacities within Power BI Premium and Power BI Embedded.
If you don't need to use this capacity, you can pause it to stop billing. For more information, see Pause and start
your Power BI Embedded capacity in the Azure portal.
To begin embedding Power BI content within your application, see How to embed your Power BI dashboards,
reports, and tiles.
More questions? Try asking the Power BI Community
 Multi-Geo support for Power BI Embedded
3/7/2019 • 2 minutes to read • Edit Online

Multi-Geo support for Power BI Embedded means that ISVs and organizations that build applications using
Power BI Embedded to embed analytics into their apps can now deploy their data in different regions around the
world.
Now customers using Power BI Embedded can set up an A capacity using Multi-Geo options, based on the
same features and limitations that Power BI Premium supports using Multi-Geo.

Creating new Power BI Embedded Capacity resource with Multi-Geo

In the Create resource screen, you need to choose the location of your capacity. Until now, it was limited only to
the location of your Power BI tenant, so only a single location was available. With Multi-Geo, you can choose
between different regions to deploy your capacity.
Notice that when opening the location drop-down menu, your home tenant is the default selection.
When choosing a different location, a message prompts you to make sure you're aware of the selection.

View Capacity location

You can see your capacities location easily when going to the main Power BI Embedded management page in the
Azure portal.

It’s also available in the Admin Portal in Powerbi.com. In the Admin portal, choose ‘Capacity settings,’ and then
switch to ‘Power BI Embedded’ tab.

Learn more about creating capacities with Power BI Embedded.

Manage existing capacities location
You can't change a Power BI Embedded resource location once you've created a new capacity.
To move your Power BI content to a different region, follow these steps:
1. Create a new capacity in a different region.
2. Assign all workspaces from the existing capacity to the new capacity.
3. Delete or pause the old capacity.
It’s important to note that if you decide to delete a capacity without reassigning its content, all the content in that
capacity moves to a shared capacity, which is in your home region.

API support for Multi-Geo

To support management of capacities with Multi-Geo through API, we have made some changes to existing APIs:
1. Get Capacities - The API returns a list of capacities with access to the user. The response now includes an
additional property called ‘region,’ that specifies the capacity’s location.
2. Assign To Capacity - The API allows assigning a given workspace to a capacity. This operation doesn't
allow you to assign workspaces to a capacity outside of your home region or move workspaces between
capacities in different regions. To perform this operation, the user or service principal still needs admin
permissions on the workspace, and admin or assign permissions on the target capacity.
3. Azure Resource Manager API - all of the Azure Resource Manager API operations, including Create and
Delete, supports Multi-Geo.

Limitations and considerations

Confirm that any movement you initiate between regions follows all corporate and government compliance
requirements before initiating data transfer.
A cached query stored in a remote region stays in that region at rest. However, other data in transit may go
back and forth between different geographies.
When moving data from one region to another in a Multi-Geo environment, the source data may stay in the
region from which the data was moved for up to 30 days. During that time, users don't have access to it. It's
removed from this region and destroyed during the 30-day period.
Multi-Geo doesn't result in better performance in general. Loading reports and dashboards still involve
requests to the home region for metadata.

Next steps
Learn more about Power BI Embedded capacities and Multi-Geo options for all capacities by referencing the links
below.
What is Power BI Embedded?
Create a Power BI Embedded capacity
Multi-Geo in Power BI Premium capacities
More questions? Try asking the Power BI Community
 Scale your Power BI Embedded capacity in the Azure
portal
2/6/2019 • 2 minutes to read • Edit Online

This article walks through how to scale a Power BI Embedded capacity in Microsoft Azure. Scaling allows you to
increase or decrease the size of your capacity.
This assumes you have created a Power BI Embedded capacity. If you have not, see Create Power BI Embedded
capacity in the Azure portal to get started.

NOTE
A scaling operation can take about a minute. During this time, the capacity will not be available. Embedded content may fail
to load.

Scale a capacity
1. Sign into the Azure portal.
2. Select All services > Power BI Embedded to see your capacities.

3. Select the capacity you want to scale.

4. Select Pricing tier under Scale within your capacity.

Your current pricing tier is outlined in blue.

5. To scale up or down, select the new tier to move to. Selecting a new tier places a dashed blue outline around
the selection. Select Select to scale to the new tier.

Scaling your capacity may take a minute or two to complete.

6. Confirm your tier by viewing the overview tab. The current pricing tier is listed.
Next steps
To pause or start your capacity, see Pause and start your Power BI Embedded capacity in the Azure portal .
To begin embedding Power BI content within your application, see How to embed your Power BI dashboards,
reports, and tiles.
More questions? Try asking the Power BI Community
 Pause and start your Power BI Embedded capacity in
the Azure portal
7/30/2018 • 2 minutes to read • Edit Online

This article walks through how to pause and start a Power BI Embedded capacity in Microsoft Azure. This assumes
you have created a Power BI Embedded capacity. If you have not, see Create Power BI Embedded capacity in the
Azure portal to get started.
If you don't have an Azure subscription, create a free account before you begin.

Pause your capacity

Pausing your capacity prevents you from being billed. Pausing your capacity is great if you do not need to use the
capacity for a period of time. Use the following steps to pause your capacity.

NOTE
Pausing a capacity may prevent content from being available within Power BI. Make sure to unassign workspaces from your
capacity before pausing to prevent interruption.

1. Sign into the Azure portal.

2. Select All services > Power BI Embedded to see your capacities.

3. Select the capacity you want to pause.

4. Select Pause within the capacity details.

5. Select Yes, which confirms you want to pause the capacity.

Start your capacity

Resume usage by starting your capacity. Starting your capacity also resumes billing.
1. Sign into the Azure portal.
2. Select All services > Power BI Embedded to see your capacities.
3. Select the capacity you want to start.

4. Select Start within the capacity details.

5. Select Yes, which confirms you want to start the capacity.

If any content is assigned to this capacity, it is available once started.

Next steps
If you want to scale your capacity up or down, see Scale your Power BI Embedded capacity.
To begin embedding Power BI content within your application, see How to embed your Power BI dashboards,
reports and tiles.
More questions? Try asking the Power BI Community
 Tutorial: Embed Power BI content into an application
for your customers
3/18/2019 • 12 minutes to read • Edit Online

With Power BI Embedded in Azure, you can embed reports, dashboards, or tiles into an application using app
owns data. App owns data is about having an application that uses Power BI as its embedded analytics platform.
As an ISV developer, you can create Power BI content that displays reports, dashboards, or tiles in an application
that is fully integrated and interactive, without requiring users to have a Power BI license. This tutorial
demonstrates how to integrate a report into an application using the Power BI .NET SDK with the Power BI
JavaScript API using Power BI Embedded in Azure for your customers.

In this tutorial, you learn how to:

Register an application in Azure.
Embed a Power BI report into an application.

Prerequisites
To get started, you're required to have:
A Power BI Pro account (a master account that is a username and password to sign in to your Power BI Pro
account), or a service principal (app-only token) .
A Microsoft Azure subscription.
You need to have your own Azure Active Directory tenant setup.
If you're not signed up for Power BI Pro, sign up for a free trial before you begin.
If you don’t have an Azure subscription, create a free account before you begin.

Set up your embedded analytics development environment

Before you start embedding reports, dashboard, or tiles into your application, you need to make sure your
environment allows for embedding with Power BI.
You can go through the Embedding setup tool, so you can quickly get started and download a sample application
that helps you walk through creating an environment and embedding a report.
However, if you choose to set up the environment manually, you can continue below.
Register an application in Azure Active Directory (Azure AD)
Register your application with Azure Active Directory to allow your application access to the Power BI REST APIs.
Registering your application allows you to establish an identity for your application and specify permissions to
Power BI REST resources. Depending if you want to use a master account or service principal, determines how to
get started registering an application.
Depending on which method you take, affects which type of application you register in Azure.
If you proceed using a master account, then proceed with registering a Native app. You use a Native app because
you're working with a non-interactive login.
However, if you proceed using the service principal, you need to proceed with registering a server-side web
application app. You register a server-side web application to create an application secret.

Set up your Power BI environment

Create an app workspace
If you're embedding reports, dashboards, or tiles for your customers, then you have to place your content within
an app workspace. There are different types of workspaces that you can set up: the traditional workspaces or the
new workspaces. If you're using a master account, then it doesn't matter which type of workspaces you use.
However, if you use service principal to sign into your application, then you're required to you use the new
workspaces. In either scenario, both the master account or service principal must be an admin of the app
workspaces involved with your application.
Create and publish your reports
You can create your reports and datasets using Power BI Desktop and then publish those reports to an app
workspace. There are two ways to accomplish this task: As an end user, you can publish reports to a traditional
app workspace with a master account (Power BI Pro license). If you're using service principal, you can publish
reports to the new workspaces using the Power BI REST APIs.
The below steps walk through how to publish your PBIX report to your Power BI workspace.
1. Download the sample Blog Demo from GitHub.
2. Open sample PBIX report in Power BI Desktop.

3. Publish to app workspaces. This process differs depending on whether you're using a master account
(Power Pro license), or service principal. If you're using a master account, then you can publish your report
through Power BI Desktop. Now if you're using service principal, you must use the Power BI REST APIs.

Embed content using the sample application

This sample is deliberately kept simple for demonstration purposes. It's up to the you or your developers to
protect the application secret or the master account credentials.
Follow the steps below to start embedding your content using the sample application.
1. Download Visual Studio (version 2013 or later). Make sure to download the latest NuGet package.
2. Download the App Owns Data sample from GitHub to get started.

3. Open the Web.config file in the sample application. There are fields you need to fill in to run the
application. You can choose MasterUser or ServicePrincipal for the AuthenticationType. Depending
on which type of authentication method you choose there are different fields to complete.

NOTE
The default AuthenticationType in this sample is MasterUser.
 MASTERUSER SERVICEPRINCIPAL
(POWER BI PRO LICENSE) (APP-ONLY TOKEN)

applicationId applicationId

workspaceId workspaceId

reportId reportId

pbiUsername

pbiPassword

applicationsecret

tenant

Application ID
This attribute is needed for both AuthenticationTypes (master account and service principal).
Fill in the applicationId information with the Application ID from Azure. The applicationId is used by the
application to identify itself to the users from which you're requesting permissions.
To get the applicationId, follow these steps:
1. Sign into the Azure portal.
2. In the left-hand navigation pane, select All Services, and select App Registrations.
3. Select the application that needs the applicationId.

4. There's an Application ID that is listed as a GUID. Use this Application ID as the applicationId for the
application.

Workspace ID
This attribute is needed for both AuthenticationTypes (master account and service principal).
Fill in the workspaceId information with the app workspace (group) GUID from Power BI. You can get this
information either from the URL when signed into the Power BI service or using Powershell.
URL

Powershell

Get-PowerBIworkspace -name "App Owns Embed Test"

Report ID
This attribute is needed for both AuthenticationTypes (master account and service principal).
Fill in the reportId information with the report GUID from Power BI. You can get this information either from the
URL when signed into the Power BI service or using Powershell.
URL

Powershell

Get-PowerBIworkspace -name "App Owns Embed Test" | Get-PowerBIReport

Power BI username and password

These attributes are needed only for the master account AuthenticationType.
If you're using service principal to authenticate, then you don't need to fill in the username or password attributes.
Fill in the pbiUsername with the Power BI master account.
Fill in the pbiPassword with the password for the Power BI master account.
Application secret
This attribute is needed only for the service principal AuthenticationType.
Fill in the ApplicationSecret information from the Keys section of your App registrations section in Azure.
This attribute works when using service principal.
To get the ApplicationSecret, follow these steps:
1. Sign in to the Azure portal.
2. In the left-hand navigation pane, select All services and then select App registrations.
3. Select the application that needs to use the ApplicationSecret.

4. Select Settings.

5. Select Keys.
6. Enter a name in the Description box and select a duration. Then select Save to get the Value for your
application. When you close the Keys pane after saving the key value, the value field shows only as hidden.
At that point, you aren't able to retrieve the key value. If you lose the key value, create a new one in the
Azure portal.

Tenant
This attribute is needed only for the service principal AuthenticationType.
Fill in the tenant information with your azure tenant ID. You can get this information from the Azure AD admin
center when signed into the Power BI service or by using Powershell.
Run the application
1. Select Run in Visual Studio.
2. Then select Embed Report. Depending on which content you choose to test with - reports, dashboards or
tiles - then select that option in the application.

3. Now you can view the report in the sample application.

Embed content within your application

Even though the steps to embed your content are done with the Power BI REST APIs, the example codes
described in this article are made with the .NET SDK.
Embedding for your customers within your application requires you to get an access token for your master
account or service principal from Azure AD. You're required to get an Azure AD access token for your Power BI
application before you make calls to the Power BI REST APIs.
To create the Power BI Client with your access token, you want to create your Power BI client object, which
allows you to interact with the Power BI REST APIs. You create the Power BI client object by wrapping the
AccessToken with a Microsoft.Rest.TokenCredentials object.

using Microsoft.IdentityModel.Clients.ActiveDirectory;
using Microsoft.Rest;
using Microsoft.PowerBI.Api.V2;

var tokenCredentials = new TokenCredentials(authenticationResult.AccessToken, "Bearer");

// Create a Power BI Client object. it's used to call Power BI APIs.

using (var client = new PowerBIClient(new Uri(ApiUrl), tokenCredentials))
{
// Your code to embed items.
}

Get the content item you want to embed

You can use the Power BI client object to retrieve a reference to the item you want to embed.
Here is a code sample of how to retrieve the first report from a given workspace.
A sample of getting a content item whether it's a report, dashboard, or tile that you want to embed is available
within the Services\EmbedService.cs file in the sample application.

using Microsoft.PowerBI.Api.V2;
using Microsoft.PowerBI.Api.V2.Models;

// You need to provide the workspaceId where the dashboard resides.

ODataResponseListReport reports = await client.Reports.GetReportsInGroupAsync(workspaceId);

// Get the first report in the group.

Report report = reports.Value.FirstOrDefault();

Create the embed token

Generated an embed token, which can be used from the JavaScript API. The embed token is specific to the item
you're embedding. So at any time you embed a piece of Power BI content, you need to create a new embed token
for it. For more information, including which accessLevel to use, see GenerateToken API.
A sample of creating an embed token for a report, dashboard, or tile want to embed is available within
the Services\EmbedService.cs file in the sample application.

using Microsoft.PowerBI.Api.V2;
using Microsoft.PowerBI.Api.V2.Models;

// Generate Embed Token.

var generateTokenRequestParameters = new GenerateTokenRequest(accessLevel: "view");
EmbedToken tokenResponse = client.Reports.GenerateTokenInGroup(workspaceId, report.Id,
generateTokenRequestParameters);

// Generate Embed Configuration.

var embedConfig = new EmbedConfig()
{
EmbedToken = tokenResponse,
EmbedUrl = report.EmbedUrl,
Id = report.Id
};

A class is created for EmbedConfig and TileEmbedConfig. A sample is available within the
Models\EmbedConfig.cs file and the Models\TileEmbedConfig.cs file.
Load an item using JavaScript
You can use JavaScript to load a report into a div element on your web page.
For a full sample of using the JavaScript API, you can use the Playground tool. The Playground tool is a quick way
to play with different types of Power BI Embedded samples. You can also get more Information about the
JavaScript API by visiting the PowerBI-JavaScript wiki page.
Here is a sample that uses an EmbedConfig model and a TileEmbedConfig model along with views for a
report.
A sample of adding a view for a report, dashboard, or tile is available within the
Views\Home\EmbedReport.cshtml, Views\Home\EmbedDashboard.cshtml, or Views\Home\Embedtile.cshtml files
in the sample application.

<script src="~/scripts/powerbi.js"></script>
<div id="reportContainer"></div>
<script>
// Read embed application token from Model
var accessToken = "@Model.EmbedToken.Token";

// Read embed URL from Model

var embedUrl = "@Html.Raw(Model.EmbedUrl)";

// Read report Id from Model

var embedReportId = "@Model.Id";

// Get models. models contains enums that can be used.

var models = window['powerbi-client'].models;

// Embed configuration used to describe what and how to embed.

// This object is used when calling powerbi.embed.
// This also includes settings and options such as filters.
// You can find more information at https://github.com/Microsoft/PowerBI-JavaScript/wiki/Embed-
Configuration-Details.
var config = {
type: 'report',
tokenType: models.TokenType.Embed,
accessToken: accessToken,
embedUrl: embedUrl,
id: embedReportId,
permissions: models.Permissions.All,
settings: {
filterPaneEnabled: true,
navContentPaneEnabled: true
}
};

// Get a reference to the embedded report HTML element

var reportContainer = $('#reportContainer')[0];

// Embed the report and display it within the div container.

var report = powerbi.embed(reportContainer, config);
</script>

Move to production
Now that you've completed developing your application, it's time to back your app workspace with a dedicated
capacity.

IMPORTANT
Dedicated capacity is required to move to production.
Create a dedicated capacity
By creating a dedicated capacity, you can take advantage of having a dedicated resource for your customer. You
can purchase a dedicated capacity within the Microsoft Azure portal. For details on how to create a Power BI
Embedded capacity, see Create Power BI Embedded capacity in the Azure portal.
Use the table below to determine which Power BI Embedded capacity best fits your needs.

TOTAL CORES
(BACKEND + DIRECTQUERY/LIVE
CAPACITY NODE FRONTEND) BACKEND CORES FRONTEND CORES CONNECTION LIMITS

A1 1 v-core(s) 0.5 core(s), 3-GB 0.5 cores 0 5 per second

RAM

A2 2 v-core(s) 1 core(s), 5-GB RAM 1 cor(e) 10 per second

A3 4 v-core(s) 2 core(s), 10-GB RAM 2 core(s) 15 per second

A4 8 v-core(s) 4 core(s), 25-GB RAM 4 core(s) 30 per second

A5 16 v-core(s) 8 core(s), 50-GB RAM 8 core(s) 60 per second

A6 32 v-core(s) 16 core(s), 100-GB 16 core(s) 120 per second

RAM

With A SKUs, you can't access Power BI content with a FREE Power BI license.
Using embed tokens with PRO licenses are intended for development testing, so the number of embed tokens a
Power BI master account or service principal can generate is limited. A dedicated capacity requires embedding in
a production environment. There's no limit on how many embed tokens you can generate with a dedicated
capacity. Go to Available Features to check the usage value that indicates the current embedded usage in
percentage. The usage amount is based per master account.
For more information, see Embedded analytics capacity planning whitepaper.
Assign an app workspace to a dedicated capacity
Once you create a dedicated capacity, you can assign your app workspace to that dedicated capacity.
To assign a dedicated capacity to a workspace using service principal, use the Power BI REST API. When you are
using the Power BI REST APIs, make sure to use the service principal object ID.
Follow the steps below to assign a dedicated capacity to a workspace using a master account.
1. Within the Power BI service, expand workspaces and select the ellipsis for the workspace you're using for
embedding your content. Then select Edit workspaces.
2. Expand Advanced, then enable Dedicated capacity, then select the dedicated capacity you created. Then
select Save.

3. After you select Save, you should see a diamond next to the app workspace name.

Next steps
In this tutorial, you've learned how to embed Power BI content into an application for your customers. You can
also try to embed Power BI content for your organization.
Embed for your organization
More questions? Try asking the Power BI Community
 Tutorial: Embed Power BI content into an
application for your organization
3/11/2019 • 11 minutes to read • Edit Online

In Power BI, you can embed reports, dashboards, or tiles into an application by using user owns data. User
owns data lets your application extend the Power BI service so it can use embedded analytics. This tutorial
demonstrates how to integrate a report into an application. You use the Power BI .NET SDK with the Power BI
JavaScript API to embed Power BI into an application for your organization.

In this tutorial, you learn the following tasks:

Register an application in Azure.
Embed a Power BI report into an application using your Power BI tenant.

Prerequisites
To get started, you're required to have:
A Power BI Pro account.
A Microsoft Azure subscription.
You need to have your own Azure Active Directory tenant setup.
If you're not signed up for Power BI Pro, sign up for a free trial before you begin.
If you don’t have an Azure subscription, create a free account before you begin.

Set up your embedded analytics development environment

Before you start embedding reports, dashboard, or tiles into your application, you need to make sure your
environment allows for embedding with Power BI.
You can go through the Embedding setup tool, so you can quickly get started and download a sample
application that helps you walk through creating an environment and embedding a report.
However, if you choose to set up the environment manually, you can continue below.
Register an application in Azure Active Directory
Register your application with Azure Active Directory to allow your application access to the Power BI REST
APIs. Registering your application allows you to establish an identity for your application and specify
permissions to Power BI REST resources.
You need to proceed with registering a server-side web application app. You register a server-side web
application to create an application secret.

Set up your Power BI environment

Create an app workspace
If you're embedding reports, dashboards, or tiles for your customers, then you have to place your content within
an app workspace. There are different types of workspaces that you can set up: the traditional workspaces or the
new workspaces.
Create and publish your reports
You can create your reports and datasets by using Power BI Desktop. Then you can publish those reports to an
app workspace. The end user publishing the reports needs to have a Power BI Pro license to publish to an app
workspace.
1. Download the sample Demo from GitHub.

2. Open the sample .pbix report in Power BI Desktop.

3. Publish to the app workspace.

 Now you can view the report in the Power BI service online.

Embed your content by using the sample application

This sample is deliberately kept simple for demonstration purposes.
Follow the steps below to start embedding your content using the sample application.
1. Download Visual Studio (version 2013 or later). Make sure to download the latest NuGet package.
2. Download the User Owns Data sample from GitHub to get started.
3. Open the Cloud.config file in the sample application.
There are fields you need to fill in to run the application.

FIELD

Application ID

Application Secret

Workspace ID

Report ID

AADAuthorityUrl

Application ID
Fill in the applicationId information with the Application ID from Azure. The applicationId is used by the
application to identify itself to the users from which you're requesting permissions.
To get the applicationId, follow these steps:
1. Sign into the Azure portal.
2. In the left-hand navigation pane, select All Services, and select App Registrations.

3. Select the application that needs the applicationId.

4. There's an Application ID that is listed as a GUID. Use this Application ID as the applicationId for
the application.

Application secret
Fill in the ApplicationSecret information from the Keys section of your App registrations section in Azure.
This attribute works when using service principal.
To get the ApplicationSecret, follow these steps:
1. Sign in to the Azure portal.
2. In the left-hand navigation pane, select All services and then select App registrations.
3. Select the application that needs to use the ApplicationSecret.

4. Select Settings.

5. Select Keys.
6. Enter a name in the Description box and select a duration. Then select Save to get the Value for your
application. When you close the Keys pane after saving the key value, the value field shows only as
hidden. At that point, you aren't able to retrieve the key value. If you lose the key value, create a new one
in the Azure portal.

Workspace ID
Fill in the workspaceId information with the app workspace (group) GUID from Power BI. You can get this
information either from the URL when signed into the Power BI service or using Powershell.
URL

Powershell

Get-PowerBIworkspace -name "User Owns Embed Test"

Report ID
Fill in the reportId information with the report GUID from Power BI. You can get this information either from
the URL when signed into the Power BI service or using Powershell.
URL

Powershell

Get-PowerBIworkspace -name "User Owns Embed Test" | Get-PowerBIReport

AADAuthorityUrl
Fill in the AADAuthorityUrl information with the URL that either allows you to embed within your
organizational tenant or embed with a guest user.
For embedding with your organizational tenant, use the URL -
https://login.microsoftonline.com/common/oauth2/authorize.
For embedding with a guest, use the URL - https://login.microsoftonline.com/report-owner-tenant-id - where
you add the tenant ID of the report owner in replacement of report-owner-tenant-id.
Run the application
1. Select Run in Visual Studio.

2. Then select Embed Report. Depending on which content you choose to test with - reports, dashboards
or tiles - then select that option in the application.
3. Now you can view the report in the sample application.

Embed your content within your application

Even though the steps to embed your content can be done with the Power BI REST APIs, the example codes
described in this article are made with the .NET SDK.
To integrate a report into a web app, you use the Power BI REST API or the Power BI C# SDK. You also use an
Azure Active Directory authorization access token to get a report. Then you load the report by using the same
access token. The Power BI Rest API provides programmatic access to specific Power BI resources. For more
information, see Power BI REST APIs and the Power BI JavaScript API.
Get an access token from Azure AD
Within your application, you must get an access token from Azure AD before you can make calls to the Power BI
REST API. For more information, see Authenticate users and get an Azure AD access token for your Power BI
app.
Get a report
To get a Power BI report, you use the Get Reports operation, which gets a list of Power BI reports. From the list
of reports, you can get a report ID.
Get reports by using an access token
The Get Reports operation returns a list of reports. You can get a single report from the list of reports.
To make the REST API call, you must include an Authorization header in the format of Bearer {access token}.
Get reports with the REST API
The following code sample shows you how to retrieve reports with the REST API:
 NOTE
A sample of getting a content item that you want to embed is available in the Default.aspx.cs file in the sample application.
Examples are a report, dashboard, or tile.

using Newtonsoft.Json;

//Get a Report. In this sample, you get the first Report.

protected void GetReport(int index)
{
//Configure Reports request
System.Net.WebRequest request = System.Net.WebRequest.Create(
String.Format("{0}/Reports",
baseUri)) as System.Net.HttpWebRequest;

request.Method = "GET";
request.ContentLength = 0;
request.Headers.Add("Authorization", String.Format("Bearer {0}", accessToken.Value));

//Get Reports response from request.GetResponse()

using (var response = request.GetResponse() as System.Net.HttpWebResponse)
{
//Get reader from response stream
using (var reader = new System.IO.StreamReader(response.GetResponseStream()))
{
//Deserialize JSON string
PBIReports Reports = JsonConvert.DeserializeObject<PBIReports>(reader.ReadToEnd());

//Sample assumes at least one Report.

//You could write an app that lists all Reports
if (Reports.value.Length > 0)
{
var report = Reports.value[index];

txtEmbedUrl.Text = report.embedUrl;
txtReportId.Text = report.id;
txtReportName.Text = report.name;
}
}
}
}

//Power BI Reports used to deserialize the Get Reports response.

public class PBIReports
{
public PBIReport[] value { get; set; }
}
public class PBIReport
{
public string id { get; set; }
public string name { get; set; }
public string webUrl { get; set; }
public string embedUrl { get; set; }
}

Get reports by using the .NET SDK

You can use the .NET SDK to retrieve a list of reports instead of calling the REST API directly. The following
code sample shows you how to list reports:
 using Microsoft.IdentityModel.Clients.ActiveDirectory;
using Microsoft.PowerBI.Api.V2;
using Microsoft.PowerBI.Api.V2.Models;

var tokenCredentials = new TokenCredentials(<ACCESS TOKEN>, "Bearer");

// Create a Power BI Client object. It is used to call Power BI APIs.

using (var client = new PowerBIClient(new Uri(ApiUrl), tokenCredentials))
{
// Get the first report all reports in that workspace
ODataResponseListReport reports = client.Reports.GetReports();

Report report = reports.Value.FirstOrDefault();

var embedUrl = report.EmbedUrl;

}

Load a report by using JavaScript

You can use JavaScript to load a report into a div element on your web page. The following code sample shows
you how to retrieve a report from a given workspace:

NOTE
A sample of loading a content item that you want to embed is available in the Default.aspx file in the sample application.

<!-- Embed Report-->

<div>
<asp:Panel ID="PanelEmbed" runat="server" Visible="true">
<div>
<div><b class="step">Step 3</b>: Embed a report</div>

<div>Enter an embed url for a report from Step 2 (starts with https://):</div>
<input type="text" id="tb_EmbedURL" style="width: 1024px;" />
<br />
<input type="button" id="bEmbedReportAction" value="Embed Report" />
</div>

<div id="reportContainer"></div>
</asp:Panel>
</div>

Site.master
 window.onload = function () {
// client side click to embed a selected report.
var el = document.getElementById("bEmbedReportAction");
if (el.addEventListener) {
el.addEventListener("click", updateEmbedReport, false);
} else {
el.attachEvent('onclick', updateEmbedReport);
}

// handle server side post backs, optimize for reload scenarios

// show embedded report if all fields were filled in.
var accessTokenElement = document.getElementById('MainContent_accessTokenTextbox');
if (accessTokenElement !== null) {
var accessToken = accessTokenElement.value;
if (accessToken !== "")
updateEmbedReport();
}
};

// update embed report

function updateEmbedReport() {

// check if the embed url was selected

var embedUrl = document.getElementById('tb_EmbedURL').value;
if (embedUrl === "")
return;

// get the access token.

accessToken = document.getElementById('MainContent_accessTokenTextbox').value;

// Embed configuration used to describe the what and how to embed.

// This object is used when calling powerbi.embed.
// You can find more information at https://github.com/Microsoft/PowerBI-JavaScript/wiki/Embed-
Configuration-Details.
var config = {
type: 'report',
accessToken: accessToken,
embedUrl: embedUrl
};

// Grab the reference to the div HTML element that will host the report.
var reportContainer = document.getElementById('reportContainer');

// Embed the report and display it within the div container.

var report = powerbi.embed(reportContainer, config);

// report.on will add an event handler which prints to Log window.

report.on("error", function (event) {
var logView = document.getElementById('logView');
logView.innerHTML = logView.innerHTML + "Error<br/>";
logView.innerHTML = logView.innerHTML + JSON.stringify(event.detail, null, " ") + "<br/>";
logView.innerHTML = logView.innerHTML + "---------<br/>";
}
);
}

Using a Power BI Premium dedicated capacity

Now that you've completed developing your application, it's time to back your app workspace with a dedicated
capacity.
Create a dedicated capacity
By creating a dedicated capacity, you can take advantage of having a dedicated resource for the content in your
app workspace. You can create a dedicated capacity by using Power BI Premium.
The following table lists the Power BI Premium SKUs available in Microsoft Office 365:

TOTAL VCORES
(BACK END + FRONT DIRECTQUERY/LIVE
CAPACITY NODE END) BACK-END VCORES FRONT-END VCORES CONNECTION LIMITS

EM1 1 vCore 0.5 vCore, 10 GB of 0.5 vCore 3.75 per second

RAM

EM2 2 vCores 1 vCore, 10 GB of 1 vCores 7.5 per second

RAM

EM3 4 vCores 2 vCores, 10 GB of 2 vCores 15 per second

RAM

P1 8 vCores 4 vCores, 25 GB of 4 vCores 30 per second

RAM

P2 16 vCores 8 vCores, 50 GB of 8 vCores 60 per second

RAM

P3 32 vCores 16 vCores, 100 GB of 16 vCores 120 per second

RAM

P4 64 vCores 32 vCores, 200 GB of 32 vCores 240 per second

RAM

P5 128 vCores 64 vCores, 400 GB of 64 vCores 480 per second

RAM

NOTE
When you’re trying to embed with Microsoft Office apps, you can use EM SKUs to access content with a free Power BI
license. But you can't access content with a free Power BI license when you're using Powerbi.com or Power BI mobile.
When you're trying to embed with Microsoft Office apps by using Powerbi.com or Power BI mobile, you can access
content with a free Power BI license.

Assign an app workspace to a dedicated capacity

After you create a dedicated capacity, you can assign your app workspace to that dedicated capacity. To complete
this process, follow these steps:
1. Within the Power BI service, expand workspaces and select the ellipsis for the workspace you're using for
embedding your content. Then select Edit workspaces.
2. Expand Advanced and enable Dedicated capacity. Select the dedicated capacity you created. Then
select Save.

3. After you select Save, you should see a diamond next to the app workspace name.

Admin settings
Global admins or Power BI service administrators can turn the ability to use the REST APIs on or off for a
tenant. Power BI admins can set this setting for the entire organization or for individual security groups. It's
enabled for the entire organization by default. You can make these changes in the Power BI admin portal.

Next steps
In this tutorial, you learned how to embed Power BI content into an application by using your Power BI
organization account. You can now try to embed Power BI content into an application by using apps. You can
also try to embed Power BI content for your customers:
Embed from apps
Embed for your customers
If you have more questions, try asking the Power BI Community.
 Tutorial: Embed a Power BI content into your
application for national clouds
3/25/2019 • 9 minutes to read • Edit Online

Learn how to embed analytical content within your business process applications for the national cloud. You can
use the Power BI .NET SDK with the Power BI JavaScript API to embed a report, dashboard, or tile, into your web
applications.
Power BI also supports national clouds.
The different national clouds are:
U.S. Government Community Cloud (GCC )
U. S. Military Contractors (DoDCON )
U. S. Military (DoD )
Power BI for Germany cloud
Power BI for China cloud

To get started with this walkthrough, you need a Power BI account. If you don't have an account set up, then
depending on the type of government or country you can choose the right national cloud for you. You can sign up
for a U. S. government Power BI account, a Power BI for Germany cloud account or a Power BI for China cloud
account.

NOTE
Looking to embed a dashboard for your organization instead? See, Integrate a dashboard into an app for your organization.

To integrate a dashboard into a web app, you use the Power BI API, and an Azure Active Directory (AD )
authorization access token to get a dashboard. Then, you load the dashboard using an embed token. The Power
BI API provides programmatic access to specific Power BI resources. For more information, see Power BI REST
API, [Power BI .NET SDK, and the Power BI JavaScript API.
Download the sample
This article shows the code used in the App Owns Data sample on GitHub. To follow along with this walkthrough,
you can download the sample.

Government Community Cloud (GCC ):

NOTE
GCC accounts only support P and EM capacities.

1. Overwrite Cloud.config file with GCCCloud.config content.

2. Update applicationId (Native app applicationId), workspaceId, the user (your master user), and password in
Web.config file.
3. Add the GCC parameters in the web.config file as follows.

<add key="authorityUrl" value="https://login.microsoftonline.net/common/" />

<add key="resourceUrl" value="https://analysis.usgovcloudapi.net/powerbi/api" />
<add key="apiUrl" value="https://api.powerbigov.us/" />
<add key="embedUrlBase" value="https://app.powerbigov.us" />

Military Contractors (DoDCON ):

1. Overwrite Cloud.config file with TBCloud.config content.
2. Update applicationId (Native app applicationId), workspaceId, the user (your master user), and password in
Web.config file.
3. Add the DoDCON parameters in the web.config file as follows.

<add key="authorityUrl" value="https://login.microsoftonlineS.net/common/" />

<add key="resourceUrl" value="https://high.analysis.usgovcloudapi.net/powerbi/api" />
<add key="apiUrl" value="https://api.high.powerbigov.us/" />
<add key="embedUrlBase" value="https://app.high.powerbigov.us" />

Military (DoD ):
1. Overwrite Cloud.config file with PFCloud.config content.
2. Update applicationId (Native app applicationId), workspaceId, the user (your master user), and password in
Web.config file.
3. Add the DoDCON parameters in the web.config file as follows.
 <add key="authorityUrl" value="https://login.microsoftonline.net/common/" />
<add key="resourceUrl" value="https://mil.analysis.usgovcloudapi.net/powerbi/api" />
<add key="apiUrl" value="https://api.mil.powerbigov.us/" />
<add key="embedUrlBase" value="https://app.mil.powerbigov.us" />

Power BI for Germany cloud parameters

1. Overwrite Cloud.config file with Power BI for Germany cloud content.
2. Update applicationId (Native app applicationId), workspaceId, the user (your master user), and password in
Web.config file.
3. Add the Power BI for Germany cloud parameters in the web.config file as follows.

<add key="authorityUrl" value="https://login.microsoftonline.de/common/" />

<add key="resourceUrl" value="https://analysis.cloudapi.de/powerbi/api" />
<add key="apiUrl" value="https://api.powerbi.de/" />
<add key="embedUrlBase" value="https://app.powerbi.de" />

Power BI for China cloud parameters

1. Overwrite Cloud.config file with Power BI for China cloud content.
2. Update applicationId (Native app applicationId), workspaceId, the user (your master user), and password in
Web.config file.
3. Add the Power BI for China cloud parameters in the web.config file as follows.

<add key="authorityUrl" value="https://login.chinacloudapi.cn/common/" />

<add key="resourceUrl" value="https://analysis.chinacloudapi.cn/powerbi/api" />
<add key="apiUrl" value="https://api.powerbi.cn/" />
<add key="embedUrlBase" value="https://app.powerbi.cn" />

Step 1 - register an app in Azure AD

Register your application with Azure AD to make REST API calls. For more information, see Register an Azure AD
app to embed Power BI content. Since there are different national cloud affiliations, there are distinct URLs to
register your application.
Government Community Cloud (GCC ) - https://app.powerbigov.us/apps

Military Contractors (DoDCON ) - https://app.high.powerbigov.us/apps

Military (DoD ) - https://app.mil.powerbigov.us/apps

Power BI for Germany cloud - https://app.powerbi.de/apps

Power BI for China cloud - https://app.powerbi.cn/apps

If you downloaded the Embedding for your customer sample, you would use the applicationId you get, so that
the sample can authenticate to Azure AD. To configure the sample, change the applicationId in the web.config file.

Step 2 - get an access token from Azure AD

Within your application, you need to get an access token, from Azure AD, before you can make calls to the Power
BI REST API. For more information, see Authenticate users and get an Azure AD access token for your Power BI
app. Since there are different national cloud affiliations, there are distinct URLs to get an access token for your
application.
Government Community Cloud (GCC ) - https://login.microsoftonline.com

Military Contractors (DoDCON ) - http://login.microsoftonline.us

Military (DoD ) - https://login.microsoftonline.us

Power BI for Germany cloud - https://login.microsoftonline.de

Power BI for China cloud - https://login.chinacloudapi.cn

You can see examples of these access tokens within each content item task in the Controllers\HomeController.cs
file.

Step 3 - get a content item

To embed your Power BI content, you need to do a couple of things to make sure it embeds correctly. While all of
these steps can be done with the REST API directly, the sample application and the examples here use the .NET
SDK.
Create the Power BI Client with your access token
With your access token, you want to create your Power BI client object, which allows you to interact with the Power
BI APIs. You create your Power BI client object by wrapping the AccessToken with a
Microsoft.Rest.TokenCredentials object.

using Microsoft.IdentityModel.Clients.ActiveDirectory;
using Microsoft.Rest;
using Microsoft.PowerBI.Api.V2;

var tokenCredentials = new TokenCredentials(authenticationResult.AccessToken, "Bearer");

// Create a Power BI Client object. This is used to call the Power BI APIs.
using (var client = new PowerBIClient(new Uri(ApiUrl), tokenCredentials))
{
// Your code to embed items.
}

Get the content item you want to embed

Use the Power BI client object to retrieve a reference to the item you want to embed. You can embed dashboards,
tiles, or reports. Here is an example of how to retrieve the first dashboard, tile, or report from a given workspace.
A sample is available within Controllers\HomeController.cs of the App Owns Data sample.
Reports

using Microsoft.PowerBI.Api.V2;
using Microsoft.PowerBI.Api.V2.Models;

// You need to provide the workspaceId where the dashboard resides.

ODataResponseListReport reports = client.Reports.GetReportsInGroupAsync(workspaceId);

// Get the first report in the group.

Report report = reports.Value.FirstOrDefault();

Dashboards
 using Microsoft.PowerBI.Api.V2;
using Microsoft.PowerBI.Api.V2.Models;

// You need to provide the workspaceId where the dashboard resides.

ODataResponseListDashboard dashboards = client.Dashboards.GetDashboardsInGroup(workspaceId);

// Get the first report in the group.

Dashboard dashboard = dashboards.Value.FirstOrDefault();

Tiles

using Microsoft.PowerBI.Api.V2;
using Microsoft.PowerBI.Api.V2.Models;

// To retrieve the tile, you first need to retrieve the dashboard.

// You need to provide the workspaceId where the dashboard resides.

ODataResponseListDashboard dashboards = client.Dashboards.GetDashboardsInGroup(workspaceId);

// Get the first report in the group.

Dashboard dashboard = dashboards.Value.FirstOrDefault();

// Get a list of tiles from a specific dashboard

ODataResponseListTile tiles = client.Dashboards.GetTilesInGroup(workspaceId, dashboard.Id);

// Get the first tile in the group.

Tile tile = tiles.Value.FirstOrDefault();

Create the embed token

Using the JavaScript API, you can generate an embed token. The embed token is specific to the item you're
embedding. Anytime you embed a piece of Power BI content, you need to create a new embed token for it. For
more information, including which accessLevel to use, see Embed Token.

IMPORTANT
Because embed tokens are intended for developer testing only, the number of embed tokens a Power BI master account can
generate is limited. A capacity must be purchased for production embedding scenarios. There is no limit to embed token
generation when a capacity is purchased.

A sample is available within Controllers\HomeController.cs of the Embedding for your organization sample.
A class is created for EmbedConfig and TileEmbedConfig. A sample is available within
Models\EmbedConfig.cs and Models\TileEmbedConfig.cs.
Reports
 using Microsoft.PowerBI.Api.V2;
using Microsoft.PowerBI.Api.V2.Models;

// Generate Embed Token.

var generateTokenRequestParameters = new GenerateTokenRequest(accessLevel: "view");
EmbedToken tokenResponse = client.Reports.GenerateTokenInGroup(workspaceId, report.Id,
generateTokenRequestParameters);

// Generate Embed Configuration.

var embedConfig = new EmbedConfig()
{
EmbedToken = tokenResponse,
EmbedUrl = report.EmbedUrl,
Id = report.Id
};

Dashboards

using Microsoft.PowerBI.Api.V2;
using Microsoft.PowerBI.Api.V2.Models;

// Generate Embed Token.

var generateTokenRequestParameters = new GenerateTokenRequest(accessLevel: "view");
EmbedToken tokenResponse = client.Dashboards.GenerateTokenInGroup(workspaceId, dashboard.Id,
generateTokenRequestParameters);

// Generate Embed Configuration.

var embedConfig = new EmbedConfig()
{
EmbedToken = tokenResponse,
EmbedUrl = dashboard.EmbedUrl,
Id = dashboard.Id
};

Tiles

using Microsoft.PowerBI.Api.V2;
using Microsoft.PowerBI.Api.V2.Models;

// Generate Embed Token for a tile.

var generateTokenRequestParameters = new GenerateTokenRequest(accessLevel: "view");
EmbedToken tokenResponse = client.Tiles.GenerateTokenInGroup(workspaceId, dashboard.Id, tile.Id,
generateTokenRequestParameters);

// Generate Embed Configuration.

var embedConfig = new TileEmbedConfig()
{
EmbedToken = tokenResponse,
EmbedUrl = tile.EmbedUrl,
Id = tile.Id,
dashboardId = dashboard.Id
};

Step 4 - load an item using JavaScript

You can use JavaScript to load a dashboard into a div element on your web page. The sample uses an
EmbedConfig/TileEmbedConfig model along with views for a dashboard, tile, or report. For a full sample of using
the JavaScript API, you can use the Microsoft Power BI Embedded Sample.
An application sample is available within the Embedding for your organization sample.
Views\Home\EmbedDashboard.cshtml
 <script src="~/scripts/powerbi.js"></script>
<div id="dashboardContainer"></div>
<script>
// Read embed application token from Model
var accessToken = "@Model.EmbedToken.Token";

// Read embed URL from Model

var embedUrl = "@Html.Raw(Model.EmbedUrl)";

// Read dashboard Id from Model

var embedDashboardId = "@Model.Id";

// Get models. models contains enums that can be used.

var models = window['powerbi-client'].models;

// Embed configuration used to describe the what and how to embed.

// This object is used when calling powerbi.embed.
// This also includes settings and options such as filters.
// You can find more information at https://github.com/Microsoft/PowerBI-JavaScript/wiki/Embed-
Configuration-Details.
var config = {
type: 'dashboard',
tokenType: models.TokenType.Embed,
accessToken: accessToken,
embedUrl: embedUrl,
id: embedDashboardId
};

// Get a reference to the embedded dashboard HTML element

var dashboardContainer = $('#dashboardContainer')[0];

// Embed the dashboard and display it within the div container.

var dashboard = powerbi.embed(dashboardContainer, config);
</script>

Views\Home\EmbedTile.cshtml
 <script src="~/scripts/powerbi.js"></script>
<div id="tileContainer"></div>
<script>
// Read embed application token from Model
var accessToken = "@Model.EmbedToken.Token";

// Read embed URL from Model

var embedUrl = "@Html.Raw(Model.EmbedUrl)";

// Read tile Id from Model

var embedTileId = "@Model.Id";

// Read dashboard Id from Model

var embedDashboardId = "@Model.dashboardId";

// Get models. models contains enums that can be used.

var models = window['powerbi-client'].models;

// Embed configuration used to describe the what and how to embed.

// This object is used when calling powerbi.embed.
// This also includes settings and options such as filters.
// You can find more information at https://github.com/Microsoft/PowerBI-JavaScript/wiki/Embed-
Configuration-Details.
var config = {
type: 'tile',
tokenType: models.TokenType.Embed,
accessToken: accessToken,
embedUrl: embedUrl,
id: embedTileId,
dashboardId: embedDashboardId
};

// Get a reference to the embedded tile HTML element

var tileContainer = $('#tileContainer')[0];

// Embed the tile and display it within the div container.

var tile = powerbi.embed(tileContainer, config);
</script>

Views\Home\EmbedReport.cshtml
 <script src="~/scripts/powerbi.js"></script>
<div id="reportContainer"></div>
<script>
// Read embed application token from Model
var accessToken = "@Model.EmbedToken.Token";

// Read embed URL from Model

var embedUrl = "@Html.Raw(Model.EmbedUrl)";

// Read report Id from Model

var embedReportId = "@Model.Id";

// Get models. models contains enums that can be used.

var models = window['powerbi-client'].models;

// Embed configuration used to describe the what and how to embed.

// This object is used when calling powerbi.embed.
// This also includes settings and options such as filters.
// You can find more information at https://github.com/Microsoft/PowerBI-JavaScript/wiki/Embed-
Configuration-Details.
var config = {
type: 'report',
tokenType: models.TokenType.Embed,
accessToken: accessToken,
embedUrl: embedUrl,
id: embedReportId,
permissions: models.Permissions.All,
settings: {
filterPaneEnabled: true,
navContentPaneEnabled: true
}
};

// Get a reference to the embedded report HTML element

var reportContainer = $('#reportContainer')[0];

// Embed the report and display it within the div container.

var report = powerbi.embed(reportContainer, config);
</script>

Next steps
A sample application is available on GitHub for you to review. The above examples are based on that
sample. For more information, see Embedding for your organization sample.
For more information about JavaScript API, reference Power BI JavaScript API.
For more information about for Power BI for Germany cloud, reference Power BI for Germany cloud FAQ
How to migrate Power BI Workspace Collection Workspace Collection content to Power BI
Considerations and limitations
More questions? Try asking the Power BI Community
 Power BI Embedded performance best practices
1/30/2019 • 2 minutes to read • Edit Online

This article provides recommendations for faster rendering of reports, dashboards, and tiles in your application

Embed parameters
Powerbi.embed() method receives few parameters to embed a report, a dashboard, or a tile. These parameters
have performance implications.
Embed URL
Avoid generating the embed URL yourself. Instead, make sure you get the Embed URL by calling the Get reports,
the Get dashboards, or the Get tiles API. We added a new parameter to the URL called config, used for
performance improvements.
Permissions
Provide View permissions if you're not intending to embed a report in Edit mode. This way embed code doesn't
initialize components, which are used for Edit mode.
Filters, bookmarks, and slicers
Usually, report visuals are saved with cached data. The cached data is used to give perceived performance. Reports
render cached data while queries are executed. If filters, bookmarks or slicers are provided, cached data isn't
relevant. Then, the visuals are rendered only after running the visual query.
If you embed reports with the same filters, to avoid passing a list of filters in the load configuration, save the report
with filters already applied.

Preload
Use the preload JavaScript API to improve the end-user performance. Powerbi.preload() downloads javascript, css
files, and other artifacts, which is used later to embed in a report.
Call preload if you're not embedding the report immediately. For example, if you embed a report on a button click,
it’s better to call preload when the previous page loads. Then when the application user clicks the button, the
rendering is faster.

Measure performance
To measure performance, use:
1. Loaded: time until report is initialized (user sees no spinny).
2. Rendered: time until fully report is rendered using actual data. The rendered event is fired each time the report
is re-rendered (that is, after applying filters). To measure a report first, make sure you do the calculations in the
first raised event.
Cached data is rendered when available, but we don’t have an event for this data yet.

Update tools and SDK packages

Keep tools and SDK packages up-to-date.
Always use the latest version of Power BI Desktop.
 Install the latest version of the Power BI client SDK. We continue to release more enhancements, so make
sure to follow up from time to time.
Packages to install:
Npm package: powerbi-client
NuGet package: Microsoft.PowerBI.JavaScript

NOTE
Remember that loading time mainly depends on elements relevant to the report and data itself. Such as number of visuals,
size of data and complexity of the queries and calculated measures. Please follow best practices to improve the report’s
loading time.

Next steps
Power BI report performance best practices
How to troubleshoot Power BI Embedded issues
Power BI Embedded FAQ
 Service principal with Power BI (Preview)
4/2/2019 • 7 minutes to read • Edit Online

With service principal, you can embed Power BI content into an application and use automation with Power
BI using an app-only token. Service principal is beneficial when using Power BI Embedded or when
automating Power BI tasks and processes.
When working with Power BI Embedded, there are advantages when using service principal. A primary
advantage is you don't need a master account (Power BI Pro license that is merely a username and password
to sign in) to authenticate into your application. Service principal uses an application ID and an application
secret to authenticate the application.
When working to automate Power BI tasks, you can also script how to process and manage service principals
to scale.

Application and service principal relationship

To access resources that secure an Azure AD tenant, the entity that requires access represents a security
principal. This action holds true for both users (user principal) and applications (service principal).
The security principal defines the access policy and permissions for users and applications in the Azure AD
tenant. This access policy enables core features such as authentication of users and applications during sign-
in, and authorization during resource access. For more information, reference Application and service
principal in Azure Active Directory (AAD ).
When you register an Azure AD application in the Azure portal, two objects are created in your Azure AD
tenant:
An application object
A service principal object
Consider the application object as the global representation of your application for use across all tenants, and
the service principal object as the local representation for use in a specific tenant.
The application object serves as the template from which common and default properties are derived for use
in creating corresponding service principal objects.
A service principal is required per tenant where the application is used — enabling it to establish an identity
for sign-in and access to resources that are secured by the tenant. A single-tenant application has only one
service principal (in its home tenant), created and consented for use during application registration.

Service principal with Power BI Embedded

With service principal, you can mask your master account information in your application by using an
application ID and an application secret. You no longer need to hard-code a master account into your
application to authenticate.
Since Power BI APIs and Power BI .NET SDK now support calls using service principal, you can use the
Power BI REST APIs with service principal. For example, you can make changes to workspaces such as create
workspaces, add or remove users from workspaces, and import content into workspaces.
You can only use service principal if your Power BI artifacts and resources are stored in the new Power BI
workspace.
Service principal vs. master account
There are differences between using a service principal and a standard master account (Power BI Pro license)
for authentication. The below table highlights some significant differences.

MASTER USER ACCOUNT SERVICE PRINCIPAL

FUNCTION (POWER BI PRO LICENSE) (APP-ONLY TOKEN)

Can sign in to the Power BI service Yes No

Enabled in the Power BI Admin portal No Yes

Works with app workspaces (v1) Yes No

Works with the new app workspaces Yes Yes

(v2)

Needs to be a workspace admin if Yes Yes

used with Power BI Embedded

Can use Power BI REST APIs Yes Yes

Needs a global admin to create Yes No

Can install and manage an On- Yes No

premises data gateway

Get started with a service principal

Different from the traditional use of a master account, using the service principal (app-only token) requires a
few different pieces to set up. To get started with service principal (app-only token), you need to set up the
right environment.
1. Register a server-side web application in Azure Active Directory (AAD ) to use with Power BI. After
registering an application you can capture an application ID, an application secret, and the service
principal object ID to access your Power BI content. You can create a service principal with PowerShell.
Below is a sample script to create a new Azure Active Directory application.

# The app id - $app.appid

# The service principal object id - $sp.objectId
# The app key - $key.value

# Sign in as a user that is allowed to create an app.

Connect-AzureAD

# Create a new AAD web application

$app = New-AzureADApplication -DisplayName "testApp1" -Homepage "https://localhost:44322" -
ReplyUrls "https://localhost:44322"

# Creates a service principal

$sp = New-AzureADServicePrincipal -AppId $app.AppId

# Get the service principal key.

$key = New-AzureADServicePrincipalPasswordCredential -ObjectId $sp.ObjectId
 IMPORTANT
Once you enable service principal to be used with Power BI, the application's AD permissions don't take effect
anymore. The application's permissions are then managed through the Power BI admin portal.

2. Create a security group in Azure Active Directory (AAD ), and add the application you created to that
security group. You can create an AAD security group with PowerShell.
Below is a sample script to create a new security group and add an application to that security group.

# Required to sign in as a tenant admin

Connect-AzureAD

# Create an AAD security group

$group = New-AzureADGroup -DisplayName <Group display name> -SecurityEnabled $true -MailEnabled
$false -MailNickName notSet

# Add the service principal to the group

Add-AzureADGroupMember -ObjectId $($group.ObjectId) -RefObjectId $($sp.ObjectId)

3. As a Power BI admin, you need to enable service principal in the Developer settings in the Power BI
admin portal. Add the security group that you created in Azure AD to the Specific security group
section in the Developer settings.

IMPORTANT
Service principals have access to any tenant settings that are enabled for the entire organization or enabled for
security groups that have service principals as a part of the group. To restrict service principal access to specific
tenant settings, allow access only to specific security groups, or create a dedicated security group for service
principals and exclude it.

4. Set up your Power BI environment.

5. Add the service principal as an admin to the new workspace you created. You can manage this task
 through the APIs or with the Power BI service.

6. Now choose to embed your content within a sample application, or within your own application.
Embed content using the sample application
Embed content within your application
7. Now you're ready to move to production.

Migrate to service principal

You can migrate to use service principal if you're currently using a master account with Power BI or with
Power BI Embedded.
Complete the first three steps in section Get started with a service principal , and once complete, follow the
information below.
If you're already using the new workspaces in Power BI, then add the service principal as an admin to the
workspaces with your Power BI artifacts. However, if you're using the traditional workspaces, copy or move
your Power BI artifacts and resources into the new workspaces, and then add the service principal as an
admin to those workspaces.
There's no UI feature to move Power BI artifacts and resources from one workspace to another, so you need
to use APIs to accomplish this task. When using the APIs with service principal, you need the service principal
object ID.
How to get the service principal object ID
To assign a service principal to a new app workspace, you use the Power BI REST APIs. To reference a service
principal for operations or to make changes you use the service principal object ID — for example,
applying a service principal as an admin to a workspace.
Below are steps to get the service principal object ID from the Azure portal.
1. Create a new App registration in the Azure portal.
2. Then under Managed application in local directory, select the name of the application you created.
 NOTE
The object Id in the image above is not the one used with service principal.

3. Select Properties to see the Object ID.

Below is a sample script to retrieve the service principal object ID with PowerShell.

Get-AzureADServicePrincipal -Filter "DisplayName eq '<application name>'"

Considerations and limitations

Service principal only works with new app workspaces.
My Workspace isn't supported when using service principal.
Dedicated Premium capacity is required when moving to production.
You can't sign into the Power BI portal using service principal.
Power BI admin rights are required to enable service principal in developer settings within the Power BI
admin portal.
You can't install or manage an on-premises data gateway using service principal.
Embed for your organization applications are unable to use service principal.
Dataflows management is not supported.
Service principal does not support admin APIs.

Next steps
Register an app
Power BI Embedded for your customers
Application and service principal objects in Azure Active Directory
 Row-level security with Power BI Embedded
3/28/2019 • 13 minutes to read • Edit Online

Row-level security (RLS ) can be used to restrict user access to data within dashboards, tiles, reports, and
datasets. Different users can work with those same artifacts all while seeing different data. Embedding supports
RLS.
If you're embedding for non-Power BI users (app owns data), which is typically an ISV scenario, then this article is
for you! Configure the embed token to account for the user and role.
If you're embedding to Power BI users (user owns data), within your organization, RLS works the same as it does
within the Power BI service directly. There's nothing more you need to do in your application. For more
information, see Row -Level security (RLS ) with Power BI.

To take advantage of RLS, it’s important you understand three main concepts; Users, Roles, and Rules. Let’s take a
closer look at each:
Users – End users viewing the artifact (dashboard, tile, report, or dataset). In Power BI Embedded, users are
identified by the username property in an embed token.
Roles – Users belong to roles. A role is a container for rules and can be named something like Sales Manager or
Sales Rep. You create roles within Power BI Desktop. For more information, see Row -level security (RLS ) with
Power BI Desktop.
Rules – Roles have rules, and those rules are the actual filters that are going to be applied to the data. The rules
could be as simple as “Country = USA” or something much more dynamic. For the rest of this article, there's an
example of authoring RLS, and then consuming that within an embedded application. Our example uses the Retail
Analysis Sample PBIX file.

Adding roles with Power BI Desktop

Our Retail Analysis sample shows sales for all the stores in a retail chain. Without RLS, no matter which district
manager signs in and views the report, they all see the same data. Senior management has determined each
district manager should only see the sales for the stores they manage. Using RLS allows Senior management to
restrict data based on a district manager.
RLS is authored in Power BI Desktop. When the dataset and report are opened, we can switch to diagram view to
see the schema:

Here are a few things to notice with this schema:

All measures, like Total Sales, are stored in the Sales fact table.
There are four additional related dimension tables: Item, Time, Store, and District.
The arrows on the relationship lines indicate which way filters can flow from one table to another. For
example, if a filter is placed on Time[Date], in the current schema it would only filter down values in the
Sales table. No other tables are affected by this filter since all the arrows on the relationship lines point to
the sales table and not away.
The District table indicates who the manager is for each district:

Based on this schema, if we apply a filter to the District Manager column in the District table, and if that filter
matches the user viewing the report, that filter down the Store and Sales tables to show data for that district
manager.
Here's how:
1. On the Modeling tab, select Manage Roles.
2. Create a new role called Manager.

3. In the District table, enter this DAX expression: [District Manager] = USERNAME ().

4. To make sure the rules are working, on the Modeling tab, select View as Roles, and then select both the
Manager role you created, along with Other users. Enter AndrewMa for the user.

The reports show data as if you're signed in as AndrewMa.

Applying the filter, the way we did here, filters down all records in the District, Store, and Sales tables. However,
because of the filter direction on the relationships between Sales and Time, Sales and Item, and Item and Time
tables aren't filtered down. To learn more about bidirectional cross-filtering, download the Bidirectional cross-
filtering in SQL Server Analysis Services 2016 and Power BI Desktop whitepaper.

Applying user and role to an embed token

Now that you have your Power BI Desktop roles configured, there's some work needed in your application to take
advantage of the roles.
Users are authenticated and authorized by your application and embed tokens are used to grant that user access
to a specific Power BI Embedded report. Power BI Embedded doesn’t have any specific information on who your
user is. For RLS to work, you need to pass some additional context as part of your embed token in the form of
identities. You can pass the identities by using the Embed Token API.
The API accepts a list of identities with indication of the relevant datasets. For RLS to work, you need to pass the
below pieces as part of the identity.
username (mandatory) – A string that can be used to help identify the user when applying RLS rules. Only a
single user can be listed. Your username can be created with ASCII characters.
roles (mandatory) – A string containing the roles to select when applying Row Level Security rules. If passing
more than one role, they should be passed as a string array.
dataset (mandatory) – The dataset that is applicable for the artifact you're embedding.
You can create the embed token by using the GenerateTokenInGroup method on PowerBIClient.Reports.
For example, you could change the PowerBIEmbedded_AppOwnsData sample. Services\EmbedService.cs line 76
and 77 could be updated from:

// Generate Embed Token.

var generateTokenRequestParameters = new GenerateTokenRequest(accessLevel: "view");

var tokenResponse = await client.Reports.GenerateTokenInGroupAsync(GroupId, report.Id,

generateTokenRequestParameters);

to

var generateTokenRequestParameters = new GenerateTokenRequest("View", null, identities: new

List<EffectiveIdentity> { new EffectiveIdentity(username: "username", roles: new List<string> { "roleA",
"roleB" }, datasets: new List<string> { "datasetId" }) });

var tokenResponse = await client.Reports.GenerateTokenInGroupAsync("groupId", "reportId",

generateTokenRequestParameters);

If you're calling the REST API, the updated API now accepts an additional JSON array, named identities,
containing a username, list of string roles and list of string datasets.
Use the following code below as an example:

{
"accessLevel": "View",
"identities": [
{
"username": "EffectiveIdentity",
"roles": [ "Role1", "Role2" ],
"datasets": [ "fe0a1aeb-f6a4-4b27-a2d3-b5df3bb28bdc" ]
}
]
}

Now, with all the pieces together, when someone logs into your application to view this artifact, they’ll only see the
data that they're allowed to see, as defined by our row -level security.

Working with Analysis Services live connections

Row -level security can be used with Analysis Services live connections for on-premises servers. There are a few
specific concepts that you should understand when using this type of connection.
The effective identity that is provided for the username property must be a Windows user with permissions on the
Analysis Services server.
On-premises data gateway configuration
An On-premises data gateway is used when working with Analysis Services live connections. When generating an
embed token, with an identity listed, the master account needs to be listed as an admin of the gateway. If the
master account isn't listed, the row -level security isn't applied to the property of the data. A non-admin of the
gateway can provide roles, but must specify its own username for the effective identity.
Use of roles
Roles can be provided with the identity in an embed token. If no role is provided, the username that was provided
can be used to resolve the associated roles.
Using the CustomData feature
The CustomData feature only works for models that lie in Azure Analysis Services, and it only works in
Connect live mode. Unlike users and roles, the Custom data feature can't be set inside a .pbix file. When
generating a token with the Custom data feature, you need to have a username.
The CustomData feature allows you to add a Row filter when viewing Power BI data in your application when
using Azure Analysis Services as your data source (viewing Power BI data connected to Azure Analysis Services
in your application).
The CustomData feature allows passing free text (string) using the CustomData connection string property.
Analysis Services use this value via the CUSTOMDATA () function.
The only way to have dynamic RLS (which uses dynamic values for filter evaluation) in Azure Analysis Services,
is using the CUSTOMDATA () function.
You can use it inside the role DAX query, and you can use it without any role in a measure DAX query.
CustomData feature is part of our token generation functionality for the following artifacts: dashboard, report, and
tile. Dashboards can have multiple CustomData identities (one per tile/model).
CustomData SDK Additions
The CustomData string property was added to our effective identity in the token generation scenario.

[JsonProperty(PropertyName = "customData")]
public string CustomData { get; set; }

The identity can be created with custom data using the following call:

public EffectiveIdentity(string username, IList<string> datasets, IList<string> roles = null, string

customData = null);

CustomData SDK Usage

If you're calling the REST API, you can add custom data inside each identity, for example:

{
"accessLevel": "View",
"identities": [
{
"username": "EffectiveIdentity",
"roles": [ "Role1", "Role2" ],
"customData": "MyCustomData",
"datasets": [ "fe0a1aeb-f6a4-4b27-a2d3-b5df3bb28bdc" ]
}
]
}

Here are the steps to begin setting up the CustomData() feature with your Power BI Embedded application.
1. Create your Azure Analysis Services database. Then sign in to your Azure Analysis Services server via SQL
Server Management Studio.
2. Create a Role in the Analysis Services server.

3. Set your General settings. Here you give the Role Name and set the database permissions to Read only.
4. Set the Membership settings. Here you add te users that are affected by this role.
5. Set your Row filters DAX query using the CUSTOMDATA () function.
6. Build a PBI report and publish it to a workspace with dedicated capacity.

7. Use the Power BI APIs to use the CustomData feature in your application. When generating a token with
the Custom data feature, you need to have a username. The username must be equal to the UPN of the
master user. The master user must be a member of the role(s) you created. If no role(s) are specified, then
all the roles the master user is a member of are used for RLS evaluation.
 When working with a service principal, you also need to do the above steps in place of using a master
account. When generating embed token, use the service principal object ID as the username.

NOTE
When you're ready to deploy your application to production, the master user account field or option should not be
visible to the end user.

View the code to add the CustomData feature.

8. Now you can view the report in your application before applying the Custom data value(s) to see all the
data your report holds.

Then apply the Custom data value(s) to see how the report displays a different set of data.
Using RLS vs. JavaScript filters
When deciding on filtering your data in a report, you can use row-level security (RLS ) or JavaScript filters.
Row -level security is a feature that filters data at the data model level. Your backend data source controls your RLS
settings. Based on your data model, the embed token generation sets the username and the roles for the session.
It cannot be overridden, removed, or controlled by the client-side code and that’s why it’s considered secure. We
recommend using RLS for filtering data securely. You can filter data with RLS by using one of the options below.
Configuring roles in a Power BI report.
Configuring roles at the data source level (Analysis Services live connection only).
Programmatically with an Embed Token using EffectiveIdentity . When using an embed token, the actual
filter passes through the embed token for a specific session.
JavaScript filters are used to allow the user to consume reduced, scoped, or a filtered view of the data. However,
the user still has access to the model schema tables, columns, and measures and potentially can access any data
there. Restricted access to the data can only be applied with RLS and not through client-side filtering APIs.

Token-based Identity with Azure SQL Database (Preview)

The token-based identity allows you to specify the effective identity for an embed token using Azure Active
Directory (AAD ) access token for an Azure SQL Database.
Customers that hold their data in Azure SQL Database can now enjoy a new capability to manage users and
their access to data in Azure SQL when integrating with Power BI Embedded.
When you're generating the embed token, you can specify the effective identity of a user in Azure SQL. You can
specify the effective identity of a user by passing the AAD access token to the server. The access token is used to
pull only the relevant data for that user from Azure SQL, for that specific session.
It can be used to manage each user’s view in Azure SQL or to sign in to Azure SQL as a specific customer in a
multi-tenant DB. It can also apply row -level security on that session in Azure SQL and retrieve only the relevant
data for that session, removing the need to manage RLS in Power BI.
Such effective identity issues apply to RLS rules directly on the Azure SQL Server. Power BI Embedded uses the
provided access token when querying data from the Azure SQL Server. The UPN of the user (for which the access
token was provided) is accessible as a result of the USER_NAME () SQL function.
The token-based identity only works for DirectQuery models on dedicated capacity - connected to an Azure SQL
Database, which is configured to allow AAD authentication (learn more about AAD authentication for Azure SQL
Database). The dataset’s data source must be configured to use end users’ OAuth2 credentials, to use a token-
based identity.

Token-based Identity SDK additions

The identity blob property was added to our effective identity in the token generation scenario.

[JsonProperty(PropertyName = "identityBlob")]
public IdentityBlob IdentityBlob { get; set; }

The IdentityBlob type is a simple JSON structure holding a value string property

[JsonProperty(PropertyName = "value")]
public string value { get; set; }

The EffectiveIdentity can be created with identity blob using the following call:

public EffectiveIdentity(string username, IList<string> datasets, IList<string> roles = null, string

customData = null, IdentityBlob identityBlob = null);
Identity blob can be created using the following call.

public IdentityBlob(string value);

Token-based Identity REST API Usage

If you're calling the REST API, you can add identity blob inside each identity.

{
"accessLevel": "View",
"identities": [
{
"datasets": ["fe0a1aeb-f6a4-4b27-a2d3-b5df3bb28bdc"],
“identityBlob”: {
“value”: “eyJ0eXAiOiJKV1QiLCJh….”
}
}
]
}

The value provided in the identity blob should be a valid access token to Azure SQL Server (with a resource URL
of (https://database.windows.net/).

NOTE
To be able to create an access token for Azure SQL, the application must have Access Azure SQL DB and Data Warehouse
delegated permission to Azure SQL Database API on AAD app registration configuration in the Azure portal.

On-premises data gateway with service principal (Preview)

Customers that configure row -level security (RLS ) using an SQL Server Analysis Services (SSAS ) on-premises
live connection data source can enjoy the new service principal capability to manage users and their access to data
in SSAS when integrating with Power BI Embedded.
Using Power BI REST APIs, allows you to specify the effective identity for SSAS on-premises live connections for
an embed token using a service principal object.
Until now, to be able to specify the effective identity for SSAS on-premises live connection, the master user
generating the embed token had to be a gateway admin. Now, instead of requiring the user to be gateway admin,
the gateway admin can give the user dedicated permission to that data source, that allows the user to override the
effective identity when generating the embed token. This new ability enables embedding with service principal for
a live SSAS connection.
To enable this scenario, the gateway admin uses the Add Datasource User REST API to give the service principal
the ReadOverrideEffectiveIdentity permission for Power BI Embedded.
You can't set this permission using the admin portal. This permission is only set with the API. In the admin portal,
you see an indication for users and SPNs with such permissions.

Considerations and limitations

Assignment of users to roles within the Power BI service doesn't affect RLS when using an embed token.
While the Power BI service doesn't apply RLS setting to admins or members with edit permissions, when you
supply an identity with an embed token, it applies to the data.
Analysis Services live connections are supported for on-premises servers.
Azure Analysis Services live connections support filtering by roles. Dynamic filtering can be done using
CustomData.
If the underlying dataset doesn’t require RLS, the GenerateToken request must not contain an effective
identity.
If the underlying dataset is a cloud model (cached model or DirectQuery), the effective identity must include at
least one role, otherwise role assignment doesn't occur.
A list of identities enables multiple identity tokens for dashboard embedding. For all others artifacts, the list
contains a single identity.
Token-based Identity limitations (Preview)
This capability restricts use with Power BI Premium only.
This capability doesn’t work with SQL Server on-premises.
This capability doesn't work with multi-geo.
More questions? Try asking the Power BI Community
 Manage multi-tenancy with Power BI embedded
analytics
2/28/2019 • 18 minutes to read • Edit Online

When designing a multi-tenant SaaS application, you must carefully choose the tenancy model that best fits the
needs of your SaaS application. This process is also valid for Power BI as an embedded analytics part of your SaaS
application. A tenancy model determines how each tenant’s data is mapped and managed within Power BI and the
storage account. Your tenancy model impacts application design and management. Switching to a different model
later may become costly and disruptive.
With Power BI Embedded, there are two main fundamental approaches to maintaining separation between tenants.
1. Workspace-based isolation - creating a separate Power BI Workspace per tenant.
2. Row-level security-based isolation - where the underlying data is used to control and manage access to data
per user or group.
This article describes the different approaches and analyzes them according to several evaluation criteria.

Concepts and terminology

AAD - Azure Active Directory.
AAD application - An application identity in AAD. An AAD application is required for authentication.
SaaS application (software-as-a-service) - A system implemented by an enterprise or ISV that is usually an
online service. Its also related software systems for serving multiple customer tenants (organizations). For this
article, the SaaS application uses Power BI Embedded to serve analytics to its different tenants. Power BI
Embedded can also work for all types of applications when they have an online connection.
Tenant – A single customer (organization) that uses the SaaS application and any resources or data that the
customer brings to the SaaS application.
Power BI - The Power BI cloud service that serves as a platform for Power BI Embedded.
Power BI tenant - Is a set of Power BI resources associated with a single AAD tenant.
Power BI workspace - A container for content in Power BI.
Power BI artifacts – There are several Power BI artifacts in Power BI workspaces such as dashboards, reports,
datasets, and dataflows.
Power BI Embedded - A set of public APIs that allow developers to build applications that manage Power BI
content and embed Power BI elements.
Row-level security (RLS ) - Gives the ability to control user access to the data for individual rows in a table. You
can implement row -level security at the data source level or in the Power BI semantic model.
Master user - The identity that represents the SaaS application in Power BI and that the SaaS application uses
when calling Power BI APIs. Needs to be an AAD user with a Power BI Pro license.
AAD Application user (service principal) - The identity that represents the SaaS application in Power BI and
that the SaaS application uses when calling Power BI APIs. Needs to be an AAD web application. Can replace the
use of a master user to authenticate with Power BI.
Capacity - A set of resources dedicated to running the Power BI service. Power BI Premium capacities Intended
for enterprise companies using Power BI internally, while Power BI Embedded capacities intend for application
developers to develop SaaS applications for third parties.
Power BI Pro license - A user-based license, which grants rights to publish content to app workspaces, consume
apps without Premium capacity, share dashboards, and subscribe to dashboards and reports.
Data connectivity modes - Connecting data sources to Power BI that can be done in different modes:
Import - which is the most common way to get data.
DirectQuery - connect directly to the data in its source repository.
Live connection - another mode that connects directly to Analysis Services data (both Azure and on-premises).

Evaluation criteria
The optimal choice for the right tenancy model for your SaaS application varies according to specific business and
technical requirements, data architecture and more. Deep understanding of these requirements along with
available tenancy model options and trade-offs can help define robust, performant, cost-effective, and scalable
architecture for your SaaS application.
The following are a set of areas to consider when choosing between the different tenancy models.
Data architecture
Usually, developers building applications with Power BI Embedded already have a single or multi-tenant database.
It's easier to use a tenancy model for Power BI Embedded which is similar to the tenancy model of the database. If
the database tenancy model hasn’t been defined yet, you may want to consider other aspects before deciding on
your data architecture.
Data Isolation
How sensitive is the data being stored? What level of isolation do you need separating different customer tenants?
The answer might vary across different industries or specific customers that have certain requirements.
Scalability
To find the best solution, define the scale you reach in the foreseeable future. Remember that a solution that might
be suitable now might not suffice when usage and data scale up. When analyzing scalability, consider the following
list:
Number of tenants (customers).
Number of reports, dashboards, and datasets for each tenant.
Size of data on each dataset and frequency of refreshes.
Number of users.
Number of concurrent users in peak times.
Some SaaS applications might have a low number of customers and low usage, but large amounts of data. Others
might have many customers and high usage, but a small amount of data and reports for each customer. High
numbers in any of these situations can impact future costs and operational complexity.
Automation & operational complexity
Identify frequently occurring processes that need automation.
What is the frequency of onboarding new tenants? What actions are needed to fully onboard each one?
What is the release cadence for new or updated Power BI content, that needs to be deployed?
How many row -level security roles are defined for each tenant?
Identifying these processes and how you address them can help you understand the operational complexity
involved in maintaining each model.
Data Residency Requirements and the need to support multiple geographies
Power BI Embedded supports multi-geo deployment (preview feature). Multi-Geo enables Power BI Embedded
resources to be deployed in different regions with specific content assigned to reside in specific regions. This
feature can be used across all models, but can have an impact on the amount of content to manage and cost.
Currently multi-geo is designed for meeting data residency requirements and doesn't improve performance by
moving data closer to consumers.
Cost
Power BI Embedded has a resource-based purchase model, like Power BI Premium. You purchase one or more
capacities with fixed computing power and memory. This capacity is the main cost item when working with Power
BI Embedded. There's no limit on the number of users using the capacity. The only limit is the performance of the
capacity. A Power BI Pro license is required for each master user, or specific users that need to access the Power BI
portal.
We recommend testing and measuring the expected load on your capacity by simulating live environment and
usage and run load testing on the capacity. You can measure the load and performance with the various Metrics
available in the Azure capacity or Premium capacity metrics app.
Content customization and authoring
There are two approaches to SaaS applications that give users the ability to edit and create reports or upload data
into the service as part of the flow:
Edit/Create mode in an embedded iFrame - The user gets a view of the report or a new blank canvas inside
the SaaS application. This way they can use the Power BI toolbar to create content based on a dataset in the
workspace. We recommend this option since it’s in the user’s context in a familiar environment. It’s easier to
get started working and editing, and the user creates a report attached to an existing dataset.
Use Power BI Desktop to create content and upload it through the SaaS application UI to the workspace. In
this approach, users have more tools to work with using the Power BI Desktop. However, we do not
recommend this approach since users need to be familiar with an additional tool outside of the SaaS
application context. Uploading a PBIX file means the user is adding an additional dataset, that might be a
duplicate of datasets already in the workspace.

Power BI workspace-based isolation

With Power BI workspace-based isolation, the SaaS application supports multiple tenants from a single Power BI
tenant. Workspace-based isolation contains all the Power BI content that different tenants use. The separation of
tenants is done at the Power BI workspace level, by creating multiple workspaces. Each workspace contains the
relevant datasets, reports, and dashboards for that tenant. Also, each workspace is connected only to that tenant’s
data. If you need additional isolation, you can create a master user or a service principal for each workspace and its
content.
Data architecture
There are two main approaches to manage tenant’s data.
A separate database per tenant
A single multi-tenant database
If the SaaS application storage is keeping a separate database per tenant, then the natural choice is to use single-
tenant datasets in Power BI with the connection string for each dataset pointing to the matching database.
If the SaaS application storage is using a multi-tenancy database for all tenants, it’s easy to separate tenants by
workspace. You can configure the database connection for the Power BI dataset with a parameterized database
query that only retrieves the relevant tenant’s data. You can update the connection using the Power BI Desktop or
using the API with parameters on the query.
Data isolation
Data in this tenancy model is separated at the workspace level. A simple mapping between a workspace and a
tenant prevents users from one tenant seeing content from another tenant. Using a single master user demands
you to have access to all the different workspaces. The configuration of which data to show an end user is defined
during the generation of the embed token, a backend-only process which end users can’t see, or change.
To add additional isolation, an application developer can define a master user or an application per workspace
rather than a single master user or application with access to multiple workspaces. This way, you can ensure that
any human error or credential leak does not cause multiple customers' data to be exposed.
Scalability
One advantage of this model is that separating the data into multiple datasets for each tenant overcomes the size
limits of a single dataset (currently 10 GB in a capacity). When the capacity is overloaded, it can evict unused
datasets to free memory for active datasets. This task isn't possible with a single large dataset. Using multiple
datasets, it is also possible to separate tenants into multiple Power BI capacities if needed.
Despite these advantages, one must consider the scale that the SaaS application can reach in the future. For
example, one might reach limitations around the number of artifacts one can manage. See deployment limitations
later in this article for more details. The capacity SKU used introduces a limit on the size of memory that datasets
need to fit in, how many refreshes can run at the same time and the maximum frequency of data refreshes. It's
recommended to test when managing hundreds or thousands of datasets. It is also recommended to consider the
average and peak volume of usage, as well as any specific tenants with large datasets, or different usage patterns,
that are managed differently than other tenants.
Automation & operational complexity
With Power BI workspace-based isolation, an application developer might need to manage hundreds or thousands
of artifacts. It’s essential to define the processes that frequently happen in your application lifecycle management,
and ensure you have the right set of tools to perform these operations at scale in this tenancy model. Some
example operations include:
Adding a new tenant (customer)
Updating a report or dashboard for some or all the tenants
Updating the dataset schema for some or all the tenants
Unplanned customizations for specific tenants
Frequency of dataset refreshes
For example, creating a workspace for a new tenant is a common task, which needs automation. With the Power BI
REST API, you can achieve full automation when creating workspaces.
Multi-Geo needs
Multi-geo involves purchasing capacity in the desired regions and assigning a workspace to that capacity. If you
need to support different tenants in different regions, you need to assign the tenant’s workspace to a capacity in the
desired region. This task is a simple operation and one where the cost is not more than having all workspaces in
the same capacity. However, if you have tenants that need data resident in multiple regions, all artifacts in the
workspace need to be duplicated in each regional capacity, increasing both cost and management complexity.
Cost
Application developers using Power BI Embedded need to purchase Power BI Embedded capacity to go to
production. It’s important to understand the impact of workspace-based isolation model and their effect on
capacities.
The workspace-based isolation model sits well with capacities for the following reasons:
The smallest object you can independently assign to a capacity is a workspace that is, you can’t assign a
report, for example), so by separating tenants by workspaces, you get full flexibility in managing each tenant
and its performance needs, and optimizing capacity utilization by scaling up/down. For example, large and
essential tenants with high volume and volatility can be managed in a separate capacity to ensure a
consistent service level, while grouping smaller tenants in another capacity to optimize costs.
Separating workspaces also means separating datasets between tenants so that data models can be in
smaller chunks, rather than in a single large dataset. This task allows the capacity to manage memory usage
better, evicting small, and unused datasets when not needed, while keeping users satisfied with the
performance.
Application developers need to consider the limit on the number of parallel refreshes, as refresh processes might
need extra capacity when you have multiple datasets.
Content customization and authoring
For the primary use cases of content creation, the application developer needs to carefully consider which tenants
can have editing capabilities, and how many users in each tenant can edit. Permitting multiple users in each tenant
to edit can result in many contents being generated, that can reach a dataset limitation such as the number of
reports per dataset, or the number of datasets in a workspace. If you give users this capability, we recommend
monitoring the content generation closely and scale up as needed. For the same reasons, we don’t recommend
using this capability for content personalization, where each user can make small changes to a report and save it
for themselves. If the SaaS application allows content personalization, consider introducing and communicating
workspace retention policies for user-specific content to facilitate the flow of content deletion when end users
move to a new position, leaving the company or not using the platform anymore.
Row-level security-based isolation
With row -level security-based isolation, the SaaS application uses a single workspace to host multiple tenants. It
means each Power BI artifact report, dashboard, & dataset, is created once all tenants use it. Data separation
between tenants is accomplished using row -level security on the multi-tenant dataset. When end users log into the
SaaS application and open content, an Embed token is generated for that user’s session, with the roles and filters
that ensure the user only sees the data they are permitted to see. If users from the same tenant are not permitted to
view the same data, the application developer needs to implement hierarchical roles both between tenants and
within the same tenant.

Data architecture
Implementing row -level security-based isolation is most comfortable when all tenants’ data is stored in a single
data warehouse. In this case, the application developer can pass only the relevant data from the data warehouse
into the Power BI dataset, either via Direct Query or data import. If data in the database is separated per tenant, it
needs to be combined into a single dataset, which results in a lower degree of separation between tenants that
existed in the database.
Data isolation
With row -level security-based isolation, data separation is accomplished using row -level security definitions on the
dataset, which means all the data coexist. This form of data separation is more susceptible to data leakage through
developer error. Even though row -level security is done on the backend and secured from an end user, if the data is
highly sensitive or customers are asking for data separation, it might be better to use workspace-based isolation.
Scalability
With row -level security-based isolation, the data needs to fit within the dataset size limit, which is currently 10 GB.
With the introduction of incremental refresh and the upcoming release of an XMLA endpoint for Power BI
datasets, the dataset size limit is expected to increase significantly. However, the data still needs to fit into the
capacity’s memory, with enough remaining memory for data refreshes to run. Large-scale deployments need a
large capacity to avoid users experiencing issues due to memory exceeding the limits of the current capacity.
Alternative ways to handle scale include using aggregations or connecting to the data source directly using
DirectQuery or Live connection, rather than caching all the data in the Power BI capacity.
Automation & operational complexity
Managing artifacts is far more comfortable using row -level security-based isolation than with workspace-based
isolation as there is only one version of an artifact for each environment (dev/test/production), instead of a version
per tenant. At a large scale, managing artifacts means managing and updating tens of artifacts, rather than
thousands to ten-thousands.
Power BI doesn’t yet have an API to modify or create RLS roles and rules. Adding or changing roles can only be
done manually in the Power BI Desktop. If an RLS hierarchy needs to be applied, it can be complicated and error-
prone to manage if you don't plan it carefully.
If the application developer needs to manage many roles and role definitions that need to be created or updated
frequently, row -level security-based isolation isn't scalable, from a manageability perspective.
Another operational complexity is the need to closely monitor memory utilization and build a robust mechanism of
alerts and scaling to ensure users get a smooth experience.
Multi-Geo needs
Since all the data is stored in a single dataset, it is challenging to meet data residency requirements that require
certain data to be bound to specific locations. It can also significantly increase the cost of using multiple regions as
all the data is replicated and stored in each region. If only a limited number of tenants need different geographies,
you can keep only those tenants’ data in a different region, using the workspace-based isolation model described
above.
Cost
The primary cost driver with row -level security-based isolation is the memory footprint of the dataset. You need
enough capacity to store the dataset and keep some additional memory buffer for any peaks in memory demand.
One way to mitigate this situation is to store the data in a SQL Server database or SQL Server Analysis Services
cube and using Direct Query or a Live connection to retrieve the data from the data source in real time. This
approach increases the cost of the data sources, but reduces the need for large capacity because of memory needs,
hence reducing the cost of Power BI capacity.
Content customization and authoring
As end users edit or create reports, they can use the production multi-tenant dataset. For that reason, we advise
only using the embedded iFrame option to edit or create reports, as it relies on the same dataset, with row -level
security applied. Having users uploading PBIX files with additional datasets can be costly and difficult to manage
with row -level security-based isolation. Also, when users generate new content that is in the same workspace, you
need to make sure the production workspace doesn't hit its limits and build a robust mechanism to distinguish
which content is connected to which tenant.

Summary comparison of the different approaches

IMPORTANT
The following analysis is based on the current state of the product. As we are releasing new features on a monthly cadence,
we continue to provide new capabilities and features that answer existing limitations and weak spots. Make sure to check our
monthly blog posts to see what’s new and come back to this article to see how new features affect the tenancy model
recommendation.

ROW-LEVEL SECURITY-
EVALUATION CRITERIA WORKSPACE-BASED BASED

Data architecture Easiest when there's a Easiest when all the

separate database per data for all tenants
tenant are in a single data
warehouse
 ROW-LEVEL SECURITY-
EVALUATION CRITERIA WORKSPACE-BASED BASED

Data isolation Good. Each tenant Moderate. All data is

has a dedicated in the same shared
dataset. dataset but managed
through access-
control.

Scalability Medium. Breaking the Lowest. Constrained

data into multiple by dataset limits.
datasets enables
optimization.

Multi-Geo needs Good fit when most Not recommended.

tenants are only in Needs to keep the
one region. entire dataset stored
in multiple regions.

Automation & Good automation for Easy to manage

operational the individual tenant. Power BI artifacts but
complexity Complex to manage complex to manage
many artifacts at RLS at scale.
scale.

Cost Low-medium. Can Medium- high if using

optimize utilization to Import mode. Low-
reduce cost-per- medium if using
tenant. Might Direct Query mode.
increase when
frequent refreshes are
needed.

Content Good fit. Might hit Content generation in

customization and limitations at large embedded iFrame
authoring scale. only

Deployment considerations and limitations

Power BI Artifact limits:
The number of workspaces V1 (groups) that a single user/application can be a member/admin of is 250.
The number of workspaces V2 (folders) that a single user/application can be a member/admin of is 1000.
The number of datasets in a single workspace is 1000.
The number of reports/dashboards connected to a single dataset is 1000.
THe dataset memory size limit to upload a .pbix file is 10 GB.
Power BI Capacity considerations and limitations:
Each capacity can only use its allocated memory and V -cores, according to the SKU purchased.
For the recommended dataset size for each SKU, reference Premium large datasets.
The max dataset size in a dedicated capacity is 10 GB.
The number of scheduled refreshes for an import mode dataset in a day is 48.
The time between scheduled refreshes for an import mode dataset is 30 minutes.
For the number of refreshes that can run concurrently on a capacity, reference resource management and
optimization.
 The average time of scaling a capacity is between 1-2 minutes. During that time, the capacity isn't available. We
recommend using a scale-out approach to avoid downtime.

Next steps
Embedded analytics with Power BI
Power BI Embedded
Power BI Premium
Row -level security
 Diagnostic logging for Power BI Embedded in Azure
2/13/2019 • 6 minutes to read • Edit Online

With Azure resource diagnostic logs, you can log many events from your capacity, pour them into an analytics tool
and get insights into the behavior of your resource.
Using Diagnostics can answer a few scenarios, such as:
Detection of long-running or problematic queries.
Detecting errors when reaching the limit of your capacity.
Derivation of capacity metrics.
Tracking usage of specific datasets.

Set up diagnostics logging

Azure portal
1. In Azure portal > Power BI Embedded resource, select Diagnostic logs in the left navigation, and then
select Turn on diagnostics.

2. In Diagnostic settings, specify the following options:

Name - Enter a name for the diagnostics setting to create.
 Archive to a storage account - To use this option, you need to connect to an existing storage
account. See Create a storage account, and follow the instructions to create a storage account. Then
select your storage account by returning to this page in the portal. It may take a few minutes for
newly created storage accounts to appear in the drop-down menu. Log file storage is in JSON
format.
Stream to an event hub - To use this option, you need to connect to an existing Event Hub
namespace and event hub. To learn more, see Create an Event Hubs namespace and an event hub
using the Azure portal.
Send to Log Analytics - To use this option, either use an existing workspace or create a new Log
Analytics workspace by following the steps to create a new workspace in the portal. This leverages
Azure Log Analytics, which provides built-in analysis, dashboarding and notification capabilities. You
can use Log Analytics to connect more data from other resources and get a single and complete view
of data across all your application’s resources. It can also be connected to Power BI with a single click.
For more information on viewing your logs in Log Analytics, see View logs in Log Analytics.
Engine - Select this option to log the set of engine events listed below.
AllMetrics - Select this option to store verbose data in Metrics. If you are archiving to a storage
account, you can select the retention period for the diagnostic logs. Logs are auto-deleted after the
retention period expires.
3. Select Save.
To change how your diagnostic logs are saved, you can return to this page to modify settings.

Using PowerShell to enable diagnostics

To enable metrics and diagnostics logging by using PowerShell, use the following commands:
 To enable storage of diagnostics logs in a storage account, use this command:

Set-AzureRmDiagnosticSetting -ResourceId [your resource id] -StorageAccountId [your storage account id]
-Enabled $true

The storage account ID is the resource ID for the storage account where you want to send the logs.
To enable streaming of diagnostics logs to an event hub, use this command:

Set-AzureRmDiagnosticSetting -ResourceId [your resource id] -ServiceBusRuleId [your service bus rule id]
-Enabled $true

The Azure Service Bus rule ID is a string with this format:

{service bus resource ID}/authorizationrules/{key name}

To enable sending diagnostics logs to a Log Analytics workspace, use this command:

Set-AzureRmDiagnosticSetting -ResourceId [your resource id] -WorkspaceId [resource id of the log

analytics workspace] -Enabled $true

You can obtain the resource ID of your Log Analytics workspace by using the following command:

(Get-AzureRmOperationalInsightsWorkspace).ResourceId

You can combine these parameters to enable multiple output options.

REST API
Learn how to change diagnostics settings by using the Azure Monitor REST API.
Resource Manager template
Learn how to enable diagnostics settings at resource creation by using a Resource Manager template.

What's logged?
You can select Engine and/or the AllMetrics categories.
Engine
The engine category instructs the resource to log the following events, and on each of the events there are
properties:

EVENT NAME EVENT DESCRIPTION

Audit Login Records all new connection to the engine events since the
trace started.

Session Initialize Records all session initialization events since the trace started.

Vertipaq Query Begin Records all VertiPaq SE query begin events since the trace
started.

Query Begin Records all query begin events since the trace started.
EVENT NAME EVENT DESCRIPTION

Query End Records all query end events since the trace started.

Vertipaq Query End Records all VertiPaq SE query end events since the trace
started.

Audit Logout Records all disconnect from engine events since the trace
started.

Error Records all engine error events since the trace started.

PROPERTY NAME VERTIPAQ QUERY END EXAMPLE PROPERTY DESCRIPTION

EventClass XM_SEQUERY_END Event Class is used to categorize events.

EventSubclass 0 Event Subclass provides additional

information about each event class. (for
example, 0: VertiPaq Scan)

RootActivityId ff217fd2-611d-43c0-9c12- Root activity ID.

19e202a94f70

CurrentTime 2018-04-06T18:30:11.9137358Z Time at which the event started when

available.

StartTime 2018-04-06T18:30:11.9137358Z Time at which the event started when

available.

JobID 0 Job ID for progress.

ObjectID 464 Object ID

ObjectType 802012 ObjectType

ObjectName SalesLT Customer ObjectName

ObjectPath 5eaa550e-06ac-4adf-aba9- Object path. A comma-separated list of

dbf0e8fd1527.Model.SalesLT Customer parents, starting with the object's
parent.

ObjectReference SalesLT Customer Object reference. Encoded as XML for all

parents, using tags to describe the
Model5eaa550e-06ac-4adf-aba9- object.
dbf0e8fd1527

EndTime 2018-04-06T18:30:11.9137358Z Time at which the event ended.

Duration 0 Amount of time (in milliseconds) taken

by the event.
 PROPERTY NAME VERTIPAQ QUERY END EXAMPLE PROPERTY DESCRIPTION

SessionType User Session type (what entity caused the

operation).

ProgressTotal 0 Progress total.

IntegerData 0 Integer data.

Severity 0 Severity level of an exception.

Success 1 1 = success. 0 = failure (for example, a 1

means success of a permissions check
and a 0 means a failure of that check).

Error 0 Error number of a given event.

TextData SET DC_KIND="AUTO"; SELECT [SalesLT Text data associated with the event.
Customer (464)].[rowguid (606)] AS
[SalesLT Customer (464)$rowguid (606)]
FROM [SalesLT Customer (464)];
[Estimated size (volume marshalling
bytes): 850 6800]

ConnectionID 3 Unique connection ID.

DatasetID 5eaa550e-06ac-4adf-aba9- Id of the dataset in which the statement

dbf0e8fd1527 of the user is running.

SessionID 3D063F66-A111-48EE-B960- Session GUID.

141DEBDA8951

SPID 180 Server process ID. This uniquely

identifies a user session. This directly
corresponds to the session GUID used
by XML/A.

ClientProcessID null The process ID of the client application.

ApplicationName null Name of the client application that

created the connection to the server.

CapacityName pbi641fb41260f84aa2b778a85891ae2d The name of the Power BI Embedded

97 capacity resource.

RequestParameters

RequestProperties

AllMetrics
Checking the AllMetrics option logs the data of all the metrics that you can use with a Power BI Embedded
resource.
Manage your logs
Logs are typically available within a couple of hours after setting up logging. It's up to you to manage your logs in
your storage account:
Use standard Azure access control methods to secure your logs by restricting who can access them.
Delete logs that you no longer want to keep in your storage account.
Be sure to set a retention period, so old logs are deleted from your storage account.

View logs in Log Analytics

Metrics and server events are integrated with xEvents in Log Analytics for side-by-side analysis. Log Analytics can
also be configured to receive events from other Azure services that provide a holistic view of diagnostic logging
data across your architecture.
To view your diagnostic data in Log Analytics, open the Logs page from the left menu or the Management area, as
shown below.

Now that you've enabled data collection, in Logs, select All collected data.
In Type, select AzureDiagnostics, and then select Apply. AzureDiagnostics includes Engine events. Notice a Log
Analytics query is created on-the-fly.
Select EventClass_s or one of the event names and Log Analytics continues constructing a query. Be sure to save
your queries to reuse later.
Be sure to see Log Analytics, which provides a website with an enhanced query, dashboarding, and alerting
capabilities on collected data.
Queries
There are hundreds of queries you can use. Here are a few to get you started. To learn more about using the new
Log Search query language, see Understanding log searches in Log Analytics.
Query return that took less than five minutes (300,000 milliseconds) to complete.

search *
| where Type == "AzureDiagnostics"
| where ( OperationName == "QueryEnd" )
| where toint(Duration_s) < 300000

Identify capacity names.

search *
| where ( Type == "AzureDiagnostics" )
| summarize count() by CapacityName_s

Next steps
You can learn more about Azure resource diagnostic logging.
Azure resource diagnostic logging
Set-AzureRmDiagnosticSetting
 Frequently asked questions about Power BI
Embedded
3/28/2019 • 17 minutes to read • Edit Online

If you have other questions, try asking the Power BI Community.

Still have an issue? Visit the Power BI support page.

General
What is Power BI Embedded?
Microsoft Power BI Embedded (PBIE ) allows application developers to embed stunning, fully interactive reports,
into applications without the time and expense of building their own data visualizations and controls from the
ground-up.
Who is the target audience for Power BI Embedded?
Developers and software companies making their applications referred to as independent software vendors (ISVs).
How is Power BI Embedded different from Power BI the service?
Power BI Embedded is intended for ISVs or developers who are building applications and want to embed visuals
into those applications to help their customers make decisions without building an analytics’ solution from the
ground up. Embedded analytics enables business users to access the business data and perform queries to
generate insights using this data within the application.
Power BI is a software-as-a-service analytics solution that gives organizations a single view of their most critical
business data.
What is the difference between Power BI Premium and Power BI Embedded?
Power BI Premium is capacity geared toward enterprises, who want a complete BI solution that provides a single
view of its organization, partners, customers, and suppliers. Power BI Premium helps your organization make
decisions. Power BI Premium is a SaaS product and comes with the ability for users to consume content through
the Power BI portal, mobile app, and through internally developed apps.
Power BI Embedded is for ISVs or developers who are building applications and want to embed visuals into those
applications. Power BI Embedded helps your customers make decisions because Power BI Embedded is for
application developers, customers of that application can consume content stored on Power BI Embedded
capacity, including anyone inside or outside the organization. Power BI Embedded capacity content can't be shared
through one-click publish to Web or one-click publish to SharePoint, and it doesn't support SSRS reports.
What is the Microsoft recommendation for when a customer should buy Power BI Premium vs. Power BI
Embedded?
Microsoft recommends that enterprises buy Power BI Premium, an enterprise-grade, self-service cloud BI
solution, and ISVs buy Power BI Embedded, cloud-powered embedded analytics components. However, there are
no restrictions on which product a customer can buy.
There may be some cases where an ISV (typically large) wants to use a P SKU to get the additional benefits of the
pre-packaged Power BI service within their organization as well as embed in their applications. Some enterprises
may decide to use A SKUs in Azure if they're only interested in building line-of-business applications and
embedding analytics into them and aren't interested in using the pre-packaged Power BI service.
How many embed tokens can I create?
Embed tokens with PRO license are intended for development testing, so the number of embed tokens a Power BI
master account or service principal can generate is limited. Purchase a capacity for embedding in a production
environment. There's no limit to how many embed tokens you can generate when a capacity is purchased. Go to
Available Features to check the usage value that indicates the current embedded usage in percentage.

Technical
What is the difference between the A SKUs in Azure and the EM SKUs in Office 365?
PowerBI.com is an enterprise solution that includes many capabilities like social collaboration, email subscription,
and other features. in a Software as a Service offering
Power BI Embedded is a set of APIs available for developers to create an embedded analytics solution in a
Platform as a Service offering. For the Embedded analytics scenario, PowerBI.com helps ISVs and developers
manage their embedded analytics solution content and tenant level settings.
Here is a partial list of differences you may use with each.

FEATURE POWER BI EMBEDDED POWER BI PREMIUM CAPACITY POWER BI PREMIUM CAPACITY

(A SKUs) (EM SKUs) (P SKUs)

Embed artifacts from a Azure capacity Office 365 capacity Office 365 capacity
Power BI App workspace

Consume Power BI reports Yes Yes Yes

in an Embedded application

Consume Power BI reports No Yes Yes

in SharePoint

Consume Power BI reports No Yes Yes

in Dynamics

Consume Power BI reports No Yes Yes

in Teams (excludes mobile
app)

Access content with a FREE No No Yes

Power BI license in
Powerbi.com and Power BI
mobile

Access content with a FREE No Yes Yes

Power BI license embedded
in MS Office apps

Power BI now offers three SKUs for embedding: A SKUs, EM SKUs, and P SKUs. Which one should I purchase
for my scenario?
A SKU (POWER BI EMBEDDED) EM SKU (POWER BI PREMIUM) P SKU (POWER BI PREMIUM)

Purchase Azure portal Office Office

 A SKU (POWER BI EMBEDDED) EM SKU (POWER BI PREMIUM) P SKU (POWER BI PREMIUM)

Use cases Embed content in your own Embed content in your Embed content in your
application own application own application

Embed content in MS Embed content in MS

Office applications: Office applications:
- SharePoint - SharePoint
- Teams (excludes mobile - Teams (excludes mobile
app) app)
- Dynamics 365 - Dynamics 365

Share content with Power

BI users through the Power
BI service

Billing Hourly Monthly Monthly

Commitment No commitment Yearly Monthly/Yearly

Differentiation Full elasticity- can scale up/ Can be used to embed Combine embedding in
down, pause/ resume content in SharePoint Online applications and use the
resources in Azure portal or and Microsoft Teams Power BI Service in the same
through API (excludes mobile app) capacity

What are the prerequisites to create a PBIE capacity in Azure?

Sign in to your organizational directory (MSA accounts are not supported).
You need to have a Power BI tenant, that is, at least one user in your directory has signed up to Power BI.
You need to have an Azure subscription in your organizational directory.
How can I monitor Power BI Embedded capacity consumption?
Using the Power BI Admin portal.
Downloading the metric app in Power BI.
Using Azure diagnostic logging.
Can my capacity scale automatically to adjust to the consumption of my app?
While there is no automatic scaling now, all the APIs are available to scale at any time.
Why creating/scaling/resuming a capacity results in putting the capacity into a suspended state?
The provisioning of a capacity (scale/resume/create) may fail. The caller of the provisioning call should check the
ProvisioningState of a capacity using Get Details API: Capacities - Get Details.
Can I only create Power BI Embedded capacities in a specific region?
With the Multi-geo (Preview ) feature, you can purchase a Power BI Embedded capacity in a different region than
your Power BI home tenant location
How can I find what is my PBI tenant region?
You can use the PBI portal to understand what is your PBI Tenant region.
https://app.powerbi.com/ > ? > About Power BI
What is supported by the Cloud Solution Provider (CSP) channel?
You can create PBIE for your tenant with subscription type CSP
Partner account can sign in to customer tenant and purchase PBIE for customer tenant, specify customer tenant
user as Power BI capacity admin
Why do I get an unsupported account message?
Power BI requires you to sign up with an organizational account. Trying to sign up for Power BI using an MSA
(Microsoft account) isn't supported.
Can I use APIs to create & manage Azure capacities?
Yes, there are Powershell cmdlets and Azure Resource Manager APIs you can use to create & manage PBIE
resources.
Rest APIs - https://docs.microsoft.com/rest/api/power-bi-embedded/
Powershell cmdlets - https://docs.microsoft.com/powershell/module/azurerm.powerbiembedded/
What is the PBI Embedded dedicated capacity role in a PBI Embedded solution?
To promote your solution to production, you need the Power BI content (app workspace) that you are using in
your application to be assigned to a Power BI Embedded (A SKU ) capacity.
What are the Azure regions PBI Embedded is available?
PAM (EcoManager) - see Product availability manager
Available regions (16 - same regions as Power BI)
US (6) - East US, East US 2, North Central US, South Central US, West US, West US 2
Europe (2) - North Europe, West Europe
Asia Pacific (2) - Southeast Asia, East Asia
Brazil (1) - Brazil South
Japan (1) - Japan East
Australia (1) - Australia Southeast
India (1) - West India
 Canada (1) - Canada Central
United Kingdom (1) - UK South
What is the authentication model for Power BI Embedded?
Power BI Embedded continues to use Azure AD for authentication of the master user (a designated Power BI Pro
licensed user), or with service principal for authenticating the application inside Power BI.
The authentication and authorization of application users implemented by the ISV, the ISV can implement their
authentication for their applications.
If you already have an Azure AD tenant, you can use your existing directory, or you can create a new Azure AD
tenant for your embedded application content security.
To get an AAD token, you can use one of the Azure Active Directory Authentication Libraries. There are client
libraries available for multiple platforms.
My Application already uses AAD for User Authentication. How can we use this Identity when authenticating to
Power BI in a "User Owns Data" scenario?
It is standard OAuth on-behalf-of flow (https://docs.microsoft.com/azure/active-directory/develop/web-api). The
Application needs to be configured to require permissions to Power BI service (with the required scopes). Once
you have a user token to your app, you simply call to ADAL API AcquireTokenAsync using the user access token
and specify the Power BI resource URL as the resource ID. See the following code snippet showing how this can
be done:

var context = new AD.AuthenticationContext(authorityUrl);

var userAssertion = new AD.UserAssertion(userAccessToken);
var clientAssertion = new AD.ClientAssertionCertificate(MyAppId, MyAppCertificate)
var authenticationResult = await context.AcquireTokenAsync(resourceId, clientAssertion, userAssertion);

What object ID is the service principal object ID?

The Object ID from the main screen of a registered app is the object ID for the app.
The object ID found in the Managed application in local directory > Properties section is the service principal
object ID you need to use. This object ID is to reference a service principal for operations or to make changes to
the service principal object ID. Such as applying a service principal as an admin to a workspace.
How is Power BI Embedded different from other Azure services?
The ISV/developer must have a Power BI account before the purchase of Power BI Embedded in Azure. Your
Power BI Embedded deploys region determines your Power BI account. Manage your Power BI Embedded
resource in Azure to:
Scale up/down
Add capacity admins
Pause/resume of service
Use PowerBI.com to assign/un-assign workspaces to your Power BI Embedded capacity.
What deploy regions are supported?
Australia Southeast, Brazil South, Canada Central, East US 2, India West, Japan East, North Central US, North
Europe, South Central US, Southeast Asia, UK South, West Europe, West US, and West US 2.
What type of content pack data can be embedded?
Dashboards and tiles that are built from content pack datasets cannot be embedded, however, reports built from
a content pack dataset can be embedded.
What is the difference between using RLS vs. JavaScript filters?
There’s often confusion around when to use RLS vs. JavaScript filters, because one method is about controlling
what a specific user can see, and the other is about optimizing the user's view.
For RLS, the ISV developer controls the data filtering as part of the model creation and embed token generation.
The end user sees only what the ISV allows the user to see. In this case, the user can choose to see less than what's
being filtered, but won’t be able to bypass the RLS configuration and see more than what's allowed.
For client-side filtering (JavaScript), the ISV might decide what the end user sees at the initial view, but the ISV
cannot control changes the end user might apply to the view itself. Even though data filtering can happen on the
backend, it’s triggered by the JavaScript client code, and therefore it can be changed by an end user, and cannot be
considered secure.
Reference RLS vs JavaScript filters for more details.
How do I manage permissions for service principals with Power BI?
Once you enable service principal to be used with Power BI, the application's AD permissions don't take effect
anymore. The application's permissions are then managed through the Power BI admin portal.
Service principals inherit the permissions for all Power BI tenant settings from their security group. To restrict
permissions, create a dedicated security group for service principals and add it to the 'Except specific security
groups' list for the relevant, enabled Power BI settings.
This situation matters when you add the service principal as an admin to the new workspace. You can manage
this task through the APIs or with the Power BI service.
When to use an application ID vs. a service principal object ID?
The application ID is used to create the access token when passing the application ID for authentication.
To reference a service principal for operations or to make changes you use the service principal object ID — for
example, applying a service principal as an admin to a workspace.
Can you manage an On-premises data gateway with service principal?
You can't manage an On-premises data gateway (data gateway) using service principal like you can with a master
account.
With a master account, you can install a data gateway, add users to the gateway, connect to data sources, and do
other administrative tasks.
With service principal, you can configure row -level security (RLS ) using an SQL Server Analysis Services (SSAS )
on-premises live connection data source. This way you can manage users and their access to data in SSAS when
integrating with Power BI Embedded using a service principal.
Can you sign into the Power BI service with service principal?
No - you can't sign into Power BI using service principal.
Also, you can’t consume content as a user in external applications (SaaS embed), only when you generate an
embed token.
What are the best practices to improve performance?
Power BI Embedded performance

Licensing
How do I purchase Power BI Embedded?
Power BI Embedded is available through Azure.
What happens if I already purchased Power BI Premium and now I want some of the benefits of Power BI
Embedded in Azure?
Customers continue to pay for any existing Power BI Premium purchases until the end of their current agreement
term and then may switch their Power BI Premium purchases as necessary at that point.
Do I still have to buy Power BI Premium to get access to Power BI Embedded?
No, Power BI Embedded includes the Azure-based capacity that you need to deploy and distribute your solution to
customers.
What’s the purchase commitment for Power BI Embedded?
Customers may change their usage on an hourly basis. There is no monthly or annual commitment for the Power
BI Embedded service.
How does the usage of Power BI Embedded show up on my bill?
Power BI Embedded bills on a predictable hourly rate based on the type of node(s) deployed. As long as your
resource is active, you are billed even if there is no usage. To stop being billed, you need to pause your resource
actively.
Who needs a Power BI Pro license for Power BI Embedded and why?
Any developer that requires the use of the REST APIs needs a Power BI Pro license or service principal. Any
analyst that needs to add reports to a Power BI workspace can either have a Power BI Pro license or use service
principal. Any tenant admin that needs to manage the Power BI tenant and capacity is required to have a Power BI
Pro license.
Because Power BI Embedded allows the use of the Power BI portal for managing and validating embedded
content, the Power BI Pro license is required to authenticate the App inside PowerBI.com to get access to the
reports in the right repositories.
However, for creating/editing embedded reports inside your application, the end user does not need a Pro license
as the user isn't required to be a Power BI user at all.
Can I get started for free?
Yes, you can use your Azure credits for Power BI Embedded.
Can I get a trial experience for Power BI Embedded in Azure?
Since Power BI Embedded is a part of Azure, it is possible to use the service with the $200 credit received when
signing up for Azure.
Is Power BI Embedded available for national clouds (US Government, Germany, China)?
Power BI Embedded is also available for the national clouds.
Is Power BI Embedded available for non-profits and educational?
Non-profit and educational entities can purchase Azure. There is no special pricing for these types of customers in
Azure.

Power BI Workspace Collection

What is Power BI Workspace Collection?
Power BI Workspace Collection (Power BI Embedded Version 1) is a solution that is based on the Power BI
Workspace Collection Azure resource. This solution allows you to create Power BI Embedded applications for
your customers using Power BI content under the Power BI Workspace Collection solution, dedicated APIs, and
workspace collection keys to authenticate the application to Power BI.
Can I migrate from Power BI Workspace Collection to Power BI Embedded?
1. You can use the migration tool to clone Power BI Workspace Collection content to Power BI -
https://docs.microsoft.com/power-bi/developer/migrate-from-powerbi-embedded#content-migration.
2. Start with the Power BI Embedded application POC that uses Power BI content.
3. Once you are ready for production, purchase a Power BI Embedded dedicated capacity and assign your
Power BI content (workspace) to that capacity.

NOTE
You can continue to use Power BI Workspace Collection while building in parallel with a Power BI Embedded
solution. Once you are ready, you can move your customer to the new Power BI Embedded solution and retire the
Power BI Workspace Collection solution.

For more information, please reference How to migrate Power BI Workspace Collection content to Power BI
Embedded
Is Power BI Workspace Collection on a path to be deprecated?
Yes, but customers that are already using the Power BI Workspace Collection solution can continue to use it
until it is deprecated. Customers can also create new workspace collections and any Power BI Embedded
applications that still use the Power BI Workspace Collection solution.
However, this also means that new features aren't added to any Power BI Workspace Collection solutions and
that customers are encouraged to plan their migration to the new Power BI Embedded solution.
When is Power BI Workspace Collection support discontinued?
Customers that are already using the Power BI Workspace Collections solution can continue to use it until the
end of June 2018 or until the end of their support agreement.
In what regions can PBI Workspace Collection be created?
The available regions are Australia Southeast, Brazil South, Canada Central, East US 2, Japan East, North Central
US, North Europe, South Central US, Southeast Asia, UK South, West Europe, West India, and West US.
Why should I migrate from PBI Workspace Collection to Power BI Embedded?
Some new features and capabilities are introduced in the Power BI Embedded solution that you can't do with
Power BI Workspace Collection.
Some of the features are:
All the PBI data sources are supported as opposed to the two data sources that are with Power BI Workspace
Collection).
New features such as Q&A, refresh, bookmarks, embedding dashboards & tiles, and custom menus are only
supported in the Power BI Embedded solution.
Capacity billing model.

Embedding setup tool

What is the Embedding setup tool?
The Embedding setup tool allows you to quickly get started and download a sample application to begin
embedding with Power BI.
Which solution should I choose?
Embedding for your customers provides the ability to embed dashboards and reports to users who don't have
an account for Power BI. Run the Embed for your customers solution.
Embedding for your organization allows you to extend the Power BI service. Run the Embed for your
organization solution.
I've downloaded the sample app, which solution do I choose?
If you're working with the Embed for your customers experience, save and unzip the PowerBI -Developer-
Samples.zip file. Then open the PowerBI -Developer-Samples-master\App Owns Data folder and run the
PowerBIEmbedded_AppOwnsData.sln file.
If you're working with the Embed for your organization experience, save and unzip the PowerBI -Developer-
Samples.zip file. Then open the PowerBI -Developer-Samples-master\User Owns Data\integrate-report-web -app
folder and run the pbi-saas-embed -report.sln file.
How can I edit my registered application?
To learn how to edit Azure AD -registered applications, see Quickstart: Update an application in Azure Active
Directory.
How can I edit my Power BI user profile or data?
You can learn how to edit your Power BI data here.
For more information, see Troubleshooting your embedded application.
More questions? Try the Power BI Community
 Power BI permissions
2/13/2019 • 3 minutes to read • Edit Online

Permission scopes
Power BI permissions give an application the ability to take certain actions on a user's behalf. All permissions must
be approved by a user in order to be valid.

DISPLAY NAME DESCRIPTION SCOPE VALUE

View all Datasets The app can view all datasets for the Dataset.Read.All
signed in user and datasets that the
user has access to.

Read and Write all Datasets The app can view and write to all Dataset.ReadWrite.All
datasets for the signed in user and
datasets that the user has access to.

Add data to a user's dataset Gives an app access to add or delete a Data.Alter_Any
user's dataset rows. This permission
does not grant the app access to the
user's data.

Create content App can automatically create content Content.Create

and datasets for a user.

View users Groups The app can view all groups that the Group.Read
signed in user belongs to.

View all Groups The app can view all groups that the Group.Read.All
signed in user belongs to.

Read and write all Groups The app can view and write to all the Group.ReadWrite.All
groups for the signed in user and any
groups that the user has access to.

View all Dashboards The app can view all dashboards for the Dashboard.Read.All
signed in user and dashboards that the
user has access to.

View all Reports The app can view all reports for the Report.Read.All
signed in user and reports that the user
has access to. The app can also see the
data within the reports as well as its
structure.

Read and write all Reports The app can view and write to all the Report.ReadWrite.All
reports for the signed in user and any
reports that the user has access to. This
does not provide rights to create a new
report.
 DISPLAY NAME DESCRIPTION SCOPE VALUE

Read and write all Capacities The app can view and write to all the Capacities.ReadWrite.All
capacities for the signed in user and any
capacity that the user has access to.
This does not provide rights to create a
new capacity.

Read all Capacities The app can view and write to all the Capacities.Read.All
capacities for the signed in user and any
capacities that the user has access to.
This does not provide rights to create a
new capacity.

Read and write all content in tenant The app can view and write to all Tenant.ReadWrite.All
artifacts, such as groups, reports,
dashboards, and datasets in Power BI.
Provided the signed in user is a Power
BI service administrator.

View all content in tenant The app can view all artifacts, such as Tenant.Read.All
groups, reports, dashboards, and
datasets in Power BI. Provided the
signed in user is a Power BI service
administrator.

An application can request permissions when it first attempts to sign in to a user's page by passing in the
requested permissions in the scope parameter of the call. If the permissions are granted, an access token will be
returned to the app, which can be used on future API calls. The access can only be used by a specific application.

NOTE
The Power BI APIs still refer to app workspaces as groups. Any references to groups mean that you are working with app
workspaces.

Requesting Permissions
While you can call the API to authenticate with a username and password, in order to take actions on behalf of
another user, they will need to request permissions that the user then approves and then send the resulting access
token on all future calls. For this process, we will follow the standard OAuth 2.0 protocol. While the actual
implementation may vary, the OAuth flow for Power BI has the following elements:
Login UI - This is a UI that the developer can evoke to request permissions. It would require the user to sign in
if not already. The user would also need to approve the permissions that the application is requesting. The login
window will post back either an access code or an error message to a redirect URL that is supplied.
A standard redirect URL should be supplied by Power BI for use by native applications.
Authorization Code - Authorization Codes are returned to web applications after login via URL parameters in
the redirect URL. Since they are in parameters, there is some security risk. Web applications will have to
exchange the authorization code for an Authorization Token
Authorization Token - Are used to authenticate API calls on another user's behalf. They will be scoped to a
specific application. Tokens have a set lifespan and when they expire they will need to be refreshed.
Refresh Token - When tokens expire there will be a process of refreshing them.
More questions? Try asking the Power BI Community
 Embed reports or dashboards from apps
1/14/2019 • 2 minutes to read • Edit Online

In Power BI, you can create apps to bring related dashboards and reports together, all in one place. Then you
publish them to large groups of people in your organization. The usage of those apps is relevant when all your
users are Power BI users. So you can share content with them by using Power BI apps. This article gives you a few
quick steps to embed content out of a published Power BI app and into a third-party application.

Grab a report embedURL for embedding

1. Instantiate the application in a user workspace, My Workspace. Either share with yourself or guide another
user to go through this flow.
2. Open the report you want in the Power BI service.
3. Go to File > Embed In SharePoint Online and grab the report embedURL. An embedURL sample is
shown in the below snapshot. Alternatively, you can call the GetReports/GetReport REST API and extract
the corresponding report embedURL field out of the response. The REST call shouldn’t have a workspace
identifier as part of the URL as the app got instantiated in the user’s workspace.

4. Use the embedURL retrieved in step 3 with the JavaScript SDK.

Grab a dashboard embedURL for embedding

1. Instantiate the application in a user workspace, My Workspace. Either share with yourself or guide another
user to go through this flow.
2. Call the GetDashboards REST API and extract the corresponding dashboard embedURL field out of the
response. The REST call shouldn’t have a workspace identifier as part of the URL as the app got instantiated
in the user’s workspace.
3. Use the embedURL retrieved in step 2 with the JavaScript SDK.

Next steps
Review how to embed from app workspaces for your third-party customers and your organization:
Embed for third-party customers
Embed for your organization
 Create an Azure Active Directory tenant to use with
Power BI
3/26/2019 • 3 minutes to read • Edit Online

Learn how to create a new Azure Active Directory (Azure AD ) tenant for use with your custom application using
the Power BI REST APIs.
A tenant is representative of an organization within Azure Active Directory. It is a dedicated instance of the Azure
AD service that an organization receives and owns when it signs up for a Microsoft cloud service such as Azure,
Microsoft Intune, or Office 365. Each Azure AD tenant is distinct and separate from other Azure AD tenants.
Once you have an Azure AD tenant, you can define an application and assign permissions so your application can
make use of the Power BI REST APIs.
Your organization may already have an Azure AD tenant that you can use for your application. You can make use
of that tenant for your application needs or you can create a new tenant specifically for your application. This
article looks at how to create a new tenant.

Create an Azure Active Directory tenant

In order to integrate Power BI into your custom application, you need to define an application within Azure AD.
To do that, you need a directory within Azure AD. This is your tenant. If your organization doesn't have a tenant
yet, because they aren't using Power BI or Office 365, you will need to create one. You may also need to create
one if you don't want your application mixing with your organization's tenant. This allows you to keep things
isolated.
Or, you may just want to create a tenant for testing purposes.
To create a new Azure AD tenant, do the following.
1. Browse to the Azure portal and sign in with an account that has an Azure subscription.
2. Select the plus icon (+) and search for Azure Active Directory.

3. Select Azure Active Directory in the search results.

4. Select Create.
5. Provide a name for the organization along with the initial domain name. Then select Create. This will
create your directory.

NOTE
Your initial domain will be part of onmicrosoft.com. You can add other domain names later. The directory, of a
tenant, can have multiple domains assigned to it.

6. After your directory creation is complete, select the information box to manage your new directory.
Your directory is now created. Next we will want to add a user to the tenant.

Create some users in your Azure Active Directory tenant

Now that we have a directory, let's create at least two users. One that will be a Global Admin for the tenant and
another that will be our master user for embedding. Think of this as a service account.
1. Within the Azure portal, make sure we are on the Azure Active Directory fly out.
 If you are not, select the Azure Active Directory icon from the left services bar.

2. Under Manage, select Users and groups.

3. Select All users and then select + New user.

4. Provide a name and username for this user. This will be your Global Admin for the tenant. You will also
want to change the Directory role to Global administrator. You can also show the temporary password.
When you are done, select Create.

5. You will want to do the same thing again for a regular user in your tenant. This could also be used for your
master embedding account. This time, for Directory role, we will leave it as User. Be sure to make note of
the password. Then select Create.
6. Sign up for Power BI with your user account that you created in step 5. You can do that by going to
powerbi.com and selecting Try free under Power BI - Cloud collaboration and sharing.

When you sign up, you will be prompted to try Power BI Pro free for 60 days. You can opt into that to
become a pro user. Now you can also start developing an embedded solution if that is what you are
looking for.

NOTE
Make sure you sign up with the email address you gave the user account.

Next steps
Now that you have an Azure AD tenant, you can use this tenant to test items within Power BI, and/or you can
move forward to embed Power BI dashboards and reports in your application. For more information on how to
embed items, see How to embed your Power BI dashboards, reports and tiles.
What is an Azure AD directory?
How to get an Azure Active Directory tenant
More questions? Try asking the Power BI Community
 Register an Azure AD application to use with Power
BI
2/6/2019 • 7 minutes to read • Edit Online

Learn how to register an application within Azure Active Directory (Azure AD ) for use with embedding Power BI
content.
You register your application with Azure AD to allow your application access to the Power BI REST APIs. Once
you register your application, you can establish an identity for your application and specify permissions to Power
BI REST resources.

IMPORTANT
Before you register a Power BI app you need an Azure Active Directory tenant and an organizational user. If you haven't
signed up for Power BI with a user in your tenant, the app registration doesn't complete successfully.

There are two ways to register your application. The first is with the Power BI App Registration Tool, or you can
do it directly within the Azure portal. The Power BI App Registration Tool is more convenient to use since there
are just a few fields to complete. Use the Azure portal if you want to make changes to your app.

Register with the Power BI Application Registration Tool

Register your application in Azure Active Directory to establish an identity for your application and specify
permissions to Power BI REST resources. When you register an application, such as a console app or a website,
you receive an identifier, which is used by the application to identify themselves to the users that they're
requesting permissions.
Here's how to register your application with the Power BI App Registration Tool:
1. Go to dev.powerbi.com/apps.
2. Select Sign in with your existing account then select Next.
3. Provide an Application Name.
4. Provide an Application Type.
Here are the differences for why you choose Native versus Server-side web applications for an
application type.
Native:
You plan on creating an application that is designed for your customers using a master user account (a
Power BI Pro license used for signing in to Power BI) to authenticate.
Server-side web application:
You plan on creating an application designed for your organization.
You plan on creating an application designed for your customers using service principal to authenticate.
You plan on creating web apps or web APIs.
5. If you selected Server-side web application for the application type, then continue with entering a value
for Home Page URL and Redirect URL. The Redirect URL works with any valid URL and should
correspond with the application you have created. If you selected Native, then continue to step 6.
6. Choose the Power BI APIs that your application needs. For more information about Power BI access
permissions, see Power BI Permissions. Then select Register.

IMPORTANT
If you enable service principals to be used with Power BI, the Azure Active Directory permissions don't take effect
anymore. The permissions are managed through the Power BI admin portal.

7. If you choose Native for the application type, then you are then provided an Application ID. If you select
Server-side Web app for the application type, then you receive an Application ID and an Application
secret.

NOTE
The Application ID can be retrieved from the Azure portal, at a later time, if needed. If you lose the Application
secret, you need to create a new one within the Azure portal.
 NATIVE SERVER-SIDE WEB APPLICATION

You can now use the registered application as part of your custom application to interact with the Power BI
service and with your Power BI Embedded application.

Register with the Azure portal

Your other option for registering your application is to do so directly in the Azure portal. To register your
application, follow these steps.
1. Accept the Microsoft Power BI API Terms.
2. Sign into the Azure portal.
3. Choose your Azure AD tenant by selecting your account in the top-right corner of the page.
4. In the left-hand navigation pane, All services, Azure Active Directory, select App Registrations and
then select New application registration.

5. Follow the prompts and create a new application.

For Web Applications, provide the Sign-On URL, which is the base URL of your app, where users sign
into (for example, http://localhost:13526 ).
For Native Applications, provide a Redirect URI, which Azure AD uses to return token responses.
Make sure to enter a value specific to your application (for example, http://myapplication/Redirect ).

For more information about how to register applications in Azure Active Directory, see Integrating applications
with Azure Active Directory
How to get the Application ID
When you register an application, you receive an Application ID. The Application ID requests permissions to the
users by the application to identify themselves.

How to get the service principal object ID

When using the Power BI APIs, make sure to define operations using the service principal object ID to reference
the service principal - for example, applying a service principal as an admin to a workspace.

Apply permissions to your application within Azure AD

Enable additional permissions to your application in addition to what the app registration page provides. You can
accomplish this task through the Azure AD portal, or programmatically.
You want to be logged in with either the master account, used for embedding, or a Global admin account.
Using the Azure AD portal
1. Browse to App registrations within the Azure portal and select the app that you're using for embedding.

2. Select Required permissions under API Access.

3. Within Required permissions, select Power BI Service (Power BI ).

 NOTE
If you created the app directly in the Azure AD portal, Power BI Service (Power BI) may not be present. If it isn't,
select + Add and then 1 Select and API. Select Power BI Service in the API list and select Select. If Power BI
Service (Power BI) isn't available within + Add, sign up for Power BI with at least one user.

4. Select all permissions under Delegated Permissions. Select them one by one to save the selections.
Select Save when done.

5. Within Required permissions, select Grant Permissions.

The Grant Permissions action needs for the master account to avoid being prompted for consent by
Azure AD. If the account performing this action is a Global Admin, you grant permissions to all users
within your organization for this application. If the account performing this action is the master account
and isn't a Global Admin, you grant permissions only to the master account for this application.

Applying permissions programmatically

1. You need to get the existing service principals (users) within your tenant. For information on how to do
that, see Get servicePrincipal.
You can call the Get servicePrincipal API without {ID }, and it gets you all of the service principals within the
 tenant.
2. Check for a service principal with your app application ID as appId property.
3. Create a new service plan if missing from your app.

Post https://graph.microsoft.com/beta/servicePrincipals
Authorization: Bearer ey..qw
Content-Type: application/json
{
"accountEnabled" : true,
"appId" : "{App_Client_ID}",
"displayName" : "{App_DisplayName}"
}

4. Grant App Permissions to Power BI API

If you're using an existing tenant, and not interested in granting permissions on behalf of all tenant users,
you can grant permissions to a specific user by replacing the value of contentType to Principal.
The value for consentType can supply either AllPrincipals or Principal.
AllPrincipals can only be used by a tenant admin to grant permissions on behalf of all users in the
tenant.
Principal is used to grant permissions on behalf of a specific user. In this case, an additional
property should be added to the request's body - principalId={User_ObjectId }.
You need to Grant permissions for the master account to avoid being prompted for consent by
Azure AD, which isn't possible when doing non-interactive sign-in.

Post https://graph.microsoft.com/beta/OAuth2PermissionGrants
Authorization: Bearer ey..qw
Content-Type: application/json
{
"clientId":"{Service_Plan_ID}",
"consentType":"AllPrincipals",
"resourceId":"c78a3685-1ce7-52cd-95f7-dc5aea8ec98e",
"scope":"Dataset.ReadWrite.All Dashboard.Read.All Report.Read.All Group.Read Group.Read.All
Content.Create Metadata.View_Any Dataset.Read.All Data.Alter_Any",
"expiryTime":"2018-03-29T14:35:32.4943409+03:00",
"startTime":"2017-03-29T14:35:32.4933413+03:00"
}

The resourceId c78a3685 -1ce7 -52cd -95f7 -dc5aea8ec98e isn't universal but it's tenant dependant. This
value is the objectId of the “Power BI Service” application in the Azure Active Directory (AAD ) tenant.
The user can quickly get this value in the Azure portal:
a. https://portal.azure.com/#blade/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/AllApps
b. Search for “Power BI Service” in the SearchBox
5. Grant App Permissions to Azure Active Directory (AAD )
The value for consentType can supply either AllPrincipals or Principal.
AllPrincipals can only be used by a tenant admin to grant permissions on behalf of all users in the
tenant.
Principal is used to grant permissions on behalf of a specific user. In this case, an additional property
should be added to the request's body - principalId={User_ObjectId }.
 You need to Grant permissions for the master account to avoid being prompted for consent by Azure AD,
which isn't possible when doing non-interactive sign-in.

Post https://graph.microsoft.com/beta/OAuth2PermissionGrants
Authorization: Bearer ey..qw
Content-Type: application/json
{
"clientId":"{Service_Plan_ID}",
"consentType":"AllPrincipals",
"resourceId":"61e57743-d5cf-41ba-bd1a-2b381390a3f1",
"scope":"User.Read Directory.AccessAsUser.All",
"expiryTime":"2018-03-29T14:35:32.4943409+03:00",
"startTime":"2017-03-29T14:35:32.4933413+03:00"
}

Next steps
Now that you've registered your application within Azure AD, you need to authenticate users within your
application. Have a look at Authenticate users and get an Azure AD access token for your Power BI app to learn
more.
More questions? Try asking the Power BI Community
 Get an Azure AD access token for your Power BI
application
2/6/2019 • 4 minutes to read • Edit Online

Learn how you can authenticate users in your Power BI application and retrieve an access token to use with the
REST API.
Before you can call the Power BI REST API, you need to get an Azure Active Directory (Azure AD )
authentication access token (access token). An access token is used to allow your app access to Power BI
dashboards, tiles, and reports. To learn more about Azure Active Directory access token flow, see Azure AD
Authorization Code Grant Flow.
Depending on how you're embedding content, the access token is retrieved differently. Two different approaches
are used in this article.

Access token for Power BI users (user owns data)

This example is for when your users manually log into Azure AD with their organization login. This task is used
when embedding content for Power BI users that access content has access to the Power BI service.
Get an authorization code from Azure AD
The first step to get an access token is to get an authorization code from Azure AD. Construct a query string
with the following properties, and redirect to Azure AD.
Authorization code query string

var @params = new NameValueCollection

{
//Azure AD will return an authorization code.
//See the Redirect class to see how "code" is used to AcquireTokenByAuthorizationCode
{"response_type", "code"},

//Client ID is used by the application to identify themselves to the users that they are requesting
permissions from.
//You get the client id when you register your Azure app.
{"client_id", Properties.Settings.Default.ClientID},

//Resource uri to the Power BI resource to be authorized

// https://analysis.windows.net/powerbi/api
{"resource", Properties.Settings.Default.PowerBiAPI},

//After user authenticates, Azure AD will redirect back to the web app
{"redirect_uri", "http://localhost:13526/Redirect"}
};

After you construct a query string, you redirect to Azure AD to get an authorization code. Below is a complete
C# method to construct an authorization code query string, and redirect to Azure AD. After you have the
authorization code, you get an access token using the authorization code.
Within redirect.aspx.cs, AuthenticationContext.AcquireTokenByAuthorizationCode calls to generate the token.
Get authorization code
 protected void signInButton_Click(object sender, EventArgs e)
{
//Create a query string
//Create a sign-in NameValueCollection for query string
var @params = new NameValueCollection
{
//Azure AD will return an authorization code.
//See the Redirect class to see how "code" is used to AcquireTokenByAuthorizationCode
{"response_type", "code"},

//Client ID is used by the application to identify themselves to the users that they are requesting
permissions from.
//You get the client id when you register your Azure app.
{"client_id", Properties.Settings.Default.ClientID},

//Resource uri to the Power BI resource to be authorized

// https://analysis.windows.net/powerbi/api
{"resource", Properties.Settings.Default.PowerBiAPI},

//After user authenticates, Azure AD will redirect back to the web app
{"redirect_uri", "http://localhost:13526/Redirect"}
};

//Create sign-in query string

var queryString = HttpUtility.ParseQueryString(string.Empty);
queryString.Add(@params);

//Redirect authority
//Authority Uri is an Azure resource that takes a client id to get an Access token
// AADAuthorityUri = https://login.microsoftonline.net/common/
string authorityUri = Properties.Settings.Default.AADAuthorityUri;
var authUri = String.Format("{0}?{1}", authorityUri, queryString);
Response.Redirect(authUri);
}

Get an access token from authorization code

You should now have an authorization code from Azure AD. Once Azure AD redirects back to your web app with
an authorization code, you use the authorization code to get an access token. Below is a C# sample that you
could use in your redirect page and the Page_Load event for your default.aspx page.
The Microsoft.IdentityModel.Clients.ActiveDirectory namespace can be retrieved from the Active Directory
Authentication Library NuGet package.

Install-Package Microsoft.IdentityModel.Clients.ActiveDirectory

Redirect.aspx.cs
 using Microsoft.IdentityModel.Clients.ActiveDirectory;

protected void Page_Load(object sender, EventArgs e)

{
//Redirect uri must match the redirect_uri used when requesting Authorization code.
string redirectUri = String.Format("{0}Redirect", Properties.Settings.Default.RedirectUrl);
string authorityUri = Properties.Settings.Default.AADAuthorityUri;

// Get the auth code

string code = Request.Params.GetValues(0)[0];

// Get auth token from auth code

TokenCache TC = new TokenCache();

AuthenticationContext AC = new AuthenticationContext(authorityUri, TC);

ClientCredential cc = new ClientCredential
(Properties.Settings.Default.ClientID,
Properties.Settings.Default.ClientSecret);

AuthenticationResult AR = AC.AcquireTokenByAuthorizationCode(code, new Uri(redirectUri), cc);

//Set Session "authResult" index string to the AuthenticationResult

Session[_Default.authResultString] = AR;

//Redirect back to Default.aspx

Response.Redirect("/Default.aspx");
}

Default.aspx

using Microsoft.IdentityModel.Clients.ActiveDirectory;

protected void Page_Load(object sender, EventArgs e)

{

//Test for AuthenticationResult

if (Session[authResultString] != null)
{
//Get the authentication result from the session
authResult = (AuthenticationResult)Session[authResultString];

//Show Power BI Panel

signInStatus.Visible = true;
signInButton.Visible = false;

//Set user and token from authentication result

userLabel.Text = authResult.UserInfo.DisplayableId;
accessTokenTextbox.Text = authResult.AccessToken;
}
}

Access token for non-Power BI users (app owns data)

This approach is typically used for ISV type applications where the app owns access to the data. Users aren't
necessarily Power BI users, and the application controls authentication and access for the end users.
Access token with a master account
For this approach, you use a single master account that is a Power BI Pro user. The credentials for this account are
stored with the application. The application authenticates against Azure AD with those stored credentials. The
example code shown below comes from the App owns data sample
Access token with service principal
For this approach, you use a service principal, that is an app-only token. The application authenticates against
Azure AD with service principal. The example code shown below comes from the App owns data sample
EmbedService.cs

var authenticationContext = new AuthenticationContext(AuthorityUrl);

AuthenticationResult authenticationResult = null;
if (AuthenticationType.Equals("MasterUser"))
{
// Authentication using master user credentials
var credential = new UserPasswordCredential(Username, Password);
authenticationResult = authenticationContext.AcquireTokenAsync(ResourceUrl, ApplicationId,
credential).Result;
}
else
{
// Authentication using app credentials
var credential = new ClientCredential(ApplicationId, ApplicationSecret);
authenticationResult = await authenticationContext.AcquireTokenAsync(ResourceUrl, credential);
}

m_tokenCredentials = new TokenCredentials(authenticationResult.AccessToken, "Bearer");

Next steps
Now that you have the access token, you can call the Power BI REST API to embed content. For information on
how to embed your content, see How to embed your Power BI content.
More questions? Try asking the Power BI Community
 Q&A in Power BI Embedded
3/11/2019 • 2 minutes to read • Edit Online

Power BI Embedded offers you a way to incorporate Q&A into an application and allow your users to ask
questions using natural language and receive immediate answers in the form of visuals like charts or graphs.

There are two modes for embedding Q&A within your application: interactive and result only. Interactive
mode allows you to type in questions and have them displayed within the visual. If you have a saved question, or a
set question you want to display, you can use the result only mode by populating the question in your embed
config.
Here is a look at what the JavaScript code will look like.

// Embed configuration used to describe the what and how to embed.

// This object is used when calling powerbi.embed within the JavaScript API.
// You can find more information at https://github.com/Microsoft/PowerBI-JavaScript/wiki/Embed-Configuration-
Details.
var config= {
type: 'qna',
tokenType: models.TokenType.Embed | models.TokenType.Aad,
accessToken: access token value,
embedUrl: https://app.powerbi.com/qnaEmbed (groupId to be appended as query parameter if required),
datasetIds: array of requested data set ids (at the moment we support only one dataset),
viewMode: models.QnAMode.Interactive | models.QnAMode.ResultOnly,
question: optional parameter for Explore mode (QnAMode.Interactive) and mandatory for Render Result
mode (QnAMode.ResultOnly)
};

// Get a reference to the embedded QNA HTML element

var qnaContainer = $('#qnaContainer')[0];

// Embed the QNA and display it within the div container.

var qna = powerbi.embed(qnaContainer, config);

Set question
If you used result mode with a set question, you can inject additional questions into the frame and have them
immediately answered replacing the previous result. A new visual is rendered matching the new question.
One example of this usage would be a frequently asked question list. The user could go through the questions and
have them answered within the same embedded part.
Code snippet for JS SDK usage:

// Get a reference to the embedded Q&A HTML element

var qnaContainer = $('#qnaContainer')[0];

// Get a reference to the embedded Q&A.

qna = powerbi.get(qnaContainer);

qna.setQuestion("This year sales")

.then(function (result) {
…….
})
.catch(function (errors) {
…….
});

Visual rendered event

For interactive mode, the application can be notified with a data changed event each time the rendered visual
changes to target the updated input query as it is being typed.
Listening to the visualRendered event allows you to save questions for use later.
Code snippet for JS SDK usage:

// Get a reference to the embedded Q&A HTML element

var qnaContainer = $('#qnaContainer')[0];

// Get a reference to the embedded Q&A.

qna = powerbi.get(qnaContainer);

// qna.off removes a given event listener if it exists.

qna.off("visualRendered");

// qna.on will add an event listener.

qna.on("visualRendered", function(event) {
…….
});

Embed token
Create an embed token off of a dataset to start a Q&A part. For more information, see Generate token.

Next steps
To give Q&A embedding a try, check out the JavaScript embed sample.
More questions? Try asking the Power BI Community
 Create Power BI Embedded capacity in the Azure
portal
2/6/2019 • 2 minutes to read • Edit Online

This article walks through how to create a Power BI Embedded capacity in Microsoft Azure. Power BI
Embedded simplifies Power BI capabilities by helping you quickly add stunning visuals, reports, and
dashboards to your apps.
If you don't have an Azure subscription, create a free account before you begin.

Before you begin

To complete this quickstart, you need:
Azure subscription: Visit Azure Free Trial to create an account.
Azure Active Directory: Your subscription must be associated with an Azure Active Directory (AAD )
tenant. Also, you need to be signed in to Azure with an account in that tenant. Microsoft accounts aren't
supported. To learn more, see Authentication and user permissions.
Power BI tenant: At least one account in your AAD tenant must have signed up for Power BI.
Resource group: Use a resource group you already have or create a new one.

Create a capacity
1. Sign into the Azure portal.
2. In the search box, search for Power BI Embedded.
3. Within Power BI Embedded, select Create.
4. Fill in the required information and then select Create.
SETTING DESCRIPTION

Resource name A name to identify the capacity. The resource name is

displayed within the Power BI admin portal in addition
to the Azure portal.

Subscription The subscription you would like to create the capacity

against.

Resource group The resource group that contains this new capacity. Pick
from an existing resource group, or create another. For
more information, see Azure Resource Manager
overview.

Power BI capacity administrator Power BI capacity administrators can view the capacity in
the Power BI admin portal and give assignment
permissions to other users. By default, the capacity
administrator is your account. The capacity administrator
must be within your Power BI tenant.
 SETTING DESCRIPTION

Location The location where Power BI is hosted for your tenant.

Your default location is your home region, but you can
change the location using Multi-Geo options.

Pricing tier Select the SKU (v-core count and memory size) that
meets your needs. For details, see Power BI Embedded
pricing

You can navigate to All services > Power BI Embedded to see if your capacity is ready. Alternatively, you can
select Pin to dashboard from the notifications section or from within the blade, to navigate to your dashboard
to see your new capacity.

Next steps
To use your new Power BI Embedded capacity, browse to the Power BI admin portal to assign workspaces. For
more information, see Manage capacities within Power BI Premium and Power BI Embedded.
If you don't need to use this capacity, you can pause it to stop billing. For more information, see Pause and start
your Power BI Embedded capacity in the Azure portal.
To begin embedding Power BI content within your application, see How to embed your Power BI dashboards,
reports, and tiles.
More questions? Try asking the Power BI Community
 Multi-Geo support for Power BI Embedded
3/7/2019 • 2 minutes to read • Edit Online

Multi-Geo support for Power BI Embedded means that ISVs and organizations that build applications using
Power BI Embedded to embed analytics into their apps can now deploy their data in different regions around the
world.
Now customers using Power BI Embedded can set up an A capacity using Multi-Geo options, based on the
same features and limitations that Power BI Premium supports using Multi-Geo.

Creating new Power BI Embedded Capacity resource with Multi-Geo

In the Create resource screen, you need to choose the location of your capacity. Until now, it was limited only to
the location of your Power BI tenant, so only a single location was available. With Multi-Geo, you can choose
between different regions to deploy your capacity.
Notice that when opening the location drop-down menu, your home tenant is the default selection.
When choosing a different location, a message prompts you to make sure you're aware of the selection.

View Capacity location

You can see your capacities location easily when going to the main Power BI Embedded management page in the
Azure portal.

It’s also available in the Admin Portal in Powerbi.com. In the Admin portal, choose ‘Capacity settings,’ and then
switch to ‘Power BI Embedded’ tab.

Learn more about creating capacities with Power BI Embedded.

Manage existing capacities location
You can't change a Power BI Embedded resource location once you've created a new capacity.
To move your Power BI content to a different region, follow these steps:
1. Create a new capacity in a different region.
2. Assign all workspaces from the existing capacity to the new capacity.
3. Delete or pause the old capacity.
It’s important to note that if you decide to delete a capacity without reassigning its content, all the content in that
capacity moves to a shared capacity, which is in your home region.

API support for Multi-Geo

To support management of capacities with Multi-Geo through API, we have made some changes to existing APIs:
1. Get Capacities - The API returns a list of capacities with access to the user. The response now includes an
additional property called ‘region,’ that specifies the capacity’s location.
2. Assign To Capacity - The API allows assigning a given workspace to a capacity. This operation doesn't
allow you to assign workspaces to a capacity outside of your home region or move workspaces between
capacities in different regions. To perform this operation, the user or service principal still needs admin
permissions on the workspace, and admin or assign permissions on the target capacity.
3. Azure Resource Manager API - all of the Azure Resource Manager API operations, including Create and
Delete, supports Multi-Geo.

Limitations and considerations

Confirm that any movement you initiate between regions follows all corporate and government
compliance requirements before initiating data transfer.
A cached query stored in a remote region stays in that region at rest. However, other data in transit may
go back and forth between different geographies.
When moving data from one region to another in a Multi-Geo environment, the source data may stay in
the region from which the data was moved for up to 30 days. During that time, users don't have access to
it. It's removed from this region and destroyed during the 30-day period.
Multi-Geo doesn't result in better performance in general. Loading reports and dashboards still involve
requests to the home region for metadata.

Next steps
Learn more about Power BI Embedded capacities and Multi-Geo options for all capacities by referencing the links
below.
What is Power BI Embedded?
Create a Power BI Embedded capacity
Multi-Geo in Power BI Premium capacities
More questions? Try asking the Power BI Community
 Scale your Power BI Embedded capacity in the Azure
portal
2/6/2019 • 2 minutes to read • Edit Online

This article walks through how to scale a Power BI Embedded capacity in Microsoft Azure. Scaling allows you to
increase or decrease the size of your capacity.
This assumes you have created a Power BI Embedded capacity. If you have not, see Create Power BI Embedded
capacity in the Azure portal to get started.

NOTE
A scaling operation can take about a minute. During this time, the capacity will not be available. Embedded content may fail
to load.

Scale a capacity
1. Sign into the Azure portal.
2. Select All services > Power BI Embedded to see your capacities.

3. Select the capacity you want to scale.

4. Select Pricing tier under Scale within your capacity.

Your current pricing tier is outlined in blue.

5. To scale up or down, select the new tier to move to. Selecting a new tier places a dashed blue outline around
the selection. Select Select to scale to the new tier.

Scaling your capacity may take a minute or two to complete.

6. Confirm your tier by viewing the overview tab. The current pricing tier is listed.
Next steps
To pause or start your capacity, see Pause and start your Power BI Embedded capacity in the Azure portal .
To begin embedding Power BI content within your application, see How to embed your Power BI dashboards,
reports, and tiles.
More questions? Try asking the Power BI Community
 Pause and start your Power BI Embedded capacity in
the Azure portal
7/30/2018 • 2 minutes to read • Edit Online

This article walks through how to pause and start a Power BI Embedded capacity in Microsoft Azure. This
assumes you have created a Power BI Embedded capacity. If you have not, see Create Power BI Embedded
capacity in the Azure portal to get started.
If you don't have an Azure subscription, create a free account before you begin.

Pause your capacity

Pausing your capacity prevents you from being billed. Pausing your capacity is great if you do not need to use the
capacity for a period of time. Use the following steps to pause your capacity.

NOTE
Pausing a capacity may prevent content from being available within Power BI. Make sure to unassign workspaces from your
capacity before pausing to prevent interruption.

1. Sign into the Azure portal.

2. Select All services > Power BI Embedded to see your capacities.

3. Select the capacity you want to pause.

4. Select Pause within the capacity details.

5. Select Yes, which confirms you want to pause the capacity.

Start your capacity

Resume usage by starting your capacity. Starting your capacity also resumes billing.
1. Sign into the Azure portal.
2. Select All services > Power BI Embedded to see your capacities.
3. Select the capacity you want to start.

4. Select Start within the capacity details.

5. Select Yes, which confirms you want to start the capacity.

If any content is assigned to this capacity, it is available once started.

Next steps
If you want to scale your capacity up or down, see Scale your Power BI Embedded capacity.
To begin embedding Power BI content within your application, see How to embed your Power BI dashboards,
reports and tiles.
More questions? Try asking the Power BI Community
 Troubleshoot your embedded application
3/18/2019 • 10 minutes to read • Edit Online

This article discusses some common issues you may get when embedding content from Power BI.

Tools to troubleshoot
Fiddler Trace
Fiddler is a free tool from Telerik that monitors HTTP traffic. You can see the traffic with the Power BI APIs from
the client machine. This tool may show errors and other related information.

F12 in Browser for front-end debugging

F12 launches the developer window within your browser. This tool provides the ability to look at network traffic
and other information.

Extract error details from Power BI response

This code snippet shows how to extract the error details from HTTP exception:

public static string GetExceptionText(this HttpOperationException exc)

{
var errorText = string.Format("Request: {0}\r\nStatus: {1} ({2})\r\nResponse: {3}",
exc.Request.Content, exc.Response.StatusCode, (int)exc.Response.StatusCode, exc.Response.Content);
if (exc.Response.Headers.ContainsKey("RequestId"))
{
var requestId = exc.Response.Headers["RequestId"].FirstOrDefault();
errorText += string.Format("\r\nRequestId: {0}", requestId);
}

return errorText;
}

We recommend logging the Request ID (and error details for troubleshooting). Provide the Request ID when
approaching Microsoft support.
App registration
App registration failure
Error messages within the Azure portal or the Power BI app registration page mention insufficient privileges. To
register an application, you must be an admin in the Azure AD tenant or application registrations must be enabled
for non-admin users.
Power BI Service doesn't appear in the Azure portal when registering a new App
At least one user must be signed up for Power BI. If you don't see Power BI Service listed within the API list, no
user is signed up for Power BI.

REST API
API call returning 401
A fiddler capture may be required to investigate further. The required permission scope may be missing for the
registered application within Azure AD. Verify the required scope is present within the app registration for Azure
AD within the Azure portal.
API call returning 403
A fiddler capture may be required to investigate further. There could be several reasons for a 403 error.
The user has exceeded the amount of embed token that can be generated on a shared capacity. Purchase Azure
capacities to generate embed tokens and assign the workspace to that capacity. See Create Power BI Embedded
capacity in the Azure portal.
The Azure AD auth token expired.
The authenticated user isn't a member of the group (app workspace).
The authenticated user isn't an admin of the group (app workspace).
The authorization header may not be listed correctly. Make sure there are no typos.
The backend of the application may need to refresh the auth token before calling GenerateToken.

```
GET https://wabi-us-north-central-redirect.analysis.windows.net/metadata/cluster HTTP/1.1
Host: wabi-us-north-central-redirect.analysis.windows.net
...
Authorization: Bearer eyJ0eXAiOi...
...

HTTP/1.1 403 Forbidden

...

{"error":{"code":"TokenExpired","message":"Access token has expired, resubmit with a new access token"}}

```

Authentication
Authentication failed with AADSTS90002: Tenant 'authorize' not found
If you're receiving messages logging in such as error: invalid_request, error_description: AADSTS90002:
Tenant 'authorize' not found, that is because ADAL 4.x doesn't support
"https://login.microsoftonline.com/{Tenant}/oauth2/authorize/" as an authority url.
To resolve this issue you should trim "oauth2/authorize/" from the end of your authority url, see Power BI
Developer Samples for reference.
Check Better Authority validation from ADAL 4.x release notes.
Authentication failed with AADSTS70002 or AADSTS50053
(AADSTS70002: Error validating credentials. AADSTS50053: You've tried to sign in too many times with
an incorrect User ID or password)
If you're using Power BI Embedded and using Azure AD Direct authentication, and you're receiving messages
logging in such as error:unauthorized_client, error_description:AADSTS70002: Error validating credentials.
AADSTS50053: You've tried to sign in too many times with an incorrect User ID or password, that is because
direct authentication is no longer in use since June 14, 2018 by default.
There's a way to turn this back on using an Azure AD Policy that is scoped to the organization or a service
principal.
We recommend you enable this policy only as a per-app basis.
To create this policy, you need to be a Global Administrator for the directory where you’re creating the policy
and assigning. Here is a sample script for creating the policy and assigning it to the SP for this application:
1. Install the Azure AD Preview PowerShell Module.
2. Run the following PowerShell commands line-by-line (making sure the variable $sp doesn’t have more
than one application as a result).

Connect-AzureAD

$sp = Get-AzureADServicePrincipal -SearchString "Name_Of_Application"

$policy = New-AzureADPolicy -Definition @("{`"HomeRealmDiscoveryPolicy`":

{`"AllowCloudPasswordValidation`":true}}") -DisplayName EnableDirectAuth -Type HomeRealmDiscoveryPolicy -
IsOrganizationDefault $false

Add-AzureADServicePrincipalPolicy -Id $sp.ObjectId -RefObjectId $policy.Id

After assigning the policy, wait approximately 15-20 seconds for propagation before testing.
Generate token fails when providing effective identity
GenerateToken can fail, with effective identity supplied, for a few different reasons.
Dataset doesn't support effective identity
Username wasn't provided
Role wasn't provided
DatasetId wasn't provided
User doesn't have the correct permissions
To verify which it is, try the steps below.
Execute get dataset. Is the property IsEffectiveIdentityRequired true?
Username is mandatory for any EffectiveIdentity.
If IsEffectiveIdentityRolesRequired is true, Role is required.
DatasetId is mandatory for any EffectiveIdentity.
For Analysis Services, the master user has to be a gateway admin.
AADSTS90094: The grant requires admin permission
Symptoms:
When a non-admin user tries to sign in to an application for the first time while granting consent, then gets one of
the following errors:
ConsentTest needs permission to access resources in your organization that only an admin can grant. Ask
an admin to grant permission to this app before you can use it.
AADSTS90094: The grant requires admin permission.

An admin user can sign in and grant consent successfully.

Root cause:
User consent is disabled for the tenant.
Several fixes are possible:
Enable user consent for the entire tenant (all users, all applications)
1. In the Azure portal, navigate to "Azure Active Directory" => "Users and groups" => "User settings"
2. Enable the "Users can consent to apps accessing company data on their behalf" setting and save the
changes

Grant permissions to the application by an admin - either for the entire tenant or a specific user.

Data sources
ISV wants to have different credentials for the same data source
A data source can have a single set of credentials for one master user. If you need to use different credentials,
create additional master users. Then, assign the different credentials in each of the master users contexts, and
embed using the Azure AD token of that user.

Troubleshoot your embedded application with the IError object

Use the IError object returned by the error event from the JavaScript SDK to debug your application and better
understand the cause of your errors.
After acquiring the IError object, you should look at the appropriate common errors table that fits the embed type
you're using. Compare the IError properties with the ones in the table and find the possible reason(s) for the
failure.
Typical errors when embedding for Power BI users
MESSAGE DETAILED MESSAGE ERROR CODE POSSIBLE REASON(S)

TokenExpired Access token has expired, 403 Expired token

resubmit with a new access
token

PowerBIEntityNotFound Get report failed 404 Wrong Report ID

Report doesn’t exist

Invalid parameters powerbiToken parameter N/A No access token provided

not specified No Report ID provided

LoadReportFailed Fail to initialize - Couldn't 403 * Bad access token * Embed

resolve cluster type doesn't match token
type

PowerBINotAuthorizedExcep Get report failed 401 Wrong group ID

tion Unauthorized group

TokenExpired Access token has expired, N/A Query data Expired token
resubmit with a new access
token. Couldn't render a
report visual titled:

OpenConnectionError Can't display the visual. N/A Capacity paused or deleted

Couldn't render a report while a report related to the
visual titled: capacity was open in a
session

ExplorationContainer_FailedT Couldn't load the model N/A Capacity paused

oLoadModel_DefaultDetails schema associated with this Capacity deleted
report. Make sure you have
a connection to the server
and try again.

Typical errors when embedding for non-Power BI users (using an Embed Token)
MESSAGE DETAILED MESSAGE ERROR CODE REASON(S)

TokenExpired Access token has expired, 403 Expired token

resubmit with a new access
token
 MESSAGE DETAILED MESSAGE ERROR CODE REASON(S)

LoadReportFailed Get report failed 404 Wrong Report ID

Report doesn’t exist

LoadReportFailed Get report failed 403 Report ID doesn't match

token

LoadReportFailed Get report failed 500 Report provided ID isn't a

guid

Invalid parameters powerbiToken parameter N/A No access token provided

not specified No Report ID provided

LoadReportFailed Fail to initialize - Couldn't 403 Wrong token type, Bad

resolve cluster Token

PowerBINotAuthorizedExcep Get report failed 401 Wrong/unauthorize group

tion ID

TokenExpired Access token has expired, N/A Query data Expired token
resubmit with a new access
token. Couldn't render a
report visual titled:

OpenConnectionError Can't display the visual. N/A Capacity paused or deleted

Couldn't render a report while a report related to the
visual titled: capacity was open in a
session

ExplorationContainer_FailedT Couldn't load the model N/A Capacity paused

oLoadModel_DefaultDetails schema associated with this Capacity deleted
report. Make sure you have
a connection to the server
and try again.

Content rendering
Performance
Power BI Embedded performance
Rendering, or consumption, of embedded content, fails or times out
Make sure the embed token did not expire. Make sure you're checking the embed token expiration and refreshing
it. For more information, see Refresh token using JavaScript SDK.
Report or dashboard doesn't load
If the user is unable to see the report or dashboard, make sure the report or dashboard loads correctly within
powerbi.com. The report or dashboard doesn't work within your application if it doesn't load within powerbi.com.
Report or dashboard is performing slowly
Open the file from Power BI Desktop, or within powerbi.com, and verify that performance is acceptable to rule out
issues with your application or the embedding APIs.

Embed setup tool

You can go through the Embedding setup tool to quickly download a sample application. Then you can compare
your application to the sample.
Prerequisites
Verify that you have all the proper prerequisites before using the Embedding setup tool. You need a Power BI Pro
account and a Microsoft Azure subscription.
If you're not signed up for Power BI Pro, sign up for a free trial before you begin.
If you don’t have an Azure subscription, create a free account before you begin.
You need to have your own Azure Active Directory tenant setup.
You need Visual Studio installed (version 2013 or later).
Common Issues
Some common issues you might encounter while testing with the Embed setup tool are:
Using the Embed for your customers sample application
If you're working with the Embed for your customers experience, save and unzip the PowerBI -Developer-
Samples.zip file. Then open the PowerBI -Developer-Samples-master\App Owns Data folder and run the
PowerBIEmbedded_AppOwnsData.sln file.
When selecting Grant permissions (the Grant permissions step), you get the following error:

AADSTS70001: Application with identifier <client ID> wasn't found in the directory <directory ID>

The solution is to close the popup, wait a few seconds and try again. You might need to repeat this action a few
times. A time interval causes the issue from completing the application registration process to when it's available
to external APIs.
The following error message appears when running the sample app:

Password is empty. Please fill password of Power BI username in web.config.

This error occurs because the only value that isn't being injected into the sample application is your user password.
Open the Web.config file in the solution and fill the pbiPassword field with your user's password.
If you get the error - AADSTS50079: The user is required to use multi-factor authentication.

Need to use an AAD account that doesn't have MFA enabled.

Using the Embed for your organization sample application

If you're working with the Embed for your organization experience, save and unzip the PowerBI -Developer-
Samples.zip file. Then open the PowerBI -Developer-Samples-master\User Owns Data\integrate-report-web -app
folder and run the pbi-saas-embed -report.sln file.
When you run the Embed for your organization sample app, you get the following error:

AADSTS50011: The reply URL specified in the request doesn't match the reply URLs configured for the
application: <client ID>

This error is because the redirect URL specified for the web-server application is different from the sample's URL.
If you want to register the sample application, then use http://localhost:13526/ as the redirect URL.
If you'd like to edit the registered application, then learn how to update the Azure AD -registered application, so the
application can provide access to the web APIs.
If you would like to edit your Power BI user profile or data, then learn how to edit your Power BI data.
If you get the error - AADSTS50079: The user is required to use multi-factor authentication.

Need to use an AAD account that doesn't have MFA enabled.

For more information, please see Power BI Embedded FAQ.

More questions? Try the Power BI Community
If you require further assistance, then contact support or create a support ticket via the Azure portal and provide
the error messages you encounter.

Next steps
For more information, see FAQs.
More questions? Try the Power BI Community
 How to migrate Power BI Workspace Collection content to
Power BI Embedded
2/13/2019 • 8 minutes to read • Edit Online

Learn how to migrate from Power BI Workspace Collection to Power BI Embedded and leverage advances for embedding in
apps.
Microsoft recently announced Power BI Embedded, a new capacity-based licensing model that increases flexibility for how users
access, share and distribute content. The offering also delivers additional scalability and performance.
With Power BI Embedded, you will have one API surface, a consistent set of capabilities and access to the latest Power BI
features – such as dashboards, gateways and app workspaces – when embedding your content. Moving forward you’ll be able to
start with Power BI Desktop and move to deployment with Power BI Embedded.
The current Power BI Workspace Collection will continue to be available for a limited time. Customers under an Enterprise
Agreement will have access through the expiration of their existing agreements; customers that acquired Power BI Workspace
Collection through Direct or CSP channels will maintain access for one year from the General Availability release of Power BI
Embedded. This article will provide some guidance for migrating from Power BI Workspace Collection to the new Power BI
Embedded experience and what to expect for changes in your application.

IMPORTANT
While the migration will take a dependency on Power BI Embedded, there is not a dependency on Power BI for the users of your application
when using an embed token. They do not need to sign up for Power BI to view the embedded content in your application. You can use this
embedding approach to Embedded non-Power BI users.

Before you get started migrating to the new Power BI Embedded, you can quickly go through a walkthrough that helps you set
up your new Power BI Embedded environment using the Embedding setup tool.
Choose the solution that is right for you:
Embed for your customers - when you are interested in an app owns data solution. Embedding for your customers
provides the ability to embed dashboards and reports to users who don't have an account for Power BI.
Embed for your organization - when you are interested in a user owns data solution. Embedding for your organization
allows you to extend the Power BI service.

Prepare for the migration

There are a few things you need to do to prepare for migrating from Power BI Workspace Collection to Power BI Embedded.
You will need a tenant available, along with a user that has a Power BI Pro license.
1. Make sure you have access to an Azure Active Directory (Azure AD ) tenant.
You need to determine which tenant setup to use.
Use your existing corporate Power BI tenant?
Use a separate tenant for your application?
Use a separate tenant for each customer?
If you decide to create a new tenant for your application, or each customer, see Create an Azure Active Directory
tenant or How to get an Azure Active Directory tenant.
2. Create a user within this new tenant that will act as your application "master" account. That account needs to sign up for
Power BI and needs to have a Power BI Pro license assigned to it.

Accounts within Azure AD

The following accounts will need to exist within your tenant.

NOTE
These accounts will need to have Power BI Pro licenses in order to use App workspaces.

1. A tenant admin user.

It is recommended that this user be a member of all App workspaces created for the purpose of embedding.
2. Accounts for analysts that will create content.
These users should be assigned to App workspaces as needed.
3. An application master user account, or Embedded account.
The applications backend will store the credentials for this account and use it for acquiring an Azure AD token for use
with the Power BI REST APIs. This account will be used to generate the embed token for the application. This account also
needs to be an admin of the App workspaces created for embedding.

NOTE
This is just a regular user account in your organization that will be used for the purposes of embedding.

App registration and permissions

You will need to register an application within Azure AD and grant certain permissions.
Register an application
You will need to register your application with Azure AD in order to make REST API calls. This includes going to the Azure
portal to apply additional configuration in addition to the Power BI app registration page. For more information, see Register an
Azure AD app to embed Power BI content.
You should register the application using the application master account.
Create App workspaces (Required)
You can take advantage of App workspaces to provide better isolation if your application is servicing multiple customers.
Dashboards and reports would be isolated between your customers. You could then use a Power BI account per App workspace
to further isolate application experiences between your customers.

IMPORTANT
You cannot use a personal workspace to take advantage of embedding to non-Power BI users.

You will need a user that has a Pro license in order to create an app workspace within Power BI. The Power BI user that creates
the App workspace will be an admin of that workspace by default.

NOTE
The application master account needs to be an admin of the workspace.

Content migration
Migrating your content from your workspace collections to Power BI Embedded can be done in parallel to your current solution
and doesn’t require any downtime.
A migration tool is available for you to use in order to assist with copying content from Power BI Workspace Collection to
Power BI Embedded. Especially if you have a lot of content. For more information, see Power BI Embedded migration tool.
Content migration relies mainly on two APIs.
1. Download PBIX - this API can download PBIX files which were uploaded to Power BI after October 2016.
2. Import PBIX - this API uploads any PBIX to Power BI.
For some related code snippets, see Code snippets for migrating content from Power BI Workspace Collection.
Report types
There are several types of reports, each requiring a somewhat different migration flow.
Cached dataset & report
Cached datasets refer to PBIX files that had imported data as opposed to a live connection or DirectQuery connection.
Flow
1. Call Download PBIX API from PaaS workspace.
2. Save PBIX.
3. Call Import PBIX to SaaS workspace.
DirectQuery dataset & report
Flow
1. Call GET
https://api.powerbi.com/v1.0/collections/{collection_id}/workspaces/{wid}/datasets/{dataset_id}/Default.GetBoundGatewayDataSources
and save connection string received.
2. Call Download PBIX API from PaaS workspace.
3. Save PBIX.
4. Call Import PBIX to SaaS workspace.
5. Update connection string by calling - POST
https://api.powerbi.com/v1.0/myorg/datasets/{dataset_id}/Default.SetAllConnections
6. Get GW id and datasource id by calling - GET
https://api.powerbi.com/v1.0/myorg/datasets/{dataset_id}/Default.GetBoundGatewayDataSources
7. Update user's credentials by calling - PATCH
https://api.powerbi.com/v1.0/myorg/gateways/{gateway_id}/datasources/{datasource_id}
Old dataset & reports
These are datasets/reports created before October 2016. Download PBIX doesn't support PBIXs which were uploaded before
October 2016
Flow
1. Get PBIX from your development environment (your internal source control).
2. Call Import PBIX to SaaS workspace.
Push Dataset & report
Download PBIX doesn't support Push API datasets. Push API dataset data can't be ported from PaaS to SaaS.
Flow
1. Call "Create dataset" API with dataset Json to create dataset in SaaS workspace.
2. Rebuild report for the created dataset*.
It is possible, using some workarounds, to migrate the push api report from PaaS to SaaS by trying the following.
1. Uploading some dummy PBIX to PaaS workspace.
2. Clone the push api report and bind it to the dummy PBIX from step 1.
3. Download push API report with the dummy PBIX.
4. Upload dummy PBIX to your SaaS workspace.
5. Create push dataset in your SaaS workspace.
6. Rebind report to push api dataset.

Create and upload new reports

In addition to the content you migrated from the Power BI Workspace Collection, you can create your reports and datasets using
Power BI Desktop and then publish those reports to an app workspace. The end user publishing the reports need to have a
Power BI Pro license in order to publish to an app workspace.

Rebuild your application

1. You will need to modify your application to use the Power BI REST APIs and the report location inside powerbi.com.
2. Rebuild your AuthN/AuthZ authentication using the master account for your application. You can take advantage of using an
embed token to allow this user to act on behalf of other users.
3. Embed your reports from powerbi.com into your application.

Map your users to a Power BI user

Within your application, you will map users that you manage within the application to a master Power BI credential for the
purposes of your application. The credentials for this Power BI master account will be stored within your application and be used
to creating embed tokens.

What to do when you are ready for production

When you are ready to move to production, you will need to do the following.
If you are using a separate tenant for development, then you will need to make sure your app workspaces, along with
dashboards and reports, are available in your production environment. You will also need to make sure that you created
the application in Azure AD for your production tenant and assigned the proper app permissions as indicated in Step 1.
Purchase a capacity that fits your needs. To better understand how the amount and type of capacity you need, see the
Power BI Embedded analytics capacity planning whitepaper. You can purchase capacity in Azure.
Edit the App workspace and assign it to a Premium capacity under advanced.
 Deploy your updated application to production and begin embedding reports from the Power BI Embedded.

After migration
You should do some cleanup within Azure.
Remove all workspaces off of the deployed solution within the Azure Embedded of Power BI Workspace Collection.
Delete any Workspace Collections that exist within Azure.

Next steps
Embedding with Power BI
Power BI Workspace Collection migration tool
Code snippets for migrating content from Power BI Workspace Collection
How to embed your Power BI dashboards, reports and tiles
Power BI Premium - what is it?
JavaScript API Git repo
Power BI C# Git repo
JavaScript embed sample
Workspace Collection analytics capacity planning whitepaper
Power BI Premium whitepaper
More questions? Try asking the Power BI Community
 Power BI Embedded migration tool
2/13/2019 • 8 minutes to read • Edit Online

This migration tool can be used to copy your reports from the Power BI Embedded Azure service (PaaS ) to the
Power BI service (SaaS ).
Migrating your content from your workspace collections to the Power BI service can be done in parallel to your
current solution and doesn’t require any downtime.

Limitations
Pushed datasets cannot be downloaded and will need to be recreated using the Power BI REST APIs for the
Power BI service.
PBIX files imported before November 26, 2016 will not be downloadable.

Download
You can download the migration tool sample from GitHub. You can either download a zip of the repository, or you
can clone it locally. Once downloaded, you can open powerbi-migration-sample.sln within Visual Studio to build
and run the migration tool.

Migration Plans
Your migration plan is just metadata that catalogs the content within Power BI Embedded and how you want to
publish them to the Power BI service.
Start with a new migration plan
A migration plan is the metadata of the items available in Power BI Embedded that you then want to move over to
the Power BI service. The migration plan is stored as an XML file.
You will want to start by creating a new migration plan. To create a new migration plan, do the following.
1. Select File > New Migration Plan.

2. In the Select Power BI Embedded Resource Group dialog, you will want to select the Environment
dropdown and select prod.
3. You will be prompted to sign in. You will use your Azure subscription login.

IMPORTANT
This is not your Office 365 organization account that you sign into Power BI with.

4. Select the Azure subscription which stores your Power BI Embedded workspace collections.
5. Below the subscription list, select the Resource Group that contains your workspace collections and select
Select.

6. Select Analyze. This will get an inventory of the items within your Azure subscription for you to begin your
plan.

NOTE
The analyze process could take several minutes depending on the number of Workspace collections and how much
content exists in the workspace collection.

7. When Analyze is complete, it will prompt you to save your migration plan.
At this point, you have connected your migration plan to your Azure subscription. Read below to understand the
flow of how to work with your migration plan. This includes Analyze & Plan Migration, Download, Create Groups
and Upload.
Save your migration plan
You can save your migration plan for use later. This will create an XML file that contained all the information in
your migration plan.
To save your migration plan, do the following.
1. Select File > Save Migration Plan.

2. Give your file a name or use the generated file name and select Save.
Open an existing migration plan
You can open a saved migration plan to continue working on your migration.
To open your existing migration plan, do the following.
1. Select File > Open Existing Migration Plan.

2. Select your migration file and select Open.

Step 1: Analyze & Plan Migration

The Analyze & Plan Migration tab gives you a view of what is currently in your Azure subscription’s resource
group.

We will look at the SampleResourceGroup as an example.

PaaS Topology
This is a listing of your Resource Group > Workspace collections > Workspaces. The resource group and
workspace collections will show a friendly name. The workspaces will show a GUID.
The items in the list will also display a color and a number in the format of (#/#). This indicates the number of
reports that can be downloaded. A black color means that all reports can be downloaded.
A red color means that some reports cannot be downloaded. The left number will indicate the total number of
reports that can be downloaded. The number on the right indicates the total number of reports within the
grouping.
You can select an item within the PaaS topology to display the reports in the reports section.
Reports
The reports section will list out the reports available and indicates whether it can be downloaded or not.
Target structure
The Target structure is where you tell the tool where things will be downloaded to and how to upload them.
Download Plan
A path will automatically be created for you. You can change this path if you wish. If you do change the path, you
will need to select Update paths.

NOTE
This does not actually perform the download. This is only specifying the structure of where the reports will be downloaded
to.

Upload Plan
Here you can specify a prefix to be used for the App Workspaces that will be created within the Power BI service.
After the prefix will be the GUID for the workspace that existed in Azure.

NOTE
This does not actually create the groups within the Power BI service. This only defines the naming structure for the groups.

If you change the prefix, you will need to select Generate Upload Plan.
You can right click on a group and choose to rename the group within the Upload plan directly, if desired.
 NOTE
The name of the group must not contain spaces or invalid characters.

Step 2: Download
On the Download tab, you will see the list of reports and associated metadata. You can see what the export status
is along with the previous export status.

You have two options.

Select specific reports and select Download Selected
Select Download All.

For a successful download, you will see a status of Done and it will reflect that the PBIX file exists.
After the download is completed, select the Create Groups tab.
Step 3: Create Groups
After you have downloaded the reports that are available, you can go to the Create Groups tab. This tab will
create the app workspaces within the Power BI service based on the migration plan that you created. It will create
the app workspace with the name you provided on the Upload tab within Analyze & Plan Migration.

To create the app workspaces, you can select either Create Selected Groups or Create All Missing Groups.
When you select either of these options, you will be prompted to sign in. You will want to use your credentials for
the Power BI service that you want to create the app workspaces on.

This will create the app workspace within the Power BI service. This does not upload the reports to the app
workspace.
You can verify that the app workspace was created by signing into Power BI and validating that the workspace
exists. You will notice that nothing is in the workspace.

After the workspace is created, you can move onto the Upload tab.

Step 4: Upload
On the Upload tab, this will upload the reports to the Power BI service. You will see a list of the reports that we
downloaded on the Download tab along with the target group name based on your migration plan.
You can upload selected reports, or you could upload all the reports. You can also reset the upload status to re-
upload items.
You also have the option of selecting what to do if a report with the same name exists. You can choose between
Abort, Ignore and Overwrite.

Duplicate report names

If you have a report that has the same name, but you know it is a different report, you will need to change the
TargetName of the report. You can change the name by manually editing the migration plan XML.
You will need to close the migration tool to make the change and then re-open the tool and the migration plan.
In the above example, one of the cloned reports failed indicating a report with the same name existed. If we go
look at the migration plan XML, we will see the following.
 <ReportMigrationData>
<PaaSWorkspaceCollectionName>SampleWorkspaceCollection</PaaSWorkspaceCollectionName>
<PaaSWorkspaceId>4c04147b-d8fc-478b-8dcb-bcf687149823</PaaSWorkspaceId>
<PaaSReportId>525a8328-b8cc-4f0d-b2cb-c3a9b4ba2efe</PaaSReportId>
<PaaSReportLastImportTime>1/3/2017 2:10:19 PM</PaaSReportLastImportTime>
<PaaSReportName>cloned</PaaSReportName>
<IsPushDataset>false</IsPushDataset>
<IsBoundToOldDataset>false</IsBoundToOldDataset>
<PbixPath>C:\MigrationData\SampleResourceGroup\SampleWorkspaceCollection\4c04147b-d8fc-478b-8dcb-
bcf687149823\cloned-525a8328-b8cc-4f0d-b2cb-c3a9b4ba2efe.pbix</PbixPath>
<ExportState>Done</ExportState>
<LastExportStatus>OK</LastExportStatus>
<SaaSTargetGroupName>SampleMigrate</SaaSTargetGroupName>
<SaaSTargetGroupId>6da6f072-0135-4e6c-bc92-0886d8aeb79d</SaaSTargetGroupId>
<SaaSTargetReportName>cloned</SaaSTargetReportName>
<SaaSImportState>Failed</SaaSImportState>
<SaaSImportError>Report with the same name already exists</SaaSImportError>
</ReportMigrationData>

For the failed item, we can change the name of the SaaSTargetReportName.

<SaaSTargetReportName>cloned2</SaaSTargetReportName>

We can then re-open the plan, in the migration tool, and upload the failed report.
Going back to Power BI, we can see that the reports and datasets have been uploaded in the app workspace.

Upload a local PBIX file

You can upload a local version of a Power BI Desktop file. You will have to close the tool, edit the XML and put the
full path to your local PBIX in the PbixPath property.

<PbixPath>[Full Path to PBIX file]</PbixPath>

After you have edited the xml, re-open the plan within the migration tool and upload the report.
DirectQuery reports
You will need to update to update the connection string for DirectQuery reports. This can be done within
powerbi.com, or you can programmatically query the connection string from Power BI Embedded (PaaS ). For an
example, see Extract DirectQuery connection string from PaaS report.
You can then update the connection string for the dataset within the Power BI service (SaaS ) and set the
credentials for the data source. You can look at the following examples to see how to do this.
Update DirectQuery connection string is SaaS workspace
Set DirectQuery credentials in SaaS workspace

Embedding
Now that your reports have been migrated from the Power BI Embedded Azure service to the Power BI service,
you can now update your application and begin embedding the reports in this app workspace.
For more information, see How to migrate Power BI Embedded workspace collection content to Power BI.

Next steps
Embedding with Power BI
How to migrate Power BI Embedded workspace collection content to Power BI
Power BI Premium - what is it?
JavaScript API Git repo
Power BI C# Git repo
JavaScript embed sample
Power BI Premium whitepaper
More questions? Try asking the Power BI Community
 Code snippets for migrating content from Power BI
Workspace Collection
2/13/2019 • 4 minutes to read • Edit Online

Here are some code snippets of basic operations needed for content migration. For related flows for certain report
types, see How to migrate Power BI workspace collection content to Power BI Embedded.
A migration tool is available for you to use in order to assist with copying content from Power BI Embedded
(PaaS ) to the Power BI service (SaaS ). Especially if you have a lot of content. For more information, see Power BI
Embedded migration tool.
The code below are examples using C# and the Power BI .NET SDK.
Make sure you are using the following namespaces to execute the code snippets below.

using Microsoft.IdentityModel.Clients.ActiveDirectory;
using Microsoft.PowerBI.Api.V1;
using Microsoft.PowerBI.Api.V1.Models;
using Microsoft.PowerBI.Api.V2;
using Microsoft.PowerBI.Api.V2.Models;
using Microsoft.Rest;
using Microsoft.Rest.Serialization;
using Newtonsoft.Json;
using Newtonsoft.Json.Linq;
using System;
using System.Collections.Generic;
using System.IO;
using System.Linq;
using System.Net;
using System.Net.Http;
using System.Net.Http.Headers;
using System.Text;
using System.Threading.Tasks;

Export report from PaaS workspace

 // Create a token credentials with "AppKey" type
var credentials = new TokenCredentials(<myAppKey==>, "AppKey");

// Instantiate your Power BI client passing in the required credentials

var client = new PowerBIClient(credentials);

client.BaseUri = new Uri("https://api.powerbi.com");

var response = client.Reports.ExportReportWithHttpMessagesAsync(<myWorkspaceCollectionName>,

<myWorkspaceId>, <myReportId>);

if (response.Result.Response.StatusCode == HttpStatusCode.OK)
{
var stream = response.Result.Response.Content.ReadAsStreamAsync();

using (FileStream fileStream = File.Create(@"C:\Migration\myfile.pbix"))

{
stream.Result.CopyTo(fileStream);
fileStream.Close();
}
}

Import report to SaaS workspace

AuthenticationContext authContext = new
AuthenticationContext("https://login.microsoftonline.net/common/");
var PBISaaSAuthResult = authContext.AcquireToken("https://analysis.windows.net/powerbi/api", <myClientId>,
new Uri("urn:ietf:wg:oauth:2.0:oob"), PromptBehavior.Always);
var credentials = new TokenCredentials(PBISaaSAuthResult.AccessToken);
var client = new PowerBIClient(new Uri($"{"https://api.powerbi.com"}"), credentials);
using (var file = File.Open(@"C:\Migration\myfile.pbix", FileMode.Open))
{
client.Imports.PostImportWithFileInGroup(<mySaaSWorkspaceId>, file, "importedreport", "Abort");
while (true) ;
}

Extract DirectQuery connection string from PaaS report

This is for updating the PBIX after migrating to SaaS.

// Extract connection string from PaaS - DirectQuery report

// Create a token credentials with "AppKey" type
var credentials = new TokenCredentials(<myAppKey==>, "AppKey");

// Instantiate your Power BI client passing in the required credentials

var client = new PowerBIClient(credentials);

client.BaseUri = new Uri("https://api.powerbi.com");

var reports = client.Reports.GetReports(<myWorkspaceCollectionName>, <myWorkspaceId>);

Report report = reports.Value.FirstOrDefault(r => string.Equals(r.Id, <myReportId,

StringComparison.OrdinalIgnoreCase));

var datasource = client.Datasets.GetDatasources(<myWorkspaceCollectionName>, <myWorkspaceId>,

report.DatasetId);

Update DirectQuery connection string is SaaS workspace

 public class ConnectionString
{
[JsonProperty(PropertyName = "connectionString")]
public string connection { get; set; }
}

AuthenticationContext authContext = new

AuthenticationContext("https://login.microsoftonline.net/common/");
var PBISaaSAuthResult = authContext.AcquireToken("https://analysis.windows.net/powerbi/api",<myclient_id>,
new Uri("urn:ietf:wg:oauth:2.0:oob"), PromptBehavior.Always);
var credentials = new TokenCredentials(PBISaaSAuthResult.AccessToken);
var client = new PowerBIClient(new Uri($"{"https://api.powerbi.com"}"), credentials);

ConnectionString connection = new ConnectionString() { connection = "data source = <server_name>; initial

catalog = <db_name>; persist security info = True; encrypt = True; trustservercertificate = False" };

client.Datasets.SetAllConnectionsInGroup(<myWorkspaceId>, <dataset_id>, connection);

Set DirectQuery credentials in SaaS workspace

In this snippet, we are using unencrypted credentials for simplicity, sending encrypted credentials is supported as
well.

public class ConnectionString

{
[JsonProperty(PropertyName = "connectionString")]
public string connection { get; set; }
}

public class BasicCreds

{
[JsonProperty(PropertyName = "username")]
public string user { get; set; }

[JsonProperty(PropertyName = "password")]
public string pwd { get; set; }
}

var basicCreds = new BasicCreds() { user = <sqldb_username>, pwd = <sqldb_password> };

var body = new SetCredsRequestBody() { credentialType = "Basic", basicCredentials = basicCreds };

var url = string.Format("https://api.powerbi.com/v1.0/myorg/gateways/{0}/datasources/{1}", <gateway_id>,

<datasource_id>);
var request = new HttpRequestMessage(new HttpMethod("PATCH"), url);
// Set authorization header from you acquired Azure AD token
AuthenticationContext authContext = new
AuthenticationContext("https://login.microsoftonline.net/common/");
var PBISaaSAuthResult = authContext.AcquireToken("https://analysis.windows.net/powerbi/api",
<myclient_id>, new Uri("urn:ietf:wg:oauth:2.0:oob"), PromptBehavior.Always);

request.Headers.Authorization = new AuthenticationHeaderValue("Bearer", PBISaaSAuthResult.AccessToken);

request.Content = new StringContent(JsonConvert.SerializeObject(body), Encoding.UTF8, "application/json");

HttpClient simpleClient = new HttpClient();

var response = await simpleClient.SendAsync(request);

Push dataset & report

You will need to rebuild the report for the created dataset.
In this snippet, we assume that the pushable dataset is already in an app workspace within the SaaS environment.
For information about the push API, see Push data into a Power BI dataset.
 var credentials = new TokenCredentials(<Your WSC access key>, "AppKey");

// Instantiate your Power BI client passing in the required credentials

var client = new Microsoft.PowerBI.Api.V1.PowerBIClient(credentials);
client.BaseUri = new Uri("https://api.powerbi.com");

// step 1 -> create dummy dataset at PaaS workspace

var fileStream = File.OpenRead(<Path to your dummy dataset>);
var import = client.Imports.PostImportWithFileAsync(<Your WSC NAME>, <Your workspace ID>, fileStream,
"dummyDataset");
while (import.Result.ImportState != "Succeeded" && import.Result.ImportState != "Failed")
{
import = client.Imports.GetImportByIdAsync(<Your WSC NAME>, <Your workspace ID>, import.Result.Id);
Thread.Sleep(1000);
}
var dummyDatasetID = import.Result.Datasets[0].Id;

// step 2 -> clone the pushable dataset and rebind to dummy dataset
var cloneInfo = new Microsoft.PowerBI.Api.V1.Models.CloneReportRequest("pushableReportClone",null,
dummyDatasetID);
var clone = client.Reports.CloneReportAsync(<Your WSC NAME>, <Your workspace ID>, <Your pushable report
ID>, cloneInfo);
var pushableReportCloneID = clone.Result.Id;

// step 3 -> Download the push API clone report with the dummy dataset
var response = client.Reports.ExportReportWithHttpMessagesAsync(<Your WSC NAME>, <Your workspace ID>,
pushableReportCloneID);
if (response.Result.Response.StatusCode == HttpStatusCode.OK)
{
var stream = response.Result.Response.Content.ReadAsStreamAsync();
using (fileStream = File.Create(@"C:\Migration\PushAPIReport.pbix"))
{
stream.Result.CopyTo(fileStream);
fileStream.Close();
}
}

// step 4 -> Upload dummy PBIX to SaaS workspace

AuthenticationContext authContext = new
AuthenticationContext("https://login.microsoftonline.net/common/");
var PBISaaSAuthResult = authContext.AcquireToken("https://analysis.windows.net/powerbi/api", <Your client
ID>, new Uri("urn:ietf:wg:oauth:2.0:oob"), PromptBehavior.Always);
var credentialsSaaS = new TokenCredentials(PBISaaSAuthResult.AccessToken);
var clientSaaS = new Microsoft.PowerBI.Api.V2.PowerBIClient(new Uri($"{"https://api.powerbi.com"}"),
credentialsSaaS);
using (var file = File.Open(@"C:\Migration\PushAPIReport.pbix", FileMode.Open))
{

var importSaaS = clientSaaS.Imports.PostImportWithFileAsyncInGroup(<Your GroupID>, file,

"importedreport1", "Abort");
while (importSaaS.Result.ImportState != "Succeeded" && importSaaS.Result.ImportState != "Failed")
{
importSaaS = clientSaaS.Imports.GetImportByIdAsync(importSaaS.Result.Id);
Thread.Sleep(1000);
}
var importedreport1ID = importSaaS.Result.Reports[0].Id;

// step 5 -> Rebind report to "real" push api dataset

var rebindInfoSaaS = new Microsoft.PowerBI.Api.V2.Models.RebindReportRequest(<Your pushable dataset
ID at power bi>);
var rebindSaaS = clientSaaS.Reports.RebindReportInGroupWithHttpMessagesAsync(<Your GroupID>,
importedreport1ID, rebindInfoSaaS);

}
Next steps
Power BI Embedded migration tool
Embedding with Power BI
How to migrate Power BI Embedded workspace collection content to Power BI
How to embed your Power BI dashboards, reports and tiles
Power BI Premium - what is it?
JavaScript API Git repo
Power BI C# Git repo
JavaScript embed sample
Power BI Premium whitepaper
More questions? Try asking the Power BI Community
 Power BI REST API Reference
1/14/2019 • 2 minutes to read • Edit Online

Power BI is a cloud-based service that you can use to build custom dashboard applications. The Power BI REST API
is a REST-based API that provides programmatic access to Dashboard resources such as Datasets, Tables, and
Rows in Power BI.

NOTE
If you’re interested in viewing or deleting personal data, please review Microsoft's guidance in the Windows Data Subject
Requests for the GDPR site. If you’re looking for general information about GDPR, see the GDPR section of the Service Trust
portal.

The Power BI REST API has the following operations:

Dataset operations: Get and create Datasets.
Table operations: Get Tables and update Table schema.
Row operations: Add Rows and Delete Rows.
Group operations: Get Groups.
To learn more about the Power BI REST API, see Power BI REST API.
More questions? Try asking the Power BI Community
 Custom layouts
2/6/2019 • 2 minutes to read • Edit Online

Use custom layout to embed a report with different layout than in an original report. Defining a new layout varies
between defining only a page size, controlling visual sizes, or position and visibility.
To define a custom layout, define a custom layout object and pass it into the settings object in embed configuration.
In addition, set LayoutType to Custom. To learn more, see Embed Configuration Details.

var embedConfig = {
...
settings: {
layoutType: models.LayoutType.Custom
customLayout: {...}
}
};

Object Definition
interface ICustomLayout {
pageSize?: IPageSize;
displayOption?: DisplayOption;
pagesLayout?: PagesLayout;
}

enum PageSizeType {
Widescreen,
Standard,
Cortana,
Letter,
Custom
}
interface IPageSize {
type: PageSizeType;
}
interface ICustomPageSize extends IPageSize {
width?: number;
height?: number;
}

enum DisplayOption {
FitToPage,
FitToWidth,
ActualSize
}

pageSize : Use page size to control the canvas area size (i.e. report white area).
displayOptions : Possible values are: FitToWidth, FitToPage or ActualSize. It controls how to scale the canvas to
fit into the iframe.
pagesLayout : Controls the layout for each visual. see PagesLayout for more details.

Pages layout
Defining a pages layout object is basically defining a layout for each page, and for each page, you define a layout
for each visual. PageLayout is optional. If you don't define a layout for a page, the default layout (which is saved in
the report) will be applied.
pagesLayout is a map from page name to PageLayout object. Definition:

type PagesLayout = { [key: string]: IPageLayout; };

PageLayout contains a visual layout map, which maps each visual name to a visual layout object:

interface IPageLayout {
visualsLayout: { [key: string]: IVisualLayout; };
}

Visual layout
To define a visual layout, pass a new position and size and a new visibility state.

interface IVisualLayout {
x?: number;
y?: number;
z?: number;
width?: number;
height?: number;
displayState?: IVisualContainerDisplayState;
}

interface IVisualContainerDisplayState {
mode: VisualContainerDisplayMode;
}

enum VisualContainerDisplayMode {
Visible,
Hidden
}

x,y,z : Defines the new position of the visual.

width , height: Defines the new size of the visual.
displayState : Defines the visibility of the visual.

Update layout
You can use updateSettings method to update the report layout any time while the report is loaded. See Update
Settings.

Code example
 // Get models. models contains enums that can be used.
var models = window['powerbi-client'].models;

var embedConfiguration = {
type: 'report',
id: '5dac7a4a-4452-46b3-99f6-a25915e0fe55',
embedUrl: 'https://app.powerbi.com/reportEmbed',
tokenType: models.TokenType.Embed,
accessToken: 'H4...rf',
settings: {
layoutType: models.LayoutType.Custom
customLayout: {
pageSize: {
type: models.PageSizeType.Custom,
width: 1600,
height: 1200
},
displayOption: models.DisplayOption.ActualSize,
pagesLayout: {
"ReportSection1" : {
visualsLayout: {
"VisualContainer1": {
x: 1,
y: 1,
z: 1,
width: 400,
height: 300,
displayState: {
mode: models.VisualContainerDisplayMode.Visible
}
},
"VisualContainer2": {
displayState: {
mode: models.VisualContainerDisplayMode.Hidden
}
},
}
}
}
}
}
};

// Get a reference to the embedded report HTML element

var embedContainer = document.getElementById('embedContainer');

// Embed the report and display it within the div container.

var report = powerbi.embed(embedContainer, embedConfiguration);

See also
Embed your Power BI dashboards, reports and tiles
Ask the Power BI Community
 Custom visuals in Power BI
3/14/2019 • 5 minutes to read • Edit Online

When creating or editing a Power BI report, there are many different types of visuals available for you to use.
These visuals display in the Visualizations pane. When you download Power BI Desktop or open Power BI
service, this set of visuals comes "pre-packaged."

But you aren't limited to this set of visuals, selecting the ellipses opens up another source of report visuals:
custom visuals.
Custom visuals are created by developers, using the custom visuals SDK, to enable business users to see their
data in a way that fits the business best. Report authors can then import the custom visuals files into their reports
and use them as any other Power BI visuals. Custom visuals are first class citizens in Power BI and can be filtered,
highlighted, edited, shared, etc.
Custom visuals can be in the form of three deployment channels:
Custom visual files
Organizational visuals
Marketplace visuals

Custom visual files

Custom visuals are packages that include code for rendering the data that is served to them. Anyone can create a
custom visual and package it as a single .pbiviz file, that can be imported into a Power BI report.

WARNING
A custom visual could contain code with security or privacy risks; Make sure you trust the author and the source of the
custom visual before importing it to your report.

Organizational visuals
Power BI admins can deploy custom visuals into their organization, so that report authors can easily discover and
use the custom visuals that the admin has approved to use inside of the organization. The admin then has control
to choose specific custom visuals to deploy in the organization, as well as an easy way to manage (for example,
update version, disable/enable) those visuals. For the report author, it is an easy way to discover visuals that are
unique to the organization, as well as a seamless support for updating those visuals.
To get more information about organization custom visuals, read more about organizational visuals.
Marketplace visuals
Members of the community, as well as Microsoft, have contributed their custom visuals to the benefit of the
public and published them to AppSource marketplace. These visuals can be downloaded and added to Power BI
reports. All of these custom visuals have been tested and approved by Microsoft for functionality and quality.
What is AppSource? Put, it is the place to find apps, add-ins, and extensions for your Microsoft software.
AppSource connects millions of users of products like Office 365, Azure, Dynamics 365, Cortana, and Power BI to
solutions that help them get work done more efficiently, more insightfully, or more beautifully than before.
Certified visuals
Power BI certified visuals are marketplace visuals that have passed additional rigorous testing for quality, and are
supported in additional scenarios, such as email subscriptions, and export to PowerPoint. To see the list of
certified custom visuals or to submit your own, see Certified custom visuals.
Are you a Web developer and interested in creating your own visualizations and adding them to AppSource? See
Developing a Power BI custom visual and learn how to publish custom visuals to AppSource.
Import a custom visual from a file
1. Select the ellipses from the bottom of the Visualizations pane.

2. From the dropdown, select Import from file.

3. From the Open file menu, select the .pbiviz file that you want to import and then select Open. The icon
for the custom visual is added to the bottom of your Visualizations pane and is now available for use in
your report.
Import organizational visuals
1. Select the ellipses from the bottom of the Visualizations pane.

2. From the dropdown, select Import from marketplace.

3. Select MY ORGANIZATION from the top tab menu.

4. Scroll through the list to find the visual to import.

5. Import the custom visual by selecting Add. The icon for the custom visual is added to the bottom of your
 Visualizations pane and is now available for use in your report.

Download or import custom visuals from Microsoft AppSource

You have two options for downloading and importing custom visuals; from within Power BI and from the
AppSource website.
Import custom visuals from within Power BI
1. Select the ellipses from the bottom of the Visualizations pane.

2. From the dropdown, select Import from marketplace.

3. Scroll through the list to find the visual to import.

4. To learn more about one of the visuals, highlight and select it.

5. On the detail page you can view screenshots, videos, detailed description and more.

6. Scroll to the bottom to see reviews.

7. Import the custom visual by selecting Add. The icon for the custom visual is added to the bottom of your
Visualizations pane and is now available for use in your report.

Download and import custom visuals from Microsoft AppSource

1. Start at Microsoft AppSource and select the tab for Apps.

2. Go to the Apps results page where you can view top apps in each category, including Power BI Apps. But
we're looking for custom visuals, so let's narrow down the results by selecting Power BI visuals from the
left navigation list.

3. AppSource displays a tile for each custom visual. Each tile has a snapshot of the custom visual and gives a
brief description and a download link. To see more details, select the tile.
4. On the detail page you can view screenshots, videos, detailed description and more. Download the custom
visual by selecting Get it now and then agreeing to the Terms of use.

5. Select the link to download the custom visual.

The download page also includes instructions on how to import the custom visual into Power BI Desktop
and Power BI service.
You can also download a sample report that includes the custom visual and showcases its capabilities.
6. Save the '.pbiviz' file and then open Power BI.
7. Import the '.pbiviz' file into your report. (See the Import a custom visual from a file section above.)

Considerations and limitations

A custom visual is added to a specific report when imported. If you'd like to use the visual in another
report, you need to import it into that report as well. When a report with a custom visual is saved using
the Save As option, a copy of the custom visual is saved with the new report.
If you don't see a Visualizations pane, that means you do not have edit permissions for the report. You
can only add custom visuals to reports you can edit, not to reports that have been shared with you.

Troubleshoot
For information about troubleshooting, visit Troubleshooting your Power BI custom visuals.

FAQ
For more information and answers to questions, visit Frequently asked questions about Power BI custom visuals.

Next steps
Visualizations in Power BI
More questions? Try the Power BI Community.
 Tutorial: Developing a Power BI custom visual
3/18/2019 • 10 minutes to read • Edit Online

We’re enabling developers to easily add custom visuals into Power BI for use in dashboard and reports. To help
you get started, we’ve published the code for all of our visualizations to GitHub.
Along with the visualization framework, we’ve provided our test suite and tools to help the community build
high-quality custom visuals for Power BI.
This tutorial shows you how to develop a Power BI custom visual named Circle Card to display a formatted
measure value inside a circle. The Circle Card visual supports customization of fill color and thickness of its
outline.
In the Power BI Desktop report, the cards are modified to become Circle Cards.

In this tutorial, you learn how to:

Create a Power BI custom visual.
Develop the custom visual with D3 visual elements.
Configure data binding with the visual elements.
Format data values.

Prerequisites
If you're not signed up for Power BI Pro, sign up for a free trial before you begin.
You need Visual Studio Code installed.
You need Windows PowerShell version 4 or later for windows users OR the Terminal for OSX users.

Setting up the developer environment

In addition to the prerequisites, there are a few more tools you need to install.
Installing node.js
1. To install Node.js, in a web browser, navigate to Node.js.
2. Download the latest feature MSI installer.
3. Run the installer, and then follow the installation steps. Accept the terms of the license agreement and all
defaults.

4. Restart the computer.

Installing packages
Now you need to install the pbiviz package.
1. Open Windows PowerShell after the computer has been restarted.
2. To install pbiviz, enter the following command.

npm i -g powerbi-visuals-tools

Creating and installing a certificate

Windows
1. To create a certificate, enter the following command.

pbiviz --create-cert

It returns a result that produces a passphrase. In this case, the passphrase is 15105661266553327.

2. Now we need to install the certificate. to install the certificate, enter the following command.

pbiviz --install-cert

3. In the Certificate Import Wizard, verify that the store location is set to Current User. Then select Next.
4. At the File to Import step, select Next.
5. At the Private Key Protection step, in the Password box, paste the passphrase you received from
creating the cert. Again, in this case it is 15105661266553327.

6. At the Certificate Store step, select the Place all certificates in the Following store option. Then
select Browse.
7. In the Select Certificate Store window, select Trusted Root Certification Authorities and then select
OK. Then select Next on the Certificate Store screen.

8. To complete the import, select Finish.

9. If you receive a security warning, select Yes.
10. When notified that the import was successful, select OK.

IMPORTANT
Do not close the Windows PowerShell session.

OSX
1. If the lock in the upper left is locked, select it to unlock. Search for localhost and double-click on the
certificate.

2. Select Always Trust and close the window.

3. Enter your username and password. Select Update Settings.

4. Close any browsers that you have open.

NOTE
If the certificate is not recognized, you may need to restart your computer.

Creating a custom visual

Now that you have set up your environment, it is time to create your custom visual.
You can download the full source code for this tutorial.
1. Verify that the Power BI Visual Tools package has been installed.

pbiviz

You should see the help output.

 +syyso+/
oms/+osyhdhyso/
ym/ /+oshddhys+/
ym/ /+oyhddhyo+/
ym/ /osyhdho
ym/ sm+
ym/ yddy om+
ym/ shho /mmmm/ om+
/ oys/ +mmmm /mmmm/ om+
oso ommmh +mmmm /mmmm/ om+
ymmmy smmmh +mmmm /mmmm/ om+
ymmmy smmmh +mmmm /mmmm/ om+
ymmmy smmmh +mmmm /mmmm/ om+
+dmd+ smmmh +mmmm /mmmm/ om+
/hmdo +mmmm /mmmm/ /so+//ym/
/dmmh /mmmm/ /osyhhy/
// dmmd
++

PowerBI Custom Visual Tool

Usage: pbiviz [options] [command]

Commands:

new [name] Create a new visual

info Display info about the current visual
start Start the current visual
package Package the current visual into a pbiviz file
update [version] Updates the api definitions and schemas in the current visual. Changes the version
if specified
help [cmd] display help for [cmd]

Options:

-h, --help output usage information

-V, --version output the version number
--install-cert Install localhost certificate

2. Review the output, including the list of supported commands.

3. To create a custom visual project, enter the following command. CircleCard is the name of the project.

pbiviz new CircleCard

NOTE
You create the new project at the current location of the prompt.

4. Navigate to the project folder.

cd CircleCard

5. Start the custom visual. Your CircleCard visual is now running while being hosted on your computer.

pbiviz start
 IMPORTANT
Do not close the Windows PowerShell session.

Testing the custom visual

In this section, we are going to test the CircleCard custom visual by uploading a Power BI Desktop report and
then editing the report to display the custom visual.
1. Sign in to PowerBI.com > go to the Gear icon > then select Settings.

2. Select Developer then check the Enable Developer Visual for testing checkbox.

3. Upload a Power BI Desktop report.

Get Data > Files > Local File.
You can download a sample Power BI Desktop report if you do not have one created already.
 Now to view the report, select US_Sales_Analysis from the Report section in the navigation pane on the
left.

4. Now you need to edit the report while in the Power BI service.
Go to Edit report.

5. Select the Developer Visual from the Visualizations pane.

 NOTE
This visualization represents the custom visual that you started on your computer. It is only available when the
developer settings have been enabled.

6. Notice that a visualization was added to the report canvas.

NOTE
This is a very simple visual that displays the number of times its Update method has been called. At this stage, the
visual does not yet retrieve any data.

7. While selecting the new visual in the report, Go to the Fields Pane > expand Sales > select Quantity.

8. Then to test the new visual, resize the visual and notice the update value increments.
To stop the custom visual running in PowerShell, enter Ctrl+C. When prompted to terminate the batch job, enter
Y, then press Enter.

Adding visual elements

Now you need to install the D3 JavaScript library. D3 is a JavaScript library for producing dynamic, interactive
data visualizations in web browsers. It makes use of widely implemented SVG HTML5, and CSS standards.
Now you can develop the custom visual to display a circle with text.

NOTE
Many text entries in this tutorial can be copied from here.

1. To install the D3 library in PowerShell, enter the command below.

npm i [email protected] --save

2. To install type definitions for the D3 library, enter the command below.

npm i @types/[email protected]
 This command installs TypeScript definitions based on JavaScript files, enabling you to develop the
custom visual in TypeScript (which is a superset of JavaScript). Visual Studio Code is an ideal IDE for
developing TypeScript applications.
3. Launch Visual Studio Code.
You can launch Visual Studio Code from PowerShell by using the following command.

code .

4. In the Explorer pane, expand the node_modules folder to verify that the d3 library was installed.

5. Notice the TypeScript file, index.d.ts, by expanding node_modules > @types > d3 in the Explorer pane.

6. Select the pbiviz.json file.

7. To register the d3 library, enter the following file reference into the externalJS array. Be sure to add a
comma between the existing file reference and the new file reference.

"node_modules/d3/d3.min.js"

8. Save the pbiviz.json file changes.

Developing the visual elements
Now we can explore how to develop the custom visual to show a circle and sample text.
1. In the Explorer pane, expand the src folder and then select visual.ts.

NOTE
Notice the comments at the top of the visual.ts file. Permission to use the Power BI custom visual packages is
granted free of charge under the terms of the MIT License. As part of the agreement, you must leave the
comments at the top of the file.

2. Remove the following default custom visual logic from the Visual class.
The four class-level private variable declarations.
All lines of code from the constructor.
All lines of code from the update method.
All remaining lines within the module, including the parseSettings and enumerateObjectInstances
methods.
Verify that the module code looks like the following.

module powerbi.extensibility.visual {
"use strict";
export class Visual implements IVisual {

constructor(options: VisualConstructorOptions) {

public update(options: VisualUpdateOptions) {

}
}
}

3. Beneath the Visual class declaration, insert the following class-level properties.
 private host: IVisualHost;
private svg: d3.Selection<SVGElement>;
private container: d3.Selection<SVGElement>;
private circle: d3.Selection<SVGElement>;
private textValue: d3.Selection<SVGElement>;
private textLabel: d3.Selection<SVGElement>;

4. Add the following code to the constructor.

this.svg = d3.select(options.element)
.append('svg')
.classed('circleCard', true);
this.container = this.svg.append("g")
.classed('container', true);
this.circle = this.container.append("circle")
.classed('circle', true);
this.textValue = this.container.append("text")
.classed("textValue", true);
this.textLabel = this.container.append("text")
.classed("textLabel", true);

This code adds an SVG group inside the visual and then adds three shapes: a circle and two text elements.
To format the code in the document, right-select anywhere in the Visual Studio Code document, and
then select Format Document.
 To improve readability, it is recommended that you format the document every time that paste in code
snippets.
5. Add the following code to the update method.

let width: number = options.viewport.width;

let height: number = options.viewport.height;
this.svg.attr({
width: width,
height: height
});
let radius: number = Math.min(width, height) / 2.2;
this.circle
.style("fill", "white")
.style("fill-opacity", 0.5)
.style("stroke", "black")
.style("stroke-width", 2)
.attr({
r: radius,
cx: width / 2,
cy: height / 2
});
let fontSizeValue: number = Math.min(width, height) / 5;
this.textValue
.text("Value")
.attr({
x: "50%",
y: "50%",
dy: "0.35em",
"text-anchor": "middle"
}).style("font-size", fontSizeValue + "px");
let fontSizeLabel: number = fontSizeValue / 4;
this.textLabel
.text("Label")
.attr({
x: "50%",
y: height / 2,
dy: fontSizeValue / 1.2,
"text-anchor": "middle"
})
.style("font-size", fontSizeLabel + "px");

This code sets the width and height of the visual, and then initializes the attributes and styles of the visual
 elements.
6. Save the visual.ts file.
7. Select the capabilities.json file.
At line 14, remove the entire objects element (lines 14-60).
8. Save the capabilities.json file.
9. In PowerShell, start the custom visual.

pbiviz start

Toggle auto reload

1. Navigate back to the Power BI report.
2. In the toolbar floating above the developer visual, select the Toggle Auto Reload.

This option ensures that the visual is automatically reloaded each time you save project changes.
3. From the Fields pane, drag the Quantity field into the developer visual.
4. Verify that the visual looks like the following.

5. Resize the visual.

Notice that the circle and text value scales to fit the available dimension of the visual.
The update method is called continuously with resizing the visual, and it results in the fluid rescaling of the
visual elements.
You have now developed the visual elements.
6. Continue running the visual.

Configuring data binding

Define the data roles and data view mappings, and then modify the custom visual logic to display the value and
display name of a measure.
Configuring the capabilities
Modify the capabilities.json file to define the data role and data view mappings.
1. In Visual Studio code, in the capabilities.json file, from inside the dataRoles array, remove all content
(lines 3-12).
2. Inside the dataRoles array, insert the following code.

{
"displayName": "Measure",
"name": "measure",
"kind": "Measure"
}

The dataRoles array now defines a single data role of type measure, that is named measure, and
displays as Measure. This data role allows passing either a measure field, or a field that is summarized.
3. From inside the dataViewMappings array, remove all content (lines 10-31).
4. Inside the dataViewMappings array, insert the following content.

{
"conditions": [
{ "measure": { "max": 1 } }
],
"single": {
"role": "measure"
}
}

The dataViewMappings array now defines one field can be passed to the data role named measure.
5. Save the capabilities.json file.
6. In Power BI, notice that the visual now can be configured with Measure.

NOTE
The visual project does not yet include data binding logic.

Exploring the dataview

1. In the toolbar floating above the visual, select Show Dataview.
2. Expand down into single, and then notice the value.

3. Expand down into metadata, and then into the columns array, and in particular notice the format and
displayName values.

4. To toggle back to the visual, in the toolbar floating above the visual, select Show Dataview.

Configuring data binding

1. In Visual Studio Code, in the visual.ts file, add the following statement as the first statement of the
update method.

let dataView: DataView = options.dataViews[0];

This statement assigns the dataView to a variable for easy access, and declares the variable to reference
the dataView object.
2. In the update method, replace.text(“Value”)** with the following.

.text(dataView.single.value as string)
3. In the update method, replace .text(“Label”) with the following.

.text(dataView.metadata.columns[0].displayName)

4. Save the visual.ts file.

5. In Power BI, review the visual, which now displays the value and the display name.
You have now configured the data roles and bound the visual to the dataview.
In the next tutorial you learn how to add formatting options to the custom visual.

Debugging
For tips about debugging your custom visual, see the debugging guide.

Next steps
Adding formatting options
 Tutorial: Adding formatting options to a Power BI
custom visual
3/8/2019 • 4 minutes to read • Edit Online

In this tutorial, we go through how to add common properties to the visual.

In this tutorial, you learn how to:
Add visual properties.
Package the visual.
Import the custom visual to a Power BI Desktop report.

Adding formatting options

1. In Power BI, select the Format page.
You should see a message that reads - Formatting options are unavailable for this visual.

2. In Visual Studio Code, open the capabilities.json file.

3. Before the dataViewMappings array, add objects (after line 8).

"objects": {},
4. Save the capabilities.json file.
5. In Power BI, review the formatting options again.

NOTE
If you do not see the formatting options change then select Reload Custom Visual.

6. Set the Title option to Off. Notice that the visual no longer displays the measure name at the top-left corner.
Adding custom formatting options
You can add custom properties to enable configuring the color of the circle, and also the border width.
1. In PowerShell, stop the custom visual.
2. In Visual Studio Code, in the capabilities.json file, insert the following JSON fragment into the object
labeled objects.

"circle": {
"displayName": "Circle",
"properties": {
"circleColor": {
"displayName": "Color",
"description": "The fill color of the circle.",
"type": {
"fill": {
"solid": {
"color": true
}
}
}
},
"circleThickness": {
"displayName": "Thickness",
"description": "The circle thickness.",
"type": {
"numeric": true
}
}
}
},

The JSON fragment describes a group named circle, which consists of two options named circleColor and
circleThickness.
3. Save the capabilities.json file.
4. In the Explorer pane, from inside the src folder, and then select settings.ts. This file represents the settings
for the starter visual.
5. In the settings.ts file, replace the two classes with the following code.

export class CircleSettings {

public circleColor: string = "white";
public circleThickness: number = 2;
}
export class VisualSettings extends DataViewObjectsParser {
public circle: CircleSettings = new CircleSettings();
}

This module defines the two classes. The CircleSettings class defines two properties with names that
match the objects defined in the capabilities.json file (circleColor and circleThickness) and also sets
default values. The VisualSettings class inherits the DataViewObjectParser class and adds a property
named circle, which matches the object defined in the capabilities.json file, and returns an instance of
CircleSettings.
6. Save the settings.ts file.
 7. Open the visual.ts file.
8. In the Visual class, add the following property.

private visualSettings: VisualSettings;

This property stores a reference to the VisualSettings object, describing the visual settings.

9. In the Visual class, add the following method before the update method. This method is used to populate
the formatting options.

public enumerateObjectInstances(options: EnumerateVisualObjectInstancesOptions):

VisualObjectInstanceEnumeration {
const settings: VisualSettings = this.visualSettings ||
VisualSettings.getDefault() as VisualSettings;
return VisualSettings.enumerateObjectInstances(settings, options);
}

This method is used to populate the formatting options.

10. In the update method, after the declaration of the radius variable, add the following code.

this.visualSettings = VisualSettings.parse<VisualSettings>(dataView);

this.visualSettings.circle.circleThickness = Math.max(0, this.visualSettings.circle.circleThickness);

this.visualSettings.circle.circleThickness = Math.min(10, this.visualSettings.circle.circleThickness);

This code retrieves the format options. It adjusts any value passed into the circleThickness property,
converting it to 0 if negative, or 10 if it's a value greater than 10.
11. For the circle element, modify the value passed to the fill style to the following expression.

this.visualSettings.circle.circleColor

12. For the circle element, modify the value passed to the stroke-width style to the following expression.

this.visualSettings.circle.circleThickness

13. Save the visual.ts file.

14. In PowerShell, start the visual.

pbiviz start

15. In Power BI, in the toolbar floating above the visual, select Toggle Auto Reload.
16. In the visual format options, expand Circle.
 Modify the color and thickness option.
Modify the thickness option to a value less than zero, and a value higher than 10. Then notice the visual
updates the value to a tolerable minimum or maximum.

Packaging the custom visual

Enter property values for the custom visual project, update the icon file, and then package the custom visual.
1. In PowerShell, stop the custom visual.
2. Open the pbiviz.json file in Visual Studio Code.
3. In the visual object, modify the displayName property to Circle Card.
In the Visualizations pane, hovering over the icon reveals the display name.

4. For the description property, enter the following text.

Displays a formatted measure value inside a circle
5. Optionally, in the author object, enter your details.
6. Save the pbiviz.json file.
7. In the assets object, notice that the document defines a path to an icon. The icon is the image that appears
in the Visualizations pane. It must be a PNG file, 20 pixels by 20 pixels.
8. In Windows Explorer, copy the icon.png file, and then paste it to replace the default file located at assets
folder.
9. In Visual Studio Code, in the Explorer pane, expand the assets folder, and then select the icon.png file.
10. Review the icon.
11. In Visual Studio Code, ensure that all files are saved.
12. To package the custom visual, in PowerShell, enter the following command.

pbiviz package

Now the package is output to the dist folder of the project. The package contains everything required to import
the custom visual into either the Power BI service or a Power BI Desktop report. You have now packaged the
custom visual, and it is now ready for use.

Importing the custom visual

Now you can open the Power BI Desktop report, and import the Circle Card custom visual.
1. Open Power BI Desktop, create a new report with any sample dataset
2. In the Visualizations pane, select the ellipsis, and then select Import from File.

3. In the import window, select Import.

4. In the Open window, navigate to the dist folder in your project directory.
5. Select the circleCard.pbiviz file, and then select Open.
6. When the visual has successfully imported, select OK.
7. Verify that the visual has been added to the Visualizations pane.
8. Hover over the Circle Card icon, and notice the tooltip that appears.

Debugging
For tips about debugging your custom visual, see the debugging guide.

Next steps
You can list your newly developed visual for others to use by submitting it to the AppSource. For more
information on this process reference Publish custom visuals to AppSource.
 Organizational custom visuals in Power BI
3/8/2019 • 2 minutes to read • Edit Online

You can use custom visuals in Power BI to create a unique type of visual that’s tailored to you. Custom visuals are
created by developers, and they're often created when the multitude of visuals that are included in Power BI don’t
quite meet their need.
In some organizations, custom visuals are even more important – they might be necessary to convey specific
data or insights unique to the organization, they may have special data requirements, or they may highlight
private business methods. Such organizations need to develop custom visuals, share them throughout their
organization, and make sure they’re properly maintained. Power BI custom visuals lets organizations do just that.
The following image shows the process by which organization custom visuals in Power BI flow from
administrator, through development and maintenance, all finally make their way to the data analyst.

Organizational visuals are deployed and managed by the Power BI administrator from the Admin portal. Once
deployed into the organizational repository, users in the organization can easily discover them, and import the
organizational custom visuals into their reports directly from Power BI Desktop.
To learn more about how to use organizational custom visuals in the reports that you created, see the following
article: Learn more about importing organizational visuals into your reports .

Administer organizational custom visuals

To learn more about how to administer, deploy, and manage organizational custom visuals in your organization,
see the following article: Learn more about deployment and management of organization custom visuals.

WARNING
A custom visual can contain code with security or privacy risks. Make sure you trust the author and the source of any
custom visual before deploying it to the organization repository.

Considerations and limitations

There are several considerations and limitations that you need to be aware of.
Admin:
Legacy custom visuals (such as custom visuals that aren't built on top of the new versioned APIs) aren't
supported
If a custom visual is deleted from the repository, any existing reports that use the deleted visual will stop
rendering. Deletion operation from the repository isn't reversible. To temporarily disable a custom visual,
use the "Disable" feature.
End user:
Organizational custom visuals are private visuals imported from the organization repository. As any
private visual they can't be exported to PowerPoint or displayed in emails received when a user subscribes
to report pages. Only certified custom visuals imported directly from the marketplace supports these
features.
Visio visual, PowerApps visual, the Map box visual, and the GlobeMap visual from AppSource
marketplace don't render if deployed through the organization repository.

Troubleshoot
For information about troubleshooting, visit Troubleshooting your Power BI custom visuals.

FAQ
For more information and answers to questions, visit Frequently asked questions about Power BI custom visuals.
More questions? Try the Power BI Community.
 Guidelines for Power BI visuals
3/25/2019 • 2 minutes to read • Edit Online

Guidelines for Power BI visuals with additional purchases

Until recently, the Marketplace (AppSource) accepted only Power BI visuals that are free. This policy has changed
(December '18), so that you can also submit visuals to AppSource that have an "additional purchase may be
required" price tag.
"Additional purchase may be required" visuals are similar to in-app purchase (IAP ) add-ins in the Office Store.
Developers may also submit these visuals for certification after the AppSource team approves them, and after
making sure they comply with certification requirements. For more information about the requirements, see
Certified custom visuals.

NOTE
For the visual to be certified, it must not access external services or resources.

IMPORTANT
If you update your visual from free to "Additional purchase may be required", users must receive the same level of free
functionality as before the update. You may add optional advanced paid features in addition to the existing free features. We
recommend that you submit the IAP visuals with the advanced features as new visuals and not update the existing free ones.

What changed in the submission process?

Developers upload their IAP visuals to AppSource via the Seller Dashboard, as they've been doing for free visuals.
To indicate that the submitted visual has IAP features, developers should write in the Seller Dashboard notes,
"Visual with in-app purchase." Also, developers need to provide a license key or token so that the validation team
can validate the IAP features. After the visual is validated and approved, the AppSource listing for the IAP visual
states, "Additional purchase may be required" under the pricing options.

What is a Power BI visual with IAP features?

An IAP visual is a free visual that offers free features. It also has some advanced features for which extra charges
may be applied to operate them. In the visual's description, developers must notify users about the features that
require additional purchases to operate. Currently, Microsoft does not provide native APIs to support the purchase
of apps and add-ins.
Developers may use any third-party payment system for these purchases. For more information, see our store
policy.

NOTE
Watermarks are not allowed on the free features or free visuals. Watermarks may only be used on paid features that are used
without a valid license. We recommend to display a pop-up window with all the license related information, if the advanced
paid features are used without a valid license.
Logo guidelines
This section describes the specifications for adding logos and logotypes in visuals.

IMPORTANT
Logos are allowed in edit mode only. Logos can't be displayed in view mode.
Best practices
Visual landing page
Use the landing page to clarify to users how they can use your visual and where to purchase the license. Don't
include videos that are automatically triggered. Add only material that helps improve the user's experience, such as
information or links to license purchasing details and how to use IAP features.
License key and token
For the user's convenience, add the license key or token related fields at the top of the format pane.

FAQ
For more information about visuals, see Frequently asked questions about visuals with additional purchases.
Next steps
Learn how you can publish your custom visual to AppSource for others to discover and use.
 Frequently asked questions about Power BI custom
visuals
3/14/2019 • 7 minutes to read • Edit Online

Organizational custom visuals

How can the admin manage the organizational custom visuals?
In the Admin portal, under the "Organizational custom visuals" tab, the admin can see and manage all the
organizational custom visuals in the enterprise: add, disable, enable, and delete. There's no need to share those
visuals by emails or shared folder anymore! Once deployed into the organizational repository, users in the
organization can easily find them, and import the organizational custom visuals into their reports directly from
Power BI Desktop or Service. The organizational custom visuals can be found from the built-in store (in desktop
and service) under the MY ORGANIZATION tab. Once the admin uploads a new organizational custom visual’s
version, everyone in the organization gets the same updated version. Report authors don't need to delete the visual
in their reports to get the new version of these visuals as all reports using these visuals are automatically updated!
The update mechanism is similar to the marketplace visuals.
If an admin uploads a custom visual from the public marketplace to the organization store, is it automatically
updated once a vendor updates the visual in the public marketplace?
No, there's no automatic update from the public marketplace. It's the Admin's responsibility to update the
organizational custom visuals' version.
Is there a way to disable the organizational store?
No, users always see the "MY ORGANIZATION" tab from the Power BI desktop and service. Admin can disable or
delete all organizational custom visuals from the admin portal and the organizational store is empty.
If the administrator disables custom visuals from the Admin portal (Tenant settings) do users still have access to
the organizational custom visuals?
Yes, if the admin disables the custom visuals from the admin portal, it doesn’t affect the organizational store. Some
organizations disable custom visuals and enable only hand-picked visuals that were imported and uploaded by the
Power BI administrator to the organizational store. Disabling the custom visuals from the Admin portal isn't
enforced in Power BI Desktop. Desktop users can still add and use custom visuals from the public marketplace in
their reports. However, those public custom visuals stop rendering once published to the Power BI Service and
issue an appropriate error. When using the Power BI service, you aren't able to import custom visuals from the
public marketplace. Only visuals from the organizational store can be imported because the custom visuals setting
in the admin portal is enforced in the Power BI service.
Why does the organizational store and organizational custom visuals make a great enterprise solution?
Everyone gets the same visual version, which is controlled by the Power BI administrator. Once the admin
updates the visual's version in the admin portal, all the users in the organization get the updated version
automatically.
No need to share visual files by email or shared folders anymore! One place, visible to all members who are
logged-in.
Security and supportability, new versions of organizational custom visuals are updated automatically in all
reports similar to marketplace visuals.
Users in the organization using the organizational custom visuals needs to be logged-in to see and use the
organizational custom visuals, which are a security element for organization.
 Admins can control which custom visuals to be available in the organization.
Admins can enable/disable visuals for testing from the admin portal. Better security enforcement as those
visuals will be allowed for organizational members only.

Certified custom visuals

What are certified custom visuals?
Certified custom visuals are visuals in the marketplace that meet certain specified code requirements and testing
by the Power BI team. The tests performed are designed to check that the visual does not access external services
or resources. However, Microsoft isn't the author of third-party custom visuals, and we advise customers to contact
the author directly to verify the functionality of such visual.
What tests are done during the certification process?
The certification process tests include but are not limited to: Code reviews, static code analysis, data leakage, data
fuzzing, penetration testing, access XSS testing, malicious data injection, input validation and functional testing.
Do you certify visuals every submission?
Yes. Every time a new version of certified visual is submitted to the Marketplace, the visual’s version update goes
under the same certification checks.
Note for developers: if you are submitting a version update of certified visual, you do not need to send a separate
email as first time certification request. Certification of version update happens automatically, and any violations
that cause a rejection are sent an email to explain what things need to be fixed.
Is it possible that a certified visual stops being certified with a new update?
No, this is not possible. A certified visual can’t be uncertified with a new update. The update is rejected.
Do I need to share my code in public repository if I am submitting to the certification process?
No, you don’t need to share your code publicly. However, you need to give us read permissions to check the
visuals code. E.g. private repository in GitHub.
Do we have to publish the visual in the Marketplace to certify it?
Yes. Publishing the visual to Marketplace first is an obligatory requirement for certification. To certify a custom
visual, it should be in our servers. We cannot certify private visuals.
How long does it take to certify my visual?
For updated version it may take up to 2 weeks. For a new submission (first-time certification) it may take up to 3
weeks.
Does the Certification process ensure that no data leakage occurs?
The tests performed are designed to check that the visual does not access external services or resources. However,
Microsoft is not the author of third-party custom visuals, and we advise customers to contact the author directly to
verify the functionality of such visual.
Are uncertified custom visuals safe to use?
Uncertified custom visuals do not necessarily mean unsafe visuals. Some visuals aren't certified because they don’t
comply with one or more of the certification requirements. For example, connecting to an external service like map
visuals, or visuals using commercial libraries.

Visuals with additional purchases

What is a visual with additional purchases?
A visual with additional purchases issimilar toin-app purchase(IAP )adds-in in the marketplace, these adds-in have
a pricetag Additional purchase may be required.
IAP custom visuals are free, downloadable custom visuals - users pay nothing to download those custom visuals
from the marketplace. IAP visuals offer optional in-app purchases for advanced features.
What's the benefit to developers?
IAP custom visuals inAppSource, will be discoverable to the many daily visitors, bringing valuable traffic, and
increased awareness for your IAP custom visuals and to you as the developer.
If until recently you managed those visuals through your website, now you can submit them to AppSource. Which
will increase the level of discoverability and visibility of the IAP visuals inside the Power BI community.
Visuals in the AppSource enjoy a Direct feedback channel from your customers who are using the IAP custom
visual, through the reviews and ratings system in the store.
Once the IAP visual was approved by the AppSource validation team, you may also submit those visuals for
certification. It is an optional process.
Once the visual is certified, IAP custom visuals can beexported to PowerPointand displayed in the emails received
when a usersubscribes to report pages. So today by submitting IAP visuals to the marketplace, IAP custom visuals
can also be certified and support extra feature set.
Do IAP visuals need to be certified?
Certification process is optional. It is up to the developer to decide whether to certify their IAP custom visuals or
not same with free visuals.
What is changing in the submission process?
The IAP custom visuals submission process to the marketplace, is same process as for free visuals. It happens
through the seller dashboard.The only change to the submission process is that developers will need to state in the
developer notes in the seller dashboard:“Visual with in-app purchase”. You’ll also need to providea license
key/token, if necessary to validate the paid/advanced features.
There will be no new option in the seller dashboard: free with in-app purchases, you will need to submit your IAP
visuals as free.
In addition, let users know what to expect by providing in your store long description whichfeatures are freeand
whichfeatures require additional purchasesto operate.
What should I do beforesubmittingmy IAP custom visual?
Ifyou’reworking on an IAP custom visual or already have one, make sure that itcomplies to theguidelines.
Ifyou have a logo in the custom visual, make sureit complies to the logo guidelines (color, location, size, and action
triggering).
You can also find,in the guidelines,best practicenotes.

NOTE
All free visuals should keep same free features previously offered. You may add optional advanced paid features on top of the
old free features. We recommend to submit the IAP visuals with the advanced features as new visuals and not to update the
old free ones.

Can I get my IAP custom visual certified?

Yes, same with free visuals. Once your IAP custom visual is approved by the AppSource team, you can submit your
visual to thecertification process.
To certify your visual, it should comply with the certificationrequirements, forexamplethe visual cannot access
external services for licenses validation.
Recall certification is an optional process, it's up to you to decide if you want your IAP visual to be certified.

Additional questions
How to get support?
Feel free to contact the custom visuals support team:*[email protected]*with any questions,
comments, or issues you have.

Next steps
For more information, visit Troubleshooting your Power BI custom visuals.
 Certified custom visuals
3/18/2019 • 4 minutes to read • Edit Online

What are certified custom visuals?

Certified custom visuals are visuals in the Marketplace that meet certain specified code requirements that the
Microsoft Power BI team has tested and approved. Once a custom visual is certified, it offers more features.
Such as you can export to PowerPoint, and you can display the visual in emails received when a user subscribes to
report pages.
Certified custom visuals are used like standard custom visuals. Certified custom visuals can be added to the
Power BI service, a Power BI Desktop report, and viewed with Power BI mobile and Power BI Embedded.
The tests performed are designed to check the visual does not access external services or resources. Microsoft is
not the author of third-party custom visuals, and we advise customers to contact the author directly to verify the
functionality of such visual.
The certification process is an optional process, and it is up to the developers to decide if they want their visual in
the marketplace to be certified.
Uncertified custom visuals do not necessarily mean unsafe visuals. Some visuals aren't certified because they
don’t comply with one or more of the certification requirements. For example, connecting to an external service
like map visuals, or visuals using commercial libraries.
Are you a Web developer and interested in creating your own visualizations and adding them toMicrosoft
AppSource? SeeDevelop a Power BI custom visualto learn how.

Removal of Power BI Certified custom visuals

Microsoft can remove a visual from the certified list at its discretion.

Getting a custom visualcertified

Certification requirements
To get your custom visual certified, make sure your custom visual complies with the below:
Microsoft AppSource approved. Your custom visual should be in our marketplace.
Custom visual is written with versioned API 1.2 or higher.
Code repository available for review by Power BI team (for instance, source code (JavaScript or
TypeScript) in human readable format available to us, through GitHub).

NOTE
You don’t have to publicly share your code in Github.

Uses only public reviewable OSS components (JS libraries or TypeScript that are public. The source code is
available for reviewing and doesn't have known vulnerabilities). We can't verify a custom visual using a
commercial component.
Does not access external services or resources, including but not limited to, no HTTP/S or WebSocket
 requests go out of Power BI to any services.

TIP
We recommend that you use EsLint with default security ruleset, to pre-validate your code before submission.

Process for submitting a custom visual for certification

To submit a custom visual for certification:
1. Send an email to Power BI Custom Visuals Support team ([email protected]). In the email,
include the following information:
Title: Visual Certification Request
Link to GitHub repository where the human readable source code is hosted
Adhere to the requirements
Pass the code review
2. The Microsoft Custom Visuals team notifies you when your custom visual is certified and added to the
certified list, or is rejected with a report of the issues that need to be fixed. It is the developer’s
responsibility to maintain an open line of communication with Microsoft and to update their certified
visuals as needed.

List of custom visuals that have been certified

LINK TO APPSOURCE LINK TO VIDEO

3AG Systems - Bar Chart With Relative Variance

3AG Systems - Column Chart With Relative Variance

Advanced Donut Visual

Advanced Network Visualization

Advanced TimeSeries Visual

Advanced Combo Visual

Aster Plot

Beyondsoft Calendar

Bowtie Chart by MAQ Software Video

Box and Whisker chart

Box and Whisker chart by MAQ Software Video

Brick Chart by MAQ Software Video

Bubble Chart by Akvelon

LINK TO APPSOURCE LINK TO VIDEO

Bullet Chart Video

Bullet Chart by OKViz Video

Calendar by Tallan

Candlestick by OKViz Video

Card with States by OKViz

Chiclet Slicer

Chord Video

Circular Gauge by MAQ Software Video

Cluster Map

Cylindrical Gauge by MAQ Software Video

Dial Gauge

Dot Plot

Dot Plot by OKViz Video

Drilldown Cartogram

Drilldown Choropleth

Drill-down column chart Video

Drill-down column chart for time based data Video

Drill-down donut chart Video

Dual KPI

Dynamic Tooltip by MAQ Software Video

Enhanced Scatter Video

Enlighten Aquarium

Enlighten Slicer

Enlighten Stack Shuffle

Enlighten Waffle Chart

LINK TO APPSOURCE LINK TO VIDEO

Filter by List by Devscope Video

Force-Directed Graph Video

Funnel with Source by MAQ Software Video

Gantt Video

Gantt Chart by MAQ Software Video

Globe Data Bars

Grid by MAQ Software Video

Hierarchy Chart by Akvelon Video

Histogram Chart

Histogram with points by MAQ Software Video

Horizontal Funnel by MAQ Software Video

Image by CloudScope

Image Grid

Infographic Designer

KPI Chart by Akvelon

KPI Column by MAQ Software Video

KPI Grid by MAQ Software Video

KPI Indicator

KPI Ticker by MAQ Software Video

Linear Gauge by MAQ Software Video

LineDot Chart

Mekko Chart Video

Multi KPI

Overview by CloudScope

Play Axis (Dynamic Slicer)

LINK TO APPSOURCE LINK TO VIDEO

Power KPI Video

Power KPI Matrix Video

Pulse Chart Video

Quadrant Chart by MAQ Software Video

Radar Chart

Ring Chart by MAQ Software Video

Rotating Chart by MAQ Software Video

Sankey Chart Video

Scatter Chart by Akvelon

Scroller

Smart Filter by OKViz Video

Sparkline by OKViz Video

Stream Graph

Sunburst

Synoptic Panel by OKViz

Table Heatmap

Tachometer Video

Text Filter

Text Wrapper by MAQ Software

Thermometer by MAQ Software Video

Time Brush Slicer

Timeline Slicer Video

Timeline by CloudScope Video

Tornado chart Video

Trading Chart by MAQ Software Video

 LINK TO APPSOURCE LINK TO VIDEO

Ultimate Variance Video

Ultimate Waterfall Video

User List by CloudScope

Waffle Chart Video

Word Cloud Video

FAQ
For more information about visuals, see Frequently asked questions about certified visuals.

Next steps
Developing a Power BI custom visual
Microsoft's custom visual playlist on YouTube
Visualizations in Power BI
Custom Visualizations in Power BI
Publish custom visuals to Microsoft AppSource
More questions? Try the Power BI Community
 Publish custom visuals to AppSource
3/8/2019 • 8 minutes to read • Edit Online

Learn how you can publish your custom visual to AppSource for others to discover and use.
Once you have created your custom visual, you may want to publish it AppSource for others to discover and use.
There is some preparation that needs to be done before you can do that. For more information on how to create a
custom visual, see Developing a Power BI Custom Visual.

What is AppSource?
The AppSource is the place to find SaaS apps and add-ins for your Microsoft products and service. AppSource
connects millions of users of Office 365, Dynamics 365, Cortana Intelligence, and others, to solutions that help
them get work done more efficiently, more insightfully or more beautifully than before.

Preparing to submit your custom visual

Once you're done coding and testing your custom visual and have packaged it into a pbiviz file, you should also
have the following ready for your submission.

ITEM REQUIRED DESCRIPTION

Pbiviz package contains all the required Yes Visual name

metadata Display name
GUID
Version
Description
Author name and email
ITEM REQUIRED DESCRIPTION

Sample .pbix report file Yes To showcase your visual, you should
help users to get acquainted with the
visual. You should emphasize on the
value the visual brings to the user and
give examples of usage, formatting
options, etc. You can also add a "hints"
page at the end with some tips and
tricks, things to avoid and the like.
The sample .pbix report file must work
offline, without any external connection

Icon Yes You should include the custom visual

logo that will appear in the store front.
The format can be .png, .jpg, .jpeg or
.gif. It must be exactly 300 px (width) x
300 px (height). Important! Please
review the short guide carefully before
submitting the Icon.

Screenshots Yes You must provide at least one

screenshot. The format can be .png,
.jpg, .jpeg or .gif. It must be exactly
1366 px (width) x 768 px (height). It
can be no larger than 1024 kb for the
file size. For greater usage, add text
bubbles to articulate the value
proposition of key features shown in
each screenshot.

Support download link Yes Provide the URL to support customers

who have issues with your visual. This
link is entered as part of your
SellerDashboard listing and is visible to
users when they access your visual’s
listing on AppSource. The format of
your URL should include https:// or
http://.

Privacy document link Yes Provide a link to the privacy policy for
customers who use your visual. This
link is entered as part of your
SellerDashboard listing and is visible to
users when they access your visual’s
listing on AppSource. The format of
your link should include https:// or
http://.

End-user license agreement (EULA) Yes You must upload a EULA file. This can
be either your own EULA or use the
default EULA within the Office store for
Power BI custom visuals. To use the
default EULA, paste the following URL
in the seller dashboard's "End-User
License Agreement" file upload dialog:
https://visuals.azureedge.net/app-
store/Power BI - Default Custom Visual
EULA.pdf.
 ITEM REQUIRED DESCRIPTION

Video link No To increase the interest of users for

your custom visual, it is advised to
provide a link to a video about your
visual. The format of your URL should
include https:// or http://.

GitHub repository No It is preferred to have a valid and public

link to a GitHub repository with
sources of your visual and sample data
in it to allow other developers to
provide feedback and propose
improvements to your code.

Submitting to Power BI
Submission starts with sending an email to the Power BI custom visuals submission team. You can email
[email protected].

IMPORTANT
You must fill the following fields in the pbiviz.json file: “description”, “supportUrl”, “author“, “name” and “email” before you
create the .pbiviz package.

Attach the .pbiviz file and the sample report .pbix file in your email. The Power BI team will reply back with
instructions and an app package XML file to upload. This XML app package is required in order to submit your
visual through the Office developer center.

NOTE
To improve quality and assure that existing reports are not breaking, updates to existing visuals will take an additional two
weeks to reach production environment after approval in the store.

Submitting to AppSource
Once you get the app package XML from the Power BI team, navigate to the developer center to submit your
visual to AppSource.

NOTE
You must have a valid Office developer account to log in to the Office developer center. An Office developer account must
be a Microsoft Account (Live ID, e.g. hotmail.com or outlook.com).

IMPORTANT
You must send an email with the .pbiviz file and the .pbix file to the Power BI team before submitting to AppSource. This
allows the Power BI team to upload the files to the public share server. Otherwise, the store will not be able to retrieve the
files. You must send the files with each new visual submission, update to existing visual, and fixes to rejected submissions.

Process to submit visual

Follow the below steps to complete the submission.
1. Select Add a new app.

2. Select Power BI custom visual and then Next.

3. Select the + under App package and select the app package XML file that you received from the Power BI
team from the open file dialog.

4. You should receive an approval that this is a valid Power BI app package.

5. Fill out the General info details.

Submission title: How your submission will be named in the developer center
Version: Your version number is auto-populated from your add-in app package.
Release Date (UTC ): Select a date for your app to release to the store. If a future date is chosen, your
app will not be available in the store until that date is reached.
Category: The first category will be auto populated as "Data Visualization + BI". That's how all Power BI
custom visuals will be tagged. You may provide up to 2 additional categories, for help users easily
search for your visual
Testing notes: optional, if you'd like to provide some instructions for the testers at Microsoft
My app calls, supports, contains, or uses cryptography or encryption: leave unchecked
Make this add -in available in the Office add -in catalog on iPad: leave unchecked
6. Upload your visual's logo by selecting the + under App logo. Then select the icon file in the open file
dialog. The file must be .png, .jpg, .jpeg or .gif. It must be exactly 300 px (width) x 300 px (height) and no
larger than 512 kb in size.

7. Fill out the Support documents details.

Support document link
Privacy document link
 Video link
End User License Agreement (EULA)
You must upload a EULA file. This can be either your own EULA or use the default EULA within the
Office store for Power BI custom visuals. To use the default EULA, paste the following URL in the
seller dashboard's "End-User License Agreement" file upload dialog:
https://visuals.azureedge.net/app-store/Power BI - Default Custom Visual EULA.pdf.
8. Select Next to proceed to the Details page.
9. Select Language and pick a language from the list.

10. Fill out the "Description" details.

App name (for this language): Enter the title of your app as it should appear in the storefront.
Short description: Enter the short description of your app, up to 100 characters, as it should appear in
the storefront. This description will show up in the top-level pages along with the logo. You can use the
description from the pbiviz package.
Long description: Provide a more detailed description of your app that customers will see on your app
details page. If you'd like to let the community improve your visual by making it open source, provide
the link to the public repository, such as GitHub, here.
11. Upload at least one screenshot. The format can be .png, .jpg, .jpeg or .gif. It must be exactly 1366 px (width)
x 768 px (height). It can be no larger than 1024 kb for the file size. For greater usage, add text bubbles to
articulate the value proposition of key features shown in each screenshot.
12. If you'd like to add more languages, select Add a language and repeat steps 10 and 11. Adding more
languages will help your users view the custom visual details in their own language. Languages that will
not be listed will default to the first language selected.
13. When you are done adding languages, select Next to proceed to the Block access page.
14. If you want to prevent customers in specific countries or regions from using or purchasing your app, check
the box and select from the list.
15. Select Next to proceed to the Pricing page.
16. Currently, only free visuals are supported and additional purchases inside the visual (In-App purchase) are
not allowed. Select This app is free.

NOTE
If you select any other option other than free, or have an In-App purchase content in the submitted visual, the
submission will be rejected.

17. You can now select Save as draft and submit later, or select Submit for approval to submit the custom
 visual to the Office store.

Tracking submission status and usage

You can review the validation policies.
After submission, you will be able to view the submission status in the app dashboard.

Certify your visual

Once your visual is created, you can optionally get your visual certified. This means it can run within the Power BI
service and be used with other features of the service such as exporting to PowerPoint. For more information, see
Getting a custom visual certified.

Next steps
Developing a Power BI custom visual
Visualizations in Power BI
Custom Visualizations in Power BI
Getting a custom visual certified
More questions? Try asking the Power BI Community
 Use R-powered custom visuals in Power BI
3/8/2019 • 5 minutes to read • Edit Online

In Power BI Desktop and the Power BI service, you can use R -powered custom visuals without any knowledge
of R and without any R scripting. This enables you to harness the analytic and visual power of R visuals, and R
scripts, without learning R or doing any programming yourself.
To use R -powered custom visuals, you first select and download the R custom visual you're interested in using
from the AppSource gallery of custom visuals for Power BI.

The following sections describe how to select, load, and use R -powered visuals in Power BI Desktop.

Use R custom visuals

To use R -powered custom visuals, download each visual from the custom visuals library, then use the visual like
any other type of visual in Power BI Desktop. There are two ways to get custom visuals: you can download them
from the online AppSource site, or browse and get them from within Power BI Desktop.
Get custom visuals from AppSource
Following are the steps to browse and select visuals from the online AppSource site:
1. Navigate to the Power BI visuals library, found at https://appsource.microsoft.com. Select the Power BI apps
checkbox under Refine by product, then select the See all link.
2. On the Power BI visuals library page, select Power BI visuals from the list of Add-ins in the left pane.

3. Select the visual you're interested in using from the gallery, and you're taken to a page that describes the
visual. Select the Get it now button to download.

NOTE
For authoring in Power BI Desktop, you need to have R installed on your local machine. But, when users want to
view an R-powered visual in the Power BI service they do not need R installed locally.
 You do not need to install R to use R -powered custom visuals in the Power BI service, however, if you want
to use R -powered custom visuals in Power BI Desktop you must install R on the local machine. You can
download R from the following locations:
CRAN
MRO
4. Once the visual is downloaded (which is like downloading any file from your browser), go to Power BI
Desktop and click the ellipsis (...) in the Visualizations pane, and select Import from file.

5. You're warned about importing a custom visual, as shown in the following image:
6. Navigate to where the visual file was saved, then select the file. Power BI Desktop custom visualizations
have the .pbiviz extension.

7. When you return to Power BI Desktop, you can see the new visual type in the Visualizations pane.

8. When you import the new visual (or open a report that contains an R -powered custom visual), Power BI
Desktop installs the required R packages.
9. From there, you can add data to the visual just as you would any other Power BI Desktop visual. When
complete, you can see your finished visual on the canvas. In the following visual, the Forecasting R -
powered visual was used with United Nations (UN ) birth rate projections (the visual on the left).

Like any other Power BI Desktop visual, you can publish this report with its R -powered visuals to the
Power BI service and share it with others.
Check the library often, since new visuals are being added all the time.
Get custom visuals from within Power BI Desktop
1. You can also get custom visuals from within Power BI Desktop. In Power BI Desktop click the ellipsis (the
...) in the Visualizations pane, and select Import from marketplace.
2. When you do so, the Power BI Visuals dialog appears, where you can scroll through the available custom
visuals and select what you would like. You can search by name, select a category, or just scroll through the
available visuals. When you're ready, just select Add to add the custom visual to Power BI Desktop.

Contribute R-powered custom visuals

If you create your own R visuals for use in your reports, you can share those visuals with the world by contributing
your custom visual to the custom visuals gallery. Contributions are made through GitHub, and the process is
outlined in the following location:
Contributing to the R -powered custom visuals gallery

Troubleshoot R-powered custom visuals

R -powered custom visuals have certain dependencies that must be met for the visuals to work properly. When R -
powered custom visuals don't run or load properly, the problem is usually one of the following:
The R engine is missing
Errors in the R script on which the visual is based
R packages are missing or out of date
The following section describes troubleshooting steps you can take to help address trouble you might run into.
Missing or outdated R packages
When attempting to install an R -powered custom visual, you can run into errors when there are missing or
outdated R packages; this is due to one of the following reasons:
The R installation is incompatible with the R package
The firewall, anti-virus software, or proxy settings are preventing R from connecting to the Internet
The Internet connection is slow or there's an Internet connection problem
The Power BI team is actively working on mitigating these issues before they reach you and the next Power BI
Desktop will incorporate updates to address these problems. Until then, you can take one or more of the following
steps to mitigate the issues:
1. Remove the custom visual, then install it again. This initiates a reinstallation of the R packages.
2. If your installation of R is not current, upgrade your R installation, then remove and reinstall the custom
visual as described in the previous step.
Supported R versions are listed in the description of each R -powered custom visual, as shown in the
following image.
 NOTE
You can keep the original R installation and only associate Power BI Desktop with the current version you install. Go
to File > Options and settings > Options > R scripting.

3. Install R packages manually, using any R console. The steps for this approach follow:
a. Download the R -powered visual installation script and save that file to a local drive.
b. From the R console, run the following:

source(“C:/Users/david/Downloads/ScriptInstallPackagesForForecastWithWorkarounds.R”)

Typical default installation locations are the following:

c:\Program Files\R\R-3.3.x\bin\x64\Rterm.exe (for CRAN-R)

c:\Program Files\R\R-3.3.x\bin\x64\Rgui.exe (for CRAN-R)
c:\Program Files\R\R-3.3.x\bin\R.exe (for CRAN-R)
c:\Program Files\Microsoft\MRO-3.3.x\bin\R.exe (for MRO)
c:\Program Files\Microsoft\MRO-3.3.x\bin\x64\Rgui.exe (for MRO)
c:\Program Files\RStudio\bin\rstudio.exe (for RStudio)

4. If the previous steps don't work, try the following:

a. Use R Studio and follow the step outlined in 3.b. above (run the script line from the R console).
b. If the previous step doesn't work, change Tools > Global Options > Packages in R Studio, and enable
the checkbox for Use Internet Explorer library/proxy for HTTP, then repeat step 3.b. from the above
steps.

Next steps
Take a look at the following additional information about R in Power BI.
Power BI custom visuals gallery
Running R Scripts in Power BI Desktop
Create R visuals in Power BI Desktop
Use an external R IDE with Power BI
 Troubleshoot Power BI custom visuals
3/8/2019 • 2 minutes to read • Edit Online

Debug
Pbiviz command not found (or similar errors)
When you run pbiviz in your terminal's command line, you should see the help screen. If not, then it is not
installed correctly. Make sure you have at least the 4.0 version of NodeJS installed.
Can't find the debug visual in the Visualizations tab
The debug visual looks like a prompt icon within the Visualizations tab.

If you don't see it, make sure you have enabled it within the Power BI settings.

NOTE
The debug visual is currently only available in the Power BI service and not in Power BI Desktop or the mobile app. The
packaged visual will still work everywhere.

Can't contact visual server

Run the visual server with the command pbiviz start in your terminal's command line from the root of your
visual project. If the server is not running, it is likely that your SSL certificates weren't installed correctly.
Feel free to contact the custom visuals support team:*[email protected]*with any questions,
comments, or issues you have.

Next steps
For more information, visit Frequently asked questions about Power BI custom visuals.
 What can developers do with the Power BI API?
4/2/2019 • 2 minutes to read • Edit Online

Using Power BI REST API, you can create apps that integrate with Power BI reports, dashboards, and tiles.
With Power BI REST API, it is possible to perform management tasks on Power BI objects like reports, datasets,
and workspaces.
Here are some of the things you can do with the Power BI APIs.

TO LEARN MORE REFERENCE THIS INFORMATION

Embed reports, dashboards, and tiles for Power BI users and How to embed your Power BI dashboards, reports, and tiles
Non-Power BI users.

Perform management tasks on Power BI objects. Power BI REST API reference

Extend an existing business workflow to push key data into a Push data into a dashboard
Power BI dashboard.

Authenticate to Power BI. Authenticate to Power BI

NOTE
The Power BI APIs still refer to app workspaces as groups. Any references to groups mean that you are working with app
workspaces.

API Developer tools

TOOL(S) DESCRIPTION

Playground tool Experience a full sample of

using the Power BI
JavaScript APIs. This tool is
also a quick way to play with
different types of Power BI
Embedded samples.

Power BI JavaScript wiki To get more Information

about the Power BI
JavaScript APIs.

Postman Run requests, test, debug,

monitor, run automated
tests and more.

Push data into Power BI

You can use the Power BI API to push data into a dataset. This feature allows you to add a row to a table within a
dataset. The new data is then reflected in tiles on a dashboard and within visuals within your report.
GitHub repositories
Power BI Developer samples
.NET SDK
JavaScript API

Next Steps
Push data into a dataset
Developing a Power BI custom visual
Power BI REST API Reference
Power BI REST APIs
More questions? Try asking the Power BI Community
 Push data into a Power BI dataset
2/6/2019 • 2 minutes to read • Edit Online

With the Power BI API, you can push data into a Power BI dataset. For example, you want to extend an existing
business workflow to push key data into your dataset. In this case, you want to push a Sales Marketing dataset
which has a Product table into a dataset.
Before you get started pushing data into a dataset, you need an Azure Active Directory (Azure AD ) and a Power
BI account.

Steps to push data into a dataset

Step 1: Register an app with Azure AD
Step 2: Get an authentication access token
Step 3: Create a dataset in Power BI
Step 4: Get a dataset to add rows into a Power BI table
Step 5: Add rows to a Power BI table
The next section is a general discussion of Power BI API operations that push data.

Power BI API operations to push data

With the Power BI REST API, you can push data sources to Power BI. When an app adds rows to a dataset, tiles
on the dashboard are updated automatically with the updated data. To push data, you use the PostDataset
operation along with the PostRows operation. To find a dataset, you use the Get Datasets operation. For any of
these operations, you can pass a group id to work with a group. Use the Get Groups operation to get a list of
group id's.
Here are the operations to push data into a dataset:
PostDataset
Get Datasets
Post Rows
Get Groups
You create a dataset in Power BI by passing a JavaScript Object Notation (JSON ) string to the Power BI service.
To learn more about JSON, see Introducing JSON.
The JSON string for a dataset has the following format:
Power BI Dataset JSON object

{"name": "dataset_name", "tables":

[{"name": "", "columns":
[{ "name": "column_name1", "dataType": "data_type"},
{ "name": "column_name2", "dataType": "data_type"},
{ ... }
]
}
]
}
So, for our Sales Marketing dataset example, you would pass a JSON string such as the example below. In this
example, SalesMarketing is the name of the dataset, and Product is the name of the table. After you define
the table, you define the table schema. For the SalesMarketing dataset, the table schema has these columns:
ProductID, Manufacturer, Category, Segment, Product, and IsCompete.
Example dataset object JSON

{
"name": "SalesMarketing",
"tables": [
{
"name": "Product",
"columns": [
{
"name": "ProductID",
"dataType": "int"
},
{
"name": "Manufacturer",
"dataType": "string"
},
{
"name": "Category",
"dataType": "string"
},
{
"name": "Segment",
"dataType": "string"
},
{
"name": "Product",
"dataType": "string"
},
{
"name": "IsCompete",
"dataType": "bool"
}
]
}
]
}

For a Power BI table schema, you can use the following data types.

Power BI table data types

DATA TYPE RESTRICTIONS

Int64 Int64.MaxValue and Int64.MinValue not allowed.

Double Double.MaxValue and Double.MinValue values not allowed.

NaN not supported.+Infinity and -Infinity not supported in
some functions (e.g. Min, Max).

Boolean None

Datetime During data loading we quantize values with day fractions to

whole multiples of 1/300 seconds (3.33ms).

String Currently allows up to 128K characters.

Learn more about pushing data into Power BI
To get started pushing data into a dataset, see Step 1: Register an app with Azure AD in the left navigation pane.
Next Step >

Next steps
Sign up for Power BI
Introducing JSON
Overview of Power BI REST API
More questions? Try the Power BI Community
 Step 1: Register an app with Azure AD
2/6/2019 • 2 minutes to read • Edit Online

This article is part of a step-by-step walkthrough to push data into a dataset.

The first step to push data into a Power BI dataset is to register your app in Azure AD. You need to do this first so
that you have a Client ID that identifies your app in Azure AD. Without a Client ID, Azure AD cannot
authenticate your app.

NOTE: Before you register an app for Power BI, you need to Sign up for Power BI.

Here are the steps to register an app in Azure AD.

Register an app in Azure AD

1. Go to dev.powerbi.com/apps.
2. Click Sign in with your existing account, and sign into your Power BI account.
3. Enter an App Name such as "Sample push data app".
4. For App Type, choose Native app.
5. Enter a Redirect URL, such as https://login.live.com/oauth20_desktop.srf. For a Native client app, a
redirect uri gives Azure AD more details on the specific application that it will authenticate. The standard Uri
for a client app is https://login.live.com/oauth20_desktop.srf.
6. For Choose APIs to access, choose Read and Write All Datasets. For all Power BI app permissions, see
Power BI Permissions.
7. Click Register app, and save the Client ID that was generated. A Client ID identifies the app in Azure AD.
Here's how your Register an Application for Power BI page should look:
The next step shows you how to get an authentication access token.
Next Step >

Next steps
Sign up for Power BI
Get an authentication access token
Walkthrough: Push data into a dataset
Register an application
Overview of Power BI REST API
More questions? Try asking the Power BI Community
 Step 2: Get an authentication access token
2/13/2019 • 4 minutes to read • Edit Online

This article is part of a step-by-step walkthrough to push data into a dataset.

In step 1 of Push data into a dataset, Register the app with Azure AD, you registered a client app in Azure AD. In
this step, you get an authentication access token. Power BI apps are integrated with Azure AD to provide secure
sign in and authorization for your app. You use a token to authenticate to Azure AD and gain access to Power BI
resources.
Here's how to get an authentication access token.

Get an authentication access token

NOTE: Before you get started, make sure you have followed the previous steps in the push data into a
dataset walkthrough.

1. In Visual Studio 2015, create a Console Application project.

2. Install the Azure AD Authentication Library for .NET NuGet package. To get an authentication security
token in a .NET app, you use this package. Here's how to install the package:
a. In Visual Studio 2015, choose Tools > NuGet Package Manager > Package Manager Console.
b. In Package Manager Console, enter Install-Package Microsoft.IdentityModel.Clients.ActiveDirectory -
Version 2.21.301221612.
3. Add the code below into class Program {...}.
4. Replace "{ClientID }", with the Client ID you got when you registered the app. See Register the app with
Azure AD.
5. After installing the Microsoft.IdentityModel.Clients.ActiveDirectory package, add using
Microsoft.IdentityModel.Clients.ActiveDirectory; to Program.cs.
6. Run the Console App, and login to your Power BI account. You should see a token string in the Console
Window.
Sample code to get authentication security token
Add this code to Program {...}.
A token variable to call operations:

private static string token = string.Empty;

static void Main(string[] args)

{
}

In static void Main(string[] args):

 static void Main(string[] args)
{
//Get an authentication access token
token = GetToken();
}

Add a GetToken() method:

#region Get an authentication access token

private static string GetToken()
{
// TODO: Install-Package Microsoft.IdentityModel.Clients.ActiveDirectory -Version 2.21.301221612
// and add using Microsoft.IdentityModel.Clients.ActiveDirectory

//The client id that Azure AD created when you registered your client app.
string clientID = "{Client_ID}";

//RedirectUri you used when you register your app.

//For a client app, a redirect uri gives Azure AD more details on the application that it will
authenticate.
// You can use this redirect uri for your client app
string redirectUri = "https://login.live.com/oauth20_desktop.srf";

//Resource Uri for Power BI API

string resourceUri = "https://analysis.windows.net/powerbi/api";

//OAuth2 authority Uri

string authorityUri = "https://login.microsoftonline.net/common/";

//Get access token:

// To call a Power BI REST operation, create an instance of AuthenticationContext and call
AcquireToken
// AuthenticationContext is part of the Active Directory Authentication Library NuGet package
// To install the Active Directory Authentication Library NuGet package in Visual Studio,
// run "Install-Package Microsoft.IdentityModel.Clients.ActiveDirectory" from the nuget Package
Manager Console.

// AcquireToken will acquire an Azure access token

// Call AcquireToken to get an Azure token from Azure Active Directory token issuance endpoint
AuthenticationContext authContext = new AuthenticationContext(authorityUri);
string token = authContext.AcquireToken(resourceUri, clientID, new Uri(redirectUri)).AccessToken;

Console.WriteLine(token);
Console.ReadLine();

return token;
}

#endregion

After you get an authentication token, you can call any Power BI operation. The next step shows you how to call
the PostDataset operation to create a dataset to push data into a dashboard.
The next step shows you how to create a dataset in Power BI.
Below is the complete code listing.

Complete code listing

 using System;
using Microsoft.IdentityModel.Clients.ActiveDirectory;

namespace walkthrough_push_data
{
class Program
{
private static string token = string.Empty;

static void Main(string[] args)

{

//Get an authentication access token

token = GetToken();

#region Get an authentication access token

private static string GetToken()
{
// TODO: Install-Package Microsoft.IdentityModel.Clients.ActiveDirectory -Version 2.21.301221612
// and add using Microsoft.IdentityModel.Clients.ActiveDirectory

//The client id that Azure AD created when you registered your client app.
string clientID = "{Client_ID}";

//RedirectUri you used when you register your app.

//For a client app, a redirect uri gives Azure AD more details on the application that it will
authenticate.
// You can use this redirect uri for your client app
string redirectUri = "https://login.live.com/oauth20_desktop.srf";

//Resource Uri for Power BI API

string resourceUri = "https://analysis.windows.net/powerbi/api";

//OAuth2 authority Uri

string authorityUri = "https://login.microsoftonline.net/common/";

//Get access token:

// To call a Power BI REST operation, create an instance of AuthenticationContext and call
AcquireToken
// AuthenticationContext is part of the Active Directory Authentication Library NuGet package
// To install the Active Directory Authentication Library NuGet package in Visual Studio,
// run "Install-Package Microsoft.IdentityModel.Clients.ActiveDirectory" from the nuget Package
Manager Console.

// AcquireToken will acquire an Azure access token

// Call AcquireToken to get an Azure token from Azure Active Directory token issuance endpoint
AuthenticationContext authContext = new AuthenticationContext(authorityUri);
string token = authContext.AcquireToken(resourceUri, clientID, new Uri(redirectUri)).AccessToken;

Console.WriteLine(token);
Console.ReadLine();

return token;
}

#endregion

}
}

Next Step >

Next steps
Create a dataset in Power BI
Register an app with Azure AD
Azure AD Authentication Library for .NET NuGet package
Push data into a Power BI dataset
Overview of Power BI REST API
Power BI REST API reference
More questions? Try the Power BI Community
 Step 3: Create a dataset in Power BI
2/13/2019 • 4 minutes to read • Edit Online

This article is part of a step-by-step walkthrough to push data into a dataset.

In step 2 of Push data into a dataset, Get an authentication access token, you got a token to authenticate to Azure
AD. In this step, you use the token to call the PostDataset operation.
To make a call to a REST resource, you use a url that locates the resource, and you send a JavaScript Object
Notation (JSON ) string, which describes the dataset, to the Power BI service resource. A REST resource identifies
the part of the Power BI service you want to work with. To push data into the dataset, the target resource is a
Dataset. The URL that identifies a dataset is https://api.PowerBI.com/v1.0/myorg/datasets. If you are pushing
data within a group, the url is https://api.PowerBI.com/v1.0/myorg/groups/{group_id}/datasets.
To authenticate a Power BI REST operation, you add the token you got in Get an authentication access token to a
request header:
When you call the PostDataset operation, a new dataset is created.

Here's how to create a dataset in Power BI.

Create a dataset in Power BI

NOTE
Before you get started, make sure you have followed the previous steps in the push data into a dataset walkthrough.

1. In the Console Application project you created in Step 2 - Get an authentication access token, add using
System.Net;, and using System.IO; to Program.cs.
2. In Program.cs, add the code below.
3. Run the Console App, and login to your Power BI account. You should see Dataset Created in the Console
 Window. Also, you can login to Power BI to see the new dataset.
Sample push data into a dataset
Add this code into Program.cs.
In static void Main(string[] args):

static void Main(string[] args)

{
//Get an authentication access token
token = GetToken();

//Create a dataset in Power BI

CreateDataset();
}

Add a CreateDataset() method:

 #region Create a dataset in Power BI
private static void CreateDataset()
{
//TODO: Add using System.Net and using System.IO

string powerBIDatasetsApiUrl = "https://api.powerbi.com/v1.0/myorg/datasets";

//POST web request to create a dataset.
//To create a Dataset in a group, use the Groups uri:
https://api.PowerBI.com/v1.0/myorg/groups/{group_id}/datasets
HttpWebRequest request = System.Net.WebRequest.Create(powerBIDatasetsApiUrl) as
System.Net.HttpWebRequest;
request.KeepAlive = true;
request.Method = "POST";
request.ContentLength = 0;
request.ContentType = "application/json";

//Add token to the request header

request.Headers.Add("Authorization", String.Format("Bearer {0}", token));

//Create dataset JSON for POST request

string datasetJson = "{\"name\": \"SalesMarketing\", \"tables\": " +
"[{\"name\": \"Product\", \"columns\": " +
"[{ \"name\": \"ProductID\", \"dataType\": \"Int64\"}, " +
"{ \"name\": \"Name\", \"dataType\": \"string\"}, " +
"{ \"name\": \"Category\", \"dataType\": \"string\"}," +
"{ \"name\": \"IsCompete\", \"dataType\": \"bool\"}," +
"{ \"name\": \"ManufacturedOn\", \"dataType\": \"DateTime\"}" +
"]}]}";

//POST web request

byte[] byteArray = System.Text.Encoding.UTF8.GetBytes(datasetJson);
request.ContentLength = byteArray.Length;

//Write JSON byte[] into a Stream

using (Stream writer = request.GetRequestStream())
{
writer.Write(byteArray, 0, byteArray.Length);

var response = (HttpWebResponse)request.GetResponse();

Console.WriteLine(string.Format("Dataset {0}", response.StatusCode.ToString()));

Console.ReadLine();
}
}
#endregion

The next step shows you how to get a dataset to add rows into a Power BI table.
Below is the complete code listing.

Complete code listing

using System;
using Microsoft.IdentityModel.Clients.ActiveDirectory;
using System.Net;
using System.IO;

namespace walkthrough_push_data
{
class Program
{
private static string token = string.Empty;

static void Main(string[] args)

 static void Main(string[] args)
{

//Get an authentication access token

token = GetToken();

//Create a dataset in Power BI

CreateDataset();

#region Get an authentication access token

private static string GetToken()
{
// TODO: Install-Package Microsoft.IdentityModel.Clients.ActiveDirectory -Version 2.21.301221612
// and add using Microsoft.IdentityModel.Clients.ActiveDirectory

//The client id that Azure AD created when you registered your client app.
string clientID = "{Client_ID}";

//RedirectUri you used when you register your app.

//For a client app, a redirect uri gives Azure AD more details on the application that it will
authenticate.
// You can use this redirect uri for your client app
string redirectUri = "https://login.live.com/oauth20_desktop.srf";

//Resource Uri for Power BI API

string resourceUri = "https://analysis.windows.net/powerbi/api";

//OAuth2 authority Uri

string authorityUri = "https://login.microsoftonline.net/common/";

//Get access token:

// To call a Power BI REST operation, create an instance of AuthenticationContext and call
AcquireToken
// AuthenticationContext is part of the Active Directory Authentication Library NuGet package
// To install the Active Directory Authentication Library NuGet package in Visual Studio,
// run "Install-Package Microsoft.IdentityModel.Clients.ActiveDirectory" from the nuget Package
Manager Console.

// AcquireToken will acquire an Azure access token

// Call AcquireToken to get an Azure token from Azure Active Directory token issuance endpoint
AuthenticationContext authContext = new AuthenticationContext(authorityUri);
string token = authContext.AcquireToken(resourceUri, clientID, new Uri(redirectUri)).AccessToken;

Console.WriteLine(token);
Console.ReadLine();

return token;
}

#endregion

#region Create a dataset in Power BI

private static void CreateDataset()
{
//TODO: Add using System.Net and using System.IO

string powerBIDatasetsApiUrl = "https://api.powerbi.com/v1.0/myorg/datasets";

//POST web request to create a dataset.
//To create a Dataset in a group, use the Groups uri:
https://api.PowerBI.com/v1.0/myorg/groups/{group_id}/datasets
HttpWebRequest request = System.Net.WebRequest.Create(powerBIDatasetsApiUrl) as
System.Net.HttpWebRequest;
request.KeepAlive = true;
request.Method = "POST";
request.ContentLength = 0;
request.ContentType = "application/json";
 //Add token to the request header
request.Headers.Add("Authorization", String.Format("Bearer {0}", token));

//Create dataset JSON for POST request

string datasetJson = "{\"name\": \"SalesMarketing\", \"tables\": " +
"[{\"name\": \"Product\", \"columns\": " +
"[{ \"name\": \"ProductID\", \"dataType\": \"Int64\"}, " +
"{ \"name\": \"Name\", \"dataType\": \"string\"}, " +
"{ \"name\": \"Category\", \"dataType\": \"string\"}," +
"{ \"name\": \"IsCompete\", \"dataType\": \"bool\"}," +
"{ \"name\": \"ManufacturedOn\", \"dataType\": \"DateTime\"}" +
"]}]}";

//POST web request

byte[] byteArray = System.Text.Encoding.UTF8.GetBytes(datasetJson);
request.ContentLength = byteArray.Length;

//Write JSON byte[] into a Stream

using (Stream writer = request.GetRequestStream())
{
writer.Write(byteArray, 0, byteArray.Length);

var response = (HttpWebResponse)request.GetResponse();

Console.WriteLine(string.Format("Dataset {0}", response.StatusCode.ToString()));

Console.ReadLine();
}
}
#endregion
}
}

Next Step >

Next steps
Get a dataset to add rows into a Power BI table
Get an authentication access token
PostDataset
PostDatasetInGroup
Push data into a Power BI Dashboard
Overview of Power BI REST API
Power BI REST API reference
More questions? Try the Power BI Community
 Step 4: Get a dataset to add rows into a Power BI
table
2/13/2019 • 5 minutes to read • Edit Online

This article is part of a step-by-step walkthrough to push data into a dataset.

In step 3 of Push data into a dataset, Create a dataset in Power BI, you called the Create Dataset operation to
create a dataset in Power BI. In this step, you use the Get Datasets operation and Newtonsoft.Json to get a dataset
id. You use the dataset id in step 4 to add rows to a dataset.
To push data into a Power BI dataset, you need to reference the table in the dataset. To reference a table in a
dataset, you first need to get a Dataset ID. You get a Dataset ID using the Get Dataset By ID operation. The Get
Dataset By ID operation returns a JSON string containing a list of all datasets in Power BI. The recommended
way to deserialize a JSON string is with Newtonsoft.Json.
Here's how you get a dataset.

Get a Power BI dataset

NOTE: Before you get started, make sure you have followed the previous steps in the push data into a dataset
walkthrough.

1. In the Console Application project you created in Step 2: Walkthrough to push data, Get an authentication
access token, install the Newtonsoft.Json NuGet package. Here's how to install the package:
a. In Visual Studio 2015, choose Tools > NuGet Package Manager > Package Manager Console.
b. In Package Manager Console, enter Install-Package Newtonsoft.Json.
2. After the package is installed, add using Newtonsoft.Json; to Program.cs.
3. In Program.cs, add the code below to get a Dataset ID.
4. Run the Console App, and login to your Power BI account. You should see Dataset ID: followed by an id in
the Console Window.
Sample get a dataset
Add this code into Program.cs.
In static void Main(string[] args):

static void Main(string[] args)

{

//Get an authentication access token

token = GetToken();

//Create a dataset in Power BI

CreateDataset();

//Get a dataset to add rows into a Power BI table

string datasetId = GetDataset();
}
 Add a GetDatset() method:

#region Get a dataset to add rows into a Power BI table

private static string GetDataset()
{
string powerBIDatasetsApiUrl = "https://api.powerbi.com/v1.0/myorg/datasets";
//POST web request to create a dataset.
//To create a Dataset in a group, use the Groups uri:
https://api.PowerBI.com/v1.0/myorg/groups/{group_id}/datasets
HttpWebRequest request = System.Net.WebRequest.Create(powerBIDatasetsApiUrl) as
System.Net.HttpWebRequest;
request.KeepAlive = true;
request.Method = "GET";
request.ContentLength = 0;
request.ContentType = "application/json";

//Add token to the request header

request.Headers.Add("Authorization", String.Format("Bearer {0}", token));

string datasetId = string.Empty;

//Get HttpWebResponse from GET request
using (HttpWebResponse httpResponse = request.GetResponse() as System.Net.HttpWebResponse)
{
//Get StreamReader that holds the response stream
using (StreamReader reader = new System.IO.StreamReader(httpResponse.GetResponseStream()))
{
string responseContent = reader.ReadToEnd();

//TODO: Install NuGet Newtonsoft.Json package: Install-Package Newtonsoft.Json

//and add using Newtonsoft.Json
var results = JsonConvert.DeserializeObject<dynamic>(responseContent);

//Get the first id

datasetId = results["value"][0]["id"];

Console.WriteLine(String.Format("Dataset ID: {0}", datasetId));

Console.ReadLine();

return datasetId;
}
}
}
#endregion

The next step shows you how to add rows to a Power BI table.
Below is the complete code listing.

Complete code listing

using System;
using Microsoft.IdentityModel.Clients.ActiveDirectory;
using System.Net;
using System.IO;
using Newtonsoft.Json;

namespace walkthrough_push_data
{
class Program
{
private static string token = string.Empty;

static void Main(string[] args)

{
 //Get an authentication access token
token = GetToken();

//Create a dataset in Power BI

CreateDataset();

//Get a dataset to add rows into a Power BI table

string datasetId = GetDataset();

#region Get an authentication access token

private static string GetToken()
{
// TODO: Install-Package Microsoft.IdentityModel.Clients.ActiveDirectory -Version 2.21.301221612
// and add using Microsoft.IdentityModel.Clients.ActiveDirectory

//The client id that Azure AD created when you registered your client app.
string clientID = "{Client_ID}";

//RedirectUri you used when you register your app.

//For a client app, a redirect uri gives Azure AD more details on the application that it will
authenticate.
// You can use this redirect uri for your client app
string redirectUri = "https://login.live.com/oauth20_desktop.srf";

//Resource Uri for Power BI API

string resourceUri = "https://analysis.windows.net/powerbi/api";

//OAuth2 authority Uri

string authorityUri = "https://login.microsoftonline.net/common/";

//Get access token:

// To call a Power BI REST operation, create an instance of AuthenticationContext and call
AcquireToken
// AuthenticationContext is part of the Active Directory Authentication Library NuGet package
// To install the Active Directory Authentication Library NuGet package in Visual Studio,
// run "Install-Package Microsoft.IdentityModel.Clients.ActiveDirectory" from the nuget Package
Manager Console.

// AcquireToken will acquire an Azure access token

// Call AcquireToken to get an Azure token from Azure Active Directory token issuance endpoint
AuthenticationContext authContext = new AuthenticationContext(authorityUri);
string token = authContext.AcquireToken(resourceUri, clientID, new Uri(redirectUri)).AccessToken;

Console.WriteLine(token);
Console.ReadLine();

return token;
}

#endregion

#region Create a dataset in Power BI

private static void CreateDataset()
{
//TODO: Add using System.Net and using System.IO

string powerBIDatasetsApiUrl = "https://api.powerbi.com/v1.0/myorg/datasets";

//POST web request to create a dataset.
//To create a Dataset in a group, use the Groups uri:
https://api.PowerBI.com/v1.0/myorg/groups/{group_id}/datasets
HttpWebRequest request = System.Net.WebRequest.Create(powerBIDatasetsApiUrl) as
System.Net.HttpWebRequest;
request.KeepAlive = true;
request.Method = "POST";
request.ContentLength = 0;
request.ContentType = "application/json";
 //Add token to the request header
request.Headers.Add("Authorization", String.Format("Bearer {0}", token));

//Create dataset JSON for POST request

string datasetJson = "{\"name\": \"SalesMarketing\", \"tables\": " +
"[{\"name\": \"Product\", \"columns\": " +
"[{ \"name\": \"ProductID\", \"dataType\": \"Int64\"}, " +
"{ \"name\": \"Name\", \"dataType\": \"string\"}, " +
"{ \"name\": \"Category\", \"dataType\": \"string\"}," +
"{ \"name\": \"IsCompete\", \"dataType\": \"bool\"}," +
"{ \"name\": \"ManufacturedOn\", \"dataType\": \"DateTime\"}" +
"]}]}";

//POST web request

byte[] byteArray = System.Text.Encoding.UTF8.GetBytes(datasetJson);
request.ContentLength = byteArray.Length;

//Write JSON byte[] into a Stream

using (Stream writer = request.GetRequestStream())
{
writer.Write(byteArray, 0, byteArray.Length);

var response = (HttpWebResponse)request.GetResponse();

Console.WriteLine(string.Format("Dataset {0}", response.StatusCode.ToString()));

Console.ReadLine();
}
}
#endregion

#region Get a dataset to add rows into a Power BI table

private static string GetDataset()
{
string powerBIDatasetsApiUrl = "https://api.powerbi.com/v1.0/myorg/datasets";
//POST web request to create a dataset.
//To create a Dataset in a group, use the Groups uri:
https://api.PowerBI.com/v1.0/myorg/groups/{group_id}/datasets
HttpWebRequest request = System.Net.WebRequest.Create(powerBIDatasetsApiUrl) as
System.Net.HttpWebRequest;
request.KeepAlive = true;
request.Method = "GET";
request.ContentLength = 0;
request.ContentType = "application/json";

//Add token to the request header

request.Headers.Add("Authorization", String.Format("Bearer {0}", token));

string datasetId = string.Empty;

//Get HttpWebResponse from GET request
using (HttpWebResponse httpResponse = request.GetResponse() as System.Net.HttpWebResponse)
{
//Get StreamReader that holds the response stream
using (StreamReader reader = new System.IO.StreamReader(httpResponse.GetResponseStream()))
{
string responseContent = reader.ReadToEnd();

//TODO: Install NuGet Newtonsoft.Json package: Install-Package Newtonsoft.Json

//and add using Newtonsoft.Json
var results = JsonConvert.DeserializeObject<dynamic>(responseContent);

//Get the first id

datasetId = results["value"][0]["id"];

Console.WriteLine(String.Format("Dataset ID: {0}", datasetId));

Console.ReadLine();

return datasetId;
}
 }
}
}
#endregion
}
}

Next Step >

Next steps
Add rows to a Power BI table
Newtonsoft.Json
Get Datasets
Push data into Power BI
Overview of Power BI REST API
Power BI REST API reference
More questions? Try the Power BI Community
 Step 5: Add rows to a Power BI table
2/13/2019 • 5 minutes to read • Edit Online

This article is part of a step-by-step walkthrough to push data into a dataset.

In step 4 of Push data into a dataset, Get a dataset to add rows into a Power BI table, you used the Get Datasets
operation and Newtonsoft.Json to get a dataset id. In this step, you use the dataset id with the PostRows operation
to add rows to a Power BI dataset.
When you call the PostRows operation, you add rows to a dataset.

Here's how to add rows to a dataset using the Power BI API.

Add rows to a Power BI table

NOTE
Before you get started, make sure you have followed the previous steps in the push data into a dataset walkthrough.

1. In the Console Application project you created in Step 2: Walkthrough to push data, Get an authentication
access token, add the code below.
2. Run the Console App, and login to your Power BI account. You should see Rows Added in the Console
Window. You can also login to Power BI to see the rows added to the dataset.
Sample push data into a dataset
Add this code into Program.cs.
In static void Main(string[] args):
 static void Main(string[] args)
{

//Get an authentication access token

token = GetToken();

//Create a dataset in Power BI

CreateDataset();

//Get a dataset to add rows into a Power BI table

string datasetId = GetDataset();

//Add rows to a Power BI table

AddRows(datasetId, "Product");
}

Add an AddRows() method:

 #region Add rows to a Power BI table
private static void AddRows(string datasetId, string tableName)
{
string powerBIApiAddRowsUrl =
String.Format("https://api.powerbi.com/v1.0/myorg/datasets/{0}/tables/{1}/rows", datasetId, tableName);

//POST web request to add rows.

//To add rows to a dataset in a group, use the Groups uri:
https://api.powerbi.com/v1.0/myorg/groups/{group_id}/datasets/{dataset_id}/tables/{table_name}/rows
//Change request method to "POST"
HttpWebRequest request = System.Net.WebRequest.Create(powerBIApiAddRowsUrl) as
System.Net.HttpWebRequest;
request.KeepAlive = true;
request.Method = "POST";
request.ContentLength = 0;
request.ContentType = "application/json";

//Add token to the request header

request.Headers.Add("Authorization", String.Format("Bearer {0}", token));

//JSON content for product row

string rowsJson = "{\"rows\":" +
"[{\"ProductID\":1,\"Name\":\"Adjustable
Race\",\"Category\":\"Components\",\"IsCompete\":true,\"ManufacturedOn\":\"07/30/2014\"}," +
"{\"ProductID\":2,\"Name\":\"LL
Crankarm\",\"Category\":\"Components\",\"IsCompete\":true,\"ManufacturedOn\":\"07/30/2014\"}," +
"{\"ProductID\":3,\"Name\":\"HL Mountain Frame -
Silver\",\"Category\":\"Bikes\",\"IsCompete\":true,\"ManufacturedOn\":\"07/30/2014\"}]}";

//POST web request

byte[] byteArray = System.Text.Encoding.UTF8.GetBytes(rowsJson);
request.ContentLength = byteArray.Length;

//Write JSON byte[] into a Stream

using (Stream writer = request.GetRequestStream())
{
writer.Write(byteArray, 0, byteArray.Length);

var response = (HttpWebResponse)request.GetResponse();

Console.WriteLine("Rows Added");

Console.ReadLine();
}
}

#endregion

Below is the complete code listing.

Complete code listing

using System;
using Microsoft.IdentityModel.Clients.ActiveDirectory;
using System.Net;
using System.IO;
using Newtonsoft.Json;

namespace walkthrough_push_data
{
class Program
{
private static string token = string.Empty;

static void Main(string[] args)

 {

//Get an authentication access token

token = GetToken();

//Create a dataset in Power BI

CreateDataset();

//Get a dataset to add rows into a Power BI table

string datasetId = GetDataset();

//Add rows to a Power BI table

AddRows(datasetId, "Product");

#region Get an authentication access token

private static string GetToken()
{
// TODO: Install-Package Microsoft.IdentityModel.Clients.ActiveDirectory -Version
2.21.301221612
// and add using Microsoft.IdentityModel.Clients.ActiveDirectory

//The client id that Azure AD created when you registered your client app.
string clientID = "{Client_ID}";

//RedirectUri you used when you register your app.

//For a client app, a redirect uri gives Azure AD more details on the application that it will
authenticate.
// You can use this redirect uri for your client app
string redirectUri = "https://login.live.com/oauth20_desktop.srf";

//Resource Uri for Power BI API

string resourceUri = "https://analysis.windows.net/powerbi/api";

//OAuth2 authority Uri

string authorityUri = "https://login.microsoftonline.net/common/";

//Get access token:

// To call a Power BI REST operation, create an instance of AuthenticationContext and call
AcquireToken
// AuthenticationContext is part of the Active Directory Authentication Library NuGet package
// To install the Active Directory Authentication Library NuGet package in Visual Studio,
// run "Install-Package Microsoft.IdentityModel.Clients.ActiveDirectory" from the nuget
Package Manager Console.

// AcquireToken will acquire an Azure access token

// Call AcquireToken to get an Azure token from Azure Active Directory token issuance endpoint
AuthenticationContext authContext = new AuthenticationContext(authorityUri);
string token = authContext.AcquireToken(resourceUri, clientID, new
Uri(redirectUri)).AccessToken;

Console.WriteLine(token);
Console.ReadLine();

return token;
}

#endregion

#region Create a dataset in a Power BI

private static void CreateDataset()
{
//TODO: Add using System.Net and using System.IO

string powerBIDatasetsApiUrl = "https://api.powerbi.com/v1.0/myorg/datasets";

//POST web request to create a dataset.
//To create a Dataset in a group, use the Groups uri:
https://api.PowerBI.com/v1.0/myorg/groups/{group_id}/datasets
 HttpWebRequest request = System.Net.WebRequest.Create(powerBIDatasetsApiUrl) as
System.Net.HttpWebRequest;
request.KeepAlive = true;
request.Method = "POST";
request.ContentLength = 0;
request.ContentType = "application/json";

//Add token to the request header

request.Headers.Add("Authorization", String.Format("Bearer {0}", token));

//Create dataset JSON for POST request

string datasetJson = "{\"name\": \"SalesMarketing\", \"tables\": " +
"[{\"name\": \"Product\", \"columns\": " +
"[{ \"name\": \"ProductID\", \"dataType\": \"Int64\"}, " +
"{ \"name\": \"Name\", \"dataType\": \"string\"}, " +
"{ \"name\": \"Category\", \"dataType\": \"string\"}," +
"{ \"name\": \"IsCompete\", \"dataType\": \"bool\"}," +
"{ \"name\": \"ManufacturedOn\", \"dataType\": \"DateTime\"}" +
"]}]}";

//POST web request

byte[] byteArray = System.Text.Encoding.UTF8.GetBytes(datasetJson);
request.ContentLength = byteArray.Length;

//Write JSON byte[] into a Stream

using (Stream writer = request.GetRequestStream())
{
writer.Write(byteArray, 0, byteArray.Length);

var response = (HttpWebResponse)request.GetResponse();

Console.WriteLine(string.Format("Dataset {0}", response.StatusCode.ToString()));

Console.ReadLine();
}
}
#endregion

#region Get a dataset to add rows into a Power BI table

private static string GetDataset()
{
string powerBIDatasetsApiUrl = "https://api.powerbi.com/v1.0/myorg/datasets";
//POST web request to create a dataset.
//To create a Dataset in a group, use the Groups uri:
https://api.PowerBI.com/v1.0/myorg/groups/{group_id}/datasets
HttpWebRequest request = System.Net.WebRequest.Create(powerBIDatasetsApiUrl) as
System.Net.HttpWebRequest;
request.KeepAlive = true;
request.Method = "GET";
request.ContentLength = 0;
request.ContentType = "application/json";

//Add token to the request header

request.Headers.Add("Authorization", String.Format("Bearer {0}", token));

string datasetId = string.Empty;

//Get HttpWebResponse from GET request
using (HttpWebResponse httpResponse = request.GetResponse() as System.Net.HttpWebResponse)
{
//Get StreamReader that holds the response stream
using (StreamReader reader = new System.IO.StreamReader(httpResponse.GetResponseStream()))
{
string responseContent = reader.ReadToEnd();

//TODO: Install NuGet Newtonsoft.Json package: Install-Package Newtonsoft.Json

//and add using Newtonsoft.Json
var results = JsonConvert.DeserializeObject<dynamic>(responseContent);

//Get the first id

 //Get the first id
datasetId = results["value"][0]["id"];

Console.WriteLine(String.Format("Dataset ID: {0}", datasetId));

Console.ReadLine();

return datasetId;
}
}
}
#endregion

#region Add rows to a Power BI table

private static void AddRows(string datasetId, string tableName)
{
string powerBIApiAddRowsUrl =
String.Format("https://api.powerbi.com/v1.0/myorg/datasets/{0}/tables/{1}/rows", datasetId, tableName);

//POST web request to add rows.

//To add rows to a dataset in a group, use the Groups uri:
https://api.powerbi.com/v1.0/myorg/groups/{group_id}/datasets/{dataset_id}/tables/{table_name}/rows
//Change request method to "POST"
HttpWebRequest request = System.Net.WebRequest.Create(powerBIApiAddRowsUrl) as
System.Net.HttpWebRequest;
request.KeepAlive = true;
request.Method = "POST";
request.ContentLength = 0;
request.ContentType = "application/json";

//Add token to the request header

request.Headers.Add("Authorization", String.Format("Bearer {0}", token));

//JSON content for product row

string rowsJson = "{\"rows\":" +
"[{\"ProductID\":1,\"Name\":\"Adjustable
Race\",\"Category\":\"Components\",\"IsCompete\":true,\"ManufacturedOn\":\"07/30/2014\"}," +
"{\"ProductID\":2,\"Name\":\"LL
Crankarm\",\"Category\":\"Components\",\"IsCompete\":true,\"ManufacturedOn\":\"07/30/2014\"}," +
"{\"ProductID\":3,\"Name\":\"HL Mountain Frame -
Silver\",\"Category\":\"Bikes\",\"IsCompete\":true,\"ManufacturedOn\":\"07/30/2014\"}]}";

//POST web request

byte[] byteArray = System.Text.Encoding.UTF8.GetBytes(rowsJson);
request.ContentLength = byteArray.Length;

//Write JSON byte[] into a Stream

using (Stream writer = request.GetRequestStream())
{
writer.Write(byteArray, 0, byteArray.Length);

var response = (HttpWebResponse)request.GetResponse();

Console.WriteLine("Rows Added");

Console.ReadLine();
}
}

#endregion
}
}

Although, we specify that we //Get the first id in the code above, the correct thing to do is search the dataset by
name.

Next steps
Push data into a Power BI Dashboard
Overview of Power BI REST API
Power BI REST API reference
More questions? Try the Power BI Community
 Automatic retention policy for real-time data
2/6/2019 • 2 minutes to read • Edit Online

The automatic retention policy in the Power BI service is a query string parameter, which enables a default
retention policy to automatically clean up old data while keeping a constant flow of new data going into your
dashboard. The first retention policy is called first in first out (FIFO ). When enabled, the data is collected in a table
until it hits 200,000 rows. Once the data goes beyond 200,000 rows, the oldest rows get dropped from the dataset.
This maintains between 200,000 and 210,000 rows of only the latest data.

The retention policies are enabled when you first create your datasets. All you need to do is add the “default
retention policy” query parameter to your POST datasets call and set it equal to basicFIFO.

POST https://api.powerbi.com/v1.0/myorg/datasets?defaultRetentionPolicy={None | basicFIFO}

 Power BI REST API limitations
2/6/2019 • 2 minutes to read • Edit Online

To POST Rows
75 max columns
75 max tables
10,000 max rows per single POST rows request
1,000,000 rows added per hour per dataset
5 max pending POST rows requests per dataset
120 POST rows requests per minute per dataset
If table has 250,000 or more rows, 120 POST rows requests per hour per dataset
200,000 max rows stored per table in FIFO dataset
5,000,000 max rows stored per table in ‘none retention policy’ dataset
4,000 characters per value for string column in POST rows operation

See also
Azure AD service limits and restrictions
Overview of Power BI REST API
 Dataset properties
3/29/2019 • 3 minutes to read • Edit Online

The current v1 of datasets API only allows for a dataset to be created with a name and a collection of tables. Each
table can have a name and a collection of columns. Each column has a name and datatype. We are expanding these
properties most notably with support for measures and relationships between tables. The complete list of
supported properties for this release is as follows:

IMPORTANT
It can be accessed at the Datasets Operation Groups page.

Dataset
NAME TYPE DESCRIPTION READ ONLY REQUIRED

id Guid System wide unique True False

identifier for the
dataset.

name String User defined name of False True

the dataset.

tables Table[] Collection of tables. False False

relationships Relationship[] Collection of False False

relationships between
tables.

defaultMode String Determines whether False False

the dataset is pushed,
streamed, or both,
with values of "Push"
and "Streaming."

Table
NAME TYPE DESCRIPTION READ ONLY REQUIRED

name String User defined name of False True

the table. It is also
used as the identifier
of the table.

columns column[] Collection of columns. False True

measures measure[] Collection of False False

measures.
NAME TYPE DESCRIPTION READ ONLY REQUIRED

isHidden Boolean If true, table will be False False

hidden from client
tools.

Column
NAME TYPE DESCRIPTION READ ONLY REQUIRED

name String User defined name of False True

the column.

dataType String Supported EDM data False True

types and restrictions.
See Data type
restrictions.

formatString String A string describing False False

how the value should
be formatted when it
is displayed. To learn
more about string
formatting, see
FORMAT_STRING
Contents.

sortByColumn String String name of a False False

column in the same
table to be used to
order the current
column.

dataCategory String String value to be False False

used for the data
category which
describes the data
within this column.
Some common values
include: Address, City,
Continent, Country,
Image, ImageUrl,
Latitude, Longitude,
Organization, Place,
PostalCode,
StateOrProvince,
WebUrl

isHidden Boolean Property indicating if False False

the column is hidden
from view. Default is
false.
 NAME TYPE DESCRIPTION READ ONLY REQUIRED

summarizeBy String Default aggregation False False

method for the
column. Values
include: default, none,
sum, min, max, count,
average,
distinctCount

Measure
NAME TYPE DESCRIPTION READ ONLY REQUIRED

name String User defined name of False True

the measure.

expression String A valid DAX False True

expression.

formatString String A string describing False False

how the value should
be formatted when it
is displayed. To learn
more about string
formatting, see
FORMAT_STRING
Contents.

isHidden String If true, table will be False False

hidden from client
tools.

Relationship
NAME TYPE DESCRIPTION READ ONLY REQUIRED

name String User defined name of False True

the relationship. It is
also used as the
identifier of the
relationship.

crossFilteringBehavior String The filter direction of False False

the relationship:
OneDirection
(default),
BothDirections,
Automatic

fromTable String Name of the foreign False True

key table.

fromColumn String Name of the foreign False True

key column.
 NAME TYPE DESCRIPTION READ ONLY REQUIRED

toTable String Name of the primary False True

key table.

toColumn String Name of the primary False True

key column.

Data type restrictions (applies to dataType property)

DATA TYPE RESTRICTIONS

Int64 Int64.MaxValue and Int64.MinValue not allowed.

Double Double.MaxValue and Double.MinValue values not allowed.

NaN not supported.+Infinity and -Infinity not supported in
some functions (e.g. Min, Max).

Boolean True or False.

Datetime During data loading we quantize values with day fractions to

whole multiples of 1/300 seconds (3.33ms).

String Currently allows up to 4000 characters per string value.

Decimal precision=28, scale=4

Example
The following code sample includes a number of these properties:

"name": "PushAdvanced",

"tables": [

"name": "Date",

"columns": [

"name": "Date",

"dataType": "dateTime",

"formatString": "dddd\\, mmmm d\\, yyyy",

"summarizeBy": "none"

},
{

"name": "sales",

"columns": [

"name": "Date",

"dataType": "dateTime",

"formatString": "dddd\\, mmmm d\\, yyyy",

"summarizeBy": "none"

},

"name": "Sales",

"dataType": "int64",

"formatString": "0",

"summarizeBy": "sum"

],

"measures": [

"name": "percent to forecast",

"expression": "SUM(sales[Sales])/SUM(forecast[forecast])",

"formatString": "0.00 %;-0.00 %;0.00 %"

},

"name": "forecast",

"columns": [

"name": "date",

"dataType": "dateTime",

"formatString": "m/d/yyyy",

"summarizeBy": "none"

},

"name": "forecast",
 "name": "forecast",

"dataType": "int64",

"formatString": "0",

"summarizeBy": "sum"

],

"relationships": [

"name": "2ea345ce-b147-436e-8ac2-9d3c4d82af8d",

"fromTable": "sales",

"fromColumn": "Date",

"toTable": "Date",

"toColumn": "Date",

"crossFilteringBehavior": "bothDirections"

},

"name": "5d95f419-e589-4345-9581-6e70670b1bba",

"fromTable": "forecast",

"fromColumn": "date",

"toTable": "Date",

"toColumn": "Date",

"crossFilteringBehavior": "bothDirections"

}
 Data Model versioning
2/6/2019 • 2 minutes to read • Edit Online

The Data Model exposed by an OData Service, such as the Power BI data model, defines a contract between the
OData service and its clients. Services are allowed to extend their model only to the degree that it does not break
existing clients. Breaking changes, such as removing properties or changing the type of existing properties, require
that a new service version is provided at a different service root URL for the new model.
The following Data Model additions are considered safe and do not require services to version their entry point.
Adding a property that is nullable or has a default value; if it has the same name as an existing dynamic
property, it must have the same type (or base type) as the existing dynamic property
Adding a navigation property that is nullable or collection-valued; if it has the same name as an existing
dynamic navigation property, it must have the same type (or base type) as the existing dynamic navigation
property
Adding a new entity type to the model
Adding a new complex type to the model
Adding a new entity set
Adding a new singleton
Adding an action, a function, an action import, or function import
Adding an action parameter that is nullable
Adding a type definition or enumeration
Adding any annotation to a model element that does not need to be understood by the client to interact with the
service correctly
Clients SHOULD be prepared for services to make such incremental changes to their model. In particular, clients
should be prepared to receive properties and derived types not previously defined by the service.
Services SHOULD NOT change their data model depending on the authenticated user. If the data model is user or
user group dependent, all changes MUST be safe changes as defined in this section when comparing the full model
to the model visible to users with limited authorizations.
For more about OData Data Model standards, see OData Version 4.0 Part 1: Protocol Plus Errata 02.

See also
Overview of Power BI REST API
 Configure credentials programmatically for Power BI
2/26/2019 • 2 minutes to read • Edit Online

Follow these steps to configure credentials programmatically for Power BI.

Configure a credential flow for data sources

1. Call Get Datasources to discover the data sources of the dataset. In the response body for each data source,
there's the type, connection details, gateway, and data source ID.

var datasources = pbiClient.Datasets.GetDatasources(datasetId).Value;

var datasource = datasources.First(); // select a datasource

2. Build credentials string according to Update Datasource Examples depending on the credentials type.

var credentials = "{\"credentialData\":[{\"name\":\"username\", \"value\":\"john\"},

{\"name\":\"password\", \"value\":\"*****\"}]}";

3. Build the credential details.

var credentialDetails = new CredentialDetails(

credentials,
CredentialTypeEnum.Basic,
EncryptedConnectionEnum.Encrypted,
EncryptionAlgorithmEnum.None,
PrivacyLevelEnum.Private);

4. Call Update Datasource to set credentials, using the gateway and data source ID from step 1 and using the
credential details from step 4.

pbiClient.Gateways.UpdateDatasource(gatewayId, datasourceId, credentialDetails);

Expired on-premises data source credentials flow

1. Follow steps 1 and 2 from the previous scenario.
2. Call Get Gateway to retrieve the gateway public key.

var gateway = pbiClient.Gateways.GetGatewayById(datasource.GatewayId);

3. Encrypt the credentials string with Gateway public key using the RSA encryption algorithm.
Use the following helper class for encryption:

public static class AsymmetricKeyEncryptionHelper

{
private const int SegmentLength = 85;
private const int EncryptedLength = 128;

/// <summary>

/// Encrypts credentials using the RSA algorithm

 /// Encrypts credentials using the RSA algorithm

/// </summary>

public static string EncodeCredentials(string credentialData, string publicKeyExponent, string

publicKeyModulus)
{
using (RSACryptoServiceProvider rsa = new RSACryptoServiceProvider(EncryptedLength * 8))
{
var parameters = rsa.ExportParameters(false);

parameters.Exponent = Convert.FromBase64String(publicKeyExponent);

parameters.Modulus = Convert.FromBase64String(publicKeyModulus);

rsa.ImportParameters(parameters);

return Encrypt(credentialData, rsa);

}
}

private static string Encrypt(string plainText, RSACryptoServiceProvider rsa)

{

byte[] plainTextArray = Encoding.UTF8.GetBytes(plainText);

// Split the message into different segments, each segment's length is 85. So, the result
may be 85,85,85,20.

bool hasIncompleteSegment = plainTextArray.Length % SegmentLength != 0;

int segmentNumber = (!hasIncompleteSegment) ? (plainTextArray.Length / SegmentLength) :

((plainTextArray.Length SegmentLength) + 1);

byte[] encryptedData = new byte[segmentNumber * EncryptedLength];

int encryptedDataPosition = 0;

for (var i = 0; i < segmentNumber; i++)

{
int lengthToCopy;

if (i == segmentNumber - 1 && hasIncompleteSegment)

lengthToCopy = plainTextArray.Length % SegmentLength;

else

lengthToCopy = SegmentLength;

var segment = new byte[lengthToCopy];

Array.Copy(plainTextArray, i * SegmentLength, segment, 0, lengthToCopy);

var segmentEncryptedResult = rsa.Encrypt(segment, true);

Array.Copy(segmentEncryptedResult, 0, encryptedData, encryptedDataPosition,

segmentEncryptedResult.Length);

encryptedDataPosition += segmentEncryptedResult.Length;

return Convert.ToBase64String(encryptedData);

var encryptedCredentials = AsymmetricKeyEncryptionHelper.EncodeCredentials(credentials);

 var encryptedCredentials = AsymmetricKeyEncryptionHelper.EncodeCredentials(credentials);

4. Build credentials details with encrypted credentials.

var credentialDetails = new CredentialDetails(

encryptedCredentials,
CredentialTypeEnum.Basic,
EncryptedConnectionEnum.Encrypted,
EncryptionAlgorithmEnum.RSA-OAEP,
PrivacyLevelEnum.Private);

5. Call Update Datasource to set credentials.

pbiClient.Gateways.UpdateDatasource(gatewayId, datasourceId, credentialDetails);

Configure a new data source for a data gateway

1. Install the On-premises data gateway on your machine.
2. Call Get Gateways to retrieve the gateway ID and public key.

var gateways = pbiClient.Gateways.GetGateways().Value;

var gateway = gateways.First(); // select a gateway

3. Build credential details like in the previous scenario using the gateway public key retrieved in step [expired
on-prem data source credentials flow ](#expired-on-premises-data source-credentials-flow -on-premises-
data-gateway).
4. build the request body

var request = new PublishDatasourceToGatewayRequest(

dataSourceType: "SQL",
connectionDetails: "{\"server\":\"myServer\",\"database\":\"myDatabase\"}",
credentialDetails: credentialDetails,
dataSourceName: "my sql datasource");

5. Call the Create Datasource API.

pbiClient.Gateways.CreateDatasource(gateway.Id, request);

Troubleshooting
No gateway and data source ID found when calling get data sources
This issue means the dataset isn't bound to a gateway. When creating a new dataset, for each cloud connection a
data source with no credentials is created automatically on the cloud gateway of the user. This gateway is used to
store the credentials for cloud connections.
After you create the dataset, an automatic binding is done between the dataset and a suitable gateway, which
contains matching data sources for all connections. If there's no such gateway or multiple suitable gateways, the
automatic binding fails.
Create missing on-premises data sources if any, and bind the dataset to a gateway manually by using Bind To
Gateway.
To discover gateways that could be bound use Discover Gateways.
 Encrypt credentials
2/26/2019 • 2 minutes to read • Edit Online

When you call Create Datasource or Update Datasource under an enterprise on-prem gateway using Power BI
Rest API, the credentials value needs to be encrypted using the gateway's public key.
See code example below how to encrypt the credentials in .NET.
Credentials provided to EncodeCredentials method below should be in one of the following formats depending on
the credentials type:
Basic / Windows credentials

var credentials = "{\"credentialData\":[{\"name\":\"username\", \"value\":\"john\"},{\"name\":\"password\",

\"value\":\"*****\"}]}";

Key credentials

var credentials = "{\"credentialData\":[{\"name\":\"key\", \"value\":\"ec....LA=\"}]}";

OAuth2 credentials

var credentials = "{\"credentialData\":[{\"name\":\"accessToken\", \"value\":\"eyJ0....fwtQ\"}]}";

Anonymous credentials

var credentials = "{\"credentialData\":\"\"}";

Encrypt credentials
public static class AsymmetricKeyEncryptionHelper
{

private const int SegmentLength = 85;

private const int EncryptedLength = 128;

public static string EncodeCredentials(string credentials, string publicKeyExponent, string

publicKeyModulus)
{
using (RSACryptoServiceProvider rsa = new RSACryptoServiceProvider(EncryptedLength * 8))
{
var parameters = rsa.ExportParameters(false);
parameters.Exponent = Convert.FromBase64String(publicKeyExponent);
parameters.Modulus = Convert.FromBase64String(publicKeyModulus);
rsa.ImportParameters(parameters);
return Encrypt(credentials, rsa);
}
}

private static string Encrypt(string plainText, RSACryptoServiceProvider rsa)

{
byte[] plainTextArray = Encoding.UTF8.GetBytes(plainText);

// Split the message into different segments, each segment's length is 85. So the result may be
85,85,85,20.
bool hasIncompleteSegment = plainTextArray.Length % SegmentLength != 0;

int segmentNumber = (!hasIncompleteSegment) ? (plainTextArray.Length / SegmentLength) :

((plainTextArray.Length / SegmentLength) + 1);

byte[] encryptedData = new byte[segmentNumber * EncryptedLength];

int encryptedDataPosition = 0;

for (var i = 0; i < segmentNumber; i++)

{
int lengthToCopy;

if (i == segmentNumber - 1 && hasIncompleteSegment)

lengthToCopy = plainTextArray.Length % SegmentLength;
else
lengthToCopy = SegmentLength;

var segment = new byte[lengthToCopy];

Array.Copy(plainTextArray, i * SegmentLength, segment, 0, lengthToCopy);

var segmentEncryptedResult = rsa.Encrypt(segment, true);

Array.Copy(segmentEncryptedResult, 0, encryptedData, encryptedDataPosition,

segmentEncryptedResult.Length);

encryptedDataPosition += segmentEncryptedResult.Length;
}

return Convert.ToBase64String(encryptedData);
}
}
 Power BI REST API Reference
1/14/2019 • 2 minutes to read • Edit Online

Power BI is a cloud-based service that you can use to build custom dashboard applications. The Power BI REST
API is a REST-based API that provides programmatic access to Dashboard resources such as Datasets, Tables,
and Rows in Power BI.

NOTE
If you’re interested in viewing or deleting personal data, please review Microsoft's guidance in the Windows Data Subject
Requests for the GDPR site. If you’re looking for general information about GDPR, see the GDPR section of the Service Trust
portal.

The Power BI REST API has the following operations:

Dataset operations: Get and create Datasets.
Table operations: Get Tables and update Table schema.
Row operations: Add Rows and Delete Rows.
Group operations: Get Groups.
To learn more about the Power BI REST API, see Power BI REST API.
More questions? Try asking the Power BI Community
 Push data to a dataset complete code listing
2/6/2019 • 3 minutes to read • Edit Online

This article is part of a step-by-step walkthrough to push data into a dataset.

After you follow Steps 2 to 5 in Push data into a dataset, your complete source code should look like the
following.

Push data to dataset code

using System;
using Microsoft.IdentityModel.Clients.ActiveDirectory;
using System.Net;
using System.IO;
using Newtonsoft.Json;

namespace walkthrough_push_data
{
class Program
{
private static string token = string.Empty;

static void Main(string[] args)

{

//Get an authentication access token

token = GetToken();

//Create a dataset in Power BI

CreateDataset();

//Get a dataset to add rows into a Power BI table

string datasetId = GetDataset();

//Add rows to a Power BI table

AddRows(datasetId, "Product");

#region Get an authentication access token

private static string GetToken()
{
// TODO: Install-Package Microsoft.IdentityModel.Clients.ActiveDirectory -Version 2.21.301221612
// and add using Microsoft.IdentityModel.Clients.ActiveDirectory

//The client id that Azure AD created when you registered your client app.
string clientID = "{Client_ID}";

//RedirectUri you used when you register your app.

//For a client app, a redirect uri gives Azure AD more details on the application that it will
authenticate.
// You can use this redirect uri for your client app
string redirectUri = "https://login.live.com/oauth20_desktop.srf";

//Resource Uri for Power BI API

string resourceUri = "https://analysis.windows.net/powerbi/api";

//OAuth2 authority Uri

string authorityUri = "https://login.microsoftonline.net/common/";

//Get access token:

 //Get access token:
// To call a Power BI REST operation, create an instance of AuthenticationContext and call
AcquireToken
// AuthenticationContext is part of the Active Directory Authentication Library NuGet package
// To install the Active Directory Authentication Library NuGet package in Visual Studio,
// run "Install-Package Microsoft.IdentityModel.Clients.ActiveDirectory" from the nuget Package
Manager Console.

// AcquireToken will acquire an Azure access token

// Call AcquireToken to get an Azure token from Azure Active Directory token issuance endpoint
AuthenticationContext authContext = new AuthenticationContext(authorityUri);
string token = authContext.AcquireToken(resourceUri, clientID, new Uri(redirectUri)).AccessToken;

Console.WriteLine(token);
Console.ReadLine();

return token;
}

#endregion

#region Create a dataset in Power BI

private static void CreateDataset()
{
//TODO: Add using System.Net and using System.IO

string powerBIDatasetsApiUrl = "https://api.powerbi.com/v1.0/myorg/datasets";

//POST web request to create a dataset.
//To create a Dataset in a group, use the Groups uri:
https://api.PowerBI.com/v1.0/myorg/groups/{group_id}/datasets
HttpWebRequest request = System.Net.WebRequest.Create(powerBIDatasetsApiUrl) as
System.Net.HttpWebRequest;
request.KeepAlive = true;
request.Method = "POST";
request.ContentLength = 0;
request.ContentType = "application/json";

//Add token to the request header

request.Headers.Add("Authorization", String.Format("Bearer {0}", token));

//Create dataset JSON for POST request

string datasetJson = "{\"name\": \"SalesMarketing\", \"tables\": " +
"[{\"name\": \"Product\", \"columns\": " +
"[{ \"name\": \"ProductID\", \"dataType\": \"Int64\"}, " +
"{ \"name\": \"Name\", \"dataType\": \"string\"}, " +
"{ \"name\": \"Category\", \"dataType\": \"string\"}," +
"{ \"name\": \"IsCompete\", \"dataType\": \"bool\"}," +
"{ \"name\": \"ManufacturedOn\", \"dataType\": \"DateTime\"}" +
"]}]}";

//POST web request

byte[] byteArray = System.Text.Encoding.UTF8.GetBytes(datasetJson);
request.ContentLength = byteArray.Length;

//Write JSON byte[] into a Stream

using (Stream writer = request.GetRequestStream())
{
writer.Write(byteArray, 0, byteArray.Length);

var response = (HttpWebResponse)request.GetResponse();

Console.WriteLine(string.Format("Dataset {0}", response.StatusCode.ToString()));

Console.ReadLine();
}
}
#endregion

#region Get a dataset to add rows into a Power BI table

private static string GetDataset()
 private static string GetDataset()
{
string powerBIDatasetsApiUrl = "https://api.powerbi.com/v1.0/myorg/datasets";
//POST web request to create a dataset.
//To create a Dataset in a group, use the Groups uri:
https://api.PowerBI.com/v1.0/myorg/groups/{group_id}/datasets
HttpWebRequest request = System.Net.WebRequest.Create(powerBIDatasetsApiUrl) as
System.Net.HttpWebRequest;
request.KeepAlive = true;
request.Method = "GET";
request.ContentLength = 0;
request.ContentType = "application/json";

//Add token to the request header

request.Headers.Add("Authorization", String.Format("Bearer {0}", token));

string datasetId = string.Empty;

//Get HttpWebResponse from GET request
using (HttpWebResponse httpResponse = request.GetResponse() as System.Net.HttpWebResponse)
{
//Get StreamReader that holds the response stream
using (StreamReader reader = new System.IO.StreamReader(httpResponse.GetResponseStream()))
{
string responseContent = reader.ReadToEnd();

//TODO: Install NuGet Newtonsoft.Json package: Install-Package Newtonsoft.Json

//and add using Newtonsoft.Json
var results = JsonConvert.DeserializeObject<dynamic>(responseContent);

//Get the first id

datasetId = results["value"][0]["id"];

Console.WriteLine(String.Format("Dataset ID: {0}", datasetId));

Console.ReadLine();

return datasetId;
}
}
}
#endregion

#region Add rows to a Power BI table

private static void AddRows(string datasetId, string tableName)
{
string powerBIApiAddRowsUrl =
String.Format("https://api.powerbi.com/v1.0/myorg/datasets/{0}/tables/{1}/rows", datasetId, tableName);

//POST web request to add rows.

//To add rows to a dataset in a group, use the Groups uri:
https://api.powerbi.com/v1.0/myorg/groups/{group_id}/datasets/{dataset_id}/tables/{table_name}/rows
//Change request method to "POST"
HttpWebRequest request = System.Net.WebRequest.Create(powerBIApiAddRowsUrl) as
System.Net.HttpWebRequest;
request.KeepAlive = true;
request.Method = "POST";
request.ContentLength = 0;
request.ContentType = "application/json";

//Add token to the request header

request.Headers.Add("Authorization", String.Format("Bearer {0}", token));

//JSON content for product row

string rowsJson = "{\"rows\":" +
"[{\"ProductID\":1,\"Name\":\"Adjustable
Race\",\"Category\":\"Components\",\"IsCompete\":true,\"ManufacturedOn\":\"07/30/2014\"}," +
"{\"ProductID\":2,\"Name\":\"LL
Crankarm\",\"Category\":\"Components\",\"IsCompete\":true,\"ManufacturedOn\":\"07/30/2014\"}," +
"{\"ProductID\":3,\"Name\":\"HL Mountain Frame -
Silver\",\"Category\":\"Bikes\",\"IsCompete\":true,\"ManufacturedOn\":\"07/30/2014\"}]}";
 //POST web request
byte[] byteArray = System.Text.Encoding.UTF8.GetBytes(rowsJson);
request.ContentLength = byteArray.Length;

//Write JSON byte[] into a Stream

using (Stream writer = request.GetRequestStream())
{
writer.Write(byteArray, 0, byteArray.Length);

var response = (HttpWebResponse)request.GetResponse();

Console.WriteLine("Rows Added");

Console.ReadLine();
}
}

#endregion
}
}

Next steps
Push data into a Power BI dataset
Walkthrough - Push data into a Power BI dataset
Register an app with Azure AD
Get an authentication access token
Create a dataset in Power BI
Get a dataset to add rows into a Power BI table
Add rows to a Power BI table
Power BI REST API reference
Overview of Power BI REST API
More questions? Try the Power BI Community
 What is Power BI Report Server?
2/15/2019 • 3 minutes to read • Edit Online

Power BI Report Server is an on-premises report server with a web portal in which you display and manage
reports and KPIs. Along with it come the tools to create Power BI reports, paginated reports, mobile reports, and
KPIs. Your users can access those reports in different ways: viewing them in a web browser or mobile device, or
as an email in their in-box.

Comparing Power BI Report Server

Power BI Report Server is similar to both SQL Server Reporting Services and the Power BI online service, but in
different ways. Like the Power BI service, Power BI Report Server hosts Power BI reports (.PBIX) and Excel files.
Like Reporting Services, Power BI Report Server is on premises, and hosts paginated reports (.RDL ). Power BI
Report Server is a superset of Reporting Services: everything you can do in Reporting Services, you can do with
Power BI Report Server, along with support for Power BI reports. See Comparing Power BI Report Server and
the Power BI service for details.

Licensing Power BI Report Server

Power BI Report Server is available through two different licenses: Power BI Premium and SQL Server
Enterprise Edition with Software Assurance. With a Power BI Premium license, you can create a hybrid
deployment mixing cloud and on-premises.

NOTE
For Power BI Premium, Power BI Report Server is only included with P SKUs. It is not included with EM SKUs.

Web portal
The entry point for Power BI Report Server is a secure web portal you can view in any modern browser. Here,
you access all your reports and KPIs. The content on the web portal is organized in a traditional folder hierarchy.
In your folders, content is grouped by type: Power BI reports, mobile reports, paginated reports, KPIs, and Excel
workbooks. Shared datasets and shared data sources are in their own folders, to use as building blocks for your
reports. You tag favorites to view them in a single folder. And you create KPIs right in the web portal.

Depending on your permissions, you can manage the content in the web portal. You can schedule report
processing, access reports on demand, and subscribe to published reports. You can also apply your own custom
branding to your web portal.
More about the Power BI Report Server web portal.

Power BI reports
You create Power BI reports (.PBIX) with the version of Power BI Desktop optimized for the report server. Then
you publish them to and view them in the web portal in your own environment.
A Power BI report is a multi-perspective view into a data model, with visualizations that represent different
findings and insights from that data model. A report can have a single visualization or pages full of
visualizations. Depending on your role, you may read and explore reports, or you may create them for others.
Install Power BI Desktop optimized for Power BI Report Server.

Paginated reports
Paginated reports (.RDL ) are document-style reports with visualizations, in which tables expand horizontally and
vertically to display all their data, continuing from page to page as needed. They're great for generating fixed-
layout, pixel-perfect documents optimized for printing, such as PDF and Word files.

You can create modern-looking reports using Report Builder or Report Designer in SQL Server Data Tools
(SSDT).

Reporting Services mobile reports

Mobile reports connect to on-premises data and have a responsive layout that adapts to different devices and
the different ways you hold them. You create them with SQL Server Mobile Report Publisher.
More about Reporting Services mobile reports.

Report Server programming features

Take advantage of Power BI Report Server programming features to extend and customize your reports, with
APIs to integrate or extend data and report processing in custom applications.
More Report Server developer documentation.

Next steps
Install Power BI Report Server
Download Report Builder
More questions? Try asking the Power BI Community
 Comparing Power BI Report Server and the Power BI
service
3/4/2019 • 2 minutes to read • Edit Online

Power BI Report Server and the Power BI service have many similarities and some key differences. This table
explains which is which.

Features of Power BI Report Server and the Power BI service

FEATURES POWER BI REPORT SERVER POWER BI SERVICE NOTES

Deployment On-premises or hosted Cloud Power BI Report Server can

cloud be deployed in Azure VMs
(hosted cloud) if licensed
through Power BI Premium

Source data Cloud and/or on-premises Cloud and/or on-premises

License Power BI Premium or SQL Power BI Pro and/or Power

Server EE with SA BI Premium

Lifecycle Modern lifecycle policy Fully managed service

Release cycle Once every 4 months Once a month Latest features and fixes
come to Power BI Service
first. Most core functionality
comes to Power BI Report
Server in the next few
releases; some features only
meant for the Power BI
service.

Create Power BI reports in Yes Yes

Power BI Desktop

Create Power BI reports in No Yes

the browser

Gateway required No Yes for on-premises data

sources

Real-time streaming No Yes Real-time streaming in

Power BI

Dashboards No Yes Dashboards in the Power BI

service

Distribute group of reports No Yes Create and publish apps

using apps with dashboards and reports
FEATURES POWER BI REPORT SERVER POWER BI SERVICE NOTES

Content packs No Yes Organizational content

packs: Introduction

Connect to services like Yes Yes Connect to the services you

Salesforce use with content packs in
the Power BI service. In
Power BI Report Server, use
certified connectors to
connect to services. See
Power BI report data
sources in Power BI Report
Server for details.

Q&A No Yes Q&A in the Power BI service

and Power BI Desktop

Quick insights No Yes Automatically generate data

insights with Power BI

Analyze in Excel No Yes Analyze in Excel

Paginated reports Yes Yes Paginated reports are

available in the Power BI
service in preview in a
Premium capacity

Power BI mobile apps Yes Yes Power BI mobile apps

overview

ARC GIS maps No Yes ArcGIS maps in Power BI

service and Power BI
Desktop by Esri

Email subscriptions for No Yes Subscribe yourself or others

Power BI reports to a report or dashboard in
the Power BI service

Email subscriptions for Yes No E-Mail delivery in Reporting

paginated reports Services

Data alerts No Yes Data alerts in the Power BI

service

Row-level security (RLS) Yes Yes Available in both

DirectQuery (data source) &
Import mode
Row-level security in the
Power BI service
Row-level security in Power
BI Report Server

Full-screen mode No Yes Full-screen mode in the

Power BI service
 FEATURES POWER BI REPORT SERVER POWER BI SERVICE NOTES

Advanced Office 365 No Yes Collaborate in an app

collaboration workspace with Office 365

R visuals No Yes Create R visuals in Power BI

Desktop and publish them
to the Power BI service. You
can't save Power BI reports
with R visuals to Power BI
Report Server.

Preview features No Yes Opt in for Power BI service

preview features

Custom visuals Yes Yes Custom visuals in Power BI

Power BI Desktop Version optimized for Report Version optimized for Power Power BI Desktop for the
Server, available for BI Service, available from the report server
download with Report Server Windows Store
Power BI Desktop for the
Power BI service

Next steps
Install Power BI Report Server
 Tutorial: Explore the Power BI Report Server web
portal in a VM
2/15/2019 • 5 minutes to read • Edit Online

In this tutorial, you create an Azure virtual machine with Power BI Report Server already installed, so you can
experience viewing, editing, and managing sample Power BI and paginated reports, and KPIs.

Here are the tasks you'll do in this tutorial:

Create and connect to a VM
Start and explore the Power BI Report Server web portal
Tag a favorite item
View and edit a Power BI report
View, manage, and edit a paginated report
View an Excel workbook in Excel Online
For this tutorial, you need an Azure subscription. If you don’t have one, create a free account before you begin.

Create a Power BI Report Server VM

Luckily, the Power BI team has created a VM that comes with Power BI Report Server already installed.
1. In the Azure Marketplace, open Power BI Report Server.
2. Select Get it now.
3. To agree to the provider's terms of use and privacy policy, select Continue.
4. Step 1 Basics, for VM Name, call it reportservervm.
5. Create a user name and password.
6. For Resource group, keep Create new, and call it reportserverresourcegroup.
If you go through the tutorial more than once, you need to give the resource group a different name after
the first time. You can't use the same resource group name twice in one subscription.
7. Keep the other defaults > OK.
 8. Step 2 Settings, keep the defaults > OK.
9. Step 3 Summary > OK.
10. Step 4, review the Terms of user and privacy policy > Create.
The Submitting deployment for Power BI Report Server process takes a several minutes.

Connect to your virtual machine

1. In the Azure left navigation pane, select Virtual machines.
2. In the Filter by name box, type "report".
3. Select the VM named REPORTSERVERVM.
4. Under REPORTSERVERVM Virtual machine, select Connect.

5. In the Remote Desktop Connection dialog box, select Connect.

6. Enter the name and password you created for the VM > OK.
7. The next dialog box says the identity of the remote computer cannot be identified. Select Yes.
Voila, your new VM opens.

Power BI Report Server on the VM

When your VM opens, here are the items you see on the desktop.
 NUMBER WHAT IT IS

Starts SQL Server Data Tools, for creating paginated (.RDL)

reports

Sample Power BI (.PBIX) reports

Links to Power BI Report Server documentation

Starts Power BI Desktop optimized for Power BI Report Server

(March 2018)

Opens Power BI Report Server web portal in the browser

Double-click the Report Server Web Portal icon. The browser opens http://localhost/reports/browse . In the web
portal, you see various files grouped by type.
 NUMBER WHAT IT IS

KPIs created in the web portal

Power BI (.PBIX) reports

Mobile reports created in SQL Server Mobile Report Publisher

Paginated reports created in Report Builder or SQL Server

Data Tools

Excel workbooks

Data sources for paginated reports

Tag your favorites

You can tag the reports and KPIs that you want to be favorites. They're easier to find because they're all gathered in
a single Favorites folder, both in the web portal and in the Power BI mobile apps.
1. Select the ellipsis (… ) in the upper-right corner of the Profit Margin KPI > Add to Favorites.
2. Select Favorites on the web portal ribbon to see it along with your other favorites on the Favorites page in
the web portal.

3. Select Browse to go back to the web portal.

View items in List view

By default, the web portal displays its contents in Tile view.
You can switch to List view, where it's easy to move or delete multiple items at a time.
1. Select Tiles > List.

2. Go back to Tiles view: Select List > Tiles.

Power BI reports
You can view and interact with Power BI reports in the web portal, and start Power BI Desktop right from the web
portal.
View Power BI reports
1. In the web portal under Power BI reports, select Sample Customer Overview Report. The report opens
in the browser.
2. Select the United States block in the tree map to see how it highlights related values in the other visuals.
Edit in Power BI Desktop
1. Select Edit in Power BI Desktop.
2. Select Allow to allow this web site to open a program on your computer.
The report opens in Power BI Desktop. Note the name in the top bar, "Power BI Desktop (March 2018)".
That's the version optimized for Power BI Report Server.

Use the version of Power BI Desktop that's installed on the VM. You can't go across domains to upload a
report.
3. In the Fields pane, expand the Customers table and drag the Occupation field to Report level filters.
4. Save the report.
5. Go back to the report in the browser and select the browser Refresh icon.

6. Expand the Filters pane on the right to see the Occupation filter you added. Select Professional.
7. Select Browse to go back to the web portal.

Paginated (.RDL) reports

You can view and manage paginated reports, and launch Report Builder, from the web portal.
Manage a paginated report
1. In the web portal under Paginated reports, select the ellipsis (...) next to Sales Order > Manage.
2. Select Parameters, change the default value for SalesOrderNumber to SO50689 > Apply.

3. Select Browse to go back to the web portal.

View a paginated report
1. Select Sales Order in the web portal.
2. You see it opened to the Order parameter you set, SO50689.
 You can change that parameter here, along with the other parameters, without changing the defaults.
3. Select Order SO48339 > View Report.
4. You see that this is page 1 of 2. Select the right arrow to see the second page. The table continues on that
page.
5. Select Browse to go back to the web portal.
Edit a paginated report
You can edit paginated reports in Report Builder, and you can start Report Builder right from the browser.
1. In the web portal, select the ellipsis (...) next to Sales Order > Edit in Report Builder.
2. Select Allow to allow this web site to open a program on your computer.
3. The Sales Order report opens in Design View in Report Builder.

4. Select Run to preview the report.

5. Close Report Builder and go back to the browser.

View Excel workbooks

You can view and interact with Excel workbooks in Excel Online in Power BI Report Server.
1. Select the Excel workbook Office Liquidation Sale.xlsx. It may ask for credentials. Select Cancel. It opens
in the web portal.
2. Select Appliance in the slicer.

3. Select Browse to go back to the web portal.

Clean up resources
Now that you've finished this tutorial, delete the resource group, virtual machine, and all related resources.
To do so, select the resource group for the VM and select Delete.

Next steps
In this tutorial, you've created a VM with Power BI Report Server. You've tried some of the functionality of the web
portal, and you've opened a Power BI report and a paginated report in their respective editors. This VM has SQL
Server Analysis Services data sources installed, so you can try creating your own Power BI and paginated reports
with those same data sources.
To learn more about creating reports for Power BI Report Server, continue on.
Create a Power BI report for Power BI Report Server
 What's new in Power BI Report Server
2/21/2019 • 12 minutes to read • Edit Online

Learn about what's new in Power BI Report Server. This article covers the major feature areas and is updated as
new items are released.
To download the latest versions of Power BI Report Server and Power BI Desktop optimized for Power BI Report
Server, go to On-premises reporting with Power BI Report Server.
For related Power BI "What's New" information, see:
What's new in the Power BI service
What's new in Power BI Desktop
What's new in the mobile apps for Power BI

January 2019
Support for these features in Power BI reports:
Row-level security Setting up row -level security (RLS ) with Power BI Report Server can restrict data access for
given users. Filters restrict data access at the row level, and you can define filters within roles.
Expand and collapse on matrix row headers We've added the ability to expand and collapse individual row
headers, one of the most requested visual features.
Copy and paste between .pbix files You can copy visuals between .pbix files, either from the visual’s context
menu or with the standard Ctrl+C keyboard shortcut, and paste it into another report with Ctrl+V.
Smart alignment guides You see smart alignment guides when moving objects on your report page, like you see
in PowerPoint, to help you align everything on your page. You see the smart guides any time you drag or resize
something on your page. When you move an object near another one, it snaps into a position aligned with the
other object.
Accessibility features Too many accessibility features to list: for example, fields list pane accessibility support. The
fields list pane is fully accessible. You can navigate around the pane using just your keyboard and a screen reader
and use the context menu to add fields to your report page.
Custom Visuals
The API version shipped with this release is 2.3.
Administrator settings
Administrators can set the following properties in SSMS Advanced Properties for the server farm:
AllowedResourceExtensionsForUpload Set extensions of resources that can be uploaded to the report server.
Extensions for built-in file types like *.rdl and *.pbix are not required to be included. Default is “*, *.xml, *.xsd, *.xsl,
*.png, *.gif, *.jpg, *.tif, *.jpeg, *.tiff, *.bmp, *.pdf, *.svg, *.rtf, *.txt, *.doc, *.docx, *.pps, *.ppt, *.pptx”.
SupportedHyperlinkSchemes Sets a comma-separated list of the URI schemes allowed to be defined on
Hyperlink actions that are allowed to be rendered or “*” to enable all hyperlink schemes. For example, setting
“http,https” would allow hyperlinks to “https://www. contoso.com”, but would remove hyperlinks to
“mailto:[email protected]” or “javascript:window.open(‘www.contoso.com’, ‘_blank’)”. Default is “*”.

August 2018
August 2018 sees many new features added to the version of Power BI Desktop optimized for Power BI Report
Server. Here they are, broken out by area:
Reporting
Analytics
Modeling
Highlights of the August 2018 release
Out of the whole long list of new features, these features stand out as especially interesting. For more information,
see our blog post.
Report theming
Report theming has been added to the August 2018 release of Power BI Report Server, which allows you to
quickly color your entire report to match a theme or corporate branding. When you import a theme, all your charts
automatically update to use the theme colors, and you can have access to the theme colors from the color palette.
You can upload a theme file using the Import Theme option under the Switch Theme button.
A theme file is a JSON file that includes all the colors you want us to use in your report along with any default
formatting you want to apply to visuals. Here is a simple sample JSON theme that just updates the default colors
of the report:

{
"name": "waveform",
"dataColors": [ "#31B6FD", "#4584D3", "#5BD078", "#A5D028", "#F5C040", "#05E0DB", "#3153FD", "#4C45D3",
"#5BD0B0", "#54D028", "#D0F540", "#057BE0" ],
"background":"#FFFFFF",
"foreground": "#F2F2F2",
"tableAccent":"#5BD078"
}

Conditional formatting by a different field

The ability to format a column by a different field in your model is one of the significant improvements to
conditional formatting.
Conditional formatting by values
Another new conditional formatting type is the Format by field value. The Format by field value lets you use a
measure or column that specifies a color, either through a hex code or name, and applies that color to the
background or font color.
Report page tooltips
The report page tooltips feature is included in the August 2018 update of Power BI Report Server. This feature lets
you design a report page to be used as a custom tooltip for other visuals in your report.
Log axis improvements
We’ve greatly improved log axis in your cartesian charts. You should now be able to select log scale for the
numeric axis of any cartesian chart, including combo chart, when you have data that is completely positive or
completely negative.
SAP HANA SSO Direct Query
SAP HANA SSO Direct Query support with Kerberos is now available for Power BI Reports.

NOTE
This scenario is supported only when SAP HANA is treated as a relational data source with reports you’ve created in Power BI
desktop. To enable this in Power BI Desktop, in the DirectQuery menu under Options, check the “Treat SAP HANA as a
relational source” and click OK.
Custom Visuals
The API version shipped with this release is 1.13.0.
Now custom visuals can fall back to a previous version compatible with the current version of the server
API (if available).
Reporting
Report Theming
Buttons to trigger actions
Combo chart line styles
Improved default sort for visuals
Numeric slicer
Advanced slicer syncing
Log axis improvements
Data label options for funnel chart
Set line stroke width to zero
High contrast support for reports
Donut radius control
Pie and donut detail labels position control
Format data labels separately for each measure in a combo chart
New visual header with more flexibility and formatting
Wallpaper formatting
Tooltips for table & matrix
Turn tooltips off for visuals
Slicer accessibility
Formatting pane improvements
Stepped line support for line and combo charts
Sorting experience improvement
Print reports through Export to PDF (in Power BI Desktop)
Create bookmark groups
Slicer restatement
Report page tooltips
Analytics
New DAX function: COMBINEVALUES ()
Measure drillthrough
Conditional formatting by a different field
Conditional formatting by values
Modeling
Filtering and sorting in data view
Improved locale formatting
Data categories for measures
Statistical DAX functions

May 2018
Configure Power BI iOS mobile apps for report servers remotely
As an IT admin, you can now use your organization's MDM tool to remotely configure Power BI iOS mobile app
access to a report server. See Configure Power BI iOS mobile app access to a report server remotely for details.

March 2018
March 2018 sees many, many new features added to the version of Power BI Desktop optimized for Power BI
Report Server. Here they are, broken out by area:
Visuals
Reporting
Analytics
Performance
Report server
Others
Highlights of the March 2018 release
Out of the whole long list of new features, these features stand out as especially interesting.
Rule-based conditional formatting for table and matrix
Create rules to conditionally color the background or font color of a column based on specific business logic in
your table or matrix.
Show and hide pages
You want readers to have access to your report, but some of the pages aren't quite finished. Now you can hide
them until they're ready. Or you can hide pages from normal navigation, and readers can get to the page by
bookmarks or drillthrough.
Bookmarking
Speaking of bookmarking, create bookmarks to tell a story with the data in your report.
Cross-highlighting for bookmarks: Bookmarks maintain and display the cross-highlighted state of the report
page at the time you created the bookmark.
More bookmark flexibility: Bookmarks reflect the properties you set in your report, and affect only the visuals
you choose.
Multi-select data points across multiple charts
Select multiple data points in multiple charts and have the cross-filtering apply to the entire page.
Sync slicers across multiple pages of your report
A slicer can apply to one, two, or more pages in a report.
Quick measures
Create new measures based on existing measures and numerical columns in a table.
Drilling down filters other visuals
When you drill down in a given category in one visual, you can have it filter all the visuals on the page by that
same category.
Visuals updates
Cell alignment for table and matrix
Display units and precision control for table & matrix columns
Overflow data labels for bar and column charts
Control data label background color for Cartesian and maps visuals
Bar/column padding control
Increase area used for axis labels in charts
Scatter visual from x- & y-axis groupings
High density sampling for maps based on latitude and longitude
 Responsive slicers
Add an anchor date for relative date slicer
Reporting
Turn off the visual header in reading mode for a report
Report options for slow data sources
Improved default visual placement
Control visual ordering through the selection pane
Lock objects on your report
Search the formatting and analytics pane
Field properties pane and field descriptions
Analytics
UTCNOW () and UTCTODAY ()
Mark custom date table
Drill filters other visuals
Cell-level formatting for multidimensional AS models for multi-row card
Performance
Filtering performance improvements
DirectQuery performance improvements
Open and save performance improvements
“Show items with no data” improvements
Report server
Export to accessible PDF
When you export a paginated (RDL ) report to PDF, you can now get an accessible/tagged PDF file. It's larger in
size but easier for screen readers and other assistive technologies to read and navigate. You enable accessible PDF
by setting the AccessiblePDF device information setting to True. See PDF Device Information Settings and
Changing Device Information Settings.
Other improvements
Add Column From Examples improvements
Consulting Services quick link
Improved error reporting
View previous errors you’ve encountered

October 2017
Power BI report data sources
Power BI reports in Power BI Report Server can connect to a variety of data sources. You can import data and
schedule data refresh, or query it directly using DirectQuery or a live connection to SQL Server Analysis Services.
See the list of data sources that support scheduled refresh and those that support DirectQuery in "Power BI report
data sources in Power BI Report Server".
Scheduled data refresh for imported data
In Power BI Report Server, you can set up scheduled data refresh to keep data up-to-date in Power BI reports with
an embedded model rather than a live connection or DirectQuery. With an embedded model you import the data,
so it's disconnected from the original data source. It needs to be updated to keep the data fresh, and scheduled
refresh is the way to do that. Read more about "scheduled refresh for Power BI reports in Power BI Report Server".
Editing Power BI reports from the server
You can open and edit Power BI report (.pbix) files from the server, but you get back the original file you uploaded.
This means if the data has been refreshed by the server, the data won’t be refreshed when you first open
the file. You need to manually refresh it locally to see the change.
Large file upload/download
You can upload files up to 2 GB in size, though by default this limit is set to 1 GB in the Report Server settings in
SQL Server Management Studio (SSMS ). These files are stored in the database just as they are for SharePoint,
and no special configuration for the SQL Server catalog is required.
Accessing shared datasets as OData feeds
You can access shared datasets from Power BI Desktop with an OData feed. For more information, see Accessing
shared datasets as OData feeds in Power BI Report Server.
Scale -out
This release supports scale-out. Use a load-balancer and set server affinity for the best experience. Note that the
scenario is not yet optimized for scale-out, so you'll see models potentially replicated across multiple nodes. The
scenario will work without the Network Load Balancer and sticky sessions. However, you'll not only see an over-
use of memory across nodes as the model is loaded N times, but performance will slow in between connections as
the model is streamed as it hits a new node in between requests.
Administrator settings
Administrators can set the following properties in SSMS Advanced Properties for the server farm:
EnableCustomVisuals: True/False
EnablePowerBIReportEmbeddedModels: True/False
EnablePowerBIReportExportData: True/False
MaxFileSizeMb: Default is now 1000
ModelCleanupCycleMinutes: How often it checks to evict models from memory
ModelExpirationMinutes: How long until model expires and is evicted, based on last time used
ScheduleRefreshTimeoutMinutes: How long data refresh can take for a model. By default, this is two hours.
There is no hard upper limit.
Config file rsreportserver.config

<Configuration>
<Service>
<PollingInterval>10</PollingInterval>
<IsDataModelRefreshService>false</IsDataModelRefreshService>
<MaxQueueThreads>0</MaxQueueThreads>
</Service>
</Configuration>

Developer API
The developer API (REST API) introduced for SSRS 2017 has been extended for Power BI Report Server to work
with both Excel files and .pbix files. One potential use case is to programmatically download files from the server,
refresh them, and then republish them. This is the only way to refresh Excel workbooks with PowerPivot models,
for example.
Note that there is a new separate API for large files, which will be updated in the Power BI Report Server version
of Swagger.
SQL Server Analysis Services (SSAS ) and the Power BI Report Server memory footprint
Power BI Report Server now hosts SQL Server Analysis Services (SSAS ) internally. This isn't specific to scheduled
refresh. Hosting SSAS can greatly expand the report server memory footprint. The AS.ini configuration file is
available on the server nodes, so if you're familiar with SSAS, you may want to update the settings, including
maximum memory limit and disk caching etc. See Server properties in Analysis Services for details.
Viewing and interacting with Excel workbooks
Excel and Power BI contain a portfolio of tools that is unique in the industry. Together, they enable business
analysts to more easily gather, shape, analyze, and visually explore their data. In addition to viewing Power BI
reports in the web portal, business users can now do the same with Excel workbooks in Power BI Report Server,
giving them a single location to publish and view their self-service Microsoft BI content.
We’ve published a walkthrough of how to add Office Online Server (OOS ) to your Power BI Report Server
preview environment. Customers with a Volume Licensing account can download OOS from the Volume License
Servicing Center at no cost and will have view -only functionality. Once configured, users can view and interact with
Excel workbooks that:
Have no external data source dependencies
Have a live connection to an external SQL Server Analysis Services data source
Have a PowerPivot data model
Support for new table and matrix visuals
Power BI Report Server now supports the new Power BI table and matrix visuals. To create reports with these
visuals, you will need an updated Power BI Desktop release for the October 2017 release. It can't be installed side
by side with the Power BI Desktop (June 2017) release. For the latest version of Power BI Desktop, on the Power
BI Report Server download page, select Advanced download options.

June 2017
Power BI Report Server made generally available (GA).

May 2017
Power BI Report Server Preview made available
Ability to publish Power BI reports on-premises
support for custom visuals
Support for Analysis Services live connections only with more data sources to come.
Power BI Mobile app updated to display Power BI reports hosted in Power BI Report Server
Enhanced collaboration in reports with comments

Next steps
Check these sources to keep up-to-date on new features in Power BI Report Server.
Microsoft Power BI Blog
SQL Server Reporting Services Team Blog
The Guy in a Cube YouTube channel
More questions? Try asking the Power BI Community
 Changelog for Power BI Report Server
4/2/2019 • 6 minutes to read • Edit Online

This change log is for Power BI Report Server and lists new items along with bug fixes for each released build.
For detailed information about new features, see What's new in Power BI Report Server.

January 2019
Power BI Report Server
Version 1.4.7024.16477 (Build 15.0.1102.299 ), Released: March 28, 2019
Bug Fixes
Power BI Reports
Fix for issue with basic credentials when using direct query for SAP Hana and SAP
BW
Fix for OData feed data refresh fails with "Could not load file or assembly
'Microsoft.OData.Core.NetFX35.V7"
Power BI Report Server
Version 1.4.6969.7395 (Build 15.0.1102.235 ), Released: January 30, 2019
Bug Fixes
Power BI Reports
Fix for issue with basic credentials when using direct query
Fix for bidirectional relationships with row -level security filters applied
Fix for stale data after a model refresh in a scale-out environment
Fix for double scrollbar for table/ matrix on Firefox 63+
Fix for +/- icon size in Internet Explorer
Paginated Reports
Fix for issue with updating usage of a shared datasource for a report
Version 1.4.6960.38798 (Build 15.0.1102.222 ), Released: January 22, 2019
Features
Power BI Reports
Support for Row -level security
Expand and collapse on matrix row headers
Copy and paste between .pbix files
Smart alignment guides
Support for SAP BW 2.0 Connector
Administrators
Ability to restrict extensions of resources that can be uploaded to the report server
Ability to restrict supported hyperlink schemes
Programmability
New Web API: /PowerBIReports({Id})/DataModelRoles (GET)
New Web API: /PowerBIReports({Id})/DataModelRoleAssignments (GET & PUT)
See Power BI Report Server REST API for more details
 Bug Fixes
HTML Injection Vulnerability
Export to PDF is not showing Euro symbol
Saving a password with multiple data sources in Power BI reports invalidates non changed
passwords
Visuals display issues in Power BI Mobile App after being idle
Power BI Desktop (optimized for Power BI Report Server)
Version: 2.65.5313.1562 (January 2019 ), Released: January 30, 2019
Shortcut and pinned icons remain after uninstalling Power BI Report Server
Fix for pinning Power BI Report Server to start menu giving black text on a black icon
Version: 2.65.5313.1421 (January 2019 ), Released: January 22, 2019
Contains changes required for connection with Power BI Report Server (January 2019)

August 2018
Power BI Report Server
Version 1.3.6816.37243 (Build 15.0.2.557 ), Released: August 30, 2018
Bug fixes
Fixed an issue when server was upgraded from earlier versions of PBI Report Server
where a binding redirect was not updated, customers saw this :
Failed to load expression host assembly. Details: Could not load file or assembly
'Microsoft.ReportingServices.ProcessingObjectModel, Version=2018.7.0.0,
Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The
located assembly's manifest definition does not match the assembly reference.
(Exception from HRESULT: 0x80131040) (rsErrorLoadingExprHostAssembly)

Bug for Data Label Transparency is now fixed.

Version 1.3.6801.38816 (Build 15.0.2.540 ), Released: August 15, 2018
Features
SAP HANA SSO Direct Query support with Kerberos now available for Power BI Reports
Custom Visual API shipped with release - version 1.13.0
Custom visuals will fall back to a previous version compatible with the current version of
the server API (if available)
Power BI Desktop (optimized for Power BI Report Server)
Version: 2.61.5192.641 (August 2018 ), Released: August 15, 2018
Contains changes required for connection with Power BI Report Server (August 2018)

March 2018
Power BI Report Server
Version 1.2.6690.34729 (Build 15.0.2.402 ), Released: April 27, 2018
Bug fixes
Enable migration of SQL Server Reporting Services 2017 catalogs
For Power BI Reports (PBIX)
Reports can be refresh when a server is configured to use custom authentication
Modifying the properties of a report does not reset data source credentials
 For Paginated Reports (RDL )
Usage of Lookup() or derivative functions such as LookupSet() and MultiLookup()
in RDL Expressions no longer result in #Error
Linked reports respect the page size of the target report when printing
Subscriptions can be created for linked reports that use cascading parameters
Multi-value parameter defaults can be modified when using IE11
Data-driven subscription delivery options are editable
Subscriptions can be viewed and edited while the subscription is executing
Setting data source credentials does not remove expression-based connection
strings
For KPIs
Trend lines are refreshed when data is updated
General stability improvements
Version 1.2.6660.39920 (Build 15.0.2.389 ), Released: March 28, 2018
Bug fixes
For Power BI Reports (PBIX), fix for Export Data not working from Power BI Visuals
For Power BI Reports (PBIX), fix for URL filters not working
For Paginated Reports (RDL ), fix for images not being displayed correctly in IE11 after
upgrading to Power BI Report Server March release
Version 1.2.6648.38132 (Build 15.0.2.378 ), Released: March 19, 2018
Security Updates
Accessibility Improvements
Bug fixes
For Paginated Reports (RDL ), fix for parameters visibility in a linked report that is reverted
after editing its properties
Fix for web portal with custom forms authentication that is ignoring the sliding expiration
cookie
Fix for export to Word that creates unequal row height if row content is empty
For Paginated Reports (RDL ), fix for expression based connection string that is deleted
when we change credential for data source
Fix for ability to use KPI with text values
For Paginated Reports (RDL ), fix for ability to assign a new dataset to an existing Paginated
Report (RDL )
Other stability and usability fixes
Power BI Desktop (optimized for Power BI Report Server)
Version: 2.56.5023.1043 (March 2018), Released: March 19, 2018
Contains changes required for connection with Power BI Report Server (March 2018)

October 2017
Power BI Report Server
Version 1.1.6582.41691 (Build 14.0.600.442 ), Released: January 10, 2018
Security Updates
Bug Fixes
Fix for Model.GetParameters returning 400
Fix for setting shared data set to existing Paginated Reports (RDL )
 Fix for ExecutionNotFoundException when exporting report with different parameter
values to PDF
Version 1.1.6551.5155 (Build 14.0.600.438 ), Released: December 11, 2017
Bug Fixes
Failure to save data after refreshing for certain Power BI Desktop reports.
Version 1.1.6530.30789 (Build 14.0.600.437 ), Released: November 17, 2017
Bug Fixes
Fix for Basic Authentication Scenarios
Fix for weekdays were not selectable on schedule page for Subscriptions, Cache Refresh
Plans and History Snapshots on Portal
For Paginated Reports (RDL ), fix for having expressions in Textbox with CanGrow property
set to false is resulting in values not showing colors and fonts not being proper
For Power BI Reports (PBIX), fix for adding Legends to line chart renders an empty visual
Version 1.1.6514.9163 (Build 14.0.600.434 ), Released: November 1, 2017
Bug Fixes
Fix for upload reliability problems for PBIX reports over 500MB
Fix for data loading issue for PBIX reports over 1GB
Version 1.1.6513.3500 (Build 14.0.600.433 ), Released: October 31, 2017
Features
Embedded Data Model Support
Excel Workbook Viewing (with Office Online Server integration enabled)
Scheduled Data Refresh (PBIX)
Direct Query Support
Large File Support (up to 2 GB )
Public REST API
Shared Dataset support in Power BI Desktop (via oData)
URL Parameter Support for PBIX files
Accessibility improvements
Power BI Desktop (optimized for Power BI Report Server)
Version: 2.51.4885.3981 (October 2017 ), Released: April 10, 2018
Security Updates
Version: 2.51.4885.2501 (October 2017 ), Released: January 10, 2018
Security Updates
Version: 2.51.4885.1423 (October 2017 ), Released: November 17, 2017
Bug Fixes
Fix for 32-bit Power BI Desktop failing to run on x86 OS
For Power BI Reports (PBIX), fix to show x-axis gridlines
Other minor bug fixes
Version: 2.51.4885.1041 (October 2017 ), Released: October 31, 2017
Features
Contains changes required for connection with Power BI Report Server (October 2017)

June 2017
 Power BI Report Server
Build 14.0.600.309, Released: January 10, 2018
Security Updates
Build 14.0.600.305, Released: September 19, 2017
Bug Fixes
Update to the latest Bing Maps Web Control
Build 14.0.600.301, Released: July 11, 2017
Bug Fixes
The {{UserId}} tag resolves to the stored credentials instead of the user executing the
report in Power BI Reports
Some images fail to render in Power BI Report Server reports
Unable to change the name of a Power BI Report in the Power BI Report Server
Unable to load Custom Visuals in the Power BI mobile application (it requires reinstall of
the mobile app to clear up the local cache)
Build 14.0.600.271,Released: June 12, 2017
Power BI Report Server initial release
Power BI Desktop (optimized for Power BI Report Server)
Version: 2.47.4766.4901 (June 2017 ), Released: January 10, 2018
Security Updates

Next steps
What is Power BI Report Server? Administrator overview
Install Power BI Report Server
Download Report Builder
Download SQL Server Data Tools (SSDT)
More questions? Try asking the Power BI Community
 Support timeline for Power BI Report Server
2/15/2019 • 2 minutes to read • Edit Online

Power BI Report Server releases a few times per year. Security and critical updates are available until the next
release becomes generally available (GA). After the next release, the previous release continues to receive security
updates for the remainder of the 12-month release lifespan.
This support policy allows us to deliver innovation to customers at a rapid rate while providing flexibility for
customers to adopt the innovation at their pace.
Security and Critical Updates servicing phase - When running the latest current version of Power BI Report
Server, you receive both Security and Critical updates.
Security Updates (Only) servicing phase - After the release of a new version, support for older versions
reduces to Security updates only for the rest of the 12-month support lifecycle (shown in figure 1).

Version history
VERSION AVAILABILITY DATE SUPPORT END DATE

June 2017 June 12, 2017 No longer supported

October 2017 October 31, 2017 No longer supported

March 2018 March 19, 2018 March 19, 2019

August 2018 August 15, 2018 August 15, 2019

January 2019 January 23, 2019 January 23, 2020

To download Power BI Report Server, and Power BI Desktop optimized for Power BI Report Server, go to On-
premises reporting with Power BI Report Server.
Next steps
What's new in Power BI Report Server
What is Power BI Report Server? Administrator overview
Install Power BI Report Server
More questions? Try asking the Power BI Community
 Hardware and software requirements for installing
Power BI Report Server
3/22/2019 • 3 minutes to read • Edit Online

This article lays out the minimum hardware and software requirements to install and run Power BI Report Server.

Processor, Memory, and Operating System Requirements

COMPONENT REQUIREMENT

.NET Framework 4.6

You can manually install the .NET Framework from Microsoft

.NET Framework 4.6 (Web Installer) for Windows.

For more information, recommendations, and guidance about

the .NET Framework 4.6 see .NET Framework Deployment
Guide for Developers.

Windows 8.1, and Windows Server 2012 R2 require

KB2919355 before installing .NET Framework 4.6.

Hard Disk Power BI Report Server requires a minimum of 1 GB of

available hard-disk space.

Addition space will be required on the database server that is

hosting the report server database.

Memory Minimum: 1 GB

Recommended: At least 4 GB

Processor speed Minimum: x64 Processor: 1.4 GHz

Recommended: 2.0 GHz or faster

Processor type x64 Processor: AMD Opteron, AMD Athlon 64, Intel Xeon
with Intel EM64T support, Intel Pentium IV with EM64T
support
 COMPONENT REQUIREMENT

Operating system Windows Server 2019 Datacenter

Windows Server 2019 Standard

Windows Server 2016 Datacenter

Windows Server 2016 Standard

Windows Server 2012 R2 Datacenter

Windows Server 2012 R2 Standard

Windows Server 2012 R2 Essentials

Windows Server 2012 R2 Foundation

Windows Server 2012 Datacenter

Windows Server 2012 Standard

Windows Server 2012 Essentials

Windows Server 2012 Foundation

Windows 10 Home

Windows 10 Professional

Windows 10 Enterprise

Windows 8.1

Windows 8.1 Pro

Windows 8.1 Enterprise

Windows 8

Windows 8 Pro

Windows 8 Enterprise

NOTE
Installation of Power BI Report Server is supported on x64 processors only.

Database server version requirements

SQL Server is used to host the report server databases. The SQL Server Database Engine instance can be a local
or remote instance. The following are the supported versions of SQL Server Database Engine that can be used to
host the report server databases:
SQL Server 2017
SQL Server 2016
SQL Server 2014
SQL Server 2012
When you create the report server database on a remote computer, you have to configure the connection to use a
domain user account or a service account with network access. If you decide to use a remote SQL Server instance,
consider carefully which credentials the report server should use to connect to the SQL Server instance. For more
information, see Configure a Report Server Database Connection.

Considerations
Power BI Report Server will install default values to configure the core settings required to make a report server
operational. It has the following requirements:
A SQL Server Database Engine must be available after setup and before you configure the database for the
report server. The Database Engine instance hosts the report server database that Reporting Services
Configuration Manager will create. The Database Engine is not required for the actual setup experience.
Reporting Services Features Supported by the Editions of SQL Server outlines differences between the editions
of SQL Server.
The user account that runs Setup must be a member of the local Administrators group.
The user account that runs Reporting Services Configuration Manager must have permission to access and
create databases on the Database Engine instance that hosts the report server databases.
Setup must be able to use the default values to reserve the URLs that provide access to the report server and
the web portal. These values are port 80, a strong wildcard, and the virtual directory names in the format
ReportServer and Reports.

Read-only domain controller (RODC)

You can install the report server in an environment that has a Read-Only Domain Controller (RODC ). However,
Reporting Services needs access to a Read-Write Domain Controller to function properly. If Reporting Services
only has access to a RODC, you may encounter errors when trying to administer the service.

Power BI reports and Analysis Services live connections

You can use a live connection against tabular or multidimensional instances. Your Analysis Services server has to
be the proper version and edition to work properly.

SERVER VERSION REQUIRED SKU

2012 SP1 CU4 or later Business Intelligence and Enterprise SKU

2014 Business Intelligence and Enterprise SKU

2016 and later Standard SKU or higher

Next steps
What is Power BI Report Server?
Administrator overview
Install Power BI Report Server
Download Report Builder
Download SQL Server Data Tools (SSDT)
More questions? Try asking the Power BI Community
 Browser support for Power BI Report Server
1/14/2019 • 3 minutes to read • Edit Online

Learn about what browser versions are supported for managing and viewing Power BI Report Server and the
Report Viewer Controls.

Browser requirements for the web portal

The following is the current list of browsers supported for the web portal.
Microsoft Windows
Windows 7, 8.1, 10; Windows Server 2008 R2, 2012, 2012 R2
Microsoft Edge (+)
Microsoft Internet Explorer 11
Google Chrome (+)
Mozilla Firefox (+)
Apple OS X
OS X 10.9 -10.11
Apple Safari (+)
Google Chrome (+)
Mozilla Firefox (+)
Apple iOS
iPhone and iPad with iOS 10
Apple Safari (+)
Google Android
Phones and tablets with Android 4.4 (KitKat) or later
Google Chrome (+)
(+) Latest publicly released version

Browser requirements for the Report Viewer web control (2015)

The following is the current list of browsers supported with the Report Viewer web control. The report viewer
supports viewing reports from the web portal.
Microsoft Windows
Windows 7, 8.1, 10; Windows Server 2008 R2, 2012, 2012 R2
Microsoft Edge (+)
Microsoft Internet Explorer 11
Google Chrome (+)
Mozilla Firefox (+)
Apple OS X
OS X 10.9 -10.11
 Apple Safari (+)
(+) Latest publicly released version
Authentication requirements
Browsers support specific authentication schemes that must be handled by the report server in order for the client
request to succeed. The following table identifies the default authentication types supported by each browser
running on a Windows operating system.

BROWSER TYPE SUPPORTS BROWSER DEFAULT SERVER DEFAULT

Microsoft Edge (+) Negotiate, Kerberos, NTLM, Negotiate Yes. The default
Basic authentication settings work
with Edge.

Microsoft Internet Negotiate, Kerberos, NTLM, Negotiate Yes. The default

Explorer Basic authentication settings work
with Internet Explorer.

Google Chrome(+) Negotiate, NTLM, Basic Negotiate Yes. The default

authentication settings work
with Chrome.

Mozilla Firefox(+) NTLM, Basic NTLM Yes. The default

authentication settings work
with Firefox.

Apple Safari(+) NTLM, Basic Basic Yes. The default

authentication settings work
with Safari.

(+) Latest publicly released version

Script requirements for viewing reports
To use the report viewer, configure your browser to run scripts.
If scripting is not enabled, you will see an error message similar to the following when you open a report:

Your browser does not support scripts or has been configured to not allow scripts to run. Click here to view
this report without scripts

If you choose to view the report without script support, the report is rendered in HTML without report viewer
capabilities such as the report toolbar and the document map.

NOTE
The report toolbar is part of the HTML Viewer component. By default the toolbar appears at the top of every report that is
rendered in a browser window. The report viewer provides features include the ability to search the report for information,
scroll to a specific page, and adjust the page size for viewing purposes. For more information about the report toolbar or
HTML Viewer, see HTML Viewer and the Report Toolbar.

Browser support for Report Viewer web server controls in Visual Studio
The Report Viewer Web server control is used to embed report functionality in an ASP.NET web application. For
more information on how to get the Report Viewer Control, see Integrating Reporting Services Using Report
Viewer Controls - Get Started.
Use a browser that has script support enabled. If the browser cannot run scripts, you cannot view the report.
Microsoft Windows
Windows 7, 8.1, 10; Windows Server 2008 R2, 2012, 2012 R2
Microsoft Edge (+)
Microsoft Internet Explorer 11
Google Chrome (+)
Mozilla Firefox (+)
(+) Latest publicly released version

Next steps
Administrator overview
Install Power BI Report Server
Download Report Builder
Download SQL Server Data Tools (SSDT)
More questions? Try asking the Power BI Community
 Admin overview, Power BI Report Server
1/14/2019 • 2 minutes to read • Edit Online

This article is the administration overview of Power BI Report Server, an on-premises location for storing and
managing your Power BI, mobile, and paginated reports. This article introduces concepts of planning, deploying,
and managing your Power BI Report Server, with links to more information.

Installing and migration

You need to install Power BI Report Server to start using it. We have articles that explain how to handle this task.
Before you start to install, upgrade, or migrate to Power BI Report Server, take a look at the system requirements
for the report server.
Installing
If you are deploying a new Power BI Report Server, you use the following document to help you.
Install Power BI Report Server
Migration
There is no in-place upgrade for SQL Server Reporting Services. If you have an existing SQL Server Reporting
Services instance that you want to make a Power BI Report Server, you need to migrate it. You may want to
perform a migration for other reasons as well. Review the migration document for more details.
Migrate a report server installation

Configuring your report server

You have many options when configuring your report server. Will you use SSL? Are you configuring an email
server? Do you want to integrate with the Power BI service to pin visualizations?
The majority of your configuration will occur within the Report Server Configuration Manager. Check out the
configuration manager documentation for more details.

Security
Security and protection are important to every organization. You can learn about authentication, authorization,
roles, and permissions over in the security documentation.

Next steps
Install Power BI Report Server
Find your report server product key
Install Power BI Desktop optimized for Power BI Report Server
Download Report Builder
Download SQL Server Data Tools (SSDT)
More questions? Try asking the Power BI Community
 Power BI report scheduled refresh in Power BI Report
Server
1/17/2019 • 3 minutes to read • Edit Online

Scheduled refresh for Power BI reports allows the data for a report to stay up to date.

Scheduled refresh is specific to Power BI reports with an embedded model. Meaning you imported data into the
report instead of using a live connection or DirectQuery. When importing your data, it is disconnected from the
original data source and needs to be updated to keep data fresh. Scheduled refresh is the way to keep your data up
to date.
Scheduled refresh is configured within the management section of a report. For more information on how to
configure scheduled refresh, see How to configure Power BI report scheduled refresh.

How this works

Several components are involved when using scheduled refresh for your Power BI reports.
SQL Server Agent as a timer to generate scheduled events.
Scheduled jobs are added to a queue of events and notifications in the report server database. In a scale-out
deployment, the queue is shared across all of the report servers in the deployment.
All report processing that occurs as a result of a schedule event is performed as a background process.
The data model is loaded within an Analysis Services instance.
For some data sources, the Power Query mashup engine is used to connect to data sources and transform the
data. Other data sources may be connected to directly from an Analysis Services service used to host the data
models for Power BI Report Server.
New data is loaded into the data model within Analysis Services.
Analysis Services processes the data and executes any needed calculations.
Power BI Report Server maintains an event queue for all scheduled operations. It polls the queue at regular
intervals to check for new events. By default, the queue is scanned at 10 second intervals. You can change the
interval by modifying the PollingInterval, IsNotificationService, and IsEventService configuration settings in
the RSReportServer.config file. IsDataModelRefreshService can also be used to set whether a report server
process scheduled events.
Analysis Services
Rendering a Power BI report, as well as performing a scheduled refresh, requires loading the Power BI report's
data model in Analysis Services. An Analysis Services process will be running with Power BI Report Server.

Considerations and limitations

When scheduled refresh can't be used
Not all Power BI Reports can have a scheduled refresh plan created on them. The following is a list of Power BI
Reports that you Can't create a scheduled refresh plan.
Your report contains one or more Analysis Services data sources, which use a live connection.
Your report contains one or more data sources, which use DirectQuery.
Your report does not contain any data source. For example, data is manually entered via Enter Data or a report
contains only static content like images, text, etc.
In addition to the above list, there are specific scenarios with data sources in import mode, for which you cannot
create refresh plans.
If a File or Folder data source is used and the file path is a local path (e.g. C:\Users\user\Documents), then a
refresh plan cannot be created. The path must be a path the report server can connect to like a network share.
For example, \myshare\Documents.
If data source can be connected using only OAuth (e.g. Facebook, Google Analytics, Salesforce, etc.), then cache
refresh plan cannot be created. At the moment, RS does not support OAuth authentication for any data source
whether it is for paginated, mobile or Power BI reports.
Memory limits
Traditional workload for a report server has been similar to a web application. The ability to load reports with
imported data or DirectQuery, and the ability to perform scheduled refresh, rely on an Analysis Services instance
being hosted alongside of the report server. As a result, this could result is unexpected memory pressure on the
server. Plan your server deployment accordingly knowning that Analysis Services may be consuming memory
alongside the report server.
For information on how to monitor an Analysis Services instance, see Monitor an Analysis Services Instance.
For information about memory settings within Analysis Services, see Memory Properties.

Next steps
Configure scheduled refresh on a Power BI report.
More questions? Try asking the Power BI Community
 Power BI report data sources in Power BI Report
Server
1/14/2019 • 6 minutes to read • Edit Online

Power BI reports can connect to a number of data sources. Depending on how data is used, different data sources
are available. Data can be imported or data can be queried directly using DirectQuery or a live connection to SQL
Server Analysis Services.
These data sources are specific to Power BI reports used within Power BI Report Server. For information about
data sources supported with paginated reports (.rdl), see Data Sources Supported by Reporting Services.

IMPORTANT
All data sources in a Power BI Desktop report must support configuring scheduled refresh.

List of supported data sources

Other data sources may work even though they aren't on the supported list.

DATA SOURCE CACHED DATA SCHEDULED REFRESH LIVE/DIRECTQUERY

SQL Server Database Yes Yes Yes

SQL Server Analysis Services Yes Yes Yes

Azure SQL Database Yes Yes Yes

Azure SQL Data Warehouse Yes Yes Yes

Excel Yes Yes No

Access Database Yes Yes No

Active Directory Yes Yes No

Amazon Redshift Yes No No

Azure Blob Storage Yes Yes No

Azure Data Lake Store Yes No No

Azure HDInsight (HDFS) Yes No No

Azure HDInsight (Spark) Yes Yes No

Azure Table Storage Yes Yes No

Dynamics 365 (online) Yes No No

DATA SOURCE CACHED DATA SCHEDULED REFRESH LIVE/DIRECTQUERY

Facebook Yes No No

Folder Yes Yes No

Google Analytics Yes No No

Hadoop File (HDFS) Yes No No

IBM DB2 Database Yes Yes No

Impala Yes No No

JSON Yes Yes No

Microsoft Exchange Yes No No

Microsoft Exchange Online Yes No No

MySQL Database Yes Yes No

OData Feed Yes Yes No

ODBC Yes Yes No

OLE DB Yes Yes No

Oracle Database Yes Yes Yes

PostgreSQL Database Yes Yes No

Power BI service No No No

R Script Yes No No

Salesforce Objects Yes No No

Salesforce Reports Yes No No

SAP Business Warehouse Yes Yes Yes

server

SAP HANA Database Yes Yes Yes

SharePoint Folder (on- Yes Yes No

premises)

SharePoint List (on- Yes Yes No

premises)

SharePoint Online List Yes No No

DATA SOURCE CACHED DATA SCHEDULED REFRESH LIVE/DIRECTQUERY

Snowflake Yes No No

Sybase Database Yes Yes No

Teradata Database Yes Yes Yes

Text/CSV Yes Yes No

Web Yes Yes No

XML Yes Yes No

appFigures (Beta) Yes No No

Azure Analysis Services Yes No Yes

database

Azure Cosmos DB (Beta) Yes No No

Azure HDInsight Spark Yes No No

(Beta)

Common Data Service (Beta) Yes No No

comScore Digital Analytix Yes No No

(Beta)

Dynamics 365 for Customer Yes No No

Insights (Beta)

Dynamics 365 for Financials Yes No No

(Beta)

GitHub (Beta) Yes No No

Google BigQuery (Beta) Yes No No

IBM Informix database (Beta) Yes No No

IBM Netezza (Beta) Yes No No

Kusto (Beta) Yes No No

MailChimp (Beta) Yes No No

Microsoft Azure Yes No No

Consumption Insights (Beta)

Mixpanel (Beta) Yes No No

Planview Enterprise (Beta) Yes No No

 DATA SOURCE CACHED DATA SCHEDULED REFRESH LIVE/DIRECTQUERY

Projectplace (Beta) Yes No No

QuickBooks Online (Beta) Yes No No

Smartsheet Yes No No

Spark (Beta) Yes No No

SparkPost (Beta) Yes No No

SQL Sentry (Beta) Yes No No

Stripe (Beta) Yes No No

SweetIQ (Beta) Yes No No

Troux (Beta) Yes No No

Twilio (Beta) Yes No No

tyGraph (Beta) Yes No No

Vertica (Beta) Yes No No

Visual Studio Team Services Yes No No

(Beta)

Webtrends (Beta) Yes No No

Zendesk (Beta) Yes No No

IMPORTANT
Row-level security configured at the data source should work for certain DirectQuery (SQL Server, Azure SQL Database,
Oracle and Teradata) and live connections assuming Kerberos is configured properly in your environment.

List of supported authentication methods for model refresh

Power BI Report Server does not support OAuth-based authentication for model refresh. Some data sources such
as Excel or Access databases make use of a separate step like File or Web to connect to data.

ANONYMOUS USERNAME AND WINDOWS

DATA SOURCE AUTHENTICATION KEY AUTHENTICATION PASSWORD AUTHENTICATION

SQL Server Database No No Yes Yes

SQL Server Analysis No No Yes Yes

Services

Web Yes No Yes Yes

 ANONYMOUS USERNAME AND WINDOWS
DATA SOURCE AUTHENTICATION KEY AUTHENTICATION PASSWORD AUTHENTICATION

Azure SQL Database No No Yes No

Azure SQL Data No No Yes No

Warehouse

Active Directory No No Yes Yes

Amazon Redshift No No No No

Azure Blob Storage Yes Yes No No

Azure Data Lake Store No No No No

Azure HDInsight No No No No
(HDFS)

Azure HDInsight Yes Yes No No

(Spark)

Azure Table Storage No Yes No No

Dynamics 365 (online) No No No No

Facebook No No No No

Folder No No No Yes

Google Analytics No No No No

Hadoop File (HDFS) No No No No

IBM DB2 Database No No Yes Yes

Impala No No No No

Microsoft Exchange No No No No

Microsoft Exchange No No No No
Online

MySQL Database No No Yes Yes

OData Feed Yes Yes Yes Yes

ODBC Yes No Yes Yes

OLE DB Yes No Yes Yes

Oracle Database No No Yes Yes

 ANONYMOUS USERNAME AND WINDOWS
DATA SOURCE AUTHENTICATION KEY AUTHENTICATION PASSWORD AUTHENTICATION

PostgreSQL Database No No Yes No

Power BI service No No No No

R Script No No No No

Salesforce Objects No No No No

Salesforce Reports No No No No

SAP Business No No Yes No

Warehouse server

SAP HANA Database No No Yes Yes

SharePoint Folder Yes No No Yes

(on-premises)

SharePoint List (on- Yes No No Yes

premises)

SharePoint Online List No No No No

Snowflake No No No No

Sybase Database No No Yes Yes

Teradata Database No No Yes Yes

appFigures (Beta) No No No No

Azure Analysis No No No No
Services database
(Beta)

Azure Cosmos DB No No No No
(Beta)

Azure HDInsight No No No No
Spark (Beta)

Common Data Service No No No No

(Beta)

comScore Digital No No No No
Analytix (Beta)

Dynamics 365 for No No No No

Customer Insights
(Beta)
 ANONYMOUS USERNAME AND WINDOWS
DATA SOURCE AUTHENTICATION KEY AUTHENTICATION PASSWORD AUTHENTICATION

Dynamics 365 for No No No No

Financials (Beta)

GitHub (Beta) No No No No

Google BigQuery No No No No
(Beta)

IBM Informix No No No No
database (Beta)

IBM Netezza (Beta) No No No No

Kusto (Beta) No No No No

MailChimp (Beta) No No No No

Microsoft Azure No No No No
Consumption Insights
(Beta)

Mixpanel (Beta) No No No No

Planview Enterprise No No No No
(Beta)

Projectplace (Beta) No No No No

QuickBooks Online No No No No
(Beta)

Smartsheet No No No No

Spark (Beta) No No No No

SparkPost (Beta) No No No No

SQL Sentry (Beta) No No No No

Stripe (Beta) No No No No

SweetIQ (Beta) No No No No

Troux (Beta) No No No No

Twilio (Beta) No No No No

tyGraph (Beta) No No No No

Vertica (Beta) No No No No
 ANONYMOUS USERNAME AND WINDOWS
DATA SOURCE AUTHENTICATION KEY AUTHENTICATION PASSWORD AUTHENTICATION

Visual Studio Team No No No No

Services (Beta)

Webtrends (Beta) No No No No

Zendesk (Beta) No No No No

List of supported authentication methods for DirectQuery

Power BI Report Server does not support OAuth-based authentication for DirectQuery.

INTEGRATED
ANONYMOUS KEY USERNAME AND WINDOWS WINDOWS
DATA SOURCE AUTHENTICATION AUTHENTICATION PASSWORD AUTHENTICATION AUTHENTICATION

SQL Server No No Yes Yes Yes

Database

SQL Server No No Yes Yes Yes

Analysis Services

Azure SQL No No Yes No No

Database

Azure SQL Data No No Yes No No

Warehouse

Oracle Database No No Yes Yes Yes

SAP Business No No Yes No Yes

Warehouse
server

SAP HANA No No Yes Yes No

Database

Teradata No No Yes Yes Yes

Database

Next steps
Now that you've connected to your data source, create a Power BI report using data from that data source.
More questions? Try asking the Power BI Community
 Paginated report data sources in Power BI Report
Server
1/14/2019 • 2 minutes to read • Edit Online

Reporting Services paginated reports in Power BI Report Server support the same data sources that are supported
in SQL Server Reporting Services. See the list of Data sources supported by Reporting Services.

Next steps
Now that you've connected to your data source, create a paginated report.
More questions? Try asking the Power BI Community
 Troubleshoot scheduled refresh in Power BI Report
Server
2/13/2019 • 7 minutes to read • Edit Online

This article discusses resources available to troubleshoot issues with scheduled refresh in Power BI Report Server.
As issues come up, this article will be updated with information to help you.

Common issues
The following are the more common issues you will hit when trying to schedule refresh for a report.
Driver related problems
Connecting to different data sources may require 3rd party drivers that need to be installed in order to connect
successfully. Not only would you need to install them on the machine you are using Power BI Desktop on, but you
will also need to make sure the driver is installed on the report server.
The driver may also come in both 32bit and 64bit. Make sure to install the 64bit driver as Power BI Report Server
is 64bit.
Please refer to the manufacturer for details on how to install and configure 3rd party drivers.
Memory pressure
Memory pressure can occur when reports require more memory to process and render. Schedule refresh on
reports may demand a significant amount of memory on the machine. Especially for larger reports. Memory
pressure can result in report failures as well as a potential crash of the report server itself.
If you are encountering memory pressure consistently, it may be worth looking at a scaled out deployment of the
report server in order to spread the load of resources. You can also define that a given report server is used for
data refresh with the IsDataModelRefreshService setting within rsreportserver.config. With this setting, you could
define one or more servers to be the front end server to handle on demand reports, and have another set of
servers to only be used for scheduled refresh.
For information on how to monitor an Analysis Services instance, see Monitor an Analysis Services Instance.
For information about memory settings within Analysis Services, see Memory Properties.
Kerberos configuration
Connecting to a data source with windows credentials may require configuring Kerberos constrained delegation to
make a successful connection. For more information about how to configure Kerberos constrained delegation, see
Configure Kerberos to use Power BI reports.

Known issues
Information about known issues will be listed here when they become available.

Configuration settings
The following settings can be used to affect scheduled refresh. Settings set within SQL Server Management Studio
(SSMS ) apply to all report servers within a scale-out deployment. Settings configured within rsreportserver.config
are for the specific server they are set on.
Settings within SSMS:

SETTING DESCRIPTION

MaxFileSizeMb Maximum file size for uploaded reports. Default is 1000 MB (1

GB). Maximum value is 2000 MB (2 GB).

ModelCleanupCycleMinutes Defines how often the model is checked to evict it from

memory. Default is 15 minutes.

ModelExpirationMinutes Defines how long until the model expires based on the last
time used and is evicted. Default is 60 minutes.

ScheduleRefreshTimeoutMinutes Defines how long the data refresh can take for a mode.
Default is 120 minutes. There is no upper limit.

Settings within rsreportserver.config:

<Configuration>
<Service>
<PollingInterval>10</PollingInterval>
<IsDataModelRefreshService>false</IsDataModelRefreshService>
<MaxQueueThreads>0</MaxQueueThreads>
</Service>
</Configuration>

Tools for troubleshooting

Logs relevant for scheduled refresh of Power BI reports
The log files which hold information about scheduled refresh are the RSPowerBI_ logs. They are located in the
LogFiles folder of your report server installation location.

C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\RSPowerBI_*.log

Error condition

2017-10-20 02:00:09.5188|ERROR|744|Error Processing Data Model Refresh: SessionId: e960c25e-ddd4-4763-aa78-

0e5dceb53472, Status: Error Model can not be refreshed because not all the data sources are embedded, Exception
Microsoft.PowerBI.ReportServer.AsServer.InvalidDataSourceException: Model can not be refreshed because not all
the data sources are embedde
at
Microsoft.PowerBI.ReportServer.WebHost.EventHandler.AnalysisServicesDataRefresh.CanModelRefresh(IEnumerable`1
dataSources)
at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.<>c__DisplayClass7.
<ExecuteActionWithLogging>b__5()
at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.
<ExecuteFuncWithLogging>d__1`1.MoveNext()

Successful refresh
 2017-10-25 15:23:41.9370|INFO|6|Handling event with data: TimeEntered: 10/25/2017 8:23:41 PM, Type: Event,
SessionId: 46d398db-0b1f-49d8-b7bd-c5461c07ec7a, EventType: DataModelRefresh
2017-10-25 15:23:41.9370|INFO|6|Processing Data Model Refresh: SessionId: 46d398db-0b1f-49d8-b7bd-c5461c07ec7a,
Status: Starting Data Refresh.
2017-10-25 15:23:41.9370|INFO|6|Processing Data Model Refresh: SessionId: 46d398db-0b1f-49d8-b7bd-c5461c07ec7a,
Status: Starting Retrieving PBIX AsDatabaseInfo.
2017-10-25 15:23:42.7134|INFO|6|Processing Data Model Refresh: SessionId: 46d398db-0b1f-49d8-b7bd-c5461c07ec7a,
Status: Starting Verifying all the data sources are embedded.
2017-10-25 15:23:42.7134|INFO|6|Processing Data Model Refresh: SessionId: 46d398db-0b1f-49d8-b7bd-c5461c07ec7a,
Status: Starting Verifying connection strings are valid.
2017-10-25 15:23:42.7134|INFO|6|Processing Data Model Refresh: SessionId: 46d398db-0b1f-49d8-b7bd-c5461c07ec7a,
Status: Starting Streaming model to Analysis Server.
2017-10-25 15:23:42.7603|INFO|6|Processing Data Model Refresh: SessionId: 46d398db-0b1f-49d8-b7bd-c5461c07ec7a,
Status: Starting Refreshing the model.
2017-10-25 15:23:51.5258|INFO|6|Processing Data Model Refresh: SessionId: 46d398db-0b1f-49d8-b7bd-c5461c07ec7a,
Status: Starting Removing credentials from the model.
2017-10-25 15:23:51.6508|INFO|6|Processing Data Model Refresh: SessionId: 46d398db-0b1f-49d8-b7bd-c5461c07ec7a,
Status: Starting Saving model to the catalog.

Incorrect Credentials

2017-10-20 08:22:01.5595|INFO|302|Processing Data Model Refresh: SessionId: 22cd9ec3-b21a-4eb1-81ae-

15fac8d379ea, Status: Starting Refreshing the model.
2017-10-20 08:22:02.3758|ERROR|302|Error Processing Data Model Refresh: SessionId: 22cd9ec3-b21a-4eb1-81ae-
15fac8d379ea, Status: Error Failed to refresh the model, Exception
Microsoft.AnalysisServices.OperationException: Failed to save modifications to the server. Error returned: 'The
credentials provided for the SQL source are invalid. (Source at rosecatalog;reportserver.). The exception was
raised by the IDbCommand interface.
'.
at Microsoft.AnalysisServices.Tabular.Model.SaveChanges(SaveOptions saveOptions)
at Microsoft.PowerBI.ReportServer.AsServer.TOMWrapper.RefreshModel(Database database)
at Microsoft.PowerBI.ReportServer.AsServer.AnalysisServicesServer.RefreshDatabase(String databaseName,
IEnumerable`1 dataSources)
at
Microsoft.PowerBI.ReportServer.WebHost.EventHandler.AnalysisServicesDataRefresh.RefreshDatabase(AsDatabaseInfo
asDatabaseInfo)
at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.<>c__DisplayClass7.
<ExecuteActionWithLogging>b__5()
at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.
<ExecuteFuncWithLogging>d__1`1.MoveNext()
2017-10-20 08:22:02.4588|ERROR|302|Error Processing Data Model Refresh: SessionId: 22cd9ec3-b21a-4eb1-81ae-
15fac8d379ea, Status: Error Failed Data Refresh, Exception Microsoft.AnalysisServices.OperationException:
Failed to save modifications to the server. Error returned: 'The credentials provided for the SQL source are
invalid. (Source at rosecatalog;reportserver.). The exception was raised by the IDbCommand interface.
'.
at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.ExecuteActionWithLogging(Action
methodToExecute, String description, String localizedDescription, String messageInFailure, RefreshInfo
refreshInfo, DataAccessors dataAccessors, ReportEventType operation, Int64 size, Boolean isDataRetrieval,
Boolean showInExecutionLog)
at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.AnalysisServicesDataRefresh.RefreshData(RefreshInfo
refreshInfo)
at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.<>c__DisplayClass7.
<ExecuteActionWithLogging>b__5()
at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.
<ExecuteFuncWithLogging>d__1`1.MoveNext()

Enabling Verbose Logging

Enabling verbose logging, in Power BI Report Server, is the same as it is for SQL Server Reporting Services.
1. Open <install directory>\PBIRS\ReportServer\bin\ReportingServicesService.exe.config .
2. Under <system.diagnostics> , change DefaultTraceSwitch to 4.
3. Under <RStrace> , change Components to all:4.
ExecutionLog
Whenever a Power BI report is rendered, or a schedule refresh plan is executed, new entries are added to the
Execution Log in the database. These entries are available in the ExecutionLog3 view within the report server
catalog database.
Execution log entries for Power BI reports differ from entries for other report types.
TimeRendering columns is always 0. Rendering of Power BI reports happens in the browser, not in the server.
There are 2 Request Types and subsequent item actions:
Interactive: whenever a report is being viewed.
ASModelStream: when the data model is streamed to Analysis Services from the catalog.
ConceptualSchema: when user clicks on viewing the report.
QueryData: whenever data is being requested from client.
Refresh Cache: whenever a schedule refresh plan has been executed.
ASModelStream: whenever the data model is streamed to Analysis Services from the catalog.
DataRefresh: whenever data is being refreshed from one or more data sources.
SaveToCatalog: whenever the data model is being saved back to the catalog.

Analysis Services
There may be times you want to modify Analysis Services for diagnosing issues, or adjust memory limits.

IMPORTANT
These settings will be reset any time you upgrade the report server. Be sure to keep a copy of your changes and reapply
them if needed.

Install location
The default location for Power BI Report Server, and Analysis Services is the following.
C:\Program Files\Microsoft Power BI Report Server\PBIRS\ASEngine

Configuring Analysis Services settings (msmdsrv.ini)

In the <install directory>\PBIRS\ASEngine directory, you will find the msmdsrv.ini file, which you can use to control
different settings of Analysis Services. When you open this file, you will immediately realize that this file doesn't
have all the settings you would expect in the msmdsrv.ini file.
This is because the actual Analysis Services process that is run by Power BI Report Server is launched in
<install directory>\PBIRS\ASEngine\workspaces . In that folder, you will see the full msmdsrv.ini file you are used to.
It is important not to modify the file within the workspaces folder as it is rewritten whenever the Analysis Services
process launches. If you want to control a setting, please do this by modifying msmdsrv.ini in the
<install directory>\PBIRS\ASEngine directory.

The following settings are reset when ever the Analysis Services process is launched. Any changes you make to
these will be ignored.
ConfigurationSettings\PrivateProcess
ConfigurationSettings\DataDir
ConfigurationSettings\LogDir
ConfigurationSettings\TempDir
ConfigurationSettings\BackupDir
ConfigurationSettings\AllowedBrowsingFolders
ConfigurationSettings\CrashReportsFolder
 ConfigurationSettings\ExtensionDir
ConfigurationSettings\Port
ConfigurationSettings\DeploymentMode
ConfigurationSettings\ServerLocation
ConfigurationSettings\TMCompatabilitySKU
ConfigurationSettings\FlightRecorder\TraceDefinitionFile
Profiling the local Analysis Services process
A SQL Profiler trace can be run on the local Analysis Services process for diagnostic purposes. To connect to the
local Analysis Services instance, do the following.
SQL Server Profiler Trace is included with the SQL Server Management Studio (SSMS ) download.
1. Start SQL Server Profiler as an administrator.
2. Select the New Trace button.
3. In the Connect to server dialog, select Analysis Services and enter localhost:5132 for the server name.
4. In the Trace properties dialog, select the events you want to capture and select Run.

Lock Pages In Memory Windows privilege

If you find that you are unable to render a Power BI report, assigning the Lock pages in memory privilege to the
services account running Power BI Report server may help. For more information about how to configure Lock
pages in memory, see Windows privileges assigned to the Analysis Services service account.
More questions? Try asking the Power BI Community
 Developer handbook overview, Power BI Report
Server
3/4/2019 • 2 minutes to read • Edit Online

Welcome to the developer handbook for Power BI Report Server, an on-premises location for storing and
managing your Power BI, mobile, and paginated reports.

This handbook highlights options you have, as a developer, to work with Power BI Report Server.

Embedding
For any report within Power BI Report Server, you can embed within an iFrame by adding the querystring
parameter ?rs:Embed=true to the URL. This technique works with Power BI reports as well as other report types.
Report Viewer Control
For paginated reports, you can take advantage of the Report Viewer Control. With it, you can place the control
within a .NET windows or web application. For more information, see Get started with the Report Viewer Control.

APIs
You have several API options for interacting with Power BI Report Server. This technique includes the following.
REST APIs
URL Access
WMI Provider
You can also use the open-source PowerShell utilities to manage your report server.
 NOTE
The PowerShell utilities don't currently support Power BI Desktop files (.pbix).

Custom extensions
The Extension Library is a set of classes, interfaces, and value types that are included in Power BI Report Server.
This library provides access to system functionality and is designed to be the foundation on which Microsoft .NET
Framework applications can be used to extend Power BI Report Server components.
There are several types of extensions you can build.
Data processing extensions
Delivery extensions
Rendering extensions for paginated reports
Security extensions
To learn more, see Extension library.

Next steps
Get started with the Report Viewer Control
Building Applications Using the Web Service and the .NET Framework
URL Access
Extension library
WMI Provider
More questions? Try asking the Power BI Community
 Quickstart: Embed a Power BI Report Server report
using an iFrame in SharePoint Server
2/13/2019 • 2 minutes to read • Edit Online

In this quickstart you will learn how to embed a Power BI Report Server report by using an iFrame in a SharePoint
page. If you are working with SharePoint Online, Power BI Report Server must be publicly accessible. In
SharePoint Online, the Power BI Web Part that works with the Power BI service doesn’t work with Power BI Report
Server.

Prerequisites
You will need to have Power BI Report Server installed and configured.
You will need to have Power BI Desktop optimized for Power BI Report Server installed.
You will need to have a SharePoint environment installed and configured.

Creating the Power BI Report Server report URL

1. Download the sample from GitHub - Blog Demo.
2. Open the sample PBIX file from GitHub in Power BI Desktop optimized for Power BI Report Server.

3. Save the report to the Power BI Report Server.

4. View report in the Web Portal.

Capturing the URL parameter

Once you have your URL, you can create an iFrame within a SharePoint page, to host the report. For any Power BI
Report Server report URL you can add a querystring parameter of ?rs:embed=true to embed your report into an
iFrame.
For example: http://myserver/reports/powerbi/Sales?rs:embed=true

Embedding a Power BI Report Server report in a SharePoint iFrame

1. Navigate to a SharePoint Site Contents page.

2. Choose the page where you want to add your report.

3. Select the gear on the top right and select Edit Page.

4. Select Add Web Part.

 5. Under Categories select Media and Content, under Parts, select Content Editor, and then select Add.

6. Select Click here to add new content.

7. In the ribbon select the Format Text tab then select Edit Source.

8. In the Edit Source window paste your iFrame code and select OK.

For example:

<iframe width="800" height="600" src="http://myserver/reports/powerbi/Sales?rs:embed=true"

frameborder="0" allowFullScreen="true"></iframe>

9. In the ribbon select the Page tab and select Stop Editing.

10. Now you should see the report on the page.

Next steps
Quickstart: Create a Power BI report for Power BI Report Server
Quickstart: Create a paginated report for Power BI Report Server
More questions? Try asking the Power BI Community
 Install Power BI Desktop optimized for Power BI
Report Server
2/15/2019 • 3 minutes to read • Edit Online

Learn how to install Power BI Desktop optimized for Power BI Report Server.
To create Power BI reports for Power BI Report Server, you need to download and install Power BI Desktop
optimized for Power BI Report Server. This release is different from the Power BI Desktop used with the Power BI
service. For example, the version of Power BI Desktop for the Power BI service includes preview features that
aren't in the Power BI Report Server version until they're released. Using this release makes sure that the report
server can interact with a known version of the reports and model.
The good news is that you can install Power BI Desktop, and Power BI Desktop optimized for Power BI Report
Server, side by side on the same computer.

Download and install Power BI Desktop

The easiest way to be sure you have the most up-to-date version of Power BI Desktop optimized for Power BI
Report Server is to start from the web portal of your report server.
1. In the report server web portal, select the Download arrow > Power BI Desktop.

Or go directly to Microsoft Power BI Desktop (Optimized for Power BI Report Server - January 2019) in
the Microsoft Download Center.
2. In the Download Center page, select Download.
3. Depending on your computer, select:
PBIDesktopRS.msi (the 32-bit version) or
PBIDesktopRS_x64.msi (the 64-bit version).
4. After you download the installer, run the Power BI Desktop (January 2019) Setup Wizard.
5. At the end of the installation, check Start Power BI Desktop now.
It starts automatically and you're ready to go.

Verify you're using the correct version

It's easy to verify that you're using the correct Power BI Desktop: Look at the launch screen or title bar within
Power BI Desktop. The title bar indicates the month and year of the release. Also, the Power BI logo colors are
reversed, yellow on black instead of black on yellow.

The Power BI Desktop version for the Power BI service doesn't have the month and year in the title bar.

File extension association

If you install both Power BI Desktop and Power BI Desktop optimized for Power BI Report Server on the same
machine, the most recent installation of Power BI Desktop has the file association with .pbix files. Thus, when you
double-click a .pbix file, it launches the Power BI Desktop you installed most recently.
If you have Power BI Desktop and then install Power BI Desktop optimized for Power BI Report Server, all .pbix
files open in Power BI Desktop optimized for Power BI Report Server by default. If you would rather have Power
BI Desktop be the default to launch when opening a .pbix file, reinstall Power BI Desktop from the Microsoft Store.
You can always open the version of Power BI Desktop you want to use first. And then open the file from within
Power BI Desktop.
Editing a Power BI report from within Power BI Report Server, or creating a new Power BI report from the web
portal, always opens the correct version of Power BI Destop.

Considerations and limitations

Power BI reports in Power BI Report Server, in the Power BI service ( http://app.powerbi.com), and in the Power BI
mobile apps act almost exactly the same, but a few features are different.
In a browser
Power BI Report Server reports support all visualizations, including:
Custom visuals
Power BI Report Server reports don’t support:
R visuals
ArcGIS maps
Breadcrumbs
Power BI Desktop preview features
In the Power BI mobile apps
Power BI Report Server reports support all the basic functionality in the Power BI mobile apps, including:
Phone report layout: You can optimize a report for the Power BI mobile apps. On your mobile phone,
optimized reports have a special icon , and layout.
Power BI Report Server reports don’t support these features in the Power BI mobile apps:
R visuals
ArcGIS maps
Custom visuals
Breadcrumbs
Geofiltering or bar codes

Power BI Desktop for earlier versions of Power BI Report Server

If your report server is an earlier version, you need the corresponding version of Power BI Desktop. Here's the
previous version.
Microsoft Power BI Desktop (Optimized for Power BI Report Server - August 2018)

Next steps
Now that you have Power BI Desktop installed, you can start creating Power BI reports.
Create a Power BI report for Power BI Report Server
What is Power BI Report Server?
More questions? Try asking the Power BI Community
 Create a Power BI report for Power BI Report Server
2/15/2019 • 2 minutes to read • Edit Online

You can store and manage Power BI reports on premises in the Power BI Report Server web portal, just as you
can store Power BI reports in the cloud in the Power BI service (https://powerbi.com). You create and edit reports
in Power BI Desktop, and publish them to the web portal. Then report readers in your organization can view
them in a browser or in a Power BI mobile app on a mobile device.

Here are four quick steps to get you started.

Step 1: Install Power BI Desktop optimized for Power BI Report Server

If you've already created Power BI reports in Power BI Desktop, then you're almost ready to create Power BI
reports for Power BI Report Server. We recommend installing the version of Power BI Desktop optimized for
Power BI Report Server so you know the server and the app are always in sync. You can have both versions of
Power BI Desktop on the same computer.
1. In the report server web portal, select the Download arrow > Power BI Desktop.

Or go directly to Microsoft Power BI Desktop (Optimized for Power BI Report Server - August 2018) in
the Microsoft Download Center.
2. In the Download Center page, select Download.
3. Depending on your computer, select:
PBIDesktopRS.msi (the 32-bit version) or
PBIDesktopRS_x64.msi (the 64-bit version).
4. After you download the installer, run the Power BI Desktop (August 2018) Setup Wizard.
5. At the end of the installation, check Start Power BI Desktop now.
It starts automatically and you're ready to go. You can tell you have the right version because "Power BI
Desktop (August 2018)" is in the title bar.

6. If you're not familiar with Power BI Desktop, consider watching the videos on the welcome screen.

Step 2: Select a data source

You can connect to a variety of data sources. Read more about connecting to data sources.
1. From the welcome screen, select Get Data.
Or on the Home tab, select Get Data.
2. Select your data source -- in this example, Analysis Services.
3. Fill in Server, and optionally, Database. Make sure Connect live is selected > OK.

4. Choose the report server where you'll save your reports.

Step 3: Design your report

Here's the fun part: You get to create visuals that illustrate your data.
For example, you could create a funnel chart of customers and group values by yearly income.
1. In Visualizations, select Funnel chart.
2. Drag the field to be counted to the Values well. If it's not a numeric field, Power BI Desktop automatically
makes it a Count of the value.
3. Drag the field to group on to the Group well.
Read much more about designing a Power BI report.

Step 4: Save your report to the report server

When your report is ready, you save it to the Power BI Report Server you chose in Step 2.
1. On the File menu, select Save as > Power BI Report Server.

2. Now you can view it in the web portal.

Next steps
Power BI Desktop
There are so many great resources for creating reports in Power BI Desktop. This link is a good starting point.
Get started with Power BI Desktop
Guided learning: Getting started with Power BI Desktop
Power BI Report Server
Install Power BI Desktop optimized for Power BI Report Server
What is Power BI Report Server?
More questions? Try asking the Power BI Community
 Manage content in the web portal
2/15/2019 • 2 minutes to read • Edit Online

The Power BI Report Server web portal is an on-premises location for viewing, storing and managing your Power
BI, mobile, and paginated reports, and KPIs.

You can view the web portal in any modern browser. In the web portal, reports and KPIs are organized in folders,
and you can mark them as favorites. You can also store Excel workbooks there. From the web portal, you can
launch the tools you need to create reports:
Power BI reports created with Power BI Desktop: View them in the web portal and the Power BI mobile apps.
Paginated reports created in Report Builder: Modern-looking, fixed-layout documents optimized for printing.
KPIs created right in the web portal.
In the web portal you can browse the report server folders or search for specific reports. You can view a report, its
general properties and past copies of the report that are captured in report history. Depending on your
permissions, you might also be able to subscribe to reports for delivery to your e-mail inbox or a shared folder on
the file system.

Web portal roles and permissions

The web portal application runs in a browser. When you start the web portal, the pages, links, and options you see
vary based on the permissions you have on the report server. If you're assigned to a role with full permissions, you
have access to the complete set of application menus and pages for managing a report server. If you're assigned to
a role with permissions to view and run reports, you only see the menus and pages you need for those activities.
You can have different role assignments for different report servers, or even for the various reports and folders on
a single report server.

Start the web portal

1. Open your web browser.
 See this list of supported web browsers and versions.
2. In the address bar, type the web portal URL.
By default, the URL is http://[ComputerName]/reports.
The report server might be configured to use a specific port. For example,
http://[ComputerName]:80/reports or http://[ComputerName]:8080/reports
You see that the web portal groups items into these categories:
KPIs
Mobile reports
Paginated reports
Power BI Desktop reports
Excel workbooks
Datasets
Data sources
Resources

Manage items in the web portal

Power BI Report Server offers detailed control of the items you store on the web portal. For example, you can set
up subscriptions, caching, snapshots, and security on individual paginated reports.
1. Select the ellipsis (...) in the upper-right corner of an item, then select Manage.

2. Choose the property or other feature you want to set.

3. Select Apply.
Read more about working with subscriptions in the web portal.

Next steps
What is Power BI Report Server?
More questions? Try asking the Power BI Community
 Row-level security (RLS) in Power BI Report Server
3/26/2019 • 6 minutes to read • Edit Online

Setting up row -level security (RLS ) with Power BI Report Server can restrict data access for given users. Filters
restrict data access at the row level, and you can define filters within roles. If you're using the default permissions
in Power BI Report Server, any user with Publisher or Content Manager permissions for the Power BI report can
assign members to roles for that report.
You configure RLS for reports imported into Power BI with Power BI Desktop. You can also configure RLS on
reports that use DirectQuery, such as SQL Server. Keep in mind that RLS isn't respected if your DirectQuery
connection uses integrated authentication for report readers. For Analysis Services live connections, you configure
row -level security on the on-premises model. The security option doesn't show up for live connection datasets.

Define roles and rules in Power BI Desktop

You can define roles and rules within Power BI Desktop. When you publish to Power BI, it also publishes the role
definitions.
To define security roles, follow these steps.
1. Import data into your Power BI Desktop report, or configure a DirectQuery connection.

NOTE
You can't define roles within Power BI Desktop for Analysis Services live connections. You need to do that within the
Analysis Services model.

2. Select the Modeling tab.

3. Select Manage Roles.

4. Select Create.

5. Provide a name for the role.

6. Select the table that you want to apply a DAX rule.
7. Enter the DAX expressions. This expression should return a true or false. For example: [Entity ID ] = “Value”.
 NOTE
You can use username() within this expression. Be aware that username() has the format of DOMAIN\username
within Power BI Desktop. Within the Power BI service and Power BI Report Server, it's in the format of the user's User
Principal Name (UPN). Alternatively, you can use userprincipalname(), which always returns the user in the format of
their user principal name, [email protected].

8. After you have created the DAX expression, you can select the check above the expression box to validate
the expression.

9. Select Save.
You can't assign users to a role within Power BI Desktop. You assign them in the Power BI service. You can enable
dynamic security within Power BI Desktop by making use of the username() or userprincipalname() DAX functions
and having the proper relationships configured.

Bidirectional cross-filtering
By default, row -level security filtering uses single-directional filters, regardless of whether the relationships are set
to single direction or bidirectional. You can manually enable bidirectional cross-filter with row -level security.
Select the relationship and check the Apply security filter in both directions checkbox.

Check this box when implementing dynamic row -level security based on user name or login ID.
To learn more, see Bidirectional cross-filtering using DirectQuery in Power BI Desktop and the Securing the
Tabular BI Semantic Model technical whitepaper.

Validate the roles within Power BI Desktop

After you've created your roles, test the results of the roles within Power BI Desktop.
1. Select View As Roles.
 In View as roles, you see the roles you've created.

2. Select a role you created > OK to apply that role. The report renders the data relevant for that role.
3. You can also select Other user and supply a given user. It's best to supply the User Principal Name (UPN )
as that's what the Power BI service and Power BI Report Server use.

4. Select OK and the report renders based on what that user can see.
Within Power BI Desktop, Other user only displays different results if you're using dynamic security based on
your DAX expressions.

Add members to roles

After you save your report in Power BI Report Server, you manage security and add or remove members on the
server. Only users with either Publisher or Content Manager permissions for the report have the row -level
security option available and not greyed out.
If the report doesn't have the roles it needs, you need to open it in Power BI Desktop, add or modify roles, then
save it back to Power BI Report Server.
1. In Power BI Desktop, save the report to Power BI Report Server. You need to use the version of Power BI
Desktop optimized for Power BI Report Server.
2. In Power BI Report Service, select the ellipsis (… ) next to the report.
3. Select Manage > Row-level security.
 On the Row-level security page, you add members to a role you created in Power BI Desktop.
4. To add a member, select Add Member.
5. Enter the user or group in the text box in the Username format (DOMAIN\user) and select the roles you
wish to assign to them. The member has to be within your organization.

Depending on how you have Active Directory configured, entering the User Principal Name here also
works. In that case, the Report Server shows the corresponding username in the list.
6. Click OK to apply.
7. To remove members, check the box next to their names and select Delete. You can delete multiple
members at a time.

username() and userprincipalname()

You can take advantage of the DAX functions username() or userprincipalname() within your dataset. You can use
them within expressions in Power BI Desktop. When you publish your model, Power BI Report Server uses them.
Within Power BI Desktop, username() returns a user in the format of DOMAIN\User and userprincipalname()
returns a user in the format of [email protected].
Within Power BI Report Server, username() and userprincipalname() both return the user's User Principal Name
(UPN ), which is similar to an email address.
If you're using custom authentication in Power BI Report Server, it returns the username format you’ve set up for
users.

Limitations
Here are the current limitations for row -level security on Power BI models.
Users that had reports using the username() DAX function will notice new behavior now where the User Principal
Name (UPN ) is returned EXCEPT when using DirectQuery with integrated security. Since RLS isn't respected in
that scenario, the behavior in that scenario is unchanged.
You can define RLS only on datasets created with Power BI Desktop. To enable RLS for datasets created with Excel,
you must convert your files into Power BI Desktop (PBIX) files first. Learn more about converting Excel files.
Only Extract, Transform, Load (ETL ) and DirectQuery connections using stored credentials are supported. Live
connections to Analysis Services and DirectQuery connections using integrated authentication are handled in the
underlying data source.
If you're using integrated security with DirectQuery, then your users may notice:
RLS is disabled and all data is returned.
Users can't update their role assignments, and get an error on the RLS Manage page.
For the DAX username function, you continue to receive the username as DOMAIN\USER.
Report authors don't have access to view the report data in Power BI Report Server until they've assigned
themselves roles accordingly after uploading the report.

FAQ
Can I create these roles for Analysis Services data sources?
You can if you imported the data into Power BI Desktop. If you're using a live connection, you can't configure RLS
within the Power BI service. RLS is defined within the Analysis Services model on-premises.
Can I use RLS to limit the columns or measures accessible by my users?
No. If a user has access to a particular row of data, they can see all the columns of data for that row.
Does RLS let me hide detailed data but give access to data summarized in visuals?
No, you secure individual rows of data but users can always see either the details or the summarized data.
Can I add new roles in Power BI Desktop if I already have existing roles and members assigned?
Yes, if you already have existing roles defined and members assigned in Power BI Report Server, you can make
additional roles and republish your report with no effect on your current assignments.

Next steps
What is Power BI Report Server? Administrator handbook
More questions? Try asking the Power BI Community
 Create a paginated report for Power BI Report
Server
2/15/2019 • 3 minutes to read • Edit Online

As the name suggests, paginated reports can run to many pages. They're laid out in a fixed format and offer
precise customization. Paginated reports are .rdl files.
You can store and manage paginated reports in the Power BI Report Server web portal, just as you can in the SQL
Server Reporting Services (SSRS ) web portal. You create and edit them in Report Builder or Report Designer in
SQL Server Data Tools (SSDT), then publish them to either web portal. Then report readers in your organization
can view them in a browser or in a Power BI mobile app on their mobile device.

If you've already created paginated reports in Report Builder or Report Designer, then you're ready to create
paginated reports for Power BI Report Server. If not, here are some quick steps to get you started.

Step 1: Install and start Report Builder

You may already have installed Report Builder to create reports for an SSRS server. You can use the same version
or Report Builder to create reports for Power BI Report Server. If you haven't installed it, the process is easy.
1. In the Power BI Report Server web portal, select New > Paginated Report.

If you don't have Report Builder installed already, it leads you through the installation process now.
2. After it's installed, Report Builder opens to the New Report or Dataset screen.

3. Select the wizard for the kind of report you want to create:
Table or matrix
Chart
Map
Blank
4. Let's start with the Chart wizard.
The Chart wizard walks you the steps of creating a basic chart in a report. From there, you can customize
your report in almost unlimited ways.

Step 2: Go through the Chart wizard

The Chart wizard walks you through the basic steps of creating a visualization in a report.
Paginated reports can connect to a wide variety of data sources, from Microsoft SQL Server and Microsoft Azure
SQL Database to Oracle, Hyperion, and many more. Read about data sources supported by paginated reports.
In the first page in the Chart wizard, Choose a dataset, you can create a dataset or choose a shared dataset on a
server. Datasets return report data from a query on an external data source.
1. Select Browse > select a shared dataset on a server > Open > Next.
 Need to create a dataset? See Create a shared or embedded dataset.
2. Choose a chart type -- in this case, a bar chart.

3. Arrange the fields by dragging them to the Categories, Series, and Values boxes.
4. Select Next > Finish.

Step 3: Design your report

Now you're in Report Design view. Notice the data is placeholder data, not your data.

To view your data, select Run.

 To go back to Design view, select Design.
You can modify the chart you just created, changing the layout, values, legend... really just about anything.
And you can add all sorts of other visualizations: gauges, tables, matrixes, tables, maps, and more. You can add
headers and footers for multiple pages. See the Report Builder tutorials to try them for yourself.

Step 4: Save your report to the report server

When your report is ready, save it to Power BI Report Server.
1. On the File menu, select Save as, and save it to the report server.
2. Now you can view it in the browser.

Next steps
There are many great resources for designing reports in Report Builder and in Report Designer in SQL Server
Data Tools. The Report Builder tutorials are a good place to start.
Report Builder tutorials
What is Power BI Report Server?
More questions? Try asking the Power BI Community
 Enter data directly in a paginated report in Report
Builder (Preview) - Power BI
2/15/2019 • 3 minutes to read • Edit Online

In this article, you learn about a feature in the new version of SQL Server 2016 Report Builder that lets you enter
data directly into an RDL report as an embedded dataset. This feature is similar to Power BI Desktop. You can type
the data directly in a dataset in your report, or paste it from another program like Microsoft Excel. After you've
created a dataset by entering data, you can use it just like you would any other embedded dataset you've created.
Plus you can add more than one table and use one as a filter for the other. This feature is especially useful for
small, static datasets you might need to use in your report, like report parameters.

Prerequisites
To enter data directly in a paginated report, install the new version of Report Builder from the Microsoft
Download Center.
To save your paginated report to the Power BI service, you need a Power BI Pro account and write access to a
workspace in a Power BI Premium capacity.
To save your paginated report to a report server, you need permissions to edit the RsReportServer.config file.

Get started
After you’ve downloaded and installed Report Builder, you follow the same workflow you use to add an embedded
data source and dataset to your report. In the following procedure, under Data Sources you see a new option:
Enter Data. You only need to set up this data source once in a report. After that, you can create multiple tables of
entered data as separate datasets, all using that single data source.
1. In the Report Data pane, select New > Dataset.

2. In the Dataset Properties dialog box, select Use a dataset embedded in my report.
3. Next to Data source, select New.
4. In the Data Source Properties dialog box, select Use a connection embedded in my report.
5. In the Select connection type box, select ENTER DATA > OK.

6. Back in the Dataset Properties dialog box, select Query Designer.

7. In the Query Designer pane, right-click and paste your data in the table.
 8. To set the column names, double-click each NewColumn and type the column name.

9. If the first row contains column headings from the original data, right-click and delete it.
10. By default, the data type for each column is String. To change the data type, right-click the column header >
Change Type, and set it to another data type, such as Date or Float.

11. When you’ve finished creating the table, select OK.

The query that’s generated is the same as you’d see with an XML data source. Under the covers, we’re using
XML as the data provider. We’ve repurposed it to enable this scenario as well.
12. In the Dataset Properties dialog box, select OK.
13. You see your data source and dataset in the Report Data pane.

You can use your dataset as the basis for data visualizations in your report. You can also add another dataset and
use the same data source for it.

Upload the paginated report to the Power BI service

Now that paginated reports are supported in the Power BI service in preview, you can upload your paginated
report to a Premium capacity. See Upload a paginated report for details.

Upload the paginated report to a report server

You can also upload your paginated report to a Power BI Report Server or SQL Server Reporting Services 2016 or
2017 report server. Before you do, you need to add the following item to your RsReportServer.config as an
additional data extension. Back up your RsReportServer.config file before you make the change, in case you run
into any issues.
 <Extension Name="ENTERDATA"
Type="Microsoft.ReportingServices.DataExtensions.XmlDPConnection,Microsoft.ReportingServices.DataExtensions">
<Configuration>
<ConfigName>ENTERDATA</ConfigName>
</Configuration>
</Extension>

After you've edited it, here's what the list of data providers in the config file should look like:

That’s it – you can now publish reports that use this new functionality to your report server.

Next steps
What are paginated reports in Power BI Premium? (Preview )
What is Power BI Report Server?
 Accessing shared datasets as OData feeds in Power BI
Report Server
1/14/2019 • 2 minutes to read • Edit Online

You can access shared datasets from Power BI Desktop with an OData feed.
1. With the OData feed URL, you connect to the OData source.

2. After you bring the data into Power BI Desktop, you can modify it in the Query Editor.

3. Now you can use the data in designing reports.

Be sure to use Advanced Options so you can turn on Open Type Columns and format the columns accordingly in
Power Query to meet your needs.
Read more about connecting to OData feeds in Power BI Desktop.
More questions? Try asking the Power BI Community
 How to configure Power BI report scheduled refresh
1/14/2019 • 2 minutes to read • Edit Online

To refresh data in your Power BI report, a scheduled refresh plan must be created. This is done within the Manage
area of a Power BI report.

Configure data source credentials

Prior to creating a schedule data refresh plan, you need to set the credentials for each data source used in your
Power BI report.
1. In the web portal, right-click on the Power BI report and select Manage.

2. In the left menu, select the Data sources tab.

3. For each data source that appears, choose the type of authentication to use when connecting to that data
source. Enter the appropriate credentials.
Creating a Schedule Refresh Plan
Follow these steps to create a scheduled refresh plan.
1. In the web portal, right-click on the Power BI report and select Manage.

2. In the left menu, select the Scheduled refresh tab.

3. On the Scheduled refresh page, select New scheduled refresh plan.
4. On the New Scheduled Refresh Plan page, enter a description and set a schedule for when you want
your data model to be refreshed.
5. Select Create scheduled refresh plan when done.

Modifying a Schedule Refresh Plan

Modifying a scheduled refresh plan is similar to creating one.
1. In the web portal, right-click on the Power BI report and select Manage.
2. In the left menu, select the Scheduled refresh tab.
3. On the Scheduled refresh page, select Edit beside the refresh plan you want to manage.

4. On the Edit Scheduled Refresh Plan page, enter a description and set a schedule for when you want your
data model to be refreshed.
5. Select Apply when done.
Viewing the status of Schedule Refresh Plan
View the status of a schedule refresh plan in the web portal.
1. In the web portal, right-click on the Power BI report and select Manage.

2. In the left menu, select the Scheduled refresh tab.

3. On the Scheduled refresh page, the right most column displays the status of a plan.

STATUS DESCRIPTION

New Scheduled Refresh Plan The plan has been created but has not ran.

Refreshing The refresh process has started.

Streaming model to Analysis Server Copying the model from the report server catalog
database to the hosted Analysis Services instance.

Refreshing data Refreshing the data within the model.

Removing credentials from the model Removed the credentials used to connect to the data
source from the model.

Saving model to the catalog Refreshing of data is complete and the refreshed model is
being saved back to the report server catalog database.

Completed: Data Refresh Refresh is done.

Error: An error occurred during refresh and is displayed.

The web page must be refreshed to see the current status. The status will not change automatically.

Next steps
To learn more about creating and modifying schedules, see Create, modify, and delete schedules.
For information on how to troubleshoot scheduled refresh, see Troubleshoot scheduled refresh in Power BI Report
Server.
More questions? Try asking the Power BI Community
 Add comments to a report in a report server - Power
BI Report Server
2/15/2019 • 2 minutes to read • Edit Online

You can add comments to reports, including Power BI reports, within the web portal of a report server. The
comments live with the report, and anyone with the right permissions can see the comments for the report. See the
Permissions section below for details.

Add or view comments

1. Open a paginated or Power BI report on a report server.
2. In the upper-right corner, select Comments.

In the Comments pane, you can see any existing comments.

3. Write your comment, then select Post Comment.
 Your comment shows in the pane on the web portal, along with any previous comments. They don't appear
with the report on in the Power BI mobile apps.

TIP
Did you know? You can annotate Power BI reports in the Power BI mobile apps and share the annotated reports with
others.

Permissions
Depending on your permissions, you can:
Not see comments.
See all comments, and post, edit, and delete your own.
See all comments; post, edit, and delete your own; and delete other people’s.

Next steps
What is Power BI Report Server?
More questions? Try asking the Power BI Community
 Install Power BI Report Server
2/28/2019 • 5 minutes to read • Edit Online

Learn how to install Power BI Report Server.

Download
To download Power BI Report Server, go to On-premises reporting with Power BI Report Server, and select
Download free trial.

Before you begin

Before you install Power BI Report Server, we recommend you review the Hardware and Software
Requirements for installing Power BI Report Server.

IMPORTANT
While you can install Power BI Report Server in an environment that has a Read-Only Domain Controller (RODC), Power
BI Report Server needs access to a Read-Write Domain Controller to function properly. If Power BI Report Server only has
access to a RODC, you may encounter errors when trying to administer the service.

Power BI Report Server product key

Power BI Premium
If you have purchased Power BI Premium, within the Premium settings tab of the Power BI admin portal, you
have access to your Power BI Report Server product key. This is only available for Global Admins or users
assigned the Power BI service administrator role.

Selecting Power BI Report Server key displays a dialog contain your product key. You can copy it and use it
with the installation.
SQL Server Enterprise Software Assurance (SA)
If you have a SQL Server Enterprise SA agreement, you can get your product key from the Volume Licensing
Service Center.

Install your report server

Installing Power BI Report Server is straightforward. There are only a few steps to install the files.
You don't need a SQL Server Database Engine server available at the time of install. You will need one to
configure Reporting Services after install.
1. Find the location of PowerBIReportServer.exe and launch the installer.
2. Select Install Power BI Report Server.

3. Choose an edition to install and then select Next.

 You can choose either Evaluation or Developer edition from the drop down.

Otherwise, you can enter a product key for the server that you acquired from either the Power BI service
or the Volume License Service Center. For more information about how to get your product key, see the
Before you begin section.
4. Read and agree to the license terms and conditions and then select Next.

5. You need to have a Database Engine available to store the report server database. Select Next to install
the report server only.
6. Specify the install location for the report server. Select Install to continue.

The default path is C:\Program Files\Microsoft Power BI Report Server.

7. After a successful setup, select Configure Report Server to launch the Reporting Services
Configuration Manager.

Configuring your report server

After you select Configure Report Server in the setup, you're presented with Reporting Services Configuration
Manager. For more information, see Reporting Services Configuration Manager.
You need to create a report server database to complete the initial configuration of Reporting Services. A SQL
Server Database server is required to complete this step.
Creating a database on a different server
If you are creating the report server database on a database server on a different machine, you need to change
the service account for the report server to a credential that is recognized on the database server.
By default, the report server uses the virtual service account. If you try to create a database on a different server,
you may receive the following error on the Applying connection rights step.
System.Data.SqlClient.SqlException (0x80131904): Windows NT user or group '(null)' not found. Check the name
again.

To work around the error, you can change the service account to either Network Service or a domain account.
Changing the service account to Network Service applies rights in the context of the machine account for the
report server.

For more information, see Configure the report server service account .

Windows Service
A windows service is created as part of the installation. It is displayed as Power BI Report Server. The service
name is PowerBIReportServer.

Default URL reservations

URL reservations are composed of a prefix, host name, port, and virtual directory:

PART DESCRIPTION

Prefix The default prefix is HTTP. If you previously installed a Secure

Sockets Layer (SSL) certificate, Setup tries to create URL
reservations that use the HTTPS prefix.
 PART DESCRIPTION

Host name The default host name is a strong wildcard (+). It specifies
that the report server accepts any HTTP request on the
designated port for any host name that resolves to the
computer, including
http://<computername>/reportserver ,
http://localhost/reportserver , or
http://<IPAddress>/reportserver.

Port The default port is 80. If you use any port other than port
80, you have to explicitly add it to the URL when you open
web portal in a browser window.

Virtual directory By default, virtual directories are created in the format of

ReportServer for the Report Server Web service and Reports
for the web portal. For the Report Server Web service, the
default virtual directory is reportserver. For the web portal,
the default virtual directory is reports.

An example of the complete URL string might be as follows:

http://+:80/reportserver , provides access to the report server.
http://+:80/reports , provides access to the web portal.

Firewall
If you are accessing the report server from a remote machine, you want to make sure you have configured any
firewall rules if there is a firewall present.
You need to open up the TCP port that you have configured for your Web Service URL and Web Portal URL. By
default, these are configured on TCP port 80.

Additional configuration
To configure integration with the Power BI service so you can pin report items to a Power BI dashboard, see
Integrate with the Power BI service.
To configure email for subscriptions processing, see E -Mail settings and E -Mail delivery in a report server .
To configure the web portal so you can access it on a report computer to view and manage reports, see
Configure a firewall for report server access and Configure a report server for remote administration .

Next steps
Administrator overview
How to find your report server product key
Install Power BI Desktop optimized for Power BI Report Server
Verify a reporting services installation
Configure the report server service account
Configure report server URLs
Configure a report server database connection
Initialize a report server
Configure SSL connections on a report server
Configure windows service accounts and permissions
Browser support for Power BI Report Server
More questions? Try asking the Power BI Community
 How to find your report server product key
1/14/2019 • 2 minutes to read • Edit Online

Learn how you can find your Power BI Report Server product key to install your server in a production
environment.
https://www.youtube.com/embed/6CQnf-NGtpU?rel=0&showinfo=0
You downloaded Power BI Report Server, and you have a SQL Server Enterprise Software Assurance agreement.
Or, you purchased Power BI Premium. You want to install the server in a production environment, but you need a
product key in order to do that. Where is the product key?
The product key will be in one of two places depending on what you purchased.

Purchased Power BI Premium

If you have purchased Power BI Premium, within the Capacity settings tab of the Power BI admin portal, you will
have access to your Power BI Report Server product key. This will only be available for Global Admins or users
assigned the Power BI service administrator role.

Selecting Power BI Report Server key will display a dialog contain your product key. You can copy it and use it
with the installation.

Purchased Software Assurance agreement

If you have a SQL Server Enterprise SA agreement, you can get your product key from the Volume Licensing
Service Center. Look under the latest service pack, for the latest version of SQL Server. If you don't see it there,
look under the RTM release of the latest SQL Server version.
 NOTE
You need to look under the download section. Not the keys section.

Next steps
Install Power BI Report Server
Install Power BI Desktop optimized for Power BI Report Server
Download Report Builder
Download SQL Server Data Tools (SSDT)
More questions? Try asking the Power BI Community
 Upgrade Power BI Report Server
1/14/2019 • 2 minutes to read • Edit Online

Learn how to upgrade Power BI Report Server.

Download
To download Power BI Report Server, and Power BI Desktop optimized for Power BI Report Server, go to On-
premises reporting with Power BI Report Server.

Before you begin

Before you upgrade a report server, it is recommended that you perform the following steps to back up your report
server.
Backing up the encryption keys
You should backup the encryption keys when you configure a report server installation for the first time. You
should also backup the keys any time you change the identity of the service accounts or rename the computer. For
more information, see Back Up and Restore Reporting Services Encryption Keys.
Backing up the report server databases
Because a report server is a stateless server, all application data is stored in the reportserver and
reportservertempdb databases that run on a SQL Server Database Engine instance. You can backup the
reportserver and reportservertempdb databases using one of the supported methods for backing up SQL
Server databases. Recommendations that are specific to the report server databases include the following:
Use the full recovery model to backup the reportserver database.
Use the simple recovery model to backup the reportservertempdb database.
You can use different backup schedules for each database. The only reason to backup the reportservertempdb
is to avoid having to recreate it if there is a hardware failure. In the event of hardware failure, it is not necessary
to recover the data in reportservertempdb, but you do need the table structure. If you lose
reportservertempdb, the only way to get it back is to recreate the report server database. If you recreate the
reportservertempdb, it is important that it have the same name as the primary report server database.
For more information about backup and recovery of SQL Server relational databases, see Back Up and Restore of
SQL Server Databases.
Backing up the configuration files
Power BI Report Server uses configuration files to store application settings. You should backup the files when you
first configure the server and after you deploy any custom extensions. Files to back up include:
config.json
RSHostingService.exe.config
Rsreportserver.config
Rssvrpolicy.config
Reportingservicesservice.exe.config
Web.config for the Report Server ASP.NET applications
Machine.config for ASP.NET

Upgrade the report server

Upgrading Power BI Report Server is straight forward. There are only a few steps to install the files.
1. Find the location of PowerBIReportServer.exe and launch the installer.
2. Select Upgrade Power BI Report Server.

3. Read and agree to the license terms and conditions and then select Upgrade.

4. After a successful upgrade, you can select Configure Report Server to launch the Reporting Services
Configuration Manager, or select Close to exit the installer.
Upgrade Power BI Desktop
After the report server is upgrade, you will want to make sure that any Power BI report authors upgrade to the
version of Power BI Desktop optimized for Power BI Report Server that matches the server.

Next steps
Administrator overview
Install Power BI Desktop optimized for Power BI Report Server
Verify a reporting services installation
Configure the report server service account
Configure report server URLs
Configure a report server database connection
Initialize a report server
Configure SSL connections on a report server
Configure windows service accounts and permissions
Browser support for Power BI Report Server
More questions? Try asking the Power BI Community
 Migrate a report server installation
1/21/2019 • 2 minutes to read • Edit Online

Learn how to migrate your existing SQL Server Reporting Services (SSRS ) instance to an instance of Power BI
Report Server.
Migration is defined as moving application data files to a new Power BI Report Server instance. The following are
common reasons why you might migrate your installation:
You want to move from SQL Server Reporting Services to Power BI Report Server

NOTE
There is not an inplace upgrade from SQL Server Reporting Services to Power BI Report Server. A migration is
necessary.

You have a large-scale deployment or update requirements

You're changing the hardware or topology of your installation
You encounter an issue that blocks upgrade

Migrating to Power BI Report Server from SSRS (Native mode)

Migrating from an SSRS (Native mode) instance to Power BI Report Server consists of a few steps.

NOTE
SQL Server 2008 Reporting Services and later are supported for migration.
 Backup database, application, and configuration files
Back up the encryption key
Clone your report server database hosting your reports
Install Power BI Report Server. If you're using the same hardware, you can install Power BI Report Server on
the same server as the SSRS instance. For more information on installing Power BI Report Server, see Install
Power BI Report Server.

NOTE
The instance name for the Power BI Report Server will be PBIRS.

Configure the report server using Report Server Configuration Manager and connect to the cloned database.
Perform any cleanup needed for the SSRS (Native mode) instance

Migration to Power BI Report Server from SSRS (SharePoint-integrated

mode)
Migrating from an SSRS (SharePoint-integrated mode) to Power BI Report Server is not as straight forward as
native mode. While these steps provide some guidance, you may have other files and assets within SharePoint that
you need to manage outside of these steps.

You need to migrate the specific report server content from SharePoint to your Power BI Report Server. You need
to have already installed Power BI Report Server somewhere in your environment. For more information on
installing Power BI Report Server, see Install Power BI Report Server.
If you want to copy the report server content from your SharePoint environment to Power BI Report Server, you
need to use tools such as rs.exe to copy the content. Below is a sample of what the script would be to copy report
server content from SharePoint to Power BI Report Server.

NOTE
The sample script should work against SharePoint 2010 and later and SQL Server 2008 Reporting Services and later.

Sample script
 Sample Script
rs.exe
-i ssrs_migration.rss -e Mgmt2010
-s http://SourceServer/_vti_bin/reportserver
-v st="sites/bi" -v f="Shared Documents“
-u Domain\User1 -p Password
-v ts=http://TargetServer/reportserver
-v tu="Domain\User" -v tp="Password"

Migrating from one Power BI Report Server to another

Migrating from one Power BI Report Server is the same process as migrating from SSRS (Native-mode).

Backup database, application, and configuration files

Back up the encryption key
Clone your report server database hosting your reports
Install Power BI Report Server. You can't install Power BI Report Server on the same server as the one you're
migrating from. For more information on installing Power BI Report Server, see Install Power BI Report Server.

NOTE
The instance name for the Power BI Report Server will be PBIRS.

Configure the report server using Report Server Configuration Manager and connect to the cloned database.
Perform any cleanup needed for the old Power BI Report Server installation.

Next steps
Administrator overview
Install Power BI Report Server
Script with the rs.exe Utility and the Web Service
More questions? Try asking the Power BI Community
 Configure Kerberos to use Power BI reports
2/13/2019 • 9 minutes to read • Edit Online

https://www.youtube.com/embed/vCH8Fa3OpQ0?showinfo=0
Learn how to configure your report server for Kerberos authentication to data sources used within your Power BI
reports for a distributed environment.
Power BI Report Server includes the ability to host Power BI reports. Many data sources are supported by your
report server. While this article focuses specifically on SQL Server Analysis Services, you can use the concepts and
apply that to other data sources such as SQL Server.
You can install Power BI Report Server, SQL Server and Analysis Services on a single machine and everything
should work without additional configuration. This is great for a test environment. You may hit errors if you have
these services installed on separate machines which is called a distributed environment. In this environment, you
are required to use Kerberos authentication. There is configuration required to implement this.
Specifically, you will need to configure constrained delegation. You may have Kerberos configured in your
environment but it may not be configured for constrained delegation.

Error running report

If your report server is not configured properly, you may receive the following error.

Something went wrong.

We couldn’t run the report because we couldn’t connect to its data source. The report or data source might not
be configured correctly.

Within Technical details, you will see the following message.

We couldn’t connect to the Analysis Services server. The server forcibly closed the connection. To connect as
the user viewing the report, your organization must have configured Kerberos constrained delegation.

Configuring Kerberos constrained delegation

There are several items that need to be configured in order for Kerberos constrained delegation to work. This
includes Service Principal Names (SPN ) and delegation settings on service accounts.
 NOTE
In order to configure SPNs and delegation settings, you need to be a domain administrator.

We will need to configure, or validate, the following.

1. Authentication type within Report Server config.
2. SPNs for the report server service account.
3. SPNs for the Analysis Services service.
4. SPNs for the SQL Browser service on the Analysis Services machine. This is for named instances only.
5. Delegation settings on the report server service account.

Authentication type within Report Server configuration

We need to configure the authentication type for the report server to allow for Kerberos constrained delegation.
This is done within the rsreportserver.config file. The default location for this file is
C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer .

Within the rsreportserver.config file, you will want to fine the Authentication/AuthenticationTypes section.
We want to make sure that RSWindowsNegotiate is listed and the first in the list of authentication types. It should
look similar to the following.

<AuthenticationTypes>
<RSWindowsNegotiate/>
<RSWindowsNTLM/>
</AuthenticationTypes>

If you had to change the configuration file, you will want to stop and start the report server to make sure the
changes take effect.
For more information, see Configure Windows Authentication on the Report Server.

SPNs for the report server service account

Next, we need to make sure that the report server has valid SPNs available. This is based on the service account
that is configured for the report server.
Virtual Service Account or Network Service
If your report server is configured for the Virtual Service Account or Network Service account, you should not
have to do anything. These are in the context of the machine account. The machine account will have HOST SPNs
by default. These will cover the HTTP service and will be used by the report server.
If you are using a virtual server name, one that is not same as the machine account, the HOST entries will not
cover you and you will need to manually add the SPNs for the virtual server host name.
Domain user account
If your report server is configured to use a domain user account, you will have to manually create HTTP SPNs on
that account. This can be done using the setspn tool that comes with Windows.

NOTE
You will need domain admin rights in order to create the SPN.
It is recommended to create two SPNs. One with the NetBIOS name and the other with the fully qualified domain
name (FQDN ). The SPN will be in the following format.

<Service>/<Host>:<port>

Power BI Report Server will use a Service of HTTP. For HTTP SPNs you will not list a port. The service we are
interested in here is HTTP. The host of the SPN will be the name you use in a URL. Typically, this is the machine
name. If you are behind a load balancer, this may be a virtual name.

NOTE
You can verify the URL by either looking at what you enter into the address bar of the browser, or you can look in the Report
Server Configuration Manager on the Web Portal URL tab.

If your machine name is ContosoRS, your SPNs would be the following.

SPN TYPE SPN

Fully Qualified Domain Name (FQDN) HTTP/ContosoRS.contoso.com

NetBIOS HTTP/ContosoRS

Location of SPN
So, where do you put the SPN? The SPN will be placed on whatever you are using for your service account. If you
are using Virtual Service Account or Network Service, this will be the machine account. Although we mentioned
before you should only need to do this for a virtual URL. If you are using a domain user for the report server
service account, then you will place the SPN on that domain user account.
For example, if we are using the Network Service account and our machine name is ContosoRS, we would place
the SPN on ContosoRS.
If we are using a domain user account of RSService, we would place the SPN on RSService.
Using SetSPN to add the SPN
We can use the SetSPN tool to add the SPN. We will follow the same example as above with the Machine account
and the domain user account.
Placing the SPN on a machine account, for both the FQDN and NetBIOS SPN, would look similar to the following
if we were using a virtual URL of contosoreports.

Setspn -a HTTP/contosoreports.contoso.com ContosoRS

Setspn -a HTTP/contosoreports ContosoRS

Placing the SPN on a domain user account, for both the FQDN and NetBIOS SPN, would look similar to the
following if you were using the machine name for the host of the SPN.

Setspn -a HTTP/ContosoRS.contoso.com RSService

Setspn -a HTTP/ContosoRS RSService

SPNs for the Analysis Services service

The SPNs for Analysis Services are similar to what we did with Power BI Report Server. The format of the SPN is a
little different if you have a named instance.
For Analysis Services, we use a Service of MSOLAPSvc.3. We will specify the instance name for the port location
on the SPN. The host part of the SPN will either be the machine name, or the Cluster virtual name.
An example of an Analysis Services SPN would look like the following.

TYPE FORMAT

Default instance MSOLAPSvc.3/ContosoAS.contoso.com

MSOLAPSvc.3/ContosoAS

Named instance MSOLAPSvc.3/ContosoAS.contoso.com:INSTANCENAME

MSOLAPSvc.3/ContosoAS:INSTANCENAME

Placement of the SPN is also similar to what was mentioned with Power BI Report Server. It is based on the
service account. If you are using Local System or Network Service, you will be in the context of the machine
account. If you are using a domain user account for the Analysis Services instance, you will place the SPN on the
domain user account.
Using SetSPN to add the SPN
We can use the SetSPN tool to add the SPN. For this example, the machine name will be ContosoAS.
Placing the SPN on a machine account, for both the FQDN and NetBIOS SPN, would look similar to the following.

Setspn -a MSOLAPSvc.3/ContosoAS.contoso.com ContosoAS

Setspn -a MSOLAPSvc.3/ContosoAS ContosoAS

Placing the SPN on a domain user account, for both the FQDN and NetBIOS SPN, would look similar to the
following.

Setspn -a MSOLAPSvc.3/ContosoAS.contoso.com OLAPService

Setspn -a MSOLAPSvc.3/ContosoAS OLAPService

SPNs for the SQL Browser service

If you have an Analysis Services named instance, you also need to make sure you have an SPN for the browser
service. This is unique to Analysis Services.
The SPNs for SQL Browser are similar to what we did with Power BI Report Server.
For SQL Browser, we use a Service of MSOLAPDisco.3. We will specify the instance name for the port location on
the SPN. The host part of the SPN will either be the machine name, or the Cluster virtual name. You do not have
to specify anything for the instance name or port.
An example of an Analysis Services SPN would look like the following.

MSOLAPDisco.3/ContosoAS.contoso.com
MSOLAPDisco.3/ContosoAS

Placement of the SPN is also similar to what was mentioned with Power BI Report Server. The difference here is
that SQL Browser always runs under the Local System account. This means that the SPNs will always go on the
machine account.
Using SetSPN to add the SPN
 We can use the SetSPN tool to add the SPN. For this example, the machine name will be ContosoAS.
Placing the SPN on the machine account, for both the FQDN and NetBIOS SPN, would look similar to the
following.

Setspn -a MSOLAPDisco.3/ContosoAS.contoso.com ContosoAS

Setspn -a MSOLAPDisco.3/ContosoAS ContosoAS

For more information, see An SPN for the SQL Server Browser service is required.

Delegation settings on the report server service account

The last part that we have to configure are the delegation settings on the report server service account. There are
different tools you can use to perform these steps. For the purposes of this document, we will stick with Active
Directory Users and Computers.
You will need to start by going to the properties of the report server service account within Active Directory Users
and Computers. This will either be the machine account, if you used Virtual Service Account or Network Service, or
it will be a domain user account.
We will want to configure constrained delegation with protocol transiting. With constrained delegation, you need
to be explicit with which services we want to delegate to. We will go and add both the Analysis Services service
SPN and the SQL Browser SPN to the list that Power BI Report Server can delegate to.
1. Right click on the report server service account and select Properties.
2. Select the Delegation tab.
3. Select Trust this computer for delegation to specified services only.
4. Select Use any authentication protocol.
5. Under the Services to which this account can present delegated credentials: select Add.
6. In the new dialog, select Users or Computers.
7. Enter the service account for the Analysis Services service and select Ok.
8. Select the SPN that you created. It will begin with MSOLAPSvc.3 . If you added both the FQDN and the
NetBIOS SPN, it will select both. You may only see one.
9. Select OK. You should see the SPN in the list now.
10. Optionally, you can select Expanded to show both the FQDN and NetBIOS SPN in the list.
11. Select Add again. We will add the SQL Browser SPN now.
12. In the new dialog, select Users or Computers.
13. Enter the Machine name for the machine the SQL Browser service is on and select Ok.
14. Select the SPN that you created. It will begin with MSOLAPDisco.3 . If you added both the FQDN and the
NetBIOS SPN, it will select both. You may only see one.
15. Select Ok. The dialog should look similar to the following if you checked Expanded.
16. Select Ok.
17. Reboot the Power BI Report Server.

Running a Power BI Report

After all of the above configuration is in place, your report should display properly.

While this configuration should work in most cases, with Kerberos, there can be different configuration depending
on your environment. If the report will still not load, you will want to reach out to your domain administrator to
investigate further or contact support.

Next steps
Administrator overview
Install Power BI Report Server
More questions? Try asking the Power BI Community
 Configure Power BI iOS mobile app access to a
report server remotely
2/15/2019 • 2 minutes to read • Edit Online

In this article, learn how to use your organization's MDM tool to configure Power BI iOS mobile app access to a
report server. To configure it, IT administrators create an app configuration policy with the required information to
be pushed to the app.
With the report server connection already configured, Power BI iOS mobile app users can connect to their
organization's report server more easily.

Create the app configuration policy in MDM tool

As admin, here are the steps you follow in Microsoft Intune to create the app configuration policy. The steps and
experience of building the app configuration policy may be different in other MDM tools.
1. Connect your MDM tool.
2. Create and name a new app configuration policy.
3. Choose which users to distribute this app configuration policy to.
4. Create key-value pairs.
The following table spells out the pairs.

KEY TYPE DESCRIPTION

com.microsoft.powerbi.mobile.ServerUR String Report Server URL

L Should start with http/https

com.microsoft.powerbi.mobile.ServerUs String [optional]

ername The username to use for connecting the
server.
If one does not exist, the app prompts
the user to type the username for the
connection.

com.microsoft.powerbi.mobile.ServerDis String [optional]

playName Default value is “Report server”
A friendly name used in the app to
represent the server
 KEY TYPE DESCRIPTION

com.microsoft.powerbi.mobile.OverrideS Boolean Default value is True

erverDetails When set to “True”, it overrides any
Report Server definition already in the
mobile device. Existing servers that are
already configured are deleted.
Override set to True also prevents the
user from removing that configuration.
Set to “False” adds the pushed values,
leaving any existing settings.
If the same server URL is already
configured in the mobile app, the app
leaves that configuration as is. The app
doesn't ask the user to reauthenticate
for the same server.

Here's an example of setting the configuration policy using Intune.

End users connecting to a report server

Say you publish the app configuration policy for a distribution list. When users and devices on that distribution list
start the iOS mobile app, they have the following experience.
1. They see a message that their mobile app is configured with a report server, and tap Sign in.

2. On the Connect to server page, the report server details already filled in. They tap Connect.
3. They type a password to authenticate, then tap Sign in.

Now they can view and interact with KPIs and Power BI reports stored on the report server.

Next steps
Administrator overview
Install Power BI Report Server
More questions? Try asking the Power BI Community
 Configure your report server to host Excel workbooks
using Office Online Server (OOS)
2/13/2019 • 5 minutes to read • Edit Online

In addition to viewing Power BI reports in the web portal, Power BI Report Server can host Excel workbooks by
using Office Online Server (OOS ). Your report server becomes a single location to publish and view self-service
Microsoft BI content.

Prepare server to run Office Online Server

Perform these procedures on the server that will run Office Online Server. This server must be Windows Server
2012 R2 or Windows Server 2016. Windows Server 2016 requires Office Online Server April 2017 or later.
Install prerequisite software for Office Online Server
1. Open the Windows PowerShell prompt as an administrator and run this command to install the required
roles and services.
Windows Server 2012 R2:

Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-
Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-
Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-
Includes,InkandHandwritingServices,NET-Framework-Features,NET-Framework-Core,NET-HTTP-Activation,NET-
Non-HTTP-Activ,NET-WCF-HTTP-Activation45,Windows-Identity-Foundation,Server-Media-Foundation

Windows Server 2016:

Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-
Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-
Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-
Includes,NET-Framework-Features,NET-Framework-45-Features,NET-Framework-Core,NET-Framework-45-Core,NET-
HTTP-Activation,NET-Non-HTTP-Activ,NET-WCF-HTTP-Activation45,Windows-Identity-Foundation,Server-Media-
Foundation

If prompted, restart the server.

2. Install the following software:
 .NET Framework 4.5.2
Visual C++ Redistributable Packages for Visual Studio 2013
Visual C++ Redistributable for Visual Studio 2015
Microsoft.IdentityModel.Extention.dll
Install Office Online Server
If you plan to use any Excel Online features that utilize external data access (such as Power Pivot), note that Office
Online Server must reside in the same Active Directory forest as its users as well as any external data sources that
you plan to access using Windows-based authentication.
1. Download Office Online Server from the Volume Licensing Service Center (VLSC ). The download is located
under those Office products on the VLSC portal. For development purposes, you can download OOS from
MSDN subscriber downloads.
2. Run Setup.exe.
3. On the Read the Microsoft Software License Terms page, select I accept the terms of this agreement
and select Continue.
4. On the Choose a file location page, select the folder where you want the Office Online Server files to be
installed (for example, C:\Program Files\Microsoft Office Web Apps*) and select Install Now. If the folder
you specified doesn’t exist, Setup creates it for you.
We recommend that you install Office Online Server on the system drive.
5. When Setup finishes installing Office Online Server, select Close.
Install language packs for Office Web Apps Server (optional)
Office Online Server Language Packs let users view web-based Office files in multiple languages.
To install the language packs, follow these steps.
1. Download the Office Online Server Language Packs from the Microsoft Download Center.
2. Run wacserverlanguagepack.exe.
3. In the Office Online Server Language Pack Wizard, on the Read the Microsoft Software License Terms
page, select I accept the terms of this agreement and select Continue.
4. When Setup finishes installing Office Online Server, select Close.

Deploy Office Online Server

Create the Office Online Server farm (HTTPS )
Use the New -OfficeWebAppsFarm command to create a new Office Online Server farm that consists of a single
server, as shown in the following example.

New-OfficeWebAppsFarm -InternalUrl "https://server.contoso.com" -ExternalUrl "https://wacweb01.contoso.com" -

CertificateName "OfficeWebApps Certificate"

Parameters
–InternalURL is the fully qualified domain name (FQDN ) of the server that runs Office Online Server, such as
http://servername.contoso.com .
–ExternalURL is the FQDN that can be accessed on the Internet.
–CertificateName is the friendly name of the certificate.
Create the Office Online Server farm (HTTP)
Use the New -OfficeWebAppsFarm command to create a new Office Online Server farm that consists of a single
server, as shown in the following example.

New-OfficeWebAppsFarm -InternalURL "http://servername" -AllowHttp

Parameters
–InternalURL is the name of the server that runs Office Online Server, such as http://servername .
–AllowHttp configures the farm to use HTTP.
Verify that the Office Online Server farm was created successfully
After the farm is created, details about the farm are displayed in the Windows PowerShell prompt. To verify that
Office Online Server is installed and configured correctly, use a web browser to access the Office Online Server
discovery URL, as shown in the following example. The discovery URL is the InternalUrl parameter you specified
when you configured your Office Online Server farm, followed by /hosting/discovery, for example:

<InternalUrl>/hosting/discovery

If Office Online Server works as expected, you should see a Web Application Open Platform Interface Protocol
(WOPI)-discovery XML file in your web browser. The first few lines of that file should resemble the following
example:

<?xml version="1.0" encoding="utf-8" ?>

<wopi-discovery>
<net-zone name="internal-http">
<app name="Excel" favIconUrl="<InternalUrl>/x/_layouts/images/FavIcon_Excel.ico" checkLicense="true">
<action name="view" ext="ods" default="true" urlsrc="<InternalUrl>/x/_layouts/xlviewerinternal.aspx?
<ui=UI_LLCC&><rs=DC_LLCC&>" />
<action name="view" ext="xls" default="true" urlsrc="<InternalUrl>/x/_layouts/xlviewerinternal.aspx?
<ui=UI_LLCC&><rs=DC_LLCC&>" />
<action name="view" ext="xlsb" default="true" urlsrc="<InternalUrl>/x/_layouts/xlviewerinternal.aspx?
<ui=UI_LLCC&><rs=DC_LLCC&>" />
<action name="view" ext="xlsm" default="true" urlsrc="<InternalUrl>/x/_layouts/xlviewerinternal.aspx?
<ui=UI_LLCC&><rs=DC_LLCC&>" />

Configure Excel workbook maximum size

The maximum file size for all files in Power BI Report Server is 100 MB. To stay in sync with that, you need to
manually set this in OOS.

Set-OfficeWebAppsFarm -ExcelWorkbookSizeMax 100

Using EffectiveUserName with Analysis Services

To allow for live connections to Analysis Services, for connections within an Excel workbook that make use of
EffectiveUserName. For OOS to make use of EffectiveUserName, you will need to add the machine account of the
OOS server as an administrator for the Analysis Services instance. Management Studio for SQL Server 2016 or
later is needed to do this.
Only embedded Analysis Services connections are currently supported within an Excel workbook. The user's
account will need to have permission to connect to Analysis Services as the ability to proxy the user is not
available.
Run the following PowerShell commands on the OOS Server.
 Set-OfficeWebAppsFarm -ExcelUseEffectiveUserName:$true
Set-OfficeWebAppsFarm -ExcelAllowExternalData:$true
Set-OfficeWebAppsFarm -ExcelWarnOnDataRefresh:$false

Configure a Power Pivot instance for data models

Installing an Analysis Services Power Pivot mode instance lets you work with Excel workbooks that are using
Power Pivot. Make sure that the instance name is POWERPIVOT. Add the machine account of the OOS server as
an administrator, for the Analysis Services Power Pivot mode instance. Management Studio for SQL Server 2016
or later is needed to do this.
For OOS to use the Power Pivot mode instance, run the following command.

New-OfficeWebAppsExcelBIServer -ServerId <server_name>\POWERPIVOT

If you did not already allow external data, from the Analysis Services step above, run the following command.

Set-OfficeWebAppsFarm -ExcelAllowExternalData:$true

Firewall considerations
To avoid firewall issues, you may need to open the ports 2382 and 2383. You can also add the msmdsrv.exe, for the
Power Pivot instance, as an application firewall wall policy.

Configure Power BI Report Server to use the OOS Server

On the General page of Site settings, enter the OOS discovery url. The OOS discovery url is the InternalUrl,
used when deploying the OOS server, followed by /hosting/discovery. For example,
http://servername/hosting/discovery , for HTTP. And, https://server.contoso.com/hosting/discovery for HTTPS.

To get to Site settings, select the gear icon in the upper right and select Site settings.
Only a user with the System Administrator role will see the Office Online Server discovery url setting.

After you enter the discovery url, and select Apply, selecting an Excel workbook, within the web portal, should
display the workbook within the web portal.
Limitations and considerations
You will have read only capability with workbooks.

Next steps
Administrator overview
Install Power BI Report Server
Download Report Builder
Download SQL Server Data Tools (SSDT)
More questions? Try asking the Power BI Community
 Develop with the REST APIs for Power BI Report
Server
3/4/2019 • 3 minutes to read • Edit Online

Power BI Report Server support Representational State Transfer (REST) APIs. The REST APIs are service
endpoints that support a set of HTTP operations (methods), which provide create, retrieve, update, or delete access
for resources within a report server.
The REST API provides programmatic access to the objects in a Power BI Report Server catalog. Examples of
objects are folders, reports, KPIs, data sources, datasets, refresh plans, subscriptions, and more. Using the REST
API, you can, for example, navigate the folder hierarchy, discover the contents of a folder, or download a report
definition. You can also create, update, and delete objects. Examples of working with objects are upload a report,
execute a refresh plan, delete a folder, and so on.

NOTE
If you’re interested in viewing or deleting personal data, please review Microsoft's guidance in the Windows Data Subject
Requests for the GDPR site. If you’re looking for general information about GDPR, see the GDPR section of the Service Trust
portal.

Components of a REST API request/response

A REST API request/response pair can be separated into five components:
The request URI, which consists of: {URI-scheme} :// {URI-host} / {resource-path} ? {query-string} .
Although the request URI is included in the request message header, we call it out separately here because
most languages or frameworks require you to pass it separately from the request message.
URI scheme: Indicates the protocol used to transmit the request. For example, http or https .
URI host: Specifies the domain name or IP address of the server where the REST service endpoint is
hosted, such as myserver.contoso.com .
Resource path: Specifies the resource or resource collection, which may include multiple segments used
by the service in determining the selection of those resources. For example:
CatalogItems(01234567-89ab-cdef-0123-456789abcdef)/Properties can be used to get the specified
properties for the CatalogItem.
Query string (optional): Provides additional simple parameters, such as the API version or resource
selection criteria.
HTTP request message header fields:
A required HTTP method (also known as an operation or verb), which tells the service what type of
operation you are requesting. Reporting Services REST APIs support DELETE, GET, HEAD, PUT, POST,
and PATCH methods.
Optional additional header fields, as required by the specified URI and HTTP method.
Optional HTTP request message body fields, to support the URI and HTTP operation. For example, POST
operations contain MIME -encoded objects that are passed as complex parameters. For POST or PUT
operations, the MIME -encoding type for the body should be specified in the Content-type request header
as well. Some services require you to use a specific MIME type, such as application/json .
HTTP response message header fields:
 An HTTP status code, ranging from 2xx success codes to 4xx or 5xx error codes. Alternatively, a service-
defined status code may be returned, as indicated in the API documentation.
Optional additional header fields, as required to support the request's response, such as a Content-type
response header.
Optional HTTP response message body fields:
MIME -encoded response objects are returned in the HTTP response body, such as a response from a
GET method that is returning data. Typically, these objects are returned in a structured format such as
JSON or XML, as indicated by the Content-type response header.

API documentation
A modern REST API calls for modern API documentation. The REST API is built on the OpenAPI specification
(a.k.a. the swagger specification) and documentation is available on SwaggerHub. Beyond documenting the API,
SwaggerHub helps generate a client library in the language of choice – JavaScript, TypeScript, C#, Java, Python,
Ruby, and more.

Testing API calls

A tool for testing HTTP request/response messages is Fiddler. Fiddler is a free web debugging proxy that can
intercept your REST requests, making it easy to diagnose the HTTP request/ response messages.

Next steps
Review the available APIs over on SwaggerHub.
Samples are available on GitHub. The sample includes an HTML5 app built on TypeScript, React, and webpack
along with a PowerShell example.
More questions? Try asking the Power BI Community
 Capacity planning guidance for Power BI Report Server
1/14/2019 • 7 minutes to read • Edit Online

Power BI Report Server is a self-service BI and enterprise reporting solution that customers can deploy on their premises, behind their firewall. It
combines the interactive report capability of Power BI Desktop with the on-premises server platform of SQL Server Reporting Services. With heavy and
growing usage of analytics and reporting within enterprises, budgeting the hardware infrastructure and software licenses required to scale to an
enterprise user base can be a challenge. This paper aims to offer guidance on capacity planning for Power BI Report Server by sharing results of
numerous load test executions of various workloads against a report server. While organizations’ reports, queries, and usage patterns vary widely, the
results presented in this paper, along with the actual tests used and a detailed description of how they were executed, serve as a reference point for
anyone in the early-stage planning process of deploying Power BI Report Server.

Executive summary
We executed two different types of workloads against Power BI Report Server; each workload consisted of rendering different types of reports as well as
performing various web portal operations.
In “Power BI Report Heavy” workload, the most frequently executed operation (i.e. the operation executed 60% of the time) was rendering Power BI
reports.
In “Paginated Report Heavy” workload, the most frequently executed operation was rendering paginated reports.
Under a four-server topology of Power BI Report Server and the expectation that no more than 5% of users will access a report server at any one time,
the following table describes the maximum number of users Power BI Report Server can handle with at least 99% reliability.

WORKLOAD 8 CORE/32 GB RAM 16 CORE/64 GB RAM

Power BI Report Heavy (>60%) 1,000 users 3,000 users

Paginated (RDL) Report Heavy (>60%) 2,000 users 3,200 users

In each run, the most overwhelmed resource was CPU. Due to this, increasing the number of cores to Power BI Report Server would yield a higher gain
in the reliability of the system than increasing the amount of memory or hard-disk space.

Test methodology
The testing topology used was based on Microsoft Azure Virtual Machines instead of vendor-specific physical hardware. All machines were hosted in US
regions. This reflects the general trend of hardware virtualization both on-premises and in the public cloud.
Power BI Report Server topology
The Power BI Report Server deployment consisted of the following virtual machines:
Active Directory Domain Controller: this was needed by SQL Server Database Engine, SQL Server Analysis Services, and Power BI Report Server to
securely authenticate all requests.
SQL Server Database Engine and SQL Server Analysis Services: this was where we stored all the databases for the reports to consume when we
rendered them.
Power BI Report Server
Power BI Report Server Database. The report server database is hosted on a different machine than Power BI Report Server so that it does not need
to compete with SQL Server Database Engine for memory, CPU, network, and disk resources.

See Appendix 1.1 Power BI Report Server Topology and Appendix 1.2 Power BI Report Server Virtual Machine Configuration for a thorough
configuration of each virtual machine used in the topology.
Tests
The tests used in the load test runs are publicly available in a GitHub project called Reporting Services LoadTest. This tool allows users to study the
performance, reliability, scalability and recoverability characteristics of SQL Server Reporting Services and Power BI Report Server. This project consists
of four groups of test cases:
Tests simulating rendering Power BI reports,
Tests simulating rendering mobile reports,
Tests simulating rendering small and large paginated reports, and
Tests simulating performing various types of web portal operations.
All tests were written to perform an end-to-end operation (such as rendering a report, creating a new data source, etc.). They accomplish this by making
one or more web requests to the report server (via APIs). In the real world, a user may need to perform a few intermediate operations to complete one
of these end-to-end operations. For example, to render a report a user will need to go to the web portal, navigate to the folder where the report is, then
click the report to render it. While tests don’t perform all the operations needed to accomplish an end-to-end task, they still impose most of the load that
Power BI Report Server would experience. You can learn more about the different types of reports used as well as the variety of operations performed by
exploring the GitHub project.
Workloads
There are 2 workload profiles used in testing: Power BI Report Heavy and Paginated Report Heavy. The table below describes the distribution of
requests executed against the Report Server.

ACTIVITY POWER BI REPORT HEAVY, FREQUENCY OF OCCURRENCE PAGINATED REPORT HEAVY, FREQUENCY OF OCCURRENCE

Rendering Power BI reports 60% 10%

Rendering paginated (RDL) reports 30% 60%

Rendering mobile reports 5% 20%

Web portal operations 5% 10%

User load
For each test run, tests were executed based on the frequency specified in one of the two workloads. Tests started with 20 concurrent user requests to
the report server. The user load was then gradually increased until reliability dropped below the 99% target.

Results
Concurrent user capacity
As stated earlier, tests started with 20 concurrent users making requests to the report server. The number of concurrent users was then gradually
increased until 1% of all requests were failing. The results in the following table tell us the number of concurrent user requests that the server would be
able to handle under peak load with a failure rate of less than 1%.

WORKLOAD 8 CORE/32 GB 16 CORE/64 GB

Power BI Report Heavy 50 concurrent users 150 concurrent users

Paginated Report Heavy 100 concurrent users 160 concurrent users

Total user capacity

At Microsoft, we have a production deployment of Power BI Report Server that several teams used. When we analyze actual usage of this environment,
we observe that the number of concurrent users at any given time (even during daily peak load) doesn’t tend to exceed 5% of the total user base. Using
this 5% concurrency ratio as a benchmark, we extrapolated the total user base Power BI Report Server could handle with 99% reliability.

WORKLOAD 8 CORE/32 GB 16 CORE/64 GB

Power BI Report Heavy 1,000 users 3,000 users

Paginated Report Heavy 2,000 users 3,200 users

View results
Select a report to view the results of the load test.

WORKLOAD 8 CORE/32 GB 16 CORE/64 GB

Power BI Report Heavy View - 8 core View - 16 core

Paginated Report Heavy View - 8 core View - 16 core

https://msit.powerbi.com/view?
r=eyJrIjoiMDhhNGY4NGQtNGRhYy00Yzk4LTk2MzAtYzFlNWI5NjBkMGFiIiwidCI6IjcyZjk4OGJmLTg2ZjEtNDFhZi05MWFiLTJkN2NkMDExZGI0NyIsImMiOjV9
https://msit.powerbi.com/view?
r=eyJrIjoiNDBiODk1OGUtYTAyOC00MzVhLThmZmYtNzVjNTFjNzMwYzkwIiwidCI6IjcyZjk4OGJmLTg2ZjEtNDFhZi05MWFiLTJkN2NkMDExZGI0NyIsImMiOjV9
https://msit.powerbi.com/view?
r=eyJrIjoiNDFiZWYzMTktZGIxNS00MzcwLThjODQtMmJkMGRiZWEzNjhlIiwidCI6IjcyZjk4OGJmLTg2ZjEtNDFhZi05MWFiLTJkN2NkMDExZGI0NyIsImMiOjV9
https://msit.powerbi.com/view?
r=eyJrIjoiOTU0YjJkYTgtNDg4Yy00NzlhLWIwMGYtMzg4YWI2MjNmOTZjIiwidCI6IjcyZjk4OGJmLTg2ZjEtNDFhZi05MWFiLTJkN2NkMDExZGI0NyIsImMiOjV9

Summary
For each load test run, CPU was the most overwhelmed resource at the point of peak load on the Power BI Report Server machine. Due to this, the first
resource that should be increased is the number of cores. Alternately, you can consider scaling out by adding more servers hosting Power BI Report
Server in your topology.
The results presented in this paper were derived from executing a specific set of reports consuming a specific set of data, repeated in a specific way. It’s a
useful reference point, but keep in mind that your usage will depend on your reports, queries, usage patterns and deployment of your Power BI Report
Server.

Appendix
1 Topology
1.1 Power BI Report Server Topology
To focus solely on Power BI Report Server behavior under different configurations, the VM configuration for each type of machine (except for the
machine hosting Power BI Report Server) was fixed. Each machine was provisioned according to the second-generation (v2) D Series machines with
Premium Storage Disks. You can find detailed information about each VM size under the “General Purpose” section on
https://azure.microsoft.com/pricing/details/virtual-machines/windows/.

VIRTUAL MACHINE TYPE PROCESSOR MEMORY AZURE VM SIZE

Active Directory Domain Controller 2 Cores 7 GB Standard_DS2_v2

SQL Server Database Engine and 16 Cores 56 GB Standard_DS5_v2

Analysis Services

Report Server Database 16 Cores 56 GB Standard_DS5_v2

1.2 Power BI Report Server Virtual Machine Configuration

Different configurations of processor and memory were used for the Virtual Machine hosting Power BI Report Server. Unlike the other VMs, this
machine was provisioned according to the third-generation (v3) D Series Machines with Premium Storage Disks. You can find detailed information
about this VM size under the “General Purpose” section on https://azure.microsoft.com/pricing/details/virtual-machines/windows/.

VIRTUAL MACHINE PROCESSOR MEMORY AZURE VM SIZE

Power BI Report Server (Small) 8 Cores 32 GB Standard_D8S_v3

Power BI Report Server (Large) 16 Cores 64 GB vStandard_D16S_v3

2 Run the LoadTest tool

If you’d like to run the Reporting Services LoadTest tool against your or a Microsoft Azure deployment of Power BI Report Server, follow these steps.
1. Clone the Reporting Services LoadTest project from GitHub (https://github.com/Microsoft/Reporting-Services-LoadTest).
2. In the project directory, you will find a solution file called RSLoadTests.sln. Open this file in Visual Studio 2015 or later.
3. Determine whether you want to run this tool against your deployment of Power BI Report Server or against a deployment of Power BI Report Server
in Microsoft Azure. If you are going to run it against your own deployment, go to step 5.
4. Follow the instructions listed on https://github.com/Microsoft/Reporting-Services-LoadTest#create-a-sql-server-reporting-services-load-
environment-in-azure to create a Power BI Report Server environment in Azure.
5. Once you finish deploying the environment, follow the instructions listed on https://github.com/Microsoft/Reporting-Services-LoadTest#load-test-
execution to run the tests.
More questions? Try asking the Power BI Community
 What are On-Premises Data Gateways?
3/5/2019 • 2 minutes to read • Edit Online

A Power BI gateway is software that you install within an on-premises network; it facilitates access to data in that
network. It's like a gatekeeper that listens for connection requests, and grants them only when a users' requests
meet certain criteria. This lets organizations keep databases and other data sources on their on-premises networks,
yet securely use that on-premises data in Power BI reports and dashboards.
A gateway can be used for a single data source or multiple data sources. The following diagram shows a basic
view, with the gateway handling requests from the cloud for three on-premises computers. We'll expand on this
later in the article.

Types of gateways
Power BI offers two gateways, each for a different scenario:
On-premises data gateway (personal mode) – allows one user to connect to sources, and can’t be
shared with others. Can only be used with Power BI. This gateway is well-suited to scenarios where you’re
the only person who creates reports, and you don't need to share the data sources with others.
On-premises data gateway – allows multiple users to connect to multiple on-premises data sources. Can
be used by Power BI, PowerApps, Flow, Azure Analysis Services, and Azure Logic apps, all with a single
gateway installation. This gateway is well-suited to more complex scenarios with multiple people accessing
multiple data sources.

Using a gateway
There are four main steps for using a gateway:
1. Install the gateway on a local computer, using the appropriate mode
2. Add users to the gateway, so they can access on-premises data sources
3. Connect to data sources, so they can be used in reports and dashboards
4. Refresh on-premises data, so Power BI reports are up to date
You can install a stand-alone gateway or add a gateway to a cluster, which is recommended for high availability.

How gateways work

The gateway you install runs as a Windows service, On-premises data gateway. This local service is registered
with the Gateway Cloud Service through Azure Service Bus. The following diagram shows the flow between on-
premises data and the cloud services that use the gateway.
Queries and data flow:
1. A query is created by the cloud service with the encrypted credentials for the on-premises data source. It's then
sent to a queue for the gateway to process.
2. The gateway cloud service analyzes the query and pushes the request to the Azure Service Bus. Power BI
manages the Service Bus for you, so there are no additional costs or configuration steps required.
3. The on-premises data gateway polls the Azure Service Bus for pending requests.
4. The gateway gets the query, decrypts the credentials, and connects to the data sources with those credentials.
5. The gateway sends the query to the data source for execution.
6. The results are sent from the data source, back to the gateway, and then onto the cloud service and your server.

Next steps
Install the on-premises data gateway
More questions? Try the Power BI Community
 Tutorial: Connect to on-premises data in SQL Server
1/14/2019 • 4 minutes to read • Edit Online

An on-premises data gateway is software that you install within an on-premises network; it facilitates access to
data in that network. In this tutorial you build a report in Power BI Desktop based on sample data imported from
SQL Server. You then publish the report to the Power BI service, and configure a gateway so the service can access
the on-premises data. This access means the service can refresh the data to keep the report up to date.
In this tutorial, you learn how to:
Create a report from data in SQL Server
Publish the report to the Power BI Service
Add SQL Server as a gateway data source
Refresh the data in the report
If you're not signed up for Power BI, sign up for a free trial before you begin.

Prerequisites
Install Power BI Desktop
Install SQL Server on a local computer
Install an on-premises data gateway on the same local computer (in production, it would typically be a different
computer)

Set up sample data

You start by adding sample data to SQL Server, so you can use that data in the rest of the tutorial.
1. In SQL Server Management Studio (SSMS ), connect to your instance of SQL Server and create a test
database.

CREATE DATABASE TestGatewayDocs

2. In the database you created, add a table and insert data.

 USE TestGatewayDocs

CREATE TABLE Product (

SalesDate DATE,
Category VARCHAR(100),
Product VARCHAR(100),
Sales MONEY,
Quantity INT
)

INSERT INTO Product VALUES('2018-05-05','Accessories','Carrying Case',9924.60,68)

INSERT INTO Product VALUES('2018-05-06','Accessories','Tripod',1350.00,18)
INSERT INTO Product VALUES('2018-05-11','Accessories','Lens Adapter',1147.50,17)
INSERT INTO Product VALUES('2018-05-05','Accessories','Mini Battery Charger',1056.00,44)
INSERT INTO Product VALUES('2018-05-06','Accessories','Telephoto Conversion Lens',1380.00,18)
INSERT INTO Product VALUES('2018-05-06','Accessories','USB Cable',780.00,26)
INSERT INTO Product VALUES('2018-05-08','Accessories','Budget Movie-Maker',3798.00,9)
INSERT INTO Product VALUES('2018-05-09','Digital video recorder','Business Videographer',10400.00,13)
INSERT INTO Product VALUES('2018-05-10','Digital video recorder','Social Videographer',3000.00,60)
INSERT INTO Product VALUES('2018-05-11','Digital','Advanced Digital',7234.50,39)
INSERT INTO Product VALUES('2018-05-07','Digital','Compact Digital',10836.00,84)
INSERT INTO Product VALUES('2018-05-08','Digital','Consumer Digital',2550.00,17)
INSERT INTO Product VALUES('2018-05-05','Digital','Slim Digital',8357.80,44)
INSERT INTO Product VALUES('2018-05-09','Digital SLR','SLR Camera 35mm',18530.00,34)
INSERT INTO Product VALUES('2018-05-07','Digital SLR','SLR Camera',26576.00,88)

3. Select the data from the table to verify it.

SELECT * FROM Product

Build and publish a report

Now that you have sample data to work with, you connect to SQL Server in Power BI Desktop and build a report
based on that data. You then publish the report to the Power BI service.
1. In Power BI Desktop, on the Home tab, select Get Data > SQL Server.
2. Under Server enter your server name, and under Database enter "TestGatewayDocs". Select OK.
3. Verify your credentials, then select Connect.
4. Under Navigator, select the Product table, then select Load.

5. In the Power BI Desktop Report view, in the Visualizations pane, select the Stacked column chart.

6. With the column chart selected in the report canvas, in the Fields pane select the Product and Sales fields.
 The chart should now look like the following.

Notice that SLR Camera is the current sales leader. This will change when you update data and refresh the
report later in this tutorial.
7. Save the report with the name "TestGatewayDocs.pbix".
8. On the Home tab select Publish > My Workspace > Select. Sign in to the Power BI service if you're
asked to do so.

9. On the Success screen, select Open 'TestGatewayDocs.pbix' in Power BI.

Add SQL Server as a gateway data source
In Power BI Desktop, you connect directly to SQL Server, but the Power BI service requires a gateway to act as a
bridge. Now you add your instance of SQL Server as a data source for the gateway you created in a previous
article (listed under Prerequisites).

1. In the upper-right corner of the Power BI service, select the gear icon > Manage gateways.

2. Select Add data source, and enter "test-sql-source" for Data Source Name.

3. Select a Data Source Type of SQL Server, then enter other values as shown.
OPTION VALUE

Data Source Name test-sql-source

Data Source Type SQL Server

Server The name of your SQL Server instance (must be identical

to what you specified in Power BI Desktop)

Database TestGatewayDocs

Authentication Method Windows

Username The account, such as [email protected], you use to

connect to SQL Server

Password The password for the account you use to connect to SQL
Server
4. Select Add. You see Connection Successful when the process succeeds.

You can now use this data source to include data from SQL Server in your Power BI dashboards and
reports.

Configure and use data refresh

You have a report published to the Power BI service, and the SQL Server data source configured. With these in
place, you now make a change in the Product table, and that change flows through the gateway to the published
report. You also configure scheduled refresh to handle any future changes.
1. In SSMS, update data in the Product table.

UPDATE Product
SET Sales = 32508, Quantity = 252
WHERE Product='Compact Digital'

2. In the Power BI Service, in the left navigation pane, select My Workspace.

3. Under Datasets, for the TestGatewayDocs dataset select more (. . .) > Refresh now.

4. Select My Workspace > Reports > TestGatewayDocs. See how the update flowed through, and the sales
leader is now Compact Digital.
5. Select My Workspace > Reports > TestGatewayDocs. Select more (. . .) > Schedule refresh.
6. Under Schedule refresh, set refresh to On, then select Apply. The dataset is refreshed daily by default.

Clean up resources
If you don't want to use the sample data anymore, run DROP DATABASE TestGatewayDocs in SSMS. If you don't want
to use the SQL Server data source, remove the data source.

Next steps
In this tutorial, you learned how to:
Create a report from data in SQL Server
Publish the report to the Power BI Service
Add SQL Server as a gateway data source
Refresh the data in the report
Advance to the next article to learn more
Manage a Power BI gateway
 Guidance for deploying a data gateway for Power BI
1/14/2019 • 8 minutes to read • Edit Online

This article provides guidance and considerations for deploying a data gateway in your network environment. A
gateway is software that facilitates access to data that resides on a private, on-premises network, for subsequent
use in a cloud service like Power BI. This article walks you through the deployment, and provides guidance for, the
On-premises data gateway setup.

For more about On-premises data gateway, including a link to install it, take a look at the blog post.

Installation considerations for the On-premises data gateway

Before getting too far into the details of installation and deployment, there are a handful of considerations you
should keep in mind. The following sections describe important things to keep in mind.
Number of users
The number of users consuming a report that's using the gateway is an important metric in deciding where to
install the gateway. Here are some questions to consider:
Are users using these reports at different times of the day?
What types of connections are they using (DirectQuery or Import)?
Are all users using the same report?
If users are all accessing a given report at the same time each day, you'll want to make sure you install the gateway
on a machine that's capable of handling all those requests (see following sections for performance counters and
minimum requirements that can help you determine this).
There is a constraint in Power BI that allows only one gateway per report, so even if a report is based on multiple
data sources, all such data sources must go through a single gateway. However, if a dashboard is based on multiple
reports, you can use a dedicated gateway for each contributing report, and thereby distribute the gateway load
among those multiple reports that contribute to that single dashboard.
Connection type
Power BI offers two types of connections: DirectQuery and Import. Not all data sources support both
connection types, and many reasons may contribute to choosing one over the other, such as security requirements,
performance, data limits, and data model sizes. You can learn more about connection type and supported data
sources in the list of available data source types section of the On-premises data gateway article.
Depending on which type of connection are use, gateway usage can be different. For example, you should try to
separate DirectQuery data sources from Scheduled Refresh data sources whenever possible (assuming they're
in different reports and can be separated). Doing so prevents the gateway from having thousands of DirectQuery
requests queued up, at the same time as the morning's scheduled refresh of a large size data model that's used for
the company's main dashboard. Here's what to consider for each:
For Scheduled Refresh: depending on your query size and the number of refreshes occurring per day, you can
choose to stay between the recommended minimum hardware requirements or upgrade to a higher
performance machine. If a given query is not folded, transformations occur on the gateway machine, and as
such, the gateway machine benefits from having more available RAM.
For DirectQuery: a query is be sent each time any user opens the report or looks at data. So if you anticipate
more than 1,000 users accessing the data concurrently, you'll want to make sure your computer has robust and
capable hardware components. More CPU cores will result in better throughput for a DirectQuery connection.
The requirements for a machine on which you install an On-premises data gateway are the following:
Minimum:
.NET 4.5 Framework
64-bit version of Windows 7 / Windows Server 2008 R2 (or later)
Recommended:
8 Core CPU
8 GB Memory
64-bit version of Windows 2012 R2 (or later)
Location
The location of the gateway installation can have significant impact on your query performance, so try to make
sure your gateway, data source locations, and the Power BI tenant are as close as possible to each other to
minimize network latency. To determine your Power BI tenant location, in the Power BI service select the ? icon in
the upper-right corner, and then select About Power BI.
Monitoring gateways
There are a few tools that you can use to monitor the use and performance of your installed gateways.
Performance counters
There are many performance counters that can be used to evaluate and assess activity occurring on the gateway.
The counters can help you understand whether you have large volume of activities by the specific type, which may
prompt you to deploy a new gateway.

NOTE
These counters will not capture specific task duration time.

The gateway counter, in addition to your machine's counters, provide you with an idea of how much load your
machine is handling, and can provide an indication of whether the server resource capacity is becoming stretched
or exceeded.
These counters can be accessed from Windows Performance Monitor, and can be consumed by any reporting
tools you use for this purpose. For a detailed walk-through of how to use the gateway performance monitor with
Power BI, take a look at the following community-create blog post.
Monitor On-premises data gateways
Logs
Configuration and service logs provide another dimension on what's happening with your gateway. Always check
your gateway logs when your connection is not working as expected, as not all error messages are surfaced on the
Power BI service.
An easy way to view all the log files on your local machine is to use the Export Logs button on the On-premises
data gateway when you re-open the gateway after the initial installation is complete, and then select Diagnostics
> Export Logs.
Additional logging
By default the gateway performs basic logging. If you're investigating gateway issues, and need more information
about query connection details, you can temporarily enable verbose logging to gather additional log information.
To do this, in the installed gateway select Diagnostics > Additional logging.
Enabling this setting likely will increase the log size significantly, based on gateway usage. It's recommended that
once you're done reviewing the logs, you disable Additional logging. It's not recommended to leave this setting
enabled during normal gateway usage.

Network configuration
The gateway creates an outbound connection to the Azure Service Bus. The gateway communicates on the
following outbound ports:
TCP 443 (default)
5671
5672
9350 thru 9354
The gateway does not require inbound ports. All required ports are listed in the above list.
It is recommended that you whitelist the IP addresses, for your data region, in your firewall. You can download list
of IP addresses, which are found in the Microsoft Azure Datacenter IP list. That list is updated weekly. The gateway
will communicate with Azure Service Bus using the specified IP address, along with the fully qualified domain
name (FQDN ). If you're forcing the gateway to communicate using HTTPS, the gateway strictly uses FQDN only,
and no communication will occur using IP addresses.
Forcing HTTPS communication with Azure Service Bus
You can force the gateway to communicate with the Azure Service Bus by using HTTPS, instead of direct TCP.
Doing so will slightly reduce performance. You can also force the gateway to communicate with the Azure Service
Bus by using HTTPS by using the gateway's user interface (beginning with the March 2017 release of the
gateway).
To do so, in the gateway select Network, then turn the Azure Service Bus connectivity mode On.
Additional guidance
This section provides additional guidance for deploying and managing gateways.
Avoid having a single point of failure. If possible, distribute your on-premises data sources across several
gateways; in this case, if one machine becomes unavailable, you'll still be able to refresh portions of your data,
and not lose that functionality completely.
The gateway cannot be installed on a domain controller, so don't plan or try to do so.
Don't install a gateway on a computer that may be turned off, go into the sleep mode, or not be connected to
the Internet (for example, a laptop computer), because the gateway can't run under any of those circumstances.
Avoid installing a gateway on a wireless network, since performance might suffer over a wireless network.
Gateway Recovery
You can recover your existing gateway, or move it to a new machine, using the recovery key. The recovery key is
provided to the user who installs the gateway, and it cannot be changed later. The recovery key is used for both
data encryption and gateway recovery.
To recover your gateway, make sure you're an admin on the gateway, make sure you know the gateway name,
ensure you have the correct recovery key, and that you have a new machine available with similar performance
characteristics.
After you sign in, select the Migrate an existing gateway option. Next, you need to choose the gateway you'd
like to recover or migrate, and finally provide the recovery key and hit configure. Once that step is done, the old
gateway will be replaced by the new gateway, and the new gateway will inherit its name and all data sources
previously configured. All data sources will now go through the new machine, without the need to re-publish
anything. Automatic failover is not yet supported, but it is a feature that the gateway team is actively considering.
Administrators
You can find a list of gateway administrators in the Power BI service. When signed into the Power BI service,
select Settings (the gear icon) > Manage Gateways > Gateway UI.
From there, you can select a gateway and see the list of gateway administrators. The administrators listed can
access, recover, and delete the gateway. They can also add and delete data sources in the gateway. To make sure all
administrators in the organization have access to all gateways in their group, the following is recommended:
Create an AAD security group and add other users to it, then add this security group to the list of the respective
gateway administrators. This ensures that more than one person has access to the gateway in case of a failure,
or when you need to recover or migrate the gateway. This also gives other administrators a view of what
gateways are being used in their groups, and which data sources exist on each gateway.

Next steps
Configuring proxy settings
Troubleshooting the On-premises data gateway
On-premises data gateway FAQ
More questions? Try the Power BI Community
 On-premises data gateway FAQ
1/14/2019 • 7 minutes to read • Edit Online

General
Question: What is the actual Windows service called?
Answer: The gateway is called On-premises data gateway service in Services
Question: What are the requirements for the gateway?
Answer: Take a look at the requirements section of the main gateway article.
Question: What data sources are supported with the gateway?
Answer: See the data sources table in the main gateway article.
Question: Do I need a gateway for cloud data sources like Azure SQL Database?
Answer: No! The service will be able to connect to that data source without a gateway.
Question: Are there any inbound connections to the gateway from the cloud?
Answer: No. The gateway uses outbound connections to Azure Service Bus.
Question: What if I block outbound connections? What do I need to open?
Answer: See the list of ports and hosts that the gateway uses.
Question: Does the gateway have to be installed on the same machine as the data source?
Answer: No. The gateway will connect to the data source using the connection information that was provided.
Think of the gateway as a client application in this sense. It will just need to be able to connect to the server name
that was provided.
Question: What is the latency for running queries to a data source from the gateway? What is the best
architecture?
Answer: It is recommended to have the gateway as close to the data source as possible to avoid network latency. If
you can install the gateway on the actual data source, it will minimize the latency introduced. Consider the data
centers as well. For example, if your service is making use of the West US data center, and you have SQL Server
hosted in an Azure VM, you will want to have the Azure VM in West US as well. This will minimize latency and
avoid egress charges on the Azure VM.
Question: Are there any requirements for network bandwidth?
Answer: It is recommended to have good throughput for your network connection. Every environment is different
and this is also dependent on the amount of data being sent. Using ExpressRoute could help to guarantee a level of
throughput between on-premises and the Azure data centers.
You can use the 3rd party Azure Speed Test app to help gauge what your throughput is.
Question: Can the gateway Windows service run with an Azure Active Directory account?
Answer: No. The Windows service needs to have a valid Windows account. By default it will run with the Service
SID, NT SERVICE\PBIEgwService.
Question: How are results sent back to the cloud?
Answer: This is done by way of the Azure Service Bus. For more information, see how it works.
Question: Where are my credentials stored?
Answer: The credentials you enter for a data source are stored encrypted in the gateway cloud service. The
credentials are decrypted at the gateway on-premises.
Question: Can I place the gateway in a perimeter network (also known as DMZ, demilitarized zone, and screened
subnet)?
Answer: The gateway requires connectivity to the data source. If the data source is not accessible in your
perimeter network, the gateway may not be able to connect to it. For example, your SQL Server may not be in
your perimeter network. And, you cannot connect to your SQL Server from the perimeter network. If you placed
the gateway in your perimeter network, it would not be able to reach the SQL Server.
Question: Is it possible to force the gateway to use HTTPS traffic with Azure Service Bus instead of TCP?
Answer: Yes. Although, this will greatly reduce performance. You will want to modify the
Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file. You will want to change the value from
AutoDetect to Https . This file is located, by default, at C:\Program Files\On-premises data gateway.

Question: Do I need to whitelist the Azure Datacenter IP list? Where do I get the list?
Answer: If you are blocking outbound IP traffic, you may need to whitelist the Azure Datacenter IP list. Currently,
the gateway will communicate with Azure Service Bus using the IP address in addition to the fully qualified
domain name. The Azure Datacenter IP list is updated weekly. You can download the Microsoft Azure Datacenter
IP list.

<setting name="ServiceBusSystemConnectivityModeString" serializeAs="String">

<value>Https</value>
</setting>

High Availability/Disaster Recovery

Question: Are there any plans for enabling high availability scenarios with the gateway?
Answer: Yes, this is an area of active investment for the Power BI team. Please stay tuned to the Power BI blog for
further updates about this feature.
Question: What options are available for disaster recovery?
Answer: You can use the recovery key to restore or move a gateway. When you install the gateway, supply the
recovery key.
Question: What is the benefit of the recovery key?
Answer: It provides a way to migrate or recover your gateway settings. This is also used for disaster recovery.

Troubleshooting
Question: Where are the gateway logs located?
Answer: See the tools section of the troubleshooting article.
Question: How can I see what queries are being sent to the on-premises data source?
Answer: You can enable query tracing. This will include the queries being sent. Remember to change it back to the
original value when done troubleshooting. Having query tracing enabled will cause the logs to be larger.
You can also look at tools your data source has for tracing queries. For example, for SQL Server and Analysis
Services you can use Extended Events or SQL Profiler.

Analysis Services
Question: Can I use msdmpump.dll to create custom effective username mappings for Analysis Services?
Answer: No. This is not supported at this time.
Question: Can I use the gateway to connect to a multidimensional (OLAP ) instance.
Answer: Yes! The On-premises data gateway supports live connections to both Analysis Services Tabular and
Multidimensional models.
Question: What if I install the gateway on a computer in a different domain from my on-premises server that uses
Windows authentication?
Answer: No guarantees here. It all depends on the trust relationship between the two domains. If the two different
domains are in a trusted domain model, then the gateway might be able to connect to the Analysis Services server
and the effective user name can be resolved. If not, you may encounter a login failure.
Question: How can I find out what effective username is being passed to my on-premises Analysis Services
server?
Answer: We answer this in the troubleshooting article.
Question: I have 25 databases in Analysis Services, is there a way to have them all enabled for the gateway at
once?
Answer: No. This is on the roadmap, but we don’t have a timeframe.

Administration
Question: Can I have more than one admin for a gateway?
Answer: Yes! When you manage a gateway, you can go to the administrator’s tab to add additional admins.
Question: Does the gateway admin need to be an admin on the machine where the gateway is installed?
Answer: No. The gateway admin is used to manage the gateway from within the service.
Question: Can I prevent users in my organization from creating a gateway?
Answer: No. This is on the roadmap, but we don’t have a timeframe.
Question: Can I get usage and statistics information of the gateways in my organization?
Answer: No. This is on the roadmap, but we don’t have a timeframe.

Power BI
Question: Do I need to upgrade the personal gateway? Answer: No, you can keep using the personal gateway for
Power BI.
Question: How often are tiles in a dashboard, in Power BI, refreshed when connected through the On-premises
data gateway?
Answer: About ten minutes. DirectQuery connections are just that. This doesn’t mean that a tile issues a query to
your on-premises server, and shows new data, every ten minutes.
Question: Can I upload Excel workbooks with Power Pivot data models that connect to on-premises data sources?
Do I need a gateway for this scenario?
Answer: Yes, you can upload the workbook. And, no, you don’t need a gateway. But, because the data will reside in
the Excel data model, reports in Power BI based on the Excel workbook will not be live. In order to refresh reports
in Power BI, you’d have to re-upload an updated workbook each time. Or, use the gateway with scheduled refresh.
Question: If users share dashboards that has a DirectQuery connection, will those other users be able to see the
data even though they might not have the same permissions.
Answer: For a dashboard connected to Analysis Services, users will only see the data they have access to. If the
users do not have the same permissions, they will not be able to see any data. For other data sources, all users will
share the credentials entered by the admin for that data source.
Question: Why can't I connect to my Oracle server?
Answer: You may need to install the Oracle client and configure the tnsnames.ora file with the proper server
information in order to connect to your Oracle server. This is a separate install outside of the gateway. For more
information, see Installing the Oracle Client.
Question: Will the gateway work with ExpressRoute?
Answer: Yes. For more information about ExpressRoute and Power BI, see Power BI and ExpressRoute.
Question: I'm using R scripts. Is that supported? Answer: R scripts are supported only for personal mode.

Next steps
On-premises data gateway
On-premises data gateway in-depth
Troubleshooting the On-premises data gateway
More questions? Try the Power BI Community
 Install a gateway for Power BI
1/14/2019 • 2 minutes to read • Edit Online

A Power BI gateway is software that you install within an on-premises network; it facilitates access to data in that
network. As described in the overview, you can install a gateway in personal mode or standard mode
(recommended). In standard mode, you can install a stand-alone gateway or add a gateway to a cluster, which is
recommended for high availability. In this article, we show you how to install a standard gateway, then add
another gateway to create a cluster.
If you're not signed up for Power BI, sign up for a free trial before you begin.

Download and install a gateway

The gateway runs on the computer where you install it, so ensure that you install on a computer that is always on.
For better performance and reliability, we recommend that the computer is on a wired network, rather than a
wireless one.

1. In the Power BI service in the upper right corner, select the download icon > Data Gateway.

2. On the download page, select the DOWNLOAD GATEWAY button.

3. Select Next.

4. Select On-premises data gateway (recommended) > Next.

5. Keep the default install path, and accept the terms > Install.

6. Enter the account you use to sign in to Power BI > Sign in.
 The gateway is associated with your Power BI account, and you manage gateways from within the Power
BI service. You're now signed in to your account.
7. Select Register a new gateway on this computer > Next.

8. Enter a name for the gateway (must be unique across the tenant) and a recovery key. You need this key if
you ever want to recover or move your gateway. Select Configure.

Notice the option Add to an existing gateway cluster. We'll use this option in the next section of the
article.
9. Review the information in the final window. Notice that the gateway is available for Power BI, and also
PowerApps and Flow, because I use the same account for all three. Select Close.
Now you've successfully installed a gateway, you can add another gateway to create a cluster.

Add another gateway to create a cluster

A cluster allows gateway administrators to avoid having a single point of failure for on-premises data access. If the
primary gateway is unavailable, data requests are routed to the second gateway that you add, and so on. You can
install only one standard gateway on a computer, so you must install the second gateway for the cluster on a
different computer. This makes sense because you want redundancy in the cluster.
High availability gateway clusters require the November 2017 update to On-premises data gateway, or later.
1. Download the gateway to a different computer, and install it.
2. After you've signed in to your Power BI account, register the gateway. Select Add to an existing cluster.
Under Available gateway clusters, select the first gateway you installed (the primary gateway), and enter
the recover key for that gateway. Select Configure.
Next steps
Manage a Power BI gateway
More questions? Try the Power BI Community
 Manage a Power BI on-premises gateway
2/15/2019 • 5 minutes to read • Edit Online

After you install a Power BI data gateway, you manage it based on your requirements. In this topic, you learn
how to: add and remove data sources and users; restart a gateway; and migrate, restore, take over, and remove a
gateway.
You can manage a gateway through the Manage gateways area of the Power BI service, in the gateway app on
your local computer, and with PowerShell scripts. This article focuses on the Power BI service.
If you've just installed a gateway, we recommend that you next add a data source, and then add users so they can
access the data source.

Manage data sources

Power BI supports many on-premises data sources, and each has its own requirements. A gateway can be used
for a single data source or multiple data sources. For this example, we'll show you how to add SQL Server as a
data source, but the steps are similar for other data sources.
Add a data source
1. In the upper-right corner of the Power BI service, select the gear icon > Manage gateways.

2. Either select a gateway > Add data source, or go to Gateways > Add data source.

3. Select the Data Source Type.

4. Enter information for the data source. For this example, it's Server, Database, and other information.

5. For SQL Server, you would choose an Authentication Method of Windows or Basic (SQL
 Authentication). If you choose Basic, enter the credentials for your data source.
6. Under Advanced settings, optionally configure the privacy level) for your data source (does not apply to
DirectQuery).

7. Select Add. You see Connection Successful if the process succeeds.

You can now use this data source to include data from SQL Server in your Power BI dashboards and reports.
Remove a data source
You can remove a data source if you're no longer using it. Be aware that removing a data source breaks any
dashboards and reports that rely on that data source.
To remove a data source, go to the data source then select Remove.

Manage users and administrators

After you add a data source to a gateway, you give users and security groups access to the specific data source
(not the entire gateway). The data source users list controls only who is allowed to publish reports that include
data from the data source. Report owners can create dashboards, content packs, and apps, and then share those
with other users.
You can also give users and security groups administrative access to the gateway.
Add users to a data source
1. In the upper-right corner of the Power BI service, select the gear icon > Manage gateways.
2. Select the data source where you want add users.
3. Select Users, and enter a user from your organization who you want to grant access to the selected data
source. In the following screen, you can see that I'm adding Maggie and Adam.

4. Select Add, and the added member shows up in the box.

And that’s all there is to it. Remember that you need to add users to each data source to which you want to grant
access. Each data source has a separate list of users, and you must add users to each data source separately.
Remove users from a data source
On the Users tab for the data source, you can remove users and security groups that use this data source.
Add and remove administrators
On the Administrators tab for the gateway, add and remove users (or security groups) that can administer the
gateway.

Manage a gateway cluster

Once you create a cluster of two or more gateways, all gateway management operations, such as adding a data
source or granting administrative permissions to a gateway, apply to all gateways that are part of the cluster.
When administrators use the Manage gateways menu item, found under the gear icon in the Power BI
service, they see the list of registered clusters or individual gateways, but do not see the individual gateway
instances that are members of the cluster.
All new Scheduled Refresh requests and DirectQuery operations are automatically routed to the primary
instance of a given gateway cluster. If the primary gateway instance is not online, the request is routed to another
gateway instance in the cluster.

Share a gateway
You can't share a gateway per se, but you can add administrators to the gateway, and you can add users to the
gateway's data sources.
After you install a gateway, you are by default the administrator of that gateway. As shown earlier, you can add
other people as administrators. These administrators can add data sources, configure, and remove the gateway.
You can also assign users to the data sources you create under each of your gateways. Users can then use those
data sources to refresh Power BI reports. They can't, however, change any of the data sources or the gateway
settings.

Migrate, restore, or take over a gateway

Run the gateway installer on the computer where you want to migrate, restore, or take over the gateway.
1. Download the gateway and install it.
2. After you've signed in to your Power BI account, register the gateway. Select Migrate, restore or take
over an existing gateway > Next.

3. Select from the available clusters and gateways, and enter the recover key for the selected gateway. Select
Configure.
Restart a gateway
The gateway runs as a Windows service. Like any Windows service, there multiple ways to start and stop it. Here
is how you can do it from the command prompt.
1. On the machine where the gateway is running, launch a command prompt with Administrator privileges
2. Enter net stop PBIEgwService to stop the service.
3. Enter net start PBIEgwService to restart the service.

Remove a gateway
You can remove a gateway if you're no longer using it. But be aware that removing a gateway deletes all the data
sources under it. This in turn breaks any dashboards and reports that rely on those data sources.

1. In the upper-right corner of the Power BI service, select the gear icon > Manage gateways.
2. Select the gateway > Remove

Next steps
Guidance for deploying a data gateway
More questions? Try the Power BI Community
 Manage your data source - Analysis Services
1/14/2019 • 11 minutes to read • Edit Online

Once you have installed the On-premises data gateway, you will need to add data sources that can be used with
the gateway. This article will look at how to work with gateways and data sources. You can use the Analysis
Services data source either for scheduled refresh or for live connections.
https://www.youtube.com/embed/ownIGbcRAAU

Download and install the gateway

You can download the gateway from the Power BI service. Select Downloads > Data Gateway, or by going to
the gateway download page.

Limitations of Analysis Services live connections

You can use a live connection against tabular or multidimensional instances.

SERVER VERSION REQUIRED SKU

2012 SP1 CU4 or later Business Intelligence and Enterprise SKU

2014 Business Intelligence and Enterprise SKU

2016 Standard SKU or higher

Cell level Formatting and translation features are not supported.

Actions and Named Sets are not exposed to Power BI, but you can still connect to multidimensional cubes that
also contain Actions or Named sets and create visuals and reports.

Add a gateway
To add a gateway, simply download and install the gateway on a server in your environment. After you have
installed the gateway, it will show in the lists of gateways under Manage gateways.
 NOTE
Manage gateways will not show up until you are the admin of at least one gateway. This can happen either by being
added as an admin or you installing and configuring a gateway.

Remove a gateway
Removing a gateway will also delete any data sources under that gateway. This will also break any dashboards
and reports that rely on those data sources.

1. Select the gear icon in the upper-right corner > Manage gateways.
2. Gateway > Remove

Add a data source

You can add a data source by either selecting a gateway and click Add data source, or go to Gateway > Add
data source.

You can then select the Data Source Type from the list. Select Analysis Services if you are connecting to either a
Multidimensional or Tabular server.
You will then want to fill in the information for the data source which includes the Server and the Database.
The Username and Password that you enter will be used by the gateway to connect to the Analysis Services
instance.

NOTE
The Windows account you enter must have Server Administrator permissions for the instance you are connecting to. If this
account’s password is set to expire, users could get a connection error if the password isn’t updated for the data source. For
more information, see the main On-premises data gateway article to learn more about how credentials are stored.
You can click Add after you have everything filled in. You can now use this data source for scheduled refresh, or
live connections, against an Analysis Services instance that is on premises. You will see Connection Successful if it
succeeded.

Advanced settings
You can configure the privacy level for your data source. This controls how data can be mashed up. This is only
used for scheduled refresh. It does not apply to live connections. Learn more
Usernames with Analysis Services
Each time a user interacts with a report connected to Analysis Services, the effective username is passed to the
gateway and then onto your on-premises Analysis Services server. The email address, that you sign into Power BI
with, is what we will pass to Analysis Services as the effective user. This is passed in the connection property
EffectiveUserName. This email address should match a defined UPN within the local Active Directory Domain.
The UPN is a property of an Active Directory account. That Windows account then needs to be present in an
Analysis Services role. If a match cannot be found, in Active Directory, the login will not be successful. Learn
more
You can also map your Power BI sign in name with a local directory UPN. Learn more
https://www.youtube.com/embed/Qb5EEjkHoLg
How do I tell what my UPN is?
You may not know what your UPN is, and you may not be a domain administrator. You can use the following
command from your workstation to find out the UPN for your account.

whoami /upn

The result will look similar to an email address, but this is the UPN that is on your domain account. If you are
using an Analysis Services data source for live connections, and If this doesn't match the email address you sign
into Power BI with, you may want to look at how to Map user names.

Map user names

https://www.youtube.com/embed/eATPS -c7YRU
You can map user names for Analysis Services in two different ways:
1. Manual user re-mapping
2. On-premises Active Directory Property Lookup to remap AAD UPNs to Active Directory users (AD Lookup
mapping)
While it's possible to perform manual mapping using the second approach, doing so would be time consuming
and difficult to maintain; it's especially difficult when pattern matching doesn't suffice--such as when domain
names are different between AAD and on-premises AD, or when user account names are different between AAD
and AD. As such, manual mapping with the second approach is not recommended.
We describe these two approaches, in order, in the following two sections
Manual user name re -mapping
For Analysis Services data sources, you can configure custom User Principal Name (UPN ) rules. This will help
you if your Power BI service login names do not match your local directory UPN. For example, if you sign into
Power BI with [email protected], but your local directory UPN is [email protected], you can configure a
mapping rule to have [email protected] passed to Analysis Services.
To get to the UPN Mapping screen, do the following.
1. Go to the gear icon and select Manage Gateways.
2. Expand the gateway that contains the Analysis Services data source. Or, if you haven't created the Analysis
Services data source, you can do that at this point.
3. Select the data source and then select the Users tab.
4. Select Map user names.
You will then see options to add rules as well as test for a given user.

NOTE
You may inadvertently change a user that you didn't intend to. For example, if your Replace (original value) is
@contoso.com and your With (New name) is @contoso.local, all users with a sign in that contains @contoso.com will
then be replaced with @contoso.local. Also, if your Replace (Original name) is [email protected] and your With (New
name) is [email protected], a user with the sign in of [email protected] would be sent as [email protected].

AD lookup mapping
To perform on-premises AD property lookup to re-map AAD UPNs to Active Directory users, follow the steps in
this section. To begin with, let's review how this works.
In the Power BI service the following occurs:
For each query by a Power BI AAD user to an on-premises SSAS server, a UPN string is passed along, such
as: [email protected]
 NOTE
Any manual UPN user mappings defined in the Power BI data source configuration are still applied before sending the user
name string to the On-premises data gateway.

On the On-premises data gateway with configurable Custom User Mapping, do the following:
1. Find Active Directory to search (automatic, or configurable)
2. Look up the attribute of the AD Person (such as Email) based on incoming UPN string
(“[email protected]”) from the Power BI service.
3. If the AD Lookup fails, it attempts to use the passed-along UPN as EffectiveUser to SSAS.
4. If the AD Lookup succeeds, it retrieves UserPrincipalName of that AD Person.
5. It passes the UserPrincipalName email as EffectiveUser to SSAS, such as: [email protected]
How to configure your gateway to perform the AD Lookup:
1. Download and install the latest gateway
2. In the gateway, you need to change the On-premises data gateway service to run with a domain
account (instead of a local service account – otherwise the AD lookup won’t work properly at runtime).
You'll need to restart the gateway service for the change to take effect. Go to the gateway app on your
machine (search for “On-premises data gateway”). To do this, go to Service settings > Change service
account. Make sure you have the recovery key for this gateway, since you'll need to restore it on the same
machine unless you want to create a new gateway instead.
3. Navigate to the gateway’s installation folder, C:\Program Files\On-premises data gateway as an
administrator, to ensure that you have write-permissions, and edit the following file:
Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config
4. Edit the following two configuration values according to your Active Directory attribute configurations for
your AD users. The configuration values shown below are just examples – you need to specify them based
on your Active Directory configuration. These configurations are case-sensitive so make sure they match
the values in Active Directory.

If no value is provided for the ADServerPath configuration, the gateway uses the default Global Catalog.
You can also specify multiple values for the ADServerPath. Each value must be separated by a semicolon
as in the following example.

<setting name="ADServerPath" serializeAs="String">

<value> >GC://serverpath1; GC://serverpath2;GC://serverpath3</value>
</setting>

The gateway parses the values for ADServerPath from left to right until it finds a match. If no match is
found then the original UPN is used. Make sure the account running the gateway service (PBIEgwService)
has query permissions to all AD servers that you specify in ADServerPath.
The gateway supports two types of ADServerPath, as in the following examples.
WinNT
 <value="WinNT://usa.domain.corp.contoso.com,computer"/>

GC

<value> GC://USA.domain.com </value>

5. Restart the On-premises data gateway service for the configuration change to take effect.
Working with mapping rules
To create a mapping rule, enter a value for Original name and New Name and then select Add.

FIELD DESCRIPTION

Replace (Original name) The email address that you signed into Power BI with.

With (New Name) The value you want to replace it with. The result of the
replacement is what will be passed to the EffectiveUserName
property for the Analysis Services connection.

When you select an item in the list, you can choose to re-order it by using the chevron icons, or Delete the
entry.

Using wildcard (*)

You can use a wildcard for your Replace (Original name) string. It can only be used on its own and not with any
other string part. This will allow you to take all users and pass a single value to the data source. This is useful
when you want all users in your organization to use the same user in your local environment.
Test a mapping rule
You can validate what an original name will be replaced with by entering a value for Original name and
selecting Test rule.

NOTE
Rules that are saved will take a few minutes for the service to start using them. Within the browser, the rule will work
immediately.

Limitations for mapping rules

Mapping is for the specific data source that is being configured. It is not a global settings. If you have multiple
Analysis Services data sources, you will have to map the users for each data source.

Remove a data source

Removing a data source will break any dashboards or reports that rely on the given data source.
To remove a data source, go to Data Source > Remove.

Manage administrators
On the Administrators tab for the gateway, you can add and remove users (or security groups) that can
administer the gateway.
Manage users
On the Users tab for the data source, you can add, and remove, users, or security groups, that can use this data
source.

NOTE
The users list only controls who are allowed to publish reports. The report owners can create dashboards, or content packs,
and share those with other users.

Using the data source

After you have created the data source, it will be available to use with either live connections, or through
scheduled refresh.
 NOTE
Server and database name have to match between Power BI Desktop and the data source within the On-premises data
gateway!

The link between your dataset and the data source within the gateway is based on your server name and
database name. These have to match. For example, if you supply an IP Address for the server name, within Power
BI Desktop, you will need to use the IP Address for the data source within the gateway configuration. If you use
SERVER\INSTANCE, in Power BI Desktop, you will need to use the same within the data source configured for
the gateway.
This is the case for both live connections and scheduled refresh.
Using the data source with live connections
You will need to make sure the server and database name matches between Power BI Desktop and the
configured data source for the gateway. You will also need to make sure your user is listed in the Users tab of the
data source in order to publish live connection datasets. The selection, for live connections, occurs within Power
BI Desktop when you first import data.
After you publish, either from Power BI Desktop or Get Data, your reports should start working. It may take
several minutes, after creating the data source within the gateway, for the connection to be usable.
Using the data source with scheduled refresh
If you are listed in the Users tab of the data source configured within the gateway, and the server and database
name match, you will see the gateway as an option to use with scheduled refresh.

Next steps
On-premises data gateway
On-premises data gateway - in-depth
Troubleshooting the On-premises data gateway
More questions? Try the Power BI Community
 Manage your SAP HANA data source
1/14/2019 • 3 minutes to read • Edit Online

Once you have installed the On-premises data gateway , you will need to add data sources that can be used with
the gateway. This article will look at how to work with gateways and data sources. You can use the SAP HANA
data source either for scheduled refresh or for DirectQuery.

Download and install the gateway

You can download the gateway from the Power BI service. Select Downloads > Data Gateway, or by going to
the gateway download page.

Add a gateway
To add a Gateway, simply download and install the gateway on a server in your environment. After you have
installed the gateway, it will show in the lists of gateways under Manage gateways.

NOTE
Manage gateways will not show up until you are the admin of at least one gateway. This can happen either by being added
as an admin or you installing and configuring a gateway.

Remove a gateway
Removing a gateway will also delete any data sources under that gateway. This will also break any dashboards and
reports that rely on those data sources.

1. Select the gear icon in the upper-right corner > Manage gateways.
2. Gateway > Remove
Add a data source
You can add a data source by either selecting a gateway and click Add data source, or go to Gateway > Add
data source.

You can then select the Data Source Type from the list.

You will then want to fill in the information for the data source which includes the Server, Username and
Password.
 NOTE
All queries to the data source will run using these credentials. For more information, see the main On-premises data
gateway article to learn more about how credentials are stored.

You can click Add after you have everything filled in. You can now use this data source for scheduled refresh, or
DirectQuery, against a SAP HANA server that is on-premises. You will see Connection Successful if it succeeded.

Advanced settings
You can configure the privacy level for your data source. This controls how data can be mashed up. This is only
used for scheduled refresh. It does not apply to DirectQuery. Learn more
Remove a data source
Removing a data source will break any dashboards or reports that rely on the given data source.
To remove a Data Source, go to the Data Source > Remove.

Manage administrators
On the Administrators tab for the gateway, you can add and remove users (or security groups) that can administer
the gateway.

Manage users
On the Users tab, for the data source, you can add, and remove, users, or security groups, that can use this data
source.
 NOTE
The users list only controls who are allowed to publish reports. The report owners can create dashboards, or content packs,
and share those with other users.

Using the data source

After you have created the data source, it will be available to use with either DirectQuery connections, or through
scheduled refresh.

NOTE
Server and database name have to match between Power BI Desktop and the data source within the On-premises data
gateway!

The link between your dataset and the data source within the gateway is based on your server name and database
name. These have to match. For example, if you supply an IP Address for the server name, within Power BI
Desktop, you will need to use the IP Address for the data source within the gateway configuration. If you use
SERVER\INSTANCE, in Power BI Desktop, you will need to use the same within the data source configured for the
gateway.
This is the case for both DirectQuery and scheduled refresh.
Using the data source with DirectQuery connections
You will need to make sure the server and database name matches between Power BI Desktop and the configured
data source for the gateway. You will also need to make sure your user is listed in the Users tab of the data source
in order to publish DirectQuery datasets. The selection for DirectQuery occurs within Power BI Desktop when you
first import data. Learn more
After you publish, either from Power BI Desktop or Get Data, your reports should start working. It may take
several minutes, after creating the data source within the gateway, for the connection to be usable.
Using the data source with scheduled refresh
If you are listed in the Users tab of the data source configured within the gateway, and the server and database
name match, you will see the gateway as an option to use with scheduled refresh.
Next steps
On-premises data gateway
On-premises data gateway - in-depth
Troubleshooting the On-premises data gateway
More questions? Try the Power BI Community
 Manage your data source - SQL Server
2/13/2019 • 4 minutes to read • Edit Online

Once you have installed the On-premises data gateway, you can add data sources that can be used with the
gateway. This article will look at how to work with gateways and data sources. You can use the SQL Server data
source either for scheduled refresh or for DirectQuery.

Download and install the gateway

You can download the gateway from the Power BI service. Select Downloads > Data Gateway, or by going to
the gateway download page.

Add a gateway
To add a gateway, simply download and install the gateway on a server in your environment. After you have
installed the gateway, it will show in the lists of gateways under Manage gateways.

NOTE
Manage gateways will not show up until you are the admin of at least one gateway. This occurs when you are added as an
admin to a gateway, or you install and configure a gateway yourself.

Remove a gateway
Removing a gateway will also delete any data sources under that gateway. This will also break any dashboards and
reports that rely on those data sources.

1. Select the gear icon in the upper-right corner > Manage gateways.
2. Gateway > Remove
Add a data source
You can add a data source by either selecting a gateway and click Add data source, or go to Gateway > Add
data source.

You can then select the Data Source Type from the list.

NOTE
When using DirectQuery, the gateway only supports SQL Server 2012 SP1 and subsequent versions.

You will then want to fill in the information for the data source which includes the Server and the Database.
You will also need to choose an Authentication Method. This can either be Windows or Basic. You would want
to choose Basic if you are going to use SQL Authentication instead of Windows Authentication. Then enter the
credentials that will be used for this data source.

NOTE
All queries to the data source will run using these credentials, unless Kerberos Single Sign On (SSO) is configured and
enabled for the data source. With SSO, import datasets use the stored credentials, but DirectQuery datasets use the current
Power BI user to execut the queries using SSO. For more information, see the main On-premises data gateway article to
learn more about how credentials are stored, or the article describing how to use Kerberos for SSO (single sign-on) from
Power BI to on-premises data sources.

You can click Add after you have everything filled in. You can now use this data source for scheduled refresh, or
DirectQuery, against a SQL Server that is on-premises. You will see Connection Successful if it succeeded.
Advanced settings
You can configure the privacy level for your data source. This controls how data can be mashed up. This is only
used for scheduled refresh. It does not apply to DirectQuery. Learn more

Remove a data source

Removing a data source will break any dashboards or reports that rely on the given data source.
To remove a Data Source, go to the Data Source > Remove.

Manage administrators
On the Administrators tab for the gateway, you can add and remove users (or security groups) that can administer
the gateway.
Manage users
On the Users tab, for the data source, you can add, and remove, users, or security groups, that can use this data
source.

NOTE
The users list only controls who are allowed to publish reports. The report owners can create dashboards, or content packs,
and share those with other users.

Using the data source

After you have created the data source, it will be available to use with either DirectQuery connections, or through
scheduled refresh.

NOTE
Server and database name have to match between Power BI Desktop and the data source within the On-premises data
gateway!

The link between your dataset and the data source within the gateway is based on your server name and database
name. These have to match. For example, if you supply an IP Address for the server name, within Power BI
Desktop, you will need to use the IP Address for the data source within the gateway configuration. If you use
SERVER\INSTANCE, in Power BI Desktop, you will need to use the same within the data source configured for the
gateway.
This is the case for both DirectQuery and scheduled refresh.
Using the data source with DirectQuery connections
You will need to make sure the server and database name matches between Power BI Desktop and the
configured data source for the gateway. You will also need to make sure your user is listed in the Users tab of the
data source in order to publish DirectQuery datasets. The selection, for DirectQuery, occurs within Power BI
Desktop when you first import data. Learn more
After you publish, either from Power BI Desktop or Get Data, your reports should start working. It may take
several minutes, after creating the data source within the gateway, for the connection to be usable.
Using the data source with scheduled refresh
If you are listed in the Users tab of the data source configured within the gateway, and the server and database
name match, you will see the gateway as an option to use with scheduled refresh.

Next steps
On-premises data gateway
On-premises data gateway - in-depth
Troubleshooting the On-premises data gateway
Use Kerberos for SSO (single sign-on) from Power BI to on-premises data sources.
More questions? Try the Power BI Community
 Manage your data source - Oracle
2/13/2019 • 6 minutes to read • Edit Online

Once you have installed the On-premises data gateway, you will need to add data sources that can be used with
the gateway. This article will look at how to work with gateways and data sources. You can use the Oracle data
source either for scheduled refresh or for DirectQuery.

Download and install the gateway

You can download the gateway from the Power BI service. Select Downloads > Data Gateway, or by going to
the gateway download page.

WARNING
In order for the gateway to be able to connect to your Oracle server, the Oracle Data Provider for .NET (ODP.NET) needs to
be installed and configured. This is part of the Oracle Data Access Components (ODAC). For more information on how to
download the Oracle provider, see Installing the Oracle Client below.

Installing the Oracle client

For 32-bit versions of Power BI Desktop, use the following link to download and install the 32-bit Oracle client:
32-bit Oracle Data Access Components (ODAC ) with Oracle Developer Tools for Visual Studio (12.1.0.2.4)
For 64-bit versions of Power BI Desktop, or for the On-premises data gateway, use the following link to download
and install the 64-bit Oracle client:
64-bit ODAC 12.2c Release 1 (12.2.0.1.0) for Windows x64
Once that is installed, you will need to configure your tnsnames.ora file with the proper information for your
database. Power BI Desktop and the gateway will go off of the net_service_name defined in the tnsnames.ora file.
If it isn't configured, you will not be able to connect. The default path for tnsnames.ora is the following:
[Oracle Home Directory]\Network\Admin\tnsnames.ora . For more information about how to configure tnsnames.ora
files, see Oracle: Local Naming Parameters (tnsnames.ora).
Example tnsnames.ora file entry
The basic format of an entry in tnsname.ora is the following.
 net_service_name=
(DESCRIPTION=
(ADDRESS=(protocol_address_information))
(CONNECT_DATA=
(SERVICE_NAME=service_name)))

Here is an example of the server and port information filled in.

CONTOSO =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = oracleserver.contoso.com)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = CONTOSO)
)
)

Add a gateway
To add a gateway, simply download and install the gateway on a server in your environment. After you have
installed the gateway, it will show in the lists of gateways under Manage gateways.

NOTE
Manage gateways will not show up until you are the admin of at least one gateway. This can happen either by being added
as an admin or you installing and configuring a gateway.

Remove a gateway
Removing a gateway will also delete any data sources under that gateway. This will also break any dashboards and
reports that rely on those data sources.

1. Select the gear icon in the upper-right corner > Manage gateways.
2. Gateway > Remove

Add a data source

You can add a data source by either selecting a gateway and click Add data source, or go to Gateway > Add data
source.
You can then select the Data Source Type from the list.

You will then want to fill in the information for the data source which includes the Server and the Database.
You will also need to choose an Authentication Method. This can either be Windows or Basic. You would want
to choose Basic if you are going to use an account that is created within Oracle instead of Windows
Authentication. Then enter the credentials that will be used for this data source.

NOTE
All queries to the data source will run using these credentials. For more information, see the main On-premises data gateway
article to learn more about how credentials are stored.
You can click Add after you have everything filled in. You can now use this data source for scheduled refresh, or
DirectQuery, against an Oracle server that is on-premises. You will see Connection Successful if it succeeded.

Advanced settings
You can configure the privacy level for your data source. This controls how data can be mashed up. This is only
used for scheduled refresh. It does not apply to DirectQuery. Learn more
Remove a data source
Removing a data source will break any dashboards or reports that rely on the given data source.
To remove a Data Source, go to the Data Source > Remove.

Manage administrators
On the Administrators tab for the gateway, you can add and remove users (or security groups) that can administer
the gateway.

Manage users
On the Users tab, for the data source, you can add, and remove, users, or security groups, that can use this data
source.

NOTE
The users list only controls who are allowed to publish reports. The report owners can create dashboards, or content packs,
and share those with other users. Users that are consuming the report or dashboard do not need to be in the users list.
Using the data source
After you have created the data source, it will be available to use with either DirectQuery connections, or through
scheduled refresh.

WARNING
Server and database name have to match between Power BI Desktop and the data source within the On-premises data
gateway!

The link between your dataset and the data source within the gateway is based on your server name and database
name. These have to match! For example, if you supply an IP Address for the server name, within Power BI
Desktop, you will need to use the IP Address for the data source within the gateway configuration. This name also
has to match an alias defined within the tnsnames.ora file. For more information about the tnsnames.ora file, see
Installing the Oracle Client.
This is the case for both DirectQuery and scheduled refresh.
Using the data source with DirectQuery connections
You will need to make sure the server and database name matches between Power BI Desktop and the configured
data source for the gateway. You will also need to make sure your user is listed in the Users tab of the data source
in order to publish DirectQuery datasets. The selection, for DirectQuery, occurs within Power BI Desktop when
you first import data. Learn more
After you publish, either from Power BI Desktop or Get Data, your reports should start working. It may take
several minutes, after creating the data source within the gateway, for the connection to be usable.
Using the data source with scheduled refresh
If you are listed in the Users tab of the data source configured within the gateway, and the server and database
name match, you will see the gateway as an option to use with scheduled refresh.
Troubleshooting
You may encounter several errors from Oracle when the naming syntax is either incorrect or not configured
properly.
ORA-12154: TNS: could not resolve the connect identifier specified
ORA-12514: TNS listener does not currently know of service requested in connect descriptor
ORA-12541: TNS: no listener
ORA-12170: TNS:Connect timeout occurred
ORA-12504: TNS listener was not given the SERVICE_NAME in CONNECT_DATA
These errors could occur if either the Oracle client is not installed, or if it is not configured properly. If it is installed,
you will want to verify the tnsnames.ora file is properly configured and you are using the proper
net_service_name. You will also need to make sure that the net_service_name is the same between the machine
using Power BI Desktop and the machine that is running the gateway. For more information, see Installing the
Oracle Client.

NOTE
You may also be hitting an issue due to compatability between the Oracle server version and the Oracle client version.
Typically you want these to match.

For additional troubleshooting information relating to the gateway, see Troubleshooting the On-premises data
gateway.

Next steps
On-premises data gateway
On-premises data gateway - in-depth
Troubleshooting the On-premises data gateway
Power BI Premium
More questions? Try asking the Power BI Community
 Manage your data source - Import/Scheduled
Refresh
1/14/2019 • 4 minutes to read • Edit Online

Once you have installed the On-premises data gateway, you will need to add data sources that can be used with
the gateway. This article will look at how to work with gateways and data sources that are used for scheduled
refresh as opposed to DirectQuery or live connections.

Download and install the gateway

You can download the gateway from the Power BI service. Select Downloads > Data Gateway, or by going to
the gateway download page.

Add a gateway
To add a gateway, simply download and install the enterprise gateway on a server in your environment. After you
have installed the gateway, it will show in the lists of gateways under Manage gateways.

NOTE
Manage gateways will not show up until you are the admin of at least one gateway. This can happen either by being added
as an admin or you installing and configuring a gateway.

Remove a gateway
Removing a gateway will also delete any data sources under that gateway. This will also break any dashboards and
reports that rely on those data sources.

1. Select the gear icon in the upper-right corner > Manage gateways.
2. Gateway > Remove
Add a data source
You can add a data source by either selecting a gateway and click Add data source, or go to Gateway > Add
data source.

You can then select the Data Source Type from the list. All of the data sources listed can be used for scheduled
refresh with the enterprise gateway. Analysis Services, SQL Server and SAP HANA can be used for either
scheduled refresh, or DirectQuery/live connections.

You will then want to fill in the information for the data source which includes the source information and
credentials used to access the data source.
 NOTE
All queries to the data source will run using these credentials. For more information, see the main On-premises data
gateway article to learn more about how credentials are stored.

You can click Add after you have everything filled in. You can now use this data source for scheduled refresh with
your on-premises data. You will see Connection Successful if it succeeded.

List of available data source types

USER CONFIGURED MANUAL OR
DATA SOURCE LIVE/DIRECTQUERY SCHEDULED REFRESH

Analysis Services Tabular Yes Yes

Analysis Services Multidimensional Yes Yes

 USER CONFIGURED MANUAL OR
DATA SOURCE LIVE/DIRECTQUERY SCHEDULED REFRESH

File No Yes

Folder No Yes

IBM DB2 Yes Yes

IBM Informix Database No Yes

IBM Netezza Yes Yes

Impala Yes Yes

MySQL No Yes

OData No Yes

ODBC No Yes

Oledb No Yes

Oracle Yes Yes

PostgresSQL No Yes

SAP BW Yes Yes

SAP HANA Yes Yes

SharePoint list (on-premises) No Yes

Snowflake Yes Yes

Spark Yes Yes

SQL Server Yes Yes

Sybase No Yes

Teradata Yes Yes

Web No Yes

Advanced settings
You can configure the privacy level for your data source. This controls how data can be mashed up. This is only
used for scheduled refresh. Learn more
Remove a data source
Removing a data source will break any dashboards or reports that rely on the given data source.
To remove a Data Source, go to the Data Source > Remove.

Manage administrators
On the Administrators tab, for the gateway, you can add, and remove, users that can administer the gateway. You
can only add users at this time. Security groups cannot be added.

Manage users
On the Users tab, for the data source, you can add, and remove, users, or security groups, that can use this data
source.
 NOTE
The users list only controls who are allowed to publish reports. The report owners can create dashboards, or content packs,
and share those with other users.

Using the data source for scheduled refresh

After you have created the data source, it will be available to use with either DirectQuery connections, or through
scheduled refresh.

NOTE
Server and database name have to match between Power BI Desktop and the data source within the On-premises data
gateway!

The link between your dataset and the data source within the gateway is based on your server name and database
name. These have to match. For example, if you supply an IP Address for the server name, within Power BI
Desktop, you will need to use the IP Address for the data source within the gateway configuration. If you use
SERVER\INSTANCE, in Power BI Desktop, you will need to use the same within the data source configured for the
gateway.
If you are listed in the Users tab of the data source configured within the gateway, and the server and database
name match, you will see the gateway as an option to use with scheduled refresh.
 WARNING
If your dataset contains multiple data sources, each data source must be added within the gateway. If one or more data
sources are not added to the gateway, you will not see the gateway as available for scheduled refresh.

Limitations
OAuth is not a supported authentication scheme with the On-premises data gateway. You cannot add data
sources that require OAuth. If your dataset has a data source requiring OAuth, you will not be able to use the
gateway for scheduled refresh.

Next steps
On-premises data gateway
On-premises data gateway - in-depth
Troubleshooting the On-premises data gateway
More questions? Try the Power BI Community
 Merge or append on-premises and cloud data
sources
1/14/2019 • 2 minutes to read • Edit Online

The On-premises data gateway enables you to merge or append on-premises and cloud data sources in the same
query. This is helpful when you want to mashup data from multiple sources without having to use separate queries.

Prerequisites
A gateway installed on a local computer.
A Power BI Desktop file with queries that combine on-premises and cloud data sources.

1. In the upper-right corner of the Power BI service, select the gear icon > Manage gateways.

2. Select the gateway you want to configure.

3. Under Gateway Cluster Settings, select Allow user's cloud data sources to refresh through this
gateway cluster > Apply.
4. Under this gateway cluster, add any on-premises data sources used in your queries. You don't need to add
the cloud data sources here.
5. Upload to the Power BI service your Power BI Desktop file with the queries that combine on-premises and
cloud data sources.
6. On the Dataset settings page for the new dataset:
For the on-premises source, select the gateway associated with this data source.
Under Data source credentials, edit the cloud data source credentials as necessary.
7. With the cloud credentials set, you can now refresh the dataset using the Refresh now option, or schedule it
to refresh periodically.

Next steps
To learn more about data refresh for gateways, see Using the data source for scheduled refresh.
 Overview of single sign-on (SSO) for gateways in
Power BI
1/14/2019 • 2 minutes to read • Edit Online

You can get seamless single sign-on connectivity, enabling Power BI reports and dashboards to update from on-
premises data, by configuring your On-premises data gateway either with Kerberos constrained delegation or
Security Assertion Markup Language (SAML ). The On-premises data gateway facilitates SSO using DirectQuery,
which it uses to connect to on-premises data sources.
We currently support the following data sources:
SQL Server (Kerberos)
SAP HANA (Kerberos and SAML
SAP BW (Kerberos
Teradata (Kerberos)
Spark (Kerberos)
Impala (Kerberos)
When a user interacts with a DirectQuery report in the Power BI Service, each cross-filter, slice, sorting, and report
editing operation can result in queries executing live against the underlying on-premises data source. When SSO is
configured for the data source, queries execute under the identity of the user interacting with Power BI (that is,
through the web experience or Power BI mobile apps). Thereby, each user sees precisely the data for which they
have permissions in the underlying data source – with single sign-on configured, there is no shared data caching
across different users.

Query steps when running SSO

A query that runs with SSO consists of three steps, as shown in the following diagram.
 NOTE
SSO for Oracle is not enabled yet, but is under development and coming soon.

Here are additional details about those steps:

1. For each query, the Power BI service includes the user principal name (UPN ) when sending a query
request to the configured gateway.
2. The gateway needs to map the Azure Active Directory UPN to a local Active Directory identity.
a. If Azure AD DirSync (also known as Azure AD Connect) is configured, then the mapping works
automatically in the gateway.
b. Otherwise, the gateway can look up and map the Azure AD UPN to a local user by performing a lookup
against the local Active Directory domain.
3. The gateway service process impersonates the mapped local user, opens the connection to the underlying
database and sends the query. The gateway does not need to be installed on the same machine as the
database.

Next steps
Now that you understand the basics of SSO, read more detailed information about Kerberos and SAML:
Single sign-on (SSO ) - Kerberos
Single sign-on (SSO ) - SAML
 Use Kerberos for single sign-on (SSO) from Power
BI to on-premises data sources
3/18/2019 • 18 minutes to read • Edit Online

Use Kerberos constrained delegation to enable seamless single sign-on (SSO ) connectivity. Enabling SSO
makes it easy for Power BI reports and dashboards to refresh data from on-premises sources.

Supported data sources

We currently support the following data sources:
SQL Server
SAP HANA
SAP BW
Teradata
Spark
Impala
We also support SAP HANA with Security Assertion Markup Language (SAML ).
SAP HANA
To enable SSO for SAP HANA, follow these steps first:
Ensure the SAP HANA server is running the required minimum version, which depends on your SAP
HANA server platform level:
HANA 2 SPS 01 Rev 012.03
HANA 2 SPS 02 Rev 22
HANA 1 SP 12 Rev 122.13
On the gateway machine, install SAP’s latest HANA ODBC driver. The minimum version is HANA ODBC
version 2.00.020.00 from August 2017.
For more information about setting up SSO for SAP HANA by using Kerberos, see Single Sign-on Using
Kerberos in the SAP HANA Security Guide. Also see the links from that page, particularly SAP Note 1837331 –
HOWTO HANA DBSSO Kerberos/Active Directory.

Prepare for Kerberos constrained delegation

You must configure several items for Kerberos constrained delegation to work properly, including Service
Principal Names (SPN ) and delegation settings on service accounts.
Prerequisite 1: Install and configure the Microsoft on-premises data gateway
This release of the on-premises data gateway supports an in-place upgrade, as well as settings take-over of
existing gateways.
Prerequisite 2: Run the gateway Windows service as a domain account
In a standard installation, the gateway runs as a machine-local service account (specifically, NT
Service\PBIEgwService).
To enable Kerberos constrained delegation, the gateway must run as a domain account, unless your Azure
Active Directory (Azure AD ) instance is already synchronized with your local Active Directory instance (using
Azure AD DirSync/Connect). To switch to a domain account, see Switch the gateway to a domain account later
in this article.

NOTE
If Azure AD Connect is configured, and user accounts are synchronized, the gateway service doesn't need to perform local
Azure AD lookups at runtime. You can use the local service SID (instead of requiring a domain account) for the gateway
service. The Kerberos constrained delegation configuration steps outlined in this article are the same as that
configuration. They are simply applied to the gateway's computer object in Azure AD, instead of the domain account.

Prerequisite 3: Have domain admin rights to configure SPNs (SetSPN ) and Kerberos constrained delegation
settings
It's not recommended for a domain administrator to temporarily or permanently allow rights to someone else
to configure SPNs and Kerberos delegation without requiring domain admin rights. In the following section, we
cover the recommended configuration steps in more detail.

Configure Kerberos constrained delegation for the gateway and data

source
As a domain administrator, configure an SPN for the gateway service domain account, and configure delegation
settings on the gateway service domain account.
Configure an SPN for the gateway service account
First, determine whether an SPN was already created for the domain account used as the gateway service
account:
1. As a domain administrator, open Active Directory Users and Computers.
2. Right-click on the domain, select Find, and enter the account name of the gateway service account.
3. In the search result, right-click the gateway service account, and select Properties.
4. If the Delegation tab is visible on the Properties dialog box, then an SPN was already created. You can
jump ahead to configuring delegation settings.
If there is no Delegation tab on the Properties dialog box, you can manually create an SPN on that
account. This adds the Delegation tab. Use the setspn tool that comes with Windows (you need domain
admin rights to create the SPN ).
For example, imagine the gateway service account is “PBIEgwTest\GatewaySvc”, and the machine name
with the gateway service running is called Machine1. To set the SPN for the gateway service account for
that machine in this example, run the following command:

With that step completed, we can move on to configuring delegation settings.

Configure delegation settings on the gateway service account
The second configuration requirement is the delegation settings on the gateway service account. There are
multiple tools you can use to perform these steps. Here, we'll use Active Directory Users and Computers, which
is a Microsoft Management Console (MMC ) snap-in to administer and publish information in the directory. It's
available on domain controllers by default. You can also enable it through Windows Feature configuration on
other machines.
We need to configure Kerberos constrained delegation with protocol transiting. With constrained delegation,
you must be explicit about which services you want to delegate to. For example, only SQL Server or your SAP
HANA server accepts delegation calls from the gateway service account.
This section assumes you have already configured SPNs for your underlying data sources (such as SQL Server,
SAP HANA, Teradata, and Spark). To learn how to configure those data source server SPNs, refer to technical
documentation for the respective database server. You can also see the What SPN does your app require? blog
post.
In the following steps, we assume an on-premises environment with two machines: a gateway machine and a
database server running SQL Server. For the sake of this example, we'll also assume the following settings and
names:
Gateway machine name: PBIEgwTestGW
Gateway service account: PBIEgwTest\GatewaySvc (account display name: Gateway Connector)
SQL Server data source machine name: PBIEgwTestSQL
SQL Server data source service account: PBIEgwTest\SQLService
Here's how to configure the delegation settings:
1. With domain administrator rights, open Active Directory Users and Computers.
2. Right-click the gateway service account ( PBIEgwTest\GatewaySvc), and select Properties.
3. Select the Delegation tab.
4. Select Trust this computer for delegation to specified services only > Use any authentication
protocol.
5. Under Services to which this account can present delegated credentials, select Add.
6. In the new dialog box, select Users or Computers.
7. Enter the service account for the SQL Server data source ( PBIEgwTest\SQLService), and select OK.
8. Select the SPN that you created for the database server. In our example, the SPN begins with
MSSQLSvc. If you added both the FQDN and the NetBIOS SPN for your database service, select both.
You might only see one.
9. Select OK. You should see the SPN in the list now.
Optionally, you can select Expanded to show both the FQDN and NetBIOS SPN. The dialog box looks
similar to the following if you selected Expanded. Select OK.
Finally, on the machine running the gateway service ( PBIEgwTestGW in our example), you must grant the
gateway service account the local policy Impersonate a client after authentication. You can perform and
verify this with the Local Group Policy Editor (gpedit).
1. On the gateway machine, run: gpedit.msc.
2. Go to Local Computer Policy > Computer Configuration > Windows Settings > Security
Settings > Local Policies > User Rights Assignment.

3. Under User Rights Assignment, from the list of policies, select Impersonate a client after
authentication.

Right-click, and open Properties. Check the list of accounts. It must include the gateway service account
(PBIEgwTest\GatewaySvc).
4. Under User Rights Assignment, from the list of policies, select Act as part of the operating system
(SeTcbPrivilege). Ensure that the gateway service account is included in the list of accounts as well.
5. Restart the On-premises data gateway service process.
If you're using SAP HANA, we recommend following these additional steps, which can yield a small
performance improvement.
1. In the gateway installation directory, find and open this configuration file:
Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config.
2. Find the FullDomainResolutionEnabled property, and change its value to True.

<setting name=" FullDomainResolutionEnabled " serializeAs="String">

<value>True</value>
</setting>

Run a Power BI report

After completing all the configuration steps, you can use the Manage Gateway page in Power BI to configure
the data source. Then, under Advanced Settings, enable SSO, and publish reports and datasets binding to that
data source.

This configuration works in most cases. However, with Kerberos there can be different configurations
depending on your environment. If the report still won't load, contact your domain administrator to investigate
further.

Switch the gateway to a domain account

If necessary, you can switch the gateway from a local service account to run as a domain account, by using the
On-premises data gateway user interface. Here's how:
1. Open the On-premises data gateway configuration tool.

2. Select the Sign-in button on the main page, and sign in with your Power BI account.
3. After sign-in is completed, select the Service Settings tab.
4. Select Change account to start the guided walk-through.

Configure SAP BW for SSO

Now that you understand how Kerberos works with a gateway, you can configure SSO for your SAP Business
Warehouse (SAP BW ). The following steps assume you've already prepared for Kerberos constrained
delegation, as described earlier in this article.
This guide attempts to be as comprehensive as possible. If you've already completed some of these steps, you
can skip them. For example, you might have already created a service user for your SAP BW server and
mapped an SPN to it, or you might have already installed the gsskrb5 library.
Set up gsskrb5 on client machines and the SAP BW server

NOTE
gsskrb5 is no longer actively supported by SAP. For more information, see SAP Note 352295. Also note that gsskrb5
doesn't allow for SSO connections from the data gateway to SAP BW Message Servers. Only connections to SAP BW
Application Servers are possible.

must be in use by both the client and server to complete an SSO connection through the gateway. The
gsskrb5
Common Crypto Library (sapcrypto) isn't currently supported.
1. Download gsskrb5 - gx64krb5 from SAP Note 2115486 (SAP s-user required). Ensure you have at
least version 1.0.11.x of gsskrb5.dll and gx64krb5.dll.
2. Put the library in a location on your gateway machine that is accessible by your gateway instance (and
 also by the SAP GUI if you want to test the SSO connection by using SAP Logon).
3. Put another copy on your SAP BW server machine in a location accessible by the SAP BW server.
4. On the client and server machines, set the SNC\_LIB and SNC\_LIB\_64 environment variables to point to
the locations of gsskrb5.dll and gx64krb5.dll, respectively.
Create a SAP BW service user and enable SNC communication
In addition to the gateway configuration you've already done, there are a few additional steps specific to SAP
BW. The Configure delegation settings on the gateway service account section of the documentation assumes
you've already configured SPNs for your underlying data sources. To complete this configuration for SAP BW:
1. On an Active Directory Domain Controller server, create a service user (initially just a plain Active
Directory user) for your SAP BW Application Server in your Active Directory environment. Then assign
an SPN to it.
SAP recommends starting the SPN with SAP/ , but it should also be possible to use other prefixes, such
as HTTP/ . What comes after the SAP/ is up to you; one option is to use the SAP BW server's service
user's username. For example, if you create BWServiceUser@\<DOMAIN\> as your service user, you can use
the SPN SAP/BWServiceUser . One way to set the SPN mapping is the setspn command. For example, to
set the SPN on the service user we just created, you would run the following command from a cmd
window on a Domain Controller machine: setspn -s SAP/ BWServiceUser DOMAIN\ BWServiceUser . For
more information, see the SAP BW documentation.
2. Give the service user access to your SAP BW Application Server:
a. On the SAP BW server machine, add the service user to the Local Admin group for your SAP BW
server. Open the Computer Management program and double-click the Local Admin group for
your server.

b. Double-click the Local Admin group, and select Add to add your service user to the group. Select
Check Names to ensure you've entered the name correctly. Select OK.
3. Set the SAP BW server's service user as the user who starts the SAP BW server service on the SAP BW
server machine.
 a. Open Run, and enter "Services.msc". Look for the service corresponding to your SAP BW
Application Server instance. Right-click it, and select Properties.

b. Switch to the Log on tab, and change the user to your SAP BW service user. Enter the user's
password, and select OK.
4. Sign in to your server in SAP Logon, and set the following profile parameters by using the RZ10
transaction:
a. Set the snc/identity/as profile parameter to p:<the SAP BW service user you've created>, such as
p:[email protected]. Note the p: that precedes the service user's UPN. It's not
p:CN= like when Common Crypto Lib is used as the SNC library.
b. Set the snc/gssapi_lib profile parameter to <path to gsskrb5.dll/gx64krb5.dll on the server
machine (the library you'll use depends on OS bitness)>. Remember to put the library in a
location the SAP BW Application Server can access.
c. Also set the following additional profile parameters, changing the values as required to fit your
needs. Note that the last five options enable clients to connect to the SAP BW server by using
SAP Logon, without having SNC configured.

SETTING VALUE

snc/data_protection/max 3

snc/data_protection/min 1

snc/data_protection/use 9

snc/accept_insecure_cpic 1

snc/accept_insecure_gui 1

snc/accept_insecure_r3int_rfc 1

snc/accept_insecure_rfc 1

snc/permit_insecure_start 1

d. Set the property snc/enable to 1.

5. After setting these profile parameters, open the SAP Management Console on the server machine, and
restart the SAP BW instance. If the server won't start, confirm that you've set the profile parameters
correctly. For more on profile parameter settings, see the SAP documentation. You can also consult the
 troubleshooting information later in this section if you encounter problems.
Map a SAP BW user to an Active Directory user
Map an Active Directory user to an SAP BW Application Server user, and test the SSO connection in SAP
Logon.
1. Sign in to your SAP BW server by using SAP Logon. Run transaction SU01.
2. For User, enter the SAP BW user you want to enable SSO connections for (in the previous screenshot,
we're setting permissions for BIUSER ). Select the Edit icon (the image of a pen) near the top left of the
SAP Logon window.

3. Select the SNC tab. In the SNC name input box, enter p:<your Active Directory user>@<your domain>.
Note the mandatory p: that must precede the Active Directory user's UPN. The Active Directory user you
specify should belong to the person or organization for whom you want to enable SSO access to the
SAP BW Application Server. For example, if you want to enable SSO access for the user
[email protected], enter p:[email protected].
4. Select the Save icon (the image of a floppy disk) near the top left of the screen.
Test sign-in by using SSO
Verify that you can sign in to the server. Use the SAP Logon through SSO as the Active Directory user for
whom you've just enabled SSO access.
1. As the Active Directory user you just enabled SSO access for, sign in to a machine on which SAP Logon
is installed. Launch SAP Logon, and create a new connection.
2. In the Create New System Entry screen, select User Specified System > Next.

3. Fill in the appropriate details on the next screen, including the application server, instance number, and
system ID. Then select Finish.
4. Right-click the new connection and select Properties. Select the Network tab. In the SNC Name text
box, enter p:<the SAP BW service user's UPN>, such as p:[email protected]. Then
select OK.
5. Double-click the connection you just created to attempt an SSO connection to your SAP BW server. If
this connection succeeds, proceed to the next step. Otherwise, review the earlier steps in this document
to make sure they've been completed correctly, or review the troubleshooting section below. Note that if
you can't connect to the SAP BW server via SSO in this context, you won't be able to connect to the SAP
BW server using SSO in the gateway context.
Troubleshoot installation and connections
If you encounter any problems, follow these steps to troubleshoot the gsskrb5 installation and SSO connections
from the SAP Logon.
Viewing the server logs (…work\dev_w0 on the server machine) can be helpful in troubleshooting any
errors you encounter in completing the gsskrb5 setup steps. This is particularly true if the SAP BW
server won't start after the profile parameters have been changed.
If you're unable to start the SAP BW service due to a logon failure, you might have provided the wrong
password when setting the SAP BW "start-as" user. Verify the password by logging in to a machine in
your Active Directory environment as the SAP BW service user.
If you get errors about SQL credentials preventing the server from starting, verify that you've granted
the service user access to the SAP BW database.
You might get the following message: "(GSS -API) specified target is unknown or unreachable." This
usually means you have the wrong SNC name specified. Make sure to use "p:" only, not "p:CN=" or
anything else in the client application, other than the service user's UPN.
You might get the following message: "(GSS -API) An invalid name was supplied." Make sure "p:" is in the
value of the server's SNC identity profile parameter.
You might get the following message: "(SNC error) the specified module could not be found." This is
usually caused by putting the gsskrb5.dll/gx64krb5.dll somewhere that requires elevated privileges
(administrator rights) to access.
Add registry entries to the gateway machine
Add required registry entries to the registry of the machine that the gateway is installed on. Here are the
commands to run:
1. REG ADD HKLM\SOFTWARE\Wow6432Node\SAP\gsskrb5 /v ForceIniCredOK /t REG_DWORD /d 1
/f
2. REG ADD HKLM\SOFTWARE\SAP\gsskrb5 /v ForceIniCredOK /t REG_DWORD /d 1 /f
Set configuration parameters on the gateway machine
There are two options for setting configuration parameters, depending on whether you have Azure AD Connect
configured so that users can sign in to the Power BI service as an Azure AD user.
If you have Azure AD Connect configured, follow these steps.
1. Open the main gateway configuration file, Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll . By
default, this file is stored at C:\Program Files\On-premises data gateway.
2. Ensure the FullDomainResolutionEnabled property is set to True, and
SapHanaSsoRemoveDomainEnabled is set to False.
3. Save the configuration file.
4. From the Services tab of Task Manager, right-click the gateway service and select Restart.

If you don't have Azure AD Connect configured, follow these steps for every Power BI service user you want to
map to an Azure AD user. These steps manually link a Power BI service user to an Active Directory user with
permission to sign in to SAP BW.
1. Open the main gateway configuration file, Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll . By
default, this file is stored at C:\Program Files\On-premises data gateway.
2. Set the ADUserNameLookupProperty to msDS-cloudExtensionAttribute1 , and the
ADUserNameReplacementProperty to SAMAccountName . Save the configuration file.
3. From the Services tab of Task Manager, right-click the gateway service and select Restart.

4. Set the msDS-cloudExtensionAttribute1 property of the Active Directory user. This is the user you mapped
to a SAP BW user. Set the property to the Power BI service user for whom you want to enable Kerberos
 SSO. One way to set the msDS-cloudExtensionAttribute1 property is by using the Active Directory Users
and Computers MMC snap-in. (You can also use other methods.)
a. Sign in to a Domain Controller machine as an administrator user.
b. Open the Users folder in the snap-in window, and double-click the Active Directory user you
mapped to a SAP BW user.
c. Select the Attribute Editor tab.
If you don't see this tab, you'll need to search for directions on how to enable it, or use another
method to set the property. Select one of the attributes and then the M key to go to the Active
Directory properties that start with the letter m. Locate the msDS-cloudExtensionAttribute1
property, and double-click it. Set the value to the username you use to sign in to the Power BI
Service, in the form YourUser@YourDomain.
d. Select OK.

e. Select Apply. Verify that the correct value has been set in the Value column.
Add a new SAP BW Application Server data source to the Power BI service
Add the SAP BW data source to your gateway by following the instructions earlier in this article on running a
report.
1. In the data source configuration window, enter the Application Server's Hostname, System Number,
and client ID, as you would to sign in to your SAP BW server from Power BI Desktop. For the
Authentication Method, select Windows.
2. In the SNC Partner Name field, enter p: <the SPN you mapped to your SAP BW service user>. For
example, if the SPN is SAP/[email protected], you should enter
p:SAP/[email protected] in the SNC Partner Name field.
3. For the SNC Library, select SNC_LIB or SNC_LIB_64.
4. The Username and Password should be the username and password of an Active Directory user with
permission to sign in to the SAP BW server with SSO. In other words, these should belong to an Active
Directory user who has been mapped to a SAP BW user through the SU01 transaction. These credentials
are only used if the Use SSO via Kerberos for DirectQuery queries box is not checked.
5. Select the Use SSO via Kerberos for DirectQuery queries box, and select Apply. If the test
connection is not successful, verify that the previous setup and configuration steps were completed
correctly.
The gateway always uses the typed-in credentials to establish a test connection to the server, and to do
scheduled refreshes of import-based reports. The gateway only attempts to establish an SSO connection
if the Use SSO via Kerberos for DirectQuery queries is selected, and the user is accessing a direct
query-based report or dataset.
Test your setup
To test your setup, publish a DirectQuery report from Power BI Desktop to the Power BI service. Make sure
you’re signed in to the Power BI service as either an Azure AD user, or a user you’ve mapped to the
msDS-cloudExtensionAttribute1 property of an Azure AD user. If the setup has been completed successfully, you
should be able to create a report from the published dataset in the Power BI service. You should also be able to
pull data through visuals in the report.
Troubleshoot gateway connectivity issues
1. Check the gateway logs. Open the gateway configuration application, and select Diagnostics > Export
logs. The most recent errors are at the bottom of any log files you examine.

2. Turn on SAP BW tracing, and review the generated log files. There are several different types of SAP BW
tracing available. Consult the SAP documentation for more information.

Errors from an insufficient Kerberos configuration

If the underlying database server and gateway are not configured properly for Kerberos constrained delegation,
you might receive the following error message about failing to load data:

The technical details associated with the error message (DM_GWPipeline_Gateway_ServerUnreachable) might
look like the following:

The result is that the gateway can't impersonate the originating user properly, and the database connection
attempt failed.
Next steps
For more information about the On-premises data gateway and DirectQuery, check out the following
resources:
On-premises data gateway
DirectQuery in Power BI
Data sources supported by DirectQuery
DirectQuery and SAP BW
DirectQuery and SAP HANA
 Use resource-based Kerberos for single sign-on (SSO)
from Power BI to on-premises data sources
3/22/2019 • 5 minutes to read • Edit Online

Use resource-based Kerberos constrained delegation to enable single sign-on connectivity for Windows Server
2012 and later versions, permitting front-end and back-end services to be in different domains. For this to work,
the back-end service domain needs to trust the front-end service domain.

Preparing for resource-based Kerberos constrained delegation

Several items must be configured for Kerberos Constrained Delegation to work properly, including Service
Principal Names (SPN ) and delegation settings on service accounts.
Prerequisite 1: Operating system requirements
Resource-based constrained delegation can only be configured on a domain controller running Windows Server
2012 R2 or Windows Server 2012 or higher.
Prerequisite 2: Install and configure the On-premises data gateway
This release of the On-premises data gateway supports an in-place upgrade, and settings takeover of existing
gateways.
Prerequisite 3: Run the gateway Windows service as a domain account
In a standard installation, the gateway runs as a machine-local service account (specifically, NT
Service\PBIEgwService) such as what's shown in the following image:

To enable **Kerberos Constrained Delegation, the gateway must run as a domain account, unless your Azure AD is
already synchronized with your local Active Directory (using Azure AD DirSync/Connect). If you need to switch the
account to a domain account, see Switching the gateway to a domain account.
If Azure AD DirSync / Connect is configured and user accounts are synchronized, the gateway service does not
need to perform local AD lookups at runtime. You can use the local Service SID (instead of requiring a domain
account) for the gateway service. The Kerberos Constrained Delegation configuration steps outlined in this article
are the same as that configuration (they are simply applied to the gateway's computer object in Active Directory,
instead of the domain account).
Prerequisite 4: Have domain admin rights to configure SPNs (SetSPN ) and Kerberos constrained delegation
settings
While it is technically possible for a domain administrator to temporarily or permanently allow rights to someone
else to configure SPNs and Kerberos delegation without requiring domain admin rights, that's not the
recommended approach. In the following section, we cover the configuration steps necessary for Prerequisite 3 in
detail.

Configuring Kerberos constrained delegation for the gateway and data

source
To properly configure the system, we need to configure or validate the following two items:
1. If needed, configure an SPN for the gateway service domain account.
2. Configure delegation settings on the gateway service domain account.
Note that you must be a domain administrator to perform those two configuration steps.
The following sections describe these steps in turn.
Configure an SPN for the gateway service account
First, determine whether an SPN was already created for the domain account used as the gateway service account,
but following these steps:
1. As a domain administrator, launch Active Directory Users and Computers.
2. Right-click on the domain, select Find, and type in the account name of the gateway service account
3. In the search result, right-click on the gateway service account and select Properties.
4. If the Delegation tab is visible on the Properties dialog, then an SPN was already created and you can
jump ahead to the next subsection about configuring Delegation settings.
If there is no Delegation tab on the Properties dialog, you can manually create an SPN on that account,
which adds the Delegation tab (that is the easiest way to configure delegation settings). Creating an SPN
can be done using the setspn tool that comes with Windows (you need domain admin rights to create the
SPN ).
For example, imagine the gateway service account is "PBIEgwTest\GatewaySvc", and the machine name
with the gateway service running is called Machine1. To set the SPN for the gateway service account for
that machine in this example, you would run the following command:

With that step completed, we can move on to configuring delegation settings.

Configure delegation settings
In the following steps, we assume an on-premises environment with two machines in different domains: a gateway
machine and a database server running SQL Server. For the sake of this example, we also assume the following
settings and names:
Gateway machine name: PBIEgwTestGW
Gateway service account: PBIEgwTestFrontEnd\GatewaySvc (account display name: Gateway Connector)
SQL Server data source machine name: PBIEgwTestSQL
SQL Server data source service account: PBIEgwTestBackEnd\SQLService
Given those example names and settings, use the following configuration steps:
1. Using Active Directory Users and Computers, which is a Microsoft Management Console (MMC ) snap-
in, on the domain controller for PBIEgwTestFront-end domain, make sure no delegation settings are
applied for the gateway service account.
2. Using Active Directory Users and Computers, on the domain controller for PBIEgwTestBack-end
domain, make sure no delegation settings are applied for the back-end service account. In addition, make
sure that the "msDS -AllowedToActOnBehalfOfOtherIdentity" attribute for this account is also not set. You
can find this attribute in the "Attribute Editor", as shown in the following image:

3. Create a group in Active Directory Users and Computers, on the domain controller for
PBIEgwTestBack-end domain. Add the gateway service account to this group as shown in the following
image. The image shows a new group called ResourceDelGroup and the gateway service account
 GatewaySvc added to this group.

4. Open command prompt and run the following commands n the domain controller for PBIEgwTestBack-
end domain to update msDS -AllowedToActOnBehalfOfOtherIdentity attribute of the back-end service
account:

$c = Get-ADGroup ResourceDelGroup
Set-ADUser SQLService -PrincipalsAllowedToDelegateToAccount $c

5. You can verify that the update is reflected in the "Attribute Editor" tab in the properties for the back-end
service account in Active Directory Users and Computers.
Finally, on the machine running the gateway service ( PBIEgwTestGW in our example), the gateway service
account must be granted the local policy "Impersonate a client after authentication". You can perform/verify this
with the Local Group Policy Editor (gpedit).
1. On the gateway machine, run: gpedit.msc.
2. Navigate to Local Computer Policy > Computer Configuration > Windows Settings > Security
Settings > Local Policies > User Rights Assignment, as shown in the following image.
3. From the list of policies under User Rights Assignment, select Impersonate a client after
authentication.

4. Right-click and open the Properties for Impersonate a client after authentication, and check the list of
accounts. It must include the gateway service account ( PBIEgwTestFront-end \GatewaySvc ).
5. From the list of policies under User Rights Assignment, select Act as part of the operating system
(SeTcbPrivilege). Ensure that the gateway service account is included in the list of accounts as well.
6. Restart the On-premises data gateway service process.

Running a Power BI report

After all the configuration steps outlined earlier in this article have been completed, you can use the Manage
Gateway page in Power BI to configure the data source. Then under its Advanced Settings enable SSO, and
publish reports and datasets binding to that data source.
This configuration will work in most cases. However, with Kerberos there can be different configurations depending
on your environment. If the report still won't load, you'll need to contact your domain administrator to investigate
further.

Next steps
For more information about the On-premises data gateway and DirectQuery, check out the following
resources:
On-premises data gateway
DirectQuery in Power BI
Data sources supported by DirectQuery
DirectQuery and SAP BW
DirectQuery and SAP HANA
 Use Security Assertion Markup Language (SAML) for
single sign-on (SSO) from Power BI to on-premises
data sources
3/20/2019 • 6 minutes to read • Edit Online

Use Security Assertion Markup Language (SAML ) to enable seamless single sign-on connectivity. Enabling SSO
makes it easy for Power BI reports and dashboards to refresh data from on-premises sources.

Supported data sources

We currently support SAP HANA with SAML. For more information about setting up and configuring single sign-
on for SAP HANA using SAML, see the topic SAML SSO for BI Platform to HANA in the SAP HANA
documentation.
We support additional data sources with Kerberos.
Note that for HANA it is highly recommended that encryption be enabled before establishing a SAML SSO
connection (that is, you should configure the HANA server to accept encrypted connections and also configure the
Gateway to use encryption when communicating with your HANA server). The HANA ODBC driver is not able to
encrypt SAML assertions by default, and without encryption turned on the signed SAML assertion will be sent
from the Gateway to the HANA server "in the clear" and be vulnerable to interception and reuse by third parties.

Configuring the gateway and data source

To use SAML, you must establish a trust relationship between the HANA server(s) for which you want to enable
SSO and the Gateway, which serves as the SAML Identity Provider (IdP ) in this scenario. There are various ways
to establish this relationship, such as importing the Gateway IdP's x509 certificate into the HANA server(s) trust
store, or by having the Gateway's X509 certificate signed by a root Certification Authority (CA) trusted by the
HANA server(s). We describe the latter approach in this guide, but you may use another approach if it is more
convenient.
Also note that while this guide uses OpenSSL as the HANA server's cryptographic provider, it is also possible to
use the SAP Cryptographic Library (also known as CommonCryptoLib or sapcrypto) instead of OpenSSL to
complete the setup steps where we establish the trust relationship. Refer to the official SAP documentation for
further information.
The following steps describe how to establish a trust relationship between a HANA server and the Gateway IdP
by signing the Gateway IdP's X509 certificate using a Root CA trusted by the HANA server.
1. Create the Root CA's X509 certificate and private key. For example, to create the Root CA's X509 certificate
and private key in .pem format:

openssl req -new -x509 -newkey rsa:2048 -days 3650 -sha256 -keyout CA_Key.pem -out CA_Cert.pem -extensions
v3_ca

Add the certificate (for example, CA_Cert.pem) to the HANA server's Trust Store so that the HANA server will
trust any certificates signed by the Root CA you have just created. The location of your HANA server's Trust Store
can be found by examining the ssltruststore configuration setting. If you have followed the SAP Documentation
covering how to configure OpenSSL, your HANA server may already trust a Root CA you that can reuse. See how
How to Configure Open SSL for SAP HANA Studio to SAP HANA Server for details. If you have multiple HANA
servers that you want to enable SAML SSO for, make sure that each of the servers trusts this Root CA.
1. Create the Gateway IdP's X509 certificate. For example, to create a certificate-signing request (IdP_Req.pem)
and a private key (IdP_Key.pem) that are valid for a year, execute the following command:

openssl req -newkey rsa:2048 -days 365 -sha256 -keyout IdP_Key.pem -out IdP_Req.pem -nodes

Sign the certificate-signing request using the Root CA you've configured your HANA server(s) to trust. For
example, to sign IdP_Req.pem using CA_Cert.pem and CA_Key.pem (the certificate and key of the Root CA),
execute the following command:

openssl x509 -req -days 365 -in IdP_Req.pem -sha256 -extensions usr_cert -CA CA_Cert.pem -CAkey CA_Key.pem -
CAcreateserial -out IdP_Cert.pem

The resulting IdP certificate will be valid for a year (see the -days option). Now, import your IdP's certificate in
HANA Studio to create a new SAML Identity Provider.
1. In SAP HANA Studio, right-click your SAP HANA server, then navigate to Security > Open Security
Console > SAML Identity Provider > OpenSSL Cryptographic Library.

2. Select Import, navigate to IdP_Cert.pem,and import it.

3. In SAP HANA Studio, select the Security folder.

4. Expand Users then select the user you want to map your Power BI user to.
5. Select SAML then Configure.

6. Select the identity provider you created in step 2. For External Identity , enter the Power BI user's UPN,
then select Add.
Now that you have the certificate and identity configured, you convert the certificate to a pfx format and configure
the gateway machine to use the certificate.
1. Convert the certificate to the pfx format by running the following command. Note that this command sets
"root" as the pfx file's password.

openssl pkcs12 -export -out samltest.pfx -in IdP_Cert.pem -inkey IdP_Key.pem -passin pass:root -passout
pass:root

2. Copy the pfx file to the gateway machine:

a. Double-click samltest.pfx, then select Local Machine > Next.
b. Enter the password, then select Next.
c. Select Place all certificates in the following store, then Browse > Personal > OK.
d. Select Next , then Finish.

3. Grant the gateway service account access to the private key of the certificate:
a. On the gateway machine, run the Microsoft Management Console (MMC ).

b. Under File , select Add/Remove Snap-in.

 c. Select Certificates > Add , then select Computer account > Next.
d. Select Local Computer > Finish > OK.
e. Expand Certificates > Personal > Certificates , and find the certificate.
f. Right-click the certificate and navigate to All Tasks > Manage Private Keys.

g. Add the gateway service account to the list. By default, the account is NT
SERVICE\PBIEgwService. You can find out what account is running gateway service by running
services.msc and find On-premises data gateway service.

Finally, follow these steps to add the certificate thumbprint to the gateway configuration.
1. Run the following PowerShell command to list the certificates on your machine.

Get-ChildItem -path cert:\LocalMachine\My

2. Copy the thumbprint for the certificate you created.

3. Navigate to the gateway directory, which defaults to C:\Program Files\On-premises data gateway.
4. Open PowerBI.DataMovement.Pipeline.GatewayCore.dll.config, and find the
*SapHanaSAMLCertThumbprint* section. Paste in the thumbprint you copied.
5. Restart the gateway service.

Running a Power BI report

Now you can use the Manage Gateway page in Power BI to configure the data source, and under its Advanced
Settings , enable SSO. Then you can publish reports and datasets binding to that data source.
Troubleshooting
After configuring SSO, you might see the following error in the Power BI portal: "The credentials provided cannot
be used for the SapHana source." This error indicates that the SAML credential was rejected by SAP HANA.
Authentication traces provide detailed information for troubleshooting credential issues on SAP HANA. Follow
these steps to configure tracing for your SAP HANA server.
1. On the SAP HANA server, turn on the authentication trace by running the following query.

ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini', 'SYSTEM') set ('trace', 'authentication') =

'debug' with reconfigure

2. Reproduce the issue you have been facing.

3. In HANA Studio, open the administration console, and go to the Diagnosis Files tab.
4. Open the latest indexserver trace and search for SAMLAuthenticator.cpp.
You should find a detailed error message that indicates the root cause, like the following example.

[3957]{-1}[-1/-1] 2018-09-11 21:40:23.815797 d Authentication SAMLAuthenticator.cpp(00091) : Element

'{urn:oasis:names:tc:SAML:2.0:assertion}Assertion', attribute 'ID': '123123123123123' is not a valid
value of the atomic type 'xs:ID'.
[3957]{-1}[-1/-1] 2018-09-11 21:40:23.815914 i Authentication SAMLAuthenticator.cpp(00403) : No valid
SAML Assertion or SAML Protocol detected

5. Once the troubleshooting is complete, turn off the authentication trace by running the following query.

ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini', 'SYSTEM') UNSET ('trace', 'authentication');

Next steps
For more information about the On-premises data gateway and DirectQuery, check out the following
resources:
On-premises data gateway
DirectQuery in Power BI
Data sources supported by DirectQuery
DirectQuery and SAP BW
DirectQuery and SAP HANA
 Configuring proxy settings for the On-premises data
gateway
3/12/2019 • 3 minutes to read • Edit Online

Your work environment may require that you go through a proxy to access the internet. This could prevent the
On-premises data gateway from connecting to the service.

Does your network use a proxy?

The following post on superuser.com discusses how you can try to determine if you have a proxy on your
network.
How do I know what proxy server I'm using? (SuperUser.com)

Configuration file location and default configuration

Proxy information is configured within a .NET configuration file. The location, and file names, will be different
depending on the gateway you are using.
On-premises data gateway
There are two main configuration files that are involved with the On-premises data gateway.
Configuration
The first is for the configuration screens that actually configure the gateway. If you are having issues configuring
the gateway, this is the file you will want to look at.

C:\Program Files\On-premises data gateway\enterprisegatewayconfigurator.exe.config

Windows Service
The second is for the actual windows service that interacts with the Power BI service, and handles the requests.

C:\Program Files\On-premises data gateway\Microsoft.PowerBI.EnterpriseGateway.exe.config

Configuring proxy settings

The default proxy configuration is the following.

<system.net>
<defaultProxy useDefaultCredentials="true" />
</system.net>

The default configuration works with Windows authentication. If your proxy uses another form of
authentication, you will need to change the settings. If you are not sure, you should contact your network
administrator. Basic proxy authentication is not recommended, and attempting to use basic proxy authentication
may cause proxy authentication errors that result in the gateway not being properly configured. Use a stronger
proxy authentication mechanism to resolve.
In addition to using default credentials, you can add a element to define proxy server settings in more detail. For
example, you can specify that your On-premises data gateway should always use the proxy even for local
resources by setting the bypassonlocal parameter to false. This can help in troubleshooting situations if you
want to track all https requests originating from an On-premises data gateway in the proxy log files. The
following sample configuration specifies that all requests must go through a specific proxy with the IP address
192.168.1.10.

<system.net>
<defaultProxy useDefaultCredentials="true">
<proxy
autoDetect="false"
proxyaddress="http://192.168.1.10:3128"
bypassonlocal="false"
usesystemdefault="true"
/>
</defaultProxy>
</system.net>

Additionally, for the gateway to connect to cloud data sources through a proxy, update the following file:
C:\Program Files\On-premises data gateway\Microsoft.Mashup.Container.NetFX45.exe. In the file, expand the
<configurations> section to include the contents below, and update proxyaddress attribute with your proxy
information. The following example would route all cloud requests via a specific proxy with the IP address
192.168.1.10.

<configuration>
<system.net>
<defaultProxy useDefaultCredentials="true" enabled="true">
<proxy proxyaddress=""http://192.168.1.10:3128" bypassonlocal="true" />
</defaultProxy>
</system.net>
</configuration>

To learn more about the configuration of the proxy elements for .NET configuration files, see defaultProxy
Element (Network Settings).

Changing the gateway service account to a domain user

When configuring the proxy settings to use default credentials, as explained above, you may encounter
authentication issues with your proxy. This is because the default service account is the Service SID and not an
authenticated domain user. You can change the service account of the gateway to allow proper authentication
with your proxy.

NOTE
It is recommended that you use a managed service account to avoid having to reset passwords. Learn how to create a
managed service account within Active Directory.

Change the On-premises data gateway service account

1. Change the Windows service account for the On-premises data gateway service.
The default account for this service is NT SERVICE\PBIEgwService. You will want to change this to a
domain user account within your Active Directory domain. Or, you will want to use a managed service
account to avoid having to change the password.
You will want to change the account on the Log On tab within the properties of the Windows service.
2. Restart the On-premises data gateway service.
From an admin command prompt, issue the following commands.

net stop PBIEgwService

net start PBIEgwService

3. Start the On-premises data gateway configurator. You can select the windows start button and search
for On-premises data gateway.
4. Sign in to Power BI.
5. Restore the gateway using your recovery key.
This will allow the new service account to be able to decrypt stored credentials for data sources.

NOTE
When you change the service account directly using Services Control panel, it does not update ACLs automatically. You
need to ensure that new service account has access to the installation files and folder. You can find Gateway Installation
folder under C:\Program Files\On-premises data gateway.

Next steps
On-premises data gateway (personal mode) Firewall information
More questions? Try the Power BI Community
 High availability clusters for On-premises data
gateway
2/13/2019 • 5 minutes to read • Edit Online

You can create high availability clusters of On-premises data gateway installations, to ensure your
organization can access on-premises data resources used in Power BI reports and dashboards. Such clusters allow
gateway administrators to group gateways to avoid single points of failure in accessing on-premises data
resources. The Power BI service always uses the primary gateway in the cluster, unless it’s not available. In that
case, the service switches to the next gateway in the cluster, and so on.
This article describes the steps you can take to create a high availability cluster of On-premises data gateways and
shares best practices when setting them up. High availability gateway clusters require the November 2017 update
to On-premises data gateway, or later.

Setting up high availability clusters of gateways

During the On-premises data gateway installation process, you can specify whether the gateway should be
added to an existing gateway cluster.

To add a gateway to an existing cluster, you must provide the Recovery key for the primary gateway instance for
the cluster you want the new gateway to join. The primary gateway for the cluster must be running the gateway
update from November 2017 or later.

Managing a gateway cluster

Once a gateway cluster consists of two or more gateways, all gateway management operations, such as adding a
data source or granting administrative permissions to a gateway, apply to all gateways that are part of the cluster.
When administrators use the Manage gateways menu item, found under the gear icon in the Power BI service,
they see the list of registered clusters or individual gateways, but do not see the individual gateway instances that
are members of the cluster.
All new Scheduled Refresh requests and DirectQuery operations are automatically routed to the primary
instance of a given gateway cluster. If the primary gateway instance is not online, the request is routed to another
gateway instance in the cluster.

Distribute requests traffic across all gateways in a cluster

You can choose to allow traffic to be distributed across all gateways in a cluster. In the Manage gateways page in
the Power BI service, when you click on a gateway cluster in the list on the left navigation tree, you can enable the
option to "Distribute requests across all active gateways in this cluster."

PowerShell support for gateway clusters

PowerShell scripts are available in the On-premises data gateway installation folder. By default, that folder is
C:\Program Files\On-premises data gateway. You must be using PowerShell version 5 or newer for these scripts
to work correctly. The PowerShell scripts let users perform the following operations:
Retrieve the list of gateway clusters available for a user
Retrieve the list of gateway instances registered in a cluster, as well as their online or offline status
Modify the enable/disable status for a gateway instance within a cluster, as well as other gateway properties
Delete a gateway
To run the PowerShell commands in the table, you first need to take the following steps: :
1. Open a PowerShell command window, as an Administrator
2. Then run the following one-time PowerShell command (this presumes you've never run PowerShell
commands on the current machine):
 Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Force

3. Next, navigate to the On-premises data gateway installation folder in the PowerShell window, and import
the necessary module using the following command:

Import-Module .\OnPremisesDataGatewayHAMgmt.psm1

Once those steps are complete, you can use the commands in the following table to manage your gateway clusters.

COMMAND DESCRIPTION PARAMETERS

Login-OnPremisesDataGateway This command allows a user to log in to AAD username and password (provided
manage his or her On-premises data as part of the command execution, not
gateway clusters. You must run this initial invocation)
command and log in before other high
availability commands can work
properly. Note: the AAD auth token
acquired as part of a Login call is only
valid for 1 hour, after which it expires.
You can re-run the Login command to
acquire a new token.

Get-OnPremisesDataGatewayClusters Retrieves the list of gateway clusters for Optionally, you can pass formatting
the logged in user. parameters to this command for better
readability, such as Format-Table -
AutoSize -Wrap

Get-OnPremisesDataClusterGateways Retrieves the list of gateways within the -ClusterObjectID xyz (where xyz is
specified cluster, as well as additional replaced with an actual cluster object ID
information for each gateway value, which can be retrieved using the
(online/offline status, machine name, so Get-OnPremisesDataGatewayClusters
on) command)

Set-OnPremisesDataGateway Lets you set property values for a given -ClusterObjectID xyz (xyz, should be
gateway within a cluster, including the replaced with an actual cluster object ID
ability to Enable/Disable a specific value, which can be retrieved using the
gateway instance Get-OnPremisesDataGatewayClusters
command) -GatewayObjectID abc (abc
should be replaced with an actual
gateway object ID value, which can be
retrieved using the Get-
OnPremisesDataClusterGateways
command, given a cluster object ID)

Get-OnPremisesDataGatewayStatus Lets you retrieve the status for a given -ClusterObjectID xyz (xyz should be
gateway instance within a cluster replaced with an actual cluster object ID
value, which can be retrieved using the
Get-OnPremisesDataGatewayClusters
command) -GatewayObjectID abc (abc
should be replaced with an actual
gateway object ID value, which can be
retrieved using the Get-
OnPremisesDataClusterGateways
command, given a cluster object ID)
 COMMAND DESCRIPTION PARAMETERS

Remove-OnPremisesDataGateway Lets you remove a gateway instance -ClusterObjectID xyz (xyz should be
from a cluster - note that the primary replaced with an actual cluster object ID
gateway in the cluster cannot be value, which can be retrieved using the
removed until all other gateways in the Get-OnPremisesDataGatewayClusters
cluster are removed. command) -GatewayObjectID abc (abc
should be replaced with an actual
gateway object ID value, which can be
retrieved using the Get-
OnPremisesDataClusterGateways
command, given a cluster object ID)

Next steps
Manage your data source - Analysis Services
Manage your data source - SAP HANA
Manage your data source - SQL Server
Manage your data source - Oracle
Manage your data source - Import/Scheduled refresh
On-premises data gateway in-depth
On-premises data gateway (personal mode)
Configuring proxy settings for the On-premises data gateway
Use Kerberos for SSO (single sign-on) from Power BI to on-premises data sources
More questions? Try the Power BI Community
 On-premises data gateway
1/30/2019 • 12 minutes to read • Edit Online

The On-premises data gateway acts as a bridge, providing quick and secure data transfer between on-
premises data (data that is not in the cloud) and the Power BI, Microsoft Flow, Logic Apps, and
PowerApps services.
You can use a single gateway with different services at the same time. If you are using Power BI as well as
PowerApps, a single gateway can be used for both. It is dependent on the account you sign in with.

NOTE
The On-premises data gateway implements data compression, and transport encryption, in all modes.

Requirements
Minimum Requirements:
.NET 4.6 Framework
64-bit version of Windows 7 / Windows Server 2008 R2 (or later)
Recommended:
8 Core CPU
8 GB Memory
64-bit version of Windows 2012 R2 (or later)
Related Considerations:
The gateway cannot be installed on a domain controller
If you are planning to use Windows authentication, make sure you install the gateway on a computer
that is a member of the same Active Directory environment as the data source(s).
You shouldn't install a gateway on a computer, such a laptop, that may be turned off, asleep, or not
connected to the Internet because the gateway can't run under any of those circumstances. In addition,
gateway performance might suffer over a wireless network.
Analysis Services is not required to use the gateway. You can use the gateway to connect to an Analysis
Services data source.
Limitations of Analysis Services live connections
You can use a live connection against tabular or multidimensional instances.

SERVER VERSION REQUIRED SKU

2012 SP1 CU4 or later Business Intelligence and Enterprise SKU

2014 Business Intelligence and Enterprise SKU

2016 Standard SKU or higher

Cell level Formatting and translation features are not supported.

 Actions and Named Sets are not exposed to Power BI, but you can still connect to multidimensional
cubes that also contain Actions or Named sets and create visuals and reports.

List of available data source types

USER CONFIGURED MANUAL OR
DATA SOURCE LIVE/DIRECTQUERY SCHEDULED REFRESH

Analysis Services Tabular Yes Yes

Analysis Services Multidimensional Yes Yes

File No Yes

Folder No Yes

IBM DB2 Yes Yes

IBM Informix Database No Yes

IBM Netezza Yes Yes

Impala Yes Yes

MySQL No Yes

OData No Yes

ODBC No Yes

Oledb No Yes

Oracle Yes Yes

PostgresSQL No Yes

SAP BW Yes Yes

SAP HANA Yes Yes

SharePoint list (on-premises) No Yes

Snowflake Yes Yes

Spark Yes Yes

SQL Server Yes Yes

Sybase No Yes

Teradata Yes Yes

Web No Yes
Download and install the On-premises data gateway
To download the gateway, select Data Gateway under the Downloads menu. Download the On-premises
data gateway.
Note that you update the On-premises data gateway by installing the gateway again, as described in this
section. As long as you install a newer version of the gateway, your existing settings are retained. If you
install the same version, it treats this as a complete reinstall, and your settings are not retained.

Install the On-premises data gateway

The data gateway installs and runs on your computer. It is best to install the gateway on a machine that
can be left running all the time.

NOTE
The gateway is supported only on 64-bit Windows operating systems.

For Power BI, the first choice you have to make is the mode of the gateway.
On-premises data gateway: Multiple users can share and reuse a gateway in this mode. This
gateway can be used by Power BI, PowerApps, Flow or Logic Apps. For Power BI, this includes support
for both schedule refresh and DirectQuery
Personal: This is for Power BI only and can be used as an individual without any administrator
configuration. This can only be used for on-demand refresh and schedule refresh. This selection
launchs installation of the personal gateway.
There are a few things to note about installing either mode of the gateway:
both gateways require 64-bit Windows operating systems
gateways can’t be installed on a domain controller
you can install up to two On-premises data gateways on the same computer, one running in each
mode (personal and standard).
you cannot have more than one gateway running in the same mode on the same computer.
you can install multiple On-premises data gateways on different computers, and manage them all from
the same Power BI gateway management interface (excluding personal, see the following bullet point)
You can only have one Personal mode gateway running for each Power BI user. If you install another
Personal mode gateway for the same user, even on a different computer, the most recent installation
replaces the existing previous installation.
Here are a few things to consider before installing the gateway.
If you are installing on a laptop, and your laptop is turned off, not connected to the internet, or asleep
the gateway won’t work and the data in the cloud service will not be synchronized with your on-
premises data.
If your machine is connected to a wireless network, the gateway may perform more slowly which will
cause it to take longer to synchronize the data in the cloud service with your on-premises data.
Once the gateway is installed, you will need to sign in with your work or school account.

After you are signed in, you will have the option to configure a new gateway, or to migrate, restore, or take
over an existing gateway.
Configure a new gateway
1. Enter a name for the gateway
2. Enter a recovery key. This has to be a minimum of 8 characters.
3. Select Configure.

NOTE
The recovery key will be needed if you ever need to migrate, restore or take over a gateway. Be sure to keep this
key in a safe place.
Migrate, restore or take over an existing gateway
You will need to select the gateway you want to recover and supply the recovery key that was used to first
create the gateway.
On-premises data gateway connected
Once the gateway is configured, you will be able to make use of it to connect to on-premises data sources.
If the gateway is for Power BI, you will need to add your data sources to the gateway within the Power BI
service. This is done within the Manage gateways area. You can refer to the manage data sources
articles for more information.
For PowerApps, you will need to select a gateway for a defined connection for supported data sources.
For Flow and Logic Apps, this gateway is ready to be used with your on-premises connections.

Install the gateway in personal mode

NOTE
The Personal version of gateway only works with Power BI.

After the personal gateway is installed, you will need to launch the Power BI Gateway - Personal
Configuration Wizard.

You will then need to sign into Power BI to register the gateway with the cloud service.
You will also need to supply the windows user name and password that the windows service will run as.
You can specify a different Windows account from your own. The gateway service will run using this
account.

After the installation is complete, you will need to go to your datasets within Power BI and make sure
credentials are entered for your on-premises data sources.

Storing encrypted credentials in the cloud

When you add a data source to the gateway, you need to provide credentials for that data source. All
queries to the data source will run using these credentials. The credentials are encrypted securely, using
asymmetric encryption so that they cannot be decrypted in the cloud, before they are stored in the cloud.
The credentials are sent to the machine, running the gateway, on-premises where they are decrypted
when the data sources are accessed.

Sign in account
Users sign in with either a work or school account. This account is your organization account. If you
signed up for an Office 365 offering and didn’t supply your actual work email, it may look like
[email protected]. Your account is stored within a tenant in Azure Active Directory (AAD ).
In most cases, your AAD account’s UPN will match the email address.
Windows Service account
The On-premises data gateway is configured to use NT SERVICE\PBIEgwService for the Windows
service logon credential. By default, it has the right of Log on as a service, in the context of the machine
that you are installing the gateway on. The account is not the same account used to connect to on-
premises data sources. The account is also not the work or school account that you sign in to cloud
services with.

NOTE
If you selected personal mode, you configure the Windows service account separately.

If you encounter authentication issues with your proxy server, try changing the Windows service account
to a domain user or managed service account. For more information, see proxy configuration.

Ports
The gateway creates an outbound connection to Azure Service Bus. It communicates on outbound ports:
TCP 443 (default), 5671, 5672, 9350 through 9354. The gateway does not require inbound ports.
It is recommended that you whitelist the IP addresses, for your data region, in your firewall. You can
download the Microsoft Azure Datacenter IP list, which is updated weekly. The gateway will communicate
with Azure Service Bus using the IP address along with the fully qualified domain name (FQDN ). If you
are forcing the gateway to communicate using HTTPS it will strictly use FQDN only, and no
communication will happen using IP addresses.

NOTE
The IP Addresses listed in the Azure Datacenter IP list are in CIDR notation. For example, 10.0.0.0/24 does not
mean 10.0.0.0 through 10.0.0.24. Learn more about the CIDR notation.

Here is a listing of the fully qualified domain names used by the gateway.

DOMAIN NAMES OUTBOUND PORTS DESCRIPTION

*.download.microsoft.com 80 HTTP used to download the installer.

*.powerbi.com 443 HTTPS

*.analysis.windows.net 443 HTTPS

*.login.windows.net 443 HTTPS

*.servicebus.windows.net 5671-5672 Advanced Message Queuing

Protocol (AMQP)

*.servicebus.windows.net 443, 9350-9354 Listeners on Service Bus Relay over

TCP (requires 443 for Access Control
token acquisition)

*.frontend.clouddatahub.net 443 HTTPS

*.core.windows.net 443 HTTPS

 DOMAIN NAMES OUTBOUND PORTS DESCRIPTION

login.microsoftonline.com 443 HTTPS

*.msftncsi.com 443 Used to test internet connectivity if

the gateway is unreachable by the
Power BI service.

*.microsoftonline-p.com 443 Used for authentication depending

on configuration.

NOTE
Traffic going to visualstudio.com or visualstudioonline.com are for app insights and are not required for the
gateway to function.

Forcing HTTPS communication with Azure Service Bus

You can force the gateway to communicate with Azure Service Bus using HTTPS instead of direct TCP.
using HTTPS may have an impact on performance. To do so, modify the
Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file by changing the value from
AutoDetect to Https , as shown in the code snippet directly following this paragraph. That file is located
(by default) at C:\Program Files\On-premises data gateway.

<setting name="ServiceBusSystemConnectivityModeString" serializeAs="String">

<value>Https</value>
</setting>

The value for the ServiceBusSystemConnectivityModeString parameter is case-sensitive. Valid values are
AutoDetect and Https.
Alternatively, you can force the gateway to adopt this behavior using the gateway user interface. In the
gateway user interface select Network, then toggle the Azure Service Bus connectivity mode to On.
Once changed, when you select Apply (a button that only appears when you make a change), the
gateway Windows service restarts automatically, so the change can take effect.
For future reference, you can restart the gateway Windows service from the user interface dialog by
selecting Service Settings then select Restart Now.
Support for TLS 1.2
By default, the On-premises data gateway uses Transport Layer Security (TLS ) 1.2 to communicate with
the Power BI service. To ensure all gateway traffic uses TLS 1.2, you might have to add or modify the
following registry keys on the machine running the gateway service:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]"SchUseStrongCrypto"=dword
:00000001

NOTE
Adding or modifying these registry keys applies the change to all .NET applications. For information about registry
changes that affect TLS for other applications, see Transport Layer Security (TLS) registry settings.

How to restart the gateway

The gateway runs as a windows service. You can start and stop it like any windows service. Here is how
you can do it from the command prompt.
1. On the machine where the gateway is running, launch an admin command prompt.
2. Use the following command to stop the service.
net stop PBIEgwService
3. Use the following command to start the service.
net start PBIEgwService

How the gateway works

Let’s first look at what happens when a user interacts with an element connected to an on-premises data
source.

NOTE
For Power BI, you will need to configure a data source for the gateway.

1. A query will be created by the cloud service, along with the encrypted credentials for the on-premises
data source, and sent to the queue for the gateway to process.
2. The gateway cloud service will analyze the query and will push the request to the Azure Service Bus.
3. The On-premises data gateway polls the Azure Service Bus for pending requests.
4. The gateway gets the query, decrypts the credentials and connects to the data source(s) with those
credentials.
5. The gateway sends the query to the data source for execution.
6. The results are sent from the data source, back to the gateway, and then onto the cloud service. The
service then uses the results.

Limitations and Considerations

Azure Information Protection is not currently supported.
Access Online is not currently supported.
R scripts are supported only when the gateway is run in personal mode.

Tenant level administration

As a tenant admin, you can see all On-premises data gateways installed within your tenant and manage
them. This capability is currently in public preview. For more information, see the Power Platform Admin
Center documentation.
Alternatively, If you’re a tenant administrator, we recommend that you ask the users in your organization
to add you as an administrator to every gateway they install. This allows you to manage all the gateways
in your organization through the Gateway Settings page or through PowerShell commands.

Enabling outbound Azure connections

The On-premises data gateway relies on Azure Service Bus for cloud connectivity and correspondingly
establishes outbound connections to its associated Azure region. By default, this is the location of your
Power BI tenant. See Where is my Power BI tenant located? If a firewall is blocking outbound connections,
you must configure the firewall to allow outbound connections from the On-premises data gateway to its
associated Azure region. See Microsoft Azure Datacenter IP Ranges for details about the IP address
ranges of each Azure data center.

NOTE
The IP address ranges might change over time, so make sure you download the latest information on a regular
basis.

Troubleshooting
If you’re having trouble when installing and configuring a gateway, be sure to see Troubleshooting the
On-premises data gateway. If you think you are having an issue with your firewall, see the firewall or
proxy section in the troubleshooting article.
If you think you are encountering proxy issues, with the gateway, see Configuring proxy settings for the
Power BI gateways.

Next steps
Manage your data source - Analysis Services
Manage your data source - SAP HANA
Manage your data source - SQL Server
Manage your data source - Oracle
Manage your data source - Import/Scheduled refresh
On-premises data gateway in-depth
On-premises data gateway (personal mode) - the new version of the personal gateway
Configuring proxy settings for the On-premises data gateway
More questions? Try the Power BI Community
 On-premises data gateway in-depth
3/22/2019 • 13 minutes to read • Edit Online

It's possible for users in your organization to access on-premises data (to which they already have access
authorization), but before those users can connect to your on-premises data source, an On-premises data
gateway needs to be installed and configured. The gateway facilitates quick and secure behind-the-scenes
communication between a user in the cloud, to your on-premises data source, and then back to the cloud.
Installing and configuring a gateway is usually done by an administrator. It may require special knowledge of
your on-premises servers and in some cases may require Server Administrator permissions.
This article doesn’t provide step-by-step guidance on how to install and configure the gateway. For that, be sure
to see On-premises data gateway. This article is meant to provide you with an in-depth understanding of how
the gateway works. We’ll also go into some detail about usernames and security in both Azure Active Directory
and Analysis Services, and how the cloud service uses the e-mail address a user sign in with, the gateway, and
Active Directory to securely connect to and query your on-premises data.

How the gateway works

Let’s first look at what happens when a user interacts with an element connected to an on-premises data source.

NOTE
For Power BI, you will need to configure a data source for the gateway.

1. A query will be created by the cloud service, along with the encrypted credentials for the on-premises data
source, and sent to the queue for the gateway to process.
2. The gateway cloud service will analyze the query and will push the request to the Azure Service Bus.
3. The On-premises data gateway polls the Azure Service Bus for pending requests.
4. The gateway gets the query, decrypts the credentials and connects to the data source(s) with those
 credentials.
5. The gateway sends the query to the data source for execution.
6. The results are sent from the data source, back to the gateway, and then onto the cloud service. The service
then uses the results.

List of available data source types

USER CONFIGURED MANUAL OR
DATA SOURCE LIVE/DIRECTQUERY SCHEDULED REFRESH

Analysis Services Tabular Yes Yes

Analysis Services Multidimensional Yes Yes

File No Yes

Folder No Yes

IBM DB2 Yes Yes

IBM Informix Database No Yes

IBM Netezza Yes Yes

Impala Yes Yes

MySQL No Yes

OData No Yes

ODBC No Yes

Oledb No Yes

Oracle Yes Yes

PostgresSQL No Yes

SAP BW Yes Yes

SAP HANA Yes Yes

SharePoint list (on-premises) No Yes

Snowflake Yes Yes

Spark Yes Yes

SQL Server Yes Yes

Sybase No Yes
 USER CONFIGURED MANUAL OR
DATA SOURCE LIVE/DIRECTQUERY SCHEDULED REFRESH

Teradata Yes Yes

Web No Yes

Sign in account
Users will sign in with either a work or school account. This is your organization account. If you signed up for an
Office 365 offering and didn’t supply your actual work email, it may look like [email protected].
Your account, within a cloud service, is stored within a tenant in Azure Active Directory (AAD ). In most cases,
your AAD account’s UPN will match the email address.

Authentication to on-premises data sources

A stored credential will be used to connect to on-premises data sources from the gateway except Analysis
Services. Regardless of the individual user, the gateway uses the stored credential to connect.

Authentication to a live Analysis Services data source

Each time a user interacts with Analysis Services, the effective username is passed to the gateway and then onto
your on-premises Analysis Services server. The user principal name (UPN ), typically the email address you sign
into the cloud with, is what we will pass to Analysis Services as the effective user. The UPN is passed in the
connection property EffectiveUserName. This email address should match a defined UPN within the local Active
Directory domain. The UPN is a property of an Active Directory account. That Windows account then needs to
be present in an Analysis Services role to have access to the server. The login will not be successful if no match is
found in Active Directory.
Analysis Services can also provide filtering based on this account. The filtering can occur with either role based
security, or row -level security.

Role-based security
Models provide security based on user roles. Roles are defined for a particular model project during authoring
in SQL Server Data Tools – Business Intelligence (SSDT-BI), or after a model is deployed, by using SQL Server
Management Studio (SSMS ). Roles contain members by Windows username or by Windows group. Roles
define permissions a user has to query or perform actions on the model. Most users will belong to a role with
Read permissions. Other roles are meant for administrators with permissions to process items, manage
database functions, and manage other roles.

Row-level security
Row -level security is specific to Analysis Services row -level security. Models can provide dynamic, row -level
security. Unlike having at least one role in which users belong to, dynamic security is not required for any tabular
model. At a high-level, dynamic security defines a user’s read access to data right down to a particular row in a
particular table. Similar to roles, dynamic row -level security relies on a user’s Windows username.
A user’s ability to query and view model data are determined first by the roles their Windows user account are a
member of and second, by dynamic row -level security, if configured.
Implementing role and dynamic row -level security in models are beyond the scope of this article. You can learn
more at Roles (SSAS Tabular) and Security Roles (Analysis Services - Multidimensional Data) on MSDN. And,
for the most in-depth understanding of tabular model security, download and read the Securing the Tabular BI
Semantic Model whitepaper.

What about Azure Active Directory?

Microsoft cloud services use Azure Active Directory to take care of authenticating users. Azure Active Directory
is the tenant that contains usernames and security groups. Typically, the email address a user signs in with is the
same as the UPN of the account.
What is my local Active Directory’s role?
For Analysis Services to determine if a user connecting to it belongs to a role with permissions to read data, the
server needs to convert the effective username passed from AAD to the gateway, and onto the Analysis Services
server. The Analysis Services server passes the effective username to a Windows Active Directory domain
controller (DC ). The Active Directory DC then validates the effective username is a valid UPN, on a local account,
and returns that user’s Windows username back to the Analysis Services server.
EffectiveUserName cannot be used on a non-domain joined Analysis Services server. The Analysis Services
server must be joined to a domain to avoid any login errors.

How do I tell what my UPN is?

You may not know what your UPN is, and you may not be a domain administrator. You can use the following
command from your workstation to find out the UPN for your account.

whoami /upn

The result will look similar to an email address, but this is the UPN that is on your local domain account. If you
are using an Analysis Services data source for live connections, this must match what was passed to
EffectiveUserName from the gateway.

Mapping usernames for Analysis Services data sources

Power BI allows for mapping usernames for Analysis Services data sources. You can configure rules to map a
username logged in with Power BI to a name that is passed for EffectiveUserName on the Analysis Services
connection. The map user names feature is a great way to work around when your username in AAD doesn't
match a UPN in your local Active Directory. For example, if your email address is
[email protected], you could map it to [email protected], and that value would be passed to
the gateway. You can learn more about how to map user names.

Synchronize an on-premises Active Directory with Azure Active

Directory
You would want your local Active Directory accounts to match Azure Active Directory if you are going to be
using Analysis Services live connections. As the UPN has to match between the accounts.
The cloud services only know about accounts within Azure Active Directory. It doesn’t matter if you added an
account in your local Active Directory, if it doesn’t exist in AAD, it cannot be used. There are different ways that
you can match your local Active Directory accounts with Azure Active Directory.
1. You can add accounts manually to Azure Active Directory.
You can create an account on the Azure portal, or within the Microsoft 365 admin center, and the account
name matches the UPN of the local Active Directory account.
2. You can use the Azure AD Connect tool to synchronize local accounts to your Azure Active Directory
 tenant.
The Azure AD Connect tool provides options for directory synchronization and setting up authentication,
including password hash sync, pass-through authentication, and federation. If you are not a tenant admin
or a local domain administrator, you will need to contact your IT admin to get this configured.
Using Azure AD Connect ensures that the UPN will match between AAD and your local Active Directory.

NOTE
Synchronizing accounts with the Azure AD Connect tool will create new accounts within your AAD tenant.

Now, this is where the gateway comes in

The gateway acts as a bridge between the cloud and your on-premises server. Data transfer between the cloud
and the gateway is secured through Azure Service Bus. The Service Bus creates a secure channel between the
cloud and your on-premises server through an outbound connection on the gateway. There are no inbound
connections that you need to open on your on-premises firewall. Power BI manages the Service Bus for you, so
there are no additional costs or configuration steps required.
If you have an Analysis Services data source, you’ll need to install the gateway on a computer joined to the same
forest/domain as your Analysis Services server.
The closer the gateway is to the server, the faster the connection will be. If you can get the gateway on the same
server as the data source, that is best to avoid network latency between the gateway and the server.

What to do next?
After you get the gateway installed, you will want to create data sources for that gateway. You can add data
sources within the Manage gateways screen. For more information, see the manage data sources articles.
Manage your data source - Analysis Services
Manage your data source - SAP HANA
Manage your data source - SQL Server
Manage your data source - Oracle
Manage your data source - Import/Scheduled refresh

Where things can go wrong

Sometimes installing the gateway fails. Or, maybe the gateway seems to install ok, but the service is still unable
to work with it. In many cases, it’s something simple, like the password for the credentials the gateway uses to
sign into the data source.
In other cases, there might be issues with the type of e-mail address users sign in with, or Analysis Services’
inability to resolve an effective username. If you have multiple domains with trusts between them, and your
gateway is in one and Analysis Services in another, this sometimes can cause some problems.
Rather than go into troubleshooting gateway issues here, we’ve put a series of troubleshooting steps into
another article; Troubleshooting the On-premises data gateway. Hopefully, you won’t have any problems. But if
you do, understanding how all of this works and the troubleshooting article should help.

Sign in account
Users sign in with either a work or school account. This account is your organization account. If you signed up
for an Office 365 offering and didn’t supply your actual work email, it may look like
[email protected]. Your account is stored within a tenant in Azure Active Directory (AAD ). In
most cases, your AAD account’s UPN will match the email address.

Windows Service account

The On-premises data gateway is configured to use NT SERVICE\PBIEgwService for the Windows service
logon credential. By default, it has the right of Log on as a service, in the context of the machine that you are
installing the gateway on. The account is not the same account used to connect to on-premises data sources. The
account is also not the work or school account that you sign in to cloud services with.

NOTE
If you selected personal mode, you configure the Windows service account separately.

If you encounter authentication issues with your proxy server, try changing the Windows service account to a
domain user or managed service account. For more information, see proxy configuration.

Ports
The gateway creates an outbound connection to Azure Service Bus. It communicates on outbound ports: TCP
443 (default), 5671, 5672, 9350 through 9354. The gateway does not require inbound ports.
It is recommended that you whitelist the IP addresses, for your data region, in your firewall. You can download
the Microsoft Azure Datacenter IP list, which is updated weekly. The gateway will communicate with Azure
Service Bus using the IP address along with the fully qualified domain name (FQDN ). If you are forcing the
gateway to communicate using HTTPS it will strictly use FQDN only, and no communication will happen using
IP addresses.

NOTE
The IP Addresses listed in the Azure Datacenter IP list are in CIDR notation. For example, 10.0.0.0/24 does not mean
10.0.0.0 through 10.0.0.24. Learn more about the CIDR notation.

Here is a listing of the fully qualified domain names used by the gateway.

DOMAIN NAMES OUTBOUND PORTS DESCRIPTION

*.download.microsoft.com 80 HTTP used to download the installer.

*.powerbi.com 443 HTTPS

*.analysis.windows.net 443 HTTPS

*.login.windows.net 443 HTTPS

*.servicebus.windows.net 5671-5672 Advanced Message Queuing Protocol

(AMQP)

*.servicebus.windows.net 443, 9350-9354 Listeners on Service Bus Relay over

TCP (requires 443 for Access Control
token acquisition)

*.frontend.clouddatahub.net 443 HTTPS

 DOMAIN NAMES OUTBOUND PORTS DESCRIPTION

*.core.windows.net 443 HTTPS

login.microsoftonline.com 443 HTTPS

*.msftncsi.com 443 Used to test internet connectivity if the

gateway is unreachable by the Power
BI service.

*.microsoftonline-p.com 443 Used for authentication depending on

configuration.

NOTE
Traffic going to visualstudio.com or visualstudioonline.com are for app insights and are not required for the gateway to
function.

Forcing HTTPS communication with Azure Service Bus

You can force the gateway to communicate with Azure Service Bus using HTTPS instead of direct TCP. using
HTTPS may have an impact on performance. To do so, modify the
Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file by changing the value from AutoDetect
to Https , as shown in the code snippet directly following this paragraph. That file is located (by default) at
C:\Program Files\On-premises data gateway.

<setting name="ServiceBusSystemConnectivityModeString" serializeAs="String">

<value>Https</value>
</setting>

The value for the ServiceBusSystemConnectivityModeString parameter is case-sensitive. Valid values are
AutoDetect and Https.
Alternatively, you can force the gateway to adopt this behavior using the gateway user interface. In the gateway
user interface select Network, then toggle the Azure Service Bus connectivity mode to On.
Once changed, when you select Apply (a button that only appears when you make a change), the gateway
Windows service restarts automatically, so the change can take effect.
For future reference, you can restart the gateway Windows service from the user interface dialog by selecting
Service Settings then select Restart Now.
Support for TLS 1.2
By default, the On-premises data gateway uses Transport Layer Security (TLS ) 1.2 to communicate with the
Power BI service. To ensure all gateway traffic uses TLS 1.2, you might have to add or modify the following
registry keys on the machine running the gateway service:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]"SchUseStrongCrypto"=dword:00000
001

NOTE
Adding or modifying these registry keys applies the change to all .NET applications. For information about registry
changes that affect TLS for other applications, see Transport Layer Security (TLS) registry settings.

How to restart the gateway

The gateway runs as a windows service. You can start and stop it like any windows service. Here is how you can
do it from the command prompt.
1. On the machine where the gateway is running, launch an admin command prompt.
2. Use the following command to stop the service.
net stop PBIEgwService
3. Use the following command to start the service.
net start PBIEgwService

Next steps
Troubleshooting the On-premises data gateway
Azure Service Bus
Azure AD Connect
More questions? Try the Power BI Community
 On-premises data gateway (personal mode)
2/13/2019 • 7 minutes to read • Edit Online

You can use on-premises data sources, and create Power BI reports and dashboards, using a gateway. A
gateway is software that facilitates access to data that is stored on a private, on-premises network, then enables
you to use that data in online services like the Power BI service. The On-premises data gateway (personal
mode) is a recently released update to the Power BI gateway that allows individuals to install a gateway on their
own computer, and gain access to on-premises data.

NOTE
The On-premises data gateway (personal mode) replaces the previously supported version of the personal gateway,
which is called Power BI Gateway - Personal. The previous personal gateway will continue working only until July 31,
2017. See the sections below for information on how to update to the new version.

Features of the On-premises data gateway (personal mode)

With the release of the On-premises data gateway (personal mode), a collection of improvements and
features are now available. In the previous version of the personal gateway (which is called Power BI Gateway
- Personal), its implementation imposed some limitations. As with many Power BI products, we listened to
customer needs, requests, and how they used the product. As a result, the On-premises data gateway
(personal mode) has been redesigned from the ground up, and includes the following features and
improvements:
Improved reliability - the new version of the personal gateway has improved reliability over the previous
 version, due to code and structural software improvements.
Enhanced extensibility - as part of the structural software improvements, additional features can easily be
added to the personal gateway as they become available.
Delete personal gateway from the Power BI service - with the new version, you can now delete your
personal gateway from within the Power BI service.
Configuration and service logs - the new version lets you easily export configuration and service logs to a
.zip file, with a single click.

Installing On-premises data gateway (personal mode)

To install the On-premises data gateway (personal mode) without having the previous version of the
gateway installed, select the gear icon in the Power BI service and select Data Gateway.

You can also download the gateway from this location. You can follow the installation steps, and since the
installation process allows you to install either version of the gateway (the standard gateway, which can be
shared with others, or personal mode), make sure you select On-premises data gateway (personal mode)
when prompted for which version of the gateway you want to install.
Updating from the previous personal gateway
If you already have the Power BI Gateway - personal gateway installed, you'll be prompted to install the new
and enhanced version of the personal gateway when you view Datasets under Settings in the Power BI
service.
When you select a dataset, and then select Gateway connection you're notified that the new and enhanced
version of the personal gateway is available. When you do, select Install now.

NOTE
If you're running the previous version of Power BI Gateway - personal as an elevated process, make sure you start the
new gateway installation process elevated as well, so your dataset credentials can be automatically updated. Otherwise,
you'll have to update dataset credentials manually.

You'll be taken through the update process, after which you'll see that the installation was successful. Don't close
things out yet, there's one last step.
Here's the last step. Once the new personal gateway is installed (and the last installation screen still visible), sign
in to the Power BI service, and wait until you see that the gateway is online, as shown in the following image.
If you've updated the personal gateway on the same machine as the previous gateway is installed, your
credentials will update automatically, and all refresh activities will go through the new gateway. If the previous
gateway was installed on a different machine, you'll be asked to update your credentials on certain datasets. In
the previous image, notice the list of datasets in the window; the list will show datasets that might require
updated credentials. Each dataset listed is a direct link that you simply click on to easily update your credentials.
That's it - almost. With the new gateway installed, you no longer need to previous version installed on your
machine, so you should uninstall it. You can do this by searching for Power BI Gateway - personal on your
machine, and uninstalling it.
Determining which version of the personal gateway you have installed
To determine which version of the personal gateway you currently have installed, you can do the following:
The previous version of the personal gateway is called Power BI Gateway - Personal and uses the Power BI
icon in its installation dialog.
The new version of the personal gateway is called On-premises data gateway (personal mode) and uses
the gateway icon (a cloud with an up-and-down arrow along the bottom).
You can go to Add/Remove Programs and see whether Power BI Gateway - Personal appears on the list,
and if so, you have the previous version of the personal gateway installed.

Using Fast Combine with the personal gateway

If you were using Fast Combine with the previous gateway, you'll need to take the following steps to re-enable
Fast Combine to work with the On-premises data gateway (personal mode):
1. Using File Explorer, open the following file:

%localappdata%\Microsoft\On-premises data gateway (personal

mode)\Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config

2. At the bottom of the file, add the following text:

<setting name="EnableFastCombine" serializeAs="String">

<value>true</value>
</setting>

3. Once complete, the setting will take effect in approximately one minute. To check that it's working
properly, try an on-demand refresh in the Power BI service to confirm that Fast Combine is working.

Limitations and considerations

There are a few things to consider when using the On-premises data gateway (personal mode), as described
in the following list.
If you're using Windows Hello or a pin to sign in to Windows, you might run into the following error:
The user account you selected does not match the requirements of the application. Please use a
different account.
To remedy that error, select Use a different account and sign in again.
The following data sources are currently not supported for the On-premises data gateway (personal mode):
ADO.NET
CurrentWorkbook
FTP
 HDFS
SAP BusinessObjects
Spark
Support for Spark is planned for the second half of the 2017 calendar year.

Frequently Asked Questions (FAQ)

Can I run the On-premises data gateway (personal mode) side by side with the On-premises data
gateway (previously known as the Enterprise version of the gateway)?
Answer: Yes, with the new version, both can run simultaneously.
Can I run the On-premises data gateway (personal mode) as a service?
Answer: No. the On-premises data gateway (personal mode) can only run as an application. If
you need to run the gateway as a service and/or in admin mode, you'll need to consider the On-
premises data gateway (previously known as the Enterprise gateway).
How often is the On-premises data gateway (personal mode) updated?
Answer: We plan to update the personal gateway monthly.
Why am I asked to update my credentials?
Answer: Many situations can trigger a request for credentials. The most common is that you've re-
installed the On-premises data gateway (personal mode) on a different machine than your Power
BI - personal gateway. It could also be an issue in the data source, and Power BI failed to perform a
test connection, or a timeout or a system error occurred. You can update your credentials in the Power
BI service by going to the gear icon and selecting Settings then Datasets, and finding the dataset in
question and clicking on update credentials.
How much time will my previous personal gateway be offline during the upgrade?
Answer: Upgrading the personal gateway to the new version should only take few minutes.
What happens if I don't migrate to the new personal gateway by July 31st, 2017?
Answer: If you’re refreshing your reports with the current gateway, your refreshes will stop. The only
way to set up a new refresh schedule will be by installing and configuring the new gateway.
I'm using R script. Is that supported?
Answer: R scripts are supported for personal mode.
Why am I not seeing the message to update my gateway in the Power BI service?
Answer: Most likely, this is because you have one or more datasets that include a data source that is
still currently not supported.

Next steps
Configuring proxy settings for the Power BI Gateways
More questions? Try the Power BI Community
 Use custom data connectors with the On-premises
data gateway
1/14/2019 • 2 minutes to read • Edit Online

Data Connectors for Power BI enable you to connect to and access data from an application, service, or data
source. You can develop custom data connectors and use them in Power BI Desktop.
To learn more about how to develop custom data connectors for Power BI, check out our documentation here.
When you build reports in Power BI Desktop that use custom data connectors, you can use the On-premises data
gateway to refresh those reports from the Power BI service.

Here is a guide on how to enable and use this capability

When you install the July 2018 version of the On-premises data gateway or a later version, you can see a
“Connectors” tab in the configurator with an option to choose a folder from which to load custom connectors.
Make sure you pick a folder that can be accessed by the user running the gateway service (which is “NT
SERVICE\PBIEgwService” by default). The gateway automatically loads the custom connector files located in that
folder, and you should see them in the list of the data connectors.

If you are using the personal version of the On-premises data gateway, you should be able at this point to upload
your Power BI report to the Power BI service and use the gateway to refresh it.
For the enterprise version of the gateway, you still need to create a data source for your custom connector. In the
gateway settings page in the Power BI service, you should see a new option when you select the gateway cluster to
allow using custom connectors with this cluster. Make sure all gateways in the cluster have the July 2018 update
release or later for this option to be available. Now select that option to enable using custom connectors with this
cluster.

When this option is enabled, you now see your custom connectors as available data sources that you can create
under this gateway cluster. Once you create a data source using your new custom connector, you can now refresh
Power BI reports using that custom connector in the Power BI service.
Considerations and limitations
Make sure the folder you create is accessible to the background gateway service. Typically, folders under your
user’s Windows folder or system folders won’t be accessible. The gateway configurator shows a message if the
folder is not accessible (this doesn't apply for the personal version of the gateway)
For custom connectors to work with the On-premises data gateway, they need to implement a “TestConnection”
section in the custom connector’s code. This is not required when using custom connectors with Power BI
Desktop. You can have one that works with the Desktop, but not with the gateway for this reason. Please refer to
this documentation on how to implement a TestConnection section.

Next steps
Manage your data source - Analysis Services
Manage your data source - SAP HANA
Manage your data source - SQL Server
Manage your data source - Oracle
Manage your data source - Import/Scheduled refresh
On-premises data gateway in-depth
On-premises data gateway (personal mode)
Configuring proxy settings for the On-premises data gateway
Use Kerberos for SSO (single sign-on) from Power BI to On-premises data sources
More questions? Try the Power BI Community
 Troubleshooting the On-premises data gateway
2/13/2019 • 25 minutes to read • Edit Online

This article discusses some common issues when using the On-premises data gateway.

NOTE
If you encounter an issue that is not listed below, you can ask for further assistance in the following locations.
For Power BI, you can use the communities site or you can create a support ticket.
For PowerApps, you can use the communities site or you can create a support ticket.
For Microsoft Flow, you can use the communities site of you can create a support ticket.
For Logic Apps, you can submit a support ticket through the Azure portal.

Update to the latest version

A lot of issues can surface when the gateway version is out of date. It is a good general practice to make
sure you are on the latest version. If you haven't updated the gateway for a month, or longer, you may want
to consider installing the latest version of the gateway and see if you can reproduce the issue.

Common issues
Here are a few common issues and resolutions that have helped a number of customers in environments
that restrict internet access.
Authentication to proxy server
Your proxy may require authentication from a domain user account. By default, the gateway uses a Service
SID for the windows service log on user. Changing the log on user to a domain user can help with this. For
more information, see Changing the gateway service account to a domain user.
Your proxy only allows ports 80 and 443 traffic
Some proxies restrict traffic to only ports 80 and 443. By default, communication to Azure Service Bus will
occur on ports other than 443.
You can force the gateway to communicate with Azure Service Bus using HTTPS instead of direct TCP. You
will need to modify the Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file. Change the
value from AutoDetect to Https . This file is located, by default, at C:\Program Files\On-premises data
gateway.

<setting name="ServiceBusSystemConnectivityModeString" serializeAs="String">

<value>Https</value>
</setting>

Installation
Error: Failed to add user to group. (-2147463168 PBIEgwService Performance Log Users )
You may receive this error if you are trying to install the gateway on a domain controller. Deploying on a
domain controller is not supported. You will need to deploy the gateway on a machine that is not a domain
controller.
Installation fails
You may encounter installation failures if the anti-virus software on the installation machine is out of date.
You can either update the anti-virus installation, or disable anti-virus only for the duration of the gateway
installation to complete, then re-enable anti-virus.

Configuration
How to restart the gateway
The gateway runs as a Windows service, so you can start and stop it in a few ways. For example, you can
open a command prompt with elevated permissions on the machine where the gateway is running and
then run either of these commands:
To stop the service, run this command:

net stop PBIEgwService

To start the service, run this command:

net start PBIEgwService

Log file configuration

The gateway service logs are categorized into three buckets: information, error, and network. This
categorization provides a better troubleshooting experience that allows you to focus on a specific area,
depending on the error or issue. You can see the three categories in the following snippet from the gateway
configuration file: GatewayInfo.log,GatewayErrors.log,GatewayNetwork.log .

<system.diagnostics>
<trace autoflush="true" indentsize="4">
<listeners>
<remove name="Default" />
<add name="ApplicationFileTraceListener"

type="Microsoft.PowerBI.DataMovement.Pipeline.Common.Diagnostics.RotatableFilesManagerTraceListener,
Microsoft.PowerBI.DataMovement.Pipeline.Common"
initializeData="%LOCALAPPDATA%\Microsoft\On-premises data
gateway\,GatewayInfo.log,GatewayErrors.log,GatewayNetwork.log,20,50" />
</listeners>
</trace>
</system.diagnostics>

This file is located by default at: \Program Files\On-premises data

gateway\Microsoft.PowerBI.EnterpriseGateway.exe.config. To configure the number of log files to retain,
change the first number (20 in this example): GatewayInfo.log,GatewayErrors.log,GatewayNetwork.log,20,50 .
Error: Failed to create a gateway. Try again
All of the details are available, but the call to the Power BI service returned an error. The error and an
activity id are displayed. This could happen for different reasons. You can collect, and review, the logs, as
mentioned below, to get more details.
This could also be due to proxy configuration issues. The user interface does now allow for proxy
configuration. You can learn more about making proxy configuration changes
Error: Failed to update gateway details. Please try again
Information was received from the Power BI service to the gateway. The information was passed onto the
local windows service, but it failed to return. Alternatively, a symmetric key generation failed. The inner
exception is displayed under Show details. To get more details, you can collect and review the logs
mentioned below.
Error: Power BI service reported local gateway as unreachable. Restart the gateway and try again
At the end of configuration, the Power BI service is called again to validate the gateway. The Power BI
service does not report the gateway as live. Restarting the windows service may allow the communication
to be successful. You can collect, and review, the logs, as mentioned below, to get more details.
Script error during sign into Power BI
You may receive a script error when signing into Power BI as part of the On-premises data gateway
configuration. Installing the following security update resolves the issue. This can be installed via Windows
Update.
MS16-051: Security update for Internet Explorer: May 10, 2016 (KB 3154070)
Gateway configuration failed with a null reference exception
You may encounter an error similar to the following.

Failed to update gateway details. Please try again.

Error updating gateway configuration.

This includes a stack trace, and that stack trace may include the following message.

Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.CouldNotUpdateGatewayConfigurationException:
Error updating gateway configuration. ----> System.ArgumentNullException: Value cannot be null.
Parameter name: serviceSection

If you are upgrading from an older gateway, we preserve the config file. There may be a section that is
missing. When the gateway tries to read it, we can get the above null reference exception.
To correct this, do the following steps.
1. Uninstall the gateway.
2. Delete the following folder.

c:\Program Files\On-premises data gateway

3. Reinstall the gateway.

4. Optionally apply the recovery key to restore an existing gateway.

Support for TLS 1.2

By default, the On-premises data gateway uses Transport Layer Security (TLS ) 1.2 to communicate with the
Power BI service. To ensure all gateway traffic uses TLS 1.2, you might have to add or modify the following
registry keys on the machine running the gateway service:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]"SchUseStrongCrypto"=dword:
00000001
 NOTE
Adding or modifying these registry keys applies the change to all .NET applications. For information about registry
changes that affect TLS for other applications, see Transport Layer Security (TLS) registry settings.

Data sources
Error: Unable to Connect. Details: "Invalid connection credentials"
Within Show details, it displays the error message received from the data source. For SQL Server, you see
something like the following.

Login failed for user 'username'.

Verify that you have the correct username and password. Also, verify that those credentials can successfully
connect to the data source. Make sure the account being used matches the Authentication Method.
Error: Unable to Connect. Details: "Cannot connect to the database"
We were able to connect to the server, but not to the database supplied. Verify the name of the database,
and that the user credential as the proper permission to access that database.
Within Show details, it displays the error message received from the data source. For SQL Server, you see
something like the following.

Cannot open database "AdventureWorks" requested by the login. The login failed. Login failed for user
'username'.

Error: Unable to Connect. Details: "Unknown error in data gateway"

This error could occur for different reasons. Be sure to validate that you can connect to the data source from
the machine hosting the gateway. This could be the result of the server not being accessible.
Within Show details, you can see an error code of DM_GWPipeline_UnknownError.
You can also look in the Event Logs > Applications and Services Logs > On-premises data gateway
Service for more details.
Error: We encountered an error while trying to connect to . Details: "We reached the data gateway, but
the gateway can't access the on-premises data source."
We were unable to connect to the specified data source. Be sure to validate the information provided for
that data source.
Within Show details, you can see an error code of
DM_GWPipeline_Gateway_DataSourceAccessError.
If the underlying error message is similar to the following, this means that the account you are using for the
data source is not a server admin for that Analysis Services instance. Learn more

The 'CONTOSO\account' value of the 'EffectiveUserName' XML for Analysis property is not valid.

If the underlying error message is similar to the following, it could mean that the service account for
Analysis Services may be missing the token-groups-global-and-universal (TGGAU ) directory attribute.

The username or password is incorrect.

Domains with Pre-Windows 2000 compatibility access have the TGGAU attribute enabled. However, most
newly created domains do not enable this attribute by default. You can read more about this here.
You can confirm this by doing the following.
1. Connect to the Analysis Services machine within SQL Server Management Studio. Within the
Advanced connection properties, include EffectiveUserName for the user in question and see if this
reproduces the error.
2. You can use the dsacls Active Directory tool to validate whether the attribute is listed. This is a tool
found on a domain controller. You need to know what the distinguished domain name is for the
account and pass that to the tool.

dsacls "CN=John Doe,CN=UserAccounts,DC=contoso,DC=com"

You want to see something similar to the following in the results.

Allow BUILTIN\Windows Authorization Access Group

SPECIAL ACCESS for tokenGroupsGlobalAndUniversal
READ PROPERTY

To correct this issue, you need to enable TGGAU on the account used for the Analysis Services windows
service.
Another possibility for username or password incorrect
This error could also be caused if the Analysis Services server is in a different domain than the users and
there is not a two-way trust established.
You need to work with your domain administrators to verify the trust relationship between domains.
Unable to see the data gateway data sources in the 'Get Data' experience for Analysis Services from the Power BI service
Make sure that your account is listed in the Users tab of the data source within the gateway configuration.
If you don't have access to the gateway check with the administrator of the gateway and ask them to verify.
Only accounts in the Users list can see the data source listed in the Analysis Services list.
Error: You don't have any gateway installed or configured for the data sources in this dataset
Ensure that you have added one or more data sources to the gateway, as described in Add a data source. If
the gateway doesn't appear in the admin portal under Manage gateways, try clearing your browser cache
or signing out of the service then signing back in.

Datasets
Error: There is not enough space for this row
This occurs if you have a single row greater than 4 MB in size. You need to determine what the row is from
your data source and attempt to filter it out or reduce the size for that row.
Error: The server name provided doesn't match the server name on the SQL Server SSL Certificate
This can occur when the certificate CN is for the servers fully qualified domain name (FQDN ), but you only
supplied the NetBIOS name for the server. This causes a mismatch for the certificate. To resolve this issue,
you need to make the server name within the gateway data source, and the PBIX file, to use the FQDN of
the server.
I don't see the On-premises data gateway present when configuring scheduled refresh
This could be because of a few different scenarios.
1. The server and database name don't match between what was entered in Power BI Desktop and the
data source configured for the gateway. These need to be the same values. They are not case-sensitive.
2. Your account is not listed in the Users tab of the data source within the gateway configuration. You need
to get with the administrator of the gateway to be added to that list.
3. Your Power BI Desktop file has multiple data sources within it and not all of those data sources are
configured with the gateway. You need to have each data source defined with the gateway for the
gateway to show up within Scheduled Refresh.
Error: The received uncompressed data on the gateway client has exceeded the limit
The exact limitation is 10 GB of uncompressed data per table. If you are hitting this issue, there are good
options to optimize and avoid the issue. In particular, reducing the use of highly constant, long string values
and instead using a normalized key or removing the column (if not in use) helps.

Reports
Report could not access the data source because you do not have access to our data source via an On-
premises data gateway
This is usually caused by one of the following.
1. The data source information does not match what is in the underlying dataset. The server and database
name need to match between the data source defined for the On-premises data gateway and what you
supply within Power BI Desktop. If you use an IP Address in Power BI Desktop, the data source, for the
On-premises data gateway, needs to use an IP Address as well.
2. There is not a data source available on any gateway within your organization. You can configure the data
source on a new, or existing On-premises data gateway.
Error: Data source access error. Please contact the gateway administrator
If this report is making use of a live Analysis Services connection, you could be encountering an issue with
a value being passed to EffectiveUserName that is either not valid or doesn't have permissions on the
Analysis Services machine. Typically, an authentication issue is due to the fact that the value being passed
for EffectiveUserName doesn't match a local user principal name (UPN ).
To confirm this, you can do the following.
1. Find the effective username within the gateway logs.
2. Once you have the value being passed, validate that it is correct. If it is your user, you can use the
following command from a command prompt to see the UPN. The UPN looks like an email address.

whoami /upn

Optionally, you can see what Power BI gets from Azure Active Directory.
1. Browse to https://developer.microsoft.com/graph/graph-explorer.
2. Select Sign in in the upper right.
3. Run the following query. You see a rather large JSON response.

https://graph.windows.net/me?api-version=1.5

4. Look for userPrincipalName.

If your Azure Active Directory UPN doesn't match your local Active Directory UPN, you can use the Map
usernames feature to replace it with a valid value. Or you can work with either your tenant admin or local
Active Directory admin, to get your UPN changed.

Firewall or Proxy
For information on providing proxy information for your gateway, see Configuring proxy settings for the
Power BI gateways.
You can test to see if your firewall, or proxy, may be blocking connections by running Test-NetConnection
from a PowerShell prompt. This will test connectivity to the Azure Service Bus. This only tests network
connectivity and doesn't have anything to do with the cloud server service or the gateway. It helps to
determine if your machine can actually get out to the internet.

Test-NetConnection -ComputerName watchdog.servicebus.windows.net -Port 9350

NOTE
Test-NetConnection is only available on Windows Server 2012 R2 and later. It is also available on Windows 8.1 and
later. On earlier OS versions, you can use Telnet to test port connectivity.

The results should look similar to the following. The difference will be with TcpTestSucceeded. If
TcpTestSucceeded is not true, then you may be blocked by a firewall.

ComputerName : watchdog.servicebus.windows.net
RemoteAddress : 70.37.104.240
RemotePort : 5672
InterfaceAlias : vEthernet (Broadcom NetXtreme Gigabit Ethernet - Virtual Switch)
SourceAddress : 10.120.60.105
PingSucceeded : False
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded : True

If you want to be exhaustive, substitute the ComputerName and Port values with those listed for ports
The firewall may also be blocking the connections that the Azure Service Bus makes to the Azure data
centers. If that is the case, you will want to whitelist (unblock) the IP addresses for your region for those
data centers. You can get a list of Azure IP addresses here.
You can find the data center region you are in by doing the following:
1. Select the ? in the upper right of the Power BI service.
2. Select About Power BI.
3. Your data region is listed in Your data is stored in.

If you are still not getting anywhere, you could try getting a network trace using a tool like fiddler or netsh,
although these are advanced collection methods and you may need assistance in analyzing the collected
data. You can contact support for assistance.
Performance
https://www.youtube.com/embed/IJ_DJ30VNk4?showinfo=0
Performance Counters
There are a number of performance counters that can be used to gauge the activities for the gateway. These
can be helpful to understand if we have a large load of activity and may need to make a new gateway. These
counters do not reflect how long something takes.
These counters can be accessed through the Windows Performance Monitor tool.

There are general groupings of these counters.

COUNTER TYPE DESCRIPTION

ADO.NET This is used for any DirectQuery connection.

ADOMD This is used for Analysis Services 2014 and earlier.

OLEDB Certain data sources use this. This includes SAP HANA and
Analysis Service 2016 or later.

Mashup This includes any imported data source. If you are

scheduling refresh or doing an on-demand refresh, it goes
through the mashup engine.

Here is a listing of the available performance counters.

COUNTER DESCRIPTION

# of ADO.NET open connection executed / sec Number of ADO.NET open connection actions executed
per second (succeeded or failed).

# of ADO.NET open connection failed / sec Number of ADO.NET open connections actions failed per
second.

# of ADO.NET queries executed / sec Number of ADO.NET queries executed per second
(succeeded or failed).

# of ADO.NET queries failed / sec Number of ADO.NET failed queries executed per second.
COUNTER DESCRIPTION

# of ADOMD open connection executed / sec Number of ADOMD open connection actions executed
per second (succeeded or failed).

# of ADOMD open connection failed / sec Number of ADOMD open connection actions failed per
second.

# of ADOMD queries executed / sec Number of ADOMD queries executed per second
(succeeded or failed).

# of ADOMD queries failed / sec Number of ADOMD failed queries executed per second.

# of all open connection executed / sec Number of open connection actions executed per second
(succeeded or failed).

# of all open connection failed / sec Number of failed open connection actions executed per
second.

# of all queries executed / sec Number of queries executed per second (succeeded or
failed).

# of items in the ADO.NET connection pool Number of items in the ADO.NET connection pool.

# of items in the OLEDB connection pool Number of items in the OLEDB connection pool.

# of items in the Service Bus pool Number of items in the Service Bus pool.

# of Mashup open connection executed / sec Number of Mashup open connection actions executed per
second (succeeded or failed).

# of Mashup open connection failed / sec Number of Mashup open connection actions failed per
second.

# of Mashup queries executed / sec Number of Mashup queries executed per second
(succeeded or failed).

# of Mashup queries failed / sec Number of Mashup failed queries executed per second

# of OLEDB multiple result set queries failed / sec Number of multiple result sets of OLEDB failed queries
executed per second.

# of OLEDB multiple result sets of queries executed / sec Number of OLEDB multiple result sets of queries executed
per second (succeeded or failed).

# of OLEDB open connection executed / sec Number of OLEDB open connection actions executed per
second (succeeded or failed).

# of OLEDB open connection failed / sec Number of OLEDB open connection actions failed per
second.

# of OLEDB queries executed / sec Number of OLEDB multiple result sets of queries executed
per second (succeeded or failed).
 COUNTER DESCRIPTION

# of OLEDB queries failed / sec Number of OLEDB multiple result sets of failed queries
executed per second.

# of OLEDB single result set queries executed / sec Number of OLEDB single result set queries executed per
second (succeeded or failed).

# of queries failed / sec Number of failed queries executed per second.

# of single result set OLEDB queries failed / sec Number of single result set OLEDB failed queries executed
per second.

Reviewing slow performing queries

You may find that response through the gateway is slow. This could be for DirectQuery queries or when
refreshing your imported dataset. You can enable additional logging to output queries and their timings to
help understand what is performing slow. When you find a long-running query, it may require additional
modification on your data source to tune query performance. For example, adjusting indexes for a SQL
Server query.
You need to modify two configuration files to determine the duration of a query.
Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config
Within the Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file, change the
EmitQueryTraces value from False to True . This file is located, by default, at C:\Program Files\On-
premises data gateway. Enabling EmitQueryTraces begins to log queries that are sent from the gateway to a
data source.

IMPORTANT
Enabling EmitQueryTraces could increase the log size significantly depending on gateway usage. Once you are done
reviewing the logs, you can need to set EmitQueryTraces to False. It is not recommended to leave this setting
enabled long term.

<setting name="EmitQueryTraces" serializeAs="String">

<value>True</value>
</setting>

Example query entry

 DM.EnterpriseGateway Information: 0 : 2016-09-15T16:09:27.2664967Z DM.EnterpriseGateway 4af2c279-
1f91-4c33-ae5e-b3c863946c41 d1c77e9e-3858-4b21-3e62-1b6eaf28b176 MGEQ c32f15e3-699c-4360-9e61-
2cc03e8c8f4c FF59BC20 [DM.GatewayCore] Executing query (timeout=224) "<pi>
SELECT
TOP (1000001) [t0].[ProductCategoryName],[t0].[FiscalYear],SUM([t0].[Amount])
AS [a0]
FROM
(
(select [$Table].[ProductCategoryName] as [ProductCategoryName],
[$Table].[ProductSubcategory] as [ProductSubcategory],
[$Table].[Product] as [Product],
[$Table].[CustomerKey] as [CustomerKey],
[$Table].[Region] as [Region],
[$Table].[Age] as [Age],
[$Table].[IncomeGroup] as [IncomeGroup],
[$Table].[CalendarYear] as [CalendarYear],
[$Table].[FiscalYear] as [FiscalYear],
[$Table].[Month] as [Month],
[$Table].[OrderNumber] as [OrderNumber],
[$Table].[LineNumber] as [LineNumber],
[$Table].[Quantity] as [Quantity],
[$Table].[Amount] as [Amount]
from [dbo].[V_CustomerOrders] as [$Table])
)
AS [t0]
GROUP BY [t0].[ProductCategoryName],[t0].[FiscalYear] </pi>"

Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.dll.config
Within the Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.dll.config file, change the
TracingVerbosity value from 4 to 5 . This file is located, by default, at C:\Program Files\On-premises
data gateway. Changing this setting begins to log verbose entries to the gateway log. This includes entries
that show duration. You can also enable verbose entries by enabling the "Additional Logging" button in the
On-Premises Gateway application.
 IMPORTANT
Enabling TracingVerbosity to 5 could increase the log size significantly depending on gateway usage. Once you are
done reviewing the logs, you need to set TraceVerbosity to 4 . It is not recommended to leave this setting enabled
long term.

<setting name="TracingVerbosity" serializeAs="String">

<value>5</value>
</setting>

Activity Types
ACTIVITY TYPE DESCRIPTION

MGEQ Queries executed over ADO.NET. This includes

DirectQuery data sources.

MGEO Queries executed over OLEDB. This includes SAP HANA

and Analysis Services 2016.

MGEM Queries executed from the Mashup engine. This is used

with imported datasets that use scheduled refresh or
refresh on-demand.

Determine the duration of a query

To determine the time it took to query the data source, you can do the following.
1. Open the gateway log.
2. Search for an Activity Type to find the query. An example of this would be MGEQ.
3. Make a note of the second GUID as this is the request id.
4. Continue to search for MGEQ until you find the FireActivityCompletedSuccessfullyEvent entry with
the duration. You can verify the entry has the same request id. Duration is in milliseconds.

DM.EnterpriseGateway Verbose: 0 : 2016-09-26T23:08:56.7940067Z DM.EnterpriseGateway baf40f21-

2eb4-4af1-9c59-0950ef11ec4a 5f99f566-106d-c8ac-c864-c0808c41a606 MGEQ 21f96cc4-7496-
bfdd-748c-b4915cb4b70c B8DFCF12 [DM.Pipeline.Common.TracingTelemetryService] Event:
FireActivityCompletedSuccessfullyEvent (duration=5004)

NOTE
FireActivityCompletedSuccessfullyEvent is a verbose entry. This entry is not logged unless TraceVerbosity is at
level 5.

Firewall or Proxy
For information on providing proxy information for your gateway, see Configuring proxy settings for the
Power BI gateways.
You can test to see if your firewall, or proxy, may be blocking connections by running Test-NetConnection
from a PowerShell prompt. This tests connectivity to the Azure Service Bus. This only tests network
connectivity and don't have anything to do with the cloud server service or the gateway. It helps to
determine if your machine can actually get out to the internet.

Test-NetConnection -ComputerName watchdog.servicebus.windows.net -Port 9350

NOTE
Test-NetConnection is only available on Windows Server 2012 R2 and later. It is also available on Windows 8.1 and
later. On earlier OS versions, you can use Telnet to test port connectivity.

The results look similar to the following. The difference is with TcpTestSucceeded. If TcpTestSucceeded is
not true, then you may be blocked by a firewall.

ComputerName : watchdog.servicebus.windows.net
RemoteAddress : 70.37.104.240
RemotePort : 5672
InterfaceAlias : vEthernet (Broadcom NetXtreme Gigabit Ethernet - Virtual Switch)
SourceAddress : 10.120.60.105
PingSucceeded : False
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded : True

If you want to be exhaustive, substitute the ComputerName and Port values with those listed for ports
The firewall may also be blocking the connections that the Azure Service Bus makes to the Azure data
centers. If that is the case, you want to whitelist (unblock) the IP addresses for your region for those data
centers. You can get a list of Azure IP addresses here.
Network Ports Test
The network ports test is a tool to check if your gateway can access the correct ports for all remote servers
that are required by your gateway for transferring data. If the network ports test fails to connect to any of
the ports, your gateway may experience network issues. If you are currently experiencing network issues
with your gateway, run a network ports test to ensure that you have the optimal network environment.
Start a new test
To run a new network ports test, in theOn-premises data gatewayuser interface.

When executing the network ports test, your gateway retrieves a list of ports and servers from Azure
Service Bus and then it attempts to connect to all the servers and ports. When the Start new test link
reappears, the network ports test has finished executing.
Test results
A summary of the test can be seen below the Start new test link as Recent test results. The two results are
Completed (Succeeded) and Completed (Failed, see last test results). If the test succeeded, then your
gateway successfully connected to all the required ports. If the test failed, then your network environment
may be blocking these required ports and servers.
To view the results of the last completed test, select the Open last completed test results link, as seen below.
The test results open in Windows’ default text editor.
The test results list all the servers, ports, and IP addresses that are required by your gateway. If the test
results display Closed for any ports as shown below, ensure that your network environment is not blocking
the connection. You may need to contact your network administrator to open the required ports.
Kerberos
If the underlying database server and On-premises data gateway are not appropriately configured for
Kerberos Constrained Delegation, enable verbose logging on the gateway, and investigate based on the
errors/traces in the gateway’s log files as a starting point for troubleshooting.
ImpersonationLevel
The ImpersonationLevel is related to the SPN setup or the local policy setting.

[DataMovement.PipeLine.GatewayDataAccess] About to impersonate user DOMAIN\User (IsAuthenticated: True,

ImpersonationLevel: Identification)

Solution
Follow these steps to solve the issue:
1. Setup an SPN for the On-Premises Gateway
2. Setup constrained delegation in your Active Directory (AD )
FailedToImpersonateUserException: Failed to create windows identity for user userid
The FailedToImpersonateUserException happens if you are not able to impersonate on behalf of another
user. This could also happen if the account you are trying to impersonate is from another domain than the
one the gateway service domain is on (this is a limitation).
Solution
Verify that the configuration is correct as per the steps in the ImpersonationLevel section above
Ensure that the userid it's trying to impersonate is a valid AD Account
General error; 1033 error while parsing the protocol
You get the 1033 error when your external ID that is configured in SAP HANA is not matching the login if
the user is impersonated using the UPN ([email protected]). In the logs you see the “Original UPN
'[email protected]' replaced with a new UPN '[email protected]' at the top of the error logs as seen
below.”

[DM.GatewayCore] SingleSignOn Required. Original UPN '[email protected]' replaced with new UPN
'[email protected].'

Solution
SAP HANA requires the impersonated user to use the sAMAccountName attribute in AD (user
alias). If this is not correct, you see the 1033 error.

In the logs you see the sAMAccountName (alias) and not the UPN, which is the alias followed by the
domain ([email protected])

<setting name="ADUserNameReplacementProperty" serializeAs="String">

<value>sAMAccount</value>
</setting>
<setting name="ADServerPath" serializeAs="String">
<value />
</setting>
<setting name="CustomASDataSource" serializeAs="String">
<value />
</setting>
<setting name="ADUserNameLookupProperty" serializeAs="String">
<value>AADEmail</value>

[SAP AG ][LIBODBCHDB DLL ][HDBODBC ] Communication link failure;-10709 Connection failed (RTE:[-1]
Kerberos error. Major: "Miscellaneous failure [851968]", minor: "No credentials are available in the
security package
You get the -10709 Connection failed error message if your delegation is not configured correctly in AD.
Solution
Ensure you have the SAP Hana server on the delegation tab in AD for the gateway service account
Tools for troubleshooting
Collecting logs from the gateway configurator
There are several logs you can collect for the gateway, and you should always start with the logs. The
simplest way to collect logs after installing the gateway is through the user interface. In the On-premises
data gateway user interface, select Diagnostics and then select the Export logs link near the bottom of
the page, as shown in the following image.
Installer logs

%localappdata%\Temp\On-premises_data_gateway_*.log

Configuration logs

%localappdata%\Microsoft\On-premises Data Gateway\GatewayConfigurator*.log

On-premises data gateway service logs

C:\Users\PBIEgwService\AppData\Local\Microsoft\On-premises Data Gateway\Gateway*.log

Event Logs
The On-premises data gateway service event logs are present under Application and Services Logs.
Fiddler Trace
Fiddler is a free tool from Telerik that monitors HTTP traffic. You can see the back and forth with the Power
BI service from the client machine. This may show errors and other related information.

Refresh History
When using the gateway for a scheduled refresh, Refresh History can help you see what errors have
occurred, as well as provide useful data if you need to create a support request. You can view both
scheduled, as well as on-demand, refreshes. Here is how you can get to the Refresh History.
1. In the Power BI navigation pane, in Datasets, select a dataset > Open Menu > Schedule Refresh.

2. In Settings for... > Schedule Refresh, select Refresh History.

For additional information about troubleshooting refresh scenarios, take a look at the Troubleshooting
Refresh Scenarios article.

Next steps
Configuring proxy settings for the Power BI gateways
On-premises data gateway
On-premises data gateway - in-depth
Manage your data source - Analysis Services
Manage your data source - SAP HANA
Manage your data source - SQL Server
Manage your data source - Import/Scheduled refresh
More questions? Try the Power BI Community
 What is Power BI administration?
3/22/2019 • 4 minutes to read • Edit Online

Power BI administration is the management of a Power BI tenant, including the configuration of governance
policies, usage monitoring, and provisioning of licenses, capacities, and organizational resources. This article
provides an overview of administration roles, tasks, and tools; and links to articles that go into more detail.

Power BI is designed for self-service business intelligence, and the administrator is the guardian of data,
processes, and policies in the Power BI tenant. A Power BI administrator is a key member of a team that includes
BI developers, analysts, and other roles. The administrator can help support an organization to make sure that
critical goals are met:
Understand the KPIs and metrics that users actually need
Decrease the time to delivery for IT-led corporate reporting
Increase adoption and return on investment from a Power BI deployment
The job is to make business users productive and ensure security and compliance with laws and regulations.
Responsibilities may include help and support and, in many cases, assisting business users to do the right thing.

Administrator roles related to Power BI

There are several roles related to Power BI administration, which are covered in the following table.

TYPE OF ADMINISTRATOR ADMINISTRATIVE SCOPE POWER BI SCOPE

Office 365 Global Administrator Office 365 Can manage all aspects of a Power BI
tenant and other services.

Office 365 Billing Administrator Office 365 Can acquire Power BI licenses through
Office 365 subscriptions.
 TYPE OF ADMINISTRATOR ADMINISTRATIVE SCOPE POWER BI SCOPE

Power BI Service Administrator Power BI tenant Has full control over a Power BI tenant
and its administrative features (except
for licensing).

Power BI Premium Capacity A single Premium capacity Has full control over a premium
Administrator capacity and its administrative features.

Power BI Embedded Capacity A single Embedded capacity Has full control over an embedded
Administrator capacity and its administrative features.

Global Administrators in Office 365 or Azure Active Directory have administrator rights in Power BI. An Office
365 Global Administrator can assign other users to the Power BI Service Administrator role, which grants
administrative rights over Power BI features only.
Power BI Service Administrators have access to the Power BI admin portal which includes various tenant-level
settings regarding functionality, security, and monitoring. Service Administrators have full access to all resources
of a Power BI tenant. In most cases, Service Administrators identify issues and then follow up with the resource
owners to take corrective actions.
The Power BI Service Administrator role does not grant the ability to assign licenses to users or view audit logs in
Office 365. Therefore, the task of administering Power BI cannot currently be performed by users who are solely
members of the Power BI Service Administrator role.

Administrative tasks
Administrators perform many tasks to support the Power BI tenant for their organization, which are covered in
the following table.

TASK AREA TYPICAL TASKS

Manage the Power BI tenant Enable and disable key Power BI features
Report on usage and performance
Review and manage auditing of events

Acquire and assign Power BI licenses Manage user signup

Purchase and assign Pro licenses
Block users from accessing Power BI

Manage Premium capacity Acquire and work with Premium capacity

Ensure quality of service

Manage Embedded capacity Acquire Embedded capacity to simplify how ISVs and
developers use Power BI capabilities

Ensure compliance with internal policies, laws, and regulations Manage classification of business data
Help to enforce content publishing and sharing
policies
 TASK AREA TYPICAL TASKS

Manage Power BI resources Manage workspaces

Publish custom visuals
Verify codes used to embed Power BI in other
applications

Provide help and support to tenant users Troubleshoot data access and other issues

Other tasks Deploy Power BI Desktop, e.g. using System Center

Configuration Manager
Manage Power BI mobile app deployment with Intune
Manage data privacy and security, such as source data
security

Administrative tools
There are several tools related to Power BI administration, which are covered in the following table.
Administrators typically spend most of their time in the Power BI Admin portal and use other tools as necessary.

TOOL TYPICAL TASKS

Power BI Admin portal Acquire and work with Premium capacity

Ensure quality of service
Manage classification of business data
Help to enforce content publishing and sharing
policies
Manage workspaces
Publish custom visuals
Verify codes used to embed Power BI in other
applications
Troubleshoot data access and other issues

Microsoft 365 admin center Manage user signup

Purchase and assign Pro licenses
Block users from accessing Power BI

Office 365 Security & Compliance Center Review and manage auditing of events

Azure Active Directory (AAD) in the Azure portal Configure conditional access to Power BI resources
through AAD
Provision Power BI Embedded capacity

PowerShell cmdlets Manage workspaces and other aspects of Power BI

through scripts
 TOOL TYPICAL TASKS

Administrative APIs and SDK Build custom administrative tools to facilitate the work
of a Power BI admin. For example, Power BI Desktop
can use these APIs to build reports based on data
related to administration

Next steps
We hope this article gave you some quick insights into the job of the Power BI administrator, and the specific
roles, tasks, and tools that are involved. We recommend the follow articles topics to deepen your understanding.
Use the Power BI admin portal
Use PowerShell cmdlets
Power BI administration FAQ
More questions? Try asking the Power BI Community
 What is Microsoft Power BI Premium?
3/15/2019 • 3 minutes to read • Edit Online

NOTE
This article is currently being updated to describe new features, provide more details, and improve readability. For
the latest information, see Deploying and Managing Power BI Premium Capacities.

Power BI Premium provides resources dedicated to running the Power BI service for your organization. It
gives you more dependable performance and enables larger data volumes. Premium also enables
widespread distribution of content without requiring you to purchase per-user Pro licenses for content
consumers.

Premium capacity and shared capacity

You take advantage of Power BI Premium by assigning workspaces to a Premium capacity. Premium
capacity is a dedicated resource for your organization. Workspaces not assigned to a premium capacity
are in a shared capacity. With shared capacity, your workloads run on computational resources shared by
other customers.
The following image shows the relationship between Premium capacity and shared capacity, using the
Contoso organization as an example.

AREA DESCRIPTION
 AREA DESCRIPTION

(1) Items within a Premium capacity Accessing app workspaces (as members or
admins) and publishing apps requires a Power BI
Pro license.
Sharing an app requires a Pro license, but
consuming an app doesn't.
All dashboard recipients, regardless of the license
they're assigned, can set data alerts.
REST APIs for embedding use a service account
with a Pro license, rather than a user account.

(2) My workspace in shared capacity Sharing and consuming an app both require a Pro
license.

(3) App workspaces in shared capacity Any app usage requires a Pro license.

In shared capacity, Power BI puts more limits on individual users to ensure quality of experience for all
users. By default, your workspace is in a shared capacity, including your personal My workspace and App
workspaces.
The following table provides a summary of the differences between shared capacity and Premium
capacity:

SHARED CAPACITY POWER BI PREMIUM CAPACITY

Refresh rate 8/day 48/day

Isolation with dedicated hardware

Enterprise Distribution to all users

Apps and sharing

Embedded API and controls 1

Publish Power BI reports on-

premises

1 Future enhancements coming to Power BI Premium.

Premium capacity nodes
Power BI Premium is available in node configurations with different v-core capacities. For more
information about specific SKU offerings and costs, see Power BI pricing. A cost calculator is also
available. For information regarding embedded analytics capacity planning, see Planning a Power BI
Enterprise Deployment whitepaper. To summarize:
P nodes can be used for embedded or service deployments.
EM nodes can be used for embedded deployments only. EM nodes do not have access to premium
 capabilities, such as sharing apps to users that don't have a Power BI Pro license.

TOTAL V-CORES DIRECTQUERY/LI MAX

(BACKEND+FRO BACKEND V- FRONTEND V- VE CONNECTION CONCURRENT
CAPACITY NODE NTEND) CORES 1 CORES 2 LIMITS REFRESHES

EM1 (month to 1 v-core 0.5 v-cores, 0.5 v-cores 3.75 per second 1
month) 2.5-GB RAM

EM2 (month to 2 v-cores 1 v-core, 5-GB 1 v-core 7.5 per second 2

month) RAM

EM3 (month to 4 v-cores 2 v-cores, 10- 2 v-cores 15 3

month) GB RAM

P1 8 v-cores 4 v-cores, 25- 4 v-cores 30 per second 6

GB RAM

P2 16 v-cores 8 v-cores, 50- 8 v-cores 60 per second 12

GB RAM

P3 32 v-cores 16 v-cores, 16 v-cores 120 per second 24

100-GB RAM

1: Frontend v-cores are responsible for the web service. For example, dashboard and report document
management, access rights management, scheduling, APIs, uploads and downloads, and generally for
everything that relates to the user experience.
2: Backend v-cores are responsible for the heavy lifting, like query processing, cache management,
running R servers, data refresh, natural language processing, real-time feeds, and server-side rendering
of reports and images. With the backend v-cores, a certain amount of memory is reserved as well. Having
sufficient memory becomes especially important when dealing with large data models or with a large
number of active datasets.

Workloads in Premium capacity

By default, Power BI Premium and Power BI Embedded capacities support only the workload associated
with running Power BI queries in the cloud. Premium also supports additional workloads for AI,
Dataflows, and Paginated reports. Before these workloads can use your capacity's resources, they must
be enabled in the Power BI admin portal or through the Power BI REST API. Each workload has default
settings for the maximum amount of memory each workload can consume. However, you can configure
different memory consumption settings to determine how the workloads affect each other and consume
your capacity resources. To learn more, see Configure workloads.

Power BI Report Server

Power BI Premium also includes the capability to run Power BI Report Server on-premises in your
organization. To learn more, see Get started with Power BI Report Server.

Next steps
Deploying and Managing Power BI Premium Capacities
How to purchase Power BI Premium
Power BI Premium FAQ
More questions? Try asking the Power BI Community
 Microsoft Power BI Premium capacity resource
management and optimization
2/28/2019 • 7 minutes to read • Edit Online

This article describes how Power BI Premium manages resources; the article also provides examples and
troubleshooting suggestions. For an overview, see What is Power BI Premium?.

Premium capacity memory management

Premium capacity memory is consumed by:
The datasets that are loaded into memory
Dataset refresh (both scheduled and on-demand)
Workloads that the capacity supports
Report queries
When a request is issued against a published dataset in your capacity, that dataset is loaded into memory from
persistent storage (this is also called image load). Keeping the dataset loaded in memory helps in fast response to
future queries to this dataset. In addition to the memory needed for keeping the dataset loaded in the memory,
report queries and dataset refresh consume additional memory.
Dataset memory estimation
When attempting to load a dataset into memory, Power BI estimates the amount of memory that the dataset will
require to complete the requested command. Datasets in memory tend to be larger in size than they are when
saved to disk. During refresh of a dataset, Power BI requires at least double the amount of memory than required
when the dataset is idle.
Overcommitting capacity, eviction, and reloading of datasets
Power BI Premium gives you the advantage of overcommitting your capacity. For example, you can publish more
datasets than your capacity can hold. If the published datasets need more memory than what's available in the
capacity, some of the datasets are stored separately in persistent storage. The persistent storage is part of the 100
TB of storage associated with each of your capacities.
So what datasets stay in memory and what happens to the other datasets? As described earlier, when a request is
issued against a dataset, it is loaded into memory (image load). The request could be a report query or a refresh
operation. But because you can overcommit your capacity, the capacity may also face memory pressure. When a
capacity faces memory pressure, the node evicts one or more datasets from memory. Datasets that are inactive
(with no query/refresh operation currently executing) are evicted first. Then the eviction order is based on a
measure of 'least recently used' (LRU ). If new commands are issued to the evicted dataset, the service attempts to
reload the dataset into memory, potentially evicting other datasets. This behavior allows for more efficient
utilization by allowing the capacity to serve many more datasets than its memory can hold.
Loading a dataset into memory is a fairly costly operation. Depending on the dataset size, it can last from a couple
of seconds for small datasets to tens of seconds or even minutes for significant datasets like ~10-GB datasets.
Premium capacity attempts to minimize the number of times the capacity will need to be loaded by keeping the
least recently used datasets in memory for as long as possible. When additional memory is needed, some
datasets will need to be evicted and the system will attempt to choose the one that has the least impact on the
user experience. When additional memory is needed, some datasets will need to be evicted and the system will
attempt to choose the one that has the least impact on the user experience. For example, the system will avoid
evicting datasets that were actively used within the last few minutes. These datasets are likely to be queried again
very soon.
The eviction process itself is a fast operation. If the dataset is not in active use at the time of eviction, the user will
not be able to determine much impact from the eviction. However, if too many datasets are in active use at the
same time and there is not enough memory to hold them all, many evictions can occur. Too many active datasets
can lead to a ‘thrashing’ situation, where datasets are constantly being evicted and reloaded, and users could see a
noticeable drop in response times and performance.
Dataset refresh memory requirement competing with an active dataset memory requirement
Datasets can be refreshed on a schedule or on-demand by users. As described earlier, the memory required for
full refreshes is at least doubled the memory size of the loaded and idle datasets. Before refresh starts, a refresh
memory requirement is estimated. If the total memory requirement is more than the available memory in the
capacity, some datasets are evicted. Again, eviction is based on LRU.
If the required memory is not available despite eviction, the refresh is queued to be retried. The service retries
until it succeeds or a new refresh action begins.
If an interactive query is issued to any dataset in the capacity and there is not enough memory available because
of an ongoing refresh, that request fails and needs to be retried by the user.
Workloads
By default, capacities for Power BI Premium and Power BI Embedded support only the workload associated
with running Power BI queries in the cloud. We now offer preview support for two additional workloads:
Paginated reports and Dataflows. If enabled, these workloads can impact memory usage in your capacity.

CPU resource management in premium capacity

There are two primary consumers of CPU resources:
Queries from reports
Refresh (processing)
Queries from reports
Report queries consume CPU resources in your capacity. Reports with inefficient queries, or many concurrent
users, can consume a lot of CPU resources. Your existing capacity may not be sufficient to handle the load.
Refresh parallelization policy
Memory is not the only resource that can constrain dataset refresh. The number of v-cores on a server can also be
a factor. Because each refresh operation requires a certain number of v-cores, there is a limit as to how many
refreshes can run in parallel. The limit per SKU is detailed in the following table. Additional refreshes that go
beyond these limits are queued.

SKU BACKEND V-CORES MODEL REFRESH PARALLELISM

A1 0.5 1

A2 1 2

A3 2 3

A4 4 6

A5 8 12

A6 16 24
 SKU BACKEND V-CORES MODEL REFRESH PARALLELISM

EM1 0.5 1

EM2 1 2

EM3 2 3

P1 4 6

P2 8 12

P3 16 24

P4 32 48

P5 64 96

TIP
If your refreshes are delayed, check the number of parallel refreshes supported by your capacity.

Example scenarios
Here are some common scenarios and the actions taken by the service:
Twenty scheduled refreshes submitted all at the same time. Power BI attempts to start the first x refreshes at
the same time. The value for x is determined by the refresh parallelization policy for that SKU. If Power BI is
unable to obtain enough memory by evicting inactive datasets (datasets not used recently), not all x refreshes will
start at the same time. Any refresh that cannot start is queued until it can start.
Two refreshes running at the same time and there is only enough memory for one to finish. The one that
can finish starts. The other is retried later.
Large number of datasets being queried while several datasets are being refreshed. If enough memory is
not available, Power BI attempts to stop active refreshes to give priority to interactive queries. This decreases the
refresh performance.
Dataset requires too much memory to be refreshed on current capacity size. Refresh fails. No attempts are
made to obtain more memory by eviction.
Refreshing a single dataset which has a large spike in memory. If the spike is larger than the amount of
memory that can be obtained by evicting inactive datasets, refresh is retried later until there is enough memory to
handle the spike.
Query is executed for a dataset which cannot obtain enough memory by evicting all inactive datasets
and refreshes. Those queries fail. For these kinds of workload requirements, higher capacity should be
purchased.

Troubleshooting and testing

If reports are slow or unresponsive, start by testing for just one user on your report. Then start increasing the
concurrent user load to find the limit. In many cases, tuning your DAX queries can dramatically change the
performance of your reports. Query tuning also increases the number of concurrent users supported by your
capacity. Monitor your capacity to identify potential performance issues.
Use Power BI Embedded capacity in Azure to test different SKUs and determine the best Premium SKU for your
expected workload. The Power BI Embedded A4 SKU is equal to the P1, A5 = P2, and A6 = P3. In Azure you can
easily switch between SKUs by scaling up and down in the Azure portal. When you find the SKU that works best
for your workload and are done testing, you can delete the SKU.
In some cases, opening a Power BI Desktop (.pbix) file of the model on your computer and checking memory and
CPU consumption tells a lot about the issue. This doesn't help for very large models, but for some smaller models,
try opening, refreshing, and querying the model from your computer. Check the model size, memory, and CPU
consumed when you open the model. Try refreshing and querying. Use task manager to check CPU and memory
consumption for the local file. Sometimes, those metrics on your computer itself can tell that lower premium
capacity like P1/ P2 may not work for your solution.
 How to purchase Power BI Premium
3/22/2019 • 3 minutes to read • Edit Online

NOTE
This article is currently being updated to describe new features, provide more details, and improve readability.

This article describes how to purchase Power BI Premium capacity (P1-P3) for your organization. You purchase
Power BI Premium capacity in the Microsoft 365 admin center, and you manage your capacities in the Power BI
admin portal. For current pricing and planning information, see the Power BI pricing page and the Power BI
Premium calculator.
Content creators still need a Power BI Pro license, even if your organization uses Power BI Premium. Ensure you
purchase at least one Power BI Pro license for your organization.
If a Premium subscription expires, you have 30 days of full access to your capacity. After that, your content
reverts to a shared capacity. Models that are greater than 1 GB will are not supported in shared capacity.

Create a new tenant with Power BI Premium P1

If you don't have an existing tenant and want to create one, you can purchase Power BI Premium at the same
time. The following link walks you through the process of creating a new tenant and enables you to purchase
Power BI Premium: Power BI Premium P1 offer. When you create your tenant, you will automatically be assigned
to the Office 365 Global Administrator role for that tenant.

Purchase a Power BI Premium capacity for an existing organization

If you have an existing organization (tenant), you must be in the Office 365 Global Administrator role or Billing
Administrator role to purchase subscriptions and licenses. For more information, see About Office 365 admin
roles.
To purchase Premium capacity, follow these steps.
1. From within the Power BI service, select the Office 365 app picker then Admin.

Alternatively, you can browse to the Microsoft 365 admin center. You can get there by going to
 https://portal.office.com and selecting Admin.
2. Select Billing > Purchase services.
3. Under Other plans, look for Power BI Premium offerings. This will list as P1 through P3, EM3 and P1
(month to month).
4. Hover over the ellipsis (. . .) and then select Buy now.

5. Follow the steps to complete the purchase.

After you have completed the purchase, the Purchase services page shows that the item is purchased and
active.

Purchase additional capacities

Now that you have a capacity, you can add more as your needs grow. You can use any combination of Premium
capacity SKUs (P1 through P3) within your organization. The different SKUs provide different resource
capabilities.
1. In the Microsoft 365 admin center, select Billing > Purchase services.
2. Find the Power BI Premium item you want to purchase more of under Other plans.
3. Hover over the ellipsis (...) and then select Change license quantity.
4. Change the number of instances that you want to have for this item. Then select Submit when finished.

IMPORTANT
Selecting Submit charges the credit card on file.

The Purchase services page will then indicate the number of instances you have. Within the Power BI admin
portal, under Capacity settings, the available v-cores reflects the new capacity purchased.

Cancel your subscription

You can cancel your subscription from within the Microsoft 365 admin center. To cancel your Premium
subscription, do the following.
1. Browse to the Microsoft 365 admin center.
2. Select Billing > Subscriptions.
3. Select your Power BI Premium subscription from the list.
4. Select More actions > Cancel subscription.
5. The Cancel subscription page will indicate whether or not you are responsible for an early termination
fee. This page will also let you know when the data will be deleted for the subscription.
6. Read through the information, and if you want to proceed, select Cancel subscription.
When canceling or your license expires
When you cancel your Premium subscription, or your capacity license expires, you can continue to access your
Premium capacities for a period of 30 days from the date of cancellation or license expiration. After 30 days, you
will no longer be able to access your Premium capacities or workspaces in them.

Next steps
Power BI pricing page
Power BI Premium calculator
Power BI Premium FAQ
Planning a Power BI Enterprise Deployment whitepaper
More questions? Try asking the Power BI Community
 Monitor Premium capacities with the app
3/27/2019 • 12 minutes to read • Edit Online

Monitoring your capacities is essential to making informed decisions on how best to utilize your Premium
capacity resources. You can monitor capacities in the Admin portal or with the Power BI Premium Capacity
Metrics app. This article describes using the Premium Capacity Metrics app. The app provides the most in-depth
information into how your capacities are performing. For a higher level overview of average use metrics over the
last seven days, you can use the Admin portal. To learn more about monitoring in the portal, see Monitor
Premium capacities in the Admin portal.
The app is updated regularly with new features and functionality. Make sure you're running the latest version. If
you have a previous version of the app already installed, it’s best to delete it from your apps and then press
CTRL+F5 to refresh.

Install the app

You can go straight to Premium Capacity Metrics app, or install it like you do other apps in Power BI.
1. In Power BI, click Apps.

2. On the right side, click Get apps.

3. In the Apps category, search for Power BI Premium Capacity Metrics app.
4. Subscribe to install the app.
Be patient. It takes a few minutes to install and refresh metrics. If the app shows blank metrics, press F5 to refresh
your browser.

Get app refresh history

To check the last time your Premium Capacity Metrics app refreshed, click Settings > Datasets > Power BI
Premium Capacity Metrics > Refresh History.
The last refresh is shown, or click Refresh history to see scheduled and on demand refreshes.

Monitor capacities with the app

Now that you've installed the app, you can see metrics for the capacities in your organization. The app provides a
Dashboard with metrics summaries, and detailed metrics Reports.
Dashboard
To see a dashboard that summarizes key metrics for capacities for which you are an admin, in Dashboards, click
Power BI Premium Capacity Metrics. A dashboard appears.

The dashboard includes the following metrics:

Top

METRIC DESCRIPTION

Version App version.

Capacities Number of capacities for which you are admin.

Workspaces Number of workspaces in your capacities that are reporting

metrics.

System Summary

METRIC DESCRIPTION

CPU Highest Utilization Capacity Capacity with the maximum number of times CPU exceeded
80% of the thresholds in the past seven days.

CPU Highest Utilization Count Number of times CPU the named capacity exceeded 80% of
the thresholds in the past seven days.

Memory Max Utilization Capacity Capacity with the maximum number of times max memory
limit was hit in the past seven days, split into three-minute
buckets.

Memory Max Utilization Count Number of times the named capacity reached the max
memory limit in the past seven days, split into three-minute
buckets.

Dataset Summary

METRIC DESCRIPTION

Datasets Total number of datasets across all workspaces in your

capacities.

Datasets Average Size (MB) Average size of datasets across all workspaces in your
capacities.

Datasets Average Loaded Count Average count of datasets loaded into memory.

Datasets - Average Active Dataset (%) Average active datasets in the past seven days. A dataset is
defined as active if the user has interacted on the visuals with
the past three minutes.

CPU - Datasets Max (%) Max CPU consumption by dataset workload in the past seven
days.

CPU - Datasets Average (%) Average CPU consumption by dataset workload in the past
seven days.

Memory - Datasets Average (GB) Average memory consumption by dataset workload in the
past seven days.
 METRIC DESCRIPTION

Memory - Datasets Max (GB) Max memory consumption by dataset workload in the past
seven days.

Datasets Evictions Total number of datasets evicted due to memory pressure.

DirectQuery/Live High Utilization Count Number of times DirectQuery/Live connections exceeded 80%
of the thresholds in the past seven days, split into three-
minute buckets.

DirectQuery/Live Max Utilization Count Most times the DirectQuery/Live connections exceeded 80%
in the past seven days, split into one-hour buckets.

DirectQuery/Live Max High Utilization Maximum number of times DirectQuery/Live connections

exceeded 80% of the thresholds in the past seven days, split
into three-minute buckets.

DirectQuery/Live Max Occurred Time Time in UTC that DirectQuery/Live connections exceeded 80%
the most times in an hour.

Refreshes Total Total number of refreshes in the past seven days.

Refresh Reliability (%) Number of successful refreshes divided by the total number
of refreshes in the past seven days.

Refreshes Average Duration (Minutes) Average amount of time to complete refresh.

Refreshes Average Wait Time (Minutes) Average amount of time before starting refresh.

Queries Total Total number of queries run in the past seven days.

Queries Total Wait Count Total number of queries that had to wait before being
executed.

Queries Average Duration (MS) Average time taken to complete queries.

Queries Average Wait Time (MS) Average time queries waited on system resources before
being executed.

Dataflow Summary

METRIC DESCRIPTION

Dataflows Total number of dataflows across all workspaces in your

capacities.

Refreshes Total Total number of refreshes in the past seven days.

Refreshes Average Duration (Minutes) The time taken to complete the refresh.

Refreshes Average Wait Times (Minutes) The lag between the scheduled time and actual start of the
refresh.
 METRIC DESCRIPTION

CPU - Dataflows Max (%) Max CPU consumption by dataflows workload in the past
seven days.

CPU - Dataflows Average (%) Average CPU consumption by dataflows workload in the past
seven days.

Memory - Dataflows Max (GB) Max memory consumption by dataflows workload in the past
seven days.

Memory - Dataflows Average (GB) Average memory consumption by dataflows workload in the
past seven days.

Paginated Report Summary

METRIC DESCRIPTION

Paginated Reports Total number of paginated reports across all workspaces in

your capacities.

Views Total Total number of times that all reports have been viewed by
users.

Rows Total Total number of rows of data in all reports.

Total Time Total time it takes for all phases (data retrieval, processing,
and rendering) of all reports, in milliseconds.

CPU - Paginated Reports Max (%) Maximum CPU consumption by paginated report workload in
the past seven days.

CPU - Paginated Reports Average (%) Average CPU consumption by paginated report workload in
the past seven days.

Memory - Paginated Reports Max (GB) Maximum memory consumption by paginated report
workload in the past seven days.

Memory - Paginated Reports Average (GB) Average memory consumption by paginated report workload
in the past seven days.

Reports
Reports provide more detailed metrics. To see reports for capacities for which you are an admin, in Reports, click
Power BI Premium Capacity Metrics. Or, from the dashboard, click a metric cell to go to the underlying report.
At the bottom of the report, there are five tabs:
Datasets - Provides detailed metrics on the health of the Power BI datasets in your capacities.
Paginated Reports - Provides detailed metrics on the health of the paginated reports in your capacities.
Dataflows - Provides detailed refresh metrics for dataflows in your capacities.
Resource Consumption - Provides detailed resource metrics including memory and CPU high utilization.
IDs and Info - Names, IDs, and owners for capacities, workspaces, and workloads.
Each tab opens a page where you can filter metrics by capacity and date range. If no filters are selected, the report
defaults to show the past week’s metrics for all capacities that are reporting metrics.
Datasets
The Datasets page has different areas, which include Refreshes, Query Durations, Query Waits, and Datasets.
Use the buttons at the top of the page to navigate to different areas.
Refreshes area

REPORT SECTION METRICS

Refreshes Total Count: Total refreshes for each dataset.

Reliability: the percentage of refreshes that completed for
each dataset.
Avg Wait Time: The average lag between the scheduled time
and start of a refresh for the dataset, in minutes.
Max Wait Time: The maximum wait time for the dataset, in
minutes.
Avg Duration: The average duration of refresh for the dataset,
in minutes.
Max Duration: The duration of the longest-running refresh
for the dataset, in minutes.

Top 5 Datasets by Average Duration (minutes) The five datasets with the longest average refresh duration, in
minutes.

Top 5 Datasets by Average Wait Time (minutes) The five datasets with the longest average refresh wait time,
in minutes.

Hourly Refresh Count and Memory Consumption (GB) Successes, failures, and memory consumption, split into one-
hour buckets, reported in UTC time.

Hourly Average Refresh Wait Times (minutes) The average refresh wait time, split into one-hour buckets,
reported in UTC time. Multiple spikes with high refresh wait
times are indicative of the capacity running hot.

Query Durations area

REPORT SECTION METRICS

Query Durations Data in this section is sliced by datasets, workspace, and

hourly buckets in the past seven days.
Total: The total number of queries run for the dataset.
Average: The average query duration for the dataset, in
milliseconds
Max: The duration of the longest-running query in the
dataset, in milliseconds.

Query Duration Distribution The query duration histogram is bucketed by query durations
(in milliseconds)into the following categories: <= 30ms, 30-
100ms, 100-300ms, 300ms-1sec, 1sec-3sec, 3sec-10sec,
10sec-30sec, and> 30 seconds intervals. Long query
durations and long wait times are indicative of the capacity
running hot. It may also mean that a single dataset is causing
problems and further investigation is needed.

Top 5 Datasets by Average Duration The five datasets with the longest average query duration, in
milliseconds.
 REPORT SECTION METRICS

Hourly Query Duration Distributions Query counts and average duration (in milliseconds) vs.
memory consumption in GB, split into one-hour buckets,
reported in UTC time.

DirectQuery / Live Connections (> 80% Utilization) The times that a DirectQuery or live connection exceeded
80% CPU utilization, split into one-hour buckets, reported in
UTC time.

Query Waits area

REPORT SECTION METRICS

Query Wait Times Data in this section is sliced by datasets, workspace, and
hourly buckets in the past seven days.
Total: The total number of queries run for the dataset.
Wait count: The number of queries in the dataset that waited
on system resources before starting execution.
Average: The average query wait time for the dataset, in
milliseconds.
Max: The duration of the longest-waiting query in the
dataset, in milliseconds.

Top 5 Datasets by Average Wait Time The five datasets with the longest average wait time to start
executing a query, in milliseconds.

Wait Time Distributions The query duration histogram is bucketed by query durations
(in milliseconds)into the following categories: <= 50ms , 50-
100ms , 100-200ms , 200-400ms 400ms-1sec , 1 sec-5 sec
and> 5 secondsintervals.

Hourly Query Wait Time Distributions Query wait counts and average wait time (in milliseconds) vs.
memory consumption in GB, split into one-hour buckets
reported in UTC time.

Datasets area

REPORT SECTION METRICS

Dataset Sizes Max size: The maximum size of the dataset in MB for the
period shown.

Dataset Eviction Counts Total: The total number of dataset evictions for each capacity.
When a capacity faces memory pressure, the node evicts one
or more datasets from memory. Datasets that are inactive
(with no query/refresh operation currently executing) are
evicted first. Then the eviction order is based on a measure of
'least recently used' (LRU).

Hourly Loaded Dataset Counts Number of datasets loaded into memory vs. memory
consumption in GB, split into one-hour buckets, reported in
UTC time.

Hourly Dataset Evictions and Memory Consumption Dataset evictions vs. memory consumption in GB, split into
one-hour buckets, reported in UTC time.
 REPORT SECTION METRICS

Consumed Memory Percentages Total active datasets in memory as a percentage of total

memory. The delta between Active and All define datasets
that can be evicted. Shown hourly, for the previous seven
days.

Paginated Reports
REPORT SECTION METRICS

Overall usage Total Views: The number of times that the report has been
viewed by users.
Row Count: The number of rows of data in the report.
Retrieval (avg): The average amount of time it takes to
retrieve data for the report, in milliseconds. Long durations
can indicate slow queries or other data source issues.
Processing (avg): The average amount of time it takes to
process the data for a report, in milliseconds.
Rendering (avg): The average amount of time it takes to
render a report in the browser, in milliseconds.
Total time: The time it takes for all phases of the report, in
milliseconds.

Top 5 Reports by Average Data Retrieval Time The five reports with the longest average data retrieval time,
in milliseconds.

Top 5 Reports by Average Report Processing Time The five reports with the longest average report processing
time, in milliseconds.

Hourly Results Successes, failures, and memory consumption, split into one-
hour buckets, reported in UTC time.

Hourly Durations Data retrieval vs. processing and rendering time, split into
one-hour buckets, reported in UTC time.

Dataflows
REPORT SECTION METRICS

Refreshes Total: Total refreshes for each dataflow.

Reliability: the percentage of refreshes that completed for
each dataflow.
Avg Wait Time: The average lag between the scheduled time
and start of a refresh for the dataflow, in minutes.
Max Wait Time: The maximum wait time for the dataflow, in
minutes.
Avg Duration: The average duration of refresh for the
dataflow, in minutes.
Max Duration: The duration of the longest-running refresh
for the dataflow, in minutes.

Top 5 dataflows by Average Refresh Duration The five dataflows with the longest average refresh duration,
in minutes.
 REPORT SECTION METRICS

Top 5 dataflows by Average Wait Time The five dataflows with the longest average refresh wait time,
in minutes.

Hourly Average Refresh Wait Times The average refresh wait time, split into one-hour buckets,
reported in UTC time. Multiple spikes with high refresh wait
times are indicative of the capacity running hot.

Hourly Refresh Count and Memory Consumption Successes, failures, and memory consumption, split into one-
hour buckets, reported in UTC time.

Resource Consumption
REPORT SECTION METRICS

CPU consumption Consumption by workload as a percentage of total CPU

capacity. Shown hourly, for the previous seven days.

Memory consumption Memory consumption in GB by workload (solid lines) overlaid

with workload limits (dotted line). Shown hourly, for the
previous seven days.

IDs and Info

The IDs and Info tab contains areas for Capacities, Workspaces, Datasets, Paginated Reports, and
Dataflows.
Capacities area

REPORT SECTION METRICS

SKU and Workload Information SKU and workload settings for the capacity.

Administrators Names of administrators for the capacity.

Workspaces area

REPORT SECTION METRICS

Workspaces Names and IDs for all workspaces.

Datasets area

REPORT SECTION METRICS

Datasets Workspace names and IDs for all datasets.

Paginated Reports area

 REPORT SECTION METRICS

Paginated Reports Names, workspace names, and IDs for all paginated reports.

Dataflows area

REPORT SECTION METRICS

Dataflows Dataflow names, workspace names, and IDs for all dataflows.

Monitor Power BI Embedded capacity

You can use the Power BI Premium Capacity Metrics app to monitor A SKU capacities in Power BI Embedded.
Those capacities will show up in the report as long as you are an admin of the capacity. However, refresh of the
report fails unless you grant certain permissions to Power BI on your A SKUs:
1. Open your capacity in the Azure portal.
2. Click Access control (IAM ), and then add the Power BI Premium app to the reader role. If you are
unable to find the app by name, you can also add it by client Id: cb4dc29f-0bf4-402a-8b30-7511498ed654 .

NOTE
You can monitor Power BI Embedded capacity usage in the app or the Azure portal, but not in the Power BI admin portal.

Next steps
Power BI Premium capacity resource management and optimization
 Monitor capacities in the Admin portal
2/6/2019 • 2 minutes to read • Edit Online

This article describes how you can use the Capacity settings area in the Admin portal to get a quick view of your
capacity's performance. To get the most in-depth metrics about your capacity, it's best to use the Power BI
Premium Capacity Metrics app.

Capacity metrics
The Capacity settings area of the admin portal provides four gauges that indicate the loads placed and the
resources utilized by your capacity for the past seven days. These four tiles work on an hourly time window that
indicates how many hours in the past seven days the corresponding metric was above 80%. This metric indicates a
potential degradation for the end-user experience.

METRIC DESCRIPTION

CPU Number of times CPU exceeded 80% utilization.

Memory Thrashing Represents the memory pressure on your backend cores.

Specifically, this is a metric of how many times datasets are
evicted from memory due to memory pressure from the
usage of multiple datasets.

Memory Usage Average memory usage, represented in gigabytes (GB).

DQ/s Number of times Direct Query and Live Connections count

exceeded 80% of the limit.
The total number of DirectQuery and live connection queries
per second is limited. The limits are 30/s for P1, 60/s for P2
and 120/s for P3. Direct Query and live connection queries
count add to the above throttle. For example, if you have 15
DirectQueries and 15 live connections in a second, you hit
your throttle
This applies equally to on-premises and cloud connections.

Metrics reflect utilization over the past week. If you'd like to see a more detailed view of the metrics, you can do so
by clicking any of the summary tiles. This will take you to detailed charts for each of the metrics for your premium
capacity. The following chart shows details for the CPU metric.
These charts are summarized on an hourly basis for the past week, and can help isolate when you may have had
specific performance-related events in your premium capacity.
You may also export the underlying data for any of the metrics to a csv file. This export will give you detailed
information in three minute intervals for each day of the past week.

Next steps
Now that you understand how to monitor Power BI Premium capacities, learn more about optimizing capacities.
Power BI Premium capacity resource management and optimization
 Configure workloads in a Premium capacity
4/1/2019 • 2 minutes to read • Edit Online

This article describes enabling and configuring workloads for Power BI Premium capacities. By default, capacities
support only the workload associated with running Power BI queries. You can also enable and configure additional
workloads for AI (Cognitive Services), Dataflows, and Paginated reports.

Default memory settings

Query workloads are optimized for and limited by resources determined by your Premium capacity SKU.
Premium capacities also support additional workloads that can use your capacity's resources. Default memory
values for these workloads are based on the capacity nodes available for your SKU. Max memory settings are not
cumulative. Memory up to the max value specified is dynamically allocated for AI and dataflows, but is statically
allocated for paginated reports.
Microsoft Office SKUs for software as a service (SaaS ) scenarios
EM2 EM3 P1 P2 P3

AI (Cognitive 20% default; min 20% default; min 20% default; min 20% default; min 20% default; min
Services) TBD TBD TBD TBD TBD

Dataflows N/A 20% default; 12% 20% default; 5% 20% default; 3% 20% default; 2%
minimum minimum minimum minimum

Paginated N/A N/A 20% default; 10% 20% default; 5% 20% default;
reports minimum minimum 2.5% minimum

Microsoft Azure SKUs for platform as a service (PaaS ) scenarios

A1 A2 A3 A4 A5 A6

AI (Cognitive N/A 20% default; 20% default; 20% default; 20% default; 20% default;
Services) min TBD min TBD min TBD min TBD min TBD

Dataflows 40% default; 24% default; 20% default; 20% default; 20% default; 20% default;
40% 24% minimum 12% minimum 5% minimum 3% minimum 2% minimum
minimum

Paginated N/A N/A N/A 20% default; 20% default; 20% default;
reports 10% minimum 5% minimum 2.5%
minimum

Configure workloads
Maximize your capacity's available resources by enabling workloads only if they will be used. Change memory
settings only when you have determined default settings are not meeting your capacity resource requirements.
To configure workloads in the Power BI admin portal
1. In Capacity settings > PREMIUM CAPACITIES, select a capacity.
2. Under MORE OPTIONS, expand Workloads.
3. Enable one or more workloads, and set a value for Max Memory.

4. Click Apply.

NOTE
If enabling the paginated reports workload, paginated reports allow you to run your own code when rendering a report
(such as dynamically changing text color based on content). Power BI Premium runs paginated reports in a contained space
within the capacity. The maximum memory you specify to this space is used whether or not the workload is active. If you use
Power BI reports or dataflows in the same capacity, make sure you set memory low enough for paginated reports that it
doesn't negatively affect the other workloads. In rare circumstances, the paginated reports workload can become
unavailable. In this case, the workload shows an error state in the admin portal, and users see timeouts for report rendering.
To mitigate this issue, disable the workload then enable it again.

REST API
Workloads can be enabled and assigned to a capacity by using the Capacities REST APIs.

Monitoring workloads
The Power BI Premium Capacity Metrics app provides dataset, dataflows, and paginated reports metrics to
monitor workloads enabled for your capacities.

Next steps
Power BI Premium capacity resource management and optimization
Self-service data prep in Power BI with Dataflows
What are paginated reports in Power BI Premium?
More questions? Ask the Power BI Community
 Restart a Power BI Premium capacity
2/6/2019 • 2 minutes to read • Edit Online

As a Power BI administrator, you might need to restart a Premium capacity. This article explains how to restart a
capacity and addresses several questions about restart and performance.

Why does Power BI provide this option?

Power BI gives users the ability to perform complex analyses on huge amounts of data. Unfortunately, users can
cause performance issues by overloading the Power BI service with jobs, writing overly complex queries, creating
circular references, and so on.
Power BI shared capacity offers some protection from such cases by imposing limits on file sizes, refresh schedules,
and other aspects of the service. In a Power BI Premium capacity, by contrast, most of those limits are raised. As a
result, a single report with a bad DAX expression or a very complex model can cause significant performance
issues. When processed, the report can consume all of the resources available on the capacity.
Power BI is constantly improving in how it protects Premium capacity users against such issues. We are also
empowering administrators with the tools to analyze when capacities are overburdened and why. For more
information, see our short training session and longer training session. At the same time, you need the ability to
mitigate significant issues when they occur. The quickest way to mitigate these issues is to restart the capacity.

Is the restart process safe? Will I lose any data?

All the saved data, definitions, reports, and dashboards on your capacity remain fully intact after restart. When you
restart a capacity, all ongoing scheduled and ad-hoc refreshes are stopped. Refreshes are restarted when the
capacity is available. Users interacting with the capacity will lose unsaved work. They should refresh their browsers
after the restart is complete.

How do I restart a capacity?

Follow these steps to restart a capacity.
1. In the Power BI admin portal, on the Capacity Settings tab, navigate to your capacity.
2. Add the CapacityRestart feature flag to your capacity URL: https://app.powerbi.com/admin-
portal/capacities/?capacityRestartButton=true.
3. Under Advanced Settings > CAPACITY RESTART, select Restart capacity.

4. In the Capacity restart dialog box, select Yes, restart capacity.

How can I prevent issues from happening in the future?
The best way to prevent issues is to educate users about efficient data modeling. For more information, see our
training session.
We also recommend that you monitor your capacities regularly to look for trends that indicate underlying issues.
We plan regular releases of the monitoring app and other tools so that you can monitor and manage your
capacities more effectively.

Next steps
What is Power BI Premium?
More questions? Try asking the Power BI Community
 Power BI Premium support for large datasets
2/6/2019 • 2 minutes to read • Edit Online

Power BI Premium supports uploads of Power BI Desktop (.pbix) files that are up to 10 GB in size. Once uploaded,
a dataset can be refreshed to up to 12 GB in size. To use a large dataset, publish it to a workspace that is assigned
to Premium capacity.

Best practices
This section describes best practices for working with large datasets.
Large models can be very resource-intensive on your capacity. We recommend at least a P1 SKU for any
models larger than 1 GB. Although publishing large models to workspaces backed by A SKUs up to A3 might
work, refreshing them will not.
The following table describes recommended SKUs for various .pbix sizes:

SKU SIZE OF .PBIX

P1 < 3 GB

P2 < 6 GB

P3, P4, P5 up to 10 GB

The Power BI Embedded A4 SKU is equal to the P1 SKU, A5 = P2 and A6 = P3. Note that publishing large models
to A and EM SKUs might return errors that aren't specific to the model size limitation error in the shared capacity.
Refresh errors for large models in A and EM SKUs are likely to point to timeouts. We are working on improving
the error messages for these scenarios.
Your .pbix files represent data in a highly compressed state. The data will likely expand several times when
loaded in memory, and from there it may expand several more times during data refresh.
Scheduled refresh of large datasets can take a long time and be very resource-intensive. Accordingly, do not
schedule too many overlapping refreshes. Notice also that the timeout for scheduled refresh jobs has been
doubled to four hours for all datasets in this capacity. We recommend incremental refresh, because it's faster, more
reliable, and consumes fewer resources.
The initial report load of large datasets can take a long time if it has been a while since the last time the
dataset was used, because the model is loaded into memory of your Premium capacity. A loading bar for longer-
loading reports displays the load progress.
If you remove the workspace from Premium capacity, the model and all associated reports and dashboards
will not work.
While the per-query memory and time constraints are much higher in Premium capacity, it is highly
recommended that you use filters and slicers to limit visuals to display only what is necessary.
Next steps
What is Power BI Premium? Power BI Premium release notes Microsoft Power BI Premium whitepaper Planning
a Power BI Enterprise Deployment whitepaper
More questions? Try asking the Power BI Community
 Incremental refresh in Power BI Premium
2/13/2019 • 7 minutes to read • Edit Online

Incremental refresh enables very large datasets in the Power BI Premium service with the following benefits:
Refreshes are faster - Only data that has changed needs to be refreshed. For example, refresh only the
last five days of a ten-year dataset.
Refreshes are more reliable - It's no longer necessary to maintain long-running connections to volatile
source systems.
Resource consumption is reduced - Less data to refresh reduces overall consumption of memory and
other resources.

Configure incremental refresh

Incremental refresh policies are defined in Power BI Desktop and applied when published to the Power BI
service.
To start, enable incremental refresh in Preview features.

Filter large datasets in Power BI Desktop

Large datasets with potentially billions of rows may not fit into a Power BI Desktop model because the PBIX file
is limited by the memory resources available on the desktop computer. Such datasets are therefore commonly
filtered upon import. This type of filtering applies whether using incremental refresh or not. For incremental
refresh, you filter by using Power Query date/time parameters.
RangeStart and RangeEnd parameters
For incremental refresh, datasets are filtered by using Power Query date/time parameters with the reserved,
case-sensitive names RangeStart and RangeEnd. These parameters are used to filter the data imported into
Power BI Desktop, and also to dynamically partition the data into ranges once published to the Power BI service.
The parameter values are substituted by the service to filter for each partition. Once published, the parameter
values are overridden automatically by the Power BI service. There's no need to set them in dataset settings in
the service. Once published, the parameter values are overridden automatically by the Power BI service.
To define the parameters with default values, in the Power Query Editor, select Manage Parameters.

With the parameters defined, you can then apply the filter by selecting the Custom Filter menu option for a
column.
Ensure rows are filtered where the column value is after or equal to RangeStart and before RangeEnd.

TIP
While the data type of the parameters must be date/time, it's possible to convert them to match the requirements of the
datasource. For example, the following Power Query function converts a date/time value to resemble an integer surrogate
key of the form yyyymmdd, which is common for data warehouses. The function can be called by the filter step.
(x as datetime) => Date.Year(x)*10000 + Date.Month(x)*100 + Date.Day(x)

Select Close and Apply from the Power Query Editor. You should have a subset of the dataset in Power BI
Desktop.
Filter date column updates
The filter on the date column is used to dynamically partition the data into ranges in the Power BI service.
Incremental refresh isn't designed to support cases where the filtered date column is updated in the source
system. An update is interpreted as an insertion and a deletion, not an actual update. If the deletion occurs in the
historical range and not the incremental range, it won’t get picked up. This can cause data refresh failures due to
partition-key conflicts.
Query folding
It's important the partition filters are pushed to the source system when queries are submitted for refresh
operations. To push filtering down means the datasource should support query folding. Most data sources that
support SQL queries support query folding. However, data sources like flat files, blobs, web, and OData feeds
typically do not. In cases where the filter is not supported by the datasource back-end, it cannot be pushed down.
In such cases, the mashup engine compensates and applies the filter locally, which may require retrieving the full
dataset from the data source. This can cause incremental refresh to be very slow, and the process can run out of
resources either in the Power BI service or in the on-premises data gateway if used.
Given the various levels of query folding support for each datasource, it's recommended that verification is
performed to ensure the filter logic is included in the source queries. To make this easier, Power BI Desktop
attempts to perform this verification for you. If unable to verify, a warning is displayed in the incremental refresh
dialog when defining the incremental refresh policy. SQL based data sources such as SQL, Oracle, and Teradata
can rely on this warning. Other data sources may be unable to verify without tracing queries. If Power BI Desktop
is unable to confirm, the following warning is displayed.

Define the refresh policy

Incremental refresh is available on the context menu for tables, except for Live Connection models.
Incremental refresh dialog
The incremental refresh dialog is displayed. Use the toggle to enable the dialog.
 NOTE
If the Power Query expression for the table doesn't refer to the parameters with reserved names, the toggle is disabled.

The header text explains the following:

Incremental refresh is supported only for workspaces on Premium capacities. Refresh policies are defined
in Power BI Desktop, and they are applied by refresh operations in the service.
If you're able to download the PBIX file containing an incremental-refresh policy from the Power BI
service, it cannot be opened in Power BI Desktop. While this may be supported in the future, keep in mind
these datasets can grow to be so large that they are impractical to download and open on a typical desktop
computer.
Refresh ranges
The following example defines a refresh policy to store data for five full calendar years plus data for the current
year up to the current date, and incrementally refresh ten days of data. The first refresh operation loads historical
data. Subsequent refreshes are incremental, and (if scheduled to run daily) perform the following operations:
Add a new day of data.
Refresh ten days up to the current date.
Remove calendar years that are older than five years prior to the current date. For example, if the current
date is January 1 2019, the year 2013 is removed.
The first refresh in the Power BI service may take longer to import all five full calendar years. Subsequent
refreshes may be finished in a fraction of the time.
 NOTE
Definition of these ranges might be all you need, in which case you can go straight to the publishing step below. The
additional dropdowns are for advanced features.

Advanced policy options

Detect data changes
Incremental refresh of ten days is more efficient than full refresh of five years. However, it's possible to do even
better. If you select the Detect data changes checkbox, you can select a date/time column used to identify and
refresh only the days where the data has changed. This assumes such a column exists in the source system, which
is typically for auditing purposes. This should not be the same column used to partition the data with the
RangeStart/RangeEnd parameters. The maximum value of this column is evaluated for each of the periods in
the incremental range. If it has not changed since the last refresh, there is no need to refresh the period. In the
example, this could further reduce the days incrementally refreshed from ten to around two.

TIP
The current design requires that the column to detect data changes is persisted and cached into memory. You may want to
consider one of the following techniques to reduce cardinality and memory consumption.
Persist only the maximum value of this column at time of refresh, perhaps using a Power Query function.
Reduce the precision to a level that is acceptable given your refresh-frequency requirements.
We plan to allow the definition of custom queries for data-change detection at a later date. This could be used to avoid
persisting the column value altogether.

Only refresh complete periods

Let's say your refresh is scheduled to run at 4:00 AM every morning. If data appears in the source system during
those 4 hours, you may not want to account for it. Some business metrics -- such as barrels per day in the oil and
gas industry -- make no sense with partial days.
Another example is refreshing data from a financial system where data for the previous month is approved on
the 12th calendar day of the month. You could set the incremental range to 1 month and schedule the refresh to
run on the 12th day of the month. With this option checked, it would for example refresh January data on
February 12th.

NOTE
Refresh operations in the service run under UTC time. This can determine the effective date and affect complete periods.
We plan to add the ability to override the effective date for a refresh operation.

Publish to the service

Since incremental refresh is a Premium only feature, the publish dialog only allows selection of a workspace on
Premium capacity.
You can now refresh the model. The first refresh may take longer to import the historical data. Subsequent
refreshes can be much quicker because they use incremental refresh.

Query timeouts
The troubleshooting refresh article explains that refresh operations in the Power BI service are subject to
timeouts. Queries can also be limited by the default timeout for the data source. Most relational sources allow
overriding timeouts in the M expression. For example, the expression below uses the SQL Server data-access
function to set it to 2 hours. Each period defined by the policy ranges submits a query observing the command
timeout setting.

let
Source = Sql.Database("myserver.database.windows.net", "AdventureWorks", [CommandTimeout=#duration(0, 2,
0, 0)]),
dbo_Fact = Source{[Schema="dbo",Item="FactInternetSales"]}[Data],
#"Filtered Rows" = Table.SelectRows(dbo_Fact, each [OrderDate] >= RangeStart and [OrderDate] < RangeEnd)
in
#"Filtered Rows"
 Multi-Geo support for Power BI Premium
3/7/2019 • 3 minutes to read • Edit Online

Multi-Geo is a Power BI Premium feature that helps multinational customers address regional, industry-specific,
or organizational data residency requirements. As a Power BI Premium customer, you can deploy content to
datacenters in regions other than the home region of the Power BI tenant. A geo (geography) can contain more
than one region. For example, the United States is a geo, and West Central US and South Central US are regions
in the United States. You may choose to deploy content to any of the following geos:
United States
Canada
United Kingdom
Brazil
Europe
Japan
India
Asia Pacific
Australia
Multi-Geo isn't available for Power BI Germany, Power BI China operated by 21Vianet, or Power BI for the US
government.
Multi-Geo is now also available in Power BI Embedded. Read more at Multi-Geo support in Power BI Embedded.

Using Multi-Geo
For new capacities, enable Multi-Geo by selecting a region other than the default region from the dropdown.
Each available capacity shows the region where it's currently located, such as West Central US.
After you've created capacity, it remains in that region, and any workspaces created will have their content stored
in that region. You can migrate workspaces from one region to another through the dropdown on the workspace
settings screen.

You see this message to confirm the change.

You don't need to reset the gateway credentials during a migration at this time. After they're stored in the
Premium capacity region, you will need to reset them upon migration.
During migration, certain operations may fail, such as publishing new datasets or scheduled data refresh.
The following items are stored in the Premium region when Multi-Geo is enabled:
Models (.ABF files) for import and Direct Query datasets
Query cache
R images
These items remain in the home region for the tenant:
Push datasets
Excel workbooks
Dashboard/report metadata: e.g., tile names, tile queries
Service buses for gateway queries or scheduled refresh jobs
Permissions
Dataset credentials

View Capacity Regions

In the Admin Portal, you can view all the capacities for your Power BI tenant and the regions where they’re
currently located.
Change the region for existing content
If you need to change the region for existing content, you have two options.
Create a second capacity and move workspaces. Free users won't experience any downtime as long as the
tenant has spare v-cores.
If creating a second capacity isn't an option, you can temporarily move the content back to shared capacity
from Premium. You don't need extra v-cores, but free users will experience some downtime.

Move content out of Multi-Geo

You can take workspaces out of Multi-Geo capacity in one of two ways:
Delete the current capacity where the workspace is located. This moves the workspace back to shared capacity
in the home region.
Migrate individual workspaces back to Premium capacity located in the home tenant.

Limitations and considerations

Confirm that any movement you initiate between regions follows all corporate and government compliance
requirements prior to initiating data transfer.
A cached query stored in a remote region stays in that region at rest. However, other data in transit may go
back and forth between multiple geographies.
When moving data from one region to another in a Multi-Geo environment, the source data may remain in
the region from which the data was moved for up to 30 days. During that time end users don't have access to
it. It's removed from this region and destroyed during the 30-day period.
Multi-Geo doesn't result in better performance in general. Loading reports and dashboards still involves
requests to the home region for metadata.
The dataflows feature (in preview ) is not supported on Multi-GEO at this time.

Next steps
Power BI Premium: What is it?
Multi-Geo for Power BI Embedded capacities
More questions? Try asking the Power BI Community
 Connect to datasets with client applications and tools
(Preview)
3/28/2019 • 4 minutes to read • Edit Online

Power BI Premium workspaces and datasets support read -only connections from Microsoft and third-party client
applications and tools.

NOTE
This article is intended only to introduce read-only connectivity to Power BI Premium workspaces and datasets. It is not
intended to provide in-depth information about programmability, specific tools and applications, architecture, and workspace
and dataset management. Subjects described here require a solid understanding of Analysis Services tabular model database
architecture and administration.

Protocol
Power BI Premium uses the XML for Analysis (XMLA) protocol for communications between client applications
and the engine that manages your workspaces and datasets. These communications are through what are
commonly referred to as XMLA endpoints. XMLA is the same communication protocol used by the Microsoft
Analysis Services engine, which under the hood, runs Power BI's semantic modeling, governance, lifecycle, and
data management.
The vast majority of client applications and tools do not explicitly communicate with the engine by using XMLA
endpoints. Instead, they use client libraries such as MSOLAP, ADOMD, and AMO as an intermediary between the
client application and the engine, which communicates exclusively by using XMLA.

Supported tools
These tools support read-only access to Power BI Premium workspaces and datasets:
SQL Server Management Studio (SSMS ) - Supports DAX, MDX, XMLA, and TraceEvent queries. Requires
version 18.0 (Preview ). Download here.
SQL Server Profiler - Included with SSMS 18.0 (Preview ), this tool provides tracing and debugging of server
events. You can capture and save data about each event to a file or table to analyze later. While officially deprecated
for SQL Server, Profiler continues to be included in SSMS and remains supported for Analysis Services and Power
BI Premium. To learn more, see SQL Server Profiler.
DAX Studio - Open-source, community tool for executing and analyzing DAX queries against Analysis Services.
Requires version 2.8.2 or higher. To learn more, see daxstudio.org.
Excel PivotTables - Click-to-Run version of Office 16.0.11326.10000 or above is required.
Third party - Includes client data visualization applications and tools that can connect to, query, and consume
datasets in Power BI Premium. Most tools require the latest versions of MSOLAP client libraries, but some may
use ADOMD.

Client libraries
Client libraries are necessary for client applications and tools to connect to Power BI Premium workspaces. The
same client libraries used to connect to Analysis Services are also supported in Power BI Premium. Microsoft client
applications like Excel, SQL Server Management Studio (SSMS ), and SQL Server Data Tools (SSDT) install all
three client libraries and update them along with regular application updates. In some cases, particularly with third-
party applications and tools, you may need to install newer versions of the client libraries. Client libraries are
updated monthly. To learn more, see Client libraries for connecting to Analysis Services.

Connecting to a Premium workspace

You can connect to workspaces assigned to Premium dedicated capacities. Workspaces assigned to a dedicated
capacity have a connection string in URL format.
To get the workspace connection string, in Power BI, in Workspace Settings, on the Premium tab, in Workspace
Connection, click Copy.

Workspace connections use the following URL format to address a workspace as though it were an Analysis
Services server name:
powerbi://api.powerbi.com/v1.0/[tenant name]/[workspace name]

For example, powerbi://api.powerbi.com/v1.0/contoso.com/Sales Workspace

NOTE
[workspace name] is case sensitive and can include spaces.

To connect in SSMS
In Connect to Server > Server Type, select Analysis Services. In Server name, enter the URL. In
Authentication, select Active Directory - Universal with MFA Support, and then in User name, enter your
organizational user ID.
When connected, the workspace is shown as an Analysis Services server, and datasets in the workspace are shown
as databases.
Initial catalog
Some tools, such as SQL Server Profiler, you may need to specify an Initial Catalog. Specify a dataset (database) in
your workspace. In Connect to Server, click Options. In the Connect to Server dialog, on the Connection
Properties tab, in Connect to database, enter the dataset name.
Duplicate workspace name
When connecting to a workspace with the same name as another workspace, you may get the following error:
Cannot connect to powerbi://api.powerbi.com/v1.0/[tenant name]/[workspace name].
To get around this error, in addition to the workspace name, specify the ObjectIDGuid, which can be copied from
the workspace objectID in the URL. Append the objectID to the connection URL. For example,
`powerbi://api.powerbi.com/v1.0/myorg/Contoso Sales - 9d83d204-82a9-4b36-98f2-a40099093830'
Duplicate dataset name
When connecting to a dataset with the same name as another dataset in the same workspace, append the dataset
guid to the dataset name. You can get both dataset name and guid when connected to the workspace in SSMS.
Delay in datasets shown
When connecting to a workspace, changes from new, deleted, and renamed datasets can take up to 5 minutes to
appear.

Audit logs
When client applications and tools connect to a workspace, access through XMLA endpoints is logged in the Power
BI audit logs under the GetWorkspaces operation. To learn more, see Auditing Power BI.

See also
Analysis Services References
SQL Server Management Studio
SQL Server Analysis Services Tabular Protocol
Dynamic Management Views (DMVs)
More questions? Try asking the Power BI Community
 Power BI Premium FAQ
3/22/2019 • 5 minutes to read • Edit Online

This article addresses questions frequently asked about Power BI Premium. For an overview, see What is Power
BI Premium?.
If you have other questions, try asking the Power BI Community.
Still have an issue? Please visit the Power BI support page.
What is Power BI Premium?
Power BI Premium is a capacity-based offering that includes:
Flexibility to publish reports broadly across an enterprise, without requiring recipients to be licensed
individually per user.
Greater scale and performance than shared capacity in the Power BI service.
The ability to maintain BI assets on-premises with Power BI Report Server.
One API surface, a consistent set of capabilities, and access to the latest features for embedded analytics.
What does Power BI Premium do? How does it work?
Power BI Premium consists of capacity in the Power BI service exclusively allocated to each organization. The
capacity is supported by dedicated hardware fully managed by Microsoft. Organizations can choose to apply their
dedicated capacity broadly, or allocate it to assigned workspaces based on the number of users, workload needs,
or other factors—and scale up or down as requirements change.
How is Power BI Pro different than Power BI Premium?
Power BI Premium is a capacity-based license, while Power BI Pro is a user-based license. Power BI Pro is for
those users publishing reports, sharing dashboards, collaborating with colleagues in workspaces and engaging in
other related activities – such as the ability to:
Edit and save customized views
Create personal dashboards (pin to new dashboard)
Analyze data in Excel or Power BI Desktop
Share with Excel Web App support
Share dashboards and collaborate with Office 365 Groups
Integrate content with Microsoft Teams
Do I need Power BI Pro to use Power BI Premium?
Yes. Power BI Pro is required to publish reports, share dashboards, collaborate with colleagues in workspaces and
engage in other related activities. Power BI Pro isn't required to consume content in Premium capacity.
Can you outline a scenario of how Power BI Pro and Power BI Premium work to cover an organization
for Modern BI?
The following examples outline how customers can meet their BI needs using a combination of Power BI Pro and
Power BI Premium.
 SCENARIO 1 SCENARIO 2 SCENARIO 3 SCENARIO 4

An organization or An organization or An organization or A finance department is

department wants every department has a department has users who actively working to analyze
employee to have self- combination of users who require self-service BI and several large datasets in
service BI and collaborate require self-service BI and collaboration as well as the advance of an earnings
with each other – sharing collaboration as well as users requirement to keep reports announcement and requires
dashboards, performing ad who only need to consume on-premises. unthrottled and isolated
hoc analysis, and publishing BI content. capacity to manage the
reports. workloads.

Solution: Solution: Solution: Solution:

1. Power BI Pro for every 1. Power BI Pro for users 1. Power BI Pro for users 1. Power BI Pro for every
user that require self-service BI that require self-service BI user in the finance
and collaboration and collaboration department
2. Look to expand the
opportunity by adding 2. Add Power BI Premium to 2. Add Power BI Premium to 2. Add Power BI Premium
Power BI Premium – see the be able to distribute BI be able to publish reports for the dedicated resources
additional scenarios content to users who only on-premises – and move to – in the cloud – to be used
need to consume the cloud as appropriate exclusively by the finance
team, providing larger scale
and greater performance

How much does Power BI Premium cost? How many SKUs will you make available?
Power BI Premium is purchased based on the number of virtual cores. You can see prices at the Power BI pricing
page. For more information on nodes and v-cores, see the Microsoft Power BI Premium whitepaper. Also use this
calculator to get an estimate of how much Premium capacity you may need.
What do you mean by "capacity"?
A capacity is a grouping of one or more nodes that is provisioned by an admin through the Power BI Premium
capacity admin portal. See the Microsoft Power BI Premium whitepaper for more information.
How is Power BI Premium billed?
Power BI Premium is billed monthly with an annual commitment.
How do I buy Power BI Premium?
Power BI Premium is available from the Microsoft 365 admin center. For more information, see How to purchase
Power BI Premium. You can also contact your Microsoft representative for more information.
How do I know how much Power BI Premium capacity I need to purchase?
Use the cost calculator to estimate how much Power BI Premium capacity you may need.
Is Power BI Premium available with Office 365 E5?
Power BI Premium is available as an add-on to Power BI Pro. Office 365 E5 includes Power BI Pro. E5 customers
can purchase Premium as an add-on to their existing Pro licenses.
What is Power BI Report Server? Does this mean you’re making Power BI available on-premises?
Power BI Report Server is an on-premises server that allows the deployment and distribution of interactive Power
BI reports, and paginated reports, completely within the boundaries of the organization’s firewall. Power BI Report
Server is available through Power BI Premium or as a benefit for customers with SQL Server Enterprise Edition
with Software Assurance. Contact your Microsoft representative for more information.
With Power BI Premium. the same number of virtual cores an organization provisions in the cloud can also be
deployed on-premises through Power BI Report Server. There is no need to split the capacity. Organizations can
choose Power BI in the cloud, or elect to keep reports on-premises with Power BI Report Server and move to the
cloud at their pace.
For more information, see Get started with Power BI Report Server.
Next steps
What is Power BI Premium? Power BI Premium release notes Microsoft Power BI Premium whitepaper Planning
a Power BI Enterprise Deployment whitepaper Extended Pro Trial activation Power BI Embedded FAQ
More questions? Try asking the Power BI Community
 Understanding the Power BI service administrator
role
3/22/2019 • 2 minutes to read • Edit Online

Learn how you can use the Power BI service administrator role in your organization. Users in this role have full
control over a Power BI tenant and its administrative features, except for licensing.
https://www.youtube.com/embed/PQRbdJgEm3k?showinfo=0
The Power BI service administrator role can be assigned to users who need access to the Power BI Admin portal
without also granting those users complete Office 365 administrative access.
Office 365 user management administrators assign users to the Power BI service administrator role in the
Microsoft 365 admin center, or by using a PowerShell script. Once a user is assigned, they can access the Power BI
admin portal. There, they have access to tenant-wide usage metrics, and can control tenant-wide usage of Power
BI features.

Limitations and considerations

The Power BI service administrator role does not provide the following capabilities:
Ability to modify users and licenses within the Microsoft 365 admin center,
Access to the audit logs. For more information, see Using auditing within your organization.

Assign users to the admin role in Office 365

To assign users to the Power BI admin role in the Microsoft 365 admin center, follow these steps.
1. In the Microsoft 365 admin center, select Users > Active Users.

2. Select the user that you want to assign the role to.
3. Under Roles, select Edit.
4. Select Customized administrator > Power BI service administrator.

5. Select Save, then Close.

You should see Power BI service administrator listed for the role of that user.

Assign users to the admin role with PowerShell

You can also assign users to roles by using PowerShell. Users are managed in Azure Active Directory (Azure AD. If
you don't already have the Azure AD PowerShell module, download and install the latest version.
1. First, get the ObjectId for the Power BI Service Administrator role. You can run Get-
AzureADDirectoryRole to get the ObjectId
 PS C:\Windows\system32> Get-AzureADDirectoryRole

ObjectId DisplayName Description

-------- ----------- -----------
00f79122-c45d-436d-8d4a-2c0c6ca246bf Power BI Service Administrator Full access in the Power BI
Service.
250d1222-4bc0-4b4b-8466-5d5765d14af9 Helpdesk Administrator Helpdesk Administrator has
access to perform..
3ddec257-efdc-423d-9d24-b7cf29e0c86b Directory Synchronization Accounts Directory Synchronization
Accounts
50daa576-896c-4bf3-a84e-1d9d1875c7a7 Company Administrator Company Administrator role has
full access t..
6a452384-6eb9-4793-8782-f4e7313b4dfd Device Administrators Device Administrators
9900b7db-35d9-4e56-a8e3-c5026cac3a11 AdHoc License Administrator Allows access manage AdHoc
license.
a3631cce-16ce-47a3-bbe1-79b9774a0570 Directory Readers Allows access to various read
only tasks in ..
f727e2f3-0829-41a7-8c5c-5af83c37f57b Email Verified User Creator Allows creation of new email
verified users.

In this case, the role's ObjectId is 00f79122-c45d-436d-8d4a-2c0c6ca246bf.

2. Next, get the user's ObjectId. You can find that by running Get-AzureADUser.

PS C:\Windows\system32> Get-AzureADUser -SearchString '[email protected]'

ObjectId DisplayName UserPrincipalName UserType

-------- ----------- ----------------- --------
6a2bfca2-98ba-413a-be61-6e4bbb8b8a4c Tim [email protected] Member

3. To add the member to the role, run Add-AzureADDirectoryRoleMember.

PARAMETER DESCRIPTION

ObjectId The Role ObjectId.

RefObjectId The members ObjectId.

Add-AzureADDirectoryRoleMember -ObjectId 00f79122-c45d-436d-8d4a-2c0c6ca246bf -RefObjectId 6a2bfca2-

98ba-413a-be61-6e4bbb8b8a4c

Next steps
Administering Power BI in your Organization
Power BI admin portal
More questions? Try asking the Power BI Community
 Administering Power BI - frequently asked questions
(FAQ)
3/22/2019 • 11 minutes to read • Edit Online

This article addresses frequently asked questions for Power BI administration. For an overview of the Power BI
administration, see What is Power BI administration?.

What's in this article

Sign up for Power BI section
Using PowerShell
How do users sign up for Power BI?
How do individual users in my organization sign up?
How can I prevent users from joining my existing Office 365 tenant?
How can I allow users to join my existing Office 365 tenant?
How do I verify if I have the block on in the tenant?
How can I prevent my existing users from starting to use Power BI?
How can I allow my existing users to sign up for Power BI?
Administration of Power BI section
How will this change the way I manage identities for users in my organization today?
How do we manage Power BI?
What is the process to manage a tenant created by Microsoft for my users?
If I have multiple domains, can I control the Office 365 tenant that users are added to?
How do I remove Power BI for users that already signed up?
How do I know when new users have joined my tenant?
Are there any additional things I should be prepared for?
Where is my Power BI tenant located?
What is the Power BI SLA (Service Level Agreement)?
How does Power BI handle high availability and failover?
Security in Power BI section
Does Power BI meet national, regional, and industry-specific compliance requirements?
How does security work in Power BI?

Sign up for Power BI

Using PowerShell
Some of the procedures in this section require Windows PowerShell scripts. If you're not familiar with PowerShell,
we recommend the PowerShell getting started guide. To run the scripts, first install the latest 64-bit version of the
Azure Active Directory PowerShell for Graph.
How do users sign up for Power BI?
As an administrator, you can sign up for Power BI through the Power BI web site or the Purchase services page on
the Microsoft 365 admin center. When an administrator signs up for Power BI, they can assign user licenses to
users who should have access.
Additionally, individual users in your organization may be able to sign up for Power BI through the Power BI web
site. When a user in your organization signs up for Power BI, that user is assigned a Power BI license automatically.
For more information, see Signing up for Power BI as an individual and Power BI licensing in your organization.
How do individual users in my organization sign up?
There are three scenarios that might apply to users in your organization:
Scenario 1: Your organization already has an existing Office 365 environment, and the user signing up for
Power BI already has an Office 365 account. In this scenario, if a user already has a work or school account
in the tenant (for example, contoso.com) but does not yet have Power BI, Microsoft simply activates the plan
for that account, and the user is automatically notified of how to use the Power BI service.
Scenario 2: Your organization has an existing Office 365 environment, but the user signing up for Power BI
doesn’t have an Office 365 account. In this scenario, the user has an email address in your organization’s
domain (for example, contoso.com) but does not yet have an Office 365 account. In this case, the user can
sign up for Power BI and is automatically given an account. This lets the user access the Power BI service.
For example, if an employee named Nancy uses her work email address (such as [email protected]) to
sign up, Microsoft automatically adds Nancy as a user in Contoso’s Office 365 environment and activates
Power BI for that account.
Scenario 3: Your organization does not have an Office 365 environment connected to your email domain.
There are no administrative actions your organization needs to take to take advantage of Power BI. Users
are added to a new, cloud-only user directory, and you have the option to elect to take over as the tenant
admin and manage them.

IMPORTANT
If your organization has multiple email domains and you prefer all email address extensions to be in the same tenant, add all
email address domains to an Azure Active Directory tenant before any users sign up. There is no automated mechanism to
move users across tenants after they have been created. For more information on this process, see If I have multiple
domains, can I control the Office 365 tenant that users are added to? later in this article and Add a domain to Office 365.

How can I prevent users from joining my existing Office 365 tenant?
There are steps you can take, as an admin, to prevent users from joining your existing Office 365 tenant. If you
block access, users’ attempts to sign up fail, and they are directed to contact their organization’s admin. You do not
need to repeat this process if you have already disabled automatic license distribution (e.g. through Office 365 for
Education for Students, Faculty, and Staff).
Use the following PowerShell script to prevent new users from joining a managed tenant. (Learn more about
PowerShell.)

$msolcred = get-credential
connect-msolservice -credential $msolcred

Set-MsolCompanySettings -AllowEmailVerifiedUsers $false

NOTE
Blocking access prevents new users in your organization from signing up for Power BI. Users that sign up for Power BI prior
to disabling new signups for your organization still retain their licenses. To remove a user, see How do I remove Power BI for
users that already signed up? later in this article.

How can I allow users to join my existing Office 365 tenant?

Use the following PowerShell script to enable new users to join a managed tenant. (Learn more about PowerShell.)
 $msolcred = get-credential
connect-msolservice -credential $msolcred

Set-MsolCompanySettings -AllowEmailVerifiedUsers $true

How do I verify if I have the block on in the tenant?

Use the following PowerShell script to verify settings. AllowEmailVerifiedUsers should be false. (Learn more about
PowerShell.)

$msolcred = get-credential
connect-msolservice -credential $msolcred

Get-MsolCompanyInformation | fl allow*

How can I prevent my existing users from starting to use Power BI?
The Azure AD setting that controls this is AllowAdHocSubscriptions. Most tenants have this setting set to true,
which means it is enabled. If you acquired Power BI through a partner, this may be set to false, which means it is
disabled.
Use the following PowerShell script to disable ad hoc subscriptions. (Learn more about PowerShell.)
1. Sign into Azure Active Directory using your Office 365 credentials. The first line of the following PowerShell
script prompts you for your credentials. The second line connects to Azure Active Directory.

$msolcred = get-credential
connect-msolservice -credential $msolcred

2. Once you are signed in, run the following command to see how your tenant is currently configured.

Get-MsolCompanyInformation | fl AllowAdHocSubscriptions

3. Run the following command to enable ($true) or disable ($false) AllowAdHocSubscriptions.

Set-MsolCompanySettings -AllowAdHocSubscriptions $false

 NOTE
The AllowAdHocSubscriptions flag is used to control several user capabilities in your organization, including the ability for
users to sign up for the Azure Rights Management Service. Changing this flag affects all of these capabilities.

How can I allow my existing users to sign up for Power BI?

To allow your existing users to sign up for Power BI, run the command listed for the above question, but pass true
instead of false in the last step.

Administration of Power BI
How will this change the way I manage identities for users in my organization today?
There are three scenarios that might apply to users in your organization:
Scenario 1: If your organization already has an existing Office 365 environment and all users in your
organization have Office 365 accounts, there is no change in how you manage identity.
Scenario 2: If your organization already has an existing Office 365 environment but not all users in your
organization have Office 365 accounts, we create a user in the tenant and assign licenses based on the
user’s work, or school, email address.
This means that the number of users you are managing at any particular time grows as users in your
organization sign up for the service.
Scenario 3: If your organization does not have an Office 365 environment connected to your email domain,
there is no change in how you manage identity.
Users are added to a new, cloud-only user directory, and you have the option to elect to take over as the
tenant admin and manage them.
How do we manage Power BI?
Power BI provides an admin portal that enables you to view usage statistics, provides a link to the Microsoft 365
admin center to manage users and groups, and provides the ability to control tenant-wide settings.
To access the Power BI admin portal, your account must be marked as a Global Admin within Office 365 or Azure
Active Directory, or have been assigned the Power BI service administrator role. For more information, see
Understanding the Power BI admin role and Power BI Admin Portal.
What is the process to manage a tenant created by Microsoft for my users?
When a self-service user signs up for a cloud service that uses Azure AD, they are added to an unmanaged Azure
AD directory based on their email domain. You can claim and manage the tenant that was created using a process
known as an admin takeover. The type of takeover you do depends on whether there is an existing managed
tenant associated with your domain:
Use an internal takeover to create a new managed tenant for the domain.
Use an external takeover to move the domain to an existing managed tenant.
For more information, see Take over an unmanaged directory as administrator in Azure Active Directory.
When you perform an external takeover, Power BI content that was created before the takeover is placed in a
Power BI Archived Workspace. You must manually migrate any content that you want to use in the new tenant.
If I have multiple domains, can I control the Office 365 tenant that users are added to?
If you do nothing, a tenant is created for each user email domain and subdomain. If you want all users to be in the
same tenant regardless of their email address extensions: Create a target tenant ahead of time, or use an existing
tenant, and add all the existing domains and subdomains that you want consolidated within that tenant. Then all
the users with email addresses ending in those domains and subdomains automatically join the target tenant when
they sign up.

IMPORTANT
There is no supported automated mechanism to move users across tenants once they have been created. To learn about
adding domains to a single Office 365 tenant, see Add your users and domain to Office 365.

How do I remove Power BI for users that already signed up?

If a user is signed up for Power BI, but you no longer want them to have access to Power BI, you can remove the
Power BI license for that user.
1. Navigate to the Microsoft 365 admin center.
2. In the left navigation bar, select Users > Active Users.
3. Find the user you want to remove the license for, then select their name.
You can perform bulk license management to users as well. To do that, select multiple users and select Edit
product licenses.
4. On the user details page, next to Product licenses, select Edit.
5. Set Power BI (free) or Power BI Pro to Off, depending on what license is applied to their account.
6. Select Save.
How do I know when new users have joined my tenant?
Users who have joined your tenant as part of this program are assigned a unique license that you can filter on
within your active user pane in the admin dashboard. To create this new view, follow these steps.
1. Navigate to the Microsoft 365 admin center.
2. In the left navigation bar, select Users > Active Users.
3. On the Views menu, select Add custom view.
4. Name your new view, and under Assigned product license, select Power BI (free) or Power BI Pro.
You can only have one license selected per view. If you have both Power BI (free) and Power BI Pro
licenses in your organization, you can create two views.
5. Enter any other conditions you want, then select Add.
6. Once the new view is created, it's available from the Views menu.
Are there any additional things I should be prepared for?
You might experience an increase in password reset requests. For information about this process, see Reset a user's
password.
You can remove a user from your tenant via the standard process in the Microsoft 365 admin center. However, if
the user still has an active email address from your organization, they can rejoin unless you block all users from
joining.
Where is my Power BI tenant located?
For information about which data region your Power BI tenant is in, see Where is my Power BI tenant located?.
What is the Power BI SLA?
For information about the Power BI SLA (Service Level Agreement), see the Licensing Terms and Documentation
article in the Licensing section of the Microsoft Licensing website.
How does Power BI handle high availability and failover?
For information about high availability and failover, see Power BI high availability, failover, and disaster recovery
FAQ.

Security in Power BI
Does Power BI meet national, regional, and industry-specific compliance requirements?
To learn more about Power BI compliance, see the Microsoft Trust Center.
How does security work in Power BI?
Power BI is built on the foundation of Office 365, which in turn builds on Azure services like Azure Active
Directory. For an overview of Power BI architecture, see Power BI Security.

Next steps
Power BI admin portal
Understanding the Power BI admin role
Self-service sign up for Power BI
Purchasing Power BI Pro
What is Power BI Premium?
How to purchase Power BI Premium
Power BI Premium whitepaper
Manage your group in Power BI and Office 365
Office 365 user account management
Office 365 group management
More questions? Try asking the Power BI Community
 Power BI high availability, failover, and disaster
recovery FAQ
2/19/2019 • 4 minutes to read • Edit Online

This article explains how the Power BI service delivers high availability and provides business continuity and
disaster recovery to its users. After reading this article, you should have a better understanding of how high
availability is achieved, under what circumstances Power BI performs a failover, and what to expect from the
service when it fails over.

What does "high availability" mean for Power BI?

Power BI is fully managed software as a service (SaaS ). Microsoft designs and operates it to be resilient to
infrastructure failures so that users can always access their reports. The service is supported by a 99.9% SLA.

What is a Power BI failover?

Power BI maintains multiple instances of each component in Azure datacenters (also known as regions) to
guarantee business continuity. If there is an outage, or an issue that causes Power BI to be inaccessible or
inoperable in a region, Power BI fails all its components in that region to a backup instance. The failover restores
availability and operability to the Power BI service instance in a new region (usually within the same geographic
location, as noted in the Microsoft Trust Center).
A failed-over Power BI service instance supports only read operations, which means the following operations
aren't supported during failover: refreshes, report publish operations, dashboard or report modifications, and
other operations that require changes to Power BI metadata (for example, inserting a comment in a report). Read
operations, such as displaying dashboards and displaying reports (that are not based on DirectQuery or Live
Connect to on-premises data sources) continue to function normally.

How are backup instances kept in sync with my data?

All Power BI service components regularly sync their backup instances. We target a 15-minute point-in-time sync
for any content uploaded or changed in Power BI. In the event of a failover, Power BI uses Azure storage geo-
redundant replication and Azure SQL geo redundant replication to guarantee backup instances exist in other
regions and can be used in the case of a failover.

Where are the failover clusters located?

Backup instances reside within the same geographic location (geo) that you selected when your organization
signed up for Power BI, except where noted in the Microsoft Trust Center. A geo can contain several regions, and
Microsoft may replicate data to any of the regions within a given geo for data resiliency. Microsoft will not replicate
or move customer data outside the geo. For a mapping of the geos offered by Power BI and the regions within
them, see the Microsoft Trust Center.

How does Microsoft decide to failover?

There are two different systems that indicate when a failover might be required:
Our external and internal monitoring probes indicate a lack of availability or inability to operate properly. Such
indications can be based on outages detected in Power BI components or one or more of the services that
 Power BI depends on in a region.
Microsoft Azure's central operations team informs us of a critical outage in a region.
In both cases, Power BI executive team members make the decision to fail over; the decision itself isn't automated.
Once the decision is made, the process of failing over takes place automatically.

How do I know Power BI is now in failover mode?

A notification is posted on the Power BI support page ( https://powerbi.microsoft.com/en-us/support/ ). The
notification includes the major operations that are not available during the failover, including publish, refresh,
create dashboard, duplicate dashboard, and permission changes.

How long does it take Power BI to fail over?

Once a decision to fail over is made, it can take up to 60 minutes for a failover instance to become available.

When does my Power BI instance return to the original region?

Power BI service instances return to their original region when the issue that caused the failover is resolved. Check
the Power BI support page: When the issue is resolved, the Power BI team removes the notification that describes
the failover. At that point, operations should be back to normal.

Am I responsible for the availability of my Power BI solution?

If the Power BI solution used in your organization involves one of the following elements, you must take some
measures to guarantee that the solution remains highly available:
If your organization uses Power BI Premium, you must ensure that the Premium capacity is sized to meet the
load demands of your deployment. The Power BI Premium Planning and Deployment whitepaper, and the
Power BI Premium Capacity Metrics app can help you to plan and meet this requirement. We regularly add new
features to the metrics app and the admin portal in Power BI to help.
If your organization accesses on-premises data sources using the Power BI On-premises gateway, you must set
the gateway up as described in this article to support high availability. Follow this guidance whether you're
refreshing reports in import mode, or you're accessing data or data models by using DirectQuery or Live
Connect.

Will gateways function when in failover mode?

No. Data required from on-premises data sources (any reports and dashboards based on Direct Query and Live
Connect) will not work during a failover. The gateway configuration doesn't change though: When the Power BI
instance returns to its original state, the gateways return to their normal functions.
 Power BI licensing in your organization
3/22/2019 • 5 minutes to read • Edit Online

In the Power BI service, users have defined capabilities based on two types of licenses:
Per-user - Power BI Pro licensing and free licensing. A Power BI Pro license enables access to all content
and capabilities in the Power BI service, including the ability to share content and collaborate with other
Pro users. Only Pro users can publish to and consume content from app workspaces, share dashboards,
and subscribe to dashboards and reports. A free license enables access to some of the features of the
Power BI service. For more information, see Per-user license type comparison.
Capacity-based - Power BI Premium licensing. Premium provides dedicated capacity to deliver more
consistent performance and support larger data volumes in Power BI. For individual users, Premium also
enables widespread distribution of content by Pro users without requiring Pro licenses for recipients who
view the content. For more information, see What is Power BI Premium?.
This article focuses on per-user licensing from an administrator perspective.

Manage Power BI Pro licenses

As an administrator, you can purchase and assign Power BI Pro licenses; and you can sign up for a Power BI Pro
trial for your organization. Individuals can also sign up for a Power BI Pro trial.
Purchasing Power BI Pro
You purchase Power BI Pro licenses through Microsoft Office 365 or through a certified Microsoft partner. After
you purchase the licenses, you assign them to individual users. For more information, see Purchase and assign
Power BI Pro licenses.
Power BI Pro trial for individuals
Individuals in your organization can sign up for a Power BI Pro trial. For more information, see Signing up for
Power BI as an individual.
Users who take advantage of the in-product Power BI Pro trial do not appear in the Microsoft 365 admin center
as Power BI Pro Trial users (they appear as Power BI free users). They do, however, show up as Power BI Pro Trial
users in the manage storage page in Power BI.
Power BI Pro trial for organizations
If you want to acquire and deploy Power BI trial licenses to multiple users in your organization without users
accepting trial terms individually, sign up for a Power BI Pro trial for your organization.
Keep the following in mind before you follow the steps to sign up:
To sign up, you must be a member of the Global administrator or Billing administrator role in Office
365.
There is a limit of one organizational trial per tenant. This means that if someone has already applied the
Power BI Pro Trial to your tenant, you cannot do it again. If you need assistance with this, contact Office
365 Billing support.
1. Navigate to the Microsoft 365 admin center.
2. On the left navigation pane, select Billing then Subscriptions.
3. On the right side, select Add subscriptions.

4. Under Other Plans, hover over the ellipsis (. . .) for Power BI Pro and select Start free trial.
5. On the order confirmation screen, select Try now.
6. On the order receipt, select Continue.
Now you can assign licenses in Office 365.

Manage Power BI free licenses

Users within your organization can gain access to Power BI free licenses in two different ways:
You can assign a Power BI license to them within the Microsoft 365 admin center.
If a user signs up for a Power BI Pro trial and the trial expires, they are assigned a free license.
Requesting and assigning free licenses
If you plan to manage license requests and assignments centrally, first check whether you already have the
unlimited Power BI (free) license block.
This block of licenses is available after the first time someone signs up for Power BI as an individual. During that
process, this license block is attached to your organization, and a license is assigned to the user who is signing up.
1. In the Microsoft 365 admin center, under Billing > Licenses, check for unlimited.

2. If the block is available, you can now assign licenses in Office 365. If the block isn't available, you have two
choices:
Have a member of your organization sign up individually, which triggers the creation of the
unlimited block.
 Go to the next procedure, where you can sign up for a fixed number of licenses.
If the unlimited Power BI (free) license block isn't available and you don't want to do an individual sign up, follow
this procedure.
1. Navigate to the Microsoft 365 admin center.
2. On the left navigation pane, select Billing > Subscriptions.
3. On the right side, select Add subscriptions +.
4. Under Other Plans, hover over the ellipsis (. . .) for Power BI (free) and select Buy now.

5. Enter the number of licenses you want to add and select Check out now or Add to cart.
6. Enter the required information in the check out flow.
There is no purchase when using this approach, although you will need to either enter your credit card
information for billing, or choose to be invoiced.
7. You can now assign licenses in Office 365.
8. If you decide later that you want to add more licenses, you can go back to Add subscriptions, and select
Change license quantity for Power BI (free).

Enable or disable individual user sign up in Azure Active Directory

As an administrator, you can choose to enable or disable individual user sign ups through Azure Active Directory
(AAD ). This section of the article shows you how to manage sign ups with PowerShell commands. For more
information about Azure PowerShell, see Overview of Azure PowerShell.
The AAD setting that controls sign up is AllowAdHocSubscriptions. In most tenants, this is set to true, which
means it is enabled. If you acquired Power BI through a partner, this might be set to false, which means it is
disabled. If you change the setting from true to false, new users in your organization are blocked from signing up
individually. Users that signed up for Power BI prior to the setting change retain their licenses.
1. Sign into Azure Active Directory using your Office 365 credentials. The first line of the following
PowerShell script prompts you for your credentials. The second line connects to Azure Active Directory.

$msolcred = get-credential
connect-msolservice -credential $msolcred

2. Once you are signed in, run the following command to see how your tenant is currently configured.

Get-MsolCompanyInformation | fl AllowAdHocSubscriptions

3. Run the following command to enable ($true) or disable ($false) AllowAdHocSubscriptions.

Set-MsolCompanySettings -AllowAdHocSubscriptions $true

NOTE
The AllowAdHocSubscriptions flag is used to control several user capabilities in your organization, including the ability for
users to sign up for the Azure Rights Management Service. Changing this flag affects all of these capabilities.

Next steps
Self-service sign up for Power BI
Purchase and assign Power BI Pro licenses
More questions? Try asking the Power BI Community
 Purchase and assign Power BI Pro licenses
3/22/2019 • 2 minutes to read • Edit Online

Power BI Pro is an individual license that allows access to all content and capabilities in the Power BI service,
including the ability to share content and collaborate with other Pro users. Only Pro users can publish to and
consume content from app workspaces, share dashboards, and subscribe to dashboards and reports. For more
information, see Power BI features by license type.
This article first explains how to purchase Power BI Pro licenses in Office 365. The article then explains the two
options you have for assigning those licenses to individual users: Office 365 and Azure (choose one option).

Prerequisites
You must be a member of the Global administrator or Billing administrator role in Office 365.
To assign licenses in Azure, you must be an owner of the Azure subscription that Power BI uses for Active
Directory lookups.

Purchase licenses in Office 365

Follow these steps to purchase Power BI Pro licenses:
1. Open the Microsoft 365 admin center.
2. On the left navigation pane, select Billing > Subscriptions.

3. In the upper right corner of the Subscriptions page, select Add subscriptions.
4. Locate the desired subscription offering:
Under Enterprise Suite, select Office 365 Enterprise E5.

Under Other Plans, select Power BI Pro.

5. Hover over the ellipsis (. . .) for the desired subscription, and select Buy now.
6. Choose Pay monthly or Pay for a full year, according to your billing preference.
7. Under How many users do you want? enter the desired number of licenses, and then select Check out
now to complete the transaction.
8. Verify that the acquired subscription is now listed on the Subscriptions page.

9. To add more licenses after the initial purchase, select Power BI Pro from the Subscriptions page, and
then select Add/Remove licenses.

Assign licenses in Office 365

Follow these steps to assign Power BI Pro licenses to individual user accounts:
1. Open the Microsoft 365 admin center.
2. On the left navigation pane, expand Users, and then select Active users.

3. Select a user, then under Product licenses select Edit.

4. Under Power BI Pro, toggle the setting to On, then select Save.

5. Under Status for the selected account, verify that the Power BI Pro license has been assigned successfully.
Assign licenses in Azure
Follow these steps to assign Power BI Pro licenses to individual user accounts:
1. Open the Azure portal.
2. In the left navigation bar, select Azure Active Directory.

3. Under Azure Active Directory, select Licenses.

4. Under Licenses, select All products then select Power BI Pro to display the list of licensed users.

5. Select Assign to add a Power BI Pro license to an additional user account.

Next steps
Now that you've assigned licenses, learn more about Power BI Pro.
Power BI licensing in your organization
Find Power BI users who have signed in
More questions? Try asking the Power BI Community
 Signing up for Power BI with a new Office 365 Trial
1/30/2019 • 2 minutes to read • Edit Online

https://www.youtube.com/embed/gbSuFST-Nx4?showinfo=0
This article describes an alternative way to sign up for Power BI, using an Office 365 trial. If you're having
problems signing up for Power BI with your work email address, first make sure it's an email address that can be
used with Power BI. If that's not successful, try signing up for an Office 365 trial first and then signing up for
Power BI. You'll be able to use Power BI even after the Office 365 trial expires.
1. Sign up for an Office 365 trial on the Office 365 web site.
2. When you complete that signup process, you're given a new sign-in name that looks like
[email protected]. This is the sign-in you'll use with Power BI.
3. Sign up for Power BI using this link. If you're prompted, sign in using the sign-in name and password you
selected for Office 365 in the previous step.
4. That's it! When you're finished, you'll be redirected to Power BI. If you have any issues signing in with the
new account, try using a private browser session.

Important considerations
By using this signup method, you are creating a new organizational tenant and you'll become the administrator of
the tenant. For more information, see What is Power BI administration?. You can add new users to your tenant,
then share with them, as described in the Office 365 admin documentation.

Next steps
What is Power BI administration?
Power BI licensing in your organization
Signing up for Power BI as an individual
More questions? Try asking the Power BI Community
 Unable to add Power BI to Office 365 partner
subscription
3/22/2019 • 2 minutes to read • Edit Online

Office 365 enables companies to resell Office 365 bundled and integrated with their own solutions, providing end-
customers with a single point of contact for purchasing, billing, and support.
If you are interested in acquiring Power BI alongside your Office 365 subscription, we recommend you contact
your partner to do so. If your partner does not currently offer Power BI, you have different options to pursue.

Work with your partner to purchase Power BI

If you want to buy a subscription to Power BI Pro or Power BI Premium, work with your partner to consider what
options you have:
Your partner agrees to add Power BI to their portfolio so that you can purchase from them.
Your partner is able to transition you to a model where you can buy Power BI directly from Microsoft or
another partner who offers Power BI.

Purchase from Microsoft or another channel

Depending on the relationship with your partner, you might be able to purchase Power BI directly from Microsoft
or another partner. You can verify whether you can add Power BI subscriptions in the Microsoft 365 admin center
(requires membership in the Global Administrator or Billing Administrator role).
1. Go to the Microsoft 365 admin center.
2. In the left menu, open Billing:
If you see Subscriptions, you can acquire the service from Microsoft directly, or you can contact
another partner that offers Power BI.

If you don't see Subscriptions, you can't buy from Microsoft directly or from another partner.
If your partner does not offer Power BI and you can't buy directly from Microsoft or another partner, consider
signing up for a free trial.
Sign up for a free trial
You can sign up for a free trial of Power BI Pro. If you don't purchase Power BI Pro at the end of the trial period,
you still have a free license that offers many of the features of Power BI. For more information, see Power features
by license type.
Enable ad-hoc subscriptions
By default, individual sign-ups (also known as ad-hoc subscriptions) are disabled. In this case, you see the
following message when you try to sign up: Your IT department has turned off signup for Microsoft Power BI.

To enable ad-hoc subscriptions, you can contact your partner and request that they turn it on. If you are an
administrator of your tenant, and know how to use Azure Active Directory PowerShell commands, you can enable
ad-hoc subscriptions yourself. Azure Active Directory PowerShell for Graph
1. Sign in to Azure Active Directory using your Office 365 credentials. The first line of the script below
prompts you for your credentials. The second line connects to Azure Active Directory.

$msolcred = get-credential
connect-msolservice -credential $msolcred

2. Once you're signed in, run the following command to check the current setting for AllowAdHocSubscriptions .

Get-MsolCompanyInformation
3. Run the following command to enable free sign ups.

Set-MsolCompanySettings -AllowAdHocSubscriptions $true

Next steps
Power BI licensing in your organization
More questions? Try asking the Power BI Community
 Administering Power BI in the admin portal
4/1/2019 • 15 minutes to read • Edit Online

The admin portal enables you to manage a Power BI tenant for your organization. The portal includes items
such as usage metrics, access to the Microsoft 365 admin center, and settings.
The full admin portal is accessible to all users who are Global Admins in Office 365 or have been assigned the
Power BI service administrator role. If you're not in one of these roles, you only see Capacity settings in the
portal. For more information about the Power BI service administrator role, see Understanding the Power BI
admin role.

How to get to the admin portal

Your account needs to be marked as a Global Admin, within Office 365 or Azure Active Directory, or have been
assigned the Power BI service administrator role, to get access to the Power BI admin portal. For more
information about the Power BI service administrator role, see Understanding the Power BI admin role. To get to
the Power BI admin portal, do the following.
1. Select the settings gear in the top right of the Power BI service.
2. Select Admin portal.

There are seven tabs in the portal. The rest of this article provides information about each of these tabs.
 Usage metrics
Users
Audit logs
Tenant settings
Capacity settings
Embed codes
Organizational visuals

Usage metrics
The Usage metrics enables you to monitor Power BI usage for your organization. It also provides the ability to
see which users, and groups, are the most active within Power BI for your organization.

NOTE
The first time you access the dashboard, or after you visit again after a long period of not viewing the dashboard, you'll
likely see a loading screen while we load the dashboard.

Once the dashboard loads, you see two sections of tiles. The first section includes usage data for individual users,
and the second section has similar information for groups in your organization.
Here’s a breakdown of what you can see in each tile:
Distinct count of all dashboards, reports, and datasets in the user workspace

Most consumed dashboard by number of users who can access it. For example, if you have a dashboard
that you shared with 3 users, and you also added it to a content pack that two different users connected
to, its count would be 6 (1 + 3 + 2)
 The most popular content users connected to. This would be anything the users could reach through the
Get Data process, so SaaS content packs, Organizational content packs, files or databases.

A view of your top users based on how many dashboards they have, both dashboards they created
themselves and dashboards shared to them.

A view of your top users based on how many reports they have

The second section shows the same type of information, but based on groups. This lets you see which groups in
your organization are most active and what kind of content they are consuming.
With this information, you can get real insights into how people are using Power BI across your organization,
and be able to recognize those users and groups who are very active in your organization.

Users
You manage Power BI users, groups, and admins in the Microsoft 365 admin center. The Users tab provides a
link to the admin center for your tenant.

Audit logs
You manage Power BI audit logs in the Office 365 Security & Compliance center. The Audit logs tab provides a
link to the Security & Compliance center for your tenant. Learn more
To use audit logs, make sure the Create audit logs for internal activity auditing and compliance setting is
enabled.

Tenant settings
The Tenant settings tab enables fine-grained control over the features that are made available to your
organization. If you have concerns around sensitive data, some of our features may not be right for your
organization, or you may only want a particular feature to be available to a specific group.
The following image shows the first two sections of the Tenant settings tab.

NOTE
It can take up to 10 minutes for a setting change to take effect for everyone in your tenant.
Settings can have three states:
Disabled for the entire organization: No one in your organization can use this feature.

Enabled for the entire organization: Everyone in your organization can use this feature.

Enabled for a subset of the organization: A specific subset of users or groups in your organization can
use this feature.
You can enable the feature for your entire organization, except for a specific group of users.

You can also enable the feature only for a specific group of users and also disable it for a group of users.
Using this approach ensures that certain users do not have access to the feature even if they are in the
allowed group.
The next few sections provide an overview of the different types of tenant settings.

Workspace settings
Create workspaces (preview)
Users in the organization can create app workspaces to collaborate on dashboards, reports, and other content.
Learn more

Export and sharing settings

Share content to external users
Users in the organization can share dashboards with users outside the organization. Learn more

The following image shows the message that appears when you share with an external user.
Publish to web
Users in the organization can publish reports to the web. Learn more
The following image shows the File menu for a report when the Publish to web setting is enabled.

Users see different options in the UI based on what the Publish to web setting is.

ENABLED FOR ENTIRE DISABLED FOR ENTIRE

FEATURE ORGANIZATION ORGANIZATION SPECIFIC SECURITY GROUPS

Publish to web under Enabled for all Not visible for all Only visible for authorized
report's File menu. users or groups.

Manage embed codes Enabled for all Enabled for all Enabled for all
under Settings
* Delete option only for
authorized users or groups.
* Get codes enabled for all.

Embed codes within admin Status reflects one of the Status displays Disabled Status reflects one of the
portal following: following:
* Active * Active
* Not supported * Not supported
* Blocked * Blocked

If a user is not authorized

based on the tenant setting,
status displays as infringed.

Existing published reports All enabled All disabled Reports continue to render
for all.

Export data
Users in the organization can export data from a tile or visualization. Learn more
The following image shows the option to export data from a tile.
 NOTE
Disabling Export Data also prevents users from using the Analyze in Excel feature, as well as using the Power BI service
live connection.

Export reports as PowerPoint presentations or PDF documents

Users in the organization can export Power BI reports as PowerPoint files or PDF documents. Learn more
The following image shows the File menu for a report when the Export reports as PowerPoint presentations
or PDF documents setting is enabled.

Print dashboards and reports

Users in the organization can print dashboards and reports. Learn more
The following image shows the option to print a dashboard.

The following image shows the File menu for a report when the Print dashboards and reports setting is
enabled.
Allow external guest users to edit and manage content in the organization
Azure B2B guest users can edit and manage content in the organization. Learn more
The following image shows the option to Allow external guest users to edit and manage content in the
organization.

Content pack and app settings

Publish content packs and apps to the entire organization
Users in the organization can publish content packs and apps to the entire organization, rather than just specific
groups. Learn more
The following image shows the My entire organization option when creating a content pack.
Create template apps
Users in the organization can create template apps that use datasets built in Power BI Desktop. Learn more
about template apps
Push apps to end users
Users can share apps directly with end users without requiring installation from AppSource. Learn more

Integration settings
Ask questions about data using Cortana
Users in the organization can ask questions about their data using Cortana. Learn more

NOTE
This setting applies to the entire organization and cannot be limited to specific groups.

Use Analyze in Excel with on-premises datasets

Users in the organization can use Excel to view and interact with on-premises Power BI datasets. Learn more

NOTE
Disabling Export Data also prevents users from using the Analyze in Excel feature.

Use ArcGIS Maps for Power BI

Users in the organization can use the ArcGIS Maps for Power BI visualization provided by Esri. Learn more
Use global search for Power BI (Preview)
Users in the organization can use external search features that rely on Azure Search. For example, users can use
Cortana to retrieve key information directly from Power BI dashboards and reports. Learn more

Custom visuals settings

Add and use custom visuals
Users in the organization can interact with and share custom visuals. Learn more

NOTE
This setting can be applied to the entire organization or can be limited to specific groups.

Power BI Desktop (starting from March '19 release) supports using Group Policy to disable the usage of
custom visuals across an organization's deployed computers.

ATTRIBUTE VALUE
 key Software\Policies\Microsoft\Power BI Desktop\

valueName EnableCustomVisuals

A value of 1 (decimal) enables the use of custom visuals in Power BI (This is the default).
A value of 0 (decimal) disable the use of custom visuals in Power BI.
Allow only certified visuals
Users in the organization who have been granted permissions to add and use custom visuals, denoted by the
setting "Add and use custom visuals", will only be able to use certified custom visuals (uncertified visuals will be
blocked and will display an error message when used).
Power BI Desktop (starting from March '19 release) supports using Group Policy to disable the usage of
uncertified custom visuals across an organization's deployed computers.

ATTRIBUTE VALUE

key Software\Policies\Microsoft\Power BI Desktop\

valueName EnableUncertifiedVisuals

A value of 1 (decimal) enables the use of uncertified custom visuals in Power BI (This is the default).
A value of 0 (decimal) disable the use of uncertified custom visuals in Power BI (This option enables only the use
of certified custom visuals).

R visuals settings
Interact with and share R visuals
Users in the organization can interact with and share visuals created with R scripts. Learn more

NOTE
This setting applies to the entire organization and cannot be limited to specific groups.

Audit and usage settings

Create audit logs for internal activity auditing and compliance
Users in the organization can use auditing to monitor actions taken in Power BI by other users in the
organization. Learn more
This setting must be enabled for audit log entries to be recorded. There can be up to a 48 hour delay between
enabling auditing and being able to view audit data. If you don't see data immediately, check the audit logs later.
There can be a similar delay between getting permission to view audit logs and being able to access the logs.

NOTE
This setting applies to the entire organization and cannot be limited to specific groups.

Usage metrics for content creators

Users in the organization can see usage metrics for dashboards and reports they create. Learn more
Per-user data in usage metrics for content creators
Usage metrics for content creators will expose display names and email addresses of users who are accessing
content. Learn more
Per-user data is enabled for usage metrics by default, and content creator account information is included in the
metrics report. If you don’t want to include this information for some or all users, disable the feature for
specified security groups or for an entire organization. Account information will then show in the report as
Unnamed.

Dashboard settings
Data classification for dashboards
Users in the organization can tag dashboards with classifications that indicate dashboard security levels. Learn
more

NOTE
This setting applies to the entire organization and cannot be limited to specific groups.

Developer settings
Embed content in apps
Users in the organization can embed Power BI dashboards and reports in Software as a Service (SaaS )
applications. Disabling this setting prevents users from being able to use the REST APIs to embed Power BI
content within their application. Learn more

Dataflow settings
Create and use dataflows
Users in the organization can create and use dataflows. For an overview of dataflows, see Self-service data prep
in Power BI. To enable dataflows in a Premium capacity, see Configure workloads.

NOTE
This setting applies to the entire organization and cannot be limited to specific groups.

Template apps settings (preview)

Two settings control template apps.
The first setting, Create template apps, controls who in your organization can create template apps. Template
app creators can then distribute them to clients outside your organization by way of AppSource or other
distribution method.

With the second setting, Install template apps, you control who in your organization can download and install
template apps from AppSource or another source

Capacity settings
Power BI Premium
The Power BI Premium tab enables you to manage any Power BI Premium capacities (EM or P SKU ) that have
been purchased for your organization. All users within your organization can see the Power BI Premium tab,
but they only see contents within it if they are assigned as either a Capacity admin or a user that has assignment
permissions. If a user does not have any permissions, the following message appears.

Power BI Embedded
The Power BI Embedded tab enables you to view your Power BI Embedded (A SKU ) capacities that you've
purchased for your customer. Since you can only purchase A SKUs from Azure, you manage embedded
capacities in Azure from the Azure Portal.
For more information about how to manage Power BI Embedded (A SKU ) settings, see What is Power BI
Embedded.

Embed codes
As an administrator, you can view the embed codes that are generated for your tenant. You can also revoke or
delete codes. Learn more

Organizational visuals
The Organizational visuals tab enables you to deploy and manage custom visuals inside your organization.
With organizational visuals, you can easily deploy proprietary visuals in your organization, which report authors
can then discover and import into their reports from Power BI Desktop. Learn more

WARNING
A custom visual could contain code with security or privacy risks; make sure you trust the author and the source of the
custom visual before deploying to the organization's repository.

The following image shows all the custom visuals that are currently deployed in an organization's repository.
Add a new custom visual
To add a new custom visual to the list, follow these steps.
1. In the right pane, select Add a custom visual.

2. Fill in the Add custom visual form:

Choose a .pbiviz file (required): select a custom visual file to upload. Only versioned API custom
visuals are supported (read here what this means).
Before you upload a custom visual, you should review that visual for security and privacy to make sure it
fits your organization's standards.
Name your custom visual (required): give a short title to the visual so Power BI Desktop users
easily understand what it does
Icon: The icon file that is shown in the Power BI Desktop UI.
 Description: a short description of the visual to provide more context and education to the user
3. Select Add to initiate the upload request. If successful you can see the new item in the list. If failed, you
can get an appropriate error message
Delete a custom visual from the list
To permanently delete a visual, select the trash bin icon for the visual in the repository.

IMPORTANT
Deletion is irreversible. Once deleted, the visual immediately stops rendering in existing reports. Even if you upload the
same visual again, it won't replace the previous one that was deleted. However, users can import the new visual again and
replace the instance they have in their reports.

Disable a custom visual in the list

To disable the visual from the organizational store, select the gear icon. In the Access section, disable the custom
visual.
After you disable the visual, the visual won't render in existing reports, and it displays the error message below.
This custom visual is no longer available. Please contact your administrator for details.
However, visuals that are bookmarked still work.
After any update or administrator change, Power BI Desktop users should restart the application or refresh the
browser in the Power BI service to see the updates.
Update a visual
To update the visual from the organizational store, select the gear icon. Browse and upload a new version of the
visual.
Make sure the Visual ID remains unchanged. The new file replaces the previous file for all the reports
throughout the organization. However, if the new version of the visual might break any usage or data structure
of the previous version of the visual, then do not replace the previous version. Instead, you should create a new
listing for the new version of the visual. For example, add a new version number (version X.X) to the title of the
new listed visual. This way it is clear that it is the same visual just with an updated version number, so existing
reports do not break their functionality. Again, make sure the Visual ID remains unchanged. Then the next time
users enter the organization repository from Power BI Desktop, they can import the new version, which prompts
them to replace the current version that they have in the report.
For more information, visit Frequently asked questions about organizational custom visuals

Dataflow storage (preview)

By default, data used with Power BI is stored in internal storage provided by Power BI. With the integration of
dataflows and Azure Data Lake Storage Gen2 (ADLS Gen2), you can store your dataflows in your organization's
Azure Data Lake Storage Gen2 account. For more information, see Dataflows and Azure Data Lake integration
(Preview ).

Workspaces (preview)
As an administrator, you can view the workspaces that exist in your tenant. You can sort and filter the list of
workspaces and display the details for each workspace. Note that the table columns correspond to the properties
returned by the Power BI admin Rest API for workspaces. Personal workspaces are of type PersonalGroup,
legacy workspaces are of type Group, and modern workspaces are of type Workspace. For more information,
see Create the new workspaces (preview ) in Power BI.
Next steps
Administering Power BI in your Organization Understanding the Power BI admin role
Auditing Power BI in your organization
More questions? Try asking the Power BI Community
 Where is my Power BI tenant located?
3/7/2019 • 2 minutes to read • Edit Online

https://www.youtube.com/embed/0fOxaHJPvdM?showinfo=0
Learn where your Power BI tenant is located and how that location is selected. Understanding the location is
important, because it can impact the interactions you have with the service.

How to determine where your Power BI tenant is located

To find the region your tenant is in, follow these steps.
1. In the Power BI service, in the top menu, select help ( ?) then About Power BI.
2. Look for the value next to Your data is stored in. This is the region where your tenant is located. This is
also the region where your data is stored, unless you are using dedicated capacities in different regions for
your workspaces.

How the data region is selected

The data region is based on the country you select when you create the tenant. This applies to sign up for Office
365 in addition to Power BI, because this information is shared. If this is a new tenant, select the appropriate
country from the list when you sign up.
Power BI picks a data region closest to this selection, which determines where data is stored for your tenant.

IMPORTANT
You cannot change this selection after you create the tenant.

More questions? Try the Power BI Community

 Find Power BI users that have signed in
4/2/2019 • 2 minutes to read • Edit Online

If you are a tenant admin, and want to see who has signed into Power BI, use the Azure Active Directory access
and usage reports to gain visibility.
https://www.youtube.com/embed/1AVgh9w9VM8?showinfo=0

NOTE
The activity report provides useful information, but it doesn't identify the type of license each user has. Use the Microsoft
365 admin center to view licenses.

Requirements
Any user (including non-admins) can see a report of their own sign-ins, but you must meet the following
requirements to see a report for all users.
Your tenant must have an Azure AD Premium license associated with it.
You must be in one of the following roles: Global Admin, Security Admin, or Security Reader.

Use the Azure portal to view sign-ins

To view sign-in activity, follow these steps.
1. In the Azure portal, select Azure Active Directory.
2. Under Monitoring, select Sign-ins.

3. Filter the application by either Microsoft Power BI or Power BI Gateway, and select Apply.
Microsoft Power BI filters to sign-in activity related to the service, whereas Power BI Gateway filters to
sign-in activity specific to the On-premises data gateway.
Export the data
You have two options to export the sign-in data: download a csv file, or use PowerShell. At the top of the sign-in
report, select one of the following options:
Download to download a csv file for the currently filtered data.
Script to download a PowerShell script for the currently filtered data. You can update the filter in the script
as necessary.

Data retention
Sign-in related data is available for up to 30 days. For more information, see Azure Active Directory report
retention policies.

Next steps
Using auditing within your organization
More questions? Try asking the Power BI Community
 Using auditing within your organization
3/22/2019 • 9 minutes to read • Edit Online

Knowing who is taking what action on which item in your Power BI tenant can be critical in helping your
organization fulfill its requirements, such as meeting regulatory compliance and records management. Use
Power BI auditing to audit actions performed by users, such as "View Report" and "View Dashboard". You cannot
use auditing to audit permissions.
You work with auditing in the Office 365 Security and Compliance Center or use PowerShell. Auditing relies on
functionality in Exchange Online, which is automatically provisioned to support Power BI.
You can filter the audit data by date range, user, dashboard, report, dataset and activity type. You can also
download the activities in a csv (comma separated value) file to analyze offline.

Requirements
You must meet these requirements to access audit logs:
You must either be a global admin or be assigned the Audit Logs or View -Only Audit Logs role in
Exchange Online to access the audit log. By default, these roles are assigned to the Compliance
Management and Organization Management role groups on the Permissions page in the Exchange
admin center.
To provide non-administrator accounts with access to the audit log, you must add the user as a member of
one of these role groups. Alternatively, you can create a custom role group in the Exchange admin center,
assign the Audit Logs or View -Only Audit Logs role to this group, and then add the non-administrator
account to the new role group. For more information, see Manage role groups in Exchange Online.
If you can't access the Exchange admin center from the Microsoft 365 admin center, go to
https://outlook.office365.com/ecp and sign in using your credentials.
If you have access to the audit log but are not a global admin or Power BI Service admin, you will not have
access to the Power BI Admin portal. In this case, you must use a direct link to the Office 365 Security &
Compliance Center.

Accessing your audit logs

To access logs, first make sure that logging is enabled in Power BI. For more information, see Audit logs in the
admin portal documentation. There can be up to a 48 hour delay between enabling auditing and being able to
view audit data. If you don't see data immediately, check the audit logs later. There can be a similar delay between
getting permission to view audit logs and being able to access the logs.
The Power BI audit logs are available directly through the Office 365 Security & Compliance Center. There is also
a link from the Power BI admin portal:
1. In Power BI, select the gear icon in the upper right, then select Admin portal.
2. Select Audit logs.
3. Select Go to Microsoft 365 admin center.

Search only Power BI activities

Restrict results to only Power BI activities by following these steps. For a list of activities, see the list of activities
audited by Power BI later in this article.
1. On the Audit log search page, under Search, select the drop down for Activities.
2. Select Power BI activities.
3. Select anywhere outside of the selection box to close it.
Your searches will now be filtered to only Power BI activities.

Search the audit logs by date

You can search the logs by date range using the Start date and End date fields. The last seven days are selected
by default. The date and time are presented in Coordinated Universal Time (UTC ) format. The maximum date
range that you can specify is 90 days.
An error is displayed if the selected date range is greater than 90 days. If you're using the maximum date range of
90 days, select the current time for Start date. Otherwise, you'll receive an error saying that the start date is
earlier than the end date. If you've turned on auditing within the last 90 days, the date range can't start before the
date that auditing was turned on.
Search the audit logs by users
You can search for audit log entries for activities performed by specific users. To do this, enter one or more user
names in the Users field. The user name looks like an email address; it's the account that users log into Power BI
with. Leave this box blank to return entries for all users (and service accounts) in your organization.

View search results

After you select Search, the search results are loaded and after a few moments they are displayed under Results.
When the search is finished, the number of results found is displayed. A maximum of 1000 events is displayed, If
more than 1000 events meet the search criteria, the newest 1000 events are displayed.
View the main results
The Results area contains the following information for each event returned by the search. Select a column
header under Results to sort the results.

COLUMN DEFINITION

Date The date and time (in UTC format) when the event occurred.

IP address The IP address of the device that was used when the activity
was logged. The IP address is displayed in either an IPv4 or
IPv6 address format.

User The user (or service account) who performed the action that
triggered the event.

Activity The activity performed by the user. This value corresponds to

the activities that you selected in the Activities drop down
list. For an event from the Exchange admin audit log, the
value in this column is an Exchange cmdlet.

Item The object that was created or modified as a result of the

corresponding activity. For example, the file that was viewed
or modified, or the user account that was updated. Not all
activities have a value in this column.

Detail Additional detail about an activity. Again, not all activities will
have a value.

View the details for an event

You can view more details about an event by clicking the event record in the list of search results. A Details page
is displayed that contains the detailed properties from the event record. The properties that are displayed depend
on the Office 365 service in which the event occurs.
To display these details, select More information. All Power BI entries have a value of 20 for the RecordType
property. For information about other properties, see Detailed properties in the audit log.
Export search results
To export the Power BI audit log to a csv file, follow these steps.
1. Select Export results.
2. Select either Save loaded results or Download all results.

Use PowerShell to search audit logs

You can also use PowerShell to access the audit logs based on your login. The following example shows how to
connect to Exchange Online PowerShell and then use the Search-UnifiedAuditLog command to pull Power BI
audit log entries. To run the script, you must be assigned the appropriate permissions, as described in the
Requirements section.

Set-ExecutionPolicy RemoteSigned

$UserCredential = Get-Credential

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri

https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -
AllowRedirection

Import-PSSession $Session
Search-UnifiedAuditLog -StartDate 9/11/2018 -EndDate 9/15/2018 -RecordType PowerBI -ResultSize 1000 | Format-
Table | More

For more information on connecting to Exchange Online, see Connect to Exchange Online PowerShell. For
another example of using PowerShell with audit logs, see Using Power BI audit log and PowerShell to assign
Power BI Pro licenses.
Activities audited by Power BI
The following activities are audited by Power BI.

FRIENDLY NAME OPERATION NAME NOTES

Added data source to Power BI AddDatasourceToGateway

gateway

Added Power BI folder access AddFolderAccess Not currently used

Added Power BI group members AddGroupMembers

Admin attached dataflow storage AdminAttachedDataflowStorageAccoun Not currently used

account to tenant tToTenant

Analyzed Power BI dataset AnalyzedByExternalApplication

Analyzed Power BI report AnalyzeInExcel

Binded Power BI dataset to gateway BindToGateway

Changed capacity state ChangeCapacityState

Changed capacity user assignment UpdateCapacityUsersAssignment

Changed Power BI dataset connections SetAllConnections

Changed Power BI gateway admins ChangeGatewayAdministrators

Changed Power BI gateway data ChangeGatewayDatasourceUsers

source users

Created organizational Power BI CreateOrgApp

content pack

Created Power BI app CreateApp

Created Power BI dashboard CreateDashboard

Created Power BI dataflow CreateDataflow

Created Power BI dataset CreateDataset

Created Power BI email subscription CreateEmailSubscription

Created Power BI folder CreateFolder

Created Power BI gateway CreateGateway

Created Power BI group CreateGroup

Created Power BI report CreateReport

FRIENDLY NAME OPERATION NAME NOTES

Dataflow migrated to external storage DataflowMigratedToExternalStorageAcc Not currently used

account ount

Dataflow permissions added DataflowPermissionsAdded Not currently used

Dataflow permissions removed DataflowPermissionsRemoved Not currently used

Deleted organizational Power BI DeleteOrgApp

content pack

Deleted Power BI comment DeleteComment

Deleted Power BI dashboard DeleteDashboard Not currently used

Deleted Power BI dataflow DeleteDataflow Not currently used

Deleted Power BI dataset DeleteDataset

Deleted Power BI email subscription DeleteEmailSubscription

Deleted Power BI folder DeleteFolder

Deleted Power BI folder access DeleteFolderAccess Not currently used

Deleted Power BI gateway DeleteGateway

Deleted Power BI group DeleteGroup

Deleted Power BI report DeleteReport

Discovered Power BI dataset data GetDatasources

sources

Downloaded Power BI report DownloadReport

Edited Power BI certification permission EditCertificationPermission Not currently used

Edited Power BI dashboard EditDashboard Not currently used

Edited Power BI dataset EditDataset

Edited Power BI dataset properties EditDatasetProperties Not currently used

Edited Power BI report EditReport

Exported Power BI dataflow ExportDataflow

Exported Power BI report visual data ExportReport

Exported Power BI tile data ExportTile

FRIENDLY NAME OPERATION NAME NOTES

Failed to add dataflow permissions FailedToAddDataflowPermissions Not currently used

Failed to remove dataflow permissions FailedToRemoveDataflowPermissions Not currently used

Generated Power BI dataflow SAS GenerateDataflowSasToken

token

Generated Power BI Embed Token GenerateEmbedToken

Imported file to Power BI Import

Installed Power BI app InstallApp

Migrated workspace to a capacity MigrateWorkspaceIntoCapacity

Posted Power BI comment PostComment

Printed Power BI dashboard PrintDashboard

Printed Power BI report page PrintReport

Published Power BI report to web PublishToWebReport

Received Power BI dataflow secret from ReceiveDataflowSecretFromKeyVault Not currently used

Key Vault

Removed data source from Power BI RemoveDatasourceFromGateway

gateway

Removed Power BI group members DeleteGroupMembers

Removed workspace from a capacity RemoveWorkspacesFromCapacity

Renamed Power BI dashboard RenameDashboard

Requested Power BI dataflow refresh RequestDataflowRefresh Not currently used

Requested Power BI dataset refresh RefreshDataset

Retrieved Power BI workspaces GetWorkspaces

Set scheduled refresh on Power BI SetScheduledRefreshOnDataflow

dataflow

Set scheduled refresh on Power BI SetScheduledRefresh

dataset

Shared Power BI dashboard ShareDashboard

Shared Power BI report ShareReport

 FRIENDLY NAME OPERATION NAME NOTES

Started Power BI extended trial OptInForExtendedProTrial Not currently used

Started Power BI trial OptInForProTrial

Took over a Power BI datasource TakeOverDatasource

Took over Power BI dataset TakeOverDataset

Unpublished Power BI app UnpublishApp

Update capacity resource governance UpdateCapacityResourceGovernanceSe Not currently in Microsoft 365 admin
settings ttings center

Updated capacity admin UpdateCapacityAdmins

Updated capacity display name UpdateCapacityDisplayName

Updated organization's Power BI UpdatedAdminFeatureSwitch

settings

Updated Power BI app UpdateApp

Updated Power BI dataflow UpdateDataflow

Updated Power BI dataset data sources UpdateDatasources

Updated Power BI dataset parameters UpdateDatasetParameters

Updated Power BI email subscription UpdateEmailSubscription

Updated Power BI folder UpdateFolder

Updated Power BI folder access UpdateFolderAccess

Updated Power BI gateway data source UpdateDatasourceCredentials

credentials

Viewed Power BI dashboard ViewDashboard

Viewed Power BI dataflow ViewDataflow

Viewed Power BI report ViewReport

Viewed Power BI tile ViewTile

Viewed Power BI usage metrics ViewUsageMetrics

Next steps
What is Power BI administration?
Power BI Admin Portal
More questions? Try asking the Power BI Community
 Track Power BI service health in Office 365
3/22/2019 • 2 minutes to read • Edit Online

The Microsoft 365 admin center provides important tools for Power BI administrators, including current and
historical information about service health. To access this information, you must be in one of the following roles:
Power BI Service Administrator or Office 365 Global Administrator. For more information about roles, see
Administrator roles related to Power BI.
1. Sign in to the Microsoft 365 admin center.
2. Select the Service health tile.

3. In the current list select N advisories or N incidents, and review the results. In the graphic below, you see
one of three active advisories.

4. To see more information, select Show details for an item. In the graphic below, you see additional details,
including recent status updates.
 Scroll down to see more info, then close the pane when you're finished.
5. To see historical information across all services, in the upper right of the main list select View history. Then
select Last 7 days or Last 30 days. To return to current service health, select View current status.
 Closing your Power BI Account
1/14/2019 • 2 minutes to read • Edit Online

If you don't want to use Power BI any longer, you can close your Power BI account. After your account is closed,
you can no longer sign in to Power BI. Any customer data you uploaded or created in Power BI is deleted,
according to the data retention policy in the Power BI Terms of Service.

Individual Power BI users

If you signed up for Power BI as an individual, you can close your account from the Settings screen.
1. In Power BI, select the gear in the upper right, then select Settings.

2. On the General tab, select Close Account.

3. Select a reason for closing the account (1). You can also provide further information (2). Then select Close
account.
4. Confirm that you want to close your account.

You should see a confirmation that your account is closed. You can reopen your account from here if
necessary.

Managed tenant users

If your organization signed you up for Power BI, contact your tenant admin. Ask them to unassign the license from
your account.

More questions? Try asking the Power BI Community

 Power BI and ExpressRoute
1/14/2019 • 2 minutes to read • Edit Online

ExpressRoute is an Azure service that lets you create private connections between Azure datacenters (where
Power BI resides) and your on-premises infrastructure, or create private connections between Azure datacenters
and your colocation environment.
With Power BI and ExpressRoute, you can create a private network connection from your organization to Power
BI (or using an ISP’s colocation facility), bypassing the Internet to better secure your sensitive Power BI data and
connections.
For more information, see ExpressRoute overview. Power BI is compliant with ExpressRoute, with some
exceptions, where Power BI gets or sends data over the public Internet. For a list of the URLs that Power BI uses,
see Power BI URLs.
 Distribute Power BI content to external guest users
with Azure AD B2B
3/7/2019 • 5 minutes to read • Edit Online

Power BI integrates with Azure Active Directory business-to-business (Azure AD B2B ) to allow secure distribution
of Power BI content to guest users outside your organization, while still maintaining control over the internal data.
Additionally, you can allow guest users outside your organization to edit and manage content within your
organization.

Enable access
Make sure the Share content with external users feature is enabled in the Power BI admin portal before inviting
guest users.
Additionally, the Allow external guest users to edit and manage content in the organization feature lets you select
which guest user can see and create content in workspaces, including browsing your organization's Power BI.

Who can you invite?

You can invite guest users with any email address, including personal accounts such as gmail.com, outlook.com,
and hotmail.com. In Azure AD B2B, these addresses are called social identities.

Invite guest users

Invitations are required only for the first time an external guest user is invited to your organization. There are two
ways to invite users: planned invites and ad-hoc invites.
Planned invites
Use a planned invite if you know which users to invite. You can send the invite using the Azure portal or
PowerShell. You must be a tenant admin to invite people.
Follow these steps to send an invite in the Azure portal.
1. In the Azure Portal, select Azure Active Directory.
2. Under Manage, go to Users > All users > New guest user.
3. Enter an email address and personal message.

4. Select Invite.
To invite more than one guest user, use PowerShell. For more information, see Azure AD B2B collaboration code
and PowerShell samples.
The guest user needs to select Get Started in the email invitation they receive. The guest user is then added to the
tenant.
Ad-hoc invites
To perform an invite at anytime, add the external user to your dashboard or report through the share UI, or your
app through the access page. Here is an example of what to do when inviting an external user to use an app.

The guest user will receive an email indicating that the app has been shared with them.
The guest user must sign in with their organization email address. They will be prompted to accept the invitation
after signing in. After sign in, the guest user is redirected to the app content. To return to the app, they can
bookmark the link or save the email.

Licensing
The guest user must have the proper licensing in place to view the content that was shared. There are three
options to accomplish this: use Power BI Premium; assign a Power BI Pro license; or use the guest's Power BI Pro
license.
When using the Allow external guest users to edit and manage content in the organization feature, guest users
contributing content to workspaces or sharing content with others require a Power BI Pro license.
Use Power BI Premium
Assigning the app workspace to Power BI Premium capacity enables the guest user to use the app without
requiring a Power BI Pro license. Power BI Premium also enables apps to take advantage of other capabilities like
increased refresh rates, dedicated capacity, and large model sizes.

Assign a Power BI Pro license to guest user

Assigning a Power BI Pro license to the guest user, within your tenant, allows that guest user to view content in
the tenant.
Guest user brings their own Power BI Pro license
The guest user already has a Power BI Pro license assigned within their tenant.

Guest users who can edit and manage content

When using the Allow external guest users to edit and manage content in the organization, the specified guest
users get access to your orgnaizaiton's Power BI and see any content to which they have permission. They can
access Home, browse workspaces, install apps that where they are on the access list, and contribute content to
workspaces. They can create or be an Admin of workspaces that use the new workspace experience. Some
limitations apply and are listed in the Considerations and Limitations section.
To help these users login to Power BI, provide them with the Tenant URL. To find the tenant URL, follow these
steps.
1. In the Power BI service, in the top menu, select help ( ?) then About Power BI.
2. Look for the value next to Tenant URL. This is the tenat URL you can share with your guest users.
Considerations and Limitations
By default, External B2B guests are limited to consumption of content only. External B2B guests can view
apps, dashboards, reports, export data and create email subscriptions for dashboards and reports. They
can't access workspaces or publish their own content. However, these restrictions do not apply to guest
users who are allowed through the Allow external guest users to edit and manage content in the
organization tenant setting.
For guest users users enabled through the Allow external guest users to edit and manage content in the
organization tenant setting, some experiences are not available to them. To update or publish reports, they
need to use the Power BI service web UI, including Get Data to upload Power BI Desktop files. The
following experiences are not supported:
Direct publishing from Power BI desktop to the Power BI service
Guest users cannot use Power BI desktop to connect to service datasets in the Power BI service
Classic workspaces tied to Office 365 Groups: Guest user cannot create or be Admins of these
workspaces. They can be members.
Sending ad-hoc invites is not supported for workspace access lists
Power BI Publisher for Excel is not supported for guest users
Guest users cannot install a Power BI Gateway and connect it to your organization
Guest users cannot install apps publish to the entire organization
Guest users cannot use, create, update, or install organizational content packs
Guest users cannot use Analyze in Excel
Guest users cannot be @mentioned in commenting
Guest users cannot use subscriptions
Guest users who use this capability should have a work or school account. Guest users using Personal
accounts will experience more limitations due ot sign-in restrictions.
This feature is not currently available with the Power BI SharePoint Online report web part.
There are Active Directory Settings that can limit what external guest users can do within your overall
organization and that also apply to your Power BI environment. The following documentation discusses the
settings:
Manage External Collaboration Settings
Allow or block invitations to B2B users from specific organizations

Next steps
For more detailed information, including how row -level security works, check out the whitepaper: Distribute
Power BI content to external guest users using Azure AD B2B.
For information regarding Azure AD B2B, see What is Azure AD B2B collaboration?.
 Row-level security (RLS) with Power BI
1/14/2019 • 7 minutes to read • Edit Online

Row -level security (RLS ) with Power BI can be used to restrict data access for given users. Filters restrict data
access at the row level, and you can define filters within roles. Be aware that in the Power BI service, members of
a workspace have access to datasets in the workspace. RLS doesn't restrict this data access.
You can configure RLS for data models imported into Power BI with Power BI Desktop. You can also configure
RLS on datasets that are using DirectQuery, such as SQL Server. Previously, you were only able to implement
RLS within on-premises Analysis Services models outside of Power BI. For Analysis Services live connections,
you configure Row -level security on the on-premises model. The security option will not show up for live
connection datasets.

Define roles and rules in Power BI Desktop

You can define roles and rules within Power BI Desktop. When you publish to Power BI, it also publishes the role
definitions.
To define security roles, follow these steps.
1. Import data into your Power BI Desktop report, or configure a DirectQuery connection.

NOTE
You can't define roles within Power BI Desktop for Analysis Services live connections. You need to do that within
the Analysis Services model.

2. Select the Modeling tab.

3. Select Manage Roles.

4. Select Create.

5. Provide a name for the role.

6. Select the table that you want to apply a DAX rule.
7. Enter the DAX expressions. This expression should return a true or false. For example: [Entity ID ] =
 “Value”.

NOTE
You can use username() within this expression. Be aware that username() has the format of DOMAIN\username
within Power BI Desktop. Within the Power BI service and Power BI Report Server, it's in the format of the user's
User Principal Name (UPN). Alternatively, you can use userprincipalname(), which always returns the user in the
format of their user principal name, [email protected].

8. After you have created the DAX expression, you can select the check above the expression box to validate
the expression.

9. Select Save.
You can't assign users to a role within Power BI Desktop. You assign them in the Power BI service. You can
enable dynamic security within Power BI Desktop by making use of the username() or userprincipalname() DAX
functions and having the proper relationships configured.
By default, row -level security filtering uses single-directional filters, regardless of whether the relationships are
set to single direction or bi-directional. You can manually enable bi-directional cross-filter with row -level security
by selecting the relationship and checking the Apply security filter in both directions checkbox. You should
check this box when implementing dynamic row -level security, wherein you provide row -level security based on
user name or login ID.
For more information, see Bidirectional cross-filtering using DirectQuery in Power BI Desktop and the Securing
the Tabular BI Semantic Model technical article.

Validate the roles within Power BI Desktop

After you've created your roles, test the results of the roles within Power BI Desktop.
1. Select View As Roles.
 In View as roles, you see the roles you've created.

2. Select a role you created > OK to apply that role. The report renders the data relevant for that role.
3. You can also select Other user and supply a given user. It's best to supply the User Principal Name (UPN )
as that's what the Power BI service and Power BI Report Server use.

4. Select OK and the report renders based on what that user can see.
Within Power BI Desktop, Other user only displays different results if you're using dynamic security based on
your DAX expressions.

Manage security on your model

To manage security on your data model, you will want to do the following.
1. Select the ellipse (… ) for a dataset.
2. Select Security.

This will take you to the RLS page for you to add members to a role you created in Power BI Desktop. Only the
owners of the dataset will see Security available. If the dataset is in a Group, only Administrators of the group
will see the security option.
You can only create or modify roles within Power BI Desktop.
Working with members
Add members
You can add a member to the role by typing in the email address, or name, of the user, security group or
distribution list you want to add. This member has to be within your organization. You cannot add Groups
created within Power BI.

You can also see how many members are part of the role by the number in parenthesis next to the role name, or
next to Members.

Remove members
You can remove members by selecting the X next to their name.

Validating the role within the Power BI service

You can validate that the role you defined is working correctly by testing the role.
1. Select the ellipsis (...) next to the role.
2. Select Test data as role

You will then see reports that are available for this role. Dashboards are not presented in this view. In the blue
bar above, you will see what is being applied.
You can test other roles, or combination of roles, by selecting Now viewing as.

You can choose to view data as a specific person, or you can select a combination of available roles to validate
they are working.
To return to normal viewing, select Back to Row-Level Security.

Using the username() or userprincipalname() DAX function

You can take advantage of the DAX functions username() or userprincipalname() within your dataset. You can
use them within expressions in Power BI Desktop. When you publish your model, it will be used within the
Power BI service.
Within Power BI Desktop, username() will return a user in the format of DOMAIN\User and userprincipalname()
will return a user in the format of [email protected].
Within the Power BI service, username() and userprincipalname() will both return the user's User Principal
Name (UPN ). This looks similar to an email address.

Using RLS with app workspaces in Power BI

If you publish your Power BI Desktop report to an app workspace within the Power BI service, the roles will be
applied to read-only members. You will need to indicate that members can only view Power BI content within
the app workspace settings.

WARNING
If you have configured the app workspace so that members have edit permissions, the RLS roles will not be applied to
them. Users will be able to see all of the data.
Limitations
Following is a list of the current limitations for row -level security on cloud models.
If you previously defined roles and rules in the Power BI service, you must re-create them in Power BI
Desktop.
You can define RLS only on the datasets created with Power BI Desktop. If you want to enable RLS for
datasets created with Excel, you must convert your files into Power BI Desktop (PBIX) files first. Learn
more
Only ETL and DirectQuery connections are supported. Live connections to Analysis Services are handled
in the on-premises model.
Cortana is not supported with RLS at this time.

Known issues
There is a known issue where you'll get an error message if you try to publish a previously published report
from Power BI Desktop. The scenario is as follows.
1. Anna has a dataset that is published to the Power BI service and has configured RLS.
2. Anna updates the report in Power BI Desktop and republishes.
3. Anna receives an error.
Workaround: Republish the Power BI Desktop file from the Power BI service until this issue is resolved. You can
do that by selecting Get Data > Files.

FAQ
Question: What if I had previously created roles and rules for a dataset in the Power BI service? Will they still
work if I do nothing?
Answer: No. Visuals will not render properly. You will have to re-create the roles and rules within Power BI
Desktop and then publish to the Power BI service.
Question: Can I create these roles for Analysis Services data sources?
Answer: You can if you imported the data into Power BI Desktop. If you are using a live connection, you will not
be able to configure RLS within the Power BI service. This is defined within the Analysis Services model on-
premises.
Question: Can I use RLS to limit the columns or measures accessible by my users?
Answer: No. If a user has access to a particular row of data, they can see all the columns of data for that row.
Question: Does RLS let me hide detailed data but give access to data summarized in visuals?
Answer: No, you secure individual rows of data but users can always see either the details or the summarized
data.

Next steps
Row -level security (RLS ) with Power BI Desktop
More questions? Try asking the Power BI Community
 Power BI Archived Workspace
1/14/2019 • 2 minutes to read • Edit Online

With Power BI, anyone can sign up and start using the service in a few minutes. Later, your organization's IT
department might choose to take over managing Power BI for users in your organization. If this takeover occurs,
you benefit from central management of users and permissions in your organization. You might also be able to
take advantage of streamlined sign-in using the same username and password you use for other services in your
organization.
Any content you created before your IT department started managing Power BI is be placed in a Power BI
Archived Workspace, which is accessible from the left navigation of Power BI. You should start creating new Power
BI content in My Workspace, which is secured and managed by your organization's IT department. Your Archived
Workspace will continue to exist, but there are restrictions on actions you can perform on content in your Archived
Workspace. To remove these restrictions, you must migrate the content from your Archived Workspace to My
Workspace, managed by your IT department.

Restrictions in your Archived Workspace

Power BI won't delete content from your Archived Workspace. You can continue to get data, create reports and
dashboards, and refresh datasets. Existing users you have shared content with can still view the content in their
Archived Workspace too. However, there are some restrictions on content in your Archived Workspace:
OneDrive for Business: For datasets in your Archived Workspace, you can no longer get or refresh data
from OneDrive for Business. If you try to connect to this source, you receive a warning.
Sharing dashboards: You can't share dashboards with other users from your Archived Workspace. Any
users that already have access can continue to view shared dashboards by accessing their Archived
Workspace.
Creating groups: You can't create groups in your Archived Workspace.
Access on Power BI mobile apps: While you can still view content on the web in your Archived
Workspace, this content no longer appears in the Power BI mobile apps.

Migrating Content in your Archived Workspace

To continue using Power BI, you should create new content in My Workspace. You should also plan to migrate any
content in your Archived Workspace to My Workspace. How you migrate content depends on the kind of content:
Excel or Power BI Desktop datasets: Migrate these datasets by switching from your Archived Workspace
to My Workspace and re-uploading the Excel or Power BI Desktop file by selecting the My Data button. If
you set up scheduled refresh, you must reconfigure those settings for the new dataset in My Workspace.
Other Datasets: Switch to My Workspace and then select the Get Data button to reconnect to any other
datasets you created in your Archived Workspace. You may need to re-enter security or connection
information.
Reports: Reports contained in Excel or Power BI Desktop files are automatically recreated once you re-
upload the corresponding Excel or Power BI Desktop file. Reports installed as part of a content pack are also
recreated when you reconnect to the content pack. If you created your own reports through the Power BI
service, recreate those reports in My Workspace.
Dashboards: Dashboards installed as part of content packs are automatically recreated when you
 reconnect to the content pack in My Workspace. If you created your own dashboards through the Power BI
service, recreate those dashboards in My Workspace.
More questions? Try asking the Power BI Community
 Configure mobile apps with Microsoft Intune
1/14/2019 • 6 minutes to read • Edit Online

Microsoft Intune enables organizations to manage devices and applications. The Power BI mobile applications for
iOS and Android integrate with Intune. This integration enables you to manage the application on your devices,
and to control security. Through configuration policies, you can control items like requiring an access pin, how data
is handled by the application, and even encrypting application data when the app is not in use.

General mobile device management configuration

This article assumes that Intune is configured properly and you have devices enrolled with Intune. The article is not
meant as a full configuration guide for Microsoft Intune. For more information on Intune, see What is Intune?.
Microsoft Intune can co-exist with Mobile Device Management (MDM ) within Office 365. If you're using MDM, the
device will show enrolled within MDM, but is available to manage within Intune.

NOTE
After you configure Intune, background data refresh is turned off for the Power BI mobile app on your iOS or Android device.
Power BI refreshes the data from the Power BI service on the web when you enter the app.

Step 1: Get the URL for the application

Before we create the application within Intune, we need to get the URLs for the apps. For iOS, we will get this from
iTunes. For Android, you can get it from the Power BI mobile page.
Save the URL, as you will need it when we create the application.
Get iOS URL
To get the app URL for iOS, we will need to get it from iTunes.
1. Open iTunes.
2. Search for Power BI.
3. You should see Microsoft Power BI listed under iPhone Apps and iPad Apps. You can use either, as you
will get the same URL.
4. Select the Get drop down and select Copy Link.
It should look similar to the following: https://itunes.apple.com/us/app/microsoft-power-bi/id929738808?mt=8.
Get Android URL
You can get the URL to Google Play from the Power BI mobile page. Select Download from Google Play to take
you to the app page. You can copy the URL from the browser address bar. It should look similar to the following:
https://play.google.com/store/apps/details?id=com.microsoft.powerbim.

Step 2: Create a mobile application management policy

The mobile application management policy allows you to enforce items like an access pin. You can create one
within the Intune portal.
You can create the application, or the policy first. The order in which they are added doesn't matter. They will just
need to both exist for the deploy step.
1. In the Intune portal, select Policy > Configuration Policies.

2. Select Add....
3. Under Software you can select Mobile Application Management for either Android or iOS. To get started
quickly, you can select Create a policy with the recommended settings, or you can create a custom
policy.
4. Edit the policy to configure the restrictions you want on the application.

Step 3: Create the application

The application is a reference, or package, that is saved into Intune for deployment. We will need to create an
application and reference the app URL that we got from either Google Play or iTunes.
You can create the application, or the policy first. The order in which they are added doesn't matter. They will just
need to both exist for the deploy step.
1. Go to the Intune portal and select Apps from the left menu.
2. Select Add App. This will launch the Add Software application.
Create for iOS
1. Select Managed iOS App from the App Store from the drop down.
2. Enter the app URL, that we got from Step 1, and select Next.

3. Provide a Publisher, Name and Description. You can optionally provide an Icon. The Category is for the
Company Portal app. Once you are done, select Next.
4. You can decide if you want the publish the app as Any (default), iPad or iPhone. By default it will show Any
and will work for both device types. The Power BI app is the same URL for both iPhone and iPad. Select
Next.
5. Select Upload.
6. If you don't see the app in the list, refresh the page: Go to Overview then back to Apps.

Create for Android

1. Select External Link from the drop down.
2. Enter the app URL, that we got from Step 1, and select Next.
3. Provide a Publisher, Name and Description. You can optionally provide an Icon. The Category is for the
Company Portal app. Once you are done, select Next.
4. Select Upload.
5. If you don't see the app in the list, refresh the page: Go to Overview then back to Apps.

Step 4: Deploy the application

After you have added the application, you will need to deploy it so that it is available to your end users. This is the
step where you will bind the policy you created with the app.
Deploy for iOS
1. On the apps screen, select the app you created. Then select the Manage Deployment... link.

2. In the Select Groups screen, you can choose which groups you want to deploy this app to. Select Next.
3. In the Deployment Action screen, you can choose how you want to deploy this app. Selecting Available
Install, or Required Install, will make the app available in the Company Portal for users to install on-
demand. After you are done making your selection, select Next.
4. In the Mobile App Management screen, you can select the Mobile App Management policy that we
created in Step 2. It will default to the policy you made, if that is the only iOS policy available. Select Next.

5. In the VPN Profile screen, you can select a policy if you have one for your organization. It defaults to
None. Select Next.
6. In the Mobile App Configuration screen, you can select an App Configuration Policy if you created
one. It defaults to None. This is not required. Select Finish.
After you have deployed the app, it should show Yes for deployed, in the apps page.
Deploy for Android
1. On the apps screen, select the app you created. Then select the Manage Deployment... link.

2. In the Select Groups screen, you can choose which groups you want to deploy this app to. Select Next.
3. In the Deployment Action screen, you can choose how you want to deploy this app. Selecting Available
Install, or Required Install, will make the app available in the Company Portal for users to install on-
demand. After you are done making your selection, select Next.

4. In the Mobile App Management screen, you can select the Mobile App Management policy that we
 created in Step 2. It will default to the policy you made, if that is the only Android policy available. Select
Finish.

After you have deployed the app, it should show Yes for deployed, in the apps page.

Step 5: Install the application on a device

You install the application through the Company Portal app. If you haven't installed the Company Portal, you can
get it through the app store on either iOS or Android platforms. You will sign into the Company Portal with your
organizational login.
1. Open the Company Portal app.
2. If you don't see the Power BI app listed as a featured app, select Company Apps.

3. Select the Power BI app that you deployed.

4. Select Install.
5. If you are on iOS, it will push the app to you. Select Install on the push dialog.

6. After the app is installed, you will see that it is Managed by your company. If you enabled access with a
pin, in the policy, you will see the following.
Next steps
Configure and deploy mobile application management policies in the Microsoft Intune console
Power BI apps for mobile devices
More questions? Try asking the Power BI Community
 PowerShell cmdlets, REST APIs, and .NET SDK for
Power BI administration
1/14/2019 • 2 minutes to read • Edit Online

Power BI enables administrators to script common tasks with PowerShell cmdlets. It also exposes REST APIs and
provides a .NET SDK for developing administrative solutions. This topic shows a list of cmdlets and the
corresponding SDK method and REST API endpoint. For more information, see:
PowerShell download and documentation
REST API documentation
.NET SDK download

Cmdlets below should be called with -Scope Organization to operate against the tenant for administration.

CMDLET NAME ALIASES SDK METHOD REST API ENDPOINT DESCRIPTION

Get- N/A /v1.0/myorg/admin/d

Datasets_GetDataSourcesAsAdmin Gets the data sources
PowerBIDatasource atasets/{datasetkey}/d for a given dataset.
atasources

Get- N/A /v1.0/myorg/admin/d

Datasets_GetDatasetsAsAdmin Gets the full list of
PowerBIDataset atasets datasets in a Power BI
tenant.

Get- Get-PowerBIGroup Groups_GetGroupsAsAdmin/v1.0/myorg/admin/gr Gets the full list of

PowerBIWorkspace oups workspaces in a
Power BI tenant.

Add- Add- Groups_AddUserAsAdmin /v1.0/myorg/admin/gr Adds a user as a

PowerBIWorkspaceUser PowerBIGroupUser oups/{groupId}/users member to a given
workspace.

Remove- Remove- /v1.0/myorg/admin/gr

Groups_DeleteUserAsAdmin Removes a user from
PowerBIWorkspaceUser PowerBIGroupUser oups/{groupId}/users/ the membership list of
{user} a given workspace.

Restore- Restore- /v1.0/myorg/admin/gr

Groups_RestoreDeletedGroupAsAdmin Restores a deleted
PowerBIWorkspace PowerBIGroup oups/{groupId}/restor workspace.
e

Set- Set-PowerBIGroup /v1.0/myorg/admin/gr

Groups_UpdateGroupAsAdmin Updates the
PowerBIWorkspace oups/{groupId} properties of a given
workspace.

Get- N/A /v1.0/myorg/admin/gr

Groups_GetDatasetsAsAdmin Gets the datasets
PowerBIDataset - oups/{group_id}/datas within a given
WorkspaceId
ets workspace.

Get-PowerBIReport N/A /v1.0/myorg/admin/re

Reports_GetReportsAsAdmin Gets the full list of
ports reports in a Power BI
tenant.
CMDLET NAME ALIASES SDK METHOD REST API ENDPOINT DESCRIPTION

Get- N/A /v1.0/myorg/admin/d

Dashboards_GetDashboardsAsAdmin Gets the full list of
PowerBIDashboard ashboards dashboards in a
Power BI tenant.

Get- N/A /v1.0/myorg/admin/gr

Groups_GetDashboardsAsAdmin Gets the dashboards
PowerBIDashboard oups/{group_id}/dash within a given
-WorkspaceId
boards workspace.

Get-PowerBITile Get- /v1.0/myorg/admin/d

Dashboards_GetTilesAsAdmin Gets the tiles of a
PowerBIDashboardTile ashboards/{dashboard given dashboard.
_id}/tiles

Get-PowerBIReport N/A /v1.0/myorg/admin/gr

Groups_GetReportsAsAdmin Gets the reports
oups/{group_id}/repor within a given
ts workspace.

Get-PowerBIImport N/A /v1.0/myorg/admin/i

Imports_GetImportsAsAdmin Gets the full list of
mports imports in a Power BI
tenant.

Connect- Login-PowerBI & N/A N/A Login to Power BI and

PowerBIServiceAccount start a session.
Login-
PowerBIServiceAccount

Disconnect- Logout-PowerBI & N/A N/A Logout of Power BI

PowerBIServiceAccount and close the existing
Logout-
PowerBIServiceAccount session.

Invoke- N/A N/A N/A Send arbitrary REST

PowerBIRestMethod API calls to Power BI.

Get- N/A N/A N/A Obtain the Power BI

PowerBIAccessToken access token in a
session.

Resolve- N/A N/A N/A Get detailed error

PowerBIError information for
unsuccessful cmdlet
calls.
 Power BI URLs for whitelisting
2/13/2019 • 3 minutes to read • Edit Online

The Power BI online service, also known as the Power BI SaaS (Software as a Service) application, requires
connectivity to the internet. The endpoints below should be reachable for customers using the Power BI online
service.
To use the Power BI online service, you must have access to connect to the endpoints marked required in the
tables below, and any endpoints marked required on the linked sites. If the link to an external site refers to a
specific section, you only need to review the endpoints in that section.
Endpoints marked optional may also be whitelisted for specific functionality to work.
The Power BI online service requires only TCP Port 443 to be opened for the listed endpoints.
Wildcards (*) represent all levels under the root domain, and we use N/A when information isn't available. The
Destination(s) column is a list with FQDN/domains and links to external sites, which contain further endpoint
information.

IMPORTANT
The information in the tables below doesn't represent the U.S. Government cloud, the Germany cloud, or the China
cloud.

Authentication
Power BI depends on the required endpoints in the Office 365 authentication and identity sections. To use Power
BI, you must be able to connect to the endpoints in the linked site below.

ROW PURPOSE DESTINATION(S) PORT(S)

1 Required: Authentication See the Office 365 N/A

and identity documentation for Office
Online and common URLs

General site usage

For the general use of Power BI, you must be able to connect to the endpoints in the table and linked sites below.

ROW PURPOSE DESTINATION(S) PORT(S)

1 Required: Backend APIs *.analysis.windows.net TCP 443

2 Required: Office 365 See the Office 365 N/A

integration documentation for Office
Online and common URLs

3 Required: Portal app.powerbi.com TCP 443

4 Required: Service telemetry dc.services.visualstudio.com TCP 443

 ROW PURPOSE DESTINATION(S) PORT(S)

5 Optional: Informational dynmsg.modpim.com TCP 443

messages

6 Optional: NPS surveys nps.onyx.azure.net TCP 443

Administration
To perform administrative functions within Power BI, you must be able to connect to the endpoints in the linked
sites below.

ROW PURPOSE DESTINATION(S) PORT(S)

1 Required: For managing See the Office 365 N/A

users and viewing audit logs documentation for Office
Online and common URLs

Getting data
To get data from specific data sources, such as OneDrive, you must be able to connect to the endpoints in the table
below. Access to additional internet domains and URLs may be required for specific data sources used within your
organization.

ROW PURPOSE DESTINATION(S) PORT(S)

1 Required: AppSource appsource.microsoft.com TCP 443

(internal or external apps in *.s-microsoft.com
Power BI)

2 Optional: Sign in and get Depends on content packs Depends on content packs
data for content packs used used

3 Optional: Import files From See the Required URLs and N/A
OneDrive personal ports for OneDrive site

4 Optional: Power BI in 60- *.doubleclick.net TCP 443

Seconds tutorial video *.ggpht.com
*.google.com
*.googlevideo.com
*.youtube.com
*.ytimg.com
fonts.gstatic.com

5 Optional: PubNub See the PubNub N/A

streaming data sources documentation

Dashboard and report integration

Power BI depends on certain endpoints to be able to support your dashboards and reports. You must be able to
connect to the endpoints in the table and linked sites below.
 ROW PURPOSE DESTINATION(S) PORT(S)

1 Required: Excel integration See the Office 365 N/A

documentation for Office
Online and common URLs

Custom visuals
Power BI depends on certain endpoints to be able to view and access the custom visuals. You must be able to
connect to the endpoints in the table and linked sites below.

ROW PURPOSE DESTINATION(S) PORT(S)

1 Required: Import a custom *.azureedge.net TCP 443

visual from the Marketplace *.blob.core.windows.net
interface or from a file store.office.com

2 Optional: Bing Maps bing.com TCP 443

platform.bing.com
*.virtualearth.net

3 Optional: PowerApps See the Required services N/A

section from the PowerApps
system requirements site

4 Optional: Visio See the Office 365 N/A

documentation for Office
Online and common URLs,
as well as SharePoint Online
and OneDrive for Business

Related external sites

Power BI links to other related sites. These sites include those for documentation, support, new feature requests,
and more. These sites will not affect the functionality of Power BI, so can be optionally whitelisted if desired.

ROW PURPOSE DESTINATION(S) PORT(S)

1 Optional: Community site community.powerbi.com TCP 443

oxcrx34285.i.lithium.com

2 Optional: Documentation docs.microsoft.com TCP 443

site img-prod-cms-rt-microsoft-
com.akamaized.net
statics-uhf-
eas.akamaized.net
cdnssl.clicktale.net
ing-district.clicktale.net

3 Optional: Download site download.microsoft.com TCP 443

(for Power BI Desktop, etc.)
ROW PURPOSE DESTINATION(S) PORT(S)

4 Optional: External redirects aka.ms TCP 443

go.microsoft.com

5 Optional: Ideas feedback ideas.powerbi.com TCP 443

site powerbi.uservoice.com

6 Optional: Power BI site - powerbi.microsoft.com TCP 443

landing page, learn more
links, support site, download
links, partner showcase, etc.

7 Optional: Power BI dev.powerbi.com TCP 443

Developer Center

8 Optional: Support site support.powerbi.com TCP 443

s3.amazonaws.com
*.olark.com
logx.optimizely.com
mscom.demdex.net
tags.tiqcdn.com
 Governance and deployment approaches
2/15/2019 • 2 minutes to read • Edit Online

Over the last few decades, companies have become increasingly aware of the need to leverage data assets to profit
from market opportunities. Either by performing competitive analysis or by understanding operational patterns,
many organizations now understand they can benefit from having a data strategy as a way to stay ahead of their
competition.
The Planning a Power BI Enterprise Deployment whitepaper provides a framework for increasing the return on
investment related to Power BI as companies increasingly seek to become more data-savvy.
Business Intelligence practitioners typically define data-savvy companies as those that benefit from the use of
factual information to support decision making. We even describe certain organizations as having a data culture.
Whether at the organizational level, or at a departmental level, a data culture can positively alter a company’s
ability to adapt and thrive. Data insights don't always have to be at enterprise scope to be far-reaching: small
operational insights that alter day-to-day operations can be transformational as well.
For these companies, there is an understanding that facts – and fact analysis – must drive how business processes
are defined. Team members attempt to seek data, identify patterns, and share findings with others. This approach
can be useful regardless of if the analysis is done over external or internal business factors. It is first and foremost a
perspective, not a process. Read the whitepaper to learn about concepts, options and suggestions for governance
within the Power BI ecosystem.
 Power BI Security
3/25/2019 • 4 minutes to read • Edit Online

For a detailed explanation of Power BI security, read the Power BI Security whitepaper.
The Power BI service is built on Azure, which is Microsoft’s cloud computing infrastructure and platform. The
Power BI service architecture is based on two clusters – the Web Front End (WFE ) cluster and the Back-End
cluster. The WFE cluster manages the initial connection and authentication to the Power BI service, and once
authenticated, the Back-End handles all subsequent user interactions. Power BI uses Azure Active Directory (AAD )
to store and manage user identities, and manages the storage of data and metadata using Azure BLOB and Azure
SQL Database, respectively.

Power BI Architecture
Each Power BI deployment consists of two clusters – a Web Front End (WFE ) cluster, and a Back-End cluster.
The WFE cluster manages the initial connection and authentication process for Power BI, using AAD to
authenticate clients and provide tokens for subsequent client connections to the Power BI service. Power BI also
uses the Azure Traffic Manager (ATM ) to direct user traffic to the nearest datacenter, determined by the DNS
record of the client attempting to connect, for the authentication process and to download static content and files.
Power BI uses the Azure Content Delivery Network (CDN ) to efficiently distribute the necessary static content
and files to users based on geographical locale.

The Back-End cluster is how authenticated clients interact with the Power BI service. The Back-End cluster
manages visualizations, user dashboards, datasets, reports, data storage, data connections, data refresh, and other
aspects of interacting with the Power BI service. The Gateway Role acts as a gateway between user requests and
the Power BI service. Users do not interact directly with any roles other than the Gateway Role. Azure API
Management will eventually handle the Gateway Role.

IMPORTANT
It is imperative to note that only Azure API Management (APIM) and Gateway (GW) roles are accessible through the
public Internet. They provide authentication, authorization, DDoS protection, Throttling, Load Balancing, Routing, and other
capabilities.

Data Storage Security

Power BI uses two primary repositories for storing and managing data: data that is uploaded from users is
typically sent to Azure BLOB storage, and all metadata as well as artifacts for the system itself are stored in Azure
SQL Database.
The dotted line in the Back-End cluster image, above, clarifies the boundary between the only two components
that are accessible by users (left of the dotted line), and roles that are only accessible by the system. When an
authenticated user connects to the Power BI Service, the connection and any request by the client is accepted and
managed by the Gateway Role (eventually to be handled by Azure API Management), which then interacts on
the user’s behalf with the rest of the Power BI Service. For example, when a client attempts to view a dashboard,
the Gateway Role accepts that request then separately sends a request to the Presentation Role to retrieve the
data needed by the browser to render the dashboard.

User Authentication
Power BI uses Azure Active Directory (AAD ) to authenticate users who sign in to the Power BI service, and in turn,
uses the Power BI login credentials whenever a user attempts to access resources that require authentication.
Users sign in to the Power BI service using the email address used to establish their Power BI account; Power BI
uses that login email as the effective username, which is passed to resources whenever a user attempts to connect
to data. The effective username is then mapped to a User Principal Name (UPN and resolved to the associated
Windows domain account, against which authentication is applied.
For organizations that used work emails for Power BI login (such as [email protected]), the effective username
to UPN mapping is straightforward. For organizations that did not use work emails for Power BI login (such as
[email protected]), mapping between AAD and on-premises credentials will require directory
synchronization to work properly.
Platform security for Power BI also includes multi-tenant environment security, networking security, and the ability
to add additional AAD -based security measures.

Data and Service Security

For more information, please visit the Microsoft Trust Center.
As described earlier in this article, a user’s Power BI login is used by on-premises Active Directory servers to map
to a UPN for credentials. However, it’s important to note that users are responsible for the data they share: if a
user connects to data sources using her credentials, then shares a report (or dashboard, or dataset) based on that
data, users with whom the dashboard is shared are not authenticated against the original data source, and will be
granted access to the report.
An exception is connections to SQL Server Analysis Services using the On-premises data gateway;
dashboards are cached in Power BI, but access to underlying reports or datasets initiates authentication for the
user attempting to access the report (or dataset), and access will only be granted if the user has sufficient
credentials to access the data. For more information, see On-premises data gateway deep dive.

Enforcing TLS version usage

Network and IT administrators can enforce the requirement to use current TLS (Transport Layer Security) for any
secured communication on their network. Windows provides support for TLS versions over the Microsoft
Schannel Provider, as described in the TLS Schannel SSP article.
This enforcement can be done by administratively setting registry keys. Enforcement is described in the Managing
SSL Protocols in AD FS article.
Power BI Desktop respects the registry key settings described in those articles, and only created connections
using the version of TLS allowed based on those registry settings, when present.
For more information about setting these registry keys, see the TLS Registry Settings article.