Document Details
Resource Governance With App Groups
❌
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
⚠️
missing_linux_example
⚠️
windows_tools
Summary:
The documentation demonstrates a Windows bias by providing detailed PowerShell examples (a Windows-centric tool), listing PowerShell before CLI in several sections, and omitting any Linux-specific shell or scripting examples. There are no bash or Linux-native command examples, and the use of PowerShell is assumed as a primary automation tool. The CLI examples are present but are not explicitly shown in a Linux context, and there are no references to Linux tools or scripting patterns.
Recommendations:
- Add explicit bash/Linux shell examples for all CLI commands, including sample scripts and environment variable usage.
- Clarify that Azure CLI commands work cross-platform and provide sample outputs from both Windows (CMD/PowerShell) and Linux (bash).
- Avoid listing PowerShell before CLI unless there is a technical reason; alternate the order or clarify parity.
- Include notes or sections on using these commands in Linux environments, including any differences in authentication, file paths, or environment setup.
- Where automation is discussed, provide both PowerShell and bash scripting examples to ensure Linux users are equally supported.
- Explicitly mention that PowerShell Core is cross-platform if recommending PowerShell, and provide Linux installation instructions if relevant.
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 `-IsEnabled` set to `false` to disable an application group. Similarly, to enable an application group, set this property to `true` and run the command.
The following sample command disables the application group named `myappgroup` in the Event Hubs namespace `mynamespace` that's in the resource group `myresourcegroup`.
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
### [Azure PowerShell](#tab/powershell)
Use the [Set-AzEventHubApplicationGroup](/powershell/module/az.eventhub/set-azeventhubapplicationgroup) command with `-ThrottlingPolicyConfig` set to appropriate values.
**Example:**