Azure Relay

44
Total Pages
26
Linux-Friendly Pages
18
Pages with Bias
40.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (23)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/authenticate-managed-identity.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a Windows bias by exclusively providing instructions and examples for Windows environments, such as creating and connecting to Windows VMs, referencing RDP, and omitting Linux-based alternatives. There are no Linux VM setup or usage instructions, and the sample walkthrough assumes a Windows workflow throughout.
Recommendations:
  • Add parallel instructions for creating and configuring a Linux VM, including enabling managed identity on Linux.
  • Include steps for copying and running the sample application on a Linux VM (e.g., using SSH and .NET Core on Linux).
  • Mention and link to Linux-specific documentation for connecting to Azure VMs (e.g., SSH instead of RDP).
  • Ensure code samples and instructions are platform-agnostic or provide both Windows and Linux variants where applicable.
  • Clarify that the sample applications can be run on both Windows and Linux, and provide any prerequisites or differences for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-exceptions.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools
Summary:
The documentation page does not provide any OS-specific examples, but it references .NET APIs and tools (such as ServicePointManager) that are traditionally associated with Windows environments. There are no Linux-specific troubleshooting steps, examples, or mentions of Linux tools or patterns. The guidance assumes a .NET/Windows-centric development environment, which may not be directly applicable to Linux users or those using other languages/platforms.
Recommendations:
  • Include troubleshooting steps and examples for Linux environments, such as checking ulimit settings, systemd service logs, or relevant Linux network configuration.
  • Mention cross-platform SDKs and tools (e.g., Azure CLI, Node.js SDK) and provide equivalent guidance for those environments.
  • Clarify when advice is specific to .NET/Windows and offer alternative steps for non-Windows users.
  • Add examples or notes for common Linux firewall configurations and how they might affect Azure Relay connections.
  • Reference platform-agnostic documentation or provide links to language-specific guides for non-Windows platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-hybrid-connections-http-requests-dotnet-get-started.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation assumes the use of Visual Studio (a primarily Windows-based IDE) for all development steps and does not mention or provide instructions for Linux users or alternative development environments. There are no examples or guidance for running or developing the .NET applications on Linux, nor are cross-platform .NET CLI instructions provided.
Recommendations:
  • Include instructions for setting up and running the .NET applications using the .NET CLI (dotnet new, dotnet run, etc.), which works on Linux, macOS, and Windows.
  • Mention and provide examples for using cross-platform editors such as Visual Studio Code.
  • Explicitly state that the tutorial can be followed on Linux and macOS, not just Windows.
  • Add notes or sections for any platform-specific considerations (e.g., how to open/close console windows, install .NET SDK on Linux).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-http-requests-node-get-started-client.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation refers to running npm install from a 'Node command prompt', which is a Windows-centric term and may imply a Windows-first approach. However, the rest of the instructions and code samples are cross-platform and do not show explicit bias towards Windows or PowerShell. There are no Windows-only tools, commands, or examples, but the terminology could be more inclusive.
Recommendations:
  • Replace 'Node command prompt' with 'terminal' or 'command line' to ensure the instructions are clearly applicable to both Windows and Linux users.
  • Explicitly mention that the instructions and code samples work on all major platforms (Windows, Linux, macOS).
  • If there are any platform-specific considerations (such as environment variable syntax), add notes or examples for both Windows and Linux.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/move-across-regions.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a Windows bias by exclusively referencing the Azure portal UI (which is most commonly used on Windows), mentioning Windows Communication Foundation (WCF) relays (a Windows-centric technology), and omitting any command-line or scripting examples (such as Azure CLI, PowerShell, or Bash) that would be relevant for Linux users. There are no Linux-specific instructions or parity in tooling or workflow.
Recommendations:
  • Add Azure CLI examples for exporting, editing, and deploying Resource Manager templates, as Azure CLI is cross-platform and widely used on Linux.
  • Include PowerShell examples as an alternative, but ensure CLI/Bash examples are presented first or alongside PowerShell.
  • Mention that the Azure portal is accessible from any OS, but provide parity for users who prefer or require command-line tools.
  • Clarify that WCF relays are a Windows-specific technology and suggest alternatives or note limitations for Linux users.
  • Provide guidance for editing JSON templates using common Linux text editors (e.g., vim, nano) in addition to generic 'editor of your choice'.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-http-requests-dotnet-get-started-server.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation assumes a Windows development environment by instructing users to create the project in Visual Studio and referencing .NET Framework, which is primarily Windows-only. There are no instructions or examples for creating the application on Linux or using cross-platform tools like .NET Core/SDK CLI. The NuGet package installation steps are also Visual Studio-specific, with no mention of command-line alternatives suitable for Linux.
