This document discusses Azure Key Vault, which allows centralizing application secrets and securing storage of keys and secrets. It can simplify administration by centralizing configurations and allowing monitoring of access and usage. The document demonstrates how to create an Azure Key Vault and connect to it from Visual Studio using managed identities. It also discusses how Azure Key Vault can integrate with app settings and be called externally with a token.

1. AZURE
KEY VAULT
Malin De Silva
MVP – Microsoft Azure
Azure and Office 365 Solutions Consultant

2. Challenges with configurations
Team
Development
QA Testing
User
Acceptance
Testing
Production
◦ Changes when moving through
environments
◦ Configurations shared with multiple
people
◦ Mostly stored in plain text
◦ No way to monitor the usage

3. What is Azure Key Vault?
◦ Centralize Application Secrets
◦ Securing Storage of Keys and Secrets
◦ Monitor Access and Use
◦ Simplified Administration
◦ Simplified integration
◦ Secrets
Store secured access tokens, passwords and API Keys
◦ Keys
Encryption keys
◦ Certificates
SSL Certificates for Azure services

4. Terminology
◦ HSM - A hardware security module (HSM) is a physical computing device that safeguards and manages
digital keys for strong authentication and provides cryptoprocessing.
◦ EC Keys – Elliptic Curve Cryptography, Based on Algebraic Structure of elliptic curves over a finite field
◦ RSA Keys - Rivest–Shamir–Adleman Generates a public key based on 2 prime numbers. Prime numbers
kept secret. Public key shared for encryption.

5. CREATING AZURE
KEY VAULT
DEMONSTRATION

6. What is Managed Identity?
Azure AD App Registration
Azure Key Vault Azure App Service
Client ID and Client Secret

7. CONNECTING TO
VISUAL STUDIO
DEMONSTRATION

8. Azure Hosted Scenario
Can Integrate with App
Settings
Externally call with token

9. Thank You
Malin De Silva
malindesilva@live.com
MVP – Microsoft Azure
Azure and Office 365 Solutions Consultant