Tenant architecture
Compare shared resources, separate customer deployments and hybrid approaches. Assess isolation, deployment frequency and the risk that one customer's heavy usage affects others before selecting a tenancy model.
Azure / Overview
DIGITAL CLOUD / Azure
Become a SaaS Provider
Plan the move from software delivery to an operated service. Consider customer isolation, onboarding, billing integration and service responsibilities.
Plan your solution01
Become a SaaS Provider
Understanding the solution
Offering software as a service adds a customer lifecycle to the application: onboarding, isolation, operation and eventual offboarding. Digital Cloud can help design a technically credible first SaaS offering on Azure. Product and commercial decisions remain connected to architecture so that customer commitments can be supported by the operating model.
Application modernization changes how software is built, delivered or operated to address a business need. Keeping, adapting and rebuilding are different choices with different cost and maintenance consequences.
Capabilities and scope
Customer lifecycle
Map account creation, tenant provisioning, configuration and data export. Define how authentication, subscriptions and billing integration connect without assuming that a payment system alone establishes tenant access.
Service economics
Plan tenant-aware telemetry, support access and cost allocation. Test onboarding and upgrade procedures alongside application features, including how customer data is handled during termination.
A practical example
A software vendor could pilot a hosted edition with separate deployments for early customers, then evaluate shared infrastructure when usage patterns and isolation requirements are understood.
What your project can deliver
- Tenancy and identity architecture with isolation assumptions
- Onboarding, upgrade and offboarding process design
- Pilot service backlog with operational and cost measures
The final deliverables, licensing and responsibilities are agreed for your environment before implementation.
02
Requirements and considerations
Review code ownership, dependencies, interfaces, test coverage and release constraints. SaaS designs also need customer separation, onboarding, billing integration and clear service responsibilities.
Become a SaaS Provider
Project priorities
Tenant isolation
Customer onboarding
Service economics
We begin with a conversation about the task, the people involved and the systems already in place. Together we identify what a useful result would look like and which dependencies need attention first. The agreed proposal sets the delivery boundaries, responsibilities and acceptance criteria.
Your engagement
How Digital Cloud can help
| Project phase | What happens |
|---|---|
| 01Define the design | Translate the requirements into a practical design. Confirm product choices, interfaces, permissions and the responsibilities needed to operate the solution. |
| 02Deliver in stages | Configure or implement the agreed scope, test representative workflows and resolve material issues. Plan user communication and any controlled transition from existing systems. |
| 03Prepare for ongoing operation | Confirm acceptance, document the relevant configuration and prepare the people responsible for daily use. Define maintenance and support arrangements before handover. |
Become a SaaS Provider
Questions before you start
Must SaaS use one shared database?
No. Shared and dedicated data stores are both possible; security boundaries, customization, cost and operational effort guide the decision.
What determines the cost and schedule?
The starting environment, integrations, user groups and agreed outputs determine the effort. We confirm scope and commercial terms before work begins. Software licenses, infrastructure consumption and ongoing support may be separate items.
What will we receive?
The proposal identifies the deliverables: these may include findings, a prioritized roadmap, a tested configuration, a prototype, documentation or training. We agree what is included and how completion will be assessed.
Can this work with our existing systems?
We review the actual applications, data sources and access requirements before recommending an integration. Dependencies and compatibility limits are recorded so the delivery plan reflects your environment.
What happens after the initial work?
You can use the findings to guide your own team or discuss a follow-on phase. Any maintenance, monitoring or support includes separately agreed service hours, responsibilities and response targets.
Product documentationMicrosoft Learn ↗