databricks-migration

Replace all dbutils calls with notebookutils equivalents, convert DBFS paths to OneLake or Lakehouse-relative paths, and collapse Unity Catalog three-level namespaces to two-level Lakehouse schemas. Most fs, secrets, and notebook operations have direct replacements.

Use notebookutils.credentials.getSecret with a Key Vault URL and secret name. Databricks secret scopes map to Azure Key Vault instances, and the notebook identity needs the Key Vault Secrets User role.

No, dbutils.widgets has no direct equivalent in Fabric. Use a parameter-tagged cell in the notebook for pipeline or parent-notebook injection, or notebookutils.variableLibrary for centralized cross-notebook configuration.

Delta Live Tables has no Fabric equivalent and cannot be ported verbatim. Rewrite DLT datasets as parameterized notebook cells orchestrated by Fabric Data Pipelines.

Map single-task jobs to Spark Job Definitions referencing a notebook, and multi-task DAGs to Fabric Data Pipelines orchestrating multiple notebooks or SJDs. Cron schedules become pipeline recurrence triggers.

dbutils is not available in Fabric and raises a NameError if imported or referenced. All calls must be replaced with notebookutils, which is pre-instantiated and covers fs, credentials, notebook, and session operations.