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 876-900 of 982 flagged pages
Automation Azure Automation FAQ ...e-docs/blob/main/articles/automation/automation-faq.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, especially in sections discussing Hybrid Runbook Workers and Python environment configuration. Windows-specific environment variables and file paths are described in detail, while Linux equivalents are only briefly mentioned or omitted. Examples and instructions for Windows precede or overshadow Linux guidance, and there are no explicit Linux command or configuration examples.
Recommendations
  • Provide explicit Linux examples for configuring Python environment variables, including typical Linux file paths and environment variable usage.
  • Include instructions or examples for locating Python interpreters on Linux Hybrid Runbook Workers, such as referencing /usr/bin/python3 or using $PATH.
  • Ensure parity in troubleshooting and configuration guidance for both Windows and Linux environments.
  • When listing steps or examples, alternate or parallelize Windows and Linux instructions to avoid Windows-first presentation.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-13 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 demonstrates a notable Windows bias. All migration scripts and runbook examples are provided exclusively in PowerShell and PowerShell Workflow, which are Windows-centric tools. There are no equivalent Bash, Python, or Linux-native script examples for migrating Automation account assets. The instructions and tabs for Hybrid Runbook Worker installation and migration reference Windows first and do not provide Linux-specific guidance or parity. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native Linux tools.
Recommendations
  • Provide equivalent migration scripts in Bash or Python for Linux/macOS users.
  • Include Linux-specific instructions and examples alongside Windows, especially for Hybrid Runbook Worker installation and migration.
  • Add guidance on using cross-platform tools (e.g., Azure CLI, REST API) for asset migration.
  • Ensure that examples and tabs do not default to Windows/PowerShell first; present Linux options equally.
  • Clarify any platform-specific limitations and offer workarounds for non-Windows environments.
GitHub Create Pull Request
Automation Run Azure Automation Runbooks on a Hybrid Runbook Worker ...ain/articles/automation/automation-hrw-run-runbooks.md
Medium Priority View Details →
Scanned: 2026-01-13 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 demonstrates a moderate Windows bias. Windows instructions, examples, and tool references (e.g., PowerShell, Windows environment variable setup, certificate management) are presented first and in greater detail. PowerShell-based workflows dominate authentication and runbook management sections, with Linux equivalents often described later, more briefly, or omitted (e.g., no Linux example for starting runbooks via CLI, no Linux credential asset support). Windows-specific tools and paths are referenced more frequently, and some features (like Hybrid Worker Credentials) are unsupported on Linux, but this is noted.
Recommendations
  • Provide Linux/Bash examples for starting runbooks and authentication workflows, not just PowerShell.
  • Include Linux-first or side-by-side instructions for environment variable setup, credential management, and certificate/key management.
  • Clarify parity and limitations for Linux Hybrid Workers, especially where features are Windows-only (e.g., credential assets, signed runbooks).
  • Reference Linux tools and commands (e.g., OpenSSL, Bash scripting) where Windows uses PowerShell or certutil.
  • Ensure troubleshooting and logging sections include Linux-specific guidance and examples.
  • Where PowerShell is required, note cross-platform support and alternatives for Linux users.
