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 101-125 of 492 flagged pages
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-deploy-vm-extensions.md
...er/templates/template-tutorial-deploy-vm-extensions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All examples and instructions focus exclusively on deploying a PowerShell script to a Windows VM using the Custom Script Extension. The template and scripts are Windows-specific, and there is no mention of Linux VMs, Bash scripts, or Linux equivalents. Windows tools and patterns (e.g., PowerShell, Install-WindowsFeature, IIS) are used throughout, and Linux options are omitted.
Recommendations
- Add parallel examples for deploying to Linux VMs using Bash scripts and the Custom Script Extension for Linux.
- Include a Linux quickstart template (e.g., 'Deploy a simple Linux VM') alongside the Windows template, and show how to edit it.
- Demonstrate how to install a web server (e.g., Apache or Nginx) on a Linux VM using a Bash script.
- Provide Linux command examples for retrieving the public IP address (e.g., using Azure CLI in Bash).
- Mention and link to the Linux extensions documentation and features.
- Structure the tutorial to present both Windows and Linux options, or clearly indicate that this tutorial is Windows-specific and link to a Linux-focused equivalent.
Create Pull Request
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-export-template.md
...manager/templates/template-tutorial-export-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell is mentioned before Azure CLI in prerequisites and deployment instructions, and PowerShell examples are presented before CLI equivalents. There are no explicit Linux shell examples (e.g., bash), nor are Linux-specific tools or patterns (such as scripting in bash or using Linux-native editors) discussed. The use of Visual Studio Code is cross-platform, but no mention is made of Linux-specific alternatives or considerations.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Include explicit bash shell examples for template deployment, especially for Linux users.
- Mention Linux-native editors (such as Vim, Nano, or Gedit) as alternatives to Visual Studio Code.
- Clarify that both Azure CLI and PowerShell are cross-platform, and provide installation guidance for Linux users.
- Add notes or sections highlighting Linux-specific workflows or troubleshooting steps.
- Ensure that screenshots and instructions referencing the Azure portal do not assume a Windows environment.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-quickstart-template.md
...ger/templates/template-tutorial-quickstart-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows a moderate Windows bias. In the deployment section, Azure PowerShell (a Windows-centric tool) is presented before Azure CLI, and the PowerShell example is given first. There is also mention of Visual Studio Code as the editor, which is cross-platform but often associated with Windows. The instructions for cleaning up resources use the Azure Portal, which is platform-agnostic, but there are no explicit Linux-specific instructions or terminal examples. There are no Linux shell (bash) examples, and no mention of Linux-native editors or tools.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (which is more cross-platform and Linux-friendly) first.
- Explicitly mention that both Azure CLI and PowerShell are available on Linux, macOS, and Windows, and provide installation links for all platforms.
- Add bash shell examples for deploying templates, especially for Linux users.
- Mention alternative editors such as Vim, Nano, or Emacs for Linux users, or clarify that Visual Studio Code is available on Linux.
- Include a section or note highlighting any platform-specific differences or requirements.
- Provide resource cleanup instructions using the Azure CLI in addition to the Azure Portal.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-use-conditions.md
...-manager/templates/template-tutorial-use-conditions.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a clear Windows bias. It uses a Windows VM template as the primary example, provides only PowerShell deployment scripts (no Azure CLI or Bash equivalents), and references Windows tools and patterns (e.g., PowerShell, Windows VM Quickstart template) before or instead of Linux alternatives. Linux users are only briefly acknowledged (e.g., Bash in Cloud Shell), but no full Linux/CLI workflow is provided.
Recommendations
- Provide parallel Azure CLI (az) or Bash script examples for all deployment and cleanup steps, not just PowerShell.
- Include a Linux VM Quickstart template as an alternative or in addition to the Windows VM template.
- When referencing Cloud Shell, give equal prominence to Bash and PowerShell, and show both script types.
- Avoid using only Windows-specific terminology and tools (e.g., PowerShell, Windows VM) in examples and instructions.
- Add a section or callout for Linux/macOS users, outlining any differences or considerations.
- Ensure screenshots and walkthroughs are not exclusively based on Windows environments.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-use-key-vault.md
...e-manager/templates/template-tutorial-use-key-vault.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows and PowerShell bias. All command-line examples for creating and deploying resources use Azure PowerShell scripts, with no equivalent Azure CLI (az) or Bash examples provided. The tutorial centers on deploying a Windows VM, and the only template referenced is for a Windows VM. There is no mention of Linux VM templates or how to use Key Vault secrets with Linux deployments. The instructions for connecting to the VM use RDP, a Windows-specific protocol, and do not mention SSH or Linux alternatives. Visual Studio Code is recommended as the editor, which is cross-platform, but all automation and scripting is Windows/PowerShell-centric.
Recommendations
- Provide equivalent Azure CLI (az) and Bash examples for all PowerShell scripts, especially for key vault creation, secret retrieval, and template deployment.
- Include a Linux VM deployment scenario alongside or instead of the Windows VM example, referencing a Linux quickstart template.
- Demonstrate how to connect to a Linux VM using SSH, and how to use Key Vault secrets for Linux admin credentials.
- When referencing password requirements, link to both Windows and Linux VM documentation.
- Explicitly state that the instructions apply to both Windows and Linux, or clarify when steps are OS-specific.
- Consider providing a toggle or tabs for PowerShell and CLI/Bash instructions throughout the tutorial.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-use-template-reference.md
.../templates/template-tutorial-use-template-reference.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation shows a slight Windows bias: Visual Studio Code is required as the editor (commonly used on Windows, though cross-platform), and file operations are described using GUI steps typical of Windows workflows. In deployment instructions, both PowerShell and Azure CLI (Bash) examples are provided, but PowerShell is mentioned first and in more detail. There is no mention of Linux-native editors or command-line file operations, and no explicit Linux-specific guidance for file handling or environment setup.
Recommendations
- Include instructions for opening and saving files using Linux command-line tools (e.g., curl, nano, vim) alongside Visual Studio Code.
- Explicitly mention that Visual Studio Code is available on Linux and macOS, or suggest alternative editors for those platforms.
- Alternate the order of PowerShell and CLI examples, or present CLI (Bash) first to avoid Windows-first perception.
- Add a note clarifying that all steps can be performed on Linux, macOS, or Windows, and provide platform-specific tips where relevant.
- Provide screenshots or descriptions for Linux/macOS file dialogs or terminal commands where file upload/download is discussed.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/create-troubleshooting-template.md
...ger/troubleshooting/create-troubleshooting-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by mentioning Azure PowerShell (a Windows-centric tool) before Azure CLI, and by referencing PowerShell-specific commands. There are no explicit Linux or Bash examples, and the instructions do not clarify parity or differences for Linux users. The guidance assumes familiarity with PowerShell, which is more common on Windows, and does not offer alternative command-line examples or considerations for Linux environments.
Recommendations
- Provide both Azure PowerShell and Azure CLI examples side by side, or clarify which is cross-platform.
- List Azure CLI (which is cross-platform and common on Linux) before Azure PowerShell, or at least equally.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash shell examples where appropriate.
- If PowerShell is referenced, note that PowerShell Core is available cross-platform, or provide Bash equivalents.
- Add a section or note about running deployments from Linux or macOS, including any differences or prerequisites.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/deployment-quota-exceeded.md
...e-manager/troubleshooting/deployment-quota-exceeded.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI (with Bash shell) and PowerShell examples for managing deployment quotas. However, the PowerShell section is given equal prominence, and there is no mention of Linux-specific shell environments (e.g., zsh, fish) or Windows Command Prompt. The Bash examples are generic, but the PowerShell examples are Windows-centric. There is no explicit guidance for Linux users beyond Bash, and the documentation does not clarify cross-platform compatibility for the CLI commands.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and mention supported shells (e.g., Bash, zsh, fish).
- Add examples for other popular Linux shells if syntax differs, or clarify that Bash syntax is portable.
- Clarify that PowerShell Core is cross-platform, and provide guidance for running PowerShell commands on Linux/macOS if relevant.
- Consider adding a Windows Command Prompt example or explicitly state that PowerShell is the recommended Windows shell.
- Add a note about prerequisites for each environment (e.g., Azure CLI installation on Linux/macOS, PowerShell installation on non-Windows platforms).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/enable-debug-logging.md
...source-manager/troubleshooting/enable-debug-logging.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Azure PowerShell (which is most commonly used on Windows) for enabling debug logging, with no equivalent method available for Azure CLI (the typical cross-platform/Linux tool). All actionable examples for enabling debug logging use PowerShell cmdlets, and the documentation explicitly states that debug logging cannot be enabled via Azure CLI. There are no references to Linux-specific tools, shell scripting, or platform-agnostic alternatives for the core debug logging functionality.
Recommendations
- Work with Azure engineering to add support for enabling debug logging via Azure CLI, or document any workarounds if available.
- If enabling debug logging is fundamentally unavailable in Azure CLI, clearly state this limitation and suggest alternative troubleshooting approaches for Linux users.
- Provide Bash or shell scripting examples where possible, especially for retrieving and managing deployment logs.
- Consider mentioning platform-agnostic tools or REST API methods for enabling debug logging, if available, to improve parity.
- Ensure that documentation does not assume PowerShell as the default and provides equal visibility to Linux/cross-platform workflows.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/error-not-found.md
...re-resource-manager/troubleshooting/error-not-found.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell and Azure CLI for command-line operations, with PowerShell (a Windows-centric tool) mentioned first. There are no explicit Linux shell (bash) examples or instructions, and the only command-line tools referenced are PowerShell and Azure CLI. The Azure portal is also referenced as a GUI tool, which is cross-platform but not a Linux-native experience. No Linux-specific troubleshooting steps, shell commands, or examples are provided.
Recommendations
- Provide bash shell examples for Azure CLI commands, especially for common troubleshooting steps.
- Mention Azure CLI before PowerShell, or present both equally, to avoid Windows-first ordering.
- Include explicit instructions or notes for users on Linux/macOS, such as verifying the current subscription context using bash.
- Reference cross-platform tools and workflows where possible, and clarify that Azure CLI is available on all platforms.
- If referencing PowerShell, also mention that Azure PowerShell is available on Linux/macOS, or provide equivalent bash commands.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/error-policy-requestdisallowedbypolicy.md
...ubleshooting/error-policy-requestdisallowedbypolicy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for investigating policy errors, but the PowerShell section is more detailed, with additional explanation and advanced usage (e.g., ConvertTo-Json with Depth). There is no mention of Bash scripting or Linux-specific command-line patterns, and the PowerShell section appears after the Azure CLI section, but is more comprehensive. No explicit Linux tools or shell examples are provided.
Recommendations
- Add Bash shell scripting examples for users on Linux/macOS, especially for parsing JSON output from Azure CLI.
- Ensure CLI and PowerShell sections are equally detailed, or provide advanced CLI usage (e.g., using jq to parse JSON).
- Explicitly mention that Azure CLI commands work cross-platform, and provide sample commands for common Linux shells.
- Consider adding a note or section for troubleshooting using REST API calls with curl, which is common on Linux.
- Review the PowerShell section to ensure parity with CLI examples, avoiding unnecessary detail imbalance.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/error-register-resource-provider.md
...er/troubleshooting/error-register-resource-provider.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed examples for Azure CLI and Azure PowerShell, with PowerShell examples given equal prominence to CLI. However, there are no explicit Linux shell (bash) examples, and the CLI examples are not specifically shown in a Linux context. PowerShell is a Windows-centric tool, and its inclusion without bash or Linux shell equivalents may bias the documentation towards Windows users. Additionally, the order of sections places Azure CLI first, but the lack of explicit Linux shell examples and the presence of PowerShell may still indicate a subtle Windows bias.
Recommendations
- Add explicit bash/Linux shell examples for all Azure CLI commands, clarifying that Azure CLI is cross-platform and can be run in bash.
- Include notes or tabs for bash and PowerShell to show parity and help users on both platforms.
- Consider adding troubleshooting steps or examples using native Linux tools or scripting patterns where relevant.
- Clarify in the introduction that Azure CLI commands are cross-platform and provide guidance for both Windows and Linux users.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/error-resource-quota.md
...source-manager/troubleshooting/error-resource-quota.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for checking quotas, but the PowerShell example is given equal prominence, despite PowerShell being primarily associated with Windows. There are no explicit Linux shell (bash) examples, and the Azure CLI example is not clearly marked as cross-platform. The documentation does not mention or show how to perform these actions using native Linux tools or in a Linux context, and the portal instructions are platform-neutral but do not address Linux-specific workflows.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide bash-specific context or examples where appropriate.
- Add a note or section highlighting how Linux users can install and use Azure CLI, and clarify that PowerShell is optional and not required on Linux.
- Consider providing bash script examples or mentioning common Linux shell environments to ensure parity.
- If PowerShell is mentioned, clarify its cross-platform availability, or de-emphasize it in favor of the more universal Azure CLI.
- Ensure that any screenshots or portal instructions do not assume a Windows environment (e.g., file paths, UI differences).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/quickstart-troubleshoot-bicep-deployment.md
...leshooting/quickstart-troubleshoot-bicep-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently presenting PowerShell examples alongside Azure CLI, and by referencing Windows-centric tools and workflows (e.g., Visual Studio Code, PowerShell, and Cloud Shell) without mentioning Linux-specific alternatives. PowerShell is given equal prominence to Azure CLI, and there are no Bash or Linux shell examples. The use of Visual Studio Code, while cross-platform, is often associated with Windows workflows. There are no explicit Linux or macOS-specific instructions, nor are there references to native Linux editors or shells.
Recommendations
- Add explicit Bash/Linux shell examples for all Azure CLI commands, demonstrating usage in a typical Linux terminal.
- Clarify that Visual Studio Code is cross-platform, and mention alternative editors (e.g., Vim, nano) for Linux users.
- Include instructions for installing and using the Azure CLI and Bicep tools on Linux systems.
- Avoid presenting PowerShell examples with equal prominence to Azure CLI; instead, default to Azure CLI (which is cross-platform) and provide PowerShell as an optional tab.
- Mention that all commands can be run from Bash on Linux/macOS, and provide troubleshooting tips for common Linux-specific issues (e.g., file permissions, line endings).
Azure Resource Manager
Relocate Azure Virtual Machine Scale Sets to another region
...nt/relocation/relocation-virtual-machine-scale-sets.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides instructions for relocating Azure Virtual Machine Scale Sets but consistently references the Azure portal and PowerShell/ARM templates without offering Linux/macOS-specific command-line examples (e.g., Azure CLI bash commands). The use of screenshots and instructions is portal-centric, which is platform-agnostic, but when mentioning Infrastructure as Code tools, PowerShell is listed alongside Azure CLI and ARM templates, with no explicit Linux/macOS shell examples or guidance. There are no references to Linux-specific tools or workflows, and example commands/scripts are absent.
Recommendations
- Add explicit Azure CLI bash examples for key steps, such as exporting and deploying templates, to ensure Linux/macOS users have parity.
- Clarify that all steps can be performed using Azure CLI on any platform, not just PowerShell or the Azure portal.
- When listing Infrastructure as Code tools, mention Azure CLI first or equally with PowerShell, and provide sample commands for both.
- Include notes or links to cross-platform documentation for template export and deployment.
Azure Resource Manager
Relocation guidance for Azure Firewall
...e-manager/management/relocation/relocation-firewall.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides step-by-step guidance for relocating Azure Firewall, with examples and automation instructions exclusively using Azure PowerShell. There are no CLI (az) or Bash examples, and all scripting guidance is PowerShell-centric, which is more familiar and accessible to Windows users. This creates friction for Linux/macOS users who typically use Bash and Azure CLI for automation.
Recommendations
- Add equivalent Azure CLI (az) examples for all template export, modification, and deployment steps.
- Include Bash shell commands for template handling (e.g., unzipping, file editing) alongside PowerShell instructions.
- Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI and provide links to relevant CLI documentation.
- Consider reordering or parallelizing examples so CLI/Bash instructions are not secondary to PowerShell.
Azure Resource Manager
Relocate an Azure Container Registry to another region
...management/relocation/relocation-container-registry.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation includes several PowerShell-specific commands (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without providing equivalent Bash/Azure CLI or cross-platform alternatives. In some sections, PowerShell commands are presented before or instead of Azure CLI examples, and there is at least one instance where only a PowerShell command is given for a key step. This creates friction for Linux/macOS users who may not have access to or familiarity with Azure PowerShell modules.
Recommendations
- For every PowerShell command provided, include an equivalent Azure CLI or Bash example, especially for common tasks like listing repositories or importing images.
- When referencing both Azure CLI and PowerShell, present Azure CLI (which is cross-platform) examples first, or clearly indicate both options.
- Audit the documentation to ensure that all critical steps can be completed using cross-platform tools, and explicitly mention if a step is only possible with PowerShell.
- Where possible, use Bash scripting for automation examples, as it is more universally accessible across platforms.
Azure Resource Manager
Relocate an Azure Container Registry to another region
...management/relocation/relocation-container-registry.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides several examples using Azure PowerShell cmdlets (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without equivalent Bash/Azure CLI or cross-platform alternatives. In some cases, PowerShell commands are shown first or exclusively, even though Azure CLI is generally more cross-platform. There is a Bash/Azure CLI script for image import, but the initial steps and AKS integration are PowerShell-centric. No explicit Linux/macOS guidance is provided for these steps.
Recommendations
- For every PowerShell command (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster), provide equivalent Azure CLI or Bash examples, or clearly indicate if there is no cross-platform equivalent.
- When listing command options, present Azure CLI (Bash) examples first or side-by-side with PowerShell, since Azure CLI is cross-platform.
- Explicitly state when a step is Windows/PowerShell-only, and provide guidance or workarounds for Linux/macOS users if possible.
- Review all code snippets and ensure Linux/macOS users can follow the workflow without switching to Windows or PowerShell.
Azure Resource Manager
Relocation guidance for Azure Firewall
...e-manager/management/relocation/relocation-firewall.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides step-by-step instructions for relocating Azure Firewall using the Azure Portal and Azure PowerShell. All CLI-based examples and automation instructions use Azure PowerShell cmdlets, with no mention of Azure CLI or Bash scripting. This creates friction for Linux/macOS users who may prefer or require cross-platform tools. There is no explicit Windows-only requirement for the relocation process; Azure PowerShell is available on Linux/macOS, but Azure CLI is more commonly used in cross-platform automation.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell steps, especially for template export, modification, and deployment.
- Clarify that Azure PowerShell can be used on Linux/macOS, but offer Azure CLI as a first-class alternative.
- Include Bash scripting examples for automation where appropriate.
- Consider reordering examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
Azure Resource Manager
Relocate an Azure Container Registry to another region
...management/relocation/relocation-container-registry.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides several examples and command snippets using Azure PowerShell cmdlets (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without equivalent Bash/Azure CLI or Linux/macOS-native alternatives. In some cases, Azure CLI is used, but PowerShell commands are often shown first or exclusively for key steps (such as listing repositories or configuring AKS integration). There is no mention of Linux/macOS-specific considerations or examples for these tasks.
Recommendations
- For every PowerShell example (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster), provide an equivalent Azure CLI or Bash command, and show both side-by-side or with clear tabs for each platform.
- Ensure that Azure CLI (cross-platform) examples are shown first, or at least equally, before PowerShell-specific commands.
- Clarify in each section which commands are cross-platform and which are Windows/PowerShell-specific.
- Add notes or links for Linux/macOS users where PowerShell commands are shown, explaining how to install/use Azure CLI or PowerShell Core if needed.
- Review the use of terms like 'script' and ensure that Bash scripting examples are provided alongside PowerShell scripts.
Azure Resource Manager
Relocation guidance for Azure Firewall
...e-manager/management/relocation/relocation-firewall.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides step-by-step instructions for relocating Azure Firewall using the Azure Portal and Azure PowerShell. All command-line examples use Azure PowerShell, with no mention of Azure CLI or Bash scripts, which are cross-platform and preferred by many Linux/macOS users. There are no Linux-specific instructions or parity for command-line operations, and the only automation tooling referenced is PowerShell, which is most commonly used on Windows.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell command-line steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that both Azure PowerShell and Azure CLI can be used, and link to Azure CLI documentation where relevant.
- Where scripts or automation are referenced, provide Bash script examples or note how Linux/macOS users can perform the same actions.
- Consider reordering examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell, or use tabs for both.
Azure Resource Manager
Relocate Azure Virtual Machine Scale Sets to another region
...nt/relocation/relocation-virtual-machine-scale-sets.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation references PowerShell and Azure portal workflows, but does not provide Linux/macOS-specific CLI examples or mention cross-platform tools first. The use of PowerShell is implied as a primary method, and the Azure portal screenshots and instructions are Windows-centric. There is no explicit guidance for Linux users, such as Bash or Azure CLI commands, nor are Linux/macOS workflows shown alongside Windows ones.
Recommendations
- Add Azure CLI (az) command examples for all steps where PowerShell or portal is referenced, especially for exporting templates, setting instance counts, and deploying resources.
- Include screenshots or instructions for Linux/macOS environments where relevant, such as using Azure CLI in Bash.
- Explicitly state that all steps can be performed on Linux/macOS using Azure CLI, and provide links to cross-platform tool documentation.
- Present CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
Azure Resource Manager
Relocate Azure Backup to Another Region
...rce-manager/management/relocation/relocation-backup.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides some OS-specific guidance, but Windows examples and instructions are generally mentioned before Linux equivalents. PowerShell/Azure PowerShell is referenced for scripting, but there are no explicit Bash or Linux CLI script examples. Linux instructions are limited to generic statements like 'refer to distributor guidance,' and there are no concrete Linux command examples for tasks such as certificate updates or agent configuration. This may create friction for Linux users, especially those less familiar with Azure's Windows-centric tooling.
Recommendations
- Provide explicit Linux/Bash/CLI command examples alongside or before PowerShell examples, especially for scripting bulk VM protection.
- Include concrete steps or references for updating certificates and CRLs on popular Linux distributions (e.g., Ubuntu, RHEL).
- Clarify agent installation and configuration steps for Linux-based on-premises VMs, not just Windows (e.g., for MARS or alternatives).
- When listing OS-specific instructions, alternate the order or group them together to avoid always listing Windows first.
- Where possible, provide parity in screenshots and UI walkthroughs for both Windows and Linux environments.
Azure Resource Manager
Linter rule - no location expressions outside of parameter default values
...anager/bicep/linter-rule-no-loc-expr-outside-params.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation provides deployment guidance exclusively using Azure PowerShell commands, which are primarily Windows-centric. There are no examples or mentions of cross-platform alternatives such as Azure CLI, and the discussion of parameter naming conflicts is specific to PowerShell cmdlets. This creates friction for Linux/macOS users who typically use Azure CLI or other tools.
Recommendations
- Add equivalent Azure CLI examples for deployment scenarios, including parameter naming guidance.
- Mention that Azure CLI is cross-platform and provide links to relevant documentation.
- Clarify which guidance applies to PowerShell and which to CLI, so users can choose the appropriate workflow.
- Consider listing CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
Azure Resource Manager
Create multiple resource instances in Bicep
...icles/azure-resource-manager/bicep/quickstart-loops.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides deployment and cleanup instructions using Azure CLI and Azure PowerShell, but does not include explicit Linux/macOS shell examples (e.g., Bash). While Azure CLI is cross-platform, the examples use Windows-style variable assignment (resourceGroupName = "{provide-a-resource-group-name}") instead of Bash syntax (resourceGroupName="value"). PowerShell examples are given equal prominence, and Visual Studio Code is recommended, which is cross-platform, but no mention is made of Linux-specific tooling or shell environments. The documentation assumes familiarity with Windows/PowerShell patterns and does not address Linux/macOS users directly.
Recommendations
- Add explicit Bash examples for variable assignment and command usage, e.g., resourceGroupName="value" instead of resourceGroupName = "value".
- Clarify that Azure CLI commands work on Linux/macOS and provide shell-specific notes where syntax differs.
- Include a section or note for Linux/macOS users about environment setup and command usage.
- Consider listing Bash examples before PowerShell, or at least alternating order to avoid Windows-first bias.