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 201-225 of 365 flagged pages
Automation Manage variables in Azure Automation ...main/articles/automation/shared-resources/variables.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 page demonstrates a notable Windows bias. PowerShell (and specifically Windows PowerShell) is referenced as the primary scripting environment for variable management, with all CLI examples given in PowerShell. Windows-specific terminology and cmdlets (e.g., 'Windows PowerShell', 'Hybrid Runbook Worker') are used throughout, and there are no Bash, Azure CLI, or Linux shell examples. The Python section is included, but only as runbook code, not as general CLI usage. No Linux/macOS shell equivalents or guidance are provided for users who may prefer or require non-Windows environments.
Recommendations
  • Add Azure CLI examples for variable management tasks alongside PowerShell examples.
  • Clarify which cmdlets and features are available cross-platform (Windows, Linux, macOS) and which are Windows-only.
  • Provide Bash or shell script examples for common tasks, or explicitly state if such functionality is unavailable.
  • Avoid using 'Windows PowerShell' as the default term; use 'PowerShell' and specify platform differences where relevant.
  • Include guidance for Linux/macOS users on how to perform equivalent operations, or note any limitations.
  • Add a section on platform compatibility for Automation features and tools.
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-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 notable Windows bias by providing only Windows PowerShell examples and focusing on Windows tools (PowerShell cmdlets) for command-line automation. There are no Linux/macOS CLI examples (e.g., Azure CLI, Bash), and PowerShell is presented as the primary scripting method. The page does not mention cross-platform alternatives or clarify PowerShell Core support, and Windows-centric terminology is used throughout.
Recommendations
  • Add equivalent Azure CLI examples for starting and managing runbooks, which work natively on Linux/macOS.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide examples if so.
  • Include Bash or REST API examples for common tasks, especially for parameter passing and job tracking.
  • Reorder sections so that cross-platform methods (Azure CLI, REST API) are presented before or alongside Windows PowerShell.
  • Explicitly mention platform compatibility for each method, helping users choose the right tool for their OS.
GitHub Create Pull Request
Automation Troubleshoot agent-based Hybrid Runbook Worker issues in Azure Automation ...icles/automation/troubleshoot/hybrid-runbook-worker.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. Troubleshooting steps and examples are frequently presented for Windows first, with PowerShell and Windows-specific tools (e.g., registry edits, event logs, config files in Windows paths) featured prominently. Linux troubleshooting is covered in a separate section, but many scenarios (such as module updates, config file changes, and proxy issues) provide only Windows-specific instructions or examples, with Linux equivalents missing or less detailed. Windows tools and patterns (e.g., registry, event logs, PowerShell cmdlets) are mentioned exclusively or before Linux alternatives.
Recommendations
  • Ensure every troubleshooting scenario includes both Windows and Linux instructions/examples where applicable.
  • Provide Linux equivalents for Windows-specific steps (e.g., config file locations, service management commands, log file paths, authentication methods).
  • Present Windows and Linux troubleshooting steps in parallel, rather than segregating them or listing Windows first.
  • Include Linux shell commands and configuration file examples alongside PowerShell and Windows registry instructions.
  • Reference Linux logs and diagnostic tools (e.g., journalctl, /var/log/) where Windows event logs are mentioned.
  • Clarify when a step is Windows-only and provide alternative guidance for Linux users.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation shared resource issues ...n/articles/automation/troubleshoot/shared-resources.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 cmdlets and scripts, which are native to Windows environments. All troubleshooting examples and resolutions use PowerShell commands (e.g., Remove-AzAutomationModule, New-AzAutomationModule, Connect-AzAccount), with no mention of Bash, Azure CLI, or Linux/macOS alternatives. Windows-specific terminology and tools (DLL errors, .psd1/.psm1 files, PowerShell runbooks) are used exclusively, and no Linux/macOS-specific troubleshooting steps or examples are provided.
