Multi Tenant Saas
Primary orchestration skill for building a multi-tenant Azure SaaS platform, integrating ISV landing zone guidance, SaaS Accelerator patterns, and marketplace publication workflows.
This skill is reviewed through Azure/git-ape PRs and maintained by its listed author. It is not bundled or activated with core. See the Skill Registry and use /git-ape-skills install multi-tenant-saas for explicit project or personal installation. Review is not a guarantee of safety.
Details
| Property | Value |
|---|---|
| Skill Directory | .github/community-skills/multi-tenant-saas/ |
| Author | dawright22 |
| Maturity | experimental |
| Available with Core | ❌ No — explicit installation required |
| Usage | /multi-tenant-saas SaaS product type, target tenants, regions, compliance needs, and preferred offer model |
Documentation
Multi-Tenant SaaS Orchestrator
Use this skill as the top-level entrypoint: /git-ape:multi-tenant-saas.
What this skill does
- Collects platform requirements (tenant model, scale profile, compliance, regions).
- Maps requirements to ISV landing zone and SaaS Accelerator implementation tracks.
- Produces a staged execution plan:
- Foundation and landing zone
- SaaS platform build-out
- Marketplace onboarding and publication
- Routes work to specialized skills in this plugin.
Authoritative multitenancy guidance
Use Architect multitenant solutions on Azure as the primary Azure Architecture Center reference for multitenancy decisions. Apply its principles across the specialist skills rather than treating multitenancy as only a data isolation concern.
For every architecture:
- Define tenants and the business-to-tenant mapping explicitly.
- Record the isolation model and trade-offs for compute, data, identity, messaging, and networking.
- Design tenant context propagation and authorization across every request and asynchronous message.
- Evaluate deployment stamps, tenant-to-stamp placement, scaling, and migration between stamps.
- Address noisy-neighbor controls, tenant-aware observability, metering, cost allocation, and operations.
- Automate the complete tenant lifecycle, including onboarding, configuration, movement, and offboarding.
- Avoid assumptions that all Azure services provide equivalent multitenancy or isolation guarantees.
Required outputs
- Target architecture with tenancy boundaries.
- Multitenancy decision record covering isolation, tenant context, deployment stamps, and tenant placement.
- Offer strategy (SaaS vs Azure app/VM/container alternatives).
- Marketplace readiness checklist with go-live gates.
- Day-2 operations and SRE control plan.