Azure Compute Fleet

9
Total Pages
6
Linux-Friendly Pages
3
Pages with Bias
33.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

16 issues found
Showing 1-16 of 16 flagged pages
Azure Compute Fleet Create an Azure Compute Fleet using an ARM template ...cles/azure-compute-fleet/quickstart-create-rest-api.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: feature registration is shown only with PowerShell and Azure portal, with no Azure CLI or Linux shell example; the ARM template exclusively provisions Windows VMs (WindowsServer image, osType: Windows) with no mention of Linux alternatives; and Windows-centric tools (PowerShell) are referenced before cross-platform options. There are no Linux or Bash examples for registration, deployment, or VM configuration.
Recommendations
  • Add Azure CLI and Bash examples for resource provider registration alongside PowerShell.
  • Include ARM template snippets or guidance for deploying Linux-based fleets (e.g., Ubuntu, CentOS images, osType: Linux).
  • Ensure that cross-platform tools (Azure CLI) are presented before or alongside Windows-specific tools.
  • Provide explicit instructions or links for Linux users on how to perform prerequisite steps and clean-up operations.
  • Clarify that the ARM template can be adapted for Linux VMs and show how to do so.
GitHub Create Pull Request
Azure Compute Fleet Create an Azure Compute Fleet using Azure portal ...ticles/azure-compute-fleet/quickstart-create-portal.md
High Priority View Details →
Scanned: 2026-01-12 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 mild Windows bias. The password requirements link references Windows documentation first, and password complexity rules are described in detail, while SSH key guidance for Linux is brief and refers to a separate page. There are no concrete Linux-specific examples or screenshots, and Windows terminology (e.g., password complexity) is foregrounded over Linux SSH key usage. Linux images are mentioned, but the workflow and examples are not equally detailed for Linux users.
Recommendations
  • Provide equal detail for Linux workflows, including step-by-step SSH key generation and usage directly in the page.
  • Reference both Windows and Linux documentation for password and SSH requirements, not just Windows.
  • Include screenshots or examples showing both Windows and Linux image selection and administrator account setup.
  • Clarify parity in supported features and options for both OS types throughout the guide.
  • Avoid linking only to Windows documentation for generic requirements; link to OS-agnostic or Linux-specific resources as appropriate.
GitHub Create Pull Request
Azure Compute Fleet Create an Azure Compute Fleet using an ARM template ...cles/azure-compute-fleet/quickstart-create-rest-api.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: feature registration is shown only with PowerShell and Azure portal, with no Azure CLI or Linux shell example; the ARM template exclusively provisions Windows VMs (WindowsServer image, osType: Windows); and all command-line examples for resource management use PowerShell or Azure CLI, but Linux-specific patterns (e.g., Bash, Linux VM images) are absent. Windows tools and terminology (PowerShell, WindowsServer) are mentioned before or instead of Linux equivalents.
Recommendations
  • Add Azure CLI and Bash examples for feature registration and resource management, alongside PowerShell.
  • Provide ARM template variants or parameters for deploying Linux VMs (e.g., Ubuntu, CentOS) and document their usage.
  • Include Linux-specific instructions and screenshots for portal steps where relevant.
  • Ensure examples and templates are platform-neutral or offer both Windows and Linux options side-by-side.
  • Mention Linux VM images and osType: Linux in ARM template documentation.
GitHub Create Pull Request
Azure Compute Fleet Create an Azure Compute Fleet using Azure portal ...ticles/azure-compute-fleet/quickstart-create-portal.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 mild Windows bias. Password requirements link only to Windows VM documentation, and the password complexity rules are described before mentioning SSH keys for Linux. The example for generating SSH keys refers to Azure's automatic key generation, with only a brief link to Linux/macOS SSH key creation, but no explicit Linux command-line example is provided. Windows terminology and links are presented first or exclusively in some sections.
Recommendations
  • Provide direct links to both Windows and Linux password/SSH requirements and documentation.
  • Include explicit Linux command-line examples for generating SSH keys (e.g., 'ssh-keygen' usage) in addition to Azure portal options.
  • Ensure that Linux options (such as SSH key authentication) are described with equal detail and prominence as Windows password options.
  • Reference Linux-specific documentation (e.g., Azure Linux VM FAQ) alongside Windows documentation.
  • Where possible, present Windows and Linux options in parallel, rather than listing Windows first.
