Azure Fluid Relay

27
Total Pages
21
Linux-Friendly Pages
6
Pages with Bias
22.2%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

15 issues found
Showing 1-15 of 15 flagged pages
Azure Fluid Relay Customer-managed keys for Azure Fluid Relay encryption ...es/azure-fluid-relay/concepts/customer-managed-keys.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided and referenced before Azure CLI, and prerequisite links and instructions (e.g., managed identity tutorial) point to Windows-centric resources. Azure PowerShell (a Windows-first tool) is given equal or greater prominence than Azure CLI, and there are no explicit Linux shell or scripting examples. The documentation does not mention Linux-specific patterns, nor does it clarify cross-platform compatibility for CLI or REST instructions.
Recommendations
  • Provide explicit Bash/Linux shell examples alongside PowerShell, especially for Azure CLI usage.
  • Ensure prerequisite tutorials and links include Linux and cross-platform instructions (e.g., managed identity setup for Linux VMs).
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and highlight any platform-specific considerations.
  • Consider listing Azure CLI examples before PowerShell, as CLI is cross-platform.
  • Add notes or sections on using REST API and CLI from Linux environments, including authentication and environment setup.
  • Review all referenced tutorials and ensure Linux parity in their content.
GitHub Create Pull Request
Azure Fluid Relay Customer-managed keys for Azure Fluid Relay encryption ...es/azure-fluid-relay/concepts/customer-managed-keys.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell examples and instructions before Azure CLI examples, and references Windows-specific tutorials for managed identities. There are no explicit Linux shell or Bash examples, nor any mention of Linux-specific patterns or tools. The PowerShell instructions are more prominent, and prerequisite links reference Windows VM tutorials, indicating a bias toward Windows environments.
Recommendations
  • Add Bash and Linux shell examples for resource creation and management, especially for REST API calls.
  • Reference Linux VM tutorials for managed identity setup alongside Windows VM tutorials.
  • Ensure Azure CLI examples are as detailed and prominent as PowerShell examples.
  • Include notes on cross-platform compatibility for all commands and tools.
  • Where possible, provide parity in troubleshooting steps for Linux environments (e.g., Key Vault access from Linux VMs).
GitHub Create Pull Request
Azure Fluid Relay Customer-managed keys for Azure Fluid Relay encryption ...es/azure-fluid-relay/concepts/customer-managed-keys.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for creating and updating Azure Fluid Relay resources with CMK, and references a Windows VM tutorial for managed identities. PowerShell is a Windows-centric tool, and its examples are presented before Azure CLI, which is more cross-platform. There are no explicit Linux/bash examples or references to Linux-specific workflows, and the prerequisites link to a Windows VM tutorial for managed identities, omitting Linux VM equivalents.
Recommendations
  • Add explicit bash/Linux shell examples for REST API calls (e.g., using curl) and Azure CLI usage.
  • Include links to managed identity tutorials for Linux VMs alongside the Windows VM tutorial.
  • Present Azure CLI examples before PowerShell examples, or clarify that CLI is cross-platform and suitable for both Windows and Linux.
  • Mention that PowerShell Core is available on Linux, if relevant, but provide bash alternatives for common operations.
  • Review troubleshooting and prerequisites sections for references to Windows-only tools or workflows, and add Linux equivalents where missing.
GitHub Create Pull Request
Azure Fluid Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-fluid-relay/concepts/customer-managed-keys.md ...es/azure-fluid-relay/concepts/customer-managed-keys.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples and references are provided before Azure CLI, and prerequisite links and instructions (such as managed identity setup) reference Windows VM tutorials. The PowerShell module is highlighted and installed first, and troubleshooting steps reference Azure portal and Windows-centric patterns. There are no explicit Linux shell or cross-platform scripting examples, and the documentation assumes familiarity with PowerShell and Windows resource management tools.
Recommendations
  • Provide Bash and Linux shell scripting examples alongside PowerShell, especially for resource creation and management.
  • Reference Linux VM tutorials and managed identity setup guides, not just Windows VM instructions.
  • Clarify that Azure CLI commands work cross-platform and highlight usage on Linux/macOS where relevant.
  • Balance the order of examples: present Azure CLI before or alongside PowerShell, as CLI is more platform-neutral.
  • Add troubleshooting steps and notes relevant to Linux environments (e.g., file path formats, authentication issues).
GitHub Create Pull Request
Azure Fluid Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-fluid-relay/concepts/customer-managed-keys.md ...es/azure-fluid-relay/concepts/customer-managed-keys.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided and discussed in detail, and PowerShell is listed before Azure CLI in all example sections. References to installing PowerShell modules and links to Windows-specific tutorials are present. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments. The CLI examples are generic and do not clarify cross-platform usage or differences.
Recommendations
  • Add explicit Bash examples alongside Azure CLI commands to demonstrate usage in Linux/macOS environments.
  • Clarify that Azure CLI commands work cross-platform and provide notes on any OS-specific considerations.
  • Ensure links to tutorials and prerequisites include Linux/macOS instructions, not just Windows (e.g., managed identity setup).
  • Consider listing Azure CLI before PowerShell in example sections to avoid implicit prioritization of Windows tooling.
  • Mention that PowerShell Core is available cross-platform, or provide Bash alternatives where possible.
