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 51-75 of 200 flagged pages
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased toward Windows development environments and tooling. All examples and instructions assume the use of Visual Studio on Windows, with no mention of Linux or cross-platform alternatives. The tutorial exclusively uses Windows-specific technologies (WCF, .NET Framework, Visual Studio), and does not provide guidance for Linux users or alternative development environments. There are no Linux or macOS setup steps, nor any command-line or cross-platform tooling options. The use of Windows-specific project templates and instructions further reinforces this bias.
Recommendations
  • Add instructions for setting up the development environment on Linux and macOS, including using Visual Studio Code or JetBrains Rider.
  • Provide .NET Core/.NET 6+ examples that run cross-platform, rather than .NET Framework-only code.
  • Include steps for using command-line tools (dotnet CLI) to create and run projects, in addition to Visual Studio GUI instructions.
  • Mention and demonstrate how to run the sample applications on Linux (e.g., using Ubuntu, Docker containers, or WSL).
  • Clarify which parts of the tutorial are Windows-specific and offer alternatives or workarounds for non-Windows platforms.
  • If WCF Relay is not supported on Linux, explicitly state this and suggest cross-platform alternatives (such as gRPC, REST APIs, or Azure Functions with Hybrid Connections).
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/private-link-service.md ...blob/main/articles/azure-relay/private-link-service.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for automation, referencing the creation of a Windows virtual machine for validation, and omitting equivalent Linux/CLI/Bash examples. The validation steps explicitly direct users to create a Windows VM, and there is no mention of Linux tools or cross-platform alternatives.
Recommendations
  • Add equivalent Azure CLI (az) examples alongside or before PowerShell scripts to ensure Linux and macOS users are supported.
  • Include instructions for creating and validating with a Linux virtual machine, or provide a cross-platform section for both Windows and Linux.
  • Reference both Windows and Linux tools (e.g., Bash, SSH, nslookup on Linux) when suggesting command-line validation steps.
  • Avoid language that assumes the user is on Windows; instead, offer parallel steps for both major operating systems.
  • Where screenshots are shown, consider including those from the Azure CLI or Bash terminal, not just the Azure Portal or Windows environments.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/authenticate-managed-identity.md .../articles/azure-relay/authenticate-managed-identity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 using Windows VM examples, referencing Windows-specific tools (RDP), and omitting Linux VM instructions or parity. All step-by-step guidance assumes a Windows environment, and there are no Linux-specific examples or mentions of Linux tools or workflows.
Recommendations
  • Add parallel instructions for enabling managed identity on Linux VMs, referencing the appropriate Azure documentation.
  • Include examples for connecting to Linux VMs (e.g., SSH) instead of only mentioning RDP for Windows.
  • Provide sample walkthroughs for running the sample applications on Linux VMs, including build and execution steps.
  • Clarify that the process is cross-platform and highlight any differences or additional steps required for Linux environments.
  • Ensure that code samples and links to sample applications include Linux compatibility notes or instructions where relevant.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/authenticate-application.md .../main/articles/azure-relay/authenticate-application.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Dotnet Heavy
Summary
The documentation page primarily focuses on .NET and C# examples, which are most commonly associated with Windows development environments. The main sample provided is a .NET console application, and the instructions and highlighted code are exclusively in C#. There are no explicit Linux or cross-platform command-line instructions, nor are there examples for running the sample on Linux or with non-Windows tools. While there are links to Java and JavaScript samples, the walkthrough and code focus solely on .NET, potentially making it less accessible to Linux-first or cross-platform developers.
Recommendations
  • Include explicit instructions for running the sample applications on Linux (e.g., using .NET Core/SDK on Linux, or Java/Node.js samples).
  • Provide code walkthroughs or highlighted code for at least one non-.NET sample (e.g., Java or JavaScript), demonstrating parity in authentication flows.
  • Add command-line instructions using Azure CLI for all relevant steps (e.g., app registration, role assignment), and clarify that these commands work cross-platform.
  • Mention that the .NET sample can be run on Linux using .NET Core/SDK, and provide any necessary prerequisites or troubleshooting tips for Linux users.
  • Balance the documentation by alternating or paralleling Windows and Linux tool references, rather than focusing on Windows-first patterns.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/ip-firewall-virtual-networks.md ...n/articles/azure-relay/ip-firewall-virtual-networks.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Azure portal and Resource Manager template deployment instructions that link specifically to PowerShell-based guidance, without mentioning or providing equivalent Linux or cross-platform CLI instructions. There are no examples using Azure CLI, Bash, or Linux-native tools, and the deployment workflow assumes familiarity with Windows-centric tooling.
