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 601-625 of 982 flagged pages
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/runbook-input-parameters.md ...b/main/articles/automation/runbook-input-parameters.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. Nearly all code examples, parameter definitions, and workflows are presented using PowerShell or PowerShell Workflow, which are Windows-centric technologies. The only mention of Python runbooks is brief and lacks concrete examples, and there are no examples or guidance for Linux shell scripting or CLI-based automation. The documentation assumes the use of Windows tools and patterns (e.g., PowerShell cmdlets, .NET types), and Linux/Unix equivalents are not discussed or demonstrated. Even SDK and REST API examples are shown in C# (another Windows-centric language), and all automation scenarios are illustrated using Windows tools and conventions.
Recommendations
  • Provide equivalent examples for Linux/Unix environments, such as using Bash scripts or Azure CLI to start and manage runbooks.
  • Expand the Python runbook section with concrete parameter handling examples, including how to pass parameters from Linux environments.
  • Include examples of starting runbooks using Azure CLI (az automation runbook start) and show how to pass parameters from the command line.
  • Discuss differences and considerations for users running automation from Linux/macOS, such as authentication and file path handling.
  • Balance SDK examples by including Python or JavaScript code snippets, not just C#.
  • Clarify which features or patterns are Windows/PowerShell-specific and provide Linux-friendly alternatives where possible.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/start-runbooks.md ...e-docs/blob/main/articles/automation/start-runbooks.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a clear Windows bias. All command-line examples use Windows PowerShell, and there are no examples for Linux users (e.g., Azure CLI, Bash, or cross-platform PowerShell Core). The term 'Windows PowerShell' is used explicitly, and the documentation does not mention or provide parity for Linux tools or workflows. The order of presentation also places Windows/PowerShell methods before more cross-platform or API-based approaches.
Recommendations
  • Add equivalent Azure CLI examples for starting and managing runbooks, as Azure CLI is cross-platform and widely used on Linux.
  • Clarify when 'PowerShell' refers to Windows PowerShell versus cross-platform PowerShell Core, and provide examples that work on both.
  • Include Bash/cURL examples for API-based methods to demonstrate Linux-friendly workflows.
  • Reorder the methods table or present cross-platform options (like Azure CLI and REST API) before or alongside Windows-specific tools.
  • Explicitly mention Linux/macOS compatibility and provide guidance for non-Windows environments.
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-26 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 examples for configuring encryption of secure assets in Azure Automation, with no equivalent CLI or Linux/macOS shell examples. PowerShell is presented as the primary scripting method, and REST API examples are given as alternatives, but Azure CLI or bash examples are missing. The PowerShell module is referenced as a prerequisite, and PowerShell commands are used in all procedural sections before REST API alternatives. This creates friction for Linux/macOS users who may prefer Azure CLI or bash scripting.
Recommendations
  • Add Azure CLI examples for all procedural steps, including assigning managed identities, configuring Key Vault access policies, and reconfiguring Automation accounts.
  • Include bash scripting samples where relevant, especially for users on Linux/macOS.
  • Mention that PowerShell examples can be run cross-platform with PowerShell Core, but also clarify CLI alternatives.
  • List Azure CLI as a prerequisite alongside PowerShell.
  • Ensure that REST API and CLI examples are given equal prominence to 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-26 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 throughout. Many backup and retention examples reference Windows PowerShell cmdlets, with no equivalent Linux CLI or scripting examples. Windows registry settings and tools are linked, while Linux guidance is more generic (OpenSSL changelog, Python script).
Recommendations
  • Add Azure CLI or Bash examples alongside PowerShell cmdlets for backup and retention tasks.
  • Provide explicit Linux/macOS instructions for exporting runbooks, DSC configurations, and managing assets, not just referencing PowerShell.
  • Ensure Linux guidance is as detailed as Windows guidance (e.g., specific commands/scripts for asset management, not just generic references).
  • Where possible, mention Linux tools (such as az CLI, shell scripts) before or alongside Windows tools.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation heavily relies on PowerShell scripts and workflows for disaster recovery tasks, with no equivalent examples or guidance for Linux-native tools (such as Bash or Python). All migration scripts and runbook examples are PowerShell-based, and the instructions for Hybrid Runbook Worker installation link to Windows-focused tabs first. This creates friction for Linux users, especially those who prefer or require Bash or Python for automation.
