Azure Emulators

The Azure emulator family, composed. This repo runs no emulator of its own — no binary, no image, no Go module. It is the neutral place where six independently released emulators are wired together, documented as a family, and tested against each other.

docker compose up            # entra + arm + keyvault
docker compose --profile fabric up   # …adds fabric
docker compose --profile apim up         # …adds apim
docker compose --profile databricks up   # …adds databricks

ARM governs the vault, as it does in Azure: role assignments decide who may read a secret, and no assignment means no access.

Note

No single emulator’s CI can verify the family. entra’s tests prove entra issues correct tokens; ARM’s prove ARM validates some issuer. Neither proves that ARM validates entra’s tokens, nor that the six images boot together in the right order. That cross-cutting proof has to live somewhere neutral — here.

Start here

• Quickstart — the whole family in one command
• The family — who the members are, and why the boundary between them is real
• Release coordination — the BOM, the three consumption channels, and the ordering rule
• The chain test — the one check no single repo can make

The members

Emulator	Docs
entra-emulator	site
arm-emulator	site
azure-keyvault-emulator	site
fabric-emulator	site
azure-apim-emulator	site
databricks-emulator	site