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 301-325 of 365 flagged pages
Automation Runbook authoring using VS Code in Azure Automation ...in/articles/automation/automation-runbook-authoring.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias: Windows operating systems and PowerShell (especially Windows PowerShell 5.1) are mentioned first and in more detail than Linux/macOS equivalents. Examples and directory paths use Windows-style notation (e.g., C:\abc), and there are no explicit Linux/macOS command or path examples. Debugging support is focused on PowerShell, with Python debugging left to third-party extensions and no mention of Linux/macOS-specific workflows or troubleshooting.
Recommendations
  • Include Linux/macOS-specific examples for directory paths (e.g., /home/user/abc) alongside Windows examples.
  • Provide explicit instructions for installing required PowerShell modules and Python packages on Linux/macOS.
  • Clarify any differences in local runbook execution or debugging on Linux/macOS, including limitations or workarounds.
  • List supported operating systems in a neutral order (e.g., alphabetical or grouped by platform) rather than Windows-first.
  • Add troubleshooting or FAQ sections for common Linux/macOS issues.
  • Ensure parity in feature descriptions, especially for debugging and asset management, across all platforms.
GitHub Create Pull Request
Automation Azure Automation network configuration details ...rticles/automation/automation-network-configuration.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 under /powershell/dsc/reference/resources/windows/waitForAllResource) without mentioning Linux equivalents or providing parity for Linux DSC resources. The only example of DSC resource communication is Windows-focused, and the documentation links to Windows-centric PowerShell DSC documentation first. There are no explicit Linux/macOS examples or references, and Linux DSC resource requirements are not discussed.
Recommendations
  • Include references and examples for Linux DSC resources, such as links to Linux DSC documentation and resource requirements.
  • Clarify whether the network requirements and DSC resource communication guidance apply equally to Linux nodes, and provide any Linux-specific caveats.
  • Add examples or notes for configuring DSC on Linux/macOS, including any differences in resource communication or network setup.
  • Provide parity in documentation links, referencing both Windows and Linux DSC resources where applicable.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows-specific tools (PowerShell cmdlets) are referenced frequently and often exclusively for backup/export tasks, with Linux alternatives missing. Windows instructions and links are presented before Linux equivalents. Linux guidance is limited to TLS configuration, with no Linux/macOS-specific examples for backup, export, or asset management.
Recommendations
  • Provide Linux/macOS-specific examples for exporting runbooks and DSC configurations, such as using Azure CLI or REST API.
  • Include parity for asset management and retrieval using cross-platform tools (e.g., Azure CLI, az automation commands).
  • List Linux/macOS instructions alongside Windows, not after or separately.
  • Reference cross-platform documentation and tools before or alongside Windows/PowerShell-specific ones.
  • Add explicit guidance for Linux/macOS users for tasks currently covered only by PowerShell cmdlets.
GitHub Create Pull Request
Automation Encryption of secure assets in Azure Automation ...icles/automation/automation-secure-asset-encryption.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias by providing only PowerShell examples for all command-line operations, referencing Windows-centric tools (Azure Az PowerShell module) and cmdlets, and omitting equivalent instructions for Linux/macOS users (e.g., Bash, Azure CLI). PowerShell is presented as the primary method for configuration, with REST API as a secondary option. There are no examples using Azure CLI or Bash, and PowerShell prerequisites are explicitly called out, reinforcing the Windows-first approach.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, especially for key vault and automation account management.
  • Include Bash script snippets where appropriate, demonstrating cross-platform usage.
  • Present Azure CLI and REST API methods before or alongside PowerShell to avoid Windows-first ordering.
  • Clarify that PowerShell cmdlets can be run on Linux/macOS, but also provide CLI alternatives for users who prefer native tools.
  • Explicitly mention platform compatibility and provide guidance for Linux/macOS users in the prerequisites section.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools, with examples and scenarios almost exclusively referencing PowerShell, PowerShell Gallery, and Windows Azure VMs. There is little to no mention of Linux/macOS equivalents, and no examples or guidance for Linux users. Even Python runbooks are mentioned only in passing, with no Linux-specific instructions or parity for common tasks.
