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 501-525 of 613 flagged pages
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/concepts/definition-structure-parameters.md ...nce/policy/concepts/definition-structure-parameters.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates Windows bias primarily in the 'strongType' section, where the only tool mentioned for determining valid resource types is 'Get-AzResourceProvider', a PowerShell cmdlet. No Linux or cross-platform alternatives (such as Azure CLI) are referenced, and the Windows/PowerShell tool is introduced without parity or mention of equivalent Linux workflows. The rest of the page avoids OS-specific tooling and examples, focusing on JSON and Azure concepts.
Recommendations
  • Include Azure CLI equivalents (e.g., 'az provider show' or 'az resource list') alongside PowerShell examples to ensure Linux and macOS users have clear guidance.
  • When referencing tools, avoid mentioning Windows/PowerShell tools exclusively or first; present cross-platform options together or in a neutral order.
  • Add a note clarifying that both PowerShell and Azure CLI can be used to query resource providers, with example commands for each.
  • Review other sections for implicit assumptions about Windows environments and ensure all instructions are OS-agnostic or provide alternatives.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/whats-new/agent.md ...es/governance/machine-configuration/whats-new/agent.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 provides both Windows and Linux release notes in parallel, but in the example for updating the Linux extension, PowerShell is presented before Azure CLI, which may be less familiar to Linux users. Additionally, the use of PowerShell as the first example for Linux extension management suggests a Windows-centric approach. There are no Linux shell (bash) examples, and the documentation does not mention Linux-native tools or patterns for extension management.
Recommendations
  • Provide bash or shell script examples for Linux users alongside or before PowerShell examples.
  • Present Azure CLI examples before PowerShell when discussing Linux extensions, as CLI is more commonly used in Linux environments.
  • Mention Linux-native tools or package managers if relevant for managing the agent.
  • Review the ordering of examples and ensure Linux-relevant instructions are not secondary to Windows-centric tools.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by mentioning PowerShell and Azure CLI as the primary tools for specifying the 'mode' parameter in policy definitions. PowerShell is listed first, and the default behavior for 'mode' is described for Azure PowerShell before Azure CLI. There are no Linux-specific examples, nor is Bash or shell scripting referenced, and no explicit Linux tools or patterns are discussed.
Recommendations
  • Provide explicit examples using Bash or shell scripting for policy definition creation and management, alongside PowerShell and Azure CLI.
  • When mentioning tools, avoid listing Windows-centric tools (e.g., PowerShell) first; instead, present Azure CLI and Bash examples equally or in parallel.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, and provide usage notes or examples for Linux environments.
  • Add a section or note highlighting Linux compatibility and best practices for managing Azure Policy definitions from Linux systems.
  • Ensure that any references to command-line tools or scripting include both Windows and Linux usage patterns.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes using the Azure portal (a web UI) for policy assignment and management, with no command-line examples. In the exemption section, it mentions that resources can be created in exempted scopes using Azure CLI, Azure PowerShell, or ARM templates, but does not provide any CLI or script examples. The order of mention ('Azure CLI, Azure PowerShell, or ARM templates') is neutral, but the lack of actual examples for CLI tools (especially for Linux users) means the tutorial is Windows/portal-centric and omits Linux parity.
Recommendations
  • Add step-by-step examples for assigning and managing policies using Azure CLI and Azure PowerShell, including full command syntax.
  • Provide equivalent instructions for Linux and macOS users, especially for exemption creation and resource management.
  • Include sample scripts for common tasks (assignment, exemption, clean-up) using cross-platform tools (Azure CLI, ARM templates), not just portal navigation.
  • Explicitly mention platform compatibility for each tool and provide links to installation guides for Azure CLI and PowerShell on Linux/macOS.
  • Consider reordering or balancing the presentation of portal and CLI/script-based workflows to avoid implicit prioritization of Windows/portal approaches.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/alerts-query-quickstart.md ...s/governance/resource-graph/alerts-query-quickstart.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Linux First Missing Windows Example
