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 26-48 of 48 flagged pages
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 assumes the use of Visual Studio on Windows and does not mention or provide instructions for Linux/macOS users. There are no examples or guidance for running the .NET applications or setting up the development environment on Linux or macOS, nor are cross-platform editors or .NET Core/SDK usage discussed.
Recommendations
  • Add instructions for installing and using the .NET SDK and CLI on Linux/macOS.
  • Include examples for creating and running the applications using cross-platform tools like VS Code or the dotnet CLI.
  • Clarify that .NET Core/.NET 6+ is cross-platform and provide steps for Linux/macOS users.
  • Mention alternative editors (e.g., VS Code) and terminal usage for non-Windows platforms.
  • Add troubleshooting notes for platform-specific issues (e.g., firewall, permissions).
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-12 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 WCF Relay quick starts and samples alongside cross-platform Hybrid Connections. WCF Relay is described as a legacy but still supported feature, and its examples are Windows-centric. However, Hybrid Connections are presented as cross-platform and open-standard, with examples for .NET, Node.js, and Java, mitigating the overall bias.
Recommendations
  • Clearly indicate platform limitations for WCF Relay and suggest alternatives for Linux/macOS users.
  • Provide explicit guidance for Linux/macOS users on how to use Hybrid Connections, including links to relevant samples and setup instructions.
  • Reorder sections so that cross-platform Hybrid Connections are presented before Windows-specific WCF Relay features.
  • Add a comparison table or section that highlights platform compatibility for each feature.
  • Include more Linux/macOS-specific examples or references where appropriate.
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 06:20
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 and NuGet, both of which are primarily Windows-centric tools. There are no instructions or examples for Linux/macOS users (e.g., using .NET Core/.NET 6+, cross-platform editors, or command-line tools), nor is there mention of alternative workflows for non-Windows environments.
Recommendations
  • Add instructions for creating a .NET (Core/6+) console application using the dotnet CLI, which works on Linux and macOS.
  • Include examples for installing the Microsoft.Azure.Relay NuGet package via the command line (dotnet add package).
  • Mention cross-platform editors such as VS Code, and provide guidance for users not on Windows.
  • Clarify that the sample code works on .NET Core/.NET 6+ and is not limited to .NET Framework/Windows.
  • Consider providing a Linux/macOS-specific section or notes to ensure parity.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE) for development and execution steps, without mentioning or providing guidance for Linux/macOS users (e.g., using VS Code, .NET CLI, or Mono). All examples and instructions assume a Windows environment, and there are no alternative steps or notes for Linux/macOS platforms.
Recommendations
  • Add instructions for setting up and running the .NET applications using cross-platform tools such as VS Code and the .NET CLI.
  • Explicitly mention that .NET Core/.NET 5+ can be used on Linux/macOS and provide steps for installing the .NET SDK on those platforms.
  • Include Linux/macOS-specific guidance for running console applications (e.g., terminal commands).
  • Clarify any platform-specific limitations or differences, if any, in the Azure Relay Hybrid Connections usage.
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 06:20
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 the .NET Framework, both of which are traditionally Windows-centric. All instructions and examples are tailored for Windows users, with no mention of Linux/macOS development environments, alternative IDEs, or cross-platform .NET Core/.NET 6+ usage. There are no Linux-specific instructions or parity examples.
Recommendations
  • Add instructions for creating the console application using cross-platform .NET (e.g., .NET 6/8) via the command line (`dotnet new console`) and mention compatible IDEs like VS Code.
  • Include steps for installing NuGet packages using the `dotnet` CLI (`dotnet add package Microsoft.Azure.Relay`) for Linux/macOS users.
  • Clarify that the sample code works on Linux/macOS with .NET Core/.NET 6+ and provide any necessary caveats or adjustments.
  • Explicitly mention Linux/macOS compatibility and provide troubleshooting tips for those platforms.
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-11 06:20
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 that link to a PowerShell-based guide, with no mention of Linux/macOS CLI alternatives. There are no examples or instructions for using Azure CLI, Bash, or other cross-platform tools to deploy the Resource Manager template. The only explicit deployment path is via PowerShell, which is primarily a Windows tool, and the documentation does not provide parity for Linux/macOS users.
Recommendations
  • Add instructions for deploying the Resource Manager template using Azure CLI (az deployment group create) and Bash, which are cross-platform.
  • Include links to Linux/macOS-specific documentation for template deployment.
  • Present deployment options for both Windows (PowerShell) and Linux/macOS (Azure CLI, Bash) side-by-side, or in a neutral order.
  • Explicitly state that PowerShell is available on Linux/macOS, if relevant, or clarify cross-platform support.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily references .NET console application samples, which are most commonly associated with Windows environments. The step-by-step instructions and highlighted code are exclusively for .NET, with no mention of how to run equivalent samples on Linux or macOS, nor any guidance for non-Windows development environments. While Java and JavaScript samples are linked, the walkthrough and code focus solely on .NET, and there is no explicit parity for Linux users in the main instructional flow.
