Andrew Nester

Thanks for the detailed description, I will pass it on to the team owning this functionality and will update this ticket with any new information. In the meantime relying on...

I believe supporting Volumes should be done for `sync` command, @pietern what do you think?

@denik is it reproducible still? There was a fix related to this but for all resources https://github.com/databricks/cli/issues/1685

Databricks CLI depends on Databricks Go SDK which recently added support for OIDC, see this: https://github.com/databricks/databricks-sdk-go/pull/965/files#diff-fe44f09c4d5977b5f5eaea29170b6a0748819c9d02271746a20d81a5f3efca17 The configuration you need to provide though is `ACTIONS_ID_TOKEN_REQUEST_URL ` and `ACTIONS_ID_TOKEN_REQUEST_TOKEN ` Please...

Ah, indeed, I see. In this case, Go SDK we rely on for authentication is not yet supporting OIDC for Azure pipelines. I'm moving this issue to Go SDK as...

Also it seems to be related to this feature request https://github.com/databricks/databricks-sdk-go/issues/495

@Pim-Mostert what is surprising is that CLI commands work for you, could you try to run this command with --log-level TRACE flag and provide an output? ``` databricks experiments list-experiments...

Ah, I see, CLI auth works because it eventually configures to use `azure-cli` auth type and not OIDC one so it might be not what you expect anyway. So to...

All integration test passed

First, could you try to upgrade to the latest CLI version and try it again. Secondly, when you deploy from CI, do you deploy to the same workspace.root_path or the...