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/how-to-import-export-data.md
.../blob/main/articles/redis/how-to-import-export-data.md
High Priority
View Details →
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.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Azure PowerShell examples before Azure CLI, using PowerShell for resource cleanup, and omitting explicit Linux shell (bash) or cross-platform instructions. The 'Deploy to Azure' button and portal-centric workflow also favor Windows users, while Linux users may prefer CLI or automation. There are no bash or Linux-specific examples, and PowerShell is used exclusively for cleanup.
Recommendations
- Add bash/Linux shell examples for deployment and cleanup alongside PowerShell.
- Present Azure CLI examples before or alongside PowerShell to emphasize cross-platform support.
- Include notes or sections on running commands from Linux/macOS terminals.
- Replace or supplement PowerShell-only cleanup instructions with Azure CLI equivalents.
- Clarify that both CLI and PowerShell are cross-platform, but show examples for both environments.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page shows evidence of Windows bias by referencing PowerShell cmdlets (Export/Import), mentioning AzCopy (primarily a Windows tool) for file transfer, and providing no equivalent Linux CLI or shell examples. Windows tools and patterns are mentioned before any Linux alternatives, and there are no explicit instructions or examples for Linux users (e.g., Bash, Linux CLI, or Linux-native tools).
Recommendations
- Provide Linux-specific examples for exporting and importing RDB files, such as using Bash scripts or the Azure CLI.
- Mention and demonstrate Linux-native tools for file transfer, such as 'azcopy' on Linux, 'scp', or 'rsync', alongside AzCopy.
- Include instructions for using Azure CLI (az redis) for migration tasks, as it is cross-platform.
- Present PowerShell and Linux/Bash examples side-by-side where relevant, ensuring parity.
- Explicitly state that migration steps can be performed on both Windows and Linux, and clarify any platform-specific differences.
Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/configure.md
...tDocs/azure-docs/blob/main/articles/redis/configure.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page for configuring Azure Managed Redis demonstrates subtle Windows bias. References to PowerShell and Windows-centric tools appear before or instead of cross-platform or Linux alternatives. For example, the 'Export template' section links to deploying resources with Azure Resource Manager templates using PowerShell, without mentioning Azure CLI or Bicep. There are no explicit Linux or cross-platform command-line examples, nor references to Linux-specific tools or workflows. The documentation assumes use of the Azure portal and Windows-native automation, with no parity for Linux users.
Recommendations
- Include Azure CLI and Bicep examples alongside PowerShell for resource deployment and automation tasks.
- Explicitly mention that all features are accessible from Linux/macOS environments and provide relevant command-line examples.
- Add references to cross-platform tools (e.g., Azure CLI, REST API) in sections that currently only mention PowerShell.
- Ensure screenshots and walkthroughs include both Windows and Linux terminal environments where applicable.
- Review all links and instructions to ensure Linux users are not excluded or forced to adapt Windows-specific workflows.
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 →
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.
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 →
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).
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 →
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.
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 →
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.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools (Visual Studio), Windows-centric workflows (right-clicking in Visual Studio, using Ctrl+F5), and omitting any mention of Linux equivalents or cross-platform development environments. There are no instructions for running the sample on Linux, nor are alternative IDEs or command-line workflows provided.
Recommendations
- Add instructions for setting up and running the sample on Linux, including using .NET Core/SDK and command-line tools (e.g., dotnet CLI).
- Mention and provide examples for cross-platform editors such as VS Code, JetBrains Rider, or using the terminal.
- Include Linux-specific steps for installing dependencies, running the app, and editing configuration files.
- Clarify that StackExchange.Redis and the sample code can be run on Linux and macOS, not just Windows.
- Provide equivalent keyboard shortcuts and commands for building and running the app on non-Windows platforms.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell examples first and in detail, with no Linux-specific shell (bash) examples. The CLI examples are platform-neutral, but there are no explicit Linux or macOS shell commands, nor is there mention of Linux tooling or patterns. The only scripting example mentioned is PowerShell, which is primarily used on Windows.
Recommendations
- Add explicit Bash shell examples for Linux/macOS users alongside PowerShell examples.
- Mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample Bash scripts for automation.
- Include references to Linux-native tools or scripting environments (e.g., cron jobs for scheduled exports) where appropriate.
- Reorder examples so that platform-neutral (CLI) or Linux/Bash examples are presented before or alongside PowerShell.
- Clarify that PowerShell Core is cross-platform, but provide guidance for Linux users who may prefer Bash.
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 →
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.
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 →
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.
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 →
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).
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 →
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.
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 →
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.
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 →
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.
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 →
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.
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 →
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.
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 →
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.
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 →
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.
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 →
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.
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 →
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.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools, patterns, and examples. It references Windows-specific concepts (such as ThreadPool, performance counters, and .NET/StackExchange.Redis exceptions) without providing equivalent Linux guidance or examples. Linux is only briefly mentioned in a single section, and there are no Linux-specific troubleshooting commands or monitoring instructions. The use of XML configuration for RedisSessionStateProvider also assumes a .NET/Windows environment, and there is no parity for Linux-based client configuration or monitoring.
Recommendations
- Provide Linux-specific examples for monitoring CPU and network usage (e.g., using top, htop, vmstat, sar, or netstat).
- Include equivalent Linux troubleshooting steps for ThreadPool or concurrency issues (e.g., using systemd, ulimit, or thread/process monitoring tools).
- Offer sample configuration for popular Linux Redis clients (such as redis-py, Jedis, or Lettuce) alongside .NET examples.
- Document how to collect and interpret relevant metrics on Linux systems, not just via Azure portal or Windows performance counters.
- Ensure that all configuration and troubleshooting steps are presented for both Windows and Linux environments, or at least provide clear cross-references.
- When mentioning tools or patterns (such as performance counters or XML configuration), also mention or link to Linux-native alternatives.
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 →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by providing a PowerShell-based PSPING example for connectivity testing without offering a Linux equivalent. The use of PSPING (a Windows-specific tool) and PowerShell syntax, without mentioning or prioritizing Linux alternatives, may disadvantage Linux users. Additionally, the order and prominence of Windows tools and patterns suggest a Windows-first approach.
Recommendations
- Provide equivalent Linux connectivity testing examples, such as using 'nc' (netcat), 'telnet', or 'nmap' for port checks.
- When introducing a tool like PSPING, explicitly mention its platform specificity and immediately offer a Linux alternative.
- Balance the order of examples so that Linux and Windows instructions are presented together or alternate which comes first.
- Where possible, use cross-platform tools (e.g., redis-cli, curl) in examples.
- Add a table or section summarizing connectivity troubleshooting commands for both Windows and Linux.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio and IIS Express. All instructions and examples assume the use of Visual Studio 2019 on Windows, with no mention of Linux or cross-platform alternatives. There are no instructions for developing, running, or deploying the app from Linux or using non-Windows tools. The workflow and screenshots are all based on Windows tools and UI patterns.
Recommendations
- Add instructions for developing and running the ASP.NET app on Linux using cross-platform tools such as Visual Studio Code, JetBrains Rider, or the dotnet CLI.
- Include examples for editing configuration files and running the app using the dotnet CLI, not just Visual Studio and IIS Express.
- Provide deployment instructions using Azure CLI or GitHub Actions, which are platform-agnostic, in addition to Visual Studio publishing.
- Mention how to install required dependencies (e.g., .NET SDK, StackExchange.Redis) on Linux distributions.
- Add screenshots and workflow steps for Linux/macOS users where applicable.
- Clarify in the prerequisites that the instructions are Windows-specific, and provide a parallel section or links for Linux/macOS users.