123
Total Pages
24
Linux-Friendly Pages
99
Pages with Bias
80.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

982 issues found
Showing 976-982 of 982 flagged pages
Automation Quickstart: Use Terraform to create an Azure Automation account ...ickstarts/create-azure-automation-account-terraform.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but PowerShell is presented as a primary tab, and the 'Next steps' section links to a PowerShell-specific tutorial. There is no mention of Linux/macOS-specific shell environments, nor are there Bash or shell script examples. The CLI instructions are cross-platform, but the presence and order of PowerShell content, and the PowerShell-focused next step, indicate a mild Windows bias.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
  • Add Bash/shell script examples where environment variables are set and commands are run, to demonstrate parity for Linux/macOS users.
  • In the 'Next steps' section, provide links to tutorials using Bash or Azure CLI, not just PowerShell.
  • Consider listing CLI/Bash instructions before PowerShell, or clarify that both are supported equally.
Automation Forward Azure Automation job data to Azure Monitor logs ...mation/automation-manage-send-joblogs-log-analytics.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page shows mild Windows bias. PowerShell is mentioned as a tool to view job logs, and Windows terminology (PowerShell error streams) is referenced when discussing error handling. No Linux/macOS-specific tools or CLI examples are provided, and PowerShell is the only command-line tool mentioned for individual job inspection. However, most instructions are platform-neutral and focus on the Azure portal and Kusto queries, which are accessible from any OS.
Recommendations
  • Explicitly mention cross-platform tools such as Azure CLI and provide equivalent examples for querying job logs and streams.
  • Clarify that Kusto queries and Azure portal steps are OS-independent.
  • If PowerShell is referenced, note that PowerShell Core is available on Linux/macOS, or provide Azure CLI/Bash alternatives where relevant.
  • Add a section or note describing how Linux/macOS users can perform equivalent tasks (e.g., viewing job logs) without relying on Windows-specific tools.
Automation Azure Automation Hybrid Runbook Worker Overview ...rticles/automation/automation-hybrid-runbook-worker.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally maintains parity between Windows and Linux, mentioning both platforms in installation and operational contexts. However, there is a subtle Windows bias: PowerShell is referenced as a primary onboarding channel before alternatives like Azure CLI, and Windows terminology (such as 'System' account) is explained in more detail than Linux equivalents. Windows is often mentioned first in lists and examples, and PowerShell Workflow runbooks are specifically referenced for job checkpointing, with no equivalent Linux shell workflow mentioned.
Recommendations
  • Ensure onboarding examples and tool references (e.g., Azure CLI, Bicep) are presented with equal prominence to PowerShell, and provide explicit Linux shell examples where possible.
  • When describing operational details (such as job execution accounts), provide equal detail for Linux (e.g., explain the 'nxautomation' account as thoroughly as 'System' for Windows).
  • Avoid listing Windows before Linux in tables and lists unless there is a technical reason.
  • Include references to Linux-specific automation tools or scripting languages (e.g., Bash, Python) where PowerShell is mentioned.
  • Clarify workflow/checkpointing behavior for non-PowerShell runbooks on Linux.
Automation Enforce job execution on Azure Automation Hybrid Runbook Worker ...cles/automation/enforce-job-execution-hybrid-worker.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for policy creation and assignment, but PowerShell (a Windows-centric tool) is given equal prominence and detail as Azure CLI. In some sections, PowerShell commands are shown after CLI, but PowerShell-specific instructions and parameter explanations are included, which may suggest a slight Windows bias. There are no Linux/macOS-specific shell examples (e.g., Bash scripts), nor is there mention of platform-specific considerations for Linux users. However, Azure CLI is cross-platform and shown first, mitigating the impact.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Add a note clarifying that PowerShell Core is available on Linux/macOS, and provide installation links.
  • Include brief Bash script examples for file creation or command chaining, where relevant.
  • Mention any platform-specific considerations (e.g., file path formats, authentication differences) for Linux/macOS users.
  • Ensure that CLI examples remain first and are complete, as CLI is the most universal option.
Automation Azure Automation extension for Visual Studio Code ...ation/how-to/runbook-authoring-extension-for-vscode.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias by referencing PowerShell modules as a prerequisite and not mentioning Linux/macOS equivalents or considerations. There are no explicit Linux/macOS instructions or examples, and the documentation does not clarify whether the extension or runbook local execution works equally well on non-Windows platforms.
Recommendations
  • Clarify whether the Azure Automation extension and local runbook execution are supported on Linux/macOS.
  • Mention installation steps for PowerShell Core on Linux/macOS, and specify if Python runbooks can be authored and tested locally on these platforms.
  • Add notes or examples for Linux/macOS users, including any platform-specific limitations or requirements.
  • Explicitly state any differences in experience or troubleshooting steps for non-Windows users.
Automation Create an Azure Automation account using a Resource Manager template ...ation/quickstart-create-automation-account-template.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides deployment instructions for both PowerShell and Azure CLI, but PowerShell (a Windows-centric tool) is mentioned first and in more detail. The error handling and parameter instructions also reference PowerShell before Azure CLI, and the reference link is titled 'Create Azure Automation account (microsoft.com)' but refers to PowerShell in its section heading. No Linux/macOS-specific guidance or screenshots are provided, and no mention is made of platform-specific differences or requirements.
Recommendations
  • Present Azure CLI instructions before or alongside PowerShell, as CLI is cross-platform.
  • Add explicit notes or examples for Linux/macOS users, including screenshots if relevant.
  • Clarify that both PowerShell and Azure CLI are supported, and highlight any platform-specific considerations.
  • Avoid language that implies PowerShell is the default or preferred method.
  • Include troubleshooting steps or common issues for Linux/macOS environments.
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/includes/automation-dsc-linux-retirement-announcement.md ...cludes/automation-dsc-linux-retirement-announcement.md
Low Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
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.
← Previous Page 40 of 40 Next →