Azure Arc

926
Total Pages
755
Linux-Friendly Pages
171
Pages with Bias
18.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

432 issues found
Showing 301-325 of 432 flagged pages
Azure Arc Use Azure Private Link to Connect Servers to Azure Arc by Using a Private Endpoint ...in/articles/azure-arc/servers/private-link-security.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates mild Windows bias, primarily by presenting Windows-specific instructions and examples before Linux equivalents, especially in the Hosts file configuration section. Windows tools and terminology (e.g., Windows Admin Center, C:\Windows\System32\drivers\etc\hosts) are mentioned first or exclusively in some places, and screenshots are Windows-centric. However, Linux instructions are present and reasonably clear, and most steps are platform-agnostic.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which OS is shown first in instructions.
  • Include screenshots or CLI examples for Linux environments where relevant (e.g., Azure portal on Linux, Linux agent installation commands).
  • Explicitly mention macOS where applicable, especially in Hosts file configuration.
  • Avoid Windows-centric terminology in generic steps (e.g., refer to 'Hosts file' generically before specifying OS paths).
  • Add parity in troubleshooting steps, e.g., show Linux command-line DNS checks (dig, host) alongside nslookup.
GitHub Create Pull Request
Azure Arc Azure Arc agent ...n/articles/azure-arc/vmware-vsphere/azure-arc-agent.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation presents Windows agent installation details before Linux, with more granular information about Windows-specific artifacts (services, security groups, environment variables, and Group Policy adjustments). Windows tools and concepts (MSI installer, NT SERVICE accounts, Group Policy) are described in detail, while Linux equivalents are covered but with less depth and fewer troubleshooting specifics. However, both platforms are supported and installation instructions are provided for each.
Recommendations
  • Present Linux and Windows installation details in parallel sections, or alternate which platform is described first.
  • Provide equally detailed troubleshooting and artifact removal information for Linux, including service management, user/group permissions, and post-uninstall cleanup.
  • Include Linux-specific considerations (e.g., SELinux/AppArmor, systemd service management, package manager commands) to match the Windows Group Policy and MSI details.
  • Ensure that examples and paths for both platforms are given equal prominence and detail.
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash (Linux/macOS) and PowerShell (Windows) examples for all major command-line steps, ensuring parity in instructions. However, PowerShell examples are consistently presented immediately after Bash, and in some cases, Windows-specific encoding and command nuances are explained in more detail (e.g., handling carriage returns, base64 encoding). There are no sections that are Windows-only, and Linux users can follow all steps. Minor Windows bias is present in the ordering and some command explanations.
Recommendations
  • Explicitly state that Bash examples are suitable for Linux and macOS, and PowerShell for Windows, at the top of each tabbed section.
  • Randomize or alternate the order of Bash and PowerShell tabs to avoid implicit prioritization.
  • Add clarifying notes where command differences exist (e.g., file encoding, base64) to help users on both platforms.
  • Ensure troubleshooting and portal instructions mention cross-platform compatibility where relevant.
GitHub Create Pull Request
Azure Arc Turn on transparent data encryption in SQL Managed Instance enabled by Azure Arc (preview) ...igure-transparent-data-encryption-sql-managed-instance.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Examples Windows Path Notes
Summary
The documentation provides both Windows and Linux examples for file operations (copying certificates/keys to and from containers), but Windows examples are consistently presented first. There are explicit notes about Windows path issues, and Windows-specific commands (using 'type' and backslash paths) are shown before Linux equivalents. However, all critical operations are covered for Linux users, and Linux-native tools (kubectl, openssl) are used throughout.
Recommendations
  • Alternate the order of Windows and Linux examples, or present Linux examples first to match the likely environment for Kubernetes workloads.
  • Add a short note at the top clarifying that all commands work on Linux/macOS unless otherwise noted.
  • Where possible, use platform-neutral commands or highlight cross-platform compatibility.
  • Consider grouping platform-specific instructions together, or using tabs that default to Linux.
  • Review notes about Windows path issues to ensure Linux/macOS users are equally informed about any platform-specific caveats.
