Forum Discussion
Azure Analysis services and on prem data gateway
Resident RockstarHi Anonymous ,
I have a little confused about your scenario.
The on-premises gateway you mentioned is the on-premises data gateway in Power BI?
If it is, I'm afraid that if your data source is Azure Analysis services, you don't need to configure the on-premises gateway in Power BI Service.
If you really want to manage the cloud source within gateway, you could select this option under Gateway Cluster Settings when set the gateway, "Allow user's cloud data sources to refresh through this gateway cluster "> Apply.
In addition, if you want to achieve this "I hade hoped that my @onmicrosoft.com account that has also admin rights on azure could be used. ", you'd better have a contact with your global admin in your tenant. You also could get a help from Azure support.
If you still have the problems about Power BI, please feel free to ask.
Best Regards,
Cherry
Hi again. Thanks for spending time on me. I have had some progress. I have succeeded to create an on-prem datagateway on the same server where my database is and connected it to an azure account (still free version).
I created an user on the database which is the service user NT Service\PBIEgwService like
use master;
GO
CREATE LOGIN [NT Service\PBIEgwService] FROM Windows;
GO
use mydb;
CREATE USER [NT Service\PBIEgwService] for login [NT Service\PBIEgwService]
GO
EXEC sp_addrolemember db_datareader, [NT Service\PBIEgwService]
GO
This is fine, I deployed my Visual Studio 2017 Analysis project up to the azure account, where impersonation is set to impersonate service account. I was able to process the AAS in SSMS.
So far so good. But in my customer's environment they already has a on-prem datagateway which is connected to active directory service user domain\serviceuser. This on-prem datagateway is installed on a different machine but inside the same domain of course. I tried to use the same approach, but this time I logged in on azure on the azure account for the customers datagateway account if you understand. Everything seems identical and I have green on connecting azure to onprem datagateway. I now deployed to the new azure analysis services (do not process), that was ok. Then I tried to process and I got the following error:
Failed to save modifications to the server. Error returned: 'An error occurred during On-Premise Gateway related activity. Additional error details: DM_GWPipeline_Gateway_DataSourceAccessError
Received error payload from gateway service with ID 371137: An exception encountered while accessing the target data source.
An exception encountered while accessing the target data source
The specified length exceeds maximum capacity of SecureString.
Parameter name: length
I can't see what is different here and what is causing the error in the second approach. It is two different azure accounts, but that is only for separating the cases here. There are both connecting to the same database, but the first is using the standard local onprem service user and the second is connected through the domain service user (set on the on prem datagateway on the second machine).
Hope you and others understand what I wa trying to tell here. If not let me know and I will try to explain better