Automation

232
Total Pages
137
Linux-Friendly Pages
95
Pages with Bias
40.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

365 issues found
Showing 276-300 of 365 flagged pages
Automation Edit textual runbooks in Azure Automation ...articles/automation/automation-edit-textual-runbook.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 workflows. All command-line examples use Windows PowerShell, with Windows file paths and terminology. There are no examples or guidance for Linux/macOS users, such as using PowerShell Core (pwsh), cross-platform file paths, or Azure CLI alternatives. Windows tools and patterns are mentioned exclusively, and Linux/macOS parity is not addressed.
Recommendations
  • Provide equivalent examples using PowerShell Core (pwsh) on Linux/macOS, including appropriate file paths (e.g., /home/user/runbooks).
  • Mention that Az PowerShell module can be used cross-platform and clarify any differences in usage or prerequisites.
  • Include Azure CLI examples for runbook export/import, if available.
  • Add notes or sections specifically addressing Linux/macOS workflows for editing and managing runbooks.
  • Avoid using only Windows file paths in examples; show both Windows and Linux/macOS paths where relevant.
GitHub Create Pull Request
Automation Handle errors in Azure Automation graphical runbooks ...omation/automation-runbook-graphical-error-handling.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 references Windows PowerShell concepts, cmdlets, and error types, with all examples and recommended practices centered around PowerShell and Windows-specific tooling. There is no mention of Linux or cross-platform alternatives, nor any examples using Bash, Python, or other non-Windows scripting environments. This creates friction for Linux/macOS users who may use Azure Automation with hybrid workers or non-Windows environments.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how graphical runbooks interact with non-Windows hybrid workers.
  • Provide examples using Bash, Python, or other supported languages in Azure Automation, especially for error handling.
  • Clarify which features (such as error links and exception conversion) are available or behave differently on Linux-based workers.
  • Reference cross-platform cmdlets or scripting patterns where applicable, and avoid assuming PowerShell is the only runtime.
  • Reorder examples or sections to present cross-platform guidance before or alongside Windows/PowerShell-specific instructions.
GitHub Create Pull Request
Automation Use Microsoft Entra ID in Azure Automation to authenticate to Azure ...ob/main/articles/automation/automation-use-azure-ad.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page is heavily focused on Windows and PowerShell tooling, with all code examples and module references using PowerShell. There are no Bash, CLI, or Linux/macOS-specific instructions or examples. Windows terminology and tools (e.g., PSCredential, Windows PowerShell modules) are used exclusively, and alternative cross-platform approaches are not mentioned.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for Linux/macOS users.
  • Clarify which steps and modules are cross-platform and which are Windows-specific.
  • Include instructions for installing and using Az modules and authentication on Linux/macOS.
  • Provide guidance on credential management and runbook authoring for non-Windows environments.
  • Explicitly state platform requirements or limitations for each method.
GitHub Create Pull Request
Automation Convert configurations to composite resources for Azure Automation State Configuration ...articles/automation/automation-dsc-create-composite.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 Windows PowerShell 5.1 and does not provide examples or guidance for Linux/macOS users. All instructions, terminology, and linked resources are centered on Windows tools and workflows, with no mention of cross-platform PowerShell or Linux-specific DSC scenarios. This creates friction for non-Windows users attempting to follow the guide.
Recommendations
  • Add explicit guidance for Linux/macOS users, including prerequisites and supported PowerShell versions (e.g., PowerShell Core).
  • Provide Linux/macOS-specific examples for configuration authoring, module creation, and MOF file generation.
  • Clarify which steps and tools are cross-platform and which are Windows-only.
  • Include references to Linux DSC onboarding and management workflows, not just Windows.
  • Update links and terminology to reflect cross-platform capabilities where applicable.