GitHub Create Pull Request
Azure Fluid Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-fluid-relay/concepts/customer-managed-keys.md ...es/azure-fluid-relay/concepts/customer-managed-keys.md
High Priority View Details →
Scanned: 2025-07-17 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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).
GitHub Create Pull Request
Azure Fluid Relay Rotate Azure Fluid Relay access keys ...-fluid-relay/how-tos/rotate-fluid-relay-access-keys.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents PowerShell (Windows-centric) instructions before Azure CLI (cross-platform) in both key viewing and rotation sections. PowerShell is highlighted as a primary automation method, which can create friction for Linux/macOS users who typically use Azure CLI or Bash. No explicit Linux/macOS examples or shell commands are provided, and there is no mention of platform-specific considerations.
Recommendations
  • Present Azure CLI instructions before PowerShell to prioritize cross-platform usage.
  • Explicitly mention that Azure CLI works on Windows, Linux, and macOS.
  • Add Bash shell examples for common tasks, especially for Linux users.
  • Clarify any platform-specific prerequisites or differences (e.g., installation steps for CLI on Linux/macOS).
  • Avoid language that implies PowerShell is the default or preferred method.
GitHub Create Pull Request
Azure Fluid Relay Customer-managed keys for Azure Fluid Relay encryption ...es/azure-fluid-relay/concepts/customer-managed-keys.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation presents PowerShell examples and references before Azure CLI examples in each section, and includes explicit instructions for installing the Azure Fluid Relay PowerShell module. PowerShell is a Windows-centric tool, and this ordering subtly prioritizes Windows workflows. There is no mention of Linux/macOS-specific considerations, nor are bash or shell script examples provided. The CLI examples are cross-platform, but are always listed after PowerShell, reinforcing a Windows-first bias.
Recommendations
  • List Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows, while PowerShell is primarily for Windows (with note on PowerShell Core availability on other platforms if relevant).
  • Add bash or shell script examples for REST API calls to demonstrate Linux-native workflows.
  • Include notes or links for Linux/macOS users about installing and using Azure CLI and PowerShell Core.
  • Review prerequisite links to ensure they do not reference Windows-only tutorials unless alternatives are provided.
GitHub Create Pull Request
Azure Fluid Relay Customer-managed keys for Azure Fluid Relay encryption ...es/azure-fluid-relay/concepts/customer-managed-keys.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 🔧 Windows Tools
Summary
The documentation consistently presents PowerShell examples before Azure CLI, and references to PowerShell modules and commands are prominent. The prerequisites link to a Windows VM tutorial for managed identities, and there is no mention of Linux/macOS-specific considerations or examples. The REST API and Azure CLI are cross-platform, but the documentation implicitly assumes Windows-first patterns and tools.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI first to avoid Windows-first bias.
  • Add explicit notes confirming that Azure CLI and REST API are fully supported on Linux/macOS, and provide links to installation guides for those platforms.
  • Replace or supplement the prerequisite link to the Windows VM tutorial with a cross-platform or Linux VM managed identity tutorial.
  • Clarify that PowerShell examples are for Windows users, and encourage Linux/macOS users to use Azure CLI or REST API.
  • Where possible, add troubleshooting tips relevant to Linux/macOS environments.
GitHub Create Pull Request
Azure Fluid Relay 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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
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 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.
GitHub Create Pull Request
Azure Fluid Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-fluid-relay/concepts/customer-managed-keys.md ...es/azure-fluid-relay/concepts/customer-managed-keys.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 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.
GitHub Create Pull Request
Azure Fluid Relay 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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Azure Fluid Relay 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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 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.
GitHub Create Pull Request
Azure Fluid Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-fluid-relay/how-tos/use-audience-in-fluid.md ...les/azure-fluid-relay/how-tos/use-audience-in-fluid.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', 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).
GitHub Create Pull Request
Azure Fluid Relay Rotate Azure Fluid Relay access keys ...-fluid-relay/how-tos/rotate-fluid-relay-access-keys.md
Low 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 presents Windows-centric tools (PowerShell) before cross-platform alternatives (Azure CLI) in both key viewing and rotation sections. PowerShell examples and instructions are given equal prominence to Azure CLI, but are listed first, which may subtly prioritize Windows workflows. No Linux/macOS-specific shell examples or notes are provided, though Azure CLI is cross-platform.
Recommendations
  • List Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly note that Azure CLI commands work on Windows, Linux, and macOS.
  • Add bash/zsh shell example blocks for Linux/macOS users where relevant (e.g., showing CLI usage in a Linux terminal).
  • Clarify any OS-specific prerequisites or installation steps for CLI and PowerShell modules.
  • Consider removing the PowerShell tab or making it secondary unless there are Windows-only features.
GitHub Create Pull Request