You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am deploying a tabular model from one environment to another via VSTS, where I want to modify the data source connection in the <model_name>.asddatabase and the auth credentials (tokens). My data source is Azure Datalake.
When deploying from one environment to another manually and modifying the data source connection so that the model points to the new Datalake, we get a prompt to enter the credentials for that particular datalake data source. Once we authenticate,the credentials of the model for that analysis service gets refreshed as new tokens are generated on oauth.
Question: Is there any way to modify the data source connection of a bim file and authenticating it simultaneously when deploying to a new env
The text was updated successfully, but these errors were encountered:
At this moment the deploy task only supports connections to Azure SQL Databases/Datawarehouse via an username/password combination. I will add this as a feature in a new version.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I am deploying a tabular model from one environment to another via VSTS, where I want to modify the data source connection in the <model_name>.asddatabase and the auth credentials (tokens). My data source is Azure Datalake.
When deploying from one environment to another manually and modifying the data source connection so that the model points to the new Datalake, we get a prompt to enter the credentials for that particular datalake data source. Once we authenticate,the credentials of the model for that analysis service gets refreshed as new tokens are generated on oauth.
Question: Is there any way to modify the data source connection of a bim file and authenticating it simultaneously when deploying to a new env
The text was updated successfully, but these errors were encountered: