{"id":2266,"date":"2025-07-21T16:17:37","date_gmt":"2025-07-21T16:17:37","guid":{"rendered":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2025\/07\/21\/azure-developer-cli-from-dev-to-prod-with-one-click\/"},"modified":"2025-07-21T16:17:37","modified_gmt":"2025-07-21T16:17:37","slug":"azure-developer-cli-from-dev-to-prod-with-one-click","status":"publish","type":"post","link":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2025\/07\/21\/azure-developer-cli-from-dev-to-prod-with-one-click\/","title":{"rendered":"Azure Developer CLI: From Dev to Prod with One Click"},"content":{"rendered":"

This post walks through how to implement a \u201cbuild once, deploy everywhere\u201d<\/strong> pattern using Azure Developer CLI (azd)<\/a> that provisions environment-specific infrastructure and promotes applications from dev to prod with the same build artifacts. You\u2019ll learn how to use conditional Bicep deployment, environment variable injection, package preservation across environments, and automated CI\/CD promotion from development to production.<\/p>\n

Environment-Specific Infrastructure<\/h2>\n

When deploying applications across environments, different requirements emerge:<\/p>\n

Component
\nDevelopment
\nProduction<\/p>\n

Networking<\/strong>
\nPublic access
\nVNet integration + Private endpoints<\/p>\n

Storage<\/strong>
\nPublic with restrictions
\nPrivate endpoints only<\/p>\n

App Service Plan<\/strong>
\nB2 Basic
\nS1 Standard<\/p>\n

Security<\/strong>
\nManaged identity
\nEnhanced network isolation<\/p>\n

Rather than maintaining separate infrastructure templates or complex configuration files for each environment, we can use a single set of Bicep files that adapt based on an environment variable. This approach eliminates infrastructure drift while keeping deployments simple and consistent.<\/p>\n

Set up resources based on an environment variable<\/h2>\n

To conditionally provision resources based on environment type, azd leverages an environment variable AZURE_ENV_TYPE to make decisions at deployment time.<\/p>\n

Behind the scenes, azd passes AZURE_ENV_TYPE to Bicep as the envType parameter:<\/p>\n

@description(‘Environment type – determines networking configuration (dev\/test\/prod)’)
\n@allowed([‘dev’, ‘test’, ‘prod’])
\nparam envType string = ‘dev’<\/p>\n

This parameter then drives conditional resource deployment in Bicep:<\/p>\n

For Network Deployment:<\/strong><\/p>\n

\/\/ Deploy network infrastructure only for production environments
\nmodule network ‘.\/network.bicep’ = if (envType == ‘prod’) {
\n name: ‘networkDeployment’
\n params: {
\n location: location
\n tags: tags
\n abbrs: abbrs
\n resourceToken: resourceToken
\n }
\n}<\/p>\n

Similarly for Storage Configuration:<\/strong><\/p>\n

module storageAccount ‘br\/public:avm\/res\/storage\/storage-account:0.17.2’ = {
\n name: ‘storageAccount’
\n params: {
\n name: storageAccountName
\n allowSharedKeyAccess: false
\n publicNetworkAccess: envType == ‘prod’ ? ‘Disabled’ : ‘Enabled’
\n networkAcls: envType == ‘prod’ ? {
\n defaultAction: ‘Deny’
\n virtualNetworkRules: []
\n bypass: ‘AzureServices’
\n } : {
\n defaultAction: ‘Allow’
\n virtualNetworkRules: []
\n bypass: ‘AzureServices’
\n }
\n \/\/ … other configuration
\n }
\n}<\/p>\n

Finally for App Service Plan Sizing:<\/strong><\/p>\n

sku: {
\n name: envType == ‘prod’ ? ‘S1’ : ‘B2’
\n tier: envType == ‘prod’ ? ‘Standard’ : ‘Basic’
\n}<\/p>\n

Enhance default CI\/CD workflow<\/h2>\n

azd includes a powerful command to bootstrap CI\/CD pipeline:<\/p>\n

azd pipeline config<\/p>\n

This generates a basic workflow. However, for dev-to-prod promotion, enhance it with these steps:<\/p>\n

1. Package Once:<\/strong><\/p>\n

– name: Package Application
\n run: |
\n mkdir -p .\/dist
\n azd package app –output-path .\/dist\/app-package.zip
\n # Create a backup copy for production deployment
\n cp .\/dist\/app-package.zip .\/app-package-backup.zip
\n echo “\u2705 Application packaged and backup created”<\/p>\n

2. Deploy to Dev:<\/strong><\/p>\n

– name: Deploy to Development
\n run: azd deploy app –from-package .\/dist\/app-package.zip –no-prompt<\/p>\n

3. Validation Gate:<\/strong><\/p>\n

– name: Validate Application
\n run: |
\n echo “\ud83d\udd0d Validating application in development environment…”
\n # Add your validation logic here:
\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

4. Set environment variables:<\/strong><\/p>\n

– name: Promote to Production
\n run: |
\n # Create production environment name by replacing -dev with -prod, or adding -prod if no -dev suffix
\n PROD_ENV_NAME=”${AZURE_ENV_NAME%-dev}-prod”
\n echo “Production environment name: $PROD_ENV_NAME”<\/p>\n

# Set environment variables for this step
\n export AZURE_ENV_NAME=”$PROD_ENV_NAME”
\n export AZURE_ENV_TYPE=”prod”<\/p>\n

5. Deploy to Prod:<\/strong><\/p>\n

# Use the same package created earlier – true “build once, deploy everywhere”
\nPACKAGE_PATH=”.\/app-package-backup.zip”<\/p>\n

if [ -f “$PACKAGE_PATH” ]; then
\n echo “\ud83d\ude80 Deploying to production using existing package: $PACKAGE_PATH”
\n azd deploy app –from-package “$PACKAGE_PATH” –no-prompt
\n echo “\u2705 Production deployment completed successfully”<\/p>\n

6. Clean Up:<\/strong><\/p>\n

# Clean up the backup package after successful deployment
\n rm -f “$PACKAGE_PATH”
\n echo “\ud83e\uddf9 Cleaned up package backup”
\nelse
\n echo “\u274c Package backup not found – falling back to regular deployment”
\n azd deploy –no-prompt
\nfi<\/p>\n

Try It Out<\/h2>\n

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

Watch the walkthrough:<\/strong> See this entire process in action in the video below that shows the complete setup and deployment flow.<\/p>\n\n

Step-by-Step Setup<\/h3>\n

Follow these steps to set up both development and production environments, then configure the CI\/CD pipeline:<\/p>\n

1. Initialize project from the template<\/strong><\/p>\n

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

This downloads the complete implementation with all Bicep files and enhanced<\/strong> GitHub Actions workflow.<\/p>\n

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

azd up<\/p>\n

When prompted for the environment name, use myproj-dev (or your preferred naming pattern with -dev suffix).<\/p>\n

Note<\/strong>: The default envType is dev, so you don\u2019t need to set the AZURE_ENV_TYPE environment variable for development. The infrastructure will automatically provision with public access and cost-optimized resources.<\/p>\n

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

Create and configure the production environment:<\/p>\n

# Create new production environment
\nazd env new myproj-prod<\/p>\n

# Set environment type to production
\nazd env set AZURE_ENV_TYPE prod<\/p>\n

# Deploy production environment
\nazd up<\/p>\n

This provisions production infrastructure with VNet integration, private endpoints, and enhanced security. Note that running azd up deploys the app to the production infrastructure as well. This is for demonstration purpose plus we are still in development stage. In a real-world scenario, you\u2019d probably never deploy your app directly if it is already in production.<\/p>\n

4. Switch Back to Development Environment<\/strong><\/p>\n

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

You\u2019re now ready to develop and test in the development environment.<\/p>\n

5. Make Code Changes<\/strong><\/p>\n

Edit your application code (e.g., modify app\/templates\/index.html or app.py) to test the promotion workflow.<\/p>\n

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

azd pipeline config<\/p>\n

The GitHub Actions workflow is enhanced with dev-to-prod promotion logic. Specifically, the pipeline will:<\/p>\n

Deploy and validate in development (`myproj-dev`)
\nAutomatically promote to production (`myproj-prod`) using the same package
\nHandle environment naming conversion automatically<\/p>\n

Once configured, every push to the main branch will trigger the automated dev-to-prod promotion pipeline!<\/p>\n

Conclusion<\/h2>\n

In summary, this pattern combines conditional Bicep deployment, package preservation, and smart environment naming to create reliable dev-to-prod promotions with the same build artifacts.<\/p>\n

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

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

This post walks through how to implement a \u201cbuild once, deploy everywhere\u201d pattern using Azure Developer CLI (azd) that provisions […]<\/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-2266","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\/2266","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=2266"}],"version-history":[{"count":0,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/posts\/2266\/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=2266"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/categories?post=2266"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/tags?post=2266"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}