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 2051-2075 of 2334 flagged pages
Azure Arc Whats new in Azure Arc-enabled VMware vSphere ...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents a generally balanced overview of new features for Azure Arc-enabled VMware vSphere, mentioning both Windows and Linux enhancements. However, Windows-specific features (such as customizing guest OS settings for Windows VMs and Windows Server Management) are listed before Linux-related improvements. Additionally, Azure PowerShell is referenced alongside Azure CLI and REST APIs, but there is no explicit Linux shell example or mention of Bash-specific tooling. Windows tools (like System Center Configuration Manager, Group Policy) are mentioned before Linux equivalents (Ansible), and Windows VM management features are highlighted more prominently.
Recommendations
  • Ensure Linux-related features and examples are given equal prominence and ordering as Windows features.
  • When listing management tools, mention Linux-native tools (e.g., Ansible, Bash scripts) alongside or before Windows tools.
  • Provide explicit Linux shell (Bash) examples for agent installation and VM management where PowerShell is referenced.
  • Clarify when features are Windows-only to avoid confusion for Linux users.
  • Add links or references to Linux documentation and guides where relevant.
GitHub Create Pull Request
Azure Arc Connect VMware vCenter Server to Azure Arc by using the helper script ...ere/quick-start-connect-vcenter-to-arc-using-script.md
Low Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows instructions and notes are presented first in several sections. The retry command is also shown for Windows before Linux. There is no evidence of missing Linux examples or exclusive mention of Windows tools; parity is maintained, but Windows is prioritized in ordering.
Recommendations
  • Present Windows and Linux instructions side-by-side or in parallel tabs to avoid implicit prioritization.
  • Alternate the order of Windows and Linux sections, or explicitly state that both platforms are equally supported.
  • Ensure screenshots and UI references do not assume Windows environments unless necessary.
  • Add a brief statement at the start clarifying that both Windows and Linux workstations are fully supported.
GitHub Create Pull Request
Azure Arc Delete Resources in Workload Orchestration ...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every command, but consistently presents Bash examples first. No Windows-specific tools or patterns are mentioned, and Linux parity is maintained throughout. There is a minor bias in example ordering, but all tasks are fully documented for Linux/macOS users.
Recommendations
  • Continue providing both Bash and PowerShell examples for all commands.
  • Consider explicitly stating that Bash examples are suitable for Linux/macOS terminals, and PowerShell for Windows environments.
  • Optionally, alternate the order of examples or clarify that Bash is the default for cross-platform use.
GitHub Create Pull Request
Azure Arc Staging Resources Before Deployment ...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring Linux/macOS and Windows users are covered. However, PowerShell examples are consistently shown after Bash, indicating a minor 'windows_first' bias in ordering. No Windows-only tools or patterns are used, and Linux examples are present throughout.
Recommendations
  • Consider alternating the order of Bash and PowerShell tabs in some sections to avoid implicit prioritization.
  • Explicitly mention that Bash examples are suitable for Linux/macOS and PowerShell for Windows, for clarity.
  • Ensure any troubleshooting or advanced sections also provide parity between Bash and PowerShell.
GitHub Create Pull Request
Azure Arc Solution with Multiple Shared Dependencies at Different Hierarchy Levels ...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are present throughout, and in some sections (such as variable naming and file paths), Windows conventions (e.g., backslashes in file paths) are used. Bash examples are always shown first, but the PowerShell tab is equally detailed. No Windows-only tools or patterns are used; all commands rely on the Azure CLI and Helm, which are cross-platform.
Recommendations
  • Ensure that file path examples in PowerShell use forward slashes or note that backslashes are Windows-specific.
  • Clarify that PowerShell examples are intended for Windows users, while Bash is for Linux/macOS.
  • Consider adding a brief note at the start explaining that all commands are cross-platform and that users should choose the tab matching their OS.
  • Double-check that all referenced files (e.g., YAML, JSON) are accessible and usable on both platforms.
GitHub Create Pull Request
Azure Arc Release Notes for Workload Orchestration ...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The release notes for Azure Arc Workload Orchestration generally provide cross-platform guidance, focusing on Azure CLI and portal usage. However, in the May 2025 release, CLI examples are shown exclusively in PowerShell syntax, which is Windows-centric. Bash syntax is used elsewhere, but PowerShell appears first and is the only example for configuration file operations, suggesting a mild Windows bias.
Recommendations
  • Provide equivalent Bash examples alongside PowerShell for CLI commands, especially for configuration operations.
  • Clarify that Azure CLI is cross-platform and can be used on Linux/macOS, not just Windows.
  • Ensure that CLI instructions are not presented exclusively in Windows syntax.
  • Consider alternating the order of examples or showing Bash first in some cases.
