Bastion

82
Total Pages
52
Linux-Friendly Pages
30
Pages with Bias
36.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

76 issues found
Showing 26-50 of 76 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 →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the 'Next steps' section, where only Windows virtual machine creation and RDP connection guides are linked. There are no equivalent instructions or links for Linux VM creation or SSH connections via Bastion, which are common use cases for Linux/macOS users. The main deployment steps are platform-neutral (using the Azure portal), but the follow-up guidance is Windows-centric.
Recommendations
  • Add 'Next steps' links for Linux VM creation in the Azure portal.
  • Include instructions or links for connecting to Linux VMs via Bastion (SSH).
  • Ensure parity by providing examples and guidance for both Windows and Linux VM scenarios after Bastion deployment.
  • Consider mentioning SSH as an alternative to RDP for Linux/macOS users.
GitHub Create Pull Request
Bastion Create a shareable link for Azure Bastion ...zure-docs/blob/main/articles/bastion/shareable-link.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes using the Azure portal GUI for all tasks and references PowerShell cmdlets for permissions, with no mention of Linux/macOS CLI tools (such as Azure CLI or Bash scripting) or parity for non-Windows environments. There are no examples or instructions for performing these tasks via Linux/macOS-friendly methods, nor is there guidance for users who do not use Windows or PowerShell.
Recommendations
  • Add equivalent Azure CLI (az) commands for creating, viewing, and deleting shareable links, and for managing permissions, alongside PowerShell cmdlets.
  • Explicitly mention that the Azure portal and shareable links are cross-platform and can be accessed from any browser, including on Linux/macOS.
  • Provide screenshots or instructions for Linux/macOS users where relevant, such as using Bash or terminal commands.
  • Clarify whether any features or steps are Windows-specific, and if not, state cross-platform compatibility.
  • Include a section or note for Linux/macOS users about how to perform these tasks without PowerShell.
GitHub Create Pull Request
Bastion About VM connections and features ...Docs/azure-docs/blob/main/articles/bastion/vm-about.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific features and examples before Linux equivalents. For instance, the 'Copy and paste' section links only to 'Copy and paste - Windows VMs,' with no mention of Linux VM support or guidance. There is no explicit coverage of Linux/macOS workflows or examples, and Windows terminology is prioritized.
Recommendations
  • Add equivalent documentation and examples for Linux/macOS VMs, especially for features like copy/paste and file transfer.
  • Ensure links and references include both Windows and Linux scenarios, or clarify platform limitations.
  • Where features are Windows-only, explicitly state this and provide alternative guidance for Linux users.
  • Review referenced articles (e.g., bastion-vm-copy-paste.md) to ensure Linux parity is addressed.
GitHub Create Pull Request
Bastion VNet peering and Azure Bastion architecture .../azure-docs/blob/main/articles/bastion/vnet-peering.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references Windows virtual machines first and links only to the Windows VM creation guide, omitting equivalent Linux VM instructions. The connection example also points to a Windows-specific RDP guide, with no mention of SSH or Linux VM connection patterns. This creates a subtle bias toward Windows users and may cause confusion or extra steps for Linux/macOS users.
Recommendations
  • Include links to both Windows and Linux VM creation guides in the deployment overview.
  • Provide connection instructions/examples for both RDP (Windows) and SSH (Linux/macOS) when describing how to connect to VMs via Azure Bastion.
  • Ensure that references to VM management and connection are platform-neutral or explicitly mention both Windows and Linux scenarios.
