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 676-700 of 982 flagged pages
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page is heavily focused on PowerShell cmdlets and Windows-centric patterns for managing credentials in Azure Automation. All CLI examples are in PowerShell, and there is no mention of Bash, Azure CLI, or Linux-native credential management approaches. The 'Create a new credential asset' section only provides a Windows PowerShell example, with no Linux or cross-platform CLI equivalent. The documentation assumes familiarity with PowerShell concepts and tools, which may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for creating and managing credential assets, if supported.
  • Explicitly state if credential asset management is only possible via PowerShell, or clarify cross-platform alternatives.
  • Provide guidance for Linux/macOS users, including how to install and use PowerShell Core (pwsh) if required.
  • Mention any limitations or platform requirements for credential management in Azure Automation.
  • Consider including Bash or shell script examples if relevant APIs exist.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides extensive PowerShell-based examples for configuring secure asset encryption in Azure Automation, with REST API alternatives but no Azure CLI or Linux/macOS-specific guidance. PowerShell is presented as the primary scripting method, and Linux-friendly approaches (such as Azure CLI or Bash) are either missing or only briefly mentioned. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer CLI/Bash workflows.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all tasks, including assigning managed identities, configuring Key Vault access policies, and updating encryption settings.
  • Explicitly mention cross-platform options (e.g., Azure CLI, Bash) and their compatibility with Linux/macOS.
  • Reorder sections to present REST API and CLI examples before or alongside PowerShell, rather than after.
  • Clarify that PowerShell examples are cross-platform (if using Az PowerShell Core), or provide guidance for Linux/macOS users if not.
  • Link to Azure CLI documentation for relevant commands.
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-17 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 management, module installation, and runbook scripting are exclusively in the context of PowerShell. There are no examples or guidance for users who may wish to use Python, Bash, or other cross-platform scripting languages supported by Azure Automation. The phrase 'Windows PowerShell' is used, and no mention is made of PowerShell Core (pwsh) or cross-platform compatibility. Linux/macOS users may find it unclear whether these instructions apply to them or how to adapt them.
Recommendations
  • Clarify whether the PowerShell examples are compatible with PowerShell Core (pwsh) on Linux/macOS, or if they require Windows PowerShell.
  • Add equivalent examples or guidance for using Python runbooks, which are supported in Azure Automation and widely used on Linux/macOS.
  • If PowerShell is required, explicitly state that PowerShell Core is supported on all platforms, and provide installation instructions for Linux/macOS.
  • Avoid using 'Windows PowerShell' unless the feature is truly Windows-only; otherwise, use 'PowerShell' to indicate cross-platform compatibility.
  • Mention or link to documentation for Bash or other cross-platform scripting options in Azure Automation, if applicable.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page for 'Disaster recovery for Azure Automation' is notably PowerShell-centric, with all migration scripts and runbook examples provided exclusively in PowerShell and PowerShell Workflow. There are no equivalent examples or guidance for Linux-native scripting tools (such as Bash or Python), nor are cross-platform alternatives discussed. Additionally, links and instructions often default to Windows tabs or terminology, and Windows is mentioned first in several hybrid worker scenarios. This creates friction for Linux/macOS users, especially those who prefer or require non-PowerShell solutions.
Recommendations
  • Provide Bash or Python script examples for migrating Automation account assets, or clarify if PowerShell Core (pwsh) is fully supported cross-platform.
  • Explicitly state PowerShell Core compatibility and provide instructions for Linux/macOS users, including installation and execution steps.
  • Add guidance or links for using Azure CLI or REST API for asset migration where possible.
  • Ensure hybrid worker instructions and links are balanced, showing both Windows and Linux tabs equally.
  • Mention cross-platform considerations in prerequisites and limitations, such as PowerShell module support on Linux/macOS.
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-17 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 public network access flags, without offering an equivalent CLI or Linux-friendly example. While the article mentions both Windows and Linux in the context of Hybrid Runbook Workers and Update Management, the scripting guidance is Windows-centric. The PowerShell example is presented as the primary method for automation, and no Azure CLI, REST API, or ARM template alternatives are given. Additionally, PowerShell is mentioned before any Linux tools or cross-platform options.
Recommendations
  • Add Azure CLI and/or REST API examples for configuring public network access flags, ensuring Linux/macOS users can follow along without PowerShell.
  • Explicitly mention that PowerShell is available cross-platform, but provide guidance for Linux users on installing and using it if PowerShell is required.
  • Where possible, provide ARM template snippets or portal instructions alongside scripting examples.
  • Review other scripting sections for Windows-centric language or assumptions, and clarify cross-platform applicability.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-17 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 for certificate management in Azure Automation, with no mention of Linux/macOS shell equivalents or cross-platform CLI usage. All detailed examples for creating and managing certificates use PowerShell, and PowerShell is presented first and most prominently. There are Python examples for runbooks, but no guidance for Linux users on certificate creation or management outside of PowerShell.
