Virtual Machines

1080
Total Pages
1005
Linux-Friendly Pages
75
Pages with Bias
6.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

815 issues found
Showing 476-500 of 815 flagged pages
Virtual Machines Migrate Standard HDD OS disks by September 08, 2028 ...n/articles/virtual-machines/disks-hdd-os-retirement.md
Low Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation covers both Linux and Windows VMs, and provides Azure CLI and PowerShell examples for listing affected disks. However, the PowerShell example is presented before the Azure CLI example, which is a minor 'windows_first' bias. Both tools are mentioned, and the Disk Storage Center is a web portal, not Windows-specific. No critical Windows-only tools or missing Linux examples are found.
Recommendations
  • Present Azure CLI and PowerShell examples in parallel or list Azure CLI first, as it is cross-platform.
  • Explicitly note that Azure CLI works on Linux/macOS/Windows, while PowerShell is primarily Windows-focused.
  • Consider adding Bash script examples for Linux users, if relevant.
GitHub Create Pull Request
Virtual Machines Secure Azure Managed Disk Downloads and Uploads ...icles/virtual-machines/disks-secure-upload-download.md
Low Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for most operations, but PowerShell examples are often presented before CLI (which is more cross-platform). References to the portal and PowerShell are frequent, and PowerShell is sometimes highlighted more prominently. However, Linux parity is generally maintained, especially in the 'Next steps' section, which includes both Linux and Windows links.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly mention that Azure CLI commands work on Linux/macOS, and provide Bash shell examples where relevant.
  • Where PowerShell is referenced, clarify if it is available cross-platform (PowerShell Core), or provide alternatives for Linux users.
  • Ensure screenshots and portal instructions are not Windows-centric (e.g., avoid showing Windows UI elements unless necessary).
GitHub Create Pull Request
Virtual Machines Instantly access managed disk snapshots ...les/virtual-machines/disks-instant-access-snapshots.md
Low Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating instant access snapshots, but PowerShell (a Windows-centric tool) is given equal prominence. Azure CLI is cross-platform, but there are no explicit Linux/macOS-specific instructions or notes. The ordering of examples sometimes puts PowerShell before CLI, and there are no references to Linux-native scripting or shell environments. However, the CLI examples are sufficient for Linux users, and no critical tasks are Windows-only.
Recommendations
  • Always present Azure CLI examples before PowerShell to emphasize cross-platform parity.
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows, and provide any relevant shell-specific notes (e.g., quoting, environment variables).
  • Consider adding a note for Linux/macOS users about installing Azure CLI and running the commands in bash/zsh.
  • If possible, provide bash script examples or highlight any OS-specific considerations for disk snapshot operations.
GitHub Create Pull Request
Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.md
Low Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides both Azure CLI and PowerShell options for configuring disk restrictions, but PowerShell is mentioned first and linked more prominently. The custom RBAC role section links only to a PowerShell-based guide, and PowerShell is referenced before CLI in the NetworkAccessPolicy section. Linux-specific examples and parity are present but less emphasized.
Recommendations
  • Add links to Azure CLI guides for creating custom RBAC roles, not just PowerShell.
  • Present CLI and PowerShell options equally, or list CLI first to better support Linux/macOS users.
  • Ensure all sections referencing PowerShell also reference CLI equivalents.
  • Include explicit Linux/macOS instructions or examples where possible.
GitHub Create Pull Request
Virtual Machines What's new in Azure Disk Storage ...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally neutral and focused on Azure Disk Storage features, but there are a few subtle signs of Windows bias. Some links and references point to Windows-specific documentation first or exclusively (e.g., expand disks links, unattached disks documentation), and Windows tools (Azure PowerShell) are mentioned alongside Azure CLI, but Linux equivalents are not always given equal prominence. In a few cases, Linux documentation is referenced, but often after Windows or not at all.
Recommendations
  • Ensure that all feature links referencing disk operations (such as expanding disks, finding unattached disks) include both Windows and Linux documentation, ideally side-by-side or with equal prominence.
  • When mentioning Azure PowerShell, also mention Azure CLI and Bash where appropriate, and clarify cross-platform support.
  • Review linked articles to ensure Linux/macOS parity in examples and instructions.
  • Avoid referencing Windows documentation first when the feature is cross-platform; alternate or combine links for Windows and Linux.
  • Add explicit statements about Linux/macOS support for features where relevant.
