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 226-250 of 613 flagged pages
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways. Windows is the default operating system for the jumpbox VM, and Windows VM deployment examples are listed before Linux equivalents in the artifact parameters table. Windows-centric tools and patterns such as Active Directory Domain Services are included without mentioning Linux alternatives. There are no Linux-specific deployment or management examples, and Linux is only referenced as an option in a few artifact parameters, often after Windows.
Recommendations
  • Provide explicit Linux deployment examples and walkthroughs alongside Windows instructions, especially for jumpbox and VM artifacts.
  • List Linux and Windows options together or alternate their order to avoid Windows-first presentation.
  • Include Linux-native identity and directory service alternatives (e.g., LDAP, FreeIPA) where Active Directory is referenced.
  • Add guidance for Linux users on managing blueprint artifacts, parameters, and assignments using Linux tools and shell commands.
  • Ensure parity in documentation for troubleshooting, monitoring, and automation for both Windows and Linux environments.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias in several areas. Many controls and audit recommendations specifically mention Windows VMs, Windows servers, or Windows web servers, often without equivalent Linux examples or guidance. Windows-specific tools (such as Microsoft IaaSAntimalware extension) are referenced, while Linux alternatives are not discussed. In sections where both Windows and Linux could be relevant (e.g., auditing privileged accounts, secure communication protocols, antivirus deployment), Windows is mentioned explicitly and frequently, with Linux coverage either missing or much less detailed.
Recommendations
  • For every control or audit recommendation that references Windows VMs or Windows servers, add equivalent guidance and examples for Linux VMs and servers.
  • When mentioning Windows-specific tools (e.g., IaaSAntimalware extension), also reference popular or supported Linux alternatives (e.g., ClamAV, Linux VM extensions for antimalware).
  • Ensure that audit instructions and prerequisites are provided for both Windows and Linux environments, especially in areas like privileged access, account policies, and secure communication protocols.
  • Where possible, use neutral language (e.g., 'virtual machines' instead of 'Windows VMs') and clarify when recommendations apply to all platforms.
  • Review and update sections such as event logging, endpoint protection, and secure web server configuration to include Linux-specific best practices and Azure-supported solutions.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows evidence of Windows bias in several ways. Most queries and examples either reference Windows-specific concepts (e.g., 'WindowsPendingReboot'), use Windows-centric assignment names, or lack Linux equivalents for similar scenarios. The documentation consistently presents PowerShell examples (a Windows-native tool) alongside Azure CLI, but does not provide Linux shell (bash) or scripting examples. In the 'pending reboot' section, only Windows machines are referenced, with no mention of how to check for pending reboots on Linux. There is only one explicit Linux example (installed_application_linux), and it appears last in the page, rather than being presented in parity with Windows scenarios.
