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 1-25 of 982 flagged pages
Automation Set up Azure Automation continuous deployment with Chocolatey ...in/articles/automation/automation-dsc-cd-chocolatey.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically using PowerShell DSC and Chocolatey, with all examples, tooling, and walkthroughs tailored to Windows. Linux is only mentioned in passing (with a retirement announcement), and there are no equivalent instructions, examples, or tools provided for Linux/macOS users. The documentation assumes the reader is deploying to Windows VMs and using Windows-centric package management and configuration tools.
Recommendations
  • Add equivalent Linux/macOS continuous deployment examples using native tools (e.g., apt, yum, dnf, or Homebrew) and configuration management (e.g., Ansible, Chef, Puppet, or native Azure Automation alternatives).
  • Provide step-by-step instructions for setting up Azure Automation State Configuration for Linux nodes, if still supported, or link to alternatives.
  • Include Linux/macOS PowerShell Core examples where possible, or clarify platform limitations.
  • Mention and demonstrate cross-platform package managers and configuration resources.
  • Clearly state the Windows-only scope at the top if Linux is not supported, and provide links to Linux alternatives.
GitHub Create Pull Request
Automation Use the Azure Automation graphical runbook SDK (preview) ...blob/main/articles/automation/graphical-runbook-sdk.md
High Priority View Details →
Scanned: 2026-01-14 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 oriented toward Windows and PowerShell. All code examples and SDK usage are based on PowerShell concepts and Windows-specific DLLs. There is no mention of Linux or macOS compatibility, nor are there examples or guidance for non-Windows platforms. The SDK and runbook activities are described exclusively in terms of PowerShell and Windows workflows, with no alternatives or parity for Linux users.
Recommendations
  • Explicitly state platform compatibility for the SDK and graphical runbooks (Windows-only, or cross-platform).
  • Provide guidance or examples for Linux/macOS users, if supported (e.g., using PowerShell Core, .NET Core, or alternative scripting environments).
  • Mention any limitations or workarounds for non-Windows platforms.
  • If Linux/macOS are unsupported, clarify this early in the documentation.
  • If possible, add examples using PowerShell Core on Linux/macOS, or note how Linux users can interact with Azure Automation runbooks.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows and PowerShell. All examples use PowerShell cmdlets and Windows-specific DSC resources (e.g., WindowsFeature IIS). The prerequisites and walkthrough assume a Windows VM, with no Linux equivalent steps, examples, or discussion. Linux support is not covered, and Linux users are directed elsewhere for onboarding, but not for configuration or usage.
Recommendations
  • Add parallel Linux-focused sections or examples, including onboarding, configuration authoring, and assignment for Linux VMs.
  • Provide sample DSC configurations for Linux (e.g., using nxFile, nxPackage, or other Linux DSC resources).
  • Include Bash/CLI examples where possible, or reference cross-platform tools.
  • Clarify in the prerequisites and intro whether Linux is supported, and if not, provide clear links to Linux-specific documentation.
  • If Linux support is deprecated (as hinted by the retirement announcement), make this explicit at the top and guide users to alternatives.
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-14 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 exclusively uses PowerShell cmdlets and scripting for all troubleshooting scenarios, such as Connect-AzAccount, Get-AzVM, and Invoke-RestMethod. There are no examples or references for Bash, Azure CLI, or Linux-native tools. The troubleshooting steps and code samples are tailored to Windows/PowerShell environments, making it difficult for Linux/macOS users to follow or adapt the instructions. Windows tools and patterns are mentioned first and exclusively, with no Linux parity.
Recommendations
  • Provide equivalent troubleshooting steps using Azure CLI (az) commands and Bash scripts for each scenario.
  • Include examples for Linux/macOS environments, such as how to authenticate with managed identities using Azure CLI.
  • Add notes or sections clarifying how Linux users can adapt PowerShell-based instructions, or link to cross-platform alternatives.
  • Ensure screenshots and UI instructions are not Windows-centric, or provide Linux/macOS equivalents where relevant.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools (e.g., Az.Automation PowerShell module, cmdlets like Start-AzAutomationRunbook), with all examples and instructions provided in PowerShell syntax. There is no mention of Linux/macOS alternatives (such as Python runbooks, Bash, or cross-platform CLI usage), nor are any examples given for non-Windows environments. Windows/PowerShell patterns are presented exclusively and first, making it difficult for Linux/macOS users to follow or adapt the guidance.