GitHub Create Pull Request
Automation Handle errors in Azure Automation graphical runbooks ...omation/automation-runbook-graphical-error-handling.md
Medium Priority View Details →
Scanned: 2026-01-13 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 Windows PowerShell, with all examples, terminology, and cmdlets being Windows-centric. There is no mention of Linux or cross-platform alternatives, nor are Bash or Python examples provided. The error handling logic and recommended practices are described exclusively in terms of PowerShell activities and cmdlets, which may not be directly applicable to Linux/macOS users or hybrid environments.
Recommendations
  • Add explicit notes on Linux/macOS support for Azure Automation graphical runbooks, clarifying any platform limitations.
  • Provide equivalent examples using Bash, Python, or other supported languages for error handling in graphical runbooks.
  • Mention cross-platform cmdlets or tools where available, and clarify if PowerShell Core (pwsh) is supported on non-Windows platforms.
  • Reorder examples or sections to avoid always presenting Windows/PowerShell first, or provide parallel examples for each platform.
  • List any prerequisites or platform-specific behaviors that Linux/macOS users should be aware of.
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-13 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 Windows and PowerShell, with all examples and instructions using PowerShell cmdlets and Windows-specific modules. There are no references to Bash, CLI, or Linux/macOS equivalents, and Windows terminology (e.g., 'Windows PowerShell') is used throughout. This creates friction for Linux/macOS users who may prefer or require cross-platform tools.
Recommendations
  • Add equivalent examples using Azure CLI and Bash for credential management and runbook automation.
  • Clarify which steps and modules are cross-platform (e.g., Az PowerShell module vs. Windows-only modules).
  • Provide guidance for Linux/macOS users, including how to install and use the Az module or Azure CLI on those platforms.
  • Rephrase sections to avoid Windows-first terminology (e.g., use 'PowerShell' instead of 'Windows PowerShell' where appropriate).
  • Include links to Linux/macOS setup guides for Azure Automation and authentication.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides command-line examples exclusively using Azure PowerShell cmdlets (Remove-AzResource, Remove-AzActionGroup), with no equivalent Azure CLI or REST API examples. This creates friction for Linux/macOS users, who are more likely to use Azure CLI or REST API. The portal instructions are platform-neutral, but all automation examples are Windows-centric.
Recommendations
  • Add equivalent Azure CLI examples for resource and action group removal (e.g., az resource delete, az monitor action-group delete).
  • Include REST API example snippets for resource deletion and workspace unlinking.
  • Explicitly mention that PowerShell is available cross-platform, but recommend CLI for Linux/macOS users.
  • Order examples so that CLI and PowerShell are presented together or alternate which is shown first.
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-13 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 is heavily biased towards Windows and PowerShell. All code samples, walkthroughs, and examples use PowerShell cmdlets and Windows-centric tooling (e.g., Az Module, Invoke-WebRequest, file paths with backslashes). There are no examples for Linux/macOS users, such as using Bash, curl, or Azure CLI. REST API usage is also shown only via PowerShell, not with cross-platform tools. 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 invocation and REST API calls.
  • Show how to use Azure CLI to create and manage webhooks and runbooks.
  • Include Linux/macOS file path conventions in examples (forward slashes).
  • Explicitly mention cross-platform alternatives to PowerShell, and clarify which steps require PowerShell and which can be done with other tools.
  • Add notes or sections for Linux/macOS users, highlighting any differences or requirements.
GitHub Create Pull Request
Automation Quickstart: Use Terraform to create an Azure Automation account ...ickstarts/create-azure-automation-account-terraform.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell verification steps, but PowerShell is given equal prominence and is referenced in the 'Next steps' section. The final tutorial link specifically references PowerShell runbooks, which are Windows-centric. There are no Linux/macOS-specific examples or notes, and PowerShell is not flagged as Windows-only, potentially implying parity where it may not exist.
Recommendations
  • Add explicit notes clarifying platform compatibility for Azure PowerShell, especially for Linux/macOS users.
  • Include Bash shell examples for verification steps, not just Azure CLI and PowerShell.
  • In 'Next steps', provide links to tutorials for both PowerShell and Python runbooks, ensuring Linux users have a clear path.
  • If PowerShell is not fully supported on Linux/macOS for certain tasks, state this clearly.
  • Consider ordering CLI examples before PowerShell, as CLI is cross-platform.
GitHub Create Pull Request
Automation Use Azure Private Link to securely connect networks to Azure Automation ...in/articles/automation/how-to/private-link-security.md
Medium Priority View Details →
Scanned: 2026-01-13 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 moderate Windows bias. The only code example provided for configuring public network access uses PowerShell, with no equivalent CLI, Bash, or REST API example for Linux/macOS users. The State Configuration section references PowerShell Desired State Configuration (DSC) without mentioning Linux alternatives or cross-platform configuration tools. While the page notes that Update Management supports both Windows and Linux, practical examples and tooling references are Windows-centric. The Azure portal instructions are platform-neutral, but scripting and automation guidance favor Windows.
Recommendations
  • Provide equivalent Azure CLI, Bash, or REST API examples alongside PowerShell scripts for configuring Automation account properties.
  • Explicitly mention and link to cross-platform configuration management options for Linux nodes (e.g., Ansible, Chef, or native Linux DSC support if available).
  • Include Linux/macOS-specific guidance or screenshots where relevant, especially for agent installation and configuration.
  • Clarify any platform-specific limitations or differences in features and setup steps.
