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 351-375 of 982 flagged pages
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/overview.md ...s/azure-docs/blob/main/articles/automation/overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias by emphasizing PowerShell and Windows-centric tools and patterns. PowerShell is mentioned repeatedly as the primary language for runbooks and configuration management (DSC), with only brief references to Python. The State Configuration feature is described exclusively in terms of PowerShell DSC, with no mention of Linux-native equivalents like Ansible or Chef. The modules gallery and shared resources focus on PowerShell Gallery integration, and examples of automation scenarios (e.g., managing SQL Server, Active Directory, SharePoint) are Windows-centric. Linux support is acknowledged, but concrete Linux-specific examples, tools, or patterns are missing.
Recommendations
  • Provide Linux-specific examples for runbooks, such as using Bash, Python, or other Linux-native scripting languages.
  • Mention and document configuration management tools popular in Linux environments (e.g., Ansible, Chef, Puppet) and how they can be integrated with Azure Automation.
  • Expand the discussion of the Modules Gallery to include Python packages and other Linux-relevant resources, not just PowerShell Gallery.
  • Include automation scenarios that are relevant to Linux workloads (e.g., managing Apache, Nginx, MySQL, systemd services).
  • Ensure that documentation for features like State Configuration covers both Windows (PowerShell DSC) and Linux (cross-platform DSC, or alternatives) use cases.
  • Balance references to Windows-centric services (SQL Server, Active Directory) with Linux equivalents (PostgreSQL, LDAP, etc.).
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/manage-runtime-environment.md ...main/articles/automation/manage-runtime-environment.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 clear bias toward Windows and PowerShell environments. Most examples, screenshots, and instructions focus on PowerShell, with repeated references to PowerShell modules, cmdlets, and the PowerShell Gallery. Windows/PowerShell patterns and tools (e.g., Az PowerShell package, Get-Module) are mentioned and illustrated exclusively or before their Linux/Python equivalents. Linux-specific details, such as package formats or Python environments, are only briefly mentioned and lack parity in example depth, tooling, and screenshots.
Recommendations
  • Provide equivalent, detailed examples for Python runbooks, including REST API payloads and portal screenshots.
  • Include Linux-specific instructions and tooling, such as using pip, .whl files, and Linux-based package management for Python environments.
  • Show how to view installed Python packages in a runbook, similar to the PowerShell Get-Module example.
  • Balance references to PowerShell Gallery with Python Package Index (PyPI) and clarify how to upload Python packages from PyPI.
  • Add troubleshooting and management examples for Python runbooks and Linux-based runtime environments.
  • Ensure that both PowerShell and Python/Linux options are presented equally in all sections, not just as afterthoughts or notes.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md ...g-agent-based-hybrid-worker-to-extension-based-workers.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows and PowerShell examples are presented first and in greater detail, especially in Bicep and ARM template sections, which only show Windows VM creation and extension installation. PowerShell is emphasized as the primary automation tool, with Linux alternatives (such as Bash or cloud-init) missing. The extension installation examples and resource definitions are Windows-centric, and Linux-specific instructions or examples for extension deployment are absent or minimal. Additionally, folder permissions and requirements are described in Windows terms, with Linux equivalents omitted.
