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 651-675 of 982 flagged pages
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-02-20 00:00
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 public network access flags, without offering equivalent CLI or scripting examples for Linux/macOS users. Additionally, PowerShell is mentioned before any cross-platform alternatives, creating friction for non-Windows users. However, the rest of the documentation is largely platform-neutral, and Azure Automation features discussed (Hybrid Runbook Worker, Update Management, DSC) are available for both Windows and Linux machines.
Recommendations
  • Add Azure CLI and/or REST API examples for configuring public network access flags, alongside the PowerShell example.
  • Explicitly mention that the PowerShell example is for Windows users, and provide guidance for Linux/macOS users.
  • Where possible, present cross-platform commands (e.g., Azure CLI) before or alongside PowerShell examples.
  • Clarify that both Windows and Linux Hybrid Runbook Workers are supported, and provide links to relevant Linux documentation 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-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page heavily focuses on PowerShell and Windows-centric tools and patterns. Most examples, parameter types, and workflows are presented using PowerShell, PowerShell Workflow, and graphical runbooks (which are also PowerShell-based). Windows/PowerShell terminology and tooling are referenced throughout, with only brief mention of Python runbooks. The examples for starting runbooks, passing parameters, and working with JSON objects are almost exclusively PowerShell-based, and Windows PowerShell features are discussed. There is little to no coverage of Linux/macOS-specific workflows or CLI tools (e.g., Bash, Azure CLI), and PowerShell examples are shown first and most frequently.
Recommendations
  • Add equivalent examples using Azure CLI (bash) for assigning parameters and starting runbooks, especially for Linux/macOS users.
  • Clarify that PowerShell examples can be run cross-platform (PowerShell Core), and note any Windows-specific limitations.
  • Expand Python runbook examples to show parameter passing and invocation from Linux/macOS environments.
  • Mention and demonstrate how to use REST API and SDKs from Linux/macOS, including sample shell commands (curl, jq) for REST calls.
  • Balance the order of examples so that PowerShell and non-Windows approaches are presented equally or in parallel.
GitHub Create Pull Request
Automation Manage modules in Azure Automation ...b/main/articles/automation/shared-resources/modules.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on PowerShell modules and Windows-centric workflows for Azure Automation. Most examples, tools, and instructions reference PowerShell, Windows PowerShell versions, and Windows-specific cmdlets. Internal cmdlets and modules are noted as unavailable on Linux Hybrid Runbook Workers, but Linux alternatives or parity are not discussed. Python modules are briefly mentioned, but no Linux-specific guidance or examples are provided.
Recommendations
  • Add explicit guidance and examples for Linux Hybrid Runbook Workers, including module management and limitations.
  • Provide parity for module import, update, and deletion using Linux tools or CLI (e.g., Azure CLI, Bash) where possible.
  • Clarify which features are Windows-only and which are cross-platform, and offer Linux/macOS alternatives or workarounds.
  • Expand documentation on Python modules and other cross-platform scripting options, including examples.
  • Include a comparison table or section outlining feature support differences between Windows and Linux Hybrid Runbook Workers.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page heavily features PowerShell cmdlets and examples, with all certificate management tasks (creation, upload, retrieval) shown exclusively using PowerShell. There are no Bash, CLI, or Linux-native examples for certificate management, and PowerShell is presented first and most prominently. Python examples are provided for runbook access, but not for certificate creation or upload. The page assumes PowerShell as the primary tool, which may create friction for Linux/macOS users who prefer Bash or Azure CLI.
