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 251-275 of 613 flagged pages
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/develop-custom-package/overview.md ...onfiguration/how-to/develop-custom-package/overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by focusing on PowerShell Desired State Configuration (PSDSC) and the GuestConfiguration PowerShell module as the primary tools for authoring and validating machine configuration packages. The instructional video and linked resources are PowerShell-centric, with no Linux-specific examples, tools, or workflows provided. While Linux support is mentioned, practical guidance and examples for Linux users are missing, and Windows/PowerShell patterns are presented as the default.
Recommendations
  • Include Linux-specific examples for authoring, testing, and publishing machine configuration packages, using native Linux tools and workflows.
  • Provide guidance on using DSC on Linux, including supported modules, configuration syntax, and troubleshooting steps.
  • Add sample commands and scripts for Linux environments (e.g., Bash, shell scripts) alongside PowerShell examples.
  • Reference Linux documentation and resources equally, and consider adding a Linux-focused instructional video.
  • Clarify any differences in workflow or tooling between Windows and Linux, and highlight Linux compatibility and best practices.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/how-to/programmatically-create.md ...es/governance/policy/how-to/programmatically-create.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a Windows bias by prioritizing PowerShell instructions and tools, referencing Windows-specific installation paths, and omitting explicit Linux/macOS guidance. PowerShell is presented before Azure CLI, and ARMClient (a .NET/Windows-centric tool) is recommended without alternatives. The Azure CLI installation link is for Windows only, and there are no Linux/macOS-specific notes or examples, especially in the prerequisites and tool installation sections.
Recommendations
  • Provide Azure CLI installation instructions and links for Linux and macOS alongside Windows.
  • Present Azure CLI examples before or alongside PowerShell to avoid implying PowerShell is the primary or preferred method.
  • Include Bash shell examples where appropriate, especially for scripting and automation.
  • Mention cross-platform alternatives to ARMClient, or clarify its compatibility with non-Windows systems.
  • Explicitly state that both Azure CLI and PowerShell are cross-platform, and provide OS-agnostic instructions for installing and using them.
  • Ensure all code snippets and instructions are tested and applicable on Linux/macOS as well as Windows.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/concepts/effect-modify.md ...n/articles/governance/policy/concepts/effect-modify.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through its exclusive use of Azure PowerShell for command-line examples (specifically, the Get-AzPolicyAlias cmdlet), without mention of Azure CLI or other cross-platform tools. No Linux-specific or cross-platform command-line examples are provided, and the only referenced tooling is PowerShell, which is traditionally associated with Windows environments. This may disadvantage users on Linux or macOS who prefer or require Azure CLI or other non-PowerShell interfaces.
Recommendations
  • Include equivalent Azure CLI examples for all PowerShell commands, especially for listing modifiable aliases.
  • Explicitly mention that Azure CLI is supported and provide links or references to relevant documentation.
  • Where possible, use cross-platform language and tooling in examples (e.g., bash scripts, REST API calls) alongside PowerShell.
  • Clarify that PowerShell is available on Linux and macOS, but also provide alternatives for users who do not use PowerShell.
  • Review all examples and instructions to ensure parity for Linux and macOS users, not just Windows/PowerShell users.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/overview/02-setup-prerequisites.md ...chine-configuration/overview/02-setup-prerequisites.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. Windows and PowerShell tools are mentioned first in several sections, such as validation tools and managed identity configuration. PowerShell Desired State Configuration (DSC) is emphasized for both Windows and Linux, with no mention of native Linux configuration tools (e.g., Ansible, Bash, or cloud-init). The instructions for configuring managed identities reference the Azure portal specifically for Windows VMs, and there is no Linux-specific portal or CLI walkthrough. Chef InSpec is mentioned for Linux, but only as a validation tool, not for configuration. Overall, the documentation assumes familiarity with Windows-centric tools and workflows, with Linux equivalents either missing or presented second.
Recommendations
  • Provide Linux-first or parallel examples for key workflows, such as managed identity configuration and extension deployment.
  • Include references to native Linux configuration tools (e.g., Ansible, cloud-init) where appropriate, or clarify why PowerShell DSC is preferred on Linux.
  • Add explicit Linux CLI walkthroughs for tasks currently described only for Windows or generically.
  • Balance the order of tool presentation in tables and lists to avoid always listing Windows first.
  • Clarify any differences in extension deployment or management between Windows and Linux VMs.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/concepts/initiative-definition-structure.md ...nce/policy/concepts/initiative-definition-structure.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits mild Windows bias. The only specific tooling mentioned for resource type validation is 'Get-AzResourceProvider', a PowerShell cmdlet, with no mention of Linux/CLI alternatives. The order of presentation and examples tends to reference Windows/PowerShell tools first or exclusively, without providing parity for Linux users (e.g., Azure CLI or REST API). No explicit Linux examples or instructions are present.
