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 351-375 of 613 flagged pages
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-14 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-based workflows and commands, with all examples using PowerShell and Azure PowerShell modules. Windows tools and patterns are mentioned exclusively, and Linux-specific instructions or examples are missing. While there is some acknowledgement of Linux support, practical guidance is almost entirely Windows-centric, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent CLI or Bash examples for Linux/macOS users, especially for exporting configurations and managing modules.
  • Explicitly document how to perform migration steps on Linux/macOS, including installation of required tools and handling of file paths.
  • Highlight any platform-specific differences in workflows, such as issues with file naming or module compatibility.
  • Include troubleshooting steps and workarounds for common Linux/macOS issues upfront, not just in the troubleshooting section.
  • Reference and link to Linux/macOS-specific documentation where available.
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-14 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 oriented towards Windows and PowerShell, referencing Windows PowerShell versions, DSC extension specifics, and commands without providing Linux/macOS equivalents or guidance. Examples and migration steps assume PowerShell usage and Windows-centric workflows, with no mention of Linux DSC extension scenarios, Bash/CLI alternatives, or cross-platform considerations.
Recommendations
  • Add explicit guidance for Linux and macOS users, including how to check for DSC extension usage on non-Windows VMs.
  • Provide examples using Bash, Azure CLI, or cross-platform PowerShell Core where possible.
  • Clarify whether machine configuration and migration steps apply to Linux VMs, and if so, detail any differences.
  • Include references to Linux DSC extension documentation and migration paths.
  • List OS-specific limitations or considerations for both Windows and Linux up front.
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-14 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. PowerShell-specific syntax and escape characters are explained in detail, while Linux/Bash equivalents are mentioned only briefly or as secondary notes. All command examples use Azure CLI, but the syntax and escaping are tailored for PowerShell, with Linux/Bash instructions relegated to side comments. No explicit Linux/macOS command blocks or examples are provided, and Windows tools (PowerShell, Visual Studio Code) are listed first in prerequisites.
Recommendations
  • Provide explicit Bash/Linux/macOS command examples alongside PowerShell, using correct escape characters and syntax.
  • Add a dedicated section or callouts for Linux/macOS users, including common shells (bash, zsh, etc.) and their nuances.
  • List platform prerequisites in parallel (e.g., 'PowerShell (Windows), Bash (Linux/macOS)') rather than Windows-first.
  • Clarify that Visual Studio Code is cross-platform, or suggest alternative editors for Linux/macOS.
  • Where escape characters differ, show both forms in code blocks, not just in explanatory text.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references the Windows-specific PowerShell cmdlet 'Get-AzResourceProvider' as the primary method to determine valid resource types for the 'strongType' property. No equivalent CLI or REST API method for Linux/macOS users is mentioned, and the Windows tool is presented first and exclusively.
Recommendations
  • Include equivalent Azure CLI commands (e.g., 'az provider list') for Linux/macOS users alongside PowerShell examples.
  • Add REST API references or examples for cross-platform access.
  • Present Windows and Linux/macOS methods in parallel, or mention cross-platform options before platform-specific tools.
  • Clarify that PowerShell is available on Linux/macOS, but also provide native CLI alternatives.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page contains a notable Windows bias by exclusively referencing Azure PowerShell for obtaining modifiable aliases, without mentioning equivalent Azure CLI or REST API methods. No Linux/macOS-specific examples or tools are provided, and the only command-line example is PowerShell-centric.
Recommendations
  • Add equivalent Azure CLI commands for listing modifiable aliases, such as using 'az policy alias list' or REST API examples.
  • Explicitly mention that Azure CLI and REST API can be used on Linux/macOS and provide sample commands.
  • Ensure that command-line examples are provided for both PowerShell and CLI, with equal prominence.
  • Add a note clarifying cross-platform options for policy management tasks.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for command-line operations, but PowerShell examples are more detailed and include advanced usage (e.g., background jobs). PowerShell is featured prominently, and some explanations (such as job handling) are specific to Windows/PowerShell environments. There are no explicit Linux/macOS shell examples (e.g., Bash), nor is there mention of Linux-specific patterns or tools. The order of presentation often places PowerShell before CLI, and CLI examples are less detailed.
