Azure Fluid Relay

54
Total Pages
50
Linux-Friendly Pages
4
Pages with Bias
7.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

7 issues found
Showing 1-7 of 7 flagged pages
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-12-29 18:00
Reviewed by: Unknown
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 discussed before Azure CLI examples, and the PowerShell module is mentioned first in each relevant section. There are no explicit Linux-specific examples or references to Linux shells or scripting environments. The CLI examples are present, but PowerShell is consistently prioritized, and no Bash or cross-platform scripting guidance is given. Additionally, the prerequisites link to a tutorial for managed identities that is Windows VM-specific.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
  • Add explicit Bash or shell scripting examples where relevant, or clarify that Azure CLI commands work identically on Linux/macOS.
  • Review and update prerequisite links to ensure they are not Windows-specific (e.g., avoid linking to Windows VM tutorials unless necessary).
  • Mention that PowerShell examples can also be run on Linux/macOS if using PowerShell Core, or provide Bash equivalents for common tasks.
  • Where possible, include troubleshooting steps or notes relevant to Linux environments (e.g., file path formats, authentication differences).
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
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing 'Command Prompt' and using Windows-style paths (e.g., C:\My Fluid Projects, \src\App.js) throughout. All command-line instructions assume a Windows environment, with no mention of Linux or macOS equivalents (e.g., using 'cd' with Windows paths, no mention of terminal or shell). There are no examples or instructions for Linux users, and the only terminal environment referenced is Windows Command Prompt.
Recommendations
  • Add Linux/macOS equivalents for all command-line instructions, including path formats (e.g., ~/fluid-projects or ./src/App.js) and terminal usage.
  • Replace references to 'Command Prompt' with more inclusive terms like 'terminal' or 'command line', or specify instructions for both Windows and Linux/macOS.
  • Show both Windows and Linux/macOS path examples when navigating directories or opening files.
  • Explicitly state that the instructions apply to all platforms, or provide platform-specific notes where behavior differs.
  • Consider including screenshots or code snippets that use Linux/macOS environments in addition to Windows.
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-12 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, and includes explicit instructions for installing the Azure Fluid Relay PowerShell module. The prerequisites link to a Windows VM tutorial for managed identities. There is a slight preference for Windows-centric tooling and patterns, such as PowerShell, which may create friction for Linux/macOS users, although Azure CLI examples are provided and REST API usage is documented.
Recommendations
  • Ensure that Azure CLI examples are presented before or alongside PowerShell examples, as CLI is cross-platform.
  • Add explicit notes clarifying that both Azure CLI and REST API methods are fully supported on Linux and macOS.
  • Replace or supplement links to Windows VM tutorials with platform-neutral or Linux/macOS equivalents for managed identity setup.
  • Where PowerShell modules are referenced, provide equivalent Bash or shell script snippets for common Linux/macOS workflows.
  • Explicitly state platform compatibility for all tools and commands.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Windows-centric tooling (PowerShell) before cross-platform options (Azure CLI) in both key viewing and rotation sections. PowerShell examples and instructions are given equal prominence to Azure CLI, but PowerShell is traditionally Windows-focused, and its module installation instructions may not be as relevant for Linux/macOS users. No Linux-specific shell examples (e.g., Bash) are provided, and the ordering implies a Windows-first approach.
Recommendations
  • Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Add Bash shell examples for common tasks, such as piping output or using jq to parse CLI results.
  • Clarify PowerShell's cross-platform availability, or note any limitations for non-Windows users.
  • Consider adding a table comparing tool compatibility across OSes.
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-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation focuses exclusively on using Visual Studio Code (VS Code) for Azure sign-in, which is a tool more commonly associated with Windows environments. There are no examples or instructions for signing into Azure using Linux-native tools or command-line interfaces, and no mention of alternatives such as the Azure CLI or platform-specific guidance for Linux users.
Recommendations
  • Add instructions for signing into Azure using the Azure CLI, which is cross-platform and widely used on Linux.
  • Explicitly mention that VS Code is available on Linux and macOS, or provide platform-specific notes if there are differences.
  • Include screenshots or terminal commands relevant to Linux environments.
  • Provide parity by listing both GUI (VS Code) and CLI (Azure CLI) methods for signing in to Azure.
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-12 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 'View your access keys' and 'Rotate your access keys' sections. PowerShell examples are given equal prominence to Azure CLI, but are listed before CLI, which is more universally available on Linux/macOS. There are no Linux/macOS-specific examples or notes, and the documentation does not mention platform compatibility for the tools.
Recommendations
  • List Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly state that Azure CLI commands work on Windows, Linux, and macOS.
  • Add notes or sections clarifying platform compatibility for each tool.
  • Consider including bash shell examples or instructions for Linux/macOS users where relevant.
  • If PowerShell is required for certain tasks, provide installation guidance for PowerShell on Linux/macOS.
GitHub Create Pull Request
Azure Fluid Relay Customer-managed keys for Azure Fluid Relay encryption ...es/azure-fluid-relay/concepts/customer-managed-keys.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation presents PowerShell examples and instructions before Azure CLI, and references Windows-specific tools and tutorials (e.g., managed identity tutorial for Windows VM). PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. However, Azure CLI examples are provided, which are cross-platform, and REST API instructions are included. No critical functionality is Windows-only, but the ordering and references show a mild Windows bias.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Replace or supplement references to Windows-specific tutorials (e.g., managed identity tutorial for Windows VM) with platform-neutral or Linux/macOS equivalents.
  • Explicitly state that Azure CLI and REST API methods work on all platforms, and highlight cross-platform compatibility.
  • Consider adding bash or shell script examples where appropriate.
  • Review and adjust language to avoid assuming PowerShell as the default automation tool.
GitHub Create Pull Request