Skip to main content

Notifications

Announcements

No record found.

Power BI Licensing and On-premise Data Gateway

 
Important information to understand Power BI Licensing and to quickly understand how the On-premises Data Gateway can help you and your organization
The key areas about the gateway and provide links to more information. This is a great way to get started with the gateway and be on your way to take your reports, apps and flows to the next level.
 
1. What are Useful links for On-premise Data Gateway?
4. Can I share reports/dashboards for free license?
 
a) A Power BI Pro license is required to distribute content to other users, and for peer-to-peer sharing and collaboration.
b) A Power BI Pro license is required to publish content to Power BI Premium.
c) A Power BI Pro license is required to receive content from other users, unless the user is associated with dedicated capacity in Power BI Premium.
d) Natural language query, Quick Insights, dashboards, and other Power BI features are not available with Power BI Report Server.
e) A Power BI Pro license is required to publish content to Power BI Report Server.
 

https://docs.microsoft.com/en-us/power-bi/service-share-dashboards

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.
 
 
5. What is the On-premises Data Gateway?
I. Pull data from on-premises data sources
The On-Premises Data Gateway allows you to install on a machine within your on-premises environment. It then reaches out to the Power Platform to allow data to be used within the cloud services. This could be for refreshing data or querying data as it is needed. 

II. More than just Power BI!
The On-premises Data Gateway can be used with the entire Power Platform. This includes Power BI, PowerApps and Microsoft Flow. In addition, Azure Analysis Services and Azure Logic Apps can take advantage of the Onpremises data gateway.

III. Enterprise mode
Use a central gateway for multiple reports and datasets. The enterprise mode gateway can be shared by many users. It also allows for DirectQuery and Live connections to Analysis Services. 
IV. Personal mode
If you just need a gateway for yourself, you can use the personal mode of the On-premises data gateway. This allows you to refresh data for reports you are working on without needing to rely on IT to configure it. Just make sure you leave your machine on.

V. Outbound communication
The gateway reaches out to the cloud. The cloud services never reach into your environment. This is done by polling an Azure Service Bus queue for requests and then processing them. No need to open up inbound firewall ports.

VI. Gateway cluster
A gateway acts as part of a cluster with other gateways. This allows a defined gateway and its data sources to be used across many physical gateways. These can be managed by way of the On-premises Data Gateway PowerShell cmdlets.
VII. High availability
The gateway cluster allows for high availability of your gateway. This means if one gateway were to go offline, your gateway operations would still succeed. This allows you not to worry about your refreshes or DirectQuery/Live connection requests.

VIII. Distribute requests across all gateways
The gateway cluster also allows for distribution of requests across all gateways in the cluster. This is off by default, but when you enable this feature, you can spread your request load across multiple gateway resources. This allows for better resource consumption and preventing a single gateway from being overloaded.

IX. Kerberos SSO for DirectQuery
Certain DirectQuery sources, like SQL Server, allow for Kerberos SSO. This means that the user in Power BI will be impersonated on-premises to allow for individual user auditing or advanced functionality like row-level security at the data source. Configuration of Kerberos can be challenging but it can be a powerful option for DirectQuery sources.

X. AD lookup mapping
Using either Kerberos SSO for DirectQuery, or Live connections for Analysis Services, may need you to map the Power BI user to a user in your local active directory. This is another advanced topic and you can use your local Active Directory, in combination with your gateway, to accomplish the mapping needed.

Comments

*This post is locked for comments