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 76-100 of 186 flagged pages
Governance How to create a machine configuration assignment using Terraform ...configuration/how-to/assign-configuration/terraform.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively provides examples for assigning configurations to Windows virtual machines using Terraform. All resource references and built-in configuration examples target Windows (e.g., azurerm_windows_virtual_machine, AzureWindowsBaseline). There are no examples, instructions, or references for Linux virtual machines or Linux-specific configurations. Additionally, the 'get started' link points to a Windows PowerShell guide, further reinforcing a Windows-centric approach.
Recommendations
  • Include equivalent examples for Linux virtual machines (e.g., using azurerm_linux_virtual_machine).
  • Provide sample assignments for built-in Linux baselines or configurations.
  • Update or supplement the 'get started' link to include Linux/macOS setup guides.
  • Clarify in the introduction whether the process applies to both Windows and Linux, and note any differences.
GitHub Create Pull Request
Governance How to install the machine configuration authoring module ...velop-custom-package/1-set-up-authoring-environment.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily PowerShell-centric, with all examples using PowerShell commands and modules. Windows is often mentioned first in tables and instructions. While Linux is supported, Linux-specific nuances, troubleshooting, or alternative tools are not addressed. The PSDesiredStateConfiguration module is only available as a prerelease for Linux, which is noted but not explained or mitigated.
Recommendations
  • Provide bash or native Linux shell examples where possible, especially for installation and validation steps.
  • Include troubleshooting tips or common issues for Linux users (e.g., permissions, module compatibility).
  • Clarify the limitations of prerelease modules on Linux and suggest stable alternatives if available.
  • Balance the order of presentation (alternate Windows and Linux first in tables and instructions).
  • Mention any Linux-specific dependencies or configuration steps that may differ from Windows.
GitHub Create Pull Request
Governance View Machine Configuration Compliance Reporting ...rnance/machine-configuration/how-to/view-compliance.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides a mostly platform-neutral overview of Azure Machine Configuration compliance reporting, focusing on portal-based experiences and Azure Resource Graph queries. However, there is evidence of Windows bias in the programmatic access section, where PowerShell (Get-AzGuestConfigurationAssignment) is listed as the only example of a language-specific cmdlet, and Windows-centric tooling (PowerShell) is mentioned before Linux-native alternatives. The references table lists PowerShell before CLI and REST API options, and does not mention Linux/macOS-specific shell examples (e.g., Bash, curl, or scripting with az CLI). No Linux/macOS command-line examples are provided, and PowerShell is referenced without parity for Linux users.
Recommendations
  • Add Linux/macOS command-line examples using Bash and az CLI for common compliance reporting tasks.
  • Include references to Linux-native tools and scripting patterns (e.g., curl with REST API, jq for JSON parsing).
  • Present CLI and REST API options before or alongside PowerShell to avoid Windows-first ordering.
  • Explicitly note cross-platform support for all APIs and tools, and provide usage examples for each major OS.
  • Where PowerShell is referenced, clarify that it is available cross-platform, or provide equivalent Bash/CLI commands.
GitHub Create Pull Request
Governance How to sign machine configuration packages ...ration/how-to/develop-custom-package/6-sign-package.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 instructions and examples before Linux equivalents, relying heavily on Powershell cmdlets and Windows certificate tooling. Linux instructions are present but appear after Windows, and some certificate export/import examples are Windows-specific. References and templates are also Windows-centric.
Recommendations
  • Present Windows and Linux instructions in parallel sections or side-by-side, rather than Windows first.
  • Provide Linux-native examples for certificate export/import, such as using openssl or gpg, not just Powershell.
  • Include references and templates for Linux VM scenarios, not only Windows.
  • Clarify which steps are OS-specific and provide direct links to Linux documentation where available.
  • Where Powershell is used on Linux, note prerequisites and alternatives (e.g., bash, native Linux tools).
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by focusing on PowerShell tools and modules (such as GuestConfiguration), referencing PowerShell DSC, and providing a video guide based on the PowerShell module. There is no mention of Linux-native tooling, nor are there Linux-specific examples or workflows. The only Linux-specific note is a limitation about module availability, and macOS is explicitly excluded from testing.
Recommendations
  • Include Linux-native examples and workflows, such as authoring and testing packages using Bash or other Linux tools.
  • Reference Linux equivalents to PowerShell DSC, or clarify how Linux users can perform each step without PowerShell.
  • Provide sample commands and scripts for Ubuntu and other supported Linux distributions.
  • Add a Linux-focused video or walkthrough to match the PowerShell-based guide.
  • Clearly indicate which steps require PowerShell and offer alternatives for Linux users where possible.
