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 1476-1500 of 2334 flagged pages
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/view-billing-data-in-azure.md .../articles/azure-arc/data/view-billing-data-in-azure.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates bias towards Windows environments by exclusively referencing Windows-centric tools (such as Excel for viewing CSV files) and omitting any examples or guidance for Linux users. There are no instructions for using Linux-native tools to view or process billing data, nor are there any command-line examples for Linux or cross-platform usage.
Recommendations
  • Include examples of how to view and process downloaded CSV files using Linux tools such as LibreOffice Calc, csvkit, or command-line utilities like awk, grep, and cut.
  • Provide instructions for automating billing data uploads using Bash scripts or Linux shell commands, in addition to any PowerShell or Windows-based automation.
  • Mention cross-platform editors (e.g., VS Code) and clarify that the download location may vary depending on the operating system.
  • Add explicit notes or sections for Linux users, ensuring parity in guidance and examples.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/azcmagent-connect.md ...b/main/articles/azure-arc/servers/azcmagent-connect.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation displays a mild Windows bias by describing the interactive browser login as 'Windows only' and listing it first among authentication options. It references a PowerShell cmdlet (Get-AzAccessToken) for obtaining an access token, without mentioning a Linux/CLI equivalent. However, most examples and instructions are cross-platform, and Linux is explicitly mentioned in several places.
Recommendations
  • For the interactive browser login, clarify whether this method is available on Linux with a desktop environment (e.g., GNOME/KDE) and provide instructions or caveats for Linux users.
  • When referencing tools for obtaining access tokens, provide both PowerShell (Get-AzAccessToken) and Azure CLI (az account get-access-token) examples, or mention that both are supported.
  • Consider reordering authentication options so that cross-platform or Linux-default methods (like device code login) are listed first, or group them by platform applicability.
  • Explicitly state in each authentication option which platforms are supported, and provide Linux-specific notes or examples where behavior differs.
  • Ensure that all sample commands and flags are shown in a cross-platform way, and avoid implying that Windows is the primary or default environment.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/includes/esu-network-requirements.md ...azure-arc/servers/includes/esu-network-requirements.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on Windows Server 2012 and SQL Server 2012, with all examples and endpoint descriptions tailored to Windows environments. There are no references to Linux servers, Linux-specific endpoints, or instructions for Linux-based Azure Arc-enabled servers. This creates a Windows-first bias and omits guidance for Linux users.
Recommendations
  • Include information about required endpoints for Linux-based Azure Arc-enabled servers, if applicable.
  • Add examples or notes for Linux package downloads and update mechanisms (e.g., mention if endpoints are also used for Linux extension packages).
  • Clarify whether the endpoints listed are relevant for Linux servers, and specify any differences.
  • Provide parity in documentation by listing both Windows and Linux scenarios, or explicitly state if Linux is not supported in this context.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/set-up-and-manage-self-service-access-scvmm.md ...manager/set-up-and-manage-self-service-access-scvmm.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation is focused exclusively on SCVMM (System Center Virtual Machine Manager), a Windows-centric virtualization management tool. All examples and instructions assume the use of Windows-based management interfaces (Azure Portal, SCVMM), with no mention of Linux tools, CLI, or cross-platform alternatives. There are no Linux-specific instructions or parity examples for managing access or resources.
Recommendations
  • Include equivalent instructions for managing access using Azure CLI and/or PowerShell Core, which are cross-platform.
  • Clarify whether SCVMM resources can be managed from Linux environments, and if so, provide examples.
  • Mention any limitations or requirements for Linux administrators, such as needing to use the Azure Portal or specific tools.
  • Provide guidance for Linux users on how to interact with Azure Arc-enabled SCVMM resources, if possible.
  • Add references to cross-platform documentation or tools where appropriate.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/create-virtual-machine.md ...les/azure-arc/vmware-vsphere/create-virtual-machine.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily describes VM creation via the Azure portal, with administrator account setup focused on username/password authentication (typical for Windows). Linux-specific options, such as SSH key authentication, are mentioned only as an alternative and not illustrated with examples or screenshots. There are no Linux-specific configuration steps, patterns, or troubleshooting tips, and Windows-centric patterns (username/password) are presented first and in more detail.