Recommendations
  • Provide Linux-specific examples for all scenarios, especially for 'pending reboot' and compliance queries.
  • Include bash or shell script equivalents alongside PowerShell, not just Azure CLI.
  • Use assignment names and queries that are OS-agnostic or provide both Windows and Linux versions side-by-side.
  • Document how to check for Linux pending reboots, e.g., using assignment names like 'LinuxPendingReboot' if available.
  • Ensure that Linux examples are presented with equal prominence and order as Windows examples.
  • Clarify in each section which OS the example applies to, and offer alternatives for the other OS.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/overview.md ...s/blob/main/articles/governance/blueprints/overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page for Azure Blueprints exhibits a Windows bias primarily in the 'Next steps' section, where PowerShell is listed as the only command-line example for creating a blueprint, with no mention of Bash, Azure CLI, or Linux-native workflows. Additionally, PowerShell is referenced before REST API, and there is no explicit guidance or examples for Linux users or cross-platform command-line tools. The absence of Linux or Azure CLI examples may make it less accessible to users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples for blueprint creation and management alongside PowerShell examples.
  • Explicitly mention cross-platform tools (such as Azure CLI) in the 'Next steps' section and throughout the documentation.
  • Ensure that command-line instructions are provided for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) users.
  • Where PowerShell is referenced, clarify its cross-platform availability or provide alternatives for Linux users.
  • Review linked documentation pages to ensure Linux parity in examples and instructions.
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-08 00:53
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. While some controls mention both Linux and Windows (e.g., auditing Linux VM password files), the only detailed password policy audits are for Windows VMs, with no equivalent Linux password complexity or aging controls referenced. The 'Password management system' section exclusively lists Windows VM policies, and there are no examples or references to Linux tools or equivalent Linux security controls. Windows terminology and tools (such as password complexity settings and password age) are mentioned without Linux parity.
Recommendations
  • Add equivalent Linux VM password policy audits (e.g., minimum password length, complexity, password aging) to match the Windows controls.
  • Provide examples or references for managing password policies and auditing on Linux VMs (e.g., using PAM, chage, or other Linux-native tools).
  • Ensure that for every Windows-specific audit or control, a Linux equivalent is also described or referenced, or explicitly state if not available.
  • Balance the order of presentation so that Linux and Windows controls are given equal prominence, rather than listing Windows controls first or exclusively.
  • Where Azure Policy does not support Linux parity, note this limitation and suggest alternative monitoring or compliance strategies for Linux environments.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for Azure Blueprints functions demonstrates a Windows bias primarily through its references to Azure PowerShell and REST API as the main management interfaces for Blueprints-as-code. There is no mention of Azure CLI or Linux-native tooling, and PowerShell is referenced before REST API. No Linux-specific examples or cross-platform command-line usage are provided, and the documentation implicitly assumes a Windows/PowerShell-centric workflow.
Recommendations
  • Include Azure CLI examples alongside or before Azure PowerShell examples to ensure Linux parity.
  • Explicitly mention that all REST API operations and JSON templates can be managed from any OS, including Linux and macOS.
  • Add notes or sections highlighting cross-platform management options, such as using Azure CLI, Bash, or automation tools available on Linux.
  • Avoid referencing PowerShell as the default or primary management tool; present CLI and REST API options equally.
  • Provide sample commands for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) environments.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Several control mappings and policy definitions specifically reference Windows virtual machines, Windows-specific settings (such as password policies, Administrators group membership, and Microsoft IaaSAntimalware extension), and Windows web servers. In many cases, Windows examples or controls are listed before or without equivalent Linux examples, and some controls are exclusively described for Windows (e.g., password complexity, antimalware deployment). Linux coverage is present but less detailed and often appears after Windows references.
Recommendations
  • Ensure that for every Windows-specific control or example, an equivalent Linux control or example is provided where applicable (e.g., password policies, administrator group management, antimalware solutions).
  • Present Linux and Windows examples in parallel, rather than listing Windows first or exclusively.
  • Include references to Linux-native tools and security practices (e.g., auditd, fail2ban, Linux password complexity enforcement) where relevant.
  • Expand descriptions for Linux controls to match the detail given to Windows controls, especially in areas like password management, endpoint protection, and administrator group auditing.
  • Where a control is not applicable to Linux, explicitly state so to clarify parity.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-related parameters and examples in the artifact parameters table (e.g., Windows VM Administrators group, Windows domain join), providing more detailed Windows-specific instructions, and lacking parity in Linux-specific examples or administrative patterns. Linux-related artifacts are present but less emphasized and lack corresponding examples for tasks like group membership or domain join.