GitHub Create Pull Request
Governance Understand Azure Machine Configuration .../articles/governance/machine-configuration/overview.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell Desired State Configuration (DSC) is referenced as the primary validation tool for both Windows and Linux, with Chef InSpec only mentioned for Linux. The open-source nxtools module is described as a PowerShell-based solution for Linux management, reinforcing PowerShell as the main automation approach across platforms. Troubleshooting and log collection examples are provided for both Windows (PowerShell) and Linux (Bash), but the Windows example is presented first. Some policy definitions and sample links are Windows-centric, and Windows tooling is often mentioned before or instead of native Linux alternatives.
Recommendations
  • Include examples using native Linux tools (e.g., Ansible, native shell scripts) for configuration and validation, not just PowerShell DSC.
  • Present Linux and Windows examples side-by-side or alternate which platform is shown first to avoid implicit prioritization.
  • Expand documentation of Linux-specific workflows and troubleshooting, including alternatives to PowerShell for Linux users.
  • Clarify when PowerShell is required on Linux and provide guidance for users who prefer native Linux tools.
  • Highlight Chef InSpec and other Linux-native validation tools more prominently, and provide parity in sample scripts and modules.
GitHub Create Pull Request
Governance Troubleshooting Azure Machine Configuration ...onfiguration/overview/04-operations-troubleshooting.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Minor Windows Example Order
Summary
The documentation provides both Windows and Linux examples for log collection and file locations, but there is a notable emphasis on PowerShell tooling and Windows-specific patterns. The open-source nxtools module is highlighted as a way for PowerShell users to manage Linux systems, suggesting a Windows-centric workflow even for Linux management. Some sections list Windows examples or tools before Linux equivalents, and several built-in policy definitions are Windows-specific (though Linux policies are also present).
Recommendations
  • Provide more native Linux tooling examples (e.g., Bash, system utilities) alongside or before PowerShell-based approaches.
  • Clarify that Linux users do not need to use PowerShell for management tasks, and offer alternative workflows using standard Linux tools.
  • Balance the order of examples so that Linux and Windows are presented equally, or alternate which is shown first.
  • Expand documentation on Linux-specific troubleshooting and management patterns, not just those accessible via PowerShell.
  • Highlight Linux-native DSC resources and modules, if available, rather than focusing on PowerShell-centric solutions.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. It focuses almost exclusively on PowerShell-based tooling and workflows, referencing Windows PowerShell 5.1, PowerShell 7.2, and commands like Remove-DscConfigurationDocument without mentioning Linux/macOS equivalents or alternatives. Examples and migration steps assume a Windows-centric environment, and there is no guidance for Linux users regarding DSC extension usage, migration, or machine configuration specifics.
Recommendations
  • Add explicit guidance for Linux and macOS users, including how to check for DSC extension usage and migrate configurations on those platforms.
  • Provide examples of machine configuration and DSC extension management for Linux VMs, including relevant commands and tools.
  • Clarify which features and steps are Windows-only and which are cross-platform.
  • Include references to Linux DSC resources, modules, and compatibility considerations.
  • Present examples for both Windows and Linux side-by-side, or indicate platform applicability for each step.