Recommendations
  • Add explicit examples and instructions for importing and using runbooks/modules on Linux/macOS environments.
  • Include scenarios and runbooks for Linux Azure VMs, such as file copy operations or diagnostics, alongside Windows examples.
  • Clarify which features and modules are supported on PowerShell Core (cross-platform) and which are Windows-only.
  • Provide parity in documentation for Python runbooks, including Linux/macOS usage patterns.
  • Reorder examples so Linux/macOS scenarios are presented alongside or before Windows ones where appropriate.
GitHub Create Pull Request
Automation Configure runbook output and message streams ...s/automation/automation-runbook-output-and-messages.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows PowerShell, with all code examples, cmdlets, and patterns using PowerShell syntax and Windows-centric tooling. There is no mention of Linux/macOS equivalents, such as Bash, Python, or cross-platform Azure CLI commands. The retrieval of runbook output is described only with Windows PowerShell cmdlets, and preference variables are referenced as Windows PowerShell constructs. The documentation assumes familiarity with PowerShell and does not provide guidance for Linux/macOS users or cross-platform alternatives.
Recommendations
  • Add equivalent examples using Azure CLI and/or REST API for retrieving runbook output and messages, which are cross-platform.
  • Include references and examples for Python runbooks, especially since Python is mentioned as supported for output streams.
  • Explicitly state platform requirements and limitations for PowerShell-based runbooks, and provide guidance for Linux/macOS users.
  • Provide links to documentation for running and managing Azure Automation from Linux/macOS environments.
  • Where possible, show both PowerShell and Bash/Azure CLI examples side-by-side.
  • Clarify which features (such as preference variables) are PowerShell-specific and what alternatives exist for other languages/platforms.
GitHub Create Pull Request
Automation Azure Automation Runbook Types ...b/main/articles/automation/automation-runbook-types.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. PowerShell (a Windows-centric technology) is presented first and in greatest detail, with extensive examples and troubleshooting focused on Windows paths and tools (e.g., C:\modules, environment variables like TEMP, Windows PowerShell Workflow). Many examples and workarounds reference Windows file paths and cmdlets, and graphical runbooks are based on Windows PowerShell and cannot run on Linux Hybrid Workers. Python runbooks receive less coverage, and Linux-specific guidance is minimal, with several sections lacking Linux examples or explicit parity notes.
Recommendations
  • Provide Linux-specific examples and troubleshooting for PowerShell runbooks, especially for Hybrid Runbook Workers.
  • Include Linux file path examples and clarify differences in environment variables and module locations.
  • Add parity notes for features unavailable on Linux (e.g., graphical runbooks, PowerShell Workflow) and suggest alternatives.
  • Expand Python runbook documentation to include Linux-specific package management, environment setup, and known issues.
  • Where Windows tools or patterns are mentioned (e.g., C:\modules, python.exe), offer equivalent Linux guidance (e.g., /usr/lib/python3, python3 binary).
  • Reorder sections or provide parallel examples so Linux and Windows users see relevant information simultaneously.
GitHub Create Pull Request
Automation Track updated files with an Azure Automation watcher task ...s/automation/automation-scenario-using-watcher-task.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows environments, with all examples and instructions using PowerShell and Windows-style paths (e.g., D:\examplefiles). There are no Linux or macOS equivalents provided for file creation, folder paths, or hybrid worker setup. The only method shown for triggering the watcher is via PowerShell, and the runbooks referenced are PowerShell scripts. This creates friction for Linux/macOS users, who must adapt the instructions and scripts themselves.
Recommendations
  • Provide equivalent examples for Linux/macOS environments, such as using Bash to create test files and referencing Unix-style paths (e.g., /home/examplefiles).
  • Clarify whether hybrid runbook workers can run on Linux, and if so, provide setup instructions and examples.
  • Include notes or sections on adapting PowerShell runbooks for cross-platform compatibility, or offer Bash/Python alternatives where possible.
  • Explicitly mention any platform limitations (e.g., if watcher tasks only work on Windows hybrid workers) at the start of the article.
  • Show Linux/macOS commands alongside PowerShell commands when demonstrating how to trigger watcher tasks.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively uses PowerShell for all examples and instructions, including setup, resource management, and runbook creation. There are no Bash, CLI, or Linux/macOS-specific examples or guidance. Windows-centric tools and patterns (PowerShell cmdlets, Windows terminology) are used throughout, with no mention of alternatives or parity for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all major steps, including Key Vault creation, secret management, and role assignment.
  • Include instructions for creating and editing runbooks using Python (supported in Azure Automation) and demonstrate sending email via SendGrid in Python.
  • Explicitly mention cross-platform compatibility and provide guidance for Linux/macOS users, including how to install required modules and run scripts.
  • Reorder examples so that CLI/Bash and PowerShell are presented together or with CLI first to avoid implicit Windows-first bias.
  • Reference documentation for Linux/macOS environments where relevant (e.g., installing Azure CLI, using VS Code on Linux).
