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 26-50 of 613 flagged pages
Governance Deploy ISO 27001 Shared Services blueprint sample ...overnance/blueprints/samples/iso27001-shared/deploy.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 in several ways. Windows operating system is set as the default for the jumpbox VM, and Windows VM examples are listed alongside Linux but often appear first or with more detail. The artifact parameters table includes separate entries for deploying Log Analytics Agents to Windows and Linux VMs, but the jumpbox and Active Directory sections default to Windows-centric patterns (e.g., Windows OS, Active Directory Domain Services). There are no explicit Linux-based alternatives or examples for jumpbox or domain services, and no mention of Linux-native identity or management solutions.
Recommendations
  • Provide Linux-first or Linux-equal examples for jumpbox deployment, including setting the default OS to Linux or showing both options equally.
  • Include guidance or references for deploying Linux-based identity management solutions (e.g., LDAP, FreeIPA) as alternatives to Active Directory Domain Services.
  • Ensure artifact parameters and deployment steps mention Linux options wherever Windows is mentioned, especially for VM OS selection and management.
  • Add explicit Linux deployment walkthroughs or screenshots alongside Windows-centric UI instructions.
  • Clarify that both Windows and Linux are supported for all relevant artifacts, and provide links to Linux-specific documentation where available.
GitHub Create Pull Request
Governance Deploy SWIFT CSP-CSCF v2020 blueprint sample ...les/governance/blueprints/samples/swift-2020/deploy.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways. Windows-specific concepts (e.g., Windows VM Administrators group, domain join for Windows VMs) are mentioned explicitly, while Linux equivalents (such as sudoers or Linux domain join) are absent. Windows-related artifact parameters appear before Linux ones in the artifact table, and examples or explanations for Linux are minimal or missing. No Linux-specific administrative group or domain join instructions are provided, and the overall flow assumes familiarity with Windows management patterns.
Recommendations
  • Add Linux-specific examples and explanations, such as how to manage Linux VM administrator groups (e.g., sudoers or wheel group) and domain join equivalents (e.g., Azure AD Join for Linux, or integration with LDAP/SSSD).
  • Ensure Linux-related artifact parameters are presented with equal prominence and detail as Windows ones, including administrative group management and security controls.
  • Provide parity in instructions for both Windows and Linux VM management, including explicit mention of Linux tools, patterns, and configuration steps.
  • Consider reordering artifact tables or sections so that Linux and Windows examples alternate or are grouped together for easy comparison.
  • Include links to Linux-specific documentation where appropriate, such as managing identities, logging, and security on Linux VMs in Azure.
GitHub Create Pull Request
Governance Remediation options for machine configuration .../machine-configuration/concepts/remediation-options.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through its reliance on PowerShell DSC concepts (Test/Set methods), references to PowerShell documentation, and lack of explicit Linux examples or mention of Linux-specific tools. The terminology and linked resources (such as DSC resource documentation) are Windows-centric, and there is no discussion of how remediation works on Linux VMs or with Linux configuration management tools.
Recommendations
  • Include explicit examples and explanations for Linux VM remediation, such as how machine configuration interacts with Linux configuration management (e.g., shell scripts, Ansible, or native Linux DSC support).
  • Reference Linux-specific documentation and tools alongside PowerShell/DSC links, ensuring parity in guidance.
  • Clarify whether concepts like Test/Set methods are applicable to Linux, and if not, describe the Linux equivalents.
  • Add cross-platform notes or tables indicating differences in remediation behavior or supported features between Windows and Linux.
  • Provide sample policy definitions or remediation workflows for Linux environments.
GitHub Create Pull Request
Governance [Azure CLI](#tab/azure-cli) ...ce/includes/policy/azure-policy-guest-configuration.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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. Most queries and examples are generic, but the only explicit OS-specific scenario is 'WindowsPendingReboot', with no equivalent Linux example (e.g., 'LinuxPendingReboot'). Windows terminology and resource names are used exclusively or first, and there is no parity for Linux-specific guest configuration queries. Additionally, while Azure CLI and PowerShell are both cross-platform, PowerShell is traditionally associated with Windows, and its inclusion without Linux shell examples (e.g., Bash, shell scripting) further reinforces the bias.
Recommendations
  • Add Linux-specific examples for scenarios such as pending reboot (e.g., 'LinuxPendingReboot').
  • Ensure parity by providing both Windows and Linux resource queries where applicable.
  • Include Linux shell (Bash) command examples for Azure CLI usage to demonstrate cross-platform applicability.
  • Clarify in documentation that PowerShell examples are cross-platform, or provide alternative Linux-native scripting examples.
  • Review resource naming and ensure that Linux resources are mentioned and queried with equal prominence as Windows resources.
GitHub Create Pull Request
Governance How to create a machine configuration assignment using an Azure Resource Manager template .../how-to/assign-configuration/azure-resource-manager.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by providing only Windows-centric configuration examples, specifically referencing the 'AzureWindowsBaseline' built-in configuration and password policies typical of Windows environments. There are no examples or references to Linux configurations, built-in Linux baselines, or Linux-specific parameters. Additionally, the link to the ARM template tutorial defaults to Azure PowerShell, which is more commonly used on Windows.
Recommendations
  • Include examples of assigning built-in Linux configurations, such as 'AzureLinuxBaseline', alongside Windows examples.
  • Provide sample configuration parameters relevant to Linux systems (e.g., SSH settings, file permissions, etc.).
  • Ensure documentation links offer parity for Linux users, such as Bash/CLI tabs and instructions.
  • Explicitly mention Linux support and provide guidance for Linux-specific scenarios in the text.
  • Avoid using Windows-centric terminology or examples exclusively; strive for balanced representation.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. Windows-specific scoping patterns (e.g., 'WindowsServer\<Year>\<Role>') are described in detail before Linux equivalents, and the Windows example is more complex and feature-rich. Linux examples are simpler and lack parity in scoping or advanced configuration. Windows terminology and patterns (e.g., 'WindowsServer', 'DomainController') are mentioned explicitly, while Linux is described generically and without equivalent advanced features.
Recommendations
  • Provide Linux examples with advanced scoping or role-based configuration, if supported, to match the Windows example's complexity.
  • Describe any Linux-specific patterns or conventions for rule targeting, similar to the WindowsServer\<Year>\<Role> pattern.
  • Ensure that Linux and Windows examples are presented with equal detail and order (e.g., alternate which comes first, or present both side-by-side).
  • Explicitly mention any limitations or differences in Linux baseline configuration compared to Windows, so users understand feature parity.
  • If Linux does not support certain advanced features, clarify this explicitly rather than omitting detail.
GitHub Create Pull Request
Governance How to create custom machine configuration package artifacts ...tion/how-to/develop-custom-package/2-create-package.md
High Priority View Details →
Scanned: 2026-01-11 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 is heavily PowerShell-centric, with all examples and tooling instructions using PowerShell commands and modules. Windows-specific paths, outputs, and tools (such as PSDscResources and Windows file paths) are shown first and in more detail. Linux examples are present but less detailed, and there are no examples using native Linux tools or shell commands. The packaging and inspection steps use Windows-centric PowerShell commands, with no Linux alternatives provided.
Recommendations
  • Provide equivalent Linux-native examples using Bash or shell commands for compiling, packaging, and inspecting configuration artifacts (e.g., using zip, unzip, ls, du).
  • Include Linux file paths and outputs alongside Windows examples to illustrate cross-platform parity.
  • Mention and demonstrate Linux-specific DSC resources and modules in more detail, not just referencing external articles.
  • Clarify how Linux users can perform each step without PowerShell, or explicitly state PowerShell is required on Linux and provide installation guidance.
  • Balance the order of presentation so that Linux examples and considerations are given equal prominence to Windows.
GitHub Create Pull Request
Governance Discover And Assign Built In Machine Configuration Policies ...chine-configuration/how-to/assign-built-in-policies.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by providing a detailed example only for a Windows policy ('Audit Windows Time Zone'), with no equivalent Linux example. Windows policies and terminology are introduced before Linux ones in lists and examples. Programmatic automation references PowerShell prominently, while Linux-native tools and shell scripting are not discussed. Although Linux policies are mentioned, practical guidance and examples for Linux are missing.
Recommendations
  • Add a step-by-step example for assigning a Linux-specific Machine Configuration policy (e.g., 'Audit Linux machines that have the specified applications installed'), including screenshots and parameter explanations.
  • Ensure lists and examples alternate or balance Windows and Linux policies, rather than presenting Windows first.
  • Include Linux-native automation examples, such as using Bash with Azure CLI, and reference Linux shell scripting where appropriate.
  • Highlight any differences or considerations for Linux environments in prerequisites and compliance reporting.
  • Review and update screenshots to include Linux policy assignment flows.
GitHub Create Pull Request
Governance How to create a machine configuration assignment using Terraform ...configuration/how-to/assign-configuration/terraform.md
High Priority View Details →
Scanned: 2026-01-11 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. There are no examples or mentions of Linux virtual machines, Linux configuration baselines, or Linux-specific tools. The link to the getting started guide is Windows PowerShell-focused, further reinforcing the Windows bias.
Recommendations
  • Add equivalent examples for azurerm_linux_virtual_machine, showing how to assign configurations to Linux VMs.
  • Include built-in Linux configuration assignment examples (e.g., AzureLinuxBaseline) if available.
  • Reference Linux-specific getting started guides and tools alongside Windows resources.
  • Clarify in the introduction that both Windows and Linux are supported (if true), and provide parity in documentation structure and examples.
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-11 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. All code examples use PowerShell and reference Windows-specific paths (e.g., C:\Local\Path\To\Package). The 'Platform' parameter is always set to 'Windows' in examples, and Windows services are referenced in parameter examples. There are no Linux-specific examples, commands, or references to Linux service management, nor are Linux file paths or tools shown. The documentation assumes the use of Windows tools and patterns throughout, with Linux only mentioned in passing (e.g., version requirements).
Recommendations
  • Include Linux-specific examples for all major steps, such as using Bash or Azure CLI instead of PowerShell, and referencing Linux file paths (e.g., /home/user/package.zip).
  • Demonstrate policy definitions targeting Linux, with 'Platform' set to 'Linux', and use Linux service names and management patterns in parameter examples.
  • Provide guidance for setting up the authoring environment on Linux, including installation of required modules and dependencies.
  • Reference Linux equivalents for Windows-specific cmdlets and tools, or clarify cross-platform compatibility where appropriate.
  • Ensure that both Windows and Linux scenarios are covered equally in all example sections, including managed identity usage and storage access patterns.
GitHub Create Pull Request
Governance How to access custom machine configuration package artifacts ...tion/how-to/develop-custom-package/5-access-package.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by exclusively providing PowerShell examples for generating SAS tokens and referencing Azure PowerShell cmdlets. There are no equivalent examples for Linux environments (such as Bash/CLI), nor is there mention of cross-platform tools or commands. This may hinder Linux users or those working in heterogeneous environments from easily following the guide.
Recommendations
  • Add equivalent Bash/Azure CLI examples for generating SAS tokens and accessing blobs.
  • Explicitly mention that the steps can be performed on Linux and macOS, not just Windows.
  • Reference cross-platform tools (e.g., az CLI) alongside PowerShell, and provide links to their documentation.
  • Clarify any platform-specific requirements or differences, ensuring parity in instructions for both Windows and Linux users.
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-11 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 demonstrates a Windows bias by presenting Windows/Powershell examples first, using Windows-specific tools and cmdlets (e.g., New-SelfSignedCertificate, Export-Certificate, Import-PfxCertificate), and providing more detailed step-by-step instructions for Windows than for Linux. The Linux section is shorter, uses generic GPG commands, and lacks parity in guidance for certificate management and integration with Azure Policy. Additionally, certificate export and installation examples are only shown for Windows, with no equivalent Linux example.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate their order to avoid Windows-first bias.
  • Expand Linux instructions to match the detail level of Windows, including step-by-step guidance for certificate creation, export, and installation.
  • Provide Linux-specific examples for exporting and installing public keys, including commands for placing certificates in /usr/local/share/ca-certificates/gc and updating CA trust.
  • Include Linux equivalents for Azure Policy integration and certificate deployment, referencing relevant templates or scripts.
  • Use cross-platform language and tools where possible, and clarify when a step is OS-specific.
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-11 00:00
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 through the inclusion and prioritization of Windows-centric tools and examples. The only named command-line example for programmatic access is a PowerShell cmdlet (Get-AzGuestConfigurationAssignment), and Windows/PowerShell tooling is referenced before or in addition to Linux equivalents. There is no explicit Linux shell (bash) or Linux-specific example, and the documentation references Windows tools (PowerShell) without providing parity for Linux users.
Recommendations
  • Include Linux shell (bash) and CLI examples alongside PowerShell cmdlets, such as az guestconfig and az policy commands.
  • Explicitly mention Linux compatibility and provide guidance for Linux users where Windows/PowerShell tools are referenced.
  • Add sample queries or automation scripts using bash, Python, or other cross-platform tools to demonstrate Linux parity.
  • Ensure documentation references both Windows and Linux tools in parallel, rather than prioritizing Windows/PowerShell examples.
GitHub Create Pull Request
Governance Understand Azure Machine Configuration .../articles/governance/machine-configuration/overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits 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 for Linux management but is PowerShell-centric. Troubleshooting and log collection instructions are provided for both platforms, but the Windows PowerShell example appears first. References to Azure portal and PowerShell are frequent, and links for managed identity configuration point to Windows-specific guides. Overall, Windows tools and patterns are emphasized, and PowerShell is positioned as the main cross-platform solution, potentially sidelining native Linux tools and workflows.
Recommendations
  • Provide examples using native Linux configuration management tools (e.g., Ansible, Bash scripts) alongside PowerShell DSC.
  • Include troubleshooting and log collection instructions using standard Linux utilities (e.g., grep, journalctl) before or alongside PowerShell-based methods.
  • Offer parity in documentation links, ensuring Linux-specific guides (e.g., configuring managed identities on Linux VMs) are referenced equally.
  • Clarify the role and limitations of PowerShell DSC on Linux, and mention alternatives where appropriate.
  • Highlight Chef InSpec and other Linux-native validation tools more prominently, and consider listing them before or alongside PowerShell DSC for Linux.
  • Expand the discussion of open-source modules to include non-PowerShell options for Linux management.
GitHub Create Pull Request
Governance Azure Machine Configuration prerequisites ...chine-configuration/overview/02-setup-prerequisites.md
High Priority View Details →
Scanned: 2026-01-11 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 terminology and tools (PowerShell DSC) are mentioned first and more prominently, with Linux equivalents (Chef InSpec, PowerShell DSC v3) listed after. The instructions and links for configuring managed identities reference Windows VM examples, and validation tooling for Linux is less detailed. There is a general assumption of familiarity with Windows-centric patterns and tools.
Recommendations
  • Provide Linux-first or parallel examples for key configuration steps, such as managed identity setup and extension deployment.
  • Include explicit instructions and links for configuring managed identities on Linux VMs, not just Windows.
  • Balance the order of tool presentation in tables and text, listing Linux and Windows tools together or alternating which comes first.
  • Expand details on Linux validation tools, including troubleshooting and operational notes.
  • Add more references to Linux-specific documentation, such as Azure CLI usage for Linux environments.
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-11 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 Windows bias by focusing on PowerShell Desired State Configuration (PSDSC) and the GuestConfiguration PowerShell module, with no equivalent Linux-specific tooling or examples provided. The instructional video and module references are PowerShell-centric, and Linux support is mentioned only in terms of compatibility, not in terms of authoring or usage examples. There are no Linux command-line examples, nor is there guidance for Linux-native configuration authoring workflows.
Recommendations
  • Include Linux-specific examples for authoring and validating machine configuration packages, using native Linux tools and workflows (e.g., Bash, shell scripts, or Ansible).
  • Provide parity in documentation by offering step-by-step guides for Linux environments, not just PowerShell.
  • Reference and link to Linux-native configuration management tools where appropriate, or clarify how PSDSC concepts map to Linux equivalents.
  • Add video or written tutorials demonstrating the process on Linux systems, including Ubuntu and other supported distributions.
  • Explicitly state any differences in authoring, testing, and deploying packages on Linux versus Windows.
GitHub Create Pull Request
Governance Troubleshooting Azure Machine Configuration ...onfiguration/overview/04-operations-troubleshooting.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 policies and troubleshooting, even for Linux scenarios. Windows examples and tools (such as PowerShell modules and scripts) are mentioned first or exclusively in several sections. The open-source nxtools module is highlighted as a way for PowerShell users to manage Linux, reinforcing PowerShell as the preferred cross-platform automation method. While Linux examples are present, they often appear after Windows examples and rely on Windows-centric tooling.
Recommendations
  • Provide equivalent Linux-native tooling and examples (e.g., Bash, Python, Ansible) for creating and managing machine configuration packages, not just PowerShell.
  • Avoid presenting Windows examples or tools first; alternate or parallelize Windows and Linux instructions.
  • Highlight Linux-native management options (such as native systemd, shell scripts, or configuration management tools) alongside PowerShell-based solutions.
  • Clarify that PowerShell is optional for Linux users and provide guidance for those who prefer not to use it.
  • Expand troubleshooting and log collection sections to include more Linux-specific diagnostic commands and workflows.
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-11 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, primarily through exclusive use of PowerShell-based examples and tooling, with all code samples and module management instructions centered around PowerShell and Azure PowerShell modules. Windows-specific patterns (such as MOF compilation and module compatibility workarounds) are discussed in detail, while Linux equivalents are either omitted or mentioned only in passing. Troubleshooting and export instructions for Linux/macOS are minimal and relegated to a workaround, rather than being integrated into the main workflow.
Recommendations
  • Provide equivalent Linux/bash examples for exporting configurations and managing modules, using native Linux tools where possible.
  • Include instructions for using cross-platform PowerShell Core (pwsh) on Linux, and clarify any differences in behavior or compatibility.
  • Discuss Linux-specific DSC resources and modules, with examples of how to migrate and test them.
  • Address common Linux migration issues (such as file permissions, path formats, and module compatibility) in dedicated troubleshooting sections.
  • Ensure that all steps and workflows are presented in a cross-platform manner, with clear notes on OS-specific differences.
  • Highlight Linux onboarding and management scenarios (e.g., onboarding Linux hybrid machines to Azure Arc) with step-by-step guidance.
GitHub Create Pull Request
Governance Azure machine configuration agent release notes ...es/governance/machine-configuration/whats-new/agent.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page presents Windows release notes before Linux, and in the example for updating the Linux extension, PowerShell is used first, followed by Azure CLI. There are no Linux-native command examples (e.g., Bash or shell scripts), and the documentation does not mention Linux-specific tools or patterns for extension management, relying instead on cross-platform Azure CLI and PowerShell. This ordering and example choice may subtly reinforce a Windows-centric perspective.
Recommendations
  • Present Linux and Windows sections in parallel or alternate their order between releases to avoid implicit prioritization.
  • Provide Linux-native command examples (e.g., Bash scripts using az CLI, or instructions for using package managers where relevant).
  • Include Linux-specific troubleshooting steps and tools (such as systemctl, journalctl, or log file paths) where appropriate.
  • Clarify that PowerShell and Azure CLI are cross-platform, but also offer native alternatives for Linux users.
  • Ensure that any configuration file paths or environment variables are explained for both platforms, highlighting differences.
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-11 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 primarily providing PowerShell-specific syntax and guidance, referencing Windows tools (PowerShell, Visual Studio Code) first, and only briefly mentioning Bash shells (like Git Bash) as alternatives. There are no explicit Linux-native shell examples (e.g., Ubuntu bash, macOS Terminal), and escape character explanations are focused on PowerShell, with limited coverage for Bash. The prerequisites and workflow assume a Windows-centric environment.
Recommendations
  • Provide explicit Linux/macOS shell examples, including native bash syntax for all commands.
  • Clarify escape character usage for both PowerShell and bash (Linux/macOS), with side-by-side examples.
  • List prerequisites for Linux/macOS environments (e.g., native bash, gedit, nano, or VS Code alternatives) alongside Windows tools.
  • Avoid referencing Windows tools (PowerShell, Visual Studio Code) first; present cross-platform options equally.
  • Add notes or sections for running commands in Linux/macOS terminals, including any differences in file handling or command syntax.
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-11 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 mention and example of Azure PowerShell for listing modifiable policy aliases, with no equivalent CLI or Linux-native example. The only tooling guidance is for PowerShell, and there is no mention of Bash, Azure CLI, or cross-platform alternatives. This may disadvantage users on Linux or macOS, or those who prefer non-Windows tooling.
Recommendations
  • Provide equivalent Azure CLI (az) commands for listing modifiable policy aliases, alongside PowerShell examples.
  • Explicitly mention cross-platform tools and scripting options (e.g., Bash, Azure CLI) where PowerShell is referenced.
  • Ensure that all code/tooling examples are available for both Windows and Linux environments.
  • Add a note clarifying that Azure Policy management can be performed from any OS, and link to cross-platform tool documentation.
  • Where possible, avoid referencing Windows-specific resource properties (e.g., osProfile.windowsConfiguration) without also mentioning Linux equivalents (e.g., osProfile.linuxConfiguration) in examples.
GitHub Create Pull Request
Governance Details of the initiative definition structure ...nce/policy/concepts/initiative-definition-structure.md
High Priority View Details →
Scanned: 2026-01-11 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. The only explicit tooling mentioned for resource type discovery is 'Get-AzResourceProvider', a PowerShell cmdlet, with no Linux or cross-platform alternatives (such as Azure CLI or REST API) referenced. This places Windows/PowerShell tooling first and exclusively in that context. No Linux-specific examples or tools are provided, and the documentation does not mention cross-platform alternatives where relevant.
Recommendations
  • Where PowerShell cmdlets are referenced (e.g., Get-AzResourceProvider), also provide equivalent Azure CLI commands (e.g., 'az provider list') and/or REST API calls.
  • Explicitly state that Azure Policy definitions and initiative management can be performed using cross-platform tools such as Azure CLI, REST API, and SDKs, not just PowerShell.
  • Add example commands for Linux/macOS users using Azure CLI where relevant, especially in sections discussing resource discovery or assignment.
  • Review all references to tooling and ensure parity between Windows/PowerShell and Linux/Azure CLI usage patterns.
  • Consider a short section or note on cross-platform support for Azure Policy management, including links to CLI and REST documentation.
GitHub Create Pull Request
Governance Tutorial: Create a custom policy definition ...ce/policy/tutorials/create-custom-policy-definition.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by presenting Azure PowerShell examples alongside Azure CLI, mentioning PowerShell explicitly, and referencing Windows-centric tools and patterns (such as VS Code extension and Azure portal) without providing Linux-specific alternatives or parity. The order of examples and tool mentions often places Windows/PowerShell first or equally, but never gives Linux-specific shell or scripting examples. There is no mention of Linux-native tools, nor are there bash or shell script equivalents for tasks such as finding aliases or managing policies.
Recommendations
  • Add explicit bash/shell script examples for Azure CLI commands, demonstrating usage in Linux environments.
  • Clarify that Azure CLI is cross-platform and provide Linux-specific installation or usage notes where appropriate.
  • Include references to Linux-native editors (such as Vim, nano, or Emacs) for viewing and editing JSON policy definitions, in addition to VS Code.
  • Mention that Azure CLI commands can be run in Linux terminals and provide screenshots or instructions for Linux environments.
  • If referencing Azure PowerShell, clarify its cross-platform support and provide installation instructions for Linux.
  • Consider the order of tool presentation: present Azure CLI and Linux-native approaches before or alongside PowerShell and Windows-centric tools.
  • Add a section or callout for Linux users, summarizing the workflow and toolset for policy definition and assignment on Linux.
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-11 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 subtle Windows bias by mentioning PowerShell as a primary export method for policy and initiative definitions before CLI or Azure Resource Graph, and by not providing explicit Linux shell (bash) or cross-platform CLI examples. The absence of Linux-specific or cross-platform command examples and tools may make it less accessible for users working in Linux environments.
Recommendations
  • Provide explicit bash/Azure CLI examples alongside PowerShell for exporting and managing policy resources.
  • When listing export methods, mention CLI and Azure Resource Graph before or alongside PowerShell to avoid Windows-first ordering.
  • Include references to Linux-compatible automation tools and workflows (e.g., bash scripts, cross-platform CI/CD runners) in addition to GitHub workflows and Azure Pipelines.
  • Clarify that all steps and tools are cross-platform where possible, and highlight any platform-specific caveats.
  • Add a section or note on best practices for Linux environments, including shell scripting and integration with Linux-based CI/CD systems.
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-11 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 moderate Windows bias. Azure CLI and Azure portal instructions are provided throughout, but Azure PowerShell is mentioned as an alternative for resource provider registration, and Windows-specific domains (login.windows.net) are referenced. The documentation refers to Azure portal navigation patterns (which are more familiar to Windows users), and PowerShell is mentioned before Linux-native alternatives. There is a lack of explicit Linux shell examples for some administrative tasks (e.g., resource provider registration), and Windows terminology (e.g., 'login.windows.net') is used without Linux equivalents or context. However, the core Kubernetes operations (kubectl, helm) are platform-neutral and the add-on itself is Linux-only, which is clearly stated in the limitations.
Recommendations
  • Provide bash and Linux shell equivalents for all PowerShell commands and administrative tasks, especially for resource provider registration.
  • Clarify that Azure CLI and kubectl commands are cross-platform and provide explicit instructions for Linux and macOS users where relevant.
  • Avoid using Windows-centric terminology (such as 'login.windows.net') without context; explain its relevance for all platforms.
  • Ensure that portal navigation instructions are supplemented with CLI alternatives for users who prefer non-GUI workflows.
  • Explicitly state when features or instructions are Windows-only, and provide Linux alternatives or clarifications.
  • Add a section summarizing platform support and parity, including any differences in experience for Linux, macOS, and Windows users.
GitHub Create Pull Request
← Previous Page 2 of 25 Next →