Embed Power BI Reports in DotNetNuke (DNN)

Yes, we provide 24*7 support for all and any issues you might face while using the plugin, which includes technical support from our developers. You can get prioritized support based on the Support Plan you have opted. You can check out the different Support Plans from here.

Single Sign-On (SSO) is required for embedding Power BI reports using a Power BI Premium Per User (PPU) license. It allows users to access reports with their existing Microsoft credentials, ensuring seamless and secure access within organizational environments. For embedding Power BI reports for external customers or non-PPU users, SSO is not required.

RLS (Role Level Security) allows you to control the data that each user can see in embedded Power BI reports. The RLS rules are applied based on attributes such as: Email address Domain DNN roles

Use Power BI Embedded (A1, A2, A3, etc.) or Power BI Premium Capacity. There is no need for SSO. Customers do not need a Power BI account; access can be granted either through logging into DNN or via direct links.

Licensing for miniOrange plugins/modules/connectors is application instance-based and linked to the Fully Qualified Domain Name (FQDN) / unique URLs of the application(s). ‘Application implies an instance of software that is hosted and run on a server. E.g. If you have separate apps for different purposes, both of these applications can be accessed with any one type of FQDN shown below: 1. domain1.com and domain2.com OR 2. app1.domain.com and app2.domain.com OR 3. domain.com/app1 and domain.com/app2 OR 4. test.domain.com/app1 and test.domain.com/app2 You’ll be required to have two separate licenses for each application. With pre-production environments (staging, user acceptance testing, and testing), you'll need separate licenses for each.

We do not provide the developer license for our paid plugins and the source code is protected. It is strictly prohibited to make any changes in the code without having written permission from miniOrange. There are hooks provided in the plugin which can be used by the developers to extend the plugin's functionality.

The plugin licenses are subscription based and you have to pay annually.

Yes, we have an instance-based licensing policy. The plugin's licensing is linked to the domain of the DNN instance. Thus, if you have a dev-staging-prod environment, you'll need three licenses (with discounts applicable on pre-production environments). Additionally, If you need to transfer a license to a different domain, you can deactivate it from the current domain and activate it on the new one.