Recommendations
  • Provide Bash or Python script examples for migrating Automation account assets, or clarify if PowerShell Core (pwsh) is fully supported cross-platform.
  • Explicitly mention PowerShell Core compatibility for Linux/macOS users, and provide instructions for installing and running PowerShell scripts on Linux.
  • Add Linux/macOS-specific guidance for Hybrid Runbook Worker installation, ensuring links and instructions are not Windows-first.
  • Include notes or alternative steps for users who do not have access to PowerShell or prefer other scripting 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-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively uses Windows PowerShell and PowerShell-based examples for authenticating to Azure via Microsoft Entra ID in Azure Automation. All code samples, module references, and credential handling instructions are PowerShell-centric, with no mention of Bash, CLI, or Linux/macOS alternatives. The page refers to 'Windows PowerShell' and does not clarify cross-platform support for PowerShell Core or Azure CLI, potentially creating friction for Linux/macOS users.
Recommendations
  • Clarify whether PowerShell Core (pwsh) is supported for these tasks and provide examples if so.
  • Add Azure CLI examples for credential asset creation and authentication, where possible.
  • Explicitly state platform requirements and limitations (e.g., if only Windows PowerShell is supported, mention it up front).
  • Provide guidance for Linux/macOS users on how to use Azure Automation and Microsoft Entra ID authentication, including any necessary prerequisites or workarounds.
  • Mention whether the Az module and related cmdlets are available and supported on Linux/macOS runbooks.
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-26 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 workflows, with all code examples, parameter handling, and runbook invocation methods centered around PowerShell cmdlets and Windows tools. There are no Linux shell (bash) or cross-platform CLI examples for starting runbooks or passing parameters, and PowerShell is presented as the default or primary method throughout. Python runbooks are briefly mentioned, but only in the context of parameter handling, not invocation. The SDK and REST API sections are platform-neutral, but the practical invocation guidance is Windows-first and lacks Linux parity.
Recommendations
  • Add Azure CLI (az automation runbook start) examples for starting runbooks and passing parameters, including JSON parameter handling.
  • Include bash shell examples for invoking runbooks via REST API (using curl) and passing parameters.
  • Clarify that PowerShell examples are cross-platform when applicable (e.g., PowerShell Core/7), and note any Windows-specific limitations.
  • Provide guidance for Linux/macOS users on installing and using PowerShell Core, or alternatives via Azure CLI.
  • Expand Python runbook section to include invocation examples from Linux/macOS environments.
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-26 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 presented as the primary scripting method, which may create friction for non-Windows users. However, the overall content is largely platform-neutral, and Linux is mentioned in the context of Hybrid Runbook Workers and Update Management.
Recommendations
  • Add Azure CLI and/or ARM template examples for configuring 'publicNetworkAccess' to complement the PowerShell script.
  • Explicitly mention that the PowerShell example is for Windows users, and provide guidance for Linux/macOS users.
  • Where possible, provide cross-platform scripting options (e.g., Bash, Azure CLI) alongside PowerShell.
  • Ensure screenshots and portal instructions are not Windows-centric (they appear neutral here).
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-26 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 cmdlets and Windows-centric patterns for managing credentials in Azure Automation. All CLI examples are in PowerShell, with no Bash, Linux shell, or cross-platform CLI equivalents. The 'Create a new credential asset' section only provides a Windows PowerShell example, and the cmdlet tables exclusively reference PowerShell tools. While Python runbook examples are included, there are no Linux-native or cross-platform CLI instructions for credential asset management outside of the Azure portal.
Recommendations
  • Add Azure CLI examples for creating, retrieving, and managing credential assets, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Clarify whether credential asset management is possible via REST API or Azure CLI, and provide those examples if available.
  • Explicitly state if PowerShell is required for certain operations, and note any limitations for Linux/macOS users.
  • Include guidance for Linux/macOS users on installing and using PowerShell Core if PowerShell is required.
  • Consider providing Bash or shell script equivalents where possible, or at least link to cross-platform alternatives.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-26 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 certificate management patterns, with all scripting examples and advanced workflows provided in PowerShell. There are no explicit Linux/macOS shell (bash, CLI) examples, and PowerShell is consistently presented first. While Python examples are included, they are limited to runbook usage and do not cover certificate creation or management outside the Azure portal/PowerShell context. There is no mention of Linux tools or cross-platform CLI equivalents for certificate management.