Recommendations
  • Add equivalent examples for Python runbooks, which are supported in Azure Automation and are cross-platform.
  • Include guidance and examples for Bash or other scripting languages where applicable.
  • Reference and provide examples using Azure CLI for starting runbooks, which is cross-platform.
  • Explicitly state platform requirements and limitations for each method, and clarify which instructions are Windows/PowerShell-specific.
  • Reorder or balance examples so that Linux/macOS-friendly options are presented alongside or before Windows-specific ones.
GitHub Create Pull Request
Automation Compile DSC configurations in Azure Automation State Configuration ...lob/main/articles/automation/automation-dsc-compile.md
High Priority View Details →
Scanned: 2026-01-14 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 Windows and PowerShell workflows for compiling DSC configurations in Azure Automation. All code examples use Windows PowerShell, and references to Windows-specific modules and paths are prevalent. There are no Linux/macOS-specific examples or guidance, and the only mention of Linux is in a retirement announcement. The documentation assumes users are working in a Windows environment, which creates friction for Linux/macOS users.
Recommendations
  • Add explicit guidance for Linux/macOS users, including alternative workflows or tools for compiling DSC configurations.
  • Provide examples using cross-platform PowerShell Core (pwsh) and clarify compatibility.
  • Include notes or sections on how Linux users can interact with Azure Automation State Configuration, if supported.
  • If Linux support is deprecated, clearly state limitations and suggest migration paths or alternatives for Linux users.
  • Avoid Windows-specific file paths in examples; use generic or platform-neutral paths where possible.
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-14 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 tooling references centered on Windows PowerShell DSC and the PowerSTIG project, which is Windows-specific. There is no mention of Linux/macOS equivalents, nor are there examples or guidance for configuring STIG baselines on non-Windows platforms. The only reference to Linux is a link about onboarding Linux machines, but no substantive content or examples are provided for Linux users.
Recommendations
  • Add explicit guidance and examples for configuring STIG baselines on Linux using Azure Automation State Configuration.
  • Include references to Linux DSC resources or alternatives, such as cross-platform DSC implementations or Ansible/Chef for Linux.
  • Clarify platform support and limitations for PowerSTIG and DSC, and provide links to Linux/macOS documentation where relevant.
  • Present examples for both Windows and Linux side-by-side, or clearly indicate when a solution is Windows-only.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows PowerShell and PowerShell DSC, with all examples and instructions referencing Windows-specific tools and workflows. There are no Linux/macOS equivalents or examples, and the applicability note explicitly mentions Windows PowerShell 5.1. References to configuration management and DSC resources are all Windows-centric, with no mention of cross-platform alternatives or Linux-specific guidance.
Recommendations
  • Add explicit instructions and examples for Linux/macOS environments, including how to use cross-platform PowerShell (pwsh) and any differences in DSC usage.
  • Clarify whether Datum and Azure Automation State Configuration support Linux nodes, and provide guidance for onboarding and managing Linux machines.
  • Include links to Linux/macOS documentation and resources where relevant.
  • Present examples for both Windows and Linux side-by-side, or indicate platform-specific steps clearly.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation is exclusively focused on Windows environments and tools, specifically Windows Server versions, Windows Management Framework (WMF), and PowerShell DSC. There is no mention of Linux or macOS support, examples, or equivalents, except for a brief retirement announcement for Linux DSC. All instructions, features, and troubleshooting steps are Windows-specific, and PowerShell is referenced throughout as the primary tool. This creates a strong Windows bias and leaves Linux/macOS users without guidance or parity.
