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 51-75 of 365 flagged pages
Automation Use an alert to trigger an Azure Automation runbook ...utomation/automation-create-alert-triggered-runbook.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. All code examples and instructions are provided exclusively in PowerShell, which is primarily a Windows-centric tool (though available on Linux, it's less commonly used there). The prerequisites specifically reference Windows virtual machines and the Azure Az PowerShell module, with no mention of Linux VMs or CLI alternatives. There are no Bash, Azure CLI, or Linux shell examples, nor any guidance for users working in non-Windows environments. The workflow and tooling are presented from a Windows-first perspective, and Linux parity is not addressed.
Recommendations
  • Add equivalent Azure CLI (az) and Bash script examples for all PowerShell instructions, especially for role assignment and runbook creation.
  • Explicitly mention that the Az PowerShell module is cross-platform, and provide installation instructions for Linux/macOS.
  • Include Linux VM scenarios in prerequisites and examples, such as links to Linux VM quickstart guides.
  • Show how to create and trigger runbooks using Azure CLI and REST API, not just PowerShell.
  • Clarify which steps or scripts are platform-agnostic and which are Windows-specific.
  • Provide troubleshooting or notes for users working on Linux/macOS, especially regarding authentication and managed identity.
  • Balance the documentation by alternating or paralleling Windows and Linux instructions throughout the page.
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-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 exhibits a strong Windows bias. It is focused almost exclusively on Windows PowerShell 5.1 and Windows-centric tools (DSC, SharePointDSC, ReverseDSC). All examples, references, and next steps are tailored to Windows environments, with no Linux-specific instructions, examples, or equivalent tooling mentioned. Linux is referenced only in passing, with no guidance on how to achieve similar outcomes on Linux servers.
Recommendations
  • Add explicit examples and instructions for Linux environments, including how to extract configurations from Linux servers.
  • Mention and link to Linux equivalents of DSC, such as 'OMI' or 'DSC for Linux', and community projects relevant to Linux configuration extraction.
  • Provide parity in step-by-step guides for Linux, including how to generate MOF files from Linux servers and upload them to Azure Automation.
  • Update the 'Applies to' section to clarify Linux support and limitations, and offer alternative approaches for Linux users.
  • Include references to Linux-specific documentation and resources in the 'Next steps' section.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page is heavily focused on Windows and PowerShell, with all examples and tooling references centered around Windows PowerShell DSC and the PowerSTIG project. Linux is only briefly mentioned as a possible target for onboarding, but no Linux-specific configuration guidance, examples, or tools are provided. The documentation assumes familiarity with Windows PowerShell and does not address Linux equivalents or cross-platform DSC usage.
Recommendations
  • Include Linux-specific examples for configuring STIG baselines using DSC, such as using DSC for Linux or alternative configuration management tools (e.g., Ansible, Chef, or native Linux DSC support).
  • Mention and link to Linux-compatible DSC resources and documentation, clarifying any platform limitations.
  • Provide guidance or references for generating and applying MOF files on Linux systems, including any prerequisites or differences from Windows.
  • Balance the introduction and next steps by equally highlighting Linux and cross-platform approaches, not just Windows PowerShell.
  • If PowerSTIG is Windows-only, explicitly state this and suggest Linux alternatives for STIG compliance automation.
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-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. All code examples and setup instructions use PowerShell and Az PowerShell modules, which are native to Windows and only available on Linux via PowerShell Core (which is less commonly used). There are no Bash, CLI, or Linux-native examples, and no mention of Linux-specific tools or workflows. The prerequisites and troubleshooting modules are PowerShell-centric. The only reference to Linux is an end-of-life announcement, not guidance or parity.
Recommendations
  • Add equivalent Azure CLI (az) commands for all PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash script examples for setup and integration steps.
  • Explicitly state Linux support status and provide guidance for Linux users where possible.
  • Reference Linux-compatible DSC modules and workflows if available.
  • Clarify which steps are platform-agnostic and which require Windows/PowerShell, and suggest alternatives for Linux environments.
  • Update troubleshooting and onboarding sections to include Linux-specific instructions or note limitations.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All configuration examples use Windows PowerShell DSC syntax and the WindowsFeature resource, with no Linux equivalents or cross-platform DSC resources shown. The prerequisites and VM creation instructions reference only Windows VMs, and links point to Windows-specific documentation. Linux support is only mentioned in passing and in the context of retirement announcements, with no practical guidance or examples for Linux users.
Recommendations
  • Add equivalent Linux DSC configuration examples, such as using nxFile or nxPackage resources.
  • Include instructions for creating and onboarding Linux VMs, with links to Linux VM creation guides.
  • Provide cross-platform DSC examples and clarify which resources and steps are supported on Linux.
  • Update prerequisites to mention supported Linux operating systems and their requirements.
  • Balance references to Windows PowerShell DSC with information about cross-platform DSC (including PowerShell Core and Linux).
  • Remove or update retirement announcements to clarify current Linux support and alternatives.
GitHub Create Pull Request
Automation Remediate noncompliant Azure Automation State Configuration servers ...b/main/articles/automation/automation-dsc-remediate.md
High Priority View Details →
Scanned: 2026-01-10 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 page presents remediation steps for Azure Automation State Configuration servers with a clear Windows bias. Windows remediation is described first, with a direct PowerShell example and references to Windows-specific tools (PowerShell, Update-DscConfiguration). Linux remediation is described as less capable, with no script example, and only general guidance to repeat registration or use Python scripts, but no concrete code. Windows tools and patterns are mentioned exclusively or before Linux equivalents.
Recommendations
  • Provide concrete Linux remediation script examples, similar to the PowerShell example for Windows.
  • Include references to Linux-native tools and commands (e.g., shell scripts, Python commands) for correcting drift.
  • Present Linux and Windows remediation steps in parallel, rather than Windows-first.
  • Clarify the limitations and alternatives for Linux users, and link to up-to-date Linux DSC documentation.
  • Avoid exclusive reliance on PowerShell and Windows tools; highlight cross-platform or Linux-specific solutions where available.
GitHub Create Pull Request
Automation Edit textual runbooks in Azure Automation ...articles/automation/automation-edit-textual-runbook.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 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on PowerShell and Windows-specific workflows. All code examples use Windows PowerShell, with explicit references to Windows paths (e.g., c:\runbooks) and no mention of Linux or cross-platform alternatives. There are no Bash or Linux shell examples, nor guidance for users on non-Windows platforms. Windows tools and patterns are referenced exclusively, and the documentation does not address Linux or macOS users.
Recommendations
  • Include equivalent examples for Linux/macOS environments, such as using PowerShell Core (pwsh) on non-Windows platforms.
  • Use platform-neutral file paths in examples (e.g., $HOME/runbooks or ./runbooks).
  • Clarify that Az PowerShell module and Azure Automation can be used from Linux/macOS, and provide instructions for installing and using PowerShell Core.
  • Add Bash or Azure CLI examples for common runbook management tasks.
  • Explicitly state cross-platform compatibility and provide guidance for users on Linux and macOS.
GitHub Create Pull Request
Automation Forward Azure Automation job data to Azure Monitor logs ...mation/automation-manage-send-joblogs-log-analytics.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. PowerShell is mentioned as the primary CLI for viewing job logs, and the only example of CLI interaction is with PowerShell. There are no references to Linux tools, Bash, or cross-platform alternatives for querying or interacting with Azure Automation job data. The documentation assumes familiarity with Windows-centric workflows and does not provide parity for Linux users.
Recommendations
  • Add examples using Azure CLI (az), which is cross-platform and works on both Windows and Linux.
  • Include Bash shell examples for querying logs and interacting with Azure Monitor, especially for Linux users.
  • Explicitly mention that all portal and Kusto query steps are platform-agnostic, and clarify that PowerShell is just one option.
  • Provide links or references to Linux-specific documentation for Azure Automation and Azure Monitor.
  • Where PowerShell is referenced, add equivalent steps for Bash/Azure CLI to ensure Linux users can follow along.
  • Review and update any screenshots or instructions that show Windows-only interfaces to include Linux or web-based alternatives where possible.
GitHub Create Pull Request
Automation Azure Automation account authentication overview ...in/articles/automation/automation-security-overview.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 referencing PowerShell cmdlets as the primary method for Azure Automation authentication, without mentioning or providing equivalent Linux or cross-platform examples (such as Azure CLI, Bash, or Python SDK). Windows tools and patterns (PowerShell, Azure Resource Manager templates) are mentioned exclusively or before any Linux alternatives. There are no examples or guidance for Linux users or those using non-Windows environments, and no mention of how to authenticate from Linux-based Hybrid Runbook Workers.
Recommendations
  • Include authentication examples using Azure CLI, Bash, or Python SDK alongside PowerShell cmdlets.
  • Explicitly mention and provide guidance for Linux-based Hybrid Runbook Workers, including how to configure authentication from Linux systems.
  • Add cross-platform code snippets for creating and managing Automation accounts and managed identities.
  • Reference Linux tools and patterns (e.g., shell scripts, cron jobs) where relevant, and ensure parity in documentation structure and examples.
  • Clarify that Azure Automation supports both Windows and Linux environments, and provide links to Linux-specific documentation where available.
GitHub Create Pull Request
Automation Track updated files with an Azure Automation watcher task ...s/automation/automation-scenario-using-watcher-task.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 and Windows environments. All examples and instructions assume the use of PowerShell and Windows-style paths (e.g., D:\examplefiles), with no mention of Linux equivalents or Bash commands. The Hybrid Runbook Worker is only described in the context of Windows, and there are no examples or guidance for monitoring directories on Linux systems or using Linux-native tools. This creates a clear Windows bias and leaves Linux users without guidance for equivalent scenarios.
Recommendations
  • Add parallel examples using Bash or shell scripts for Linux Hybrid Runbook Workers.
  • Include instructions and screenshots for Linux file paths and directory monitoring.
  • Clarify whether watcher tasks and runbooks can run on Linux Hybrid Runbook Workers, and provide setup steps if supported.
  • Mention Linux tools (e.g., inotifywait, find) for file monitoring alongside PowerShell.
  • Ensure all parameter examples (e.g., FOLDERPATH) include both Windows and Linux path formats.
  • Provide troubleshooting and output examples for Linux environments.
GitHub Create Pull Request
Automation Disable local authentication in Azure Automation ...in/articles/automation/disable-local-authentication.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 page demonstrates a strong Windows bias by exclusively providing PowerShell examples and referencing Windows-centric tools (e.g., PowerShell cmdlets like Invoke-AzRestMethod and Get-AzAutomationAccount). There are no CLI, Bash, or Linux-native examples or instructions, and the workflow assumes the user is operating in a Windows environment. Linux alternatives (such as using curl or Azure CLI) are not mentioned, and PowerShell is presented as the default/first (and only) method for interacting with the API.
Recommendations
  • Add equivalent examples using Azure CLI (az automation account update) for disabling/enabling local authentication.
  • Provide REST API usage examples with curl or httpie, which are common on Linux systems.
  • Explicitly mention that PowerShell is cross-platform, but clarify how Linux/macOS users can install and use it, or offer alternative commands.
  • Reorder or supplement instructions so that Linux-friendly methods (CLI, REST with curl) are presented alongside or before PowerShell examples.
  • Include troubleshooting or verification steps using Azure CLI or REST API responses, not just PowerShell.
GitHub Create Pull Request
Automation Using a system-assigned managed identity for an Azure Automation account ...s/automation/enable-managed-identity-for-automation.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 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows and PowerShell bias. Nearly all code examples and step-by-step instructions use PowerShell, with no equivalent Bash, CLI, or Linux-native scripting examples provided. Windows-specific tools and paths are mentioned first or exclusively in several places, such as instructions for checking Hybrid Runbook Worker versions and file paths. REST API and ARM template sections also use PowerShell for invocation, omitting cross-platform alternatives. Linux is mentioned only briefly and without practical examples. This limits accessibility for users on Linux or those preferring Azure CLI or Bash.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell scripts, especially for enabling managed identity, assigning roles, and authenticating.
  • Include Linux-native instructions and file paths alongside Windows instructions, not only in version checks but also in practical automation scenarios.
  • Demonstrate REST API and ARM template invocations using curl or az CLI, not just PowerShell.
  • Add examples of using managed identity in Bash or Python scripts for resource access, not only PowerShell.
  • Ensure that instructions for hybrid workers, authentication, and troubleshooting are platform-neutral or include both Windows and Linux variants.
  • Consider a 'Platform parity' table or section summarizing how each step can be performed on both Windows and Linux.
GitHub Create Pull Request
Automation Create an Azure Automation account using a Resource Manager template ...ation/quickstart-create-automation-account-template.md
High Priority View Details →
Scanned: 2026-01-10 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. PowerShell is mentioned explicitly and referenced before Azure CLI in deployment instructions. The error handling example is given for PowerShell and the portal, with Azure CLI mentioned only after PowerShell. There are no Linux-specific examples, nor is Bash or shell scripting referenced. The documentation does not provide parity in example commands or troubleshooting steps for Linux users.
Recommendations
  • Provide explicit Bash/Azure CLI examples alongside PowerShell instructions, including full command syntax for Linux/macOS users.
  • List Azure CLI instructions before or alongside PowerShell to avoid Windows-first ordering.
  • Include troubleshooting steps and error messages for Azure CLI and Bash, not just PowerShell.
  • Mention cross-platform compatibility and clarify which steps apply to Windows, Linux, or macOS.
  • Add a note or section for Linux/macOS users, highlighting any differences or considerations.
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-10 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 demonstrates a strong Windows bias by centering all configuration and automation steps around PowerShell, referencing Windows-centric DSC resources, and mentioning Windows server management explicitly. Linux support is noted as retired, and while a LAMP stack example is given, all code samples use PowerShell syntax and Windows DSC tooling. There are no equivalent Linux-native examples, and references to tools like Chocolatey further reinforce the Windows focus.
Recommendations
  • Provide Linux-native configuration examples using tools such as Ansible, Chef, or native shell scripts, especially since Azure Automation DSC for Linux is retired.
  • Include alternative workflows for Linux VMs, such as using Azure Policy Guest Configuration or other supported mechanisms.
  • Clearly separate instructions for Windows and Linux, indicating which steps/tools apply to each platform.
  • Offer guidance on migrating from DSC to supported Linux configuration management solutions.
  • Avoid referencing Windows-only tools (e.g., Chocolatey) in general quickstarts, or provide Linux equivalents (e.g., apt, yum, dnf).
GitHub Create Pull Request
Automation Use Source Control Integration in Azure Automation ...main/articles/automation/source-control-integration.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 demonstrates a strong Windows bias. All command-line examples use PowerShell, with no mention of Bash, Azure CLI, or Linux-native workflows. The prerequisites and configuration steps assume use of PowerShell and Windows tooling, and there are no Linux-specific instructions or parity for non-Windows users. The only supported runbook type for source control integration is PowerShell 5.1, which is Windows-specific. Encoding issues are referenced via PowerShell documentation, and all automation examples are presented with PowerShell cmdlets.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash for Linux/macOS users.
  • Clarify whether source control integration supports Python or other cross-platform runbook types, and update documentation if support is added.
  • Include instructions for configuring managed identities and role assignments using Azure CLI.
  • Reference Linux editors and encoding issues, not just PowerShell/VSCode.
  • Explicitly state platform requirements and limitations (e.g., PowerShell 5.1 is Windows-only) at the top of the documentation.
  • Add troubleshooting and configuration steps for Linux environments, including authentication and token management.
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-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 page exhibits a strong Windows bias, primarily through exclusive use of PowerShell cmdlets and scripts for troubleshooting and resolution steps. All code examples and tool references are Windows-centric (PowerShell, .psd1, .psm1, .dll files), with no mention of Linux equivalents or cross-platform alternatives. The troubleshooting steps assume familiarity with Windows tooling and scripting, and there are no Bash, CLI, or Linux-specific instructions provided.
Recommendations
  • Provide equivalent troubleshooting steps using Azure CLI and Bash scripts for Linux users.
  • Mention cross-platform module management tools and patterns, such as az automation module commands.
  • Include examples of how to resolve issues on Linux-based automation accounts or hybrid worker scenarios.
  • Clarify which steps are Windows-specific and offer alternative instructions for Linux environments.
  • Reference Linux file formats and dependency management (e.g., .so files, shell scripts) where relevant.
GitHub Create Pull Request
Automation Runtime Environment in Azure Automation ...in/articles/automation/runtime-environment-overview.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 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows and PowerShell environments. PowerShell is mentioned as the primary scripting language, with multiple versions listed and detailed integration with Azure CLI. Examples and package management references focus on PowerShell and Windows-centric tools, with little to no mention of Linux-specific patterns, shell scripting, or non-Windows automation tools. Python is referenced, but only as an alternative language, without parity in examples or tooling. There are no Linux shell (bash) examples, nor is there discussion of Linux-native package management or runtime environments.
Recommendations
  • Add examples and guidance for Linux shell scripting (e.g., bash) in Azure Automation runbooks.
  • Include details on how to use Azure CLI directly in Python or bash runbooks, not just PowerShell.
  • List Linux-native package management options and patterns for custom packages (e.g., pip for Python, apt for bash).
  • Provide parity in documentation for Python environments, including versioning, package management, and integration with Azure CLI.
  • Explicitly mention cross-platform support and clarify any Windows-specific limitations or behaviors.
  • Add links to Linux and Python documentation alongside PowerShell references.
GitHub Create Pull Request
Automation Remove DSC and node from Automation State Configuration ...configuration/remove-node-and-configuration-package.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Windows-specific tools (cmdlets like Unregister-AzAutomationDscNode and Remove-DscConfigurationDocument) are mentioned first and in more detail, while Linux instructions are less prominent and less detailed. The manual deletion section provides explicit PowerShell commands for Windows but only describes file deletion for Linux without command-line examples. The overall structure and examples favor Windows users, with Linux instructions often appearing as secondary notes.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., shell commands for deleting .mof files) alongside PowerShell examples.
  • Present Windows and Linux instructions in parallel, rather than listing Windows steps first.
  • Include references to Linux-native automation tools (such as Bash scripts or Ansible) where appropriate.
  • Expand Linux sections to match the detail and clarity of Windows instructions, including troubleshooting and verification steps.
  • Avoid assuming PowerShell as the default tool; clarify when instructions are OS-specific.