GitHub Create Pull Request
Azure Arc Prerequisites | Direct connect mode ...rc/data/create-data-controller-direct-prerequisites.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
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 connecting a Kubernetes cluster to Azure Arc, but the PowerShell example is given equal prominence to the CLI example, and there are no Linux/macOS-specific instructions or notes. The use of PowerShell may imply a Windows-centric approach, and the documentation does not clarify cross-platform compatibility for the CLI or PowerShell commands. However, Helm and kubectl are mentioned, which are cross-platform tools.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily for Windows.
  • Present Azure CLI (cross-platform) examples before PowerShell (Windows-centric) examples.
  • Add notes or sections for Linux/macOS users, including installation instructions for Azure CLI on those platforms.
  • Remove or de-emphasize PowerShell examples unless there is a Windows-specific need.
  • Include troubleshooting tips for common Linux/macOS issues (e.g., permissions, environment variables).
GitHub Create Pull Request
Azure Arc Encrypt a database with transparent data encryption manually in SQL Managed Instance enabled by Azure Arc ...data/configure-transparent-data-encryption-manually.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Windows and Linux examples for file operations, but consistently lists Windows examples first and uses Windows-specific tools and patterns (e.g., 'type' command, Windows path syntax like $HOME\sqlcerts). There is a note about Windows-specific issues with kubectl cp, but no equivalent troubleshooting for Linux/macOS. The use of Windows shell commands and paths may create friction for Linux/macOS users, though Linux examples are present for all major steps.
Recommendations
  • Alternate the order of Windows and Linux examples, or present Linux/macOS examples first to balance visibility.
  • Add troubleshooting notes for Linux/macOS users where relevant, not just for Windows.
  • Provide a summary table of commands for both platforms to help users quickly find their platform-specific instructions.
  • Clarify when commands are cross-platform and when they are not, and avoid Windows-centric terminology (e.g., use $HOME/sqlcerts for both platforms where possible).
  • Consider including macOS explicitly in the examples or notes.
GitHub Create Pull Request
Azure Arc Connect to AD-integrated SQL Managed Instance enabled by Azure Arc .../data/connect-active-directory-sql-managed-instance.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation shows a mild Windows bias: Windows-based tools (SSMS, ADS) are mentioned and illustrated, and the Windows connection section appears before Linux/Mac OS. However, Linux/Mac connection steps are present and reasonably detailed, including Kerberos setup. There are no PowerShell-specific commands, but the overall tone and tool selection favor Windows environments.
Recommendations
  • Add explicit screenshots or instructions for connecting from Azure Data Studio on Linux/macOS.
  • Include a section or examples for connecting from Linux/macOS GUI tools (e.g., Azure Data Studio) in addition to command-line.
  • List Linux/Mac connection instructions before or alongside Windows instructions to avoid 'windows_first' bias.
  • Clarify that both Windows and Linux/macOS are equally supported, and provide parity in examples and illustrations.
GitHub Create Pull Request
Azure Arc Deploy a new SQL Managed Instance enabled by Azure Arc using Kubernetes tools ...ate-sql-managed-instance-using-kubernetes-native-tools.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both PowerShell (Windows) and Linux/macOS CLI examples for base64 encoding credentials, but the PowerShell example is presented first. In the kubectl create example, the file path uses Windows-style backslashes and a C: drive, which may confuse Linux/macOS users. No Linux-specific tools or patterns are mentioned first, and the overall structure subtly prioritizes Windows conventions.
Recommendations
  • Present Linux/macOS and Windows examples side-by-side, or alternate which platform is shown first.
  • Use platform-neutral file paths in examples (e.g., <path-to-yaml-file>), or provide both Windows and Linux/macOS path examples.
  • Explicitly mention that kubectl and all steps work equally on Linux/macOS and Windows.
  • Add more Linux/macOS-specific notes or troubleshooting tips if relevant.
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows installation links are listed first for some tools (e.g., kubectl, curl), and there are specific notes about using cmd.exe instead of PowerShell on Windows, as well as a PowerShell-specific note for curl. Linux installation instructions are less detailed, sometimes just mentioning 'install curl package' without a direct link. No Linux-specific troubleshooting or usage notes are provided, and macOS is only mentioned in passing.
Recommendations
  • Present installation links for all platforms in parallel, or rotate the order so Linux is not always last.
  • Provide direct installation instructions or links for Linux (e.g., apt, yum, zypper) for curl and other tools, not just a generic 'install curl package'.
  • Add Linux/macOS-specific notes where Windows-specific notes are given (e.g., for curl usage differences).
  • Include troubleshooting tips or usage caveats for Linux/macOS, not just Windows/PowerShell.
  • Ensure parity in detail and clarity for all platforms.