Recommendations
  • Clearly state the current support status for Linux/macOS DSC extension, including any alternatives or migration paths.
  • If Linux support is retired, provide links to relevant documentation for configuration management on Linux VMs in Azure (e.g., using Ansible, Chef, Puppet, or Azure VM Custom Script Extension).
  • Add a historical section outlining previous Linux support and guidance for users affected by the retirement.
  • Ensure that future documentation includes cross-platform notes or alternatives where applicable, and does not assume Windows-only usage.
  • If any features or troubleshooting steps apply to Linux, include explicit Linux/macOS examples and instructions.
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-14 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 biased towards Windows environments. All configuration examples use Windows PowerShell DSC syntax and resources (e.g., WindowsFeature), and the only sample VM creation link is for Windows. There are no Linux-specific examples, resources, or guidance, and references to DSC are consistently tied to Windows PowerShell. The documentation does not demonstrate how to use Azure Automation State Configuration with Linux nodes, nor does it provide Linux DSC resource examples or onboarding steps.
Recommendations
  • Add Linux-specific examples, including sample DSC configurations using cross-platform resources or Linux-specific resources.
  • Include links and instructions for creating Linux VMs in Azure, not just Windows VMs.
  • Provide onboarding steps and screenshots for enabling Linux VMs for management with State Configuration.
  • Clarify which features and resources are supported on Linux, and provide parity in documentation structure for Linux users.
  • Reference cross-platform DSC (such as DSC Core or PSDesiredStateConfiguration for PowerShell 7+) where appropriate.
GitHub Create Pull Request
Automation Author graphical runbooks in Azure Automation ...les/automation/automation-graphical-authoring-intro.md
High Priority View Details →
Scanned: 2026-01-14 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 Windows PowerShell, with all examples, scripting, and workflow logic based on PowerShell syntax and cmdlets. There is no mention of Linux or cross-platform alternatives, nor are Bash, Python, or other scripting languages referenced. Windows-centric tools and terminology (PowerShell, System Center Orchestrator, Service Management Automation) are used exclusively, and Linux/macOS users are not provided with equivalent examples or guidance.
Recommendations
  • Clarify that Azure Automation graphical runbooks are PowerShell-based and may not support Bash or Python natively, but note any cross-platform capabilities if available.
  • Add explicit statements about platform requirements and limitations, including whether Linux/macOS users can author or run graphical runbooks.
  • Provide guidance or links for Linux/macOS users on how to interact with Azure Automation (e.g., via Azure CLI, Bash, or Python runbooks if supported).
  • Include examples or documentation for non-Windows environments, or clearly state that graphical runbooks are Windows/PowerShell-only.
  • Mention any future plans or alternatives for Linux/macOS parity if graphical runbooks are not cross-platform.
GitHub Create Pull Request
Automation Compose DSC configurations ...omation/compose-configurationwithcompositeresources.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. It references PowerShell DSC concepts and cmdlets exclusively, with no mention of Linux equivalents or examples. The composite resources highlighted (e.g., PSExecutionPolicy, RenameAndDomainJoin) are Windows-centric, and the only example of continuous deployment uses Chocolatey, a Windows package manager. There are no Linux/macOS-specific instructions, examples, or tools mentioned, and the retirement announcement for Linux DSC is included, further reducing Linux relevance.
Recommendations
  • Add examples or references for Linux/macOS DSC workflows, if still supported.
  • Include Linux-specific composite resources or clarify their absence.
  • Provide parity in tooling references (e.g., mention Ansible, Chef, or native Linux DSC if applicable).
  • If Linux DSC is deprecated, clearly state alternatives for Linux users.
  • Balance example selection to include cross-platform scenarios, not just Windows-centric ones.
