# Microsoft Azure

> DFNS now runs on Microsoft Azure. Deploy the full platform in your own subscription today, with MPC signing and Entra ID identity throughout, or use DFNS-operated Azure regions starting in the United States and Europe. Here is what is available, how it is built and what comes next.

- Author: Arnaud Dezandee (Principal Infrastructure Engineer)
- Published: 2026-11-18
- Category: Product
- Canonical: https://dfns.co/article/microsoft-azure/
- All DFNS articles: https://dfns.co/llms-full.txt

---

DFNS is now available on Microsoft Azure. Institutions that have standardized on Azure can run the full DFNS platform there, under their own identity and network controls. The whole platform is included. Wallets, transaction management, policies, governance and MPC signing.

Two months ago we announced [DFNS on AWS Marketplace](https://www.dfns.co/article/dfns-available-on-aws-marketplace), which made buying the platform as simple as adding a line to an AWS bill. This post is about something different. It is about running DFNS on Azure, for the many banks and financial institutions whose cloud, security tooling and regulatory approvals are built around Microsoft.

## Why Azure

Microsoft has long said that more than 80 percent of the world's largest banks use Azure. Their landing zones, their identity provider, their key management and their supervisory approvals are all tied to it. For those institutions, deploying critical infrastructure on another cloud means a second cloud risk assessment and a second set of controls to operate, even when the software is right.

Digital asset infrastructure raises the stakes further. Supervisors ask where the keys are, who can reach them and which jurisdiction governs them. The simplest answer a bank can give is that the keys sit in its own cloud, in its own region, behind its own identity provider. Azure support makes that answer available to institutions that had no practical way to give it before.

## Two ways to run DFNS on Azure

**In your own subscription.** An institution can deploy the complete DFNS platform inside its own Azure subscription, in the region it chooses. Every key share is generated and held inside the institution's environment, and DFNS has no access to the infrastructure or to the keys. This is available now.

**In DFNS-operated Azure regions.** For institutions that want the platform on Azure without operating it themselves, DFNS is opening its own Azure regions. The first are in the United States and Europe. The United Arab Emirates and Asia-Pacific will follow. Each region keeps data and key material within its geography, so an institution can choose the jurisdiction that matches its regulatory perimeter.

The rest of this post describes the architecture, which is the same in both cases.

## How it is built

The DFNS deployment for Azure installs the platform in four layers:

1. The first layer is the foundation. It creates the virtual network and NAT gateway, an Azure Kubernetes Service cluster spread across availability zones, a private Azure Database for PostgreSQL server, an Azure Key Vault and a container registry.  
2. The second layer is the platform. It installs the service mesh and the ingress gateway that terminates TLS, and it runs HashiCorp Vault for secrets and certificates. Vault unseals automatically through a key held in Azure Key Vault. It stores its data in the private Postgres server, so the database's point-in-time restore is Vault's backup as well.  
3. The third layer is the product. It deploys the DFNS services themselves, the API, the dashboard and everything behind them.  
4. The fourth layer is signing. It deploys the MPC signers, by default five parties with a threshold of three, each running as its own workload inside the cluster.

A few properties of this design are worth describing, because they are what a security team will look for.

* **Entra ID is the only infrastructure identity.** Every component authenticates as its own Microsoft Entra workload identity. Vault logs in to Postgres as itself. Each signer logs in to its own database role as itself. The operators who run a deployment authenticate with Entra tokens that are minted for the run and never written to disk. Local cluster accounts are disabled. There is no database password anywhere in the deployment, so there is none to rotate, leak or forget.  
* **Nothing private touches the public internet.** The Postgres server has no public endpoint and resolves only inside the virtual network. Vault is reachable only from inside the cluster. The Kubernetes API server and the Key Vault firewall accept connections only from authorized IP ranges.  
* **Each signer is isolated from the others.** Every MPC party has its own managed identity, its own database role and its own storage container. One signer cannot read another's data. Certificates are issued by Vault at start-up and replaced automatically well before they expire. The signers' long-lived key material is generated directly inside Vault and never appears in a configuration file or in infrastructure state.  
* **Key shares are backed up at the moment they are created.** Each signer writes an encrypted copy of every key share to its own Azure Blob container when the key is generated. A copy can only be read with the core keys of the signer that wrote it, so the backup is useless to anyone else. The storage is zone-redundant, keeps versions, retains deleted data for thirty days and refuses shared-key access. A documented procedure restores a signer's shares, with a dry run that checks every share before anything is committed and a way to undo the restore from a database snapshot.  
* **The sensitive steps need a person.** Deployment is automated, but it stops at the moments that should never be automated. Initializing Vault and taking custody of its recovery keys. Loading third-party secrets. Registering and provisioning the MPC key store, which requires a registered staff credential and a passkey signature, with no service-account shortcut. These pauses are deliberate. They are the points where custody procedures take over.

## What is honest to say about today's scope

The Azure deployment supports MPC signing today. The signers run as isolated workloads inside the cluster rather than inside attested enclaves, which the confidential computing work described below will add. Key stores backed by hardware security modules, which DFNS supports in other deployments, are not yet part of it. The backup model covers encrypted key shares per signer, and the additional backup tier that allows keys to be rebuilt independently is not yet configured on Azure. Storage immutability locks, available in our AWS deployment, are not yet configured on Azure. Blob Storage supports them through its immutability policies, and they are on the parity list below. An institution that needs any of these on day one should talk to us about timing.

## What comes next

* **Azure Marketplace.** The listing is in progress. When it arrives, institutions will be able to procure DFNS through their Microsoft agreement and count the purchase against their Azure consumption commitments, with no separate vendor onboarding, as AWS customers can today.  
* **More regions.** DFNS-operated Azure regions begin in the United States and Europe, then expand to the United Arab Emirates and Asia-Pacific.  
* **Hardware-backed key stores.** Institutions that require keys in hardware will be able to have them on Azure, without leaving the cloud they have standardized on.  
* **Backup parity.** The remaining backup and immutability options will reach parity with our other deployments, so the same recovery guarantees apply wherever DFNS runs.  
* **Confidential computing.** Azure confidential computing will let signers run in attested, hardware-isolated confidential VM node pools inside the cluster, on AMD SEV-SNP or Intel TDX, so that key material is protected even from the infrastructure it runs on.

## Getting started

DFNS on Azure is available now. The deployment kit, the runbooks and our engineers are part of the onboarding. If your institution runs on Azure and has been waiting for digital asset infrastructure that does too, we would like to hear from you.

* Learn more about onchain core banking: [dfns.co](https://dfns.co/)  
* Explore the platform and documentation: [docs.dfns.co](https://docs.dfns.co/)  
* Read about DFNS on AWS Marketplace: [dfns.co/article/dfns-available-on-aws-marketplace](https://www.dfns.co/article/dfns-available-on-aws-marketplace)  
* Talk to our team about Azure: [sales@dfns.co](mailto:sales@dfns.co)