Document Details
Howto Cluster Manager
❌
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:
⚠️
windows_first
⚠️
powershell_heavy
⚠️
windows_tools
⚠️
missing_linux_example
Summary:
The documentation demonstrates a Windows bias by consistently presenting Azure PowerShell examples alongside Azure CLI and ARM Template, with PowerShell (a Windows-centric tool) given equal prominence to the cross-platform CLI. There are no explicit Linux shell (bash) examples, and the instructions for role assignment and portal usage assume familiarity with Windows-oriented tools and workflows. No mention is made of Linux-native scripting or automation approaches, and the documentation does not clarify that Azure CLI commands are cross-platform or provide Linux-specific usage tips.
Recommendations:
- Explicitly state that Azure CLI commands are cross-platform and provide example invocations in bash/zsh (e.g., using environment variables, quoting, or piping output to jq).
- Add Linux shell (bash) script examples for common operations, especially for automation scenarios.
- Clarify that PowerShell examples are primarily for Windows users, and suggest alternatives for Linux/macOS users (such as bash or Azure CLI).
- When describing portal-based steps, mention that the Azure portal is accessible from any OS/browser, and provide keyboard shortcuts or accessibility tips that are not Windows-specific.
- Include references to Linux-native tools (e.g., jq for JSON parsing) when discussing output manipulation.
- Consider the order of examples: present Azure CLI (cross-platform) first, then PowerShell, to avoid implying Windows-first workflows.
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 | ✅ Clean |
| 2025-07-12 23:44 | #41 | in_progress | ❌ Biased |
Flagged Code Snippets
### [Azure PowerShell](#tab/azure-powershell)
This command updates the Cluster Manager in the specified Resource group.
### [Azure PowerShell](#tab/azure-powershell)
Arguments:
- `--name` or `-n` [Required] - The name of the Cluster Manager.
- `--resource-group` or `-g` [Required] - The name of resource group. You can configure the default resource group using `az configure --defaults group=<name>`.
- `--fabric-controller-id` [Required] - The resource ID of the Network Fabric Controller that is associated with the Cluster Manager.
- `--location` or `-l` - The Azure region where the Cluster Manager is created. Values from: `az account list -locations`. You can configure the default location using `az configure --defaults location="<LOCATION>"`.
- `--managed-resource-group-configuration` - The configuration of the managed resource group associated with the resource.
- Usage: `--managed-resource-group-configuration location=XX name=XX`
- location: The region of the managed resource group. If not specified, the region of the
parent resource is chosen.
- name: The name for the managed resource group. If not specified, a unique name is
automatically generated.
- `wait`/`--no-wait` - Wait for command to complete or don't wait for the long-running operation to finish.
- `--tags` - Space-separated tags: key[=value] [key[=value]...]. Use '' to clear existing tags.
- `--subscription` - Name or ID of subscription. You can configure the default subscription using `az account set -s NAME_OR_ID`.
- `--mi-system-assigned` - Enable System-assigned managed identity. One of `--mi-user-assigned` or `--mi-system-assigned` can be used at a time.
- `--mi-user-assigned` - The resource ID of the user-assigned managed identity to be added. One of `--mi-user-assigned` or `--mi-system-assigned` can be used at a time. Cluster Managers only support one user-assigned managed identity.
- `--if-match`/`if-none-match` - Specify the last-seen ETag value to prevent accidentally overwriting concurrent changes. The ETag is returned as the resource property once the resource is created and can be used on the update operations.
Common arguments that are available for every Azure CLI command:
- `--debug` - prints detailed information about CLI execution that is used for debugging purposes. If you find a bug, provide output generated with the `--debug` flag on when submitting a bug report.
- `--output` or `-o` - specifies the output format. The available output formats are Json, Jsonc (colorized JSON), tsv (Tab-Separated Values), table (human-readable ASCII tables), and yaml. By default the CLI outputs JSON.
- `--query` - uses the JMESPath query language to filter the output returned from Azure services.
### [Azure PowerShell](#tab/azure-powershell)
Create Cluster Manager with System Assigned Managed Identity:
### [Azure PowerShell](#tab/azure-powershell)
This command lists the Cluster Managers in the specified Resource group.