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 76-100 of 982 flagged pages
Automation Automation services in Azure - overview ...s/blob/main/articles/automation/automation-services.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 exhibits a Windows bias in several ways: PowerShell is repeatedly emphasized as the primary automation scripting language, with frequent references to PowerShell runbooks, modules, and integration. Windows-centric tools and concepts (e.g., registry, Active Directory, SQL Server) are mentioned more often than Linux equivalents. Examples and scenarios tend to focus on Windows environments, with little explicit mention of Linux-specific automation patterns, tools, or shell scripting. Although some services claim Linux support, practical Linux usage examples or references to Linux-native tools (e.g., Bash, systemd, cron) are missing.
Recommendations
  • Provide explicit Linux automation examples, such as Bash or Python runbooks, and reference Linux shell scripting in addition to PowerShell.
  • Mention Linux-native tools and concepts (e.g., systemd, cron, package managers) when discussing configuration and update management.
  • Balance references to Windows-specific technologies (e.g., registry, Active Directory) with Linux equivalents (e.g., /etc files, LDAP, system logs).
  • Include Linux-focused scenarios in tables and user stories, such as automating patching or configuration drift detection on Ubuntu or CentOS servers.
  • Clarify cross-platform capabilities in Azure Automation, Logic Apps, and Functions, and provide links to Linux documentation where relevant.
GitHub Create Pull Request
Automation Migration guidance from Change Tracking and inventory using Log Analytics to Azure Monitoring Agent ...g/guidance-migration-log-analytics-monitoring-agent.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 demonstrates several Windows biases. PowerShell is the only scripting method provided for bulk migration, with no equivalent Bash or Linux-native script. Windows-specific concepts (e.g., registry, Windows services) are mentioned before Linux equivalents, and the migration script parameters and prerequisites are PowerShell-centric. There are no Linux command-line examples or explicit Linux onboarding steps outside of the generic Azure portal workflow. Windows terminology and tools are referenced more frequently and prominently than Linux ones.
Recommendations
  • Provide Bash or shell script examples for Linux users, especially for bulk migration scenarios.
  • Include Linux-specific onboarding steps and screenshots where applicable, not just generic portal instructions.
  • List Linux data types (e.g., daemons, files) alongside Windows types, and avoid Windows-first ordering.
  • Reference Linux-native tools and commands (e.g., az CLI, systemd) where relevant, not just PowerShell.
  • Ensure all instructions and prerequisites explicitly mention Linux compatibility and provide parity in detail.
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-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 exclusively uses PowerShell for all examples, setup, and automation steps, with no mention of Bash, CLI, or Python alternatives. All code snippets, module requirements, and instructions are tailored for PowerShell and the Azure Az PowerShell module, which are more commonly associated with Windows environments. There are no Linux shell (Bash) or cross-platform scripting examples, and the documentation does not address how to perform these tasks using the Azure CLI or other non-Windows tools. The structure and language assume familiarity with Windows/PowerShell paradigms, contributing to a strong Windows bias.
Recommendations
  • Provide equivalent examples using Azure CLI (az commands) and Bash scripts for all major steps, including Key Vault creation, secret management, and role assignments.
  • Include a section or parallel instructions for creating and running runbooks using Python, which is supported in Azure Automation and is cross-platform.
  • Mention that Azure Automation supports both PowerShell and Python runbooks, and show how to select the runbook type accordingly.
  • Reference Linux/macOS environments explicitly, including any prerequisites or differences in module installation or authentication.
  • Where PowerShell modules are required, note any cross-platform compatibility or provide alternatives for users on Linux/macOS.
  • Ensure that tool and command references do not assume a Windows environment by default, and avoid presenting Windows-specific tools or patterns before their cross-platform equivalents.
GitHub Create Pull Request
Automation Start an Azure Automation Runbook from a Webhook ...s/blob/main/articles/automation/automation-webhooks.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 demonstrates a strong Windows bias. All code examples and instructions use PowerShell, a Windows-centric tool, and reference Windows file paths (e.g., 'path\names.json'). There are no examples using Bash, curl, or other Linux-native tools. REST API usage is shown only via PowerShell's Invoke-RestMethod. The documentation does not mention or show how to perform these tasks from Linux or macOS environments, nor does it provide parity for non-Windows users.
Recommendations
  • Add equivalent examples using Bash and curl for creating, invoking, and deleting webhooks.
  • Show how to use Azure CLI (az) for all operations, as it is cross-platform.
  • Include Linux/macOS file path conventions in examples (e.g., '/home/user/names.json').
  • Demonstrate REST API calls using curl or httpie, not just PowerShell.
  • Clarify that PowerShell Core is available cross-platform, but provide examples for both Windows PowerShell and PowerShell Core on Linux/macOS.
  • Explicitly mention platform compatibility and provide troubleshooting tips for Linux/macOS users.
GitHub Create Pull Request
Automation Compose DSC configurations ...omation/compose-configurationwithcompositeresources.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 is heavily oriented towards Windows and PowerShell. All examples and terminology (e.g., 'PSExecutionPolicy', '[PSCredential]', PowerShell cmdlets) are Windows-centric, with no Linux equivalents or examples provided. The mention of Chocolatey (a Windows package manager) further reinforces the Windows bias. Additionally, the inclusion of a Linux retirement announcement suggests diminishing support for Linux, but no alternative guidance is offered for Linux users.
Recommendations
  • Provide equivalent Linux examples for composing DSC configurations, including references to Linux-specific resources and parameters.
  • Include guidance or links for Linux users on how to achieve similar configuration management, possibly with other tools or Azure features.
  • Mention Linux tools and patterns (such as native shell scripts or Ansible) where appropriate, and avoid assuming PowerShell is the only option.
  • Ensure that examples and screenshots include both Windows and Linux scenarios, or clarify platform limitations explicitly.
  • If Linux support is deprecated, offer migration paths or alternatives 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-12 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 primarily through PowerShell and the Azure portal, both of which are Windows-centric tools. There are no examples or instructions for Linux users (e.g., using Azure CLI, Bash, or other cross-platform tools). The mention of PowerShell and portal actions comes before any consideration of Linux alternatives, and no Linux-specific guidance is provided.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and commonly used on Linux.
  • Include Bash script examples for deleting Run As accounts, if applicable.
  • Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI or other supported tools.
  • Ensure that any references to PowerShell are balanced with references to cross-platform alternatives.
  • Add a section or note for Linux/macOS users to clarify platform compatibility.
GitHub Create Pull Request
Automation Context switching in Azure Automation ...ocs/blob/main/articles/automation/context-switching.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 exclusively uses PowerShell examples and Windows-centric Azure PowerShell cmdlets (Az, AzureRM) for context switching in Azure Automation. There are no references to Linux-native tools, Bash, CLI, or cross-platform scripting approaches. The guidance and code samples assume a Windows/PowerShell environment, which may disadvantage Linux users or those using Azure CLI.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands for context management and runbook authentication.
  • Include Bash or Python runbook snippets to demonstrate context switching in non-PowerShell environments.
  • Explicitly mention cross-platform support and clarify which recommendations apply to Linux-based runbooks.
  • Reference Linux tools and patterns (e.g., environment variables, service principals via CLI) alongside PowerShell guidance.
  • Reorder sections or provide parallel guidance so Linux/CLI approaches are presented equally or before Windows/PowerShell methods.
GitHub Create Pull Request
Automation Manage your Azure Automation account ...e-docs/blob/main/articles/automation/delete-account.md
High Priority View Details →
Scanned: 2026-01-12 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 page demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, with no equivalent Azure CLI or bash examples. The use of PowerShell cmdlets is emphasized for automation and solution removal tasks, and there is no mention of Linux shell commands or cross-platform scripting approaches. Additionally, the PowerShell examples are presented before any mention of Azure CLI, and the portal instructions reference Windows-centric UI patterns. This limits accessibility for users on Linux or macOS platforms.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations, such as deleting Automation accounts and removing solutions.
  • Include bash shell script examples where applicable to demonstrate cross-platform automation.
  • Explicitly mention that both PowerShell and Azure CLI are supported on Windows, Linux, and macOS, and provide guidance for installing and using these tools on non-Windows platforms.
  • Ensure that references to the Azure portal UI do not assume a Windows environment, and clarify that the portal is accessible from any modern browser on any OS.
  • Consider reordering examples so that Azure CLI and PowerShell are presented together, or alternate which is shown first, to avoid implicit prioritization of Windows tools.
GitHub Create Pull Request
Automation Disable local authentication in Azure Automation ...in/articles/automation/disable-local-authentication.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 demonstrates a strong Windows bias by exclusively providing PowerShell examples and referencing Windows-centric tools (e.g., PowerShell cmdlets like Invoke-AzRestMethod and Get-AzAutomationAccount). No Linux shell (bash, curl, az CLI) examples are given, nor are Linux workflows or tools mentioned. The instructions and verification steps are written for PowerShell users, implicitly prioritizing Windows environments and leaving Linux users without direct guidance.
Recommendations
  • Add equivalent examples using Azure CLI (az) and REST API calls via curl for Linux/macOS users.
  • Explicitly mention that the PowerShell examples are for Windows and provide parallel instructions for Linux environments.
  • Include verification steps using az CLI or curl to check the disableLocalAuth property.
  • Reference cross-platform tools and patterns before or alongside Windows-specific ones.
  • Add a note about platform compatibility and recommend tools for both Windows and Linux users.
GitHub Create Pull Request
Automation Using a system-assigned managed identity for an Azure Automation account ...s/automation/enable-managed-identity-for-automation.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 and PowerShell bias. All code examples for enabling and using managed identity (including REST API, ARM template deployment, role assignment, authentication, and resource access) are provided exclusively in PowerShell, with only one Python example (for runbooks) and no Bash, CLI, or Linux-native scripting alternatives. Windows/PowerShell tools and patterns (e.g., New-Object, Invoke-RestMethod, Windows file paths) are used throughout, and instructions for checking Hybrid Runbook Worker versions list Windows before Linux. There is no mention of Azure CLI, Bash, or Linux shell commands for any of the main workflows.
Recommendations
  • Add Azure CLI and Bash examples for all major workflows (enabling managed identity, assigning roles, authenticating, accessing resources).
  • Include Linux-native instructions and file paths where applicable, especially for REST API and ARM template deployment steps.
  • Present Linux and Windows instructions in parallel, or alternate their order to avoid 'windows_first' bias.
  • Expand Python and other cross-platform runbook examples beyond the single Python snippet.
  • Reference Linux tools and patterns (e.g., curl, jq, az CLI) alongside PowerShell equivalents.
  • Ensure troubleshooting and migration sections include Linux/CLI guidance, not just PowerShell.
