1 / 7
What we take care of
Consulting and concept. Which services you need, which you don't, and how they interact with your existing IT. Before the purchase, not after.
Migration. Moving from an on-premises Exchange, from another provider, or out of a grown environment – with mailboxes, calendars, contacts and files.
Setup and hardening. Sign-in, permissions, device management, sharing rules. The part that decides your security, and that almost nobody tidies up afterwards.
Ongoing operations. User management, new starters, leavers, licence adjustments, incidents. On request, as part of our Managed Services.
Hybrid connectivity. If parts of your IT stay in-house or in our private cloud, we connect both into one environment.
Migration is the part that can go wrong
A move to Microsoft 365 isn't a copy operation. It touches every workstation, every mailbox and every application that sends an email somewhere – and there are usually more of those than you'd think: the inventory system, the scanner in the hallway, the time-tracking tool, the till system.
That's why it starts with an assessment, not a cutover. We look at how things are connected today, plan the move in stages, and schedule the critical part for a window when nobody's working.
What matters to us: you shouldn't sit down on Monday morning to a computer where everything looks different and the signature is missing. Preparation decides whether a migration feels like progress or an imposition.
Licences: the right package, not the biggest one
Microsoft's licensing model is confusing, and that's no accident. There are packages that include services you'll never use, and standalone add-on licences that would be cheaper than the next tier up.
We look at who in your company actually needs what. A colleague who uses mail and Word needs something different from someone who works in SharePoint every day. Not every workstation needs the same licence.
That also includes tidying up old licences: former employees, duplicate assignments, services that were trialled three years ago and never used again. It's unglamorous, and it often saves more than a negotiation over discounts would.
The out-of-the-box state isn't secure
Microsoft 365 doesn't arrive hardened. It arrives functional – that's a different thing.
What we consider essential:
- Two-factor sign-in for everyone, not just management. Stolen passwords are the most common way in, and a second factor makes them largely worthless.
- Rules for who can sign in from where. Access from a country where you have no employees doesn't need to be possible.
- Permissions that follow actual need. In many grown environments, everyone can access everything – often without anyone realising.
- Control over external sharing. Who's allowed to share files externally, and what happens to links once they've been created?
- A clean offboarding process. The mailbox is rarely the problem. Forgotten shares and sign-ins are.
How this protection fits into your overall IT is covered on our IT Security page.
Microsoft doesn't back up your data the way many people assume
This is the point in conversations where things usually go quiet.
Microsoft makes sure the service runs and the infrastructure doesn't fail. Your content is your responsibility. The built-in recycle bins and retention periods are time-limited and designed for their own purpose – they're not a substitute for a backup.
In practice that means: if an employee deleted a folder four months ago and it's only noticed today, if a compromised account has emptied mailboxes, or if you need to retain data for years for legal reasons, the provider won't help you.
That's why every Microsoft 365 environment we support gets its own backup. What that looks like depends on your requirements – the basic questions are covered on our IT Security page.
Teams as a phone system
If you're already working in Teams, it makes sense to also make calls through it – with real phone numbers and call forwarding, not just internally.
That works well when it's properly connected. We implement both native Teams calling and standalone cloud phone systems – these are separate solutions, we don't combine them. More on our VoIP & Telephony page.
Where Microsoft 365 reaches its limits
We recommend Microsoft 365 where it fits – and say so where it doesn't. Typical cases:
Industry software that doesn't belong there. Practice-management, planning and inventory systems often need an environment Microsoft 365 doesn't offer. We run these systems in our private cloud, while mail and collaboration run on Microsoft.
Large files and many simultaneous users. Anyone working daily with large planning files or models hits sync limits sooner than the marketing suggests.
Especially sensitive data. Whether, and for which categories of data, Microsoft 365 is appropriate from a data-protection standpoint is assessed differently among data protection professionals – particularly in healthcare and for professionals bound by confidentiality. We tell you where we think caution is warranted, and offer an alternative in our own data center for that data. You make the decision, ideally together with your data protection officer.
That combination is exactly the solution for most of our customers: Microsoft 365 for what it's good at. Our private cloud for the rest.