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 151-175 of 365 flagged pages
Automation Remove DSC and node from Automation State Configuration ...configuration/remove-node-and-configuration-package.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows and PowerShell tools are mentioned first and in greater detail, with explicit PowerShell cmdlet references and examples. Linux instructions are present but less detailed, and Linux-specific steps are often described generically or as manual file deletions, while Windows users are given dedicated PowerShell cmdlets. The overall structure and example order favor Windows and PowerShell, creating friction for Linux users.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., shell scripts) for unregistering nodes and deleting configurations, not just manual file deletion.
  • Mention Linux tools and commands (such as omicli, systemctl, or relevant DSC/OMI utilities) where appropriate, and provide step-by-step instructions similar to the PowerShell examples.
  • Ensure that Linux instructions are as detailed and explicit as Windows/PowerShell instructions, including troubleshooting tips and automation options.
  • Present Windows and Linux examples side-by-side or in parallel tabs, rather than listing Windows/PowerShell first.
  • Include references to Linux documentation and community resources for DSC management.
GitHub Create Pull Request
Automation Quickstart - Enable managed identities for your Automation account using the Azure portal ...cles/automation/quickstarts/enable-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page is primarily focused on using the Azure portal UI, which is cross-platform. However, the only next step tutorial linked is for creating an Automation PowerShell runbook, which is Windows-centric. There are no examples or references to Linux shell scripting, Bash, or cross-platform automation approaches. The documentation implicitly prioritizes Windows/PowerShell patterns over Linux equivalents.
Recommendations
  • Include links or examples for creating Automation runbooks using Python or Bash, which are more common on Linux/macOS.
  • Add a 'Next steps' link to a tutorial for Linux users, such as 'Create Automation Python runbook using managed identity'.
  • Explicitly mention that Automation runbooks can be authored in multiple languages and provide parity in guidance.
  • Where PowerShell is referenced, clarify cross-platform support or alternatives for Linux/macOS users.
GitHub Create Pull Request
Automation Troubleshoot extension-based Hybrid Runbook Worker issues in Azure Automation .../troubleshoot/extension-based-hybrid-runbook-worker.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation generally provides parity between Windows and Linux troubleshooting steps for Hybrid Runbook Workers, including separate sections and commands for each OS. However, there is a notable Windows bias in several areas: Windows examples and tools (such as PowerShell scripts and registry edits) are often presented first, and some troubleshooting scenarios (e.g., registry permissions, event logs, UAC issues) are Windows-specific with no Linux equivalent or guidance. Windows-centric terminology (e.g., 'Microsoft-SMA event logs', 'Win32 Process') is used throughout, and some references (like log collection scripts) are PowerShell-heavy, with Linux alternatives mentioned but less detailed. In some scenarios, only Windows instructions are given, or Windows tools are referenced before their Linux counterparts.
Recommendations
  • Alternate the order of Windows and Linux instructions to avoid always presenting Windows first.
  • Where Windows-specific troubleshooting (e.g., registry, event logs, UAC) is described, provide Linux equivalents or explicitly state if not applicable.
  • Ensure Linux troubleshooting tools and scripts are described with equal detail and clarity as Windows/PowerShell tools.
  • Add more Linux-specific troubleshooting scenarios, such as SELinux/AppArmor issues, systemd service failures, or log analysis tips.
  • Use OS-neutral terminology where possible, and clarify when a step is OS-specific.
  • Provide references to Linux documentation or community resources for deeper troubleshooting.