GitHub Create Pull Request
Virtual Machines Ephemeral OS disks ...b/main/articles/virtual-machines/ephemeral-os-disks.md
Low Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Minor Powershell Reference
Summary
The documentation covers ephemeral OS disks for both Linux and Windows VMs, with clear applicability to both platforms. Examples and guidance are provided for both OS types, and VM size recommendations are given for Ubuntu (Linux) and Windows Server images. However, there are minor instances of Windows bias: Windows Server image sizing is mentioned first in the 'Size requirements' section, and PowerShell is referenced before CLI in the 'Customer Managed key' section. These are minor ordering biases and do not impact the ability of Linux/macOS users to follow the documentation.
Recommendations
  • Alternate the order of Linux and Windows examples in sections where both are relevant, or present them side-by-side.
  • When referencing tooling, mention Azure CLI and PowerShell together, or list CLI first for Linux parity.
  • Ensure that all critical steps and examples are available for both Linux and Windows users, especially in linked deployment guides.
GitHub Create Pull Request
Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation is focused on the Azure Key Vault VM Extension for Linux and provides Linux-specific guidance throughout. However, in several sections, Windows-oriented tools (Azure PowerShell) are presented first or in greater detail than their Linux equivalents (Azure CLI). PowerShell deployment instructions and troubleshooting commands are shown before CLI, and PowerShell-specific warnings are included. There are no missing Linux examples, but the ordering and emphasis may create friction for Linux users.
Recommendations
  • Present Azure CLI examples before Azure PowerShell examples, as CLI is cross-platform and native to Linux/macOS.
  • Add explicit notes clarifying that PowerShell is not required for Linux users and that Azure CLI is the preferred tool for Linux/macOS.
  • Ensure troubleshooting commands are shown with Azure CLI first, and PowerShell only as an alternative.
  • Remove or minimize PowerShell-specific warnings unless they are relevant to Linux users.
  • Consider adding a brief section on using Bash scripts or other Linux-native automation tools for deployment, if applicable.
GitHub Create Pull Request
Virtual Machines NVIDIA GPU Driver Extension - Azure Linux VMs ...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is focused on Linux VM GPU driver installation, but includes PowerShell examples alongside Azure CLI and ARM template examples. The PowerShell example is presented before the Azure CLI example, which is more relevant for Linux users. There are references to Windows extensions, but these are clearly separated and not the main focus. No Linux example is missing, and Linux-specific tools and commands are well represented.
Recommendations
  • Move the Azure CLI example before the PowerShell example to prioritize Linux-relevant tooling.
  • Clarify that PowerShell is primarily for users on Windows or those using Azure Cloud Shell, and recommend Azure CLI for Linux users.
  • Consider adding Bash shell script examples for common deployment scenarios, as Bash is native to Linux.
  • Explicitly note that PowerShell examples are optional for Linux users and not required.
GitHub Create Pull Request
Virtual Machines Deprovision or generalize a VM before creating an image ...docs/blob/main/articles/virtual-machines/generalize.md
Low Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation covers both Linux and Windows VM generalization, but Windows examples and prerequisites are more detailed and are presented after Linux, with Windows-specific tools (Sysprep, PowerShell) used. The Windows section includes registry edits, role checks, and encryption steps, while the Linux section is simpler and relies on waagent. The Azure CLI is used for Linux, but PowerShell is used for Windows, with no Azure CLI equivalent shown for Windows. Overall, both platforms are covered, but Windows examples are more tool-specific and detailed.
Recommendations
  • Provide Azure CLI examples for generalizing Windows VMs, not just PowerShell.
  • Ensure parity in detail: add more troubleshooting and validation steps for Linux, similar to Windows.
  • Consider showing Linux and Windows sections in parallel or with equal prominence.
  • Add a note clarifying that both Azure CLI and PowerShell can be used for either OS where applicable.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to benchmark disk performance using custom I/O workloads, so that I can optimize storage configurations for maximum read and write IOPS in my virtual machines. ...ncludes/virtual-machines-managed-disks-benchmarking.md