GitHub Create Pull Request
Bastion Record Bastion sessions ...e-docs/blob/main/articles/bastion/session-recording.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively describes configuration and usage steps via the Azure portal UI, which is platform-agnostic, but it implicitly assumes users are familiar with Windows-centric Azure workflows. There are no CLI, PowerShell, or Linux/macOS-specific instructions or examples. The absence of Linux CLI (az), Bash, or cross-platform automation examples means Linux/macOS users may find it harder to automate or script these tasks, and may feel the documentation is tailored primarily for Windows users.
Recommendations
  • Add Azure CLI (az) command examples for enabling Bastion session recording, configuring storage containers, and uploading SAS URLs.
  • Include Bash scripting examples for relevant steps, such as generating SAS tokens or managing storage containers.
  • Explicitly mention that all steps can be performed from any OS via the Azure portal, but provide parity for users who prefer command-line or automation workflows.
  • If PowerShell examples are added in the future, ensure equivalent Bash/Azure CLI examples are provided.
GitHub Create Pull Request
Bastion File transfer via native client ...lob/main/articles/bastion/vm-upload-download-native.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by presenting Windows/RDP file transfer instructions first, focusing on the Windows native client (MSTSC) and its copy-paste workflow. Linux/macOS instructions are provided later and rely on SSH/SCP, but lack detailed step-by-step guidance or parity in ease-of-use. Windows tools and patterns (MSTSC, right-click copy/paste) are mentioned exclusively and in more detail than their Linux equivalents.
Recommendations
  • Provide Linux/macOS examples and instructions before or alongside Windows examples.
  • Include detailed step-by-step guidance for Linux/macOS users, such as using native SSH/SCP clients and graphical SFTP tools.
  • Mention and demonstrate equivalent Linux/macOS workflows (e.g., Nautilus, Finder, or command-line SCP/SFTP) for file transfer.
  • Avoid assuming Windows as the default platform; use neutral language and structure.
  • Add troubleshooting tips specific to Linux/macOS environments.
GitHub Create Pull Request
Bastion File transfer via native client ...lob/main/articles/bastion/vm-upload-download-native.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page presents Windows/RDP file transfer instructions first, with detailed steps for the Windows native client and MSTSC. Linux/macOS workflows are described later and less prominently, with a brief mention of SCP for SSH file transfer. Windows tools and patterns (MSTSC, right-click Copy/Paste) are emphasized, while Linux/macOS equivalents are not shown in detail.
Recommendations
  • Provide explicit Linux/macOS examples for file transfer, such as step-by-step SCP usage and GUI client instructions (e.g., Remmina, Terminal).
  • Include screenshots or detailed instructions for Linux/macOS workflows, matching the depth of Windows sections.
  • Present Linux/macOS instructions before or alongside Windows instructions to avoid 'Windows first' bias.
  • Mention cross-platform tools and clarify parity in supported features.
GitHub Create Pull Request
Bastion Deploy Bastion:PowerShell ...ain/articles/bastion/bastion-create-host-powershell.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page is heavily focused on deploying Azure Bastion using PowerShell, with all code examples and step-by-step instructions provided exclusively for PowerShell. There are no equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI), and the guidance assumes use of Windows-centric tools. References to creating VMs also link to Windows VM creation guides first, further reinforcing a Windows-first approach.
Recommendations
  • Add Azure CLI (Bash) examples alongside PowerShell for all deployment steps.
  • Explicitly mention cross-platform compatibility and provide guidance for Linux/macOS users.
  • Ensure links to VM creation include both Windows and Linux quickstart guides.
  • Consider reordering or parallelizing examples so Linux/Bash instructions are not secondary.
  • Clarify that Azure PowerShell can be used on Linux/macOS, but provide CLI alternatives for users who prefer native tools.
GitHub Create Pull Request
Bastion Connect to a Linux VM using SSH .../main/articles/bastion/bastion-connect-vm-ssh-linux.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page is generally Linux-focused, as it describes connecting to Linux VMs via SSH. However, there is a notable bias in the sections describing how to create and manage Azure Key Vault secrets: links and instructions reference PowerShell and Azure CLI, but do not provide explicit Linux/macOS shell examples or guidance. The 'quick-create-powershell' link and repeated mention of PowerShell as the recommended method for storing SSH keys in Key Vault suggest a Windows-first approach, and there is no parity for Linux users (e.g., Bash, shell, or cross-platform CLI examples).
Recommendations
  • Add explicit Bash/shell/Azure CLI examples for creating and managing Key Vault secrets, especially for storing SSH keys.
  • Provide links to Linux/macOS-specific documentation or clarify that Azure CLI commands work cross-platform.
  • Avoid referencing PowerShell as the default method; present Azure CLI and PowerShell equally, or lead with CLI for cross-platform parity.
  • Clarify any platform-specific formatting issues when storing secrets, and provide troubleshooting steps for Linux/macOS users.