Recommendations
  • Add Azure CLI examples for certificate management tasks, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Clarify whether PowerShell examples are usable on PowerShell Core (pwsh) on Linux/macOS, or if Windows PowerShell is required.
  • Provide guidance for Linux/macOS users on preparing .pfx/.cer files and uploading them via the Azure portal or CLI.
  • Mention any limitations or differences for Linux/macOS users, especially if certain cmdlets or features are Windows-only.
  • Ensure that introductory sections acknowledge cross-platform usage and link to relevant Linux/macOS documentation where applicable.
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-17 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 is heavily focused on PowerShell modules and Windows-centric workflows, with almost all examples, instructions, and tooling based on PowerShell and Windows Automation environments. Linux Hybrid Runbook Worker support is mentioned only to highlight limitations (e.g., internal cmdlets not available), and there are no Linux-specific or cross-platform module management examples. Python module support is referenced, but not detailed. The guidance, examples, and screenshots are almost exclusively Windows/PowerShell-oriented, creating friction for Linux/macOS users.
Recommendations
  • Add explicit guidance and examples for managing modules on Linux Hybrid Runbook Workers, including any differences in workflow or limitations.
  • Provide parity in examples for module import, update, and deletion using cross-platform tools (e.g., Azure CLI, REST API), not just PowerShell.
  • Clarify which features are Windows-only and which are available cross-platform, ideally with a comparison table.
  • Expand the Python module section with more details and examples, especially for Linux environments.
  • Include at least one end-to-end Linux Hybrid Runbook Worker scenario for module management.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page heavily emphasizes PowerShell and Windows-centric tooling and patterns throughout, with most examples, screenshots, and workflows using PowerShell cmdlets or referencing Windows concepts. Linux/macOS equivalents (such as Bash, CLI, or Python) are minimally covered, and PowerShell is presented as the primary interface for parameter assignment and runbook invocation. There are no examples showing how to start runbooks or pass parameters from Linux/macOS environments using Azure CLI or Bash, nor is there guidance for non-Windows users beyond Python runbooks.
Recommendations
  • Add Azure CLI examples for starting runbooks and passing parameters, including JSON input, to demonstrate cross-platform usage.
  • Include Bash shell examples for parameter assignment and runbook invocation.
  • Clarify that PowerShell examples work on PowerShell Core (pwsh) on Linux/macOS, and provide explicit instructions for those environments.
  • Expand Python runbook parameter examples to show invocation from Linux/macOS.
  • Reorder sections so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell examples.
  • Add notes or links for Linux/macOS users about installing and using PowerShell Core, if PowerShell is required.
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-16 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 public network access flags, without offering a Linux/macOS equivalent (such as Azure CLI or REST API). Additionally, PowerShell and Windows terminology appear first or exclusively in some sections, though Linux is mentioned in agent support. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI and/or REST API examples alongside PowerShell scripts for configuration tasks.
  • Where possible, mention cross-platform tools (e.g., Azure CLI, Bash) before or alongside Windows/PowerShell tools.
  • Clarify that PowerShell examples are for Windows users, and provide guidance for Linux/macOS users.
  • Ensure screenshots and portal instructions are platform-neutral, or note any platform-specific differences.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-02-16 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 cmdlets and Windows-centric tools (e.g., PSCredential, PowerShell modules), with Windows PowerShell examples and terminology used throughout. While Python examples are provided, there are no Linux/bash or cross-platform shell examples. Windows tools and patterns are mentioned first and exclusively in several sections, and the creation of credentials via CLI is only shown for Windows PowerShell.
