Cloud & email management
Keep your business email and cloud tools organized and secure
Administration of Google Workspace and Microsoft 365 — accounts, access, mailboxes, domains, security and backups — handled deliberately instead of whenever something breaks.
For businesses running Google Workspace or Microsoft 365 with nobody formally administering it.
- Platforms
- Google Workspace and Microsoft 365
- Scope
- Identity, mail, storage, domains and DNS
- Delivery
- Remote, with documented changes
Identity
- User accounts
- Groups
- MFA policy
Mail
- Mailboxes
- Shared mailboxes
- Anti-phishing
Storage & domains
- Drive / OneDrive
- Sharing rules
- Domain and DNS
Accounts follow a process
Creating and removing access is a documented procedure rather than a message to whoever has the admin password.
Configuration is recorded
Domains, DNS records, sharing rules and security settings are documented as they are changed.
Backups are verified
Backup coverage is checked on a schedule instead of assumed because a setting was switched on once.
The business problem
Email and cloud tools are business-critical and almost never administered.
They are bought once, configured by whoever set them up, and then left alone until a mailbox stops receiving, a former employee still has files, or a phishing message reaches finance. The platform is doing exactly what it was configured to do — which is the problem.
- Nobody knows how many licences are being paid for, or by whom they are used
- Former employees still have accounts, files or mail forwarding in place
- The admin password is shared, and no one can say who changed what
- DNS records for mail authentication were never completed correctly
- Sharing settings allow anything to be made public by accident
- Backup coverage is assumed rather than verified
- Onboarding a new employee takes a day of manual steps, done differently each time
Capabilities
What is administered.
Coverage is agreed in writing. Anything outside it is quoted rather than absorbed silently.
Accounts and access
- Account provisioning
- User access and roles
- Group management
- Shared mailboxes
- Licence review
- Onboarding and offboarding
Mail and domains
- Domain configuration
- DNS records
- Mail authentication (SPF, DKIM, DMARC)
- Anti-spam
- Anti-phishing
- Mail flow and aliases
Storage and devices
- Cloud storage management
- Sharing and permission rules
- Backups
- Retention settings
- Device setup assistance
- Documentation
Account lifecycle
Joiners, movers and leavers, done the same way every time.
Most cloud problems are lifecycle problems. Someone joins and gets access copied from a colleague. Someone changes role and keeps both sets of permissions. Someone leaves and nobody closes the account because nobody is sure what depends on it.
Access defined by role
Permissions come from a role definition, so nobody inherits an ex-colleague’s access by accident.
Departures close cleanly
Licences are reclaimed, data is retained or transferred deliberately, and forwarding does not quietly persist.
- Request A joiner, role change or departure is submitted through the agreed channel.
- Provision Account, licence, groups and access are created from the role definition, not copied from a person.
- Configure Mailbox, storage, device access and MFA are set up and verified.
- Change or revoke On a role change, old permissions are removed. On departure, access is revoked the same day.
- Retain and document Mail and files are retained or transferred per policy, and the change is recorded.
Email security
What protecting business email actually involves.
Email security is mostly configuration that nobody enjoys doing. It is also where most incidents start.
Mail authentication
SPF, DKIM and DMARC configured and monitored so your domain cannot be trivially spoofed.
Anti-phishing controls
Platform protections enabled and tuned, including external sender warnings and impersonation rules.
Access hardening
MFA enforced, legacy authentication disabled, admin accounts separated from daily-use accounts.
Sharing controls
Default sharing scoped so files are not public by accident, with exceptions granted deliberately.
Backup oversight
Coverage checked against what actually needs recovering, and verified on a schedule.
Incident documentation
When something happens, what occurred and what changed is written down.
Fit
Who this service is for.
A good fit when
- You run Google Workspace or Microsoft 365 and nobody administers it deliberately.
- Onboarding and offboarding are manual and inconsistent.
- You are paying for licences you cannot account for.
- Email deliverability or phishing has already caused a problem.
Consider a wider service when
- You also need device and end-user support — managed IT covers this plus the help desk.
- You first need to know the current state — an IT audit is the better starting point.
Process
How we take over an environment.
- 01
Review
We document the tenant as it is: users, licences, groups, mail flow, sharing, DNS and backups.
- 02
Stabilise
Urgent items — open access, missing authentication, orphaned accounts — are addressed first, with approval.
- 03
Standardise
Role definitions, provisioning steps and security baselines are written and applied.
- 04
Administer
Ongoing administration with documented changes and periodic review.
Engagement models
How this is contracted.
Managed monthly
Ongoing administration with an agreed scope and documented changes.
- Provisioning and access
- Security and backup oversight
- Best for teams without an administrator
Cleanup project
A one-off remediation of licences, access, DNS and security settings.
- Fixed scope
- Documented end state
- Best before recurring coverage
Part of managed IT
Included within a broader managed IT engagement.
- Same provider for support and cloud
- One escalation path
- Best when you also need a help desk
Why ZitDevs
How we work in your tenant.
Documented before changed
The environment is recorded as it is before we modify anything, so there is always a known previous state.
Your tenant stays yours
Administration is performed in your own tenant, under your ownership, not migrated into ours.
Change with approval
Anything that affects users or mail flow is proposed before it is applied.
Both platforms
We administer Google Workspace and Microsoft 365, including businesses running both.
FAQ
Questions about cloud and email management.
Answers are written for this service. Where a figure depends on your situation, we say so instead of publishing an average.
Do you support both Microsoft 365 and Google Workspace?
Yes, including businesses running both. Administration covers users, licences, groups, shared mailboxes, storage, sharing rules, security settings and domain configuration on either platform.
Can you migrate us from one platform to the other?
Migration is quoted as a project rather than included in ongoing administration, because it depends on mailbox count, data volume and how much has to be preserved.
Do we keep ownership of our accounts?
Yes. Administration is performed inside your own tenant under your ownership. Nothing is moved into an account controlled by us.
What happens when an employee leaves?
Access is revoked on the agreed timeline, the licence is reclaimed, and mail and files are retained or transferred according to the policy set with you. The change is documented.
Can you fix our email deliverability?
We can review and correct mail authentication records — SPF, DKIM and DMARC — and platform settings that affect delivery. Deliverability also depends on sending behaviour and list quality, which we will assess honestly rather than promise to solve.
Do you provide email backups?
We oversee backup coverage and verify it on a schedule. Where no suitable backup exists, we will recommend an approach and quote it rather than assume the platform’s defaults are sufficient.
Is this included in managed IT?
Cloud and email administration is part of a managed IT engagement. It is also available on its own if you have device and user support handled elsewhere.
Can you help with domains and DNS?
Yes: domain registration and renewal oversight, DNS records, mail authentication, subdomains and the records needed by your website and third-party tools.
Tell us what your cloud environment looks like.
Which platform, how many users, and what has already gone wrong. We will come back with a scope for review and ongoing administration.
The form is preselected for cloud and email management and asks which platform you run.