Azure Arc

465
Total Pages
253
Linux-Friendly Pages
212
Pages with Bias
45.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

2334 issues found
Showing 1251-1275 of 2334 flagged pages
Azure Arc Migrate a database from SQL Server to SQL Managed Instance enabled by Azure Arc ...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides examples and instructions that prioritize Windows environments, such as using Windows file paths (C:\Backupfiles\...) and referencing Windows tools (Notepad, OneNote) for copying credentials. There are no explicit Linux/macOS examples for backup file paths or alternative tools, which may create friction for users on non-Windows platforms.
Recommendations
  • Include Linux/macOS equivalents for file paths in backup and restore examples (e.g., /home/user/Backupfiles/test.bak).
  • Mention cross-platform editors (e.g., VS Code, nano) alongside Notepad/OneNote for saving credentials.
  • Clarify that Azure Data Studio and Azure Storage Explorer are available on Linux/macOS and provide installation links for those platforms.
  • Provide example commands for copying backup files from Linux/macOS systems using kubectl cp.
  • Add notes or callouts where steps differ for Linux/macOS users.
GitHub Create Pull Request
Azure Arc Upload metrics to Azure Monitor ...cs/blob/main/articles/azure-arc/data/upload-metrics.md
Medium 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 provides examples for PowerShell and macOS/Linux for most commands, but the Windows tab is frequently marked as 'N/A' or only provides basic SET/echo commands. The automation section gives a Linux shell script example and mentions Windows Task Scheduler, but does not provide a concrete Windows batch or PowerShell script for automating uploads. PowerShell examples are shown before Linux/macOS in most cases, and Linux-specific tools (like jq) are used without Windows alternatives. There is a lack of parity in scripting and automation guidance for Windows users.
Recommendations
  • Provide Windows batch (.bat/.cmd) and PowerShell script examples for automating metric uploads, similar to the Linux shell script provided.
  • Include Windows-friendly alternatives to Linux tools (e.g., suggest PowerShell's ConvertFrom-Json instead of jq for parsing JSON).
  • Ensure that all command examples are available for Windows users, not just marked as 'N/A'.
  • Present Linux/macOS and Windows examples side-by-side or in a consistent order to avoid implicit prioritization.
GitHub Create Pull Request
Azure Arc Configure "BYOM" Endpoint Authentication for Edge RAG ...zure-arc/edge-rag/configure-endpoint-authentication.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page provides all command-line examples using PowerShell syntax and Windows-specific patterns (e.g., .\kubectl.exe), without any Bash or Linux/macOS shell equivalents. This creates friction for Linux/macOS users, who must adapt the commands themselves. The use of PowerShell-specific constructs (e.g., [System.Text.Encoding]::UTF8.GetString) and explicit references to .exe files further reinforce a Windows-first approach.
Recommendations
  • Provide equivalent Bash/Linux/macOS shell commands alongside PowerShell examples.
  • Use platform-agnostic kubectl commands (e.g., 'kubectl' instead of '.\kubectl.exe') unless Windows-only behavior is required.
  • Replace PowerShell-specific base64 decoding with cross-platform alternatives (e.g., 'base64 --decode' in Bash).
  • Add a note clarifying any platform-specific differences and how Linux/macOS users should adapt the instructions.
GitHub Create Pull Request
Azure Arc Deploy the Edge RAG Extension ...t-docs/blob/main/articles/azure-arc/edge-rag/deploy.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides Azure CLI deployment instructions exclusively using PowerShell syntax and variable assignment, without any Bash or Linux shell equivalents. All CLI examples use Windows-style PowerShell variables and line continuations, which may confuse or hinder Linux/macOS users. There are no Bash examples or notes for Linux users, and PowerShell is presented as the default scripting environment for CLI usage.
Recommendations
  • Add equivalent Bash shell examples for Azure CLI commands, using Bash variable assignment and syntax.
  • Include a note clarifying that Azure CLI works cross-platform and provide guidance for Linux/macOS users.
  • Present both PowerShell and Bash examples side-by-side or in tabs, or default to Bash for CLI documentation unless Windows-specific features are required.
  • Avoid using Windows-specific line continuations (backtick `) in CLI examples; use standard Bash line continuations (backslash \) for Linux/macOS.
  • Explicitly mention any platform-specific requirements if PowerShell is required for certain steps.
GitHub Create Pull Request
Azure Arc Verify Contributor Role for Edge RAG Preview Enabled by Azure Arc ...s/azure-arc/edge-rag/prepare-contributor-permission.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides only PowerShell CLI examples for verifying contributor permissions, without mentioning or demonstrating equivalent Linux/macOS shell usage. This may create friction for non-Windows users, as the Azure CLI is cross-platform and typically used via Bash or other shells on Linux/macOS.
Recommendations
  • Include example commands using Bash or generic shell syntax to demonstrate Azure CLI usage on Linux/macOS.
  • Clarify that the Azure CLI commands are cross-platform and can be run in any shell, not just PowerShell.
  • Avoid using PowerShell-specific formatting unless the task is Windows-only.
GitHub Create Pull Request
Azure Arc Configure DNS for Edge RAG Preview Enabled by Azure Arc ...s/blob/main/articles/azure-arc/edge-rag/prepare-dns.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only Windows-specific instructions for updating the hosts file (using Notepad, referencing the Windows hosts file path), with no mention of how to perform the equivalent task on Linux or macOS. This creates friction for non-Windows users who need to configure DNS for Edge RAG deployments.
Recommendations
  • Add instructions for editing the hosts file on Linux and macOS, including the typical file path (/etc/hosts) and required permissions (sudo/root).
  • Include example commands for editing the hosts file using common Linux/macOS tools (e.g., nano, vim, or echo with sudo).
  • Clarify that the process is similar across platforms, but file paths and required privileges differ.
  • Consider presenting platform-agnostic steps first, or grouping instructions by OS.
GitHub Create Pull Request
Azure Arc Quickstart: Install Edge RAG on Azure Kubernetes Service ...ain/articles/azure-arc/edge-rag/quickstart-edge-rag.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias in the 'Connect to the developer portal' section, where instructions for editing the hosts file are provided exclusively for Windows (using Notepad and the Windows file path). There are no equivalent instructions for Linux or macOS users, nor is there mention of alternative editors or file locations for those platforms. Additionally, the use of PowerShell-style variable assignment and backtick line continuation in Azure CLI examples may be confusing for non-Windows users, though the commands themselves are cross-platform.
Recommendations
  • Add instructions for editing the hosts file on Linux (e.g., using sudo nano /etc/hosts) and macOS (e.g., sudo open -e /etc/hosts or sudo nano /etc/hosts).
  • Mention the location of the hosts file on Linux/macOS (/etc/hosts) and provide example commands for editing and saving the file.
  • Clarify that the Azure CLI commands can be run on any platform, and provide alternative syntax for variable assignment and line continuation for Bash/zsh (e.g., export rg="edge-rag-aks-rg" and using \ for line continuation).
  • Where PowerShell-specific instructions are given, offer Bash/zsh equivalents or note the differences.
GitHub Create Pull Request
Azure Arc Uninstall Edge RAG Extension ...ain/articles/azure-arc/edge-rag/uninstall-extension.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only PowerShell examples for command-line operations, including Azure CLI and kubectl commands, and does not offer equivalent Linux/macOS shell examples. The use of PowerShell syntax (e.g., $variable assignment) and code blocks labeled as 'powershell' may confuse or hinder Linux/macOS users. There is no mention of Bash or shell alternatives, and Windows-centric patterns are shown first and exclusively.
Recommendations
  • Provide Bash/shell examples alongside PowerShell, especially for Azure CLI and kubectl commands, using standard shell variable syntax.
  • Clarify that Azure CLI and kubectl are cross-platform and can be used from Linux/macOS terminals.
  • Label code blocks appropriately (e.g., 'bash' for shell examples) and avoid PowerShell-only variable assignment for cross-platform commands.
  • Add a note or tab for Linux/macOS users, showing equivalent steps.
GitHub Create Pull Request
Azure Arc Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge." ...e-arc/resource-bridge/includes/network-requirements.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation lists both Windows and Linux-related endpoints, but there is a subtle Windows bias: Windows NTP is mentioned explicitly before any Linux time source, and endpoints such as sts.windows.net, login.windows.net, and time.windows.com are highlighted. The notes for NTP mention only the Windows NTP server and Hyper-V defaults, with no reference to Linux NTP servers or alternatives. The Azure CLI installer download is mentioned, but there is no explicit guidance for Linux package managers or installation methods. Overall, the documentation assumes familiarity with Windows-centric endpoints and patterns.
Recommendations
  • Add explicit references to Linux NTP servers (e.g., pool.ntp.org) and clarify when time.windows.com is only needed for Windows-based deployments.
  • Provide guidance or notes for Linux management machines, such as how to install Azure CLI via native package managers (apt, yum, etc.), and clarify if any endpoints are Windows-specific.
  • Where endpoints or tools are Windows-specific (e.g., sts.windows.net, login.windows.net), clarify their relevance for Linux deployments or provide Linux equivalents if applicable.
  • Ensure examples and notes mention both Windows and Linux scenarios, especially for network configuration and tool installation.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Arc resource bridge issues ...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium 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 provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, several examples and troubleshooting steps show a Windows-first bias: PowerShell is used for network and DNS troubleshooting, Windows paths are referenced in error messages, and some CLI troubleshooting steps (such as downgrading Azure CLI) mention Windows installer methods before Linux alternatives. There are few explicit Linux/macOS command examples, and some troubleshooting steps (e.g., SSH folder access, DNS resolution) use Windows-centric tools or terminology. The documentation does mention Linux-specific errors (GLIBC version), but overall, Linux/macOS users may need to adapt instructions or infer equivalent steps.
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell and Windows command examples (e.g., use dig, nslookup, ping, or host for DNS troubleshooting).
  • When referencing CLI installation or downgrade, include explicit instructions for Linux/macOS (e.g., apt, yum, brew, or direct download).
  • Ensure troubleshooting steps for file permissions, SSH folder access, and networking include Linux/macOS guidance (e.g., chmod, chown, ls -l).
  • Where Windows paths or error messages are shown, clarify Linux/macOS equivalents or note differences.
  • If PowerShell is used for HTTP/HTTPS troubleshooting, offer curl or wget alternatives for Linux/macOS.
GitHub Create Pull Request
Azure Arc Simplify Network Configuration Requirements with Azure Arc Gateway ...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides examples for Azure portal, Azure CLI, and PowerShell for all major operations. PowerShell examples are included and sometimes shown before or alongside CLI, but there is no explicit mention of Linux shell equivalents (e.g., Bash) or guidance for Linux-specific usage patterns. In some sections, PowerShell is referenced for log collection and command execution, with Linux instructions given separately but less prominently. The documentation references Windows installation packages and folders before Linux equivalents, and some examples (such as log file locations) list Windows paths first. There are no explicit Bash or Linux shell script examples, and the CLI examples use backticks (`) for line continuation, which is a Windows/PowerShell convention and not valid in Bash.
Recommendations
  • Provide explicit Bash/Linux shell examples for CLI commands, using correct line continuation (\) and syntax.
  • When listing file paths or installation instructions, present Linux and Windows examples with equal prominence, or alternate their order.
  • Clarify that Azure CLI commands can be run on Linux/macOS and provide any necessary platform-specific notes (e.g., environment variables, permissions).
  • Ensure that Linux onboarding and troubleshooting steps are as detailed as Windows ones, including log file locations and script execution.
  • Avoid using Windows-centric conventions (such as backticks for line continuation) in CLI examples; use platform-neutral or dual examples.
GitHub Create Pull Request
Azure Arc Deploy Azure Monitor agent on Arc-enabled servers ...es/azure-arc/servers/azure-monitor-agent-deployment.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation describes deployment methods for the Azure Monitor agent on both Windows and Linux Arc-enabled servers, but examples and tooling references (e.g., PowerShell, Azure CLI) are presented generically or with a slight Windows-first bias. PowerShell is mentioned before Python when discussing Azure Automation, and there are no explicit Linux shell (bash) or Linux-specific example commands. The documentation does not provide parity in showing Linux-native tooling or step-by-step Linux examples, which may create friction for Linux users.
Recommendations
  • Add explicit Linux shell (bash) examples for deploying the extension via Azure CLI and ARM templates.
  • When referencing scripting in Azure Automation, provide both PowerShell and Python examples, and clarify which is recommended for Linux targets.
  • Include links or sections specifically for Linux users, such as troubleshooting Linux agent installation or verifying agent status on Linux.
  • Ensure that references to PowerShell are balanced with Linux equivalents (e.g., bash, sh, or Python) where appropriate.
GitHub Create Pull Request
Azure Arc CLI reference for `azcmagent show` ...blob/main/articles/azure-arc/servers/azcmagent-show.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation examples use Windows-style quoting (double quotes) and file redirection syntax (e.g., "> agent-status.json"), which may not work as shown on Linux/macOS shells. No Linux/macOS-specific examples or notes are provided.
Recommendations
  • Add Linux/macOS shell examples using single quotes and appropriate file redirection syntax.
  • Include a note clarifying shell differences for quoting and redirection.
  • Show both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) example commands side by side.