Recommendations
  • Add examples for creating and managing credential assets using Azure CLI or REST API, which are cross-platform and usable from Linux/macOS.
  • Clarify whether PowerShell Core (pwsh) on Linux/macOS is supported for these operations, and provide examples if so.
  • Mention or link to any Linux/macOS-compatible automation options, if available.
  • Where possible, avoid referring to 'Windows PowerShell' exclusively and use 'PowerShell' if the cmdlets are compatible across platforms.
  • Provide parity in credential management examples for Python, Azure CLI, and REST API.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation heavily features PowerShell examples for all procedural steps, with no equivalent Bash/Azure CLI examples provided. PowerShell is presented as the primary scripting interface, and references to installing the Azure Az PowerShell module are made without mention of cross-platform alternatives. REST API examples are included, but the lack of Azure CLI or Bash scripting guidance creates friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for all procedural steps currently shown only in PowerShell.
  • Mention that PowerShell Core and Azure Az PowerShell module are cross-platform, but also provide Bash/CLI alternatives.
  • Reorder sections to present REST API and CLI examples alongside PowerShell, not after.
  • Reference Azure CLI installation and usage for Linux/macOS users where PowerShell module installation is mentioned.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-16 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 Azure Automation disaster recovery is heavily focused on PowerShell scripts and workflows for asset migration, with no equivalent examples or guidance for Linux-native tools or scripting languages. All migration instructions and runbook examples are PowerShell-based, and there is no mention of Bash, Python, or CLI alternatives. While the page states applicability to both Linux and Windows VMs, the practical guidance and tooling are Windows-centric.
Recommendations
  • Provide equivalent migration scripts or runbook examples using Bash, Python, or Azure CLI for Linux users.
  • Include guidance on how Linux users can import, execute, or adapt runbooks without relying on PowerShell.
  • Mention any limitations or considerations for Linux environments explicitly, and offer workarounds or alternatives.
  • Where possible, show both PowerShell and Linux-native (e.g., Bash, Python) examples side-by-side.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-16 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 (with links and explicit steps) are mentioned first and in more detail. PowerShell cmdlets are referenced for several backup and retention operations, but equivalent Linux/CLI/REST examples are not provided. Some operations (like exporting runbooks or DSC configurations) only mention PowerShell cmdlets, with no Linux-native or cross-platform alternatives. This creates friction for Linux/macOS users, though most tasks are still possible via the portal or other means.
Recommendations
  • Provide Azure CLI or REST API examples alongside PowerShell cmdlets for tasks like exporting runbooks and DSC configurations.
  • List Linux and Windows instructions in parallel or in separate, clearly labeled sections to avoid 'Windows first' ordering.
  • Where PowerShell cmdlets are referenced, add notes or links to equivalent Linux-compatible tools or scripts, or clarify if the operation is only possible via PowerShell.
  • For asset backup/retrieval, clarify cross-platform limitations and suggest 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-16 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 tooling, with nearly all examples, screenshots, and code snippets using PowerShell or referencing Windows concepts. 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 guidance for local execution and parameter passing is almost exclusively Windows/PowerShell-oriented.
Recommendations
  • Add examples for starting runbooks from Linux/macOS using Azure CLI, Bash, or Python scripts.
  • Provide guidance on how to pass parameters using Azure CLI (az automation runbook start) and include sample commands.
  • Expand the Python runbook section with more detailed examples, including parameter passing and execution from Linux/macOS environments.
  • Mention cross-platform tools and clarify which instructions are Windows-specific.
  • Include notes or tables summarizing parity between PowerShell and CLI/SDK approaches for parameter assignment.
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-16 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 users who may wish to use Azure Automation with Python runbooks or other cross-platform scripting options, nor is there mention of Bash/CLI alternatives. The documentation refers to 'Windows PowerShell' specifically and does not clarify cross-platform compatibility.
Recommendations
  • Add examples using Azure CLI or Python runbooks to demonstrate cross-platform automation.
  • Clarify whether the PowerShell modules and cmdlets used are compatible with PowerShell Core (pwsh) on Linux/macOS, or if they are Windows-only.
  • Where possible, use 'PowerShell' instead of 'Windows PowerShell' unless the feature is truly Windows-only, and note any platform limitations.
  • Provide links or references to documentation for using Azure Automation with Python or other supported languages.
  • Explicitly state if certain features or modules are Windows-only, so Linux/macOS users are aware of limitations.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-16 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 workflows for certificate management in Azure Automation, with all CLI examples provided in PowerShell. There are no Bash, Linux CLI, or cross-platform shell examples for certificate upload or management. PowerShell is presented first and as the primary method, with Python examples only for certificate retrieval in runbooks, not for certificate creation or upload. There is no mention of Linux-native tools or workflows for certificate management.
