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 1526-1550 of 2334 flagged pages
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-08 00:53
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 Windows-specific tool (certutil) is mentioned after the Linux example and receives additional explanation, including manual header removal and use of findstr. This section is the only place where platform-specific tooling is discussed, and Windows tools are given extra detail. The rest of the documentation uses cross-platform tools (OpenSSL, Azure CLI, kubectl) and does not show bias in command examples.
Recommendations
  • Provide equivalent Linux commands for header removal after base64 encoding, such as using grep or sed, to match the detail given for Windows.
  • When introducing platform-specific tools, present both Linux and Windows options together, or in parallel subsections, rather than giving extra detail to one platform.
  • Consider adding a table summarizing base64 encoding/decoding commands for both platforms for clarity.
  • Explicitly state that OpenSSL, Azure CLI, and kubectl commands are cross-platform and provide any necessary platform-specific notes if differences exist.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by consistently presenting Windows-centric examples and file paths (e.g., C:\Backupfiles\test.bak) for backup operations, and by referencing Windows tools (Azure Data Studio, SSMS) without mentioning Linux equivalents or providing Linux-specific instructions. There are no examples showing how to perform backup operations on Linux systems, nor are Linux file paths or tools (such as sqlcmd or native Linux editors) mentioned. The use of Windows paths and instructions appears before any mention of Linux-compatible methods, and Linux users are left to infer how to adapt the steps.
Recommendations
  • Add explicit Linux examples for backup and restore commands, using Linux file paths (e.g., /home/user/backup/test.bak).
  • Mention and provide instructions for using Linux-native tools such as sqlcmd, nano/vim, and alternatives to SSMS/Azure Data Studio on Linux.
  • Clarify cross-platform compatibility for Azure Data Studio and Azure Storage Explorer, including installation instructions for Linux.
  • When showing kubectl cp examples, provide both Windows and Linux source file path formats.
  • Ensure that prerequisites and steps do not assume a Windows environment, and highlight any platform-specific differences.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing a path example using Windows-style (C:\temp\logs) and omitting a Linux equivalent (such as /tmp/logs). No Linux-specific examples or notes are given for file paths or usage, despite the cross-platform nature of Azure CLI and Kubernetes tools.
Recommendations
  • Include Linux path examples (e.g., /tmp/logs) alongside Windows examples when demonstrating command usage.
  • Explicitly state that the Azure CLI and Kubernetes tools work on both Windows and Linux, and provide examples for both platforms.
  • Add notes or examples for common Linux shell usage patterns (such as using $HOME or ~ for home directories).
  • Ensure that folder hierarchy and output examples use platform-neutral or dual-platform paths.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions both Linux and Windows automation options, but Windows tools (Task Scheduler, .cmd/.bat/.ps1 scripts) are listed alongside Linux options, and Windows-specific patterns are mentioned before Linux equivalents in some cases. However, the main scripting example is for Linux shell scripts, and Linux tools (cron, chmod, watch) are demonstrated explicitly.
Recommendations
  • Provide explicit Windows PowerShell or batch script examples for automating uploads, similar to the Linux shell script provided.
  • List Linux automation tools (cron) before Windows Task Scheduler to avoid subtle ordering bias.
  • Include step-by-step instructions for setting up scheduled tasks on Windows, not just mentioning Task Scheduler.
  • Clarify cross-platform compatibility of az arcdata commands and note any differences in usage or prerequisites between Windows and Linux.
  • Ensure that all examples and instructions are provided for both Linux and Windows environments, with equal detail.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page shows mild Windows bias by referencing Microsoft-centric tools (Azure Data CLI, Azure Data Studio) and several partner solutions that are Windows-focused (e.g., DataON for Azure Stack HCI, Hitachi UCP with Microsoft AKS-HCI, Lenovo ThinkAgile MX). Linux-native or cross-platform alternatives are not explicitly mentioned, and Windows-oriented solutions are listed before Linux equivalents in some partner sections.