Recommendations
  • Provide explicit Linux VM creation examples, including screenshots illustrating SSH key authentication setup.
  • Include guidance on Linux-specific configuration options (e.g., cloud-init, OS customization, package installation).
  • Mention Linux guest customization and management patterns (e.g., using Azure Arc agent on Linux, troubleshooting Linux connectivity).
  • Ensure parity in documentation structure, presenting Linux and Windows options side-by-side where relevant.
  • Add references to Linux CLI tools and automation patterns (e.g., Bash scripts, Linux-based Infrastructure-as-Code).
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/azure-firewall-explicit-proxy.md ...in/articles/azure-arc/azure-firewall-explicit-proxy.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides instructions and examples for configuring Azure Arc resources with Azure Firewall Explicit Proxy, but it implicitly favors Windows environments. The onboarding and proxy configuration steps reference the Azure Connected Machine agent CLI without specifying OS-specific commands or clarifying Linux support. The Private Link integration section links to proxy bypass instructions specifically for Windows, with no mention of Linux equivalents. There are no explicit PowerShell examples, but the lack of Linux-specific guidance and the use of Windows-centric links and terminology indicate a Windows-first bias and missing Linux parity.
Recommendations
  • Add explicit instructions and examples for Linux environments, including onboarding, proxy configuration, and troubleshooting steps using Linux shell commands.
  • Clarify whether the Azure Connected Machine agent CLI commands are OS-agnostic, and provide Linux-specific syntax or notes if necessary.
  • Include links and documentation for proxy bypass features for Linux, not just Windows.
  • Ensure that all referenced features and troubleshooting steps are demonstrated for both Windows and Linux platforms, with clear parity in guidance.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/container-storage/howto-configure-onelake-identity.md .../container-storage/howto-configure-onelake-identity.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Power BI web links and portals, which are typically accessed via web browsers on Windows systems. There are no Linux-specific examples, CLI commands, or alternative instructions for Linux users. The configuration steps rely on graphical interfaces and do not mention command-line or automation options that are common in Linux environments.
Recommendations
  • Provide equivalent instructions using Azure CLI or REST API, which are platform-agnostic and can be used on Linux.
  • Include examples of configuring OneLake Identity and subvolumes using command-line tools available on Linux.
  • Mention any Linux-specific considerations or prerequisites for Azure Arc and Container Storage.
  • Add screenshots or walkthroughs for Linux environments where applicable.
  • Clarify that the portal-based steps are accessible from any OS and offer alternatives for users who prefer not to use a GUI.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-sql-managed-instance-using-kubernetes-native-tools.md ...ate-sql-managed-instance-using-kubernetes-native-tools.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by presenting PowerShell as the first example for base64 encoding credentials, followed by Linux/macOS. Additionally, file path examples use Windows-style paths (e.g., C:\arc-data-services\sqlmi.yaml) without showing Linux equivalents. The text editor recommendation (VS Code) is cross-platform, and most Kubernetes commands are platform-neutral, but the ordering and examples subtly favor Windows users.
Recommendations
  • Present Linux/macOS and Windows examples side-by-side or alternate which comes first.
  • Include Linux file path examples (e.g., /home/user/arc-data-services/sqlmi.yaml) alongside Windows paths.
  • Explicitly state that all commands work on Linux/macOS and Windows, and highlight any platform-specific differences.
  • Consider adding a table or section summarizing commands for each major platform.
  • Where PowerShell is used, also mention Bash or other common Linux shells for parity.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/delete-azure-resources.md ...main/articles/azure-arc/data/delete-azure-resources.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (a web UI often associated with Windows workflows) for resource deletion steps and by not providing any Linux-specific examples or commands for managing Kubernetes resources directly. All CLI examples use the Azure CLI, which is cross-platform, but there are no examples of using Linux-native tools (e.g., kubectl) for resource deletion, nor is there any mention of Linux shell commands or patterns. The documentation does not reference PowerShell, but the absence of Linux-specific guidance or parity in examples indicates a bias toward Windows-centric management patterns.