Recommendations
  • Add Azure CLI (az) examples for certificate management, including upload, retrieval, and deletion.
  • Provide Bash or shell script examples for certificate manipulation and upload, especially for Linux/macOS users.
  • Clarify whether PowerShell Core (pwsh) is supported on Linux/macOS for these cmdlets, and if so, provide guidance for cross-platform usage.
  • Mention any limitations or alternatives for Linux/macOS users if PowerShell is required.
  • Consider including references to OpenSSL or other Linux-native certificate tools for preparing certificates before upload.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on PowerShell modules and Windows-centric patterns, with most examples, instructions, and tooling referencing Windows PowerShell, Az/AzureRM modules, and Windows-specific cmdlets. Linux Hybrid Runbook Worker support is mentioned only to note limitations, and there are no Linux or cross-platform examples for module management. Python module support is referenced but not detailed. All portal and PowerShell instructions assume Windows environments and tools.
Recommendations
  • Add explicit guidance and examples for Linux Hybrid Runbook Workers, including how to manage modules and any differences in module import, execution, and limitations.
  • Provide parity in examples for module management using cross-platform tools (e.g., Azure CLI, REST API), or clarify which steps are Windows-only.
  • Include a section summarizing which features are Windows-only and which are supported on Linux/macOS, with links to Linux-specific documentation.
  • Expand documentation for Python modules and other non-PowerShell module types, including import and management instructions.
  • Where possible, show Linux/macOS command-line equivalents or note limitations for non-Windows users.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-15 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 Azure Automation disaster recovery is heavily focused on PowerShell scripts and workflows for asset migration, with no equivalent examples or guidance for Linux-native tools or scripting languages (e.g., Bash, Python). All migration instructions and runbook examples are PowerShell-based, and there is no mention of alternatives for Linux users. While the page states support for both Linux and Windows VMs, the practical guidance is Windows-centric.
Recommendations
  • Provide equivalent Bash or Python scripts for asset migration, or clarify if PowerShell Core (cross-platform) is supported and provide explicit instructions for Linux/macOS environments.
  • Add examples and instructions for importing and executing runbooks using Linux tools or Azure CLI.
  • Mention PowerShell Core compatibility and any prerequisites for Linux users (e.g., installation steps for PowerShell on Linux).
  • Include guidance for Linux users on managing Automation accounts and assets, especially for hybrid worker scenarios.
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-15 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 all major configuration steps, with REST API alternatives, but does not offer Azure CLI or bash examples. PowerShell is presented as the primary scripting interface, and Linux/macOS users are not shown equivalent command-line workflows. The only mention of Azure CLI is in the context of revoking access, and even there, no CLI example is provided.
Recommendations
  • Add Azure CLI examples for all major steps (e.g., assigning managed identity, configuring Key Vault access policy, updating Automation account encryption).
  • Where PowerShell is used, provide equivalent bash/CLI commands, or at least reference how Linux/macOS users can accomplish the same tasks.
  • Clarify that PowerShell examples can be run cross-platform using PowerShell Core, if applicable, or note any Windows-specific requirements.
  • Reorder sections or provide parallel examples so that Linux/macOS users do not feel secondary to Windows users.