GitHub Create Pull Request
Automation Use Source Control Integration in Azure Automation ...main/articles/automation/source-control-integration.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong bias toward Windows and PowerShell. All command-line examples use Azure PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux/macOS workflows. Instructions for assigning roles and configuring source control are exclusively provided for PowerShell, and references to file encoding issues link to PowerShell/VSCode documentation. There are no Linux/macOS-specific instructions or parity examples, and Windows tools and patterns are presented first and exclusively.
Recommendations
  • Add equivalent examples using Azure CLI and Bash for all PowerShell command-line instructions, especially for role assignment and source control configuration.
  • Explicitly state platform compatibility for PowerShell cmdlets and clarify if they can be run on Linux/macOS (e.g., via PowerShell Core).
  • Provide guidance for Linux/macOS users on prerequisites, authentication, and troubleshooting, including common editors and encoding issues.
  • Include links to cross-platform documentation and tools where available.
  • Reorder or balance examples so that Windows and Linux/macOS instructions are presented with equal prominence.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation managed identity issues ...n/articles/automation/troubleshoot/managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 PowerShell cmdlets (e.g., Connect-AzAccount, Get-AzVM, Invoke-RestMethod) and provides only PowerShell-based troubleshooting scripts and examples. There are no Bash, Azure CLI, or Linux/macOS shell equivalents, nor are cross-platform patterns mentioned. The examples and troubleshooting steps assume the reader is using Windows tooling, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all PowerShell cmdlets and scripts.
  • Explicitly mention that the steps apply to both Windows and Linux/macOS Automation accounts, and clarify any platform-specific differences.
  • Provide troubleshooting scripts in Bash or Python for Linux/macOS users.
  • List cross-platform tools and commands before or alongside Windows/PowerShell examples.
  • Include notes on how to run these commands on Linux/macOS, including installation instructions for required modules.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias by exclusively using PowerShell for all code examples, setup instructions, and runbook creation steps. Prerequisites and links reference Windows-centric resources (e.g., 'quick-create-powershell' for VMs, Azure Az PowerShell module), and there are no Bash, CLI, or Linux/macOS-specific instructions or examples. The workflow assumes users are familiar with PowerShell and does not mention or demonstrate how to accomplish the same tasks using Azure CLI, Bash, or other cross-platform tools.
Recommendations
  • Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and work on Linux/macOS.
  • Include instructions for creating and managing Automation runbooks using Bash or shell scripts, where supported.
  • Reference Linux/macOS VM creation guides alongside Windows guides in prerequisites.
  • Clarify which steps are platform-agnostic (e.g., portal actions) and which require adaptation for non-Windows environments.
  • Add notes or links for installing and using Azure CLI on Linux/macOS.
  • Consider providing sample runbooks written in Python, which is supported in Azure Automation and is cross-platform.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a notable Windows bias, primarily through exclusive use of PowerShell scripts and workflows for migration tasks, with no mention of Bash, Python, or Linux-native alternatives. All scripting examples and instructions are centered on PowerShell, a Windows-centric tool, and references to installation steps and hybrid worker management default to Windows tabs and links. Linux users are left without direct guidance or parity in automation and migration workflows.
Recommendations
  • Provide equivalent Bash or Python scripts for asset migration, or document how Linux users can perform these tasks using cross-platform tools (e.g., Azure CLI, REST API).
  • Include Linux/macOS-specific instructions and examples alongside PowerShell, especially for runbook migration and hybrid worker setup.
  • Ensure documentation tabs and links offer Linux-first or cross-platform options, not just Windows.
  • Clarify which steps are platform-agnostic and which require Windows-specific tooling, and suggest alternatives for Linux users where possible.
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-13 06:17
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 biased toward Windows and PowerShell usage. Nearly all CLI examples use PowerShell cmdlets, with no Bash, Azure CLI, or Linux shell equivalents provided. Even REST API and ARM template sections rely on PowerShell for invocation and authentication. The order of presentation consistently puts PowerShell/Windows-centric approaches first, and there is no mention of Linux-specific tooling or cross-platform alternatives. Python is only briefly mentioned for runbooks, but not for setup or deployment tasks.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell cmdlets, especially for resource creation, role assignment, and identity management.
  • Provide Bash or shell script examples for REST API calls, using curl or httpie, and show how to obtain access tokens on Linux/macOS.
  • Include instructions for deploying ARM templates using Azure CLI (az deployment group create) and not just PowerShell.
  • Clearly indicate which steps and scripts are cross-platform and which are Windows-specific.
  • Consider reordering examples so that platform-neutral or cross-platform methods (portal, REST API, ARM template, Azure CLI) are presented before PowerShell.
  • Add troubleshooting and verification steps for Linux/macOS environments.