Recommendations
  • Add Bash shell examples for REST API usage (e.g., using curl or httpie) to demonstrate Linux/macOS workflows.
  • Expand Azure CLI sections to include advanced usage comparable to PowerShell (e.g., background execution, output parsing).
  • Ensure CLI and REST examples are presented before or alongside PowerShell, not after.
  • Clarify that Azure CLI works cross-platform and highlight any differences in output or usage between platforms.
  • Avoid PowerShell-specific explanations unless a cross-platform equivalent is provided.
GitHub Create Pull Request
Governance Programmatically create policies ...es/governance/policy/how-to/programmatically-create.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits a moderate Windows bias. Windows-centric tools (PowerShell, ARMClient) are emphasized, and Windows installation instructions for Azure CLI are given before Linux equivalents. PowerShell examples are presented first and in greater detail, with Linux/macOS alternatives (such as Bash or shell scripting) absent. ARMClient is a Windows-only tool, and its use is recommended without Linux alternatives.
Recommendations
  • Provide installation instructions for Azure CLI on Linux/macOS alongside Windows, or link to the cross-platform install page.
  • Include Bash or shell scripting examples for policy creation and assignment, especially for Azure CLI and REST API usage.
  • Mention cross-platform alternatives to ARMClient (such as curl or httpie) for REST API calls, with example commands.
  • Alternate the order of examples so that Azure CLI or REST API (which are cross-platform) are shown before PowerShell.
  • Explicitly note which tools are Windows-only and suggest Linux/macOS equivalents.
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-14 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. Windows-specific tools (e.g., Windows Admin Center) are highlighted, and Windows examples or extensions are often mentioned before Linux equivalents. Some sections, such as Microsoft Antimalware and Windows Admin Center, are exclusively Windows-focused, with no Linux alternatives or parity discussed. While Linux is referenced in areas like Change Tracking and Update Manager, examples and guidance are less detailed or appear after Windows instructions.
Recommendations
  • Add equivalent Linux management tool guidance (e.g., alternatives to Windows Admin Center for Linux VMs).
  • Ensure that examples for policy deployment, agent installation, and extension configuration are provided for both Windows and Linux, with equal detail.
  • Present Windows and Linux instructions side-by-side or in parallel sections, rather than listing Windows first.
  • For features that are Windows-only (e.g., Microsoft Antimalware, Windows Admin Center), explicitly state this and suggest Linux alternatives or clarify limitations.
  • Include more Linux-specific policy examples and references, especially for security, backup, and monitoring.
GitHub Create Pull Request
Governance Remediate non-compliant resources ...ticles/governance/policy/how-to/remediate-resources.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. PowerShell examples are provided in detail and are shown before Azure CLI equivalents. The use of PowerShell (a Windows-centric tool) is prominent, and instructions often reference Windows-first workflows (e.g., 'Connect-AzAccount', PowerShell cmdlets). While Azure CLI examples are present, they are less detailed and typically follow PowerShell instructions. There is no explicit mention of Linux/macOS-specific considerations, nor are there examples using Bash or shell scripting, which are common on those platforms.
Recommendations
  • Provide Azure CLI examples before or alongside PowerShell examples to avoid Windows-first perception.
  • Expand Azure CLI sections with detailed, step-by-step instructions and explanations matching the PowerShell coverage.
  • Include notes or examples for Linux/macOS users, such as shell scripting alternatives or environment-specific caveats.
  • Clarify that Azure CLI and portal workflows are fully supported on Linux/macOS, and highlight any cross-platform differences.
  • Consider including Bash script snippets or references to automation on Linux/macOS.
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-14 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 notable Windows bias. The majority of policy definitions and examples are for Windows, with only a handful for Linux. The introductory text and table focus on PowerShell Desired State Configuration (DSC) modules, which are primarily Windows-centric, and reference Windows-specific tools and patterns. Linux policies are fewer, less detailed, and sometimes marked as 'Preview'. There is little information about Linux equivalents or parity in tooling and examples.
Recommendations
  • Add more Linux-specific policy definitions and examples to match Windows coverage.
  • Include references to Linux configuration management tools (e.g., Ansible, Chef, native shell scripts) where appropriate.
  • Provide detailed documentation and links for Linux DSC modules and their usage.
  • Ensure Linux examples are presented alongside Windows examples, not only as an afterthought.
  • Clarify which modules and configurations are cross-platform and which are Windows-only.
  • Remove or balance the emphasis on PowerShell by mentioning Linux-native approaches.
