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 126-150 of 200 flagged pages
Azure Relay Authenticate from an application - Azure Relay .../main/articles/azure-relay/authenticate-application.md
Medium Priority View Details →
Scanned: 2026-01-27 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 from a .NET console application, with code samples and instructions focused on .NET/C#. The 'Run the sample' section only references running the .NET sample, with no explicit instructions for Linux/macOS users or for running Java/JavaScript samples. The 'Next steps' section lists Azure PowerShell before Azure CLI, which is more cross-platform. There is no mention of Linux/macOS-specific considerations, nor are there examples or guidance for running the sample on those platforms.
Recommendations
  • Add explicit instructions for running the Java and JavaScript samples, including prerequisites and platform-specific notes for Linux/macOS users.
  • Include guidance on installing .NET Core/SDK on Linux/macOS if users wish to run the .NET sample outside Windows.
  • Present Azure CLI instructions before or alongside PowerShell, as CLI is cross-platform.
  • Add a note clarifying that the authentication flow and SDKs are supported on Linux/macOS, and link to relevant platform setup guides.
  • Provide example commands or troubleshooting tips for Linux/macOS environments.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-client.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-client.md
Medium Priority View Details →
Scanned: 2026-01-27 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 or provide instructions for Linux/macOS users (e.g., using .NET Core/.NET 5+ with VS Code or CLI). All steps and examples assume a Windows development environment.
Recommendations
  • Add instructions for creating a .NET Core or .NET 5+ console application using the dotnet CLI, which works cross-platform.
  • Include alternative steps for Linux/macOS users, such as using VS Code or JetBrains Rider instead of Visual Studio.
  • Clarify which steps are Windows-specific and provide equivalent Linux/macOS workflows where possible.
  • Explicitly state if the sample code is compatible with .NET Core/.NET 5+ and how to run it on non-Windows platforms.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing step-by-step instructions for running the sample application on a Windows VM, including references to RDP and Windows-specific VM creation guides. There are no equivalent instructions or examples for running the sample on Linux VMs or other platforms, despite managed identities and Azure Relay supporting cross-platform development. While code samples are in .NET (which is cross-platform), the operational guidance is Windows-centric.
Recommendations
  • Add instructions for deploying and running the sample application on a Linux VM, including SSH access and relevant Linux commands.
  • Provide parity in guidance for enabling managed identity on Linux VMs, linking to Linux-specific Azure documentation.
  • Clarify that the .NET sample can run on Linux and macOS, and provide build/run steps for those platforms.
  • Include examples or references for Java and JavaScript samples, especially for Linux environments.
GitHub Create Pull Request
Azure Relay Configure IP firewall for Azure Relay namespace ...n/articles/azure-relay/ip-firewall-virtual-networks.md
Medium Priority View Details →
Scanned: 2026-01-27 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides instructions for configuring IP firewall rules for Azure Relay namespaces using the Azure portal and Resource Manager templates. While the technical steps are platform-neutral, the only explicit deployment guidance for the template links to a PowerShell-based deployment page, which is typically Windows-first. There are no Linux/macOS CLI or automation examples, and no mention of cross-platform tools like Azure CLI or Bicep.
Recommendations
  • Add instructions or links for deploying Resource Manager templates using Azure CLI (az deployment), which is cross-platform.
  • Include examples or references for using Bicep, which is also platform-neutral.
  • Where possible, provide parity in deployment steps for Linux/macOS users, such as Bash or Azure CLI examples.
  • Clarify that PowerShell is not required and that other deployment methods are available.
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-27 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 Windows environments throughout, with all examples and instructions referencing Visual Studio for creating and running .NET console applications. There is no mention of cross-platform .NET development tools (such as VS Code, CLI, or Linux/macOS compatibility), nor are there instructions or examples for running the sample applications on Linux or macOS. This creates friction for users on non-Windows platforms, even though .NET Core/.NET 5+ is cross-platform.
Recommendations
  • Add instructions for creating and running the .NET applications using the .NET CLI, which works on Windows, Linux, and macOS.
  • Mention and provide examples for using Visual Studio Code or other cross-platform editors.
  • Clarify that the sample code works on .NET Core/.NET 5+ and is not Windows-only.
  • Include notes or steps for Linux/macOS users, such as terminal commands for building and running the applications.
  • Explicitly state any platform-specific requirements 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-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides instructions for creating a .NET Framework console application using Visual Studio, a Windows-centric IDE, and references project types only available on Windows. There are no examples or guidance for Linux/macOS users, such as using .NET Core/.NET 5+ or cross-platform development tools.