Recommendations
  • Add equivalent Azure CLI commands and examples for each PowerShell cmdlet mentioned, especially for module management and authentication.
  • Include troubleshooting steps for Linux/macOS users, such as how to handle module imports and runbook errors in non-Windows environments.
  • Mention cross-platform tools and patterns (e.g., Bash scripts, Python runbooks) where applicable.
  • Provide guidance on using Azure Automation with Linux Hybrid Workers, if relevant.
  • Reorder examples to present cross-platform solutions first, or at least in parallel with Windows/PowerShell solutions.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation runbook issues ...blob/main/articles/automation/troubleshoot/runbooks.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 and Windows-centric tools and workflows. All code examples use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux/macOS-specific troubleshooting steps. Windows/PowerShell tools (e.g., PowerShell ISE, Windows-specific modules) are referenced exclusively, and there is no parity for users who prefer or require Linux/macOS environments. Even when Python is mentioned, no examples or troubleshooting steps are provided for it.
Recommendations
  • Add Azure CLI (az) and Bash examples alongside PowerShell for common tasks such as starting runbooks, authenticating, and managing modules.
  • Include troubleshooting steps and examples for Python runbooks, especially since Python is supported and mentioned.
  • Reference cross-platform editors (e.g., VS Code) and avoid recommending Windows-only tools like PowerShell ISE.
  • Explicitly state which solutions are platform-agnostic and which are Windows-specific, and provide alternatives for Linux/macOS where needed.
  • Add notes or sections addressing common Linux/macOS issues (e.g., module installation, authentication differences, hybrid worker setup on Linux).
GitHub Create Pull Request
Automation What's New in Azure Automation .../azure-docs/blob/main/articles/automation/whats-new.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 notable bias towards Windows and PowerShell. Most examples and feature announcements focus on PowerShell runbooks, with Windows terminology and tools mentioned more frequently and often before Linux equivalents. While Linux is occasionally referenced (e.g., Hybrid Runbook Worker support), there is a lack of parity in examples, guidance, and tool coverage for Linux and macOS users. Python is mentioned as an alternative, but PowerShell (a Windows-centric technology) dominates the documentation, and there are few explicit Linux/macOS usage scenarios or examples.
Recommendations
  • Provide equal examples and guidance for Linux/macOS users, including bash and shell scripting runbooks.
  • When announcing new features (e.g., Azure CLI support), clarify cross-platform compatibility and provide Linux/macOS usage instructions.
  • Include Linux/macOS-specific troubleshooting, migration, and setup steps where relevant.
  • Ensure that references to tools (e.g., VS Code extension, CLI) mention cross-platform support and usage.
  • Add explicit Linux/macOS runbook samples alongside PowerShell examples.
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-12 00:00
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 PowerShell-centric examples and instructions, referencing PowerShell runbooks and cmdlets as primary automation methods, and omitting equivalent Linux/macOS CLI (Azure CLI, Bash) examples for key tasks such as rotating access keys. Windows/PowerShell tools and patterns are mentioned first and most frequently, while Linux alternatives are either absent or relegated to secondary references.
Recommendations
  • Add Azure CLI and Bash examples for all tasks currently shown only with PowerShell, such as rotating access keys.
  • Include explicit instructions and screenshots for Linux/macOS users where portal or command-line steps may differ.
  • Ensure parity in runbook tutorials by providing examples for Python and Bash runbooks alongside PowerShell.
  • Reference cross-platform tools (e.g., Azure CLI) before or alongside PowerShell, not after.
  • Clarify that PowerShell examples are usable on Linux/macOS (if true), or provide platform-specific notes.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily focused on PowerShell and Windows-centric workflows, with all examples and scenarios referencing PowerShell Gallery, PowerShell modules, and Windows Azure VMs. There are no Linux/macOS-specific instructions, examples, or parity for Linux tools or workflows, and the only mention of Linux is as a tag in a note. This creates friction for users on non-Windows platforms, especially those seeking to automate Azure resources using Linux-native tools or Python runbooks.