GitHub Create Pull Request
Azure Compute Fleet Create an Azure Compute Fleet using an ARM template ...cles/azure-compute-fleet/quickstart-create-rest-api.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is the only command-line example given for resource provider registration, with no Azure CLI or Bash equivalent. The ARM template exclusively provisions Windows VMs (using Windows images and osType), with no mention of Linux options or images. Windows-centric tools and patterns (PowerShell, Windows VM images) are presented first and exclusively, while Linux alternatives are missing throughout the page.
Recommendations
  • Add Azure CLI and Bash examples for resource provider registration alongside PowerShell.
  • Include ARM template examples or parameters for deploying Linux-based VMs (e.g., Ubuntu, CentOS) and document the required changes (osType, imageReference, adminUsername, etc.).
  • Explicitly mention that Compute Fleet supports both Windows and Linux VMs, and provide guidance for Linux users.
  • Ensure that documentation sections do not assume Windows as the default, and present Linux options with equal prominence.
  • Where possible, provide cross-platform instructions for all steps, including RBAC assignment and resource cleanup.
GitHub Create Pull Request
Azure Compute Fleet Create an Azure Compute Fleet using Azure portal ...ticles/azure-compute-fleet/quickstart-create-portal.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 mild Windows bias. Password requirements link to a Windows-specific FAQ, and Windows Server is mentioned before Linux images. There is no example of Linux-specific deployment steps, and the SSH key generation link is for Mac, not Linux. No Linux command-line or tool examples are provided, and Windows terminology appears first in several places.
Recommendations
  • Provide links to both Windows and Linux password/username requirements documentation.
  • Mention Linux images before or alongside Windows Server to avoid Windows-first ordering.
  • Include examples or links for generating SSH keys on Linux (e.g., using ssh-keygen).
  • Ensure parity in terminology and examples for both Windows and Linux users.
  • Reference Linux-specific documentation for VM creation and management where appropriate.
GitHub Create Pull Request
Azure Compute Fleet https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-compute-fleet/quickstart-create-rest-api.md ...cles/azure-compute-fleet/quickstart-create-rest-api.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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias in several areas. Feature registration is shown only with PowerShell and Azure portal, omitting Azure CLI or Linux shell examples. The ARM template exclusively provisions Windows VMs (Windows image, osType: Windows), with no mention of Linux alternatives. The template uses MicrosoftWindowsServer images and Windows-specific configuration. There are no Linux VM examples, nor is there guidance for Linux users in prerequisites or deployment steps. The only CLI example given (for resource cleanup) uses Azure CLI, which is cross-platform, but all other operational examples and templates are Windows-centric.
Recommendations
  • Add Azure CLI/bash examples for feature registration alongside PowerShell.
  • Provide ARM template examples for Linux VM deployment (e.g., Ubuntu, CentOS) and show how to switch osType and imageReference.
  • Include Linux-specific instructions in prerequisites and RBAC steps where relevant.
  • Order examples so that cross-platform tools (Azure CLI, bash) are presented before or alongside PowerShell.
  • Explicitly mention that the ARM template can be adapted for Linux, and link to Linux VM documentation.
GitHub Create Pull Request
Azure Compute Fleet https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-compute-fleet/quickstart-create-portal.md ...ticles/azure-compute-fleet/quickstart-create-portal.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. While it mentions that both Windows and Linux images are supported, the password requirements link points to Windows VM documentation first, and there is no explicit Linux example or parity in the password requirements section. The SSH key generation link is provided for Linux, but the overall flow and references prioritize Windows tools and documentation.
Recommendations
  • Provide direct links to Linux VM password requirements documentation alongside the Windows link.
  • Include explicit Linux-focused examples or screenshots, such as deploying a fleet with Ubuntu or RHEL images.
  • Clarify password complexity requirements for Linux VMs, noting any differences from Windows.
  • Ensure that references to documentation (e.g., password requirements) are platform-neutral or include both Windows and Linux equivalents.
  • Consider adding a section or note on using Linux-specific tools or patterns in the Azure portal, if applicable.