GitHub Create Pull Request
Azure Arc Solution with a Non-Leaf Target ...oad-orchestration/tutorial-service-group-scenario-2.md
Low Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are shown first, followed by PowerShell. No Windows-specific tools, patterns, or terminology are used exclusively or prioritized. All commands use the Azure CLI, which is cross-platform. There are no missing Linux examples or Windows-only instructions.
Recommendations
  • Maintain the current parity between Bash and PowerShell examples.
  • Consider explicitly stating that all examples are cross-platform and that Azure CLI works on Windows, Linux, and macOS.
  • If possible, add a brief note about using Azure CLI in macOS environments to further reassure non-Windows users.
GitHub Create Pull Request
Azure Arc Access Azure resources with managed identity on Azure Arc-enabled servers ...s/azure-arc/servers/managed-identity-authentication.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for acquiring access tokens with managed identity on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first, and PowerShell is referenced in the 'Related content' section before Azure CLI. There is a slight preference for Windows tools and ordering, but Linux parity is maintained throughout with equivalent Bash examples and links.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
  • In the 'Related content' section, list Azure CLI and Bash examples before or alongside PowerShell to balance tool visibility.
  • Explicitly state that both Windows and Linux are fully supported at the start of the article to reassure cross-platform users.
GitHub Create Pull Request
Azure Arc Connect VMware vCenter Server to Azure Arc by using the helper script ...ere/quick-start-connect-vcenter-to-arc-using-script.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the helper script, but Windows/PowerShell instructions are consistently presented first and with more detailed notes (e.g., warnings about PowerShell ISE). The retry command section also shows Windows before Linux. There is a slight emphasis on Windows tools and patterns, but Linux parity is maintained throughout.
Recommendations
  • Alternate the order of Windows and Linux instructions to avoid always showing Windows first.
  • Provide equally detailed notes for Linux users (e.g., potential issues with Bash shells or permissions).
  • Explicitly mention macOS support if applicable, or clarify if only Windows and Linux are supported.
  • Ensure screenshots and UI references are OS-neutral or include Linux/macOS equivalents if relevant.
GitHub Create Pull Request
Azure Arc Create a Solution with Multiple Dependencies with Workload Orchestration ...quickstart-solution-multiple-shared-adapter-dependency.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every CLI command and workflow step, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash examples, which is a minor 'windows_first' bias. There are no Windows-only tools, patterns, or commands used, and all instructions are cross-platform via Azure CLI and kubectl.
Recommendations
  • Consider alternating the order of Bash and PowerShell examples in sections, or explicitly state that both are equally supported.
  • Add a short note at the top clarifying that Bash is for Linux/macOS and PowerShell is for Windows, to help users quickly identify their relevant section.
  • Ensure that any future additions (e.g., troubleshooting, environment setup) include Linux/macOS-specific guidance where relevant.
GitHub Create Pull Request
Azure Arc Whats new in Azure Arc-enabled VMware vSphere ...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page lists new features for Azure Arc-enabled VMware vSphere. While it covers both Windows and Linux enhancements, Windows-specific features (such as customizing Windows VM guest settings and Windows Server Management) are mentioned before Linux equivalents. Windows tools like Azure PowerShell and System Center Configuration Manager are highlighted, and PowerShell is listed alongside Azure CLI and REST API, but Linux-focused tooling (e.g., Bash, shell scripts) is not explicitly referenced. However, Linux support is mentioned (Arc agent installation via SSH), and cross-platform SDKs and tools are covered.
Recommendations
  • Ensure Linux examples and tooling (e.g., Bash scripts, Linux-native automation tools) are mentioned alongside Windows tools.
  • When listing management tools, alternate the order or explicitly state cross-platform compatibility.
  • Add links or references to Linux-specific guides or examples where possible.
  • Clarify when features are Windows-only to avoid confusion for Linux users.
