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 1901-1925 of 2334 flagged pages
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-22 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 CLI command and variable definition, but PowerShell examples are always shown directly after Bash, and the structure is strictly parallel. There are no Windows-specific tools or patterns mentioned, and all commands are cross-platform (az CLI). However, the presence of PowerShell examples may create a slight perception of Windows bias, especially since Bash is shown first but PowerShell is always present, which is not strictly necessary for Linux/macOS users.
Recommendations
  • Consider clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users quickly identify their relevant section.
  • If possible, provide a brief note at the start of the tutorial indicating that all az CLI commands are cross-platform and can be run in Bash (Linux/macOS) or PowerShell (Windows).
  • Optionally, add a section for macOS users if there are any subtle differences (e.g., file paths, shell syntax).
  • If Bash is the primary shell for most users, consider making Bash the default and PowerShell an optional tab.
  • Ensure that any references to environment setup or prerequisites mention both Bash and PowerShell environments equally.
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-22 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 presented immediately after Bash examples, not before. There are no Windows-specific tools or patterns used; all commands are cross-platform (Azure CLI, kubectl). No critical steps are Windows-only, and Linux parity is maintained. The only minor bias is the inclusion of PowerShell examples alongside Bash, which may slightly favor Windows users by offering familiar syntax, but Bash is always shown first.
Recommendations
  • Maintain Bash as the primary example for cross-platform parity.
  • Consider clarifying in the introduction that Bash and PowerShell examples are provided for both Linux/macOS and Windows users.
  • If possible, add a note that Azure CLI and kubectl commands are fully supported on Linux/macOS.
  • Ensure that Bash examples remain first in each section to reinforce Linux parity.
GitHub Create Pull Request
Azure Arc Solution with a Leaf Target ...oad-orchestration/tutorial-service-group-scenario-1.md
Low Priority View Details →
Scanned: 2026-02-22 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 consistently presented before PowerShell examples, which is a minor 'windows_first' bias in ordering. No Windows-specific tools or patterns are used; all commands rely on the Azure CLI and Helm, which are cross-platform. There are no missing Linux examples or exclusive Windows tools.
Recommendations
  • Maintain the current parity by continuing to provide both Bash and PowerShell examples.
  • Consider alternating the order of Bash and PowerShell tabs, or explicitly state that Bash is for Linux/macOS and PowerShell for Windows to clarify intent.
  • Ensure that any future additions (e.g., troubleshooting, environment setup) include Linux/macOS guidance alongside Windows instructions.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are present throughout, and in some sections (e.g., variable naming, file paths), Windows conventions (backslashes, PowerShell syntax) are used. Bash examples are always shown first, so there is no 'windows_first' ordering. No Windows-only tools or patterns are used; all commands rely on the Azure CLI and Helm, which are cross-platform.
Recommendations
  • Ensure that PowerShell examples use only cross-platform syntax and avoid Windows-specific conventions (e.g., backslashes in file paths) where possible.
  • Clarify that both Bash and PowerShell examples are equivalent and that users can choose either based on their OS.
  • Consider adding a note about Helm and Azure CLI installation on Linux/macOS if not already covered in prerequisites.
  • Review PowerShell snippets for any Windows-specific assumptions (e.g., file path formats) and provide alternatives for Linux/macOS if needed.
GitHub Create Pull Request
Azure Arc Multiple Solutions with a Single Shared Dependency at Different Levels ...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, in nearly all sections, Bash examples are shown first, followed by PowerShell. No Windows-specific tools or patterns are mentioned exclusively, and all commands use cross-platform Azure CLI and Helm tools. There are no missing Linux examples or Windows-only instructions.
Recommendations
  • Continue to provide both Bash and PowerShell examples for all steps.
  • Consider alternating the order of Bash and PowerShell tabs in some sections, or explicitly state that Bash is suitable for Linux/macOS and PowerShell for Windows, to reinforce parity.
  • Ensure that any future additions (e.g., troubleshooting, file manipulation) also include both Bash and PowerShell examples.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation references SQL Server Management Studio (SSMS) as the primary GUI client, which is Windows-only, and mentions it before cross-platform tools like sqlcmd. However, sqlcmd usage is shown with a Linux/Windows-neutral example. There is no explicit Linux GUI client mentioned, and SSMS is presented as the default option. Azure CLI commands are used throughout, which are cross-platform, but the overall tone and examples favor Windows tools and patterns.
