1641
Pages Scanned
48
Pages Flagged
1641
Changed Pages
2.9%
% Pages Flagged
Scan Information
Started At: 2026-01-06 22:28:06
Finished At: 2026-02-10 18:00:39
Status: completed
Target Repo: Azure Compute
Current Phase: discovery
Files Queued: 1641
Files Completed: 1641
Problematic Pages
48 issues found
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/linux/use-remote-desktop.md
.../articles/virtual-machines/linux/use-remote-desktop.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation is generally Linux-focused but exhibits Windows bias in several areas: Windows and PowerShell examples for Azure network security group (NSG) rules are provided before Linux equivalents, and Windows-specific tools and patterns (such as PowerShell and references to using SSH from Windows) are mentioned prominently. There is also a tendency to reference Windows workflows (e.g., using the Azure portal, PowerShell) alongside or before Linux-native approaches.
Recommendations
- Present Linux/Azure CLI examples before Windows/PowerShell examples, especially in sections about Azure resource management.
- Clearly separate Windows-specific guidance (such as PowerShell commands or SSH from Windows) into optional or 'additional information' sections, rather than interleaving them with core Linux instructions.
- Add parity by including Linux-native tools and workflows for all steps, and ensure that Linux examples are primary and complete.
- Where Windows tools or patterns are referenced (e.g., Azure PowerShell), provide equivalent Linux-native alternatives (e.g., Bash scripts, Azure CLI) first.
- Review and adjust the order of instructions and references so that Linux users are not required to sift through Windows-specific content to find relevant information.
Create Pull Request
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.
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.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/snapshot-copy-managed-disk.md
...rticles/virtual-machines/snapshot-copy-managed-disk.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
linux_example_last
Summary
The documentation presents Windows/PowerShell examples and references before Linux/CLI equivalents in both the main instructions and the 'Next steps' section. PowerShell (a Windows-centric tool) is given prominence, and links to further examples for Windows are listed before Linux. There is also a slight emphasis on Windows tools and workflows.
Recommendations
- Present Azure CLI (cross-platform) examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Ensure that 'Next steps' and further reading links for Linux are listed with equal prominence and before or alongside Windows links.
- Explicitly mention that Azure CLI commands work on both Linux and Windows to reinforce cross-platform parity.
- Where possible, add Bash or Linux shell-specific notes or troubleshooting steps, especially if there are differences.
- Review language to ensure it does not implicitly prioritize Windows tools or workflows over Linux equivalents.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/ssh-keys-portal.md
...blob/main/articles/virtual-machines/ssh-keys-portal.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides only a PowerShell example for connecting to the VM, without mentioning or showing equivalent Linux/macOS terminal commands. The only explicit example for using SSH is shown in a PowerShell context, and the phrase 'open a PowerShell prompt' is used, which prioritizes Windows users. There are no Linux-specific instructions or screenshots, and the only reference to Linux is in the context of the VMs, not the client environment.
Recommendations
- Provide explicit Linux/macOS terminal examples alongside the PowerShell example, e.g., 'Open a terminal (Linux/macOS) or PowerShell (Windows) and type: ...'.
- Use more neutral language such as 'Open a terminal' instead of 'Open a PowerShell prompt', or clarify both options for different operating systems.
- Include screenshots or instructions that are relevant to Linux/macOS users where appropriate.
- Ensure that links to further documentation (e.g., 'Use SSH keys to connect to Linux VMs') include Linux client instructions, or add a direct section here.
- Consider adding a table or callout box that shows the SSH command usage on Windows (PowerShell), Linux, and macOS for parity.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/trusted-launch-existing-vm-gen-1.md
...s/virtual-machines/trusted-launch-existing-vm-gen-1.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias in several areas: Windows tools and patterns (such as MBR2GPT.exe, BitLocker, and PowerShell) are mentioned first or exclusively, with Linux equivalents either missing, less detailed, or referenced after Windows. The PowerShell and Windows-specific instructions are more comprehensive, while Linux instructions are less detailed and sometimes defer to external registration or validation steps. There are also sections where only Windows troubleshooting steps are provided, and Linux-specific upgrade scenarios are less supported or described.
Recommendations
- Provide equally detailed Linux instructions for disk layout conversion (MBR to GPT and EFI partition creation), including common commands and troubleshooting steps for popular distributions.
- Include Linux-specific troubleshooting sections similar to the Windows 'Known issues' (e.g., handling EFI partition issues, common errors during upgrade).
- When listing prerequisites or best practices, avoid mentioning Windows tools (e.g., BitLocker, Defrag) first or exclusively; instead, provide Linux equivalents or parallel guidance.
- In the 'Update Guest OS volume' section, add step-by-step instructions for converting MBR to GPT and adding EFI partitions on Linux, not just validation steps.
- Balance the use of PowerShell and CLI examples by providing Bash shell scripts or commands for Linux users where appropriate.
- Ensure that all sections referencing Windows tools or patterns (e.g., MBR2GPT.exe, Defrag, BitLocker) also mention or link to Linux alternatives (e.g., gdisk, parted, cryptsetup/LUKS).
- Add more Linux-focused examples and clarify support for distributions beyond the Azure Marketplace images, or provide guidance for custom images.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/trusted-launch-existing-vmss.md
...icles/virtual-machines/trusted-launch-existing-vmss.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation exhibits a Windows bias in several ways: Windows-based OS images (e.g., '2022-datacenter-azure-edition') are used as the default and only example in ARM template, CLI, and PowerShell code blocks. The ARM template quickstart link points to a Windows-specific template. PowerShell is heavily featured, and the CLI/PowerShell examples use Windows image SKUs without showing Linux equivalents. The Guest Attestation extension section lists both Windows and Linux publishers, but no Linux-specific example is provided. There are no explicit Linux OS image examples or instructions for enabling Trusted Launch on Linux-based scale sets.
Recommendations
- Provide parallel examples using Linux OS images (e.g., Ubuntu, RHEL) in all code snippets (ARM template, CLI, PowerShell) alongside or alternating with Windows examples.
- Include links to Linux-specific ARM template quickstarts, not just Windows.
- In the Guest Attestation extension section, show explicit examples for both Windows and Linux extension publishers.
- Clarify in each section that Trusted Launch is supported for both Windows and Linux, and highlight any Linux-specific considerations.
- Ensure that CLI and PowerShell examples use both Windows and Linux image SKUs, or alternate between them.
- Review and update screenshots and portal instructions to reflect Linux scenarios where applicable.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/virtual-machine-scale-sets-maintenance-control.md
...ines/virtual-machine-scale-sets-maintenance-control.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell (a Windows-centric tool) in both the management options list and the 'Next steps' section, where only the PowerShell guide is directly linked. There are no explicit Linux/Unix shell examples or references, and the Azure CLI (which is cross-platform and more common on Linux) is listed after PowerShell. No Linux-specific guidance or parity is provided.
Recommendations
- Provide equal prominence to Azure CLI examples and documentation, especially in the 'Next steps' section (e.g., link to both PowerShell and CLI guides).
- Include explicit Linux/Unix shell examples or references where relevant.
- Consider listing Azure CLI before PowerShell in management options to reflect cross-platform parity.
- Add a note clarifying that all features are available via CLI on Linux and macOS, not just PowerShell on Windows.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/virtual-machines-create-restore-points.md
...ual-machines/virtual-machines-create-restore-points.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows-first bias by describing application consistency in detail for Windows (mentioning VSS writers) before Linux (which is only briefly referenced as using pre- and postscripts). Windows-specific tools (VSS) are mentioned explicitly, while Linux equivalents are not named or explained. There are no concrete examples or guidance for Linux users, and no Linux-specific tools or scripts are referenced.
Recommendations
- Provide equal detail for Linux application consistency, including naming common tools (e.g., fsfreeze, custom scripts) and describing their use.
- Include explicit Linux examples or references, such as sample pre- and post-scripts for achieving application consistency.
- Reorder or parallelize explanations so that Linux and Windows approaches are presented with equal prominence and detail.
- Link to Linux-specific documentation or resources for configuring application-consistent backups.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/linux/time-sync.md
...blob/main/articles/virtual-machines/linux/time-sync.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page is focused on Linux VM time synchronization in Azure and provides comprehensive Linux-specific guidance and examples. However, it opens with a lengthy discussion of Windows Server 2016 time sync improvements, including links to Windows documentation, and references to Windows infrastructure and tools before discussing Linux-specific mechanisms. There are no PowerShell or Windows command examples for Linux, but the initial context and references are Windows-centric, which may give the impression that Windows is the primary or default platform. The only PowerShell example is for encoding cloud-init data, which is a cross-platform Azure deployment detail, not a time sync operation.
Recommendations
- Move or minimize the Windows Server 2016 discussion to a background or reference section, focusing the introduction on Linux time sync requirements and mechanisms.
- If mentioning Azure's host OS, clarify that the underlying host time is provided to all guest OSes (Linux and Windows) equally, and that the Linux mechanisms are distinct.
- Prioritize Linux-specific tools, services, and configuration examples in the introduction and throughout the document.
- Provide Linux command-line examples exclusively (as is already done), and only include Windows/PowerShell examples if strictly necessary for cross-platform deployment scenarios, clearly labeling them as such.
- Add a brief summary or table comparing Linux and Windows time sync approaches in Azure, if cross-platform context is needed, but keep Linux as the focus.
- Ensure that all external links in the 'Next steps' or 'More information' sections are relevant to Linux, or clearly separate Windows references.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/metadata-security-protocol/faq.md
...les/virtual-machines/metadata-security-protocol/faq.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing Windows provisioning philosophy as the default and not providing Linux-specific usage examples or tools. Windows patterns are described first, and Linux is discussed mainly in terms of limitations. There are no Linux command-line or tool examples, and the documentation does not mention Linux equivalents for checking MSP status or managing the GPA.
Recommendations
- Add Linux-specific examples for checking MSP status, such as using curl, jq, or other Linux-native tools to query the VM API or instance view.
- Provide guidance on installing and managing the Guest Proxy Agent on Linux, including package management commands (e.g., apt, yum) and service management (systemd).
- Clarify Linux provisioning workflows and offer parity with Windows documentation, including any available VM extensions or automation options.
- Avoid framing Windows philosophy as the default; present both Windows and Linux approaches equally and in parallel.
- Include troubleshooting steps and health checks using Linux tools (e.g., journalctl, systemctl) for the GPA.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/migration/dedicated-host-migration-guide.md
...l-machines/migration/dedicated-host-migration-guide.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides command-line examples for both PowerShell and Azure CLI, but PowerShell is consistently listed first in all tabbed sections. This ordering can subtly prioritize Windows users, as PowerShell is more closely associated with Windows environments. There are no explicit Linux shell (bash) examples or mentions of Linux-specific tools, though Azure CLI is cross-platform. No Windows-only tools are referenced, but the absence of bash or Linux-native command examples may disadvantage Linux users.
Recommendations
- Alternate the order of PowerShell and CLI tabs, or list CLI first in some sections to avoid implicit Windows prioritization.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide bash examples where appropriate.
- Add a short note or section for Linux users, clarifying that all CLI instructions are fully supported on Linux systems.
- Consider including bash script snippets for common migration tasks, especially for users who automate with shell scripts.
- Review for any subtle language that assumes a Windows environment and adjust to be OS-neutral.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/network-security-group-test.md
...ticles/virtual-machines/network-security-group-test.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exhibits a Windows bias by focusing its main example on testing RDP (Remote Desktop Protocol) connectivity, which is specific to Windows VMs. There are no equivalent examples for common Linux connectivity scenarios (such as SSH), and the only explicit example provided is for RDP. While the prerequisites mention both Linux and Windows VMs, the step-by-step instructions and screenshots are tailored to a Windows-centric use case, and no Linux-specific protocols or ports are demonstrated.
Recommendations
- Provide parallel examples for Linux VMs, such as testing SSH (port 22) connectivity, alongside the RDP example.
- In the 'Test inbound connections' section, add a table row and screenshot for SSH (Linux) in addition to RDP (Windows).
- Explicitly mention that the steps apply to both Linux and Windows VMs, and clarify which service types (RDP, SSH, etc.) are relevant for each OS.
- Ensure that the documentation alternates or balances the order of Windows and Linux examples, or presents them together, to avoid the perception of Windows-first bias.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/setup-infiniband.md
...lob/main/articles/virtual-machines/setup-infiniband.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation generally maintains OS neutrality but shows mild Windows bias by listing Windows Server alongside Linux distributions in the OS support section, and by mentioning Microsoft HPC Pack (a Windows-centric tool) as a primary cluster option. Linux tools and patterns are referenced, but Windows tools (HPC Pack, MS-MPI) are given equal or slightly more prominent placement, and the only explicit cluster management tool described in detail is Microsoft HPC Pack. There are no explicit command-line examples, but the mention of Windows tools without equal Linux alternatives in some sections suggests a subtle bias.
Recommendations
- Provide explicit Linux-based cluster management options (e.g., Slurm, OpenHPC) alongside Microsoft HPC Pack in the cluster configuration section.
- When listing supported operating systems, consider listing Linux distributions first, as they are more commonly used for HPC workloads.
- Include example workflows or references for configuring InfiniBand and MPI on Linux, not just links to generic setup pages.
- If mentioning Windows-specific tools like HPC Pack, also mention and link to Linux-native alternatives and guides.
- Ensure parity in detail and guidance for both Linux and Windows users throughout the documentation.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/compute-optimized/faldsv7-series.md
...ual-machines/sizes/compute-optimized/faldsv7-series.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page is largely neutral and platform-agnostic, but there are subtle signs of Windows bias. In the 'Feature support' section, Windows features are listed before Linux equivalents. In the networking section, the only bandwidth/throughput testing tool mentioned is NTTTCP, which is a Windows-native tool (though it has a Linux port, it's primarily associated with Windows). There are no explicit Linux command-line examples or Linux-specific tools referenced, and the only mention of Linux is in the context of unsupported disk encryption.
Recommendations
- When listing feature support, alternate the order of Windows and Linux features or group them together to avoid implying priority.
- In the networking section, mention Linux-native tools for bandwidth testing (e.g., iperf3, netperf) alongside NTTTCP, and provide links to their usage.
- Where relevant, provide both Windows and Linux command-line examples or references for common VM operations.
- Add explicit references to Linux documentation or best practices, especially in sections discussing optimization, troubleshooting, or feature support.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/general-purpose/dadsv7-series.md
...irtual-machines/sizes/general-purpose/dadsv7-series.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page shows mild Windows bias. In the 'Feature support' section, the Windows disk encryption feature is listed before the Linux equivalent. In the 'Nested Virtualization' feature, only a Windows/Hyper-V link is provided. In the networking section, the only bandwidth testing tool mentioned is NTTTCP, which is a Windows-centric tool, and no Linux alternatives are referenced. No explicit Linux command-line or tool examples are given, and Linux is only mentioned in passing.
Recommendations
- In the 'Feature support' section, list Linux and Windows features in parallel or alphabetically, and provide equivalent detail and links for both platforms.
- For 'Nested Virtualization', add a reference or guidance for nested virtualization on Linux (e.g., KVM/QEMU), or clarify if it's not supported.
- In the networking section, mention Linux bandwidth testing tools such as iperf or netperf alongside NTTTCP, and provide links to relevant Linux documentation.
- Wherever possible, ensure that examples, tools, and troubleshooting steps are provided for both Windows and Linux environments.
- Review all resource links and ensure Linux-specific documentation is included where relevant.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/general-purpose/daldsv6-series.md
...rtual-machines/sizes/general-purpose/daldsv6-series.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page shows mild Windows bias. It references Windows-specific tools (e.g., NTTTCP for bandwidth testing) and links to a Windows-specific nested virtualization guide before any Linux equivalent. There are no explicit Linux command-line examples or Linux-first guidance, and Linux is only mentioned in passing (e.g., 'Azure Disk Encryption for Linux VMs').
Recommendations
- Include Linux equivalents for all Windows-specific tools mentioned (e.g., mention iPerf or netperf for bandwidth testing alongside NTTTCP).
- Add links to Linux-specific documentation for features like nested virtualization, or clarify Linux support status.
- Where possible, provide both Linux and Windows examples or guidance in parallel, especially for performance testing and optimization.
- Review all feature support and resource lists to ensure Linux and Windows are given equal prominence and detail.
- If a feature is not supported on Linux or Windows, provide a brief explanation or link to more information for both platforms.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/general-purpose/dldsv6-series.md
...irtual-machines/sizes/general-purpose/dldsv6-series.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is largely neutral and platform-agnostic, focusing on VM specifications and features. However, there is mild Windows bias in the 'Feature support' section, where 'Nested Virtualization' links only to a Windows/Hyper-V guide, and in the 'Bandwidth/Throughput testing (NTTTCP)' resource, which references a Windows-centric tool before mentioning Linux compatibility. No Linux-specific examples, tools, or guides are provided, and Windows resources are mentioned first or exclusively in relevant contexts.
Recommendations
- Add equivalent Linux documentation links for features like Nested Virtualization (e.g., KVM or nested virtualization on Linux in Azure).
- When referencing tools like NTTTCP, clarify Linux support and provide direct links to Linux usage guides or alternative Linux-native tools (e.g., iperf, netperf).
- Ensure that feature support sections mention both Windows and Linux resources equally, or provide parity in documentation links.
- Where features are not supported for either OS (e.g., Azure Disk Encryption), clarify restrictions for both platforms and link to both Windows and Linux documentation.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/general-purpose/dcadsv5-series.md
...rtual-machines/sizes/general-purpose/dcadsv5-series.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page demonstrates mild Windows bias, most notably in the 'Feature support' section where 'Nested Virtualization' links exclusively to a Windows/Hyper-V guide, and in the 'Network' section where bandwidth testing references NTTTCP, a Microsoft/Windows-centric tool, without mentioning Linux alternatives. There are no explicit Linux examples or equivalent Linux tooling references, and Windows tools/patterns are mentioned first or exclusively in relevant contexts.
Recommendations
- Include Linux equivalents or alternatives when referencing Windows-specific features or tools (e.g., mention KVM/QEMU for nested virtualization, and iperf or netperf for network bandwidth testing).
- Provide links to Linux documentation or guides alongside Windows/Hyper-V links, especially in feature support sections.
- Add explicit Linux usage examples or notes where relevant, ensuring parity in guidance for both platforms.
- Review referenced tools and resources to ensure cross-platform applicability, or clearly indicate platform-specific limitations.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/memory-optimized/eadsv7-series.md
...rtual-machines/sizes/memory-optimized/eadsv7-series.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page generally maintains OS neutrality, but there are subtle signs of Windows bias. Specifically, the 'Nested Virtualization' feature links only to a Windows/Hyper-V guide, and the bandwidth/throughput testing resource references NTTTCP, a tool with a Windows-centric history (though now cross-platform). In the network section, Windows is mentioned before Linux in the context of performance optimization, and no Linux-specific tools or examples are provided. There are no explicit Linux command examples, and Linux parity is not highlighted.
Recommendations
- Provide equivalent Linux documentation links for features like Nested Virtualization (e.g., KVM/QEMU on Linux).
- When referencing tools like NTTTCP, clarify their cross-platform availability and consider mentioning Linux-native alternatives (e.g., iperf, netperf) for network testing.
- When discussing OS-specific requirements or optimizations, list Linux and Windows in parallel or alphabetically, rather than putting Windows first.
- Add explicit Linux examples or links where relevant, especially in sections discussing performance tuning, disk encryption, or network testing.
- Review all feature support and resource links to ensure Linux parity and visibility.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/memory-optimized/ebdsv6-series.md
...rtual-machines/sizes/memory-optimized/ebdsv6-series.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page shows mild Windows bias. In the 'Feature support' section, nested virtualization links to a Windows-specific guide ('hyper-v-on-windows'), and the network performance testing resource references NTTTCP, a Microsoft/Windows tool, without mentioning Linux alternatives. Additionally, Windows terminology and resources (e.g., 'Generation 1/2 VMs', 'Azure Disk Encryption for Windows VMs') are mentioned before or alongside Linux equivalents, but Linux-specific examples or tools are not provided.
Recommendations
- Include Linux-specific examples and links for features such as nested virtualization (e.g., KVM/QEMU guides for Linux).
- Mention and link to Linux-compatible network performance testing tools (e.g., iperf, netperf) alongside NTTTCP.
- Ensure parity in documentation by providing both Windows and Linux references for VM features and management tasks.
- Where possible, alternate the order of Windows and Linux mentions, or group them together to avoid implicit prioritization.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/memory-optimized/m-series.md
...es/virtual-machines/sizes/memory-optimized/m-series.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page shows mild Windows bias. In the VM Basics section, Windows Server is listed first among supported guest OS versions for large vCPU counts, ahead of Linux distributions. In the Feature Support section, nested virtualization links specifically to a Windows/Hyper-V guide, with no mention of Linux alternatives. In the Networking section, bandwidth testing references NTTTCP, a Windows-centric tool, without mentioning Linux equivalents like iperf.
Recommendations
- List supported guest OS versions in alphabetical order or alternate the order to avoid Windows-first bias.
- Provide links to nested virtualization documentation for both Windows (Hyper-V) and Linux (KVM/QEMU) environments.
- Mention Linux-compatible network testing tools (e.g., iperf, netperf) alongside NTTTCP in the networking resources.
- Ensure that examples, guides, and references are provided for both Windows and Linux wherever relevant.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/using-managed-disks-template-deployments.md
...l-machines/using-managed-disks-template-deployments.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation consistently uses Windows-based examples and references, such as the 'vm-simple-windows' template and 'MicrosoftWindowsServer' images, throughout all code samples and explanations. Linux equivalents are not provided in the main body, and Linux-specific image references or templates are only mentioned in the 'Next steps' section, not in the core instructional content.
Recommendations
- Provide parallel Linux examples alongside Windows examples in all code snippets, using Linux image references (e.g., 'publisher': 'Canonical', 'offer': 'UbuntuServer').
- Reference both Windows and Linux quickstart templates in the main instructional sections, not just in 'Next steps'.
- Explicitly show how parameters (such as 'windowsOSVersion') would differ for Linux deployments.
- Clarify any OS-specific differences in disk deployment or template structure, if applicable.
- Ensure that introductory and example sections do not default to Windows-only resources or naming conventions.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/understand-vm-reboots.md
...ain/articles/virtual-machines/understand-vm-reboots.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation claims applicability to both Linux and Windows VMs, but there is a subtle Windows-first bias. In the 'Reduce downtime' section, the link to 'scheduled events for Linux' is listed after 'scheduled events for Windows', and there are no explicit Linux-specific examples or tools mentioned elsewhere. No PowerShell or Windows-only commands are present, but Linux parity is not fully achieved due to lack of Linux-specific guidance or examples.
Recommendations
- List Linux and Windows resources in parallel or alternate the order to avoid Windows-first bias.
- Include Linux-specific examples, such as using cloud-init, waagent, or relevant Linux commands for handling maintenance events.
- Explicitly mention any Linux-specific considerations or tools where applicable, similar to how Windows tools would be referenced.
- Ensure that links to Linux and Windows documentation are given equal prominence and detail.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/virtual-machines-create-restore-points-portal.md
...hines/virtual-machines-create-restore-points-portal.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page focuses exclusively on using the Azure portal for creating and restoring VM restore points, with references to alternative methods via Azure CLI and PowerShell. However, when linking to further instructions on restoring a VM from a disk, it directs users to Windows-specific guides ('./windows/create-vm-specialized-portal.md' and './windows/attach-managed-disk-portal.yml'), without mentioning or linking to Linux equivalents. There are no Linux-specific examples or instructions, and the restoration workflow appears Windows-centric.
Recommendations
- Include links to Linux-specific documentation for creating VMs from disks and attaching managed disks, such as './linux/create-vm-specialized-portal.md' and './linux/attach-managed-disk-portal.yml'.
- Add explicit instructions or examples for restoring Linux VMs from restore points, ensuring parity with the Windows workflow.
- Where alternative methods (CLI, PowerShell) are mentioned, clarify which commands or scripts are suitable for Linux environments.
- Review all referenced guides and ensure both Windows and Linux paths are presented side-by-side, or at least both are mentioned.