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 701-725 of 982 flagged pages
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-15 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 in PowerShell, and references to credential objects and cmdlets are specific to Windows/PowerShell environments. The creation of credentials via CLI is only shown using Windows PowerShell, with no mention of Bash, Azure CLI, or Linux-native alternatives. The Python section is present, but only for runbooks, not for asset management or credential creation. Windows/PowerShell tools and patterns are mentioned first and exclusively in several sections.
Recommendations
  • Add Azure CLI examples for credential asset management, if supported.
  • Clarify whether credential management is possible via Bash or Linux shell scripts, and provide examples if so.
  • Explicitly state platform limitations if credential management is only possible via PowerShell.
  • Where possible, provide parity in examples for Linux/macOS users, such as using Azure CLI or REST API.
  • Add a note about cross-platform support and limitations for credential management in Azure Automation.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page is heavily focused on PowerShell modules and Windows-centric workflows, with almost all examples, tools, and instructions centered around PowerShell and Windows Automation environments. Internal cmdlets and features are explicitly unavailable on Linux Hybrid Runbook Workers, and Linux-specific guidance is minimal or absent. Python module support is briefly mentioned, but no Linux-native module management or examples are provided.
Recommendations
  • Add explicit guidance and examples for managing modules on Linux Hybrid Runbook Workers, including any limitations and supported workflows.
  • Provide parity in module import, update, and deletion instructions for Linux environments, including CLI or scripting alternatives where PowerShell is not available.
  • Include Linux-specific troubleshooting, best practices, and known issues for module management in Azure Automation.
  • Expand documentation for Python modules and other non-PowerShell runtimes, including how to manage them on Linux Hybrid Runbook Workers.
  • Clearly indicate which features are Windows-only and offer alternative approaches for Linux users where possible.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-14 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 and Windows-centric tooling, with all CLI examples using PowerShell cmdlets and objects (PSCredential). The creation and management of credentials outside the portal is only shown with Windows PowerShell. There is no mention of Linux-native CLI tools (e.g., Bash, Azure CLI) or cross-platform scripting approaches for credential management. While Python runbook usage is covered, all asset management examples outside the portal are Windows/PowerShell-only.
Recommendations
  • Add Azure CLI examples for credential asset creation and management, if supported.
  • Clarify whether credential management via CLI is possible on Linux/macOS, and provide relevant instructions.
  • If PowerShell Core (pwsh) is supported cross-platform, note this explicitly and provide examples for non-Windows environments.
  • Consider including Bash or other scripting examples for credential retrieval and usage, where applicable.
  • Explicitly state any platform limitations for credential management features.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell scripts and workflows for migration tasks, with no mention of Bash, Python, or other cross-platform scripting alternatives. All migration examples and instructions are PowerShell-centric, and the tabs/links for Hybrid Runbook Worker installation default to Windows. There are no Linux-specific examples or guidance for asset migration, and Linux users are implicitly expected to use PowerShell, which may not be native or preferred on Linux/macOS systems.
Recommendations
  • Provide equivalent Bash or Python scripts for asset migration, or clarify PowerShell Core (pwsh) compatibility for Linux/macOS users.
  • Add explicit instructions or examples for Linux/macOS users, including how to install and use PowerShell Core if required.
  • Ensure that links and tabs for Hybrid Runbook Worker installation are balanced, showing both Windows and Linux options equally.
  • Mention any limitations or requirements for Linux/macOS users when using PowerShell scripts, such as module compatibility or installation steps.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily focused on Windows PowerShell and related tools, with all examples and instructions given in PowerShell. There are no Bash, Python, or Linux/macOS shell examples, nor is there mention of cross-platform alternatives. Windows-specific terminology and tools (e.g., PSCredential, Windows PowerShell modules) are used throughout, and Linux/macOS users are not provided with equivalent guidance.
Recommendations
  • Add examples using Azure CLI and/or Python SDK for authentication and credential management, which are cross-platform.
  • Clarify which steps are PowerShell-specific and provide Linux/macOS alternatives where possible.
  • Mention that Azure Automation runbooks can use Python or other languages, and link to relevant documentation.
  • Provide guidance for Linux/macOS users on how to create and manage credential assets via the Azure portal or CLI.
  • Reorder sections to avoid always presenting Windows/PowerShell methods first.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation heavily emphasizes PowerShell and Windows-centric tools and patterns throughout, with nearly all code examples, parameter configuration, and usage scenarios presented in PowerShell or C#. There are no Linux/bash examples for starting runbooks or passing parameters, and PowerShell is consistently presented first and in greater detail. The only mention of Python runbooks is brief and lacks practical examples for Linux/macOS users. The guidance for calling runbooks from a local machine is exclusively PowerShell-based, with no mention of cross-platform alternatives.