Recommendations
  • Add explicit instructions and examples for deploying Resource Manager templates using Azure CLI (az deployment), which is cross-platform and widely used on Linux.
  • Include Bash shell examples for common tasks, such as querying IP addresses or manipulating JSON templates.
  • Reference both Windows and Linux environments when discussing deployment options, and avoid linking exclusively to PowerShell-based documentation.
  • Where screenshots or UI references are made, clarify that the Azure portal is accessible from any OS/browser, and provide parity for command-line workflows.
  • Consider a dedicated section or callout for Linux users, summarizing equivalent steps and tools.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-hybrid-connections-dotnet-get-started.md ...e-relay/relay-hybrid-connections-dotnet-get-started.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a bias towards Windows by exclusively referencing Visual Studio (a Windows-centric IDE) for development, and does not mention or provide examples for Linux development environments or tools. There are no instructions or examples for running the .NET applications on Linux, nor any mention of cross-platform .NET Core/SDK usage. The tutorial assumes a Windows workflow throughout.
Recommendations
  • Include instructions for setting up and running the .NET applications on Linux using .NET Core/SDK and cross-platform editors like VS Code.
  • Provide Linux-specific commands and examples for building and running the applications (e.g., using the dotnet CLI).
  • Mention alternative development environments, such as JetBrains Rider or VS Code, which are available on Linux.
  • Clarify that .NET Core/.NET 6+ is cross-platform and provide guidance for non-Windows users.
  • Add screenshots or terminal output examples from Linux environments.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows development environments. All examples and instructions assume the use of Visual Studio on Windows, with no mention of Linux or cross-platform alternatives. There are no instructions for using .NET Core/SDK on Linux, nor for using VS Code or command-line tools. The tutorial relies on Windows-specific technologies (WCF, .NET Framework, Visual Studio), and does not offer Linux-compatible guidance or alternatives.
Recommendations
  • Add instructions for setting up the development environment on Linux, including installing the .NET SDK and using VS Code or other editors.
  • Provide examples using .NET Core (or .NET 6/8) and cross-platform WCF alternatives, such as CoreWCF, where possible.
  • Include command-line steps for project creation, building, and running, using dotnet CLI, instead of relying solely on Visual Studio GUI.
  • Clarify which steps are Windows-specific and offer Linux/macOS equivalents where possible (e.g., running as administrator, project templates, NuGet package installation).
  • Mention any limitations or requirements for running WCF/Azure Relay on non-Windows platforms, and link to relevant resources.
  • Consider restructuring the tutorial to present cross-platform options first, or in parallel, rather than assuming Windows as the default.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-what-is-it.md ...ocs/blob/main/articles/azure-relay/relay-what-is-it.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias, primarily through its emphasis on WCF Relay, which is tightly coupled to Windows technologies (WCF, .NET Framework). WCF Relay is described as a legacy but still prominent feature, with all examples and quick starts for it referencing .NET and WCF, which are Windows-centric. There are no Linux-specific examples or guidance for WCF Relay, nor any mention of Linux-compatible tools for this feature. While Hybrid Connections are described as cross-platform and examples are provided for Node.js and Java, the documentation still leads with .NET examples and does not explicitly address Linux usage or parity in setup instructions.
Recommendations
  • Add explicit Linux setup and usage examples for both Hybrid Connections and WCF Relay, if possible.
  • Clarify which features are Windows-only and which are cross-platform at the start of each section.
  • Provide parity in quick start ordering: alternate or lead with cross-platform (Node.js, Java) examples before Windows/.NET ones.
  • Include guidance or links for using Azure Relay from Linux environments, including any required dependencies or limitations.
  • If WCF Relay is not supported on Linux, state this clearly and suggest alternatives for Linux users.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-relay-rest-tutorial.md ...rticles/azure-relay/service-bus-relay-rest-tutorial.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The tutorial is heavily oriented toward Windows development environments. It exclusively uses Visual Studio (a Windows-centric IDE), relies on WCF (Windows Communication Foundation), and provides step-by-step instructions and code samples that assume a Windows/.NET Framework setup. There are no Linux or cross-platform alternatives mentioned, nor are there instructions for using Linux tools, editors, or .NET Core/.NET 6+ (which are cross-platform). The documentation also references Windows-specific DLLs and project types, and omits guidance for running or developing the service on Linux.