Summary
The documentation demonstrates a bias toward Linux by providing detailed instructions and examples specifically for creating and configuring an Ubuntu Linux virtual machine. There are no equivalent instructions, examples, or references for creating or managing a Windows virtual machine, nor are there any Windows-specific tools, PowerShell commands, or screenshots. The agent installation and verification steps are also Linux-centric, with no mention of Windows agent setup or validation.
Recommendations
  • Add a parallel example for creating a Windows virtual machine, including recommended OS version and configuration steps.
  • Include instructions for installing and verifying the Azure Monitor Agent on Windows VMs, referencing Windows-specific settings and agent extensions.
  • Provide screenshots and walkthroughs for Windows VM setup and monitoring agent status.
  • Where queries or agent steps differ for Windows, clarify those differences and provide both Linux and Windows code snippets or UI paths.
  • Explicitly mention that the process applies to both Linux and Windows, or clarify any limitations or differences in alerting or monitoring capabilities.
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-08 00:53
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 cross-platform) and the absence of Linux-specific shell examples (such as Bash or scripting with jq/curl) indicates a bias toward Windows tooling. Additionally, PowerShell examples are given equal prominence to CLI, which can reinforce Windows-first patterns for users. There are no explicit Linux shell or scripting examples, nor guidance for Linux users beyond the CLI.
Recommendations
  • Add Linux/Bash shell examples using az CLI and common Linux tools (e.g., piping to jq, curl, grep) to demonstrate usage in Linux environments.
  • Clarify that Azure CLI is cross-platform and provide explicit instructions for running queries in Linux/macOS terminals.
  • Consider including a section or tab for 'Linux Shell' or 'Bash' to balance the PowerShell tab.
  • If PowerShell is shown, note its cross-platform availability and provide installation/usage notes for Linux/macOS.
  • Review documentation for any assumptions about Windows environments and add notes for Linux-specific considerations (e.g., authentication, environment variables, output formatting).
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-08 00:53
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 consistently lists Azure PowerShell (a Windows-centric tool) as a primary tab alongside Azure CLI. There are no Linux-specific shell examples (e.g., Bash with curl, jq, etc.), nor is there mention of Linux-native scripting or integration patterns. The CLI examples are cross-platform, but the presence and prominence of PowerShell may suggest a slight Windows bias.
Recommendations
  • Add explicit Bash/Linux shell examples using Azure CLI to demonstrate usage in a Linux environment (e.g., piping output to jq for parsing).
  • Clarify that Azure CLI is fully cross-platform and highlight its usage in Linux/macOS terminals.
  • Consider reordering tabs so that Azure CLI (the cross-platform tool) appears before PowerShell, or make CLI the default example.
  • Mention Linux-native automation options (e.g., scripting with Bash, using cron jobs) where relevant.
  • If PowerShell is shown, note that PowerShell Core is available on Linux, but provide examples of usage in both Windows and Linux contexts.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/microsoft-defender.md ...aph/includes/samples-by-category/microsoft-defender.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 provides both Azure CLI and Azure PowerShell examples for every query, but PowerShell is always given equal prominence, and in some cases, the PowerShell tab appears before the Portal tab. There are no Linux-specific shell examples (e.g., Bash, zsh), nor are there any references to Linux-native tools or scripting patterns. The documentation assumes parity between Azure CLI and PowerShell, but PowerShell is a Windows-centric tool, and its inclusion may signal a Windows bias, especially in environments where Linux is more common.
Recommendations
  • Add explicit Bash/zsh shell examples for each query, showing usage in Linux environments.
  • Clarify that Azure CLI is cross-platform and highlight its use on Linux/macOS.
  • Consider reordering tabs so that Azure CLI (the cross-platform tool) appears before PowerShell.
  • Add notes or sections about running these queries in Linux containers or cloud shells.
  • If PowerShell is included, also mention PowerShell Core and its cross-platform availability, but avoid implying it is the default for all users.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/ukofficial-uknhs.md ...cles/governance/blueprints/samples/ukofficial-uknhs.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows Linux Parity Artifact Equivalence
