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
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring active geo-replication, but does not include any Linux-specific shell (e.g., Bash) or cross-platform scripting examples. PowerShell, which is traditionally associated with Windows, is given a dedicated section with detailed examples. There are no explicit Linux command-line (bash) or scripting examples, nor is there mention of Linux-specific tools or workflows. The ordering of examples (CLI first, then PowerShell) is somewhat neutral, but the lack of Linux/Bash parity and the heavy PowerShell focus indicate a mild Windows bias.
Recommendations
  • Add explicit Bash shell examples for all CLI commands, demonstrating usage in a typical Linux environment.
  • Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows, possibly with sample terminal prompts (e.g., $ for bash, PS> for PowerShell).
  • Include notes or examples for automation using Linux-native tools (e.g., bash scripts, cron jobs) where PowerShell scripting is shown.
  • Where PowerShell is mentioned, consider also mentioning cross-platform PowerShell Core, or clarify if the examples are intended for Windows PowerShell only.
  • Ensure that any references to tools or workflows are inclusive of both Windows and Linux environments, and avoid assuming a Windows-first context.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-01-14 00:00 #250 in_progress Biased Biased
2026-01-13 00:00 #246 completed Biased Biased
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-29 00:01 #95 completed Clean Clean
2025-08-17 00:01 #83 cancelled Clean Clean
2025-07-13 21:37 #48 completed Biased Biased
2025-07-12 23:44 #41 cancelled Biased Biased

Flagged Code Snippets

To configure active geo-replication properly, the ID of the cache instance being created must be added with the `-LinkedDatabase` parameter. The ID is in the format:

`/subscriptions/<your-subscription-ID>/resourceGroups/<your-resource-group-name>/providers/Microsoft.Cache/redisEnterprise/<your-cache-name>/databases/default`

#### Create new Azure Managed Redis instance in an existing geo-replication group using PowerShell

This example creates a new Balanced B10 cache instance called _Cache2_ in the West US region. Then, the script adds the cache to the  active geo-replication group, _replicationGroup_ created in the previous procedure. The result is the two caches, _Cache1_ and _Cache2_, are linked in an active-active configuration.

As before, you need to list both _Cache1_ and _Cache2_ using the `--linked-databases` parameter.

### Azure PowerShell

Use Azure PowerShell to create a new cache and geo-replication group, or to add a new cache to an existing geo-replication group. For more information, see [New-AzRedisEnterpriseCache](/powershell/module/az.redisenterprisecache/new-azredisenterprisecache).

#### Create new Azure Managed Redis instance in a new geo-replication group using PowerShell

This example creates a new Azure Managed Redis Balanced B10 cache instance called _Cache1_ in the East US region. Then, the cache is added to a new active geo-replication group called _replicationGroup_: