Azure Signalr

78
Total Pages
59
Linux-Friendly Pages
19
Pages with Bias
24.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

77 issues found
Showing 1-25 of 77 flagged pages
Azure Signalr Develop with ASP.NET - Azure SignalR Service ...in/articles/azure-signalr/signalr-quickstart-dotnet.md
High Priority View Details →
Scanned: 2026-01-14 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 towards Windows development environments. It assumes the use of Visual Studio (Windows-only for .NET Framework), references .NET Framework (not .NET Core), and provides instructions for using PowerShell and Visual Studio tools without mentioning Linux/macOS alternatives. There are no examples or guidance for running the sample app or installing dependencies on Linux or macOS, nor is there mention of cross-platform editors or command-line tools.
Recommendations
  • Add instructions for running the sample app on Linux/macOS, including using .NET Core/Mono where possible.
  • Include examples for installing NuGet packages via the dotnet CLI (cross-platform), not just PowerShell.
  • Mention cross-platform editors (e.g., VS Code) and how to open/modify the project on non-Windows systems.
  • Clarify whether the sample can be run on Linux/macOS, and if not, provide links to equivalent ASP.NET Core samples that are cross-platform.
  • Provide parity in troubleshooting and cleanup steps for Linux/macOS users.
GitHub Create Pull Request
Azure Signalr Develop with ASP.NET - Azure SignalR Service ...in/articles/azure-signalr/signalr-quickstart-dotnet.md
High Priority View Details →
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 oriented toward Windows development environments. It lists Visual Studio (Windows-only) as a prerequisite, references .NET Framework (not .NET Core), and provides instructions and examples that assume use of Visual Studio and PowerShell. There are no instructions or examples for Linux/macOS users, such as using VS Code, .NET Core, or command-line alternatives. This creates significant friction for non-Windows users attempting to follow the quickstart.
Recommendations
  • Add instructions for Linux/macOS environments, including using VS Code or JetBrains Rider.
  • Include .NET Core/ASP.NET Core alternatives and examples, which are cross-platform.
  • Provide command-line instructions for package installation (e.g., dotnet CLI) instead of only PowerShell/NuGet Package Manager Console.
  • Clarify which steps are Windows-specific and offer platform-agnostic alternatives where possible.
  • List prerequisites for Linux/macOS, such as Mono or .NET Core SDK, and provide installation guidance.
GitHub Create Pull Request
Azure Signalr Move an Azure SignalR resource to another region ...les/azure-signalr/signalr-howto-move-across-regions.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides detailed instructions for moving an Azure SignalR resource using the Azure portal and Azure PowerShell. All command-line examples use PowerShell, and Windows-specific tools (e.g., notepad) are referenced. There are no examples or guidance for Linux users (e.g., Bash, Azure CLI, Linux text editors), and PowerShell is presented as the only scripting option. This creates a bias towards Windows users and leaves Linux users without parity in instructions.
Recommendations
  • Add equivalent instructions using Azure CLI (az commands) for exporting, editing, and deploying Resource Manager templates.
  • Include examples of editing JSON files with cross-platform editors (e.g., vim, nano, code) instead of only referencing notepad.
  • Provide explicit Bash shell command examples for Linux/macOS users.
  • Mention that PowerShell Core is available cross-platform, but also offer Azure CLI alternatives for common operations.
  • Ensure that all steps (resource group creation, deployment, verification, deletion) have both PowerShell and Azure CLI examples side-by-side.
GitHub Create Pull Request
Azure Signalr Troubleshooting practice for Azure SignalR Service ...les/azure-signalr/signalr-howto-troubleshoot-method.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (Fiddler, web.config, Windows Phone 8) are mentioned before or more prominently than Linux equivalents. Logging and tracing instructions often reference Windows-centric configuration (web.config, Windows desktop apps) and platforms (Windows Phone 8) without equivalent Linux or cross-platform guidance. Linux tools (tcpdump) are mentioned, but typically after Windows tools and without detailed parity in examples.
Recommendations
  • Present Linux tools (e.g., tcpdump) alongside Windows tools (e.g., Fiddler), giving equal prominence and detail.
  • Provide explicit Linux configuration examples for logging and tracing (e.g., alternatives to web.config for .NET Core on Linux).
  • Include troubleshooting steps and examples for Linux and macOS environments, such as using systemd, journalctl, or other native logging mechanisms.
  • Avoid referencing Windows-only platforms (e.g., Windows Phone 8) without noting their obsolescence and providing alternatives for other platforms.
  • Ensure all code/configuration samples are cross-platform or provide separate samples for Windows and Linux.
  • Add a section or callouts for Linux-specific troubleshooting tips and common issues.
