On-behalf-of-user authorization for Databricks Apps became generally available on October 7, 2026

The main announcement of the month was general availability of on-behalf-of-user (OBO) authorization for Databricks Apps on October 7 [24]. It lets an app run actions under the signed-in user's identity. Developers pair API scopes with Unity Catalog and warehouse permissions to limit what an app can reach, and keep app-level and user-level clients separate [24].

Tooling changes followed through the month. Databricks CLI v1.20.0 removed the Terraform deployment engine for Asset Bundles, so users had to move to the direct engine or stay on v1.19.x. It also added expanded authentication options for Databricks Apps [25]. CLI v1.22.0 added the `features` resource type and changed how bundle bind and unbind accept references [11]. SDK releases added a model service securable type for Apps, which lets model serving endpoints be declared as app resources, in the Python SDK [21], the Java SDK [20] and a further SDK release [18]. The Java SDK also added a healthCheck field to AppDeployment [26], and the Terraform provider's resource exporter began covering Apps [29].

Other announcements placed Apps inside larger stacks. Document Intelligence real-time APIs can be embedded in Apps [15], and Lakeflow Designer listed an Apps integration as an upcoming addition [16]. Lakebase appeared alongside Apps in several pieces: branching databases for coding agents with preview environments deployed on Apps [23], a telecom fraud workbench [10], a manufacturing digital twin [2], and a two-episode video series on building an agentic support co-pilot [17][28]. Databricks Free Edition teaching material also listed Apps among the tools students use [6].

Community discussion centered on operations. Users asked about idle timeouts [5], auto stop [27], deployment questions [3], quota problems on a new workspace [9], and whether personal access tokens are accepted by Apps [19]. Others shared finished projects [1][7][8] and compared Apps with Model Serving on authentication, cost and performance [13].