Recommendations
  • Add examples for deleting resources using kubectl commands, especially for Kubernetes clusters running on Linux.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample shell commands for Linux users.
  • Include guidance for managing resources via Linux terminal, such as using bash scripts or native Linux tools.
  • Balance instructions by providing both portal (GUI) and command-line (CLI) options for all major operations, and clarify platform compatibility.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/migrate-to-managed-instance.md ...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently presents Windows-centric examples and file paths (e.g., C:\Backupfiles\test.bak) when demonstrating backup and restore operations. There are no equivalent Linux examples or file paths (e.g., /home/user/test.bak) provided, and Windows patterns/tools are mentioned first or exclusively. This may make it less accessible for users working on Linux environments.
Recommendations
  • Provide Linux-specific examples alongside Windows ones, such as using /home/user/test.bak for backup file paths.
  • Explicitly mention that the backup and restore steps can be performed on both Windows and Linux, and clarify any platform-specific differences.
  • Include screenshots or instructions for Azure Data Studio and Azure Storage Explorer usage on Linux, if available.
  • Add notes or sections that address common Linux tools or commands for file manipulation and backup management.
  • Ensure that references to file paths, commands, and tooling are not exclusively Windows-centric and offer parity for Linux users.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/rotate-user-tls-certificate.md ...articles/azure-arc/data/rotate-user-tls-certificate.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation provides both Linux and Windows instructions for base64 encoding, but Windows-specific tools (certutil, findstr) are mentioned separately and in detail, while the Linux example is presented first and more simply. The Windows tool usage is explained with extra steps (removing headers), which may indicate a slight Windows bias in tool coverage and troubleshooting. However, the main certificate generation and Kubernetes steps use cross-platform tools (OpenSSL, Azure CLI, kubectl), and Linux is referenced first in the base64 section.
Recommendations
  • Provide equivalent Linux troubleshooting steps for base64 encoding (e.g., how to remove headers if needed), to match the detail given for Windows.
  • Mention cross-platform alternatives for base64 encoding/decoding (e.g., Python, OpenSSL) for both OSes.
  • Clarify that all CLI and YAML steps are OS-agnostic unless otherwise noted.
  • Consider grouping OS-specific instructions together, or using tabs to separate Windows and Linux workflows for encoding/decoding.
  • Ensure that any Windows-specific tool (certutil, findstr) is matched with a Linux equivalent (e.g., grep, sed) and provide example commands.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/troubleshooting-get-logs.md ...in/articles/azure-arc/data/troubleshooting-get-logs.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a CLI example that uses a Windows-style file path (C:\temp\logs) as the only explicit example for the --target-folder parameter. There are no Linux or cross-platform path examples, and no mention of Linux-specific considerations. This may lead Linux users to feel the documentation is Windows-centric and less relevant to their environment.
Recommendations
  • Include Linux-style file path examples (e.g., /tmp/logs) alongside Windows examples when demonstrating CLI parameters that accept file paths.
  • Explicitly state that the az CLI and arcdata extension work on both Windows and Linux, and provide guidance for both platforms where relevant.
  • Add a note or section on cross-platform usage, including any differences in file system paths, permissions, or environment setup.
  • Ensure that all examples and instructions are platform-neutral or provide parallel examples for both Windows and Linux.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/validation-program.md ...lob/main/articles/azure-arc/data/validation-program.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias by prominently featuring Windows-centric partner solutions (such as DataON AZS-6224 for Azure Stack HCI, Hitachi UCP with Microsoft AKS-HCI, Lenovo ThinkAgile MX1020/MX3520) and referencing tools and patterns commonly associated with Windows environments (e.g., Azure Data Studio, Azure Data CLI). Windows-based Kubernetes distributions (AKS-HCI, Azure Stack HCI) are mentioned before Linux-based equivalents (Red Hat OpenShift, VMware Tanzu, etc.), and some partner solutions are described with a clear Windows orientation. However, the page does include Linux-oriented solutions and tools (kubectl, OpenShift, Kublr, Wind River, etc.), and does not provide command-line examples that are exclusive to Windows or PowerShell.
