The Technology Chronicle

In Part 1 of the blog series , we created the build configuration for CI/CD pipeline of ARM template deployment. In this blog, we will create the release pipeline and deploy the VMs across dev and test environments in Azure when a commit is triggered Create the release pipeline by clicking on the release option once the build is completed In the Release definition, select a blank template to start with And provide name of your first environment Now we have our first environment ready, lets add the tasks. Select the created environment. Start adding tasks from  Tasks->Deploy->Resource Group deployment Edit the settings of the added task. You need to add your Azure subscription to VSTS as a service endpoint Click on Manage and it will open the service end point configuration in a different tab. Add your Azure subscription here.Click on New Service Endpoint->Azure Resource manager

Infrastructure as code , at high level is how you can configure and manage your infrastructure the same way that you would manage your application code .It leverages the concepts of continuous integration and deployment to update or provision your environment based on the changes made to the code. In Azure you can leverage ARM template , which is essentially a json file to implement this concept.  In this blog series we will explore the concepts of Infrastructure as a code deployment for Azure environments using ARM templates. The  Continuous Integration and Deployment pipeline leverages  VSTS for build and deployment and the source code repository will be Git. The code in this case is the ARM template json file and the related parameter files.  The following blog gives a nice explanation on how to get started with VSTS and integrate  it with the Git repository  : https://blog.kloud.com.au/2017/06/24/azure-build-pipeline-using-arm-templates-and-visual-studio-team-services /  We w

We saw a lot of new exciting features for Azure being announced in the recently concluded MSIgnite conference. Many of the long anticipated features or products were released in preview and in this blog series I will try to explore some of these features and how you can get started with them. Azure Data box This can be considered as an extension to the Storage import/export services already available in GA in Azure. While using the Import/export service, customers have to copy their data to HDDs of a given specification and then send them off to Azure datacenters, where the data will be moved to your storage of choice . This services targets migration scenarios where customer have to transfer several terabytes of data to Azure storage and over the network transfer would take  a very long time or is practically impossible.More details about this service can be found here :  https://docs.microsoft.com/en-us/azure/storage/common/storage-import-export-service  With Azure Data box we