Quickstart: Use an ARM template to deploy a Linux web app to Azure

Azure DevOps Services

Get started with Azure Resource Manager templates (ARM templates) by deploying a Linux web app with MySQL. ARM templates give you a way to save your configuration in code. Using an ARM template is an example of infrastructure as code and a good DevOps practice.

An ARM template is a JavaScript Object Notation (JSON) file that defines the infrastructure and configuration for your project. The template uses declarative syntax. In declarative syntax, you describe your intended deployment without writing the sequence of programming commands to create the deployment.

You can use either JSON or Bicep syntax to deploy Azure resources. Learn more about the difference between JSON and Bicep for templates.

Prerequisites

Before you begin, you need:

• An Azure account with an active subscription. Create an account for free.
• An active Azure DevOps organization. Sign up for Azure Pipelines.
• (For Bicep deployments) An existing resource group. Create a resource group with Azure portal, Azure CLI, or Azure PowerShell.

Get the code

Fork this repository on GitHub:

https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.web/webapp-linux-managed-mysql

Review the template

JSON

The template used in this quickstart is from Azure Quickstart Templates.

The template defines several resources:

• Microsoft.Web/serverfarms
• Microsoft.Web/sites
• Microsoft.DBforMySQL/servers
• Microsoft.DBforMySQL/servers/firewallrules
• Microsoft.DBforMySQL/servers/databases

Bicep

The Bicep template used in this quickstart deploys the same resources as the JSON template. Bicep provides a more readable syntax for defining Azure resources.

Create your pipeline and deploy your template

JSON

1. Sign in to your Azure DevOps organization and navigate to your project. Create a project if you do not already have one.

2. Go to Pipelines, and then select Create Pipeline.

3. Select GitHub as the location of your source code.

   Note

   You may be redirected to GitHub to sign in. If so, enter your GitHub credentials.

4. When the list of repositories appears, select yourname/azure-quickstart-templates/.

   Note

   You may be redirected to GitHub to install the Azure Pipelines app. If so, select Approve and install.

5. When the Configure tab appears, select Starter pipeline.

6. Replace the content of your pipeline with this code:

   trigger:
     - none
   
   pool:
     vmImage: 'ubuntu-latest'
   

7. Create pipeline variables for siteName, administratorLogin, and administratorLoginPassword. The password variable should be marked as secret.

   • Select Variables on the pipeline page.
   • Use the + button to add variables.
   • For administratorLoginPassword, select Keep this value secret.

8. Add the Copy Files task to the YAML file:

   trigger:
     - none
   
   pool:
     vmImage: 'ubuntu-latest'
   
   steps:
     - task: CopyFiles@2
       inputs:
         SourceFolder: 'quickstarts/microsoft.web/webapp-linux-managed-mysql/'
         Contents: '**'
         TargetFolder: '$(Build.ArtifactStagingDirectory)'
   

9. Add and configure the Azure Resource Group Deployment task:

   trigger:
     - none
   
   pool:
     vmImage: 'ubuntu-latest'
   
   steps:
     - task: CopyFiles@2
       inputs:
         SourceFolder: 'quickstarts/microsoft.web/webapp-linux-managed-mysql/'
         Contents: '**'
         TargetFolder: '$(Build.ArtifactStagingDirectory)'
   
     - task: AzureResourceManagerTemplateDeployment@3
       inputs:
         deploymentScope: 'Resource Group'
         azureResourceManagerConnection: '<your-resource-manager-connection>'
         subscriptionId: '<your-subscription-id>'
         action: 'Create Or Update Resource Group'
         resourceGroupName: 'ARMPipelinesLAMP-rg'
         location: '<your-closest-location>'
         templateLocation: 'Linked artifact'
         csmFile: '$(Build.ArtifactStagingDirectory)/azuredeploy.json'
         csmParametersFile: '$(Build.ArtifactStagingDirectory)/azuredeploy.parameters.json'
         overrideParameters: '-siteName $(siteName) -administratorLogin $(administratorLogin) -administratorLoginPassword $(administratorLoginPassword)'
         deploymentMode: 'Incremental'
   

10. Click Save and run to deploy your template. The pipeline job will be launched and after a few minutes, depending on your agent, the job status should indicate Success.

Bicep