Recommendations
  • Add instructions for creating a cross-platform .NET (Core/.NET 5+) console application using the 'dotnet' CLI, which works on Windows, Linux, and macOS.
  • Include alternative steps for installing NuGet packages via CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Clarify that the code sample works with .NET Core/.NET 5+ and provide guidance for using VS Code or other cross-platform editors.
  • Mention that Visual Studio is Windows-only and suggest alternatives for non-Windows 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: 2026-01-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references Visual Studio and .NET Framework, both of which are traditionally Windows-centric tools. There are no instructions or examples for creating the application using cross-platform tools (e.g., .NET Core/.NET 5+, VS Code, CLI) or on Linux/macOS environments. The workflow assumes a Windows development environment and omits Linux/macOS alternatives.
Recommendations
  • Add instructions for creating the project using the .NET CLI (dotnet new console) for .NET Core/.NET 5+.
  • Clarify whether the Microsoft.Azure.Relay package and sample code work on .NET Core/.NET 5+ and on Linux/macOS.
  • Provide examples for installing NuGet packages via CLI (dotnet add package) and for editing code in cross-platform editors like VS Code.
  • Explicitly mention platform compatibility and any limitations for Linux/macOS users.
  • If the sample is Windows-only due to .NET Framework, state this clearly at the top.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for integrating Azure Relay with Azure Private Link Service, but command-line automation is only covered using Azure PowerShell, with no equivalent Azure CLI or Linux/macOS shell examples. The validation step explicitly references creating a Windows VM and does not mention Linux VM options or provide parity in testing instructions. The overall flow and screenshots are portal-based (cross-platform), but scripting and VM validation are Windows-centric.
