Anonymised ITFR client case study. The client name and identifying details have been changed for confidentiality.
ITFR began supporting this Australian legal practice when it had two lawyers. As the firm grew to 27 lawyers, the technology that had worked for a very small team became harder to manage. Ageing servers, local Exchange, mapped drives and remote access all needed to evolve without interrupting active matters, email or client service.
The problem was operational risk, not just old hardware
The servers were approaching end of support, backups depended on a narrow maintenance window and several applications used the same identity credentials. Staff worked around file-locking problems by creating local copies, which made version control and matter confidentiality harder to manage.
We mapped applications, mail flow, file ownership, permissions, internet dependencies and recovery requirements before choosing a destination. The aim was not to copy every old habit into the cloud. It was to preserve the working legal process while removing avoidable infrastructure risk.
A security baseline that grew with the firm
When the practice was small, we used SMB1001 as a practical baseline for controls such as multi-factor authentication, patching, backups and secure administration. As the firm grew, we mapped the evolving environment against CIS Controls and the risks that mattered to a legal practice. The purpose was to guide decisions and evidence improvement, not to imply certification.
The target design used Microsoft Entra ID, Exchange Online, SharePoint, OneDrive and managed endpoints. Matter access followed role and team membership instead of inherited drive permissions that nobody could confidently explain.
How the ITFR stack was implemented
We moved mail to Exchange Online, personal working files to OneDrive and shared matter content to structured SharePoint libraries. Microsoft Entra ID became the identity layer, with multi-factor authentication and Conditional Access. Managed Windows devices were brought into Microsoft Intune for encryption, configuration, update and compliance policies, with endpoint protection and managed Microsoft 365 backup added to the operating stack.
Implementation methodology
- Inventory mailboxes, aliases, applications, file shares, permissions and recovery requirements before changing production.
- Create the Microsoft 365 tenant baseline, verified domains, Exchange Online mail flow, Entra ID roles and separate administrative accounts.
- Build SharePoint matter libraries and Entra ID access groups, then test permissions with representative legal, finance and administration users.
- Enrol pilot devices in Intune and validate encryption, update rings, compliance policies, endpoint protection and Conditional Access behaviour.
- Migrate mailboxes in controlled waves, pre-stage frequently used files and keep coexistence and rollback steps available during each change window.
- Validate Microsoft 365 backup jobs and complete sample mailbox, OneDrive and SharePoint restores before retiring the local platform.
We piloted with a partner, a paralegal, finance and administration. Their feedback changed folder mapping, Outlook profiles and the support notes before the wider rollout. Short, role-specific sessions replaced a generic training day, and floor support was available during the first mornings after cutover.
The business result
The firm retired local Exchange and legacy infrastructure services, reduced dependence on after-hours server maintenance and gained consistent sign-in and device controls. As the practice grew from two to 27 lawyers, new starters could be provisioned from role templates rather than a handwritten checklist. Matter teams collaborated on one controlled copy, while version history reduced routine restore requests.
The commercial benefit came from replacing unpredictable hardware events with a planned operating model. More importantly, the practice could keep working during an office outage because identity, mail and current matter files were no longer tied to one server room.