Recommendations
  • Add Azure CLI examples for certificate management tasks (creation, retrieval, deletion) to provide parity for Linux/macOS users.
  • Include bash or shell script snippets for uploading and managing certificates where possible.
  • Present cross-platform options (Azure CLI, REST API) before or alongside PowerShell examples.
  • Clarify which tasks require PowerShell and which can be accomplished with other tools.
  • Add a section discussing certificate requirements and handling on Linux/macOS environments, including any limitations or differences.
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-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 Windows PowerShell, with all examples and instructions using PowerShell cmdlets and Windows-specific modules. There are no examples or guidance for Linux/macOS users, such as using Bash, Azure CLI, or cross-platform scripting. The use of Windows PowerShell terminology and tools is pervasive, and Linux alternatives are not mentioned.
Recommendations
  • Add equivalent Azure CLI examples for credential asset creation and authentication, which work cross-platform.
  • Clarify that Azure Automation runbooks can be authored in Python and provide a Python example for managing Azure resources.
  • Mention that PowerShell Core (pwsh) is available on Linux/macOS and indicate whether the provided scripts are compatible with PowerShell Core.
  • Include guidance for Linux/macOS users on how to install required modules and authenticate to Azure from their platforms.
  • Reorder sections to present cross-platform options (Azure CLI, Python) before Windows PowerShell-specific instructions.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-25 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 scripting and automation instructions provided in PowerShell. There are no Linux shell (bash) or cross-platform CLI examples for certificate management, and PowerShell is presented first and most thoroughly. The Python section is present, but only for runbook scripting, not for certificate management tasks like creation or upload. There is no mention of Linux tools or Azure CLI equivalents for certificate operations.
Recommendations
  • Add Azure CLI examples for certificate creation, upload, and management, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include bash shell scripting examples for certificate manipulation where relevant.
  • Clarify whether PowerShell Core (pwsh) is supported for these operations, and provide guidance for non-Windows environments.
  • Mention any limitations or alternatives for Linux/macOS users if PowerShell is required.
  • Consider referencing third-party tools or scripts for certificate handling on Linux/macOS.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page for Azure Automation disaster recovery is notably PowerShell-centric, with all migration scripts and runbook examples provided exclusively in PowerShell and PowerShell Workflow. There are no Linux shell (bash) or cross-platform scripting examples, nor are alternatives like Azure CLI or REST API mentioned for asset migration. Windows terminology and links (e.g., 'tabs=windows') appear first or exclusively in Hybrid Runbook Worker instructions, even though Linux is supported. This creates friction for Linux/macOS users, especially those who prefer bash or cross-platform tools.
Recommendations
  • Provide equivalent migration scripts or instructions using Azure CLI and/or bash for asset migration between Automation accounts.
  • Mention and link to cross-platform tools or REST API options for Automation asset management.
  • When referencing Hybrid Runbook Worker installation, ensure both Windows and Linux tabs/examples are equally visible and linked.
  • Clarify that PowerShell scripts can be executed from Linux/macOS environments using PowerShell Core, or provide guidance for those platforms.
  • Consider including Python runbook migration options, since Python is supported in Azure Automation.
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-25 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 presented as the primary scripting method, and Windows terminology (such as host file usage and PowerShell DSC) is referenced before Linux alternatives. However, the overall guidance is mostly platform-neutral, and Linux is acknowledged in the context of Hybrid Runbook Workers and Update Management.
Recommendations
  • Add Azure CLI and/or ARM template examples for configuring 'publicNetworkAccess' property, alongside the PowerShell example.
  • Explicitly mention that the steps can be performed from any OS using Azure CLI or portal.
  • Where PowerShell DSC is referenced, clarify Linux equivalents or alternatives (such as using Python or Bash for runbooks).
  • Ensure that host file and DNS configuration instructions include Linux/macOS syntax and paths (e.g., /etc/hosts).
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-25 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 cmdlets and Windows PowerShell examples for managing credentials in Azure Automation. While Python examples are provided, there are no examples or guidance for Linux/macOS users who may want to use Bash, CLI, or other non-Windows tools. The PowerShell-centric approach may create friction for Linux/macOS users, especially since credential management is presented almost exclusively in the context of PowerShell and Windows.
Recommendations
  • Add Azure CLI examples for credential asset management, where possible, to support Linux/macOS users.
  • Clarify whether PowerShell Core (pwsh) on Linux/macOS is supported for these cmdlets, and provide examples if so.
  • Explicitly mention any limitations or alternatives for Linux/macOS users in sections that reference Windows PowerShell.
  • Provide guidance or links for managing credentials via REST API or SDKs for cross-platform scenarios.
  • Ensure that the 'Create a new credential asset' section includes steps for users on Linux/macOS, or at least clarifies platform requirements.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-25 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 are mentioned first and more prominently, with explicit links to Windows registry settings and PowerShell cmdlets. Several sections (data retention, backup) reference Windows PowerShell cmdlets without Linux CLI or scripting equivalents, and Windows-specific tools (PowerShell) are used for examples. Linux guidance is present but less detailed and less prominent.
