Virtual Machine Scale Sets

186
Total Pages
138
Linux-Friendly Pages
48
Pages with Bias
25.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

143 issues found
Showing 126-143 of 143 flagged pages
Virtual Machine Scale Sets Azure Virtual Machine Scale Sets Attached Data Disks ...cale-sets/virtual-machine-scale-sets-attached-disks.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Windows and Linux examples for preparing data disks in scale sets, but the Windows (PowerShell) example is presented first and uses a named script (prepare_vm_disks.ps1) with explicit PowerShell invocation. The Linux example follows, using bash. The initial tutorial links list Azure CLI before PowerShell, but the main example section gives Windows precedence. There is a slight bias toward Windows/PowerShell in ordering and example prominence.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them side-by-side for parity.
  • Explicitly state that both Windows and Linux are supported before showing examples.
  • Provide equal detail and context for both PowerShell and Bash scripts (e.g., describe what each script does).
  • Where possible, use cross-platform tools (e.g., Azure CLI) as the primary example, with OS-specific instructions as secondary.
  • Add a note that Linux/macOS users can use Azure CLI and Bash for all operations, and link to relevant tutorials.
GitHub Create Pull Request
Virtual Machine Scale Sets Encrypt disks for Azure scale sets with Azure CLI ...cles/virtual-machine-scale-sets/disk-encryption-cli.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Heavy Minor Linux Example
Summary
The documentation page is titled and described as targeting Windows Virtual Machine Scale Sets, and the introductory context is Windows-centric. However, the main Azure CLI examples use Linux images and Linux tooling (Custom Script Extension with a shell script), and there is a link to a Linux batch file example at the end. The page does not provide explicit Windows-specific CLI commands or PowerShell examples, but the framing and references are Windows-first, with Linux support present but less emphasized.
Recommendations
  • Update the title and description to clarify that both Windows and Linux VMSS are supported, or provide separate sections/examples for each.
  • Add explicit Windows VMSS examples (e.g., using Windows images, Windows Custom Script Extension, and PowerShell commands) alongside the Linux examples.
  • Present Linux and Windows examples in parallel, or clearly indicate which steps apply to which OS.
  • Ensure that references to OS support (such as the ADE supported OS link) are accompanied by guidance for both platforms.
  • Move or duplicate the Linux batch file example to a more prominent location, not just in 'Next steps'.
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Low 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. Windows-specific scenarios (such as VM activation and Windows updates) are mentioned before Linux equivalents, and troubleshooting links are provided only for Windows. There are no explicit Linux-focused migration examples or references to Linux-specific tools or package managers. Azure PowerShell is listed as a primary tool alongside Azure CLI, but Linux-specific command-line patterns are not highlighted. The only CLI example uses Azure CLI, which is cross-platform, but the overall narrative and troubleshooting guidance favor Windows environments.
Recommendations
  • Add explicit Linux migration scenarios and troubleshooting links (e.g., for Linux VM activation or common Linux update issues).
  • Provide examples of Linux package manager outbound connectivity requirements (e.g., apt, yum, zypper) and link to relevant documentation.
  • Ensure parity in listing tools: mention Bash scripting and Linux-native automation tools alongside PowerShell.
  • Where Windows-specific requirements are listed (e.g., activation, updates), provide Linux equivalents in parallel.
  • Consider reordering sections so that Windows and Linux requirements are presented together, or alternate which is listed first.
GitHub Create Pull Request
Virtual Machine Scale Sets Create virtual machines in a Flexible scale set using Azure portal ...ale-sets/flexible-virtual-machine-scale-sets-portal.md
Low 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. Password requirements link to a Windows-specific FAQ, and Windows terminology (e.g., 'Password' complexity) is described before Linux SSH key options. The password requirements reference a Windows documentation page, while the SSH key generation link is Linux/macOS-specific but less prominent. No explicit Linux command-line examples or Linux-specific troubleshooting are provided, and Windows is mentioned first when discussing OS image choices.
Recommendations
  • Provide equal prominence to Linux and Windows options when describing administrator account setup, including direct links to both Linux and Windows documentation for password/SSH requirements.
  • When referencing password requirements, link to a cross-platform or Linux-specific page if available, or clarify that requirements apply to both OS types.
  • Mention Linux images first or alternate the order to avoid Windows-first bias.
  • Include a brief note or link about Linux-specific considerations (e.g., SSH key management, cloud-init usage) in the portal workflow.
  • Ensure that screenshots and examples reflect both Windows and Linux scenarios where relevant.
GitHub Create Pull Request
Virtual Machine Scale Sets Update a Virtual Machine Scale Set with instance mix ...cles/virtual-machine-scale-sets/instance-mix-update.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for updating VMSS instance mix settings, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and is presented before REST API examples. There are no explicit Linux/macOS-specific examples or notes, and PowerShell code is detailed and assumes familiarity with Windows tooling. However, Azure CLI is cross-platform and all critical tasks can be completed with CLI or REST API, so Linux/macOS users are not blocked.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows.
  • Add a note clarifying that PowerShell examples are primarily for Windows users, while CLI is recommended for Linux/macOS.
  • Consider presenting Azure CLI examples before PowerShell, or grouping them together with a note on platform compatibility.
  • If relevant, mention installation or usage differences for CLI on Linux/macOS.
  • Add troubleshooting or FAQ notes for Linux/macOS users if any issues are known.
GitHub Create Pull Request
Virtual Machine Scale Sets Get high availability and cost savings with Spot Priority Mix for Virtual Machine Scale Sets ...ticles/virtual-machine-scale-sets/spot-priority-mix.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Azure CLI and Azure PowerShell examples in parallel, but PowerShell is shown as a first-class method throughout, and no explicit Linux/macOS shell (e.g., Bash) examples are provided. The CLI examples use generic syntax compatible with Linux/macOS, but PowerShell is given equal prominence, which may imply a Windows-centric approach. There are no references to Linux-specific tools or workflows, and the portal instructions are platform-neutral.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide sample Bash shell usage (e.g., with environment variables or piping).
  • Add a note clarifying that PowerShell examples are for Windows and Azure PowerShell Core is available cross-platform, if relevant.
  • Consider including a Bash script example for scale set creation and update to demonstrate parity.
  • If there are any platform-specific caveats (e.g., CLI installation, authentication), link to Linux/macOS instructions.
  • Ensure that CLI examples are shown before PowerShell, or clarify that both are supported equally across platforms.
GitHub Create Pull Request
Virtual Machine Scale Sets Understand the health state of your standby pool ...rtual-machine-scale-sets/standby-pools-health-state.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure CLI, PowerShell, and REST API. The PowerShell example is given equal prominence to the CLI example, but PowerShell is a Windows-centric tool. There is no explicit mention of Linux/macOS-specific shell usage (e.g., Bash), nor are there examples showing how to use the REST API with Linux-native tools like curl or httpie. The CLI example is cross-platform, but the ordering and inclusion of PowerShell may suggest a slight Windows bias.
Recommendations
  • Add explicit Bash/Linux/macOS shell examples for REST API usage (e.g., using curl or httpie).
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS as well as Windows.
  • Consider including Bash scripting examples for automation on Linux/macOS.
  • If PowerShell is included, note that PowerShell Core is available cross-platform, or provide equivalent Bash examples.
GitHub Create Pull Request
Virtual Machine Scale Sets Get standby pool and instance details ...irtual-machine-scale-sets/standby-pools-get-details.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all major tasks, but PowerShell examples are given equal prominence as CLI, despite PowerShell being primarily a Windows tool. There is no explicit Linux shell scripting or macOS-specific guidance, and PowerShell is presented as a first-class option, which may create friction for Linux/macOS users who typically use Bash or other shells. However, the Azure CLI and REST API examples are cross-platform and sufficient for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI commands work on Linux/macOS and Windows equally.
  • Add Bash shell scripting examples for common tasks, especially where PowerShell is shown.
  • Explicitly mention platform compatibility for each example tab.
  • Consider moving PowerShell examples after CLI examples, or labeling CLI as the recommended cross-platform approach.
GitHub Create Pull Request
Virtual Machine Scale Sets Delete or update a standby pool for Virtual Machine Scale Sets ...tual-machine-scale-sets/standby-pools-update-delete.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for updating and deleting standby pools, but PowerShell (a Windows-centric tool) is given equal prominence and is mentioned in deployment instructions (e.g., ARM/Bicep templates) alongside the CLI. The use of PowerShell-specific cmdlets and deployment instructions referencing PowerShell before Linux-native alternatives (like Bash scripts or automation) shows a mild Windows bias. However, Azure CLI examples are present and shown first, which are cross-platform, and REST API examples are included. There are no Linux/macOS-specific examples or notes, and no mention of Linux tools or shell scripting.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users where appropriate.
  • Clarify that Azure CLI commands work on Linux/macOS and Windows, and consider adding OS-specific notes.
  • When referencing deployment methods (ARM/Bicep), mention cross-platform automation tools (e.g., Bash, GitHub Actions) before or alongside PowerShell.
  • Include troubleshooting notes or links for Linux/macOS environments if any differences exist.
  • Ensure that PowerShell is not presented as the default or primary method unless required.
