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 101-125 of 144 flagged pages
Redis Azure Managed Redis with Azure Private Link ...cs/azure-docs/blob/main/articles/redis/private-link.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows-centric tools (Azure PowerShell) are introduced before cross-platform alternatives (Azure CLI), and PowerShell examples are more detailed and appear first. The portal instructions are platform-neutral, but command-line automation is presented with a Windows-first approach, which may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform.
  • Explicitly state that Azure CLI works on Linux/macOS and Windows, while PowerShell is primarily Windows-focused.
  • Add Bash and/or Linux/macOS-specific notes or troubleshooting tips where relevant.
  • Ensure parity in detail and completeness between PowerShell and CLI sections.
  • Consider adding links to install Azure CLI on Linux/macOS.
GitHub Create Pull Request
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 →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates Windows bias primarily through the exclusive mention of PowerShell cmdlets for export/import operations and by referencing Windows-specific tools before cross-platform or Linux alternatives. While open-source migration tools are mentioned later, the initial migration instructions and examples focus on PowerShell, which is native to Windows. There are no Linux-specific CLI examples (e.g., Bash, Azure CLI), nor is parity established for Linux/macOS users in critical migration steps.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for export/import operations alongside PowerShell instructions.
  • Explicitly mention cross-platform compatibility for migration steps and tools, including how to perform them on Linux/macOS.
  • List open-source, platform-agnostic tools (e.g., redis-cli, redis-copy, RIOT) before or alongside PowerShell cmdlets.
  • Add notes or sections clarifying how Linux/macOS users can complete each migration step without relying on Windows-specific tools.
  • Ensure screenshots and walkthroughs are not exclusively from the Windows Azure Portal experience.
GitHub Create Pull Request
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 →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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 Azure CLI equivalent, which is more commonly used on Linux/macOS. There are no explicit Linux/macOS-specific instructions or notes, and the documentation does not mention platform differences or requirements for running PowerShell on non-Windows systems.
Recommendations
  • Add Azure CLI examples for all tasks, especially for resource cleanup, to ensure Linux/macOS users have clear guidance.
  • Explicitly mention that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • If PowerShell is shown, clarify that it is available on Linux/macOS and provide installation links or notes.
  • Consider showing CLI examples first, as it is the default on most platforms.
  • Add a note about platform compatibility for both CLI and PowerShell.
GitHub Create Pull Request
Redis Using Redis modules with Azure Managed Redis ...s/azure-docs/blob/main/articles/redis/redis-modules.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page references Windows-specific tools (PowerShell) and lists PowerShell before Linux equivalents (REST API, Azure CLI) when describing how to configure module parameters. There are no explicit Linux/macOS examples or mentions of Linux-specific tools, and the ordering of management tools puts PowerShell (Windows) last but still gives it equal prominence, with no parity in example commands or usage patterns for Linux/macOS users.
Recommendations
  • Provide explicit Linux/macOS examples using Azure CLI and REST API, including sample commands for configuring modules.
  • Add notes or sections clarifying cross-platform usage, such as how to perform tasks on Linux/macOS terminals.
  • Reorder management tool references to list Azure CLI (cross-platform) before PowerShell, or group them by platform.
  • Include screenshots or terminal snippets from Linux/macOS environments where relevant.
GitHub Create Pull Request
Redis Troubleshoot connectivity in Azure Managed Redis .../blob/main/articles/redis/troubleshoot-connectivity.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing a connectivity testing example using PSPING in PowerShell, a Windows-only tool, without offering a Linux/macOS equivalent. The example is presented immediately after the redis-cli section, with no mention of Linux-native alternatives like netcat, telnet, or nmap. This creates friction for Linux/macOS users who cannot use PSPING and must infer or research their own solutions.
Recommendations
  • Add Linux/macOS equivalents for connectivity testing, such as examples using netcat (nc), telnet, or nmap.
  • Explicitly mention that PSPING is a Windows-only tool and provide alternative commands for other platforms.
  • Present cross-platform examples side-by-side or in parallel sections to ensure parity.
  • Review other troubleshooting steps to ensure tools and instructions are not Windows-centric.
