Sad Tux - Windows bias detected
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_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell-based instructions for all command-line operations, with no equivalent Azure CLI (cross-platform) or Bash examples. PowerShell is featured as the only scripting option, and all automation steps outside the portal are shown using PowerShell cmdlets, which are primarily used on Windows. There are no Linux/macOS-specific instructions or CLI examples, and PowerShell is presented before any mention of Azure CLI. The only mention of Azure CLI is in a passing reference for configuring service endpoints, with no actual CLI commands or walkthroughs provided.
Recommendations
  • Add Azure CLI examples (az commands) for all PowerShell-based steps, including exporting and deploying templates, and managing resources.
  • Present Azure CLI and PowerShell examples side-by-side or in tabs, ensuring parity for Linux/macOS users.
  • Explicitly mention that PowerShell can be used cross-platform, but highlight Azure CLI as the recommended tool for Linux/macOS.
  • Include Bash shell script examples where automation is discussed, or reference Bash scripting for Linux users.
  • Ensure that references to tools and commands are not Windows-centric; provide equal visibility to cross-platform tools.
  • Review and update the documentation to avoid assuming the reader is using Windows or PowerShell by default.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-01-12 00:00 #99 completed Biased Biased
2026-01-11 06:20 #98 completed Biased Biased
2026-01-10 00:00 #92 completed Clean Clean
2026-01-09 00:00 #87 cancelled Clean Clean
2026-01-06 22:28 #78 completed Clean Clean
2025-12-29 18:00 #48 cancelled Biased Biased
2025-12-15 00:00 #7 completed Clean Clean
2025-12-14 05:05 #6 completed Clean Clean

Flagged Code Snippets

1. Export the template of your source key vault. These commands save a json template to your current directory.

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

To deploy the template by using PowerShell:

1. In the **template.json** file, name the target key vault by setting the default value of the key vault name. This example sets the default value of the key vault name to `key-vault-name`.

   
   You can obtain region codes by running the [Get-AzLocation](/powershell/module/az.resources/get-azlocation) command.

   
---

### Redeploy

Deploy the template to create a new key vault in the target region.

#### [Portal](#tab/azure-portal)

1. Save the **template.json** file.
1. Enter or select the property values:

   - **Subscription**: Select an Azure subscription.
   - **Resource group**: Select **Create new** and give the resource group a name.
   - **Location**: Select an Azure location.

1. Select **I agree to the terms and conditions stated above**, and then select **Select Purchase**.
1. Access Policies and Network configuration settings (private endpoints) need to be re-configured in the new Key Vault. Soft delete and purge protection need to be re-configured in the new key vault and the _Autorotation settings_.

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

1. Obtain the subscription ID where you want to deploy the target public IP with [Get-AzSubscription](/powershell/module/az.accounts/get-azsubscription):