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 751-775 of 982 flagged pages
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-04 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 are in PowerShell, and references are made to 'Windows PowerShell' and Windows-specific modules. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform scripting approaches. The documentation assumes the use of PowerShell, which, while available cross-platform, is still more familiar to Windows users. The term 'Windows PowerShell' is used, and no parity is provided for non-Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI and/or Bash for Linux/macOS users, especially for credential asset creation and runbook management.
  • Clarify that PowerShell Core (pwsh) is cross-platform and supported, and update terminology to avoid 'Windows PowerShell' unless specifically required.
  • Provide guidance or links for installing and using PowerShell on Linux/macOS if PowerShell is required.
  • Mention and, where possible, provide examples for using REST APIs or SDKs (e.g., Python, .NET) for automation tasks.
  • Explicitly state if certain features are only available via PowerShell or Windows, and offer alternatives if available.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for managing certificates in Azure Automation is heavily focused on PowerShell-based workflows and cmdlets, which are most commonly used on Windows. All detailed examples for certificate creation and management use PowerShell, with no equivalent CLI, Bash, or Linux-native instructions. The Python section provides parity for retrieving certificates in runbooks, but creation and management are exclusively shown with PowerShell. The portal instructions also recommend PowerShell as a workaround for CSP accounts, again prioritizing Windows tooling.
Recommendations
  • Add Azure CLI examples for certificate creation, management, and retrieval, as Azure CLI is cross-platform.
  • Include Bash or shell script snippets for common certificate operations, especially for uploading and managing certificates.
  • Explicitly note any limitations or differences for Linux/macOS users in Azure Automation, and provide guidance for those platforms.
  • Reorder or balance examples so that PowerShell and cross-platform methods (CLI, Python) are presented equally, or at least clarify that PowerShell is not required on non-Windows systems.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Windows and Linux guidance for TLS configuration, but Windows/PowerShell tools and examples are mentioned first and more frequently throughout the page. Several backup and data management tasks reference only PowerShell cmdlets, with no equivalent CLI or Linux-native examples provided. Linux guidance is present for TLS but is less detailed elsewhere.
Recommendations
  • For every PowerShell cmdlet example (e.g., Unregister-AzAutomationDscNode, Get-AzAutomationRunbookContent, Export-AzAutomationDscConfiguration), provide equivalent Azure CLI or REST API examples that work cross-platform.
  • When listing platform-specific instructions or tables, alternate the order or present Linux and Windows guidance in parallel to avoid a 'Windows-first' impression.
  • Expand Linux guidance beyond TLS—for example, explain how to unregister DSC nodes, export runbooks, or manage assets using cross-platform tools.
  • Where only PowerShell is supported, explicitly state this and, if possible, link to feature requests or workarounds for Linux/macOS users.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for configuring runbook input parameters in Azure Automation exhibits a notable Windows/PowerShell bias. Most examples, code snippets, and workflows are based on PowerShell, PowerShell Workflow, or graphical runbooks (which are PowerShell-based). The only Linux-relevant section is for Python runbooks, which is brief and lacks parity in depth and example coverage compared to PowerShell. All command-line examples for starting runbooks use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux-native tooling. The JSON passing example is exclusively PowerShell-based, and SDK examples use C#, which is more common in Windows environments. There is no guidance for Linux/macOS users on how to interact with runbooks using Azure CLI or Bash scripts.
Recommendations
  • Add equivalent Azure CLI examples for starting runbooks and passing parameters, including JSON objects.
  • Provide Bash script examples for interacting with the Azure Automation REST API.
  • Expand the Python runbook section with more detailed parameter handling examples, including complex types and best practices.
  • Clarify which features or examples are platform-agnostic and which are PowerShell/Windows-specific.
  • Include notes or links for Linux/macOS users on how to install and use Azure CLI and Python for Azure Automation tasks.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-03 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 tools and patterns. All CLI examples are in PowerShell, and cmdlet usage is described exclusively in terms of PowerShell modules and objects (e.g., PSCredential). The only non-PowerShell examples are for Python runbooks, but there are no Bash, Azure CLI, or cross-platform shell examples. The section on creating credentials via CLI only covers Windows PowerShell, and PowerShell terminology is used throughout, even when discussing general credential management.
