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 101-125 of 613 flagged pages
Governance How to create a machine configuration assignment using Terraform ...configuration/how-to/assign-configuration/terraform.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides examples for Windows virtual machines, referencing only azurerm_windows_virtual_machine resources and built-in Windows configurations (e.g., AzureWindowsBaseline). There are no examples or mentions of Linux virtual machines, Linux-specific configurations, or equivalent Linux resources. The 'get-started' link also points to a Windows PowerShell guide, reinforcing the Windows-centric approach.
Recommendations
  • Add parallel examples for Linux virtual machines using azurerm_linux_virtual_machine resources.
  • Include built-in configuration assignment examples for Linux, such as AzureLinuxBaseline.
  • Reference Linux-specific getting started guides and tools alongside Windows equivalents.
  • Clearly indicate which steps or resources are platform-specific, and provide guidance for both Windows and Linux users.
GitHub Create Pull Request
Governance How to install the machine configuration authoring module ...velop-custom-package/1-set-up-authoring-environment.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on PowerShell, which is traditionally a Windows-centric tool, even though it is available on Linux. All installation and validation steps use PowerShell commands, and there is no mention of native Linux tools or shell alternatives. The instructions for installing modules on Linux rely on PowerShell, and there are no bash or apt examples. Additionally, the documentation references Windows tools and patterns (such as PowerShell Gallery and Az PowerShell modules) without discussing Linux-native equivalents or integration.
Recommendations
  • Provide equivalent bash or shell commands for Linux users, especially for installation and validation steps.
  • Mention Linux-native configuration management tools (such as Ansible, Chef, or native DSC implementations) where relevant.
  • Clarify whether PowerShell is required on Linux, or if there are alternative approaches for Linux environments.
  • Include troubleshooting steps or notes specific to Linux environments, such as permissions, package dependencies, or differences in module versions.
  • Ensure that Linux examples are given equal prominence and detail as Windows examples, and avoid assuming PowerShell is the default shell on Linux.
GitHub Create Pull Request
Governance Remediation options for machine configuration .../machine-configuration/concepts/remediation-options.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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) and linking to PowerShell documentation, without providing equivalent examples or references for Linux systems. The terminology and remediation patterns are described in a way that assumes familiarity with Windows/PowerShell tooling, and there are no explicit Linux-specific instructions or parity examples.
Recommendations
  • Include Linux-specific examples and references, such as how remediation works with Linux guest configuration agents.
  • Provide documentation links for Linux equivalents to PowerShell DSC, such as Ansible, Chef, or native Linux guest configuration modules.
  • Clarify whether the described assignment types and remediation flows apply identically to Linux VMs, and note any differences.
  • Add sample workflows or code snippets for Linux, showing how to audit and remediate configurations.
  • Balance references to PowerShell DSC with explanations of how configuration management is handled on Linux.
GitHub Create Pull Request
Governance How to create a machine configuration assignment using the Azure Rest API ...-configuration/how-to/assign-configuration/rest-api.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by referencing the PowerShell Get-AzAccessToken cmdlet as the only method for obtaining an Azure access token, without mentioning or providing equivalent Linux or cross-platform alternatives. There are no Linux-specific tools or commands (such as Azure CLI or direct curl-based authentication) referenced, and the only authentication example is PowerShell-based.
Recommendations
  • Include Azure CLI examples (e.g., az account get-access-token) for obtaining access tokens, which work on both Linux and Windows.
  • Explicitly mention cross-platform methods for authentication, such as using curl with a token obtained via Azure CLI.
  • Provide links to documentation for both PowerShell and Azure CLI authentication methods.
  • Ensure that all examples and tool references are platform-neutral or provide parity between Windows and Linux environments.
