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 51-75 of 77 flagged pages
Azure Signalr Use Azure SignalR Service .../blob/main/articles/azure-signalr/signalr-howto-use.md
Medium Priority View Details →
Scanned: 2026-01-14 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 mild Windows bias, particularly in the legacy ASP.NET SignalR section, where the SDK installation is shown only using the Windows-specific Package Manager Console (PowerShell). There are no Linux/macOS equivalents or cross-platform installation instructions for legacy ASP.NET SignalR. The ordering also places Windows tooling first, and omits Linux/macOS alternatives for configuration and setup. The ASP.NET Core section is more cross-platform, using dotnet CLI, but the legacy section is Windows-centric.
Recommendations
  • Provide cross-platform installation instructions for legacy ASP.NET SignalR, such as NuGet CLI or manual package reference for Linux/macOS users.
  • Include Linux/macOS equivalents for configuration steps, e.g., how to set environment variables or edit config files on non-Windows platforms.
  • Where PowerShell or Windows tools are mentioned, add alternative commands for Bash or other shells.
  • Explicitly state platform compatibility and provide guidance for non-Windows users in all relevant sections.
GitHub Create Pull Request
Azure Signalr Troubleshooting practice for Azure SignalR Service ...les/azure-signalr/signalr-howto-troubleshoot-method.md
Medium Priority View Details →
Scanned: 2026-01-14 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 exhibits moderate Windows bias. Windows tools (Fiddler, web.config) are mentioned first or exclusively in several troubleshooting sections, and some logging examples (e.g., enabling tracing in Windows Phone 8 clients, web.config for ASP.NET SignalR) are Windows-specific. Linux tools (tcpdump) are referenced, but often after Windows tools, and some examples (like .NET client logging for desktop apps) are Windows-only. There is limited guidance for Linux/macOS users in certain areas, especially for classic ASP.NET SignalR scenarios.
Recommendations
  • Present Linux/macOS tools (e.g., tcpdump, Wireshark) alongside or before Windows tools like Fiddler.
  • Provide explicit Linux/macOS examples for enabling .NET client logging and server-side tracing, especially for ASP.NET SignalR.
  • Clarify which instructions are cross-platform and which are Windows-only, and offer alternatives where possible.
  • Add guidance for configuring logs and traces on Linux/macOS environments (e.g., using environment variables, configuration files other than web.config).
  • Ensure parity in troubleshooting steps and tool recommendations for all platforms.
GitHub Create Pull Request
Azure Signalr Authorize access with Microsoft Entra ID for Azure SignalR Service ...lr/signalr-concept-authorize-azure-active-directory.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references Microsoft-specific tools and patterns, such as Microsoft Entra ID and Azure RBAC, which are inherently Windows-centric. The only explicit tooling link for cross-tenant provisioning points to 'msgraph-powershell', a Windows-first tool, without mentioning Linux/macOS alternatives or CLI equivalents. No Linux/macOS-specific instructions or parity examples are provided, and Windows tools are referenced before any cross-platform options.
Recommendations
  • Include Azure CLI and REST API instructions/examples for cross-tenant provisioning and role assignments, as these are cross-platform.
  • Where PowerShell is referenced, provide equivalent commands for Azure CLI and/or REST API.
  • Explicitly state platform compatibility for all tools and workflows.
  • Add notes or sections for Linux/macOS users, highlighting any differences or additional steps required.
  • Link to documentation for installing and using Azure CLI on Linux/macOS.