GitHub Create Pull Request
Bastion Working with VMs and NSGs in Azure Bastion ...s/azure-docs/blob/main/articles/bastion/bastion-nsg.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only a PowerShell script for creating NSG rules, with no equivalent Azure CLI, Bash, or Linux/macOS-friendly example. PowerShell is a Windows-centric tool, and its exclusive use here creates friction for Linux/macOS users who typically use Azure CLI or REST API. No mention is made of cross-platform alternatives, and the script is presented as the sole automation method.
Recommendations
  • Add equivalent Azure CLI and/or Bash examples for creating NSG rules, ensuring Linux/macOS users can follow along without needing PowerShell.
  • Explicitly mention that PowerShell is one of several options, and link to cross-platform tooling documentation.
  • Consider providing REST API or ARM template examples for full platform neutrality.
  • Reorder or parallelize examples so that Windows and Linux/macOS methods are presented equally.
GitHub Create Pull Request
Bastion About Azure Bastion configuration settings ...s/blob/main/articles/bastion/configuration-settings.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently lists Azure PowerShell as a configuration method alongside Azure portal and Azure CLI, but provides direct links and parameter examples only for PowerShell and CLI, with no mention of Linux/macOS-specific tools or shell patterns. In several tables, PowerShell is listed before CLI, and no Bash or Linux-native scripting examples are provided. There is a notable absence of explicit Linux/macOS guidance, which may create friction for non-Windows users.
Recommendations
  • Add explicit Bash and Linux/macOS shell examples for each configuration step, especially for Azure CLI usage.
  • Ensure CLI examples use cross-platform syntax and clarify that Azure CLI works on Linux/macOS.
  • Where PowerShell is referenced, also provide equivalent Bash/Unix shell commands and note platform compatibility.
  • Consider listing Azure CLI before PowerShell in tables to reflect its cross-platform nature.
  • Add a section or note highlighting Linux/macOS usage and any platform-specific considerations.
GitHub Create Pull Request
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 →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where only Windows virtual machine creation and Windows RDP connection guides are linked. There are no Linux/macOS-specific examples, nor are Linux SSH connection instructions provided. The main deployment instructions are platform-neutral (using the Azure portal), but the follow-up guidance assumes Windows usage.
Recommendations
  • Add links to equivalent Linux VM quickstart guides (e.g., 'Quickstart: Create a Linux virtual machine in the Azure portal').
  • Include instructions or links for connecting to Linux VMs via SSH using Azure Bastion.
  • Ensure parity in examples and next steps for both Windows and Linux users.
  • Explicitly mention that Bastion supports SSH for Linux/macOS and provide relevant documentation.
GitHub Create Pull Request
Bastion Configure Bastion for native client connections ...azure-docs/blob/main/articles/bastion/native-client.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by listing Windows native client connection instructions and examples before Linux equivalents, referencing Windows-specific tools (RDP, Windows native client) more prominently, and providing links that prioritize Windows connection guides. Linux instructions are present but appear secondary, and macOS is not mentioned at all.
Recommendations
  • Present Linux and Windows instructions in parallel or alternate their order to avoid Windows-first bias.
  • Include explicit examples and instructions for macOS users, as they are also common in cross-platform scenarios.
  • Ensure that Linux tools and commands are described with equal detail and prominence as Windows tools.
  • Add a table or section that summarizes connection methods for all platforms (Windows, Linux, macOS) at the top of the page.
  • Avoid using Windows-centric terminology (e.g., 'native client' meaning RDP) without clarifying Linux/macOS equivalents.
