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 1-25 of 200 flagged pages
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-client.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-client.md
High Priority View Details →
Scanned: 2026-02-04 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 clear Windows bias: it instructs users to create a .NET Framework console app in Visual Studio, which is only available on Windows. There are no instructions or examples for Linux/macOS users (e.g., using .NET Core/.NET 5+, cross-platform editors, or command-line tools). The steps and code samples assume a Windows development environment.
Recommendations
  • Add instructions for creating a cross-platform .NET console application (using .NET Core or .NET 5+) that can run on Linux/macOS.
  • Include examples using command-line tools (dotnet CLI) for project creation and NuGet package installation.
  • Mention alternative editors (e.g., VS Code) and how to set up the project outside Visual Studio.
  • Clarify in the introduction if the sample is Windows-only, or update the sample to be cross-platform if possible.
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
High Priority View Details →
Scanned: 2026-02-03 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-only IDE and targets the Windows-only .NET Framework. There are no instructions or examples for Linux/macOS users, such as using .NET Core/.NET 5+ or cross-platform development tools (e.g., VS Code, CLI). 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 or Visual Studio Code.
  • Clarify whether the Microsoft.Azure.Relay NuGet package supports .NET Core/.NET 5+ and provide relevant code samples.
  • If the feature is not Windows-only, include Linux/macOS setup steps and examples.
  • Explicitly state platform requirements and alternatives for non-Windows users.
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-client.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-client.md
High Priority View Details →
Scanned: 2026-02-02 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, which is a Windows-only IDE and targets the Windows-only .NET Framework. 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 examples for installing the NuGet package via CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Clarify whether the Azure Relay client library supports .NET Core/.NET 5+ and provide sample code for those platforms.
  • Mention alternative development environments (e.g., VS Code, JetBrains Rider) that are available on Linux/macOS.
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
High Priority View Details →
Scanned: 2026-02-02 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 app in Visual Studio, which is a Windows-centric workflow. There are no instructions or examples for creating the equivalent application on Linux or macOS (e.g., using .NET Core/.NET 5+ and cross-platform tools like VS Code or CLI). The steps and code are specific to .NET Framework, which is Windows-only, and do not mention alternatives for non-Windows environments.
Recommendations
  • Add instructions for creating a cross-platform .NET (Core/5+) console application using the dotnet CLI.
  • Include guidance for using VS Code or other cross-platform editors.
  • Clarify that the current instructions are for .NET Framework (Windows-only), and provide links or steps for Linux/macOS users to achieve similar functionality with .NET Core/5+.
  • If Azure Relay supports .NET Core/5+, provide sample code and setup steps for those platforms.
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
High Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation instructs users to create a Console App (.NET Framework) project in Visual Studio, which is only available on Windows. All instructions and examples assume the use of Visual Studio and .NET Framework, with no mention of cross-platform alternatives (such as .NET Core/.NET 5+ or Visual Studio Code). There are no Linux/macOS-specific instructions or examples provided.
Recommendations
  • Add instructions for creating a cross-platform .NET project (e.g., .NET Core or .NET 5+) using the 'dotnet' CLI, which works on Linux and macOS.
  • Include examples for using Visual Studio Code or JetBrains Rider, which are available on Linux/macOS.
  • Clarify whether the Microsoft.Azure.Relay SDK and Hybrid Connections are supported on non-Windows platforms, and provide guidance for those environments if so.
  • If .NET Framework is required and the feature is Windows-only, explicitly state this limitation at the beginning of the documentation.
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
High Priority View Details →
Scanned: 2026-01-31 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation 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, such as using .NET Core/.NET 5+ or cross-platform editors like VS Code. The NuGet package installation and project setup steps are tailored to Visual Studio on Windows, omitting CLI-based or cross-platform alternatives.
Recommendations
  • Add instructions for creating a .NET Core or .NET 5+ console application, which is cross-platform.
  • Include examples for using the dotnet CLI to create projects and install NuGet packages.
  • Mention and provide steps for using cross-platform editors like Visual Studio Code.
  • Clarify if the Microsoft.Azure.Relay package and sample code are compatible with Linux/macOS, and provide any necessary platform-specific notes.
