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 626-650 of 815 flagged pages
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is focused on Linux, but several sections (notably deployment and troubleshooting) present Azure PowerShell examples before Azure CLI, and provide more detailed PowerShell guidance. This ordering and emphasis may create friction for Linux users, who typically prefer Azure CLI or shell-based workflows. However, all critical tasks are also covered with Azure CLI, and Linux-specific details are well documented.
Recommendations
- Present Azure CLI examples before Azure PowerShell in all sections, as CLI is more native to Linux environments.
- Expand troubleshooting guidance to include more CLI-based commands and workflows, matching the detail given for PowerShell.
- Add explicit notes clarifying that Azure CLI is recommended for Linux users, and PowerShell is optional.
- Ensure all JSON and shell examples use Linux path conventions and syntax (e.g., avoid PowerShell-specific backslashes or quoting).
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux and Windows guidance, but there is a subtle bias in example ordering and tool emphasis. In the PowerShell section, Windows examples are shown first and more prominently, while Linux is mentioned as an alternative. The CLI section is more neutral, but overall, Windows terminology and PowerShell are prioritized in some areas.
Recommendations
- In PowerShell examples, show Linux usage first or provide parallel examples for both OS types.
- Ensure that CLI and PowerShell sections equally highlight Linux and Windows scenarios, including explicit Linux-focused examples.
- Where possible, clarify that both Linux and Windows are supported and provide links to OS-specific guidance directly in each example.
- Review example ordering so Linux and Windows are alternated or presented together, rather than Windows first.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides parity for both Windows and Linux users, with CLI, PowerShell, and ARM template examples. However, in sections where screenshots are shown, Windows installations are presented first, followed by Linux. Additionally, PowerShell examples are included, which are Windows-centric, but CLI and ARM template examples are also provided, ensuring Linux users are not excluded.
Recommendations
- Alternate the order of screenshots and examples so Linux is shown first in some sections.
- Explicitly state that PowerShell is Windows-only and recommend Bash or CLI for Linux users.
- Consider adding Bash script examples for Linux users alongside PowerShell.
- Ensure that all instructions and validation steps are equally clear for both OS types.
Virtual Machines
Create an Azure Image Builder Bicep file or ARM template JSON template
.../articles/virtual-machines/linux/image-builder-json.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides extensive parity between Windows and Linux throughout, with clear sections and examples for both OS types. However, there are minor signs of Windows bias: PowerShell and Windows-specific tools are sometimes mentioned first or exclusively (e.g., PowerShell for checksum generation, WindowsRestart/WindowsUpdate customizers, and PowerShell validator examples), and Windows commands are occasionally shown before Linux equivalents. The guidance for generating SHA256 checksums and some validator examples reference PowerShell cmdlets before Linux commands. Windows customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux equivalents (Shell) are covered but less prominently. Overall, Linux users can complete all tasks, but may need to scroll past Windows-first content or adapt some instructions.
Recommendations
- Ensure Linux and macOS examples (e.g., shell commands, checksum generation) are presented alongside or before Windows/PowerShell equivalents.
- Where PowerShell is referenced for checksum generation, add Linux/macOS alternatives (e.g., sha256sum) in the same prominence.
- In customizer and validator sections, balance the order and detail between Windows and Linux types.
- Highlight Linux-specific customizers and validation options as much as Windows ones.
- Consider a table or side-by-side comparison for OS-specific commands and tools to improve clarity.
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 →
Detected Bias Types
Windows First
Summary
The documentation covers multiple hypervisors (Hyper-V, KVM, VMware, Kickstart) for preparing a Red Hat Enterprise Linux VHD for Azure. However, in several sections, instructions for Hyper-V (a Windows-centric hypervisor) are presented first, and the workflow often references Hyper-V Manager as the primary example, with Linux-native hypervisors (KVM, VMware) following. There are also occasional references to Windows tools (e.g., Hyper-V Manager, convert-vhd cmdlet) before Linux alternatives, but Linux workflows and tools are thoroughly documented. No critical steps are Windows-only, and Linux users can complete all tasks.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before Hyper-V, or at least in parallel tabs.
- When mentioning disk conversion tools, list Linux-native tools (e.g., qemu-img) before Windows tools (e.g., Hyper-V Manager, convert-vhd).
- Clarify that Hyper-V instructions are for users on Windows, and highlight Linux-native workflows for Linux users.
- Consider adding a summary table at the top showing parity between Windows and Linux tools/workflows for each step.
Virtual Machines
Time sync for Linux VMs in Azure
...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority
View Details →
Detected Bias Types
Windows Reference
Powershell Example
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides extensive Linux-specific guidance, commands, and examples. However, there are minor signs of Windows bias: references to Windows Server 2016 time improvements and links to Windows documentation are given in the introduction and 'Next steps' sections, and a PowerShell example is provided for base64 encoding cloud-init (though the main cloud-init example is Linux-centric). No critical Linux examples are missing, and all configuration steps are Linux-oriented.
Recommendations
- Move or minimize Windows Server references to a background section, clarifying their relevance to Linux users.
- Provide a Linux shell command (e.g., `base64 cloud-config.txt`) for base64 encoding cloud-init files, alongside the PowerShell example.
- Ensure 'Next steps' links prioritize Linux resources or clearly indicate Windows-specific links are for background only.
Virtual Machines
Share VM images in a compute gallery
...in/articles/virtual-machines/shared-image-galleries.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation covers both Linux and Windows VM images, but there is evidence of Windows bias. PowerShell examples are given alongside Azure CLI, but PowerShell is a Windows-centric tool. Windows-specific tools and terminology (e.g., Sysprep, Windows upload instructions, Windows image links) are mentioned before or more prominently than Linux equivalents. In some cases, Windows links are listed first or separately, and PowerShell examples are provided even though Linux users typically use Bash/CLI. However, Linux-specific instructions (e.g., waagent for generalization, Linux upload links) are present, and Azure CLI examples are included, mitigating the bias.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, ideally side-by-side or in parallel sections.
- When referencing tools, mention Linux equivalents (e.g., waagent) before or alongside Windows tools (e.g., Sysprep), not after.
- Provide Bash or shell script examples for Linux users where PowerShell is used for Windows.
- When linking to upload instructions or specialized image creation, list Linux and Windows links together, not with Windows first.
- Clarify that Azure CLI is cross-platform and encourage its use for both Linux and Windows users.
Virtual Machines
Time sync for Linux VMs in Azure
...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides comprehensive Linux-specific guidance, commands, and configuration examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific information, which may create a perception of Windows-first bias. All technical guidance, tools, and examples are Linux-centric, with only a minor PowerShell snippet for base64 encoding cloud-init (which is not critical and is contextually relevant for Azure users). There are no missing Linux examples, nor are Windows tools or patterns used for Linux configuration.
Recommendations
- Move or minimize Windows Server 2016 discussion in the introduction, focusing first on Linux-specific time sync mechanisms.
- Add a brief explanation that Windows infrastructure is mentioned only for context, and all configuration guidance is Linux-focused.
- Provide a Linux shell command alternative for base64 encoding cloud-init (e.g., `base64 cloud-config.txt`) alongside the PowerShell example.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. While the CLI example is platform-neutral and suitable for Linux/macOS, the PowerShell example is Windows-specific. The structure presents CLI first, but the PowerShell section is equally prominent and detailed, potentially favoring Windows users. There are no Linux-specific tools or shell examples (e.g., Bash), but the CLI coverage is sufficient for Linux parity.
Recommendations
- Clarify that Azure CLI works on Linux, macOS, and Windows, and is recommended for cross-platform usage.
- Explicitly mention that PowerShell is primarily for Windows users, though PowerShell Core is available cross-platform.
- Add a brief Bash shell example for invoking Azure CLI, or note that Azure CLI commands can be run in any shell.
- Consider adding a note for Linux/macOS users about installing Azure CLI if not already present.
Virtual Machines
NVIDIA GPU Driver Extension - Azure Linux VMs
...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is focused on Linux VM GPU driver installation, but includes PowerShell examples for deploying the extension before Azure CLI examples. PowerShell is primarily a Windows-centric tool, and its inclusion and placement before Azure CLI may create friction for Linux users. However, Linux-specific instructions, examples, and troubleshooting are present throughout, and Azure CLI (cross-platform) is well represented.
Recommendations
- Move Azure CLI examples before PowerShell examples, as CLI is more commonly used on Linux/macOS.
- Clarify that PowerShell is optional and primarily for Windows users, while Azure CLI is recommended for Linux/macOS.
- Add Bash shell script examples for common tasks (e.g., checking extension status, troubleshooting).
- Ensure all screenshots and instructions are Linux-specific (which is already mostly the case).
Virtual Machines
What's new in Azure Disk Storage
...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is primarily a changelog and summary of new features for Azure Disk Storage, which is a cross-platform service. While most content is platform-neutral, there are minor instances of Windows bias: some links and references show Windows documentation or tools first, and in one case, the Azure PowerShell module is mentioned before Azure CLI. However, Linux parity is generally maintained, and critical tasks are not Windows-exclusive.
Recommendations
- Ensure that links to platform-specific guides (e.g., disk expansion) always include both Windows and Linux versions, ideally with equal prominence.
- When referencing Azure management tools, mention Azure CLI and PowerShell together, or list CLI first for cross-platform neutrality.
- Avoid linking to Windows-specific documentation as the primary resource unless the feature is Windows-only; provide Linux/macOS equivalents where applicable.
- Review and update any examples or links that default to Windows paths or tools to ensure Linux/macOS users are equally supported.
Virtual Machines
Instantly access managed disk snapshots
...les/virtual-machines/disks-instant-access-snapshots.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating instant access snapshots, but the PowerShell example is given equal prominence to the CLI example. However, the CLI example (Linux/macOS-friendly) is shown first, and there are no Windows-only tools or patterns mentioned. The documentation avoids Windows-specific terminology and does not reference Windows tools exclusively. Both CLI and PowerShell are cross-platform, but PowerShell is more commonly used on Windows. No Linux-specific commands (e.g., Bash scripts) or explicit Linux/macOS parity notes are present.
Recommendations
- Add explicit notes clarifying that Azure CLI commands work on Linux, macOS, and Windows.
- Consider including Bash shell script examples or referencing Linux/macOS environments where appropriate.
- Mention that PowerShell Core is available cross-platform, but Azure CLI is typically preferred on Linux/macOS.
- Ensure parity in troubleshooting and monitoring examples for both CLI and PowerShell users.
Virtual Machines
Secure Azure Managed Disk Downloads and Uploads
...icles/virtual-machines/disks-secure-upload-download.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both PowerShell and Azure CLI examples for key tasks, but PowerShell (a Windows-centric tool) is presented before Azure CLI in most sections. Portal instructions are also included, but the ordering and prominence of PowerShell may subtly favor Windows users. However, Linux parity is generally maintained, and CLI examples are present. The 'Next steps' section lists Linux and Windows guides separately, showing parity.
Recommendations
- Present Azure CLI and PowerShell examples side-by-side, or alternate their ordering to avoid implicit prioritization.
- Explicitly note that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Where possible, add Bash or shell script examples for Linux users.
- Clarify in each section which tools are cross-platform and which are Windows-specific.
- Consider adding a short statement at the start indicating that all tasks can be completed on Linux/macOS using Azure CLI.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is focused on the Azure Key Vault VM Extension for Linux and provides comprehensive Linux-specific details. However, there is evidence of Windows bias in the deployment sections: PowerShell examples and instructions are presented first and in greater detail than Azure CLI, despite PowerShell being more associated with Windows environments. Additionally, troubleshooting instructions reference Azure PowerShell before Azure CLI, which may create friction for Linux users who typically use CLI tools.
Recommendations
- Present Azure CLI examples and instructions before PowerShell, as CLI is more commonly used on Linux.
- Ensure that all deployment and troubleshooting steps are equally detailed for Azure CLI and PowerShell.
- Clarify that PowerShell can be used cross-platform, but highlight Azure CLI as the primary tool for Linux users.
- Add explicit notes or sections for Linux-native shell usage where relevant.
Virtual Machines
Create an image definition and image version
...s/blob/main/articles/virtual-machines/image-version.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Linux and Windows guidance, but there is a slight bias in the PowerShell section, where Windows is used as the default in examples and Linux is only mentioned as an alternative. Additionally, in the PowerShell tab, the example is for Windows, while in the CLI tab, the example is for Linux. Both platforms are covered, but the PowerShell section leans Windows-first, and there is a slight emphasis on Windows in some explanations.
Recommendations
- In the PowerShell section, provide a Linux example first or present both Linux and Windows examples side by side.
- Clarify in each code example which OS it is targeting, and ensure parity by showing both Linux and Windows variants where applicable.
- Consider adding a note at the start of the PowerShell section to explicitly state that the cmdlets work for both Linux and Windows images, and provide explicit Linux-focused PowerShell examples.
- Review the order of presentation in sections where OS-specific guidance is given to ensure Linux is not always secondary.
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 →
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, the Hyper-V (Windows) workflow is presented first in each major section, and Windows-specific tools (Hyper-V Manager, convert-vhd cmdlet) are mentioned before their Linux equivalents. The Linux/KVM/VMware workflows are present and well-detailed, but Windows tools and patterns are prioritized in ordering and introductory notes.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware) are presented before Hyper-V, or at least provide equal prominence.
- In introductory notes, mention Linux conversion tools (e.g., qemu-img) alongside or before Windows tools (e.g., convert-vhd, Hyper-V Manager).
- Where possible, clarify that all workflows are equally supported and highlight Linux-native approaches for users not on Windows.
- Consider a summary table at the top listing all supported hypervisors and tools, with links to each section, to avoid implicit prioritization.
Virtual Machines
Share VM images in a compute gallery
...in/articles/virtual-machines/shared-image-galleries.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation covers both Linux and Windows VM images, but there are signs of Windows bias. PowerShell examples and references are given alongside Azure CLI, but PowerShell is often presented first or with more detail. Windows-specific tools (Sysprep) are mentioned before Linux equivalents (waagent), and links to Windows upload guides are listed before Linux ones. Some references to Windows-specific pages (e.g., Marketplace images) are more prominent. However, Linux parity is generally maintained, and Linux users can complete all tasks.
Recommendations
- Ensure that Linux and Windows examples are presented with equal prominence, alternating their order where possible.
- Provide Linux-specific CLI and tool references before or alongside Windows/PowerShell equivalents.
- Where PowerShell is referenced, ensure Bash/CLI examples are equally detailed and easy to find.
- Link to Linux upload guides before or alongside Windows guides.
- Review FAQ answers and ensure Linux scenarios are explicitly addressed, not just Windows.
Virtual Machines
Time sync for Linux VMs in Azure
...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides extensive Linux-specific guidance, examples, and tooling. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific details. There are no PowerShell or Windows-only tools used for Linux configuration, except for a single PowerShell command for base64 encoding cloud-init data, which is contextually appropriate for Azure ARM templates and not for VM time sync itself.
Recommendations
- Move the Windows Server 2016 discussion and links to a background or context section, making clear it is for Azure host infrastructure and not directly relevant to Linux VM configuration.
- Add a brief summary at the start clarifying that all configuration steps and examples are Linux-specific.
- If referencing Windows documentation, ensure Linux documentation is referenced with equal prominence and in the same section.
- For the PowerShell base64 example, consider providing a Linux equivalent (e.g., `base64 cloud-config.txt`) for users preparing ARM templates from Linux/macOS environments.
Virtual Machines
Create a Gallery for Sharing Resources
.../blob/main/articles/virtual-machines/create-gallery.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides examples for Azure portal, Azure CLI, PowerShell, and REST API. PowerShell is presented as a distinct example, but it is not prioritized above CLI or REST. However, in the 'Create a private gallery' section, the PowerShell example is shown after the CLI example, and both are given equal prominence. The CLI examples use Bash syntax and variables, which are cross-platform and friendly for Linux/macOS users. There are no Windows-only tools or patterns, and no critical steps are Windows-exclusive. The only minor bias is the inclusion of PowerShell as a separate example, which could be interpreted as slightly favoring Windows users, but this is mitigated by the presence of CLI and REST examples. No Linux/macOS examples are missing, and the CLI is presented before PowerShell.
Recommendations
- Consider explicitly noting that Azure CLI commands work on Linux, macOS, and Windows.
- If possible, add a note clarifying that PowerShell examples are for Windows users, while CLI examples are cross-platform.
- Ensure screenshots and portal instructions do not reference Windows-specific UI elements.
- Maintain the current order (CLI before PowerShell) to minimize perceived Windows bias.
Virtual Machines
Azure VM Extensions and Features for Linux
...articles/virtual-machines/extensions/features-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major tasks, but consistently presents PowerShell examples immediately after CLI, and sometimes with more detailed output formatting. There is minor bias in mentioning PowerShell as a primary tool alongside Azure CLI, despite the Linux focus. However, all examples and instructions are fully applicable to Linux users, and no Windows-specific tools or patterns are prioritized or required.
Recommendations
- Consider presenting Azure CLI examples first in all sections, as CLI is the native cross-platform tool and more relevant for Linux users.
- Where possible, clarify that PowerShell examples are optional for Linux users, and highlight that Azure CLI is the default for Linux environments.
- Ensure that output examples and troubleshooting steps are equally detailed for CLI and PowerShell.
- Add explicit notes that Azure PowerShell can be run on Linux, but Azure CLI is typically preferred for Linux workflows.
Virtual Machines
Qualys Cloud Agent Extension for Azure VMs
...ob/main/articles/virtual-machines/extensions/qualys.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation generally provides parity between Windows and Linux deployment methods, but there is a subtle bias in the prominence of PowerShell (a Windows-centric tool) as a primary automation method, and in some sections, Windows is mentioned before Linux. However, Linux-specific tools (like Ansible) are also referenced, and Linux deployment links are provided alongside Windows equivalents.
Recommendations
- When listing deployment methods or examples, alternate the order of Windows and Linux, or present them together to avoid 'Windows first' bias.
- Clarify that PowerShell Core is cross-platform if recommending it for Linux, or provide Bash/Azure CLI examples for Linux users.
- Expand on Linux-native automation tools (e.g., Bash scripts, Azure CLI, cloud-init) in addition to PowerShell, especially in sections focused on command-line deployment.
- Ensure that all external links for deployment steps are equally available and visible for both Windows and Linux.
- Explicitly mention when a method is equally applicable to both OSes, or provide OS-specific instructions where necessary.
Virtual Machines
Instantly access managed disk snapshots
...les/virtual-machines/disks-instant-access-snapshots.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating instant access snapshots, but the PowerShell example is given equal prominence and appears before the portal example. There is no explicit Linux/macOS bias, but Windows tools (PowerShell) are featured alongside cross-platform CLI. No Linux-specific shell or tooling is referenced, and the CLI examples use Bash syntax, which is cross-platform but most common on Linux/macOS. The ordering of examples (CLI, PowerShell, Portal, ARM template) is neutral, but PowerShell is still a Windows-centric tool.
Recommendations
- Clearly indicate that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
- Consider providing example CLI commands using both Bash and PowerShell syntax, or clarify that Bash is the default for CLI.
- Add a note that Azure PowerShell is available on Linux/macOS, but CLI is recommended for cross-platform use.
- Ensure that CLI examples are shown first and are complete, which is already the case.
- Optionally, add a section for Linux/macOS users highlighting any OS-specific considerations (none appear necessary here).
Virtual Machines
What's new in Azure Disk Storage
...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is primarily a changelog and summary of new features for Azure Disk Storage, which is a cross-platform service. Most content is neutral, but there are minor instances of Windows bias: Windows documentation links are sometimes listed before Linux equivalents, and references to Azure PowerShell are made without equal mention of Linux tools. However, Linux links and parity are generally present, and no critical features are Windows-only.
Recommendations
- When linking to both Windows and Linux documentation, list Linux links first or side-by-side with Windows links to avoid subtle ordering bias.
- Where Azure PowerShell is mentioned, also reference Azure CLI (which is cross-platform) to ensure Linux/macOS users are equally supported.
- Review linked documentation to ensure Linux/macOS parity in examples and instructions.
- Explicitly state cross-platform support in feature descriptions where relevant.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is focused on Linux, but in several sections (e.g., upgrading, troubleshooting, deployment), Windows/PowerShell examples are presented before their Linux/Azure CLI equivalents. The PowerShell deployment section is more detailed and appears before the Azure CLI section, which may create friction for Linux users. Additionally, troubleshooting commands are shown with PowerShell first, even though Azure CLI is more common on Linux.
Recommendations
- Present Azure CLI examples before PowerShell examples in all sections, as CLI is the default for Linux users.
- Ensure troubleshooting commands are shown with Azure CLI first, or provide parity in detail between CLI and PowerShell.
- Clarify that PowerShell is optional and not required for Linux deployments.
- Add explicit notes or guidance for Linux users about which tools are recommended (e.g., Azure CLI).