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 201-225 of 613 flagged pages
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation consistently provides Azure CLI and Azure PowerShell examples for all operations, but does not offer Linux-specific shell examples (e.g., Bash, scripting patterns) or mention Linux tools. Azure PowerShell is a Windows-centric tool and is presented alongside Azure CLI, but there is no parity for Linux-native scripting or automation approaches. Additionally, PowerShell examples are given equal prominence to CLI, which may suggest a Windows-first orientation, and there are no references to Linux-specific usage patterns or troubleshooting.
Recommendations
  • Add explicit Bash shell scripting examples for each operation, demonstrating how to use az graph query in Linux environments.
  • Clarify that Azure CLI is cross-platform and provide examples of piping CLI output to Linux tools (e.g., jq, grep, awk) for further processing.
  • Mention Linux-native automation approaches (e.g., cron jobs, shell scripts) for working with large data sets.
  • Consider referencing or linking to documentation on using Azure Resource Graph with Linux SDKs or REST API via curl.
  • Ensure that CLI examples are presented before PowerShell, or clearly indicate cross-platform applicability to avoid Windows-first perception.
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-09 00:34
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 on Linux) and the lack of explicit Linux shell (bash) or scripting examples indicates a mild Windows bias. There are no Linux-specific command-line examples (e.g., using curl, jq, or bash scripting), nor is there mention of Linux-native tools or patterns. The PowerShell example is given equal prominence to Azure CLI, but no Linux shell alternative is presented.
Recommendations
  • Add explicit bash or shell script examples for running Azure CLI queries on Linux.
  • Mention that Azure CLI is cross-platform and provide usage notes for Linux environments.
  • If PowerShell is included, clarify that PowerShell Core is available on Linux, or provide a Linux PowerShell example.
  • Consider including examples using Linux-native tools (e.g., piping Azure CLI output to jq for JSON parsing).
  • Ensure that documentation does not assume Windows as the default environment and highlights cross-platform compatibility.
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-09 00:34
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 PowerShell (a Windows-centric tool) is featured alongside Azure CLI in every example, with detailed PowerShell usage notes (e.g., ConvertTo-Json, variable handling) that are specific to Windows environments. Shell scripting examples for Azure CLI use Unix tools (awk, sed, tail), but there is no mention of Windows equivalents (e.g., PowerShell cmdlets or batch scripting), nor is there guidance for running CLI commands on Windows. The JSON output examples and resource properties are heavily focused on Windows VMs (e.g., WindowsServer image, osType: Windows, windowsConfiguration), with no Linux VM examples or properties shown.
Recommendations
  • Add Linux VM examples and properties (e.g., osType: Linux, imageReference for Ubuntu or CentOS) in JSON output and queries.
  • Include Azure CLI command usage on Windows (e.g., using PowerShell or cmd.exe), or provide equivalent PowerShell scripting for CLI examples.
  • Balance PowerShell-specific notes with Bash/Linux shell notes, such as handling JSON output or variables in Bash.
  • Explicitly mention cross-platform support for Azure CLI and PowerShell, and provide guidance for users on both Windows and Linux.
  • Where scripting is shown (e.g., file handling, text processing), provide both Bash (Linux/macOS) and PowerShell (Windows) approaches.
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-09 00:34
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 its treatment of shell-specific syntax. In the 'Escape characters' section, PowerShell is described in detail and given a code example, while Bash is mentioned but not exemplified, and Windows cmd is referenced without an example. No Linux-specific tools or usage patterns are discussed elsewhere, and there are no Linux CLI examples (such as Azure CLI or Bash scripting). The ordering of shell instructions places PowerShell last but provides more detail and a code sample, while Bash and cmd are treated more briefly. No Linux-centric workflows or tools are mentioned, and the documentation does not provide parity in examples for Linux users.
Recommendations
  • Provide explicit Bash and Azure CLI examples alongside PowerShell examples, especially in sections discussing shell-specific syntax.
  • Include Linux-centric usage patterns, such as running queries from Bash scripts or using Azure CLI on Linux.
  • Ensure that shell-specific instructions are presented with equal detail and code samples for both Windows (PowerShell/cmd) and Linux (Bash).
  • Add a section or note highlighting cross-platform compatibility and best practices for Linux users.
  • Where possible, avoid assuming PowerShell as the default shell and present instructions for both Windows and Linux environments in parallel.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-arc-enabled-servers.md ...ludes/samples-by-category/azure-arc-enabled-servers.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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, but does not include any Linux-specific shell examples (such as Bash or shell scripting). PowerShell examples are given equal prominence to CLI, and there is no mention of Linux-native tools or usage patterns. The documentation assumes users are either using PowerShell (Windows-centric) or the Azure CLI, but does not address Linux users directly or provide parity for Linux command-line environments.
