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 151-175 of 613 flagged pages
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/tutorials/modify-virtual-machine-identity.md ...ce/policy/tutorials/modify-virtual-machine-identity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for performing tasks using the Azure Portal and Azure PowerShell, with all CLI examples and automation scripts given exclusively in PowerShell. There are no examples using cross-platform tools like Azure CLI or Bash, and no mention of Linux-specific workflows or tooling. The PowerShell section is extensive and assumes the reader is familiar with Windows-centric tools, which may disadvantage Linux users or those working in non-Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
  • Include Bash script snippets for automation to complement the PowerShell examples.
  • Explicitly mention that Azure CLI and Bash can be used for these tasks, and provide links or references to relevant documentation.
  • Ensure that the order of presentation does not prioritize Windows/PowerShell over cross-platform solutions; consider presenting Azure CLI examples before or alongside PowerShell.
  • Review and update prerequisites and instructions to avoid assumptions of a Windows environment.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/overview.md ...-docs/blob/main/articles/governance/policy/overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation mentions PowerShell and Azure CLI as ways to assign policies, but lists PowerShell before Azure CLI, and does not provide any Linux-specific examples or mention Bash explicitly. There is a tendency to reference Windows-centric tools (PowerShell) first, and no explicit parity or guidance for Linux users is provided. No Linux-specific tools, shell commands, or examples are given.
Recommendations
  • List Azure CLI before PowerShell when mentioning cross-platform tooling, or mention both together as equal options.
  • Explicitly state that Azure CLI works on Linux, macOS, and Windows, and provide Bash examples where relevant.
  • Include links or sections for Linux users, such as 'Assign policies using Bash/Azure CLI on Linux'.
  • Avoid implying PowerShell is the primary or default method unless justified by usage data; otherwise, present both CLI and PowerShell as equal choices.
  • Add a note clarifying that all policy management tasks can be performed on Linux and macOS using Azure CLI.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/first-query-rest-api.md ...cles/governance/resource-graph/first-query-rest-api.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
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 the PowerShell example is presented before the Bash example. Visual Studio Code is recommended as the terminal environment, which is more common on Windows. The documentation also refers to 'Bash shell like Git Bash', which is a Windows-centric Bash environment, rather than referencing native Linux or macOS terminals. There is no explicit Linux or macOS mention, and the guidance is tailored toward Windows users, especially those using PowerShell or Git Bash.
Recommendations
  • List Bash (or native Linux/macOS shells) before PowerShell in prerequisites and examples, or present them in parallel.
  • Explicitly mention support for Linux and macOS terminal environments, not just 'Bash shell like Git Bash'.
  • Provide example commands and notes for native Linux/macOS terminals, not just Windows-centric shells.
  • Recommend terminal environments that are cross-platform (e.g., 'any terminal of your choice'), not just Visual Studio Code.
  • Clarify that the instructions apply equally to Linux, macOS, and Windows, and provide troubleshooting notes for each platform if needed.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/iot-defender.md ...rce-graph/includes/samples-by-category/iot-defender.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. 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) examples, nor any mention of Linux-specific tools or usage patterns. This may subtly reinforce a Windows-oriented workflow, especially for users seeking Linux-native command-line guidance.
Recommendations
  • Add explicit bash/zsh shell examples using Azure CLI to demonstrate Linux-native usage (e.g., with piping, jq, etc.).
  • Clarify that Azure CLI is cross-platform and highlight its usage on Linux and macOS.
  • Consider reordering examples to present Azure CLI before PowerShell, or provide a Linux shell tab.
  • Mention installation and usage notes for Azure CLI on Linux systems.
  • If PowerShell is shown, clarify that PowerShell Core is available cross-platform, but provide native Linux shell alternatives for parity.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-container-registry.md ...cludes/samples-by-category/azure-container-registry.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal, but the PowerShell example is Windows-centric and there is no explicit Linux shell example (e.g., Bash). While Azure CLI is cross-platform, the lack of a Linux-specific shell example or mention of Linux tools/patterns may make the documentation feel biased toward Windows users, especially since PowerShell is highlighted as a separate tab.
