[Documentation] Add link to Workload Identity Federation page (#4786)

tanmay-db · web-flow · commit 13533c5b6097 · 2025-06-13T00:50:11.000Z
## Changes
&lt;!-- Summary of your changes that are easy to understand --&gt;
The page contains details on the environment variables people can set to
use WIF.

## Tests
&lt;!-- 
How is this tested? Please see the checklist below and also describe any
other relevant tests
--&gt;
N/A
- [ ] `make test` run locally
- [ ] relevant change in `docs/` folder
- [ ] covered with integration tests in `internal/acceptance`
- [ ] using Go SDK
- [ ] using TF Plugin Framework
diff --git a/NEXT_CHANGELOG.md b/NEXT_CHANGELOG.md
@@ -9,6 +9,7 @@
 ### Bug Fixes
 
 ### Documentation
+ * Added link to Workload Identity Federation page ([#4786](https://github.com/databricks/terraform-provider-databricks/pull/4786)).
 
 * auto `zone_id` can only be used for fleet node types in `databricks_instance_pool` resource ([#4782](https://github.com/databricks/terraform-provider-databricks/pull/4782)).
 * Document `tags` attribute in `databricks_pipeline` resource ([#4783](https://github.com/databricks/terraform-provider-databricks/pull/4783)).
diff --git a/docs/index.md b/docs/index.md
@@ -271,6 +271,10 @@ provider "databricks" {
 }
 ```
 
+### Authenticating with Workload Identity Federation (WIF)
+
+Workload Identity Federation can be used to authenticate Databricks from automated workflows. This is done through the tokens issued by the automation environment. For more details on environment variables regarding the specific environments, please see: https://docs.databricks.com/aws/en/dev-tools/auth/oauth-federation-provider. 
+
 ## Special configurations for Azure
 
 The below Azure authentication options are supported at both the account and workspace levels. The provider works with [Azure CLI authentication](https://docs.microsoft.com/en-us/cli/azure/authenticate-azure-cli?view=azure-cli-latest) to facilitate local development workflows, though for automated scenarios, managed identity or service principal auth is recommended (and specification of `azure_use_msi`, `azure_client_id`, `azure_client_secret` and `azure_tenant_id` parameters).

Original file line number	Diff line number	Diff line change
`@@ -271,6 +271,10 @@ provider "databricks" {`
`271`	`271`	`}`
`272`	`272`	```
`273`	`273`
	`274`	`+### Authenticating with Workload Identity Federation (WIF)`
	`275`	`+`
	`276`	`+Workload Identity Federation can be used to authenticate Databricks from automated workflows. This is done through the tokens issued by the automation environment. For more details on environment variables regarding the specific environments, please see: https://docs.databricks.com/aws/en/dev-tools/auth/oauth-federation-provider.`
	`277`	`+`
`274`	`278`	`## Special configurations for Azure`
`275`	`279`
`276`	`280`	The below Azure authentication options are supported at both the account and workspace levels. The provider works with [Azure CLI authentication](https://docs.microsoft.com/en-us/cli/azure/authenticate-azure-cli?view=azure-cli-latest) to facilitate local development workflows, though for automated scenarios, managed identity or service principal auth is recommended (and specification of `azure_use_msi`, `azure_client_id`, `azure_client_secret` and `azure_tenant_id` parameters).