{"id":2372,"date":"2025-08-13T18:29:24","date_gmt":"2025-08-13T18:29:24","guid":{"rendered":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2025\/08\/13\/azure-developer-cli-from-dev-to-prod-with-azure-devops-pipelines\/"},"modified":"2025-08-13T18:29:24","modified_gmt":"2025-08-13T18:29:24","slug":"azure-developer-cli-from-dev-to-prod-with-azure-devops-pipelines","status":"publish","type":"post","link":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2025\/08\/13\/azure-developer-cli-from-dev-to-prod-with-azure-devops-pipelines\/","title":{"rendered":"Azure Developer CLI: From Dev to Prod with Azure DevOps Pipelines"},"content":{"rendered":"

Building on our previous post<\/a> about implementing dev-to-prod promotion with GitHub Actions, this follow-up demonstrates the same \u201cbuild once, deploy everywhere\u201d pattern using Azure DevOps Pipelines. You\u2019ll learn how to leverage Azure DevOps YAML pipelines with Azure Developer CLI (azd)<\/a>. This approach ensures consistent, reliable deployments across environments.<\/p>\n

Environment-Specific Infrastructure<\/h2>\n

The infrastructure approach is identical to our previous GitHub Actions implementation<\/a>. It uses conditional Bicep deployment with a single envType parameter. This drives environment-specific resource configuration. The same Bicep templates work seamlessly across both CI\/CD platforms.<\/p>\n

For the complete infrastructure setup details, refer to the GitHub Actions post<\/a>.<\/p>\n

From File Backup to Pipeline Artifacts<\/h2>\n

The original approach used local file backups (copying zip files within the same job). However, the community pointed out that using native CI\/CD artifact systems is more idiomatic. This provides several key advantages:<\/p>\n

Cross-job compatibility<\/strong>: Artifacts work seamlessly across multiple jobs and stages.
\nAutomatic cleanup<\/strong>: The platform handles retention policies automatically.
\nBetter traceability<\/strong>: Artifacts are visible in the platform UI with download history.
\nPlatform integration<\/strong>: Native features with built-in security and access controls.<\/p>\n

This artifact-based approach represents the industry standard for \u201cbuild once, deploy everywhere\u201d patterns. It works across modern CI\/CD platforms. We have updated the original GitHub Actions implementation to use the same pattern demonstrated in this Azure DevOps version.<\/p>\n

Azure DevOps Pipeline Enhancement<\/h2>\n

Azure DevOps pipelines require a different approach than GitHub Actions. However, they achieve the same outcome. We\u2019ll demonstrate a multi-stage pipeline<\/strong> that provides proper separation of concerns and enterprise-ready deployment patterns. This staged approach offers better isolation, approval workflows, and traceability compared to single-job pipelines.<\/p>\n

The enhanced pipeline follows a three-stage structure:<\/p>\n

1. Pipeline Structure<\/strong><\/p>\n

The multi-stage pipeline uses separate stages for build, development deployment, and production promotion:<\/p>\n

# Run when commits are pushed to main
\ntrigger:
\n – main<\/p>\n

pool:
\n vmImage: ubuntu-latest<\/p>\n

stages:
\n– stage: build_and_test
\n– stage: deploy_development
\n dependsOn: build_and_test
\n– stage: promote_to_Prod
\n dependsOn: deploy_development<\/p>\n

2. Build and Package Stage<\/strong><\/p>\n

The first stage focuses solely on building and packaging the application for deployment:<\/p>\n

– stage: build_and_test
\n jobs:
\n – job: buildAndPackage
\n pool:
\n vmImage: ubuntu-latest
\n steps:
\n – task: Bash@3
\n displayName: Install azd
\n inputs:
\n targetType: ‘inline’
\n script: |
\n curl -fsSL https:\/\/aka.ms\/install-azd.sh | bash<\/p>\n

– task: PowerShell@2
\n displayName: Configure AZD to Use AZ CLI Authentication.
\n inputs:
\n targetType: inline
\n script: |
\n azd config set auth.useAzCliAuth “true”
\n pwsh: true<\/p>\n

– task: AzureCLI@2
\n displayName: Package Application
\n inputs:
\n azureSubscription: azconnection
\n scriptType: bash
\n scriptLocation: inlineScript
\n keepAzSessionActive: true
\n inlineScript: |
\n mkdir -p .\/dist
\n azd package app –output-path .\/dist\/app-package.zip –no-prompt
\n echo “\u2705 Application packaged successfully”<\/p>\n

– task: PublishPipelineArtifact@1
\n displayName: Upload Package Artifact
\n inputs:
\n targetPath: ‘.\/dist\/app-package.zip’
\n artifact: ‘app-package’
\n publishLocation: ‘pipeline’<\/p>\n

3. Deploy to Development Stage<\/strong><\/p>\n

The second stage provisions development infrastructure and deploys the packaged application:<\/p>\n

– stage: deploy_development
\n dependsOn: build_and_test
\n jobs:
\n – job: deployToDevelopment
\n pool:
\n vmImage: ubuntu-latest
\n steps:
\n – task: Bash@3
\n displayName: Install azd
\n inputs:
\n targetType: ‘inline’
\n script: |
\n curl -fsSL https:\/\/aka.ms\/install-azd.sh | bash<\/p>\n

– task: PowerShell@2
\n displayName: Configure AZD to Use AZ CLI Authentication.
\n inputs:
\n targetType: inline
\n script: |
\n azd config set auth.useAzCliAuth “true”
\n pwsh: true<\/p>\n

– task: AzureCLI@2
\n displayName: Provision DEV Infrastructure
\n inputs:
\n azureSubscription: azconnection
\n scriptType: bash
\n scriptLocation: inlineScript
\n keepAzSessionActive: true
\n inlineScript: |
\n azd provision –no-prompt<\/p>\n

– task: DownloadPipelineArtifact@2
\n displayName: Download Package Artifact
\n inputs:
\n buildType: ‘current’
\n artifactName: ‘app-package’
\n targetPath: ‘.\/artifacts’<\/p>\n

– task: AzureCLI@2
\n displayName: Deploy to Development
\n inputs:
\n azureSubscription: azconnection
\n scriptType: bash
\n scriptLocation: inlineScript
\n keepAzSessionActive: true
\n inlineScript: |
\n azd deploy app –from-package .\/artifacts\/app-package.zip –no-prompt<\/p>\n

4. Validation Gate<\/strong><\/p>\n

Add validation checks before promotion to production:<\/p>\n

– task: AzureCLI@2
\n displayName: Validate Application
\n inputs:
\n azureSubscription: azconnection
\n scriptType: bash
\n scriptLocation: inlineScript
\n keepAzSessionActive: true
\n inlineScript: |
\n echo “\ud83d\udd0d Validating application in development environment…”
\n # TODO: Add actual validation here
\n # Examples:
\n # – Health checks and integration tests
\n # – Security and compliance scanning
\n # – Performance validation
\n sleep 3 # Simulate validation time
\n echo “\u2705 Application validation passed”<\/p>\n

5. Promote to Production Stage<\/strong><\/p>\n

The final stage uses environment-specific variables to deploy to production:<\/p>\n

– stage: promote_to_Prod
\n dependsOn: deploy_development
\n jobs:
\n – job: deployProduction
\n # use prod settings to override default environment variables
\n # this variables become ENV VARS for all tasks in this job
\n variables:
\n AZURE_ENV_NAME: $(AZURE_PROD_ENV_NAME)
\n AZURE_ENV_TYPE: $(AZURE_PROD_ENV_TYPE)
\n AZURE_LOCATION: $(AZURE_PROD_LOCATION)
\n AZURE_SUBSCRIPTION_ID: $(AZURE_PROD_SUBSCRIPTION_ID)
\n pool:
\n vmImage: ubuntu-latest
\n steps:
\n – task: Bash@3
\n displayName: Install azd
\n inputs:
\n targetType: ‘inline’
\n script: |
\n curl -fsSL https:\/\/aka.ms\/install-azd.sh | bash<\/p>\n

– task: PowerShell@2
\n displayName: Configure AZD to Use AZ CLI Authentication.
\n inputs:
\n targetType: inline
\n script: |
\n azd config set auth.useAzCliAuth “true”
\n pwsh: true<\/p>\n

– task: DownloadPipelineArtifact@2
\n displayName: Download Package Artifact
\n inputs:
\n buildType: ‘current’
\n artifactName: ‘app-package’
\n targetPath: ‘.\/artifacts’<\/p>\n

– task: AzureCLI@2
\n displayName: Deploy to PROD
\n inputs:
\n azureSubscription: azconnection
\n scriptType: bash
\n scriptLocation: inlineScript
\n keepAzSessionActive: true
\n inlineScript: |
\n azd deploy app –from-package .\/artifacts\/app-package.zip –no-prompt<\/p>\n

Try It Out<\/h2>\n

You can try this approach using the complete implementation here<\/a><\/p>\n

Watch the walkthrough:<\/p>\n\n

Prerequisites<\/h3>\n

You\u2019ll need a Personal Access Token (PAT) to set up Azure DevOps pipelines with azd. For detailed guidance on PAT creation and pipeline setup, refer to the Microsoft Learn documentation<\/a>.<\/p>\n

Setup Steps<\/h3>\n

1. Initialize Project<\/strong><\/p>\n

azd init -t https:\/\/github.com\/puicchan\/azd-dev-prod-appservice-storage<\/p>\n

Use environment name like projazdo-dev.<\/p>\n

2. Edit azure.yaml<\/strong><\/p>\n

Make sure you configure Azure DevOps as the CICD tool and add these pipeline variables:<\/p>\n

pipeline:
\n provider: azdo
\n variables:
\n – AZURE_PROD_ENV_NAME
\n – AZURE_PROD_ENV_TYPE
\n – AZURE_PROD_LOCATION
\n – AZURE_PROD_SUBSCRIPTION_ID<\/p>\n

3. Set Up Development Environment<\/strong><\/p>\n

azd up<\/p>\n

4. Set Up Production Environment<\/strong><\/p>\n

We will run azd provision and rely on Azure Pipeline to deploy the app to production:<\/p>\n

azd env new projazdo-prod
\nazd env set AZURE_ENV_TYPE prod
\nazd provision<\/p>\n

5. Test the Flow<\/strong><\/p>\n

Switch back to Development:<\/p>\n

azd env select projazdo-dev<\/p>\n

Edit your application code and make sure you run azd env set to configure the following environment variables the pipeline requires:<\/p>\n

AZURE_PROD_ENV_NAME
\nAZURE_PROD_ENV_TYPE
\nAZURE_PROD_LOCATION
\nAZURE_PROD_SUBSCRIPTION_ID <\/p>\n

6. Configure CI\/CD Pipeline<\/strong><\/p>\n

azd pipeline config<\/p>\n

Go to your Azure Pipelines Organization and check out the pipeline run.<\/p>\n

Pro Tip: Enhance Your Pipeline with AI<\/h2>\n

Need help with Azure DevOps and azd? GitHub Copilot for Azure<\/a> with Azure MCP<\/a> can help you enhance your azure-dev.yml file directly in VS Code.<\/p>\n

With the GitHub Copilot for Azure extension installed, and the GitHub Copilot for Azure and Azure MCP tools enabled in Agent mode, GitHub Copilot can:<\/p>\n

Debug pipeline issues<\/strong>: Analyze YAML syntax errors and configuration problems.
\nAdd validation steps<\/strong>: Suggest health checks, security scans, or integration tests.
\nOptimize deployment strategies<\/strong>: Recommend blue-green deployments or canary releases.
\nConfigure environment-specific logic<\/strong>: Help set up conditional steps for different environments.<\/p>\n

Simply ask GitHub Copilot questions like:<\/p>\n

\u201cAdd a health check validation step to my Azure DevOps pipeline\u201d
\n\u201cHow can I add manual approval gates before production deployment?\u201d<\/p>\n

Agent mode with GitHub Copilot for Azure provides contextual understanding of your Azure resources. It can suggest pipeline improvements based on your specific infrastructure setup.<\/p>\n

Conclusion<\/h2>\n

This Azure DevOps implementation demonstrates how the \u201cbuild once, deploy everywhere\u201d pattern translates seamlessly across different CI\/CD platforms. The core azd and Bicep logic remains identical. Meanwhile, platform-specific features like service connections and task definitions provide the Azure DevOps-native experience.<\/p>\n

Whether you choose GitHub Actions or Azure DevOps, the fundamental approach remains consistent. Conditional infrastructure deployment and package promotion ensure reliable deployments across your development lifecycle.<\/p>\n

Questions about implementation or want to share your Azure DevOps approach? Join the discussion here<\/a>.<\/p>\n

The post Azure Developer CLI: From Dev to Prod with Azure DevOps Pipelines<\/a> appeared first on Azure DevOps Blog<\/a>.<\/p>","protected":false},"excerpt":{"rendered":"

Building on our previous post about implementing dev-to-prod promotion with GitHub Actions, this follow-up demonstrates the same \u201cbuild once, deploy […]<\/p>\n","protected":false},"author":0,"featured_media":94,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[3],"tags":[],"class_list":["post-2372","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure"],"_links":{"self":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/posts\/2372","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/comments?post=2372"}],"version-history":[{"count":0,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/posts\/2372\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/media\/94"}],"wp:attachment":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/media?parent=2372"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/categories?post=2372"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/tags?post=2372"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}