Recommendations
  • Add a Linux/Bash shell example using Azure CLI to demonstrate usage in a native Linux environment.
  • Clarify that Azure CLI commands work on both Windows and Linux, and provide notes or examples for common Linux shell usage (e.g., piping, jq for JSON parsing).
  • Consider including a table or section comparing usage on Windows (PowerShell) vs Linux (Bash) for parity.
  • Avoid presenting PowerShell as the only scripting option; mention alternatives such as Bash or Zsh where appropriate.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/management-groups.md ...raph/includes/samples-by-category/management-groups.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is a Windows-centric tool and is always presented alongside CLI, sometimes before or with equal prominence. There are no explicit Linux shell (bash, zsh) examples, nor any mention of Linux-specific patterns or tools. The documentation does not acknowledge Linux environments or provide parity for Linux users beyond the CLI, which may lead to a perception of Windows bias.
Recommendations
  • Add explicit bash/zsh shell examples for each query, demonstrating usage in native Linux environments.
  • Clarify that Azure CLI is cross-platform and provide Linux-specific installation or usage notes where appropriate.
  • Consider reordering examples to present CLI (cross-platform) before PowerShell, or group them under 'Command-line' with OS notes.
  • Mention alternative Linux-native tools or scripting patterns where relevant.
  • Explicitly state platform compatibility for each tool to help users choose the best option for their OS.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-arc-enabled-kubernetes.md ...es/samples-by-category/azure-arc-enabled-kubernetes.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, PowerShell is traditionally associated with Windows, and its inclusion as a primary example can suggest Windows bias. There are no explicit Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-native tools or patterns. The ordering of examples (CLI, then PowerShell, then Portal) puts Windows-centric tooling before Linux-centric alternatives, and there is no guidance for Linux users beyond the CLI.
Recommendations
  • Add explicit Bash shell examples for Linux users, especially for command-line queries.
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux environments (e.g., installation, shell differences).
  • Consider including examples using other Linux-native tools (such as curl, jq, or REST API calls) where relevant.
  • Reorder examples or provide tabs for 'Linux/Bash' and 'Windows/PowerShell' to make parity clear.
  • Add notes or links to Linux-specific documentation for users who may not use PowerShell.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/overview.md ...ob/main/articles/governance/resource-graph/overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and Power BI connectors (Windows-centric tools) prominently, listing Azure PowerShell before REST API and CLI, and omitting explicit Linux or cross-platform command-line examples. There is no mention of Linux-specific tools or workflows, and the CLI is referenced but not prioritized. PowerShell is a Windows-first technology, and Power BI is primarily a Windows application.
Recommendations
  • Provide explicit Linux and macOS usage examples, especially for Azure CLI, which is cross-platform.
  • List Azure CLI before PowerShell when presenting command-line options, as CLI is more platform-neutral.
  • Include references to Linux-native tools (such as jq for JSON parsing, curl for REST API calls) in relevant sections.
  • Clarify that Power BI is Windows-only and suggest alternatives for Linux/macOS users (such as exporting data for use in other BI tools).
  • Add a section or note about running Resource Graph queries from Linux/macOS environments, including installation and authentication steps for Azure CLI.
  • Ensure parity in screenshots and walkthroughs, showing both Windows and Linux terminal examples where appropriate.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/concepts/sequencing-order.md ...les/governance/blueprints/concepts/sequencing-order.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation references PowerShell as the primary CLI tool for creating blueprint artifacts, mentioning it before REST API and omitting equivalent Linux-native tools or Azure CLI examples. This suggests a bias toward Windows tooling and patterns, potentially making it less accessible for Linux users.
Recommendations
  • Include Azure CLI examples alongside PowerShell for artifact creation and management.
  • Mention cross-platform tools (e.g., Azure CLI, Bash scripts) before or alongside Windows-specific tools.
  • Clarify that PowerShell is available on Linux, but also provide examples using Bash or other Linux-native environments.
  • Ensure REST API usage is demonstrated with curl or other Linux-friendly tools, not just referenced.
  • Review other documentation pages linked from this one to ensure Linux parity in tooling and examples.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/create-blueprint-rest-api.md ...les/governance/blueprints/create-blueprint-rest-api.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for making REST API calls, recommending PowerShell as the primary tool, and omitting equivalent Linux/macOS command-line examples (such as curl, httpie, or bash scripting). Windows tools and patterns are mentioned first and exclusively, with no guidance for users on non-Windows platforms.
