Redis

69
Total Pages
42
Linux-Friendly Pages
27
Pages with Bias
39.1%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

144 issues found
Showing 51-75 of 144 flagged pages
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/best-practices-development.md ...blob/main/articles/redis/best-practices-development.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the 'Data Persistence or Data Backup' section, where export operations are described as being triggered from the portal, CLI, PowerShell, or SDK tools. PowerShell is explicitly mentioned as a tool for export, while Linux equivalents (such as Bash, Azure CLI on Linux, or shell scripting) are not referenced. The ordering of tools places PowerShell before SDK tools, and no Linux-specific examples or guidance are provided throughout the page. There are no code snippets or operational examples for Linux environments, and the documentation does not mention Linux command-line patterns or tools. This may lead Linux users to feel unsupported or unclear about parity in tooling and workflows.
Recommendations
  • Explicitly mention Linux-compatible tools such as Bash, Azure CLI, or shell scripting alongside PowerShell in sections discussing operational tasks.
  • Provide example commands for both Windows (PowerShell) and Linux (Bash/Azure CLI) when describing how to perform exports, backups, or other Redis operations.
  • Reorder tool mentions to avoid always listing Windows tools first; consider grouping by platform or listing cross-platform tools first.
  • Add a section or callout clarifying that all operational tasks (such as export/import) can be performed from Linux environments and provide links to relevant Linux documentation.
  • Ensure that any references to SDKs or CLI tools include installation and usage instructions for both Windows and Linux.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/how-to-active-geo-replication.md ...b/main/articles/redis/how-to-active-geo-replication.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring geo-replication, but PowerShell is given equal prominence to Azure CLI, despite PowerShell being primarily a Windows tool. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or workflows. The documentation does not clarify cross-platform compatibility for commands, and PowerShell examples may not be relevant for Linux users who typically use bash or other shells.
Recommendations
  • Add explicit bash examples for all CLI procedures, showing how Linux/Mac users would perform the same tasks.
  • Clarify that Azure CLI commands work cross-platform, and provide installation instructions for Linux and Mac users.
  • Deprioritize PowerShell by listing Azure CLI (bash) examples first, as CLI is the primary cross-platform tool.
  • Mention that PowerShell Core is available on Linux, but most Linux users prefer bash; provide guidance accordingly.
  • Include troubleshooting or workflow notes relevant to Linux environments (e.g., environment variables, authentication).
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/how-to-scale.md ...cs/azure-docs/blob/main/articles/redis/how-to-scale.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. PowerShell is presented as the first scripting/tool example for scaling, with a dedicated section and explicit command, while Azure CLI (cross-platform) is presented second. There are no Linux-specific instructions, nor are there examples using Bash or shell scripting, and no mention of Linux tools or patterns. The documentation does not discuss platform-specific considerations, such as differences in environment setup or authentication between Windows and Linux. The page assumes users are familiar with PowerShell and does not provide parity for Linux users.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to emphasize cross-platform support.
  • Provide explicit Bash/shell script examples for scaling operations, especially for automation scenarios.
  • Include notes or sections on platform-specific setup or authentication differences for Linux users.
  • Mention that Azure CLI can be used natively on Linux/macOS and provide installation links or references.
  • Add troubleshooting tips or environment setup instructions for Linux users, such as using environment variables or handling authentication.
  • Consider adding a table summarizing available tools for Windows, Linux, and macOS, with links to relevant documentation.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/entra-for-authentication.md ...s/blob/main/articles/redis/entra-for-authentication.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias primarily through exclusive use of PowerShell scripts for troubleshooting, with no equivalent Linux or cross-platform alternatives provided. The troubleshooting section directs users to a PowerShell script for token validation, implicitly prioritizing Windows environments. There are no Bash, shell, or Linux-native tool examples, nor is there mention of how to perform these tasks on Linux or macOS. Additionally, the workflow and instructions reference the Azure portal and Windows-centric patterns first, without acknowledging command-line or cross-platform alternatives.
