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 626-650 of 982 flagged pages
Automation Encryption of secure assets in Azure Automation ...icles/automation/automation-secure-asset-encryption.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 provides extensive PowerShell examples for configuring secure asset encryption in Azure Automation, with PowerShell commands shown first and in detail. There are no equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash), and PowerShell is referenced as the primary tool for tasks like assigning managed identities and configuring Key Vault access policies. REST API examples are included, but Linux-native tooling is not covered.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all major configuration steps (e.g., assigning managed identities, configuring Key Vault access policies, switching to customer-managed keys).
  • Explicitly mention that PowerShell commands can be run cross-platform (on Linux/macOS) if using PowerShell Core, or clarify any Windows-specific requirements.
  • Provide Bash or Azure CLI scripts for Linux/macOS users to ensure parity.
  • Reorder sections so that REST API and CLI examples are not always secondary to PowerShell.
  • Reference Azure CLI documentation and modules where relevant.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page is heavily focused on PowerShell and Windows-centric tooling, with most examples, screenshots, and parameter handling described in terms of PowerShell, PowerShell Workflow, and graphical runbooks (which are also PowerShell-based). Windows/PowerShell tools and patterns are mentioned first and most frequently, while Python runbooks (the main cross-platform option) receive minimal coverage and lack detailed examples. There are no Linux-specific CLI examples or references to Bash/Az CLI workflows for assigning parameters, and the PowerShell-centric approach may create friction for Linux/macOS users.
Recommendations
  • Add detailed examples for Python runbooks, including parameter handling and invocation from Linux/macOS environments.
  • Include Az CLI examples for starting runbooks and passing parameters, demonstrating cross-platform workflows.
  • Clarify that PowerShell examples are applicable on Linux/macOS when using PowerShell Core, or provide explicit guidance for those platforms.
  • Balance the order of examples so that Python and Az CLI are not always secondary to PowerShell.
  • Mention any limitations or differences for Linux/macOS users, especially regarding graphical runbooks or PowerShell-specific features.
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-23 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 for managing modules in Azure Automation is heavily focused on PowerShell and Windows-centric workflows. Most examples, instructions, and module references are for PowerShell, with explicit mentions of Windows PowerShell versions and cmdlets. Internal cmdlets and certain module features are unavailable on Linux Hybrid Runbook Workers, but this is noted. There are no Linux/bash examples, and Linux-specific guidance is minimal or missing. Python module support is mentioned but not detailed. The portal instructions and PowerShell Gallery workflows are also Windows-oriented.
Recommendations
  • Add explicit Linux Hybrid Runbook Worker guidance, including limitations and supported module types.
  • Provide bash or Python examples for module management where possible, especially for custom modules.
  • Clarify which features are cross-platform and which are Windows-only, ideally with a summary table.
  • Expand the 'Python modules' section to include practical examples and parity with PowerShell workflows.
  • Add links or references to Linux-specific documentation for Azure Automation, 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-22 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 for Azure Automation' demonstrates a notable Windows bias. All migration scripts and runbook examples are provided exclusively in PowerShell and PowerShell Workflow, with no equivalent Bash, Python, or cross-platform scripting options. The instructions for Hybrid Runbook Worker installation link to pages with Windows tabs by default, and the prerequisites and module requirements are focused on PowerShell modules. There is no guidance for Linux users on using alternative scripting languages or tools, nor are Linux-specific examples or considerations provided.
Recommendations
  • Provide equivalent Bash or Python scripts for asset migration, or clearly state if PowerShell is required regardless of OS.
  • Include Linux/macOS-specific instructions or examples, especially for Hybrid Runbook Worker scenarios.
  • Clarify whether PowerShell Core (pwsh) is supported and provide guidance for Linux users on installing and using PowerShell if it is required.
  • Add links or tabs for Linux-specific documentation where Windows tabs are referenced.
  • Mention any limitations or requirements for Linux users explicitly, such as module compatibility or script execution 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-22 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 examples for all procedural steps, with no equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI). PowerShell is presented as the primary scripting interface, and REST API alternatives are provided, but Azure CLI or Bash examples are missing. The prerequisites and procedural sections reference PowerShell modules and cmdlets first and exclusively, creating friction for users on Linux/macOS platforms.
