Automation

232
Total Pages
137
Linux-Friendly Pages
95
Pages with Bias
40.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

365 issues found
Showing 1-25 of 365 flagged pages
Automation Get started with Azure Automation State Configuration .../articles/automation/automation-dsc-getting-started.md
High Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. All configuration examples use Windows PowerShell DSC syntax and resources (e.g., WindowsFeature IIS), with no Linux equivalents or cross-platform examples. The only VM creation link is for Windows, and references to DSC documentation and resources are Windows-centric. Linux support is only mentioned in passing, and there are no Linux-specific instructions, examples, or resource references.
Recommendations
  • Add Linux DSC configuration examples, such as managing Linux packages or services using cross-platform DSC resources.
  • Include links to Linux VM creation guides alongside Windows VM creation instructions.
  • Reference Linux-specific DSC documentation and resources where applicable.
  • Clarify current support status for Linux DSC, especially given the retirement announcement, and provide migration or alternative guidance for Linux users.
  • Present examples for both Windows and Linux side-by-side, or indicate platform-specific steps clearly.
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-13 06:17
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 and patterns. All examples use PowerShell syntax and cmdlets, with explicit references to Windows PowerShell and the Az.Automation module. There are no examples or guidance for Linux/macOS users, such as using Python runbooks or Bash scripts, nor is there mention of cross-platform alternatives. Windows tools and terminology are used exclusively and presented first, making it difficult for non-Windows users to follow or adapt the instructions.
Recommendations
  • Add examples for Python and/or Bash runbooks, which are supported in Azure Automation and commonly used on Linux/macOS.
  • Clarify which features and cmdlets are cross-platform and which are Windows-only.
  • Provide equivalent instructions and code samples for Linux/macOS environments, including authentication and context management.
  • Explicitly state platform limitations and offer links to platform-specific documentation where appropriate.
  • Reorder examples or provide parallel examples so that Windows and Linux/macOS users are equally supported.
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 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows and PowerShell, with all code examples and tooling references using Windows PowerShell and Windows-centric paths. There are no Linux/macOS-specific examples, nor any mention of cross-platform alternatives for compiling DSC configurations. Windows tools and patterns are presented exclusively and before any mention of Linux, and the only compilation methods described are via the Azure portal or Windows PowerShell.
Recommendations
  • Add explicit notes about Linux/macOS support status for DSC compilation in Azure Automation.
  • If Linux/macOS compilation is supported, provide equivalent examples using cross-platform PowerShell Core (pwsh) and clarify any differences.
  • Include sample paths and commands for Linux/macOS environments where applicable.
  • Mention any limitations or retirement of Linux DSC support more prominently and link to migration guidance.
  • If Windows-only is intentional due to platform support, clarify this at the top of the article to set expectations for non-Windows users.
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 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation exclusively covers Windows operating systems, PowerShell, and Windows Management Framework (WMF) in all examples and version histories. There is no mention of Linux or macOS support, nor are there examples or instructions for non-Windows platforms. The only reference to Linux is an end-of-life/retirement announcement, further reinforcing the Windows-centric focus.
Recommendations
  • Clearly state the current support status for Linux/macOS, including any retirement or alternative solutions.
  • If Linux support is deprecated, provide links or guidance for users migrating from Linux DSC to supported alternatives (e.g., Azure Automation, Ansible, Chef, etc.).
  • If any versions previously supported Linux, include those in the version history and document their features and limitations.
  • Add a section comparing Windows and Linux DSC extension capabilities, even if only for historical context.
  • Provide migration guides or FAQs for Linux users affected by the retirement.
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 06:17
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, with all examples, configuration scripts, and tooling (Chocolatey, PowerShell DSC, WindowsFeature, xNetworking, etc.) being Windows-specific. There is no guidance or example for Linux or macOS users, and Linux support is explicitly deprecated. The workflow, commands, and package management are all tailored to Windows, making it difficult or impossible for Linux users to follow or adapt the instructions.
Recommendations
  • Clearly state at the beginning that the guide is Windows-only and Linux support is deprecated.
  • Provide links to equivalent Linux workflows (e.g., using apt, yum, or native Azure Automation alternatives for Linux) if available.
  • If Azure Automation State Configuration for Linux is retired, suggest alternative Azure solutions for Linux configuration management (such as Azure VM extensions for custom scripts, or third-party tools like Ansible, Chef, or Puppet).
  • Add a section comparing Windows and Linux approaches to continuous deployment in Azure, highlighting current limitations and alternatives.
  • Remove or update references that imply cross-platform support where it no longer exists.
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-13 06:17
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. It only references Windows PowerShell 5.1, PowerShell DSC, and Windows-specific tools like SharePointDSC and ReverseDSC, with no Linux/macOS equivalents or examples. Linux is mentioned only in a link, with no guidance or parity for non-Windows users.
Recommendations
  • Add explicit guidance or examples for Linux/macOS users, such as using DSC for Linux or alternative configuration management tools.
  • Clarify whether ReverseDSC or similar extraction tools exist for Linux environments, or state the limitation clearly.
  • Provide Linux/macOS command-line examples where possible, or reference cross-platform DSC solutions.
  • Reorganize the content to mention cross-platform or Linux support (if any) earlier, not just in a link.
  • If the solution is Windows-only, add a clear note at the top to set expectations for Linux/macOS users.
