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 1526-1550 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/integrate-kubernetes-deployment-helm.md
...-configuration/integrate-kubernetes-deployment-helm.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is generally cross-platform but introduces a Windows/Powershell bias in the section demonstrating how to pass secrets to Helm using the --set argument. The only example provided for this workflow uses Powershell scripting, with no equivalent Bash or Linux shell example. Additionally, the Powershell example is presented first and exclusively, which may disadvantage Linux/macOS users.
Recommendations
- Provide equivalent Bash (Linux/macOS) examples alongside the Powershell script for passing secrets to Helm using the --set argument.
- When presenting scripts or command-line workflows, include both Windows (Powershell) and Linux/macOS (Bash) variants, or use a neutral scripting language where possible.
- Explicitly state that the Azure CLI and Helm commands are cross-platform and can be run on Windows, Linux, or macOS.
- Consider using tabbed code blocks to allow users to select their preferred platform (Windows/Powershell, Linux/Bash, macOS).
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/quickstart-chat-completion-dotnet.md
...app-configuration/quickstart-chat-completion-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows Command Prompt and PowerShell before mentioning the equivalent command for macOS/Linux. The Windows instructions are more detailed (e.g., mentioning restarting the command prompt), and the PowerShell example is given before the Linux/macOS example. There are no Linux-specific tools or patterns mentioned elsewhere, but the order and detail of examples show a mild Windows-first and PowerShell-heavy bias.
Recommendations
- Present environment variable setup instructions for all platforms in parallel, using a table or side-by-side format, rather than listing Windows first.
- Provide equal detail for Linux/macOS instructions (e.g., mention if restarting the terminal is needed, as is done for Windows).
- Consider using neutral, cross-platform language and examples where possible (e.g., recommend using the .NET CLI, which works on all platforms, for all steps).
- Explicitly state that the instructions apply equally to Windows, Linux, and macOS, and avoid giving the impression that Windows is the primary or default platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/howto-import-export-data.md
...es/azure-app-configuration/howto-import-export-data.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently presents file path examples and CLI usage with Windows-style paths (e.g., C:/Users/john/Downloads/data.json, D:/abc.json) and does not provide equivalent Linux/macOS path examples. There are no explicit Linux or macOS shell command examples, and all CLI instructions use Windows conventions by default. This may give the impression that the documentation is primarily intended for Windows users, potentially making Linux/macOS users feel less supported.
Recommendations
- For every CLI example that uses a Windows-style file path, provide an equivalent Linux/macOS example (e.g., /home/john/data.json).
- Explicitly mention that the Azure CLI commands work on Windows, Linux, and macOS, and show at least one example per platform where file paths or shell conventions differ.
- Where referencing the Azure Cloud Shell, clarify that it is available in-browser and supports both Bash and PowerShell, and provide examples for both where relevant.
- Avoid using only Windows drive letters (C:/, D:/) in examples; use generic or cross-platform paths, or alternate between Windows and Linux/macOS paths in examples.
- If referencing commands to retrieve resource IDs or similar, show both PowerShell and Bash variants if there are differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/quickstart-container-apps.md
...s/azure-app-configuration/quickstart-container-apps.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by exclusively referencing an ASP.NET Core application (commonly associated with Windows development) and providing no Linux-specific instructions or examples. All command-line instructions are generic (Docker, Azure CLI), but there are no explicit Linux shell or cross-platform notes, and the prerequisite app is created via a prior ASP.NET Core quickstart. There are no PowerShell-specific commands, but the lack of Linux/Unix shell context or alternative frameworks (e.g., Node.js, Python) limits Linux parity.
Recommendations
- Add explicit notes or sections clarifying that all CLI commands (Docker, Azure CLI) work on both Windows and Linux, and provide any necessary differences (e.g., path separators, environment variable syntax).
- Include a Linux/Unix shell example for building and running the Docker container, especially for environment variable handling.
- Provide a parallel quickstart or references for non-Windows frameworks (e.g., Node.js, Python) to broaden applicability.
- Mention that Docker Desktop is available on Windows, Mac, and Linux, and provide links or instructions for Linux installation.
- If the app is not Windows-specific, clarify that the instructions are cross-platform, or provide a Linux-specific sample application.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/quickstart-bicep.md
...//articles/azure-app-configuration/quickstart-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all deployment, review, and cleanup steps. However, PowerShell is presented as an equal alternative to Azure CLI, despite being a Windows-centric tool. There is no explicit mention of Linux or macOS environments, nor are there any Bash or shell script examples. The structure (CLI tab first, then PowerShell) is good, but the heavy inclusion of PowerShell and lack of explicit Linux guidance may subtly bias toward Windows users.
Recommendations
- Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS), while PowerShell is primarily for Windows users (though PowerShell Core is cross-platform, but less common on Linux).
- Add a note or section for Linux/macOS users, clarifying that Azure CLI is the recommended tool and is available natively.
- Consider providing Bash script examples or at least mentioning that the CLI commands can be run in Bash or other Unix shells.
- If PowerShell is included, clarify its cross-platform status and provide installation instructions for non-Windows users if relevant.
- Ensure parity in troubleshooting or environment setup notes for both Windows and Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/quickstart-feature-flag-javascript.md
...pp-configuration/quickstart-feature-flag-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates mild Windows bias, particularly in the 'Run the application' section. Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents, and there is more detailed guidance for Windows users (e.g., mentioning restarting the command prompt after setx). The prerequisite section also references Windows and WSL before Linux, and the linked Node.js installation guide is Windows-focused. However, Linux/macOS commands are present and correct, and the code samples themselves are cross-platform.
Recommendations
- Present Linux/macOS and Windows instructions in parallel tabs or in a consistent order (e.g., Linux/macOS first, or alphabetical).
- Avoid giving Windows-specific instructions (such as 'restart the command prompt') without equivalent context for Linux/macOS.
- In the prerequisites, provide equal prominence to Linux/macOS installation instructions for Node.js, not just Windows/WSL.
- Where possible, use neutral language and structure (e.g., 'On Windows, run...', 'On Linux/macOS, run...') rather than always leading with Windows.
- Ensure all screenshots and portal instructions are OS-agnostic or provide alternatives if there are differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/quickstart-python-provider.md
.../azure-app-configuration/quickstart-python-provider.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before macOS/Linux, and references Windows-specific Python setup documentation in prerequisites. While Linux/macOS commands are present, Windows instructions are consistently listed first and more prominently, indicating a subtle Windows-first bias.
Recommendations
- Present environment variable setup instructions for all platforms in parallel, or alternate the order (e.g., show Linux/macOS first in some sections).
- In prerequisites, provide links for setting up Python on Linux and macOS in addition to Windows.
- Consider using tabbed or side-by-side layouts for platform-specific commands to avoid implying priority.
- Ensure all tooling and setup steps are equally covered for Linux/macOS, not just referenced after Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/quickstart-feature-flag-spring-boot.md
...p-configuration/quickstart-feature-flag-spring-boot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes explicit PowerShell commands. While Linux/macOS instructions are present and correct, the ordering and inclusion of Windows-specific tooling (setx, PowerShell) before bash commands demonstrates a subtle Windows-first bias.
Recommendations
- Present Linux/macOS and Windows instructions in parallel (side-by-side tabs) or alternate the order to avoid always listing Windows first.
- Avoid giving extra detail or emphasis to Windows tools (such as setx or PowerShell) unless there is a platform-specific reason.
- Where possible, use cross-platform commands or highlight platform-specific differences only when necessary.
- Consider using tabbed sections for each OS to improve clarity and parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/cache-event-grid.md
...in//articles/azure-cache-for-redis/cache-event-grid.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation lists PowerShell (a Windows-centric tool) before Azure CLI (cross-platform) in both the quickstart table and the 'Next steps' section, which may suggest a Windows-first bias. There are no explicit Linux-only examples or tools mentioned, and no mention of Linux-specific considerations, but Azure CLI is included, which is cross-platform.
Recommendations
- List Azure CLI before PowerShell in tables and 'Next steps' sections to prioritize the cross-platform tool.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows to reinforce cross-platform support.
- If possible, add a Linux-specific quickstart or note, or clarify that all examples (except PowerShell) are fully supported on Linux.
- Consider adding Bash or shell script examples where relevant, or link to Linux-specific guidance if available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/quickstart-go-web-app.md
...icles/azure-app-configuration/quickstart-go-web-app.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes explicit PowerShell examples. While Linux/macOS commands are present, Windows instructions are consistently listed first, and PowerShell is given its own example block, which may suggest a slight prioritization of Windows environments.
Recommendations
- Alternate the order of platform instructions (sometimes show Linux/macOS first) to avoid implicit prioritization.
- Group platform-specific commands in a tabbed or collapsible format so users can easily select their OS, rather than listing Windows first by default.
- Ensure parity in detail and clarity between Windows and Linux/macOS instructions.
- Consider including WSL (Windows Subsystem for Linux) notes if relevant, to bridge Windows and Linux workflows.
- Where possible, use cross-platform commands or highlight them as the default, with platform-specific notes as needed.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/reference-kubernetes-provider.md
...ure-app-configuration/reference-kubernetes-provider.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation exhibits a subtle Windows bias in the authentication examples, specifically in the instructions for enabling managed identity on the virtual machine scale set (VMSS) used by AKS. The links and references for enabling managed identity and assigning roles point to Windows VMSS documentation, and do not mention or link to Linux VMSS equivalents. There are no explicit PowerShell or Windows command-line examples, but the guidance assumes a Windows-centric environment for VMSS operations. No Linux-specific instructions or parity are provided for these steps.
Recommendations
- Provide parallel instructions and links for both Windows and Linux VMSS when describing how to enable managed identity and assign roles.
- Where referencing Azure documentation for VMSS, include both Windows and Linux guides, or clarify that the steps are OS-agnostic if applicable.
- Explicitly state that the Azure App Configuration Kubernetes Provider works with both Windows and Linux VMSS, and provide any OS-specific caveats if they exist.
- Review all external links to ensure Linux users are not inadvertently excluded or confused by Windows-only references.
- If any command-line examples are added in the future (e.g., PowerShell), ensure equivalent Bash/Azure CLI examples are also provided.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/quickstart-go-console-app.md
...s/azure-app-configuration/quickstart-go-console-app.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both setx (cmd) and PowerShell commands, which may suggest a slight Windows-first and PowerShell-heavy bias. However, Linux/macOS instructions are also present and complete. There are no missing Linux examples or exclusive use of Windows tools elsewhere.
Recommendations
- Present environment variable setup instructions for all platforms in parallel (e.g., in a table or side-by-side tabs), or rotate which OS is presented first in different sections.
- Avoid giving Windows instructions (cmd, PowerShell) before Linux/macOS by default; consider listing Linux/macOS first or equally.
- Ensure parity in all command-line instructions, and consider mentioning that Linux/macOS users do not need to restart the shell after export, while setx on Windows does.
- If possible, provide a single cross-platform script or tool (e.g., a .env file or a Go-based setup script) to reduce OS-specific steps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/reload-key-vault-secrets-dotnet.md
...e-app-configuration/reload-key-vault-secrets-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on ASP.NET Core and C#, which are traditionally associated with Windows development, and does not provide equivalent examples or guidance for Linux or cross-platform environments. There are no Linux-specific instructions, nor are there examples for other popular frameworks or languages used on Linux. The prerequisites and code samples assume a .NET/Windows-centric workflow, and there is no mention of how to achieve the same functionality in Linux-native environments or with other programming languages.
Recommendations
- Provide equivalent examples for Linux environments, such as using .NET Core on Linux, or other languages/frameworks commonly used on Linux (e.g., Python, Node.js).
- Include instructions for setting up and running the sample code on Linux, including any necessary package installations or environment configurations.
- Mention cross-platform compatibility explicitly, clarifying that the approach works on both Windows and Linux, or provide alternatives if there are differences.
- Add references or links to documentation for other languages and frameworks that are popular in Linux environments.
- Ensure that UI instructions (such as those for the Azure portal) are not OS-specific, and clarify any steps that might differ between platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/quickstart-javascript-provider.md
...re-app-configuration/quickstart-javascript-provider.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias, particularly in the 'Run the application' section. Instructions for setting environment variables are presented with Windows Command Prompt and PowerShell commands before the Linux/macOS equivalent, and Windows-specific tools (setx, PowerShell) are mentioned explicitly. The Node.js installation prerequisite also references Windows and WSL before Linux. However, Linux/macOS examples are present and correct, and the main code samples are cross-platform.
Recommendations
- Present environment variable instructions in a neutral or parallel order (e.g., group Windows, macOS, and Linux together, or alternate which comes first).
- Avoid language such as 'If you use Windows...' before mentioning Linux/macOS, or use a table to present all OSes equally.
- In the prerequisites, provide Linux installation links and instructions alongside Windows, not after or as a secondary note.
- Where possible, use cross-platform commands (e.g., 'set' for Windows CMD, 'export' for Unix shells) in a table or side-by-side tabs.
- Consider referencing Linux and macOS tools and patterns as prominently as Windows ones.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/quickstart-javascript.md
...icles/azure-app-configuration/quickstart-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally provides cross-platform instructions, but there is a subtle Windows bias in the ordering and presentation of environment variable setup commands. Windows Command Prompt and PowerShell instructions are listed before Linux/macOS equivalents, and PowerShell is given a dedicated example. The initial Node.js installation link also references Windows and WSL before other platforms. However, Linux and macOS commands are present and correct, and the main code samples are platform-agnostic.
Recommendations
- Present environment variable setup instructions in a neutral or rotating order (e.g., Linux/macOS first in some sections, or all platforms in a single table).
- Avoid always listing Windows and PowerShell before Linux/macOS; consider grouping all OS instructions together for parity.
- In the prerequisites, provide installation links and guidance for Node.js on all major platforms equally, not just Windows and WSL.
- If possible, use a tabbed or side-by-side format for OS-specific commands to visually reinforce parity.
- Review other sections for subtle language that centers Windows as the default or primary platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/includes/redis-cache-resource-group-clean-up.md
...-redis/includes/redis-cache-resource-group-clean-up.md
Medium Priority
View Details →
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, and no Linux-specific instructions or parity. This can disadvantage users who prefer or require command-line or Linux-native workflows.
Recommendations
- Add equivalent instructions for deleting resource groups using the Azure CLI (az group delete), which works cross-platform (Windows, Linux, macOS).
- If including PowerShell examples, ensure Azure CLI examples are presented first or alongside them, as Azure CLI is more commonly used on Linux.
- Explicitly mention that the Azure portal instructions are platform-agnostic, but provide command-line alternatives for users who prefer scripting or automation.
- Include sample commands for both Windows (PowerShell) and Linux/macOS (Bash) environments to ensure parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/includes/cache-entra-access.md
...s/azure-cache-for-redis/includes/cache-entra-access.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page primarily describes using the Azure portal (a web UI) for configuration, which is platform-neutral. However, it references Microsoft Entra ID integration and only links to Azure CLI documentation without providing any command-line examples. There are no explicit Windows-only tools or PowerShell examples, but the lack of Linux-specific or cross-platform command-line examples (such as Bash or Linux CLI usage) may disadvantage Linux users. The documentation implicitly assumes familiarity with the Azure portal, which is equally accessible from all platforms, but does not demonstrate parity in command-line workflows.
Recommendations
- Add explicit Azure CLI command examples for enabling Microsoft Entra ID authentication, showing both Windows (PowerShell) and Linux (Bash) syntax if there are differences.
- Include a section or note clarifying that the Azure portal steps are platform-agnostic, but also provide equivalent command-line instructions for users who prefer or require CLI workflows.
- If PowerShell examples are added in the future, ensure that Bash/Linux equivalents are also provided.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/cache-troubleshoot-timeouts.md
...s/azure-cache-for-redis/cache-troubleshoot-timeouts.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally avoids explicit Windows bias in terms of tooling or examples, but there is a subtle 'Windows-first' pattern: most troubleshooting steps and examples are generic or platform-agnostic, but when platform-specific advice is given, Linux is treated as an exception (e.g., 'TCP settings for Linux based client applications'), and no equivalent Windows-specific advice is provided. There are no explicit Linux command-line or monitoring examples, and the only command-line example given (redis-cli) is cross-platform. There are no PowerShell or Windows-specific tool references, but Linux-specific troubleshooting is minimal and not as detailed as the general guidance.
Recommendations
- Provide equivalent troubleshooting sections for Windows-based client applications, such as TCP settings or common Windows networking issues, to match the Linux-specific section.
- When mentioning platform-specific issues (e.g., TCP settings for Linux), present both Windows and Linux considerations side by side, or clarify when an issue is not relevant to one platform.
- Include example commands or monitoring tools for both Linux (e.g., top, vmstat, netstat) and Windows (e.g., Task Manager, Resource Monitor, perfmon) when discussing CPU, memory, and network troubleshooting.
- Ensure parity in depth and detail for both Linux and Windows client troubleshooting, so Linux users do not feel their scenarios are an afterthought.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-compute-fleet/quickstart-create-portal.md
...ticles/azure-compute-fleet/quickstart-create-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. In the section on administrator account setup, password requirements are described first, referencing the Windows VM FAQ, while SSH key guidance for Linux is secondary. The password requirements link points to Windows-specific documentation, and the Linux SSH key link is less prominent. No Linux-specific troubleshooting or advanced options are provided, and the general tone and ordering favor Windows patterns.
Recommendations
- Present Linux and Windows options in parallel or with equal prominence, rather than listing Windows (password) first.
- Link to both Windows and Linux password/SSH requirements documentation where appropriate.
- Include Linux-specific guidance or troubleshooting tips, such as SSH connection verification or common Linux deployment considerations.
- Ensure that examples and references are balanced between Windows and Linux, and avoid defaulting to Windows terminology or documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-fluid-relay/includes/sign-in-extensions.md
...icles/azure-fluid-relay/includes/sign-in-extensions.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation focuses exclusively on signing in to Azure using Visual Studio Code, a GUI tool that is often associated with Windows workflows. There is no mention of command-line alternatives (such as Azure CLI), nor are there instructions for users on Linux or macOS who may prefer or require non-GUI methods. This creates a bias towards Windows-centric tools and omits Linux-friendly approaches.
Recommendations
- Include instructions for signing in to Azure using the Azure CLI, which is cross-platform and commonly used on Linux.
- Mention alternative sign-in methods for users who do not use Visual Studio Code or prefer command-line interfaces.
- Add explicit notes or sections for Linux/macOS users, ensuring parity in documentation and tool recommendations.
- If screenshots are provided, consider including examples from multiple platforms or clarifying that the process is similar across OSes.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-fluid-relay/how-tos/deploy-fluid-static-web-apps.md
...re-fluid-relay/how-tos/deploy-fluid-static-web-apps.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows environments by exclusively using Visual Studio Code and its Azure extension for all deployment and management steps, without mentioning or providing alternatives for Linux users (such as command-line tools or cross-platform instructions). There are no examples or instructions for deploying or managing the app outside of the Visual Studio Code GUI, which is more common in Windows workflows. No Linux-specific tools, shell commands, or terminal-based alternatives are provided.
Recommendations
- Add instructions for deploying and managing Azure Static Web Apps using the Azure CLI and/or GitHub Actions directly from the terminal, which are cross-platform and commonly used on Linux.
- Include examples of how to run build and deployment commands from a Linux shell (bash), not just through Visual Studio Code's GUI.
- Mention that Visual Studio Code is available on Linux and macOS, and clarify if the extension workflow is supported equally on those platforms.
- Provide alternative steps for users who prefer not to use Visual Studio Code, such as using the Azure Portal or CLI.
- Ensure screenshots and instructions are not specific to Windows UI elements, or provide equivalent visuals for Linux/macOS if needed.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-fluid-relay/how-tos/local-mode-with-azure-client.md
...re-fluid-relay/how-tos/local-mode-with-azure-client.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation does not explicitly mention or provide examples for Linux or macOS environments. It uses generic terms like 'terminal window' and 'browser console', but does not clarify cross-platform compatibility or provide Linux-specific instructions. There are no PowerShell or Windows-specific commands, but the lack of explicit Linux parity may lead to user uncertainty.
Recommendations
- Explicitly state that the instructions and commands (such as 'npx ...') work on Windows, Linux, and macOS.
- If there are any platform-specific considerations (e.g., different ways to set environment variables or run services), provide examples for both Windows (Command Prompt/PowerShell) and Linux/macOS (bash/zsh).
- Mention that the 'terminal window' can be any shell (e.g., Command Prompt, PowerShell, bash, zsh) and clarify any differences if they exist.
- Add a note confirming that the Azure Fluid Relay local service and the sample code are cross-platform, or provide troubleshooting tips for Linux/macOS users if needed.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-fluid-relay/includes/fork-fluidhelloworld.md
...les/azure-fluid-relay/includes/fork-fluidhelloworld.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation instructs users to open the cloned repository in Visual Studio Code using the menu path 'File > Open Folder', which reflects the Windows UI and does not mention Linux or macOS equivalents. There are no Linux-specific instructions or alternative methods provided for opening the folder, and the documentation assumes familiarity with the Windows interface.
Recommendations
- Include instructions for opening the folder in Visual Studio Code on Linux and macOS, such as using the command line (e.g., 'code .') or referencing the appropriate menu paths for those platforms.
- Use cross-platform language, or explicitly mention that the steps apply to all operating systems, noting any differences where relevant.
- Consider providing screenshots or notes that clarify any platform-specific UI differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-fluid-relay/how-tos/rotate-fluid-relay-access-keys.md
...-fluid-relay/how-tos/rotate-fluid-relay-access-keys.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents PowerShell (a Windows-centric tool) examples before Azure CLI (cross-platform) in both the 'View your access keys' and 'Rotate your access keys' sections. This ordering and the prominence of PowerShell may suggest a Windows-first bias, even though Azure CLI is available on all major platforms. No Linux- or macOS-specific instructions or shell examples are provided, but the presence of Azure CLI mitigates some bias.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more accessible to Linux and macOS users.
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and provide example shell prompts (e.g., bash) to reinforce cross-platform support.
- Consider adding a section or note for Linux/macOS users, clarifying installation steps for Azure CLI and the fluid-relay extension on those platforms.
- If possible, provide bash/zsh shell script examples for common tasks, or at least indicate that the CLI commands can be run in any shell.
- Avoid language that implies PowerShell is the default or preferred method unless there is a technical reason.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/configure-networking-how-to.md
...rticles/azure-functions/configure-networking-how-to.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page does not provide explicit Windows or PowerShell command-line examples, but it does mention AzCopy and Azure Storage Explorer as common tools for copying storage content. Both tools are primarily associated with Windows environments, and there is no mention of Linux-native alternatives or instructions for Linux users. There are no CLI (Bash, PowerShell) examples at all, and the documentation relies on portal and template-based workflows, which are cross-platform. However, the lack of Linux-specific guidance or tool parity constitutes a subtle Windows bias.
Recommendations
- Include explicit instructions or examples for copying storage content using cross-platform tools such as Azure CLI or AzCopy on Linux, including installation and usage notes for Linux users.
- Mention that AzCopy is available for Linux and provide a sample command for Linux environments.
- List alternative tools or methods for Linux users, such as using Azure CLI (az storage blob/file commands) for copying data.
- When referencing Azure Storage Explorer, clarify its cross-platform availability and provide installation links for Linux and macOS.
- Consider adding a section or callout for Linux/macOS users to ensure parity and inclusivity in tooling and instructions.