Microsoft 365 adoption in the mid-market — four phases, clear costs.

In 2026, "adopting Microsoft 365" (formerly: adopting Office 365, Office 365 implementation, Microsoft 365 implementation) means significantly more than migrating mailboxes to the cloud. Microsoft 365 is an integrated platform of productivity apps (Word, Excel, PowerPoint, Outlook), communication services (Microsoft Teams, Exchange Online), document management (SharePoint Online, OneDrive), identity platform (Microsoft Entra ID), security (Microsoft Defender, Microsoft Purview), endpoint management (Microsoft Intune) — and in the higher plans, Windows licenses.

A proper Microsoft 365 adoption in the mid-market therefore decides on five topics simultaneously:

• License strategy — which audience groups (knowledge workers, frontline, external) need which plans (Business Basic, Business Standard, Business Premium, Enterprise E3/E5)?
• Tenant setup — single tenant, multi-tenant, dedicated hosting region, custom domain, mail routing, compliance region choice.
• Identity — Microsoft Entra ID configuration, Conditional Access policies, Privileged Identity Management, B2B guest access.
• Migration — mailbox migration from Exchange on-prem or Google Workspace, OneDrive/SharePoint data, Teams voice setup, endpoint enrollment in Microsoft Intune.
• Adoption — training, power-user program, Microsoft Teams governance, Copilot rollout.

Anyone not thinking through these five topics together builds shadow IT, gives away 30 to 60% of license value and ultimately fails the NIS2 audit. arades GmbH delivers the full adoption in a 4-phase model with a fixed price per phase and a clear timeline.

Trap 1 — "We'll just do it quickly on Business Standard for everyone"

Microsoft 365 Business Standard costs around €11 per user/month — tempting, but it lacks Microsoft Defender for Business, Microsoft Intune and Microsoft Entra ID P1. For an NIS2-relevant mid-market company this is not sufficient. Business Premium (around €23) is the real mid-market plan.

Trap 2 — Migration without discovery

Migrating mailboxes without discovery often overlooks regulatory requirements (email archiving per GoBD, GDPR retention periods), special mailbox configurations (shared mailboxes, delegations, public folders) or third-party app integration (Salesforce, SAP, CRM tools). Result: corrections after go-live that cost three times the savings.

Trap 3 — Security baseline "later"

The tenant goes productive without Conditional Access, without MFA enforcement, without Defender. "We'll do that after go-live" — and then usually it never happens. Result: phishing successes, compromised accounts, NIS2 audit findings. The security baseline has to be in Phase 2, not "later".

Trap 4 — Microsoft Teams sprawl

Without governance, Microsoft Teams typically grows to 5 to 10 times more teams than are actually used after 12 months. SharePoint sites, OneDrive volumes and storage costs grow without control. Lifecycle policies (auto-archiving of inactive teams after 180 days) and naming conventions have to be in place from Phase 2 on.

Trap 5 — Adoption only as a one-day training

A one-day Microsoft 365 training for all employees has a half-life of about two weeks. After three months, most users use only mail and 20% of the actual features. Real adoption includes power-user programs, monthly use-case workshops, documented prompt libraries for Copilot and champion roles per department.

Trap 6 — No defined go-live

Microsoft 365 adoptions often slide for months into a "let's just pilot it" mode without a clear cut-over date. Result: legacy systems running in parallel, duplicate license costs, user confusion. A defined cut-over (weekend, clear communication, 24h standby) is mandatory.