GitHub Create Pull Request
Redis Quickstart: Connect to Azure Managed Redis with TypeScript in a Node.js app ...re-docs/blob/main/articles/redis/nodejs-get-started.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a slight Windows bias in its code execution instructions. The 'Run the code' section uses the 'dos' code block type, which is typically associated with Windows command prompt, and does not provide equivalent Linux/macOS shell examples. There is no mention of Linux-specific tools or patterns, nor are Linux commands shown alongside Windows ones.
Recommendations
  • Provide code execution instructions using the 'bash' or 'sh' code block type, or show both Windows and Linux/macOS command examples side by side.
  • Explicitly mention that the commands (e.g., 'tsc', 'node index.js') work on Linux/macOS terminals as well as Windows.
  • Avoid using 'dos' code block type unless there are Windows-specific commands; use 'bash' for cross-platform compatibility.
  • Add a note or section clarifying any platform-specific steps or differences, if applicable.
GitHub Create Pull Request
Redis Deploy Azure Cache for Redis using Bicep ...lob/main/articles/redis/redis-cache-bicep-provision.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation consistently presents both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is always presented immediately after CLI, rather than as a secondary or platform-specific option. There are no Linux-specific instructions, nor any mention of platform differences or guidance for Linux/macOS users. The documentation implicitly assumes parity between CLI and PowerShell, but PowerShell is primarily used on Windows, which may suggest a subtle Windows bias.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows.
  • Add notes or callouts specifying which commands are platform-agnostic (CLI) and which are Windows-centric (PowerShell).
  • Consider presenting Azure CLI examples first, with PowerShell as an alternative for Windows users.
  • Include explicit instructions or troubleshooting tips for Linux/macOS environments, such as shell compatibility or installation links.
  • If PowerShell Core (cross-platform) is supported, clarify its usage and differences from Windows PowerShell.
GitHub Create Pull Request
Redis Use redis-cli with Azure Managed Redis ...docs/blob/main/articles/redis/how-to-redis-cli-tool.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page provides both Linux and Windows instructions for installing redis-cli, but Windows guidance is focused on using WSL rather than native Windows solutions. When discussing how to gather cache access information, Azure PowerShell is mentioned before Azure CLI, and both are listed before the Azure portal. There are no redis-cli usage examples specific to Windows (e.g., CMD or PowerShell), nor are there Linux-specific shell examples beyond installation. The page assumes Linux tools are used on Windows via WSL, which may not be ideal for all users.
Recommendations
  • Provide native Windows redis-cli installation instructions (e.g., using pre-built binaries or Chocolatey) for users who do not want to use WSL.
  • Include redis-cli usage examples for Windows Command Prompt and PowerShell, as well as for Linux shells.
  • List Azure CLI and Azure PowerShell access methods in a neutral order, or prioritize the cross-platform Azure CLI.
  • Explicitly mention Linux and macOS support in all relevant sections, not just in the alternatives.
  • Add troubleshooting notes for common platform-specific issues (e.g., TLS on Windows, path issues, etc.).
GitHub Create Pull Request
Redis Quickstart: Connect to Azure Managed Redis with TypeScript in a Node.js app ...re-docs/blob/main/articles/redis/nodejs-get-started.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page shows subtle Windows bias, notably in the 'Run the code' section where the code execution commands are presented using DOS-style formatting (tsc, node index.js) and output blocks, which can suggest a Windows-centric approach. There are no explicit Linux or cross-platform terminal examples, nor any mention of Linux-specific tools or shell commands. The Azure CLI example is cross-platform, but there is no parity for Linux shell usage elsewhere. No PowerShell-specific commands or Windows-only tools are present, but the formatting and lack of Linux examples indicate a mild Windows-first bias.
Recommendations
  • Provide both Windows (cmd) and Linux/macOS (bash/sh) command examples for running the code, e.g., use generic shell blocks or show both.
  • Use neutral code block formatting (e.g., 'bash' or 'sh') for commands that are cross-platform.
  • Explicitly mention that the instructions apply to all platforms, or add notes for Linux/macOS users where relevant.
  • Include sample output blocks that do not use DOS formatting, or provide both styles.
  • Where tools are cross-platform (like Azure CLI), clarify their usage on different operating systems.
