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 851-875 of 982 flagged pages
Automation Azure Automation extension for Visual Studio Code ...ation/how-to/runbook-authoring-extension-for-vscode.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation page references PowerShell modules as a prerequisite for local runbook execution, but does not mention Linux/macOS equivalents or clarify cross-platform compatibility. There are no explicit Linux/macOS instructions or examples, and the documentation does not address potential differences in setup or usage for non-Windows environments.
Recommendations
  • Clarify whether the Azure Automation extension and runbook authoring features work equally on Linux/macOS, especially for local execution and debugging.
  • Add instructions for installing required PowerShell modules and Python packages on Linux/macOS, including any platform-specific considerations.
  • Explicitly state any limitations or differences in functionality when using the extension on Linux/macOS.
  • Include screenshots or examples from Linux/macOS environments to demonstrate parity.
  • Mention alternative shells (e.g., bash) if supported, or clarify that only PowerShell is supported for local execution.
GitHub Create Pull Request
Automation Manage runbooks in Azure Automation ...-docs/blob/main/articles/automation/manage-runbooks.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 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 Windows-style file paths and cmdlets, and there is no mention of Bash, CLI, or Linux/macOS-specific workflows. Windows tools and patterns (such as PowerShell scripts and Windows file paths) are referenced exclusively, and Linux alternatives are absent. The documentation assumes familiarity with PowerShell and Windows environments, creating friction for users on Linux or macOS.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash for common tasks (creating, importing, publishing, and retrieving runbook/job status).
  • Include Linux/macOS file path examples alongside Windows paths.
  • Mention cross-platform tools and clarify which steps are OS-agnostic.
  • Add notes or sections on how Linux/macOS users can perform these tasks, especially for scripting and automation.
  • Reference Python runbooks and their management more prominently, with examples.
  • Clarify any platform-specific limitations or requirements for Hybrid Runbook Worker and other features.
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
Medium Priority View Details →
Scanned: 2026-01-14 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 exhibits several Windows-centric biases. Most code examples (Bicep, ARM template, PowerShell, Azure CLI) focus on creating and managing Windows VMs, with explicit references to Windows images and extension types (HybridWorkerForWindows). Linux equivalents are either missing, mentioned only in passing, or relegated to notes. PowerShell is heavily featured, and Windows-specific requirements (e.g., Windows PowerShell 5.1, .NET Framework) are detailed, while Linux requirements are less emphasized. In step-by-step migration and extension installation instructions, Windows is prioritized, and Linux guidance is minimal or absent.
Recommendations
  • Provide parallel Linux examples for Bicep, ARM template, PowerShell, and Azure CLI, including explicit use of Linux VM images and the HybridWorkerForLinux extension type.
  • Ensure all steps and prerequisites are equally detailed for Linux, including package installation, permissions, and troubleshooting.
  • List Linux instructions and examples alongside Windows, not after or in notes, to demonstrate parity.
  • Include Linux-specific PowerShell Core usage and clarify support for Linux automation scenarios.
  • Add troubleshooting and removal steps for Linux with the same depth as Windows.
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
Medium Priority View Details →
Scanned: 2026-01-14 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 provides both Windows and Linux coverage, but there is a notable Windows bias. Windows examples, especially PowerShell-based, are presented first and in greater detail. Many code samples, templates (Bicep, ARM), and CLI instructions default to Windows VM creation and management. PowerShell cmdlets are heavily emphasized, with Linux-specific nuances often relegated to notes or secondary sections. Some operational details (e.g., folder permissions, registry edits, proxy settings) are Windows-centric, and Linux equivalents are missing or less detailed.
Recommendations
  • Present Linux and Windows examples in parallel, not sequentially, and alternate which comes first.
  • Provide Linux-specific code samples for Bicep and ARM templates, not just Windows VM creation.
  • Expand Linux operational details (e.g., folder permissions, proxy configuration, troubleshooting) to match Windows coverage.
  • Include Bash or shell script examples for Linux alongside PowerShell for Windows.
  • Clarify Linux-specific limitations and workarounds (e.g., CPU quota, Python version support) with actionable guidance.
  • Where PowerShell is used for Linux, explain installation and usage, or provide native Linux alternatives.
  • Ensure all management and monitoring instructions (e.g., checking extension status, uninstalling) have Linux equivalents.
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
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 Windows bias primarily through the exclusive use of PowerShell for configuration examples, such as setting the publicNetworkAccess property. There are no equivalent CLI or scripting examples for Linux/macOS users (e.g., Azure CLI, Bash). The State Configuration scenario references PowerShell DSC, a Windows-centric technology, without mentioning cross-platform alternatives or Linux-specific configuration management tools. While the Log Analytics agent is noted as available for Windows and Linux, actionable steps and examples are Windows-first or Windows-only.
Recommendations
  • Provide Azure CLI and/or REST API examples alongside PowerShell scripts for all configuration tasks, especially for setting properties like publicNetworkAccess.
  • Include Linux/macOS-specific instructions or examples where relevant, such as Bash scripts or CLI commands.
  • Mention cross-platform configuration management options (e.g., Ansible, Chef, or native Linux DSC support) in the State Configuration section.
  • Ensure that screenshots and UI walkthroughs do not assume Windows-only environments.
  • Explicitly state platform parity or limitations for each feature, so Linux/macOS users can assess applicability.