GitHub Create Pull Request
Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations (attach, detach, update VMSS), but consistently lists PowerShell examples after CLI and before any Linux-specific shell scripts. The PowerShell examples use Windows-centric syntax (backticks, variable assignment), and troubleshooting links for disk migration and proximity placement groups point to Windows documentation first. There is no explicit Linux bias, but the ordering and example selection subtly favor Windows/PowerShell users.
Recommendations
  • Ensure that Linux/macOS shell examples (e.g., Bash scripts) are provided where PowerShell is shown, especially for advanced scenarios.
  • When linking to migration or troubleshooting guides, include both Windows and Linux documentation, or link to OS-neutral pages.
  • Alternate the order of CLI and PowerShell examples, or group them under 'Command-line' with clear OS applicability.
  • Explicitly state that Azure CLI works cross-platform and highlight any OS-specific caveats.
  • Add notes or examples for common Linux/macOS patterns (e.g., using export for environment variables, handling file paths).
GitHub Create Pull Request
Virtual Machine Scale Sets Autoscale Virtual Machine Scale Sets in the Azure portal ...le-sets/virtual-machine-scale-sets-autoscale-portal.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page primarily describes how to configure autoscale rules for Azure Virtual Machine Scale Sets using the Azure portal, which is cross-platform. However, when referencing command-line alternatives, it consistently lists Azure PowerShell (Windows-centric) before Azure CLI (cross-platform). Additionally, the 'Next steps' section links only to PowerShell-based management documentation, omitting Azure CLI or Linux-native alternatives. There are no Linux/macOS-specific examples or considerations, and Windows tools/patterns are mentioned first throughout.
Recommendations
  • When referencing command-line alternatives, list Azure CLI before or alongside Azure PowerShell to emphasize cross-platform support.
  • In the 'Next steps' section, provide links to both Azure PowerShell and Azure CLI management documentation.
  • Explicitly mention that the Azure portal and Azure CLI are available on Linux/macOS, and provide examples or links for those platforms.
  • Add a brief note or section highlighting parity and considerations for Linux/macOS users, especially for automation or scripting tasks.
GitHub Create Pull Request
Virtual Machine Scale Sets Change the upgrade policy mode on Virtual Machine Scale Sets ...ts/virtual-machine-scale-sets-change-upgrade-policy.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides platform-specific instructions for Azure Portal, CLI, PowerShell, and ARM Template. While CLI and ARM Template are cross-platform, PowerShell is Windows-centric and is given a dedicated section with detailed examples. The PowerShell example is as detailed as the CLI example, but there is no mention of Bash, Linux shell, or macOS-specific guidance. The ordering of tabs places PowerShell before ARM Template, which may subtly prioritize Windows tooling.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, and consider providing Bash-specific examples or notes where relevant.
  • Clarify that PowerShell Core is available cross-platform, or provide Bash equivalents for PowerShell commands where possible.
  • Consider reordering tabs so that cross-platform tools (CLI, ARM Template) appear before Windows-centric tools (PowerShell).
  • Add a note for Linux/macOS users about installing and using Azure CLI and PowerShell Core.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell examples are always present and shown after CLI, which is cross-platform. There are no Linux/macOS-specific examples or mentions of platform-specific considerations. The use of PowerShell may imply a Windows bias, as it is traditionally associated with Windows environments, although PowerShell Core is available cross-platform. No explicit Windows-only tools or instructions are present, but the documentation does not address Linux/macOS shell usage or potential differences.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and recommend CLI for cross-platform users.
  • Add bash or shell script examples for Linux/macOS users where appropriate.
  • Note that PowerShell Core is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI.
  • Consider reordering examples to show CLI first, emphasizing its cross-platform nature.
GitHub Create Pull Request
Virtual Machine Scale Sets Rolling upgrades with MaxSurge for Virtual Machine Scale Sets ...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides configuration instructions for rolling upgrades with MaxSurge using the Azure Portal, Azure CLI, PowerShell, and ARM templates. While the CLI and ARM template examples are cross-platform, the PowerShell example is Windows-specific and presented as a primary method. The PowerShell tab is included before ARM template instructions, and there is no mention of Linux/macOS-specific tools (e.g., Bash scripting, Cloud Shell usage on Linux/macOS, or cross-platform automation patterns). There are no explicit Linux/macOS examples or guidance.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users, especially for scripting with Azure CLI.
  • Clarify that Azure CLI commands work identically on Windows, Linux, and macOS, and recommend CLI for cross-platform automation.
  • Reorder tabs so CLI instructions appear before PowerShell, emphasizing CLI as the default cross-platform method.
  • Mention Azure Cloud Shell as a cross-platform environment for running CLI and PowerShell commands.
  • Note any limitations or differences for Linux/macOS users when using PowerShell (e.g., installation requirements, feature parity).