GitHub Create Pull Request
Automation Manage Office 365 services using Azure Automation ...ocs/blob/main/articles/automation/manage-office-365.md
High Priority View Details →
Scanned: 2026-01-14 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 using Windows PowerShell and related modules. There is an explicit note that the Microsoft Graph PowerShell module cmdlets must be run from Windows PowerShell, and no Linux/macOS alternatives or cross-platform guidance is provided. All scripting and automation instructions are PowerShell-centric, and there is no mention of Bash, Azure CLI, or other non-Windows tools.
Recommendations
  • Provide equivalent examples using PowerShell Core (pwsh) and clarify which cmdlets are cross-platform.
  • Include instructions or alternatives for Linux/macOS users, such as using Azure CLI, REST API, or cross-platform scripting.
  • Clearly state platform limitations for each tool/module and suggest workarounds or alternatives.
  • Add a section addressing Linux/macOS automation scenarios, including how to manage Office 365 services from those platforms.
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-14 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 exhibits a Windows bias by focusing on PowerShell-based DSC workflows, referencing Windows-centric tools and patterns, and providing examples in PowerShell syntax. Although the example configures a LAMP stack (Linux), the process relies on Azure Automation DSC, which is retired for Linux, and does not provide alternative Linux-native solutions or examples. The documentation also references Chocolatey (a Windows package manager) in the next steps, further emphasizing Windows tooling.
Recommendations
  • Clearly state the limitations and alternatives for Linux users, especially since Azure Automation DSC for Linux is retired.
  • Provide Linux-native configuration management alternatives (e.g., Ansible, Chef, Puppet) and link to relevant Azure documentation.
  • Offer example workflows for Linux VMs using supported Azure features (e.g., Azure Policy Guest Configuration) with step-by-step instructions.
  • Avoid referencing Windows-specific tools (like Chocolatey) as the primary next step for cross-platform documentation.
  • Include Bash or shell script examples where appropriate, and clarify which steps are Windows-only.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All configuration examples use PowerShell DSC syntax and the WindowsFeature resource, with no Linux equivalents or cross-platform DSC examples. The only VM creation link is for Windows VMs, and references to DSC documentation and resources are all Windows-centric. There are no Linux-specific instructions, examples, or references, and the documentation does not demonstrate how to manage Linux nodes or author Linux-compatible configurations.
Recommendations
  • Include examples of authoring DSC configurations for Linux nodes, using cross-platform resources (e.g., nxFile, nxPackage).
  • Provide links to both Windows and Linux VM creation guides.
  • Reference cross-platform DSC documentation and clarify which features are Windows-only.
  • Add explicit instructions or notes for managing Linux nodes, including any limitations or retirement status.
  • If Linux support is deprecated, clearly state this at the top and provide migration guidance.
GitHub Create Pull Request
Automation Author graphical runbooks in Azure Automation ...les/automation/automation-graphical-authoring-intro.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows PowerShell workflows and cmdlets, with all examples and instructions using PowerShell syntax and concepts. There is no mention of Linux or macOS equivalents, nor any Bash, Python, or cross-platform scripting options. Windows-centric tools and terminology (e.g., PowerShell, System Center Orchestrator) are used exclusively and introduced first, with no Linux alternatives or parity discussed.
Recommendations
  • Clarify that Azure Automation graphical runbooks are PowerShell-based and note platform limitations up front.
  • Explicitly state that graphical runbooks do not support Bash, Python, or Linux-native scripting.
  • Provide guidance or links for Linux/macOS users on how to use textual runbooks with Bash or Python in Azure Automation.
  • Add a comparison table or section outlining which runbook types are suitable for Linux/macOS users.
  • Mention cross-platform PowerShell (PowerShell Core) where applicable, and clarify compatibility.
  • If possible, include examples or references for Linux/macOS users on how to author automation using supported languages.
