Reduction of costs and dependencies in critical integrations in the insurance sector

The insurer maintained essential processes and APIs operating outside its own infrastructure, and with an iPaaS not approved within the insurer's architectural ecosystem, which represented a strategic opportunity for internalization and greater governance. The main points of attention were:

• Operation on an external platform: critical processes for contracting, cancellation, claims, enrollment, and fraud prevention operated entirely on a third-party iPaaS, which motivated the search for greater autonomy and control over its own operations.

• Opportunity for greater traceability: the evolution of compliance and audit requirements demanded more robust logs and trails, especially in sensitive regulatory journeys.

• Complexity of business rules: 11 processes and APIs concentrated sophisticated data transformations, integrations with legacy systems, and conditional logic specific to each type of operation — all of this needed to be fully preserved in the migration.

• High operational criticality: the reliability of contracting and claims APIs allowed no room for error, given the direct impact on the end customer experience and the insurer's reputation.

Squadra conducted the migration to Azure API Management (APIM) and Azure Functions with Genius acting as an accelerator in all phases — from discovery to deploy. The approach ensured the full preservation of business rules and operational continuity throughout the transition.

Genius in action: API Gateway Portability with Azure

Discovery: Mapping and Inventory of Integrations

The insurer identified the need for a consolidated view of its integrations. Genius supported the mapping of the 11 existing processes and APIs, making visible what was dispersed or not yet centralized — system dependencies, points of attention, and critical business rules.

• Dependency mapping: identification of all calls between legacy systems, conditional logic, and data transformations in each process.

• Integration inventory: documentation of the 11 processes and APIs with their business rules, operation types, and security requirements — the basis for a structured and predictable migration.

Design: Target Architecture on Azure

With the map in hand, the target architecture on Azure was designed. Decisions that normally emerge during the build phase were anticipated and formalized at this stage, increasing project predictability and efficiency.

• Azure API Management (APIM): definition of policies for exposure, authentication, rate limiting, and versioning for all migrated APIs.

• Serverless architecture: modeling of schedulers as Azure Functions with paginated processing and state control. Formalized SLAs: REST within 5s for 95% of calls and Functions within 500ms.

Build: Implementation and Observability

The implementation went beyond technical translation — it preserved all the business complexity of critical APIs and provided the insurer with the necessary operational visibility for more robust management.

• Application Insights: structured logging, response time metrics, error rates, and throughput for at-a-glance operational management.

• Resilience mechanisms: idempotency, reversibility, and rollback plans incorporated into critical APIs from the start, with bi-weekly checkpoints and a technical governance committee.

Deploy: CI/CD Pipeline and Governance

The pipeline was structured to ensure that only validated code reached production, with automatic blocking of critical vulnerabilities and guaranteed availability during business hours without additional cost impact outside peak times.

• CI/CD pipeline with Fortify: integrated SAST/DAST analysis with automatic blocking for high criticality issues.

• API lifecycle management: formalized versioning and deprecation process with operations teams, ensuring controlled transitions.

The migration to Azure went beyond technological modernization: it represented a strategic business decision with immediate returns.

The quality of the delivery was an important item highlighted by the insurer, as it reduced the homologation time and brought confidence in the solution's implementation.

By internalizing critical integrations into the Azure infrastructure already contracted by the insurer, the project generated direct operational cost reductions without new infrastructure contracts, while delivering greater control, traceability, and resilience over the most sensitive business journeys: contracting, cancellation, claims, enrollment, and fraud prevention.

With 11 critical integrations migrated in 12 sprints, the insurer now operates on its own governed and scalable platform, ready to support business growth securely.

Technologies Used