Recommendations
  • Provide Linux CLI or scripting equivalents for PowerShell cmdlets (e.g., az CLI, Bash, Python) when discussing data retention and backup.
  • Ensure Linux examples are given equal prominence and detail as Windows examples, including links to relevant Linux documentation.
  • Consider presenting platform-neutral guidance first, or alternate Windows and Linux examples to avoid 'windows_first' bias.
  • Where PowerShell is referenced, clarify if az CLI or REST API alternatives exist for Linux/macOS users.
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-25 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 examples for configuring secure asset encryption in Azure Automation, with REST API alternatives. However, it lacks examples or guidance for Linux/macOS users, such as Azure CLI or Bash scripting. PowerShell is presented as the primary method, and Linux-friendly tools are only mentioned briefly (in the context of revoking access), creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for all major tasks (assigning managed identities, configuring Key Vault access policies, switching to customer-managed keys, etc.) alongside PowerShell examples.
  • Explicitly mention that PowerShell Core (pwsh) is cross-platform and provide guidance for Linux/macOS users where applicable.
  • Where REST API calls are shown, provide sample Bash/cURL commands to demonstrate usage from Linux/macOS environments.
  • Ensure that references to PowerShell modules clarify their compatibility with PowerShell Core and non-Windows platforms.
  • Consider showing CLI or REST examples before PowerShell, or at least in parallel, to reduce Windows-first bias.
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-25 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-based runbooks, with examples, screenshots, and parameter handling almost exclusively shown via PowerShell and PowerShell Workflow. PowerShell cmdlets and Windows-centric patterns (e.g., PowerShell hashtables, .NET types) are presented first and in detail, while Python runbooks (the main cross-platform alternative) receive minimal coverage and lack practical examples. There are no Linux/macOS-specific instructions or CLI examples for starting runbooks or passing parameters, and the REST API section does not clarify cross-platform usage.
Recommendations
  • Add detailed examples for Python runbooks, including parameter handling and starting runbooks from Linux/macOS environments.
  • Provide Azure CLI examples for starting runbooks and passing parameters, as CLI is cross-platform.
  • Clarify that PowerShell examples can be run on PowerShell Core (pwsh) on Linux/macOS, and provide any necessary caveats.
  • Include guidance for Linux/macOS users on prerequisites and environment setup for Azure Automation.
  • Expand REST API examples to show how to invoke from Linux/macOS (e.g., using curl or HTTPie).
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-25 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 nearly all examples, tools, and instructions referencing PowerShell, Windows PowerShell versions, and Windows-specific cmdlets. Internal cmdlets and modules are explicitly unavailable on Linux Hybrid Runbook Workers, but Linux support is only briefly mentioned. There are no Linux/bash examples, and Linux module management is not covered. Python module support is referenced, but only as a link to another page.
Recommendations
  • Add explicit guidance and examples for Linux Hybrid Runbook Workers, including module management and limitations.
  • Include bash or Python examples for relevant tasks, especially for module import and management.
  • Clarify which features are Windows-only and provide Linux alternatives or workarounds where possible.
  • Expand documentation on Python modules and their management within Azure Automation, including parity with PowerShell module workflows.
  • Add a comparison table or section summarizing feature parity and limitations between Windows and Linux Hybrid Runbook Workers.
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-23 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, with all code examples and module references using PowerShell. There are no examples or guidance for Linux/macOS users, such as using Bash, Azure CLI, or cross-platform scripting. Windows terminology and tools are mentioned exclusively and before any Linux alternatives, which are absent.
Recommendations
  • Add equivalent Azure CLI examples for credential asset creation and runbook authentication.
  • Clarify which steps are platform-agnostic and which require Windows-specific tooling.
  • Provide guidance for Linux/macOS users on how to authenticate to Azure Automation using Microsoft Entra ID, including references to Bash or Python SDKs where possible.
  • Mention cross-platform PowerShell Core (pwsh) compatibility and any limitations.
  • Include a note on how Linux users can use Azure Automation, and link to relevant documentation.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows/PowerShell tools and cmdlets are mentioned first or exclusively in several sections (e.g., retention and backup), while Linux equivalents are missing or less detailed. Linux is acknowledged in the TLS upgrade section, but PowerShell is the only scripting example for backup/export tasks, and references to Linux tools for managing Automation assets are lacking.