Recommendations
  • Add Azure CLI examples for certificate creation, upload, and management tasks.
  • Include Bash shell scripts or commands for Linux/macOS users where possible.
  • Document any limitations or parity gaps between PowerShell and CLI for certificate management in Azure Automation.
  • Present CLI or Bash examples alongside PowerShell, not only after or instead of.
  • Clarify if PowerShell is required for certain tasks, and provide guidance for Linux/macOS users (e.g., using PowerShell Core, or alternatives).
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page for managing credentials in Azure Automation is heavily focused on Windows PowerShell tools and patterns. All CLI examples are PowerShell-based, and cmdlet tables exclusively reference PowerShell/Az modules. Windows PowerShell is mentioned as the primary method for creating credential assets, with no equivalent Bash, Linux CLI, or cross-platform scripting examples. While Python runbook examples are provided, there is no guidance for Linux-native shell scripting or non-PowerShell automation. The structure and ordering of the page consistently present Windows/PowerShell approaches first and in greater detail.
Recommendations
  • Add examples for managing credentials using Azure CLI (az) commands, which are cross-platform.
  • Include guidance or examples for Bash or shell scripting where applicable, especially for Linux/macOS users.
  • Clarify that PowerShell Core (pwsh) is cross-platform and indicate if the cmdlets work on Linux/macOS, or note any limitations.
  • Provide parity in documentation structure by presenting Python and CLI examples alongside PowerShell, not only after.
  • Explicitly state if certain features are Windows-only, or if PowerShell cmdlets are supported on Linux/macOS.
GitHub Create Pull Request
Automation Encryption of secure assets in Azure Automation ...icles/automation/automation-secure-asset-encryption.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides extensive PowerShell-based examples for all key configuration steps, with REST API alternatives, but does not include Azure CLI or bash examples. PowerShell is presented as the primary scripting interface, which may create friction for Linux/macOS users who typically use Azure CLI or bash. References to PowerShell modules and cmdlets are frequent and precede any mention of other tools.
Recommendations
  • Add Azure CLI examples for all major configuration steps, including assigning managed identities, configuring Key Vault access policies, and updating Automation account encryption settings.
  • Where PowerShell is referenced, provide equivalent bash/CLI commands or scripts.
  • Explicitly mention that PowerShell Core is cross-platform if PowerShell must be used, and provide installation guidance for non-Windows users.
  • Reorder sections or provide parallel examples so that Linux/macOS-friendly tools (like Azure CLI) are not secondary.
  • Clarify in prerequisites that all steps can be performed from Linux/macOS using CLI or REST, not just PowerShell.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-19 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 shows a moderate Windows bias. Windows/PowerShell tools and cmdlets are mentioned first or exclusively in several sections (e.g., data retention, backup, DSC node removal, runbook export), while Linux equivalents are missing or only briefly referenced. Linux guidance is present for TLS configuration, but not for other management or export tasks.
Recommendations
  • Provide Linux/CLI/REST API equivalents for PowerShell cmdlets such as Unregister-AzAutomationDscNode, Get-AzAutomationRunbookContent, and Export-AzAutomationDscConfiguration.
  • When describing export or backup procedures, include az CLI or REST API examples alongside PowerShell.
  • In tables and lists, present Linux and Windows options with equal prominence, or group them together rather than listing Windows first.
  • Clarify when a feature or cmdlet is Windows-only, and suggest alternatives for Linux users where possible.
  • Add explicit Linux examples for asset management and DSC node removal, or link to relevant Linux documentation.
GitHub Create Pull Request
Automation Manage modules in Azure Automation ...b/main/articles/automation/shared-resources/modules.md
Medium Priority View Details →
Scanned: 2026-02-19 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 PowerShell modules and Windows-centric workflows, with most examples, instructions, and screenshots referencing Windows tools, cmdlets, and portal UI. Linux Hybrid Runbook Worker support is mentioned only to note limitations, and there are no Linux-specific examples or guidance. Python module support is referenced but not detailed. The internal cmdlets and module management instructions are Windows-oriented, and Linux users are left without parity in critical areas.
Recommendations
  • Add explicit instructions and examples for managing modules on Linux Hybrid Runbook Workers, including any supported workflows or limitations.
  • Provide parity for module import, update, and deletion using Linux tools (e.g., Bash, Azure CLI) where possible.
  • Include Linux/macOS-specific guidance for authoring and packaging custom modules, noting any differences in file structure or compatibility.
  • Clarify which features are Windows-only and which are cross-platform, and provide links or references to Linux-specific documentation where available.
  • Expand the Python module section to include more details and examples, especially for Linux users.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page provides disaster recovery guidance for Azure Automation, which applies to both Linux and Windows VMs. However, all migration examples and scripts are PowerShell-based, with no mention of Bash, Python, or cross-platform alternatives. Instructions and links for Hybrid Runbook Worker installation use Windows tabs/paths first, and Linux-specific guidance is not surfaced or referenced. The documentation assumes PowerShell as the default tooling, which creates friction for Linux/macOS users.