Recommendations
  • Add examples for starting runbooks and passing parameters using Azure CLI (az), which is cross-platform and works on Linux/macOS.
  • Include bash shell examples for calling REST APIs to start runbooks and pass parameters, demonstrating usage from Linux/macOS environments.
  • Expand the Python runbook section with concrete examples for parameter handling and invocation from Linux/macOS.
  • Clarify which PowerShell instructions are compatible with PowerShell Core (pwsh) on Linux/macOS, and provide guidance for non-Windows users.
  • Consider reordering sections so that cross-platform tools (Azure CLI, REST API) are presented alongside or before Windows-specific tools.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows a moderate Windows bias. Windows/PowerShell tools and cmdlets are mentioned first or exclusively in several sections (e.g., DSC node removal, runbook export, DSC configuration export). Linux guidance is present for TLS configuration, but Linux alternatives for PowerShell cmdlets or asset export are missing or less detailed.
Recommendations
  • Provide Linux/CLI/REST API equivalents for PowerShell cmdlets where possible (e.g., for unregistering DSC nodes, exporting runbooks, and exporting DSC configurations).
  • When referencing PowerShell cmdlets, also mention if and how the same tasks can be performed using Azure CLI, Azure portal, or REST API, especially for Linux/macOS users.
  • In tables and step-by-step guides, present Linux and Windows options with equal prominence, not always listing Windows first.
  • Add explicit examples or links for Linux users where only Windows/PowerShell guidance is currently given.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides extensive PowerShell-based examples for configuring encryption of secure assets in Azure Automation, with REST API alternatives. There are no examples using Azure CLI, Bash, or cross-platform scripting tools. PowerShell is presented as the primary scripting interface, and Linux/macOS users are not shown equivalent workflows, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Where possible, provide Bash script snippets or guidance for Linux/macOS users.
  • Explicitly mention that PowerShell Core (pwsh) is cross-platform if PowerShell is required, and clarify if Windows PowerShell-specific modules are needed.
  • Reorder or parallelize examples so that REST API and CLI options are shown alongside PowerShell, not only after.
  • Add a note clarifying that all operations can be performed from any OS using REST API or Azure CLI, and link to relevant cross-platform tooling.
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-14 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, with no equivalent CLI, REST API, or Linux-native example. The State Configuration scenario references PowerShell DSC, which is cross-platform but is often perceived as Windows-centric. The documentation does mention Linux support in the context of Update Management and Log Analytics agents, but practical configuration steps and code samples are Windows/PowerShell-focused.
Recommendations
  • Add Azure CLI and/or REST API examples for setting 'publicNetworkAccess', alongside PowerShell.
  • Include explicit Linux/macOS command-line examples where relevant, especially for DNS configuration and agent setup.
  • Clarify that PowerShell DSC can be used on Linux, and provide links or brief instructions for Linux-based DSC agent installation.
  • Where screenshots or portal instructions are given, note any platform-specific differences (if any) for Linux/macOS users.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page heavily features PowerShell cmdlets and examples, with all certificate management tasks (creation, retrieval, deployment) demonstrated using PowerShell. There is no mention of Linux shell (bash) or cross-platform CLI equivalents for certificate management. PowerShell is presented as the primary and default method, with no Linux/macOS-specific guidance or parity for certificate operations outside of Python runbooks.
Recommendations
  • Add Azure CLI examples for certificate management tasks (creation, retrieval, removal) alongside PowerShell examples.
  • Explicitly state PowerShell Core (pwsh) compatibility and whether examples work on Linux/macOS, or provide Linux-specific instructions if needed.
  • Include bash or shell script examples for uploading and managing certificates, or clarify if PowerShell is required for all platforms.
  • Mention any limitations or requirements for Linux/macOS users, such as needing PowerShell Core or alternate tools.
  • Reorder sections so that cross-platform methods (Azure CLI, REST API) are presented before or alongside 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-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 page provides both Windows and Linux guidance for TLS upgrades, but Windows instructions are referenced first and in more detail (with links to registry settings and PowerShell cmdlets), while Linux guidance is limited to a Python script and OpenSSL references. Throughout the data retention and backup sections, Windows PowerShell cmdlets are used exclusively for examples and asset management, with no equivalent Linux CLI or scripting examples provided. This creates friction for Linux users, especially those managing Automation assets or DSC nodes, as they must infer or research Linux alternatives.
