Microsoft Azure in Princeton North, NJ

Related, and in most firms, confused — the inventory separates them: Microsoft 365 is the tenancy behind your email, documents and collaboration; Azure is the platform of servers, databases and applications that can run beneath and beside it. Practices typically find three states coexisting: workloads properly on an Azure subscription the firm owns; resources billing under subscriptions nobody remembers opening (a project, a trial, a departed associate); and material on a vendor’s Azure, under the vendor’s tenancy and terms. The map prices each state and the programme consolidates them into one estate in the firm’s name — most firms discover they were paying Azure rent already; they were simply not receiving the estate.

It is a custody arrangement that should be chosen rather than inherited — and examined either way: whose tenancy holds the material, under what export and exit terms, with what access, and at what price of departure. Where the vendor’s platform is genuinely the right home, the programme’s work is to formalise it — terms read and recorded in the register, the firm’s export rights confirmed in writing, the access governed. Where it is not, the archive is brought home in a verified wave like any other workload. The unacceptable state is the common one: the firm’s most sensitive historical material held under terms nobody at the firm has ever read.

By construction and by audit, together: the landing zone’s policy means new resources can only be created inside the firm’s structure, tagged to their purpose and owner — nobody’s credit card can start a new estate again; commitments and sizes are set from measured use rather than estimates; and the monthly review itemises the meter, names the idle and the oversized, and closes or right-sizes them with the partners’ sight. The first audit typically recovers the sprawl’s waste (forgotten test estates running at production prices are the type specimen); the standing discipline then keeps the bill growing only where the firm has decided it should.

Named people, to named things, under review: identity is the estate’s centre — individual accounts, access bounded by role and, where the obligation requires, by matter; administrative rights held sparingly and logged; joiners and leavers processed against the register so one departure closes the platform as it closes the office. The posture is measured against its baseline on cycle and the evidence kept, so the answer to a client’s or an insurer’s question is producible rather than asserted. This is the same access discipline the practice applies to its files, extended to the ground the files now live on.

That is its designed purpose here: the practice system re-homed or integrated under the firm’s policy, and the firm’s own applications — the portal, the internal tools — built on the platform its identity already governs, instead of on a separate host with separate rules. The data and AI layer above it is where the partners feel it: reporting that assembles itself from the systems, and the drafting and research instruments running on the firm’s own material under its own keys — the cloud programme and the AI programme meeting on ground the firm owns. Placements are decided per workload in the design, with the reasoning written; nothing is moved to Azure for fashion.

The estate is designed for the day, not in denial of it: the critical working set architected with an agreed recovery order, backups held independently of any single service’s health, restoration rehearsed on schedule so the procedure is known, and the firm’s practical fallback (the day’s matters available read-only where the partners want them) part of the design conversation. What is never sold is a percentage: the commitment is a tested procedure with named responsibilities and evidence it works — the same standard the practice’s own disaster recovery is held to, and the only version of the promise a client should be given.

In three visible parts: the platform rent itself, at your measured use, audited monthly with waste named — you see the same meter we do; the consolidation and build, priced per wave from the map with the proving discipline inside; and the management as the standing line that keeps identity, policy, posture and costs governed as the firm changes. The map usually funds its own engagement from the sprawl’s recovered waste, and the report says so in figures when it does. No commitment device (reserved capacity and the like) is bought until its pattern is proven — the meter is fitted to the firm, never the firm to the meter.