GitHub Create Pull Request
Automation Manage connections in Azure Automation ...lob/main/articles/automation/automation-connections.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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. PowerShell (and Az module) examples are provided extensively and are presented before Python/Linux alternatives. The creation and management of connections are described primarily through PowerShell cmdlets, with no mention of equivalent Bash, Azure CLI, or Linux-native workflows. The 'Create a new connection' section only covers PowerShell and portal methods, omitting Linux/macOS command-line approaches. The Python section is present but secondary, and no Linux shell or Azure CLI examples are given.
Recommendations
  • Add Azure CLI examples for creating and managing connections, especially for Linux/macOS users.
  • Include Bash or shell script samples for common connection management tasks.
  • Present examples in a more platform-neutral order (e.g., CLI, PowerShell, Python), or use tabs for each platform.
  • Explicitly mention cross-platform compatibility and any platform-specific limitations.
  • Clarify whether PowerShell examples can be run on PowerShell Core on Linux/macOS, or if they are Windows-only.
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-13 06:17
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. Most automation and key management examples use Azure PowerShell, with no CLI (az) or Bash/Linux shell equivalents provided. PowerShell runbooks and tutorials are emphasized and listed first, while Python is mentioned only as an alternative. There are no explicit instructions or examples for Linux/macOS users, and Windows-centric tools (PowerShell) are referenced exclusively for command-line operations.
Recommendations
  • Add equivalent Azure CLI (az) commands for key rotation and other management tasks alongside PowerShell examples.
  • Provide Bash or shell script examples for Linux/macOS users where applicable.
  • Reorder tutorial links to present Python and PowerShell examples equally, or clarify cross-platform options.
  • Explicitly state that PowerShell Core is available on Linux/macOS, and link to installation instructions.
  • Include notes or sections addressing Linux/macOS users, highlighting any platform-specific considerations.
GitHub Create Pull Request
Automation Configure data based on STIG for Azure Automation State Configuration ...tomation/automation-dsc-configuration-based-on-stig.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 and PowerShell, with all examples and tooling references centered around Windows PowerShell DSC and the PowerSTIG project. There is no mention of Linux/macOS equivalents, and Linux onboarding is only referenced via a link, not in the main content. The article assumes familiarity with Windows tooling and does not provide guidance for Linux users.
Recommendations
  • Include explicit examples and instructions for configuring Linux servers using Azure Automation State Configuration.
  • Mention and link to Linux DSC resources, such as the OMI-based DSC agent for Linux.
  • Clarify which features are Windows-only and provide Linux alternatives where possible.
  • Add a section describing how Linux users can achieve STIG compliance using Azure Automation, including any limitations.
  • Present onboarding steps for both Windows and Linux side-by-side, rather than referencing Linux only in a link.
GitHub Create Pull Request
Automation Integrate Azure Automation State Configuration with Azure Monitor Logs ...main/articles/automation/automation-dsc-diagnostics.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 biased towards Windows, with all code examples and instructions using PowerShell and Az PowerShell modules. There are no CLI, Bash, or Linux/macOS-specific instructions or examples. The prerequisites and tooling (e.g., xDscDiagnostics, Az PowerShell) are Windows-centric, and there is no mention of Linux alternatives or parity. The guidance assumes the user is on a Windows environment, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent instructions and examples using Azure CLI (az) and Bash scripts for Linux/macOS users.
  • Explicitly mention platform compatibility for each tool/module, and provide alternatives where possible.
  • Include notes or sections for Linux/macOS users, clarifying any limitations or differences in workflow.
  • If PowerShell Core is supported on Linux/macOS, clarify usage and provide cross-platform examples.
  • Reference Linux onboarding and management documentation if available, or clarify end-of-life/retirement status for Linux DSC.