Recommendations
  • Add instructions and examples for using .NET Core/.NET 6+ (which are cross-platform) instead of or in addition to .NET Framework.
  • Include steps for setting up the development environment on Linux (e.g., using VS Code, JetBrains Rider, or command-line tools like dotnet CLI).
  • Provide Linux-specific instructions for installing prerequisites, running the service, and managing dependencies (e.g., using dotnet CLI and NuGet on Linux).
  • Mention and demonstrate how to run and test the service on Linux, including file paths, permissions, and launching the executable.
  • Clarify which features (such as WCF) are Windows-only, and suggest cross-platform alternatives (e.g., ASP.NET Core for REST services).
  • Where possible, use cross-platform APIs and libraries, or note any platform limitations.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-hybrid-connections-dotnet-get-started.md ...e-relay/relay-hybrid-connections-dotnet-get-started.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio, and does not provide guidance or examples for Linux users. All instructions assume use of Visual Studio, which is primarily a Windows tool, and there are no mentions of Linux-compatible alternatives or cross-platform development workflows. No Linux-specific instructions, screenshots, or terminal commands are provided.
Recommendations
  • Include instructions for setting up and running the .NET applications on Linux, using tools like Visual Studio Code or the 'dotnet' CLI.
  • Provide Linux-specific prerequisites, such as installation of .NET SDK on Ubuntu or other distributions.
  • Add examples of running the applications from a Linux terminal, including relevant commands.
  • Mention cross-platform development options and clarify that .NET Core/.NET 5+ applications can run on Linux and macOS.
  • Add screenshots or terminal output from Linux environments to illustrate parity.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/authenticate-managed-identity.md .../articles/azure-relay/authenticate-managed-identity.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 using Windows VM examples, referencing Windows-specific tools (RDP), and linking only to instructions for configuring managed identity on Windows VMs. There are no Linux VM examples, nor instructions for Linux VM setup, nor mention of Linux-specific access methods. While code samples are cross-platform (.NET, Java, JavaScript), the operational walkthrough is Windows-centric.
Recommendations
  • Add parallel instructions for enabling managed identity on Linux VMs, linking to relevant documentation.
  • Include examples of connecting to a Linux VM (e.g., using SSH) instead of only RDP for Windows.
  • Provide sample walkthroughs for running the sample applications on Linux VMs, including build and execution steps.
  • Reference both Windows and Linux VM quick-create guides when suggesting VM creation.
  • Ensure that role assignment and managed identity configuration steps are not limited to Windows-specific portals or tools.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-api-overview.md ...s/blob/main/articles/azure-relay/relay-api-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing .NET Framework (Windows-only) APIs and tools before cross-platform or Linux-friendly options, such as Node.js. The .NET Framework/WCF Relay is highlighted, with explanations focused on Windows-specific protocols and environments. There are no explicit Linux or cross-platform usage examples, nor are Linux-specific tools or patterns mentioned.
Recommendations
  • Add explicit Linux usage examples, such as running .NET Standard libraries on Linux (e.g., with .NET Core/6/7) and Node.js on Linux.
  • Include instructions or links for installing and using the Relay client libraries on Linux distributions.
  • Mention cross-platform compatibility and highlight open standards/protocols that work on Linux and macOS, not just Windows.
  • Balance the order of presentation so that cross-platform options (e.g., .NET Standard, Node.js) are listed before or alongside Windows-only options.
  • Provide parity in sample code and walkthroughs for both Windows and Linux environments.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/ip-firewall-virtual-networks.md ...n/articles/azure-relay/ip-firewall-virtual-networks.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Azure portal and Resource Manager template deployment instructions that link to PowerShell-based guides, without mentioning or providing equivalent Linux or cross-platform CLI examples. There are no Linux-specific instructions, nor is Azure CLI (which is cross-platform) referenced for template deployment. The documentation implicitly assumes a Windows environment for management tasks.
