Governance

305
Total Pages
190
Linux-Friendly Pages
115
Pages with Bias
37.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

613 issues found
Showing 476-500 of 613 flagged pages
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/virtual-instance-sap-solutions-vm-health.md ...gory/query/virtual-instance-sap-solutions-vm-health.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments. There are no explicit Linux shell (bash) or scripting examples, and PowerShell examples are given equal prominence to CLI, which can reinforce a Windows-centric workflow. There is no mention of Linux-specific tools or usage patterns, nor any guidance for Linux users beyond the CLI.
Recommendations
  • Add explicit bash shell examples for running Azure CLI commands, including output parsing with jq or grep for Linux users.
  • Clarify that Azure CLI is fully supported on Linux and macOS, and provide installation or usage notes for those platforms.
  • If PowerShell is mentioned, note that PowerShell Core is available cross-platform, and provide examples for both Windows PowerShell and PowerShell Core on Linux/macOS.
  • Consider including a section or tab for Linux-specific usage patterns, such as scripting with bash or integrating with Linux monitoring tools.
  • Review documentation to ensure that Windows tools or patterns are not presented as the default or primary method unless truly necessary.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/canada-federal-pbmm.md ...s/governance/blueprints/samples/canada-federal-pbmm.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides examples and parameters for both Linux and Windows VMs in the artifact parameters table, but Windows-specific concepts (such as the 'Administrators group' and 'List of users that should be included in Windows VM Administrators group') are described in detail, while equivalent Linux user/group management is not mentioned. There are no Linux-specific examples or guidance for managing Linux VM users/groups, and the documentation refers to Windows VM administration patterns without Linux parity.
Recommendations
  • Add equivalent Linux examples for user/group management, such as specifying users for the 'sudo' or 'admin' group on Linux VMs.
  • Include guidance or references for managing Linux VM users/groups in the context of blueprint assignments, similar to the Windows Administrators group example.
  • Ensure that Linux-specific parameters and operational patterns are described with the same level of detail as Windows examples.
  • Where both Linux and Windows artifacts are present, present their documentation in parallel or clarify differences, rather than focusing on Windows-specific concepts.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/assign-configuration/terraform.md ...configuration/how-to/assign-configuration/terraform.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively provides examples for Windows virtual machines, referencing only azurerm_windows_virtual_machine resources and built-in Windows configurations. There are no examples or guidance for Linux virtual machines, nor mention of Linux-specific configurations or resources.
