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 151-175 of 200 flagged pages
Azure Relay Azure Relay API overview | Microsoft Docs ...s/blob/main/articles/azure-relay/relay-api-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page shows a moderate Windows bias, primarily through the emphasis on .NET Framework (which is Windows-only) and Windows Communication Foundation (WCF), with no mention of Linux/macOS equivalents or usage patterns. Windows-specific tools and protocols (WCF, net.tcp) are discussed in detail, while Linux/macOS scenarios are not addressed. Examples and guidance for Linux users (e.g., using .NET Core/.NET Standard on Linux, or Node.js on Linux/macOS) are missing.
Recommendations
  • Add explicit guidance and examples for using .NET Standard library on Linux/macOS, including installation and runtime instructions.
  • Clarify that .NET Framework and WCF are Windows-only, and suggest alternatives for Linux/macOS users.
  • Provide sample commands and code snippets for Linux/macOS environments (e.g., using Node.js modules on Linux, running .NET Standard on Linux).
  • Include a table or section comparing platform compatibility for each client library.
  • Mention any Linux-specific considerations or troubleshooting tips.
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-01-14 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 (Windows-centric) for all steps, and does not mention or provide instructions/examples for Linux/macOS users (e.g., using VS Code, .NET CLI, or alternative editors). All examples and workflow steps are tailored to Windows environments, creating friction for Linux/macOS users.
Recommendations
  • Add instructions for using .NET CLI to create and run the applications on Linux/macOS.
  • Mention and provide examples for using VS Code or other cross-platform editors.
  • Clarify that the .NET code can be run on Linux/macOS and provide any necessary platform-specific notes.
  • Include terminal commands for building and running the applications outside Visual Studio.
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-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows development, specifically using Visual Studio and .NET Framework. All instructions and code samples assume a Windows environment, with no mention of Linux/macOS alternatives (e.g., using .NET Core/.NET 6+, VS Code, or command-line tools). There are no Linux-specific instructions or examples, and the setup steps (project creation, NuGet package management) are Windows-centric.
Recommendations
  • Add instructions for creating a console application using .NET Core/.NET 6+ that works cross-platform (Windows, Linux, macOS).
  • Include examples for using VS Code or command-line tools (dotnet CLI) to create and manage projects and NuGet packages.
  • Explicitly mention that the code sample works on Linux/macOS if using .NET Core/.NET 6+.
  • Provide guidance for installing .NET SDK on Linux/macOS and running the sample.
  • Reorder or parallelize instructions so that Windows and Linux/macOS users are equally supported.
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-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a notable Windows bias. All CLI examples are provided only for Azure PowerShell, with no Bash, Azure CLI, or Linux/macOS shell equivalents. The validation step explicitly instructs users to create a Windows VM, with no mention of Linux VM creation or validation. Windows tools and patterns (PowerShell, Windows VM creation guide) are referenced exclusively and/or before any Linux alternatives, which are entirely absent.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
  • Include instructions for creating and validating with a Linux VM (e.g., Ubuntu), referencing the appropriate Azure quickstart guide.
  • Show validation steps using Bash commands (e.g., nslookup, dig) on Linux/macOS, not just Windows.
  • Explicitly mention that all steps can be performed from Linux/macOS environments using Azure CLI.
  • Where screenshots are shown, consider including Linux terminal or Azure CLI output where relevant.