Recommendations
  • Include examples and instructions for importing and using Python runbooks, especially for Linux/macOS users.
  • Provide parity by listing Linux automation scenarios (e.g., copying files to/from Linux Azure VMs) alongside Windows examples.
  • Add guidance for using Azure Automation with Linux-based modules and scripts, including any platform-specific caveats.
  • Ensure that documentation for contributing runbooks highlights both PowerShell and Python equally, and encourages Linux scenarios.
  • Clarify support for PowerShell Core and its cross-platform capabilities, and note any limitations for Linux/macOS users.
GitHub Create Pull Request
Automation Manage connections in Azure Automation ...lob/main/articles/automation/automation-connections.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits a notable Windows bias. PowerShell and Az module cmdlets are featured prominently and exclusively for connection management tasks, with no equivalent CLI or Linux-native examples. The 'Create a new connection' section provides a detailed PowerShell example but omits any Azure CLI, REST API, or Linux shell alternatives. Windows/PowerShell tools are mentioned first and in greater detail, while Linux/macOS users are left to infer or seek out their own solutions.
Recommendations
  • Add Azure CLI examples for creating and managing connections, as CLI is cross-platform.
  • Include REST API usage for connection management, which is platform-agnostic.
  • Provide explicit guidance for Linux/macOS users, such as using the Azure CLI or Python SDK.
  • Reorder examples so that platform-neutral or cross-platform methods (CLI, REST, Python) are presented before or alongside PowerShell.
  • Clarify which steps or tools are Windows-specific and offer alternatives for other platforms.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page presents Windows remediation steps first, with detailed PowerShell and Azure Run Command examples, while Linux instructions are less detailed, lack direct script examples, and highlight limitations (no Run Command support). References and next steps also prioritize Windows/PowerShell tools and workflows.
Recommendations
  • Provide explicit Linux shell script examples for remediation, similar to the PowerShell example for Windows.
  • Include step-by-step instructions for Linux drift correction, not just references to external documentation.
  • Clarify alternative Linux workflows, such as using SSH or cloud-init, where Run Command is unavailable.
  • Balance the order of presentation so Linux instructions are not secondary to Windows.
  • Add references to Linux-specific tools and modules, not just PowerShell/Az.Automation.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows and PowerShell, with all examples and tooling based on Windows technologies. The migration process centers around converting Orchestrator runbooks to Azure Automation graphical runbooks using PowerShell modules and cmdlets, with no mention of Linux/macOS alternatives or cross-platform considerations. All example commands use Windows paths and PowerShell syntax, and there is no guidance for users on non-Windows platforms.
Recommendations
  • Provide examples for Linux/macOS users, such as using Azure CLI or Bash where possible.
  • Clarify whether the migration tools (e.g., Runbook Converter, Integration Pack Converter) can be run on Linux/macOS, or specify Windows-only requirements.
  • Offer guidance for users who manage Azure Automation from non-Windows environments, including alternative workflows or toolchains.
  • Include notes on cross-platform compatibility for PowerShell modules, especially since PowerShell Core is available on Linux/macOS.
  • List prerequisites and supported platforms for each tool mentioned, and suggest alternatives if available.
GitHub Create Pull Request
Automation Azure Automation extension for Visual Studio Code ...ation/how-to/runbook-authoring-extension-for-vscode.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation page references PowerShell modules as a prerequisite for local runbook execution, but does not mention Linux/macOS equivalents or provide guidance for installing Python packages or PowerShell modules on non-Windows platforms. No explicit Windows-only tools are referenced, but the lack of Linux/macOS-specific instructions or examples may create friction for non-Windows users.
Recommendations
  • Add explicit instructions for installing PowerShell modules and Python packages on Linux and macOS (e.g., using pip, PowerShell Core on Linux).
  • Clarify that Visual Studio Code and the Azure Automation extension are cross-platform, and provide any platform-specific caveats.
  • Include examples or troubleshooting tips for running runbooks locally on Linux/macOS, especially if there are known differences.
  • Mention that PowerShell Core is available on Linux/macOS and link to installation guides.
