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 26-50 of 365 flagged pages
Automation Manage runbooks in Azure Automation ...-docs/blob/main/articles/automation/manage-runbooks.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for managing runbooks in Azure Automation exhibits a strong Windows bias. All code examples use PowerShell, with Windows-style file paths and cmdlets, and there are no Bash, CLI, or Linux/macOS-specific instructions or examples. Windows tools and patterns (such as PowerShell Workflow, .ps1 files, and Windows file paths) are mentioned exclusively or before any Linux equivalents. The documentation does not provide parity for Linux/macOS users, who may prefer Bash, Azure CLI, or Python for automation tasks.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all key operations (create, import, publish, retrieve job status, etc.).
  • Include Linux/macOS-specific instructions for file paths, script execution, and environment setup.
  • Clarify which steps and tools are cross-platform and which are Windows-only.
  • Mention Python runbooks and provide Python code samples where relevant.
  • Reorder examples so that cross-platform or platform-neutral approaches are presented first, or provide parallel examples for each OS.
  • Explicitly state any platform limitations or requirements for each method.
GitHub Create Pull Request
Automation Azure Quickstart - Configure a VM with Desired State Configuration ...n/articles/automation/quickstarts/dsc-configuration.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows and PowerShell, with most instructions and references assuming a Windows environment. The use of PowerShell DSC, references to PowerShell Gallery, and links to Windows-specific documentation are prevalent. Although a LAMP stack (Linux) example is provided, the overall workflow, tooling, and instructions are Windows-centric, and the retirement notice for Linux DSC further reduces Linux parity.
Recommendations
  • Provide clear guidance and examples for Linux/macOS users using Azure Policy Guest Configuration, as DSC for Linux is retired.
  • Include alternative workflows or migration paths for Linux users, with step-by-step instructions.
  • Reference Linux-native configuration management tools (e.g., Ansible, Chef, Puppet) where appropriate.
  • Ensure that documentation sections do not assume PowerShell or Windows-only tooling, and offer cross-platform alternatives.
  • Update links and references to include Linux/macOS documentation where relevant.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation shared resource issues ...n/articles/automation/troubleshoot/shared-resources.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a strong Windows bias, primarily by providing only PowerShell-based troubleshooting steps and examples, referencing Windows-centric tools and patterns (e.g., PowerShell cmdlets, .psd1/.psm1 modules, DLL errors), and omitting Linux/macOS-specific guidance or CLI alternatives. All code samples and troubleshooting flows assume the use of PowerShell, which is native to Windows, and there is no mention of Bash, Azure CLI, or Linux-specific troubleshooting. The page also references DLL errors and Windows file structures, further reinforcing the bias.
Recommendations
  • Provide equivalent troubleshooting steps using Azure CLI and Bash scripts for Linux/macOS users.
  • Include examples of how to manage Azure Automation modules from Linux/macOS environments.
  • Clarify which steps are platform-agnostic and which are Windows-specific.
  • Reference cross-platform tools and patterns (e.g., Azure CLI, REST API) alongside PowerShell.
  • Add notes or links to documentation for Linux/macOS users where PowerShell or Windows-specific tools are required.
GitHub Create Pull Request
Automation Configure machines to a desired state in Azure Automation ...automation/tutorial-configure-servers-desired-state.md
High Priority View Details →
Scanned: 2026-01-12 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 is heavily biased toward Windows environments and PowerShell usage. All examples use Windows PowerShell cmdlets and focus on managing Windows VMs, specifically referencing IIS installation. Prerequisites and walkthroughs exclusively mention Windows tools and patterns, with no Linux/macOS equivalents or examples. Although there is a brief mention of Linux machine support, no Linux-specific onboarding or configuration steps are provided.
Recommendations
  • Add equivalent examples for onboarding and configuring Linux VMs, including sample DSC configurations for Linux resources.
  • Include instructions for using cross-platform tools (such as Azure CLI or REST API) where possible, not just PowerShell.
  • Provide Linux/macOS prerequisites and setup steps, including links to relevant documentation.
  • Show Linux examples alongside Windows examples, or clearly separate sections for each platform.
  • Reference Linux-specific DSC resources and modules, and clarify any limitations or retirement status for Linux support.
