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 801-825 of 982 flagged pages
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for managing certificates in Azure Automation is heavily focused on PowerShell cmdlets and Windows-centric tooling. Most examples and workflows use PowerShell, with only secondary mention of Python. There is no explicit guidance or examples for Linux/macOS users, such as using Azure CLI, Bash, or platform-agnostic certificate management approaches. The reliance on PowerShell and references to Windows cryptographic providers may create friction for non-Windows users.
Recommendations
  • Add equivalent examples using Azure CLI and/or REST API for certificate management tasks.
  • Clarify whether PowerShell cmdlets can be run cross-platform (e.g., via PowerShell Core on Linux/macOS), and provide instructions if so.
  • Include notes or examples for uploading certificates from Linux/macOS systems, including how to prepare .pfx/.cer files and any platform-specific caveats.
  • Mention alternative cryptographic providers if supported, or clarify Windows-only requirements.
  • Ensure that Python examples cover both certificate creation and retrieval, not just access.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance for upgrading TLS, but Windows instructions and PowerShell cmdlets are consistently mentioned first and more prominently. Several backup and data management procedures reference only Windows PowerShell cmdlets, with no equivalent CLI or Linux-native commands provided. This creates friction for Linux/macOS users, who must infer or research their own solutions.
Recommendations
  • When listing platform-specific instructions, alternate the order or present Linux and Windows guidance in parallel sections.
  • For backup/export tasks (runbooks, DSC configurations), provide Azure CLI or REST API examples alongside PowerShell cmdlets, or explicitly state if only PowerShell is supported.
  • Where possible, include Linux/macOS-compatible commands or scripts for asset management and data export.
  • Clarify if certain features (like asset export) are not available on Linux, and suggest alternative approaches for non-Windows users.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation for disaster recovery in Azure Automation is heavily focused on PowerShell scripts and workflows for asset migration, with no mention of Bash, Python, or cross-platform alternatives. While the page states applicability to both Linux and Windows VMs, all migration examples and tooling are PowerShell-centric, and instructions reference Windows tabs and runtime versions first. There are no Linux/macOS-specific examples or guidance for users who prefer or require non-Windows tooling.
Recommendations
  • Provide equivalent Bash or Python scripts for asset migration, or clarify if PowerShell Core (cross-platform) is supported and provide instructions for Linux/macOS environments.
  • Add explicit instructions or examples for running migration scripts on Linux/macOS, including prerequisites and installation steps for PowerShell Core.
  • Reorder or balance examples so that Linux and Windows instructions are presented equally, or in parallel tabs.
  • Clarify any platform limitations (e.g., if only PowerShell is supported, state that PowerShell Core is required and provide installation guidance for Linux/macOS users).
GitHub Create Pull Request
Automation Use Microsoft Entra ID in Azure Automation to authenticate to Azure ...ob/main/articles/automation/automation-use-azure-ad.md
Medium Priority View Details →
Scanned: 2026-01-23 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 and Windows-centric tooling, with all examples and instructions using PowerShell modules and cmdlets. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or Python SDKs. The term 'Windows PowerShell' is used explicitly, and no cross-platform alternatives are mentioned, which may create friction for non-Windows users.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands for credential management and authentication, which are cross-platform.
  • Clarify that PowerShell Core (pwsh) is supported on Linux/macOS and provide examples or notes for running scripts on these platforms.
  • Mention and provide examples for using the Azure SDK for Python or other languages to authenticate with Microsoft Entra ID in Azure Automation.
  • Where 'Windows PowerShell' is referenced, clarify if the steps also apply to PowerShell Core, and if not, provide alternatives.
  • Include a section or callout for Linux/macOS users outlining supported approaches and any limitations.