GitHub Create Pull Request
Azure Signalr Move an Azure SignalR resource to another region ...les/azure-signalr/signalr-howto-move-across-regions.md
Medium Priority View Details →
Scanned: 2026-01-13 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. The PowerShell section is extensive and uses Windows-specific tools (e.g., Notepad for editing JSON files), with no mention of Linux/macOS equivalents or CLI alternatives. There are no Bash, Azure CLI, or cross-platform scripting examples, and the PowerShell workflow is presented before any Linux-friendly alternatives.
Recommendations
  • Add equivalent instructions using Azure CLI, which is cross-platform and commonly used on Linux/macOS.
  • Replace or supplement 'notepad' with cross-platform editors (e.g., 'code', 'vim', 'nano') or generic instructions for editing JSON files.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, and provide guidance for those platforms.
  • Present Azure CLI and PowerShell examples side-by-side, or at least mention CLI alternatives before or alongside PowerShell.
  • Include notes or links for Linux/macOS users on how to install and use required tools.
GitHub Create Pull Request
Azure Signalr Troubleshooting guide for Azure SignalR Service ...cles/azure-signalr/signalr-howto-troubleshoot-guide.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias: troubleshooting steps and code samples are almost exclusively for ASP.NET/ASP.NET Core (C#), which are most commonly deployed on Windows. Debugging instructions reference Visual Studio features ('Just My Code', CLR exceptions), and network traffic inspection suggests Fiddler (a Windows tool) without mentioning Linux/macOS alternatives. There are no explicit Linux/macOS troubleshooting steps, nor are cross-platform tools (like Wireshark, tcpdump, or VS Code debugging) referenced. No examples or guidance are provided for running SignalR on Linux or macOS, nor for troubleshooting in those environments.
Recommendations
  • Add equivalent troubleshooting steps for Linux/macOS environments, such as using VS Code or JetBrains Rider for debugging, and referencing Mono/.NET Core cross-platform capabilities.
  • Include examples of inspecting network traffic using cross-platform tools like Wireshark or tcpdump.
  • Provide guidance for configuring TLS and debugging on Linux (e.g., using OpenSSL, systemd logs, journalctl).
  • Mention how to enable server-side logging and diagnostics in Linux containers and on macOS.
  • Ensure that code samples and configuration steps are applicable to .NET Core running on Linux/macOS, and clarify any Windows-specific instructions.
  • List Linux/macOS equivalents for tools like Fiddler (e.g., mitmproxy, Wireshark) and Visual Studio features.
GitHub Create Pull Request
Azure Signalr Use Azure SignalR Service .../blob/main/articles/azure-signalr/signalr-howto-use.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page shows mild Windows bias, especially in the legacy ASP.NET SignalR section, where the SDK installation is demonstrated only using PowerShell's Package Manager Console (a Windows-centric tool). The configuration examples reference web.config, which is more common in Windows/IIS deployments. There are no explicit Linux/macOS instructions or parity for SDK installation or configuration, and Windows tools are mentioned first or exclusively in relevant sections.
Recommendations
  • Add instructions for installing the SignalR Service SDK using cross-platform tools such as the dotnet CLI (e.g., 'dotnet add package Microsoft.Azure.SignalR.AspNet') for legacy ASP.NET SignalR.
  • Include notes or examples for configuring connection strings and application settings in Linux/macOS environments (e.g., environment variables, appsettings.json, or other configuration files).
  • Where Package Manager Console is mentioned, clarify that it is Windows-only and provide alternatives for non-Windows users.
  • Ensure that examples and instructions are presented in a platform-neutral order, or explicitly call out platform-specific steps.
GitHub Create Pull Request
Azure Signalr Authorize requests to Azure SignalR Service resources with Microsoft Entra managed identities ...re-signalr/signalr-howto-authorize-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides configuration and code examples for Azure SignalR Service authorization using managed identities, but it implicitly favors Windows environments. Application settings examples reference the Azure portal (Windows-centric) and local development via Visual Studio, Azure CLI, and Azure PowerShell, with no explicit Linux shell or tool examples. There are no Linux-specific instructions or parity for configuring managed identities or accessing environment variables, and the order of examples and tool mentions (Visual Studio, Azure CLI, Azure PowerShell) suggests a Windows-first approach.
Recommendations
  • Add explicit Linux shell examples for configuring environment variables and application settings, such as using bash or zsh.
  • Include instructions for using Linux-native tools (e.g., vim, nano, or code editors) to edit local.settings.json.
  • Mention Linux equivalents for Azure CLI usage and clarify cross-platform compatibility.
  • Provide parity in examples for both Windows and Linux environments, including authentication flows and troubleshooting steps.
  • Explicitly state that the instructions apply to both Windows and Linux, and highlight any platform-specific differences.
GitHub Create Pull Request
Azure Signalr Quickstart: Create an Azure SignalR Service - Bicep ...nalr/signalr-quickstart-azure-signalr-service-bicep.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment, resource review, and cleanup. However, PowerShell is featured equally alongside CLI, and there is no explicit mention of Linux-specific tools or patterns. The use of PowerShell (which is traditionally associated with Windows) and the lack of Linux-specific shell examples (such as Bash) or explicit Linux instructions may indicate a mild Windows bias, especially for users unfamiliar with PowerShell or working primarily on Linux systems.
Recommendations
  • Add explicit Bash shell examples for all CLI commands to demonstrate usage on Linux and macOS.
  • Clarify that Azure CLI commands work identically on Windows, Linux, and macOS, and provide guidance for running them in Bash or other Linux shells.
  • Mention installation and usage of Azure CLI on Linux systems in the prerequisites.
  • Consider including screenshots or instructions for Linux terminal environments where relevant.
  • If PowerShell is included, note that PowerShell Core is cross-platform, but clarify differences if any exist for Linux users.
GitHub Create Pull Request
Azure Signalr Authorize requests to Azure SignalR Service resources with Microsoft Entra managed identities ...re-signalr/signalr-howto-authorize-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides configuration examples and instructions that are platform-neutral in some areas (e.g., JSON config files, Azure portal), but when discussing local development, it references Visual Studio, Azure CLI, and Azure PowerShell as authentication mechanisms without mentioning Linux-specific alternatives or editors. There are no explicit Linux shell or tool examples, and the documentation implicitly assumes a Windows-centric development environment.
Recommendations
  • Include explicit Linux development instructions, such as using VS Code, JetBrains Rider, or other cross-platform editors.
  • Provide examples for authenticating via Azure CLI on Linux and macOS, and clarify that Azure CLI is cross-platform.
  • Mention and provide examples for configuring managed identities and local development on Linux, including shell commands (bash/zsh) and environment variable setup.
  • Clarify that local.settings.json and related configuration files are platform-agnostic, and provide sample workflows for both Windows and Linux.
  • Avoid listing Windows tools (Visual Studio, PowerShell) before cross-platform alternatives, or provide parity in examples.
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
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows-specific tools and patterns before Linux equivalents. In the CLI prerequisites, Bash is mentioned as 'such as Git Bash, which is included in Git for Windows,' prioritizing a Windows-centric Bash environment over native Linux/macOS shells. The PowerShell instructions are presented as a primary option, which is inherently Windows-focused, and the CLI section references Bash in a Windows context first. There are no explicit Linux/macOS examples or instructions, and the documentation does not mention native Linux or macOS terminal environments or their installation processes.
Recommendations
  • In the CLI prerequisites, mention native Bash shells on Linux and macOS before referencing Git Bash for Windows. For example: 'A Bash shell (available by default on Linux and macOS, or via Git Bash on Windows)'.
  • Add explicit instructions or notes for Linux and macOS users regarding shell usage and Azure CLI installation.
  • Where PowerShell is referenced, clarify that it is available cross-platform, and provide links or instructions for installing PowerShell on Linux/macOS if relevant.
  • Consider adding example commands or screenshots from Linux/macOS environments to demonstrate parity.
  • Review and update language to avoid Windows-first phrasing, ensuring all platforms are treated equally.
GitHub Create Pull Request
Azure Signalr Authorize requests to Azure SignalR Service resources with Microsoft Entra managed identities ...re-signalr/signalr-howto-authorize-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing configuration via the Azure portal and local development tools (Visual Studio, Azure CLI, Azure PowerShell) without providing explicit Linux or cross-platform command-line examples. The use of application settings and local.settings.json is described, but there are no bash, shell, or Linux-specific instructions or examples. The documentation assumes familiarity with Windows-centric tools and workflows, and does not mention Linux equivalents or provide parity in example coverage.
Recommendations
  • Include explicit Linux examples for configuring managed identities, such as using bash scripts or Linux command-line tools.
  • Provide instructions for using Azure CLI on Linux to set application settings and role assignments.
  • Mention cross-platform development environments (e.g., VS Code, JetBrains Rider) and how managed identities can be configured outside of Visual Studio.
  • Clarify that local.settings.json and Azure CLI are cross-platform, and provide sample commands for both Windows and Linux shells.
  • Add notes or sections highlighting any differences or considerations for Linux users when configuring managed identities or developing with Azure SignalR Service.
GitHub Create Pull Request
Azure Signalr https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-howto-authorize-managed-identity.md ...re-signalr/signalr-howto-authorize-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure portal configuration and local development environments primarily through tools and patterns common on Windows (such as Visual Studio and Azure PowerShell), without providing equivalent Linux-specific examples or guidance. There are no explicit Linux shell or configuration examples, and Windows-centric development tools are mentioned before alternatives like Azure CLI or cross-platform editors.
Recommendations
  • Add explicit Linux examples for configuring managed identities, such as using Azure CLI commands in bash.
  • Include instructions for configuring local development environments on Linux, referencing editors like VS Code and authentication via Azure CLI.
  • Mention cross-platform tools and workflows before or alongside Windows-specific ones (e.g., Azure CLI before PowerShell).
  • Provide sample shell scripts or configuration steps for Linux environments where applicable.
  • Clarify that the instructions and SDKs are cross-platform, and highlight any platform-specific considerations.
GitHub Create Pull Request
Azure Signalr https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-quickstart-azure-signalr-service-bicep.md ...nalr/signalr-quickstart-azure-signalr-service-bicep.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment, resource review, and cleanup. However, PowerShell is featured equally alongside CLI, despite being a Windows-centric tool, and is presented as a primary alternative throughout. There is no explicit mention of Linux-specific considerations, nor are Linux shell examples (e.g., Bash) or platform-specific notes provided. The documentation implicitly assumes PowerShell is available and relevant for all users, which may not be the case for Linux users.
Recommendations
  • Clarify that Azure CLI commands work natively on Linux, macOS, and Windows, while PowerShell is primarily a Windows tool (though cross-platform versions exist).
  • Add explicit Bash shell examples or notes for Linux/macOS users, especially for file operations (e.g., saving the Bicep file).
  • Reorder examples to present Azure CLI first, emphasizing its cross-platform nature, and mention PowerShell as an alternative for Windows users.
  • Include a brief section or note on installing and using Azure CLI on Linux/macOS.
  • Avoid implying PowerShell is a default or primary option for all users; clarify platform applicability.
GitHub Create Pull Request
Azure Signalr https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-howto-authorize-managed-identity.md ...re-signalr/signalr-howto-authorize-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides configuration examples and instructions that are platform-neutral in most places, but references to development tools (Visual Studio, Azure PowerShell) and environment variable usage are presented without explicit Linux or cross-platform alternatives. The local development authentication flow mentions Visual Studio, Azure CLI, and Azure PowerShell, but does not provide equivalent Linux-specific guidance or examples (e.g., VS Code, Bash, or Linux credential management). There are no explicit Linux shell or tool examples, and the ordering of tools implies a Windows-first perspective.
Recommendations
  • Include explicit Linux examples for configuring managed identities, such as using Bash scripts or Linux credential management tools.
  • Mention and provide examples for cross-platform development environments like VS Code, not just Visual Studio.
  • Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell/CMD) and Linux (Bash).
  • Add notes or sections on how to perform equivalent steps on Linux, including environment variable configuration and authentication flows.
  • Ensure that references to local development tools and environment variables include Linux-specific details (e.g., ~/.bashrc, export commands) alongside Windows instructions.
