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 126-150 of 982 flagged pages
Automation Encryption of secure assets in Azure Automation ...icles/automation/automation-secure-asset-encryption.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell examples for all command-line operations, referencing Windows-centric tools (Azure Az PowerShell module) and cmdlets, and omitting equivalent instructions for Linux users (e.g., Bash, Azure CLI). PowerShell is presented as the primary or only scripting interface, and there are no examples or guidance for Linux shell environments or cross-platform automation tools. REST API examples are included, but the CLI and Bash alternatives are missing, and PowerShell is always presented before REST. The prerequisites and next steps also reference PowerShell modules and documentation, reinforcing the Windows-centric approach.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all command-line operations, including account identity assignment, Key Vault access policy configuration, and key management.
  • Reference cross-platform tools (e.g., Azure CLI) in prerequisites and next steps, not just PowerShell modules.
  • Explicitly state that all operations can be performed from Linux, macOS, or Windows, and provide guidance for non-Windows environments.
  • Where PowerShell is used, clarify that it is available cross-platform, but also offer native Bash/CLI alternatives for Linux users.
  • Ensure that REST API examples are supplemented with CLI equivalents, and provide sample scripts for Linux shell 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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell examples and referencing Windows-centric tools (e.g., PowerShell cmdlets like Invoke-AzRestMethod and Get-AzAutomationAccount). There are no equivalent examples for Linux users (such as using curl or Azure CLI), and the instructions assume familiarity with PowerShell, which is primarily associated with Windows environments. This may hinder accessibility for users working on Linux or macOS platforms.
Recommendations
  • Add equivalent examples using Azure CLI and REST API via curl for Linux/macOS users.
  • Present cross-platform instructions side-by-side, or indicate which commands are platform-specific.
  • Reference and link to documentation for Linux tools and patterns where appropriate.
  • Avoid assuming PowerShell as the default; clarify that PowerShell is one option among several.
  • Explicitly state platform requirements or compatibility for each method.
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-11 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 mild Windows bias. PowerShell is mentioned explicitly before Azure CLI, and the error handling and deployment instructions prioritize PowerShell syntax and patterns. There are no explicit Linux-specific examples, nor is Bash mentioned. The references to 'PowerShell/CLI' tend to put PowerShell first, and the sample runbooks include PowerShell and Python, but not Bash or Linux shell scripts.
Recommendations
  • Provide explicit Bash/Linux shell examples alongside PowerShell and Azure CLI for template deployment.
  • Alternate the order of PowerShell and CLI instructions to avoid implicit prioritization of Windows tools.
  • Include sample runbooks for Bash or other Linux-native scripting languages to demonstrate parity.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Add troubleshooting notes for common Linux-specific issues (e.g., file permissions, environment variables) when deploying ARM templates.
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-11 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 and PowerShell bias. Nearly all code examples use PowerShell, with no Bash, CLI, or Linux-native scripting alternatives provided. Even REST API and ARM template deployment examples are wrapped in PowerShell scripts. The prerequisites and instructions frequently reference Windows tools and patterns first, and Linux equivalents are only mentioned briefly or not at all. There are no examples using Azure CLI, Bash, or Linux shell scripting, and the Python example is generic rather than tailored to Linux environments. This lack of Linux parity may hinder users who prefer or require Linux-based automation.
Recommendations
  • Add equivalent examples using Azure CLI and Bash for all major steps, including enabling managed identity, assigning roles, and authenticating.
  • Provide Linux-native scripting examples (e.g., Bash scripts using curl for REST API calls) alongside PowerShell.
  • Ensure that instructions for checking Hybrid Runbook Worker versions and other operational steps are presented for both Windows and Linux, with equal detail.
  • Include examples of using managed identity in Python runbooks that demonstrate Linux-specific considerations (e.g., environment variables, file paths).
  • Where PowerShell is used to interact with REST APIs or ARM templates, provide parallel examples using curl, jq, or Azure CLI.
  • Review the order of presentation so that Windows and Linux approaches are given equal prominence, rather than Windows-first.