GitHub Create Pull Request
Automation Manage role permissions and security in Azure Automation ...les/automation/automation-role-based-access-control.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias in its examples and tooling. All command-line instructions for managing Azure RBAC roles are provided exclusively using Azure PowerShell cmdlets, with no mention of Azure CLI or REST API alternatives that are cross-platform and commonly used on Linux/macOS. The 'Configure Azure RBAC' section lists PowerShell as the only programmatic method, and all code samples are PowerShell-centric. There are no Linux/macOS-specific instructions, nor are cross-platform tools (like Azure CLI) presented as alternatives or even referenced.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets, especially for role assignment, listing, and removal.
  • Explicitly mention that Azure CLI and REST API can be used on Linux/macOS and provide links to relevant documentation.
  • Where possible, present cross-platform tools (Azure CLI, REST API) before or alongside PowerShell examples.
  • Clarify that PowerShell is available on Linux/macOS, but users may prefer Azure CLI for native experience.
  • Include a table or section comparing PowerShell, Azure CLI, and REST API approaches for RBAC management.
GitHub Create Pull Request
Automation Context switching in Azure Automation ...ocs/blob/main/articles/automation/context-switching.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 Azure PowerShell cmdlets and runbooks, with all examples and recommendations using PowerShell syntax and tools. There are no references to Bash, Azure CLI, or Linux/macOS automation patterns, and all code snippets and error messages are PowerShell-centric. This creates friction for users who prefer or require Linux-native automation approaches.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands and Bash scripting for context management in Azure Automation.
  • Clarify whether context switching issues also apply to non-PowerShell runbooks (e.g., Python, Bash) and provide guidance for those environments.
  • Include troubleshooting steps and error messages relevant to Linux/macOS users and Azure CLI.
  • Reorganize examples to present both PowerShell and CLI/Bash approaches side-by-side, or alternate which is shown first.
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-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, primarily through the exclusive use of PowerShell for configuration examples and the absence of equivalent Linux CLI (e.g., Azure CLI, Bash) or macOS instructions. Windows terminology and tools (PowerShell, host file) are mentioned first or exclusively in several sections, while Linux alternatives are referenced only in passing, with no actionable examples provided.
Recommendations
  • Provide Azure CLI (az) and Bash examples alongside PowerShell scripts for all configuration steps, especially for setting publicNetworkAccess.
  • Explicitly mention and illustrate how Linux/macOS users can perform the same tasks, including DNS configuration and host file edits.
  • Ensure screenshots and UI instructions are platform-neutral or clarify any platform-specific differences.
  • Add a dedicated section or callouts for Linux/macOS users, highlighting any differences or additional steps required.
GitHub Create Pull Request
Automation Remediate noncompliant Azure Automation State Configuration servers ...b/main/articles/automation/automation-dsc-remediate.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation prioritizes Windows remediation with detailed PowerShell examples and direct use of Windows tools (Update-DscConfiguration, Run Command), while Linux remediation is described in less detail, lacks direct script examples, and is presented as less capable (no Run Command support, registration process repetition required). Windows solutions are shown first and more completely, creating friction for Linux users.
Recommendations
  • Provide explicit Linux shell or Python script examples for remediation, similar to the PowerShell example for Windows.
  • Clarify and expand on Linux remediation steps, including direct command-line instructions and code samples.
  • Mention Linux alternatives to Windows tools (e.g., how to trigger DSC configuration application on Linux).
  • Present Windows and Linux sections with equal detail and prominence, possibly side-by-side.
  • Update links and references to include Linux-specific resources and documentation.
GitHub Create Pull Request
Automation Manage your Azure Automation account ...e-docs/blob/main/articles/automation/delete-account.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides command-line examples exclusively using Azure PowerShell, with no mention of Azure CLI or Bash commands. Windows-centric tools and patterns (PowerShell) are presented as the only automation option, and PowerShell examples are shown before any alternatives. There are no Linux/macOS-specific instructions or parity for command-line operations, which may hinder non-Windows users.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (e.g., deleting Automation accounts, removing solutions).
  • Explicitly mention that Azure CLI and Bash can be used on Linux/macOS and provide equivalent commands.
  • Reorder examples so that Azure CLI and PowerShell are presented with equal prominence, or alternate which is shown first.
  • Include notes or sections for Linux/macOS users, clarifying any platform-specific considerations.
