Microsoft Commercial and Professional Services global Company newsroom

Infosys

Application Refactoring

Infosys wanted to move beyond basic AI augmentation in the software development life cycle because developers still had to manually review, validate, integrate, and fix generated code in large enterprise applications, limiting productivity and increasing delivery risk.

Creating end-to-end unit test cases took about 45 minutes with AI assistance, compared to a couple of weeks it would have required manually.
Migrating Oracle database views to SQL views was completed in just 10 minutes instead of the approximately three days usually needed.
between 60% and 70% improvement in generating application programming interfaces (APIs) and microservices
between 80% and 90% improvement in database code generation

Reported impact

Business outcome

Infosys reports materially faster software development and modernization work, including higher productivity in database code generation, API and microservices creation, user interface generation, unit-test creation, database-view migration, and application dependency upgrades, while using iLEAD guardrails to keep generated code aligned with enterprise standards.

  • Productivity Improvement
  • Speed to Market

Solution

Infosys uses GitHub Copilot agent mode as the execution layer for software-development work across enterprise applications and its own IP products and platforms. Architects and developers feed the agent detailed context such as tech-stack information, business rules, user stories, coding standards, prompts, and rule sets so it can plan multistep tasks, generate code, suggest terminal commands, inspect runtime errors, and iterate on its own output through self-reflection. Infosys then wraps this workflow with its iLEAD platform, an AI-first, agent-integrated SDLC environment that supports requirements definition through release management and adds guardrails for maintainability, security, and enterprise standards. Infosys is also developing model context protocol servers inside iLEAD to bridge agents to external systems and expose tools such as databases, design patterns, and industry- or technology-specific endpoints, so generated changes can be better integrated, reviewed in smaller chunks, and handed off across architect, developer, and DevOps roles.

Data flow

Tech-stack details, business rules, user stories, coding standards, and prompts are provided to GitHub Copilot agent mode as context. The agent works against the existing code base, terminal, and operating system, iterating on generated code and runtime errors. Within iLEAD, model context protocol servers expose databases and design-pattern resources, and reviewed output then moves through SDLC and release-management workflows for architects, developers, and DevOps teams.

Solution architecture

3 components · 2 layers
  1. Serving
    • GitHub Copilot agent mode Acts as the coding agent that plans tasks, generates code, suggests terminal actions, analyzes runtime errors, and iterates on its own output.
  2. Orchestration
    • iLEAD platform Provides the agent-integrated SDLC environment and guardrails from requirements definition to release management.
    • model context protocol servers Bridge AI agents to external systems and expose databases, design patterns, and domain-specific endpoints as tools.

Architecture clues

  • Infosys says it has adopted GitHub Copilot at scale.
  • Model context protocol servers are being developed inside iLEAD to expose industry-specific and technology endpoints.
  • Tests covered C#, Java, HTML, CSS, Angular, React, Vue.JS and SQL.
  • The agent is described as iterating against its own output, runtime errors, the terminal, the OS, and the code base.
  • iLEAD is described as an AI-first, agent-integrated platform spanning requirements definition to release management.

Evidence from the source

According to our analysis, which includes experiments from both senior architects and junior developers at Infosys, agent mode can achieve between 80% and 90% improvement in database code generation; between 60% and 70% improvement in generating application programming interfaces (APIs) and microservices; and up to 60% improvement in generating user interface code.
At Infosys we have adopted GitHub Copilot at scale and its agent mode is particularly exciting.
Creating end-to-end unit test cases took about 45 minutes with AI assistance, compared to a couple of weeks it would have required manually.
Migrating Oracle database views to SQL views was completed in just 10 minutes instead of the approximately three days usually needed.
The platform ensures that the agent-generated code adheres to best practices, incorporates strong security measures, and is straightforward to maintain.
This agent is capable of iterating on its own code, understanding its own errors, and then fixing them itself through self-reflection.
To facilitate this, we are also developing model context protocol servers — software components that act as bridges between AI agents and external systems — within the iLEAD platform, providing tools and resources for agents.
To help in this, Infosys leverages the iLEAD platform. This is an AI-first, agent-integrated platform providing end-to-end SDLC assistance tailored for key personas including architects, developers, and DevOps teams, supporting the journey from requirements definition to release management.
Transparency Evidence & methodology 100/100 reference value · 94% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    6 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence94%
  • Source authority25/25
    The deployment is described by the adopting organization or a government source.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    8 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Infosys

    Infosys customer story

    First-party
    https://www.infosys.com/iki/perspectives/agentic-ai-software-development.html
    Source type
    Customer-published story
    Published
    Jun 3, 2025
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Jun 3, 2025 · Infosys · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.