GitHub Create Pull Request
Azure Signalr Troubleshooting guide for Azure SignalR Service ...cles/azure-signalr/signalr-howto-troubleshoot-guide.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 consistently referencing Windows-specific tools (Fiddler, Performance Monitor), using Windows-centric terminology (e.g., HTTP.SYS), and providing troubleshooting steps and code samples that assume a Windows environment. There is a lack of Linux-specific guidance, examples, or parity in troubleshooting instructions, especially for diagnostics, logging, and network inspection. Linux alternatives are not mentioned or are omitted entirely.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples alongside Windows instructions, especially for diagnostics and network inspection.
  • Mention and demonstrate Linux tools such as tcpdump, Wireshark, strace, and journalctl for viewing outgoing requests, logs, and performance metrics.
  • Include guidance for configuring TLS and .NET on Linux (e.g., using OpenSSL, configuring Kestrel, setting environment variables).
  • Add instructions for collecting and analyzing thread pool starvation and memory dumps on Linux (e.g., using dotnet-dump, perf, or gdb).
  • Ensure all code samples and configuration steps are cross-platform or clearly indicate platform-specific differences.
  • Reference Linux container scenarios (e.g., Docker, Kubernetes) with relevant links and examples.
GitHub Create Pull Request
Azure Signalr Use Azure SignalR Service .../blob/main/articles/azure-signalr/signalr-howto-use.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias in several areas: installation instructions for the legacy ASP.NET SignalR SDK use PowerShell/Package Manager Console (Windows-only), configuration references web.config (Windows/IIS-centric), and there are no Linux-specific equivalents or examples (e.g., Bash, Linux environment variable setup, or cross-platform configuration guidance). Windows tools and patterns are mentioned exclusively or before any Linux alternatives, and Linux users are left to infer how to adapt instructions.
Recommendations
  • Provide Linux/macOS equivalents for SDK installation (e.g., dotnet CLI, NuGet CLI, or Bash commands).
  • Include instructions for setting environment variables on Linux (e.g., using export in Bash, or systemd service files).
  • Document configuration alternatives for non-Windows environments (e.g., appsettings.json for .NET Core, environment variables, or other cross-platform config files).
  • Avoid referencing Windows-specific tools (like Package Manager Console and web.config) without mentioning cross-platform alternatives.
  • Add explicit notes or sections for Linux/macOS users to ensure parity and clarity.
GitHub Create Pull Request
Azure Signalr Quickstart: Create an Azure SignalR Service - ARM template ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-quickstart-azure-signalr-service-arm-template.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. PowerShell is presented as a primary deployment option alongside Portal and CLI, and PowerShell examples are given in full detail. In the CLI prerequisites, Bash is mentioned, but the example specifically suggests Git Bash (a Windows-centric Bash implementation) before any native Linux shell, and does not mention Linux or macOS shells explicitly. The documentation does not provide explicit Linux-specific instructions or acknowledge Linux environments directly, and the ordering of PowerShell before CLI in all sections subtly prioritizes Windows tooling.
Recommendations
  • Explicitly mention Linux and macOS compatibility in CLI sections, and recommend native Bash shells for those platforms.
  • Provide instructions or notes for running Azure CLI commands on Linux and macOS, including installation links for those platforms.
  • Avoid suggesting Git Bash as the default Bash shell for CLI usage; instead, mention it as an option for Windows users, and recommend native Bash for Linux/macOS.
  • Consider alternating the order of PowerShell and CLI examples, or grouping them under 'Command-line' to avoid Windows-first presentation.
  • Add a short section or note confirming that all CLI commands work natively on Linux and macOS, and provide troubleshooting tips for those platforms if needed.
