MICROSOFT CLOUD
TENANT FOUNDATIONS
Security baselines, environment standards and monitoring in the customer tenant – so that delivery becomes reproducible, incidents are recognized faster and audits cause less effort.
MFA/Conditional Access & RBAC Models
Dev/Test/Prod Standards & Runbooks
Monitoring/Alerting + Evidence Documentation
When clients come to us
Need for Tenant/Security Hardening
MFA, Conditional Access, Roles
Lack of Standards
for Dev/Test/Prod and delivery processes
No Monitoring/Alerting
Incidents are detected too late
Integration/Connectivity
must be implemented securely and auditably
Cost/Governance Pressure
Policies, standards, transparency
Audit Findings
or security reviews are upcoming
Standardization
after growth/M&A
Typically included
Architecture & Baselines
Identity/Access, Policies, Monitoring, Logging
Setup/Optimization
in the customer tenant incl. documentation
Operating Concepts
Runbooks, Alerting, Roles/Responsibilities
Automation
e.g., Templates/Standard Configurations, Naming/Tagging
Explicitly not included*
*(unless ordered separately)
Reselling of licenses or contract brokerage
Own hosting/managed hosting outside the customer tenant
24/7 NOC without an explicit SLA model
On-prem network/infrastructure work without coordinated interfaces/partners
TYPICAL DELIVERABLES
Cloud/Tenant Architecture & Security Baseline
Policies, Roles, Access
Monitoring/Alerting Concept
incl. Runbooks
Standardized Environment Blueprints
Dev/Test/Prod
IaC/Config Artifacts
Templates, Conventions, Naming/Tagging
Operations & Handover Documentation
RACI, Incident/Change Process
Audit-Ready Evidence
Control points, configuration, documentation