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 176-200 of 613 flagged pages
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows and PowerShell. All code examples use PowerShell, with no equivalent Bash or Linux shell examples. The 'Platform' parameter is always set to 'Windows' in examples, and file paths use Windows conventions (e.g., C:\Local\Path\To\Package). Windows-specific tools and cmdlets are referenced exclusively, and Linux equivalents or cross-platform alternatives are not demonstrated. There is little to no guidance for Linux users, despite the product supporting Linux.
Recommendations
  • Provide equivalent examples using Bash or Azure CLI for Linux environments.
  • Include at least one example with the 'Platform' parameter set to 'Linux', and use Linux-style file paths (e.g., /home/user/package.zip).
  • Mention and demonstrate how to install required modules and set up the authoring environment on Linux, not just Windows.
  • Clarify any differences or additional steps needed for Linux-based machines, especially regarding managed identities and agent versions.
  • Where PowerShell is required, explicitly note cross-platform compatibility and provide instructions for PowerShell Core on Linux.
  • Balance the order of presentation so that Linux and Windows are treated equally, or alternate which platform is shown first.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily PowerShell-centric, with all examples and tooling instructions using PowerShell commands and modules. Windows-specific patterns (such as MOF file locations, output paths, and cmdlet usage) are presented first and in detail, while Linux-specific differences are only briefly mentioned or deferred to other articles. There is a lack of Linux-native command examples (e.g., Bash, native Linux packaging tools), and the workflow assumes a Windows-style development environment (e.g., C:\ paths, PowerShell cmdlets for file operations).
Recommendations
  • Provide Linux-native examples using Bash or other common Linux shells for compiling, renaming, and packaging configuration artifacts.
  • Include Linux file path conventions (e.g., /home/user/dsc/MyConfig) alongside Windows paths.
  • Document how to use Linux-native tools (e.g., mv, zip, unzip) for file operations instead of only PowerShell cmdlets.
  • Clarify any platform-specific differences in the workflow, such as where files are stored and how permissions are managed on Linux.
  • Ensure that Linux examples are presented with equal prominence and detail as Windows examples, not just referenced or deferred to external articles.
  • Explicitly state any prerequisites or limitations for Linux environments (e.g., required packages, supported distributions) in the main workflow.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/develop-custom-package/6-sign-package.md ...ration/how-to/develop-custom-package/6-sign-package.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 Windows bias by presenting Windows/Powershell examples and instructions before Linux equivalents, relying heavily on Powershell cmdlets and Windows certificate tooling, and providing more detailed guidance for Windows scenarios. Linux instructions are present but less detailed and still use Powershell for signing, which is less typical for Linux environments.
Recommendations
  • Present Linux and Windows examples in parallel or alternate order to avoid Windows-first bias.
  • Provide native Linux command-line examples for signing (e.g., using OpenSSL or GPG directly) instead of Powershell on Linux.
  • Expand Linux-specific instructions, including certificate/key management and installation using common Linux tools (e.g., update-ca-certificates, openssl).
  • Clarify when Powershell is required on Linux and offer alternatives where possible.
  • Ensure references and templates for Linux are as comprehensive as those for Windows (e.g., provide Linux VM certificate deployment templates).
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/view-compliance.md ...rnance/machine-configuration/how-to/view-compliance.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates mild Windows bias by referencing Windows-specific tools (PowerShell cmdlet) in its API/SDK table, listing the PowerShell example before Linux equivalents, and mentioning Power BI (a Windows-centric reporting tool) for dashboard integration. There are no explicit Linux command-line examples or references to Linux-native tools (such as Bash, shell scripts, or Linux reporting solutions), and the only CLI examples are generic 'az' CLI commands, which are cross-platform but not specifically highlighted for Linux usage.
Recommendations
  • Include explicit Linux command-line examples (e.g., Bash scripts using az CLI) for querying compliance data.
  • Reference Linux-native reporting and dashboard tools (such as Grafana or Kibana) alongside Power BI.
  • Provide parity in SDK/API documentation by listing Linux-friendly tools (e.g., Bash, curl, jq) and showing how to use them to access compliance data.
  • Avoid listing Windows/PowerShell tools before cross-platform or Linux equivalents; present them side-by-side or in separate, clearly labeled sections.
  • Add screenshots or walkthroughs from Linux environments where possible, not just Azure Portal or Windows-centric interfaces.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/overview/02-setup-prerequisites.md ...chine-configuration/overview/02-setup-prerequisites.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 mild Windows bias by listing Windows and PowerShell tools and patterns before Linux equivalents, referencing PowerShell DSC as the primary validation tool for both Windows and Linux, and linking to Windows-specific configuration guides. Linux tools (Chef InSpec) are mentioned but appear secondary, and Linux-specific configuration or deployment examples are missing.
Recommendations
  • Provide Linux-first or parallel examples for configuration and deployment, such as using Azure CLI or Linux-native tools.
  • Include links to Linux VM managed identity configuration guides, not just Windows VM guides.
  • Expand documentation to cover Linux-specific extension deployment steps and troubleshooting.
  • Clarify the role and usage of PowerShell DSC on Linux, and offer alternative Linux-native configuration tools where possible.
  • Ensure validation tools and patterns for Linux are described with equal detail and prominence as Windows equivalents.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a moderate Windows bias. PowerShell Desired State Configuration (DSC) is presented as the primary validation tool for both Windows and Linux, with Chef InSpec only mentioned for Linux. The open-source nxtools module is highlighted as a PowerShell-based solution for Linux management, reinforcing PowerShell as the main cross-platform automation tool. Troubleshooting and log collection instructions are provided for both platforms, but PowerShell and Windows-centric tools and patterns are consistently emphasized. Windows-specific policy definitions and examples appear before Linux equivalents in lists. There is limited mention of native Linux configuration management tools (such as Ansible, Puppet, or native shell scripting), and PowerShell is positioned as the default for Linux automation.
Recommendations
  • Provide examples and guidance using native Linux configuration management tools (e.g., Ansible, Puppet, shell scripts) alongside PowerShell DSC.
  • Expand validation tool documentation to include native Linux tools and clarify when Chef InSpec or PowerShell DSC is preferable.
  • Offer troubleshooting and log collection examples using standard Linux utilities (e.g., grep, awk, journalctl) in addition to Bash scripts.
  • Balance the order of Windows and Linux examples and policy definitions to avoid consistently listing Windows first.
  • Clarify the limitations and trade-offs of using PowerShell DSC on Linux, and provide links to alternative Linux-native solutions.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, Windows paths) are mentioned first or exclusively in several sections. Troubleshooting and log collection instructions prioritize PowerShell and Windows examples, with Linux equivalents provided but often following the Windows instructions. The open-source nxtools module is described as a PowerShell solution for Linux, reinforcing a Windows-centric management approach. There is a heavier focus on Windows policy definitions in the multiple assignments table, and Windows terminology appears more frequently throughout.
Recommendations
  • Provide Bash and native Linux tool examples before or alongside PowerShell examples, especially in troubleshooting sections.
  • Highlight Linux-first management tools and workflows, not just PowerShell-based solutions for Linux.
  • Balance the listing of policy definitions to ensure equal visibility for Linux and Windows policies.
  • Include references to Linux-native automation/configuration tools (e.g., Ansible, shell scripts) where appropriate.
  • Clarify that PowerShell is optional for Linux management and offer alternative approaches.
  • Ensure that documentation sections do not default to Windows terminology or tools unless necessary.
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-09 00:34
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-native tools (such as Bash, curl, or Azure CLI). The only code sample is in PowerShell, which is primarily used on Windows. There is no mention of Linux shell commands or cross-platform alternatives, and the guidance implicitly assumes use of Windows tooling.
Recommendations
  • Add equivalent examples using Bash and curl to demonstrate REST API usage from Linux/macOS environments.
  • Provide Azure CLI examples for the same operations, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that the REST API can be accessed from any platform, and link to generic REST API usage guides.
  • Balance the documentation by presenting Linux/macOS instructions alongside Windows/PowerShell instructions.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/management-groups/manage.md ...b/main/articles/governance/management-groups/manage.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 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell (a Windows-centric tool) is consistently presented before Azure CLI examples in each section, and PowerShell command output is shown with Windows-style prompts (e.g., 'PS C:\>'). There are no Linux-specific shell examples, and the narrative assumes familiarity with PowerShell conventions. The documentation does not mention Linux-specific tools, shell environments, or considerations, and does not provide parity in example output for Bash or other Linux shells.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first in some sections to avoid implicit prioritization of Windows tools.
  • Include example outputs for Azure CLI commands, ideally shown in a Linux shell (e.g., Bash prompt), to demonstrate parity and usability for Linux users.
  • Explicitly mention that Azure CLI works cross-platform and provide guidance for Linux/macOS users where relevant.
  • Avoid using Windows-style prompts (e.g., 'PS C:\>') exclusively; consider showing CLI examples with '$' or other neutral prompts.
  • Add a short section or note about running Azure CLI and PowerShell on Linux/macOS, including installation links and shell usage tips.
  • Ensure that any advanced scripting examples (e.g., output parsing) are shown for both PowerShell and Bash where applicable.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/whats-new/agent.md ...es/governance/machine-configuration/whats-new/agent.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 🔧 Windows Tools