GitHub Create Pull Request
Automation Disable system-assigned managed identity for Azure Automation account .../automation/disable-managed-identity-for-automation.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 provides detailed PowerShell-based instructions for disabling a system-assigned managed identity in Azure Automation, including use of Windows-specific tools and cmdlets. No equivalent Linux or cross-platform CLI examples (such as Azure CLI, curl, or bash scripts) are provided, and the PowerShell workflow is presented as the only programmatic option after the REST API section. This creates a bias toward Windows users and leaves Linux users without clear guidance.
Recommendations
  • Add equivalent Azure CLI examples for authentication and REST API invocation, which work on both Windows and Linux.
  • Provide curl or bash script examples for sending PATCH requests to the REST API.
  • Include instructions for obtaining access tokens using cross-platform tools (e.g., Azure CLI's 'az account get-access-token').
  • Explicitly mention that PowerShell examples are Windows-centric and offer alternative steps for Linux/macOS users.
  • Reorder or parallelize example sections so that Windows and Linux methods are presented together, rather than Windows-first.
GitHub Create Pull Request
Automation Deploy an extension-based Windows or Linux User Hybrid Runbook Worker in Azure Automation ...ation/extension-based-hybrid-runbook-worker-install.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 several forms of Windows bias. Windows and PowerShell examples are presented first and in greater detail, with Linux examples often following or being less emphasized. PowerShell is the primary automation tool referenced, even for Linux scenarios, and Windows-specific tools and paths are mentioned more frequently. Infrastructure-as-code examples (Bicep, ARM) and CLI samples focus on Windows VM creation and extension installation, with little to no Linux VM equivalents. Folder permissions and troubleshooting notes are Windows-centric, and Linux-specific requirements or commands are less visible or omitted.
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which platform is shown first in code samples and walkthroughs.
  • Provide Linux-native automation examples (e.g., Bash scripts, cloud-init, Ansible) in addition to PowerShell, especially for Linux VM onboarding and extension management.
  • Expand infrastructure-as-code samples (Bicep, ARM templates) to include Linux VM creation and extension installation, not just Windows.
  • Include Linux-specific troubleshooting, permissions, and configuration steps with equal detail to Windows.
  • Reference Linux tools and patterns (e.g., systemd, SELinux, package managers) where relevant, not just Windows tools.
  • Clarify when PowerShell Core is required or optional on Linux, and offer alternatives for users who prefer native Linux scripting.
  • Ensure all folder paths, permissions, and operational notes are provided for both platforms, not just Windows.
GitHub Create Pull Request
Automation Manage runbooks in Azure Automation ...-docs/blob/main/articles/automation/manage-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 for managing runbooks in Azure Automation exhibits a strong Windows bias. All code examples use PowerShell, with cmdlets and patterns specific to Windows environments. File paths are given in Windows format (e.g., C:\Runbooks\...), and there is no mention of Bash, shell scripting, or Linux-native tools. The documentation assumes the use of Windows-centric tools and workflows, and does not provide equivalent guidance or examples for Linux users or those preferring Bash/Python automation. Linux alternatives are not discussed, and PowerShell is presented as the default or only option for scripting and automation.
Recommendations
  • Add equivalent examples using Bash and Azure CLI for all major operations (create, import, publish, schedule, restore runbooks).
  • Include Linux file path examples and clarify cross-platform compatibility for script imports.
  • Explicitly mention and link to documentation for using Python runbooks, including how to author, test, and publish them from Linux environments.
  • Provide guidance on using Azure CLI and REST API for runbook management, with sample commands.
  • Clarify which features and cmdlets are available and supported on Linux, macOS, and Windows.
  • Add a section addressing cross-platform considerations, including differences in authentication, file handling, and environment setup.
GitHub Create Pull Request
Automation Use the Azure Automation graphical runbook SDK (preview) ...blob/main/articles/automation/graphical-runbook-sdk.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 is heavily oriented toward Windows and PowerShell. All examples and SDK usage revolve around PowerShell commands, modules, and workflows, with no mention of Linux-compatible scripting or tools. The graphical runbook SDK is described as managing Windows PowerShell code, and all activity types and value descriptors are PowerShell-centric. There are no Linux/bash examples, nor is there guidance for non-Windows environments.
Recommendations
  • Add examples that demonstrate how to use the SDK with Linux-compatible scripting languages (e.g., Bash, Python) if supported.
  • Clarify whether the graphical runbook SDK and Azure Automation graphical runbooks can be authored or executed on Linux environments, and document any limitations or alternatives.
  • Include references to cross-platform modules or scripting patterns, and provide parity in documentation for Linux users.
  • If PowerShell Core (cross-platform) is supported, explicitly mention this and provide examples for Linux/macOS usage.
  • Document any differences in runbook execution or authoring between Windows and Linux environments.
GitHub Create Pull Request
Automation Use Azure Private Link to securely connect networks to Azure Automation ...in/articles/automation/how-to/private-link-security.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive use of PowerShell for configuration examples, especially in the section on setting public network access flags. There are no equivalent CLI or Linux shell examples provided. Additionally, the State Configuration scenario highlights PowerShell Desired State Configuration (DSC) as the main configuration management tool, which is Windows-centric, without mention of cross-platform alternatives. While the page acknowledges Linux support in some features (e.g., Update Management), practical examples and tooling guidance are focused on Windows.
Recommendations
  • Provide Azure CLI and/or Bash examples alongside PowerShell scripts for configuration tasks such as setting public network access flags.
  • Include Linux-specific instructions and examples for agent installation, configuration, and management where relevant.
  • Mention and link to cross-platform configuration management options (such as Ansible or Chef) in addition to PowerShell DSC, especially in the State Configuration scenario.
  • Ensure screenshots and UI walkthroughs clarify parity for Linux users (e.g., agent installation, hybrid worker setup).
  • Explicitly state any differences or limitations for Linux environments where applicable, and provide workarounds or alternatives.
GitHub Create Pull Request
Automation Manage Office 365 services using Azure Automation ...ocs/blob/main/articles/automation/manage-office-365.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 exclusively uses Windows PowerShell examples and tools, such as the Microsoft Graph PowerShell module and Send-MailMessage, with explicit notes that PowerShell Core (cross-platform) is not supported. There are no Linux or cross-platform alternatives, and all instructions assume a Windows environment, both in tooling and workflow.
Recommendations
  • Provide equivalent examples using PowerShell Core (pwsh) where possible, or clarify platform limitations.
  • Include guidance for Linux/macOS users, such as using Azure CLI, REST API, or cross-platform scripting alternatives.
  • List platform support for each tool/module, and suggest alternatives for unsupported platforms.
  • Add explicit instructions or links for setting up Azure Automation and Office 365 management from non-Windows environments.
  • Where Windows-specific tools (e.g., Send-MailMessage) are used, suggest cross-platform alternatives (e.g., using SMTP libraries in Python, or other PowerShell modules that work on Linux).
GitHub Create Pull Request
Automation Manage Runtime Environment and Associated Runbooks in Azure Automation ...main/articles/automation/manage-runtime-environment.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 demonstrates a Windows bias by focusing heavily on PowerShell examples, referencing Windows PowerShell modules and patterns, and providing detailed instructions for PowerShell environments and packages. Windows-centric tools (e.g., PowerShell Gallery, Az PowerShell module) are mentioned and used as defaults, while Linux-specific details and examples are minimal or absent. Python (Linux) environments are mentioned but not explored in equivalent depth, and Linux-native tools or workflows are not provided.
Recommendations
  • Provide equal depth and step-by-step examples for Python (Linux) runbooks, including REST API payloads and portal workflows.
  • Include Linux-native package management instructions (e.g., pip, requirements.txt) and clarify how Python packages are managed and uploaded.
  • Add examples of viewing installed Python packages (e.g., using pip list) similar to the PowerShell Get-Module example.
  • Reference Linux-specific documentation for Python modules and packages, and avoid linking only to Windows PowerShell module documentation.
  • Clarify the runtime environment OS (Windows vs. Linux) and provide troubleshooting steps for both platforms.
  • Ensure screenshots and UI instructions are not PowerShell-centric and show parity for Python workflows.
  • Mention and provide examples for Azure CLI usage in Python runbooks, not just PowerShell.
GitHub Create Pull Request
Automation Manage databases in Azure SQL databases using Azure Automation ...articles/automation/manage-sql-server-in-automation.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 demonstrates a strong Windows bias by exclusively using PowerShell and Az PowerShell cmdlets for all automation and SQL management examples. There are no references to Linux-native tools, Bash, or cross-platform alternatives. Instructions for installing modules and running commands assume a Windows environment (elevated PowerShell prompt), and there is no mention of how to accomplish these tasks on Linux-based Hybrid Runbook Workers or using Bash/CLI. The documentation also introduces Windows-centric patterns and tools before any Linux equivalents (which are absent).
Recommendations
  • Include equivalent examples using Azure CLI and Bash scripts for connecting and managing Azure SQL databases.
  • Document how to install required modules and run automation tasks on Linux-based Hybrid Runbook Workers.
  • Add notes or sections clarifying cross-platform support and differences, especially for Linux users.
  • Reference Linux tools (e.g., sqlcmd, Azure CLI) alongside PowerShell cmdlets, and provide sample code for both environments.
  • Ensure that instructions for configuring Hybrid Runbook Workers cover both Windows and Linux setup steps.
GitHub Create Pull Request
Automation Migrate an existing agent-based hybrid workers to extension-based-workers in Azure Automation ...g-agent-based-hybrid-worker-to-extension-based-workers.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 page exhibits a Windows bias in several areas. Windows examples, tools, and terminology are presented first or exclusively in key sections, especially in the Bicep and ARM template samples, which only provision Windows VMs. PowerShell is heavily featured, with detailed cmdlets and usage, while Linux equivalents are minimal or absent. The extension installation examples and resource definitions focus on Windows-specific handlers (HybridWorkerForWindows), and Linux-specific instructions are either missing or relegated to notes or optional sections. The removal process for agent-based workers is more detailed for Windows (registry manipulation) than for Linux (simple directory removal), and permissions guidance is Windows-centric.
Recommendations
  • Provide parallel Bicep and ARM template examples for Linux VMs, using the correct image references and extension types (HybridWorkerForLinux).
  • Include Linux-specific CLI and PowerShell commands, such as az vm create with Linux images and Set-AzVMExtension/New-AzConnectedMachineExtension using HybridWorkerForLinux.
  • Expand Linux prerequisites and troubleshooting sections to match the depth given to Windows, including permissions, identity, and hardening guidance.
  • Ensure all extension installation examples clearly show both Windows and Linux type values and settings.
  • Balance the order of presentation so that Linux instructions/examples are given equal prominence and detail as Windows.
  • Add more Linux-specific automation and management scenarios, including common distributions and shell scripting examples.
GitHub Create Pull Request
Automation Manage Python 3 packages in Azure Automation ...ocs/blob/main/articles/automation/python-3-packages.md
High Priority View Details →
Scanned: 2026-01-12 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 displays a Windows bias in several ways. Windows and PowerShell examples are given exclusively for Python 3.8, with instructions and screenshots referencing Windows environments and tools first or only. Linux instructions are present for Python 3.10, but there is no parity for Linux-based management of Python 3.8 packages. PowerShell cmdlets are provided for package management, but there are no equivalent CLI or bash examples for Linux users. Windows terminology and tooling are referenced before or instead of Linux alternatives.
Recommendations
  • Provide Linux-based examples for Python 3.8 package management, including instructions for generating wheel files and importing packages using Linux tools.
  • Add Azure CLI or bash script equivalents for all PowerShell cmdlet examples, ensuring Linux users have clear guidance.
  • Present Windows and Linux instructions side-by-side or in tabs, rather than prioritizing Windows first.
  • Explicitly mention Linux support and limitations for Hybrid Runbook Workers and package management.
  • Review screenshots and UI references to ensure they are not Windows-specific unless necessary, and provide Linux alternatives where applicable.
GitHub Create Pull Request
Automation Create an Azure Automation account using a Resource Manager template ...ation/quickstart-create-automation-account-template.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and the Azure portal as primary deployment methods, with PowerShell examples and terminology appearing before Azure CLI equivalents. There is no mention of Linux-specific tools or workflows, and no Linux shell examples are provided. The guidance for resolving template errors and deploying via command line is focused on PowerShell, with Azure CLI only mentioned secondarily and without detailed Linux context.
Recommendations
  • Provide explicit Bash/Linux shell examples for deploying the ARM template using Azure CLI, including command syntax and environment notes.
  • Mention Linux and macOS compatibility for Azure CLI, and clarify that PowerShell is not required for non-Windows users.
  • Reorder instructions to present Azure CLI and Bash examples before or alongside PowerShell, rather than after.
  • Include troubleshooting steps and error messages relevant to Linux environments (e.g., file permissions, shell quoting).
  • Reference Linux-native tools (such as curl, jq) where appropriate for template management and deployment.
  • Add a note or section highlighting cross-platform support and differences, ensuring parity in guidance for Linux users.
GitHub Create Pull Request
Automation Azure Automation overview ...s/azure-docs/blob/main/articles/automation/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 for Azure Automation demonstrates a Windows bias in several ways. PowerShell is mentioned repeatedly as the primary automation language, especially in the context of Desired State Configuration (DSC), with little to no mention of Linux-native equivalents. Windows-centric tools and scenarios (e.g., Active Directory, SharePoint Server, SQL Server) are listed prominently, while Linux-specific examples or tools are missing or only referenced generically. When discussing runbooks and configuration management, Windows/PowerShell approaches are described first and in more detail, with Linux support only mentioned as a general capability rather than with concrete examples or guidance.
Recommendations
  • Include explicit Linux shell (Bash, sh) runbook examples alongside PowerShell and Python.
  • Discuss Linux-native configuration management tools (e.g., Ansible, Chef, Puppet) and how they integrate with Azure Automation.
  • Provide Linux-specific scenarios (e.g., automating package updates, managing systemd services, configuring iptables) in the 'Common scenarios' section.
  • Clarify how Azure Automation supports Linux DSC (if available) or alternatives, and provide links to relevant documentation.
  • Balance the order of presentation so that Linux and Windows are treated equally, rather than Windows/PowerShell first.
  • Add references to Linux-specific modules or packages available in the Automation account.
  • Highlight any differences or considerations when deploying Hybrid Runbook Worker on Linux vs. Windows.
GitHub Create Pull Request
Automation Quickstart - Enable managed identities for your Automation account using the Azure portal ...cles/automation/quickstarts/enable-managed-identity.md
High Priority View Details →
Scanned: 2026-01-12 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 Windows bias primarily through its exclusive reference to PowerShell in the 'Next steps' section, suggesting the use of a PowerShell runbook as the default follow-up. There are no examples or guidance for Linux users, such as Bash or Python runbooks, nor are there references to Linux command-line tools or workflows. The instructions are entirely portal-based, which is cross-platform, but the only code-based example is Windows-centric.
Recommendations
  • Include links or examples for creating and using managed identities with Bash or Python runbooks in addition to PowerShell.
  • Add references to Azure CLI or REST API methods for enabling managed identities, which are platform-agnostic.
  • In the 'Next steps' section, provide alternative tutorials for Linux users, such as 'Create Automation Python runbook using managed identity' or 'Create Automation Bash runbook using managed identity'.
  • Ensure that any code snippets or automation examples are available in both PowerShell and Bash/Python where applicable.
GitHub Create Pull Request
Automation Configure runbook input parameters in Azure Automation ...b/main/articles/automation/runbook-input-parameters.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 is heavily focused on PowerShell and Windows-centric tooling, with examples, code snippets, and workflow patterns almost exclusively using PowerShell, PowerShell Workflow, and Windows-specific cmdlets. Windows tools and patterns (such as PowerShell hashtables, .NET types, and Windows PowerShell attributes) are mentioned throughout, with little to no equivalent coverage for Linux or cross-platform scenarios. Python runbooks are briefly mentioned, but lack parity in example depth and practical usage scenarios compared to PowerShell. There are no examples or guidance for using Linux-native tools, shell scripts, or cross-platform automation approaches.
Recommendations
  • Add equivalent examples for Bash/shell runbooks, including parameter passing and invocation from Linux environments.
  • Provide guidance and code samples for starting runbooks using Azure CLI (az), which is cross-platform, alongside PowerShell examples.
  • Include Linux-specific notes and troubleshooting tips for common scenarios, such as file paths, authentication, and environment differences.
  • Expand Python runbook examples to match the depth and practical scenarios shown for PowerShell, including parameter handling, JSON input, and automation patterns.
  • Clarify which features and patterns are Windows-only, and offer alternatives or workarounds for Linux users.
  • Mention and demonstrate usage of cross-platform SDKs (e.g., Azure SDK for Python, Node.js) for starting runbooks and passing parameters.
GitHub Create Pull Request
Automation Manage schedules in Azure Automation ...main/articles/automation/shared-resources/schedules.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 demonstrates a strong Windows bias by exclusively providing PowerShell examples and cmdlets for managing Azure Automation schedules. All CLI-based instructions use PowerShell syntax, and there is no mention of Bash, Azure CLI, or Linux-native tools. The use of PowerShell is assumed throughout, and no alternative cross-platform scripting examples are provided. Windows-centric tools and patterns (e.g., PowerShell, .ps1 scripts) are referenced without Linux equivalents, and PowerShell instructions are presented before any mention of ARM templates or portal usage.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets and scenarios, demonstrating how to manage schedules using az automation commands.
  • Include Bash script examples for common scheduling tasks to support Linux users.
  • Explicitly state cross-platform options for automation (e.g., Azure CLI, REST API) and provide usage instructions.
  • Reference Linux-native tools or patterns where relevant, such as cron for local scheduling, and clarify the platform compatibility of each method.
  • Reorganize sections to present cross-platform or platform-neutral methods (e.g., Azure CLI, REST API, ARM templates) before platform-specific tools like PowerShell.
GitHub Create Pull Request
← Previous Page 4 of 40 Next →