GitHub Create Pull Request
Automation Azure Automation network configuration details ...rticles/automation/automation-network-configuration.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references Windows-specific DSC resources (such as WaitFor resources) and links to PowerShell DSC documentation for Windows, without mentioning or providing Linux equivalents or guidance for cross-platform scenarios. Windows tools and terminology appear first and exclusively in some sections, which may create friction for Linux users seeking parity.
Recommendations
  • Include explicit references to Linux DSC resources and their documentation.
  • Provide examples or guidance for configuring network requirements for Linux-based Hybrid Runbook Workers and DSC nodes.
  • Clarify whether the described network requirements apply equally to Linux and Windows environments.
  • Add links to cross-platform DSC documentation and note differences in resource usage or configuration.
  • Avoid referencing Windows-only resources (like WaitForAllResource) without mentioning Linux alternatives or limitations.
GitHub Create Pull Request
Automation Send an email from an Azure Automation runbook ...blob/main/articles/automation/automation-send-email.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses PowerShell for all examples and automation steps, with no mention of Bash, CLI, or Linux/macOS alternatives. All code samples, module references, and instructions assume a PowerShell environment, which is most common on Windows. There is no guidance for users who may prefer or require Bash, Azure CLI, or other cross-platform tools, nor any indication of how to adapt the process for Linux/macOS environments.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts, especially for key steps like creating Key Vaults, assigning permissions, and sending emails.
  • Explicitly mention that Azure Automation runbooks can be authored in Python or graphical formats, and link to relevant documentation.
  • Add a section or callouts for Linux/macOS users, including installation instructions for required modules or tools.
  • Order examples so that cross-platform options (e.g., Azure CLI) are shown before or alongside PowerShell.
  • Clarify which steps are platform-agnostic and which require adaptation for non-Windows environments.
GitHub Create Pull Request
Automation Migrate from a Run As account to Managed identities ...automation/migrate-run-as-accounts-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell-based automation, with all code samples and migration steps using PowerShell cmdlets and syntax. There are no examples or guidance for Linux/macOS users, such as using Python, Bash, or cross-platform SDKs. The use of PowerShell and references to Windows-centric tools and patterns (e.g., 'Connect-AzAccount', 'Get-AutomationConnection') dominate the page, making it challenging for non-Windows users to follow or adapt the instructions.
Recommendations
  • Add equivalent examples using Azure CLI, Python SDK, or Bash scripts to demonstrate managed identity authentication and resource access.
  • Explicitly mention cross-platform alternatives and clarify which steps are platform-agnostic.
  • Provide guidance or links for Linux/macOS users on setting up and using managed identities in Azure Automation with non-PowerShell tools.
  • Reorder examples or add tabs for different platforms (Windows/PowerShell, Linux/Bash, macOS/Python) to improve parity.
  • Clarify that Azure Automation runbooks can be authored in Python and provide migration steps for Python-based runbooks.
GitHub Create Pull Request
Automation Manage Python 3 packages in Azure Automation ...ocs/blob/main/articles/automation/python-3-packages.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits several Windows-centric biases. Windows examples and instructions are presented first or exclusively in key sections, particularly for Python 3.8, with explicit references to Windows architectures and requirements. PowerShell cmdlets are provided for package management without Linux or cross-platform CLI alternatives. Linux instructions are present for Python 3.10 but missing for Python 3.8, and Windows tooling is assumed for some package preparation steps.
Recommendations
  • Provide Linux/macOS equivalents for all Windows-specific instructions, especially for Python 3.8 (e.g., how to build wheels on Linux for Python 3.8).
  • Include Azure CLI or REST API examples alongside PowerShell cmdlets for package management tasks.
  • Present Linux and Windows instructions in parallel or clarify platform requirements before each example.
  • Add notes or guidance for users on non-Windows platforms regarding package preparation and upload.
  • Ensure screenshots and UI instructions are platform-neutral or provide alternatives where UI differs.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Azure PowerShell cmdlets and runbooks, with all examples and recommendations using PowerShell syntax and tools. There is no mention of Linux/macOS equivalents, such as Azure CLI or Python SDK, nor are any cross-platform scripting options provided. Windows/PowerShell tools and patterns are presented exclusively and first, making it difficult for Linux/macOS users to follow or adapt the guidance.