Azure Relay Tutorial: REST tutorial using Azure Relay ...rticles/azure-relay/service-bus-relay-rest-tutorial.md
High Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The tutorial is heavily focused on Windows development environments and tools, specifically Visual Studio and the Windows Communication Foundation (WCF) REST programming model. All examples use C#/.NET Framework and Visual Studio, with instructions tailored to Windows workflows (e.g., 'Run as administrator', Solution Explorer, .NET Framework Console App). There are no Linux/macOS equivalents or cross-platform alternatives provided, and the documentation does not mention how to perform these steps on non-Windows systems or using cross-platform .NET (Core/5+).
Recommendations
  • Clarify early in the tutorial that the WCF REST programming model and WCF Relay are Windows-centric and require .NET Framework, which is only supported on Windows.
  • If possible, mention or link to cross-platform alternatives for Azure Relay (such as using .NET Core/.NET 5+ with Azure Relay SDK, or using REST APIs directly).
  • Provide guidance for Linux/macOS users, such as using Visual Studio Code with .NET Core if any part of the workflow is supported, or explicitly state that the tutorial is Windows-only.
  • Add a note in the prerequisites section about platform limitations and recommend alternatives for non-Windows users.
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
High 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 is focused on creating a .NET Framework console application using Visual Studio, which is a Windows-centric development environment and technology. There are no instructions or examples for Linux/macOS users, such as using .NET Core/.NET 5+ or cross-platform editors like VS Code. The NuGet package installation steps are also tailored to Visual Studio, omitting command-line alternatives suitable for Linux/macOS.
Recommendations
  • Add instructions for creating a .NET Core or .NET 5+ console application, which is cross-platform and supported on Linux/macOS.
  • Include examples for using VS Code or command-line tools (dotnet CLI) to create and manage projects and NuGet packages.
  • Clarify whether the Microsoft.Azure.Relay package and sample code are compatible with .NET Core/.NET 5+ and non-Windows platforms.
  • Provide parity in code samples and setup steps for Linux/macOS users.
Azure Relay Tutorial: REST tutorial using Azure Relay ...rticles/azure-relay/service-bus-relay-rest-tutorial.md
High Priority View Details →
Scanned: 2026-01-27 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The tutorial is heavily focused on Windows development tools and patterns, specifically Visual Studio, .NET Framework, and WCF, all of which are traditionally Windows-centric. All examples and instructions assume the use of Visual Studio on Windows, with no mention of Linux/macOS alternatives or cross-platform approaches. There are no instructions or code samples for Linux/macOS users, nor guidance on running the sample outside Windows environments.
Recommendations
  • Clarify early in the tutorial that WCF and .NET Framework are primarily Windows technologies, and note any cross-platform limitations.
  • If possible, provide guidance or references for running similar Azure Relay REST services using .NET Core/.NET 5+ (which are cross-platform) or other languages/frameworks that work on Linux/macOS.
  • Offer alternative instructions for Linux/macOS users, such as using VS Code, the .NET CLI, or Mono where feasible.
  • Explicitly state any Windows-only requirements, and suggest equivalent Linux/macOS workflows if available.
  • Include a note about the lack of Linux/macOS support if the tutorial cannot be completed on those platforms.
Azure Relay Tutorial: REST tutorial using Azure Relay ...rticles/azure-relay/service-bus-relay-rest-tutorial.md
High Priority View Details →
Scanned: 2026-01-26 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The tutorial is heavily focused on Windows development environments and tools, specifically Visual Studio and the .NET Framework (WCF), with all examples and instructions tailored for Windows users. There are no instructions, examples, or notes on how to perform the same tasks on Linux or macOS, nor any mention of cross-platform alternatives. The documentation assumes the use of Visual Studio, Windows-specific DLLs, and Windows-centric development workflows, making it difficult or impossible for Linux/macOS users to follow along.
Recommendations
  • Clearly state in the prerequisites and introduction that this tutorial is Windows-only due to its reliance on WCF and .NET Framework (not .NET Core/.NET 5+).
  • If possible, provide guidance or links for Linux/macOS users on alternative approaches, such as using Azure Relay with .NET Core or other REST frameworks.
  • Add a note explaining that WCF REST services and related tooling are not supported on Linux/macOS, and suggest supported cross-platform technologies where applicable.
  • Consider including a section on how to use Azure Relay with cross-platform frameworks (e.g., ASP.NET Core, Node.js) if the service supports them.
