Cannot Authenticate with CLI

I am trying to use the SQL Server adapter with the CLI authentication. My config is the following :

dbt version: 0.18.1
dbt-mssql version: 0.18.1
python version: 3.7.4
os info: Windows-10-10.0.19041-SP0

Here is my profiles.yml

my_profile:
  target: dev
  outputs:
    dev:
      type: sqlserver
      driver: 'ODBC Driver 17 for SQL Server'
      server: ip_of_my_server
      port: port_of_my_server
      database: db_of_my_server_that_is_not_master
      schema: my_schema
      authentication: CLI

I run az login sucessfully

You have logged in. Now let us find all the subscriptions to which you have access...

But when I run dbt debug I encounter the following error :

Connection:
  database: my_db
  schema: my_schema
  port: 1433
  UID: None
  client_id: None
  authentication: CLI
  encrypt: False
  trust_cert: False
  Connection test: ERROR

dbt was unable to connect to the specified database.
The database returned the following error:

  >Database Error
  ('28000', "[28000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Login failed for user '<token-identified principal>'. (18456) (SQLDriverConnect); [28000] [Microsoft][ODBC Driver 17 for SQL 
Server][SQL Server]Login failed for user '<token-identified principal>'. (18456)")

If I use :

authentication: ActiveDirectoryInteractive
user: [e-mail]

It works but I have to authenticate at every command executed which is not efficient. Do you have any idea of what I could be doing wrong ? Or how we can fix this ?

[EatZeBaby]

I actually just made it work by running az logout and az login. I tried to reproduce the issue but couldn’t. Sorry for the false alert. Hope it might help someone one day !

Thanks a lot for your time and help @swanderz

[dataders]

@EatZeBaby thanksX1000 for the time to write up this issue. I have none of the normally-required follow up questions.

@mikaelene and @NandanHegde15 are the SQL Server Server experts here, but I’ll take a stab at this…

What version of SQL Server do you have? Where is it hosted? How is it connected to Azure?

I’m am by no means an expert, but my understanding is that you can only use the Azure CLI if your SQL Server db is associated with the Azure tenant. The two ways that I think this can be done is either by:

• Using SQL Server Managed Instance – a pseudo-platform-as-a-service Azure offering; or
• Using Active Directory Federation Services (ADFS) to link your Azure Active Directory to an on-premise (“classic”) Active Directory