Loading...
Loading...
RapidClaw runs in the customer’s Azure tenant. For clean isolation, create a new dedicated Azure subscription for RapidClaw instead of mixing the runtime with unrelated workloads. Before starting setup, confirm the subscription, target region, and Azure AI Foundry / Azure OpenAI quota are ready.
Create a new Azure subscription for RapidClaw so the runtime, quota, cost, access, and policy boundary are easy to understand.
The subscription should belong to the customer tenant and be used specifically for RapidClaw. This keeps the deployment isolated from unrelated Azure workloads and makes billing, governance, and support conversations cleaner.
RapidClaw needs available model capacity in the subscription and region selected for deployment.
A valid Azure subscription is not enough by itself. Azure AI Foundry / Azure OpenAI capacity is quota-based, and quota availability varies by region and model family.
Open the official Microsoft quota instructions so you can confirm the current Microsoft process.
Open Microsoft quota instructions
For the Azure OpenAI quota request form, use these RapidClaw recommendations:
Quota is a capacity limit, not a usage charge. You do not pay for the requested quota itself. Azure OpenAI / Foundry billing is based on tokens actually used by RapidClaw.
Do not start RapidClaw deployment until you receive the Microsoft email confirming quota approval. Approval may take a day or two.