Recommendations
  • Provide parallel Linux examples for Bicep and ARM templates, including VM creation and extension installation using 'HybridWorkerForLinux'.
  • Add Linux-specific PowerShell or Bash scripts for extension installation and management.
  • Include Linux folder permission requirements and management steps, similar to the Windows section.
  • Ensure that CLI, REST API, and automation examples explicitly show both Windows and Linux extension types and settings.
  • Present Windows and Linux instructions/examples in parallel, rather than listing Windows first or exclusively.
  • Reference Linux-specific documentation and troubleshooting steps where appropriate.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/migrate-run-as-accounts-managed-identity.md ...automation/migrate-run-as-accounts-managed-identity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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-based automation, with all code samples, migration steps, and graphical runbook instructions using PowerShell cmdlets and patterns. There is no mention of Linux-native tools, Bash, CLI, or cross-platform scripting alternatives. Windows-centric terminology and tools (e.g., PowerShell, AzureRM/Az modules, graphical runbooks) are used exclusively and presented first, with no parity for Linux or non-Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands for authentication and resource management, which are cross-platform and commonly used on Linux.
  • Include Bash script samples for managed identity authentication and resource access.
  • Clarify which steps and scripts are platform-agnostic and which are Windows/PowerShell-specific.
  • Provide guidance for users running hybrid workers on Linux VMs, including how to authenticate with managed identities using non-PowerShell tools.
  • Mention and link to documentation for automating Azure resources from Linux environments.
  • Explicitly state platform requirements or limitations for each approach, and offer alternatives where possible.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/python-3-packages.md ...ocs/blob/main/articles/automation/python-3-packages.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several areas. Windows and Windows tools (PowerShell cmdlets) are presented first or exclusively, especially for Python 3.8 scenarios. Linux instructions/examples are only provided for Python 3.10, and there is no parity for PowerShell cmdlets or package management examples for Linux environments. The guidance for generating wheel files is split by OS, but Windows is prioritized for Python 3.8, and Linux for Python 3.10, with no cross-OS examples for each version. There are no Linux CLI or shell script equivalents for the PowerShell cmdlets, and the documentation does not mention Linux tools or patterns for managing packages on Hybrid Runbook Workers.
Recommendations
  • Provide Linux-based examples for Python 3.8 package preparation and import, including instructions for generating wheel files on Linux for Python 3.8.
  • Include cross-platform CLI alternatives (such as Azure CLI or REST API examples) alongside PowerShell cmdlets for package management tasks.
  • Present Windows and Linux instructions in parallel, rather than prioritizing one OS over the other.
  • Add guidance for managing Python packages on Linux Hybrid Runbook Workers, including relevant tools and patterns.
  • Explicitly mention OS requirements and limitations for each scenario, and clarify when Windows or Linux is required or preferred.
  • Where PowerShell is used, provide equivalent bash/shell script examples for Linux users.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/create-azure-automation-account-portal.md .../quickstarts/create-azure-automation-account-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on using the Azure portal (web UI) for creating an Automation account, which is cross-platform. However, the 'Next steps' section directs users to a PowerShell runbook tutorial, implying a Windows-centric workflow. There are no references to Linux tools, Bash, or cross-platform scripting alternatives. The absence of Linux or Bash examples, and the prioritization of PowerShell, suggest a Windows-first bias.
Recommendations
  • Include links to tutorials for creating Automation accounts using Azure CLI and Bash scripts, which are cross-platform and widely used on Linux.
  • Add examples or references for creating and managing Automation accounts using REST API or ARM templates, which are OS-agnostic.
  • In the 'Next steps' section, provide parity by linking to both PowerShell and Bash/Python runbook tutorials.
  • Explicitly mention that the Azure portal is accessible from any OS/browser to reinforce cross-platform accessibility.
  • Where scripting is referenced, clarify which options are available for Linux users and provide sample commands.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/dsc-configuration.md ...n/articles/automation/quickstarts/dsc-configuration.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. The workflow is centered around PowerShell DSC, with all code examples in PowerShell, and references to Windows-centric tools and patterns (e.g., MOF, PowerShell Gallery, Chocolatey). Linux support is explicitly noted as retired, and while a LAMP stack is configured, it is done via PowerShell DSC resources rather than native Linux tooling. There are no examples using native Linux configuration management tools or command-line patterns.