GitHub Create Pull Request
Bastion Record Bastion sessions ...e-docs/blob/main/articles/bastion/session-recording.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes configuration and usage steps via the Azure Portal UI, which is most commonly accessed from Windows environments. There are no CLI, PowerShell, Bash, or Linux/macOS-specific instructions or examples. All screenshots and workflow descriptions assume a graphical interface typical of Windows users, and there is no mention of how to perform these tasks from Linux or macOS (e.g., using Azure CLI or REST API).
Recommendations
  • Add equivalent instructions for enabling and configuring Bastion session recording using Azure CLI and/or Azure PowerShell, with explicit Linux/macOS shell examples.
  • Provide REST API examples for advanced users who may not use the portal.
  • Include notes or sections clarifying platform independence where applicable, and highlight any steps that differ for Linux/macOS users.
  • Add screenshots or terminal output examples from Linux/macOS environments where relevant.
GitHub Create Pull Request
Bastion Create a shareable link for Azure Bastion ...zure-docs/blob/main/articles/bastion/shareable-link.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on using the Azure portal GUI for all steps and does not provide any CLI, PowerShell, or shell-based examples. While this avoids explicit Windows/Powershell bias, it implicitly favors Windows users by referencing the Azure portal UI, which is most commonly accessed from Windows environments. There are no examples or instructions for using Azure CLI, Bash, or other Linux/macOS-friendly tools to enable, create, or manage shareable links. The only mention of command-line tools is in the Permissions section, where PowerShell cmdlets are referenced for permissions, with no mention of Azure CLI or REST API equivalents.
Recommendations
  • Add Azure CLI and/or Bash examples for enabling the Shareable Link feature, creating, viewing, and deleting shareable links.
  • Include REST API references or examples for users who prefer automation or non-GUI workflows.
  • When mentioning permissions, provide Azure CLI and REST API equivalents alongside PowerShell cmdlets.
  • Explicitly state that all steps can be performed from any OS via the Azure portal, but highlight cross-platform command-line alternatives.
GitHub Create Pull Request
Bastion About VM connections and features ...Docs/azure-docs/blob/main/articles/bastion/vm-about.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page shows a mild Windows bias. For example, the 'Copy and paste' section links only to 'Copy and paste - Windows VMs', with no mention of Linux VM copy/paste support or equivalent documentation. Windows terminology (RDP) is referenced before SSH, and there are no explicit Linux/macOS examples or links. However, some sections (file transfer, full screen, audio) are described in a platform-neutral way or reference native SSH clients, which are more common on Linux/macOS.
Recommendations
  • Add equivalent documentation links and examples for Linux VMs, especially for features like copy/paste and file transfer.
  • Ensure that both RDP (Windows) and SSH (Linux/macOS) scenarios are described with parity, including configuration steps and limitations.
  • When referencing features, mention Linux/macOS support explicitly and provide links to relevant articles.
  • Avoid using Windows terminology exclusively; use cross-platform terms where possible.
GitHub Create Pull Request
Bastion VNet peering and Azure Bastion architecture .../azure-docs/blob/main/articles/bastion/vnet-peering.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references Windows virtual machines first and links only to the Windows VM quick-create guide, omitting explicit mention or guidance for Linux VM deployment. The connection instructions link to a Windows-specific RDP guide, with no parallel Linux SSH example or link provided. This creates a subtle but notable bias toward Windows users.
Recommendations
  • Include links to both Windows and Linux VM quick-create guides when referencing VM deployment.
  • Provide connection instructions for both RDP (Windows) and SSH (Linux/macOS) scenarios, or link to relevant Linux connection documentation.
  • Ensure examples and terminology are platform-neutral or explicitly mention both Windows and Linux where applicable.
