Virtual Machines
2112
Total Pages
1865
Linux-Friendly Pages
247
Pages with Bias
11.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
818 issues found
Showing 76-100 of 818 flagged pages
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/maintenance-notifications.md
...articles/virtual-machines/maintenance-notifications.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation mentions both Linux and Windows VMs as supported, but when discussing how to query and handle maintenance notifications, it lists the Azure portal, PowerShell, REST API, and CLI, with PowerShell (a Windows-centric tool) mentioned before CLI. There are no explicit Linux-specific command examples or references to Linux-native tools or shell commands. The FAQ and guidance sections do not provide parity in examples or instructions for Linux users, and the links to further instructions prioritize PowerShell over CLI. This creates a subtle Windows bias by assuming familiarity with PowerShell and by not providing Linux-specific guidance or examples.
Recommendations
- Provide explicit Linux shell (bash) examples for querying and handling maintenance notifications, using Azure CLI and REST API.
- When listing tools, mention CLI before PowerShell or present them together to avoid prioritizing Windows-centric tools.
- Include references to Linux-native automation patterns (e.g., cron jobs, shell scripts) for handling notifications and maintenance.
- Add a section or FAQ entry specifically addressing Linux VM users and their workflows.
- Ensure all linked guides (e.g., CLI, PowerShell, portal) are presented with equal prominence and parity in content.
Create Pull Request
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/managed-disks-overview.md
...in/articles/virtual-machines/managed-disks-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates several instances of Windows bias. Windows terminology, tools, and examples are often mentioned first or exclusively, such as referencing Sysprep for image creation, linking to Windows-specific guides before Linux equivalents, and using Windows-centric disk partitioning concepts (MBR/GPT) with Windows documentation links. PowerShell is highlighted as a primary tool for disk uploads, and Windows drive letters (C, D) are referenced more prominently than Linux device paths. Some Linux equivalents (e.g., Pacemaker for clustering, Azure CLI for VHD upload) are present but less emphasized or appear after Windows options.
Recommendations
- Ensure Linux and Windows examples/tools are presented with equal prominence and ordering.
- Provide Linux-specific links and guides wherever Windows-specific ones are given (e.g., for disk partitioning, image creation).
- Mention Linux device paths and conventions alongside Windows drive letters in all relevant sections.
- Include Linux-first or cross-platform examples for common operations (e.g., uploading VHDs, disk encryption).
- Reference Linux clustering solutions (like Pacemaker) with equal detail as Windows Server Failover Cluster.
- Avoid assuming Windows defaults (e.g., MBR partitioning) and clarify OS-specific behaviors.
- Where possible, use neutral, cross-platform terminology before introducing OS-specific details.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/manage-restore-points.md
...ain/articles/virtual-machines/manage-restore-points.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation exclusively provides Azure PowerShell examples for all command-line operations, with no equivalent examples for Bash, Azure CLI, or other Linux-friendly tools. The use of PowerShell (a tool most commonly associated with Windows environments) is pervasive and unaccompanied by cross-platform alternatives. There is no mention of Linux or macOS workflows, and the documentation implicitly assumes a Windows-centric audience.
Recommendations
- Add Azure CLI (az) command examples alongside PowerShell for all operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash script examples where appropriate, especially for automation scenarios.
- Explicitly mention that the APIs and operations are platform-agnostic, and provide guidance for users on Linux or macOS.
- Reorder or parallelize examples so that Linux-friendly tools (e.g., Azure CLI) are presented before or alongside PowerShell.
- Add a section or note clarifying tool availability and installation instructions for different platforms.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/metadata-security-protocol/advanced-configuration.md
...s/metadata-security-protocol/advanced-configuration.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias by providing Windows-specific process examples (e.g., 'C:\Windows\OEM\Unattend.wsf.exe', 'winpa.exe', 'SYSTEM') and referencing Windows tools and paths. Linux examples are present but less prominent, and there is no parity in showing both Windows and Linux examples side by side. The documentation also uses Windows terminology (e.g., 'admin user') without explicitly referencing Linux equivalents (e.g., 'root').
Recommendations
- For every Windows-specific example (such as process paths, usernames, and process names), provide an equivalent Linux example alongside it.
- When referencing Windows concepts (like 'admin user'), explicitly mention the Linux equivalent (e.g., 'root user').
- Ensure that examples and sample configurations alternate or pair Windows and Linux scenarios to demonstrate cross-platform applicability.
- Add a section or table summarizing common process metadata values for both Windows and Linux environments.
- Review the documentation for implicit assumptions of a Windows environment and clarify where behavior or configuration differs on Linux.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/metadata-security-protocol/brownfield.md
...tual-machines/metadata-security-protocol/brownfield.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by describing the Windows extension installation as the default behavior, while Linux requires a separate, less-detailed step. The example output and extension status are shown only for Windows, with no equivalent Linux example or output. Windows extension details and paths are provided, but Linux equivalents are not.
Recommendations
- Provide explicit, step-by-step instructions and example REST API calls for installing the Proxy Agent extension on Linux VMs, similar to the detail given for Windows.
- Include example output and status messages for the Linux extension (Microsoft.CPlat.ProxyAgent.ProxyAgentLinux), mirroring the Windows example.
- List both Windows and Linux extension behaviors together, or present Linux first in at least some sections to avoid a 'Windows-first' impression.
- Add troubleshooting or validation steps for Linux, including example logs or command-line checks.
- Where Windows-specific tools or paths are mentioned, provide the Linux equivalents (e.g., process paths, command lines).
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/marketplace-images.md
...b/main/articles/virtual-machines/marketplace-images.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All command-line examples are provided exclusively in Azure PowerShell, with no Bash/CLI equivalents. The workflow and tooling (e.g., Get-AzVM, New-AzGalleryImageDefinition, Set-AzVMPlan) are all PowerShell-centric, which is more familiar to Windows users. References and links (e.g., 'Find and use Azure Marketplace images') point to Windows/PowerShell documentation. There are no examples using Azure CLI, Bash, or Linux-native tools, despite the page stating applicability to Linux VMs.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands, especially for common Linux workflows.
- Provide Bash shell script examples where appropriate.
- Ensure references and links include both Windows/PowerShell and Linux/CLI documentation.
- Explicitly call out any differences in workflow or parameters for Linux users.
- Consider reordering or parallelizing examples so that Linux/CLI and Windows/PowerShell approaches are presented equally.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/metadata-security-protocol/greenfield.md
...tual-machines/metadata-security-protocol/greenfield.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation displays Windows bias by describing the Windows process first and in more detail, mentioning the GuestProxyAgent (GPA) can be enabled directly from an ARM template on Windows, while for Linux, the process is described as more complex but not documented with examples. All code and resource names (e.g., 'GPAWinVM') are Windows-centric, and there are no Linux-specific examples or instructions. No Linux command-line or configuration examples are provided, and the documentation does not mention Linux tools or scripts.
Recommendations
- Provide Linux-specific examples for enabling MSP and configuring GPA, including the two-step process required.
- Include ARM template or REST API examples for Linux VMs, with resource names and comments relevant to Linux.
- Document the Linux-specific steps in detail, possibly with bash/CLI commands or scripts.
- Mention Linux tools or patterns (e.g., cloud-init, shell scripts) where appropriate.
- Ensure parity by presenting Linux instructions and examples alongside Windows, not only as a note.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/metadata-security-protocol/configuration.md
...l-machines/metadata-security-protocol/configuration.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias. PowerShell is explicitly listed as a configuration method, while no equivalent Linux-native CLI (such as Bash/CLI/Cloud-init) is mentioned. In the configuration section, automatic GPA installation/uninstallation is described only for Windows, with no mention of Linux. The audit log section does provide both Linux and Windows paths, but the overall pattern is to mention Windows tools and behaviors first or exclusively.
Recommendations
- Add explicit examples and instructions for configuring MSP using Linux-native tools, such as the Azure CLI, Bash scripts, or cloud-init.
- Clarify whether automatic GPA installation/uninstallation is supported on Linux VMs, and document the process if so.
- When listing configuration methods, mention cross-platform tools (e.g., Azure CLI) before or alongside PowerShell.
- Ensure that all examples and behavioral descriptions include both Windows and Linux scenarios where applicable.
- Review the ordering of OS mentions to avoid consistently listing Windows first.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/migration/sizes/nv-series-migration-guide.md
...-machines/migration/sizes/nv-series-migration-guide.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation shows a Windows bias by only referencing Windows guest OS support for NVv4, linking exclusively to Windows driver setup guides, and providing no Linux-specific instructions or examples for migration, driver installation, or extensions. All driver and extension links point to Windows documentation, and there is no mention of Linux equivalents or parity.
Recommendations
- Add explicit information about Linux support for each VM series, including whether Linux is supported or not for NVsv3 and NVv4.
- Provide Linux-specific migration steps, including guidance for installing Nvidia and AMD GPU drivers on Linux VMs where supported.
- Include links to Linux driver setup guides and extension documentation alongside or before Windows equivalents.
- Clarify in the FAQ and migration steps which features or extensions are available for Linux and provide parity where possible.
- If NVv4 does not support Linux, state this clearly and provide guidance for Linux users migrating from NV-series.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/monitor-vm-reference.md
...main/articles/virtual-machines/monitor-vm-reference.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-specific tools and logs (e.g., Windows Event Log, IIS, WindowsFirewall, AD assessments, Windows DNS servers, Windows Security Events) are mentioned and described in detail, often before or without equivalent Linux examples. Many log tables and data collection methods reference Windows-centric workloads and tools, while Linux equivalents (such as Syslog) are less frequent and less detailed. Some examples and explanations (e.g., VM shutdown behavior, event collection) focus on Windows mechanisms or terminology. Linux-specific monitoring (e.g., Linux Daemons, Syslog) is present but less emphasized, and there are few direct Linux examples or tool mentions.
Recommendations
- Ensure Linux examples are provided for all major monitoring scenarios, especially where Windows-specific tools (Event Log, IIS, AD, DNS) are described.
- Add explicit references to Linux equivalents (e.g., systemd, journald, Apache/Nginx logs, Linux DNS servers) alongside Windows tools.
- Balance the order of presentation so that Linux and Windows monitoring approaches are introduced together, rather than Windows-first.
- Expand the description and guidance for Linux-specific log tables and data collection methods to match the detail given to Windows.
- Where PowerShell or Windows CLI is referenced, provide Bash or Linux CLI equivalents.
- Clarify any OS-specific behaviors (e.g., VM shutdown) for both Windows and Linux, not just Windows.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/move-region-maintenance-configuration-resources.md
...nes/move-region-maintenance-configuration-resources.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page exhibits a Windows bias by providing PowerShell examples first and in greater detail, referencing Windows-specific tools and patterns (e.g., PowerShell cmdlets, Format-Table), and linking to migration instructions with a Windows-centric URL. While Azure CLI examples are present, the overall structure and emphasis favor Windows/PowerShell workflows over Linux-native approaches.
Recommendations
- Provide Bash/Linux shell examples alongside PowerShell, especially for variable definitions and command usage.
- Ensure that CLI examples are given equal prominence and detail as PowerShell examples, possibly presenting CLI first since it is cross-platform.
- Avoid using Windows-specific terminology (e.g., Format-Table) without Linux equivalents or explanations.
- Link to migration instructions and documentation that are not Windows-specific, or provide parallel links for Linux.
- Explicitly mention that all CLI commands work on Linux/macOS, and consider adding screenshots or outputs from a Linux terminal.
- If PowerShell is required, clarify that PowerShell Core is cross-platform and provide installation instructions for Linux users.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/move-region-maintenance-configuration.md
...tual-machines/move-region-maintenance-configuration.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation consistently lists PowerShell before CLI when describing how to create, assign, and delete maintenance configurations. PowerShell is a Windows-centric tool, and this ordering subtly prioritizes Windows workflows. There are no explicit Linux shell or Bash examples, and no mention of Linux-specific tools or guidance, despite the page stating it applies to Linux VMs.
Recommendations
- List Azure CLI examples and links before PowerShell, as CLI is cross-platform and more accessible to Linux users.
- Add explicit Bash/Linux shell command examples where possible, especially for common tasks like saving lists or mapping configurations.
- Clarify that PowerShell Core is available on Linux, if referencing PowerShell, or provide guidance for installing it on Linux.
- Ensure parity in documentation by including Linux/Bash-specific instructions or notes, not just CLI.
- Review and update the language to avoid implying PowerShell is the default or preferred method for all users.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/move-virtual-machines-regional-zonal-portal.md
...achines/move-virtual-machines-regional-zonal-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific documentation (e.g., checking VM SKU availability via a Windows/Powershell page), mentioning PowerShell before CLI in the 'Next steps', and lacking explicit Linux or Bash examples throughout the tutorial. The workflow is described entirely through Azure Portal UI steps, with no command-line examples for either platform, but the only referenced automation is PowerShell, which is Windows-centric.
Recommendations
- Provide equivalent Bash/Azure CLI examples for all operations, especially for selecting and moving VMs.
- Reference Linux/Bash documentation alongside or before Windows/PowerShell documentation when discussing prerequisites or next steps.
- Ensure links to 'Check VM SKU availability' and similar tasks include both Windows and Linux instructions.
- In 'Next steps', mention Azure CLI and Bash automation explicitly, not just PowerShell.
- Add a section or callout for Linux users, clarifying any differences or additional steps required.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/scripts/virtual-machines-powershell-sample-copy-snapshot-to-storage-account.md
...nes-powershell-sample-copy-snapshot-to-storage-account.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively provides a PowerShell script and references only PowerShell commands and modules for exporting/copying Azure managed snapshots as VHDs. There are no Bash, Azure CLI, or Linux-native examples or instructions. The tools and workflow described are Windows-centric, and Linux alternatives are not mentioned or linked, despite the relevance for cross-platform cloud administrators.
Recommendations
- Add equivalent sample scripts using Azure CLI and Bash to demonstrate the same workflow for Linux users.
- Include a section comparing PowerShell and CLI approaches, with links to relevant Linux documentation.
- Mention Linux-compatible tools and patterns (e.g., az snapshot, az storage blob copy) alongside PowerShell commands.
- Ensure that Linux examples are presented with equal prominence and clarity as Windows/PowerShell examples.
- Update the 'Next steps' and related links to include Linux/Bash/CLI alternatives, not just PowerShell samples.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/security-policy.md
...blob/main/articles/virtual-machines/security-policy.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation displays a mild Windows bias. Windows tools and patterns (e.g., PowerShell, BitLocker) are often mentioned first or exclusively, and some examples or instructions reference Windows before Linux. In some sections, Linux equivalents are mentioned but not always with equal detail or parity. The use of Azure PowerShell is emphasized for Windows, while Azure CLI is suggested for Linux, but with less prominence. There are also references to Windows-specific tools (e.g., BitLocker) before their Linux counterparts (e.g., dm-crypt).
Recommendations
- Ensure that Linux and Windows examples are presented with equal prominence and detail, ideally side-by-side.
- When referencing tools or commands, provide both PowerShell (Windows) and Bash/CLI (Linux) equivalents in each section.
- Avoid listing Windows tools or patterns before Linux equivalents; alternate or group them together.
- Expand Linux-specific instructions and examples to match the detail provided for Windows.
- Where possible, use cross-platform tools (e.g., Azure CLI) as the primary example, with PowerShell as an alternative.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/share-using-app-registration.md
...icles/virtual-machines/share-using-app-registration.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for sharing gallery images across tenants, but the PowerShell section is significantly more detailed and uses Windows-centric tools and patterns (e.g., RDP, Windows OS configuration, New-AzVMConfig with Set-AzVMOperatingSystem -Windows). The PowerShell example includes steps for creating networking resources and configuring a Windows VM, while the CLI example is much simpler and omits these details. There is no explicit Linux VM creation example, and Windows terminology and tools are used by default.
Recommendations
- Add a detailed Azure CLI example that matches the depth of the PowerShell example, including networking setup and VM configuration.
- Include explicit instructions and examples for creating Linux VMs (e.g., using --os-type Linux in CLI and Set-AzVMOperatingSystem -Linux in PowerShell).
- Provide parity in troubleshooting and related content for both Windows and Linux scenarios.
- Avoid defaulting to Windows-centric tools (e.g., RDP, Windows OS) and mention Linux alternatives (e.g., SSH, Linux OS configuration) alongside Windows options.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/share-gallery.md
...s/blob/main/articles/virtual-machines/share-gallery.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides examples for the Azure Portal, Azure CLI, and PowerShell. PowerShell is a Windows-centric tool, and its inclusion as a primary example (with a dedicated tab) can indicate Windows bias, especially since there is no mention of Linux-native scripting alternatives (such as Bash scripts or Cloud Shell Bash usage). The CLI examples use Azure CLI, which is cross-platform, but the PowerShell section is Windows-focused. There are no explicit Linux-specific examples or references to Linux tools, and the order of examples (Portal, CLI, PowerShell) puts PowerShell ahead of any Linux-native scripting guidance.
Recommendations
- Add explicit Bash script examples for Linux users, especially for common tasks like assigning roles.
- Clarify that Azure CLI commands work on all platforms, and consider providing sample Bash scripts or command-line usage in a Linux context.
- If PowerShell is included, mention that PowerShell Core is cross-platform, or provide guidance for Linux users on how to use PowerShell if needed.
- Consider adding a section or tab specifically for Linux users, highlighting any platform-specific considerations or best practices.
- Review the order of examples to avoid the perception of Windows/PowerShell being the primary or preferred method.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/general-purpose/daldsv7-series.md
...rtual-machines/sizes/general-purpose/daldsv7-series.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page shows mild Windows bias. In the 'Feature support' section, Windows features (e.g., nested virtualization) are referenced with Windows-specific links before Linux equivalents, and the nested virtualization link points only to Windows/Hyper-V documentation. Disk encryption support is split into Linux and Windows, but both are marked 'Not Supported'. In the networking section, bandwidth testing references NTTTCP, a Windows-centric tool, without mentioning Linux alternatives. There are no command-line examples, but where tooling is mentioned, Windows tools are referenced exclusively or first. No Linux-specific examples or tools are provided.
Recommendations
- Include Linux equivalents for all referenced Windows features and tools (e.g., provide links to nested virtualization documentation for Linux/KVM).
- Mention Linux-compatible bandwidth testing tools (such as iperf3) alongside NTTTCP.
- Ensure that feature support documentation links are provided for both Windows and Linux, or clarify when a feature is Windows-only.
- Add example usage or troubleshooting steps for both Windows and Linux environments where relevant.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/high-performance-compute/hbv3-series.md
...machines/sizes/high-performance-compute/hbv3-series.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page shows mild Windows bias. It references Windows-specific technologies (e.g., Hyper-V nested virtualization) and Windows tools (NTTTCP) for network testing, without mentioning or providing Linux equivalents. Where optimization or testing is discussed, Windows is mentioned before Linux, and no Linux-specific examples or tools are provided. There are no command-line examples, but the referenced resources and terminology lean toward Windows.
Recommendations
- Include Linux-specific tools for network bandwidth testing, such as iperf or netperf, alongside NTTTCP.
- When referencing features like nested virtualization, provide links or notes about Linux support and alternatives (e.g., KVM).
- Ensure that optimization guidance and resource links cover both Linux and Windows, with parity in detail and order of presentation.
- Add explicit Linux examples or instructions where relevant, especially in areas like storage and networking configuration.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/memory-optimized/eadsv6-series.md
...rtual-machines/sizes/memory-optimized/eadsv6-series.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Feature support links to nested virtualization documentation specifically for Hyper-V on Windows, without mentioning Linux alternatives (such as KVM). The network section references NTTTCP, a Windows-centric bandwidth testing tool, without mentioning Linux equivalents (like iperf). There are no Linux-specific command examples or references to Linux tools, and Windows features/tools are mentioned first or exclusively in some cases.
Recommendations
- Include Linux equivalents for referenced tools (e.g., mention iperf for bandwidth testing alongside NTTTCP).
- When discussing nested virtualization, reference both Windows (Hyper-V) and Linux (KVM) documentation or clarify support for Linux.
- Add Linux-specific examples or resources where relevant, such as links to Linux disk encryption documentation, Linux network optimization, and Linux storage performance.
- Ensure parity in mentioning both Windows and Linux features/tools, and avoid listing Windows options first unless there is a technical reason.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/memory-optimized/edsv6-series.md
...irtual-machines/sizes/memory-optimized/edsv6-series.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. References to features and tools are often Windows-first or Windows-exclusive (e.g., nested virtualization links to Hyper-V on Windows, bandwidth testing references NTTTCP—a Windows tool). There are no Linux-specific usage examples, and Linux equivalents are not mentioned alongside Windows tools. Feature support for disk encryption is split by OS, but both are marked 'Not Supported', so no bias there. Overall, the page lacks Linux parity in tooling and examples.
Recommendations
- Include Linux equivalents when referencing Windows tools (e.g., mention Linux bandwidth testing tools like iperf alongside NTTTCP).
- Provide links to Linux documentation for features such as nested virtualization (e.g., KVM/QEMU guides for nested virtualization on Linux).
- Add Linux-specific usage examples or optimization guidance where relevant.
- Ensure that references to OS-specific features/tools are presented in parallel, not Windows-first.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/memory-optimized/mdsv3-vhm-series.md
...al-machines/sizes/memory-optimized/mdsv3-vhm-series.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. Windows Server is listed first in the compatible images section, and the only external feature link for nested virtualization points to a Windows/Hyper-V guide. There are no Linux-specific operational examples, tools, or links for features like nested virtualization or storage/network performance testing. Linux images are mentioned, but not prioritized or accompanied by equivalent Linux documentation links.
Recommendations
- List Linux distributions before or alongside Windows Server in compatibility sections, or randomize order.
- Provide Linux-specific links for features such as nested virtualization (e.g., KVM, QEMU guides) and performance testing tools (e.g., fio, iperf).
- Include examples or references for common Linux administrative tasks relevant to these VM sizes, such as disk and network tuning.
- Where Windows tools or guides are linked, ensure Linux equivalents are also referenced.
- Add explicit notes about Linux support and best practices where operational guidance is given.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/retirement/av1-series-retirement.md
...ual-machines/sizes/retirement/av1-series-retirement.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides detailed instructions for resizing VMs using the Azure portal and PowerShell, both of which are Windows-centric tools. There are no examples or instructions for resizing VMs using the Azure CLI, which is cross-platform and commonly used on Linux. The PowerShell example is given before any mention of CLI, and no Linux-specific guidance or screenshots are provided.
Recommendations
- Add step-by-step instructions and examples for resizing VMs using the Azure CLI, including command-line examples that work on Linux and macOS.
- Explicitly mention that the Azure CLI is cross-platform and suitable for Linux users.
- Consider providing Bash shell examples alongside PowerShell examples to ensure parity.
- If possible, include screenshots or instructions relevant to Linux environments (e.g., using Azure CLI in a terminal).
- Reorder the examples so that cross-platform tools (Azure CLI) are presented before or alongside Windows-specific tools (PowerShell).
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/resize-vm.md
...blob/main/articles/virtual-machines/sizes/resize-vm.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is given extensive coverage with multiple scripts and detailed explanations, while Linux-native tools (such as Bash or shell scripting) are not mentioned. The Terraform example references a Windows VM quickstart, and the CLI examples use generic shell syntax but do not provide explicit Linux/Bash examples or clarify cross-platform differences. Windows tools and patterns (PowerShell, Windows VM resource blocks) are mentioned before or instead of Linux equivalents, and there is a lack of Linux-specific guidance or examples.
Recommendations
- Add explicit Bash/shell script examples for resizing VMs using Azure CLI, highlighting any Linux-specific considerations.
- Provide Terraform examples for both azurerm_linux_virtual_machine and azurerm_windows_virtual_machine, with links to Linux quickstart guides.
- Balance the PowerShell section with equivalent Bash or cross-platform scripting guidance for Linux users.
- Clarify cross-platform differences in CLI usage, such as environment variables, quoting, and authentication steps for Linux.
- Reference Linux documentation and tools where relevant, and avoid referencing only Windows quickstarts or resources.
- Ensure that examples and explanations are presented in a platform-neutral order, or alternate between Windows and Linux where possible.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/retirement/dcsv2-series-retirement.md
...l-machines/sizes/retirement/dcsv2-series-retirement.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is given as a primary example for command-line migration, and the Azure CLI example is shown with PowerShell syntax (e.g., variable assignment with $), which is not standard for Linux shells. The Azure portal (a GUI tool popular among Windows users) is always listed first for migration steps, and there are no explicit Bash or Linux shell examples. There is also no mention of Linux-specific considerations, such as SSH usage, Linux-specific scripting, or differences in VM management between Windows and Linux environments.
Recommendations
- Provide Bash/Linux shell examples for Azure CLI commands, using standard Linux variable syntax (e.g., export resourceGroup="myResourceGroup").
- Clearly distinguish between PowerShell and Bash syntax in CLI examples, and provide both where appropriate.
- Add Linux-specific migration considerations, such as SSH access, file permissions, or common Linux admin tasks during migration.
- Balance the order of presentation: alternate or randomize between portal, PowerShell, and CLI (Bash) examples, or explicitly state that the instructions apply to both Windows and Linux users.
- Mention Linux tools (e.g., cloud-init, SSH, Bash scripting) where relevant, especially in sections discussing custom scripts or images.
- Ensure screenshots and UI instructions clarify any OS-specific differences, or note when steps are OS-agnostic.