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 2151-2175 of 2334 flagged pages
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-10 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 sqlcmd is mentioned and a Linux-compatible example is provided, SSMS is consistently listed first and no Linux-native GUI tools (such as Azure Data Studio or DBeaver) are referenced. The documentation does not provide parity in client tool recommendations or examples for Linux/macOS users, potentially creating friction for those not on Windows.
Recommendations
  • Mention cross-platform SQL client tools such as Azure Data Studio or DBeaver alongside SSMS.
  • Provide explicit examples for connecting with sqlcmd on Linux/macOS, including any OS-specific authentication or encoding requirements.
  • List Linux/macOS-compatible tools before or alongside SSMS to avoid 'windows_first' bias.
  • 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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation generally aims for cross-platform parity, but there are subtle signs of Windows bias. In the installation links for tools like kubectl and curl, Windows is listed first, and the Linux installation instructions are less explicit (e.g., 'Linux: install curl package' vs. a direct link for Windows). There is also a note specifically about using cmd.exe instead of PowerShell on Windows, and a PowerShell-specific note about curl, but no equivalent Linux/macOS notes or troubleshooting tips. No explicit Linux/macOS command examples are provided.
Recommendations
  • List installation options for all platforms in parallel order (e.g., Windows, Linux, macOS) or rotate the order to avoid always listing Windows first.
  • Provide direct installation links for Linux and macOS tools (e.g., link to curl installation instructions for Linux and macOS, not just Windows).
  • Include Linux/macOS-specific notes or troubleshooting tips where Windows-specific notes are given (e.g., clarify curl behavior on Linux shells if needed).
  • Add example commands for Linux/macOS where Windows-specific command-line nuances are discussed.
GitHub Create Pull Request
Azure Arc Features and Capabilities of SQL Managed Instance enabled by Azure Arc ...n/articles/azure-arc/data/managed-instance-features.md
Low Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation references several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and highlights PowerShell scripting support as a manageability feature. However, it also mentions cross-platform tools (Azure CLI, Visual Studio Code extension) and notes that Azure PowerShell is not supported. There are no explicit Windows-first examples or missing Linux-specific examples, but the tool listing is weighted toward Windows tools.
Recommendations
  • Add explicit mention of cross-platform alternatives for Windows tools, such as Azure Data Studio (which runs on Linux/macOS), and clarify which tools are available on Linux/macOS.
  • Include examples or links for using SQL Managed Instance enabled by Azure Arc from Linux/macOS environments, such as using Azure CLI or VS Code.
  • Consider listing cross-platform tools before Windows-only tools in the Tools section.
  • Clarify PowerShell scripting support: specify if cross-platform PowerShell (pwsh) is supported or if only Windows PowerShell is relevant.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent, with clear parity in most features and fixes. However, Windows download links and version numbers are consistently listed first, and Windows-specific installer instructions (e.g., PowerShell, msiexec, UAC) are detailed while Linux equivalents are not. Some bug fixes and improvements reference Windows tools (e.g., PowerShell scripts, MSI installer) without mentioning Linux alternatives or providing comparable Linux instructions.
Recommendations
  • Alternate the order of Windows and Linux download links and version numbers to avoid implicit prioritization.
  • Provide Linux-specific installer troubleshooting guidance (e.g., using RPM or DEB commands, sudo usage) in the Known Issues section, similar to the Windows installer instructions.
  • When referencing Windows tools/scripts (e.g., PowerShell, MSI), mention Linux equivalents (e.g., Bash scripts, RPM/DEB installers) where applicable.
  • Ensure that bug fixes and improvements for Linux are described with equal detail as Windows, especially when referencing OS-specific behaviors.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references Azure CLI, PowerShell, and REST API as supported experiences, but PowerShell is mentioned alongside Azure CLI in metadata and navigation, potentially prioritizing Windows-centric tooling. The 'Next steps' section lists PowerShell before REST API, and the metadata includes 'devx-track-azurepowershell', which may signal a Windows-first approach. However, the page clearly states support for both Windows and Linux, and notes a Linux-specific limitation. No Linux-specific examples or tools (e.g., Bash) are highlighted, and there are no Linux-first instructions.
