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 726-750 of 982 flagged pages
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-10 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 for managing certificates in Azure Automation, with PowerShell presented first and in greater detail than Python. There are no examples or guidance for Linux/macOS users who may prefer Bash, CLI, or other non-PowerShell tools. The PowerShell-centric approach may create friction for non-Windows users, especially since Azure Automation supports Python runbooks but does not provide parity in certificate management examples or CLI alternatives.
Recommendations
  • Add Azure CLI examples for certificate management tasks alongside PowerShell examples.
  • Include guidance or examples for uploading certificates using Bash or other Linux-native tools.
  • Clarify whether PowerShell cmdlets can be used cross-platform (e.g., PowerShell Core on Linux/macOS) and provide instructions if so.
  • Present Python and CLI examples before or alongside PowerShell to avoid Windows-first bias.
  • Explicitly mention any limitations or requirements for Linux/macOS users when managing certificates in Azure 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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation heavily focuses on PowerShell and PowerShell Workflow runbooks, with detailed examples, screenshots, and step-by-step instructions. PowerShell cmdlets and Windows-centric patterns are used throughout, and PowerShell is presented first in nearly all sections. There are no examples or instructions for starting runbooks from Linux/macOS terminals or using cross-platform tools (e.g., Azure CLI, Bash). Python runbooks are briefly mentioned, but only in passing, with no concrete example. The SDK and REST API sections are platform-neutral, but the practical examples for parameter assignment are almost exclusively PowerShell-based.
Recommendations
  • Add Azure CLI examples for starting runbooks and passing parameters, including JSON and object parameters.
  • Include Bash shell examples for calling REST API endpoints to start runbooks and assign parameters.
  • Provide explicit instructions for Linux/macOS users, such as how to authenticate and use Azure Automation from non-Windows platforms.
  • Expand the Python runbook section with a concrete example of parameter usage and invocation.
  • Where PowerShell is used, clarify its cross-platform availability (PowerShell Core/7+) and note any Windows-only limitations.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-10 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 Windows PowerShell cmdlets and examples, with all CLI instructions and code samples provided only for PowerShell. There is no mention of Bash, Linux shell, or cross-platform CLI equivalents for credential management. The Python section is present, but all CLI and asset creation instructions are Windows/PowerShell-centric, and the graphical runbook instructions also assume a Windows/PowerShell context.
Recommendations
  • Add Azure CLI examples for credential asset creation and management, if supported.
  • Clarify whether credential assets can be managed from Linux/macOS environments, and provide instructions if possible.
  • Include Bash or cross-platform shell examples where applicable.
  • Explicitly state if PowerShell is required for certain operations, and provide guidance for Linux/macOS users (e.g., using PowerShell Core on Linux).
  • Mention PowerShell Core as a cross-platform option, and provide installation links 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-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on PowerShell and Windows-centric patterns, with nearly all examples, screenshots, and code snippets using PowerShell or referencing Windows tools. There is minimal coverage of Python runbooks, and no examples or guidance for Linux/macOS users on how to interact with Azure Automation runbooks outside of PowerShell. The REST API and SDK sections are platform-neutral, but the practical, step-by-step instructions and sample workflows are overwhelmingly Windows/PowerShell-oriented.
Recommendations
  • Provide equivalent examples for Linux/macOS users, such as using Azure CLI or Bash scripts to start runbooks and pass parameters.
  • Expand the Python runbook section with concrete examples, including how to start Python runbooks from Linux/macOS environments.
  • Add guidance for using REST API and SDKs from non-Windows platforms, including sample Bash/cURL commands.
  • Clarify that PowerShell examples are applicable on Linux/macOS where PowerShell Core is available, and provide notes or examples for cross-platform usage.
  • Include troubleshooting tips for Linux/macOS users, such as handling authentication and file paths.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-09 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 Linux/macOS shell (bash/CLI) examples, and PowerShell is presented first and most extensively. The Python section is included for runbooks, but lacks parity in certificate creation and management instructions compared to PowerShell. There is no mention of Linux tools or cross-platform alternatives for certificate handling.