Recommendations
  • Add Linux-specific examples and parameters where appropriate, such as managing Linux VM administrator groups or domain join equivalents (e.g., Azure AD login for Linux).
  • Ensure Linux artifacts and instructions are presented with equal detail and prominence as Windows equivalents.
  • Provide cross-platform guidance for common administrative tasks (e.g., configuring users/groups, monitoring, security) for both Windows and Linux VMs.
  • Review and update the artifact parameters table to include Linux-specific administrative controls, not just monitoring or agent deployment.
  • Avoid listing Windows parameters and examples before Linux ones; consider grouping by OS or presenting both in parallel.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits Windows bias by referencing PowerShell as the primary CLI tool for creating blueprint artifacts, mentioning it before REST API alternatives, and omitting Linux-native tools or examples (such as Azure CLI or Bash). All example instructions and notes assume familiarity with PowerShell, and there are no Linux-specific or cross-platform command-line examples provided.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for artifact creation and management.
  • Reference cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools like PowerShell.
  • Explicitly state that all operations can be performed from Linux, macOS, and Windows, and provide links to relevant cross-platform documentation.
  • Where REST API is mentioned, provide sample curl commands or scripts usable on Linux.
  • Review all notes and instructions to ensure they do not assume a Windows environment or PowerShell 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-08 00:53
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 concepts (Test/Set methods) and linking to PowerShell documentation, without mentioning or providing equivalent examples for Linux. The terminology and referenced modules (GuestConfiguration, DSC) are strongly associated with Windows environments, and there is no guidance or examples for Linux systems or tools.
Recommendations
  • Include explicit examples and references for Linux environments, such as how machine configuration works with Linux VMs.
  • Mention and link to Linux equivalents for configuration management (e.g., Ansible, Chef, or native Linux DSC support if available).
  • Clarify whether the GuestConfiguration module and assignment types apply equally to Linux and Windows, and note any differences.
  • Provide sample remediation workflows or commands for Linux, not just PowerShell/DSC.
  • Add documentation links for Linux-specific configuration resources and methods.
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-08 00:53
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 examples and controls (such as password complexity, password age, and password reuse policies) are more detailed and numerous. The 'Password management system' section is exclusively focused on Windows VMs, with no equivalent Linux guidance. There are also more granular controls and audit checks described for Windows than for Linux. No PowerShell or CLI examples are present, but the focus on Windows VM policies and lack of Linux parity in several sections indicate a Windows-centric approach.
Recommendations
  • For each Windows VM password policy (complexity, age, length, reuse), provide equivalent Linux VM audit policies and examples (e.g., checking PAM configuration, /etc/login.defs, or auditd rules).
  • Where audit results are shown for Windows VMs, ensure similar audit checks are available and documented for Linux VMs (e.g., password complexity, password expiration, password reuse).
  • Explicitly mention and link to Linux security hardening guidance (such as CIS benchmarks for Linux) alongside Windows references.
  • Ensure that sections covering VM security, authentication, and logging provide Linux-specific details and not just generic or Windows-focused content.
  • If certain controls are not available for Linux, state this transparently and provide a roadmap or alternatives where possible.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific concepts (such as Windows VM Administrators group and Microsoft IaaSAntimalware extension for Windows servers) are mentioned explicitly, while Linux equivalents (such as sudoers group or Linux antimalware solutions) are not discussed. Examples and parameters for Windows VMs are listed before Linux VMs in several places, and there are more detailed options for Windows VM user management. There are no explicit Linux command-line or configuration examples, and the documentation does not provide parity in describing Linux administrative group management or security extensions.
Recommendations
  • Include Linux-specific administrative group management parameters and examples, such as managing sudoers or other privileged groups.
  • Provide equivalent Linux antimalware extension details and guidance, similar to the Microsoft IaaSAntimalware extension for Windows.
  • Ensure that examples and parameter tables alternate or balance Windows and Linux references, rather than listing Windows first.
  • Add explicit Linux command-line or configuration examples where relevant, especially for user/group management and security settings.
  • Clarify any differences in deployment or configuration steps for Linux VMs, not just Windows VMs.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/create-policy-definition.md ...chine-configuration/how-to/create-policy-definition.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All code examples use PowerShell, and the 'Platform' parameter is always set to 'Windows' in sample configurations. File paths in examples use Windows-style paths (e.g., C:\Local\Path\To\Package), and there are no equivalent Linux/Bash examples or Linux file paths. Windows-specific tools and cmdlets (e.g., New-GUID, Get-AzUserAssignedIdentity) are used exclusively, and references to Linux are minimal and only in passing (such as mentioning required agent versions).