GitHub Create Pull Request
Azure Arc Cloud-native governance and policy with Azure Arc-enabled servers ...es/azure-arc/servers/cloud-native/governance-policy.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses heavily on Windows-centric governance concepts, such as Group Policy Objects (GPOs), Resultant Set of Policy (RSoP), and Windows security baselines. Examples and scenarios almost exclusively reference Windows servers, with no mention of Linux equivalents (e.g., Linux security baselines, Linux configuration policies, or Linux-specific compliance scenarios). The documentation does not provide Linux-specific examples or guidance for Azure Arc-enabled Linux servers, despite Azure Policy and machine configuration supporting both Windows and Linux.
Recommendations
  • Add explicit examples and scenarios for Azure Policy and machine configuration on Linux servers, such as auditing and enforcing SSH settings, file permissions, or Linux service configurations.
  • Reference Linux equivalents to Windows concepts (e.g., compare GPO with Linux configuration management tools like Ansible, Chef, or native OS mechanisms).
  • Include links to documentation about Azure Policy for Linux, and mention built-in policies relevant to Linux security/compliance.
  • Clarify which features or policies are cross-platform and which are Windows-only, to help Linux/macOS administrators understand applicability.
  • Provide sample DSC or policy definitions for Linux settings (e.g., password complexity, firewall rules) alongside Windows examples.