GitHub Create Pull Request
Azure Arc Disaster recovery - SQL Managed Instance enabled by Azure Arc - portal ...-arc/data/managed-instance-disaster-recovery-portal.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes disaster recovery configuration using the Azure portal UI, which is platform-agnostic but visually and procedurally most familiar to Windows users. There are no command-line examples (PowerShell, Bash, CLI) in this page, and no mention of Linux/macOS-specific workflows or tools. The only alternative offered is a link to a separate CLI documentation page, but this is not integrated or referenced in the main workflow.
Recommendations
  • Integrate CLI examples (Azure CLI, Bash) directly into this page, alongside portal instructions, to provide parity for Linux/macOS users.
  • Explicitly mention that the Azure portal is accessible from any OS/browser to clarify platform neutrality.
  • Reference PowerShell and Bash/CLI alternatives equally in the main workflow, not just as related content.
  • Provide screenshots or notes indicating cross-platform compatibility for portal steps.
GitHub Create Pull Request
Azure Arc Data collection and reporting | Azure Arc-enabled data services ...zure-arc/data/privacy-data-collection-and-reporting.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. While it is mostly platform-neutral and focuses on Azure Arc concepts, there are subtle signs of Windows preference: Windows is mentioned as the 'osType' in billing data JSON examples, and the example manufacturer/model is 'Microsoft/Hyper-V'. There are no explicit Linux/macOS examples or references, and no mention of Linux-specific tools or patterns. The documentation does not provide parity by showing Linux or cross-platform scenarios, especially in the example data payloads.
Recommendations
  • Include Linux/macOS examples in JSON payloads, e.g., set 'osType' to 'Linux' and use common Linux VM models.
  • Add notes clarifying that Azure Arc-enabled data services support both Windows and Linux environments.
  • Provide example inventory and billing data for Linux-based SQL Server instances.
  • Mention Linux-native tools (e.g., Bash, kubectl) alongside Azure CLI and Azure Data Studio.
  • Ensure that references to operating systems, manufacturers, and models in examples are balanced between Windows and Linux.
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows Example Present Linux First
Summary
The documentation provides both Linux and Windows instructions for base64 encoding, but the Linux method (using 'base64') is presented first and described as universal, while the Windows method (using 'certutil' and 'findstr') is given as an alternative. There is no evidence of Windows/Powershell bias in the main workflow, as all other examples use cross-platform tools (OpenSSL, Azure CLI, kubectl) and Linux commands are shown first. The only Windows-specific mention is for base64 encoding, and it is not prioritized.
Recommendations
  • Consider explicitly mentioning macOS compatibility for all CLI commands, especially for base64 and OpenSSL usage.
  • Provide PowerShell examples for certificate manipulation if relevant, or clarify that the workflow is identical on Windows using WSL or native tools.
  • Add notes about differences in file path syntax between Windows and Linux/macOS where relevant.
  • Ensure that all referenced tools (OpenSSL, Azure CLI, kubectl) are available and documented for Windows, Linux, and macOS.
