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 2076-2100 of 2334 flagged pages
Azure Arc Plan for deployment ...phere/support-matrix-for-arc-enabled-vmware-vsphere.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 and Linux requirements for guest management, but Windows tools (.NET Framework, PowerShell) are listed first and in more detail, including download links. Linux requirements are mentioned briefly and lack equivalent detail or links. The Windows download links are provided, but Linux equivalents (such as wget or systemd documentation) are not. No Linux-specific example scripts or troubleshooting guidance are given, and Windows tools are mentioned before Linux tools.
Recommendations
  • Provide download links or documentation references for Linux tools (e.g., wget, systemd).
  • List Linux requirements before or alongside Windows requirements, rather than after.
  • Add example installation scripts for both Windows (PowerShell) and Linux (bash), or clarify that both are supported with parity.
  • Include troubleshooting guidance for Linux environments, similar to any provided for Windows.
  • Ensure parity in detail and clarity for both Windows and Linux prerequisites.
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-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 all commands, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown immediately after Bash, which is a minor form of 'windows_first' bias. No Windows-specific tools or patterns are used, and Linux examples are present throughout.
Recommendations
  • Consider alternating the order of Bash and PowerShell examples in different sections to avoid implicit prioritization.
  • Explicitly state that Bash examples are suitable for Linux/macOS terminals and PowerShell for Windows, to clarify cross-platform applicability.
  • Add a brief note confirming that all commands are supported equally on Linux, macOS, and Windows when using Azure CLI.
GitHub Create Pull Request
Azure Arc Set Up Workload Orchestration .../workload-orchestration/initial-setup-configuration.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 all steps, but the Bash tab is presented first, followed by PowerShell. No Windows-specific tools or patterns are mentioned exclusively, and all commands use the Azure CLI, which is cross-platform. There are no missing Linux examples, and no Windows tools are referenced. The PowerShell examples are provided for parity, but Bash is prioritized in tab order.
Recommendations
  • Consider clarifying that both Bash and PowerShell examples are fully supported on Windows, Linux, and macOS, as Azure CLI works across platforms.
  • Explicitly mention that Bash examples can be used on Linux/macOS, and PowerShell on Windows, but both shells are available on all platforms.
  • If possible, provide a brief note about how to install Azure CLI on Linux/macOS for completeness.
  • Ensure that tab order does not imply platform preference, or rotate tab order periodically.
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-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 all CLI operations, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently presented immediately after Bash, which could be interpreted as a minor 'windows_first' bias. No Windows-specific tools, patterns, or exclusive instructions are present, and all steps are equally applicable to Linux/macOS environments via Bash and Azure CLI.
Recommendations
  • Consider alternating the order of Bash and PowerShell examples in different sections, or explicitly state that Bash is suitable for Linux/macOS and PowerShell for Windows.
  • Add a brief note clarifying that all Azure CLI commands are cross-platform and Bash examples are intended for Linux/macOS users.
  • Ensure screenshots and portal instructions do not reference Windows-specific UI elements unless necessary.
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-15 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 all major steps, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash, and some PowerShell-specific commands (such as base64 encoding) are included. There are minor instances where Windows-specific file encoding (UTF-8 with BOM) is mentioned, but Linux/Mac equivalents are also addressed. No critical steps are Windows-only, and Linux users can complete all tasks using the Bash instructions.
Recommendations
  • Continue providing both Bash and PowerShell examples for all commands.
  • Consider explicitly stating that Bash examples are suitable for Linux/macOS and PowerShell for Windows at the start of the page.
  • Where file encoding is discussed, clarify how to check/change encoding on Linux/macOS (e.g., using 'file' or 'iconv').
  • Ensure that any command or tool referenced (such as 'armclient' in PowerShell) has a Linux/macOS equivalent or a note if it is Windows-only.
  • If possible, provide a combined table or toggle for Bash/PowerShell examples to make parity clearer.
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-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 variable definition, ensuring parity between Linux/macOS and Windows users. However, in most sections, Bash examples are presented before PowerShell, which is a minor 'windows_first' bias. There are no Windows-exclusive tools, patterns, or terminology, and Linux examples are not missing.
Recommendations
  • Maintain the current parity by continuing to provide both Bash and PowerShell examples.
  • Consider alternating the order of Bash and PowerShell examples in future documentation, or explicitly state that Bash is shown first for consistency, not preference.
  • Ensure that any future additions (e.g., troubleshooting, environment setup) include Linux/macOS guidance alongside Windows instructions.