Recommendations
  • Add equivalent examples using Azure CLI and/or Python SDK, which are cross-platform and commonly used on Linux/macOS.
  • Explicitly mention that PowerShell is available on Linux/macOS, but also provide non-PowerShell alternatives.
  • Clarify whether the recommendations apply to runbooks written in other languages (e.g., Python) and provide guidance for those scenarios.
  • Reorder examples or provide parallel examples so that Linux/macOS users do not feel secondary.
GitHub Create Pull Request
Automation Manage modules in Azure Automation ...b/main/articles/automation/shared-resources/modules.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on PowerShell modules and cmdlets, with almost all examples, instructions, and internal tooling referencing Windows PowerShell and Azure PowerShell modules. Windows-specific features and tools (e.g., Orchestrator.AssetManagement.Cmdlets, Hybrid Runbook Worker on Windows) are described in detail, while Linux equivalents are either missing, explicitly unsupported, or only briefly mentioned. There are no Linux or cross-platform CLI examples, and the workflow assumes a Windows-centric approach to module management and runbook authoring.
Recommendations
  • Add equivalent examples and instructions for Linux/macOS users, such as using Azure CLI or Python modules where possible.
  • Clearly indicate which features are Windows-only and provide alternative workflows for Linux Hybrid Runbook Workers.
  • Include Linux-specific guidance for module management, runbook authoring, and troubleshooting.
  • Provide parity in screenshots and portal instructions for Linux environments.
  • Expand documentation on Python modules and other cross-platform options, not just PowerShell.
  • List limitations and workarounds for Linux users up front, and link to relevant Linux 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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for managing Azure Automation accounts primarily via the Azure portal and Azure PowerShell, with no examples or guidance for Linux/macOS users using Bash, Azure CLI, or REST API. PowerShell commands are shown as the only code examples, and there is no parity for Linux-native tooling or scripting. This creates friction for users who do not use Windows or PowerShell.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all automation and deletion tasks.
  • Include REST API sample requests for account deletion and recovery.
  • Explicitly mention that PowerShell commands can be run on macOS/Linux (if true), or provide alternatives.
  • Ensure that CLI/Bash examples are shown before or alongside PowerShell to avoid Windows-first bias.
  • Add notes or sections for Linux/macOS users, clarifying any platform-specific steps or limitations.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias by focusing almost exclusively on PowerShell cmdlets and Windows-centric tooling for credential management in Azure Automation. All CLI examples are PowerShell-based, with no Bash, Linux shell, or cross-platform CLI alternatives provided. Windows tools and patterns (e.g., PSCredential, Get-Credential) are mentioned and explained in detail, while Linux/macOS equivalents or guidance are absent. The Python section is present but limited, and there are no examples using Azure CLI or REST API, which are platform-agnostic.
Recommendations
  • Add Azure CLI examples for credential management tasks, as Azure CLI is cross-platform.
  • Include Bash or shell script examples for Linux/macOS users where applicable.
  • Document REST API methods for managing credentials to provide a platform-neutral approach.
  • Clarify which features and cmdlets are Windows-specific and provide Linux/macOS alternatives or workarounds.
  • Reorder sections to present platform-neutral or cross-platform methods before Windows/PowerShell-specific ones.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. PowerShell cmdlets are emphasized throughout, with all CLI examples provided exclusively in PowerShell. Windows-centric tools (e.g., Add-AzureCertificate) are referenced without Linux equivalents. No Bash, Azure CLI, or Linux-native certificate management examples are given, and PowerShell examples are presented first and most extensively. Python examples are included, but only for runbook scripting, not for certificate management tasks outside Automation.
Recommendations
  • Add Azure CLI and Bash examples for certificate management tasks, such as uploading and retrieving certificates.
  • Reference cross-platform tools (e.g., OpenSSL, az CLI) for certificate handling, especially for Linux/macOS users.
  • Include guidance for Linux/macOS users on preparing and uploading certificates (e.g., converting formats, permissions).
  • Present examples for both Windows and Linux environments, or clarify platform requirements for PowerShell usage.
  • Avoid recommending PowerShell as the only workaround for portal limitations; suggest Azure CLI or REST API alternatives.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Windows-specific cmdlets are mentioned and exemplified before Linux equivalents. Manual deletion instructions for Windows use PowerShell cmdlets, while Linux instructions are less detailed and only mention file deletion. The re-registration and configuration removal steps reference Windows tooling more prominently, and Linux package removal is relegated to an optional section at the end. There is a lack of parity in example depth and guidance for Linux users.
