Automation

123
Total Pages
37
Linux-Friendly Pages
86
Pages with Bias
69.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (132)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/delete-account.md [View Details]
Scanned: 2025-07-17 00:00 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell examples are presented as the only scripting/automation option, and the documentation does not mention or prioritize Linux-native tools or workflows. The structure and examples assume a Windows-centric approach, potentially excluding Linux users or those preferring cross-platform tools.
Recommendations:
  • Add Azure CLI examples (az automation account delete, az monitor log-analytics solution delete, etc.) alongside PowerShell for all relevant operations.
  • Include Bash shell snippets where appropriate, especially for users on Linux or macOS.
  • When listing command-line options, present Azure CLI before or alongside PowerShell to avoid the impression of Windows-first bias.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider providing REST API examples using curl or httpie for users who prefer direct API calls.
  • Review screenshots and UI instructions to ensure they are not Windows-specific (e.g., avoid showing only Windows browser UI elements).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-types.md [View Details]
Scanned: 2025-07-17 00:00 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation page exhibits a strong Windows and PowerShell bias. PowerShell (including Windows PowerShell and PowerShell Workflow) is presented first and in much greater detail than Python or Linux-specific options. Many examples, sample scripts, and troubleshooting steps reference Windows file paths (e.g., C:\modules), Windows environment variables, and Windows-specific behaviors. There is little to no coverage of Linux-specific runbook authoring, execution, or troubleshooting, and no Linux shell (bash) examples are provided. Even where Linux is mentioned (e.g., Hybrid Runbook Workers), details are minimal compared to the extensive PowerShell/Windows coverage.
Recommendations:
  • Add Linux-specific examples and troubleshooting steps, especially for Hybrid Runbook Workers running on Linux.
  • Provide parity in sample scripts, such as showing how to manage modules, file paths, and environment variables on Linux (e.g., using /opt, $HOME, or /tmp instead of C:\ paths).
  • Include bash or Python shell examples where appropriate, not just PowerShell.
  • Clarify which features and limitations apply to Linux Hybrid Runbook Workers, and document any Linux-specific constraints or workarounds.
  • Reorder or balance the presentation so that Python and Linux options are not always secondary to Windows/PowerShell.
  • Explicitly mention Linux support (or lack thereof) in each runbook type's description and limitations.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-webhooks.md [View Details]
Scanned: 2025-07-16 00:00 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a strong Windows and PowerShell bias. All code examples for creating, using, and managing webhooks are provided exclusively in PowerShell, with no equivalent Bash, curl, or CLI examples for Linux or cross-platform users. Windows/PowerShell tools and cmdlets (e.g., Invoke-WebRequest, Get-Content, Az Module) are used throughout, and there is no mention of Linux-native tools or workflows. Even REST API usage is shown only via PowerShell. The documentation does not address how to perform these tasks from a Linux environment or with cross-platform tools, and the PowerShell-first approach may hinder accessibility for non-Windows users.
Recommendations:
  • Provide equivalent examples using Bash and curl for all webhook operations (creation, invocation, deletion, etc.), especially for REST API calls.
  • Include Azure CLI (az) command examples for creating and managing Automation webhooks, as Azure CLI is cross-platform.
  • Show how to use common Linux tools (e.g., jq, curl, wget) to interact with webhooks and parse responses.
  • Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux users.
  • Where PowerShell is required (e.g., for runbook code), clarify that PowerShell Core is available cross-platform and provide notes on any differences.
  • Add a section or callouts for Linux/macOS users, outlining any prerequisites or differences in workflow.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-use-azure-ad.md [View Details]
Scanned: 2025-07-16 00:00 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation is heavily focused on Windows and PowerShell, with all examples and module references using Windows PowerShell cmdlets and patterns. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or cross-platform scripting. Windows-specific tools and classes (e.g., PSCredential, Get-Credential) are mentioned exclusively, and the documentation does not acknowledge or provide alternatives for Linux environments.
Recommendations:
  • Add equivalent Azure CLI (az) examples for all major steps, such as authentication, credential management, and resource management, to support Linux and macOS users.
  • Include Bash or Python script examples for common automation tasks, demonstrating how to interact with Azure Automation and Microsoft Entra ID from non-Windows platforms.
  • Explicitly mention cross-platform options and clarify which steps or modules are Windows-only, providing links or references to Linux-compatible alternatives.
  • Reorganize sections to present cross-platform or CLI approaches alongside PowerShell, rather than only after or not at all.
  • Reference documentation for Azure CLI and SDKs in the 'Next steps' section, not just PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-types.md [View Details]