GitHub Create Pull Request
Azure Arc Cloud-native licensing and cost management with Azure Arc-enabled servers ...-arc/servers/cloud-native/licensing-cost-management.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses almost exclusively on Windows Server and SQL Server licensing options via Azure Arc, with all examples and scenarios centered around Windows environments. There is no mention of Linux server licensing, cost management, or how Azure Arc features apply to Linux workloads. The structure and examples assume Windows as the primary use case, potentially leaving Linux users unclear about their options.
Recommendations
  • Add a section describing how Azure Arc licensing and cost management applies to Linux servers, even if only to clarify that Linux OS licensing is not managed through Azure Arc.
  • Include explicit statements about the scope of Azure Arc cost management for Linux workloads (e.g., monitoring, inventory, billing for other software, etc.).
  • If SQL Server on Linux is supported, clarify whether pay-as-you-go licensing via Arc applies to those instances.
  • Provide parity in examples, such as cost management for Linux servers, or note differences in licensing models.
GitHub Create Pull Request
Azure Arc Next steps for cloud-native server management with Azure Arc-enabled servers .../articles/azure-arc/servers/cloud-native/next-steps.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows-centric tools and workflows (Windows Admin Center, Configuration Manager, WSUS, GPOs) are mentioned first and in detail, while Linux onboarding and management equivalents are not described or linked. There are no explicit Linux onboarding examples, and Linux-native tools or patterns are not referenced, which may cause friction for Linux users seeking parity.
Recommendations
  • Add explicit onboarding instructions or links for Linux servers, such as using shell scripts or Ansible for agent deployment.
  • Mention Linux-native management tools (e.g., cron, systemd, configuration management systems like Chef/Puppet/Ansible) when discussing automation and configuration.
  • Provide examples or references for patching and compliance management on Linux (e.g., using Azure Update Manager with Linux, or alternatives to GPO/WSUS).
  • Ensure that examples and tool references are balanced between Windows and Linux, or clarify when a tool is Windows-only.