Recommendations
  • Provide equivalent Bash or Python scripts for asset migration, or clarify if PowerShell Core (pwsh) is fully supported on Linux/macOS for these tasks.
  • Add explicit Linux/macOS instructions and examples for Hybrid Runbook Worker installation and management.
  • Mention PowerShell Core compatibility and installation steps for Linux/macOS users, including any prerequisites.
  • Where possible, offer ARM template or REST API alternatives for migration tasks.
  • Ensure that documentation tabs or sections show Linux examples first or equally alongside Windows examples.
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-02-19 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-specific tools and patterns. All code examples and module references are PowerShell-based, with no mention of Bash, Azure CLI, or cross-platform scripting alternatives. The process for creating credential assets and authenticating to Azure is described only using PowerShell cmdlets, and the only automation script provided is a PowerShell workflow. There are no Linux/macOS-specific instructions or examples.
Recommendations
  • Add equivalent examples using Azure CLI (az) for credential management and authentication, which are cross-platform.
  • Provide Bash or Python runbook examples for Azure Automation, or clarify if only PowerShell runbooks are supported.
  • Explicitly state platform limitations if Azure Automation only supports PowerShell for these scenarios.
  • Mention cross-platform PowerShell (pwsh) if the instructions are compatible, or clarify if only Windows PowerShell is supported.
  • List Linux/macOS prerequisites or alternatives where possible, such as using Azure CLI to manage credentials.
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-02-19 00:00
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, without offering an equivalent CLI or ARM template example for Linux/macOS users. Additionally, PowerShell is mentioned before any cross-platform alternatives, creating friction for non-Windows users. However, the overall guidance is platform-neutral, and Azure Automation supports both Windows and Linux Hybrid Runbook Workers.
Recommendations
  • Add Azure CLI and/or ARM template examples for configuring 'publicNetworkAccess' property, alongside the PowerShell example.
  • Explicitly mention that the configuration steps can be performed from any OS using Azure CLI, REST API, or portal.
  • Where PowerShell is used, provide cross-platform alternatives or clarify if the step is Windows-specific.
  • Ensure screenshots and instructions reference both Windows and Linux scenarios where applicable.
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-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page heavily focuses on PowerShell examples and Windows-centric tooling, with nearly all code snippets, parameter handling, and automation workflows demonstrated using PowerShell or PowerShell Workflow. There is minimal coverage of Python runbooks, and no examples or guidance are provided for Linux/macOS users on how to interact with Azure Automation runbooks using native shell tools (e.g., Bash, CLI), nor is there parity in examples for starting runbooks from Linux environments. The REST API and SDK sections are platform-neutral, but the practical, step-by-step guidance is overwhelmingly Windows/PowerShell oriented.
Recommendations
  • Add examples for starting runbooks using Azure CLI (az automation runbook start) from Bash or Linux/macOS terminals.
  • Provide sample Bash scripts for passing parameters to runbooks, including JSON parameter handling.
  • Expand the Python runbook section with more detailed examples, including parameter parsing and invocation from Linux/macOS.
  • Explicitly mention cross-platform alternatives to PowerShell for Linux/macOS users, and clarify any limitations.
  • Include notes or tables summarizing which features/tools are available on Windows, Linux, and macOS.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page heavily emphasizes PowerShell cmdlets and Windows-centric tooling for certificate management in Azure Automation. All detailed command-line examples are PowerShell-based, with no mention of Linux shell (bash) or cross-platform CLI equivalents. PowerShell examples are presented first and are the only option for tasks like certificate creation and deployment, while Python examples are limited to certificate retrieval in runbooks. There are no Linux/macOS-specific instructions or examples for certificate management outside of Python runbooks.
