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 401-425 of 613 flagged pages
Governance How to access custom machine configuration package artifacts ...tion/how-to/develop-custom-package/5-access-package.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation exclusively provides PowerShell code for generating SAS tokens, with no equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI, or REST API). The use of PowerShell and references to Azure VMs (typically Windows-centric) further reinforce a Windows-first approach. There is no mention of Linux tools or cross-platform alternatives, which may hinder Linux/macOS users from following the guide directly.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for generating SAS tokens.
  • Include instructions or code snippets for using REST API to generate SAS tokens, which are platform-agnostic.
  • Explicitly mention that the steps can be performed on Linux/macOS and provide guidance for those environments.
  • Reorder or parallelize examples so that Windows and Linux/macOS approaches are presented together.
GitHub Create Pull Request
Governance Troubleshooting Azure Machine Configuration ...onfiguration/overview/04-operations-troubleshooting.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates moderate Windows bias. Windows-specific tools (PowerShell, Windows paths, Windows-centric policy definitions) are mentioned frequently and sometimes before Linux equivalents. The open-source nxtools module is described as a PowerShell tool for Linux, reinforcing PowerShell as the primary interface even for Linux users. However, Linux examples and paths are provided in most relevant sections, and Linux-specific policy definitions are listed alongside Windows ones.
Recommendations
  • Provide Bash or native Linux command examples before or alongside PowerShell examples, especially in troubleshooting sections.
  • Highlight native Linux management tools and workflows (e.g., systemctl, journalctl) for log collection and service management, not just PowerShell.
  • Clarify that PowerShell is optional for Linux users and offer alternatives where possible.
  • Balance the order of Windows and Linux examples and references throughout the documentation.
  • Expand documentation for Linux-specific policy definitions and troubleshooting steps.
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-13 00:00
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 and Windows-centric tooling, with all code examples using PowerShell cmdlets and modules. There is minimal mention of Linux-specific workflows, and Linux users are only referenced in troubleshooting, not in primary migration steps or examples. No bash or Linux-native commands are provided, and Windows tools/patterns are presented first and exclusively.
Recommendations
  • Provide equivalent Linux migration examples using bash, Azure CLI, or Python where possible.
  • Explicitly document any differences in workflow for Linux machines, including how to export configurations and modules.
  • Include Linux-specific troubleshooting and best practices for DSC migration.
  • Clarify cross-platform compatibility for PowerShell commands and note any limitations or required adjustments for Linux/macOS.
  • Add links or references to Linux DSC documentation and migration guides.
GitHub Create Pull Request
Governance Quickstart: Create a management group with .NET Core ...ce/management-groups/create-management-group-dotnet.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing only Windows-style execution instructions (using mgCreate.exe and backtick line continuations) and omitting Linux/macOS equivalents (such as mgCreate.dll or ./mgCreate, and bash syntax). No Linux-specific guidance or examples are given for running the .NET Core application, which may cause confusion or friction for non-Windows users.
Recommendations
  • Include explicit instructions for running the .NET Core application on Linux/macOS, such as using './mgCreate' or 'dotnet mgCreate.dll' instead of 'mgCreate.exe'.
  • Provide example commands using bash syntax and line continuation (\) for Linux/macOS users.
  • Clarify any platform-specific differences in building and publishing .NET Core applications (e.g., output file extensions, execution methods).
  • Mention that .NET Core is cross-platform and highlight steps for verifying installation on Linux/macOS.
GitHub Create Pull Request
Governance Details of the Azure Policy attestation structure ...es/governance/policy/concepts/attestation-structure.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation mentions PowerShell as a primary management tool for attestations and lists it before Azure CLI. There are no explicit Linux/macOS examples or references to platform-specific considerations. The focus on PowerShell and lack of parity in examples may create friction for Linux/macOS users.
Recommendations
  • Provide explicit Linux/macOS usage examples, especially for Azure CLI.
  • List Azure CLI before PowerShell or equally, as CLI is cross-platform.
  • Clarify that both PowerShell and CLI are available on all platforms, and link to installation guides for Linux/macOS.
  • Add notes or sections addressing platform differences, if any, in attestation management.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists Windows-centric tools (Visual Studio Code extension, Azure PowerShell) before cross-platform options (Azure CLI, REST API). PowerShell examples are more detailed, including advanced usage notes, while CLI examples are simpler. This ordering and detail level may create friction for Linux/macOS users who are less likely to use PowerShell.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform parity.
  • Expand Azure CLI examples to match the depth of PowerShell examples, including advanced queries and notes about modifiable aliases.
  • Explicitly mention that Azure CLI and REST API are fully supported on Linux/macOS.
  • Add Bash shell snippets where appropriate, especially for scripting use cases.
  • Clarify that Visual Studio Code is cross-platform, and highlight any Linux/macOS-specific installation notes if relevant.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references the Windows-specific PowerShell cmdlet 'Get-AzResourceProvider' as the method to determine valid strongType resource types, without mentioning an equivalent Azure CLI or REST API approach for Linux/macOS users. No Linux/macOS-specific examples or alternative tooling are provided.