GitHub Create Pull Request
Redis Deploy Azure Cache for Redis using Bicep ...lob/main/articles/redis/redis-cache-bicep-provision.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell examples are presented alongside CLI examples in every section, and PowerShell is a Windows-centric tool. There is no explicit mention of Linux-specific patterns, nor is there guidance for Bash scripting or shell environments commonly used on Linux. The documentation does not clarify that Azure CLI is cross-platform and does not provide Linux-specific context or troubleshooting.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and works on Windows, Linux, and macOS.
  • Provide examples of running Azure CLI commands in Bash or other Linux shells, including installation instructions for Linux.
  • Add notes or sections for Linux users, such as common troubleshooting steps or environment setup.
  • Consider reordering examples to present Azure CLI first, emphasizing its cross-platform nature.
  • Avoid implying parity between PowerShell and CLI unless both are equally supported on all platforms; clarify platform limitations if any exist.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/how-to-redis-cli-tool.md ...docs/blob/main/articles/redis/how-to-redis-cli-tool.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by listing Windows-specific instructions (WSL) before Linux alternatives in several sections, and by mentioning Azure PowerShell as a method for gathering access information before Linux-native tools. However, Linux installation and usage are covered well, and most examples use cross-platform commands.
Recommendations
  • Present Linux instructions before Windows-specific alternatives, especially in installation and connection sections.
  • Include Linux-native command-line tools (e.g., bash scripts, curl) as alternatives to Azure PowerShell for gathering access information.
  • Clarify that redis-cli usage and examples are identical across platforms, and explicitly mention macOS support where relevant.
  • Add explicit Linux terminal examples for gathering cache access information (e.g., using Azure CLI in bash).
  • Avoid framing Windows as the default or primary platform for redis-cli usage; emphasize cross-platform parity.
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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by presenting PowerShell instructions before Azure CLI instructions in the 'How to scale' section. PowerShell is a Windows-centric tool, and its precedence may suggest a prioritization of Windows workflows. However, Azure CLI examples are present and use cross-platform syntax, and no Windows-only tools or patterns are exclusively mentioned. There are no missing Linux examples, but the ordering and emphasis could be improved for Linux parity.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Explicitly state that both Azure CLI and PowerShell are supported on Windows, Linux, and macOS, clarifying cross-platform compatibility.
  • Add Bash or shell script snippets where appropriate to demonstrate Linux-native usage.
  • Avoid language that implies PowerShell is the default or preferred tool unless justified by usage statistics.
  • Consider adding a short section on using these commands in Linux environments, including installation and authentication notes.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/nodejs-get-started.md ...re-docs/blob/main/articles/redis/nodejs-get-started.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by using DOS-style code blocks for build/run commands (tsc, node index.js) and not providing explicit Linux/macOS equivalents. The instructions and examples do not mention platform-specific differences or provide parity for Linux users, such as using bash or sh for running commands. No PowerShell-specific commands are present, but the overall presentation assumes a Windows environment by default.