Recommendations
  • Add Azure CLI examples for certificate management tasks (creation, retrieval, deletion) to provide cross-platform parity.
  • Mention whether PowerShell Core (pwsh) is supported on Linux/macOS for these cmdlets, and clarify any limitations.
  • Include bash or shell script examples for uploading certificates, or reference relevant Azure CLI documentation.
  • Explicitly state if certain tasks are only possible via PowerShell and provide guidance for Linux/macOS users.
  • Reorder examples so that cross-platform solutions (Azure CLI, REST API) are presented alongside or before PowerShell.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page is heavily focused on PowerShell and Windows-centric tools and patterns. All credential management examples and cmdlets are PowerShell-based, with explicit references to Windows PowerShell and PSCredential objects. The only non-Windows section is for Python runbooks, but there are no Linux shell (bash) or cross-platform CLI examples. The portal instructions are platform-neutral, but all scripting and automation guidance assumes Windows/PowerShell environments.
Recommendations
  • Add examples using Azure CLI (az) for credential asset management, which is cross-platform.
  • Clarify whether credential assets can be managed or accessed from Linux/macOS environments, and provide guidance if possible.
  • Include bash or shell scripting examples where applicable, or explicitly state limitations if PowerShell is required.
  • Mention PowerShell Core (pwsh) compatibility for cross-platform users, and provide examples using pwsh if supported.
  • Add a section summarizing platform support for Azure Automation credential assets, including any Linux/macOS limitations.
GitHub Create Pull Request
Automation What's New in Azure Automation .../azure-docs/blob/main/articles/automation/whats-new.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page for 'What's New in Azure Automation' demonstrates a moderate bias towards Windows and PowerShell. Most examples and feature announcements reference PowerShell runbooks, often before Python equivalents. PowerShell versions and module retirements are highlighted more frequently and in greater detail. While Linux is mentioned (e.g., Hybrid Runbook Worker support for Windows and Linux), examples and guidance are predominantly PowerShell-focused, and Windows terminology appears first in several places.
Recommendations
  • Ensure that Python runbook updates and examples are given equal prominence alongside PowerShell announcements.
  • When listing supported platforms (Windows and Linux), alternate the order or explicitly state parity.
  • Provide more examples or links for Linux-specific scenarios, such as shell scripting or Linux tools in Automation.
  • Include guidance or references for managing Automation assets from Linux/macOS environments (e.g., using Azure CLI or Python).
  • Highlight Python package management and troubleshooting in parity with PowerShell module updates.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-18 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 PowerShell and Windows-centric patterns for managing credentials in Azure Automation. All CLI examples are in PowerShell, and references to credential objects (PSCredential) are tied to Windows/PowerShell concepts. There are no examples or guidance for Linux/macOS shell users (e.g., Bash, CLI), nor is there mention of cross-platform alternatives. The Python section is present, but only for runbooks, not for asset management or CLI usage. The portal instructions are platform-neutral, but all scripting is Windows/PowerShell-oriented.
Recommendations
  • Add Azure CLI examples for credential asset management (creation, retrieval, deletion) to provide parity for Linux/macOS users.
  • Clarify whether credential assets can be managed via Azure CLI or REST API, and provide links or examples if available.
  • Explicitly state if PowerShell is required for certain operations, and mention cross-platform PowerShell Core compatibility where relevant.
  • Include a note or section for Linux/macOS users, outlining any limitations or alternative approaches.
  • Expand Python examples to include asset creation and management, not just credential retrieval in runbooks.
