Azure Relay

44
Total Pages
23
Linux-Friendly Pages
21
Pages with Bias
47.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

200 issues found
Showing 76-100 of 200 flagged pages
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-relay-tutorial.md ...ain/articles/azure-relay/service-bus-relay-tutorial.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/authenticate-application.md .../main/articles/azure-relay/authenticate-application.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/authenticate-managed-identity.md .../articles/azure-relay/authenticate-managed-identity.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/ip-firewall-virtual-networks.md ...n/articles/azure-relay/ip-firewall-virtual-networks.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/private-link-service.md ...blob/main/articles/azure-relay/private-link-service.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Azure Relay Authenticate with managed identities for Azure Relay resources .../articles/azure-relay/authenticate-managed-identity.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing step-by-step instructions and examples exclusively for Windows VMs. It references Windows VM creation, Windows-specific connection methods (RDP), and does not include equivalent instructions or examples for Linux VMs or macOS environments. While code samples are cross-platform (.NET, Java, JavaScript), the walkthrough for enabling managed identity and running the sample app is Windows-only.
Recommendations
  • Add parallel instructions for creating and configuring a Linux VM with managed identity.
  • Include guidance for connecting to Linux VMs (e.g., SSH) and copying files.
  • Provide sample commands for building and running the sample app on Linux/macOS.
  • Clarify that the sample apps are cross-platform and can be run on non-Windows environments.
  • Reference documentation for enabling managed identity on Linux VMs.
GitHub Create Pull Request
Azure Relay Authenticate from an application - Azure Relay .../main/articles/azure-relay/authenticate-application.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily demonstrates authentication with Azure Relay using .NET console application samples, which are most commonly run on Windows. The highlighted code and walkthrough focus on .NET/C#, with no explicit mention of Linux/macOS compatibility or instructions for running the sample on those platforms. While Java and JavaScript samples are linked, the main example and step-by-step guidance center on .NET. Additionally, PowerShell is mentioned first in the 'Next steps' section for role assignment, before CLI or REST API alternatives.
Recommendations
  • Explicitly mention that the .NET sample can be run on Linux/macOS using .NET Core/.NET 5+.
  • Provide example commands or instructions for running the sample on Linux/macOS (e.g., using 'dotnet run' on Ubuntu).
  • Include a Linux/macOS terminal screenshot or walkthrough alongside the Windows example.
  • List Azure CLI instructions before or alongside PowerShell for role assignment, or clarify parity.
  • Highlight Java and JavaScript samples in the main body, not just in the 'Samples' section, and note their cross-platform nature.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-server.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-server.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is focused on creating a .NET Framework console application using Visual Studio, which is a Windows-centric development environment and technology. There are no instructions or examples for Linux/macOS users, such as using .NET Core/.NET 5+ (cross-platform) or alternative IDEs like VS Code. The NuGet package installation steps are specific to Visual Studio's GUI, with no mention of command-line alternatives suitable for Linux/macOS.
Recommendations
  • Add instructions for creating a cross-platform .NET (Core/.NET 5+) console application using the 'dotnet' CLI.
  • Include NuGet package installation steps using the 'dotnet add package' command.
  • Mention alternative IDEs such as Visual Studio Code or JetBrains Rider, which are available on Linux/macOS.
  • Clarify whether the Microsoft.Azure.Relay package and sample code are compatible with .NET Core/.NET 5+ on Linux/macOS.
  • Provide example commands and code snippets that work on Linux/macOS.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-http-requests-dotnet-get-started-client.md ...id-connections-http-requests-dotnet-get-started-client.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation assumes the use of Visual Studio and .NET Framework, both of which are primarily Windows-centric. Instructions for creating the console app and installing NuGet packages are given only for Visual Studio on Windows, with no mention of cross-platform alternatives like .NET Core/.NET 5+ or command-line tooling usable on Linux/macOS. There are no Linux/macOS-specific instructions or examples.
