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 301-325 of 982 flagged pages
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/how-to/move-account.md ...s/blob/main/articles/automation/how-to/move-account.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 providing only PowerShell examples for resource deletion and management, referencing Windows-centric tools (PowerShell cmdlets), and omitting equivalent Azure CLI or REST API examples that would be more familiar to Linux users. The workflow and instructions prioritize the Azure portal and PowerShell, with no mention of Linux shell commands or cross-platform alternatives.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all resource management steps, especially for deleting resources and action groups.
  • Explicitly mention that PowerShell is available cross-platform, but also provide bash/CLI syntax for Linux users.
  • Include REST API sample requests for key operations, or link to relevant REST API documentation.
  • Ensure that instructions do not assume familiarity with Windows tools or terminology; clarify when steps are platform-agnostic.
  • Consider a section or callout for Linux/macOS users, highlighting cross-platform approaches and tools.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/manage-runbooks.md ...-docs/blob/main/articles/automation/manage-runbooks.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. All code examples and automation patterns are provided exclusively in PowerShell, with no Bash, Python, or Linux-native CLI equivalents. File paths and script references use Windows conventions (e.g., C:\Runbooks\), and Windows-centric tools and terminology (PowerShell, .ps1 files) are used throughout. There is no mention of Linux shell scripting, Azure CLI, or cross-platform alternatives, and Windows/PowerShell approaches are always presented first or exclusively.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for all PowerShell code samples.
  • Include Linux file path conventions and clarify cross-platform compatibility for runbook scripts.
  • Mention and provide guidance for authoring and managing runbooks using Python and Bash, especially for Linux-based Hybrid Runbook Workers.
  • Explicitly state platform requirements and limitations for each example (e.g., PowerShell vs. Bash vs. Python).
  • Where PowerShell cmdlets are referenced, provide links or examples for Azure CLI commands achieving the same tasks.
  • Balance the documentation structure so that Linux and cross-platform approaches are presented alongside Windows/PowerShell methods, not only as afterthoughts.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/install-hybrid-worker-extension.md ...omation/quickstarts/install-hybrid-worker-extension.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on installing the Hybrid Worker extension on Windows Azure Virtual Machines. The step-by-step instructions, screenshots, and extension selection are all specific to Windows ('Azure Automation Windows Hybrid Worker'), with no equivalent Linux example or mention of the Linux extension. The prerequisites also only mention a Windows VM, and there are no Linux-specific instructions, screenshots, or troubleshooting notes. References to PowerShell and Windows tools are present, while Linux patterns are absent.
Recommendations
  • Add parallel instructions and screenshots for installing the Hybrid Worker extension on Linux Azure Virtual Machines.
  • Explicitly mention and show how to select the Linux Hybrid Worker extension in the Azure portal.
  • Include Linux VM as a prerequisite option, and clarify any differences in the installation process or requirements.
  • Provide troubleshooting notes or links specific to Linux installations.
  • Ensure that examples and terminology are balanced between Windows and Linux, avoiding Windows-first ordering.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/tutorial-configure-servers-desired-state.md ...automation/tutorial-configure-servers-desired-state.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All code examples use PowerShell and target Windows Server VMs, with explicit references to Windows features (e.g., IIS installation). Prerequisites and instructions focus exclusively on Windows environments, and there are no Linux-specific examples, tools, or configuration patterns. While Linux support is mentioned in passing, it is not demonstrated or explained. Windows tools and patterns (PowerShell, WindowsFeature resource) are used exclusively throughout.
Recommendations
  • Add equivalent examples for Linux machines, such as configuring Apache or Nginx using DSC resources for Linux.
  • Include instructions for onboarding and managing Linux VMs, with relevant DSC configuration samples.
  • Provide Bash/CLI examples where possible, or reference cross-platform tools.
  • Clarify the current support status for Linux in Azure Automation State Configuration, especially in light of the retirement announcement.
  • Ensure documentation sections for prerequisites, onboarding, and configuration are platform-neutral or have parallel guidance for Linux.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/source-control-integration.md ...main/articles/automation/source-control-integration.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 command-line examples use PowerShell, with no mention of Bash, Azure CLI, or Linux-native workflows. The prerequisites and configuration steps assume the use of PowerShell consoles, and references to file encoding issues link to PowerShell/VSCode documentation. There are no Linux or cross-platform command-line examples, nor any discussion of how to perform these tasks on non-Windows systems. Windows tools and patterns (PowerShell, .ps1 files, PowerShell Workflow) are mentioned exclusively and/or first.