GitHub Create Pull Request
Azure Compute Fleet https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-compute-fleet/quickstart-create-portal.md ...ticles/azure-compute-fleet/quickstart-create-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. Password requirements link to Windows VM documentation first, and the password complexity rules are described in a Windows-centric way. The SSH key generation for Linux is mentioned, but only as an alternative, and the link provided is for Mac/Linux, not Linux specifically. No Linux-specific examples, troubleshooting, or references to Linux tools are given. The documentation does not provide parity in examples or links for Linux users compared to Windows users.
Recommendations
  • Provide direct links to Linux-specific documentation for password requirements and SSH key generation.
  • Include explicit Linux VM deployment examples or screenshots alongside Windows examples.
  • Mention Linux-specific considerations (e.g., cloud-init, SSH configuration) in the setup steps.
  • Ensure that references to administrator account setup are equally detailed for both Windows and Linux (e.g., password vs. SSH key).
  • Add troubleshooting or FAQ sections for common Linux deployment issues.
GitHub Create Pull Request
Azure Compute Fleet https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-compute-fleet/quickstart-create-rest-api.md ...cles/azure-compute-fleet/quickstart-create-rest-api.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by providing PowerShell as the only command-line example for resource provider registration, using a Windows image in the ARM template, and specifying 'osType: Windows' for VM deployment. There are no Linux/Unix shell examples, nor is there mention of Linux VM images or configuration patterns. Windows tools and workflows (PowerShell, WindowsServer image) are presented exclusively and/or before any Linux alternatives.
Recommendations
  • Add Azure CLI (bash) examples alongside PowerShell for resource provider registration and other command-line operations.
  • Include ARM template snippets or parameter options for deploying Linux-based VMs (e.g., Ubuntu, CentOS) with 'osType: Linux' and appropriate image references.
  • Ensure documentation mentions both Windows and Linux VM deployment scenarios, and provides guidance for each.
  • Present cross-platform instructions in parallel tabs or sections, with equal prominence for Linux and Windows workflows.
  • Reference Linux tools and patterns (e.g., bash, SSH, cloud-init) where relevant, not just Windows-centric approaches.
GitHub Create Pull Request
Azure Compute Fleet Create an Azure Compute Fleet using an ARM template ...cles/azure-compute-fleet/quickstart-create-rest-api.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a notable Windows bias. Feature registration is shown only via PowerShell and Azure portal, with no Azure CLI or Linux shell example. The ARM template exclusively provisions Windows VMs, with no mention of Linux images or configuration. The admin credentials are described in Windows-centric terms, and there are no Linux-specific instructions or parity examples. While the cleanup step uses Azure CLI (cross-platform), the critical steps for registration and deployment are Windows-focused.
Recommendations
  • Add Azure CLI (bash) instructions for resource provider registration alongside PowerShell and portal.
  • Include ARM template examples or parameters for deploying Linux-based VMs (e.g., Ubuntu, CentOS).
  • Clarify that admin credentials can be for Linux VMs and provide SSH key configuration examples.
  • Ensure examples and instructions are presented in a platform-neutral order, or alternate which platform is shown first.
  • Explicitly mention cross-platform compatibility for all steps, especially for automation and scripting.
GitHub Create Pull Request
Azure Compute Fleet Create an Azure Compute Fleet using an ARM template ...cles/azure-compute-fleet/quickstart-create-rest-api.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. Feature registration is shown only using PowerShell and Azure portal, with no Azure CLI or Bash example. The ARM template exclusively provisions Windows VMs (Windows image, osType: Windows), with no mention of Linux alternatives. The RBAC and resource clean-up instructions use Azure portal and Azure CLI, but the initial registration step omits CLI/Bash. Overall, Linux users are not provided with equivalent examples or guidance.
Recommendations
  • Add Azure CLI/Bash examples for feature registration alongside PowerShell.
  • Provide ARM template snippets or guidance for deploying Linux-based fleets (e.g., Ubuntu, CentOS images, osType: Linux).
  • Ensure examples and instructions are presented in a cross-platform manner, or explicitly note platform-specific steps.
  • Consider showing CLI examples before or alongside PowerShell to avoid Windows-first perception.