Recommendations
  • Add explicit instructions for deploying Resource Manager templates using Azure CLI, which works on Linux, macOS, and Windows.
  • Include examples or links for managing firewall rules via Azure CLI or REST API, not just via portal or PowerShell.
  • Ensure that references to deployment guides include both PowerShell and Azure CLI options, and clarify cross-platform compatibility.
  • Consider adding a note or section highlighting cross-platform management options for Azure Relay firewall configuration.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/authenticate-application.md .../main/articles/azure-relay/authenticate-application.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Dotnet Heavy
Summary
The documentation page demonstrates a bias towards Windows and .NET environments. The only detailed code sample is in C# (.NET), and the primary sample application referenced is a .NET console app. There are no explicit Linux or cross-platform command-line instructions, and no examples are provided for running the sample on Linux or using non-Windows tools. While Java and JavaScript samples are mentioned, they are not highlighted or explained, and the main walkthrough assumes a Windows/.NET development context.
Recommendations
  • Provide explicit instructions and code samples for running the authentication flow on Linux, including using Java and JavaScript sample applications.
  • Include cross-platform command-line instructions (e.g., Azure CLI) for steps like app registration and secret management, not just portal-based steps.
  • Highlight Java and JavaScript samples equally, with code snippets and run instructions for those environments.
  • Clarify that the .NET sample can be run on Linux using .NET Core/6+, and provide any necessary prerequisites or troubleshooting tips for Linux users.
  • Where possible, avoid assuming the use of Visual Studio or other Windows-specific tooling.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-relay-tutorial.md ...ain/articles/azure-relay/service-bus-relay-tutorial.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows environments, with all examples and instructions based on Visual Studio, Windows-specific project types, and .NET Framework. There is no mention of Linux-compatible development environments, cross-platform .NET Core/.NET 5+ options, or alternative tooling. The tutorial assumes use of Windows tools and patterns throughout, and does not provide guidance for Linux users or those using non-Windows platforms.
Recommendations
  • Add instructions and examples for developing and running the WCF Relay service and client using .NET Core/.NET 5+ (which are cross-platform) instead of only .NET Framework.
  • Include guidance for using Visual Studio Code or JetBrains Rider, which are available on Linux and macOS, as alternatives to Visual Studio.
  • Provide command-line instructions for project creation and package management using dotnet CLI (e.g., 'dotnet new', 'dotnet add package'), which work on all platforms.
  • Clarify which steps are Windows-specific, and offer Linux/macOS equivalents where possible (e.g., running as administrator, file paths, etc.).
  • Mention any platform limitations of WCF or Azure Relay, and suggest alternatives for Linux users if full parity is not possible.
  • Add troubleshooting notes for common issues encountered on Linux (e.g., certificate handling, firewall configuration).
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/private-link-service.md ...blob/main/articles/azure-relay/private-link-service.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing only Azure PowerShell examples for CLI-based integration, referencing the creation of a Windows virtual machine for validation, and omitting equivalent Linux/Bash/Azure CLI instructions. The validation section specifically instructs users to create a Windows VM, with no mention of Linux alternatives. No Linux-native tools or commands are referenced, and the only automation example uses PowerShell.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell scripts and automation steps, ensuring parity for Linux and macOS users.
  • In the validation section, provide instructions for creating both Windows and Linux virtual machines, or use neutral language and link to both Windows and Linux VM creation guides.
  • Show how to run the nslookup command on both Windows (cmd/PowerShell) and Linux (bash/terminal), clarifying any differences in output or usage.
  • Reference cross-platform tools and avoid assuming the user is on Windows; where screenshots or UI steps are shown, clarify that the Azure portal is OS-agnostic.
  • Consider including Bash shell snippets or guidance for users who prefer Linux environments, especially for networking and DNS validation steps.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-relay-tutorial.md ...ain/articles/azure-relay/service-bus-relay-tutorial.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented toward Windows development environments. All examples and instructions assume the use of Visual Studio (a Windows-centric IDE), and there is no mention of Linux or cross-platform alternatives. Steps such as 'Run as administrator', project creation, and configuration are described only for Visual Studio. There are no instructions or code samples for Linux users, nor any mention of .NET Core/.NET 5+ cross-platform capabilities or command-line alternatives (e.g., dotnet CLI). The use of Windows-specific tools and terminology (e.g., Solution Explorer, App.config, NuGet via Visual Studio UI) further reinforces the Windows bias.
