Build on Azure and the Microsoft stack

Could we build new infrastructure on Azure and the Microsoft stack? The phase tested the viability of moving to the cloud by trialling the move on an independent process.

We investigated the "all-in with Microsoft" option. This included restoring the Myriad database to an Azure database using the migration assistant to test compatibility, and exploring Azure Storage, Data Factory pipelines, and SQL Managed Instances.

Moving entirely to Microsoft Dynamics 365 and the Power Platform would cause significant disruption and require rebuilding the team's knowledge from scratch. More critically, the Myriad database had missing indexes and primary keys, causing data integrity issues in Azure, a fundamental compatibility blocker.

We discounted the wholesale Microsoft cloud migration. The costs were too high, and the timeframe was unrealistic given the requirement to simultaneously run business as usual. The legacy database issues compounded the problem, this was not a path we could realistically take without a complete rebuild of Myriad itself.