Azure Key Vault Integration


I apologize if this is the incorrect place to post this or if this is a repeat question. I have been reading the documentation to setup Azure Key Vault as a Credential Store. I have complete the process all the way to the point of actually adding it into Orchestrator. Every time I click add I get a (#2303) error. In the documentation it says to edit the web config file for Orchestrator does this mean that other credential stores aside the from the default one can not be used unless you have an on prem orchestrator server?

1 Like

Hey @Jcircuit13

Nope. You should be able to select the key vault from the settings I believe.


Im not sure where in settings that would be. I only see the following options (in screenshot). When selecting what seems like the only relevant one (Credential Manager) it only allows me to attempt to add the new credential store which results in the 2303 error. Could you elaborate on where the specific setting is?


Under Credential Stores.

I’m not seeing any additional settings under the credential stores tab.

I only have the add credential store option. When filling that out with the correct info from Azure App reg and the key vault I receive the same error.

Invalid Credential Store configuration. Reason: Secure store operation set is not authorized. (#2303)

1 Like

I still feel like the configuration issue, most probably something with the details you pass.

“Key Vault Uri” and Directory ID are copy-pasted directly from Azure’s Key vault overview page.
“client ID” is copy-pasted from the App Registrations overview page in Azure

The “client secret” is stored in a secure location and copy-pasted from there. I know it works as I use it with API requests successfully.

Okay great. You are using community or enterprise cloud ?

Enterprise Cloud Trial

I would reach out to Cloud Support team and update the thread after you have a response for others to learn.

I have not seen that specific error message, but I don’t find it helpful to point to a particular problem.
Perhaps they need to whitelist on their side, and/or you need to whitelist UiPath Cloud in your Azure.