Azure Resource Manager
504
Total Pages
312
Linux-Friendly Pages
192
Pages with Bias
38.1%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
1281 issues found
Showing 301-325 of 1281 flagged pages
Azure Resource Manager
Use Bicep to deploy resources to subscription
...azure-resource-manager/bicep/deploy-to-subscription.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 deploying Bicep files at the subscription scope. However, the PowerShell example is given equal prominence to Azure CLI, and there is no mention of Bash or Linux-specific shell usage. The references to deployment commands and further reading prioritize Azure PowerShell and do not mention Linux-native tools or workflows. There are no explicit Linux/Bash examples, and the documentation assumes familiarity with PowerShell, which is traditionally a Windows-centric tool.
Recommendations
- Add explicit Bash examples for Azure CLI usage, demonstrating deployment from a Linux shell.
- Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, while PowerShell is available on all platforms but is more familiar to Windows users.
- Include notes or sections on deploying Bicep files from Linux/macOS environments, including any platform-specific considerations (e.g., file paths, authentication).
- Ensure that Azure CLI examples appear before PowerShell examples, or provide both in parallel tabs with clear platform guidance.
- Reference Linux-native tools or workflows where applicable, such as scripting deployments in Bash or using automation tools common in Linux environments.
Create Pull Request
Azure Resource Manager
Create and deploy Azure deployment stacks in Bicep
...cles/azure-resource-manager/bicep/deployment-stacks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell examples are consistently presented first in all command sections, and the documentation refers to 'Azure PowerShell' and its cmdlets throughout, which are most commonly used and best supported on Windows. There is no mention of Linux-specific shell patterns (e.g., Bash, zsh), nor any guidance for Linux users regarding shell differences, environment setup, or command syntax variations. The CLI examples use generic syntax, but the overall structure and ordering prioritize Windows-centric tools and workflows.
Recommendations
- Alternate the order of examples so that Azure CLI (cross-platform) appears before Azure PowerShell, or present CLI examples first in each section.
- Explicitly mention that Azure CLI works natively on Linux/macOS and provide shell-specific notes or examples (e.g., Bash, zsh) where relevant.
- Add a brief section or note at the top clarifying platform compatibility for both Azure CLI and Azure PowerShell, including installation and usage notes for Linux/macOS.
- Where PowerShell is referenced, clarify that PowerShell Core is available cross-platform, but highlight any differences or limitations on Linux/macOS.
- Consider including troubleshooting tips or environment setup instructions for Linux users, especially for PowerShell commands.
- Review and update screenshots and portal instructions to ensure they are not Windows-specific (e.g., avoid showing Windows-only UI elements or file paths).
Azure Resource Manager
Configure development environment for deployment scripts in Bicep | Microsoft Docs
...manager/bicep/deployment-script-bicep-configure-dev.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell environments. PowerShell examples are given first and in greater detail, including all deployment, upload, and testing steps. Scripts for uploading files to Azure Storage use PowerShell exclusively, with no Bash or Linux-native alternatives. Docker usage instructions assume Windows-style drive mapping (e.g., d:/docker:/data), and do not provide Linux or macOS volume mount examples. The CLI (Bash) examples are present but less detailed, and the overall workflow is oriented around Windows tools and patterns.
Recommendations
- Provide Bash/Azure CLI equivalents for all PowerShell upload and deployment steps, including examples for uploading files to Azure Storage using az CLI and Bash.
- Include Linux/macOS Docker volume mount examples (e.g., -v /home/user/docker:/data) alongside Windows drive letter examples.
- Present CLI/Bash examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Clarify that the instructions are cross-platform and highlight any OS-specific differences, especially in file paths and Docker usage.
- Ensure parity in detail and completeness between PowerShell and Bash/CLI sections, including troubleshooting and output handling.
Azure Resource Manager
Develop a deployment script in Bicep
...re-resource-manager/bicep/deployment-script-develop.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias: PowerShell examples are given equal prominence to CLI/Bash, but Windows-specific tools and patterns (such as PowerShell, Connect-AzAccount, and references to Windows APIs like CommandLineToArgvW) are mentioned throughout. In some cases, Windows/PowerShell terminology and tools are referenced before or more thoroughly than their Linux equivalents. The CLI (Bash) examples are present and generally sufficient, but the documentation assumes familiarity with PowerShell and Windows-centric scripting patterns.
Recommendations
- Ensure that CLI/Bash examples are always presented before or alongside PowerShell examples, especially in introductory sections.
- Where Windows-specific APIs or tools are referenced (e.g., CommandLineToArgvW), provide equivalent Linux/Unix context or explain the cross-platform behavior.
- Add explicit notes about cross-platform compatibility, especially for users developing on Linux/macOS.
- Expand CLI/Bash troubleshooting and error-handling guidance to match the detail given for PowerShell (e.g., discuss Bash error handling, not just $ErrorActionPreference).
- Where PowerShell-specific advice is given (e.g., Start-Sleep), offer Bash equivalents (e.g., sleep).
- Review sample links and ensure parity in complexity and coverage between CLI/Bash and PowerShell samples.
Azure Resource Manager
Export Bicep files in Azure portal
...es/azure-resource-manager/bicep/export-bicep-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and the Azure portal (which is most commonly used on Windows) before mentioning Azure CLI or REST API. Examples and instructions for exporting Bicep files are exclusively shown via the Azure portal, with no Linux-specific or cross-platform command-line examples. The CLI is mentioned only as an alternative for exporting ARM JSON templates, not Bicep files, and PowerShell is listed before CLI in multiple places.
Recommendations
- Provide explicit Azure CLI examples for exporting ARM templates and decompiling to Bicep, highlighting cross-platform compatibility.
- List Azure CLI before Azure PowerShell when mentioning export options to avoid Windows-first ordering.
- Clarify that the Azure portal is accessible from any OS/browser, and mention any limitations or alternatives for Linux users.
- Add a section or note on how Linux/macOS users can perform equivalent operations using CLI and Bicep tools.
- Ensure parity in documentation by including screenshots or walkthroughs from non-Windows environments where relevant.
Azure Resource Manager
Troubleshoot problems with Bicep installation
...re-resource-manager/bicep/installation-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by providing troubleshooting steps and examples that are specific to Windows environments. The use of the 'where' command (Windows-only) is given without mention of the Linux equivalent ('which'), and the PATH modification instructions reference Windows environment variables and folder paths (e.g., %USERPROFILE%\.Azure\bin) exclusively. There are no Linux or macOS-specific instructions or examples for locating or managing Bicep CLI installations.
Recommendations
- Add Linux/macOS equivalents for all command-line instructions (e.g., use 'which bicep' for Linux/macOS).
- Include instructions for modifying the PATH variable on Linux/macOS (e.g., editing ~/.bashrc or ~/.zshrc).
- Mention the default installation paths for Bicep CLI on Linux/macOS, if applicable.
- Ensure troubleshooting steps are platform-agnostic or provide parallel instructions for each supported OS.
- Add screenshots or examples for Linux/macOS environments where relevant.
Azure Resource Manager
Install Bicep tools
.../main/articles/azure-resource-manager/bicep/install.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides extensive coverage of Windows-specific installation methods and tools (Windows Installer, Chocolatey, Winget, PowerShell), with detailed PowerShell scripts for manual installation. Windows installation options are listed with multiple package managers and a dedicated installer, while Linux and macOS are limited to shell scripts and Homebrew. The PowerShell example is more elaborate than the Linux/macOS equivalents, and Windows tools are mentioned before Linux alternatives in several sections. Although Linux and macOS instructions are present and functional, the overall emphasis and detail favor Windows environments.
Recommendations
- Add parity for Linux/macOS package managers (e.g., apt, yum, zypper for Linux; MacPorts for macOS) if available.
- Provide more detailed Linux/macOS installation scripts, including troubleshooting steps and PATH configuration examples.
- Include Bash/Zsh shell configuration examples for Linux/macOS similar to the PowerShell script for Windows.
- Present installation options in a neutral order (e.g., alphabetical or grouped by OS) rather than listing Windows tools first.
- Highlight cross-platform CLI usage and troubleshooting equally for all operating systems.
- Consider adding screenshots or step-by-step guides for Linux/macOS installation and configuration, matching the detail given for Windows.
Azure Resource Manager
Migrate Azure resources and JSON ARM templates to use Bicep
.../main/articles/azure-resource-manager/bicep/migrate.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows tools and patterns (such as Azure PowerShell and Visual Studio Code keyboard shortcuts) are mentioned before or alongside their Linux equivalents, but Linux-specific examples and tools are not highlighted. Azure PowerShell is referenced as a primary method for exporting resources, with no explicit mention of Bash or Linux shell scripting. Keyboard shortcuts are described with Windows notation first, and Linux is only mentioned as sharing the same shortcut, with macOS listed separately. There are no explicit Linux CLI or shell examples, and no mention of Linux-specific workflows or considerations.
Recommendations
- Provide explicit Linux/Bash shell examples for exporting resources and running Bicep commands, alongside PowerShell examples.
- List Azure CLI usage before or alongside Azure PowerShell, and clarify that both work cross-platform.
- Include Linux-specific notes or considerations where workflows may differ (e.g., file paths, environment setup).
- When describing keyboard shortcuts, avoid Windows-first notation; instead, present shortcuts for all platforms equally.
- Reference Linux-native editors (such as Vim or VS Code on Linux) and their integration with Bicep, if applicable.
- Ensure that all tools and commands mentioned are available and documented for Linux users, and provide links to relevant Linux documentation.
Azure Resource Manager
Bicep null-forgiving operator
...zure-resource-manager/bicep/operator-null-forgiving.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell and Visual Studio Code as the primary tools for deploying and authoring Bicep files. Azure CLI is mentioned, but Azure PowerShell is listed first, and no Linux-specific editors or deployment methods are discussed. There are no examples or guidance for using Linux-native tools or editors, nor is there mention of Linux shell usage (e.g., Bash).
Recommendations
- Provide explicit Linux/Bash examples for deploying Bicep files using Azure CLI.
- Mention and link to Linux-native editors (e.g., Vim, Emacs, VS Code on Linux) for authoring Bicep files.
- List Azure CLI before Azure PowerShell when discussing deployment options, as CLI is cross-platform.
- Clarify that all examples and tools are cross-platform where applicable, and provide instructions for both Windows and Linux environments.
- Include troubleshooting or environment setup notes for Linux users.
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
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. While both Azure CLI and Azure PowerShell examples are provided throughout, PowerShell examples (which are Windows-centric) are always present and sometimes more detailed (e.g., use of ConvertTo-SecureString). The only platform-specific scenario referenced is a Windows VM (WinRM), with no mention of Linux VM equivalents. There is no explicit mention of Linux shell usage (bash/zsh), nor any Linux-specific patterns or troubleshooting. The ordering of examples does not always favor Windows, but Windows tools and scenarios are referenced exclusively in some cases.
Recommendations
- Add explicit Linux VM scenarios and references, such as a quickstart template for SSH on a Linux VM using Key Vault secrets.
- Include bash/zsh shell command examples where appropriate, especially for scripting deployments.
- Clarify that Azure CLI commands work cross-platform and provide notes on usage in Linux/macOS environments.
- Balance references to Windows and Linux in scenario links and related content.
- Ensure that PowerShell-specific constructs (like ConvertTo-SecureString) are explained or alternatives are provided for non-Windows users.
Azure Resource Manager
Linter rule - no location expressions outside of parameter default values
...anager/bicep/linter-rule-no-loc-expr-outside-params.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page provides deployment guidance and examples exclusively using Azure PowerShell commands, which are most commonly used on Windows. There is no mention of cross-platform alternatives such as Azure CLI, nor are Linux-specific patterns or tools referenced. The discussion of parameter naming conflicts is focused solely on PowerShell cmdlets, with no equivalent information for other deployment tools.
Recommendations
- Include Azure CLI examples alongside PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Mention that Azure CLI does not have the same parameter naming conflicts as PowerShell, or document any equivalent issues if they exist.
- Add a section or note clarifying that the guidance applies regardless of OS, and reference Linux/macOS usage where relevant.
- Provide links to documentation for Azure CLI deployment commands (e.g., az deployment group create) in addition to PowerShell cmdlets.
- Ensure that examples and troubleshooting steps are not Windows-centric and are applicable to users on all platforms.
Azure Resource Manager
Migrate blueprints to deployment stacks
...cles/azure-resource-manager/bicep/migrate-blueprint.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell in the export step and linking to a PowerShell-specific guide for exporting blueprint definitions. There is no mention of Linux or cross-platform alternatives (such as Azure CLI) for this step. Additionally, instructions for configuring DenySettingsMode mention both Azure CLI and PowerShell, but PowerShell is listed first, and no explicit CLI example is provided. No Linux-specific or cross-platform command examples are included.
Recommendations
- Provide Azure CLI examples alongside PowerShell for exporting blueprint definitions and configuring DenySettingsMode.
- Link to both PowerShell and Azure CLI documentation for relevant steps.
- Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and clarify tool parity.
- Ensure sample commands and references are platform-neutral or include both Windows and Linux variants.
Azure Resource Manager
Quickstart: Use MSBuild tasks to convert Bicep files and parameters to JSON
...les/azure-resource-manager/bicep/msbuild-bicep-file.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias by consistently presenting Windows and PowerShell examples first and exclusively, especially in command-line instructions and project setup. Directory paths, shell commands, and cleanup steps use Windows conventions (e.g., C:\ paths, PowerShell cmdlets) without providing equivalent Linux/macOS examples. The use of PowerShell is assumed throughout, and there are no bash or Linux terminal instructions. Package references and environment variable configuration do mention Linux and macOS options, but practical usage steps and screenshots are Windows-centric.
Recommendations
- Provide parallel examples for Linux/macOS users, including bash/zsh commands for directory creation, navigation, and cleanup.
- Include Linux/macOS directory path conventions (e.g., /home/user/msBuildDemo) alongside Windows paths.
- Show how to run MSBuild and dotnet CLI commands in Linux/macOS terminals, including installation prerequisites for those platforms.
- Add tabs or sections for Linux/macOS in all step-by-step instructions, not just in package reference tables.
- Offer cleanup instructions using Linux commands (e.g., rm -rf ~/msBuildDemo).
- Clarify that Visual Studio Code and the Bicep extension are cross-platform, and provide guidance for installing them on Linux/macOS.
- Ensure screenshots and sample outputs do not exclusively use Windows file paths.
Azure Resource Manager
Bicep safe-dereference operator
...re-resource-manager/bicep/operator-safe-dereference.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell and Visual Studio Code (a Microsoft tool) as the primary ways to deploy and author Bicep files. Azure CLI is mentioned, but PowerShell is listed first, and there are no Linux-specific instructions or examples. The guidance assumes familiarity with Windows-centric tools and workflows, with no mention of Linux editors or deployment methods.
Recommendations
- Provide explicit Linux deployment instructions, such as using Azure CLI from Bash or shell scripts.
- Include examples for deploying Bicep files on Linux/macOS, not just PowerShell.
- Mention and link to cross-platform editors (e.g., VS Code, Vim, Emacs) and clarify that VS Code is available on Linux/macOS.
- List Azure CLI before PowerShell, or present both equally, to avoid implying a Windows-first workflow.
- Add troubleshooting or environment setup notes for Linux users.
Azure Resource Manager
Bicep accessor operators
...icles/azure-resource-manager/bicep/operators-access.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where Azure PowerShell is mentioned alongside Azure CLI as the way to deploy Bicep files, and Visual Studio Code is referenced as the editor. There are no explicit Linux shell (bash) deployment examples, nor is there mention of Linux-native editors or workflows. All example code is platform-neutral, but the guidance for running and authoring Bicep files leans toward Windows tools and patterns.
Recommendations
- Add explicit Linux shell (bash) deployment instructions and examples, such as using 'az deployment' commands in bash.
- Mention Linux-native editors (e.g., Vim, Emacs) or provide guidance for using Visual Studio Code on Linux.
- Ensure that references to Azure PowerShell are balanced with Azure CLI, and clarify that Azure CLI is cross-platform and can be used on Linux and macOS.
- Consider adding a section or note highlighting cross-platform support and workflows for Bicep, including links to Linux-specific documentation.
Azure Resource Manager
Create a parameters file for bicep deployment
...ticles/azure-resource-manager/bicep/parameter-files.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. All Azure PowerShell examples use Windows-style paths (e.g., C:\MyTemplates\...), and only Windows PowerShell is referenced for command-line deployment. There is no mention of Linux equivalents (such as bash, sh, or pwsh), nor are Linux/macOS file path conventions shown. Visual Studio Code is referenced as the editor, but without explicit mention of cross-platform usage. Azure CLI examples are platform-neutral, but PowerShell sections are Windows-centric.
Recommendations
- Include Linux/macOS path examples alongside Windows paths in PowerShell command samples (e.g., use /home/user/templates/storage.bicep).
- Mention that Azure PowerShell is available on Linux/macOS via pwsh, and provide example commands using those environments.
- Clarify that Visual Studio Code and Bicep CLI are cross-platform, and provide installation or usage notes for Linux/macOS users.
- Add notes or tabs for Bash or shell scripting where appropriate, especially for deployment automation.
- Avoid using only Windows-style paths in examples; show both styles or use placeholders that are platform-agnostic.
Azure Resource Manager
Create a private container registry in Azure for Bicep modules
...zure-resource-manager/bicep/private-module-registry.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are consistently presented before Azure CLI equivalents, and the documentation refers to Windows-specific tools and environment variables (e.g., %USERPROFILE%). There is a lack of parity in some explanations, such as more detailed path examples for Windows than for Linux/Mac. While Azure CLI (cross-platform) is included, the structure and ordering favor Windows/PowerShell users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (cross-platform) examples first to promote neutrality.
- Ensure all path examples are equally detailed for Linux and Mac, not just Windows. For example, provide full Linux and Mac path examples with placeholders matching the Windows example.
- Where Windows environment variables (e.g., %USERPROFILE%) are mentioned, also mention the Linux/Mac equivalents (e.g., $HOME).
- Add explicit notes that Azure CLI commands work identically on Windows, Linux, and Mac, and encourage use of CLI for cross-platform scenarios.
- Where possible, avoid Windows-centric terminology or tools unless absolutely necessary, or provide Linux/Mac alternatives in parallel.
Azure Resource Manager
Create Bicep files - Visual Studio
...ger/bicep/quickstart-create-bicep-use-visual-studio.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Visual Studio (a Windows-centric IDE) for Bicep file creation, listing Visual Studio as the primary tool in prerequisites and instructions. While it briefly mentions Visual Studio Code as an alternative, all step-by-step guidance is for Visual Studio. Additionally, deployment and cleanup instructions provide both Azure CLI and Azure PowerShell examples, but PowerShell (a Windows-native tool) is given equal prominence, and no Linux-specific shell or editor workflows are discussed. There are no Linux-specific instructions, screenshots, or troubleshooting tips.
Recommendations
- Provide parallel instructions and screenshots for Visual Studio Code, which is cross-platform, or clarify that Visual Studio is Windows-only.
- Explicitly mention platform compatibility for each tool and extension (e.g., note that Visual Studio is Windows-only, while VS Code works on Linux/Mac).
- Include Linux-specific examples, such as using Bash with Azure CLI, and troubleshooting tips for Linux environments.
- Add links or references to Linux editor workflows (e.g., Vim, Emacs, VS Code on Linux) for Bicep authoring.
- Ensure that CLI examples are shown first or equally with PowerShell, and clarify that PowerShell Core is available cross-platform if relevant.
Azure Resource Manager
Create and deploy a template spec with Bicep
...urce-manager/bicep/quickstart-create-template-specs.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias by consistently using Windows-style file paths (e.g., C:\templates\main.bicep) in all command examples, regardless of whether Azure CLI or PowerShell is being used. There are no explicit Linux/macOS examples or notes on path differences. Additionally, PowerShell is presented as a primary tool alongside Azure CLI, and the only editor recommended is Visual Studio Code. There is also a reference to a PowerShell-specific tutorial for role assignments. No Linux-specific tools, shell commands, or considerations are mentioned.
Recommendations
- Provide both Windows and Linux/macOS path examples for file locations in all CLI and PowerShell commands (e.g., C:\templates\main.bicep and ~/templates/main.bicep).
- Add notes or tabs to clarify differences in command syntax or file paths between Windows and Linux/macOS environments.
- Include bash/zsh shell examples where appropriate, especially for Azure CLI usage.
- Reference cross-platform editors (such as VS Code, Sublime Text, Atom) and clarify that the Bicep extension is available on all platforms.
- When linking to tutorials or further reading, provide both PowerShell and CLI (bash) options, or ensure parity in Linux/macOS guidance.
- Explicitly state that all commands are cross-platform unless otherwise noted, and highlight any known issues or differences for Linux/macOS users.
Azure Resource Manager
Create and deploy template specs in Bicep
...rticles/azure-resource-manager/bicep/template-specs.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently presenting Azure PowerShell (a Windows-centric tool) examples before Azure CLI, and by referencing PowerShell scripts and integration with DevOps pipelines (which are often Windows-based). There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments. The documentation assumes familiarity with PowerShell and Windows conventions, such as parameter passing and script syntax, without providing parity for Linux users.
Recommendations
- Alternate the order of examples so that Azure CLI (cross-platform) is shown before Azure PowerShell, or present both side-by-side.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample Bash shell usage (e.g., variable assignment, command chaining).
- Include notes or examples for Linux/macOS users, such as using Bash for scripting deployments, handling file paths, and environment variables.
- Avoid language that implies PowerShell is the default or preferred tool; clarify that both CLI and PowerShell are supported equally.
- Where PowerShell scripts are referenced for integration, provide equivalent Bash script examples for Linux users.
- Add troubleshooting or installation notes for Azure CLI and PowerShell on Linux/macOS platforms.
Azure Resource Manager
Create a custom resource provider
...rce-manager/custom-providers/create-custom-provider.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for all operations, which is good for cross-platform parity. However, in the PowerShell section, it recommends ARMClient—a Windows-only .exe tool—for REST operations, without mentioning Linux alternatives (such as curl or httpie). There are no Linux-specific examples or guidance for users who prefer Bash or native Linux tools for REST calls, and the PowerShell examples assume a Windows environment. This creates a subtle Windows bias, especially in the tooling recommendations.
Recommendations
- In the PowerShell section, mention that ARMClient is Windows-only and suggest Linux/macOS alternatives such as curl, httpie, or using PowerShell Core on Linux.
- Provide explicit Bash/curl examples for REST operations alongside Azure CLI and PowerShell, or at least mention that Azure CLI and PowerShell Core are cross-platform.
- Clarify that PowerShell 7+ and Azure CLI are available on Linux and macOS, and provide installation links for those platforms.
- Avoid recommending Windows-only tools (like ARMClient) without cross-platform alternatives.
- Add a note or tab for Linux users, showing how to perform REST operations with native tools.
Azure Resource Manager
Use Bicep to deploy an Azure Managed Application definition
...anager/managed-applications/deploy-bicep-definition.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation consistently presents Windows-centric tools and patterns first, such as PowerShell and Visual Studio Code, and assumes the use of Windows terminals (PowerShell) before Linux equivalents (Bash/Azure CLI). Visual Studio Code is recommended as the editor, which is popular on Windows but less so on Linux. There are no explicit Linux-specific instructions, and the examples for command-line usage are split between PowerShell and Azure CLI, but PowerShell is always listed first. There is no mention of Linux-native editors or shell environments beyond Bash, nor any guidance for non-Windows users regarding setup or troubleshooting.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to avoid implicit Windows prioritization.
- Include explicit instructions or notes for Linux users, such as using native editors (e.g., Vim, Nano) and shell environments.
- Mention cross-platform alternatives to Visual Studio Code, or clarify that VS Code is available on Linux and macOS.
- Add troubleshooting or setup notes for Linux environments, such as package manager installation commands for Azure CLI and Bicep.
- Consider including examples for MacOS users, or a general note on cross-platform compatibility for all tools and commands.
Azure Resource Manager
Develop ARM templates for cloud consistency
...source-manager/templates/template-cloud-consistency.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: PowerShell is frequently used for scripting and verification examples, often presented before or alongside Azure CLI but with more detailed PowerShell workflows; examples of VM extensions and scripts focus on Windows (e.g., configure-music-app.ps1, CustomScriptExtension for Windows); references to Windows-specific tools and patterns (such as Visual Studio and PowerShell DSC) are prevalent; and there is a lack of Linux-specific examples for VM images, extensions, and scripting, with no mention of Bash scripts or Linux VM extension usage.
Recommendations
- Provide Linux-focused examples alongside Windows ones, such as using Bash scripts for VM extensions and referencing Linux VM images (e.g., Ubuntu, CentOS) in ARM templates.
- Balance scripting examples by including Bash/Azure CLI workflows wherever PowerShell is shown, especially for verification and resource queries.
- Mention and demonstrate Linux-compatible development tools (e.g., VS Code on Linux, cross-platform editors) in the testing and automation section.
- Show examples of deploying and configuring Linux VM extensions (e.g., CustomScriptExtension with .sh files, OMI/OMS agents) and how to retrieve their available versions.
- Reference Linux-specific documentation links and best practices where relevant, ensuring parity in guidance for both Windows and Linux environments.
Azure Resource Manager
Template functions - scope
...resource-manager/templates/template-functions-scope.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page provides ARM template function references and examples, but in the 'Next steps' section, it exclusively links to instructions for deploying templates using Azure PowerShell, which is Windows-centric. There are no references to Linux-native tools (such as Azure CLI or Bash scripting), nor are examples provided for Linux environments. This suggests a Windows-first and PowerShell-heavy bias, with missing Linux deployment examples.
Recommendations
- Add links and examples for deploying ARM templates using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
- Include Bash scripting examples for template deployment to demonstrate Linux parity.
- In the 'Next steps' section, mention both Azure PowerShell and Azure CLI equally, and provide guidance for both Windows and Linux users.
- Review other referenced documentation (such as 'deploy-powershell.md') to ensure Linux-friendly instructions are present and visible.
Azure Resource Manager
Convert portal template to template spec
...re-resource-manager/templates/template-spec-convert.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell-based migration instructions, referencing a PowerShell script, and omitting any Linux or cross-platform CLI alternatives. The only automated migration method described uses PowerShell, which is natively available only on Windows (though PowerShell Core is cross-platform, this is not clarified). No Bash, Azure CLI, or Linux shell examples are given, and Windows-centric terminology and tools are presented first and exclusively.
Recommendations
- Add equivalent instructions for using Azure CLI or Bash scripts to perform the migration, ensuring Linux users have a clear path.
- Clarify whether the provided PowerShell script is compatible with PowerShell Core on Linux/macOS, and provide installation guidance if so.
- Present cross-platform options (e.g., Azure CLI, REST API) before or alongside PowerShell examples to avoid Windows-first bias.
- Explicitly mention Linux/macOS compatibility in all automation steps and provide examples for those platforms.
- Consider providing downloadable scripts or templates in multiple formats (PowerShell, Bash, Azure CLI) for parity.