Recommendations
  • Provide equivalent Linux/Bash examples for all PowerShell code snippets, including how to set variables, generate GUIDs, and interact with Azure resources using CLI or Bash.
  • Show examples where the 'Platform' parameter is set to 'Linux', and use Linux-style file paths (e.g., /home/user/package) in those examples.
  • Mention and demonstrate the use of Azure CLI as an alternative to PowerShell for relevant operations.
  • Clarify any differences in workflow or prerequisites for Linux environments, such as package authoring, publishing, and assignment.
  • Ensure that references to Windows and Linux are balanced, and avoid defaulting to Windows in all examples.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/whats-new/migrating-from-azure-automation.md ...iguration/whats-new/migrating-from-azure-automation.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell tooling and commands, with all examples using PowerShell and Azure PowerShell modules. Windows-specific modules and patterns (such as MOF files, Windows PowerShell compatibility, and Windows DSC resources) are mentioned and demonstrated, while Linux equivalents are only referenced in passing and lack concrete examples. Troubleshooting and workarounds are also PowerShell-centric, with minimal guidance for Linux users. The order of presentation and examples implicitly prioritizes Windows environments.
Recommendations
  • Provide explicit Linux/Bash examples for key steps such as exporting configurations, listing modules, and compiling configurations.
  • Include references to Linux-native DSC resources and modules, with examples of their usage.
  • Add troubleshooting guidance specific to Linux environments, including common issues and workarounds.
  • Clarify cross-platform differences in migration steps, and offer parity in documentation for both Windows and Linux users.
  • Highlight any Linux-specific tools or patterns for DSC and machine configuration, and ensure they are presented alongside Windows equivalents.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/management-groups/how-to/protect-resource-hierarchy.md ...management-groups/how-to/protect-resource-hierarchy.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a detailed Azure PowerShell sample for configuring hierarchy settings, but does not offer equivalent examples for Linux shells (such as Bash or CLI). The only command-line example is in PowerShell, which is primarily used on Windows, and there is no mention of Linux-native tools or cross-platform Azure CLI usage. This creates a bias toward Windows users and leaves Linux users without direct guidance.
Recommendations
  • Add equivalent sample commands using Azure CLI (az) in Bash or other Linux shells for all REST API operations shown.
  • Explicitly mention that the REST API can be called from any platform, and provide curl or wget examples for Linux users.
  • Where PowerShell is referenced, clarify cross-platform availability or provide alternatives for Linux and macOS.
  • Include troubleshooting notes for Linux users, such as authentication methods for acquiring access tokens outside of PowerShell.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation is heavily PowerShell-centric, with all examples and instructions using PowerShell commands. Windows is often mentioned first in tables and instructions, and Windows-specific modules/tools (e.g., PSDesiredStateConfiguration stable release) are prioritized, while Linux users are directed to use a prerelease version. There is no mention of Linux-native tools or alternative workflows, and the documentation assumes PowerShell is the primary shell on both platforms.
Recommendations
  • Provide equivalent examples using native Linux tools or shells (e.g., Bash), where possible.
  • Include Linux-first instructions and highlight Linux-specific considerations, such as package management or file system differences.
  • Offer guidance for users who may not wish to use PowerShell on Linux, including alternative approaches or clarifications about limitations.
  • Ensure parity in module versions and stability between Windows and Linux, or explain the differences and roadmap for Linux support.
  • Reorder sections to alternate or start with Linux instructions to avoid implicit prioritization of Windows.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/overview.md .../articles/governance/machine-configuration/overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell Desired State Configuration (DSC) is emphasized as the primary validation tool for both Windows and Linux, with Chef InSpec only mentioned for Linux. The open-source 'nxtools' module is highlighted for Linux management but is PowerShell-centric. Troubleshooting and log collection instructions are provided for both platforms, but Windows PowerShell examples are more detailed and appear first. References to Azure PowerShell and Windows tools are frequent, and links for managed identity configuration point to Windows VM guides before Linux equivalents.
Recommendations
  • Provide equal emphasis and examples for native Linux configuration tools (e.g., Ansible, native shell scripts) alongside PowerShell DSC.
  • Include Linux-first instructions and examples where appropriate, especially in troubleshooting and log collection sections.
  • Highlight Chef InSpec and other Linux-native validation tools with usage examples, not just mention them.
  • Add links and references to Linux VM guides and Azure CLI usage before or alongside Windows/PowerShell equivalents.
  • Clarify that PowerShell DSC is optional for Linux, and mention alternative approaches for Linux users.
  • Expand the 'nxtools' section to clarify its PowerShell focus and suggest alternatives for users who prefer native Linux tooling.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/overview/04-operations-troubleshooting.md ...onfiguration/overview/04-operations-troubleshooting.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is referenced as the primary tool for creating custom machine configuration packages and for managing Linux systems (via nxtools). Windows examples and tools (such as PowerShell scripts and Windows-specific policy definitions) are often presented first or exclusively, while Linux equivalents are present but less emphasized. The open-source nxtools module is described as a way for PowerShell users to manage Linux, reinforcing a Windows-centric workflow even for Linux administration.