GitHub Create Pull Request
Automation Migration guidance from Change Tracking and inventory using Log Analytics to Azure Monitoring Agent ...g/guidance-migration-log-analytics-monitoring-agent.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides migration guidance for both Windows and Linux VMs, but script-based migration is exclusively covered using PowerShell, with no Bash, shell, or Linux-native scripting alternatives. The prerequisites and instructions for scripting are PowerShell-centric, and examples for Linux users are missing. Additionally, the order of presentation and screenshots tend to focus on Windows-centric workflows, with Linux-specific details (such as file paths, commands, or daemon management) not explicitly demonstrated.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux users, or document how to perform the migration using Linux-native tools.
  • Explicitly mention Linux prerequisites and steps for running PowerShell on Linux, including installation and environment setup.
  • Add screenshots and walkthroughs for Linux VM onboarding and migration, highlighting any differences from Windows.
  • Include Linux-specific troubleshooting and limitations, especially regarding agent removal and file/daemon tracking.
  • Ensure parity in example order and visibility, alternating or grouping Windows and Linux instructions equally.
GitHub Create Pull Request
Automation Delete an Azure Automation Run As account ...blob/main/articles/automation/delete-run-as-account.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses on deleting Azure Automation Run As accounts primarily through PowerShell and the Azure portal, both of which are Windows-centric tools. There are no examples or instructions for Linux/macOS users, such as using Azure CLI or Bash scripts, and PowerShell is mentioned as the main scripting method without alternatives.
Recommendations
  • Add Linux/macOS-friendly instructions using Azure CLI or Bash.
  • Provide examples for deleting Run As accounts with Azure CLI commands.
  • Clarify cross-platform availability of PowerShell and mention installation steps for non-Windows users.
  • Include notes or links for Linux/macOS users on how to perform equivalent actions.
GitHub Create Pull Request
Automation Automation services in Azure - overview ...s/blob/main/articles/automation/automation-services.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a notable Windows bias, primarily through its heavy emphasis on PowerShell for automation examples and tooling. Azure Automation is repeatedly described in terms of PowerShell runbooks, modules, and integration, with only secondary mention of Python. Windows-centric tools (PowerShell, registry, Active Directory, SQL Server) are referenced frequently, and Windows scenarios (e.g., registry changes, ServiceNow integration, on-premises Windows server management) are highlighted. Linux support is mentioned in passing (e.g., Azure Automanage supports Linux and Windows), but Linux-specific examples, tools, or workflows are not provided. The order of presentation and scenario descriptions generally favor Windows/PowerShell first, with Linux parity implied but not demonstrated.
Recommendations
  • Add explicit Linux-focused examples for each automation service, such as Bash scripts, Ansible playbooks, or Python runbooks managing Linux VMs.
  • Include references to Linux-native tools and configuration management systems (e.g., systemd, cron, SSH, SELinux, apt/yum package management) in relevant scenarios.
  • Balance scenario tables and user descriptions to include Linux administrators and DevOps engineers, not just Windows-centric roles.
  • When describing PowerShell, equally highlight Python and other cross-platform scripting options, and provide links to Linux-specific documentation.
  • Showcase hybrid and Linux-only automation workflows, such as patching, compliance, and configuration drift detection on Linux servers.
