Automation

232
Total Pages
137
Linux-Friendly Pages
95
Pages with Bias
40.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

365 issues found
Showing 126-150 of 365 flagged pages
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides disaster recovery guidance for Azure Automation that applies to both Linux and Windows VMs. However, all migration scripts and runbook examples are exclusively PowerShell-based, with no mention of Bash, Python, or CLI alternatives. The only automation asset migration tools referenced are PowerShell scripts and workflows, and all step-by-step instructions assume use of PowerShell. There are no Linux-native scripting examples or guidance for users who prefer Bash or Python, which creates friction for Linux-focused users.
Recommendations
  • Provide equivalent migration scripts or runbooks using Azure CLI, Bash, or Python for users who do not use PowerShell.
  • Explicitly mention if PowerShell is the only supported method for asset migration, and provide guidance for Linux users on how to install and use PowerShell Core if necessary.
  • Add examples or references for Linux/macOS users, such as using PowerShell Core on Linux, or alternative approaches using REST API or Azure CLI.
  • Clarify in the prerequisites that PowerShell is required, and link to instructions for installing PowerShell on Linux/macOS if no alternatives exist.
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
Medium Priority View Details →
Scanned: 2026-01-25 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily focused on PowerShell and Windows-centric tooling, with all code examples and module references using PowerShell. There are no Bash, CLI, or Linux/macOS-specific examples or guidance. Windows terminology (e.g., 'Windows PowerShell') is used, and Linux alternatives are not mentioned, which may create friction for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI examples for credential management and runbook authentication.
  • Clarify which steps are platform-agnostic and which require Windows/PowerShell, and provide alternatives where possible.
  • Include notes or links for Linux/macOS users on how to perform similar tasks using supported tools.
  • If Azure Automation supports Python runbooks or other languages, mention and provide examples.
  • Avoid using 'Windows PowerShell' terminology when referring to cross-platform PowerShell Core, unless specifically required.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-01-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation is heavily focused on PowerShell cmdlets and Windows tooling for managing credentials in Azure Automation. All CLI examples are PowerShell-based, and references to creating credentials outside the portal are exclusively via Windows PowerShell. The documentation does mention Python runbooks, but there are no examples or guidance for Linux/macOS shell environments or cross-platform CLI tools (e.g., Azure CLI, Bash). Windows/PowerShell tools are presented first and in greater detail.
Recommendations
  • Add examples for creating and managing credential assets using Azure CLI, which is cross-platform and works on Linux/macOS.
  • Clarify which steps or cmdlets are PowerShell-specific and provide alternative instructions for Linux/macOS users where possible.
  • Include Bash or shell scripting examples for credential retrieval and usage, if supported.
  • Explicitly state platform requirements for PowerShell-based steps, and link to cross-platform alternatives.
  • Ensure parity in example detail and guidance for Python runbooks and other supported languages.
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
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily focused on PowerShell and Windows-centric tooling, such as PSCredential, Get-AutomationPSCredential, and Windows PowerShell modules. All code examples and instructions use PowerShell, with no mention of Bash, Azure CLI, or Linux/macOS alternatives. The creation of credential assets and runbook examples are exclusively shown using PowerShell, which may create friction for Linux/macOS users who prefer or require non-PowerShell environments.
Recommendations
  • Add equivalent examples using Azure CLI and Bash for credential management and runbook authentication.
  • Clarify which steps are PowerShell-specific and provide guidance for Linux/macOS users where possible.
  • Mention cross-platform alternatives to PSCredential and PowerShell modules, such as using environment variables or Azure CLI for authentication.
  • Include notes on how Azure Automation can be used with Python or other cross-platform languages, if supported.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for managing credentials in Azure Automation is heavily focused on PowerShell, specifically Windows PowerShell and Az modules. All command-line examples are given in PowerShell, with no mention of Bash, CLI, or Linux-native tools. The process for creating credentials outside the portal is described only with Windows PowerShell, and PowerShell cmdlets are listed first and in detail. Python is supported and documented, but only as an alternative for runbooks, not for asset management or administrative tasks. There are no Linux/macOS shell examples or references to cross-platform CLI usage.