Recommendations
  • Add Linux/macOS command-line examples using curl or httpie for REST API calls, including authentication steps.
  • Include bash or shell script snippets for generating bearer tokens and making authenticated requests.
  • Mention cross-platform tools (e.g., Azure CLI, ARMClient, REST clients) and provide usage instructions for both Windows and Linux/macOS.
  • Rephrase recommendations to avoid suggesting PowerShell as the default or only option for REST API interaction.
  • Ensure all code blocks are labeled with their platform or tool, and provide parity in example coverage.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/reference/blueprint-functions.md ...governance/blueprints/reference/blueprint-functions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Blueprints functions references Azure PowerShell and REST API as the primary management interfaces, with no mention of Azure CLI or Linux-specific tooling. Examples and usage patterns are generic and do not include platform-specific command-line instructions, but the only explicit tool mentioned is Azure PowerShell, which is most commonly associated with Windows. There are no Linux or cross-platform examples, nor is Azure CLI (which is cross-platform) referenced. This suggests a bias toward Windows tooling and a lack of Linux parity in the documentation.
Recommendations
  • Include Azure CLI examples alongside Azure PowerShell, especially in sections discussing management of blueprints-as-code.
  • Explicitly mention that REST API and Azure CLI are cross-platform and suitable for Linux/macOS users.
  • Add notes or examples showing how to perform common blueprint management tasks from Linux environments.
  • Review references to PowerShell and ensure they are not presented as the default or only option for automation.
  • Where possible, provide side-by-side command examples for both PowerShell and CLI to improve accessibility for non-Windows users.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/ism-protected/control-mapping.md ...ce/blueprints/samples/ism-protected/control-mapping.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several areas: many control mappings and audit recommendations explicitly mention Windows VMs, Windows web servers, and Windows-specific tools (e.g., Microsoft IaaSAntimalware extension), while equivalent Linux examples or tools are often missing or less emphasized. Windows-specific audit steps (such as auditing the Administrators group or Security Settings - Account Policies) are repeatedly listed without Linux parity. In sections where Linux is mentioned (e.g., auditing accounts without passwords), it is less frequent and less detailed compared to Windows coverage.
Recommendations
  • Ensure all audit and control recommendations that mention Windows VMs or Windows-specific tools also provide equivalent steps or tools for Linux VMs (e.g., audit sudoers group, Linux security policies, Linux antimalware solutions).
  • Where Windows web server configuration is discussed (e.g., secure communication protocols), add parallel guidance for common Linux web servers (Apache, Nginx) and their audit prerequisites.
  • For antivirus and endpoint protection, include recommendations for Linux-compatible solutions and extensions, not just Microsoft IaaSAntimalware.
  • When referencing account policies or privileged access audits, provide Linux-specific instructions (e.g., checking /etc/passwd, /etc/group, sudoers, SSH configuration).
  • Review all sections for Windows-first language and ensure Linux is mentioned with equal prominence and detail.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/ism-protected/deploy.md .../governance/blueprints/samples/ism-protected/deploy.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific concepts (such as Windows VM Administrators group and Microsoft IaaSAntimalware extension) are mentioned explicitly, while Linux equivalents (like sudoers or Linux security extensions) are not. Windows-related parameters and examples appear before or more frequently than Linux ones, and there are no Linux-specific administrative group examples or security extension references. The documentation lacks parity in describing Linux VM management and security controls, focusing more on Windows patterns and tools.
Recommendations
  • Include Linux-specific examples and explanations where Windows VM Administrators group is referenced, such as managing sudoers or other Linux admin groups.
  • Mention Linux security extensions or antimalware solutions analogous to Microsoft IaaSAntimalware extension for Windows.
  • Ensure that Linux-related parameters and controls are described with equal detail and frequency as Windows ones.
  • Where lists of users/groups are referenced for Windows, provide equivalent Linux patterns (e.g., /etc/sudoers, usermod commands).
  • Review the artifact parameters table to ensure Linux and Windows controls are presented in parallel, not with Windows first or exclusively.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/iso27001-ase-sql-workload/control-mapping.md ...s/samples/iso27001-ase-sql-workload/control-mapping.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed audit controls and policy mappings for Windows VMs (especially regarding password policies and complexity requirements), while similar Linux-specific examples are either less detailed or missing. For instance, password management and complexity settings are only described for Windows VMs, with no equivalent guidance for Linux VMs. Additionally, Windows terminology and tools are referenced without always providing Linux alternatives or parity.
