fix: Complete ABFS auth exclusivity list to match runtime validation

The ABFS connector docs listed only 4 mutually exclusive auth methods
(access_key, bearer_token, client_secret, skip_signature) but the
runtime enforces 8. Add the missing methods: sas_string, client
credentials (client_id + client_secret + tenant_id as a group),
use_cli, msi_endpoint, and federated_token_file.

Applied to vNext and all 7 versioned docs (1.5.x through 1.11.x).

Author: claudespice

website/docs/components/data-connectors/abfs.md

@@ -86,11 +86,15 @@ The dataset name cannot be a [reserved keyword](../../reference/spicepod/keyword
 
 #### Authentication parameters
 
-The following parameters are used when authenticating with Azure. Only one of these parameters can be used at a time:
+The following authentication methods are mutually exclusive — only one can be used at a time:
 
 - `abfs_access_key`
 - `abfs_bearer_token`
-- `abfs_client_secret`
+- `abfs_sas_string`
+- Client credentials (`abfs_client_id` + `abfs_client_secret` + `abfs_tenant_id`)
+- `abfs_use_cli`
+- `abfs_msi_endpoint`
+- `abfs_federated_token_file`
 - `abfs_skip_signature`
 
 If none of these are set the connector will default to using a [managed identity](https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/overview)

website/versioned_docs/version-1.10.x/components/data-connectors/abfs.md

@@ -82,11 +82,15 @@ The dataset name cannot be a [reserved keyword](../../reference/spicepod/keyword
 
 #### Authentication parameters
 
-The following parameters are used when authenticating with Azure. Only one of these parameters can be used at a time:
+The following authentication methods are mutually exclusive — only one can be used at a time:
 
 - `abfs_access_key`
 - `abfs_bearer_token`
-- `abfs_client_secret`
+- `abfs_sas_string`
+- Client credentials (`abfs_client_id` + `abfs_client_secret` + `abfs_tenant_id`)
+- `abfs_use_cli`
+- `abfs_msi_endpoint`
+- `abfs_federated_token_file`
 - `abfs_skip_signature`
 
 If none of these are set the connector will default to using a [managed identity](https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/overview)

website/versioned_docs/version-1.11.x/components/data-connectors/abfs.md

@@ -82,11 +82,15 @@ The dataset name cannot be a [reserved keyword](../../reference/spicepod/keyword
 
 #### Authentication parameters
 
-The following parameters are used when authenticating with Azure. Only one of these parameters can be used at a time:
+The following authentication methods are mutually exclusive — only one can be used at a time:
 
 - `abfs_access_key`
 - `abfs_bearer_token`
-- `abfs_client_secret`
+- `abfs_sas_string`
+- Client credentials (`abfs_client_id` + `abfs_client_secret` + `abfs_tenant_id`)
+- `abfs_use_cli`
+- `abfs_msi_endpoint`
+- `abfs_federated_token_file`
 - `abfs_skip_signature`
 
 If none of these are set the connector will default to using a [managed identity](https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/overview)

website/versioned_docs/version-1.5.x/components/data-connectors/abfs.md

@@ -82,11 +82,15 @@ The dataset name cannot be a [reserved keyword](../../reference/spicepod/keyword
 
 #### Authentication parameters
 
-The following parameters are used when authenticating with Azure. Only one of these parameters can be used at a time:
+The following authentication methods are mutually exclusive — only one can be used at a time:
 
 - `abfs_access_key`
 - `abfs_bearer_token`
-- `abfs_client_secret`
+- `abfs_sas_string`
+- Client credentials (`abfs_client_id` + `abfs_client_secret` + `abfs_tenant_id`)
+- `abfs_use_cli`
+- `abfs_msi_endpoint`
+- `abfs_federated_token_file`
 - `abfs_skip_signature`
 
 If none of these are set the connector will default to using a [managed identity](https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/overview)

website/versioned_docs/version-1.6.x/components/data-connectors/abfs.md

@@ -82,11 +82,15 @@ The dataset name cannot be a [reserved keyword](../../reference/spicepod/keyword
 
 #### Authentication parameters
 
-The following parameters are used when authenticating with Azure. Only one of these parameters can be used at a time:
+The following authentication methods are mutually exclusive — only one can be used at a time:
 
 - `abfs_access_key`
 - `abfs_bearer_token`
-- `abfs_client_secret`
+- `abfs_sas_string`
+- Client credentials (`abfs_client_id` + `abfs_client_secret` + `abfs_tenant_id`)
+- `abfs_use_cli`
+- `abfs_msi_endpoint`
+- `abfs_federated_token_file`
 - `abfs_skip_signature`
 
 If none of these are set the connector will default to using a [managed identity](https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/overview)

website/versioned_docs/version-1.7.x/components/data-connectors/abfs.md

@@ -82,11 +82,15 @@ The dataset name cannot be a [reserved keyword](../../reference/spicepod/keyword
 
 #### Authentication parameters
 
-The following parameters are used when authenticating with Azure. Only one of these parameters can be used at a time:
+The following authentication methods are mutually exclusive — only one can be used at a time:
 
 - `abfs_access_key`
 - `abfs_bearer_token`
-- `abfs_client_secret`
+- `abfs_sas_string`
+- Client credentials (`abfs_client_id` + `abfs_client_secret` + `abfs_tenant_id`)
+- `abfs_use_cli`
+- `abfs_msi_endpoint`
+- `abfs_federated_token_file`
 - `abfs_skip_signature`
 
 If none of these are set the connector will default to using a [managed identity](https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/overview)

website/versioned_docs/version-1.8.x/components/data-connectors/abfs.md

@@ -82,11 +82,15 @@ The dataset name cannot be a [reserved keyword](../../reference/spicepod/keyword
 
 #### Authentication parameters
 
-The following parameters are used when authenticating with Azure. Only one of these parameters can be used at a time:
+The following authentication methods are mutually exclusive — only one can be used at a time:
 
 - `abfs_access_key`
 - `abfs_bearer_token`
-- `abfs_client_secret`
+- `abfs_sas_string`
+- Client credentials (`abfs_client_id` + `abfs_client_secret` + `abfs_tenant_id`)
+- `abfs_use_cli`
+- `abfs_msi_endpoint`
+- `abfs_federated_token_file`
 - `abfs_skip_signature`
 
 If none of these are set the connector will default to using a [managed identity](https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/overview)

website/versioned_docs/version-1.9.x/components/data-connectors/abfs.md

@@ -82,11 +82,15 @@ The dataset name cannot be a [reserved keyword](../../reference/spicepod/keyword
 
 #### Authentication parameters
 
-The following parameters are used when authenticating with Azure. Only one of these parameters can be used at a time:
+The following authentication methods are mutually exclusive — only one can be used at a time:
 
 - `abfs_access_key`
 - `abfs_bearer_token`
-- `abfs_client_secret`
+- `abfs_sas_string`
+- Client credentials (`abfs_client_id` + `abfs_client_secret` + `abfs_tenant_id`)
+- `abfs_use_cli`
+- `abfs_msi_endpoint`
+- `abfs_federated_token_file`
 - `abfs_skip_signature`
 
 If none of these are set the connector will default to using a [managed identity](https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/overview)