GitHub Create Pull Request
Automation Configure data at scale for Azure Automation State Configuration ...cles/automation/automation-dsc-config-data-at-scale.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 and PowerShell, with all examples and instructions referencing Windows PowerShell DSC. There is no mention of Linux/macOS equivalents, nor are there examples or guidance for non-Windows platforms. The prerequisites and next steps are all Windows-centric, and Linux users are only referenced in a link, not in the main content.
Recommendations
  • Add explicit instructions and examples for configuring data at scale using Linux/macOS-compatible DSC implementations (e.g., cross-platform PowerShell, Open Management Infrastructure).
  • Clarify which steps are applicable to Linux/macOS and provide alternative commands or tools where needed.
  • Include references to Linux DSC onboarding and configuration in the main body, not just as a link.
  • Highlight any platform limitations or differences up front, so users know what to expect.
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-13 06:17
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 explicit guidance or examples for Linux/macOS users. All instructions and references are centered around PowerShell, with no mention of cross-platform alternatives or compatibility considerations for non-Windows environments. The introductory section and steps assume a Windows context, and links point to Windows-centric resources.
Recommendations
  • Explicitly state whether the CompositeResource module and related tooling work on PowerShell Core (cross-platform) and/or Linux/macOS.
  • Provide examples or instructions for running the process on Linux/macOS, including any required dependencies or differences.
  • Clarify any limitations or required adaptations for non-Windows platforms, such as MOF file handling or DSC support.
  • Include links to documentation about Linux DSC agent onboarding and configuration.
  • Add a section comparing Windows and Linux workflows for composite resource creation and usage.
GitHub Create Pull Request
Automation Enable Azure Automation State Configuration .../main/articles/automation/automation-dsc-onboarding.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Windows and PowerShell examples are presented first and in greater detail, with Linux instructions often relegated to later sections or presented as addenda. Most configuration and onboarding steps rely on PowerShell scripts and Windows-specific tooling (WMF 5, PowerShell DSC cmdlets), with Linux instructions sometimes referencing Windows tools for initial setup. Linux examples are less detailed, and some advanced scenarios (custom metaconfigurations, remote onboarding) require Windows-based tools or PowerShell, creating friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS examples alongside Windows/PowerShell instructions, not just as addenda.
  • Expand Linux-specific guidance, including native Linux commands and scripts for all major steps (e.g., generating and applying metaconfigurations).
  • Document Linux/macOS workflows that do not require access to Windows or PowerShell tools.
  • Clarify which steps are platform-specific and offer parity in tooling or alternatives where possible.
  • Include troubleshooting and status-checking instructions for Linux nodes, not just Windows.
  • Where PowerShell is required, note any Linux-compatible options (e.g., PowerShell Core) or provide equivalent bash/python scripts.
GitHub Create Pull Request
Automation Edit textual runbooks in Azure Automation ...articles/automation/automation-edit-textual-runbook.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 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 parity is missing.
Recommendations
  • Add examples using PowerShell Core (pwsh) with cross-platform file paths (e.g., /home/user/runbooks).
  • Clarify that Az PowerShell module can be used on Linux/macOS, and provide instructions for those platforms.
  • Include Azure CLI examples for runbook management, where possible.
  • Explicitly mention any platform limitations or differences in the editor and cmdlet usage.
  • Reorder or balance examples so Linux/macOS usage is shown alongside Windows.
GitHub Create Pull Request
Automation Azure Automation network configuration details ...rticles/automation/automation-network-configuration.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references Windows-specific DSC resources (e.g., WaitFor resources in the /powershell/dsc/reference/resources/windows/waitForAllResource link) when discussing node-to-node communication, without mentioning Linux equivalents or cross-platform alternatives. Windows terminology and links appear first and exclusively in the context of DSC resource examples.
Recommendations
  • Include references to Linux DSC resources and documentation, such as links to cross-platform DSC modules or Linux-specific resources.
  • Clarify whether the guidance applies equally to Linux nodes, and provide examples or notes for Linux/macOS environments where applicable.
  • Add explicit mention of any differences in network configuration or resource requirements for Linux/macOS Hybrid Runbook Workers and State Configuration nodes.
  • Where Windows-specific resources are mentioned, provide Linux alternatives or note if none exist.
