What problem does it solve?
Configuring mTLS Proof-of-Possession (PoP) authentication is complex because the setup differs across credential types (certificate, managed identity, federated identity credential) and resources like Azure Key Vault require special headers. This Skill provides the exact configuration patterns and troubleshooting guidance needed to bind access tokens to client certificates correctly.
Core Features & Use Cases
- Three Credential Patterns: Complete configuration for certificate credentials (Key Vault, store, or file), pure managed identity via IMDS v2, and federated identity credentials (FIC) using signed assertions.
- Azure Key Vault Support: Explains the required
x-ms-tokenboundauth extra header for AKV's TLS renegotiation, including sovereign cloud endpoints for China and US Government.
- Troubleshooting Guide: Maps common 401 errors and MSAL exceptions to their root causes and fixes.
- Use Case: You have a daemon app on an Azure VM that must call Azure Key Vault with token-bound authentication. Use this Skill to configure
ProtocolScheme = "MTLS_POP" with a user-assigned managed identity and the required extra header.
Quick Start
Ask the AI to configure an mTLS PoP downstream API call to Azure Key Vault using a user-assigned managed identity in Microsoft.Identity.Web.