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 101-125 of 200 flagged pages
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-01 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 client application on Linux or macOS (e.g., using .NET Core/SDK and cross-platform editors like VS Code). The NuGet package installation steps are Visual Studio-specific, and there is no mention of command-line alternatives (e.g., dotnet CLI).
Recommendations
  • Add instructions for creating the console application using the .NET CLI (dotnet new console) to support Linux/macOS users.
  • Mention that the Microsoft.Azure.Relay package can be installed using the dotnet CLI (dotnet add package Microsoft.Azure.Relay).
  • Clarify that the code sample works with .NET Core/.NET 5+ and is not limited to .NET Framework, if applicable.
  • Provide editor-agnostic instructions or mention alternatives like VS Code.
  • If there are Windows-only requirements, explicitly state them at the beginning.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation instructs users to create a .NET Framework console app using Visual Studio and NuGet Package Manager, both of which are Windows-centric tools. There are no instructions or examples for creating or running the server on Linux or macOS, nor is there mention of .NET Core/.NET 5+ (cross-platform) alternatives.
Recommendations
  • Provide parallel instructions for creating a console app using .NET Core or .NET 5+ (which are cross-platform) via the dotnet CLI.
  • Include guidance for installing the Microsoft.Azure.Relay NuGet package using the CLI (e.g., 'dotnet add package') for non-Windows users.
  • Clarify whether the sample code is compatible with .NET Core/.NET 5+ and, if not, note that the instructions are Windows-only.
  • If possible, add a section for Linux/macOS users, or explicitly state if only Windows is supported for this scenario.
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-01 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 command-line automation is only demonstrated using Azure PowerShell. There are no CLI (az cli), Bash, or Linux/macOS-specific examples, and the validation steps explicitly reference creating a Windows VM, with no mention of Linux alternatives. Windows tools and workflows are prioritized or exclusively shown, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI (az cli) examples for creating and managing private endpoints, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • 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 apply equally to Linux VMs.
  • Where possible, use neutral language (e.g., 'create a virtual machine') and provide both Windows and Linux options, or explicitly state that the steps are OS-agnostic unless there is a Windows-specific requirement.
  • If PowerShell is shown, consider also showing Bash/CLI equivalents, or link to relevant cross-platform documentation.
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-02-01 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 (a Windows-centric IDE) and .NET Framework, with no mention of cross-platform .NET (Core/5+) or alternative development environments (e.g., VS Code, CLI). There are no instructions or examples for Linux/macOS users, and all steps reference Visual Studio without alternatives.
Recommendations
  • Add instructions for using cross-platform .NET (e.g., .NET 6/7/8) and clarify if .NET Framework is required or if .NET Core/5+ is supported.
  • Provide guidance for developing and running the sample applications using the .NET CLI (dotnet new, dotnet run), which works on Linux/macOS.
  • Mention and provide examples for using VS Code or other cross-platform editors.
  • Explicitly state OS requirements if the sample is Windows-only, or clarify cross-platform compatibility.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides instructions for configuring IP firewall rules for Azure Relay namespaces, focusing on the Azure portal and Resource Manager templates. However, when referencing deployment of the ARM template, it links only to PowerShell-based deployment instructions, with no mention of Linux/macOS CLI alternatives (such as Azure CLI or Bash). This creates a subtle Windows-first bias and omits Linux/macOS-friendly guidance.
Recommendations
  • Add instructions or links for deploying the ARM template using Azure CLI (az deployment group create) and Bash, which are cross-platform and preferred by many Linux/macOS users.
  • When referencing deployment methods, mention both PowerShell and Azure CLI/Bash options, or provide a table with platform-specific instructions.
  • Ensure that screenshots and UI references are not Windows-specific unless necessary; clarify that the Azure portal 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-client.md ...id-connections-http-requests-dotnet-get-started-client.md