Summary
The documentation page presents release notes for both Windows and Linux extensions of the Azure machine configuration agent. However, there is evidence of Windows bias: PowerShell examples are provided for Linux extension management, Windows extension release notes are listed before Linux, and Windows-specific tools (PowerShell) are referenced more prominently than Linux-native alternatives. Linux examples and tools (such as Bash or native Linux commands) are missing or secondary.
Recommendations
  • Provide Linux-native command examples (e.g., Bash scripts, systemctl usage) alongside or before PowerShell/Azure CLI examples for Linux extension management.
  • Alternate the order of release notes or present Windows and Linux updates in parallel to avoid implicit prioritization.
  • Reference Linux-specific troubleshooting and management tools where appropriate (e.g., journalctl, systemctl, package managers).
  • Ensure that instructions for Linux users do not rely on Windows-centric tooling (such as PowerShell) unless absolutely necessary, and clearly indicate when cross-platform tools are required.
  • Include explicit guidance for Linux environments in all relevant sections, especially where configuration or troubleshooting steps differ from Windows.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. It focuses almost exclusively on PowerShell Desired State Configuration (DSC), Windows PowerShell versions, and Windows-specific tools and patterns. All examples, commands, and migration steps are presented using PowerShell and Windows-centric terminology, with no mention of Linux equivalents or cross-platform considerations. There are no examples or guidance for Linux VMs, nor any reference to Linux configuration management tools or patterns.
Recommendations
  • Include explicit guidance and examples for Linux VMs, such as how to check for DSC extension presence and migrate configurations on Linux.
  • Mention and provide examples for Linux configuration management tools (e.g., Ansible, Chef, native DSC for Linux) where relevant.
  • Clarify whether Azure machine configuration supports Linux and, if so, provide parity in instructions and migration steps.
  • Add cross-platform PowerShell examples (using pwsh) and note differences between Windows PowerShell and PowerShell Core on Linux.
  • Reference Linux-specific documentation and best practices for configuration management in Azure environments.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation mentions PowerShell as a primary management tool for Azure Policy attestations and lists it before Azure CLI, which may suggest a Windows-first approach. No Linux-specific examples, tools, or usage patterns are provided, and there is no mention of Bash or Linux shell scripting. The examples and instructions are platform-neutral but omit explicit Linux parity.
Recommendations
  • Provide explicit Bash or Linux shell examples for attestation management using Azure CLI.
  • Mention cross-platform compatibility for Azure CLI and clarify that PowerShell Core is available on Linux and macOS.
  • List Azure CLI before PowerShell to avoid implicit Windows-first ordering.
  • Add notes or links to Linux-specific documentation for attestation management.
  • Clarify that all operations shown (API, CLI, PowerShell) are available on both Windows and Linux platforms.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/concepts/effect-modify.md ...n/articles/governance/policy/concepts/effect-modify.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 demonstrates Windows bias primarily through the exclusive use of Azure PowerShell for querying modifiable aliases, without mentioning or providing equivalent examples for Azure CLI or REST API, which are cross-platform and commonly used on Linux. There are no Linux-specific or cross-platform command examples, and the only tooling guidance is for PowerShell, a Windows-centric tool.
Recommendations
  • Provide equivalent Azure CLI examples for operations currently shown only with Azure PowerShell.
  • Mention REST API methods for querying modifiable aliases, if available.
  • Explicitly state that Azure CLI and REST API are supported and provide links or examples for those platforms.
  • Ensure that all command-line examples are presented in both PowerShell and Azure CLI formats, or indicate platform-neutral alternatives.
  • Review other referenced documentation pages to ensure Linux parity in tooling and examples.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/concepts/initiative-definition-structure.md ...nce/policy/concepts/initiative-definition-structure.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits mild Windows bias, primarily in the 'strongType' section, where the PowerShell cmdlet Get-AzResourceProvider is referenced as the method to determine valid resource types for strongType. No Linux or cross-platform CLI alternatives are mentioned, and PowerShell is referenced before any other tooling. The rest of the page is platform-neutral, focusing on JSON and Azure concepts, but the only concrete tooling example is Windows-centric.