GitHub Create Pull Request
Automation Integrate Azure Automation State Configuration with Azure Monitor Logs ...main/articles/automation/automation-dsc-diagnostics.md
High 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 toward Windows and PowerShell usage. All code examples and setup instructions use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux/macOS-specific workflows. Prerequisites and tooling references are exclusively PowerShell-centric, and Windows tools (e.g., PowerShell modules) are referenced without Linux alternatives. There is no guidance for Linux users, and the documentation assumes a Windows environment throughout.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, enabling Linux/macOS users to follow along.
  • Explicitly mention platform compatibility for each step, clarifying whether actions can be performed from Linux/macOS.
  • Provide Bash script samples or instructions for Linux environments.
  • Reference cross-platform tools and modules where available, or note limitations if certain features are Windows-only.
  • Reorder examples to present platform-neutral or cross-platform options before Windows-specific ones.
GitHub Create Pull Request
Automation Compile DSC configurations in Azure Automation State Configuration ...lob/main/articles/automation/automation-dsc-compile.md
High 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 is heavily focused on Windows and PowerShell workflows for compiling DSC configurations in Azure Automation. All code samples, tool references, and procedural steps use Windows PowerShell and Windows-centric paths and modules. There is no mention of Linux/macOS equivalents, nor are there examples or instructions for non-Windows platforms. The only nod to Linux is an announcement about retirement, not functional guidance.
Recommendations
  • Add explicit guidance for compiling DSC configurations from Linux/macOS environments, if supported.
  • Provide Bash or cross-platform PowerShell Core examples where possible.
  • Clarify platform requirements and limitations early in the documentation.
  • If Linux support is deprecated, state this clearly and offer migration advice.
  • Reference any available CLI or REST API alternatives that are platform-agnostic.
  • Avoid Windows-centric file paths and tools in generic instructions; use platform-neutral language or provide alternatives.
GitHub Create Pull Request
Automation Create configurations from existing servers for Azure Automation State Configuration ...ticles/automation/automation-dsc-config-from-server.md
High 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 Windows and PowerShell, with all examples and referenced tools (ReverseDSC, SharePointDSC) being Windows-centric. There is no mention of Linux/macOS equivalents, and the prerequisites explicitly state Windows PowerShell 5.1. Steps and resources are tailored for Windows environments, leaving Linux users without guidance or parity.
Recommendations
  • Add explicit guidance for Linux/macOS users, including whether ReverseDSC or similar extraction tools exist for those platforms.
  • Clarify if Azure Automation State Configuration supports Linux nodes for configuration extraction, and provide examples or links for Linux DSC equivalents.
  • Include Linux-specific onboarding and MOF generation instructions, referencing any cross-platform DSC resources.
  • If functionality is Windows-only, state this clearly at the beginning and suggest alternatives for Linux users.
GitHub Create Pull Request
Automation Set up Azure Automation continuous deployment with Chocolatey ...in/articles/automation/automation-dsc-cd-chocolatey.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, with all examples, tools, and instructions tailored to Windows systems and PowerShell. There is no guidance for Linux or macOS users, and the article explicitly uses Windows-specific technologies (Chocolatey, PowerShell DSC, Windows Management Framework, WindowsFeature). Linux equivalents (such as apt-get, Ansible, or native Linux DSC support) are mentioned only in passing, and not integrated into the workflow or examples. The retirement of Linux DSC support is noted, but no alternative Linux automation approach is provided.
Recommendations
  • Add a section or parallel workflow for Linux VMs, using native Linux package managers (apt, yum) and configuration tools (Ansible, Chef, native Linux DSC if available).
  • Provide Linux/macOS-specific examples for automation, package management, and VM configuration.
  • Clarify the impact of Azure Automation DSC Linux retirement and suggest alternative solutions for Linux users (e.g., Azure Automation Runbooks, Ansible on Azure, etc.).
  • Where possible, use cross-platform tools or highlight platform-specific differences and workarounds.
  • Explicitly state that the documented workflow is Windows-only, and link to Linux/macOS alternatives.
