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 301-325 of 613 flagged pages
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/develop-custom-package/2-create-package.md
...tion/how-to/develop-custom-package/2-create-package.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows and PowerShell bias. All code examples use PowerShell, including for Linux scenarios, and Windows-specific paths and outputs are shown by default. Windows configuration steps and tools are described first and in more detail, while Linux-specific guidance is minimal or deferred to external articles. There are no examples using native Linux tools or shell environments, and the packaging and inspection steps assume Windows conventions.
Recommendations
- Provide equivalent examples using native Linux shell commands (e.g., Bash) for compiling, renaming, and packaging configuration files.
- Show Linux file paths and outputs alongside or instead of Windows paths (e.g., use /home/user/dsc/MyConfig instead of C:\dsc\MyConfig).
- Include instructions for using Linux-native tools (e.g., mv, zip/unzip, du) for tasks like renaming files, creating archives, and checking file sizes.
- Balance the order of presentation so that Linux and Windows steps/examples are given equal prominence, or alternate which platform is described first.
- Clarify which steps are platform-agnostic and which are platform-specific, and provide clear, parallel guidance for both environments.
- Consider including a section or appendix specifically for Linux users, summarizing the end-to-end workflow using Linux-native tools and conventions.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for making REST API calls, recommending PowerShell as the tool of choice, and omitting equivalent Linux/macOS command-line examples (such as curl or HTTPie). The guidance assumes familiarity with PowerShell cmdlets and Windows-centric tooling, with no mention of cross-platform alternatives or how to perform the same tasks on Linux or macOS.
Recommendations
- Add equivalent examples using curl or HTTPie for making REST API calls, which are available on Linux, macOS, and Windows.
- Mention cross-platform tools (e.g., Azure CLI, REST clients like Postman, or ARMClient) alongside PowerShell, and provide sample usage.
- Rephrase guidance to avoid recommending PowerShell as the default or only tool, instead offering a choice of tools for different platforms.
- Include notes or sections specifically for Linux/macOS users, ensuring parity in authentication and REST invocation instructions.
- Where PowerShell-specific cmdlets are referenced (e.g., ConvertFrom-Json), provide equivalent commands for bash/jq or other common Linux utilities.
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 →
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- or macOS-specific shell examples (e.g., Bash). The PowerShell example is present, which is primarily associated with Windows environments, and there is no mention of Linux-native tools or shell usage. This may make Linux users feel less directly supported, especially since PowerShell is highlighted as a primary scripting interface.
Recommendations
- Add a Bash shell example for running the Azure CLI command, demonstrating usage in a typical Linux environment.
- Explicitly mention that the Azure CLI example works cross-platform (Windows, Linux, macOS) and provide any OS-specific notes if needed.
- If PowerShell is included, consider also including a Bash or zsh example to ensure parity for Linux/macOS users.
- Clarify in the documentation that PowerShell Core is available cross-platform, if relevant, to reduce the perception of Windows-only bias.
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 →
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 equally alongside CLI. There are no explicit Linux shell (bash) or scripting examples, and no mention of Linux-specific tooling or workflows. The use of PowerShell as a primary example and the absence of Linux-native command-line patterns (e.g., bash, curl, jq) indicate a Windows bias.
Recommendations
- Add Linux shell (bash) examples for each scenario, using tools like curl for REST API calls and jq for JSON processing.
- Clearly indicate cross-platform compatibility for Azure CLI and PowerShell, and provide notes on installation or usage differences on Linux/macOS.
- Where PowerShell is shown, also provide equivalent bash or shell script snippets to ensure Linux users are equally supported.
- Mention Linux-native tools and workflows (e.g., piping Azure CLI output to jq) when discussing result formatting and processing.
- Consider the order of examples: alternate or lead with cross-platform (CLI/bash) examples before PowerShell to avoid Windows-first perception.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways. PowerShell examples are given in detail and before Azure CLI examples, with file paths and usage patterns that are Windows-specific (e.g., 'c:\policies\coolAccessTier.json'). There are no explicit Linux or macOS command-line examples, nor are there notes about cross-platform differences or alternative shells. The documentation assumes familiarity with Windows tools and conventions, potentially making it less accessible to Linux users.
Recommendations
- Provide Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
- Include Linux/macOS file path examples (e.g., '/home/user/policies/coolAccessTier.json') wherever file paths are shown.
- Add notes clarifying that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and highlight any OS-specific considerations.
- Avoid using Windows-specific terminology (like 'right-click') without also mentioning keyboard or alternative methods for other platforms.
- Explicitly mention that the Azure portal and REST API are OS-agnostic, and provide guidance for users on non-Windows systems.
- Where possible, provide Bash shell equivalents for PowerShell commands, especially for scripting scenarios.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/networking.md
...ource-graph/includes/samples-by-category/networking.md
High Priority
View Details →
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 always presented alongside the CLI. There are no explicit Linux shell (e.g., Bash) or scripting examples, nor is there guidance for Linux-specific environments. The documentation does not clarify shell quoting/escaping differences, and PowerShell is given equal prominence to CLI, which may suggest a Windows bias.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash, zsh).
- Add notes or examples for common Linux shell quoting/escaping issues, especially when embedding Kusto queries.
- If PowerShell examples are provided, consider also providing Bash or other Linux shell script equivalents for parity.
- Clarify in introductory sections that Azure CLI is the recommended cross-platform tool, and PowerShell is optional for Windows users.
- Where relevant, mention installation or usage differences for Linux users (e.g., package managers, environment variables).
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 →
Detected Bias Types
Powershell Heavy
Windows First
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 historically Windows-centric, though now available cross-platform) and the absence of explicit Linux/macOS shell or scripting examples (such as Bash) indicate a mild Windows bias. Additionally, PowerShell examples are always present and given equal prominence to CLI, and there are no Linux-specific notes or examples, such as using Bash scripting or mentioning shell environments. There are no references to Windows-only tools, but the documentation does not address Linux users directly or provide parity in scripting approaches.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users, especially for common scenarios such as running az graph query and processing output.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide sample shell usage (e.g., piping output to jq or grep).
- If PowerShell is mentioned, note that PowerShell Core is cross-platform, or provide a Bash alternative where appropriate.
- Consider including a 'Platform compatibility' note to reassure users that the instructions are not Windows-specific.
- If scripting is discussed, show both PowerShell and Bash script blocks for parity.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates some Windows bias, particularly in the 'Escape characters' section, where PowerShell (a Windows-centric shell) is given a dedicated example and is mentioned before Bash. The Bash example is present, but the ordering and explicit mention of PowerShell and cmd (both Windows shells) before Bash suggests a Windows-first approach. There are no CLI (az), Linux shell, or cross-platform examples for running queries, and no mention of Linux-specific tools or workflows elsewhere in the document.
Recommendations
- Reorder shell-specific instructions to list Bash (Linux/macOS) before PowerShell and cmd, or present all at the same time in a neutral order.
- Include examples using the Azure CLI (az) for running Resource Graph queries from Linux/macOS terminals.
- Add explicit Linux/macOS usage notes or examples where relevant, especially in sections discussing shell-specific syntax or escaping.
- Where PowerShell is mentioned, clarify that cross-platform PowerShell Core is available, or provide both Windows PowerShell and Linux/macOS PowerShell Core examples.
- Audit other sections for implicit Windows assumptions and ensure parity in tooling and workflow guidance for Linux users.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for all queries, but there is a notable bias toward Windows/PowerShell patterns. PowerShell examples are always present and sometimes explained in more detail (e.g., use of ConvertTo-Json and depth), and Windows-centric tools and patterns (PowerShell variables, cmdlets) are used throughout. In the multi-step public IP address example, the Azure CLI workflow uses Unix tools (awk, sed, tail), but there is no explicit mention of Linux shell environments or guidance for Linux users. The JSON output examples use Windows-centric values (e.g., WindowsServer images, osType: Windows), and there is no mention of Linux VMs or their properties.
Recommendations
- Add explicit Linux/Unix shell examples (e.g., bash, zsh) for workflows involving Azure CLI, especially for variable handling and file manipulation.
- Include examples or notes for querying Linux virtual machines (e.g., using 'osType: Linux', 'publisher: Canonical', etc.) in JSON and queries.
- Balance explanations between PowerShell and CLI, ensuring that CLI examples are as detailed and accessible as PowerShell ones.
- When discussing output formatting (e.g., ConvertTo-Json in PowerShell), provide equivalent CLI/jq or other Linux-friendly alternatives.
- Avoid Windows-centric sample data where possible, or provide parallel Linux examples (e.g., show both Windows and Linux VM JSON).
- Clarify in notes or callouts when CLI examples assume a Unix-like shell, and provide Windows CMD or PowerShell equivalents if needed.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. In most sections, examples are provided for Azure CLI, Azure PowerShell, and the Azure Portal, but there is a consistent presence of PowerShell (a Windows-centric tool) as a primary example. In OS update queries, Windows and general OS queries are presented before Linux-specific queries, and the Linux example appears later in the document. There are no Linux-native command-line examples (e.g., Bash scripts or Linux-specific tooling) outside of the Azure CLI, and terminology and patterns (such as PowerShell) are more familiar to Windows users. The documentation does not provide parity in Linux-native usage or highlight Linux-specific considerations except in one dedicated Linux section.
Recommendations
- Provide Linux-native command-line examples (e.g., Bash, shell scripts) alongside PowerShell, especially for scenarios where users may interact with Azure from Linux environments.
- Ensure that Linux-specific queries and examples are given equal prominence and are not grouped only at the end or in a separate section.
- Where PowerShell is used, clarify that it is cross-platform or provide explicit Linux installation/use instructions.
- Highlight any differences in resource properties or behaviors between Windows and Linux VMs in the documentation.
- Consider adding a table or section summarizing OS-specific queries for both Windows and Linux at the top of the page for quick reference.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page consistently provides examples using Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. There are no explicit Linux shell (bash) or cross-platform scripting examples, and PowerShell examples are always present alongside CLI, reinforcing a Windows-first approach. No mention is made of Linux-specific tools, patterns, or considerations, and there are no bash or shell script examples for Linux users.
Recommendations
- Add bash or shell script examples for Linux users alongside Azure CLI and PowerShell examples.
- Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- Where PowerShell is shown, consider also showing equivalent bash scripting for common automation scenarios.
- Explicitly mention that Azure CLI is available on Linux and provide installation or usage links for Linux users.
- If discussing object formatting or output manipulation, provide Linux-native alternatives (e.g., jq for JSON processing) in addition to PowerShell's ConvertTo-Json.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/samples/ukofficial-uknhs.md
...articles/governance/policy/samples/ukofficial-uknhs.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. In several policy tables, Windows-specific policies (e.g., 'Windows machines should be configured to use secure communication protocols') are listed without equivalent Linux examples, or Windows policies are listed before Linux ones. There are also more granular and numerous password and security policies for Windows than for Linux, and some controls reference Windows tools or settings without Linux parity. Linux is represented, but not as comprehensively or as early in the lists.
Recommendations
- Ensure that for every Windows-specific policy or example, a Linux equivalent is provided where applicable, and vice versa.
- Present Linux and Windows policies/examples in parallel or grouped together, rather than listing all Windows items first.
- Expand Linux coverage to match the granularity of Windows controls (e.g., password complexity, password age, etc.).
- Avoid referencing Windows tools or settings (such as Group Policy or Windows-specific password policies) without also providing Linux alternatives (e.g., PAM, passwd, chage).
- Where a policy is only applicable to one OS, clearly state this and explain why, to avoid the perception of bias.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is the only CLI example provided for duplicating policy definitions, with no Bash, Azure CLI, or cross-platform alternatives. References to 'Azure PowerShell' for on-demand evaluation scans are made repeatedly, but no equivalent Azure CLI or REST examples are shown. The documentation assumes the use of Windows-centric tools and patterns (such as PowerShell and Visual Studio Code) and does not provide parity for Linux or macOS users. This may hinder users on non-Windows platforms from following the troubleshooting steps effectively.
Recommendations
- For every PowerShell example, provide an equivalent Azure CLI (az) or Bash example, especially for common tasks like duplicating policy definitions or triggering evaluation scans.
- When referencing 'Azure PowerShell or the REST API', explicitly include Azure CLI commands and examples, or link to relevant cross-platform documentation.
- Mention cross-platform editors (such as VS Code, which is cross-platform) but clarify that the Azure Policy extension works on all supported OSes.
- Audit all troubleshooting steps to ensure that Linux/macOS users are not excluded, and add notes or examples where platform-specific differences exist.
- Where possible, use generic REST API calls or platform-neutral scripting in examples, or provide both PowerShell and Bash/Azure CLI snippets side by side.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for discovering policy aliases, but it lists Azure PowerShell after Azure CLI and does not provide any explicit Linux-specific guidance or examples. The use of PowerShell is emphasized, and there are no references to Linux shells or tools, nor is there any mention of platform differences in command usage. The document assumes the reader is comfortable with PowerShell and the Azure Portal, both of which are more familiar to Windows users. There is also no mention of Bash, shell scripting, or Linux-specific environments, and the clean-up instructions are portal-centric, omitting CLI-based deletion steps.
Recommendations
- Include explicit Bash/Linux shell examples alongside PowerShell and Azure CLI, especially for common tasks like discovering aliases or managing policies.
- Clarify that Azure CLI commands work cross-platform (Windows, macOS, Linux) and provide any necessary notes about differences in command syntax or authentication (e.g., az login in Bash).
- Add instructions for deleting policy definitions and assignments using Azure CLI commands, not just via the Azure Portal UI.
- When listing tools or command-line options, avoid always listing PowerShell after CLI, and consider grouping by platform or providing parallel examples.
- Mention that VS Code and Azure CLI are cross-platform, and provide links or notes for Linux/macOS installation if relevant.
- Where possible, provide guidance for users working in Linux environments, such as using Azure Cloud Shell (Bash) or local Bash terminals.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: PowerShell examples are provided before Azure CLI examples, and the PowerShell examples use Windows-style file paths (e.g., 'c:\policies\coolAccessTier.json') without Linux alternatives. There is no mention of Linux-specific shell usage or file path conventions, and no explicit Bash or Linux terminal examples are given. The documentation assumes familiarity with Windows tools and patterns, which may hinder Linux users.
Recommendations
- Provide Azure CLI and PowerShell examples side-by-side or alternate their order to avoid always presenting PowerShell (Windows) first.
- Include Linux/Bash-specific examples, especially for file paths (e.g., use '/home/user/policies/coolAccessTier.json' alongside 'c:\policies\coolAccessTier.json').
- Explicitly mention that Azure CLI works cross-platform and show usage in a Bash shell or terminal.
- Where file paths are shown, provide both Windows and Linux/Mac formats.
- Reference Linux and MacOS environments in prerequisites and tool installation steps.
- Add notes or callouts for any platform-specific behaviors or requirements.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed instructions for using the Azure Portal and PowerShell (with Azure PowerShell cmdlets) to add user assigned identities to virtual machines. There are no examples or instructions for performing these tasks using cross-platform tools such as Azure CLI, nor are there any references to Linux shell environments or scripts. The PowerShell section is extensive and assumes the use of PowerShell, which is more commonly associated with Windows environments, and the documentation does not mention or demonstrate Linux-native workflows.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell Core is available on Linux and macOS if PowerShell must be used, and provide installation guidance or links.
- Include bash or shell script examples where appropriate, especially for file creation and command execution.
- Ensure that any references to tools or commands are balanced, presenting Azure CLI or REST API options alongside PowerShell.
- Review the documentation for terminology or instructions that assume a Windows environment and generalize them for cross-platform audiences.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/concepts/guidance-for-throttled-requests.md
...urce-graph/concepts/guidance-for-throttled-requests.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page provides only C# code examples and references to the Azure Resource Graph SDK, which is most commonly used in Windows/.NET environments. There are no examples or guidance for Linux-native tools, scripting languages (such as Bash or Python), or cross-platform command-line interfaces like Azure CLI. There is also no mention of PowerShell, but the heavy reliance on C# and .NET patterns suggests a Windows-centric approach.
Recommendations
- Add equivalent examples using Azure CLI (az graph query) to demonstrate how to handle throttling, grouping, and pagination from the command line, which is widely used on Linux.
- Provide Python SDK examples, as Python is a popular cross-platform scripting language for automation on both Linux and Windows.
- Include Bash scripting examples for staggered and parallel queries using curl or az CLI, showing how to parse throttling headers and implement backoff logic.
- Explicitly mention that the guidance and APIs are cross-platform, and provide links or references to SDKs and tools for Linux users.
- If PowerShell is relevant, provide PowerShell Core (cross-platform) examples, not just Windows PowerShell.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page generally avoids platform-specific bias in most sections, focusing on the Kusto Query Language and Azure Resource Graph concepts. However, in the 'Escape characters' section, Windows shells (cmd and PowerShell) are mentioned before Bash, and PowerShell-specific escaping is detailed with an example, which may indicate a subtle 'windows_first' and 'powershell_heavy' bias. There is also a lack of parity in the depth of examples for Linux shells compared to PowerShell. No Linux-specific tools or workflows are referenced, and there are no CLI (az) or cross-platform scripting examples provided.
Recommendations
- Present Bash (Linux/macOS) examples before or alongside Windows (cmd/PowerShell) examples to avoid 'windows_first' bias.
- Provide equally detailed examples for Bash and other Linux shells as are given for PowerShell.
- Include cross-platform CLI (az) examples where relevant, especially for query execution.
- Explicitly mention that the Resource Graph and KQL are platform-agnostic, and provide guidance for both Windows and Linux users.
- Where shell-specific behavior is discussed, ensure all major platforms (Linux, macOS, Windows) are covered with equal depth and clarity.
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 →
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, though now available cross-platform) and the absence of explicit Linux shell (bash) examples or notes about Linux usage may indicate a subtle Windows bias. Additionally, the PowerShell example is given equal prominence to the CLI, and there are no Linux-specific instructions or troubleshooting notes.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide a bash shell example if usage differs.
- Clarify that PowerShell Core is cross-platform, or provide a bash/zsh example for Linux users.
- Add a section or note for Linux users, highlighting any differences or confirming parity.
- Consider including troubleshooting tips or environment setup notes for Linux environments.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by listing PowerShell before Bash in the prerequisites and example tabs, recommending Visual Studio Code (a Microsoft tool) as the terminal environment, and referencing PowerShell-specific syntax and escape characters in more detail than Bash. The use of 'Bash shell like Git Bash' also suggests a Windows-centric perspective, as Git Bash is primarily used to provide Bash on Windows.
Recommendations
- Present Bash and PowerShell examples in parallel or list Bash first to avoid implying Windows is the primary platform.
- In prerequisites, mention native Linux/macOS terminals (e.g., 'Bash shell (Linux/macOS Terminal or Windows Git Bash)') and not just Git Bash, which is Windows-specific.
- Offer alternative editors/terminals such as GNOME Terminal, Konsole, or Terminal.app, and suggest VS Code as one option rather than the default.
- Balance the detail in shell-specific notes (e.g., explain both Bash and PowerShell escaping equally).
- Explicitly mention Linux/macOS as supported environments in the introduction and prerequisites.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all queries, but it demonstrates a subtle Windows bias. PowerShell examples are always present and sometimes described in more detail (e.g., explanation of ConvertTo-Json and object depth). The PowerShell examples use Windows-specific scripting patterns and variable handling. In the multi-step public IP address example, the Azure CLI solution uses Unix tools (awk, sed, tail), but there is no explicit mention of Linux or cross-platform compatibility, nor any Windows Command Prompt or PowerShell equivalents for those CLI steps. The JSON output examples are based on Windows VMs (e.g., osType: Windows, WindowsServer images), and there is no mention of Linux VM properties or images. There are no explicit Linux shell (bash) or cross-platform scripting examples, and the documentation assumes familiarity with Windows-centric tools and patterns.
Recommendations
- Add Linux/Unix shell (bash) examples for scripting steps, especially where Azure CLI is used with Unix tools (awk, sed, tail).
- Include Windows Command Prompt or PowerShell equivalents for Azure CLI scripting steps to ensure parity.
- Provide examples and JSON output for both Windows and Linux virtual machines (e.g., osType: Linux, imageReference for Ubuntu or CentOS).
- Explicitly mention cross-platform compatibility of Azure CLI and how to adapt scripts for different environments.
- Balance explanations and notes between Azure CLI and PowerShell, ensuring neither is favored in depth or detail.
- Where possible, use cross-platform scripting constructs or highlight differences for users on Windows, Linux, and macOS.
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
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal for each scenario. Azure PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) is standard for Microsoft docs. However, there are no explicit Linux shell (bash) examples, and PowerShell is always given as a primary automation example. There are no references to Linux-specific tools or shell scripting, and PowerShell is presented on equal footing with CLI, which may suggest a Windows bias. Additionally, PowerShell examples are always present, but there are no bash or Linux-native command examples.
Recommendations
- Add explicit bash or shell script examples for each scenario to demonstrate Linux parity.
- Clarify in the documentation that Azure CLI commands work identically on Windows, Linux, and macOS, and provide sample shell invocations (e.g., bash, zsh).
- Consider including notes or tabs for Linux users, such as 'Bash (Linux/macOS)' alongside 'Azure CLI' and 'Azure PowerShell'.
- If PowerShell is included, clarify that PowerShell Core is cross-platform, or otherwise indicate when a command is Windows-only.
- Highlight any differences or prerequisites for running these commands on Linux (e.g., installation steps for Azure CLI or PowerShell Core on Linux).
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 →
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 (bash) examples or Linux-specific guidance may indicate a mild Windows bias. The PowerShell example is given equal prominence to the CLI, and there is no mention of Linux-native tools or shell scripting patterns. There is also no explicit confirmation that all examples work identically on Linux, nor are there troubleshooting notes for Linux users.
Recommendations
- Add explicit bash/zsh shell examples for Linux users, demonstrating the same query using az graph query in a Linux terminal.
- Clarify that the Azure CLI example works identically on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
- If PowerShell is included, note that PowerShell Core is cross-platform and provide installation or usage notes for Linux.
- Consider adding troubleshooting tips or environment notes for Linux users (e.g., authentication, output formatting).
- Ensure that documentation sections and examples do not implicitly prioritize Windows tools or workflows over Linux equivalents.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a mild Windows bias. Most queries and examples are generic and cross-platform (using Azure CLI, PowerShell, and Portal), but specific Windows-centric patterns are present. For example, the 'List machines and status of pending reboot' section only references 'WindowsPendingReboot' with no Linux equivalent, and there is no mention of a Linux reboot status policy. Additionally, Windows-specific resource names are used without Linux parity in some sections, and Windows is often mentioned before Linux. There are no explicit Linux guest configuration examples for reboot status or non-compliance reasons, except for a single 'installed_application_linux' example.
Recommendations
- Add Linux equivalents for all Windows-specific queries, such as a 'LinuxPendingReboot' example if available.
- Ensure that when referencing guest configuration assignments, both Windows and Linux resource names and scenarios are included side by side.
- Where possible, provide Linux-focused examples for compliance and non-compliance queries, not just for installed applications.
- Review the ordering of examples and resource names to avoid always listing Windows first.
- Explicitly mention if certain features (like pending reboot detection) are not available for Linux, to clarify platform support.
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 →
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 most commonly associated with Windows environments) and the lack of explicit Linux shell (bash) examples or mention of Linux-specific tooling introduces a subtle Windows bias. Furthermore, the PowerShell example is given equal prominence to the CLI, and there is no explicit indication that all commands are tested or work identically on Linux. There are no bash or Linux-native command examples, and PowerShell is still often perceived as a Windows-first tool.
Recommendations
- Add explicit bash or Linux shell examples for running the Azure CLI command, demonstrating usage in a Linux terminal.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide any necessary notes about cross-platform differences if they exist.
- If PowerShell Core (cross-platform) is supported, specify this, or otherwise clarify the Windows-centric nature of the PowerShell example.
- Consider reordering the examples to present the Azure CLI (the most cross-platform tool) first, followed by PowerShell and then the Portal.
- Explicitly mention platform compatibility in the documentation introduction or in each example section.