Recommendations
  • Include Azure CLI equivalents (e.g., 'az provider list') alongside PowerShell examples to ensure Linux parity.
  • When referencing tools or commands, present cross-platform options first or equally (e.g., 'You can use Azure CLI or PowerShell...').
  • Add notes or examples for Linux/macOS users where PowerShell is mentioned, clarifying that Azure CLI is available and supported.
  • Review other referenced documentation (e.g., samples, programmatic creation) to ensure examples are not Windows/Powershell-only.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/concepts/policy-for-kubernetes.md ...es/governance/policy/concepts/policy-for-kubernetes.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 several forms of Windows bias. Windows tools (Azure portal, Azure CLI, Azure PowerShell) are consistently presented as the primary or only method for cluster and policy management, with PowerShell commands included for resource provider registration. Instructions for using the Azure portal (a Windows-centric tool) are given before CLI alternatives. There are no explicit Linux shell or native Linux tool examples for resource provider registration, and the documentation does not mention Linux-specific patterns (e.g., bash scripting for automation, package managers for CLI installation). The page also references Windows domains and endpoints, and only briefly mentions Linux in the context of node pool support and pod security. There are no examples or guidance for Linux users who may prefer non-Microsoft tooling or workflows.
Recommendations
  • Provide Linux-native instructions for resource provider registration and other setup steps, such as using bash scripts or REST API calls.
  • Include examples for installing and managing Azure CLI on Linux distributions, and reference package managers like apt, yum, or zypper.
  • Offer parity for PowerShell commands by providing equivalent bash or shell script examples.
  • Clarify that Azure CLI and kubectl are cross-platform and provide explicit instructions for Linux users (e.g., installation, environment setup).
  • Mention and link to Linux-specific troubleshooting resources and best practices.
  • When listing portal and CLI options, alternate the order or explicitly state that both Windows and Linux users are supported.
  • Expand the FAQ and limitations sections to address Linux-specific scenarios, such as SELinux/AppArmor interactions, and clarify any differences in policy enforcement or logging on Linux clusters.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/concepts/policy-as-code.md .../articles/governance/policy/concepts/policy-as-code.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 page demonstrates a mild Windows bias. In the 'Source control' section, PowerShell is listed first when discussing export options, before CLI or Azure Resource Graph, suggesting a Windows-first approach. There are no explicit Linux shell (bash) or cross-platform CLI examples provided, nor is there mention of Linux-specific tools or workflows. The documentation references Azure Pipelines and GitHub workflows for deployment, which are cross-platform, but does not provide parity in example commands or scripts for Linux users. No explicit PowerShell scripts are shown, but the mention of PowerShell as a primary export method and lack of Linux-specific guidance or examples indicates a subtle bias.
Recommendations
  • Provide explicit bash/Azure CLI examples alongside PowerShell for common tasks such as exporting policy definitions.
  • When listing tools or methods, alternate or balance the order (e.g., CLI first, then PowerShell) to avoid Windows-first perception.
  • Include references to Linux-based automation workflows (e.g., shell scripts, cron jobs) where relevant.
  • Clarify that all steps can be performed on Linux, macOS, and Windows, and link to platform-specific guidance if available.
  • Add sample scripts or commands for both PowerShell and bash/CLI in relevant sections.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/how-to/get-compliance-data.md ...ticles/governance/policy/how-to/get-compliance-data.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 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for command-line operations, but PowerShell examples are more detailed, especially in the on-demand scan section (including job management and output inspection). PowerShell is presented before CLI in several places, and advanced usage (background jobs, output inspection) is only shown for PowerShell. There are no explicit Linux shell (bash) examples, and no mention of Linux-specific tools or patterns. The Visual Studio Code extension and GitHub Actions are cross-platform, but command-line guidance leans toward Windows/PowerShell.