Recommendations
  • Provide equivalent Bash or shell scripts for token validation and troubleshooting, or document how to use the PowerShell script on Linux/macOS (e.g., via PowerShell Core).
  • Include explicit instructions or examples for Linux and macOS users, such as using Azure CLI or REST API for authentication and management tasks.
  • Mention cross-platform compatibility for all tools and scripts, and clarify any Windows-specific requirements.
  • Add troubleshooting steps using Linux-native tools (e.g., curl, openssl) for validating tokens and diagnosing authentication issues.
  • Ensure that examples and workflows are presented in a platform-neutral order, or provide parallel instructions for both Windows and Linux environments.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/how-to-import-export-data.md .../blob/main/articles/redis/how-to-import-export-data.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. Automation instructions mention PowerShell first, and provide direct links to PowerShell modules before Azure CLI equivalents. There are no explicit Linux shell or bash examples, nor references to Linux-specific tooling or workflows. The page refers to importing data from Redis servers running on Linux or Windows, but does not provide parity in example commands or scripts for Linux environments.
Recommendations
  • Provide bash or Linux shell examples for automating import/export operations, alongside PowerShell examples.
  • Mention and link to Linux-native tools (e.g., azcopy, curl, Azure CLI) where relevant, not just PowerShell.
  • Ensure that CLI instructions are presented with equal prominence as PowerShell, or consider listing CLI first to avoid Windows-first perception.
  • Add example workflows for Linux users, such as uploading RDB files using Linux commands.
  • Clarify that all automation steps can be performed on Linux, macOS, and Windows, and specify any platform-specific considerations.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/migrate/migrate-overview.md ...s/blob/main/articles/redis/migrate/migrate-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits Windows bias primarily through the use of PowerShell cmdlets as the only explicit example for exporting and importing Redis data. Windows-specific tools (PowerShell) are mentioned before any cross-platform or Linux alternatives, and no Linux shell or CLI examples are provided. The migration instructions reference Azure portal and PowerShell, but do not mention or demonstrate Linux CLI, Bash, or other non-Windows approaches, potentially leaving Linux users without clear guidance.
Recommendations
  • Include equivalent Linux/Bash/CLI examples for all migration steps, especially for exporting/importing RDB files.
  • Mention and demonstrate use of Azure CLI (az rediscache commands) alongside PowerShell, with explicit Linux usage instructions.
  • Reference cross-platform tools and provide usage examples for both Windows and Linux environments.
  • Ensure that any tool or script mentioned (such as redis-copy, RIOT) includes installation and usage instructions for Linux.
  • Avoid mentioning Windows tools (PowerShell) first; present cross-platform or Linux options in parallel or before Windows-specific ones.
  • Add a section or callout for Linux users, summarizing migration steps and tools available on Linux.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/private-link.md ...cs/azure-docs/blob/main/articles/redis/private-link.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by presenting Azure PowerShell examples before Azure CLI examples, and by exclusively referencing the Azure portal (which is most commonly used on Windows) for GUI-based instructions. The scripting examples for managing private endpoints and cache resources are provided first in PowerShell, a tool native to Windows, with Azure CLI examples following. There are no explicit Linux-specific instructions, nor are Linux shell patterns (such as Bash or shell scripting) mentioned. The documentation does not reference Linux tools or provide parity for Linux users beyond the Azure CLI, which is cross-platform but not highlighted as such.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform support.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide shell-specific notes where relevant.
  • Include instructions or screenshots for using the Azure portal on non-Windows platforms (e.g., macOS, Linux browsers) if there are differences.
  • Add Bash script examples for automation tasks, especially for Linux users.
  • Where PowerShell is referenced, clarify its availability on Linux and macOS, or suggest Azure CLI as the preferred cross-platform tool.
  • Review terminology to avoid implicit Windows-first assumptions (e.g., avoid phrases like 'run the following PowerShell script' without offering alternatives).
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/redis-modules.md ...s/azure-docs/blob/main/articles/redis/redis-modules.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page references PowerShell as a primary management tool and lists it alongside REST API and Azure CLI for configuration, but does not provide explicit Linux shell or bash examples. The mention of PowerShell and the absence of Linux-specific instructions or examples suggest a Windows-first approach and a bias toward Windows tooling.
Recommendations
  • Provide explicit bash or Linux shell examples for configuring modules using Azure CLI, as this is the most common cross-platform tool.
  • List Azure CLI before PowerShell in tool recommendations, as CLI is cross-platform and more commonly used on Linux.
  • Include a note or section clarifying that all management operations can be performed from Linux/macOS environments using Azure CLI or REST API.
  • If possible, add sample commands for both PowerShell and bash to ensure parity and inclusivity for Linux users.
  • Avoid implying PowerShell is required or preferred unless there is unique functionality unavailable elsewhere.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/troubleshoot-connectivity.md .../blob/main/articles/redis/troubleshoot-connectivity.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by featuring PSPING (a Windows-only tool) and providing a PowerShell example for connectivity testing, without offering equivalent Linux commands or tools. Windows tools and patterns are mentioned before or instead of Linux alternatives, and there is a lack of Linux-specific troubleshooting examples for connectivity testing.
