Azure Relay

88
Total Pages
67
Linux-Friendly Pages
21
Pages with Bias
23.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

48 issues found
Showing 1-25 of 48 flagged pages
Azure Relay WCF Relay hybrid on-premises/cloud application (.NET) ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows environments. All examples and instructions are tailored for Visual Studio on Windows, using .NET Framework, WCF, and Windows-specific tools and workflows. There are no instructions or examples for Linux or macOS users, nor any mention of cross-platform alternatives. Linux users cannot follow the tutorial as written.
Recommendations
  • Provide instructions for setting up the development environment on Linux and macOS, including supported IDEs (e.g., VS Code, JetBrains Rider) and .NET Core/5+/6+ where possible.
  • Clarify WCF and Azure Relay support on non-Windows platforms, and if not supported, explicitly state this limitation early in the tutorial.
  • If possible, offer alternative approaches for Linux/macOS users (e.g., using REST APIs, gRPC, or other cross-platform communication methods with Azure Relay).
  • Include Linux/macOS command-line equivalents for all steps that use Windows-specific tools or UI (e.g., dotnet CLI for project creation, NuGet package management, and app configuration).
  • Mention and link to any official documentation about cross-platform support or limitations for WCF and Azure Relay.
GitHub Create Pull Request
Azure Relay Tutorial: REST tutorial using Azure Relay ...rticles/azure-relay/service-bus-relay-rest-tutorial.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The tutorial is heavily oriented toward Windows development environments, specifically Visual Studio and WCF/.NET Framework. All examples and instructions assume the use of Visual Studio on Windows, with no mention of Linux/macOS equivalents or cross-platform alternatives. There are no instructions or code samples for running or developing the service on Linux or macOS, nor are any cross-platform .NET Core/.NET 6+ approaches discussed.
Recommendations
  • Add instructions and examples for using .NET Core/.NET 6+ (which is cross-platform) instead of .NET Framework.
  • Include steps for setting up the development environment on Linux and macOS, such as using VS Code or JetBrains Rider.
  • Provide command-line instructions (e.g., dotnet CLI) for project creation, package management, and building/running the service.
  • Clarify which features (such as WCF) are Windows-only and suggest alternatives for Linux/macOS (e.g., ASP.NET Core with Azure Relay Hybrid Connections).
  • Explicitly state platform requirements and limitations at the beginning of the tutorial.
GitHub Create Pull Request
Azure Relay Expose on-premises WCF REST service to clients ...ain/articles/azure-relay/service-bus-relay-tutorial.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows development environments. All examples use Visual Studio (Windows-only), .NET Framework, and C#/.NET-specific tooling. Instructions reference Windows UI elements (e.g., Solution Explorer, context menus), and there are no mentions of Linux or macOS alternatives, nor any guidance for cross-platform development. No examples are provided for using .NET Core/.NET 5+ (which are cross-platform), nor for command-line or editor-agnostic workflows. There is no mention of how to run or configure the service or client on Linux or macOS, nor any troubleshooting or parity notes.
Recommendations
  • Add instructions and examples for using .NET Core/.NET 5+ (cross-platform) instead of or alongside .NET Framework.
  • Provide guidance for setting up and running the service and client on Linux and macOS, including installation steps for .NET SDK and Azure SDK.
  • Include command-line alternatives (e.g., using dotnet CLI) for project creation, package management, and building/running, rather than relying solely on Visual Studio.
  • Mention and demonstrate usage in other editors (e.g., VS Code) that are available on Linux/macOS.
  • Clarify any Windows-specific requirements and offer workarounds or alternatives for non-Windows users.
  • Add troubleshooting notes for common cross-platform issues (e.g., binding, configuration file locations, permissions).