GitHub Create Pull Request
Governance Understand The Baseline Settings Parameter Format ...ty-baselines/understand-baseline-settings-parameter.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 mild Windows bias. Windows-specific patterns (such as the scoping syntax for Windows Server year/role) are described in detail and presented before Linux equivalents. The Windows example includes unique tooling concepts (server roles, wildcard syntax) not mirrored for Linux. The Linux section is less detailed, omitting equivalent scoping or advanced configuration examples. No PowerShell commands are present, but the overall structure and example order favor Windows.
Recommendations
  • Provide equally detailed Linux examples, including any advanced scoping or configuration patterns if available.
  • Describe Linux-specific tools or configuration patterns where relevant, not just Windows-centric ones.
  • Present Windows and Linux examples in parallel or alternate order to avoid implicit prioritization.
  • If Windows-specific syntax (such as server role scoping) is not available for Linux, explicitly state this and discuss Linux alternatives or limitations.
  • Ensure that documentation for both platforms is equally comprehensive in terms of schema explanation and example complexity.
GitHub Create Pull Request
Governance How to create custom machine configuration policy definitions ...chine-configuration/how-to/create-policy-definition.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All code examples use PowerShell and reference Windows-specific paths and services. The 'Platform' parameter is always set to 'Windows' in examples, and there are no Linux-specific examples or references to Linux services, file paths, or shell commands. Windows tools and patterns (e.g., PowerShell cmdlets, Windows service auditing) are used exclusively, with no parity for Linux equivalents.
Recommendations
  • Add Linux-specific examples for creating and publishing machine configuration policies, including setting 'Platform' to 'Linux'.
  • Provide sample code using Linux file paths (e.g., '/home/user/package.zip') and Linux services (e.g., 'sshd', 'cron') in DSC resource definitions.
  • Include instructions and code snippets for using Bash or Azure CLI where appropriate, not just PowerShell.
  • Clarify any differences in managed identity usage or agent versions between Windows and Linux, and provide Linux-focused guidance.
  • Ensure that examples and explanations alternate or equally represent both Windows and Linux scenarios, rather than defaulting to Windows.
GitHub Create Pull Request
Governance How to test machine configuration package artifacts ...ration/how-to/develop-custom-package/3-test-package.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 using PowerShell commands and cmdlets. Windows-specific tools (SysInternals PSExec) are mentioned explicitly, and Windows instructions are consistently presented before Linux equivalents. There is no mention of Linux-native scripting or tooling beyond sudo, and no bash or shell script examples are provided.
Recommendations
  • Provide Linux-first examples or alternate between Windows and Linux in example order.
  • Include bash or shell script equivalents for key operations, where possible.
  • Mention Linux-native tools and patterns for privilege elevation and package management.
  • Clarify PowerShell requirements and alternatives for Linux users who may prefer native shells.
  • Add a section comparing Windows and Linux workflows for testing configuration packages.
GitHub Create Pull Request
Governance How to sign machine configuration packages ...ration/how-to/develop-custom-package/6-sign-package.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting Windows/Powershell examples and instructions before Linux equivalents, relying heavily on Powershell cmdlets and Windows certificate tooling, and referencing Windows-specific certificate stores and Azure templates. Linux instructions are present but less detailed and are introduced after the Windows content.
Recommendations
  • Present Linux and Windows instructions in parallel sections or side-by-side to avoid ordering bias.
  • Expand Linux examples to include more details, such as certificate installation commands and verification steps, similar to the Windows section.
  • Reference Linux-native tools (e.g., openssl for certificate creation) in addition to gpg, and provide guidance for common Linux distributions.
  • Include Azure template examples for Linux, not just Windows.
  • Clarify any differences in prerequisites or environment setup for Linux users.
  • Ensure that all parameters and steps for Linux are as thoroughly documented as for Windows.