GitHub Create Pull Request
Bastion Enable remote work by using Azure Bastion ...cs/blob/main/articles/bastion/work-remotely-support.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page references PowerShell as a primary method for configuring Azure Bastion, which is a Windows-centric tool. PowerShell is mentioned before Azure CLI, and there are no explicit Linux/macOS-specific instructions or examples. The page does not mention SSH clients, Linux terminal usage, or remote desktop tools commonly used on non-Windows platforms.
Recommendations
  • Provide explicit Linux/macOS instructions and examples for configuring Azure Bastion, such as using SSH from a Linux terminal.
  • Mention and link to Linux/macOS equivalents for remote access (e.g., Remmina, Terminal, native SSH).
  • Ensure Azure CLI examples are given equal prominence to PowerShell, and clarify cross-platform compatibility.
  • Consider adding a table or section comparing access methods for Windows, Linux, and macOS users.
GitHub Create Pull Request
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 →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 Windows RDP connection guides are linked. There are no Linux VM or SSH connection examples or references, and the workflow assumes Windows usage patterns. No Linux-specific instructions, tools, or parity are provided throughout the page.
Recommendations
  • Add links to Linux VM quickstart guides alongside Windows VM guides in the 'Next steps' section.
  • Include instructions or references for connecting to Linux VMs via SSH using Azure Bastion.
  • Provide example ARM template parameters and usage for both Windows and Linux VM scenarios.
  • Ensure parity in screenshots and walkthroughs by showing both Windows and Linux VM resource validation and connection steps.
GitHub Create Pull Request
Bastion Quickstart: Use Terraform to deploy Azure Bastion ...b/main/articles/bastion/quickstart-deploy-terraform.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is given equal prominence as CLI, and there is no mention of Linux-specific shell environments or alternative tools. The CLI examples are generic and cross-platform, but the inclusion of PowerShell examples (which are most commonly used on Windows) without mentioning Bash or other Linux-native shells suggests a mild Windows bias. There are no explicit Linux examples or references to Linux tools or patterns.
Recommendations
  • Explicitly mention that Azure CLI commands work in Bash, Zsh, and other Linux shells, not just Windows.
  • Add example commands using Bash syntax (e.g., export instead of $var=...) to demonstrate Linux parity.
  • Clarify that PowerShell examples are optional and provide guidance for users on Linux/macOS who may not use PowerShell.
  • Consider including troubleshooting or environment setup notes for Linux users, such as installing Azure CLI on Linux.
  • Ensure that any referenced scripts or instructions do not assume a Windows environment by default.
GitHub Create Pull Request
Bastion VNet peering and Azure Bastion architecture .../azure-docs/blob/main/articles/bastion/vnet-peering.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows virtual machines first and exclusively in deployment steps and example links (e.g., linking to '/azure/virtual-machines/windows/quick-create-portal' but not the Linux equivalent). There are no Linux-specific examples, instructions, or links, and the connection instructions reference RDP (primarily a Windows protocol) without mentioning SSH (commonly used for Linux VMs).
Recommendations
  • Include parallel instructions and links for Linux virtual machines, such as '/azure/virtual-machines/linux/quick-create-portal'.
  • Mention SSH explicitly alongside RDP when describing connection options, clarifying that Azure Bastion supports both.
  • Provide examples or references for connecting to Linux VMs via Bastion, not just Windows.
  • Ensure that deployment steps and architecture descriptions are OS-neutral or include both Windows and Linux scenarios.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-connect-vm-linux-rdp.md .../main/articles/bastion/bastion-connect-vm-linux-rdp.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by requiring the use of RDP (a protocol and toolset traditionally associated with Windows environments) for connecting to Linux VMs, and referencing xrdp as a necessary component. There are no examples or mentions of Linux-native remote desktop protocols (such as VNC or X11 forwarding), nor are Linux-specific client tools or command-line examples provided. The documentation assumes RDP as the default/only method, which may not reflect common Linux administration practices.
