Microsoft 365
Tenant, identity, licensing, collaboration and administration planning.
Cloud and Microsoft 365
Plan, migrate and manage cloud services around identity, collaboration, resilience and the way employees actually work.

Direct answer
ABT’s existing Cloud IT page establishes cloud infrastructure and Microsoft 365 as long-standing service areas. The new page focuses on the ongoing responsibilities that follow a migration: identity, access, licensing, protection, recovery, user support and change management.
Specific platforms, migration scope and retention or recovery capabilities must be confirmed during discovery.
Service coverage
Tenant, identity, licensing, collaboration and administration planning.
Assess dependencies, sequencing, user impact, security and rollback before moving workloads or data.
Connect cloud access to user lifecycle, authentication and administrative responsibility.
Configure approved tools around communication, files, meetings and business workflows.
Clarify native retention, backup requirements, recovery ownership and testing.
Support users, maintain configuration and coordinate cloud vendors as business needs change.
The ABT difference
ABT stays at the center, coordinating the connected responsibilities around this service instead of leaving the business to manage the gaps between them.
Operating rhythm
Inventory users, applications, data, dependencies and current contracts.
Define the target environment, responsibility model and migration sequence.
Execute approved changes with communication, validation and rollback planning.
Manage access, support, licensing, security and improvement after cutover.
Common questions
No. Cloud services still require identity, configuration, licensing, security, support and governance.
Migration scope depends on the source systems, data, applications and approved project plan.
Retention and recovery vary by service and configuration. Backup requirements should be assessed explicitly rather than assumed.
Start with the business problem