GitHub Create Pull Request
Automation Troubleshoot agent-based Hybrid Runbook Worker issues in Azure Automation ...icles/automation/troubleshoot/hybrid-runbook-worker.md
High Priority View Details →
Scanned: 2026-01-10 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 demonstrates a Windows bias in several ways: troubleshooting steps and examples are often presented for Windows first or exclusively, with PowerShell commands and Windows-specific tools (event logs, registry keys, config files) dominating the guidance. Linux troubleshooting is covered in a separate, shorter section, and some scenarios (e.g., updating Az modules, config file changes, registry edits) only provide Windows instructions or examples. In mixed sections, Windows tools and patterns (event logs, registry, PowerShell) are mentioned before or instead of Linux equivalents.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples for all scenarios currently covered only for Windows (e.g., updating Az modules, config file changes, registry edits).
  • Where PowerShell or Windows event logs are referenced, include equivalent Linux commands (e.g., Bash, journalctl, syslog) and file paths.
  • Ensure that Linux and Windows troubleshooting guidance is presented in parallel for each scenario, rather than segregating Linux into a separate section.
  • Include Linux-specific error messages and their resolutions alongside Windows examples.
  • Reference Linux tools and patterns (e.g., systemd, sudoers, log file locations) with the same level of detail as Windows tools.
  • Avoid using Windows paths and registry keys as the default; provide Linux equivalents where relevant.
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-10 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 towards Windows and PowerShell. All examples use Windows-specific resources (such as installing IIS via WindowsFeature) and PowerShell cmdlets. The prerequisites and instructions focus exclusively on Windows VMs, with no Linux configuration examples or equivalent Linux tooling mentioned. References to onboarding Linux machines are present only as links, not as actionable steps or examples.
Recommendations
  • Add explicit Linux configuration examples, such as using DSC resources for Linux (e.g., nxPackage, nxFile) and show how to configure a Linux VM to a desired state.
  • Include Bash/CLI examples or instructions for Linux users, not just PowerShell.
  • Update prerequisites to mention Linux VM support, and provide links to creating Linux VMs in Azure.
  • Present Windows and Linux instructions/examples in parallel, or clarify platform-specific differences early in the document.
  • Reference Linux equivalents for Windows tools and patterns (e.g., alternatives to WindowsFeature for package installation on Linux).
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-configuration-based-on-stig.md ...tomation/automation-dsc-configuration-based-on-stig.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page is heavily focused on Windows and PowerShell, with all examples and tooling references centered around PowerShell DSC and Windows environments. Linux is only mentioned in passing, with no concrete examples, instructions, or equivalent tooling for Linux systems. The guidance, resources, and next steps are exclusively Windows/PowerShell-oriented.
Recommendations
  • Include explicit examples and instructions for configuring Linux servers with STIG baselines using Azure Automation State Configuration.
  • Reference and link to Linux DSC resources or equivalent configuration management tools (e.g., Chef, Ansible, or native Linux DSC support).
  • Provide parity in documentation by showing how to generate and apply configurations for Linux, not just Windows.
  • Clarify any limitations or differences in Azure Automation State Configuration support for Linux vs. Windows.
  • Add Linux-focused next steps and resources, such as guides for onboarding Linux machines and managing their configurations.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-config-aws-account.md ...n/articles/automation/automation-config-aws-account.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing only Windows-centric tools and documentation, such as linking to AWS PowerShell credential instructions and omitting any mention of Linux or cross-platform alternatives. There are no examples or guidance for Linux users, such as using AWS CLI or bash scripts, and the documentation assumes familiarity with Windows patterns and Azure portal workflows.