Recommendations
  • Provide Linux equivalents for connectivity testing, such as using 'nc', 'telnet', or 'nmap' to test Redis port connectivity.
  • Include example commands for both Windows and Linux environments side-by-side, ensuring parity in troubleshooting steps.
  • Mention cross-platform tools (e.g., 'redis-cli', 'curl', 'netcat') before platform-specific tools like PSPING.
  • Add explicit Linux troubleshooting examples for steps currently only shown with Windows tools.
  • Clarify which steps or tools are platform-specific and offer alternatives for other operating systems.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/web-app-cache-howto.md ...e-docs/blob/main/articles/redis/web-app-cache-howto.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio (Windows-only), IIS Express (Windows default web server), and Windows-centric workflows for building, running, and deploying the ASP.NET app. There are no examples or instructions for Linux-based development environments, such as using VS Code, .NET CLI, or running the app on Kestrel or Apache/Nginx. The prerequisites and step-by-step instructions assume the user is on Windows, omitting Linux equivalents.
Recommendations
  • Add instructions for developing and running the ASP.NET app on Linux, including using VS Code, JetBrains Rider, or the .NET CLI.
  • Include examples for running the app with Kestrel (cross-platform) instead of IIS Express.
  • Provide deployment steps using Azure CLI or GitHub Actions, which work on both Windows and Linux.
  • Mention package installation via dotnet CLI (e.g., 'dotnet add package') as an alternative to NuGet Package Manager in Visual Studio.
  • Clarify which steps are Windows-specific and offer Linux/macOS alternatives where applicable.
  • Add screenshots and terminal commands for Linux environments to improve parity.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/migrate/migration-guide.md ...cs/blob/main/articles/redis/migrate/migration-guide.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets (Export/Import), mentioning AzCopy (primarily a Windows tool) without Linux alternatives, and providing no Linux or cross-platform command examples. Windows-specific tools and patterns are mentioned before or instead of Linux equivalents, and there are no explicit Linux instructions or examples for migration steps.
Recommendations
  • Provide equivalent CLI examples using Azure CLI (az redis ...) alongside or instead of PowerShell cmdlets.
  • Mention and provide examples for using AzCopy on Linux/macOS, or suggest alternative tools (such as rsync, scp, or Azure CLI storage commands) for copying RDB files.
  • Explicitly state that all migration steps can be performed from Linux, and provide sample shell commands (bash) for relevant steps.
  • Where PowerShell is referenced, add parallel instructions for Linux environments.
  • Include a table or section comparing Windows and Linux approaches for common migration tasks.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/troubleshoot-timeouts.md ...docs/blob/main/articles/redis/troubleshoot-timeouts.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While it mentions Linux in one section (TCP settings for Linux based client applications), most troubleshooting steps and examples assume a Windows/.NET/StackExchange.Redis environment. There is a strong focus on Windows-specific tools and patterns (e.g., performance counters, NuGet, RedisSessionStateProvider XML config), and no Linux-specific monitoring or troubleshooting examples are provided. Powershell or Windows-centric terminology appears first or exclusively in several sections, and Linux equivalents (such as using top, htop, or Linux system metrics) are missing.
