Our cloud services
From Microsoft 365 to day-to-day operations – bookable individually, most effective together.
Microsoft 365 & Entra ID
Mail, Teams, SharePoint and identities set up properly – with security baselines, licence advice and a backup Microsoft doesn't include.
- Tenant setup or clean-up of a tenant that grew over time
- Multi-factor authentication and Conditional Access as the default
- Licences matched to the role instead of the most expensive plan for everyone
- File storage: SharePoint/OneDrive structure with a permissions concept
- Backup of mailboxes, Teams and SharePoint outside Microsoft
Cloud migration
Servers, file servers, line-of-business applications or email – we migrate in waves, test beforehand and keep a fallback until the very end.
- Inventory: what may, what should, what must stay
- Migration in waves with planned, short interruptions
- Test run and sign-off before every cutover
- Rollback plan for every phase
Cloud infrastructure
Virtual servers, storage and networks on Azure, IONOS, AWS or Google Cloud – matched to the application and the data situation.
- Provider choice by application, data protection and cost
- Network, access and encryption from the start
- Infrastructure as code so nothing lives only in someone's head
Cloud backup & recovery
Protected copies in a second data centre – with regularly rehearsed recovery, not just a green tick.
- 3-2-1 principle including an immutable copy
- Recovery tests on a fixed schedule
- Also for Microsoft 365 and on-premises servers
Operations & cost control
After the migration the real work starts: updates, monitoring, access and above all keeping an eye on the bill. We run what we built – or what you bring along.
- Monitoring and alerting for services and costs
- Monthly cost report with concrete savings proposals (FinOps)
- Access reviews: who still has access, who no longer needs it
- Updates, patches and lifecycle of cloud services
- Documentation you keep – even if you leave us
Access & hardening
Identities, network rules and encryption for cloud environments – aligned with the security building blocks of the rest of your IT.
- Identity and permissions concept
- Logging of security-relevant events
- Documentation for data protection and processing agreements
Which cloud suits whom?
We're not tied to any provider. As a rule of thumb:
Microsoft Azure
When Microsoft 365 is already in place and Windows servers, Entra ID or Windows-based applications are in use.
IONOS Cloud
When storage in Germany is mandatory, requirements are manageable and a German contracting partner is preferred.
AWS
When development teams, containers or specialised services are needed and the environment grows fast.
Google Cloud
When Google Workspace is in use or data and analytics workloads are the focus.
When the cloud fits – and when it doesn't
Not everything belongs in the cloud. We'll say so even if it costs us a project.
Good candidates
- Email, collaboration and file storage for distributed teams
- Servers that would need replacing anyway
- Backups and emergency copies at a second location
- Applications with fluctuating load or seasonal peaks
- Sites without their own server room
Better to check or keep local
- Machine controls and production that must run without internet
- Applications whose vendor doesn't approve cloud operation
- Very large data volumes with little change
- Sites with weak or single internet connectivity
- Cases where running costs would be permanently higher than on premises
How a migration works with us
Four steps – and every step has a fallback.
Inventory
Which systems, which data, which dependencies, which contracts. Plus the question: what is allowed in the cloud at all?
Target picture & costs
Provider, architecture, storage location, licences and the realistic monthly bill – compared with today's solution.
Migration in waves
Non-critical systems first, then the rest. Every wave is tested, signed off and can be rolled back.
Operate & adjust
Monitoring, access, costs. After three months we compare plan and invoice and adjust.
Frequently asked questions about the cloud
Sensible next steps in the cloud
These services build directly on the topic of this page — not a standard bundle, just the sensible next step.
Microsoft 365
Mail, Teams and files set up properly – with clear permissions instead of sprawl.
The most common entry point: mail, Teams and files.
Learn moreBackup & recovery plan
Automatic backups, regular restore tests and a plan for the worst case.
The cloud is not a backup — your data still needs a copy.
Learn moreHosting & servers
Solid hosting in European data centres, monitored and kept up to date.
For applications that don't fit a standard package.
Learn more