GitHub Create Pull Request
Automation Manage databases in Azure SQL databases using Azure Automation ...articles/automation/manage-sql-server-in-automation.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 Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell and Windows-centric tooling. All code examples use PowerShell syntax and cmdlets, with no mention of Bash, Azure CLI, or Linux-native approaches. Instructions for installing modules and running commands are tailored to Windows environments, and there are no Linux/macOS-specific examples or guidance. The documentation assumes familiarity with PowerShell and does not address cross-platform usage, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for connecting and managing Azure SQL databases.
  • Provide instructions for installing required modules and running automation tasks on Linux/macOS Hybrid Runbook Workers.
  • Include notes or sections highlighting cross-platform compatibility and differences, especially for authentication and module installation.
  • List both PowerShell and CLI examples side-by-side where possible, and avoid assuming the reader is on Windows.
  • Reference Linux/macOS documentation for Azure Automation and SQL connectivity.
GitHub Create Pull Request
Automation Migrate from a Run As account to Managed identities ...automation/migrate-run-as-accounts-managed-identity.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 Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell-based examples and workflows, which are most familiar to Windows users. All sample scripts and migration instructions use PowerShell cmdlets (Connect-AzAccount, Get-AzResourceGroup, etc.), with no mention of Bash, CLI, or Python alternatives. The guidance assumes the use of PowerShell modules and Windows-centric automation patterns, and does not provide Linux/macOS-specific instructions or examples. This creates friction for users who prefer or require cross-platform automation tools.
Recommendations
  • Add equivalent Azure CLI (az) examples for authentication and resource management using managed identities.
  • Include sample scripts in Bash or Python for common migration tasks.
  • Clarify which steps are platform-agnostic and which are PowerShell-specific.
  • Explicitly state PowerShell requirements and provide links to cross-platform PowerShell installation guides.
  • Mention that Azure Automation supports Python runbooks and provide migration guidance for Python users.
  • Order examples so that platform-neutral or cross-platform options are presented first, or side-by-side.
GitHub Create Pull Request
Automation Quickstart - Enable managed identities for your Automation account using the Azure portal ...cles/automation/quickstarts/enable-managed-identity.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 is heavily focused on the Azure portal UI, which is cross-platform, but the only 'Next steps' tutorial links to a PowerShell runbook example, implying a Windows-centric approach. No Linux-specific CLI or Bash examples are provided, and PowerShell is referenced before any Linux alternatives.
Recommendations
  • Include examples for creating and managing managed identities using Azure CLI and Bash scripts, which are commonly used on Linux/macOS.
  • Provide links to tutorials for creating Automation runbooks using Python or Bash, not just PowerShell.
  • Explicitly state that the Azure portal is accessible from any OS and clarify any OS-specific requirements for Automation runbooks.
  • Add parity in 'Next steps' by linking to Linux/macOS-friendly runbook creation guides.
GitHub Create Pull Request
Automation Manage schedules in Azure Automation ...main/articles/automation/shared-resources/schedules.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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias by exclusively providing PowerShell examples for command-line operations, referencing Windows-centric tools and patterns (e.g., Az PowerShell modules), and omitting equivalent instructions for Linux/macOS environments (such as Azure CLI or Bash). All code samples and automation steps outside the Azure portal rely on PowerShell, which is natively available only on Windows and requires extra setup on Linux/macOS. No Linux-first or cross-platform CLI examples are provided.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlet operations (e.g., creating, linking, disabling, and removing schedules).
  • Include Bash script examples where appropriate, especially for ARM template deployments.
  • Explicitly mention cross-platform support for PowerShell Core, and provide installation/setup guidance for Linux/macOS users.
  • Present CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Clarify which steps/tools are cross-platform and which are Windows-specific.