GitHub Create Pull Request
Automation Configure data at scale for Azure Automation State Configuration ...cles/automation/automation-dsc-config-data-at-scale.md
High 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 Windows PowerShell DSC, with all examples and references tailored to Windows environments. There is no mention of Linux/macOS equivalents, nor any examples or guidance for non-Windows platforms, despite Azure Automation DSC supporting Linux nodes. The use of PowerShell-specific tooling and terminology further excludes Linux users.
Recommendations
  • Include explicit guidance and examples for configuring data at scale for Linux/macOS nodes managed by Azure Automation DSC.
  • Provide Linux-specific configuration file formats and workflows, such as using native Linux tools or shell scripts.
  • Clarify which steps are applicable to Linux nodes and highlight any platform-specific differences.
  • Reference Linux DSC resources and documentation alongside Windows resources.
  • Add cross-platform notes where PowerShell DSC is used, indicating alternatives or compatibility for Linux/macOS.
GitHub Create Pull Request
Automation Work with Azure Desired State Configuration extension version history ...rticles/automation/automation-dsc-extension-history.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, exclusively listing Windows Server and Windows Client OS support for all extension versions. All tooling references are to Windows Management Framework (WMF) and PowerShell DSC, with no mention of Linux equivalents or examples. There are no Linux-specific instructions, environments, or supported OS versions described, and the only Linux-related content is a retirement announcement, further emphasizing the Windows bias.
Recommendations
  • Clearly state the current and historical support status for Linux, including which extension versions (if any) supported Linux and when support was retired.
  • Add a dedicated section summarizing Linux support lifecycle, with links to relevant Linux DSC documentation (if available).
  • If Linux support is retired, provide migration guidance or alternatives for Linux users.
  • Where possible, include examples or notes for Linux users, even if only to clarify that features are Windows-only.
  • Avoid presenting Windows-only tools and instructions without context about Linux support status.
GitHub Create Pull Request
Automation Configure data based on STIG for Azure Automation State Configuration ...tomation/automation-dsc-configuration-based-on-stig.md
High 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 Windows and PowerShell, with all examples and references centered around Windows PowerShell DSC and the PowerSTIG project, which is Windows-specific. There are no Linux/macOS equivalents, examples, or guidance, and the prerequisites and next steps all assume a Windows environment.
Recommendations
  • Add explicit guidance or examples for Linux/macOS users, such as how to achieve STIG compliance using cross-platform tools.
  • Clarify whether PowerSTIG or DSC can be used on Linux/macOS, and if not, suggest alternative solutions for those platforms.
  • Include references to Linux configuration management tools (e.g., Ansible, Chef, or native DSC for Linux) and how they can be integrated with Azure Automation.
  • Reorder or balance examples so that Linux is not an afterthought, and provide parity in documentation structure.
GitHub Create Pull Request
Automation Get started with Azure Automation State Configuration .../articles/automation/automation-dsc-getting-started.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric, with all examples and configuration samples using Windows PowerShell DSC and Windows-specific resources (e.g., WindowsFeature). The only VM creation link is for Windows, and there are no Linux configuration examples or references to Linux DSC resources or onboarding steps. The documentation mentions Linux support only in passing, and does not provide parity in instructions, examples, or tooling for Linux/macOS users.
Recommendations
  • Add explicit Linux onboarding and configuration examples, including sample DSC configurations for Linux resources.
  • Provide links and instructions for creating Linux VMs in Azure alongside Windows VM instructions.
  • Reference Linux DSC documentation and resources, such as nxFile, nxPackage, etc.
  • Clarify any limitations or retirement notices for Linux support at the top, and provide migration guidance if Linux support is deprecated.
  • Include PowerShell Core or cross-platform alternatives where possible, and note differences in workflow for Linux/macOS users.
GitHub Create Pull Request
Automation Migrate from Orchestrator to Azure Automation (Beta) ...ticles/automation/automation-orchestrator-migration.md
High 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 and PowerShell, with all examples, tools, and migration steps centered around Windows technologies. PowerShell is presented as the default and only scripting environment, and all commands and file paths use Windows conventions. There is no mention of Linux/macOS alternatives, nor any guidance for users on those platforms. The migration toolkit, integration modules, and converter tools are all Windows-specific, and Linux users are left without clear instructions or parity.
Recommendations
  • Explicitly state platform requirements and limitations at the beginning of the documentation.
  • Provide guidance for Linux/macOS users, including any available alternatives or workarounds.
  • If Azure Automation supports Python or Bash runbooks, mention these options and link to relevant documentation.
  • Include Linux/macOS file path examples and clarify if tools like the Runbook Converter or integration modules can be run via PowerShell Core on non-Windows platforms.
  • If migration is only possible on Windows, suggest using a Windows VM or container for Linux/macOS users and provide step-by-step instructions.
  • Add a section comparing Windows and Linux/macOS support for Azure Automation and migration tooling.