GitHub Create Pull Request
Azure Arc Multiple Solutions with a Single Shared Dependency at Different Levels ...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, but consistently lists Bash examples before PowerShell. There are no Windows-only tools or patterns used, and Linux parity is maintained throughout. No Linux/macOS examples are missing, and all commands are cross-platform via the Azure CLI and Helm.
Recommendations
  • Consider alternating the order of Bash and PowerShell tabs or explicitly stating that Bash is suitable for Linux/macOS and PowerShell for Windows.
  • Add a brief note clarifying that Bash examples are for Linux/macOS and PowerShell for Windows users, to help new users identify their platform.
  • Ensure that any future examples using platform-specific tools (e.g., Windows CMD or Linux utilities) are accompanied by their cross-platform equivalents.
GitHub Create Pull Request
Azure Arc Connect to SQL Managed Instance enabled by Azure Arc ...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page primarily references SQL Server Management Studio (SSMS), a Windows-only tool, as the first example for connecting to SQL Managed Instance enabled by Azure Arc. While it does mention sqlcmd (which is cross-platform), SSMS is listed first and no Linux-native graphical tools (such as Azure Data Studio or DBeaver) are mentioned. The examples for connecting via sqlcmd are generic and do include Linux, but the overall pattern is Windows-first in tool recommendations and examples.
Recommendations
  • Mention cross-platform SQL client tools such as Azure Data Studio, DBeaver, or Squirrel SQL alongside SSMS.
  • Provide explicit examples for connecting from Linux/macOS using graphical tools, not just sqlcmd.
  • Reorder tool recommendations so that cross-platform options are listed before or alongside Windows-only tools.
  • Clarify that SSMS is Windows-only and suggest alternatives for Linux/macOS users.
GitHub Create Pull Request
Azure Arc Install client tools ...b/main/articles/azure-arc/data/install-client-tools.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides installation instructions for client tools across platforms, but there are subtle Windows biases. Windows links are often listed first, and specific instructions for Windows (e.g., using cmd.exe instead of PowerShell for curl) are highlighted, while Linux installation instructions are less explicit or only briefly mentioned (e.g., 'Linux: install curl package'). There is a PowerShell-specific note about curl, but no equivalent Linux/macOS shell guidance. The Linux installation process for curl is not linked, and Linux/macOS users may need to search for details.
Recommendations
  • List Linux/macOS installation instructions and links before or alongside Windows, not after.
  • Provide explicit installation links for Linux/macOS tools (e.g., link to curl installation instructions for Linux/macOS).
  • Add shell-specific notes for Linux/macOS users, similar to the PowerShell note for Windows.
  • Ensure all tool installation instructions are equally detailed for all platforms.
GitHub Create Pull Request
Azure Arc Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc ...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides both Linux and Windows methods for base64 encoding, but the Windows section is more detailed, mentioning certutil and findstr, while the Linux example is brief. The Linux example is presented first, but the Windows section includes additional manual steps and commands. No PowerShell-specific examples are given, and the rest of the guide uses cross-platform tools (OpenSSL, Azure CLI, kubectl). However, the Windows encoding example lacks parity with Linux: Linux users are not told how to remove headers, and Windows users are given more guidance.
Recommendations
  • Add instructions for Linux users to remove certificate headers (e.g., using grep or sed) to match the Windows guidance.
  • Clarify that base64 encoding and header removal steps are needed on both platforms.
  • Consider providing macOS-specific notes if there are differences.
  • Ensure all steps are equally detailed for both Windows and Linux users.
GitHub Create Pull Request
Azure Arc Azure RBAC on Azure Arc-enabled Kubernetes clusters .../blob/main/articles/azure-arc/kubernetes/azure-rbac.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page provides Azure CLI and kubectl examples throughout, which are cross-platform. However, there are subtle signs of Windows bias: Windows and Mac installation instructions for Azure kubelogin are mentioned first, with Linux instructions following. The page also references the Azure portal for role assignment and Conditional Access configuration, which is equally accessible on all platforms but often associated with Windows environments. There are no PowerShell-specific commands, but the ordering of instructions and references to Windows/Mac before Linux indicate a minor Windows-first bias.
Recommendations
  • Reorder installation instructions for Azure kubelogin to mention Linux first or equally alongside Windows/Mac.
  • Explicitly state that all Azure CLI and kubectl commands are cross-platform and provide any necessary Linux/macOS-specific notes where relevant.
  • Where possible, provide parity in screenshots or UI references for Linux/macOS users (for example, browser access or Azure portal usage).
  • Ensure that any references to local file paths or SSH instructions clarify platform differences (e.g., path separators, default shell environments).
