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 451-475 of 613 flagged pages
Governance
How to create a machine configuration assignment using an Azure Resource Manager template
.../how-to/assign-configuration/azure-resource-manager.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by providing only a Windows-specific built-in configuration example ('AzureWindowsBaseline') and omitting any Linux equivalents. The examples and references focus on Windows resources and configurations, with no mention or example of Linux built-in configurations or Linux-specific parameters.
Recommendations
- Include examples for built-in Linux configurations (e.g., 'AzureLinuxBaseline') alongside Windows examples.
- Provide configuration parameter examples relevant to Linux systems, such as password policies, file permissions, or audit rules.
- Ensure that references and links include Linux-focused documentation and not only Windows/Powershell tabs.
- Explicitly mention Linux support and parity in the introductory sections, clarifying how to apply configurations to Linux VMs.
Create Pull Request
Governance
Manage your Azure subscriptions at scale with management groups - Azure Governance
...b/main/articles/governance/management-groups/manage.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure Portal, Azure PowerShell, and Azure CLI for all operations, but PowerShell examples are consistently presented before Azure CLI examples. PowerShell commands are shown with Windows-style prompts (e.g., PS C:\>), and output examples are given only for PowerShell, not for CLI or Linux shell environments. There are no explicit Linux shell (bash/zsh) examples, nor are there references to Linux-specific tools or patterns. The documentation assumes familiarity with PowerShell and Windows conventions, which may disadvantage Linux users.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present them side-by-side to avoid implicit prioritization.
- Provide sample outputs for Azure CLI commands, similar to the detailed PowerShell output shown.
- Include explicit bash/zsh shell examples where applicable, especially for scripting scenarios.
- Avoid Windows-specific prompts (e.g., PS C:\>) in code blocks unless also providing equivalent Linux shell context.
- Add notes or tips for Linux users regarding environment setup and command usage.
- Ensure that references to documentation modules (e.g., Az.Resources) include both PowerShell and CLI/Linux equivalents.
Governance
Details of the policy definition structure parameters
...nce/policy/concepts/definition-structure-parameters.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits Windows bias primarily in the 'strongType' section, where it references the Windows PowerShell cmdlet 'Get-AzResourceProvider' as the method to determine valid resource types for 'strongType'. No equivalent CLI or Linux-native command is mentioned, and PowerShell is referenced before any cross-platform alternatives. The rest of the page is platform-neutral, focusing on JSON and Azure concepts.
Recommendations
- Include Azure CLI equivalents (e.g., 'az provider list') alongside PowerShell examples to ensure Linux parity.
- When referencing tools or commands, present cross-platform options first or in parallel, rather than defaulting to Windows/PowerShell.
- Add explicit notes or examples for Linux/macOS users where platform-specific instructions are given.
- Audit other sections for implicit Windows-first assumptions and ensure documentation is inclusive of all major platforms.
Governance
Details of the initiative definition structure
...nce/policy/concepts/initiative-definition-structure.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates mild Windows bias by referencing Windows-specific tools (such as PowerShell's Get-AzResourceProvider) for resource type validation, without mentioning Linux or cross-platform alternatives. Additionally, the first and only tool example for strongType validation is a PowerShell cmdlet, which may implicitly prioritize Windows users. No explicit Linux or CLI examples are provided for these operations.
Recommendations
- Include Azure CLI equivalents (e.g., 'az provider show' or 'az provider list') alongside PowerShell examples for resource provider queries.
- Add notes or examples demonstrating how to perform relevant operations on Linux/macOS, especially for tasks currently shown only with PowerShell.
- Where possible, use cross-platform tools or commands first, or present them in parallel with Windows-specific ones.
- Review other referenced documentation (such as samples and how-to guides) to ensure Linux parity in examples and tooling.
Governance
Details of the policy definition structure aliases
...vernance/policy/concepts/definition-structure-alias.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation lists methods for discovering Azure Policy aliases, presenting the Visual Studio Code extension (commonly used on Windows) first, followed by Azure PowerShell examples before Azure CLI and REST API. The PowerShell section is more detailed, including advanced usage notes and examples, while the Azure CLI section is less extensive. There are no Linux-specific tools or shell examples, and the ordering and depth favor Windows-centric tools and workflows.
Recommendations
- Ensure parity in example depth and advanced usage notes between Azure PowerShell and Azure CLI sections.
- Alternate the order of CLI and PowerShell examples, or present them side-by-side to avoid implicit prioritization.
- Include Bash or shell script examples for Linux users where appropriate.
- Mention that Visual Studio Code and its Azure Policy extension are cross-platform, and highlight any Linux-specific installation or usage notes.
- Consider referencing Linux-native tools or workflows if available, or clarify the cross-platform nature of all tools mentioned.
Governance
Details of Azure Policy definition structure basics
...ernance/policy/concepts/definition-structure-basics.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias by referencing PowerShell and Azure CLI as the primary tools for policy definition creation and configuration. PowerShell is mentioned first, and specific default behaviors for Azure PowerShell and Azure CLI are described, but there is no mention of Linux-native tools, shell examples, or parity for Linux users. There are no explicit Linux or bash examples, and the only command-line tooling referenced is PowerShell and Azure CLI, which are often associated with Windows environments.
Recommendations
- Include bash or shell script examples for Linux users alongside PowerShell and Azure CLI examples.
- Clarify that Azure CLI is cross-platform and provide explicit instructions or examples for Linux/macOS environments.
- Avoid mentioning PowerShell before Azure CLI unless there is a technical reason; consider presenting both tools equally or in parallel.
- Reference Linux-native tooling or workflows where relevant, such as using curl, jq, or other common Linux utilities for interacting with Azure Policy APIs.
- Add a note or section highlighting cross-platform support and best practices for both Windows and Linux users.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by consistently listing PowerShell before Azure CLI when mentioning tooling for policy assignment and management. The phrase 'assign any of these policies through the Azure portal, PowerShell, or Azure CLI' and the order of links to assignment steps (portal, PowerShell, Azure CLI) suggest a Windows-first approach. There are no Linux-specific examples, tools, or patterns mentioned, and no explicit parity guidance for Linux users.
Recommendations
- Alternate the order of PowerShell and Azure CLI mentions, or list Azure CLI first in some sections to avoid Windows-first perception.
- Provide explicit examples or links for Linux users, such as Bash scripts or CLI usage on Linux.
- Include a note clarifying that Azure CLI is cross-platform and suitable for Linux and macOS users.
- Add references to Linux-native automation tools (e.g., shell scripting, Ansible) where relevant.
- Ensure that all instructions and code samples are tested and presented for both Windows (PowerShell) and Linux (Azure CLI/Bash) environments.
Governance
Tutorial: Disallow resource types in your cloud environment
...es/governance/policy/tutorials/disallowed-resources.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (a graphical interface most commonly accessed from Windows) for all steps and examples. There are no command-line examples using Azure CLI, Bash, or PowerShell, nor are there any references to Linux-specific workflows or tools. The only mention of command-line tools is in a warning, which lists Azure CLI and Azure PowerShell together, but does not provide any actual example or guidance for either. This results in a Windows-first and GUI-centric bias, with missing parity for Linux or cross-platform users who prefer or require CLI-based instructions.
Recommendations
- Add step-by-step instructions for assigning and managing policies using Azure CLI (with Bash examples) and Azure PowerShell.
- Include examples for creating exemptions, viewing disabled resource types, and cleaning up resources using CLI commands.
- Explicitly mention that all CLI instructions work on Linux, macOS, and Windows, and provide Bash and PowerShell syntax where appropriate.
- Add links to official Azure CLI and PowerShell documentation for policy management.
- Consider including screenshots or terminal outputs for CLI workflows to match the portal-based visuals.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric and is listed before the Portal example. There is no explicit Linux shell (e.g., Bash) or scripting example, and PowerShell is highlighted as a primary method, which may indicate a subtle Windows bias.
Recommendations
- Add explicit Bash or shell scripting examples for Linux users, demonstrating how to run the Azure CLI command in a typical Linux environment.
- Clarify that Azure CLI works cross-platform and provide usage notes for Linux/macOS where relevant.
- Consider listing cross-platform tools (Azure CLI) before Windows-centric tools (PowerShell) to avoid 'windows_first' ordering bias.
- If PowerShell is mentioned, note that PowerShell Core is available on Linux/macOS, or provide equivalent Bash alternatives.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal for each scenario. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and its inclusion alongside CLI in every example may indicate a slight Windows bias. Additionally, the PowerShell example is always presented immediately after the CLI example, which can be interpreted as giving Windows tools parity or priority over Linux-native alternatives (such as Bash scripts or direct REST API calls). There are no explicit Linux-specific examples or mentions of Linux shell scripting, nor are there references to Linux tools or patterns.
Recommendations
- Add explicit Bash shell examples using Azure CLI to demonstrate Linux usage (e.g., piping, jq for JSON parsing).
- Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows.
- Consider including REST API examples with curl for advanced users on Linux.
- If PowerShell is included, note that PowerShell Core is available on Linux and macOS, and provide usage notes or examples for those platforms.
- Avoid implying that PowerShell is the default or preferred scripting environment by alternating the order of CLI and PowerShell examples, or by grouping them under 'Scripting' rather than by platform.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for each query, but PowerShell is given equal prominence to CLI, despite being a Windows-centric tool. There are no Linux-specific shell examples (e.g., Bash, zsh), nor is there any mention of Linux-native scripting or usage patterns. The tab order consistently lists Azure CLI first, which is cross-platform, but the inclusion of PowerShell as a primary method may signal a Windows bias, especially for users who expect Bash or other Linux shell examples. No Windows-only tools are mentioned, but the lack of Linux-specific guidance or examples is notable.
Recommendations
- Add explicit Bash/zsh shell examples for running Azure CLI commands, demonstrating Linux usage patterns (e.g., piping, jq for JSON parsing).
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Consider adding notes or sections for Linux users, such as installation instructions for Azure CLI on Linux, or troubleshooting tips specific to Linux environments.
- If PowerShell is included, clarify its availability on Linux and macOS, or provide parity examples using native Linux tools.
- Review tab ordering and prominence to ensure CLI (cross-platform) is emphasized over Windows-centric tools.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. PowerShell (a Windows-centric tool) is given a dedicated tab and example, and is listed before the Portal tab. There is no explicit mention of Linux-specific tools or shell examples (e.g., Bash), nor is there guidance for running queries in a Linux-native environment. The CLI example is cross-platform, but the presence and ordering of PowerShell may suggest a Windows-first bias.
Recommendations
- Add explicit Bash shell examples for running Azure CLI commands on Linux/macOS.
- Clarify that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
- Consider reordering tabs so that cross-platform tools (Azure CLI) appear before Windows-specific tools (PowerShell).
- Mention installation and usage notes for Azure CLI on Linux systems.
- If relevant, provide guidance for using the query in other Linux-native environments (e.g., via shell scripts or automation).
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation consistently presents Azure PowerShell examples alongside Azure CLI and Portal, but always lists PowerShell before Portal and never provides Linux-specific shell examples (e.g., Bash). PowerShell is a Windows-centric tool, and its prominence may indicate a Windows bias. There are no explicit Linux shell (bash, zsh) or scripting examples, nor any mention of Linux-specific tooling or usage patterns.
Recommendations
- Add explicit Bash or Linux shell examples for each scenario, demonstrating use of Azure CLI in a Linux environment (e.g., with environment variables, piping, jq for output parsing).
- Reorder tabs or examples so that Azure CLI (cross-platform) appears before PowerShell, or clarify that CLI is recommended for Linux/macOS users.
- Include notes or sections on running these queries from Linux/macOS, addressing any differences or prerequisites.
- Consider adding troubleshooting or usage tips for Linux users (e.g., authentication, output formatting, scripting best practices).
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for every query, but PowerShell is always presented as a primary tab alongside CLI and Portal, and is explicitly called out as 'Azure PowerShell' with interactive code blocks. This can be interpreted as a Windows bias, as PowerShell is traditionally a Windows-centric tool, and there are no Linux-specific shell examples (such as Bash, zsh, or direct REST/cURL usage). The documentation does not mention Linux tools or patterns, nor does it provide parity guidance for Linux users beyond Azure CLI, which is cross-platform but not explicitly called out as such.
Recommendations
- Explicitly state that Azure CLI is cross-platform and suitable for Linux, macOS, and Windows.
- Add example usage for Bash/zsh or cURL/REST API to demonstrate Linux-native workflows.
- Consider reordering tabs so Azure CLI appears first, or clarify platform support for each tool.
- Add a note that PowerShell Core is available on Linux, if relevant, and clarify usage differences.
- Where possible, provide links or references to Linux-specific documentation or troubleshooting.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents examples for Azure CLI, Azure PowerShell, and the Azure Portal. Azure PowerShell, a Windows-centric tool, is given equal prominence to Azure CLI, but there is no explicit mention of Linux shell (bash) usage or examples. The ordering places Azure CLI first, which is cross-platform, but the inclusion of PowerShell without a Linux shell example may suggest a slight Windows bias, especially for users seeking parity in command-line tooling.
Recommendations
- Add explicit bash or shell script examples for Linux users, demonstrating how to use az graph query in a typical Linux environment.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide platform-specific notes if there are differences.
- Consider including a note about PowerShell Core being available cross-platform, or clarify if the example is for Windows PowerShell only.
- Ensure that future documentation includes Linux-specific troubleshooting or usage tips where relevant.
Governance
[Azure CLI](#tab/azure-cli)
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/authorization-resources-role-definitions-actions-list.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. Azure PowerShell, a Windows-centric tool, is given a dedicated tab and example, and appears immediately after Azure CLI. There is no explicit mention of Linux-specific tools, nor are there any Bash or shell script examples. The ordering of examples (CLI, then PowerShell, then Portal) may reinforce a Windows-first perspective, especially since PowerShell is most commonly associated with Windows environments.
Recommendations
- Add explicit Bash or shell script examples for Linux users, demonstrating the same query via Azure CLI in a Linux shell context.
- Clarify that Azure CLI is cross-platform and provide usage notes for both Windows and Linux terminals.
- Consider reordering the tabs to present cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell), or merge PowerShell and CLI examples under a 'Command Line' heading with OS-specific notes.
- Add a note or section highlighting Linux compatibility and any platform-specific considerations for running these queries.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and its inclusion as a main example can signal a Windows bias. Additionally, the PowerShell example is always presented immediately after the CLI example, which may reinforce a Windows-centric workflow. There are no Linux-specific shell examples (e.g., Bash scripts using curl, jq, etc.), nor is there mention of Linux-native tools or patterns.
Recommendations
- Add explicit Linux shell (bash) examples using Azure CLI, demonstrating output parsing with common Linux tools (e.g., jq, grep).
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Consider including a note or section for Linux users, highlighting any OS-specific considerations or tips.
- If PowerShell is included, also mention PowerShell Core (pwsh) is available on Linux/macOS, or provide parity examples for Bash.
- Review ordering of examples to avoid always presenting Windows-centric tools before cross-platform or Linux-native options.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric and is listed before any mention of Linux-specific tools or shell environments. There are no examples using native Linux shells (e.g., Bash) or scripting patterns, nor is there mention of Linux-specific command-line usage beyond Azure CLI. The ordering and inclusion of PowerShell may reinforce a Windows-first perspective.
Recommendations
- Add explicit Bash shell examples to demonstrate usage in native Linux environments.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide sample shell usage (e.g., piping, environment variables).
- Consider reordering examples to present cross-platform tools (Azure CLI) before Windows-centric tools (PowerShell).
- Mention that PowerShell Core is available on Linux, if relevant, and provide guidance for Linux users.
- Include troubleshooting or usage notes for Linux users where command syntax or environment may differ.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but the PowerShell example is given equal prominence as the CLI example, despite PowerShell being primarily a Windows-centric tool. There is no explicit Linux shell (bash, zsh) example, nor mention of Linux-specific usage patterns. The CLI example is generic, but the inclusion of PowerShell as a primary tab suggests a Windows bias, especially for users who may expect bash or shell script examples on Linux.
Recommendations
- Add a dedicated Bash/Linux shell example using Azure CLI, showing usage in a typical Linux terminal.
- Clarify that Azure CLI works cross-platform and provide explicit instructions for Linux users (e.g., how to install and run az CLI on Linux).
- Consider reordering tabs so that Azure CLI (which is cross-platform) appears before PowerShell, or add a 'Linux/Bash' tab for parity.
- Mention that PowerShell Core is available on Linux, if relevant, but provide bash examples for users who do not use PowerShell.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation consistently presents Azure CLI and Azure PowerShell examples side-by-side, but Azure PowerShell (a Windows-centric tool) is always given its own dedicated tab and example, despite Azure CLI being cross-platform and more commonly used on Linux. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples showing how to use the CLI in Linux environments or integrate with Linux tools. The documentation implicitly prioritizes Windows tooling by always including PowerShell examples, which may suggest a Windows bias.
Recommendations
- Add explicit Bash shell examples for Azure CLI usage, demonstrating command execution in Linux environments.
- Clarify that Azure CLI is cross-platform and highlight its usage on Linux and macOS, not just Windows.
- Consider including examples of piping Azure CLI output to Linux tools (e.g., jq, grep) for further processing.
- If PowerShell is included, also mention PowerShell Core (pwsh) for Linux/macOS, or clarify platform compatibility.
- Review tab ordering: consider listing Azure CLI first, as it is the most cross-platform option.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation consistently presents Azure CLI and Azure PowerShell examples for each query, with PowerShell (a Windows-centric tool) always included. In all cases, the CLI example is shown first, but PowerShell is always present, and no Linux-specific shell (such as Bash) or platform-neutral scripting is referenced. There is no explicit mention of Linux tools or shell environments, nor any guidance for Linux users beyond the Azure CLI. The documentation does not acknowledge differences in shell experience or provide parity for Linux-native workflows.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and can be used in Bash, Zsh, and other Linux shells.
- Add example command lines for Bash or other Linux shells where relevant, especially for scripting or output parsing.
- Clarify that PowerShell Core is available on Linux and macOS, and provide installation guidance or links for those platforms.
- Where possible, provide platform-neutral instructions or note any differences in command syntax or output between Windows and Linux environments.
- Include troubleshooting or environment setup notes for Linux users, such as package dependencies or shell configuration tips.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation consistently provides both Azure CLI and Azure PowerShell examples for each query, with PowerShell being a Windows-centric tool. In several places, PowerShell examples are given equal prominence to CLI, and in some cases, PowerShell-specific instructions (e.g., variable assignment) are included. There is no explicit mention of Linux-specific shell usage (e.g., Bash, Zsh), nor are there examples tailored to Linux environments, such as handling quoting or environment differences. The documentation assumes parity between CLI and PowerShell, but PowerShell is primarily a Windows tool, and its inclusion may signal a Windows bias, especially for new users. Additionally, installation instructions reference Azure PowerShell before Azure CLI in some places.
Recommendations
- Add explicit Bash/Zsh/Linux shell examples where CLI usage may differ (e.g., quoting, environment variables).
- Clarify that Azure CLI is cross-platform and provide Linux-specific notes for installation and usage.
- Where PowerShell examples are given, ensure that equivalent Bash/Linux shell scripting examples are also provided.
- Review the order of presentation: consider listing Azure CLI before PowerShell to reflect its cross-platform nature.
- Add troubleshooting notes for common Linux shell issues (e.g., escaping quotes, output formatting).
- Mention that PowerShell Core is available on Linux, but clarify differences if relevant.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/concepts/definition-structure-parameters.md
...nce/policy/concepts/definition-structure-parameters.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias by referencing the Windows PowerShell cmdlet Get-AzResourceProvider as the primary method for determining valid resource types for the 'strongType' property. No equivalent Linux or cross-platform CLI (such as Azure CLI) example or mention is provided. The PowerShell tool is mentioned exclusively and before any alternative, suggesting Windows-first tooling.
Recommendations
- Include Azure CLI equivalents (e.g., 'az provider list') alongside PowerShell examples to ensure Linux and cross-platform parity.
- Explicitly state that both PowerShell and Azure CLI can be used, and provide sample commands for each.
- Avoid referencing Windows-specific tools exclusively; always offer alternatives for Linux/macOS users.
- Consider reordering examples or tool mentions so that cross-platform tools are listed first or equally.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-key-vault.md
...-graph/includes/samples-by-category/azure-key-vault.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, but there are no explicit Linux shell (e.g., Bash) or scripting examples. The ordering of tabs places Azure CLI first, which is cross-platform, but the inclusion of Azure PowerShell without mention of Linux-native alternatives (such as Bash or shell scripting) may suggest a slight Windows bias. No Linux-specific tools or patterns are referenced.
Recommendations
- Add explicit Bash or shell script examples for Linux users, demonstrating how to run Azure CLI queries in a Linux environment.
- Clarify that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
- Consider including instructions for installing and using Azure CLI on Linux.
- If PowerShell is mentioned, note that PowerShell Core is cross-platform, or provide Linux-specific usage notes.
- Review tab ordering to ensure cross-platform tools (Azure CLI) are prioritized and Windows-specific tools (Azure PowerShell) are not presented as the default or only alternative.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/microsoft-defender.md
...aph/includes/samples-by-category/microsoft-defender.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation consistently provides both Azure CLI and Azure PowerShell examples for each query, but PowerShell is given equal prominence to CLI and is always included, which can be seen as a Windows bias. There are no Linux-specific shell examples (e.g., Bash scripts, curl, jq, etc.), nor any mention of Linux-native tools or patterns. The documentation assumes users will use either Azure CLI (cross-platform) or PowerShell (primarily Windows, though available on Linux), but does not address Linux-specific usage or troubleshooting. The order of examples is Azure CLI first, then PowerShell, which is neutral, but the inclusion of PowerShell throughout is a subtle Windows bias.
Recommendations
- Add Linux-native shell examples (e.g., Bash scripts using az CLI, piping output to jq for JSON parsing).
- Explicitly mention that Azure CLI is cross-platform and provide usage notes for Linux environments.
- Include troubleshooting tips for common Linux issues (e.g., az CLI installation, authentication, file permissions).
- Consider adding examples using REST API with curl for advanced Linux users.
- Clarify that PowerShell examples are optional and provide guidance for users who prefer Bash or other shells.