GitHub Create Pull Request
Automation Azure Automation overview ...s/azure-docs/blob/main/articles/automation/overview.md
Medium Priority View Details →
Scanned: 2026-01-13 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 for Azure Automation demonstrates a moderate Windows bias. PowerShell and Windows-centric tools (e.g., DSC, PowerShell Gallery, Microsoft Script Center) are mentioned more frequently and in greater detail than their Linux equivalents. Examples and terminology (such as runbooks, DSC, modules) are primarily Windows/PowerShell-focused, with Linux support referenced only in passing or as an afterthought. There are no Linux-specific examples, tools, or workflows highlighted, and the documentation does not provide parity in guidance for Linux users.
Recommendations
  • Add explicit Linux examples for runbooks, configuration management, and automation scenarios (e.g., Bash, Python, Ansible).
  • Mention and link to Linux-native tools and patterns (such as Ansible, shell scripting, cron jobs) alongside PowerShell and DSC.
  • Provide step-by-step guides or references for onboarding Linux machines, including common Linux automation use cases.
  • Ensure that shared resources and modules sections include Linux-relevant content (e.g., Python package management, Linux-specific modules).
  • Balance the order of presentation so that Linux and Windows are treated equally, rather than Windows-first.
GitHub Create Pull Request
Automation Use Source Control Integration in Azure Automation ...main/articles/automation/source-control-integration.md
Medium Priority View Details →
Scanned: 2026-01-13 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 strong Windows bias by exclusively providing PowerShell-based examples and instructions for source control integration in Azure Automation. All command-line guidance relies on Azure PowerShell, with no mention of Bash, Azure CLI, or Linux/macOS-specific workflows. The prerequisites, configuration, and troubleshooting sections assume familiarity with Windows tools and patterns, and do not offer Linux or cross-platform alternatives.
Recommendations
  • Add equivalent examples using Azure CLI and Bash for configuring managed identities, assigning roles, and connecting source control.
  • Explicitly state platform compatibility for PowerShell cmdlets and provide guidance for installing PowerShell Core on Linux/macOS if required.
  • Include notes or sections for Linux/macOS users, highlighting any differences or additional steps needed.
  • Where possible, provide REST API examples and curl commands for source control operations.
  • Reorder examples to present cross-platform or platform-neutral options first, or side-by-side.
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-13 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 strong bias toward Windows and PowerShell. All command-line examples use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux-native tools. Even REST API usage is shown exclusively via PowerShell, and verification steps rely on PowerShell cmdlets. There are no Linux/macOS shell examples, and Windows/PowerShell tooling is referenced first and exclusively throughout.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, including authentication, resource modification, and verification.
  • Show REST API invocation using curl or HTTPie in Bash, including how to obtain an access token via Azure CLI.
  • Include notes or sections for Linux/macOS users, clarifying cross-platform compatibility and providing alternative commands.
  • When referencing tools or scripting, present Azure CLI/Bash examples before or alongside PowerShell to avoid Windows-first bias.
  • Mention that PowerShell Core is cross-platform, but still provide native shell examples for parity.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation managed identity issues ...n/articles/automation/troubleshoot/managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-13 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 biased towards Windows and PowerShell environments. All troubleshooting examples and code snippets use PowerShell cmdlets (e.g., Connect-AzAccount, Get-AzVM), and there are no equivalent instructions or examples for Linux/macOS users (such as Bash, Azure CLI, or Python SDK). The troubleshooting steps assume the use of Windows-based Automation runbooks and tools, and do not mention Linux alternatives or cross-platform considerations.