GitHub Create Pull Request
Azure Arc Create a Basic Solution with Common Configurations with Workload Orchestration ...ation/quickstart-solution-with-common-configuration.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 Bash and PowerShell examples for every step, but PowerShell examples are consistently shown after Bash. There is a slight bias in the sense that PowerShell is given equal prominence, even though Bash is the more universal shell for Linux/macOS users. No Windows-only tools or patterns are used, and all commands are based on the Azure CLI, which is cross-platform. There are no missing Linux examples, and no Windows-specific tools are mentioned.
Recommendations
  • Consider clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users choose the right tab.
  • Optionally, add a short note in the prerequisites section indicating that all CLI commands work on Linux, macOS, and Windows, and that users should select the appropriate shell tab.
  • Ensure that any environment setup instructions in linked prerequisite docs also provide Linux/macOS parity.
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-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, ensuring parity between Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash examples, which is a minor 'windows_first' bias. No Windows-specific tools or patterns are used, and all commands are cross-platform (az CLI, Helm). No critical sections are Windows-only.
Recommendations
  • Maintain the current structure, as Bash and PowerShell parity is good.
  • Consider clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users quickly identify their relevant section.
  • If possible, add a note at the top indicating that all commands are cross-platform unless otherwise specified.
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-15 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 between 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. There is no evidence of Windows-only tools or missing Linux examples; all commands use the Azure CLI, which is 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 for Windows users and Bash for Linux/macOS, if not already stated.
  • Consider adding a note that all Azure CLI commands are cross-platform and can be run in Bash or PowerShell on any OS.
  • If possible, provide additional context for macOS users regarding any potential differences in shell behavior.
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-14 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, and occasionally references Windows-specific tools (e.g., PowerShell, msiexec) and issues. However, Linux is well-represented with dedicated download links, release notes, and Linux-specific improvements. There are a few minor instances where Windows tools or patterns are mentioned without Linux equivalents, but Linux users are not blocked from completing tasks.
Recommendations
  • Alternate the order of Windows and Linux download links or present them together to avoid a 'Windows-first' impression.
  • Where Windows-specific installation instructions or troubleshooting steps are given (e.g., using msiexec or PowerShell), consider providing equivalent Linux instructions or explicitly stating when an issue is Windows-only.
  • When referencing scripts or tools (e.g., ExtensionCleanup.ps1), clarify if a Linux equivalent exists or note that it is Windows-only.
  • Continue to highlight Linux-specific improvements and fixes to reinforce parity.
GitHub Create Pull Request
Azure Arc Set Up Workload Orchestration .../workload-orchestration/initial-setup-configuration.md
Low Priority View Details →
Scanned: 2026-02-14 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 setting up workload orchestration, but the Bash tab is presented first, followed by PowerShell. There are no Windows-specific tools or patterns used; all commands rely on the Azure CLI, which is cross-platform. No Linux/macOS examples are missing, and there is no exclusive mention of Windows tools. The PowerShell examples are provided for parity, but the Bash examples are shown first, which is a minor bias in favor of Linux/macOS users rather than Windows.
Recommendations
  • Ensure that both Bash and PowerShell examples are equally accessible, perhaps by defaulting to the user's OS or by providing clear guidance for both platforms.
  • Consider adding a note clarifying that Azure CLI commands are cross-platform and can be used on Windows, Linux, and macOS.
  • If possible, provide a brief section explaining how to install Azure CLI on all supported platforms.
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-14 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 are presented first in each relevant section. All critical steps and commands are available for Linux users, and Linux parity is maintained throughout. The only minor bias is the ordering of Windows instructions before Linux.
Recommendations
  • Present Windows and Linux instructions in parallel (side-by-side tabs or columns) or alternate which OS is shown first.
  • Explicitly mention macOS compatibility if the Bash script works on macOS.
  • Clarify that both PowerShell and Bash scripts are functionally equivalent and supported.
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-14 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, but PowerShell examples are consistently shown after Bash examples. There are no Windows-only tools or patterns; all commands use cross-platform Azure CLI and kubectl. No critical steps are Windows-only, and Linux parity is maintained. The only minor bias is that Bash (Linux/macOS) examples are always presented first, with PowerShell (Windows) second.
Recommendations
  • Consider alternating the order of Bash and PowerShell examples in some sections to avoid implicit prioritization.
  • Explicitly state that both Bash and PowerShell are supported on Windows, Linux, and macOS, and that users can choose either based on their environment.
  • Add a short note at the top clarifying that all commands are cross-platform and that PowerShell Core is available on Linux/macOS.
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-14 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 between Linux/macOS and Windows users. However, in each section, Bash examples are presented first, followed by PowerShell. There are no Windows-specific tools or patterns, and all commands use the Azure CLI, which is cross-platform. No critical steps are Windows-only, and Linux users can fully complete the tutorial.
Recommendations
  • Maintain Bash-first ordering, as it is inclusive for Linux/macOS users.
  • Continue providing both Bash and PowerShell examples for all steps.
  • If possible, clarify that Azure CLI commands are cross-platform and can be run on any OS.
  • Consider adding a brief note at the top indicating that both Linux/macOS and Windows environments are supported.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation 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 presented as the default/favored client. There is no mention of other cross-platform or Linux-native SQL clients (e.g., DBeaver, Azure Data Studio). The documentation does not provide PowerShell examples, but the Windows bias is evident in tool selection and ordering.
