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 426-432 of 432 flagged pages
Azure Arc Quickstart: Connect an existing Kubernetes cluster to Azure Arc ...les/azure-arc/kubernetes/quickstart-connect-cluster.md
Low Priority View Details →
Scanned: 2026-01-10 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 instructions for all major steps, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, which is cross-platform. In several places, Windows and Mac instructions are mentioned together, but Linux is not explicitly referenced when discussing local Kubernetes cluster creation. The use of PowerShell examples and environment variable syntax is Windows-first, and Linux-specific instructions (such as bash environment variable syntax) are only present in the Azure CLI sections. There are no Linux-only tools or patterns discussed, and the documentation does not provide Linux-specific troubleshooting or guidance.
Recommendations
  • Explicitly mention Linux as a supported platform when discussing local Kubernetes cluster creation, not just Mac and Windows.
  • Provide Linux-specific environment variable examples in PowerShell sections, or clarify that PowerShell is not available on Linux by default.
  • Add troubleshooting notes or links for Linux-specific issues (e.g., permissions, package installation).
  • Consider listing Azure CLI (the cross-platform tool) before PowerShell in all sections to reinforce platform neutrality.
  • Where Docker Desktop is referenced for Mac and Windows, add a note or link for Linux alternatives (e.g., Minikube, MicroK8s).
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-10 00:00
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 listing ways to run Resource Graph queries, subtly prioritizing Windows-centric tooling. The metadata also tracks Azure PowerShell separately, reinforcing this bias. No explicit Linux/macOS examples or tools are highlighted, though Azure CLI is mentioned.
Recommendations
  • List Azure CLI before Azure PowerShell when describing cross-platform query options.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide example commands for both CLI and PowerShell.
  • Add a note clarifying platform compatibility for each tool.
  • Consider including screenshots or walkthroughs for running queries on Linux/macOS terminals.
GitHub Create Pull Request
Azure Arc Authenticate against Azure resources with Azure Arc-enabled servers ...s/azure-arc/servers/managed-identity-authentication.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents both Windows (PowerShell) and Linux (Bash) examples for authenticating against Azure resources with Azure Arc-enabled servers. However, Windows/PowerShell instructions and references are frequently listed first, and PowerShell is emphasized in key steps (e.g., assigning access policies, next steps). Windows-specific tools and terminology (e.g., IIS, PowerShell, Administrators group) are mentioned more prominently than their Linux equivalents, and links to Windows instructions often precede Linux ones.
Recommendations
  • Alternate the order of Windows and Linux examples throughout the documentation, or present them side-by-side for parity.
  • Provide equal emphasis and detail for Linux/Bash instructions, including screenshots and troubleshooting notes.
  • Reference both Windows and Linux tools/groups in prerequisite and procedural sections, avoiding Windows-first phrasing.
  • Ensure all linked tutorials and next steps offer both PowerShell and Azure CLI (cross-platform) options, with CLI presented as the default or equally with PowerShell.
  • Include explicit notes or callouts for macOS users where applicable.
GitHub Create Pull Request
Azure Arc How to organize and inventory servers using hierarchies, tagging, and reporting ...ticles/azure-arc/servers/organize-inventory-servers.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation describes organizational and inventory features for Azure Arc-enabled servers, claiming support for both Windows and Linux platforms. However, examples and tool references (Azure CLI, PowerShell, ARM templates) are generic and do not provide explicit Linux-specific guidance or examples. The order of tool mention (Azure CLI, PowerShell) and lack of Linux command-line or automation examples suggest a subtle Windows-first bias. There are no explicit Linux shell (bash) or platform-specific instructions, which may leave Linux users needing to infer or adapt steps.
Recommendations
  • Include explicit Linux shell (bash) examples for tagging and querying resources.
  • Clarify any platform-specific differences in onboarding, tagging, or reporting processes for Linux servers.
  • Mention Linux-native tools or automation patterns where relevant (e.g., scripting with bash, using curl, etc.).
  • Ensure parity in example coverage for both Windows and Linux, possibly with side-by-side code blocks.
GitHub Create Pull Request
Azure Arc Azure Arc-enabled servers Overview ...-docs/blob/main/articles/azure-arc/servers/overview.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation generally mentions Windows and Linux support, but Windows-specific tools and patterns (such as PowerShell and Windows registry) are referenced first or exclusively in some sections. Examples and links often default to Windows tabs or content, and Windows terminology (registry, files) is listed before Linux equivalents (daemons). There is an implicit prioritization of Windows in automation and configuration guidance.
Recommendations
  • Ensure all examples and links provide Linux-first or Linux-parity content, such as Bash or shell scripts alongside PowerShell.
  • When listing configuration or monitoring capabilities, alternate or balance the order between Windows and Linux features (e.g., 'Windows registry and files, Linux daemons and configuration files').
  • Explicitly mention Linux tools and patterns (systemd, cron, shell scripting) where Windows tools (PowerShell, registry) are referenced.
  • Provide direct links to Linux-specific documentation or tabs, not just Windows-first or Windows-default tabs.
  • Include Linux/macOS screenshots or walkthroughs where applicable.
GitHub Create Pull Request
Azure Arc Limit access to Run command ...ain/articles/azure-arc/servers/run-command-security.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation presents the Windows example before the Linux example in the section on blocking/allowing Run commands locally. Both platforms are covered with equivalent Azure CLI commands, and no Windows-specific tools or patterns are used. However, the ordering may subtly prioritize Windows users.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which platform is shown first in examples.
  • Explicitly state that both Windows and Linux are supported and that the commands are analogous.
  • Consider adding a short note clarifying parity between platforms for the Run command extension.
GitHub Create Pull Request
Azure Arc Extensions security for Azure Arc-enabled servers ...main/articles/azure-arc/servers/security-extensions.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux examples for most configuration tasks, but Windows examples (PowerShell) are consistently presented first, and references to Windows-specific tools and scenarios (e.g., 'elevated command console', Windows Server 2012 ESU) appear before or more prominently than their Linux equivalents. The CLI examples are present for Linux, but the ordering and language favor Windows users.
Recommendations
  • Alternate the order of Windows and Linux examples so Linux is shown first in some sections.
  • Use neutral language when referring to command consoles (e.g., 'administrator or root shell' instead of 'elevated command console').
  • Provide explicit parity for all examples, ensuring Linux and macOS users see their commands and scenarios equally.
  • Add notes or examples for macOS where relevant, or clarify if features are not supported.
  • Avoid referencing Windows-specific scenarios (e.g., Windows Server 2012 ESU) without mentioning Linux equivalents or clarifying applicability.
GitHub Create Pull Request
← Previous Page 18 of 18 Next →