Who Opened This Account? Running a Shadow Cloud Census Across a UK Business
Photo: Roger DeWitt on Flickr, CC BY 2.0, via Wikimedia Commons
Shadow IT used to mean a marketing team running a spreadsheet macro they weren't supposed to. In 2026 it means a customer-facing data pipeline living in somebody's personal Azure subscription, paid for with an expense claim marked 'software', understood by two people, one of whom has since left.
You cannot govern what you have not counted. So before the policy, before the stern note from the CISO, comes the census — a plain, slightly boring count of the cloud accounts your UK business is actually running, as opposed to the ones on the architecture diagram.
The cloud lowered the barrier and raised the blind spot
A decade ago, standing up a server took a purchase order, a lead time and a conversation with someone in infrastructure. Today it takes a card, a free tier and about eleven minutes. The friction that used to keep unsanctioned kit out of a business has largely evaporated, and nothing structural replaced it except hope.
The bill leaks in small amounts across dozens of expense lines, which is why finance rarely spots it and the platform team never sees it. The uncomfortable truth is that most of these accounts are neither malicious nor even careless. They are how the work got done in a busy quarter.
Four places where shadow accounts leave a trail
Nobody spins up a cloud tenancy in complete silence. Look for the residue.
- DNS and certificates. Your zone files are a confession. CNAMEs pointing at vendors, validation records for certificates nobody requested, subdomains resolving to regions you never chose. Start here and you will find half the estate in an afternoon.
- Identity. Pull the last ninety days of SSO sign-ins and compare them with your known application list. Anything with a healthy login rate and no owner is a finding.
- Money. Corporate card statements, expense categories, and marketplace subscriptions inside your main account. Look for recurring small charges: they are the signature of a tool that became load-bearing.
- Delegated access. OAuth grants to third-party apps, API keys issued to contractors, and the domain registrar account that was set up by the agency in 2019 and never handed over.
The three archetypes that always turn up
The experiment that worked. A proof of concept that quietly became production. Real users, no monitoring, a database with no tested restore. Nobody decided to promote it; it simply accumulated uptime.
The contractor handover. A partner built something in their own tenancy. The project ended, the invoices stopped, the subscription did not. The only person with admin rights is now on a different contract.
The acquisition souvenir. A business you bought in 2024 brought its own estate, its own domains, its own region choices and its own definition of a backup.
There is a fourth, more common than any of these: the perfectly reasonable tool. A SaaS product with a cloud backend attached, bought by a team lead on a card because procurement took six weeks and the project took three.
Triage: four decisions, no drama
Resist the urge to switch things off on a Friday afternoon. Sort each account into one of four buckets instead.
- Absorb. Bring it into the main estate, give it tagging, monitoring and a backup policy.
- Adopt. Leave it where it is, but attach an owner, a budget line, an SSO connection and an alert.
- Retire. No users, no traffic, no owner. Decommission it properly and keep the evidence that you did.
- Tolerate. Deliberately accepted, time-boxed, written down. A known unknown is better than an unknown unknown.
The UK GDPR questions that follow
This is where a shadow account stops being a housekeeping issue. Under UK GDPR your organisation is the controller for personal data wherever it sits, including in a tenancy the DPO has never heard of. If that account holds customer records, four questions arrive at once. Is there a data processing agreement with the provider? Where is the data stored, and does any of it leave the UK? Is the provider listed in your subprocessor register? And would you know within 72 hours if it were breached, in a form you could report to the ICO?
Post-Brexit transfers add a wrinkle. Sending data to the EU still runs on the UK's adequacy regulations, but onward transfers to the US need a valid mechanism — the UK extension to the Data Privacy Framework, or the International Data Transfer Agreement. A developer clicking through a vendor's standard terms has, in effect, made a transfer decision on your behalf. The census is how you find that out on your own schedule rather than the regulator's.
Guardrails beat gatekeeping
The instinct after a census is to tighten approvals. Done badly, that just pushes the next account further out of sight. What genuinely reduces shadow IT is making the sanctioned path faster than the unsanctioned one.
Give every engineer a sandbox subscription with a hard budget cap and no production data. Build a landing zone that issues an approved account in under ten minutes. Create a small-tools procurement route that takes a day rather than a quarter. Enforce tagging at creation so cost and ownership arrive attached. And keep a public register of accounts so the question 'does anyone own this?' has an answer.
Put it on the calendar
Run the census quarterly, and always after an acquisition, a restructure or a significant contractor exit. Once the discovery queries exist it is an afternoon of work — and it is the difference between a register and a surprise.