GitHub Create Pull Request
Azure Signalr https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/howto-service-tags.md ...blob/main/articles/azure-signalr/howto-service-tags.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes how to configure service tags using the Azure Portal UI, which is a graphical interface commonly associated with Windows environments. There are no command-line examples (such as Azure CLI, PowerShell, or Bash scripts), and no mention of Linux-specific tools or workflows. This approach implicitly favors Windows users and omits guidance for users who prefer or require Linux-based or cross-platform automation.
Recommendations
  • Add equivalent Azure CLI examples for all configuration steps, as Azure CLI is cross-platform and widely used on Linux.
  • If PowerShell examples are provided in other documentation, ensure Bash or Azure CLI equivalents are also included.
  • Explicitly mention that all steps can be performed from any OS using the Azure Portal, but provide links or examples for command-line automation.
  • Include a section or callout for Linux users, highlighting any differences or additional considerations.
  • Ensure screenshots and UI references are supplemented with command-line instructions for parity.
GitHub Create Pull Request
Azure Signalr https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/howto-use-managed-identity.md ...n/articles/azure-signalr/howto-use-managed-identity.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows by exclusively referencing the Azure portal (a web-based GUI) and not providing any command-line examples, such as Azure CLI or PowerShell. There are no Linux-specific instructions or examples, and no mention of how to perform these tasks from a Linux environment. The lack of CLI examples particularly impacts Linux users, who often prefer or require command-line interfaces over GUIs.
Recommendations
  • Add Azure CLI examples for all major tasks (adding managed identities, configuring upstream settings, enabling authentication, etc.), as the CLI is cross-platform and widely used on Linux.
  • Explicitly mention that the Azure portal is accessible from any OS, but provide alternative instructions for users who prefer or require command-line tools.
  • If PowerShell is referenced in other related documentation, ensure that equivalent Azure CLI (bash-friendly) examples are always provided.
  • Include a section or callout noting that all features are available via CLI/automation, with links to relevant scripts or documentation.
  • Where screenshots are used, consider including CLI output or code blocks to supplement GUI steps.