Recommendations
  • Provide parity by including examples for Linux VMs using native Linux configuration management tools (e.g., Ansible, Chef, Puppet) or Azure's guest configuration feature for Linux.
  • Offer alternative workflows for Linux users, such as using cloud-init or shell scripts for configuration.
  • If PowerShell DSC is no longer supported for Linux, clearly direct Linux users to the recommended replacement (e.g., Azure Policy guest configuration) and provide a step-by-step example.
  • Avoid referencing Windows-specific tools (e.g., Chocolatey) as the next step for all users; suggest Linux equivalents (e.g., apt, yum, dnf) where appropriate.
  • Add a section summarizing the differences in support and recommended approaches for Windows vs. Linux, with links to relevant documentation for each.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/runbook-input-parameters.md ...b/main/articles/automation/runbook-input-parameters.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page is heavily focused on PowerShell and Windows-centric tooling and patterns. Most examples, code snippets, and workflows are presented using PowerShell, PowerShell Workflow, and graphical runbooks (which are also PowerShell-based). Windows tools and terminology (e.g., PowerShell cmdlets, .NET types, C# SDK) are used exclusively or described first, with little to no mention of Linux-native equivalents or cross-platform alternatives. There are no examples of starting runbooks from Linux shells (e.g., Bash), nor is there guidance for using Azure CLI or REST API from Linux environments. Python runbooks are mentioned, but only briefly and without parity in example depth.
Recommendations
  • Add examples for starting runbooks using Azure CLI, which is cross-platform and commonly used on Linux.
  • Provide Bash shell examples for invoking REST API to start runbooks and pass parameters.
  • Include guidance for Linux users on prerequisites and environment setup for Azure Automation.
  • Expand Python runbook sections with detailed parameter usage and invocation examples, matching the depth of PowerShell coverage.
  • Clarify which features and patterns are cross-platform, and highlight any Windows-specific limitations.
  • Where PowerShell is used, note its availability on Linux and macOS, and provide examples for PowerShell Core (pwsh) on non-Windows systems.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/shared-resources/certificates.md ...n/articles/automation/shared-resources/certificates.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 strong bias toward Windows and PowerShell. All command-line examples use PowerShell cmdlets, which are native to Windows. Windows-centric tools (e.g., Add-AzureCertificate, PowerShell modules) are referenced exclusively and before any cross-platform alternatives. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or OpenSSL to manage certificates. The Python examples are limited to runbooks and do not address certificate management outside the Azure Automation context. There is no mention of Linux-compatible workflows or tools for certificate creation, upload, or management.
Recommendations
  • Add equivalent Azure CLI examples for certificate management, which are cross-platform and work on Linux, macOS, and Windows.
  • Include Bash or shell script examples for uploading and managing certificates, using tools like OpenSSL for certificate creation.
  • Reference Linux-compatible certificate providers and clarify any platform-specific requirements (e.g., alternatives to 'Microsoft Enhanced RSA and AES Cryptographic Provider').
  • Explicitly state whether PowerShell Core (pwsh) on Linux/macOS is supported and provide examples if so.
  • Balance the ordering of examples so that cross-platform tools (Azure CLI, REST API) are presented alongside or before Windows-specific tools.
  • Add troubleshooting guidance for Linux users, including common issues with certificate formats and permissions.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/shared-resources/modules.md ...b/main/articles/automation/shared-resources/modules.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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, with a heavy focus on PowerShell modules, cmdlets, and workflows. Examples and instructions are almost exclusively centered on Windows PowerShell and Azure PowerShell modules, with little to no coverage of Linux-specific workflows or tools. Internal cmdlets and features are noted as unavailable on Linux Hybrid Runbook Workers, but Linux alternatives or parity are not discussed. Python support is mentioned briefly, but without examples or guidance comparable to the PowerShell coverage.
Recommendations
  • Add equivalent Linux and cross-platform examples for module management, including CLI (az), Bash, or Python workflows.
  • Explicitly document limitations and alternatives for Linux Hybrid Runbook Workers, and provide guidance for achieving similar outcomes on Linux.
  • Include instructions and examples for managing Python modules/packages in Automation, with parity to PowerShell module instructions.
  • Highlight cross-platform capabilities and note which features are Windows-only, suggesting workarounds or alternatives for Linux users.
  • Provide a comparative table or section listing supported features and modules for both Windows and Linux Hybrid Runbook Workers.
  • Reference Linux-specific documentation or best practices for Azure Automation where relevant.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/remove-user-assigned-identity.md ...n/articles/automation/remove-user-assigned-identity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 strong Windows bias by providing only PowerShell-based command-line examples and instructions, referencing Windows-centric tools (PowerShell cmdlets) throughout, and omitting equivalent Linux shell (bash/CLI) examples. REST API usage is also shown exclusively via PowerShell, with no mention of curl, az CLI, or other cross-platform tools. The structure and order of examples prioritize Windows tooling and patterns, leaving Linux users without direct guidance.
Recommendations
  • Add Azure CLI (az) examples for all operations, including removing managed identities and verifying results.
  • Provide REST API invocation examples using curl or httpie, which are standard on Linux/macOS.
  • Include bash shell script snippets alongside PowerShell, especially for variable assignment and API calls.
  • Mention that PowerShell Core is cross-platform, but clarify usage differences if any.
  • Reorder sections or add parallel instructions so Linux and Windows users are equally supported.
  • Reference Linux tools and patterns (e.g., jq for JSON parsing) where appropriate.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/runtime-environment-overview.md ...in/articles/automation/runtime-environment-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias by focusing predominantly on PowerShell as the primary scripting language, referencing multiple PowerShell versions and workflows, and highlighting Azure CLI usage specifically within PowerShell environments. There is a lack of Linux-oriented examples, tools, or explicit parity for Python or Bash scripting, and Windows-centric terminology (e.g., *.dll* files, PowerShell modules) is used throughout. Linux equivalents and usage patterns are not mentioned or are secondary.
Recommendations
  • Provide explicit examples and guidance for Python runbooks, including package management and runtime configuration.
  • Include references to Linux-native tools and scripting environments, such as Bash, and clarify their support or limitations within Azure Automation.
  • Balance the order of presentation so that Python and Linux options are described alongside or before PowerShell/Windows options.
  • Add documentation or links for managing Python packages (e.g., pip) and clarify how Linux users can leverage Azure CLI outside PowerShell environments.
  • Use neutral terminology for assemblies and packages, avoiding Windows-specific language where possible.
  • Offer cross-platform usage scenarios and troubleshooting tips for both Windows and Linux users.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/shared-resources/credentials.md ...in/articles/automation/shared-resources/credentials.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 strong Windows bias by focusing almost exclusively on PowerShell cmdlets and workflows, which are native to Windows environments. All code examples for credential management are provided in PowerShell, with no equivalent Bash, CLI, or Linux-native examples. Windows tools and terminology (such as 'Windows PowerShell', 'PSCredential', and PowerShell modules) are referenced throughout, and the process for creating credentials via command line is only described using Windows PowerShell. Linux or cross-platform alternatives are not mentioned or demonstrated, except for Python runbook examples, which are not sufficient for parity.
Recommendations
  • Add Azure CLI examples for credential management tasks, demonstrating how to create, retrieve, and use credentials from Linux or macOS environments.
  • Include Bash or shell script samples for common credential operations, especially for users who automate with Linux-based agents.
  • Clarify which features and cmdlets are cross-platform and which are Windows-specific, and provide guidance for Linux users where PowerShell is not available.
  • Mention and demonstrate usage of PowerShell Core (pwsh), which is cross-platform, and specify any differences or limitations compared to Windows PowerShell.
  • Provide a section or table comparing Windows and Linux approaches to Azure Automation credential management, highlighting parity and gaps.
  • Reference relevant documentation for Linux users, such as using managed identities or Azure Key Vault with automation from non-Windows environments.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/shared-resources/schedules.md ...main/articles/automation/shared-resources/schedules.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 providing PowerShell examples and cmdlets, which are native to Windows environments. There are no equivalent examples or guidance for Linux users (e.g., Bash, Azure CLI), and Windows-centric tools and patterns (PowerShell, Az modules) are mentioned first and exclusively throughout the page. This limits accessibility and parity for users working on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all schedule management operations (create, link, disable, remove schedules).
  • Include Bash script samples where appropriate, especially for ARM template deployments.
  • Explicitly mention cross-platform compatibility of Az modules and clarify how Linux/macOS users can install and use them.
  • Provide a section or table comparing PowerShell and Azure CLI commands for common schedule management tasks.
  • Ensure that references to tools and patterns do not assume a Windows environment; highlight platform-agnostic approaches where possible.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/shared-resources/variables.md ...main/articles/automation/shared-resources/variables.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 strong Windows bias by focusing almost exclusively on PowerShell and Windows-centric tools for managing Azure Automation variables. Examples and instructions are given for Windows PowerShell and Az PowerShell cmdlets, with no mention of Bash, CLI, or Linux-native scripting alternatives. The documentation refers to Windows Hybrid Runbook Worker and Windows PowerShell as the primary means for advanced variable manipulation, and complex type handling is described only in the context of PowerShell. Python examples are provided, but there are no Linux shell or Azure CLI examples, and PowerShell is presented first and in greater detail.
Recommendations
  • Add equivalent examples using Azure CLI (az automation variable ...) for variable management, including creation, retrieval, and deletion.
  • Include Bash or shell script examples for accessing variables in runbooks executed on Linux Hybrid Runbook Workers.
  • Clarify which features and cmdlets are available cross-platform, and note any Windows-only limitations.
  • Present examples for both Windows and Linux environments side-by-side, or alternate which platform is presented first.
  • Mention and document Linux Hybrid Runbook Worker scenarios and how variable management differs or is supported.
  • Reference Linux tools and patterns (e.g., jq for JSON manipulation, curl for API calls) where relevant.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/start-runbooks.md ...e-docs/blob/main/articles/automation/start-runbooks.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 strong Windows bias by exclusively providing PowerShell examples and referencing Windows PowerShell cmdlets as the primary command-line method for starting runbooks. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or cross-platform scripting tools. Windows tools and terminology are used throughout, and Linux alternatives are not mentioned or linked, resulting in a lack of parity for non-Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
  • Include Bash script samples for starting runbooks via the Azure Automation API.
  • Explicitly mention that PowerShell Core is available on Linux/macOS and provide examples using pwsh where appropriate.
  • Reorder sections or provide parallel examples so that Windows and Linux methods are presented with equal prominence.
  • Reference Linux-specific documentation or tooling where relevant, such as curl for API calls.
  • Clarify that the Azure portal and API methods are platform-agnostic, and provide guidance for Linux users on authentication and scripting.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/extension-based-hybrid-runbook-worker.md .../troubleshoot/extension-based-hybrid-runbook-worker.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows examples, tools, and troubleshooting steps are frequently presented first, with PowerShell scripts and Windows registry paths detailed extensively. Several troubleshooting scenarios and resolutions are Windows-specific, with Linux equivalents sometimes less detailed or omitted. Windows event logs and registry modifications are covered in depth, while Linux troubleshooting relies more on generic file and service checks. In some cases, Linux instructions are present but less comprehensive than their Windows counterparts.
Recommendations
  • Ensure Linux troubleshooting steps are as detailed and actionable as Windows steps, including explicit commands and file paths.
  • Provide Linux-first or parallel examples for all scenarios, especially where Windows PowerShell scripts or registry edits are shown.
  • Include Linux equivalents for Windows event log checks, such as referencing relevant system logs (e.g., journalctl, /var/log/syslog) and diagnostic commands.
  • Balance the order of presentation so that Linux and Windows instructions are given equal prominence, possibly by grouping OS-specific instructions together or alternating their order.
  • Expand Linux-specific troubleshooting scenarios, such as authentication, permissions, and service management, to match the depth of Windows coverage.
  • Where Windows tools (e.g., PowerShell scripts) are referenced, provide or link to Linux shell script equivalents.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/state-configuration/remove-node-and-configuration-package.md ...configuration/remove-node-and-configuration-package.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Windows-specific cmdlets are mentioned and given as primary examples for unregistering nodes and deleting configurations, while Linux instructions are less detailed and appear after Windows steps. Windows tools (PowerShell cmdlets) are referenced by name and with links, whereas Linux instructions are more generic and lack equivalent command-line examples or references to Linux-native tools. The manual deletion section provides a PowerShell cmdlet for Windows but only a file path for Linux, without a sample command.
Recommendations
  • Provide explicit Linux command-line examples for unregistering nodes and deleting configuration files, such as using 'rm' or scripting with Bash.
  • Reference Linux-native tools or commands (e.g., shell scripts, systemctl for service management) where appropriate, similar to how PowerShell cmdlets are referenced for Windows.
  • Ensure that Linux instructions are as detailed and actionable as Windows instructions, including step-by-step commands and links to relevant documentation.
  • Present Windows and Linux instructions in parallel, rather than listing Windows steps first or in greater detail.
  • Where possible, include cross-platform automation examples (e.g., using Azure CLI or REST API) that work on both Windows and Linux.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/desired-state-configuration.md ...automation/troubleshoot/desired-state-configuration.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 significant Windows bias. Troubleshooting steps, examples, and tools are predominantly PowerShell-based, with Windows-specific cmdlets and patterns presented as the default or only option. Linux scenarios are rarely mentioned and typically appear only as exceptions or in isolated sections. Many troubleshooting steps, such as log analysis, certificate management, and node registration, lack Linux-specific guidance or examples, and Windows tools (e.g., xDscDiagnostics, w32tm) are referenced without Linux equivalents.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples alongside Windows instructions, especially for log analysis, certificate management, and node registration.
  • Include Linux command-line equivalents (e.g., bash, systemd, OpenSSL) for tasks currently shown only in PowerShell.
  • Reference Linux DSC extension documentation and tools where relevant, and clarify differences in behavior or error messages between platforms.
  • Ensure that Linux onboarding and error scenarios are covered with the same level of detail as Windows, including portal and CLI steps.
  • Avoid presenting Windows tools and patterns first or exclusively; structure content to address both platforms in parallel where possible.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/hybrid-runbook-worker.md ...icles/automation/troubleshoot/hybrid-runbook-worker.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: troubleshooting steps and examples are frequently presented for Windows first or exclusively, with PowerShell commands and Windows-specific tools (e.g., registry edits, event logs, config files in Program Files) dominating the instructions. Linux troubleshooting is covered in a separate section, but is less detailed, and many scenarios (e.g., corrupt cache, proxy issues, certificate handling) are only described for Windows or with Windows-first guidance. Some issues provide only Windows examples or mention Windows tools before Linux equivalents.
Recommendations
  • Ensure that troubleshooting scenarios are presented in parallel for both Windows and Linux, with equivalent detail and step-by-step instructions.
  • Provide Linux-specific commands and file paths wherever Windows PowerShell commands or registry edits are given (e.g., systemd/service management, config file locations, log file locations).
  • When referencing tools (e.g., event logs, registry, config files), include Linux equivalents (e.g., journalctl, /var/log, config files in /etc or /opt).
  • Avoid presenting Windows solutions or examples before Linux ones; consider grouping by scenario and providing both OS instructions side-by-side.
  • Expand Linux troubleshooting coverage to match the depth and specificity of Windows sections, including common Linux issues (e.g., permissions, SELinux/AppArmor, systemd service failures, certificate management).
  • Where PowerShell is used for Windows, provide Bash or Python script examples for Linux.
  • Review all scenarios for OS parity and add missing Linux examples where only Windows is covered.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/runbooks.md ...blob/main/articles/automation/troubleshoot/runbooks.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 cmdlets, with no equivalent examples for Bash, Azure CLI, or Python (except for a brief mention of Python runbooks in parameter length limits). Windows tools and concepts (e.g., PowerShell ISE, Windows Management Instrumentation, COM servers) are referenced without Linux alternatives. Troubleshooting steps and recommendations consistently use PowerShell modules and commands, and there is no mention of Linux shell scripting, Azure CLI, or cross-platform guidance. The documentation assumes a Windows/PowerShell environment as the default, with little to no consideration for Linux users or those using non-PowerShell automation.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash for common troubleshooting scenarios, especially for starting runbooks, authentication, and module management.
  • Include Python runbook troubleshooting steps and code samples where relevant, given that Python is supported.
  • Reference cross-platform editors (e.g., VS Code) and clarify that runbook authoring and troubleshooting can be performed on Linux and macOS, not just Windows/PowerShell ISE.
  • Mention Linux-specific considerations for Hybrid Runbook Workers, such as module installation and environment setup.
  • When discussing Windows-specific limitations (e.g., COM servers, WMI), note whether these apply or differ on Linux.
  • Add links to Azure CLI documentation and Linux troubleshooting guides for Azure Automation.
  • Ensure that troubleshooting steps do not assume PowerShell as the only language or tool, and provide parity for Linux/CLI users.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/whats-new.md .../azure-docs/blob/main/articles/automation/whats-new.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Azure Automation updates demonstrates a Windows bias in several ways. PowerShell is consistently mentioned as the primary automation language, with frequent updates and new features centered around PowerShell versions and runbooks. Windows-specific tools and modules (e.g., AzureRM, Az PowerShell) are referenced more often and in greater detail than their Linux or cross-platform equivalents. Examples and migration guides typically focus on PowerShell and Windows, with Linux support mentioned only as an add-on or afterthought. There are few, if any, explicit Linux shell (bash) or cross-platform scripting examples, and Windows terminology (such as 'Hybrid Runbook Worker (Windows and Linux)') often lists Windows first.
Recommendations
  • Provide equal coverage and examples for Linux environments, including bash and Python scripting, alongside PowerShell.
  • When listing supported platforms or features, alternate the order or explicitly mention Linux first in some cases to avoid implicit prioritization.
  • Include migration guides and troubleshooting steps that are specific to Linux users, not just Windows/PowerShell.
  • Add documentation and examples for Linux-native tools and workflows (e.g., cron, systemd, bash scripts) in the context of Azure Automation.
  • Ensure that all new features and updates are described with platform parity, highlighting any differences or special considerations for Linux users.
  • Where possible, provide cross-platform code samples (PowerShell, bash, Python) for common automation tasks.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-hybrid-runbook-worker.md ...rticles/automation/automation-hybrid-runbook-worker.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias. Windows is frequently mentioned first (e.g., 'PowerShell cmdlets' listed before Azure CLI, and 'System account on Windows' before 'nxautomation on Linux'). The onboarding and management examples reference PowerShell and Windows-centric tools, with no explicit Linux shell or scripting examples. While Linux is acknowledged as a supported platform, there are no Linux-specific usage patterns or examples, and the documentation lacks parity in describing Linux workflows or troubleshooting steps.
Recommendations
  • Provide explicit Linux shell (bash) and Azure CLI examples alongside PowerShell cmdlets for onboarding and management.
  • Describe Linux-specific operational details, such as log locations, troubleshooting steps, and service management commands.
  • Ensure Linux is mentioned equally or first in lists and examples to avoid implicit prioritization of Windows.
  • Include screenshots or walkthroughs of Linux onboarding and management in addition to Windows.
  • Clarify any differences in permissions, accounts, or behaviors between Windows and Linux Hybrid Runbook Workers.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-graphical-error-handling.md ...omation/automation-runbook-graphical-error-handling.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 bias by exclusively referencing PowerShell, Windows cmdlets, and Windows error handling patterns. All examples and recommended practices are based on PowerShell and Windows-centric tools, with no mention of Linux shell equivalents, Bash, or cross-platform scripting approaches. There are no examples or guidance for Linux users or those using non-PowerShell runbooks.
Recommendations
  • Include examples using Bash or other Linux shells for error handling in graphical runbooks.
  • Mention cross-platform capabilities of Azure Automation and clarify how error handling works for Linux-based runbooks.
  • Provide Linux-specific cmdlet or script examples alongside PowerShell examples.
  • Discuss differences in error handling between Windows/PowerShell and Linux/Bash environments.
  • Add guidance on configuring error handling for Linux activities, including relevant tools and patterns.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/extension-based-hybrid-runbook-worker-install.md ...ation/extension-based-hybrid-runbook-worker-install.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 several forms of Windows bias. Windows examples, especially those using PowerShell and Windows-specific tools (.NET Framework, Windows PowerShell 5.1), are presented first and in greater detail. Many code samples, templates (Bicep, ARM), and CLI instructions default to Windows VM creation and extension installation, with Linux equivalents either missing or less emphasized. The PowerShell cmdlets and extension installation instructions are almost exclusively shown for Windows, with Linux instructions often relegated to brief mentions or not provided at all. Folder permission and proxy configuration examples are Windows-centric, and troubleshooting notes focus on Windows-specific scenarios (UAC/LUA, registry paths).
Recommendations
  • Provide Linux-first or side-by-side examples for all major steps, including extension installation, VM creation, and configuration.
  • Include Linux-specific code samples for Bicep, ARM, REST API, and CLI, not just Windows VM creation.
  • Expand Linux troubleshooting and operational guidance, such as folder permissions, proxy settings, and uninstall instructions.
  • Balance the use of PowerShell with Bash or other Linux-native scripting examples.
  • Highlight Linux package requirements and configuration steps with equal detail as Windows prerequisites.
  • Ensure documentation screenshots and portal instructions are applicable to both Windows and Linux scenarios.
  • Clarify when instructions are OS-specific and provide links or references to Linux documentation where appropriate.
GitHub Create Pull Request
← Previous Page 15 of 40 Next →