Recommendations
  • Add equivalent examples for Linux virtual machines using azurerm_linux_virtual_machine.
  • Include built-in configuration assignment examples relevant to Linux (e.g., AzureLinuxBaseline).
  • Clarify in the introduction that both Windows and Linux are supported, if applicable.
  • Provide links to Linux-specific Terraform resources and configuration documentation.
  • Ensure parameter and configuration details are shown for Linux scenarios where they differ from Windows.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/management-groups/create-management-group-dotnet.md ...ce/management-groups/create-management-group-dotnet.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides instructions and examples that implicitly assume a Windows environment, such as referencing the executable as 'mgCreate.exe' and using backtick (`) line continuations typical of PowerShell. There are no explicit instructions or examples for running the application on Linux or macOS, nor is there guidance for Linux-specific usage patterns (e.g., using './mgCreate' or bash line continuations).
Recommendations
  • Include Linux/macOS instructions for running the .NET Core application, such as using './mgCreate' instead of 'mgCreate.exe'.
  • Provide bash/zsh shell examples with appropriate line continuations (using '\' instead of '`').
  • Clarify cross-platform compatibility of .NET Core applications and note any OS-specific differences in executable naming and invocation.
  • Mention how to install .NET Core on Linux/macOS, or link to relevant installation guides.
  • Add a note about file permissions (e.g., 'chmod +x mgCreate') for Linux/macOS users.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/concepts/definition-structure-alias.md ...vernance/policy/concepts/definition-structure-alias.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists methods for discovering Azure Policy aliases in the following order: Visual Studio Code extension (cross-platform), Azure PowerShell (Windows-centric), Azure CLI (cross-platform), and REST API. The PowerShell examples are more detailed, including advanced usage notes and commands, while the Azure CLI section is shorter and less comprehensive. PowerShell is presented before Azure CLI, which may suggest a Windows-first bias. There are no Linux-specific tools or shell examples, and PowerShell is traditionally associated with Windows environments.
Recommendations
  • Provide equally detailed examples for Azure CLI, including advanced queries and usage notes similar to those given for PowerShell.
  • Consider listing Azure CLI before PowerShell, or present both together to avoid implying preference for Windows tools.
  • Add explicit notes about cross-platform compatibility for both Azure CLI and PowerShell (since PowerShell Core is available on Linux/macOS).
  • Include Linux shell (bash) usage examples where relevant, such as using jq for parsing CLI output.
  • Clarify that all tools mentioned are available on multiple platforms, and provide links or instructions for installation on Linux/macOS.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/concepts/definition-structure-basics.md ...ernance/policy/concepts/definition-structure-basics.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a Windows bias primarily in the section discussing how to specify the 'mode' parameter when creating policy definitions. PowerShell and Azure CLI are mentioned as the tools for policy creation, with Azure PowerShell behavior described first and in more detail. There are no explicit Linux examples, nor are Linux-native tools (such as Bash scripts) referenced. The documentation assumes familiarity with Windows-centric tools and patterns, potentially leaving Linux users without clear guidance.
Recommendations
  • Provide explicit examples using Bash and Azure CLI on Linux, not just PowerShell.
  • When discussing tool-specific behavior (such as default values), present Azure CLI and PowerShell equally, and clarify platform differences.
  • Include a section or note on cross-platform usage, highlighting how Linux users can perform the same actions.
  • Reference Linux-native scripting patterns or workflows in addition to Windows/PowerShell.
  • Ensure that sample commands and instructions are not Windows-centric and are tested on Linux environments.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/how-to/export-resources.md .../articles/governance/policy/how-to/export-resources.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for exporting Azure Policy resources, but the PowerShell section is given equal prominence despite PowerShell being primarily a Windows-centric tool. There is no mention of Linux-specific shell patterns (e.g., Bash, jq), nor are there examples showing how to process or manipulate the exported JSON on Linux. The CLI example is generic, but the PowerShell example includes additional processing (ConvertTo-Json), which may suggest richer functionality for Windows users. There are no explicit Linux-only tools or workflows discussed.
Recommendations
  • Add examples showing how to process the exported JSON using Linux-native tools such as jq or grep.
  • Include notes or examples demonstrating how the Azure CLI commands can be used in Bash scripts on Linux.
  • If possible, provide parity in post-processing examples (e.g., show how to convert output to JSON or CSV using Linux tools).
  • Clarify that Azure CLI is cross-platform and highlight its use on Linux and macOS.
  • Consider adding a section or callout for Linux users, mentioning installation and usage patterns specific to Linux environments.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/how-to/remediate-resources.md ...ticles/governance/policy/how-to/remediate-resources.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by consistently presenting PowerShell examples before Azure CLI equivalents, and by providing more detailed, step-by-step instructions for PowerShell users. The portal instructions are also Windows-centric, as the Azure portal is most commonly accessed from Windows environments. There are no explicit Linux-specific examples, nor is there mention of Linux shell scripting or tooling. The CLI examples are present, but often after PowerShell, and with less explanatory detail.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to avoid implicit prioritization of Windows tooling.
  • Provide equivalent step-by-step instructions for Azure CLI usage, matching the detail given to PowerShell.
  • Include notes or examples for Linux shell environments (e.g., bash scripting, environment variables) where relevant.
  • Explicitly state that both Azure CLI and PowerShell are cross-platform, and clarify usage on Linux/macOS.
  • Add troubleshooting or usage tips for Linux users, such as differences in authentication or file paths.
  • Consider adding a section or tab for Linux-specific workflows or common scenarios.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/tutorials/disallowed-resources.md ...es/governance/policy/tutorials/disallowed-resources.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively using Azure portal (a GUI tool most commonly used on Windows) for all examples and instructions. There are no command-line examples (such as Azure CLI or PowerShell), nor are there any Linux-specific instructions or parity. The only mention of cross-platform tools is in a note, which states that resources in exempted scopes can be created with Azure CLI, Azure PowerShell, or ARM templates, but no examples or guidance are provided for these tools. All step-by-step instructions assume use of the Azure portal, which is most familiar to Windows users.
Recommendations
  • Add step-by-step instructions for assigning and managing policies using Azure CLI and Azure PowerShell, including full command examples.
  • Explicitly mention that Azure CLI is cross-platform and provide Linux/macOS usage notes where relevant.
  • Include ARM template examples for policy assignment and exemption creation.
  • Ensure that all major actions (assignment, exemption, deletion) have both portal and CLI/PowerShell/ARM template instructions, presented in parallel.
  • Consider starting with CLI/PowerShell examples or presenting them before portal instructions to avoid 'windows_first' bias.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/app-service-resources-tls-version.md ...by-category/query/app-service-resources-tls-version.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples, but lists Azure PowerShell (a Windows-centric tool) as a primary tab alongside Azure CLI. There is no explicit Linux shell example (e.g., Bash), nor is there mention of Linux-specific usage patterns. The PowerShell example may imply a Windows-first approach, and the lack of Linux/Bash shell context could hinder parity for Linux users.
Recommendations
  • Add a Bash shell example using Azure CLI to demonstrate usage on Linux/macOS.
  • Clarify that Azure CLI commands work cross-platform and can be run in Bash, Zsh, or other Linux shells.
  • Consider listing Azure CLI (cross-platform) before Azure PowerShell (Windows-centric) to avoid Windows-first impression.
  • Explicitly mention platform compatibility for each tool, helping users choose the best option for their OS.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-cosmos-db.md ...-graph/includes/samples-by-category/azure-cosmos-db.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. The PowerShell example is given equal prominence to the CLI example, but PowerShell is a Windows-centric tool, and there is no mention of Linux-specific shell usage (e.g., Bash) or cross-platform scripting considerations. The ordering of examples places Azure CLI first, which is cross-platform, but the inclusion of PowerShell without clarifying its platform limitations may suggest a slight Windows bias.
Recommendations
  • Explicitly note that Azure CLI is cross-platform and can be used in Bash, Zsh, or other Linux shells.
  • Provide example usage in a Linux shell (e.g., Bash) to demonstrate parity and clarify any differences in quoting or command syntax.
  • Clarify that PowerShell is available on Linux and macOS, or provide links to installation instructions for non-Windows platforms.
  • Consider adding a section on scripting these queries in Bash or other Linux-native tools to improve inclusivity.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-monitor.md ...ce-graph/includes/samples-by-category/azure-monitor.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, the inclusion of Azure PowerShell examples introduces a Windows bias, as PowerShell is historically a Windows-centric tool (despite recent cross-platform support). Additionally, the documentation lists Azure CLI first, followed by Azure PowerShell, which is a positive sign for parity, but the presence of PowerShell-specific examples may still signal a Windows preference. There are no Linux-specific shell examples (e.g., Bash scripts, curl, jq), nor is there mention of Linux-native tooling or usage patterns.
Recommendations
  • Add Linux/Bash shell examples using Azure CLI, demonstrating output parsing with tools like jq or grep.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide explicit instructions for installing and using CLI on Linux.
  • If PowerShell is included, mention that PowerShell Core is available cross-platform and provide installation guidance for Linux users.
  • Consider including sample scripts for Linux environments, such as Bash or Zsh, to show parity.
  • Avoid implying that PowerShell is the default or preferred scripting environment unless justified by technical reasons.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-policy.md ...rce-graph/includes/samples-by-category/azure-policy.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for each query, but PowerShell is given equal prominence as CLI, despite being a Windows-centric tool. The tab order consistently lists Azure CLI first, which is cross-platform, but the inclusion of PowerShell examples for every scenario introduces a subtle Windows bias. There are no Linux-specific shell examples (e.g., Bash scripting), nor is there mention of Linux-native tools or usage patterns. No explicit Windows-only tools are referenced, but the parity between CLI and PowerShell may suggest to users that PowerShell is equally relevant on all platforms, which is not the case.
Recommendations
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit Bash or shell script examples for Linux users where appropriate.
  • Note that PowerShell examples are primarily for Windows users, or mention PowerShell Core for Linux/macOS.
  • Consider adding a 'Linux/macOS' tab with usage notes or examples tailored for those platforms.
  • Review documentation for any assumptions about the user's OS and make platform recommendations explicit.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/authorization-resources-role-assignments-key-properties.md ...uthorization-resources-role-assignments-key-properties.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric and is presented as a primary tab. There is no explicit mention of Linux shell (bash) usage or examples, and PowerShell is listed before the Portal, which may reinforce a Windows-first perspective.
Recommendations
  • Add explicit Linux/Bash shell examples where applicable, especially for Azure CLI usage.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
  • Consider reordering tabs so that cross-platform tools (Azure CLI) appear before Windows-centric tools (PowerShell).
  • If PowerShell is shown, note that PowerShell Core is available on Linux, or provide a bash equivalent.
  • Add a note about platform compatibility for each tool to help users choose the best option for their environment.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/authorization-resources-classic-administrators-key-properties.md ...zation-resources-classic-administrators-key-properties.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and its inclusion as a primary example may indicate a Windows bias. The ordering of examples places Azure PowerShell immediately after Azure CLI, which can reinforce a Windows-centric perspective. No explicit Linux shell (bash) or scripting examples are provided, nor is there mention of Linux-specific usage patterns.
Recommendations
  • Add explicit Linux shell (bash) examples for running Azure CLI commands, demonstrating usage in a Linux terminal.
  • Clarify that Azure CLI is cross-platform and provide guidance for both Windows and Linux users.
  • Consider including examples for other popular shells (e.g., zsh, bash) to improve Linux parity.
  • If PowerShell is mentioned, note that PowerShell Core is available on Linux and macOS, and provide instructions for those platforms.
  • Review the ordering of examples to avoid implying Windows tools are primary or preferred.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/authorization-resources-role-definitions-actions-list.md ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/authorization-resources-role-definitions-actions-list.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and its example is given equal prominence. There are no explicit Linux shell (bash/zsh) examples, nor is there mention of Linux-specific tooling or patterns. The ordering of examples (CLI, PowerShell, Portal) puts PowerShell before Portal, which may reinforce Windows-centric workflows.
Recommendations
  • Add explicit bash/zsh shell examples to demonstrate usage on Linux and macOS platforms.
  • Clarify that Azure CLI is cross-platform and provide sample commands for Linux/macOS terminals (e.g., with curl or jq where relevant).
  • Consider reordering examples to present cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell), or provide a clear note about platform compatibility.
  • Mention installation and usage notes for Linux users, such as package managers or shell integration.
  • If PowerShell is shown, note that PowerShell Core is available on Linux/macOS, and provide guidance for those platforms.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/authorization-resources-role-definitions-key-properties.md ...uthorization-resources-role-definitions-key-properties.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments and is presented as a main example. There is no explicit mention of Linux shell (bash) usage, nor are there examples tailored for Linux users (e.g., bash scripts, shell commands, or Linux-specific tooling). The order of examples also places PowerShell before any Linux-specific alternatives, which may reinforce a Windows-first perspective.