Recommendations
  • Mention cross-platform SQL clients such as Azure Data Studio, DBeaver, or Squirrel SQL alongside SSMS.
  • Provide explicit examples for connecting from Linux/macOS using GUI tools (e.g., Azure Data Studio) in addition to sqlcmd.
  • Reorder examples so that cross-platform tools are listed first or equally with SSMS.
  • Clarify that SSMS is Windows-only and suggest alternatives for Linux/macOS users.
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-14 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 Profiler, SQL Server PowerShell) and mentions PowerShell scripting support as a manageability feature. However, it also lists cross-platform tools (Azure CLI, VS Code extension) and notes that Azure PowerShell is not supported. No explicit Linux/macOS examples or tools are provided, but the page does not prioritize Windows tools over Linux equivalents in critical workflows.
Recommendations
  • Add explicit mention of Linux/macOS-compatible management tools (e.g., Azure Data Studio, sqlcmd, mssql-cli).
  • Provide examples or links for using SQL Managed Instance enabled by Azure Arc from Linux/macOS environments.
  • Clarify which tools are cross-platform and which are Windows-only.
  • Include sample workflows for Linux users (e.g., using Azure CLI or VS Code extension on Linux).
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page lists connectivity requirements for Azure Arc Resource Bridge, including both Windows and Linux-related endpoints. However, there is a mild bias toward Windows: Windows NTP server ('time.windows.com') is mentioned explicitly, and several endpoints reference 'windows.net' and 'windows.com'. Windows-specific notes (e.g., Hyper-V default NTP) are present, but Linux equivalents (such as ntp.org or chrony) are not mentioned. The Azure CLI installation section references downloading the installer but does not clarify Linux/macOS installation differences. Windows-related endpoints are listed before Linux endpoints in some cases.
Recommendations
  • Add Linux/macOS NTP server examples (e.g., ntp.org, pool.ntp.org) alongside 'time.windows.com', and clarify when Windows NTP is relevant.
  • Clarify Azure CLI installation requirements for Linux/macOS, including relevant URLs or package managers (apt, yum, brew).
  • Ensure Linux-specific endpoints (such as 'packages.microsoft.com') are given equal prominence and explanation.
  • Where Windows-specific notes are given (e.g., Hyper-V default NTP), add Linux-specific notes (e.g., default NTP behavior on Ubuntu/CentOS).
  • Consider listing Linux and Windows endpoints/examples together, rather than Windows-first.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation is generally cross-platform, but there are subtle signs of Windows bias. Azure CLI is used throughout, which is available on all platforms, but installation instructions and links often mention Windows or Mac first, with Linux instructions appearing later or being less detailed. In the section on Azure kubelogin, Windows/Mac installation instructions are mentioned before Linux, and Linux instructions are less explicit. There are no PowerShell-specific commands, but Azure CLI is sometimes associated with Windows usage. No Linux-specific tools or patterns are mentioned, and some steps (such as SSH into master nodes, editing files, and using kubectl) are generic, but could benefit from more explicit Linux guidance. Overall, Linux users can complete all tasks, but may encounter minor friction.
Recommendations
  • Ensure Linux installation instructions are as prominent and detailed as Windows/Mac instructions, especially for tools like Azure kubelogin.
  • Provide explicit Linux command examples for common tasks (e.g., editing files with nano as well as vi, handling file permissions, SSH usage).
  • When referencing Azure CLI, clarify that it is fully supported on Linux and provide links to Linux-specific installation guides.
  • Avoid mentioning Windows/Mac first in tool installation sections; present all platforms equally or start with Linux.
  • Add troubleshooting tips for Linux environments where relevant (e.g., file permissions, sudo usage).
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-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation references Azure CLI installation with a link that defaults to Windows instructions and mentions Azure CLI x64/32-bit requirements, but does not specify Linux/macOS equivalents or provide parity in example links. No explicit Windows-only tools or PowerShell commands are used, and the CLI commands are cross-platform. However, the documentation could be improved by clarifying Linux/macOS support and providing relevant links.
Recommendations
  • Add explicit mention that Azure CLI is cross-platform and supported on Windows, Linux, and macOS.
  • Provide links to Azure CLI installation instructions for Linux and macOS alongside the Windows link.
  • Clarify that management machine requirements (such as Azure CLI x64) apply equally to Linux/macOS, or specify any OS-specific caveats.
  • Include example CLI commands run on Linux/macOS, or note that the commands are identical across platforms.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides comprehensive coverage for both Windows and Linux VM extensions, including separate tables for each OS and partner extensions. However, Windows extensions are listed first, which may subtly reinforce Windows as the default or primary platform. All deployment methods (CLI, PowerShell, portal, ARM templates) are mentioned equally, and Linux examples are not missing. No critical sections are Windows-only.