Recommendations
  • Add Linux-specific examples for monitoring CPU and network bandwidth (e.g., using top, htop, sar, ifstat, or netstat).
  • Provide equivalent Linux configuration and troubleshooting steps alongside Windows/.NET examples, especially for client-side monitoring and configuration.
  • Include examples for popular Linux Redis clients (e.g., redis-py, Jedis) and their error messages or troubleshooting steps.
  • When mentioning tools like performance counters or NuGet, also mention and provide instructions for Linux alternatives (e.g., system metrics, pip for Python clients).
  • Ensure that Linux and Windows troubleshooting steps are presented with equal prominence, ideally side-by-side or in clearly labeled sections.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/dotnet-how-to-use-azure-redis-cache.md .../articles/redis/dotnet-how-to-use-azure-redis-cache.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows development environments. It assumes the use of Visual Studio (a Windows-centric IDE), references .NET Framework (not .NET Core/.NET 5+ which are cross-platform), and provides instructions specific to Windows workflows (e.g., right-clicking in Visual Studio, editing app.config). There are no examples or guidance for Linux or cross-platform development environments, such as using VS Code, the .NET CLI, or running the sample on Linux/macOS.
Recommendations
  • Add instructions for setting up and running the sample using the .NET CLI (dotnet new, dotnet add package, dotnet run), which works on Linux, macOS, and Windows.
  • Include guidance for using cross-platform editors like Visual Studio Code.
  • Mention .NET (Core/5/6/7+) as an alternative to .NET Framework for cross-platform compatibility.
  • Provide Linux/macOS-specific instructions for installing prerequisites and running the sample.
  • Avoid assuming the use of Visual Studio or Windows-specific workflows; present cross-platform alternatives first or alongside.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/best-practices-development.md ...blob/main/articles/redis/best-practices-development.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias, particularly in the 'Data Persistence or Data Backup' section, where PowerShell is mentioned as a tool for triggering data export before CLI or SDKs, and no explicit Linux or cross-platform command-line examples are provided. There are no Linux-specific tools or patterns mentioned, and the guidance on tooling is not platform-neutral. The absence of Linux/Bash examples and the ordering of PowerShell before CLI suggest a Windows-first approach.
Recommendations
  • When listing tools or command-line interfaces, mention cross-platform options (like Azure CLI) before platform-specific ones (like PowerShell).
  • Provide example commands for both Windows (PowerShell) and Linux (Bash/Azure CLI) where relevant, especially for common operations like data export/import.
  • Explicitly state when a tool or method is cross-platform, and provide links to relevant documentation for both Windows and Linux users.
  • Avoid assuming the use of Windows-specific tools or patterns unless the majority of the audience is known to be on Windows.
  • Add a section or callout for Linux/macOS users if there are any differences or additional considerations.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/migrate/migrate-overview.md ...s/blob/main/articles/redis/migrate/migrate-overview.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets for export/import operations, linking to PowerShell documentation, and mentioning a compiled Windows binary for a migration tool before its source code. There are no explicit Linux/bash examples or references to Linux-native tools, and the order of presentation favors Windows-centric approaches.
Recommendations
  • Provide equivalent bash/CLI examples for export/import operations, not just PowerShell.
  • Link to both Windows and Linux instructions or clarify cross-platform compatibility for CLI commands.
  • When mentioning downloadable tools, indicate if they are cross-platform or provide Linux build instructions.
  • Avoid referencing only PowerShell cmdlets; include Azure CLI and bash scripting alternatives.
  • Explicitly state OS compatibility for all tools and commands, and ensure Linux users are not left out of migration guidance.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/how-to-persistence.md ...re-docs/blob/main/articles/redis/how-to-persistence.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples before Azure CLI, mentioning PowerShell scripting for automation, and omitting any Linux-specific shell (e.g., Bash) or cross-platform scripting examples. There is no mention of Linux tools or guidance for Linux users, and the scripting automation section only references PowerShell and Azure CLI, with PowerShell listed first.
Recommendations
  • Provide Bash shell examples alongside PowerShell and Azure CLI for all command-line instructions.
  • When discussing automation, mention Bash scripts and Linux cron jobs as alternatives to PowerShell scripting.
  • Alternate the order of examples (sometimes show Azure CLI or Bash first) to avoid always privileging Windows/PowerShell.
  • Explicitly state that Azure CLI commands work cross-platform and, where relevant, show example commands in both Windows (PowerShell) and Linux (Bash) syntax.
  • Add a note or section for Linux/macOS users, clarifying any differences or additional steps required.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/redis-cache-arm-provision.md .../blob/main/articles/redis/redis-cache-arm-provision.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting PowerShell examples alongside Azure CLI, but omits explicit Linux/bash examples. PowerShell is used for both deployment and cleanup, and the CLI example references a Bicep file rather than the ARM template file described earlier. There are no bash shell or Linux-specific instructions, and PowerShell is presented as the default scripting language for resource cleanup.