Recommendations
  • Ensure equal prominence and ordering of Linux-based solutions alongside Windows-based ones in partner tables and descriptions.
  • Include explicit Linux command-line examples (e.g., bash, kubectl usage on Linux) where platform-specific instructions are relevant.
  • Reference Linux-native tools (such as Linux package managers for azdata installation) in the prerequisites section.
  • Clarify platform compatibility for all tools (e.g., Azure Data Studio, azdata) and provide installation instructions for both Windows and Linux.
  • Avoid listing Windows-centric solutions (e.g., AKS-HCI, Azure Stack HCI) before Linux equivalents unless there is a technical reason.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/upload-usage-data.md ...blob/main/articles/azure-arc/data/upload-usage-data.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Linux First
Summary
The documentation provides automation examples using Linux shell scripting and mentions Linux/Mac script extensions before Windows equivalents. It references both Linux (cron) and Windows (Task Scheduler) job schedulers, but Linux tools and patterns are presented first and in more detail. There are no PowerShell or Windows-specific command examples, nor is there exclusive use of Windows tools.
Recommendations
  • Add explicit PowerShell or Windows batch script examples for automating uploads, similar to the Linux shell script provided.
  • Provide step-by-step instructions for setting up scheduled uploads using Windows Task Scheduler, including sample .bat or .ps1 scripts.
  • Ensure that references to both Linux and Windows automation tools are balanced and that examples for both platforms are equally detailed.
  • Mention cross-platform scripting options, such as Python, for users who may want a unified approach.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/observability.md ...blob/main/articles/azure-arc/edge-rag/observability.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (a graphical interface most commonly used on Windows) and Azure Managed Grafana for metric visualization, without providing any Linux-specific or cross-platform command-line examples. There are no instructions for accessing metrics via Linux-native tools (such as kubectl, curl, or Prometheus CLI), nor are there any PowerShell or Windows tool references, but the workflow is centered on Azure portal navigation and GUI screenshots, which are typically more accessible to Windows users. Linux CLI options (e.g., Azure CLI, kubectl) are mentioned only in links, not in the main workflow or examples.
Recommendations
  • Add explicit Linux command-line examples for viewing Edge RAG metrics, such as using Azure CLI, kubectl, or Prometheus queries.
  • Provide step-by-step instructions for monitoring metrics using Linux-native tools and terminal workflows.
  • Include screenshots or terminal output examples from Linux environments.
  • Ensure parity by presenting both GUI (portal) and CLI methods side-by-side, or in separate tabs, for each workflow.
  • Reference cross-platform tools and clarify that Azure CLI and Grafana are available on Linux, macOS, and Windows.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/quickstart-edge-rag.md ...ain/articles/azure-arc/edge-rag/quickstart-edge-rag.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by providing host file editing instructions exclusively for Windows (using Notepad and the C:\windows\System32\drivers\etc\hosts path), without mentioning Linux or macOS equivalents. Additionally, the instructions for opening Azure Cloud Shell mention switching to PowerShell, which is more relevant for Windows users, and variable assignment syntax (e.g., $var = ...) is PowerShell-style, which may not be familiar to Linux/bash users.
Recommendations
  • Include instructions for editing the hosts file on Linux (e.g., using sudo nano /etc/hosts) and macOS.
  • Provide both PowerShell and bash syntax for variable assignment and command examples, or clarify which shell is being used.
  • When referencing Azure Cloud Shell, mention both Bash and PowerShell options, and provide guidance for users on Linux/macOS.
  • Ensure that all steps involving local file paths or tools have cross-platform equivalents or notes.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/includes/arc-region-note.md ...ob/main/articles/azure-arc/includes/arc-region-note.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for listing regions, but the PowerShell example is given immediately after the CLI example, and no explicit Linux shell (bash/zsh) or cross-platform command-line examples are provided. The presence of Azure PowerShell, which is most commonly used on Windows, may signal a slight Windows bias, especially since there is no mention of Linux-specific tools or shell usage.
Recommendations
  • Add explicit bash/zsh examples for Linux users, such as using jq or grep with az CLI output.
  • Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Consider listing the Azure CLI example first, as it is more universally available.
  • Mention that PowerShell Core is available on Linux, if retaining the PowerShell example.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/private-link.md ...lob/main/articles/azure-arc/kubernetes/private-link.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing the Azure portal (GUI) and Azure CLI for configuration steps, without providing any Linux-specific or cross-platform command-line examples (e.g., Bash, PowerShell, or Linux-native tools). There are no references to Linux-specific patterns, tools, or considerations, and all example commands are generic Azure CLI, which is available on both platforms but lacks explicit Linux context. The troubleshooting section uses 'nslookup' (available on both platforms), but does not mention Linux-specific DNS tools or troubleshooting steps. No PowerShell-specific examples are present, but the overall flow assumes familiarity with Azure portal and Azure CLI, which are more commonly used in Windows environments.
