Sad Tux - Windows bias detected
This page contains Windows bias

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.

Bias Analysis

Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation presents deployment options in the order: Portal, PowerShell, and then CLI. PowerShell is given equal prominence to CLI, and the CLI section references Git Bash (included in Git for Windows) as the example Bash shell, rather than a native Linux shell. There are no explicit Linux-specific instructions or examples, and the CLI instructions are written generically, but the only shell mentioned is Git Bash for Windows. This subtly prioritizes Windows tools and environments.
Recommendations
  • Explicitly mention native Linux/macOS shells (e.g., bash, zsh) as supported environments for Azure CLI, not just Git Bash for Windows.
  • Add a note or section confirming that all CLI commands work natively on Linux/macOS terminals, and provide any Linux/macOS-specific prerequisites if needed.
  • When listing deployment options, consider rotating or randomizing the order, or explicitly stating that all platforms are supported equally.
  • Provide links or references to installing Azure CLI on Linux/macOS, not just a generic install link.
  • If referencing PowerShell, clarify that PowerShell Core is cross-platform, or provide Bash equivalents for any PowerShell-specific scripts where possible.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-01-14 00:00 #250 in_progress Clean Clean
2026-01-13 00:00 #246 completed Clean Clean
2026-01-12 00:00 #243 cancelled Biased Biased
2026-01-11 00:00 #240 completed Biased Biased
2026-01-10 00:00 #237 completed Biased Biased
2026-01-09 00:34 #234 completed Biased Biased
2026-01-08 00:53 #231 completed Biased Biased
2026-01-06 18:15 #225 cancelled Clean Clean
2025-08-17 00:01 #83 cancelled Clean Clean
2025-07-13 21:37 #48 completed Clean Clean
2025-07-09 13:09 #3 cancelled Clean Clean
2025-07-08 04:23 #2 cancelled Biased Biased

Flagged Code Snippets

---

## Clean up resources

When it's no longer needed, delete the resource group, which deletes the resources in the resource group.

# [Portal](#tab/azure-portal)

1. In the [Azure portal](https://portal.azure.com), search for and select **Resource groups**.

2. In the resource group list, choose the name of your resource group.

3. In the **Overview** page of your resource group, select **Delete resource group**.

4. In the confirmation dialog box, type the name of your resource group, and then select **Delete**.

# [PowerShell](#tab/PowerShell)

---

> [!NOTE]
> The deployment may take a few minutes to complete. Note the names for the Azure SignalR Service and the resource group, which you use to review the deployed resources later.

## Review deployed resources

# [Portal](#tab/azure-portal)

Follow these steps to see an overview of your new Azure SignalR Service:

1. In the [Azure portal](https://portal.azure.com), search for and select **SignalR**.

2. In the SignalR list, select your new service. The **Overview** page for the new Azure SignalR Service appears.

# [PowerShell](#tab/PowerShell)

Run the following interactive code to view details about your Azure SignalR Service. You have to enter the name of the new service and the resource group.