Recommendations
  • Add bash shell examples for REST API calls using curl, jq, etc., to demonstrate Linux-native workflows.
  • Ensure Azure CLI examples are as detailed as PowerShell, including advanced usage (background execution, output parsing).
  • Present CLI and PowerShell examples side-by-side, or alternate which is shown first, to avoid Windows-first ordering.
  • Explicitly mention that Azure CLI works cross-platform and highlight Linux usage where relevant.
  • Include troubleshooting or output inspection examples for CLI (e.g., using jq or grep) similar to PowerShell's job/output handling.
  • Reference Linux-native tools (e.g., curl, wget) for REST API usage, not just browser-based 'Try It' options.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/how-to/migrate-from-automanage-best-practices.md ...olicy/how-to/migrate-from-automanage-best-practices.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (e.g., Windows Admin Center, IaaSAntimalware extension for Windows Server) are mentioned explicitly and in detail, while Linux equivalents are either omitted or referenced only briefly. Windows examples and policies are listed before Linux ones, and some features (such as antimalware deployment and Windows Admin Center) are described only for Windows, with no mention of Linux alternatives. There is also a lack of Linux-specific configuration or troubleshooting examples, and no mention of Linux management tools comparable to Windows Admin Center.
Recommendations
  • Provide Linux-specific examples and configuration steps for all features where Windows examples are given (e.g., antimalware, admin tools).
  • Mention Linux management tools (such as Cockpit, SSH, or Azure-native Linux management solutions) alongside Windows Admin Center.
  • Ensure that policy assignment and extension deployment instructions are given for both Windows and Linux VMs, with equal detail.
  • Avoid listing Windows policies or tools before Linux equivalents; present them together or alternate their order.
  • Include troubleshooting and diagnostic guidance for Linux VMs, not just Windows (e.g., boot diagnostics, agent installation).
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/how-to/programmatically-create.md ...es/governance/policy/how-to/programmatically-create.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 exhibits a Windows bias by prioritizing Windows tools and workflows, such as PowerShell and ARMClient, and by referencing Windows-specific installation instructions before cross-platform alternatives. PowerShell is introduced and used before Azure CLI, and ARMClient (a Windows-centric tool) is listed as a prerequisite. There is a lack of explicit Linux/macOS installation or usage guidance, and no mention of Linux-specific shell or scripting examples.
Recommendations
  • Provide cross-platform installation instructions for Azure CLI and ARMClient, including Linux and macOS, not just Windows.
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform.
  • Include bash or shell script examples for Linux/macOS users where scripting is demonstrated.
  • Clarify that ARMClient can be used on non-Windows platforms (if true), or suggest alternative tools for Linux/macOS.
  • Balance references to PowerShell and CLI throughout the document, ensuring neither is given undue prominence.
  • Explicitly mention platform compatibility for all tools and commands.
  • Add a table or section summarizing tool/platform compatibility and installation links for Windows, Linux, and macOS.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/troubleshoot/general.md ...ain/articles/governance/policy/troubleshoot/general.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias in several ways: PowerShell is the only CLI example provided for duplicating policy definitions, with no equivalent Bash, Azure CLI, or Linux shell example. Windows tools and patterns (such as PowerShell and references to Windows machines in policy audit examples) are mentioned exclusively or before Linux alternatives. There are no Linux-specific troubleshooting steps or examples, and the documentation assumes familiarity with Windows-centric tools and workflows.
Recommendations
  • Provide equivalent Azure CLI and Bash examples alongside PowerShell samples, especially for tasks like duplicating policy definitions.
  • Explicitly mention Linux compatibility and provide troubleshooting steps or examples for Linux environments where applicable.
  • When referencing policy definitions that audit Windows machines, also include examples or notes for Linux machines.
  • Ensure that instructions for tasks (such as registering resource providers or running on-demand scans) include both Windows and Linux command-line options.
  • Review all sections for implicit assumptions of Windows usage and add clarifications or alternatives for Linux users.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/tutorials/create-and-manage.md ...icles/governance/policy/tutorials/create-and-manage.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 demonstrates a Windows bias by providing PowerShell examples before Azure CLI, using Windows-style file paths (e.g., 'c:\policies\coolAccessTier.json'), and omitting Linux-specific instructions or examples (such as bash, shell, or Linux file paths). There are no explicit references to Linux tools, nor are Linux command-line patterns or environment-specific notes included. The overall flow assumes familiarity with Windows conventions and does not address Linux users' needs.