GitHub Create Pull Request
Azure Relay What is Azure Relay? | Microsoft Docs ...ocs/blob/main/articles/azure-relay/relay-what-is-it.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page for Azure Relay exhibits a moderate Windows bias, primarily through its emphasis on WCF Relay, which is tightly coupled to Windows technologies (.NET Framework, WCF). WCF Relay is described as a legacy but still prominent feature, and all examples for it are inherently Windows-centric. However, the Hybrid Connections feature is presented as cross-platform, with examples for .NET, Node.js, and Java, and explicit mention of multi-platform support. The page does not provide PowerShell-heavy examples or exclusively Windows instructions, but Windows technologies are mentioned first and more prominently in some sections.
Recommendations
  • Add explicit Linux/macOS instructions or examples for Hybrid Connections, such as using Python or Go.
  • Clarify that WCF Relay is Windows-only and suggest alternatives for Linux/macOS users.
  • Reorder sections to present cross-platform Hybrid Connections before Windows-centric WCF Relay.
  • Include a table or summary highlighting platform compatibility for each feature.
  • Provide links to Linux/macOS setup guides or troubleshooting resources.
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-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples for creating private endpoints use Azure PowerShell, with no mention of Azure CLI or Bash alternatives. The validation section instructs users to create a Windows VM and references Windows-specific documentation, omitting Linux VM creation steps and validation commands. There are no Linux/macOS-specific instructions or parity in tooling, making it harder for non-Windows users to follow the guide.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for resource creation and management.
  • Include instructions for creating and validating with a Linux VM, referencing the appropriate Azure Linux VM documentation.
  • Present cross-platform command-line examples (e.g., Azure CLI) before or alongside PowerShell to avoid Windows-first bias.
  • Explicitly state that the steps apply to all supported platforms, and highlight any platform-specific differences.
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-01-13 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. All setup instructions reference Visual Studio GUI actions, with no mention of cross-platform alternatives (e.g., .NET Core/SDK CLI, VS Code, or Linux/macOS development). There are no Linux/macOS-specific instructions or examples for creating the project or installing NuGet packages.
Recommendations
  • Add instructions for creating the console application using the .NET CLI (dotnet new console) for cross-platform compatibility.
  • Include NuGet package installation steps using the CLI (dotnet add package Microsoft.Azure.Relay) instead of only Visual Studio GUI.
  • Clarify that the code works with .NET Core/.NET 5+ and is cross-platform, or specify any Windows-only dependencies.
  • Mention and provide examples for using VS Code or other editors on Linux/macOS.
  • Explicitly state OS requirements and compatibility for the Azure Relay SDK.
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-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily features .NET (C#) console application samples and instructions, which are most commonly associated with Windows environments. The 'Run the sample' section only references .NET code and does not provide explicit instructions or examples for running the sample on Linux or macOS. While Java and JavaScript samples are mentioned in the 'Samples' section, the step-by-step guidance and highlighted code are Windows-centric, and there is no mention of cross-platform setup, dependencies, or troubleshooting for Linux/macOS users.
Recommendations
  • Add explicit instructions for running the .NET sample on Linux and macOS, including prerequisites and troubleshooting tips.
  • Provide equivalent step-by-step examples for Java and JavaScript samples, which are more cross-platform.
  • Clarify any platform-specific requirements or limitations for the Azure Relay SDKs.
  • Include notes or links to documentation on installing .NET Core/SDK on Linux/macOS.
  • Ensure that CLI-based instructions (such as Azure CLI) are presented before or alongside PowerShell, as CLI is cross-platform.
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-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation assumes use of Visual Studio and .NET Framework, both of which are primarily Windows-centric. There are no instructions or examples for creating the application on Linux or macOS (e.g., using .NET Core/SDK CLI or cross-platform editors). The NuGet package installation steps are Visual Studio-specific, omitting CLI alternatives. No mention is made of Linux/macOS compatibility or development workflow.
Recommendations
  • Add instructions for creating the console application using the .NET CLI (e.g., 'dotnet new console') for cross-platform development.
  • Include NuGet package installation steps using the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Clarify whether the code works with .NET Core/.NET 5+ and on Linux/macOS, and provide guidance for those platforms.
  • Mention alternative editors (e.g., VS Code) and workflows for non-Windows environments.
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-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by referencing deployment instructions specifically for PowerShell, a Windows-centric tool, without mentioning Linux/macOS equivalents (such as Azure CLI or Bash). The link to deployment instructions is for PowerShell, and there are no examples or guidance for Linux/macOS users. Windows tools and patterns are implicitly prioritized.
Recommendations
  • Include instructions and examples for deploying the Resource Manager template using Azure CLI and Bash, which are cross-platform and commonly used on Linux/macOS.
  • Provide explicit guidance for Linux/macOS users, such as terminal commands or links to relevant documentation.
  • When referencing deployment methods, list cross-platform options (Azure CLI, portal, PowerShell) together, rather than defaulting to PowerShell.
  • Add a note clarifying that the Azure portal and Resource Manager templates are platform-agnostic, and provide links to platform-specific instructions.
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-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation assumes use of Visual Studio on Windows and does not mention or provide instructions/examples for Linux or macOS environments. All steps reference Visual Studio, with no alternatives (e.g., VS Code, CLI, or cross-platform .NET SDK usage) or guidance for running .NET applications on non-Windows platforms.
Recommendations
  • Add instructions for setting up and running the .NET applications on Linux and macOS, including using .NET CLI and cross-platform editors like VS Code.
  • Include explicit examples for creating, building, and running the applications using the dotnet command-line tools.
  • Clarify that .NET Core/.NET 5+ is cross-platform and provide guidance for installing .NET SDK on Linux/macOS.
  • Mention alternative editors (VS Code, JetBrains Rider) and how to use them for this tutorial.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, terminal usage).
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-01-13 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 main walkthrough for authenticating with managed identities and accessing Azure Relay resources is centered around creating and using a Windows VM, with instructions and links specific to Windows. There are no equivalent Linux VM instructions or examples, and tools like RDP (Windows Remote Desktop) are referenced exclusively. While sample code is cross-platform (.NET, Java, JavaScript), the operational steps and environment setup are Windows-centric.
Recommendations
  • Add parallel instructions for creating and configuring a Linux VM, including enabling managed identity.
  • Provide guidance for connecting to Linux VMs (e.g., SSH) and running the sample applications on Linux.
  • Include Linux-specific examples and screenshots where appropriate.
  • Reference Linux documentation links alongside Windows ones, especially for VM creation and connection.
  • Clarify that the sample applications can run on Linux and provide any necessary prerequisites or troubleshooting tips.
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-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation assumes use of Visual Studio and .NET Framework, both of which are primarily Windows-centric. All instructions and examples reference Windows workflows (Visual Studio, right-clicking project, etc.) and do not mention Linux/macOS equivalents (e.g., using dotnet CLI, VS Code, or Mono). No Linux/macOS-specific guidance or examples are provided.
Recommendations
  • Add instructions for creating a .NET console application using the dotnet CLI, which works cross-platform.
  • Include guidance for installing NuGet packages via the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay') for Linux/macOS users.
  • Mention alternative editors such as VS Code or JetBrains Rider that are available on Linux/macOS.
  • Clarify that the code sample works on .NET Core/.NET 5+ (cross-platform), not just .NET Framework.
  • Provide explicit steps for running the sample on Linux/macOS (terminal commands, prerequisites, etc.).
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-01-13 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 App in Visual Studio, a Windows-centric workflow, and provides no guidance or examples for Linux/macOS users (e.g., .NET Core/SDK CLI, VS Code, or cross-platform development). All instructions and tooling references are Windows-specific, with no mention of Linux-compatible alternatives.
Recommendations
  • Add instructions for creating a cross-platform .NET (Core/6/7/8) console application using the dotnet CLI, which works on Linux and macOS.
  • Include examples for using VS Code or other editors available on Linux/macOS.
  • Clarify that the Microsoft.Azure.Relay NuGet package is compatible with .NET Standard/.NET Core and can be used on Linux/macOS.
  • Provide Linux/macOS-specific setup steps, such as installing the .NET SDK and running the application from the terminal.
  • Reorder or parallelize instructions so that Windows and Linux/macOS workflows are presented equally.