GitHub Create Pull Request
Automation Manage Python 3 packages in Azure Automation ...ocs/blob/main/articles/automation/python-3-packages.md
High Priority View Details →
Scanned: 2026-01-11 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 displays a Windows bias in several areas. For Python 3.8, instructions and examples are provided for Windows environments first and exclusively, such as generating wheel files using a Windows machine and referencing Windows-specific wheel filenames. PowerShell cmdlets are heavily featured for package management, with no Linux CLI or Bash alternatives shown. There is a lack of parity in examples for Linux users, especially for Hybrid Runbook Workers running on Linux, and Windows tools/patterns are mentioned without Linux equivalents.
Recommendations
  • Provide Linux-based examples for Python 3.8 package preparation, including wheel file generation on Linux.
  • Include Bash or Azure CLI equivalents for PowerShell cmdlets used to manage Python packages.
  • Mention Linux-specific wheel filename patterns and clarify when Windows or Linux environments are required.
  • Ensure instructions for both Windows and Linux environments are presented in parallel, not Windows-first.
  • Add guidance for managing packages on Linux Hybrid Runbook Workers, including troubleshooting and environment setup.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation State Configuration issues ...automation/troubleshoot/desired-state-configuration.md
High Priority View Details →
Scanned: 2026-01-11 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 is heavily focused on Windows and PowerShell tooling. Most troubleshooting steps, examples, and commands are presented using PowerShell cmdlets and Windows-centric tools (e.g., xDscDiagnostics, PowerShell DSC extension, w32tm). Linux is mentioned only in a few scenarios, often as an exception or in a single dedicated section. There are few, if any, Linux-specific troubleshooting steps, commands, or parity in examples. Windows tools and patterns are referenced first and more frequently, while Linux equivalents are largely absent.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples for each scenario, especially where PowerShell or Windows tools are referenced.
  • Include Linux command-line equivalents (e.g., bash, journalctl, systemctl) alongside PowerShell commands for log collection, certificate management, and agent registration.
  • Reference Linux DSC extension documentation and tools where appropriate, and clarify differences in workflow or error handling for Linux nodes.
  • Ensure that links and references to onboarding, configuration, and troubleshooting are provided for both Windows and Linux, not just Windows.
  • Add explicit notes or sections for Linux users in scenarios that currently only mention Windows or PowerShell.
  • Where Windows tools (e.g., w32tm) are used, provide Linux alternatives (e.g., ntpdate, timedatectl) for time synchronization troubleshooting.
GitHub Create Pull Request
Automation Remove user-assigned managed identity for Azure Automation account ...n/articles/automation/remove-user-assigned-identity.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based examples for command-line and scripting tasks, including REST API invocation and verification steps. No Linux shell (bash, Azure CLI, curl) examples are given, and Windows/PowerShell tools are mentioned first and exclusively. This limits accessibility for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all operations, especially for removing managed identities and verifying account status.
  • Provide REST API invocation examples using curl or httpie, which are available on Linux/macOS.
  • Include bash shell script snippets alongside PowerShell for variable assignment and file manipulation.
  • Mention cross-platform tools and approaches before or alongside Windows/PowerShell-specific methods.
  • Clarify that PowerShell Core is available on Linux/macOS, but still provide native Linux shell alternatives.