Recommendations
  • Add Azure CLI examples for credential management tasks (creation, retrieval, deletion) where possible.
  • Clarify if credential management via CLI is only possible with PowerShell, or document Linux/macOS-compatible alternatives.
  • If PowerShell Core (pwsh) is supported on Linux/macOS, explicitly mention this and provide examples.
  • Reorganize sections so that cross-platform or portal-based methods are presented before Windows-specific PowerShell methods.
  • Explicitly state any limitations for non-Windows users and provide guidance or workarounds.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation for disaster recovery in Azure Automation is heavily focused on PowerShell scripts and workflows, with no mention or examples of Bash, Python, or other Linux-native scripting options. All migration instructions and runbook examples are provided using PowerShell, and tabs for script installation reference Windows first. While the documentation states applicability to both Linux and Windows VMs, Linux users may find it difficult to follow or replicate the migration process without PowerShell or Windows environments.
Recommendations
  • Provide equivalent migration scripts or runbook examples using Bash or Python, which can run natively on Linux.
  • Clarify if PowerShell Core (pwsh) is supported and provide instructions for Linux/macOS environments.
  • Include explicit steps or notes for Linux users on how to execute migration tasks without requiring Windows or PowerShell Desktop.
  • Add examples or references for Linux tools and workflows where applicable, such as az CLI or ARM template deployment via Bash.
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-03 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 tooling, such as PSCredential, Get-AutomationPSCredential, and Windows PowerShell modules. All code examples and instructions use PowerShell, with no mention of Bash, CLI, or Linux/macOS alternatives. Windows terminology and tools are referenced first and exclusively, which may create friction for Linux/macOS users who wish to use Azure Automation with Microsoft Entra ID.
Recommendations
  • Add equivalent examples using Azure CLI and Bash for credential management and runbook automation.
  • Clarify which steps are platform-agnostic and which are Windows/PowerShell-specific.
  • Provide guidance or links for Linux/macOS users on how to authenticate to Azure Automation using Microsoft Entra ID.
  • Mention cross-platform alternatives to PSCredential and PowerShell modules where possible.
  • Explicitly state if PowerShell is required for certain features, and suggest installation steps for PowerShell Core on Linux/macOS if relevant.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-03 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 demonstrates a notable Windows/PowerShell bias. PowerShell cmdlets are emphasized throughout, with detailed examples and workarounds provided for PowerShell users (including recommendations to use PowerShell when the portal fails for CSP accounts). The creation and management of certificates are described almost exclusively via PowerShell, and Windows-centric cryptographic provider requirements are mentioned. While Python examples are included for runbooks, there are no Linux shell (bash/CLI) examples, nor is there guidance for Linux/macOS users on certificate creation or management outside PowerShell. The documentation assumes familiarity with Windows tools and patterns, and PowerShell examples are presented before Python ones.
Recommendations
  • Add Azure CLI examples for certificate management tasks, especially for creation and retrieval.
  • Include guidance or examples for Linux/macOS users on preparing and uploading certificates (e.g., using OpenSSL to generate .pfx/.cer files).
  • Clarify whether PowerShell cmdlets must be run on Windows, or if cross-platform PowerShell Core is supported.
  • Mention any platform-specific limitations or requirements for certificate provider compatibility.
  • Present Python and CLI examples alongside PowerShell, not only after.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents Windows/PowerShell guidance and tools more prominently than Linux equivalents. Windows registry settings and PowerShell cmdlets are referenced repeatedly, while Linux guidance is less detailed and sometimes limited to external links or a single Python script. Most backup and export examples use Windows PowerShell cmdlets, with no Linux CLI or automation examples provided.
Recommendations
  • Provide equivalent Linux CLI (e.g., Azure CLI, Bash) examples for tasks currently shown only with PowerShell cmdlets, such as exporting runbooks and DSC configurations.
  • Include Linux-specific instructions or scripts for managing TLS settings, backing up assets, and other automation tasks, not just a single Python script.
  • Present platform guidance in parallel (Windows and Linux side by side), rather than listing Windows first or in more detail.
  • Reference cross-platform tools (e.g., Azure CLI, REST API) where possible, and clarify which steps are platform-agnostic.
  • Add explicit notes when a feature or cmdlet is Windows-only, and suggest Linux alternatives if available.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation for disaster recovery in Azure Automation presents only PowerShell and PowerShell Workflow scripts for asset migration, with no Bash, CLI, or Python alternatives. Steps and tabs for Hybrid Runbook Worker installation reference Windows first, and there are no Linux-specific examples or instructions for migration. This creates friction for Linux/macOS users who may prefer or require non-PowerShell tooling.