Recommendations
  • Include explicit Linux/Bash shell examples for Azure CLI commands, showing usage in a Linux terminal.
  • Add instructions for configuring DNS forwarding and firewall rules using Linux-native tools (e.g., iptables, firewalld, systemd-resolved).
  • Provide guidance for users managing Kubernetes clusters on Linux, such as using kubeadm, kubectl, or Linux-based DNS servers (e.g., BIND, dnsmasq).
  • Mention cross-platform compatibility of Azure CLI and clarify any OS-specific prerequisites or differences.
  • Add troubleshooting steps using Linux tools (e.g., dig, systemctl status) alongside nslookup.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/multicloud-connector/add-public-cloud.md ...les/azure-arc/multicloud-connector/add-public-cloud.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page presents instructions for connecting AWS and GCP to Azure via the multicloud connector, but all example workflows for uploading templates and configuring access are described using graphical portals (Azure portal, AWS CloudFormation console, GCP Console/Cloud Shell). There are no explicit examples or command-line instructions for Linux users (e.g., using AWS CLI, gcloud CLI, or Terraform from a Linux shell). The only mention of running Terraform locally refers to Azure Cloud Shell, which is typically a Bash environment, but this is not highlighted or explained for Linux parity. There is no mention of Powershell, but the overall approach assumes users are comfortable with web portals and does not provide parity for Linux command-line workflows.
Recommendations
  • Add explicit Linux CLI instructions for uploading CloudFormation templates to AWS (using aws CLI) and running Terraform for GCP (using gcloud CLI and terraform CLI).
  • Provide example commands for each major step (e.g., creating stacks, uploading templates, assigning IAM roles) using CLI tools on Linux.
  • Clarify that Azure Cloud Shell is Bash-based and suitable for Linux users, and provide equivalent instructions for running commands locally on Linux.
  • Include troubleshooting tips for common Linux environments (e.g., Ubuntu, CentOS) when running Terraform or gcloud CLI.
  • Ensure parity by listing both portal and CLI workflows side-by-side, so users can choose their preferred method regardless of OS.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/resource-bridge/system-requirements.md ...icles/azure-arc/resource-bridge/system-requirements.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page for Azure Arc resource bridge system requirements shows evidence of Windows bias. The management machine requirements and Azure CLI installation instructions link specifically to the Windows version first, with no mention of Linux or macOS equivalents. There are no examples or instructions for installing or running Azure CLI or the arcappliance extension on Linux or macOS, nor are there references to Linux-specific patterns or tools. All CLI examples and references assume a Windows environment.
Recommendations
  • Add explicit instructions and links for installing Azure CLI and the arcappliance extension on Linux and macOS management machines.
  • Include examples of CLI commands being run on Linux/macOS, including any differences in file paths, permissions, or environment setup.
  • Ensure that references to management machine requirements mention Linux and macOS as supported platforms, and clarify any platform-specific requirements or limitations.
  • Where CLI commands are shown, provide cross-platform notes or tabs (e.g., Windows, Linux, macOS) to demonstrate parity and highlight any differences.
  • Review all links and references to ensure they do not default to Windows unless Windows is the only supported platform (which should be explicitly stated if true).
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/api-extended-security-updates.md ...les/azure-arc/servers/api-extended-security-updates.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows Server 2012 and 2012 R2, with all examples and API payloads referencing Windows-specific targets. There are no examples or guidance for Linux systems, nor any mention of Linux equivalents, tools, or patterns. The only OS referenced for license management is Windows Server, and the customer intent is explicitly for Windows. No Linux scenarios or cross-platform considerations are discussed.
Recommendations
  • Add examples for managing ESU licenses for Linux servers, if supported by Azure Arc.
  • Include Linux-specific API payloads or CLI commands, such as targeting Linux distributions in the 'target' parameter.
  • Clarify in the introduction whether Linux systems are supported or not, and if not, explicitly state the Windows-only scope.
  • If Linux is not supported, provide links or references to documentation for Linux lifecycle management in Azure Arc.
  • Ensure parity in documentation structure and examples for both Windows and Linux where applicable.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/azcmagent-disconnect.md ...ain/articles/azure-arc/servers/azcmagent-disconnect.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation exhibits mild Windows bias by describing the interactive browser login as 'Windows only' and listing it first among authentication options. Additionally, the only explicit method given for obtaining an access token is via the Windows PowerShell cmdlet `Get-AzAccessToken`, with no mention of Linux alternatives (e.g., Azure CLI). Linux is mentioned as a default for device code login, but examples and tooling references favor Windows.