Recommendations
  • Explicitly mention Linux support for Azure Data CLI and Azure Data Studio, or provide alternative Linux-native tools if available.
  • Balance partner solution listings by alternating or grouping Windows and Linux-focused solutions, rather than listing Windows-first.
  • Add examples or guidance for Linux users, such as how to generate and use kubeconfig files on Linux systems.
  • Clarify platform compatibility for each tool and solution, especially for those that are Windows-centric.
  • Include references to Linux distributions and tools (e.g., Ubuntu, CentOS, OpenShift, etc.) in prerequisites and process sections.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/includes/azure-arc-enabled-servers.md ...ticles/azure-arc/includes/azure-arc-enabled-servers.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal for each query. While Azure CLI is cross-platform, the inclusion of Azure PowerShell examples (which are most commonly used on Windows and have a Windows-centric history) and the explicit '[Azure PowerShell]' tab for every scenario introduces a subtle Windows bias. Additionally, the ordering of tabs consistently places Azure PowerShell immediately after Azure CLI, which can reinforce a Windows-first perception. There are no explicit Linux shell examples (e.g., Bash, shell scripting), nor are Linux-native tools or patterns mentioned. However, the use of Azure CLI does provide parity for Linux users, and the queries themselves are platform-neutral.
Recommendations
  • Add explicit Bash/shell script examples for Linux users, demonstrating how to run the Azure CLI queries in a Linux terminal.
  • Clarify that Azure CLI is fully supported on Linux and macOS, and link to installation instructions for those platforms.
  • Consider alternating the order of tabs or grouping Azure CLI and PowerShell under a generic 'Command Line' heading to avoid reinforcing a Windows-first mindset.
  • Where relevant, mention Linux-native tools (e.g., jq, grep) that can be used to process Azure CLI output.
  • If PowerShell examples are included, clarify that PowerShell Core is cross-platform and provide instructions for Linux/macOS installation.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily in the 'Connect to the developer portal' section, where instructions for updating the hosts file are given exclusively for Windows (using Notepad and the Windows file path). There are no equivalent instructions for Linux or macOS users. Additionally, the mention of 'Switch to PowerShell' in Azure Cloud Shell may imply a Windows-first approach, though most command examples use Azure CLI and bash-like syntax.
Recommendations
  • Add instructions for updating the hosts file on Linux (e.g., using sudo nano /etc/hosts) and macOS.
  • Include notes or examples for common Linux/macOS editors (nano, vim, etc.) and file paths.
  • Clarify that the Azure CLI commands can be run in bash/zsh shells on Linux/macOS, and provide any necessary syntax adjustments (e.g., backtick line continuations vs. backslash).
  • When referencing Azure Cloud Shell, mention both Bash and PowerShell options, and clarify which shell is used in examples.
  • Review other sections for subtle Windows-centric language or assumptions, and ensure parity for Linux/macOS users.
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-08 00:53
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, which may suggest a slight Windows-first or PowerShell-heavy bias. There is no explicit Linux shell (bash) example, nor is there mention of Linux-specific tools or patterns.
Recommendations
  • Include a bash shell example using Azure CLI to demonstrate parity for Linux users, e.g., 'az account list-locations --output table'.
  • Clarify that Azure CLI works cross-platform and is recommended for both Windows and Linux environments.
  • If mentioning PowerShell, note that PowerShell Core is available on Linux, or provide context for when to use each tool.
  • Consider listing examples in a neutral order or grouping them by platform to avoid perceived prioritization.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/extensions-troubleshooting.md ...les/azure-arc/kubernetes/extensions-troubleshooting.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias in a few areas. The Azure CLI is used throughout, which is cross-platform, but some troubleshooting steps and examples reference Windows-centric tools and patterns before their Linux equivalents. For example, the use of iptables troubleshooting is described in the context of Oracle Linux, but the error message and remediation steps are presented in a way that assumes familiarity with Windows-style error output and troubleshooting. Additionally, the documentation references Azure-specific features and tools (such as Azure Policy, Azure Monitor, and Azure CLI) that are more commonly used and documented in Windows environments, with less emphasis on Linux-native alternatives or patterns.
