Azure Resource Manager
1002
Total Pages
808
Linux-Friendly Pages
194
Pages with Bias
19.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
492 issues found
Showing 426-450 of 492 flagged pages
Azure Resource Manager
Install Bicep tools
.../main/articles/azure-resource-manager/bicep/install.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides comprehensive installation instructions for Bicep CLI across Windows, Linux, and macOS. However, there is a notable emphasis on Windows-specific tools and patterns, such as dedicated sections for Chocolatey, Winget, and PowerShell scripts, while Linux and macOS instructions are more generic. Windows installer options are described in detail, and PowerShell is used for manual installation, whereas Linux/macOS rely on shell scripts. In some sections, Windows tools are listed before Linux/macOS equivalents, and PowerShell commands are shown for verification and installation on Windows, but not for Linux/macOS. Overall, Linux and macOS users can complete all tasks, but Windows-centric tooling and examples may create minor friction.
Recommendations
- Add parity for package manager installation on Linux (e.g., apt, yum, zypper) and macOS (e.g., MacPorts) if available.
- Provide shell script examples for verification and installation steps on Linux/macOS, similar to the PowerShell examples for Windows.
- Balance the order of presentation so that Linux/macOS instructions are not always listed after Windows equivalents.
- Include troubleshooting steps and common issues for Linux/macOS environments, not just for Windows.
- Mention alternative editors and environments that are popular on Linux/macOS, if relevant.
Create Pull Request
Azure Resource Manager
Use Azure Key Vault to pass a secret as a parameter during Bicep deployment
...es/azure-resource-manager/bicep/key-vault-parameter.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all command-line operations, but consistently lists Azure PowerShell examples immediately after Azure CLI, and refers to PowerShell-specific patterns (e.g., use of backticks, ConvertTo-SecureString). There is a minor Windows-first bias in the 'Related content' section, which references a Windows VM scenario as the only quickstart template. No Linux-specific tools, shell patterns, or troubleshooting are mentioned, and no explicit Linux/macOS examples are provided.
Recommendations
- Explicitly state that Azure CLI commands work cross-platform (Windows, Linux, macOS) and highlight this in introductory sections.
- Provide Linux/macOS-specific notes or troubleshooting tips where PowerShell commands differ or are unavailable.
- Include bash/zsh shell examples for relevant operations, especially where scripting or environment differences may affect usage.
- Balance references to Windows scenarios with Linux equivalents in related content and quickstart links.
- Clarify that PowerShell examples are primarily for Windows users, and suggest using Azure CLI for Linux/macOS.
Azure Resource Manager
Create and deploy Azure deployment stacks in Bicep
...cles/azure-resource-manager/bicep/deployment-stacks.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all operations, ensuring cross-platform parity in command-line instructions. However, Azure PowerShell examples are consistently presented first in every code block, which may subtly prioritize Windows users. The documentation refers to 'Azure PowerShell' and 'PowerShell' in headings and explanations, which are more strongly associated with Windows environments, though Azure PowerShell is available cross-platform. No exclusive use of Windows-only tools or patterns is present, and Linux/macOS users can complete all tasks using Azure CLI. There are no missing Linux examples, and no Windows-only tools are required.
Recommendations
- Alternate the order of Azure CLI and Azure PowerShell examples, or present Azure CLI first to reflect its cross-platform nature.
- Clarify in introductory sections that both Azure PowerShell and Azure CLI are available on Windows, Linux, and macOS.
- Add explicit notes or links for installing Azure CLI and Azure PowerShell on Linux/macOS.
- Consider grouping CLI and PowerShell examples together, or using tabs labeled 'Cross-platform (CLI)' and 'Windows (PowerShell)' to make parity clear.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page references Visual Studio Code and the Bicep CLI as the main tools for using the Bicep linter. While these tools are cross-platform, the page only provides screenshots and instructions for Visual Studio Code (which is available on Windows, Linux, and macOS) and generic command-line usage, without any explicit mention of Linux/macOS environments or examples. There is no evidence of PowerShell-specific commands or Windows-only instructions, but the lack of Linux/macOS-specific guidance or screenshots may create minor friction for non-Windows users.
Recommendations
- Add explicit statements confirming that Bicep CLI and Visual Studio Code are supported on Linux and macOS, not just Windows.
- Include screenshots or terminal examples from Linux/macOS environments to demonstrate parity.
- If there are platform-specific considerations (e.g., installation paths, CLI usage differences), document them clearly.
- Mention alternative editors or CLI usage patterns common on Linux/macOS, if relevant.
Azure Resource Manager
Bicep safe-dereference operator
...re-resource-manager/bicep/operator-safe-dereference.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Azure PowerShell and Visual Studio Code as primary tools for deploying and authoring Bicep files, which are commonly associated with Windows environments. Azure CLI is mentioned, but Azure PowerShell is listed first, and there is no mention of Linux-specific editors or deployment methods. There are no explicit Linux/macOS examples or instructions.
Recommendations
- List Azure CLI before Azure PowerShell when describing deployment options, as CLI is cross-platform.
- Explicitly mention that Azure CLI and Visual Studio Code are available on Linux/macOS, and provide links or instructions for installation on those platforms.
- Include alternative editors (e.g., Vim, Emacs) or note that Bicep files can be authored in any text editor.
- Add a section or note about deploying Bicep files from Linux/macOS terminals.
- Ensure that all example commands are platform-agnostic or provide platform-specific variants.
Azure Resource Manager
Bicep accessor operators
...icles/azure-resource-manager/bicep/operators-access.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page is generally platform-neutral in its technical content and examples, focusing on Bicep syntax. However, in the 'Next steps' section, it recommends Azure CLI or Azure PowerShell for deploying Bicep files, listing Azure PowerShell (a Windows-centric tool) alongside Azure CLI, and links to a Visual Studio Code quickstart (which is often associated with Windows development environments). There are no explicit Linux/macOS examples, nor are Linux-specific tools or deployment patterns mentioned.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and works on Linux/macOS, while Azure PowerShell is available on all platforms but may be more familiar to Windows users.
- Provide example commands for deploying Bicep files using Azure CLI on Linux/macOS (e.g., bash shell), not just PowerShell.
- Include links or references to Linux/macOS setup guides for Bicep and Azure CLI.
- Clarify that Visual Studio Code is available on Linux/macOS and provide parity instructions for those platforms.
Azure Resource Manager
Migrate Azure resources and JSON ARM templates to use Bicep
.../main/articles/azure-resource-manager/bicep/migrate.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates mild Windows bias by listing Windows tools (Azure PowerShell) alongside Azure CLI and portal for resource export, and mentioning Visual Studio Code keyboard shortcuts with Windows first. There is no explicit Linux/macOS example for exporting resources, and PowerShell is referenced as a primary tool, which may not be as familiar or available to Linux/macOS users. However, Azure CLI and VS Code are cross-platform, and Linux/macOS shortcuts are mentioned, so the bias is not severe.
Recommendations
- Provide explicit Linux/macOS examples for resource export, such as using Azure CLI commands in a Linux shell.
- When listing tools, alternate or randomize the order (e.g., 'Azure CLI, Azure PowerShell, or Azure portal') instead of always listing Windows tools first.
- Include screenshots or terminal examples from Linux/macOS environments.
- Clarify that Azure CLI and VS Code are cross-platform, and provide installation links for Linux/macOS.
- Avoid referencing Windows-specific extensions or tools unless Linux/macOS equivalents are also described.
Azure Resource Manager
Bicep spread operator
...ticles/azure-resource-manager/bicep/operator-spread.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page does not provide OS-specific code examples, but in the 'Next steps' section, it lists Azure PowerShell before Azure CLI and references Visual Studio Code as the editor, which is commonly associated with Windows. There is no mention of Linux-specific tools, editors, or deployment instructions, nor are there explicit Linux/macOS examples or guidance.
Recommendations
- List Azure CLI before Azure PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
- Explicitly mention that all examples work on Linux/macOS as well as Windows.
- Provide links or instructions for deploying Bicep files on Linux/macOS, including terminal usage.
- Suggest alternative editors (e.g., Vim, VS Code on Linux/macOS) or clarify cross-platform support for Visual Studio Code.
- Add a note about Bicep support and installation on Linux/macOS environments.
Azure Resource Manager
Bicep numeric operators
...cles/azure-resource-manager/bicep/operators-numeric.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions using Azure CLI or Azure PowerShell to deploy Bicep files, listing Azure PowerShell (a Windows-centric tool) before Azure CLI. No explicit Linux or macOS examples or instructions are provided, but Azure CLI is cross-platform. The rest of the page is platform-neutral, focusing on Bicep syntax and operators.
Recommendations
- Explicitly state that Azure CLI is cross-platform and works on Linux/macOS.
- Provide example commands for deploying Bicep files using Azure CLI on Linux/macOS.
- Avoid listing Azure PowerShell before Azure CLI, or clarify that PowerShell Core is available cross-platform.
- Add a note or section for Linux/macOS users to ensure parity and clarity.
Azure Resource Manager
Parameters in Bicep
...in/articles/azure-resource-manager/bicep/parameters.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page is largely platform-neutral in its technical content, focusing on Bicep syntax and concepts. However, in the 'Next steps' section, deployment guidance references both Azure CLI and Azure PowerShell, but lists Azure PowerShell after Azure CLI. There are no explicit examples or instructions for Linux/macOS users, nor is there mention of platform-specific differences in deployment. The only tool-specific links are to Azure CLI (cross-platform) and Azure PowerShell (Windows-centric), but CLI is listed first. No explicit Windows-only tools or patterns are described, and no PowerShell-specific examples are given in the main content.
Recommendations
- Add explicit notes clarifying that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Provide example commands for both Azure CLI and Azure PowerShell when referencing deployment, ideally side-by-side.
- Include a brief section or callout about platform compatibility for deployment tools.
- Ensure that any future examples or instructions do not assume Windows or PowerShell as the default environment.
Azure Resource Manager
Resource declaration in Bicep
...s/azure-resource-manager/bicep/resource-declaration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for querying supported resource locations, but the PowerShell example is presented first. No other Windows-specific tools or patterns are used, and Linux/macOS users are not excluded from completing any tasks.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more widely used on Linux/macOS.
- Explicitly note that both CLI and PowerShell commands work on Windows, Linux, and macOS, but CLI is natively cross-platform.
- Consider adding Bash or shell script snippets where relevant, especially for automation scenarios.
Azure Resource Manager
Create a private container registry in Azure for Bicep modules
...zure-resource-manager/bicep/private-module-registry.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for key tasks, but consistently lists Azure PowerShell (a Windows-centric tool) first in each example section. The initial instructions and code samples prioritize PowerShell, which is more commonly used on Windows, before presenting Azure CLI commands that are cross-platform. There is also a focus on Windows-specific patterns, such as referencing %USERPROFILE% for cache location, and the use of PowerShell cmdlets, which may be less familiar or accessible to Linux/macOS users.
Recommendations
- Alternate the order of examples, sometimes showing Azure CLI first to avoid implicit prioritization of Windows tools.
- Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Provide Bash shell examples for common tasks, especially for Linux/macOS users.
- Clarify that PowerShell is available cross-platform, but Azure CLI may be more familiar to non-Windows users.
- Ensure all file path examples use platform-agnostic notation or show all platforms equally.
- Add a table or note summarizing tool availability and platform compatibility.
Azure Resource Manager
Create Azure Managed Application that deploys storage account encrypted with customer-managed key
...ed-applications/create-storage-customer-managed-key.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides command-line build instructions for Bicep files using both PowerShell and Azure CLI, but PowerShell is listed first and the examples are presented in a tabbed format that defaults to PowerShell. There are no explicit Linux/macOS-specific instructions or examples for tasks like installing prerequisites or using alternative editors/tools. The overall workflow is platform-neutral, but the ordering and emphasis subtly favor Windows/PowerShell users.
Recommendations
- Present Azure CLI examples before PowerShell, or default to CLI as it is cross-platform.
- Explicitly mention that all steps (including Visual Studio Code and Azure CLI) work on Linux/macOS, and provide installation links for those platforms.
- Add notes or examples for Linux/macOS users where relevant (e.g., command-line usage, file paths, package managers).
- Clarify that Azure CLI commands are identical across platforms and highlight any platform-specific caveats if they exist.
Azure Resource Manager
Create and publish Azure Managed Application in service catalog
...er/managed-applications/publish-service-catalog-app.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all command-line steps, ensuring Linux parity in terms of functionality. However, PowerShell examples are consistently presented first, and PowerShell-specific concepts (such as 'splatting') are explained in detail, while Bash/Linux-specific concepts (like environment variables or piping) are not. The use of Visual Studio Code is platform-neutral, but the initial terminal instructions mention PowerShell first, which may subtly reinforce a Windows-centric workflow. There are no steps that are Windows-only, and all tasks can be completed on Linux/macOS using Azure CLI or the portal.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first in some sections.
- Provide Bash/Linux-specific tips or explanations where relevant, similar to the PowerShell splatting explanation.
- Explicitly state that all steps can be performed on Linux/macOS, and highlight any platform-specific nuances if they exist.
- Consider adding a short section on choosing between PowerShell and CLI based on OS, or link to such guidance.
Azure Resource Manager
Bring your own storage to create and publish an Azure Managed Application definition
...ions/publish-service-catalog-bring-your-own-storage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all major steps, ensuring cross-platform coverage. However, PowerShell examples are consistently presented first, and PowerShell-specific concepts (like splatting) are explained in detail, while Bash/Linux-specific notes are minimal. There is a minor note about Git Bash for Windows, but no explicit Linux/macOS troubleshooting or tool recommendations. Visual Studio Code is recommended as the editor, which is cross-platform, but no mention is made of alternative editors popular on Linux/macOS.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first in some sections to avoid implicit Windows-first bias.
- Provide brief explanations of Bash/Linux-specific patterns or troubleshooting tips, similar to the PowerShell splatting explanation.
- Include notes or links for Linux/macOS users regarding shell differences, file paths, or authentication nuances.
- Mention alternative editors (e.g., Vim, nano) for Linux/macOS users, or clarify that VS Code is cross-platform.
- Add troubleshooting notes for common Linux/macOS issues (e.g., file permissions, environment variables) where relevant.
Azure Resource Manager
Configure data boundary
...re-resource-manager/management/manage-data-boundary.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, REST API, and Azure portal. However, PowerShell examples are given equal prominence to Azure CLI, and references to PowerShell are frequent (including in 'For more information' links). The documentation does not mention Linux or macOS platforms explicitly, nor does it provide shell-specific guidance for bash/zsh or highlight cross-platform usage. The ordering of examples sometimes places PowerShell before REST API, and links to PowerShell documentation are included. There is no explicit Windows-only content, but the presence and prominence of PowerShell and lack of Linux/macOS-specific notes or examples indicate a mild Windows bias.
Recommendations
- Add explicit notes that Azure CLI and REST API are cross-platform and work on Linux/macOS.
- Include bash/zsh shell examples where relevant, especially for scripting.
- Clarify that PowerShell examples work on PowerShell Core (which is cross-platform), or provide bash alternatives for Linux/macOS users.
- Ensure that Azure CLI examples are shown before PowerShell, or at least alternate the order.
- Add a section or note on platform compatibility for all tools mentioned.
Azure Resource Manager
Manage resource management private links
...ager/management/manage-private-link-access-commands.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for all operations, with REST API calls included. However, PowerShell examples are always present and shown in parallel with CLI, and the introductory comments reference PowerShell-specific login commands (Connect-AzAccount) without mentioning Linux/macOS shell alternatives. There is a slight 'windows_first' bias in the ordering and presence of PowerShell, but Azure CLI is cross-platform and shown first in each tab. No Windows-only tools or patterns are used, and Linux/macOS users can complete all tasks using Azure CLI or REST.
Recommendations
- Explicitly state that Azure CLI works on Windows, Linux, and macOS.
- Add brief notes for Linux/macOS users, such as using Bash or zsh with Azure CLI.
- Clarify that PowerShell examples are for users who prefer PowerShell, which is available cross-platform but more common on Windows.
- Consider adding example shell commands for Bash/zsh where appropriate (e.g., using curl for REST calls).
- Avoid implying PowerShell is the default or primary method unless justified.
Azure Resource Manager
Lock your Azure resources to protect your infrastructure
...es/azure-resource-manager/management/lock-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Azure PowerShell examples before Azure CLI examples in the 'Configure locks' section, and provides detailed PowerShell command usage. While Azure CLI and Python examples are included, there is a subtle Windows bias in the ordering and prominence of PowerShell instructions, which are most commonly used on Windows. No Linux-specific tools or shell examples (e.g., Bash) are provided, but the CLI examples are cross-platform. No critical tasks are Windows-only, and Linux/macOS users can complete all tasks using Azure CLI or REST API.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Add Bash shell usage examples for Azure CLI where relevant (e.g., variable assignment, piping).
- Clarify that PowerShell is available cross-platform, but is most commonly used on Windows.
- Consider including a table summarizing tool/platform compatibility for each method.
Azure Resource Manager
Manage Azure resources by using Azure CLI
...re-resource-manager/management/manage-resources-cli.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is generally cross-platform, using Azure CLI and shell syntax compatible with Linux/macOS. However, there is a notable Windows bias in the 'Deploy a template' section, where the primary link for creating ARM templates references Visual Studio Code with a PowerShell tab, a Windows-centric tool and shell. This reference appears before any mention of Linux-friendly alternatives. No Linux/macOS-specific tools or examples (such as Bash scripting, VS Code on Linux, or cross-platform editors) are highlighted, and the documentation does not clarify that all shown scripts work equally on Linux/macOS.
Recommendations
- Add explicit notes clarifying that all Azure CLI examples are compatible with Linux/macOS shells.
- Provide links or references to Linux/macOS-friendly tools for ARM template authoring (e.g., VS Code on Linux, vim, nano).
- Include Bash-specific tabs or examples where PowerShell is referenced, especially in linked tutorials.
- Ensure that cross-platform parity is maintained in all linked documentation, not just on this page.
Azure Resource Manager
Handling special cases when moving virtual machines to resource group or subscription
.../move-limitations/virtual-machines-move-limitations.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for all command-line operations, maintaining parity in terms of functionality. However, PowerShell examples are always present and sometimes shown before or alongside CLI, reflecting a slight 'windows_first' bias. There are no Linux-specific shell examples (e.g., Bash), nor are there any references to Linux/macOS platform nuances, but the CLI examples are cross-platform. No Windows-only tools or patterns are used, and Linux users can complete all tasks using the CLI instructions.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS and Windows, to reassure non-Windows users.
- Consider providing Bash script examples for multi-step operations, especially where variables or loops are used.
- Where PowerShell is mentioned, clarify that it is available cross-platform, or link to installation instructions for Linux/macOS.
- If there are platform-specific caveats (e.g., file paths, authentication), note them.
Azure Resource Manager
Manage Azure resources by using the REST API
...e-resource-manager/management/manage-resources-rest.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication and resource listing, but PowerShell is given equal prominence and is included in all code tabs. There is a slight Windows-first bias, as PowerShell is a Windows-centric tool and is featured alongside Azure CLI, which is cross-platform. References to Visual Studio Code and PowerShell for template deployment may also reinforce Windows patterns, though VS Code is cross-platform. No Linux/macOS-specific tools or shell examples (e.g., bash, zsh) are provided, but the CLI and cURL examples are generally cross-platform.
Recommendations
- Add explicit bash/zsh shell examples for Linux/macOS users, especially for authentication and REST calls.
- Clarify that Azure CLI and cURL examples work on Linux/macOS, and note any OS-specific differences.
- Consider providing examples using other common Linux tools (e.g., wget) where appropriate.
- Balance the prominence of PowerShell by mentioning it as an option, not as a default or primary method.
- Where Visual Studio Code is referenced, clarify its cross-platform availability.
Azure Resource Manager
Evaluate a cloud workload for relocation
...azure-resource-manager/management/relocate-evaluate.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing PowerShell in the only explicit example for exporting public IP configuration, and by linking to a PowerShell-specific guide. There are no Linux or cross-platform CLI examples provided, and the documentation does not mention Linux/macOS tools or patterns for resource management or automation. All tool references are Azure portal or PowerShell-centric, with no mention of Azure CLI or other cross-platform alternatives.
Recommendations
- Provide Azure CLI examples alongside PowerShell for tasks such as exporting and moving public IP configurations.
- Reference cross-platform tools and automation patterns (e.g., bash scripts, Terraform, Ansible) where applicable.
- Explicitly state when a process or tool is platform-agnostic, and offer guidance for both Windows and Linux/macOS users.
- Include links to Linux/macOS documentation or guides for Azure resource management.
- Balance example ordering so that Windows and Linux approaches are presented equally or in parallel.
Azure Resource Manager
Relocate Azure HDInsight clusters to another region
...-manager/management/relocation/relocation-hdinsight.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation displays a mild Windows bias by consistently listing Azure PowerShell methods alongside Azure CLI and portal options, and sometimes mentioning PowerShell before Linux-friendly alternatives. However, Linux/macOS-compatible tools (Azure CLI, Cloud Shell, VS Code) are also referenced, and no critical steps are Windows-only.
Recommendations
- Alternate the order of examples so that Azure CLI (cross-platform) is listed before PowerShell in each section.
- Explicitly mention that Azure CLI and Cloud Shell work on Linux/macOS, and provide example commands for both environments where relevant.
- Add a note clarifying that all steps can be completed on Linux/macOS using Azure CLI, Cloud Shell, or VS Code.
- Ensure that any referenced scripts or templates do not assume Windows-specific paths or conventions.
Azure Resource Manager
Label mission-critical workloads
...ce-manager/management/tag-mission-critical-workload.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation lists Azure PowerShell (a Windows-centric tool) before Azure CLI and other cross-platform options in the 'How to apply Azure tags' section. This ordering subtly prioritizes Windows tooling and may suggest to readers that PowerShell is the primary or preferred method, despite Azure CLI being more universally available across platforms. No explicit Linux/macOS examples or guidance are provided, and no mention is made of platform-specific considerations.
Recommendations
- List Azure CLI before Azure PowerShell in automation tool recommendations, as CLI is cross-platform.
- Explicitly state that Azure CLI, Bicep, Terraform, and the Azure portal are fully supported on Linux and macOS.
- Provide example commands for both Azure CLI and PowerShell, or clarify that CLI examples are suitable for all platforms.
- Add a note or section on platform parity, reassuring Linux/macOS users that all tagging functionality is available to them.
Azure Resource Manager
Relocate Azure Virtual Machine Scale Sets to another region
...nt/relocation/relocation-virtual-machine-scale-sets.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation references Azure CLI and PowerShell as Infrastructure as Code (IAC) tools for redeployment, but does not provide explicit examples for either. However, PowerShell is mentioned alongside Azure CLI, which may imply parity, but there are no Linux-specific instructions, nor is Bash or shell scripting referenced. All screenshots and step-by-step instructions use the Azure Portal GUI, which is platform-neutral, but the lack of Linux/macOS command-line examples or explicit mention of cross-platform tooling creates a subtle Windows bias.
Recommendations
- Provide explicit Azure CLI (bash/shell) examples for key steps, especially template export, modification, and deployment.
- Clarify that Azure CLI is cross-platform and can be used on Linux/macOS, not just Windows.
- Include references or links to Linux/macOS setup guides for Azure CLI.
- If PowerShell is mentioned, also mention that PowerShell Core is available cross-platform, or provide parity with bash examples.
- Add a note or section on performing these tasks from Linux/macOS environments.