GitHub Create Pull Request
Azure Arc Identity and access management with Azure Arc-enabled servers ...cles/azure-arc/servers/cloud-native/identity-access.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page generally describes identity and access management for Azure Arc-enabled servers in a cross-platform manner. However, it shows a subtle Windows bias: Windows/Active Directory scenarios are described first and in greater detail, and concrete examples (such as Remote Desktop access) are given for Windows, while Linux access (via SSH) is mentioned only briefly and without example commands or further explanation. There are no Linux-specific management scenarios or tools discussed.
Recommendations
  • Provide concrete Linux examples alongside Windows ones, such as showing how to use SSH with Microsoft Entra ID credentials to access Linux Arc-enabled servers.
  • Include Linux-specific management scenarios, such as using Azure CLI or automation tools on Linux servers.
  • Balance the order of presentation so that Linux and Windows are treated equally, or explicitly state when a feature or example is Windows-only.
  • Mention Linux equivalents for tools or processes (e.g., alternatives to Group Policy, LAPS, etc.) where relevant.
GitHub Create Pull Request
Azure Arc Cloud-native server management with Azure Arc-enabled servers ...in/articles/azure-arc/servers/cloud-native/overview.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references several Windows-centric management tools (Active Directory Group Policy, SCCM, MECM, PowerShell remoting, WSUS) as examples of legacy/on-premises solutions that Azure Arc replaces, with limited mention of Linux equivalents. Windows tools and patterns are described first and in more detail, while Linux management paradigms (such as Ansible, Chef, or native Linux configuration management) are not referenced. However, the core Azure Arc features are described as supporting both Windows and Linux servers.
Recommendations
  • Include references to common Linux management tools (e.g., Ansible, Chef, Puppet, cron, SSH) when discussing legacy/on-premises solutions that Azure Arc replaces.
  • Provide examples or analogies for Linux system administrators, such as how Azure Policy and Machine Configuration can replace Linux configuration management tools.
  • Clarify that features like Azure Update Manager, Run Command, and inventory work for both Windows and Linux, and provide links or notes about Linux-specific usage where relevant.
  • Balance the introductory discussion so that both Windows and Linux audiences see their familiar tools and workflows represented.