GitHub Create Pull Request
Azure Signalr Develop with ASP.NET - Azure SignalR Service ...in/articles/azure-signalr/signalr-quickstart-dotnet.md
High Priority View Details →
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 page exhibits a Windows bias by exclusively referencing Windows tools (Visual Studio, NuGet Package Manager, Package Manager Console), providing instructions tailored for Windows environments, and omitting Linux equivalents or cross-platform alternatives. There are no examples or guidance for developing or running the sample on Linux (e.g., using VS Code, CLI tools, or Mono), and PowerShell is used for package installation without mention of dotnet CLI or NuGet CLI alternatives.
Recommendations
  • Add instructions for setting up and running the sample on Linux, including using VS Code or JetBrains Rider.
  • Include package installation steps using dotnet CLI (e.g., 'dotnet add package') and NuGet CLI, not just PowerShell/Package Manager Console.
  • Mention cross-platform prerequisites, such as Mono or .NET Core SDK, where applicable.
  • Clarify that the sample can be run on Linux and macOS, and provide any necessary configuration steps.
  • Provide troubleshooting steps or notes specific to non-Windows environments.
  • Avoid assuming Visual Studio as the only IDE; suggest alternatives for Linux/macOS users.
GitHub Create Pull Request
Azure Signalr Move an Azure SignalR resource to another region ...les/azure-signalr/signalr-howto-move-across-regions.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides detailed instructions for moving an Azure SignalR resource using the Azure portal and Azure PowerShell, with all CLI examples and tooling focused on PowerShell. There are no examples or guidance for using Azure CLI, Bash, or Linux-native tools, and even text editors referenced (e.g., Notepad) are Windows-specific. The PowerShell workflow is presented as the only command-line option, and Windows tools are mentioned without Linux alternatives.
Recommendations
  • Add equivalent instructions and examples using Azure CLI (az), which is cross-platform and commonly used on Linux and macOS.
  • Include Bash shell command examples for template editing and deployment, such as using vim, nano, or code editors available on Linux.
  • Reference cross-platform text editors (e.g., VS Code, nano) instead of Notepad.
  • Explicitly mention that all steps can be performed on Linux/macOS, and provide OS-agnostic guidance where possible.
  • Consider reordering or parallelizing sections so that PowerShell and CLI/Linux approaches are presented together, rather than PowerShell being the only command-line method.
GitHub Create Pull Request
Azure Signalr Troubleshooting guide for Azure SignalR Service ...cles/azure-signalr/signalr-howto-troubleshoot-guide.md
High Priority View Details →
Scanned: 2026-01-11 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 prioritizing Windows-centric troubleshooting steps, tools, and examples. It references Windows-specific debugging patterns (such as 'Just My Code', CLR exceptions), uses Windows-only tools (Fiddler), and omits Linux equivalents for diagnostics and troubleshooting. There are no examples or guidance for Linux environments, such as using Linux-based debugging tools, viewing logs, or handling TLS settings on Linux servers.
Recommendations
  • Add Linux-specific troubleshooting steps, such as using strace, tcpdump, or curl for network diagnostics.
  • Include instructions for enabling logging and tracing in Linux environments (e.g., configuring logging in systemd services, using journalctl, or inspecting logs in /var/log).
  • Provide examples for viewing outgoing requests using Linux tools (e.g., Wireshark, tcpdump, or browser developer tools on Linux).
  • Mention how to configure TLS settings for .NET Core/ASP.NET apps running on Linux (e.g., environment variables, OpenSSL configuration).
  • Reference cross-platform tools and patterns (such as dotnet CLI, VS Code debugging, or platform-agnostic logging frameworks) alongside or before Windows-specific ones.
  • Ensure that any code or configuration snippets are applicable to both Windows and Linux, or clearly indicate platform-specific differences.
GitHub Create Pull Request
Azure Signalr Troubleshooting practice for Azure SignalR Service ...les/azure-signalr/signalr-howto-troubleshoot-method.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. Windows tools (Fiddler, web.config, Windows Phone 8) are mentioned first or exclusively in several troubleshooting sections. While tcpdump is referenced for Linux/macOS, Windows tools and patterns (Fiddler, web.config, Windows Phone 8 tracing) are often listed before or without Linux equivalents. There are no explicit Linux logging examples, and configuration samples (web.config) are Windows-centric.
Recommendations
  • Ensure Linux tools (e.g., tcpdump, Wireshark) are mentioned alongside or before Windows tools like Fiddler.
  • Provide explicit logging/tracing configuration examples for Linux environments (e.g., systemd journal, syslog, Linux file paths).
  • Include instructions for enabling server-side logs in Linux deployments, such as modifying appsettings.json or using environment variables.
  • Avoid referencing Windows-only platforms (e.g., Windows Phone 8) without mentioning Linux/mobile alternatives.
  • Where web.config is referenced, provide equivalent configuration for Linux (e.g., environment variables, appsettings.json, or other cross-platform approaches).
