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 26-50 of 982 flagged pages
Automation Manage runbooks in Azure Automation ...-docs/blob/main/articles/automation/manage-runbooks.md
High Priority View Details →
Scanned: 2026-01-13 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 file paths that are native to Windows environments. There are no Bash, CLI, or Linux/macOS shell examples, nor are Linux-specific tools or patterns mentioned. Windows file paths (e.g., C:\Runbooks\Sample_TestRunbook.ps1) are used exclusively, and PowerShell is referenced as the primary automation language throughout. The documentation does not address how Linux/macOS users can perform equivalent tasks, nor does it mention cross-platform alternatives like Azure CLI or REST API usage.
Recommendations
  • Add equivalent examples using Azure CLI and Bash for all major tasks (create, import, publish, retrieve job status, etc.).
  • Include Linux/macOS file path examples and clarify any platform-specific differences.
  • Explicitly mention cross-platform options and note any limitations or differences for non-Windows users.
  • Provide guidance on using Python runbooks and how to manage them from Linux/macOS environments.
  • Reference REST API methods for runbook management as a platform-neutral alternative.
GitHub Create Pull Request
Automation Azure Quickstart - Configure a VM with Desired State Configuration ...n/articles/automation/quickstarts/dsc-configuration.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented towards Windows, with PowerShell-based examples and references to Windows-centric tooling and workflows. Although a Linux scenario (LAMP stack) is mentioned, the underlying DSC platform for Linux is retired, and the instructions and examples remain PowerShell-centric. There is minimal guidance for Linux users, and the workflow assumes familiarity with Windows and PowerShell environments.
Recommendations
  • Clearly state at the beginning that Azure Automation DSC for Linux is retired and provide alternative solutions for Linux configuration management (e.g., Azure Policy Guest Configuration, Ansible, Chef, Puppet).
  • Remove or de-emphasize Linux scenarios (like LAMP stack) from the quickstart if they are no longer supported, or provide explicit migration paths.
  • If Linux support is still relevant, include bash or shell script examples, and reference Linux-native tools and workflows.
  • Provide parity in documentation structure: if Windows instructions are given, ensure Linux/macOS equivalents are present and easy to follow.
  • Update links and references to point to current Linux management options in Azure.
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-13 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 for Windows Azure Virtual Machines. All step-by-step instructions, screenshots, and extension selection are Windows-specific, with no equivalent guidance or visuals for Linux VMs. The prerequisites and installation steps mention only Windows, and the extension referenced is 'Azure Automation Windows Hybrid Worker', with no mention of the Linux version or its installation process.
Recommendations
  • Include parallel instructions and screenshots for installing the Hybrid Worker extension on Linux Azure Virtual Machines.
  • Explicitly mention and show how to select the Linux Hybrid Worker extension in the Azure portal.
  • Update the prerequisites to include Linux VM requirements and clarify any differences in setup.
  • Provide troubleshooting tips or notes specific to Linux environments.
  • Ensure that examples and terminology are balanced between Windows and Linux, or presented in a neutral order.
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-13 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 is heavily biased toward Windows and PowerShell usage. All examples use PowerShell cmdlets and Windows-specific DSC resources (e.g., WindowsFeature IIS). The prerequisites and walkthrough focus exclusively on Windows VMs, with no Linux equivalents or examples provided. Linux support is only mentioned in passing, and there are no instructions or code samples for Linux systems.
Recommendations
  • Add equivalent Linux examples throughout the tutorial, including onboarding, configuration authoring, and node registration.
  • Provide sample DSC configurations for Linux (e.g., ensuring an Apache web server is installed using nxPackage or other cross-platform DSC resources).
  • Include Bash/CLI examples where possible, or reference cross-platform tools.
  • Clarify in the prerequisites and introduction whether Linux is supported and, if not, clearly state the limitations.
  • If Linux support is deprecated (as hinted by the retirement announcement), make this explicit at the start and provide migration guidance.
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-13 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 tools and patterns. All troubleshooting steps and code examples use PowerShell cmdlets and scripts, with no mention of Bash, Azure CLI, or Linux/macOS workflows. Windows-specific DLL errors are discussed, and solutions are provided only in the context of PowerShell and Windows automation modules. There are no Linux/macOS equivalents or alternative instructions, and Windows tools and terminology are used exclusively and presented first.
Recommendations
  • Provide equivalent troubleshooting steps and examples using Azure CLI and Bash scripts for Linux/macOS users.
  • Include instructions for managing Azure Automation modules via REST API or Azure CLI, which are cross-platform.
  • Document how to resolve module import issues and authentication in runbooks using Python or other supported languages on Linux/macOS.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and add notes or links for Linux/macOS alternatives.
  • Address DLL-specific errors with guidance for non-Windows environments, or clarify their relevance.
