What is your primary use case for Microsoft Azure Key Vault?

I use the solution in my company to store secrets and certificates.

The product’s most valuable feature is the ability to store secret information.

We integrate Azure Key Vault to Azure DevOps for configuration automation. It allows selected access to the client IDs. Centralizing these keys ensures developers don't have direct access to sensitive information. Instead, the platform management team or developers can securely retrieve these keys during the pipeline execution.

We use the solution for a lending platform in the BFSI domain. It helps to store secrets.

I only work with Azure Defender for Key Vault because I'm on the security team. So, it's currently used for passwords and secrets.

We use it to secure passwords and conceal various types of information within documents and data.

We use Azure Key Vault to store secrets.

We use the solution to store passwords, some information, and authentication.

We are working with a lot of our clients who use the solution to protect sensitive information and to store it in the key vault within their infrastructure.

We use the solution to authenticate security features for environments. Using it, we can encrypt keys and protect the databases from getting hacked.

We use Azure Key Vault to store all of our applications’ keys and secrets in the Azure platform. The secrets and keys are for our public facing SaaS software which mainly includes websites and APIs.

We use the Azure Key Vault to encrypt and to get our secrets such as passwords and connection strings.

We use the solution to store our keys securely because authentication, encryption, and endpoint keys are significant concerns. Azure Key Vault allows storing confidential and secure information in an encrypted way, protecting our keys from threats or theft. We have over 100 end users spread over geographically diverse areas in the US, Europe, the UK, Asia Pacific, and India. We operate a shared environment where users can store their passwords and keys in the vault and share them within teams.

We use Azure Key Vault to store our keys, which we use for application access and security validations. It stores keys in a secure way, just like a password. We always use the latest version. The solution is deployed on the cloud. It is deployed on the organization level, so about 75 to 100 people are currently using the solution.

We use it for storing secrets for different accounts. If a service account or a storage account or a resource needs access to a resource, and there's a password involved, you would book out a password, and access Key Vault to gain access to the password, and get access to the resource.

We use Microsoft Azure Key Vault to store encrypted credentials.

We will likely use Microsoft Azure Key Vault for secure key management.

I have used the solution on a couple of projects for a client, mainly for storing credentials and secrets, such as API keys and application or username passwords into the vault, as well as certificates. It is used for anything we need to keep safe and secure and not have users access, except via applications that programmatically access Key Vault and retrieve the secrets and connect to other APIs. That way, we don't supply usernames and passwords within application code or to people. We vault them in Key Vault and those secrets can be used within an application without human intervention. Azure Key Vault is a SaaS solution.

The primary use case is for storing secrets.

We primarily use the solution for key management.

We use Microsoft Azure Key Vault for the secret management side of things; that's where all our application secrets are stored.

We use this product to manage our keys for storage, as well as the SQL server.

I am a system architect and this is one of the products that I work with when designing systems for our customers. This key vault allows you to store passwords and secret keys so that you can retrieve them when needed. Each customer will have their own secret password that can be used in a cloud-based scenario to retrieve their login usernames, passwords, and other secrets.

There are currently two people in my team using this solution. I'm an associate consultant.