GitHub Create Pull Request
Automation Quickstart - Create an Azure Automation account using the portal .../quickstarts/create-azure-automation-account-portal.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 using the Azure portal UI to create an Automation account, with no mention of Linux-specific tools, CLI commands, or cross-platform alternatives. The only 'Next steps' link is to a PowerShell runbook tutorial, which is Windows-centric. There are no examples or references to Bash, Azure CLI, or Linux automation patterns, and the documentation implicitly assumes a Windows/PowerShell workflow for further automation.
Recommendations
  • Include links to tutorials for creating Automation accounts using Azure CLI and Bash scripts, which are cross-platform and commonly used on Linux.
  • Add 'Next steps' options for creating runbooks using Python or Bash, not just PowerShell.
  • Mention that Automation accounts and managed identities can be managed via REST API, Azure CLI, or ARM templates, with examples.
  • Ensure screenshots and instructions do not assume a Windows environment; clarify that the Azure portal is browser-based and OS-agnostic.
  • Provide parity in documentation for Linux users by referencing Linux-friendly automation tools and workflows.
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 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 environments and PowerShell usage. All examples use Windows-specific tools (PowerShell, WindowsFeature), and the tutorial is centered on configuring IIS on Windows Server. Prerequisites and instructions reference only Windows VMs and PowerShell DSC, with no Linux configuration examples or parity in onboarding, configuration, or compliance checking. Linux support is only mentioned in passing, and a retirement announcement for Linux DSC is included, further reducing Linux relevance.
Recommendations
  • Add equivalent Linux onboarding and configuration examples using supported tools (e.g., DSC for Linux, or alternatives if DSC is deprecated).
  • Include sample configurations for common Linux workloads (e.g., installing Apache or Nginx) alongside the IIS/Windows example.
  • Provide guidance for managing Linux VMs with Azure Automation State Configuration, or clearly state limitations and alternatives if Linux support is deprecated.
  • Reference Linux documentation and tooling where appropriate, and avoid presenting Windows as the default or only supported platform.
  • If Linux support is deprecated, offer migration paths or alternative solutions for Linux users.
GitHub Create Pull Request
Automation Start a runbook in Azure Automation ...e-docs/blob/main/articles/automation/start-runbooks.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing examples and instructions for Windows PowerShell, referencing Windows-specific tools and cmdlets, and omitting equivalent Linux or cross-platform CLI examples. The PowerShell method is highlighted before any mention of cross-platform alternatives, and there is no mention of Azure CLI, Bash, or other Linux-friendly approaches for starting runbooks. The documentation assumes the reader is using Windows and PowerShell, with no guidance for users on Linux or macOS platforms.
Recommendations
  • Add Azure CLI examples for starting runbooks, including parameter passing and job status tracking.
  • Include Bash or shell script samples for interacting with the Azure Automation API.
  • Clarify which methods are cross-platform and which are Windows-specific, ideally listing cross-platform methods first.
  • Reference Linux and macOS compatibility in relevant sections, and link to documentation for those platforms.
  • Provide guidance on installing and using PowerShell Core (pwsh) on Linux/macOS if PowerShell is required.
  • Ensure that all code samples and instructions are available for both Windows and Linux environments.
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-11 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 by exclusively providing PowerShell-based troubleshooting steps and examples, referencing Windows-centric tools (such as PowerShell cmdlets and .psd1/.psm1 files), and omitting any Linux or cross-platform alternatives. There are no Bash, CLI, or Linux-specific instructions, and all examples assume the user is operating in a Windows/PowerShell environment.
Recommendations
  • Add equivalent troubleshooting steps using Azure CLI and Bash scripts for Linux users.
  • Include notes or sections explaining how module import and management differ on Linux-based Automation accounts, if applicable.
  • Provide examples for authenticating and managing Azure Automation from Linux environments, including use of managed identities.
  • Reference cross-platform tools and patterns (such as Azure CLI, REST API, or SDKs) alongside PowerShell, rather than focusing solely on Windows tools.
  • Explicitly state platform requirements or limitations for each scenario, and offer guidance for non-Windows users.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation managed identity issues ...n/articles/automation/troubleshoot/managed-identity.md
High Priority View Details →
Scanned: 2026-01-11 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. All troubleshooting examples and code snippets use PowerShell cmdlets (e.g., Connect-AzAccount, Get-AzVM), which are native to Windows and not directly usable on Linux without installing PowerShell Core. There are no Bash, CLI, or Linux-native examples provided. The troubleshooting steps and error messages reference Windows-centric tools and workflows, such as PowerShell runbooks and Windows environment variables, with no mention of Linux alternatives or Azure CLI usage. This may hinder Linux users from effectively troubleshooting managed identity issues in Azure Automation.
Recommendations
  • Add equivalent troubleshooting steps and code examples using Azure CLI (az) and Bash scripts, which are native to Linux environments.
  • Include guidance for running runbooks on Linux Hybrid Runbook Workers, with examples using Bash or Python.
  • Explicitly mention cross-platform compatibility for each scenario, clarifying whether steps apply to both Windows and Linux Automation accounts.
  • Provide links to documentation on installing and using PowerShell Core on Linux, if PowerShell-based troubleshooting is required.
  • Ensure error messages and resolutions reference tools and commands available on both Windows and Linux platforms.