GitHub Create Pull Request
Azure Signalr https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-overview.md ...s/blob/main/articles/azure-signalr/signalr-overview.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by emphasizing ASP.NET Core and ASP.NET (both traditionally associated with Windows development) as the primary server-side frameworks for Azure SignalR Service. There is no mention of Linux-based server frameworks, nor are there examples or references to non-Windows development environments. The documentation also lacks explicit Linux or cross-platform setup or usage examples, which may leave Linux users underserved.
Recommendations
  • Include explicit references to Linux and cross-platform server environments (e.g., running ASP.NET Core on Linux, using Docker, or deploying on Linux-based Azure App Services).
  • Provide examples or links for setting up and using Azure SignalR Service from Linux environments, including command-line instructions for both Windows (PowerShell/CMD) and Linux (Bash).
  • Highlight cross-platform compatibility of ASP.NET Core and SignalR, and clarify that development and hosting are supported on Linux, macOS, and Windows.
  • Mention and provide examples for non-.NET server-side frameworks or languages (such as Node.js, Java, or Python) where possible, to broaden the appeal and utility for non-Windows developers.
GitHub Create Pull Request
Azure Signalr https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-quickstart-azure-functions-java.md ...ure-signalr/signalr-quickstart-azure-functions-java.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page is mostly cross-platform in its language and instructions, but it exhibits subtle Windows bias by referencing the Azure Storage Emulator (which is Windows-only) without mentioning or prioritizing its cross-platform replacement, Azurite. There are no explicit Linux/macOS-specific instructions or troubleshooting notes, and no shell or command-line examples that are unique to Linux/macOS. The documentation does not provide PowerShell-specific commands or Windows command prompt examples, but it does reference a Windows-only tool as the default for local storage emulation.
Recommendations
  • Replace references to 'Azure Storage Emulator' with 'Azurite', which is cross-platform and recommended for all OSes.
  • Explicitly mention that all CLI commands (e.g., mvn, func) work on Windows, macOS, and Linux, and note any OS-specific prerequisites or differences.
  • Add troubleshooting notes or links for common Linux/macOS issues (such as file permissions, path separators, or Java installation).
  • If screenshots or UI steps are shown, ensure they are not Windows-only, or provide equivalent Linux/macOS visuals or notes.
  • Where possible, provide parity in instructions for all major platforms, especially for local development tools and environment setup.