Azure Relay Expose on-premises WCF REST service to clients ...ain/articles/azure-relay/service-bus-relay-tutorial.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily Windows-centric, focusing exclusively on Windows tools (Visual Studio), Windows project types, and .NET Framework. All examples and instructions assume a Windows environment, with no mention of Linux/macOS alternatives, cross-platform .NET Core/.NET 5+, or non-Windows development workflows. There are no instructions for using Linux-compatible editors, SDKs, or command-line tools, nor any guidance for running or hosting WCF services on Linux.
Recommendations
  • Add instructions and examples for using cross-platform .NET (such as .NET 6/7/8) and clarify which parts are Windows-only.
  • Include guidance for Linux/macOS users, such as using VS Code, JetBrains Rider, or command-line tools (dotnet CLI) to create and run projects.
  • Specify whether WCF Relay is supported on non-Windows platforms, and if not, provide alternatives or workarounds.
  • Provide sample commands for installing prerequisites on Linux/macOS (e.g., using apt, yum, brew).
  • Clarify any limitations or requirements for running WCF services and clients on Linux/macOS, and link to relevant cross-platform documentation.
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 tutorial is heavily oriented toward Windows development environments, specifically Visual Studio on Windows. All examples, instructions, and screenshots assume the use of Windows tools and workflows. There is no mention of Linux or macOS alternatives, nor guidance for cross-platform development. The use of WCF and .NET Framework further restricts the tutorial to Windows, as WCF server hosting is not supported on Linux. The instructions for running applications, managing dependencies, and deploying are all Windows-centric.
Recommendations
  • Explicitly state Windows-only requirements at the top of the tutorial.
  • Provide guidance or links for .NET Core/.NET 6+ cross-platform alternatives where possible (e.g., using ASP.NET Core, gRPC, or other relay-compatible frameworks).
  • Offer instructions for Linux/macOS users, such as using Visual Studio Code, JetBrains Rider, or CLI tools (dotnet CLI) for project creation and management.
  • Clarify which steps are not possible on Linux/macOS due to WCF server limitations, and suggest alternative architectures for hybrid scenarios.
  • Include notes or sections for Linux/macOS users, even if only to explain limitations and direct them to relevant resources.
Azure Relay Tutorial: REST tutorial using Azure Relay ...rticles/azure-relay/service-bus-relay-rest-tutorial.md
High 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 tutorial is heavily oriented toward Windows development environments. It exclusively references Visual Studio (Windows-only), assumes use of .NET Framework (not .NET Core/.NET 5+), and relies on WCF, which is not supported on Linux/macOS for REST hosting. All instructions, tooling, and code samples are tailored for Windows, with no mention of Linux/macOS alternatives or cross-platform approaches.
Recommendations
  • Provide instructions and examples for .NET Core/.NET 5+ using cross-platform libraries, such as ASP.NET Core, which can run on Linux/macOS.
  • Include guidance for setting up development environments on Linux/macOS (e.g., using VS Code, JetBrains Rider, or CLI tools).
  • Clarify that WCF REST hosting is not supported on Linux/macOS and suggest alternatives for cross-platform REST services with Azure Relay (such as using ASP.NET Core with Azure Relay Hybrid Connections).
  • Add explicit notes about platform limitations and link to cross-platform Azure Relay tutorials if available.
  • Reorder sections or examples so that cross-platform options are presented first or alongside Windows-specific instructions.
