Release v1.20.0 removed the Terraform engine for Asset Bundles and added group-level run-as support

The main release news for service principals in October 2026 came on 7 October with v1.20.0. It removed the Terraform deployment engine for Databricks Asset Bundles, so users had to migrate to the direct engine or stay on CLI v1.19.x. The same release added group-level run-as support in bundles and expanded authentication options for Databricks Apps [9].

Two more releases followed on 13 October, v0.166.0 and v0.152.0. Both added OAuth scope configuration for service principal secrets, a filter for deleted bundle deployments, and Slack and Teams destination settings. Both also made a breaking change to AgentKit managed memory entry requests, where the read mask parameter was replaced by a view field [6][7].

The community discussion centered on running pipelines as a group. One post announced that an SDP pipeline could now run as a group [10]. A later thread asked whether running Lakeflow pipelines as a group improved governance or worked around service principal gatekeeping [3]. A related question asked how teams handle, in a bundle-based CI/CD setup, the permissions and access resources that a bundle cannot declare [2].

Other threads covered service principals in specific products. Users reported that service principals created by the Genie App builder were not visible in the Databricks UI [8]. Another thread asked how to manage past conversations that a service principal account started in Genie One [4]. A separate question asked whether personal access tokens, for users or service principals, were accepted by Databricks Apps [5]. A Power BI import gateway strategy thread also mentioned service principals [1].