GitHub Create Pull Request
Automation Runbook authoring using VS Code in Azure Automation ...in/articles/automation/automation-runbook-authoring.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows operating systems are listed first in the supported OS matrix, and examples for directory paths use Windows-style (C:\abc) exclusively. The documentation focuses heavily on PowerShell, with specific mention of Windows PowerShell 5.1 and PowerShell Core, but provides no Linux/macOS-specific usage examples, troubleshooting, or directory path conventions. Debugging support is only described for PowerShell, with Python debugging relegated to a generic recommendation to use a debugger extension, without platform-specific guidance.
Recommendations
  • Include Linux/macOS directory path examples alongside Windows (e.g., /home/user/abc).
  • Provide explicit instructions or screenshots for changing directories and configuring settings on Linux/macOS.
  • Add troubleshooting tips or notes for Linux/macOS users, especially regarding PowerShell and Python environment setup.
  • Clarify any platform-specific limitations or differences in feature support.
  • Balance the order of OS mentions and examples so Linux/macOS are not always listed after Windows.
  • Offer parity in debugging guidance for Python runbooks on Linux/macOS.
GitHub Create Pull Request
Automation Runbook execution in Azure Automation ...in/articles/automation/automation-runbook-execution.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 runbooks and Windows-centric tools and patterns. All code examples use PowerShell syntax, and references to modules, environment variables, and file paths are Windows-specific (e.g., C:\temp, $env:TEMP). Windows tools like WinSCP.exe and IIS are mentioned as examples, with no Linux equivalents or cross-platform alternatives provided. There are no Bash, Python, or Linux shell examples, and Linux-specific considerations are only briefly mentioned in passing (e.g., Defender for Cloud constraints).
Recommendations
  • Provide equivalent Linux/macOS examples for runbook scripting, such as Bash or Python runbooks.
  • Include Linux-specific file paths and environment variable usage (e.g., /tmp instead of C:\temp or $env:TEMP).
  • Mention Linux tools and modules (e.g., scp, Apache/Nginx administration) alongside Windows tools like WinSCP and IIS.
  • Clarify which features and modules are cross-platform, and explicitly note any Windows-only limitations.
  • Add examples and guidance for managing Linux resources and handling Linux-specific errors or authentication scenarios.
GitHub Create Pull Request
Automation Azure Automation FAQ ...e-docs/blob/main/articles/automation/automation-faq.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 (e.g., /usr/bin/python3, $PATH usage) are not mentioned or illustrated. Windows Hybrid Runbook Worker configuration is explained first and in more depth, with Linux only referenced briefly. No Linux-specific examples or instructions are provided for Python interpreter selection or environment variable setup.
Recommendations
  • Add explicit Linux examples for configuring Python interpreter selection, including environment variable usage and typical Linux file paths (e.g., /usr/bin/python3).
  • Describe how Linux Hybrid Runbook Workers locate Python interpreters, including any differences from Windows.
  • Ensure that instructions and examples for both platforms are presented in parallel, or alternate which is shown first.
  • Include troubleshooting tips for Linux users similar to those provided for Windows.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows and PowerShell tools are referenced first and more frequently, especially in backup and retention sections. Linux guidance is present but less detailed, and Linux-specific examples are limited to TLS configuration. Several cmdlets and procedures are described only for Windows/PowerShell, with no direct Linux or cross-platform alternatives provided.
Recommendations
  • Provide Linux/macOS equivalents for PowerShell cmdlets, such as CLI or REST API examples for exporting runbooks and DSC configurations.
  • Include Linux-first or side-by-side examples for asset management and backup procedures.
  • Reference cross-platform tools (e.g., Azure CLI, az automation) before or alongside Windows/PowerShell tools.
  • Clarify which procedures are platform-agnostic and which are Windows-specific.
  • Expand Linux guidance beyond TLS configuration, especially in backup and retention sections.