Recommendations
  • Add Azure CLI examples alongside Azure PowerShell 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 equivalent DNS validation commands (e.g., using nslookup or dig), or clarify that the steps apply equally to Linux/macOS VMs.
  • Where possible, avoid language or examples that imply Windows is the default or only supported platform unless a feature is genuinely Windows-only.
  • Consider including a note that all Azure portal steps are platform-agnostic and can be performed from any OS with a supported browser.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily features .NET (C#) console application samples, which are most commonly run on Windows, and references PowerShell for role assignment management before mentioning Azure CLI. There is a lack of explicit Linux/macOS instructions or examples for running the sample applications, and the highlighted code is Windows-centric. Although Java and JavaScript samples are linked, the walkthrough and code focus on .NET, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit instructions for running the sample applications on Linux/macOS, including prerequisites and environment setup.
  • Provide highlighted code samples for Java and JavaScript, not just .NET/C#.
  • When listing tools for role assignment, mention Azure CLI before or alongside PowerShell, and clarify cross-platform options.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., dependency installation, authentication differences).
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-server.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-server.md
Medium Priority View Details →
Scanned: 2026-01-26 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, which is a Windows-only development environment and runtime. There are no instructions or examples for Linux/macOS users (e.g., .NET Core/.NET 5+ projects, cross-platform editors like VS Code, or CLI-based workflows). This creates friction for non-Windows users who wish to use Azure Relay with .NET.
Recommendations
  • Add instructions for creating a cross-platform .NET (Core/5+) console application using the dotnet CLI.
  • Include examples for using Visual Studio Code or other cross-platform editors.
  • Clarify whether the Microsoft.Azure.Relay NuGet package and sample code work on Linux/macOS, and provide any necessary platform-specific notes.
  • If .NET Framework is required, explicitly state that the instructions are Windows-only and link to cross-platform alternatives if available.
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-26 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 add NuGet packages via the Visual Studio GUI. There are no instructions or examples for Linux/macOS users, such as using .NET Core/.NET 5+ (cross-platform) or command-line tools like dotnet CLI and alternative editors. This creates friction for non-Windows users who may want to follow the tutorial on their platforms.
Recommendations
  • Add instructions for creating a cross-platform .NET (Core/5+) console application using the dotnet CLI.
  • Include examples for installing NuGet packages via the command line (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Mention alternative editors (e.g., VS Code) and workflows for Linux/macOS users.
  • Clarify whether the sample code is compatible with .NET Core/.NET 5+ and, if not, provide equivalent cross-platform samples.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation instructs users to create a .NET Framework console application using Visual Studio, which is a Windows-centric IDE and framework. There are no instructions or examples for creating the equivalent application on Linux or macOS (e.g., using .NET Core/.NET 5+ with VS Code or CLI). The NuGet package installation steps are also tailored to Visual Studio's GUI, omitting cross-platform CLI alternatives.
Recommendations
  • Add instructions for creating a .NET Core or .NET 5+ console application using the 'dotnet new console' CLI command, which works on Linux and macOS.
  • Include NuGet package installation steps using the 'dotnet add package Microsoft.Azure.Relay' CLI command.
  • Mention that the code sample is compatible with .NET Core/.NET 5+ and provide guidance for running it on Linux/macOS.
  • Reference cross-platform editors like VS Code in addition to Visual Studio.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias: the step-by-step instructions for authenticating with managed identities for Azure Relay resources exclusively use a Windows VM as the runtime environment, referencing Windows-specific setup (RDP, Windows VM creation) and omitting Linux VM or cross-platform instructions. While sample code is cross-platform (.NET, Java, JavaScript), the walkthrough for running the sample app is Windows-centric, with no guidance for Linux/macOS users.
Recommendations
  • Add parallel instructions for running the sample app on a Linux VM, including VM creation, enabling managed identity, copying files (e.g., using SCP/SFTP), and running the executable via terminal.
  • Reference both Windows and Linux VM setup guides when discussing enabling managed identity.
  • Include notes or examples for macOS users where relevant, especially for local development.
  • Clarify that the sample code itself is cross-platform and provide explicit instructions for building/running on Linux/macOS.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-http-requests-dotnet-get-started-client.md ...id-connections-http-requests-dotnet-get-started-client.md
Medium Priority View Details →
Scanned: 2026-01-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation instructs users to create a .NET Framework console application using Visual Studio and provides steps that are specific to Windows development environments. There are no examples or guidance for Linux/macOS users, such as using .NET Core/.NET 5+ (which is cross-platform), nor are alternative development environments or package installation methods mentioned.
Recommendations
  • Add instructions for creating a cross-platform .NET Core/.NET 5+ console application, which can run on Linux and macOS as well as Windows.
  • Include command-line instructions for installing the Microsoft.Azure.Relay NuGet package (e.g., using dotnet CLI), which works on all platforms.
  • Mention alternative editors (such as VS Code) and development workflows suitable for Linux/macOS users.
  • Clarify that the code sample is compatible with .NET Core/.NET 5+ if applicable, or provide a separate sample for those frameworks.
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-26 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, focusing primarily on the Azure portal and Azure PowerShell. The only CLI example is for Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash example. The validation step explicitly instructs users to create a Windows VM and references the Windows VM creation guide, with no mention of Linux VM alternatives or parity. This creates friction for Linux/macOS users who may prefer Azure CLI or Bash and Linux-based validation steps.
Recommendations
  • Add equivalent Azure CLI 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) alongside the Windows VM option, and reference the Linux VM creation guide.
  • Show how to run the nslookup command on Linux/macOS, noting any differences if relevant.
  • When listing command-line options, present Azure CLI and PowerShell examples side-by-side, or indicate both options are available.
  • Avoid language or examples that assume Windows as the default unless the feature is Windows-only (which is not the case here).
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-26 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 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 are no CLI or Linux/macOS-specific deployment examples or links, and PowerShell is implicitly prioritized over cross-platform alternatives.
Recommendations
  • Add instructions or links for deploying ARM templates using Azure CLI (az deployment), which is cross-platform and works on Linux/macOS.
  • Explicitly mention that ARM template deployment can be performed from any OS using Azure CLI or REST API, not just PowerShell.
  • Provide example commands for both PowerShell and Azure CLI, or link to documentation for both methods.
  • Ensure that references to deployment tools do not implicitly prioritize Windows/PowerShell unless the feature is Windows-only.
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-26 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 provides instructions and examples only for C# console applications created in Visual Studio. There is no mention of cross-platform .NET development tools (such as VS Code or CLI), nor are there instructions for running the sample on Linux or macOS. This creates friction for developers using .NET Core/.NET 5+ on non-Windows platforms.
Recommendations
  • Add instructions for creating and running the .NET console applications using the .NET CLI, which works on Windows, Linux, and macOS.
  • Mention and provide examples for using Visual Studio Code or other cross-platform editors.
  • Clarify that the sample works with .NET Core/.NET 5+ and is not limited to Windows, if applicable.
  • Include notes or troubleshooting tips for running the sample on Linux/macOS (e.g., terminal commands, environment setup).
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-26 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 guidance for developing or running the .NET applications on Linux or macOS. All instructions and examples are tailored to Windows environments, with no parity for Linux users.
Recommendations
  • Add instructions for creating and running the .NET applications using cross-platform tools such as Visual Studio Code, the .NET CLI, or JetBrains Rider.
  • Include explicit steps for Linux/macOS users, such as installing the .NET SDK, creating projects via the command line, and running applications in a terminal.
  • Clarify that .NET Core/.NET 5+ is cross-platform and provide sample commands for Linux/macOS where applicable.
  • Mention alternative editors and development environments suitable for non-Windows platforms.
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-14 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 application samples, which are most commonly run on Windows, and does not provide explicit Linux/macOS instructions or examples for running the sample application. The highlighted code is C#, and the main sample walkthrough assumes a Windows-centric development environment. While Java and JavaScript samples are linked, the main instructional flow and code snippets focus on .NET, with no mention of Linux-specific steps or cross-platform considerations for running the .NET sample.
Recommendations
  • Add explicit instructions for running the .NET sample on Linux/macOS, including prerequisites (e.g., .NET SDK installation, command-line usage).
  • Include terminal commands for Linux/macOS alongside any Windows-specific instructions.
  • Provide parity in highlighted code samples by showing equivalent Java or JavaScript authentication flows.
  • Clarify that the .NET sample can be run cross-platform and link to documentation for .NET on Linux/macOS.
  • If PowerShell or Windows tools are referenced elsewhere, ensure Azure CLI or bash equivalents are shown and prioritized equally.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page assumes the use of Visual Studio and .NET Framework, both of which are primarily Windows-centric. The instructions for creating the console application and installing the NuGet package are tailored for Visual Studio on Windows, with no mention of cross-platform alternatives (e.g., .NET Core/.NET 6+, VS Code, CLI commands) or Linux/macOS development environments. There are no Linux/macOS-specific instructions or examples.