GitHub Create Pull Request
Governance Protect your resource hierarchy - Azure Governance ...management-groups/how-to/protect-resource-hierarchy.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a detailed Azure PowerShell example for configuring hierarchy settings but does not offer equivalent CLI or scripting examples for Linux/macOS users (e.g., Bash, Azure CLI, curl). The only code sample is in PowerShell, which is Windows-centric, and the section is labeled 'Azure PowerShell sample.' There is no mention of Linux-native tools or workflows, and the PowerShell example is given before any alternative approaches.
Recommendations
  • Add equivalent examples using Bash with curl or Azure CLI to demonstrate how Linux/macOS users can interact with the REST API.
  • Explicitly mention that the REST API can be used from any platform and provide platform-agnostic sample requests.
  • Reorder or parallelize examples so that Windows and Linux/macOS approaches are presented together, or alternate which is shown first.
  • Clarify that PowerShell Core is cross-platform, but also provide native Bash/curl examples for users who do not use PowerShell.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on PowerShell-based workflows and commands, with all code examples using PowerShell and Azure PowerShell modules. Windows terminology and tools are referenced first and most frequently, while Linux-specific guidance is minimal or absent. The only mention of Linux is in troubleshooting, and there are no Linux shell (bash) examples or explicit instructions for Linux/macOS users.
Recommendations
  • Provide equivalent bash/CLI examples for Linux/macOS users alongside PowerShell commands.
  • Explicitly document any differences or additional steps required for Linux/macOS environments, especially for exporting configurations and handling modules.
  • Highlight cross-platform compatibility and limitations in each section, not just in troubleshooting.
  • Include links to Linux/macOS-specific documentation or guides where relevant.
  • Clarify when commands or modules are Windows-only or have different behavior on Linux/macOS.
GitHub Create Pull Request
Governance Azure Policy definitions modify effect ...n/articles/governance/policy/concepts/effect-modify.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through its exclusive use of Azure PowerShell for alias discovery, with no mention of Linux/macOS equivalents (such as Azure CLI or REST API). The only example of interacting with Azure Policy aliases is a PowerShell command, which is most commonly used on Windows. There are no Linux/macOS-specific instructions or examples, nor is there guidance for users who prefer Bash, Azure CLI, or REST API approaches.
Recommendations
  • Provide equivalent Azure CLI and REST API examples for discovering modifiable aliases and other operations.
  • Explicitly mention cross-platform tools and approaches, such as Bash scripting and Azure CLI, alongside PowerShell.
  • Add a note clarifying that Azure PowerShell is available on Linux/macOS, but also provide alternatives for users who do not wish to install PowerShell.
  • Ensure that all code samples and operational instructions are platform-neutral or include both Windows and Linux/macOS options.
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-11 06:20
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, but lists PowerShell first and does not provide explicit Linux/macOS shell examples or mention cross-platform CLI usage in detail. There are no examples or instructions tailored for Linux/macOS users, and the workflow references Azure Pipelines and GitHub workflows without clarifying platform compatibility. The absence of Linux-specific instructions or parity in examples may create friction for non-Windows users.
Recommendations
  • Explicitly provide CLI (az) command examples for all tasks alongside PowerShell, highlighting cross-platform compatibility.
  • When listing tools or methods, alternate or balance the order (e.g., 'CLI, PowerShell, or Azure Resource Graph') to avoid Windows-first bias.
  • Include notes or sections clarifying that all workflows and automation steps can be performed on Linux/macOS, with links to relevant setup guides.
  • Add example scripts or code snippets using Bash/zsh for Linux/macOS users where appropriate.
  • Mention and link to documentation for running Azure Pipelines and GitHub workflows from Linux/macOS agents.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell-specific syntax and escape characters are emphasized throughout, with examples and explanations tailored to PowerShell users. While Bash/Git Bash is mentioned, Linux/macOS-specific command examples and escape patterns are not shown explicitly. The order and phrasing prioritize Windows/PowerShell usage, leaving Linux/macOS users to infer necessary adaptations.
