Skip to content

Commit

Permalink
backport of commit 5cbb87e (#20671)
Browse files Browse the repository at this point in the history
Co-authored-by: Equus quagga <jan.prinsloo@hashicorp.com>
  • Loading branch information
hc-github-team-secure-vault-core and kwagga authored May 19, 2023
1 parent 6e7da68 commit 6b99ca7
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions website/content/docs/secrets/databases/mssql.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -100,6 +100,10 @@ the proper permission, it can generate credentials.

Here is a complete example using Azure SQL Database. Note that databases in Azure SQL Database are [contained databases](https://docs.microsoft.com/en-us/sql/relational-databases/databases/contained-databases) and that we do not create a login for the user; instead, we associate the password directly with the user itself. Also note that you will need a separate connection and role for each Azure SQL database for which you want to generate dynamic credentials. You can use a single database backend mount for all these databases or use a separate mount for each of them. In this example, we use a custom path for the database backend.

<Note>
Azure SQL databases may use different authentication mechanism that are configured on the SQL server. Vault only supports SQL authentication. Azure AD authentication is not supported.
</Note>

First, we mount a database backend at the azuresql path with `vault secrets enable -path=azuresql database`. Then we configure a connection called "testvault" to connect to a database called "test-vault", using "azuresql" at the beginning of our path:

```shell-session
Expand Down

0 comments on commit 6b99ca7

Please sign in to comment.