Cyclecloud

179
Total Pages
160
Linux-Friendly Pages
19
Pages with Bias
10.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

86 issues found
Showing 1-25 of 86 flagged pages
Cyclecloud Microsoft HPC Pack Integration ...cs/azure-docs/blob/main/articles/cyclecloud/hpcpack.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric, focusing exclusively on Microsoft HPC Pack clusters with Windows Server technologies. All examples, prerequisites, and tooling (e.g., azhpcpack.ps1 CLI, Windows Scheduled Task) are Windows-specific. Linux compute nodes are explicitly not supported, and there are no Linux/macOS equivalents or examples provided. Windows tools and patterns (Active Directory, PFX certificates, PowerShell scripts) are mentioned exclusively, with no mention of Linux alternatives.
Recommendations
  • Clearly state Linux/macOS limitations at the top of the documentation.
  • Provide guidance or links for Linux-based HPC alternatives (e.g., SLURM, PBS, or CycleCloud's Linux support).
  • Add a roadmap or reference for future Linux support if planned.
  • Where possible, mention cross-platform tools or clarify which steps are Windows-only.
  • If Linux support is planned, prepare parity documentation and examples for Linux environments.
GitHub Create Pull Request
Cyclecloud Microsoft HPC Pack Integration ...cs/azure-docs/blob/main/articles/cyclecloud/hpcpack.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric, with exclusive references to Windows Server technologies, Active Directory, and Windows-only tools (e.g., azhpcpack.ps1 PowerShell CLI). Linux compute nodes are explicitly not supported, and all configuration and operational examples are tailored for Windows environments. There are no Linux/macOS equivalents or guidance, and critical tasks (cluster creation, autoscaling, credential management) rely on Windows-specific patterns and tools.
Recommendations
  • Explicitly state Linux/macOS limitations and expected roadmap for support.
  • Provide alternative guidance or links for Linux-based HPC solutions in Azure CycleCloud.
  • If/when Linux support is added, ensure parity in examples, CLI tooling, and configuration instructions.
  • Mention any cross-platform tools or APIs (if available) for cluster management.
  • Add a section comparing Windows and Linux HPC options in CycleCloud for user clarity.
GitHub Create Pull Request
Cyclecloud Microsoft HPC Pack Integration ...cs/azure-docs/blob/main/articles/cyclecloud/hpcpack.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric, focusing exclusively on Microsoft HPC Pack, which only supports Windows nodes. All examples, prerequisites, and tooling (such as azhpcpack.ps1 CLI) are Windows-specific, with no mention of Linux equivalents, Linux node support, or cross-platform patterns. Windows technologies (Active Directory, Windows Scheduled Task, PowerShell scripts) are referenced throughout, and Linux support is explicitly stated as not available.
Recommendations
  • Add information about Linux support roadmap and alternatives for Linux clusters.
  • Provide parity documentation for CycleCloud integration with Linux-based schedulers (e.g., Slurm, PBS, Grid Engine).
  • Include Linux CLI and automation examples where possible, or clarify cross-platform limitations.
  • Mention Linux equivalents for concepts like autoscaling, node management, and credential handling.
  • Clearly state at the top that the documentation is Windows-only, and link to Linux documentation for similar workflows.
GitHub Create Pull Request
Cyclecloud Cluster Template Reference - Nodes ...lecloud/cluster-references/node-nodearray-reference.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific features (such as Hybrid Benefit licensing and Secure Boot/TPM options) are described in detail, and Windows is often mentioned first in lists of supported platforms or licensing options. While Linux images and attributes are present, there are no explicit Linux-specific examples or guidance (e.g., for SSH key management, Linux-specific VM configuration, or Jetpack installation nuances). Windows licensing and features are described more thoroughly than Linux equivalents, and there are no PowerShell-heavy examples, but Windows-centric attributes (e.g., HybridBenefit, HybridBenefitLicense defaulting to Windows_Server) are prominent.
Recommendations
  • Add explicit Linux-focused examples, such as SSH key management, Linux VM configuration, and Jetpack installation for Linux images.
  • Ensure Linux licensing options (e.g., RHEL_BYOS, SLES_BYOS) are described as thoroughly as Windows options.
  • Present Linux and Windows features in parallel, rather than listing Windows first or in more detail.
  • Include notes or examples for Linux-specific security features and VM attributes where applicable.
  • Where attributes default to Windows (e.g., HybridBenefitLicense), clarify Linux alternatives and provide usage scenarios.
GitHub Create Pull Request
Cyclecloud Connecting to a Cluster Node ...lob/main/articles/cyclecloud/how-to/connect-to-node.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides detailed instructions for connecting to cluster nodes, but there is a noticeable Windows bias. Windows tools and workflows (RDP, Microsoft RDP client) are mentioned explicitly and with more detail, while Linux-specific examples (such as using SSH for graphical applications or alternative Linux RDP clients) are missing. The documentation also describes Windows connection methods (RDP tunnel) before offering Linux alternatives, and does not provide parity for Linux desktop access or mention Linux-specific tools for remote desktop connections.
Recommendations
  • Add explicit Linux examples for connecting to graphical desktops (e.g., using X11 forwarding or Linux RDP clients like Remmina or xfreerdp).
  • Mention Linux tools and workflows for remote desktop access alongside Windows RDP instructions.
  • Ensure that instructions for connecting to services (such as databases or desktops) include Linux-specific command examples and tool recommendations.
  • Present Windows and Linux connection methods in parallel, rather than focusing on Windows first.
  • Clarify that SSH tunneling and agent forwarding are cross-platform, and provide troubleshooting tips for Linux users.
GitHub Create Pull Request
Cyclecloud Install the Command Line Interface ...n/articles/cyclecloud/how-to/install-cyclecloud-cli.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows installation instructions, but Windows-specific details (such as PowerShell scripts and GUI extraction steps) are described in greater detail and with more emphasis on Windows tools and patterns. The Windows installation section mentions PowerShell and Windows Explorer, while the Linux section uses standard shell commands. The prerequisites section gives explicit instructions for installing Python on Windows, while assuming Linux/Mac users already have Python. The order of presentation puts Linux instructions before Windows, but the Windows section is more verbose and tool-specific.
Recommendations
  • Provide equivalent command-line instructions for Windows users (e.g., using PowerShell to unzip and run the installer, rather than relying on GUI steps).
  • Mention Linux tools (such as unzip) and their installation if not present, similar to how Python installation is mentioned for Windows.
  • Ensure parity in detail and clarity between Linux and Windows sections, avoiding assumptions about user familiarity.
  • Include Mac-specific instructions if supported, or clarify platform support.
  • List prerequisites for all platforms equally, including links to Python installation for Linux/Mac if needed.
GitHub Create Pull Request
Cyclecloud Volume Mount ...ocs/blob/main/articles/cyclecloud/how-to/mount-disk.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits subtle Windows bias by referencing Azure-specific device assignment via Logical Unit Numbers (LUN) and linking to PowerShell modules, while omitting explicit Linux device assignment examples. Windows/Azure tooling and terminology are mentioned first and exclusively in device assignment contexts, and there are no Linux-specific commands or examples for mounting, formatting, or device management. Linux concepts (LVM, ext4/xfs filesystems) are mentioned, but only as configuration parameters, not as actionable examples.
Recommendations
  • Add explicit Linux device assignment examples (e.g., using /dev/sdX, lsblk, or Linux mount commands) alongside Azure LUN references.
  • Provide Linux CLI commands for formatting, mounting, and managing volumes (e.g., mkfs, mount, cryptsetup, mdadm for RAID).
  • Include references to Linux documentation or man pages for relevant tools (e.g., LVM, RAID, encryption).
  • Clarify cross-platform differences in device naming and management, and ensure Linux patterns are described with equal detail and prominence.
  • Avoid linking only to PowerShell modules; include links to Linux equivalents or general Azure CLI documentation.
GitHub Create Pull Request
Cyclecloud Projects ...-docs/blob/main/articles/cyclecloud/how-to/projects.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for Azure CycleCloud projects demonstrates a Windows bias in several ways. It references PowerShell scripts as a primary supported script type, mentions log file locations using Windows-style environment variables (e.g., $JETPACK_HOME), and refers to configuration files in home directories using Windows-style notation (e.g., ~/.cycle/config.ini). While shell scripts are mentioned, there are no explicit Linux/Bash examples, and the documentation does not provide Linux-specific usage patterns or file paths before or alongside Windows equivalents. Windows tools and conventions are referenced first or exclusively, with little attention to Linux parity.
Recommendations
  • Provide explicit Bash/Linux shell script examples alongside PowerShell examples.
  • Include Linux-specific file paths and environment variable usage (e.g., $HOME, /var/log) in addition to Windows-style paths.
  • Clarify that both Linux and Windows nodes are supported, and note any differences in script execution or file locations.
  • Mention Linux tools and patterns (such as chmod, systemd, etc.) where relevant, and provide cross-platform guidance.
  • Ensure that CLI commands and configuration instructions are platform-neutral or have both Windows and Linux variants.
GitHub Create Pull Request
Cyclecloud User Authentication ...main/articles/cyclecloud/how-to/user-authentication.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by prioritizing Active Directory (a Windows-centric technology) in both order and detail, providing examples and screenshots tailored to Windows environments (e.g., DOMAIN\user format, AD server naming). There is no mention of Linux-native authentication tools or integration patterns, and no Linux-specific examples (such as OpenLDAP configuration or Linux user management commands). The Entra ID section references Linux clusters but only in the context of SSH keys, without providing parity in authentication setup examples for Linux environments.
Recommendations
  • Add Linux-specific authentication examples, such as configuring OpenLDAP or integrating with Linux PAM modules.
  • Provide sample configurations and screenshots for Linux environments (e.g., using 'uid' and 'gid', Linux user formats, OpenLDAP server URLs).
  • Include instructions for managing authentication via Linux command line tools (e.g., ldapsearch, useradd) alongside GUI steps.
  • Reorder sections or provide parallel examples for both Windows and Linux environments to avoid implicit prioritization.
  • Explicitly mention Linux equivalents when discussing Windows-centric technologies (e.g., contrast Active Directory with OpenLDAP).
GitHub Create Pull Request
Cyclecloud Jetpack Reference ...cs/azure-docs/blob/main/articles/cyclecloud/jetpack.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias: Windows paths and behaviors are often listed before Linux equivalents, and some features (like 'run_on_shutdown') are described as unsupported for Windows but lack Linux-specific usage examples. Windows tools and conventions (e.g., directory paths, environment variables) are mentioned explicitly, sometimes before Linux ones. There are no PowerShell-specific examples, but Linux-specific scripting and integration patterns are underrepresented.
Recommendations
  • Present Linux and Windows paths and behaviors in parallel, or alternate which platform is listed first.
  • Add explicit Linux usage examples for features that differ between platforms (e.g., show a sample bash script for 'run_on_shutdown').
  • Clarify Linux-specific requirements or behaviors, such as permissions, init system integration, or udev rules.
  • Include Linux shell command examples where appropriate, not just generic 'console' blocks.
  • Note any platform-specific limitations or enhancements for Linux, not just for Windows.
GitHub Create Pull Request
Cyclecloud Release Notes v8.5.0 ...s/blob/main/articles/cyclecloud/release-notes/8-5-0.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing Windows Server support and HPC Pack (a Windows-centric tool) as prominent new features, while Linux equivalents are mentioned later or not at all. There are no Linux-specific examples or tools highlighted, and Windows features are described in more detail or with more emphasis than Linux ones.
Recommendations
  • Add explicit mention of supported Linux distributions and versions alongside Windows Server in the 'New Features' section.
  • Highlight Linux-based HPC tools (e.g., OpenHPC, Warewulf) if supported, similar to how HPC Pack is mentioned.
  • Provide examples or links for both Windows and Linux cluster node setup, configuration, and health checks.
  • Ensure that Linux features (e.g., Ubuntu 22 support for Slurm) are given equal prominence and detail as Windows features.
  • Include troubleshooting steps or resolved issues that are specific to Linux environments, not just generic or Windows-centric problems.
GitHub Create Pull Request
Cyclecloud Cluster Template Reference - Nodes ...lecloud/cluster-references/node-nodearray-reference.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific features (such as Hybrid Benefit licensing and Secure Boot) are described in detail, and Windows is mentioned first or exclusively in some contexts (e.g., HybridBenefit defaults to Windows_Server). There are references to Windows images and licensing, but Linux equivalents are not always given equal prominence. Some examples and attributes (e.g., KeyPairLocation) use Linux-style paths, but there are no explicit Linux-specific examples or notes about Linux-only features, except for Jetpack installation. Powershell or Windows command-line examples are not present, but Windows features are described before or in more detail than Linux ones in some cases.
Recommendations
  • Provide explicit Linux examples and notes where Windows features are described, such as Linux equivalents for licensing, security, and image attributes.
  • Ensure parity in attribute descriptions: when mentioning Windows-specific features (e.g., HybridBenefit), also describe Linux-specific options (e.g., RHEL_BYOS, SLES_BYOS) with equal detail.
  • Add Linux-focused sample templates and highlight Linux-specific configuration options, such as SSH key management, OS extension support, and Jetpack installation.
  • Where Windows is mentioned first or as the default, consider reordering or balancing the presentation to avoid implicit prioritization.
  • Include references to Linux tools and patterns where relevant, such as cloud-init, Linux security features, and package management.
GitHub Create Pull Request
Cyclecloud Connecting to a Cluster Node ...lob/main/articles/cyclecloud/how-to/connect-to-node.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides examples for connecting to both Linux and Windows nodes, but Windows-specific tools and workflows (RDP, Microsoft RDP client) are mentioned explicitly and in detail, while Linux equivalents (e.g., X11 forwarding, Linux-native remote desktop options) are not discussed. Windows connection methods (RDP) are described with more tooling support (auto-launching clients), and Linux connection examples are limited to SSH without further guidance for graphical sessions. There is a lack of parity in remote desktop instructions for Linux users.
Recommendations
  • Add examples for connecting to Linux nodes using graphical remote desktop solutions (e.g., X11 forwarding, VNC, or xrdp) alongside the RDP instructions for Windows.
  • Mention Linux-native remote desktop clients (e.g., Remmina, KRDC) in addition to Microsoft RDP client.
  • Provide parity in tunnel setup instructions for Linux graphical sessions (e.g., SSH -X for X11 forwarding, or port forwarding for VNC/xrdp).
  • Ensure that Linux connection methods are described with equal detail and tooling support as Windows methods.
  • When describing connection strings and CLI usage, clarify differences and provide explicit Linux and Windows examples side-by-side.
GitHub Create Pull Request
Cyclecloud Install the Command Line Interface ...n/articles/cyclecloud/how-to/install-cyclecloud-cli.md
High 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 installation instructions for both Linux and Windows, but Windows-specific details (such as PowerShell scripts and Windows Explorer usage) are given equal prominence to Linux instructions. The prerequisites section mentions Windows Python installation separately, and the Windows installation relies on PowerShell and GUI actions, while the Linux section uses standard shell commands. There is a slight 'windows_first' bias in the prerequisites and installer download instructions, and Windows tools (PowerShell, Explorer) are referenced without Linux equivalents being explained in the same detail.
Recommendations
  • Ensure Linux and Windows instructions are presented with equal detail and clarity.
  • Provide command-line alternatives for Windows installation (e.g., using PowerShell or Command Prompt to unzip and run scripts), similar to the Linux shell instructions.
  • Mention Linux file managers or CLI tools where Windows Explorer is referenced.
  • Include explicit instructions for adding the CLI to PATH on Windows, as is done for Linux.
  • Consider listing Linux instructions before Windows, or interleaving them, to avoid implicit prioritization.
GitHub Create Pull Request
Cyclecloud Volume Mount ...ocs/blob/main/articles/cyclecloud/how-to/mount-disk.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows/Azure bias by referencing Azure-specific tooling and concepts (such as Logical Unit Numbers (LUN) and Disk Encryption Sets) without providing equivalent Linux or cross-cloud examples. The mention of device assignment refers to Azure and links to Powershell modules, with no mention of Linux device naming conventions or tools (e.g., /dev/sdX, udev, or Linux CLI utilities). There are no examples showing how to mount or format volumes using Linux commands or configuration files outside of the CycleCloud INI syntax. The documentation assumes Azure as the platform and omits guidance for Linux-specific workflows, tools, or alternative platforms.
Recommendations
  • Add Linux-specific examples for device assignment, such as referencing /dev/sdX naming, udev rules, or using lsblk/fdisk.
  • Include links to Linux documentation or man pages for mounting and formatting disks (e.g., mount, mkfs, parted).
  • Provide parity in examples by showing how to perform similar operations on Linux systems outside of Azure, or at least clarify Azure-specific steps versus general Linux steps.
  • Mention Linux tools (e.g., LVM, mdadm for RAID, cryptsetup for encryption) alongside Azure-specific features.
  • Clarify when instructions are Azure-specific and offer alternatives or notes for users on other platforms.
GitHub Create Pull Request
Cyclecloud Microsoft HPC Pack Integration ...cs/azure-docs/blob/main/articles/cyclecloud/hpcpack.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation for Microsoft HPC Pack integration in Azure CycleCloud exhibits significant Windows bias. All examples, tools, and configuration steps are centered around Windows technologies (Active Directory, Windows Server, PowerShell scripts, Windows Scheduled Tasks, and Windows-specific CLI tools). Linux compute nodes are explicitly not supported, and there are no Linux equivalents or examples provided. Windows patterns and tools are mentioned exclusively and first throughout the page.
Recommendations
  • Add information about Linux support and roadmap, if available, or clarify limitations and alternatives for Linux users.
  • Provide Linux-specific examples, tools, or configuration steps where possible, or reference equivalent Linux HPC solutions.
  • Include notes or cross-references to CycleCloud documentation for Linux clusters to help users find relevant information.
  • If CLI tools or scripts are Windows-only, suggest or develop cross-platform alternatives, or clarify their platform limitations.
  • Document any planned or experimental support for Linux compute nodes, and invite feedback from Linux users.
GitHub Create Pull Request
Cyclecloud User Authentication ...main/articles/cyclecloud/how-to/user-authentication.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Active Directory (a Windows-centric technology) in both order and detail, providing examples and terminology specific to Windows (e.g., DOMAIN\user), and referencing Windows authentication patterns and tools. There is no mention of Linux-specific authentication methods (such as FreeIPA or OpenLDAP), nor are there examples tailored for Linux environments. While LDAP is mentioned, it is not contextualized for Linux use cases, and no Linux command-line or configuration examples are provided.
Recommendations
  • Provide Linux-centric authentication examples, such as integration with OpenLDAP or FreeIPA, including sample configurations and command-line instructions.
  • Include Linux username formats and authentication patterns alongside Windows examples (e.g., uid=user,ou=people,dc=example,dc=com).
  • Offer parity in troubleshooting steps for Linux environments, such as using SSH or Linux utilities to verify authentication.
  • Reference Linux tools and workflows (e.g., PAM, sssd, nslcd) where relevant, and clarify cross-platform differences in authentication setup.
  • Reorder sections or provide parallel examples so that Linux and Windows approaches are equally represented and accessible.
GitHub Create Pull Request
Cyclecloud Jetpack Reference ...cs/azure-docs/blob/main/articles/cyclecloud/jetpack.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation generally presents Windows and Linux paths and behaviors in parallel, but there are signs of Windows bias: Windows paths are listed before Linux in several places, Windows-specific behaviors (such as the 'forever' option for HealthCheck) are called out, and some references (e.g., Azure metadata link) point to Windows-specific documentation. There are no explicit Linux/Powershell command examples, but some commands (like 'run_on_shutdown') are noted as unsupported on Windows, which is helpful for parity. However, Linux-specific details (such as init system integration or udev rules) are mentioned only briefly and without examples.
Recommendations
  • List Linux paths and behaviors before or alongside Windows equivalents to avoid Windows-first ordering.
  • Provide explicit Linux command examples (e.g., systemd integration, udev rule details, bash script samples) where relevant.
  • Link to both Windows and Linux versions of Azure documentation (e.g., metadata service).
  • Expand on Linux-specific features (such as init scripts, udev rules, and shell integration) with concrete examples.
  • Clarify any differences in command behavior or support between platforms with side-by-side tables or notes.
GitHub Create Pull Request
Cyclecloud https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/download-cluster-templates.md ...main/articles/cyclecloud/download-cluster-templates.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 shows evidence of Windows bias by referencing Microsoft HPC Pack (a Windows-only job scheduler) prominently, linking to a PowerShell-based overview for HPC Pack, and omitting Linux-specific instructions or examples. There are no explicit Linux CLI or shell examples, and Windows tools are mentioned before their Linux equivalents in the template table.
Recommendations
  • Include Linux shell (bash) examples for importing templates, alongside or before Azure CLI examples.
  • Provide links to Linux documentation or man pages for each scheduler (e.g., Slurm, HTCondor, OpenPBS) in the template table.
  • Balance the presentation of Windows and Linux tools by listing Linux-native schedulers (Slurm, HTCondor, OpenPBS) before Windows-only options like HPC Pack.
  • Add a section highlighting Linux compatibility and usage patterns for CycleCloud templates.
GitHub Create Pull Request
Cyclecloud https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/cluster-references/node-nodearray-reference.md ...lecloud/cluster-references/node-nodearray-reference.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 demonstrates a mild Windows bias. Windows-specific features (such as Hybrid Benefit licensing and Secure Boot/TPM options) are described in detail, and Windows is mentioned first or exclusively in several places (e.g., HybridBenefit defaults to Windows_Server). There are no explicit Linux-specific examples or instructions, and some attributes (like KeyPairLocation) are ambiguous about Linux/Windows differences. The documentation does mention Linux images and Jetpack installation, but does not provide parity in terms of Linux-specific configuration, troubleshooting, or examples.
Recommendations
  • Add explicit Linux configuration examples, such as specifying SSH keys, user data, or cloud-init for Linux nodes.
  • Provide Linux-first or Linux-equivalent instructions for attributes that differ between Windows and Linux (e.g., KeyPairLocation, Jetpack installation).
  • Include troubleshooting or best practices for Linux nodes, such as handling SSH connectivity, file permissions, or OS extension installation.
  • Ensure that Windows-specific features (like HybridBenefit, Secure Boot, TPM) are clearly marked as Windows-only, and provide Linux alternatives or note their irrelevance for Linux.
  • Balance the order of presentation so that Linux and Windows options are given equal prominence, or alternate which is mentioned first.
GitHub Create Pull Request
Cyclecloud https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/connect-to-node.md ...lob/main/articles/cyclecloud/how-to/connect-to-node.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 provides both SSH (Linux) and RDP (Windows) connection methods, but Windows-specific tools and patterns (RDP, Microsoft RDP client) are mentioned explicitly and with more detail. Several examples focus on connecting to Windows nodes (RDP tunnel setup, automatic RDP client launch), while equivalent Linux GUI access (e.g., X11 forwarding) is not discussed. There is no example for connecting to a Linux desktop environment, and Windows connection methods are described before Linux alternatives in some sections.
Recommendations
  • Add examples for connecting to Linux nodes with graphical interfaces (e.g., X11 forwarding, VNC tunnels) to match the RDP tunnel example for Windows.
  • Provide parity in tool recommendations, such as mentioning open-source RDP clients for Linux and macOS, or alternatives to Microsoft RDP client.
  • Ensure Linux connection methods (SSH, agent forwarding) are described with equal detail and appear before or alongside Windows methods.
  • Include troubleshooting tips and security notes for Linux users, such as handling SSH keys, agent forwarding, and firewall settings.
  • Clarify that the CycleCloud CLI and Connect button work equally for both Linux and Windows nodes, and provide explicit Linux-centric usage scenarios.
GitHub Create Pull Request
Cyclecloud https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/mount-disk.md ...ocs/blob/main/articles/cyclecloud/how-to/mount-disk.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 demonstrates a Windows/Azure bias by referencing Azure-specific concepts and tools (such as Logical Unit Numbers and Disk Encryption Sets) without providing equivalent Linux or cross-cloud examples. The only device assignment example links to a PowerShell module, and Azure portal instructions are given without CLI or Linux alternatives. There are no explicit Linux command-line examples (e.g., mount, mkfs, lvm), and Linux-specific configuration options are mentioned only in passing, after Azure/Windows-centric instructions.
Recommendations
  • Provide Linux CLI examples for mounting and formatting volumes (e.g., using mount, mkfs, parted, or LVM commands).
  • Include instructions for device assignment and disk encryption using Linux tools (e.g., udev rules, cryptsetup, LVM).
  • Reference cross-platform or Linux-native documentation and tools alongside Azure/Windows-specific ones.
  • Present Linux examples and options before or alongside Windows/Azure examples to ensure parity.
  • Clarify which configuration options are platform-specific and provide guidance for both Windows and Linux users.
GitHub Create Pull Request
Cyclecloud https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/install-cyclecloud-cli.md ...n/articles/cyclecloud/how-to/install-cyclecloud-cli.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 installation instructions for both Linux and Windows, but Windows-specific details (such as PowerShell scripts and Windows Explorer usage) are given equal or greater prominence. The prerequisites section mentions installing Python for Windows explicitly, while Linux and Mac are assumed to have Python. Windows installation relies on graphical tools and PowerShell scripts, with no mention of Linux equivalents (e.g., shell scripts for automation). The order of presentation sometimes favors Windows, and Windows tools (PowerShell, Explorer) are described in detail.
Recommendations
  • Provide equivalent shell script automation examples for Linux, similar to the PowerShell script for Windows.
  • Include command-line extraction instructions for Windows (e.g., using 'tar' or 'Expand-Archive' in PowerShell) to match the Linux unzip example.
  • Mention how to add the CLI to PATH on Windows via command line, not just via system settings.
  • Ensure Linux instructions are presented first or in parallel with Windows instructions to avoid perceived prioritization.
  • Clarify that both platforms require Python and provide installation links for Linux and Mac as well as Windows.
GitHub Create Pull Request
Cyclecloud https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/projects.md ...-docs/blob/main/articles/cyclecloud/how-to/projects.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 a Windows bias by referencing PowerShell scripts as a primary example of spec types, mentioning Windows file paths and environment variables, and not providing equivalent Linux shell script examples or Linux-specific usage patterns. Windows-centric terminology and tools are mentioned before Linux equivalents, and there is a lack of explicit Linux command-line examples or discussion of Linux-specific file locations and permissions.
Recommendations
  • Include explicit Linux shell script examples alongside PowerShell examples when describing spec scripts.
  • Provide Linux-specific file paths and environment variable usage where relevant, such as /var/log or /etc.
  • Mention Linux tools (e.g., bash, sh) and patterns before or alongside Windows tools.
  • Add examples of using the CycleCloud CLI and jetpack commands in a Linux environment, including permissions and file system considerations.
  • Clarify cross-platform compatibility for all commands and scripts, and note any differences in behavior between Windows and Linux nodes.
GitHub Create Pull Request
Cyclecloud https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/user-authentication.md ...main/articles/cyclecloud/how-to/user-authentication.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 demonstrates a Windows bias by prioritizing Active Directory (a Windows-centric authentication method) and providing examples specifically for Windows users (e.g., DOMAIN\user format). There is no mention of Linux-specific authentication patterns (such as sAMAccountName vs. UPN for Linux clients), nor are there examples or instructions tailored to Linux environments (e.g., Kerberos, PAM integration, or Linux CLI tools). The Entra ID section briefly mentions Linux clusters and SSH keys, but lacks detailed Linux configuration steps or parity in example depth compared to Windows/AD. No PowerShell commands are present, but Windows terminology and workflows are foregrounded.
Recommendations
  • Add explicit Linux authentication examples, such as using sAMAccountName or UPN formats in Linux tools (e.g., ldapsearch, kinit).
  • Include instructions for configuring LDAP/AD integration with Linux clients, referencing common Linux authentication stacks (SSSD, PAM, Kerberos).
  • Provide CLI-based configuration steps for Linux environments, not just GUI workflows.
  • Clarify differences in authentication workflows between Windows and Linux clients, especially for AD and Entra ID scenarios.
  • Balance examples and screenshots to include Linux tools and environments alongside Windows-centric ones.
GitHub Create Pull Request
← Previous Page 1 of 4 Next →