GitHub Create Pull Request
Automation Start a runbook in Azure Automation ...e-docs/blob/main/articles/automation/start-runbooks.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell examples and referencing Windows PowerShell cmdlets as the primary CLI method for starting runbooks. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform scripting. Windows tools and terminology are used throughout, and PowerShell is presented before any mention of API or other methods, creating friction for non-Windows users.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and available on Linux/macOS.
  • Include Bash or shell script samples for starting runbooks via the Azure REST API.
  • Explicitly state which methods are cross-platform and which are Windows-only.
  • Reorder sections to present cross-platform methods (Azure CLI, API) before or alongside Windows-specific (PowerShell) methods.
  • Provide links to Linux/macOS setup guides for Azure Automation tasks.
GitHub Create Pull Request
Automation Migrate an existing agent-based hybrid workers to extension-based-workers in Azure Automation ...g-agent-based-hybrid-worker-to-extension-based-workers.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits several Windows biases. Most code examples (Bicep, ARM template, PowerShell) are exclusively for Windows VMs, with parameters and resource types hardcoded for Windows. The PowerShell and Azure CLI sections focus on Windows extension types and do not provide Linux-specific commands or examples. The REST API section mentions both 'HybridWorkerForWindows' and 'HybridWorkerForLinux', but does not provide concrete Linux-focused examples. The removal instructions for agent-based workers do include both Windows and Linux, but the migration and extension installation steps are Windows-centric. Windows tools (PowerShell, .NET Framework) are referenced in prerequisites and examples, while Linux equivalents are either missing or mentioned briefly and without actionable guidance.
Recommendations
  • Provide parallel Linux examples for Bicep, ARM template, PowerShell, and Azure CLI, including parameters and resource types for Linux VMs (e.g., 'HybridWorkerForLinux').
  • Explicitly document the steps and commands for installing the extension on Linux VMs, including any required package installation and configuration.
  • Include sample code for Linux VM creation and extension installation in Bicep and ARM templates.
  • In PowerShell and CLI sections, show how to target Linux VMs and use 'HybridWorkerForLinux' extension type.
  • List Linux prerequisites and troubleshooting steps with the same detail as Windows.
  • Ensure that Linux instructions are presented with equal prominence and clarity as Windows instructions, not just as notes or afterthoughts.
GitHub Create Pull Request
Automation Manage Python 2 packages in Azure Automation ...-docs/blob/main/articles/automation/python-packages.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides explicit instructions for downloading Python packages and dependencies using pip on a Windows 64-bit machine, but does not offer equivalent guidance or examples for Linux or macOS users. The command given is Windows-specific, and there is no mention of how to perform the same task on other platforms.
Recommendations
  • Add Linux/macOS instructions for downloading packages and dependencies, e.g., using 'pip download' on those platforms.
  • Include example commands for Linux/macOS alongside Windows commands, such as 'pip2 download -d <output dir> <package name>'.
  • Clarify that the process is not limited to Windows and provide cross-platform guidance where applicable.
  • Where screenshots or UI references are platform-neutral, ensure any CLI or scripting examples are also platform-neutral or have parity.
