Case studies

From a full Microsoft cloud modernisation for Worth's Motor Services, to a temporary remote-access arrangement that kept a 25-year-old bespoke application running when it could not be moved at all.

Jump to: Cloud modernisation · Temporary cloud access for a legacy application

Case study 1

Worth's Motor Services — Microsoft Cloud Modernisation

Worth's Motor Services Ltd, trading as Worth's Coaches, is a family-run coach operator based in Enstone, Oxfordshire. Established in 1922, the business provides private coach hire and school contract services. When Latchman Consulting took over the environment, the organisation relied on a business-critical physical server located on the ground in the back office, creating a genuine single point of failure.

A Worth's Coaches vehicle parked outside Blenheim Palace, Oxfordshire
Worth's Coaches at Blenheim Palace. Photo courtesy of Worth's Motor Services Ltd, reproduced with permission.

The challenge

The server in the back office ran the business-critical line-of-business application and its SQL database alongside on-premises Active Directory. If it failed, the business lost access to the systems it runs on.

Remote access was unreliable. VPN connectivity was not working properly when Latchman Consulting took over the environment, and remote and hybrid workers needed dependable access to business systems.

Microsoft 365 was already licensed but not being used efficiently. The organisation held more licences than it needed, and services already included in the subscription, including SharePoint, were not being used.

The outcome

  • Reduced dependence on on-premises infrastructure
  • Improved remote access
  • Simplified cloud architecture
  • Better Microsoft 365 administration
  • Better identity management
  • More effective use of Microsoft 365 licensing
  • SharePoint introduced where it had previously not been used
  • Reduced unnecessary cloud overhead
  • A clearer path toward a cloud-first environment

The solution

Latchman Consulting began modernising the environment: moving suitable workloads into Azure, improving remote connectivity, managing Microsoft 365 and identity, introducing SharePoint, and simplifying the underlying cloud and network infrastructure. For the technically minded, the work involved:

  • Migrated on-premises workloads to Microsoft Azure
  • Hosted the line-of-business application and SQL workload in Azure
  • Configured and managed hybrid identity using Microsoft Entra Connect
  • Diagnosed and resolved identity synchronisation issues
  • Implemented secure connectivity for office, hybrid and remote workers
  • Simplified Azure networking
  • Reduced unnecessary Azure infrastructure and cost, an ongoing effort
  • Took on management of Microsoft 365 users, licences and administration
  • Began rationalising Microsoft 365 licensing, which continues
  • Introduced practical SharePoint use within the organisation
  • Integrated business applications with Microsoft 365 where appropriate
  • Security managed as part of the environment
  • Automation used where appropriate
  • Ongoing Microsoft infrastructure and cloud consultancy
Case study 2

Temporary Cloud Access for a 25-Year-Old Bespoke Transport Application

A passenger transport operator depended on a bespoke business application that had been in use for around 25 years and was still running on a legacy laptop.

The challenge

The application was custom-built, business-critical and running on a single ageing laptop. If that machine failed, the business lost the application.

Latchman Consulting first attempted to move the application onto newer infrastructure, but a clean redeployment was not practical. Parts of the original installation process were no longer available, including missing setup files and legacy dependencies, so the application could not simply be reinstalled elsewhere.

The outcome

  • Reduced dependence on a single physical device
  • Improved continuity for a business-critical legacy application
  • Authorised staff able to access the application remotely
  • Avoided forcing an unreliable migration
  • Bought the business time to consider longer-term options

The solution

Rather than risk disrupting a business-critical application, a temporary Azure Virtual Desktop solution was implemented around the existing working environment. The application itself was not modernised; the aim was preventative as well as operational.

This reduced reliance on the original physical laptop and allowed authorised staff to access the application remotely from different locations during a busy operational period. The arrangement was intentionally temporary and pragmatic, giving the business continuity now and time to decide what replaces the application in the longer term.

Similar situation?

If your organisation depends on an ageing server, a legacy application or remote access that is not working well, read how we work with transport operators or tell us what is not working.