Recommendations
  • Add Azure CLI examples for certificate creation, management, and retrieval to provide Linux/macOS parity.
  • Include bash or shell script examples for uploading and managing certificates where possible.
  • Clarify whether PowerShell examples are cross-platform (PowerShell Core) or Windows-only, and provide guidance for Linux/macOS users.
  • Mention any limitations or differences for Linux/macOS users in Azure Automation certificate management.
  • Ensure Python examples include certificate creation and management, not just retrieval.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for disaster recovery in Azure Automation is heavily focused on PowerShell scripts and workflows for asset migration, with no equivalent examples or guidance for Linux-native tools (such as Bash, CLI, or Python). All migration instructions and runbook examples are PowerShell-based, and references to script execution are tied to Windows-centric tooling. While the page states applicability to both Linux and Windows VMs, Linux users are left without clear guidance or parity for migration tasks.
Recommendations
  • Provide Bash or Azure CLI script examples for asset migration, or reference Python-based approaches if available.
  • Clarify whether PowerShell Core (cross-platform) is supported and provide instructions for Linux/macOS environments.
  • Add explicit guidance for Linux users on how to execute migration scripts/runbooks, including prerequisites and tooling.
  • Mention or link to any available Python runbooks or modules for asset migration, if supported.
  • Ensure that instructions for Hybrid Runbook Worker installation reference both Windows and Linux tabs equally, not just Windows.
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-09 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 code examples, module references, and credential handling instructions using PowerShell cmdlets and Windows-specific concepts. There are no examples or guidance for Linux/macOS users, such as using Python, Bash, or cross-platform Azure CLI. The page refers to 'Windows PowerShell' explicitly and does not mention alternatives or parity for non-Windows environments.
Recommendations
  • Add examples using Azure CLI, which is cross-platform, for credential asset creation and authentication.
  • Clarify whether Azure Automation runbooks can be authored in Python or other languages, and provide equivalent examples if possible.
  • Mention that PowerShell Core (pwsh) is available on Linux/macOS and indicate whether the provided scripts are compatible.
  • Provide guidance for Linux/macOS users on how to install and use required modules (e.g., Az, Microsoft Graph PowerShell SDK) in their environments.
  • Explicitly state any limitations or Windows-only requirements for Azure Automation, if applicable.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-09 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. Data retention and backup instructions reference Windows PowerShell cmdlets without Linux CLI or scripting equivalents, and Windows registry settings are linked before Linux OpenSSL guidance. Linux examples are present but less detailed and less prominent.
Recommendations
  • Provide equivalent Linux CLI or scripting examples for data retention and backup tasks, such as using Azure CLI or REST API instead of only PowerShell.
  • Balance the order of platform-specific guidance so Linux instructions are not always secondary to Windows.
  • Where PowerShell cmdlets are referenced, also mention Azure CLI or relevant REST API methods for cross-platform users.
  • Expand Linux-specific backup and export instructions, e.g., how to export runbooks or DSC configurations using Azure CLI or portal.
  • Clarify which tasks are platform-agnostic and which require Windows tools, to help Linux/macOS users navigate the documentation.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-09 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 cmdlets, and the process for creating credential assets outside the portal is described only with Windows PowerShell. There is no mention of Linux-native CLI tools or Bash/Az CLI equivalents for credential management. PowerShell examples are presented before Python, and no Linux shell or cross-platform CLI examples are provided.
Recommendations
  • Add equivalent examples using Azure CLI (az) for credential asset management, if supported.
  • Clarify whether PowerShell examples can be run cross-platform (e.g., PowerShell Core on Linux/macOS), or provide instructions for non-Windows environments.
  • Explicitly state any platform limitations (e.g., if credential management is only possible via PowerShell on Windows).
  • Provide guidance or links for Linux/macOS users on how to manage credentials in Azure Automation using supported tools.
  • Consider adding Bash or REST API examples for credential management, 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-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation heavily relies on PowerShell scripts and workflows for migration tasks, with no equivalent examples or guidance for Linux/macOS users (e.g., Bash, Python, or CLI). All migration instructions and runbook examples are PowerShell-centric, and there is no mention of cross-platform alternatives or Azure CLI usage. While the page acknowledges Linux VMs are supported, the practical guidance is Windows/PowerShell-focused.