GitHub Create Pull Request
Governance Tutorial: Add user assign identities to virtual machines ...ce/policy/tutorials/modify-virtual-machine-identity.md
Medium Priority View Details →
Scanned: 2026-01-14 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 instructions for the Azure Portal and PowerShell, but omits equivalent CLI or scripting examples for Linux/macOS users. The PowerShell section is extensive and assumes use of Azure PowerShell, which is most commonly used on Windows. There are no Bash, Azure CLI, or cross-platform scripting examples, and PowerShell is presented as the only command-line option.
Recommendations
  • Add equivalent Azure CLI (az) commands for all PowerShell steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash script examples for file creation and command execution.
  • Explicitly mention that Azure PowerShell can be used on Linux/macOS, or provide installation guidance for non-Windows platforms.
  • Present command-line options in parallel (e.g., 'Using PowerShell or Azure CLI'), rather than PowerShell-only.
  • Consider listing Azure CLI examples before or alongside PowerShell to avoid Windows-first bias.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are given in detail and are presented before Azure CLI equivalents. File path examples use Windows-style paths (e.g., 'c:\policies\coolAccessTier.json') with no mention of Linux/macOS alternatives. There are no explicit Linux/macOS shell examples, nor are there notes about cross-platform differences in command usage or file paths. The Azure portal instructions are platform-agnostic, but scripting and automation sections favor Windows/PowerShell users.
Recommendations
  • Provide Linux/macOS shell examples (e.g., Bash) alongside PowerShell, especially for file paths and scripting.
  • Use platform-neutral file paths in examples, or show both Windows and Linux/macOS variants.
  • Explicitly state that Azure CLI works cross-platform and highlight any OS-specific considerations.
  • Where PowerShell is used, mention that it is available on Linux/macOS, or link to installation instructions.
  • Consider presenting Azure CLI examples before PowerShell, as CLI is more universally available.
GitHub Create Pull Request
Governance Explore your Azure resources ...overnance/resource-graph/concepts/explore-resources.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all queries, but PowerShell examples are always present and often accompanied by detailed PowerShell-specific notes (e.g., ConvertTo-Json depth). The PowerShell examples are given equal prominence to CLI, and Windows-centric tooling (PowerShell) is referenced throughout. There are no explicit Linux/macOS shell examples (e.g., Bash, zsh), nor is there discussion of Linux-specific patterns or considerations. The CLI examples do use Bash-style command composition (awk, sed), but these are not explained or highlighted for Linux users.
Recommendations
  • Add explicit Bash/zsh examples for Linux/macOS users, especially for multi-step workflows involving file manipulation.
  • Clarify that Azure CLI works cross-platform and note any differences in shell usage between Windows (cmd, PowerShell) and Linux/macOS (Bash/zsh).
  • Provide guidance or links for installing and using Azure CLI and PowerShell on Linux/macOS, if relevant.
  • Where PowerShell-specific notes are given (e.g., ConvertTo-Json), provide equivalent notes for Bash/CLI output parsing.
  • Consider listing CLI/Bash examples before PowerShell examples to reduce perceived Windows-first bias.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides command-line examples exclusively using Azure CLI and Azure PowerShell. While Azure CLI is cross-platform, Azure PowerShell examples are Windows-centric and are always shown alongside or immediately after the CLI, with no mention of Linux/macOS shell equivalents (e.g., Bash scripting, jq for JSON processing). There are no explicit Linux/macOS-specific instructions or examples, and PowerShell-specific patterns (like ConvertTo-Json) are referenced without Linux alternatives.