Recommendations
  • Add instructions for determining valid strongType resource types using Azure CLI (e.g., 'az provider show' or 'az resource list') and/or REST API.
  • Include cross-platform command examples (Azure CLI, REST API) alongside PowerShell references.
  • Clarify that PowerShell is available on Linux/macOS, but provide parity for users who prefer native tools.
  • Consider listing both Windows and Linux/macOS approaches in all tool references.
GitHub Create Pull Request
Governance Learn Azure Policy for Kubernetes ...es/governance/policy/concepts/policy-for-kubernetes.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools (Azure portal, Azure CLI, Azure PowerShell) are mentioned and shown first in most procedural sections, with Azure CLI and PowerShell examples provided for resource provider registration. Linux-specific instructions are not highlighted or prioritized, and there is little explicit mention of Linux/macOS parity. However, most commands (kubectl, helm, bash) are cross-platform, and the Azure CLI is available on Linux/macOS, so Linux users can generally follow along, though with some friction.
Recommendations
  • Explicitly state that Azure CLI and kubectl commands work on Linux/macOS and provide installation links for those platforms.
  • When listing tools or examples, alternate the order or provide Linux/macOS-specific instructions/examples first in some sections.
  • Add troubleshooting notes or links for Linux/macOS users where Azure CLI or PowerShell installation or usage may differ.
  • Clarify that the Azure portal is web-based and platform-agnostic.
  • Where PowerShell is mentioned, provide Bash or shell alternatives if possible.
  • Add a section or callout confirming full support for Linux/macOS environments, especially for developer workstations.
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-13 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 moderate Windows bias. Several sections, such as Microsoft Antimalware and Windows Admin Center, focus exclusively on Windows tools and extensions, with no Linux equivalents or alternatives mentioned. In example lists, Windows is often referenced first, and Linux-specific guidance is less detailed or omitted entirely. While some features (e.g., Change Tracking, Update Manager) acknowledge Linux support, the overall emphasis and example depth favor Windows users.
Recommendations
  • Include Linux-specific examples and configuration steps wherever Windows examples are provided, especially for extensions and policy assignments.
  • For tools like Microsoft Antimalware and Windows Admin Center, clarify Linux alternatives or explicitly state platform limitations.
  • Ensure that lists and instructions mention Linux and Windows equally, and avoid consistently listing Windows first.
  • Add references to Linux documentation and best practices for parity.
  • Where features are Windows-only, clearly indicate this and suggest Linux-compatible security or management solutions.
GitHub Create Pull Request
Governance Remediate non-compliant resources ...ticles/governance/policy/how-to/remediate-resources.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation presents examples and instructions for three interfaces: Azure Portal, Azure PowerShell, and Azure CLI. However, PowerShell examples are given in greater detail and complexity than Azure CLI, and are presented before CLI in each section. PowerShell is a Windows-centric tool, and its prominence may disadvantage Linux/macOS users. There are no Bash or shell script examples, and no explicit mention of Linux/macOS-specific considerations. The Azure Portal instructions are platform-neutral, but the overall example ordering and depth favor Windows/PowerShell users.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Expand Azure CLI examples to match the depth and complexity of PowerShell examples, including advanced scenarios.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Add Bash/shell script snippets where appropriate, especially for automation tasks.
  • Include notes or links for Linux/macOS users regarding installation and usage of Azure CLI and PowerShell Core.
GitHub Create Pull Request
Governance Get policy compliance data ...ticles/governance/policy/how-to/get-compliance-data.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed examples for Azure PowerShell, REST API, Azure CLI, and GitHub Actions, but PowerShell examples are more extensive and appear before CLI examples in several sections. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell-specific patterns (such as jobs) are described in detail, while CLI usage is covered more briefly. This creates a subtle bias toward Windows/PowerShell users, with Linux/macOS users receiving less guidance, especially for advanced usage.
Recommendations
  • Add Bash and cross-platform shell examples for common tasks, especially for querying and automation.
  • Expand Azure CLI sections to include advanced usage patterns (e.g., background jobs, output parsing) similar to PowerShell coverage.
  • Where PowerShell-specific features (like jobs) are described, provide equivalent CLI or Bash patterns (e.g., using & or nohup for background processes).
  • Ensure CLI examples are presented before or alongside PowerShell examples to signal parity.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