GitHub Create Pull Request
Azure Arc Upload usage data, metrics, and logs to Azure ...e-arc/data/upload-metrics-and-logs-to-azure-monitor.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Windows, macOS/Linux, and PowerShell, but Windows examples are consistently presented first in each tabbed section. PowerShell examples are included as a separate tab, which may reinforce a Windows-centric workflow. There is no evidence of missing Linux examples or exclusive use of Windows tools; all commands use Azure CLI, which is cross-platform.
Recommendations
  • Alternate the order of example tabs so Linux/macOS is sometimes shown first.
  • Add a brief note at the top clarifying that all CLI commands work equally on Linux, macOS, and Windows.
  • Consider merging PowerShell and Windows tabs if the commands are identical, or clarify when PowerShell is required.
  • Ensure that any referenced external content (e.g., service principal creation) also includes Linux/macOS instructions.
GitHub Create Pull Request
Azure Arc Upload logs to Azure Monitor ...-docs/blob/main/articles/azure-arc/data/upload-logs.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable examples for Windows (CMD), PowerShell, and Linux/macOS, but consistently lists Windows and PowerShell examples before Linux/macOS. This ordering may subtly prioritize Windows users. However, all major steps and commands are cross-platform, and Linux/macOS instructions are present and accurate. There is no evidence of missing Linux examples or exclusive use of Windows-only tools.
Recommendations
  • Alternate the order of examples so that Linux/macOS instructions are sometimes shown first, or present all OS options in a single table for parity.
  • Explicitly state that all commands are cross-platform where applicable.
  • Add more Linux/macOS-specific automation examples (e.g., cron usage) alongside Windows Task Scheduler.
  • Ensure that any referenced scripts or automation tools are demonstrated for both platforms equally.
GitHub Create Pull Request
Azure Arc Upload usage data to Azure ...blob/main/articles/azure-arc/data/upload-usage-data.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Linux Example Present Windows First
Summary
The documentation provides Linux shell scripting examples for automating uploads and mentions Linux/Mac script file extensions first. However, it also references Windows automation tools (Task Scheduler) and script extensions (.cmd, .bat, .ps1), and lists them alongside Linux options. The mention of Windows tools and extensions is present, but Linux examples and patterns are given first and in more detail.
Recommendations
  • Provide explicit PowerShell or Windows batch script examples, if mentioning Windows automation tools, to ensure parity and clarity for Windows users.
  • Clarify which steps or commands are cross-platform and which require OS-specific adjustments.
  • Consider splitting automation instructions into separate sections for Linux/Mac and Windows, each with tailored examples.
  • List Linux/Mac and Windows options in parallel, rather than grouping them together, to avoid implicit prioritization.
GitHub Create Pull Request
Azure Arc Upload metrics to Azure Monitor ...cs/blob/main/articles/azure-arc/data/upload-metrics.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides examples for PowerShell, macOS/Linux, and Windows, but PowerShell (which is Windows-centric) is consistently presented first. Windows-specific tools and patterns (PowerShell, Windows Task Scheduler) are mentioned before their Linux equivalents (cron, shell scripts). Some commands are shown only for PowerShell and macOS/Linux, with 'N/A' for Windows, which may confuse users. Automation examples focus on Linux shell scripting, with only brief mentions of Windows automation tools.
Recommendations
  • Alternate the order of examples so Linux/macOS commands are shown first in some sections.
  • Provide equivalent Windows batch (.bat/.cmd) script examples for automation, not just PowerShell.
  • Clarify when PowerShell examples are cross-platform (since PowerShell Core runs on Linux/macOS) or provide explicit Windows batch alternatives.
  • Expand automation guidance to include concrete Windows Task Scheduler and batch script examples.
  • Ensure all critical steps have both Windows and Linux/macOS command examples, or clearly state platform limitations.
GitHub Create Pull Request
Azure Arc Azure Arc-enabled data services validation ...lob/main/articles/azure-arc/data/validation-program.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias by referencing Windows-centric partner solutions (e.g., Azure Stack HCI, AKS-HCI) and listing Windows-based tools (Azure Data Studio, azdata CLI) without mentioning Linux/macOS alternatives or installation instructions. Windows-oriented solutions are often listed first in partner tables, and the prerequisites do not clarify cross-platform support for the listed tools.
Recommendations
  • Explicitly mention that Azure Data Studio and azdata CLI are available on Linux/macOS, and provide installation links or instructions for those platforms.
  • Add examples or notes for using the validation process on Linux/macOS, including any platform-specific steps for generating Kubernetes config files.
  • Ensure partner solution tables highlight both Windows and Linux-based Kubernetes distributions equally, and avoid listing Windows-centric solutions first.
  • Reference Linux-native tools or environments where appropriate, such as using bash or Linux package managers for CLI installation.