GitHub Create Pull Request
Automation Azure Automation overview ...s/azure-docs/blob/main/articles/automation/overview.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 Tools Windows First
Summary
The documentation page for Azure Automation demonstrates a moderate Windows bias. PowerShell is repeatedly mentioned as the primary language for runbooks and configuration management (DSC), with Windows-centric tools and scenarios (Active Directory, SharePoint Server, SQL Server) highlighted. The modules gallery emphasizes PowerShell Gallery integration, and Windows examples or terminology often appear before Linux equivalents. Although Linux support is acknowledged, examples and tooling references are predominantly Windows/PowerShell-focused.
Recommendations
  • Provide equal prominence and examples for Python runbooks and Linux shell scripting where applicable.
  • Explicitly mention Linux equivalents for configuration management (e.g., Ansible, Chef, or native Linux DSC support).
  • Include Linux-specific automation scenarios (e.g., managing Apache, Nginx, systemd services) alongside Windows scenarios.
  • Highlight cross-platform modules and gallery resources, not just PowerShell Gallery.
  • Ensure documentation sections reference Linux tools and patterns before or alongside Windows ones, not after.
  • Add links to Linux-focused quickstarts and tutorials.
GitHub Create Pull Request
Automation Azure Quickstart - Install Hybrid Worker extension on Azure portal. ...omation/quickstarts/install-hybrid-worker-extension.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page is notably Windows-centric: the prerequisites specify a Windows VM, all installation steps and screenshots reference the 'Azure Automation Windows Hybrid Worker' extension, and there are no explicit instructions or examples for Linux VMs. Linux users are left to infer applicability, creating friction and uncertainty.
Recommendations
  • Add explicit instructions and screenshots for installing the Hybrid Worker extension on Linux VMs.
  • Include a separate section or parallel steps for Linux, highlighting any differences in the process or extension name.
  • Clarify in the prerequisites that Linux VMs are supported and detail any Linux-specific requirements.
  • Ensure that extension names and UI elements for Linux are mentioned alongside Windows equivalents.
GitHub Create Pull Request
Automation Runtime Environment in Azure Automation ...in/articles/automation/runtime-environment-overview.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 demonstrates a notable Windows bias. PowerShell is consistently highlighted as the primary scripting language, with multiple versions listed and referenced before Python. Azure CLI usage is described specifically in the context of PowerShell 7.4, with no mention of Bash or native Linux shell integration. Package management examples and references (e.g., PSGallery) are Windows-centric, and there are no explicit Linux/macOS examples, nor is there guidance for users who prefer Bash or Python-first workflows.
Recommendations
  • Include examples and guidance for running Azure CLI commands in Python runbooks and clarify Bash support, if available.
  • List Python runtime environments before or alongside PowerShell to avoid Windows-first ordering.
  • Reference Linux/macOS package sources (e.g., pip for Python) equally with PSGallery.
  • Provide explicit examples or notes for Linux/macOS users, including any differences in environment setup or limitations.
  • Clarify whether Bash or other Linux-native shells are supported as runtime environments.
GitHub Create Pull Request
Automation Configure runbook input parameters in Azure Automation ...b/main/articles/automation/runbook-input-parameters.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 strong Windows/PowerShell bias. Most examples, code snippets, and workflows are centered around PowerShell and PowerShell Workflow, which are primarily Windows technologies. The use of Windows PowerShell cmdlets, references to Windows-specific tools and patterns (such as GUID creation in PowerShell), and the lack of equivalent Linux/macOS shell examples or CLI workflows make it difficult for Linux/macOS users to follow or adapt the instructions. Python runbooks are mentioned, but only briefly and without detailed examples or parity in parameter handling. There are no Bash, Azure CLI, or cross-platform SDK examples provided.
Recommendations
  • Add equivalent examples using Azure CLI and Bash for starting runbooks and passing parameters, especially for Linux/macOS users.
  • Include instructions and code snippets for creating and passing parameters to runbooks from Linux/macOS environments.
  • Provide parity in SDK examples, such as Python or JavaScript, not just C#.
  • Clarify which steps and tools are cross-platform and which are Windows-specific.
  • Expand the Python runbook section with more detailed examples, including parameter handling and invocation from Linux/macOS.
  • Mention and demonstrate how Linux/macOS users can generate GUIDs, manipulate JSON, and interact with Azure Automation without PowerShell.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.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 Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by focusing almost exclusively on PowerShell cmdlets and workflows, which are native to Windows environments. All detailed command-line examples use PowerShell, and Windows-centric tools (e.g., Add-AzureCertificate) are referenced without Linux or cross-platform alternatives. There are no CLI or bash examples, and Linux/macOS users are not guided on how to perform equivalent tasks outside PowerShell. Python examples are provided, but only for certificate retrieval, not management or creation.
