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.
11. Operate Functions and App Service workloads
A Functions app runs the real Azure Functions host and .NET isolated worker. An App Service web app runs its image's ordinary entrypoint. Both use one Microsoft.Web provider for plans, state, settings, identities and lifecycle, and one separately operated Docker helper. App Service is a distinct module that enables web-app admission and routing through the shared hosting capability.
Step 1: prepare and approve executable images
For an isolated test lab, the provided fixtures can be prepared as follows. The web fixture includes a token-returning identity probe for interoperability tests: never expose that fixture to untrusted users. For a shared installation, approve your own application image and its authentication policy instead.
make functions-example
make app-service-example
python3 infrastructure/functions/register.py \
--image quinzee-functions-example:local \
--registry .local/functions-helper/images.json
python3 infrastructure/functions/register.py \
--image quinzee-app-service-example:local \
--registry .local/functions-helper/images.json
make functions-run
Registration resolves a local image name to an immutable image ID. It authorizes
that executable code. The helper does not pull an arbitrary image named in ARM.
Restart the helper after changing the registry. The registry file is not a
network container registry; it is the private allowlist used by this helper.
register.py accepts exactly --image and --registry as required inputs.
Complete hosting-helper settings
| Option | Meaning |
|---|---|
--data-dir |
Required cloud data root; mailbox stays under functions-runtime for both hosting kinds |
--state-dir |
Required private state outside cloud data; preserve its CA and ownership files |
--registry |
Required approved image-name → immutable image-ID JSON map |
--network |
Required existing Docker network that can reach the cloud and dependent services |
--dns |
Optional DNS server IPv4 for containers |
--identity-endpoint |
HTTPS cloud origin; default https://quinzee.cloud:11443 |
--add-host |
Repeatable administrator name=IPv4 override |
--trust-ca |
Repeatable additional public CA file trusted inside hosted containers |
make functions-run supplies ENGINE_DATA_DIR, ENGINE_NETWORK,
FUNCTIONS_STATE_DIR/FUNCTIONS_REGISTRY and the standard DNS/CA values. For a
custom lab, call the helper directly with the matching origin/network/trust.
Its private state and data root must not overlap. Run it as a non-root Docker
administrator. The cloud and application containers do not receive the Docker
socket.
Step 2: create a plan and app in QHQ
- Create the resource group.
- Open Azure / App Service → App Service plans; enter scope, name, group and location. Create a Linux B1/Basic plan with capacity one.
- Open Web apps, or Functions → Function apps. Enter the same group/location, select the plan and approved image name, and choose desired identity types.
- Create and refresh until provisioning completes and runtime is Running.
- Test the returned hostname from a client with the lab DNS and CA.
Functions native hosts use <app>.functions.quinzee.cloud; web apps use
<app>.appservice.quinzee.cloud. Azure emulation also supports the corresponding
azurewebsites.net route. Functions forwards only /api/...; its host enforces
the function invocation key and blocks administrative paths. Web apps forward
normal paths and must implement their own application authentication. A resource
management token is not automatically an application login session.
Hosting resource and setting values
| Surface | Accepted configuration |
|---|---|
| Plan | kind linux, reserved true, B1/Basic, capacity 1 |
| Site | Immutable kind functionapp,linux,container or app,linux,container; same-group/location plan, httpsOnly true |
| Site config | linuxFxVersion `DOCKER |
| Identity | None, SystemAssigned, UserAssigned or both; at most eight supported user-assigned attachments |
| App setting names | 1–128 letters/digits/underscore; protected runtime prefixes/names rejected |
| App setting values | Strings up to 8,192 bytes, no newline/NUL; at most 64 settings and 32 KiB aggregate |
| Workload lifecycle | Start/Stop/Restart; image/settings changes reconcile a new revision |
In App settings, Load settings fetches private values internally and displays names. Set setting reads/merges/writes so unrelated settings survive. Remove setting deletes the selected name. Two administrators can still race because this API has no ETag merge contract; coordinate concurrent changes.
The helper reserves ASPNETCORE_, DOTNET_, COMPlus_, LD_, FUNCTIONS_, WEBSITE_,
IDENTITY_ and MSI_ families and the exact names AzureWebJobsScriptRoot, AzureWebJobsSecretStorageType,
SSL_CERT_FILE, SSL_CERT_DIR, HOME and PATH (case-insensitive). Do not replace
the helper’s identity endpoint/header or TLS paths.
For Service Bus managed identity, use the supported binding prefix such as
ServiceBusConnection__fullyQualifiedNamespace, __credential=managedidentity
and optional __clientId. Those are application binding settings, not helper
credentials.
Step 3: make identity grants explicit
System-assigned identity belongs to the site and is removed with it. A user-assigned identity is an independent resource. Attaching either grants no resource access by itself. Assign the required Azure resource role or API app role to its principal ID. The helper injects a protected workload endpoint/header and the server checks the site's actual attachments. Ordinary clients cannot claim to be a managed identity merely by supplying its client ID.
QHQ preserves existing user-assigned attachments when adding a selected one. Clearing its attachment checkbox removes all user-assigned attachments; use ARM for precise multi-identity removal. Public inventory includes identity IDs but omits token headers, Function keys and setting values.
Step 4: diagnose readiness and lifecycle
Functions readiness is a verified TLS host-status request using a private
master key. A web app must listen on TLS port 8443 and return 2xx/3xx at /.
The ASP.NET example uses injected Kestrel certificate settings. An arbitrary
HTTP-only image will not pass that contract. Separate name-constrained CAs
protect upstream Functions and App Service connections.
No image means Stopped. Missing helper, unapproved image or failed readiness leaves Updating until failure; the timeout is 180 seconds. Only the current revision's status is accepted. A stale heartbeat stops gateway forwarding. Gateway bodies are bounded at 64 KiB and exchanges at ten seconds; there is no streaming/WebSocket forwarding.
Stop the app and wait for Stopped before stopping the helper when execution must cease. Helper shutdown or module unload alone can leave containers and queue triggers running. App Service unload blocks its gateway but retains containers/state. Unload it before Functions. Delete queues runtime removal; keep the helper running to complete that cleanup. Deleted app names remain reserved by tombstones, so use a fresh name for a new exercise.
Slots, autoscaling, Windows containers, ZIP/Kudu deployment, managed custom TLS, VNet integration and Easy Auth are not implemented. Functions' verified triggers are HTTP and Service Bus queues with .NET 10 isolated; an unrelated binding is not supported simply because an image can contain its package.