Recommendations
  • Add equivalent Azure CLI and/or Bash examples for all PowerShell commands, especially for role assignment and source control configuration.
  • Explicitly mention cross-platform support and provide guidance for performing these tasks on Linux/macOS systems.
  • Include references to Linux editors and encoding issues, not just PowerShell/VSCode.
  • Clarify whether runbook synchronization supports scripts written for Linux environments and provide examples if so.
  • Review and update screenshots and instructions to ensure they are not Windows-centric (e.g., avoid references to 'PowerShell console with elevated privileges').
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/enable-managed-identity.md ...cles/automation/quickstarts/enable-managed-identity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on enabling managed identities via the Azure portal UI, which is platform-agnostic. However, the only next step provided is a tutorial for creating a PowerShell runbook, implicitly prioritizing Windows and PowerShell workflows. There are no references to Linux or cross-platform scripting options (e.g., Python runbooks), nor are there CLI or automation examples using Bash, Azure CLI, or other Linux-friendly tools.
Recommendations
  • Include links or examples for creating and using managed identities in Linux environments, such as Bash or Python runbooks.
  • Provide parity by referencing tutorials for both PowerShell and Python runbooks using managed identities.
  • Add Azure CLI or REST API instructions for enabling managed identities, which are platform-neutral and widely used on Linux.
  • Explicitly mention that the Azure portal UI can be accessed from any OS, and clarify that runbooks can be authored in multiple languages.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/shared-resources.md ...n/articles/automation/troubleshoot/shared-resources.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 troubleshooting and examples, which are primarily Windows-centric. All code samples use PowerShell cmdlets and scripts, with no mention of Bash, CLI, or Linux-native tools. Windows-specific DLL errors are discussed without Linux equivalents or guidance. There is no coverage of how these issues or resolutions would apply in a Linux environment, nor are Linux automation patterns or tools referenced.
Recommendations
  • Provide equivalent troubleshooting steps and examples using Azure CLI and Bash scripts for Linux users.
  • Include guidance for resolving module import issues when using Linux-based Hybrid Workers or Automation accounts.
  • Discuss how DLL-related errors manifest (or do not) in Linux environments and offer Linux-specific troubleshooting advice.
  • Reference Linux-native tools and patterns (e.g., systemd, cron, shell scripting) where relevant.
  • Ensure that examples and resolutions are presented for both Windows and Linux platforms, or clarify platform-specific limitations.
  • Add notes or sections explicitly addressing Linux users and cross-platform considerations.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/managed-identity.md ...n/articles/automation/troubleshoot/managed-identity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively uses PowerShell cmdlets and scripting patterns (e.g., Connect-AzAccount, Get-AzVM, Invoke-RestMethod) for troubleshooting Azure Automation managed identity issues. There are no examples or references to Linux shell commands, Bash, Azure CLI, or cross-platform scripting approaches. The troubleshooting steps and code samples assume a Windows/PowerShell environment, which may disadvantage users operating on Linux or preferring non-PowerShell tools.