GitHub Create Pull Request
Azure Arc Manage and maintain the Azure Connected Machine agent ...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium 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 provides both Windows and Linux instructions for all major agent lifecycle operations (install, upgrade, uninstall, proxy config). However, Windows-specific tools and patterns (Control Panel, Msiexec, PowerShell, Group Policy, WSUS, Configuration Manager) are described in greater detail, with more step-by-step guidance and context than their Linux equivalents. Windows examples and sections are frequently presented first, and PowerShell is used heavily for Windows automation, while Linux instructions are more concise and rely on standard package manager commands. The Linux sections are present and functional, but lack the depth and troubleshooting detail provided for Windows.
Recommendations
  • Add more detailed Linux troubleshooting and automation guidance, similar to the Windows sections (e.g., scripting upgrades/uninstalls, handling package manager errors).
  • Provide parity in step-by-step instructions for Linux package manager configuration and agent management, including links to relevant Linux admin tools and best practices.
  • Include Linux-first examples in some sections, or alternate the order of Windows and Linux instructions to avoid implicit prioritization.
  • Expand on Linux-specific update infrastructure (e.g., using unattended-upgrades, cron jobs, or configuration management tools like Ansible or Chef) for agent lifecycle management.
  • Ensure that advanced scenarios (e.g., proxy configuration, environment variable migration) are equally covered for both platforms, with troubleshooting tips for Linux.