GitHub Create Pull Request
Azure Arc Azure Arc resource bridge system requirements ...icles/azure-arc/resource-bridge/system-requirements.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation consistently refers to Azure CLI installation, but in the 'Management machine requirements' section, the Azure CLI installation link defaults to the Windows tab. There are no explicit Linux/macOS examples or links, and no mention of Linux-specific installation or requirements for the management machine, despite Azure CLI being cross-platform. However, the overall guidance is generic and does not reference Windows-only tools or patterns.
Recommendations
  • Add explicit instructions or links for installing Azure CLI on Linux and macOS, not just Windows.
  • Clarify that the management machine can be Windows, Linux, or macOS, and provide parity in example commands and links.
  • Where referencing Azure CLI installation, use a neutral link or include tabs for all supported OSes.
  • If there are OS-specific requirements (e.g., 32-bit/64-bit), clarify whether these apply to Linux/macOS as well.
GitHub Create Pull Request
Azure Arc What's new with Azure Connected Machine agent ...main/articles/azure-arc/servers/agent-release-notes.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally presents Windows download links and version numbers before Linux equivalents and occasionally references Windows-specific tools (e.g., PowerShell, msiexec) and installer behaviors. However, Linux support is consistently present, and Linux-specific improvements and bug fixes are also documented. There are no critical sections that are Windows-only, and Linux users can access all relevant information.
Recommendations
  • Present Windows and Linux download links and version numbers in parallel or randomize order to avoid implicit prioritization.
  • When referencing Windows-specific installation methods (e.g., msiexec, PowerShell), provide equivalent Linux installation instructions or cross-link to Linux install documentation.
  • Where possible, clarify when a fix or feature is platform-specific to avoid confusion.
  • Consider adding a short section or table at the top summarizing parity and platform-specific differences.
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
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page lists both Windows and Linux-related endpoints and requirements, but there is a mild Windows bias. Windows-specific services (e.g., Windows NTP, sts.windows.net, login.windows.net, servicebus.windows.net) are mentioned, and Windows terminology appears in some notes. However, Linux endpoints (e.g., packages.microsoft.com, linuxgeneva-microsoft.azurecr.io) are also included. No platform-specific command examples are given, and the requirements are generally platform-agnostic. The order of some Windows-related endpoints precedes Linux equivalents, and Windows NTP is called out explicitly, but Linux NTP is not.
Recommendations
  • Explicitly mention Linux NTP server options (e.g., pool.ntp.org) alongside Windows NTP.
  • Clarify that the management machine and appliance VM can be either Windows or Linux, and provide any platform-specific notes if needed.
  • Ensure parity in endpoint explanations (e.g., for log collection, clarify if Windows and Linux logs are handled differently).
  • Where Windows-specific endpoints are listed, note Linux alternatives if applicable.
GitHub Create Pull Request
Azure Arc CLI reference for `azcmagent connect` ...b/main/articles/azure-arc/servers/azcmagent-connect.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides authentication options and examples for connecting servers to Azure Arc using the azcmagent CLI. While the core command syntax and most examples are platform-neutral, the authentication section presents 'Interactive browser login (Windows only)' as the first option and describes Windows certificate store usage in detail, including specific certificate store locations and thumbprint-based authentication. Additionally, the access token example references the Windows PowerShell cmdlet Get-AzAccessToken without mentioning Linux/macOS alternatives. These patterns indicate a mild Windows bias, though Linux authentication methods are described and supported.
Recommendations
  • Reorder authentication options so platform-neutral or Linux-default methods (e.g., device code login) are presented first.
  • When referencing access token acquisition, include cross-platform alternatives (e.g., Azure CLI az account get-access-token) alongside PowerShell.
  • Clarify certificate authentication for Linux/macOS, noting file-based certificate usage and omitting Windows certificate store details unless relevant.
  • Add explicit Linux/macOS command examples where possible, especially for authentication and certificate handling.