Recommendations
  • Include equivalent Linux VM password policy controls and examples, such as auditing password complexity, minimum/maximum age, and password reuse restrictions for Linux VMs.
  • Where Windows-specific audit items are listed, provide parallel Linux-specific audit items (e.g., for /etc/login.defs, PAM configuration, or other Linux password management mechanisms).
  • Ensure that for every Windows VM control or example, there is a corresponding Linux VM control or example, or explicitly state if such parity is not available.
  • Avoid listing Windows controls first or exclusively; present Windows and Linux controls together or in parallel sections.
  • Reference Linux-native tools and configuration files (such as passwd, shadow, PAM, or auditd) where appropriate, alongside Windows tools.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/iso27001-shared/deploy.md ...overnance/blueprints/samples/iso27001-shared/deploy.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits Windows bias in several ways: Windows is the default or first-mentioned operating system for jumpbox VMs; Active Directory Domain Services (a Windows-centric technology) is a core component; and there is no example or guidance for deploying Linux-based equivalents (e.g., Linux jumpbox, LDAP/FreeIPA for directory services). While some artifact parameters reference Linux VM support, the overall workflow and examples are Windows-centric, and Linux alternatives are not described or prioritized.
Recommendations
  • Provide explicit examples and guidance for deploying Linux jumpbox VMs, including parameter values and recommended configurations.
  • Include instructions or options for using Linux-based directory services (such as LDAP or FreeIPA) as alternatives to Active Directory Domain Services.
  • Ensure that artifact parameters and deployment steps equally highlight both Windows and Linux options, rather than defaulting to Windows.
  • Add cross-platform PowerShell and Bash/CLI examples for blueprint deployment and management.
  • Clarify which steps or components are platform-agnostic and which are Windows-specific, and provide Linux equivalents where possible.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/iso27001-shared/control-mapping.md .../blueprints/samples/iso27001-shared/control-mapping.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation shows a moderate Windows bias. While some controls mention Linux (e.g., auditing Linux VM password files and accounts), Windows-specific controls and audit items are more detailed and numerous, especially regarding password policies and complexity. There are explicit audit items for Windows VMs (e.g., password complexity, password age, password history), but equivalent Linux controls are either missing or less detailed. Additionally, Windows terminology and tools (such as Windows VMs and their password policies) are mentioned without always providing Linux equivalents or parity in coverage.
Recommendations
  • For every Windows VM password policy audit, provide equivalent Linux VM audit controls (e.g., minimum password length, password complexity, password aging, password history) and document how to enforce/audit these on Linux VMs.
  • When listing audit controls, avoid listing Windows controls first or exclusively; instead, group by OS or provide parallel examples for both Windows and Linux.
  • Include references to Linux-native tools and configuration methods (e.g., PAM, /etc/login.defs, chage) where appropriate.
  • Ensure that all security and compliance controls that apply to Windows VMs are also considered for Linux VMs, or explicitly state if a control is not applicable to Linux.
  • Expand the documentation to mention how to monitor and enforce password and authentication policies on Linux VMs, not just Windows.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/swift-2020/control-mapping.md ...nance/blueprints/samples/swift-2020/control-mapping.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Several control mappings and policy definitions reference Windows-specific features, tools, or audit checks (e.g., Windows VMs, Windows password policies, Microsoft IaaSAntimalware extension) without providing equivalent Linux examples or parity. In some sections, Windows controls are listed before Linux ones, and certain controls (e.g., password complexity, antimalware) are only described for Windows, with no mention of Linux alternatives. While Linux is referenced in some audit controls (e.g., passwd file permissions, remote access), the coverage and detail for Linux is generally less comprehensive than for Windows.
