Hi sandy311,
How are you doing today?, As per my understanding, It sounds like you're really closeโthis issue is happening because when your job runs through Databricks Asset Bundles (DAB) on a job cluster, it doesnโt automatically have access to the PAT token you use in your CI pipeline to authenticate with Azure Artifacts. Even though it works in CI, the environment in DAB is isolated, so youโll need to pass the token securely to your job cluster at runtime. The simplest fix is to store your PAT token as a Databricks secret, and then in your job definition or init script, use that secret to set the environment variable or auth config before installing the package. Since you're using uv for building, make sure it supports pulling credentials from environment variables or a .pypirc file, and set that up using the secret. This way, the job cluster can authenticate properly with Azure Artifacts when it tries to install the private dependency. Let me know if you want a quick example of how to pass the secret into your DAB job!
Regards,
Brahma