Recommendations:
  • Add instructions for creating the console application using the .NET CLI (e.g., 'dotnet new console') for cross-platform compatibility.
  • Mention and provide steps for installing the NuGet package via the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay'), which works on Linux, macOS, and Windows.
  • Clarify whether the code is compatible with .NET Core/.NET 5+ and, if so, recommend using those frameworks for cross-platform support.
  • Include a note or section specifically for Linux/macOS users, outlining any differences or additional steps required.
  • Avoid assuming Visual Studio as the only development environment; reference VS Code or other editors where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation is heavily biased toward Windows development environments. All examples and instructions assume the use of Visual Studio on Windows, with no mention of Linux or cross-platform alternatives. The tutorial relies on .NET Framework (not .NET Core/.NET 5+), WCF, and Windows-specific tooling and patterns. There are no instructions or code samples for Linux users, nor any guidance on using cross-platform tools or editors.
Recommendations:
  • Provide equivalent instructions for setting up the development environment on Linux, including using Visual Studio Code or JetBrains Rider, and installing the Azure SDK for .NET on Linux.
  • Include examples using .NET Core or .NET 5+ (which are cross-platform), rather than only .NET Framework.
  • Offer guidance on running and debugging the sample applications on Linux (e.g., using the dotnet CLI, configuring launch.json in VS Code).
  • If WCF is required, clarify its Windows-only limitations and suggest alternatives for Linux (such as gRPC or REST APIs with ASP.NET Core).
  • Mention and provide examples for using Azure CLI (which is cross-platform) instead of only GUI-based steps in Visual Studio.
  • Explicitly state the platform requirements and, if Windows is required, explain why and what Linux/macOS users can do as alternatives.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-relay-tutorial.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation is heavily oriented toward Windows development environments. All examples and instructions assume the use of Visual Studio (a Windows-centric IDE), and there is no mention of Linux or cross-platform alternatives. Steps such as 'Run as administrator', project creation, and configuration are described only for Visual Studio. There are no instructions or code samples for Linux users, nor any mention of .NET Core/.NET 5+ cross-platform capabilities or command-line alternatives (e.g., dotnet CLI). The use of Windows-specific tools and terminology (e.g., Solution Explorer, App.config, NuGet via Visual Studio UI) further reinforces the Windows bias.
Recommendations:
  • Add equivalent instructions for Linux and macOS environments, including how to use the dotnet CLI to create, build, and run projects.
  • Mention and provide examples using cross-platform editors such as VS Code.
  • Include steps for installing prerequisites (e.g., .NET SDK) on Linux and macOS.
  • Show how to manage NuGet packages via the command line (dotnet add package) instead of only through Visual Studio UI.
  • Clarify that WCF on .NET Core/.NET 5+ is limited (client-only), and suggest alternatives or workarounds for Linux users.
  • Avoid assuming the reader is using Windows or Visual Studio; provide generic instructions where possible.
  • If certain features are Windows-only, explicitly state this and provide guidance for non-Windows users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/private-link-service.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a Windows bias by providing only Azure PowerShell CLI examples for automation, referencing the creation of a Windows virtual machine for validation, and omitting equivalent Linux/Bash/CLI instructions. The validation steps assume the use of Windows tools and environments, and there are no examples or guidance for Linux users.
Recommendations:
  • Provide equivalent Azure CLI (az) and/or Bash shell examples for all PowerShell automation steps, ensuring Linux and cross-platform users are supported.
  • Include instructions for creating and validating with a Linux virtual machine, not just Windows, in the validation section.
  • When referencing command-line tools (e.g., nslookup), clarify that the command works on both Windows and Linux, or provide both Windows and Linux command syntax/examples.
  • Avoid assuming the user is on Windows in validation and management steps; offer parity for Linux/macOS environments.
  • Explicitly mention cross-platform support and tools in the prerequisites and throughout the documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-api-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates Windows bias by prioritizing .NET Framework (a Windows-only technology) and WCF (Windows Communication Foundation) in both the API table and the detailed explanations. There are no explicit Linux or cross-platform command-line examples, nor is there mention of Linux-specific tools or patterns. The .NET Standard library is described as cross-platform, but examples and references (such as ASP.NET Core) are still Microsoft-centric. No Linux-native frameworks or usage patterns are discussed.
