search

liprec / vsts-release-aas

Repository for my Analysis Service Azure pipelines tasks related to Azure Analysis Service or Power BI Premium
Other
27 stars 28 forks source link

AAS deployment Error during detecting agent IP address #71

Closed mmikos closed 2 years ago

mmikos commented 2 years ago

After the update we seem to have a problem with deployment of analysis services database. We're logging in through a named used with a managed account. Everything was working properly before but now we're getting this error:

Error during detecting agent IP address (Exception calling "Connect" with "1" argument(s): "Unable to obtain authentication token using the credentials provided. If your Active Directory tenant administrator has configured Multi-Factor Authentication or if your account is a Microsoft Account, please remove the user name and password from the connection string, and then retry. You should then be prompted to enter your credentials.")

Would you mind looking into this?

We checked that username and password is correct and all the other necessary pipeline variables. Here are the logs: log_pipeline.txt

liprec commented 2 years ago

The new version is using the credentials of the service connection for all Azure activities, including adding and removing the firewall rules. The named user is only used to connect to the AAS instance. Is it possible to configure the SPN of the service connection to add contribute rights to the AAS resource?

mmikos commented 2 years ago

For the service connection we already have configured a service principle with contributor rights to aas.

Patrickva commented 2 years ago

We're experiencing the same issue. If I can provide you with any information regarding the issue please let me know. Our SPN has full security rights on the AAS resource.

liprec commented 2 years ago

Sorry, was misjudging what was causing this, but it is indeed caused on how to the named user is passed to the AAS. I will submit an update anytime soon.

For the easy way forward, you use the inherit option to drop the named user. But for that you have to add the SPN as Analysis Services Admins.

liprec commented 2 years ago

The extension had been updated to version 1.5.3 and will be available anytime soon.

mmikos commented 2 years ago

The bug has been resolved for Tabular Database Deployment, however I'm still getting a similar message for the TMSL script.

liprec commented 2 years ago

Version v1.5.3 of the TMSL task contains the same fix. Probably you are hitting a cached version of the task; my experience is when you rerun the pipeline the latest version of the task will be used.

Patrickva commented 2 years ago

Thanks, for the quick respond. On our side everything is working again.