Recommendations
  • Add explicit Bash/shell examples for each query, showing how to run az graph query commands in a Linux terminal.
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS environments (e.g., differences in quoting, escaping, or prerequisites).
  • Include troubleshooting or environment setup notes for Linux users, such as installing Azure CLI on Ubuntu or other distributions.
  • Avoid presenting PowerShell examples before CLI or Linux-native examples; consider listing CLI/Bash first to reduce Windows-first perception.
  • Mention that all queries can be run from Linux, macOS, and Windows, and provide links to relevant cross-platform documentation.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Most queries and examples focus on Windows-specific guest configuration assignments (e.g., 'WindowsPendingReboot') and do not provide equivalent Linux examples (such as 'LinuxPendingReboot'). Windows terminology and resource names are used exclusively or before Linux equivalents. There is a lack of parity in examples for Linux guest configuration scenarios, except for a single section ('installed_application_linux'). PowerShell is featured as a primary automation tool, which is traditionally associated with Windows environments.
Recommendations
  • Add equivalent Linux guest configuration assignment examples (e.g., 'LinuxPendingReboot') wherever Windows-specific queries are shown.
  • Ensure that both Windows and Linux resource names and scenarios are covered in all query examples, not just in one section.
  • When listing tools or automation options, clarify cross-platform support (e.g., Azure CLI and PowerShell are available on Linux, macOS, and Windows).
  • Consider providing Bash or shell script examples for Linux users alongside PowerShell.
  • Review terminology and ordering to avoid presenting Windows scenarios first or exclusively, and strive for equal representation of Linux and Windows use cases.
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
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Azure Portal. While Azure CLI is cross-platform, the PowerShell example is Windows-centric and is presented before any explicit Linux shell example. There are no bash or Linux shell-specific examples, nor is there mention of Linux-specific tooling or usage patterns. The documentation implicitly prioritizes Windows/PowerShell workflows and omits Linux-native command-line usage.
Recommendations
  • Add explicit bash/shell examples for running az graph query on Linux/macOS, including sample output redirection and parsing.
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS environments.
  • Consider reordering examples so that cross-platform tools (Azure CLI) are presented before Windows-centric tools (PowerShell).
  • Include troubleshooting or environment setup notes for Linux users, such as package installation or authentication differences.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-storage.md ...ce-graph/includes/samples-by-category/azure-storage.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and no explicit Linux shell (e.g., Bash) or scripting examples are provided. The PowerShell examples are given equal prominence to CLI, and there is no mention of Linux-specific tools, patterns, or considerations. There are no examples showing how to use these queries in a native Linux shell or with Linux-specific tools.