Recommendations
  • Add Azure CLI examples for certificate management tasks (creation, retrieval, deletion) to provide parity for Linux/macOS users.
  • Include bash or shell script examples for uploading and managing certificates, especially for tasks currently shown only in PowerShell.
  • Reference cross-platform tools and workflows (e.g., Azure CLI, REST API) before or alongside PowerShell cmdlets.
  • Clarify which steps or tools are Windows-only and provide alternatives for Linux/macOS environments.
  • Expand Python examples to cover certificate creation and management, not just retrieval.
GitHub Create Pull Request
Automation Manage modules in Azure Automation ...b/main/articles/automation/shared-resources/modules.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 Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on PowerShell modules and cmdlets, with nearly all examples, instructions, and tooling references centered around Windows PowerShell and Az/AzureRM modules. Internal cmdlets and features (e.g., Orchestrator.AssetManagement.Cmdlets) are explicitly unavailable on Linux Hybrid Runbook Workers, and there are no Linux/macOS-specific instructions or examples for module management. Python module support is mentioned briefly, but without parity in examples or guidance. The documentation assumes a Windows-centric workflow and tooling, with little consideration for Linux/macOS users.
Recommendations
  • Add explicit instructions and examples for managing modules on Linux Hybrid Runbook Workers, including any supported alternatives to Windows-only features.
  • Clearly indicate which features and cmdlets are Windows-only and provide Linux/macOS equivalents or workarounds where possible.
  • Include Linux/macOS shell examples (e.g., Bash, CLI) for module import, management, and runbook authoring.
  • Expand the Python module section to provide parity in guidance and examples for Python users on Linux/macOS.
  • Add a summary table or section comparing Windows and Linux/macOS capabilities and limitations in Azure Automation.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.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 Tools Windows First Missing Linux Example
Summary
The documentation page is heavily focused on Windows and PowerShell tooling, with all command-line examples using PowerShell cmdlets and Windows-centric patterns. There is no mention of Linux or macOS shell equivalents, nor are there CLI or REST API examples for credential management. The Python section is present, but only for runbooks, not for asset management outside of runbooks. The instructions for creating credentials outside the portal are exclusively Windows PowerShell-based, and Windows tools are referenced throughout without Linux alternatives.
Recommendations
  • Add Azure CLI examples for credential asset management, as Azure CLI is cross-platform and works on Linux/macOS.
  • Include REST API or SDK examples for credential management to provide platform-agnostic options.
  • Explicitly mention Linux/macOS compatibility where applicable, and clarify any platform limitations.
  • Provide bash or shell script equivalents for relevant operations, or state if such operations are not supported outside PowerShell.
  • Reorder examples so that cross-platform methods (portal, CLI, REST) are presented before Windows/PowerShell-specific ones.
GitHub Create Pull Request
Automation Manage variables in Azure Automation ...main/articles/automation/shared-resources/variables.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 Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows PowerShell for variable management in Azure Automation. All CLI examples use PowerShell cmdlets, and references to 'Windows PowerShell' and 'Windows Hybrid Runbook Worker' are frequent. There are no Bash, Linux shell, or cross-platform CLI examples, nor is there mention of Linux-specific tooling or patterns. The Python examples are platform-neutral, but all scripting outside Python is Windows-centric.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands for variable management, which are cross-platform.
  • Clarify which features and cmdlets are available or not available on Linux/macOS Hybrid Runbook Workers.
  • Include Bash or shell script examples for common tasks, or explicitly state if only PowerShell is supported.
  • Reorder sections so platform-neutral or cross-platform approaches (e.g., portal, Python) are presented before Windows-specific tools.
  • Explicitly mention Linux/macOS support and limitations in relevant sections.