Recommendations
  • Add Azure CLI examples for all procedural steps (e.g., assigning managed identity, configuring Key Vault access policy, switching encryption keys).
  • Include Bash scripting examples where applicable, especially for automation scenarios.
  • Mention cross-platform tools (Azure CLI, Bash) alongside PowerShell in prerequisites and procedural guidance.
  • Clarify that PowerShell examples can be run on Linux/macOS using PowerShell Core, but provide native CLI/Bash alternatives for parity.
  • Reorganize sections so that REST API and CLI examples are not secondary to PowerShell.
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-22 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, with all examples and instructions provided exclusively for PowerShell. There are no references to Bash, Linux CLI tools, or cross-platform scripting approaches. Windows-specific tools and patterns (e.g., PSCredential, Get-AutomationPSCredential, New-AzAutomationCredential) are mentioned without Linux/macOS alternatives or guidance. The PowerShell-centric approach creates friction for Linux/macOS users, especially since Azure Automation supports Python runbooks and cross-platform scripting.
Recommendations
  • Add examples for Python runbooks, which are supported in Azure Automation and are cross-platform.
  • Clarify which steps are PowerShell-specific and provide equivalent instructions for Bash/CLI where possible (e.g., using Azure CLI for credential management).
  • Mention that PowerShell Core (pwsh) is cross-platform and provide guidance for Linux/macOS users on how to install and use it.
  • Include links or references to Linux/macOS-specific documentation for Azure Automation authentication.
  • Explicitly state any Windows-only limitations if present, or clarify that the steps are applicable to all platforms if using PowerShell Core.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-22 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 tools (PowerShell cmdlets) are mentioned first and more frequently throughout the data retention and backup sections. Examples for exporting and managing resources rely heavily on Windows PowerShell cmdlets, with no equivalent Linux/CLI examples provided. Linux guidance is present for TLS, but less so for other management tasks.
Recommendations
  • Provide Azure CLI or REST API examples alongside PowerShell cmdlets for resource management, backup, and retention tasks.
  • Include Linux-specific instructions for exporting runbooks, DSC configurations, and retrieving asset details, where possible.
  • Ensure Linux guidance is given equal prominence and order in tables and lists, not always after Windows.
  • Clarify which tasks are cross-platform and which are Windows-only, and offer alternatives 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-22 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on PowerShell-based runbooks and examples, with all code snippets and parameter-passing walkthroughs using PowerShell, PowerShell Workflow, or C# (for SDK usage). There are no examples or guidance for using Linux-native tools (e.g., Azure CLI, Bash) to start or interact with runbooks, nor are there examples for Python runbooks beyond a brief mention. The PowerShell-centric approach may create friction for Linux/macOS users who prefer or require non-PowerShell tooling.
Recommendations
  • Add Azure CLI (az automation runbook) examples for starting runbooks and passing parameters, including JSON parameter input.
  • Provide Bash and/or Python-based examples for interacting with runbooks, especially for Linux/macOS users.
  • Include explicit guidance or code snippets for starting Python runbooks with parameters from non-PowerShell environments.
  • Where possible, present cross-platform tooling (e.g., Azure CLI, REST API with curl) before or alongside PowerShell examples.
  • Clarify in relevant sections that PowerShell examples are shown, and link to equivalent CLI or SDK documentation for other platforms.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-22 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 Windows PowerShell and PowerShell-based cmdlets for managing credentials in Azure Automation. All CLI examples are PowerShell-based, and there are no Bash, Linux shell, or cross-platform CLI examples. The page refers to 'Windows PowerShell' specifically and does not mention Linux or macOS equivalents for credential management. Python examples are provided, but only for runbooks, not for asset management outside runbooks. The documentation assumes familiarity with PowerShell and Windows-centric tools, creating friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for credential management tasks, where possible, to provide cross-platform guidance.
  • Clarify whether credential asset management is possible via Azure CLI, REST API, or SDKs, and provide links or examples.
  • Explicitly state if PowerShell is required for certain operations, and note any limitations for Linux/macOS users.
  • If PowerShell Core (pwsh) is supported on Linux/macOS for these tasks, mention this and provide relevant examples.
  • Include guidance or links for Linux/macOS users on installing and using PowerShell Core if it is needed.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-only script example for configuring the 'publicNetworkAccess' property, without offering a Linux/macOS equivalent (such as Azure CLI or REST API). While the page covers both Windows and Linux in the context of Hybrid Runbook Workers and Update Management, the scripting example is Windows-centric and may create friction for Linux/macOS users. Additionally, PowerShell is presented as the primary automation method, with no mention of cross-platform alternatives.