GitHub Create Pull Request
Automation Remove DSC and node from Automation State Configuration ...configuration/remove-node-and-configuration-package.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Windows-specific tools (cmdlets) are mentioned and given as examples before Linux equivalents. The manual deletion section provides a PowerShell cmdlet for Windows, but only a brief file path deletion instruction for Linux, lacking command-line examples. The Azure PowerShell method is emphasized for unregistering nodes, with no Linux CLI or automation tool alternatives. Linux instructions are present, but less detailed and appear after Windows steps.
Recommendations
  • Provide Linux shell command examples for unregistering nodes (e.g., using curl or az CLI).
  • Include explicit Linux commands for deleting .mof files (e.g., rm /etc/opt/omi/conf/dsc/configuration/*.mof).
  • Present Windows and Linux instructions side-by-side or in parallel tabs for equal visibility.
  • Mention Linux automation tools (such as Ansible, shell scripts) where relevant.
  • Clarify any differences in process or limitations for Linux 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-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias, with nearly all examples, code snippets, and tool references centered on PowerShell and Windows-centric workflows. PowerShell is presented as the primary runbook language, with detailed parameter configuration and invocation examples. There are no equivalent Bash, Linux shell, or cross-platform CLI examples for starting runbooks or passing parameters. Even SDK and REST API sections use Windows/PowerShell patterns, and the JSON passing section is exclusively PowerShell-focused. Linux/macOS users are left without guidance for their native environments.
Recommendations
  • Add examples for starting runbooks and passing parameters using Azure CLI (az automation runbook ...), which is cross-platform.
  • Include Bash or shell script examples for invoking REST API endpoints to start runbooks and pass parameters.
  • Clarify which steps and tools are cross-platform, and explicitly mention Linux/macOS compatibility where applicable.
  • Provide parity in parameter configuration examples for Python runbooks, including how to invoke them from Linux/macOS.
  • Reference Linux-native tools (curl, jq, etc.) for interacting with Azure Automation where appropriate.
  • Reorder sections so that cross-platform methods (REST API, Azure CLI) are presented before or alongside Windows/PowerShell methods.
GitHub Create Pull Request
Automation Manage variables in Azure Automation ...main/articles/automation/shared-resources/variables.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is the primary scripting language shown for variable management, with all CLI examples using Windows PowerShell cmdlets. There are no Bash, Azure CLI, or Linux shell examples for variable management. The documentation refers to 'Windows PowerShell' and 'Windows Hybrid Runbook Worker' explicitly, and does not mention Linux equivalents or cross-platform alternatives. The PowerShell examples and tools are presented before Python, and there is no parity for Linux-native scripting or command-line usage.
Recommendations
  • Add Azure CLI and Bash examples for variable management, showing how Linux/macOS users can create, retrieve, and update variables.
  • Clarify which features and cmdlets are cross-platform and which are Windows-only.
  • Mention Linux Hybrid Runbook Worker where applicable, and provide examples for it.
  • Reorder examples so that PowerShell and Python (or other cross-platform options) are presented equally, or indicate platform specificity.
  • Explicitly state any limitations for Linux/macOS users and provide guidance or workarounds.
GitHub Create Pull Request
Automation Create modular runbooks in Azure Automation .../main/articles/automation/automation-child-runbooks.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 examples use PowerShell syntax and cmdlets (e.g., Start-AzAutomationRunbook, Get-AzVM), with no mention of Linux/macOS alternatives or Bash/CLI equivalents. Windows/PowerShell terminology and modules are referenced exclusively and repeatedly, and there are no examples or guidance for users working with Python, Bash, or other cross-platform scripting environments. This creates friction for Linux/macOS users who may not use PowerShell as their primary automation language.
Recommendations
  • Add equivalent examples using Azure CLI and Bash, which are cross-platform and commonly used on Linux/macOS.
  • Explicitly mention platform support and limitations for runbook types (e.g., clarify if only PowerShell is supported, or if Python runbooks are possible).
  • Provide guidance or links for users who want to author runbooks in Python or other supported languages.
  • Reorder or balance examples so that PowerShell and CLI/Bash are presented equally, or clarify that PowerShell is required if that is the case.
  • Note any OS-specific behaviors or requirements, especially where Windows/PowerShell features do not translate to Linux/macOS.
GitHub Create Pull Request
Automation Manage connections in Azure Automation ...lob/main/articles/automation/automation-connections.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation is heavily focused on Windows PowerShell and Az PowerShell modules for managing Azure Automation connections. All CLI examples for creating and managing connections use PowerShell cmdlets, with no mention of Linux/macOS equivalents (such as Azure CLI or REST API usage). Windows tools and terminology (PowerShell, cmdlets) are presented first and exclusively in critical sections, such as connection creation and management. Python is supported for runbooks, but not for asset management outside runbooks. There are no Linux/macOS-specific instructions or parity examples.
Recommendations
  • Add Azure CLI examples for connection management tasks (create, get, remove) and clarify cross-platform compatibility.
  • Include REST API usage examples for connection asset management, which are platform-agnostic.
  • Explicitly state whether PowerShell cmdlets can be run on Linux/macOS (via PowerShell Core), or provide alternatives if not.
  • Reorder examples so that cross-platform or platform-agnostic methods (CLI, API) are presented before or alongside PowerShell.
  • Add a section or note on Linux/macOS usage, including any limitations or required steps.
GitHub Create Pull Request
Automation Using a user-assigned managed identity for an Azure Automation account ...main/articles/automation/add-user-assigned-identity.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias, primarily through the exclusive use of PowerShell for all command-line examples, deployment steps, and REST API invocations. Windows/PowerShell tools (e.g., Connect-AzAccount, Invoke-RestMethod, New-AzResourceGroupDeployment) are used throughout, with no mention or examples of equivalent Linux/macOS shell commands (such as Azure CLI or Bash scripting). Even in sections where REST API or ARM templates are discussed, the invocation and file handling are shown only via PowerShell. Python is briefly mentioned for runbooks, but only for token retrieval, not for resource management or deployment. There are no Linux/macOS-specific instructions or parity examples.
Recommendations
  • Provide Azure CLI examples for all major operations (assigning identities, deploying ARM templates, role assignments, REST API calls), as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash shell script examples for REST API invocation and file handling, demonstrating how Linux/macOS users can perform the same tasks.
  • Explicitly state that all PowerShell examples can be run on PowerShell Core (pwsh) on Linux/macOS, or provide alternative instructions if there are platform-specific limitations.
  • Reorder sections so that cross-platform tools (Azure CLI, REST API via curl) are presented before or alongside PowerShell examples.
  • Add troubleshooting and verification steps using Azure CLI and Bash, not just PowerShell.
  • Clarify any prerequisites or environmental variables for Linux/macOS users, such as file path conventions.
GitHub Create Pull Request
Automation Use an alert to trigger an Azure Automation runbook ...utomation/automation-create-alert-triggered-runbook.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a notable Windows bias. All code examples and instructions use PowerShell, with no mention of Bash, CLI, or cross-platform alternatives. Prerequisites and links reference Windows-centric resources (e.g., 'quick-create-powershell' for VMs), and the Azure Az PowerShell module is required. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented exclusively and first.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands, which are cross-platform and work on Linux/macOS.
  • Include instructions for creating and managing Azure Automation runbooks using Bash or shell scripts where possible.
  • Reference Linux/macOS VM creation guides alongside Windows guides in prerequisites.
  • Clarify that PowerShell Core is available cross-platform, and specify any OS-specific requirements.
  • Provide links to Linux/macOS setup guides for the Az modules and Azure Automation.
  • Explicitly state OS compatibility for all steps and highlight any differences.
GitHub Create Pull Request
Automation Create a standalone Azure Automation account ...les/automation/automation-create-standalone-account.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing examples and instructions primarily for Azure PowerShell, with no equivalent CLI or Linux/macOS-specific guidance. PowerShell runbooks and cmdlets are referenced and linked before alternatives, and there are no Bash/Azure CLI examples for key management or account creation tasks. The page assumes familiarity with PowerShell and Windows-centric tooling, creating friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for all tasks currently shown with PowerShell, especially for key rotation and account management.
  • Include Bash shell snippets where appropriate, and clarify cross-platform compatibility for all commands.
  • Present examples for both PowerShell and Azure CLI side-by-side, or use tabs to allow users to select their preferred environment.
  • Reference Python runbooks and other cross-platform automation options earlier and more prominently.
  • Explicitly state platform compatibility for all steps, and avoid assuming a Windows environment.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a strong bias towards Windows and PowerShell. All migration scripts and runbook examples are provided exclusively in PowerShell and PowerShell Workflow, with no mention of Bash, Python, or other Linux-native scripting options. The installation and management instructions for Hybrid Runbook Workers consistently reference Windows tabs and links first, and Linux instructions are only implied, not explicitly detailed. There is no guidance for Linux users on how to perform equivalent tasks using Linux tools or scripting languages.
Recommendations
  • Provide equivalent migration scripts and runbook examples using Bash, Python, or other Linux-native tools.
  • Explicitly document Linux installation and management steps for Hybrid Runbook Workers, including links and tabs for Linux.
  • Ensure that examples and instructions are presented in a platform-neutral order, or alternate between Windows and Linux first.
  • Mention cross-platform alternatives to PowerShell where applicable, and clarify any platform-specific limitations.
  • Add a section addressing Linux/macOS users and common scenarios they may encounter.
GitHub Create Pull Request
Automation Enable Azure Automation State Configuration .../main/articles/automation/automation-dsc-onboarding.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. PowerShell is the primary tool referenced throughout, with most examples and scripts written in PowerShell and targeted at Windows environments. Windows-specific tools (WMF 5, PowerShell DSC cmdlets) are mentioned first and in greater detail, while Linux instructions are comparatively brief, often referencing Python scripts but lacking equivalent step-by-step examples or explanations. Some sections, such as enabling VMs via PowerShell or generating metaconfigurations, are Windows-only or require a Windows machine even for Linux onboarding. Linux users must rely on workarounds or external scripts, and parity in guidance is lacking.
Recommendations
  • Provide Linux-first or Linux-parallel examples in each section, especially for onboarding and configuration tasks.
  • Include step-by-step Linux instructions using native Linux tools (e.g., shell scripts, Python) rather than requiring PowerShell or Windows hosts.
  • Expand Linux sections to match the detail and clarity of Windows instructions, including troubleshooting and verification steps.
  • Reference Linux equivalents for all Windows tools and cmdlets, and avoid assuming access to Windows environments for Linux onboarding.
  • Clearly indicate when a method is Windows-only and offer Linux alternatives upfront.
GitHub Create Pull Request
Automation Author graphical runbooks in Azure Automation ...les/automation/automation-graphical-authoring-intro.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 Windows PowerShell and PowerShell Workflow, with all examples, code snippets, and references using PowerShell syntax and Windows-centric tools. There is no mention of Linux/macOS equivalents, Bash, or cross-platform scripting. The graphical runbook authoring experience is described entirely in terms of PowerShell, and all referenced cmdlets and scripting patterns are Windows/PowerShell-specific. This creates friction for Linux/macOS users and those accustomed to Bash or other shells.
Recommendations
  • Explicitly state platform requirements and limitations at the top of the documentation (e.g., graphical runbooks require PowerShell and are not compatible with Bash or Linux-native scripting).
  • Provide guidance or links for Linux/macOS users, including alternative runbook types (e.g., Python runbooks) or cross-platform automation strategies.
  • Add a section comparing graphical runbooks (PowerShell-based) with textual runbooks that support Python or Bash, highlighting use cases and limitations.
  • Include examples or references for Python or Bash runbooks where appropriate, or clarify that graphical runbooks are Windows/PowerShell-only.
  • Mention that Azure Automation supports Python runbooks and provide links to relevant documentation for non-Windows users.
GitHub Create Pull Request
Automation Azure Automation State Configuration overview ...ob/main/articles/automation/automation-dsc-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell and Windows-centric terminology (e.g., PowerShell DSC, WMF, WinRM) are used throughout, with Windows operating systems and tools listed first and in more detail. Linux support is mentioned but receives less coverage, with no Linux-specific examples or detailed instructions. Proxy support and configuration examples are described for Windows first, with Linux details given briefly and secondarily. The documentation lacks parity in examples and guidance for Linux users.
Recommendations
  • Provide Linux-specific examples and walkthroughs for onboarding, configuration, and troubleshooting.
  • Include Linux tools and terminology (e.g., shell scripts, systemd, native DSC agent usage) alongside PowerShell examples.
  • List supported Linux distributions explicitly, not just by reference.
  • Ensure proxy configuration instructions for Linux are as detailed as those for Windows.
  • Balance the order of presentation so Linux and Windows are treated equally in lists and explanations.
  • Add links to Linux DSC documentation and community resources.
GitHub Create Pull Request
Automation Azure Automation FAQ ...e-docs/blob/main/articles/automation/automation-faq.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page generally covers both Windows and Linux scenarios, but there is a notable Windows bias in the Python interpreter selection section. Windows-specific environment variables and file paths (e.g., C:\Python2\python.exe) are described in detail, while Linux equivalents (such as typical Linux paths or environment variables) are omitted. There are no Linux-specific examples or instructions for configuring Python interpreter selection on Linux Hybrid Runbook Workers, and Windows terminology/tools are presented first.
Recommendations
  • Add explicit Linux examples for Python interpreter selection, such as environment variables and typical Linux paths (e.g., /usr/bin/python3).
  • Describe how Linux Hybrid Runbook Workers locate Python interpreters, including any differences from Windows.
  • Present Windows and Linux instructions in parallel or side-by-side, rather than Windows-first.
  • Include Linux-specific troubleshooting tips where relevant.
GitHub Create Pull Request
← Previous Page 12 of 15 Next →