Recommendations
  • Provide equivalent troubleshooting examples using Azure CLI (az commands) and Bash scripts for each scenario.
  • Explicitly mention that the PowerShell examples are Windows-centric and offer guidance for Linux users.
  • Include notes or links to documentation for using managed identities with Linux-based Hybrid Runbook Workers.
  • Add cross-platform code samples and clarify which steps/tools are OS-agnostic versus Windows-specific.
  • Ensure screenshots and UI instructions are relevant for both Windows and Linux environments where applicable.
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: 2026-01-09 00:34
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 using PowerShell-based examples, referencing Windows-centric cmdlets (e.g., Start-AzAutomationRunbook, Disable-AzContextAutosave), and omitting any Linux shell (Bash, Python) or cross-platform scripting alternatives. All examples and troubleshooting steps are presented with PowerShell syntax and tools, with no mention of Linux-native approaches or parity for users who may prefer Bash or Python runbooks. The documentation also refers to 'Start a runbook with Windows PowerShell' and does not provide Linux-first or cross-platform guidance.
Recommendations
  • Add equivalent examples for Bash and Python runbooks, showing how to call child runbooks and handle parameters/output.
  • Include references to Linux-native tools and scripting environments supported by Azure Automation.
  • Present cross-platform guidance, making it clear which features and patterns work on both Windows and Linux environments.
  • Reorder sections or add notes to clarify that Azure Automation supports multiple runbook types, not just PowerShell.
  • Explicitly mention any limitations or differences for Linux-based runbooks and provide workarounds or alternatives.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-connections.md ...lob/main/articles/automation/automation-connections.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 tooling. All command-line examples for creating and managing connections use PowerShell cmdlets (Az modules), with no mention of Bash, Azure CLI, or Linux-native approaches. The phrase 'Windows PowerShell' is used explicitly, and PowerShell cmdlets are introduced before Python examples. There are no Linux shell or cross-platform CLI examples for managing connections, and the workflow assumes a Windows-centric environment. The documentation also references Windows-specific patterns (e.g., PowerShell hashtables, cmdlets) and does not provide parity for Linux users.
Recommendations
  • Add equivalent Azure CLI (az) examples for creating, listing, and managing Automation connections, and show how to use them from Linux/macOS.
  • Include Bash shell script examples for common operations, or clarify if certain operations are only possible via PowerShell.
  • When introducing command-line tools, present cross-platform options (e.g., Azure CLI) before or alongside PowerShell.
  • Clarify which features or examples are Windows-specific, and provide guidance for Linux/macOS users where possible.
  • Consider adding a section on managing connections via REST API or ARM templates, which are platform-agnostic.
  • Ensure that all code samples and workflows are tested and documented for both Windows and Linux environments.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing AWS credential management via the AWS PowerShell user guide and omitting Linux or cross-platform alternatives. The only external credential management link is for PowerShell, and there are no examples or instructions for Linux users (e.g., AWS CLI usage, Linux credential storage patterns). The documentation implicitly assumes a Windows-centric workflow and does not mention Linux tools or provide parity for non-Windows environments.
Recommendations
  • Include links and examples for AWS credential management using the AWS CLI, which is cross-platform and widely used on Linux.
  • Add instructions or references for storing and managing AWS credentials on Linux systems, such as using environment variables or the ~/.aws/credentials file.
  • Ensure that all steps and examples are platform-neutral or provide both Windows (PowerShell) and Linux (CLI, Bash) alternatives.
  • Explicitly mention that Azure Automation runbooks can be authored and executed from Linux environments, and provide guidance for those scenarios.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-compile.md ...lob/main/articles/automation/automation-dsc-compile.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 workflows are exclusively presented using Windows PowerShell and Windows-centric tools (e.g., WindowsFeature resource, C: paths, PowerShell cmdlets). There is no mention of Linux equivalents, nor are any Linux-specific examples or tools provided. The documentation repeatedly refers to Windows PowerShell as the primary or only method for compiling DSC configurations, and references to Linux support are limited to a retirement announcement, with no guidance for Linux users.
Recommendations
  • Add examples for compiling DSC configurations on Linux, using cross-platform PowerShell Core or native Linux tools where possible.
  • Include Linux-specific resources and patterns (e.g., using DSC resources for Linux, Linux file paths, and node configuration examples targeting Linux VMs).
  • Clearly indicate platform compatibility for each method and cmdlet, specifying whether they work on Windows, Linux, or both.
  • Provide guidance for Linux users affected by the retirement, including migration paths or alternatives.
  • Ensure that documentation structure does not always present Windows methods first; consider parallel presentation of Windows and Linux workflows.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-config-from-server.md ...ticles/automation/automation-dsc-config-from-server.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page is heavily biased towards Windows and PowerShell. All examples and tools referenced (ReverseDSC, SharePointDSC, MOF files, PowerShell DSC) are Windows-centric, with no Linux equivalents or examples provided. The prerequisites and next steps focus exclusively on Windows PowerShell 5.1 and Windows DSC resources, and there is no guidance for Linux users or mention of cross-platform alternatives.
