Power BI Embedded

(0) Share

Report

Posted on by Tony zhong

897

Dear friends,

Got a question regarding Power BI (internal) embedded, as I haven't got experienced of F&O in Production stage before. The thing is I always worked in DevBox or UAT and to make Power BI embed run from F&O dashboard workspace, I need to tweak a bit of the Web.config.

As well as there is an addition of create Azure Workspace Collection in which actually being deprecated already about 2 years ago (but still working until now)

When talking about Production, the setup of this Web.config, obviously out of my control, if I'm not mistaken ? Can someone share about how to manage all this when we're Go Live / already in Production ? Should we leave it all to Microsoft and we do nothing, or something need to be done first ?

PS: I'm referring to Power BI embed as AX Resources like any other standard out of the box Aggregate measure with Refresh entity store, not PBI integration with PowerBI.com and BYOD stuff.

Thanks in advance,

I have the same question (0)

All responses (10)

Answers (3)

Suggested answer

André Arnaud de Cal... 299,576 Super User 2025 Season 2 on at

Like (0)

Report

RE: Power BI Embedded

Hi Tony,

You are correct that the web.config file in Microsoft managed environments can't be changed. In these environments it should work out of the box: docs.microsoft.com/.../power-bi-embedded-integration

Was this reply helpful? Yes No
Tony zhong 897 on at

Like (0)

Report

RE: Power BI Embedded

Hi Andre,

I'm sorry, just want to find out deeper on this. I've understand the "web.cofig" can't be changed by us, but Microsoft Support will do it for us in Production, can I say that ? I mean all the configuration / maintenance of Production environment will be handled by them, at least this is my understanding.

As my Power BI report is same as other standard Aggregate Measurement, all the PBIX also stored in AOT-Resources, as well as in LCS and it only need to run "Deploy Power BI" for the reports, and about the data population is go through Entity Store Refresh. I cannot see why we must use PowerBI (.com) integration ?

They (Microsoft support) will still need to configure it in order to make the standard Analytics report to run. Reports such as Customer credit & collection, Financial Analyst etc, the connection as we downloaded is set to Localhost - AXDW, I'm just assuming this is when some setup will automatically set to wherever Azure SQL DB they created for our Production, we just can't set it our self. can I say that ?

Thanks,

Was this reply helpful? Yes No
Suggested answer

Jolanta Malkowska on at

Like (1)

Report

RE: Power BI Embedded

Hi Tony,

Power BI Embedded integration in UAT and Production environments is made available by Microsoft during the deployment of the environment. Custom reports are moved via deployable package and that is all you need to do. After the deployable package has been applied, these reports will be deployed automatically the first time the custom report is opened in the analytical workspace you created. Support does not do anything here either, it is all automatic. You open a support request only if there is an issue in any phase of this process.

For Power BI Embedded reports, you do not have to configure PowerBI.com configuration, upload the reports to LCS, and run Deploy Power BI files menu option. These steps are for integration with PowerBI.com service only which is completely independent of the Power BI Embedded integration. Power BI Embedded integration uses different types of Power BI service behind the scenes. Before 10.0.22/PU46 it was using Workspace Collections, as you already know. Starting with 10.0.22/PU46 it uses workspaces in Power BI Embedded capacities of PowerBI.com service. These workspaces are also managed by Microsoft and are configured automatically.

It is recommended that you use the out-of-the-box Power BI reports that you take from the development system for customizations because only those are current. Reports in the Shared asset library might be outdated. Only reports in the development system are 100% up to date. If you enable PowerBI.com integration in an environment too, then the best is to upload the latest versions of PBIX files from the development system to the Asset library of your LCS project and select them when deploying. You can find the reports in the development system by searching for .pbix file extension in the Service volume <drive letter>:\AOSService\PackagesLocalDirectory folder.

I hope this is helpful.

Best regards,

Jolanta

Was this reply helpful? Yes No
Tony zhong 897 on at

Like (0)

Report

