Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 326-350 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/quickstart-java-spring-app.md
.../azure-app-configuration/quickstart-java-spring-app.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows-first bias in the 'Build and run the app locally' section by presenting Windows Command Prompt and PowerShell commands before the Linux/macOS equivalent. The use of 'setx' (a Windows-specific tool) and explicit mention of Windows PowerShell further reinforce this bias. Although Linux/macOS commands are provided, they are listed after the Windows examples, and the command prompt syntax is used for Maven and curl commands, which may be confusing for non-Windows users.
Recommendations
- Present Linux/macOS and Windows instructions in parallel or in separate, clearly labeled sections to ensure equal visibility.
- Avoid using Windows-specific tools (like 'setx') without providing equivalent Linux/macOS alternatives (e.g., 'export' or instructions for setting persistent environment variables).
- Use neutral shell syntax (e.g., '$' for bash) for cross-platform commands like Maven and curl, or provide both Windows and Linux/macOS command examples.
- Consider starting with Linux/macOS examples or alternating the order in which platforms are presented to avoid implicit prioritization of Windows.
- Add explicit notes or callouts for platform-specific steps to help users quickly find relevant instructions.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/quickstart-configure-dev-box-service.md
...ticles/dev-box/quickstart-configure-dev-box-service.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-based images (e.g., 'Visual Studio 2022 Enterprise on Windows 11 Enterprise'), requiring Windows Enterprise licenses, and omitting any mention of Linux-based dev box images or workflows. All examples, prerequisites, and recommended images are Windows-centric, with no guidance for Linux users or cross-platform development scenarios.
Recommendations
- Include explicit instructions and examples for creating dev box definitions using Linux images (e.g., Ubuntu, CentOS) from the Azure Marketplace or Compute Gallery.
- List Linux-compatible licensing and identity prerequisites, or clarify if Linux dev boxes are supported and under what conditions.
- Provide example dev box definitions and pools using Linux images, and highlight any differences in setup or management.
- Mention Linux developer scenarios and tools (e.g., VS Code, JetBrains IDEs, CLI tooling) alongside Windows/Visual Studio examples.
- Clarify in the prerequisites and image selection sections whether Linux-based dev boxes are supported, and if not, state this limitation explicitly.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/quickstart-resource-manager.md
...azure-app-configuration/quickstart-resource-manager.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for deploying and cleaning up resources, with no equivalent Azure CLI or bash examples. The use of PowerShell cmdlets and the absence of Linux/macOS-specific or cross-platform instructions may hinder users on non-Windows platforms. Additionally, the PowerShell deployment method is presented before any mention of Azure CLI, and the only CLI command shown is for a specific configuration scenario, not for deployment.
Recommendations
- Provide equivalent Azure CLI and/or bash examples for all PowerShell deployment and cleanup instructions.
- Present cross-platform (CLI) instructions before or alongside PowerShell examples to ensure Linux/macOS parity.
- Clearly indicate that PowerShell is just one option and link to Azure CLI documentation for ARM template deployment.
- Consider including a table or section comparing deployment methods across platforms (Azure Portal, PowerShell, Azure CLI, etc.).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/quickstart-create-dev-box.md
...ob/main//articles/dev-box/quickstart-create-dev-box.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 the Windows App as the method to connect to a dev box, without mentioning or providing instructions for Linux or macOS users. There are no examples or guidance for connecting from Linux-based systems, and the only tool mentioned for remote access is the Windows App, reinforcing a Windows-centric approach.
Recommendations
- Include explicit instructions and examples for connecting to a dev box from Linux and macOS systems, such as using RDP clients available on those platforms (e.g., Remmina, FreeRDP, or rdesktop for Linux; Microsoft Remote Desktop for macOS).
- Mention and provide download links for cross-platform remote desktop clients in the prerequisites section.
- Ensure that all steps and screenshots that reference the Windows App are accompanied by equivalent guidance for Linux and macOS users.
- Add a table or section comparing connection options across Windows, Linux, and macOS, highlighting any differences or limitations.
- Review and update language throughout the documentation to avoid assuming the user is on Windows, and to clarify when instructions are platform-specific.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/cache-administration.md
...articles/azure-cache-for-redis/cache-administration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell cmdlets and management instructions, without providing equivalent examples or explicit guidance for Linux users (e.g., Azure CLI or Bash). The only automation or scripting examples are for PowerShell, and there is no mention of Linux-native tools or cross-platform alternatives. This could make it harder for Linux users to manage Azure Cache for Redis using their preferred environments.
Recommendations
- Provide Azure CLI examples alongside PowerShell for all management tasks (reboot, flush, schedule updates), as CLI is cross-platform and widely used on Linux.
- Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI or REST API, and link to relevant documentation.
- Add Bash script snippets or command-line examples where appropriate, to ensure Linux users have clear, actionable guidance.
- Reorganize sections that mention management tools so that cross-platform options (CLI, REST API) are listed before or alongside PowerShell.
- Where screenshots or UI instructions are given, clarify that the Azure Portal is web-based and platform-agnostic.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/cache-best-practices-connection.md
...ure-cache-for-redis/cache-best-practices-connection.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page primarily references .NET/ASP.NET and StackExchange.Redis (which are Windows-centric or at least Windows-first technologies), and provides code/configuration examples only for these. There are no equivalent Linux/Unix or cross-platform client examples, and no mention of Linux-specific tools or patterns except for a brief section on Linux TCP settings. The guidance for ForceReconnect and timeout configuration is focused on .NET/Windows environments, with no parity for common Linux/Unix Redis clients (e.g., redis-py, Jedis, Lettuce, etc.).
Recommendations
- Add equivalent examples and guidance for popular Linux/Unix Redis clients (such as redis-py for Python, Jedis/Lettuce for Java, redis-cli, etc.), including how to handle reconnections, timeouts, and keepalive/heartbeat functionality.
- When referencing code patterns (such as ForceReconnect), provide cross-platform examples or at least mention how the pattern applies (or does not apply) to non-.NET clients.
- Balance the focus between Windows/.NET and Linux/open-source client libraries, ensuring that Linux-first or cross-platform developers can easily find relevant guidance.
- Include Linux shell/command-line examples (e.g., using redis-cli or systemd for service restarts) where appropriate, not just Windows/PowerShell or .NET-centric approaches.
- Explicitly mention any differences in behavior or configuration between Windows and Linux environments for Azure Cache for Redis clients.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/cache-configure.md
...ain//articles/azure-cache-for-redis/cache-configure.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only PowerShell examples for configuring certain settings (such as the 'databases' property during cache creation), mentioning PowerShell before CLI or other cross-platform tools, and omitting explicit Linux or Bash examples. There is no mention of Linux-specific tools or workflows, and the only example for configuring databases during cache creation is via PowerShell, with no Azure CLI (bash) or REST API example provided.
Recommendations
- Provide Azure CLI (bash) examples alongside or before PowerShell examples for all configuration tasks, especially for cross-platform scenarios.
- Ensure that all code snippets and configuration instructions are available for both Windows (PowerShell) and Linux/macOS (Bash/CLI) users.
- Explicitly mention cross-platform tools (such as Azure CLI) in all relevant sections, not just PowerShell.
- Review all sections for implicit Windows-first ordering and alternate with Linux-first or neutral ordering.
- Add notes or links to Linux/macOS documentation where appropriate, especially in sections that currently only reference Windows tools or patterns.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/use-key-vault-references-spring-boot.md
...-configuration/use-key-vault-references-spring-boot.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows-first bias in several areas. Environment variable setup instructions are presented first for Windows (cmd and PowerShell), with Linux/macOS instructions following. The use of 'setx' and PowerShell commands are highlighted, while the Linux/macOS equivalent uses a generic 'export' command. Visual Studio Code is mentioned as cross-platform, but no Linux-specific editors or shell instructions are provided. The overall flow and examples assume a Windows-centric workflow, with Linux/macOS support added as an afterthought.
Recommendations
- Present Linux/macOS and Windows instructions side by side or in parallel tabs, rather than listing Windows first.
- Use cross-platform shell commands (e.g., bash) as the default, with Windows alternatives provided as needed.
- Include Linux/macOS-specific tooling or editor suggestions (e.g., Vim, Emacs, GNOME Terminal) alongside Visual Studio Code.
- Avoid using Windows-specific tools (like 'setx') as the primary example; instead, provide both 'export' (for Linux/macOS) and 'setx' (for Windows) in equal prominence.
- Where possible, use neutral language and avoid implying Windows is the default or primary development environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/cache-how-to-redis-cli-tool.md
...s/azure-cache-for-redis/cache-how-to-redis-cli-tool.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by prioritizing Windows-specific tools and patterns. Windows installation instructions are given significant space, with a strong emphasis on using Windows Subsystem for Linux (WSL) rather than native Windows binaries. Azure PowerShell is mentioned alongside Azure CLI for retrieving cache keys, and Windows Terminal is referenced as the default terminal for Windows users. Linux is covered, but often as a secondary consideration or via WSL on Windows.
Recommendations
- Provide explicit instructions for native redis-cli installation on Windows (e.g., via precompiled binaries or Chocolatey), not just via WSL.
- List Azure CLI (cross-platform) before Azure PowerShell when describing how to retrieve cache keys, or clarify parity.
- When referencing terminals, mention cross-platform options (e.g., Windows Terminal, GNOME Terminal, iTerm2) equally.
- Ensure all examples and instructions are clearly labeled for both Linux and Windows environments, and provide parity in detail.
- Consider including a table or section summarizing installation and usage steps for all major platforms (Linux, Windows, macOS) for quick reference.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/cache-retired-features.md
...ticles/azure-cache-for-redis/cache-retired-features.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation references PowerShell as a method to trigger the Redis version upgrade, and does not provide explicit Linux command-line examples or mention Linux-specific tools. The focus on PowerShell and lack of Linux parity in examples or instructions indicates a Windows bias.
Recommendations
- Include explicit Linux command-line examples (e.g., Bash/Azure CLI) alongside PowerShell instructions.
- Mention Linux tools and workflows (such as Bash scripts or Linux terminal commands) when describing upgrade processes.
- Ensure that all references to command-line tools are cross-platform, and provide equivalent instructions for both Windows and Linux users.
- Clarify that Azure CLI commands can be run on any platform, and provide sample commands for both environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/cache-how-to-active-geo-replication.md
...cache-for-redis/cache-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 Azure PowerShell examples for configuring active geo-replication, but it demonstrates a Windows bias by listing PowerShell (a Windows-centric tool) as a primary automation method alongside CLI, and does not provide any Linux shell (bash) or cross-platform scripting examples. There are no explicit Linux-specific instructions or screenshots, and the PowerShell section is as prominent as the CLI section, which may disadvantage Linux users. Additionally, there is no mention of using Azure Cloud Shell (which is cross-platform) or guidance for Linux/macOS environments.
Recommendations
- Add explicit bash shell examples for all CLI commands, including any necessary export or environment variable steps for Linux/macOS users.
- Clarify that Azure CLI commands work identically on Windows, Linux, and macOS, and recommend Azure Cloud Shell as a cross-platform option.
- Reorder sections so that CLI (which is cross-platform) appears before PowerShell, or clearly indicate that PowerShell is primarily for Windows users.
- Include notes or screenshots showing the experience on Linux/macOS where relevant, or mention any OS-specific considerations.
- If there are differences in command syntax or prerequisites for Linux/macOS, document them explicitly.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-resolve-dev-box-connectivity-issues.md
.../dev-box/how-to-resolve-dev-box-connectivity-issues.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation is heavily Windows-centric, providing step-by-step troubleshooting instructions that assume a Windows environment (e.g., registry edits, Group Policy Editor, Windows-specific processes like msrdc.exe). macOS receives a brief mention at the end, but Linux is not referenced at all. All command-line examples and troubleshooting steps are tailored to Windows tools and workflows, with no Linux equivalents or guidance.
Recommendations
- Add equivalent troubleshooting steps for Linux users, including how to diagnose and resolve RDP connectivity issues using common Linux RDP clients (e.g., xfreerdp, Remmina).
- Provide Linux-specific commands or configuration file edits for switching between TCP and UDP, and for capturing logs or process dumps.
- Include examples of how to check for client and server status on Linux, such as using systemctl, journalctl, or netstat.
- Mention and link to popular Linux RDP clients and how to update or restart them.
- Ensure that all major troubleshooting steps are presented for Windows, macOS, and Linux in parallel, or at least reference where Linux users can find equivalent guidance.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/cache-how-to-premium-vnet.md
...les/azure-cache-for-redis/cache-how-to-premium-vnet.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation demonstrates a Windows bias primarily in the troubleshooting and verification steps. The only explicit command-line example for verifying connectivity uses tcping.exe, a Windows-specific tool, with no mention of Linux or cross-platform alternatives. There are no Linux shell or Azure CLI examples for connectivity testing, and the only tool referenced for port testing is a Windows executable. Additionally, the general pattern is to mention PowerShell and Resource Manager templates before Azure CLI, and there are no Linux-specific instructions or screenshots.
Recommendations
- Provide equivalent Linux/macOS examples for connectivity testing, such as using 'nc' (netcat), 'telnet', or 'nmap' for port checks.
- Mention cross-platform tools (e.g., 'tcping' for Linux, or alternatives like 'curl' or 'openssl s_client') alongside Windows tools.
- When listing automation options, mention Azure CLI before or alongside PowerShell and Resource Manager templates.
- Include screenshots or instructions that are not specific to the Windows Azure Portal experience, or clarify that the portal is web-based and platform-agnostic.
- Explicitly state that all steps can be performed from any OS, and provide command-line examples for both Windows and Linux where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/cache-migration-guide.md
...rticles/azure-cache-for-redis/cache-migration-guide.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (AzCopy, PowerShell cmdlets) for migration tasks without providing equivalent Linux/Unix alternatives or cross-platform instructions. The examples and tool recommendations (such as Import-AzRedisCache and Export-AzRedisCache) are PowerShell-centric, and there are no CLI or Bash examples. This may hinder Linux users or those working in non-Windows environments.
Recommendations
- For every PowerShell cmdlet (e.g., Import-AzRedisCache, Export-AzRedisCache), provide equivalent Azure CLI commands and Bash examples.
- When recommending AzCopy, clarify that it is cross-platform and provide example commands for Linux/macOS shells as well as Windows.
- Explicitly mention and provide instructions for performing migration steps from Linux environments, including file copying and automation.
- Ensure that tool recommendations and examples are presented in a platform-neutral order, or group them by platform, rather than listing Windows/PowerShell first.
- Add notes or links to official documentation for Linux/macOS users where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/cache-how-to-premium-persistence.md
...re-cache-for-redis/cache-how-to-premium-persistence.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by providing detailed instructions and examples for Azure PowerShell, a Windows-centric tool, and referencing PowerShell/Windows tooling before or more prominently than Linux-native alternatives. While Azure CLI is mentioned (which is cross-platform), there are no explicit Linux shell (bash) or scripting examples, and no mention of Linux-specific considerations or tools. The documentation assumes familiarity with PowerShell and does not provide parity for Linux users in terms of command-line examples or troubleshooting.
Recommendations
- Provide explicit bash/Linux shell examples alongside PowerShell examples, especially in sections about scripting or automation.
- When referencing Azure CLI, include example commands that are tested and formatted for Linux/macOS terminals (e.g., with single quotes, handling of environment variables, etc.).
- Add a section or notes on Linux-specific prerequisites or troubleshooting (e.g., file permissions, path formats, CLI installation on Linux).
- Balance the order of presentation so that Azure CLI (cross-platform) examples appear before or alongside PowerShell examples.
- Avoid assuming the use of Windows tools (such as PowerShell) as the default; clarify that both Windows and Linux environments are supported and provide guidance for both.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/monitor-dev-box.md
...re-docs/blob/main//articles/dev-box/monitor-dev-box.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed instructions and code samples for enabling diagnostic logging using Azure PowerShell, but does not include equivalent examples for Azure CLI, Bash, or other cross-platform tools. All automation examples are PowerShell-based, which is primarily a Windows-centric tool, despite Azure CLI being available and commonly used on Linux and macOS. There is no mention of Linux-specific workflows or parity in scripting approaches.
Recommendations
- Add equivalent Azure CLI examples for enabling diagnostic logging, including commands for both storage account and Log Analytics workspace scenarios.
- Explicitly mention that Azure CLI is cross-platform and provide Bash-friendly scripts for Linux/macOS users.
- Where PowerShell is referenced, also provide a parallel section for Azure CLI to ensure users on all platforms have clear guidance.
- Review the documentation for any other Windows-centric terminology or assumptions, and ensure that instructions are inclusive of Linux/macOS environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/cache-remove-tls-10-11.md
...ticles/azure-cache-for-redis/cache-remove-tls-10-11.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell scripts and commands for checking and configuring TLS settings, with no equivalent Bash, Linux shell, or cross-platform examples. The use of PowerShell and references to the Az.RedisCache module are specific to Windows environments, and there is no mention of Linux tools or commands for performing the same tasks. The CLI section is minimal and does not provide a Linux-friendly workflow for updating existing caches. The order of presentation also places Windows/PowerShell instructions before any mention of CLI or cross-platform approaches.
Recommendations
- Provide equivalent Bash or shell script examples for checking TLS versions from Linux environments, using tools like openssl or nmap.
- Include Azure CLI commands for both creating and updating the Minimum TLS version, and clarify any limitations or workarounds for Linux users.
- When presenting scripts or commands, offer both Windows (PowerShell) and Linux (Bash/shell) examples side by side.
- Reference cross-platform tools (e.g., openssl s_client) for TLS version checks.
- Avoid assuming the use of Windows-specific modules or tools; mention alternatives for Linux/macOS users.
- Ensure that CLI and cross-platform instructions are given equal prominence and not relegated to secondary status after Windows/PowerShell instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/cache-managed-identity.md
...ticles/azure-cache-for-redis/cache-managed-identity.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Azure PowerShell (commonly used on Windows) alongside Azure CLI, and by providing detailed step-by-step instructions and screenshots for the Azure Portal (which is OS-agnostic but often illustrated with Windows UI). There are no explicit Linux-specific instructions, nor are there examples showing Linux shell commands or considerations for Linux users. The PowerShell example is given equal prominence to the Azure CLI, but there are no Bash or Linux-native command examples, and no mention of Linux tools or environments.
Recommendations
- Add explicit Linux/Bash shell command examples for all CLI instructions, including any differences in quoting, line continuation, or environment setup.
- Clarify that Azure CLI commands work cross-platform and, where appropriate, show screenshots or terminal output from a Linux shell.
- If PowerShell is mentioned, also mention Bash or other common Linux shells to ensure parity.
- Include notes or tips for Linux users, such as package installation commands for Azure CLI or PowerShell on Linux.
- Review screenshots and UI instructions to ensure they are not Windows-specific, or add clarifying notes for Linux/macOS users if UI elements differ.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/cache-private-link.md
...//articles/azure-cache-for-redis/cache-private-link.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through the ordering and emphasis of examples and tooling. Azure PowerShell (a Windows-centric tool) is presented before Azure CLI, and extensive step-by-step instructions are given for the Azure Portal (which is platform-agnostic but often associated with Windows workflows). There are no explicit Linux-specific instructions, nor are there any Bash or shell script examples outside of Azure CLI. No mention is made of Linux-native tools or workflows, and the PowerShell examples are more detailed than the CLI ones. There is also no mention of cross-platform scripting considerations.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and preferred by many Linux users.
- Include explicit Bash/shell script examples where appropriate, especially for automation scenarios.
- Add notes clarifying that Azure CLI commands work on Linux, macOS, and Windows.
- Where PowerShell is shown, also provide equivalent Bash or shell commands for parity.
- Mention Linux-native tools or workflows if relevant (e.g., using curl for REST API calls, or jq for JSON parsing).
- Ensure that screenshots and portal instructions do not assume a Windows environment (e.g., avoid showing Windows-specific UI elements or file paths).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/configure-lab-remote-desktop-gateway.md
...s/devtest-labs/configure-lab-remote-desktop-gateway.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a strong Windows bias. All examples and scripts for certificate creation and automation use PowerShell, with no mention of Linux or cross-platform alternatives. Required tools and modules (e.g., RDGatewayFedAuth.msi, IIS Application Routing, System Center VMM) are Windows-specific. There are no instructions or examples for Linux clients or servers, and the documentation assumes the use of RDP, which is primarily a Windows protocol. Linux equivalents for certificate management, automation, or remote access are not discussed.
Recommendations
- Provide equivalent instructions and scripts for Linux environments, such as using OpenSSL for certificate creation and Bash scripts for automation.
- Mention and provide examples for Linux-compatible RDP clients (e.g., FreeRDP, Remmina) and clarify token authentication support.
- Discuss alternatives to IIS Application Routing for Linux (e.g., NGINX or Apache reverse proxy configuration).
- Clarify whether the gateway solution can be deployed on Linux-based VMs, and if not, explicitly state the Windows-only limitation.
- Include Linux command-line examples (e.g., az CLI, OpenSSL) alongside PowerShell examples.
- Add a section or note about remote access options for Linux VMs in DevTest Labs, if supported.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/cache-troubleshoot-connectivity.md
...ure-cache-for-redis/cache-troubleshoot-connectivity.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing a connectivity test example using PSPING in Azure PowerShell, a Windows-specific tool, without offering an equivalent Linux command or example. The Windows tool is mentioned immediately after the cross-platform redis-cli, and no Linux-native alternatives (such as nc, telnet, or nmap) are provided. This may leave Linux users without clear guidance for connectivity troubleshooting.
Recommendations
- Provide Linux-equivalent commands for connectivity testing, such as using 'nc', 'telnet', or 'nmap' to check port connectivity.
- When mentioning Windows-specific tools like PSPING, always include a Linux alternative in the same section.
- Consider reordering examples so that cross-platform or Linux-native tools are presented before or alongside Windows tools.
- Explicitly state which tools are platform-specific to avoid confusion for non-Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/cache-vnet-migration.md
...articles/azure-cache-for-redis/cache-vnet-migration.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) and Windows-specific tools (AzCopy) without providing equivalent Linux/CLI examples. PowerShell is mentioned as an alternative for exporting/importing data, but no Azure CLI, Bash, or Linux-native instructions are given. The order of presentation also places PowerShell and Windows tools before any cross-platform or Linux alternatives, and there is no mention of Linux-specific guidance for common migration steps.
Recommendations
- Provide Azure CLI examples alongside PowerShell cmdlets for exporting and importing Redis cache data.
- Mention and link to Linux-compatible tools for copying files to Azure Storage (e.g., azcopy for Linux, Azure CLI storage commands, or sftp/scp).
- Include Bash script examples or general command-line instructions that are platform-agnostic.
- Explicitly state that the migration steps can be performed from Linux, macOS, or Windows, and provide any OS-specific caveats.
- Reorder tool mentions so that cross-platform or Linux-native options are presented before or alongside Windows/PowerShell tools.
- Add a section or callout for Linux users, ensuring parity in instructions and tool recommendations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/add-artifact-vm.md
...cs/blob/main//articles/devtest-labs/add-artifact-vm.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias by providing only Azure PowerShell examples for scripting and automation, with no equivalent CLI or Bash examples for Linux users. The prerequisites and instructions for command-line usage focus exclusively on PowerShell, and there is no mention of Azure CLI or Linux-native tooling. The documentation also refers to running PowerShell scripts as a primary example of artifact usage, and the PowerShell environment is emphasized in the prerequisites.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell scripts and commands, demonstrating how to add artifacts to VMs using the CLI.
- Include Bash script examples or references for Linux users, especially in automation scenarios.
- In the prerequisites, mention both PowerShell and Azure CLI as supported options, and provide installation/use instructions for both.
- When describing artifact capabilities, give equal prominence to Bash and Linux scripting as to PowerShell.
- Ensure screenshots and UI descriptions are platform-neutral or show parity between Windows and Linux workflows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/scripts/powershell-webhook-secure-delivery-microsoft-entra-app.md
...powershell-webhook-secure-delivery-microsoft-entra-app.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively provides a PowerShell script for configuring secure webhook delivery with Microsoft Entra Application in Azure Event Grid. There are no examples or instructions for Linux users or for using cross-platform tools such as Azure CLI or Bash. The script and instructions assume familiarity with PowerShell and Windows-centric tooling, and there is no mention of equivalent steps or commands for Linux environments.
Recommendations
- Provide equivalent Azure CLI (az) or Bash script examples for each step, ensuring Linux and macOS users can follow along without PowerShell.
- Explicitly mention that the PowerShell script can be run on PowerShell Core (pwsh) on Linux/macOS, if applicable, and provide installation instructions if needed.
- Include a section or callout for Linux users, highlighting any differences or additional steps required.
- Where possible, use cross-platform tools (e.g., Azure CLI, Microsoft Graph CLI) in examples before or alongside PowerShell.
- Clarify any prerequisites or environment requirements for non-Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-compute-fleet/quickstart-create-rest-api.md
...cles/azure-compute-fleet/quickstart-create-rest-api.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias by providing PowerShell and Azure Portal instructions for feature registration, but omitting Azure CLI or Bash examples. The ARM template exclusively deploys Windows VMs (Windows image reference, osType set to 'Windows'), with no mention of Linux images or configuration. This prioritizes Windows tools and patterns, and lacks Linux parity in both deployment and operational guidance.
Recommendations
- Add Azure CLI (az) and Bash examples alongside PowerShell for all command-line operations, including resource provider registration.
- Provide ARM template examples or parameters for deploying Linux-based fleets (e.g., using Ubuntu or other Linux images, osType: 'Linux').
- Ensure that all instructions and examples are presented in a platform-neutral order, or provide Linux/CLI first where appropriate.
- Mention and link to relevant Linux tools and workflows (e.g., Bash, SSH) where applicable.
- Explicitly state that both Windows and Linux fleets are supported, and provide guidance for each.