Deploy To Resource Group - Document Details

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.

View on GitHub 📚 View on Microsoft Learn

Bias Analysis

Detected Bias Types

windows_first

powershell_heavy

Summary

The documentation provides both Azure CLI and Azure PowerShell examples for deploying Bicep files, but consistently lists Azure CLI (which is cross-platform) first, followed by Azure PowerShell (which is traditionally Windows-centric, though now available cross-platform). There are no explicit Linux-only or Windows-only commands, but the presence of PowerShell examples and references may be perceived as Windows-leaning, especially since no Bash or Linux-native shell examples are provided. There is no mention of Windows-specific tools, but the documentation could better highlight Linux parity by including Bash or shell script examples and clarifying cross-platform compatibility.

Recommendations

Explicitly state that Azure CLI commands work identically on Windows, Linux, and macOS.
Add Bash or shell script examples for common deployment scenarios to demonstrate Linux parity.
Clarify that Azure PowerShell is available cross-platform, and provide installation links for Linux/macOS.
Consider including a table or section comparing deployment options across platforms (Windows, Linux, macOS).
Avoid implying PowerShell is the default or preferred method unless justified by technical reasons.

Create Pull Request

Scan History

Date	Scan	Status	Result
2025-07-12 23:44	#41	cancelled	Biased
2025-07-12 00:58	#8	cancelled	Clean
2025-07-10 05:06	#7	processing	Clean

Flagged Code Snippets

For an example template, see [Deploy to target resource group](#deploy-to-target-resource-group).

### Scope to different resource group

To deploy resources to a resource group that isn't the target resource group, add a [module](modules.md). Use the [`resourceGroup` function](bicep-functions-scope.md#resourcegroup) to set the `scope` property for that module.

If the resource group is in a different subscription, provide the subscription ID and the name of the resource group. If the resource group is in the same subscription as the current deployment, provide only the name of the resource group. If you don't specify a subscription in the `resourceGroup` function, the current subscription is used.

The following example shows a module that targets a resource group in a different subscription:

# [Azure PowerShell](#tab/azure-powershell)

For the PowerShell deployment command, use [New-AzResourceGroupDeployment](/powershell/module/az.resources/new-azresourcegroupdeployment). The following example deploys a template to create a resource group. The resource group you specify in the `-ResourceGroupName` parameter is the **target resource group**.