Create a Microsoft Azure Private Key Vault machine
Table of Contents
Expand all | Collapse all
-
- Activate Next-Generation Trust Security
-
-
- Configure AWS connection
- Configure Azure Key Vault connection
-
- Workload Identity Federation authentication
- Workload Identity Federation - Azure Identity Provider authentication
- Next-Gen Trust Security Generated Key authentication
- User permissions
- Workload Identity Federation authentication
- Next-Gen Trust Security Generated Key authentication
- User permissions
- Supported OIDC claims
-
-
-
-
- Create an F5 BIG-IP LTM machine
- Create a Microsoft Azure Private Key Vault machine
- Create a Microsoft IIS machine
- Create a Microsoft Windows (PowerShell) machine
- Create a Microsoft SQL Server machine
- Create a Common KeyStore machine
- Create a Citrix ADC machine
- Create an Imperva WAF machine
- Create a VMware NSX Advanced Load Balancer (AVI) machine
- Create an A10 Thunder ADC machine
- Create a Cloudflare machine
- Create Kemp Virtual LoadMaster machine
- Create a Palo Alto Panorama machine
-
- Provision to an F5 BIG-IP LTM
- Provision to a Microsoft Azure Private Key Vault
- Provision to Microsoft IIS
- Provision to Microsoft Windows (PowerShell)
- Provision to Microsoft SQL Server
- Provision to a Common KeyStore
- Provision to a Citrix ADC
- Provision to an Imperva WAF
- Provision to VMware NSX Advanced Load Balancer (AVI)
- Provision to an A10 Thunder ADC
- Provision to Cloudflare
- Provision to a Kemp Virtual LoadMaster
- Provision to Palo Alto Panorama
-
-
- 47-Day Validity Readiness TLS Certificates dashboard
- About the Certificate Inventory
- Managing certificate lifecycle settings
- Reissuing certificates in Next-Gen Trust Security
- Downloading certificates, certificate chains, and keystores
- Retiring, recovering, and deleting certificates
- Finding certificates in the certificate inventory
- Importing certificates from a CA using EJBCA
- Notification Center overview
- Domain-based validation for external emails
- Managing user accounts
- Troubleshooting
Create a Microsoft Azure Private Key Vault machine
Creating a machine enables Next-Gen Trust Security to connect directly to an Azure Key Vault so certificates can be provisioned and managed. After creating the machine, you can provision certificates to it.
Before you begin
- Azure Tenant ID
- Azure Client ID
- Azure Client secret
- Key Vault name
- Credentials with sufficient permissions to manage certificates in the target Azure Key Vault
- Enter the Tenant ID.
- Enter the Client ID.
- Enter the Client Secret.Info:
- Tenant ID identifies the Azure Active Directory instance.
- Client ID identifies the application used to access Azure services.
- Client secret is used to authenticate the application.
- Enter the Key Vault Name.Note: Next-Gen Trust Security uses the Key Vault name to construct the Key Vault URL automatically.
- Click Test Access to verify connectivity.
- Click Continue. The Continue button is enabled only after the connection test succeeds.
What's next?
- Complete discovery and provisioning scheduling. See Create a new machine.