GitHub Create Pull Request
Automation Start an Azure Automation Runbook from a Webhook ...s/blob/main/articles/automation/automation-webhooks.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All code samples and walkthroughs use PowerShell cmdlets and tools, with no mention of Linux/macOS equivalents or cross-platform alternatives. Even REST API examples are shown using PowerShell's Invoke-RestMethod. There are no bash, curl, or other Linux-native examples, and the workflow assumes the user is on Windows or has PowerShell available. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
  • Provide equivalent examples using bash and curl for webhook creation, invocation, and deletion.
  • Include instructions for using Azure CLI (az) commands, which are cross-platform.
  • Show how to use REST API calls with curl or httpie, not just PowerShell.
  • Clarify which steps are platform-agnostic and which require Windows/PowerShell.
  • Add notes or sections for Linux/macOS users, including installation of PowerShell Core if needed.
  • Reorder examples so that platform-neutral or cross-platform methods (REST API, Azure CLI) are presented before Windows/PowerShell-specific ones.
GitHub Create Pull Request
Automation Disable local authentication in Azure Automation ...in/articles/automation/disable-local-authentication.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation relies exclusively on PowerShell examples and cmdlets (e.g., Invoke-AzRestMethod, Get-AzAutomationAccount) for disabling local authentication in Azure Automation. No equivalent Linux/macOS CLI (az CLI, curl, etc.) or REST API examples are provided, making it difficult for non-Windows users to follow the instructions without adaptation.
Recommendations
  • Add equivalent az CLI examples for checking and updating the DisableLocalAuth property.
  • Provide REST API usage examples with curl or httpie for Linux/macOS users.
  • Include explicit notes or sections for Linux/macOS users, clarifying cross-platform approaches.
  • Present examples for both Windows (PowerShell) and Linux/macOS (bash/CLI) side-by-side or in parallel sections.
GitHub Create Pull Request
Automation Using a system-assigned managed identity for an Azure Automation account ...s/automation/enable-managed-identity-for-automation.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on PowerShell-based workflows and examples, which are most natural and accessible on Windows. All CLI examples use PowerShell syntax, and there are no Bash, Azure CLI, or Linux shell equivalents provided for key tasks such as enabling managed identity, assigning roles, or generating access tokens. Even REST API usage is demonstrated via PowerShell, and ARM template deployment is shown only with PowerShell. The only non-PowerShell example is a single Python snippet for token retrieval, but it does not cover the broader workflow. This creates friction for Linux/macOS users who may prefer Bash, Azure CLI, or other native tools.
Recommendations
  • Add equivalent examples using Azure CLI (az) for all major steps: enabling managed identity, assigning roles, verifying assignments, and deploying ARM templates.
  • Provide Bash shell script examples for REST API calls (using curl or httpie) and ARM template deployments.
  • Include instructions for using the Azure portal and Azure CLI on Linux/macOS, clarifying platform-agnostic steps.
  • Where PowerShell is used for file paths or environment variables, note Linux/macOS equivalents (e.g., $HOME, /opt/...).
  • Explicitly state that PowerShell Core is cross-platform and provide installation guidance for non-Windows users if PowerShell must be used.
GitHub Create Pull Request
Automation Deploy an extension-based Windows or Linux User Hybrid Runbook Worker in Azure Automation ...ation/extension-based-hybrid-runbook-worker-install.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows examples, especially PowerShell-based, are presented first and in greater detail. Many code samples, templates, and walkthroughs default to Windows VM creation and management, with Linux-specific instructions often relegated to secondary tabs or brief mentions. Critical sections such as Bicep and ARM templates focus exclusively on Windows VM deployment, with no Linux equivalents or parameterization. Folder permissions and troubleshooting are described in Windows terms, with Linux paths only briefly referenced. PowerShell is the primary automation tool throughout, with limited coverage of Linux-native alternatives.
Recommendations
  • Provide Linux-first or Linux-parallel examples in all code samples, especially for Bicep and ARM templates.
  • Include Linux-specific folder permissions and troubleshooting steps with equal detail as Windows.
  • Expand on Linux prerequisites and supported automation tools (e.g., Bash, Python) beyond PowerShell.
  • Ensure all CLI and REST API examples demonstrate both Windows and Linux extension installation, with explicit parameterization.
  • Add Linux VM creation and onboarding walkthroughs in Bicep/ARM templates.
  • Reference Linux documentation links alongside Windows in 'Next steps' and throughout the page.
