Topic hub · Roll out Microsoft 365 in the mid-market

Microsoft 365 Introduction in the Mid-Market — four phases, clear cost.

A Microsoft 365 introduction (formerly Office 365 introduction) is no longer a pure IT project — it's an identity, security, and adoption task with license strategy and migration. We deliver the complete introduction mandate in four clean phases: Discovery, Build, Migration, Go-Live + Hypercare. Fixed-price packages, clear timeframes, CSP delivery.

Microsoft Partner since 2007 4-phase approach Discovery · Build · Migration · Hypercare Fixed price per phase Microsoft licensing partner · monthly consolidated invoice in euros

Microsoft 365 introduction · Definition

What a Microsoft 365 introduction concretely covers in 2026.

Anyone who in 2026 speaks of "rolling out Microsoft 365" (formerly: rolling out Office 365, Office 365 implementation, Microsoft 365 implementation) means much 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 tariffs Windows licenses.

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

  • License strategy — which audience groups (knowledge worker, frontline, external) need which tariffs (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 about these five topics simultaneously builds shadow IT, gives away 30 to 60% of license value, and fails at the latest at the NIS2 audit. arades GmbH delivers the complete introduction in a 4-phase model with fixed price per phase and a clear timeframe.

Four phases · fixed price per phase

How a Microsoft 365 introduction runs with us.

We split the mandate into four clearly delimited phases, each with its own deliverable. After every phase you can decide whether to continue with us or take over internally.

Phase 1 · 2 weeks

Discovery — license, audience groups, migration scope

In two weeks we analyze the current setup (Exchange On-Prem, Google Workspace, Microsoft 365 estate), user structures (knowledge worker / frontline / external), data volumes (mailboxes, OneDrive, SharePoint, file shares), the compliance situation (NIS2 applicability, GDPR sensitivity classes), and the third-party systems (identity providers, antivirus, backup, third-app integration). Deliverable: written report with license recommendation, migration risk matrix, and phase schedule.

Fixed price on request · delivery: 2 weeks

Phase 2 · 3–5 weeks

Build — tenant, identity, security baseline

Based on the discovery report we set up the Microsoft 365 tenant, configure Microsoft Entra ID (tenant branding, MFA, Conditional Access, Privileged Identity Management), activate the security baseline (Microsoft Defender for Endpoint, Defender for Office 365, Purview Information Protection, Purview Audit), set up Microsoft Intune for endpoint management, define Microsoft Teams governance (naming conventions, lifecycle policies), and set DLP policies. Deliverable: productive tenant with documented configuration.

Fixed price on request

Phase 3 · 2–4 weeks

Migration — mailbox, data, endpoint

Data migration from existing systems. Mailbox migration from Exchange On-Prem (hybrid setup with Microsoft Entra Connect or cutover) or from Google Workspace (Migration Manager). OneDrive and SharePoint data via the SharePoint Migration Tool or a third-party tool. Endpoint migration: devices are enrolled in Microsoft Intune, security profiles applied, apps distributed. Deliverable: productive mailboxes, data, and endpoints — ready for go-live.

Fixed price on request

Phase 4 · 4 weeks

Go-Live + hypercare + adoption

Cutover weekend with minimal service interruption. Training of all employees in Microsoft Teams, Outlook on the web, OneDrive, SharePoint. Floor-walking in go-live week, daily stand-up. After go-live four weeks of hypercare with elevated response readiness. Optionally followed by Application Care as ongoing care. Deliverable: productive Microsoft 365 setup with enabled users.

Fixed price on request

Overall order of magnitude: We calculate a complete Microsoft 365 introduction in the mid-market as a fixed-price mandate on request — including all phases, without the ongoing Microsoft licenses. Quick-win setups without data migration we share separately.

What we've learned from 18+ years of Microsoft 365 introductions

Six traps that mid-market introductions typically fall into.

Trap 1 — "We'll just go quickly with 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 that's not sufficient. Business Premium (around €23) is the real mid-market tariff.

Trap 2 — Migration without discovery

Anyone migrating mailboxes without discovery often overlooks regulatory requirements (email archiving under GoBD, GDPR retention periods), special mailbox configurations (shared mailboxes, delegations, public folders), or third-app integration (Salesforce, SAP, CRM tools). The 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" — usually never happens. Result: phishing successes, compromised accounts, NIS2 audit findings. The security baseline must be in Phase 2, not "later".

Trap 4 — Microsoft Teams sprawl

Without governance, after 12 months Microsoft Teams typically holds 5 to 10 times as many teams as are actually used. SharePoint sites, OneDrive volume, and storage costs grow uncontrolled. Lifecycle policies (auto-archival of inactive teams after 180 days) and naming conventions must be in place from Phase 2 onward.

Trap 5 — Adoption as a one-day training only

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 covers 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 introductions often slide for months into a "let's test with a pilot" mode without a clear cutoff date. Result: parallel running legacy systems, double license costs, user confusion. A defined cutover (weekend, clear communication, 24h standby) is mandatory.

Four checklists · a concrete list for every phase

The checklists we use internally for every introduction.

Four operational lists our architects work through in every mandate. We share them openly — copy them for your own project or use them to evaluate another provider.

Checklist 1 · Pre-migration

To clarify before the first mailbox migration.

  • Mailbox inventory with size distribution and mailbox types (user, shared, resource, room)
  • Email archive status (Exchange Online Archiving, third-party, on-prem archive)
  • Public folders inventoried, migration strategy defined (mail-enabled group, SharePoint, Teams channel)
  • Delegations and proxy configurations documented
  • DNS ownership clarified (MX, SPF, DKIM, DMARC, Autodiscover)
  • Third-app integrations captured (CRM, ERP, marketing tool, ticketing system)
  • Post-migration backup strategy defined (Microsoft Backup vs. third-party)
Checklist 2 · Tenant configuration

Configuration standards in the tenant build.

  • Tenant region and data residency documented
  • Custom domain verified, primary SMTP suffix set
  • Microsoft Entra ID tenant branding, MFA enforcement, Conditional Access baseline (at least 5 policies)
  • Privileged Identity Management for Global Admin roles activated (just-in-time)
  • Microsoft Defender for Office 365 activated (Safe Attachments, Safe Links, Anti-Phishing)
  • Microsoft Purview Sensitivity Labels (at least 3 classes) and DLP policies defined
  • Microsoft Teams governance: naming conventions, expiration policy 180 days, guest-access rules
  • SharePoint external sharing policy per GDPR classification
Checklist 3 · Change management

Organize communication and training.

  • Management kickoff with clear "why now" message
  • Pilot group (10–15 champion users from 3 departments) named
  • Weekly status email to all employees during the migration weeks
  • One champion per department named with a clear role profile
  • FAQ document in the intranet, kept growing during the pilot phase
  • Go-live weekend communication: 14 days before, 3 days before, go-live day, +3 days
  • Floor-walking plan for go-live week (at least 2 companions per site)
Checklist 4 · 30/60/90-day plan

What happens after go-live in the first three months.

  • Day 0–30 (hypercare): daily stand-up, elevated response readiness, all tickets escalated
  • Day 0–30: adoption training for all departments completed, quick-reference cards distributed
  • Day 30–60: champion program started, monthly use-case workshops introduced
  • Day 30–60: Microsoft Teams telephony evaluated, calling plan or direct routing decided as needed
  • Day 60–90: first adoption metrics (active usage, Teams adoption rate) measured, improvement backlog maintained
  • Day 60–90: Copilot pilot with 10 users started, use cases documented
  • Day 90: transition to Application Care, shift to predictable monthly flat fee

Cost model note: We calculate Microsoft 365 introductions as a fixed-price mandate per phase. The underlying architect day rates we name transparently on request. The license component is itemized separately and billed monthly in euros via the CSP model — it's project-independent and can be modeled upfront with our License Cost Calculator.

Further reading

If you want to go deeper.

Frequently asked questions about the Microsoft 365 introduction

What we get asked often — clarified before the first conversation.

How long does a Microsoft 365 introduction take in the mid-market?

A complete Microsoft 365 introduction in the mid-market (50 to 250 employees) typically takes eight to 14 weeks — from discovery to after go-live. A quick-win setup without migration is possible in four to six weeks. Multi-site or complex third-party integration extends to three to six months.

What does a Microsoft 365 introduction cost?

At arades we calculate the pure advisory work as a fixed-price mandate on request. On top come the Microsoft licenses, billed monthly in euros via the CSP model. License spend depends on audience groups and tariff choice.

Which phases does a Microsoft 365 introduction have?

Four phases: Discovery (2 weeks), Build (3–5 weeks), Migration (2–4 weeks), Go-Live + Hypercare (4 weeks). Fixed price per phase, decision at the end of each phase whether to continue with us or go internal.

What's the difference between a Microsoft 365 and Office 365 introduction?

Content-wise identical today. Only the brand name changed in 2020 from Office 365 to Microsoft 365. The higher Microsoft 365 tariffs (Business Premium, Enterprise E3/E5) include Windows licenses, Intune, and Defender, which aren't included in pure Office 365 tariffs.

Can an existing on-premises Exchange environment be migrated step by step?

Yes. Microsoft supports cutover migration (up to 150 users), staged migration (in stages), and hybrid deployment (Exchange On-Prem and Online in parallel, Entra Connect syncs). Hybrid is the standard for mid-market migrations from 200 employees on.

Plan your introduction

Which phase fits for you next?

30-minute first conversation — we clarify where your Microsoft 365 setup stands today and which introduction or migration phase makes sense next. First assessment with concrete numbers, usually within one business day.