GitHub Create Pull Request
Automation Create modular runbooks in Azure Automation .../main/articles/automation/automation-child-runbooks.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell-based examples and cmdlets (e.g., Start-AzAutomationRunbook, Disable-AzContextAutosave), referencing Windows PowerShell and PowerShell Workflow runbooks, and omitting any Linux shell (Bash, Python) or cross-platform scripting examples. Windows/PowerShell tools and patterns are mentioned throughout, with no mention of Linux-native automation approaches or parity in examples.
Recommendations
  • Add equivalent examples using Bash, Python, or other Linux-supported runbook types if Azure Automation supports them.
  • Explicitly mention cross-platform support and limitations, clarifying which features are Windows/PowerShell-specific.
  • Provide guidance or links for Linux users on how to create and call modular runbooks using non-PowerShell languages.
  • List Linux-compatible tools or modules for Azure Automation, if available.
  • Reorder sections or add notes to avoid implying PowerShell/Windows is the default or only supported approach.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by exclusively providing PowerShell scripts and workflows for disaster recovery asset migration, with no equivalent examples or guidance for Linux-native tools or scripting languages (e.g., Bash, Python). The prerequisite modules and instructions focus on PowerShell, which is traditionally a Windows-centric tool, and the step-by-step instructions reference Windows tabs and patterns before Linux. There is no mention of Linux shell scripts or cross-platform alternatives, and the migration process is described only in terms of PowerShell, despite the page claiming applicability to both Linux and Windows VMs.
Recommendations
  • Provide equivalent Linux-native examples, such as Bash or Python scripts, for migrating Automation account assets.
  • Include instructions and prerequisites for running migration scripts on Linux systems, including required modules and environment setup.
  • Offer cross-platform guidance, such as using Azure CLI or REST API, which are available on both Windows and Linux.
  • Ensure that documentation tabs and examples are presented in parallel for both Windows and Linux, rather than Windows-first.
  • Clarify any platform-specific limitations or considerations for disaster recovery steps, especially for Linux users.
GitHub Create Pull Request
Automation Azure Automation network configuration details ...rticles/automation/automation-network-configuration.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 Windows-specific DSC resources (e.g., WaitFor resources with a Windows PowerShell documentation link) and omitting explicit Linux equivalents or examples. The documentation does not mention Linux DSC resources, nor does it provide guidance or examples for Linux Hybrid Runbook Worker or State Configuration scenarios. Windows terminology and links are presented without Linux parity.
Recommendations
  • Include references and links to Linux DSC resources and documentation, such as cross-platform DSC modules.
  • Provide explicit examples or notes for configuring Hybrid Runbook Worker and State Configuration on Linux systems.
  • Balance references to Windows and Linux tools, ensuring both are mentioned where applicable.
  • Add guidance for Linux-specific network requirements or considerations, if any.
  • Where PowerShell or Windows-specific resources are mentioned, add equivalent Linux instructions or clarify cross-platform applicability.
GitHub Create Pull Request
Automation Using a user-assigned managed identity for an Azure Automation account ...main/articles/automation/add-user-assigned-identity.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. Most code examples and instructions use PowerShell, a Windows-centric tool, and reference Windows-specific patterns (e.g., environment variable syntax, PowerShell cmdlets). PowerShell is presented as the primary automation method, with no Bash, CLI, or Linux shell examples. Even REST API and ARM template deployment steps use PowerShell for invocation. The Python example is the only non-Windows-centric code, but it is limited and does not cover the full workflow. There are no Linux shell, Azure CLI, or cross-platform scripting examples, and Windows tools are mentioned exclusively or before alternatives.
Recommendations
  • Add equivalent Azure CLI examples for all major steps, including authentication, resource management, and role assignment.
  • Provide Bash shell scripts for REST API calls and ARM template deployments, demonstrating Linux usage.
  • Include instructions for setting environment variables and file paths in both Windows and Linux formats.
  • Present cross-platform approaches first (e.g., Azure CLI, REST API via curl), then offer PowerShell as an alternative.
  • Expand Python examples to cover more scenarios, and consider adding examples in other popular scripting languages used on Linux.
  • Explicitly mention Linux support and test steps on Linux-based Automation Hybrid Workers.
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-11 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 the AWS PowerShell user guide for credential management, which is a Windows-centric tool, and by not providing equivalent Linux or cross-platform examples. There are no mentions of Linux tools or CLI alternatives, and the guidance assumes familiarity with Windows patterns (e.g., PowerShell, Azure Portal) without discussing Linux workflows.
Recommendations
  • Include examples using AWS CLI for credential management, which is cross-platform and commonly used on Linux.
  • Reference AWS documentation for Linux and macOS credential configuration, not just PowerShell.
  • Add instructions for storing and retrieving credentials using Linux shell scripts or automation tools.
  • Clarify that Azure Automation runbooks can be authored and executed using Python or other cross-platform languages, and provide sample code for these environments.
  • Ensure that all steps (such as credential asset creation) are described in a way that is platform-agnostic, or provide parallel instructions for Linux users.