Recommendations
  • Add troubleshooting examples using Azure CLI (az) commands and Bash scripts for Linux/macOS users.
  • Include guidance for using Python SDK or REST API for managed identity authentication in runbooks.
  • Explicitly state platform requirements for each scenario, and provide parity instructions for Linux/macOS environments.
  • Where PowerShell is used, offer equivalent code snippets for Bash/Azure CLI.
  • Clarify whether Hybrid Runbook Workers can run on Linux, and provide Linux-specific troubleshooting steps if applicable.
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 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 by focusing exclusively on Windows PowerShell for command-line examples and automation, with no mention of cross-platform alternatives such as Azure CLI, Bash, or PowerShell Core. All code samples use Windows PowerShell syntax, and references to command-line automation are tied to Windows tools. Linux/macOS users are not provided with equivalent examples or guidance, which may hinder their ability to follow the documentation effectively.
Recommendations
  • Add Azure CLI examples for starting and managing runbooks, as Azure CLI is cross-platform.
  • Include PowerShell Core examples and clarify compatibility with Linux/macOS environments.
  • Explicitly mention how Linux/macOS users can perform equivalent tasks, including any required setup or authentication differences.
  • Reorder or balance examples so that Windows and Linux/macOS methods are presented with equal prominence.
  • Reference Bash scripting or REST API usage from Linux/macOS environments, with sample code.
GitHub Create Pull Request
Automation Using a user-assigned managed identity for an Azure Automation account ...main/articles/automation/add-user-assigned-identity.md
Medium Priority View Details →
Scanned: 2026-01-13 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 workflows and examples, which are most commonly used and supported on Windows. All CLI examples use PowerShell cmdlets, and even REST API and ARM template deployment steps are shown using PowerShell. There are no Bash, Azure CLI, or Linux-native shell examples, nor are cross-platform alternatives mentioned. The Python example is limited to runbook usage and does not cover setup or deployment steps. The documentation implicitly assumes users are on Windows or have PowerShell available, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell cmdlets shown, especially for resource creation, identity assignment, and role assignment.
  • Show REST API invocation examples using curl or httpie, which are standard on Linux/macOS.
  • For ARM template deployment, provide Azure CLI (az deployment group create) commands alongside PowerShell.
  • Clarify cross-platform support for PowerShell Core and note any OS-specific limitations.
  • Present examples in a platform-neutral order (e.g., Azure portal, Azure CLI, PowerShell, REST API), or group them by platform.
  • Explicitly mention that PowerShell examples can be run on Linux/macOS with PowerShell Core, or provide links to installation instructions.
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-13 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 (e.g., Start-AzAutomationRunbook, Disable-AzContextAutosave), with all code examples in PowerShell and references to Windows PowerShell. There are no Bash, Python, or Linux-native examples, nor any mention of Linux/macOS-specific considerations. The documentation assumes users are working in a PowerShell environment, which is more common on Windows, and does not address how to achieve similar functionality from Linux/macOS or using other scripting languages.
Recommendations
  • Add equivalent examples using Bash, Python, or other cross-platform scripting languages supported by Azure Automation.
  • Explicitly mention Linux/macOS compatibility for PowerShell scripts and modules, or provide guidance for running these scripts on non-Windows platforms (e.g., PowerShell Core, Azure CLI).
  • Include references to Azure CLI commands for starting runbooks, as CLI is cross-platform and widely used on Linux/macOS.
  • Clarify any platform-specific limitations or requirements (e.g., differences in PowerShell versions, module availability).
  • Reorder examples or sections so that Windows and Linux/macOS approaches are presented with equal prominence.
GitHub Create Pull Request
Automation Use an alert to trigger an Azure Automation runbook ...utomation/automation-create-alert-triggered-runbook.md
Medium Priority View Details →
Scanned: 2026-01-13 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 is heavily focused on PowerShell, with all code examples and instructions using PowerShell cmdlets. Prerequisites and links reference Windows-centric resources (such as creating VMs with PowerShell), and there are no Bash, CLI, or Linux/macOS-specific examples. The instructions assume the use of PowerShell both locally and in runbooks, with no mention of alternatives like Python runbooks or Azure CLI. This creates friction for Linux/macOS users who may not use PowerShell as their primary automation tool.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all PowerShell scripts and steps.
  • Reference Linux/macOS VM creation guides alongside Windows guides in prerequisites.
  • Include instructions for creating Python runbooks, or at least mention their availability.
  • Clarify that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical) and provide links to relevant documentation.
  • Ensure that links to VM creation and management cover both Windows and Linux scenarios.
  • Where PowerShell modules are required, note how to install them on Linux/macOS (e.g., via PowerShell Core).