GitHub Create Pull Request
Automation Configure runbook input parameters in Azure Automation ...b/main/articles/automation/runbook-input-parameters.md
Medium Priority View Details →
Scanned: 2026-01-23 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 is heavily focused on PowerShell and Windows-centric tools and patterns. Most examples, code snippets, and workflows use PowerShell, PowerShell Workflow, or graphical runbooks (which are PowerShell-based). The process of passing parameters, especially with JSON objects, is demonstrated exclusively with PowerShell and Windows-oriented cmdlets. There is minimal coverage of Python runbooks, and no examples or guidance for Linux/macOS users on how to interact with Azure Automation runbooks using native Linux tools or shell scripts. The SDK and REST API sections are platform-neutral, but the practical examples and step-by-step instructions are Windows/PowerShell-centric.
Recommendations
  • Add equivalent examples for starting and passing parameters to runbooks using Bash, Azure CLI, or other Linux-native tools.
  • Provide Python runbook parameter examples that show how to invoke them from Linux/macOS environments, including sample Bash scripts.
  • Clarify which steps are platform-agnostic (e.g., REST API, SDK) and provide explicit Linux/macOS usage instructions where possible.
  • Include notes or sections on how Linux/macOS users can install and use Azure CLI to interact with Azure Automation.
  • Balance the order of examples so that PowerShell and Linux-native approaches are presented with equal prominence.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation for managing credentials in Azure Automation is heavily focused on PowerShell and Windows-centric tooling. All CLI examples are in PowerShell, and references to creating credentials outside the portal are exclusively via Windows PowerShell. There is no mention of Linux/macOS shell equivalents (such as Azure CLI or Bash), nor are there examples for non-Windows environments. Python is covered for runbooks, but only as an alternative scripting language, not for credential management or asset creation from Linux/macOS shells.
Recommendations
  • Add Azure CLI examples for credential asset management, demonstrating how to create, retrieve, and delete credentials from Linux/macOS terminals.
  • Clarify whether credential asset management is possible via Azure CLI or REST API, and provide links or examples if so.
  • Explicitly state any limitations or platform dependencies for credential management, so Linux/macOS users know what is and isn't possible.
  • Reorder sections so that platform-neutral or cross-platform methods (e.g., Azure portal, REST API, Azure CLI) are presented before Windows PowerShell.
  • Include notes or guidance for Linux/macOS users on how to interact with Azure Automation credentials, especially for asset creation and retrieval outside of runbooks.
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-14 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-heavy examples, referencing PowerShell cmdlets for key operations (e.g., key rotation), and listing PowerShell runbooks and tutorials before Python equivalents. There are no CLI or Bash examples for Linux/macOS users, and the documentation does not mention cross-platform alternatives for key management or runbook creation.
Recommendations
  • Add equivalent Azure CLI and Bash examples for key operations (e.g., key rotation) alongside PowerShell commands.
  • Present Python and cross-platform runbook tutorials before or alongside PowerShell tutorials to avoid Windows-first ordering.
  • Explicitly mention that Azure Automation is cross-platform and provide guidance for Linux/macOS users where relevant.
  • Reference documentation for Az CLI and REST API methods for managing Automation accounts and keys.
  • Clarify which steps or tools are platform-agnostic and which are Windows-specific.
GitHub Create Pull Request
Automation Azure Automation FAQ ...e-docs/blob/main/articles/automation/automation-faq.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The FAQ provides more detailed environment variable and path examples for Windows Hybrid Runbook Workers (e.g., referencing C:\Python2\python.exe and specific Windows environment variables), while Linux equivalents are mentioned only briefly and without concrete examples. Windows-specific tooling and patterns are described first and in more detail, with Linux guidance being less explicit and lacking step-by-step instructions.
Recommendations
  • Add explicit Linux examples for environment variable configuration (e.g., show how to set PYTHON_2_PATH and PYTHON_3_PATH in bash or systemd environments).
  • Provide concrete Linux path examples (e.g., /usr/bin/python2, /usr/bin/python3) alongside Windows examples.
  • Describe how the Hybrid Runbook Worker locates Python interpreters on Linux, including fallback mechanisms and typical installation paths.
  • Ensure that Linux instructions are given equal prominence and detail as Windows instructions, possibly by separating sections for each OS or presenting them in parallel.
  • Include troubleshooting steps or references for common Linux-specific issues.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias, primarily through its heavy emphasis on PowerShell as the automation scripting language, frequent references to Windows-centric tools (e.g., registry, Active Directory, SQL Server), and the prioritization of PowerShell examples and modules. While Linux support is mentioned (e.g., in Azure Automanage), there is a lack of parity in examples and tooling references for Linux/macOS users, and Windows patterns are often described first or exclusively.