Recommendations
  • Provide Linux/CLI/REST API examples alongside PowerShell cmdlets for tasks like exporting runbooks, DSC configurations, and managing assets.
  • Include references to Azure CLI and/or az automation commands where possible, not just PowerShell.
  • In tables and instructions, present Linux and Windows guidance with equal prominence, or group by platform rather than listing Windows first.
  • For asset backup/recovery, clarify options for Linux/macOS users, including any limitations or alternative workflows.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-23 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 disaster recovery operations, with no equivalent examples or guidance for Linux-native tools (such as Bash, CLI, or Python). All migration scripts and runbook examples are PowerShell-based, and there is no mention of alternatives for Linux users. While the page claims applicability to both Linux and Windows VMs, the practical guidance is Windows-centric.
Recommendations
  • Provide Bash or Azure CLI script examples for migrating Automation account assets.
  • Include guidance for using Python runbooks or scripts, which are supported in Azure Automation and more common in Linux environments.
  • Explicitly mention any limitations or workarounds for Linux users, such as how to execute PowerShell scripts from Linux (using PowerShell Core), or alternative approaches.
  • Add parity in runbook import instructions for Python or Bash runbooks, if supported.
  • Clarify if PowerShell Core (cross-platform) is supported for these scripts, and provide instructions for Linux/macOS users.
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-23 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 a Linux/macOS equivalent (such as Azure CLI or REST API). Additionally, PowerShell is presented as the primary scripting method, which may create friction for Linux/macOS users. However, the overall guidance is platform-neutral, and most steps are performed in the Azure Portal, which is accessible from any OS.
Recommendations
  • Add Azure CLI and/or REST API examples for configuring 'publicNetworkAccess', alongside the PowerShell script.
  • Explicitly mention that the Azure Portal steps are OS-agnostic.
  • Where PowerShell is used, clarify if it can be run cross-platform (e.g., PowerShell Core), or provide alternative commands for Bash/CLI users.
  • Ensure any references to agents/tools (e.g., Log Analytics agent) include both Windows and Linux instructions or links.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-23 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) shown exclusively via PowerShell. There are no Linux/bash/CLI examples for certificate management, and PowerShell is presented first and most extensively. While Python examples are provided for runbook usage, all administrative tasks are PowerShell-centric, creating friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for certificate management tasks (creation, retrieval, removal, etc.) alongside PowerShell examples.
  • Include bash or shell script snippets for common certificate operations, especially for uploading and managing certificates.
  • Clarify whether PowerShell cmdlets can be used cross-platform (PowerShell Core), and provide guidance for Linux/macOS users if so.
  • Present examples in a more balanced order (e.g., CLI, PowerShell, Python) or clearly indicate platform requirements for each method.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation heavily emphasizes PowerShell cmdlets and Windows-centric patterns for managing credentials in Azure Automation. All CLI examples are PowerShell-based, with no equivalent Bash, Azure CLI, or Linux-native scripting examples. The 'Create a new credential asset' section only offers Windows PowerShell guidance, and PowerShell cmdlets are described before Python functions. There is no mention of Linux/macOS shell alternatives or cross-platform CLI usage.
Recommendations
  • Add Azure CLI examples for credential asset management, where possible.
  • Clarify whether credential management is possible from Linux/macOS and provide guidance or limitations.
  • Include Bash or shell scripting examples for relevant operations.
  • Explicitly state if PowerShell is required for certain tasks, and provide cross-platform PowerShell Core guidance if applicable.
  • Reorder sections or add parity so that Python and cross-platform options are presented alongside PowerShell.
  • Mention any limitations or workarounds for Linux/macOS users.
GitHub Create Pull Request
← Previous Page 25 of 40 Next →