GitHub Create Pull Request
Automation Deploy an Amazon Web Services VM with an Azure Automation runbook ...icles/automation/automation-scenario-aws-deployment.md
High 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 and PowerShell ISE for all examples and instructions, with no mention of Linux/macOS alternatives such as Bash, AWS CLI, or cross-platform scripting. Windows tools and workflows are referenced throughout, and Linux/macOS users are not provided with equivalent guidance or examples.
Recommendations
  • Include examples using AWS CLI and Bash scripts for runbook authoring and VM provisioning.
  • Document how to import and use AWS CLI modules in Azure Automation, including authentication steps for Linux/macOS users.
  • Provide guidance for authoring runbooks in Python or other cross-platform languages supported by Azure Automation.
  • Add explicit instructions for Linux/macOS users, including how to retrieve AWS images and credentials without PowerShell.
  • Reorder examples or provide parallel instructions so that Windows and Linux/macOS users are equally supported.
GitHub Create Pull Request
Automation Compose DSC configurations ...omation/compose-configurationwithcompositeresources.md
High 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 is heavily oriented towards Windows and PowerShell. It references PowerShell DSC concepts, cmdlets, and credential types, and all examples and screenshots are based on Windows-centric tools and workflows. There is no mention of Linux/macOS equivalents, and the retirement announcement for Linux DSC further reduces Linux relevance. Linux users are left without guidance or examples for composing configurations, and the documentation assumes familiarity with Windows/PowerShell patterns.
Recommendations
  • Add explicit notes about Linux/macOS support status and alternatives, especially given the Linux retirement announcement.
  • Provide examples or guidance for Linux users where possible, or link to migration strategies.
  • Clarify which features are Windows-only and suggest cross-platform alternatives if available.
  • Include references to non-Windows configuration management tools or workflows for parity.
GitHub Create Pull Request
Automation Use the Azure Automation graphical runbook SDK (preview) ...blob/main/articles/automation/graphical-runbook-sdk.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows and PowerShell, referencing PowerShell commands, modules, and workflows exclusively. There are no Linux or cross-platform equivalents mentioned, and all examples assume a Windows/PowerShell environment. The SDK and its DLL are presented without discussion of Linux compatibility or alternatives.
Recommendations
  • Clarify whether the SDK and graphical runbooks are supported or usable on Linux/macOS environments.
  • If supported, provide Linux/macOS installation instructions and usage examples.
  • Discuss any platform limitations or requirements (e.g., .NET Core/Mono compatibility, PowerShell Core support).
  • Include examples using PowerShell Core (pwsh) and note differences from Windows PowerShell.
  • Mention any Linux-specific considerations for Azure Automation graphical runbooks.
GitHub Create Pull Request
Automation Manage Office 365 services using Azure Automation ...ocs/blob/main/articles/automation/manage-office-365.md
High 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 focused on Windows and PowerShell, with all examples and instructions using Windows PowerShell and related modules. There is an explicit note that the Microsoft Graph PowerShell module cmdlets must be run from Windows PowerShell, and PowerShell Core (used on Linux/macOS) is not supported. No Linux/macOS alternatives or examples are provided, and all tooling and workflow references are Windows-centric.
Recommendations
  • Provide guidance or alternatives for Linux/macOS users, such as using PowerShell Core where possible, or using REST API calls via scripting languages like Python or Bash.
  • Explicitly state platform limitations and suggest workarounds for non-Windows environments.
  • Include examples for Linux/macOS users, or clarify which steps are Windows-only.
  • Mention cross-platform tools or modules if available, and provide parity in documentation structure.
