The MuleSoft Azure Key Vault Connector connection fails with "AADSTS900382: Confidential Client is not supported in Cross Cloud request" because the connection authorization request is going to Azure Commerce cloud instead of Gov cloud.
Caused by: com.mulesoft.connector.lib.keyvault.error.AuthenticationException: com.microsoft.aad.msal4j.MsalServiceException: AADSTS900382: Confidential Client is not supported in Cross Cloud request. Trace ID: e3549bf8-7470-4937-ba22-faa105020300 Correlation ID: b0dce0e2-f609-4263-bd10-b91bcb3f2623 Timestamp: 2023-10-24 00:07:01Z at com.mulesoft.connector.lib.keyvault.client.KeyVaultClientImpl.testConnection(KeyVaultClientImpl.java:132) at com.mulesoft.connector.keyvault.internal.connection.AzureKeyVaultConnection.lambda$testConnection$4(AzureKeyVaultConnection.java:72) at com.mulesoft.connector.keyvault.internal.connection.AzureKeyVaultConnection.execute(AzureKeyVaultConnection.java:38)
In order to resolve the MuleSoft Azure Key Vault Connector connection failure, perform the following:
1) Please make sure to copy and paste as it is from your Azure Vault API endpoint URL into the connector Uri Override field.
Please refer Connection - Connection Type section of the following documentation.
https://docs.mulesoft.com/azure-key-vault-connector/1.1/azure-key-vault-connector-reference
If you configure the "Uri override" field, then the value for the Vault Name field is not considered for the connection configuration. If the key vault is not located on Azure Commercial Cloud, then configure this field.
2) Please configure the following Mule runtime JVM command line system property also
This value is for GovCloud: AZURE_AUTHORITY_HOST="https://login.microsoftonline.us"
Please review:
https://docs.mulesoft.com/mule-runtime/4.5/mule-app-properties-system
Disclaimer: This article involves products and technologies which do not form part of the MuleSoft product set. Technical assistance for such products is limited to this article.
001117461

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.