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 76-100 of 144 flagged pages
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 page demonstrates a Windows bias by providing PowerShell examples and references before Azure CLI, emphasizing PowerShell as a primary automation tool, and omitting explicit Linux/bash shell examples. The use of PowerShell and the order in which it is presented may suggest a preference for Windows environments, potentially making the documentation less approachable for Linux users.
Recommendations
- Provide bash shell examples alongside PowerShell for all command-line operations, especially for Azure CLI commands.
- Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI commands can be run in bash, PowerShell, or CMD, and provide sample commands for each where syntax differs.
- Avoid referring to PowerShell as the default or primary automation tool; instead, present both PowerShell and CLI as equal options.
- Where possible, include screenshots or terminal output from both Windows and Linux environments to demonstrate parity.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is explicitly mentioned as a supported method for exporting and importing data, with direct links to PowerShell cmdlets. There are no equivalent Linux shell or Bash examples or references to cross-platform scripting. The mention of a compiled migration tool (redis-copy) links to a Windows .zip release first, and the order of instructions and examples tends to prioritize Windows-native tools and workflows.
Recommendations
- Provide Bash or cross-platform CLI examples alongside or before PowerShell examples for export/import operations.
- Reference az CLI as the primary method for scripting, as it is cross-platform, and only mention PowerShell as an alternative.
- When linking to migration tools, highlight both Windows and Linux installation options equally, and provide .tar.gz or Linux package links where available.
- Explicitly state that all instructions are applicable to both Windows and Linux unless otherwise noted.
- Include example commands for Linux environments (e.g., using Bash, curl, or wget for downloads, and Linux file paths).
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-AzRedisCache) as the only explicit automation examples, mentioning AzCopy (primarily a Windows tool) for file transfer, and not providing equivalent Linux/Unix command-line examples or tools. The PowerShell approach is mentioned before any Linux alternatives, and there are no bash, shell, or cross-platform CLI examples for key migration steps.
Recommendations
- Provide equivalent Linux/Unix shell command examples for exporting and importing RDB files, such as using Azure CLI (az redis) or REST API calls.
- Mention cross-platform tools for file transfer (e.g., Azure CLI az storage blob upload, or standard tools like scp/rsync) alongside or before AzCopy.
- When referencing PowerShell cmdlets, also provide the corresponding Azure CLI commands and highlight their cross-platform compatibility.
- Include explicit Linux/macOS workflow steps and code snippets for each migration scenario, ensuring parity with Windows/PowerShell instructions.
- Clarify that AzCopy and PowerShell are available on multiple platforms, but provide installation links and usage notes for Linux/macOS users.
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 Windows bias by prioritizing Azure PowerShell examples and workflows before Azure CLI, and by providing detailed PowerShell scripts for key operations. The portal-based instructions implicitly assume a GUI workflow common to Windows users. There is no mention of Linux-specific tools, shells, or considerations, and no explicit parity for Linux-native environments.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, and provide shell-agnostic variable syntax (e.g., export VAR=val for bash).
- Add Linux shell (bash) equivalents for any PowerShell-specific scripting or variable usage.
- Clarify that the Azure portal is web-based and platform-agnostic, but consider adding CLI-only workflows for users who prefer not to use a GUI.
- Where relevant, reference Linux-native tools (e.g., dig instead of nslookup) in troubleshooting or verification steps.
- Ensure that all automation and scripting examples are available in both PowerShell and bash/CLI formats, and that neither is presented as the default or primary method.
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 Tools
Powershell Heavy
Windows First
Summary
The documentation page exhibits subtle Windows bias, particularly in the section discussing configuration via management APIs. PowerShell is mentioned explicitly alongside REST API and Azure CLI, and the PowerShell link appears last, but no explicit Linux shell (bash) or cross-platform scripting examples are provided. There are no code snippets or command-line examples, but the only scripting tool mentioned by name is PowerShell, which is Windows-centric. There are no Linux-specific tools or workflows referenced, nor is there mention of Linux-first or cross-platform command-line usage.
Recommendations
- Include explicit bash/Azure CLI examples for configuring modules, especially for Linux users.
- When referencing management APIs, clarify that Azure CLI is cross-platform and provide sample commands for both bash and PowerShell.
- Avoid listing PowerShell as a primary or sole scripting example; if included, always pair with bash or CLI equivalents.
- Add a note or section highlighting cross-platform parity and how Linux/macOS users can accomplish the same tasks.
- Where possible, provide code snippets or command-line instructions for both Windows (PowerShell) and Linux (bash/CLI) environments.
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 commands alongside Azure CLI, but with CLI examples referencing Bicep files (not ARM JSON), and PowerShell being used for cleanup. There are no explicit Linux shell or cross-platform cleanup examples, and the PowerShell example is the only one provided for deleting resources. The use of 'azurepowershell-interactive' for cleanup further centers Windows tooling. Additionally, the Azure Portal (web UI) is platform-agnostic but is not a substitute for command-line parity.
Recommendations
- Provide equivalent Bash (Linux/macOS) cleanup commands using Azure CLI, e.g., 'az group delete --name <resourceGroupName>'.
- Ensure that ARM template deployment examples use the same template file (e.g., 'azuredeploy.json') for both CLI and PowerShell, and show both commands side-by-side.
- Avoid using only PowerShell for interactive scripts; provide Bash alternatives or use Azure CLI for all cross-platform scenarios.
- Clearly label which commands are cross-platform and which are Windows-specific, and avoid defaulting to PowerShell for tasks that can be accomplished with Azure CLI.
- Consider including a table summarizing all deployment and cleanup options for Windows, Linux, and macOS users.
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.
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/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
Move from Basic, Standard, Premium, and Enterprise tiers to Azure Managed Redis
...s/blob/main/articles/redis/migrate/migrate-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides migration guidance for Azure Cache for Redis to Azure Managed Redis and is generally cross-platform. However, in the migration steps for exporting/importing RDB files, PowerShell cmdlets are mentioned explicitly, with no Linux/macOS CLI or Bash alternatives provided. Additionally, PowerShell is referenced before any other tooling, which may create friction for non-Windows users.
Recommendations
- Add equivalent Azure CLI commands for export/import operations alongside PowerShell examples.
- Include Bash or shell script examples for common migration steps.
- Where PowerShell is mentioned, clarify that Azure CLI and REST API alternatives exist and link to their documentation.
- Present cross-platform tooling (e.g., Azure CLI) before or alongside PowerShell to avoid Windows-first impression.
Redis
Quickstart: Use an Azure Redis cache in .NET Framework
.../articles/redis/dotnet-how-to-use-azure-redis-cache.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE), providing instructions that assume a Windows environment (e.g., right-clicking in Visual Studio, using Ctrl+F5), and omitting any guidance for Linux or macOS users. There are no examples or instructions for using cross-platform tools (such as VS Code, JetBrains Rider, or command-line approaches), nor are there any Linux/macOS-specific setup or run instructions.
Recommendations
- Add instructions for setting up and running the sample using cross-platform IDEs (e.g., VS Code, JetBrains Rider) and command-line tools (dotnet CLI).
- Include Linux/macOS-specific steps for installing .NET and running the sample.
- Provide alternative commands for building and running the app (e.g., 'dotnet run' instead of Ctrl+F5).
- Mention package installation via command line (e.g., 'dotnet add package') as an alternative to Visual Studio's NuGet UI.
- Clarify that the sample can be run on Linux/macOS and provide troubleshooting tips for those platforms.
Redis
Configure active geo-replication for Azure Managed Redis instances
...b/main/articles/redis/how-to-active-geo-replication.md
Medium 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 and detail as CLI, despite being Windows-specific. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is presented as a primary automation option alongside CLI, which may create friction for Linux/macOS users. No Linux-specific tools or patterns are mentioned, and there is no guidance for Linux users regarding prerequisites or environment setup.
Recommendations
- Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Add explicit Bash shell examples for Azure CLI commands, demonstrating usage in Linux/macOS terminals.
- De-emphasize PowerShell as a primary automation method, or clearly label it as Windows-specific.
- Include a section or note for Linux/macOS users about environment setup (e.g., installing Azure CLI, authentication).
- Ensure that all automation and scripting examples are available in a cross-platform format.
Redis
Use Microsoft Entra for cache authentication with Azure Managed Redis
...s/blob/main/articles/redis/entra-for-authentication.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation references a PowerShell script as the primary troubleshooting tool for validating Microsoft Entra tokens with Azure Managed Redis, without mentioning equivalent tools or scripts for Linux/macOS users. No Linux/macOS-specific instructions or cross-platform alternatives are provided for this critical troubleshooting step. The rest of the documentation is generally platform-neutral, but the reliance on PowerShell for diagnostics introduces a notable Windows bias.
Recommendations
- Provide a cross-platform (e.g., Bash, Python) script or CLI-based instructions for token validation and troubleshooting that work on Linux and macOS.
- Explicitly mention whether the PowerShell script can be run using PowerShell Core on Linux/macOS, and provide installation instructions if so.
- Wherever scripts or tools are referenced, include both Windows and Linux/macOS usage examples.
- Add a note or section for Linux/macOS users outlining equivalent troubleshooting steps.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. PowerShell cmdlets are referenced for export/import operations, and AzCopy (a Microsoft tool) is suggested for file transfers without mentioning Linux/macOS alternatives. There are no explicit Linux or macOS command-line examples, and Windows-centric tools are mentioned before any cross-platform or Linux-native approaches.
Recommendations
- Provide equivalent Linux/macOS command-line instructions for exporting/importing RDB files (e.g., using redis-cli, curl, or REST APIs).
- Mention and give examples for Linux-native file transfer tools such as scp, rsync, or curl alongside AzCopy.
- Include Bash or shell script examples for migration steps, not just PowerShell.
- Clarify that PowerShell cmdlets are available on Linux/macOS (if true), or provide alternative instructions.
- Explicitly state platform requirements or parity for all migration tools and steps.
Redis
Configure data persistence - Azure Managed Redis
...re-docs/blob/main/articles/redis/how-to-persistence.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides detailed instructions and examples for configuring data persistence in Azure Managed Redis, with a notable emphasis on PowerShell commands and examples. PowerShell is a Windows-centric tool, and its examples are presented before Azure CLI examples. There are no explicit Linux/macOS shell examples (e.g., Bash), nor is there guidance for Linux-specific workflows or tools. This creates friction for Linux/macOS users who may not use PowerShell and expect Bash or other native shell instructions.
Recommendations
- Add Bash shell examples for Azure CLI commands, demonstrating usage on Linux/macOS.
- Explicitly mention that Azure CLI commands work cross-platform and can be run in Bash, zsh, or other shells.
- Reorder examples so that Azure CLI (cross-platform) instructions are presented before PowerShell (Windows-centric) instructions.
- Include notes or links for installing and using Azure CLI on Linux/macOS.
- Avoid language that implies PowerShell is the primary or preferred method for automation.
Redis
Move from Basic, Standard, Premium, and Enterprise tiers to Azure Managed Redis
...s/blob/main/articles/redis/migrate/migrate-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page demonstrates Windows bias primarily through the exclusive mention and use of PowerShell cmdlets for export/import operations, with no equivalent Linux/macOS CLI or script examples. The migration instructions reference PowerShell before any cross-platform alternatives, and do not provide parity for Linux users in critical migration steps.
Recommendations
- Add Azure CLI and/or Bash script examples for export/import operations alongside PowerShell instructions.
- Explicitly mention cross-platform tools and provide usage examples for Linux/macOS environments (e.g., Azure CLI, REST API, or open-source migration tools).
- Reorder instructions so that platform-agnostic methods (Azure Portal, REST API, Azure CLI) are presented before or alongside Windows-specific tools.
- Clarify which steps are platform-independent and which require OS-specific tooling.
- Link to documentation for Linux/macOS users where relevant.
Redis
Azure Managed Redis with Azure Private Link
...cs/azure-docs/blob/main/articles/redis/private-link.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Portal-based instructions (GUI) are platform-neutral, but all scripting examples for Azure PowerShell use Windows-centric tools and syntax, and PowerShell is presented before Azure CLI. There are no Linux/macOS-specific notes or parity checks for scripting, and PowerShell is traditionally associated with Windows. Azure CLI examples (cross-platform) are present, but appear after PowerShell, and there are no bash or shell script examples for Linux/macOS users.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly note that Azure CLI commands work on Linux/macOS and Windows, and provide installation links for each OS.
- Add bash/shell script examples for common tasks, or clarify that Azure CLI commands can be used directly in Linux/macOS terminals.
- Where PowerShell is used, mention that PowerShell Core is available cross-platform, and provide installation instructions for Linux/macOS.
- Add troubleshooting notes for Linux/macOS users where relevant (e.g., DNS resolution, network policies).
Redis
Using Redis modules with Azure Managed Redis
...s/azure-docs/blob/main/articles/redis/redis-modules.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page references Windows-specific tools (PowerShell) and links to PowerShell documentation before Linux alternatives. Examples for configuring modules mention PowerShell and REST API, but do not provide explicit Linux or cross-platform CLI examples. There is no mention of Linux/macOS-specific instructions or parity in tooling, and the Azure CLI is referenced only as a link, not as an example.
Recommendations
- Provide explicit Azure CLI examples for module configuration alongside PowerShell, demonstrating parity for Linux/macOS users.
- List cross-platform tools (Azure CLI, REST API) before or alongside Windows-specific tools (PowerShell) when describing management options.
- Include sample commands for Linux/macOS environments, such as bash scripts or CLI usage, especially in sections discussing configuration.
- Clarify that all management APIs and tools are cross-platform where applicable, and highlight any differences in usage between platforms.
Redis
Deploy Azure Cache for Redis by using Azure Resource Manager template
.../blob/main/articles/redis/redis-cache-arm-provision.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides deployment instructions using both Azure CLI and Azure PowerShell, but PowerShell examples are shown alongside CLI without clear prioritization. The cleanup section only provides a PowerShell example, omitting an equivalent Azure CLI (Linux/macOS-friendly) command. There is a subtle Windows bias in example ordering and tool selection, which may create friction for Linux/macOS users.
Recommendations
- Add Azure CLI examples for resource cleanup alongside PowerShell, ensuring parity for Linux/macOS users.
- When presenting multiple tool options (CLI, PowerShell), list Azure CLI first or equally to avoid Windows-first perception.
- Explicitly mention that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Provide links or references to installing and using Azure CLI on Linux/macOS.
Redis
Troubleshoot connectivity in Azure Managed Redis
.../blob/main/articles/redis/troubleshoot-connectivity.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias in the troubleshooting section by exclusively recommending PSPING (a Windows/PowerShell tool) for connectivity testing, providing a PowerShell example, and omitting Linux/macOS alternatives (e.g., netcat, telnet, nmap). The order of examples also places Windows tooling before any mention of Linux equivalents, and no Linux-specific command-line connectivity test is shown.
Recommendations
- Add Linux/macOS equivalents for PSPING, such as netcat (nc), telnet, or nmap, with example commands.
- Present connectivity testing examples for both Windows and Linux/macOS side by side.
- Explicitly mention which tools are available on which platforms.
- Avoid assuming PowerShell is the default shell for all users; provide Bash examples where appropriate.
Redis
Best practices for development for Azure Managed Redis
...blob/main/articles/redis/best-practices-development.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page mentions PowerShell as a tool for triggering data export operations before mentioning CLI or SDK tools, and does not provide explicit Linux/macOS examples or parity in tooling references. The order and emphasis on PowerShell may create friction for Linux/macOS users, though workarounds exist via CLI or SDK.
Recommendations
- Explicitly mention cross-platform tools (e.g., Azure CLI) before or alongside PowerShell.
- Provide example commands for both Azure CLI and PowerShell when discussing operations like data export.
- Clarify that all operations can be performed from Linux/macOS using CLI or SDK, and link to relevant documentation.
- Avoid listing Windows-specific tools first unless there is a technical reason.
Redis
Quickstart: Use an Azure Redis cache in .NET Framework
.../articles/redis/dotnet-how-to-use-azure-redis-cache.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page is heavily oriented toward Windows development environments, specifically Visual Studio and .NET Framework. All setup and usage instructions assume Visual Studio on Windows, with no mention of Linux/macOS equivalents (e.g., VS Code, JetBrains Rider, or CLI workflows). There are no Linux/macOS-specific instructions or examples, and Windows tools/patterns (Visual Studio, NuGet GUI) are referenced exclusively.
Recommendations
- Add instructions for setting up and running the sample on Linux/macOS, including using .NET Core/SDK and alternative editors like VS Code.
- Provide command-line examples for installing NuGet packages (e.g., 'dotnet add package') instead of only Visual Studio GUI steps.
- Clarify that the code works cross-platform and provide guidance for running the sample on Linux/macOS (e.g., 'dotnet run').
- Mention and link to cross-platform development tools and environments.
- Include screenshots or terminal output for Linux/macOS where appropriate.
Redis
Use Microsoft Entra for cache authentication with Azure Managed Redis
...s/blob/main/articles/redis/entra-for-authentication.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the troubleshooting section, where only a PowerShell script is provided for validating Microsoft Entra tokens. There are no equivalent Linux/bash examples or tools mentioned for Linux/macOS users. The rest of the documentation is generally platform-neutral, focusing on Azure Portal and client libraries, but the exclusive use of PowerShell for diagnostics creates friction for non-Windows users.
Recommendations
- Provide a bash or cross-platform (e.g., Python) script for token validation alongside the PowerShell script.
- Explicitly mention if the PowerShell script can be run on PowerShell Core (pwsh) on Linux/macOS, or provide installation instructions.
- Wherever scripts or tools are referenced, include platform-agnostic alternatives or note their compatibility.
- Add troubleshooting steps or tools that Linux/macOS users can use without requiring Windows or PowerShell.
Redis
Configure data persistence - Azure Managed Redis
...re-docs/blob/main/articles/redis/how-to-persistence.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for configuring data persistence, with Azure CLI examples following. There is an explicit mention of using 'automated scripts using PowerShell or Azure CLI' for backups, but no mention of Bash, Linux shell scripting, or macOS-specific guidance. The PowerShell section appears first and is more verbose, which may signal a Windows-first approach. There are no Linux/macOS-specific instructions, troubleshooting tips, or references to platform differences, potentially leaving Linux/macOS users with less tailored guidance.
Recommendations
- Add Bash/Linux shell script examples for exporting data and configuring persistence, especially for common Linux environments.
- Present Azure CLI examples before or alongside PowerShell to avoid Windows-first ordering.
- Explicitly mention that Azure CLI works cross-platform and provide guidance for Linux/macOS users (e.g., installation links, environment notes).
- Include troubleshooting notes or tips for Linux/macOS users, such as file permissions, shell differences, or environment setup.
- Clarify that PowerShell Core is available on Linux/macOS if PowerShell usage is required, or provide equivalent Bash commands.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page exhibits moderate Windows bias, primarily through the use of Windows-specific tools (AzCopy, PowerShell cmdlets) for migration steps. PowerShell examples and references are given for exporting and importing data, with no equivalent Linux/macOS CLI or scripting alternatives mentioned. Windows tools are referenced before any cross-platform or Linux-native options, and there is no guidance for Linux users on how to perform these tasks using their preferred environments.
Recommendations
- Provide Linux/macOS equivalents for PowerShell cmdlets, such as Azure CLI commands for exporting and importing Redis data.
- Include examples using cross-platform tools (e.g., Azure CLI, REST API, or Python SDK) alongside PowerShell.
- Mention Linux-native file transfer tools (e.g., scp, rsync) as alternatives to AzCopy for copying RDB files.
- Explicitly state platform compatibility for each tool and command, and offer step-by-step instructions for Linux/macOS users.
- Reorder examples so that cross-platform or Linux options are presented before or alongside Windows-specific ones.