Recommendations
  • Include explicit Linux/macOS automation examples alongside PowerShell, such as Bash, Python, or Ansible scripts.
  • Highlight Linux-compatible modules and tooling (e.g., systemd, cron, Linux file system paths) in relevant automation scenarios.
  • Balance references to Windows-specific technologies (e.g., registry, Active Directory) with Linux equivalents (e.g., system configuration files, LDAP).
  • Add guidance for Linux users on integrating Azure Automation with common Linux administration tasks.
  • Ensure that tables and scenario descriptions mention both Windows and Linux use cases and users equally.
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-14 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 Windows bias by exclusively providing PowerShell examples for checking and modifying the local authentication setting in Azure Automation. There are no equivalent examples for Linux/macOS users (e.g., using Bash, curl, or Azure CLI), and Windows/PowerShell tools are mentioned first and exclusively for all code snippets and instructions.
Recommendations
  • Add equivalent examples using Bash and curl for REST API calls to update and verify the 'disableLocalAuth' property.
  • Include Azure CLI commands where possible, as they are cross-platform.
  • Explicitly mention that the REST API can be accessed from any OS, and provide sample requests for Linux/macOS users.
  • Reorder examples so that cross-platform solutions (REST API, Azure CLI) are presented before or alongside PowerShell.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed, actionable remediation steps for Windows VMs using PowerShell and the Azure Run Command feature, including specific cmdlets and code examples. In contrast, Linux remediation is described in vague terms, lacks direct script examples, and notes that the Run Command feature is unavailable for Linux. Linux users are referred to external documentation and must re-register or use Python scripts, with no concrete code or step-by-step guidance provided.
Recommendations
  • Provide equivalent, step-by-step Linux remediation instructions directly in the article, including example commands/scripts.
  • Clarify and, if possible, update the status of Run Command support for Linux VMs, or suggest alternative Azure-native mechanisms for Linux.
  • Include direct links to relevant Linux scripts or commands, not just external documentation.
  • Ensure Linux and Windows sections are equally detailed and actionable, with parity in code samples and guidance.
  • Consider listing Linux remediation steps before or alongside Windows steps to avoid 'windows_first' bias.