GitHub Create Pull Request
Automation Use the Azure Automation graphical runbook SDK (preview) ...blob/main/articles/automation/graphical-runbook-sdk.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows and PowerShell, with all examples and SDK references assuming PowerShell-centric workflows. There is no mention of Linux or cross-platform alternatives, and the SDK appears to be designed for PowerShell/Windows environments. No Linux/macOS usage patterns, tools, or examples are provided.
Recommendations
  • Clarify platform requirements and whether the SDK can be used on Linux/macOS (e.g., via .NET Core/Mono).
  • Provide explicit instructions or examples for Linux/macOS users, including installation steps and code samples.
  • Mention any limitations or workarounds for non-Windows platforms.
  • If the SDK is Windows-only, state this clearly at the top of the documentation.
  • If possible, expand SDK support to cross-platform .NET and document accordingly.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows and PowerShell workflows for compiling DSC configurations in Azure Automation. All code examples use Windows PowerShell, and Windows-specific tools and paths (e.g., C:\, WindowsFeature) are referenced throughout. There are no Linux or cross-platform examples, and Linux-specific workflows are not discussed. The documentation mentions the retirement of Linux support, but does not provide guidance for Linux users or alternatives.
Recommendations
  • Clearly state the current support status for Linux/macOS, including any retirement or migration paths.
  • If any Linux workflows remain supported, add equivalent Linux examples (e.g., using Azure CLI, Bash, or cross-platform PowerShell Core).
  • Where possible, use platform-neutral terminology and examples, or explicitly note platform-specific steps.
  • Provide guidance for users migrating from Linux DSC to supported alternatives.
  • If Linux is no longer supported, make this explicit at the top of the documentation and link to migration resources.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows PowerShell 5.1, with all examples and instructions assuming a Windows environment. There is no mention of Linux/macOS equivalents, nor any examples or guidance for non-Windows platforms. The use of Windows-specific terminology and tools (PowerShell, MOF files, DSC) is pervasive, and Linux is only referenced in a link about onboarding, not in the main workflow or examples.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, including how to use DSC with cross-platform PowerShell.
  • Clarify which steps are Windows-only and provide alternatives or workarounds for Linux/macOS environments.
  • Include references to Linux-compatible DSC resources and modules, and document any platform-specific limitations.
  • Present examples for both Windows and Linux platforms side-by-side, or clearly indicate platform applicability for each step.
GitHub Create Pull Request
Automation Set up Azure Automation continuous deployment with Chocolatey ...in/articles/automation/automation-dsc-cd-chocolatey.md
High Priority View Details →
Scanned: 2026-01-13 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, specifically using PowerShell DSC and Chocolatey, with all examples and instructions tailored to Windows VMs. Linux is mentioned only in passing, and there are no equivalent examples or guidance for Linux systems, package managers, or automation tools. The retirement of Linux DSC is noted, but no alternative Linux workflow is provided.
Recommendations
  • Add a section explaining how to achieve similar continuous deployment workflows on Linux VMs, possibly using native Linux configuration management tools (e.g., Ansible, Chef, Puppet) and package managers (e.g., apt, yum).
  • Provide parallel examples for Linux, including Resource Manager template modifications, onboarding, and package installation steps.
  • Clarify the current support status for Linux in Azure Automation State Configuration and suggest alternatives for Linux users.
  • Reference Linux-compatible VM extensions and automation modules where appropriate.
  • If Linux DSC is deprecated, link to migration guides or recommended replacement solutions for Linux 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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows PowerShell and PowerSTIG, a Windows-centric tool. All examples and references are for Windows PowerShell DSC, with no Linux/macOS equivalents or guidance. Linux is only mentioned in passing, with no actionable instructions or parity for Linux users.
Recommendations
  • Include examples and instructions for configuring STIG compliance on Linux systems using Azure Automation State Configuration.
  • Reference Linux DSC resources and modules, if available, or provide alternative approaches for Linux users.
  • Clarify which features are Windows-only and suggest Linux-compatible tools or workflows.
  • Add a section comparing Windows and Linux support for STIG automation in Azure Automation.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exclusively covers Windows operating systems and Windows-specific tools (PowerShell, WMF, Nano Server) in all version histories and examples. There is no mention of Linux support, Linux equivalents, or cross-platform usage. All instructions, remarks, and troubleshooting steps are focused on Windows environments, with PowerShell and WMF as the only configuration mechanisms discussed. Even the 'Next steps' section only references PowerShell DSC resources.
