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 351-375 of 2334 flagged pages
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/remove-scvmm-from-azure-arc.md ...virtual-machine-manager/remove-scvmm-from-azure-arc.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias by prioritizing Windows-specific instructions and tools. The deboarding script is only available for Windows/PowerShell, with no Linux equivalent or instructions. Windows uninstall steps are described first and in greater detail, while Linux instructions are brief and lack parity in tooling. The use of PowerShell and Windows-centric management patterns is prevalent, and Linux users are left with manual, less integrated steps.
Recommendations
  • Provide a Linux-compatible deboarding script or manual CLI instructions for Linux environments.
  • Offer Linux examples and tooling alongside Windows instructions, not just as an afterthought.
  • Ensure parity in detail and guidance for both Windows and Linux uninstall steps.
  • Mention cross-platform alternatives to PowerShell where possible, such as Bash scripts or Azure CLI.
  • Explicitly state platform limitations and offer workarounds for Linux users.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/clean-up-script.md ...es/azure-arc/workload-orchestration/clean-up-script.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively provides a PowerShell script for resource clean-up, with all usage examples and instructions tailored to Windows environments. There is no mention of Linux-compatible alternatives (such as Bash scripts or Azure CLI commands), nor are Linux usage patterns or cross-platform considerations addressed. This creates a Windows-centric bias and may hinder users working on Linux or macOS systems.