Recommendations
  • Provide equivalent migration scripts using Azure CLI, Bash, or Python for Linux/macOS users.
  • Include explicit Linux/macOS instructions and examples for Hybrid Runbook Worker installation and migration steps.
  • When listing tabs or instructions, alternate or parallelize Windows and Linux options rather than presenting Windows first.
  • Clarify any PowerShell requirements for Linux users (e.g., PowerShell Core installation) and provide guidance.
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-02 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, referencing Windows PowerShell modules and cmdlets throughout. All code examples and instructions are provided exclusively for PowerShell, with no mention of Bash, Azure CLI, or cross-platform scripting alternatives. The use of Windows-specific terminology and tools (e.g., PSCredential, Windows PowerShell modules) is prevalent, and Linux/macOS users are not given guidance for equivalent workflows.
Recommendations
  • Add Azure CLI examples for credential management and authentication to Azure using Microsoft Entra ID.
  • Clarify which steps are cross-platform and which are Windows-specific, especially around credential assets and runbook scripting.
  • Provide Bash or Python runbook examples, or reference how Linux/macOS users can achieve similar automation tasks.
  • Explicitly state PowerShell Core (pwsh) compatibility if applicable, and note any limitations for non-Windows platforms.
  • Mention that Azure Automation supports Python runbooks and link to relevant documentation for Linux/macOS users.
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-02 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 for configuring and invoking runbooks use PowerShell cmdlets or C# SDKs, with no equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or Python SDK). The only mention of Python is for runbook authoring, not for parameter assignment or invocation. There are no Linux-native shell or cross-platform CLI examples for starting or managing runbooks, and PowerShell is always presented first and in detail.
Recommendations
  • Add Azure CLI examples for starting runbooks and passing parameters, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script examples for invoking runbooks via the REST API, demonstrating how Linux users can automate these tasks.
  • Provide parity in SDK examples by including Python or JavaScript/TypeScript code snippets for starting runbooks and passing parameters.
  • Clarify in each section whether the instructions are cross-platform or Windows-specific, and link to cross-platform alternatives where possible.
  • Highlight any platform-specific limitations or differences explicitly, so users know what is or isn't supported on their OS.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-02 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 use PowerShell, and cmdlet references are exclusively for Windows PowerShell/Az modules. The process for creating credentials outside the portal is described only for Windows PowerShell, with no mention of Bash, Azure CLI, or Linux-native approaches. Python examples are included, but only as runbook code, not for asset management. There is no guidance for Linux/macOS users who may wish to automate credential management outside the portal.
Recommendations
  • Add Azure CLI examples for credential asset management, if supported.
  • Clarify whether credential management via CLI is possible on Linux/macOS, and provide instructions or alternatives.
  • If PowerShell is required, note cross-platform availability (PowerShell Core) and provide installation guidance for non-Windows platforms.
  • Explicitly state any limitations or platform requirements for credential management tasks.
  • Consider including Bash or REST API examples for asset creation and retrieval, if supported.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for managing certificates in Azure Automation is heavily focused on PowerShell cmdlets and workflows, which are most commonly used on Windows. All example scripts for certificate creation and management use PowerShell, with no equivalent CLI, Bash, or Linux-native instructions. The portal workaround also recommends PowerShell. While Python examples are provided for runbook access, all asset management and deployment examples are PowerShell-centric, and there are no Linux/macOS-specific instructions or parity for certificate creation or management.
Recommendations
  • Add Azure CLI examples for certificate creation, management, and deployment, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script examples for uploading certificates, leveraging az CLI or REST API.
  • Clarify which steps are platform-agnostic and which are PowerShell-specific, and provide alternatives where possible.
  • Mention any limitations or differences for Linux/macOS users explicitly, and link to relevant cross-platform guidance.
  • Reorder examples so that platform-neutral or cross-platform methods (such as Azure portal or Azure CLI) are presented before 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-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page provides both Windows and Linux guidance for TLS upgrades, but consistently references Windows tools (PowerShell cmdlets) for resource management and backup tasks. Examples and instructions for exporting or managing resources (runbooks, DSC nodes, configurations) are almost exclusively given using Windows PowerShell cmdlets, with no Linux or cross-platform CLI alternatives. Windows registry settings and links are presented before Linux equivalents in some sections.