GitHub Create Pull Request
Automation Convert configurations to composite resources for Azure Automation State Configuration ...articles/automation/automation-dsc-create-composite.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 is heavily focused on Windows PowerShell and Windows-centric tools and patterns. All examples and instructions are PowerShell-based, with no mention of Linux equivalents or cross-platform DSC authoring. References to configuration management, module creation, and automation are exclusively tied to Windows PowerShell and related repositories, with Linux support only briefly mentioned in passing (e.g., onboarding physical/virtual Linux machines) and no concrete examples or guidance provided.
Recommendations
  • Add explicit examples and instructions for authoring and converting configurations on Linux systems, using cross-platform PowerShell (pwsh) where appropriate.
  • Clarify which steps and tools are compatible with Linux, and provide alternatives or notes for Linux users.
  • Include Linux-specific scenarios (e.g., Apache web server, iptables firewall) alongside Windows scenarios.
  • Reference and link to documentation for DSC on Linux, including supported resources and configuration patterns.
  • Ensure that onboarding and usage instructions for both Windows and Linux are presented with parity, ideally side-by-side.
GitHub Create Pull Request
Automation Remediate noncompliant Azure Automation State Configuration servers ...b/main/articles/automation/automation-dsc-remediate.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 page demonstrates Windows bias by presenting Windows remediation steps first, providing detailed PowerShell examples and references, and focusing on Windows tools (PowerShell, Chocolatey) with direct code samples. In contrast, Linux remediation is described in more abstract terms, lacks direct script/code examples, and refers to external documentation for details. The Windows workflow is more streamlined and better supported, while Linux instructions are less clear and actionable.
Recommendations
  • Provide direct Linux command/script examples for remediation, similar to the PowerShell example for Windows.
  • Include step-by-step instructions for Linux drift correction, not just references to external documentation.
  • Present Windows and Linux remediation options in parallel sections, giving equal prominence and detail.
  • Reference Linux-native tools and workflows (e.g., shell scripts, Ansible, native DSC commands) where appropriate.
  • Avoid using Windows tools (e.g., Chocolatey) as the sole example for continuous deployment pipelines; include Linux alternatives.
GitHub Create Pull Request
Automation Compile DSC configurations in Azure Automation State Configuration ...lob/main/articles/automation/automation-dsc-compile.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. All code examples use Windows PowerShell, and all tooling references are for Windows-based tools (PowerShell cmdlets, WindowsFeature resource, etc.). There are no examples or guidance for compiling DSC configurations on Linux, nor are Linux tools or workflows mentioned. The structure and language consistently prioritize Windows and PowerShell, with no parity for Linux users.
Recommendations
  • Add explicit guidance and examples for compiling DSC configurations on Linux, using native Linux tools or cross-platform PowerShell Core.
  • Include Linux-specific resources and workflows, such as using OpenSSH, Linux file paths, and Linux DSC resources.
  • Clarify any limitations or differences for Linux users, especially in light of the referenced 'automation-dsc-linux-retirement-announcement'.
  • Where PowerShell is referenced, specify whether PowerShell Core (cross-platform) is supported, and provide examples for both Windows and Linux environments.
  • Mention alternative configuration management tools or patterns for Linux if DSC support is deprecated or limited.
GitHub Create Pull Request
Automation Use Microsoft Entra ID in Azure Automation to authenticate to Azure ...ob/main/articles/automation/automation-use-azure-ad.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 is heavily focused on Windows and PowerShell tooling, with all examples, instructions, and referenced modules using PowerShell and Windows-centric patterns. There are no Bash, CLI, or Linux-native examples, and Windows tools and terminology (such as PSCredential, Windows PowerShell, and PowerShell-specific cmdlets) are used exclusively and introduced first. No Linux or cross-platform alternatives are mentioned.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for Linux users.
  • Mention cross-platform authentication approaches, such as using service principals or managed identities via CLI.
  • Clarify which steps and modules are available on Linux/macOS and which are Windows-only.
  • Reference Linux-compatible credential management patterns (e.g., environment variables, Azure CLI credential store).
  • Provide links to Azure CLI documentation and examples alongside PowerShell references.
  • Explicitly state platform requirements and limitations for each method.
