Virtual Machines
2112
Total Pages
1865
Linux-Friendly Pages
247
Pages with Bias
11.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
818 issues found
Showing 626-650 of 818 flagged pages
Virtual Machines
Run scripts in a Linux VM in Azure using action Run Commands
...ob/main/articles/virtual-machines/linux/run-command.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page is focused on Linux VMs and provides Azure CLI examples as the primary method for running scripts. However, it also includes PowerShell examples and references to PowerShell cmdlets, which are traditionally associated with Windows environments. The PowerShell example is given its own section, and PowerShell is mentioned alongside Azure CLI in several places. There is some implicit Windows bias in the inclusion and prominence of PowerShell, and in the troubleshooting section, Windows logging differences are discussed before Linux specifics. However, the page does not provide Windows-only instructions, and Linux users can complete all tasks described.
Recommendations
- Clarify that PowerShell examples are cross-platform and can be run on Linux/macOS as well as Windows.
- Add explicit Bash or shell script examples where appropriate, especially in sections that mention PowerShell.
- Reorder sections so that Azure CLI and Bash/shell examples appear before PowerShell, emphasizing Linux-native tools.
- Minimize references to Windows-specific tools or patterns unless directly relevant to Linux VM management.
- In troubleshooting, lead with Linux log details and only mention Windows differences as a footnote.
Create Pull Request
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
Windows Reference
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides thorough Linux-specific guidance and examples. However, there is a notable Windows bias in the introductory sections: Windows Server 2016 time sync improvements are discussed first and in detail, and multiple references to Windows documentation are provided. No Windows-only tools or examples are present, and all configuration instructions and code samples are Linux-centric. The only PowerShell example is for base64 encoding a cloud-init file, which is relevant for Azure ARM template usage and not for time sync configuration itself.
Recommendations
- Move or minimize Windows Server 2016 details to a background or architecture section, focusing the introduction on Linux VM time sync challenges and solutions.
- Provide parity in references: link to Linux time sync architecture documentation (e.g., chrony, ntpd, systemd-timesyncd) in the introduction, not just Windows resources.
- Clarify that the PowerShell example is for Azure deployment and not for time sync configuration, and offer a Linux shell equivalent for base64 encoding if relevant.
- Ensure that 'Next steps' and reference sections include Linux-focused resources as prominently as Windows ones.
Virtual Machines
Use a template to deploy Azure Spot Virtual Machines
.../main/articles/virtual-machines/linux/spot-template.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides a cross-platform Resource Manager template example for deploying Azure Spot VMs, with explicit mention that it applies to Linux VMs. However, in the 'Next steps' section, the link to the Azure PowerShell method (Windows-centric) is listed before the Azure CLI method (cross-platform), indicating a minor 'windows_first' bias. No PowerShell-heavy content, exclusive Windows tools, or missing Linux examples are present.
Recommendations
- List Azure CLI (cross-platform) before Azure PowerShell in the 'Next steps' section to avoid implying Windows is the primary platform.
- Consider adding explicit instructions or links for Linux/macOS users where relevant, especially in sections referencing command-line tools.
- Maintain parity in example ordering and tool recommendations to ensure equal visibility for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias by consistently listing Windows tools (PowerShell) before Linux equivalents (CLI), referencing Windows-specific documentation and examples first, and occasionally linking to Windows-specific pages before Linux ones. There are also references to 'Scheduled Events for Windows' before Linux, and some examples or instructions are only linked for Windows, with Linux equivalents mentioned as 'corresponding article' rather than directly linked. The CLI (cross-platform) is mentioned, but PowerShell is often listed first, and there are no explicit Linux shell examples or screenshots.
Recommendations
- Alternate the order of CLI and PowerShell mentions, or list CLI (cross-platform) first to reduce perceived Windows-first bias.
- Provide direct links to Linux-specific documentation and examples alongside Windows ones, rather than referencing 'corresponding article'.
- Include explicit Linux shell examples (bash, etc.) where PowerShell examples are given.
- Clarify that the Azure CLI is cross-platform and suitable for Linux/macOS users.
- Add screenshots or step-by-step instructions for Linux environments where applicable.
Virtual Machines
Overview of Maintenance Configurations for Azure virtual machines
...rticles/virtual-machines/maintenance-configurations.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation mentions both Linux and Windows VMs as supported, but there are subtle signs of Windows bias. Azure PowerShell is listed before Azure CLI in management options, and the only sample code linked is a PowerShell-based Azure Functions sample. There is no explicit Linux shell or Bash example, nor are Linux-specific tools or patterns mentioned. The documentation refers to 'Windows Server and Linux machines' together, but examples and tooling references lean toward Windows-first approaches.
Recommendations
- Provide Bash or Linux shell examples alongside PowerShell samples, especially in code sample links.
- List Azure CLI before Azure PowerShell in management options, or present them together to avoid perceived prioritization.
- Include references to Linux-native tools or workflows where relevant, such as cron for scheduling or systemd for service management.
- Add explicit Linux/macOS command-line walkthroughs in the documentation or link to them.
- Ensure parity in troubleshooting and usage guides for Linux environments.
Virtual Machines
Export an image version to a managed disk
...es/virtual-machines/managed-disk-from-image-version.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for exporting an image version to a managed disk. The CLI section is presented first and uses Bash-style syntax, which is cross-platform and suitable for Linux/macOS users. However, the PowerShell section is extensive and detailed, with multiple code blocks and explanations, potentially giving the impression of a Windows-centric approach. There are no Linux-specific tools or shell examples beyond Azure CLI, and PowerShell is presented as an equal alternative, but with more step-by-step detail.
Recommendations
- Ensure parity in the depth of explanation between CLI and PowerShell sections. The CLI section could include more detailed variable assignment and step-by-step breakdowns, matching the PowerShell section.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash, zsh) where appropriate.
- If possible, add a short Linux/macOS-specific note or troubleshooting tip for common issues (e.g., environment variable syntax differences, authentication).
- Consider including a table summarizing cross-platform compatibility of each method.
Virtual Machines
Azure Dedicated Host SKU Retirement Migration Guide
...l-machines/migration/dedicated-host-migration-guide.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides migration steps for Azure Dedicated Host SKUs and includes instructions for stopping and starting VMs using PowerShell, CLI, and Portal. In the 'Stop the VM(s) or virtual machine scale set' and 'Start the VM(s) or virtual machine scale set' sections, PowerShell instructions are listed before CLI instructions, which may subtly prioritize Windows users. However, Azure CLI is cross-platform and no Windows-only tools or patterns are exclusively referenced. No explicit Linux/macOS bias or missing Linux examples are present.
Recommendations
- Alternate the order of PowerShell and CLI instructions, or present CLI instructions first to better reflect cross-platform usage.
- Explicitly mention that Azure CLI works on Linux/macOS and provide links to installation guides for those platforms.
- Add brief notes or examples for common Linux/macOS shell usage where relevant, such as bash scripting for automation.
- Ensure that any referenced scripts or commands are tested and documented for both Windows and Linux environments.
Virtual Machines
Migrate Managed image to Compute gallery
...igration/migration-managed-image-to-compute-gallery.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples, but the PowerShell section is present and detailed, which can indicate a slight bias toward Windows users. The CLI example uses Azure CLI, which is cross-platform, but the PowerShell example is given equal prominence. The portal instructions use Windows-style screenshots and terminology (e.g., backticks in CLI, which is a PowerShell convention), and the page metadata includes 'devx-track-azurepowershell', suggesting a Windows-centric approach. No Linux/macOS-specific shell examples (like bash/zsh) or notes are provided.
Recommendations
- Add explicit bash/zsh shell examples for Linux/macOS users, using appropriate syntax (e.g., line continuation with \ instead of backticks).
- Clarify that Azure CLI commands are cross-platform and provide any Linux/macOS-specific notes if needed.
- Ensure screenshots and UI references are not Windows-specific, or add notes for Linux/macOS users if the experience differs.
- Balance the prominence of PowerShell and CLI sections, possibly listing CLI first as it is more cross-platform.
- Remove or clarify the 'devx-track-azurepowershell' metadata if not relevant to Linux/macOS users.
Virtual Machines
Monitor Azure Virtual Machines
...docs/blob/main/articles/virtual-machines/monitor-vm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. Windows-specific terminology (e.g., 'Windows events', 'IIS logs') is mentioned before Linux equivalents, and some examples (such as log collection levels and Performance Diagnostics) are described in more detail for Windows. There is a lack of concrete Linux command-line or syslog configuration examples, and Windows tools (like IIS logs and Windows event levels) are referenced without similar detail for Linux alternatives. However, Linux is acknowledged throughout, and most features are described as available for both OS types.
Recommendations
- Provide explicit Linux examples alongside Windows ones, such as syslog configuration, log levels, and performance counter collection.
- List Linux equivalents (e.g., Apache/Nginx logs) when mentioning Windows tools like IIS logs.
- Ensure Linux terminology (e.g., syslog, journald, SNMP, application logs) is given equal prominence and detail.
- When describing alerting or diagnostics, include Linux-specific guidance and screenshots.
- Avoid listing Windows examples or tools before Linux ones; present both in parallel or alternate order.
Virtual Machines
Network security group test
...ticles/virtual-machines/network-security-group-test.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a mild Windows bias by using RDP (Remote Desktop Protocol) as the primary example for testing inbound connections, which is specific to Windows VMs. Although both Linux and Windows VM creation links are provided in prerequisites, the step-by-step example focuses solely on RDP and does not offer a Linux-relevant protocol (such as SSH) as an equivalent example. No PowerShell commands or Windows-specific tools are mentioned, and the instructions are primarily portal-based and cross-platform, but the example choice centers Windows use cases.
Recommendations
- Add an SSH example for inbound connection testing to demonstrate Linux VM scenarios (e.g., test port 22/TCP for SSH).
- Explicitly mention that the same steps can be used for Linux VMs by selecting SSH as the service type.
- Consider alternating or presenting both Windows (RDP) and Linux (SSH) examples side-by-side to improve parity.
- Clarify that the portal-based workflow applies equally to both Linux and Windows VMs.
Virtual Machines
Isolated Image Builds for Azure VM Image Builder
...chines/security-isolated-image-builds-image-builder.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. While the main content is platform-neutral and references Linux-specific guides, the only explicit command-line example for registering the Microsoft.ContainerInstance provider is given in both Azure CLI and PowerShell, with PowerShell shown second but not omitted. There are no Linux shell (bash) equivalents for resource provider registration, and no macOS-specific notes. The troubleshooting and template references point to Linux-specific documentation, but the main page does not provide direct Linux command examples or clarify cross-platform differences for key steps.
Recommendations
- Add bash (Linux/macOS) equivalents for all command-line examples, especially for resource provider registration.
- Explicitly state that Azure CLI commands work on Linux/macOS and provide usage context.
- Where PowerShell is mentioned, clarify its availability on Linux/macOS or provide alternatives.
- Ensure that all critical steps (e.g., troubleshooting, template updates) have platform-agnostic or platform-specific instructions as needed.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates mild Windows bias in several areas. Windows terminology and tools (e.g., PowerShell) are mentioned first or exclusively in some sections, such as Key Vault setup and Azure RBAC. The use of Windows-specific technologies (BitLocker) is described before Linux equivalents (dm-crypt), and PowerShell is referenced for Windows VM management, while Linux instructions rely on Azure CLI. Some cross-platform parity is present, but Windows examples and tools are often prioritized or described first.
Recommendations
- Present Linux and Windows examples side-by-side or alternate which platform is described first in each section.
- Explicitly mention Linux tools (e.g., Bash, cloud-init) where relevant, not just Azure CLI.
- Provide PowerShell and CLI commands for both platforms in all sections, ensuring parity.
- Clarify when features/tools are Windows-only and offer Linux alternatives or workarounds.
- Include links to Linux-specific documentation as prominently as Windows links.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is mostly platform-neutral, but there is mild Windows bias in the 'Feature support' section, where nested virtualization is linked to a Windows-specific guide, and in the 'Network' section, where the NTTTCP bandwidth testing tool is referenced without mentioning Linux alternatives. Windows features and tools are mentioned before Linux equivalents, and some links are Windows-centric.
Recommendations
- In the 'Feature support' section, provide links to nested virtualization documentation for Linux (e.g., KVM/QEMU) if relevant, or clarify if only Windows is supported.
- In the 'Network' section, mention Linux-compatible bandwidth testing tools (such as iperf3) alongside NTTTCP, and provide links to their usage.
- Where features are not supported for either OS (e.g., disk encryption), list Linux and Windows together, or clarify parity.
- Review all external links to ensure Linux documentation is referenced where available.
- Explicitly state OS support for features that may differ between Windows and Linux.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is largely platform-neutral, focusing on VM specifications and features. However, there is mild Windows bias in the 'Feature support' section, where 'Nested Virtualization' links to a Windows-specific Hyper-V guide, and in the 'Bandwidth/Throughput testing' section, which references NTTTCP—a Microsoft tool primarily documented for Windows. Linux equivalents or parity are not provided or mentioned first.
Recommendations
- Include links to Linux-specific nested virtualization documentation, such as KVM/QEMU guides for Azure.
- Mention and link to Linux-compatible network throughput testing tools (e.g., iperf, netperf) alongside NTTTCP.
- Where Windows-specific tools or guides are referenced, provide Linux/macOS alternatives or note cross-platform usage.
- Ensure that feature support links (e.g., for nested virtualization) include both Windows and Linux documentation if available.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is mostly platform-neutral, but there is mild Windows bias in the 'Feature Support' section, where nested virtualization is referenced via a Windows/Hyper-V link, and in the networking section, where the bandwidth testing tool NTTTCP is mentioned (a Microsoft/Windows tool) without reference to Linux alternatives. Windows and Linux are both mentioned in support statements, but Windows tools are referenced first and exclusively in some cases.
Recommendations
- When referencing nested virtualization, include links or notes about Linux/KVM alternatives or clarify that the feature is not supported for either OS.
- For bandwidth testing, mention Linux-compatible tools (e.g., iperf, netperf) alongside NTTTCP and provide links to their usage in Azure.
- Ensure that any tooling or example is presented for both Windows and Linux, or clarify platform-specific limitations.
- Review all resource links to ensure parity between Windows and Linux documentation.
Virtual Machines
Create an Azure snapshot of a virtual hard disk
...rticles/virtual-machines/snapshot-copy-managed-disk.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Minor Linux Example
Summary
The documentation provides parity in the main snapshot creation steps for both Windows and Linux users via Azure CLI and PowerShell, but exhibits mild Windows bias: PowerShell (a Windows-centric tool) is presented before Azure CLI, and references to Windows-specific VM creation guides appear before Linux equivalents in the 'Next steps' section. The PowerShell section is more detailed, and links to Windows VM creation guides are more prominent than Linux ones.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
- Ensure equal detail and step-by-step guidance for both PowerShell and CLI sections.
- In 'Next steps', list Linux and Windows VM creation guides side-by-side, or present Linux first for parity.
- Add explicit notes clarifying that both CLI and PowerShell methods work for Linux and Windows VMs.
- Consider adding Bash scripting examples for advanced Linux users.
Virtual Machines
Troubleshoot problems with shared images in Azure
...cles/virtual-machines/troubleshooting-shared-images.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions both Azure CLI and PowerShell for troubleshooting, but lists PowerShell's '-Debug' switch alongside Azure CLI's '--debug' switch in the introductory troubleshooting section. This subtly prioritizes PowerShell (a Windows-centric tool) and does not mention Bash or shell scripting alternatives for Linux/macOS users. No explicit Linux/macOS command examples or troubleshooting patterns are provided, and the only command-line tooling referenced is Azure CLI and PowerShell, with PowerShell mentioned first. However, the error tables and mitigations are platform-neutral and do not show overt Windows bias in the technical content.
Recommendations
- Explicitly mention Bash/shell scripting for Linux/macOS users when discussing troubleshooting commands.
- Provide examples for enabling debug mode in Azure CLI on Linux/macOS (e.g., using Bash).
- If PowerShell is referenced, clarify its cross-platform availability or provide parity examples for Bash.
- Ensure that any command-line instructions are not Windows-centric and are equally applicable to Linux/macOS environments.
- Consider listing Azure CLI (which is cross-platform) before PowerShell, or clarify that both are supported on all OSes.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally addresses both Linux and Windows VMs, but there is a subtle bias in the ordering and example coverage. In the 'Reduce downtime' section, scheduled events for Linux are mentioned after Windows, and there are no concrete examples or Linux-specific tools/patterns provided elsewhere in the document. The page does not provide command-line or tooling examples for either OS, but the ordering and lack of Linux-specific guidance may create minor friction for Linux users.
Recommendations
- Present Linux and Windows examples/tools in parallel or alternate order to avoid implicit prioritization.
- Provide explicit examples or links for both Linux and Windows scheduled events, ensuring parity in detail and guidance.
- Include Linux-specific best practices or references (e.g., handling reboots, using cloud-init, systemd, etc.) where relevant.
- Ensure that any future tooling or command-line instructions include both PowerShell and Bash equivalents.
Virtual Machines
We're retiring Azure unmanaged disks by March 31, 2026
...ticles/virtual-machines/unmanaged-disks-deprecation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by referencing PowerShell as a primary method for querying affected VMs and listing the Windows migration guide before the Linux equivalent. While both Linux and Windows migration guides are linked, the example for querying VMs uses PowerShell and does not mention CLI or Bash alternatives for Linux/macOS users.
Recommendations
- Include Azure CLI and Bash examples for querying affected VMs, alongside PowerShell.
- Present Windows and Linux migration links together or alternate their order to avoid implicit prioritization.
- Explicitly mention cross-platform tools and commands where possible, ensuring parity in instructions for Linux/macOS users.
Virtual Machines
Copy VM restore points to another region
...achines/virtual-machines-copy-restore-points-how-to.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is largely platform-neutral in its API focus, but there is a subtle Windows bias in the ordering and detail of OS-specific configuration examples. Windows configuration fields (e.g., 'windowsConfiguration', 'certificateStoreName on Windows', 'additionalUnattendContent', 'winRM') are described first and in more detail than their Linux equivalents. Linux configuration is present but less detailed and always appears after Windows. There are no PowerShell-only examples or Windows-exclusive tools, but the documentation does not provide parity in example depth for Linux.
Recommendations
- Provide equally detailed examples and explanations for Linux VM configuration fields, such as common SSH settings, cloud-init usage, and Linux-specific restore scenarios.
- Alternate the order of Windows and Linux configuration blocks, or present them side-by-side for parity.
- Add notes or examples for Linux-specific restore point considerations (e.g., file system consistency, SELinux contexts, etc.) where relevant.
- Ensure that any references to certificate stores or VM agent provisioning are matched with Linux equivalents (e.g., trusted CA bundles, waagent settings).
Virtual Machines
Manage, Update, and Delete VM Applications on Azure
...in/articles/virtual-machines/vm-applications-manage.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides parity between Azure CLI and Azure PowerShell for all major tasks, but PowerShell examples are present throughout and sometimes referenced in CLI scripting notes. PowerShell is a Windows-centric tool, and its inclusion and scripting examples may create friction for Linux/macOS users. In one CLI scripting note, PowerShell syntax is used for iterating over VMSS instance IDs, rather than Bash. The documentation does not show explicit Bash scripting examples, and PowerShell is listed as a primary tab in all code sections. However, Azure CLI is cross-platform and is given equal coverage, so Linux users can complete all tasks using CLI or REST. No critical steps are Windows-only, but the presence and occasional preference for PowerShell and Windows scripting patterns indicate a mild Windows bias.
Recommendations
- Replace PowerShell scripting examples in CLI notes with Bash equivalents, especially in sections referencing scripting for VMSS instance status.
- Add explicit Bash scripting examples for tasks that require iteration or advanced scripting, to help Linux/macOS users.
- Clarify in introductory sections that Azure CLI is fully cross-platform and recommend it for Linux/macOS users.
- Consider listing CLI examples before PowerShell in each section to signal platform neutrality.
- Where possible, avoid referencing PowerShell in CLI sections unless strictly necessary.
Virtual Machines
Create a VM from a specialized image version
...icles/virtual-machines/vm-specialized-image-version.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all major workflows, but the PowerShell examples are extensive and use Windows-centric tools and patterns (e.g., New-AzNetworkSecurityRuleConfig for RDP, Windows-style variable naming, and PowerShell-specific networking setup). The PowerShell sections are much longer and more detailed than the CLI sections, which are more cross-platform. There is also a tendency to mention RDP and Windows networking rules before SSH or Linux equivalents. However, the CLI examples are sufficient for Linux/macOS users, and the portal instructions are platform-agnostic.
Recommendations
- Add Bash or shell script examples for network setup and VM creation to match the detail of PowerShell examples.
- Ensure networking examples mention SSH (port 22) before or alongside RDP (port 3389), especially in PowerShell sections.
- Clarify that PowerShell examples are primarily for Windows users and recommend CLI for Linux/macOS users.
- Balance the length and detail of CLI and PowerShell sections to avoid perceived preference.
- Explicitly state cross-platform compatibility for CLI commands at the start of the article.
Virtual Machines
Quickstart: Deploy WebLogic Server on Azure Virtual Machines (VMs)
...kloads/oracle/weblogic-server-azure-virtual-machine.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on deploying WebLogic Server using the Azure portal, with no explicit bias toward Windows or Windows-only tools. However, there is a subtle 'windows_first' bias: authentication defaults to password-based login (common for Windows), and SSH key authentication is referenced only as an alternative with a link out to Linux/macOS instructions. There are no command-line examples (e.g., PowerShell, Bash), and no explicit mention of Windows-specific tools, but Linux parity is not fully addressed in the authentication section. The documentation does not provide Linux-specific deployment or management examples, nor does it clarify OS-specific differences in the workflow.
Recommendations
- Provide explicit instructions and examples for both password and SSH key authentication, including direct steps for Linux/macOS users rather than linking out.
- Clarify any OS-specific differences in the deployment workflow, especially regarding VM management and authentication.
- Include a brief section or note on how the process applies to both Windows and Linux VMs, with screenshots or examples for each where relevant.
- If command-line management is relevant, offer both PowerShell (Windows) and Bash (Linux/macOS) examples.
Virtual Machines
Enable double encryption at rest for managed disks
...hines/disks-enable-double-encryption-at-rest-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides parity between Azure CLI and Azure PowerShell, but PowerShell examples and references are consistently presented after CLI, and there is a notable emphasis on PowerShell in the 'Next steps' section. The 'Next steps' links prioritize PowerShell/Windows content, with Linux/CLI content listed last. There are no Linux-specific shell examples (e.g., bash), but the CLI examples are cross-platform. No critical steps are Windows-only, but the documentation leans toward Windows/PowerShell tools and patterns.
Recommendations
- Ensure that Linux/CLI examples are given equal prominence in 'Next steps' and cross-links, not just at the end.
- Add explicit bash/zsh shell examples where relevant, especially for Linux users, to demonstrate parity.
- Consider alternating the order of CLI and PowerShell sections or providing a clear statement that CLI commands are cross-platform.
- Add a note clarifying that Azure CLI is fully supported on Linux/macOS and is recommended for cross-platform automation.
- Include more Linux/macOS-specific troubleshooting tips or environment notes if applicable.
Virtual Machines
Enable end-to-end encryption using encryption at host - Azure portal - managed disks
...-machines/disks-enable-host-based-encryption-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates mild Windows bias. In sections describing how to find supported VM sizes, the Windows/PowerShell method is listed before the Linux/Azure CLI method. Throughout the prerequisites, PowerShell examples are presented before Azure CLI, and the 'Next steps' link points to a PowerShell-focused sample repository. While Azure CLI examples are provided for Linux users, the ordering and emphasis favor Windows/PowerShell tools and patterns.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present CLI first in Linux-focused documentation.
- Provide direct links to both PowerShell and CLI sample repositories in the 'Next steps' section.
- Explicitly state parity between Windows and Linux throughout, and ensure screenshots and instructions are not Windows-centric.
- Consider adding a note that all steps are equally applicable to Linux/macOS users when using Azure CLI.
- Where possible, include Linux/macOS-specific tips or troubleshooting notes.