Recommendations
  • Provide equivalent migration scripts or runbook examples using Azure CLI, Bash, or Python for Linux/macOS users.
  • Explicitly mention whether PowerShell Core (pwsh) is supported on Linux/macOS for the provided scripts, and clarify any limitations.
  • Add guidance or links for Linux/macOS users on how to execute migration tasks without relying on Windows PowerShell.
  • Include examples or references for using cross-platform tools (e.g., Azure CLI, REST API) to perform asset migration.
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-08 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 are made to Windows PowerShell modules and cmdlets. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Python SDK, or bash scripting, even though Azure Automation and Microsoft Entra ID are cross-platform services. The documentation refers to 'Windows PowerShell' explicitly and does not mention alternatives for non-Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI and/or Python SDK for credential management and authentication, especially for Linux/macOS users.
  • Clarify that PowerShell Core (pwsh) is cross-platform and can be used on Linux/macOS, and provide guidance for installing and using it.
  • Avoid using 'Windows PowerShell' unless the feature is truly Windows-only; otherwise, refer to 'PowerShell' generically.
  • Include notes or sections for Linux/macOS users, explaining any differences or limitations.
  • Provide links to cross-platform tools and documentation, such as Azure CLI and Microsoft Graph SDKs for other languages.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-08 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 via PowerShell. No Linux shell (bash) or cross-platform CLI examples are provided, and PowerShell is presented first and most extensively. While Python examples are included for runbooks, there are no Linux-native instructions or parity for certificate management outside PowerShell.
Recommendations
  • Add Azure CLI examples for certificate management tasks (creation, retrieval, deployment) to support Linux/macOS users.
  • Include bash shell scripting examples where applicable, especially for uploading certificates or interacting with Azure Automation.
  • Clarify whether PowerShell Core (pwsh), which is cross-platform, can be used for these tasks, and provide guidance for Linux/macOS environments.
  • Ensure that instructions for uploading certificates via the Azure portal are platform-neutral and note any OS-specific limitations.
  • Consider referencing or linking to Linux/macOS certificate management tools (e.g., openssl) for preparing .pfx/.cer files.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-08 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 (including PowerShell cmdlets and registry settings) are often presented first or more prominently. Several backup and retention examples rely on Windows PowerShell cmdlets, with no equivalent Linux CLI or scripting examples. Windows tools and terminology are referenced more frequently, creating friction for Linux users.
Recommendations
  • Provide Linux CLI or scripting alternatives (e.g., Azure CLI, Bash) alongside PowerShell cmdlet examples for backup and retention tasks.
  • Present Windows and Linux guidance in parallel or with equal prominence, rather than Windows-first ordering.
  • Reference Linux-specific tools (such as Bash scripts, Azure CLI, or Python) for asset and runbook export/import, where possible.
  • Clarify when a task is Windows-only, and offer Linux workarounds or note limitations if Linux parity is not possible.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on PowerShell and Windows-centric patterns, with all code examples and parameter assignment workflows using PowerShell or Windows tools. There are no Linux/bash examples for starting runbooks or passing parameters, and PowerShell is presented as the primary method for automation. Python runbooks are mentioned, but only briefly and without parity in example depth. The SDK and REST API sections are platform-neutral, but the practical guidance and walkthroughs are Windows-first.
Recommendations
  • Add examples for starting runbooks and passing parameters using Azure CLI (bash) on Linux/macOS.
  • Provide equivalent bash or shell scripts for JSON parameter passing and runbook invocation.
  • Clarify that PowerShell can be used cross-platform, but also highlight Azure CLI as a Linux-friendly alternative.
  • Expand Python runbook examples to match the depth of PowerShell walkthroughs.
  • Explicitly mention any limitations or differences for Linux/macOS users when using Azure Automation.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-08 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 for managing credentials in Azure Automation. All CLI examples are in PowerShell, and references to 'Windows PowerShell' are explicit. There is no mention of Linux shell equivalents (e.g., Bash, Azure CLI), nor are there examples for Linux/macOS users outside of Python runbooks. The documentation assumes familiarity with PowerShell and Windows credential objects, which may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for credential management tasks, such as creating, retrieving, and deleting credentials.
  • Clarify whether PowerShell cmdlets can be used cross-platform (PowerShell Core on Linux/macOS), and provide guidance for non-Windows environments.
  • Explicitly mention limitations or alternatives for Linux/macOS users, especially if certain features are Windows-only.
  • Provide Bash or shell script examples where possible, or link to relevant Azure CLI documentation.
  • Reorder sections to present platform-neutral or cross-platform methods first, or clearly label Windows-specific instructions.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-05 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 instructions and PowerShell cmdlets are mentioned first and more frequently, especially in backup/export and retention sections. Linux-specific examples for exporting or managing Automation account data are missing, and most command-line examples use Windows PowerShell cmdlets without Linux CLI or scripting alternatives.