Recommendations
  • Add Azure CLI examples for credential management, if supported.
  • Clarify whether PowerShell Core (cross-platform) is supported and provide examples if so.
  • Explicitly state platform requirements for PowerShell cmdlets (Windows-only or cross-platform).
  • If credential management is possible via REST API or SDKs, provide links or examples.
  • Consider reordering sections so that platform-neutral or cross-platform methods are presented before Windows-specific ones.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides disaster recovery guidance for Azure Automation that applies to both Linux and Windows VMs. However, all migration scripts and runbook examples are exclusively in PowerShell or PowerShell Workflow, with no Bash, Python, or cross-platform alternatives. The documentation references only PowerShell modules and tools, and does not provide Linux-native scripting options or examples. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other scripting environments.
Recommendations
  • Provide equivalent migration scripts or runbook examples in Bash or Python, or explicitly state if PowerShell is the only supported method.
  • Clarify if PowerShell Core (pwsh) is required/supported on Linux/macOS, and provide installation guidance if so.
  • Mention or link to any available cross-platform tools or SDKs (e.g., Azure CLI, Python SDK) that can be used for asset migration.
  • Add a note about PowerShell availability on Linux/macOS and any limitations.
  • If PowerShell is required due to Azure Automation platform constraints, make this explicit for Linux users.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance for TLS upgrades, but Windows instructions and PowerShell cmdlets are mentioned first and more frequently. Several backup and retention examples rely on Windows PowerShell cmdlets, with no Linux CLI or cross-platform alternatives provided for tasks like exporting runbooks or DSC configurations. References to Windows registry settings and PowerShell modules are prominent, while Linux equivalents (such as Azure CLI or REST API) are missing.
Recommendations
  • Include Azure CLI or REST API examples for exporting runbooks and DSC configurations, alongside PowerShell cmdlets.
  • Provide Linux/macOS-specific instructions for asset backup and retrieval, not just Windows PowerShell.
  • Present platform guidance in a parallel or grouped manner, rather than listing Windows first.
  • Reference cross-platform tools (e.g., Azure CLI, Python SDK) where possible, especially for automation and backup tasks.
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-24 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/PowerShell bias. Most examples, code snippets, and workflows are centered around PowerShell, PowerShell Workflow, and graphical runbooks (which are inherently PowerShell-based). The only non-Windows example is a brief mention of Python runbooks, which lacks detailed code samples and practical usage scenarios. All CLI examples for starting runbooks use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux-native workflows. The process for passing parameters, especially with JSON, is exclusively shown using PowerShell, and there are no Linux shell or cross-platform alternatives provided.
Recommendations
  • Add equivalent examples using Azure CLI (az automation runbook start) for assigning parameters, including JSON object passing.
  • Provide Bash or shell script examples for starting runbooks and passing parameters, especially for Python runbooks.
  • Expand the Python runbook section with concrete code samples and parameter passing scenarios.
  • Clarify which features are platform-agnostic and which are PowerShell-specific, to help Linux/macOS users understand applicability.
  • Include notes or links to cross-platform tooling where possible (e.g., REST API usage from curl or other Linux tools).
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for managing certificates in Azure Automation is heavily PowerShell-centric, with all creation and management examples using PowerShell cmdlets and Windows-centric tooling. PowerShell examples are presented first and in greater detail than Python, and there are no Linux-native CLI or bash examples. The certificate provider requirement ('Microsoft Enhanced RSA and AES Cryptographic Provider') is Windows-specific, and workarounds for portal limitations are PowerShell-only. This creates friction for Linux/macOS users who may prefer Azure CLI, bash, or other cross-platform tools.
Recommendations
  • Add equivalent Azure CLI examples for certificate management tasks (creation, retrieval, deletion).
  • Clarify whether certificate provider requirements are Windows-only and provide guidance for Linux/macOS users on generating compatible certificates.
  • Include bash or shell script examples for uploading and managing certificates.
  • Present Python and cross-platform examples with equal prominence to PowerShell.
  • Document any limitations or differences for Linux/macOS users explicitly.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation for disaster recovery in Azure Automation is heavily focused on PowerShell scripts and workflows for migration, with no equivalent examples or guidance for Linux users (e.g., Bash, CLI, Python SDK). All migration automation is described using PowerShell, which is more familiar to Windows users. While the documentation mentions both Windows and Linux Hybrid Runbook Workers, all automation and scripting examples are PowerShell-centric, and there are no Linux-native or cross-platform alternatives provided.
