For Azure users
If you are experienced with Microsoft Azure, this guide translates Azure service vocabulary, security concepts, and deployment models into Crusoe AI Platform terminology.
While Azure often requires upfront configuration decisions—such as selecting hosting plans, pricing tiers, and virtual network subnet delegates—Crusoe AI Platform provides a streamlined experience where services deploy instantly with built-in networking and security defaults.
Vocabulary Translation
| Azure Service / Concept | Crusoe AI Platform | Key Distinctions |
|---|---|---|
| Entra ID Tenant | Organization | Single organizational scope owning projects and user accounts. |
| Subscription & Resource Group | Project | Single unified workspace boundary for resources, access control, quota limits, and audit logs. |
| Subscription ID & Resource Group Name | Project Slug & Short ID | Human-readable slug (ml-team) and permanent short ID (ab12cd) used in workload network addresses. |
Entra RBAC Role (Contributor, Reader) | Project Role: admin or member | Streamlined access model (admin or member) eliminating complex custom role definitions. |
| Azure Portal | Web Console | Web management portal at https://console.codyhill.dev. See Create an Account. |
Azure CLI (az) & azd | platformctl | Unified CLI binary for agents, functions, container services, messaging, and data stores. See Install CLI. |
| Service Principal / Managed Identity | Service Account | Project-scoped machine identity (name@<project-short>.cai.local) holding project roles. |
| Client Secret / Certificate | API Key (cai_<keyid>_<secret>) | Single-reveal API key generated for service accounts with instant revocation capabilities. See Service Accounts. |
| Entra Token Acquisition | Authorization: Bearer <key> | Direct API key header authentication without requesting OAuth tokens from MSAL endpoints. |
| Container Apps Environment | Project Boundary | Project boundaries isolate network traffic automatically without requiring managed environment resources. |
| Azure Container Apps | Serverless Service | Direct container-to-HTTPS deployment with automatic scale-to-zero execution. |
| Container Apps Revision | Revision | Immutable snapshot of code and configuration created on every deploy, supporting traffic splitting. See Revisions. |
| Container Apps Scale Rules (KEDA) | Autoscaling & Min Instances | Built-in scale-to-zero autoscaling with optional min instances for zero cold-start latency. See Autoscaling. |
Ingress FQDN (*.azurecontainerapps.io) | Built-in HTTPS URL | Automatic HTTPS address assigned to every deployed service (https://<name>-<project-short>.apps.codyhill.dev). |
| Azure Functions | Function | Event-driven serverless code exposing handle(event) across Python, Node.js, Go, and Ruby runtimes. |
| Hosting Plan (Consumption, Flex) | Unified Serverless Execution | Single serverless execution engine with no complex plan selection required. |
| Azure AI Foundry Agent Service | Agents | Serverless AI agent execution for ADK, LangGraph, or CrewAI frameworks with built-in state management. |
| Foundry Thread | Sessions | Native conversation context management replayed automatically to models on each invocation turn. |
| Foundry Run | Agent Invocation | Single execution call to an agent endpoint via the API or platformctl invoke. See Invoke. |
| Container Apps Dynamic Sessions | Code Sandbox | Ephemeral, isolated container sandbox executing untrusted code securely per invocation. |
| Azure AI Search Vector Store | VectorDB Index | Dedicated high-performance vector database using HNSW indexing and payload filtering. |
| Azure Managed Redis | MemoryStore | Managed in-memory key-value store speaking standard Redis wire protocol. |
| Service Bus Queue / Topic | Pub/Sub Topic & Subscriptions | Unified messaging service providing point-to-point queues and pub/sub fan-out subscriptions. |
| Event Grid | Pub/Sub | Single unified event messaging service eliminating multiple overlapping event services. |
| Durable Functions | Pub/Sub Chains / Agent Orchestration | Multi-step workflows orchestrated via Pub/Sub event sequences or AI agent tool chains. |
| Azure Key Vault | Secrets Manager | Project-scoped secret management with numbered version history injected directly into workloads. |
| Azure Monitor & Log Analytics | Logs | Real-time log streaming with 14-day persistent history surviving container scaling. |
| Activity Log | Project Audit Log | Always-on management operations auditing recorded automatically for all project members. |
| Subscription Quotas | Project Quotas | Real-time resource quota tracking providing clear capacity bounds without complex billing sub-SKUs. |
| M365 Copilot Agent | Embed Chat | Turnkey web chat widget embeddable on any website with domain allowlisting. |
Key Similarities
- Immutable Revisions: Deploying creates an immutable revision snapshot, enabling safe traffic splitting and instant rollbacks—matching Container Apps revision lifecycles.
- Scale-to-Zero Compute: Workloads pause when idle and wake instantly on demand, mirroring Container Apps scale-to-zero behavior.
- Thread and Session Model: Managing conversation state using session identifiers matches Azure AI Foundry thread and run concepts.
- Role-Based Machine Identities: Service accounts function as project-scoped identities holding roles and authenticating via API keys.
Architectural Distinctions
Platform Streamlining
- Zero Upfront Plan Decisions: Deploy immediately without selecting hosting plans, capacity tiers, or subnet delegations.
- Single Standard Authorization Header: Authenticate directly with
Authorization: Bearer <key>—no MSAL libraries or token endpoints needed. - Unified Messaging Model: A single Pub/Sub service handles both point-to-point queuing and fan-out notifications.
- Built-in HTTPS Endpoints: Every function, agent, and service receives a public HTTPS URL upon deployment.
- Ephemeral Sandbox Execution: Code Sandbox instances run in isolated single-use containers destroyed upon completion, preventing cross-tenant residue.
Azure Migration Considerations
- Single-Region High Efficiency: Compute resources operate in high-density, low-latency environments optimized for fast execution and inference.
- Workflow Orchestration: Multi-step workflows utilize Pub/Sub event chains or AI agent tool sequences to orchestrate steps.
- Secret Lifecycle: Updating a secret creates a new version and automatically updates attached workload revisions.
Hands-On: Manage Secrets Without Provisioning a Vault
On Azure, storing a secret requires first provisioning a Key Vault resource. On Crusoe AI Platform, secrets belong directly to your project. Using platformctl or the HTTP API:
export CAI_API="https://api.codyhill.dev"
export CAI_PROJECT="your-project-id"
curl -s -X POST "$CAI_API/v1/projects/$CAI_PROJECT/secrets" \
-H "Authorization: Bearer <your-api-key>" \
-H "Content-Type: application/json" \
-d '{"name":"openai-api-key","value":"sk-..."}'
Response (201 Created):
{
"name": "openai-api-key",
"version": 1,
"created": true
}
Updating the secret with a new value automatically creates version 2. See Manage Secrets.
Workload Migration Guide
| Azure Workload | Crusoe AI Platform Destination |
|---|---|
| Azure Container Apps | Serverless Overview and Autoscaling |
| Azure Function | Function Quickstart and Runtimes |
| Azure AI Foundry Agent | Agent Quickstart and Agent Deployment |
| Foundry Threads & Runs | Sessions and Invoke |
| Azure AI Search Vector Store | VectorDB Quickstart and Search |
| Azure Managed Redis | MemoryStore Quickstart |
| Service Bus Queues & Topics | Pub/Sub Quickstart and Publish & Consume |
| Durable Functions | Pub/Sub Event Chains or Agent Tool Pipelines |
| Container Apps Dynamic Sessions | Code Sandbox and Security & Limits |
| Key Vault Secrets | Manage Secrets and Use Secrets in Workloads |
| Entra Roles & Managed Identities | Projects & Access and CI/CD Service Accounts |
Next Steps
- Review the side-by-side Service Mapping across all providers.
- Read the AWS Migration Guide and GCP Migration Guide.
- Explore core concepts in Core Concepts.