GitHub Create Pull Request
Governance Programmatically create policies ...es/governance/policy/how-to/programmatically-create.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Prerequisites and examples prioritize Windows-centric tools and workflows, such as PowerShell and ARMClient, with PowerShell instructions and references appearing before Azure CLI. The Azure CLI installation link is specifically for Windows, and there is no mention of Linux/macOS equivalents for installing Azure CLI or using ARMClient. PowerShell commands are presented first and in greater detail, while Linux/macOS-specific guidance is missing throughout.
Recommendations
  • Add explicit instructions and links for installing Azure CLI on Linux and macOS, not just Windows.
  • Clarify whether ARMClient is cross-platform, and if not, suggest alternatives for Linux/macOS users (e.g., curl, httpie, or native REST API usage).
  • Provide example commands for Linux/macOS shells (bash/zsh), especially for file paths and environment variables.
  • Balance the order of examples: present Azure CLI and REST API examples before or alongside PowerShell, not after.
  • Note any platform-specific limitations or differences in tool usage.
  • Where PowerShell is used, offer equivalent bash/CLI commands for Linux/macOS users.
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-13 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 moderate Windows bias. PowerShell examples and references are given significant prominence, with detailed usage and file path examples (e.g., 'c:\policies\coolAccessTier.json') that are Windows-specific. PowerShell is covered before Azure CLI, and Windows file system conventions are used without Linux/macOS equivalents. There are no explicit Linux/macOS shell examples (e.g., Bash), nor are alternative file path formats or OS-specific notes provided. The portal instructions are OS-neutral, but command-line sections favor Windows.
Recommendations
  • Add Bash/Linux/macOS examples alongside PowerShell, especially for file paths and scripting.
  • Use cross-platform file path examples (e.g., '/home/user/policies/coolAccessTier.json') or note both formats.
  • Clarify that Azure CLI works on all platforms and provide OS-specific installation or usage notes if relevant.
  • Alternate the order of PowerShell and CLI examples, or present them side-by-side.
  • Explicitly mention that all command-line examples are cross-platform unless otherwise noted.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. The majority of policy definitions and examples are for Windows machines, with only a handful of Linux-specific entries. The guidance and table focus on PowerShell Desired State Configuration (DSC) modules, which are primarily Windows-centric, and frequently reference Windows tools and patterns. Linux policies are less represented, and there is little detail about Linux equivalents or modules. The introductory text also directs users to review PowerShell scripts to understand settings for both Windows and Linux, but in practice, nearly all referenced modules and configurations are for Windows.
Recommendations
  • Add more Linux-specific policy definitions and examples to the table.
  • Provide explicit links and documentation for Linux DSC resource modules, if available.
  • Balance the introductory guidance to equally discuss Linux configuration mechanisms (e.g., shell scripts, Ansible, or native Linux DSC resources).
  • Ensure Linux examples are shown alongside Windows examples, not only as a minority or afterthought.
  • Clarify which modules and configurations are cross-platform and which are Windows-only.
  • Include Linux-specific tools and patterns (such as OpenSCAP, auditd, or native configuration management tools) where relevant.