Recommendations
  • Provide equivalent migration scripts or automation examples using Azure CLI, Bash, or Python SDK to support Linux/macOS users.
  • Explicitly mention if PowerShell Core (pwsh) is supported on Linux/macOS and provide instructions for those platforms.
  • Add guidance or links for running PowerShell scripts on Linux/macOS, if PowerShell is the only supported method.
  • Include at least one end-to-end example for Linux users, such as using Bash or Azure CLI to replicate Automation account assets.
  • Clarify any platform limitations in the prerequisites or introduction.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page provides both Windows and Linux guidance for TLS upgrades, but several critical examples and references are Windows/PowerShell-centric. Key backup and retention operations reference Windows PowerShell cmdlets without Linux or cross-platform CLI alternatives. Windows registry settings and PowerShell cmdlets are mentioned before Linux equivalents, and Linux instructions are less detailed or rely on manual scripting.
Recommendations
  • Include Azure CLI or REST API examples for backup and retention operations, especially for exporting runbooks and DSC configurations, to provide parity for Linux/macOS users.
  • Add explicit Linux/macOS instructions or scripts for tasks currently covered only by Windows PowerShell cmdlets (e.g., unregistering DSC nodes, exporting runbooks/configurations).
  • Where possible, present platform-neutral or cross-platform solutions first, or provide parallel examples for both Windows and Linux/macOS.
  • Clarify when a feature or cmdlet is Windows-only, and suggest alternatives for other platforms if available.
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-23 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 and Windows-centric tooling, with most examples, screenshots, and instructions using PowerShell cmdlets and patterns. There is minimal coverage of Python runbooks, and no examples or guidance for Linux/macOS users on how to interact with Azure Automation runbooks outside of PowerShell. REST API and SDK examples are platform-neutral, but all CLI examples use PowerShell, and Windows tools are referenced exclusively.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux/macOS.
  • Provide Python runbook parameter examples with more detail, including how to pass arguments from non-Windows environments.
  • Include instructions or examples for starting runbooks from Linux/macOS terminals, such as using Bash scripts or Azure CLI.
  • Clarify that PowerShell examples can be run using PowerShell Core (pwsh) on Linux/macOS, and note any differences.
  • Where screenshots show Windows-only tools, add notes or alternative visuals for Linux/macOS users.
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
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on PowerShell-based workflows and examples, with all code samples and module instructions referencing PowerShell. There is no mention of Bash, CLI, or cross-platform scripting alternatives. The term 'Windows PowerShell' is used, and no Linux/macOS-specific guidance or parity examples are provided, which may create friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI (az) examples for credential creation, authentication, and runbook management, where possible.
  • Clarify that Azure Automation runbooks can use PowerShell Core (cross-platform) and/or Python, and provide examples for these where supported.
  • Replace 'Windows PowerShell' with 'PowerShell' where the instructions are not Windows-specific, and clarify when Windows-only modules are required.
  • Explicitly state the platform requirements for each module or script, and provide guidance for Linux/macOS users on how to achieve similar outcomes.
  • Link to documentation on using Azure Automation with Python runbooks and/or Bash scripts, if supported.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for managing credentials in Azure Automation is heavily focused on PowerShell and Windows-centric tooling. All CLI examples are provided in PowerShell, with explicit references to Windows PowerShell and PSCredential objects. There is no mention of Linux shell (bash, sh) equivalents, nor are there examples for managing credentials via Azure CLI or REST API. The Python section is present, but only for runbook usage, not for asset management. The ordering also places Windows/PowerShell methods before Python, and there is no guidance for Linux/macOS users who may wish to manage credentials outside the portal or Python runbooks.