Recommendations
  • Provide Linux-specific examples alongside PowerShell, such as bash scripts or Linux file paths (e.g., '/home/user/policies/coolAccessTier.json').
  • When showing file path usage, include both Windows and Linux formats.
  • Add notes or sections clarifying any OS-specific behaviors, especially for CLI commands and file handling.
  • Ensure Azure CLI examples are given equal prominence and order as PowerShell examples, or consider presenting CLI first due to its cross-platform nature.
  • Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and provide installation links for each platform.
  • Where possible, include screenshots or instructions for Linux desktop environments (e.g., GNOME, KDE) in addition to Windows.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/samples/built-in-packages.md ...rticles/governance/policy/samples/built-in-packages.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 strong Windows bias. The introductory text and table overwhelmingly focus on Windows policies, PowerShell Desired State Configuration (DSC), and Windows-specific modules and tools. Windows policies are listed first and in far greater number than Linux policies. PowerShell and Windows DSC modules are referenced as the primary or only method for configuration, with little to no mention of Linux-native equivalents or modules. Linux examples are sparse, with only two Linux-related policies present, and there is no guidance or parity in module/tooling references for Linux.
Recommendations
  • Add more Linux-specific policy examples and ensure Linux policies are represented proportionally to Windows policies.
  • Include references to Linux-native configuration management tools or modules (e.g., Ansible, Chef, native shell scripts, or Linux DSC equivalents) where applicable.
  • In the introductory text, mention both Windows and Linux approaches equally, and provide guidance for reviewing Linux configurations, not just PowerShell scripts.
  • Where a policy applies to both Windows and Linux, provide side-by-side examples or clearly indicate the differences in implementation.
  • Ensure that for every Windows example or module, a Linux equivalent is provided if available, or explicitly state if not supported.
  • Avoid using 'Windows' as the default or primary context; instead, structure the documentation to treat both platforms equally.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/tutorials/create-custom-policy-definition.md ...ce/policy/tutorials/create-custom-policy-definition.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 page demonstrates Windows bias by providing Azure PowerShell examples alongside Azure CLI, mentioning PowerShell as a primary tool for alias discovery, and referencing the Azure portal (a GUI most commonly used on Windows) for resource export and creation. There are no explicit Linux-specific examples, nor is there mention of Linux-native tools or shell scripting alternatives. The order of presentation often places PowerShell and portal methods before or alongside CLI, rather than emphasizing cross-platform parity.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide shell-specific notes where relevant.
  • Add Linux shell scripting examples (e.g., using bash, jq) for tasks such as parsing JSON output from Azure CLI.
  • Clarify that the Azure portal is web-based and platform-agnostic, but offer alternatives for users who prefer command-line or automation.
  • Where PowerShell is mentioned, also provide equivalent bash or shell script examples for Linux users.
  • Consider reordering sections to present Azure CLI and cross-platform methods before PowerShell and Windows-centric tools.
  • Highlight any platform-specific limitations or differences in SDKs or tools.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/changes/get-resource-changes.md ...ernance/resource-graph/changes/get-resource-changes.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 page demonstrates a bias toward Windows environments by consistently presenting PowerShell examples alongside Azure CLI and Portal, with PowerShell mentioned before CLI in prerequisites and examples. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific usage patterns or tools. The CLI examples are generic and do not clarify Linux-specific nuances, and PowerShell is treated as a primary interface, which is more common on Windows.
Recommendations
  • Add explicit bash shell examples for Azure CLI usage, including login and query commands, to demonstrate parity for Linux users.
  • Clarify that Azure CLI commands work cross-platform and provide notes or examples for Linux/macOS environments (e.g., handling authentication, environment variables).
  • Reorder prerequisites and examples to present Azure CLI before PowerShell, or present both equally, to avoid Windows-first impression.
  • Include troubleshooting or tips relevant to Linux environments, such as installation steps for Azure CLI on Linux, or common issues.
  • Mention that PowerShell Core is available cross-platform, but clarify its usage on Linux/macOS if PowerShell examples are retained.
GitHub Create Pull Request
Governance https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/concepts/get-list-query-service-differences.md ...e-graph/concepts/get-list-query-service-differences.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 page demonstrates Windows bias by listing Azure PowerShell as a supported client before Azure CLI, and by referencing a REST API tutorial that is explicitly tagged with 'powershell'. There are no Linux-specific examples, nor is there mention of Linux-native tooling or shell usage. The documentation lacks parity in example coverage for Linux users.
Recommendations
  • Provide explicit Linux shell (bash) and Azure CLI examples alongside PowerShell examples.
  • Ensure that CLI examples are presented before or equally with PowerShell to avoid Windows-first perception.
  • Reference tutorials and documentation tabs that include both PowerShell and CLI (bash) instructions.
  • Mention Linux-native environments and usage patterns where appropriate, such as scripting with bash or using Linux containers.
  • Clarify that the APIs and SDKs are cross-platform and provide links to relevant Linux usage guides.
GitHub Create Pull Request
← Previous Page 8 of 25 Next →