Governance
496
Total Pages
410
Linux-Friendly Pages
86
Pages with Bias
17.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
186 issues found
Showing 151-175 of 186 flagged pages
Low 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 example is given equal prominence. There is no explicit mention of Linux/macOS-specific tools or shell environments (e.g., Bash), nor are there any Linux/macOS-specific usage notes. The ordering places Azure CLI first, which is positive, but the inclusion of PowerShell as a main tab and lack of Linux/macOS context creates a mild Windows bias.
Recommendations
- Add explicit notes confirming Azure CLI works on Linux/macOS and provide example commands for Bash or zsh shells.
- Clarify that Azure PowerShell can be used on Linux/macOS, or provide alternative shell examples if available.
- Consider adding a 'Linux/macOS' tab or section to highlight platform parity and address any OS-specific considerations.
- If there are differences in authentication or environment setup for Linux/macOS, document them.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides shell-specific guidance for escaping the dollar sign ($) character, listing Bash, cmd, and PowerShell. While Bash is mentioned first, PowerShell is given a dedicated example, and Windows shells (cmd, PowerShell) are covered explicitly. However, there is no evidence of exclusive Windows/Powershell examples elsewhere, nor are Windows tools or patterns prioritized in other sections.
Recommendations
- Add explicit examples for macOS shells (e.g., zsh, fish) if their escaping differs from Bash.
- Clarify that Bash guidance applies to most Unix-like shells, including Linux and macOS.
- Ensure parity in shell-specific examples by providing equal detail for Linux/macOS environments as for Windows/PowerShell.
- Consider grouping shell guidance by OS (Windows, Linux, macOS) to make parity more visible.
Governance
Run Azure Resource Graph query using REST API
...cles/governance/resource-graph/first-query-rest-api.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates mild Windows bias by listing PowerShell and Windows tools (Visual Studio Code) before Linux equivalents, and by providing PowerShell-specific guidance (escaping with backtick) before Bash. The prerequisites mention PowerShell first and suggest Git Bash for Bash users, which is a Windows-centric Bash environment. Visual Studio Code is recommended as the terminal, which is more common on Windows. However, Linux/Bash examples are present and parity is generally maintained for the core task.
Recommendations
- List Bash/Linux shell options before or alongside PowerShell in prerequisites.
- Recommend generic terminal applications (e.g., GNOME Terminal, Konsole) in addition to Visual Studio Code.
- Clarify that Bash examples work natively on Linux/macOS, not just Git Bash on Windows.
- Provide explicit mention of macOS compatibility where relevant.
- Balance example ordering so Bash/Linux instructions are not always secondary to PowerShell/Windows.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for each query, but PowerShell (a Windows-centric tool) is always listed immediately after the CLI, and no explicit Linux/macOS shell examples (e.g., Bash, zsh) are shown. There is a minor Windows-first ordering bias, but the CLI examples are cross-platform and appear first, mitigating most friction for Linux/macOS users.
Recommendations
- Explicitly state that Azure CLI examples work on Linux/macOS and Windows.
- Add example command lines for Bash/zsh where shell escaping or quoting may differ.
- Clarify any platform-specific caveats (e.g., quote escaping) with concrete examples for Linux/macOS shells.
- Consider alternating the order of CLI and PowerShell examples or grouping them under 'Cross-platform' and 'Windows-specific' headings.
Governance
Deploy Australian Government ISM PROTECTED blueprint sample
.../governance/blueprints/samples/ism-protected/deploy.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page exhibits mild Windows bias. While the main deployment steps are platform-agnostic and focus on the Azure portal UI, the artifact parameters table includes several parameters that are specific to Windows VMs (e.g., users in Windows VM Administrators group, Microsoft IaaSAntimalware extension for Windows servers). Windows-related parameters and examples are listed before or alongside Linux equivalents, but there are no explicit Linux-only examples or tools highlighted. No PowerShell or Windows command-line instructions are present, and Linux is referenced in some artifact parameters, but Windows-centric terminology and controls appear more frequently and are sometimes listed first.
Recommendations
- Ensure Linux and macOS controls and terminology are given equal prominence in artifact parameters and descriptions.
- Where Windows-specific parameters are described (e.g., Administrators group membership), provide equivalent Linux guidance (e.g., sudoers or admin group management) if applicable.
- Explicitly mention Linux/macOS compatibility and provide examples or notes for those platforms where possible.
- Review ordering in tables and lists to alternate or balance Windows and Linux references, rather than defaulting to Windows-first.
- Add links to Linux-specific documentation or best practices where relevant.
Governance
Deploy ISO 27001 Shared Services blueprint sample
...overnance/blueprints/samples/iso27001-shared/deploy.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. While the blueprint supports both Windows and Linux VM deployments, Windows is consistently presented as the default or first option (e.g., Jumpbox Operating System default is Windows, Active Directory Domain Services are Windows-centric). There are explicit artifact parameters for both Windows and Linux Log Analytics agents, but examples and guidance for Linux are less prominent. No Linux-specific tools or workflows are described, and the documentation assumes familiarity with Windows-centric Azure services (e.g., Active Directory Domain Services, Jumpbox defaults).
Recommendations
- Explicitly mention Linux support and provide Linux-first or parallel examples where applicable.
- Clarify how to select Linux as the Jumpbox OS and provide example parameter values for Linux scenarios.
- Include guidance or references for integrating with Linux-native identity solutions (e.g., LDAP, SSSD) if possible.
- Ensure that artifact parameters and deployment steps highlight Linux options equally with Windows.
- Add notes or links for Linux-specific considerations (e.g., SSH key management, Linux VM images).
Governance
Understand The Baseline Settings Parameter Format
...ty-baselines/understand-baseline-settings-parameter.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides examples and schema details for both Windows and Linux baseline settings. However, in the Azure Security Baseline (ASB) section, Windows-specific scoping patterns and examples are described in greater detail and presented before the Linux equivalent. The Windows example includes unique concepts (server roles, wildcards) not mirrored for Linux, and the Linux section is comparatively brief. There is no evidence of PowerShell-heavy bias or missing Linux examples, but Windows patterns/tools are explained first and in more depth.
Recommendations
- Present Linux and Windows examples with equal depth and order, or alternate which comes first.
- Expand the Linux ASB section to describe any unique scoping or configuration patterns analogous to Windows roles, or clarify their absence.
- Explicitly state any differences in capabilities or limitations between Windows and Linux baselines.
- Add more detailed Linux examples, possibly covering multiple distributions or advanced scenarios.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for every query, with PowerShell being a Windows-centric tool. However, Azure CLI is fully cross-platform and is presented alongside PowerShell in every case. There are no examples that are exclusively Windows/Powershell, nor is PowerShell given priority over CLI. No Linux-specific tools or shell examples (e.g., Bash, scripting, piping) are provided, but the CLI coverage ensures Linux parity for all tasks.
Recommendations
- Add explicit notes that Azure CLI commands work identically on Linux, macOS, and Windows.
- Consider including example Bash scripts or usage patterns for Linux/macOS users (e.g., piping az graph output to jq).
- Clarify that PowerShell Core is available cross-platform, but most Linux users will prefer CLI.
- If relevant, mention installation instructions for Azure CLI on Linux/macOS.
Governance
Azure Machine Configuration prerequisites
...chine-configuration/overview/02-setup-prerequisites.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates mild Windows bias by listing Windows and PowerShell examples before Linux equivalents, referencing Windows-specific tools and patterns (e.g., PowerShell DSC), and linking to Windows VM configuration guides before Linux ones. Linux is supported, but Windows terminology and tooling are more prominent and often appear first.
Recommendations
- Ensure Linux examples and instructions are presented alongside or before Windows ones, especially in sections like managed identity configuration.
- Provide explicit links and guidance for configuring managed identities and extensions on Linux VMs, not just Windows VMs.
- Clarify the use of validation tools for Linux, including PowerShell DSC v3 and Chef InSpec, and offer more detail on their installation and usage.
- Balance references to Azure PowerShell with Azure CLI, which is more cross-platform.
- Include screenshots or walkthroughs for Linux VM configuration in the Azure portal.
Governance
Azure machine configuration agent release notes
...es/governance/machine-configuration/whats-new/agent.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Windows release notes before Linux, and in the example for updating the Linux extension, PowerShell is shown first, followed by Azure CLI. There is a slight preference for Windows and PowerShell in ordering and example choice, but Linux-specific content and examples are present and reasonably complete.
Recommendations
- Alternate the ordering of Windows and Linux sections or present them in parallel to avoid implicit prioritization.
- When providing command examples for Linux, show Azure CLI first (the more platform-neutral choice), or provide bash-native examples where appropriate.
- Explicitly state platform parity in features and fixes where applicable.
- Ensure that Linux tools and workflows are mentioned with equal prominence as Windows tools.
Governance
Manage your Azure subscriptions at scale with management groups - Azure Governance
...b/main/articles/governance/management-groups/manage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation consistently presents Azure PowerShell examples before Azure CLI examples in each section, and PowerShell command outputs use Windows-style prompts (e.g., 'PS C:\>'). While both PowerShell and CLI examples are provided, the ordering and contextual cues (such as the prompt) suggest a Windows-first approach. There are no Linux/macOS-specific CLI nuances or examples, and PowerShell is traditionally associated with Windows environments.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first in some sections to balance platform representation.
- Remove or generalize Windows-specific prompts (e.g., 'PS C:\>') in command outputs to avoid implying Windows-only usage.
- Add notes clarifying that Azure CLI works natively on Linux/macOS and provide any relevant platform-specific tips (such as shell differences, authentication nuances, or installation instructions).
- Include screenshots or terminal outputs from Linux/macOS environments where appropriate.
- Explicitly state that all CLI and PowerShell commands are cross-platform, and link to installation guides for each OS.
Governance
Details of Azure Policy definition structure basics
...ernance/policy/concepts/definition-structure-basics.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions both Azure PowerShell and Azure CLI for specifying the 'mode' parameter, but it lists PowerShell first and provides slightly more detail about its default behavior. No examples are given for either tool, and no Windows-only tools or patterns are present. There are no missing Linux/macOS equivalents, but the ordering subtly prioritizes Windows tooling.
Recommendations
- When referencing command-line tools, alternate the order (e.g., mention Azure CLI before PowerShell in some sections).
- Provide explicit examples for both Azure PowerShell and Azure CLI, ensuring parity and clarity for users on all platforms.
- Add a note clarifying that both Azure CLI and PowerShell are cross-platform and available on Windows, Linux, and macOS.
- Ensure that any future examples or instructions do not assume a Windows environment or shell.
Governance
Details of the initiative definition structure
...nce/policy/concepts/initiative-definition-structure.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Summary
The documentation page is largely platform-neutral, focusing on JSON structures and Azure concepts. However, there is a minor Windows bias in the 'strongType' section, where the only tool referenced for determining valid resource types is the PowerShell cmdlet 'Get-AzResourceProvider'. No Linux or cross-platform alternatives (such as Azure CLI) are mentioned, and PowerShell is a Windows-centric tool, though it is available on other platforms.
Recommendations
- Include Azure CLI equivalents (e.g., 'az provider list') alongside PowerShell examples for tasks like listing resource providers.
- Explicitly mention that PowerShell is available cross-platform, or provide links to installation instructions for Linux/macOS.
- Where possible, provide examples using both PowerShell and Azure CLI to ensure parity for Linux/macOS users.
- Add a note that all JSON examples and Azure REST API/SDK usage are platform-agnostic.
Governance
Learn Azure Policy for Kubernetes
...es/governance/policy/concepts/policy-for-kubernetes.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias, primarily through the consistent use of Azure CLI and Azure portal instructions, which are cross-platform but often associated with Windows environments. Azure PowerShell is mentioned as an alternative for resource provider registration, but Linux-specific instructions (such as shell scripting or package manager commands) are absent. The documentation does not provide explicit Linux/macOS examples for Azure CLI installation or troubleshooting, and references to Windows domains (login.windows.net) and portal navigation are frequent. However, the core Kubernetes operations (kubectl, helm) are platform-agnostic and the add-on itself is Linux-only, which mitigates the impact of the bias.
Recommendations
- Add explicit Linux/macOS installation instructions for Azure CLI and PowerShell, including package manager commands (apt, yum, brew).
- Include troubleshooting steps or notes for Linux/macOS users, such as common permission issues or environment setup.
- Clarify that Azure CLI and kubectl commands are cross-platform and provide any OS-specific caveats.
- Where Azure portal navigation is described, mention that the portal is web-based and accessible from any OS.
- Remove or rephrase references that imply Windows exclusivity (e.g., 'login.windows.net') unless strictly necessary.
- Highlight that the Azure Policy Add-on only supports Linux node pools, and provide guidance for users on Linux clusters.
Governance
Author policies for array properties on resources
...governance/policy/how-to/author-policies-for-arrays.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Azure CLI, Azure PowerShell, and REST API as methods for passing array parameters during policy assignment. Azure PowerShell is listed explicitly alongside Azure CLI, but there is no mention of Linux/macOS-specific tools or shell environments. The Azure CLI is cross-platform, but PowerShell is traditionally associated with Windows, and its mention before REST API or other platform-neutral options may suggest a slight Windows-first bias. However, the CLI is listed first, and all examples are in JSON, which is platform-neutral.
Recommendations
- Explicitly state that Azure CLI works on Linux/macOS and provide example commands for Bash/zsh if relevant.
- Clarify that Azure PowerShell is available cross-platform, or provide links to documentation for using PowerShell on Linux/macOS.
- Consider mentioning other automation tools or SDKs that are popular on Linux/macOS, such as Python or Terraform, if relevant.
- Ensure that REST API usage is described as platform-neutral and provide curl examples for Linux/macOS users where appropriate.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for exporting Azure Policy resources, but the PowerShell section is given equal prominence despite PowerShell being primarily a Windows-centric tool. There is no explicit Linux/macOS bias, but PowerShell is less commonly used on Linux/macOS, and the documentation does not mention platform compatibility or alternatives for Linux users. The CLI example is shown first, which is positive, but the PowerShell section may create friction for non-Windows users.
Recommendations
- Clarify that Azure CLI works cross-platform (Windows, Linux, macOS), while PowerShell is traditionally Windows-focused but now available on Linux/macOS.
- Add a note about installing PowerShell Core on Linux/macOS if users wish to use PowerShell examples.
- Consider providing bash or shell script examples for exporting resources, especially for Linux/macOS users.
- Explicitly mention platform compatibility for each tool.
- If possible, provide REST API curl examples for maximum cross-platform parity.
Governance
Tutorial: Create a custom policy definition
...ce/policy/tutorials/create-custom-policy-definition.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for discovering resource aliases, but the PowerShell example is given equal prominence to the CLI, and there is no explicit mention of Linux/macOS compatibility for PowerShell. The 'Export template' and portal instructions are platform-neutral, but the PowerShell example may create friction for Linux/macOS users, as Azure PowerShell is less commonly used or installed on those platforms. The ordering of examples (CLI before PowerShell) is appropriate, but the presence of PowerShell may suggest a slight Windows bias.
Recommendations
- Explicitly note that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Clarify Azure PowerShell availability on Linux/macOS, or link to installation instructions for non-Windows platforms.
- Consider including Bash or shell script examples where appropriate.
- If PowerShell is mentioned, add a note about its cross-platform support and installation steps for Linux/macOS.
Governance
Tutorial: Self-enforce MFA through Azure Policy
...rticles/governance/policy/tutorials/mfa-enforcement.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is primarily focused on Azure portal usage, which is platform-neutral, but when command-line examples are provided, Azure CLI and Azure PowerShell are both mentioned. However, Azure PowerShell is a Windows-centric tool and is given equal prominence to Azure CLI, which is cross-platform. There are no Linux-specific tools or shell examples (e.g., Bash scripts), and PowerShell is referenced without noting its cross-platform availability or alternatives. The ordering of client experiences (portal, CLI, PowerShell) puts Windows tools before any Linux/macOS-specific guidance.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, but highlight Azure CLI as the preferred tool for Linux/macOS users.
- Provide explicit Bash shell examples for Linux/macOS users where CLI commands are shown.
- Add a note or section on how to perform equivalent tasks on Linux/macOS, especially for scripting and automation.
- If PowerShell is shown, mention that it is available for Linux/macOS and provide installation instructions or links.
- Consider reordering examples to show Azure CLI before PowerShell, or group them by platform.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and PowerShell examples for running queries, but PowerShell (a Windows-centric tool) is given equal prominence and is mentioned in prerequisites and examples. The order of presentation sometimes puts PowerShell before CLI, and there is no mention of Bash, shell scripting, or Linux/macOS-specific guidance. All command-line instructions are limited to Azure CLI (cross-platform) and PowerShell (Windows-first), with no explicit Linux/macOS context or troubleshooting.
Recommendations
- Explicitly state that Azure CLI is cross-platform and works on Linux/macOS, while PowerShell is available on all platforms but is traditionally Windows-centric.
- Add Bash or shell scripting examples where appropriate, especially for tasks like authentication or automation.
- Provide troubleshooting notes for Linux/macOS users (e.g., installation paths, permissions, environment variables).
- When listing prerequisites or examples, present Azure CLI first to emphasize cross-platform parity.
- Include a note or section on running queries from Linux/macOS environments, and link to relevant setup guides.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for running the query, but includes a dedicated Azure PowerShell tab and example, which is a Windows-centric tool. There is no explicit Linux shell example (e.g., Bash), nor is there mention of Linux-specific considerations. The Azure CLI example is cross-platform, but PowerShell is highlighted as a primary method, which may suggest a slight Windows bias.
Recommendations
- Add explicit Bash or Linux shell examples to demonstrate parity and clarify cross-platform usage.
- Note that Azure CLI works on Linux/macOS and Windows, and provide any OS-specific instructions if needed.
- Clarify whether PowerShell Core (cross-platform) is supported, or if the example is intended for Windows PowerShell.
- Consider listing Azure CLI (cross-platform) before PowerShell in tab order to emphasize platform neutrality.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all queries, but consistently lists PowerShell examples immediately after CLI, and before any mention of Linux-specific tools or shell environments. There are no Linux/macOS-specific shell examples (e.g., Bash scripts, shell pipelines), nor is there any mention of Linux-specific patterns or troubleshooting. The examples are cross-platform in that Azure CLI works on all OSes, but the presence and order of PowerShell examples, without any Linux shell equivalents, creates a subtle Windows-first bias.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users, demonstrating how to run az graph query and process results.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide OS-specific installation or usage notes if relevant.
- Consider alternating the order of CLI and PowerShell examples, or grouping them under 'Cross-platform' and 'Windows-specific' headings.
- Mention common Linux troubleshooting patterns or tools (e.g., jq for JSON parsing) where relevant.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all queries, but PowerShell is featured as a primary tab alongside CLI and Portal, which may indicate a slight Windows bias. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux/macOS-specific tools or usage patterns. However, the Azure CLI is cross-platform and is presented first in each example, which helps mitigate bias. No critical functionality is locked to Windows-only tools.
Recommendations
- Add explicit Bash shell examples for Azure CLI usage to demonstrate Linux/macOS workflows.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
- Consider including notes or links for installing and using Azure CLI on Linux/macOS.
- If PowerShell is shown, mention that PowerShell Core is available cross-platform, or provide Bash equivalents for common tasks.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure CLI (cross-platform), Azure PowerShell (Windows-centric), and the Azure Portal (web-based). However, the PowerShell example is given equal prominence as the CLI, and there is no explicit mention of Linux/macOS-specific shell usage or considerations. The CLI example is cross-platform, but PowerShell is primarily a Windows tool, and its inclusion may suggest a Windows bias. There are no Linux/macOS-specific shell examples (e.g., Bash), nor is there guidance for Linux users regarding prerequisites or environment setup.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide explicit Bash/Zsh shell examples if there are any platform-specific nuances.
- Add a note about installing and using Azure CLI on Linux/macOS, including links to relevant setup guides.
- If PowerShell is mentioned, clarify its cross-platform availability, or provide Linux/macOS PowerShell installation instructions.
- Consider adding troubleshooting or environment notes for Linux/macOS users, especially if there are known differences.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Windows Heavy Examples
Summary
The documentation demonstrates a mild Windows bias. Most queries and examples are generic and cross-platform, using Azure CLI, Azure PowerShell, and the Azure Portal, which are available on Windows, Linux, and macOS. However, several sections focus on Windows-specific scenarios (e.g., 'WindowsPendingReboot'), and Windows terminology is used in example names before Linux equivalents. PowerShell is featured as a primary tool, which is historically Windows-centric, though now available cross-platform. There is only one explicit Linux example ('installed_application_linux'), and it appears last in the sequence.
Recommendations
- Provide equivalent Linux/macOS-specific examples where Windows-specific queries are shown (e.g., add 'LinuxPendingReboot' queries).
- Balance example naming and ordering so Linux and Windows are treated equally (e.g., show both 'WindowsPendingReboot' and 'LinuxPendingReboot' queries).
- Clarify that Azure CLI and PowerShell are cross-platform, and provide Bash or shell script snippets where relevant.
- Add notes or links for Linux/macOS users about installation and usage of Azure CLI and PowerShell on their platforms.
- Where possible, avoid Windows-centric terminology in generic sections.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for each query, with PowerShell (a Windows-centric tool) always present and often listed after CLI. There are several queries and sections that specifically call out Windows Server or Windows OS update installation, with separate queries for Linux. However, there is no evidence of Linux-specific command-line tools (such as bash scripts or Linux-native tools) being referenced, and PowerShell is always included even though it is less commonly used on Linux/macOS. The documentation does not provide parity for Linux/macOS users in terms of native tooling or usage patterns, and Windows terminology (e.g., KB IDs, Windows patch classifications) is present in some queries. The examples and instructions are generally platform-neutral (using Azure CLI and PowerShell), but the inclusion and emphasis on PowerShell and Windows-specific queries/tools create a mild Windows bias.
Recommendations
- Include bash or shell script examples for Linux/macOS users where appropriate.
- Clarify that Azure CLI is cross-platform and highlight its usage for Linux/macOS users.
- Add notes or sections explaining how Linux users can use Azure CLI natively, and mention PowerShell Core for Linux if PowerShell is required.
- Where Windows-specific terminology (e.g., KB IDs, patch classifications) is used, provide Linux equivalents or clarify the differences.
- Balance the presentation order so that CLI (cross-platform) is shown before PowerShell, and explicitly mention Linux/macOS compatibility where relevant.