Recommendations
  • Clearly state the current status of Linux support for the Azure DSC extension, including any retirement or deprecation (the retirement announcement is included, but not explained in detail).
  • If Linux support is retired, provide links to alternative solutions for Linux VM configuration management in Azure (e.g., Azure Automation State Configuration alternatives, Chef, Ansible, or native cloud-init).
  • Add historical context or a summary table indicating which extension versions (if any) supported Linux, and when support ended.
  • Where possible, include examples or references for configuration management on Linux VMs in Azure, or direct users to relevant documentation.
  • If the extension is now Windows-only, make this explicit at the top of the page and remove ambiguity for cross-platform users.
GitHub Create Pull Request
Automation Deploy an Amazon Web Services VM with an Azure Automation runbook ...icles/automation/automation-scenario-aws-deployment.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell and PowerShell ISE for all examples and instructions, with no mention of Linux/macOS alternatives such as AWS CLI, Python, or Bash. All tooling and scripting guidance is Windows-centric, and steps assume familiarity with Windows environments. There are no examples or instructions for Linux or macOS users, nor any mention of how to adapt the process for those platforms.
Recommendations
  • Add equivalent instructions and examples using AWS CLI and/or Python scripts, which are cross-platform and commonly used on Linux/macOS.
  • Include guidance for installing and using the AWS CLI module in Azure Automation, and provide sample runbooks using Bash or Python.
  • Mention how Linux/macOS users can author and test runbooks locally, including any platform-specific considerations.
  • Clarify whether Azure Automation supports Python or Bash runbooks for AWS provisioning, and link to relevant documentation.
  • Reorder examples so that cross-platform tools (AWS CLI, Python) are presented before or alongside PowerShell.
GitHub Create Pull Request
Automation Compose DSC configurations ...omation/compose-configurationwithcompositeresources.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. It exclusively references PowerShell DSC concepts, cmdlets, and types (e.g., [PSCredential]), and all examples and screenshots are based on Windows-centric workflows. There is no mention of Linux/macOS equivalents, nor are there examples or guidance for non-Windows platforms. The 'Next steps' section further reinforces this bias by linking to PowerShell and Chocolatey (a Windows package manager) resources, with no Linux alternatives provided.
Recommendations
  • Add explicit guidance or examples for Linux/macOS users, including how composite resources and configurations are managed on those platforms.
  • Clarify whether the features described are Windows-only, especially given the referenced Linux retirement announcement.
  • If Linux support is deprecated, provide clear migration paths or alternatives for Linux users.
  • Include cross-platform notes or highlight differences in workflows, tools, and supported features between Windows and Linux/macOS.
  • Reference Linux DSC resources or modules if still relevant, or direct users to supported configuration management solutions for Linux.
GitHub Create Pull Request
Automation Manage Office 365 services using Azure Automation ...ocs/blob/main/articles/automation/manage-office-365.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows and PowerShell, with all examples and instructions using Windows PowerShell and related cmdlets. There is an explicit note that the Microsoft Graph PowerShell module cmdlets must be run from Windows PowerShell, and no Linux/macOS alternatives or cross-platform guidance are provided. The use of Send-MailMessage and other Windows-centric tools further reinforces the bias.
Recommendations
  • Provide equivalent examples using PowerShell Core (pwsh) and clarify which features are available cross-platform.
  • Explicitly state platform limitations and offer workarounds or alternatives for Linux/macOS users.
  • Include bash/CLI or REST API examples for key tasks, where possible.
  • Document any Azure Automation features that work on Linux/macOS, or clarify if only Windows is supported.
  • Mention and link to cross-platform modules or tools if available.
GitHub Create Pull Request
← Previous Page 1 of 40 Next →