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.
23. Service compatibility and limits
Use this page when an SDK offers an operation that the emulator rejects. Client
libraries generally expose more APIs than the local service implements. The
main tutorial uses the package versions locked in test/backend/packages.lock.json.
Service Bus and Functions have their own locks under tests/compatibility/;
the Functions build also locks the generated binding-extension project.
A newer package can select a different API version; upgrading it is a separate
compatibility check, not a reason to silently change the emulator's API version.
| Area | Supported contract | Important exclusions/limits |
|---|---|---|
| Identity | Client credentials, browser PKCE/device sign-in, managed identities, app roles, shared groups and scoped ARM/Service Bus RBAC; QHQ management forms | Single local tenant; no MFA, federation, full Graph, delegated consent or other data-plane RBAC |
| LDAP / Windows directory | PostgreSQL-backed POSIX and Windows-oriented user/group views, nested group DNs, verified LDAPS bind/search/compare | No LDAP writes, Kerberos, SIDs, domain join or full AD DS schema |
| App Service | Real Linux web containers, B1 plans, settings, lifecycle, managed identity and QHQ editing | TLS 8443 container contract; no Windows hosting, slots, autoscale, Kudu or cloud synchronization |
| ARM | Local subscriptions/groups, provider discovery, inventory, asynchronous operations | No real Azure subscription/billing backend |
| Deployments | Resource-group Incremental mode; inline array-form resources, supported expressions/dependencies/outputs | 1 MiB request, 128 resources, 16 queued deployments; no Complete/nested/linked/loop-based deployment |
| Blob | Block blobs, metadata, ranges, ETags, staged block commit, account-key service SAS | 256 MiB PUT/block requests; 1 GiB committed blob; no leases, snapshots, page/append blobs, account/delegation SAS |
| Queue | Queue/message CRUD, peek, leases, receipt rotation, TTL, metadata | 64 KiB encoded text, 1,024 queues/account and messages/queue, 16 MiB queue file; no Queue SAS |
| Table | Tables, typed entities, ETags, merge/replace/upsert, OData filters, $select, paging, entity group transactions; SharedKey/SharedKeyLite/bearer |
Azure's entity limits; 1,000 tables/account, 4 GiB per emulator; no Table SAS, ACLs or service properties |
| Event Grid | Custom topics (Event Grid schema, CloudEvents 1.0), storage system topics (Blob Created/Deleted), WebHook and StorageQueue subscriptions with filters and retries | No advanced filters, dead-lettering, other destinations, namespaces or MQTT; 10,000 pending deliveries |
| Service Bus | Standard namespaces, queues, topics/subscriptions, SAS/bearer auth, AMQP/TLS and HTTPS, durable locks and settlement | 256 KiB AMQP messages; no sessions, batch sends, transactions, scheduling or WebSockets |
| Functions | Linux B1 plans, registered containers, real .NET 10 isolated HTTP/Service Bus queue triggers, ARM settings and lifecycle | One instance, 64 KiB HTTP bodies, 10-second gateway exchange; no autoscaling, slots, ZIP/Kudu, other workers or triggers |
| Key Vault | Secret versions, attributes, soft delete, recover/purge | 25 KB values, 500 versions/secret; no keys, certificates, backup/restore or policy enforcement |
| App Configuration | Key/label pairs, filters, ETags, locks, revisions; bearer/HMAC auth | 10 KB key plus value, 1,000 revisions; no snapshots, replicas or continuation paging |
| SQL | PostgreSQL 18/MySQL 8.4; databases; native TLS/password connections; start/stop/restart | 128 server records/provider, 64 databases/server; no HA/backup/upgrade/credential rotation |
| Cache | Managed Redis ARM shape with Valkey; encrypted native protocol, default database | No cluster mode, key rotation or Azure SKU performance simulation |
| Workspaces/components | ARM lifecycle, stable IDs, workspace binding, local-auth option, group cleanup | 64 workspaces and 64 components; component workspace binding is immutable |
| Application ingestion | Request/dependency/log/exception/event/metric JSON envelopes; 100% sampling | 1 MiB/256 envelopes, 8 KiB rows; no gzip or sampled envelopes |
| Logs Query | Six App* tables; comparisons, projection, sorting, take/count | 4,096 query characters, 16 stages, 1,000 result rows; no joins, cross-workspace/batch queries or full KQL |
| Monitoring storage | Persistent workspace rows and configured retention | 4,096 rows/workspace can shorten effective retention; no unlimited analytics store |
| ARM Metrics | Requests/dependencies count, failed, duration; bounded aggregations and intervals | Up to 10 names, 30 days, 1,440 buckets; no arbitrary custom metrics or dimension splitting |
| Platform diagnostics | JSON logs, recent requests, bounded metrics, OTLP export and readiness | Native recent history 128; export queue 512; delivery is best effort |
Event Hubs, Cosmos DB, Azure File Storage, Azure DNS resource-zone APIs, monitoring alerts and diagnostic settings are not supplied services. Local DNS resolves emulator names; it does not emulate Azure DNS management APIs. QHQ is a local management client, not an Azure Portal replica.
For every service, test real Azure's authorization and failure/scale behavior separately before deployment. The most useful local workflow is to keep your business logic and client calls unchanged while making the environment and its deliberately limited guarantees explicit.
For messaging walkthroughs, see Service Bus and Functions. Both exercises use the same endpoints, credentials and lifecycle operations explained in the chapters. A passing smoke test covers that workflow; it does not certify every API in the Microsoft service.