Recommendations
  • Provide Linux CLI or scripting examples (e.g., Azure CLI, Bash) alongside PowerShell cmdlets for asset management, runbook export/import, and DSC node operations.
  • Include links to Linux-specific documentation or tools where PowerShell cmdlets are referenced.
  • Ensure Linux guidance is given equal prominence and detail, not just as a secondary note or after Windows instructions.
  • Clarify when certain operations are Windows-only, and offer Linux alternatives when possible.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page heavily emphasizes PowerShell cmdlets and examples, with all certificate management operations (creation, retrieval, deployment) shown exclusively via PowerShell. There are no Linux/bash/CLI examples for certificate management, and PowerShell is presented first in most sections. While Python examples are provided for runbooks, all administrative tasks are PowerShell-centric, creating friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for certificate creation, retrieval, and management where possible.
  • Include bash or shell script snippets for uploading certificates, especially for users on Linux/macOS.
  • Clarify if PowerShell examples are cross-platform (PowerShell Core), or provide guidance for Linux/macOS users.
  • Present examples in a more balanced order (e.g., CLI, PowerShell, Python) rather than always PowerShell first.
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-13 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 tools and patterns. All code examples, parameter handling, and workflow descriptions are based on PowerShell, PowerShell Workflow, and graphical runbooks (which are PowerShell-based). There is minimal coverage for Python runbooks, and no examples or guidance are provided for Linux/macOS users on how to interact with Azure Automation runbooks outside of PowerShell. The SDK and REST API sections are platform-neutral, but the practical examples and instructions are overwhelmingly Windows/PowerShell-oriented.
Recommendations
  • Provide CLI (az) examples for starting runbooks and passing parameters, which are cross-platform.
  • Add explicit guidance and examples for Linux/macOS users, such as using Bash scripts or Python to call the REST API or SDK.
  • Expand the Python runbook section with parameter passing examples and clarify how Linux users can invoke runbooks.
  • Mention that PowerShell Core (pwsh) is available on Linux/macOS and provide examples using it, or clarify any limitations.
  • Balance the order of examples so that platform-neutral methods (REST API, SDK, CLI) are presented before or alongside PowerShell.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for disaster recovery in Azure Automation is heavily focused on PowerShell scripts and workflows for asset migration, with no equivalent examples or guidance for Linux-native tools or scripting languages (such as Bash or Python). All migration instructions and runbook examples are PowerShell-based, and references to gallery scripts are exclusively for PowerShell. While the page states applicability to both Linux and Windows VMs, Linux users are left without platform-native guidance or parity in scripting options.
Recommendations
  • Provide Bash or Python script examples for asset migration, or clarify if PowerShell Core (cross-platform) is required and supported for Linux users.
  • Explicitly mention whether PowerShell Core can be used on Linux for these migration tasks, and provide installation instructions if so.
  • Add guidance or links for Linux users to install and use PowerShell Core, or offer alternative migration approaches using Azure CLI or REST API.
  • Include notes or examples for running migration scripts on Linux Hybrid Runbook Workers, not just Windows.
  • Clarify any limitations or requirements for Linux users in the prerequisites section.
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-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 code examples and module references are for PowerShell, with no mention of Bash, Azure CLI, or cross-platform scripting. The process for creating credential assets and managing Azure resources is only shown using PowerShell cmdlets, and the 'Windows PowerShell' terminology is used explicitly. Linux/macOS users are not provided with equivalent instructions or examples.
Recommendations
  • Add Azure CLI examples for credential asset creation and authentication flows where possible.
  • Clarify which steps are PowerShell-specific and provide Bash or cross-platform alternatives if supported.
  • Use 'PowerShell' (which is cross-platform) instead of 'Windows PowerShell' unless referring to Windows-only modules.
  • Explicitly mention platform compatibility for each approach, and link to Linux/macOS guidance where relevant.
  • Provide a note if certain features are only available via PowerShell, and suggest alternatives for Linux/macOS users.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-13 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 tools and patterns. All CLI examples are provided in PowerShell, with explicit references to Windows PowerShell and PSCredential objects. There are no examples or guidance for Linux/macOS shell environments (e.g., Bash, CLI), nor is there mention of cross-platform alternatives for credential management outside of Python runbooks. The PowerShell/Windows approach is presented first and in greater detail than Python, and no parity is offered for Linux-native scripting or automation tools.
