Your issues are tied to authentication and network/configuration differences between Unity Catalog and Workspace models in Databricks, specifically when using the FeatureEngineeringClient.

Key Issues

• FeatureEngineeringClient + Unity Catalog: You get "MlflowException: Connection to storageaccountname.blob.core.windows.net timed out." This is a known problem often related to private endpoint configuration and/or lack of correct authentication for artifact access in Azure Storage.​

• FeatureEngineeringClient + workspace models: Works fine.

• MLflow Client + Unity Catalog: Works fine, pointing to authentication/config differences between the two clients.

• model_uri = "runs:/{run_id}/model": Causes "ValueError: default auth: cannot configure default credentials." This indicates the client can't resolve Azure credentials or configuration to access the storage.​

Likely Causes & Solutions

Azure Storage Permissions (Unity Catalog)

• Unity Catalog models/artifacts in Azure use Azure Storage and require both DFS and Blob private endpoints for access, something the FeatureEngineeringClient tries to access directly. If only DFS or only Blob endpoints are configured, you will get timeouts or authorization failures.​

• Check that your storage account has private endpoints for both Blob and DFS, and that these resolve (try nslookup storage_account_name.blob.core.windows.net in a Databricks notebook).​

Authentication & Credentials

• "default auth: cannot configure default credentials" means your current context lacks necessary credentials for ML artifacts. Common fixes:

  • Make sure your .databricks.cfg file is set up with a default profile including a Databricks PAT token, or with service principal authentication.​

  • For cluster mode, verify your managed identity or service principal has permission to access storage and the Unity Catalog.

  • MLflow client uses different auth flows; FeatureEngineeringClient may expect SDK or environment-based unified authentication.

Client Differences

• MLflow may fallback to workspace-centric authentication flows that work for Unity Catalog, whereas FeatureEngineeringClient is stricter or calls Azure APIs directly.

• Check the Databricks docs for unified authentication for clients and ensure your setup matches what's required for Unity Catalog – especially for non-interactive runs.​

Troubleshooting Checklist

• Verify network connectivity and endpoint configuration for both Blob and DFS storage in Azure.

• Confirm you have valid authentication: either Databricks token, service principal, or managed identity in cluster context.

• Check that your .databricks.cfg contains a proper [DEFAULT] profile.

• Make sure your cluster/node has required permissions to Unity Catalog storage.

• If still blocked, try using MLflow client for serving or accessing Unity Catalog models.

You may also need to consult Databricks support or monitor product release notes for FeatureEngineeringClient, as there are ongoing improvements in Azure/Unity Catalog integration.

For detailed credential setup, see Databricks' unified authentication documentation.​

If you need command examples for checking endpoints or configuring .databricks.cfg, specify your environment further and that can be providedovided.