Recommendations
  • Add Azure CLI and/or REST API examples for configuring 'publicNetworkAccess', alongside the PowerShell script.
  • Explicitly mention that PowerShell examples are Windows-centric and provide guidance for Linux/macOS users.
  • Ensure that scripting and automation instructions are presented in a cross-platform manner, or at least offer parity.
  • Consider showing Azure CLI examples before or alongside PowerShell to avoid 'windows_first' bias.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-22 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, which are primarily associated with Windows environments. All certificate management tasks (creation, retrieval, deployment) are shown using PowerShell, with no equivalent Bash, CLI, or Linux-native tooling examples. PowerShell is presented first and in greater detail than Python, and there are no explicit instructions or examples for Linux/macOS users to perform certificate operations outside of Python runbooks.
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 where applicable, especially for uploading certificates or interacting with Azure Automation.
  • Clarify whether PowerShell examples are cross-platform (PowerShell Core) or Windows-only, and provide guidance for Linux/macOS users if PowerShell Core is supported.
  • Consider referencing or linking to documentation for certificate management on Linux/macOS, such as using OpenSSL to generate .pfx/.cer files.
  • Present Python and CLI examples alongside PowerShell, not after, to avoid 'windows_first' bias.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell modules and Windows-centric workflows, with nearly all examples, tools, and instructions assuming the use of PowerShell and Windows environments. There is minimal mention of Linux or cross-platform scenarios, and Linux-specific guidance is limited to brief notes about unsupported features. No Linux shell (e.g., Bash) or cross-platform scripting examples are provided, and the internal cmdlets and modules are often unavailable on Linux Hybrid Runbook Workers, with no Linux alternatives or workarounds described.