Recommendations
  • Provide equivalent Linux CLI or scripting examples (e.g., using Azure CLI, az automation, or REST API) for tasks like exporting runbooks, DSC configurations, and managing assets.
  • When listing platform-specific instructions, alternate the order or present Linux and Windows equally rather than always listing Windows first.
  • Include references to Linux-compatible tools and commands (such as Bash scripts or Azure CLI) alongside PowerShell cmdlets.
  • Clarify when a feature or cmdlet is Windows-only, and suggest Linux alternatives where 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-05 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 is heavily focused on PowerShell and Windows-centric tooling. All CLI examples for certificate creation and management use PowerShell cmdlets, with no mention of Linux/macOS equivalents or cross-platform CLI tools (e.g., Azure CLI). The recommended workaround for portal upload issues is PowerShell, and PowerShell examples are presented first and in greater detail than Python. There is no guidance for Linux/macOS users on how to perform these tasks outside of PowerShell.
Recommendations
  • Add Azure CLI examples for certificate management tasks (creation, upload, retrieval) to provide parity for Linux/macOS users.
  • Explicitly mention platform requirements for PowerShell cmdlets and note alternatives for non-Windows environments.
  • Include guidance or links for certificate management using REST API or ARM templates from non-Windows platforms.
  • Clarify whether PowerShell Core (pwsh) on Linux/macOS is supported for these cmdlets, and provide examples if so.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation for managing credentials in Azure Automation is heavily PowerShell-centric, with all CLI examples and cmdlet references using Windows PowerShell syntax and concepts. There are no Bash, Linux shell, or cross-platform CLI examples provided, and PowerShell is presented first and in more detail than Python. This creates friction for Linux/macOS users who may prefer or require non-PowerShell approaches.
Recommendations
  • Add Azure CLI (az) examples for credential management, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Clarify whether PowerShell Core (pwsh) is supported for these cmdlets and provide examples for it if so.
  • If credential management is possible via REST API or SDKs (e.g., Python, .NET), include references and basic usage examples.
  • Explicitly note any platform limitations for cmdlets (e.g., if some are Windows PowerShell only).
  • Consider adding Bash or shell script examples for common tasks, or at least mention how Linux users can perform equivalent actions.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-05 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 for asset migration, with no mention of Bash, Python, or cross-platform alternatives. All migration examples and instructions are PowerShell-based, which is more native to Windows environments. While the page claims applicability to both Linux and Windows VMs, Linux users are left without platform-native guidance or examples, and PowerShell is assumed as the default automation tool. Additionally, links and tabs for Hybrid Runbook Worker installation default to Windows, with Linux instructions only referenced indirectly.
Recommendations
  • Provide equivalent Bash or Python scripts for asset migration, or clarify PowerShell Core (pwsh) compatibility on Linux/macOS.
  • Explicitly document how Linux users can install and use PowerShell (Core) for these tasks, including prerequisites and platform-specific caveats.
  • Add Linux/macOS specific examples or tabs for Hybrid Runbook Worker installation and migration steps.
  • Where PowerShell is required, clarify whether Windows PowerShell or PowerShell Core is supported, and highlight cross-platform usage.
  • Consider listing Linux instructions/examples before or alongside Windows ones to avoid implicit prioritization.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. All code examples and module references are for PowerShell, with no mention of Bash, Azure CLI, or cross-platform scripting options. The process for creating credential assets and managing Azure resources is only described using PowerShell cmdlets, which may not be familiar or accessible to Linux/macOS users. The phrase 'Windows PowerShell' is used, and there is no parity for Linux or macOS environments.
Recommendations
  • Add equivalent Azure CLI (az) examples for credential management and authentication, which are cross-platform.
  • Clarify that PowerShell Core (pwsh) is supported on Linux/macOS and provide examples or notes for those platforms.
  • Where possible, provide Bash or Python SDK examples for common automation tasks.
  • Avoid using 'Windows PowerShell' unless the feature is truly Windows-only; otherwise, use 'PowerShell' to indicate cross-platform support.
  • Explicitly state platform requirements and alternatives for non-Windows 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-05 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 and Windows-centric tools and patterns. All code examples for interacting with Azure Automation runbooks (defining parameters, starting runbooks, passing JSON, etc.) use PowerShell or C#. There are no CLI (az), Bash, or Linux-native examples for starting runbooks or passing parameters, and PowerShell is assumed as the primary interface. The only non-PowerShell runbook type discussed is Python, but even there, examples for starting Python runbooks from non-PowerShell environments are missing.