GitHub Create Pull Request
Azure Relay WCF Relay hybrid on-premises/cloud application (.NET) ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
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 macOS alternatives. The tutorial relies on WCF, .NET Framework, and Visual Studio-specific workflows, and does not provide guidance for cross-platform development or command-line alternatives. Linux users are left without clear instructions or supported tooling.
Recommendations
  • Add instructions for setting up the development environment on Linux and macOS, including using Visual Studio Code, JetBrains Rider, or the .NET CLI.
  • Provide examples using .NET Core/5+/6+ (which are cross-platform) instead of .NET Framework where possible.
  • Include command-line alternatives for project creation, building, and running (e.g., using 'dotnet new', 'dotnet build', 'dotnet run').
  • Clarify which steps are Windows-only and offer workarounds or alternatives for Linux/macOS users.
  • Mention and provide guidance for using Azure SDK and Service Bus libraries in cross-platform scenarios.
  • If WCF is required, note its limited cross-platform support and suggest alternatives (such as gRPC or REST APIs) for Linux/macOS users.
GitHub Create Pull Request
Azure Relay Tutorial: REST tutorial using Azure Relay ...rticles/azure-relay/service-bus-relay-rest-tutorial.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The tutorial is heavily oriented toward Windows development environments. All examples use Visual Studio, .NET Framework, and WCF, which are Windows-centric technologies. Steps such as 'Run Visual Studio as administrator', adding references via Visual Studio UI, and using .NET Framework-specific assemblies are tailored for Windows. There are no instructions or examples for Linux or macOS users, nor any mention of cross-platform alternatives like .NET Core/5+/6+, VS Code, or command-line tooling. The documentation assumes the reader is using Windows and Visual Studio, creating friction for non-Windows users.
Recommendations
  • Add instructions for Linux/macOS users, including how to set up the development environment using .NET Core/6+ (which is cross-platform).
  • Provide examples using VS Code or command-line tools (dotnet CLI) for creating, building, and running the project.
  • Clarify which features (such as WCF) are Windows-only and suggest alternatives for Linux/macOS (e.g., ASP.NET Core with Azure Relay for REST services).
  • Include steps for installing prerequisites on Linux/macOS (e.g., .NET SDK, Azure CLI).
  • Explicitly state platform limitations and provide links to cross-platform documentation where available.