Recommendations
  • Provide equivalent examples using native Linux tools (e.g., Bash, shell scripts, Ansible) for creating and managing machine configuration packages, not just PowerShell.
  • When listing policy definitions, alternate or group Windows and Linux entries to avoid Windows-first ordering.
  • Highlight Linux-native workflows and tools for troubleshooting and management, not just PowerShell-based approaches.
  • Expand documentation on Linux-specific troubleshooting steps and best practices, including references to common Linux administration tools.
  • Clarify that PowerShell is optional for Linux management, and provide guidance for users who prefer native Linux tooling.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/concepts/attestation-structure.md ...es/governance/policy/concepts/attestation-structure.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation mentions PowerShell as a primary management tool for attestations and lists it before Azure CLI, which is more cross-platform. No Linux-specific examples, shell commands, or references to Linux tooling are provided. The documentation implicitly prioritizes Windows-centric tools and patterns, potentially making it less accessible for Linux users.
Recommendations
  • Provide explicit Linux shell (bash) examples for attestation management using Azure CLI.
  • List Azure CLI before PowerShell when describing cross-platform management options.
  • Clarify that Azure CLI is fully supported on Linux and macOS, and link to installation guides for those platforms.
  • Avoid language that implies PowerShell is the default or preferred tool; present CLI and API options as equal.
  • Add a section or note for Linux users, highlighting any platform-specific considerations or best practices.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/whats-new/migrating-from-dsc-extension.md ...onfiguration/whats-new/migrating-from-dsc-extension.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows and PowerShell workflows, referencing Windows PowerShell, DSC extension for Windows, and PowerShell cmdlets throughout. There is no mention of Linux-specific equivalents, examples, or considerations, and all migration steps and tooling are described in terms of Windows/PowerShell usage. The guidance assumes familiarity with Windows-centric tools and omits Linux scenarios, leading to a lack of parity for cross-platform users.
Recommendations
  • Include explicit guidance and examples for Linux virtual machines, such as how to check for DSC extension presence and migrate configurations on Linux.
  • Describe any differences in machine configuration behavior or supported features on Linux vs. Windows.
  • Provide Linux shell (bash) or cross-platform CLI examples alongside PowerShell commands.
  • Clarify whether the migration steps and tools (such as packaging, deployment, and removal) are applicable to Linux, and if not, offer Linux-specific alternatives.
  • Reference Linux documentation and tools where relevant, such as Azure CLI or native Linux configuration management approaches.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/develop-custom-package/2-create-package.md ...tion/how-to/develop-custom-package/2-create-package.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by relying exclusively on PowerShell for all instructions and examples, including Linux scenarios. Windows-specific tools and patterns (e.g., MOF file paths, PowerShell cmdlets, output examples with Windows paths) are presented first and in detail, while Linux-specific instructions are minimal or deferred to external articles. There are no examples using native Linux tools or shell commands, and Linux users are expected to use PowerShell and Windows-centric workflows.
Recommendations
  • Provide Linux-native examples using Bash, shell scripting, or native Linux tools for authoring, compiling, and packaging configurations.
  • Include Linux file system paths and outputs in examples, not just Windows paths (e.g., show `/home/user/MyConfig` instead of `C:\dsc\MyConfig`).
  • Document alternative workflows for Linux users who may not use PowerShell, such as leveraging Ansible, shell scripts, or other configuration management tools.
  • Present Windows and Linux instructions in parallel, rather than Windows-first, to improve parity and clarity.
  • Clarify platform-specific requirements and limitations, and provide direct Linux examples within the main documentation rather than referring out to other articles.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/assign-policy-rest-api.md ...n/articles/governance/policy/assign-policy-rest-api.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 primarily using PowerShell syntax and conventions in all command examples, such as escaping with backticks and referencing PowerShell-specific behaviors. While it mentions Bash shells like Git Bash, it does not provide explicit Linux-native examples or address common Linux environments (e.g., Ubuntu, macOS Terminal) directly. The guidance for escaping characters and file referencing is tailored to Windows/PowerShell users, with only brief notes for Bash users, and no full Linux command equivalents are shown.