Low Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation presents benchmarking instructions for both Windows (DISKSPD) and Linux (FIO), but the Windows section appears first and is more detailed in its parameter explanations. Both platforms are covered with clear examples and screenshots, but Windows tools and examples are prioritized in order of presentation.
Recommendations
  • Consider presenting Linux (FIO) and Windows (DISKSPD) sections in parallel or alternating order, or explicitly state that both tools are equally supported.
  • Add a brief introductory note clarifying that both Windows and Linux are fully supported for disk benchmarking, and that the order of examples does not imply preference.
  • Ensure parameter explanations and example depth are consistent across both Windows and Linux sections.
  • If possible, provide a summary table comparing DISKSPD and FIO usage for common scenarios.
GitHub Create Pull Request
Virtual Machines Create an image definition and image version ...s/blob/main/articles/virtual-machines/image-version.md
Low Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows guidance, but there is a notable Windows bias in several areas. PowerShell examples are prominent and often shown before or alongside CLI examples. Windows-specific tools (Sysprep, PowerShell) are referenced, sometimes before Linux equivalents. In the PowerShell section, Windows is the default in the example, with Linux only mentioned as an alternative. However, Linux parity is generally maintained, and CLI and REST examples are provided for both OS types.
Recommendations
  • Ensure Linux and Windows examples are equally represented and alternated in order of appearance.
  • In PowerShell sections, provide explicit Linux examples (e.g., -OsType Linux) rather than only mentioning it as an alternative.
  • Where Windows tools are referenced (e.g., Sysprep), ensure Linux equivalents (e.g., waagent -deprovision) are mentioned with equal prominence.
  • Consider starting with a neutral or Linux example in code blocks, or alternate the default OS type in examples.
  • Add explicit notes clarifying that all steps are applicable to both Linux and Windows unless otherwise stated.
GitHub Create Pull Request
Virtual Machines Azure Disk Encryption scenarios on Linux VMs ...ticles/virtual-machines/linux/disk-encryption-linux.md
Low Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is given equal prominence throughout, including detailed scripts and explanations. PowerShell cmdlets are referenced frequently and sometimes before CLI equivalents. The documentation also refers to using PowerShell sessions on local machines, which is a Windows-native pattern, though PowerShell Core is cross-platform. There are no missing Linux examples, but the heavy use of PowerShell and its prominence may create friction for Linux users who prefer native Bash or CLI workflows.
Recommendations
  • Make clear that Azure PowerShell is cross-platform, but highlight Azure CLI as the default for Linux users.
  • Consider showing Azure CLI examples first in each section, as CLI is more native to Linux environments.
  • Add brief Bash scripting examples for common tasks (e.g., mounting disks, preparing VHDs) where relevant.
  • Clarify that PowerShell scripts can be run on Linux/macOS with PowerShell Core, but CLI is often simpler.
  • Reduce references to 'PowerShell session' and instead use 'terminal session' or 'shell session' for Linux contexts.
GitHub Create Pull Request
Virtual Machines Verify encryption status for Linux - Azure Disk Encryption ...tual-machines/linux/how-to-verify-encryption-status.md
Low Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for verifying disk encryption status on Linux VMs, but the PowerShell section is presented before the Azure CLI section and contains more detailed, step-by-step examples. This may create friction for Linux users, as PowerShell is not the default scripting environment on most Linux distributions. However, Azure CLI examples are present and comprehensive, and OS-level Linux commands are included.
Recommendations
  • Move the Azure CLI section before the PowerShell section to prioritize Linux-native tooling.
  • Ensure all PowerShell examples have equivalent Azure CLI examples, matching detail and coverage.
  • Explicitly note that PowerShell commands are optional and primarily for users who prefer PowerShell or are working cross-platform.
  • Expand OS-level Linux command examples (e.g., using 'lsblk', 'cryptsetup') to cover more scenarios, such as checking encryption status for multiple disks or partitions.
  • Add a short introductory note clarifying that Azure CLI and Bash are the recommended tools for Linux users.