Recommendations
  • Include examples for authenticating AWS from Linux environments, such as using AWS CLI and bash scripts.
  • Reference AWS documentation for both PowerShell and CLI tools, providing links to Linux/macOS instructions.
  • Clarify that Azure Automation runbooks can be authored in multiple languages (PowerShell, Python, etc.), and provide sample code for each.
  • Add guidance for storing and retrieving credentials using cross-platform methods, not just Azure portal workflows.
  • Explicitly mention platform-agnostic approaches and ensure parity in instructions for both Windows and Linux users.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/add-user-assigned-identity.md ...main/articles/automation/add-user-assigned-identity.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
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. All command-line examples use PowerShell, which is primarily a Windows tool (despite cross-platform support, most Linux users prefer Bash or CLI). There are no Bash, Azure CLI, or Linux-native shell examples. REST API and ARM template deployment steps are also shown using PowerShell. Even the Python example uses Windows-centric environment variables and patterns. The documentation does not mention or demonstrate Linux workflows, nor does it provide parity for Linux users who may use Bash, Azure CLI, or other native tools.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands for all PowerShell examples.
  • Provide Bash shell script examples for REST API calls and ARM template deployments.
  • Explicitly mention Linux support and provide steps for Linux environments, including authentication and environment variable handling.
  • Clarify cross-platform compatibility for PowerShell scripts, or recommend alternatives for Linux users.
  • Include troubleshooting and verification steps using Azure CLI and Bash.
  • Ensure that Python examples work seamlessly on Linux and document any OS-specific considerations.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-child-runbooks.md .../main/articles/automation/automation-child-runbooks.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
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-based runbooks and Windows-centric tools and patterns. All examples use PowerShell syntax and cmdlets, such as Start-AzAutomationRunbook, Get-AzVM, and Disable-AzContextAutosave, with no mention of Linux-native scripting languages (e.g., Bash, Python) or cross-platform alternatives. Windows/PowerShell terminology is used exclusively, and there are no Linux or non-PowerShell examples or guidance. The documentation assumes the user is working in a Windows/PowerShell environment, omitting Linux-specific considerations and parity.
Recommendations
  • Provide equivalent examples using Python runbooks, which are supported in Azure Automation and commonly used on Linux.
  • Include Bash or shell script runbook examples and guidance for Linux users.
  • Mention cross-platform considerations, such as authentication and context management for Linux-based runbooks.
  • Clarify which features and cmdlets are available or limited on Linux, and provide alternatives where possible.
  • Add links to documentation for creating and managing runbooks in Linux environments.
  • Avoid using Windows/PowerShell terminology exclusively; use neutral language where possible.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-managing-data.md ...b/main/articles/automation/automation-managing-data.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas: Windows-specific instructions and links are presented before Linux equivalents, PowerShell cmdlets are referenced heavily for resource management and backup, and Windows registry/TLS settings are described in detail while Linux guidance is minimal or generic. Linux examples are limited, with only a single Python script for TLS configuration and no Linux-native command-line or automation tool references for backup/export tasks.
Recommendations
  • Provide Linux-native examples for all resource management and backup operations, such as using Azure CLI, Bash scripts, or Python scripts for exporting runbooks, DSC configurations, and other assets.
  • Reference Linux tools and patterns (e.g., cron jobs, shell scripts, Azure CLI) alongside or before Windows/PowerShell equivalents to ensure parity.
  • Include explicit instructions for Linux users on how to confirm TLS settings, export resources, and manage assets, rather than relying on generic OpenSSL references.
  • Balance the documentation by giving equal prominence and detail to Linux and Windows procedures, including links to relevant Linux documentation.
  • Avoid assuming PowerShell is the default automation tool; mention cross-platform alternatives like Azure CLI or REST API where possible.
GitHub Create Pull Request
← Previous Page 3 of 15 Next →