Recommendations
  • Add explicit Bash or shell script examples for running Azure CLI queries on Linux.
  • Clarify that Azure CLI commands work on both Windows and Linux, and provide any necessary notes about environment differences (e.g., quoting, escaping).
  • If relevant, mention alternative Linux-native tools or scripting approaches for interacting with Azure Resource Graph.
  • Consider reordering or grouping examples to avoid implying PowerShell is the primary or preferred method, or explicitly state cross-platform parity.
  • Add troubleshooting or environment setup notes for Linux users where differences may arise (e.g., authentication, shell compatibility).
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
High Priority View Details →
Scanned: 2026-01-09 00:34
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 each query, but PowerShell is highlighted as a primary scripting interface, which is strongly associated with Windows. There are no explicit Linux shell (bash, zsh) or scripting examples, nor is there mention of Linux-native tools or patterns. PowerShell is listed alongside CLI, but its presence and lack of Linux-specific alternatives or notes may signal a Windows bias. The documentation does not clarify cross-platform compatibility for PowerShell, nor does it mention Linux-specific usage or troubleshooting.
Recommendations
  • Add explicit bash/zsh shell examples for running Azure CLI commands, showing typical Linux usage patterns (e.g., piping, jq for JSON parsing).
  • Clarify that Azure CLI is fully cross-platform and provide installation or usage notes for Linux users.
  • If PowerShell is recommended, note that PowerShell Core is available on Linux and macOS, and provide examples or links for those platforms.
  • Consider including troubleshooting or environment setup notes for Linux users, especially regarding authentication and environment variables.
  • Balance the prominence of PowerShell by either providing equivalent Linux-native scripting examples or by making CLI the default/first example, with PowerShell as an alternative.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-virtual-machines.md ...includes/samples-by-category/azure-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Many queries and examples are generic and apply to Azure resources regardless of OS, but when OS-specific queries are shown, Windows Server examples are presented before Linux equivalents. Windows terminology (e.g., KB ID, update classifications like 'updateRollup', 'featurePack', 'servicePack') is used without Linux equivalents or explanations. PowerShell is given equal prominence to Azure CLI, but Linux-native shell examples (e.g., bash, zsh) are missing. There is a distinct separation of Windows and Linux update queries, but the Windows example appears first and is more detailed. No Linux-specific tools or patterns are mentioned, and the documentation does not address Linux-specific update types or classifications.
Recommendations
  • Alternate the order of Windows and Linux examples so Linux is not always second.
  • Provide Linux-specific terminology and update classifications (e.g., reference apt/yum/dnf package types, CVE IDs, etc.) alongside Windows terms.
  • Include Linux-native shell examples (bash, zsh) for CLI usage, especially for scripting and automation.
  • Add explanations or links for both Windows and Linux update mechanisms and patch types.
  • Ensure parity in detail and coverage between Windows and Linux queries, including troubleshooting and result interpretation.
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-09 00:34
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 traditionally Windows-centric, though now available cross-platform) and the absence of explicit Linux shell examples (such as bash or zsh) or references to Linux-native tools may indicate a mild Windows bias. Additionally, the PowerShell example is given equal prominence to the CLI, and there is no mention of Linux-specific usage patterns or troubleshooting.
Recommendations
  • Add explicit bash/zsh shell examples for running Azure CLI commands on Linux.
  • Clarify that Azure CLI is fully supported on Linux and macOS, and provide installation links for those platforms.
  • If PowerShell is mentioned, note its cross-platform availability and provide installation instructions for Linux/macOS.
  • Consider including troubleshooting notes or environment setup tips for Linux users.
  • Ensure that examples and instructions do not assume a Windows environment (e.g., avoid referencing Windows-only paths or conventions).
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-permissions-list.md ...horization-resources-role-definitions-permissions-list.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 associated with Windows environments) without mentioning Bash or other Linux-native scripting options, and the absence of explicit Linux shell examples, indicates a bias towards Windows tools and workflows. There is no example showing how to run the query using Bash or other Linux-native tools, and PowerShell is given equal prominence to the CLI.
Recommendations
  • Add explicit Bash shell examples for running the Azure CLI command to demonstrate Linux parity.
  • Clarify that Azure CLI commands work identically on Windows, Linux, and macOS.
  • If PowerShell is included, consider also including a Bash or shell script tab to balance cross-platform representation.
  • Mention that Azure PowerShell is available cross-platform (if true), or clarify its platform support.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/insight-resources-monitor-data-collection-rules.md ...ery/insight-resources-monitor-data-collection-rules.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 traditionally Windows-centric, though now available on Linux) and the absence of Linux shell-specific examples (such as Bash scripts or direct REST API calls via curl) indicate a bias towards Windows tooling. Additionally, PowerShell is given a dedicated tab, reinforcing its prominence. There are no explicit Linux-first or Linux-only examples, nor is there mention of Linux-native tools or shell patterns.