Recommendations
  • Provide explicit Linux-native (e.g., Ubuntu, macOS Terminal) command examples alongside PowerShell examples, using appropriate syntax for file referencing and escaping (e.g., '@request-body.json' without backticks, and proper use of single/double quotes and backslashes).
  • Structure command sections to show both Windows (PowerShell) and Linux (Bash) variants, clearly labeled, so users on either platform can follow without confusion.
  • Include notes about running commands in standard Linux terminals, not just 'Git Bash', and clarify any differences in prerequisites or environment setup for Linux/macOS users.
  • Where escape characters differ (e.g., backtick vs. backslash), provide side-by-side examples or a table summarizing the differences.
  • Review the prerequisites section to mention Linux/macOS shells and editors (e.g., nano, vim) as alternatives to Visual Studio Code, which is cross-platform but often associated with Windows.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/assign-configuration/rest-api.md ...-configuration/how-to/assign-configuration/rest-api.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates bias towards Windows by referencing the PowerShell Get-AzAccessToken cmdlet as the only method for obtaining an Azure access token, without mentioning Linux or cross-platform alternatives. There are no examples using Linux-native tools (such as Azure CLI or other authentication methods), and the only tool-specific guidance is Windows-centric.
Recommendations
  • Include instructions for obtaining an Azure access token using Azure CLI (az account get-access-token) or other cross-platform methods.
  • Provide example commands for both Windows (PowerShell) and Linux/macOS (bash, curl, Azure CLI) environments.
  • Reference cross-platform authentication documentation, not just PowerShell-specific modules.
  • Explicitly state that the REST API can be used from any OS and provide parity in tooling guidance.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides detailed schema and examples for both Windows and Linux baselines, but Windows-specific patterns (such as the scoping syntax for Windows Server roles/years) are described in greater detail and presented before Linux equivalents. The Windows ASB section introduces a unique, complex scoping pattern and provides a full example, while the Linux ASB section is comparatively brief and lacks equivalent advanced scoping or pattern examples. There is also a lack of parity in describing Linux-specific configuration nuances or advanced use cases, and no mention of Linux-native tooling or patterns.
Recommendations
  • Add more advanced Linux ASB examples, including scenarios with multiple distributions, roles, or controls if supported.
  • Describe any Linux-specific scoping or grouping mechanisms, or explicitly state if none exist.
  • Include references to Linux-native tools or configuration patterns where relevant (e.g., systemd, auditd, SSH config).
  • Ensure that Linux examples are as detailed as Windows examples, especially for complex or enterprise scenarios.
  • Present Windows and Linux examples in parallel where possible, rather than describing Windows-specific features first.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/develop-custom-package/3-test-package.md ...ration/how-to/develop-custom-package/3-test-package.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is used as the primary interface for both Windows and Linux, with examples and instructions centered around PowerShell commands. Windows-specific tools (PSExec) are mentioned before their Linux equivalents (sudo), and Windows paths and privilege contexts are described first in most sections. There is little discussion of native Linux tools or workflows outside of PowerShell, and no Linux shell (bash) examples are provided.
Recommendations
  • Provide native Linux shell (bash) examples for key operations, not just PowerShell.
  • Mention Linux privilege elevation (sudo) before or alongside Windows tools (PSExec) to avoid Windows-first ordering.
  • Discuss Linux-specific troubleshooting or file locations in parity with Windows details.
  • Clarify if PowerShell is required on Linux, or if alternative workflows (e.g., bash scripts) are possible.
  • Include notes or links for Linux users who may not have PowerShell installed by default.
GitHub Create Pull Request
← Previous Page 10 of 25 Next →