GitHub Create Pull Request
Azure Relay Expose on-premises WCF REST service to clients ...ain/articles/azure-relay/service-bus-relay-tutorial.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio and .NET Framework. All examples and instructions assume use of Visual Studio on Windows, with no mention of Linux/macOS alternatives or cross-platform development tools. There are no instructions for running or developing the WCF service or client on Linux or macOS, nor any guidance for using .NET Core/.NET 5+ (which is cross-platform). The tutorial relies on Windows-specific tooling and project types.
Recommendations
  • Add instructions and examples for developing and running the WCF Relay service and client using .NET Core/.NET 5+ on Linux and macOS.
  • Include alternative steps for using cross-platform editors (e.g., VS Code) and command-line tools (dotnet CLI) instead of Visual Studio.
  • Clarify which steps are Windows-specific and provide equivalent steps for Linux/macOS users, such as project creation, NuGet package installation, and configuration.
  • Mention any platform limitations of WCF and Azure Relay, and suggest alternatives if full parity is not possible.
  • Reorder examples so that cross-platform approaches are presented alongside or before Windows-specific 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-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by focusing primarily on .NET (C#) code samples, referencing the Azure portal UI (which is most familiar to Windows users), and providing sample applications only for .NET, Java, and JavaScript, with the highlighted code exclusively in C#. There are no explicit Linux or cross-platform command-line examples (e.g., Bash), and the 'Next steps' section lists PowerShell before Azure CLI, which is more common on Linux. There is no mention of Linux-specific tools, nor are there instructions for running the sample on Linux or macOS.
Recommendations
  • Add explicit instructions and code samples for running the authentication flow on Linux and macOS, including any prerequisites or differences.
  • Provide Bash or cross-platform shell examples for common tasks (e.g., using Azure CLI for authentication and role assignment).
  • Include code samples in additional languages (e.g., Python) that are popular on Linux.
  • When listing tools or commands, mention Azure CLI before or alongside PowerShell, as CLI is more common on Linux.
  • Clarify that the sample applications can be run on Linux (if true), and provide any necessary steps or troubleshooting tips for non-Windows environments.
  • Reference Linux package managers or installation instructions for required SDKs or tools.
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
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation assumes the use of Visual Studio and .NET Framework, both of which are primarily Windows-centric. All instructions for creating the project and managing dependencies are given using Visual Studio GUI steps, with no mention of cross-platform alternatives such as .NET Core/SDK CLI tools or Visual Studio Code. There are no Linux-specific instructions or examples, and the workflow is tailored to Windows development environments.
Recommendations
  • Provide alternative instructions for creating the console application using the .NET CLI (e.g., 'dotnet new console') which works on Linux, macOS, and Windows.
  • Mention and provide examples for using Visual Studio Code or other cross-platform editors.
  • Clarify whether the code and dependencies are compatible with .NET Core/5+/6+ and not just .NET Framework.
  • Include instructions for installing the NuGet package via the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay') in addition to the Visual Studio GUI.
  • Explicitly state cross-platform compatibility and provide any Linux-specific notes if necessary.
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-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates Windows bias by referencing deployment instructions specifically for Azure Resource Manager via a PowerShell link, without mentioning or providing equivalent CLI/Bash/Linux instructions. No Linux-specific tools or examples are provided, and the only automation/deployment path referenced is PowerShell, which is primarily a Windows tool. There are no explicit Linux or cross-platform command-line examples.
Recommendations
  • Add Azure CLI (az) examples for deploying the Resource Manager template, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash shell examples for common tasks, such as using curl or jq to interact with Azure REST APIs.
  • When referencing deployment instructions, provide links for both PowerShell and Azure CLI, and mention them together (e.g., 'To deploy the template, follow the instructions for Azure Resource Manager using PowerShell or Azure CLI').
  • Explicitly state that the instructions apply to all platforms, and clarify any platform-specific steps if necessary.
  • Consider adding a section or callout for Linux/macOS users to ensure parity and inclusivity.
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-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a clear Windows bias. All command-line examples for automating private endpoint creation use Azure PowerShell, with no equivalent Azure CLI, Bash, or Linux shell examples. The validation steps explicitly instruct users to create a Windows virtual machine, with no mention of Linux VMs or cross-platform alternatives. The only command-line validation example uses Windows-centric instructions. There is no guidance for Linux users, and the only automation tooling referenced is PowerShell.
Recommendations
  • Add Azure CLI examples alongside (or before) PowerShell examples for all automation steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • In the validation section, provide instructions for creating both Windows and Linux virtual machines, or use neutral language (e.g., 'Create a virtual machine') with links to both Windows and Linux VM creation guides.
  • Show command-line validation examples (such as nslookup) in both Windows Command Prompt/PowerShell and Linux shell (bash) formats.
  • Mention Linux tools and patterns (such as Bash scripting, Azure CLI, and Linux VM setup) wherever Windows tools are referenced.
  • Ensure screenshots and portal instructions are platform-neutral, or clarify that the Azure portal is accessible from any OS.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-api-overview.md ...s/blob/main/articles/azure-relay/relay-api-overview.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows a Windows bias by listing .NET Framework (Windows-only) and WCF Relay (Windows-specific technology) before cross-platform alternatives. There is no mention of Linux-specific usage, examples, or tools, and the .NET Framework library is described in detail without clarifying its Windows-only nature. No Linux command-line or environment-specific guidance is provided, and examples focus on Windows technologies and patterns.
Recommendations
  • Explicitly mention platform compatibility for each API/library, including which are cross-platform and which are Windows-only.
  • Add Linux-specific usage notes and examples, such as how to use the .NET Standard library on Linux and how to run Node.js modules on Linux.
  • Provide parity in examples and guidance for Linux environments, including installation, configuration, and troubleshooting steps.
  • Avoid listing Windows-only technologies (e.g., WCF Relay) before cross-platform options, or clearly separate them.
  • Include references to Linux tools and patterns where applicable, such as systemd for service management or Linux networking concepts.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-hybrid-connections-dotnet-get-started.md ...e-relay/relay-hybrid-connections-dotnet-get-started.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE) for all development steps, without mentioning cross-platform alternatives or providing Linux-specific instructions. There are no examples or guidance for developing or running the .NET applications on Linux (e.g., using VS Code, JetBrains Rider, or the dotnet CLI). The prerequisites and instructions implicitly assume a Windows environment.
