quinzee.cloud

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.

Administrator’s guide

7. Control resources and infrastructure deployments

A subscription is a local administrative boundary. A resource group owns related resources and gives deletion a concrete scope. A deployment is a recorded attempt to create or update resources. It is not their owner: deleting deployment history does not delete the resources that the deployment created.

Step 1: create a group and set its location

Open Resource Manager → Resource groups, choose the subscription, then Create. Enter a simple name such as admin-training, a supported location and optional string tags. Tags are public metadata, not a secret store. Note the resource ID. Most services require their group to exist before creation. Location is metadata used for compatible resource relationships and endpoints; it does not move data to an Azure region.

Step 2: compile infrastructure as code

Bicep is authoring source. ARM JSON is the deployment document. Compile the provided workshop files on the host:

mkdir -p .local/admin-training
python3 scripts/deps/bicep.py build examples/book-iac/storage.bicep \
  --outfile .local/admin-training/storage.json

In Resource Manager → Deployments, select the subscription and group. Supply a deployment name, compiled template path and optional private parameter-file path. The files are read by QHQ on its own workstation, then submitted over HTTPS. A path inside the cloud container is not automatically a path QHQ can read. Submit and refresh until the operation succeeds or fails; inspect resource operations and outputs rather than assuming that an accepted request is complete.

Deployment controls

Step 3: supply parameters safely

A standard parameter document can contain $schema, contentVersion and a parameters object; each parameter contains a value. The native tutorial client also accepts the bare parameter mapping. Keep secret parameter files mode 0600 and out of source control. Bicep @secure() and ARM secureString / secureObject prevent those values from appearing in deployment history. They do not encrypt an operator's local file.

Ordinary names and tags must not contain secrets. Secure parameters cannot be used as resource names or deployment outputs, including through variables. Provider GET responses still follow each provider's redaction rules. Treat returned connection strings as private even when the platform exposes them through an authorized operation.

Step 4: recover a failed deployment

  1. Identify the first failed resource operation and the actual service error.
  2. Check required modules, group/location, API version and helper health.
  3. Correct the template/input or service prerequisite.
  4. Redeploy incrementally with the same intended resource names.
  5. Inspect application data and outputs after success.

A failed template is not automatically rolled back. Resources completed earlier remain. Active deployments interrupted by cloud restart are marked failed; their secure inputs are not persisted to resume later. Re-submit from your protected source and parameter files. Deleting completed deployment history preserves resources; deleting the group invokes every provider's cleanup and can destroy SQL volumes, queue messages, telemetry and secrets.

Supported deployment settings and fixed limits

Setting Accepted behavior
Scope Resource group only
Mode Incremental only
Template Inline ARM JSON, array-form resources
Inputs string/secureString, object/secureObject, array, int, bool; supported bounds/defaults
Dependencies dependsOn, supported resource references and parent relationships
API versions Provider discovery reports the deployed subset; examples use verified versions
Request/resource limits 1 MiB template request, 128 resources, 16 queued deployments
Retention 256 deployment records, 1,024 operation records

Supported expressions include parameters/variables, resourceGroup/subscription, current-group resourceId, concat/format, case/string transformations, limited condition helpers, and reference to resources in the same deployment. Complete mode, loops, linked/nested templates, symbolic resource maps, resource conditions and arbitrary ARM expressions fail explicitly. Validation checks the deployment language; service-specific errors and missing runtimes can still occur later.