GitHub Create Pull Request
Azure Signalr Use Azure SignalR Service .../blob/main/articles/azure-signalr/signalr-howto-use.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation shows bias towards Windows environments by providing package installation instructions for the legacy ASP.NET SignalR SDK only via PowerShell (Package Manager Console), referencing configuration via web.config (a Windows/IIS-centric pattern), and omitting Linux or cross-platform equivalents. There are no Linux-specific instructions or examples for configuring environment variables, installing packages, or managing configuration files. The documentation assumes a Windows development environment for legacy ASP.NET SignalR and does not mention Linux alternatives or parity.
Recommendations
  • Provide Linux and cross-platform instructions for installing the legacy ASP.NET SignalR SDK, such as using the dotnet CLI or NuGet CLI.
  • Include examples for setting environment variables on Linux (e.g., using export in bash) and configuring connection strings outside of web.config (such as appsettings.json for .NET Core, or environment variables for ASP.NET).
  • Mention configuration file alternatives for Linux (e.g., appsettings.json, environment variables) alongside web.config.
  • Clarify that the Package Manager Console is a Visual Studio/Windows tool and suggest alternatives for Linux/macOS users.
  • Add notes or sections explicitly addressing Linux/macOS development environments for both ASP.NET Core and legacy ASP.NET SignalR.
GitHub Create Pull Request
Azure Signalr Develop with ASP.NET - Azure SignalR Service ...in/articles/azure-signalr/signalr-quickstart-dotnet.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 oriented towards Windows development, with prerequisites listing only Visual Studio (Windows-only), .NET Framework (Windows-only), and ASP.NET SignalR (classic, not Core). All configuration and run instructions assume Visual Studio, and the only package installation example uses PowerShell (Package Manager Console). There are no instructions or examples for Linux or cross-platform development environments, nor any mention of alternatives like VS Code, .NET Core, or command-line tools for Linux/macOS.
Recommendations
  • Add instructions for running the sample on Linux/macOS using .NET Core and ASP.NET Core where possible.
  • Include examples for installing packages via the dotnet CLI (e.g., 'dotnet add package ...') instead of only PowerShell.
  • Mention and provide steps for using VS Code or other cross-platform editors.
  • Clarify which steps are Windows-specific and provide Linux/macOS equivalents (e.g., editing config files, running the app).
  • List Linux/macOS prerequisites (e.g., .NET Core SDK, Mono if needed) and provide download links.
  • Add troubleshooting notes for common Linux/macOS issues.
GitHub Create Pull Request
Azure Signalr Quickstart: Create an Azure SignalR Service - ARM template ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-quickstart-azure-signalr-service-arm-template.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation presents deployment options in three tabs: Portal, PowerShell, and CLI. PowerShell (a Windows-centric tool) is given equal prominence to CLI, and is listed before CLI in all sections. The CLI instructions mention Bash and Git Bash, but the Bash example is generic and does not provide explicit Linux-specific guidance or examples. The prerequisites for CLI mention Git Bash (a Windows tool) before referencing Bash shells in general, which may imply a Windows-first perspective. There are no explicit Linux examples, nor is there mention of Linux-specific shell environments or considerations.
Recommendations
  • Explicitly mention Linux and macOS as supported platforms for Azure CLI, and provide examples or notes for common Linux shells (e.g., bash, zsh).
  • In CLI prerequisites, list Bash (Linux/macOS) before Git Bash (Windows), or clarify that Bash is available natively on Linux/macOS.
  • Add a note or section highlighting that all CLI commands work on Linux/macOS terminals without modification.
  • Consider providing sample screenshots or terminal outputs from Linux environments to reinforce cross-platform parity.
  • If PowerShell is mentioned, clarify that PowerShell Core is available on Linux/macOS, and provide installation links for those platforms.