Recommendations
  • Provide explicit Bash/Linux/macOS command examples alongside PowerShell, especially for escape characters and file referencing.
  • Clearly distinguish between PowerShell and Bash syntax in all command blocks, possibly with separate tabs or sections.
  • Include notes or tables summarizing differences in shell behavior (e.g., escaping @, $, etc.) for both environments.
  • List Bash/Linux prerequisites and tools before or alongside Windows/PowerShell equivalents, not after.
  • 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-11 06:20
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 primarily associated with Windows, and CLI is more common on Linux/macOS.
Recommendations
  • Provide equally detailed examples and advanced usage notes for Azure CLI, matching those given for PowerShell.
  • Consider listing Azure CLI before PowerShell, or presenting both together, to avoid implicit prioritization.
  • Explicitly mention cross-platform compatibility for each tool, especially for PowerShell Core and Azure CLI.
  • Add links or notes for installing Azure CLI and PowerShell on Linux/macOS.
  • Ensure screenshots and walkthroughs are not Windows-centric (e.g., show CLI usage in Linux terminal).
GitHub Create Pull Request
Governance Details of the policy definition structure parameters ...nce/policy/concepts/definition-structure-parameters.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references the Windows PowerShell cmdlet 'Get-AzResourceProvider' as the sole method for determining valid resource types for the 'strongType' property, without mentioning an equivalent Azure CLI or REST API approach for Linux/macOS users. No Linux or cross-platform command-line examples are provided.
Recommendations
  • Include Azure CLI examples (e.g., 'az provider list') alongside PowerShell cmdlets for resource provider queries.
  • Mention REST API alternatives for resource provider information retrieval.
  • Explicitly state that PowerShell is available cross-platform, or clarify platform requirements for the cmdlet.
  • Provide side-by-side examples for both PowerShell and Azure CLI where command-line interaction is discussed.
GitHub Create Pull Request
Governance List of built-in packages for guest configuration ...rticles/governance/policy/samples/built-in-packages.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. Most of the listed built-in packages and policy definitions are Windows-specific, referencing Windows tools, PowerShell DSC modules, and Windows-centric configuration tasks. The introductory text and table structure prioritize Windows scenarios, with Linux policies being rare and often marked as 'Preview'. There is a heavy reliance on PowerShell modules, which are native to Windows, and little to no mention of equivalent Linux tools or modules. Linux examples are sparse, and when present, lack the detail and parity of their Windows counterparts.
Recommendations
  • Expand the list of Linux-specific policies and packages to achieve parity with Windows offerings.
  • Provide equivalent Linux DSC modules or configuration resources, and link to their documentation.
  • Include Linux examples and usage patterns alongside Windows examples, not just as 'Preview'.
  • Clarify which modules and policies are cross-platform, and highlight Linux/macOS compatibility where applicable.
  • Reorganize the table or documentation so that Linux and Windows policies are presented with equal prominence.
  • Add guidance for Linux users on how to audit and remediate configurations using native Linux tools (e.g., shell scripts, Ansible, etc.) if PowerShell is not available.
GitHub Create Pull Request
Governance Tutorial: Build policies to enforce compliance ...icles/governance/policy/tutorials/create-and-manage.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for creating and managing Azure Policy definitions, including file path examples using Windows-style paths (e.g., 'c:\policies\coolAccessTier.json'). PowerShell is presented before Azure CLI, and there are no explicit Linux/macOS shell (bash) examples or notes about cross-platform usage. The REST API and Azure CLI sections are platform-neutral, but the PowerShell focus and Windows file paths may create friction for Linux/macOS users.
Recommendations
  • Add explicit Linux/macOS shell (bash) examples for creating policy definitions, including file paths using POSIX style (e.g., '/home/user/policies/coolAccessTier.json').
  • Clarify that Azure CLI commands work cross-platform and provide sample usage in bash/zsh.
  • Add notes or callouts indicating how Linux/macOS users should adapt PowerShell and file path examples.
  • Consider presenting Azure CLI examples before PowerShell to emphasize cross-platform support.
  • Avoid using Windows-specific file paths in generic examples, or provide both Windows and Linux/macOS variants.