GitHub Create Pull Request
Automation Use an alert to trigger an Azure Automation runbook ...utomation/automation-create-alert-triggered-runbook.md
High Priority View Details →
Scanned: 2026-01-11 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. All code examples and instructions use PowerShell, with no mention of Bash, Azure CLI, or Linux shell alternatives. The prerequisites and VM references point to Windows-specific resources, and Windows tools (PowerShell, Az PowerShell module) are used exclusively. There are no Linux or cross-platform examples, and the workflow assumes a Windows-centric approach to Azure Automation and VM management.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for runbook creation and VM management.
  • Include references and links to Linux VM quickstart guides alongside Windows VM links.
  • Provide instructions for installing and using Az modules on Linux/macOS environments.
  • Clarify that Azure Automation supports both Windows and Linux VMs, and show how to manage Linux VMs in runbooks.
  • Offer cross-platform code samples and highlight differences or considerations for Linux users.
  • Mention that the Azure portal and Automation features are OS-agnostic, and avoid implying a Windows-only workflow.
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 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows and PowerShell, with all examples and 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 for Linux systems. References to configuration management are exclusively in the context of Windows PowerShell DSC, and the prerequisites and next steps reinforce a Windows-centric approach.
Recommendations
  • Add explicit instructions and examples for configuring data at scale for Linux systems, including references to Linux-compatible DSC implementations (e.g., OMI-based DSC, cross-platform PowerShell DSC).
  • Include Linux shell (bash) or cross-platform PowerShell Core examples where applicable.
  • Clarify which steps or tools are Windows-only and provide Linux alternatives or note limitations.
  • Update prerequisites and next steps to include links and resources for Linux DSC usage and management.
  • Ensure that references to onboarding or registering servers include Linux-specific guidance, not just Windows.
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 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page is heavily focused on Windows and PowerShell. All examples and references are centered around Windows PowerShell DSC, SharePoint (a Windows-only product), and tools like ReverseDSC that operate in Windows environments. There is no mention of Linux equivalents, nor are there examples or guidance for Linux systems. Even though Azure Automation DSC supports Linux nodes, the documentation does not provide steps, examples, or resources for Linux users.
Recommendations
  • Add explicit examples and guidance for extracting configurations from Linux servers using Azure Automation State Configuration.
  • Reference and link to Linux DSC resources, such as nxDSC or other Linux-compatible DSC modules.
  • Include steps for generating MOF files from Linux systems, or clarify limitations if not supported.
  • Ensure that onboarding instructions for Linux machines are as detailed as those for Windows, including troubleshooting and best practices.
  • Balance references to PowerShell with mentions of cross-platform tools or alternatives where applicable.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows and PowerShell, with all examples and instructions assuming the use of Windows PowerShell 5.1. There are no Linux-specific examples or guidance, and Windows-centric tools and patterns (such as MOF generation, PowerShellGet, and dot sourcing) are referenced exclusively. Linux onboarding is only briefly mentioned in a link, with no substantive content or parity in the main text.
