Quinzee Cloud

Service compatibility

A practical map of supported services and their important limits.

Compatibility is explicit

This guide describes the development snapshot reviewed on 16 November 2026. It is not a stable release guarantee. The service matrix on the Product page summarizes supported contracts and major exclusions.

Supported families

  • Identity and resource management: client credentials, browser/device sign-in, managed identities, scoped ARM/Service Bus roles, resource groups and incremental deployments.
  • Storage: block Blob, Queue and Table operations within documented bounds.
  • Application services: Key Vault secrets and App Configuration key/value revisions.
  • Messaging: Event Grid topics and Service Bus queues/topics with defined protocol subsets.
  • Compute: registered Linux .NET isolated Functions with HTTP and Service Bus queue triggers, plus Linux App Service containers with settings, lifecycle and managed identity.
  • Data: real PostgreSQL/MySQL engines and a Redis-compatible Valkey engine.
  • Observability: workspace-backed Application Insights ingestion and a bounded Logs Query subset.
  • Directory: shared users and groups over LDAPS with an optional PostgreSQL/OpenLDAP backend; no LDAP writes, Kerberos or domain join.

Outside the current contract

Cosmos DB, Event Hubs, Azure File Storage, Azure DNS resource-zone APIs, monitoring alerts and diagnostic settings are not supplied services. Local DNS is a routing facility, not an implementation of Azure DNS management APIs.

There is no full Azure permission boundary, autoscaling or regional high availability. QHQ manages Quinzee; it is not an Azure Portal replica.