Recommendations
  • Where PowerShell cmdlets are referenced (e.g., Get-AzResourceProvider), also provide the equivalent Azure CLI command (e.g., 'az provider show') and/or REST API method.
  • Include examples or notes for Linux/macOS users, especially for command-line operations, to ensure cross-platform usability.
  • Review all tooling references and ensure both Windows (PowerShell) and Linux (CLI) options are presented side-by-side.
  • Add a section or note clarifying that all JSON-based policy definitions and assignments can be managed equally from any OS using Azure CLI, REST API, or SDKs.
  • Where portal instructions are given, clarify that the portal is OS-agnostic.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/samples/built-in-packages.md ...rticles/governance/policy/samples/built-in-packages.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias: the majority of policy definitions and examples are Windows-specific, with only a handful of Linux-related entries. The documentation references PowerShell Desired State Configuration (DSC) and PowerShell modules as the primary configuration mechanism, which is inherently Windows-centric. Linux policies are few, and there are no Linux-specific configuration module links or detailed parity in examples. The language and tooling focus on Windows patterns and tools, with Linux support appearing as an afterthought.
Recommendations
  • Increase the number and visibility of Linux-specific policy definitions and configuration examples.
  • Provide equivalent Linux configuration module links and documentation, not just for baseline policies but for other common scenarios (e.g., password policies, service status, certificate management).
  • Balance the order and presentation of Windows and Linux policies, or group them by OS to avoid implicit prioritization.
  • Reference and link to Linux-native configuration tools or modules (such as Ansible, Chef, or native Linux DSC resources) where appropriate.
  • Clarify in the introduction that PowerShell DSC is primarily for Windows, and explicitly mention the configuration approach for Linux systems.
  • Where a policy is Windows-only, consider providing a Linux equivalent or noting the lack of parity.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/concepts/policy-for-kubernetes.md ...es/governance/policy/concepts/policy-for-kubernetes.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Azure CLI and Azure portal are used for most examples, but Azure PowerShell is also mentioned as an alternative for resource provider registration. All portal instructions implicitly assume Windows usage, and all CLI examples use Azure CLI, which is cross-platform, but there are no explicit Linux shell or macOS-specific instructions. The documentation references Windows domains (login.windows.net) and does not provide parity for Linux-specific troubleshooting or installation patterns. Additionally, PowerShell is mentioned before Bash/Helm in some cases, and there are no examples using native Linux tools or package managers. The FAQ section clarifies that many policy definitions only apply to Linux pods, but does not provide guidance for Linux users or mention Linux-specific caveats beyond this.
Recommendations
  • Add explicit instructions for Linux and macOS environments, including shell commands and references to package managers (e.g., apt, yum, brew) for installing Azure CLI.
  • Provide parity for PowerShell examples by including Bash equivalents where possible.
  • Clarify that Azure CLI is cross-platform and provide troubleshooting steps for Linux users (e.g., permissions, environment variables).
  • Include Linux-specific troubleshooting steps, such as log file locations, SELinux/AppArmor caveats, or systemd service management.
  • Avoid referencing Windows domains or tools exclusively; where possible, mention that the domains are accessed from any OS.
  • In portal instructions, clarify that the Azure portal is accessible from any OS and provide screenshots or steps relevant to Linux users.
  • Where Windows-specific limitations are mentioned (e.g., Windows pods not supporting security contexts), provide guidance for Linux users and highlight Linux advantages.
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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed examples for Azure PowerShell and Azure CLI, but the PowerShell example is more elaborate (including conversion to JSON), which may favor Windows users. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples showing how to process or export policy resources using Linux-native tools. The ordering places Azure CLI first, but the PowerShell section is more detailed, and no Linux-specific patterns or tools are discussed.
Recommendations
  • Provide equivalent Bash examples for exporting and processing Azure Policy resources, demonstrating use of jq or other Linux-native tools for JSON manipulation.
  • Ensure parity in example detail: if PowerShell examples show advanced processing (e.g., ConvertTo-Json), show how to achieve the same with Azure CLI and Linux tools.
  • Explicitly mention cross-platform compatibility for Azure CLI commands and clarify that they work on Linux, macOS, and Windows.
  • Add a section or note on how to install and use Azure CLI on Linux, and reference common Linux shell environments.
  • Avoid assuming PowerShell is the default scripting environment; balance with examples for Bash/zsh/fish where appropriate.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/concepts/get-list-query-service-differences.md ...e-graph/concepts/get-list-query-service-differences.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell as a supported client before Azure CLI, and by referencing PowerShell-specific tabs in example links. There are no explicit Linux or bash examples, nor is there mention of Linux-specific tooling or usage patterns. The documentation does not provide parity in examples or guidance for Linux users.