Recommendations
  • Add explicit Bash shell examples using az CLI to demonstrate Linux usage patterns.
  • Include REST API examples using curl or httpie for platform-neutral access.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide OS-specific notes where relevant.
  • Consider adding a tab for 'Linux Shell' or 'Bash' to balance the PowerShell tab.
  • If PowerShell is shown, note its cross-platform availability and provide installation instructions for Linux users.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/troubleshoot/general.md ...cles/governance/resource-graph/troubleshoot/general.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for batch querying subscriptions, referencing Windows-centric tools (PowerShell), and omitting equivalent Linux or cross-platform CLI examples (such as Azure CLI or Bash). The resolution steps for key scenarios focus on PowerShell usage, and do not mention or prioritize Linux-compatible methods.
Recommendations
  • Add equivalent Azure CLI (az) and Bash script examples for batch querying subscriptions, ensuring Linux users have clear guidance.
  • When referencing tools, mention both PowerShell and Azure CLI, and provide links to documentation for both.
  • Ensure that examples and instructions are presented in a cross-platform manner, or explicitly note platform-specific differences.
  • Consider listing Azure CLI examples before or alongside PowerShell to avoid 'windows_first' bias.
  • Audit other troubleshooting scenarios for similar bias and update with Linux-friendly guidance where missing.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/service-groups/manage-membership.md ...rticles/governance/service-groups/manage-membership.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell scripts and examples for managing Azure Service Group membership at scale, with no equivalent examples for Linux or cross-platform tools such as Azure CLI, Bash, or Python. The only automation script is written in PowerShell, and all command-line instructions and output are shown in a Windows/PowerShell context. There is no mention of Linux shell usage, nor are there alternative scripts or instructions for non-Windows environments.
Recommendations
  • Add equivalent Azure CLI and Bash examples for querying Resource Graph and deploying Service Group memberships.
  • Provide sample scripts in Python or other cross-platform languages for bulk membership management.
  • Include explicit instructions for running these tasks on Linux/macOS, such as using Azure CLI or REST API calls.
  • Where PowerShell is used, note how to adapt the script for PowerShell Core on Linux/macOS, or provide alternatives.
  • Ensure that all automation and scripting sections offer both Windows and Linux options, and avoid assuming a Windows environment by default.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/assign-built-in-policies.md ...chine-configuration/how-to/assign-built-in-policies.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page, while stating support for both Windows and Linux, provides a detailed example only for a Windows-specific policy (Audit Windows Time Zone). No Linux policy assignment example is shown, and the walkthrough focuses exclusively on Windows parameters and UI options. In the programmatic section, PowerShell is listed prominently alongside CLI and REST, but Linux-specific command-line examples (e.g., Bash, shell scripts) are not provided. The overall flow introduces Windows policies and examples before Linux equivalents, and does not demonstrate parity in guidance for Linux users.
Recommendations
  • Add a parallel example that walks through assigning a Linux-specific policy (e.g., Audit Linux machines for required applications), including screenshots and parameter explanations.
  • Ensure that Linux policies are mentioned with equal prominence and detail as Windows policies in the discovery and assignment sections.
  • Provide Linux-centric command-line examples (e.g., Bash scripts using Azure CLI) in the programmatic access section, and clarify which commands are cross-platform.
  • Explicitly note any differences in prerequisites or assignment steps for Linux machines.
  • Balance screenshots and UI walkthroughs to include Linux policy scenarios, not just Windows.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/create-blueprint-rest-api.md ...les/governance/blueprints/create-blueprint-rest-api.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 demonstrates a Windows bias by providing only PowerShell examples for REST API calls, recommending PowerShell as the primary tool, and omitting equivalent Linux/macOS command-line examples (such as curl or HTTPie). Windows tooling and patterns (PowerShell cmdlets, Azure Cloud Shell with PowerShell) are mentioned exclusively and before any cross-platform alternatives.