Medium Priority View Details →
Scanned: 2026-01-31 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 instructions for creating a Console App (.NET Framework) project in Visual Studio, with no mention of cross-platform alternatives such as .NET Core/.NET 5+ or Visual Studio Code. There are no instructions or examples for Linux or macOS users, and the workflow is Windows-centric.
Recommendations
  • Add instructions for creating a cross-platform .NET (Core/5/6/7+) console application using the dotnet CLI, which works on Linux, macOS, and Windows.
  • Mention Visual Studio Code as an alternative IDE, and provide guidance for users on Linux/macOS.
  • Clarify whether the Microsoft.Azure.Relay NuGet package and the sample code are compatible with .NET Core/.NET 5+.
  • If possible, provide a sample using the dotnet CLI to add the NuGet package (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Explicitly state if the instructions are Windows-only and link to cross-platform guides if available.
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-31 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation assumes the use of Visual Studio (a Windows-centric IDE) for all development steps and does not mention or provide guidance for Linux/macOS users or alternative tools (e.g., VS Code, .NET CLI). While the .NET code itself is likely cross-platform, the instructions and prerequisites are Windows/Visual Studio focused.
Recommendations
  • Add instructions for using cross-platform tools such as Visual Studio Code or the .NET CLI (dotnet new, dotnet run) for creating and running the sample applications.
  • Clarify that the code samples work on Linux and macOS, and provide any platform-specific notes if needed.
  • Mention that Visual Studio is optional and that other editors/IDEs can be used.
  • If any steps are Windows-specific (e.g., screenshots, file paths), provide Linux/macOS equivalents or clarify differences.
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-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
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 on Linux/macOS (e.g., using .NET Core/SDK and command-line tools like 'dotnet new'), nor any mention of cross-platform editors or workflows.
Recommendations
  • Add instructions for creating the project using the .NET CLI (e.g., 'dotnet new console') for cross-platform compatibility.
  • Clarify whether the Microsoft.Azure.Relay package and code sample work with .NET Core/.NET 5+ on Linux/macOS, and provide guidance if so.
  • Include alternative instructions for installing NuGet packages via the command line (e.g., 'dotnet add package').
  • Mention cross-platform editors like VS Code as alternatives to Visual Studio.
  • If .NET Framework is required and cross-platform is not supported, explicitly state that this sample is Windows-only.
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-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation primarily features .NET (C#) console application samples and highlights PowerShell for role assignment, which are Windows-centric technologies. While Java and JavaScript samples are mentioned, the main walkthrough and code snippets are exclusively .NET/C#, with no explicit Linux/macOS instructions or parity in example ordering. Azure CLI is referenced only in the 'Next steps' section, after PowerShell.
Recommendations
  • Provide step-by-step instructions and code samples for Java and JavaScript applications, not just .NET/C#.
  • Include explicit instructions for running samples on Linux/macOS, such as prerequisites, environment setup, and command-line usage.
  • Present Azure CLI examples before or alongside PowerShell for role assignments, as CLI is cross-platform.
  • Clarify that the .NET sample can be run on Linux/macOS using .NET Core/.NET 5+ if applicable, and provide guidance for doing so.
  • Ensure all sample links are accompanied by brief instructions or notes about platform compatibility.
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-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation primarily guides users through authenticating with managed identities for Azure Relay resources using a Windows VM. All step-by-step instructions, including VM creation, enabling managed identity, copying files, and running the sample, are Windows-specific. There are no equivalent instructions or explicit guidance for Linux or macOS users, despite the cross-platform nature of managed identities and the availability of .NET Core/Java/JavaScript samples that can run on non-Windows platforms.
Recommendations
  • Add parallel instructions for creating and configuring a Linux VM, including enabling managed identity for Linux VMs.
  • Provide examples or notes on how to copy files and run the sample app on Linux (e.g., using SSH/SCP instead of RDP).
  • Clarify that the .NET sample can run on Linux if using .NET Core/5+ and provide relevant build/run instructions.
  • Include sample commands or scripts for Linux/macOS environments where applicable.
  • Reorder or balance the presentation so that Linux/macOS options are not secondary to Windows.
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-31 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 Windows-first approach, instructing users to create a .NET Framework console application in Visual Studio and referencing Windows-specific workflows (e.g., right-clicking in Visual Studio to manage NuGet packages). There are no instructions or examples for Linux/macOS users, such as using .NET Core/.NET 5+ (which is cross-platform), command-line alternatives to Visual Studio, or platform-agnostic project creation and package management.
Recommendations
  • Add instructions for creating a .NET (Core/5+) console application using the 'dotnet' CLI, which works on Linux/macOS as well as Windows.
  • Include steps for installing the Microsoft.Azure.Relay NuGet package via the command line (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Clarify that the sample code works with .NET Core/.NET 5+ and is not limited to .NET Framework, or provide a separate section for cross-platform usage.
  • Mention alternative code editors (e.g., VS Code) and workflows for non-Windows environments.
  • Explicitly state any Windows-only requirements if applicable, or highlight cross-platform compatibility.
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-31 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides instructions for configuring IP firewall rules for Azure Relay namespaces primarily via the Azure portal and Resource Manager templates. However, when referencing deployment of the ARM template, it links specifically to PowerShell-based instructions, with no mention of Linux/macOS CLI alternatives (such as Azure CLI or Bash). This creates a subtle Windows-first bias and omits Linux/macOS-friendly guidance.
Recommendations
  • Add instructions or links for deploying Resource Manager templates using Azure CLI (az deployment group create) and Bash, which are cross-platform and commonly used on Linux/macOS.
  • When referencing deployment methods, mention both PowerShell and Azure CLI options, and order them neutrally or based on platform relevance.
  • Consider including example commands for both PowerShell and Azure CLI to ensure parity for Linux/macOS 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-01-31 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 examples for developing or running the .NET applications on Linux or macOS. All instructions and tooling references are Windows-centric, with no guidance for cross-platform development environments.
Recommendations
  • Add instructions for creating and running the .NET console applications using cross-platform tools such as VS Code, JetBrains Rider, or the .NET CLI.
  • Clarify that .NET Core/.NET 5+ applications can be developed and run on Linux and macOS, and provide example commands for these platforms.
  • Include steps for installing the .NET SDK on Linux/macOS and running the applications from the terminal.
  • Mention alternative editors (e.g., VS Code) and provide parity in screenshots or walkthroughs.
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-31 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 shows a notable Windows bias. The only CLI automation example is in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash example. The validation steps explicitly instruct users to create a Windows VM, with no mention of Linux VMs or alternative OS options. This creates friction for Linux/macOS users and suggests a Windows-centric approach.
Recommendations
  • Add equivalent Azure CLI (az) examples for creating private endpoints and related resources, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • In the validation section, provide instructions for creating and using a Linux VM (e.g., Ubuntu) in addition to the Windows VM example. Show how to run nslookup or dig on Linux.
  • When referencing command-line operations, avoid assuming the user is on Windows. Use neutral language or provide both Windows and Linux/macOS options.
  • If screenshots are needed, consider including at least one from a Linux VM for parity.
  • Explicitly mention that the steps work on both Windows and Linux unless there is a genuine limitation.
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-30 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-only IDE, and does not mention Linux/macOS-compatible alternatives such as .NET Core/.NET 5+ or cross-platform development tools. All instructions and code samples assume a Windows development environment, with no guidance for Linux or macOS users.
Recommendations
  • Add instructions for creating a .NET Core or .NET 5+ console application, which is cross-platform and can run on Windows, Linux, and macOS.
  • Include examples for using cross-platform IDEs or command-line tools (e.g., Visual Studio Code, dotnet CLI) to create and manage the project.
  • Clarify which steps are Windows-specific and provide Linux/macOS alternatives where possible.
  • Explicitly state the platform requirements and recommend cross-platform approaches for broader accessibility.
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-30 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. However, when referencing deployment of the ARM template, it links only to PowerShell-based instructions, which are Windows-centric. There is no mention of Linux/macOS CLI alternatives (such as Azure CLI or Bash), and the deployment guidance implicitly prioritizes Windows/PowerShell tooling.
Recommendations
  • Add explicit instructions or links for deploying ARM templates using Azure CLI (az deployment group create) and Bash, which are cross-platform and widely used on Linux/macOS.
  • When referencing deployment guides, include both PowerShell and Azure CLI options, or link to a page that covers all supported methods.
  • Ensure that examples and instructions do not assume the use of Windows/PowerShell unless the feature is Windows-only.
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-30 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 most commonly run on Windows. The highlighted code samples are in C#, and the main sample referenced is for .NET. While Java and JavaScript samples are mentioned, they are not described or linked in the main walkthrough. The instructions for running the sample do not clarify cross-platform compatibility or provide Linux/macOS-specific guidance. Additionally, in the 'Next steps' section, Azure PowerShell is listed before Azure CLI, which is more commonly used on Linux/macOS.
Recommendations
  • Explicitly state that the .NET sample can be run cross-platform (Windows, Linux, macOS) if applicable, and provide instructions for running on Linux/macOS (e.g., using .NET Core/SDK).
  • Include code snippets or walkthroughs for Java and JavaScript samples, not just .NET.
  • In the 'Next steps' section, list Azure CLI before PowerShell, or clarify parity between tools.
  • Add notes or links to platform-specific setup instructions (e.g., installing .NET SDK on Linux/macOS).
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-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page primarily provides instructions and examples for running the sample application on a Windows VM, including references to RDP and Windows-specific VM images. There are no explicit instructions or examples for running the sample on Linux VMs, nor are there mentions of Linux tools or remote access methods. While the underlying Azure Relay and managed identity features are cross-platform, the guidance is Windows-centric.
Recommendations
  • Add parallel instructions for creating and configuring a Linux VM, including enabling managed identity.
  • Provide guidance on copying and running the sample application on Linux VMs (e.g., using SSH instead of RDP).
  • Clarify whether the .NET sample can be built and run on Linux (using .NET Core/5+/6+), or highlight the Java/JavaScript samples as Linux-friendly alternatives.
  • Include Linux-specific links for connecting to VMs and managing identities.
  • Reorder or balance examples so that Linux and Windows are presented with equal prominence.
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-30 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 given only for Visual Studio GUI, not for CLI or cross-platform workflows.
Recommendations
  • Add instructions for creating a .NET Core or .NET 5+ console application, which is cross-platform and supported on Linux/macOS.
  • Include examples for installing the NuGet package using the dotnet CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Mention alternative development environments such as Visual Studio Code and provide corresponding setup steps.
  • Clarify which steps are Windows-specific and provide parity guidance 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-01-30 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides instructions and examples exclusively for creating a .NET Framework console application using Visual Studio, a Windows-centric IDE. It does not mention or provide guidance for Linux/macOS users, such as using .NET Core/.NET 5+ (cross-platform), alternative IDEs, or command-line approaches. The NuGet package installation steps are tailored to Visual Studio's GUI, omitting CLI instructions suitable for non-Windows environments.
Recommendations
  • Add instructions for creating a .NET Core/.NET 5+ console application, which is cross-platform and supported on Linux/macOS.
  • Include guidance for using Visual Studio Code or command-line tools (dotnet CLI) to create and manage projects.
  • Provide NuGet package installation steps using the dotnet CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Clarify that the code sample works on any OS with .NET Core/.NET 5+ and is not limited to Windows.
  • Consider reordering or parallelizing instructions so that Windows and cross-platform approaches are presented equally.
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-30 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 .NET Framework console application using Visual Studio and relies on Windows-centric tooling and workflows. There are no examples or guidance for Linux/macOS users, such as using .NET Core/.NET 5+ or cross-platform development environments. The instructions for adding NuGet packages and project creation are specific to Visual Studio on Windows.
Recommendations
  • Add instructions for creating a cross-platform .NET (Core/5+) console application using the 'dotnet' CLI, which works on Linux and macOS.
  • Provide alternative steps for adding NuGet packages via the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Clarify whether the Azure Relay SDK and sample code are compatible with .NET Core/.NET 5+ and non-Windows platforms.
  • Include notes or examples for using VS Code or other cross-platform editors.
  • If .NET Framework is required, explicitly state that this is a Windows-only workflow.
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-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for integrating Azure Relay with Azure Private Link Service, primarily using the Azure Portal and Azure PowerShell. The only CLI example is given in PowerShell, with no equivalent Azure CLI (cross-platform) or Bash example. The validation step explicitly instructs users to create a Windows VM and does not mention Linux VM alternatives, nor does it provide Linux/macOS-specific guidance for DNS validation. Overall, the documentation assumes a Windows-centric workflow and omits Linux/macOS parity in examples and validation steps.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for creating resources and private endpoints, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • In the validation section, provide instructions for creating a Linux VM and running equivalent DNS validation commands (e.g., nslookup or dig) on Linux/macOS.
  • Clarify that the steps are applicable regardless of VM OS, and provide OS-agnostic guidance where possible.
  • Where screenshots are shown, note that the Azure Portal experience is the same on all platforms.
  • Explicitly mention that PowerShell examples can be run on Linux/macOS using PowerShell Core, or provide links to documentation for cross-platform PowerShell usage.
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-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation assumes the use of Visual Studio on Windows and provides instructions and examples exclusively for .NET Framework console applications developed and run in Visual Studio. There are no examples or guidance for developing or running the sample applications on Linux or macOS, nor is there mention of cross-platform .NET (Core/5+) or alternative editors/IDEs. This creates friction for Linux/macOS users who may wish to use .NET Core/5+ and cross-platform tools.
Recommendations
  • Clarify whether the sample code works with .NET Core/.NET 5+ and provide instructions for using cross-platform .NET SDKs.
  • Include steps for creating and running the applications using the .NET CLI (dotnet new, dotnet run) on Linux/macOS.
  • Mention alternative editors (e.g., VS Code) and provide guidance for non-Windows environments.
  • Explicitly state any Windows-only requirements (e.g., if the code requires .NET Framework or Visual Studio-specific features).
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-30 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 Windows for .NET development, with all examples and instructions referencing Visual Studio and console applications. There are no instructions or examples for developing or running the sample applications on Linux or macOS, nor mention of cross-platform .NET development tools like VS Code or CLI workflows.
Recommendations
  • Add instructions for creating and running the .NET applications using cross-platform tools such as Visual Studio Code and the .NET CLI.
  • Explicitly mention that .NET Core/.NET 5+ is cross-platform and provide guidance for Linux/macOS users.
  • Include example commands for building and running the applications on Linux/macOS terminals.
  • Clarify any Windows-specific requirements (if any), or state that the tutorial works on Linux/macOS as well.
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-27 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 on Windows and does not mention or provide guidance for developing or running the .NET applications on Linux or macOS. All instructions and examples are tailored to Windows users, with no mention of cross-platform .NET development tools or alternatives.
Recommendations
  • Add instructions for using cross-platform .NET SDK (dotnet CLI) to create, build, and run the sample applications.
  • Mention and provide examples for using VS Code or other cross-platform editors.
  • Clarify that .NET Core/.NET 5+ can run on Linux and macOS, and provide steps for those platforms.
  • Include terminal commands for Linux/macOS users to build and run the applications.
GitHub Create Pull Request
← Previous Page 5 of 8 Next →