Recommendations
  • Include examples and instructions for Linux environments, such as using DSC on Linux or alternative configuration extraction tools.
  • Mention and link to Linux-compatible DSC resources and modules, if available.
  • Clarify whether ReverseDSC or similar tools can be used on Linux servers, and provide steps or limitations.
  • Add parity in documentation structure, ensuring Linux onboarding and configuration steps are described alongside Windows.
  • Update prerequisites and next steps to reference cross-platform PowerShell and DSC resources, not just Windows PowerShell 5.1.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-create-standalone-account.md ...les/automation/automation-create-standalone-account.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 predominantly featuring PowerShell examples and references, mentioning PowerShell runbooks and cmdlets first and exclusively, and omitting equivalent Linux or cross-platform CLI examples (such as Azure CLI or Bash). There is no mention of Linux tools or workflows, and the instructions for key rotation and account management only provide PowerShell and portal methods, both of which are more familiar to Windows users.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all automation account management tasks, including key rotation.
  • Provide Bash or shell script examples where applicable, especially for Linux users.
  • Mention Python runbooks earlier and equally alongside PowerShell runbooks in the 'Next steps' section.
  • Include references to Linux-friendly tools and workflows, such as using SSH, Bash, or cross-platform scripting.
  • Ensure that screenshots and instructions are not exclusively tailored to Windows environments; clarify cross-platform compatibility.
  • Explicitly state that all steps can be performed from Linux, macOS, or Windows, and provide guidance for each platform where differences exist.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-cd-chocolatey.md ...in/articles/automation/automation-dsc-cd-chocolatey.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. All examples, instructions, and tooling references are specific to Windows (e.g., Chocolatey, PowerShell DSC, Windows Management Framework, WindowsFeature DSC resource). There are no Linux equivalents or examples provided, and Linux is only mentioned in passing (e.g., apt-get as a comparison, and a retirement announcement for Linux DSC). The step-by-step setup, code samples, and resource references are exclusively for Windows, with no guidance for Linux users.
Recommendations
  • Provide parallel examples for Linux environments, such as using apt, yum, or other Linux package managers.
  • Include instructions for setting up Azure Automation State Configuration for Linux VMs, if supported.
  • Reference Linux DSC resources or alternatives, and clarify the current support status for Linux.
  • Offer sample configuration scripts for Linux nodes, using Bash or Python where appropriate.
  • Mention Linux VM extensions and how they can be used in Resource Manager templates.
  • Clearly state any limitations or retirement of Linux support, and suggest alternatives for Linux users.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-config-data-at-scale.md ...cles/automation/automation-dsc-config-data-at-scale.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 instructions referencing Windows PowerShell DSC and related tooling. There is no mention of Linux equivalents, nor are there examples or guidance for configuring data at scale on Linux systems. References to configuration management are exclusively in the context of PowerShell DSC, which is primarily a Windows technology.
