Virtual Machines
1073
Total Pages
1027
Linux-Friendly Pages
46
Pages with Bias
4.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
284 issues found
Showing 76-100 of 284 flagged pages
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 significantly more detailed and complex, including full network setup and VM configuration. The CLI examples are much simpler and do not cover equivalent advanced scenarios. PowerShell is a Windows-centric tool, and the lack of parity in example depth and coverage creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before CLI in some sections, and there are no Bash or Linux-native scripting examples for advanced scenarios.
Recommendations
- Expand Azure CLI examples to include full VM creation workflows, including network configuration, to match the detail provided in PowerShell examples.
- Add Bash/Linux shell script examples for advanced scenarios, especially for users who prefer or require Linux-native tooling.
- Ensure CLI examples are presented before or alongside PowerShell examples to avoid implicit prioritization of Windows tooling.
- Explicitly note that PowerShell examples are primarily for Windows users, and provide links to equivalent Linux/macOS guidance where possible.
Create Pull Request
Virtual Machines
Share VM images in a compute gallery
...in/articles/virtual-machines/shared-image-galleries.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation is intended for both Linux and Windows VM images, but there is a notable Windows bias in several areas. PowerShell examples are given equal or greater prominence than Azure CLI, and in some cases, only PowerShell is referenced for certain tasks (e.g., sharing images across tenants). Windows/PowerShell links and terminology often appear first or exclusively, while Linux/Bash equivalents are less emphasized or missing. Some references and examples (such as uploading VHDs) do link to both Windows and Linux guides, but overall, Windows tooling and patterns are more visible.
Recommendations
- Ensure that every PowerShell example is paired with an Azure CLI (Bash) example, especially for sharing and management tasks.
- When referencing external guides or examples, always provide both Windows and Linux links side-by-side.
- In lists or tables, alternate or randomize the order of Windows and Linux references to avoid always listing Windows first.
- Expand troubleshooting and FAQ sections to explicitly mention Linux/Bash commands and common issues.
- Review all cross-references to ensure Linux parity in linked documentation.
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 an Azure Compute Gallery. However, the PowerShell examples are exclusively for Windows, with all VM creation commands using Set-AzVMOperatingSystem -Windows and prompting for Windows credentials. There are no PowerShell examples for Linux VM creation, nor is there guidance for using PowerShell to deploy Linux VMs. In contrast, the CLI examples default to Linux VM creation with SSH keys, but do mention how to adapt for Windows. The PowerShell sections are Windows-centric and do not offer Linux parity.
Recommendations
- Add PowerShell examples for creating Linux VMs, using Set-AzVMOperatingSystem -Linux and appropriate credential handling.
- Include a note in PowerShell sections explaining how to adapt the examples for Linux VMs.
- Ensure both CLI and PowerShell sections provide parity in Linux and Windows VM creation instructions.
- Consider showing Linux examples first or side-by-side with Windows examples in PowerShell 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 significantly more detailed and complex, including full network setup and VM configuration, while CLI examples are much simpler. PowerShell is a Windows-centric tool, and the lack of parity in example depth may disadvantage Linux/macOS users. Additionally, PowerShell examples are presented before CLI in some sections, and there are no Bash or Linux-native scripting examples for advanced scenarios.
Recommendations
- Provide equally detailed Bash/Azure CLI examples for advanced VM creation steps, including network setup and configuration, matching the PowerShell depth.
- Clarify that PowerShell examples are primarily for Windows users, and recommend CLI/Bash for Linux/macOS users.
- Ensure that CLI examples are presented before PowerShell, or at least in parallel, to avoid Windows-first perception.
- Consider adding a section or tab for Bash scripts or Linux-native automation for users who do not use PowerShell.
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. While CLI examples are generally cross-platform and default to Linux VM creation (using SSH keys), the PowerShell examples are Windows-centric: they use Windows-specific cmdlets and always configure the VM OS as Windows, with no PowerShell example for Linux VM creation. Additionally, in the PowerShell sections, the VM configuration uses Set-AzVMOperatingSystem -Windows, and there is no mention of how to create a Linux VM using PowerShell. REST and CLI examples do show both Linux and Windows options, but PowerShell guidance is Windows-first and Windows-only.
Recommendations
- Add PowerShell examples for creating Linux VMs, using Set-AzVMOperatingSystem -Linux and appropriate credential handling.
- In PowerShell sections, clarify how to create either Linux or Windows VMs, and provide both code samples.
- In introductory text for PowerShell, mention Linux support and link to Linux-specific guidance if available.
- Review the order of examples to ensure Linux and Windows parity in all scripting sections.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring VM vCore customization. However, the PowerShell example is given equal prominence to the CLI example, and the CLI example uses Ubuntu as the image, but does not show any Linux-specific post-deployment steps or verification. There are no Linux shell (bash) examples for checking the resulting vCPU configuration inside the VM, nor are there instructions for Linux users to verify or interact with the settings post-deployment. The PowerShell section is detailed and uses Windows-centric SDK objects, while Linux users are not given parity in terms of OS-level verification or scripting.
Recommendations
- Add Linux shell (bash) examples for verifying vCPU and SMT status inside the VM after deployment (e.g., using lscpu or /proc/cpuinfo).
- Include a section with Linux-specific post-deployment steps to confirm the configuration.
- Provide parity in scripting examples, such as showing how to automate VM creation and verification using bash scripts.
- Clarify that the Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, and provide links to installation instructions for each OS.
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 significantly more detailed, including full networking setup and resource creation, while CLI examples are minimal. PowerShell is a Windows-centric tool, and its prominence and depth compared to CLI may create friction for Linux/macOS users. Additionally, the PowerShell examples are shown before CLI in some sections, and there are no Bash or Linux shell-specific examples for tasks like networking setup, which are only covered in PowerShell.
Recommendations
- Expand Azure CLI examples to include full resource creation steps (networking, NIC, NSG, etc.) similar to PowerShell, using Bash syntax and variables.
- Ensure CLI examples are as comprehensive as PowerShell, so Linux/macOS users have parity in guidance.
- Consider adding explicit Bash scripts for common Linux/macOS workflows, especially for networking setup.
- Where possible, present CLI examples before PowerShell, or clarify that both are fully supported and provide equivalent coverage.
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
Missing Linux Example
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from generalized images in a gallery. However, PowerShell examples are exclusively Windows-focused, with all sample code using Windows-specific parameters (e.g., Set-AzVMOperatingSystem -Windows), and there are no PowerShell examples for Linux VM creation. Additionally, in the full parameter set, network security rules are configured for RDP (port 3389), which is Windows-specific, and the PowerShell code always prompts for a password (typical for Windows VMs). The CLI examples do mention Linux and SSH keys, but the PowerShell sections do not provide Linux parity. REST and Portal instructions do cover both OS types, but Windows examples and terminology often appear first or exclusively in PowerShell sections.
Recommendations
- Add PowerShell examples for creating Linux VMs, including usage of Set-AzVMOperatingSystem -Linux and SSH key authentication.
- In PowerShell networking examples, include security rules for SSH (port 22) alongside or instead of RDP (port 3389) when demonstrating Linux VM creation.
- Ensure that both CLI and PowerShell tabs consistently show both Linux and Windows scenarios, or clearly indicate when an example is OS-specific.
- In summary and instructional text, avoid implying that PowerShell is only for Windows VM creation; clarify its cross-platform capabilities.
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 significantly more detailed and complex, including full network setup and VM configuration. CLI examples are brief and do not cover equivalent advanced scenarios. PowerShell is a Windows-centric tool, and its prominence and depth here may disadvantage Linux/macOS users. Additionally, PowerShell examples are shown before CLI in some sections, and there are no Bash or Linux-native scripting examples for advanced scenarios.
Recommendations
- Expand Azure CLI examples to include full VM creation workflows, including network setup, matching the detail of PowerShell examples.
- Add Bash shell scripting examples for advanced scenarios, especially for users on Linux/macOS.
- Ensure CLI examples are presented before or alongside PowerShell examples to avoid Windows-first impression.
- Clarify that PowerShell examples are primarily for Windows users, and provide links to equivalent Linux/macOS guidance where possible.
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 Tools
Powershell Heavy
Windows First
Summary
The documentation is focused on Linux, but there are several instances of Windows bias: PowerShell is used heavily for deployment examples, and troubleshooting instructions reference Azure PowerShell before Azure CLI. There are also references to Windows-centric tools and patterns, such as the use of PowerShell and a link to a Windows VM access policy guide. While Azure CLI examples are present, PowerShell is often shown first or exclusively in some troubleshooting sections.
Recommendations
- Prioritize Azure CLI examples over PowerShell, as CLI is cross-platform and native to Linux/macOS.
- Where PowerShell is referenced, always provide an equivalent Azure CLI or Bash example.
- In troubleshooting sections, list Azure CLI commands before PowerShell, or present both together.
- Remove or clarify references to Windows-specific guides (e.g., access policy configuration for Windows VMs) and link to Linux-specific guides where possible.
- Explicitly mention that PowerShell is available on Linux/macOS, or recommend Azure CLI for Linux users.
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, but the PowerShell sections are heavily focused on Windows VM creation. In several PowerShell examples, the use of Set-AzVMOperatingSystem -Windows is shown by default, and there is no equivalent example for Linux VM creation using PowerShell. Additionally, the PowerShell examples consistently show Windows configuration first and exclusively, while CLI examples are more Linux-focused. The REST and Portal sections provide parity for both OS types, but PowerShell users on Linux/macOS may find the guidance lacking.
Recommendations
- Add PowerShell examples for creating Linux VMs, using Set-AzVMOperatingSystem -Linux and appropriate credential handling.
- Include comments or notes in PowerShell sections to clarify how to adapt examples for Linux VMs.
- Where PowerShell is used, show both Windows and Linux VM creation patterns, or link to Linux-specific PowerShell guidance.
- Ensure that introductory text in PowerShell sections does not imply Windows is the only supported OS.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring VM vCore customization, but the PowerShell example is given equal prominence to the CLI example, and there is no explicit Linux/macOS shell example (e.g., Bash). The CLI example uses Ubuntu as the image, but does not show Linux-specific verification steps or mention Linux tooling for post-deployment validation. The PowerShell section is detailed and uses Windows-centric SDK objects, which may be less familiar to Linux/macOS users. The order of examples (CLI, then PowerShell) is reasonable, but the lack of Linux/macOS shell-specific instructions and verification creates mild friction for non-Windows users.
Recommendations
- Add explicit Bash shell examples for Linux/macOS users, especially for post-deployment verification of vCPU and SMT settings.
- Include instructions or commands (e.g., lscpu, nproc) to verify CPU configuration inside a Linux VM after deployment.
- Clarify that Azure CLI works cross-platform and can be run from Linux/macOS, and provide guidance for those environments.
- Consider reducing the emphasis on PowerShell SDK object manipulation, or provide equivalent automation examples for Linux (e.g., using az CLI with JSON templates or shell scripting).
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 notably more detailed, including full network setup and VM configuration, while the CLI examples are more minimal. PowerShell is a Windows-centric tool, and the documentation does not provide equivalent Linux shell scripting examples (e.g., Bash with Azure CLI), nor does it mention Linux-specific patterns or tools. In several sections, PowerShell examples are given with more context and steps than CLI, and the PowerShell tabs appear before Portal tabs, suggesting a Windows-first approach. There are no explicit Linux shell script examples or guidance for Linux/macOS users beyond the CLI commands.
Recommendations
- Provide full Bash shell script examples using Azure CLI, matching the detail level of the PowerShell examples (including network setup, NIC creation, etc.).
- Add notes or guidance for Linux/macOS users regarding environment setup, authentication, and scripting best practices.
- Ensure parity in example complexity and completeness between PowerShell and CLI sections.
- Consider reordering tabs so CLI (cross-platform) examples appear before PowerShell (Windows-centric) examples.
- Explicitly mention that Azure CLI works on Linux/macOS and provide troubleshooting tips for those platforms.
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 significantly more detailed and complex, including full network setup and VM configuration, while the CLI examples are minimal. PowerShell is a Windows-centric tool, and there are no equivalent Bash or Linux shell scripting examples for users who prefer Linux-native automation. Additionally, in several sections, PowerShell examples are presented before CLI, and the CLI examples lack parity in terms of completeness and depth. There are no references to Linux-specific tools or workflows beyond the CLI, and the documentation does not address Linux/macOS users who may wish to automate these tasks outside of PowerShell.
Recommendations
- Provide full Bash/Linux shell script examples that match the depth and completeness of the PowerShell examples, including network resource creation and VM configuration.
- Ensure CLI examples are as detailed as PowerShell examples, covering all necessary steps for both Windows and Linux users.
- Explicitly mention that PowerShell is available cross-platform, but also offer native Linux automation alternatives (e.g., Bash scripts, use of Azure CLI in Linux environments).
- Alternate the order of CLI and PowerShell examples, or present CLI first to reduce Windows-first perception.
- Add notes or links for Linux/macOS users on best practices for scripting and automation in those environments.
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 configuring vCore customization, but the PowerShell section is more detailed and uses direct object manipulation, which is specific to Windows/PowerShell users. The CLI example uses Ubuntu as the image, but there is no explicit Linux shell or scripting example, nor is there parity in depth between PowerShell and CLI sections. The PowerShell example appears after the CLI, but its depth and specificity may create friction for Linux/macOS users seeking equivalent automation or scripting guidance.
Recommendations
- Provide a Bash shell script example for Linux/macOS users that demonstrates the same VM customization using Azure CLI.
- Ensure that CLI and PowerShell sections are equally detailed, including notes on how to script or automate the process on Linux/macOS.
- Clarify that all features are available regardless of guest OS, and explicitly state that the CLI examples are cross-platform.
- If possible, add a note or example for using Azure CLI in PowerShell and Bash to highlight parity.
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 Azure CLI and PowerShell examples for creating VMs from generalized images, but PowerShell coverage is extensive and primarily Windows-focused. In PowerShell sections, Windows VM creation is shown by default, with explicit use of Windows-specific parameters (e.g., Set-AzVMOperatingSystem -Windows). Linux VM creation via PowerShell is not demonstrated, and Windows-centric networking (RDP port rules) is prominent. CLI examples do show Linux VM creation and SSH key usage, but PowerShell examples are Windows-first and lack Linux parity. REST and Portal instructions are generally neutral, but password requirements link to Windows documentation.
Recommendations
- Add PowerShell examples for creating Linux VMs, including use of Set-AzVMOperatingSystem -Linux and SSH key authentication.
- In PowerShell networking examples, show how to allow SSH (port 22) for Linux VMs, not just RDP (port 3389) for Windows.
- Where possible, present Linux and Windows examples side-by-side in PowerShell sections, or clarify how to adapt commands for Linux.
- In password requirement links, reference both Windows and Linux complexity requirements, or clarify when requirements are OS-specific.
Virtual Machines
Enable Trusted launch on existing Gen2 VMs
...rticles/virtual-machines/trusted-launch-existing-vm.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides parity for both Linux and Windows VMs in terms of feature applicability and mentions both RDP (Windows) and SSH (Linux) for VM access. However, there is a notable bias in the scripting and automation sections: PowerShell is given a dedicated tab alongside Azure CLI, and ARM templates, and is used for both Windows and cross-platform scenarios. The PowerShell tab is presented with equal prominence as the CLI, but PowerShell is a Windows-native tool, and the template deployment steps also use PowerShell commands (e.g., New-AzResourceGroupDeployment, Stop-AzVM) rather than cross-platform CLI equivalents. Additionally, the PowerShell tab appears before the Template tab, and PowerShell is used for ARM template deployment, which could create friction for Linux/macOS users. There are no Linux shell (bash) or macOS-specific examples for template deployment, and the documentation assumes familiarity with PowerShell cmdlets for automation.
Recommendations
- Add bash (Azure CLI) examples for ARM template deployment, showing how to deploy templates using az deployment group create.
- Clarify that PowerShell is optional and provide equivalent CLI commands for all automation steps.
- Where PowerShell is used for template deployment, provide a CLI alternative or explicitly note that PowerShell is not required.
- Consider reordering tabs so that cross-platform tools (CLI, Template) appear before PowerShell.
- In the prerequisites and best practices, briefly mention that all steps can be performed from Linux/macOS using Azure CLI or Cloud Shell.
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 significantly more detailed, including full network setup and VM configuration, while the CLI examples are minimal. PowerShell is a Windows-centric tool, and the lack of parity in example depth creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before CLI in some sections, and there are no Bash or Linux shell-specific examples for tasks like network setup, which could be performed using Azure CLI on Linux/macOS.
Recommendations
- Expand Azure CLI examples to include full VM creation workflows, including network resources and configuration, matching the detail of PowerShell examples.
- Add explicit Bash/Linux shell examples for Azure CLI commands, demonstrating usage on Linux/macOS platforms.
- Ensure CLI examples are presented before or alongside PowerShell examples to avoid Windows-first perception.
- Clarify that Azure CLI is cross-platform and recommend it for Linux/macOS users.
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 (cross-platform) and PowerShell examples for creating VMs from generalized images in a gallery. However, the PowerShell examples are heavily Windows-centric, with parameters and configuration steps (e.g., Set-AzVMOperatingSystem -Windows) defaulting to Windows VM creation. There are no equivalent PowerShell examples for Linux VM creation, and the full parameter set for PowerShell only demonstrates Windows VM configuration. Additionally, in PowerShell examples, Windows VM creation is shown first and exclusively, while Linux VM creation is only covered in CLI and REST examples.
Recommendations
- Add PowerShell examples for creating Linux VMs from generalized images, including the use of Set-AzVMOperatingSystem -Linux and SSH key configuration.
- In PowerShell sections, clarify how to adapt the examples for Linux VMs, including differences in credential handling and network security rules (e.g., SSH port 22 instead of RDP port 3389).
- Ensure that both Windows and Linux VM creation are equally represented in all code samples and explanations, especially in PowerShell sections.
- Consider presenting Linux and Windows examples side-by-side or clearly labeling them to improve parity and reduce friction for Linux users.
Virtual Machines
Create a Gallery for Sharing Resources
.../blob/main/articles/virtual-machines/create-gallery.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides examples for creating Azure Compute Galleries using the Portal, Azure CLI, PowerShell, and REST API. While the CLI and REST examples are cross-platform, PowerShell is a Windows-centric tool and is presented as a primary method. Additionally, PowerShell examples are given equal prominence as CLI, and are not marked as Windows-only, which may create friction for Linux/macOS users. The ordering of examples sometimes places PowerShell before REST, and there is no mention of Linux/macOS equivalents to PowerShell.
Recommendations
- Clearly label PowerShell examples as Windows-only or for Windows users.
- Present Azure CLI examples first, as it is cross-platform and preferred for Linux/macOS users.
- Add a note for Linux/macOS users recommending Azure CLI or REST API for automation.
- Consider omitting PowerShell examples or moving them to a dedicated Windows section if parity is not possible.
- Ensure that all code snippets and instructions are platform-neutral unless a platform-specific tool is required.
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 significantly more detailed and complex, including full networking setup, while the CLI examples are minimal. PowerShell is a Windows-centric tool, and the lack of parity in example depth and coverage creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before CLI in some sections, and there are no Bash or Linux-native scripting examples for advanced scenarios.
Recommendations
- Expand Azure CLI examples to include full VM creation workflows, including networking setup, to match the detail provided in PowerShell examples.
- Add Bash shell scripting examples for Linux/macOS users, especially for advanced scenarios.
- Ensure CLI examples are presented before or alongside PowerShell examples to avoid Windows-first perception.
- Explicitly mention cross-platform compatibility for CLI commands and clarify that PowerShell examples are primarily for Windows users.
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 Azure CLI and PowerShell examples for creating VMs from generalized images in an Azure Compute Gallery. However, PowerShell examples are heavily focused on Windows workflows, with parameters and cmdlets (e.g., Set-AzVMOperatingSystem -Windows) that are specific to Windows VM creation. Windows-centric networking (RDP port 3389) and credential prompts are shown by default. In several sections, Windows VM creation is described first or exclusively in PowerShell, while Linux is only mentioned as an alternative in CLI examples. There is limited guidance for Linux VM creation using PowerShell, and the REST and Portal instructions tend to treat Windows and Linux equally, but PowerShell sections are notably Windows-biased.
Recommendations
- Add explicit PowerShell examples for creating Linux VMs, including the use of Set-AzVMOperatingSystem -Linux and SSH key authentication.
- In PowerShell code blocks, clarify which parameters or cmdlets are for Windows and which are for Linux, and provide both variants.
- When showing networking rules, include examples for both SSH (port 22) and RDP (port 3389), not just RDP.
- Ensure that Linux VM creation is described with equal prominence in PowerShell sections, not just as a CLI alternative.
- Consider alternating the order of Windows and Linux examples, or grouping them together for parity.
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 CLI and PowerShell examples for creating VMs from generalized images in an Azure Compute Gallery. However, the PowerShell examples are exclusively for Windows, with commands like Set-AzVMOperatingSystem -Windows and prompts for Windows credentials. There are no PowerShell examples for Linux VM creation, nor guidance for Linux-specific PowerShell usage. In CLI and REST sections, Linux is shown first, but PowerShell sections always default to Windows. This creates friction for Linux users who prefer PowerShell or need parity in automation scripts.
Recommendations
- Add PowerShell examples for creating Linux VMs, using Set-AzVMOperatingSystem -Linux and appropriate credential handling.
- Explicitly mention how to adapt PowerShell scripts for Linux VM creation, including SSH key configuration and Linux-specific parameters.
- Ensure that both Windows and Linux scenarios are covered equally in PowerShell sections, similar to the parity shown in CLI and REST examples.
- Consider adding a table or note summarizing differences in PowerShell usage for Windows vs. Linux VM creation.
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 significantly more detailed and complex, including full network setup and VM configuration. CLI examples are much shorter and do not cover equivalent steps. PowerShell is a Windows-centric tool, and the lack of parity in example depth may disadvantage Linux/macOS users who rely on CLI or other scripting environments. Additionally, PowerShell examples are presented in every scenario, and in some sections, the PowerShell tab appears before CLI, reinforcing a Windows-first pattern. There are no Bash or Linux-native scripting examples for advanced scenarios.
Recommendations
- Expand Azure CLI examples to include full VM creation workflows, including network setup and configuration, matching the detail of PowerShell examples.
- Add Bash shell script examples for Linux/macOS users, especially for advanced scenarios.
- Ensure CLI examples are presented before or alongside PowerShell examples to avoid a Windows-first impression.
- Explicitly mention that PowerShell examples are primarily for Windows users and suggest CLI/Bash alternatives for Linux/macOS users.
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 an Azure Compute Gallery. However, PowerShell examples are heavily Windows-centric, with explicit use of Windows-specific parameters (e.g., Set-AzVMOperatingSystem -Windows) and RDP-related networking rules. In several PowerShell code blocks, only Windows VM creation is shown, while Linux VM creation is not addressed. Additionally, PowerShell examples appear before REST and Portal instructions, and often before CLI in some sections, which may reinforce a Windows-first perspective. CLI and REST examples do include Linux scenarios, but PowerShell is presented as the default for Windows, with no Linux PowerShell parity.
Recommendations
- Add PowerShell examples for creating Linux VMs, using Set-AzVMOperatingSystem -Linux and appropriate credential handling.
- In PowerShell networking examples, show how to open SSH (port 22) for Linux VMs, not just RDP (port 3389) for Windows.
- Clearly label CLI and PowerShell examples as Linux or Windows, and provide both where possible.
- Ensure that Linux scenarios are equally represented in PowerShell sections, not only in CLI/REST.
- Consider alternating the order of CLI and PowerShell tabs, or defaulting to CLI (cross-platform) first.