GitHub Create Pull Request
Automation Use Azure Private Link to securely connect networks to Azure Automation ...in/articles/automation/how-to/private-link-security.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides only PowerShell examples for configuring public network access flags, with no equivalent CLI, Bash, or Azure CLI examples. The State Configuration scenario is described as PowerShell DSC-focused, and Windows terminology (PowerShell, DSC) is used before mentioning Linux. While Linux is referenced in the context of Update Management and Log Analytics agent support, actionable configuration examples and instructions are Windows/PowerShell-centric.
Recommendations
  • Add Azure CLI and/or Bash examples alongside PowerShell for tasks such as setting publicNetworkAccess.
  • Explicitly document Linux/macOS-compatible workflows for configuring Automation account network settings.
  • In the State Configuration section, clarify how Linux nodes can be managed, and provide examples or references for Linux DSC equivalents.
  • Where PowerShell is referenced, add a note or link to cross-platform alternatives (e.g., Azure CLI, REST API).
  • Ensure screenshots and portal instructions are not Windows-specific (they appear neutral here, but review for any subtle bias).
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Windows and Linux guidance for TLS upgrades, but Windows registry/PowerShell tools and cmdlets are referenced more frequently and often first. Several backup and data management examples rely exclusively on Windows PowerShell cmdlets, with no equivalent Azure CLI, Bash, or cross-platform alternatives provided. Linux guidance is present but less detailed, and Linux users may need to infer or research equivalent steps.
Recommendations
  • Add Azure CLI or REST API examples for tasks currently only documented with Windows PowerShell cmdlets, such as exporting runbooks and DSC configurations.
  • When referencing platform-specific steps, present Linux and Windows guidance with equal prominence and detail.
  • Provide Bash or shell script examples for Linux users where PowerShell cmdlets are used for Windows.
  • Clarify when a feature or cmdlet is Windows-only, and suggest cross-platform alternatives if available.
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-15 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 exclusively uses Windows PowerShell examples and references Windows-specific PowerShell modules and cmdlets. There are no examples or guidance for Linux/macOS users, such as Bash, Azure CLI, or cross-platform scripting. The focus on PowerShell and Windows tools creates friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples for credential asset creation and runbook authentication, which are cross-platform.
  • Clarify whether PowerShell Core (pwsh) is supported in Azure Automation and provide examples if so.
  • Mention that Azure Automation runbooks can be authored in Python and provide equivalent Python examples where possible.
  • Explicitly note any limitations or requirements for Windows PowerShell vs. PowerShell Core, especially for Linux/macOS users.
  • Provide links or references to Linux/macOS-specific guidance for Azure Automation authentication.
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-15 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, with nearly all code examples, parameter handling, and automation workflows demonstrated using PowerShell or PowerShell Workflow. Windows tools and patterns (such as PowerShell cmdlets and .NET types) are referenced throughout, and examples for starting and passing parameters to runbooks are almost exclusively shown with PowerShell. Linux/macOS users are not provided with equivalent Bash, CLI, or Python examples for parameter assignment, nor are cross-platform alternatives discussed. The Python section is brief and lacks practical parameter assignment examples. The ordering of sections and examples consistently puts Windows/PowerShell first.
Recommendations
  • Add Azure CLI examples for starting runbooks and assigning parameters, demonstrating cross-platform usage.
  • Expand the Python runbook section with concrete examples of parameter assignment and invocation from Linux/macOS environments.
  • Include Bash shell examples for calling the REST API to start runbooks and pass parameters, showing how Linux/macOS users can automate these tasks.
  • Clarify which features are PowerShell-specific and which are cross-platform, and provide guidance for Linux/macOS users where possible.
  • Consider reordering sections or providing parallel examples (PowerShell and CLI/Bash/Python) 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-15 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on PowerShell modules and Windows-centric workflows, with most examples, tools, and instructions tailored to Windows environments. Internal cmdlets and features are explicitly unavailable on Linux Hybrid Runbook Workers, and Linux-specific guidance is minimal or absent. Python module support is mentioned but not detailed, and there are no Linux shell or cross-platform examples for module management. The documentation assumes familiarity with Windows/PowerShell tools and patterns, creating friction for Linux/macOS users.
Recommendations
  • Add explicit guidance and examples for managing modules on Linux Hybrid Runbook Workers, including any limitations or alternative workflows.
  • Provide parity for module import, update, and deletion using Linux-compatible tools (e.g., Azure CLI, REST API) and shell examples.
  • Clarify which features are Windows-only and offer Linux alternatives or workarounds where possible.
  • Expand the Python module section to include more details and cross-platform examples.
  • Include a summary table of feature availability by OS (Windows, Linux, macOS) for clarity.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page heavily emphasizes PowerShell cmdlets and examples, with all CLI instructions and code samples provided exclusively in PowerShell. There are no Bash, Linux CLI, or cross-platform shell examples for certificate management tasks. PowerShell is presented first and as the primary method, with Python examples included only for runbook scripting, not for certificate management operations. There is no mention of Linux-native tools or workflows for certificate handling in Azure Automation.
Recommendations
  • Add Bash or Azure CLI examples for certificate management tasks, such as uploading and retrieving certificates.
  • Clarify whether PowerShell cmdlets can be used cross-platform (on Linux/macOS) or if they are Windows-only, and provide alternatives if needed.
  • Include guidance for Linux/macOS users on preparing and uploading certificates, including any OS-specific requirements or limitations.
  • Present PowerShell and Python examples side-by-side, rather than PowerShell-first, to improve parity.
  • Mention any limitations or differences for Linux/macOS users in Azure Automation certificate handling.
GitHub Create Pull Request
← Previous Page 28 of 40 Next →