GitHub Create Pull Request
Automation Manage runbooks in Azure Automation ...-docs/blob/main/articles/automation/manage-runbooks.md
High 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 strong Windows bias, primarily through exclusive use of PowerShell examples, Windows-centric file paths, and references to Windows tools and patterns. There are no CLI/bash examples, nor any mention of Linux/macOS-specific workflows or tools. All code samples and automation instructions rely on PowerShell cmdlets, which are native to Windows and only available on Linux/macOS via PowerShell Core, which is not referenced. Windows file paths (e.g., C:\Runbooks\...) are used, and there is no guidance for Linux/macOS users regarding file locations, shell usage, or alternative approaches. The documentation assumes familiarity with Windows conventions and does not provide parity for Linux/macOS users.
Recommendations
  • Add Azure CLI/bash examples alongside PowerShell for all major tasks (creating, importing, publishing, retrieving runbook/job status).
  • Include Linux/macOS file path examples and clarify cross-platform compatibility for scripts and automation.
  • Mention PowerShell Core and its installation/usage on Linux/macOS where PowerShell is required.
  • Explicitly state platform requirements and provide guidance for Linux/macOS users on how to adapt instructions.
  • Where possible, provide REST API or SDK-based examples that are platform-agnostic.
  • Ensure that references to tools (e.g., file browsers, script editors) include Linux/macOS equivalents.
GitHub Create Pull Request
Automation Azure Quickstart - Configure a VM with Desired State Configuration ...n/articles/automation/quickstarts/dsc-configuration.md
High 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 is heavily oriented towards Windows and PowerShell, with all configuration examples provided in PowerShell syntax and references to Windows-centric tools and workflows. Although the quickstart claims to configure a LAMP stack (Linux), it relies on Azure Automation DSC, which has been retired for Linux, and does not provide Linux-native alternatives or guidance for Linux users. The documentation references Windows DSC concepts and tools (e.g., PowerShell Gallery, MOF files) without Linux equivalents, and the only example is a PowerShell script. The 'Next steps' section further reinforces Windows bias by linking to Chocolatey, a Windows package manager.
Recommendations
  • Clearly state that Azure Automation DSC is no longer supported for Linux and provide alternative solutions for Linux configuration management (e.g., Azure Policy Guest Configuration, Ansible, Chef, Puppet).
  • Provide Linux-native configuration management examples and workflows, such as using cloud-init, Ansible, or Azure Policy for Linux VMs.
  • Offer parity in documentation by including Linux CLI commands, scripts, and configuration file examples alongside PowerShell/Windows examples.
  • Update 'Next steps' to include links relevant to Linux users, such as guides for continuous deployment with Linux tools.
  • Explicitly guide Linux users to supported and recommended approaches for VM configuration in Azure.
GitHub Create Pull Request
Automation Configure machines to a desired state in Azure Automation ...automation/tutorial-configure-servers-desired-state.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows environments and PowerShell usage. All examples use Windows PowerShell cmdlets and focus on configuring Windows VMs (specifically installing IIS). Prerequisites and walkthroughs reference only Windows Server and Windows-specific tooling, with no Linux/macOS equivalents or examples. Although there is a mention of Linux support, no Linux-specific instructions, shell commands, or configuration examples are provided.
Recommendations
  • Add Linux-specific examples, such as configuring a Linux VM (e.g., installing Apache or Nginx) using DSC.
  • Include Bash/CLI instructions alongside PowerShell, especially for onboarding and configuration steps.
  • Clarify the current support status for Linux DSC in Azure Automation, given the retirement announcement.
  • Provide links to Linux onboarding documentation and highlight any differences or limitations.
  • Present examples for both Windows and Linux in parallel, or clearly indicate platform-specific sections.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell-based migration scripts and workflows, with no mention of Bash, Python, or other Linux-native scripting alternatives. The examples and instructions for Hybrid Runbook Worker installation and migration reference Windows tabs and steps first, and do not provide parity for Linux users. There is no guidance or sample code for Linux-centric automation or migration, despite the article stating applicability to both Linux and Windows VMs.
Recommendations
  • Provide equivalent Bash or Python scripts for migrating Automation account assets, suitable for Linux environments.
  • Include Linux-first or Linux-parallel tabs/examples in all step-by-step instructions, especially for Hybrid Runbook Worker installation and migration.
  • Document any Linux-specific modules, tools, or patterns for Azure Automation disaster recovery.
  • Clarify any differences in process or limitations for Linux users, and offer troubleshooting steps or best practices for Linux environments.
  • Ensure that all PowerShell instructions are accompanied by Linux-native alternatives where possible, or explicitly state if PowerShell Core is required and supported on Linux.