GitHub Create Pull Request
Virtual Machine Scale Sets Orchestration modes for Virtual Machine Scale Sets in Azure ...sets/virtual-machine-scale-sets-orchestration-modes.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. While it generally describes Azure orchestration modes in a platform-neutral way, there are several areas where Windows is referenced first or exclusively. For example, the Managed Identity section links to a Windows VMSS-specific guide, and Azure Site Recovery is noted as supported 'via PowerShell' (a Windows-centric tool) without mentioning Linux alternatives. There are no explicit Linux CLI or shell script examples; the only command-line example uses Azure CLI, which is cross-platform, but the documentation does not clarify Linux usage or provide bash-specific guidance. Overall, Linux/macOS users may need to infer or adapt instructions, but most features are described in a way that is not strictly Windows-only.
Recommendations
  • Add explicit Linux/macOS examples or notes where PowerShell is referenced, such as for Azure Site Recovery.
  • Ensure links and references to Managed Identity configuration include Linux VMSS guides, not only Windows.
  • Where command-line examples are given, clarify cross-platform compatibility and provide bash or shell script equivalents if relevant.
  • Review all feature tables and descriptions to ensure Linux support is mentioned where applicable, especially for VM extensions and monitoring.
  • Avoid referencing Windows tools (e.g., PowerShell) exclusively; mention Azure CLI or REST API alternatives where possible.
GitHub Create Pull Request
Virtual Machine Scale Sets Performing manual upgrades on Virtual Machine Scale Sets ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-perform-manual-upgrades.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure Portal, Azure CLI, PowerShell, and REST API. While CLI and REST are cross-platform, the PowerShell section is Windows-centric and is presented before REST. There is no explicit Linux/macOS bias, but PowerShell is a Windows-first tool and its inclusion without Bash or other Linux-native shell examples may create friction for Linux users. The CLI example is cross-platform and shown before PowerShell, which helps mitigate bias.
Recommendations
  • Add explicit Bash or shell script examples for Linux users, especially for automation scenarios.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows.
  • Consider mentioning cross-platform alternatives to PowerShell for Linux/macOS users.
  • Reorder sections to consistently present cross-platform tools (CLI, REST) before Windows-centric tools (PowerShell).
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell (a Windows-centric tool) is frequently presented before CLI, and some advanced examples are more detailed in PowerShell. There is a slight preference for Windows tools and patterns, with PowerShell examples shown before CLI in several sections. However, Linux/macOS users can generally complete all tasks using the CLI or ARM templates, and Linux-specific links/examples are present where relevant.
Recommendations
  • Present CLI examples before PowerShell examples to reflect cross-platform parity.
  • Ensure CLI and PowerShell examples are equally detailed and comprehensive.
  • Explicitly state that CLI commands work on Linux/macOS and Windows, and clarify any platform-specific caveats.
  • Where PowerShell is referenced, provide Bash or shell script equivalents for Linux/macOS users.
  • Review external links to ensure Linux documentation is as discoverable and prominent as Windows documentation.
GitHub Create Pull Request
Virtual Machine Scale Sets Use scale-in policies with Azure Virtual Machine Scale Sets ...ale-sets/virtual-machine-scale-sets-scale-in-policy.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation presents Azure PowerShell examples before Azure CLI examples, and uses PowerShell-specific syntax and terminology. This ordering and emphasis may suggest a Windows-centric approach, especially since PowerShell is most commonly associated with Windows environments, even though it is cross-platform. There is no explicit mention of Linux/macOS-specific considerations, nor are there examples using Bash or other Linux-native tools. However, Azure CLI examples are provided, which are suitable for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is more commonly used on Linux/macOS.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide guidance for those platforms.
  • Add notes clarifying PowerShell's cross-platform availability, but avoid implying it is the default for all users.
  • Consider including Bash script examples for resource creation and management, or link to Linux/macOS-specific guides.
  • Ensure troubleshooting and next steps sections reference both CLI and PowerShell equally, and highlight platform parity.
GitHub Create Pull Request
← Previous Page 6 of 6 Next →