Recommendations
  • Ensure Linux/Bash examples are included and visible in main documentation and navigation.
  • Balance PowerShell and Azure CLI examples with Bash or shell script examples for Linux users.
  • Explicitly mention Linux support in introductory sections and provide Linux-specific guidance where relevant.
  • Consider listing Azure CLI (cross-platform) before PowerShell in navigation and 'Next steps' to avoid Windows-first impression.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides troubleshooting guidance for both Windows and Linux, but Windows examples and terminology are often presented first or in greater detail. PowerShell and Windows-specific paths and tools are referenced, sometimes before their Linux equivalents. The log file locations and installation error codes are clearly separated for Windows and Linux, but Windows commands are shown first and in more detail. The severity of the bias is low, as Linux examples and information are present and Linux users can complete all tasks.
Recommendations
  • Alternate the order of Windows and Linux sections/examples so Linux is not always second.
  • Provide Linux examples before or alongside Windows examples, especially in critical sections.
  • Ensure that troubleshooting steps reference Linux tools and paths equally (e.g., mention sudo and Linux log locations alongside Windows equivalents).
  • Where PowerShell is used for Windows, clarify the equivalent Bash or shell command for Linux.
  • Add explicit notes for Linux users where Windows-specific terminology (e.g., 'elevated command prompt') is used.
GitHub Create Pull Request
Azure Arc Set Up Workload Orchestration .../workload-orchestration/initial-setup-configuration.md
Low Priority View Details →
Scanned: 2026-02-10 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 steps, but the Bash tab is presented first. There are no Windows-specific tools, patterns, or exclusive references; all commands use the cross-platform Azure CLI. No Linux/macOS examples are missing, and no Windows-only tools are required.
Recommendations
  • Consider alternating the order of Bash and PowerShell tabs across related documentation pages to avoid a consistent 'Windows-first' impression.
  • Explicitly note that all examples are cross-platform and that Azure CLI is supported on Windows, Linux, and macOS.
  • If possible, clarify in the introduction that both Windows (PowerShell) and Linux/macOS (Bash) users are fully supported.
GitHub Create Pull Request
Azure Arc What's new in Azure Arc-enabled VMware vSphere ...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page lists new features for Azure Arc-enabled VMware vSphere. While most features are platform-neutral or mention both Windows and Linux, there is a tendency to mention Windows-specific features (such as customizing Windows VM guest settings and Windows Server Management) before Linux equivalents. Windows tools (System Center Configuration Manager, Group Policy) are mentioned for agent installation, but Linux tools (Ansible) are also included. Azure PowerShell is listed after Azure CLI and REST APIs, showing some parity. Overall, minor Windows bias is present, but Linux users can complete all tasks.
Recommendations
  • Ensure Linux-related features (such as guest customization for Linux VMs) are mentioned alongside Windows features where applicable.
  • When listing agent installation methods, consider mentioning Linux-native tools (like Ansible) before or alongside Windows tools.
  • Add explicit examples or links for Linux guest customization if supported.
  • Maintain parity in SDK and tool coverage for both Windows and Linux platforms.
