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 326-350 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
Minor Windows Tools
Summary
The documentation is primarily focused on Linux, as expected given the page title and content. However, there are some minor signs of Windows bias: PowerShell deployment instructions are presented before Azure CLI instructions in several sections, and troubleshooting commands reference Azure PowerShell first. There are also warnings about PowerShell-specific issues, which may not be relevant to Linux users. All examples, paths, and instructions are Linux-centric, and no Windows-only tools or patterns are promoted for core tasks.
Recommendations
- Present Azure CLI deployment instructions before PowerShell, as CLI is more commonly used on Linux.
- Clarify that PowerShell instructions are for users managing Linux VMs from Windows or cross-platform environments.
- Move PowerShell-specific warnings to a dedicated section for cross-platform administrators.
- Ensure troubleshooting sections highlight Azure CLI commands first, or equally with PowerShell.
- Add a brief note explaining that PowerShell can be used from any OS, but Azure CLI is native to Linux.
Create Pull Request
Virtual Machines
Deprovision or generalize a VM before creating an image
...docs/blob/main/articles/virtual-machines/generalize.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides clear, separate instructions for both Linux and Windows VMs, with Linux steps appearing first. Both platforms are covered with their respective tools (waagent for Linux, Sysprep for Windows), and Azure CLI commands are used for Linux, while PowerShell is used for Windows. There is no evidence of missing Linux examples, Windows-only tools, or Windows-first ordering. The only minor bias is that the Windows section includes a PowerShell example for marking the VM as generalized, while the Linux section uses Azure CLI. However, this reflects typical platform usage rather than bias.
Recommendations
- Consider providing both Azure CLI and PowerShell examples for marking VMs as generalized in both Linux and Windows sections to ensure parity.
- Ensure that any Azure portal steps or cross-platform tools are referenced equally for both OS types.
- Explicitly mention that Azure CLI can be used for Windows VMs as well, if applicable.
Virtual Machines
Create an encrypted image version with customer-managed keys
.../articles/virtual-machines/image-version-encryption.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for creating encrypted image versions with customer-managed keys, but the PowerShell section is presented first and is more detailed. The prerequisites and linked articles also prioritize PowerShell and Windows-specific instructions before CLI or portal options. While Linux is supported and CLI examples are present, the overall structure and example order show a mild Windows bias.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, especially since CLI is cross-platform and preferred by many Linux/macOS users.
- Expand CLI examples to match the detail and complexity of PowerShell examples, ensuring parity in guidance.
- Review linked prerequisite articles to ensure Linux/CLI instructions are not secondary to Windows/PowerShell instructions.
- Explicitly mention that both PowerShell and CLI can be used on any supported OS, and clarify any OS-specific limitations if present.
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
Minor Windows Example
Summary
The documentation provides cross-platform guidance for creating image definitions and versions in Azure Compute Gallery, with CLI, PowerShell, Portal, and REST examples. However, PowerShell examples are Windows-centric by default, and Windows is often mentioned first or as the primary example in PowerShell sections. Linux is referenced in CLI and REST examples, but PowerShell examples default to Windows, and Windows terminology appears before Linux in some cases. Overall, the bias is minor and does not prevent Linux/macOS users from completing tasks.
Recommendations
- In PowerShell sections, provide explicit Linux examples alongside Windows examples, or clarify that PowerShell can be used for Linux images by showing -OsType Linux.
- Ensure that Linux and Windows examples are presented with equal prominence, alternating which OS is shown first in code samples.
- Add notes or links for Linux/macOS users about using Azure CLI or REST as preferred cross-platform tools.
- Where possible, clarify that PowerShell can be used on macOS/Linux via PowerShell Core, and provide guidance for those environments.
Virtual Machines
Azure Disk Encryption scenarios on Linux VMs
...ticles/virtual-machines/linux/disk-encryption-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell examples and terminology (cmdlets, parameters, scripts) are frequently mentioned first or in prominent positions, even though the page is Linux-focused. PowerShell is a Windows-native tool, and while it is available cross-platform, Linux users typically prefer Bash/CLI. Some instructions reference using PowerShell sessions for Azure CLI, which may confuse Linux users. There are no missing Linux examples, but the overall tone and ordering subtly favor Windows/PowerShell patterns.
Recommendations
- Present Azure CLI examples and instructions before PowerShell, as CLI is more native and familiar to Linux users.
- Clarify that Azure CLI can be used in Bash shells and is the recommended tool for Linux environments.
- Avoid suggesting PowerShell sessions for Azure CLI usage; instead, mention Bash or native Linux shells.
- Add explicit notes about cross-platform support for PowerShell, but emphasize CLI for Linux scenarios.
- Review terminology to ensure Linux-native patterns (e.g., Bash, shell scripting) are referenced where appropriate.
Virtual Machines
Expand Virtual Hard Disks on a Linux VM
...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Summary
The documentation is overwhelmingly Linux-focused, with detailed, distribution-specific guidance for Ubuntu, SUSE, and Red Hat (with and without LVM). However, there is a single section at the end that uses PowerShell to check classic VM SKU support for expanding disks without downtime. This section is not accompanied by a Linux/CLI equivalent, which could create friction for Linux users managing classic VM SKUs.
Recommendations
- Provide an Azure CLI or Bash equivalent for checking classic VM SKU support for expanding disks without downtime, or clarify if this check is only possible via PowerShell.
- If PowerShell is required for this specific check, explicitly state its necessity and provide guidance for Linux users on how to install/use Azure PowerShell cross-platform.
- Consider linking to relevant Azure CLI documentation or tools for VM SKU capability queries, if available.
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 comprehensive instructions for creating and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, there is a notable Windows bias: Hyper-V (a Windows-only tool) is presented first in nearly every major section and is referenced as the primary example for VM creation and disk conversion. Windows tools and terminology (e.g., Hyper-V Manager, 'Connect', 'Action > Shut Down') are used before Linux-native alternatives. Linux/KVM/VMware instructions are present and detailed, but Windows/Hyper-V steps are prioritized and sometimes referenced as the canonical workflow.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware) are presented before Hyper-V, or at least in parallel.
- Add a summary table or navigation at the top to help users quickly find instructions for their preferred platform.
- Where possible, avoid referencing Hyper-V steps as canonical (e.g., 'Follow the steps in Hyper-V Manager...') in Linux/KVM/VMware sections; instead, provide full instructions within each section.
- Clarify that Hyper-V is Windows-only and provide explicit guidance for Linux/macOS users on alternative workflows.
- Ensure that conversion steps (e.g., VHD creation) reference both Windows and Linux tools equally, and do not assume Hyper-V as the default.
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 opening sections discuss Windows Server 2016 time sync improvements and reference Windows documentation before Linux-specific information. This creates a minor 'windows_first' bias, as Windows context is presented before Linux details, despite the page being Linux-focused.
Recommendations
- Move Windows Server 2016 context to a background or infrastructure section, clarifying its relevance to Linux VM time sync.
- Begin the documentation with Linux-specific time sync concepts and configuration options.
- Ensure Linux guidance and examples are always presented first and are the primary focus.
- If referencing Windows documentation, clearly explain its relevance to Linux VM users.
Virtual Machines
Verify encryption status for Linux - Azure Disk Encryption
...tual-machines/linux/how-to-verify-encryption-status.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs, but PowerShell examples are presented before Azure CLI, and are more extensive. This creates a minor Windows bias, as PowerShell is less commonly used on Linux compared to Bash/Azure CLI. However, Linux-native CLI and OS-level commands are also included, ensuring Linux users can complete all tasks.
Recommendations
- Present Azure CLI (bash) examples before PowerShell, as CLI is more native to Linux environments.
- Expand Azure CLI sections to match the detail and coverage of PowerShell examples, ensuring parity.
- Clarify that PowerShell examples are optional for Linux users, and highlight Azure CLI as the primary method.
- Consider removing or minimizing PowerShell sections unless there is a clear Linux PowerShell user base.
- Add explicit Bash scripting examples where appropriate, especially for OS-level checks.
Virtual Machines
Best practices for virtual machine cost optimization
...s/virtual-machines/cost-optimization-best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally neutral, but there is a minor bias where Windows-specific guidance appears before Linux equivalents. For example, in the VM selector section, 'Use at least B2 for Windows machines' is mentioned without a corresponding Linux recommendation, and Windows pricing links are listed before Linux. However, Linux is referenced in pricing and VM creation links, and most recommendations are platform-agnostic.
Recommendations
- Ensure Linux-specific guidance is provided alongside Windows guidance, such as recommended B-Series sizes for Linux VMs.
- Present Windows and Linux links in parallel or alphabetical order to avoid perceived prioritization.
- Where possible, clarify when recommendations are platform-specific (e.g., disk types, automation tools) and provide Linux alternatives if applicable.
Virtual Machines
Migrate Standard HDD OS disks by September 08, 2028
...n/articles/virtual-machines/disks-hdd-os-retirement.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation covers both Linux and Windows VMs and provides Azure CLI and PowerShell examples for listing affected disks. However, the PowerShell example is mentioned first, which may indicate a minor 'windows_first' bias. Both Linux (Azure CLI) and Windows (PowerShell) tools are referenced, and no critical steps are Windows-only.
Recommendations
- Present Azure CLI and PowerShell examples side-by-side or list Azure CLI first, as it is cross-platform.
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
- Ensure parity in example depth and clarity for both CLI and PowerShell instructions.
Virtual Machines
Restrict managed disks from being imported or exported
...tual-machines/disks-restrict-import-export-overview.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides links and examples for both Azure CLI (Linux-friendly) and Azure PowerShell (Windows-centric), but PowerShell is mentioned first in several sections and the custom RBAC role creation link points only to a PowerShell-based guide. This creates a mild Windows bias, as Linux users may need to search for CLI or ARM template equivalents.
Recommendations
- Add links or examples for creating custom RBAC roles using Azure CLI or ARM templates, not just PowerShell.
- Ensure that CLI and PowerShell examples are presented together, or alternate which is shown first.
- Clarify that all steps can be performed on Linux/macOS using Azure CLI, and provide explicit guidance or links.
- Where possible, provide parity in documentation for both PowerShell and CLI approaches.
Virtual Machines
Benchmark your application on Azure Disk Storage
...lob/main/articles/virtual-machines/disks-benchmarks.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions both Windows and Linux VMs are supported and provides examples using DiskSpd (Windows) and FIO (Linux). However, DiskSpd (Windows) is mentioned first, and the overall narrative and tool descriptions are slightly Windows-first. There is a mild bias toward Windows tools and patterns, but Linux parity is generally maintained.
Recommendations
- Alternate the order of tool mentions (e.g., mention FIO first in some sections).
- Ensure example commands and tool descriptions for Linux (FIO) are as detailed as those for Windows (DiskSpd).
- Add explicit Linux setup instructions and troubleshooting tips where relevant.
- Consider including a comparison table of DiskSpd and FIO features for both platforms.
Virtual Machines
Secure Azure Managed Disk Downloads and Uploads
...icles/virtual-machines/disks-secure-upload-download.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for key operations, but PowerShell examples are often presented before CLI, and references to PowerShell are slightly more prominent. There is no explicit Linux shell example (e.g., Bash), but Azure CLI is cross-platform and suitable for Linux/macOS users. The 'Next steps' section lists both Linux and Windows guides, but Windows PowerShell is mentioned before Linux CLI in some places.
Recommendations
- Ensure Azure CLI examples are presented before or alongside PowerShell examples, especially since CLI is cross-platform.
- Add explicit Bash or Linux shell examples where relevant, or clarify that Azure CLI commands are suitable for Linux/macOS.
- In 'Next steps', alternate the order of Linux and Windows links, or group them by platform for clarity.
- Where PowerShell is referenced, also mention that Azure CLI is available for Linux/macOS users.
Virtual Machines
Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents."
...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides backup and disaster recovery guidance for Azure Managed Disks on both Linux and Windows VMs. While most sections are platform-neutral, there are a few instances where Windows tools (e.g., Volume Shadow Service) are mentioned before Linux equivalents (e.g., fsfreeze), and Windows-specific examples (SQL Server) are highlighted first. However, Linux options are also described, and the overall guidance is inclusive.
Recommendations
- When mentioning coordinated backup mechanisms, present Linux tools (e.g., fsfreeze) alongside Windows tools (e.g., Volume Shadow Service) with equal prominence.
- Include examples of Linux-based database backup and disaster recovery (e.g., PostgreSQL, MySQL) in the 'Major database solutions' scenario, not just SQL Server and Oracle.
- Ensure that file system consistency and application consistency for Linux VMs are explained in detail, similar to Windows.
- Add links to Linux-specific documentation for backup and disaster recovery where relevant.
Virtual Machines
Support matrix for VM restore points
...n/articles/virtual-machines/concepts-restore-points.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides a support matrix for VM restore points and covers both Windows and Linux operating systems. However, in the 'Operating system support for application consistency' section, Windows is discussed first and in greater detail (listing specific supported versions), while Linux is described more generally and with less granularity. No Windows-specific tools or examples are present, and Linux support is clearly mentioned. The 'Next steps' section references CLI, Azure portal, and PowerShell, but does not show a preference for Windows tools.
Recommendations
- Present Windows and Linux operating system support in parallel, either in a single table or by listing Linux first in some cases.
- Provide a more detailed list of supported Linux distributions (or a summary of key distros) rather than only linking to another page.
- Ensure parity in detail between Windows and Linux sections, such as listing minimum requirements or notable limitations for both.
- If possible, clarify that CLI and PowerShell are cross-platform, and provide links to Linux-specific guidance where relevant.
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 creating Azure Compute Galleries using Portal, Azure CLI, PowerShell, and REST API. While all major cross-platform tools are covered, PowerShell examples are presented alongside CLI and REST, and the PowerShell section is not prioritized over Linux-friendly tools. However, in the 'Create a private gallery' section, the PowerShell example is given its own tab, and is listed after CLI, which is cross-platform. There are no Windows-specific tools or patterns mentioned, and Linux parity is maintained throughout. The only minor bias is that PowerShell is included, but not prioritized, and Windows is not referenced first.
Recommendations
- Ensure that CLI examples are always shown before PowerShell examples, as CLI is cross-platform.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Consider adding Bash shell script examples where relevant, to reinforce Linux parity.
- If possible, clarify that PowerShell examples are for Windows and PowerShell Core users.
Virtual Machines
Server-side encryption of Azure Managed Disks
...blob/main/articles/virtual-machines/disk-encryption.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers server-side encryption for Azure Managed Disks and is intended for both Linux and Windows VMs. While the content is generally cross-platform, there is a consistent pattern of mentioning Windows/PowerShell tools and articles before Linux/CLI equivalents, especially in 'Next steps' and throughout the article. References to PowerShell are often listed first, and some links (e.g., for automatic key rotation) point to Windows/PowerShell-specific guides before Linux alternatives. However, Linux parity is maintained with CLI links and explanations.
Recommendations
- Present Azure CLI (Linux/macOS) and PowerShell (Windows) options together or alternate their order to avoid Windows-first bias.
- Ensure that links to Linux/CLI guides are as prominent as Windows/PowerShell guides, especially in critical sections and 'Next steps'.
- Where possible, provide code snippets or examples for both platforms side-by-side.
- Review references to PowerShell and ensure CLI equivalents are always mentioned and linked in the same context.
Virtual Machines
Share an Azure Managed Disk across VMs
...cs/blob/main/articles/virtual-machines/disks-shared.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides parity between Windows and Linux in terms of supported workloads, cluster managers, and technical concepts. However, in the 'Sample workloads' section, Windows examples and explanations are presented before Linux, and the performance throttling examples also begin with Windows scenarios. All major Linux equivalents are covered, but Windows is consistently shown first.
Recommendations
- Consider alternating the order of Windows and Linux sections, or presenting them in parallel, to avoid implicit prioritization.
- Add explicit Linux sample workload templates or links, similar to the Windows SoFS and SAP templates.
- Ensure performance throttling examples include Linux scenarios with equal detail and prominence.
- Where possible, provide Linux-specific guidance or walkthroughs alongside Windows examples.
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 mostly neutral and focused on Azure Disk Storage features, but there are a few instances where Windows-specific links or tools are mentioned before Linux equivalents, or Windows documentation is referenced without equal Linux coverage. For example, in the 'Live Resize' section, the link is to a Windows-specific article, and in the 'Expand Ultra Disks and Premium SSD v2 without downtime' section, the Windows article is listed before the Linux one. Additionally, the 'LastOwnershipUpdateTime' property section references a Windows-specific documentation link. However, most features are cross-platform and the overall impact is minor.
Recommendations
- Ensure that Linux documentation links are provided alongside Windows links wherever relevant, and consider listing Linux and Windows links together or in a neutral order.
- Where referencing OS-specific guides, clarify that both Windows and Linux are supported and provide links to both.
- Review documentation for any sections where only Windows tools (e.g., PowerShell) are mentioned, and add equivalent Linux (e.g., Bash/Azure CLI) examples if missing.
Virtual Machines
Enable shared disks for Azure Managed Disks
.../main/articles/virtual-machines/disks-shared-enable.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all disk types, but PowerShell examples are consistently present and often shown immediately after Azure CLI. The PowerShell module is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. However, Azure CLI examples are always present and are cross-platform. No Windows-only tools or patterns are mentioned, and Linux support is explicitly stated. There are no missing Linux examples, but PowerShell is given equal or greater prominence than CLI, which is more universal.
Recommendations
- Consider listing Azure CLI examples before PowerShell in all sections, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that Azure CLI is recommended for Linux/macOS users, and PowerShell is primarily for Windows users.
- Add brief notes clarifying that PowerShell examples are for Windows (or for PowerShell Core on Linux/macOS if supported), to avoid confusion.
- Ensure that all critical steps can be completed with Azure CLI, and highlight CLI as the preferred method for Linux/macOS parity.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Linux and Windows VMs, and provides parity in most explanations and examples. However, there are minor signs of Windows bias: Windows-specific details (such as page file placement and Windows Server image sizing) are often mentioned first or in more detail, and PowerShell is listed before CLI in the section about enabling customer managed keys. Linux equivalents are present but sometimes secondary.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, alternating order where possible.
- Provide explicit Linux image size examples alongside Windows ones in all relevant sections.
- When referencing tools, list Azure CLI and PowerShell together, or alternate their order.
- Expand Linux-specific operational details (e.g., swap file placement, common Linux distributions) to match Windows-specific coverage.
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 (especially deployment and troubleshooting), Windows/PowerShell examples are presented first or with more detail. Azure PowerShell is discussed before Azure CLI, and PowerShell deployment examples are more prominent. However, Linux-specific instructions, paths, and CLI examples are present and generally sufficient for Linux users.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred for Linux users.
- Clarify that PowerShell is optional and not required for Linux deployments.
- Add explicit notes or guidance for Linux users where PowerShell is mentioned, indicating that Azure CLI is the recommended tool.
- Ensure troubleshooting instructions include CLI commands before PowerShell.
- Review the order of sections to ensure Linux-centric tools and patterns are prioritized.
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 alongside Azure CLI and ARM template examples. In the deployment section, PowerShell is presented before Azure CLI, which is more native to Linux environments. However, Linux-specific commands and troubleshooting steps are well represented, and the overall guidance is Linux-centric.
Recommendations
- Move Azure CLI examples before PowerShell in all sections, as Azure CLI is more commonly used on Linux.
- Clearly indicate that PowerShell is optional and primarily for users on Windows or cross-platform environments.
- Add Bash shell script examples for extension deployment and troubleshooting, as Bash is the default shell on most Linux distributions.
- Ensure that all troubleshooting and manual steps are available in CLI or Bash, not just PowerShell.
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 are subtle signs of Windows bias. PowerShell examples are given equal prominence to CLI, but the PowerShell example defaults to Windows, while the CLI defaults to Linux. In some sections, Windows-specific terminology (e.g., Sysprep) is mentioned before Linux equivalents. However, Linux is well-represented, and the CLI examples are Linux-first.
Recommendations
- In PowerShell examples, default to Linux OS type or provide both Linux and Windows variants equally.
- Ensure that introductory guidance and examples alternate or equally represent Linux and Windows, rather than defaulting to Windows in PowerShell and Linux in CLI.
- Where Windows-specific terminology is mentioned (e.g., Sysprep), ensure Linux equivalents (e.g., waagent -deprovision) are mentioned with equal prominence.
- Consider adding explicit macOS guidance where relevant, or clarifying that CLI instructions are cross-platform.