GitHub Create Pull Request
Governance Troubleshoot common errors ...ain/articles/governance/policy/troubleshoot/general.md
Medium Priority View Details →
Scanned: 2026-01-13 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 moderate Windows bias, primarily through the exclusive use of Azure PowerShell examples for key troubleshooting steps (e.g., duplicating policy definitions with metadata). There are no CLI (az), Bash, or Linux/macOS-specific examples provided, and PowerShell is referenced as the primary automation tool for tasks that could be performed cross-platform. Additionally, Windows terminology and tools are mentioned first or exclusively in some scenarios, with no Linux parity in examples or instructions.
Recommendations
  • Provide equivalent examples using Azure CLI (az) and Bash scripts for all PowerShell-based instructions, especially for duplicating policy definitions and triggering on-demand evaluation scans.
  • Explicitly mention cross-platform support and clarify which steps can be performed on Linux/macOS, not just Windows.
  • Where PowerShell is referenced, add a note or link to Linux/macOS alternatives.
  • Ensure that troubleshooting steps do not assume the use of Windows-only tools or environments.
  • Add examples for common Linux tools (e.g., curl, jq) where appropriate, especially in sections about REST API usage.
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-13 00:00
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 Azure portal is cross-platform, the documentation assumes GUI usage and does not mention or demonstrate how to perform these tasks via CLI tools, which are commonly used on Linux/macOS. The only mention of CLI tools (Azure CLI, Azure PowerShell, ARM templates) is in a warning, suggesting their use for creating resources in exempted scopes, but no examples or guidance are provided. Windows is not directly referenced, but the lack of CLI instructions creates friction for Linux/macOS users who may prefer or require command-line automation.
Recommendations
  • Add equivalent Azure CLI examples for all major steps (assigning policies, creating exemptions, cleaning up resources).
  • Include PowerShell examples for parity, but ensure Azure CLI is presented first or equally, as it is cross-platform.
  • Explicitly mention that all steps can be performed via CLI and link to relevant documentation.
  • Clarify that the Azure portal is accessible from any OS, but provide alternatives for users who prefer command-line interfaces.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides command-line examples for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell examples are presented alongside CLI examples without clarifying cross-platform compatibility. There is also no mention of Linux-specific considerations or tools, and the PowerShell examples may not be directly usable on non-Windows systems unless users have installed PowerShell Core.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and consider providing Bash shell examples where relevant.
  • Note that PowerShell Core is cross-platform, but traditional PowerShell is Windows-only; specify which version is being referenced.
  • Add explicit Linux/macOS shell usage notes or examples to ensure parity and reduce confusion for non-Windows users.
  • Where possible, provide REST API curl examples, which are universally usable across platforms.
  • Reorder examples to show cross-platform tools (Azure CLI, REST API) before Windows-centric tools (PowerShell).