GitHub Create Pull Request
Automation Move your Azure Automation account to another subscription ...s/blob/main/articles/automation/how-to/move-account.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides command-line examples exclusively using Azure PowerShell cmdlets (e.g., Remove-AzResource, Remove-AzActionGroup), which are most commonly used in Windows environments. There are no equivalent Azure CLI or Bash examples, which are preferred on Linux and macOS. The documentation also references PowerShell-specific tooling and patterns, without mentioning or prioritizing cross-platform alternatives.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands shown, using az resource and az monitor action-group commands.
  • Explicitly mention that both PowerShell and Azure CLI can be used, and provide guidance for Linux/macOS users.
  • Where screenshots or instructions reference the Azure portal, clarify that the portal is cross-platform.
  • Consider including Bash script examples for resource management tasks.
  • Review and update troubleshooting and verification steps to ensure parity for users on Linux and macOS.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.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 strong Windows bias by exclusively providing PowerShell examples and cmdlets, referencing Windows-centric tools (e.g., PowerShell, Add-AzureCertificate), and omitting Linux-native approaches or CLI examples. The certificate management workflow is described almost entirely in terms of PowerShell and Windows cryptography providers, with no mention of Linux shell commands, OpenSSL, or cross-platform alternatives. Python examples are included, but only in the context of Azure Automation runbooks, not for general certificate management. There are no Linux-specific instructions or parity for users who may be managing certificates from Linux environments.
Recommendations
  • Add Azure CLI examples for certificate management tasks, such as uploading, retrieving, and deleting certificates.
  • Include instructions and examples for managing certificates using Linux shell commands (e.g., OpenSSL for certificate creation and manipulation).
  • Reference cross-platform tools and patterns, such as Azure CLI and REST API, before or alongside PowerShell cmdlets.
  • Clarify that PowerShell is available on Linux and macOS, but also provide native Linux command alternatives where appropriate.
  • Document any platform-specific requirements or limitations, such as cryptographic provider compatibility, for both Windows and Linux.
  • Provide troubleshooting steps for Linux users, especially for certificate file formats and permissions.
GitHub Create Pull Request
Automation Quickstart - Create an Azure Automation account using the portal .../quickstarts/create-azure-automation-account-portal.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 focuses exclusively on using the Azure portal UI to create an Automation account, with no mention of command-line alternatives (such as Azure CLI or Bash). The only 'Next steps' tutorial explicitly references PowerShell, which is primarily a Windows-centric tool, and does not provide parity for Linux users (e.g., Bash, Azure CLI, or Python SDK). There are no examples or instructions tailored for Linux environments, nor are Linux tools or patterns mentioned.
Recommendations
  • Include alternative instructions for creating an Automation account using Azure CLI and Bash, which are cross-platform and widely used on Linux.
  • Add 'Next steps' links to tutorials for creating runbooks using Azure CLI, Bash, or Python SDK, not just PowerShell.
  • Explicitly mention that PowerShell is available cross-platform, but also provide Linux-native examples to ensure parity.
  • Where screenshots or UI instructions are given, consider adding CLI equivalents for users who prefer or require command-line automation.