GitHub Create Pull Request
Automation Compose DSC configurations ...omation/compose-configurationwithcompositeresources.md
High Priority View Details →
Scanned: 2026-01-13 06:17
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 (such as [PSCredential]), and all examples and terminology are Windows-centric. There are no Linux/macOS configuration examples, nor are Linux equivalents or patterns mentioned. The only Linux-specific content is a retirement announcement, indicating reduced or discontinued support for Linux DSC in Azure Automation.
Recommendations
  • Add explicit notes clarifying the current support status for Linux/macOS DSC in Azure Automation, including alternatives if available.
  • Provide examples or guidance for Linux/macOS users, such as how to manage configurations outside of Azure Automation or using cross-platform DSC tools.
  • If Linux support is deprecated, offer migration paths or recommend other configuration management solutions for Linux/macOS users.
  • Avoid using Windows-specific terminology (e.g., [PSCredential]) without explanation or cross-platform alternatives.
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 06:17
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 Windows-centric tools (PowerShell Gallery, PowerShell ISE) for all examples and instructions. There are no references to Linux/macOS alternatives (e.g., Bash, AWS CLI in shell, CloudShell), nor are cross-platform scripting options discussed. The workflow assumes familiarity with Windows environments and does not provide guidance for users on Linux or macOS platforms.
Recommendations
  • Add equivalent instructions using AWS CLI and Bash for Linux/macOS users.
  • Mention and provide examples for using Azure Automation Python runbooks, which are cross-platform.
  • Include steps for installing and using the AWS CLI on Linux/macOS, and show how to authenticate and provision VMs via shell scripts.
  • Clarify that PowerShell Core is available on Linux/macOS and provide instructions for those platforms if PowerShell is required.
  • Avoid referencing Windows-only tools (e.g., PowerShell ISE) without alternatives; suggest VS Code or other cross-platform editors.
  • Present examples for both Windows and Linux/macOS users side-by-side, or at least note platform differences.
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 06:17
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 workflows. All examples and SDK usage revolve around PowerShell commands and concepts, with no mention of Linux or cross-platform alternatives. The SDK itself appears to be designed for Windows environments, and there are no instructions, examples, or guidance for Linux/macOS users.
Recommendations
  • Clarify platform support for the SDK (is it Windows-only, or can it be used on Linux/macOS with .NET Core?).
  • If cross-platform usage is possible, provide Linux/macOS installation and usage instructions.
  • Include examples using bash or other Linux-native scripting tools if supported.
  • Explicitly state any platform limitations and suggest alternatives for Linux/macOS users.
  • If the SDK is Windows-only, recommend equivalent automation approaches for Linux users (e.g., Python SDKs, Azure CLI, etc.).
GitHub Create Pull Request
Automation Manage runbooks in Azure Automation ...-docs/blob/main/articles/automation/manage-runbooks.md
High Priority View Details →
Scanned: 2026-01-13 06:17
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 biased toward PowerShell and Windows-centric tooling. All code examples use PowerShell cmdlets, with file paths and script references in Windows format (e.g., C:\Runbooks\Sample_TestRunbook.ps1). There is no mention of Bash, CLI, or Linux/macOS-specific workflows, nor are there examples using cross-platform tools like Azure CLI. Windows/PowerShell methods are presented exclusively and often first, with no Linux alternatives or parity.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets, especially for creating, importing, publishing, and retrieving runbooks.
  • Include Linux/macOS file path examples and clarify cross-platform compatibility for scripts.
  • Explicitly state which features/tools are cross-platform and which are Windows-only.
  • Provide guidance for authoring and managing runbooks from Linux/macOS environments.
  • Mention and demonstrate Python runbooks and their management using non-Windows tools.
  • Add troubleshooting and best practices sections relevant to Linux/macOS users.
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 06:17
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 cmdlets and modules. There is an explicit note that the Microsoft Graph PowerShell module must be run from Windows PowerShell, and no Linux/macOS alternatives or cross-platform guidance are provided. The workflow assumes familiarity with Windows-centric tools and patterns, and does not mention Bash, cross-platform PowerShell Core, or CLI alternatives.
Recommendations
  • Provide guidance and examples for Linux/macOS users, including any available cross-platform alternatives (e.g., PowerShell Core, Azure CLI, Microsoft Graph CLI, REST API).
  • Clarify which steps are Windows-only and suggest workarounds or alternatives for non-Windows platforms.
  • If the Microsoft Graph PowerShell module is truly Windows-only, explicitly state this limitation at the top and link to cross-platform options.
  • Include example scripts and runbook instructions for Bash, PowerShell Core, or other supported shells where possible.
  • Reorder examples so that platform-neutral or cross-platform approaches are presented first, or at least in parallel with Windows-specific instructions.