Recommendations
  • Provide explicit Linux/macOS command examples alongside Windows (e.g., use bash code blocks for build/run steps).
  • Clarify that the commands work cross-platform and note any platform-specific considerations.
  • Use neutral code block formatting (e.g., 'bash' instead of 'dos') for commands that are not Windows-specific.
  • Mention common Linux tools or patterns where relevant, such as using terminal or shell commands.
  • Add a note or section on running the sample on Linux/macOS, including any required dependencies or environment setup.
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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a 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 instructions. The PowerShell scripting section is more detailed and comes before CLI, which is the cross-platform alternative. There are no explicit Linux-specific instructions, nor are Linux tools or shell patterns mentioned. The CLI examples are present, but not prioritized, and there is no mention of Bash scripting, Linux shell environments, or Linux-specific troubleshooting.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform support.
  • Include explicit instructions or notes for Linux/macOS users, such as using Bash or Zsh shells, and clarify that Azure CLI works natively on these platforms.
  • Add troubleshooting steps or verification commands using Linux tools (e.g., dig, host, curl) in addition to nslookup.
  • Mention that the Azure portal is accessible from any OS and clarify any OS-specific limitations or considerations.
  • Where scripting is shown, provide both PowerShell and Bash script equivalents for resource creation and management.
  • Add references to Linux-specific documentation or best practices for Azure Managed Redis and Private Link.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/redis-cache-bicep-provision.md ...lob/main/articles/redis/redis-cache-bicep-provision.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment and resource management tasks. However, PowerShell examples are given equal prominence to Azure CLI, despite PowerShell being primarily a Windows tool. There is no explicit mention of Linux-specific considerations, nor are there examples for Bash scripting or Linux shell environments. The documentation does not acknowledge that PowerShell is less commonly used on Linux, and does not provide guidance for Linux users beyond the CLI.
Recommendations
  • Explicitly state that Azure CLI commands work cross-platform (Windows, Linux, macOS), while PowerShell is primarily a Windows tool (though available on Linux).
  • Consider listing Azure CLI examples before PowerShell examples to avoid implicit Windows-first bias.
  • Add notes or sections for Linux users, such as how to install Azure CLI on Linux, or troubleshooting tips for Linux environments.
  • Include Bash script examples for common tasks, or link to Linux-specific deployment guides.
  • Clarify that PowerShell is optional and not required for Linux users.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/python-get-started.md ...re-docs/blob/main/articles/redis/python-get-started.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by showing only Windows-style console output (e.g., C:\utils\python-quickstart>), and does not provide any Linux/macOS terminal examples or instructions. There are no references to Linux-specific tools, shell commands, or file paths, and the command-line instructions (such as az login) are not shown in a cross-platform manner.
Recommendations
  • Add Linux/macOS terminal output examples alongside Windows examples (e.g., $ python quickstart-amr.py).
  • Mention that the instructions work on Linux/macOS as well as Windows, and clarify any platform-specific differences.
  • Show file paths and command-line usage in both Windows (C:\path) and Linux/macOS (/home/user/path) formats where relevant.
  • Explicitly state that Azure CLI commands (e.g., az login) work on all platforms, and provide examples for Bash/zsh.
  • If mentioning the Azure developer command line (azd), clarify installation and usage steps for Linux/macOS.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/python-get-started.md ...re-docs/blob/main/articles/redis/python-get-started.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by showing only Windows-style command line output (e.g., C:\utils\python-quickstart>), and does not provide any Linux or macOS terminal examples. There is no mention of Linux-specific instructions or parity in command-line usage, nor are Linux shell commands (such as bash/zsh) shown. The instructions for running the code and authenticating with Azure CLI do not clarify cross-platform usage, and the example output is exclusively Windows-oriented.
Recommendations
  • Add Linux/macOS terminal examples alongside Windows examples (e.g., show `$ python quickstart-amr.py` output).
  • Explicitly mention that the instructions and code work on Linux/macOS as well as Windows.
  • Include notes about installing Python and Azure CLI on Linux/macOS, with relevant links.
  • Show example commands for authenticating with Azure CLI on Linux/macOS (e.g., using bash/zsh).
  • Avoid using Windows-specific paths in examples; use generic or cross-platform paths, or provide both.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/how-to-redis-cli-tool.md ...docs/blob/main/articles/redis/how-to-redis-cli-tool.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation gives Windows-specific instructions before Linux alternatives in several places, such as recommending WSL for Windows users and referencing Windows Terminal. It also lists Azure PowerShell as a primary method for gathering cache access information, alongside Azure CLI and Portal, but does not mention Linux-specific tools or shells. However, installation and usage examples for redis-cli are provided for both Linux and Windows (via WSL), and the main command-line examples are platform-agnostic.