Recommendations
  • Add explicit guidance and examples for Linux systems, such as using DSC for Linux or alternative configuration management tools (e.g., Ansible, Chef, Puppet).
  • Include Linux-specific steps for organizing and applying configuration data at scale, and clarify any differences in file formats, tooling, or workflows.
  • Reference cross-platform DSC capabilities and provide links to documentation for Linux node onboarding and management.
  • Balance references to PowerShell DSC with mentions of open-source, cross-platform solutions where appropriate.
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: 2026-01-09 00:34
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 tools (such as PowerSTIG and DSC) being Windows-centric. There are no Linux-specific examples or equivalent Linux tooling mentioned, and the prerequisites and next steps all reference Windows PowerShell and related resources. Linux is only briefly mentioned in the context of onboarding, without any guidance or parity in configuration or tooling.
Recommendations
  • Include Linux-specific examples for configuring STIG baselines, such as using Ansible, Chef, or native Linux DSC implementations.
  • Mention and link to Linux equivalents for PowerSTIG or provide guidance on how to achieve similar compliance on Linux systems.
  • Update the 'Next steps' section to include resources for Linux configuration management and compliance.
  • Clarify in the introduction that the current guidance is Windows-focused, and provide a roadmap or references for Linux users.
  • If Azure Automation State Configuration supports Linux, provide explicit walkthroughs or documentation links for Linux scenarios.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-diagnostics.md ...main/articles/automation/automation-dsc-diagnostics.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 example commands use PowerShell, and prerequisites reference PowerShell modules and tools exclusively. There are no equivalent instructions or examples for Linux users (e.g., Bash, Azure CLI), nor is there mention of Linux-native tooling or workflows. The documentation assumes the user is operating from a Windows environment, with no guidance for Linux or cross-platform scenarios.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, especially for authentication, resource ID retrieval, and diagnostic settings configuration.
  • Include instructions for running these steps from Linux or macOS environments, clarifying any differences in setup or tool installation.
  • Reference Linux-compatible DSC modules and clarify the current support status for Linux nodes, given the retirement announcement.
  • Provide links or sections for troubleshooting and setup on Linux, including onboarding and viewing logs.
  • Balance references to PowerShell with Azure CLI and REST API options, and avoid assuming a Windows-first workflow.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-extension-history.md ...rticles/automation/automation-dsc-extension-history.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exclusively covers Windows operating systems and Windows-specific tooling (such as Windows Management Framework and PowerShell DSC), with no mention of Linux support, Linux distributions, or equivalent Linux tooling. All examples, OS support lists, and troubleshooting steps are Windows-centric. There are no Linux examples, and the only reference to Linux is in a retirement announcement include, with no further details or parity information.
Recommendations
  • Explicitly document the status of Linux support for the Azure DSC extension, including which versions (if any) supported Linux and when support was retired.
  • If Linux support was present in previous versions, add a dedicated section summarizing Linux support history, including supported distributions, extension versions, and any differences in feature sets.
  • Provide equivalent Linux examples or troubleshooting steps where applicable, or clearly state when features are Windows-only.
  • Reference Linux configuration management alternatives (such as Chef, Puppet, or Ansible) for Azure VMs, and link to relevant Azure documentation for those tools.
  • Clarify in the introduction and version tables that the documented extension versions are Windows-only, and direct Linux users to appropriate resources or migration guides.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-onboarding.md .../main/articles/automation/automation-dsc-onboarding.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 oriented toward Windows and PowerShell workflows. Windows and PowerShell examples are presented first and in greater detail, with Linux instructions often appearing later and relying on Windows/PowerShell tooling for onboarding. Many steps for Linux require a Windows machine with PowerShell to generate configurations, and Linux-specific tooling and examples are minimal or secondary. Some features and cmdlets are explicitly Windows-only, and Linux users are often directed to use Python scripts or PowerShell from Windows hosts.
Recommendations
  • Provide Linux-first and Linux-native examples for onboarding and configuration, using Bash, Python, or native Linux tools.
  • Document how to generate DSC metaconfigurations entirely on Linux, without requiring a Windows/PowerShell host.
  • Clarify which steps or cmdlets are Windows-only and offer equivalent Linux alternatives where possible.
  • Expand Linux-specific troubleshooting and operational guidance, including common Linux issues and their resolution.
  • Ensure parity in example depth and clarity between Windows and Linux sections, including screenshots and step-by-step instructions.
  • Highlight any limitations or retirement notices for Linux support at the top of the document, and link to migration or alternative solutions for Linux users.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-edit-textual-runbook.md ...articles/automation/automation-edit-textual-runbook.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 workflows. All code examples use Windows PowerShell, with Windows file paths (e.g., c:\runbooks), and there is no mention of Linux or cross-platform alternatives. The use of Windows-specific terminology and tools (such as Windows PowerShell and Windows file system paths) excludes Linux users and those using PowerShell Core on non-Windows platforms. There are no Bash or Linux shell examples, nor any guidance for editing runbooks from Linux or macOS environments.