Recommendations
  • Add equivalent instructions for Linux and macOS environments, including how to use the dotnet CLI to create, build, and run projects.
  • Mention and provide examples using cross-platform editors such as VS Code.
  • Include steps for installing prerequisites (e.g., .NET SDK) on Linux and macOS.
  • Show how to manage NuGet packages via the command line (dotnet add package) instead of only through Visual Studio UI.
  • Clarify that WCF on .NET Core/.NET 5+ is limited (client-only), and suggest alternatives or workarounds for Linux users.
  • Avoid assuming the reader is using Windows or Visual Studio; provide generic instructions where possible.
  • If certain features are Windows-only, explicitly state this and provide guidance for non-Windows users.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased toward Windows development environments. All examples and instructions assume the use of Visual Studio on Windows, with no mention of Linux or cross-platform alternatives. The tutorial relies on .NET Framework (not .NET Core/.NET 5+), WCF, and Windows-specific tooling and patterns. There are no instructions or code samples for Linux users, nor any guidance on using cross-platform tools or editors.
Recommendations
  • Provide equivalent instructions for setting up the development environment on Linux, including using Visual Studio Code or JetBrains Rider, and installing the Azure SDK for .NET on Linux.
  • Include examples using .NET Core or .NET 5+ (which are cross-platform), rather than only .NET Framework.
  • Offer guidance on running and debugging the sample applications on Linux (e.g., using the dotnet CLI, configuring launch.json in VS Code).
  • If WCF is required, clarify its Windows-only limitations and suggest alternatives for Linux (such as gRPC or REST APIs with ASP.NET Core).
  • Mention and provide examples for using Azure CLI (which is cross-platform) instead of only GUI-based steps in Visual Studio.
  • Explicitly state the platform requirements and, if Windows is required, explain why and what Linux/macOS users can do as alternatives.
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
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing the Azure portal UI (which is most commonly used on Windows), mentioning Windows Communication Foundation (WCF) relays (a Windows-centric technology), and omitting any command-line or scripting examples (such as Azure CLI, PowerShell, or Bash) that would be relevant for Linux users. There are no Linux-specific instructions or parity in tooling or workflow.
Recommendations
  • Add Azure CLI examples for exporting, editing, and deploying Resource Manager templates, as Azure CLI is cross-platform and widely used on Linux.
  • Include PowerShell examples as an alternative, but ensure CLI/Bash examples are presented first or alongside PowerShell.
  • Mention that the Azure portal is accessible from any OS, but provide parity for users who prefer or require command-line tools.
  • Clarify that WCF relays are a Windows-specific technology and suggest alternatives or note limitations for Linux users.
  • Provide guidance for editing JSON templates using common Linux text editors (e.g., vim, nano) in addition to generic 'editor of your choice'.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/authenticate-managed-identity.md .../articles/azure-relay/authenticate-managed-identity.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively providing instructions and examples for Windows environments, such as creating and connecting to Windows VMs, referencing RDP, and omitting Linux-based alternatives. There are no Linux VM setup or usage instructions, and the sample walkthrough assumes a Windows workflow throughout.
Recommendations
  • Add parallel instructions for creating and configuring a Linux VM, including enabling managed identity on Linux.
  • Include steps for copying and running the sample application on a Linux VM (e.g., using SSH and .NET Core on Linux).
  • Mention and link to Linux-specific documentation for connecting to Azure VMs (e.g., SSH instead of RDP).
  • Ensure code samples and instructions are platform-agnostic or provide both Windows and Linux variants where applicable.
  • Clarify that the sample applications can be run on both Windows and Linux, and provide any prerequisites or differences for Linux users.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/authenticate-application.md .../main/articles/azure-relay/authenticate-application.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Dotnet Heavy