GitHub Create Pull Request
Automation Move your Azure Automation account to another subscription ...s/blob/main/articles/automation/how-to/move-account.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed PowerShell cmdlet examples (Remove-AzResource, Remove-AzActionGroup) for resource deletion and management, but does not offer equivalent Azure CLI or REST API examples. This creates friction for Linux/macOS users who are less likely to use PowerShell and more likely to use Azure CLI or REST. The documentation also refers to 'cmdlet', a Windows/PowerShell-centric term, and omits Linux-native tooling or patterns.
Recommendations
  • Add Azure CLI examples for all resource management tasks alongside PowerShell examples.
  • Include REST API sample calls for resource deletion and management.
  • Explicitly mention that PowerShell is cross-platform, but clarify Azure CLI usage for Linux/macOS users.
  • Present examples for both PowerShell and Azure CLI in parallel, or default to CLI where possible.
  • Avoid using Windows-centric terminology (e.g., 'cmdlet') without clarifying cross-platform support.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation mentions PowerShell modules as a prerequisite for local runbook execution, but does not clarify Linux/macOS compatibility or provide equivalent Linux-specific guidance. There are no explicit examples or instructions for Linux/macOS users, and the documentation implicitly assumes a Windows/PowerShell environment.
Recommendations
  • Clarify whether the extension and local runbook execution support Linux/macOS, especially for PowerShell and Python runbooks.
  • Provide explicit instructions for installing required PowerShell modules and Python packages on Linux/macOS, including any platform-specific steps.
  • Include screenshots or examples from Linux/macOS environments to demonstrate parity.
  • Mention any limitations or differences in functionality when using the extension on Linux/macOS.
GitHub Create Pull Request
Automation Manage Runtime Environment and Associated Runbooks in Azure Automation ...main/articles/automation/manage-runtime-environment.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is consistently presented as the primary example for scripting and automation, with detailed instructions and REST API payloads focused on PowerShell runbooks and modules (e.g., Az PowerShell package). Windows-centric tools and patterns, such as PowerShell Gallery and .zip module packaging, are emphasized. Linux/Python support is mentioned but lacks equivalent depth, examples, and guidance. Linux-specific details (such as .whl packaging for Python) are relegated to notes, and there are no concrete Linux or macOS workflow examples, nor parity in troubleshooting or module management instructions.
Recommendations
  • Provide equivalent, detailed examples for Python runbooks, including REST API payloads and portal workflows.
  • Include Linux/macOS-specific instructions for package management, troubleshooting, and runbook execution.
  • Balance screenshots and walkthroughs to show both PowerShell and Python workflows.
  • List Linux/Python options before or alongside Windows/PowerShell options where applicable.
  • Expand notes about Python/Linux packaging to full sections with step-by-step guidance.
  • Add troubleshooting and module management examples for Python runbooks.
GitHub Create Pull Request
Automation Manage databases in Azure SQL databases using Azure Automation ...articles/automation/manage-sql-server-in-automation.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively uses PowerShell cmdlets and patterns, which are native to Windows environments. All code samples and instructions assume the use of PowerShell, with no mention of Bash, Azure CLI, or Linux/macOS-specific workflows. The guidance for installing modules and running commands is tailored to Windows/PowerShell, and there are no Linux or cross-platform alternatives provided.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for connecting and managing Azure SQL databases.
  • Include instructions for installing required modules and running automation tasks on Linux/macOS environments.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and provide alternative steps for Linux/macOS users.
  • Mention cross-platform tools (e.g., az sql commands) alongside PowerShell cmdlets.
  • Reorder examples so that platform-neutral or cross-platform approaches are presented first, or in parallel with Windows/PowerShell methods.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell for all code samples, instructions, and migration steps, with no mention of Bash, CLI, or Linux/macOS-specific workflows. All scripts and cmdlets are PowerShell-based, and references to tools and modules (Az, AzureRM) are Windows-centric. There are no examples or guidance for users who run Azure Automation from Linux/macOS environments or prefer Bash/CLI. The documentation implicitly assumes a Windows/PowerShell environment throughout.