GitHub Create Pull Request
Azure Relay Azure Relay Hybrid Connections - WebSockets in .NET ...e-relay/relay-hybrid-connections-dotnet-get-started.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is notably Windows-centric, with all instructions and examples assuming the use of Visual Studio (a Windows-only IDE) and .NET Framework. There are no references to Linux or macOS development environments, nor are there instructions for running or building the applications outside Windows. This creates friction for Linux/macOS users who may wish to use .NET Core/.NET 6+ and cross-platform editors.
Recommendations
  • Add instructions for using cross-platform .NET (e.g., .NET 6+), including how to create and run the applications with the dotnet CLI.
  • Include examples for setting up the development environment on Linux and macOS (e.g., using VS Code or JetBrains Rider).
  • Clarify which parts of the tutorial are Windows-specific and provide Linux/macOS alternatives where possible.
  • Show how to run the applications from the command line, not just via Visual Studio.
  • Mention any platform-specific caveats or requirements (e.g., installing .NET SDK on Linux/macOS).
GitHub Create Pull Request
Azure Relay What is Azure Relay? | Microsoft Docs ...ocs/blob/main/articles/azure-relay/relay-what-is-it.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias by prominently featuring WCF Relay, which is a Windows/.NET Framework-specific technology, and listing its quick starts and samples alongside more cross-platform Hybrid Connections. WCF Relay is described as a legacy but still supported feature, and its usage is tied to Windows Communication Foundation (WCF), which is not available on Linux/macOS. However, the page also provides parity for Hybrid Connections, with examples for .NET Core, Node.js, and Java, supporting cross-platform scenarios. Windows-specific tools and patterns (WCF) are mentioned first and in detail, but Linux/macOS users can fully utilize Hybrid Connections.
Recommendations
  • Clearly indicate that WCF Relay is Windows/.NET Framework-specific and not supported on Linux/macOS.
  • Present Hybrid Connections as the default or recommended cross-platform solution, listing its quick starts and samples before WCF Relay.
  • Add explicit guidance for Linux/macOS users, including links to platform-specific setup or troubleshooting guides.
  • Consider separating legacy Windows-only features (WCF Relay) into a distinct section to avoid confusion for cross-platform users.
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-01-12 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 using Visual Studio, a Windows-centric IDE, and provides only Windows-oriented instructions (e.g., right-clicking in Visual Studio, using .NET Framework). There are no examples or guidance for Linux users, such as using .NET Core/SDK CLI, cross-platform editors, or Linux-specific setup steps.
Recommendations
  • Add instructions for creating the console application using the .NET CLI (e.g., 'dotnet new console') to support Linux and macOS users.
  • Mention cross-platform IDEs/editors such as VS Code and how to install the NuGet package via CLI ('dotnet add package Microsoft.Azure.Relay').
  • Clarify that the code works with .NET Core/.NET 5+ and is not limited to .NET Framework/Visual Studio.
  • Provide explicit Linux setup steps, including prerequisites and environment notes.
  • Ensure all code and package instructions are platform-neutral or provide alternatives for non-Windows platforms.
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-01-12 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 console application using Visual Studio and .NET Framework, both of which are Windows-centric tools and patterns. There are no instructions or examples for Linux users, such as using .NET Core/SDK CLI, VS Code, or cross-platform NuGet installation. The guidance assumes a Windows development environment and omits Linux equivalents.
Recommendations
  • Add instructions for creating the console application using the .NET CLI (dotnet new console) to support Linux and macOS users.
  • Mention and provide examples for using VS Code or other cross-platform editors, not just Visual Studio.
  • Include steps for installing the NuGet package via the CLI (dotnet add package Microsoft.Azure.Relay) as an alternative to the Visual Studio GUI.
  • Clarify that the code works on .NET Core/.NET 5+ and is cross-platform, or note any platform-specific limitations.
  • Explicitly state platform requirements and provide parity in examples for both Windows and Linux environments.
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-01-12 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-centric IDE, and provides instructions using Windows GUI patterns (right-click, Manage NuGet Packages). There are no examples or guidance for Linux users, such as using .NET Core/SDK CLI tools, cross-platform editors, or alternative package management approaches.
Recommendations
  • Add instructions for creating the console application using the .NET CLI (e.g., 'dotnet new console') to support Linux and macOS users.
  • Include guidance for installing the Relay NuGet package via the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Mention cross-platform editors such as VS Code, and provide steps for users who do not use Visual Studio.
  • Clarify that the code sample works with .NET Core/.NET 5+ and is not limited to .NET Framework.
  • Add explicit notes or sections for Linux/macOS users, including any platform-specific considerations.
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-01-12 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 using Visual Studio, a Windows-centric IDE, and provides step-by-step instructions tailored to Windows workflows. There are no examples or guidance for Linux users, such as using .NET Core/.NET 6+ (cross-platform), alternative editors (VS Code, JetBrains Rider), or command-line approaches for package management and project creation.
Recommendations
  • Add instructions for creating a .NET Core/.NET 6+ console application using the dotnet CLI, which works on Linux, macOS, and Windows.
  • Include examples for installing NuGet packages via the command line (dotnet add package Microsoft.Azure.Relay) instead of only through Visual Studio.
  • Mention and provide steps for using cross-platform editors like Visual Studio Code or JetBrains Rider.
  • Clarify that the code sample works on Linux and macOS as well, and provide any necessary platform-specific notes (e.g., prerequisites for .NET SDK installation).
  • Reorder or parallelize instructions so that Windows and Linux/macOS approaches are presented together, avoiding Windows-first bias.
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-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE) and providing instructions that assume a Windows environment. There are no examples or guidance for Linux users, such as using cross-platform .NET development tools (e.g., VS Code, CLI) or running the applications on Linux. The tutorial does not mention Linux equivalents or provide parity for non-Windows platforms.
Recommendations
  • Include instructions for setting up the development environment on Linux, such as using .NET Core SDK and Visual Studio Code.
  • Provide examples for running the applications using the .NET CLI (dotnet run) instead of only referencing Visual Studio.
  • Clarify that the sample applications can be developed and executed on Linux and macOS, not just Windows.
  • Add troubleshooting or notes for platform-specific differences, if any.
  • Mention alternative editors (e.g., VS Code, JetBrains Rider) that are available cross-platform.
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-01-11 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 console application using Visual Studio and .NET Framework, with instructions and examples tailored to Windows development workflows. There are no references to Linux-compatible development environments (e.g., .NET Core/.NET 6+, VS Code, CLI tools) or alternative package management and project creation methods for Linux users.
Recommendations
  • Add instructions for creating a .NET console application using cross-platform tools such as the 'dotnet' CLI (e.g., 'dotnet new console') that work on Linux, macOS, and Windows.
  • Include guidance for installing the Relay NuGet package via the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay') instead of only using Visual Studio's GUI.
  • Mention and provide examples for using VS Code or other cross-platform editors in addition to Visual Studio.
  • Clarify that the sample code works on .NET Core/.NET 6+ and is not limited to .NET Framework, ensuring Linux users know they can follow along.
  • Explicitly state platform compatibility and provide troubleshooting tips for Linux environments if necessary.
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-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is Windows-centric, instructing users to create a console application specifically in Visual Studio and referencing the .NET Framework, which is primarily a Windows technology. There are no instructions or examples for Linux users, such as using .NET Core/.NET 6+ (cross-platform) or alternative IDEs/editors. Package installation steps are given using Visual Studio's GUI, with no mention of command-line alternatives (e.g., dotnet CLI) that work on Linux/macOS.
Recommendations
  • Add instructions for creating the console application using the dotnet CLI, which works on Linux, macOS, and Windows.
  • Reference .NET Core or .NET 6+ instead of .NET Framework to ensure cross-platform compatibility.
  • Include package installation steps using the command line (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Mention alternative editors (e.g., VS Code) and how to set up the project outside Visual Studio.
  • Clarify that the code sample works on Linux/macOS as well as Windows, and note any platform-specific caveats if applicable.
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-01-11 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 console application using Visual Studio and the .NET Framework, both of which are Windows-centric tools. There are no instructions or examples for Linux users, such as using .NET Core/SDK CLI, cross-platform editors, or Linux-specific setup steps. The NuGet package installation is described only via Visual Studio GUI, which is not available on Linux.
Recommendations
  • Add instructions for creating the console application using the .NET CLI (e.g., 'dotnet new console') for cross-platform compatibility.
  • Include NuGet package installation steps using the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Mention and provide examples for using cross-platform editors such as VS Code.
  • Clarify that the code works on .NET Core/.NET 5+ and is not limited to .NET Framework/Visual Studio.
  • Add explicit notes or sections for Linux/macOS users, including any platform-specific considerations.
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-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a clear Windows bias by exclusively referencing Visual Studio and .NET Framework Console App creation, which are Windows-centric development tools and patterns. There are no examples or instructions for Linux users, such as using .NET Core/SDK on Linux, cross-platform editors, or command-line alternatives for project creation and NuGet package management.
Recommendations
  • Add instructions for creating the console application using .NET Core/SDK CLI (dotnet new console) which works on Linux, macOS, and Windows.
  • Include steps for adding NuGet packages via the dotnet CLI (dotnet add package Microsoft.Azure.Relay) instead of only Visual Studio UI.
  • Mention cross-platform editors (e.g., VS Code) and provide code samples that are not tied to Windows-specific tooling.
  • Explicitly state that the code samples work on Linux and macOS, and provide any platform-specific notes if necessary.
  • Reorder or parallelize instructions so that Windows and Linux approaches are presented together, rather than Windows-first.
GitHub Create Pull Request
← Previous Page 7 of 8 Next →