Document Details
Howto Move Across Regions
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by providing detailed instructions and examples exclusively for Azure PowerShell, which is most commonly used on Windows. It references Windows-specific tools (e.g., Notepad for editing JSON files) and omits equivalent Linux/macOS command-line examples (such as Azure CLI or cross-platform editors). The PowerShell workflow is presented as the only scripting alternative to the portal, with no mention of Linux-friendly options. The order of presentation also puts Windows-centric methods before any cross-platform alternatives.
Recommendations
- Add Azure CLI examples for all steps currently shown with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Replace or supplement 'notepad' with cross-platform editors (e.g., 'nano', 'vim', 'code') or generic instructions for editing JSON files.
- Explicitly mention that PowerShell Core is available cross-platform, or clarify the instructions for Linux/macOS users.
- Provide bash shell command equivalents for resource group and template management.
- Reorder sections or provide parallel instructions so that Linux/macOS users do not feel secondary to Windows users.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-12 00:00 | #99 | completed |
Biased
|
| 2026-01-11 06:20 | #98 | completed |
Biased
|
| 2026-01-10 00:00 | #92 | completed |
Biased
|
| 2026-01-06 22:28 | #78 | completed |
 Clean
|
| 2025-12-29 18:00 | #48 | cancelled |
Biased
|
| 2025-12-15 00:00 | #7 | completed |
Clean
|
| 2025-12-14 05:05 | #6 | completed |
Clean
|
Flagged Code Snippets
3. Export the template of your source Web PubSub resource. These commands save a json template to your current directory.
7. To obtain region location codes, see [Azure Web PubSub Locations](https://azure.microsoft.com/global-infrastructure/services/?products=web-pubsub). The code for a region is the region name with no spaces, **Central US** = **centralus**.
8. You can also change other parameters in the template if you choose, and are optional depending on your requirements.
9. Save the **\<resource-group-name>.json** file.
10. Create a resource group in the target region for the target Web PubSub resource to be deployed using [New-AzResourceGroup](/powershell/module/az.resources/new-azresourcegroup).
11. Deploy the edited **\<resource-group-name>.json** file to the resource group created in the previous step using [New-AzResourceGroupDeployment](/powershell/module/az.resources/new-azresourcegroupdeployment):
12. To verify the resources were created in the target region, use [Get-AzResourceGroup](/powershell/module/az.resources/get-azresourcegroup) and [Get-AzWebPubSub](/powershell/module/az.signalr/get-azwebpubsub):
## Discard After the deployment, if you wish to start over or discard the Web PubSub resource in the target, delete the resource group that was created in the target and the moved Web PubSub resource will be deleted. To do so, select the resource group from your dashboard in the portal and select **Delete** at the top of the overview page. Alternatively you can use [Remove-AzResourceGroup](/powershell/module/az.resources/remove-azresourcegroup):