We basically use the solution for keys for data encryption at rest and for storing certificates. 

I mainly use the solution for storing secrets and certificates.

My key use for Azure Key Vault is for saving private information like passwords for accessing databases or other services and also for application keys that need to be kept secret. 

I save everything secret in Key Vault, and Key Vault also rotates passwords. I rotate all the keys in the system every week, I think, and I use a product I don't remember the name of. 

Basically, every new project I start has at least one Key Vault attached to it in order to save the secrets. I use at least one Key Vault for every new project.

I mainly use it to store secrets, private keys, security keys, and related items. I utilize Key Vault for encryptions and decryptions for databases. It also helps me with key rotation, autorotation, and provides alerts for any risks or concerns. These are the features I am using.

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

We have been using Azure Key Vault for general activities, such as when we are calling some API or something similar in Azure Data Factory, we store the secret values or API keys for that purpose.

I have mostly used the secrets in Azure Key Vault, which are pretty efficient to store the keys and secret values.

We use the solution to store all our passwords. We have all our important information in one place.

We wanted to tokenize the PCI data stored in the database. We are using Azure Key Vault to store the keys for the data tokenization. We store secret keys and drive encryption keys in Azure Key Vault.

I use the solution in my company to install our digital certificates and deal with our organization's secret information.

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 the solution to secure and store managed sensitive information and cryptographic keys in an application secret.

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

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.

Azure Key Vault is used to store the encrypted keys. It can be used from the application side or the device side.

I use Azure Key Vault to securely store and manage my API keys, passwords, and certificates. It allows me to store them securely and share access without revealing the secrets. Azure Key Vault also automates password rotation every sixty days and offers options for managing keys either by me or by Azure.

I primarily use the solution to secure our DevOps processes and store all the essential secrets for our project's services.

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

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

We use the solution for API keys. We are migrating most of the data, including the application built in react native from the IBM server to Azure. AWS Key Vault stores secret keys and API keys.

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

Users can store all the security credentials in Azure Key Vault, which only authorized users can access.

We use Azure Key Vault to store secrets. 

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 are a financial institution and we are using this product to manage our keys. We are currently trying to roll out a "Bring Your Own Key" solution for Azure and Office 365.

The primary use case is for storing secrets.

Azure Key Vault is used for passwords. Instead of adding the password to everything, you can add them to Azure Key Vault and directly use it whenever required, in whichever place it's needed.

We use Microsoft Azure Key Vault to store encrypted credentials.

Our primary use case for Azure Key Vault is cloud applications that are being developed and deployed on Azure. In addition, we use it to store secrets that are used for on-premises applications.

We were using the solution to store our keys that includes secrets, passwords, and also application properties.

We are using Azure Key Vault for holding secrets, such as certificates and API management. We're using it for integrating and saving secrets for web applications.

We use Microsoft Azure Key Vault to store some secrets and then we use them outside in connectors in the Data Factory.

We use it to store our secrets and passwords for our integrations and applications.

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.

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.

Currently, we're looking at how we're going to use it in our dev environment. We actually have another product that we're using. We're going to test out those keys for maintaining our secrets, however, we first have them in our dev and test environment before we roll it out, as another protection area.

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.

We have an application connecting to the database. So we have implemented an authentication in place wherein without that particular secret value, it won't be authenticated. So that is a use case that I can tell you about Azure Key. We have implemented it for some small identity providers as well. 

I use the solution for saving keys. We use it to manage encryption keys and secrets in our applications.

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 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 this product to manage our keys for storage, as well as the SQL server.

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

The product integrates well with Azure Active Directory to manage identity or secret certificates.