GitHub Create Pull Request
Azure Compute Fleet https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-compute-fleet/quickstart-create-portal.md ...ticles/azure-compute-fleet/quickstart-create-portal.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias by referencing Windows-specific documentation first (e.g., password requirements link points to the Windows VM FAQ), and by mentioning password authentication (common for Windows) before SSH keys (common for Linux). However, both Windows and Linux images are mentioned as options, and SSH key guidance is provided for Linux users.
Recommendations
  • Provide parallel links to both Windows and Linux documentation for password and username requirements.
  • Mention SSH public key authentication before password authentication, or present both options equally, to reflect Linux best practices.
  • Ensure that any referenced documentation or examples (such as password requirements) are OS-neutral or have both Windows and Linux variants.
  • Explicitly include example steps or screenshots for both Windows and Linux image deployments, if applicable.
GitHub Create Pull Request
Azure Compute Fleet Create an Azure Compute Fleet using Azure portal ...ticles/azure-compute-fleet/quickstart-create-portal.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows minor Windows bias. Password requirements link to Windows VM documentation, while the Linux SSH key section is less detailed and links to a macOS-specific page. Windows is mentioned first in several places, and Linux instructions/examples are less prominent. No command-line or OS-specific examples are provided, but references and ordering favor Windows.
Recommendations
  • Provide equal detail for Linux and Windows administrator account setup, including links to Linux password requirements and SSH key generation for both Linux and Windows.
  • Reference both Windows and Linux documentation for password requirements, not just Windows.
  • When mentioning OS images, alternate or balance the order (e.g., 'Linux or Windows Server image').
  • Link to SSH key generation guides for Linux (not just macOS), and clarify that SSH keys are supported for both Linux and Windows (if applicable).
  • Ensure examples and references are OS-neutral or provide parallel instructions for both platforms.
GitHub Create Pull Request
Azure Compute Fleet Create an Azure Compute Fleet using Azure portal ...ticles/azure-compute-fleet/quickstart-create-portal.md
Low Priority View Details →
Scanned: 2026-01-13 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 mild Windows bias. Password requirements link to Windows VM documentation first, and the password complexity rules are described before mentioning SSH keys for Linux. The SSH key generation link is platform-neutral, but the example focuses on Azure-generated keys rather than showing Linux/macOS command-line steps. No explicit Linux/macOS examples or references to Linux-specific tools are provided, and Windows terminology (password requirements) is presented before Linux alternatives.
Recommendations
  • Provide explicit Linux/macOS examples for SSH key generation (e.g., using ssh-keygen on Linux/macOS).
  • Link to both Windows and Linux password/SSH documentation equally, or use a platform-neutral reference.
  • Mention Linux/macOS admin account setup before or alongside Windows password requirements.
  • Clarify that both Windows and Linux images are supported, and provide example screenshots or steps for each where relevant.
GitHub Create Pull Request
Azure Compute Fleet https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-compute-fleet/modify-fleet.md ...blob/main/articles/azure-compute-fleet/modify-fleet.md
Low Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively describes how to modify a Compute Fleet using the Azure portal UI, without providing any command-line examples or automation guidance. There are no references to Windows-specific tools, but there is also a lack of parity for Linux users: no CLI (Azure CLI, Bash) or PowerShell instructions are given, which may disadvantage users who prefer or require command-line or scriptable solutions, especially on Linux.
Recommendations
  • Add step-by-step instructions for modifying Compute Fleets using the Azure CLI, including example commands for both target capacity and VM size changes.
  • Include Bash script examples for automating common modification tasks.
  • If relevant, provide PowerShell examples as well, but ensure they are presented alongside (not before) Linux-friendly CLI/Bash examples.
  • Clearly indicate which methods are cross-platform and highlight any differences in behavior or prerequisites between Windows and Linux environments.
GitHub Create Pull Request