GitHub Create Pull Request
Azure Arc Create a Solution with Shared Adapter Dependency with Workload Orchestration ...ation/quickstart-solution-shared-adapter-dependency.md
Low Priority View Details →
Scanned: 2026-02-10 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 CLI steps, ensuring parity for Linux/macOS and Windows users. However, in most sections, Bash examples are presented before PowerShell, which is a minor 'windows_first' bias (since PowerShell is the Windows shell, but Bash is shown first). There are no Windows-specific tools, patterns, or commands used, and no missing Linux examples.
Recommendations
  • Maintain the current structure, as Bash and PowerShell parity is excellent.
  • Consider alternating the order of Bash and PowerShell tabs or explicitly stating that Bash is for Linux/macOS and PowerShell for Windows to clarify cross-platform support.
  • Ensure that any future examples or troubleshooting steps continue to provide both Bash and PowerShell versions.
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-10 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 consistently presented before PowerShell, which is a minor 'windows_first' bias in ordering. No exclusive Windows tools, PowerShell-heavy content, or missing Linux examples are present.
Recommendations
  • Maintain the current parity of Bash and PowerShell examples.
  • Consider alternating the order of Bash and PowerShell tabs in some sections, or clarify that both are equally supported.
  • Explicitly mention that all commands are cross-platform and supported on both Linux/macOS and Windows environments.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for every step, but consistently presents Bash examples first. There is no evidence of Windows-only tools or patterns; all commands use the Azure CLI and Helm, which are cross-platform. PowerShell examples are included throughout, which may be seen as catering to Windows users, but Linux/macOS users are fully supported via Bash. No Linux-specific examples or troubleshooting are missing.
Recommendations
  • Maintain Bash examples first, as Bash is the default shell for Linux/macOS.
  • Consider adding a brief note clarifying that all commands are cross-platform and that Bash is recommended for Linux/macOS users, while PowerShell is for Windows users.
  • Optionally, include a short section on troubleshooting common cross-platform issues (e.g., file path differences, quoting) for users switching between Bash and PowerShell.
  • Ensure that file path examples use forward slashes in Bash and backslashes in PowerShell, as appropriate, to avoid confusion.
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-10 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 PowerShell examples are consistently shown after Bash. There are no Windows-only tools or patterns, and Linux parity is maintained throughout. No critical steps are Windows-only, and all commands are cross-platform via the Azure CLI and Helm.
Recommendations
  • Consider alternating the order of Bash and PowerShell tabs in some sections to avoid implicit prioritization.
  • Explicitly state that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users quickly identify their relevant environment.
  • Add a brief note at the start clarifying that all steps are cross-platform unless otherwise noted.
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-09 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 each command, but consistently presents Bash examples before PowerShell. There are no Windows-specific tools or patterns mentioned, and Linux parity is maintained throughout. No critical sections are Windows-only.
Recommendations
  • Continue to provide both Bash and PowerShell examples for all commands.
  • Consider clarifying that Bash examples are suitable for Linux/macOS users, and PowerShell for Windows users, to further assist cross-platform readers.
  • If possible, add notes about running Azure CLI on different platforms (Windows, Linux, macOS) and any platform-specific considerations.
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-09 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 dedicated tables for each OS and clear links to relevant information. However, Windows extensions are presented first, which may subtly prioritize Windows users. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are mentioned equally, and partner extensions are shown for both OSes. No critical Linux examples or tools are missing.
Recommendations
  • Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side to reinforce parity.
  • Explicitly state that all deployment methods (CLI, PowerShell, portal, ARM templates) are fully supported for both Windows and Linux, perhaps with example links for each.
  • Ensure that future updates continue to provide equal detail and links for both OSes.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation references SQL Server Management Studio (SSMS) as the primary GUI tool for connecting, which is Windows-only, and mentions it before the cross-platform sqlcmd tool. However, the main CLI example for connecting uses sqlcmd, which is available on both Windows and Linux. There are no Linux-specific connection examples (e.g., using Azure Data Studio or other Linux-native tools), and SSMS is referenced as the default GUI option. The Azure CLI commands shown are cross-platform, but the documentation does not highlight Linux/macOS client options or workflows.