GitHub Create Pull Request
Automation Manage connections in Azure Automation ...lob/main/articles/automation/automation-connections.md
Medium Priority View Details →
Scanned: 2026-01-13 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 notable Windows bias. PowerShell and Az module cmdlets are emphasized throughout, with detailed examples and step-by-step instructions for creating and managing connections using Windows PowerShell. The 'Create a new connection' section provides a PowerShell example but omits equivalent CLI or Linux-native instructions. The Python section is present, but there are no bash, Azure CLI, or Linux-specific examples. Windows tools and patterns (PowerShell, cmdlets) are mentioned first and exclusively in several sections, with no parity for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for creating and managing connections, especially in sections currently showing only PowerShell.
  • Include bash or shell script examples for common tasks, such as retrieving or creating connection assets.
  • Clarify which instructions are cross-platform and which are Windows-specific; provide alternatives for Linux/macOS users.
  • Mention and link to Linux/macOS compatible tools and modules where relevant.
  • Reorder examples so that platform-neutral or cross-platform solutions are presented first, or in parallel tabs.
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-13 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 tailored to Windows PowerShell DSC. Linux is only mentioned in passing, with no concrete examples or guidance for Linux users. The tools and workflows described (ReverseDSC, SharePointDSC) are Windows-centric, and there is no information on how to achieve similar outcomes on Linux or macOS platforms.
Recommendations
  • Add explicit examples and workflows for Linux/macOS systems, including how to extract configurations and generate MOF files from Linux servers.
  • Clarify whether ReverseDSC or similar tools support Linux, and if not, suggest alternative approaches or community projects for Linux users.
  • Include links to Linux DSC resources and documentation, and provide step-by-step instructions for Linux environments.
  • Balance references to Windows PowerShell with equivalent instructions for PowerShell Core on Linux/macOS where possible.
GitHub Create Pull Request
Automation Edit textual runbooks in Azure Automation ...articles/automation/automation-edit-textual-runbook.md
Medium Priority View Details →
Scanned: 2026-01-13 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 Windows and PowerShell, with all command-line examples using Windows PowerShell and Windows file paths. There are no examples or guidance for Linux/macOS users, such as using PowerShell Core (pwsh), cross-platform file paths, or Azure CLI alternatives. The use of 'Windows PowerShell' is explicit, and Windows-centric tools and patterns are presented exclusively.
Recommendations
  • Add examples using PowerShell Core (pwsh) that work on Linux/macOS, including appropriate file path syntax.
  • Clarify which commands and modules are cross-platform and which are Windows-only.
  • Provide Azure CLI or REST API alternatives for runbook management, which are natively cross-platform.
  • Explicitly mention support for Linux/macOS and provide troubleshooting notes for non-Windows environments.
  • Reorder examples so that cross-platform options are presented before or alongside Windows-specific instructions.
GitHub Create Pull Request
Automation Configure data at scale for Azure Automation State Configuration ...cles/automation/automation-dsc-config-data-at-scale.md
Medium Priority View Details →
Scanned: 2026-01-13 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 PowerShell and PowerShell DSC, with all examples and references tailored to Windows environments. There is no mention of Linux/macOS equivalents or guidance for non-Windows users, despite Azure Automation DSC supporting Linux nodes. References and next steps are exclusively Windows/PowerShell-centric, and Linux onboarding is only briefly mentioned in a link.
Recommendations
  • Add explicit examples and steps for configuring data at scale for Linux/macOS nodes using Azure Automation DSC.
  • Include references to Linux DSC resources and documentation, such as onboarding Linux machines and using cross-platform DSC modules.
  • Clarify which steps or tools are Windows-only and provide Linux alternatives where possible.
  • Balance the next steps section with links to Linux DSC documentation and resources.