RE: Power BI Embedded

Hi Jolanta Malkowska

Thanks for your kind explanation.

I have another thread which I think can make some confusion since it is quite similar, although in this one is more on the configuration. So based on your explanation, it is clear now, only my question, for Power BI Embedded Capacities, what steps do we need to do ? do we need to buy a capacity plan in Azure first in the same tenant ? as you mentioned the service will be run automatically, means no parameters setting in F&O regarding this Azure service, right ?

I just did a quick search about this and run to a newer tech that Microsoft called Power BI Embedded Gen 2, any easy to understand guide to setup this ?

My main objectives is to make sure Power BI report that we have embed through AOT is run from the workspace (without the need to pin from PowerBI.com) just like all the Out-of-the-box Power BI report from F&O package. It is needed also to have it run in our 1Box, for this one, currently we are still using Workspace Collection .

My other thread is this one :

community.dynamics.com/.../power-bi-desktop-new-version-causing-error-deploy

This is already flag as Solved, I may want to create new thread, it is more on the failing Power BI publishing due to the new version of Power BI Desktop.

Thanks.

Was this reply helpful? Yes No
Verified answer

Jolanta Malkowska on at

Like (2)

Report

RE: Power BI Embedded

Hi Tony,

we are working on publishing the updated workaround on Internet, however, in order to unblock you and other customers I am including the additional required steps in this thread.

Please note that this workaround requires minimum Power BI Pro license. If you do not own this type of license, for testing, you may consider signing up for a Power BI trial.

--
Please be aware that this is an enhancement of the existing Power BI Embedded workaround for 1Box environments. It describes the process of enabling workspaces in Power BI Embedded capacities for hosting Power BI Embedded reports in Dynamics 365 FO release 10.0.22/PU46, in which support of the new format of Power BI reports and the latest version of Power BI Desktop was added.

It replaces Step 3) related to Workspace Collections and adds to Step 5) related to web.config modifications in the old workaround documented in this PDF https://1drv.ms/b/s!AtMv0vRATaKsh1YxO6qokvIGNGPt.

1) In Azure portal, create a Power BI Embedded capacity in your own Azure subscription

+ Create a resource > find and select service Power BI Embedded | Create > fill in required data > Review + Create | Create

2) Create an App registration with a secret in Azure Active Directory

Note: The App registration created in this step is the service principal that will be granted access to the PowerBI.com service in one of the next steps.

i. Create an App registration

Azure Active Directory > App registrations | + New registration > fill in the Name > Register

Take note of the Application (client) ID and Directory (tenant) ID.

ii. Create a secret for the registered application

Certificate & secrets | + New client secret > fill in required data > Add

Take note of the Value of the secret created.

3) In PowerBI.com, enable Create workspaces (new workspace experience) and Allow service principals to use Power BI APIs options under Tenant settings

i. Enable Create workspaces (new workspace experience) under Workspace settings (requires Power BI Pro license)

Note: If enabling for the entire organization is not desired for security reasons, consider adding the user allowed to create a workspace to a Security group and enabling this Security group only.

Settings > Admin portal | Tenant settings > Workspace settings section > set to Enabled | Apply

ii. Enable Allow service principals to use Power BI APIs under Developer settings

Note: If enabling for the entire organization is not desired for security reasons, as recommended, consider adding the service principal to a Security group and enabling this Security group only.

Settings > Admin portal | Tenant settings > Developer settings section > set to Enabled | Apply

4) Create a workspace in PowerBI.com in the created Power BI Embedded capacity and grant the registered application access to it

i. Create a workspace in PowerBI.com in the Power BI Embedded capacity

Workspaces | Create a workspace > fill in the Workspace name, select Embedded for the License mode and the Power BI Embedded capacity created earlier in the Select a capacity field > Save

Take note of the Workspace ID of the created workspace by looking in the browser at its URL.

For example, the Workspace ID of the workspace with the URL https://app.powerbi.com/groups/5612ae0d-fe43-48b7-b390-057379896603/list is
5612ae0d-fe43-48b7-b390-057379896603.