Recommendations
  • Include explicit instructions and code samples for running the authentication process on Linux and macOS, using Java and JavaScript samples as walkthroughs.
  • Provide guidance on installing .NET Core/SDK on Linux/macOS for cross-platform .NET sample usage.
  • Add a section or note clarifying that the .NET samples can be run on Linux/macOS, and link to relevant setup guides.
  • Present Linux/macOS instructions and examples alongside Windows/.NET ones, rather than only referencing .NET in the main flow.
  • Highlight any platform-specific prerequisites or differences for Linux/macOS users.
GitHub Create Pull Request
Azure Relay Authenticate with managed identities for Azure Relay resources .../articles/azure-relay/authenticate-managed-identity.md
Medium Priority View Details →
Scanned: 2026-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 page demonstrates a Windows bias by exclusively providing instructions and examples for Windows VMs, referencing Windows-specific tools (RDP), and omitting equivalent steps or guidance for Linux VMs. The sample application walkthrough assumes a Windows environment, with no mention of Linux or cross-platform alternatives for running the sample or connecting to the VM.
Recommendations
  • Add parallel instructions for enabling managed identity and running the sample on Linux VMs, including links to Linux-specific documentation.
  • Include guidance for connecting to Linux VMs (e.g., SSH) and copying files.
  • Clarify that the sample applications can be run on Linux and provide any necessary prerequisites or differences.
  • Present examples for both Windows and Linux environments, or explicitly state platform requirements and limitations.
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 06:20
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, which are primarily Windows-centric tools. Instructions for creating the project and managing NuGet packages are given only for Visual Studio, with no mention of cross-platform alternatives like .NET Core/SDK CLI or VS Code. There are no Linux/macOS setup instructions or examples, and the workflow is tailored to Windows users.
Recommendations
  • Add instructions for creating the console application using the .NET CLI (dotnet new console) for cross-platform compatibility.
  • Include guidance for installing NuGet packages via the CLI (dotnet add package Microsoft.Azure.Relay).
  • Clarify whether the code sample works with .NET Core/.NET 5+ and on Linux/macOS, or provide equivalent samples if not.
  • Mention alternative editors (e.g., VS Code) and how to set up the project on non-Windows platforms.
  • Explicitly state platform requirements and limitations, if any.
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 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively references Visual Studio and .NET Framework, which are primarily Windows-centric tools. There are no instructions or examples for creating the application on Linux or macOS (e.g., using .NET Core/SDK CLI, VS Code, or Mono). The NuGet package installation is described via Visual Studio GUI, with no mention of command-line alternatives suitable for Linux/macOS environments.
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 dotnet CLI (dotnet add package Microsoft.Azure.Relay) or NuGet CLI.
  • Mention alternative development environments such as VS Code or JetBrains Rider that are available on Linux/macOS.
  • Clarify that the code is compatible with .NET Core/.NET 5+ and not just .NET Framework.
  • Provide explicit steps or notes for Linux/macOS users regarding prerequisites and environment setup.
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-11 06:20
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 clear Windows bias: all CLI examples use Azure PowerShell, and the only OS-specific VM validation instructions are for Windows. There are no Linux/macOS CLI or VM examples, and the validation steps reference Windows tools and guides exclusively. This creates friction for Linux/macOS users, who must adapt instructions or seek external resources.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all PowerShell examples, as Azure CLI is cross-platform.
  • Include instructions for creating and validating with a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
  • Show DNS validation using Linux/macOS tools (e.g., nslookup, dig) and terminal commands.
  • Reference both Windows and Linux quickstart guides for VM creation.
  • Explicitly state that all steps can be performed on Linux/macOS, and note any differences.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. The .NET Framework client is highlighted as supporting WCF Relay, which is a Windows-specific technology, and no Linux/macOS equivalents or alternatives are mentioned for this feature. The .NET Standard client is 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 platform parity notes. The Node.js section is more neutral, but overall, Windows tools and patterns are referenced first and more prominently.
Recommendations
  • Add explicit Linux/macOS usage instructions and examples for .NET Standard and Node.js clients.
  • Clarify platform compatibility for each client package in the table (e.g., note that .NET Framework/WCF is Windows-only).
  • Provide alternative approaches or guidance for Linux/macOS users who need relay functionality not available outside Windows (e.g., WCF Relay).
  • Include parity notes or links to cross-platform samples for Hybrid Connections.
  • Reorder examples or add platform-neutral sections to avoid Windows-first impression.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is notably Windows-centric, requiring Visual Studio (a Windows-first IDE) and providing instructions only for Windows environments. There are no examples or guidance for Linux/macOS users, such as using cross-platform .NET CLI tools or alternative editors. This creates friction for non-Windows users attempting to follow the tutorial.
