Prerequisites and Wizard Deployment

1. Create a dedicated Azure subscription

• Open Azure Subscriptions and create a customer-owned subscription just for RapidClaw. Name it something clear, such as RapidClaw Production or RapidClaw Pilot.
• Confirm the subscription is active and you can create Azure resources and an application registration. Ask your Azure administrator for help if needed.
• The person who runs Setup becomes the first Command Center administrator.
• Set a subscription budget alert. Have a monthly budget and notification email ready for Setup. Alerts notify you; they do not stop spending.

2. Choose a supported region

• Australia East
• East US 2
• South India
• Sweden Central
• West US 3

Use the same subscription and region for the checks and requests below. Setup verifies live availability of the VM, networking, models, and embeddings before deployment.

3. Register resource providers

Register Microsoft.Compute first so Setup can read VM quota. Registration requires subscription-level /register/action permission, included in Contributor and Owner. You still need the deployment permissions listed in step 1.

Azure Portal: Open your subscription > Settings > Resource providers. Register missing providers from the table below; skip those already registered.

CLI alternative: In Azure Cloud Shell or a signed-in Azure CLI session, replace <subscription-id> with your RapidClaw subscription ID:

az provider register --namespace Microsoft.Compute --subscription <subscription-id>
az provider show --namespace Microsoft.Compute --subscription <subscription-id> --query registrationState --output tsv

Repeat for other missing providers, replacing Microsoft.Compute with each namespace. Wait for Registered before continuing. Registration enables a service; it does not create runtime resources or guarantee quota. It can add a Microsoft-managed application to your tenant. Microsoft's registration guidance.

4. Check VM-family quota

RapidClaw uses one Standard_D2as_v6 VM. Your region needs at least 2 available vCPUs in both Standard DASv6 Family vCPUs and Total Regional vCPUs.

1. Open your Azure subscription > Usage + quotas.
2. Filter by Compute and your chosen region.
3. For both quota entries, confirm limit - current usage is at least 2.
4. If either is short, request an increase or check another supported region.

Missing quota entries? Check Microsoft.Compute registration, your subscription and region filters, and your access. Sufficient quota does not guarantee VM capacity. Microsoft's vCPU quota guidance.

5. Request Microsoft Foundry quota

You do not need to create a Foundry project or Azure AI resource first; RapidClaw creates its own during deployment. Model quota is separate from VM quota.

Open Microsoft quota request form.

1. Fields 1-8: enter your name, company email, company name, and address.
2. Field 9 (Subscription Id): enter your dedicated RapidClaw subscription ID, not your tenant ID.
3. Field 10 (Justification): adapt the suggested text below to your deployment and expected usage.
4. Fields 11-16: use the table below. If Microsoft changes the numbering, match the field names.

Recommended form selections

If Setup reports missing embedding quota, submit a separate request for text-embedding-3-small: 10 kTPM in the same subscription and region, using the deployment type Setup requires. For either request, include quota already allocated to other workloads so enough remains for RapidClaw.

Submit the request and wait for Microsoft's response. If offered another region or model, confirm RapidClaw supports it before accepting. After approval, rerun Setup's prerequisite check in the same subscription and region.

Quota is a rate limit, not prepaid usage or a spending cap. Azure charges for tokens used. Microsoft's quota guidance.

6. Run Setup

Once all prerequisite checks pass, deployment normally takes about 20 minutes. Setup runs on the server and can recover progress if you refresh or sign in again.

1. Connect: Sign in, create or recover the application registration, validate your entitlement, and select the subscription.
2. Deploy: Select the region, pass the prerequisite checks, set the budget and alert email, and provision Azure resources.
3. OpenClaw: Install the verified extended-stable runtime and RapidClaw services.
4. Agents: Install agents, skills, schedules, policies, and your product extension.
5. Teams: Publish the tenant-specific Teams package and verify its connection.
6. Command Center: Check runtime health and open the administrator experience.

What is deployed

After deployment

• Check runtime, models, connectors, Teams, subscription, memory, usage, and health in Command Center.
• Review agents, skills, policies, and product-specific Agent Packs. Leave schedules disabled until their scope, tools, delivery, and approvals are understood.
• Monitor spending through Azure cost alerts and Command Center Usage & Costs.

Troubleshooting the Deploy step

VM-family quota message

"Standard_D2as_v6 is not available with sufficient family core quota in <region>."

1. Check Microsoft.Compute is Registered in the subscription selected in Setup. An unregistered provider can cause this message.
2. Check both VM-family and total regional quotas have at least 2 vCPUs available. Request an increase if needed.
3. If both quotas are sufficient, check VM-size availability and the detailed Azure error.

Microsoft.Compute is not registered

Register Microsoft.Compute in the subscription shown by Setup, wait for Registered, and retry. Then resolve any separate quota or capacity errors.

VM size is not available in the region

Choose another supported region where the VM, quota, models, and embeddings are available. To keep your original region, follow Microsoft's SKU-availability guidance. A quota increase alone does not resolve unavailable VM capacity.