Scanned: 2026-01-13 00:00
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 towards Windows development environments. All examples and instructions assume the use of Visual Studio on Windows, with no mention of Linux or macOS alternatives. The tutorial relies on Windows-specific tooling (Visual Studio, .NET Framework, Web Platform Installer) and does not provide guidance for cross-platform development or usage of .NET Core/SDK on Linux/macOS. There are no Linux/macOS setup instructions, nor are there any examples using cross-platform editors or command-line tools.
Recommendations
  • Add instructions for setting up the development environment on Linux and macOS, including installation of .NET SDK and use of cross-platform editors like VS Code.
  • Provide examples using .NET Core (now .NET 6/7/8), which is cross-platform, rather than .NET Framework.
  • Include command-line steps for project creation, package installation, and running applications using the dotnet CLI.
  • Mention and demonstrate how to use Azure Relay from Linux/macOS environments.
  • Clarify which steps are Windows-only and provide alternatives or workarounds for non-Windows users.
Azure Relay Expose on-premises WCF REST service to clients ...ain/articles/azure-relay/service-bus-relay-tutorial.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio and .NET Framework. All examples and instructions assume use of Visual Studio on Windows, with no mention of Linux or macOS alternatives. There are no instructions or examples for building, running, or configuring the WCF service or client on Linux or macOS, nor any guidance for using cross-platform .NET (Core/6+) or non-Windows IDEs. The use of Windows-specific project templates and NuGet packages is described exclusively.
Recommendations
  • Add instructions for using .NET Core/6+ (which is cross-platform) and clarify which steps work on Linux/macOS.
  • Provide equivalent examples for Linux/macOS users, such as using VS Code or JetBrains Rider, and command-line tools (dotnet CLI) for project creation, package management, and building/running.
  • Clarify whether WCF Relay is supported on non-Windows platforms, and if not, explicitly state this limitation.
  • Include troubleshooting or notes for Linux/macOS users regarding any platform-specific issues.
  • Reorder examples so that cross-platform approaches are presented first or alongside Windows-specific instructions.
Azure Relay Tutorial: REST tutorial using Azure Relay ...rticles/azure-relay/service-bus-relay-rest-tutorial.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The tutorial is heavily oriented toward Windows development environments, specifically Visual Studio and WCF, with all examples and instructions assuming Windows usage. There are no Linux/macOS equivalents or guidance, and no mention of cross-platform .NET Core/.NET 5+ or alternatives to Visual Studio. The use of WCF and related Windows-centric libraries further excludes Linux/macOS users.
Recommendations
  • Add instructions and examples for using .NET Core/.NET 5+ (which is cross-platform) instead of .NET Framework and WCF, or clarify that WCF is Windows-only.
  • Provide guidance for Linux/macOS users, such as using VS Code or JetBrains Rider, and command-line build/run instructions (dotnet CLI).
  • Explicitly state platform limitations at the start of the tutorial if the approach is Windows-only.
  • Offer alternative approaches for building REST services with Azure Relay that work on Linux/macOS (e.g., using ASP.NET Core with Azure Relay SDK).
  • Include steps for installing prerequisites and running the service on Linux/macOS, or link to relevant documentation.
Azure Relay Integrate Azure Relay with Azure Private Link Service ...blob/main/articles/azure-relay/private-link-service.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Windows-based examples and instructions, such as using Azure PowerShell and referencing the creation of a Windows virtual machine for validation. There are no Linux CLI (az CLI), Bash, or Linux VM examples, and Windows tools and patterns are mentioned exclusively or before any Linux equivalents.
Recommendations
  • Add equivalent az CLI (cross-platform) examples for creating private endpoints and managing Azure Relay resources.
  • Include instructions and screenshots for creating and validating with a Linux virtual machine, not just Windows.
  • Provide Bash shell commands for DNS validation, alongside Windows command prompt examples.
  • Mention Linux tools and patterns (e.g., using /etc/hosts, dig, or nslookup on Linux) where appropriate.
  • Ensure parity in step-by-step instructions for both Windows and Linux environments.