Recommendations
  • Add examples using Azure CLI (az automation runbook start) for starting runbooks and passing parameters, including JSON objects.
  • Include Bash or shell script examples for Linux/macOS users, especially for tasks like reading JSON and invoking REST APIs.
  • Clarify that PowerShell examples work cross-platform (if true), or provide guidance for PowerShell Core/7+ on Linux/macOS.
  • Provide parity in examples for Python runbooks, such as how to start them and pass parameters using CLI or REST from Linux/macOS.
  • Mention or link to documentation for installing and using Azure PowerShell on Linux/macOS, if PowerShell is required.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.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 Tools Windows First
Summary
The documentation is heavily focused on PowerShell and Windows-centric tooling (PSCredential, PowerShell cmdlets, Windows PowerShell examples) for managing credentials in Azure Automation. While Python examples are provided, there is no mention of Linux shell (bash) or cross-platform CLI alternatives, and the PowerShell/Windows approach is presented first and in more detail. The documentation assumes the use of PowerShell, which is traditionally a Windows tool, and does not address Linux/macOS users who may prefer bash, Azure CLI, or other cross-platform methods.
Recommendations
  • Add Azure CLI examples for credential management, especially for creating and retrieving credentials, to support Linux/macOS users.
  • Clarify whether PowerShell Core (pwsh) is supported and provide examples for cross-platform PowerShell usage.
  • Explicitly mention platform requirements and alternatives for users who do not use Windows or PowerShell.
  • Include notes or sections on how Linux/macOS users can interact with Azure Automation credentials, if possible.
  • If PowerShell is required, state this clearly at the beginning and provide guidance for installing PowerShell Core on non-Windows platforms.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-04 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 Linux-native tooling for asset migration. While the page states applicability to both Linux and Windows VMs, all migration examples and instructions are PowerShell-based, and tabs/links default to Windows-centric instructions. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other scripting environments.
Recommendations
  • Provide equivalent Bash or Python scripts for asset migration, or clarify if PowerShell Core (cross-platform) is required and supported.
  • Explicitly mention PowerShell Core compatibility and provide installation instructions for Linux/macOS users.
  • Add examples or guidance for running migration tasks from Linux/macOS environments.
  • Where possible, offer Azure CLI alternatives to PowerShell cmdlets for common operations.
  • Reorder or balance examples so Linux and Windows approaches are presented equally.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation shows moderate Windows bias. Windows/PowerShell tools and cmdlets are mentioned first or exclusively in several sections (e.g., data retention, backup, DSC configurations), while Linux equivalents are missing or only briefly referenced. Although there is a Linux-specific TLS upgrade example, most automation and backup instructions assume Windows/PowerShell usage, creating friction for Linux users.
Recommendations
  • Provide Linux CLI (az CLI, Bash, or Python) examples alongside or before PowerShell cmdlets for tasks like exporting runbooks, DSC configurations, and managing assets.
  • Include instructions or references for managing DSC nodes, assets, and runbooks from Linux environments (e.g., using Azure CLI, REST API, or SDKs).
  • Balance the order of presentation so that Linux and Windows guidance are given equal prominence.
  • Where PowerShell is referenced, clarify if cross-platform PowerShell Core can be used, or provide alternative Linux-native approaches.
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-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. Nearly all code examples, parameter handling, and automation scenarios are shown using PowerShell, PowerShell Workflow, or C# SDK, with only brief mention of Python runbooks. There are no examples using Bash, Azure CLI, or Linux-native tools for starting or interacting with runbooks. The only non-PowerShell runbook type discussed is Python, and even then, only minimal guidance is given. All examples for starting runbooks from the command line use PowerShell cmdlets, and there is no parity for Linux/macOS users who may prefer Bash or Azure CLI.
Recommendations
  • Add examples for starting and passing parameters to runbooks using Azure CLI (az automation runbook start) with equivalent parameter handling.
  • Include Bash shell examples for interacting with the REST API (using curl/jq) to start runbooks and pass parameters.
  • Expand the Python runbook section with more detailed examples, including parameter handling and invocation from Linux/macOS environments.
  • Clearly indicate which features or examples are Windows/PowerShell-specific, and provide Linux/macOS alternatives where possible.
  • Add a table or section comparing PowerShell, Azure CLI, and REST API approaches for cross-platform automation.
GitHub Create Pull Request
← Previous Page 30 of 40 Next →