GitHub Create Pull Request
Automation Migrate from a Run As account to Managed identities ...automation/migrate-run-as-accounts-managed-identity.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell-based automation, which is primarily a Windows-centric tool. All code samples, migration steps, and graphical runbook instructions use PowerShell cmdlets (Connect-AzAccount, Get-AzResourceGroup, etc.) and reference PowerShell modules (Az, AzureRM). There are no examples or guidance for using Linux-native tools, Bash, Python, or cross-platform SDKs. Windows/PowerShell patterns are presented exclusively and first, with no mention of alternatives for Linux or cross-platform users.
Recommendations
  • Add equivalent code samples for Bash (using Azure CLI) and Python (using Azure SDK) to demonstrate managed identity authentication and resource access.
  • Include migration steps and scripts for runbooks written in Bash or Python, not just PowerShell.
  • Explicitly mention cross-platform options for Azure Automation, such as using Azure CLI or Python runbooks, and link to relevant documentation.
  • Clarify which steps, scripts, and modules are Windows-specific and provide Linux-compatible alternatives where possible.
  • Add a section or note about how managed identities can be used in Linux-based hybrid runbook workers, including any differences or limitations.
GitHub Create Pull Request
Automation Manage connections in Azure Automation ...lob/main/articles/automation/automation-connections.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias by focusing heavily on PowerShell cmdlets and workflows, providing detailed PowerShell examples and references to Windows-specific tools (e.g., PowerShell, Az modules). Linux or cross-platform CLI examples are missing, and the PowerShell workflow is described before Python, with no mention of Bash, Azure CLI, or Linux-native automation approaches. The documentation assumes the use of Windows-centric tools and patterns, which may disadvantage Linux users or those preferring non-PowerShell environments.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for creating and managing connections.
  • Explicitly mention Linux compatibility and provide steps for Linux users, including installation and usage of required modules.
  • Include cross-platform instructions and clarify which features are available on Windows vs. Linux.
  • Provide Python examples earlier or in parallel with PowerShell, and add other language examples if supported.
  • Reference Linux tools and patterns where appropriate, such as environment variables, shell scripting, or alternative credential management approaches.
GitHub Create Pull Request
Automation Convert configurations to composite resources for Azure Automation State Configuration ...articles/automation/automation-dsc-create-composite.md
High Priority View Details →
Scanned: 2026-01-10 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 focusing exclusively on Windows PowerShell 5.1 and PowerShell DSC tooling. All examples and instructions are tailored to PowerShell, with no mention of Linux-native configuration management tools or cross-platform DSC usage. References to configuration management scenarios (web server, DNS, SQL, SharePoint) are implicitly Windows-centric, and links and next steps direct users to Windows PowerShell resources. There is no guidance for Linux users, nor examples using Linux shell or DSC on Linux.
Recommendations
  • Add explicit support and examples for Linux environments, including how to use DSC on Linux nodes.
  • Include Linux shell (bash) equivalents for configuration management tasks where possible.
  • Reference cross-platform DSC modules and clarify any differences in usage between Windows and Linux.
  • Provide links to documentation for Linux DSC resources and configuration management tools.
  • Update 'Applies to' section to specify whether Linux is supported and, if so, how to use these features on Linux.
GitHub Create Pull Request
Automation Authenticate Azure Automation runbooks with Amazon Web Services ...n/articles/automation/automation-config-aws-account.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing AWS credential management via a PowerShell-specific link, omitting Linux or cross-platform CLI examples. The instructions and links focus on Azure portal and PowerShell workflows, with no mention of Linux tools, shell commands, or guidance for non-Windows environments.
Recommendations
  • Include examples for authenticating and managing AWS credentials using the AWS CLI on Linux/macOS.
  • Reference AWS documentation for Linux and cross-platform credential management, not just PowerShell.
  • Provide parity in instructions for storing credentials, such as using Azure Automation assets via Azure CLI or REST API, which are platform-agnostic.
  • Add notes or sections for Linux users, including common shell commands and credential file locations.
  • Ensure that all referenced external documentation covers both Windows and Linux usage patterns.
GitHub Create Pull Request
← Previous Page 2 of 15 Next →