Recommendations
  • Add explicit bash/Azure CLI examples alongside PowerShell examples.
  • Reference Linux usage patterns and tools (e.g., curl, jq) when discussing REST API usage.
  • Ensure links to example tabs include both PowerShell and CLI/bash options.
  • List Azure CLI before or alongside PowerShell when enumerating supported clients.
  • Include notes or sections for Linux users to clarify platform-agnostic usage.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-arc-enabled-kubernetes.md ...es/samples-by-category/azure-arc-enabled-kubernetes.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal for each query, but does not include any Linux-specific shell examples (such as Bash or scripting with curl/jq). Azure PowerShell is featured as a primary method alongside Azure CLI, which may suggest a Windows-centric approach. There is no mention of Linux-native tools or patterns, nor any guidance for users working in Linux environments.
Recommendations
  • Add explicit Bash shell examples for each query, demonstrating usage of az CLI in Linux environments.
  • Clarify that Azure CLI is cross-platform and provide sample commands for Linux/macOS terminals.
  • Consider including usage patterns with Linux-native tools (e.g., piping az CLI output to jq for JSON parsing).
  • Reorder examples to present Azure CLI (cross-platform) before Azure PowerShell (Windows-centric), or clarify parity.
  • Add a note about 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/policy/tutorials/create-and-manage.md ...icles/governance/policy/tutorials/create-and-manage.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Azure PowerShell examples, referencing Windows file paths (e.g., C:\policies\coolAccessTier.json), and omitting Linux-specific instructions or examples (such as bash shell or Linux file paths). PowerShell usage is described in detail before Azure CLI, and there are no explicit Linux shell or cross-platform notes. The documentation assumes familiarity with Windows conventions and tools, which may disadvantage Linux users.