GitHub Create Pull Request
Governance Understand Azure Machine Configuration .../articles/governance/machine-configuration/overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
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 additional Linux support via Chef InSpec. The open-source nxtools module is described as a way for PowerShell users to manage Linux, reinforcing PowerShell as the main cross-platform automation tool. Troubleshooting and log collection examples are provided for both Windows (PowerShell) and Linux (Bash), but the overall structure and tool recommendations favor Windows-first approaches and PowerShell-centric workflows. There is limited mention of native Linux configuration management tools (e.g., Ansible, Puppet) and no examples using them.
Recommendations
  • Include examples and references to native Linux configuration management tools (such as Ansible, Puppet, or SaltStack) alongside PowerShell DSC.
  • Provide Linux-first or Linux-native workflow examples, not just PowerShell-based approaches for Linux.
  • Clarify the parity and limitations between PowerShell DSC and Chef InSpec for Linux, and mention when one is preferred over the other.
  • Add troubleshooting and log collection examples using common Linux utilities (e.g., grep, journalctl, systemctl) beyond Bash scripts.
  • Highlight any differences in agent behavior, extension management, or policy assignment between Windows and Linux.
  • Consider including a section on integrating Azure Machine Configuration with existing Linux automation ecosystems.
GitHub Create Pull Request
Governance Azure Machine Configuration prerequisites ...chine-configuration/overview/02-setup-prerequisites.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows tools and patterns (such as PowerShell Desired State Configuration) are mentioned first and in detail, with Linux equivalents described later or less prominently. The validation tools table lists Windows first, and PowerShell DSC is emphasized for both platforms, even though Chef InSpec is available for Linux. References to configuration via the Azure portal often link to Windows VM-specific instructions. There is limited discussion of Linux-native configuration management tools or patterns outside of PowerShell and Chef InSpec.
Recommendations
  • Provide Linux-first or parallel examples for configuration steps, especially for managed identities and extension deployment.
  • Include references and links to Linux-native configuration management tools (e.g., Ansible, Puppet) if supported, or clarify their role.
  • Balance the order of presentation in tables and lists so that Linux is not always listed after Windows.
  • Offer explicit Linux CLI examples (e.g., bash scripts) alongside PowerShell examples.
  • Clarify any differences in extension deployment or management for Linux VMs, including any unique requirements or troubleshooting steps.
GitHub Create Pull Request
Governance How to develop a custom machine configuration package ...onfiguration/how-to/develop-custom-package/overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 focusing on PowerShell Desired State Configuration (DSC) and the GuestConfiguration PowerShell module, with no Linux-specific tooling or examples provided. The instructional video is centered on PowerShell, and there is no mention of Linux-native configuration management tools or workflows. Linux support is referenced only in terms of compatibility, not in practical guidance or examples.
Recommendations
  • Include Linux-specific examples for authoring and validating machine configuration packages, such as using native shell scripts or configuration management tools (e.g., Ansible, Chef, or native DSC for Linux).
  • Provide equivalent step-by-step instructions for Linux environments, including installation and usage of the GuestConfiguration module on Ubuntu and other supported distributions.
  • Add a Linux-focused video or tutorial alongside the PowerShell example to demonstrate parity.
  • Mention Linux command-line tools and workflows where relevant, not just PowerShell.
  • Clarify any differences in package creation, testing, and deployment between Windows and Linux environments.
GitHub Create Pull Request
Governance View Machine Configuration Compliance Reporting ...rnance/machine-configuration/how-to/view-compliance.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 (such as PowerShell cmdlets) and listing them before or alongside cross-platform CLI options. The only explicit example of a platform-specific tool is the PowerShell cmdlet for Guest Configuration assignment retrieval, which is mentioned in the API/programmatic access table. There are no explicit Linux-only examples or tools, and the documentation does not provide parity for Linux-native commands or workflows (e.g., Bash, shell scripts, or Linux-specific management tools). All UI and API instructions are platform-neutral, but the programmatic access section leans toward Windows by highlighting PowerShell.
Recommendations
  • Add Linux-native command examples (e.g., Bash, shell scripts, or Linux management tools) for retrieving compliance data.
  • Provide parity in programmatic access documentation by including Linux-specific workflows, such as using curl with REST APIs or az CLI commands in Bash.
  • When listing tools or references, avoid putting Windows/PowerShell options first; instead, group CLI and REST API options before platform-specific tools.
  • Explicitly mention cross-platform compatibility for all CLI and API tools, and provide usage examples for both Windows and Linux environments.
  • Consider adding a section or note clarifying that all compliance reporting features are available and supported on both Windows and Linux machines.
GitHub Create Pull Request
Governance Planning a change from Desired State Configuration extension to machine configuration ...onfiguration/whats-new/migrating-from-dsc-extension.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 focused on Windows and PowerShell, with examples, tools, and migration steps all centered around Windows environments. There is no mention of Linux-specific DSC extension usage, Linux migration steps, or alternative tools for Linux systems. All commands, configuration references, and compatibility notes are Windows/PowerShell-centric, and the documentation assumes the reader is working with Windows VMs.
Recommendations
  • Add explicit guidance for Linux VMs, including how to check for DSC extension usage and migrate configurations.
  • Provide Linux-specific examples and commands (e.g., Bash, Azure CLI) for verifying extensions and managing configurations.
  • Clarify whether machine configuration supports Linux, and if so, document any differences or limitations.
  • Mention Linux equivalents for concepts like secrets management, configuration packaging, and module paths.
  • Include references to Linux documentation and tools where appropriate, ensuring parity in migration steps and troubleshooting.
GitHub Create Pull Request
Governance Troubleshooting Azure Machine Configuration ...onfiguration/overview/04-operations-troubleshooting.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias. PowerShell is referenced as the primary tool for creating custom machine configuration packages and policies, and the open-source nxtools module is described as a way to make managing Linux systems easier for PowerShell users, implying PowerShell as the default management interface even for Linux. In troubleshooting sections, Windows examples and tools (PowerShell scripts) are presented before Linux equivalents, and several policy definitions are Windows-specific or mention Windows tools (e.g., PowerShell execution policy, PowerShell modules).
Recommendations
  • Provide Linux-native tooling and examples (e.g., Bash, Python) for creating and managing machine configuration packages, not just PowerShell.
  • Ensure Linux troubleshooting examples are presented with equal prominence and detail as Windows examples, and alternate the order to avoid Windows-first bias.
  • Highlight Linux-specific tools and workflows for machine configuration management, not just PowerShell-based approaches.
  • Clarify that PowerShell is optional for Linux management and provide guidance for users who prefer native Linux tools.
  • Expand documentation of policy definitions to include more Linux-focused examples and use cases, especially where Windows-specific tools are referenced.
GitHub Create Pull Request
Governance Azure Automation State Configuration to machine configuration migration planning ...iguration/whats-new/migrating-from-azure-automation.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 by exclusively providing PowerShell-based examples and commands, referencing Windows-centric modules and patterns, and omitting equivalent Linux-specific guidance. While it mentions that DSC resources are available for both Linux and Windows, all practical instructions, troubleshooting, and code samples are focused on PowerShell and Windows tools. Linux users are only briefly mentioned in the context of a filename issue, with no Linux-native workflows or examples provided.
Recommendations
  • Add Linux-specific examples for exporting configurations and modules, using native Linux tools or shell commands where appropriate.
  • Include instructions for managing DSC configurations on Linux machines, such as using OpenSSH, Bash, or cross-platform PowerShell Core.
  • Provide troubleshooting steps and workarounds tailored to Linux environments, not just referencing PowerShell modules.
  • List Linux-compatible DSC resources and modules, and clarify any differences in usage or compatibility.
  • Ensure that examples and workflows are presented in a cross-platform manner, or explicitly note platform-specific steps.
  • Reference Linux documentation and best practices alongside Windows links, giving equal visibility to both platforms.
GitHub Create Pull Request
Governance Quickstart: Create policy assignment with REST API ...n/articles/governance/policy/assign-policy-rest-api.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 primarily referencing PowerShell and Windows-centric tools and patterns. Examples use PowerShell-specific syntax (backtick escaping), and instructions for Bash are only mentioned as alternatives or after PowerShell. There is a lack of explicit Linux shell examples, and tools like Visual Studio Code and Git Bash (Windows-focused) are recommended over native Linux options.
Recommendations
  • Provide explicit Bash/Linux shell examples alongside PowerShell, including correct escaping and file referencing syntax for Linux shells.
  • Mention native Linux terminals (e.g., GNOME Terminal, Konsole) and editors (e.g., Vim, Nano) as alternatives to Visual Studio Code.
  • Reorder instructions so that Linux/Bash examples are presented before or alongside Windows/PowerShell examples, not as an afterthought.
  • Clarify differences in command syntax and escaping between PowerShell and Bash, with dedicated sections or callouts for each.
  • Avoid recommending Git Bash as the primary Bash shell for Linux users; instead, reference standard Linux environments.
  • Ensure that all prerequisites and setup steps are platform-neutral or provide platform-specific guidance for both Windows and Linux.
GitHub Create Pull Request
Governance Learn Azure Policy for Kubernetes ...es/governance/policy/concepts/policy-for-kubernetes.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows tools (Azure portal, Azure CLI, Azure PowerShell) are mentioned and used extensively, often before or instead of Linux-native alternatives. PowerShell commands are provided for resource provider registration, and Azure CLI examples assume use of 'az login', which is more common in Windows environments. There is a lack of explicit Linux shell examples (e.g., bash scripts for resource provider registration), and instructions for installing Azure CLI reference Windows installation before Linux. Additionally, the documentation references Windows-specific domains (login.windows.net) and does not provide parity for Linux users in troubleshooting or setup steps. While the documentation does mention that the Azure Policy Add-on for Kubernetes can only be deployed to Linux node pools, it does not provide Linux-centric guidance or examples where appropriate.
Recommendations
  • Provide Linux-specific instructions and examples alongside Windows/PowerShell ones, especially for resource provider registration and Azure CLI installation.
  • Include bash shell examples for common administrative tasks, such as resource provider registration and troubleshooting.
  • Clarify that Azure CLI and kubectl commands are cross-platform, and provide explicit instructions for Linux environments (e.g., installation via apt, yum, or snap).
  • Avoid referencing Windows domains (login.windows.net) without context; clarify their relevance for Linux users.
  • Add troubleshooting steps and examples that are relevant for Linux environments, such as log file locations, permissions, and process management.
  • Ensure that any references to Azure portal or GUI tools are supplemented with CLI or API alternatives suitable for Linux users.
GitHub Create Pull Request
Governance Get policy compliance data ...ticles/governance/policy/how-to/get-compliance-data.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 examples are provided alongside Azure CLI, but PowerShell is given equal or greater prominence in several sections. Windows-centric tools (PowerShell, Visual Studio Code extension) are described in detail, and PowerShell-specific patterns (jobs, cmdlets) are explained, while Linux-native shells or scripting patterns are not mentioned. There is no explicit mention of Linux shell scripting, nor are Bash or other Linux-specific examples provided. The order of presentation often places PowerShell before CLI, and Windows tools are referenced without Linux alternatives.
Recommendations
  • Add explicit Bash shell scripting examples for REST API calls and Azure CLI usage, demonstrating Linux-native workflows.
  • Include notes or examples for running Azure CLI commands in Linux terminals, highlighting any differences or best practices.
  • When describing PowerShell-specific features (such as jobs), provide equivalent Linux shell backgrounding or process management examples.
  • Mention Linux-native editors (such as Vim, nano, or VS Code on Linux) when referencing the Visual Studio Code extension.
  • Ensure that Azure CLI examples are presented before or alongside PowerShell, and clarify cross-platform compatibility.
  • Reference Linux package management and installation steps for Azure CLI and PowerShell where relevant.
GitHub Create Pull Request
Governance Azure Policy definitions modify effect ...n/articles/governance/policy/concepts/effect-modify.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 alias discovery, without mentioning or providing equivalent CLI or REST API methods. No Linux shell (bash, az CLI) examples or references are provided, and the only tooling guidance is for PowerShell, which is most commonly used on Windows.
Recommendations
  • Add equivalent examples using Azure CLI (az) for alias discovery and policy management.
  • Include REST API methods for listing modifiable aliases, if available.
  • Explicitly mention cross-platform options for policy authoring and management, clarifying that PowerShell is not required.
  • Provide sample commands for both Windows (PowerShell) and Linux/macOS (bash/az CLI) environments.
  • Review all tooling recommendations to ensure Linux parity and avoid implying PowerShell is the only or preferred method.
GitHub Create Pull Request
Governance Design Azure Policy as Code workflows .../articles/governance/policy/concepts/policy-as-code.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 by mentioning PowerShell as a primary export method before CLI, and by not providing explicit Linux shell or cross-platform examples for automation tasks. While Azure CLI is referenced, there are no bash or Linux-specific workflow samples, and PowerShell is listed first when discussing export options. There is also a lack of explicit mention of Linux-native tools or scripting patterns, and no guidance for Linux users on using shell scripts or integrating with Linux-based CI/CD systems.
Recommendations
  • Provide explicit bash or shell script examples alongside PowerShell for exporting and managing policy definitions.
  • Mention Azure CLI and bash scripting as equally valid options for automation, and avoid listing PowerShell first by default.
  • Include references to Linux-based CI/CD systems (e.g., Jenkins, GitLab CI) in addition to GitHub Actions and Azure Pipelines.
  • Add notes or sections on using Linux tools (e.g., jq for JSON manipulation) in policy workflows.
  • Ensure that all automation steps are demonstrated in both Windows and Linux environments, or clarify cross-platform compatibility.
  • Where SDKs or tools are referenced, specify their availability and usage on Linux.
GitHub Create Pull Request
Governance Export Azure Policy resources .../articles/governance/policy/how-to/export-resources.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for exporting Azure Policy resources, but it gives equal prominence to PowerShell, which is primarily a Windows tool. There is no mention of Linux-specific patterns, nor are there examples showing how to use Linux-native tools (e.g., bash, jq) to process or export data. The Resource Graph export references the Azure portal, which is cross-platform, but command-line examples are limited to CLI and PowerShell, with PowerShell listed second but still heavily featured. There are no explicit Linux examples or recommendations for Linux users.
Recommendations
  • Add Linux-specific examples, such as using bash and jq to process Azure CLI output.
  • Explicitly mention that Azure CLI is cross-platform and works natively on Linux and macOS.
  • Provide sample commands for exporting and manipulating policy data using Linux shell tools.
  • Clarify that PowerShell Core is available on Linux, but offer parity by showing bash alternatives.
  • Consider listing Azure CLI examples before PowerShell to emphasize cross-platform usage.
GitHub Create Pull Request
Governance Azure Automanage Best Practices to Azure Policy migration planning ...olicy/how-to/migrate-from-automanage-best-practices.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. Several sections, such as Microsoft Antimalware and Windows Admin Center, focus exclusively on Windows tools and extensions, with no Linux equivalents or examples provided. Windows-specific configuration steps and policies are listed before Linux ones, and some features (e.g., Windows Admin Center) are only available for Windows VMs. There is a lack of parity in examples and guidance for Linux users, especially in areas like antimalware, admin tooling, and extension deployment.
Recommendations
  • Provide equivalent Linux examples and configuration steps wherever Windows-specific instructions are given, especially for antimalware and extension deployment.
  • Explicitly mention Linux alternatives or note if a feature is Windows-only, to clarify platform support.
  • Include Linux-first or cross-platform examples in sections that currently focus on Windows tools (e.g., Windows Admin Center).
  • Balance the order of presentation so that Linux and Windows instructions are given equal prominence.
  • Add guidance or references for managing Linux VMs using Azure-native or third-party tools, where Windows Admin Center is mentioned for Windows.
GitHub Create Pull Request
Governance Programmatically create policies ...es/governance/policy/how-to/programmatically-create.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 prioritizing Windows-centric tools and instructions. PowerShell is featured first and in greater detail, with prerequisite steps focused on Azure PowerShell and Windows installation links. ARMClient, a Windows-oriented tool, is recommended without Linux alternatives. The Azure CLI section references Windows installation first and does not provide explicit Linux/macOS installation guidance. There are no Linux-specific examples, shell commands, or notes on cross-platform usage, and PowerShell commands are used to obtain information even in CLI sections.
Recommendations
  • Add explicit instructions and examples for Linux and macOS environments, including installation links for Azure CLI and PowerShell on those platforms.
  • Include bash/zsh shell command examples alongside PowerShell, especially for resource group and policy management.
  • Mention cross-platform compatibility for ARMClient or suggest alternative tools (e.g., curl, httpie) that are native to Linux/macOS.
  • Reorder sections to present Azure CLI and REST API examples before PowerShell to avoid Windows-first perception.
  • Clarify that all tools (Azure CLI, PowerShell) are available on Linux/macOS and provide relevant links.
  • Avoid using PowerShell commands in CLI-focused sections; use CLI-native commands to retrieve information.
GitHub Create Pull Request
Governance List of built-in packages for guest configuration ...rticles/governance/policy/samples/built-in-packages.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 majority of policy definitions and examples are Windows-specific, with only a handful of Linux policies present. PowerShell Desired State Configuration (DSC) modules are referenced throughout, which are primarily Windows-centric tools. Windows tools and concepts (such as Windows Defender, PowerShell execution policy, domain membership, and time zone configuration) are mentioned exclusively or before any Linux equivalents. Linux coverage is minimal and often marked as 'Preview', with fewer examples and less detail.
Recommendations
  • Increase the number and detail of Linux-specific policy definitions and examples.
  • Provide parity in documentation for Linux tools and modules, including links and explanations similar to those given for Windows/PowerShell.
  • Avoid presenting Windows policies and tools first; consider grouping by OS or alternating examples.
  • Expand explanations to clarify how guest configuration works on Linux, including references to Linux-native configuration management tools (e.g., Ansible, Chef, or native shell scripts) if supported.
  • Ensure that for every Windows-specific example, a Linux equivalent is provided where possible.
  • Remove or balance language that implies Windows is the primary or default platform.
GitHub Create Pull Request
Governance Remediate non-compliant resources ...ticles/governance/policy/how-to/remediate-resources.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are consistently presented before Azure CLI, and in greater detail, with more comprehensive code samples and explanations. The structure of the documentation often places PowerShell (a Windows-centric tool) before cross-platform alternatives. There are also more elaborate step-by-step instructions and troubleshooting for PowerShell, while Azure CLI (the more cross-platform tool) receives less detailed coverage. No Linux-specific tools or shell examples (e.g., Bash) are provided, and the documentation does not mention or address Linux environments explicitly.
Recommendations
  • Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI examples first in some sections to avoid reinforcing a Windows-first perspective.
  • Ensure that Azure CLI examples are as detailed and comprehensive as PowerShell examples, including step-by-step instructions and troubleshooting notes.
  • Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS), and provide Bash shell examples where appropriate.
  • Where PowerShell-specific notes are given (e.g., about Cloud Shell or login), provide equivalent notes for Bash/Azure CLI users.
  • Consider adding a brief section or callout for Linux/macOS users, clarifying that all Azure CLI steps are fully supported on those platforms.
  • If possible, include screenshots or terminal output from Linux/macOS environments to visually reinforce cross-platform support.
GitHub Create Pull Request
← Previous Page 5 of 25 Next →