Summary
The documentation provides equivalent treatment for both Windows and Linux in the context of deploying Log Analytics Agents, listing both as preview artifacts with similar descriptions and options. There is no evidence of Windows bias in terms of examples, tools, or ordering; both platforms are referenced together and neither is prioritized. No PowerShell or Windows-specific tools are mentioned, and no examples are provided that favor Windows over Linux.
Recommendations
  • Continue to ensure that all platform-specific artifacts (e.g., Log Analytics Agent for Linux and Windows) are documented with equal detail and clarity.
  • If command-line or automation examples are added in the future, provide both PowerShell (Windows) and Bash/CLI (Linux) equivalents.
  • Explicitly mention cross-platform compatibility in relevant sections to reinforce parity.
  • If there are differences in deployment or management for Linux vs. Windows, highlight those differences and provide guidance for both.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents the Azure Policy alias discovery methods in an order that prioritizes Windows-centric tools: the Visual Studio Code extension (commonly used on Windows), followed by Azure PowerShell (Windows/PowerShell-centric), then Azure CLI (cross-platform), and finally REST API. The PowerShell example is more detailed, with additional notes and advanced usage, whereas the Azure CLI section is more basic. There are no Linux-specific examples or mentions of Linux tools, and PowerShell commands are given more prominence and depth.
Recommendations
  • Add parity in example depth for Azure CLI, including advanced queries and notes similar to those provided for PowerShell.
  • Explicitly mention that Azure CLI and REST API are cross-platform and suitable for Linux/macOS users.
  • Consider presenting Azure CLI before PowerShell to avoid implicit Windows-first ordering.
  • Include a brief example or note for using these commands in a Linux shell (e.g., bash), or clarify that all CLI commands work on Linux.
  • If possible, add links or references to Linux-specific tooling or integrations for Azure Policy management.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates bias toward Windows by providing only Windows-style execution instructions (using mgCreate.exe with backtick line continuations) and omitting Linux-specific guidance, such as how to run the published .NET Core application on Linux/macOS, or using Linux shell conventions. There are no Linux or cross-platform examples for running the application, nor any mention of Linux-specific considerations.
Recommendations
  • Include Linux/macOS instructions for running the published .NET Core application (e.g., using 'dotnet mgCreate.dll' or './mgCreate' if self-contained).
  • Show both Windows (mgCreate.exe) and Linux/macOS (mgCreate, mgCreate.dll) command examples, using appropriate line continuation characters (backslash for bash, backtick for PowerShell).
  • Clarify that .NET Core is cross-platform and provide guidance for users on non-Windows systems.
  • Mention any platform-specific prerequisites or differences (such as executable file extensions, permissions, or shell usage).
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-08 00:53
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 are Linux-specific configuration assignments or resources mentioned.
Recommendations
  • Add equivalent examples for Linux virtual machines using azurerm_linux_virtual_machine.
  • Include built-in Linux configuration assignments, such as AzureLinuxBaseline, if available.
  • Provide guidance on how to specify Linux-specific configuration parameters and package formats.
  • Ensure references and links include Linux-focused getting started guides, not just Windows/Powershell.
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-08 00:53
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 PowerShell immediately after CLI and before any mention of Linux-specific tools or shell environments. PowerShell is traditionally associated with Windows, and there are no Linux shell (bash, zsh) or scripting examples provided. The Azure CLI example is cross-platform, but the absence of explicit Linux shell usage or notes may leave Linux users without tailored guidance.
Recommendations
  • Add explicit bash or zsh shell examples to demonstrate usage on Linux and macOS platforms.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide shell-specific invocation examples (e.g., with single quotes, environment variables).
  • Consider reordering examples or grouping them by platform, or explicitly stating platform compatibility for each example.
  • If PowerShell is shown, mention that PowerShell Core is available cross-platform, and provide a Linux PowerShell invocation example if relevant.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided in detail and are presented before Azure CLI equivalents in each relevant section. The portal instructions are also Windows-centric, as the Azure portal is most commonly accessed from Windows environments. There are no Linux-specific shell examples (e.g., Bash), nor are there references to Linux-native tools or workflows. The CLI examples are present, but they are less detailed than the PowerShell ones, and PowerShell is consistently listed before CLI, reinforcing a Windows-first approach.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first in some sections to avoid implicit prioritization.
  • Expand Azure CLI examples to match the detail and explanation provided for PowerShell, including more context and optional parameters.
  • Include explicit Bash shell examples where appropriate, especially for scripting scenarios, to support Linux users.
  • Add notes or sections highlighting Linux compatibility and any platform-specific considerations for Azure CLI and SDK usage.
  • Clarify that the Azure portal is cross-platform and accessible from any modern browser, not just Windows.
  • Where possible, provide links or references to Linux-specific documentation or troubleshooting guides.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/overview.md ...-docs/blob/main/articles/governance/policy/overview.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by mentioning PowerShell and Azure CLI as the primary command-line interfaces for managing Azure Policy assignments, with PowerShell listed first. There are no explicit Linux-specific examples, nor is Bash or shell scripting referenced. The page does not mention Linux tools or workflows, and the examples and tooling recommendations are platform-neutral but default to Windows-centric patterns.