Azure Relay Authenticate from an application - Azure Relay .../main/articles/azure-relay/authenticate-application.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Dotnet Heavy
Summary
The documentation page demonstrates a Windows/.NET bias by primarily featuring .NET (C#) sample code and console applications, with instructions and highlighted code only for .NET. There are no Linux-specific instructions, nor are there examples for running the sample on Linux or using Linux-native tools. The main sample is for a Windows-oriented technology stack, and the instructions implicitly assume a Windows environment (e.g., console app, .NET, Azure portal UI). Although Java and JavaScript samples are linked, they are not described or highlighted, and there is no parity in walkthroughs or code snippets for those platforms.
Recommendations
  • Add explicit instructions and code samples for running the authentication flow on Linux, including using Java and JavaScript sample applications.
  • Provide parity in walkthroughs and highlighted code for Java and JavaScript samples, not just .NET.
  • Include guidance for using cross-platform tools (e.g., Azure CLI) for steps like app registration and secret creation, rather than relying solely on Azure portal UI.
  • Clarify that the sample applications can be run on Linux and provide any necessary setup steps (e.g., installing .NET Core on Linux, running Java/Node.js samples).
  • Consider including troubleshooting notes or platform-specific caveats for Linux users.
Azure Relay Authenticate with managed identities for Azure Relay resources .../articles/azure-relay/authenticate-managed-identity.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and examples for Windows-based Azure VMs, including references to RDP and Windows-specific VM creation guides. There are no equivalent Linux VM instructions, nor is there guidance for running the sample app on Linux. The sample walkthrough assumes a Windows environment throughout, and Windows tools (RDP) are mentioned without Linux alternatives.
Recommendations
  • Add explicit instructions for enabling managed identity on Linux VMs, including links to relevant documentation.
  • Provide a walkthrough for running the sample application on a Linux VM, including build and execution steps.
  • Mention Linux-compatible remote access tools (e.g., SSH) alongside RDP, and provide links to Linux VM connection guides.
  • Ensure that code samples and instructions are platform-agnostic or include both Windows and Linux variants where applicable.
Azure Relay Configure IP firewall for Azure Relay namespace ...n/articles/azure-relay/ip-firewall-virtual-networks.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates Windows bias by referencing Azure portal (which is most commonly used on Windows), and by directing users to deploy Resource Manager templates using a PowerShell-specific guide, without mentioning or providing examples for Linux-native tools or CLI workflows. There are no Linux or cross-platform command-line examples (such as Azure CLI or Bash), and no mention of Linux-specific deployment instructions.
Recommendations
  • Add instructions and examples for deploying Resource Manager templates using Azure CLI (az deployment group create) and Bash scripts, which are cross-platform and widely used on Linux.
  • Reference both PowerShell and Azure CLI deployment guides, and present them side-by-side or in a neutral order.
  • Explicitly mention that the Azure portal is accessible from any OS/browser, and clarify any OS-specific steps if relevant.
  • Include Linux-specific notes or troubleshooting tips where appropriate.
  • Ensure that any referenced guides (such as 'deploy-powershell.md') have equivalent Linux/CLI versions and link to them.
Azure Relay Azure Relay API overview | Microsoft Docs ...s/blob/main/articles/azure-relay/relay-api-overview.md
High Priority View Details →
Scanned: 2026-01-12 00:00
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 alternatives. It references Windows Communication Foundation (WCF) and proprietary protocols without mentioning Linux equivalents or alternatives. There are no explicit Linux or cross-platform usage examples, and the focus is on Windows-centric technologies and patterns.
Recommendations
  • Add explicit Linux usage examples for Azure Relay, such as command-line usage or integration with Linux services.
  • Highlight cross-platform capabilities and provide parity in examples for both Windows and Linux environments.
  • Include references to Linux-compatible tools and frameworks (e.g., .NET Core on Linux, Node.js on Linux) and demonstrate their usage.
  • Avoid prioritizing Windows-only technologies (like WCF) in documentation structure; present cross-platform options first or equally.
  • Clarify which APIs and libraries are supported on Linux and provide guidance for Linux users.
Azure Relay Azure Relay Hybrid Connections - WebSockets in .NET ...e-relay/relay-hybrid-connections-dotnet-get-started.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented towards Windows development environments, specifically Visual Studio, with no mention of Linux-compatible development tools or instructions. All examples assume use of Visual Studio and do not provide guidance for Linux users or alternative IDEs. There are no instructions for running or building the applications on Linux, nor any mention of .NET Core/.NET 6+ cross-platform capabilities.
Recommendations
  • Add instructions for setting up and running the sample applications on Linux, including using .NET Core/.NET 6+ and the 'dotnet' CLI.
  • Include examples for building and running the applications using VS Code or other cross-platform editors.
  • Explicitly mention that .NET is cross-platform and provide parity in steps for Linux and macOS users.
  • Provide troubleshooting notes or prerequisites for Linux (e.g., installing .NET SDK, using terminal commands).
  • Avoid assuming Visual Studio as the only development environment; offer alternatives.
Azure Relay What is Azure Relay? | Microsoft Docs ...ocs/blob/main/articles/azure-relay/relay-what-is-it.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. It prominently features Windows-centric technologies such as WCF Relay (which is tightly coupled with the full .NET Framework and Windows Communication Foundation), and all WCF Relay examples are inherently Windows-only. The quick start and sample sections list .NET (typically Windows-first) examples before Node and Java, and do not mention Linux-specific instructions, tools, or patterns. There is no explicit mention of Linux/Powershell alternatives, nor are Linux command-line or service management examples provided.
Recommendations
  • Add explicit Linux quick start guides for Hybrid Connections, including setup and usage instructions for common Linux distributions.
  • Clarify which features and samples are cross-platform and which are Windows-only (e.g., WCF Relay).
  • Provide Linux-specific examples for running relay clients/services, including service management and firewall configuration.
  • Include parity in sample ordering, listing cross-platform and Linux/Node/Java examples before or alongside .NET/Windows examples.
  • Mention alternative tools or libraries for Linux environments where Windows-specific technologies (like WCF) are referenced.
Azure Relay Tutorial: REST tutorial using Azure Relay ...rticles/azure-relay/service-bus-relay-rest-tutorial.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The tutorial exhibits significant Windows bias: all examples use Visual Studio and .NET Framework (Windows-centric tools), instructions reference Windows-specific UI actions (e.g., 'Run as administrator', Solution Explorer), and there are no Linux or cross-platform alternatives provided. The use of WCF and .NET Framework further restricts the tutorial to Windows environments, with no mention of how to achieve similar functionality on Linux or with cross-platform technologies.
Recommendations
  • Add instructions and examples for building and running the service on Linux, using .NET Core/.NET 6+ (which is cross-platform) and compatible editors like VS Code.
  • Include command-line instructions for project creation and package management (e.g., dotnet CLI) instead of relying solely on Visual Studio UI.
  • Clarify which steps are Windows-specific and provide Linux/macOS equivalents (e.g., file paths, running as administrator/sudo).
  • Mention and demonstrate how to use cross-platform alternatives to WCF (such as ASP.NET Core with Azure Relay, if supported) or note platform limitations.
  • Explicitly state the platform requirements and suggest alternatives for non-Windows users.
Scanned: 2026-01-12 00:00
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 oriented toward Windows development environments, specifically Visual Studio and .NET Framework. All examples, instructions, and tooling references assume the use of Windows, with no mention of Linux alternatives or cross-platform development. There are no instructions for using Linux-based tools, editors, or SDKs, nor any guidance for running the sample applications on Linux. The tutorial does not address how to set up or run the WCF Relay scenario outside of Windows, nor does it mention .NET Core/5+/6+ cross-platform capabilities.
Recommendations
  • Provide equivalent instructions for setting up the development environment on Linux, including installation of .NET SDK and use of cross-platform editors like VS Code.
  • Include examples for creating and running the WCF service and client using .NET Core/6+ on Linux.
  • Document how to use Azure Relay from Linux, including any required configuration or limitations.
  • Mention and demonstrate use of cross-platform tools (e.g., dotnet CLI) instead of or alongside Visual Studio.
  • Clarify which steps are Windows-specific and offer Linux/macOS alternatives where possible.
  • Add troubleshooting notes for common issues encountered on non-Windows platforms.
Previous Page 1 of 8 Next