GitHub Create Pull Request
Automation Manage modules in Azure Automation ...b/main/articles/automation/shared-resources/modules.md
Medium Priority View Details →
Scanned: 2026-02-18 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 modules and Windows-centric workflows, with exclusive use of PowerShell cmdlets and terminology. There is minimal mention of Linux or cross-platform scenarios, and Linux-specific guidance is largely absent. Some features and internal cmdlets are explicitly unavailable on Linux Hybrid Runbook Workers, but the documentation does not provide Linux alternatives or equivalent workflows.
Recommendations
  • Add explicit guidance and examples for Linux Hybrid Runbook Workers, including supported module types and any differences in usage.
  • Where features are Windows-only (e.g., internal cmdlets), clearly indicate Linux alternatives or workarounds, or link to relevant Linux documentation.
  • Include Python and cross-platform module management examples where possible, especially in sections about importing and managing modules.
  • Clarify which instructions apply to all platforms and which are Windows-specific, to help Linux/macOS users avoid confusion.
  • Provide a summary table or section outlining feature parity and limitations between Windows and Linux Hybrid Runbook Workers.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation heavily relies on PowerShell scripts and workflows for migration tasks, with no equivalent examples or guidance for Linux-native tools or scripting languages (e.g., Bash, Python). All migration instructions and runbook examples are PowerShell-based, and there is no mention of alternatives for Linux users. While the page states applicability to both Linux and Windows VMs, the practical guidance is Windows-centric.
Recommendations
  • Provide Bash or Python script examples for migrating Automation account assets, or at least mention how Linux users can accomplish the same tasks.
  • Include instructions for importing and executing runbooks using Linux-friendly tools or Azure CLI.
  • Clarify whether PowerShell Core (pwsh) is supported on Linux for these scripts, and provide guidance for Linux users to install and use PowerShell if required.
  • Add explicit notes or sections for Linux/macOS users, highlighting any differences or prerequisites.
  • Where possible, offer Azure CLI alternatives to PowerShell commands.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-18 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 frequently presents Windows/PowerShell guidance and tools first, with several sections referencing Windows registry settings and PowerShell cmdlets for data management and backup. Linux guidance is present but less detailed, and Linux equivalents for some PowerShell cmdlets are missing. This creates friction for Linux users, who may need to infer or research equivalent steps.
Recommendations
  • Provide explicit Linux command-line examples (e.g., using Azure CLI, Bash, or Python) alongside or before Windows/PowerShell examples.
  • Include Linux-specific instructions for tasks currently only described with PowerShell cmdlets, such as unregistering DSC nodes, exporting runbooks, and exporting DSC configurations.
  • Where possible, reference cross-platform tools (e.g., Azure CLI, REST API) rather than Windows-only tools.
  • Balance the order of presentation so Linux and Windows guidance are given equal prominence.
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-02-18 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 Windows PowerShell and Windows-specific tools. All code examples and instructions use PowerShell cmdlets, with no mention of Bash, CLI, or Linux/macOS alternatives. The credential asset creation is described only via the Azure portal or Windows PowerShell, and the runbook example is PowerShell-only. There is no guidance for Linux/macOS users or for using cross-platform tools like Azure CLI.
Recommendations
  • Add equivalent examples using Azure CLI and Bash for credential asset creation and runbook authentication.
  • Clarify whether Azure Automation supports Python or Bash runbooks for these authentication scenarios, and provide examples if so.
  • Mention cross-platform alternatives to PowerShell modules where available, such as Azure CLI or REST API usage.
  • Explicitly state any limitations for Linux/macOS users if PowerShell is required, and link to installation instructions for PowerShell Core on non-Windows platforms.
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-02-18 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 and Windows-centric patterns, with nearly all examples, screenshots, and code snippets using PowerShell or Windows tools. There are no Linux/bash examples for starting runbooks or passing parameters, and PowerShell is presented as the primary interface for automation, even though Azure Automation supports Python runbooks and REST API/SDK methods that are cross-platform. Linux users may find it difficult to translate PowerShell-centric instructions to their environment.
Recommendations
  • Add bash/CLI examples for starting runbooks and passing parameters, especially for REST API usage.
  • Clarify that PowerShell instructions can be run on Linux/macOS via PowerShell Core, and provide guidance for installing PowerShell on those platforms.
  • Include Python examples for parameter passing, not just a link to another tutorial.
  • Provide explicit instructions for using Azure CLI to start runbooks and assign parameters, highlighting cross-platform compatibility.
  • Mention that SDK and REST API methods are platform-agnostic, and show sample usage from Linux/macOS environments.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-18 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 heavily emphasizes PowerShell cmdlets and Windows-centric tooling. All detailed examples for certificate creation and management use PowerShell, with no equivalent Bash, CLI, or Linux-native tooling shown. PowerShell is presented first and in depth, while Python examples are limited to certificate retrieval and lack parity for creation or management. There is no mention of Linux/macOS workflows or tools for certificate management in Azure Automation.
