diff --git a/docs/console/company-configuration/providers/api-reference.md b/docs/console/company-configuration/providers/api-reference.md
index 812eff00f3..fda9156e94 100644
--- a/docs/console/company-configuration/providers/api-reference.md
+++ b/docs/console/company-configuration/providers/api-reference.md
@@ -178,14 +178,16 @@ curl --location --request POST 'https://console-url/api/backend/tenants/my-examp
 </details>
 
 :::info Supported credential types
-As discussed [here](/console/company-configuration/providers/configure-provider.mdx#step-3-credentials), different types of providers support different types of credentials. The following table shows the credential types supported by each provider, referring to the data model shown above:
+As discussed [here](/console/company-configuration/providers/configure-provider.mdx#step-3-credentials),
+different types of providers support different types of credentials.
+The following table shows the credential types supported by each provider, referring to the data model shown above:
 
 | Credentials Type   | Providers                                                             |
 | ------------------ |:---------------------------------------------------------------------:|
 | token              | gitlab, github, bitbucket, azure-devops, vault, jenkins               |
 | m2m                | vault                                                                 |
-| client_credentials | jenkins                                                               |
-:::
+| client_credentials | jenkins, azure-devops                                                 |
+
 :::caution Data model update
 The fields `capabilities` and `expirationDate` (within `credentials`) have been introduced starting from version 10.8 of the Console.
 :::
@@ -321,6 +323,7 @@ Examples of request bodies specific to each provider type are shown below. In th
 </Tabs>
 
 ### PATCH
+
 To edit an existing provider, you need to call the respective API as follows:
 
 ```sh
diff --git a/docs/console/company-configuration/providers/configure-provider.mdx b/docs/console/company-configuration/providers/configure-provider.mdx
index 33670ec579..2360282739 100644
--- a/docs/console/company-configuration/providers/configure-provider.mdx
+++ b/docs/console/company-configuration/providers/configure-provider.mdx
@@ -195,11 +195,11 @@ Credentials entered at this stage, for security reasons, will never again be sho
 Depending on the provider selected in step 1, the types of credentials supported will change. The following table shows the credential types supported by each provider:
 
 | Credentials Type               | Providers                                                                |
-| ------------------------------ |:------------------------------------------------------------------------:|
+| ------------------------------ | ------------------------------------------------------------------------ |
 | Token                          | GitLab, GitHub, Bitbucket, Azure DevOps, Vault, Jenkins, Azure Key Vault |
 | M2M                            | Vault                                                                    |
-| Client Credentials             | Azure Key Vault,Jenkins                                                  |
-| Client Credentials Certificate | Azure Key Vault                                                          |
+| Client Credentials             | Azure Key Vault, Jenkins, Azure DevOps                                   |
+| Client Credentials Certificate | Azure Key Vault, Azure DevOps                                            |
 
 :::caution Assign the right scope to your credentials
 Make sure, when generating credentials on the respective provider sites, to assign them a scope so that they have the necessary permissions for all read and write operations performed through the Console.