Recommendations
  • Provide Linux command-line examples for unregistering nodes (e.g., using az CLI or REST API).
  • Include Linux-specific automation tools or scripts for configuration removal, not just manual file deletion.
  • Present Windows and Linux instructions side-by-side or in parallel tabs, ensuring equal detail and visibility.
  • Reference Linux tools (such as shell scripts or configuration management utilities) alongside PowerShell cmdlets.
  • Clarify any differences in process for Linux users, and ensure all steps are covered for both platforms.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias, primarily through the exclusive use of PowerShell for all command-line examples and automation steps. PowerShell cmdlets are used for REST API calls, ARM template deployments, role assignments, and authentication, with no mention of Bash, Azure CLI, or Linux-native tools. Even generic HTTP requests are demonstrated using PowerShell, and file paths use Windows conventions. The only non-PowerShell example is a Python snippet, but it does not address shell or CLI parity. There are no Linux/macOS-specific instructions or examples, and PowerShell is presented as the default and only scripting environment.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell cmdlets, especially for resource creation, role assignment, and authentication.
  • Provide Bash shell examples for REST API calls using curl or wget, including access token retrieval.
  • Use platform-neutral file path conventions (e.g., forward slashes) or clarify path usage for different OSes.
  • Explicitly mention that PowerShell Core is cross-platform, but also provide instructions for Linux/macOS users who may prefer Bash or Azure CLI.
  • Include troubleshooting notes or links for Linux/macOS users regarding environment setup and authentication differences.
  • Reorder examples so that platform-neutral or cross-platform methods (portal, REST API, ARM template) are presented before platform-specific scripting.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell-based runbooks and Windows-centric tools (e.g., Az.Automation PowerShell module, Start-AzAutomationRunbook, Disable-AzContextAutosave). All code examples are in PowerShell, with no mention of Bash, Python, or Linux-native automation patterns. Windows/PowerShell terminology and tools are used exclusively and described first, with no Linux or cross-platform alternatives provided.
Recommendations
  • Include equivalent examples using Python runbooks, which are supported in Azure Automation and popular on Linux/macOS.
  • Add Bash or shell script runbook examples where applicable.
  • Explicitly mention cross-platform compatibility of Azure Automation, clarifying which features/tools work on Linux/macOS.
  • Provide guidance for Linux/macOS users on authentication and context management (e.g., using service principals, managed identities in non-Windows environments).
  • Reorder sections or add notes to clarify that Azure Automation is not limited to Windows/PowerShell.
  • Reference CLI-based alternatives (e.g., Azure CLI) for starting and managing runbooks.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All code examples and instructions use PowerShell, with no mention of Bash, Azure CLI, or Linux/macOS alternatives. The prerequisites link specifically to Windows VM creation via PowerShell, and the Az PowerShell module is referenced exclusively. There are no Linux/macOS-specific instructions, nor are cross-platform tools or patterns discussed. This creates friction for users on non-Windows platforms, who must adapt PowerShell-centric steps to their environments.
Recommendations
  • Provide equivalent Azure CLI (az) examples for all PowerShell scripts, especially for role assignment and VM management.
  • Include instructions or links for creating Azure VMs on Linux/macOS, not just Windows/PowerShell.
  • Clarify that Azure Automation runbooks can be authored in Python or other supported languages, and show how to use those.
  • Add notes or sections for Linux/macOS users, including installation of Az CLI and relevant environment setup.
  • Reorder examples so that cross-platform methods (e.g., Azure CLI) are shown before or alongside PowerShell.
  • Explicitly state platform compatibility for each step and tool.
GitHub Create Pull Request
← Previous Page 9 of 15 Next →