Recommendations
  • Add explicit bash or shell script examples for Linux users, demonstrating how to run the Azure CLI command in a Linux terminal.
  • Clarify that Azure CLI is cross-platform and provide usage notes or screenshots for both Windows and Linux environments.
  • Consider reordering examples to present cross-platform or Linux-friendly options before Windows-specific ones.
  • Mention any differences in behavior or prerequisites for Linux users when using Azure CLI or accessing the Azure Portal.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/virtual-machine-scale-sets-computeresources-uniform-orchestration.md ...hine-scale-sets-computeresources-uniform-orchestration.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but lists PowerShell immediately after CLI and before the Portal, which may suggest a slight Windows-first ordering. The inclusion of PowerShell as a primary example can be interpreted as Windows-centric, given PowerShell's historical association with Windows, even though it is now cross-platform. No explicit Linux shell (e.g., Bash) or Linux-specific instructions are provided, but the Azure CLI example is cross-platform and suitable for Linux users.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Add a Bash shell example or clarify that the Azure CLI example is suitable for Bash/Unix shells.
  • Consider listing Azure CLI first to emphasize cross-platform support, followed by PowerShell.
  • Add a note about PowerShell Core being available on Linux and macOS to reduce perceived Windows bias.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/virtual-instance-sap-solutions-vm-health-changes.md ...ry/virtual-instance-sap-solutions-vm-health-changes.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. The PowerShell example is given equal prominence as the CLI example, but there is no explicit mention of Linux-specific shell usage (e.g., Bash), nor any notes about cross-platform compatibility for the CLI commands. The ordering of tabs places Azure CLI first, which is cross-platform, but the inclusion of Azure PowerShell (a Windows-centric tool, though now available on Linux) without any Linux shell example or explicit cross-platform notes may be interpreted as a subtle Windows bias.