Recommendations
  • Add instructions for creating a console application using the .NET CLI (e.g., 'dotnet new console') that work on Linux/macOS.
  • Include steps for installing NuGet packages via the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay') instead of only Visual Studio UI.
  • Clarify that the sample code works with .NET Core/.NET 6+ and is cross-platform, or provide separate examples for cross-platform scenarios.
  • Mention and provide guidance for using VS Code or other cross-platform editors.
  • Explicitly state platform requirements and compatibility for the sample code.
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-14 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) for all development steps and does not mention or provide guidance for Linux/macOS users or alternative tooling (e.g., VS Code, CLI). All examples and instructions are tailored to Windows environments, with no mention of cross-platform .NET development or how to run the applications outside Windows.
Recommendations
  • Add instructions for setting up and running the .NET applications using cross-platform tools like VS Code or the .NET CLI.
  • Explicitly mention that .NET Core/.NET 5+ can be used on Linux/macOS and provide steps for those platforms.
  • Include Linux/macOS-specific prerequisites and example commands for building and running the applications.
  • Clarify that Visual Studio is optional and suggest alternatives for non-Windows 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-14 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 notable Windows bias. The main walkthrough for authenticating with managed identities and accessing Azure Relay resources is centered on creating and using a Windows VM, with explicit instructions and links for Windows VM setup and RDP access. There are no equivalent instructions or examples for Linux VMs or macOS environments, and the sample application steps assume a Windows workflow. While sample code is cross-platform (.NET, Java, JavaScript), the operational guidance is Windows-centric.