Recommendations
  • Add equivalent Linux/macOS command-line examples using curl, HTTPie, or similar tools for making REST API calls.
  • Present cross-platform tools (e.g., ARMClient, Azure CLI) before or alongside PowerShell, and clarify their OS compatibility.
  • Include explicit instructions for authentication and header generation using non-Windows tools (e.g., Azure CLI with curl).
  • Ensure that all code samples are available in both PowerShell and bash/shell script formats.
  • Mention that Azure Cloud Shell supports both Bash and PowerShell, and provide examples for both.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/view-compliance.md ...rnance/machine-configuration/how-to/view-compliance.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 through its tooling references and example ordering. The only OS-specific tool mentioned by name is the PowerShell cmdlet (Get-AzGuestConfigurationAssignment), which is listed in the API/programmatic access table without an equivalent Linux shell example. While CLI and REST API options are referenced (which are cross-platform), the explicit mention of PowerShell and lack of Linux shell (bash) or scripting examples suggests a preference for Windows environments. Additionally, the Power BI export is highlighted, which is primarily a Windows tool, and appears before mentioning other cross-platform dashboarding options.
Recommendations
  • Add explicit Linux shell (bash) examples for querying compliance data, such as using az CLI commands in bash scripts.
  • Include references to Linux-native tools for reporting and dashboarding, such as integrating with Grafana or Kibana, alongside Power BI.
  • Mention cross-platform scripting approaches (e.g., Python, bash) for programmatic access, not just PowerShell.
  • Where PowerShell cmdlets are referenced, provide equivalent Linux command-line or scripting alternatives.
  • Clarify that all CLI and REST API examples are cross-platform, and provide sample usage for both Windows and Linux environments.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/develop-custom-package/5-access-package.md ...tion/how-to/develop-custom-package/5-access-package.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively provides PowerShell examples and references Azure PowerShell cmdlets for generating SAS tokens, with no equivalent examples or instructions for Linux users (e.g., Bash, Azure CLI, or REST API). The use of PowerShell and Windows-centric tooling suggests a bias toward Windows environments, potentially making it less accessible for users on Linux or macOS platforms.
Recommendations
  • Add equivalent examples using Azure CLI (az storage blob generate-sas) for Linux/macOS users.
  • Include Bash shell script snippets for generating SAS tokens and accessing blobs.
  • Reference REST API methods for cross-platform access.
  • Explicitly mention that the steps can be performed on Linux/macOS and provide links to relevant cross-platform documentation.
  • Balance the order of examples so that Windows and Linux approaches are presented together or Linux is not always secondary.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/troubleshoot/general.md ...ain/articles/governance/policy/troubleshoot/general.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 in several ways. PowerShell is the only CLI tool shown in code examples, with no equivalent Bash, Azure CLI, or Linux shell examples. Windows-specific tools and patterns (such as PowerShell and references to Windows machines) are mentioned without Linux alternatives. In scenarios where command-line interaction is required, Windows/PowerShell is presented first or exclusively. There are no explicit Linux or cross-platform command examples for key troubleshooting steps, such as duplicating policy definitions or triggering evaluation scans.
Recommendations
  • Add equivalent Azure CLI and Bash examples alongside PowerShell commands for all scenarios involving command-line interaction.
  • Explicitly mention Linux and macOS compatibility for SDKs, tools, and troubleshooting steps.
  • Where Windows-specific tools are referenced (e.g., PowerShell), provide links or guidance for Linux users (e.g., using Azure CLI, Bash, or Python SDK).
  • Ensure that troubleshooting steps and code samples are presented in a cross-platform manner, with Linux examples given equal prominence.
  • Review references to Windows machines and clarify when instructions apply to all OS types or provide Linux-specific guidance where relevant.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-arc-enabled-servers.md ...ludes/samples-by-category/azure-arc-enabled-servers.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, but omits explicit Linux shell (bash) examples. PowerShell is given equal prominence to Azure CLI, despite being Windows-centric. There are no references to Linux-specific tools, nor are Linux command-line patterns (e.g., bash, curl, jq) shown. The ordering of tabs places Azure CLI first, but the lack of Linux-specific examples or notes may disadvantage Linux users.