Recommendations
  • Provide explicit Linux and macOS command examples alongside Azure CLI, especially for troubleshooting steps that may differ on non-Windows platforms.
  • Include references to Linux-native tools and troubleshooting patterns (e.g., systemd, journalctl, dmesg) where relevant, especially when discussing pod and container errors.
  • Clarify cross-platform compatibility of Azure CLI and other tools, and note any platform-specific caveats.
  • When discussing error messages or troubleshooting steps, include both Windows and Linux output formats if they differ.
  • Expand troubleshooting sections to mention Linux-specific issues and solutions, such as SELinux, AppArmor, or differences in networking stack behavior.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/includes/network-requirements-azure-cloud.md ...ubernetes/includes/network-requirements-azure-cloud.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias by listing several endpoints with '.windows.net' and 'login.windows.net' before their Linux equivalents or alternatives. The use of 'windows.net' endpoints is prevalent, and Windows-centric terminology appears before Linux-specific references. However, there are some Linux mentions (e.g., 'linuxgeneva-microsoft.azurecr.io'), and the page does not provide command-line examples, so there is no Powershell-heavy or missing Linux example bias.
Recommendations
  • Ensure endpoint lists do not prioritize Windows-named endpoints over Linux or neutral ones; group them by function or alphabetical order.
  • Add explicit notes clarifying that endpoints such as 'login.windows.net' and 'sts.windows.net' are used by both Windows and Linux agents.
  • Where possible, provide parity in documentation language, e.g., mentioning Linux endpoints or tools alongside Windows ones.
  • If command-line examples are added, ensure both Powershell (Windows) and Bash (Linux) examples are provided.
  • Clarify that Azure Arc agents and endpoints are cross-platform, and avoid implying Windows exclusivity in endpoint naming.
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-08 00:53
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 GUI commonly used by Windows administrators) for resource creation and management steps, and by omitting any Linux-specific or cross-platform command-line examples for critical operations such as DNS configuration, firewall setup, and resource provisioning. The only CLI example provided is for the Azure CLI, which is cross-platform, but there are no Linux shell commands or guidance for common Linux tools (e.g., iptables, systemd-resolved, BIND, dnsmasq) for DNS or firewall configuration. Troubleshooting steps use 'nslookup', which is available on both platforms, but do not mention Linux alternatives or context. There is no mention of PowerShell, but the overall workflow assumes familiarity with Azure portal and Windows-centric network administration patterns.
Recommendations
  • Add Linux-specific examples for DNS server configuration (e.g., BIND, dnsmasq, systemd-resolved) and provide sample configuration files or commands.
  • Include firewall configuration examples for common Linux firewalls (e.g., iptables, firewalld, ufw) alongside general guidance.
  • Provide CLI-based resource creation steps using Azure CLI or ARM templates, and clarify that these can be run on Linux, macOS, or Windows.
  • Explicitly mention that the Azure CLI commands and troubleshooting steps are cross-platform, and provide any necessary Linux-specific notes (e.g., package installation, command syntax differences).
  • Where screenshots of the Azure portal are used, offer equivalent CLI instructions for users who prefer or require command-line automation, especially for Linux environments.
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-08 00:53
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 Azure CLI installation links that default to Windows, and by not providing explicit Linux or macOS instructions or examples for management machine setup. There are no examples or guidance for Linux-specific installation, usage, or troubleshooting, despite Azure CLI being cross-platform. The documentation also omits mention of Linux tools or patterns, and does not clarify whether Linux management machines are supported or recommended.
Recommendations
  • Add explicit instructions and links for installing Azure CLI on Linux and macOS, alongside the Windows instructions.
  • Provide examples of deployment and management commands run from Linux and macOS environments.
  • Clarify that the management machine can be Linux, Windows, or macOS, and list any OS-specific requirements or caveats.
  • Include troubleshooting steps or notes for common issues on Linux (e.g., permissions, networking, file locations).
  • Ensure parity in documentation for all supported platforms, including screenshots or terminal output from Linux shells where appropriate.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/resource-bridge/maintenance.md ...main/articles/azure-arc/resource-bridge/maintenance.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page describes Azure Arc resource bridge maintenance operations but does not provide platform-specific examples or instructions. However, there is a notable absence of Linux-specific guidance, and the only credential maintenance examples reference VMware vSphere and SCVMM, which are traditionally Windows-centric environments. All command-line instructions use the Azure CLI, which is cross-platform, but there are no explicit Linux shell or script examples, nor any mention of Linux-specific tools or patterns. The documentation implicitly assumes familiarity with Windows-centric infrastructure and omits Linux parity in examples and troubleshooting.