Recommendations
  • Provide native Windows redis-cli installation instructions (e.g., via pre-built binaries or Chocolatey), not just WSL.
  • List Linux methods for gathering cache access information (e.g., using Azure CLI in bash) before or alongside PowerShell.
  • Include explicit Linux shell/terminal usage examples (e.g., bash, zsh) and clarify that redis-cli commands work identically on Linux and macOS.
  • Avoid referencing Windows-specific tools (Windows Terminal) in sections meant for general usage, or provide Linux/macOS equivalents.
  • Ensure parity in troubleshooting and alternative tool recommendations, mentioning Linux and macOS options equally.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/nodejs-get-started.md ...re-docs/blob/main/articles/redis/nodejs-get-started.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits subtle Windows bias by using DOS-style code blocks for build/run commands (tsc, node index.js) and not providing explicit Linux/macOS equivalents. The use of the 'dos' code block and lack of Linux-specific instructions or examples may make Linux users feel less prioritized, even though the commands themselves are cross-platform.
Recommendations
  • Use generic 'bash' or 'shell' code blocks for cross-platform commands instead of 'dos', unless there are truly Windows-specific instructions.
  • Explicitly mention that the build/run commands work on Linux/macOS as well as Windows.
  • If there are platform-specific steps (e.g., environment setup, path differences), provide examples for both Windows and Linux/macOS.
  • Consider adding a note or section for Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/redis-cache-bicep-provision.md ...lob/main/articles/redis/redis-cache-bicep-provision.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell examples are given equal prominence to CLI, despite PowerShell being primarily a Windows tool. There is no explicit mention of Linux-specific considerations, nor are there examples for Bash scripting or Linux shell environments. The documentation does not clarify that Azure CLI is cross-platform while PowerShell is Windows-centric (though PowerShell Core is cross-platform, most Azure users on Linux use CLI). There are no Linux-specific instructions or troubleshooting tips.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit Bash shell examples or notes for Linux users where relevant.
  • De-emphasize PowerShell as a primary option, or move PowerShell examples after CLI examples to avoid Windows-first bias.
  • Include a brief section on platform compatibility, clarifying which tools are best for Windows vs. Linux.
  • Add troubleshooting tips or links for common Linux deployment issues (e.g., file permissions, CLI installation).
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/dotnet-core-quickstart.md ...ocs/blob/main/articles/redis/dotnet-core-quickstart.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation uses .NET Core CLI commands (dotnet build/run), which are cross-platform, but the code blocks are tagged as 'dos', implying a Windows command prompt context. There are no explicit Linux or macOS shell examples, nor is there mention of running the sample on non-Windows platforms. The instructions for editing configuration files reference 'Web.config' (a Windows/IIS convention) in one section, which may confuse Linux users. There is no mention of Linux-specific considerations or parity.
Recommendations
  • Use neutral code block tags (e.g., 'bash', 'shell', or no tag) for dotnet CLI commands to indicate cross-platform compatibility.
  • Explicitly mention that the sample and commands work on Windows, Linux, and macOS.
  • Provide Linux/macOS shell command examples where appropriate, or clarify that the commands are the same across platforms.
  • Avoid references to 'Web.config' unless specifically targeting ASP.NET on Windows; use 'appsettings.json' or other cross-platform configuration files.
  • Add a note or section on any platform-specific steps or troubleshooting for Linux/macOS users.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/aspnet-core-output-cache-provider.md ...in/articles/redis/aspnet-core-output-cache-provider.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently refers to 'command prompt' and uses Windows-centric terminology and command examples (e.g., 'cmd' code blocks, references to 'command prompt'), without providing equivalent instructions or terminal commands for Linux or macOS users. There are no bash/zsh shell examples, and no mention of Linux-specific considerations, despite .NET Core and Visual Studio Code being cross-platform.