GitHub Create Pull Request
Governance [Azure CLI](#tab/azure-cli) ...amples-by-category/azure-policy-guest-configuration.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation shows a moderate Windows bias. PowerShell examples are provided for every scenario, and in some cases, Windows-specific guest configuration names (e.g., 'WindowsPendingReboot') are used without Linux equivalents. While Azure CLI examples are present (which are cross-platform), the PowerShell tab is always present and sometimes appears before CLI in the tab order. There are no explicit Linux/macOS shell or command-line examples, and some queries are tailored to Windows resources without mentioning Linux alternatives.
Recommendations
  • Add explicit Bash/Linux/macOS shell examples where appropriate, especially for Azure CLI commands.
  • When referencing guest configuration assignments, provide both Windows and Linux assignment names (e.g., show both 'WindowsPendingReboot' and any Linux equivalents).
  • Ensure that Linux-specific scenarios are covered with their own queries and examples, not just Windows ones.
  • Consider making Azure CLI the default or first example, as it is cross-platform.
  • Clarify in the documentation that Azure CLI commands work on all platforms, and provide any platform-specific notes if necessary.
GitHub Create Pull Request
Governance Troubleshoot common errors for Azure Resource Graph ...cles/governance/resource-graph/troubleshoot/general.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides a PowerShell-only example for batching queries across subscriptions, with no equivalent example for Linux/macOS users (e.g., Azure CLI or REST API). The guidance for resolving the 'Too many subscriptions' scenario is centered on Windows tooling and scripting, creating friction for users on other platforms.
Recommendations
  • Add equivalent examples using Azure CLI (bash syntax) for batching queries across subscriptions.
  • Include REST API sample requests for the same scenario, with guidance on batching.
  • Ensure that examples are presented for both PowerShell and CLI/REST, or at least mention alternatives for non-Windows users.
  • Consider presenting CLI or REST examples before PowerShell, or side-by-side.
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-13 00:00
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 is Windows-centric, relying on PowerShell and Windows-specific modules, with no mention of alternatives or parity for other platforms.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for querying Azure Resource Graph and deploying resources.
  • Explicitly mention that the PowerShell script is Windows-centric and provide guidance or links for Linux/macOS users.
  • Include cross-platform instructions for authentication and deployment (e.g., using az login, az deployment group create).
  • Highlight any platform-specific requirements and offer alternatives where possible.
  • Consider providing a Python example using the Azure SDK for resource graph queries and deployments.
GitHub Create Pull Request
Governance [Azure CLI](#tab/azure-cli) ...al-machine-scale-sets-resources-flexible-orchestration.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric and is presented as a primary tab. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-native tools or patterns. The ordering of tabs places Azure PowerShell before the Portal, which may reinforce a Windows-first perspective.
Recommendations
  • Add explicit bash or Linux shell examples alongside Azure CLI to demonstrate Linux parity.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
  • Consider reordering tabs so that cross-platform tools (Azure CLI) are presented before Windows-centric tools (PowerShell).
  • If relevant, mention Linux-native scripting or automation options for interacting with Azure Resource Graph.
GitHub Create Pull Request
Governance [Azure CLI](#tab/azure-cli) ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/authorization-resources-role-definitions-actions-list.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and its example is given equal prominence. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or patterns. The ordering places Azure CLI first, but the inclusion of PowerShell without a corresponding bash or shell example may suggest a slight Windows bias.
Recommendations
  • Add explicit bash or shell script examples for Linux users, demonstrating the same query using Azure CLI in a Linux shell environment.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide platform-specific notes if needed.
  • Consider reordering or grouping examples to emphasize cross-platform parity, such as grouping CLI and shell examples together before PowerShell.
  • If PowerShell is shown, mention that PowerShell Core is available on Linux and macOS, and provide usage notes for those platforms.
GitHub Create Pull Request
Governance Quickstart: Create a management group with .NET Core ...ce/management-groups/create-management-group-dotnet.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by providing only Windows-style execution examples (using mgCreate.exe with backticks for line continuation), and omitting Linux-specific instructions for running the .NET Core application. There is no mention of Linux or cross-platform considerations when building or executing the application, despite .NET Core being cross-platform.
Recommendations
  • Include Linux/macOS examples for running the .NET Core application (e.g., using ./mgCreate instead of mgCreate.exe, and using \ for line continuation or listing all arguments on one line).
  • Explicitly state that .NET Core applications can be run on Windows, Linux, and macOS, and provide platform-specific instructions where relevant.
  • Mention any platform-specific prerequisites or differences (such as file permissions, executable extensions, or environment setup) for Linux/macOS users.
  • Use neutral terminology and examples that apply to all supported platforms, or present both Windows and Linux/macOS variants side by side.
GitHub Create Pull Request
Governance Manage your Azure subscriptions at scale with management groups - Azure Governance ...b/main/articles/governance/management-groups/manage.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure Portal, Azure PowerShell, and Azure CLI for all major management group operations. However, PowerShell examples are consistently presented before Azure CLI examples, and PowerShell-specific notes (such as parameter aliasing and output formatting) are included. The PowerShell examples use Windows-style prompts (e.g., 'PS C:\>'), and there are no explicit Linux shell examples or references to Linux-specific patterns or tools. The documentation does not mention Linux environments or provide Bash-specific guidance, which may make it less approachable for Linux users.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present them side-by-side to avoid implicit prioritization.
  • Include explicit Bash shell examples where relevant, especially for scripting scenarios.
  • Add notes clarifying that Azure CLI works cross-platform and provide guidance for Linux/macOS users (e.g., shell environment setup, authentication differences).
  • Avoid Windows-specific prompt conventions (e.g., 'PS C:\>') unless also providing equivalent Linux shell prompts.
  • Mention that both PowerShell and Azure CLI are available on Linux and macOS, and link to installation guides for those platforms.
  • If referencing PowerShell-specific features (like parameter aliasing), clarify whether these apply to PowerShell Core on Linux/macOS.
GitHub Create Pull Request
Governance Details of Azure Policy definition structure basics ...ernance/policy/concepts/definition-structure-basics.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias by referencing PowerShell and Azure CLI as the primary tools for specifying the 'mode' parameter in policy definitions. PowerShell is mentioned before Azure CLI, and there are no explicit examples or mentions of Linux-native tools or workflows (such as Bash scripts or Linux shell usage). The documentation does not provide Linux-specific examples or guidance, and the only tooling context given is Windows-centric.
Recommendations
  • Include explicit examples using Bash or Linux shell commands for creating and managing Azure Policy definitions.
  • Mention cross-platform compatibility of Azure CLI and PowerShell, and clarify usage on Linux and macOS systems.
  • Add references to Linux-native tools or workflows where relevant, such as using Azure CLI in Bash scripts.
  • Ensure that examples and instructions are not Windows-first; alternate the order of tool mentions or provide parity in examples.
  • Consider adding a section or note on how to perform policy management tasks on Linux systems, including installation and usage of Azure CLI and PowerShell on Linux.
GitHub Create Pull Request
← Previous Page 17 of 25 Next →