Forum Discussion
Connect to SSAS instance on Azure Domain Joined VM with Azure AD Credentials using Power BI Desktop
Hi everyone,
in our setup we have two VMs running on Azure, a Windows 10 Client and a Windows Server 2019 Datacenter, which are both ONLY Azure Domain Joined with our Azure Active Directory. The goal is to connect to a SSAS Instance on our server using our Azure AD Credentials. The problem is when using our local windows admin credentials we can connect to our SSAS instance, but when using our Azure AD Crendentials the connections cannot be established.
Error Message:
The used Azure AD user is stored as a privileged user in the SSAS database.
Does anyone have any experience with this setup/problem and can help?
Sincerely,
Minh
Anonymous Yes, i found a solution for our case. The fault was in our setup. With the command
dsregcmd /statusyou can look at the state in which your device is.
State of device
Our VM was AzureAdJoined and our server with the SSAS instance was DomainJoined. Confusingly, you could still log in with the azure crendentials on both devices. Now both devices in our setup are DomainJoined with our Azure AD Domain, so the credentials are correctly transmitted and we can log on to our SSAS instance with our Azure AD Credentials.
So our conclusion is that both devices have to be either AzureAdJoined or DomainJoined.
4 Replies
- daxCommunity Support
Hi minh
According to your image, it seems that your server name is incorrect, please make sure your server name is correct. You could refer to connecting-power-bi-to-an-azure-analysis-services-server for details.
Best Regards,
Zoe ZhiIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- AnonymousNot applicable
minh - Were you able to find a solution?
- minhFrequent Visitor
Anonymous Yes, i found a solution for our case. The fault was in our setup. With the command
dsregcmd /statusyou can look at the state in which your device is.
State of device
Our VM was AzureAdJoined and our server with the SSAS instance was DomainJoined. Confusingly, you could still log in with the azure crendentials on both devices. Now both devices in our setup are DomainJoined with our Azure AD Domain, so the credentials are correctly transmitted and we can log on to our SSAS instance with our Azure AD Credentials.
So our conclusion is that both devices have to be either AzureAdJoined or DomainJoined.