Viewing: All audiences
Small Business Cloud
Bring your cloud apps, backup and recovery into one practical plan, built around the information you can’t afford to lose.
Or go straight to

Cloud productivity with clear ownership
Pick licences, sign-in, file sharing and security settings to suit your team. Then agree who adds users, approves access, removes leavers and reviews privileged accounts.
Size licences to real use, so each one earns its place in the budget.
Choose around the team
Agree who
Synchronisation is not always backup
Cloud platforms can keep old versions or deleted items, but what they keep, and for how long, may not match what you’d need to recover. A good backup design sets out what’s protected, how often it’s copied, how long it’s kept, where copies are stored and how restores are tested.
Work out which files, email, shared data, apps and settings are critical.
Set how long data is kept around legal, operational and customer needs, not a generic default.
Decide how much data you could lose and how fast you need it back, then test realistic recovery scenarios.
Keep an eye on failures, access, storage growth, licences and recovery results.
Syncing, retention settings or a recycle bin aren’t automatically a complete backup.
Plan for common failure scenarios
The right response may combine platform controls, independent backup, endpoint protection on each device, identity security and documented recovery steps.
Know the recovery objective
Recovery objectives are design inputs, not guarantees, unless they’re explicitly contracted and tested.
How much recent data your business could afford to lose.
How quickly a service needs to be back up and running.
A proposal states protection scope, retention, recovery objectives and test frequency as separate items, so you can see exactly what is and isn’t covered.
Questions
Plain answers about backup, recovery, testing and migration.
Microsoft 365 includes resilience and retention features, but they may not meet every business recovery requirement. Check your data, how it could be deleted, retention and the restore process before you decide whether you need extra backup.
Backup makes copies of your data that you can recover. Disaster recovery is broader: the process, systems, dependencies and people you need to get the business running again after a serious disruption.
It depends on your business risk and how often things change. Test a representative sample of files, users and systems, record the result and fix any failures. Don’t assume a successful backup job means recovery will work.
We may be able to, after a discovery review of your current set-up. The proposal should define the source and target, identity, data volume, permissions, sequence, testing, how users are kept informed, the switch-over and rollback.
Related services
Your cloud tools rely on a dependable connection, and your team needs them in the office, on the road and on the phone.
Internet chosen around your location, team size, cloud apps, support needs and what downtime would cost you.
Check business availabilityPlans and coverage for your team, matched to how they actually use their phones.
Compare mobile optionsNumbers, call flows and cloud calling that get customers through to the right person.
Review my call setupPlanning a wider migration, disaster recovery or hosting? See Cloud and Data Centre for Corporate, and read how we handle information in our Privacy Policy.
Continuity review
Tell us what information matters, where it lives now and how long you could work without it. We’ll point out the gaps and suggest next steps from the live service catalogue.
Helpful to have ready
Please don’t include passwords, administrator details or system configuration in an enquiry. A summary is enough to start.
Tell us who’s affected and what’s stopped, so we can prioritise within your service terms.