GitHub Create Pull Request
Automation Azure Quickstart - Install Hybrid Worker extension on Azure portal. ...omation/quickstarts/install-hybrid-worker-extension.md
High Priority View Details →
Scanned: 2026-01-13 06:17
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 for Windows Azure Virtual Machines. All step-by-step instructions, screenshots, and extension selection refer only to 'Azure Automation Windows Hybrid Worker', with no mention or examples for Linux VMs. Prerequisites and installation steps are Windows-specific, and there is no guidance for Linux users, despite the initial claim that both Windows and Linux VMs are supported.
Recommendations
  • Add explicit instructions and screenshots for installing the Hybrid Worker extension on Linux Azure Virtual Machines.
  • Include Linux-specific extension names and configuration steps, if they differ from Windows.
  • Update the prerequisites section to mention both Windows and Linux VM requirements.
  • Present Windows and Linux instructions in parallel or clearly separate sections to ensure parity.
  • Clarify any differences in extension capabilities or limitations between Windows and Linux.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented towards Windows and PowerShell, with most instructions and examples assuming a Windows environment. Although there is a brief mention of configuring a LAMP stack (Linux), the tooling, terminology, and examples are all PowerShell-centric. The documentation also notes that Azure Automation DSC for Linux has retired, and does not provide alternative Linux/macOS guidance or parity for configuration management. Windows tools and patterns (PowerShell Gallery, MOF compilation, etc.) are referenced exclusively, with no Linux-native equivalents or alternatives.
Recommendations
  • Clearly state the limitations and alternatives for Linux/macOS users, including supported configuration management options (e.g., Azure Policy Guest Configuration, Ansible, Chef, etc.).
  • Provide links or guidance for Linux/macOS users to migrate from DSC to supported solutions.
  • Offer example workflows or scripts for Linux/macOS environments using supported tools.
  • Reorder or clarify sections to make it clear that the quickstart is Windows-only, and direct Linux/macOS users to relevant documentation.
  • Remove or update references to Chocolatey and other Windows-specific tools in 'Next steps' for Linux/macOS parity.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation State Configuration issues ...automation/troubleshoot/desired-state-configuration.md
High Priority View Details →
Scanned: 2026-01-13 06:17
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, with most troubleshooting steps, examples, and cmdlets focused on Windows environments. PowerShell DSC and related modules are referenced throughout, and Windows-specific tools (such as w32tm and PowerShell certificate management) are used exclusively in examples. Linux troubleshooting is only mentioned in a single scenario, with minimal detail and no parity in examples or step-by-step guidance.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples for each scenario, especially for log collection, agent registration, and certificate management.
  • Include Bash or shell command equivalents alongside PowerShell commands where applicable.
  • Reference Linux DSC extension documentation and tools (such as OMI, omiserver logs, or systemd journal) in relevant sections.
  • Ensure that Linux onboarding and error resolution steps are given equal prominence and detail as Windows steps.
  • Add guidance for managing certificates and DSC configuration files on Linux nodes.
  • Where PowerShell cmdlets are referenced, clarify if/how they apply to Linux, or provide alternatives.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows environments, with all examples and instructions using Windows PowerShell cmdlets and focusing on Windows Server VMs. There are no Linux/macOS examples, and the prerequisites and configuration steps are exclusively Windows-centric. References to Linux support are limited to retirement announcements, with no guidance for Linux users.
