Your first request
Make a first Azure request to the emulator: fetch its certificate, check its health, then list its subscription through Azure Resource Manager. It creates nothing, so there’s nothing to clean up. The steps were checked against Vera 1.2.2 on 8 November 2026.
Before you start
Section titled “Before you start”- A running emulator. Start it as in Get started. Listing subscriptions is on the Free plan, so no license key is needed.
- curl. Any recent version; the steps run in bash or zsh.
- No Azure account. The request uses a dummy local token.
Fetch the emulator’s certificate
Section titled “Fetch the emulator’s certificate”The emulator serves Azure over HTTPS with a certificate it generates. Fetch it from your own emulator, then check the emulator’s health with it:
export VERA_CA_CERT="$PWD/vera-ca.pem"curl --fail --silent --show-error --noproxy '*' --insecure \https://localhost:8543/_vera/ca.pem --output "$VERA_CA_CERT"curl --fail --silent --show-error --noproxy '*' \--cacert "$VERA_CA_CERT" https://localhost:8543/_vera/health{ "cloud": "azure", "generation_status": "generated", "status": "ok" }--insecure is only for this download from your own machine; every later request checks the certificate with --cacert.
List the subscription
Section titled “List the subscription”Set the endpoint and the dummy token, then ask Azure Resource Manager for the subscriptions you can see:
export AZ_BASE='https://localhost:8543'export TOKEN='vera-local'curl --fail --silent --show-error --noproxy '*' \--cacert "$VERA_CA_CERT" -H "Authorization: Bearer $TOKEN" \"$AZ_BASE/subscriptions?api-version=2022-12-01"The response lists the emulator’s one subscription. These are its selected fields:
{ "value": [ { "subscriptionId": "00000000-0000-0000-0000-000000000001", "state": "Enabled", "tenantId": "00000000-0000-0000-0000-0000000000a1" } ]}vera-local is a dummy credential, not your license key. Without it, the request answers 401 AuthenticationFailed; without the api-version, 400 MissingApiVersionParameter.
Next steps
Section titled “Next steps”- Resource Manager basics: create a resource group, tag it and lock it.
- Storage: create a storage account, upload a blob and read the same bytes back.
- Using the emulator: the certificate, API versions, data host names, the request helpers, and the Azure CLI and Python SDK.