Cloud & Microsoft 365

Microsoft 365 and cloud, administered rather than just purchased

Almost every organization has Microsoft 365. Far fewer have it configured, tidied, and watched. The gap between those two shows up as security exposure and wasted licence spend.

Let's talk
An Amplaphi engineer working through a problem alongside a client

What this fixes

If any of this sounds familiar, this is the conversation

You are paying for licences nobody uses

Leavers keep their licence, duplicate subscriptions accumulate, and the bill grows a little every renewal without anyone deciding to spend more.

Sharing permissions have gone feral

Files and sites have been shared outwards over years. Nobody can say what is currently visible to people outside the organization.

A migration keeps being postponed

Moving mail, files, or a server to the cloud is planned and then deferred, because nobody can afford the day of downtime it seems to require.

Default settings are still defaults

Tenants ship configured for adoption, not for your risk profile. The settings that matter are the ones nobody has looked at.

What changes

What the business gets, not what the software does

  • Licence spend matches actual headcount and actual need
  • External sharing is known, reviewed, and reduced to what is intended
  • Migrations happen over a weekend rather than over a quarter
  • Accounts are created and removed as a process tied to HR, not to a reminder
  • Staff stop losing time to sync problems, permissions errors, and mailbox limits

Accountability

What we take responsibility for

Written into the scope before you sign, so there is no argument later about who owned it.

We own this

  • Day-to-day tenant administration and account lifecycle
  • Identity, access, and conditional access configuration
  • Migration planning and execution for mail, files, and workloads in scope
  • Collaboration configuration across Teams, SharePoint, and OneDrive
  • Licence position tracking and renewal recommendations
  • Backup of cloud data where that is in scope

What is included

  • Tenant configuration review against your actual risk profile
  • User onboarding and offboarding, including licence reclamation
  • Permission and external-sharing review
  • Teams, SharePoint, and OneDrive structure and governance
  • Mail flow, spam, and anti-phishing configuration
  • Licence inventory and rightsizing recommendations
  • Migration planning, pilot, cutover, and post-migration support

Not included, or depends on scope

  • Microsoft licence costs, which are billed by Microsoft or a licensing partner rather than absorbed into service fees
  • Cloud consumption for Azure or other platforms, which is passed through
  • Third-party backup for Microsoft 365 data, which is a separate product and a separate decision
  • Large or complex migrations, which are quoted as projects
  • Bespoke Power Platform or line-of-business development, which is outside what we take on

How it works

How the engagement runs

  1. Tenant review

    We look at configuration, permissions, licences, and sharing, and give you a written picture of what is actually set up today.

  2. Tidy and secure

    Unused licences reclaimed, external sharing brought back to what you intend, identity settings brought up to a defensible baseline.

  3. Migrate, if that is on the table

    A pilot group moves first. Cutover is scheduled outside working hours, with the old system available until the new one is proven.

  4. Keep it tidy

    Account lifecycle, licence position, and permission reviews run on a cycle so the environment does not drift back.

Honest fit

Who this suits, and who it does not

We would rather tell you now than three months into an engagement neither of us enjoys.

A good fit if…

  • Microsoft 365 is where your working day happens
  • You have accumulated years of sharing, accounts, and licences nobody has reviewed
  • You are planning a migration and cannot afford visible downtime
  • You want licence spend explained rather than simply renewed

Probably not right if…

  • You need custom application development on the Microsoft stack
  • Your business runs on a platform outside the Microsoft ecosystem and you want that supported in depth
  • You want licences bought at the lowest possible price with no administration attached

Getting started

What the transition actually looks like

Changing providers is the part everyone dreads. Here is each phase, what we need from you, and how disruptive it is.

Understand

Step 01 of 4

We go through what you have, what is breaking, and what the business is trying to do. We talk to the people who actually use the systems, not just whoever manages them.

What we need from you
Access to your current setup, time with a few key people, and an honest account of what frustrates you.
What you get
A written summary of what we found, including anything we think you should know before deciding to work with us.

Disruption to your business

None. Nothing changes during this phase, we are looking, not touching.

Straight answers

Questions we get about cloud & microsoft 365

Will a migration mean downtime?
Visible downtime is what we plan against. Mail and files are staged in advance, a pilot group moves first, and cutover happens outside working hours. You should notice a change of behaviour, not a stopped day.
Does Microsoft not back up our data already?
Microsoft protects its platform and offers limited retention. It is not a backup of your data against deletion, ransomware, or a departed employee clearing a mailbox. Third-party backup is a separate decision and we will tell you plainly what you have.
Can you reduce our licence bill?
Often, by reclaiming licences from leavers, removing duplicates, and matching plans to what people actually use. We show you the position and the saving; the decision to change stays with you.
Do you resell Microsoft licences?
Licensing arrangements are set out in your written scope so you can see exactly how licences are purchased and billed, separate from the service fee.

Wondering if cloud & microsoft 365 is what you need?

Describe what is going wrong. If this is not the right answer for you, we will say so rather than sell it to you.