Recommendations
  • Add instructions for setting up the development environment on Linux, including installing the .NET SDK and using editors like VS Code or JetBrains Rider.
  • Provide examples for creating, building, and running the .NET console applications using the dotnet CLI, which is cross-platform.
  • Update the prerequisites section to mention Linux and macOS as supported platforms for .NET development, and provide relevant installation links.
  • Include screenshots or terminal output from Linux environments to demonstrate parity.
  • Clarify that Visual Studio is not required, and that the tutorial can be completed on Linux using alternative tools.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-port-settings.md .../blob/main/articles/azure-relay/relay-port-settings.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page focuses exclusively on Windows Communication Foundation (WCF) bindings and classes, which are Windows-centric technologies. There are no examples or references to Linux-compatible tools, frameworks, or usage patterns. The documentation assumes the use of Windows tools and does not provide guidance for Linux users or alternative cross-platform approaches.
Recommendations
  • Include examples or references for Linux-compatible frameworks (e.g., Java, Python, Node.js) that can interact with Azure Relay.
  • Mention cross-platform alternatives to WCF, such as REST APIs or other supported protocols.
  • Provide guidance on configuring ports and security for Azure Relay on Linux systems, including firewall and network configuration examples.
  • Clarify which features or bindings are Windows-only and suggest alternatives for Linux environments.
  • Add links to cross-platform SDKs or documentation for Azure Relay usage outside of Windows.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All development is performed using Visual Studio (Windows-only), and all examples are based on .NET Framework (not .NET Core/5+/6+), which is primarily supported on Windows. There are no instructions or examples for Linux or cross-platform development environments. The use of Windows-specific tools (Visual Studio, Web Platform Installer) is pervasive, and there are no mentions of alternatives for Linux (e.g., VS Code, JetBrains Rider, or command-line tooling). No PowerShell or CMD scripts are shown, but the entire workflow assumes a Windows environment.
Recommendations
  • Provide equivalent instructions for Linux users, including how to set up the development environment using cross-platform tools like VS Code or JetBrains Rider.
  • Include .NET Core or .NET 6+ examples, which are cross-platform, instead of only .NET Framework.
  • Document how to install the Azure SDK and required dependencies on Linux (using apt, yum, or direct downloads).
  • Add command-line examples for project creation, building, and running (using dotnet CLI), not just Visual Studio UI steps.
  • Mention and provide guidance for running the sample applications on Linux and macOS.
  • Clarify which steps are Windows-specific and provide alternatives where possible.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-what-is-it.md ...ocs/blob/main/articles/azure-relay/relay-what-is-it.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. The WCF Relay feature is described as legacy and is tightly coupled to Windows technologies (WCF, .NET Framework), with all examples and quick starts for WCF Relay focused on Windows-centric tools and frameworks. The Hybrid Connections feature is more cross-platform, with examples for .NET, Node.js, and Java, but the documentation consistently lists .NET/.NET Framework examples first, and there are no explicit Linux or cross-platform command-line examples (e.g., Bash, curl, or Linux service setup). There is no mention of Linux-specific tools, nor are there instructions or examples for Linux environments, especially for the WCF Relay section.
Recommendations
  • Add explicit Linux quick starts and examples, such as using Bash, curl, or Linux-based services for Hybrid Connections.
  • Include instructions for setting up and running Azure Relay clients and listeners on Linux environments.
  • Provide parity in example ordering (e.g., alternate listing Node.js or Java examples first, or group by platform).
  • Clarify which features are Windows-only (WCF Relay) and which are cross-platform, and provide guidance for Linux users on alternatives.
  • Add a table or section comparing Windows and Linux support for each feature, including any limitations or workarounds.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily references .NET console applications and provides C# code samples, which are most commonly associated with Windows environments. The sample application instructions and highlighted code are focused on .NET, with no explicit mention of Linux/macOS compatibility or examples. While Java and JavaScript samples are linked, the walkthrough and code focus on Windows-centric tools and patterns, and there are no Linux-specific instructions or parity checks.