Recommendations
  • Add instructions for using .NET CLI (dotnet new, dotnet run) to create and run the applications on Linux/macOS.
  • Mention and provide examples for using cross-platform editors like VS Code.
  • Clarify that the code can run on .NET Core/.NET 5+ on Linux/macOS, not just .NET Framework on Windows.
  • Include screenshots or terminal output from Linux/macOS environments.
  • Explicitly state platform compatibility and any prerequisites for non-Windows systems.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page describes Azure Relay in a cross-platform context, emphasizing the Hybrid Connections feature as multi-platform and standards-based. However, the WCF Relay feature is Windows-centric, relying on Windows Communication Foundation and the full .NET Framework, which are not available on Linux/macOS. WCF Relay examples and quick starts are exclusively for Windows environments. The documentation lists Windows/WCF options first in several places and does not provide equivalent Linux/macOS alternatives for WCF Relay scenarios.
Recommendations
  • Clearly indicate platform limitations for WCF Relay and suggest alternatives for Linux/macOS users.
  • Provide parity in examples and quick starts by including Linux/macOS scenarios wherever possible, especially for Hybrid Connections.
  • Reorder sections or quick starts so that cross-platform options (Hybrid Connections) are presented before Windows-only options (WCF Relay).
  • Add explicit guidance for Linux/macOS users on how to achieve similar functionality using Hybrid Connections or other Azure services.
  • Include a comparison table that highlights platform compatibility for each feature.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-node-get-started-server.md ...es/relay-hybrid-connections-node-get-started-server.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation refers to running npm install from a 'Node command prompt', which is a Windows-specific term, and does not provide any Linux or cross-platform equivalent. There are no explicit Linux instructions or examples, and the only command-line context is Windows-oriented.
Recommendations
  • Replace 'Node command prompt' with a cross-platform term such as 'terminal' or 'command line'.
  • Explicitly state that the instructions work on Windows, Linux, and macOS.
  • Add a note or example showing the npm install command in a Linux or macOS terminal.
  • Ensure that any references to command-line environments are platform-neutral or provide alternatives for each major OS.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on creating a .NET Framework console application using Visual Studio, a Windows-centric IDE, and provides step-by-step instructions tailored for Windows users. There are no examples or guidance for Linux users, such as using .NET Core/SDK on Linux, alternative editors, or cross-platform development workflows.
Recommendations
  • Add instructions for creating a .NET (Core/SDK) console application using the command line (dotnet CLI), which works on Linux, macOS, and Windows.
  • Include examples for installing the NuGet package via the dotnet CLI, not just through Visual Studio.
  • Mention alternative editors (e.g., VS Code) and how to set up the project on Linux.
  • Clarify that the code sample works cross-platform and provide explicit steps for Linux users.
  • Consider providing shell commands and Linux-specific notes where relevant.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-hybrid-connections-dotnet-api-overview.md ...-relay/relay-hybrid-connections-dotnet-api-overview.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation provides only .NET/C# code samples and does not mention or provide examples for Linux environments, cross-platform usage, or alternative tools. There is an implicit Windows-first bias due to the exclusive focus on .NET and lack of guidance for Linux users.
Recommendations
  • Add explicit statements clarifying that the .NET Standard APIs and code samples are cross-platform and can be used on Linux and macOS, not just Windows.
  • Include Linux-specific instructions or examples, such as how to run the code using .NET Core/SDK on Linux, and any platform-specific considerations.
  • Mention and link to any relevant Linux tools or command-line patterns (e.g., using dotnet CLI on Linux) where appropriate.
  • If there are platform-specific authentication or networking considerations (e.g., firewall, proxy), provide guidance for both Windows and Linux.
  • Consider providing sample scripts or Dockerfiles for running the examples in a Linux container environment.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation assumes the use of Visual Studio and the .NET Framework, both of which are traditionally Windows-centric. All instructions for creating the project and managing NuGet packages are given using Visual Studio GUI steps, with no mention of cross-platform alternatives (e.g., .NET Core/SDK CLI, Visual Studio Code, or JetBrains Rider). There are no examples or guidance for Linux or macOS users, nor any mention of how to set up or run the sample outside of a Windows/Visual Studio environment.