Recommendations
  • Add explicit Linux/macOS onboarding and configuration examples, including Bash/CLI equivalents.
  • Provide sample DSC configurations for Linux targets (e.g., installing Apache instead of IIS).
  • Clarify current support status for Linux and offer migration or alternative guidance for Linux users.
  • List Linux prerequisites and link to Linux VM creation guides alongside Windows instructions.
  • Include cross-platform notes or tables summarizing differences and supported features.
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-12 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, with all examples and references tailored to Windows environments. There is no mention of Linux/macOS equivalents, and critical concepts (DSC, PowerSTIG) are presented as Windows-only solutions. Linux is referenced only in passing, with no guidance or examples for Linux users.
Recommendations
  • Include equivalent Linux/macOS configuration management tools (e.g., Ansible, Chef, Puppet) and how they can be used to implement STIG baselines.
  • Provide examples or links for configuring STIG compliance on Linux systems within Azure Automation.
  • Clarify the scope of PowerSTIG and DSC, and explicitly state limitations for non-Windows platforms.
  • Add a section comparing Windows and Linux approaches to STIG automation in Azure.
  • Reference onboarding guides or documentation for Linux nodes with Azure Automation State Configuration.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows and PowerShell, with all code examples and tooling instructions using Windows PowerShell and Windows-centric paths. There are no Linux/macOS-specific examples, nor any mention of cross-platform alternatives for compiling DSC configurations. Windows tools and patterns are presented exclusively and before any mention of platform-neutral or Linux options. The only nod to Linux is the retirement announcement, with no guidance for Linux users.
Recommendations
  • Add explicit guidance for Linux/macOS users, including whether DSC compilation is supported on those platforms and, if so, how to perform it.
  • Provide Bash or cross-platform PowerShell Core examples where possible.
  • Clarify any platform limitations or alternatives for Linux users, especially in sections about compiling and importing configurations.
  • Include notes or links to Linux-compatible DSC tooling if available.
  • Reorder sections to present platform-neutral options first, or clearly indicate platform-specific instructions.
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-12 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, with all version history, features, and instructions referencing only Windows Server and Windows Client OSs. PowerShell and Windows Management Framework (WMF) are mentioned exclusively, with no Linux or macOS equivalents or examples provided. There is no guidance for Linux users, and the only mention of Linux is a retirement announcement, implying that Linux support is deprecated or removed.
Recommendations
  • Clearly state the current support status for Linux/macOS, including any alternatives or migration paths for users on those platforms.
  • If Linux support is retired, provide links to legacy documentation or community-supported solutions for Linux DSC management.
  • Add a section comparing Windows DSC extension capabilities to those previously available for Linux, and suggest cross-platform configuration management alternatives (e.g., Ansible, Chef, Puppet) for Linux users.
  • Ensure that any remaining Linux-relevant information is easy to find, and that Windows-specific instructions are clearly marked as such.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily Windows-centric, focusing exclusively on Windows VMs, PowerShell DSC, and Chocolatey (a Windows package manager). All examples, configuration scripts, and tooling references are for Windows environments and PowerShell. Linux is only mentioned in passing, with no equivalent examples, instructions, or tooling for Linux/macOS users. The retirement of Linux DSC is noted, but no alternatives or migration guidance are provided.
Recommendations
  • Add a section explicitly addressing Linux/macOS users, including current alternatives for configuration management and package deployment (e.g., Ansible, Chef, Puppet, native Azure VM extensions for Linux).
  • Provide parallel examples for Linux VMs, such as using apt/yum and cloud-init or other Azure-supported Linux configuration mechanisms.
  • Clarify the impact of Azure Automation DSC Linux retirement and offer migration paths or links to relevant documentation for Linux users.
  • Where possible, use cross-platform scripting (e.g., Azure CLI, ARM templates) in examples, or provide both PowerShell and Bash/CLI equivalents.
  • Reorder introductory sections to mention Linux tools and patterns alongside Windows, rather than only as a comparison point.
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-12 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 no Linux/macOS examples or equivalent tools mentioned. All instructions and references are centered around Windows PowerShell DSC, and the only explicitly supported platform is Windows PowerShell 5.1. Linux is mentioned only in passing, with no guidance for Linux users on how to perform the same tasks.
Recommendations
  • Add explicit instructions and examples for Linux/macOS environments, including how to generate configurations from Linux servers.
  • Mention and link to Linux-compatible DSC resources or alternatives, such as cross-platform DSC implementations.
  • Clarify platform support for ReverseDSC and related tools, and provide parity in documentation for non-Windows users.
  • Include Linux-specific onboarding and configuration steps, not just references to Windows PowerShell.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a notable Windows bias. All configuration examples use Windows PowerShell DSC syntax and resources (e.g., WindowsFeature), with no Linux equivalent shown. The only VM creation link is for Windows, and references to DSC documentation and resources are Windows-centric. There is no demonstration of managing Linux nodes, nor are Linux-specific resources or onboarding steps included. Windows terminology and tools (PowerShell, WindowsFeature) are used exclusively throughout the guide.
