A vehicle data center connects to a cloud platform, where teams monitor connected-car services and analytics.
South African insurer The Unlimited has moved its core insurance platform off an on-premises monolith and onto a microservices architecture on Microsoft Azure. The migration was done with Cygnet.One, a technology services firm that has now published the project as a named customer case study. The announcement went out on GLOBE NEWSWIRE on September 30, 2026. It includes something vendor case studies often leave out: the actual Azure components, and a description of how the old and new systems were run side by side during the move.

Before we go further, a caveat. Every source on this story comes from Cygnet.One: the press release, its customer case study and a September 16 blog post on its own site. No outside party has audited the results. The company publishes no release-frequency numbers, uptime figures, cost savings or migration timeline. Read the outcomes below as the vendor's claims. The architecture is where the useful material is.

Who's Involved​

The Unlimited was founded in 1994. Cygnet.One says it covers more than three million people through insurance and annuity products sold through analogue and digital channels. The case study lists death, accident, vehicle and health cover, underwritten by insurance companies. The firm also handles the full claims process and works with several claim assessors.

Cygnet.One was founded in 2000. It describes itself as a global modernization firm working across digital and cloud engineering, data and AI, quality engineering, managed IT, cybersecurity, SAP and enterprise automation.

The two companies have worked together for years. According to Cygnet.One, the relationship started with one mobile development project and later grew to include:

  • Machine learning
  • Business intelligence
  • Microsoft Dynamics 365 work
  • The core platform modernization covered here

Section summary: The customer is a mid-sized insurer with a large policyholder base. The vendor is a long-standing partner, not a new supplier. That history helps explain how the project could start with deep discovery work.

What They Were Replacing​

Cygnet.One's case study describes a familiar legacy setup. The core application had become a tightly coupled monolith, so even small changes were slow and risky. There was little documentation, which left the team relying on "tribal knowledge," and new engineers took longer to become productive. Several business processes were still manual. The application ran on on-premises hardware that was expensive to maintain and limited how far the system could scale. Years of technical debt, including outdated technologies and non-standard implementations, made things worse.

If you've managed a line-of-business app that nobody wants to touch on a Friday afternoon, this will sound familiar.

The Target Architecture on Azure​

The case study lists the technology stack as Microsoft Azure, Azure Kubernetes Service, RabbitMQ, .NET, Microsoft Dynamics 365 and Azure SQL. Here is what each component does:

ComponentRole in the platform (per Cygnet.One)
Azure Kubernetes Service (AKS)Hosts the independent microservices
Azure Application GatewayRouting and authentication
RabbitMQAsynchronous messaging between services, plus CRM synchronization
Microsoft Dynamics 365 CRMIntegrated into the platform
Azure SQLPart of the cloud data layer
Azure Monitor, Application Insights, centralized loggingVisibility into system health

The monolith was split along business lines rather than technical layers. There are separate services for:

  • Product
  • Collections
  • Communications
  • Customer management
  • Lead management

Each service has a single responsibility. In Cygnet.One's architecture diagram, mobile, web and CRM requests come in through a cloud API gateway and are routed to the right service on the container platform. Each service has its own database. The vendor also says the underlying cloud infrastructure and deployment pipeline are secured and managed separately from the client-facing applications.

Two design choices stand out:

  • RabbitMQ instead of direct service calls. If services call each other synchronously, you can end up with a distributed monolith that has all the old coupling plus network latency. Cygnet.One's blog makes the same point. Asynchronous messaging lets services exchange data without waiting on each other.
  • Observability built in from the start. Once one application becomes many services, a single failed request can pass through several of them. Without Application Insights and centralized logs, tracing a production problem gets much harder.

Section summary: The stack is a fairly standard Microsoft-centric pattern: AKS, Application Gateway, Azure SQL and Dynamics 365, with open-source RabbitMQ for messaging. The notable part is that services follow business functions and that messaging and monitoring were part of the design from day one.

How They Moved It​

