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 301-325 of 492 flagged pages
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/copy-outputs.md
...icles/azure-resource-manager/templates/copy-outputs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation references Azure PowerShell before Azure CLI when discussing version requirements for supporting zero count in copy loops. The 'Next steps' section links only to a PowerShell deployment guide, omitting equivalent Linux-first or CLI-focused guides. There are no explicit Linux or cross-platform examples or instructions, and the CLI is mentioned only after PowerShell.
Recommendations
- When listing supported tools or version requirements, mention Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
- In the 'Next steps' section, add links to documentation for deploying ARM templates using Azure CLI and Bash, not just PowerShell.
- Where possible, provide cross-platform or CLI-based examples and instructions, or clarify that the steps apply equally to Linux, macOS, and Windows.
- Explicitly state that both Azure CLI and PowerShell are cross-platform, and provide guidance for users on Linux systems.
Create Pull Request
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/best-practices.md
...les/azure-resource-manager/templates/best-practices.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page shows mild Windows bias. It references PowerShell-specific deployment behavior and parameter naming conflicts, and discusses the PowerShell cmdlet New-AzResourceGroupDeployment without mentioning equivalent Azure CLI or Linux-native tools. In the section on connecting to virtual machines, Windows connection methods (RDP, WinRM) are listed before Linux, and two Windows-specific links are provided versus one for Linux. There are no explicit Linux shell or Azure CLI examples, and the only mention of Linux is in a link to 'Connect to a Linux VM.'
Recommendations
- When discussing parameter naming conflicts, mention both PowerShell and Azure CLI behaviors, and provide equivalent examples for Azure CLI (e.g., az deployment group create).
- In sections referencing deployment commands, include both PowerShell and Azure CLI examples, or clarify that the behavior applies to both.
- When listing connection methods for VMs, alternate or balance the order of Windows and Linux examples, and provide parity in the number of links for each platform.
- Add examples or references for Linux-native tools and workflows, such as Bash scripting or Azure CLI usage, alongside PowerShell examples.
- Review the documentation for other subtle Windows-first language or assumptions, and ensure Linux users are equally addressed.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deploy-cloud-shell.md
...azure-resource-manager/templates/deploy-cloud-shell.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI (Bash) and PowerShell examples for deploying ARM templates in Cloud Shell, but PowerShell (a Windows-centric tool) is consistently mentioned alongside or immediately after Bash. Visuals and instructions frequently reference toggling between Bash and PowerShell, and 'PowerShell' is often listed first or equally with Bash, despite Bash being the default and more common shell for Linux users. The 'Next steps' section links to both CLI and PowerShell guides, but PowerShell is given equal prominence, which may reinforce Windows-centric patterns.
Recommendations
- Prioritize Bash/Azure CLI instructions and visuals before PowerShell, reflecting the default Linux shell experience in Cloud Shell.
- Explicitly state that Bash/Azure CLI is cross-platform and the default for Cloud Shell, while PowerShell is optional.
- Add notes or sections highlighting Linux-specific workflows or considerations, such as file paths, permissions, or scripting differences.
- Ensure that all examples and screenshots default to Bash unless PowerShell is specifically required.
- Review and adjust the order of 'Next steps' links to feature CLI/Bash resources first, followed by PowerShell as an alternative.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deployment-history.md
...azure-resource-manager/templates/deployment-history.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure Portal, PowerShell, Azure CLI, and REST API. PowerShell is given equal prominence to Azure CLI, but PowerShell is a Windows-centric tool, and its examples are listed before Azure CLI in every section. There are no Linux shell (bash) or scripting examples, nor any mention of Linux-specific tools or patterns. The documentation assumes PowerShell is universally available, which may disadvantage Linux users who typically use bash or other shells.
Recommendations
- Add bash shell examples for Azure CLI commands to demonstrate usage in Linux environments.
- Explicitly mention that PowerShell examples are primarily for Windows users, and Azure CLI examples are cross-platform.
- Consider providing scripting examples using bash or zsh for common deployment tasks.
- Clarify tool availability and installation instructions for both Windows and Linux users.
- Ensure that Azure CLI examples are listed before or alongside PowerShell examples to avoid Windows-first ordering.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/quickstart-create-templates-use-visual-studio-code.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/quickstart-create-templates-use-visual-studio-code.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment and cleanup, but consistently lists PowerShell as an equal alternative to CLI rather than emphasizing cross-platform parity. The use of PowerShell (which is traditionally associated with Windows, though now cross-platform) and the mention of Windows-style keyboard shortcuts (ALT + SHIFT + F) and the integrated terminal shortcut (ctrl + `) may be more familiar to Windows users. There are no explicit Linux/macOS-specific instructions or examples, and no mention of Bash or shell scripting. The CLI is listed first, but the parity is not fully emphasized.
Recommendations
- Explicitly mention that both Azure CLI and PowerShell are cross-platform, and clarify that CLI commands work on Linux/macOS as well as Windows.
- Add Linux/macOS-specific keyboard shortcuts for formatting and opening the terminal in VS Code (e.g., CMD + SHIFT + I for formatting on macOS).
- Include a brief note or section for users on Linux/macOS, confirming that all steps are supported on those platforms.
- Consider including Bash shell script examples for deployment and cleanup, or at least mention that Azure CLI commands can be run in Bash.
- Avoid implying that PowerShell is the default or preferred method unless it is truly cross-platform and commonly used on all platforms.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-add-outputs.md
...rce-manager/templates/template-tutorial-add-outputs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Azure PowerShell instructions before Azure CLI, and the CLI example uses Bash-style syntax but does not explicitly mention Linux or macOS. There are no explicit Linux/macOS-specific instructions, and the prerequisites mention Azure PowerShell before Azure CLI. No Linux-specific tools or shell examples are provided, and the only editor mentioned is Visual Studio Code, which is cross-platform.
Recommendations
- Present Azure CLI instructions before PowerShell, or provide both side-by-side to avoid implying a Windows-first workflow.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide shell-specific notes if needed.
- Include Linux/macOS-specific instructions or troubleshooting notes where relevant (e.g., file path syntax, environment variable usage).
- Consider mentioning other popular editors available on Linux, or clarify that Visual Studio Code is cross-platform.
- Add a note that both Azure PowerShell and Azure CLI are available on all major platforms, and users can choose their preferred tool.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-create-multiple-instances.md
...mplates/template-tutorial-create-multiple-instances.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias. Visual Studio Code is listed as the only prerequisite editor, which is cross-platform but often associated with Windows. In deployment instructions, PowerShell is mentioned before Bash/CLI, and PowerShell examples are provided alongside CLI examples. The Azure portal instructions use Windows-centric UI terms (e.g., 'File > Open File'), and the file upload screenshot is from the Azure portal, which is most commonly used on Windows. However, Linux/CLI examples are present and not omitted.
Recommendations
- Explicitly mention that Visual Studio Code is available on Linux and macOS, or suggest alternative editors (e.g., vim, nano) for Linux users.
- Present Bash/CLI instructions before PowerShell, or alternate the order to avoid implicit prioritization.
- Include screenshots or instructions for Linux file navigation/upload where relevant.
- Clarify that the Azure portal and Cloud Shell are cross-platform and accessible from any OS.
- Add a note that all steps can be performed on Linux, macOS, or Windows, and highlight any OS-specific differences if they exist.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/overview.md
...les/azure-resource-manager/troubleshooting/overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page shows a mild Windows bias by mentioning Azure PowerShell before Azure CLI when discussing error details and troubleshooting commands. PowerShell commands are referenced first, and in more detail, which may suggest a preference for Windows tooling. There are no explicit Linux-only examples or tools, and the CLI is only mentioned after PowerShell. No Linux-specific troubleshooting patterns or tools are highlighted.
Recommendations
- Present Azure CLI examples and commands before or alongside Azure PowerShell to avoid implying a preference for Windows tools.
- Include explicit Linux/macOS troubleshooting scenarios or notes where relevant.
- Ensure parity in the depth of explanation and linking for both Azure CLI and PowerShell commands.
- Mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
- Where possible, provide Bash shell examples in addition to PowerShell.
Azure Resource Manager
Template functions - resources
...ource-manager/templates/template-functions-resource.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for discovering list operations, but the PowerShell (Windows-centric) example is presented before the Azure CLI (cross-platform) example. No other evidence of Windows bias is present; all code samples are in JSON ARM template syntax, which is platform-agnostic.
Recommendations
- Present Azure CLI examples before PowerShell examples, or provide both side-by-side to emphasize cross-platform parity.
- Explicitly note that Azure CLI is available on Linux/macOS/Windows when giving CLI examples.
- Where possible, link to cross-platform deployment guides (e.g., deploying ARM templates with Azure CLI) in the 'Next steps' section.
Azure Resource Manager
Template functions - resources
...ource-manager/templates/template-functions-resource.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for discovering list operations, but the PowerShell example is presented first. No other evidence of Windows bias is present: all code samples are in ARM template JSON, which is platform-agnostic, and there are no references to Windows-specific tools or patterns. The page does not omit Linux/macOS equivalents, and the only minor bias is the ordering of PowerShell before CLI.
Recommendations
- Present Azure CLI and PowerShell examples side-by-side or alternate which is shown first.
- Explicitly note that both Azure CLI and PowerShell are cross-platform, and users can choose either based on their environment.
- Consider adding a short note for Linux/macOS users clarifying that all template examples are platform-neutral and can be used on any OS.
Azure Resource Manager
Template functions - resources
...ource-manager/templates/template-functions-resource.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and focused on ARM template functions, which are platform-agnostic. However, in the section describing how to determine which resource types have a list operation, the PowerShell example is presented before the Azure CLI example. This ordering may subtly favor Windows/PowerShell users, but both Windows and Linux/macOS users are provided with equivalent instructions.
Recommendations
- Present Azure CLI and PowerShell examples side-by-side or alternate the order to avoid implicit prioritization.
- Explicitly state that both Azure CLI and PowerShell are available on all major platforms, and provide links to installation guides for each.
- Where possible, include Bash or shell scripting examples for Linux/macOS users, especially in sections where command-line usage is demonstrated.
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 largely platform-neutral in its technical content and examples, focusing on Bicep syntax. However, in the 'Next steps' section, Windows-centric tools (Azure PowerShell, Visual Studio Code) are mentioned first or exclusively, and there is no explicit mention of Linux/macOS alternatives or parity (e.g., Azure CLI usage on Linux, VS Code alternatives, or cross-platform deployment instructions).
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide example commands for both Azure CLI and Azure PowerShell.
- Clarify that Visual Studio Code is available on Linux/macOS, or suggest other editors if applicable.
- Add a note or section on deploying Bicep files from Linux/macOS, including any platform-specific considerations.
- Ensure that instructions and links do not imply Windows is the default or only supported environment.
Azure Resource Manager
Template functions - deployment
...rce-manager/templates/template-functions-deployment.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Summary
The documentation is largely platform-neutral, focusing on ARM template functions and their outputs. However, in the 'environment' section, when listing commands to view registered Azure environments, the Windows PowerShell cmdlet 'Get-AzEnvironment' is mentioned alongside the cross-platform 'az cloud list' CLI command. No Linux/macOS-specific tools or shell examples are provided, but the CLI command is listed first.
Recommendations
- Clarify that both 'az cloud list' and 'Get-AzEnvironment' are available on all platforms, but 'az cloud list' is cross-platform while 'Get-AzEnvironment' is PowerShell-specific.
- Provide example usage for both commands, noting platform compatibility.
- Consider adding a note or table summarizing which commands/tools are available on Windows, Linux, and macOS.
- If mentioning PowerShell, also mention Bash or other common Linux/macOS shells where relevant.
Azure Resource Manager
Bicep functions - deployment
...e-resource-manager/bicep/bicep-functions-deployment.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references both Windows PowerShell (Get-AzEnvironment) and Azure CLI (az cloud list) tools for listing Azure environments, but lists the PowerShell command first and provides a direct link to its documentation before the CLI equivalent. No Linux/macOS-specific examples or guidance are given, and the overall examples are platform-neutral otherwise.
Recommendations
- List Azure CLI (az cloud list) before PowerShell commands, as CLI is cross-platform.
- Provide explicit Linux/macOS usage notes or examples where relevant.
- Clarify that both tools are available cross-platform, but CLI is natively supported on Linux/macOS.
- Add links to Azure CLI installation and usage guides for Linux/macOS users.
Azure Resource Manager
Bicep functions - resources
...ure-resource-manager/bicep/bicep-functions-resource.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page provides both Azure CLI and PowerShell examples for discovering list operations, but the PowerShell example (Get-AzProviderOperation) is presented first and is more detailed. The CLI example is present but less emphasized. There are no Linux/macOS-specific examples or mentions of platform differences. No examples rely on Windows-only tools, but the ordering and emphasis slightly favor Windows/PowerShell users.
Recommendations
- Present Azure CLI examples before PowerShell examples to avoid implicit Windows-first bias.
- Expand Azure CLI examples with more context and explanation, matching the detail given to PowerShell.
- Explicitly state that both CLI and PowerShell commands work cross-platform and provide links to installation guides for Linux/macOS.
- Consider adding a note or example for using Bicep and related tools on Linux/macOS, if relevant.
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 consistently presents Azure PowerShell examples before Azure CLI examples in every code tab, and PowerShell is referenced as a primary tool throughout. This ordering and emphasis may subtly favor Windows users, as PowerShell is natively available on Windows and historically associated with that platform. However, Azure CLI is cross-platform and all examples are provided for both tools, with no actual functionality missing for Linux/macOS users. No Windows-only tools or patterns are used, and all commands are available via Azure CLI, which works on Linux/macOS.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to reflect cross-platform parity.
- Explicitly state that both Azure PowerShell and Azure CLI are available on all major platforms, including Linux and macOS.
- Where possible, highlight CLI usage as the default for scripting and automation, since it is more universally available.
- Add a short section clarifying that PowerShell Core is available for Linux/macOS, and link to installation instructions for non-Windows platforms.
- Consider a single combined example section (CLI and PowerShell side-by-side) for brevity and parity.
Azure Resource Manager
Develop a deployment script in Bicep
...re-resource-manager/bicep/deployment-script-develop.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI (Bash) and Azure PowerShell examples for every major scenario, maintaining parity in most technical content. However, there are signs of Windows bias: PowerShell is treated as a first-class scripting option throughout, and Windows-specific tools and APIs (e.g., CommandLineToArgvW, Connect-AzAccount) are referenced. The documentation sometimes references Windows concepts (e.g., .ps1 scripts, PowerShell cmdlets) and APIs before or more prominently than their Linux equivalents. The use of PowerShell as a primary scripting language, and references to Windows APIs, may create friction for Linux/macOS users who are less familiar with these tools.
Recommendations
- Clarify that PowerShell is cross-platform and provide explicit notes or links for Linux/macOS users on installing and using PowerShell Core.
- Where Windows-specific APIs (e.g., CommandLineToArgvW) are referenced, explain how argument parsing works on Linux/macOS, or note that this is abstracted away in the container environment.
- Add a short section or callout for Linux/macOS users, highlighting any differences in script authoring, file permissions, or environment setup.
- Ensure that CLI (Bash) examples are shown before or alongside PowerShell examples, rather than after.
- Explicitly mention that both Bash and PowerShell containers run on Ubuntu, and clarify any OS-specific behaviors or limitations.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Summary
The documentation page references Visual Studio Code and the Bicep CLI, both of which are cross-platform tools. However, there is a minor bias in the linter rule list: the rule 'use-recent-az-powershell-version' references PowerShell, which is traditionally associated with Windows, though it is now available on Linux/macOS. No command-line examples are shown, and no Windows-specific tools or patterns are prioritized. The page does not provide Linux/macOS-specific examples or mention platform-specific differences.
Recommendations
- Clarify that both Visual Studio Code and Bicep CLI are available on Windows, Linux, and macOS.
- If referencing PowerShell, note that PowerShell Core is cross-platform and provide equivalent Bash/Azure CLI guidance where relevant.
- Add explicit command-line examples for both Windows (PowerShell/CMD) and Linux/macOS (Bash) to demonstrate parity.
- Mention any platform-specific considerations for using the Bicep linter, if any exist.
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
Missing Linux Example
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for key tasks, but PowerShell (a Windows-centric tool) is consistently listed first. There is a notable emphasis on PowerShell commands and references to Windows-specific paths. Linux and macOS equivalents are mentioned for local cache paths, but command-line examples do not include explicit Linux/macOS shell variants (e.g., Bash). No Linux-specific tools or workflows are described, and the documentation assumes familiarity with Windows tooling and patterns.
Recommendations
- Alternate the order of Azure PowerShell and Azure CLI examples, or present CLI examples first to reduce implicit Windows prioritization.
- Add explicit Bash/zsh shell examples for Linux/macOS users where relevant, especially for file paths and environment variables.
- Highlight cross-platform usage of Azure CLI, and clarify that PowerShell is available on Linux/macOS but is less commonly used.
- Include troubleshooting or tips for Linux/macOS users, such as permissions or path expansion nuances.
- Reference Linux/macOS documentation links alongside Windows-specific ones.
Azure Resource Manager
Create Bicep files with Visual Studio Code
...les/azure-resource-manager/bicep/visual-studio-code.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is generally cross-platform, focusing on Visual Studio Code and Bicep, which are available on Windows, Linux, and macOS. However, there are subtle Windows biases: Azure PowerShell is mentioned alongside Azure CLI as a prerequisite, and PowerShell examples are provided in parallel with CLI examples. In the 'Insert Resource' section, Azure CLI is listed before Azure PowerShell, but both are given equal prominence. There are no Linux-specific tools or patterns mentioned, and no macOS-specific considerations. The documentation does not provide Linux/macOS-specific troubleshooting or example screenshots, but it does not prevent Linux/macOS users from completing tasks.
Recommendations
- Explicitly state that all instructions and tools (VS Code, Bicep extension, Azure CLI) work on Linux and macOS as well as Windows.
- Include Linux/macOS-specific notes or screenshots where relevant (e.g., keyboard shortcuts, file paths).
- When listing command-line tools, clarify that Azure CLI is cross-platform and highlight its parity with PowerShell.
- Add troubleshooting tips for Linux/macOS environments if there are known issues (e.g., permissions, installation paths).
- Avoid implying PowerShell is required or preferred; emphasize CLI as the default for cross-platform use.
Azure Resource Manager
What are the resource providers for Azure services
...anager/management/azure-services-resource-providers.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page lists resource providers for Azure services and provides examples for finding resource providers using Azure CLI, PowerShell, and Python SDK. There is a minor Windows bias: PowerShell (a Windows-centric tool) is given as an example alongside CLI and Python, and references to 'Windows Azure Service Management API' and 'Azure Serial Console for Windows' appear in the text. However, Linux/macOS users are not blocked from completing any tasks, as Azure CLI and Python examples are cross-platform.
Recommendations
- Clarify that PowerShell examples are primarily for Windows users, and suggest Bash or shell alternatives for Linux/macOS.
- Where PowerShell is shown, consider showing Bash or shell equivalents for Linux/macOS users.
- When referencing 'Windows Azure Service Management API', clarify its relevance to non-Windows environments.
- For sections mentioning 'Azure Serial Console for Windows', provide links or notes about Linux/macOS equivalents if available.
Azure Resource Manager
Use Bicep to deploy resources to resource groups
...ure-resource-manager/bicep/deploy-to-resource-group.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying Bicep files, but the PowerShell example is given equal prominence and detail as the CLI example. Azure PowerShell is a Windows-centric tool, and its inclusion alongside CLI (which is cross-platform) is common, but the documentation does not provide any Linux/macOS-specific guidance or mention Bash scripting, nor does it clarify that Azure CLI is the recommended cross-platform option. The order of examples (CLI first, then PowerShell) is neutral, but the presence of PowerShell examples may suggest a slight Windows bias.
Recommendations
- Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Add a note clarifying that Azure PowerShell is primarily for Windows, and that CLI works on all platforms.
- Consider including Bash script examples for Linux users, or referencing Cloud Shell as a platform-neutral option.
- Ensure that all examples and instructions are clearly applicable to Linux/macOS environments, and avoid implying that PowerShell is required.
Azure Resource Manager
Quickstart: Integrate Bicep with Azure Pipelines
...ource-manager/bicep/add-template-to-azure-pipelines.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for resource cleanup, but the PowerShell example is shown immediately after the CLI example and is given equal prominence. The YAML pipeline examples use 'ubuntu-latest' as the build agent, and Bash scripting in the Azure CLI task, which is Linux-friendly. There is no evidence of exclusive Windows tools or missing Linux examples, but the PowerShell example for cleanup may suggest a slight Windows bias by presenting it alongside the CLI example, rather than as a secondary or alternative option.
Recommendations
- Clearly indicate that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Present Azure CLI examples first and make PowerShell examples optional or in a separate section labeled for Windows users.
- Add a note clarifying platform compatibility for each example.
- Consider including macOS-specific notes if there are any platform caveats.
Azure Resource Manager
Bicep functions - deployment
...e-resource-manager/bicep/bicep-functions-deployment.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references both Windows PowerShell (Get-AzEnvironment) and Azure CLI (az cloud list) for listing registered environments, but it mentions the PowerShell cmdlet before the CLI command. There are no explicit Linux/macOS examples, and the only tool-specific references are to Windows-centric PowerShell and cross-platform Azure CLI. No code samples or instructions are platform-specific, and the main content is platform-neutral.
Recommendations
- List Azure CLI (az cloud list) before PowerShell (Get-AzEnvironment) to reflect cross-platform parity.
- Explicitly mention that Azure CLI is available on Linux/macOS and provide links to installation guides for non-Windows platforms.
- Add a note clarifying that PowerShell Core is available cross-platform, or provide Bash examples where relevant.
- Ensure future documentation includes Linux/macOS-specific guidance when referencing command-line tools.
Azure Resource Manager
Bicep functions - resources
...ure-resource-manager/bicep/bicep-functions-resource.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for discovering resource provider operations, but the PowerShell example is listed first and is more detailed. There are no Linux-specific tools or patterns mentioned, but Azure CLI is cross-platform. No examples or instructions are Windows-only, and all Bicep code is platform-agnostic. No evidence of missing Linux examples or exclusive use of Windows tools, but the ordering and emphasis slightly favor Windows/PowerShell.
Recommendations
- List Azure CLI examples before PowerShell examples to avoid implicit Windows-first bias.
- Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Where PowerShell is mentioned, clarify that it is available on Linux/macOS, or provide Bash alternatives if relevant.
- Consider adding a brief note on how to use Bicep and related tools on Linux/macOS, if relevant to the audience.