Recommendations
  • Mention Azure Data Studio as a cross-platform GUI alternative to SSMS for connecting to SQL Managed Instance.
  • Provide explicit Linux/macOS connection examples, including any prerequisites (e.g., installing sqlcmd or Azure Data Studio).
  • Clarify that SSMS is Windows-only and recommend cross-platform tools for non-Windows users.
  • Consider showing Linux/macOS examples first or alongside Windows examples to avoid implicit Windows-first bias.
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-09 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 links for client tools across Windows, Linux, and macOS, but Windows links are often listed first. There are Windows-specific notes (e.g., using cmd.exe instead of PowerShell for curl), and Linux installation instructions for curl are less explicit (just 'install curl package'). There is also a PowerShell-specific note about curl aliasing, but no equivalent Linux/macOS shell guidance. Overall, Linux/macOS users can complete the tasks, but Windows is prioritized and Linux guidance is less detailed.
Recommendations
  • List installation links for all platforms in parallel order (e.g., Windows, Linux, macOS) or rotate which platform is listed first.
  • Provide explicit Linux/macOS installation instructions for curl (e.g., 'sudo apt-get install curl' or 'brew install curl').
  • Add shell-specific notes for Linux/macOS where relevant (e.g., bash/zsh differences for curl).
  • Balance PowerShell-specific notes with equivalent Linux/macOS shell guidance.
  • Ensure all examples and guidance are equally detailed for all platforms.
GitHub Create Pull Request
Azure Arc Features and Capabilities of SQL Managed Instance enabled by Azure Arc ...n/articles/azure-arc/data/managed-instance-features.md
Low Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation references several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and explicitly lists PowerShell scripting support as a manageability feature. However, it also mentions cross-platform tools (Azure CLI, Visual Studio Code extension) and does not present Windows examples before Linux equivalents, nor does it omit Linux support for critical tasks. No explicit Windows-first ordering or missing Linux examples are observed.
Recommendations
  • Clarify which tools are cross-platform (e.g., Azure CLI, VS Code extension) and which are Windows-only (e.g., SSMS, SQL Server PowerShell, SQL Server Profiler).
  • Add references to Linux/macOS-compatible management tools, such as 'sqlcmd', Azure Data Studio, or other CLI utilities.
  • Explicitly state PowerShell scripting support is limited to Windows, and suggest Bash or other scripting alternatives for Linux/macOS users.
  • Where possible, provide links or guidance for Linux/macOS users to achieve similar manageability and scripting tasks.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides authentication options for both Windows and Linux, but the 'Interactive browser login' is described as 'Windows only' and is listed first. Windows certificate store options are explained in detail, while Linux equivalents are not mentioned. The access token example references a Windows PowerShell cmdlet ('Get-AzAccessToken') without mentioning Linux alternatives. Overall, Linux is supported, but Windows-specific tools and flows are presented first or exclusively.
