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 51-75 of 613 flagged pages
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for exporting Azure Policy resources, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and its example is more complex. There is no mention of Linux-specific patterns, nor are there examples using native Linux tools (e.g., bash scripting, jq). The documentation references PowerShell cmdlets and patterns without clarifying cross-platform compatibility, potentially implying a Windows-first approach.
Recommendations
- Explicitly state that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
- Provide Linux-native examples, such as using bash and jq to process the JSON output from Azure CLI.
- Clarify that Azure PowerShell is available on Linux and macOS, or provide installation guidance for non-Windows platforms.
- Include a section or note highlighting Linux workflows for exporting and manipulating policy resources.
- Balance example complexity: ensure CLI and PowerShell examples are equally detailed, or provide advanced examples for both.
Create Pull Request
Governance
Azure Automanage Best Practices to Azure Policy migration planning
...olicy/how-to/migrate-from-automanage-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools and features (such as Windows Admin Center and Antimalware extensions) are described in detail, often before mentioning Linux equivalents. Examples and configuration steps frequently reference Windows VMs first, with Linux coverage sometimes present but less detailed. Some sections (e.g., Antimalware, Windows Admin Center) focus exclusively on Windows, with no Linux alternatives or examples provided. There is a lack of parity in example depth and tool coverage for Linux systems.
Recommendations
- Ensure that all feature descriptions and configuration steps include Linux-specific guidance and examples where applicable.
- When listing policies or extensions, present Windows and Linux options together, or alternate which is mentioned first.
- Add equivalent Linux management tools or alternatives (e.g., Cockpit, SSH-based management) where Windows Admin Center is referenced.
- Provide detailed Linux examples for agent installation, policy assignment, and extension configuration, matching the depth given for Windows.
- Explicitly state when a feature is Windows-only, and suggest Linux alternatives or workarounds if available.
- Review all referenced links to ensure Linux documentation is equally represented and accessible.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for command-line operations, but PowerShell coverage is more extensive and detailed, including advanced usage (background jobs, object inspection) and user lookup via Azure AD. PowerShell examples and explanations are often given after CLI, but with more depth and Windows-centric tooling (e.g., Visual Studio Code extension, PowerShell jobs). There are no explicit Linux shell (bash) examples, and the CLI examples do not mention Linux-specific usage or considerations. The documentation assumes familiarity with PowerShell and Windows tools, which may disadvantage Linux users.
Recommendations
- Add bash shell examples for REST API calls and Azure CLI usage, demonstrating usage in typical Linux environments.
- Balance the depth of Azure CLI and PowerShell sections, including advanced CLI usage (e.g., piping, jq for JSON parsing, backgrounding with &).
- Mention that Azure CLI is cross-platform and provide explicit instructions for Linux/macOS users where relevant.
- Include references to Linux-native editors (e.g., Vim, nano) or mention that VS Code is available cross-platform.
- Where PowerShell jobs are discussed, provide equivalent CLI or bash backgrounding techniques.
- Review all examples to ensure parity in detail and troubleshooting tips for both CLI and PowerShell users.
Governance
Remediate non-compliant resources
...ticles/governance/policy/how-to/remediate-resources.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. In most tabbed sections, the Azure Portal (GUI) instructions are presented first, followed by PowerShell, and then Azure CLI. PowerShell examples are detailed and comprehensive, while Azure CLI examples are present but sometimes less detailed. There is no mention of Linux-specific tools, shells, or workflows, and the scripting focus is on PowerShell, which is traditionally associated with Windows environments. No Bash or Linux-native command-line examples or context are provided.
Recommendations
- Provide Bash shell examples alongside PowerShell, especially for Azure CLI commands, to demonstrate parity for Linux users.
- Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and can be run in Bash, Zsh, or other shells.
- Where scripting is shown (e.g., loops or variable assignment), include both PowerShell and Bash script examples.
- Clarify that Cloud Shell supports both Bash and PowerShell, and show how to select or use each.
- If referencing the Azure Portal, note that it is OS-agnostic, but consider adding screenshots from browsers on Linux or macOS for inclusivity.
- Avoid language that assumes PowerShell is the default or only scripting environment; instead, present PowerShell and Bash as equal options.
Governance
List of built-in packages for guest configuration
...rticles/governance/policy/samples/built-in-packages.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. The majority of policy definitions and examples are Windows-specific, with only a handful of Linux-related entries. The page consistently references PowerShell Desired State Configuration (DSC) modules and Windows tools, with little to no mention of Linux equivalents or cross-platform alternatives. Windows policies are listed first and dominate the table, while Linux entries are sparse and sometimes marked as 'Preview'. There is a lack of Linux-specific module references and practical examples for Linux guest configuration.
Recommendations
- Add more Linux-specific policy definitions and examples to achieve parity with Windows coverage.
- Include references to Linux configuration management tools (e.g., Ansible, Chef, native shell scripts) where applicable, not just PowerShell DSC.
- Provide Linux equivalents for each Windows-focused policy, or clearly indicate if a policy is not applicable to Linux.
- Ensure Linux policies are not relegated to 'Preview' status if Windows equivalents are GA.
- Document the modules and scripts used for Linux guest configuration in the 'Required DSC modules' column, similar to Windows.
- Consider reordering or grouping the table to present Windows and Linux policies side-by-side for easier comparison.
Governance
Programmatically create policies
...es/governance/policy/how-to/programmatically-create.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-specific tools and instructions, such as Azure PowerShell and ARMClient, and referencing Windows installation paths for Azure CLI. PowerShell examples are given first and in greater detail, while Linux-specific instructions, such as installing Azure CLI on Linux or using Bash, are missing. ARMClient is a Windows-only tool, and there is no mention of Linux alternatives or parity for command-line usage. The documentation lacks explicit Linux/Bash examples and does not address cross-platform differences.
Recommendations
- Include explicit instructions and examples for Linux users, such as installing Azure CLI on Linux and using Bash.
- Provide parity in example ordering, alternating or grouping PowerShell and CLI examples together, and avoid always presenting PowerShell first.
- Mention cross-platform compatibility for tools, or suggest Linux alternatives to ARMClient (e.g., curl, httpie, or az rest).
- Clarify when commands or tools are Windows-specific and provide equivalent Linux/macOS commands.
- Add notes or sections highlighting platform differences and ensuring all users can follow the documentation regardless of OS.
Governance
Tutorial: Build policies to enforce compliance
...icles/governance/policy/tutorials/create-and-manage.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing PowerShell examples before Azure CLI, using Windows-style file paths (e.g., 'c:\policies\coolAccessTier.json'), and omitting explicit Linux/macOS shell examples. The PowerShell section is more extensive and detailed than the Azure CLI section, and there are no Bash or Linux-specific instructions, nor are there notes about cross-platform differences in file paths or shell usage.
Recommendations
- Add explicit Bash/Linux/macOS shell examples alongside PowerShell, especially for file-based operations (e.g., use '/home/user/policies/coolAccessTier.json' in CLI examples).
- Ensure Azure CLI examples are as detailed and comprehensive as PowerShell examples, including parameter usage and file-based definitions.
- Include notes or callouts about cross-platform differences, such as file path formats and shell syntax.
- Consider presenting Azure CLI (cross-platform) examples before PowerShell (Windows-centric) to avoid implicit prioritization.
- Add troubleshooting or installation notes for both Azure CLI and PowerShell on Linux/macOS platforms.
Governance
Tutorial: Add user assign identities to virtual machines
...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 performing tasks using the Azure Portal and Azure PowerShell, with all CLI examples and automation scripts shown exclusively in PowerShell. There are no examples or guidance for using cross-platform tools such as Azure CLI, Bash, or other Linux-native approaches, which may disadvantage users on Linux or macOS systems. The PowerShell section is extensive and assumes familiarity with Windows-centric tooling, while Linux equivalents are absent.
Recommendations
- Add equivalent step-by-step instructions using Azure CLI (az) commands, which are cross-platform and widely used on Linux and macOS.
- Include Bash script examples for policy definition, assignment, and remediation tasks.
- Explicitly mention that PowerShell Core is available on Linux/macOS, but also provide Azure CLI alternatives for users who prefer native Linux tools.
- Review and update the documentation to ensure that Linux users can follow all steps without needing to switch to Windows or PowerShell.
- Consider adding a 'Platform parity' note at the top, clarifying which instructions apply to all platforms and linking to platform-specific guides if necessary.
High Priority
View Details →
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-specific instructions and notes. The prerequisites and query sections mention Azure PowerShell before Azure CLI, and there are no explicit Linux shell (bash) examples or references to Linux-specific usage patterns. The documentation assumes familiarity with PowerShell and Windows-centric tools, while omitting equivalent Linux command-line workflows or troubleshooting notes.
Recommendations
- Add explicit bash shell examples for Azure CLI commands, showing usage in Linux/macOS environments.
- Include troubleshooting notes for Linux users, such as authentication methods and environment setup for Azure CLI.
- Balance the order of examples: alternate between Azure CLI and PowerShell, or present CLI first to avoid implicit Windows-first bias.
- Mention cross-platform compatibility of Azure CLI and PowerShell, and clarify any differences in behavior or setup between Windows and Linux.
- Provide links to Linux-specific documentation for Azure CLI and PowerShell installation and usage.
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 PowerShell examples are consistently presented alongside CLI, and sometimes with additional explanation. Several examples and notes reference PowerShell-specific behaviors (e.g., ConvertTo-Json, variable handling), and the sample JSON data is Windows-centric (Windows OS, WindowsServer image). For CLI examples, Linux-specific shell usage is implied (awk, sed, tail), but there is no explicit mention of Linux, nor are Bash or other Linux shell alternatives discussed. There are no examples using Linux-native tools or scripting patterns outside of Azure CLI, and the documentation does not clarify cross-platform differences or parity.
Recommendations
- Explicitly state that Azure CLI examples are cross-platform and show how they work in both Windows CMD/PowerShell and Linux Bash environments.
- Add Linux/Bash-specific notes or examples, especially for file handling and command chaining (e.g., using xargs, grep, or alternative to awk/sed/tail for Windows users).
- Balance sample data to include both Windows and Linux VM images (e.g., show an example with Ubuntu or CentOS).
- Clarify any differences in output formatting or scripting between PowerShell and Bash, especially for JSON handling.
- Consider adding a section on troubleshooting or adapting queries for Linux users, including common shell pitfalls.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias in its treatment of shell-specific escape characters, listing PowerShell and cmd before Bash and providing a PowerShell-specific example. There are no Linux-specific command-line examples, and PowerShell is mentioned with a sample, while Bash is only briefly described. No Linux tools or patterns are referenced elsewhere, and there are no CLI or scripting examples for Linux users.
Recommendations
- Provide Linux shell (Bash) examples alongside PowerShell and cmd for all shell-specific instructions, not just escape characters.
- Include Azure CLI examples for running Resource Graph queries from Linux environments.
- Ensure that Linux/Bash instructions are presented before or alongside Windows/PowerShell instructions, rather than after.
- Add a section or note about cross-platform usage, clarifying parity and differences between Windows and Linux environments.
- Reference Linux tools (such as jq for JSON parsing) where relevant, and provide sample usage.
Governance
Run Azure Resource Graph query using REST API
...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. PowerShell is listed before Bash in prerequisites and examples, and Visual Studio Code is recommended as the terminal environment, which is more commonly used on Windows. The PowerShell example is presented before the Bash example, and the explanation of escaping syntax focuses on PowerShell specifics. There is no mention of native Linux terminals or editors, and the guidance assumes familiarity with Windows-centric tools.
Recommendations
- List Bash or native Linux shell options before PowerShell in prerequisites and examples.
- Include instructions for running commands in common Linux terminal environments (e.g., GNOME Terminal, Konsole) and editors (e.g., Vim, Nano), not just Visual Studio Code.
- Provide Linux-specific notes, such as file path conventions and environment setup.
- Balance the order of examples so that Bash/Linux commands are presented first or equally with PowerShell.
- Mention that Azure CLI and az rest work natively on Linux and macOS, not just in Git Bash or PowerShell.
- Clarify that Visual Studio Code is cross-platform, or suggest alternative editors for Linux users.
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. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is historically Windows-centric) and the absence of explicit Linux shell (bash/zsh) or scripting examples indicate a mild Windows bias. There are no Linux-specific command-line examples (e.g., bash, curl, jq), nor is there mention of Linux-native tools or patterns. The PowerShell example is given equal prominence as the CLI, but no Linux shell alternatives are shown.
Recommendations
- Add explicit bash/zsh shell examples using Azure CLI to demonstrate usage on Linux and macOS.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide OS-specific notes if needed.
- Consider including examples using common Linux tools (e.g., piping Azure CLI output to jq for JSON parsing).
- If PowerShell is shown, note that PowerShell Core is cross-platform, or provide a Linux PowerShell example.
- Ensure that documentation does not imply PowerShell is the default or preferred method, especially for cross-platform audiences.
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, but omits explicit Linux shell (bash) examples. PowerShell is featured as a primary method alongside CLI, which can be run on Linux but is often associated with Windows. There is no mention of Linux-specific tools, nor are Linux command-line patterns (e.g., bash, curl, jq) demonstrated. The ordering of examples (CLI, then PowerShell, then Portal) puts Windows-centric tooling before Linux-native approaches, and the lack of Linux-specific instructions or troubleshooting tips further reinforces a Windows bias.
Recommendations
- Add explicit bash/Linux shell examples for each query, showing how to run az graph query from a Linux terminal.
- Include notes or troubleshooting tips for Linux users, such as authentication, environment setup, or differences in output formatting.
- Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (cmd/PowerShell) and Linux (bash/zsh).
- Consider reordering examples or providing tabs for Linux and Windows usage to highlight parity.
- Mention Linux-native tools (e.g., curl, jq) where relevant, especially for scripting or automation scenarios.
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 and still most commonly used on Windows) and the absence of Linux-specific shell examples (such as Bash or scripting with jq/curl) indicate a bias towards Windows users. Additionally, PowerShell is presented as a primary tab, reinforcing the Windows-first approach. There are no explicit Linux shell or tool examples, nor is there guidance for Linux-native workflows.
Recommendations
- Add explicit Bash shell examples using az CLI, demonstrating output parsing with jq or similar Linux tools.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide platform-specific notes if needed.
- Consider including examples for other cross-platform scripting environments (e.g., Python, REST API via curl) to improve parity.
- Reorder tabs or provide equal prominence to Linux-native workflows alongside PowerShell.
- Mention installation and usage differences for CLI and PowerShell on Linux vs Windows, if relevant.
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 CLI, sometimes before or with equal prominence. There are no explicit Linux shell (bash/zsh) or scripting examples, nor is there mention of Linux-specific tooling or usage patterns. The documentation does not clarify cross-platform compatibility for PowerShell or CLI commands, and does not offer Linux-first or Linux-specific guidance.
Recommendations
- Add explicit bash/zsh shell examples for each query, demonstrating usage in a native Linux environment.
- Clarify that Azure CLI is cross-platform and provide usage notes for Linux and macOS users.
- If PowerShell examples are included, specify whether they work with PowerShell Core on Linux/macOS, or provide alternatives.
- Consider ordering examples with Azure CLI (cross-platform) first, followed by PowerShell, to avoid implicit Windows-first bias.
- Mention any OS-specific prerequisites or differences in command behavior between Windows and Linux.
- Include troubleshooting or environment setup notes for Linux users, such as installation instructions for Azure CLI on Linux.
High Priority
View Details →
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 there is a lack of parity for Linux-specific scenarios except for a single example ('installed_application_linux'). Windows terminology and tools (PowerShell, WindowsPendingReboot) are mentioned more frequently and prominently than Linux equivalents. There are no examples for Linux guest configuration assignments such as pending reboot or compliance checks, and the documentation does not provide Linux-specific patterns or guidance outside the one application installation example.
Recommendations
- Add equivalent Linux guest configuration assignment examples, such as checking for pending reboot or compliance status on Linux machines.
- Include Linux-specific assignment names and queries in each scenario, not just for application installation.
- Provide guidance on Linux tools or patterns where relevant, and ensure examples are balanced between Windows and Linux.
- Avoid using Windows-specific terminology exclusively; clarify when instructions apply to both platforms or provide platform-specific sections.
- Review the order of examples to avoid always listing Windows scenarios first, and alternate or group by platform for clarity.
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, but does not include explicit Linux shell (bash) or cross-platform scripting examples. PowerShell is featured as a primary scripting interface, which is traditionally Windows-centric, and is always presented alongside or immediately after the CLI example. There are no Linux- or macOS-specific instructions, nor are there any notes about running the CLI in bash or other Unix shells. This may make Linux users feel less directly supported, especially as PowerShell is still more commonly associated with Windows environments.
Recommendations
- Add explicit bash or shell script examples for each query, demonstrating usage in a typical Linux environment.
- Clarify that Azure CLI commands are cross-platform and can be run in bash, zsh, or other Unix shells, not just Windows Command Prompt or PowerShell.
- If PowerShell is included, consider also including a bash example or note for parity.
- Add a section or note about installing and using Azure CLI on Linux/macOS, if relevant.
- Where possible, avoid presenting PowerShell as the default or primary scripting interface unless there is a clear reason.
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 for each query. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and its inclusion alongside CLI in every example may signal a Windows bias. There are no explicit Linux shell (bash/zsh) examples, nor are Linux-specific usage notes provided. The ordering of examples (CLI first, then PowerShell) is neutral, but the lack of Linux-native command examples (e.g., bash scripts, curl, jq) and the exclusive mention of PowerShell as the alternative shell interface reflects a subtle Windows bias.
Recommendations
- Add explicit Linux shell examples (e.g., bash scripts using az CLI, piping to jq for output processing).
- Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS environments.
- Consider including examples for other popular Linux tools or scripting environments where relevant.
- If PowerShell is mentioned, note that PowerShell Core is available on Linux, or provide equivalent bash commands.
- Review documentation for assumptions about user environment and make sure Linux/macOS users are equally supported.
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) and the absence of explicit Linux shell examples (such as Bash) or references to Linux-specific usage patterns indicate a mild Windows bias. Additionally, PowerShell is listed as a primary tab, which may suggest Windows-first thinking. No Linux-specific tools or shell commands are mentioned.
Recommendations
- Add explicit Bash or Linux shell examples for running the Azure CLI command.
- Clarify that Azure CLI works on both Windows and Linux, and provide platform-specific notes if needed.
- Consider including examples using other cross-platform tools (e.g., REST API via curl) to further improve parity.
- If PowerShell is included, mention that PowerShell Core is available cross-platform, or clarify any platform limitations.
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 associated with Windows, though now available cross-platform) and the absence of explicit Linux shell or scripting examples (e.g., Bash) shows a mild Windows bias. Additionally, PowerShell is given its own dedicated section, and there are no Linux-specific command-line examples or notes about running these commands in a Linux environment.
Recommendations
- Add explicit Bash or Linux shell examples for running the Azure CLI command, including any necessary environment setup or authentication steps relevant to Linux users.
- Clarify that Azure CLI commands are cross-platform and provide notes or examples for both Windows and Linux terminals.
- If PowerShell is included, consider also including Bash or shell scripting equivalents to ensure parity.
- Mention any differences in behavior or prerequisites when running commands on Linux versus Windows, if applicable.
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, Azure PowerShell is primarily associated with Windows environments, and its inclusion as a primary tab suggests a Windows bias. The documentation references Azure PowerShell and its parameters before mentioning any Linux-specific alternatives or shell patterns. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or usage patterns. The documentation does not clarify that Azure CLI commands work natively on Linux, nor does it provide Linux-specific context or troubleshooting.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
- Provide bash-specific examples or notes for Linux users, such as environment variable usage, quoting, or piping.
- Clarify that Azure PowerShell is available cross-platform, but highlight CLI as the recommended tool for Linux users.
- Add troubleshooting or usage notes for common Linux shell environments (e.g., bash, zsh).
- Consider reordering tabs to present Azure CLI before PowerShell, emphasizing cross-platform parity.
Governance
Overview of Azure Resource Graph
...ob/main/articles/governance/resource-graph/overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell before Linux-friendly tools like Azure CLI in several places, referencing PowerShell and Windows-centric tools (e.g., Power BI) more prominently, and lacking explicit Linux or cross-platform examples. There is no mention of Linux-specific patterns, nor are Linux shell examples (e.g., Bash) provided. REST API is mentioned, but not in a way that highlights parity with Linux workflows.
Recommendations
- Ensure Azure CLI examples are presented before or alongside PowerShell examples, as CLI is cross-platform and widely used on Linux.
- Add explicit Bash/Linux shell examples for running Resource Graph queries.
- Mention Linux and macOS compatibility wherever tools (CLI, REST API, Power BI) are referenced.
- Include references to Linux-native tools or integrations (e.g., jq for JSON processing, shell scripting) where appropriate.
- Balance tool recommendations so that Windows-only tools (like PowerShell, Power BI) are not prioritized over cross-platform alternatives.
Governance
Troubleshoot common errors for Azure Resource Graph
...cles/governance/resource-graph/troubleshoot/general.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing troubleshooting examples exclusively using PowerShell, referencing Windows-centric tools and patterns, and omitting equivalent Linux or cross-platform CLI examples. The batch subscription workaround is shown only in PowerShell, with no Azure CLI or REST API script provided. Windows tools and terminology are mentioned before or instead of Linux alternatives.
Recommendations
- Add equivalent Azure CLI examples for batch subscription queries, demonstrating how to perform the same operation on Linux/macOS.
- Include REST API sample requests using curl or other cross-platform tools for relevant scenarios.
- When referencing PowerShell, also mention Azure CLI and provide links or code samples for both.
- Review terminology and tool references to ensure parity, mentioning cross-platform options before or alongside Windows-specific ones.
- Explicitly state which troubleshooting steps apply to all platforms and clarify any platform-specific differences.
Governance
Manage Azure Service Group membership at scale
...rticles/governance/service-groups/manage-membership.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily through the exclusive use of PowerShell for automation and scripting examples. The only provided script for bulk membership management is a PowerShell (.ps1) script, with no equivalent Bash, Azure CLI, or cross-platform example. The narrative and code samples assume the use of Windows tools and workflows, and there is no mention of Linux-compatible alternatives or guidance for non-Windows environments.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts to demonstrate cross-platform automation.
- Explicitly mention that the automation steps can be performed on Linux/macOS and provide instructions for those platforms.
- Include sample scripts or commands for Linux environments, such as Bash or Python, especially for querying Azure Resource Graph and deploying ARM templates.
- Add a note clarifying tool compatibility and prerequisites for both Windows and Linux users.
- Consider referencing or linking to documentation for cross-platform Azure management tools.