Recommendations
  • Add explicit bash/Linux shell examples for deploying and cleaning up resources, using az CLI with ARM template files (e.g., az deployment group create --resource-group exampleRG --template-file azuredeploy.json).
  • Ensure that CLI examples reference the ARM template file (azuredeploy.json) as described in the instructions, not just Bicep files.
  • Provide parity in cleanup instructions by including az CLI commands for deleting resource groups (e.g., az group delete --name <resourceGroupName> --yes --no-wait).
  • Where scripting is shown, offer both PowerShell and bash equivalents, and avoid presenting PowerShell as the default unless the context is Windows-specific.
  • Consider a tabbed or side-by-side format for all command-line examples, with clear labels for PowerShell, Azure CLI (bash), and, if relevant, Cloud Shell.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/private-link.md ...cs/azure-docs/blob/main/articles/redis/private-link.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are presented before Azure CLI examples, and the PowerShell section is more detailed (including retrieval and removal commands). The documentation refers to 'scripts' and 'commands' in a way that assumes familiarity with PowerShell, and the Azure portal UI instructions use terminology and screenshots that are more familiar to Windows users. There are no explicit Linux-specific instructions or examples, and the CLI examples are not highlighted as the primary or preferred method.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid implying PowerShell is the default or preferred method.
  • Ensure parity in the depth and breadth of examples for both PowerShell and Azure CLI, including retrieval and removal operations.
  • Add explicit notes that both Azure CLI and PowerShell are cross-platform, and clarify that CLI commands work natively on Linux/macOS.
  • Where possible, include Linux/macOS-specific tips or troubleshooting notes (e.g., shell syntax differences, environment variable usage).
  • Consider providing Bash script equivalents for multi-step operations, and clarify that the Azure portal is accessible from any OS.
  • Avoid using Windows-centric terminology or UI references unless necessary, or provide equivalent guidance for non-Windows users.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/how-to-active-geo-replication.md ...b/main/articles/redis/how-to-active-geo-replication.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring active geo-replication, but it lists PowerShell as a primary automation method alongside CLI, and does not mention or provide any Linux-specific shell (e.g., Bash) examples. There is no explicit mention of Linux or cross-platform scripting, and PowerShell is traditionally associated with Windows environments, which may give the impression of Windows preference. Additionally, there are no examples or guidance for Linux-native tools or scripting environments.
Recommendations
  • Explicitly state that Azure CLI commands work cross-platform (Windows, Linux, macOS) and can be run in Bash or other shells.
  • Provide example commands using Bash (or generic shell) where appropriate, especially for automation scenarios.
  • Clarify that PowerShell Core is available cross-platform, but also mention that users on Linux can use Bash and Azure CLI for all operations.
  • Consider including a section or note for Linux/macOS users, highlighting any differences or confirming parity.
  • Avoid presenting PowerShell as the only or primary scripting/automation option; ensure CLI/Bash examples are equally prominent.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/how-to-scale.md ...cs/azure-docs/blob/main/articles/redis/how-to-scale.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting PowerShell as the first and primary scripting example, mentioning Azure PowerShell before Azure CLI in both the introduction and the step-by-step instructions. The only explicit scripting example outside the Azure CLI is for PowerShell, with no mention of Bash, Linux shell, or cross-platform scripting environments. The Azure CLI examples are present, but PowerShell is consistently given prominence, and there are no Linux-specific considerations or examples.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more commonly used in Linux environments.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample Bash shell usage where appropriate.
  • Add a section or note for Linux users, highlighting any platform-specific considerations (such as authentication, environment variables, or prerequisites).
  • Where PowerShell is referenced, clarify that it is available cross-platform, but also provide equivalent Bash or shell script examples for Linux users.
  • Ensure that documentation metadata and custom tags do not prioritize PowerShell over CLI (e.g., avoid 'devx-track-azurepowershell' without 'devx-track-bash' or similar).
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/redis-modules.md ...s/azure-docs/blob/main/articles/redis/redis-modules.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell and Windows-centric tools (such as the Azure PowerShell module) before or instead of Linux equivalents. In the section on configuring module parameters, only PowerShell, Azure CLI, and REST API are mentioned, but the PowerShell link is called out explicitly, and there are no Linux-specific shell or scripting examples. There are no bash, shell, or Linux command-line examples or references, and no mention of Linux tools or patterns. This may make Linux users feel less supported or require extra effort to adapt instructions.
Recommendations
  • Include explicit bash/shell examples alongside PowerShell for all command-line instructions.
  • When referencing management tools, mention cross-platform tools (like Azure CLI) first, and clarify their compatibility with Linux/macOS.
  • Provide links to Linux-specific documentation or examples where available.
  • Avoid listing PowerShell or Windows tools before cross-platform or Linux-native alternatives.
  • Add a note clarifying that Azure CLI and REST API are fully supported on Linux, and provide example usage in a Linux shell context.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/troubleshoot-connectivity.md .../blob/main/articles/redis/troubleshoot-connectivity.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing a connectivity test example using PSPING in PowerShell without offering an equivalent Linux command or tool. The use of PSPING and PowerShell is Windows-specific, and there is no mention of Linux alternatives (such as nc, telnet, or nmap). Additionally, the Windows example appears before any Linux-specific troubleshooting steps, and Linux guidance is limited to a single note about TCP settings, lacking actionable troubleshooting commands.
