Azure Signalr
156
Total Pages
135
Linux-Friendly Pages
21
Pages with Bias
13.5%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
33 issues found
Showing 1-25 of 33 flagged pages
Azure Signalr
Develop with ASP.NET - Azure SignalR Service
...in/articles/azure-signalr/signalr-quickstart-dotnet.md
High Priority
View Details →
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 setup and run instructions assume Windows, with no mention of Linux/macOS alternatives. Package installation uses PowerShell, and there are no examples or guidance for Linux users (e.g., using VS Code, Mono, or .NET Core on Linux). The prerequisites and workflow are Windows-centric, creating friction for non-Windows users.
Recommendations
- Add instructions for setting up and running the sample on Linux/macOS, including using .NET Core/Mono and editors like VS Code.
- Provide package installation commands for Linux/macOS (e.g., using dotnet CLI or NuGet CLI, not just PowerShell).
- Clarify which steps are Windows-specific and offer alternatives for other platforms.
- Include troubleshooting tips for Linux/macOS environments.
- List cross-platform prerequisites (e.g., .NET Core SDK) and mention compatibility.
Create Pull Request
Azure Signalr
Develop with ASP.NET - Azure SignalR Service
...in/articles/azure-signalr/signalr-quickstart-dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily oriented towards Windows development environments. Prerequisites list only Visual Studio (Windows-only) and .NET Framework (not cross-platform), with no mention of Linux or macOS alternatives. Instructions for running and configuring the sample app assume Visual Studio and Windows tooling (e.g., NuGet Package Manager Console, web.config), and PowerShell is used for package installation. No Linux/macOS development workflows, editors, or package management alternatives are provided.
Recommendations
- Add instructions for developing and running the sample on Linux/macOS, such as using Visual Studio Code or JetBrains Rider.
- Include .NET Core or ASP.NET Core equivalents, which are cross-platform, and clarify which steps apply to non-Windows environments.
- Provide alternative package installation commands (e.g., using dotnet CLI: 'dotnet add package Microsoft.Azure.SignalR.AspNet').
- Mention configuration file differences for Linux/macOS (e.g., appsettings.json vs web.config).
- Explicitly state platform limitations and offer guidance for cross-platform development where possible.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/concept-connection-string.md
...in/articles/azure-signalr/concept-connection-string.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page primarily uses .NET-centric and Windows-oriented configuration patterns (such as appsettings.json, dotnet user-secrets, and double-underscore environment variable conventions) without providing explicit Linux/Unix examples or mentioning Linux-native tools. The only CLI example is Azure CLI, which is cross-platform, but all configuration and code examples assume a .NET/Windows development environment. There are no bash, shell, or Linux-specific configuration examples, and the secret management tools referenced are .NET/Windows-first.
Recommendations
- Add explicit Linux/Unix shell examples for setting environment variables (e.g., export Azure__SignalR__ConnectionString=...) and managing secrets.
- Mention and provide examples for Linux-native secret management tools (such as using environment variables in bash, or integrating with Linux keyrings or Azure Key Vault CLI).
- Clarify that the .NET secret manager and appsettings.json are not exclusive to Windows, but also provide parity examples for Node.js, Python, or Java apps on Linux.
- When listing configuration options, avoid assuming a Windows-first environment; present cross-platform approaches first or in parallel.
- Include a section or callout for configuring connection strings in common Linux deployment scenarios (e.g., Docker containers, systemd services, or Kubernetes pods).
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-concept-serverless-development-config.md
...gnalr/signalr-concept-serverless-development-config.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a bias towards Windows by primarily referencing Azure Portal (a web UI often associated with Windows-centric workflows), omitting explicit Linux or cross-platform command-line examples for configuration and deployment, and mentioning CORS configuration limitations for Linux Consumption plans only as a note. There are no Bash, CLI, or Linux-native tool examples for common tasks such as CORS configuration, deployment, or authentication setup. The guidance for enabling CORS in the cloud refers only to the Azure Portal UI, and the workaround for Linux plans is to use Azure API Management, without showing how to use Azure CLI or ARM templates. All code samples are in C# (a language more common on Windows), and there are no examples for Bash, PowerShell, or Linux shell environments.
Recommendations
- Add Azure CLI and/or Azure PowerShell examples for common configuration tasks (e.g., enabling CORS, setting authentication) alongside or before portal-based instructions.
- Provide explicit instructions or scripts for configuring CORS and authentication on Linux (Consumption and other plans), using cross-platform tools.
- Include deployment examples using Bash or cross-platform shell scripts, not just references to the Azure Portal.
- Ensure that any limitations or differences for Linux plans are clearly documented with actionable alternatives (e.g., ARM/Bicep templates, CLI commands).
- Add code samples in additional languages (e.g., JavaScript, Python) where possible, and clarify that C# is used for demonstration but alternatives exist.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-howto-reverse-proxy-overview.md
.../azure-signalr/signalr-howto-reverse-proxy-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias towards Windows/Azure-native tools by exclusively referencing Azure Application Gateway and Azure API Management as reverse proxy solutions, without mentioning or providing examples for popular Linux-based reverse proxies such as NGINX or Apache. No Linux-specific configuration examples or guidance are provided, and the only reverse proxy examples are Azure-centric, which are more commonly used in Windows environments. This may leave Linux users without clear guidance for integrating Azure SignalR with widely-used open-source reverse proxies.
Recommendations
- Add configuration examples for popular Linux-based reverse proxies such as NGINX and Apache, including sample config snippets for HOST header rewriting and WebSocket/SSE support.
- Explicitly mention Linux-compatible reverse proxy solutions alongside Azure-native options, and provide links to relevant documentation.
- Ensure that Linux examples are presented with parity to Azure-native/Windows tools, either by alternating order or by grouping all supported reverse proxies together.
- Include troubleshooting tips or caveats specific to Linux environments (e.g., SELinux, systemd socket activation, common pitfalls with NGINX/Apache and WebSockets).
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides detailed instructions for moving an Azure SignalR resource using the Azure portal and Azure PowerShell, with all command-line examples using PowerShell syntax and Windows-specific tools (e.g., Notepad). There are no examples for Linux users (e.g., Azure CLI, Bash, or cross-platform editors), and PowerShell is presented as the only scripting option, which may disadvantage users on Linux or macOS.
Recommendations
- Add equivalent Azure CLI (az) command examples for exporting, editing, and deploying Resource Manager templates, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Replace or supplement references to Windows-specific tools like Notepad with cross-platform editors (e.g., 'use your preferred text editor such as nano, vim, or Visual Studio Code').
- Explicitly mention that the PowerShell examples are for Windows and provide Bash/Linux alternatives where possible.
- Reorder or parallelize sections so that Azure CLI and PowerShell instructions are presented side-by-side or with equal prominence.
- Add a note at the beginning clarifying that the instructions apply to all platforms and that both PowerShell and CLI options are available.
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
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Aspnet Heavy
Summary
The documentation page exhibits a bias toward Windows by focusing primarily on ASP.NET Core and ASP.NET (which are traditionally associated with Windows development), mentioning them exclusively as server-side options. There are no examples or mentions of Linux-specific frameworks, tools, or deployment scenarios. The documentation does not provide parity for Linux users, such as examples using Node.js, Python, or Java server-side implementations, nor does it mention cross-platform development or deployment considerations.
Recommendations
- Include examples and references for using Azure SignalR Service with cross-platform frameworks such as Node.js, Python, or Java on Linux.
- Mention and link to documentation for deploying SignalR applications on Linux servers or containers.
- Balance the server-side language and framework discussion by highlighting non-.NET options and their compatibility with Azure SignalR Service.
- Add explicit statements or sections clarifying that Azure SignalR Service is platform-agnostic and can be used with both Windows and Linux environments.
- Provide sample code snippets or tutorials for Linux-based development and deployment scenarios.
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 →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation shows a bias toward Windows environments. Troubleshooting steps and examples reference Windows-specific tools (e.g., Fiddler, Performance Monitor), Visual Studio UI, and .NET/ASP.NET patterns. There are no Linux-specific equivalents or instructions for common tasks like debugging, viewing network traffic, or monitoring server metrics. Linux and cross-platform scenarios are not addressed, and Windows tools are mentioned exclusively or before any alternatives.
Recommendations
- Provide Linux equivalents for Windows tools mentioned, such as suggesting Wireshark or tcpdump for network traffic analysis, and dotnet-trace or PerfView (on Linux) for diagnostics.
- Include instructions for enabling and viewing logs, debugging, and monitoring on Linux-based deployments (e.g., using journalctl, systemd, or container logs).
- When referencing Visual Studio or Windows UI steps (e.g., 'Uncheck Just My Code'), add corresponding steps for VS Code, JetBrains Rider, or command-line debugging tools.
- When mentioning Fiddler, also mention cross-platform alternatives like mitmproxy or Wireshark.
- For performance monitoring, reference tools like top, htop, or dotnet-counters for Linux environments.
- Add explicit notes or sections for Linux users, ensuring parity in troubleshooting guidance and code samples.
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 →
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 before or more prominently than Linux equivalents. Some examples and logging instructions (web.config, Windows Phone 8 tracing) are Windows-specific, while Linux alternatives (tcpdump) are present but less emphasized. There are missing Linux-specific examples for some logging/tracing scenarios, and overall, Windows-centric patterns appear first or exclusively in several sections.
Recommendations
- Ensure Linux tools (e.g., tcpdump, journalctl, syslog) are mentioned with equal prominence and ordering as Windows tools like Fiddler.
- Provide explicit Linux/macOS examples for enabling server-side and client-side logging, including configuration file samples for common Linux hosting scenarios.
- Avoid Windows-only references (e.g., Windows Phone 8, web.config) or supplement with Linux equivalents (e.g., appsettings.json, environment variables).
- Add troubleshooting steps and examples for Linux environments, such as using systemd logs, container logs, or Linux desktop clients.
- Review all links and referenced guides to ensure Linux parity in diagnostic and troubleshooting instructions.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows environments, particularly in the legacy ASP.NET SignalR section. It exclusively uses PowerShell/Package Manager Console commands for SDK installation and references the 'web.config' file for configuration, both of which are Windows-centric tools and patterns. There are no Linux/macOS equivalents or cross-platform alternatives provided, and no mention of using the .NET CLI for package installation in the legacy section. The ASP.NET Core section is more neutral, using 'dotnet' CLI commands, but the legacy section lacks Linux parity.
Recommendations
- For SDK installation in the legacy ASP.NET SignalR section, provide cross-platform .NET CLI commands (e.g., 'dotnet add package') alongside or instead of PowerShell/Package Manager Console commands.
- Mention configuration alternatives for non-Windows environments, such as using environment variables or appsettings.json, instead of only referencing 'web.config'.
- Explicitly state that the instructions apply to Windows and provide guidance or links for Linux/macOS users where applicable.
- Review all code and configuration samples to ensure they are platform-agnostic or provide platform-specific alternatives as needed.
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
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation references the Azure Storage Emulator, which is a Windows-only tool, without mentioning or prioritizing its cross-platform replacement, Azurite. There are no explicit Linux/macOS-specific instructions or examples for setting up storage emulation or environment variables, and the only emulator mentioned is not available on Linux. This may confuse or block Linux users. The overall instructions are mostly cross-platform, but the storage setup step is Windows-biased.
Recommendations
- Replace references to 'Azure Storage Emulator' with 'Azurite', which is cross-platform and recommended by Microsoft for local storage emulation.
- Provide explicit instructions or links for installing and running Azurite on Linux and macOS, not just Windows.
- Clarify that the quickstart works on all platforms by ensuring all tools and steps are available and documented for Linux/macOS.
- If any commands or environment variable settings differ between platforms (e.g., export vs. set), provide both examples.
- Review and update any screenshots or UI references that may be Windows-specific to ensure parity.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias by listing PowerShell instructions before CLI/Bash equivalents, providing detailed PowerShell examples, and referencing Windows-centric tools (e.g., Git Bash via Git for Windows) in the prerequisites. While Azure CLI (cross-platform) examples are present, the structure and language prioritize Windows and PowerShell users, and Linux-native tools or shells are not mentioned.
Recommendations
- Alternate the order of PowerShell and CLI sections or present CLI (Bash) instructions first in some sections to avoid always prioritizing Windows tools.
- Explicitly mention support for Linux and macOS in the prerequisites, including native Bash shells (e.g., Ubuntu Terminal, macOS Terminal) rather than only referencing Git Bash for Windows.
- Add notes clarifying that Azure CLI commands work natively on Linux and macOS, not just in Git Bash on Windows.
- Ensure parity in detail and explanation between PowerShell and CLI sections.
- Where possible, provide examples or troubleshooting tips specific to Linux environments (e.g., common permission issues, package managers for installing Azure CLI).
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-quickstart-dotnet.md
...in/articles/azure-signalr/signalr-quickstart-dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. It exclusively references Visual Studio (a Windows-centric IDE), .NET Framework (not .NET Core/.NET 5+), and provides only PowerShell/NuGet Package Manager Console commands for package installation. There are no instructions or examples for Linux users (e.g., using VS Code, JetBrains Rider, or CLI tools), nor are there any bash or cross-platform command examples. The prerequisites and workflow assume a Windows environment throughout.
Recommendations
- Add instructions for Linux and macOS users, including using .NET Core or later (which is cross-platform) instead of .NET Framework.
- Provide alternative steps for using VS Code or JetBrains Rider, and for running the application via the dotnet CLI.
- Include bash/zsh shell commands for package installation (e.g., 'dotnet add package') alongside PowerShell examples.
- Clarify which steps are Windows-specific and offer equivalent Linux/macOS workflows where possible.
- Mention cross-platform compatibility and test the sample on Linux to ensure parity.
Azure Signalr
Move an Azure SignalR resource to another region
...les/azure-signalr/signalr-howto-move-across-regions.md
Medium Priority
View Details →
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 exclusively uses Windows-centric tools and commands (e.g., notepad, PowerShell cmdlets) and does not mention or provide examples for Linux/macOS users (such as Azure CLI or cross-platform editors). The order of examples also places PowerShell before any mention of Linux alternatives, and no Linux/macOS-specific guidance is given.
Recommendations
- Add equivalent instructions using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Replace or supplement 'notepad' with cross-platform editors (e.g., 'code', 'nano', 'vim', or 'your preferred editor').
- Explicitly mention that PowerShell Core is available on Linux/macOS, or provide guidance for installing and using it.
- Include Linux/macOS-specific notes for file paths, command syntax, and environment setup.
- Present Azure CLI and PowerShell examples side-by-side, or at least mention both approaches in the prerequisites.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation shows bias towards Windows in the legacy ASP.NET SignalR section, where the SDK installation is demonstrated only using the Package Manager Console (PowerShell), a Windows-specific tool. There is no mention of Linux/macOS equivalents (such as dotnet CLI or NuGet CLI) for installing the package. Additionally, the use of web.config for connection strings is a Windows/IIS-centric pattern, with no guidance for Linux-hosted ASP.NET applications. The ASP.NET Core section is more cross-platform, using dotnet CLI and environment variables, but the legacy section is Windows-first and omits Linux/macOS instructions.
Recommendations
- Add instructions for installing the SignalR Service SDK using cross-platform tools such as dotnet CLI or NuGet CLI in the legacy ASP.NET SignalR section.
- Mention how to configure connection strings for Linux-hosted ASP.NET applications, such as using environment variables or appsettings.json, if supported.
- Where possible, avoid referencing Windows-only tools (like Package Manager Console) as the sole method for key steps.
- Clarify any platform-specific requirements or limitations for legacy ASP.NET SignalR on Linux/macOS.
Azure Signalr
Authorize access with Microsoft Entra ID for Azure SignalR Service
...lr/signalr-concept-authorize-azure-active-directory.md
Medium Priority
View Details →
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 platform-neutral but are most commonly managed using Windows-centric tools. The only explicit tooling link provided for cross-tenant enterprise app creation is to 'msgraph-powershell', a Windows/PowerShell tool, with no mention of Linux/macOS alternatives or CLI equivalents. There are no explicit Linux/macOS examples or guidance, and Windows/PowerShell tooling is mentioned first and exclusively.
Recommendations
- Provide equivalent Azure CLI or REST API instructions for cross-tenant enterprise app creation and management, suitable for Linux/macOS users.
- Include examples or links for managing Microsoft Entra ID and Azure RBAC using platform-neutral tools (e.g., Azure CLI, REST API).
- When referencing PowerShell, also mention or link to Azure CLI or other cross-platform alternatives.
- Add explicit notes or sections for Linux/macOS users where Windows/PowerShell tools are referenced.
Azure Signalr
Troubleshooting guide for Azure SignalR Service
...cles/azure-signalr/signalr-howto-troubleshoot-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Troubleshooting steps and examples are almost exclusively focused on ASP.NET/ASP.NET Core (C#), which are most commonly deployed on Windows. Tools like Fiddler (Windows-only) are recommended for network traffic inspection, and performance monitoring references are primarily for Windows environments (e.g., Performance Monitor, EventSource 'Microsoft-Windows-DotNETRuntime'). There are no explicit Linux/macOS equivalents or instructions for common tasks such as enabling server-side logging, debugging, or viewing outgoing requests from non-Windows environments. Linux tools and patterns (e.g., tcpdump, Wireshark, dotnet-trace, journalctl) are not mentioned, and Windows-centric troubleshooting steps (like modifying web.config or using ServicePointManager) are presented without Linux alternatives.
Recommendations
- Include Linux/macOS equivalents for network traffic inspection, such as tcpdump, Wireshark, or mitmproxy.
- Provide guidance for enabling server-side logging and diagnostics in Linux environments (e.g., using systemd/journalctl, dotnet-trace, or container logs).
- Mention how to debug .NET Core applications on Linux/macOS, including relevant IDEs (VS Code) and debugging tools.
- Add instructions for modifying configuration files and environment variables in Linux deployments (e.g., appsettings.json, environment variables, Docker containers) instead of only referencing web.config.
- When referencing tools (e.g., Fiddler, Performance Monitor), also list cross-platform or Linux-native alternatives.
- Ensure code samples and troubleshooting steps are not Windows-specific (e.g., avoid only referencing ServicePointManager or HTTP.SYS).
Azure Signalr
Troubleshooting practice for Azure SignalR Service
...les/azure-signalr/signalr-howto-troubleshoot-method.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation shows some Windows bias, notably in the logging section for ASP.NET SignalR, where Windows-specific tools and examples (e.g., Windows Phone 8, web.config tracing) are highlighted, and Linux/macOS equivalents are not provided. In network trace collection, Fiddler (Windows-centric) is listed before tcpdump (Linux/macOS), and some logging instructions assume Windows environments. There are references to Windows desktop apps and Windows Phone clients, but no mention of Linux desktop or mobile equivalents.
Recommendations
- Provide Linux/macOS equivalents for logging and tracing, such as instructions for configuring logging in Linux environments and using Linux-native tools.
- List cross-platform tools (e.g., tcpdump, Wireshark) before or alongside Windows tools like Fiddler.
- Include examples for Linux and macOS clients and servers, especially for .NET client logging and tracing.
- Clarify which steps are platform-agnostic and which require platform-specific instructions.
- Avoid referencing only Windows-specific platforms (e.g., Windows Phone) unless alternatives are unavailable.
Azure Signalr
Troubleshooting guide for Azure SignalR Service
...cles/azure-signalr/signalr-howto-troubleshoot-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Troubleshooting steps and code samples are almost exclusively focused on ASP.NET/ASP.NET Core (C#), which are most commonly deployed on Windows. Debugging instructions reference Visual Studio features (e.g., 'Just My Code'), and tools like Fiddler are highlighted without mention of Linux/macOS alternatives. Performance monitoring and diagnostics are described using Windows-centric tools (Performance Monitor, EventSource 'Microsoft-Windows-DotNETRuntime'), with little or no guidance for Linux/macOS environments. There are no explicit Linux/macOS code samples, nor are cross-platform patterns or tools discussed.
Recommendations
- Add troubleshooting steps and code samples for Linux/macOS environments, including guidance for running ASP.NET Core on those platforms.
- Include alternative debugging instructions for VS Code, JetBrains Rider, or command-line debuggers available on Linux/macOS.
- Mention cross-platform network monitoring tools (e.g., Wireshark, tcpdump) alongside Fiddler.
- Provide instructions for collecting diagnostics and performance metrics on Linux/macOS (e.g., dotnet-counters, dotnet-trace, systemd logs).
- Clarify which steps are platform-agnostic and which are Windows-specific, and order examples so that platform-neutral or Linux/macOS options are not always last or omitted.
Azure Signalr
Move an Azure SignalR resource to another region
...les/azure-signalr/signalr-howto-move-across-regions.md
Medium Priority
View Details →
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 command-line example section exclusively uses Azure PowerShell, which is primarily a Windows tool, and references Notepad for editing JSON files. There are no examples using cross-platform tools such as Azure CLI, nor are Linux/macOS-friendly editors or shell commands mentioned. The PowerShell section appears before any mention of alternatives, and no Linux/macOS-specific guidance is provided.
Recommendations
- Add equivalent instructions using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Suggest cross-platform editors (e.g., VS Code, nano, vim) for editing JSON files instead of Notepad.
- Explicitly mention that Azure PowerShell is available on Linux/macOS, or provide installation guidance for those platforms.
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
- Include notes or sections for Linux/macOS users, highlighting any differences or additional steps.
Azure Signalr
Troubleshooting practice for Azure SignalR Service
...les/azure-signalr/signalr-howto-troubleshoot-method.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates mild Windows bias by listing Windows tools (Fiddler) before Linux alternatives (tcpdump) when discussing network trace collection, and by referencing Windows-specific logging/tracing scenarios (Windows Phone 8, .NET client Windows desktop apps) without equivalent Linux/macOS examples. Some logging instructions (web.config, .NET desktop) are Windows-centric, and Linux/macOS users may need to infer their own approaches.
Recommendations
- Present Linux/macOS tools (e.g., tcpdump, Wireshark) alongside or before Windows tools like Fiddler.
- Include explicit Linux/macOS logging/tracing examples where only Windows scenarios are described (e.g., .NET client on Linux, ASP.NET Core on Linux).
- Clarify which instructions are cross-platform and provide platform-specific notes where necessary.
- Add links or references to Linux/macOS equivalents for Windows-only tools or configuration files (e.g., alternatives to web.config for .NET apps on Linux).
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias in the legacy ASP.NET SignalR section, where the SDK installation is shown only using the Package Manager Console (PowerShell), a Windows-specific tool. There is no mention of Linux/macOS alternatives (e.g., dotnet CLI or NuGet CLI), and the configuration examples reference web.config, which is more common in Windows/IIS deployments. The ASP.NET Core section is more cross-platform, using dotnet CLI for package installation, but the legacy section lacks Linux parity.
Recommendations
- Provide Linux/macOS-friendly installation instructions for the legacy ASP.NET SignalR SDK, such as using the NuGet CLI (nuget install) or dotnet CLI if supported.
- Mention cross-platform configuration file alternatives or clarify web.config usage for non-Windows environments.
- Add notes or examples for running legacy ASP.NET SignalR on Linux (e.g., via Mono or .NET Core where possible), or explicitly state platform limitations.
- Ensure all code and command examples are presented in a cross-platform manner, or provide both Windows and Linux/macOS alternatives.
Azure Signalr
Quickstart: Create an Azure SignalR Service - Bicep
...nalr/signalr-quickstart-azure-signalr-service-bicep.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all deployment steps, but PowerShell is featured equally alongside CLI, which may suggest a Windows bias. There is no explicit mention of Linux/macOS-specific instructions, nor are Linux shell examples (e.g., Bash) or platform-specific notes provided. The CLI examples are cross-platform, but PowerShell is Windows-centric and its inclusion without Linux alternatives may create friction for non-Windows users.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and are preferred for cross-platform usage.
- Add notes or tabs indicating which commands are platform-specific (e.g., PowerShell for Windows, Bash for Linux/macOS).
- Consider providing Bash shell examples for Linux/macOS users, especially for tasks like file handling or scripting.
- Explicitly state that PowerShell examples are intended for Windows users, and recommend CLI for Linux/macOS.
- Add troubleshooting or installation links for Azure CLI on Linux/macOS.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses the Azure Portal UI for all configuration steps and does not provide any command-line examples (such as Azure CLI or PowerShell). While this avoids explicit Windows tools, the Azure Portal UI is more commonly associated with Windows workflows and is less scriptable or automatable, which can disadvantage Linux users or those preferring CLI-based automation. There are no Linux-specific instructions or parity examples for managing identities via CLI, nor are cross-platform automation options discussed.
Recommendations
- Add Azure CLI examples for all major steps (e.g., assigning managed identities, configuring upstream settings, setting Key Vault policies). The Azure CLI is cross-platform and would benefit Linux users.
- If PowerShell examples are added, ensure Azure CLI equivalents are always present and shown first or side-by-side.
- Explicitly mention that all portal-based steps can be performed via CLI, and link to relevant CLI documentation.
- Include a section or callout for automation and scripting, referencing cross-platform tools and patterns.
- Where screenshots are used, consider adding CLI command snippets as alternatives for users who do not use the portal.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/howto-custom-domain.md
...lob/main/articles/azure-signalr/howto-custom-domain.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally uses Azure Portal UI instructions, which are cross-platform, but in the few places where command-line examples are given, the PowerShell/Windows example is presented before the Bash/Linux example. The PowerShell example uses 'curl.exe', which is specific to Windows, and the Bash example is only provided as a secondary tab. There are no Linux-specific tools or command-line patterns mentioned before their Windows equivalents.
Recommendations
- Present Bash/Linux examples before or alongside PowerShell/Windows examples, or default to Bash for cross-platform parity.
- Use cross-platform command-line tools (e.g., 'curl' instead of 'curl.exe') in examples.
- When providing tabbed examples, consider making Bash the default or at least equal in prominence to PowerShell.
- Explicitly mention that all portal-based instructions are OS-agnostic to reassure Linux users.
- Where relevant, add CLI (az cli) examples, which are cross-platform, to supplement or replace PowerShell-specific instructions.