Recommendations
  • Explicitly state that .NET Core/.NET 6+ samples can run cross-platform, including Linux and macOS.
  • Provide step-by-step instructions for running the sample applications on Linux and macOS, including prerequisites and environment setup.
  • Include terminal/bash commands for Linux/macOS users where relevant (e.g., for environment variables, running the sample, installing dependencies).
  • Highlight any platform-specific considerations, such as authentication flows or file paths.
  • Consider providing sample code in Python or other languages popular on Linux, or expand the walkthrough to include Java/JavaScript samples.
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 assumes use of Visual Studio and .NET Framework, both of which are primarily Windows-centric. All instructions for creating the console application and installing NuGet packages are tailored to Visual Studio on Windows, with no mention of cross-platform alternatives such as .NET Core/SDK CLI or Visual Studio Code. There are no Linux/macOS-specific instructions or examples provided.
Recommendations
  • Add instructions for creating the project using the .NET CLI (dotnet new console) for cross-platform compatibility.
  • Include steps for installing NuGet packages via the CLI (dotnet add package Microsoft.Azure.Relay).
  • Mention that the code is compatible with .NET Core/.NET 6+ and can be run on Linux/macOS.
  • Provide alternative editor instructions (e.g., Visual Studio Code) for non-Windows users.
  • Clarify any Windows-specific requirements or limitations, if present.
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 page exclusively describes project creation and package management using Visual Studio and NuGet Package Manager, which are Windows-centric tools. There are no instructions or examples for creating a console application or installing the Relay package on Linux or macOS (e.g., using .NET CLI or VS Code). All code samples are in C#, which is cross-platform, but the workflow assumes a Windows development environment.
Recommendations
  • Add instructions for creating a .NET console application using the .NET CLI (dotnet new console) for Linux/macOS users.
  • Include steps for installing the Microsoft.Azure.Relay NuGet package using the CLI (dotnet add package Microsoft.Azure.Relay).
  • Mention alternative editors such as VS Code or JetBrains Rider that are available on Linux/macOS.
  • Clarify that the code samples work cross-platform and provide explicit guidance for non-Windows environments.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by exclusively providing instructions and examples for Windows VMs, including references to RDP and Windows-specific VM creation guides. There are no equivalent instructions or examples for Linux VMs, nor guidance for Linux/macOS users on running the sample app or connecting to VMs. The sample app is described only in the context of Windows, and Linux alternatives are not mentioned.