Recommendations
  • Include Azure CLI and/or REST API examples for resource management tasks (e.g., exporting runbooks, managing DSC nodes) alongside PowerShell cmdlets.
  • Provide Linux/macOS-specific instructions or scripts for backup and export operations, not just Windows PowerShell.
  • Where possible, mention cross-platform tools (e.g., Azure CLI, Python SDK) before or alongside Windows-specific tools.
  • Balance the order of presentation so Linux guidance is not consistently secondary to Windows instructions.
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-01 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 use PowerShell, and references to credential handling and module installation are exclusively in the context of PowerShell and Windows. There are no examples or guidance for Linux/macOS users (e.g., Bash, Azure CLI, Python SDK), nor is there mention of how to perform these tasks outside of PowerShell. The use of terms like 'Windows PowerShell' and reliance on PSCredential and PowerShell cmdlets further reinforce the Windows bias.
Recommendations
  • Add equivalent examples using Azure CLI, Bash, or Python for Linux/macOS users.
  • Clarify whether Azure Automation runbooks can be authored in languages other than PowerShell and provide links or examples if so.
  • Mention cross-platform alternatives for credential management and authentication (e.g., Azure CLI's az login with service principal).
  • Explicitly state any limitations or requirements for PowerShell/Windows if they exist, or highlight cross-platform support if available.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation for disaster recovery in Azure Automation is heavily focused on PowerShell scripts and workflows, with no mention of Bash, Python, or other Linux-native scripting options for asset migration. All migration examples and instructions are PowerShell-based, and tabs for installation and Hybrid Runbook Worker management default to Windows, even though Linux is supported. This creates friction for Linux/macOS users who may not use PowerShell as their primary automation tool.
Recommendations
  • Provide equivalent Bash or Python scripts for asset migration between Automation accounts, or clarify if PowerShell is required regardless of OS.
  • Include Linux/macOS-specific instructions and examples for tasks such as Hybrid Runbook Worker installation and management.
  • Add notes or guidance for Linux users on how to run PowerShell scripts (e.g., via PowerShell Core on Linux/macOS), or offer alternative approaches.
  • Ensure that tabs and examples are presented in a neutral order (e.g., 'Windows | Linux') and that Linux instructions are not secondary.
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-01 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 tooling, with nearly all code examples and workflows using PowerShell cmdlets or C# SDKs. There is minimal coverage of Linux/macOS command-line usage, and no examples are provided for starting runbooks from Bash, Azure CLI, or non-Windows environments. The only non-PowerShell runbook type discussed is Python, but even there, examples for starting or managing Python runbooks from Linux/macOS are absent. The REST API is mentioned, but no cross-platform command-line examples (e.g., using curl or az CLI) are given. This creates friction for Linux/macOS users and those who prefer Azure CLI over PowerShell.
Recommendations
  • Add Azure CLI examples for starting runbooks and passing parameters, including az automation runbook commands.
  • Provide Bash/curl examples for invoking the REST API to start runbooks and pass parameters.
  • Clarify that PowerShell cmdlets can be used cross-platform, but also provide explicit instructions for Linux/macOS users (e.g., using PowerShell Core on Linux).
  • Include at least one end-to-end example for managing Python runbooks from a Linux/macOS environment.
  • Reorder sections or provide parallel examples so that Linux/macOS-friendly methods (Azure CLI, REST API with curl) are not always after PowerShell/Windows methods.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-01 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 cmdlets and objects (such as PSCredential) are specific to Windows/PowerShell environments. The creation of credential assets via CLI is only shown using Windows PowerShell, with no equivalent Bash, Azure CLI, or Linux shell examples. The documentation also lists PowerShell cmdlets first and in more detail, with Python examples present but less emphasized and no mention of Linux-native tools or workflows.
Recommendations
  • Add equivalent examples for creating and managing credential assets using Azure CLI (az automation credential) or REST API, which are cross-platform.
  • Clarify whether PowerShell Core (pwsh), which runs on Linux/macOS, is supported for these cmdlets, and provide examples if so.
  • Explicitly mention Linux/macOS compatibility for Python runbooks and credential management.
  • If graphical runbooks or portal actions are platform-agnostic, highlight this to reassure non-Windows users.
  • Include a note or section for Linux/macOS users on how to manage credentials outside of PowerShell, if 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-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for managing certificates in Azure Automation is heavily focused on PowerShell, with all command-line examples using PowerShell cmdlets and no equivalent Bash, CLI, or Linux-native instructions. The portal workaround also recommends PowerShell specifically. While Python examples are provided for runbooks, there are no Linux shell or Azure CLI examples for certificate management tasks, and PowerShell is consistently presented first and in greater detail.
Recommendations
  • Add Azure CLI examples for certificate management tasks (creating, retrieving, deleting certificates) to provide parity for Linux/macOS users.
  • Include Bash or shell script examples for uploading and managing certificates where possible.
  • Clarify which steps are platform-agnostic (e.g., Azure portal, Resource Manager templates) and which are Windows/PowerShell-specific.
  • Present cross-platform options (PowerShell, CLI, Python) side-by-side or in tabs, rather than leading with PowerShell.
  • Explicitly mention any limitations or differences for Linux/macOS users, such as the availability of PowerShell Core on non-Windows systems.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-01-31 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 configuration, but Windows instructions and references (especially PowerShell cmdlets) are presented first and more frequently. Data retention and backup sections rely heavily on Windows PowerShell cmdlets, with no equivalent CLI or Linux-native examples. Linux guidance is present for TLS, but not for other management tasks.
Recommendations
  • Provide Azure CLI or REST API examples alongside PowerShell cmdlets for resource management and backup tasks.
  • Include Linux/macOS-specific instructions for exporting runbooks and DSC configurations, not just PowerShell-based methods.
  • Present Windows and Linux guidance in parallel, rather than listing Windows first.
  • Reference cross-platform tools where possible, and clarify which steps are platform-agnostic.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-01-31 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 demonstrates a notable bias towards Windows and PowerShell tooling. PowerShell cmdlets are presented first and in detail, with multiple examples and workarounds recommended via PowerShell. The creation and management of certificates rely heavily on PowerShell and Windows-centric cryptographic providers. Linux/macOS alternatives, such as CLI or bash examples, are absent, and the Python examples are limited to accessing certificates, not managing them. The documentation assumes familiarity with Windows tools and patterns, which may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for certificate management tasks, including creation, retrieval, and deletion.
  • Include guidance or examples for Linux/macOS users, such as using OpenSSL to prepare certificates for upload.
  • Clarify which steps are platform-agnostic and which require Windows, and provide parity where possible.
  • Expand Python examples to include certificate management, not just retrieval.
  • Explicitly mention any limitations or requirements for non-Windows users when using Azure Automation certificates.
GitHub Create Pull Request
Automation Use Microsoft Entra ID in Azure Automation to authenticate to Azure ...ob/main/articles/automation/automation-use-azure-ad.md
Medium Priority View Details →
Scanned: 2026-01-31 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, CLI, or Linux/macOS alternatives. The process for creating credential assets and managing Azure resources is described exclusively using PowerShell cmdlets and Windows-specific concepts (e.g., PSCredential), with no guidance for users who may prefer or require cross-platform approaches.
Recommendations
  • Add equivalent examples using Azure CLI and Bash for credential management and runbook automation.
  • Clarify whether Azure Automation runbooks can be authored and executed using non-PowerShell languages (e.g., Python) and provide examples if supported.
  • Mention cross-platform alternatives to PSCredential and PowerShell modules, or note any platform limitations explicitly.
  • Where PowerShell is required, state that these steps apply to all platforms where PowerShell Core is available, and clarify any Windows-only requirements.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation for disaster recovery in Azure Automation provides only PowerShell and PowerShell Workflow scripts for migrating Automation account assets, with no mention of Bash, Azure CLI, or Python alternatives. The instructions and examples are Windows-centric, and Linux/macOS users are not given platform-specific guidance or parity in migration tooling. While the feature itself is cross-platform, the operational guidance is heavily biased toward Windows/PowerShell users.
Recommendations
  • Provide equivalent migration scripts or runbooks using Azure CLI, Bash, or Python for Linux/macOS users.
  • Include explicit instructions or examples for importing and executing runbooks from Linux/macOS environments.
  • Clarify any platform limitations and suggest cross-platform best practices for disaster recovery operations.
  • Where PowerShell is required, note how Linux/macOS users can install and use PowerShell Core (pwsh), and provide tested examples for those 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-01-31 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 for starting and interacting with runbooks use PowerShell cmdlets, C#, or the Azure portal. There are no CLI (az), Bash, or Linux-native examples for assigning parameters or starting runbooks. The PowerShell approach is always presented first and in detail, while Python runbooks are only briefly mentioned, and no Linux/macOS-specific workflows are covered.
Recommendations
  • Add examples using the Azure CLI (az automation runbook start) for starting runbooks and passing parameters, which work cross-platform.
  • Include Bash or shell script examples for Linux/macOS users, especially for tasks like passing JSON files as parameters.
  • Clarify that PowerShell Core (pwsh) is cross-platform and, where possible, provide examples that work on both Windows and Linux.
  • Mention and link to documentation for using the REST API with curl or other cross-platform tools.
  • Balance the order of presentation so that cross-platform methods (CLI, REST) are not always after PowerShell/Windows examples.
GitHub Create Pull Request
← Previous Page 31 of 40 Next →