GitHub Create Pull Request
Azure Signalr https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-howto-scale-multi-instances.md ...s/azure-signalr/signalr-howto-scale-multi-instances.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides command-line configuration examples using 'dotnet user-secrets set' and references to 'web.config', both of which are more familiar to Windows users. There are no explicit Linux or cross-platform shell examples (e.g., bash), nor is there mention of Linux-specific configuration files or patterns. The documentation does not clarify if the commands or configuration steps differ on Linux, and it omits any Linux shell equivalents or guidance for Linux-based deployments.
Recommendations
  • Add explicit bash/zsh shell examples for setting environment variables or secrets, especially for 'dotnet user-secrets set', to show parity with Windows cmd usage.
  • Clarify that 'dotnet user-secrets' works cross-platform, or provide alternative instructions for Linux environments if needed.
  • Include examples of configuring connection strings via environment variables, which is a common pattern on Linux and in containerized deployments.
  • Mention and provide samples for using 'appsettings.json' (already referenced in some sections) as the primary configuration file, which is cross-platform.
  • When referencing 'web.config', note that this is specific to IIS/Windows hosting, and provide guidance for equivalent configuration on Linux (e.g., using environment variables or appsettings.json).
  • Ensure that all command-line instructions are either cross-platform or have both Windows and Linux/macOS variants.