Recommendations
  • Add explicit Linux/macOS shell examples, such as using Bash with Azure CLI and tools like jq for JSON processing.
  • Clarify that Azure CLI commands work cross-platform, and provide sample output or scripting patterns for Linux/macOS users.
  • When referencing PowerShell-specific commands (e.g., ConvertTo-Json), provide equivalent Bash/jq commands for Linux/macOS.
  • Consider alternating the order of examples, sometimes showing Linux/macOS/Bash first, or grouping by platform.
  • Explicitly state platform compatibility for each tool and example.
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-14 00:00
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 queries across subscriptions, but does not offer equivalent examples for Linux/macOS users (e.g., Azure CLI or REST API). The guidance assumes use of PowerShell, a Windows-centric tool, and omits cross-platform alternatives, creating friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI examples for batching queries across subscriptions.
  • Include REST API sample requests for the same scenario.
  • Explicitly mention cross-platform tools and provide links or code snippets for Linux/macOS users.
  • Reorder examples so that cross-platform tools are presented alongside or before Windows-specific tools.
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-14 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 is Windows-centric, and the sample output is shown in PowerShell format, reinforcing a Windows-first approach. No Linux or macOS alternatives or guidance are mentioned.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for bulk membership management, ensuring cross-platform compatibility.
  • Explicitly mention that the PowerShell script can be run on PowerShell Core (pwsh) on Linux/macOS, or provide instructions for doing so.
  • Provide sample outputs for Azure CLI or Bash workflows, not just PowerShell.
  • Include a note or section on how Linux/macOS users can achieve the same results, referencing tools and patterns common to those platforms.
  • 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) ...ce/includes/policy/azure-policy-guest-configuration.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windows Specific Resource
Summary
The documentation generally provides parity between Azure CLI and Azure PowerShell examples, both of which are cross-platform. However, there is a subtle Windows bias: PowerShell is a Windows-native tool (though available on Linux/macOS), and the documentation always lists PowerShell examples before CLI. Additionally, the 'List machines and status of pending reboot' section only references 'WindowsPendingReboot', with no mention of a Linux equivalent, suggesting Windows-centric resource naming and focus.
Recommendations
  • Alternate the order of Azure CLI and PowerShell examples, or list CLI first to reflect its cross-platform nature.
  • Explicitly mention that both Azure CLI and PowerShell are available on Linux/macOS, and provide any platform-specific notes if needed.
  • For sections like 'pending reboot', clarify whether there is a Linux equivalent (e.g., 'LinuxPendingReboot') and provide examples for both OS types if supported.
  • Audit resource names and queries to ensure Linux scenarios are equally represented, especially where Windows-specific resources are referenced.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation mentions PowerShell as a primary management tool for attestations, listing it before Azure CLI and ARM API. No Linux/macOS-specific examples or tools are provided, and PowerShell is traditionally associated with Windows, potentially creating friction for Linux users.
Recommendations
  • Provide explicit Bash/Azure CLI examples for attestation management tasks.
  • Clarify that Azure CLI is cross-platform and highlight its usage equally or before PowerShell.
  • Mention that PowerShell Core is available on Linux/macOS if referencing PowerShell.
  • Add a section or examples for Linux/macOS users, including installation and usage notes for CLI tools.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a PowerShell-only sample for interacting with the REST API, with no equivalent example for Bash, Azure CLI, or other Linux/macOS-friendly tools. The only scripting example uses Windows-centric tooling, and there is no mention of how Linux/macOS users can perform the same actions, despite the REST API being platform-agnostic.
Recommendations
  • Add a Bash/cURL example for calling the REST API to set hierarchy settings.
  • Include Azure CLI samples if possible, or note their absence and suggest alternatives.
  • Explicitly mention that the REST API can be used from any platform and provide cross-platform guidance.
  • Reorder or parallelize scripting examples so Linux/macOS users are not left out.
GitHub Create Pull Request
Governance How to test machine configuration package artifacts ...ration/how-to/develop-custom-package/3-test-package.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation is heavily PowerShell-centric, with all examples using PowerShell commands and cmdlets. Windows tools (PSExec) are mentioned explicitly, and Windows instructions are consistently presented before Linux equivalents. While Linux is supported, there are no Bash or native Linux shell examples, and macOS is explicitly excluded.
Recommendations
  • Provide native Linux shell (bash) examples where possible, not only PowerShell.
  • Alternate the order of Windows and Linux instructions to avoid implicit prioritization.
  • Mention Linux tools (e.g., pkexec, su) alongside sudo for privilege escalation.
  • Clarify any platform-specific limitations or differences in behavior.
  • Consider referencing cross-platform CI/CD environments and how to test on them.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides command-line examples and instructions that are tailored to Windows environments, such as using mgCreate.exe with backtick line continuations and referencing .exe files. There are no explicit Linux/macOS examples or instructions for running the application, and the documentation does not mention cross-platform considerations for .NET Core applications.