GitHub Create Pull Request
Governance Azure Automanage Best Practices to Azure Policy migration planning ...olicy/how-to/migrate-from-automanage-best-practices.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page shows moderate Windows bias. Several sections (e.g., Microsoft Antimalware, Windows Admin Center) focus exclusively on Windows tools and extensions, with no Linux equivalents or examples. Windows-specific features are described in detail, while Linux support is mentioned only briefly or as an afterthought. Examples and references for configuration and management are Windows-centric, and Windows tools (like Windows Admin Center) are highlighted without Linux alternatives.
Recommendations
  • Add equivalent Linux-focused examples and tools where possible (e.g., antimalware solutions for Linux VMs).
  • When listing configuration steps or policies, present both Windows and Linux instructions side-by-side.
  • Include references to Linux management tools (such as Cockpit or SSH-based management) where Windows Admin Center is mentioned.
  • Ensure that extension and agent installation examples cover both Windows and Linux, not just Windows.
  • Explicitly state Linux support and limitations for each feature, especially where only Windows is referenced.
GitHub Create Pull Request
Governance Programmatically create policies ...es/governance/policy/how-to/programmatically-create.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 moderate Windows bias. Prerequisites and examples prioritize Windows-centric tools and workflows, such as PowerShell and ARMClient, with explicit references to installing Azure CLI on Windows. PowerShell examples are presented first and in greater detail, while Linux/macOS-specific installation instructions and shell examples are absent. ARMClient is referenced without noting its cross-platform status or alternatives. There is no mention of Linux/macOS-specific nuances, nor are Bash or shell scripting examples provided.
Recommendations
  • Add explicit instructions for installing Azure CLI and ARMClient on Linux and macOS, including links to relevant documentation.
  • Provide Bash or shell script equivalents for PowerShell commands, especially for resource group and policy management tasks.
  • Clarify that ARMClient is cross-platform, or suggest alternative tools for Linux/macOS users if needed.
  • Alternate the order of examples, or present CLI (cross-platform) examples before PowerShell to reduce Windows-first perception.
  • Include notes about differences or considerations when running commands on Linux/macOS (e.g., file paths, environment setup).
GitHub Create Pull Request
Governance Remediate non-compliant resources ...ticles/governance/policy/how-to/remediate-resources.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation consistently presents Windows-centric tools (Azure Portal and PowerShell) before cross-platform alternatives (Azure CLI). PowerShell examples are detailed and prominent, while Azure CLI examples are present but less emphasized. There are no Linux-specific instructions, and the ordering and depth of examples may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform.
  • Ensure CLI examples are as detailed as PowerShell ones, including optional parameters and advanced scenarios.
  • Explicitly mention that Azure CLI and Portal are fully supported on Linux/macOS, and clarify any OS-specific limitations.
  • Add notes or sections for Linux/macOS users where relevant, such as installation or environment setup.
  • Avoid language that implies PowerShell is the default or preferred method unless justified by functionality.
GitHub Create Pull Request
Governance Troubleshoot common errors ...ain/articles/governance/policy/troubleshoot/general.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 several forms of Windows bias. Troubleshooting steps for policy evaluation scans repeatedly reference Azure PowerShell as the primary CLI tool, with no mention of Azure CLI (cross-platform) or Bash examples. The only code sample provided is a PowerShell script, specifically for duplicating policy definitions, with no equivalent shown for Linux/macOS users. Windows tools and patterns (PowerShell, Windows machine audit policy) are referenced without Linux parity, and Windows examples or terminology are presented first or exclusively in relevant sections.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell for all command-line instructions, especially for starting evaluation scans and duplicating policy definitions.
  • Provide code samples for Linux/macOS users, such as using Azure CLI or REST API via curl.
  • When referencing Windows-specific policies or audit scenarios, also mention or provide links to equivalent Linux policies or audit procedures.
  • Ensure that instructions for troubleshooting, registration, and resource management are platform-neutral or include both Windows and Linux/macOS workflows.
  • Reorder examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside Windows-specific tools.