GitHub Create Pull Request
Azure Signalr https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/howto-use-managed-identity.md ...n/articles/azure-signalr/howto-use-managed-identity.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using the Azure portal for all configuration steps, without providing any command-line examples (such as Azure CLI or PowerShell). While the Azure portal is cross-platform, the lack of CLI examples means users on Linux or those preferring automation/scripting are not served. There are no Linux-specific instructions or examples, and no mention of Linux tools or shell commands.
Recommendations
  • Add Azure CLI examples for all configuration steps (e.g., adding managed identities, configuring upstream settings, setting Key Vault permissions).
  • Include PowerShell examples as an option, but ensure Azure CLI (which is cross-platform) is presented first or alongside.
  • Explicitly mention that all steps can be performed from Linux, macOS, or Windows using the CLI, and provide sample commands.
  • Where screenshots are used, consider including CLI output or code blocks to improve accessibility for non-Windows users.
  • Review for any UI-specific instructions that may differ between OSes and clarify as needed.
GitHub Create Pull Request
Azure Signalr Authorize access with Microsoft Entra ID for Azure SignalR Service ...lr/signalr-concept-authorize-azure-active-directory.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits mild Windows bias by referencing Microsoft-specific tools and patterns, such as Microsoft Entra ID and Azure RBAC, which are most commonly managed via PowerShell and Azure CLI. The only explicit tool mentioned for cross-tenant provisioning is 'msgraph-powershell', with no Linux/macOS alternatives or CLI examples provided. There are no explicit Linux/macOS instructions or examples, and the documentation assumes familiarity with Microsoft-centric workflows.
Recommendations
  • Provide Azure CLI examples alongside PowerShell instructions for all provisioning and configuration steps.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI or REST API.
  • Link to cross-platform guides for managing Azure resources and Microsoft Entra ID.
  • Add notes or examples for Linux/macOS users where PowerShell is referenced, including installation instructions or alternatives.