Recommendations
  • Include Linux/macOS-specific instructions for running the published .NET Core application (e.g., mgCreate.dll with 'dotnet mgCreate.dll ...').
  • Show both Windows and Linux/macOS command-line examples, using appropriate line continuation characters (backtick for PowerShell, backslash for Bash).
  • Clarify that .NET Core is cross-platform and note any OS-specific differences in running the application.
  • Explicitly mention how to execute the application on Linux/macOS, including file extensions and invocation methods.
GitHub Create Pull Request
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell examples for generating SAS tokens and accessing Azure Storage, which are primarily Windows-centric. There are no CLI, Bash, or Linux/macOS equivalent commands or instructions. The use of Azure PowerShell modules and lack of cross-platform examples may hinder Linux/macOS users from following the guide easily.
Recommendations
  • Add equivalent Azure CLI examples for generating SAS tokens and accessing blobs, which work natively on Linux/macOS.
  • Include Bash script snippets for common operations where appropriate.
  • Explicitly mention cross-platform compatibility and provide guidance for Linux/macOS users.
  • Clarify any platform-specific requirements or limitations for the steps described.
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-14 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 and include advanced usage notes, while Azure CLI examples are more basic. There is no mention of Linux/macOS-specific considerations or alternative editors.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform support.
  • Provide equally detailed CLI examples, including advanced queries and filtering, similar to PowerShell.
  • Mention that Visual Studio Code and Azure CLI are available on Linux/macOS, and suggest alternative editors if relevant.
  • Explicitly state that all methods (CLI, REST, VS Code) work on Linux/macOS, not just Windows.
  • Add troubleshooting notes or tips for Linux/macOS users where differences may exist.
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-14 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 UI for all steps, which is a web-based tool available on all platforms but is often associated with Windows workflows. There are no command-line examples (Azure CLI, PowerShell, etc.) for assigning policies, creating exemptions, or cleaning up resources. The only mention of cross-platform tools (Azure CLI, PowerShell, ARM templates) is in a warning, which states that exemptions can be created with these tools, but no instructions or examples are provided. There is no guidance for Linux/macOS users who may prefer or require CLI-based workflows.
Recommendations
  • Add step-by-step examples for assigning policies, creating exemptions, and cleaning up resources using Azure CLI and Azure PowerShell.
  • Explicitly mention that Azure CLI is cross-platform and provide sample commands for Linux/macOS users.
  • Where portal screenshots are used, supplement with equivalent CLI/automation instructions.
  • Clarify any platform-specific limitations or differences in behavior between portal and CLI tools.
GitHub Create Pull Request
Governance Troubleshoot common errors ...ain/articles/governance/policy/troubleshoot/general.md
Medium Priority View Details →
Scanned: 2026-01-14 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. Troubleshooting steps for policy evaluation and duplication frequently reference Azure PowerShell, with no mention of Azure CLI or Bash alternatives. The only code sample provided is in PowerShell, and there are no Linux/macOS-specific examples or guidance. Windows tools and patterns (PowerShell, Windows audit policies) are referenced, while Linux equivalents are absent or only implied. This creates friction for Linux/macOS users who may not use PowerShell or Windows-centric workflows.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell, especially for critical tasks like triggering evaluation scans and duplicating policy definitions.
  • Explicitly mention cross-platform tools and workflows (e.g., Azure CLI, REST API via curl, Bash scripting) in troubleshooting steps.
  • Where Windows-specific policies or audit examples are referenced, include Linux equivalents or clarify applicability.
  • Reorder examples so that cross-platform solutions (CLI, REST API) are presented before or alongside Windows/PowerShell solutions.
  • Ensure that all code samples are provided in both PowerShell and CLI/Bash where possible.
GitHub Create Pull Request
← Previous Page 15 of 25 Next →