Recommendations
  • Add explicit Bash or shell scripting examples for Azure Policy management alongside PowerShell and Azure CLI.
  • When listing command-line tools, alternate the order or mention Bash/Azure CLI before PowerShell to avoid Windows-first bias.
  • Include references to Linux-native workflows and tools (e.g., scripting with Bash, using Azure CLI on Linux) in the 'Manage Azure Policy resources as code' section.
  • Provide links to Linux-specific quickstarts or tutorials for Azure Policy assignments.
  • Clarify that Azure CLI and PowerShell are cross-platform, and highlight usage on Linux and macOS where relevant.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-sql.md ...source-graph/includes/samples-by-category/azure-sql.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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, but the PowerShell example is given equal prominence to the CLI example and is included before any mention of Linux-specific tools or shell environments. There are no Linux shell-specific examples (e.g., Bash), nor is there mention of Linux-native scripting or usage patterns. The CLI example is cross-platform, but the presence of PowerShell (a Windows-centric tool) without explicit Linux/Bash parity suggests a subtle Windows bias.
Recommendations
  • Add explicit Bash shell examples to demonstrate usage in Linux environments.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and show sample output in a Linux terminal.
  • If PowerShell is included, also mention PowerShell Core and its cross-platform support, or provide a Bash alternative.
  • Consider reordering examples to present the cross-platform Azure CLI first, followed by Bash, then PowerShell, to avoid implicit Windows prioritization.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/management-groups.md ...raph/includes/samples-by-category/management-groups.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 consistently provides both Azure CLI and Azure PowerShell examples for each scenario, but PowerShell (a Windows-centric tool) is always presented as a primary tab alongside CLI, and sometimes before or with equal prominence. There are no Linux-specific shell examples (e.g., Bash scripts), nor is there mention of Linux-native tools or patterns. The CLI examples are cross-platform, but the documentation does not clarify this or highlight Linux parity.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
  • Add example usage in Bash or other Linux shells where appropriate, especially for scripting scenarios.
  • Consider reordering tabs to show Azure CLI first, as it is cross-platform, and clarify PowerShell's Windows-centric nature.
  • Mention installation and usage differences for CLI and PowerShell on Linux vs. Windows.
  • Where possible, include troubleshooting or environment notes for 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-08 00:53
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 ordering of tabs (CLI, PowerShell, Portal) may suggest a slight Windows-first bias. There are no explicit Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-native tools or patterns. The PowerShell example uses syntax and escaping conventions specific to Windows/PowerShell, which may be less familiar to Linux users.
Recommendations
  • Add explicit Bash shell examples using Azure CLI to demonstrate Linux usage (e.g., show how to run the query in a Linux terminal).
  • Clarify that Azure CLI works natively on Linux, macOS, and Windows, and provide installation links for each platform.
  • If PowerShell is included, note that PowerShell Core is available on Linux and macOS, and provide guidance for Linux users on how to run the example.
  • Consider reordering tabs or providing a Linux-first example to balance platform representation.
  • Mention 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/azure-service-health.md ...h/includes/samples-by-category/azure-service-health.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 consistently provides both Azure CLI and Azure PowerShell examples for each query, but PowerShell is a Windows-centric tool and is featured equally alongside CLI. There are no Linux-specific shell examples (e.g., Bash, shell scripting), nor is there mention of Linux-native tools or patterns. The ordering of examples is generally Azure CLI first (cross-platform), then PowerShell (Windows), but the presence of PowerShell throughout and lack of Linux shell examples indicates a subtle Windows bias.
