Azure through Squiid

What Azure is

Azure is Microsoft's cloud, and in AI projects its most requested piece is the Azure OpenAI Service, which serves OpenAI models inside an Azure subscription with the networking, regional and compliance controls enterprises ask for. Around it sit App Service and Container Apps for hosting, Azure SQL and Cosmos DB for data, Blob Storage for objects, and Entra ID for identity, which is usually already the organisation's directory. Deployments of models are named resources in a region, which is why Azure OpenAI code refers to a deployment rather than a model id.

For a vibe-coded app the reason to be here is nearly always institutional. A company with Microsoft 365, existing Azure commitments and a security team that has already approved Entra ID will want the AI workload in the same place, even when a direct provider API would be simpler. That is a legitimate constraint, and it is worth recognising rather than arguing with. Azure also tends to arrive with a procurement process attached, which is a reason to plan the integration rather than improvise it.

Why connect it through Squiid

Azure on Squiid is a partner arrangement. Squiid works with you to attach a subscription, configure app registrations and managed identity, and route access through the gateway at https://api.squiid.io/v1/azure/... with Authorization: Bearer $SQUIID_API_KEY, so client secrets are held centrally rather than pasted into each deployment. Usage bills at Microsoft's list price on the Squiid invoice with terms confirmed during onboarding, which keeps Azure spend visible next to the rest of the stack instead of in a separate portal.

• One account, one key, one bill, one dashboard. Azure sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Azure credentials. Your code carries SQUIID_API_KEY, so AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, AZURE_TENANT_ID, AZURE_OPENAI_ENDPOINT never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Azure costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• Partner-managed access to Azure services
• Azure OpenAI Service within your subscription
• App registrations and secrets held by Squiid
• Azure usage on the same invoice
• Microsoft list pricing, no markup

How to connect Azure

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, AZURE_TENANT_ID, AZURE_OPENAI_ENDPOINT
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/azure/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Azure charges per service by usage, region and tier, at the provider's listed price, with terms confirmed during partner onboarding. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Azure usage, with no markup and no per-request margin.

Azure has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Azure usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Your own account: Azure access is a partner arrangement on your subscription, with Squiid holding an app registration, so leaving means removing it. Squiid never owns your code, your schema or your domain, and the gateway speaks Azure's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Azure through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Azure usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.