Recommendations
  • Add examples for managing credentials using Azure CLI and/or REST API, which are cross-platform.
  • Clarify that PowerShell examples can be run using PowerShell Core on Linux/macOS, if applicable.
  • Provide guidance or links for Linux/macOS users who wish to automate credential management outside of PowerShell.
  • Reorder sections so that portal and cross-platform methods are presented before Windows/PowerShell-specific methods.
  • Explicitly state platform requirements for PowerShell cmdlets (e.g., Windows PowerShell vs PowerShell Core).
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-01-23 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 PowerShell-centric, with all command-line examples using PowerShell cmdlets and .NET types. There are no examples using Bash, Azure CLI, or Linux-native tools for certificate management. The only non-PowerShell examples are for Python runbooks, but these are limited to in-runbook usage, not certificate management or upload. The guidance for uploading certificates outside the portal recommends PowerShell as the workaround, with no Linux/macOS alternative. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Azure CLI.
Recommendations
  • Add Azure CLI examples for certificate management tasks (upload, retrieve, delete) where possible.
  • Explicitly mention if certain operations (e.g., uploading certificates) are only supported via PowerShell, and provide guidance for Linux/macOS users (e.g., using Azure CLI, REST API, or PowerShell Core on Linux).
  • If PowerShell is required, clarify that PowerShell Core is cross-platform and provide installation links for Linux/macOS.
  • Include Bash/Azure CLI equivalents alongside PowerShell examples, especially for common tasks like uploading or retrieving certificates.
  • Document any REST API options for certificate management for users who cannot use PowerShell.
GitHub Create Pull Request
Automation Manage role permissions and security in Azure Automation ...les/automation/automation-role-based-access-control.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 providing only Azure PowerShell examples for role assignment and management tasks, with no mention of equivalent Azure CLI commands or Linux/macOS workflows. The PowerShell approach is presented as the sole scripting option, and there is no guidance for users who may be working from Linux or macOS environments. This creates friction for non-Windows users who may prefer or require cross-platform tools.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlet workflows, including role assignment, listing roles, and removing assignments.
  • Explicitly mention that Azure CLI is cross-platform and provide links to relevant CLI documentation.
  • Include notes or sections clarifying that all role management operations can be performed from Linux/macOS using Azure CLI.
  • Where scripts are shown, offer both PowerShell and CLI versions side-by-side.
  • Review any referenced links to ensure Linux/macOS parity is maintained.
GitHub Create Pull Request
Automation Start an Azure Automation Runbook from a Webhook ...s/blob/main/articles/automation/automation-webhooks.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 towards Windows and PowerShell usage. All code samples, automation steps, and REST API usage are demonstrated exclusively with PowerShell commands and Windows file paths. There are no examples for Linux/macOS users (e.g., Bash, curl, or cross-platform Azure CLI). Windows tools and patterns (PowerShell cmdlets, Windows-style file paths) are mentioned exclusively and always before any Linux alternatives (which are not present). This creates friction for non-Windows users.
Recommendations
  • Provide equivalent examples using Bash and curl for webhook invocation and REST API calls.
  • Include Azure CLI examples for creating, updating, and deleting webhooks and runbooks.
  • Use platform-neutral file paths and clarify where Windows-specific syntax is used.
  • Explicitly mention cross-platform support and limitations, and link to Linux/macOS guidance where relevant.
  • Add notes or sections for Linux/macOS users, including troubleshooting tips for common issues on those platforms.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-only example for configuring the 'publicNetworkAccess' property, with no equivalent CLI, REST API, or Linux/macOS shell example. The State Configuration section references PowerShell DSC as the configuration management tool, which is Windows-centric. While the documentation mentions Linux support in the context of Update Management and Log Analytics agent, actionable examples and tooling are Windows-first or Windows-only.
