Sample Cloud Review: Sample Customer

This is a sample

Sample Customer is a made-up business, and everything in this report is fictional. The issues are ones small businesses commonly run into, so you can see exactly what a Cloud Review covers and what you get at the end.

πŸ“‹ At a Glance#

ItemDetail
BusinessSample Customer (fictional), an allied health clinic with 8 staff
WebsiteWordPress, on shared hosting set up by a former web developer
EmailMicrosoft 365, plus an online booking system that sends reminders
FilesOneDrive, and an older shared Dropbox account
Review dateNovember 2026

Summary#

The clinic’s systems work day to day, but two problems could take the business offline or put client data at risk, and both are quick to fix. The domain name is registered to the former web developer’s personal account and is due to renew on an expired card. Email has no DMARC protection and a broken SPF record, which is also why booking reminders land in spam.

Most of what we found is a one-off clean-up of about 12 hours, followed by light ongoing care.

🚦 Scorecard#

AreaRatingIn one line
Domain and DNSπŸ”΄ Act nowDomain is in someone else’s account and close to expiring
Email securityπŸ”΄ Act nowNo DMARC, and two SPF records (which is invalid)
Microsoft 365 security🟑 ImproveMulti-factor sign-in is off for 2 of 8 accounts, including an admin
Backups🟑 ImproveWebsite backups sit on the same server; Microsoft 365 data has no separate backup
Website🟑 Improve14 plugin updates waiting and an out-of-date PHP version
Licences and subscriptions🟑 ImprovePaying for licences and storage nobody uses
SSL certificates🟒 GoodValid and renewing automatically

πŸ” Key Findings#

1. The domain name isn’t in the clinic’s control πŸ”΄#

What we found: The domain (samplecustomer.example in this sample) is registered in the former web developer’s personal registrar account. Auto-renew is on, but the card on file has expired and the domain renews in six weeks.

Why it matters: if the domain lapses, the website and every email address stop working. Getting a domain back from someone else’s account can take weeks.

What to do: ask the developer to transfer the domain to an account the clinic owns (we can prepare the request), turn on auto-renew with a current card, and add a second contact so renewal notices aren’t missed. Our DNS record types guide explains the records that move with it.

2. Email can be spoofed, and reminders land in spam πŸ”΄#

What we found: there’s no DMARC record, and the domain has two SPF records. Mail servers treat that as an error, so SPF effectively isn’t working. The booking system sends reminders “as” the clinic but isn’t included in SPF or signed with DKIM.

Why it matters: anyone can send email that looks like it came from the clinic, which is how invoice and payment scams start. Legitimate reminders are more likely to be filtered as spam, which can mean missed appointments.

What to do: merge the SPF records into one, turn on DKIM for Microsoft 365 and the booking system, then add DMARC in monitoring mode and tighten it over a few weeks. Our guides cover SPF, DKIM and DMARC and third-party senders.

3. Two accounts can be taken over with just a password 🟑#

What we found: multi-factor sign-in is off for 2 of 8 Microsoft 365 accounts, and one of them is a global admin. The shared reception mailbox password is kept in a spreadsheet.

Why it matters: a stolen password on an admin account gives full control of email, files and users.

What to do: turn on multi-factor sign-in for everyone, create a separate admin account that isn’t used for daily email, and move shared passwords into a password manager. The ACSC small business guidance lists multi-factor sign-in as one of the first steps to take.

4. Backups exist, but wouldn’t survive a bad day 🟑#

What we found: the website is backed up nightly, but the backups are stored on the same hosting account. Microsoft 365 email and OneDrive files rely only on Microsoft’s built-in retention. No restore has ever been tested.

Why it matters: if the hosting account is hacked or closed, the backups go with it. Deleted or encrypted Microsoft 365 data can only be recovered for a limited time.

What to do: copy website backups off-site, add a separate backup for Microsoft 365, and test a restore every quarter.

5. The website needs maintenance 🟑#

What we found: 14 plugin updates are waiting, two plugins are no longer maintained, and the site runs on a PHP version that no longer receives security fixes. There’s no uptime monitoring.

Why it matters: out-of-date plugins and PHP are a common way small WordPress sites get hacked, and without monitoring nobody knows the site is down until a client says so.

What to do: take a backup, update plugins and PHP on a staging copy first, replace the two abandoned plugins, and add uptime monitoring.

6. Paying for things nobody uses 🟑#

What we found: three Microsoft 365 licences are still assigned to former staff, and the clinic pays for both Dropbox and OneDrive, with Dropbox only used for an old shared folder.

Why it matters: it’s money spent every month for nothing, and former staff accounts are a security risk while they stay active.

What to do: convert ex-staff mailboxes to shared mailboxes (where the history is needed) and remove the licences, then move the Dropbox folder into OneDrive and cancel Dropbox at its next renewal.

⚑ Quick Wins (This Week)#

TaskEffortWho
Update the card on the domain and request the transfer30 minutesPractice manager, with our help
Merge the SPF records into one15 minutesUs
Turn on multi-factor sign-in for the two remaining accounts30 minutesUs, with each staff member
Remove licences from former staff accounts30 minutesUs

πŸ—ΊοΈ The Plan#

Now (next 30 days)#

  • Domain transferred into the clinic’s own account, with auto-renew and two contacts
  • SPF fixed, DKIM on for Microsoft 365 and the booking system, DMARC in monitoring mode
  • Multi-factor sign-in for every account, and a separate admin account
  • Website backups copied off-site

Next (1 to 3 months)#

  • DMARC moved to quarantine once reports look clean
  • Microsoft 365 backup in place and a first restore tested
  • Website plugins and PHP updated, abandoned plugins replaced, uptime monitoring on
  • Shared passwords moved to a password manager

Later (3 to 12 months)#

  • Dropbox folder moved to OneDrive and Dropbox cancelled
  • A quarterly check of licences, renewals and backups
  • Website speed and SEO improvements

🧾 Subscription and Access Register#

Every review includes a register of the services you rely on, when they renew and who holds the keys. Here’s an extract:

ServiceRenewsAccount ownerMulti-factorStatus
Domain nameIn 6 weeksFormer developerUnknownπŸ”΄ Transfer
Microsoft 365MonthlyPractice manager6 of 8 users🟑 Fix
Website hostingAnnually, in MarchFormer developerOffπŸ”΄ Transfer
Booking systemMonthlyPractice managerOn🟒 OK
DropboxAnnually, in AugustClinic ownerOff🟑 Cancel

What Happens Next#

The report is yours to keep, whatever you decide. You can:

  • Fix things yourself using the plan and our docs.
  • Have us do the work through Cloud Experts, by the hour or as fixed-price jobs.
  • Hand the website and email over to Managed Hosting, so updates, backups and monitoring are looked after.
  • Keep it on track with a regular Check-in or Partner plan.