Azure Fluid Relay

27
Total Pages
22
Linux-Friendly Pages
5
Pages with Bias
18.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (6)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-fluid-relay/concepts/customer-managed-keys.md [View Details]
Scanned: 2025-07-17 00:00 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools
Summary:
The documentation demonstrates a Windows bias by providing detailed PowerShell examples and instructions before Azure CLI, referencing PowerShell modules and commands prominently, and linking to Windows-specific managed identity tutorials. There is no mention of Linux-specific shell usage, nor are there Bash or cross-platform scripting examples. The prerequisite tutorial link is Windows VM-specific, and PowerShell is presented as the primary scripting interface.
Recommendations:
  • Provide Bash and cross-platform shell examples alongside PowerShell, especially for Azure CLI usage.
  • Reference Linux and macOS environments explicitly, including links to managed identity tutorials for Linux VMs.
  • Avoid presenting PowerShell examples before CLI or REST unless usage data shows a clear majority of users on Windows.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide any necessary OS-specific notes.
  • Balance tool references by including both Windows and Linux equivalents where relevant (e.g., for identity creation or key management).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-fluid-relay/how-tos/use-audience-in-fluid.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation consistently refers to 'Command Prompt', uses Windows-style paths (e.g., C:\My Fluid Projects, \src\App.js), and does not provide Linux/macOS equivalents for commands or file paths. There are no explicit Linux or macOS instructions or terminal examples, and all navigation and command-line instructions are written with a Windows-first perspective.
Recommendations:
  • Provide parallel instructions for Linux/macOS users, including using 'Terminal' instead of only 'Command Prompt'.
  • Use cross-platform path examples or show both Windows (C:\My Fluid Projects) and Unix-style (~/fluid-projects) paths.
  • Mention that all commands (npx, npm) work in any terminal (Command Prompt, PowerShell, Terminal, etc.) and are not Windows-specific.
  • Use forward slashes in file paths (src/App.js) or clarify that backslashes are for Windows and forward slashes for Unix-based systems.
  • Add notes or callouts where behavior might differ on Linux/macOS (e.g., environment variables, permissions, or port usage).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-fluid-relay/includes/fork-fluidhelloworld.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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 alternative instructions or screenshots for Linux users, nor is there mention of command-line alternatives for opening the folder in VS Code.
Recommendations:
  • Include instructions for opening the folder in VS Code on Linux and macOS, such as using the 'code .' command in the terminal.
  • Mention that the menu path may differ on other operating systems and provide the equivalent steps or screenshots for Linux/macOS.
  • Use cross-platform language (e.g., 'Open the folder in Visual Studio Code using the menu or by running code . in your terminal') to ensure inclusivity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-fluid-relay/concepts/customer-managed-keys.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a mild Windows bias. In the prerequisites section, the only tutorial linked for creating a user-assigned managed identity is specifically for Windows VMs, with no equivalent Linux guidance provided. There are no command-line examples (e.g., PowerShell, CLI, Bash), but the only deep-link for a step is Windows-specific, and Linux is not mentioned as an option.
Recommendations:
  • Add links to both Windows and Linux tutorials for creating user-assigned managed identities.
  • Wherever possible, provide cross-platform Azure CLI examples instead of or in addition to platform-specific guides.
  • Explicitly mention that the steps apply to both Windows and Linux, or clarify any platform-specific differences.
  • Review all prerequisite links and ensure Linux parity for all referenced setup guides.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-fluid-relay/how-tos/deploy-fluid-static-web-apps.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a bias toward Windows by exclusively using Visual Studio Code and its Azure extension for deployment steps, without mentioning or providing alternatives for Linux users (such as CLI-based deployment or cross-platform tooling). There are no command-line examples, and all instructions assume the use of a GUI tool that is most commonly used on Windows. No mention is made of Linux-specific workflows or considerations.
Recommendations:
  • Include CLI-based deployment instructions using Azure CLI or GitHub Actions that work across Windows, Linux, and macOS.
  • Explicitly mention that Visual Studio Code and its extensions are cross-platform, or provide alternative instructions for users who may prefer terminal-based workflows.
  • Add examples or notes for deploying from Linux environments, such as using Bash scripts or terminal commands.
  • Ensure screenshots and step-by-step guides are not exclusively tied to Windows UI conventions.
  • Provide parity in documentation by showing both GUI and CLI approaches for all major steps.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-fluid-relay/includes/sign-in-extensions.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation focuses exclusively on signing into Azure via Visual Studio Code, a tool often associated with Windows workflows. There is no mention of alternative sign-in methods (such as CLI-based sign-in) that are commonly used on Linux, nor are there any Linux-specific instructions or screenshots. This may disadvantage Linux users who do not use Visual Studio Code or prefer command-line tools.
Recommendations:
  • Include instructions for signing into Azure using the Azure CLI (az login), which is cross-platform and commonly used on Linux.
  • Add screenshots or examples that show the process on Linux systems, or clarify that the process is the same across platforms if applicable.
  • Mention alternative editors or tools that Linux users may use, or provide parity in guidance for non-VS Code environments.
  • Explicitly state that Visual Studio Code is available on Linux, if relevant, and provide installation links or notes for Linux users.