1. Sign in to your Azure DevOps organization and navigate to your project. Create a project if you do not already have one.

2. Go to Pipelines, and then select Create Pipeline.

3. Select GitHub as the location of your source code.

   Note

   You may be redirected to GitHub to sign in. If so, enter your GitHub credentials.

4. When the list of repositories appears, select yourname/azure-quickstart-templates/.

   Note

   You may be redirected to GitHub to install the Azure Pipelines app. If so, select Approve and install.

5. When the Configure tab appears, select Starter pipeline.

6. Replace the content of your pipeline with this code:

   trigger:
     - none
   
   pool:
     vmImage: 'ubuntu-latest'
   

7. Create pipeline variables for siteName, administratorLogin, and administratorLoginPassword. The password variable should be marked as secret.

   • Select Variables on the pipeline page.
   • Use the + button to add variables.
   • For administratorLoginPassword, select Keep this value secret.

8. At the top of your YAML file, map values for location and resourceGroupName. Your location should be the location of the resource group. Your resource group needs to already exist.

   variables:
     vmImageName: 'ubuntu-latest'
     resourceGroupName: '<resource-group-name>'
     location: '<your-closest-location>'
     templateFile: './main.bicep'
     sourceFolder: 'quickstarts/microsoft.web/webapp-linux-managed-mysql/'
   

9. If you do not already have an Azure Resource Manager service connection, create a service connection. Learn more about connecting to Azure.

10. Add the Azure CLI task to deploy with Bicep:

    variables:
      vmImageName: 'ubuntu-latest'
      resourceGroupName: '<resource-group-name>'
      location: '<your-closest-location>'
      templateFile: './main.bicep'
      sourceFolder: 'quickstarts/microsoft.web/webapp-linux-managed-mysql/'
    
    trigger:
      - none
    
    pool:
      vmImage: $(vmImageName)
    
    steps:
      - task: AzureCLI@2
        inputs:
          azureSubscription: '<service-connection-name>'
          scriptType: bash
          scriptLocation: inlineScript
          inlineScript: |
            az deployment group create --resource-group $(resourceGroupName) --template-file $(sourceFolder)$(templateFile) \
            --parameters administratorLogin=$(administratorLogin) administratorLoginPassword=$(administratorLoginPassword)
    

Review deployed resources

JSON

1. Verify that the resources deployed. Go to the ARMPipelinesLAMP-rg resource group in the Azure portal and verify that you see App Service, App Service Plan, and Azure Database for MySQL server resources.

   

   You can also verify the resources using Azure CLI.

   az resource list --resource-group ARMPipelinesLAMP-rg --output table
   

2. Go to your new site. If you set siteName to armpipelinetestsite, the site is located at https://armpipelinetestsite.azurewebsites.net/.

Bicep

1. Verify that the resources deployed. Go to your resource group in the Azure portal and verify that you see App Service, App Service Plan, and Azure Database for MySQL server resources.

   

   You can also verify the resources using Azure CLI.

   az resource list --resource-group <resource-group-name> --output table
   

2. Go to your new site. If you set siteName to armpipelinetestsite, the site is located at https://armpipelinetestsite.azurewebsites.net/.

Clean up resources

JSON

You can also use an ARM template to delete resources. Change the action value in your Azure Resource Group Deployment task to DeleteRG. You can also remove the inputs for templateLocation, csmFile, csmParametersFile, overrideParameters, and deploymentMode.

trigger:
  - none

pool:
  vmImage: 'ubuntu-latest'

steps:
  - task: CopyFiles@2
    inputs:
      SourceFolder: 'quickstarts/microsoft.web/webapp-linux-managed-mysql/'
      Contents: '**'
      TargetFolder: '$(Build.ArtifactStagingDirectory)'

  - task: AzureResourceManagerTemplateDeployment@3
    inputs:
      deploymentScope: 'Resource Group'
      azureResourceManagerConnection: '<your-resource-manager-connection>'
      subscriptionId: '<your-subscription-id>'
      action: 'DeleteRG'
      resourceGroupName: 'ARMPipelinesLAMP-rg'
      location: '<your-closest-location>'

Bicep

If you no longer need your deployed resources, delete your resource group.

az group delete -n <resource-group-name>

Next steps

Create your first ARM template