Automation

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

Bias Trend Over Time

Pages with Bias Issues

982 issues found
Showing 951-975 of 982 flagged pages
Automation Azure Automation extension for Visual Studio Code ...ation/how-to/runbook-authoring-extension-for-vscode.md
Medium Priority View Details →
Scanned: 2026-01-11 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 for local runbook execution, without mentioning Bash or other Linux-native scripting environments. There are no explicit examples or instructions tailored for Linux users, nor is there guidance on installing Python packages or PowerShell modules on Linux. The documentation assumes familiarity with Windows-centric tools and patterns, potentially leaving Linux users with unanswered questions about compatibility and setup.
Recommendations
  • Explicitly mention that PowerShell Core is cross-platform and provide instructions for installing PowerShell modules on Linux/macOS, including relevant commands.
  • Include examples or notes for Linux users, such as how to install Python packages and PowerShell modules using native package managers (e.g., apt, yum, brew).
  • Clarify whether runbook authoring and debugging features work identically on Linux/macOS, and highlight any platform-specific limitations or considerations.
  • Add screenshots or instructions that demonstrate the extension's use on Linux/macOS, if supported.
  • Reference Bash or other Linux-native scripting environments if supported by Azure Automation, or clarify that only PowerShell/Python are supported.
GitHub Create Pull Request
Automation Azure Automation extension for Visual Studio Code ...ation/how-to/runbook-authoring-extension-for-vscode.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation page for the Azure Automation extension for Visual Studio Code shows a bias toward Windows environments by referencing PowerShell modules as a prerequisite and not mentioning Linux-specific requirements or examples. There are no explicit Linux or cross-platform instructions, and the documentation assumes PowerShell usage, which is more common on Windows. No Linux tools, shell examples, or package management instructions are provided.
Recommendations
  • Add explicit instructions for Linux users, such as how to install required Python packages and PowerShell modules on Linux (e.g., using pip and pwsh).
  • Clarify that PowerShell Core (pwsh) is supported and provide installation steps for Linux/macOS.
  • Include screenshots or examples showing the extension in use on Linux (e.g., Ubuntu) and macOS.
  • Mention any platform-specific limitations or differences in functionality.
  • List prerequisites for Linux and macOS, such as required dependencies and environment setup.
GitHub Create Pull Request
Automation Azure Automation FAQ ...e-docs/blob/main/articles/automation/automation-faq.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page generally maintains parity between Windows and Linux, but there is evidence of Windows bias in the section describing how a Hybrid Runbook Worker selects the Python interpreter. The Windows process is described in detail with explicit examples (e.g., C:\Python2\python.exe), while the Linux equivalent process is not described or exemplified. This prioritizes Windows-specific information and omits Linux-specific guidance, which may disadvantage Linux users.
Recommendations
  • Add explicit examples for Linux Hybrid Runbook Workers, such as environment variable names, typical installation paths (e.g., /usr/bin/python3), and interpreter selection logic.
  • Ensure that interpreter selection and environment variable usage are described for both Windows and Linux, with parallel detail and examples.
  • Review other sections to confirm that Linux-specific instructions or troubleshooting steps are present wherever Windows-specific ones are given.
  • Consider adding a table or side-by-side comparison for interpreter selection on Windows and Linux Hybrid Runbook Workers.
GitHub Create Pull Request
Automation Enforce job execution on Azure Automation Hybrid Runbook Worker ...cles/automation/enforce-job-execution-hybrid-worker.md
Medium Priority View Details →
Scanned: 2026-01-10 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 examples are given equal prominence and detail as CLI, and PowerShell is a Windows-centric tool. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments or guidance for Linux users. The documentation implicitly assumes familiarity with PowerShell and does not address Linux-specific considerations or alternative workflows.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Add Bash shell examples for Azure CLI commands to demonstrate usage on Linux systems.
  • Clarify that PowerShell Core is available on Linux and macOS, or provide links to installation instructions for non-Windows platforms.
  • Include notes or sections addressing Linux users, such as environment setup, file path conventions, and troubleshooting tips specific to Linux.
  • Review screenshots and UI instructions to ensure they do not assume a Windows environment (e.g., file dialogs, path formats).
GitHub Create Pull Request
Automation Manage Python 2 packages in Azure Automation ...-docs/blob/main/articles/automation/python-packages.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively providing instructions and command-line examples for downloading Python packages and dependencies using Windows tools and paths (e.g., 'C:\Python27\Scripts\pip2.7.exe'), without mentioning or providing equivalent steps for Linux or macOS environments. There are no Linux-specific examples or guidance for users who may be developing on non-Windows platforms.
Recommendations
  • Include equivalent instructions and command examples for Linux (and optionally macOS), such as using 'python2.7 -m pip download ...' or 'pip2 download ...' in a bash shell.
  • Clarify that the process is not limited to Windows and provide cross-platform guidance for downloading and preparing packages.
  • Add notes or sections highlighting any platform-specific considerations, such as file paths, Python installation locations, and package management differences.
  • Ensure screenshots and references do not exclusively show Windows environments unless necessary, and provide alternatives where possible.
GitHub Create Pull Request
Automation Archive for What's new in Azure Automation ...ocs/blob/main/articles/automation/whats-new-archive.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally maintains parity between Windows and Linux, mentioning support and features for both platforms. However, there are subtle signs of Windows bias: Windows-specific tools and scripts (e.g., PowerShell Gallery, Windows HybridWorker script) are mentioned by name, sometimes before their Linux equivalents. Windows operating system support is called out explicitly in some update notes, while Linux support is sometimes grouped or referenced via external links. PowerShell modules (Az modules) and Windows onboarding scripts are highlighted, with less emphasis on Linux-specific onboarding or tooling.
Recommendations
  • Ensure that Linux examples, scripts, and tooling are mentioned with equal prominence and detail as Windows equivalents.
  • When referencing scripts or onboarding procedures, provide direct links and names for both Windows and Linux scripts, not just Windows.
  • If PowerShell or Windows tools are mentioned, also mention and link to equivalent Bash, Python, or Linux-native tools/scripts.
  • List supported operating systems in parallel (e.g., 'Windows Server 2008 R2 and Ubuntu 18.04 are now supported') rather than Windows first.
  • Avoid referencing Windows-specific modules (e.g., Az modules) without also referencing Linux-compatible alternatives or usage patterns.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstart-create-automation-account-template.md ...ation/quickstart-create-automation-account-template.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by referencing PowerShell before Azure CLI when describing how to deploy the ARM template from the command line. The instructions and error handling examples mention PowerShell first, and provide explicit PowerShell parameter syntax before CLI equivalents. There are no Linux-specific tools or shell examples (e.g., Bash), and no mention of Linux environments or considerations. However, Azure CLI is referenced, and the overall instructions are largely platform-neutral.
Recommendations
  • Present Azure CLI (cross-platform) examples before or alongside PowerShell examples to avoid Windows-first impression.
  • Include explicit Bash shell examples for Linux users, especially for ARM template deployment.
  • Clarify that both PowerShell and Azure CLI are available on Windows, macOS, and Linux, and provide installation links for each.
  • Add a note or section on running these commands in Linux environments, including any differences or considerations.
  • Ensure that error messages and troubleshooting steps are not PowerShell-centric and provide CLI/Bash alternatives.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-faq.md ...e-docs/blob/main/articles/automation/automation-faq.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides more detailed examples and instructions for Windows environments, particularly in the section about Hybrid Runbook Worker Python version selection. It describes the use of Windows-specific environment variables and file paths (e.g., C:\Python2\python.exe) but does not provide equivalent Linux examples or mention Linux-specific environment variables or file locations. This creates a Windows-first impression and leaves Linux users without clear guidance for their platform.
Recommendations
  • Add explicit Linux examples for environment variable usage and Python interpreter location, such as referencing typical Linux paths (e.g., /usr/bin/python2, /usr/bin/python3) and environment variables.
  • Clarify how Hybrid Runbook Workers behave on Linux, including any differences in configuration or detection logic compared to Windows.
  • Ensure that instructions and examples are presented for both Windows and Linux platforms in parallel, rather than focusing on Windows first.
  • Where Windows-specific tools or patterns are mentioned, provide Linux equivalents (e.g., mention shell environment variables and file paths alongside Windows examples).
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/enforce-job-execution-hybrid-worker.md ...cles/automation/enforce-job-execution-hybrid-worker.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents both Azure CLI and Azure PowerShell examples for policy creation and assignment, but PowerShell examples are consistently given equal prominence and detail as CLI, and PowerShell is referenced as a primary method for retrieving policy definition IDs. There is no mention of Linux-specific tools, shell environments, or scripting patterns, and PowerShell (traditionally Windows-centric) is featured alongside CLI in all code sections. The documentation does not provide Linux shell (bash) or automation examples, nor does it clarify cross-platform usage for PowerShell Core.
Recommendations
  • Explicitly state that Azure CLI and PowerShell Core are cross-platform and can be used on Linux, macOS, and Windows.
  • Add bash shell script examples for Linux users, demonstrating equivalent operations using Azure CLI.
  • Clarify that PowerShell examples use PowerShell Core, which is available on Linux, or provide links to installation instructions for Linux.
  • Include notes or sections on Linux-specific considerations for Hybrid Runbook Worker environments, if any.
  • Ensure that CLI examples are presented before PowerShell, or provide a Linux-first workflow to improve parity.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/how-to/runbook-authoring-extension-for-vscode.md ...ation/how-to/runbook-authoring-extension-for-vscode.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation page displays a bias towards Windows environments by referencing PowerShell modules as a prerequisite and not mentioning Linux-specific equivalents or considerations. There are no examples or instructions tailored for Linux users, such as Bash or shell scripting, nor any mention of Linux package management or troubleshooting. The documentation assumes a Windows-centric workflow for local runbook testing and module installation.
