Azure-devops-docs: Difference between AzureResourceManagerTemplateDeployment and AzureResourceGroupDeployment

Created on 31 Jan 2020  Â·  2Comments  Â·  Source: MicrosoftDocs/azure-devops-docs

There seem to be 2 similar tasks available for deploying Azure resources.

Unfortunately, I cannot find any documentation regarding the AzureResourceManagerTemplateDeployment although this AzureResourceManagerTemplateDeployment task can be choosen from the Yaml pipeline editor in Azure Devops:

- task: AzureResourceManagerTemplateDeployment@3
  inputs:
    deploymentScope: 'Resource Group'
    action: 'Create Or Update Resource Group'
    templateLocation: 'Linked artifact'
    deploymentMode: 'Incremental'

On the other hand, I cannot find the AzureResourceGroupDeployment task in the Yaml pipelines editor in Azure Devops. What are the differences between these 2 tasks ? Where can I find the documentation regarding the AzureResourceManagerTemplateDeployment task and how come I cannot find the AsureResourceGroupDeployment task in the Yaml editor in Azure Devops ?


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Pri2 devops-cictech devopprod doc-enhancement stale-issue

Most helpful comment

Hi!

Documentation for the AzureResourceManagerTemplateDeployment can be found at https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/AzureResourceManagerTemplateDeploymentV3

Main difference is the deploymentScope part, where you can choose to target either on Management Group, Subscription or Resource Group level. Highly useful when you have service connections that span multiple subscriptions

All 2 comments

Hi!

Documentation for the AzureResourceManagerTemplateDeployment can be found at https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/AzureResourceManagerTemplateDeploymentV3

Main difference is the deploymentScope part, where you can choose to target either on Management Group, Subscription or Resource Group level. Highly useful when you have service connections that span multiple subscriptions

This issue hasn't been updated in more than 180 days, so we've closed it. If you feel the issue is still relevant and needs fixed, please reopen it and we'll take another look. We appreciate your feedback and apologize for any inconvenience.

Was this page helpful?
0 / 5 - 0 ratings