Recommendations
  • Add explicit examples and instructions for Linux environments, including how to use DSC and composite resources on Linux systems.
  • Clarify which steps or tools are cross-platform and which are Windows-specific; note any differences in usage or support for Linux.
  • Provide links to Linux DSC documentation and community resources, and include Linux-specific troubleshooting or best practices.
  • Where PowerShell is referenced, mention PowerShell Core (pwsh) and its cross-platform capabilities, and indicate any limitations or required adjustments for Linux.
  • Include sample configuration scripts and module usage for Linux, and describe how to register Linux servers for configuration management.
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 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 is heavily focused on Windows environments, exclusively listing Windows Server and Windows Client OS support for all extension versions. All examples, remarks, and references are centered around Windows Management Framework (WMF) and PowerShell DSC, with no mention of Linux support, Linux DSC equivalents, or cross-platform usage. Windows tools and patterns (such as PowerShell commands, WMF installation, and Windows-specific error logs) are referenced throughout, and Linux is only mentioned in the context of retirement, not as a supported platform.
Recommendations
  • Explicitly document the history and status of Linux support for the DSC extension, including when support was available and when it was retired.
  • Add a dedicated section summarizing Linux retirement, migration paths, and alternatives for Linux users.
  • Where possible, provide parity by including Linux-specific examples, troubleshooting steps, and references to Linux DSC resources (if any exist historically).
  • Clarify in the introduction and version tables that the extension is now Windows-only, and direct Linux users to relevant alternatives or documentation.
  • Remove or update links and references that imply cross-platform support if the extension is Windows-only, to avoid confusion.
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 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows and PowerShell workflows for compiling DSC configurations in Azure Automation. All code examples use Windows PowerShell, and Windows-specific modules and patterns are referenced throughout. There is no mention of Linux equivalents, nor are there any examples or guidance for Linux users. Windows tools and terminology are used exclusively, and the documentation assumes a Windows-centric environment.
Recommendations
  • Add examples and instructions for compiling DSC configurations from Linux environments, using cross-platform PowerShell Core or other supported tools.
  • Explicitly state Linux support status and alternatives, especially in light of the referenced Linux retirement announcement.
  • Provide parity in documentation by including Linux shell (bash) or PowerShell Core examples where applicable.
  • Mention any limitations or differences for Linux users up front, and link to relevant migration or support guidance.
  • If Linux support is deprecated, clarify migration paths and alternatives for Linux-based automation.
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 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page is heavily focused on Windows and PowerShell, with all examples and tooling references centered around Windows PowerShell DSC and the PowerSTIG project. There is no mention of Linux-specific configuration approaches, tools, or examples, and the prerequisites and next steps are exclusively Windows-oriented. Linux is only referenced in passing, with no substantive guidance or parity.
Recommendations
  • Add equivalent Linux configuration examples, such as using DSC for Linux or other configuration management tools (e.g., Ansible, Chef, Puppet) to apply STIG baselines.
  • Include references to Linux DSC resources and documentation, if available, or provide guidance on how Linux systems can be onboarded and managed in Azure Automation State Configuration.
  • Present both Windows and Linux approaches side-by-side, or clearly indicate platform-specific steps.
  • Mention Linux-compatible community projects or modules, if any, for STIG compliance.
  • Update prerequisites and next steps to include Linux-focused documentation and resources.
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 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 command-line examples use PowerShell and Az PowerShell modules, with no mention of Bash, Azure CLI, or Linux-native tooling. The prerequisites and setup steps exclusively reference PowerShell modules and commands, and there are no Linux-specific instructions or examples. The only nod to Linux is the retirement announcement for Automation DSC Linux, but the guidance and examples remain Windows-centric.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and commonly used on Linux.
  • Include instructions and examples for Linux users, such as how to authenticate and interact with Azure Automation and Monitor Logs using Bash or other Linux-native tools.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and offer alternatives where possible.
  • Explicitly state the current support status for Linux nodes and workflows, and link to migration or alternative guidance for Linux users.
  • Review and update prerequisites to mention cross-platform tools (e.g., Azure CLI) alongside PowerShell.
  • Consider including a table or section comparing Windows and Linux approaches for integration, if Linux support is still relevant for some users.
GitHub Create Pull Request
← Previous Page 6 of 40 Next →