Recommendations
  • Add Azure CLI examples for credential management tasks, where supported.
  • Clarify whether PowerShell examples work cross-platform (PowerShell Core on Linux/macOS) or are Windows-only.
  • Explicitly mention any limitations or alternatives for Linux/macOS users, especially for runbook authoring and credential retrieval.
  • Provide Bash or other shell script examples if possible, or state that only PowerShell and Python are supported for these operations.
  • Reorder or balance example sections so Python and PowerShell are presented with equal prominence.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-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 for disaster recovery in Azure Automation is heavily focused on PowerShell scripts and workflows for asset migration, with no mention of Linux-native scripting tools (such as Bash or Python) or cross-platform alternatives. All migration examples and instructions are PowerShell-based, and there are no Linux-specific examples or guidance for users who may prefer or require non-Windows tooling. While the page states applicability to both Linux and Windows VMs, the practical guidance is Windows-centric.
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.
  • Explicitly mention and provide examples for executing migration scripts from Linux/macOS environments, including any prerequisites or limitations.
  • Add guidance for Linux users on installing required PowerShell modules and executing runbooks from Linux-based Automation accounts.
  • Where possible, highlight cross-platform compatibility of PowerShell scripts (e.g., PowerShell Core) and note any Windows-specific limitations.
  • Consider including links or references to Linux-native tools or Azure CLI alternatives if available.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-12 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 operations reference Windows PowerShell cmdlets without equivalent Linux CLI or scripting examples. The Linux example for TLS upgrade is present, but other sections (e.g., asset export, DSC node removal) only mention Windows tools.
Recommendations
  • Provide Azure CLI or Bash examples alongside PowerShell cmdlets for backup and retention operations.
  • Include Linux-specific instructions for exporting runbooks, DSC configurations, and managing assets.
  • Ensure tables and lists mention Linux options with equal prominence to Windows.
  • Where PowerShell is referenced, clarify if cross-platform PowerShell (pwsh) can be used, or provide alternatives.
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-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-specific tools and patterns, with all code examples and module references using PowerShell. There are no examples or guidance for Linux/macOS users (e.g., using Azure CLI, Bash, or cross-platform scripting). The term 'Windows PowerShell' is used, and no mention is made of alternatives for non-Windows environments, despite Azure Automation supporting Python runbooks and cross-platform modules.
Recommendations
  • Add equivalent examples using Azure CLI and/or Python runbooks, which are supported in Azure Automation and are cross-platform.
  • Clarify when 'PowerShell' refers to cross-platform PowerShell Core vs. Windows PowerShell, and provide guidance for non-Windows users.
  • Mention that Azure Automation supports Python runbooks and link to relevant documentation.
  • Where possible, provide Bash/Azure CLI snippets for credential management and authentication.
  • Avoid using 'Windows PowerShell' unless the feature is truly Windows-only; otherwise, use 'PowerShell' to indicate cross-platform compatibility.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-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 heavily emphasizes PowerShell cmdlets and examples, with all CLI instructions and code samples provided only for PowerShell. There are no Linux shell (bash) or cross-platform CLI examples for certificate management, and PowerShell is presented first and most extensively. While Python examples are included, they are specific to Azure Automation runbooks and do not address certificate management from Linux/macOS environments outside of runbooks.
