Microsoft & Cloud Services in Rwanda

What this covers

Getting onto the platform. Microsoft 365 deployment sets up the tenant, licensing and mailbox migration. Email and collaboration makes Exchange Online, Teams, SharePoint and OneDrive work together instead of as four separate tools. Cloud migration moves servers, file shares or applications to the cloud with a planned cutover.

Controlling identity and devices. Microsoft Entra ID handles sign-in, conditional access and single sign-on. Microsoft Intune enrols and governs laptops and phones. User and device management covers the day-to-day: joiners, leavers, patching and compliance.

Protecting it. Microsoft Defender for Cloud protects cloud workloads. Microsoft 365 security optimisation reviews what’s enabled against what should be. For endpoint-focused Defender work across your devices, see Microsoft Defender under Cybersecurity.

Running it. Cloud infrastructure management keeps cost, performance and configuration from drifting after go-live.

Where your data lives, and why it matters here

Microsoft 365 data for an organisation in Rwanda is stored in Microsoft datacentres outside the country. An administrator can see exactly where under Settings → Org settings → Data location in the Microsoft 365 admin centre, and different services can sit in different regions.

That matters because Rwanda’s Law N° 058/2021 on personal data protection requires personal data to be stored in Rwanda unless the data controller holds a valid registration certificate from the National Cyber Security Authority that permits storage outside the country (Article 50). Moving staff and customer data into Microsoft 365 is, in practice, a decision about cross-border storage.

We don’t give legal advice. What we do is document what data will move, where it will be stored and who can access it, which is the information you and your adviser need for the registration. Then we configure Microsoft 365’s own controls, such as retention, data loss prevention and access policies, to match.

Designing for real connectivity

Cloud services assume the internet is always there. Where it isn’t, a few design choices make the difference between a platform staff trust and one they work around:

• Offline-capable clients. Outlook in cached mode and OneDrive Files On-Demand let people keep working through an outage and sync afterwards.
• A second internet link with automatic failover, for offices where Teams calls and shared documents are part of daily work.
• Bandwidth planning for the migration. Moving years of mailboxes and file shares over a modest link can take longer than the technical work itself. We measure data volumes first and schedule the bulk transfer for nights and weekends.
• Teams call quality settings that prioritise voice and video traffic on the office network.

Mistakes we see in Microsoft 365 rollouts

Most of the problems we’re asked to fix come from a handful of shortcuts taken during the original setup.

Everyone signs in as a global administrator. It’s convenient during setup and dangerous forever after. Administrator rights should sit with named, separate accounts that are protected more heavily than everyday ones.

Multi-factor authentication left optional. Optional usually means most staff never turn it on, and a single phished password then opens the mailbox.

Files copied across without structure. A file server’s folder tree dumped into one SharePoint library recreates the old mess in a new place, with worse permissions. Planning team sites and access before migrating saves months of confusion.

Licences assigned and forgotten. Departing staff keep paid licences, and nobody notices for a year. A simple leaver process fixes both the cost and the security exposure.

No owner after go-live. Microsoft changes the platform every month. Without someone reviewing settings periodically, a well-configured tenant drifts out of shape.

How the engagement works

Assess. We review your current email system, file storage, devices, any existing Microsoft licences, and how and where staff work. That includes which personal data you hold and where it lives today.

Design. We map requirements to licence tiers, plan the migration, and choose which features to switch on: multi-factor authentication, conditional access, Intune policies, retention and data loss prevention.

Deploy. Tenant configuration, migration and device enrolment are scheduled to minimise disruption, usually with a pilot group first.

Secure. Baseline security goes in with the deployment, not as a follow-up project: enforced multi-factor authentication, blocked legacy sign-in methods, mailbox protection and administrator accounts kept separate from everyday ones.

Support. Microsoft changes the platform continuously. Periodic reviews keep your configuration aligned with new features, licence changes and your own growth.

Who it’s for

NGOs and international organisations need staff to collaborate across countries, offices and very different connection speeds.

Banks and MFIs need email and document handling that supports their compliance and records obligations.

Schools and hospitals are often moving off unsupported local mail servers that nobody is maintaining.

Government agencies are standardising on a single collaboration platform across departments.

SMEs want professional email, shared files and video calls without running and patching their own servers.

What we’ll need from you

• Details of your current email system and the number of mailboxes.
• Any existing Microsoft licences, or invoices if you’re unsure what you hold.
• A list of devices to manage, both company-owned and personal.
• An idea of what personal data you store and where.
• Access to your domain’s DNS settings, or the contact who manages them, since mail migration requires DNS changes.
• A technical or management contact who can approve changes during cutover.