Problem embedding Power bi in business central onprem

(0) Share

Report

Posted on by Community Member

I have Business central 16 onprem (docker container). I want to view power Bi reports in BC.

I set up Azure Active directory using this method: https://www.linkedin.com/pulse/setting-up-power-bi-embedded-microsoft-dynamics-nav-2017-olafusi

On BC role center page under power bi dashboard area, when click "Get started with Power Bi", a new window is prompted and when I select Authorize Azure Services.

I get below error and cannot proceed further with power bi. I have trial power bi pro license and also, I’m login with same credential.

I have the same question (0)

All responses (5)

Answers (1)

Verified answer

Renato Fajdiga 1,853 on at

Like (1)

Report

Hi,

I think that your issue may be connected with this issue community.dynamics.com/.../power-bi-does-no-longer-work-in-v15-and-v16-onprem-while-this-used-to-work-with-similar-settings-accounts-in-v14 which Marco described.

Was this reply helpful? Yes No
Suggested answer

Marco Mels on at

Like (0)

Report

Thank you for sharing the posting Renato.

Our developers has been working on it since this week. One of our supporters found out that the refresh the report sometimes does work.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks Renato and Marco for the quick explanation.

Now I have installed docker BC container onprem v14 (docker image "mcr.microsoft.com/businesscentral/onprem:14.8.38658.0-de-ltsc2019")

I have Setup Azure Active Directory and I have valid trial power bi pro license.

You said power bi should works fine for BC v14, but still I have same error.

Do you have any idea what can be the reason for this error?

Was this reply helpful? Yes No
Suggested answer

Mohamad Vajid on at

Like (0)

Report

Hi Yasmeen,

For v14, can you try and click the menu in the system part and see if you can click on Refresh Page first. This will likely enable the other actions in the menu and you can then click on Select Report. This also seems like a bug. Kindly confirm.

Was this reply helpful? Yes No
Suggested answer

Marco Mels on at

Like (0)

Report

Hello,

We identified the problem and we would like to suggest the following workaround.

The application created in Application Registration Portal was single-tenant, but we do require a multi-tenant one.

Admins can fix it:

1) go to portal.azure.com

2) search for App Registrations

3) open the one used by Business Central (find the display ID using the ID in the setup wizard in Business Central)

4) in the Overview blade, set “Supported account types: Multiple organizations

We will see how to resolve the issue as the automatic registration does create a single-tenant one. In the manifest file you will see SignInAudience. This is set to AzureADMyOrg but it should be AzureADMultipleOrgs.

You may have to rename the automatically registered Azure AD application. You will find that one here:

Thanks.

Was this reply helpful? Yes No