GitHub Create Pull Request
Azure Arc Cloud-native scripting and task automation with Azure Arc-enabled servers ...-arc/servers/cloud-native/scripting-task-automation.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools and patterns (RDP, PowerShell, SCCM, Task Scheduler) are mentioned first and more frequently, while Linux equivalents (SSH, cron) are referenced less prominently. Examples and explanations often default to Windows-centric workflows, with limited explicit Linux scripting or automation examples. There is mention of Linux support (SSH, Entra authentication), but practical Linux-specific examples and tool parity are lacking.
Recommendations
  • Add explicit Linux scripting examples (e.g., Bash scripts, use of cron for scheduling) alongside PowerShell examples.
  • Mention Linux-native tools and patterns (cron, systemd timers) when discussing automation and scheduling, not just Windows Task Scheduler or SCCM.
  • Provide sample commands for Linux environments using Bash or Python, not only PowerShell.
  • Ensure that examples and explanations alternate or balance Windows and Linux scenarios, rather than defaulting to Windows-first.
  • Clarify any feature limitations or differences between Windows and Linux Arc-enabled servers.
GitHub Create Pull Request
Azure Arc Azure Connected Machine Agent Deployment Options .../main/articles/azure-arc/servers/deployment-options.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation lists both Linux and Windows as supported OS types for most onboarding methods, but there is a notable emphasis on Windows-specific tools and workflows. PowerShell is highlighted as a cross-platform option, but several onboarding methods (Windows Admin Center, Configuration Manager, Group Policy) are Windows-only and presented in detail. The PowerShell onboarding method is listed before Linux-native automation tools like Ansible, and there is no explicit mention of Linux shell (bash) or native Linux configuration management tools (e.g., shell scripts, cloud-init) for onboarding. Windows-centric tooling is described in more depth, and Windows-specific methods are given dedicated sections.
Recommendations
  • Add explicit Linux shell (bash) script examples and onboarding instructions alongside PowerShell examples.
  • Include references to Linux-native automation tools (e.g., cloud-init, shell scripts, Puppet, Chef) where appropriate.
  • Ensure that Linux onboarding methods are presented with equal prominence and detail as Windows methods.
  • Clarify which onboarding steps or scripts are cross-platform and provide OS-specific guidance where necessary.
  • Consider listing Linux and Windows methods in parallel or grouping them by OS type for clarity.
GitHub Create Pull Request
Azure Arc Enable VM Extensions Using Azure Resource Manager Template ...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides ARM template examples for both Linux and Windows VM extensions, but all deployment command examples use Azure PowerShell exclusively, with no Azure CLI or Bash alternatives. This creates friction for Linux/macOS users who may prefer or require CLI or Bash-based workflows. Additionally, file path examples use Windows-style paths (e.g., D:\Azure\Templates), and the Windows custom script extension example hardcodes PowerShell usage, with no mention of Bash or shell alternatives for Linux. The documentation does mention that extensions can be deployed to Linux or Windows machines, but the operational instructions are Windows-centric.
Recommendations
  • Add equivalent Azure CLI deployment commands alongside PowerShell examples, especially for deploying ARM templates.
  • Include Linux/macOS file path examples (e.g., /home/user/Azure/Templates) where relevant.
  • Clarify that the commandToExecute parameter for Linux custom script extensions should use shell commands (e.g., bash script.sh), and provide an explicit example.
  • Add a note or section on how to perform these deployments from Linux/macOS environments, including prerequisites (e.g., Azure CLI installation).
