Germany
Most of our German work is for the German entity of an international group — a GmbH that has its own tenant, its own works council and its own compliance obligations, but reports into a parent somewhere else. That is a specific problem, and it is the one we solve.
Who this is for
The German subsidiary of an international group. Head office runs Microsoft 365 somewhere else, the German entity has inherited its own tenant from an acquisition, and nobody owns the gap between them. English is already the working language of the IT function.
The Mittelstand company that has outgrown its reseller. Licences arrive as an invoice once a year from a Systemhaus that does not touch the tenant. When Exchange Online breaks on a Friday afternoon, there is nobody to call who understands the estate.
The group that just bought a German company. Two tenants, two identity providers, two licence renewal dates, and a works council that will have questions about any device management rollout.
What we do not do is sell licences and disappear. Our German clients are billed for engineering hours as well as subscriptions, because the subscriptions are a consequence of the relationship rather than the point of it.
What is different in Germany
These come up on almost every German project and rarely on projects anywhere else.
Under the Betriebsverfassungsgesetz, the Betriebsrat has co-determination rights over any system capable of monitoring employee behaviour or performance. Intune, Conditional Access and Defender all qualify. A rollout that ignores this gets stopped after deployment, not before it. We plan the technical work around the Betriebsvereinbarung timeline rather than assuming it away.
German buyers ask where data sits before they ask what it costs. Microsoft 365 data for EU customers stays within the EU Data Boundary, and Germany West Central is available for Azure workloads that need it. We put this in writing at the start rather than waiting for the security questionnaire.
An Auftragsverarbeitungsvertrag under Art. 28 GDPR, with the sub-processor chain named. Our contracting entity is inside the EU, which keeps that conversation short — no standard contractual clauses, no third-country transfer assessment for the contracting relationship itself.
We invoice from Estonia. With a valid USt-IdNr. the invoice carries no VAT and you account for it under the reverse charge procedure — the standard intra-EU B2B arrangement your finance team already handles. One EUR invoice, no foreign currency exposure, no withholding.
Available in Germany
Everything below is work we have delivered. Prices are fixed and quoted before we start.
Merging the German entity's tenant into the group's, or carving it out on a sale. We have run eight tenants into three, and seventeen into one.
Exchange Online, SharePoint, OneDrive and Teams. Cutover scheduled for a weekend window; our projects have not required downtime.
Mail, Drive, shared drives and calendars. The permission models do not map one to one, so the target structure is agreed before anything moves.
Active Directory to Entra ID, on-premises SharePoint to SharePoint Online, Exchange to Exchange Online. Hybrid stays up until you choose to switch it off.
Device enrolment, application deployment and Conditional Access — sequenced around works council approval, not ahead of it.
Security incident investigation, user onboarding and offboarding, mailbox and SharePoint changes, tenant administration. No retainer, no minimum — you are invoiced for the hours you use.
Invoiced in euros from our EU entity under reverse charge. Monthly or annual. You keep full ownership of the tenant and can move the CSP relationship at any time.
What you pay for against what you use: unassigned licences, duplicate subscriptions across tenants, expensive SKUs doing a cheaper SKU's job.
Relevant case study
The business was moving to another country and the entire Microsoft 365 estate had to move with it. Mid-project the migration host died. We rebuilt it and re-ran the migration, and some mailboxes came back with duplicated mail because users were already live in their new accounts. The clean-up was ugly but contained, and migration hosts are now sized at 120% of mailbox volume as a rule. The client came back later to fold a smaller company of their own into the same tenant, at 1,300 users.
Common questions
No. We invoice from our Estonian entity, inside the EU, in euros, under the reverse charge procedure. For a German company with a valid USt-IdNr. this is the same arrangement as buying from any other EU supplier — and it keeps the data protection conversation inside the EU as well.
Meetings and project sessions run in English. Email, tickets and documentation can be handled in German — if you write to us in German, you get an answer in German. Most of our clients here are international groups where English is already the IT function's working language.
In Microsoft's EU data centres. Microsoft 365 customer data for EU customers stays within the EU Data Boundary, and Azure workloads can be placed in Germany West Central where that is required. We are happy to put the specifics in writing before you send the security questionnaire.
For anything touching endpoint management, Conditional Access or security monitoring, yes — those systems fall under co-determination. We plan the technical rollout around the Betriebsvereinbarung rather than treating approval as a formality at the end. Projects that skip this get halted after deployment.
Yes, an Auftragsverarbeitungsvertrag under Art. 28 GDPR with the sub-processor chain named. Because our contracting entity is in Estonia, there is no third-country transfer to assess for the contracting relationship itself.
Yes. We hold Cloud Solution Provider authorisations covering 131 countries across Europe, the Middle East, Central Asia, Asia and Pacific, Australia and Canada, each invoiced in the local currency. Groups with entities in several countries are the reason we are structured this way. The United States is served by our US headquarters.
Scoping within a few days of the first call. Project start typically within a week or two of a signed quote, depending on the queue. First response on support requests is within four business hours, two for critical incidents.
No. Project work is quoted and delivered independently. Most clients move their subscriptions to us afterwards because it is simpler having one party responsible for both, but nothing requires it.
No charge, no obligation
A read-only review of your tenant — no agents installed, no changes made. You get a written summary of what you are paying for, what is unused, and what is exposed. Then thirty minutes with someone who has run these projects, in English, at a time that works for Central European hours.