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 provides detailed instructions and examples for Azure CLI and Azure PowerShell, with the PowerShell section being particularly extensive. PowerShell is a Windows-centric tool, and its prominence, along with the absence of explicit Linux shell (bash) examples or references to Linux-specific tooling, indicates a Windows bias. There are no Linux-specific command-line examples, nor is there guidance for Linux users beyond the Azure CLI, which is cross-platform but not presented with Linux-specific context or examples.
Recommendations
  • Add explicit bash/Linux shell examples for creating and managing Azure HPC Cache resources, demonstrating parity with PowerShell examples.
  • Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide Linux-specific setup instructions (e.g., package manager installation commands).
  • Include references to Linux-native tools or workflows where appropriate, such as using bash scripts or integrating with Linux authentication/identity mechanisms.
  • Balance the prominence of PowerShell by ensuring that Linux and cross-platform workflows are equally represented and easy to follow.
  • Where PowerShell is mentioned, also mention bash or shell scripting alternatives for Linux users.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-01-26 00:00 #302 completed Clean Clean
2026-01-24 00:00 #294 completed Clean Clean
2026-01-23 00:00 #290 failed Clean Clean
2026-01-14 00:00 #250 in_progress Biased Biased
2026-01-13 00:00 #246 completed Clean Clean
2026-01-11 00:00 #240 completed Biased Biased
2026-01-10 00:00 #237 completed Biased Biased
2026-01-09 00:34 #234 completed Biased Biased
2026-01-08 00:53 #231 completed Biased Biased
2026-01-06 18:15 #225 cancelled Clean Clean
2025-08-17 00:01 #83 cancelled Biased Biased
2025-07-13 21:37 #48 completed Clean Clean
2025-07-12 23:44 #41 cancelled Biased Biased
2025-07-09 13:09 #3 cancelled Clean Clean
2025-07-08 04:23 #2 cancelled Biased Biased

Flagged Code Snippets

## Create the cache with Azure PowerShell

> [!NOTE]
> Azure PowerShell currently does not support creating a cache with customer-managed encryption
> keys. Use the Azure portal.

Use the [New-AzHpcCache](/powershell/module/az.hpccache/new-azhpccache) cmdlet to create a new Azure
HPC Cache.

Provide these values:

* Cache resource group name
* Cache name
* Azure region
* Cache subnet, in this format:

  `-SubnetUri "/subscriptions/<subscription_id>/resourceGroups/<cache_resource_group>/providers/Microsoft.Network/virtualNetworks/<virtual_network_name>/subnets/<cache_subnet_name>"`

  The cache subnet needs at least 64 IP addresses (/24), and it can't house any other resources.

* Cache capacity. Two values set the maximum throughput of your Azure HPC Cache:

  * The cache size (in GB)
  * The SKU of the virtual machines used in the cache infrastructure

  [Get-AzHpcCacheSku](/powershell/module/az.hpccache/get-azhpccachesku) shows the available SKUs and
  the valid cache size options for each one. Cache size options range from 3 TB to 48 TB, but only
  some values are supported.

  This chart shows which cache size and SKU combinations are valid at the time this document is
  being prepared (July 2020).

  | Cache size | Standard_2G | Standard_4G | Standard_8G |
  |------------|-------------|-------------|-------------|
  | 3072 GB    | yes         | no          | no          |
  | 6144 GB    | yes         | yes         | no          |
  | 12,288 GB   | yes         | yes         | yes         |
  | 24,576 GB   | no          | yes         | yes         |
  | 49,152 GB   | no          | no          | yes         |

  Read the **Set cache capacity** section in the portal instructions tab for important information
  about pricing, throughput, and how to size your cache appropriately for your workflow.

Cache creation example: