Governance

496
Total Pages
410
Linux-Friendly Pages
86
Pages with Bias
17.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

186 issues found
Showing 101-125 of 186 flagged pages
Governance Troubleshoot common errors for Azure Resource Graph ...cles/governance/resource-graph/troubleshoot/general.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a detailed PowerShell example for batching subscription queries, but does not offer equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or Python SDK). The resolution section refers specifically to PowerShell, and Windows tools are implicitly prioritized, creating friction for users on non-Windows platforms.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for batching subscription queries.
  • Include cross-platform SDK examples (e.g., Python, .NET) where relevant.
  • Explicitly mention that the guidance applies to all platforms and provide links to Linux/macOS-specific documentation.
  • Reorder examples so that Windows and Linux/macOS solutions are presented with equal prominence.
GitHub Create Pull Request
Governance Quickstart: Create a blueprint with REST API ...les/governance/blueprints/create-blueprint-rest-api.md
Medium 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 provides only PowerShell examples for making REST API calls, with no mention of Linux/macOS alternatives such as curl, httpie, or bash scripting. Windows/PowerShell tooling is recommended first and exclusively, creating friction for users on non-Windows platforms.
Recommendations
  • Add equivalent examples using curl and/or httpie for Linux/macOS users.
  • Mention cross-platform tools (e.g., Azure CLI, ARMClient, REST clients) and clarify which are available on all OSes.
  • Reorder or parallelize examples so Linux/macOS methods are shown alongside PowerShell.
  • Explicitly state that REST API calls can be made from any OS and provide generic HTTP request examples.
GitHub Create Pull Request
Governance Canada Federal PBMM blueprint sample ...s/governance/blueprints/samples/canada-federal-pbmm.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides examples and parameters for both Windows and Linux VM deployments, but Windows-specific concepts (such as the 'Administrators group' and 'List of users that should be included in Windows VM Administrators group') are described in detail, while equivalent Linux user/group management is not mentioned. Windows VM examples and terminology appear before or in greater detail than Linux equivalents. There are no Linux-specific instructions or examples for managing users/groups or VM extensions, and the artifact parameters table includes Windows-specific details without Linux parity.
Recommendations
  • Add explicit Linux user/group management examples and parameters, such as instructions for configuring sudoers or local groups on Linux VMs.
  • Ensure that Linux VM extension deployment and audit requirements are described with the same level of detail as Windows.
  • Present Linux and Windows examples in parallel, or alternate which is shown first, to avoid implicit prioritization.
  • Clarify any differences in artifact deployment or configuration between Windows and Linux VMs, especially for audit and security controls.
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
Medium 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 exhibits Windows bias primarily by referencing the PowerShell Get-AzAccessToken cmdlet as the only method for obtaining an Azure access token, without mentioning Linux/macOS alternatives (such as Azure CLI or environment variables). The only explicit tooling example for authentication is Windows-centric, and the link to Get-AzAccessToken is provided before any mention of cross-platform options. However, the main example for making the API call uses curl, which is cross-platform.
Recommendations
  • Include instructions for obtaining an Azure access token using Azure CLI (az account get-access-token), which works on Linux/macOS/Windows.
  • Mention environment variable approaches or other cross-platform authentication methods.
  • Present both PowerShell and Azure CLI examples side-by-side, or reference Azure CLI first.
  • Clarify that curl is available on all platforms and provide installation tips for Windows users if needed.
GitHub Create Pull Request
Governance How to create a machine configuration assignment using Terraform ...configuration/how-to/assign-configuration/terraform.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively demonstrates machine configuration assignment for Windows virtual machines, referencing only azurerm_windows_virtual_machine resources and built-in Windows configurations. There are no examples, instructions, or references for Linux virtual machines or Linux-specific configurations, which may leave Linux users without guidance.
Recommendations
  • Add parallel examples for azurerm_linux_virtual_machine resources showing how to assign configurations to Linux VMs.
  • Include built-in Linux configuration assignment examples (e.g., CIS Linux Baseline) if available.
  • Reference Linux/macOS Terraform getting started guides alongside the Windows/Powershell guide.
  • Clarify in the introduction whether the process applies to both Windows and Linux, or specify any limitations.
GitHub Create Pull Request
Governance How to create custom machine configuration policy definitions ...chine-configuration/how-to/create-policy-definition.md
Medium 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 PowerShell and Windows-specific examples, with all code samples using PowerShell syntax and Windows file paths. The 'Platform' parameter is always set to 'Windows' in examples, and there are no equivalent Linux/macOS shell or file path examples. Windows tools and patterns (e.g., PowerShell cmdlets, C:\ paths) are used exclusively, and Linux is only mentioned in passing (e.g., required agent version), without actionable guidance or parity in examples.
Recommendations
  • Provide Linux/macOS-specific examples using Bash or Azure CLI, especially for steps like setting variables, uploading packages, and creating policy definitions.
  • Show examples where the 'Platform' parameter is set to 'Linux', with relevant Linux file paths (e.g., /home/user/package.zip) and context.
  • Include guidance for installing required modules and setting up the authoring environment on Linux/macOS, not just Windows.
  • Where PowerShell is required, clarify cross-platform usage and provide instructions for installing PowerShell on Linux/macOS.
  • Add notes or sections highlighting differences or additional steps for Linux/macOS users, including troubleshooting tips.
GitHub Create Pull Request
Governance How to create custom machine configuration package artifacts ...tion/how-to/develop-custom-package/2-create-package.md
Medium 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 is heavily PowerShell-centric, with most examples and tooling instructions using PowerShell commands and Windows paths. Windows examples and tools are presented first and in greater detail, while Linux-specific guidance is minimal and often deferred to external articles. There is a lack of Linux/macOS shell examples, and some steps (like file path outputs and packaging commands) are shown only with Windows conventions.
Recommendations
  • Provide equivalent Linux/macOS shell (bash) examples for compiling, renaming, and packaging configuration files.
  • Show Linux file paths and outputs alongside Windows examples (e.g., /home/user/dsc/MyConfig instead of only C:\dsc\MyConfig).
  • Clarify how to use PowerShell on Linux/macOS, or offer native shell alternatives for common tasks (e.g., using mv instead of Rename-Item).
  • Include a full Linux configuration authoring and packaging walkthrough, not just a reference to another article.
  • Explicitly state any platform limitations for each step, and provide workarounds or alternatives where possible.
GitHub Create Pull Request
Governance How to develop a custom machine configuration package ...onfiguration/how-to/develop-custom-package/overview.md
Medium 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 primarily on PowerShell tooling (GuestConfiguration PowerShell module) and referencing Windows-centric technologies (PowerShell DSC) without providing equivalent Linux-specific examples or workflows. The instructional video and module links are PowerShell-focused, and Linux support is mentioned only in limitations or as an afterthought. There are no concrete Linux command-line examples, nor is there guidance for Linux-native tooling or workflows.
Recommendations
  • Add Linux-specific examples and workflows for authoring, testing, and publishing machine configuration packages, using native Linux tools where possible.
  • Provide equivalent instructions for Linux environments, such as using Bash, shell scripts, or Linux package management tools.
  • Include a Linux-focused video or tutorial demonstrating the process on Ubuntu or other supported distributions.
  • Clarify any differences in steps or requirements for Linux users, and ensure parity in documentation structure and detail.
  • Reference Linux documentation and modules/tools explicitly, not just as limitations.
GitHub Create Pull Request
Governance Troubleshooting Azure Machine Configuration ...onfiguration/overview/04-operations-troubleshooting.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
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 is referenced as the primary tool for creating custom machine configuration packages, and the open-source nxtools module is described as a way to make Linux management easier for PowerShell users, reinforcing PowerShell as the main automation pattern. Windows-specific tools and terminology (such as PowerShell modules and Windows paths) are mentioned before or more prominently than their Linux equivalents. However, Linux examples and paths are provided alongside Windows in most troubleshooting sections, and Linux-specific policies are listed.
Recommendations
  • Provide equivalent Linux-native tooling and examples (e.g., Bash, Python, Ansible) for creating and managing machine configuration packages, not just PowerShell.
  • Highlight Linux and Windows examples equally, alternating which is shown first in each section.
  • Clarify whether PowerShell is required for Linux management or if native Linux tools can be used.
  • Expand documentation on Linux-specific troubleshooting and management workflows, including non-PowerShell approaches.
  • Consider mentioning cross-platform alternatives to PowerShell for Linux users who prefer native tools.
GitHub Create Pull Request
Governance Azure Automation State Configuration to machine configuration migration planning ...iguration/whats-new/migrating-from-azure-automation.md
Medium 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 notable Windows bias. All code examples use PowerShell and Azure PowerShell modules, with no equivalent bash, shell, or Linux-native tooling shown. Windows-specific modules and patterns (such as MOF files, Import-DscResource, and PowerShell 7/5.1 compatibility) are discussed in detail, while Linux migration steps and troubleshooting are only briefly mentioned. The troubleshooting section acknowledges issues on macOS/Linux but provides only a PowerShell-based workaround. There are no Linux-specific configuration or module management examples, and Windows terminology and tools are presented first and exclusively throughout.
Recommendations
  • Add equivalent Linux/bash examples for exporting configurations and managing modules, using native Linux tools where possible.
  • Include explicit instructions for Linux users, such as using pwsh (PowerShell Core) on Linux, and clarify cross-platform compatibility.
  • Provide troubleshooting steps and workarounds using Linux-native commands (e.g., curl, wget, REST API calls) alongside PowerShell.
  • Highlight Linux-specific modules and configuration patterns, and discuss any differences in migration for Linux machines.
  • Reorder examples so that Linux and Windows are presented with equal prominence, or alternate which platform is shown first.
GitHub Create Pull Request
Governance Planning a change from Desired State Configuration extension to machine configuration ...onfiguration/whats-new/migrating-from-dsc-extension.md
Medium 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 workflows, referencing Windows PowerShell versions, DSC extension (primarily for Windows), and PowerShell cmdlets throughout. There are no explicit Linux/macOS examples, nor is there mention of Linux-specific DSC extension usage or migration steps. Windows tools and concepts (e.g., Local Configuration Manager, PowerShell module paths, Windows PowerShell compatibility) are referenced exclusively or before any cross-platform alternatives.
Recommendations
  • Add explicit guidance and examples for Linux VMs, including how to identify DSC extension usage and migrate configurations.
  • Clarify whether machine configuration and DSC extension support Linux, and provide parity in migration steps for Linux users.
  • Include Linux/macOS PowerShell module paths and usage patterns where relevant.
  • Reference Linux-specific extension publishers/types if applicable, and provide Kusto queries/examples for Linux DSC extensions.
  • Discuss differences in configuration management between Windows and Linux, including any limitations or requirements.
GitHub Create Pull Request
Governance Quickstart: Create policy assignment with REST API ...n/articles/governance/policy/assign-policy-rest-api.md
Medium 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 demonstrates a notable Windows bias by primarily using PowerShell-specific syntax and escape characters in command examples, referencing PowerShell and Visual Studio Code as defaults, and providing only minimal guidance for Bash/Linux users. Linux/macOS users may encounter friction due to lack of explicit, parallel examples and instructions tailored to their environments.
Recommendations
  • Provide fully parallel Bash/Linux/macOS command examples alongside PowerShell, including correct escape characters and syntax.
  • Explicitly state which shell each example is for, and avoid assuming PowerShell as the default.
  • Include instructions for running Azure CLI commands in native Bash (not just Git Bash), and clarify any differences in file referencing and escaping.
  • Mention alternative editors (e.g., VS Code, vim, nano) for Linux/macOS users.
  • Add troubleshooting tips for common Linux/macOS issues (e.g., file permissions, path formats).
GitHub Create Pull Request
Governance Details of the policy definition structure aliases ...vernance/policy/concepts/definition-structure-alias.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists methods for discovering Azure Policy aliases, presenting the Visual Studio Code extension (cross-platform) first, but then gives Azure PowerShell examples before Azure CLI and REST API. The PowerShell section is more detailed, including advanced usage notes and examples, while the Azure CLI section is shorter and less emphasized. This ordering and depth may create friction for Linux/macOS users, as PowerShell is traditionally Windows-centric and CLI is more common on Linux/macOS.
Recommendations
  • Provide equally detailed examples and notes for Azure CLI, matching the PowerShell section (e.g., how to filter for modifiable aliases).
  • Consider listing Azure CLI before PowerShell, as CLI is more universally available across platforms.
  • Explicitly mention cross-platform compatibility for each tool, clarifying that PowerShell Core and VS Code are available on Linux/macOS.
  • Add links or notes for installing Azure CLI and PowerShell on Linux/macOS.
  • Ensure advanced usage scenarios (such as filtering for modifiable aliases) are shown for both CLI and PowerShell.
GitHub Create Pull Request
Governance Export Azure Policy resources .../articles/governance/policy/how-to/export-resources.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell methods for exporting Azure Policy resources, but PowerShell (a Windows-centric tool) is given a dedicated section and example. The CLI section appears first, but PowerShell is emphasized with detailed cmdlet references and a more complex example. No Linux/macOS-specific tools or shell examples (e.g., Bash, scripting, jq) are provided, and PowerShell is presented as a primary alternative despite its historical Windows bias.
Recommendations
  • Add Linux/macOS-specific examples, such as using Bash, jq, or other common shell tools to process the exported JSON.
  • Clarify that Azure CLI works cross-platform and highlight its parity with PowerShell.
  • Include a note or section on using PowerShell Core on Linux/macOS, if relevant.
  • Provide sample scripts for exporting and manipulating policy resources using native Linux tools.
  • Consider reordering or balancing the prominence of CLI and PowerShell sections to avoid implying PowerShell is the default or preferred method.
GitHub Create Pull Request
Governance Details of the initiative definition structure ...nce/policy/concepts/initiative-definition-structure.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation generally avoids platform-specific bias, but in the 'strongType' section, it references the Windows PowerShell cmdlet 'Get-AzResourceProvider' as the method to determine valid resource types for strongType. No equivalent Azure CLI or REST API command is mentioned for Linux/macOS users, which may create friction for those not using PowerShell.
Recommendations
  • Add Azure CLI and REST API equivalents to 'Get-AzResourceProvider' for determining valid resource types for strongType.
  • Where PowerShell is referenced, provide parallel examples or links for Azure CLI and REST API usage.
  • Explicitly state that all JSON-based policy definitions and initiative structures are platform-agnostic and can be managed from any OS.
GitHub Create Pull Request
Governance Design Azure Policy as Code workflows .../articles/governance/policy/concepts/policy-as-code.md
Medium 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 mentions exporting policy and initiative definitions via PowerShell, CLI, or Azure Resource Graph, listing PowerShell first and referencing it as a primary tool. There are no explicit Linux/macOS shell examples (e.g., Bash, Azure CLI on Linux), nor are there references to Linux-specific workflows or tools. The documentation assumes familiarity with Windows-centric tools and patterns, which may create friction for Linux/macOS users.
Recommendations
  • Provide explicit Bash/Azure CLI examples for common tasks such as exporting policy definitions, assigning policies, and triggering remediation.
  • List cross-platform tools (e.g., Azure CLI) before Windows-specific ones like PowerShell.
  • Include notes or sections on running workflows from Linux/macOS environments, highlighting any differences or considerations.
  • Reference automation tools and scripting environments that are popular on Linux/macOS (e.g., shell scripts, cron, GitHub Actions runners on Linux).
GitHub Create Pull Request
Governance Overview of Azure Policy ...-docs/blob/main/articles/governance/policy/overview.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions both PowerShell and Azure CLI as supported tools for assigning policies, but PowerShell is listed first and referenced more frequently. There are no explicit Linux/macOS examples or tool recommendations, and the documentation does not mention platform-specific considerations for running CLI or PowerShell commands. The overall tone and ordering suggest a slight preference for Windows/PowerShell workflows.
Recommendations
  • Alternate the order of PowerShell and Azure CLI references, or list Azure CLI first in some sections to avoid implicit prioritization of Windows tools.
  • Include explicit statements that both Azure CLI and PowerShell are cross-platform, and provide links or notes for installing/running these tools on Linux/macOS.
  • Add example commands for both Azure CLI and PowerShell side-by-side where relevant, or clarify that all examples work on Linux/macOS as well.
  • Mention that the Azure portal and CLI are accessible from any OS, and clarify any platform-specific limitations if they exist.
GitHub Create Pull Request
Governance Export Azure Policy resources .../articles/governance/policy/how-to/export-resources.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for exporting Azure Policy resources, with CLI (cross-platform) shown first. However, the PowerShell section is prominent, and there is no mention of Linux/macOS-specific considerations, nor are there examples using native Linux tools or shell scripting for further processing. The Resource Graph export is described as a portal feature, which is platform-neutral.
Recommendations
  • Add explicit notes confirming Azure CLI works on Linux/macOS and provide installation links for those platforms.
  • Include examples of exporting and processing JSON output using Linux shell tools (e.g., jq, grep, awk) to demonstrate parity.
  • Clarify that Azure PowerShell is available on Linux/macOS, or link to cross-platform installation instructions.
  • Consider adding bash/zsh script examples for common export scenarios.
GitHub Create Pull Request
Governance [Azure CLI](#tab/azure-cli) ...ery/insight-resources-monitor-data-collection-rules.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for running the query, with PowerShell given its own dedicated section and tab. The PowerShell example may be perceived as Windows-centric, and the ordering of tabs places Azure CLI first (which is cross-platform), but the presence of a PowerShell tab can signal a slight Windows bias. However, there are no examples or instructions that are strictly Windows-only, and the Azure CLI example is fully cross-platform. No Linux-specific tools or shell examples (e.g., Bash, zsh) are provided, but the CLI example suffices for Linux/macOS users.
Recommendations
  • Explicitly state that Azure CLI works on Linux/macOS and Windows.
  • Consider adding a Bash/zsh example for running the Azure CLI command on Linux/macOS.
  • Clarify that PowerShell Core is available cross-platform, or link to installation instructions for Linux/macOS if PowerShell is required.
  • If relevant, mention any platform-specific caveats for CLI or PowerShell usage.
GitHub Create Pull Request
Governance [Azure CLI](#tab/azure-cli) ...ource-graph/includes/samples-by-category/networking.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for each query, but PowerShell examples are always shown immediately after CLI and before any mention of Linux-specific shells or tools. There is no explicit mention of Linux/macOS shells (e.g., Bash), nor are there any examples tailored to Linux environments. The documentation assumes parity between Azure CLI and PowerShell, but the repeated inclusion of PowerShell and its placement may subtly favor Windows users.
Recommendations
  • Add explicit Bash or Linux shell examples where relevant, especially for Azure CLI usage.
  • Clarify that Azure CLI commands work cross-platform and provide notes or examples for Linux/macOS users (e.g., escaping quotes, shell differences).
  • Consider alternating the order of CLI and PowerShell examples, or grouping them together as 'cross-platform' and 'Windows-specific' respectively.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., quote escaping, shell syntax differences).
GitHub Create Pull Request
Governance Understand The Baseline Settings Parameter Format ...ty-baselines/understand-baseline-settings-parameter.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides examples and explanations for both Windows and Linux baseline settings, but the Windows Azure Security Baseline section is presented before the Linux equivalent, and Windows-specific scoping patterns (e.g., WindowsServer\<Year>\<Role>) are described in detail. There is a minor bias in presenting Windows examples and patterns first and with more specificity, while Linux examples are simpler and lack equivalent scoping detail.
Recommendations
  • Present Linux and Windows examples in parallel, or alternate which comes first.
  • Provide equivalent detail for Linux scoping and patterns, if available.
  • Explicitly mention any Linux-specific features or limitations in the same level of detail as Windows.
  • If Windows-specific patterns are described (e.g., role/year scoping), clarify whether similar mechanisms exist or are planned for Linux.
GitHub Create Pull Request
Governance View Machine Configuration Compliance Reporting ...rnance/machine-configuration/how-to/view-compliance.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page is generally cross-platform in its conceptual guidance, focusing on Azure portal and Resource Graph Explorer, which are accessible from any OS. However, in the 'Other Programmatic Access' section, PowerShell (Get-AzGuestConfigurationAssignment) is listed as a primary example for programmatic access, and Windows-centric tooling (PowerShell) is referenced before Linux/macOS alternatives. CLI examples (az CLI) are present, but PowerShell is given equal or greater prominence, which may create friction for Linux/macOS users. No explicit Linux/macOS shell examples are provided, and the documentation does not mention platform-specific nuances or alternatives for Linux users.
Recommendations
  • Add explicit Bash or shell examples for Linux/macOS users alongside PowerShell examples.
  • List az CLI and REST API references before PowerShell cmdlets to avoid Windows-first impression.
  • Clarify that all programmatic interfaces (az CLI, REST API, PowerShell) are cross-platform, and highlight usage on Linux/macOS where relevant.
  • Include notes or links to Linux/macOS-specific documentation or troubleshooting guides.
GitHub Create Pull Request
Governance Azure Machine Configuration prerequisites ...chine-configuration/overview/02-setup-prerequisites.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias: Windows is listed first in tool tables, PowerShell DSC is the primary validation tool for both Windows and Linux, and links to configuration guides and examples (such as managed identity setup) reference Windows VMs before Linux equivalents. Chef InSpec is mentioned for Linux, but PowerShell DSC is emphasized for both platforms, suggesting a Windows-centric approach.
Recommendations
  • Present Linux and Windows examples/tools in parallel, alternating which is listed first.
  • Provide explicit Linux VM configuration guides and links, not just Windows-focused ones.
  • Highlight native Linux tools (e.g., OpenSCAP, Ansible) as alternatives or complements to PowerShell DSC for Linux.
  • Clarify that PowerShell DSC v3 for Linux is a cross-platform solution and provide Linux-specific usage examples.
  • Ensure all instructions and policy assignment steps include Linux VM screenshots and CLI commands where applicable.
GitHub Create Pull Request
Governance Azure machine configuration agent release notes ...es/governance/machine-configuration/whats-new/agent.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Windows release notes before Linux, and in the only example provided for updating the extension, PowerShell is shown first, followed by Azure CLI. There is no Linux shell-specific example (e.g., Bash), and Windows tools/patterns (PowerShell) are prioritized in ordering. However, Linux features and fixes are covered in detail, and Azure CLI is cross-platform.
Recommendations
  • Present Linux and Windows sections in parallel or alternate their order between releases.
  • Provide Linux shell (Bash) examples alongside PowerShell and Azure CLI for extension management.
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows.
  • Ensure that any references to tools or patterns are platform-neutral or provide platform-specific alternatives.
GitHub Create Pull Request
Governance Manage your Azure subscriptions at scale with management groups - Azure Governance ...b/main/articles/governance/management-groups/manage.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently presents Azure PowerShell (which is most commonly used on Windows) examples before Azure CLI examples, and includes detailed PowerShell command usage and output, including Windows-style prompts (e.g., PS C:\>). There is a notable emphasis on PowerShell workflows and terminology, which may be less familiar or accessible to Linux/macOS users. No Linux-specific tools or shell examples (e.g., Bash) are provided, and the PowerShell examples use Windows path conventions.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first in some sections.
  • Include Bash shell examples and outputs where relevant, especially for CLI commands.
  • Avoid Windows-specific prompts (e.g., PS C:\>) in example outputs; use generic or cross-platform prompts.
  • Add notes clarifying that Azure PowerShell is available cross-platform, but CLI is often preferred on Linux/macOS.
  • Where possible, provide Linux/macOS-specific tips or troubleshooting notes.
GitHub Create Pull Request
← Previous Page 5 of 8 Next →