GitHub Create Pull Request
Automation Troubleshoot agent-based Hybrid Runbook Worker issues in Azure Automation ...icles/automation/troubleshoot/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 exhibits a Windows bias in several ways: troubleshooting steps and examples are frequently presented for Windows first, with detailed PowerShell commands and references to Windows-specific tools (event logs, registry keys, config files in C:\Program Files, etc.). Linux troubleshooting is covered in a separate, shorter section, with fewer concrete examples and less detail. Some scenarios (e.g., updating Az modules, Set-AzStorageBlobContent issues, proxy configuration) provide only Windows/PowerShell solutions or mention Windows tools/configurations without Linux equivalents. In some cases, Linux steps are missing or less explicit, and Windows-centric terminology (e.g., 'Orchestrator.Sandbox.exe', 'Microsoft-SMA event log') is used throughout.
Recommendations
  • Ensure that every troubleshooting scenario includes both Windows and Linux steps/examples where applicable.
  • Provide Linux equivalents for all PowerShell commands (e.g., Bash scripts, systemctl/service commands, log file locations).
  • Mention Linux tools and patterns (e.g., systemd, journalctl, /var/log paths) alongside Windows tools, not just in a separate section.
  • Avoid presenting Windows solutions first by default; alternate or parallelize Windows and Linux instructions.
  • Expand Linux troubleshooting details to match the depth and specificity of Windows guidance, including error messages, config file paths, and command-line examples.
  • Where Windows-specific configuration files are referenced (e.g., Orchestrator.Sandbox.exe.config), clarify if there is a Linux equivalent or explicitly state if not applicable.
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-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 for all code examples and automation scripts, referencing only Windows-centric tools and patterns (e.g., PowerShell cmdlets, AzureRM/Az modules), and omitting any examples or guidance for Linux-based automation environments (such as Python, Bash, or CLI usage). The documentation also assumes the use of PowerShell as the default automation language and does not mention or prioritize cross-platform alternatives.
Recommendations
  • Include equivalent examples using Azure CLI, Python SDK, or Bash scripts to demonstrate managed identity authentication and resource management, ensuring Linux parity.
  • Explicitly mention that Azure Automation supports Python runbooks and provide migration guidance and code samples for Python-based automation.
  • Add troubleshooting and migration notes for Linux Hybrid Runbook Workers, including how managed identities are used in non-Windows environments.
  • Reference cross-platform tools and modules (e.g., Azure CLI, REST API) alongside PowerShell, and avoid assuming PowerShell as the default or only option.
  • Reorder sections or provide parallel guidance so that Windows and Linux approaches are presented equally, rather than Windows/PowerShell first.
GitHub Create Pull Request
Automation Azure Quickstart - Configure a VM with Desired State Configuration ...n/articles/automation/quickstarts/dsc-configuration.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 Windows bias by focusing on PowerShell-based Desired State Configuration (DSC), referencing Windows-centric tools (such as Chocolatey), and providing examples and instructions primarily in PowerShell. Although the example configures a LAMP stack (Linux), the workflow, tooling, and references are all Windows/PowerShell-centric, and there is no mention of Linux-native configuration tools or workflows. The retirement notice for Linux DSC is prominent, and no alternatives or parity guidance for Linux users are provided.
Recommendations
  • Provide equivalent Linux-native configuration management examples (e.g., using Ansible, Chef, or native Azure Policy Guest Configuration for Linux).
  • Include instructions and examples for configuring Linux VMs using non-PowerShell tools.
  • Mention and link to Linux-specific documentation and alternatives where DSC for Linux is deprecated.
  • Avoid referencing Windows tools (like Chocolatey) as the next step for Linux scenarios, or provide Linux package management alternatives.
  • Clarify the limitations and retirement of Linux DSC, and guide users to supported Linux configuration management options.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation State Configuration issues ...automation/troubleshoot/desired-state-configuration.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 strong Windows bias. Most troubleshooting steps, examples, and tools are presented using PowerShell and Windows-centric terminology. Windows-specific cmdlets, tools (such as xDscDiagnostics), and portal navigation are described in detail, while Linux equivalents are rarely mentioned or are relegated to brief notes. Linux troubleshooting is only covered in a single scenario, and there are no Linux shell command examples or references to Linux DSC logs or tools. Windows solutions are consistently presented first or exclusively.
Recommendations
  • Add Linux-specific troubleshooting steps and examples for each scenario, including shell commands and log locations.
  • Provide parity in tool references, e.g., mention Linux DSC diagnostics tools or methods alongside xDscDiagnostics.
  • Include Linux portal navigation and extension management instructions where relevant.
  • Ensure that Linux onboarding, error messages, and solutions are described with the same level of detail as Windows.
  • Where PowerShell cmdlets are referenced, add equivalent Linux commands or clarify their applicability to Linux nodes.
  • Review and update all scenarios to explicitly address both Windows and Linux environments, especially as the service approaches end-of-life for Linux support.
GitHub Create Pull Request
Automation Using a user-assigned managed identity for an Azure Automation account ...main/articles/automation/add-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. PowerShell is used almost exclusively for all command-line examples, including REST API calls, ARM template deployments, and role assignments. There are no Bash, Azure CLI, or Linux shell examples provided. Even when discussing REST API or HTTP endpoints, the examples use PowerShell rather than cross-platform tools like curl or Azure CLI. Windows tools and patterns (e.g., PowerShell cmdlets, Windows-style file paths) are mentioned first and often exclusively, with Linux equivalents missing.
Recommendations
  • Add Azure CLI examples for all operations (e.g., assigning managed identities, role assignments, ARM template deployments).
  • Provide Bash or shell script examples for REST API calls, using curl or wget, to demonstrate Linux compatibility.
  • Include Linux file path conventions and clarify that examples work on both Windows and Linux, or provide OS-specific notes.
  • Reorder sections so that cross-platform or OS-neutral methods (e.g., Azure portal, REST API, Azure CLI) are presented before or alongside PowerShell.
  • Explicitly mention Linux support for Automation accounts and managed identities, and link to Linux-specific documentation if available.