Recommendations
  • Provide examples of connecting to Linux VMs using native Linux remote desktop protocols (e.g., VNC, X11 forwarding) alongside RDP.
  • Include Linux command-line examples for installing and configuring xrdp, and mention alternative Linux remote desktop solutions.
  • Clarify why RDP is chosen over other protocols for Linux, and discuss the pros/cons for Linux administrators.
  • Add instructions for connecting from Linux client machines (not just via Azure portal), including open-source RDP clients.
  • Ensure parity in documentation by referencing both Windows and Linux tools and workflows where applicable.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-connect-vm-scale-set.md .../main/articles/bastion/bastion-connect-vm-scale-set.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation provides instructions for connecting to a VM scale set using Azure Bastion exclusively through the Azure portal, with no mention of Linux-specific workflows, SSH, or command-line alternatives. The UI flow and terminology (e.g., 'RDP' anchor, 'Connect' button) are more familiar to Windows users. There are no examples or guidance for Linux users or those preferring SSH connections.
Recommendations
  • Add instructions or examples for connecting to Linux VM instances using SSH via Azure Bastion, including both portal and CLI workflows.
  • Explicitly mention that the process applies to both Windows and Linux VMs, and clarify any differences in the connection experience.
  • Provide screenshots or examples showing SSH username/password or key-based authentication for Linux VMs.
  • Include Azure CLI and/or PowerShell examples for users who prefer command-line access, ensuring parity between Windows and Linux scenarios.
  • Avoid UI terminology that is specific to Windows (such as 'RDP') unless also covering SSH and Linux workflows.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-connect-vm-ssh-linux.md .../main/articles/bastion/bastion-connect-vm-ssh-linux.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation page is generally focused on connecting to Linux VMs via Azure Bastion through the Azure portal, which is a cross-platform web interface. However, there is a recurring bias in the guidance for storing SSH keys in Azure Key Vault: the instructions and links reference PowerShell (a Windows-centric tool) first and do not provide explicit Linux/Unix shell (Bash) or cross-platform CLI examples. The linked quick-create guide for Key Vault uses PowerShell, and the recommendation to use 'PowerShell or Azure CLI' always lists PowerShell first, with no Bash-specific or Linux-native instructions. There are no explicit Linux command-line examples for common tasks, and the documentation does not mention or show parity for Linux users in these steps.
Recommendations
  • Provide explicit Azure CLI (Bash) examples for creating and managing Azure Key Vault resources and secrets, and ensure these are presented alongside or before PowerShell examples.
  • Update links such as 'Create a key vault' to point to both PowerShell and Azure CLI quickstart guides, or to a landing page that lets users choose their preferred platform.
  • When referencing command-line tools, use 'Azure CLI' as the default or present it before PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
  • Add notes or sections clarifying that all steps can be performed from Linux/macOS terminals using Azure CLI, and provide sample commands.
  • Review all instructions to ensure that Linux users are not implicitly directed to use Windows-centric tools or workflows.
GitHub Create Pull Request
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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation presents VM connectivity options with Windows (RDP) and Linux (SSH) side by side, but lists Windows RDP connectivity before Linux SSH, and does not provide any platform-specific examples or guidance for Linux users. There is no mention of Linux tools, patterns, or command-line usage (e.g., SSH from Linux terminal), nor are Linux-specific workflows or troubleshooting steps included. The documentation does not show bias in terms of exclusive Windows tools or PowerShell-heavy examples, but the ordering and lack of Linux-centric examples indicate a subtle Windows-first bias.
Recommendations
  • Provide explicit Linux usage examples, such as connecting via SSH from a Linux terminal or using Linux-native RDP clients.
  • Include Linux-specific troubleshooting tips and best practices for Bastion connectivity.
  • Balance the ordering of Windows and Linux features/examples in tables and descriptions, or alternate which platform is listed first.
  • Reference Linux command-line tools (e.g., ssh, rdesktop, xfreerdp) where appropriate, alongside Windows tools.
  • Add links to Linux documentation or guides for remote desktop and SSH connectivity through Azure Bastion.
GitHub Create Pull Request
← Previous Page 2 of 4 Next →