Microsoft

Azure can host StrongDM nodes and manage secrets. Users can be managed via Entra ID. StrongDM can govern access to Azure and to many Microsoft resource types.

Secrets Management

StrongDM integrates with the Azure Key Vault to allow your nodes to proxy access to resources using secrets that are added and maintained in your cloud-native secrets manager.

Azure Key Vault

Node Management

When configuring gateways or relays to proxy client traffic to resources, the Azure VM Nodes guide can be of use for setup.

Azure VM Nodes

User Management

StrongDM provides an integration for SSO authentication with Entra ID as well as SCIM user provisioning with Entra ID.

SSO With Microsoft Entra IDProvisioning With Microsoft Entra ID

Resources

Additionally, StrongDM offers proxied access to cloud resources using the following resource types.

Cloud Resources

  • Azure Cloud - Proxy access to manage your Azure cloud via the Azure CLI. See the Azure Cloud guide for more details.

Cluster Resources

When setting up Kubernetes, it's advisable to use a Helm chart and the Kubernetes (Pod Identity) resource type. If you're manually setting up a Kubernetes resource in the cloud, you can also use the Azure-specific AKS resource type.

Server Resources

Any of StrongDM's SSH resource types (listed on the Servers page) can be used to set up AWS server instances as resources in StrongDM.

Datasource Resources

Several of StrongDM's datasource resource types can be used to set up resources within Azure, but there are also several bespoke Microsoft resource types:

Last updated

Was this helpful?