Prerequisites and Wizard Deployment
Prepare the customer-owned Azure boundary first, then let the shared RapidClaw wizard provision and verify the operating environment.
Before you open Setup
- Create a dedicated, customer-owned Azure subscription for RapidClaw. This keeps runtime resources, quota, access, policy, and billing separate from unrelated workloads.
- Confirm the subscription is active and that the deployment administrator can create the required Azure resources and customer-owned application registration.
- Request Microsoft Foundry / Azure OpenAI Global Standard quota for the subscription before deployment. A Foundry project or Azure AI resource does not need to exist first.
- Choose one of the currently supported deployment regions and verify live VM, networking, model, and embedding availability in that subscription.
- Decide who will be the initial RapidClaw administrator. The authenticated deployment operator becomes the initial Command Center administrator.
Quota approval can take time
Submit the Microsoft quota request before the planned deployment date. Do not begin provisioning until the wizard's prerequisite check confirms the required quota in the selected region.
Supported Azure regions
- Australia East
- East US 2
- South India
- Sweden Central
- West US 3
A listed region is supported by RapidClaw, but it is not automatically ready for every Azure subscription. The wizard checks live capacity and quota before deployment. See the detailed prerequisite guide for the current Microsoft quota form, suggested justification, and requested model settings.
The six deployment stages
- Connect: Sign in with Microsoft, create or recover the customer-owned application registration, validate the product entitlement, and select the Azure subscription.
- Deploy: Select the supported Azure region, run prerequisite checks, set the cost-alert budget and email, and provision the Azure foundation.
- OpenClaw: Install the verified OpenClaw extended-stable runtime and the shared RapidClaw services.
- Agents: Install the Base agents, skills, schedules, and policies plus the selected product extension where applicable.
- Teams: Build and publish the tenant-specific RapidClaw Teams package and verify its forwarding path.
- Command Center: Verify runtime health and open the authenticated administrator experience.
What is deployed
| Setting | Current deployment |
|---|---|
| Virtual machine | Standard_D2as_v6 |
| Operating system | Ubuntu 24.04 LTS Gen2 |
| OpenClaw | Latest RapidClaw-verified extended-stable release |
| Runtime database | Customer-owned Azure Database for PostgreSQL Flexible Server |
| Secrets | Azure Key Vault-backed protected storage |
| AI plan | Verified direct Microsoft Foundry / Azure AI model deployments plus text-embedding-3-small |
The browser is not the deployment engine
Long-running work is performed by durable server-side services. If the page refreshes or you sign in again, Setup can recover the deployment state instead of creating a second runtime. A normal deployment takes about 20 minutes after prerequisites are ready.
After deployment
- Open Command Center and confirm runtime, model, connector, Teams, subscription, memory, usage, and health status.
- Review seeded agents, skills, schedules, policies, and product-specific Agent Packs before enabling broader behavior.
- Keep schedules disabled until scope, model, tools, delivery, and approval requirements are understood.
- Use the configured Azure cost alert and Command Center Usage & Costs page to monitor consumption.