Recommendations
  • Consider alternating the order of Windows and Linux sections, or explicitly state that both are equally supported.
  • Add a brief introductory note clarifying that Azure Arc-enabled servers support both Windows and Linux extensions equally.
  • Ensure that linked deployment guides (e.g., CLI, PowerShell) provide parity in Linux and Windows 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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page presents Azure CLI, PowerShell, and REST API as supported experiences, but PowerShell (a Windows-centric tool) is highlighted equally alongside Azure CLI. No explicit Linux shell examples (e.g., Bash) are shown, and PowerShell is mentioned before Linux-native tools. The page does state Run command supports both Windows and Linux, but the examples and tooling focus on Windows/PowerShell, creating mild friction for Linux/macOS users.
Recommendations
  • Add explicit Bash or Linux shell examples alongside PowerShell examples.
  • Clarify that Azure CLI is cross-platform and provide Linux-specific usage notes where relevant.
  • Ensure Linux and Windows are mentioned equally in examples and tool recommendations.
  • Consider linking to Linux-specific documentation or best practices for script execution.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation covers troubleshooting for both Windows and Linux Azure Connected Machine agent installations. However, there are minor signs of Windows bias: Windows log file paths and PowerShell/Windows command examples are presented before Linux equivalents, and Windows-specific tools (e.g., PowerShell version requirements, Windows environment variables) are referenced. Linux examples and paths are present, but Windows is often shown first or in more detail.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which OS is shown first to avoid implicit prioritization.
  • Ensure Linux-specific troubleshooting steps and log file locations are as clearly described as Windows equivalents.
  • Where Windows-specific tools (e.g., PowerShell) are mentioned, also reference Linux alternatives (e.g., Bash, shell commands) if applicable.
  • Explicitly state parity between Windows and Linux where possible, and clarify any OS-specific limitations.
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-14 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, but the Windows/PowerShell example is presented first and in greater detail (including a screenshot). The Linux example is present and functional, but the ordering and emphasis slightly favor Windows. References to Azure portal, PowerShell, and Azure CLI for related tasks are balanced, but PowerShell is mentioned before Azure CLI.
Recommendations
  • Present Windows and Linux examples in parallel or alternate their order to avoid implicit prioritization.
  • Ensure screenshots and example outputs are provided for both Windows and Linux, not just Windows.
  • Where possible, mention Azure CLI alongside PowerShell for cross-platform parity.
  • Explicitly state that both Windows and Linux are fully supported and provide links to Linux-specific tutorials before or alongside Windows equivalents.
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-14 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, Windows-specific features (such as customizing guest OS settings for Windows VMs and Windows Server Management) are mentioned explicitly, and Windows tools (like Azure PowerShell) are listed alongside cross-platform tools. However, Linux-specific examples are present (e.g., Arc agent installation on Linux via SSH), and cross-platform SDKs and tools are included. There is a minor bias in mentioning Windows features and tools before Linux equivalents in some sections.
Recommendations
  • Ensure parity by explicitly mentioning Linux/macOS support where relevant (e.g., guest OS customization for Linux VMs).
  • When listing tools (Azure CLI, PowerShell), clarify platform compatibility and provide Linux/macOS usage examples if available.
  • Avoid listing Windows-specific tools or features before Linux equivalents unless there is a technical reason.
  • Add links or references to Linux/macOS documentation where appropriate.
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-14 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 all major steps, ensuring Linux and Windows users are supported. However, in most sections, PowerShell examples are presented after Bash, and some PowerShell-specific nuances (like base64 encoding) are explained. There is a slight Windows-first bias in the order of examples and some minor PowerShell-specific notes, but Linux parity is generally maintained.
Recommendations
  • Ensure that Bash and PowerShell tabs are presented with equal prominence, possibly randomizing or alternating their order.
  • Where platform-specific nuances exist (e.g., encoding differences), clarify both Linux and Windows approaches in the main text, not just in code comments.
  • Consider adding a brief note at the top clarifying that all steps are supported on both Linux and Windows, and that Bash examples are for Linux/macOS while PowerShell is for Windows.
  • Review PowerShell examples for unnecessary Windows-specific tools (e.g., 'armclient') and suggest cross-platform alternatives if possible.
GitHub Create Pull Request
← Previous Page 84 of 94 Next →