Cloud Drive Mapper for government and public sector

Public-sector IT sits under sustained pressure to cut cost, shrink the on-premises estate, and hit sustainability targets, all without asking front-office staff to relearn a file workflow mid-shift. Cloud Drive Mapper is the way most councils, agencies and municipal IT teams retire their on-premises file servers without a change-management war. It presents your Microsoft 365 storage as the drive letters civil servants and public-safety staff already know, keeps the legacy line-of-business applications the estate depends on working exactly as before, and does it without any persistent access to your data at IAM Cloud's end.

1.5M+ active users worldwide

~5,000 organisations run CDM

ISO 27001 certified since 2016

01

Retire the on-premises file server, cut the cost that keeps it running

The file server is rarely the cheapest thing in a council or agency data centre, but it is nearly always the most politically difficult to remove. It sits under years of departmental folder structures, permission carve-outs and line-of-business dependencies that make a clean migration to SharePoint look like a change-management liability rather than a saving.

Cloud Drive Mapper is how public-sector IT teams retire the file server without a fight. The Microsoft 365 storage staff already have licences for becomes their working file storage. The drive letter they've mapped to for years still works. The line-of-business applications that expect a UNC path still get one. When the migration is done, the file server hardware, its backup appliance, its DR chain and its annual refresh budget are all optional.

02

Use the Microsoft 365 storage you already pay for

Most councils and agencies are on Microsoft 365 A5, E3 or E5, or the government cloud variants of those tenants. The SharePoint, OneDrive and Teams storage that comes with those licences is substantial, and it is already paid for. Without a middleware layer, though, it is difficult to make that storage usable for legacy applications and for staff who think in H: and S: drives, not SharePoint site URLs.

Cloud Drive Mapper is the middleware. It turns the storage you are already funding through your M365 tenant into working file storage that staff and applications treat as any other network drive. No double spend on a second storage product, no separate sync agent to keep patched, no ongoing licence for a file-share cloud alternative that duplicates what M365 already includes.

03

Shrink the data-centre footprint and hit sustainability targets

Public-sector sustainability commitments are increasingly hard: local-authority net-zero targets, central-government estate-reduction agendas, sector-specific carbon reporting. Every file server retired is watts saved, rack space returned, hardware refresh cycle broken, and one less appliance in the backup and DR chain.

Cloud Drive Mapper contributes directly to those numbers. The energy footprint of storing files moves from your building to Microsoft's hyperscale data centres, which operate at efficiencies no local server room can match, and which increasingly run on renewable power under contractually-verifiable terms. It is one of the few technical decisions that lands both a cost saving and a sustainability KPI in the same programme.

04

Familiar drive letters, no retraining, no help-desk avalanche

Front-office public-sector staff are not IT specialists. Housing officers, benefits assessors, licensing clerks, revenues staff, education administrators, public-safety professionals: they need files to be where they've always been, in folders named what they've always been named, on drive letters they've used for years. Retraining costs in this environment are political as much as financial, and they scale badly across hundreds of desks.

Cloud Drive Mapper looks like a file server to the user. The H: drive is still the H: drive. The S: drive is still the S: drive. The folder tree is the folder tree. Staff open documents the way they always did, save them the way they always did, and never need to know that the storage behind it has moved to Microsoft 365. The help-desk queue does not spike; the change is invisible where it needs to be invisible.

05

Legacy line-of-business applications keep working

Public-sector estates run a long tail of line-of-business software: planning systems, revenues and benefits, case management, licensing, GIS, electoral registration, adult social care records, public-safety dispatch, records management. Most of them predate cloud-native design and expect a Windows file system with real paths.

Cloud Drive Mapper presents Microsoft 365 storage as virtual network drives with real file paths. Whatever the software stack looks like, if it works with a Windows file server today, it works with CDM. That removes the "we can't move because X depends on the file server" objection from the migration conversation entirely.

Cloud Drive Mapper allows our City Hall and Public Safety professionals to leverage the security and reliability of the cloud without having to re-learn where and how to store their files, and with seamless access inside our legacy applications.
Mike Cook, Head of IT, City of Redondo Beach

06

Depots, satellite offices, home working and public buildings

Councils and agencies operate estates that are almost never concentrated in one building. Depots for highways and waste, satellite offices for planning and housing, libraries and leisure centres with staff PCs, home working for hybrid teams, public-safety facilities on separate networks. All need the same file experience as head office, without a VPN concentrator sized for the peak or a satellite file server per location.