Recommendations
  • Add equivalent Azure CLI (az) examples for authentication and resource management using managed identities.
  • Include notes or sections for Linux/macOS users, clarifying how to run automation tasks and migrate runbooks using Bash or Python.
  • Provide sample scripts in Bash or Python for common migration scenarios.
  • Mention cross-platform compatibility of Azure Automation and clarify when PowerShell is required versus when CLI or other languages can be used.
  • Reorder examples so that CLI/Bash/Linux options are presented alongside or before PowerShell/Windows options where appropriate.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page is heavily focused on using the Azure portal UI, which is cross-platform, but the only next step tutorial provided is for creating a PowerShell runbook, a technology most closely associated with Windows. There is no mention of Linux-native automation options (such as Python runbooks) or CLI-based instructions, and PowerShell is presented as the default for further automation.
Recommendations
  • Include links to tutorials for creating Python runbooks using managed identities, which are more common on Linux.
  • Add examples or references for using Azure CLI or REST API to enable managed identities, providing parity for users who prefer command-line tools on Linux/macOS.
  • Present automation options for both Windows and Linux users in the 'Next steps' section, rather than defaulting to PowerShell.
  • Clarify that PowerShell runbooks can be authored and executed on Linux as well, if applicable, or provide guidance for Linux users.
GitHub Create Pull Request
Automation Azure Quickstart - Install Hybrid Worker extension on Azure portal. ...omation/quickstarts/install-hybrid-worker-extension.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses almost exclusively on installing the Hybrid Worker extension on Windows Azure Virtual Machines. All step-by-step instructions, screenshots, and extension selection refer only to 'Azure Automation Windows Hybrid Worker.' There are no examples, instructions, or screenshots for Linux VMs, nor is the Linux extension mentioned in the installation steps. The prerequisites also only mention a Windows VM, and Windows terminology is used throughout.
Recommendations
  • Add parallel instructions and screenshots for installing the Hybrid Worker extension on Linux Azure Virtual Machines.
  • Explicitly mention the Linux Hybrid Worker extension in the installation steps and extension selection.
  • Update prerequisites to include Linux VMs as supported targets.
  • Present Windows and Linux instructions side-by-side or clearly indicate which steps apply to each OS.
  • Ensure terminology and screenshots are inclusive of both platforms.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias by focusing almost exclusively on PowerShell cmdlets and Windows-centric patterns for credential management in Azure Automation. All CLI examples are in PowerShell, with no Bash, Azure CLI, or Linux-native alternatives. The creation of credentials is described only via the Azure portal or Windows PowerShell, and all code snippets for credential management use PowerShell constructs. There is no mention of Linux shell equivalents, nor are there instructions for managing credentials from non-Windows environments outside of Python runbooks.
Recommendations
  • Add Azure CLI examples for credential management tasks (create, retrieve, delete credentials) that work cross-platform.
  • Include Bash or shell script examples for Linux/macOS users where applicable.
  • Clarify which PowerShell cmdlets are available in PowerShell Core (pwsh) on Linux/macOS, and provide installation guidance if needed.
  • Reorder sections so that cross-platform methods (Azure portal, Azure CLI, REST API) are presented before or alongside Windows PowerShell examples.
  • Explicitly state Linux/macOS compatibility for all procedures, or provide alternative instructions where Windows-only tools are referenced.
GitHub Create Pull Request
Automation Azure Automation overview ...s/azure-docs/blob/main/articles/automation/overview.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Windows-centric tools (such as DSC, PowerShell Gallery, and Microsoft Script Center) are referenced repeatedly and prominently, with little mention of Linux equivalents or parity. Examples and scenarios often focus on Windows technologies (Active Directory, SQL Server, SharePoint), and PowerShell is the only scripting language discussed in detail for configuration management. Linux support is acknowledged, but practical Linux-specific examples, tools, or workflows are missing.
Recommendations
  • Add explicit Linux/bash examples alongside PowerShell for runbooks and configuration management.
  • Mention and link to Linux-native configuration tools (e.g., Ansible, Chef, Puppet) where relevant, or clarify integration options.
  • Provide examples of automating common Linux workloads (e.g., Apache, Nginx, systemd services) in the 'Common scenarios' section.
  • Clarify how Python runbooks can be used for Linux automation, with sample use cases.
  • Balance references to Windows-centric tools (PowerShell Gallery, DSC) with Linux alternatives or cross-platform options.
  • Ensure that onboarding and management instructions for Hybrid Runbook Worker and Arc-enabled servers include Linux-specific steps and troubleshooting.
GitHub Create Pull Request
← Previous Page 13 of 15 Next →