Recommendations
  • Include Linux/macOS terminal instructions alongside Windows examples, using 'bash' code blocks where appropriate.
  • Refer to the terminal generically (e.g., 'open a terminal or command prompt') rather than only 'command prompt'.
  • Show both Windows and Linux/macOS commands for common tasks (e.g., directory creation, running dotnet commands, opening VS Code).
  • Explicitly state that the instructions apply to all supported platforms, and highlight any OS-specific differences if they exist.
  • Consider adding a platform selector or tabs for Windows, Linux, and macOS instructions where commands or steps differ.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/includes/cache-delete-resource-group.md ...articles/redis/includes/cache-delete-resource-group.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation only describes how to delete a resource group using the Azure portal (a web UI), with no mention of command-line alternatives. There are no examples for deleting resource groups using CLI tools such as Azure CLI or PowerShell. While the portal is cross-platform, the lack of CLI examples may disadvantage Linux users, who often prefer or require command-line instructions. Historically, Azure documentation sometimes defaults to PowerShell or Windows-centric tools, and the omission of Azure CLI (which is cross-platform and popular on Linux) is a subtle form of Windows-first bias.
Recommendations
  • Add instructions and examples for deleting a resource group using the Azure CLI (az group delete ...), which works on all platforms.
  • If PowerShell examples are included, ensure Azure CLI examples are presented first or equally, to avoid Windows-first ordering.
  • Explicitly mention that the Azure portal is accessible from any OS, but provide parity with command-line instructions for Linux users.
  • Consider including Bash script examples for automation scenarios.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/web-app-aspnet-core-howto.md .../blob/main/articles/redis/web-app-aspnet-core-howto.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation provides instructions and command-line examples that are platform-neutral in wording, but the use of 'command window' and the 'dos' code block hints at a Windows-first approach. There are no explicit Linux/macOS terminal instructions or screenshots, and no mention of platform-specific differences, which may leave Linux users without clear guidance.
Recommendations
  • Explicitly mention that the .NET CLI commands (dotnet build, dotnet run) work on Windows, Linux, and macOS.
  • Replace 'command window' with 'terminal' or 'command prompt or terminal' to be inclusive of all platforms.
  • Use the 'bash' code block for CLI commands, or provide both 'dos' and 'bash' code blocks where appropriate.
  • Add a note or section for Linux/macOS users, including any OS-specific steps (such as installing .NET SDK or running the app).
  • Include screenshots or terminal output examples from Linux/macOS environments, or clarify that the instructions are cross-platform.
GitHub Create Pull Request
Redis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/includes/redis-cache-resource-group-clean-up.md .../redis/includes/redis-cache-resource-group-clean-up.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation only provides instructions for cleaning up resources via the Azure Portal (web UI), with no mention of command-line alternatives. There are no examples for using CLI tools such as Azure CLI or PowerShell. While this avoids explicit Windows-only tools, the lack of CLI examples implicitly favors Windows users, as Linux users often expect or prefer CLI instructions.
Recommendations
  • Add Azure CLI examples for deleting resource groups, as the Azure CLI is cross-platform and widely used on Linux.
  • If mentioning PowerShell, ensure Azure CLI instructions are presented first or alongside, to avoid Windows-first bias.
  • Explicitly state that the Azure Portal method works on all platforms, but provide CLI alternatives for users who prefer command-line operations.
  • Include sample commands for both Azure CLI and, optionally, PowerShell, to ensure parity for Linux and Windows users.
GitHub Create Pull Request
← Previous Page 5 of 6 Next →