Recommendations
  • Add explicit notes that Azure CLI commands work on both Windows and Linux (Bash, Zsh, etc.), and provide example invocations in Bash or other common Linux shells.
  • Clarify that Azure PowerShell is available cross-platform, but highlight any differences in usage or installation between Windows and Linux.
  • Consider including a Bash example or a Linux shell script for parity, especially for users who may not use PowerShell.
  • If there are any platform-specific caveats (e.g., quoting, escaping), document these for both Windows and Linux users.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/virtual-machine-basic-sku-public-ip.md ...-category/query/virtual-machine-basic-sku-public-ip.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is traditionally Windows-centric, though now available on Linux) and the absence of explicit Linux shell (bash/zsh) or scripting examples may indicate a slight Windows bias. Additionally, PowerShell is listed as a primary tab alongside CLI and Portal, which can be interpreted as giving Windows tools equal or greater prominence than Linux-native alternatives.
Recommendations
  • Add explicit bash/zsh shell script examples for running the Azure CLI command, demonstrating usage in a Linux environment.
  • Clarify that Azure CLI is cross-platform and provide instructions or screenshots for running it on Linux and macOS.
  • Consider including examples using other Linux-native tools or scripting languages (e.g., Python with Azure SDK) where relevant.
  • If PowerShell is included, note its cross-platform availability and provide guidance for Linux users on installation and usage.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/virtual-machine-scale-sets-resources-flexible-orchestration.md ...al-machine-scale-sets-resources-flexible-orchestration.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but PowerShell (a Windows-centric tool) is given equal prominence as CLI, and is listed immediately after CLI. There are no explicit Linux shell (bash/sh) examples, nor is there mention of Linux-specific tooling or usage patterns. The presence of PowerShell may imply a bias toward Windows users, especially since PowerShell is traditionally associated with Windows environments.