Recommendations:
  • Add explicit Linux usage examples, such as running .NET Standard clients on Linux distributions.
  • Include command-line examples for both Windows (PowerShell) and Linux (bash) environments.
  • Mention and demonstrate integration with Linux-native frameworks (e.g., Kestrel, systemd) where applicable.
  • Clarify cross-platform compatibility in the API table, highlighting which libraries work natively on Linux.
  • Provide parity in documentation for Linux and macOS users, not just Windows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-authentication-and-authorization.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation page focuses on .NET and Microsoft-specific tooling (such as WCF and .NET SDKs) for Azure Relay authentication and authorization, with sample code and references primarily targeting Windows-centric technologies. There are no explicit Linux or cross-platform command-line examples (e.g., Bash, curl, or Azure CLI usage), and the sample links are all for .NET, Java, and JavaScript, but not for scripting or tooling commonly used on Linux. There is also a lack of guidance for generating SAS tokens or managing keys using Linux-native tools.
Recommendations:
  • Add explicit Linux and cross-platform examples for generating SAS tokens (e.g., using Bash, curl, or OpenSSL).
  • Include Azure CLI commands for managing authorization rules and keys, demonstrating usage on both Windows and Linux shells.
  • Provide sample scripts or code snippets in Python or Bash for authenticating and connecting to Azure Relay from Linux environments.
  • Mention and link to relevant Linux tools or SDKs (such as Azure CLI, Python SDK, or REST API usage) alongside .NET and Windows-specific tools.
  • Ensure that any screenshots or UI instructions clarify that the steps are platform-agnostic or provide alternatives for Linux users where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-hybrid-connections-dotnet-api-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively provides C#/.NET code samples and does not mention or provide any platform-specific instructions, but all examples implicitly assume a Windows/.NET development environment. There are no Linux-specific instructions, examples, or references to cross-platform usage, which may leave Linux developers without guidance on how to use Azure Relay in their environment.
Recommendations:
  • Explicitly state that the .NET Standard APIs and code samples are cross-platform and can be used on Linux, macOS, and Windows.
  • Include instructions or notes on how to run the provided .NET code samples on Linux (e.g., using .NET Core/SDK on Linux).
  • If there are any platform-specific considerations (such as firewall configuration, dependencies, or environment variables), document these for Linux users.
  • Provide example commands for building and running the code on Linux (e.g., using 'dotnet build' and 'dotnet run' in a terminal).
  • Link to official Microsoft documentation on installing .NET on Linux.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-hybrid-connections-dotnet-get-started.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE), omitting any mention of Linux-compatible development tools or workflows. All instructions assume the use of Visual Studio, with no guidance for Linux users (e.g., using VS Code, .NET CLI, or Mono). There are no Linux-specific examples or notes on cross-platform compatibility.
Recommendations:
  • Include instructions for setting up and running the .NET applications using the .NET CLI (dotnet new, dotnet run), which works on Linux, macOS, and Windows.
  • Mention and provide examples for using cross-platform editors like Visual Studio Code.
  • Add a note clarifying that the sample code is compatible with .NET Core/.NET 5+ and can be run on Linux and macOS, not just Windows.
  • Provide terminal/command-line instructions for Linux and macOS users alongside Visual Studio steps.
  • Explicitly state any Windows-only requirements, or confirm that there are none, to reassure non-Windows users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-hybrid-connections-http-requests-dotnet-get-started.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation assumes the use of Visual Studio (a primarily Windows IDE) and does not mention or provide instructions for Linux or cross-platform development environments. There are no examples or guidance for running or developing the .NET applications on Linux, nor are alternative tools (such as VS Code or command-line .NET CLI) mentioned.
Recommendations:
  • Include instructions for setting up and running the .NET applications using cross-platform tools such as Visual Studio Code or the .NET CLI.
  • Explicitly mention that .NET Core/.NET 5+ applications can be developed and run on Linux and macOS, not just Windows.
  • Provide Linux-specific steps or notes where relevant, such as installing the .NET SDK on Linux, and running the applications from the terminal.
  • Avoid assuming Visual Studio as the only development environment; offer alternatives suitable for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-port-settings.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation focuses exclusively on Windows Communication Foundation (WCF) Relays and .NET bindings, which are primarily Windows-centric technologies. There are no examples or guidance for Linux users, nor is there mention of cross-platform alternatives or how to configure equivalent functionality on Linux systems.
Recommendations:
  • Include information about using Azure Relay from non-Windows platforms, such as with .NET Core/.NET 5+ (which is cross-platform) or other supported SDKs.
  • Provide examples or references for configuring required ports and bindings on Linux systems, including common firewall configuration commands (e.g., using iptables, ufw, or firewalld).
  • Mention cross-platform alternatives to WCF, such as gRPC or REST-based approaches, where applicable.
  • Clarify which features or bindings are Windows-only and which are available cross-platform.
  • Add a section or note explicitly addressing Linux/macOS users and linking to relevant setup guides.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-what-is-it.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First
