Genesys Cloud CI/CD with Azure DevOps.

Trigger InProd changeset validation and deployment from Azure Pipelines — with multi-stage pipeline orchestration, environment approval checks, Simulate Run before every stage, and deployment evidence at every step of your Genesys Cloud Azure DevOps pipeline.

↗ Schedule a Demo ↗ Book a Consultation

Genesys Cloud Azure DevOps Pipelines CI/CD with InProd

Trusted By Top Companies Worldwide

Step-by-step implementation guide

How to build Genesys Cloud CI/CD with Azure DevOps and InProd — pipeline templates, environment approval checks, validation, and rollback strategy.

Read the Guide →

How It Works

Three steps from a reviewed change to a recorded production deployment.

Define changes as an InProd changeset

Package your Genesys Cloud configuration changes — routing flows, queue definitions, skill mappings, data actions — into governed deployment units managed in InProd and triggered from your Azure DevOps repository.

Validate on every pull request

Automatically trigger a validate-only pipeline run on every PR. InProd runs Simulate Run against the target environment and reports exactly what would change — before anything is merged.

Promote through Dev, UAT, and Production with approval gates

Use Azure DevOps environment approval checks to require explicit sign-off before each stage. InProd handles environment-aware variable mapping and deployment execution; Azure governs who can approve.

What You Get

PR-triggered validation

Every Genesys Cloud configuration change is automatically verified against the live target environment as part of your Azure DevOps pull request review — not after it reaches production.

Environment approval checks

Map InProd environments to Azure DevOps environments. Set approval and check policies — InProd executes only after designated approvers confirm the stage.

Simulate Run before each environment

InProd executes a pre-deployment simulation showing exactly what will be created, updated, or deleted — including environment-specific differences invisible to a standard diff.

Pipeline artifact for deployment evidence

inprod-result.json is published as a named pipeline artifact after every run, providing an immutable deployment record downloadable from Azure DevOps.

Rollback from pipeline or InProd UI

Revert to a previous state using InProd's point-in-time restore — without manual reconstruction of what the configuration was before the change.

Works With Your Existing Azure DevOps Setup

No custom infrastructure required. InProd integrates via a published Azure Pipelines step template referenced directly from the inprod/run-changesets repository. Your existing pipeline variable groups, service connections, branch policies, and environment approval rules all apply — InProd adds Genesys Cloud-specific validation and deployment governance on top of the pipeline you already run.

This makes it straightforward to add CX as Code deployments to an Azure DevOps workflow your team already understands.

New to the InProd pipeline model? See how the five-stage Genesys Cloud CI/CD pipeline works →

azure-pipelines.yml

resources:
  repositories:
    - repository: inprod_templates
      type: github
      name: inprod/run-changesets
      ref: refs/tags/v1.0.0
      endpoint: your-github-service-connection

variables:
  - group: inprod-credentials

stages:
  - stage: Validate
    jobs:
      - job: ValidateChangesets
        steps:
          - template: templates/azure-pipelines-run-changesets.yml@inprod_templates
            parameters:
              changesetFile: changesets/*.yaml
              validateOnly: true

  - stage: DeployUAT
    dependsOn: Validate
    jobs:
      - deployment: DeployUAT
        environment: UAT
        strategy:
          runOnce:
            deploy:
              steps:
                - template: templates/azure-pipelines-run-changesets.yml@inprod_templates
                  parameters:
                    changesetFile: changesets/*.yaml
                    environment: UAT

  - stage: DeployProd
    dependsOn: DeployUAT
    jobs:
      - deployment: DeployProd
        environment: Production
        strategy:
          runOnce:
            deploy:
              steps:
                - template: templates/azure-pipelines-run-changesets.yml@inprod_templates
                  parameters:
                    changesetFile: changesets/*.yaml
                    environment: Production

Azure DevOps vs GitHub Actions vs Jenkins

InProd runs the same governed Genesys Cloud deployment workflow on every platform. The right choice depends on where your team already works.

Azure DevOps

You are here

Best fit for enterprise teams standardized on the Microsoft/Azure ecosystem. Multi-stage pipelines with environment approval checks, Azure AD integration, service connections, and variable groups all apply — InProd adds the Genesys Cloud deployment layer on top.

Multi-stage pipelines with environment approval checks
Secret variable groups for credential management
Published step template — no custom infrastructure

GitHub Actions

Best fit when changeset files live in a GitHub repository. PR-native review workflow, protected environment approval gates, and the InProd action published on the GitHub Marketplace — no extra tooling or custom runners required.

PR-triggered validation native to GitHub
Protected environments enforce approval before production
Marketplace action — no custom infrastructure

GitHub Actions integration guide →

Jenkins

Best fit for teams with existing self-hosted Jenkins infrastructure who need fine-grained agent control. Runs via npx in any pipeline stage — NodeJS Plugin or Docker agent — with input-gated promotion and archived deployment artifacts.

Self-hosted — full control over agents and execution environment
Input-gated approvals between stages
Works with NodeJS Plugin or Docker agents

Jenkins integration guide →

Compare all six CI/CD integrations →

Frequently Asked Questions

Why use Azure DevOps for Genesys Cloud deployments instead of manual promotion?

Manual promotion relies on engineers replicating the same steps correctly across Dev, UAT, and Production every time. Azure Pipelines enforces the same process on every release — validation runs automatically, environment approval checks require explicit sign-off before production, and every deployment generates a pipeline artifact record. The pipeline removes the process variability that causes most configuration-related incidents.

How do Azure DevOps environment approval checks work with InProd?

You configure approval and check policies on your Azure DevOps environments under Pipelines → Environments → Approvals and checks. When a stage targets that environment, Azure requires the designated approvers to confirm before the deployment step executes. InProd then runs Simulate Run and deploys the changeset within that approved stage.

What is the difference between Azure DevOps and GitHub Actions for Genesys Cloud?

Both platforms run the same InProd changeset execution and produce the same Dev to UAT to Production promotion flow. Azure DevOps is typically preferred by enterprise teams with existing Microsoft infrastructure, Azure Active Directory integration, or compliance requirements tied to the Microsoft ecosystem. GitHub Actions is the right choice for teams already standardized on GitHub. The InProd deployment behaviour is identical across both.

Does this work with CX as Code and Terraform?

Yes. InProd sits alongside your CX as Code and Genesys Cloud Terraform workflows. Terraform manages desired-state definitions; InProd governs the deployment lifecycle — Simulate Run, promotion gates, drift detection, and the audit trail. Azure Pipelines can trigger both Terraform applies and InProd changeset deployments within the same stages.

Need the full pipeline picture? Genesys Cloud CI/CD Pipeline →

Your Genesys Cloud Azure DevOps Pipeline, Governed.

Every configuration change validated before it merges, approved through Azure DevOps environment checks, and recorded as a pipeline artifact — before the next incident forces the issue.

Book a Consultation