Development edition · 16 November 2026. Commands using repository paths, Make targets or sample projects require access to the Quinzee source checkout. No public installer is available. Examples use disposable local environments.
1. Meet Quinzee and its services
Quinzee Cloud is a local environment for applications that use Azure services.
It accepts a supported subset of Azure's APIs, so you can create resources and
use them through ordinary Microsoft client libraries. Your application can use
URLs such as https://management.azure.com and
https://myaccount.blob.core.windows.net inside a prepared development container.
Quinzee's DNS sends those requests to your local emulator; its development
certificates allow the client to verify the connection.
A resource group is a container for related resources. A control-plane call creates or configures a resource, such as a storage account. A data-plane call uses that resource, such as uploading a document. Azure Resource Manager handles the control plane; the individual service clients handle the data plane.
Services you can use
| Service | What you can do locally | Main boundary |
|---|---|---|
| Microsoft Entra ID compatibility | Authenticate applications and local users; obtain service-specific bearer tokens | Client credentials, local browser login and Functions managed identities; bounded ARM/Service Bus roles, no MFA or federation |
| Azure Resource Manager | Work with subscriptions, resource groups, provider discovery and resource inventory | Existing local tenant; no Azure billing or subscription infrastructure |
| ARM deployments and Bicep | Deploy resource-group templates, inspect operations/outputs and redeploy incrementally | Supported expression subset; no Complete mode, nested deployments or resource loops |
| Blob Storage | Containers, block blobs, metadata, ranges, staged uploads and scoped service SAS | No page/append blobs, leases, snapshots or Azure Files |
| Queue Storage | Send, peek, receive, update and delete messages; visibility leases and redelivery | At-least-once delivery; bounded local capacity; no Queue SAS |
| Table Storage | Typed entities, filters, paging, conditional updates and entity group transactions | No Table SAS, ACLs or service properties |
| Event Grid | Custom/storage system topics, filtered WebHook and StorageQueue deliveries with retries | No advanced filters, dead-lettering, namespaces or MQTT |
| Service Bus | Queues, topics/subscriptions, AMQP/TLS and HTTPS messaging, locks and settlement | No sessions, batches, transactions, scheduling or WebSockets |
| Azure App Service | Real Linux web containers, plans, settings, lifecycle and managed identities | TLS 8443 container contract; no slots, autoscale, Windows hosting or cloud synchronization |
| Shared LDAP directory | Read/authenticate the same Entra users and groups over LDAPS | Optional PostgreSQL/OpenLDAP; no LDAP writes, Kerberos or domain join |
| Azure Functions | Real .NET isolated HTTP and Service Bus queue triggers in registered Linux images | Separate Docker helper; single instance, no autoscaling, slots or other workers |
| Key Vault | Versioned secrets, attributes, soft deletion, recovery and purge | Secrets only; no cryptographic keys/certificates or Azure RBAC enforcement |
| App Configuration | Keys, labels, revisions, conditional updates and locking | No snapshots, replicas or full feature-management service |
| PostgreSQL flexible servers | Provision a real PostgreSQL 18 server and databases; start, stop and restart | Local container, password login; no HA, backups or managed-identity database login |
| MySQL flexible servers | Provision a real MySQL 8.4 server and databases; start, stop and restart | Same local lifecycle limits as PostgreSQL |
| Managed Redis-compatible resources | Provision an encrypted cache and connect with a Redis client | Valkey engine, one nonclustered database; no key rotation or Redis cluster simulation |
| Log Analytics | Create workspaces and query ingested application telemetry | Small, explicit KQL subset and bounded retention/storage |
| Application Insights | Create workspace-backed components; ingest request, dependency, log, event, exception and metric envelopes | Supported official exporter configuration; no live metrics, profiler or alerting |
| Local DNS and platform observability | Resolve service names; inspect health, workers, queue depth, logs, metrics and traces | Development/operator facilities, not Azure DNS zones or the Azure Portal |
Quinzee implements these services for application development. Real Azure's permissions, capacity, regional resilience and pricing are not simulated. The bootstrap identity has broad local access. New users and principals need supported scoped ARM/Service Bus permissions; other data planes have explicit limits. Storing an Azure-shaped policy property is not proof of enforcement. Use synthetic development data. Secrets and application data persist locally, and secret values are not encrypted at rest by the emulator.
What runs where
- quinzee.cloud serves ARM and HTTP data-plane APIs over HTTPS, and Service Bus AMQP over a separately enabled TLS listener.
- quinzee.dns resolves supported service names on a private Docker network.
- A separate engine supervisor starts and reconciles PostgreSQL, MySQL and Valkey containers. SQL and Redis clients speak their real native protocols.
- A separate Functions helper runs registered application images with the real Functions host. Its containers execute HTTP and Service Bus triggers.
- quinzee.test is a working .NET/React example application you can inspect in a browser. Separate locked examples exercise Service Bus and Functions in chapters 12–13.
- QHQ is the native management application for resources and diagnostics.
- Optional Grafana, Prometheus, Loki, Tempo and an OpenTelemetry Collector provide dashboards and trace/log exploration.
The sample environment prepares its own DNS, public trust certificates and credentials. It does not alter your host's DNS or trust store.
The supplied application brings the services together. This completed MySQL run includes Blob, Queue, Key Vault, App Configuration, Redis and monitoring checks.
Which Microsoft library?
The service libraries are the Azure SDK for .NET: for example,
Azure.Storage.Blobs, Azure.Security.KeyVault.Secrets and
Azure.Monitor.Query.Logs. They share Azure SDK conventions and accept a
TokenCredential supplied by Azure.Identity.
You may be remembering MSAL, the Microsoft Authentication Library. MSAL is
about authentication; it is not a Blob or Key Vault client. This book uses
ClientSecretCredential from Azure.Identity so that the service libraries
obtain the appropriate tokens for you. It deliberately avoids an interactive
credential chain that might select a real Azure account on your workstation.
A TokenCredential obtains the token requested by a service client. The token's
audience identifies that service; a token requested for Resource Manager cannot
be reused as a directory or messaging token. Use the verified package versions
in the workshop and check the returned HTTP status before assuming a newer SDK
operation is supported.