GitHub Create Pull Request
Azure Arc Configure Authentication for Edge RAG Preview Enabled by Azure Arc .../articles/azure-arc/edge-rag/prepare-authentication.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. It references Windows Notepad as the example tool for saving IDs, and all screenshots and instructions are based on the Azure Portal GUI, which is most commonly accessed from Windows environments. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), nor are Linux/macOS equivalents or tools mentioned. The only tool explicitly named is Windows Notepad, with no mention of alternatives for Linux or macOS users.
Recommendations
  • Replace 'Windows Notepad' with a generic phrase like 'a text editor', or mention alternatives such as 'Notepad (Windows), TextEdit (macOS), or gedit (Linux)'.
  • Add Azure CLI or Bash command examples for steps such as registering applications, creating app roles, and assigning users/groups, to support automation and parity for Linux/macOS users.
  • Include notes or screenshots showing the process on non-Windows platforms where relevant.
  • Explicitly state that the Azure Portal is accessible from any modern browser on any OS.
GitHub Create Pull Request
Azure Arc Requirements for Edge RAG Preview, Enabled by Azure Arc .../blob/main/articles/azure-arc/edge-rag/requirements.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Minor Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows Server is mentioned first in the NFS setup guides, and a Windows machine is suggested as a management host for Azure Arc-enabled Kubernetes clusters. References to Windows-specific VM sizes and a link to AKS on Windows Server are present. However, Linux is listed as the required VM operating system, and Linux NFS setup is also linked, providing some parity.
Recommendations
  • List Linux setup guides before or alongside Windows Server guides for NFS.
  • Clarify that the management host can be Linux, and provide explicit instructions or links for Linux management host setup.
  • Balance references to Windows and Linux VM sizes and tools, ensuring Linux options are equally visible.
  • Remove or supplement Windows-first links (e.g., AKS on Windows Server) with Linux equivalents where relevant.
GitHub Create Pull Request
Azure Arc Customer intent: "As a cloud administrator, I want to understand how to get the region segment of regional endpoints , so that I can configure Azure services in specific regions without errors." ...ob/main/articles/azure-arc/includes/arc-region-note.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
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 shown immediately after the CLI example, and PowerShell is a Windows-centric tool. No Linux/macOS-specific shell examples (e.g., Bash, grep, jq) are provided, and there is no mention of platform differences or guidance for non-Windows users.
Recommendations
  • Add explicit Linux/macOS shell examples (e.g., using Bash with Azure CLI and text processing tools).
  • Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Consider listing Azure CLI examples first, as it is platform-agnostic.
  • Mention that PowerShell Core is available on Linux/macOS if PowerShell examples are retained.
GitHub Create Pull Request
Azure Arc Customer intent: As a cloud administrator, I want to list all Azure Arc-enabled Kubernetes resources, so that I can monitor and manage the connected clusters and their configurations effectively. ...les/azure-arc/includes/azure-arc-enabled-kubernetes.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
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 each query, but consistently lists PowerShell examples immediately after CLI, and includes PowerShell-specific tabs and syntax. There are no explicit Linux/macOS shell examples (e.g., Bash), nor any mention of platform-specific considerations for non-Windows users. The use of Azure CLI is cross-platform, but the presence and prominence of PowerShell may suggest a slight Windows bias.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows, and clarify any platform-specific prerequisites.
  • Add Bash or shell script examples where relevant, or note that Azure CLI commands can be run in Bash, Zsh, etc.
  • Consider listing Azure CLI examples first, as it is the most cross-platform tool.
  • Add a note about installing Azure CLI and PowerShell on Linux/macOS, if relevant.
  • If PowerShell is not required for Linux/macOS users, clarify that it is optional.