GitHub Create Pull Request
Automation Authenticate Azure Automation runbooks with Amazon Web Services ...n/articles/automation/automation-config-aws-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 demonstrates Windows bias by referencing AWS credential management via the AWS PowerShell user guide and omitting Linux-specific instructions or examples. There are no mentions of Linux tools or CLI workflows, and the only external credential reference is to PowerShell. The documentation assumes Azure portal usage and does not provide parity for Linux users or alternative command-line methods.
Recommendations
  • Include instructions and examples for authenticating AWS from Linux environments, such as using the AWS CLI.
  • Reference AWS CLI documentation alongside PowerShell guides for credential management.
  • Provide examples of creating and storing credentials using Linux shell commands or scripts.
  • Clarify that the process is platform-agnostic where possible, or explicitly note differences for Windows and Linux users.
  • Add links to relevant Linux documentation and tools (e.g., AWS CLI credential configuration).
GitHub Create Pull Request
Automation Manage connections in Azure Automation ...lob/main/articles/automation/automation-connections.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 demonstrates a strong bias toward Windows and PowerShell environments. All command-line examples for creating and managing connections use PowerShell cmdlets, with no equivalent CLI or Bash/Linux shell examples. The documentation refers to 'Windows PowerShell' explicitly and does not mention cross-platform alternatives like Azure CLI or REST API for Linux/macOS users. The internal cmdlets and graphical runbook sections also assume a Windows-centric workflow. While Python examples are provided, they are specific to Azure Automation runbooks and do not address general Linux shell usage.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlet operations (e.g., creating, retrieving, and deleting connections).
  • Include Bash/Linux shell examples where applicable, especially for connection management tasks.
  • When introducing tools or workflows, mention cross-platform options (e.g., Azure CLI, REST API) alongside or before Windows/PowerShell tools.
  • Avoid using 'Windows PowerShell' as the default term; use 'PowerShell' and clarify when examples are cross-platform.
  • Provide explicit guidance for Linux/macOS users on how to perform the same tasks, including any platform-specific prerequisites or differences.
  • Ensure that all code tabs or sections (PowerShell, CLI, Python) are equally represented and easy to find.
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-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 Windows bias by primarily featuring PowerShell examples and references, mentioning Azure PowerShell as the only CLI for key rotation, and listing PowerShell runbooks and cmdlet references before alternatives. There are no examples using Azure CLI, Bash, or Linux-native tools, and Linux-centric workflows are not discussed. The documentation assumes familiarity with Windows tooling and patterns, and does not provide parity for Linux users.
Recommendations
  • Add equivalent Azure CLI (az) commands for all PowerShell cmdlet examples, especially for key rotation and account management.
  • Include Bash shell examples and instructions for Linux/macOS users where applicable.
  • Present cross-platform options side-by-side, or alternate the order so Linux tools are not always listed after Windows/PowerShell.
  • Reference both PowerShell and Python runbooks equally in tutorials and next steps, and add Bash or other language runbook examples if supported.
  • Explicitly mention platform neutrality of the Azure portal and clarify that all steps can be performed from any OS.
  • Provide links to Linux-specific documentation or troubleshooting guides for Azure Automation.
GitHub Create Pull Request
Automation Create modular runbooks in Azure Automation .../main/articles/automation/automation-child-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 Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. All examples use PowerShell syntax and cmdlets (e.g., Start-AzAutomationRunbook, Disable-AzContextAutosave), with no mention of Linux shell scripting, Python runbooks, or cross-platform alternatives. Windows/PowerShell terminology and modules are introduced first and exclusively, and there is no guidance for users working in Linux environments or with non-PowerShell runbook types.
Recommendations
  • Add equivalent examples using Python runbooks, which are supported in Azure Automation and commonly used on Linux.
  • Include notes or sections on how to create and call modular runbooks using Bash or other Linux shell scripts, if supported.
  • Mention cross-platform considerations, such as authentication and context management, for Linux and non-Windows environments.
  • Clarify which features and cmdlets are Windows/PowerShell-specific and provide Linux alternatives or limitations where applicable.
  • Reorder or balance the presentation so that Windows/PowerShell and Linux/Python approaches are given equal prominence.