Recommendations
  • Provide Linux equivalents for connectivity testing, such as using 'nc', 'telnet', or 'nmap' to check port connectivity to the Redis instance.
  • When introducing tools like PSPING, mention both Windows and Linux options together, or present Linux examples first if the majority of Azure workloads are Linux-based.
  • Expand the 'Linux-based client application' section to include actionable troubleshooting steps and commands, not just a reference to a GitHub issue.
  • Where possible, use cross-platform tools (like redis-cli) as primary examples, and clearly indicate platform-specific instructions in separate subsections.
  • Review the order of examples to ensure Linux and Windows are given equal prominence, or alternate which platform appears first in each section.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/dotnet-how-to-use-azure-redis-cache.md .../articles/redis/dotnet-how-to-use-azure-redis-cache.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented towards Windows development environments, specifically Visual Studio and .NET Framework. All setup and usage instructions assume the use of Visual Studio (a Windows-only IDE for .NET Framework), and there are no instructions or examples for Linux users or for using cross-platform tools like Visual Studio Code or the .NET CLI. There are no mentions of Linux-specific installation steps, command-line instructions, or alternative editors, and the only way to run the sample is via Visual Studio's Ctrl+F5 shortcut.
Recommendations
  • Add instructions for setting up and running the sample using the .NET CLI (dotnet new, dotnet add package, dotnet run), which works on Linux, macOS, and Windows.
  • Include guidance for using Visual Studio Code as an alternative to Visual Studio, with steps for installing required extensions and running/debugging the app.
  • Provide explicit Linux and macOS prerequisites (e.g., installing .NET SDK, using a terminal) alongside Windows/Visual Studio instructions.
  • Replace or supplement Visual Studio-specific instructions (like right-clicking to manage NuGet packages) with equivalent command-line alternatives.
  • Mention how to edit configuration files and run the application from the terminal on Linux/macOS.
  • Ensure screenshots and UI references are either cross-platform or have Linux/macOS equivalents.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/how-to-persistence.md ...re-docs/blob/main/articles/redis/how-to-persistence.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell examples before Azure CLI, and by referencing PowerShell scripting for automation without mentioning Bash or Linux scripting alternatives. There are no explicit Linux or Bash examples, and the scripting guidance implicitly assumes a Windows environment.
Recommendations
  • Provide Bash/Linux shell script examples alongside PowerShell for automation tasks, especially for exporting data.
  • When mentioning scripting (e.g., 'automated scripts using PowerShell or Azure CLI'), explicitly reference Bash or Linux shell scripting as an option.
  • Alternate the order of PowerShell and Azure CLI examples, or present them in parallel, to avoid the impression of Windows-first bias.
  • Include notes or links for Linux users on how to install and use the Azure CLI and relevant tools.
  • Ensure screenshots and UI references are OS-neutral or include Linux/macOS variants if applicable.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/how-to-active-geo-replication.md ...b/main/articles/redis/how-to-active-geo-replication.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
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
← Previous Page 3 of 6 Next →