azure-saas-architect

What problem does it solve?

This Skill turns a high-level Azure SaaS decision into a concrete, provider-idiomatic architecture that teams can actually build and operate. It prevents vague cloud advice by grounding every major choice in tenant isolation, operational maturity, cost control, and current Azure verification.

Core Features & Use Cases

• Azure service mapping: Maps identity, network, data, compute, messaging, observability, security, and IaC decisions to native Azure services.
• Tenant isolation by data store: Specifies pooled and siloed isolation mechanisms for Azure SQL, Cosmos DB, Blob Storage, Redis, and Log Analytics.
• Operational and cost guardrails: Chooses services based on team maturity, flags verification items for SKU and region dependencies, and highlights cost risks such as telemetry ingestion and per-tenant database floors.
• Use Case: A product team has already chosen Azure and needs a landing zone, subscription layout, private networking, and a safe multi-tenant database strategy before implementation begins.

Quick Start

Ask for an Azure SaaS architecture for your multi-tenant product, including identity, networking, per-store tenant isolation, compute choices, observability, security posture, IaC, and cost controls.