Bastion
41
Total Pages
10
Linux-Friendly Pages
31
Pages with Bias
75.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
222 issues found
Showing 126-150 of 222 flagged pages
Bastion
Quickstart: Deploy Azure Bastion to a virtual network using an ARM template
.../main/articles/bastion/quickstart-host-arm-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where only Windows VM creation and RDP connection guides are provided, with no mention of Linux VM equivalents or SSH connection instructions. Throughout the main deployment instructions, the examples and screenshots are platform-neutral (focused on the Azure portal and ARM templates), but the follow-up guidance exclusively targets Windows users.
Recommendations
- Add links to Linux VM quickstart guides alongside the Windows VM guide in the 'Next steps' section.
- Include instructions or links for connecting to Linux VMs via SSH using Azure Bastion.
- Ensure parity in post-deployment scenarios by providing both Windows and Linux VM connection examples.
- Review other related documentation to ensure Linux users are equally supported in Bastion deployment and usage workflows.
Create Pull Request
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by requiring the use of RDPβa protocol and toolset traditionally associated with Windowsβto connect to Linux VMs. It mandates installing xrdp on Linux, but does not provide guidance or examples for native Linux remote desktop solutions (e.g., VNC, X11 forwarding) or alternative connection methods. There are no Linux-specific client instructions or parity in tooling, and the documentation does not mention Linux desktop environments or their configuration, focusing solely on adapting Linux to fit a Windows-centric workflow.
Recommendations
- Include alternative Linux-native remote desktop solutions (such as VNC, X11 forwarding, or Wayland RDP support) and provide guidance for their setup.
- Offer examples for connecting from Linux clients, not just via Azure portal, and clarify cross-platform client compatibility.
- Discuss the limitations and trade-offs of using xrdp versus other Linux remote desktop protocols.
- Add troubleshooting and configuration steps for common Linux desktop environments (GNOME, KDE, XFCE) when using RDP.
- Ensure that documentation does not assume RDP is the only or preferred method for Linux remote access, and present alternatives equally.
Bastion
Choose the right Azure Bastion SKU to meet your needs
...s/blob/main/articles/bastion/bastion-sku-comparison.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page presents connectivity options for both Windows and Linux VMs, but consistently lists Windows RDP connectivity before Linux SSH, and Windows RDP before Linux RDP or Windows SSH. There are no explicit command-line examples, but the feature tables and descriptions mention Windows connectivity patterns first and do not provide parity in example order or detail for Linux. No Linux-specific tools or workflows are highlighted, and there is no mention of Linux-native client usage or troubleshooting. The documentation does not show explicit PowerShell bias or exclusive Windows tool usage, but the ordering and lack of Linux-centric examples suggest a subtle Windows-first bias.
Recommendations
- Alternate the order of Windows and Linux connectivity features in tables and descriptions, or present Linux options first in some sections.
- Provide explicit examples or references for connecting to Linux VMs using SSH and RDP, including Linux-native client usage (e.g., OpenSSH, Remmina).
- Include troubleshooting or configuration notes relevant to Linux users, such as SSH key management, file transfer methods, and client compatibility.
- Highlight Linux-specific workflows or tools where appropriate, ensuring parity with Windows examples.
- Ensure that upgrade and deployment instructions mention both Windows and Linux scenarios equally, including command-line and GUI options for both platforms.
Bastion
Quickstart: Use Terraform to deploy Azure Bastion
...b/main/articles/bastion/quickstart-deploy-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell tab is present and receives equal prominence to the CLI tab. There is no explicit mention of Linux-specific tools or shell environments (e.g., Bash), nor are there instructions tailored for Linux users. The CLI examples are cross-platform, but PowerShell is traditionally Windows-centric, and its inclusion without a corresponding Bash or Linux shell example suggests a mild Windows bias.
Recommendations
- Add explicit Bash/Linux shell examples alongside Azure CLI, demonstrating verification steps in a native Linux environment.
- Clarify that Azure CLI commands work cross-platform and provide guidance for Linux/Mac users (e.g., mention running commands in Bash or Zsh).
- If PowerShell is included, consider also including examples for Bash or other popular Linux shells to ensure parity.
- Mention installation and usage differences for CLI and PowerShell on Windows vs. Linux, if relevant.
Bastion
Add scale units for host scaling: Azure portal
...s/blob/main/articles/bastion/configure-host-scaling.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on using the Azure portal for host scaling and mentions PowerShell as an alternative method, which is primarily associated with Windows environments. There are no references to Linux-native tools, CLI examples, or cross-platform command-line instructions, resulting in a Windows-first and missing Linux example bias.
Recommendations
- Include Azure CLI instructions for host scaling, as the CLI is cross-platform and widely used on Linux.
- Provide explicit Linux shell (bash) examples where applicable.
- Mention and link to documentation for configuring host scaling using Linux-compatible tools.
- Ensure parity in example order by listing cross-platform methods (Azure CLI) before or alongside PowerShell.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page provides troubleshooting guidance for Azure Bastion but demonstrates Windows bias by including a dedicated section for Windows domain-joined VM sign-in issues without a corresponding section for Linux VM authentication problems. Additionally, while SSH key generation is shown using a Linux-style command, there are no examples or guidance for Windows users (e.g., using PuTTYgen or Windows OpenSSH). The documentation also references file transfer limitations with PowerShell and the Azure portal but does not mention equivalent Linux tools or workflows.
Recommendations
- Add a troubleshooting section for Linux VM authentication issues, such as common SSH login problems, username formats, and permission errors.
- Provide Windows-specific SSH key generation instructions (e.g., using PuTTYgen or Windows OpenSSH), and clarify cross-platform differences.
- Include Linux equivalents or alternatives when discussing file transfer limitations (e.g., mention scp, sftp, or other native Linux tools).
- Ensure that troubleshooting steps and examples are presented for both Windows and Linux environments, or explicitly state platform applicability.
- Review the order of examples and sections to avoid prioritizing Windows scenarios unless justified by usage statistics.
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing the Azure portal UI and not providing any command-line examples (such as Azure CLI, PowerShell, or Bash). There are no Linux-specific instructions or examples, nor is there mention of how to perform these tasks from a Linux environment or using cross-platform tools. The workflow assumes use of the Azure portal, which is platform-agnostic, but omits parity for users who may prefer or require CLI-based automation, which is common in Linux environments.
Recommendations
- Add Azure CLI examples for all configuration steps, including enabling session recording, configuring storage, and updating SAS URLs.
- Explicitly mention that all steps can be performed via the Azure CLI or ARM templates, and provide links or code snippets.
- Include Bash shell examples for generating SAS tokens and managing storage containers, to complement the portal-based instructions.
- Ensure that any references to PowerShell or Windows tools are balanced with equivalent Linux/Bash/CLI instructions.
- Add a section or callout for Linux users, clarifying that all features are accessible from Linux environments using CLI tools.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page lists new features for Azure Bastion, but the examples and feature descriptions prioritize Windows (RDP) functionality before Linux (SSH). The table lists 'Microsoft Entra ID support for portal (RDP)' before 'Microsoft Entra ID support for portal (SSH)', and the RDP feature links to a Windows-specific page, while the SSH feature links to a Linux-specific page. There are no explicit examples or details for Linux users in the main content, and Windows terminology (RDP) appears first.
Recommendations
- Alternate the order of Windows and Linux features in release tables to avoid implicit prioritization.
- Provide equal detail and visibility for Linux/SSH features as for Windows/RDP features.
- Include explicit Linux examples or use cases in the main documentation, not just in linked pages.
- Avoid listing Windows tools or terminology before their Linux equivalents unless contextually necessary.
- Add a section summarizing parity between Windows and Linux remote access capabilities.
Bastion
Enable remote work by using Azure Bastion
...cs/blob/main/articles/bastion/work-remotely-support.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page mentions PowerShell as a primary configuration method before Azure CLI, which is more commonly used on Linux. There are no explicit Linux-specific examples or references to Linux tools, and the ordering of configuration options (portal, PowerShell, then CLI) suggests a Windows-first perspective.
Recommendations
- Provide explicit Linux-focused examples, such as using SSH from a Linux terminal.
- Mention Azure CLI as a first-class configuration method, possibly listing it before PowerShell.
- Include references to Linux-native tools and workflows for remote access.
- Clarify that Azure Bastion supports both Windows (RDP) and Linux (SSH) VM management equally, with examples for each.
Bastion
Copy and paste to and from a Windows virtual machine: Azure
...cs/blob/main/articles/bastion/bastion-vm-copy-paste.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is exclusively focused on Windows virtual machines, with all instructions, prerequisites, and examples tailored to Windows. There is no mention of Linux VMs, nor any guidance for copy/paste operations on Linux systems. This creates a clear Windows-first bias and omits Linux parity.
Recommendations
- Add equivalent instructions and examples for Linux virtual machines, including any differences in clipboard behavior or limitations.
- Update prerequisites to mention support for both Windows and Linux VMs, or clarify if Linux is not supported.
- Include screenshots and step-by-step guidance for Linux VM sessions via Bastion.
- Explicitly state any feature limitations or differences between Windows and Linux VMs regarding copy/paste functionality.
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal UI and workflow, which is most familiar to Windows users, and by omitting any command-line examples (such as Azure CLI, PowerShell, or Bash) that would be relevant for Linux users or those working in cross-platform environments. There are no Linux-specific instructions or examples, nor is there mention of Linux tools or terminal-based workflows.
Recommendations
- Add Azure CLI and/or Bash examples for all configuration steps, including enabling session recording, configuring storage accounts, and generating SAS tokens.
- Include PowerShell examples if relevant, but ensure parity by providing equivalent Linux/Bash commands.
- Explicitly mention that all steps can be performed from any OS using the Azure CLI or REST API, and provide links or examples.
- Add a section or callout for Linux users, clarifying that the process is not limited to the Azure portal and can be automated or scripted.
- Where UI navigation is described, provide the equivalent CLI commands in parallel.
Bastion
VNet peering and Azure Bastion architecture
.../azure-docs/blob/main/articles/bastion/vnet-peering.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows virtual machines before Linux equivalents in the deployment overview and linking only to Windows VM creation instructions. There are no Linux-specific examples or links, and connection instructions reference Windows RDP before SSH, which is more common for Linux VMs.
Recommendations
- Include parallel instructions and links for creating Linux virtual machines (e.g., /azure/virtual-machines/linux/quick-create-portal) alongside Windows VM references.
- Ensure connection instructions mention both RDP (for Windows) and SSH (for Linux) equally, with appropriate links to documentation for each.
- Add examples or diagrams that explicitly show both Windows and Linux VM scenarios to illustrate cross-platform support.
- Review all references to VM management and ensure Linux parity in guidance, terminology, and resource links.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page describes connecting to a Linux VM using RDP via Azure Bastion, but it exhibits subtle Windows bias. The use of RDP as the primary protocol is traditionally associated with Windows environments, and the documentation does not provide alternative Linux-native remote desktop protocols or mention Linux-specific client tools. There are no examples of connecting from Linux desktops, nor are Linux command-line tools or patterns referenced. The documentation assumes the reader will use RDP (a Windows-centric protocol) and does not discuss alternatives like VNC or SSH with graphical forwarding, which are more common in Linux workflows.
Recommendations
- Include examples of connecting to Linux VMs from Linux desktops, using Linux-native RDP clients (e.g., Remmina, rdesktop, FreeRDP).
- Mention alternative remote desktop protocols (e.g., VNC, X2Go) and explain why RDP is chosen or how it compares.
- Provide command-line instructions for installing and configuring xrdp on popular Linux distributions.
- Clarify whether the Azure portal connection works equally well from Linux, macOS, and Windows clients, and provide parity in instructions.
- Add troubleshooting steps specific to Linux environments (e.g., SELinux, firewall configuration, desktop environment compatibility).
Bastion
Add scale units for host scaling: Azure portal
...s/blob/main/articles/bastion/configure-host-scaling.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the only alternative to the Azure portal for host scaling configuration, without mentioning or providing examples for Linux-based tools (such as Azure CLI or Bash). There are no Linux-specific instructions or parity in command-line tooling.
Recommendations
- Include instructions for configuring host scaling using Azure CLI, which is cross-platform and commonly used on Linux.
- Provide Bash or shell script examples alongside PowerShell examples for command-line operations.
- Explicitly mention Linux/macOS compatibility in alternative configuration methods.
- Ensure that references to command-line tools do not prioritize Windows-specific tools over cross-platform options.
Bastion
Choose the right Azure Bastion SKU to meet your needs
...s/blob/main/articles/bastion/bastion-sku-comparison.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation presents VM connectivity features for both Windows and Linux, but consistently lists Windows RDP connectivity before Linux SSH. It explicitly mentions 'Connect to Windows VM using RDP' and 'Connect to Linux VM using SSH' as baseline features, but only later introduces 'Connect to Linux VM using RDP' and 'Connect to Windows VM using SSH' as advanced features. There are no concrete usage examples, CLI commands, or screenshots, but the ordering and phrasing suggest a Windows-first perspective. There is no explicit mention of Linux tools, patterns, or parity in connection methods, and no Linux-specific configuration or troubleshooting guidance.
Recommendations
- Present Linux and Windows connectivity features in parallel, rather than listing Windows RDP before Linux SSH.
- Add explicit examples for connecting to Linux VMs (e.g., using SSH from Linux/macOS terminals, or using RDP clients on Linux).
- Include Linux-specific configuration notes, troubleshooting tips, and parity checks for advanced features (such as file transfer, session recording, and native client support).
- Where possible, provide cross-platform CLI examples (Azure CLI, Bash, PowerShell) for common tasks.
- Ensure that documentation links and next steps include Linux-focused guides and references.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides step-by-step instructions for deploying Azure Bastion using the Azure portal UI, but does not include any command-line examples. There is no mention of PowerShell or Windows-specific tools, but the absence of CLI instructions (such as Azure CLI or Bash scripts) means Linux users are not given parity in deployment guidance. The documentation implicitly assumes use of the graphical portal, which is more commonly used on Windows, and does not address Linux workflows or automation.
Recommendations
- Add Azure CLI examples for each deployment step to support Linux and cross-platform users.
- Include Bash script snippets for automating Bastion deployment.
- Explicitly mention that all steps can be performed using Azure CLI or ARM templates, and provide links or examples.
- Ensure screenshots and UI instructions are supplemented with equivalent command-line instructions.
- Add a section comparing deployment methods (Portal, PowerShell, Azure CLI) and their platform compatibility.
Bastion
Quickstart: Use Terraform to deploy Azure Bastion
...b/main/articles/bastion/quickstart-deploy-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell tab is present and equally emphasized, which may indicate a slight Windows bias. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is traditionally a Windows-centric tool, though it is now cross-platform. The order of tabs (CLI first, then PowerShell) is neutral, but the inclusion of PowerShell may suggest a tendency to cater to Windows users. No explicit Windows-only tools or patterns are present, and the Terraform workflow itself is cross-platform.
Recommendations
- Add explicit Bash/Linux shell examples for verification steps, especially for users who may not use PowerShell.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary platform-specific notes.
- If PowerShell is included, mention that it is available cross-platform, but also provide parity for native Linux shell users.
- Consider adding a section or tab for Linux/Mac users, showing verification steps using Bash and Azure CLI.
Bastion
Quickstart: Deploy Azure Bastion to a virtual network using an ARM template
.../main/articles/bastion/quickstart-host-arm-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, which exclusively links to Windows VM creation and Windows RDP connection guides, with no mention of Linux VM equivalents. Throughout the page, there are no examples or instructions specific to Linux VMs, nor are Linux connection scenarios referenced. The deployment and validation steps are generic, but the follow-up guidance is Windows-centric.
Recommendations
- Add parallel 'Next steps' links for Linux VM creation and SSH connection via Bastion, such as 'Quickstart: Create a Linux virtual machine in the Azure portal' and 'Connect to a Linux VM using Azure Bastion'.
- Include examples or notes in the deployment and validation sections that highlight Bastion's support for both Windows (RDP) and Linux (SSH) connections.
- Ensure screenshots and example values are not Windows-specific, or provide Linux-relevant examples where appropriate.
- Review and update any referenced guides or templates to include Linux scenarios alongside Windows ones.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a troubleshooting example specifically for Windows domain-joined VMs, detailing how to sign in using domain credentials. There is no equivalent guidance for Linux VMs, such as troubleshooting SSH authentication or domain integration issues. While the SSH key generation example uses a Linux shell, the domain-join troubleshooting is Windows-specific and lacks Linux parity.
Recommendations
- Add troubleshooting guidance for Linux VMs, such as common SSH authentication issues, PAM/SSSD integration, or joining Linux VMs to Active Directory.
- Include examples for both Windows and Linux scenarios when discussing VM connectivity and authentication.
- Ensure that troubleshooting steps for domain-joined VMs cover both Windows and Linux environments, or clearly state platform limitations.
- Provide parity in examples and recommendations for file transfer, including Linux-native tools and workflows.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific features and examples before Linux equivalents. For instance, the copy/paste section links only to 'Copy and paste - Windows VMs' without mentioning Linux VM support or providing equivalent instructions. There is no explicit mention of Linux tools, patterns, or examples in sections where platform parity would be relevant.
Recommendations
- Add explicit references and links to Linux VM documentation for features such as copy/paste, file transfer, and remote audio.
- Ensure examples and instructions are provided for both Windows and Linux VMs in all relevant sections.
- Where features differ between platforms, clarify the differences and provide guidance for Linux users.
- Avoid using Windows-specific terminology or links exclusively; include Linux alternatives side-by-side.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page lists new features for Azure Bastion and highlights Microsoft Entra ID support for RDP (Windows) connections before mentioning SSH (Linux) support. The RDP (Windows) feature is described first in the table, and the link for RDP support points to a Windows-specific page, while the SSH (Linux) support is listed further down. There are no explicit Linux command-line or tool examples, and the documentation does not provide parity in describing Linux workflows or tools alongside Windows ones.
Recommendations
- Ensure that Linux-related features (such as SSH support) are described with equal prominence and detail as Windows (RDP) features.
- Alternate the order of Windows and Linux features in tables and lists to avoid implicit prioritization.
- Include explicit examples and links for Linux workflows and tools wherever Windows-specific ones are mentioned.
- Add a summary section or callout highlighting cross-platform parity and support for both Windows and Linux remote access scenarios.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-vm-copy-paste.md
...cs/blob/main/articles/bastion/bastion-vm-copy-paste.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is focused exclusively on Windows virtual machines, with all instructions, prerequisites, and examples referencing Windows. There is no mention of Linux VMs, nor are there examples or guidance for Linux users. This creates a Windows-first bias and omits Linux parity.
Recommendations
- Add equivalent instructions and examples for Linux virtual machines, including any differences in clipboard behavior or keyboard shortcuts.
- Update prerequisites to mention both Windows and Linux VMs as supported scenarios.
- Clarify any limitations or differences for Linux VMs when using Bastion copy/paste features.
- Include screenshots and step-by-step guidance for Linux desktop environments (e.g., Ubuntu, CentOS) where relevant.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/private-only-deployment.md
.../blob/main/articles/bastion/private-only-deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page provides step-by-step instructions for deploying Azure Bastion in private-only mode exclusively using the Azure Portal GUI, which is most commonly accessed from Windows environments. There are no CLI, PowerShell, or Bash examples, nor any mention of Linux tools or workflows. The absence of cross-platform command-line instructions (such as Azure CLI or Bash) results in a bias towards Windows users and GUI-centric workflows.
Recommendations
- Add Azure CLI examples for each deployment step to support Linux and macOS users.
- Include Bash scripts or command-line instructions for creating and configuring Bastion resources.
- Reference cross-platform tools (e.g., Azure CLI, Terraform) alongside or before GUI instructions.
- Explicitly mention that the Azure Portal is accessible from any OS, and provide parity in instructions for non-Windows environments.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-sku-comparison.md
...s/blob/main/articles/bastion/bastion-sku-comparison.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation presents VM connectivity options with Windows RDP listed before Linux SSH, and includes features like 'Connect to Linux VM using RDP' and 'Connect to Windows VM using SSH' only in higher SKUs, but does not provide any platform-specific usage examples or tooling references. There are no explicit PowerShell or Windows tool biases, but the ordering and feature emphasis subtly prioritize Windows connectivity patterns. There are no Linux-specific examples, CLI commands, or troubleshooting tips, and no mention of Linux tools or workflows beyond basic SSH/RDP support.
Recommendations
- Provide example workflows for both Windows and Linux VM connectivity, including Azure CLI and SSH commands for Linux.
- Ensure feature tables and descriptions alternate or balance Windows and Linux connectivity options, rather than listing Windows first.
- Include troubleshooting tips or best practices for Linux users (e.g., SSH key management, file transfer methods).
- Reference Linux-native tools (such as OpenSSH, scp, sftp) alongside Windows tools where relevant.
- Add links to Linux-specific documentation or guides for Azure Bastion usage.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/troubleshoot.md
.../azure-docs/blob/main/articles/bastion/troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page provides a Windows-specific troubleshooting section (domain-joined VM sign-in) but does not offer equivalent guidance for Linux-based VMs (e.g., troubleshooting SSH sign-in issues, Linux domain integration, or Linux-specific connectivity problems). While an SSH key generation example is given (which is cross-platform), there is no troubleshooting content tailored to Linux VM scenarios, and Windows is mentioned explicitly before Linux in the context of domain-joined VMs.
Recommendations
- Add troubleshooting guidance for Linux VMs, such as common SSH authentication issues, troubleshooting Linux domain-joined VMs (e.g., with LDAP or Kerberos), and Linux-specific connectivity problems.
- Include examples and instructions for both Windows and Linux scenarios in sections that currently only mention Windows (e.g., sign-in issues).
- Ensure parity in troubleshooting steps and terminology for both platforms, such as referencing Linux tools (e.g., journalctl, systemctl, sshd logs) alongside Windows tools.
- Review and update the documentation to mention Linux scenarios wherever Windows is referenced, and avoid presenting Windows solutions first unless contextually justified.