Recommendations
  • Explicitly mention support for Linux and macOS environments in prerequisites and instructions.
  • Provide examples for installing required Python packages and PowerShell modules on Linux (e.g., using pip and PowerShell Core on Linux).
  • Clarify whether PowerShell Core (pwsh) is supported and provide instructions for its installation on Linux.
  • Include troubleshooting tips for common Linux issues (e.g., permissions, path differences).
  • Add screenshots or notes showing the extension in use on Linux/macOS, if supported.
  • List any OS-specific limitations or differences in the 'Next steps' or a dedicated section.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/python-packages.md ...-docs/blob/main/articles/automation/python-packages.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by providing package download instructions exclusively for Windows (using Windows paths and Python installed in C:\Python27), without mentioning or providing equivalent steps for Linux or macOS users. There are no Linux-specific examples, commands, or references to cross-platform compatibility in the manual package download section.
Recommendations
  • Add equivalent instructions for Linux and macOS users, such as using 'python2.7' and 'pip2' commands in a Unix shell.
  • Provide example commands for downloading packages and dependencies on Linux (e.g., 'pip2 download -d <output_dir> <package_name>').
  • Clarify that the process works on any OS with Python 2.7 and pip installed, and update screenshots or file paths to be OS-neutral or provide alternatives.
  • Explicitly mention cross-platform compatibility and note any OS-specific considerations.
  • Ensure that all steps and examples are presented for both Windows and Linux/macOS, or in a way that is platform-agnostic.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/create-azure-automation-account-terraform.md ...ickstarts/create-azure-automation-account-terraform.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides verification steps for both Azure CLI and Azure PowerShell, but PowerShell is given equal prominence, and the 'Next steps' section specifically recommends a PowerShell runbook tutorial. There is no mention of Linux-specific tools or shell environments (e.g., Bash), nor is there any explicit guidance for Linux users, which may suggest a subtle Windows bias.
Recommendations
  • Add explicit Bash/Linux shell examples alongside PowerShell, especially in verification steps.
  • Ensure that CLI examples are clearly marked as cross-platform and clarify that Azure CLI works on Linux, macOS, and Windows.
  • In the 'Next steps' section, include links to tutorials for both PowerShell and Python runbooks, or other cross-platform automation options.
  • Mention that Terraform and Azure CLI are cross-platform, and provide guidance for Linux users where appropriate.
  • Avoid defaulting to PowerShell in follow-up tutorials; offer parity for Python or Bash runbooks.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/whats-new-archive.md ...ocs/blob/main/articles/automation/whats-new-archive.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally maintains parity between Windows and Linux, especially in recent updates, but there is evidence of Windows bias. Windows examples and tools (such as PowerShell modules and scripts) are mentioned first or exclusively in several places, and Windows-specific onboarding scripts and support for Windows Server versions are highlighted before or more prominently than Linux equivalents. Linux support is present and improving, but Windows tooling and terminology (e.g., Az modules, PowerShell Gallery) are referenced more often and sometimes without Linux alternatives.