Recommendations
  • Add Azure CLI and/or REST API examples for setting 'publicNetworkAccess', demonstrating parity for Linux/macOS users.
  • Include Bash or shell script equivalents alongside PowerShell commands.
  • Mention cross-platform configuration management options (e.g., Chef, Ansible, or native Linux DSC) in the State Configuration section.
  • Ensure screenshots and UI instructions clarify any OS-specific requirements or differences.
  • Explicitly state Linux/macOS support wherever features are available, and provide links to relevant Linux documentation.
GitHub Create Pull Request
Automation Azure Automation State Configuration overview ...ob/main/articles/automation/automation-dsc-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 DSC is the primary focus throughout, with Windows-specific tools and terminology (e.g., WMF, WinRM, PowerShell cmdlets) mentioned first and in more detail. Linux support is acknowledged but lacks equivalent depth, examples, or tooling references. Proxy support and configuration details are more thoroughly explained for Windows, with Linux relegated to brief mentions. No Linux-specific configuration or onboarding examples are provided.
Recommendations
  • Provide Linux-specific examples for onboarding, configuration, and troubleshooting, similar to the Windows sections.
  • Include references to Linux-native tools and commands (e.g., shell scripts, systemd integration) where appropriate.
  • Present Windows and Linux requirements and instructions in parallel, rather than listing Windows first and in greater detail.
  • Expand documentation on Linux proxy support and network configuration, matching the detail given for Windows.
  • Add links to Linux DSC extension documentation and community resources.
GitHub Create Pull Request
Automation Configure runbook output and message streams ...s/automation/automation-runbook-output-and-messages.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 Windows PowerShell, with all examples and tooling references using PowerShell cmdlets and syntax. There are no examples or guidance for Linux/macOS users, such as Bash, Python, or cross-platform CLI usage. Windows-specific tools and patterns (e.g., preference variables, PowerShell redirection, Az.Automation cmdlets) are mentioned exclusively, and the section on retrieving runbook output explicitly references 'Windows PowerShell' without alternatives. This creates friction for users operating on Linux/macOS or those using Python runbooks.
Recommendations
  • Add equivalent examples for Bash, Azure CLI, or Python where possible, especially for retrieving runbook output and handling streams.
  • Clarify which features and cmdlets are available cross-platform, and note any limitations for Linux/macOS users.
  • Include references to Python runbooks and their output handling, with sample code and retrieval methods.
  • Reorganize sections to present cross-platform approaches first or in parallel, rather than Windows/PowerShell-only.
  • Explicitly state when a feature or cmdlet is Windows-only, and provide alternatives for other platforms.
GitHub Create Pull Request
Automation Azure Automation extension for Visual Studio Code ...ation/how-to/runbook-authoring-extension-for-vscode.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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-specific requirements or provide guidance for Linux/macOS users. There are no examples or instructions tailored to Linux environments, and the documentation assumes familiarity with PowerShell, which is traditionally Windows-centric, despite PowerShell Core being cross-platform.
Recommendations
  • Explicitly mention that PowerShell Core is available on Linux/macOS and provide installation instructions for those platforms.
  • Include guidance for installing Python packages on Linux/macOS, such as using pip or system package managers.
  • Clarify any differences in extension usage or runbook debugging on Linux/macOS, if applicable.
  • Add screenshots or notes indicating that the extension works on Linux/macOS, or specify any limitations.
  • Ensure that all steps and terminology (e.g., right-click context menus) are applicable to Linux/macOS environments.