Recommendations
  • Ensure every Windows-specific control or audit has a Linux equivalent described, where applicable (e.g., password policies, antimalware solutions, domain join status).
  • Present Linux and Windows controls together, or alternate their order, to avoid implicit prioritization of Windows.
  • Include examples or references to common Linux tools and patterns (e.g., auditd, fail2ban, ClamAV, Linux password complexity settings) where Windows tools are mentioned.
  • Expand documentation for Linux-specific security controls to match the depth provided for Windows.
  • Where a control is only applicable to Windows, explicitly state that and clarify the Linux equivalent or why it does not apply.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/swift-2020/deploy.md ...les/governance/blueprints/samples/swift-2020/deploy.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows-first bias. Windows-specific concepts (such as Windows VM Administrators group and domain join) are mentioned before Linux equivalents, and Windows VM-related parameters are described in greater detail. There are more artifact parameters and examples for Windows than for Linux, and no Linux-specific administrative group or domain join options are discussed. The documentation does not provide parity in examples or explanations for Linux environments, and Windows terminology is used without Linux alternatives.
Recommendations
  • Add Linux-specific examples and parameters, such as guidance for Linux VM administrative groups (e.g., sudoers) and domain join equivalents (e.g., LDAP, Active Directory for Linux).
  • Ensure that Linux-related artifacts and parameters are described with equal detail and clarity as Windows ones.
  • Present Windows and Linux options side-by-side in tables and explanations, rather than listing Windows first.
  • Include notes or links to Linux-specific documentation for tasks such as joining domains, managing users, and configuring diagnostic settings.
  • Where possible, use neutral terminology (e.g., 'VM administrators group' instead of 'Windows VM Administrators group') and clarify OS-specific differences.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/includes/policy/azure-policy-guest-configuration.md ...ce/includes/policy/azure-policy-guest-configuration.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows a Windows bias in several ways: Windows-specific configuration ('WindowsPendingReboot') is highlighted without a Linux equivalent, and Windows examples (PowerShell) are consistently presented alongside Azure CLI, but there are no Linux shell (bash) or Linux-specific command examples. The only explicit Linux reference is in the 'installed_application_linux' query, but no parity is provided for similar Windows scenarios. Windows tools (PowerShell) are always included, while Linux-native tools or shell usage are absent.
Recommendations
  • Provide Linux shell (bash) examples for each query, demonstrating usage from a Linux terminal.
  • Include queries and examples for Linux-specific configuration states (e.g., 'LinuxPendingReboot') where applicable.
  • Ensure that Linux scenarios are described with equal detail and prominence as Windows scenarios.
  • Add notes or sections clarifying cross-platform compatibility and differences in output or usage between Windows and Linux environments.
  • Where PowerShell is shown, also show equivalent bash/Unix shell commands for Azure CLI usage.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/concepts/remediation-options.md .../machine-configuration/concepts/remediation-options.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell DSC methods (Get/Test/Set) without mentioning Linux equivalents, linking to PowerShell documentation, and omitting examples or guidance for Linux systems. The terminology and references (such as 'VM guest configuration extension') are Windows-centric, and there is no mention of Linux-specific tools, modules, or remediation patterns.
Recommendations
  • Include explicit examples and references for Linux systems, such as using Ansible, Chef, or native Linux configuration management tools.
  • Provide links to documentation for Linux guest configuration, including how remediation works on Linux VMs in Azure.
  • Clarify whether the described mechanisms (assignmentType, enforcement, etc.) apply equally to Linux VMs and, if not, document the differences.
  • Add sample workflows or code snippets for Linux environments alongside PowerShell/Windows examples.
  • Reference cross-platform modules or APIs, and avoid assuming PowerShell DSC is the only or primary method for configuration management.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/assign-security-baselines/understand-baseline-settings-parameter.md ...ty-baselines/understand-baseline-settings-parameter.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides more detailed and complex examples for Windows (including scoping by server year and role), while Linux examples are simpler and lack equivalent advanced scoping or pattern explanations. Windows-specific patterns (e.g., 'WindowsServer\<Year>\<Role>') are described in detail, but Linux lacks parallel coverage. Windows examples are presented before Linux in the Azure Security Baseline section, and there is no mention of Linux-specific tools or advanced configuration patterns.
