Document Details
Cache How To Active Geo Replication
❌
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
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 it consistently lists PowerShell after CLI and does not provide any Linux- or macOS-specific instructions or examples. There are no references to Linux-native tools, Bash scripts, or cross-platform shell usage. The focus on PowerShell, which is traditionally associated with Windows, and the absence of explicit Linux/Bash examples or notes about cross-platform usage, indicate a mild Windows bias.
Recommendations:
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell prompts (e.g., $ for Bash, PS> for PowerShell) to clarify cross-platform compatibility.
- Add Bash-specific examples or notes where appropriate, especially for scripting or automation scenarios.
- Where PowerShell is referenced, clarify that PowerShell Core is available cross-platform, or provide equivalent Bash/Unix shell commands if possible.
- Include a section or note about running these commands on Linux/macOS, including any prerequisites or differences (e.g., installation of Azure CLI or PowerShell Core).
- Ensure screenshots and UI instructions do not assume a Windows environment unless unavoidable.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-09-16 00:00 | #113 | completed | ✅ Clean |
| 2025-09-15 00:00 | #112 | completed | ✅ Clean |
| 2025-09-14 00:00 | #111 | completed | ✅ Clean |
| 2025-09-13 00:00 | #110 | completed | ✅ Clean |
| 2025-09-12 00:00 | #109 | completed | ✅ Clean |
| 2025-09-11 00:00 | #108 | completed | ✅ Clean |
| 2025-09-10 00:00 | #107 | completed | ✅ Clean |
| 2025-09-09 00:00 | #106 | completed | ✅ Clean |
| 2025-09-08 00:00 | #105 | completed | ✅ Clean |
| 2025-09-07 00:00 | #104 | completed | ❌ Biased |
| 2025-09-06 00:00 | #103 | completed | ❌ Biased |
| 2025-09-05 00:00 | #102 | completed | ✅ Clean |
| 2025-09-04 00:00 | #101 | completed | ✅ Clean |
| 2025-09-03 00:00 | #100 | completed | ✅ Clean |
| 2025-09-02 00:00 | #99 | in_progress | ✅ Clean |
| 2025-09-01 00:00 | #98 | in_progress | ❌ Biased |
| 2025-08-31 00:01 | #97 | in_progress | ❌ Biased |
| 2025-08-30 00:01 | #96 | in_progress | ✅ Clean |
| 2025-08-29 00:01 | #95 | completed | ❌ Biased |
| 2025-08-17 00:01 | #83 | in_progress | ✅ Clean |
| 2025-07-13 21:37 | #48 | completed | ❌ Biased |
| 2025-07-09 13:09 | #3 | cancelled | ✅ Clean |
| 2025-07-08 04:23 | #2 | cancelled | ✅ Clean |
Flagged Code Snippets
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 Enterprise instance in a new geo-replication group using PowerShell
This example creates a new Azure Cache for Redis Enterprise E10 cache instance called _Cache1_ in the East US region. Then, the cache is added to a new active geo-replication group called _replicationGroup_:
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 Enterprise instance in an existing geo-replication group using PowerShell
This example creates a new Enterprise E10 cache instance called _Cache2_ in the West US region. Then, the script adds the cache to the _replicationGroup_ active geo-replication group created in the previous procedure. After the running the command, the two caches, _Cache1_ and _Cache2_, are linked in an active-active configuration.