Recommendations
  • Provide equivalent clean-up instructions using Bash scripts or Azure CLI commands that work natively on Linux/macOS.
  • Include explicit examples for running the clean-up process on Linux (e.g., using 'az group delete' or a Bash script).
  • Clarify cross-platform compatibility of the provided script, or offer a platform-neutral version.
  • List Linux/macOS instructions alongside Windows/PowerShell instructions, ensuring parity and accessibility for all users.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/how-to-stage.md ...icles/azure-arc/workload-orchestration/how-to-stage.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Bash and PowerShell examples for all major steps, but PowerShell is given equal prominence and detail, which may reflect a Windows-centric approach. Some commands and instructions (such as file encoding notes and base64 encoding) include Windows-specific details or tools (e.g., PowerShell's ConvertTo-Json, Out-File, [Convert]::ToBase64String), and the use of PowerShell tabs throughout signals parity but also a strong Windows orientation. The troubleshooting and portal instructions reference the Azure portal, which is cross-platform, but the CLI examples and scripting guidance are heavily focused on Windows and PowerShell, with no mention of Linux-specific nuances (such as file permissions, shell differences, or alternative editors). There is no explicit Linux bias, but the documentation does not address Linux-specific issues or provide guidance for Linux users beyond Bash commands.
Recommendations
  • Add explicit notes about Linux-specific considerations, such as file permissions, common editors (vim, nano), and troubleshooting steps for Linux environments.
  • Include examples for common Linux shell environments beyond Bash, such as Zsh, where relevant.
  • Where file encoding is discussed, mention Linux tools (iconv, dos2unix) for converting between UTF-8 and UTF-8 with BOM.
  • In base64 encoding sections, reference Linux commands (base64) and clarify differences in output between Linux and Windows.
  • Review all steps for any implicit Windows assumptions (such as file paths, environment variables, or command syntax) and clarify for Linux users.
  • Consider adding a 'Linux troubleshooting' section for common issues encountered on Linux systems.
  • Ensure that PowerShell examples do not assume Windows-only environments, and clarify cross-platform support for PowerShell Core on Linux.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/choose-service.md ...nt-docs/blob/main/articles/azure-arc/choose-service.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and scenarios (e.g., SCVMM, Extended Security Updates for Windows Server, Azure VMware Solution onboarding with Windows tabs) are mentioned more frequently and in greater detail than Linux equivalents. PowerShell is referenced as a primary automation tool, while Linux-specific management tools and examples are absent. The onboarding and management guidance often defaults to Windows-centric workflows, and examples or references for Linux are either missing or less prominent.
Recommendations
  • Add explicit Linux onboarding examples and workflows alongside Windows instructions, including links to Linux-specific documentation.
  • Ensure automation examples include Bash, shell scripts, or Linux-native tools in addition to PowerShell.
  • Highlight Linux management scenarios (e.g., patching, monitoring, security) with equal detail as Windows, including supported Linux distributions.
  • Mention Linux equivalents for Windows-specific tools (e.g., alternatives to SCVMM for Linux VM management).
  • Balance references to Windows and Linux in tables, feature lists, and recommendations, making it clear that both platforms are first-class citizens.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/container-storage/includes/multi-node-edge-essentials.md ...ntainer-storage/includes/multi-node-edge-essentials.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell-based examples (Invoke-AksEdgeNodeCommand) for configuring Linux nodes. It relies on a Windows-centric orchestration tool rather than showing native Linux commands or scripts, and does not provide direct Linux shell equivalents for the described tasks.
Recommendations
  • Include native Linux shell command examples (bash) for each configuration step, so users managing Linux clusters directly can follow along without requiring Windows or PowerShell.
  • Clarify whether Invoke-AksEdgeNodeCommand is mandatory, or if these steps can be performed directly on Linux nodes using standard tools (e.g., echo, tee, apt, systemctl).
  • Add a section or sidebar specifically for Linux-only environments, detailing how to perform these tasks without any Windows or PowerShell dependencies.
  • Ensure parity in documentation by presenting Linux-native instructions first or alongside any Windows/PowerShell-based orchestration methods.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/container-storage/includes/single-node-edge-essentials.md ...tainer-storage/includes/single-node-edge-essentials.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page, while focused on Linux preparation, demonstrates Windows bias by using Windows-centric tools (Invoke-AksEdgeNodeCommand) for Linux configuration, referencing Notepad as the default text editor, and relying on PowerShell-style cmdlets for Linux node management. Linux-native approaches (e.g., direct use of SSH, nano/vim for editing, bash commands) are missing or not prioritized.
Recommendations
  • Provide Linux-native command examples for configuration tasks, such as using SSH and bash directly instead of Windows PowerShell cmdlets.
  • Suggest Linux text editors (e.g., nano, vim, gedit) alongside or before Notepad for editing configuration files.
  • Include instructions for running sysctl and editing config files directly on Linux, rather than through Windows-based tools.
  • Clarify when Windows tools are required and offer Linux alternatives for all steps.
  • Ensure that all examples and workflows can be completed entirely from a Linux environment without reliance on Windows or PowerShell.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/backup-controller-database.md .../articles/azure-arc/data/backup-controller-database.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing only PowerShell examples for connecting to the SQL Server pod and running T-SQL commands, without offering equivalent Linux shell (bash) examples. The use of PowerShell syntax (e.g., command blocks labeled as 'powershell') and lack of Linux-specific instructions may hinder Linux users, especially since Kubernetes and container environments are commonly managed from Linux systems.
Recommendations
  • Add Linux/bash equivalents for all PowerShell command examples, especially for connecting to the SQL Server pod and running sqlcmd.
  • Label command blocks appropriately (e.g., 'bash' or 'console') rather than 'powershell' when the commands are cross-platform.
  • Explicitly mention that the commands can be run from both Windows and Linux environments, and provide any necessary notes about differences (e.g., path separators, shell quoting).
  • Include guidance for installing and using sqlcmd on Linux, if not already present.
  • Review the documentation for other places where Windows tools or patterns are assumed, and ensure Linux parity.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/connect-active-directory-sql-managed-instance.md .../data/connect-active-directory-sql-managed-instance.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows-based tools (SSMS, ADS) are mentioned and visually highlighted, while Linux/Mac OS connection instructions are limited to command-line sqlcmd and kinit. The Windows connection example appears before the Linux/Mac OS section, and graphical connection steps are not provided for Linux clients. There is no mention of Linux-native graphical tools or parity in screenshots/examples.
Recommendations
  • Include graphical connection instructions and screenshots for Azure Data Studio on Linux/Mac OS.
  • Mention and provide examples for Linux-native SQL clients (e.g., DBeaver, SquirrelSQL) where appropriate.
  • Present Linux/Mac OS connection examples before or alongside Windows examples to avoid ordering bias.
  • Clarify tool availability across platforms (e.g., Azure Data Studio is cross-platform, SSMS is Windows-only).
  • Add troubleshooting tips specific to Linux environments (e.g., Kerberos configuration, DNS setup).
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/automated-integration-testing.md ...ticles/azure-arc/data/automated-integration-testing.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: screenshots and instructions for tasks like converting line endings and generating SAS tokens are shown using Windows tools (VSCode on Windows, Azure Portal), and PowerShell terminals are depicted in images. There is explicit mention of handling Windows-specific issues (CRLF vs LF), but no equivalent guidance for Linux or macOS users. CLI examples are generic (bash), but visual aids and step-by-step instructions favor Windows environments, and Linux alternatives (e.g., using 'dos2unix' for line endings, or Linux-native SAS generation) are missing.
Recommendations
  • Include screenshots and instructions for Linux and macOS environments alongside Windows examples, especially for tasks like line ending conversion and SAS token generation.
  • Mention and demonstrate Linux-native tools (e.g., 'dos2unix' for line ending conversion) and provide command-line alternatives to GUI-based steps.
  • Ensure that all CLI examples are explicitly cross-platform, and clarify any OS-specific caveats for both Windows and Linux/macOS users.
  • Add troubleshooting tips for Linux/macOS users where Windows-specific issues are discussed (e.g., clarify that CRLF is not an issue on Linux, but other encoding issues may arise).
  • Balance the order of presentation so that Linux and Windows instructions/examples are given equal prominence, or group them by OS.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/configure-transparent-data-encryption-manually.md ...data/configure-transparent-data-encryption-manually.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows command examples are consistently presented before Linux equivalents in each tabbed section, and Windows-specific tools and patterns (such as the use of 'type' for file output and Windows path syntax) are highlighted. There is also a note specifically addressing Windows issues with 'kubectl cp', but no equivalent troubleshooting for Linux. The overall structure and example ordering subtly prioritize Windows users, even though Linux examples are present.
Recommendations
  • Alternate the order of Windows and Linux examples in tabbed sections, or present Linux examples first in some cases.
  • Provide troubleshooting notes for both Windows and Linux users, not just Windows.
  • Where possible, use platform-neutral commands or highlight cross-platform alternatives (e.g., use 'cat' for both Windows and Linux via WSL or Git Bash).
  • Explicitly state that both Windows and Linux are supported and encourage parity in example coverage.
  • Consider adding a summary table comparing Windows and Linux workflows for key steps.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-complete-managed-instance-directly-connected.md ...ttps://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-complete-managed-instance-directly-connected.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows file paths in command outputs, omitting Linux-specific instructions or outputs, and implicitly assuming a Windows environment for the user. No Linux/macOS-specific examples, outputs, or troubleshooting notes are provided, despite the cross-platform nature of the tools involved.
Recommendations
  • Provide example outputs for both Windows and Linux/macOS environments, especially where file paths or environment-specific details differ (e.g., ~/.kube/config vs C:\...\.kube\config).
  • Explicitly mention that the Azure CLI, kubectl, and Azure Data Studio are cross-platform, and provide installation or usage notes for Linux/macOS users.
  • Include Linux/macOS-specific troubleshooting tips or notes where relevant.
  • Where file paths or commands differ by OS, present both variants side by side or in tabs.
  • Avoid using Windows-centric terminology or outputs as the default; strive for parity in representation.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-data-controller-direct-prerequisites.md ...rc/data/create-data-controller-direct-prerequisites.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
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, despite PowerShell being primarily a Windows tool. There are no Linux-specific shell examples (e.g., Bash), nor are Linux patterns (such as using native package managers or shell scripts) discussed. The installation instructions for Azure CLI and Helm are platform-agnostic, but there is no explicit mention of Linux or macOS usage, nor are there troubleshooting notes for non-Windows environments.
Recommendations
  • Add explicit Bash/Linux shell examples alongside Azure CLI and PowerShell, especially for steps like installing Azure CLI, Helm, and running connection commands.
  • Clarify that PowerShell is primarily for Windows users and provide equivalent instructions for Linux/macOS users.
  • Include troubleshooting notes or links for common Linux/macOS issues (e.g., permissions, package manager commands).
  • Mention platform-specific prerequisites, such as required dependencies or environment setup for Linux/macOS.
  • Ensure that examples and instructions are presented in a platform-neutral order, or provide tabs for Windows, Linux, and macOS.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/deploy-active-directory-sql-managed-instance.md ...c/data/deploy-active-directory-sql-managed-instance.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Key Active Directory setup steps (such as creating accounts, DNS records, and SPNs) are described using Windows-centric tools and workflows, notably 'Active Directory Users and Computers' and the 'setspn' command, both of which are native to Windows environments. The Windows PowerShell script for keytab generation is mentioned before the Linux shell script, and the overall workflow assumes access to Windows domain controllers and tools. While Linux alternatives for keytab generation are provided, the initial instructions and examples prioritize Windows methods and tools.
Recommendations
  • Provide explicit Linux-based instructions for Active Directory account creation and SPN registration, such as using 'adutil' or 'ldapadd' for account management and SPN registration.
  • Include examples of using Samba tools (e.g., 'samba-tool') for managing Active Directory objects from Linux.
  • Reorder tool and script references so that Linux and Windows options are presented equally, or Linux-first when targeting cross-platform audiences.
  • Add guidance for environments where domain controllers are running on Samba/Unix, not just Windows Server.
  • Clarify which steps require Windows-only tools and offer alternatives or workarounds for Linux administrators.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/deploy-system-managed-keytab-active-directory-connector.md ...eploy-system-managed-keytab-active-directory-connector.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by referencing Windows-specific tools (e.g., 'netdom query fsmo' for identifying the Primary Domain Controller) without providing Linux or cross-platform alternatives. Windows terminology and patterns (such as NetBIOS and AD account naming conventions) are used exclusively or explained first. There are no examples or guidance for performing equivalent tasks from Linux or non-Windows environments, despite the cross-platform nature of Kubernetes and Azure Arc.
Recommendations
  • Provide Linux and cross-platform alternatives for domain controller discovery (e.g., using 'ldapsearch', 'samba-tool', or PowerShell Core on Linux).
  • Include examples of how to interact with Active Directory from Linux environments, such as using 'realm', 'adcli', or 'ldapsearch' for querying domain information.
  • Add notes or sections clarifying how users on Linux or macOS can perform prerequisite steps, especially for Active Directory tasks.
  • Avoid referencing Windows tools exclusively; when mentioning a Windows command, also provide the equivalent for Linux or indicate if a cross-platform tool is available.
  • Ensure terminology and instructions are inclusive of non-Windows environments, especially in cross-platform scenarios like Kubernetes deployments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/deploy-active-directory-sql-managed-instance-cli.md ...ta/deploy-active-directory-sql-managed-instance-cli.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its exclusive focus on Active Directory (AD) integration, which is a Windows-centric authentication technology. All examples and instructions assume the use of AD, with no mention of Linux-native identity solutions (such as LDAP, Kerberos, or FreeIPA). There are no examples or guidance for deploying SQL Managed Instance with non-Windows identity providers, nor is there discussion of Linux-specific tooling or patterns. The documentation also references AD setup and organizational unit (OU) configuration without Linux alternatives, reinforcing a Windows-first approach.
Recommendations
  • Add examples and guidance for integrating SQL Managed Instance with Linux-native identity providers (e.g., LDAP, Kerberos, FreeIPA) where supported.
  • Include documentation on how to perform similar deployments in environments that do not use Active Directory, or clarify AD requirements and alternatives.
  • Provide parity in prerequisites and setup instructions for Linux-based identity management tools.
  • Explicitly state platform requirements and limitations, and offer links to Linux-focused documentation if available.
  • Consider adding troubleshooting or configuration notes for common Linux scenarios (e.g., keytab management, DNS setup on Linux, etc.).
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/deploy-customer-managed-keytab-active-directory-connector.md ...loy-customer-managed-keytab-active-directory-connector.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by focusing exclusively on Active Directory (a Windows-centric technology) and referencing Windows-specific concepts such as NetBIOS names and pre-Windows 2000 naming conventions. There are no examples or guidance for Linux-based directory services, nor is there mention of Linux tools or patterns for AD integration. The documentation assumes familiarity with Windows domain environments and omits Linux equivalents or alternatives.
Recommendations
  • Include examples or guidance for integrating with Linux-based directory services (e.g., LDAP, FreeIPA) where possible.
  • Provide context or alternatives for users who may not have a Windows AD environment, such as how to adapt the connector for non-Windows domains.
  • Add notes on how Linux administrators can obtain required AD information (domain name, DNS servers, NetBIOS name) using Linux tools (e.g., ldapsearch, dig).
  • Clarify whether the connector supports non-Windows directory services, and if not, explicitly state the Windows-only limitation.
  • Balance terminology by explaining Windows-specific concepts (NetBIOS, pre-Windows 2000) for users from Linux backgrounds.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/managed-instance-features.md ...n/articles/azure-arc/data/managed-instance-features.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows Authentication Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (SSMS, SQL Server Data Tools, SQL Server Profiler, SQL Server PowerShell) are listed prominently in the 'Tools' section, with no mention of Linux-native alternatives or cross-platform equivalents. PowerShell scripting support is highlighted in the manageability features, and Windows Authentication is listed as a supported security feature, while Linux authentication mechanisms are not discussed. The overall tooling and examples focus on traditional Windows-centric patterns and utilities, with little to no reference to Linux or open-source alternatives.
Recommendations
  • Include examples and references for Linux-native tools (e.g., sqlcmd, Azure Data Studio on Linux, or other CLI utilities).
  • Mention and provide guidance for authentication mechanisms commonly used on Linux (e.g., Kerberos, certificate-based, or local accounts).
  • Add parity for scripting support by referencing Bash, shell scripting, or Python-based automation alongside PowerShell.
  • Clarify cross-platform compatibility for each tool, indicating which are available on Linux/macOS and how to install/use them.
  • Provide links or documentation for managing SQL Managed Instance enabled by Azure Arc from Linux environments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/privacy-data-collection-and-reporting.md ...zure-arc/data/privacy-data-collection-and-reporting.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias primarily through the use of Windows-centric terminology, examples, and data. SQL Server examples and JSON payloads reference Windows as the operating system (osType: 'Windows'), and the model is 'Hyper-V', a Windows virtualization technology. There are no explicit Linux or cross-platform examples, nor is there mention of Linux-specific tools or patterns. Windows tools and concepts (such as Hyper-V and SQL Server patch levels) are referenced, while Linux equivalents are absent. No PowerShell commands are present, but the overall framing and examples are Windows-centric.
Recommendations
  • Add Linux-specific examples, such as inventory and billing data for SQL Server running on Linux hosts.
  • Include references to Linux virtualization technologies (e.g., KVM, VMware) in addition to Hyper-V.
  • Provide sample JSON payloads with osType set to 'Linux' and appropriate Linux host details.
  • Mention Linux administrative tools and patterns where relevant (e.g., systemd, journalctl, Linux file paths).
  • Ensure that any references to operating system or environment are presented in a cross-platform manner, not assuming Windows as the default.
  • If discussing diagnostic data, include Linux log collection and export methods alongside any Windows approaches.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/resize-persistent-volume-claim.md ...icles/azure-arc/data/resize-persistent-volume-claim.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through the use of PowerShell-style variable assignment (e.g., $newsize=...) in command examples, which is not compatible with Linux/macOS shells. There is no mention of Linux shell equivalents or alternative syntax, and the examples assume a Windows/PowerShell environment for patching PVCs. No Linux-specific instructions or parity guidance is provided.
Recommendations
  • Provide Linux/macOS shell equivalents for variable assignment and kubectl patch commands (e.g., using export or direct inline JSON patching).
  • Explicitly mention compatibility or differences between Windows (PowerShell) and Linux/macOS (bash/zsh) environments.
  • Add examples using bash syntax, such as: newsize='{"spec":{"resources":{"requests":{"storage":"50Gi"}}}}'; kubectl patch pvc ... --patch "$newsize"
  • Clarify that the $newsize variable assignment is PowerShell-specific and provide a bash alternative.
  • Consider reordering examples or providing both Windows and Linux/macOS instructions side-by-side for each step.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/rotate-customer-managed-keytab.md ...icles/azure-arc/data/rotate-customer-managed-keytab.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools (ktpass.exe), providing PowerShell scripts, and describing password changes using Windows GUI tools (Server Manager, Active Directory Users and Computers) without offering equivalent Linux/CLI instructions. While a bash script is mentioned, the process for password rotation is only described for Windows environments, and Linux domain controller scenarios are not addressed.
Recommendations
  • Add instructions for rotating the Active Directory user password using Linux-based domain controller tools (e.g., samba-tool, ldapmodify) and CLI commands.
  • Provide screenshots or command-line examples for Linux environments, not just Windows GUI tools.
  • Ensure parity in troubleshooting steps by mentioning Linux equivalents for any referenced Windows logs or utilities.
  • Clarify which steps/scripts are applicable for Linux-based AD environments and provide guidance for those scenarios.
  • List both bash and PowerShell scripts together, and avoid presenting Windows tools/scripts first unless there is a technical reason.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/upload-metrics-and-logs-to-azure-monitor.md ...e-arc/data/upload-metrics-and-logs-to-azure-monitor.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. Windows and PowerShell examples are presented as primary or separate tabs, often before Linux/macOS equivalents. Windows-specific notes (such as quoting conventions) are highlighted, and references to PowerShell documentation are included in related content. While Linux/macOS examples are present, Windows environments and tools are given prominence.
Recommendations
  • Present Linux/macOS and Windows examples side-by-side or in a neutral order, rather than listing Windows first.
  • Include Bash and Linux shell examples wherever PowerShell or Windows command prompt examples are given.
  • Add Linux-specific notes or troubleshooting tips, not just Windows-specific ones (e.g., quoting conventions, environment variable persistence).
  • Reference Linux and Bash documentation in the 'Related content' section, not only PowerShell.
  • Clarify that Azure CLI and az commands are cross-platform, and avoid implying a Windows-first workflow.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/upload-metrics.md ...cs/blob/main/articles/azure-arc/data/upload-metrics.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides examples for PowerShell and Windows, often listing PowerShell first and referencing Windows-specific tools and environment variable syntax. While Linux/macOS examples are present, some sections (such as role assignment and managed identity retrieval) omit direct Windows command examples, marking them as 'N/A'. Automation guidance mentions Windows Task Scheduler alongside cron, but scripting examples and automation are Linux shell-centric. This creates a subtle bias toward Windows and PowerShell, with Linux parity not fully achieved in all sections.
Recommendations
  • Provide explicit Windows command examples (e.g., using batch files or Windows CLI syntax) where currently marked 'N/A', especially for role assignment and managed identity retrieval.
  • Ensure Linux/macOS examples are given equal prominence and order as Windows/PowerShell examples, rather than listing PowerShell first.
  • Expand automation examples to include Windows batch (.bat/.cmd) and PowerShell scripts, with step-by-step instructions for scheduling via Windows Task Scheduler.
  • Reference cross-platform tools and patterns (e.g., using az CLI in both Windows and Linux environments) and avoid assuming PowerShell as the default for Windows.
  • Where environment variables are set, clarify differences and provide examples for all platforms, including Windows Command Prompt, PowerShell, and Linux shells.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/upload-logs.md ...-docs/blob/main/articles/azure-arc/data/upload-logs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Linux Parity Good
Summary
The documentation provides environment variable examples for Windows (CMD), PowerShell, and Linux/macOS, with Windows examples consistently listed first. Windows-specific tools (Task Scheduler, .cmd/.bat scripts) are mentioned alongside Linux equivalents (cron, .sh scripts), but not in a way that excludes Linux. The use of Azure CLI and kubectl is cross-platform, and Linux automation is well represented. Overall, the page demonstrates mild 'Windows-first' ordering and includes PowerShell examples, but Linux parity is strong and no major Linux omissions are present.
Recommendations
  • Alternate the order of platform examples so Linux/macOS is sometimes listed first, or present all platforms in parallel tabs without implied priority.
  • Explicitly mention that Azure CLI and kubectl commands work on all platforms at the start of relevant sections.
  • Provide more detailed Linux automation examples (e.g., sample cron job setup) to match the detail given for Windows Task Scheduler.
  • Consider grouping automation tool recommendations by platform (e.g., 'On Linux, use cron; on Windows, use Task Scheduler') for clarity.
  • Ensure parity in script examples by showing full sample scripts for both Linux (.sh) and Windows (.bat/.ps1) where possible.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/configure-driver-machine.md ...rticles/azure-arc/edge-rag/configure-driver-machine.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows, providing only a Windows-focused setup script using PowerShell and referencing Windows-specific installation paths and tools. There are no examples or instructions for Linux or cross-platform environments, and Windows tools and patterns are mentioned exclusively and first.
Recommendations
  • Add equivalent setup instructions and sample scripts for Linux (e.g., Bash shell) and macOS environments.
  • Include download and installation commands for Azure CLI, kubectl, and Helm for Linux (using apt, yum, curl, etc.) and macOS (using Homebrew, curl, etc.).
  • Present cross-platform guidance, such as using environment variables and PATH modifications in a way that applies to all major operating systems.
  • Clearly indicate which steps are OS-specific and provide parity in documentation structure and detail for Linux/macOS users.
  • Consider providing a table or section comparing Windows and Linux/macOS setup steps for clarity.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/enable-gpu-aks.md ...lob/main/articles/azure-arc/edge-rag/enable-gpu-aks.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively provides a PowerShell script for enabling GPU on AKS via Azure Arc, relying on Windows-specific tools (e.g., Get-PnpDevice, pnputil, Restart-Service). There are no Linux shell or cross-platform examples, and the workflow assumes a Windows environment throughout. Linux equivalents (such as lspci, modprobe, or driver installation via apt/yum) are not mentioned or provided.
Recommendations
  • Add equivalent Linux shell script or command-line instructions for GPU enablement and driver installation.
  • Document Linux-specific tools and patterns (e.g., lspci, nvidia-smi, modprobe) for GPU detection and configuration.
  • Clarify platform requirements and provide guidance for both Windows and Linux hosts.
  • Include notes or links to Linux documentation for Azure Arc and AKS GPU enablement.
  • Present Windows and Linux instructions side-by-side or in separate sections to ensure parity.
GitHub Create Pull Request
← Previous Page 15 of 94 Next →