Summary
The documentation page demonstrates a Windows/.NET-first bias. The only detailed sample provided is a .NET console application, with C# code highlighted and step-by-step instructions tailored to Visual Studio-style workflows. There are no explicit Linux or cross-platform instructions, nor are there terminal/CLI-based examples for Linux users. While Java and JavaScript samples are linked, the walkthrough and code focus exclusively on .NET, which is most commonly associated with Windows environments.
Recommendations
  • Add explicit Linux instructions for running the sample applications, including any prerequisites or environment setup (e.g., .NET Core on Linux, Java, Node.js).
  • Provide equivalent code walkthroughs for the Java and JavaScript samples, not just .NET/C#.
  • Include command-line examples using Azure CLI for authentication and role assignment, with sample commands runnable on Linux/macOS terminals.
  • Clarify that the .NET samples can be run cross-platform (if true), and provide instructions for doing so on Linux/macOS.
  • Balance the highlighted code and instructions so that Linux and non-Windows users are equally supported.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-api-overview.md ...s/blob/main/articles/azure-relay/relay-api-overview.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by prioritizing .NET Framework (a Windows-only technology) and WCF (Windows Communication Foundation) in both the API table and the detailed explanations. There are no explicit Linux or cross-platform command-line examples, nor is there mention of Linux-specific tools or patterns. The .NET Standard library is described as cross-platform, but examples and references (such as ASP.NET Core) are still Microsoft-centric. No Linux-native frameworks or usage patterns are discussed.
Recommendations
  • Add explicit Linux usage examples, such as running .NET Standard clients on Linux distributions.
  • Include command-line examples for both Windows (PowerShell) and Linux (bash) environments.
  • Mention and demonstrate integration with Linux-native frameworks (e.g., Kestrel, systemd) where applicable.
  • Clarify cross-platform compatibility in the API table, highlighting which libraries work natively on Linux.
  • Provide parity in documentation for Linux and macOS users, not just Windows.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-authentication-and-authorization.md .../azure-relay/relay-authentication-and-authorization.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page focuses on .NET and Microsoft-specific tooling (such as WCF and .NET SDKs) for Azure Relay authentication and authorization, with sample code and references primarily targeting Windows-centric technologies. There are no explicit Linux or cross-platform command-line examples (e.g., Bash, curl, or Azure CLI usage), and the sample links are all for .NET, Java, and JavaScript, but not for scripting or tooling commonly used on Linux. There is also a lack of guidance for generating SAS tokens or managing keys using Linux-native tools.
Recommendations
  • Add explicit Linux and cross-platform examples for generating SAS tokens (e.g., using Bash, curl, or OpenSSL).
  • Include Azure CLI commands for managing authorization rules and keys, demonstrating usage on both Windows and Linux shells.
  • Provide sample scripts or code snippets in Python or Bash for authenticating and connecting to Azure Relay from Linux environments.
  • Mention and link to relevant Linux tools or SDKs (such as Azure CLI, Python SDK, or REST API usage) alongside .NET and Windows-specific tools.
  • Ensure that any screenshots or UI instructions clarify that the steps are platform-agnostic or provide alternatives for Linux users where appropriate.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-hybrid-connections-dotnet-get-started.md ...e-relay/relay-hybrid-connections-dotnet-get-started.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE), omitting any mention of Linux-compatible development tools or workflows. All instructions assume the use of Visual Studio, with no guidance for Linux users (e.g., using VS Code, .NET CLI, or Mono). There are no Linux-specific examples or notes on cross-platform compatibility.
Recommendations
  • Include instructions for setting up and running the .NET applications using the .NET CLI (dotnet new, dotnet run), which works on Linux, macOS, and Windows.
  • Mention and provide examples for using cross-platform editors like Visual Studio Code.
  • Add a note clarifying that the sample code is compatible with .NET Core/.NET 5+ and can be run on Linux and macOS, not just Windows.
  • Provide terminal/command-line instructions for Linux and macOS users alongside Visual Studio steps.
  • Explicitly state any Windows-only requirements, or confirm that there are none, to reassure non-Windows users.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/private-link-service.md ...blob/main/articles/azure-relay/private-link-service.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing only Azure PowerShell CLI examples for automation, referencing the creation of a Windows virtual machine for validation, and omitting equivalent Linux/Bash/CLI instructions. The validation steps assume the use of Windows tools and environments, and there are no examples or guidance for Linux users.
Recommendations
  • Provide equivalent Azure CLI (az) and/or Bash shell examples for all PowerShell automation steps, ensuring Linux and cross-platform users are supported.
  • Include instructions for creating and validating with a Linux virtual machine, not just Windows, in the validation section.
  • When referencing command-line tools (e.g., nslookup), clarify that the command works on both Windows and Linux, or provide both Windows and Linux command syntax/examples.
  • Avoid assuming the user is on Windows in validation and management steps; offer parity for Linux/macOS environments.
  • Explicitly mention cross-platform support and tools in the prerequisites and throughout the documentation.
GitHub Create Pull Request
← Previous Page 3 of 8 Next →