Recommendations
  • Add Linux examples that demonstrate advanced scoping or role-based configuration, if supported.
  • Present Windows and Linux examples in parallel, or alternate their order to avoid Windows-first bias.
  • Explicitly mention Linux equivalents for any Windows-specific patterns or tools, or clarify if such features are unavailable for Linux.
  • Expand Linux documentation to include more detailed use cases, such as mapping rules to distributions, roles, or environments.
  • Ensure that any advanced configuration options available for Windows are either matched for Linux or the documentation clearly states the difference.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/develop-custom-package/1-set-up-authoring-environment.md ...velop-custom-package/1-set-up-authoring-environment.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on PowerShell, which is a Windows-centric tool, even though it is available on Linux. All examples use PowerShell commands, and there are no Linux-native shell (e.g., Bash) equivalents or instructions. Windows is listed before Ubuntu in requirements and installation tables, and the documentation assumes PowerShell as the only interface for both platforms, potentially alienating Linux users who may prefer native tools.
Recommendations
  • Provide equivalent Bash or shell commands for Linux users alongside PowerShell examples.
  • List Linux and Windows requirements in a neutral or alternating order to avoid implicit prioritization.
  • Mention and link to Linux-native alternatives or clarify why PowerShell is required on Linux.
  • Add troubleshooting or environment setup notes specific to Linux, such as permissions, package managers, or common issues.
  • Explicitly state that PowerShell is required on Linux and provide guidance for users unfamiliar with PowerShell on Linux.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/develop-custom-package/5-access-package.md ...tion/how-to/develop-custom-package/5-access-package.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell code snippets for generating SAS tokens, referencing Azure PowerShell cmdlets, and omitting equivalent Linux or cross-platform command-line examples (such as Azure CLI or Bash). The use of PowerShell and Windows-centric tools is presented as the default, with no mention of Linux alternatives or guidance for non-Windows environments.
Recommendations
  • Include Azure CLI examples for generating SAS tokens, which are cross-platform and commonly used on Linux.
  • Provide Bash shell script snippets for relevant operations, ensuring Linux users have clear guidance.
  • Explicitly mention that the steps can be performed on both Windows and Linux, and clarify any platform-specific requirements.
  • Add a section comparing PowerShell and CLI/Bash approaches, helping users choose the best method for their environment.
  • Review references and links to ensure they are not Windows-specific and include cross-platform documentation where available.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/develop-custom-package/overview.md ...onfiguration/how-to/develop-custom-package/overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a bias towards Windows by focusing on PowerShell Desired State Configuration (DSC) and the GuestConfiguration PowerShell module as the primary tooling for both Windows and Linux. The only video tutorial provided is based on PowerShell, and there are no Linux-specific examples, tools, or workflows mentioned. The documentation references Windows-centric tools and patterns before mentioning Linux compatibility, and lacks parity in Linux-focused guidance.
Recommendations
  • Include Linux-native examples and workflows, such as using shell scripts or Ansible for configuration management.
  • Provide equivalent Linux tooling and commands for authoring, testing, and publishing machine configuration packages.
  • Add video or written tutorials demonstrating the process on a Linux system, using Linux command-line tools.
  • Clarify how Linux users can perform each step without relying on PowerShell, or highlight cross-platform alternatives.
  • Explicitly mention any differences or limitations in the Linux workflow, and offer guidance for overcoming them.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/assign-built-in-policies.md ...chine-configuration/how-to/assign-built-in-policies.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by providing a detailed example only for a Windows policy ('Audit Windows Time Zone'), with no equivalent Linux example. Windows policies and scenarios are mentioned before Linux ones, and the example walkthrough is exclusively Windows-focused. While Linux policies are referenced in lists and notes, there is no step-by-step assignment or parameter walkthrough for a Linux policy. The programmatic section lists PowerShell commands (Windows-centric) alongside CLI and REST, but does not provide Linux-specific command examples or shell scripts.
Recommendations
  • Add a parallel example walkthrough for a Linux policy (e.g., 'Audit Linux machines that have the specified applications installed'), including assignment steps and parameter configuration.
  • Ensure Linux policies are mentioned with equal prominence and detail as Windows policies in example sections.
  • Include Linux shell (bash) command examples for programmatic access, such as using Azure CLI from a Linux terminal.
  • Balance references to PowerShell with equivalent Linux-native tools or scripts where possible.
  • Add screenshots or illustrations showing Linux policy assignment and compliance results.
GitHub Create Pull Request
← Previous Page 7 of 25 Next →