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 226-250 of 815 flagged pages
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for resizing Azure VMs, including advanced scenarios (e.g., availability sets), while the Azure CLI section is less emphasized and lacks parity in depth and explanation. PowerShell is presented before CLI, and the Terraform example references a Windows-specific quickstart. There are no explicit Linux/macOS shell examples (e.g., Bash), and the Terraform code sample is Windows-focused. This creates friction for Linux/macOS users, who may prefer CLI or Bash-based workflows.
Recommendations
- Provide Bash shell examples using Azure CLI for resizing VMs, with explanations matching the PowerShell section.
- Ensure CLI examples cover advanced scenarios (e.g., availability sets) with the same level of detail as PowerShell.
- Add a Linux-focused Terraform example or reference, or clarify that the steps are identical for Linux VMs.
- Present CLI examples before PowerShell, or clarify that both are equally supported.
- Avoid referencing only Windows-specific Terraform quickstarts; include or link to Linux quickstarts as well.
Create Pull Request
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The FAQ for Trusted Launch covers both Windows and Linux VM scenarios, but there is a notable pattern where Windows/PowerShell examples and terminology are presented first or more prominently. CLI and PowerShell examples are given for most tasks, but Linux-specific CLI/bash examples are sometimes secondary or omitted. Windows terminology and links (e.g., Secure Boot, Hyper-V) appear before Linux equivalents, even when both are supported. However, Linux-specific guidance (e.g., SBInfo tool installation) is included, and the documentation does not exclude Linux users from completing tasks.
Recommendations
- Ensure that Linux CLI/bash examples are presented alongside or before PowerShell/Windows examples where applicable.
- Where possible, provide parity in example output for both Windows and Linux images (e.g., show both Windows and Linux sample JSON outputs).
- Explicitly mention Linux tools and workflows in introductory sections, not just in troubleshooting.
- Review the order of examples and links to avoid consistently prioritizing Windows/PowerShell.
- Add more Linux-focused troubleshooting and validation steps where relevant.
Virtual Machines
Trusted Launch for Azure VMs
.../blob/main/articles/virtual-machines/trusted-launch.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation is generally cross-platform and explicitly states Trusted Launch applies to both Linux and Windows VMs. However, there are several subtle signs of Windows bias: Windows examples and references (such as ARM templates for Windows VMs) are listed first, links to Secure Boot and vTPM documentation point to Windows-focused resources, and virtualization-based security (VBS) and HVCI sections are Windows-only without clarifying their lack of Linux applicability. The only explicit example templates are for Windows VMs, with no Linux equivalents shown.
Recommendations
- Add ARM template deployment examples for Linux VMs alongside Windows examples.
- Include links to Linux-specific documentation for Secure Boot and vTPM, or clarify when referenced resources are Windows-only.
- In sections describing features like VBS and HVCI, explicitly state that these are Windows-only and note Linux alternatives or limitations.
- Ensure parity in example code, deployment walkthroughs, and troubleshooting steps for both Linux and Windows users.
Virtual Machines
Deploy a Trusted Launch VM
...ain/articles/virtual-machines/trusted-launch-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers Trusted Launch for both Linux and Windows VMs, with parity across portal, CLI, template, and PowerShell methods. However, PowerShell examples are Windows-centric and appear before Linux equivalents in some sections. In PowerShell sections, only Windows image/OS parameters are shown, and Linux PowerShell examples are missing. Additionally, PowerShell is presented as a primary automation method, which is more relevant to Windows users.
Recommendations
- Add PowerShell examples for Linux VM deployment, including Linux image/OS parameters.
- In PowerShell sections, clarify which steps are for Windows and which are for Linux, or provide parallel Linux-focused snippets.
- Where possible, present Linux and Windows examples side-by-side or clearly label them.
- Ensure that CLI and template examples continue to show Linux and Windows parity.
- Consider mentioning cross-platform scripting tools (e.g., Bash, Python) for Linux users if relevant.
Virtual Machines
Create a VM from a generalized image in a gallery
...icles/virtual-machines/vm-generalized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux and Windows guidance, but PowerShell examples are heavily focused on Windows VM creation, with Windows-specific parameters (e.g., Set-AzVMOperatingSystem -Windows) and password authentication. Windows VM creation steps are shown first in PowerShell sections, and some network security group rules reference RDP (port 3389) before SSH (port 22). Linux examples are present (especially in CLI and REST), but Windows patterns and tools are often mentioned or demonstrated before Linux equivalents.
Recommendations
- In PowerShell examples, provide explicit Linux VM creation steps (e.g., Set-AzVMOperatingSystem -Linux) alongside Windows examples, or clarify how to adapt for Linux.
- When showing network security group rules, include SSH (port 22) examples before or alongside RDP (port 3389), and clarify Linux/Windows differences.
- Ensure parity in authentication methods: demonstrate SSH key usage in PowerShell for Linux VMs, not just password-based authentication.
- Where possible, alternate the order of Windows and Linux examples, or clearly label them to avoid implicit prioritization.
- Add notes or links to Linux-specific guidance in sections where Windows patterns dominate.
Virtual Machines
Create a VM from a specialized image version
...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from specialized images, but the PowerShell sections are notably more detailed and extensive, including full network setup and VM configuration. CLI examples are concise and do not show equivalent network/resource configuration steps. Additionally, PowerShell examples (which are Windows-centric) are always present alongside CLI, but there are no bash or Linux shell script examples. In some sections, PowerShell is presented before Portal instructions, and the PowerShell examples use Windows conventions (e.g., RDP port blocking), which may not be relevant for Linux users.
Recommendations
- Expand Azure CLI examples to include full VM/network setup steps, matching the detail of PowerShell examples.
- Add bash/Linux shell script examples for common tasks, especially for network and VM configuration.
- Clarify when PowerShell steps are Windows-specific or provide equivalent Linux-focused guidance (e.g., SSH port configuration).
- Ensure CLI and PowerShell examples are equally detailed and placed in parallel, not favoring PowerShell.
- Consider adding a section or note for Linux/macOS users about using Azure CLI in their environments.
Virtual Machines
Create a VM from a specialized image version
...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from specialized images, but PowerShell examples are notably more verbose and detailed, including full network setup and VM configuration. CLI examples are shorter and less comprehensive. PowerShell is a Windows-centric tool, and its prominence and depth in the documentation may create friction for Linux/macOS users. Additionally, PowerShell examples are often shown immediately after CLI, which can subtly reinforce Windows-first patterns.
Recommendations
- Expand Azure CLI examples to include full VM/network setup, matching the detail level of PowerShell examples.
- Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider including Bash scripts or references to native Linux tools where relevant.
- Ensure that CLI and PowerShell examples are equally comprehensive and placed with equal prominence.
- Add a note clarifying that PowerShell examples are primarily for Windows users, while CLI is suitable for all platforms.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation, while focused on Ubuntu Linux VHD creation for Azure, frequently references Windows-specific tools (Hyper-V, PowerShell's Convert-VHD cmdlet) and provides Windows-centric instructions (e.g., Hyper-V Manager steps, Convert-VHD usage) without offering Linux-native alternatives or parity. Windows tools and workflows are mentioned first and in detail, while Linux equivalents (such as qemu-img or VirtualBox) are missing, creating friction for Linux/macOS users.
Recommendations
- Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage) alongside Hyper-V/PowerShell examples.
- Provide guidance for extracting and preparing VHDs on Linux/macOS, not just Windows/WSL.
- Include steps for shutting down and managing VMs using Linux virtualization platforms (e.g., KVM, VirtualBox) in addition to Hyper-V.
- Ensure that Linux-native workflows are presented before or alongside Windows-specific ones, not only as an afterthought.
- Clarify which steps are platform-agnostic and which are Windows-specific, and offer alternatives where possible.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page for resizing an Azure virtual machine exhibits several forms of Windows bias. PowerShell is given extensive, detailed coverage with multiple scripts and explanations, while Linux-native tools (such as Bash or cloud-init) are not mentioned. The CLI section uses Bash syntax but is not explicitly labeled as a Linux example, and the Terraform section references only a Windows VM quickstart. There are no explicit Linux-specific examples or guidance, and PowerShell is presented before CLI or Terraform, reinforcing a Windows-first perspective.
Recommendations
- Add explicit Linux/Bash examples for resizing VMs, including using the Azure CLI from a Linux shell and mentioning any Linux-specific considerations.
- In the Terraform section, include both Linux and Windows VM resource block examples, or link to both quickstarts.
- Balance the order of examples: consider presenting Azure CLI (cross-platform) before PowerShell, or clarify that PowerShell is available on Linux/macOS as well.
- Where possible, mention that Azure CLI commands can be run natively on Linux/macOS, and provide any relevant troubleshooting tips for those platforms.
- If there are Linux-specific limitations or best practices (e.g., for cloud-init, SSH, etc.), include them.
Virtual Machines
Create a VM from a generalized image in a gallery
...icles/virtual-machines/vm-generalized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Linux and Windows examples for VM creation, but PowerShell examples are heavily Windows-centric, with explicit use of Windows-specific parameters and patterns (e.g., Set-AzVMOperatingSystem -Windows, RDP port configuration). In several PowerShell sections, Windows VM creation is the default, and Linux-specific instructions are missing or only briefly referenced. Windows terminology and tooling (PowerShell, RDP, Windows credential prompts) are used more extensively and often appear before Linux equivalents. CLI and REST examples are more balanced, but PowerShell sections lack Linux parity.
Recommendations
- Add explicit Linux PowerShell examples, including Set-AzVMOperatingSystem -Linux and SSH configuration.
- When showing PowerShell code, provide both Windows and Linux VM creation flows, or clarify which OS is being targeted.
- Ensure network security group examples include both SSH (22) and RDP (3389) rules, not just RDP.
- Where possible, avoid defaulting to Windows in PowerShell examples; instead, present OS-agnostic or dual examples.
- Clarify in text when an example is Windows-specific, and provide links or code for Linux equivalents.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation, while focused on Ubuntu Linux VHDs, repeatedly references Windows-centric tools and workflows (notably Hyper-V and PowerShell's Convert-VHD), often without providing Linux-native alternatives or mentioning them second. This creates friction for Linux/macOS users, especially in the disk creation and conversion steps.
Recommendations
- Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, or KVM).
- Mention Linux/macOS alternatives alongside Windows tools, not after or instead of them.
- Provide example commands for VHD conversion on Linux (e.g., qemu-img convert -O vpc ...).
- Clarify which steps are Windows-only and offer Linux equivalents where possible.
- Move Windows-specific instructions (Hyper-V, PowerShell) to a dedicated section or appendix, and prioritize Linux-native workflows in the main guide.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. However, the PowerShell example is given equal prominence to the CLI example, despite PowerShell being primarily a Windows-centric tool. There is no explicit mention of Linux-specific tools or shell environments (e.g., Bash), and the CLI example is not clearly labeled as suitable for Linux/macOS users. The PowerShell section may create friction for Linux/macOS users, as it is less relevant to their platforms.
Recommendations
- Clarify that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
- Label the PowerShell section as primarily for Windows users.
- Consider providing Bash shell examples or explicitly stating that Azure CLI works in Bash on Linux/macOS.
- Ensure that CLI examples are shown first, as they are more universally applicable.
Virtual Machines
Create a VM from a generalized image in a gallery
...icles/virtual-machines/vm-generalized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from generalized images in a gallery. However, PowerShell examples are exclusively shown using Windows VM configuration (Set-AzVMOperatingSystem -Windows), and the full parameter set for PowerShell is Windows-specific. In contrast, CLI examples default to Linux VM creation, with a brief note on how to switch to password authentication for Windows or Linux. The PowerShell tab is always present and detailed, but does not show how to create a Linux VM using PowerShell. Additionally, in the REST examples, both Linux and Windows VM creation are shown, but the PowerShell section is Windows-centric. The ordering of examples sometimes places Windows (PowerShell) before Linux (CLI), and the PowerShell examples do not provide parity for Linux users.
Recommendations
- Add PowerShell examples for creating Linux VMs, including the use of Set-AzVMOperatingSystem -Linux and SSH key authentication.
- Clarify in PowerShell sections that both Windows and Linux VMs can be created, and provide explicit instructions for both.
- Ensure that CLI and PowerShell examples are presented with equal detail for both OS types.
- Consider alternating or grouping examples by OS type, rather than by tool, to avoid implicit prioritization.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides detailed PowerShell examples and explanations for resizing Azure VMs, including both general and availability set scenarios, before presenting Azure CLI and Terraform options. The PowerShell sections are more extensive and include local usage and authentication steps, which are Windows-centric. The Terraform example references only a Windows VM quickstart, and there is no explicit Linux-focused example or mention of Linux-specific considerations. While the CLI examples are cross-platform, the overall structure and example selection favor Windows users.
Recommendations
- Add explicit Linux-focused examples, especially in the Terraform section (e.g., link to or show an azurerm_linux_virtual_machine block and a Linux quickstart).
- Balance the PowerShell and CLI sections in terms of detail and explanation, ensuring CLI (which is cross-platform) is not treated as secondary.
- In the Terraform section, provide both Windows and Linux resource block examples or link to both quickstarts.
- Where possible, clarify that CLI commands work on all platforms and highlight any OS-specific considerations.
- Consider presenting CLI examples before PowerShell, as CLI is cross-platform and PowerShell is primarily Windows-focused (though available on Linux, it is less common there).
Virtual Machines
Deploy a Trusted Launch VM
...ain/articles/virtual-machines/trusted-launch-portal.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation covers both Linux and Windows VM scenarios for Trusted Launch, but PowerShell examples are exclusively Windows-focused and provided in greater detail than Linux equivalents. In several sections, Windows-specific parameters and images are shown first or exclusively in PowerShell, while CLI examples are Linux-centric. Some PowerShell snippets lack Linux parity, and Windows terminology is used in places where Linux alternatives could be clarified.
Recommendations
- Add PowerShell examples for Linux VM deployment, including specifying Linux images and OS types.
- Ensure PowerShell snippets demonstrate both Windows and Linux VM creation, mirroring the CLI approach.
- Where possible, clarify parameters that differ between Windows and Linux (e.g., OS-specific flags, credential handling).
- In PowerShell sections, provide Linux image references and instructions for Linux VM configuration.
- Review ordering: avoid always showing Windows examples first in PowerShell, and balance with Linux examples.
Virtual Machines
Create a VM from a specialized image version
...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from specialized images. However, PowerShell examples are notably more detailed, including extensive networking and VM configuration steps, while CLI examples are more concise. PowerShell is a Windows-centric tool, and its prominence and depth in the documentation may create friction for Linux/macOS users. Additionally, in several sections, PowerShell examples are presented immediately after CLI, sometimes with more explanation and context, which could be perceived as Windows-first bias.
Recommendations
- Expand Azure CLI examples to include more detailed steps, such as networking and VM configuration, to match the depth of PowerShell examples.
- Explicitly mention that Azure CLI is cross-platform and encourage its use for Linux/macOS users.
- Consider providing Bash shell script examples for common tasks, especially for Linux users.
- Ensure that CLI and PowerShell examples are equally detailed and placed in parallel, rather than PowerShell being more comprehensive.
- Add a brief note clarifying that PowerShell examples are primarily for Windows users, while CLI is suitable for all platforms.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation, while focused on Ubuntu Linux VHDs, repeatedly references Windows-specific tools and workflows (notably Hyper-V and PowerShell's Convert-VHD) as primary or sole options for creating and converting VHDs. Windows/Hyper-V steps are described in detail, with Linux-native alternatives either missing or not given equal prominence. This creates friction for Linux/macOS users who may not have access to Hyper-V or PowerShell.
Recommendations
- Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, KVM).
- Provide parity examples for extracting and manipulating VHDs on Linux/macOS, not just Windows/WSL.
- Mention cross-platform alternatives before or alongside Windows tools, rather than after.
- Clarify which steps are Windows-specific and offer Linux/macOS equivalents wherever possible.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page provides detailed PowerShell examples for resizing Azure VMs, including multiple scripts and explanations. Azure CLI and Terraform examples are also present, but PowerShell (a Windows-centric tool) is given more prominence, detail, and appears before CLI examples. There are no explicit Linux shell (bash) or macOS-specific instructions, and the Terraform example references a Windows VM quickstart. The page does not provide parity for Linux users in terms of example scripts or guidance.
Recommendations
- Add bash shell examples for resizing VMs using Azure CLI, explicitly noting compatibility with Linux/macOS terminals.
- Provide Terraform sample code for azurerm_linux_virtual_machine alongside the Windows example.
- Ensure CLI instructions are as detailed as PowerShell, including explanations for Linux/macOS users.
- Clarify that PowerShell examples can be run cross-platform (via Azure Cloud Shell), but also provide native bash alternatives.
- Reference Linux VM quickstart documentation in the Terraform section.
Virtual Machines
Deploy a Trusted Launch VM
...ain/articles/virtual-machines/trusted-launch-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation covers both Linux and Windows VM deployment with Trusted Launch, but there are signs of Windows bias. PowerShell examples are exclusively for Windows, and Windows-specific parameters (e.g., OS type, image publisher) are used in PowerShell sections without Linux equivalents. In some sections, Windows examples or terminology appear first or are more detailed. Linux-specific PowerShell examples are missing, and some PowerShell snippets default to Windows OS, even when the CLI examples use Linux images. However, Azure CLI and template sections provide Linux parity.
Recommendations
- Add PowerShell examples for Linux Trusted Launch VMs, including Linux-specific parameters and images.
- Ensure PowerShell snippets include both Windows and Linux variants, or clarify OS-specific applicability.
- In PowerShell image definition examples, use Linux OS type and images alongside Windows examples.
- Review ordering of examples to avoid consistently placing Windows first.
- Add clarifying notes where PowerShell is Windows-only, and suggest CLI or template for Linux users.
Virtual Machines
Create a VM from a specialized image version
...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from specialized images, but the PowerShell examples are significantly more detailed and complex, including full networking setup, while CLI examples are minimal. PowerShell is a Windows-centric tool, and its prominence and depth may create friction for Linux/macOS users. Additionally, PowerShell examples are consistently shown after CLI, but the CLI examples are less comprehensive. No Linux-specific tools or shell examples (e.g., Bash scripting) are provided, and the documentation does not mention cross-platform alternatives for PowerShell tasks.
Recommendations
- Expand Azure CLI examples to include full VM/network setup, matching the detail of PowerShell examples.
- Add Bash shell scripting examples for Linux/macOS users, especially for tasks like network configuration.
- Clarify that PowerShell examples are primarily for Windows users and suggest CLI or Bash for Linux/macOS.
- Ensure CLI examples are as comprehensive as PowerShell, covering all steps needed for VM creation.
- Consider referencing cross-platform tools or workflows where possible.
Virtual Machines
Create a VM from a generalized image in a gallery
...icles/virtual-machines/vm-generalized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from generalized images in a gallery. However, PowerShell examples are heavily focused on Windows-specific patterns (e.g., Set-AzVMOperatingSystem -Windows), and Windows VM creation steps are often shown or implied first in PowerShell sections. Linux parity is generally maintained in CLI and REST examples, but PowerShell sections default to Windows, and Linux-specific PowerShell instructions are missing.
Recommendations
- Add explicit PowerShell examples for creating Linux VMs, including Set-AzVMOperatingSystem -Linux usage and SSH authentication.
- In PowerShell sections, clarify when examples are Windows-specific and provide Linux alternatives.
- Ensure parity in PowerShell instructions for both OS types, similar to the CLI and REST sections.
- Consider showing Linux examples first or equally in PowerShell sections, as is done in CLI.
- Add notes or links to Linux PowerShell guidance where only Windows is shown.
Virtual Machines
Deploy a Trusted Launch VM
...ain/articles/virtual-machines/trusted-launch-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Linux and Windows VMs for Trusted Launch and provides parity in Azure Portal, CLI, and template instructions. However, PowerShell examples are exclusively Windows-focused, and Windows-specific parameters and patterns are shown first in several places. Linux PowerShell usage is not addressed, and PowerShell sections do not mention Linux VM creation, which may create friction for Linux users who prefer PowerShell or need parity in scripting.
Recommendations
- Add PowerShell examples for Linux Trusted Launch VM deployment, including Linux image parameters and admin credential patterns.
- In PowerShell sections, clarify which examples are for Windows and provide equivalent Linux VM creation steps.
- Where possible, present CLI and template examples for both Linux and Windows side-by-side, or clarify applicability.
- Review ordering so that Linux and Windows examples are presented with equal prominence, especially in scripting sections.
Virtual Machines
Create a VM from a specialized image version
...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from specialized images, but the PowerShell examples are extensive and detailed, while the CLI examples are more concise. The PowerShell examples use Windows-centric constructs (e.g., New-AzNetworkSecurityRuleConfig for RDP port 3389), and the CLI and PowerShell tabs are presented in parallel, but PowerShell scripts are much longer and more prominent. There are no Linux shell (bash) script equivalents for the detailed resource creation steps, and the PowerShell examples assume a Windows environment. The documentation does not provide parity for Linux users who may prefer bash scripting or native Linux tools for automation.
Recommendations
- Add detailed bash shell script examples for resource creation, matching the depth of the PowerShell examples.
- Clarify that PowerShell examples can be run cross-platform (if true), or provide explicit instructions for Linux/macOS users.
- When showing network security rules, include examples for both SSH (port 22) and RDP (port 3389), and explain their relevance for Linux and Windows VMs.
- Ensure that CLI and shell examples cover all steps shown in PowerShell, including network setup and VM configuration.
- Consider presenting CLI/bash examples before or alongside PowerShell to avoid Windows-first perception.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation is focused on Linux, but several sections show Windows bias. PowerShell deployment examples are presented before Azure CLI, and troubleshooting instructions reference PowerShell first. There are no direct examples of using native Linux tools (e.g., Bash, cloud-init, or ARM templates via Linux shell), and the CLI examples use backticks (`) for line continuation, which is a Windows convention. The documentation does not provide explicit Linux shell command examples for deploying or troubleshooting the extension, nor does it discuss Linux-native automation approaches.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred on Linux.
- Use Bash-style line continuation (\) in CLI examples, not backticks (`), to match Linux shell conventions.
- Add explicit Bash deployment examples (e.g., using az CLI from Linux shell).
- Include troubleshooting steps using Linux tools (e.g., journalctl, systemctl, tail) to view logs and service status.
- Reference Linux-native automation methods (cloud-init, Ansible, etc.) for extension deployment.
- Clarify that PowerShell examples are optional and primarily for Windows users.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation, while focused on Ubuntu Linux, repeatedly references Windows tools (notably Hyper-V and PowerShell's Convert-VHD) as the primary or only method for creating and converting VHDs. Linux-native alternatives for VHD creation and conversion (such as qemu-img or VBoxManage) are not mentioned, and the workflow assumes access to Hyper-V/Windows for critical steps. This creates friction for Linux/macOS users and may block those without Windows access.
Recommendations
- Provide Linux-native instructions for creating and converting VHDs (e.g., using qemu-img, VBoxManage, or other open-source tools).
- List Linux and cross-platform tools before or alongside Windows/Hyper-V options.
- Include example commands for VHD conversion on Linux/macOS.
- Clarify which steps require Windows/Hyper-V and offer alternatives where possible.
- Consider adding a table comparing tool options for each OS.