GitHub Create Pull Request
Automation Integrate Azure Automation State Configuration with Azure Monitor Logs ...main/articles/automation/automation-dsc-diagnostics.md
Medium Priority View Details →
Scanned: 2026-01-13 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 code examples and setup instructions using PowerShell cmdlets. There are no CLI, Bash, or Linux/macOS-specific instructions or examples. The prerequisites and workflow assume the use of PowerShell, which is native to Windows and less common on Linux/macOS. References to modules and troubleshooting are also PowerShell-specific, and there is no mention of Linux/macOS alternatives or parity.
Recommendations
  • Provide equivalent instructions and examples using Azure CLI (az) and Bash, which are cross-platform and native to Linux/macOS.
  • Explicitly mention how Linux/macOS users can install and use PowerShell Core (pwsh) if PowerShell is required, or clarify if Azure CLI is sufficient.
  • Add troubleshooting and setup steps for Linux/macOS environments, including any platform-specific caveats.
  • Ensure that examples are presented for both Windows (PowerShell) and Linux/macOS (CLI/Bash), or at least clarify platform requirements at the start.
  • Reference Linux-compatible DSC modules or note any limitations due to the retirement of Linux DSC support.
GitHub Create Pull Request
Automation Azure Automation State Configuration overview ...ob/main/articles/automation/automation-dsc-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 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 DSC concepts are emphasized throughout, with Windows operating systems and tools (e.g., WinRM, WMF) described in detail and listed first. Linux support is mentioned but lacks equivalent detail, examples, or tool explanations. Proxy support, DSC requirements, and onboarding instructions are more thoroughly documented for Windows, while Linux guidance is brief and often refers out to other documentation.
Recommendations
  • Provide Linux-specific examples for onboarding, configuration, and troubleshooting, similar to the Windows sections.
  • Include Linux distributions explicitly in the operating system requirements, rather than referring to external documentation.
  • Describe Linux DSC agent installation and configuration steps in detail, matching the depth given for Windows (e.g., proxy setup, required packages, service management).
  • Offer parity in example scripts and commands, including Bash or shell snippets alongside PowerShell.
  • Clarify any feature gaps or differences between Windows and Linux support, especially in areas like proxy support and reporting.
GitHub Create Pull Request
Automation Enable Azure Automation State Configuration .../main/articles/automation/automation-dsc-onboarding.md
Medium Priority View Details →
Scanned: 2026-01-13 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 demonstrates a notable Windows bias. Most configuration and onboarding examples use PowerShell scripts and cmdlets, with detailed step-by-step instructions for Windows. Linux enablement is described, but with less detail and often requires using Windows tools (PowerShell, WMF 5) to generate configurations for Linux machines. Native Linux tooling and workflows are minimally covered, and Linux-specific examples are less comprehensive.
Recommendations
  • Provide Linux-first onboarding instructions that do not require a Windows machine or PowerShell/WMF 5 for Linux node enablement.
  • Expand Linux sections with native Bash/shell examples for generating and applying metaconfigurations.
  • Include parity in step-by-step guides for both Windows and Linux, ensuring Linux users can follow along without switching to Windows tools.
  • Highlight Linux-specific tools and workflows (e.g., using Python scripts or shell commands) before or alongside Windows/PowerShell examples.
  • Clarify when steps are Windows-only and offer equivalent Linux-native alternatives where possible.
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-13 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 prioritizes Windows remediation steps, providing a clear PowerShell example and direct guidance for Windows VMs. In contrast, Linux remediation is described in less detail, lacks a direct script example, and refers users to external documentation. The use of Windows tools and cmdlets is emphasized, while Linux users are told they cannot use the same Azure Run Command feature and are directed to more complex or external processes.
Recommendations
  • Provide a direct Linux script example for correcting drift, similar to the PowerShell example for Windows.
  • Clarify and expand the Linux remediation steps within this page, rather than referring users to external documentation.
  • If possible, mention any equivalent Azure features for Linux, or clearly state limitations and suggest best practices.
  • Balance the order of presentation by either starting with a general overview or alternating which platform is described first.
  • Include links to Linux-specific tools or scripts as prominently as Windows/PowerShell references.
GitHub Create Pull Request
← Previous Page 36 of 40 Next →