Professional Services · Projects
Plan and deliver the change.
Migrations, security and identity projects, Azure infrastructure and the data platform, scoped in a statement of work and run with milestones your team can see.
At a glance
- For
- IT leaders and partners with a defined change to make
- Starts with
- A scoping call and a licensing review
- Agreed in
- A statement of work
- Ends with
- An acceptance review and documentation
When to call
The situations this practice is built for.
Moving mail and files
On-premises or hybrid Exchange, Google Workspace, or another Microsoft 365 tenant, moving into the tenant you will keep.
Merging or splitting tenants
Acquisitions, divestitures and consolidations that need users, mailboxes and data moved between tenants.
Closing security gaps
Defender, Purview and Conditional Access configured from what you already license, before buying more.
Scope
What the practice delivers.
01
Microsoft 365
- Tenant-to-tenant migrations, merges and divestitures
- Exchange migrations, on-premises and hybrid
- Google Workspace to Microsoft 365
- Intune and Autopilot
- Teams Phone and calling plans
- Windows 365 and Azure Virtual Desktop
- SharePoint and OneDrive
02
Azure infrastructure
- Azure VM deployments
- Landing zones: identity, governance, networking and policy
- App hosting and migration
- Hybrid connectivity
- Backup and disaster recovery
03
Security & identity
- Defender for Endpoint, Servers and Cloud
- Purview: data loss prevention, sensitivity labels, retention
- Conditional Access and Entra ID governance
- Zero Trust frameworks
- Security posture management
04
Data & platform
- Power Platform and Power BI
- Microsoft Fabric architecture
- SQL database migrations and integrations
- Dataverse and automation
How an engagement runs
Four stages, agreed before work starts.
- 1
Align
Scope, a licensing review, risks and success criteria, written into the statement of work.
- 2
Plan
Architecture, migration plan and cutover runbook, with milestones your team can follow.
- 3
Deliver
Pilot, migration waves and validation, run by a named project manager.
- 4
Validate & hand over
An acceptance review against the agreed criteria, documentation your team can operate from, and an optional move into Managed Services.
What you receive
Deliverables you can hold the project to.
- Statement of work
- Scope, milestones and acceptance criteria in writing
- Project manager
- A named person accountable for the project
- Runbook
- The cutover plan, shared before cutover
- Documentation
- Written for your team to operate from
Next step
Describe the change you need to make.
The environment, the deadline and what is in the way. The services team replies by email.