Recommendations
  • Present authentication options in a neutral order (e.g., device code login first, since it's default for Linux).
  • When referencing Windows certificate stores, add a note about Linux certificate file storage and permissions.
  • For access token acquisition, mention cross-platform methods (e.g., Azure CLI 'az account get-access-token') alongside PowerShell.
  • Add explicit Linux/macOS examples where Windows-specific tools or flows are described.
  • Clarify that all examples work on both Windows and Linux unless otherwise noted.
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-09 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 files when creating Kubernetes secrets, but the Windows-specific instructions (using certutil and findstr) are more detailed and appear after the Linux example. However, the Linux example is brief and does not address decoding or removing headers, while the Windows example does. The rest of the guide uses cross-platform tools (OpenSSL, Azure CLI, kubectl) and does not show Windows bias.
Recommendations
  • Expand Linux instructions for base64 encoding/decoding to match the detail provided for Windows (e.g., how to decode, how to remove headers if needed).
  • Mention that base64 encoding/decoding can be done on macOS using the same Linux commands.
  • Consider providing a PowerShell example for base64 encoding/decoding for Windows users, but also ensure parity with Linux/macOS shell commands.
  • Clarify that OpenSSL, Azure CLI, and kubectl are cross-platform and provide links or notes for installation on all OSes.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation references Azure CLI installation with links that default to Windows instructions and mentions Azure CLI x64/32-bit requirements without clarifying Linux/macOS support. However, it does not provide Windows-specific commands or tools, and the CLI commands shown are cross-platform. No explicit Linux/macOS examples or installation guidance are given, but there is no critical Windows-only content.
Recommendations
  • Add explicit guidance for installing Azure CLI on Linux and macOS, including relevant links.
  • Clarify that the management machine can be Linux, macOS, or Windows, and specify any OS-specific requirements.
  • Provide example CLI commands and file paths for Linux/macOS environments.
  • Ensure parity in documentation for management machine prerequisites and troubleshooting steps across platforms.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Windows/PowerShell examples before Linux/Bash equivalents in the critical 'Acquire an access token using REST API' section. The PowerShell example is more visually prominent, with a screenshot and detailed explanation preceding the Bash example. Windows group membership requirements are listed before Linux equivalents in prerequisites. References to PowerShell are made before Azure CLI in related content.
Recommendations
  • Present Linux/Bash and Windows/PowerShell examples side-by-side or alternate their order to avoid Windows-first bias.
  • Ensure screenshots and example outputs for both platforms are equally prominent.
  • List Linux prerequisites before or alongside Windows prerequisites.
  • Mention Azure CLI and Bash examples before or alongside PowerShell in related content.
  • Consider adding parity notes or clarifications for macOS users where relevant.
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-09 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 and Windows parity. However, in some sections, PowerShell examples are shown immediately after Bash, and in a few cases, minor Windows-specific notes (such as carriage return handling) are included. The Bash examples are consistently presented first, and Linux-specific instructions (such as base64 encoding) are given. No Windows-only tools or patterns are used, and Linux users can complete all tasks without friction.
Recommendations
  • Maintain Bash and PowerShell parity for all steps.
  • Ensure Linux-specific notes (such as file encoding, base64 commands) are clearly marked.
  • Consider clarifying that Bash examples are suitable for Linux/macOS, and PowerShell for Windows, to help users select the right tab.
  • If possible, add a brief introductory note indicating cross-platform support.
  • Continue to avoid Windows-only tools or commands unless the feature is Windows-specific.
GitHub Create Pull Request
Azure Arc What's new in Azure Arc-enabled VMware vSphere ...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page presents new features for Azure Arc-enabled VMware vSphere. While most features are platform-neutral, there are instances where Windows-specific features or tools are mentioned first or exclusively. For example, the June 2025 update highlights customization for Windows VMs, and Windows Server Management is detailed in January 2025. In October 2024, Windows-centric tools like System Center Configuration Manager and Group Policy are listed before Linux-friendly options like Ansible. Azure PowerShell is also listed alongside Azure CLI and REST APIs, but not prioritized. Linux-specific features are present (e.g., SSH-based Arc agent installation), but Windows examples and tools tend to appear first or are more detailed.
Recommendations
  • Ensure Linux and Windows features are presented with equal prominence and detail.
  • When listing at-scale agent installation methods, mention Linux-friendly tools (e.g., Ansible, Bash scripts) before or alongside Windows tools.
  • Provide explicit examples or links for Linux/macOS users where Windows tools (e.g., Group Policy, SCCM) are referenced.
  • Consider alternating the order of Windows and Linux features in release notes to avoid implicit prioritization.
GitHub Create Pull Request
Azure Arc External Validation for Workload Orchestration ...zure-arc/workload-orchestration/external-validation.md
Low Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples throughout, ensuring parity for Linux/macOS and Windows users. However, in several sections, PowerShell examples are presented immediately after Bash, rather than in parallel tabs or with equal prominence. There are no Windows-specific tools or patterns used; all commands rely on the Azure CLI, which is cross-platform. No critical steps are Windows-only, and Linux users can complete all tasks as described.
Recommendations
  • Consider presenting Bash and PowerShell examples in parallel tabs or with equal prominence, rather than consistently listing Bash first.
  • Explicitly mention that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Add a brief note at the start clarifying that both Bash and PowerShell are supported, and users should select the shell appropriate for their OS.
GitHub Create Pull Request
← Previous Page 87 of 94 Next →