GitHub Create Pull Request
Automation Start a runbook in Azure Automation ...e-docs/blob/main/articles/automation/start-runbooks.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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell-based examples and instructions for starting runbooks, with no mention of Linux/macOS alternatives such as Azure CLI, Bash, or cross-platform scripting. Windows tools and terminology (PowerShell cmdlets, hashtables, PSCredential) are used throughout, and Windows methods are presented before platform-neutral or API-based approaches. Linux/macOS users are left without direct guidance for their environments.
Recommendations
  • Add Azure CLI examples for starting runbooks, including parameter passing and job tracking.
  • Include Bash or shell script samples for interacting with the Azure Automation API.
  • Explicitly mention cross-platform options and clarify which methods work on Linux/macOS.
  • Reorder sections to present platform-neutral methods (API, portal, CLI) before Windows-specific tools.
  • Provide links to Linux/macOS-specific documentation or troubleshooting guides.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation State Configuration issues ...automation/troubleshoot/desired-state-configuration.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 toward Windows and PowerShell, with most troubleshooting steps, examples, and cmdlets referencing Windows tools and workflows. PowerShell DSC is assumed as the default, and Linux-specific guidance is minimal and appears only in isolated sections. Many steps (such as certificate cleanup, extension management, and log analysis) provide only Windows/PowerShell instructions, and Windows terminology and tools are mentioned before or instead of Linux equivalents.
Recommendations
  • Add Linux-specific troubleshooting steps and examples for all major scenarios, especially where only PowerShell or Windows instructions are given.
  • Provide equivalent Linux commands (e.g., for certificate management, log analysis, extension handling) alongside PowerShell examples.
  • Clearly indicate when a step or tool is Windows-only and offer Linux alternatives or workarounds.
  • Ensure Linux onboarding, error resolution, and node management are covered with parity to Windows, including references to Linux DSC agents and their logs.
  • Reorder examples so that Linux and Windows are presented equally, or group them by platform.
GitHub Create Pull Request
Automation Troubleshoot agent-based Hybrid Runbook Worker issues in Azure Automation ...icles/automation/troubleshoot/hybrid-runbook-worker.md
Medium Priority View Details →
Scanned: 2026-01-14 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 moderate Windows bias. Many troubleshooting scenarios and examples are presented for Windows first, with PowerShell commands and Windows-specific tools (such as registry edits, event logs, and config files) featured prominently. Linux troubleshooting is covered in a separate section, but Windows examples and tools are often given before Linux equivalents, and some workarounds (e.g., editing Orchestrator.Sandbox.exe.config) are Windows-only. Several scenarios provide detailed PowerShell-based solutions for Windows, while Linux solutions are less detailed or missing for similar issues.
Recommendations
  • Ensure that troubleshooting steps and examples are presented in parallel for both Windows and Linux, rather than grouping most Windows content first.
  • Provide Linux equivalents for all Windows troubleshooting scenarios, especially for agent configuration, log locations, and service management.
  • Include Linux command-line examples (e.g., systemctl, journalctl, file paths) wherever PowerShell or Windows tools are mentioned.
  • Avoid referencing Windows-specific tools (e.g., registry, event logs) without noting Linux alternatives.
  • When describing configuration file changes, provide Linux file paths and instructions if applicable.
  • Balance the level of detail in Linux troubleshooting steps to match that of Windows.
GitHub Create Pull Request
Automation Remove DSC and node from Automation State Configuration ...configuration/remove-node-and-configuration-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 page demonstrates a moderate Windows bias. PowerShell-based instructions and tools are presented first and in more detail, with explicit cmdlet references for Windows tasks. Linux instructions are present, but are less detailed and often follow Windows examples. The use of PowerShell cmdlets as the primary automation method and the lack of parity in example depth and tooling for Linux users creates friction for non-Windows audiences.
Recommendations
  • Provide equivalent CLI or script examples for Linux users where PowerShell cmdlets are referenced (e.g., using Bash, Python, or native Linux tools).
  • Present Windows and Linux instructions side-by-side or in parallel tabs, rather than listing Windows first.
  • Expand Linux sections to include more detailed steps, troubleshooting, and automation options (such as using Azure CLI or REST API for Linux nodes).
  • Reference Linux-specific management tools or scripts where appropriate, not just PowerShell.
  • Ensure screenshots and UI instructions clarify any OS-specific differences.