Recommendations
  • Add instructions for creating a cross-platform .NET console application using .NET Core/.NET 5+ (e.g., 'dotnet new console').
  • Include guidance for installing NuGet packages via the command line (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Clarify whether the Microsoft.Azure.Relay SDK and sample code work on Linux/macOS, and provide any necessary platform-specific notes.
  • Present both Visual Studio (Windows) and VS Code/CLI (cross-platform) workflows, or at least mention alternatives.
  • Consider showing code examples that target .NET Standard or .NET 5+ for broader OS compatibility.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-http-requests-dotnet-get-started-server.md ...id-connections-http-requests-dotnet-get-started-server.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation instructs users to create a Console App (.NET Framework) project in Visual Studio and uses Visual Studio's GUI for NuGet package management. These are Windows-centric tools and workflows. There is no mention of cross-platform alternatives (e.g., .NET Core/.NET 5+, CLI commands, VS Code, or Linux/macOS development environments). The code itself is C# and could be cross-platform if targeting .NET Core/.NET 5+, but the instructions are Windows-first and omit Linux/macOS guidance.
Recommendations
  • Add instructions for creating a cross-platform .NET Core or .NET 5+ console application using the dotnet CLI, which works on Linux and macOS.
  • Include NuGet package installation steps using the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay') for non-Windows environments.
  • Mention alternative development environments such as VS Code or JetBrains Rider that are available on Linux/macOS.
  • Clarify whether the Microsoft.Azure.Relay SDK and Hybrid Connections are supported on non-Windows platforms, and provide any necessary platform-specific notes.
GitHub Create Pull Request
Azure Relay Authenticate from an application - Azure Relay .../main/articles/azure-relay/authenticate-application.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily demonstrates authentication with Azure Relay using .NET console applications, which are typically associated with Windows environments. The sample code and walkthrough focus on .NET and C#, with no explicit mention of how to run equivalent samples on Linux or macOS. In the 'Next steps' section, Azure PowerShell is listed before Azure CLI, and there is no guidance on Linux/macOS-specific setup or troubleshooting. Although Java and JavaScript samples are linked, the main walkthrough and code highlights are Windows/.NET-centric.
Recommendations
  • Add explicit instructions or notes on running the .NET sample on Linux and macOS (e.g., using .NET Core/.NET 6+).
  • Provide highlighted code samples or walkthroughs for Java and JavaScript, not just .NET.
  • Mention cross-platform compatibility of the Azure Relay SDKs and clarify any OS-specific requirements.
  • List Azure CLI before PowerShell in 'Next steps', or present both equally, to better support Linux/macOS users.
  • Include troubleshooting tips for common Linux/macOS issues (e.g., environment variables, certificate handling).
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-client.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-client.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is written with a clear Windows bias: it instructs users to create a Console App (.NET Framework) project in Visual Studio, a Windows-only IDE and framework. There are no instructions or examples for Linux/macOS users (e.g., using .NET Core/.NET 5+ or cross-platform editors like VS Code). The NuGet package installation steps are also Visual Studio-centric, omitting CLI alternatives.
Recommendations
  • Provide instructions for creating a cross-platform .NET (Core/5+) console application using the 'dotnet new console' CLI command.
  • Include NuGet package installation steps using the 'dotnet add package' CLI, which works on all platforms.
  • Mention and show examples for using VS Code or other cross-platform editors.
  • Clarify whether the sample code is compatible with .NET Core/.NET 5+ and, if not, provide a cross-platform version.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-http-requests-dotnet-get-started-client.md ...id-connections-http-requests-dotnet-get-started-client.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation assumes the use of Visual Studio and .NET Framework, both of which are primarily Windows tools. It provides only Windows-centric instructions for project creation and NuGet package management, with no mention of cross-platform alternatives (e.g., .NET Core/SDK CLI, Visual Studio Code, or Linux/macOS development environments). There are no Linux/macOS-specific instructions or examples.
Recommendations
  • Add instructions for creating the project using the .NET CLI (e.g., 'dotnet new console') to support Linux/macOS users.
  • Mention that the Microsoft.Azure.Relay NuGet package can be installed via the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Clarify if the code sample works with .NET Core/.NET 5+ (which are cross-platform), and update the instructions to use a cross-platform .NET version if possible.
  • Include a note or section for Linux/macOS users describing how to set up their environment and run the sample.
  • If .NET Framework is required and the feature is Windows-only, explicitly state this to avoid confusion.
GitHub Create Pull Request
Azure Relay Authenticate with managed identities for Azure Relay resources .../articles/azure-relay/authenticate-managed-identity.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides step-by-step instructions and examples exclusively for Windows VMs, including references to RDP and Windows-specific VM images. There are no equivalent instructions or examples for Linux VMs or non-Windows environments, despite Azure Relay and managed identities being cross-platform features. Linux and macOS users are left without guidance for enabling managed identity, deploying, or running the sample applications.
Recommendations
  • Add parallel instructions for enabling managed identity on Linux VMs, linking to the appropriate Azure documentation.
  • Provide examples for deploying and running the sample applications on Linux VMs, including how to connect (e.g., using SSH instead of RDP).
  • Clarify in the 'Sample app on VM accessing Relay entities' section that the steps are for Windows VMs, and provide a separate section for Linux VMs.
  • Ensure that sample code and instructions reference .NET Core/.NET 5+ (which are cross-platform) and show how to build and run the sample on Linux/macOS.
  • Mention or link to the Java and JavaScript samples in the context of Linux/macOS usage, not just in the final 'Samples' section.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-http-requests-dotnet-get-started-server.md ...id-connections-http-requests-dotnet-get-started-server.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation assumes the use of Visual Studio and .NET Framework, both of which are primarily Windows tools. There are no instructions or examples for creating the project using cross-platform tools (e.g., .NET Core/SDK CLI, VS Code), nor any mention of Linux/macOS compatibility. All setup steps are tailored to Windows users.
Recommendations
  • Add instructions for creating the project using the .NET CLI (e.g., 'dotnet new console') which works on Linux/macOS.
  • Clarify whether Microsoft.Azure.Relay supports .NET Core/.NET 5+ and, if so, provide cross-platform code/project instructions.
  • Mention and provide examples for using editors like VS Code or JetBrains Rider, which are available on Linux/macOS.
  • If the feature is not Windows-only, explicitly state Linux/macOS compatibility and provide parity in setup steps.
GitHub Create Pull Request
Azure Relay Authenticate from an application - Azure Relay .../main/articles/azure-relay/authenticate-application.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily features .NET (C#) console application samples, which are most commonly run on Windows, and references PowerShell for role assignment management before mentioning Azure CLI. There are no explicit Linux/macOS setup or run instructions, nor are there examples for running the sample applications on non-Windows platforms. While Java and JavaScript samples are linked, the main walkthrough and code snippets are Windows-centric (.NET).
Recommendations
  • Add explicit instructions or examples for running the sample applications on Linux/macOS, including any required dependencies or environment setup.
  • Provide equivalent shell (bash) commands for Azure CLI alongside PowerShell commands, and consider listing Azure CLI before PowerShell to avoid Windows-first bias.
  • Highlight cross-platform compatibility of .NET Core/.NET 5+ samples, and clarify if the provided .NET samples can be run on Linux/macOS.
  • Include code snippets or walkthroughs for Java and JavaScript samples, not just links, to improve parity.
  • Mention any platform-specific considerations or limitations for Linux/macOS users.
GitHub Create Pull Request
Azure Relay Authenticate with managed identities for Azure Relay resources .../articles/azure-relay/authenticate-managed-identity.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a notable Windows bias by providing a step-by-step walkthrough that exclusively uses a Windows 10 VM, references RDP for access, and links only to Windows VM setup guides. There are no equivalent instructions or examples for Linux VMs or non-Windows environments, even though managed identities and Azure Relay are cross-platform features. While code samples are cross-platform (.NET, Java, JavaScript), the operational guidance is Windows-centric.
Recommendations
  • Add parallel instructions for creating and configuring a Linux VM with managed identity enabled.
  • Include guidance for connecting to Linux VMs (e.g., using SSH) and copying files to Linux VMs.
  • Provide Linux/macOS command-line examples for running the sample applications.
  • Link to both Windows and Linux VM creation guides in the setup steps.
  • Clarify that the sample apps can be run on Linux/macOS and provide any necessary prerequisites or differences.
GitHub Create Pull Request
Azure Relay Configure IP firewall for Azure Relay namespace ...n/articles/azure-relay/ip-firewall-virtual-networks.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides instructions for configuring IP firewall rules for Azure Relay namespaces using the Azure portal and Resource Manager templates. When referencing command-line deployment, it links specifically to PowerShell-based instructions, which are Windows-centric, and does not mention or provide parity for Linux/macOS CLI alternatives (such as Azure CLI or Bash). Additionally, the deployment link for Resource Manager templates is PowerShell-focused and appears before any mention of cross-platform tools.
Recommendations
  • Include instructions or links for deploying Resource Manager templates using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • When referencing command-line deployment, mention both PowerShell and Azure CLI options, or provide a neutral landing page that covers both.
  • Ensure examples and links do not default to Windows tools unless the feature is Windows-only (which is not the case here).
GitHub Create Pull Request
Azure Relay Integrate Azure Relay with Azure Private Link Service ...blob/main/articles/azure-relay/private-link-service.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides detailed instructions for integrating Azure Relay with Azure Private Link Service, but it demonstrates a notable Windows bias. The only CLI-based automation example is in Azure PowerShell, with no equivalent Azure CLI or Bash example. The validation section explicitly instructs users to create a Windows VM and references the Windows VM creation guide, with no mention of Linux VMs or cross-platform alternatives. This may create friction for Linux/macOS users who prefer Azure CLI or want to validate from a Linux VM.
Recommendations
  • Add Azure CLI (az) examples alongside or in place of PowerShell for creating and managing private endpoints.
  • In the validation section, provide instructions for creating a Linux VM and running the nslookup command from a Linux shell, or clarify that the validation steps are OS-agnostic.
  • When referencing VM creation, link to both Windows and Linux VM creation guides.
  • Where possible, use cross-platform language and tools in examples to ensure parity for Linux/macOS users.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-http-requests-dotnet-get-started-client.md ...id-connections-http-requests-dotnet-get-started-client.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation assumes the use of Visual Studio and .NET Framework, both of which are primarily Windows tools. There are no instructions or examples for creating the application or installing packages using cross-platform tools (e.g., .NET Core/SDK CLI, VS Code, or Linux/macOS environments). All steps and code samples are tailored for a Windows-centric workflow.
Recommendations
  • Provide alternative instructions for creating the project and managing NuGet packages using the .NET CLI (e.g., 'dotnet new console', 'dotnet add package Microsoft.Azure.Relay'), which work on Linux and macOS.
  • Clarify whether the code and package are compatible with .NET Core/.NET 5+ and cross-platform environments, or explicitly state if .NET Framework is required.
  • Mention and provide examples for using cross-platform editors like VS Code.
  • Add a note about running the sample on Linux/macOS, including any prerequisites or limitations.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-http-requests-dotnet-get-started-server.md ...id-connections-http-requests-dotnet-get-started-server.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation assumes the use of Visual Studio and the .NET Framework, both of which are Windows-centric. It provides instructions for creating a console app using Visual Studio and .NET Framework, with no mention of cross-platform alternatives like .NET Core/.NET 5+ or Visual Studio Code. There are no instructions or examples for Linux/macOS users.
Recommendations
  • Add instructions for creating the project using .NET Core or .NET 5+ (which are cross-platform) and Visual Studio Code or the 'dotnet' CLI.
  • Clarify whether the Microsoft.Azure.Relay package and the code sample work on .NET Core/.NET 5+ and, if so, provide equivalent steps for Linux/macOS.
  • If the feature is not Windows-only, provide explicit guidance for non-Windows users, including package installation and running the sample.
  • If the feature is Windows-only, state this clearly at the top of the documentation.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-client.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-client.md
Medium Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes creating a .NET Framework console application in Visual Studio, a Windows-only workflow. There are no instructions or examples for Linux/macOS users (e.g., using .NET Core/.NET 5+ with VS Code or CLI tools). The NuGet package installation steps are also Visual Studio-centric, omitting cross-platform alternatives.
Recommendations
  • Add instructions for creating a .NET Core/.NET 5+ console application using the dotnet CLI, which works on Linux/macOS.
  • Include NuGet package installation steps using the dotnet CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Mention that the sample code works with .NET Core/.NET 5+ and can be run on Linux/macOS, not just Windows.
  • Provide alternative development environment suggestions (e.g., VS Code, JetBrains Rider) for non-Windows users.
GitHub Create Pull Request
Azure Relay Hybrid Connections - HTTP requests in .NET ...ay-hybrid-connections-http-requests-dotnet-get-started.md
Medium Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial assumes use of Visual Studio and .NET on Windows, with all examples and instructions referencing Visual Studio and C# console applications. There is no mention of cross-platform development tools (e.g., VS Code, CLI) or guidance for Linux/macOS users, despite .NET Core/.NET 5+ being cross-platform.
Recommendations
  • Add instructions for creating and running the .NET applications using cross-platform tools like Visual Studio Code or the .NET CLI.
  • Clarify that the tutorial works on Linux/macOS as well as Windows, and provide any necessary platform-specific notes (e.g., how to install .NET SDK, run console apps).
  • Include example commands for building and running the applications on Linux/macOS terminals.
  • Mention alternative editors for non-Windows users.
GitHub Create Pull Request
Azure Relay Authenticate from an application - Azure Relay .../main/articles/azure-relay/authenticate-application.md
Medium Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation primarily demonstrates authentication using .NET console applications, which are most commonly run on Windows. The highlighted code samples and walkthroughs focus exclusively on .NET and do not provide equivalent examples for Linux/macOS environments or other languages/platforms. Additionally, instructions for running the sample application do not mention cross-platform compatibility or alternative steps for Linux/macOS users. The 'Next steps' section lists Azure PowerShell before Azure CLI, subtly prioritizing Windows tooling.
Recommendations
  • Explicitly state whether the .NET sample is cross-platform and provide instructions for running it on Linux/macOS (e.g., using .NET Core/.NET 5+).
  • Add code samples or walkthroughs for Java and JavaScript, as referenced in the 'Samples' section, to demonstrate authentication from non-Windows environments.
  • In the 'Next steps' section, list Azure CLI before Azure PowerShell or clarify that both are available on all platforms.
  • Include troubleshooting notes or environment setup instructions for Linux/macOS users.
  • Where possible, use language-neutral or cross-platform examples in highlighted code sections.
GitHub Create Pull Request
Azure Relay Authenticate with managed identities for Azure Relay resources .../articles/azure-relay/authenticate-managed-identity.md
Medium Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. The primary walkthrough for authenticating with managed identities uses a Windows 10 VM, references RDP for access, and links only to instructions for enabling managed identity on Windows VMs. There are no equivalent Linux VM instructions or examples, and the sample app workflow is tailored to Windows environments. While sample code is cross-platform (.NET, Java, JavaScript), the step-by-step guidance is Windows-centric.
Recommendations
  • Add parallel instructions for enabling managed identity on Linux VMs, linking to the appropriate Azure documentation.
  • Include a Linux-based walkthrough for running the sample application, covering SSH access, file transfer (e.g., SCP), and execution on Linux.
  • Reference both Windows and Linux VM creation guides, or provide a generic VM creation step with OS-specific links.
  • Where RDP is mentioned, also mention SSH for Linux VMs.
  • Clarify that the sample app can run on both Windows and Linux, and provide any OS-specific prerequisites or commands.
GitHub Create Pull Request
← Previous Page 4 of 8 Next →