Enterprise cloud catalogue
Build, move, govern, and run enterprise workloads on Azure.
Sense Cloud joins architecture, engineering, migration, service management, cost control, security, and resilience around the constraints of each Azure estate.
Service map
Applications
- Web/API
- Integration
- Batch
Data
- Operational
- Analytical
- Archive
Platform
- Runtime
- Network
- Identity
- Cloud
- Microsoft AzureAzure-native services with qualified third-party options.
- Coverage
- Assess to manageBounded assignments or connected transformation stages.
- Delivery
- Code and controlsAutomation, technical artifacts, runbooks, and handover.
Catalogue
Services cover the estate from strategy through service management.
Each service has a defined boundary and can connect to adjacent work where dependencies require it.
Assess and plan
Cloud advisory, portfolio analysis, target architecture, sequencing, and investment assumptions.
Build and move
Landing zones, automation, workload migration, application modernization, data foundations, and hybrid connectivity.
Control and improve
Managed services, governance, security posture, FinOps, reliability engineering, backup, and disaster recovery.
Lifecycle
Work advances through explicit technical stages.
The stages scale from a single workload to a multi-subscription estate.
- 01
Baseline
Confirm scope, inventory, dependencies, service criticality, constraints, and access.
- 02
Architect
Select target services, boundaries, controls, automation, telemetry, and recovery requirements.
- 03
Implement
Build in controlled increments, verify expected behavior, and record exceptions.
- 04
Transition
Complete technical acceptance, knowledge transfer, support setup, and remaining-work ownership.
Azure domains
The catalogue uses Azure services within clear architecture domains.
Product selection follows workload requirements, support boundaries, and existing customer standards.
Foundation
- Management groups
- Subscriptions
- Microsoft Entra ID
- Azure Policy
- Azure Monitor
Workloads
- Azure Virtual Machines
- App Service
- Azure Functions
- Container Apps
- Azure Kubernetes Service
Data and AI
- Azure Storage
- Azure SQL
- Microsoft Fabric
- Azure Databricks
- Microsoft Foundry
Protection
- Microsoft Defender for Cloud
- Key Vault
- Azure Backup
- Azure Site Recovery
- Microsoft Sentinel
Common outputs
Technical artifacts remain useful after the assignment.
The exact set is agreed during scoping and aligned to customer tooling.
- 01
Architecture set
Current and target views, service choices, constraints, interfaces, and exception records.
- 02
Engineering assets
Terraform or Bicep modules, pipeline definitions, configuration, tests, and release notes where build work is included.
- 03
Service materials
Monitoring requirements, runbooks, support boundaries, change procedures, recovery steps, and ownership transfer.
Starting point
Start with a bounded business or technical objective.
Scope is sized after the estate, stakeholders, and required outputs are understood.
Best suited to
- Azure programmes that cross architecture and delivery teams
- Estates with unclear ownership, cost, risk, or migration sequence
Needed to begin
- Named sponsor and technical contacts
- Access to relevant inventory and architecture information
Customer responsibilities
- Confirm priorities and constraints
- Provide subject-matter experts and approve access
Not included by default
- Product resale or authority to interpret licensing contracts
- Unstated production support or security monitoring