Transition with a clear plan
We list accounts, domains, mailboxes and dependencies. We define migration steps, change schedules, checks and a rollback plan so you know what to expect before we start.
The licence is just the beginning. What matters is how accounts, data access and the devices your employees work from are set up.
We list accounts, domains, mailboxes and dependencies. We define migration steps, change schedules, checks and a rollback plan so you know what to expect before we start.
We manage users, groups, shared mailboxes and permissions. We help set up multi-factor authentication and access policies appropriate to your way of working and available licences.
We connect user needs with Windows device management, Intune and business identities. We pay particular attention to onboarding new employees, role changes and secure offboarding.
We check Outlook profiles, mail flow and access to services. We agree on tenant administration and document key settings so the migration does not end without clear responsibility for ongoing operation.
We get to know the system, users, risks and the desired outcome.
We define scope, schedule, responsibilities and post-work checks.
We document what was done and agree on ongoing maintenance.
The initial review covers Microsoft Entra ID, administrative roles, MFA and licence assignment. We define the procedure for creating, changing and closing accounts, group membership and access to shared resources. Administrative privileges are separated from everyday user work, and exceptions are documented.
We list mailboxes, aliases, distribution lists, shared mailbox permissions and applications that send mail. The plan covers verification of domains, DNS records, mail-flow rules and connectors, a pilot user group, final synchronisation and Outlook profile checks. Transfer of calendars, contacts and archives is verified separately according to the chosen migration method.
For the agreed devices we define enrollment, configuration profiles, compliance policies and the update schedule. Conditional Access is introduced after verifying licences and the impact on users: basic functionality requires Entra ID P1 and risk-based policies require P2, according to Microsoft's documentation. The scope of Intune and other services is aligned with your specific subscription.
Experience on projects for Rhenus includes coordinating user devices, business identities, migration activities and collaboration with central IT. The scope of a new engagement is defined separately, without assuming that every organisation needs the same configuration.
Not necessarily. The option of a phased transition depends on the source system, domains and business requirements. We first check the conditions and propose a suitable plan.
Licences and maintenance services are itemised separately in the offer. The range of available features depends on your subscriptions and the agreed service.
Tell us what works, what gets stuck and what you want to improve.