GitHub Create Pull Request
Governance Tutorial: Disallow resource types in your cloud environment ...es/governance/policy/tutorials/disallowed-resources.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively uses the Azure portal (web UI) for all steps and does not provide any command-line examples, such as Azure CLI or PowerShell. While the portal is cross-platform, the documentation implicitly assumes a graphical environment and does not mention Linux/macOS command-line workflows. The only mention of command-line tools (Azure CLI, Azure PowerShell, ARM templates) is in a warning about exemptions, but no examples or guidance are provided for these tools. Windows is not overtly prioritized, but Linux users who prefer or require CLI automation are underserved.
Recommendations
  • Add equivalent Azure CLI and/or Azure PowerShell command examples for key tasks (policy assignment, exemption creation, cleanup).
  • Explicitly mention that the Azure portal is web-based and cross-platform, but provide links to CLI documentation for users who prefer terminal workflows.
  • Include ARM template snippets for policy assignment and exemption, with instructions for deploying via CLI on any OS.
  • Reorder or parallelize instructions so that CLI and portal methods are presented side-by-side or in separate sections.
GitHub Create Pull Request
Governance Explore your Azure resources ...overnance/resource-graph/concepts/explore-resources.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 all queries, but PowerShell examples are always shown after CLI, and PowerShell-specific notes and output formatting are included. There is a notable emphasis on PowerShell usage and Windows-centric tooling (e.g., ConvertTo-Json, variable usage), with no mention of Bash scripting, Linux-specific CLI patterns, or macOS considerations. The JSON output examples use Windows-centric resource properties (e.g., osType: Windows, WindowsServer images), and shell scripting examples for Azure CLI use Unix tools (awk, sed), but there is no explicit guidance for Linux/macOS users or parity in scripting approaches.
Recommendations
  • Add explicit Bash scripting examples for Azure CLI, especially for multi-step queries and file manipulation.
  • Include notes or examples for macOS/Linux users regarding file handling and command-line differences.
  • Provide parity in output formatting guidance for Azure CLI (e.g., using jq for JSON processing) as is done for PowerShell.
  • Balance the use of Windows-centric resource properties (e.g., show Linux VM examples alongside Windows).
  • Clarify that Azure CLI works cross-platform and highlight any OS-specific caveats.
GitHub Create Pull Request
Governance Work with large data sets ...s/governance/resource-graph/concepts/work-with-data.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation consistently provides Azure CLI and Azure PowerShell examples for interacting with Azure Resource Graph, but does not include Linux/macOS-specific shell examples (such as Bash or scripting with curl for REST API). Azure PowerShell is a Windows-centric tool, and its examples are given alongside CLI, but no Linux-native alternatives or ordering are offered. REST API usage is mentioned but not exemplified with Linux-friendly tools.
Recommendations
  • Add Bash shell examples using curl or httpie to demonstrate REST API usage for Linux/macOS users.
  • Clarify that Azure CLI is cross-platform and can be used on Linux/macOS, and consider showing Bash usage explicitly.
  • Provide example scripts or command lines for Linux/macOS environments, such as using jq to process output.
  • Reorder examples so that cross-platform tools (Azure CLI, REST API) are presented before Windows-centric tools (PowerShell).
  • Explicitly mention Linux/macOS compatibility where relevant.
GitHub Create Pull Request
Governance Manage Azure Service Group membership at scale ...rticles/governance/service-groups/manage-membership.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a detailed PowerShell script for bulk membership management using Azure Resource Graph, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI, or cross-platform scripting). The only automation example for querying and deploying memberships at scale is Windows-centric, and PowerShell is presented as the primary or sole method for this workflow.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for querying Azure Resource Graph and deploying resources, ensuring cross-platform compatibility.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, and clarify any platform-specific requirements.
  • Provide guidance or links for Linux/macOS users on how to adapt the PowerShell script, or offer a Python SDK example.
  • Ensure that automation workflows are demonstrated with tools available and commonly used on all platforms, not just Windows.
GitHub Create Pull Request
← Previous Page 4 of 8 Next →