Automation

123
Total Pages
24
Linux-Friendly Pages
99
Pages with Bias
80.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

982 issues found
Showing 101-125 of 982 flagged pages
Automation Quickstart: Use Terraform to create an Azure Automation account ...ickstarts/create-azure-automation-account-terraform.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is given equal prominence and is referenced in the 'Next steps' section. The tutorial for further learning is focused on creating a PowerShell runbook, which is a Windows-centric automation pattern. There are no Linux shell (bash) or cross-platform scripting examples, and the documentation references Windows tools (PowerShell) without mentioning Linux alternatives or parity.
Recommendations
  • Add bash/Linux shell examples alongside Azure CLI and PowerShell for verifying results.
  • In the 'Next steps' section, include links to tutorials for creating Python or bash runbooks, not just PowerShell.
  • Explicitly mention that Azure CLI works cross-platform and provide guidance for Linux/macOS users.
  • Where PowerShell is referenced, note its availability on Linux and macOS, or provide equivalent bash commands.
  • Ensure that automation patterns and examples are not exclusively focused on Windows tools.
GitHub Create Pull Request
Automation Azure Quickstart - Install Hybrid Worker extension on Azure portal. ...omation/quickstarts/install-hybrid-worker-extension.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on installing the Hybrid Worker extension on Windows Azure Virtual Machines. The step-by-step instructions, screenshots, and extension selection all reference 'Windows Hybrid Worker', with no equivalent guidance or visuals for Linux VMs. Prerequisites and installation steps mention only Windows, omitting Linux-specific instructions, extension names, or considerations. The documentation does not provide parity for Linux users, despite mentioning Linux support in the introduction.
Recommendations
  • Add explicit instructions and screenshots for installing the Hybrid Worker extension on Linux Azure Virtual Machines.
  • Include the Linux-specific extension name and any differences in configuration or prerequisites for Linux VMs.
  • Present Windows and Linux examples side-by-side or in parallel sections to ensure equal visibility and usability.
  • Clarify any platform-specific limitations or requirements in the prerequisites section.
  • Ensure that all referenced links and next steps provide clear Linux guidance where applicable.
GitHub Create Pull Request
Automation Remove user-assigned managed identity for Azure Automation account ...n/articles/automation/remove-user-assigned-identity.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by providing only PowerShell examples for command-line and scripting operations, referencing Windows-centric tools and cmdlets (e.g., Set-AzAutomationAccount, Invoke-RestMethod), and omitting equivalent Linux-friendly instructions (such as Azure CLI or curl). Steps for REST API usage are shown exclusively with PowerShell, and verification steps also rely on PowerShell. No Bash, Azure CLI, or cross-platform shell examples are provided.
Recommendations
  • Add equivalent Azure CLI examples for all operations shown with PowerShell, including authentication, resource modification, and verification.
  • Provide REST API invocation examples using curl or httpie, which are standard on Linux and macOS.
  • Include Bash script snippets alongside PowerShell, especially for variable assignment and file manipulation.
  • Clarify that PowerShell examples can be run on Linux/macOS with PowerShell Core, or explicitly note platform requirements.
  • Reorder sections or provide parallel examples so that Linux-friendly methods (Azure CLI, Bash, curl) are presented alongside or before Windows/PowerShell methods.
  • Reference cross-platform tools and patterns where possible, reducing reliance on Windows-only cmdlets.
GitHub Create Pull Request
Automation Runtime Environment in Azure Automation ...in/articles/automation/runtime-environment-overview.md
High Priority View Details →
Scanned: 2026-01-12 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 demonstrates a Windows bias by prioritizing PowerShell as the primary scripting language, referencing multiple PowerShell versions, and focusing on Windows-centric tools and patterns. Azure CLI is only discussed in the context of PowerShell 7.4, with no mention of Bash or Linux shell usage. Package management examples and system-generated environments are centered around PowerShell and Python, with PowerShell always listed first. There are no Linux-specific examples, nor is there guidance for users who prefer Bash or other Linux-native tools.
Recommendations
  • Include examples and guidance for using Bash scripts and Linux shell environments in Azure Automation.
  • Discuss Azure CLI usage in the context of Bash or Linux environments, not just PowerShell.
  • List scripting languages and runtime environments in a neutral order (e.g., alphabetical) rather than always putting PowerShell first.
  • Provide parity in package management instructions for both PowerShell (PSGallery) and Python (PyPI), and mention Linux-native package sources where relevant.
  • Add links to Linux shell scripting documentation alongside PowerShell references.
  • Clarify support for Linux-based runbooks and environments, including any limitations or best practices.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
High Priority View Details →
Scanned: 2026-01-12 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. It focuses almost exclusively on PowerShell cmdlets and Windows-centric tools for credential management in Azure Automation. All code examples outside of Python are PowerShell-based, and there are no Bash, CLI, or Linux-native examples. The creation and management of credentials are described using Windows PowerShell and related modules, with no mention of Linux shell equivalents or cross-platform Azure CLI usage. The documentation assumes familiarity with Windows/PowerShell patterns and tools, and does not provide parity for Linux users.
Recommendations
  • Add Azure CLI examples for credential management, including creation, retrieval, and deletion of credentials.
  • Include Bash or shell script examples where applicable, especially for runbook scenarios.
  • Explicitly mention cross-platform support and provide guidance for Linux/macOS users.
  • List Linux-compatible tools and modules alongside PowerShell cmdlets, and clarify any platform limitations.
  • Reorder sections or provide parallel instructions so that Windows and Linux approaches are presented equally.
GitHub Create Pull Request
Automation Manage modules in Azure Automation ...b/main/articles/automation/shared-resources/modules.md
High Priority View Details →
Scanned: 2026-01-12 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 is heavily focused on PowerShell modules and Windows-centric workflows. Examples, tools, and instructions are almost exclusively PowerShell-based, with explicit references to Windows PowerShell features (such as Import-Module, using module statement, and Windows-specific cmdlets). Internal cmdlets and modules are noted as unavailable on Linux Hybrid Runbook Workers, but no Linux alternatives or parity guidance is provided. Python modules are mentioned briefly, but without examples or integration guidance. There are no Linux shell (bash, CLI) examples, and the overall structure assumes a Windows-first approach.
Recommendations
  • Provide equivalent Linux/Unix examples for module management, such as using Azure CLI or bash scripts.
  • Clarify which features and modules are supported on Linux Hybrid Runbook Workers, and offer alternatives or workarounds where functionality is missing.
  • Include guidance and examples for managing Python modules and runbooks on Linux, with parity to PowerShell workflows.
  • Add explicit notes or tables comparing Windows and Linux support for each module and cmdlet.
  • Where internal cmdlets are unavailable on Linux, suggest alternative approaches for Linux users.
  • Balance the documentation by introducing Linux-first or cross-platform sections, and ensure that instructions do not assume Windows as the default environment.
GitHub Create Pull Request
Automation Manage variables in Azure Automation ...main/articles/automation/shared-resources/variables.md
High Priority View Details →
Scanned: 2026-01-12 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. PowerShell is presented as the primary scripting interface, with cmdlets and examples focused exclusively on Windows PowerShell and Az modules. Windows terminology (e.g., 'Windows Hybrid Runbook Worker') is used throughout, and there are no Bash, CLI, or Linux-native examples or references. The documentation does not mention or provide parity for Linux shell scripting, nor does it discuss how to manage variables from Linux environments or with cross-platform tools. Python examples are included, but only in the context of Azure Automation runbooks, not general Linux usage.
Recommendations
  • Add Azure CLI examples for variable management, showing equivalent operations to PowerShell cmdlets.
  • Include Bash shell scripting examples for accessing and managing variables, especially for Linux Hybrid Runbook Workers.
  • Clarify cross-platform compatibility of cmdlets and tools, and explicitly mention Linux support where applicable.
  • Reorder sections so that platform-neutral or cross-platform approaches (e.g., Azure CLI, REST API) are presented before Windows-specific tools.
  • Add notes or guidance for Linux users, including any prerequisites or differences in workflow.
  • Avoid using 'Windows PowerShell' as the default term; use 'PowerShell' or specify when instructions are platform-specific.
GitHub Create Pull Request
Automation Use Source Control Integration in Azure Automation ...main/articles/automation/source-control-integration.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a strong Windows and PowerShell bias. All command-line examples use PowerShell, with no mention of Bash, Azure CLI, or Linux-native tooling. The only scripting language supported for source control integration is PowerShell 5.1, and all automation and configuration steps are shown using PowerShell cmdlets. There are no Linux or cross-platform examples, and the documentation assumes the user is operating in a Windows/PowerShell environment.
Recommendations
  • Provide equivalent Azure CLI and/or Bash examples for all PowerShell commands, especially for role assignment and source control configuration.
  • Explicitly state platform support and limitations (e.g., clarify if Linux-based runbooks or Python runbooks can be synchronized).
  • Include guidance for users working on Linux or macOS, such as using Azure CLI or REST API for automation tasks.
  • Mention cross-platform tools and editors (e.g., VS Code on Linux/macOS) in sections about encoding and editing runbooks.
  • If PowerShell is required, clarify that PowerShell Core (pwsh) is available cross-platform and provide examples for non-Windows environments.
GitHub Create Pull Request
Automation Start a runbook in Azure Automation ...e-docs/blob/main/articles/automation/start-runbooks.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell examples and referencing Windows PowerShell cmdlets as the primary command-line method for starting runbooks. There are no examples or mentions of Linux-native tools, Bash, Azure CLI, or cross-platform scripting approaches. The documentation assumes the use of PowerShell and Windows-centric workflows, omitting guidance for Linux users or those using non-PowerShell environments.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
  • Include Bash scripting samples for starting runbooks via the Azure Automation API.
  • Explicitly mention that PowerShell Core is available on Linux/macOS and clarify compatibility.
  • Provide guidance or links for Linux users on installing and using Azure Automation tools.
  • Reorder sections to present cross-platform or platform-neutral methods (such as Azure CLI or REST API) before Windows-specific tools.
  • Highlight platform differences and considerations for both Windows and Linux users.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation runbook issues ...blob/main/articles/automation/troubleshoot/runbooks.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page is heavily focused on PowerShell-based troubleshooting and examples, with nearly all code samples, cmdlet references, and troubleshooting steps using PowerShell or Windows-centric tools (e.g., PowerShell ISE, Windows Management Instrumentation). There is little to no mention of Linux-specific tools, shell environments, or cross-platform scripting approaches, and Linux alternatives are not provided or referenced. Python is mentioned only briefly, and no Linux shell (bash) examples or troubleshooting patterns are given.
Recommendations
  • Provide equivalent troubleshooting steps and examples for Linux environments, including bash or Python scripts where applicable.
  • Include guidance for users running Azure Automation runbooks from Linux machines, such as using Azure CLI, bash, or Python.
  • Reference cross-platform tools (e.g., VS Code, Azure CLI) and clarify when steps are OS-agnostic.
  • Add explicit notes or sections for Linux users, highlighting differences in module installation, authentication, and error handling.
  • Ensure that troubleshooting steps do not assume the use of PowerShell or Windows-only tools, or provide alternatives for Linux users.
  • Where PowerShell is required, mention PowerShell Core (pwsh) and its cross-platform capabilities, and provide examples for Linux/macOS.
GitHub Create Pull Request
Automation Configure machines to a desired state in Azure Automation ...automation/tutorial-configure-servers-desired-state.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows and PowerShell. All examples use Windows-centric DSC resources (e.g., WindowsFeature IIS), and all command-line instructions are given in PowerShell. Prerequisites and links focus on Windows VMs and Windows PowerShell DSC, with no Linux configuration examples or equivalent Linux tooling mentioned. The retirement announcement for Linux DSC is included, but there is no guidance or parity for Linux users.
Recommendations
  • Add explicit Linux onboarding/configuration examples, using Linux DSC resources (if still supported) or alternatives.
  • Include Bash/CLI examples where possible, or clarify cross-platform support and alternatives for Linux users.
  • Mention Linux VM creation and configuration in prerequisites and link to relevant documentation.
  • If Linux DSC is deprecated, provide migration guidance or alternatives for Linux configuration management (e.g., Ansible, Chef, native Azure solutions).
  • Balance references to Windows tools (PowerShell, WindowsFeature) with Linux equivalents or alternatives.
GitHub Create Pull Request
Automation Remove DSC and node from Automation State Configuration ...configuration/remove-node-and-configuration-package.md
High Priority View Details →
Scanned: 2026-01-12 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 demonstrates a Windows bias by prioritizing PowerShell-based instructions and cmdlets, mentioning Windows tools and patterns first, and providing more detailed steps for Windows nodes. Linux instructions are present but less detailed, sometimes only referencing file deletion or external resources, and Linux command examples are limited to package removal rather than configuration management.
Recommendations
  • Provide equivalent Linux command-line examples for unregistering nodes and deleting configurations, such as using shell scripts or CLI commands.
  • Include Linux-specific tooling or automation steps (e.g., omicli, systemctl for OMI/DSC services) alongside PowerShell examples.
  • Ensure that Linux instructions are as detailed as Windows instructions, with step-by-step guidance and screenshots where appropriate.
  • Present Windows and Linux instructions in parallel or in clearly separated sections to avoid implicit prioritization.
  • Reference Linux documentation and resources directly within the main content, not only as external links.
GitHub Create Pull Request
Automation Troubleshoot extension-based Hybrid Runbook Worker issues in Azure Automation .../troubleshoot/extension-based-hybrid-runbook-worker.md
High Priority View Details →
Scanned: 2026-01-12 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. In many troubleshooting steps and scenarios, Windows instructions, tools, and PowerShell examples are presented first or in greater detail than their Linux equivalents. Windows-specific tools (such as PowerShell scripts, registry edits, and references to Windows services and event logs) are frequently mentioned, sometimes without parallel Linux guidance. Some scenarios (e.g., registry and folder permissions, event log troubleshooting) are Windows-only, and Linux troubleshooting is less detailed or omitted in those cases.
Recommendations
  • Present Linux and Windows instructions in parallel, with equal detail and prominence.
  • Where Windows-specific tools (e.g., PowerShell scripts, registry edits) are referenced, provide Linux equivalents (e.g., bash scripts, config file locations, systemd service management) or note their absence.
  • Include Linux-specific troubleshooting for scenarios currently covered only for Windows (e.g., permissions, log analysis, service management).
  • Add Linux examples for event log analysis, resource monitoring, and authentication troubleshooting.
  • Ensure that Linux troubleshooting steps are as detailed and actionable as Windows steps.
  • Where possible, use OS-agnostic terminology and structure to avoid implicit prioritization of Windows.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation managed identity issues ...n/articles/automation/troubleshoot/managed-identity.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a strong Windows bias. All troubleshooting examples and code snippets use PowerShell cmdlets (e.g., Connect-AzAccount, Get-AzVM, Invoke-RestMethod), which are native to Windows and not available by default on Linux. There are no Bash, Azure CLI, or Python examples, nor any mention of Linux-specific troubleshooting patterns or tools. The documentation implicitly assumes the user is running runbooks or troubleshooting from a Windows environment, and does not address Linux automation scenarios or provide parity for Linux users.
Recommendations
  • Add equivalent troubleshooting steps and code examples using Azure CLI (az), Bash scripts, or Python SDK to support Linux users.
  • Explicitly mention how to perform managed identity troubleshooting from Linux environments, including any differences in authentication or error messages.
  • Where PowerShell cmdlets are referenced, provide side-by-side examples for Azure CLI and/or REST API calls.
  • Clarify which steps or commands are platform-specific and offer alternatives for Linux/macOS users.
  • Include notes or links to installing PowerShell Core on Linux if PowerShell is required, or recommend native Linux tools where possible.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation shared resource issues ...n/articles/automation/troubleshoot/shared-resources.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily focused on PowerShell-based troubleshooting and examples, which are primarily relevant to Windows environments. All code samples and cmdlet references use PowerShell syntax and Windows-centric tools (e.g., Remove-AzAutomationModule, Update-AzureModule.ps1). There are no equivalent examples or guidance for Linux users, such as using Azure CLI, Bash, or cross-platform scripting. Windows-specific DLL errors are discussed without mention of Linux error patterns or troubleshooting steps.
Recommendations
  • Provide equivalent troubleshooting steps and examples using Azure CLI and Bash scripts for Linux users.
  • Include cross-platform guidance for module management, such as using REST API or Azure CLI commands.
  • Mention Linux-specific error messages or scenarios where applicable, and how to resolve them.
  • Clarify which steps or tools are Windows-only and offer alternatives for Linux/macOS environments.
  • Add notes or sections explicitly addressing Linux automation environments and their unique considerations.
GitHub Create Pull Request
Automation Create a standalone Azure Automation account ...les/automation/automation-create-standalone-account.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by predominantly featuring PowerShell examples and references, with no equivalent examples for Linux or Bash. The only CLI automation example provided is via Azure PowerShell, and all runbook tutorials referenced in 'Next steps' prioritize PowerShell before Python. There is no mention of Bash, Azure CLI, or Linux-specific workflows, nor are there instructions for creating or managing Automation accounts using Linux tools or shell environments.
Recommendations
  • Add Azure CLI examples for creating and managing Automation accounts, alongside PowerShell examples.
  • Include Bash shell script examples for key operations, such as rotating access keys.
  • Provide parity in runbook tutorials by featuring Python and Bash runbooks equally with PowerShell.
  • Explicitly mention Linux and cross-platform usage in relevant sections, including screenshots from Linux environments.
  • Reference both PowerShell and Azure CLI documentation in 'Next steps' and throughout the page.
GitHub Create Pull Request
Automation Set up Azure Automation continuous deployment with Chocolatey ...in/articles/automation/automation-dsc-cd-chocolatey.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, with all examples, commands, and tooling centered around Windows, PowerShell, and Chocolatey. Linux is only mentioned in passing, and there are no Linux-specific instructions, examples, or alternatives provided. The workflow assumes Windows VMs and Windows-specific tools (PowerShell DSC, Chocolatey, Windows Management Framework), with no parity for Linux users or environments.
Recommendations
  • Add equivalent examples and instructions for Linux environments, such as using apt, yum, or other Linux package managers.
  • Provide guidance on setting up Azure Automation State Configuration for Linux VMs, including any supported alternatives to PowerShell DSC.
  • Include Linux-specific VM extension instructions and configuration samples.
  • Mention and document cross-platform package management and configuration tools where possible.
  • Clarify the current support status for Linux in Azure Automation State Configuration, and suggest alternatives if Linux support is deprecated.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting Windows-specific guidance and tools (such as PowerShell cmdlets) before or instead of Linux equivalents. Windows registry settings and PowerShell cmdlets are referenced multiple times, while Linux instructions are less detailed, less frequent, and sometimes missing entirely. Examples and export/backup procedures are almost exclusively shown for Windows/PowerShell, with Linux alternatives rarely mentioned or omitted.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for backup/export operations (e.g., how to export runbooks, DSC configurations, and assets using Linux tools or CLI).
  • Include references to cross-platform tools (such as Azure CLI or REST API) for operations currently described only with PowerShell cmdlets.
  • Ensure Linux guidance is as detailed as Windows guidance, including step-by-step instructions and troubleshooting tips.
  • List Linux and Windows options together in tables and explanations, rather than presenting Windows first or exclusively.
  • Where PowerShell is referenced, also mention Bash, Python, or other Linux-native scripting options if available.
GitHub Create Pull Request
Automation Send an email from an Azure Automation runbook ...blob/main/articles/automation/automation-send-email.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively uses PowerShell for all examples and instructions, including setup, configuration, and runbook authoring. There are no examples or guidance for Linux users, such as using Python runbooks, Bash scripts, or Azure CLI equivalents. Windows-centric tools and patterns (e.g., PowerShell cmdlets, references to the Azure Az PowerShell module) are mentioned exclusively and before any cross-platform alternatives, which are not present at all.
Recommendations
  • Provide equivalent examples using Python runbooks, which are supported in Azure Automation and are platform-agnostic.
  • Include instructions and code snippets using Azure CLI for resource creation and management tasks (e.g., creating Key Vaults, assigning permissions), as Azure CLI is cross-platform.
  • Add Bash script examples for users who prefer shell scripting, especially for automation tasks.
  • Clearly indicate that PowerShell examples work on both Windows and Linux in Azure Automation, but also offer alternatives for users who may want to develop and test scripts locally on Linux/macOS.
  • Reference cross-platform tools and modules (such as Azure CLI and REST API) alongside PowerShell, not just as an afterthought or in separate documentation.
  • Consider reordering sections or providing parallel tracks so that Linux and cross-platform users do not feel secondary to Windows/PowerShell users.
GitHub Create Pull Request
Automation Manage connections in Azure Automation ...lob/main/articles/automation/automation-connections.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples for creating and managing connections use PowerShell cmdlets, with no equivalent Bash, Azure CLI, or Linux-native examples. The terminology and tooling (e.g., 'Windows PowerShell', 'cmdlet', 'hashtable') are Windows-centric. The Python section is present, but only for runbooks, not for general connection management. There are no Linux shell or Azure CLI examples for managing connections, and the PowerShell approach is always presented first and in greater detail.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlet operations (create, get, remove, set connection).
  • Include Bash/shell script examples for common connection management tasks.
  • Use neutral language such as 'PowerShell' instead of 'Windows PowerShell' unless specifically required.
  • Present cross-platform options (PowerShell, CLI, Python) in parallel tabs or sections, not always leading with PowerShell.
  • Explicitly mention Linux/macOS compatibility and provide guidance for users on those platforms.
  • Where possible, clarify which features/tools are cross-platform and which are Windows-specific.
GitHub Create Pull Request
Automation Run Azure Automation Runbooks on a Hybrid Runbook Worker ...ain/articles/automation/automation-hrw-run-runbooks.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several forms of Windows bias. Windows instructions and examples are consistently presented before Linux equivalents, and Windows-specific tools (such as PowerShell cmdlets, Windows environment variable dialogs, and certificate management) are described in greater detail. PowerShell is the primary language for runbook examples, with no Linux shell or Python examples provided for equivalent tasks. Some features, such as Hybrid Worker Credentials and signed runbooks, are described as unsupported or less capable on Linux, but without offering alternative Linux-native solutions or workarounds. Additionally, references to file paths, permissions, and troubleshooting are more detailed for Windows than for Linux.
Recommendations
  • Present Linux instructions and examples alongside or before Windows equivalents to ensure parity.
  • Provide Linux shell (bash) and Python examples for runbook tasks, authentication, and starting runbooks, not just PowerShell.
  • Include Linux-native tools and workflows (e.g., using OpenSSL for certificates, systemd for service management) where appropriate.
  • Expand Linux troubleshooting and logging sections to match the detail provided for Windows.
  • Clarify any feature gaps for Linux and suggest alternative approaches or workarounds.
  • Ensure that credential management and signed runbook workflows are described for Linux with step-by-step instructions, not just for Windows.
  • Where PowerShell is used, note cross-platform compatibility or provide equivalent bash/Python commands for Linux users.