GitHub Create Pull Request
Azure Signalr Develop with ASP.NET - Azure SignalR Service ...in/articles/azure-signalr/signalr-quickstart-dotnet.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. It exclusively lists Windows-centric prerequisites (Visual Studio 2019, .NET Framework 4.6.1), assumes the use of Visual Studio for project setup and running, and provides package installation instructions only via the NuGet Package Manager Console (PowerShell-based). There are no Linux or cross-platform alternatives mentioned for development, tooling, or running the sample application. The page does not reference Linux-compatible IDEs, .NET Core, or command-line alternatives for key steps.
Recommendations
  • Add instructions for setting up and running the sample on Linux, including using Visual Studio Code or JetBrains Rider.
  • Include .NET Core or .NET 5+ as a prerequisite for cross-platform compatibility.
  • Provide package installation commands using the dotnet CLI (e.g., 'dotnet add package') alongside NuGet Package Manager Console.
  • Offer guidance for running and debugging the application from the command line (e.g., 'dotnet run'), not just via Visual Studio.
  • Clarify which steps are Windows-specific and provide Linux/macOS equivalents where possible.
  • Mention alternative editors and tools for non-Windows environments.
GitHub Create Pull Request
Azure Signalr Troubleshooting practice for Azure SignalR Service ...les/azure-signalr/signalr-howto-troubleshoot-method.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools (Fiddler) are mentioned before Linux equivalents (tcpdump), and some logging/tracing instructions focus on Windows-specific platforms (Windows Phone 8, Windows desktop apps) without Linux alternatives. There is a lack of parity in examples and instructions for Linux environments, especially for logging and tracing in .NET clients. The documentation also references configuration files (web.config) and patterns typical of Windows/IIS deployments, with no mention of Linux-specific equivalents.
Recommendations
  • Ensure Linux tools (e.g., tcpdump, Wireshark) are presented alongside or before Windows tools like Fiddler.
  • Provide explicit Linux/macOS examples for enabling .NET client logging and tracing, including configuration for common Linux hosting scenarios.
  • Include instructions for configuring server-side logging and tracing in Linux environments (e.g., using environment variables, systemd, or file-based logging).
  • Avoid referencing Windows-only platforms (e.g., Windows Phone 8) without noting their limited applicability and providing alternatives for other platforms.
  • Where configuration files are referenced (e.g., web.config), mention Linux equivalents or alternative approaches for cross-platform deployments.
GitHub Create Pull Request
Azure Signalr Use Azure SignalR Service .../blob/main/articles/azure-signalr/signalr-howto-use.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias toward Windows environments, particularly in the legacy ASP.NET SignalR section. Package installation is shown only via PowerShell's Package Manager Console, and configuration examples reference Windows-centric files like web.config. There are no Linux-specific instructions or parity for common Linux workflows (e.g., Bash, .NET CLI, environment variable setup). Windows tools and patterns are mentioned exclusively or before any cross-platform alternatives.
Recommendations
  • Provide Linux-friendly installation instructions for the legacy ASP.NET SignalR SDK, such as using the .NET CLI (e.g., 'dotnet add package').
  • Include examples for setting environment variables on Linux (e.g., using 'export' in Bash) alongside Windows instructions.
  • Mention configuration alternatives for Linux deployments, such as using appsettings.json or environment variables, rather than only referencing web.config.
  • When showing package installation, offer both PowerShell and Bash/.NET CLI commands, and clarify which platforms each applies to.
  • Review all tooling references to ensure Linux equivalents are presented with equal prominence and clarity.
