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

Bias Types:
⚠️ powershell_heavy
⚠️ windows_first
⚠️ windows_tools
Summary:
The documentation provides parity between Azure CLI and Azure PowerShell for most operations, but consistently lists and demonstrates PowerShell (a Windows-centric tool) before CLI, and includes detailed PowerShell scripting examples. There are no Linux-specific shell (e.g., Bash) or scripting examples, and no mention of Linux-native tools or workflows. The documentation assumes familiarity with PowerShell, which is more common on Windows, and does not address Linux users directly or provide guidance for Linux environments.
Recommendations:
  • Alternate the order of CLI and PowerShell examples, or list CLI (which is cross-platform) first to avoid implicit Windows prioritization.
  • Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, and provide Bash shell examples where appropriate.
  • Add a note or section for Linux users, highlighting any differences or tips for running these commands in Linux environments.
  • Where PowerShell scripting is shown, consider providing equivalent Bash scripting examples for Linux users.
  • Avoid assuming PowerShell as the default scripting environment; clarify that both CLI and PowerShell are supported and cross-platform where applicable.
GitHub Create pull request

Scan History

Date Scan ID Status Bias Status
2025-08-17 00:01 #83 in_progress ✅ Clean
2025-07-13 21:37 #48 completed ❌ Biased
2025-07-09 13:09 #3 cancelled ✅ Clean
2025-07-08 04:23 #2 cancelled ❌ Biased

Flagged Code Snippets

To learn more about the CLI command, see [`az eventhubs namespace application-group create`](/cli/azure/eventhubs/namespace/application-group#az-eventhubs-namespace-application-group-create). ### [Azure PowerShell](#tab/powershell) Use the PowerShell command: [`New-AzEventHubApplicationGroup`](/powershell/module/az.eventhub/new-azeventhubapplicationgroup) to create an application group at Event Hubs namespace or event hub level. You must set -ClientAppGroupIdentifier based on the security context type you are choosing. Please review the [table](#supported-security-context-type) above to know supported Security context type The following example uses the [`New-AzEventHubThrottlingPolicyConfig`](/powershell/module/az.eventhub/new-azeventhubthrottlingpolicyconfig) to create two policies that will be associated with the application. - First throttling policy for the `Incoming bytes` metric with `12345` as the threshold. - Second throttling policy for the `Incoming messages` metric with `23416` as the threshold. Then, it creates an application group named `myappgroup` in the namespace `mynamespace` in the Azure resource group `myresourcegroup` by specifying the throttling policies and shared access policy as the security context.
### [Azure PowerShell](#tab/powershell) Use the [Set-AzEventHubApplicationGroup](/powershell/module/az.eventhub/set-azeventhubapplicationgroup) command with `-ThrottlingPolicyConfig` set to appropriate values. **Example:**
To learn more about the PowerShell command, see [`New-AzEventHubApplicationGroup`](/powershell/module/az.eventhub/new-azeventhubapplicationgroup). ### [ARM template](#tab/arm) The following example shows how to create an application group using an ARM template. In this example, the application group is associated with an existing SAS policy name `contososaspolicy` by setting the client `AppGroupIdentifier` as `NamespaceSASKeyName=contososaspolicy`. The application group policies are also defined in the ARM template. You must set ClientAppGroupIdentifier based on the security context type you are choosing. Please review the [table](#supported-security-context-type) above to know supported Security context type