For IT pros, the migration method matters more than the list of products. According to Cygnet.One:

  1. Discovery before code. Documentation was thin, so the team first worked with business users to understand how processes actually ran at an operational level. This happened before any new code was written.
  2. Phased build. Work moved from the base architecture, to individual microservices, to integrating them into a single system.
  3. Coexistence. For much of the build, the legacy and new systems ran side by side and exchanged data while functions moved across. The vendor says this took careful technical planning.

Cygnet.One doesn't use the term, but this closely matches what Microsoft's Azure Architecture Center calls the Strangler Fig pattern. Microsoft describes it as a controlled and phased approach to modernization. It allows the existing application to continue functioning during the modernization effort. In Microsoft's version, a façade (proxy) intercepts requests that go to the back-end legacy system. The façade routes these requests either to the legacy application or to the new services. Then, as you migrate functionality to the new system, the legacy system becomes obsolete, and you decommission the legacy system.

We don't know whether The Unlimited's Application Gateway acted as that routing façade during the transition. The sources don't say how traffic or data was split between the two systems. Microsoft's guidance does raise an operational risk anyone copying this approach should plan for: make sure the façade doesn't become a single point of failure or a performance bottleneck. Microsoft also lists cases where the pattern is a poor fit, including when you migrate a small system and replacing the whole system is simple, or when you need to decommission the original solution quickly.

What the Vendor Says Changed​

Cygnet.One reports three outcomes:

  • Offline data capture. Field and sales staff can record policy information without an internet connection. The data syncs automatically once they're back online. In a market where mobile coverage varies, this is probably the most practical user-facing gain.
  • Digital workflows. Manual and paper-based processes are now supported by digital tools.
  • Room to grow. The vendor says the platform is "built to accommodate" customer growth, unlike the fixed capacity of the old on-premises system.

CIO Sean Peatt's statement is upbeat, as you'd expect in a press release. He said modernizing the core platform "has given us a foundation that can scale with our growth," while also supporting new digital experiences and faster responses to changing requirements.

Keep in mind what hasn't been published. There are no figures on release cadence, availability, cost, transaction volume or concurrent users. The three-million figure is the insurer's policyholder base, not a measured load on the new platform. The sources also say nothing about Azure regions, data residency, encryption, backup and disaster recovery, autoscaling or regulatory controls. Those are exactly the topics a regulated insurer's auditors would ask about.

Why It Matters to Azure and Enterprise IT Readers​

This is not a Microsoft product announcement, but it is a useful reference architecture for teams in the Microsoft ecosystem facing a similar legacy core. Some takeaways, based on general industry practice rather than claims in the case study:

  • Split by business capability, not by database table. Decomposing a monolith without understanding its business behavior usually just spreads the complexity across more pieces.
  • Budget for the transition architecture, not only the end state. Running old and new systems together, with data flowing both ways, is often the hardest engineering work. It's also where timelines slip.
  • Plan Dynamics 365 integration early. Here the CRM is synced through the messaging layer instead of being added afterward. That is a sensible pattern for organizations already using Dynamics.
  • Treat observability as required. On AKS, Application Insights and centralized logging are what let you debug a distributed system at 2 a.m.
  • Consider the cost of running more infrastructure. Microservices on Kubernetes, plus a self-managed or hosted RabbitMQ broker, mean more components to patch, monitor and staff than a single application server. The case study doesn't discuss how The Unlimited handles this.

Does all of this prove the phased approach is safer than a big-bang cutover? Not in this case, because no incident or downtime data has been published. What the case study does show is a coherent, clearly described path from an undocumented monolith to Azure-native services, and that the two companies are still building on the same architecture instead of starting over.

For WindowsForum readers interested in related topics, AKS operations, Application Gateway configuration, Dynamics 365 integration patterns and Azure Monitor/Application Insights setup all come up regularly in our Azure and enterprise IT discussions.

 

References

  1. Cygnet.One and The Unlimited Modernize Core Insurance Platform on Microsoft Azure - The Manila Times The Manila Times 2026-09-30T06:53:22+00:00
  2. Modernized Legacy Insurance Platform to Cloud-Native Architecture cygnet.one
  3. How The Unlimited Went Monolith to Microservices on Azure cygnet.one