Recommendations
  • Add explicit bash/Linux shell examples for each query, demonstrating usage with az graph query and common Linux tools (e.g., piping output to jq for parsing).
  • Include notes on cross-platform compatibility for the Azure CLI commands, clarifying any differences in usage between Windows and Linux.
  • Consider adding a 'Linux' or 'Bash' tab alongside 'Azure CLI' and 'Azure PowerShell' to highlight Linux parity.
  • Where PowerShell is referenced, clarify that it is primarily for Windows users and suggest Linux alternatives.
  • Review documentation for references to Windows-only tools or patterns and provide Linux equivalents where appropriate.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/changes/get-resource-changes.md ...ernance/resource-graph/changes/get-resource-changes.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 Windows bias by consistently presenting PowerShell examples alongside Azure CLI and Portal, with PowerShell (a Windows-centric tool) given equal prominence to CLI. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments. The prerequisites and instructions reference PowerShell modules and cmdlets without clarifying cross-platform compatibility or providing Linux/Bash alternatives. The CLI examples are generic and do not address Linux-specific nuances, such as authentication or environment setup. No Linux tools or patterns are discussed, and PowerShell is presented as a primary method for querying, which may mislead users into thinking it's required or preferred, especially for Windows users.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands, showing usage in typical Linux environments (e.g., authentication, environment variables, piping output).
  • Clarify that Azure CLI is cross-platform and can be used in Linux, macOS, and Windows, while PowerShell is available on all platforms but is traditionally Windows-centric.
  • Include notes or sections on installing and using Azure CLI in Linux distributions, including troubleshooting common Linux-specific issues.
  • Where PowerShell is referenced, add equivalent Bash or shell script snippets for Linux users.
  • Avoid presenting PowerShell as a default or primary method; instead, lead with CLI or provide equal visibility to both CLI and PowerShell, with clear platform guidance.
  • Mention that Cloud Shell supports both Bash and PowerShell, and show how to select the shell.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-container-registry.md ...cludes/samples-by-category/azure-container-registry.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 lacks explicit Linux shell (bash) examples. PowerShell is featured as a primary command-line interface, which is predominantly used on Windows. There is no mention of Linux-specific tools or shell usage, and the PowerShell example may not be directly usable on Linux systems without installing PowerShell Core. The documentation does not clarify cross-platform compatibility for the CLI or PowerShell commands.
Recommendations
  • Add explicit bash shell examples for Linux users, demonstrating how to run the Azure CLI query from a Linux terminal.
  • Clarify that Azure CLI is cross-platform and provide installation or usage notes for Linux and macOS.
  • Indicate whether the PowerShell example requires PowerShell Core on Linux/macOS, and provide installation instructions if relevant.
  • Mention any differences or considerations for running these queries on Linux versus Windows environments.
  • 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/azure-storage.md ...ce-graph/includes/samples-by-category/azure-storage.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, but does not include any explicit Linux shell (bash, zsh, etc.) or scripting examples. Azure PowerShell is a Windows-centric tool, and its inclusion alongside CLI in every example reinforces a Windows bias. The ordering of examples (CLI first, then PowerShell, then Portal) is common, but the lack of Linux-specific instructions or notes (such as bash scripting, environment differences, or cross-platform considerations) means Linux users may not see their workflows represented.
Recommendations
  • Add explicit bash/zsh shell examples for running Azure CLI commands, including notes about authentication and environment setup on Linux.
  • Include information about installing and using Azure CLI on Linux, and clarify that all CLI examples are cross-platform.
  • Where PowerShell examples are given, clarify that PowerShell Core is available on Linux and macOS, or provide bash alternatives.
  • Add troubleshooting notes for common Linux issues (e.g., quoting, environment variables, authentication differences).
  • Consider including a 'Platform compatibility' note at the top of the page, specifying which tools are available on which OSes.
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
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, but does not include any explicit Linux shell (bash/zsh) examples or mention Linux-specific usage patterns. PowerShell examples are given equal prominence to CLI, and there is no discussion of cross-platform differences or considerations. The absence of Linux shell examples or notes on platform compatibility may unintentionally favor Windows users.
Recommendations
  • Add explicit bash/zsh examples for each query, demonstrating usage in Linux shells.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Include notes on any differences or considerations when running commands in Linux vs. Windows environments (e.g., quoting, environment variables).
  • Consider reordering or grouping examples to avoid implicit prioritization of Windows tools (e.g., present CLI before PowerShell, or clarify cross-platform parity).
  • Mention that PowerShell Core is available on Linux and macOS, if relevant, and provide usage guidance.
GitHub Create Pull Request
← Previous Page 9 of 25 Next →