Deploying to on-premises Windows machines with Azure DevOps – Part 2 | DevOps Lab


    In this series, Abel and Zachary Deptawa walk through deploying to on premises Windows servers behind firewalls using Azure DevOps.

    In part two, we show how easy it is to set up Deployment Groups inside of Azure DevOps Service for Windows servers. This deployment group will be used with our .NET Build from the previous episode and will also be configured as our target in our Release Pipeline in the next episode!

    Follow Zachary Deptawa on Twitter: @zdeptawa
    Follow Abel Wang on Twitter: @abelsquidhead


    Azure DevOps:
    Deployment Groups in Azure DevOps:
    Create a Free Azure Account:

    #azuredevops #azurepipelines #windowsmachines


    Previous articleAWS CLI CloudFormation Tutorial
    Next articleHow to create BitBucket Repo and BitBucket CI/CD Pipelines? | Tech Primers


    1. I like the presenter style slow nice and easy but database server with access to the internet? Man that should have been part of the video how we deploy without having to expose the db server. Know Microsoft being Microsoft won't touch on that scenario right?

    2. Hi,

      We are trying to figure out a secure way to deploy web app from Azure DevOps to our on-premise environments (Dev, QA, Staging, and Prod).

      My security team has asked, how installing the agent is safe for our on-premise environments (Dev, QA, Staging, and Prod)? I have googled but didn't find any clue. I wonder if Azure DevOps product team use deployment groups to deploy apps to their on-premise "production" server?

    3. Thanks for these videos to make life easy for developers migrating to devops but still their organization uses on prem servers for deployment.Would you please add one more video in this series for how to configure variables for multiple environments like UAT, QA, Test, PROD and in such case we may also see how parallel job deployment works plus if we can utilize config transform(for multiple environments or something even simpler) or some other mechanism to maintain various settings depending on the type of environment?

    4. You dont need a deployment group because of the firewall. You can install agents behind a firewall without deployment groups. Deployment groups are for parallel deployments. You can achieve that with normal agents without a deployment group using agent capabilities but its not as intuitive or simple as Deployment groups