GitHub Create Pull Request
Automation Deploy an Amazon Web Services VM with an Azure Automation runbook ...icles/automation/automation-scenario-aws-deployment.md
Medium Priority View Details →
Scanned: 2026-01-14 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 and Windows-centric tooling. All examples use PowerShell scripts and modules, with no mention of Linux/macOS alternatives (such as Bash, AWS CLI, or Python). The instructions assume familiarity with PowerShell ISE and Windows authentication patterns, and do not provide guidance for users who prefer or require Linux/macOS environments.
Recommendations
  • Add equivalent examples using AWS CLI and Bash scripts for Linux/macOS users.
  • Include instructions for installing and using the AWS CLI module in Azure Automation, not just PowerShell.
  • Mention cross-platform editors (e.g., VS Code) instead of PowerShell ISE.
  • Clarify whether Azure Automation supports Python or Bash runbooks for AWS provisioning, and provide sample scripts if so.
  • Reorder examples so that cross-platform options are presented alongside or before Windows-specific instructions.
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-14 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 demonstrates a notable Windows bias. PowerShell is consistently emphasized as the primary scripting language, with detailed examples and references to Windows-specific tools (e.g., PowerShell Gallery, Az PowerShell module, Get-Module cmdlet). Windows/PowerShell examples are provided first and in greater detail, while Linux/macOS equivalents are either missing or only briefly mentioned (e.g., Python packages must be .whl for Linux, but no further Linux-specific guidance is given). There are no examples of Linux shell scripting, nor are Linux-native tools or workflows discussed.
Recommendations
  • Provide equivalent examples for Linux/macOS users, such as using Bash or Python scripts.
  • Include instructions for uploading and managing Python packages with Linux-specific details (e.g., .whl files, pip usage, troubleshooting on Linux).
  • Mention Linux-native automation tools or patterns where relevant, and clarify cross-platform compatibility.
  • Balance the order and depth of examples so that PowerShell and Python/Linux workflows are treated equally.
  • Add screenshots or walkthroughs from Linux/macOS environments where possible.
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-14 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 exclusively uses PowerShell for all examples and instructions, with no mention of Bash, CLI, or Linux/macOS-specific workflows. All code samples, prerequisites, and resource management steps rely on PowerShell cmdlets and patterns, which are native to Windows. There are no Linux or cross-platform alternatives provided, and the use of PowerShell is assumed throughout, creating friction for users on Linux or macOS.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for each major step (Key Vault creation, secret management, role assignment, runbook creation, cleanup).
  • Explicitly state that PowerShell is available cross-platform, but also offer instructions for Linux/macOS environments.
  • Include notes or sections for Linux/macOS users, highlighting any differences or additional requirements.
  • Add links to Azure CLI documentation and reference CLI commands alongside PowerShell cmdlets.
  • Consider showing CLI/Bash examples before or alongside PowerShell to avoid Windows-first bias.
GitHub Create Pull Request
Automation Manage Python 2 packages in Azure Automation ...-docs/blob/main/articles/automation/python-packages.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides explicit instructions for downloading Python packages and dependencies only on Windows, with no equivalent Linux/macOS guidance. The command-line example uses Windows paths and tools, and the text specifies using a Windows 64-bit machine, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent instructions and examples for Linux/macOS users, such as using 'pip download' on Linux.
  • Present platform-neutral commands and clarify that the process works on any OS with Python and pip installed.
  • Avoid specifying Windows as the only supported platform unless truly required.
  • Include screenshots or CLI examples for Linux/macOS where appropriate.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows/PowerShell tools and patterns are referenced first or exclusively in several sections, especially for Python 3.8. Linux equivalents are present for Python 3.10, but for Python 3.8, instructions and examples are Windows-centric (e.g., using Windows machines for wheel generation, PowerShell cmdlets for package management). There are no Linux CLI or shell examples for managing packages, and PowerShell is presented as the primary automation tool for Python 3.8 package management.
Recommendations
  • Provide Linux/macOS equivalents for all Windows/PowerShell instructions, especially for Python 3.8 (e.g., show how to generate wheels and manage packages on Linux).
  • Include CLI or shell commands for package management alongside PowerShell cmdlets.
  • Present Linux and Windows instructions in parallel or in tabs, rather than Windows-first.
  • Clarify which steps are OS-agnostic and which require a specific platform.
  • Add explicit guidance for Linux/macOS users on Hybrid Runbook Workers, including troubleshooting and environment setup.
GitHub Create Pull Request
Automation Remove user-assigned managed identity for Azure Automation account ...n/articles/automation/remove-user-assigned-identity.md
Medium Priority View Details →
Scanned: 2026-01-14 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 only PowerShell-based CLI examples for scripting and REST API invocation, with no mention of Linux/macOS shell alternatives (such as Bash, curl, or Azure CLI). PowerShell is presented as the default/only scripting environment for automation tasks, and Windows-centric tools are referenced exclusively. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native shell tools.
Recommendations
  • Add equivalent Bash/curl and Azure CLI examples for all scripting sections, especially for REST API calls and automation tasks.
  • Explicitly mention that PowerShell examples can be run cross-platform, or provide guidance for installing PowerShell on Linux/macOS if required.
  • Present examples for both Windows (PowerShell) and Linux/macOS (Bash/curl/Azure CLI) side-by-side, or indicate which examples are platform-agnostic.
  • Reference Linux/macOS tools and patterns where appropriate, such as using curl for REST API requests and jq for JSON parsing.