Summary:
The documentation page shows a moderate Windows bias, primarily through the emphasis on WCF Relay, which is a Windows-specific (WCF/.NET Framework) technology. WCF Relay is described as a core feature and is given equal prominence to the cross-platform Hybrid Connections, despite being Windows-only. All WCF Relay examples and quick starts are Windows-centric, with no Linux equivalents or alternatives mentioned. However, the Hybrid Connections feature is highlighted as cross-platform, and quick starts for Node.js and Java are included, indicating some effort toward Linux parity.
Recommendations:
  • Clearly indicate that WCF Relay is Windows/.NET Framework-specific and not available on Linux.
  • Add explicit notes or sections for Linux users, clarifying which features are cross-platform and which are Windows-only.
  • Ensure that cross-platform (Linux-friendly) quick starts and samples are listed before or alongside Windows/.NET-specific ones.
  • Consider providing Linux command-line or scripting examples (e.g., using curl, bash, or other common Linux tools) where relevant.
  • When discussing features, lead with the cross-platform Hybrid Connections and only mention WCF Relay as a legacy or Windows-specific option.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio on Windows, and .NET Framework (not .NET Core or .NET 5/6+). All instructions, screenshots, and project templates are for Windows/Visual Studio. There are no references to Linux, cross-platform .NET, or alternative development environments. The use of Windows-specific project types (Console App (.NET Framework), ASP.NET Web Application (.NET Framework)), and instructions such as 'Run as administrator' and reliance on the Web Platform Installer, further reinforce the Windows-centric approach. No Linux or cross-platform alternatives are mentioned or demonstrated.
Recommendations:
  • Add instructions for setting up the development environment on Linux (and macOS), including using Visual Studio Code or JetBrains Rider, and .NET Core/.NET 6+.
  • Provide equivalent examples using .NET Core or .NET 6+ project templates (which are cross-platform), rather than .NET Framework-only templates.
  • Include command-line instructions for dotnet CLI (dotnet new, dotnet add package, dotnet run, etc.) alongside Visual Studio GUI steps.
  • Clarify which parts of the tutorial are Windows-only (e.g., WCF on .NET Framework), and suggest alternatives or workarounds for Linux users (such as using CoreWCF or gRPC).
  • Mention and demonstrate how to run and debug the sample applications on Linux, including any required configuration changes.
  • If certain features are not available on Linux, explicitly state this and provide links to relevant tracking issues or alternative approaches.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-relay-rest-tutorial.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation exhibits a strong Windows bias. All instructions and examples assume the use of Windows-specific tools (Visual Studio, .NET Framework, WCF, App.config), and there is no mention of Linux or cross-platform alternatives. Steps such as 'Run as administrator', adding references via Visual Studio UI, and using Windows file paths are Windows-centric. No guidance is provided for Linux users, such as using .NET Core/.NET 6+, command-line tools, or cross-platform editors. There are no Linux or non-Windows development/testing instructions.
Recommendations:
  • Add a section or parallel instructions for Linux users, including how to set up the environment using .NET Core/.NET 6+ (which is cross-platform).
  • Provide command-line instructions (e.g., using dotnet CLI) for creating, building, and running the project, instead of relying solely on Visual Studio UI.
  • Mention and demonstrate how to use cross-platform editors like VS Code, and how to add NuGet packages and references via CLI.
  • Clarify which features (such as WCF) are Windows-only, and suggest alternatives or workarounds for Linux (e.g., using ASP.NET Core with Azure Relay, if possible).
  • Include Linux-specific testing and running instructions, such as terminal commands and file paths.
  • Avoid language like 'Run as administrator' or 'right-click', or provide equivalent instructions for Linux/macOS environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-relay-tutorial.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio and .NET Framework. All setup and code examples assume the use of Visual Studio on Windows, with no mention of Linux or cross-platform alternatives. There are no instructions or examples for running or developing the WCF Relay service or client on Linux or macOS, nor any mention of .NET Core/.NET 5+ (which are cross-platform). Windows-specific tools and workflows (e.g., Visual Studio, Solution Explorer, App.config) are referenced exclusively and repeatedly, and there are no PowerShell scripts, but the overall workflow is Windows-centric.
