Services

localaz emulates the following Azure services. Each runs on its own port inside the single process. Pick a service for its endpoint, configuration flags, and quick examples with the Go SDK and the Azure CLI.

Configuration overview

Every service is configured through a command-line flag or an environment variable; flags take precedence. The shared data directory flag is -data / LOCALAZ_DATA_DIR (default /data).

Service	Flag	Environment variable	Default
Blob	`-addr`	`LOCALAZ_BLOB_ADDR`	`:10000`
Queue	`-queue-addr`	`LOCALAZ_QUEUE_ADDR`	`:10001`
Table	`-table-addr`	`LOCALAZ_TABLE_ADDR`	`:10002`
Event Grid	`-eventgrid-addr`	`LOCALAZ_EVENTGRID_ADDR`	`:10003`
Web PubSub	`-webpubsub-addr`	`LOCALAZ_WEBPUBSUB_ADDR`	`:10004`
Monitor Logs	`-monitor-addr`	`LOCALAZ_MONITOR_ADDR`	`:10005`
Entra ID (AAD)	`-aad-addr`	`LOCALAZ_AAD_ADDR`	`:10006`
Resource Manager (ARM)	`-arm-addr`	`LOCALAZ_ARM_ADDR`	`:10007`
Service Bus	`-servicebus-addr`	`LOCALAZ_SERVICEBUS_ADDR`	`:5672`

The Blob flag is -addr (not -blob-addr) for compatibility with existing Azurite tooling.

Blob Storage

Block blobs, metadata, ranges, and container/blob listing.

Queue Storage

Messages, visibility timeouts, and pop receipts.

Table Storage

Entities, $filter queries, and ETag concurrency.

Event Grid

Namespace topics with pull delivery.

Web PubSub

REST broadcast plus the json.webpubsub.azure.v1 WebSocket subprotocol.

Service Bus

Queues and topic/subscription fan-out over AMQP 1.0.

Monitor Logs

Logs ingestion plus a documented KQL-subset query.

Control plane (Entra ID + ARM)