Recommendations
  • Add Azure CLI or Bash examples for certificate management tasks, such as uploading, retrieving, and deleting certificates.
  • Clarify whether PowerShell cmdlets can be used cross-platform (PowerShell Core on Linux/macOS), and provide guidance for Linux/macOS users.
  • Mention any limitations or alternative approaches for Linux/macOS users who may not have access to Windows PowerShell.
  • Ensure parity in example ordering by presenting cross-platform options before or alongside PowerShell.
  • Document certificate requirements (such as provider) in a way that is agnostic to OS-specific tooling.
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-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 heavily emphasizes PowerShell and Windows-centric tools and patterns, with most examples, screenshots, and workflows centered around PowerShell, PowerShell Workflow, and graphical runbooks (which are PowerShell-based). Linux/macOS users are not provided with equivalent CLI or shell examples, and PowerShell is assumed as the primary interface for parameter passing and runbook invocation. Python runbooks are mentioned, but only briefly, and no Linux-native shell (bash) or cross-platform CLI examples are provided for starting runbooks or passing parameters.
Recommendations
  • Add Azure CLI examples for starting runbooks and passing parameters, which are cross-platform and commonly used on Linux/macOS.
  • Include bash shell examples for invoking REST API endpoints, demonstrating how Linux users can start runbooks and pass parameters.
  • Clarify that PowerShell Core (pwsh) is cross-platform, and provide explicit instructions/examples for Linux/macOS users where relevant.
  • Expand the Python runbook section with more detailed examples, including parameter passing from Linux/macOS environments.
  • Where screenshots or UI instructions are given, note any platform differences or limitations.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-12 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 and Windows-centric tooling, with all CLI examples using PowerShell cmdlets and references to Windows PowerShell. The creation and management of credentials are described exclusively with PowerShell commands, and Windows terminology (e.g., PSCredential) is used throughout. Python examples are provided, but there are no Bash, Linux CLI, or cross-platform shell examples. The documentation does not mention or demonstrate how Linux/macOS users can interact with credential assets outside of Python runbooks.
Recommendations
  • Add examples using Azure CLI (az) for credential management, if supported.
  • Clarify whether PowerShell examples work on PowerShell Core (pwsh) on Linux/macOS, and provide guidance for non-Windows environments.
  • Explicitly state platform requirements for PowerShell cmdlets and modules (e.g., Az modules, Orchestrator.AssetManagement.Cmdlets).
  • Include a section or note for Linux/macOS users on how to manage credentials, or acknowledge any limitations.
  • If credential management is only possible via PowerShell, make this clear and suggest alternatives for Linux/macOS users (such as using the Azure portal or Python runbooks).
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Windows and Linux guidance for TLS configuration, but consistently lists Windows registry/PowerShell tools and examples first, and provides more detailed instructions for Windows (including multiple links to Windows registry settings and PowerShell cmdlets). Linux instructions are present but less detailed and sometimes only reference external sources. Several backup and data management examples reference only PowerShell cmdlets, with no equivalent CLI or scripting guidance for Linux/macOS users.
Recommendations
  • Provide Azure CLI or Bash examples alongside PowerShell cmdlets for tasks like exporting runbooks and DSC configurations.
  • When referencing platform-specific guidance, list Linux and Windows equally (or alternate order) and provide parity in detail.
  • For asset backup and retrieval, include Linux/macOS-compatible methods or explicitly state if only PowerShell is supported.
  • Where possible, link to cross-platform documentation (e.g., Azure CLI docs) in addition to Windows-specific registry or PowerShell pages.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for disaster recovery in Azure Automation provides only PowerShell-based scripts and workflows for asset migration, with no equivalent examples or guidance for Linux-native tools or Bash scripting. All migration instructions rely on PowerShell, which is traditionally a Windows-centric tool, although PowerShell Core is cross-platform. There are no Bash, CLI, or Python examples, and the documentation repeatedly references Windows patterns and tools first or exclusively.
Recommendations
  • Add Bash or Azure CLI examples for asset migration, or clarify if PowerShell Core is required and supported on Linux/macOS.
  • Explicitly mention cross-platform support for PowerShell scripts and provide installation guidance for Linux/macOS users.
  • Include alternative migration approaches using Python or REST API for users who do not wish to use PowerShell.
  • Balance the documentation by showing Linux/macOS workflows alongside Windows/PowerShell ones, especially in critical migration sections.
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-10 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 usage for Azure Automation authentication with Microsoft Entra ID. All code examples, module references, and credential management instructions are PowerShell-centric, with no mention of Bash, CLI, or Linux/macOS alternatives. Windows-specific tools and patterns (e.g., PSCredential, Get-AutomationPSCredential, New-AzAutomationCredential) are referenced exclusively, and Linux users are not provided with equivalent guidance.
Recommendations
  • Add Azure CLI examples for credential asset creation and authentication, highlighting cross-platform compatibility.
  • Clarify which steps are PowerShell-specific and provide Bash or Azure CLI alternatives where possible.
  • Mention that Azure Automation runbooks can be authored in Python and provide a Python example for credential retrieval and Azure authentication.
  • Explicitly state PowerShell requirements and link to cross-platform PowerShell installation instructions.
  • If certain features are Windows-only, clearly indicate this to set expectations for Linux/macOS users.
GitHub Create Pull Request
← Previous Page 29 of 40 Next →