Microsoft 365 Deployment in Rwanda

What is Microsoft 365 deployment, and who needs it

It’s the full move: a properly configured tenant on your own domain, licences assigned per person, accounts with multi-factor authentication from day one, mail and files migrated, devices connected and the old system retired. It suits organisations leaving an ageing on-premises Exchange server, a hosting provider’s email, or Google Workspace, and new organisations that want to start correctly rather than fix things later.

The problem it solves

Rushed migrations create problems that last for years: everyone using one admin account, multi-factor authentication left optional, licences that don’t include features the organisation needs, files dumped into one library, and a cutover that loses a day’s mail because nobody planned the DNS change. A planned deployment gets the foundations right once, so later security and collaboration work builds on solid ground.

Choosing the right migration method

The source system and mailbox count decide the method:

Cutover migration moves every mailbox from an on-premises Exchange server in one go. Microsoft’s guidance limits it to small organisations and recommends other methods above roughly 150 mailboxes.

Staged or hybrid migration moves mailboxes in batches while old and new systems work side by side. It suits larger Exchange organisations and phased moves.

Google Workspace migration moves mail, calendars and contacts from Google.

IMAP migration moves mail only, from hosting providers and other systems. Calendars and contacts are exported and imported separately.

Whatever the method, old mail is copied in the background before cutover, so the switch itself is short.

Getting the foundations right

These settings are hard to change later, so we set them at the start:

• Separate administrator accounts for named people, never everyday mailboxes with admin rights.
• Multi-factor authentication enforced for everyone, with staff helped through setup. Microsoft retired basic authentication for Exchange Online from October 2022, so older mail clients that can’t use modern sign-in must be replaced.
• Email authentication records, SPF, DKIM and DMARC, published for your domain. Since February 2024, Google and Yahoo have required them from organisations sending mail in bulk to their users, and they protect your domain from being spoofed.
• Data location checked in the admin centre and documented, since Microsoft 365 data for Rwandan organisations is stored outside the country, which matters under Rwanda’s data protection law.

What the work involves

1. Assess mailboxes, data volume, devices, licences and DNS access.
2. Design licences per person, the migration method and the file structure.
3. Set up the tenant: domain, admin accounts, multi-factor authentication and email authentication.
4. Pilot with a small group, then fix anything that surfaces.
5. Migrate in batches, copying data in the background.
6. Cut over mail routing outside working hours, then support staff on the first day.
7. Retire the old system once everything is confirmed.

What’s included and what’s not

Typical timelines and what drives cost

A single office with fewer than 50 mailboxes typically takes one to three weeks, from planning to retiring the old system. Cost is driven by mailbox count, the volume of mail and files to move over your internet connection, the source system, how much file reorganisation is needed, and the number of sites and devices to set up.

Equipment typically used

Microsoft’s own migration tools for Exchange and Google sources, and third-party migration tools where they handle a source better. Access to your domain’s DNS. Modern Outlook, Teams and OneDrive clients on every device. A reliable internet connection, ideally with a backup link, since the whole office now depends on it.

Common mistakes we see

Licences chosen on price alone, then upgraded months later. Multi-factor authentication left for later. Old mail clients that stop working after basic authentication was retired. No SPF, DKIM or DMARC, so mail lands in recipients’ spam. A file server copied into one SharePoint library. And the old server left running indefinitely, still receiving some mail.