Recommendations
  • Ensure that Linux examples, scripts, and tools are mentioned alongside Windows equivalents, not after or as an afterthought.
  • Where onboarding scripts or modules are referenced (e.g., Az modules, PowerShell Gallery), include explicit links or references to Linux-compatible alternatives or instructions.
  • When listing supported operating systems or features, alternate the order between Windows and Linux, or group them together to avoid implicit prioritization.
  • Expand documentation to include more Linux-specific troubleshooting, usage patterns, and best practices, especially for hybrid scenarios.
  • Audit all example scripts and references to ensure Linux users are equally supported and not required to adapt Windows-centric instructions.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/change-tracking/manage-change-tracking-monitoring-agent.md ...ge-tracking/manage-change-tracking-monitoring-agent.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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).
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/delete-run-as-account.md ...blob/main/articles/automation/delete-run-as-account.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/create-azure-automation-account-terraform.md ...ickstarts/create-azure-automation-account-terraform.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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).
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-faq.md ...e-docs/blob/main/articles/automation/automation-faq.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/delete-run-as-account.md ...blob/main/articles/automation/delete-run-as-account.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/enforce-job-execution-hybrid-worker.md ...cles/automation/enforce-job-execution-hybrid-worker.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
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 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.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstart-create-automation-account-template.md ...ation/quickstart-create-automation-account-template.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Automation Authenticate Azure Automation runbooks with Amazon Web Services ...n/articles/automation/automation-config-aws-account.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing the AWS PowerShell user guide for credential specification and omitting Linux/macOS-specific examples or CLI references. The only external example for specifying AWS credentials points to PowerShell documentation, with no mention of Linux tools (e.g., AWS CLI) or platform-neutral instructions. No explicit Windows-only steps are present, but the guidance assumes familiarity with Windows-centric tooling.
Recommendations
  • Add references to AWS CLI documentation for credential management on Linux/macOS.
  • Include examples for storing and retrieving credentials using platform-neutral tools.
  • Clarify that the process is platform-agnostic and provide links to both PowerShell and CLI guides.
  • Mention that Azure Automation runbooks can be authored and managed from any OS, and provide parity in instructions.
GitHub Create Pull Request
Automation Azure Automation Hybrid Runbook Worker Overview ...rticles/automation/automation-hybrid-runbook-worker.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. PowerShell is mentioned as a primary onboarding channel before alternatives, and Windows terminology (System account) is used before Linux equivalents. Windows is often referenced first in lists and examples, and Windows-centric tools (PowerShell, ARM templates) are highlighted. Linux support is present and mentioned, but Linux-specific examples, tools, and terminology are less emphasized or appear after Windows references.
Recommendations
  • Provide Linux-specific onboarding instructions and examples alongside Windows, ensuring parity in detail and visibility.
  • Mention Linux tools (such as Bash, shell scripts, systemd) and Linux-specific deployment methods (e.g., cloud-init, Ansible) where relevant.
  • Alternate the order of Windows and Linux references in tables and lists to avoid Windows-first bias.
  • Include explicit Linux account details and permissions (e.g., nxautomation) in all relevant sections, not just as a secondary note.
  • Offer troubleshooting and operational guidance tailored for Linux environments, not just generic or Windows-centric advice.
GitHub Create Pull Request
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-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 examples for policy creation and assignment, but PowerShell (a Windows-centric tool) is given equal prominence and sometimes appears first. There are no Linux-specific shell examples (e.g., Bash scripts), nor is there mention of Linux/macOS-specific considerations. The use of PowerShell may create friction for Linux/macOS users who are less familiar with it.
Recommendations
  • Ensure Azure CLI examples are shown before PowerShell examples, as CLI is cross-platform.
  • Explicitly state that Azure CLI commands work on Linux/macOS and provide any OS-specific notes if needed.
  • Add Bash script examples for common tasks, especially for file creation and manipulation.
  • Clarify that PowerShell Core is available cross-platform, but recommend Azure CLI for Linux/macOS users.
  • Add a short section on Linux/macOS prerequisites or troubleshooting tips if relevant.
GitHub Create Pull Request
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. It references PowerShell as the tool for viewing individual job logs and mentions PowerShell error streams when discussing job errors. There are no explicit Linux/macOS CLI examples or references to cross-platform tools (such as Azure CLI or Bash), and PowerShell is mentioned before any alternatives. However, most of the instructions and queries are performed in the Azure Portal or via Kusto Query Language, which are platform-agnostic.
Recommendations
  • Add explicit references and examples for Linux/macOS users, such as using Azure CLI or Bash to view job logs and streams.
  • Clarify that PowerShell examples are applicable on Linux/macOS via PowerShell Core, or provide equivalent Azure CLI commands.
  • Avoid mentioning PowerShell as the only way to access job logs; include cross-platform alternatives in all relevant sections.
  • Where error streams are discussed, note how non-PowerShell runbooks (Python, etc.) behave and how errors are surfaced.
GitHub Create Pull Request
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-14 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 is mentioned first and in more detail. The error handling and parameter instructions reference PowerShell before Azure CLI, and the example parameter syntax is shown for PowerShell first. There are no Linux/macOS-specific examples or notes, and the documentation does not mention platform differences or considerations for non-Windows users.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
  • Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and provide parity in instructions for each.
  • Add a note clarifying that PowerShell is available on Linux/macOS, but Azure CLI is often the default on those platforms.
  • Include troubleshooting steps and error messages for both PowerShell and Azure CLI, not just PowerShell.
  • Where possible, add screenshots or terminal outputs from Linux/macOS environments.
GitHub Create Pull Request
← Previous Page 39 of 40 Next →