Recommendations
  • Add instructions for creating the console application using the .NET CLI (e.g., 'dotnet new console') to support Linux and macOS users.
  • Specify that the code works with .NET Core/.NET 5+ and not just .NET Framework, or clarify any limitations.
  • Provide alternative steps for adding NuGet packages using the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Mention and provide examples for using cross-platform editors like Visual Studio Code.
  • Explicitly state platform requirements and test the instructions on Linux/macOS to ensure parity.
  • If any features are Windows-only, clearly document them and suggest workarounds or alternatives for Linux 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-server.md ...id-connections-http-requests-dotnet-get-started-server.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by instructing users to create a console application specifically in Visual Studio, a Windows-centric IDE, and by referencing .NET Framework, which is primarily supported on Windows. There are no instructions or examples for creating the application on Linux or using cross-platform tools like .NET Core/SDK, nor is there mention of alternative editors or package management approaches suitable for Linux environments.
Recommendations
  • Add instructions for creating the console application using the .NET CLI (e.g., 'dotnet new console') to support Linux and macOS users.
  • Mention and provide examples for using Visual Studio Code or other cross-platform editors.
  • Reference .NET Core or .NET 6+ instead of .NET Framework, as these are cross-platform.
  • Include Linux-specific package installation steps (e.g., using 'dotnet add package') alongside or before Visual Studio steps.
  • Clarify that the code and Azure Relay SDK are cross-platform, and provide explicit instructions for running on Linux.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/move-across-regions.md .../blob/main/articles/azure-relay/move-across-regions.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes moving an Azure Relay namespace using the Azure portal, with terminology and screenshots that are Windows-centric (e.g., ZIP file extraction, file navigation, and UI patterns familiar to Windows users). There are no examples or instructions for performing these steps via cross-platform command-line tools (such as Azure CLI, which runs on Linux, macOS, and Windows), nor is PowerShell mentioned, but the absence of Linux/macOS alternatives or parity is notable. All instructions assume use of the Azure portal, which is platform-agnostic but the workflow and file handling described are more familiar to Windows users.
Recommendations
  • Add equivalent instructions for moving an Azure Relay namespace using Azure CLI commands, which are cross-platform.
  • Include examples of extracting and editing the template.json file using Linux/macOS tools (e.g., unzip, nano, vim).
  • Clarify that the Azure portal can be used from any OS, and provide tips for users on Linux/macOS for file handling and navigation.
  • If possible, provide PowerShell and Bash script examples for automating the move process.
  • Ensure screenshots and terminology are not exclusively Windows-centric (e.g., avoid references to Windows file paths or UI conventions).
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-exceptions.md ...ocs/blob/main/articles/azure-relay/relay-exceptions.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing .NET exception types, APIs, and configuration patterns, which are primarily relevant to Windows environments. There are no examples or guidance for Linux users, alternative SDKs, or cross-platform considerations. No Linux-specific troubleshooting steps, tools, or code samples are provided.
Recommendations
  • Include examples and troubleshooting steps for Linux environments, such as using the Azure CLI or SDKs in Python/Node.js.
  • Mention cross-platform SDKs and provide links or examples for non-.NET languages.
  • Clarify when guidance is specific to .NET/Windows and offer Linux equivalents where possible.
  • Add troubleshooting steps that reference common Linux networking tools (e.g., curl, netstat, iptables) for diagnosing connectivity issues.
  • Provide parity in code samples and configuration advice for both Windows and Linux users.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-hybrid-connections-http-requests-dotnet-get-started.md ...ay-hybrid-connections-http-requests-dotnet-get-started.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation assumes and requires Visual Studio (a Windows-centric IDE) for all examples, without mentioning or providing alternatives for Linux users. There are no instructions or examples for developing or running the .NET applications on Linux (e.g., using VS Code, JetBrains Rider, or the dotnet CLI). The prerequisites and steps are Windows-focused, leading to a lack of parity for Linux developers.
Recommendations
  • Add instructions for setting up the development environment on Linux, such as installing the .NET SDK and using VS Code or the dotnet CLI.
  • Provide Linux-specific steps for creating, building, and running the server and client applications (e.g., using 'dotnet new console', 'dotnet run').
  • Mention cross-platform editors (VS Code, Rider) as alternatives to Visual Studio.
  • Clarify that the .NET code and Azure Relay features are cross-platform, and explicitly state that the tutorial can be followed on Linux and macOS.
  • Include screenshots or terminal output from Linux environments where appropriate.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-http-requests-node-get-started-server.md ...brid-connections-http-requests-node-get-started-server.md
Low Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation instructs users to run 'npm install hyco-https' from a 'Node command prompt', which is a Windows-specific term and may imply Windows as the default environment. No explicit Linux or cross-platform instructions or examples are provided, but the rest of the content is platform-neutral.
Recommendations
  • Replace 'Node command prompt' with 'terminal' or 'command line' to use platform-neutral terminology.
  • Add a note clarifying that the instructions apply to all platforms (Windows, Linux, macOS).
  • Optionally, provide example commands for both Windows and Linux/macOS if there are any platform-specific differences.
GitHub Create Pull Request
← Previous Page 2 of 2 Next →