ii. Grant the registered application access to the workspace

Access > type the first few letters of the name of the app registration created earlier and select it from the list of the found applications, keep the default Member in the second field > Add | Close

5) Modify the web.config of the environment adding keys and values required for Power BI Embedded integration in Power BI Embedded capacity

<add key="PowerBIEmbedded.IsPowerBIEmbeddedEnabled" value="true" />

<add key="PowerBIEmbedded.IsOnDedicatedCapacity" value="true" />

<add key="PowerBIEmbedded.AuthorityUrl" value="https://login.microsoftonline.com/" />

<add key="PowerBIEmbedded.V2AppAccessKey" value="<Value of the secret from the App registration>" />

<add key="PowerBIEmbedded.DataTenantId" value="<Directory (tenant) ID from the App registration>" />

<add key="PowerBIEmbedded.V2WorkspaceId" value="<Workspace ID from PowerBI.com>" />

<add key="PowerBIEmbedded.ApplicationId" value="<Application (client) ID from the App registration>" />

<add key="PowerBIEmbedded.ResourceUrl" value="https://analysis.windows.net/powerbi/api" />

<add key="PowerBIEmbedded.V2ApiUrl" value="https://api.powerbi.com" />

6) Enable Power BI Embedded integration in Power BI Embedded capacity via flighting by executing insert statement in SQL Server Management Studio against the AXDB database and iisreset

insert into SYSFLIGHTING (FLIGHTNAME, ENABLED, FLIGHTSERVICEID) values ('IsPowerBiEmbeddedCapacityEnabled', 1, 0)

7) Pause the Power BI Embedded capacity in Azure portal if not using

Power BI Embedded > open the capacity created > || Pause

--

I hope this helps.

Best regards,
Jolanta

Was this reply helpful? Yes No
Verified answer

Helmut Wimmer MSFT on at

Like (1)

Report

RE: Power BI Embedded

Hi all!

I have changed my document according Jolantas suggestions and can confirm it works (for versions after 10.0.22/PU46).

You can always download the latest version of my document here: aka.ms/D365FOPBIEmbedded

Best regards,

Helmut

Was this reply helpful? Yes No
Tony zhong 897 on at

Like (0)

Report

RE: Power BI Embedded

Hi both,

On Step 4, create New Workspace, what happened if License Mode : Embedded disabled ?

I also cannot find Map and filled map visuals (described in Step 3 of Helmut's document), after enable the "New workspace experience" and wait for sometimes.

Done step 1 to 3, btw.

Thanks

Was this reply helpful? Yes No
Verified answer

Helmut Wimmer MSFT on at

Like (0)

Report

RE: Power BI Embedded

Hi Tony!

As stated at the beginning of Step 3 it is mandatory that your PowerBI.com user must be in the same Azure AD tenant/directory as the Power BI Embedded resource created in Azure.

If you are using a different user for PowerBI.com (e.g. user@tonypower.onmicrosoft.com) and the user/directory for PowerBI Embedded (e.g. user@tonyazure.onmicrosoft.com), you will not be able to create an Embedded Power BI workspace.

Hope that solves the issue,

Helmut

Was this reply helpful? Yes No
Tony zhong 897 on at

Like (0)

Report

RE: Power BI Embedded

Hi Helmut,

Yep, just realized that, and you're quicker than me :D

Although, it is a curiosity, and it is a question from my Azure admin, is why it is consider as License option and whether it means I need another license ? I have Pro license, btw.

But up to now, it is ok. Solved.

Thanks.

Was this reply helpful? Yes No
Tony zhong 897 on at

Like (0)

Report

RE: Power BI Embedded

Hi both,

The report is showing perfectly!

Really nice to see it is finally works after all this months. Now I need to catch up what I missed with all those Power BI update features which I can't use all this while.

Thank you very much Jolanta and Helmut.

Was this reply helpful? Yes No