Scanned: 2025-07-16 00:00 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by prioritizing PowerShell (a Windows-centric technology) in both structure and content. PowerShell runbooks are described first and in the most detail, with extensive examples and troubleshooting based on Windows file paths (e.g., C:\modules). Many examples and known issues reference Windows-specific patterns, such as environment variables and file paths, with little or no equivalent Linux guidance. The documentation also references Windows tools and concepts (e.g., PowerShell Workflow, graphical runbooks based on Windows PowerShell) and often omits or minimizes Linux-specific details, especially for hybrid worker scenarios. Python runbooks receive less coverage, and Linux-specific instructions or examples are sparse or missing.
Recommendations:
  • Provide Linux-specific examples and troubleshooting steps alongside or before Windows examples, especially for hybrid worker scenarios.
  • Avoid using only Windows file paths (e.g., C:\modules); include Linux equivalents (e.g., /opt/automation/modules) where relevant.
  • Clarify which features and limitations apply to Windows, Linux, or both, particularly for hybrid runbook workers.
  • Expand Python runbook documentation to include Linux-specific package management, environment setup, and known issues.
  • Where PowerShell is discussed, explicitly note cross-platform capabilities and provide Linux usage notes or caveats.
  • For graphical and workflow runbooks, clearly state platform support and provide alternatives or workarounds for Linux users.
  • Ensure that all code samples, troubleshooting steps, and environment variable references are presented for both Windows and Linux contexts.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-remediate.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation prioritizes Windows remediation steps by providing a clear PowerShell example and direct guidance for Windows VMs, while Linux remediation is described in less detail, lacks direct script examples, and is presented as less supported (e.g., 'you don't have the option of using the Run command'). Windows tools and cmdlets are referenced directly, while Linux solutions are only linked or described in passing.
Recommendations:
  • Provide a direct Linux command-line example (e.g., Bash or Python) for remediating drift, similar to the PowerShell example for Windows.
  • Clarify and expand on the Linux remediation process, including step-by-step instructions and sample scripts.
  • Reference Linux-native tools and workflows explicitly, not just through external links.
  • Present Windows and Linux remediation sections with equal prominence and detail.
  • If certain features (like Run Command) are unavailable for Linux, suggest alternative Azure-native or open-source solutions, and explain any workarounds.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/change-tracking/manage-change-tracking-monitoring-agent.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools
Summary:
The documentation generally presents Windows-specific concepts (such as Windows Registry and environment variables) before Linux equivalents, and Windows examples (e.g., file paths, use of %winDir%) are described in more detail. Windows terminology and tools (like the Registry) are mentioned without Linux parallels, and Windows file tracking is described before Linux file tracking. However, Linux is included in most sections, and Linux-specific instructions are present.
Recommendations:
  • Alternate the order of Windows and Linux examples/tabs so that Linux is sometimes presented first.
  • When referencing Windows-specific tools (like the Registry), provide Linux equivalents or explicitly state when a feature is Windows-only.
  • Ensure that Linux examples (such as file paths or environment variables) are as detailed as Windows examples.
  • Where possible, provide parity in screenshots and step-by-step instructions for both Windows and Linux.
  • Review terminology to ensure that Windows concepts are not assumed as the default (e.g., avoid referencing environment variables only in Windows context).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy Windows Tools
Summary:
The documentation exhibits a Windows bias in several ways: (1) Windows-specific examples and tools (e.g., PowerShell, Windows registry paths) are provided first or exclusively in key sections, especially in the Bicep, ARM template, PowerShell, and removal instructions. (2) There is a lack of equivalent Linux-focused examples for core automation scenarios (e.g., Bicep/ARM templates and PowerShell/CLI commands are tailored to Windows VMs and extensions, with no Linux VM or extension examples). (3) PowerShell is heavily featured, with less emphasis on bash or Linux-native scripting. (4) Windows-specific requirements and tools (e.g., .NET Framework, Windows PowerShell 5.1) are highlighted, while Linux requirements are less detailed or are presented as secondary.
Recommendations:
  • Provide Linux-specific examples alongside Windows examples for Bicep, ARM templates, REST API, Azure CLI, and PowerShell sections. For instance, show how to deploy a Linux VM and install the HybridWorkerForLinux extension.
  • Ensure that Linux commands and requirements are given equal prominence and detail as Windows, including bash scripts and Linux-native automation tools.
  • When listing prerequisites, present Windows and Linux requirements in parallel, and avoid listing Windows first by default.
  • For PowerShell-heavy sections, provide equivalent bash or shell script examples for Linux users.
  • Clarify when a step or tool is Windows-only, and always provide the Linux alternative immediately after or in a side-by-side format.
  • In code samples and parameter tables, include Linux OS options and extension types (e.g., HybridWorkerForLinux) wherever Windows options are shown.
  • Expand the removal instructions for Linux to include cleanup of all related components, matching the detail provided for Windows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-graphical-authoring-intro.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation is heavily focused on Windows PowerShell and PowerShell Workflow, with all examples, terminology, and workflows centered around PowerShell cmdlets and scripting. There is no mention of Linux, Bash, or cross-platform scripting alternatives. The documentation assumes familiarity with Windows-centric tools and patterns, and does not provide parity or guidance for Linux users or those using non-Windows environments.
Recommendations:
  • Explicitly state that Azure Automation graphical runbooks are currently limited to PowerShell and clarify platform support (e.g., Windows-only or cross-platform PowerShell Core).
  • If Linux support is available (e.g., via PowerShell Core on Linux), provide examples and guidance for Linux users, including any differences in cmdlet availability or behavior.
  • Include a section comparing graphical runbooks with textual runbooks, highlighting scenarios where Bash, Python, or other languages (supported in Azure Automation) may be preferable, and link to relevant documentation.
  • Mention any limitations or considerations for Linux-based Automation workers, if applicable.
  • Where possible, provide cross-platform PowerShell examples (using PowerShell Core syntax) and clarify when examples are Windows-specific.
  • Add references or links to documentation for authoring and running runbooks in other languages (Bash, Python) for users who do not use PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-security-overview.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets as the primary automation interface, mentioning Azure Resource Manager and PowerShell together, and omitting any explicit mention of Linux tools, Bash, or cross-platform scripting examples. There are no Linux-specific authentication workflows, nor are there examples or guidance for Linux users. The documentation assumes a Windows-centric approach to automation, both in terminology and in the tools referenced.
Recommendations:
  • Include examples of authenticating and automating tasks using Bash, Azure CLI, or Python scripts, not just PowerShell.
  • Explicitly mention that Azure Automation supports both Windows and Linux Hybrid Runbook Workers, and provide parity in examples.
  • Add sections or notes describing how Linux users can authenticate and interact with Azure Automation, including any differences in setup or permissions.
  • Reference cross-platform tools (e.g., Azure CLI) alongside PowerShell, and avoid presenting Windows tools or patterns first or exclusively.
  • Provide links to Linux-specific or cross-platform documentation where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-secure-asset-encryption.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a strong Windows bias by providing only PowerShell examples for all command-line operations, referencing PowerShell modules and cmdlets exclusively, and omitting equivalent instructions for Linux environments (such as Azure CLI or Bash). Windows-centric tools and patterns are mentioned first and often exclusively, with no parity for Linux-native workflows.
Recommendations:
  • Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and commonly used on Linux and macOS.
  • Include Bash script examples where appropriate, especially for automation scenarios.
  • Mention both PowerShell and CLI options in prerequisites and throughout the documentation, not just PowerShell.
  • Clarify that PowerShell can be used cross-platform, but also highlight native Linux workflows.
  • Add a section or callouts for Linux/macOS users, ensuring they can follow the same procedures without relying on Windows tools.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-child-runbooks.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation is heavily focused on PowerShell-based runbooks and Windows-centric tools (such as the Az PowerShell module and cmdlets like Start-AzAutomationRunbook). All examples are in PowerShell, and there is no mention of Linux-native scripting (e.g., Bash, Python) or cross-platform approaches. The documentation assumes the use of Windows/PowerShell patterns and does not provide parity for Linux users or those preferring non-PowerShell automation.
Recommendations:
  • Add equivalent examples using Python and Bash runbooks, which are supported in Azure Automation.
  • Include references to Linux-based scripting environments and clarify which features are available for non-PowerShell runbooks.
  • Mention and provide examples for starting and managing runbooks using the Azure CLI (az automation runbook ...), which is cross-platform.
  • Reorganize sections to mention cross-platform options (Python, Bash, Azure CLI) alongside or before Windows/PowerShell-specific tools.
  • Clarify any limitations or differences in behavior for non-PowerShell runbooks (e.g., parameter passing, job output retrieval).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-output-and-messages.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a strong Windows/PowerShell bias. All code examples, tool references, and explanations are exclusively based on Windows PowerShell cmdlets and patterns. There are no examples or guidance for Linux-based automation, Bash, or Python runbooks (except for a brief note about Python output language support). Retrieval of runbook output is only shown using Windows PowerShell tools, and preference variables are discussed only in the context of PowerShell. No Linux-native or cross-platform CLI (such as Azure CLI) equivalents are provided.
Recommendations:
  • Add equivalent examples using Azure CLI (az) commands for retrieving runbook output and managing jobs, which work cross-platform.
  • Include Bash or Python runbook examples where applicable, especially in sections discussing output and message streams.
  • When referencing tools or commands, mention cross-platform options (e.g., Azure CLI, REST API) alongside or before Windows PowerShell.
  • Clarify which features or behaviors are specific to PowerShell-based runbooks versus those available in Python or other supported runbook types.
  • Provide links to documentation for managing Azure Automation from Linux/macOS environments.
  • If certain features are only available in PowerShell runbooks, explicitly state this and suggest alternatives for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-disaster-recovery.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a significant Windows and PowerShell bias. All migration scripts and automation examples are provided exclusively in PowerShell, with no mention of Bash, Python, or cross-platform scripting alternatives. The instructions for Hybrid Runbook Worker installation and management link first (and sometimes only) to Windows-specific tabs or documentation. There are no Linux-specific or cross-platform code samples, and the required modules and runtime environments are all Windows/PowerShell-centric. This creates an impression that Linux users are secondary or unsupported, despite the initial claim of Linux VM applicability.
Recommendations:
  • Provide equivalent Bash or Python scripts for asset migration, or at least reference cross-platform alternatives if available.
  • Include explicit Linux examples and instructions, especially for Hybrid Runbook Worker deployment and management.
  • Ensure that documentation tabs and links are balanced, offering both Windows and Linux options side-by-side.
  • Mention and support cross-platform modules or tools (such as Azure CLI) where possible, not just PowerShell/Az modules.
  • Clarify any limitations or differences for Linux users up front, and provide guidance for achieving parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-compile.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily focused on Windows and PowerShell-based workflows for compiling DSC configurations in Azure Automation. All code examples use PowerShell, and there is no mention or example of using Linux-based tools or workflows. Windows-specific modules, cmdlets, and file paths are referenced throughout, and Linux alternatives or cross-platform approaches are not discussed. The documentation assumes a Windows environment and does not address Linux users' needs.
Recommendations:
  • Add examples using cross-platform PowerShell Core (pwsh) and clarify compatibility with Linux/macOS.
  • Explicitly state whether DSC compilation and management is supported on Linux, and if not, provide guidance or alternatives for Linux users.
  • If Linux support is deprecated (as hinted by the retirement announcement), clearly highlight this at the top and provide migration paths or alternatives.
  • Provide equivalent command-line or scripting examples for Linux environments where possible, or explain limitations.
  • Avoid using only Windows file paths (e.g., C:\...) in examples; include Linux-style paths or note platform differences.
  • Mention and link to any Linux-native tools or approaches for configuration management if applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-role-based-access-control.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by providing only PowerShell-based examples and workflows for configuring Azure RBAC and managing role assignments in Azure Automation. There are no examples or instructions using cross-platform tools such as Azure CLI, and no mention of Linux-native workflows or shell environments. The exclusive use of PowerShell and lack of Linux/CLI parity may hinder users on non-Windows platforms.
Recommendations:
  • Add equivalent Azure CLI (az) command examples for all PowerShell cmdlet instructions, including role assignment, listing, and removal.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI, and provide sample bash shell commands.
  • Where scripts are shown, offer both PowerShell and bash/CLI alternatives side by side.
  • Review references to 'PowerShell' in headings and text, ensuring that cross-platform options are equally visible and not presented as secondary.
  • Add a section or note clarifying that Azure Automation and RBAC are fully manageable from any OS using CLI or REST API, not just Windows/PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/delete-account.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation page demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell examples are presented as the only scripting/automation option, and the documentation refers to 'Azure PowerShell' before mentioning the Azure CLI or REST API (which are only mentioned in passing in the introduction). There are no Linux-specific instructions or examples, and no mention of running commands in Bash or on Linux/macOS platforms.
Recommendations:
  • Add Azure CLI examples (az commands) alongside PowerShell for all automation and deletion tasks.
  • Include Bash shell examples where appropriate, especially for cross-platform users.
  • When listing options (e.g., Azure portal, PowerShell, CLI, REST API), present Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
  • Explicitly state that all command-line examples work on Windows, Linux, and macOS where applicable, and clarify any platform-specific limitations.
  • Provide links or references to documentation for using Azure Automation with Linux environments, if available.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-getting-started.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy Windows Tools
Summary:
The documentation demonstrates a strong Windows bias. All code examples use Windows PowerShell DSC syntax and resources (such as WindowsFeature), and there are no Linux configuration examples. The only VM creation link is for Windows, and references to DSC documentation and resources are Windows-centric. Linux is only mentioned in passing, with no practical guidance or parity in examples.
Recommendations:
  • Provide parallel Linux examples, such as a sample DSC configuration using the nx or nxFile resource for Linux nodes.
  • Include links to both Windows and Linux VM creation guides in the prerequisites.
  • Reference both Windows and Linux DSC documentation in the overview and next steps.
  • Clarify which features and steps apply to Linux, and note any differences or limitations.
  • If Linux support is deprecated, make this explicit at the start and provide migration or alternative guidance for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/dsc-configuration.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a strong Windows bias: it assumes the use of PowerShell syntax throughout, references Windows-centric tools and patterns (such as MOF documents and the PowerShell Gallery), and does not provide Linux-native alternatives or examples. Although the configuration example targets a LAMP stack (Linux), the entire workflow is described using PowerShell DSC constructs, and the documentation explicitly notes that Azure Automation DSC for Linux has been retired, further marginalizing Linux users. There are no Bash or Linux-native configuration examples, and next steps reference Chocolatey, a Windows package manager.
Recommendations:
  • Provide parity for Linux users by including examples using native Linux configuration management tools (such as Ansible, Chef, or native Azure Policy Guest Configuration for Linux).
  • Offer Bash or shell script equivalents for steps currently described only in PowerShell.
  • Clarify the current support status for Linux and direct users to up-to-date, supported alternatives for Linux VM configuration.
  • When referencing tools like Chocolatey, also mention Linux package managers (e.g., apt, yum) or cross-platform solutions.
  • Reorganize the documentation to avoid assuming PowerShell as the default, and explicitly state when steps are Windows-only.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-overview.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows and PowerShell bias. PowerShell DSC is the only configuration language discussed, and examples or references are almost exclusively Windows-centric. Windows operating systems are listed first and in detail, while Linux support is referenced generically and with less detail. Windows-specific tools and patterns (e.g., WinRM, WMF, PowerShell cmdlets, Chocolatey) are mentioned without Linux equivalents or examples. There are no Linux-specific walkthroughs or examples, and Linux support is often described as an afterthought.
Recommendations:
  • Provide Linux-specific examples for onboarding, configuration, and troubleshooting, including sample commands and scripts.
  • List Linux operating systems and their requirements with the same level of detail as Windows.
  • Include references to Linux-native configuration tools or patterns where appropriate (e.g., systemd, shell scripts, or integration with Linux package managers).
  • Offer parity in documentation structure: for every Windows/PowerShell example or tool mentioned, provide the Linux equivalent or clearly state limitations.
  • Highlight any differences or limitations in Linux support up front, and keep Linux-specific retirement or deprecation notices clearly separated from general documentation.
  • Add a Linux-focused 'Next steps' or quickstart guide, similar to the Windows/PowerShell guidance.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-managing-data.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation exhibits a Windows bias by providing more detailed and prominent guidance for Windows users, especially around TLS configuration and data backup. Windows-specific tools (PowerShell cmdlets) are referenced repeatedly, often without Linux or cross-platform equivalents. Linux guidance is present but less detailed and sometimes appears after Windows instructions. Several examples and instructions are Windows-centric, with Linux alternatives either missing or less emphasized.
Recommendations:
  • Provide Linux command-line (bash, shell) examples alongside or before Windows/PowerShell examples for all relevant operations (e.g., exporting runbooks, managing DSC nodes).
  • Reference cross-platform tools (such as Azure CLI or REST API) where possible, rather than only PowerShell cmdlets.
  • Ensure Linux-specific instructions are as detailed and actionable as Windows instructions (e.g., for TLS configuration, provide distro-specific guidance and verification steps).
  • Balance the order of presentation: alternate between Windows and Linux, or group by platform, rather than always listing Windows first.
  • Where Windows registry or PowerShell is referenced, provide equivalent Linux file or command references (e.g., for confirming TLS settings).
  • Explicitly mention if a feature or operation is not available or differs on Linux, to avoid ambiguity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/change-tracking/enable-change-tracking-at-scale-policy.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation claims support for both Windows and Linux VMs, but throughout the page, there is a clear Windows-first bias. Windows-specific features (like Registry and Software tracking) are highlighted in the introduction, and the policy breakdown lists 'Configure ChangeTracking Extension for Windows virtual machines' before the Linux equivalent. There are no Linux-specific examples, screenshots, or mentions of Linux-specific tracked items (e.g., Linux packages or configuration files), and all screenshots and UI references are generic or Windows-centric. No Linux command-line or configuration examples are provided.
Recommendations:
  • Include explicit Linux examples, such as tracking Linux package changes or configuration files.
  • Balance the order of presentation: alternate or group Windows and Linux instructions equally, or start with Linux in some sections.
  • Add screenshots or UI references that show Linux-specific tracking (e.g., tracking /etc files or installed packages).
  • Mention Linux-specific tracked items and clarify parity or differences in feature support.
  • If command-line or scripting examples are provided, ensure both PowerShell (Windows) and Bash (Linux) examples are included.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-connections.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples for creating and managing connections use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux-native tools. The section for creating a new connection specifically references 'Windows PowerShell' and provides only PowerShell examples. There is no guidance or example for users working from Linux or macOS environments. The documentation also refers to Windows-centric patterns and tools (e.g., PowerShell cmdlets, DSC configurations) before mentioning Python, and does not provide parity for Linux/CLI workflows.
Recommendations:
  • Add Azure CLI examples for creating and managing connections, suitable for Linux/macOS users.
  • Include Bash script examples where appropriate, especially for automation scenarios.
  • Clarify that PowerShell examples can be run cross-platform (if true), or provide equivalent instructions for non-Windows environments.
  • Mention and link to any Linux-compatible tools or modules for Azure Automation.
  • Rephrase headings and instructions to be OS-neutral (e.g., 'Create a new connection with the command line' instead of 'with Windows PowerShell').
  • Ensure that all workflows (creation, management, retrieval of connections) have both PowerShell and CLI/Bash examples.
  • Explicitly state platform support and any limitations for Linux/macOS users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-types.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation exhibits a Windows and PowerShell-centric bias. PowerShell (including Windows PowerShell and PowerShell Workflow) is presented first and in the most detail, with numerous examples and troubleshooting sections focused on Windows paths, environment variables, and cmdlets. Many examples and limitations reference Windows-specific file paths (e.g., C:\modules), environment variables, and tools, with little or no equivalent Linux guidance. Python runbooks are discussed, but Linux-specific instructions are minimal and often secondary to Windows explanations. Graphical runbooks and workflows are also tightly coupled to Windows PowerShell, and Linux support is explicitly limited or absent.
Recommendations:
  • Provide Linux-specific examples and troubleshooting guidance alongside or before Windows examples, especially for file paths, environment variables, and known issues.
  • When referencing environment variables or file paths, include both Windows and Linux formats (e.g., C:\modules and /opt/automation/modules).
  • Clarify which features and limitations apply to Linux Hybrid Runbook Workers, and offer Linux workarounds where possible.
  • For PowerShell runbooks, explicitly document differences in behavior or support between Windows and Linux Hybrid Runbook Workers.
  • Expand Python runbook sections to include more Linux-specific details, such as package management, file system paths, and common issues.
  • Where graphical runbooks or workflows are Windows-only, suggest alternative approaches for Linux users or clearly state the lack of support.
  • Balance the order of presentation so that Linux and cross-platform scenarios are not always secondary to Windows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-onboarding.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a strong Windows and PowerShell bias. Most examples, scripts, and workflows are presented using PowerShell and Windows-specific tooling (e.g., WMF 5, PowerShell DSC cmdlets), with Linux instructions often appearing later, being less detailed, or requiring Windows tools to manage Linux nodes. Some Linux-specific steps are present, but they are less comprehensive, and Linux users are frequently directed to use Windows/PowerShell environments for configuration generation and management.
Recommendations:
  • Provide Linux-first and cross-platform examples alongside Windows/PowerShell examples, especially in sections on generating and applying DSC metaconfigurations.
  • Include native Linux command-line examples (e.g., Bash, Python) for all major workflows, such as onboarding, configuration, and status checking.
  • Document how to generate and apply DSC metaconfigurations entirely from a Linux environment, without requiring access to Windows or PowerShell.
  • List Linux and Windows instructions in parallel, or clearly separate them, rather than always presenting Windows/PowerShell first.
  • Expand Linux troubleshooting and operational guidance to match the depth provided for Windows.
  • Where PowerShell is required for Linux, clarify if PowerShell Core on Linux is supported, and provide examples accordingly.
  • Avoid assuming the user has access to a Windows machine for managing Linux nodes; provide alternatives where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/install-hybrid-worker-extension.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows-first bias by focusing exclusively on installing the Hybrid Worker extension on Windows Azure Virtual Machines. All step-by-step instructions, screenshots, and extension names are Windows-specific, with no equivalent guidance or visuals for Linux VMs. Linux is only mentioned in passing, and there are no examples or instructions for Linux users.
Recommendations:
  • Provide parallel step-by-step instructions and screenshots for installing the Hybrid Worker extension on Linux Azure Virtual Machines.
  • Explicitly mention and show the selection of the Linux Hybrid Worker extension in the Azure portal, including its name and any differences in the installation process.
  • Update the prerequisites section to include both Windows and Linux VM requirements.
  • Ensure that all references to extension names and configuration steps are clear for both Windows and Linux scenarios.
  • Consider alternating the order of Windows and Linux instructions or presenting them side-by-side to avoid a Windows-first impression.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/change-tracking/overview-monitoring-agent.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Powershell Heavy Missing Linux Example
Summary:
The documentation demonstrates a moderate Windows bias. Windows-specific concepts (such as registry keys and Windows services) are described in greater detail and with more examples than their Linux equivalents. Windows tools, paths, and terminology (e.g., c:\ paths, registry, Windows services) are often mentioned first or exclusively, and alerting examples focus heavily on Windows scenarios. While Linux is supported and mentioned, Linux-specific examples (e.g., for daemons, package tracking, or file paths) are less detailed or absent in some sections. The registry tracking section is entirely Windows-centric, and alerting queries are predominantly Windows-focused, with only one Linux daemon example. Powershell is used as the default CLI context, even for Linux commands.
Recommendations:
  • Provide equivalent Linux-focused examples alongside Windows examples in all sections, especially for alerting queries and configuration tracking.
  • Expand the documentation on Linux-specific features, such as daemon tracking, package inventory, and typical Linux configuration files (e.g., /etc/hosts, /etc/passwd).
  • When listing features or examples, alternate the order or present both Windows and Linux scenarios together to avoid 'windows_first' bias.
  • Include Linux command-line examples using bash or shell where appropriate, rather than only using PowerShell or Windows-centric CLI.
  • Add a section on tracking Linux configuration files and directories, with concrete examples (e.g., monitoring changes in /etc/ssh/sshd_config or /var/log).
  • In registry/key tracking sections, clarify that this is Windows-only and provide a parallel discussion of Linux equivalents (e.g., tracking changes in /etc or systemd unit files).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/desired-state-configuration.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation is heavily oriented toward Windows and PowerShell environments. Troubleshooting steps, examples, and tooling (such as xDscDiagnostics, PowerShell cmdlets, and references to Windows event logs and WMI) are almost exclusively Windows-centric. Linux is only mentioned in a single scenario, with no equivalent troubleshooting depth, examples, or tooling guidance. Windows tools and patterns are introduced first and often exclusively, with Linux support treated as an afterthought or omitted.
Recommendations:
  • Provide Linux-specific troubleshooting steps and examples for each scenario where applicable, including log locations, commands, and error investigation techniques relevant to Linux nodes.
  • Include Linux equivalents for all PowerShell cmdlets and tools, such as how to collect and analyze DSC logs on Linux, and how to manage certificates or extensions.
  • Balance the order of presentation by mentioning Linux approaches alongside Windows, rather than only after or not at all.
  • Reference Linux-native tools (e.g., journalctl, systemd, log files in /var/log) and shell commands where appropriate.
  • Clarify where features or tools are Windows-only, and provide alternative guidance for Linux users.
  • Expand the Linux troubleshooting section to cover common issues, error messages, and resolutions in parity with the Windows content.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/how-to/private-link-security.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias primarily through the exclusive use of PowerShell for scripting examples (e.g., setting public network access flags), and by referencing Windows tools and patterns (such as PowerShell Desired State Configuration) without providing equivalent Linux/Unix command-line or scripting examples. While the text mentions Linux support in some features, practical examples and configuration steps are only shown for Windows/PowerShell environments, leaving Linux users without direct guidance.
Recommendations:
  • Provide equivalent Azure CLI or Bash examples alongside PowerShell scripts, especially for key configuration steps such as setting the publicNetworkAccess property.
  • When referencing configuration management (e.g., DSC), include notes or links about Linux alternatives (such as Chef, Puppet, or native Linux DSC support) and how they interact with Azure Automation.
  • Explicitly show Linux command-line examples for agent installation, configuration, and DNS setup, not just mention that Linux is supported.
  • Ensure that screenshots and UI walkthroughs do not assume a Windows-centric environment (e.g., referencing Windows file paths or tools only).
  • Add a dedicated section or callouts for Linux users, summarizing any differences or additional steps required for parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-send-email.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based instructions and examples for all steps, including Azure resource management, Key Vault operations, and the runbook itself. There are no references to Bash, Azure CLI, or Linux-based scripting alternatives. All tooling and module references (e.g., Az PowerShell module) are Windows-centric, and the workflow assumes the use of PowerShell as the default and only supported scripting environment.
Recommendations:
  • Provide equivalent Azure CLI (az) and/or Bash script examples for all resource creation, permission assignment, and secret management steps.
  • Include a sample runbook written in Python (supported in Azure Automation) or Bash, demonstrating how to retrieve secrets and send emails using SendGrid.
  • Mention and link to Linux/macOS-compatible tools and installation instructions, not just PowerShell modules.
  • Rephrase instructions to be platform-neutral where possible, or explicitly note that the steps apply to both Windows and Linux environments.
  • Add a section or callout for users who prefer or require non-Windows environments, outlining their options for achieving the same automation goals.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/source-control-integration.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily biased towards Windows and PowerShell environments. All command-line examples use PowerShell cmdlets, and there are no equivalent instructions or examples for Linux users (e.g., using Azure CLI, Bash, or cross-platform scripting). The documentation assumes the use of PowerShell consoles and Windows-specific tools, and there is no mention of how to perform these tasks on Linux or macOS. The only supported runbook type for source control integration is PowerShell 5.1, which is Windows-only, further reinforcing the Windows-centric approach.
Recommendations:
  • Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
  • Explicitly state the platform limitations (e.g., that PowerShell 5.1 is Windows-only) and provide guidance for users on other platforms.
  • Include Bash or shell script examples for common tasks, such as assigning roles or configuring source control.
  • Mention and document any Linux/macOS-compatible alternatives for tasks currently shown only with PowerShell.
  • Clarify whether source control integration is possible with Python or other cross-platform runbook types, and if not, explain the roadmap or alternatives.
  • Add troubleshooting and encoding guidance relevant to Linux/macOS editors and environments, not just those focused on Windows/PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/shared-resources.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. All troubleshooting steps, code examples, and references are provided exclusively for PowerShell, with no mention of Linux/Unix equivalents or cross-platform approaches. Windows-specific DLL errors and cmdlets are discussed without Linux context, and there are no Bash, CLI, or Python examples for Linux users.
Recommendations:
  • Provide equivalent troubleshooting steps and examples using Azure CLI (az) and Bash scripts for Linux users.
  • Mention cross-platform modules and tools where possible, and clarify which steps are Windows-specific.
  • Include notes or sections on how to perform common tasks (such as module import, authentication, and error resolution) in Linux environments.
  • Reference Linux-specific issues or error messages that may arise in Azure Automation, and how to resolve them.
  • Balance the order of presentation so that Linux and cross-platform solutions are given equal prominence to Windows/PowerShell solutions.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/shared-resources/modules.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation is heavily focused on PowerShell modules and workflows, with nearly all examples, instructions, and internal tooling centered on Windows PowerShell and Windows-specific features. Internal cmdlets and modules are explicitly unavailable on Linux Hybrid Runbook Workers, and there are no Linux shell or cross-platform scripting examples. Linux support is mentioned only to note limitations or lack of availability, and there are no Linux-native module management workflows or parity in examples.
Recommendations:
  • Provide equivalent Linux/bash examples for module management, such as using Azure CLI or bash scripts to import, update, or delete modules.
  • Clearly indicate which features are Windows-only and provide alternative workflows or guidance for Linux Hybrid Runbook Workers.
  • Include documentation and examples for managing Python modules and runbooks on Linux, not just a link to another page.
  • Highlight cross-platform capabilities and limitations in a dedicated section, making it clear what is supported on Linux vs. Windows.
  • When listing internal cmdlets or features, suggest Linux-compatible alternatives or workarounds where possible.
  • Balance the order of presentation so that Linux and cross-platform options are not always secondary or omitted.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/shared-resources/credentials.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation is heavily focused on Windows and PowerShell usage, with all command-line examples and tooling instructions centered around PowerShell cmdlets and Windows-specific patterns. Linux or cross-platform CLI alternatives are not mentioned, and there are no examples using Bash, Azure CLI, or other Linux-native tools. The Python examples are present but limited to the Azure Automation Python SDK, not general Linux workflows. The documentation assumes a Windows/PowerShell environment for automation tasks.
Recommendations:
  • Add equivalent examples using Azure CLI (az) commands for credential management, which are cross-platform and work natively on Linux.
  • Include Bash or shell script examples for retrieving and using credentials in runbooks, especially for Linux Hybrid Runbook Workers.
  • Mention and document how Linux users can interact with Azure Automation credentials, including any SDKs or REST API usage.
  • Avoid referring to 'Windows PowerShell' exclusively; use 'PowerShell' and clarify cross-platform compatibility where possible.
  • List Linux-compatible tools and workflows alongside PowerShell cmdlets, and avoid presenting Windows tools first or exclusively.
  • Clarify which features or modules are available on Linux-based Automation workers and provide parity guidance.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/runbook-input-parameters.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a strong Windows/PowerShell bias. All code examples and workflows are centered around PowerShell, PowerShell Workflow, and graphical runbooks that use PowerShell cmdlets. Windows-specific tools and patterns (such as PowerShell cmdlets, .NET types, and C# SDK examples) are used exclusively, with no equivalent Bash, Linux shell, or cross-platform CLI examples. The Python section is minimal and lacks parity in detail or examples. There are no references to Linux-native tools, and PowerShell is always presented first and in the most detail.
Recommendations:
  • Add equivalent examples for starting and managing runbooks using Azure CLI (az), which is cross-platform and widely used on Linux.
  • Provide Bash or shell script examples for interacting with Azure Automation via REST API or Azure CLI.
  • Expand the Python section to include detailed parameter handling, example scripts, and parity with PowerShell examples.
  • Mention and demonstrate how to use Linux/macOS environments for authoring and running runbooks, including any differences or considerations.
  • Where PowerShell-specific types or patterns are discussed, note their Linux/Python/CLI equivalents or limitations.
  • Ensure that references to tools and workflows are not Windows-first; present Azure CLI or REST API approaches before or alongside PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/tutorial-configure-servers-desired-state.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily focused on Windows and PowerShell, providing only Windows-centric examples (such as installing IIS), referencing only Windows VMs in prerequisites, and using only PowerShell cmdlets throughout. There are no Linux-specific examples, commands, or guidance, and Linux support is only briefly mentioned in passing. The documentation assumes the use of Windows tools and patterns, with no parity for Linux users.
Recommendations:
  • Add Linux-specific examples, such as configuring a Linux VM with a DSC configuration (e.g., ensuring nginx or Apache is installed).
  • Include Bash/CLI commands or scripts for onboarding and managing Linux nodes, not just PowerShell.
  • Update prerequisites to mention Linux VMs and provide links to creating Linux VMs in Azure.
  • Clarify the current support status for Linux in Azure Automation State Configuration, especially given the referenced retirement announcement.
  • Provide guidance or references for managing Linux nodes, including any differences in onboarding, configuration, or compliance checking.
  • Balance the documentation structure so that Linux and Windows scenarios are presented with equal prominence.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-edit-textual-runbook.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily focused on Windows and PowerShell, providing only Windows PowerShell examples and using Windows file paths (e.g., c:\runbooks). There are no examples or guidance for Linux or cross-platform PowerShell Core usage, nor is there mention of Linux-compatible editors or workflows. The use of 'Windows PowerShell' and exclusive reference to Windows tools and conventions demonstrates a clear Windows bias.
Recommendations:
  • Provide examples using PowerShell Core (pwsh), which is cross-platform, and clarify compatibility with Linux and macOS.
  • Include Linux/macOS file path examples (e.g., /home/user/runbooks) alongside Windows paths.
  • Mention and demonstrate the use of editors available on Linux/macOS (e.g., VS Code, nano, vim) for editing runbooks.
  • Clarify that Az PowerShell module cmdlets can be used from any OS, not just Windows.
  • Add a section or notes on how to perform the same tasks from Linux/macOS terminals, including installation instructions for PowerShell Core and Az modules.
  • Avoid using 'Windows PowerShell' as the default term; use 'PowerShell' or specify when something is Windows-only.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/delete-run-as-account.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools
Summary:
The documentation focuses exclusively on deleting Azure Automation Run As accounts using PowerShell (a Windows-centric tool) and the Azure portal, without providing equivalent CLI or scripting examples for Linux users. There are no references to Bash, Azure CLI, or Linux-native tools, and the only command-line method mentioned is PowerShell.
Recommendations:
  • Add examples using Azure CLI (az) commands for deleting Run As accounts, which are cross-platform and commonly used on Linux.
  • Include Bash script examples where appropriate, or clarify that the steps are platform-agnostic if using the Azure portal.
  • Explicitly mention that PowerShell Core is cross-platform if PowerShell examples are retained, and provide installation guidance for Linux users.
  • Ensure that all command-line instructions are available for both Windows and Linux environments to improve accessibility and parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/manage-sql-server-in-automation.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation is heavily biased towards Windows and PowerShell usage. All code samples use PowerShell cmdlets, and there are no examples or guidance for using Linux-based tools or Bash scripting. The instructions for installing modules and running commands assume a PowerShell environment, and there is no mention of cross-platform alternatives or how to perform these tasks on Linux-based Hybrid Runbook Workers. The documentation also refers to Windows concepts (e.g., elevated PowerShell prompt) and does not provide parity for Linux users.
Recommendations:
  • Provide equivalent Bash/CLI examples for connecting to Azure SQL Database using managed identities (e.g., using Azure CLI and sqlcmd).
  • Document how to set up and use Hybrid Runbook Workers on Linux, including module installation and authentication steps.
  • Include instructions for installing required modules or tools on Linux (e.g., using pip for Azure CLI, apt/yum for sqlcmd).
  • Mention cross-platform compatibility of Azure Automation and clarify which steps or commands are OS-specific.
  • Add a section or note explicitly addressing Linux users and linking to relevant resources for Linux-based automation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/change-tracking/extension-version-details.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows-first bias: Windows issues and features are consistently listed before Linux equivalents, and some sections provide detailed workarounds or recommendations only for Windows (e.g., use of base64_decode_tostring() for Windows, but not for Linux). There are also references to Windows-specific tools and concepts (Windows Registry, Windows Services) without Linux equivalents being described in similar detail. In some extension versions, Linux changes are marked as 'None' or are less detailed, and Linux-specific issues or workarounds are not elaborated.
Recommendations:
  • Ensure Linux issues and features are described with equal detail and prominence as Windows.
  • Provide Linux-specific workarounds or equivalent commands/tools where Windows-specific ones are mentioned (e.g., if a KQL workaround is given for Windows, note if/how it applies to Linux).
  • List Linux and Windows changes/issues in parallel, rather than always listing Windows first.
  • Include examples or references for Linux tools and patterns (e.g., mention systemd for Linux daemons, or relevant Linux file/daemon tracking specifics).
  • Avoid marking Linux sections as 'None' without further context; if there are no changes, briefly explain why or what users should expect.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/enable-managed-identity.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by referencing PowerShell runbooks exclusively in the 'Next steps' section, without mentioning Linux or Python runbooks. There are no examples or guidance for Linux users or for using non-Windows scripting environments. The documentation assumes the use of PowerShell as the default automation language, which is more common on Windows.
Recommendations:
  • Include links to tutorials for creating Python runbooks using managed identity, as Python is commonly used for automation on Linux.
  • Explicitly mention that Automation accounts support both PowerShell and Python runbooks, and provide parity in examples and next steps.
  • Add a section or note for Linux users, clarifying that the steps apply regardless of OS, and reference relevant Linux-friendly tools or scripts.
  • Ensure that future documentation alternates or balances the order of PowerShell and Python/Linux examples, rather than defaulting to Windows-first patterns.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/change-tracking/guidance-migration-log-analytics-monitoring-agent.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools
Summary:
The documentation demonstrates a moderate Windows bias. Script-based migration is only described using PowerShell, with no mention of Bash, shell, or native Linux scripting alternatives. Prerequisites and instructions for scripting focus on PowerShell installation and modules, which are more familiar to Windows users. While Linux is mentioned as a supported platform, and Linux-specific data types (like Linux files and daemons) are referenced, the scripting and automation guidance is Windows-centric. The documentation also lists Windows data types before Linux ones and generally presents Windows concepts first.
Recommendations:
  • Provide equivalent Bash or shell script examples for Linux users, or explicitly document how to run the migration using native Linux tools.
  • Include Linux-first or Linux-parity instructions and examples, such as using Azure CLI or Bash scripts for migration.
  • Clarify any platform-specific differences or limitations in the migration process for Linux VMs.
  • List Linux and Windows data types in a neutral or alternating order to avoid implicit prioritization.
  • Reference Linux-native tools and patterns (e.g., systemd, cron) where relevant, not just PowerShell and Windows modules.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/python-packages.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by providing explicit instructions and command-line examples only for Windows environments (e.g., using Windows paths and referencing a Windows 64-bit machine for package download). There are no equivalent instructions or examples for Linux or macOS users, and Windows tools and patterns are mentioned exclusively.
Recommendations:
  • Provide equivalent Linux (and optionally macOS) instructions for downloading packages and dependencies, such as using the 'pip' command in a Linux shell.
  • Include Linux command-line examples alongside Windows examples, using standard Linux paths and conventions.
  • Avoid referencing only Windows-specific tools or environments; instead, offer cross-platform guidance or clarify when steps are platform-specific.
  • Add a note or section explicitly addressing how users on non-Windows systems can perform the same tasks.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-network-configuration.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation references Windows-centric tools and patterns, such as DSC resources and WaitFor resources, with links pointing to Windows PowerShell DSC documentation. There are no Linux-specific examples or references to Linux equivalents of DSC resources, and the documentation does not mention Linux-specific considerations for network configuration or agent communication.
Recommendations:
  • Include references and links to Linux DSC resources and documentation, such as the Linux DSC resource kit or documentation for Linux OMI-based DSC.
  • Provide examples or notes on configuring network requirements for Linux Hybrid Runbook Workers and State Configuration nodes.
  • Mention any Linux-specific ports, URLs, or agent behaviors if they differ from Windows.
  • Balance references to Windows and Linux in resource links and examples, ensuring Linux users can find relevant information easily.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/includes/automation-dsc-linux-retirement-announcement.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page only mentions the retirement of Azure Automation DSC for Linux, without providing any examples, tools, or migration guidance for Linux users. There is no mention of Windows equivalents, but the lack of Linux-specific guidance or alternatives creates a gap for Linux users.
Recommendations:
  • Provide clear migration steps or alternatives for Linux users affected by the retirement.
  • Include examples or references for configuring guest configuration or policy management on Linux.
  • Ensure parity by mentioning both Windows and Linux options for configuration management where relevant.
  • Link to documentation or tools that help Linux users transition to supported solutions.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-graphical-error-handling.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a strong bias toward Windows and PowerShell environments. All examples, terminology, and cmdlets are PowerShell-centric, with no mention of Linux, Bash, or cross-platform scripting. Windows tools and patterns (e.g., PowerShell cmdlets like Start-AzVM, Write-Warning, Get-AutomationVariable) are used exclusively, and there are no Linux or Bash equivalents provided. The error handling concepts are described solely in the context of PowerShell, and the documentation implicitly assumes the reader is operating in a Windows/PowerShell environment.
Recommendations:
  • Include examples using Bash or Python runbooks, which are supported in Azure Automation, to illustrate error handling in non-Windows environments.
  • Mention and demonstrate how error handling works in Linux-based runbooks, including differences in error types and handling patterns.
  • Provide parallel examples for common tasks (e.g., starting a VM, sending notifications) using both PowerShell and Bash/Python.
  • Clarify in the introduction that the guidance is PowerShell-specific, or restructure the documentation to address both Windows and Linux automation scenarios equally.
  • Reference relevant Linux tools or scripting patterns (e.g., try/catch in Bash, error codes, set -e) where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-cd-chocolatey.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy Windows Tools
Summary:
The documentation is heavily focused on Windows environments, exclusively using Windows Server, PowerShell, and Windows-specific tools (Chocolatey, PowerShell DSC, WindowsFeature, xNetworking) in all examples and instructions. Linux is only mentioned in passing, with no equivalent examples or guidance for Linux systems. The workflow, commands, and tooling are all tailored to Windows, with no parity for Linux users.
Recommendations:
  • Provide equivalent Linux examples using native Linux package managers (e.g., apt, yum) and configuration management tools (e.g., Ansible, Chef, Puppet, or Azure Automation State Configuration for Linux if available).
  • Include step-by-step instructions for setting up continuous deployment on Linux VMs, including sample configuration files and automation scripts.
  • Mention and demonstrate cross-platform tools or patterns where possible, and clarify any Azure Automation features that are Windows-only or deprecated for Linux.
  • Balance the documentation by presenting Linux scenarios alongside Windows, especially in sections describing high-level concepts, workflows, and automation patterns.
  • Clearly indicate the current support status for Linux in Azure Automation State Configuration, and provide links or references to Linux-specific guidance if Windows is the only supported platform.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-scenario-using-watcher-task.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation is heavily biased towards Windows environments. All examples and instructions use PowerShell, reference Windows-style paths (e.g., D:\examplefiles), and mention only Windows tools and conventions. There are no examples or guidance for Linux-based Hybrid Runbook Workers, nor are Linux shell commands or file path formats provided. The documentation assumes the user is operating in a Windows environment throughout.
Recommendations:
  • Provide equivalent examples for Linux-based Hybrid Runbook Workers, including bash shell commands for file creation and Linux file path formats (e.g., /home/examplefiles).
  • Mention that Azure Automation Hybrid Runbook Workers can run on Linux, and provide any relevant prerequisites or differences.
  • Include sample runbooks or scripts that work on Linux, or explain how to adapt the provided PowerShell scripts for Linux environments (e.g., using PowerShell Core on Linux or bash scripts).
  • Clarify in the prerequisites and steps where instructions diverge for Windows vs. Linux, and offer both sets of instructions side by side.
  • Avoid assuming the use of Windows tools (like PowerShell) exclusively; reference cross-platform tools or provide alternatives.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/whats-new.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page for Azure Automation updates demonstrates a Windows and PowerShell bias. Most examples and feature announcements focus on PowerShell runbooks, with PowerShell versions and modules (e.g., AzureRM, Az) being highlighted more frequently and in greater detail than their Linux or cross-platform equivalents. Python support is mentioned, but typically as a secondary note. There is a lack of explicit Linux shell (Bash) or native Linux automation examples, and Windows/PowerShell tools and terminology are often presented first or exclusively.
Recommendations:
  • Include explicit Bash or native Linux shell script examples and announcements alongside PowerShell updates.
  • When announcing new features (e.g., runtime environments, CLI support), provide parity in examples and explanations for both Windows/PowerShell and Linux/Bash users.
  • Highlight Linux-specific tools, modules, or best practices where relevant, not just Windows/PowerShell ones.
  • Ensure that migration and retirement notices (e.g., for modules or workers) address both Windows and Linux users equally, with clear guidance for each.
  • Balance the order of presentation so that Linux and cross-platform options are not always secondary to Windows/PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-orchestrator-migration.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page is heavily oriented toward Windows environments, focusing exclusively on PowerShell-based automation, Windows file paths, and Windows-specific tools and patterns. There are no examples or guidance for Linux users, nor any mention of Bash, Linux-compatible modules, or cross-platform considerations. All examples and tool references (such as the Runbook Converter and integration modules) assume a Windows environment.
Recommendations:
  • Provide examples for Linux users, such as using Bash or Azure CLI where possible.
  • Clarify whether the Runbook Converter and integration modules can be used on Linux or only on Windows, and provide alternatives or workarounds if not.
  • Include file path examples using Linux conventions (e.g., /home/user/runbooks) alongside Windows paths.
  • Mention any cross-platform compatibility or limitations for Azure Automation and related tools.
  • If PowerShell Core (pwsh) is supported, specify this and provide examples using it on Linux.
  • Add a section or note for Linux users outlining any differences or additional steps required.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/start-runbooks.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples use Windows PowerShell cmdlets, and there are no equivalent examples for Linux users (e.g., using Azure CLI, Bash, or cross-platform PowerShell Core). The term 'Windows PowerShell' is used explicitly, and the documentation does not mention or provide guidance for Linux-native tools or workflows. The structure and ordering of the content also present Windows/PowerShell methods before platform-neutral or Linux-friendly alternatives.
Recommendations:
  • Add equivalent Azure CLI examples for starting and managing runbooks, including parameter passing and job status retrieval.
  • Clarify that PowerShell Core (pwsh), which is cross-platform, can also be used, and provide examples where appropriate.
  • Avoid using 'Windows PowerShell' exclusively; refer to 'PowerShell' and specify when examples are compatible with both Windows and Linux.
  • Include a section or table row for Linux/macOS users, highlighting supported tools and methods (e.g., Azure CLI, REST API, PowerShell Core).
  • Ensure that all parameter handling examples are shown in both PowerShell and Azure CLI syntax.
  • Review terminology and ordering to avoid presenting Windows-specific tools and workflows before cross-platform or Linux-native options.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-manage-send-joblogs-log-analytics.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows/Powershell bias. It references PowerShell as the tool for viewing job logs outside the portal and discusses error streams in the context of PowerShell. There are no examples or mentions of Linux tools or command-line interfaces (such as Azure CLI, Bash, or Linux shell scripting) for interacting with Azure Automation logs. The documentation assumes familiarity with Windows-centric tools and patterns, and does not provide Linux-specific guidance or parity in examples.
Recommendations:
  • Include examples using Azure CLI for querying or managing Automation logs, alongside or instead of PowerShell.
  • Explicitly mention that the log querying and monitoring features are available and supported on Linux systems, not just Windows.
  • Provide sample scripts or command-line instructions for Linux users (e.g., Bash scripts, use of az CLI, or Kusto queries executed via CLI).
  • Clarify that runbooks can be authored and managed from Linux environments, and provide links or references to Linux-compatible tooling.
  • Avoid language that assumes PowerShell is the default or only way to interact with Azure Automation logs; present alternatives equally.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-webhooks.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a strong Windows and PowerShell bias. All code examples for creating, using, and managing webhooks are provided exclusively in PowerShell, with no equivalent examples for Bash, curl, or other common Linux tooling. Even REST API usage is shown via PowerShell's Invoke-RestMethod. There are no references to Linux command-line tools, and the workflow assumes a Windows/PowerShell environment throughout. This limits accessibility for Linux users and those working in cross-platform environments.
Recommendations:
  • Provide equivalent examples using Bash and curl for all webhook operations (creation, invocation, deletion, etc.).
  • Show how to authenticate and interact with Azure using Azure CLI (az) commands, not just PowerShell Az module.
  • For REST API sections, include examples using curl or httpie, not only PowerShell's Invoke-RestMethod.
  • When presenting multiple approaches, do not always list PowerShell first; alternate or present both together.
  • Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux users.
  • Where possible, include notes or troubleshooting tips relevant to Linux environments (e.g., file path formats, authentication differences).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-security-guidelines.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by consistently referencing Windows-specific instructions and tools (such as the Hybrid Runbook Worker VM extension with '?tabs=windows'), and omitting Linux-specific examples or guidance. All links and examples for installing or managing Hybrid Runbook Workers default to Windows, with no mention of Linux equivalents or cross-platform considerations. This may lead Linux users to feel unsupported or unclear about best practices for their environments.
Recommendations:
  • Provide explicit Linux-specific instructions and examples alongside Windows ones, especially for installing and managing Hybrid Runbook Workers.
  • Ensure all links that currently default to '?tabs=windows' also reference or highlight the Linux tab or equivalent documentation.
  • Mention Linux tools, patterns, and security considerations where relevant, such as differences in permissions, authentication, or network isolation on Linux systems.
  • Add a section or callout clarifying cross-platform support and any differences in implementation or security best practices between Windows and Linux environments.
  • Review all examples and ensure parity by including both PowerShell (Windows) and Bash/Shell (Linux) script examples where automation or scripting is discussed.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/manage-runbooks.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily biased towards Windows and PowerShell usage. All code examples are in PowerShell, with no Bash, CLI, or Linux-native scripting examples. File paths and script types referenced (e.g., .ps1, C:\Runbooks\) are Windows-centric. There is no mention of Linux shell scripting, Azure CLI, or cross-platform automation tools. The documentation assumes the user is operating from a Windows environment and using PowerShell, omitting guidance for Linux users.
Recommendations:
  • Provide equivalent examples using Azure CLI (az) commands for each PowerShell example, especially for creating, importing, publishing, and managing runbooks.
  • Include Bash shell script examples and reference Linux file paths (e.g., /home/user/Runbooks/) alongside Windows paths.
  • Explicitly mention and demonstrate how to use runbooks authored in Python or Bash, not just PowerShell.
  • Clarify which features and procedures are available or different on Linux-based Hybrid Runbook Workers.
  • Add a section or callouts for Linux/macOS users, including prerequisites and environment setup.
  • Ensure that references to tools and patterns (such as credential management, file import, and job status retrieval) include both PowerShell and cross-platform alternatives.
  • Review and update terminology to avoid assuming a Windows-only environment (e.g., avoid only referencing .ps1 files and C:\ paths).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/change-tracking/change-tracking-data-collection-rule-creation.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by prioritizing Windows-specific settings and examples. The JSON script heavily details Windows registry paths and file settings, while Linux settings are less detailed and lack equivalent examples. The only reference example for file settings is for Windows paths, with no Linux file path example provided. Windows-specific tools and patterns (e.g., registry keys, Windows directory paths) are mentioned exclusively, and Windows is consistently presented before Linux.
Recommendations:
  • Provide equivalent Linux file settings examples alongside Windows examples, such as a JSON snippet for tracking files in typical Linux directories (e.g., /var/log/* or /etc/*).
  • Include more detailed Linux-specific configuration options, similar to the depth given for Windows registry and file settings.
  • When listing both Windows and Linux extensions or settings, present them in parallel or alternate the order to avoid always listing Windows first.
  • Add explanatory notes or tables comparing Windows and Linux settings, highlighting differences and similarities.
  • Ensure that all examples and reference sections include both Windows and Linux use cases to achieve parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/create-azure-automation-account-terraform.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation presents both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell tab is given equal prominence and is referenced in the 'Next steps' section. The final recommended tutorial specifically focuses on creating a PowerShell runbook, reinforcing a Windows-centric workflow. There are no explicit Linux shell examples or mentions of Linux-specific tools, but the CLI examples are cross-platform. However, the emphasis on PowerShell in both verification and next steps introduces a subtle Windows bias.
Recommendations:
  • Include explicit Bash/Linux shell examples where appropriate, especially in verification steps.
  • In the 'Next steps' section, provide a parallel tutorial for creating a Python or Bash runbook, not just PowerShell.
  • Clarify that Azure CLI commands work cross-platform and highlight this fact for Linux/macOS users.
  • If referencing PowerShell, also mention that PowerShell Core is cross-platform, or provide guidance for Linux users.
  • Consider adding a section or note on how to use the Automation account with non-Windows runbooks (e.g., Python, Bash).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-scenario-aws-deployment.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation exclusively uses PowerShell and Windows-centric tooling (such as PowerShell ISE and the AWSPowerShell module) for all examples and instructions. There are no references to Linux-native tools, Bash scripting, or cross-platform alternatives such as AWS CLI or Python. The workflow assumes a Windows environment and does not provide parity for Linux users, omitting any Linux shell or cross-platform scripting guidance.
Recommendations:
  • Provide equivalent examples using AWS CLI commands in Bash scripts, which can be run on Linux or macOS Automation Hybrid Workers.
  • Include instructions for importing and using the AWS Tools for PowerShell Core, which is cross-platform, or clarify if only Windows PowerShell is supported.
  • Add a section or callout for Linux/macOS users, describing how to author and execute runbooks using Python or Bash, and how to install necessary modules or packages.
  • Mention and demonstrate the use of cross-platform editors (such as VS Code) instead of PowerShell ISE, which is Windows-only.
  • Clarify any platform limitations in prerequisites, and provide links to Azure Automation documentation for Linux Hybrid Workers.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/disable-managed-identity-for-automation.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation page provides only PowerShell-based examples for disabling a system-assigned managed identity via the REST API, with no equivalent examples for Linux or cross-platform tools (such as Azure CLI or curl). The scripting and authentication steps are tailored to Windows environments and PowerShell users, and there is no mention of Linux-native workflows or tools.
Recommendations:
  • Add equivalent Azure CLI examples for authentication and sending the PATCH request, which work cross-platform (Windows, Linux, macOS).
  • Provide a curl example for sending the REST API request, including details on how to obtain an access token using Azure CLI (az account get-access-token).
  • Explicitly mention that the PowerShell example is Windows-centric and offer alternative instructions for Linux/macOS users.
  • Consider reordering or parallelizing the examples so that Windows and Linux instructions are presented together, or at least ensure Linux examples are not omitted.
  • Reference relevant documentation for Linux users, such as Azure CLI authentication and REST API invocation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/graphical-runbook-sdk.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation is heavily oriented toward Windows and PowerShell, with all examples and terminology referencing PowerShell commands, workflows, and Windows-centric assemblies. There are no Linux or cross-platform scripting examples, nor is there mention of Bash, Python, or other non-Windows automation tools. The SDK and activities are described exclusively in terms of PowerShell, and the prerequisites and workflows assume a Windows environment.
Recommendations:
  • Add explicit statements about platform support, clarifying whether the SDK and graphical runbooks can be authored or executed on Linux/macOS environments.
  • If supported, provide equivalent examples using Bash, Python, or other cross-platform scripting languages.
  • Mention any Linux-compatible tools or workflows, or clearly state if the SDK is Windows-only.
  • Include guidance for Linux users on how to interact with Azure Automation graphical runbooks, or provide alternative automation options for non-Windows environments.
  • Reorder explanations and examples to avoid always presenting Windows/PowerShell first, or provide parallel examples for other platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/manage-office-365.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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. There is an explicit note that the Microsoft Graph PowerShell module cmdlets must be run from Windows PowerShell, and no Linux or cross-platform alternatives are provided. The use of Windows-specific tools and patterns (such as Send-MailMessage and credential assets for PowerShell) further reinforces the Windows bias. There are no Bash, Azure CLI, or PowerShell Core examples, nor any mention of how to perform these tasks on Linux or macOS.
Recommendations:
  • Provide equivalent examples using PowerShell Core (pwsh), which is cross-platform, and clarify which cmdlets are supported.
  • Include Azure CLI examples for authentication and management where possible, as Azure CLI is cross-platform.
  • Explicitly state platform limitations and suggest workarounds or alternatives for Linux/macOS users.
  • Highlight any Office 365 or Azure Automation features that are not available on non-Windows platforms.
  • Where Windows PowerShell is required, suggest using cloud-based automation (e.g., Azure Automation runbooks) that abstracts away the local OS, and clarify that local scripting on Linux/macOS is not supported for these features.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/migrate-run-as-accounts-managed-identity.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation is heavily focused on PowerShell-based automation, with all code samples and instructions using PowerShell cmdlets and modules (Az, AzureRM), which are most commonly used in Windows environments. There are no examples or guidance for using other scripting languages or tools (such as Python, Bash, or CLI), nor is there mention of Linux-native automation patterns. The documentation assumes the use of the Azure portal UI, which is platform-agnostic but often associated with Windows workflows. Linux or cross-platform automation scenarios are not addressed.
Recommendations:
  • Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used in Linux environments.
  • Include sample scripts in Bash or Python for authenticating with managed identities in Azure Automation, especially for hybrid runbook workers running on Linux.
  • Explicitly mention support for Linux-based hybrid runbook workers and provide migration steps or code samples for those environments.
  • Clarify that managed identities and Azure Automation are supported on both Windows and Linux, and link to relevant Linux documentation.
  • Balance the order of presentation by including Linux or cross-platform examples alongside or before PowerShell/Windows examples.
  • Reference Linux tools (such as cloud-init, systemd, or cron) where relevant for automation scenarios.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/disable-local-authentication.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-AzAutomationAccount, Set-AzAutomationAccount) for checking and modifying the local authentication setting. There are no CLI, Bash, or Linux-native examples provided, nor are cross-platform tools like Azure CLI mentioned. The documentation assumes familiarity with Windows tooling and does not offer Linux-equivalent commands or workflows.
Recommendations:
  • Add Azure CLI examples (e.g., using 'az automation account show/update') alongside PowerShell cmdlets for all operations.
  • Include REST API curl examples for Linux users, especially since the note mentions REST API usage.
  • Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux administrators.
  • Reorder examples or present them in parallel (PowerShell and CLI) to avoid Windows-first bias.
  • Reference Linux-native tools or scripting environments where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-output-and-messages.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page exhibits a strong Windows/PowerShell bias. All code samples, explanations, and tool references are exclusively for Windows PowerShell and related cmdlets. There is no mention of Linux, Bash, or cross-platform scripting, nor are there examples or guidance for users running Azure Automation from non-Windows environments. The documentation assumes the reader is using PowerShell and Windows-centric tools, and Linux or cross-platform users are not addressed.
Recommendations:
  • Add equivalent examples for Python runbooks, which are supported in Azure Automation, especially in sections discussing output and message streams.
  • Include information and examples for retrieving runbook output and messages using Azure CLI (az command), which is cross-platform and widely used on Linux.
  • Clarify which features and cmdlets are available or behave differently in Linux Hybrid Runbook Workers or in cross-platform environments.
  • Where PowerShell preference variables or cmdlets are discussed, note their applicability (or lack thereof) in Python or other supported runbook types.
  • Provide links to documentation or guides for managing Azure Automation from Linux environments, and mention any limitations or differences.
  • Rephrase sections that refer to 'Windows PowerShell' to 'PowerShell', and clarify when instructions apply to Windows-only versus cross-platform PowerShell Core.
  • Explicitly state if certain features (such as graphical runbooks or specific cmdlets) are only available on Windows, and suggest alternatives for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-services.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation exhibits a Windows bias, primarily through a heavy emphasis on PowerShell-based automation, repeated references to Windows-centric tools and scenarios (e.g., Active Directory, SQL Server, registry changes), and by mentioning Windows/PowerShell approaches before Linux or cross-platform alternatives. While Linux is mentioned in passing (e.g., 'Linux and Windows support' in Automanage), there is a lack of Linux-specific examples, tools, or guidance, and the documentation assumes familiarity with Windows administration patterns.
Recommendations:
  • Provide Linux-specific examples and scenarios alongside Windows/PowerShell ones, such as using Bash scripts, Linux configuration management (e.g., Ansible, Chef, or native Azure DSC for Linux), and Linux-based monitoring.
  • Explicitly mention and demonstrate how Azure Automation and related services can be used with Linux VMs, including common Linux administrative tasks (e.g., package management, log rotation, cron jobs).
  • Balance references to PowerShell with equivalent Python or Bash scripting examples, and clarify cross-platform capabilities where applicable.
  • Include Linux-native tools and patterns (e.g., systemd, journald, apt/yum/zypper) in automation scenarios.
  • Highlight any differences or additional steps required for Linux environments, especially in areas like update management, configuration drift, and hybrid automation.
  • Ensure that tables and scenario descriptions do not assume Windows as the default, and use neutral or inclusive language (e.g., 'servers' instead of 'Windows servers').
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-child-runbooks.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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 (such as Start-AzAutomationRunbook, Disable-AzContextAutosave, Connect-AzAccount), and there is no mention or example of using Python or other runbook types supported by Azure Automation (such as Python runbooks, which are commonly used on Linux). The terminology and instructions assume a Windows/PowerShell environment, and there are no Linux/bash equivalents or guidance for non-Windows users.
Recommendations:
  • Add equivalent examples for Python runbooks, which are supported in Azure Automation and commonly used in Linux environments.
  • Include bash/CLI examples where possible, or at least mention how Linux users can achieve similar functionality.
  • Explicitly state the platform support and limitations for each approach (e.g., which features are PowerShell-only, which are cross-platform).
  • Reorganize sections to avoid always presenting Windows/PowerShell approaches first; consider parallel presentation of PowerShell and Python/bash examples.
  • Reference Azure CLI or REST API alternatives for starting and managing runbooks, which are platform-agnostic.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-config-aws-account.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by referencing AWS credential management via a link to the AWS PowerShell documentation, without mentioning or linking to equivalent Linux/CLI or SDK methods. There are no Linux-specific examples or references to cross-platform tools for credential management or automation, and the only external guidance provided is for PowerShell users.
Recommendations:
  • Include references and links to AWS CLI documentation for credential management, not just PowerShell.
  • Provide examples for storing and using AWS credentials in Automation runbooks using both PowerShell and Python (or other cross-platform languages).
  • Mention and link to Linux/macOS compatible tools and workflows for AWS credential management.
  • Ensure that all example commands and workflows are presented in both Windows (PowerShell) and Linux (Bash/CLI) formats where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/disable-managed-identity-for-automation.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation provides only PowerShell-based examples for interacting with the Azure REST API, with no equivalent examples for Linux or cross-platform tools such as Azure CLI or curl. The workflow assumes the use of Windows tools and patterns (e.g., PowerShell cmdlets, Windows file paths), and does not mention or prioritize Linux or cross-platform alternatives.
Recommendations:
  • Add equivalent examples using Azure CLI and/or curl for sending the PATCH request, suitable for Linux/macOS users.
  • Include bash shell scripting examples alongside PowerShell to ensure parity.
  • Use platform-neutral file path examples or clarify paths for both Windows and Linux.
  • Mention both PowerShell and CLI/curl options in the introduction to REST API usage, rather than focusing solely on PowerShell.
  • Ensure that authentication steps are described for both PowerShell and Azure CLI (e.g., az login).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-use-azure-ad.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily biased towards Windows and PowerShell environments. All examples, prerequisites, and instructions are specific to Windows (e.g., requiring Windows Management Framework, .NET Framework, and Windows PowerShell). There is no mention of Linux, macOS, or cross-platform PowerShell Core support. Installation and usage steps assume a Windows OS, and no Bash, CLI, or cross-platform alternatives are provided.
Recommendations:
  • Add equivalent instructions and examples for Linux and macOS environments, including how to use PowerShell Core (pwsh) and the Azure CLI.
  • Clarify which steps are Windows-specific and provide alternative steps for non-Windows users (e.g., installing modules on Linux/macOS, using dotnet instead of .NET Framework).
  • Include Bash/Azure CLI examples for authentication and automation tasks, not just PowerShell.
  • Mention cross-platform compatibility of the Az module and how to use it in non-Windows environments.
  • Explicitly state OS requirements and provide links to relevant installation guides for Linux/macOS.
  • Where Windows tools (e.g., Sign-in Assistant, WMF) are required, note their absence or alternatives on other platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-connections.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples for creating and managing connections use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux-native tools. The 'Create a new connection' section provides only a Windows PowerShell example, and the PowerShell tab appears before the Python tab in code samples. There is no guidance for users working from Linux or macOS environments, nor are cross-platform command-line alternatives (such as Azure CLI) presented.
Recommendations:
  • Add equivalent Azure CLI examples for creating and managing Automation connections, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include explicit instructions or notes for users on Linux/macOS, clarifying how they can perform the same tasks without PowerShell.
  • Reorder or parallelize example sections so that PowerShell and Python (or CLI) examples are presented side-by-side, or at least do not always lead with Windows/PowerShell.
  • Mention and link to any relevant Linux tools or scripts that can interact with Azure Automation, if available.
  • Clarify in the introduction that the documented PowerShell cmdlets are available cross-platform (if true), or specify platform limitations.
  • Where GUI steps are described, note any differences or limitations for users accessing the Azure portal from non-Windows systems.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/compose-configurationwithcompositeresources.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation is heavily focused on PowerShell DSC, with all examples and terminology centered around Windows-centric tools and patterns. There are no Linux-specific examples or mentions of Linux equivalents, and the only reference to Linux is an announcement about retirement, not usage or configuration.
Recommendations:
  • Provide examples or references for composing configurations with Linux nodes, if still supported.
  • Include Linux-native configuration management tools or patterns where applicable, or clarify the lack of support.
  • Balance references to PowerShell and Windows tools with equivalent Linux tools or workflows, or clearly state platform limitations.
  • If Linux support is deprecated, make this explicit at the beginning and suggest alternative solutions for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/context-switching.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page is heavily focused on Azure PowerShell cmdlets and Windows-centric tooling, with all examples and recommendations provided exclusively in PowerShell. There is no mention of Linux-native tools, Bash, or cross-platform scripting approaches. The guidance assumes the use of PowerShell and does not address how context switching or runbook management would be handled in Linux environments or with other automation languages supported by Azure Automation.
Recommendations:
  • Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used in Linux environments.
  • Include Bash or Python runbook examples to demonstrate context management outside of PowerShell.
  • Explicitly mention that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical, etc.) and clarify if context switching issues are unique to PowerShell or apply to other languages.
  • Reorganize sections to present cross-platform solutions first or in parallel, rather than focusing solely on Windows/PowerShell.
  • Reference Linux tools or patterns where appropriate, and ensure troubleshooting steps and error messages are relevant to both Windows and Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/add-user-assigned-identity.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a strong Windows bias by providing only PowerShell-based CLI examples for all command-line operations, including REST API calls, ARM template deployment, and role assignments. There are no examples using Bash, Azure CLI (az), or Linux-native tools. File paths use Windows-style backslashes, and all scripting assumes a PowerShell environment. The only non-PowerShell code sample is a Python runbook, but even this relies on environment variables typically set in Azure Automation, not on Linux shell usage. There are no explicit instructions or examples for Linux users or those using Bash or Azure CLI.
Recommendations:
  • Add equivalent examples using Azure CLI (az) commands for all PowerShell examples, especially for adding managed identities, assigning roles, and deploying ARM templates.
  • Provide Bash shell script examples for REST API calls using curl or httpie, including authentication steps for Linux environments.
  • Use platform-neutral file path syntax (forward slashes or mention both styles) when referring to file locations.
  • Explicitly mention that all PowerShell examples can be run on PowerShell Core on Linux, or provide alternative commands for Bash users.
  • Include a section or callouts for Linux/macOS users, highlighting any differences or additional steps required.
  • When listing options (e.g., portal, PowerShell, REST API, ARM template), present Azure CLI and Bash examples alongside or before PowerShell to avoid 'windows_first' ordering.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-create-standalone-account.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by providing PowerShell examples exclusively, referencing PowerShell runbooks and cmdlets as the primary automation method, and omitting equivalent CLI or Linux-native instructions. The 'Next steps' section prioritizes PowerShell tutorials and references, with only a single Python runbook tutorial mentioned. There are no examples or instructions for using Azure CLI, Bash, or Linux-native tools to perform the same tasks, nor is there guidance for users on non-Windows platforms.
Recommendations:
  • Add equivalent Azure CLI (az) command examples for all PowerShell cmdlet instructions, especially for key management and account creation.
  • Include Bash shell examples where appropriate, particularly for Linux/macOS users.
  • Balance the 'Next steps' section by providing links to both PowerShell and Azure CLI tutorials, as well as Python and other cross-platform runbook types.
  • Explicitly state that all steps can be performed from any OS via the Azure portal, and clarify any OS-specific requirements.
  • Reference cross-platform tools (e.g., Azure CLI, REST API) alongside PowerShell, and avoid assuming PowerShell as the default automation tool.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-disaster-recovery.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page exhibits a strong bias towards Windows and PowerShell. All migration scripts and runbook examples are provided exclusively in PowerShell, with no mention of Bash, Python, or other Linux-native scripting options. The instructions for Hybrid Runbook Worker installation and migration consistently link to Windows-first tabs or examples, and there is no step-by-step guidance or code samples tailored for Linux users. The documentation assumes PowerShell as the default automation tool, which may not be familiar or preferred by Linux administrators.
Recommendations:
  • Provide equivalent migration scripts and runbook examples in Bash and/or Python, and document how to execute them on Linux-based Automation accounts.
  • Include explicit Linux/Unix instructions and screenshots alongside Windows/PowerShell examples, ensuring parity in all step-by-step guides.
  • When referencing installation or configuration steps for Hybrid Runbook Workers, ensure both Windows and Linux tabs are present and that Linux is not secondary or omitted.
  • Mention and, where possible, demonstrate the use of cross-platform tools (such as Azure CLI or REST API) for asset migration and automation tasks.
  • Clarify any limitations or differences for Linux users, and provide workarounds or alternatives where PowerShell is not available or preferred.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-create-alert-triggered-runbook.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. All code examples, instructions, and prerequisites are written for PowerShell, with no mention of Linux, Bash, or cross-platform alternatives. The only VM creation link points to a Windows VM via PowerShell, and there are no references to Linux VMs or Bash/Azure CLI usage. This creates a strong Windows bias and may alienate users working in Linux or cross-platform environments.
Recommendations:
  • Provide equivalent examples using Azure CLI (az) and Bash scripts, especially for steps like assigning permissions, creating runbooks, and managing VMs.
  • Include links to both Windows and Linux VM quickstart guides, not just Windows/PowerShell.
  • When listing prerequisites, mention both PowerShell and Azure CLI as supported options.
  • Show how to create and trigger runbooks using Bash or Azure CLI, not just PowerShell.
  • Add a section or callouts for Linux users, clarifying any differences or additional steps.
  • Ensure that runbook examples are language-agnostic where possible, or provide both PowerShell and Python (or Bash) samples.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-compile.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily focused on Windows and PowerShell-based workflows for compiling DSC configurations in Azure Automation. All code examples use Windows PowerShell, and Windows-centric tools and paths (e.g., C:\, WindowsFeature) are referenced exclusively. There are no examples or instructions for compiling DSC configurations from Linux or using cross-platform tools. The documentation also refers to Windows PowerShell as the primary or only scripting environment, and does not mention Linux equivalents or alternatives.
Recommendations:
  • Add examples and instructions for compiling DSC configurations from Linux environments, using cross-platform PowerShell (pwsh) where possible.
  • Clarify which steps and cmdlets are supported on Linux and which are Windows-only.
  • Provide Linux file path examples (e.g., /home/user/configs) alongside Windows paths.
  • Mention any limitations or differences for Linux users up front, especially in sections where only Windows is supported.
  • If Linux support is deprecated or limited (as suggested by the Linux retirement announcement), make this explicit and provide guidance or alternatives for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-cd-chocolatey.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily biased towards Windows environments. All examples, tooling, and workflows are specific to Windows, PowerShell, and Windows-centric package management (Chocolatey, DSC). Linux is only mentioned in passing, and no Linux equivalents or examples are provided. The documentation assumes the user is deploying to Windows VMs and using Windows-specific tools, with no guidance for Linux users.
Recommendations:
  • Provide equivalent Linux examples using native Linux package managers (e.g., apt, yum) and configuration management tools (e.g., Ansible, Chef, Puppet, or Azure Automation State Configuration for Linux if available).
  • Include a section or parallel workflow for setting up continuous deployment for Linux VMs, including scripts and configuration files.
  • Mention and demonstrate cross-platform tools and approaches where possible, or explicitly state the Windows-only scope at the beginning.
  • If Azure Automation State Configuration for Linux is deprecated or unavailable, provide clear alternatives or migration guidance for Linux users.
  • Balance the mention of package managers by giving Linux tools equal prominence and not relegating them to a single sentence.
  • Where PowerShell is used, provide Bash or shell script equivalents for Linux scenarios.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-configuration-based-on-stig.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily focused on Windows and PowerShell, referencing only Windows PowerShell 5.1, PowerShell DSC, and the PowerSTIG project (which is Windows-centric). There are no examples or guidance for Linux systems, and Linux onboarding is only mentioned in a link reference, not in the main content. All tools and patterns discussed are Windows-specific, and Linux equivalents or cross-platform approaches are missing.
Recommendations:
  • Add explicit Linux examples for configuring STIG compliance with Azure Automation State Configuration.
  • Discuss or reference Linux-native tools or DSC resources (such as nx or xDSC resources) where applicable.
  • Clarify whether PowerSTIG or similar community projects exist for Linux, or provide guidance for Linux users.
  • Balance the 'Next steps' section with links and explanations relevant to Linux DSC usage.
  • State up front whether the guidance is Windows-only, or provide parity for Linux users where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-config-data-at-scale.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily focused on Windows and PowerShell, with all examples and instructions referencing Windows PowerShell DSC and related tooling. Linux is only mentioned in passing (e.g., onboarding Linux machines), with no Linux-specific examples, tools, or guidance provided. The documentation assumes familiarity with Windows-centric tools and workflows, and does not address Linux-native equivalents or cross-platform usage.
Recommendations:
  • Provide explicit Linux examples for configuring data at scale, including how to use Datum or similar tools on Linux systems.
  • Include instructions for using cross-platform PowerShell (PowerShell Core) and clarify any differences in behavior or support compared to Windows PowerShell 5.1.
  • Mention and link to Linux-native configuration management tools (such as Ansible, Chef, or native DSC for Linux) where appropriate, or clarify the scope if only Windows is supported.
  • Reorder or balance references so that Linux and Windows are treated equally, rather than Windows-first.
  • Add a section or callout for Linux users, detailing any prerequisites, limitations, or alternative workflows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-config-from-server.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily biased towards Windows environments, specifically PowerShell and Windows DSC tooling. All examples and references are for Windows PowerShell 5.1, with no mention of Linux equivalents or cross-platform DSC solutions. The tools and resources discussed (ReverseDSC, SharePointDSC) are Windows/PowerShell-centric, and there are no Linux-specific instructions or examples provided.
Recommendations:
  • Add equivalent instructions and examples for Linux systems, including how to extract configurations from Linux servers using cross-platform DSC tools.
  • Mention and link to cross-platform DSC resources, such as PowerShell 7+ and the Linux DSC agent.
  • Clarify in the introduction that the current solution is Windows-specific, and provide guidance or alternatives for Linux users.
  • Include examples or references for managing configurations on Linux servers, not just Windows/SharePoint.
  • Balance the documentation structure so that Linux and Windows scenarios are presented with equal prominence where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-create-composite.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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 is no mention of Linux equivalents, cross-platform PowerShell (PowerShell Core), or how to perform similar tasks on Linux systems. Windows tools and patterns (such as MOF files, PowerShellGet, and Windows-specific DSC resources) are referenced exclusively, and Linux scenarios are not addressed.
Recommendations:
  • Add explicit guidance for using PowerShell DSC and composite resources on Linux, including any differences in configuration or supported features.
  • Include examples using PowerShell Core (pwsh), which is cross-platform, and clarify when instructions are Windows-specific.
  • Reference and link to Linux onboarding and configuration documentation more prominently, not just as a secondary link.
  • Provide sample configurations and workflows for common Linux scenarios (e.g., managing Apache/Nginx, SSH, Linux firewall, etc.).
  • Clarify which features or modules are Windows-only and which are supported on Linux, and update the 'Applies to' section accordingly.
  • Mention and link to Linux DSC resources and community modules where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-extension-history.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First Powershell Heavy Windows Tools
Summary:
The documentation page exclusively covers Windows operating systems, PowerShell, and Windows Management Framework (WMF) in all version histories, features, and instructions. There is no mention of Linux support, examples, or parity, despite Azure DSC historically having some Linux support. All examples, troubleshooting, and references are Windows-centric, and the only tools and patterns discussed are Windows/PowerShell-specific.
Recommendations:
  • Explicitly state the current and historical support status for Linux in the introduction, including any retirement or deprecation notices.
  • If Linux support is retired, provide a clear summary and links to migration or alternative solutions for Linux users.
  • If any versions supported Linux, include those versions and their features in the version history table.
  • Add Linux-specific examples, troubleshooting steps, and references where applicable, or clarify their absence.
  • Where PowerShell or WMF is mentioned, note the equivalent (or lack thereof) for Linux, such as Open Management Infrastructure (OMI) or cross-platform DSC implementations.
  • Ensure that any future documentation updates maintain parity in describing both Windows and Linux support, or clearly state when features are Windows-only.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-getting-started.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy Windows Tools
Summary:
The documentation is heavily biased toward Windows environments. All configuration examples use Windows PowerShell DSC syntax and resources (e.g., WindowsFeature IIS), and the only VM creation instructions link to Windows VM guides. There are no Linux-specific examples, resources, or walkthroughs, and Linux support is only mentioned in passing or in deprecation notices. References and links are almost exclusively for Windows/PowerShell DSC, and no Linux equivalents or cross-platform DSC resources are provided.
Recommendations:
  • Add Linux-specific examples, such as a DSC configuration that manages a Linux package or service using the nx or cross-platform DSC resources.
  • Include instructions and links for creating and managing Linux VMs in Azure, alongside the Windows VM instructions.
  • Provide parity in walkthroughs for onboarding both Windows and Linux nodes to Azure Automation State Configuration.
  • Reference cross-platform DSC documentation and resources, not just Windows PowerShell DSC.
  • Clarify the current and future support status for Linux DSC in Azure Automation, and if deprecated, provide migration guidance or alternatives for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-diagnostics.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based instructions and examples, referencing Windows-centric tools (such as the Az PowerShell module and xDscDiagnostics), and omitting any Linux or cross-platform CLI alternatives. There are no Bash, Azure CLI, or Linux-native instructions, and the workflow assumes a PowerShell environment throughout. Additionally, the documentation references the retirement of Linux DSC support, but does not offer guidance for Linux users or alternatives.
Recommendations:
  • Add equivalent Azure CLI (az) command examples for all PowerShell instructions, as Azure CLI is cross-platform and works natively on Linux and macOS.
  • Explicitly state the platform requirements for the PowerShell examples, and provide guidance for Linux/macOS users (e.g., using PowerShell Core or Azure CLI).
  • Where possible, provide Bash script examples or note how Linux users can achieve the same results.
  • Clarify the impact of Linux DSC retirement and suggest supported alternatives or migration paths for Linux users.
  • Ensure that references to tools and modules (such as xDscDiagnostics) include notes on platform compatibility and alternatives for non-Windows environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by focusing heavily on PowerShell DSC, referencing Windows tools and patterns first, and providing detailed Windows OS/version support lists before Linux. Examples and references (such as Chocolatey and PowerShell cmdlets) are Windows-centric, and there are no Linux-specific usage examples or equivalent Linux tooling highlighted.
Recommendations:
  • Provide Linux-specific examples for onboarding, configuration, and troubleshooting, including sample commands and scripts.
  • List supported Linux distributions and versions explicitly, similar to the Windows OS list.
  • Highlight Linux-native configuration management tools or patterns where relevant, or clarify how PowerShell DSC for Linux integrates with typical Linux workflows.
  • Include Linux-focused continuous deployment pipeline examples (e.g., using apt, yum, or native package managers instead of Chocolatey).
  • Balance the order of presentation so that Linux and Windows are given equal prominence in prerequisites, examples, and feature descriptions.
  • Reference Linux command-line tools and scripting (e.g., Bash) where appropriate, alongside PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-remediate.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and cmdlet references for Windows VMs, while Linux remediation is described only in general terms without concrete script examples. Windows tools and workflows (PowerShell, Update-DscConfiguration) are highlighted first and in more detail, whereas Linux instructions are less actionable and defer to external documentation.
Recommendations:
  • Provide explicit Linux command-line examples (e.g., shell or Python scripts) for remediating drift, similar to the PowerShell example for Windows.
  • List Linux remediation steps before or alongside Windows steps to avoid a 'Windows-first' impression.
  • Reference and explain Linux-native tools or scripts directly in the documentation, not just via external links.
  • Include parity in detail and clarity for both platforms, ensuring Linux users have actionable, in-page guidance.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/manage-office-365.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily biased towards Windows and PowerShell. All examples and instructions are provided exclusively for Windows PowerShell, with explicit notes that PowerShell Core (cross-platform) is not supported. There are no examples or guidance for Linux or macOS users, and all tooling and workflow references assume a Windows environment.
Recommendations:
  • Provide equivalent instructions and examples for Linux/macOS environments, including how to use Azure Automation with PowerShell Core where possible.
  • Clarify which features are Windows-only and suggest alternatives or workarounds for non-Windows users.
  • Include notes or links to documentation for managing Office 365/Azure Automation from Linux/macOS, such as using Azure CLI, REST APIs, or cross-platform PowerShell modules.
  • If certain modules (like Microsoft Graph PowerShell) are not supported on PowerShell Core, explicitly state this and provide alternative approaches for Linux users.
  • Reorder sections or provide parallel instructions so that Windows and Linux users are equally supported and neither is prioritized over the other.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-onboarding.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a strong Windows and PowerShell bias. Most examples and workflows are described using PowerShell scripts and cmdlets, with Linux instructions often being secondary, less detailed, or requiring use of Windows tools (e.g., generating metaconfigurations on Windows). Windows-specific tools and terminology (WMF 5, PowerShell DSC, Set-DscLocalConfigurationManager) are used throughout, and Linux workflows are often described as adaptations of the Windows process. Linux-specific examples are minimal, and Linux users are frequently directed to use Windows-based tooling for key steps.
Recommendations:
  • Provide Linux-first and Linux-native examples for all major workflows, including onboarding, metaconfiguration generation, and status checking.
  • Document how to generate DSC metaconfigurations entirely on Linux, without requiring Windows or PowerShell.
  • Where possible, use cross-platform tools or clearly indicate platform-specific steps, offering parity in detail and clarity.
  • Include bash or Python scripts for Linux alongside PowerShell scripts for Windows.
  • Clarify when a feature or cmdlet is Windows-only, and offer Linux alternatives or workarounds.
  • Reorganize sections so that Linux and Windows instructions are presented with equal prominence and detail.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-edit-textual-runbook.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily focused on PowerShell and Windows workflows. All command-line examples use Windows PowerShell, with explicit references to Windows paths (e.g., c:\runbooks) and no mention of Linux or cross-platform PowerShell Core usage. There are no examples or instructions for editing runbooks from Linux or macOS environments, nor is there guidance for using PowerShell Core or Azure CLI as alternatives.
Recommendations:
  • Add equivalent examples using PowerShell Core (pwsh) on Linux/macOS, including Unix-style file paths (e.g., /home/user/runbooks).
  • Clarify that the Az PowerShell module and cmdlets can be used cross-platform, and provide instructions for installing and using them on Linux/macOS.
  • Include Azure CLI examples for exporting/importing runbooks, if supported, to provide a non-PowerShell alternative.
  • Avoid using 'Windows PowerShell' as the default term; use 'PowerShell' or specify when instructions apply to Windows-only environments.
  • Explicitly state platform compatibility for each method, and provide troubleshooting or caveats for non-Windows users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/delete-account.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell examples and references are presented before any mention of cross-platform tools, and there are no Linux-specific instructions or screenshots. The documentation assumes familiarity with Windows-centric tools and patterns, such as PowerShell cmdlets, and omits guidance for users on Linux or macOS platforms.
Recommendations:
  • Add Azure CLI examples alongside PowerShell for all command-line operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash shell command examples where appropriate, especially for unlinking or deleting resources.
  • Ensure that references to command-line tools do not assume a Windows environment; clarify that steps can be performed from any OS.
  • Where screenshots are used, consider including examples from both Windows and Linux environments if UI differences exist.
  • Reorder sections so that Azure CLI and PowerShell examples are presented together or in a neutral order, rather than PowerShell first.
  • Explicitly mention that all operations can be performed from Linux, macOS, or Windows, and provide any OS-specific caveats if needed.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-faq.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation generally maintains parity between Windows and Linux in most answers, but in the section about how a Hybrid Runbook Worker selects the Python interpreter, only the Windows process is described in detail with explicit examples (e.g., referencing C:\Python2\python.exe and environment variables). There is no equivalent explanation or example for Linux Hybrid Runbook Workers, leaving a gap in Linux-specific guidance.
Recommendations:
  • Add a parallel explanation for Linux Hybrid Runbook Workers in the section about Python interpreter selection, including which environment variables are checked (e.g., PYTHON_2_PATH, PYTHON_3_PATH) and typical Linux paths (e.g., /usr/bin/python3).
  • Provide Linux-specific examples alongside Windows examples when describing configuration or troubleshooting steps.
  • Review other sections for subtle Windows-first phrasing and ensure Linux is always mentioned equally where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/delete-run-as-account.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools
Summary:
The documentation focuses exclusively on deleting Azure Automation Run As accounts using PowerShell and the Azure portal, both of which are Windows-centric tools. There are no examples or instructions for performing the task using Linux-native tools, CLI, or scripts, nor is there mention of cross-platform alternatives such as Azure CLI or REST API.
Recommendations:
  • Add step-by-step instructions for deleting a Run As account using Azure CLI, which is cross-platform and widely used on Linux.
  • Include REST API examples for advanced users who may wish to automate the process from any OS.
  • Explicitly mention that the Azure portal and PowerShell examples are not limited to Windows, but provide parity by showing how to perform the same actions from Linux/macOS environments.
  • Where PowerShell is referenced, clarify if Azure PowerShell Core (cross-platform) can be used, or provide Bash equivalents.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-graphical-authoring-intro.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation is heavily focused on Windows PowerShell and PowerShell Workflow, with all examples, terminology, and tooling centered around PowerShell cmdlets and syntax. There is no mention of Linux-native scripting, Bash, or cross-platform considerations. The documentation assumes familiarity with Windows-based tools and patterns, and does not provide Linux or cross-platform alternatives or examples.
Recommendations:
  • Clarify early in the documentation that graphical runbooks in Azure Automation are currently limited to PowerShell and PowerShell Workflow, and explicitly state the lack of Bash or Linux-native scripting support.
  • If future support for Linux scripting or Bash is planned, add a roadmap or note to inform users.
  • Where possible, provide guidance for Linux users, such as how to author and manage runbooks that interact with Linux VMs or resources, even if the runbook language is PowerShell.
  • Include examples of managing Linux resources (e.g., using PowerShell cmdlets to interact with Linux VMs, run commands on Linux, or manage Linux-specific assets).
  • Reference cross-platform PowerShell (PowerShell Core) where applicable, and clarify any limitations or differences compared to Windows PowerShell.
  • Consider adding a section or FAQ addressing common Linux user questions, such as interoperability, prerequisites for managing Linux resources, and any platform-specific caveats.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-hybrid-runbook-worker.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a moderate Windows bias. PowerShell is the only scripting example provided for querying Hybrid Runbook Workers, with no equivalent Bash or Linux CLI example. When describing agent-based user Hybrid Runbook Worker deployment, Windows is mentioned before Linux, and the PowerShell-centric workflow is emphasized. References to system accounts and permissions also list Windows first, and the use of Windows-specific tools (PowerShell) is assumed for management tasks. Linux support is acknowledged, but practical examples and tool parity are lacking.
Recommendations:
  • Provide equivalent Bash or Azure CLI examples for Linux users wherever PowerShell scripts are shown.
  • When listing instructions or links for both Windows and Linux, alternate the order or present them together to avoid a 'Windows first' impression.
  • Include Linux-specific management guidance, such as using shell scripts or Linux-native tools, for querying and managing Hybrid Runbook Workers.
  • Clarify that both Windows and Linux are fully supported, and ensure all operational examples (scripts, permissions, troubleshooting) have Linux counterparts.
  • Highlight any differences or similarities in user accounts (e.g., System vs nxautomation) more equally, and provide explicit Linux instructions where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-manage-send-joblogs-log-analytics.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation page exhibits a mild Windows/Powershell bias. While the overall content is platform-neutral in its description of Azure Automation and Azure Monitor, it references PowerShell specifically when discussing error streams and job debugging. There are no explicit Linux or cross-platform CLI (e.g., Azure CLI, Bash) examples or mentions. The documentation does not provide Linux-specific guidance or alternative command-line workflows, and it assumes familiarity with PowerShell concepts and terminology.
Recommendations:
  • Add explicit references and examples for Linux users, such as using Azure CLI or Bash scripts to interact with Azure Automation and Azure Monitor logs.
  • When discussing job streams and error handling, mention how non-Windows runbooks (e.g., Python, Bash) handle errors and how their output appears in logs.
  • Where PowerShell is referenced, provide equivalent Azure CLI or REST API examples to ensure parity for Linux and macOS users.
  • Clarify that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical, etc.) and provide examples or links for each.
  • Include a section or note on how to access and query logs from Linux environments, possibly with sample Bash/Azure CLI commands.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-network-configuration.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by referencing Windows-specific DSC resources (such as WaitFor resources in the /powershell/dsc/reference/resources/windows/waitForAllResource link) without mentioning Linux equivalents or cross-platform alternatives. There are no Linux-specific examples or references, and the documentation assumes familiarity with Windows-centric tools and patterns.
Recommendations:
  • Include references to Linux DSC resources and provide equivalent Linux documentation links where Windows resources are mentioned.
  • Add explicit examples or notes for configuring network requirements on Linux-based Hybrid Runbook Workers and State Configuration nodes.
  • Clarify that the guidance applies to both Windows and Linux, and highlight any platform-specific differences in network configuration or tooling.
  • Where PowerShell or Windows-specific resources are referenced, provide parallel instructions or links for Linux environments (e.g., using OMSAgent or Linux DSC).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-orchestrator-migration.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily focused on Windows and PowerShell, with all examples and tooling instructions centered around Windows environments. PowerShell is presented as the default and only scripting language, and all file paths and command examples use Windows conventions. There is no mention of Linux or cross-platform alternatives, nor are there any examples or guidance for users working in Linux environments.
Recommendations:
  • Provide equivalent examples using Azure Automation Python runbooks or Bash scripts, where applicable.
  • Include instructions and examples for Linux users, such as using Azure CLI or Bash for automation tasks.
  • Clarify whether the migration tools and modules are supported or can be run on Linux/macOS, and provide installation steps for those platforms if possible.
  • Use neutral file path examples (e.g., /home/user/runbooks or $HOME/runbooks) alongside Windows paths.
  • Mention cross-platform PowerShell (PowerShell Core) and provide guidance for users running PowerShell on Linux or macOS.
  • Explicitly state any platform limitations or requirements for the migration toolkit and related modules.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-authoring.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows and PowerShell bias. Windows operating systems and PowerShell (especially Windows PowerShell 5.1) are mentioned first and most frequently. Directory path examples use Windows-style paths (e.g., C:\abc), and there are no Linux/macOS path examples. The documentation focuses on PowerShell runbooks and local debugging, with limited mention of Python and no Linux-specific instructions or examples. Linux and macOS are only briefly referenced in the supported OS list, with no parity in examples or troubleshooting.
Recommendations:
  • Provide Linux/macOS-specific examples for directory paths (e.g., /home/user/abc) alongside Windows examples.
  • Include instructions and screenshots for configuring the extension and running/debugging runbooks on Linux/macOS.
  • List supported operating systems in a neutral or rotating order, not always starting with Windows.
  • Expand Python runbook documentation, including debugging guidance for Linux/macOS users.
  • Clarify any OS-specific limitations or differences in feature support.
  • Ensure all command palette and settings navigation instructions are valid for Linux/macOS (e.g., keyboard shortcuts).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-execution.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. All code examples are in PowerShell, and references to modules, environment variables, and system paths are Windows-specific (e.g., $env:TEMP, C:\temp). Windows tools like WinSCP.exe and IIS are mentioned as module dependencies, with no Linux equivalents or examples provided. There is minimal mention of Linux or Bash scripting, and Linux-specific scenarios are not addressed, leading to a lack of parity for Linux users.
Recommendations:
  • Provide equivalent Bash or Python examples for common runbook tasks, especially for error handling and file operations.
  • Include Linux-specific guidance for Hybrid Runbook Workers, such as recommended temp directories (e.g., /tmp) and handling of permissions/elevation.
  • Mention Linux-compatible tools and modules (e.g., sftp, curl, Apache/Nginx) alongside Windows tools like WinSCP and IIS.
  • Clarify which features, modules, and cmdlets are supported on Linux Hybrid Runbook Workers, and document any differences.
  • Add a section or examples for authoring and running Python runbooks, which are supported in Azure Automation and are cross-platform.
  • Balance references to environment variables and file paths by including both Windows and Linux formats (e.g., $env:TEMP and /tmp).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-managing-data.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias in several ways: Windows-specific tools (PowerShell cmdlets) are referenced more frequently and prominently than Linux equivalents, and examples for backup/export tasks are provided only for Windows/PowerShell. In several sections, Windows instructions or tools are mentioned before Linux, and some Linux guidance is either less detailed or missing entirely.
Recommendations:
  • Provide Linux command-line examples (e.g., using Azure CLI or Bash scripts) alongside or before Windows/PowerShell examples for tasks like exporting runbooks, DSC configurations, and managing assets.
  • Include Linux-specific instructions for tasks such as enabling/disabling TLS protocols, not just a Python script but also relevant shell commands or configuration file edits.
  • Reference cross-platform tools (e.g., Azure CLI, REST API) wherever possible, rather than focusing on Windows PowerShell cmdlets.
  • Ensure that tables and lists do not always list Windows platforms first; alternate or group by platform type.
  • Add explicit Linux examples for asset management, backup, and recovery, not just for TLS configuration.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-role-based-access-control.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples for configuring Azure RBAC are provided exclusively using Azure PowerShell cmdlets, with no mention or examples of equivalent Azure CLI (cross-platform) commands. The only scripting language shown is PowerShell, which is primarily associated with Windows environments. There is no guidance or examples for Linux/macOS users, nor is there mention of using Azure CLI or REST API for role assignments. The structure and ordering of the documentation also present PowerShell before any other tooling, reinforcing a Windows-first approach.
Recommendations:
  • Add equivalent Azure CLI examples for all PowerShell cmdlets shown, especially for role assignment, listing, and removal.
  • Explicitly mention that Azure CLI and REST API can be used for these operations, and provide links or examples.
  • Where scripts are provided, offer both PowerShell and Bash (Azure CLI) versions side-by-side.
  • Clarify that PowerShell is available cross-platform, but also highlight the native experience for Linux/macOS users via Azure CLI.
  • Review all sections for implicit assumptions of a Windows environment and update language to be inclusive of Linux/macOS users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-gallery.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page is heavily focused on PowerShell and Windows-centric tools, with almost exclusive reference to the PowerShell Gallery, PowerShell modules, and Windows Azure VMs. There are no Linux-specific examples, tools, or workflows provided, and the only mention of Linux is in a tag suggestion. All example runbooks and scenarios are Windows/PowerShell oriented, and there is no parity in guidance for Linux automation or modules.
Recommendations:
  • Add equivalent examples and workflows for Linux automation, such as using Python runbooks or Bash scripts.
  • Include references to Linux Azure VMs and provide sample runbooks for managing Linux VMs (e.g., copying files to/from Linux VMs, managing Linux services).
  • Highlight cross-platform capabilities of Azure Automation, and clarify which features are Windows-only and which are available for Linux.
  • Provide parity in documentation structure: if PowerShell Gallery and modules are discussed, also discuss Python package sources or Bash script repositories where applicable.
  • Include at least one end-to-end example for Linux users, such as importing and running a Python runbook on a Linux VM.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-graphical-error-handling.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a strong Windows and PowerShell bias. All error handling concepts and examples are presented exclusively in terms of PowerShell cmdlets and Windows-centric tools (e.g., Write-Warning, Start-AzVM, Get-AutomationVariable). There is no mention of Linux runbooks, Bash, or cross-platform scripting. The terminology and examples assume the user is working in a Windows/PowerShell environment, with no Linux or cross-platform parity.
Recommendations:
  • Include examples and explanations for error handling in Linux-based runbooks, such as using Bash or Python activities.
  • Mention and demonstrate how error handling works in graphical runbooks that target Linux hybrid workers or use cross-platform scripting languages.
  • Provide equivalent Linux tool or command examples (e.g., using shell scripts or Python for error handling and notifications).
  • Clarify in the introduction that the guidance is PowerShell-specific, or restructure the documentation to present both Windows/PowerShell and Linux/Bash/Python approaches side by side.
  • Reference Azure Automation support for Linux hybrid workers and how error handling differs or is implemented in those scenarios.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-types.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by prioritizing PowerShell (a Windows-centric technology) in both order and depth of coverage, providing only PowerShell code examples (with Windows file paths), and referencing Windows-specific tools and environment variables. Linux support is mentioned but not illustrated with examples, and Linux-specific considerations are minimal or absent.
Recommendations:
  • Provide Linux-specific examples for PowerShell runbooks, including file paths and environment variables relevant to Linux (e.g., /home/user/modules instead of C:\modules).
  • Include explicit guidance and troubleshooting steps for running PowerShell and Python runbooks on Linux Hybrid Runbook Workers, not just Windows.
  • Balance the order of presentation so that Python and Linux scenarios are not always after PowerShell/Windows; consider parallel sections or tables.
  • Where Windows-specific tools or patterns are discussed (e.g., environment variables, file paths), provide Linux equivalents or note differences.
  • Add sample Python runbooks that demonstrate both Windows and Linux compatibility, and clarify any OS-specific limitations.
  • Highlight any differences in module/package management between Windows and Linux Hybrid Runbook Workers.
  • Explicitly state when a feature or limitation applies only to Windows, Linux, or both, to avoid ambiguity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-scenario-aws-deployment.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation exclusively uses PowerShell-based examples and workflows, referencing the AWS PowerShell module, PowerShell Gallery, and PowerShell ISE. There are no examples or instructions for using Linux-native tools (such as AWS CLI with Bash or Python scripts), nor is there mention of cross-platform scripting options. The documentation assumes a Windows-centric workflow and does not address Linux users or provide parity in tooling or examples.
Recommendations:
  • Provide equivalent instructions and examples using the AWS CLI in Bash or Python scripts for Linux users.
  • Include steps for importing and using AWS CLI modules in Azure Automation, highlighting cross-platform compatibility.
  • Mention and demonstrate how to author runbooks using Python or Bash, not just PowerShell.
  • Avoid referencing Windows-specific tools (e.g., PowerShell ISE) as the only option; suggest alternatives like VS Code or cloud-based editors.
  • Reorder sections or provide parallel instructions so that Linux and cross-platform options are presented alongside or before Windows-specific ones.
  • Explicitly state that Azure Automation supports multiple scripting languages and link to relevant documentation for non-PowerShell options.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-secure-asset-encryption.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples are provided exclusively using Azure PowerShell cmdlets, with no equivalent examples for Azure CLI, Bash, or other cross-platform tools. The PowerShell sections are always presented first and in detail, while Linux-native or cross-platform approaches are either omitted or only briefly mentioned (e.g., Azure CLI is only referenced in passing for revocation). The documentation assumes the user is familiar with PowerShell and Windows tooling, and there is no guidance for users working on Linux or macOS environments.
Recommendations:
  • Provide Azure CLI examples for all PowerShell command sequences, including creating and assigning managed identities, configuring Key Vault access policies, and updating Automation account encryption settings.
  • Include Bash shell script examples where appropriate, especially for REST API calls using curl.
  • Explicitly mention cross-platform compatibility and note any differences in behavior or prerequisites between Windows and Linux/macOS environments.
  • Reorganize sections to present PowerShell and CLI examples side-by-side, or clearly label them as 'Windows/PowerShell' and 'Linux/macOS/CLI' to improve discoverability for non-Windows users.
  • Expand the 'Revocation of access' section to include full Azure CLI command examples, not just a reference link.
  • Add a note early in the document clarifying that all operations can be performed from any OS using Azure CLI or REST, not just PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-scenario-using-watcher-task.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily oriented towards Windows environments, with exclusive use of PowerShell scripts, Windows-style file paths (e.g., D:\examplefiles), and instructions that assume the use of Windows tools and conventions. There are no examples or guidance for Linux-based Hybrid Runbook Workers, nor are Bash or Linux shell equivalents provided. The only method shown for creating test files is via PowerShell, and all directory references use Windows syntax.
Recommendations:
  • Include parallel Linux/Bash examples for all PowerShell commands, such as using 'touch' to create files.
  • Mention and show Linux file path formats (e.g., /home/user/examplefiles) alongside Windows paths.
  • Clarify that Hybrid Runbook Workers can run on Linux, and provide setup and usage instructions for Linux environments.
  • Ensure that documentation steps and screenshots are not exclusively Windows-centric; add Linux equivalents where applicable.
  • Reference both PowerShell and Bash (or other relevant shells) in runbook authoring and testing sections.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-security-guidelines.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows-first bias in its guidance for installing and managing Hybrid Runbook Workers. All referenced installation and management links explicitly use the 'windows' tab, and there is no mention of Linux equivalents or examples. The documentation refers to VM Contributor roles and domain controllers, which are more relevant to Windows environments, and does not provide parity for Linux-based automation scenarios.
Recommendations:
  • Include explicit instructions and examples for installing and managing Hybrid Runbook Workers on Linux machines, using the appropriate tabs and links.
  • Ensure that all referenced links (such as installation guides) provide both Windows and Linux options, and do not default to the Windows tab.
  • Mention Linux-specific security considerations (e.g., avoiding installation on critical Linux servers, using sudoers for least privilege) alongside Windows-specific advice.
  • Provide examples of runbook execution and authentication for both Windows and Linux Hybrid Workers.
  • Review all sections for references to Windows-only tools or concepts and add Linux equivalents where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/graphical-runbook-sdk.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation is heavily oriented toward Windows and PowerShell, with all examples and terminology referencing PowerShell commands, workflows, and concepts. There is no mention of Linux, Bash, or cross-platform scripting, and the SDK and its usage are described exclusively in the context of PowerShell and Windows-centric workflows.
Recommendations:
  • Explicitly state whether the SDK and graphical runbooks support Linux Hybrid Runbook Workers or cross-platform execution.
  • Provide examples or guidance for authoring graphical runbooks that invoke Bash scripts or Linux commands, if supported.
  • Clarify whether the .dll and SDK can be used on non-Windows platforms (e.g., via .NET Core/5/6+ on Linux/macOS), and provide instructions for those environments if possible.
  • If Linux is not supported, clearly state this limitation at the top of the documentation.
  • Include a table or section comparing Windows/PowerShell and Linux/Bash support for graphical runbooks, so users understand platform compatibility.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-security-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page exhibits a Windows bias by referencing PowerShell cmdlets as the primary method for automation, mentioning Azure Resource Manager and PowerShell together, and omitting equivalent Linux/CLI examples or tools. There is no mention of Bash, Azure CLI, or Linux-specific automation patterns. The language and examples assume a Windows-centric environment, with no guidance for users operating from Linux or cross-platform environments.
Recommendations:
  • Include equivalent examples using Azure CLI (az) commands alongside PowerShell cmdlets.
  • Explicitly mention that runbooks can be authored in Python or Bash, and provide examples for these languages.
  • Reference cross-platform tools and patterns, such as Bash scripting or Linux cron integration, where applicable.
  • Ensure that instructions for authentication and permissions are not tied exclusively to Windows tools or terminology.
  • Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
  • Review and update terminology to be platform-neutral (e.g., refer to 'command-line tools' instead of only 'PowerShell').
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-send-email.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily biased towards Windows and PowerShell. All code examples, setup instructions, and tool references are exclusively for PowerShell, with no mention of Bash, Azure CLI, or Linux-based approaches. Windows/PowerShell tools and patterns are presented as the default and only option, with no Linux or cross-platform alternatives provided.
Recommendations:
  • Provide equivalent examples using Azure CLI and Bash scripts for Linux users.
  • Mention that Azure Automation runbooks can also be authored in Python and provide a Python example for sending email via SendGrid.
  • Include instructions for installing and using the Azure CLI on Linux/macOS, and show how to perform prerequisite steps (e.g., Key Vault creation, secret management, role assignment) using CLI commands.
  • Clarify that the PowerShell examples work cross-platform (if true), or specify any platform limitations.
  • Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
  • Balance the order of presentation so that Windows/PowerShell and Linux/CLI approaches are given equal prominence.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-webhooks.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a strong Windows and PowerShell bias. All code examples for creating, invoking, and managing webhooks use PowerShell cmdlets or scripts, with no equivalent examples for Linux-native tools (such as Bash, curl, or Azure CLI). Even REST API examples are shown using PowerShell's Invoke-RestMethod. There are no Bash, curl, or Azure CLI examples, and the only scripting language shown for interacting with Azure Automation is PowerShell. This makes the documentation less accessible for Linux or cross-platform users.
Recommendations:
  • Add equivalent examples using Azure CLI for all PowerShell-based operations (creating, updating, deleting webhooks, invoking webhooks, retrieving job output, etc.).
  • Provide REST API examples using curl or HTTPie in Bash, not just PowerShell's Invoke-RestMethod.
  • Include sample scripts in Bash for preparing JSON payloads and invoking webhooks.
  • When showing code tabs, present Azure CLI or Bash/curl examples before or alongside PowerShell, not only after.
  • Explicitly mention cross-platform compatibility and provide guidance for Linux/macOS users.
  • Where possible, use neutral language (e.g., 'command line' instead of 'PowerShell prompt') and avoid assuming a Windows environment.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/enable-managed-identity-for-automation.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily biased toward Windows and PowerShell usage. All code examples for enabling and using managed identities (including REST API, ARM templates, authentication, and resource access) are provided exclusively in PowerShell, with only a single Python example (and no Bash/CLI/Linux shell examples). Windows tools and paths are referenced first or exclusively in several places, and Linux equivalents are either missing, less detailed, or mentioned after Windows. There are no Azure CLI, Bash, or Linux-native scripting examples for the main workflows, and the documentation assumes PowerShell as the default automation and scripting environment.
Recommendations:
  • Provide Azure CLI examples for all major workflows (enabling managed identity, assigning roles, authenticating, accessing resources) alongside PowerShell.
  • Include Bash/shell script examples for REST API calls and token retrieval, especially for Linux-based Automation accounts.
  • When referencing file paths or commands for both Windows and Linux Hybrid Runbook Workers, present them in parallel and with equal detail.
  • Add Python and/or Bash examples for accessing Azure Key Vault, SQL Database, and other resources using managed identity, not just PowerShell.
  • Avoid assuming PowerShell as the default; explicitly state when an example is PowerShell and offer alternatives for Linux users.
  • Where possible, use cross-platform tools (e.g., Azure CLI, REST via curl) in examples to ensure parity.
  • Review and update all sections to ensure Linux and cross-platform users can follow the documentation without needing to translate PowerShell to their environment.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/enforce-job-execution-hybrid-worker.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Azure CLI and Azure PowerShell examples for policy creation and assignment, but PowerShell examples are given equal prominence and detail as CLI, and PowerShell-specific guidance is included throughout. There are no Linux-specific command-line examples (e.g., Bash scripting), nor is there mention of Linux-native tooling or considerations for Linux users. The documentation assumes familiarity with PowerShell and does not clarify cross-platform support for the provided commands.
Recommendations:
  • Clarify that Azure CLI commands are fully cross-platform and can be run on Windows, macOS, and Linux, while PowerShell examples may require PowerShell Core for cross-platform compatibility.
  • Add explicit Bash shell examples for Linux users where appropriate, especially for file creation and command execution.
  • Note any differences in behavior or prerequisites when running commands on Linux versus Windows (e.g., file paths, authentication methods).
  • Consider reordering examples to present Azure CLI (cross-platform) before PowerShell, or clearly label both as equally supported.
  • Include a brief section or note about running these commands on Linux systems, including installation links for Azure CLI and PowerShell Core.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/extension-based-hybrid-runbook-worker-install.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a notable Windows bias. PowerShell is used as the primary scripting example throughout, including for Linux scenarios, rather than native Linux tools or shell scripts. Windows-specific tools, paths, and patterns (such as C:\ paths, Windows PowerShell, .NET Framework, and registry keys) are referenced frequently and often before or instead of Linux equivalents. The Bicep and ARM template examples are exclusively for Windows VMs, with no Linux VM deployment examples. Linux-specific guidance is minimal or absent in several sections, especially for automation and extension management.
Recommendations:
  • Provide native Linux shell (bash) examples for all automation and extension installation steps, especially where PowerShell is currently used for Linux.
  • Include Bicep and ARM template examples for deploying Hybrid Runbook Worker extensions to Linux VMs, not just Windows.
  • When listing requirements, tools, or commands, present Linux and Windows options side-by-side, or alternate which platform is shown first.
  • Reference Linux file paths, permissions, and troubleshooting steps wherever Windows equivalents are given (e.g., folder permissions, uninstall instructions, proxy settings).
  • Clarify when PowerShell Core is required on Linux, and provide installation and usage guidance for bash or Python where possible.
  • Expand troubleshooting and management sections to include Linux-specific issues, logs, and commands.
  • Ensure all code samples, especially in REST, CLI, and scripting, show both Windows and Linux extension types and relevant settings.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/manage-runbooks.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a strong Windows and PowerShell bias. All code examples are provided exclusively in PowerShell, with no Bash, Python, or cross-platform CLI equivalents. File paths and script references use Windows conventions (e.g., C:\Runbooks\), and there is no mention of Linux shell environments or tools. The documentation assumes the use of Windows tooling and patterns throughout, omitting guidance for Linux users or those preferring cross-platform automation approaches.
Recommendations:
  • Provide equivalent examples using Azure CLI (az), Bash, or Python where possible, especially for common tasks such as creating, importing, publishing, and retrieving runbooks.
  • Include Linux-friendly file path examples and clarify that runbooks can be authored and managed from Linux/macOS environments.
  • Mention and demonstrate cross-platform tools and workflows (e.g., using az CLI, REST API, or SDKs) alongside PowerShell.
  • Explicitly state platform requirements or limitations, and offer guidance for users working from Linux or macOS.
  • Balance the order of presentation so that Windows/PowerShell and Linux/CLI approaches are given equal prominence.
  • Add notes or links to resources for Linux users, such as how to install and use Azure CLI or Python SDK for automation tasks.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/manage-sql-server-in-automation.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a strong Windows and PowerShell bias. All automation and scripting examples use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux-native tools. Instructions for module installation and hybrid worker setup are PowerShell-specific, and there are no Linux or cross-platform alternatives provided. The documentation assumes a Windows-centric workflow throughout.
Recommendations:
  • Provide equivalent examples using Azure CLI (az) and Bash scripts for connecting and managing Azure SQL databases.
  • Include instructions for installing required modules or packages on Linux-based Hybrid Runbook Workers, not just via PowerShell.
  • Mention and demonstrate how to use Azure Automation with Python runbooks, which are supported and cross-platform.
  • Explicitly state cross-platform compatibility where applicable, and clarify any Windows-specific requirements.
  • Reorder or balance the presentation so that Linux and cross-platform methods are given equal prominence to PowerShell/Windows approaches.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/manage-runtime-environment.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First Missing Linux Example
Summary:
The documentation demonstrates a clear bias towards Windows and PowerShell environments. Most examples, especially for creating and managing runbooks and runtime environments, focus on PowerShell, with detailed steps and REST API payloads referencing PowerShell modules (e.g., Az PowerShell, Get-Module). Windows/PowerShell-specific packaging (.zip, PowerShell Gallery) is emphasized, while Linux/Python equivalents are only briefly mentioned or relegated to notes. There are no concrete Linux shell or Python-centric examples, and Windows tools and conventions are referenced before or instead of Linux alternatives.
Recommendations:
  • Provide equivalent, detailed examples for Python runbooks, including REST API payloads and portal workflows.
  • Include explicit Linux/Python packaging instructions and examples (e.g., using .whl files, pip, or Linux shell commands) alongside PowerShell/Windows instructions.
  • Balance the documentation by presenting Python/Linux options before or alongside PowerShell/Windows options, rather than as afterthoughts or notes.
  • Add screenshots and walkthroughs for Python runbooks and Linux-based runtime environments, not just PowerShell.
  • Reference Linux/Python package repositories (e.g., PyPI) and tools (e.g., pip) where appropriate, not just PowerShell Gallery.
  • Clarify when instructions or features are platform-specific, and provide parity where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/migrate-run-as-accounts-managed-identity.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation demonstrates a strong bias toward Windows and PowerShell environments. All code samples, migration steps, and runbook examples exclusively use PowerShell cmdlets and scripts, with no mention of Linux shell (Bash), Python, or cross-platform automation approaches. The documentation assumes the use of Windows-centric tools and workflows, such as PowerShell modules (Az, AzureRM), and does not provide equivalent guidance or examples for Linux-based Automation accounts or hybrid workers running on Linux. The order and language also assume PowerShell as the default, reinforcing a Windows-first perspective.
Recommendations:
  • Add equivalent examples using Azure CLI (az) and/or Python SDK for runbook authentication and resource management, demonstrating how to migrate from Run As accounts to managed identities in Linux-based runbooks.
  • Include sample scripts for Bash and Python runbooks, showing how to authenticate with managed identities and perform common automation tasks.
  • Explicitly mention support for Linux hybrid runbook workers, and provide migration guidance and troubleshooting steps specific to Linux environments.
  • Clarify in prerequisites and migration steps that both Windows and Linux runbook environments are supported, and link to platform-specific documentation where appropriate.
  • Balance the order of presentation so that cross-platform or Linux-native tools (e.g., Azure CLI, Python) are mentioned alongside or before PowerShell, to avoid reinforcing a Windows-first mindset.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a moderate Windows bias. PowerShell and Windows-centric tools (such as DSC) are mentioned more frequently and in greater detail than their Linux equivalents. PowerShell is referenced as the primary automation language, with only secondary mention of Python. The configuration management section focuses exclusively on PowerShell DSC, with no mention of Linux-native configuration management tools or approaches. Examples and scenarios often reference Windows-specific technologies (e.g., Active Directory, SQL Server, SharePoint) before or instead of Linux alternatives. There is a lack of explicit Linux-focused examples, tools, or guidance, despite claims of heterogeneous support.
Recommendations:
  • Provide equal prominence to Linux automation tools and scripting languages (e.g., Bash, Python) alongside PowerShell.
  • Include Linux-native configuration management options or clarify how DSC applies to Linux systems.
  • Add Linux-specific examples and scenarios, such as automating package management, service management, or configuration on Linux VMs.
  • Mention Linux equivalents to Windows technologies referenced (e.g., reference LDAP or Samba alongside Active Directory, PostgreSQL/MySQL alongside SQL Server).
  • Ensure that documentation for modules, galleries, and shared resources includes Linux-relevant content and examples.
  • Clarify any limitations or differences in feature support between Windows and Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/remove-user-assigned-identity.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a strong Windows/Powershell bias. All command-line examples use Powershell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tooling. Even REST API usage is shown via Powershell's Invoke-RestMethod, and variable paths use Windows-style backslashes. There are no Linux or cross-platform command-line examples, and Powershell is assumed as the default scripting environment throughout.
Recommendations:
  • Add equivalent Azure CLI examples for all operations, including authentication, resource modification, and verification.
  • Provide Bash shell examples for REST API calls using curl, including how to obtain an access token with Azure CLI.
  • Use platform-neutral variable naming and file path conventions, or show both Windows and Linux path styles.
  • Explicitly mention that Powershell examples are for Windows (and optionally for cross-platform Powershell Core), and provide Linux/macOS alternatives.
  • In sections where Powershell is used to verify results, also show how to do this with Azure CLI (e.g., az automation account show).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/python-3-packages.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation exhibits a Windows-first bias, particularly in the sections on preparing wheel files for Python 3.8, where only Windows instructions are provided initially and in more detail. PowerShell cmdlets are heavily featured for package management, with no equivalent CLI or bash examples for Linux users. Windows-specific terminology and tools are referenced before Linux equivalents, and Linux guidance is only provided for the Python 3.10 (preview) scenario. There are no Linux/CLI examples for managing packages, and the PowerShell-centric approach may alienate Linux users.
Recommendations:
  • Provide equivalent Linux (bash/CLI) instructions for preparing wheel files for Python 3.8, not just for Python 3.10.
  • Include Azure CLI examples for all package management tasks currently shown only with PowerShell cmdlets.
  • When describing architecture or platform requirements, mention both Windows and Linux environments together, rather than prioritizing Windows.
  • Add explicit Linux-based examples for Hybrid Runbook Worker scenarios, including how to prepare and upload packages from Linux.
  • Where possible, use cross-platform tools (e.g., Azure CLI, REST API) in examples, or provide both PowerShell and bash/CLI alternatives.
  • Review and balance screenshots and terminology to ensure Linux users are equally represented.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/python-packages.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates Windows bias by providing explicit instructions and command-line examples only for Windows environments (e.g., using Windows 64-bit machine and Windows-style pip invocation), while omitting equivalent Linux or cross-platform instructions. There are no Linux or macOS examples or notes, and Windows tools and paths are mentioned exclusively.
Recommendations:
  • Include Linux/macOS equivalents for all command-line instructions, such as pip usage and file paths.
  • Provide cross-platform guidance or clarify when steps are Windows-specific.
  • Add a note or section addressing how to perform the same tasks on Linux (e.g., using 'pip download' on Linux/Mac, and where to find the downloaded files).
  • Avoid using only Windows-style paths (e.g., C:\Python27\Scripts\pip2.7.exe); instead, show both Windows and Unix-style commands.
  • Mention any platform-specific requirements or differences explicitly to help non-Windows users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy Windows Tools
Summary:
The documentation demonstrates a Windows bias in several ways: Windows examples and tools (such as PowerShell and Windows-specific registry paths) are presented first or exclusively in key sections, especially in the Bicep and ARM template examples, which only show Windows VM creation and extension installation. PowerShell is heavily featured, while Linux command-line or scripting examples are minimal or absent for core tasks. Some operational steps (like folder permissions and extension installation) reference only Windows paths or tools, and Linux equivalents are either missing or less detailed.
Recommendations:
  • Provide parallel Linux examples for all automation, scripting, and deployment scenarios (e.g., show how to deploy the Hybrid Worker extension to a Linux VM using Bicep/ARM templates, Azure CLI, REST API, and PowerShell).
  • In code samples and step-by-step instructions, present both Windows and Linux paths, commands, and configuration details side-by-side or in clearly separated tabs.
  • Include Linux-specific operational guidance, such as required folder permissions, service management, and troubleshooting steps, matching the detail provided for Windows.
  • When listing tools or onboarding channels (e.g., PowerShell, Azure CLI), ensure Linux-friendly tools and workflows are given equal prominence and detail.
  • Avoid presenting Windows instructions or tools before Linux equivalents unless there is a technical reason; strive for parity in ordering and depth.
  • Expand the 'Remove agent-based Hybrid Worker' and other operational sections to provide more comprehensive Linux removal and cleanup steps, including agent uninstallation and configuration file cleanup.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstart-create-automation-account-template.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation demonstrates a mild Windows bias by referencing PowerShell before Azure CLI in deployment instructions and error handling, and by providing explicit PowerShell parameter usage examples. While Azure CLI is mentioned, PowerShell is consistently listed first and receives more detailed treatment. There are no Linux-specific examples, and the documentation does not mention Linux tools or shell environments.
Recommendations:
  • Present Azure CLI and PowerShell instructions in parallel, or alternate which is listed first to avoid implying preference.
  • Provide explicit Linux shell (bash) examples for deploying ARM templates, including command-line syntax and parameter usage.
  • Include a section or callout for Linux/macOS users, clarifying that all steps are cross-platform and providing any OS-specific notes if needed.
  • Where error messages reference PowerShell, also show the equivalent CLI/Linux troubleshooting steps.
  • Avoid using 'PowerShell' as the default or primary example unless there is a technical reason to do so.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/whats-new.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a bias toward Windows and PowerShell by consistently prioritizing PowerShell runbooks, mentioning PowerShell versions and features before Python or Linux equivalents, and providing examples and feature announcements that focus on PowerShell and Windows-centric tools. Linux and Python support are mentioned, but often as secondary or afterthoughts, and there are few, if any, Linux-specific examples or guidance.
Recommendations:
  • Ensure that all feature announcements and examples include both PowerShell and Python (or Bash) runbook scenarios, with equal prominence.
  • When discussing runbook support, mention Python and Linux support alongside PowerShell and Windows, not after.
  • Provide Linux-specific guidance, examples, and migration paths where appropriate (e.g., for Hybrid Runbook Workers, show both Windows and Linux installation/migration steps).
  • Highlight cross-platform capabilities and tools (such as Azure CLI in Bash) equally with PowerShell.
  • Where scripts or GitHub resources are referenced, include both PowerShell and Python/Bash versions, or clarify cross-platform compatibility.
  • Audit the documentation for sections that implicitly assume a Windows/PowerShell environment and revise to be OS-agnostic or to provide Linux parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/runtime-environment-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a strong Windows and PowerShell bias. PowerShell is consistently mentioned first and in greater detail than Python, with specific focus on PowerShell versions and features. The Azure CLI is only discussed in the context of PowerShell 7.4, with no mention of Bash or Linux-native scripting environments. There are no examples or references for Linux shell scripting, and the only default packages highlighted are Az PowerShell and Azure CLI (as used from PowerShell). The documentation does not provide parity for Linux users or those using Bash or other Unix shells.
Recommendations:
  • Include examples and explanations for using Azure CLI in Bash or Linux-native environments, not just PowerShell.
  • List Bash or shell scripting as a supported language if applicable, or clarify its support status.
  • Provide Linux-centric package examples (e.g., pip for Python, apt/yum for system packages) alongside PowerShell examples.
  • Mention and document any Linux-specific runtime environments or limitations, if they exist.
  • Ensure that references and links are balanced between PowerShell and Python, and add links to Bash or Linux scripting documentation where relevant.
  • Explicitly state if certain features are Windows/PowerShell-only, and suggest Linux alternatives if available.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/source-control-integration.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples are provided exclusively using Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native workflows. The prerequisites and configuration steps assume the use of PowerShell consoles, and references to file encoding issues point to PowerShell/VSCode documentation. There are no Linux or cross-platform command-line examples, and the documentation does not address how users on Linux or macOS systems might perform equivalent tasks.
Recommendations:
  • Add equivalent Azure CLI examples for all PowerShell commands, especially for assigning roles and configuring source control.
  • Include explicit instructions and examples for Linux/macOS users, such as using Bash or cross-platform shells.
  • Reference cross-platform tools and workflows (e.g., Azure CLI, REST API via curl) alongside PowerShell.
  • When discussing file encoding issues, link to general encoding best practices or Linux/macOS-specific guidance, not just PowerShell/VSCode.
  • Ensure that screenshots and UI walkthroughs do not assume a Windows environment where not necessary.
  • Clearly state platform compatibility and any limitations for Linux/macOS users at the start of the documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/tutorial-configure-servers-desired-state.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily biased towards Windows and PowerShell. All code examples use PowerShell cmdlets and Windows-specific DSC resources (e.g., WindowsFeature IIS). The prerequisites and instructions focus exclusively on Windows VMs, with no Linux-specific examples or guidance. References and links are also Windows/PowerShell-centric, and there is no demonstration of managing Linux nodes or using Linux-compatible DSC resources.
Recommendations:
  • Add parallel examples for onboarding and configuring Linux VMs, including sample configurations using Linux DSC resources (e.g., nxFile, nxPackage).
  • Include prerequisites and instructions for Linux VMs, such as supported distributions and required packages.
  • Provide Bash/CLI examples where possible, or at least reference how Linux users can interact with Azure Automation State Configuration.
  • Clarify in the introduction and throughout the document whether Linux is still supported, especially in light of the included retirement announcement.
  • Link to documentation specifically about managing Linux nodes with Azure Automation State Configuration, if still supported.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/runbook-input-parameters.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a strong Windows and PowerShell bias. Nearly all code examples, parameter definitions, and workflows are presented using PowerShell or PowerShell Workflow, which are Windows-centric technologies. The only mention of Python runbooks is brief and lacks concrete examples, and there are no examples or guidance for Linux shell scripting or CLI-based automation. The documentation assumes the use of Windows tools and patterns (e.g., PowerShell cmdlets, .NET types), and Linux/Unix equivalents are not discussed or demonstrated. Even SDK and REST API examples are shown in C# (another Windows-centric language), and all automation scenarios are illustrated using Windows tools and conventions.
Recommendations:
  • Provide equivalent examples for Linux/Unix environments, such as using Bash scripts or Azure CLI to start and manage runbooks.
  • Expand the Python runbook section with concrete parameter handling examples, including how to pass parameters from Linux environments.
  • Include examples of starting runbooks using Azure CLI (az automation runbook start) and show how to pass parameters from the command line.
  • Discuss differences and considerations for users running automation from Linux/macOS, such as authentication and file path handling.
  • Balance SDK examples by including Python or JavaScript code snippets, not just C#.
  • Clarify which features or patterns are Windows/PowerShell-specific and provide Linux-friendly alternatives where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/start-runbooks.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a clear Windows bias. All command-line examples use Windows PowerShell, and there are no examples for Linux users (e.g., Azure CLI, Bash, or cross-platform PowerShell Core). The term 'Windows PowerShell' is used explicitly, and the documentation does not mention or provide parity for Linux tools or workflows. The order of presentation also places Windows/PowerShell methods before more cross-platform or API-based approaches.
Recommendations:
  • Add equivalent Azure CLI examples for starting and managing runbooks, as Azure CLI is cross-platform and widely used on Linux.
  • Clarify when 'PowerShell' refers to Windows PowerShell versus cross-platform PowerShell Core, and provide examples that work on both.
  • Include Bash/cURL examples for API-based methods to demonstrate Linux-friendly workflows.
  • Reorder the methods table or present cross-platform options (like Azure CLI and REST API) before or alongside Windows-specific tools.
  • Explicitly mention Linux/macOS compatibility and provide guidance for non-Windows environments.