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 26-33 of 33 flagged pages
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes configuration steps using the Azure Portal GUI, which is most familiar to Windows users and does not provide any command-line examples (such as Azure CLI, PowerShell, or bash scripts). There are no Linux-specific instructions or parity for users who prefer or require command-line or non-GUI workflows, which are common in Linux environments.
Recommendations
- Add Azure CLI examples for configuring network security group rules using service tags, as Azure CLI is cross-platform and widely used on Linux.
- If PowerShell examples are provided, ensure Azure CLI/bash equivalents are also included and presented with equal prominence.
- Explicitly mention that the Azure Portal is web-based and platform-agnostic, but provide alternative instructions for users who prefer command-line tools.
- Include references or links to documentation for automating these tasks on Linux systems.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by referencing the Azure portal and Visual Studio as primary configuration and authentication methods, with no explicit Linux or cross-platform command-line examples (e.g., Azure CLI or Bash scripting). There are no Linux-specific instructions or examples, and the only local development authentication methods mentioned are Visual Studio, Azure CLI, and Azure PowerShell, with Visual Studio listed first. No Linux shell or editor is referenced, and no explicit Bash or cross-platform CLI commands are provided for configuring managed identities or role assignments.
Recommendations
- Add explicit Azure CLI examples for configuring managed identities and role assignments, and show their usage in both Windows and Linux shells.
- Include Bash shell examples for setting environment variables and configuring local.settings.json, highlighting cross-platform compatibility.
- Mention and provide examples for common Linux editors (e.g., nano, vim) when editing configuration files.
- Clarify that all configuration steps can be performed on Linux, macOS, or Windows, and avoid listing Visual Studio or Azure portal as the only or primary methods.
- When referencing authentication in local development, mention VS Code and cross-platform tools alongside Visual Studio.
- Ensure that any PowerShell or Windows-specific instructions are accompanied by equivalent Bash/Linux commands.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-quickstart-azure-functions-csharp.md
...e-signalr/signalr-quickstart-azure-functions-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While most commands are cross-platform (using bash), the prerequisites and tooling references (such as Azure Functions Core Tools and Visual Studio Code) do not explicitly mention Linux or macOS compatibility, nor do they provide Linux-specific instructions or troubleshooting. The storage emulator reference points to Azurite, which is cross-platform, but does not clarify installation steps for Linux. The documentation also omits explicit Linux/macOS examples for environment setup, storage emulator usage, and does not mention alternative editors or shell environments.
Recommendations
- Explicitly state that Azure Functions Core Tools and Visual Studio Code are available on Linux and macOS, and provide download links for those platforms.
- Add Linux/macOS-specific setup instructions, including installation commands for Azure Functions Core Tools and Azurite (e.g., using npm or package managers).
- Include troubleshooting notes or links for common Linux/macOS issues (such as permissions, path differences, or shell compatibility).
- Mention alternative editors (such as Vim, Emacs, or JetBrains Rider) to avoid implicit bias toward Visual Studio Code.
- When referencing the storage emulator, provide clear instructions for installing and running Azurite on Linux/macOS, and clarify that it is the recommended cross-platform solution.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-quickstart-dotnet-core.md
...ticles/azure-signalr/signalr-quickstart-dotnet-core.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation avoids explicit Windows bias in most areas, emphasizing cross-platform tools like the .NET Core CLI and Visual Studio Code, which are available on Windows, macOS, and Linux. However, there are subtle 'windows_first' and 'missing_linux_example' biases: the documentation does not provide any Linux- or macOS-specific instructions, terminal commands, or screenshots, and all output examples (e.g., localhost URL, output logs) are generic or implicitly Windows-centric. There are no mentions of Linux-specific tools, nor are there any terminal/shell commands shown in Bash or zsh, and the resource cleanup steps reference the Azure Portal UI only, not CLI or cross-platform alternatives.
Recommendations
- Explicitly mention and provide example commands for Linux/macOS terminals (e.g., Bash/zsh) where appropriate, especially for running dotnet CLI commands.
- Include sample output from Linux/macOS terminals to demonstrate parity.
- Add instructions for using the Azure CLI (az) to create and delete resources, as an alternative to the Azure Portal UI.
- Where screenshots are shown, consider including at least one from a Linux environment.
- If any troubleshooting steps are OS-specific, call out differences for Linux/macOS users.
Azure Signalr
Configure a Custom Domain for Azure SignalR Service
...lob/main/articles/azure-signalr/howto-custom-domain.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both PowerShell (Windows) and Bash (Linux/macOS) examples for verifying the custom domain with curl, but the PowerShell example is shown first. There are no other notable Windows-specific tools, patterns, or examples; most instructions are platform-neutral and focus on Azure Portal UI. There is no evidence of missing Linux examples or exclusive use of Windows tools.
Recommendations
- Present Bash (Linux/macOS) and PowerShell (Windows) examples side-by-side, or alternate which is shown first to avoid implicit prioritization.
- Explicitly state that all command-line examples work on both Windows and Linux/macOS, where applicable.
- If possible, include screenshots or instructions for Azure CLI (cross-platform) where relevant, in addition to portal steps.
Azure Signalr
Configure a Custom Domain for Azure SignalR Service
...lob/main/articles/azure-signalr/howto-custom-domain.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally maintains cross-platform parity, but in the 'Verify a custom domain' section, the PowerShell/Windows example is presented before the Bash/Linux example. No other sections show Windows-only instructions, tools, or patterns; all portal steps are OS-agnostic, and the only command-line example is provided for both platforms.
Recommendations
- Present Bash/Linux examples before or alongside PowerShell/Windows examples to avoid implicit prioritization.
- Ensure future command-line examples always include both Windows and Linux/macOS variants, and alternate their order across documentation pages.
- Explicitly state that all steps can be performed on any OS unless a step is truly OS-specific.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/howto-disable-local-auth.md
...ain/articles/azure-signalr/howto-disable-local-auth.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides instructions for disabling local authentication in Azure SignalR Service using the Azure Portal, ARM templates, and Azure Policy, but does not include any command-line examples (such as Azure CLI, PowerShell, or Bash scripts). There is no explicit Windows bias in the form of Windows/Powershell-specific tools or instructions, but the lack of CLI examples means Linux users do not see parity with GUI or template-based instructions.
Recommendations
- Add Azure CLI examples for disabling local authentication, as Azure CLI is cross-platform and widely used on Linux.
- If relevant, provide Bash script snippets for automating the process.
- Ensure that any command-line instructions are presented in a platform-neutral way, or include both PowerShell and Bash/CLI equivalents if scripting is necessary.
- Explicitly mention that the ARM template method can be deployed using Azure CLI or Azure PowerShell, and provide example commands for both.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-reference-data-plane-rest-api.md
...azure-signalr/signalr-reference-data-plane-rest-api.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples, but it also does not include any Windows- or PowerShell-specific instructions, tools, or patterns. However, there is a lack of parity in that no Linux or cross-platform command-line examples (such as curl, bash, or CLI usage) are provided for interacting with the REST API. All sample references are either generic or point to .NET-based repositories, which may implicitly favor Windows environments but are not explicitly Windows-centric.
Recommendations
- Add explicit examples of making REST API calls using cross-platform tools such as curl or httpie.
- Include sample scripts for both Windows (PowerShell) and Linux/macOS (bash) environments to demonstrate authentication and API usage.
- Clarify that the REST API can be accessed from any platform and provide links or code samples for popular Linux tools.
- If referencing .NET samples, also mention alternative SDKs or libraries available for other platforms/languages.