GitHub Create Pull Request
Virtual Machines Create and upload a Red Hat Enterprise Linux VHD for use in Azure ...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides detailed instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, throughout the document, Windows tools and patterns (such as Hyper-V Manager and PowerShell cmdlets) are often mentioned first or exclusively in key steps, especially for disk conversion and VM creation. Linux alternatives are present, but Windows-centric approaches (e.g., Hyper-V Manager, convert-vhd cmdlet) are prioritized or referenced before Linux-native tools (e.g., qemu-img, KVM).
Recommendations
  • Present Linux-native tools and procedures (such as qemu-img, KVM, VMware) before or alongside Windows/Hyper-V tools, especially in sections about disk conversion and VM creation.
  • Where Windows tools (e.g., Hyper-V Manager, convert-vhd) are mentioned, immediately provide equivalent Linux commands and workflows, not just as secondary options.
  • Clarify that Linux users can complete all steps without access to Windows or Hyper-V, and highlight Linux-only workflows in the introduction and summary.
  • Consider adding a summary table or flowchart that shows parity between Windows and Linux approaches for each major step.
  • Avoid referencing Windows/PowerShell tools as the default or primary method unless the majority of users are expected to use them.
GitHub Create Pull Request
Virtual Machines Overview of Azure Disk Storage ...in/articles/virtual-machines/managed-disks-overview.md
Low Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Minor Windows Reference
Summary
The documentation is generally cross-platform and explicitly states applicability to both Linux and Windows VMs. However, there are minor instances of Windows bias: Windows terminology and links are sometimes presented first, Windows-specific tools (PowerShell) are referenced alongside Linux tools (CLI), and Windows partitioning concepts (MBR/GPT) are discussed in detail with Windows-centric links. The temporary disk section references Windows drive letters before Linux device paths. These biases are minor and do not prevent Linux/macOS users from completing tasks or understanding features.
Recommendations
  • Ensure Linux and Windows examples/tools are presented together or alternate their order.
  • Where partitioning concepts are discussed, include links to Linux equivalents (e.g., Linux partitioning guides, GPT/MBR on Linux).
  • When referencing disk paths, mention Linux device paths before or alongside Windows drive letters.
  • Add links to Linux-specific documentation where only Windows links are provided, such as for disk conversion or partitioning.
GitHub Create Pull Request
Virtual Machines Migrate from Amazon Elastic Compute Cloud (Amazon EC2) to Azure Virtual Machines ...ion/migrate-from-elastic-compute-cloud-architecture.md
Low Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides general migration guidance from Amazon EC2 to Azure Virtual Machines, covering compute, storage, networking, and images. While it mentions both Windows and Linux operating systems, there are subtle signs of Windows bias: Windows-specific tools (Sysprep) are mentioned before Linux equivalents, and some example patterns (such as image generalization) are described in a Windows-first manner. There are no explicit Linux command-line examples (e.g., Bash, Linux CLI), and PowerShell or Windows-centric terminology appears slightly more frequently. However, the overall guidance is mostly platform-neutral and does not prevent Linux users from completing the migration.
Recommendations
  • Provide Linux-specific examples and CLI commands alongside Windows/PowerShell examples, especially in sections about image capture, agent installation, and storage migration.
  • Mention Linux tools (such as waagent, cloud-init, and relevant configuration management tools) with equal prominence to Windows tools like Sysprep.
  • Ensure that migration steps and validation guidance include Linux-specific considerations, such as SELinux/AppArmor, systemd, and Linux networking nuances.
  • Add explicit Bash or Linux CLI snippets for tasks like copying files, installing agents, or benchmarking performance.
  • Review the order of presentation to avoid Windows-first bias in listing tools or procedures.