GitHub Create Pull Request
Automation Troubleshoot extension-based Hybrid Runbook Worker issues in Azure Automation .../troubleshoot/extension-based-hybrid-runbook-worker.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation generally provides both Windows and Linux troubleshooting steps for Hybrid Runbook Worker issues, but there is a notable Windows-first bias. Windows examples, tools, and troubleshooting steps are often presented before Linux equivalents, and some scenarios (such as registry edits, PowerShell scripts, and event log checks) are Windows-specific or lack Linux analogs. Several troubleshooting and resolution steps are detailed for Windows (e.g., registry and event log manipulation, PowerShell scripts), while Linux steps are sometimes less detailed or omitted for equivalent scenarios.
Recommendations
  • Present Windows and Linux instructions in parallel or clearly separated sections, rather than always listing Windows first.
  • Where Windows-specific tools or logs are referenced (e.g., Microsoft-SMA event logs, registry edits, PowerShell scripts), provide Linux equivalents or explicitly state if no equivalent exists.
  • For troubleshooting steps that are only described for Windows (e.g., checking event logs, registry keys), add Linux-specific guidance (such as relevant log file locations, systemd journal commands, or configuration files).
  • Ensure that all scenarios (such as job suspension, authentication failures, and extension installation/uninstallation) have equally detailed Linux instructions, including command-line examples and troubleshooting tips.
  • Avoid assuming PowerShell as the default scripting environment; provide Bash or Python examples for Linux where appropriate.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation runbook issues ...blob/main/articles/automation/troubleshoot/runbooks.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 Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell cmdlets and Windows-centric tools, with all code examples and troubleshooting steps using PowerShell syntax and modules (Az.Automation, AzureRM, etc.). There are no Linux/macOS shell or Python examples for equivalent operations, and Windows/PowerShell patterns are presented exclusively and first. Windows-specific concepts (e.g., PowerShell ISE, certificate stores, WMI, msiserver.exe) are referenced without Linux/macOS alternatives or clarifications.
Recommendations
  • Add equivalent troubleshooting examples for Python runbooks, including error handling and module management.
  • Include Linux/macOS shell examples where applicable, especially for hybrid worker scenarios.
  • Clarify which steps or cmdlets are platform-agnostic and which are Windows-only; provide alternatives for Linux/macOS users.
  • Mention and link to cross-platform tools (e.g., VS Code, Azure CLI) and provide examples using them.
  • Explicitly state platform requirements or limitations for each troubleshooting step, especially where Windows-only features (like PowerShell ISE or certificate stores) are referenced.
GitHub Create Pull Request
Automation Authenticate Azure Automation runbooks with Amazon Web Services ...n/articles/automation/automation-config-aws-account.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing AWS credential management via the AWS PowerShell user guide, which is Windows-centric. There are no Linux or macOS-specific examples or references, and the only external link for credential specification points to PowerShell documentation. The page does not mention Linux tools or workflows, nor does it provide parity for non-Windows users in terms of credential management or automation scripting.
Recommendations
  • Include links to AWS CLI documentation for credential management, which is cross-platform.
  • Provide examples for storing and referencing AWS credentials using Linux/macOS tools and workflows.
  • Mention that Azure Automation runbooks can be authored in Python or other languages, and show how to authenticate with AWS using those languages on Linux/macOS.
  • Add guidance for Linux/macOS users on downloading and storing AWS key files securely.
  • Ensure that references to credential management do not exclusively point to Windows/PowerShell resources.
GitHub Create Pull Request
Automation Create a standalone Azure Automation account ...les/automation/automation-create-standalone-account.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing PowerShell examples and references exclusively, mentioning PowerShell runbooks and cmdlets first, and omitting equivalent Linux/macOS CLI (Azure CLI, Bash) instructions. No Linux-specific tools or examples are given for key actions such as rotating access keys or creating/managing the Automation account, which may create friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI and Bash examples for all tasks currently shown only with PowerShell (e.g., rotating access keys, creating Automation accounts).
  • Include Linux/macOS-specific guidance or notes where platform differences exist.
  • Present cross-platform instructions side-by-side or in tabs, ensuring parity and visibility for both Windows and Linux/macOS users.
  • Reference both PowerShell and Azure CLI documentation in 'Next steps' and throughout the article.
GitHub Create Pull Request
← Previous Page 35 of 40 Next →