GitHub Create Pull Request
Automation Remediate noncompliant Azure Automation State Configuration servers ...b/main/articles/automation/automation-dsc-remediate.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation prioritizes Windows remediation by providing direct PowerShell examples and references to Windows-specific tools (Update-DscConfiguration, Run Command). Linux remediation is described in less detail, lacks direct script examples, and refers users to external documentation. Windows solutions are presented first and more comprehensively, while Linux users face more manual or indirect steps.
Recommendations
  • Provide direct, in-page Linux remediation script examples (e.g., Python or shell commands) similar to the PowerShell example for Windows.
  • Clarify and expand the Linux remediation steps, including explicit commands and workflow.
  • Balance the order of presentation by alternating or paralleling Windows and Linux instructions.
  • Reference Linux-specific tools and modules where applicable, not just Windows/PowerShell ones.
  • Ensure that Linux users are not required to consult external documentation for basic remediation tasks.
GitHub Create Pull Request
Automation Send an email from an Azure Automation runbook ...blob/main/articles/automation/automation-send-email.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses PowerShell for all examples and instructions, including runbook creation, resource management, and cleanup. There are no Bash, CLI, or Linux/macOS-specific instructions or examples. Windows tools and patterns (PowerShell cmdlets, Windows-centric terminology) are mentioned throughout, with no parity for Linux users. The documentation assumes the use of PowerShell both locally and in the Azure Automation context, which may create friction for users on Linux or macOS who prefer Bash or Azure CLI.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for each major step (resource creation, secret management, runbook creation, cleanup).
  • Include guidance for Linux/macOS users on installing and using Azure CLI and/or PowerShell Core.
  • Clarify that Azure Automation supports Python runbooks and provide a Python example for sending email via SendGrid.
  • Reorder sections or provide parallel instructions so Linux/macOS patterns are not always secondary to Windows/PowerShell.
  • Explicitly mention cross-platform support and link to relevant documentation for non-Windows environments.
GitHub Create Pull Request
Automation Manage Runtime Environment and Associated Runbooks in Azure Automation ...main/articles/automation/manage-runtime-environment.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias, primarily through its heavy focus on PowerShell examples, repeated references to PowerShell modules and tools (e.g., Az PowerShell package, PowerShell Gallery), and the use of Windows-centric terminology and patterns. While Python is mentioned as an alternative runtime, examples, screenshots, and REST API payloads overwhelmingly default to PowerShell scenarios. Linux/macOS-specific guidance, such as package formats, is only briefly referenced and lacks parity in example depth and clarity.
Recommendations
  • Provide equal, detailed examples for Python runbooks, including REST API payloads and portal workflows.
  • Include Linux/macOS-specific instructions and screenshots, especially for package management and runtime environment creation.
  • Highlight Python and Linux options alongside PowerShell, rather than defaulting to PowerShell-first explanations.
  • Clarify package upload formats for both PowerShell and Python, with explicit Linux/macOS guidance (e.g., .whl files, supported OS versions).
  • Add troubleshooting and usage examples for Python runbooks and Linux environments.
  • Reference cross-platform tools (e.g., Azure CLI) with parity to PowerShell, and provide examples for both.
GitHub Create Pull Request
Automation Author graphical runbooks in Azure Automation ...les/automation/automation-graphical-authoring-intro.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 around Windows PowerShell and PowerShell Workflow, with all examples, scripting references, and tooling focused exclusively on PowerShell. There is no mention of Bash, Linux shell scripting, or cross-platform alternatives, and the documentation assumes familiarity with Windows-centric tools and patterns. Linux/macOS users are not provided with equivalent examples or guidance, creating friction for those not using Windows environments.
Recommendations
  • Clarify that Azure Automation graphical runbooks are PowerShell-based and note platform limitations up front.
  • Provide explicit guidance for Linux/macOS users, including any prerequisites or limitations (e.g., PowerShell Core support, installation steps).
  • Add examples using PowerShell Core (pwsh) and clarify cross-platform compatibility.
  • Where possible, mention or link to Bash or other Linux-native automation options in Azure (e.g., Python runbooks, Bash scripts in Logic Apps).
  • Include a section comparing Windows PowerShell and PowerShell Core, with notes on differences and supported features in Azure Automation.
  • Add troubleshooting tips for Linux/macOS users (e.g., file downloads, script execution).
GitHub Create Pull Request
← Previous Page 6 of 15 Next →