GitHub Create Pull Request
Virtual Machines Migrate Standard HDD OS disks by September 08, 2028 ...n/articles/virtual-machines/disks-hdd-os-retirement.md
Low Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides migration guidance applicable to both Linux and Windows VMs. However, in the section describing how to filter disks in the Disk Storage Center, the OS type filter is described as 'Linux and Windows', with Windows mentioned first. Both Azure CLI and PowerShell examples are provided, but neither is prioritized over the other. No Windows-specific tools or patterns are mentioned, and Linux parity is generally maintained.
Recommendations
  • When listing OS types or examples, alternate the order (e.g., 'Linux and Windows' or 'Windows and Linux') to avoid subtle bias.
  • Ensure that CLI and PowerShell examples are always presented together, as in this document.
  • Consider explicitly stating that all guidance applies equally to Linux and Windows VMs to reinforce parity.
GitHub Create Pull Request
Virtual Machines Support matrix for VM restore points ...n/articles/virtual-machines/concepts-restore-points.md
Low Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation presents Windows operating system support before Linux in the 'Operating system support for application consistency' section. However, both Windows and Linux are covered with equivalent detail, and no Windows-specific tools or examples are prioritized elsewhere. The 'Next steps' section lists CLI, Portal, and PowerShell documentation, but does not show a preference for Windows tools.
Recommendations
  • Consider listing Linux operating system support before Windows, or presenting both together to avoid implicit prioritization.
  • Ensure that linked 'Next steps' guides (CLI, Portal, PowerShell) provide parity for Linux users, such as Bash/CLI examples alongside PowerShell.
  • Explicitly state that all features and instructions apply equally to Linux and Windows unless otherwise noted.
GitHub Create Pull Request
Virtual Machines Share an Azure Managed Disk across VMs ...cs/blob/main/articles/virtual-machines/disks-shared.md
Low Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation covers both Windows and Linux platforms for Azure shared disks, but Windows examples and explanations are presented before Linux equivalents in several sections (e.g., sample workloads, performance throttling examples). All major features and tools for Linux are described, but Windows scenarios are consistently shown first, which may subtly reinforce Windows as the default or primary platform.
Recommendations
  • Alternate the order of Windows and Linux sections, or present them in parallel (side-by-side) where possible.
  • Ensure Linux examples are as detailed and prominent as Windows examples.
  • Consider starting some sections (such as sample workloads or performance examples) with Linux scenarios to balance presentation.
  • Explicitly state that both Windows and Linux are equally supported at the start of relevant sections.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to benchmark disk performance using custom I/O workloads, so that I can optimize storage configurations for maximum read and write IOPS in my virtual machines. ...ncludes/virtual-machines-managed-disks-benchmarking.md
Low Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation presents Windows benchmarking tool (DISKSPD) examples and explanations before Linux tool (FIO) examples. Both platforms are covered with detailed instructions and sample commands, but Windows is given precedence in ordering and tool introduction.
Recommendations
  • Reorder sections so Linux (FIO) and Windows (DISKSPD) examples are presented in parallel or with equal prominence.
  • Add a summary table comparing DISKSPD and FIO usage for benchmarking on Windows and Linux VMs.
  • Explicitly state that both tools are recommended and supported, and clarify which tool is best for each OS.
  • Ensure that Linux instructions are as detailed and prominent as Windows instructions.
GitHub Create Pull Request
Virtual Machines Expand Virtual Hard Disks on a Linux VM ...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation is focused on Linux VM disk expansion and provides thorough, distribution-specific Linux guidance. However, in the section about classic VM SKU support for 'expand without downtime', only a PowerShell script is provided to check SKU compatibility, with no equivalent Azure CLI or Bash example for Linux users.
Recommendations
  • Add an Azure CLI or Bash example for checking VM SKU compatibility for classic VM SKUs, so Linux users can perform the same check without needing PowerShell.
  • Where possible, ensure that any Azure PowerShell guidance is accompanied by Azure CLI alternatives, especially for tasks relevant to Linux VM management.
