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 276-300 of 492 flagged pages
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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and cleaning up Bicep resources. However, PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI, and Visual Studio Code is the only editor mentioned for Bicep development. There is no explicit mention of Linux-specific tools, shell environments, or editor alternatives. The examples and instructions do not reference Linux shell patterns (e.g., bash, zsh), nor do they address platform-specific nuances for Linux users.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide bash/zsh syntax for variable assignment (e.g., resourceGroupName="value") instead of PowerShell-style ($resourceGroupName).
- Include instructions or examples for deploying Bicep files using bash or other Linux-native shells, clarifying any differences in command syntax or environment setup.
- List alternative editors for Bicep development, such as Vim, Emacs, or JetBrains IDEs, and note their cross-platform availability.
- Add a note or section addressing Linux/macOS users, including any prerequisites or installation steps that differ from Windows.
- Ensure that CLI examples precede PowerShell examples, or clarify that CLI is cross-platform while PowerShell is primarily Windows-focused.
Create Pull Request
Azure Resource Manager
Use Bicep to create and publish an Azure Managed Application definition
...nager/managed-applications/publish-bicep-definition.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all major steps, but consistently lists PowerShell (a Windows-centric tool) first in each tabbed example section. The narrative also refers to opening a PowerShell terminal in Visual Studio Code before mentioning Bash, and explains PowerShell-specific features (like splatting) in detail, while not providing equivalent context for Bash/Linux users. There are no explicit Linux-only tools or patterns mentioned, and the CLI examples are present and correct, but the ordering and extra detail for PowerShell suggest a subtle Windows bias.
Recommendations
- Alternate the order of PowerShell and CLI examples, or default to CLI first, as CLI is cross-platform.
- Provide equivalent contextual explanations for Bash/Linux users (e.g., line continuation, variable usage), not just PowerShell splatting.
- Explicitly state that all commands work on Windows, macOS, and Linux, and clarify any platform-specific differences.
- Include guidance for using native Linux terminals (e.g., GNOME Terminal, xterm) in addition to Visual Studio Code.
- Where possible, add notes about using the Azure CLI in Windows Command Prompt, PowerShell, and Linux shells to reinforce parity.
Azure Resource Manager
Manage Azure resources by using Azure CLI
...re-resource-manager/management/manage-resources-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page primarily uses Azure CLI examples, which are cross-platform. However, there is evidence of Windows bias in the 'Deploy a template' section, where the link for creating ARM templates with Visual Studio Code explicitly references PowerShell tabs and does not mention Linux or Bash alternatives. There are no explicit Linux-specific instructions or examples, and the documentation does not clarify that all CLI examples work equally well on Linux/macOS. The page also lacks references to Linux tools or shell patterns, and does not provide parity for Linux users in the linked resources.
Recommendations
- Ensure that linked tutorials (such as the Visual Studio Code ARM template quickstart) include Bash/Linux tabs and examples, not just PowerShell.
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and mention any platform-specific considerations if relevant.
- Where scripts are shown, clarify that they are POSIX shell compatible and will work in Bash on Linux/macOS.
- Add references to Linux-native tools or editors (such as VS Code on Linux, nano, vim) where appropriate.
- Review all linked resources for similar bias and update them to provide Linux parity.
Azure Resource Manager
Handling special cases when moving virtual machines to resource group or subscription
.../move-limitations/virtual-machines-move-limitations.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for all command-line operations, but PowerShell is mentioned explicitly and frequently, sometimes with more detail (e.g., accepting Marketplace terms). The use of PowerShell is prominent, and the documentation references it alongside Azure CLI and ARM templates, but does not mention Linux-specific tools or shell patterns (such as Bash scripting or Linux-native command usage). There is a slight ordering bias, with PowerShell often listed before or alongside CLI, and no explicit Linux-first guidance or examples.
Recommendations
- Add explicit Bash shell scripting examples for Linux users, especially for multi-step operations.
- Clarify that Azure CLI commands work cross-platform and highlight Linux usage where appropriate.
- Ensure that PowerShell and CLI examples are presented in a neutral order or alternate which comes first.
- Add notes or links for Linux users about prerequisites (e.g., installing Azure CLI on Linux, using Bash variables).
- Consider including examples using ARM templates or REST API calls, which are platform-neutral.
Azure Resource Manager
Understand the structure and syntax of ARM templates
...in/articles/azure-resource-manager/templates/syntax.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. In sections discussing JSON schema selection and deployment tooling, Windows-centric editors (Visual Studio, Visual Studio Code) are mentioned first or exclusively, with no mention of Linux alternatives. Deployment instructions reference Azure PowerShell and Azure CLI, but PowerShell is listed first and there are no explicit Linux shell examples. There are no references to Linux-native editors (e.g., Vim, Emacs, nano) or Linux-specific deployment patterns. No Windows-only tools are used, but the ordering and omission of Linux examples suggest a subtle preference for Windows environments.
Recommendations
- Mention Linux-native editors (e.g., Vim, Emacs, nano) alongside Visual Studio and VS Code when discussing editing ARM templates.
- Provide explicit Linux shell examples (e.g., bash commands) for deploying templates, especially when referencing Azure CLI.
- Clarify that Azure CLI is cross-platform and provide usage examples for both Windows (cmd/PowerShell) and Linux (bash/zsh).
- When listing deployment tools, avoid always listing PowerShell first; alternate or group by platform.
- Add notes or links for Linux users regarding installation and usage of Azure CLI and editors.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deploy-cloud-shell.md
...les/azure-resource-manager/bicep/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, but PowerShell is mentioned before Bash in several places (e.g., 'Select either PowerShell or Bash', image alt-text), and the 'Next steps' section lists PowerShell resources before CLI ones. This ordering subtly prioritizes Windows/PowerShell workflows. However, both Bash (Linux) and PowerShell examples are provided, so there is not a complete absence of Linux parity.
Recommendations
- List Bash (Azure CLI) before PowerShell when presenting options, to avoid implicit prioritization of Windows tools.
- Use 'Bash or PowerShell' consistently instead of 'PowerShell or Bash' in instructions and image alt-text.
- Alternate the order of CLI and PowerShell examples in 'Next steps' or group them together to show equal support.
- Explicitly state that both Bash (Linux) and PowerShell (Windows) are supported equally in Cloud Shell.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/operator-null-forgiving.md
...zure-resource-manager/bicep/operator-null-forgiving.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page references Azure CLI and Azure PowerShell as the tools to run the examples, listing Azure PowerShell (a Windows-centric tool) alongside Azure CLI, and does not mention Linux-native shells or deployment methods. There are no explicit Linux examples or references to Bash, and PowerShell is mentioned before any Linux equivalent.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Provide example commands for deploying Bicep files using Bash or other Linux-native shells.
- List Azure CLI before Azure PowerShell when suggesting deployment tools, as CLI is more platform-agnostic.
- Add a note or section clarifying that all examples are platform-independent unless otherwise stated.
- Consider including a Linux-specific 'Next steps' bullet, such as using Bash with Azure CLI.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/operators-access.md
...icles/azure-resource-manager/bicep/operators-access.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a subtle Windows bias by mentioning Azure PowerShell before Azure CLI in the 'Next steps' section and by not providing any explicit Linux/macOS-specific guidance or examples. All command-line references are platform-neutral but default to Windows-centric tools and order. There are no explicit Linux examples or mentions of using Bicep on Linux/macOS, nor are there any references to shell environments other than PowerShell.
Recommendations
- When referencing deployment tools, mention Azure CLI before Azure PowerShell, as Azure CLI is cross-platform and more commonly used on Linux/macOS.
- Explicitly state that all examples and tools are cross-platform unless otherwise noted.
- Add a note or section clarifying that Bicep and the Azure CLI are fully supported on Linux/macOS, and provide links to relevant installation guides for those platforms.
- Where possible, provide example commands for both Azure CLI (bash/zsh) and Azure PowerShell, or clarify that the steps are identical across platforms.
- Avoid implying that PowerShell is the default or primary method for deployment unless there is a technical reason.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/linter-rule-protect-commandtoexecute-secrets.md
.../bicep/linter-rule-protect-commandtoexecute-secrets.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation references the Windows Custom Script Extension before the Linux equivalent and links to the Windows documentation first. There are no explicit Linux-specific examples or commands, and the pattern of mentioning Windows tools before Linux ones suggests a Windows-first bias.
Recommendations
- Mention both Windows and Linux Custom Script Extension documentation together, or list Linux first in some instances to balance ordering.
- Provide explicit examples or notes for both Windows and Linux scenarios, especially if there are differences in usage.
- Ensure parity in documentation links and guidance for both platforms.
- Consider adding a Linux-specific example or clarifying if the example provided is cross-platform.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/linter-rule-use-stable-vm-image.md
...ource-manager/bicep/linter-rule-use-stable-vm-image.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation only provides examples using Windows Server VM images (including both the failing and fixed cases), without any mention or examples of Linux-based images. This presents a Windows-first bias and omits Linux parity in usage examples.
Recommendations
- Add equivalent examples using popular Linux VM images (e.g., Ubuntu, CentOS) to demonstrate the rule's applicability across platforms.
- Explicitly mention that the rule applies to both Windows and Linux VM images.
- Where possible, alternate the order of examples or provide both Windows and Linux examples side-by-side to avoid platform bias.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/operators-numeric.md
...cles/azure-resource-manager/bicep/operators-numeric.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by mentioning Azure PowerShell (a Windows-centric tool) before Azure CLI and by referencing Visual Studio Code (which, while cross-platform, is often associated with Windows) as the primary editor for Bicep files. No explicit Linux examples or Linux-specific tools are provided, and the deployment instructions do not clarify parity or differences for Linux users.
Recommendations
- List Azure CLI before Azure PowerShell when suggesting deployment tools, as Azure CLI is more platform-neutral and widely used on Linux.
- Explicitly mention that all examples work on Linux, macOS, and Windows, and provide a sample Azure CLI command for deploying a Bicep file.
- Include a note or section on using alternative editors (such as Vim or VS Code on Linux) for authoring Bicep files.
- If referencing PowerShell, also mention Bash or shell equivalents where relevant.
- Ensure that all instructions and examples are validated on Linux platforms and clarify any OS-specific requirements.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/custom-providers/tutorial-resource-onboarding.md
...nager/custom-providers/tutorial-resource-onboarding.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes deployment using the Azure portal UI, which is most accessible and familiar to Windows users. There are no command-line examples (such as Azure CLI, PowerShell, or Bash scripts), and no mention of Linux or cross-platform tools. All screenshots and instructions are portal-centric, which may disadvantage Linux users who often prefer or require CLI-based workflows.
Recommendations
- Add Azure CLI examples for deploying the ARM template, including commands for parameter input and deployment verification.
- Include Bash script snippets for common tasks, such as copying the template and deploying it from the terminal.
- If PowerShell examples are added, ensure Azure CLI or Bash equivalents are provided and shown first or side-by-side.
- Mention that the Azure portal is cross-platform, but highlight CLI-based workflows for users on Linux or macOS.
- Provide links to official Azure CLI documentation for template deployment.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/microsoft-compute-sizeselector.md
...managed-applications/microsoft-compute-sizeselector.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a schema example that exclusively uses Windows values for 'osPlatform' and 'imageReference', without showing equivalent Linux values or examples. While the remarks mention that 'osPlatform' can be either Windows or Linux, all concrete examples and defaults are Windows-centric.
Recommendations
- Add a parallel schema example using 'osPlatform': 'Linux' and a representative Linux 'imageReference' (e.g., Ubuntu or CentOS).
- Explicitly show both Windows and Linux options in sample code and outputs.
- Where possible, alternate the order of Windows and Linux mentions, or present them together, to avoid implicit prioritization.
- Clarify in remarks or notes that all features and options are equally supported for Linux, and provide links to relevant Linux image references.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/microsoft-compute-usernametextbox.md
...aged-applications/microsoft-compute-usernametextbox.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page describes a UI element supporting both Windows and Linux user names, but the primary schema example and regex validation pattern are tailored for Windows (alphanumeric only, which is typical for Windows user names). The 'osPlatform' property in the schema is set to 'Windows', and there is no equivalent Linux example or Linux-specific validation pattern provided. Linux is only mentioned in passing, and no Linux-centric usage or validation is demonstrated.
Recommendations
- Provide a schema example with 'osPlatform' set to 'Linux', including a Linux-appropriate regex pattern and validation message.
- Add remarks or a table describing the differences in built-in validation between Windows and Linux user names.
- Ensure that both Windows and Linux usage patterns are equally represented in examples and documentation sections.
- Consider including a sample output or UI screenshot for a Linux user name scenario.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/create-private-link-access-portal.md
...anager/management/create-private-link-access-portal.md
Medium Priority
View Details →
Detected Bias Types
Portal Only
Missing Linux Example
Summary
The documentation exclusively describes how to create and manage Azure Private Links using the Azure portal, without providing any command-line examples (such as Azure CLI, PowerShell, or Bash scripts). This approach omits Linux-centric workflows and tools, which are commonly used by Linux users and administrators.
Recommendations
- Add Azure CLI examples for each step, as the Azure CLI is cross-platform and widely used on Linux.
- If relevant, include Bash script snippets to automate the process for Linux users.
- Explicitly mention that the steps can also be performed using command-line tools, and provide links to relevant documentation for Azure CLI and PowerShell.
- Ensure that any references to command-line tools do not prioritize PowerShell or Windows tools over cross-platform alternatives.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/delete-resource-group.md
...e-resource-manager/management/delete-resource-group.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for deleting resource groups and resources using PowerShell, Azure CLI, Portal, and Python. PowerShell examples are consistently presented first, which may indicate a Windows-first bias. While Azure CLI is cross-platform and included, there are no explicit Linux shell (e.g., Bash) or scripting examples, and no mention of Linux-specific tools or workflows. The documentation does not provide Linux-specific context or parity in the ordering or depth of examples.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI examples first to reflect cross-platform parity.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample Bash scripts for common deletion tasks.
- Add a section or note highlighting Linux/macOS usage patterns, such as using Bash scripting or integrating with Linux automation tools.
- Where PowerShell-specific syntax is used, provide equivalent Bash or shell scripting examples to ensure Linux users are equally supported.
- Review the documentation to ensure that no implicit assumption is made that users are on Windows, and clarify any platform-specific requirements.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/manage-resources-cli.md
...re-resource-manager/management/manage-resources-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is generally cross-platform, using Azure CLI and shell scripting compatible with both Linux and Windows. However, there is a notable Windows-first bias in the 'Deploy a template' section, where the primary link for creating ARM templates references a Visual Studio Code quickstart with a PowerShell tab, and PowerShell is mentioned in the URL tab parameter. There are no explicit Linux-only examples or references to Linux-specific tools/editors (e.g., Vim, nano), and the documentation does not mention Bash or Linux shell environments, which may implicitly favor Windows users.
Recommendations
- Provide explicit mention that the CLI examples work in both Bash (Linux/macOS) and PowerShell (Windows), or show both shell environments where relevant.
- In the 'Deploy a template' section, include links to quickstarts or guides using Linux-native editors (e.g., Vim, nano) or the Azure CLI in Bash.
- Avoid referencing PowerShell tabs or examples as the default in cross-platform documentation; instead, use Bash or a neutral shell.
- Add a note clarifying that all scripts are compatible with Linux, macOS, and Windows (with WSL or Git Bash), and provide troubleshooting tips for each OS if needed.
- When linking to external resources, ensure parity by including both Windows and Linux-focused guides.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deploy-to-azure-button.md
...e-resource-manager/templates/deploy-to-azure-button.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a PowerShell example for URL encoding but does not offer equivalent Linux/macOS (e.g., bash, curl, or Python) examples. This creates a bias towards Windows users and may hinder Linux users who are unfamiliar with PowerShell.
Recommendations
- Add a bash example using 'python3 -c', 'jq', or 'perl' for URL encoding.
- Mention common Linux tools (e.g., 'curl', 'urlencode', or 'python3') alongside PowerShell.
- Wherever a command-line example is given, provide both Windows (PowerShell) and Linux/macOS (bash) equivalents.
- Clarify that the PowerShell example is for Windows and provide a Linux/macOS alternative.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/move-limitations/app-service-move-limitations.md
...ement/move-limitations/app-service-move-limitations.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a bias towards Windows by exclusively referencing the Azure portal (a GUI tool most familiar to Windows users) and not providing any command-line examples (such as Azure CLI, PowerShell, or Bash scripts). There are no Linux-specific instructions or examples, and no mention of cross-platform tools or terminal-based workflows. The only tool mentioned for diagnostics and migration is the Azure portal, which is browser-based and often associated with Windows-centric workflows.
Recommendations
- Add Azure CLI examples for moving App Service resources, as the CLI is cross-platform and widely used on Linux.
- Include Bash script snippets for common operations, such as finding the original resource group or moving resources.
- Mention PowerShell only alongside Azure CLI, and provide parity in examples for both tools.
- Reference command-line alternatives for all portal-based steps, ensuring Linux users can follow along without relying on the GUI.
- Explicitly state that all operations can be performed from Linux, macOS, or Windows environments using the Azure CLI.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-event-grid-custom-topics.md
...ment/relocation/relocation-event-grid-custom-topics.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (web UI) for all instructions and examples, with no mention of command-line alternatives such as Azure CLI, PowerShell, or REST API. While this avoids explicit Windows tool bias, it implicitly favors Windows users by not providing Linux-friendly command-line instructions. There are no examples for Linux users or guidance on using cross-platform tools, and the workflow assumes graphical interaction typical of Windows environments.
Recommendations
- Add step-by-step instructions for relocating Event Grid custom topics using Azure CLI, which is cross-platform and widely used on Linux.
- Include PowerShell examples for parity, but ensure Azure CLI examples are presented first or alongside PowerShell to avoid Windows-first bias.
- Reference REST API methods for advanced users who may prefer scripting or automation, regardless of OS.
- Explicitly state that the Azure portal is accessible from any OS, but provide alternatives for users who prefer or require command-line workflows.
- Add notes or links to documentation on installing and using Azure CLI on Linux and macOS.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-event-grid-domains.md
...management/relocation/relocation-event-grid-domains.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (GUI) for all instructions, which is most commonly accessed from Windows environments and does not mention command-line alternatives such as Azure CLI, PowerShell, or Bash. There are no examples or guidance for Linux users or for automation via CLI tools, which are preferred in many Linux and cross-platform scenarios.
Recommendations
- Add equivalent instructions using Azure CLI commands for all major steps (exporting templates, deploying resources, deleting domains/resource groups).
- Include examples for both Windows (PowerShell) and Linux/macOS (Bash) environments where scripting or command-line actions are possible.
- Mention cross-platform tools (Azure CLI, REST API) before or alongside portal-based instructions to ensure parity.
- Add notes or links to documentation for automating these tasks in CI/CD pipelines, which are often run on Linux agents.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-event-hub-cluster.md
.../management/relocation/relocation-event-hub-cluster.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses the Azure portal for all steps, which is a web-based tool but often associated with Windows workflows. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), and no mention of Linux-native tools or patterns. The instructions and screenshots are tailored to the portal experience, which may be more familiar to Windows users. There is no guidance for users who prefer automation or scripting, which is common in Linux environments.
Recommendations
- Add equivalent instructions using Azure CLI, which is cross-platform and widely used on Linux.
- Include examples for exporting and deploying Resource Manager templates using command-line tools (e.g., az group export, az deployment group create).
- Mention PowerShell and Bash alternatives if scripting is required, and provide sample scripts for both.
- Clarify that the Azure portal is web-based and accessible from any OS, but offer parity for users who prefer command-line or automated workflows.
- Ensure screenshots and terminology do not assume a Windows environment (e.g., avoid references to Windows file paths or Windows-specific UI elements).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-virtual-machine-scale-sets.md
...nt/relocation/relocation-virtual-machine-scale-sets.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing the Azure portal (a GUI tool most commonly used on Windows), and mentioning PowerShell as an example IAC tool, but does not provide any Linux-specific examples, CLI commands, or guidance for Linux users. There are no references to Bash, Linux shell scripting, or Linux-native tools. The instructions for exporting and editing templates are portal-centric, which is less accessible for Linux users who may prefer CLI or automation.
Recommendations
- Add explicit Azure CLI examples for all steps, especially for exporting, editing, and deploying templates.
- Include instructions for performing key actions (such as setting instance count to 0, exporting templates, and deploying resources) using Bash or Linux shell scripting.
- Mention Linux-native tools and workflows alongside PowerShell, and provide parity in examples.
- Clarify that all steps can be performed on Linux, Mac, or Windows, and provide cross-platform guidance where relevant.
- Ensure screenshots and step-by-step instructions are not exclusively portal-based; provide CLI alternatives.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/resource-manager-personal-data.md
...e-manager/management/resource-manager-personal-data.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation consistently lists Windows PowerShell cmdlets before Azure CLI commands when describing how to manage deployments, resource groups, and tags. This ordering may suggest a preference for Windows tooling. Additionally, there are no Linux-specific shell examples or references to Linux-native patterns, and PowerShell is highlighted as a primary interface, which is more commonly used on Windows.
Recommendations
- Alternate the order of examples so that Azure CLI commands (cross-platform) are listed before or alongside PowerShell cmdlets.
- Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, while PowerShell is primarily a Windows tool (though available cross-platform).
- Provide example usage for both Bash (Linux/macOS) and PowerShell (Windows), especially for command-line operations.
- Add notes or sections highlighting Linux usage patterns, such as scripting with Bash or using native Linux tools in conjunction with Azure CLI.
- Review and update documentation to ensure equal visibility and accessibility for Linux users.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/tag-resources.md
...les/azure-resource-manager/management/tag-resources.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by mentioning Azure PowerShell and REST API as primary programmatic methods for tag operations, with PowerShell referenced before CLI or Linux-native tools. In the 'Next steps' section, Azure PowerShell is listed before Python and ARM templates, and the CLI is only referenced in limitations, not as a primary method. There are no explicit Linux shell or Bash examples, and PowerShell is highlighted as a main automation tool, which may disadvantage Linux users.
Recommendations
- Ensure Azure CLI examples and references are presented alongside or before PowerShell, as CLI is cross-platform and more familiar to Linux users.
- Add explicit Bash or shell scripting examples for common tagging operations.
- When listing programmatic or automation options, alternate the order (e.g., CLI, PowerShell, REST) or group them as 'cross-platform tools' and 'Windows-specific tools'.
- Clarify that PowerShell is available cross-platform, but highlight CLI as the default for Linux environments.
- Where possible, provide links to Linux-specific guides or documentation for tagging resources.