Recommendations
  • Add explicit guidance and examples for Linux Hybrid Runbook Workers, including supported modules and any differences in workflow.
  • Provide Linux/macOS shell (e.g., Bash, Python) examples where possible, especially for module management and automation tasks.
  • Clearly indicate which features are Windows-only and suggest Linux alternatives or workarounds where feasible.
  • Expand the Python modules section to include more parity with PowerShell guidance, and link to Linux-specific resources.
  • When describing portal or PowerShell Gallery workflows, note any platform-specific limitations and provide Linux-compatible instructions if available.
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-21 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 examples for all procedural steps, with no equivalent examples for Azure CLI, Bash, or other Linux/macOS-friendly tools. PowerShell is presented as the primary scripting interface, and REST API examples are included, but Linux-native workflows (such as Azure CLI or Bash scripting) are not covered. This creates friction for Linux/macOS users, who must translate PowerShell steps or rely on REST API calls without guidance.
Recommendations
  • Add Azure CLI examples for all procedural steps (e.g., assigning managed identities, configuring Key Vault access policies, reconfiguring encryption keys).
  • Include Bash scripting samples where appropriate, especially for automation scenarios.
  • Present Azure CLI and PowerShell examples side-by-side, or at least mention Azure CLI as an alternative.
  • Clarify that PowerShell examples work cross-platform (if true), or note any Windows-specific limitations.
  • Link to Azure CLI documentation for relevant commands (e.g., az automation account, az keyvault).
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-21 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 tools and patterns. All CLI examples are given in PowerShell, with no Bash, Linux, or macOS shell equivalents. The creation and management of credentials are described exclusively using PowerShell cmdlets, and the phrase 'Windows PowerShell' is used explicitly. Python examples are provided, but there are no Linux-native shell or CLI examples for credential management. The documentation assumes familiarity with PowerShell and Windows concepts, which creates friction for Linux/macOS users.
Recommendations
  • Add Bash/CLI examples for credential management where possible, such as using Azure CLI (az) commands.
  • Clarify whether PowerShell Core (pwsh), which is cross-platform, can be used instead of Windows PowerShell.
  • Explicitly mention Linux/macOS support and limitations for credential assets in Azure Automation.
  • Provide guidance or links for Linux/macOS users on how to interact with Azure Automation credentials outside of PowerShell.
  • If PowerShell is required, note that PowerShell Core is available cross-platform and provide installation instructions.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-21 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 and disaster recovery tasks, with no mention of Bash, Python, or CLI alternatives. All migration examples and instructions are PowerShell-based, and the tabs and links default to Windows/PowerShell terminology. While the page claims applicability to both Linux and Windows VMs, Linux users are left without platform-native scripting guidance, creating friction for those not using PowerShell.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for migration tasks, or at least mention if PowerShell Core (pwsh) is supported cross-platform.
  • Clarify whether PowerShell Core scripts can be executed on Linux Hybrid Runbook Workers, and provide explicit Linux instructions if so.
  • Add examples or links for Python runbooks or other cross-platform automation options.
  • Reorder or balance examples so Linux and Windows approaches are presented equally, or in parallel tabs.
  • Explicitly state any limitations or requirements for Linux users (e.g., if only PowerShell is supported, clarify that PowerShell Core is required and provide installation guidance).
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-21 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-specific instructions and PowerShell cmdlets are mentioned first or exclusively in several sections (e.g., retention and backup). Windows registry settings and PowerShell tools are referenced without Linux equivalents, and Windows examples precede Linux ones in some areas.
Recommendations
  • Add parity for Linux in retention and backup sections by referencing Linux CLI or scripting methods (e.g., Azure CLI, Bash, Python) for managing and exporting resources.
  • Where PowerShell cmdlets are mentioned, also provide equivalent Azure CLI or REST API commands for Linux/macOS users.
  • Ensure Linux instructions are presented alongside Windows instructions, not after or below them.
  • Clarify when a feature or tool is Windows-only, and provide alternative guidance for Linux users where possible.
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-21 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 and Windows terminology appear first in some sections, such as referencing the Log Analytics agent for Windows before Linux. However, the overall guidance is mostly platform-neutral, and Linux is mentioned where relevant (e.g., Log Analytics agent support, Update Management for Windows and Linux).
Recommendations
  • Add Azure CLI and/or ARM template examples for configuring 'publicNetworkAccess' to ensure Linux/macOS users can follow along without relying on PowerShell.
  • Where possible, present cross-platform options (PowerShell, CLI, Portal) together, or list CLI/portal methods before PowerShell.
  • Clarify that the PowerShell example is just one option, and link to documentation for CLI/ARM/REST alternatives.
  • Ensure screenshots and instructions are not Windows-centric unless the feature is Windows-only.
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-21 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 handling are presented exclusively in PowerShell, with no mention of Bash, Azure CLI, or Linux/macOS scripting alternatives. Windows-specific tools and patterns (PSCredential, PowerShell modules) are referenced throughout, and Linux/macOS users are not provided with equivalent guidance or examples.
Recommendations
  • Add Azure CLI examples for authentication and credential management in Azure Automation.
  • Provide guidance for Linux/macOS users on how to create and manage credential assets using the Azure portal or CLI.
  • Mention cross-platform PowerShell Core compatibility and clarify if scripts work on Linux/macOS environments.
  • Include notes or links to relevant Linux/macOS documentation for Azure Automation and Microsoft Entra ID integration.
  • Where possible, show Bash or Python alternatives for runbook automation.
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-21 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. Nearly all code examples, parameter handling, and automation scenarios are shown using PowerShell or C#, with no equivalent examples for Linux/macOS shells (e.g., Bash, Azure CLI). The only non-PowerShell runbook type discussed is Python, but even there, examples are minimal and lack parity with PowerShell sections. There are no Bash or Azure CLI examples for starting runbooks or passing parameters, and the workflow for Linux/macOS users is not addressed. The documentation assumes PowerShell as the primary interface for both authoring and invoking runbooks.
Recommendations
  • Add Azure CLI examples for starting runbooks and passing parameters, showing equivalent workflows to the PowerShell cmdlets.
  • Include Bash shell examples for interacting with the REST API (e.g., using curl or httpie) to start runbooks and pass parameters.
  • Provide guidance for Linux/macOS users on installing and using Azure PowerShell (if required), or clarify when PowerShell Core (cross-platform) is supported.
  • Expand the Python runbook section with more detailed examples, including parameter handling and invocation from non-Windows environments.
  • Clearly indicate when features or cmdlets are Windows-only, and suggest cross-platform alternatives where 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-21 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 exclusively using PowerShell. There are no examples or guidance for Linux/macOS users on how to perform equivalent tasks using bash, Azure CLI, or other cross-platform tools. PowerShell is presented as the primary and default method, and Linux alternatives are not mentioned or provided.