Recommendations
  • Add explicit Linux shell (bash) examples for Azure CLI commands, showing usage on Linux systems.
  • Include troubleshooting steps or maintenance patterns relevant to Linux-based appliance VMs, if supported.
  • Reference Linux-based infrastructure management scenarios alongside Windows/SCVMM and VMware vSphere.
  • Clarify whether the appliance VM can be Linux-based and provide credential update instructions for Linux environments.
  • Ensure parity in examples and guidance for both Windows and Linux administrators.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation shows mild Windows bias by listing Windows-specific authentication methods first and referencing PowerShell tools for access token retrieval, while Linux equivalents are not mentioned. The interactive browser login is described as 'Windows only' and presented before Linux-default device code login. The access token section references PowerShell's Get-AzAccessToken without mentioning Linux alternatives.
Recommendations
  • Present authentication options in a neutral order or alternate which OS is mentioned first.
  • For access token retrieval, mention Linux-compatible methods (e.g., Azure CLI's 'az account get-access-token') alongside PowerShell.
  • Clarify which authentication options are available on both Windows and Linux, and provide explicit Linux examples where appropriate.
  • Ensure that all examples and instructions are cross-platform, or provide parallel examples for both Windows and Linux environments.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is focused exclusively on Windows Server 2012 and Windows Server 2012 R2, with all examples and API payloads referencing Windows-specific targets. There are no examples or guidance for Linux systems, nor is there mention of Linux equivalents or parity in license management. The only OS mentioned is Windows, and all operational instructions are tailored to Windows environments.
Recommendations
  • Add examples and guidance for managing Extended Security Updates licenses for Linux servers, if supported.
  • Explicitly state whether Linux systems are supported or not, and provide parity in API payloads and CLI commands for Linux targets.
  • Include references to Linux-specific tools or patterns (e.g., bash, shell scripts) alongside Azure CLI examples.
  • Clarify in the introduction that the scope is limited to Windows if Linux is not supported, or expand the scope to include Linux where possible.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on Windows Server 2012 and SQL Server 2012, with all examples and endpoint descriptions tailored to Windows environments. There are no mentions of Linux servers, Linux-specific endpoints, or guidance for Linux-based Azure Arc-enabled servers. The documentation assumes a Windows-centric use case and omits Linux parity in both product support and operational instructions.
Recommendations
  • Explicitly state whether Linux servers are supported or not for Extended Security Updates in Azure Arc, and clarify any limitations.
  • If Linux support exists, add equivalent endpoint tables and instructions for Linux-based Azure Arc-enabled servers.
  • Provide examples or notes for Linux package download/update mechanisms (e.g., using wget/curl, package managers) alongside Windows installation instructions.
  • Include guidance on certificate management and connectivity checks for Linux environments.
  • Ensure future documentation covers both Windows and Linux scenarios, or clearly marks Windows-only content.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation describes organizing and inventorying servers with Azure Arc, emphasizing platform breadth but provides examples and tool references (e.g., Azure PowerShell, Azure CLI) without explicit Linux-specific guidance or parity. Windows-centric tools and patterns are mentioned before Linux alternatives, and there are no Linux-specific examples or references to Linux-native management workflows.
Recommendations
  • Include explicit Linux examples for tagging and inventory operations, such as using Bash scripts or Linux-native tools.
  • Mention Linux-specific management patterns (e.g., integration with Ansible, SSH-based workflows) alongside Azure CLI/PowerShell.
  • Clarify that Azure CLI is cross-platform and provide sample commands executed on Linux terminals.
  • Add screenshots or walkthroughs showing Linux server onboarding and management in Azure Arc.
  • Reference Linux documentation or best practices for server organization and tagging in hybrid environments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/security-data-privacy.md ...in/articles/azure-arc/servers/security-data-privacy.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally provides parity between Windows and Linux, especially in log file locations. However, there is evidence of Windows bias: Windows paths are consistently listed before Linux paths in tables, and the only example for retaining Azure Activity logs references PowerShell, with no mention of Bash or CLI alternatives for Linux users.
Recommendations
  • Alternate the order of OS examples in tables, or list Linux first in some cases to avoid implicit prioritization.
  • Provide equivalent Bash or Azure CLI examples alongside PowerShell for tasks such as retaining Azure Activity logs.
  • Explicitly state that all features and commands are supported on both Windows and Linux, and link to platform-specific guidance where relevant.
  • Review other sections for subtle language or tool prioritization and ensure Linux is equally represented.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/security-networking.md ...main/articles/azure-arc/servers/security-networking.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions Windows Admin Center as a tool for server access, but does not mention any equivalent Linux tools (such as SSH clients or Cockpit). There are no examples or references to Linux-specific patterns or tools, and the only access method called out by name is Windows-centric. This creates a subtle bias towards Windows environments and may leave Linux administrators without clear guidance.
Recommendations
  • Mention Linux-native access methods such as SSH, and clarify their support or limitations with private endpoints.
  • If Windows Admin Center is referenced, also mention comparable Linux tools (e.g., Cockpit, Webmin) or standard SSH usage.
  • Provide examples or notes for both Windows and Linux environments when discussing server management and network access.
  • Explicitly state any differences in behavior or support between Windows and Linux servers for Azure Arc networking features.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/administer-arc-scvmm.md ...center-virtual-machine-manager/administer-arc-scvmm.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on Azure CLI commands and Azure portal workflows, which are cross-platform, but all operational context is centered on System Center Virtual Machine Manager (SCVMM)—a Windows-only technology. There are no Linux-specific examples, nor is there mention of Linux tools, shell commands, or Linux administration patterns. The only credential update and log collection examples assume Windows-based infrastructure and do not address Linux-based alternatives or mixed environments.
Recommendations
  • Explicitly state platform requirements and limitations (e.g., SCVMM is Windows-only) at the beginning of the documentation.
  • Provide guidance for administrators working from Linux or macOS workstations, such as how to install and use Azure CLI and SSH from those platforms.
  • Include example commands using Bash or other Linux shells for credential updates and log collection, especially where SSH is involved.
  • Clarify whether the Azure Arc resource bridge VM or management cluster can be administered from Linux, and provide instructions if possible.
  • Mention any Linux-compatible alternatives or integration points, if available, for hybrid environments.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively references SCVMM (System Center Virtual Machine Manager), a Windows-only tool, and provides instructions solely through the Azure portal UI without mentioning any Linux-based management tools, command-line interfaces, or cross-platform alternatives. There are no Linux or PowerShell/CLI examples, nor is there any guidance for users who might be managing resources from non-Windows environments.
Recommendations
  • Explicitly state that SCVMM is a Windows-only technology and clarify platform requirements.
  • Provide guidance or references for Linux users, such as how to interact with Azure Arc resources using Azure CLI or REST APIs from Linux systems.
  • Include examples of role assignment using cross-platform tools (e.g., Azure CLI, which runs on Linux, macOS, and Windows), not just portal UI steps.
  • Mention any limitations or alternatives for users who do not have access to Windows environments.
  • If possible, link to documentation on managing Azure Arc resources from Linux or other non-Windows platforms.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/terraform-vm-management.md ...ter-virtual-machine-manager/terraform-vm-management.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on SCVMM (System Center Virtual Machine Manager), a Windows-centric virtualization management platform, and provides only generic Terraform examples without any OS-specific instructions. All user variables and examples assume Windows conventions (e.g., 'Administrator' username, domain/workgroup settings), and there are no Linux-specific examples, notes, or parity guidance. The documentation does not mention Linux VMs, Linux authentication patterns, or provide examples for managing Linux-based SCVMM VMs.
Recommendations
  • Add explicit examples for provisioning and managing Linux VMs via SCVMM, including sample variables.tf and main.tf files with Linux conventions (e.g., 'adminuser', SSH keys, etc.).
  • Include notes or sections describing differences in VM provisioning for Linux vs. Windows, such as OS profile settings, authentication, and agent installation.
  • Provide guidance on installing the Azure Arc agent on Linux VMs managed by SCVMM, including required credentials and steps.
  • Ensure that documentation references both Windows and Linux VM management scenarios, and avoid using only Windows-centric terminology (e.g., 'Administrator', 'domain', 'workgroup') in generic examples.
  • Where possible, mention Linux equivalents or considerations alongside Windows-specific instructions, especially in prerequisites and best practices.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/administer-arc-vmware.md ...cles/azure-arc/vmware-vsphere/administer-arc-vmware.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 Azure CLI commands and workflows that are most commonly used on Windows, without providing explicit Linux or cross-platform alternatives. There are no examples or instructions for Linux-specific tools, shell environments, or command syntax (e.g., Bash, SSH usage from Linux, file paths). The instructions and screenshots focus on Azure Portal and CLI usage, which, while technically cross-platform, are presented in a way that assumes a Windows-centric environment (e.g., 'current CLI directory' without clarifying path conventions, no mention of Linux shell usage).
Recommendations
  • Add explicit Linux/Bash examples for all CLI commands, including sample shell syntax and file path conventions.
  • Clarify that Azure CLI is cross-platform and provide guidance for installation and usage on Linux systems.
  • Include instructions for using SSH from Linux workstations, with sample commands and expected output.
  • Mention differences in file storage locations and permissions between Windows and Linux environments when handling kubeconfig and .yaml files.
  • Add screenshots or terminal output from Linux environments to balance the visual representation.
  • Where relevant, reference Linux-native tools (e.g., scp, rsync) for file transfer and log collection.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/create-custom-roles.md ...ticles/azure-arc/vmware-vsphere/create-custom-roles.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references the Azure portal and mentions Azure PowerShell before Azure CLI, with no explicit Linux-specific guidance or examples. There are no Linux shell or cross-platform command-line examples, and the workflow is described primarily through the Azure portal UI, which is platform-agnostic but often associated with Windows environments. The mention of Azure PowerShell before Azure CLI subtly prioritizes Windows tooling. No Linux-specific tools, shell commands, or screenshots are provided.
Recommendations
  • Provide explicit Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
  • Include Linux shell command examples for managing custom roles, such as using az role definition create/update commands.
  • Clarify that the Azure portal and Azure CLI are fully supported on Linux, and add notes or links for Linux users where appropriate.
  • If screenshots are included, ensure they are not Windows-specific (e.g., avoid showing Windows taskbars or UI elements).
  • Consider adding a section or callout for Linux/macOS users, highlighting any platform-specific considerations or tips.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/quick-start-create-a-vm.md ...es/azure-arc/vmware-vsphere/quick-start-create-a-vm.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. VM templates and example variable values consistently use Windows-centric names (e.g., 'contoso-template-win22', 'Administrator' as the default username), and there are no Linux-specific examples or references. All sample code and walkthroughs omit Linux VM scenarios, Linux usernames, or Linux template IDs, despite VMware vCenter supporting both Windows and Linux guests.
Recommendations
  • Include Linux VM examples alongside Windows examples in both Bicep and Terraform sections (e.g., show template IDs for Linux VMs, use 'ubuntu' or 'centos' in variable values).
  • Provide sample values for Linux admin usernames (e.g., 'azureuser', 'root') and passwords.
  • Explicitly mention that both Windows and Linux VMs are supported and provide guidance for Linux-specific provisioning steps if any exist.
  • In best practices, add notes relevant to Linux VM management (e.g., SSH key usage, Linux guest agent installation).
  • Balance the documentation by alternating Windows and Linux references in variable names, template IDs, and walkthroughs.
GitHub Create Pull Request
← Previous Page 62 of 94 Next →