Recommendations
  • Add explicit bash/sh examples for Linux users, demonstrating the same query using Azure CLI in a typical Linux shell context.
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide sample usage in a Linux terminal.
  • Consider reordering tabs or providing usage context to avoid implying PowerShell is the default or primary method.
  • Mention that PowerShell Core is available cross-platform, if relevant, to reduce Windows-centric perception.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/tags.md ...ce/resource-graph/includes/samples-by-category/tags.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and its inclusion in every example may suggest a Windows bias. Furthermore, PowerShell examples are always presented alongside CLI, and there are no explicit Linux shell (bash/zsh) or scripting examples, nor are Linux-specific tools or patterns mentioned. The ordering of tabs (CLI first, then PowerShell) is good, but the lack of Linux-specific context or examples means users on Linux may not see their workflows represented beyond the generic CLI usage.
Recommendations
  • Add explicit bash/zsh shell script examples for each query, demonstrating usage in Linux environments.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide notes or links to Linux installation and usage guides.
  • Consider including Linux-specific troubleshooting tips or environment setup notes where relevant.
  • If PowerShell is included, mention that PowerShell Core is available cross-platform, and provide instructions for using it on Linux/macOS.
  • Review the documentation for any implicit assumptions about Windows environments (e.g., file paths, environment variables) and ensure Linux equivalents are mentioned.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/resource-health.md ...-graph/includes/samples-by-category/resource-health.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation consistently presents Azure CLI and Azure PowerShell examples side-by-side, but always lists Azure PowerShell (a Windows-centric tool) as a primary tab and provides full PowerShell command examples. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments, such as shell scripting or integration with Linux-native tools. The CLI examples are generic and do not highlight Linux workflows or considerations.
