Provision Infrastructure

Operators moving into the cloud face three unique challenges: addressing infrastructure heterogeneity, managing scale, and enabling self service consumption across organizations. To address these challenges for users adopting Azure, HashiCorp offers a dedicated Terraform provider for the purpose of provisioning and managing Azure cloud-based services. Users can write configurations using infrastructure as code, check them into version control, version them, and run a few commands to test and apply changes to their Azure infrastructure.

Terraform Integrations for Azure:
Terraform Provider
Azure Modules
Terraform Provider for Azure Stack
Setting Up Azure AKS

Additional Resources:
HashiCorp Terraform on Azure
Microsoft Terraform Hub
Expanding the HashiCorp Partnership

Secure Secrets

Vault secures, stores, and tightly controls access to tokens, passwords, certificates, encryption keys for secrets and other sensitive data using a UI, CLI, and HTTP API. For Azure users, Vault offers a dedicated Auth Method for Azure Active Directory, an Azure Secrets Engine, and an Azure Key Vault seal.

Vault Integrations for Azure
Vault Auth Method
Vault Secrets Engine
Vault Cloud Auto-unseal

Additional Resources
HashiCorp Vault speaks Azure Active Directory
How to identify and eliminate secrets sprawl on Azure with HashiCorp Vault

Run Applications

Nomad is a flexible, enterprise-grade cluster scheduler that can run a diverse workload of micro-service, batch, containerized and non-containerized applications. Nomad's lightweight architecture and zero external dependencies minimize operational overhead in any on-prem or public cloud environment. Nomad Enterprise adds collaboration and governance capabilities, allowing organizations to run Nomad in a multi-team setting and meet governance and policy requirements. Users on Azure are able to run Docker-based or legacy, non-containerized workloads on both Linux and Windows using a common workflow.

Connect Applications

Consul is a service mesh offering for discovering, securing, and configuring services across your infrastructure. Consul clusters allow agents to talk across data centers to provide health monitoring, K/V storage, and a variety of other services. To create these clusters, Consul relies on the creation of agents that assume either a server or client role and join an existing cluster upon startup. To help prevent failures in cluster formation, Consul users utilizes the command "retry-join" provisioned for Azure. This instructs agents to join the first private IP of a server with a given tag and key value and authorized via a secret key.

Consul Integrations for Azure:
Auto Retry for Azure
Modern Service Discovery with Consul on Azure: Part 1
Modern Service Discovery with Consul on Azure: Part 2
Building cloud-native applications with Azure and HashiCorp