GitHub Create Pull Request
Azure Signalr Configure a Custom Domain for Azure SignalR Service ...lob/main/articles/azure-signalr/howto-custom-domain.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally maintains cross-platform neutrality, but in the 'Verify a custom domain' section, PowerShell/Windows examples are presented before Bash/Linux equivalents. The PowerShell example uses 'curl.exe', which is specific to Windows environments, indicating a slight Windows-first bias. However, Bash/cURL examples are also provided, ensuring Linux/macOS users are not excluded.
Recommendations
  • Present Bash/Linux examples before or alongside PowerShell/Windows examples to avoid implicit prioritization.
  • Use platform-neutral command syntax (e.g., 'curl' instead of 'curl.exe') in examples where possible.
  • Explicitly state that both Windows and Linux/macOS are supported and provide parity in example coverage.
  • Consider adding macOS-specific notes if there are differences in command usage or expected output.
GitHub Create Pull Request
Azure Signalr Configure a Custom Domain for Azure SignalR Service ...lob/main/articles/azure-signalr/howto-custom-domain.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both PowerShell (Windows) and Bash (Linux/macOS) examples for verifying the custom domain with cURL, but the PowerShell example is presented first. The use of 'curl.exe' in the PowerShell example is a Windows-specific pattern. However, the rest of the documentation is largely platform-neutral, focusing on Azure Portal UI and general concepts.
Recommendations
  • Present Bash (Linux/macOS) and PowerShell examples side-by-side or alternate which is shown first to avoid implicit prioritization.
  • Clarify that 'curl.exe' is used in Windows PowerShell, while 'curl' is standard on Linux/macOS.
  • Where possible, provide CLI examples using Azure CLI (az) commands, which are cross-platform.
  • Explicitly mention that all portal steps are identical across platforms.
GitHub Create Pull Request
Azure Signalr Troubleshooting practice for Azure SignalR Service ...les/azure-signalr/signalr-howto-troubleshoot-method.md
Low Priority View Details →
Scanned: 2026-01-13 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 mild Windows bias in several areas: Windows tools (Fiddler) are mentioned before Linux alternatives (tcpdump), and some logging/tracing instructions reference Windows-specific platforms (Windows Phone 8, Windows desktop apps) without equivalent Linux/macOS guidance. There is also a tendency to present Windows-centric examples and tools first, and some sections lack explicit Linux/macOS instructions, especially for ASP.NET SignalR logging/tracing.
Recommendations
  • Present Linux/macOS tools (e.g., tcpdump, browser dev tools) alongside or before Windows tools like Fiddler.
  • Add explicit instructions and examples for enabling logging/tracing on Linux/macOS platforms, especially for ASP.NET SignalR (e.g., where to place config files, how to access logs).
  • Avoid referencing Windows-only platforms (e.g., Windows Phone 8) without noting Linux/macOS equivalents or alternatives.
  • Ensure all troubleshooting steps and examples are platform-agnostic or provide parity for Linux/macOS users.
GitHub Create Pull Request
Azure Signalr https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/includes/signalr-add-role-assignments.md ...azure-signalr/includes/signalr-add-role-assignments.md
Low Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page presents the Azure portal (a GUI, often associated with Windows environments) as the primary method for role assignment, with Azure PowerShell listed before Azure CLI in the 'To learn more' section. This ordering may subtly prioritize Windows-centric tools and workflows over cross-platform or Linux-native options.
Recommendations
  • When listing command-line tools, mention Azure CLI before or alongside Azure PowerShell, as Azure CLI is cross-platform and widely used on Linux.
  • Include explicit examples or references for both Azure PowerShell and Azure CLI in the main instructions, not just in the 'To learn more' section.
  • Clarify that the Azure portal and all listed tools are cross-platform where applicable, to avoid the impression that the instructions are Windows-specific.
  • If screenshots or step-by-step instructions are provided for PowerShell or the portal, consider also providing equivalent CLI or Linux terminal examples.
GitHub Create Pull Request
← Previous Page 3 of 4 Next →