GitHub Create Pull Request
Automation Use Source Control Integration in Azure Automation ...main/articles/automation/source-control-integration.md
Medium Priority View Details →
Scanned: 2026-01-14 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 by exclusively providing PowerShell-based examples and instructions for configuring source control integration in Azure Automation. There are no CLI, Bash, or cross-platform alternatives shown, and all automation scripting references are to PowerShell (which is natively Windows-centric, especially PowerShell 5.1). Windows tools and patterns (elevated PowerShell console, PowerShell cmdlets) are mentioned first and exclusively, with no mention of Linux/macOS equivalents or guidance for those platforms.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for configuring source control, assigning roles, and updating PATs.
  • Clarify whether PowerShell Core (cross-platform) is supported, and if so, provide examples for Linux/macOS environments.
  • Explicitly mention any platform limitations and offer workarounds or alternatives for Linux/macOS users.
  • Include screenshots or step-by-step instructions for Linux/macOS terminal usage where applicable.
  • Add a section comparing PowerShell and CLI approaches, helping users choose the best method for their OS.
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-14 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 and Windows-centric tools and patterns. All troubleshooting steps and code examples use PowerShell cmdlets and scripts, with no mention of Bash, Azure CLI, or Linux/macOS equivalents. Windows-specific terminology (DLLs, PowerShell modules) is used exclusively, and Linux alternatives or cross-platform guidance are absent.
Recommendations
  • Provide equivalent troubleshooting steps using Azure CLI and Bash for Linux/macOS users.
  • Include examples and instructions for managing modules and authentication using cross-platform tools.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and offer alternatives where possible.
  • Add notes or sections addressing Linux/macOS users, especially for error messages and automation tasks.
  • Reference documentation for Linux/macOS automation environments when discussing module import and runbook execution.
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-14 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 is heavily biased towards Windows and PowerShell usage. All command-line examples use PowerShell cmdlets, and there are no equivalent Bash, Azure CLI, or Linux shell examples. REST API and ARM template sections still rely on PowerShell for invocation. Even generic HTTP token retrieval is shown only with PowerShell, with no curl or Bash alternatives. The only non-PowerShell example is a Python script, but it does not address shell usage for Linux/macOS users. This creates friction for users on Linux or macOS who do not use PowerShell.
Recommendations
  • Provide Azure CLI (az) examples alongside PowerShell for all resource management and identity assignment tasks.
  • Show REST API invocation using curl or httpie in addition to PowerShell's Invoke-RestMethod.
  • Include Bash shell script examples for environment variable usage and token retrieval.
  • Clarify that PowerShell cmdlets can be run cross-platform, but also offer native Linux/macOS alternatives.
  • Reorder examples so that platform-neutral or cross-platform methods (portal, REST, ARM template) are presented before PowerShell.
  • Explicitly mention Linux/macOS compatibility and provide troubleshooting tips for those platforms.
GitHub Create Pull Request
Automation Manage connections in Azure Automation ...lob/main/articles/automation/automation-connections.md
Medium Priority View Details →
Scanned: 2026-01-14 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 notable Windows bias. PowerShell cmdlets are emphasized throughout, with detailed examples and tables dedicated to their usage. The 'Create a new connection' section provides a step-by-step guide for Windows PowerShell but omits equivalent CLI or scripting examples for Linux/macOS users (e.g., Azure CLI, Bash). Windows tools and patterns (PowerShell, cmdlets) are mentioned first and in greater detail, while Linux alternatives are missing or only briefly referenced (Python functions). There are no examples using Azure CLI, Bash, or cross-platform scripting, and the graphical runbook instructions are also Windows-centric.
Recommendations
  • Add equivalent examples using Azure CLI and Bash for creating and managing connections, especially in the 'Create a new connection' section.
  • Present Linux/macOS-friendly instructions and tools alongside PowerShell, not after or instead of them.
  • Include cross-platform scripting guidance for runbooks, such as using Python or REST API calls.
  • Explicitly state which steps/tools are platform-agnostic and which are Windows-specific.
  • Reorder examples so that platform-neutral or Linux/macOS options are presented equally or first where possible.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a notable Windows bias, primarily through exclusive use of PowerShell scripts and workflows for migration tasks, with no mention of Bash, Python, or Linux-native alternatives. All migration examples and tooling are PowerShell-based, and instructions reference Windows tabs and tools first. Linux users are left without platform-specific guidance, despite the page claiming applicability to Linux VMs.