Recommendations
  • Add Azure CLI examples for certificate creation, retrieval, and management, where possible.
  • Provide guidance for Linux/macOS users on preparing and uploading certificates (e.g., using openssl, Azure CLI, or REST API).
  • Include Bash or shell script examples for certificate operations, especially for uploading .pfx/.cer files.
  • Clarify whether PowerShell examples are cross-platform (PowerShell Core) or Windows-only, and provide alternatives if not.
  • Ensure Python examples cover certificate creation and management, not just retrieval.
GitHub Create Pull Request
Automation Encryption of secure assets in Azure Automation ...icles/automation/automation-secure-asset-encryption.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides extensive PowerShell-based examples for all major configuration steps, with REST API alternatives, but does not offer Azure CLI or Bash examples. PowerShell is presented as the primary scripting interface, and Linux/macOS users are not shown equivalent command-line workflows, which may create friction for those not using Windows or PowerShell.
Recommendations
  • Add Azure CLI examples for all major steps (assigning managed identity, configuring Key Vault access policy, updating Automation account encryption).
  • Where PowerShell is referenced, clarify that the Azure Az PowerShell module is cross-platform and provide Bash/CLI equivalents where possible.
  • Reorder sections or add callouts to make it clear that REST and CLI options are equally supported.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI or REST, and link to relevant CLI documentation.
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-02-18 00:00
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, without offering an equivalent CLI, ARM template, or REST API example. While the page covers both Windows and Linux scenarios (e.g., Hybrid Runbook Worker, Update Management), the scripting example is Windows-centric. Additionally, PowerShell is presented as the primary automation method, which may create friction for Linux/macOS users who prefer Bash, Azure CLI, or other tools.
Recommendations
  • Add Azure CLI, ARM template, or REST API examples for configuring 'publicNetworkAccess' to ensure Linux/macOS users can follow along without relying on PowerShell.
  • Where possible, provide Bash or cross-platform scripting alternatives alongside PowerShell examples.
  • Explicitly state that PowerShell is not required and that equivalent actions can be performed using other tools.
  • Review other sections for implicit Windows-first language and ensure parity in tool recommendations.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-17 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 demonstrates a moderate Windows bias. Windows/PowerShell tools and cmdlets are consistently mentioned first or exclusively for several management and backup tasks (e.g., unregistering DSC nodes, exporting runbooks/configurations). Linux equivalents (such as Azure CLI, REST API, or bash examples) are not provided for these operations. In the TLS upgrade section, both Windows and Linux guidance are present, but Windows instructions are more detailed and linked, while Linux is limited to a Python script without broader context or alternative methods.
Recommendations
  • Provide Azure CLI, REST API, or bash examples alongside or in place of PowerShell cmdlets for tasks such as unregistering DSC nodes, exporting runbooks, and exporting DSC configurations.
  • List Linux and cross-platform methods before or alongside Windows/PowerShell approaches in tables and instructions.
  • Link to Linux-specific documentation or official Azure CLI references where available.
  • Clarify when a feature or cmdlet is Windows-only, and suggest alternatives for Linux/macOS users if possible.
GitHub Create Pull Request
← Previous Page 27 of 40 Next →