Recommendations:
  • Add instructions and examples for setting up and running the WCF Relay service and client using .NET Core or .NET 5+ (which are cross-platform) instead of only .NET Framework.
  • Include steps for using Visual Studio Code or command-line tools (dotnet CLI) for project creation, dependency management, and building/running the application, which work on Linux and macOS as well as Windows.
  • Provide sample code and configuration for Linux/macOS environments, including any necessary changes to configuration files (e.g., using appsettings.json instead of App.config where appropriate).
  • Mention and demonstrate how to install the required SDKs and dependencies on Linux (e.g., via apt, yum, or Homebrew) and how to run the applications from the terminal.
  • Clarify any platform-specific limitations of WCF (e.g., that full WCF server support is not available on .NET Core/.NET 5+ and thus not on Linux), and suggest alternatives (such as gRPC or ASP.NET Core for REST services) for cross-platform scenarios.
  • Where Visual Studio is referenced, also mention Visual Studio Code and/or JetBrains Rider as alternatives, and provide equivalent instructions.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/authenticate-application.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Dotnet Heavy
Summary:
The documentation page demonstrates a Windows/.NET-first bias. The only detailed sample provided is a .NET console application, with C# code highlighted and step-by-step instructions tailored to Visual Studio-style workflows. There are no explicit Linux or cross-platform instructions, nor are there terminal/CLI-based examples for Linux users. While Java and JavaScript samples are linked, the walkthrough and code focus exclusively on .NET, which is most commonly associated with Windows environments.
Recommendations:
  • Add explicit Linux instructions for running the sample applications, including any prerequisites or environment setup (e.g., .NET Core on Linux, Java, Node.js).
  • Provide equivalent code walkthroughs for the Java and JavaScript samples, not just .NET/C#.
  • Include command-line examples using Azure CLI for authentication and role assignment, with sample commands runnable on Linux/macOS terminals.
  • Clarify that the .NET samples can be run cross-platform (if true), and provide instructions for doing so on Linux/macOS.
  • Balance the highlighted code and instructions so that Linux and non-Windows users are equally supported.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/authenticate-managed-identity.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by exclusively providing instructions and examples for Windows environments, such as creating a Windows VM, using RDP for access, and referencing Windows-specific quickstarts. There are no equivalent instructions or examples for Linux VMs or tools, and Linux users are not guided on how to perform the same tasks.
Recommendations:
  • Add parallel instructions for creating and configuring a Linux VM, including enabling managed identity.
  • Provide examples of accessing the VM and running the sample app using SSH and Linux command-line tools.
  • Include notes or sections that highlight any differences or additional steps required for Linux environments.
  • Ensure that sample code and build instructions are platform-agnostic or provide Linux-specific guidance where necessary.
  • Reference both Windows and Linux quickstart articles where available.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/ip-firewall-virtual-networks.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates Windows bias by referencing deployment instructions that link directly to PowerShell-based guidance, omitting equivalent Linux/CLI examples. There is no mention of Linux tools or cross-platform Azure CLI commands for deploying the Resource Manager template, and the only explicit deployment path is via PowerShell, which is Windows-centric. No Linux or Bash shell examples are provided.
Recommendations:
  • Add explicit instructions and examples for deploying the Resource Manager template using Azure CLI (az deployment group create) and Bash shell, ensuring parity with PowerShell instructions.
  • Include links to both PowerShell and Azure CLI documentation for template deployment, making it clear that both Windows and Linux users are supported.
  • Wherever deployment steps are referenced, provide both PowerShell and Bash/Azure CLI command snippets side by side.
  • Review the documentation for other places where only Windows tools or workflows are mentioned, and add Linux equivalents as needed.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/move-across-regions.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation page exclusively describes the process of moving an Azure Relay namespace using the Azure Portal, with all instructions and screenshots based on the portal's UI. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), nor are there any references to Linux tools or workflows. The only technical reference outside the portal is to Windows Communication Foundation (WCF) relays, a Windows-centric technology. This results in a bias toward Windows and GUI-based workflows, potentially disadvantaging Linux users or those who prefer automation and scripting.
Recommendations:
  • Add step-by-step instructions for exporting, editing, and deploying the Resource Manager template using Azure CLI and/or Azure PowerShell, and ensure Azure CLI examples are provided (as it is cross-platform and widely used on Linux).
  • Include sample Bash commands for unzipping the template and editing JSON files, or reference common Linux tools for these tasks.
  • Mention that the Azure Portal is accessible from any OS, but provide parity for users who prefer or require command-line or automated approaches.
  • Clarify the role of WCF relays and, if possible, provide context or alternatives for users not on Windows platforms.
  • Ensure that all screenshots and instructions are not overly specific to Windows UI conventions (e.g., file explorer paths, right-click context menus) and use neutral language where possible.