Recommendations
  • Add Azure CLI examples for certificate management tasks (creation, retrieval, deployment) to provide parity for Linux/macOS users.
  • Include bash or shell script examples where relevant, especially for uploading certificates or interacting with Azure Automation.
  • Clarify that PowerShell examples are cross-platform if applicable (e.g., PowerShell Core), or specify Windows-only limitations.
  • Mention any limitations or differences for Linux/macOS users, and provide links to relevant documentation for those platforms.
  • Reorder sections or add tabs so that Azure CLI or Python examples are shown alongside or before PowerShell examples.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell modules and cmdlets, with all examples and instructions using PowerShell syntax and tools. Windows-specific modules and features (such as internal cmdlets only available on Windows Hybrid Runbook Workers) are described in detail, while Linux equivalents are either not mentioned or explicitly noted as unsupported. There are no examples or guidance for managing Python modules beyond a brief reference, and no mention of Linux-native automation tools or workflows.
Recommendations
  • Provide equivalent examples and instructions for Python runbooks, including how to manage Python modules and packages in Azure Automation.
  • Clarify which features are Windows-only at the start of each relevant section, and offer Linux alternatives or workarounds where possible.
  • Include explicit guidance for Linux Hybrid Runbook Workers, such as supported module types, limitations, and best practices.
  • Add examples using cross-platform tools (e.g., Azure CLI) where applicable, or reference them as alternatives to PowerShell.
  • Where PowerShell is required, note compatibility with PowerShell Core (pwsh) on Linux/macOS, and highlight any differences.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-20 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 in several sections, Windows/PowerShell tools are mentioned first or exclusively. Examples for exporting runbooks and DSC configurations reference only PowerShell cmdlets, with no equivalent CLI or Linux-native instructions. Some asset management and deletion tasks are described only with PowerShell cmdlets, and Linux alternatives are not provided.
Recommendations
  • Provide Azure CLI or REST API examples alongside PowerShell cmdlets for tasks like exporting runbooks, DSC configurations, and managing assets.
  • When referencing platform-specific instructions, present Linux and Windows guidance in parallel, or clarify when a feature is Windows-only.
  • Include Linux-native methods (e.g., Bash scripts, az CLI commands) for backup and management operations where possible.
  • In tables and lists, avoid consistently listing Windows before Linux unless there is a technical reason.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-20 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 migration tasks, with no mention of Bash, CLI, or Python alternatives. All migration examples and instructions are PowerShell-based, and there are no Linux-native scripting options or examples. While the page states applicability to both Linux and Windows VMs, the tooling and examples are Windows-centric, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for asset migration between Automation accounts.
  • Include Python runbook examples for migration, as Azure Automation supports Python runbooks.
  • Clarify if PowerShell scripts can be executed from Linux/macOS environments, and provide guidance for cross-platform usage.
  • Add explicit instructions or links for Linux/macOS users on how to perform migration tasks without relying on Windows tools.
  • Mention and demonstrate the use of Azure CLI for relevant operations (e.g., account creation, asset replication).
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides extensive PowerShell-based examples for configuring encryption of secure assets in Azure Automation, with REST API alternatives. There are no Azure CLI (cross-platform) examples, and PowerShell is referenced as the primary scripting interface, which may create friction for Linux/macOS users who prefer or require CLI/bash-based workflows.
Recommendations
  • Add Azure CLI examples for all major operations (assigning managed identity, configuring Key Vault access policy, updating Automation account encryption).
  • Explicitly mention that PowerShell examples work cross-platform with PowerShell Core, and clarify any Windows-only limitations.
  • Reorder sections to present REST API or CLI examples before or alongside PowerShell to avoid the impression of Windows-first bias.
  • Reference Azure CLI documentation in the prerequisites, not just PowerShell.
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-20 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 PowerShell-specific, with no mention of Bash, Azure CLI, or cross-platform scripting. The phrase 'Windows PowerShell' is used, and there are no Linux/macOS equivalents or guidance for users who may want to use Python runbooks or other cross-platform approaches in Azure Automation.
Recommendations
  • Add Azure CLI examples for credential management and authentication, showing how to achieve similar tasks using Bash or cross-platform tools.
  • Clarify that PowerShell in Azure Automation is cross-platform, but also provide explicit guidance for Linux/macOS users running scripts locally or authoring runbooks.
  • Include references to Python runbooks or other supported languages in Azure Automation, with links or examples for authenticating to Azure using Microsoft Entra ID.
  • Avoid using 'Windows PowerShell' unless the instructions are truly Windows-only; otherwise, use 'PowerShell' to reflect cross-platform support.
  • Add a section or note explaining how Linux/macOS users can install required modules and interact with Azure Automation.
GitHub Create Pull Request
← Previous Page 26 of 40 Next →