Recommendations
  • Mention cross-platform SQL GUI clients (e.g., Azure Data Studio, DBeaver) alongside SSMS.
  • Provide explicit Linux/macOS connection examples, including any differences in authentication or environment setup.
  • Clarify that sqlcmd is available on Linux/macOS and provide installation instructions or links.
  • Avoid listing SSMS first unless the majority of users are expected to be Windows-based; otherwise, present cross-platform options equally.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server Profiler, SQL Server PowerShell) and explicitly mentions PowerShell scripting support as a manageability feature. However, it also references cross-platform tools (Azure CLI, Visual Studio Code extension) and does not provide Windows-only examples or prioritize Windows tools over Linux equivalents in critical sections. No Linux/macOS-specific tools or scripting environments (e.g., Bash, sqlcmd) are mentioned, and PowerShell is highlighted as a scripting option without Linux alternatives.
Recommendations
  • Add examples or mention of Linux/macOS-compatible tools such as sqlcmd, Azure Data Studio, or Bash scripting for manageability.
  • Clarify that PowerShell scripting is available cross-platform, or provide Bash/CLI alternatives for scripting tasks.
  • List cross-platform tools before Windows-only tools, or group them by platform for clarity.
  • Include guidance for Linux/macOS users where applicable, especially in the 'Tools' and 'Manageability' sections.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation includes references to Windows-specific services (e.g., time.windows.com, sts.windows.net, login.windows.net, servicebus.windows.net) and Windows NTP as a default, but also covers Linux-related endpoints (e.g., packages.microsoft.com, linuxgeneva-microsoft.azurecr.io). Windows tools and URLs are mentioned, sometimes before Linux equivalents. However, the requirements are generally platform-neutral, and Linux endpoints are present. No PowerShell-specific instructions or Windows-only commands are given.
Recommendations
  • Clarify when Windows-specific endpoints (e.g., time.windows.com) are only required for Windows deployments, and provide Linux NTP alternatives (e.g., pool.ntp.org) if relevant.
  • Ensure Linux-related endpoints and tools are mentioned with equal prominence and detail as Windows ones.
  • Where possible, add notes or examples for Linux management machines (e.g., how to configure outbound connectivity, NTP, etc.).
  • Review the order of endpoint listings to avoid Windows-first bias unless justified by usage statistics.
GitHub Create Pull Request
Azure Arc Set Up Workload Orchestration .../workload-orchestration/initial-setup-configuration.md
Low Priority View Details →
Scanned: 2026-02-22 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 commands, but the PowerShell section is presented after Bash and is equally detailed. There is no evidence of Windows-only tools or patterns, and the Azure CLI is used throughout, which is cross-platform. However, the inclusion of PowerShell examples may suggest a slight Windows bias, especially since PowerShell is primarily associated with Windows, though it is now available cross-platform. No Linux-specific tools or patterns are missing, and Bash is presented first.
Recommendations
  • Clarify that PowerShell examples are valid for Linux/macOS users (since PowerShell Core is cross-platform).
  • Consider adding a note that Bash examples are suitable for Linux/macOS and PowerShell for Windows, or for users who prefer PowerShell on any OS.
  • If possible, provide explicit guidance for macOS users (e.g., mention terminal usage or prerequisites for PowerShell Core).
  • Ensure that any referenced scripts or files (such as onboarding scripts) are compatible with both Bash and PowerShell environments.
GitHub Create Pull Request
Azure Arc Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc ...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority View Details →
Scanned: 2026-02-22 00:00
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 the Linux example is presented first and is more concise. The Windows section introduces certutil and findstr, which are Windows-specific tools, but does not provide PowerShell alternatives or parity for Linux users. All other examples (openssl, Azure CLI, kubectl) are cross-platform and do not show Windows bias.
Recommendations
  • Clarify that certutil and findstr are Windows-specific and provide PowerShell alternatives for base64 encoding if possible.
  • For Linux, mention that base64 is available on macOS as well, and provide explicit macOS instructions if any differences exist.
  • Consider providing a table summarizing equivalent commands for Linux, macOS, and Windows for base64 encoding.
  • Ensure parity in instructions for removing headers from base64 output for both platforms.
GitHub Create Pull Request
Azure Arc Simplify network configuration requirements with Azure Arc gateway ...zure-arc/kubernetes/arc-gateway-simplify-networking.md
Low Priority View Details →
Scanned: 2026-02-22 00:00
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 consistently presents Azure PowerShell (a Windows-centric tool) alongside Azure CLI. In several sections, PowerShell is given equal prominence, and in some cases, appears before or immediately after CLI examples. There are no Linux-specific command-line examples (such as Bash scripts or references to Linux-native tools), but Azure CLI is cross-platform and is shown first in most cases. No Windows-only tools or patterns are mentioned, and the documentation does not reference Windows-specific behaviors. However, the presence of PowerShell examples may create minor friction for Linux/macOS users, as PowerShell is less commonly used on those platforms.
Recommendations
  • Clearly indicate that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
  • Add explicit notes or callouts for Linux/macOS users, clarifying that Azure PowerShell is optional and Azure CLI is fully supported.
  • Consider including Bash shell script examples or references to Linux-native workflows where relevant.
  • Ensure Azure CLI examples are always shown first and are complete for all tasks.
  • Optionally, provide links to PowerShell installation instructions for Linux/macOS users if PowerShell usage is necessary.
GitHub Create Pull Request
Azure Arc Simplify Network Configuration Requirements with Azure Arc Gateway ...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Low Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Windows Tools
Summary
The documentation provides examples for Azure portal, Azure CLI, and PowerShell throughout, with PowerShell examples included for all major operations. CLI examples use backtick (`) line continuations, which are PowerShell-specific and may confuse Linux/macOS users. The order of examples is consistently Portal, CLI, then PowerShell, putting Windows-centric tools last but CLI examples use Windows-style syntax. There is a minor bias in log file paths, but both Windows and Linux are covered. Endpoint tables clearly distinguish Linux and Windows requirements. Overall, Linux users can complete all tasks, but some friction exists due to Windows-centric syntax and PowerShell prominence.
Recommendations
  • Use standard bash-style line continuations (\) in Azure CLI examples, or provide both Windows and Linux/macOS CLI syntax.
  • Explicitly note that Azure CLI commands work on Linux/macOS and provide example commands for those platforms.
  • Consider listing CLI examples before PowerShell, or clarify that PowerShell is Windows-only.
  • Where file paths are mentioned, always show both Windows and Linux/macOS paths side-by-side.
  • Add a brief note at the start clarifying cross-platform support and tool parity.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions Azure CLI, PowerShell, and REST API as supported experiences, listing PowerShell (a Windows-centric tool) before REST API. However, it also clearly states support for both Windows and Linux operating systems and does not provide any Windows-only examples or tools in the main content. There is a minor bias in listing PowerShell before Linux-native tools, but no critical sections are Windows-only.
Recommendations
  • When listing supported experiences, consider mentioning Azure CLI (cross-platform) first, followed by PowerShell and REST API, to emphasize Linux parity.
  • Add explicit statements or examples highlighting Linux support, such as referencing Bash or shell scripting alongside PowerShell.
  • Ensure linked pages (CLI, PowerShell, REST) provide balanced examples for both Windows and Linux environments.
GitHub Create Pull Request
Azure Arc Simplify Network Configuration Requirements with Azure Arc Gateway ...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Low Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Windows Tools
Summary
The documentation provides both Windows (PowerShell) and Linux (CLI) examples for all critical operations, but Windows/PowerShell examples are often presented before Linux/CLI equivalents. Some minor notes reference Windows-specific behaviors (e.g., setting --gateway-resource-id to null in PowerShell), and Windows Admin Center is mentioned as a scenario, but Linux parity is generally maintained. The log file paths and instructions are clearly separated for Windows and Linux. There are no sections where Linux users are unable to complete tasks, but Windows examples are sometimes prioritized.
Recommendations
  • Alternate the order of CLI and PowerShell examples so Linux users see their platform first in some sections.
  • Explicitly state that all CLI commands work on Linux/macOS and Windows, and clarify any platform-specific nuances.
  • Where possible, provide Bash shell script examples alongside PowerShell for automation.
  • Review scenario lists to ensure Linux-relevant tools are mentioned equally (e.g., highlight SSH for Linux as well as Windows Admin Center).
GitHub Create Pull Request
Azure Arc Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc ...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation provides both Linux and Windows methods for base64 encoding files, but the Linux example is presented first and is more concise. The Windows section uses certutil and findstr, which are Windows-specific tools, and requires manual header removal. No PowerShell examples are given, and all other commands (openssl, kubectl, Azure CLI) are cross-platform. The Windows instructions are present but not prioritized or exclusive.
Recommendations
  • Add explicit macOS instructions for base64 encoding (if any differences exist).
  • Clarify that Azure CLI, kubectl, and openssl commands work on Windows, Linux, and macOS.
  • Consider providing PowerShell alternatives for base64 encoding on Windows, as many users may prefer PowerShell over certutil.
  • Mention that Linux commands also work on macOS, or provide macOS-specific notes if needed.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation presents Windows and Linux VM extension tables separately, but Windows extensions are listed first and in greater detail. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are mentioned together, without prioritizing Windows-specific tools. No examples or walkthroughs are provided in this page, so there is no PowerShell-heavy or missing Linux example bias. Partner extensions are shown for both OSes. Overall, the bias is limited to Windows extensions being presented before Linux extensions.
Recommendations
  • Consider alternating the order of Windows and Linux extension tables, or presenting them together in a unified table to emphasize parity.
  • Explicitly state that all deployment methods (CLI, PowerShell, portal, ARM templates) support both Windows and Linux extensions where applicable.
  • Ensure future documentation sections or linked pages provide Linux examples and instructions alongside Windows ones.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows/PowerShell instructions are consistently presented first and in greater detail (e.g., notes about PowerShell ISE, execution policy). The retry command section also lists Windows before Linux. There is minor bias toward Windows in ordering and depth, but Linux parity is generally maintained.
Recommendations
  • Alternate the order of Windows and Linux instructions, or present them side-by-side to avoid implicit prioritization.
  • Provide equivalent troubleshooting notes for Linux (e.g., shell environment caveats, permissions) as are given for Windows/PowerShell.
  • Ensure all screenshots and UI instructions are OS-neutral or clarify when differences exist.
  • Explicitly state that both Windows and Linux are fully supported and highlight any OS-specific requirements or limitations.
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-21 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 operation, ensuring parity for Linux/macOS and Windows users. However, in most sections, PowerShell examples are presented after Bash examples, which is a minor 'windows_first' bias. There are no Windows-only tools, commands, or patterns used, and all instructions are cross-platform (using Azure CLI and kubectl). No critical steps are Windows-only.
Recommendations
  • Continue to provide both Bash and PowerShell examples for all CLI operations.
  • Consider alternating the order of Bash and PowerShell examples in some sections, or explicitly state that both are equally supported.
  • Add a brief note at the top clarifying that all steps are cross-platform and that users should select the tab matching their environment.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page references SQL Server Management Studio (SSMS) as the primary GUI client, which is Windows-only, and mentions it before the cross-platform sqlcmd tool. However, it does provide a sqlcmd example that works on both Linux and Windows. There are no PowerShell-specific commands, but SSMS is emphasized as a main tool, which may create friction for Linux/macOS users. No Linux-specific GUI clients (e.g., Azure Data Studio, DBeaver) are mentioned.
Recommendations
  • Mention cross-platform GUI clients such as Azure Data Studio or DBeaver alongside SSMS.
  • Provide explicit examples for connecting from Linux/macOS using these clients.
  • Clarify that sqlcmd is available on both Linux and Windows, and provide installation instructions for Linux/macOS.
  • Consider showing Linux/macOS examples first or equally alongside Windows examples.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation primarily uses Azure CLI and kubectl commands, which are cross-platform. However, there are subtle signs of Windows bias: Windows/Mac installation instructions for Azure kubelogin are mentioned first, while Linux instructions are provided later. There are no explicit PowerShell examples, but Azure CLI is often associated with Windows users. Some instructions (such as editing files with 'vi') assume a Linux environment, but overall, the documentation does not provide Linux-specific troubleshooting or examples before Windows/Mac. The bias is minor and does not prevent Linux/macOS users from completing tasks.
Recommendations
  • Present installation instructions for Azure kubelogin for Linux, Mac, and Windows in parallel or in a table, rather than listing Windows/Mac first.
  • Explicitly state that Azure CLI and kubectl are cross-platform and provide links to installation instructions for all OSes.
  • Add troubleshooting tips for Linux-specific issues (e.g., file permissions, SELinux, systemd) where relevant.
  • Ensure that all commands and examples are clearly marked as cross-platform, and highlight any OS-specific steps.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent, with clear parity in feature and bug fix tracking. However, there is a consistent pattern of listing Windows download links and version numbers before Linux, and Windows-specific tools and patterns (e.g., PowerShell, msiexec, .msi installers) are mentioned explicitly, sometimes without Linux equivalents in the same context. Some troubleshooting and known issues sections reference only Windows installer behaviors and solutions.
Recommendations
  • Alternate the order of Windows and Linux download links and version listings, or present them together to avoid the impression of Windows primacy.
  • Where Windows-specific tools (e.g., PowerShell, msiexec) are mentioned, ensure Linux equivalents (e.g., shell commands, package managers) are also referenced where applicable, or clarify when an issue is Windows-only.
  • In known issues and troubleshooting sections, provide Linux-specific guidance if relevant, or explicitly state when an issue does not affect Linux.
  • Consider including a summary table or section highlighting cross-platform parity and any OS-specific differences to make it clear when features or fixes apply to only one OS.
GitHub Create Pull Request
Azure Arc Simplify network configuration requirements with Azure Arc gateway ...zure-arc/kubernetes/arc-gateway-simplify-networking.md
Low Priority View Details →
Scanned: 2026-02-21 00:00
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 examples are consistently presented alongside CLI, sometimes before Linux-specific guidance. There is no explicit Linux example (e.g., Bash scripts), but CLI commands are cross-platform. PowerShell is a Windows-centric tool, and its inclusion may create friction for Linux/macOS users. However, the CLI examples are sufficient for Linux parity, and environment variable instructions use both export (Linux/macOS) and $Env (Windows/PowerShell) syntax.
Recommendations
  • Continue to provide Azure CLI examples as the primary cross-platform method.
  • Consider explicitly stating that Azure CLI commands are supported on Linux/macOS and Windows.
  • Optionally, clarify that PowerShell examples are for Windows users, and CLI is recommended for Linux/macOS.
  • Add brief Bash script examples for common tasks, if relevant.
  • Ensure that any environment variable instructions always show both export (Linux/macOS) and $Env (Windows/PowerShell) syntax.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page lists both Windows and Linux-related endpoints, but there is evidence of Windows bias: Windows-specific services (e.g., time.windows.com, sts.windows.net, login.windows.net, servicebus.windows.net) are referenced, and Windows NTP is mentioned explicitly. Windows terminology (e.g., 'Management machine', 'Windows NTP') appears before Linux equivalents, and Windows endpoints are listed before Linux ones in some cases. However, Linux endpoints (e.g., packages.microsoft.com, linuxgeneva-microsoft.azurecr.io) are also included, and SSH is referenced as a connectivity requirement, which is cross-platform.
Recommendations
  • Clarify that NTP can use Linux NTP servers (e.g., pool.ntp.org) and provide guidance for Linux/macOS users.
  • Mention Linux alternatives or equivalents for Windows-specific endpoints where applicable.
  • Ensure examples and terminology are balanced, e.g., refer to 'management machine (Windows or Linux)' instead of just 'management machine'.
  • List Linux-related endpoints and requirements alongside Windows ones, not after.
  • Add explicit notes for Linux/macOS users where Windows-specific services are referenced.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for acquiring access tokens with managed identity on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first, with more detailed scripting and output illustration. PowerShell is emphasized in related content, and Windows prerequisites are listed before Linux. Overall, Linux parity is maintained, but Windows is subtly prioritized.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
  • Ensure that Bash/Linux examples are as detailed and illustrated as PowerShell/Windows examples, including output screenshots.
  • In related content, mention Azure CLI and Bash alternatives before or alongside PowerShell.
  • Clarify that both Windows and Linux are equally supported for managed identity scenarios.
GitHub Create Pull Request
← Previous Page 77 of 94 Next →