Recommendations
  • Provide Linux-specific examples, such as using bash shell and Linux file paths (e.g., /home/user/policies/coolAccessTier.json) alongside Windows examples.
  • Add notes clarifying that Azure CLI and REST API are cross-platform and can be used on Linux, macOS, and Windows.
  • Ensure parity in example ordering: present Azure CLI and PowerShell examples together or alternate their order to avoid Windows-first bias.
  • Include instructions for installing and using Azure CLI and PowerShell on Linux systems.
  • Avoid exclusive use of Windows-centric terminology (e.g., 'right-click', 'C:\') and provide equivalent actions for Linux environments.
  • Explicitly mention that all commands (except PowerShell-specific ones) work on Linux, and provide troubleshooting tips for Linux users.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/how-to/get-compliance-data.md ...ticles/governance/policy/how-to/get-compliance-data.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for command-line operations, but PowerShell is given equal or slightly more prominence, with more detailed usage and job control examples. PowerShell-specific concepts (jobs, Get-Member) are explained, while equivalent Linux shell patterns are not mentioned. Visual Studio Code and GitHub Actions are included as cross-platform tools, but there is a subtle bias toward Windows/PowerShell workflows, and no explicit mention of Linux shell scripting or native Linux tools. PowerShell examples are provided before CLI in some sections, and advanced PowerShell usage is described in detail, whereas Linux shell equivalents are absent.
Recommendations
  • Add Linux shell (bash) scripting examples for REST API calls, such as using curl or wget, especially in sections describing REST API usage.
  • Provide more advanced Azure CLI usage examples, such as background execution, piping, and filtering, to match the depth of PowerShell job control explanations.
  • Explicitly mention that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
  • Where PowerShell job control is described, offer equivalent Linux/Unix patterns (e.g., using & for background jobs, or using tools like jq for JSON parsing).
  • Ensure that CLI examples are presented before or alongside PowerShell examples to avoid 'windows_first' ordering.
  • Add a note or section highlighting Linux-native workflows for Azure Policy management, including integration with shell scripts and automation tools.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/concepts/policy-as-code.md .../articles/governance/policy/concepts/policy-as-code.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. In the 'Source control' section, PowerShell is mentioned first as a way to export policy and initiative definitions, with CLI only mentioned secondarily and without specific examples for either. There are no explicit Linux shell (bash) or cross-platform scripting examples, nor are Linux-specific tools or workflows referenced. The documentation does not provide parity in examples or guidance for Linux users, and the overall pattern is to mention Windows-oriented tools and approaches first.
Recommendations
  • Provide explicit examples for both PowerShell and Azure CLI, including bash shell usage for Linux/macOS environments.
  • When listing tools or approaches, alternate the order or mention CLI/bash first to avoid implicit prioritization of Windows tools.
  • Include references to Linux-native automation tools (e.g., shell scripts, cron jobs) where relevant.
  • Add sample workflows or code snippets that demonstrate policy management using Azure CLI in a Linux environment.
  • Clarify that all steps can be performed cross-platform and highlight any platform-specific considerations.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/concepts/query-language.md ...s/governance/resource-graph/concepts/query-language.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page provides shell-specific guidance for escaping characters, mentioning Bash, cmd, and PowerShell. However, PowerShell (Windows) is described in detail, and examples for Linux shells (Bash) are minimal and not presented first. There are no CLI examples using Linux-native tools (e.g., Azure CLI on Linux, curl, etc.), and REST API examples are generic without shell invocation context. The escape character section lists PowerShell after Bash, but cmd (Windows) is mentioned before PowerShell and Bash. Overall, the documentation lacks Linux-specific usage patterns and examples, and does not offer parity in guidance for Linux users.
Recommendations
  • Add explicit Linux shell (Bash, zsh) examples for REST API invocation, such as using curl or az CLI.
  • Provide Linux-first or at least equal examples alongside PowerShell, especially in sections discussing shell-specific syntax.
  • Include guidance for escaping characters in other popular shells (e.g., zsh, fish) and clarify differences.
  • Reference Linux tools and usage patterns where appropriate, not just Windows-centric ones.
  • Ensure that sample queries and code snippets are runnable in both Windows and Linux environments, and note any differences.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/tutorials/modify-virtual-machine-identity.md ...ce/policy/tutorials/modify-virtual-machine-identity.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides detailed instructions for using the Azure Portal and PowerShell (specifically Azure PowerShell) to add user assigned managed identities to virtual machines. There are no examples or guidance for Linux users, such as using Azure CLI or Bash scripts. PowerShell is a Windows-centric tool, and its exclusive use in command-line examples demonstrates a Windows bias. Additionally, the lack of mention or prioritization of cross-platform tools like Azure CLI further reinforces this bias.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash script snippets for Linux users where appropriate.
  • Explicitly mention that both Azure PowerShell and Azure CLI can be used, and provide links to relevant CLI documentation.
  • Reorder sections so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell examples.
  • Clarify that the steps are applicable regardless of OS, and avoid implying that PowerShell is the default or only option.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/how-to/migrate-from-automanage-best-practices.md ...olicy/how-to/migrate-from-automanage-best-practices.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates several types of Windows bias. Windows-specific tools and features (such as Windows Admin Center and Antimalware extensions) are highlighted, often with examples or links that focus exclusively on Windows. In multiple sections, Windows VM configuration and policies are described before their Linux equivalents, and some features (e.g., Windows Admin Center, Antimalware) are presented as Windows-only without Linux alternatives or parity guidance. There is a lack of Linux-specific examples, especially for management and monitoring tasks, and no mention of Linux-native tools or workflows.
Recommendations
  • Provide equivalent Linux examples and workflows for all features discussed, especially where Windows-specific tools (e.g., Windows Admin Center, Antimalware) are mentioned.
  • When listing configuration steps or policy assignments, present Windows and Linux options together or alternate which is listed first.
  • Include references to Linux-native management tools (such as Cockpit, SSH, or Linux package managers) where relevant.
  • Clarify which features are Windows-only and suggest Linux alternatives or workarounds.
  • Add explicit Linux-focused guidance for policy creation, monitoring, and automation tasks, including sample policy definitions and links to Linux documentation.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/tutorials/create-custom-policy-definition.md ...ce/policy/tutorials/create-custom-policy-definition.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell when discovering policy aliases, but it lists Azure CLI first and then Azure PowerShell, which is a common Windows tool. However, there is no explicit mention of Linux-specific tools or shell patterns (such as bash scripting), nor are there examples tailored for Linux environments. The use of VS Code extension is platform-neutral, but the overall example set leans towards Windows-centric tools and workflows, with PowerShell featured prominently and no Linux shell alternatives provided.
Recommendations
  • Include explicit bash or shell script examples for Linux users alongside Azure CLI and PowerShell examples.
  • Clarify that Azure CLI commands work cross-platform and provide sample usage in Linux shells (e.g., bash, zsh).
  • Mention Linux-native editors (such as Vim or nano) for editing policy definitions, in addition to VS Code.
  • Add a note or section highlighting any platform-specific differences in command usage or authentication (e.g., az login in Linux vs. Windows).
  • Ensure that all steps and tools referenced are accessible and documented for both Windows and Linux users.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/first-query-rest-api.md ...cles/governance/resource-graph/first-query-rest-api.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias by listing PowerShell before Bash in shell examples, referencing PowerShell and Git Bash as the main shells, and recommending Visual Studio Code (a Microsoft product) as the terminal environment. The prerequisites mention PowerShell first and only suggest 'Bash shell like Git Bash' rather than native Linux shells. There is no explicit Linux example or mention of native Linux environments, and the guidance is tailored to Windows-centric tooling and patterns.
Recommendations
  • List Bash (and/or native Linux shells) before PowerShell in examples and prerequisites to avoid 'windows_first' ordering.
  • Explicitly mention native Linux and macOS terminals as supported/tested environments, not just 'Bash shell like Git Bash'.
  • Provide examples or notes for running commands in native Linux and macOS environments, not just PowerShell and Git Bash.
  • Consider recommending cross-platform editors or terminals (e.g., 'any terminal of your choice') rather than only Visual Studio Code.
  • Clarify that the Azure CLI and REST API commands work identically on Linux, macOS, and Windows, and provide troubleshooting tips for common Linux/macOS issues if any.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/concepts/work-with-data.md ...s/governance/resource-graph/concepts/work-with-data.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation consistently provides examples using Azure CLI and Azure PowerShell, with PowerShell (a Windows-centric tool) featured alongside CLI in every code example. There are no examples using Bash, shell scripting, or Linux-specific tools. The documentation does not mention Linux environments, nor does it provide guidance or parity for Linux users beyond the Azure CLI, which is cross-platform but often used in Bash on Linux. PowerShell is presented as an equal alternative to CLI, despite its Windows origins and lower prevalence on Linux.
Recommendations
  • Add explicit Bash/shell script examples for each CLI command, demonstrating usage in a Linux terminal.
  • Clarify that Azure CLI is cross-platform and provide guidance for installation and usage on Linux.
  • De-emphasize PowerShell as the primary alternative to CLI, or at least add notes about PowerShell Core being available on Linux and macOS.
  • Include references to Linux tools (e.g., jq for JSON processing) when discussing result formatting and manipulation.
  • Add a section or note on platform compatibility for all tools mentioned, helping users on Linux or macOS understand their options.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/concepts/explore-resources.md ...overnance/resource-graph/concepts/explore-resources.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell examples are provided alongside Azure CLI for every query, and PowerShell-specific notes and output handling (e.g., ConvertTo-Json, variable usage) are included. Windows-centric resource properties (e.g., osType: Windows, windowsConfiguration) are shown in JSON samples. When scripting with Azure CLI, Linux tools (awk, sed, tail) are used, but there is no explicit mention of Linux shell environments or alternatives for Windows users. The PowerShell examples and notes are more detailed than the CLI equivalents, and Windows terminology appears first in several places.
Recommendations
  • Add explicit notes about running Azure CLI commands in Bash (Linux/macOS) and PowerShell (Windows), clarifying environment differences.
  • Provide equivalent examples for Linux and macOS users, including shell scripting alternatives for PowerShell variable handling.
  • Balance PowerShell-specific notes with Bash/Linux shell scripting notes, especially regarding output formatting and file handling.
  • Include sample JSON outputs for Linux-based VMs and resources, not just Windows-centric properties.
  • Where possible, alternate the order of CLI and PowerShell examples, or group them together without preference.
  • Add links or references to cross-platform scripting guides for Azure CLI and PowerShell.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-advisor.md ...ce-graph/includes/samples-by-category/azure-advisor.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal, but does not include any Linux-specific shell examples (such as Bash or shell scripting). The inclusion of Azure PowerShell, which is traditionally Windows-centric, and the absence of explicit Linux command-line patterns or notes about cross-platform usage, indicate a bias towards Windows users and tools.
Recommendations
  • Add explicit Bash or shell examples for running the Azure CLI command, demonstrating usage in a Linux environment.
  • Clarify that Azure CLI is cross-platform and provide notes or examples for both Windows (CMD/PowerShell) and Linux (Bash/zsh) shells.
  • If PowerShell is mentioned, note that PowerShell Core is available on Linux and macOS, and provide usage examples for those platforms.
  • Include troubleshooting or environment setup notes for Linux users, such as installation instructions for Azure CLI and PowerShell Core on Linux.
  • Ensure parity in documentation by listing Linux/Bash examples before or alongside Windows/PowerShell examples.
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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools 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 historically Windows-centric) and the absence of explicit Linux shell examples (such as Bash) or references to Linux-native tools indicates a mild Windows bias. Additionally, PowerShell is presented as a primary tab, which may reinforce Windows-first patterns for users. There are no examples or instructions tailored specifically for Linux users, such as Bash scripting or Linux-specific command-line nuances.
Recommendations
  • Add explicit Bash shell examples for running Azure CLI queries on Linux.
  • Clarify that Azure CLI works cross-platform and provide sample commands for both Windows (CMD/PowerShell) and Linux (Bash).
  • If PowerShell is included, mention that PowerShell Core is available on Linux and macOS, and provide installation/use instructions for those platforms.
  • Consider reordering tabs so that cross-platform tools (Azure CLI) appear before Windows-centric tools (PowerShell).
  • Note any differences in output formatting or command behavior between platforms, if applicable.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-key-vault.md ...-graph/includes/samples-by-category/azure-key-vault.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
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 alongside CLI in every example. There are no explicit Linux shell (e.g., Bash) examples, nor is there mention of Linux-specific usage patterns or tools. The ordering of examples (CLI, then PowerShell, then Portal) is common, but the inclusion of PowerShell without any Linux shell equivalent can reinforce a Windows bias.
Recommendations
  • Add explicit Bash or shell script examples for Linux users, showing how to run Azure CLI queries in a Linux environment.
  • Clarify that Azure CLI commands work on both Windows and Linux, and provide notes or links for installing and using Azure CLI on Linux.
  • If PowerShell is included, consider also including examples using native Linux tools (e.g., curl, jq) where appropriate.
  • Review documentation ordering to ensure cross-platform tools are not overshadowed by Windows-centric ones.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-policy-guest-configuration.md ...amples-by-category/azure-policy-guest-configuration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows-specific guest configuration assignments (e.g., 'WindowsPendingReboot') are featured without Linux equivalents, and Windows-centric terms and patterns appear before or instead of Linux ones. Most examples and queries are either generic or Windows-focused, with only one explicit Linux example ('installed_application_linux'). There is a lack of parity in showing Linux guest configuration assignments, such as pending reboot or compliance checks for Linux machines.
Recommendations
  • Add equivalent Linux guest configuration assignment examples (e.g., 'LinuxPendingReboot') wherever Windows-specific ones are shown.
  • Ensure that both Windows and Linux assignment names are referenced side-by-side in queries and explanations.
  • Provide context or notes on how queries apply to both Windows and Linux machines, or clarify any platform-specific limitations.
  • Expand examples to include common Linux compliance scenarios, not just installed applications.
  • Review terminology and ordering to avoid Windows-first presentation; alternate or parallelize Windows and Linux references.
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-list-resources.md ...category/query/app-service-resources-list-resources.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
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 any Linux shell (bash) or scripting examples, as well as no mention of Linux-specific tools or patterns, indicates a mild Windows bias. There is no explicit Linux example or reference to Linux-specific usage patterns.
Recommendations
  • Add explicit bash or shell script examples for Linux users, demonstrating the same query using az graph query.
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux environments (e.g., installation, shell differences).
  • If mentioning PowerShell, note its cross-platform availability and provide examples for both Windows and Linux terminals.
  • Consider including troubleshooting or environment setup notes for Linux users, such as package dependencies or authentication differences.
GitHub Create Pull Request
← Previous Page 11 of 25 Next →