GitHub Create Pull Request
Virtual Machines Enable on-demand disk bursting ...ain/articles/virtual-machines/disks-enable-bursting.md
Low Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples, but PowerShell (commonly associated with Windows environments) is presented before CLI. There is no explicit Linux/macOS bias, but the ordering and emphasis on PowerShell may subtly favor Windows users. All examples are cross-platform, and no Windows-only tools or patterns are used.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more universally used across Linux, macOS, and Windows.
  • Explicitly note that both PowerShell and CLI are cross-platform, and clarify that CLI is available natively on Linux/macOS.
  • Consider adding brief notes or links about installing Azure CLI on Linux/macOS for new users.
  • Ensure parity in example depth and clarity between PowerShell and CLI sections.
GitHub Create Pull Request
Virtual Machines Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents." ...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Low Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides a balanced overview of backup and disaster recovery for Azure Managed Disks, explicitly stating applicability to both Linux and Windows VMs. However, in several places, Windows tools and patterns (such as Volume Shadow Service and SQL Server Always On) are mentioned before their Linux equivalents. For example, application-consistent backup is described using Windows-specific mechanisms first, and Linux solutions (like fsfreeze) are referenced as secondary, with less detail. SQL Server backup options are discussed in depth, while Linux database solutions (like Oracle or MongoDB) are mentioned but not elaborated upon. Examples and tool recommendations tend to prioritize Windows approaches.
Recommendations
  • Provide equal detail for Linux backup tools and patterns, such as describing how to achieve application-consistent backups for popular Linux workloads (e.g., Oracle, PostgreSQL, MySQL) and referencing relevant Linux-native solutions.
  • When mentioning Windows tools (e.g., Volume Shadow Service), immediately follow with Linux equivalents (e.g., fsfreeze, LVM snapshots, or application-specific backup mechanisms) and clarify their limitations or advantages.
  • Expand examples for Linux database solutions (e.g., Oracle, MongoDB, PostgreSQL) to match the depth given to SQL Server.
  • Ensure that tables and comparison sections reference both Windows and Linux consistency mechanisms equally.
  • Consider including links to Linux backup best practices or third-party solutions for Linux VMs.
GitHub Create Pull Request
Virtual Machines Best practices for virtual machine cost optimization ...s/virtual-machines/cost-optimization-best-practices.md
Low Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation generally presents cost optimization best practices for Azure virtual machines in a platform-neutral manner. However, there is a minor bias in the development/test environment section, where Windows VM sizing guidance ('Use at least B2 for Windows machines') is provided before any Linux-specific guidance, and Windows pricing links are mentioned before Linux equivalents in one section. No PowerShell-heavy, Windows tools, or missing Linux example biases are evident. All major recommendations and features are applicable to both Windows and Linux VMs.
Recommendations
  • Provide equivalent VM sizing guidance for Linux machines if relevant, or clarify if the recommendation is Windows-specific.
  • When referencing pricing pages or VM sizes, mention Linux and Windows options together, or list Linux first in some cases for parity.
  • If automation examples are provided in future updates, include both Windows (PowerShell) and Linux (Bash/shell) scripts.
  • Clarify when recommendations are OS-specific (e.g., 'Use at least B2 for Windows machines; for Linux, B1 may suffice depending on workload').
GitHub Create Pull Request
Virtual Machines Server-side encryption of Azure Managed Disks ...blob/main/articles/virtual-machines/disk-encryption.md
Low Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation covers both Linux and Windows VM scenarios and explicitly states applicability to both. However, there are several instances where Windows/PowerShell tools and documentation links are presented before their Linux/Azure CLI equivalents. References to PowerShell are slightly more prominent (e.g., in revoking access and enabling automatic key rotation), and Windows documentation links are often listed first. No critical Linux gaps are present, but the ordering and prominence of Windows tools create minor friction for Linux users.
Recommendations
  • Present Azure CLI (Linux/macOS) and PowerShell (Windows) links and examples in parallel, or alternate their order to avoid Windows-first bias.
  • Where PowerShell and CLI are mentioned, clarify that both are fully supported and provide equal visibility to Linux/macOS workflows.
  • Add explicit Linux/macOS examples or references where only PowerShell is mentioned, such as in the 'revoking access' section.
  • Consider grouping CLI and PowerShell instructions under a common heading (e.g., 'Using Azure CLI or PowerShell') to reinforce parity.
GitHub Create Pull Request
← Previous Page 20 of 33 Next →