Today, I practiced creating a complete 𝗥𝗲𝗹𝗲𝗮𝘀𝗲 𝗣𝗶𝗽𝗲𝗹𝗶𝗻𝗲 in Azure DevOps for deploying a sample 𝗔𝗦𝗣.𝗡𝗘𝗧 𝗖𝗼𝗿𝗲 𝘄𝗲𝗯 𝗮𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻 across 𝗗𝗲𝘃, 𝗧𝗲𝘀𝘁, 𝗮𝗻𝗱 𝗣𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻 environments using 𝗔𝘇𝘂𝗿𝗲 𝗔𝗽𝗽 𝗦𝗲𝗿𝘃𝗶𝗰𝗲.

✅ 𝟭. 𝗣𝗿𝗲𝗽𝗮𝗿𝗲 𝘁𝗵𝗲 𝗕𝘂𝗶𝗹𝗱 𝗔𝗿𝘁𝗶𝗳𝗮𝗰𝘁

• Created a CI pipeline to build and publish the ASP.NET Core app
• Generated the artifact (.zip or .dll files) to be used in the release pipeline

✅ 𝟮. 𝗦𝗲𝘁 𝗨𝗽 𝗔𝘇𝘂𝗿𝗲 𝗔𝗽𝗽 𝗦𝗲𝗿𝘃𝗶𝗰𝗲𝘀

• Created three Azure App Services (or deployment slots):

  • One for 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁
  • One for 𝗧𝗲𝘀𝘁𝗶𝗻𝗴 (𝗤𝗔)
  • One for 𝗣𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻

✅ 𝟯. 𝗖𝗿𝗲𝗮𝘁𝗲 𝗮 𝗥𝗲𝗹𝗲𝗮𝘀𝗲 𝗣𝗶𝗽𝗲𝗹𝗶𝗻𝗲 𝗶𝗻 𝗔𝘇𝘂𝗿𝗲 𝗗𝗲𝘃𝗢𝗽𝘀

• Navigated to 𝗣𝗶𝗽𝗲𝗹𝗶𝗻𝗲𝘀 > 𝗥𝗲𝗹𝗲𝗮𝘀𝗲𝘀 > 𝗡𝗲𝘄 𝗣𝗶𝗽𝗲𝗹𝗶𝗻𝗲
• Linked the build artifact from the CI pipeline
• Defined 𝘁𝗵𝗿𝗲𝗲 𝘀𝘁𝗮𝗴𝗲𝘀: Dev, Test, and Production

✅ 𝟰. 𝗖𝗼𝗻𝗳𝗶𝗴𝘂𝗿𝗲 𝗘𝗮𝗰𝗵 𝗦𝘁𝗮𝗴𝗲

• Added the 𝗔𝘇𝘂𝗿𝗲 𝗔𝗽𝗽 𝗦𝗲𝗿𝘃𝗶𝗰𝗲 𝗱𝗲𝗽𝗹𝗼𝘆 𝘁𝗮𝘀𝗸 in each stage
• Selected the appropriate app service for the environment
• Used variables to manage environment-specific settings (like connection strings or API keys)

✅ 𝟱. 𝗔𝗱𝗱 𝗔𝗽𝗽𝗿𝗼𝘃𝗮𝗹 𝗚𝗮𝘁𝗲𝘀

• Added 𝗽𝗿𝗲-𝗱𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 𝗮𝗽𝗽𝗿𝗼𝘃𝗮𝗹𝘀 before the Production stage to ensure safe and reviewed deployments
• Set conditions for sequential deployment (Dev → Test → Prod)

✅ 𝟲. 𝗗𝗲𝗽𝗹𝗼𝘆 𝗮𝗻𝗱 𝗩𝗮𝗹𝗶𝗱𝗮𝘁𝗲

• Triggered the pipeline
• Verified successful deployment to each environment
• Ensured the web app ran correctly in Dev, Test, and Prod stages

This setup ensures 𝗮𝘂𝘁𝗼𝗺𝗮𝘁𝗲𝗱, 𝗿𝗲𝗹𝗶𝗮𝗯𝗹𝗲, 𝗮𝗻𝗱 𝗰𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗲𝗱 𝗱𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁𝘀 across environments—minimizing errors and improving delivery speed.

𝗛𝗼𝘄 𝗱𝗼 𝘆𝗼𝘂 𝗵𝗮𝗻𝗱𝗹𝗲 𝗲𝗻𝘃𝗶𝗿𝗼𝗻𝗺𝗲𝗻𝘁-𝘀𝗽𝗲𝗰𝗶𝗳𝗶𝗰 𝗱𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁𝘀 𝗶𝗻 𝘆𝗼𝘂𝗿 𝗖𝗜/𝗖𝗗 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄𝘀? 𝗛𝗮𝘃𝗲 𝘆𝗼𝘂 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗲𝗱 𝗮 𝗺𝘂𝗹𝘁𝗶-𝘀𝘁𝗮𝗴𝗲 𝗿𝗲𝗹𝗲𝗮𝘀𝗲 𝗽𝗶𝗽𝗲𝗹𝗶𝗻𝗲 𝘄𝗶𝘁𝗵 𝗮𝗽𝗽𝗿𝗼𝘃𝗮𝗹 𝗴𝗮𝘁𝗲𝘀 𝗶𝗻 𝗔𝘇𝘂𝗿𝗲 𝗗𝗲𝘃𝗢𝗽𝘀?