Cloud Drive Mapper works directly over the internet using Microsoft Graph. Any device with a browser-grade internet connection reaches the same drive letters and the same files. The network hardware that used to be needed to make remote sites feel like head office is no longer needed for file access.

07

Retire SMB and RDP-to-the-file-server: a security upgrade at the same time

The two most-abused footholds in public-sector breach reports over the last several years are exposed SMB shares and remote-desktop sessions to legacy file servers, often reachable through poorly-scoped VPNs. Retiring the file server does not just cut cost; it removes those attack surfaces entirely.

Cloud Drive Mapper achieves that without downgrading the user experience. Staff still see drive letters. Applications still see file paths. Behind the scenes, the SMB service is off, the VPN concentrator is doing less work, and the remote-desktop-into-the-file-server pathway does not exist any more because the file server does not exist any more. It is a security posture upgrade that self-funds through the decommissioning it enables.

08

Works with Microsoft 365 Government and sovereign cloud tenants

Data-residency and sovereignty requirements shape most public-sector Microsoft 365 deployments: Microsoft 365 Government (GCC and GCC High) for US agencies, EU data-residency tenants for European bodies, and equivalent sovereign cloud arrangements where the local jurisdiction requires them. Middleware that only works with commercial M365 tenants is a non-starter in most of these environments.

Cloud Drive Mapper is tenant-agnostic. It authenticates against whichever tenant you point it at, and the storage it exposes never leaves that tenant's data boundary. IAM Cloud never holds a copy of your files; the technical architecture below and in the Zero-access architecture guide sets out exactly why that guarantee holds.

09

Copilot readiness without the oversharing risks

Public bodies are, rightly, cautious about Copilot rollouts. The prospect of an AI assistant surfacing safeguarding case notes, sealed correspondence or personnel-sensitive material into an unrelated staff conversation is exactly the failure mode nobody in public-sector IT can absorb. Freedom-of-information regimes add another layer of scrutiny.

Cloud Drive Mapper is what moves the content off the file server and into SharePoint, where Copilot can eventually reach it, and it does so on a schedule where you retain full control over what becomes indexable when. The companion oversharing-remediation work described in the Copilot oversharing patterns guide matters especially in a public-sector context; CDM makes it possible to do that work on Microsoft 365 storage rather than parallel to a file-server migration.

Start a 30-day free trial Read the zero-access architecture guide →

Frequently asked questions

Does Cloud Drive Mapper work with Microsoft 365 Government (GCC and GCC High)?

Yes. Cloud Drive Mapper is tenant-agnostic. It authenticates against whichever Microsoft 365 tenant you point it at, including US Government cloud tenants (GCC and GCC High) and EU data-residency tenants. Your data stays inside your chosen cloud boundary throughout; CDM simply presents the storage in that tenant as a drive letter on the endpoint.

Can we run Cloud Drive Mapper without a VPN?

Yes. Cloud Drive Mapper works directly over the internet using Microsoft Graph. There is no VPN back to a file server, no persistent local cache, and no additional network middleware to deploy. Homeworkers, depot staff and satellite offices get the same file experience as head office over the same internet connection they already have.

Does IAM Cloud have access to our citizen or resident data?

No. Cloud Drive Mapper operates purely with delegated permissions inside your Microsoft 365 tenant. IAM Cloud holds no credentials that would authenticate to your tenant. Only your own signed-in users can access your content through CDM, and only within their own existing M365 permissions. If IAM Cloud's cloud systems were compromised, an attacker would not, as a result, gain access to your data. Full technical detail is in the Zero-access architecture guide.

What happens to our existing shared drive permissions when we move to Cloud Drive Mapper?

Shared drive permissions map onto SharePoint permissions during migration. Cloud Drive Mapper then presents those SharePoint permissions back through the drive-letter interface, so staff see and access exactly the folders they always did. Existing NTFS-style access-control logic translates cleanly onto SharePoint's site-level and library-level permission model.

Can Cloud Drive Mapper help us close a server room?

Yes; this is one of the most common reasons councils and agencies deploy Cloud Drive Mapper. Once the file estate has moved to Microsoft 365 through CDM, the file servers, backup appliances and DR chain those files depended on can be decommissioned. Whether the room comes back for another purpose or gets closed entirely is your decision; CDM removes the file-server dependency that used to keep it open.