Recommendations
  • Add explicit Bash shell examples for Azure CLI usage, demonstrating Linux-native command-line patterns (e.g., piping, jq for JSON parsing).
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS users, including installation and environment setup.
  • Consider including Linux-specific troubleshooting or scripting tips alongside PowerShell examples.
  • Reorder tabs or examples so that Azure CLI (the cross-platform tool) is presented before PowerShell, or at least clarify parity.
  • Mention alternative Linux tools or integrations where relevant (e.g., using cron for scheduling queries, or integrating with shell scripts).
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/assign-configuration/azure-resource-manager.md .../how-to/assign-configuration/azure-resource-manager.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by providing a built-in configuration example ('AzureWindowsBaseline') that is specific to Windows, without offering a Linux equivalent. No Linux-specific built-in configuration or example is shown, and the only built-in configuration mentioned is for Windows. The link reference for template deployment also defaults to Azure PowerShell, a tool more commonly used on Windows.
Recommendations
  • Include examples for built-in Linux configurations, such as 'AzureLinuxBaseline', if available.
  • Provide explicit mention and examples of Linux VM configuration assignments alongside Windows examples.
  • Ensure that reference links offer parity for Linux users, such as including Azure CLI or Bash tabs in addition to PowerShell.
  • Clarify in the documentation which configurations are available for Linux and Windows, and provide guidance for both platforms.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/management-groups/manage.md ...b/main/articles/governance/management-groups/manage.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides parity between Azure Portal, Azure PowerShell, and Azure CLI for all management group operations. However, PowerShell examples are consistently presented before Azure CLI examples, and PowerShell-specific notes (such as parameter aliasing) are included. The PowerShell examples use Windows-style prompts (PS C:\>), and there is no mention of Linux shells or scripting environments. While Azure CLI is cross-platform, the documentation implicitly prioritizes Windows/PowerShell usage and patterns.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid implicit prioritization of Windows tools.
  • Add explicit notes that Azure CLI commands work identically on Linux, macOS, and Windows, and provide sample Bash or shell usage where appropriate.
  • Remove Windows-specific prompt formatting (e.g., PS C:\>) or provide equivalent Linux shell prompts (e.g., $) in CLI examples.
  • Include brief guidance for Linux users on installing and using Azure CLI and PowerShell Core, if relevant.
  • Where PowerShell-specific notes are given, add equivalent notes for CLI usage or clarify cross-platform applicability.
GitHub Create Pull Request
← Previous Page 20 of 25 Next →