Recommendations
  • Provide equivalent Bash or Python scripts for migration tasks, or clarify cross-platform compatibility of PowerShell Core (pwsh) on Linux/macOS.
  • Explicitly document how Linux/macOS users can execute migration scripts, including prerequisites for PowerShell installation on non-Windows systems.
  • Add examples and instructions for using Linux-native tools (e.g., Azure CLI, Bash) where possible.
  • Ensure that tabs and instructions do not default to Windows or PowerShell unless alternatives are unavailable.
  • Clarify any platform-specific limitations or requirements for hybrid worker installation and runbook execution.
GitHub Create Pull Request
Automation Create configurations from existing servers for Azure Automation State Configuration ...ticles/automation/automation-dsc-config-from-server.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows and PowerShell, with all examples and references centered around Windows PowerShell DSC and SharePointDSC, which are Windows-specific technologies. There is no mention of Linux/macOS equivalents, and steps or tooling for Linux users are absent or relegated to links without detail.
Recommendations
  • Add explicit instructions or examples for Linux/macOS users, including how to generate and upload configurations from non-Windows servers.
  • Clarify which steps or tools (such as ReverseDSC) are Windows-only and provide alternatives or workarounds for Linux environments.
  • Include references to cross-platform DSC resources, such as those available for Linux, and show parity in documentation structure.
  • Ensure that onboarding and configuration steps for Linux machines are described in equal detail as for Windows.
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-14 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 by exclusively using PowerShell for all code examples, referencing Windows-centric tools and modules, and omitting any Linux/macOS CLI or scripting alternatives. The prerequisites and instructions assume the use of PowerShell and Windows VMs, with no mention of Bash, Azure CLI, or Linux VM management. This creates friction for users on Linux or macOS platforms who may prefer or require non-PowerShell solutions.
Recommendations
  • Provide equivalent examples using Azure CLI (az) commands for all PowerShell scripts, especially for role assignment and VM management.
  • Include instructions for managing both Windows and Linux VMs, with links to Linux-specific quickstart guides.
  • Clarify that Azure Automation runbooks can be authored in Python and/or use Bash scripts, and provide sample runbooks in those languages.
  • List prerequisites for Linux/macOS users, such as installing Azure CLI, and provide links to relevant documentation.
  • Order examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
  • Explicitly state platform compatibility for each step and tool.
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-14 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 oriented toward Windows environments, with all examples and instructions using PowerShell and Windows-style paths (e.g., D:\examplefiles). There are no Linux/macOS equivalents provided for file creation, folder paths, or hybrid worker setup. The only tooling mentioned is PowerShell, and the workflow assumes Windows conventions throughout.
Recommendations
  • Provide equivalent Linux/macOS examples for file creation (e.g., using Bash: 'touch ExampleFile1.txt').
  • Clarify whether hybrid runbook workers can run on Linux, and if so, include setup instructions for Linux-based workers.
  • Show folder path examples using Linux conventions (e.g., '/home/examplefiles') alongside Windows paths.
  • Mention and provide examples for using Azure Automation with Python or Bash runbooks, if supported.
  • Explicitly state platform limitations and alternatives for non-Windows users.
GitHub Create Pull Request
← Previous Page 33 of 40 Next →