Recommendations
  • Add parallel instructions for setting up and enabling managed identity on Linux VMs (with links to Linux VM setup and SSH access).
  • Provide examples and walkthroughs for running the sample applications on Linux (including build and execution steps).
  • Mention Linux/macOS tools and access patterns (e.g., SSH instead of RDP) alongside Windows equivalents.
  • Ensure that code samples and operational steps are presented in a way that is platform-agnostic or include platform-specific sections.
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-14 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. Instructions for project creation and NuGet package management are given only for Visual Studio, with no mention of cross-platform alternatives (e.g., .NET Core/.NET 6+, VS Code, or CLI tools). There are no Linux/macOS-specific instructions or examples, and the workflow is presented as if Windows is the default or only environment.
Recommendations
  • Add instructions for creating the console application using cross-platform .NET (e.g., 'dotnet new console') and clarify compatibility with .NET Core/.NET 6+.
  • Include steps for installing the NuGet package via the dotnet CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Mention alternative editors (e.g., VS Code) and workflows for Linux/macOS users.
  • Explicitly state platform requirements and compatibility for the Azure Relay SDK.
  • Provide example commands and screenshots for Linux/macOS environments where relevant.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation assumes the use of Visual Studio and .NET Framework, which are primarily Windows-centric tools. There are no instructions or examples for creating the application on Linux or macOS, nor is there mention of cross-platform alternatives like .NET Core/.NET 6+, VS Code, or CLI-based workflows. This creates friction for non-Windows users.
Recommendations
  • Add instructions for creating the project using the .NET CLI (dotnet new console) for cross-platform compatibility.
  • Mention and provide examples for using VS Code or other editors available on Linux/macOS.
  • Clarify that Microsoft.Azure.Relay supports .NET Standard and can be used on Linux/macOS.
  • Include steps for installing NuGet packages via CLI (dotnet add package) instead of only through Visual Studio GUI.
  • Explicitly state platform requirements and alternatives for non-Windows environments.
GitHub Create Pull Request
Azure Relay Configure IP firewall for Azure Relay namespace ...n/articles/azure-relay/ip-firewall-virtual-networks.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates Windows bias by referencing deployment instructions that are PowerShell-centric and not providing Linux/macOS equivalents. The link to deploy the Resource Manager template directs users to a PowerShell-based guide, with no mention of Azure CLI, Bash, or other cross-platform tools. There are no Linux/macOS-specific examples or instructions, and the documentation implicitly assumes a Windows environment for command-line operations.
Recommendations
  • Add instructions and examples for deploying Resource Manager templates using Azure CLI, which is cross-platform and works on Linux/macOS.
  • Include links to Bash or shell script deployment guides alongside PowerShell instructions.
  • Explicitly mention that the Azure portal and Resource Manager templates can be used from any OS, and provide parity in step-by-step examples.
  • Where command-line examples are given, present Azure CLI first or side-by-side with PowerShell to avoid Windows-first bias.
GitHub Create Pull Request
← Previous Page 6 of 8 Next →