Recommendations
  • Add parallel examples for Linux nodes, including configuration samples using cross-platform DSC resources or Linux-specific resources.
  • Include links and instructions for creating Linux VMs in Azure alongside Windows VM instructions.
  • Reference Linux DSC documentation and resources where appropriate.
  • Clarify which steps and resources are Windows-only and provide guidance for Linux users where features differ or are deprecated.
  • If Linux support is deprecated, make this clear at the start and provide migration or alternative guidance for Linux users.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows and PowerShell, referencing Windows PowerShell, PowerShell Workflow, and Windows-specific SDKs and DLLs. All code examples and activities are based on PowerShell commands and scripts, with no mention of Linux/macOS equivalents or cross-platform compatibility. There are no examples or guidance for Linux users, nor any discussion of how (or if) the SDK or graphical runbooks can be authored or executed on non-Windows platforms.
Recommendations
  • Clarify whether the SDK and graphical runbooks are supported on Linux/macOS, and document any platform limitations.
  • Provide Linux/macOS-specific instructions or note if the SDK can be used with .NET Core/Mono on those platforms.
  • Include examples using Bash or other cross-platform scripting languages if supported, or explicitly state PowerShell Core compatibility.
  • Mention any required dependencies or installation steps for Linux/macOS users.
  • Reorder or balance examples so that Linux/macOS users are not implicitly deprioritized.
GitHub Create Pull Request
Automation Track updated files with an Azure Automation watcher task ...s/automation/automation-scenario-using-watcher-task.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows environments, with all examples and instructions using PowerShell and Windows-style file paths. There are no Linux/macOS equivalents or alternative instructions, and the only tooling mentioned is PowerShell, which is native to Windows. The folder path examples and commands assume a Windows filesystem, and the process for testing the watcher task is described only for Windows users.
Recommendations
  • Provide equivalent examples for Linux/macOS environments, such as using Bash or Python scripts for file creation and monitoring.
  • Clarify whether the Hybrid Runbook Worker supports Linux hosts and, if so, include instructions for setting up watcher tasks on Linux.
  • Show Linux-style file paths (e.g., /home/examplefiles) alongside Windows paths.
  • Include commands for creating test files on Linux/macOS (e.g., 'touch ExampleFile1.txt').
  • Mention cross-platform PowerShell (pwsh) if supported, and clarify any platform limitations.
  • Explicitly state any platform restrictions for watcher tasks and runbooks.
GitHub Create Pull Request
Automation Compose DSC configurations ...omation/compose-configurationwithcompositeresources.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily oriented around PowerShell DSC concepts and tools, which are primarily Windows-centric. Examples and terminology (e.g., PSCredential, PowerShell cmdlets, Chocolatey) are Windows-focused, with no Linux/macOS equivalents or examples provided. The page references the retirement of Linux DSC support, but does not offer alternative guidance for Linux users or clarify cross-platform limitations.
Recommendations
  • Clearly state the current platform support and limitations, especially regarding Linux/macOS retirement.
  • Provide guidance or alternatives for Linux/macOS users, such as links to other configuration management solutions (e.g., Ansible, Chef, Puppet) or Azure-native equivalents.
  • If any features remain available for Linux, include Linux/macOS-specific examples and instructions.
  • Avoid using Windows-specific terminology (e.g., PSCredential, Chocolatey) without clarifying platform applicability.
  • Reorder examples and references so that platform-neutral or cross-platform information appears before Windows-specific details.
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-12 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 PowerShell Core (used on Linux/macOS) is not supported. No Linux or macOS alternatives, examples, or guidance are provided, making it difficult for non-Windows users to follow the instructions.
Recommendations
  • Provide equivalent instructions and examples for Linux/macOS users, such as using PowerShell Core where possible.
  • Clarify which features are Windows-only and suggest alternatives (e.g., using REST APIs or Microsoft Graph SDKs) for Linux/macOS.
  • Include cross-platform compatibility notes for each major step.
  • Offer guidance on running Azure Automation tasks from Linux/macOS environments, or explicitly state limitations.
  • If PowerShell Core support is not possible, recommend alternative automation approaches for non-Windows users.
GitHub Create Pull Request
← Previous Page 1 of 15 Next →