Recommendations
  • Include examples using PowerShell Core (pwsh), which is cross-platform, and clarify compatibility with Linux/macOS.
  • Provide equivalent instructions and examples for Linux and macOS users, including file paths and shell usage.
  • Mention and demonstrate how to use Az.Automation cmdlets from non-Windows platforms.
  • Add notes on any platform-specific limitations or requirements.
  • Consider including Bash or Azure CLI examples for common runbook management tasks.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-hybrid-runbook-worker.md ...rticles/automation/automation-hybrid-runbook-worker.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 mild Windows bias. PowerShell and Windows-centric tools are mentioned as onboarding channels before Linux equivalents, and references to authentication and permissions link to Windows-specific tutorials. While Linux is acknowledged as a supported platform and the extension-based installation is described as working for both Windows and Linux, examples, walkthroughs, and links tend to prioritize Windows or PowerShell. There are no explicit Linux shell or configuration examples, and the documentation does not provide parity in guidance for Linux-specific scenarios or tools.
Recommendations
  • Provide explicit Linux shell (bash) and configuration examples alongside PowerShell examples for installation, management, and troubleshooting.
  • Ensure onboarding channels (e.g., Azure CLI, REST API) are demonstrated with Linux usage and not only PowerShell.
  • Include links to Linux-specific authentication and permissions tutorials, such as managed identities for Linux VMs.
  • Clarify any differences in behavior, accounts, or permissions between Windows and Linux Hybrid Runbook Workers.
  • Add troubleshooting steps and examples for common Linux-specific issues.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-getting-started.md .../articles/automation/automation-dsc-getting-started.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All code examples use Windows PowerShell DSC syntax and resources (e.g., WindowsFeature), with no Linux equivalents or cross-platform DSC resources shown. The VM creation instructions and links are exclusively for Windows VMs, and references to DSC documentation and tools are Windows-centric. Linux support is only mentioned in retirement notices, and there are no practical Linux onboarding, configuration, or resource examples.
Recommendations
  • Add equivalent Linux DSC configuration examples, such as using nxFile or nxPackage resources.
  • Include instructions and links for creating and onboarding Linux VMs to Azure Automation State Configuration.
  • Reference cross-platform DSC documentation and resources, not just Windows PowerShell DSC.
  • Clarify current support status and alternatives for Linux users, especially given the retirement notice.
  • Present examples and instructions for both Windows and Linux in parallel, or clearly indicate platform-specific sections.
  • Provide guidance for managing Linux nodes, including configuration, compilation, and reporting steps.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-overview.md ...ob/main/articles/automation/automation-dsc-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias by primarily referencing PowerShell DSC, listing Windows operating systems and requirements first and in detail, and mentioning Windows-specific tools and patterns (e.g., WMF, WinRM, Chocolatey) without equivalent Linux examples or tools. Linux support is referenced but lacks parity in examples, details, and tooling guidance.
Recommendations
  • Provide Linux-specific examples for onboarding, configuration, and troubleshooting, similar to the Windows/PowerShell examples.
  • Include references to Linux-native configuration management tools or patterns (e.g., Ansible, Chef, native DSC for Linux) where appropriate.
  • List supported Linux distributions explicitly, not just by reference to external documentation.
  • Offer example workflows and scripts for Linux nodes, including proxy configuration and reporting.
  • Balance the order of presentation so that Linux and Windows are treated equally in lists and explanations.
  • Include guidance for Linux users on compiling and managing DSC configurations, with screenshots or CLI examples.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-remediate.md ...b/main/articles/automation/automation-dsc-remediate.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page prioritizes Windows remediation by presenting PowerShell-based examples and tools first, with detailed instructions and direct commands. Linux remediation is described in less detail, lacks direct script examples, and is presented as less capable (e.g., Run Command not available, registration must be repeated). References and next steps also focus on Windows tools and workflows, with Linux alternatives mentioned only briefly or as external links.
Recommendations
  • Provide equivalent Linux script examples for remediation, such as shell or Python commands that can be run manually or via automation.
  • Clarify and expand on Linux workflows, including step-by-step instructions for correcting drift, not just links to external documentation.
  • Mention Linux tools and patterns (e.g., cloud-init, Ansible, or native DSC for Linux) alongside Windows tools, and avoid implying Windows-first capabilities.
  • Ensure next steps and references include Linux-specific resources and examples, not just PowerShell or Windows-centric links.
  • Explicitly state any feature parity gaps and offer alternative solutions for Linux users where Azure features differ.
GitHub Create Pull Request
← Previous Page 13 of 40 Next →