GitHub Create Pull Request
Automation Migrate from Orchestrator to Azure Automation (Beta) ...ticles/automation/automation-orchestrator-migration.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 and PowerShell, with all examples, tooling, and migration steps centered around Windows technologies. There is no mention of Linux/macOS equivalents, nor are there examples or guidance for users on those platforms. The migration process assumes the use of Windows PowerShell, Windows file paths, and Windows-based modules and tools, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent instructions and examples for Linux/macOS users, including how to run PowerShell Core (pwsh) on those platforms.
  • Clarify whether the migration toolkit and Runbook Converter can be used on Linux/macOS, and if not, offer alternatives or workarounds.
  • Use platform-neutral file path examples or show both Windows and Linux/macOS paths.
  • Document any limitations or requirements for Linux/macOS users explicitly.
  • Include notes about PowerShell Core compatibility for cmdlets and modules mentioned.
  • If tools are Windows-only, suggest cross-platform alternatives or containerized approaches.
GitHub Create Pull Request
Automation Use Azure Automation runbooks and modules in PowerShell Gallery ...main/articles/automation/automation-runbook-gallery.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All examples and workflows focus exclusively on PowerShell and Windows-centric tools, with no mention of Linux/macOS equivalents or cross-platform considerations. Scenarios and sample runbooks reference Windows Azure VMs and PowerShell modules, and there are no Bash, Python, or Linux-native instructions or examples. The documentation assumes users are familiar with PowerShell and Windows conventions, making it less accessible for Linux/macOS users.
Recommendations
  • Include examples and instructions for Linux/macOS users, such as using Bash or Python runbooks.
  • Highlight cross-platform compatibility of Azure Automation and clarify which features are Windows-only.
  • Provide sample runbooks for Linux Azure VMs (e.g., file copy to/from Linux VMs).
  • Add guidance on managing modules and runbooks with Linux-native tools and workflows.
  • Explicitly state any limitations or differences for non-Windows platforms.
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-13 06:17
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, with all examples and error handling patterns described in terms of PowerShell cmdlets and syntax. There is no mention of Linux or cross-platform alternatives, nor are Bash or Python examples provided. Windows tools and terminology (e.g., PowerShell, Write-Warning, Start-AzVM) are used exclusively, and no Linux/macOS-specific guidance is offered.
Recommendations
  • Add equivalent examples using Bash, Python, or other supported languages for graphical runbooks.
  • Clarify whether graphical runbooks and error handling features are available and work identically on Linux/macOS hybrid workers.
  • Mention cross-platform cmdlets or automation modules if available.
  • Provide guidance on handling errors in non-PowerShell activities (e.g., Bash, Python) within graphical runbooks.
  • Explicitly state any platform limitations or differences in error handling behavior.
GitHub Create Pull Request
Automation Azure Automation Runbook Types ...b/main/articles/automation/automation-runbook-types.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell (a Windows-centric technology) is presented first and in greatest detail, with multiple sections and examples focused on Windows PowerShell and its workflows. Many examples and known issues reference Windows file paths (e.g., C:\modules), environment variables (e.g., TEMP), and Windows-specific behaviors. Linux support is mentioned only in passing, with no Linux-specific examples, troubleshooting, or guidance. Python runbooks mention Linux only briefly, and graphical runbooks are explicitly unsupported on Linux Hybrid Runbook Workers. There are no code samples or instructions tailored for Linux/macOS users.
Recommendations
  • Add Linux/macOS-specific examples for PowerShell (especially for Hybrid Runbook Workers), including file paths, environment variables, and troubleshooting steps.
  • Explicitly document differences and limitations for Linux Hybrid Runbook Workers, including supported features and workarounds.
  • Provide parity in examples: for every Windows-centric example (e.g., C:\modules), include the equivalent Linux/macOS example (e.g., /usr/src/PSModules).
  • Clarify which features/tools are Windows-only and suggest alternatives or workarounds for Linux/macOS users.
  • Expand Python runbook documentation to include more Linux-specific guidance, especially for package management and environment setup.
  • Reorder sections or provide parallel guidance so Linux/macOS users do not have to sift through Windows-specific content to find relevant information.
GitHub Create Pull Request
← Previous Page 7 of 15 Next →