GitHub Create Pull Request
Automation Azure Automation account authentication overview ...in/articles/automation/automation-security-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing PowerShell cmdlets as the default automation method and omitting equivalent Linux or cross-platform scripting examples. There is no mention of Bash, Python, or other Linux-native tools, nor are there examples or instructions for Linux environments. The documentation implicitly assumes Windows as the primary platform for Azure Automation, especially in sections discussing runbooks and authentication.
Recommendations
  • Include examples using Bash, Python, or other Linux-native scripting languages for Azure Automation tasks.
  • Explicitly mention cross-platform support and provide guidance for both Windows and Linux users.
  • Reference Azure CLI commands alongside PowerShell cmdlets where applicable.
  • Add instructions or links for setting up Hybrid Runbook Workers on Linux machines, not just Azure VMs (which are often Windows-based).
  • Clarify that runbooks can be authored and executed in multiple languages and environments, and provide parity in documentation for Linux users.
GitHub Create Pull Request
Automation Delete an Azure Automation Run As account ...blob/main/articles/automation/delete-run-as-account.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page focuses on deleting Azure Automation Run As accounts, but only mentions PowerShell and the Azure portal as methods, both of which are Windows-centric. There are no examples or instructions for Linux users, such as using Azure CLI or Bash. The documentation implicitly prioritizes Windows tools and patterns, lacking parity for Linux environments.
Recommendations
  • Add Azure CLI examples for deleting Run As accounts, suitable for Linux and macOS users.
  • Include Bash script samples alongside PowerShell instructions.
  • Explicitly mention cross-platform tools and clarify which steps are platform-agnostic.
  • Reorder examples so that platform-neutral or Linux-compatible methods are presented before or alongside Windows-specific ones.
GitHub Create Pull Request
Automation Migrate from Orchestrator to Azure Automation (Beta) ...ticles/automation/automation-orchestrator-migration.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All examples and tooling references are centered around Windows PowerShell, with no mention of Linux alternatives or cross-platform scripting. The conversion process, modules, and cmdlets are described exclusively in the context of Windows environments, and there are no Linux shell (e.g., Bash) or platform-neutral examples. Windows tools and patterns (such as PowerShell cmdlets and Windows file paths) are used throughout, and Linux or cross-platform automation scenarios are not addressed.
Recommendations
  • Include examples using Bash or other Linux shells where applicable, especially for importing/exporting runbooks or managing assets.
  • Clarify whether Azure Automation and the migration toolkit support Linux-based runbooks or cross-platform scripting, and provide guidance for Linux users.
  • Mention any limitations or considerations for users migrating from Orchestrator who operate in Linux environments.
  • Provide parity in documentation by listing Linux-compatible tools and modules, or explicitly state if the process is Windows-only.
  • Add notes or sections for users who may want to automate tasks using Python or other cross-platform languages supported by Azure Automation.
GitHub Create Pull Request
Automation Migrate from a Run As account to Managed identities ...automation/migrate-run-as-accounts-managed-identity.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a strong Windows bias. All code examples, instructions, and tooling references are exclusively PowerShell-based, which is primarily a Windows-centric automation language. There are no examples or guidance for Linux environments, such as Bash, Python, or CLI usage. The documentation assumes the use of PowerShell modules (Az, AzureRM) and Windows-style scripting patterns, and does not mention or prioritize Linux-native tools or workflows. This may hinder users who operate Azure Automation from Linux environments or prefer cross-platform scripting languages.
Recommendations
  • Add equivalent examples using Azure CLI (az), Bash, or Python to demonstrate managed identity authentication and resource management from Linux environments.
  • Explicitly mention cross-platform support for Azure Automation and managed identities, clarifying which features and scripts work on Linux and which are Windows-only.
  • Provide guidance for setting up and migrating runbooks that use Bash or Python scripts, including authentication flows for managed identities.
  • Include troubleshooting and migration steps for Linux hybrid runbook workers, not just Windows-based ones.
  • Reorder or balance examples so that Linux and cross-platform approaches are presented alongside or before Windows/PowerShell methods, where applicable.
GitHub Create Pull Request
← Previous Page 5 of 40 Next →