GitHub Create Pull Request
Azure Arc Connect machines from Azure Automation Update Management ...zure-arc/servers/onboard-update-management-machines.md
Medium 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 generally describes a process that applies to both Windows and Linux machines, but several sections and examples show a Windows-first pattern. References to Azure PowerShell for status retrieval are given without equivalent Linux CLI examples, and there is a lack of explicit Linux command-line or shell examples. The runbook naming convention also puts 'Windows' first, and troubleshooting/verification steps reference PowerShell and portal workflows more familiar to Windows users.
Recommendations
  • Provide explicit Linux shell (bash) examples alongside PowerShell examples for tasks such as retrieving job statuses.
  • Mention Azure CLI commands for verification and management, not just Azure PowerShell.
  • Ensure that runbook and automation instructions clarify parity for Linux users, including any OS-specific steps.
  • Add screenshots or walkthroughs for Linux onboarding and verification, if they differ from Windows.
  • Review the order of presentation so that Windows and Linux are treated equally (e.g., alternate which OS is mentioned first, or present both together).
GitHub Create Pull Request
Azure Arc REST API Requests for the Run Command on Azure Arc-enabled Servers (Preview) ...ob/main/articles/azure-arc/servers/run-command-rest.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for REST API Requests for the Run Command on Azure Arc-enabled Servers demonstrates a notable Windows bias. All example scenarios, scripts, and references are specific to Windows Server (e.g., Windows Server 2012/R2), using PowerShell cmdlets (New-NetFirewallRule) and Windows-specific tools (New-AzStorageBlobSASToken). There are no examples, scripts, or guidance for Linux Arc-enabled servers, nor any mention of Linux shell commands or tools. The documentation assumes a Windows context throughout, creating friction for Linux users who wish to use the REST API for remote command execution.
Recommendations
  • Add parallel example scenarios for Linux Arc-enabled servers, such as configuring firewall rules using bash scripts or iptables.
  • Include sample REST API payloads with Linux shell scripts (e.g., inline bash or referencing .sh files in blob storage).
  • Mention Linux equivalents for generating SAS tokens (e.g., using Azure CLI az storage commands).
  • Clarify in the introduction that the REST API supports both Windows and Linux servers, and provide links to Linux-specific documentation if available.
  • Ensure references to tools and scripting languages are balanced between Windows and Linux contexts.
GitHub Create Pull Request
Azure Arc Migrate Azure Arc-enabled server to Azure ...rticles/azure-arc/servers/scenario-migrate-to-azure.md
Medium 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 frequently references Azure PowerShell commands and workflows, often listing PowerShell before Azure CLI. Examples and instructions for inventorying extensions and reviewing access rights are PowerShell-centric, with CLI mentioned but not exemplified. Export instructions (e.g., to CSV) are PowerShell-focused, and there is a lack of explicit Linux/macOS shell examples (e.g., Bash). While the Azure Guest Agent section does mention both Windows and Linux agents, most procedural steps and examples prioritize Windows/PowerShell tools.
Recommendations
  • Provide Bash/Azure CLI examples alongside PowerShell for all relevant steps, especially for inventorying extensions and exporting data.
  • Explicitly mention Linux/macOS workflows where applicable, such as uninstalling the Connected Machine agent or installing the Linux Guest Agent.
  • Ensure that CLI and PowerShell instructions are presented with equal prominence, or group them by platform to avoid Windows-first ordering.
  • Add notes or links for Linux/macOS users for steps that differ from Windows, such as file export formats and shell commands.
GitHub Create Pull Request
← Previous Page 51 of 94 Next →