---
# source: src/content/solutions/en/microsoft.md
# route:  /en/solutions/microsoft/
title: Microsoft
tags: [cloud, modern-workplace, security]
vendors: [microsoft]
summary: From planning a Microsoft 365 estate through rollout to running it. The demanding part is rarely the technology, it is the identity.
photoNeed: An Azure or Microsoft 365 admin surface on screen, being worked in rather than presented
stub: false
draft: false
kind: vendor
addon: false
vendorName: Microsoft
status: current
---

## What we do

**Planning and design.** Choosing the services you actually need, and Microsoft 365
security workshops so the configuration stays sound.

**Introduction.** From the first concept through a proof of concept to a phased rollout.
Phased, because a migration done in one go fails on the exceptions rather than on the
mailboxes.

**Setup and configuration.** The technical side of each service, and the policies behind
them.

**Operation.** When something sticks later on, we answer.

## Where it actually gets difficult

We get called in for Exchange Online and stay for Entra ID. The mailbox migration is
manageable. Conditional access, guest accounts and the question of who is really a Global
Administrator take considerably longer.

The second recurring item is storage. It moves from a file server with permissions that
grew over fifteen years into SharePoint, and the permissions move with it. A migration is
the only good moment to clean that up.