GitHub Create Pull Request
Azure Arc Simplify network configuration requirements with Azure Arc gateway (preview) ...zure-arc/kubernetes/arc-gateway-simplify-networking.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
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 all major tasks, but PowerShell is given equal prominence and is presented as a primary option alongside CLI. There are no Linux-specific shell examples (e.g., Bash scripts), and environment variable examples for proxy configuration use both Windows (PowerShell) and Linux (export) syntax. However, the documentation does not mention Windows-only tools or patterns, and the CLI examples are cross-platform. The order of presentation sometimes places PowerShell before CLI, and vice versa, but neither is clearly prioritized. No critical steps are Windows-only, and Linux/macOS users can complete all tasks using Azure CLI.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users, especially for environment variable configuration and scripting.
  • Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
  • Where environment variables are set, provide both export (Linux/macOS) and setx/set (Windows CMD) examples, or clarify the syntax for each OS.
  • Consider adding a short section on platform compatibility, reassuring users that all steps can be completed on Linux/macOS.
  • If PowerShell is mentioned, clarify that it is available cross-platform, but provide Bash alternatives for Linux/macOS users.
GitHub Create Pull Request
Azure Arc Troubleshoot extension issues for Azure Arc-enabled Kubernetes clusters ...les/azure-arc/kubernetes/extensions-troubleshooting.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias, primarily in the ordering and selection of troubleshooting examples. Azure CLI commands are shown first, and some examples reference Azure-specific features and tools (such as Azure Policy, Azure Monitor, and Azure CLI) that are more commonly used or familiar in Windows-centric environments. However, all command-line examples use cross-platform tools (kubectl, helm, jq, bash), and there are explicit troubleshooting steps for Linux distributions (Oracle Linux, RHEL). No PowerShell-specific examples or Windows-only tools are present, and Linux/macOS users can follow all steps without significant friction.
Recommendations
  • Explicitly state that all CLI commands are cross-platform and provide any necessary notes for Linux/macOS users (e.g., Azure CLI installation, shell differences).
  • Where Azure CLI is used, mention that it is available on Linux/macOS and provide links to installation guides for those platforms.
  • If any troubleshooting steps require Windows-only tools or features, provide equivalent Linux/macOS instructions or alternatives.
  • Consider adding a short section or note at the top clarifying platform compatibility and any OS-specific caveats.
  • Ensure that examples and troubleshooting steps for Linux-specific issues (such as Oracle Linux/RHEL kernel modules) are as detailed as those for Azure/Windows environments.
GitHub Create Pull Request
Azure Arc Azure Resource Graph sample queries for Azure Arc-enabled Kubernetes ...rticles/azure-arc/kubernetes/resource-graph-samples.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions Azure PowerShell before Azure CLI when describing how to run queries, and references PowerShell in metadata. There is a slight preference for Windows-centric tools and patterns, though Azure CLI (cross-platform) is also mentioned. No Linux/macOS-specific instructions, examples, or tools are provided.
Recommendations
  • List Azure CLI before Azure PowerShell to emphasize cross-platform usage.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide example commands for those platforms.
  • Add a note or section for Linux/macOS users, confirming parity and highlighting any platform-specific considerations.
  • Ensure metadata and tracking tags do not prioritize Windows tools unless necessary.
GitHub Create Pull Request
Azure Arc Azure Arc resource bridge security overview ...rticles/azure-arc/resource-bridge/security-overview.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell as a method to retrieve Azure activity logs, and lists it before Azure CLI, which is cross-platform. There are no explicit Linux/macOS examples or mentions of platform-specific tools, but the ordering and mention of PowerShell may suggest a Windows-first bias.
Recommendations
  • Explicitly mention that Azure CLI is available on Linux/macOS and provide example commands for both platforms.
  • Avoid listing PowerShell before Azure CLI unless there is a technical reason; consider alternating or grouping examples by platform.
  • Add notes or links for Linux/macOS users regarding installation and usage of Azure CLI.
  • Where PowerShell is referenced, clarify if the same functionality is available via Bash or other shells.
GitHub Create Pull Request
← Previous Page 13 of 18 Next →