Recommendations
  • Provide Linux-specific instructions and examples where appropriate, such as how to obtain an access token using Azure CLI (`az account get-access-token`) on Linux.
  • Reorder authentication options to present cross-platform methods (device code, service principal, Azure CLI) before platform-specific ones.
  • Clarify that most authentication methods (except interactive browser login) are available on both Windows and Linux, and explicitly state Linux compatibility.
  • Add explicit Linux command-line examples (e.g., bash) alongside any PowerShell examples.
  • Where a method is Windows-only, suggest the equivalent Linux workflow or tool.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/manage-vm-extensions.md ...ain/articles/azure-arc/servers/manage-vm-extensions.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page presents Windows VM extensions before Linux equivalents, with a much longer and more detailed Windows extension table. Windows-specific tools (e.g., Windows Admin Center, OpenSSH for Windows) are highlighted, and Windows extensions are listed first, suggesting a prioritization of Windows scenarios. Linux extensions are covered, but with less detail and fewer examples. The ordering and emphasis may lead Linux users to perceive the documentation as Windows-centric.
Recommendations
  • Present Windows and Linux extension tables side-by-side or alternate their order in different sections to avoid implicit prioritization.
  • Ensure parity in the level of detail and number of examples for Linux extensions, matching those provided for Windows.
  • Highlight Linux-specific management tools or patterns where relevant, similar to the coverage of Windows Admin Center.
  • Include explicit cross-platform usage scenarios and call out differences or similarities in extension management for both OS types.
  • Add more Linux-focused extension examples and links to Linux-specific documentation, especially for commonly used extensions.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/organize-inventory-servers.md ...ticles/azure-arc/servers/organize-inventory-servers.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page discusses organizing and inventorying servers with Azure Arc, mentioning support for both Windows and Linux platforms. However, examples and tooling references (Azure CLI, Azure PowerShell, ARM templates) are presented in a generic way, with no explicit Linux-specific examples or Linux-native tools mentioned. The documentation implicitly prioritizes Windows-centric management patterns and does not provide parity in examples or guidance for Linux users.
Recommendations
  • Include explicit Linux examples alongside Windows examples, such as using Bash scripts or Linux command-line tools for tagging and querying resources.
  • Reference Linux-native tools (e.g., shell scripts, cron jobs) for automating tagging and reporting, in addition to Azure CLI and PowerShell.
  • Provide sample workflows or code snippets for Linux environments, such as onboarding Linux servers to Azure Arc using Bash.
  • Clarify cross-platform support in each section and ensure that instructions are not implicitly Windows-centric.
  • Add links to Linux-specific documentation or guides for Azure Arc management.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/run-command-security.md ...ain/articles/azure-arc/servers/run-command-security.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Windows examples before Linux ones and references the Windows extension handler first. The metadata and custom tags emphasize Azure PowerShell, suggesting a Windows-centric approach. While both Windows and Linux examples are provided, the ordering and emphasis favor Windows.
Recommendations
  • Present Linux and Windows examples in parallel or alternate the order to avoid implicit prioritization.
  • Include Azure CLI examples for both platforms and avoid referencing PowerShell unless necessary for platform-specific tasks.
  • Ensure metadata and custom tags reflect equal support for Azure CLI and Linux tools.
  • Explicitly mention that all features and instructions apply equally to Linux and Windows, unless there are platform-specific differences.
  • Provide links to Linux-specific documentation and troubleshooting resources alongside Windows ones.
GitHub Create Pull Request
← Previous Page 60 of 94 Next →