GitHub Create Pull Request
Azure Arc Customer intent: "As a network administrator, I want to configure secure outbound connectivity for the Azure Connected Machine agent so that I can ensure proper communication with Azure Arc while adhering to my organization's security policies." ...les/azure-arc/servers/includes/network-requirements.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux information for Azure Arc-enabled servers, but there are minor signs of Windows bias. Windows installation package URLs are listed first in tables, and Windows Admin Center is mentioned as a management tool without Linux alternatives. Windows-specific configuration issues are referenced before Linux equivalents. However, Linux is explicitly supported and referenced throughout, and critical information for Linux users is present.
Recommendations
  • In tables listing installation package URLs, alternate the order or list Linux and Windows together to avoid Windows-first bias.
  • When mentioning Windows Admin Center, clarify its Windows-specific nature and, if possible, reference Linux management alternatives (such as Azure CLI, SSH, or other tools).
  • Ensure troubleshooting and configuration sections provide Linux-specific guidance and links alongside Windows references.
  • Where Windows-specific tools or settings are discussed (e.g., TLS registry settings), provide equivalent Linux/OpenSSL guidance or links.
GitHub Create Pull Request
Azure Arc VM Extension Management with Azure Arc-Enabled Servers ...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides parity between Windows and Linux VM extensions, with separate tables for each OS and clear links to Linux-specific resources. However, Windows extensions are listed first, which may subtly prioritize Windows users. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are mentioned together, and Linux examples are present throughout. No critical Linux omissions or Windows-only tools are evident.
Recommendations
  • Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side to reinforce equal importance.
  • Explicitly state that all deployment methods (CLI, PowerShell, portal, templates) support both Windows and Linux extensions where applicable.
  • Add a brief introductory note confirming Linux parity and support, to reassure non-Windows users.
  • Ensure that linked deployment guides (e.g., CLI, PowerShell) include both Windows and Linux examples.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Connected Machine agent connection issues ...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation covers troubleshooting for both Windows and Linux Azure Connected Machine agent installations, but there is evidence of Windows bias. Windows examples and log file paths are presented first, and PowerShell-specific commands and references (such as using '&' and environment variables) are prominent. Windows log file locations and troubleshooting steps are often mentioned before Linux equivalents. There are also references to Windows-specific tools (e.g., PowerShell, '%TEMP%', '%ProgramData%') without always providing the Linux equivalent in the same context.
Recommendations
  • Present Windows and Linux examples side-by-side, or alternate which platform is shown first in each section.
  • Ensure all troubleshooting steps referencing Windows-specific tools or paths (e.g., '%TEMP%', '%ProgramData%') are immediately followed by Linux equivalents (e.g., '/tmp', '/var/opt/azcmagent').
  • Where PowerShell syntax is used, provide equivalent Bash commands for Linux users.
  • Clarify when a solution or log location is platform-specific, and provide parity for Linux wherever possible.
  • Consider using generic command syntax (e.g., 'azcmagent ...') before showing platform-specific examples.
GitHub Create Pull Request
Azure Arc Run command on Azure Arc-enabled servers (Preview) ...cs/blob/main/articles/azure-arc/servers/run-command.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions Azure CLI, PowerShell, and REST API as supported experiences, but lists PowerShell examples and references before Linux/CLI equivalents. The 'Next steps' section places PowerShell before REST API, and the custom metadata includes 'devx-track-azurepowershell' but not a Linux-specific tag. However, the page explicitly states support for both Windows and Linux, and provides links to Azure CLI documentation, which is cross-platform.
Recommendations
  • Ensure that Linux and Windows examples are given equal prominence in all sections.
  • List Azure CLI (Linux-friendly) examples before or alongside PowerShell examples in 'Next steps' and throughout the documentation.
  • Add explicit Linux-specific tags or metadata if possible.
  • Clarify that Azure CLI is fully supported and provide sample Linux shell commands where appropriate.
GitHub Create Pull Request
Azure Arc What is Azure Arc-enabled VMware vSphere? ...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides a balanced overview of Azure Arc-enabled VMware vSphere, mentioning both Windows and Linux support in several places. However, there is a mild Windows bias: Windows examples and links are sometimes presented first (e.g., in Azure Automation and Update Manager sections), and PowerShell is highlighted as a primary automation tool, with less emphasis on Bash or Linux-native scripting. Some links and examples reference Windows-specific tabs or features before Linux equivalents.
Recommendations
  • Ensure Linux examples and links are presented alongside Windows ones, not just as secondary options.
  • Highlight Bash and Linux-native scripting tools (e.g., Azure CLI usage on Linux/macOS) equally with PowerShell.
  • Where automation is discussed, mention both PowerShell and Bash/Python as first-class options.
  • Review linked pages to ensure Linux instructions are easily discoverable and not hidden behind Windows-first tabs.
  • Add explicit statements or examples showing Linux VM onboarding and management parity.
GitHub Create Pull Request
← Previous Page 83 of 94 Next →