GitHub Create Pull Request
Azure Signalr Troubleshooting guide for Azure SignalR Service ...cles/azure-signalr/signalr-howto-troubleshoot-guide.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific tools (Fiddler, Performance Monitor), using Windows-centric troubleshooting steps (e.g., HTTP.SYS, ServicePointManager), and omitting Linux equivalents or examples. Troubleshooting and code samples are focused on ASP.NET/ASP.NET Core (C#), with no mention of Linux server environments, Linux tools, or cross-platform diagnostics. Windows tools and patterns are mentioned exclusively or before any Linux alternatives.
Recommendations
  • Add Linux-specific troubleshooting steps and examples, such as using curl, tcpdump, or Wireshark for network diagnostics.
  • Include instructions for viewing outgoing requests on Linux (e.g., using Chrome DevTools on Linux, or command-line tools like netstat, ss, or lsof).
  • Mention Linux equivalents for performance monitoring (e.g., top, htop, dotnet-counters, or PerfView on Linux).
  • Clarify that ServicePointManager and HTTP.SYS are Windows/.NET Framework-specific and provide guidance for .NET Core on Linux (e.g., configuring TLS via environment variables or Kestrel settings).
  • Reference cross-platform logging and tracing tools (e.g., Serilog, ELK stack, journald) and provide sample configurations.
  • Ensure all troubleshooting steps and code samples are applicable to both Windows and Linux environments, or explicitly note platform differences.
GitHub Create Pull Request
Azure Signalr Move an Azure SignalR resource to another region ...les/azure-signalr/signalr-howto-move-across-regions.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides detailed instructions for moving an Azure SignalR resource using the Azure portal and Azure PowerShell, with all CLI examples and tooling based on PowerShell. There are no examples or guidance for Linux users (e.g., Azure CLI/bash), and Windows-specific tools like Notepad are referenced. The PowerShell method is presented as the only command-line option, and Windows-centric patterns (editing with Notepad, PowerShell cmdlets) are used exclusively.
Recommendations
  • Add equivalent instructions using Azure CLI (az commands) for Linux/macOS users.
  • Replace or supplement Notepad references with cross-platform editors (e.g., 'edit with your preferred text editor').
  • Explicitly mention that PowerShell is available on Linux/macOS, or provide bash/CLI alternatives.
  • Ensure that command-line examples are provided for both Windows and Linux environments.
  • Consider reordering or parallelizing sections so that Linux/CLI options are presented alongside Windows/PowerShell options, not only after or below them.
GitHub Create Pull Request
Azure Signalr https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-howto-use.md .../blob/main/articles/azure-signalr/signalr-howto-use.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by providing package installation instructions for the legacy ASP.NET SignalR SDK only via the Windows-specific 'Package Manager Console' (PowerShell), referencing configuration via 'web.config' (a Windows/IIS convention), and omitting equivalent Linux-friendly instructions (such as .NET CLI or NuGet CLI commands). There are no Linux-specific examples or mentions of Linux deployment patterns, and Windows tools/patterns are presented exclusively for legacy scenarios.
Recommendations
  • Add Linux-friendly installation instructions for the legacy ASP.NET SignalR SDK, such as using the NuGet CLI (e.g., 'nuget install') or .NET CLI where applicable.
  • Include guidance for configuring connection strings and settings in Linux environments, such as using environment variables or configuration files common to Linux deployments.
  • Mention cross-platform deployment considerations, clarifying that ASP.NET and ASP.NET Core apps can run on Linux and how to adapt configuration accordingly.
  • Where 'web.config' is referenced, provide alternative instructions for Linux scenarios (e.g., using appsettings.json or environment variables).
  • Ensure that all code samples and operational instructions are platform-neutral or provide both Windows and Linux examples side-by-side.
GitHub Create Pull Request
Azure Signalr https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-concept-authorize-azure-active-directory.md ...lr/signalr-concept-authorize-azure-active-directory.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 Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Microsoft-specific tools and patterns, such as Microsoft Entra ID and Azure RBAC, without providing cross-platform command-line examples. The only explicit tool mentioned for cross-tenant provisioning is 'msgraph-powershell', with no mention of Linux-friendly alternatives or CLI equivalents. There are no examples or instructions for Linux users, and the documentation assumes familiarity with Windows-centric workflows and tools.
Recommendations
  • Provide Azure CLI and REST API examples alongside PowerShell instructions for all provisioning and configuration steps.
  • Explicitly mention Linux compatibility and offer guidance for Linux/macOS users, including installation and usage of cross-platform tools.
  • Include sample commands for Linux shells (bash/zsh) where authentication, role assignment, or resource management is discussed.
  • Reference platform-neutral documentation links (e.g., Azure CLI, REST API) before or alongside Windows/PowerShell-specific resources.
  • Clarify that Microsoft Entra ID and Azure RBAC can be managed from any OS, and highlight cross-platform SDKs and tools.
GitHub Create Pull Request
Azure Signalr https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-howto-troubleshoot-guide.md ...cles/azure-signalr/signalr-howto-troubleshoot-guide.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (Fiddler, Performance Monitor), Windows debugging patterns (Visual Studio 'Just My Code', CLR exceptions), and providing troubleshooting steps and code samples that assume a Windows/.NET environment. There are no Linux-specific examples, nor are cross-platform alternatives mentioned for key troubleshooting steps. Linux tools and workflows are missing or not prioritized.
Recommendations
  • Include Linux-specific troubleshooting steps and examples, such as using tcpdump, Wireshark, or curl for network diagnostics.
  • Mention cross-platform alternatives to Fiddler, such as mitmproxy or Wireshark, and provide instructions for their use.
  • Add guidance for debugging .NET applications on Linux, such as using VS Code, JetBrains Rider, or command-line tools like dotnet-trace and dotnet-dump.
  • Reference Linux equivalents for performance monitoring, such as top, htop, or dotnet-counters.
  • Ensure that code samples and configuration steps are applicable to both Windows and Linux environments, or clearly indicate platform-specific instructions.
  • When describing steps (e.g., viewing outgoing requests), present Linux/macOS options alongside Windows, or in parallel.
GitHub Create Pull Request
Azure Signalr https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-quickstart-azure-signalr-service-arm-template.md ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-quickstart-azure-signalr-service-arm-template.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 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented as a primary automation option alongside the Azure portal and CLI, and PowerShell examples are given in full detail. In the CLI prerequisites, Bash is mentioned, but the example suggests using Git Bash from Git for Windows, which is a Windows-centric recommendation. The ordering of tabs and examples consistently places PowerShell before CLI, and the CLI instructions reference Bash but do not provide parity for native Linux environments or mention Linux-specific considerations. No explicit Linux-only examples or troubleshooting are provided.
Recommendations
  • In CLI prerequisites, recommend native Bash shells on Linux and macOS (e.g., Ubuntu Terminal, macOS Terminal) before mentioning Git Bash for Windows.
  • Add explicit notes or examples for Linux and macOS environments, including installation and usage of Azure CLI on those platforms.
  • Reorder tabs or examples so that CLI (cross-platform) is presented before PowerShell (Windows-centric), or clarify platform applicability for each method.
  • Include troubleshooting or environment setup instructions for Linux and macOS users, ensuring parity with Windows guidance.
  • Avoid suggesting Windows tools (like Git Bash) as the default for CLI usage; instead, provide platform-neutral or platform-specific recommendations.
GitHub Create Pull Request
Azure Signalr https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-howto-move-across-regions.md ...les/azure-signalr/signalr-howto-move-across-regions.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 Tools Missing Linux Example Windows First
Summary
The documentation provides detailed instructions for moving an Azure SignalR resource using the Azure portal and Azure PowerShell. All command-line examples use PowerShell, and references to tools like 'notepad' and PowerShell cmdlets are Windows-centric. There are no examples or guidance for Linux users (e.g., using Azure CLI, Linux text editors, or shell commands), and PowerShell is presented as the only scripting option. This creates a bias toward Windows users and leaves Linux users without parity in instructions.
Recommendations
  • Add equivalent instructions using Azure CLI, which is cross-platform and widely used on Linux.
  • Include examples of editing JSON files using Linux-friendly editors (e.g., 'nano', 'vim') alongside 'notepad'.
  • Explicitly mention that PowerShell Core is available on Linux, if PowerShell must be used, and provide installation guidance.
  • Present Azure CLI and PowerShell options side-by-side, or at least mention both, to avoid Windows-first bias.
  • Ensure all command-line steps have Linux-compatible alternatives, including resource group creation, template export, and deployment.
GitHub Create Pull Request
Azure Signalr https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-howto-troubleshoot-method.md ...les/azure-signalr/signalr-howto-troubleshoot-method.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation exhibits mild Windows bias. Windows tools like Fiddler are mentioned before Linux equivalents (tcpdump), and some logging/tracing examples reference Windows-specific platforms (Windows Phone 8, .NET client for Windows desktop apps). There is a lack of parity in examples for Linux environments, especially in logging and tracing sections, and no mention of Linux-specific troubleshooting tools beyond tcpdump.
Recommendations
  • Present Linux and Windows tools side-by-side, or alternate which is listed first to avoid implicit prioritization.
  • Expand logging/tracing examples to include Linux-specific instructions (e.g., using syslog, journalctl, or other common Linux logging mechanisms).
  • Include examples for enabling tracing/logging in Linux environments, such as .NET Core apps running on Linux, and clarify any platform-specific differences.
  • Mention cross-platform tools (e.g., Wireshark) and provide usage instructions for both Windows and Linux.
  • Remove or supplement Windows-only references (e.g., Windows Phone 8 clients) with equivalent Linux/mobile client instructions if available.
  • Ensure all troubleshooting steps and code/configuration samples are applicable to both Windows and Linux, or clearly indicate platform specificity.
GitHub Create Pull Request
← Previous Page 1 of 4 Next →