Recommendations
  • Add explicit Bash/shell script examples for each query to demonstrate Linux parity.
  • Clarify that Azure CLI commands work natively on Linux, macOS, and Windows, and provide platform-specific notes if needed.
  • Consider including examples using other cross-platform tools (e.g., REST API via curl, Python SDK) to further reduce Windows bias.
  • If PowerShell is included, note that PowerShell Core is available on Linux/macOS, but provide native shell alternatives for Linux users.
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-08 00:53
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. The PowerShell example is given equal prominence to the CLI, and there is no explicit mention of Linux-specific usage patterns, such as shell scripting or alternative Linux tools. The ordering of examples (CLI, then PowerShell, then Portal) is common, but the inclusion of PowerShell without any Linux shell (bash/zsh) examples or notes may suggest a mild Windows bias.
Recommendations
  • Add explicit Linux shell (bash/zsh) examples using Azure CLI to demonstrate usage in Linux environments.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
  • Consider including notes or links to Linux-specific documentation or troubleshooting for Azure CLI.
  • If PowerShell is shown, mention that PowerShell Core is available cross-platform, or provide bash equivalents where relevant.
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-08 00:53
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 is no explicit Linux shell (e.g., Bash) example, nor is there mention of Linux-specific patterns or tools. The ordering places Azure CLI first, which is positive for parity, but the inclusion of PowerShell without a corresponding Bash or shell script example introduces a subtle Windows bias.
Recommendations
  • Add a Bash shell example using Azure CLI to explicitly demonstrate Linux usage.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
  • Consider including a note or tab for Linux users, highlighting any OS-specific considerations.
  • If PowerShell is included, mention that PowerShell Core is cross-platform, or provide a Bash alternative.
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.md ...gory/query/virtual-instance-sap-solutions-vm-health.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 provides both Azure CLI and Azure PowerShell examples for all queries, but PowerShell is given equal prominence as CLI, despite being a Windows-specific tool. There are no Linux shell (bash) or scripting examples, and no mention of Linux-specific usage patterns or tools. The examples and tabs are structured to highlight PowerShell, which may suggest a Windows-centric approach.
Recommendations
  • Add explicit bash/Linux shell examples for running az graph queries, including sample output redirection and parsing (e.g., using jq).
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Consider reordering tabs to show Azure CLI first, emphasizing its cross-platform nature.
  • Provide guidance for Linux users on installing and using Azure CLI, and note that PowerShell is optional.
  • If relevant, mention any differences or caveats when running queries on Linux vs. Windows environments.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, with PowerShell (a Windows-centric tool) given its own tab and example. There is no explicit mention of Linux shell equivalents (e.g., Bash), nor is there guidance for running the CLI commands in Linux environments. The ordering places Azure CLI first, but PowerShell is given equal prominence, and no Linux-specific context or examples are provided.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI usage, including sample commands and expected output.
  • Clarify that Azure CLI commands work cross-platform and provide guidance for Linux users (e.g., installation, environment setup).
  • If PowerShell is mentioned, also mention alternatives for Linux (such as Bash scripts or native shell usage).
  • Consider reordering or grouping examples to avoid implying Windows/PowerShell as the default or preferred environment.
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-08 00:53
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 querying the App Service TLS version, but lists PowerShell as a primary tab alongside CLI and Portal. PowerShell is a Windows-centric tool, and its inclusion as a main example (rather than, for example, Bash or Linux shell alternatives) suggests a Windows-first approach. There are no explicit Linux shell or Bash examples, and PowerShell is presented as an equal alternative to the cross-platform CLI, which may reinforce Windows bias.
Recommendations
  • Add explicit Bash or Linux shell examples for running the Azure CLI command.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Consider listing Azure CLI before PowerShell, or providing a Linux-specific tab to improve parity.
  • Mention that PowerShell Core is available cross-platform, if relevant, to reduce perception of Windows exclusivity.
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-08 00:53
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 is no explicit Linux shell (e.g., Bash) example, nor any mention of Linux-specific tools or workflows. The ordering places Azure CLI first, which is positive for parity, but the inclusion of PowerShell without a corresponding Bash or Linux shell example suggests a mild Windows bias.
Recommendations
  • Add explicit Bash shell examples for Linux users, demonstrating the same query using az graph query.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
  • If PowerShell is included, consider also providing examples using native Linux shells to ensure parity.
  • Mention cross-platform compatibility for each tool where relevant.
GitHub Create Pull Request
← Previous Page 21 of 25 Next →