Recommendations
  • Add instructions for creating and configuring a Linux VM with managed identities.
  • Provide Linux/macOS-specific steps for copying and running the sample application (e.g., using SSH instead of RDP).
  • Include troubleshooting or notes for running .NET/Java/JavaScript samples on Linux/macOS platforms.
  • Ensure that links and references cover both Windows and Linux VM configuration guides.
  • Present examples for both Windows and Linux environments, or clarify cross-platform compatibility.
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 assumes the use of Visual Studio and .NET Framework, both of which are primarily Windows-centric. All instructions for creating the console application and managing NuGet packages are given in the context of Visual Studio, with no mention of cross-platform alternatives such as .NET Core/.NET 6+, VS Code, or CLI tools. There are no Linux/macOS-specific instructions or examples, which may hinder non-Windows users from following the tutorial.
Recommendations
  • Add instructions for creating a .NET console application using the dotnet CLI (e.g., 'dotnet new console') for cross-platform compatibility.
  • Include steps for installing NuGet packages via the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Clarify that the code sample works on .NET Core/.NET 6+ and is compatible with Linux/macOS, or provide a separate section for non-Windows environments.
  • Mention alternative editors such as VS Code or JetBrains Rider that are available on Linux/macOS.
  • Explicitly state any platform requirements or limitations, if any exist.
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 assumes the use of Visual Studio and .NET Framework, both of which are primarily Windows-centric. It provides instructions and examples tailored to Windows development environments, with no mention of Linux/macOS alternatives (such as .NET Core/SDK, VS Code, or command-line NuGet usage). There are no Linux/macOS-specific instructions or examples, which may create friction for non-Windows users.
Recommendations
  • Add instructions for creating a console application using .NET Core/SDK, which is cross-platform.
  • Include alternative steps for installing the NuGet package via the command line (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Mention and provide examples for using VS Code or other cross-platform editors.
  • Clarify that the code sample works on Linux/macOS and note any platform-specific considerations.
  • Reorder or parallelize instructions so that Windows and Linux/macOS approaches are presented equally.
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-12 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 automating private endpoint creation use Azure PowerShell, with no equivalent Azure CLI or Bash examples provided. The validation step explicitly instructs users to create a Windows VM and references the Windows VM creation guide, omitting instructions for Linux VMs. There are no Linux/macOS-specific examples or guidance, and Windows tooling is presented exclusively and first.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • In the validation section, provide instructions for creating and testing with a Linux VM (e.g., referencing the 'Create a Linux virtual machine in the Azure portal' guide).
  • When mentioning command-line validation (e.g., nslookup), clarify that the command works on both Windows and Linux, and provide Linux shell syntax if different.
  • Where possible, avoid referencing only Windows-specific guides and tools; include links and examples for Linux/macOS users.
  • Consider reordering examples so that cross-platform tools (Azure CLI, Bash) are shown before or alongside Windows-specific tools.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing deployment instructions that link to PowerShell-based guides, with no mention of Linux/macOS CLI alternatives. There is no example or guidance for deploying the Resource Manager template using Azure CLI, Bash, or other cross-platform tools. The only explicit deployment path is via PowerShell, which is Windows-centric. Additionally, the order of presentation and implicit assumptions favor Windows users.
Recommendations
  • Add instructions and examples for deploying the Resource Manager template using Azure CLI (az deployment group create) and Bash scripts.
  • Explicitly mention that the Azure portal and Resource Manager templates can be used from any OS, and provide links to cross-platform deployment guides.
  • Ensure that references to deployment guides include both PowerShell and Azure CLI options, with equal prominence.
  • Consider adding a section or note for macOS/Linux users to clarify supported workflows.
GitHub Create Pull Request
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. The .NET Framework client is highlighted as supporting WCF Relay, which is a Windows-specific technology, and there is no mention of Linux/macOS compatibility or alternatives for WCF Relay. The .NET Standard client is described as cross-platform, but examples and references (such as ASP.NET Core) are Windows-centric. There are no explicit Linux/macOS usage examples, installation instructions, or parity notes. Windows technologies and patterns (WCF, .NET Framework) are mentioned first and in detail, while Linux/macOS scenarios are not addressed.
Recommendations
  • Add explicit notes about platform compatibility for each client library, especially clarifying which features are available on Linux/macOS.
  • Provide Linux/macOS usage examples for .NET Standard and Node.js clients, including installation and runtime instructions.
  • Include parity notes or alternatives for WCF Relay functionality on non-Windows platforms.
  • Reorder sections to present cross-platform options first, or provide parallel examples for Windows and Linux/macOS.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is notably Windows-centric, with all development and execution steps referencing Visual Studio (a Windows-first IDE) and no mention of Linux/macOS alternatives or cross-platform tooling. There are no instructions or examples for running the .NET applications on Linux/macOS, nor guidance for using cross-platform .NET SDKs or editors. This creates friction for non-Windows users attempting to follow the tutorial.
Recommendations
  • Add instructions for installing and using the .NET SDK and CLI on Linux/macOS.
  • Include examples for creating and running the applications using VS Code or command-line tools, which are cross-platform.
  • Explicitly mention that .NET Core/.NET 5+ applications can be developed and run on Linux/macOS, and provide sample commands.
  • Clarify any OS-specific requirements or differences in the tutorial steps.
  • Provide screenshots or terminal output examples for Linux/macOS environments.
GitHub Create Pull Request
← Previous Page 1 of 2 Next →