GitHub Create Pull Request
Automation Use an alert to trigger an Azure Automation runbook ...utomation/automation-create-alert-triggered-runbook.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 exhibits a strong Windows bias. All code samples and runbook examples use PowerShell exclusively, with no mention or examples of Python or other cross-platform scripting languages supported by Azure Automation. Prerequisites and links reference Windows-centric resources (e.g., creating Windows VMs, installing PowerShell modules), and the runbook creation workflow defaults to PowerShell. There are no Linux-specific instructions, nor are Bash or Python alternatives provided. The documentation assumes familiarity with Windows tools and patterns, and does not address Linux users or their workflows.
Recommendations
  • Provide equivalent examples using Python runbooks, which are supported in Azure Automation and widely used on Linux.
  • Include instructions and links for creating and managing Linux VMs, not just Windows VMs.
  • Add guidance for installing and using Az CLI (cross-platform) in addition to PowerShell, especially for assigning permissions and managing resources.
  • Explicitly mention that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical, etc.), and show how to select and use them.
  • Offer Bash/CLI examples for steps that currently only show PowerShell, such as role assignment and VM management.
  • Clarify any platform-specific limitations or considerations (e.g., differences in managed identity usage between Windows and Linux VMs).
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.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 bias toward Windows and PowerShell. All migration scripts and runbook examples are provided exclusively in PowerShell and PowerShell Workflow, with no mention of Bash, Python, or other Linux-native scripting options. The instructions and tabs for Hybrid Runbook Worker installation and migration reference Windows first and do not provide Linux-specific steps or examples. There is no guidance for Linux users on how to perform equivalent disaster recovery tasks using Linux tools or scripting languages.
Recommendations
  • Provide equivalent migration scripts and runbook examples using Bash, Python, or other Linux-native tools.
  • Add Linux-specific tabs and instructions for Hybrid Runbook Worker installation, deletion, and migration.
  • Ensure that both Windows and Linux procedures are presented in parallel, with equal prominence and detail.
  • Include references to Linux command-line tools and automation patterns where appropriate.
  • Clarify any platform-specific limitations or requirements for disaster recovery steps.
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-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 page is heavily biased towards Windows environments. All examples, tooling, and step-by-step instructions focus exclusively on Windows, PowerShell, and Windows-specific package managers (Chocolatey). Linux is only mentioned in passing, with no practical examples, instructions, or equivalent tooling provided. The use of PowerShell DSC and Windows Management Framework further reinforces the Windows-centric approach, and there are no references to Linux configuration management tools or package managers beyond a brief mention of apt-get.
Recommendations
  • Provide equivalent Linux examples using native tools (e.g., Azure Automation DSC for Linux, or alternatives such as Ansible, Chef, or Puppet).
  • Include step-by-step instructions for setting up continuous deployment on Linux VMs, using Linux package managers (apt, yum, etc.) and configuration management.
  • Offer sample configuration scripts for Linux (e.g., Bash, Python, or cross-platform PowerShell Core) in addition to Windows PowerShell.
  • Mention and link to Linux-compatible VM extensions and Azure Automation modules.
  • Clarify in the introduction whether the guide is Windows-only, or update it to be cross-platform where possible.
  • Add a section comparing Windows and Linux approaches, highlighting any differences and providing guidance for both.
GitHub Create Pull Request
Automation Configure data at scale for Azure Automation State Configuration ...cles/automation/automation-dsc-config-data-at-scale.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 is heavily focused on Windows and PowerShell, with all examples and instructions referencing Windows PowerShell DSC and related cmdlets. There is no mention of Linux equivalents, nor are there examples or guidance for configuring data at scale for Linux environments. The prerequisites and next steps are all Windows/PowerShell-centric, and Linux is only referenced in a link, not in the main content or examples.
Recommendations
  • Add explicit examples and instructions for configuring data at scale using Linux DSC agents, including relevant commands and file formats.
  • Mention and describe Linux-compatible tools (such as Open Management Infrastructure (OMI) and cross-platform DSC) where appropriate.
  • Provide parity in documentation structure, ensuring that Linux onboarding, configuration, and management steps are presented alongside Windows steps.
  • Update prerequisites and applicability to include Linux platforms where supported.
  • Include links to Linux-specific documentation and community resources.
GitHub Create Pull Request
← Previous Page 2 of 40 Next →