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 1-25 of 76 flagged pages
Bastion
Configure Bastion for Kerberos authentication - Azure portal
...ain/articles/bastion/kerberos-authentication-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation is heavily biased toward Windows environments. All examples, templates, and verification steps assume Windows Server and Windows 10 VMs. Only Windows domain controllers are referenced, and all configuration scripts use PowerShell. There are no instructions or examples for Linux-based domain controllers, Linux VMs, or cross-platform Kerberos authentication. Windows tools and settings (Local Group Policy Editor, NTLM restriction) are referenced exclusively.
Recommendations
- Add instructions and examples for configuring Kerberos authentication with Linux VMs (e.g., Ubuntu, CentOS) and Linux-based domain controllers (such as Samba/Active Directory Domain Services).
- Provide equivalent verification steps for Linux, such as using kinit, checking /etc/krb5.conf, and relevant log files.
- Include ARM template parameters and script extensions for deploying Linux VMs and configuring them for Kerberos authentication.
- Offer CLI examples using Azure CLI and Bash, not just PowerShell.
- Reference Linux documentation for Kerberos and Active Directory integration, alongside Windows documentation.
Create Pull Request
Bastion
Configure Bastion for Kerberos authentication - Azure portal
...ain/articles/bastion/kerberos-authentication-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily Windows-centric, with all examples, templates, and instructions focused exclusively on Windows Server and Windows 10 VMs. Only Windows tools (such as Local Group Policy Editor and PowerShell) are referenced, and there are no Linux or macOS equivalents or guidance. The ARM template provisions only Windows VMs, and all verification and deployment steps use Windows-specific commands and interfaces.
Recommendations
- Add explicit guidance and examples for configuring Kerberos authentication with Linux VMs, including supported distributions and required packages (e.g., krb5, sssd).
- Provide ARM template parameters and examples for deploying Linux domain controllers (such as Samba/AD DC) and Linux client VMs.
- Include instructions for verifying Kerberos authentication on Linux (e.g., using kinit, klist, and system logs) and macOS.
- Reference cross-platform Kerberos documentation, not just Windows-specific links.
- Offer deployment and verification steps using Azure CLI and/or Bash, not just PowerShell.
Bastion
Copy and paste to and from a Windows virtual machine: Azure
...cs/blob/main/articles/bastion/bastion-vm-copy-paste.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively addresses copy and paste functionality for Windows virtual machines, with no mention of Linux VM support or examples. All instructions, prerequisites, and screenshots are Windows-centric, potentially leaving Linux/macOS users without guidance.
Recommendations
- Add explicit support and instructions for Linux VMs, including any differences in clipboard behavior or limitations.
- Include Linux-specific examples and screenshots where relevant.
- Clarify whether the Bastion clipboard feature works with Linux VMs and note any OS-specific caveats.
- Consider renaming the article or providing a parallel page for Linux VMs if functionality differs.
Bastion
Configure Bastion for native client connections
...azure-docs/blob/main/articles/bastion/native-client.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by listing Windows native client connection instructions and features before Linux equivalents, providing more detailed examples and links for Windows, and omitting explicit Linux command-line examples in the main text. The connection table and 'Next steps' section prioritize Windows, and references to Windows tools (RDP) are more prominent than Linux tools (SSH).
Recommendations
- Present Linux and Windows instructions with equal prominence, alternating order or grouping by scenario rather than OS.
- Include explicit Linux command-line examples and screenshots in the main documentation, not just in linked pages.
- Add parity in feature explanations, such as file transfer and authentication, for both Windows and Linux clients.
- Reference common Linux tools (e.g., OpenSSH, Remmina) alongside Windows tools (RDP), and provide usage examples.
- Ensure 'Next steps' links for Linux are as detailed and visible as those for Windows.
Bastion
Quickstart: Deploy Azure Bastion automatically
...s/blob/main/articles/bastion/quickstart-host-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and patterns before their Linux equivalents. For example, keyboard shortcuts for remote access are described in detail for Windows VMs and clients, with only a brief mention of Mac clients connecting to Windows VMs. There are no equivalent examples or guidance for connecting to Linux VMs from Linux or Mac clients. Additionally, the inbound port requirements list Windows (3389) before Linux (22), and the VM creation quickstart links mention Windows before Linux.
Recommendations
- Provide detailed examples and guidance for connecting to Linux VMs from Linux and Mac clients, including keyboard shortcuts and remote access patterns.
- Ensure parity in documentation order by listing Linux and Windows examples side-by-side or alternating which is mentioned first.
- Include Linux-specific remote access tips (e.g., SSH client usage, clipboard integration, keyboard shortcuts) where Windows-specific guidance is given.
- Explicitly mention cross-platform considerations and tools for both Windows and Linux users throughout the documentation.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-faq.md
...s/azure-docs/blob/main/articles/bastion/bastion-faq.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias by frequently referencing Windows tools, workflows, and terminology before or instead of Linux equivalents. For example, browser support is described in terms of Windows and Mac, with no mention of Linux. Keyboard layout instructions are provided only for Windows, and RDP (a Windows protocol) is discussed in detail, while SSH (commonly used on Linux) receives less focus. There are no examples or instructions tailored for Linux users, such as how to set keyboard layouts or use native SSH clients on Linux.
Recommendations
- Include Linux-specific instructions and examples where relevant, such as how to set keyboard layouts on popular Linux distributions.
- When discussing browser support, explicitly mention Linux and supported browsers on that platform.
- Provide parity in native client connection instructions, including examples for both RDP (Windows) and SSH (Linux/macOS).
- Avoid assuming the user is on Windows; use platform-neutral language or provide parallel instructions for Windows, Linux, and macOS.
- When referencing Microsoft Entra authentication, include links or notes for Linux VM scenarios, not just Windows.
- Where possible, balance the discussion of RDP (Windows) and SSH (Linux/macOS) to reflect cross-platform usage.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-developer.md
...ocs/blob/main/articles/bastion/quickstart-developer.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation shows a moderate Windows bias. Windows is consistently mentioned before Linux (e.g., in VM creation links and port requirements). Keyboard shortcut guidance is Windows-centric, with only a brief Mac note for connecting to Windows VMs. There are no Linux-specific connection examples, troubleshooting tips, or keyboard shortcut guidance. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users.
Recommendations
- Alternate the order of Windows and Linux references, or list Linux first in some sections to balance visibility.
- Provide Linux-specific connection guidance, including keyboard shortcuts and troubleshooting tips for common Linux desktop environments.
- Include examples and screenshots for connecting to Linux VMs, not just Windows.
- Clarify any differences in user experience when connecting to Linux VMs (e.g., clipboard, audio, keyboard mapping).
- Ensure that all instructions and examples are provided for both Windows and Linux VMs, including any platform-specific caveats.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/configuration-settings.md
...s/blob/main/articles/bastion/configuration-settings.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation consistently presents Azure PowerShell (a Windows-centric tool) as a primary scripting/configuration method, often before Azure CLI. There are no explicit Linux shell or Bash script examples, and no mention of Linux-specific tools or workflows. The examples and links for configuration are focused on the Azure portal and PowerShell, with Azure CLI included but not emphasized. No Linux-native guidance or parity is provided.
Recommendations
- Add explicit Bash/Linux shell examples for all configuration steps, especially for users managing Azure resources from Linux environments.
- Ensure Azure CLI examples are given equal prominence to PowerShell, and consider listing CLI before PowerShell where possible, as CLI is cross-platform.
- Include references to Linux-native tools or workflows where relevant (e.g., using Bash scripts, cloud-init, or SSH key management on Linux).
- Where possible, clarify that Azure CLI commands work on all platforms and provide sample commands in a Linux shell context.
- Add a section or note for Linux administrators highlighting any differences or considerations when configuring Azure Bastion from Linux systems.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/configure-host-scaling.md
...s/blob/main/articles/bastion/configure-host-scaling.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page focuses exclusively on using the Azure portal for host scaling and mentions PowerShell as an alternative method, with no reference to Linux-specific tools or CLI commands. Windows/PowerShell is mentioned as the only alternative to the portal, and there are no examples or guidance for Linux users (e.g., Azure CLI, Bash).
Recommendations
- Add equivalent instructions for configuring host scaling using Azure CLI (az bastion update), which is cross-platform and commonly used on Linux.
- Include examples using Bash or shell scripting for automation on Linux systems.
- Explicitly mention that PowerShell is available cross-platform, but also provide Azure CLI examples to ensure Linux parity.
- Consider reordering alternative methods so that CLI (cross-platform) options are mentioned before or alongside PowerShell.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/connect-ip-address.md
...-docs/blob/main/articles/bastion/connect-ip-address.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing RDP (a Windows protocol) in both the portal and native client sections, listing RDP before SSH, and omitting explicit Linux-focused examples or screenshots. There are no Linux-specific instructions, such as connecting from a Linux terminal or using Linux-native tools. All command-line examples use Azure CLI but are generic, with no mention of Linux authentication patterns or SSH key management. The documentation does not address Linux users' needs directly.
Recommendations
- Provide Linux-specific examples, such as connecting from a Linux terminal using SSH with Azure Bastion.
- Include screenshots or instructions that show connecting to Linux VMs (e.g., using SSH) in the Azure portal.
- List SSH (Linux) examples before RDP (Windows) examples, or present them in parallel to avoid Windows-first bias.
- Mention Linux authentication methods, such as using private key files and their typical locations on Linux systems.
- Clarify that the Azure CLI commands work on all platforms and provide any Linux-specific notes if needed.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-host-portal.md
...s/blob/main/articles/bastion/quickstart-host-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows VM creation first, listing Windows port (3389) before Linux (22), and providing keyboard shortcut guidance only for Windows VMs (including Mac-to-Windows shortcut mapping). There are no Linux-specific connection details, shortcut keys, or troubleshooting tips, and the audio output section does not clarify Linux support. The documentation does mention Linux VM creation, but examples and guidance are predominantly Windows-centric.
Recommendations
- Alternate the order of Windows and Linux VM references to avoid implicit prioritization.
- Provide Linux-specific connection instructions, including SSH client usage and relevant keyboard shortcuts for Linux VMs.
- Clarify audio output support for Linux VMs and provide troubleshooting steps if applicable.
- Include examples and tips for connecting from Linux and Mac clients to Linux VMs, not just Windows.
- Ensure parity in troubleshooting and usage notes for both Windows and Linux VM scenarios.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/work-remotely-support.md
...cs/blob/main/articles/bastion/work-remotely-support.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing PowerShell as a primary configuration method and referencing RDP (a Windows protocol) before SSH. There are no explicit Linux-focused examples or mentions of Linux tools, and the ordering and language suggest a Windows-first approach.
Recommendations
- Add explicit Linux-focused examples, such as using SSH from Linux/macOS terminals.
- Provide step-by-step instructions for configuring Azure Bastion from a Linux environment, including relevant CLI commands.
- Mention Linux-native tools (e.g., OpenSSH, terminal applications) alongside PowerShell and RDP.
- Ensure that SSH connectivity and Linux VM management are described with equal prominence to Windows/RDP scenarios.
- Reorder examples and tool mentions so that Linux and Windows approaches are presented with parity.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/vm-about.md
...Docs/azure-docs/blob/main/articles/bastion/vm-about.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific features and documentation before or instead of Linux equivalents. For example, the 'Copy and paste' section links only to a Windows VM guide, with no mention of Linux VMs. There is no explicit mention of Linux tools, SSH, or Linux-specific workflows in the main sections, and Windows terminology (such as RDP) is prioritized.
Recommendations
- Add parallel Linux examples and documentation links wherever Windows-specific features are described (e.g., provide a 'Copy and paste - Linux VMs' link or section).
- Ensure that SSH and Linux VM connection methods are mentioned alongside RDP and Windows methods in all relevant sections.
- Reference Linux tools and workflows (such as OpenSSH, SCP, or SFTP) where file transfer or remote access is discussed.
- Review all sections to ensure Linux parity in feature descriptions, troubleshooting, and FAQ links.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/whats-new.md
...ocs/azure-docs/blob/main/articles/bastion/whats-new.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page shows a subtle Windows bias: Windows-specific features (RDP, Entra ID for RDP) are listed before Linux equivalents (SSH), and the terminology and links (e.g., RDP, session recording) are Windows-centric. There is no mention of Linux remote desktop protocols or tools, and Linux examples are less prominent or missing.
Recommendations
- Ensure Linux-related features (such as SSH, Linux remote desktop protocols) are mentioned with equal prominence and detail as Windows features.
- Provide explicit examples and documentation links for Linux remote access scenarios, such as connecting to Linux VMs using Bastion.
- Include references to Linux-native tools (e.g., xrdp, VNC, SSH clients) where appropriate, and clarify parity between Windows and Linux support.
- Alternate the order of feature announcements to avoid consistently listing Windows features first.
- Add a section or table comparing Windows and Linux Bastion capabilities for transparency.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/vm-upload-download-native.md
...lob/main/articles/bastion/vm-upload-download-native.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates Windows bias by presenting Windows/RDP instructions and tools (MSTSC, Copy/Paste) first and in more detail, while Linux/SSH instructions are secondary and less detailed. There are no explicit Linux-native file manager examples, and the documentation assumes familiarity with Windows workflows. Linux users are directed to use SCP via the tunnel command, but no GUI or alternative Linux-native methods are discussed.
Recommendations
- Provide Linux-native client examples (e.g., using Remmina, KRDC, or rdesktop for RDP file transfer) alongside Windows examples.
- Present Linux and Windows instructions in parallel sections or with equal prominence.
- Include explicit Linux file transfer workflows (e.g., using Nautilus, Dolphin, or command-line tools) for both RDP and SSH.
- Avoid assuming the use of Windows-native tools (like MSTSC and Copy/Paste) as the default workflow.
- Add screenshots or step-by-step guides for Linux users, similar to those provided for Windows.
- Clarify any limitations or differences in file transfer support between platforms.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on Azure PowerShell, with all deployment steps and code samples provided exclusively in PowerShell syntax. There are no Bash, Azure CLI, or Linux/macOS-specific instructions or examples. References to VM creation link only to Windows VM guides, and PowerShell is assumed as the primary tool throughout, creating friction for Linux/macOS users who typically use Bash and Azure CLI.
Recommendations
- Add equivalent Azure CLI (Bash) examples for all deployment steps, including resource group, VNet, subnet, public IP, and Bastion creation.
- Include links to Linux VM creation guides alongside Windows VM guides.
- Explicitly mention cross-platform options (e.g., Azure CLI, Bash, Cloud Shell) in the introduction and prerequisites.
- Reorganize sections to present both PowerShell and CLI/Bash options side-by-side or in parallel, rather than PowerShell-only.
- Clarify that Azure PowerShell can be used on Linux/macOS, but provide guidance for users who prefer CLI/Bash.
Bastion
About Azure Bastion configuration settings
...s/blob/main/articles/bastion/configuration-settings.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page consistently lists Azure PowerShell as a primary configuration method, often before Azure CLI, and provides direct links to PowerShell cmdlets but not to equivalent Linux shell scripts or examples. In several configuration tables, PowerShell is mentioned explicitly, while Linux/macOS users are expected to use Azure CLI with less detailed guidance. No explicit Linux/macOS shell examples are provided, and PowerShell is given prominence, indicating a Windows-centric approach.
Recommendations
- Provide explicit Bash/Linux shell examples alongside PowerShell, especially for Azure CLI usage.
- Ensure Azure CLI instructions are as detailed and prominent as PowerShell ones.
- Add notes or sections clarifying cross-platform usage, including macOS and Linux.
- Where PowerShell is referenced, include equivalent Bash/CLI commands for Linux/macOS users.
- Consider listing Azure CLI before PowerShell in tables to signal platform neutrality.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes how to view and upgrade Bastion SKUs using the Azure portal GUI, which is most commonly accessed via a web browser on Windows. There are no CLI, PowerShell, or Bash examples, nor any mention of Linux/macOS workflows or tools. This creates friction for users who prefer or require command-line or automation approaches, which are common on Linux/macOS.
Recommendations
- Add Azure CLI examples for viewing and upgrading Bastion SKUs.
- Include PowerShell and Bash command snippets for parity.
- Explicitly mention that the portal is cross-platform, and clarify any OS-specific limitations.
- Provide links to CLI documentation for users who prefer command-line operations.
Medium Priority
View Details →
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 using Azure Bastion. However, there is a notable bias in the sections describing how to create and manage Azure Key Vault secrets: instructions and links are provided only for PowerShell (a Windows-centric tool), with no equivalent Linux/macOS CLI or Bash examples. This may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Add explicit Azure CLI and Bash examples for creating and managing Azure Key Vault secrets, alongside PowerShell instructions.
- Provide links to Azure CLI documentation for key vault operations.
- Clarify that PowerShell is cross-platform, but also acknowledge and support native Linux/macOS workflows.
- Ensure that all referenced guides (such as 'Create a key vault') include Linux/macOS instructions.
Medium Priority
View Details →
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 Bash, Azure CLI, or Linux/macOS shell examples. References to VM creation link only to Windows VM quickstart guides, and the overall workflow assumes a Windows-centric toolset and environment.
Recommendations
- Add equivalent Azure CLI (bash) examples for all deployment steps, including resource group, VNet, subnet, public IP, and Bastion creation.
- Provide links to Linux VM creation guides alongside Windows VM guides.
- Explicitly mention cross-platform options for scripting and automation, such as Azure CLI or Terraform.
- Reorder or parallelize examples so that Linux/macOS users see relevant instructions without needing to adapt PowerShell code.
- Clarify that PowerShell can be used on Linux/macOS, but also provide native shell/CLI examples for those platforms.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows a mild Windows bias in several areas. Browser recommendations list Windows options first and provide more detail for Windows users. Keyboard layout configuration instructions are given only for Windows workstations, with no equivalent guidance for Linux or macOS users. The example for regaining keyboard focus references the Windows key, which may not exist on non-Windows systems. No Linux/macOS-specific examples or instructions are provided for these scenarios.
Recommendations
- Provide browser recommendations for Linux explicitly, not just Windows and Mac.
- Add instructions for setting keyboard layouts on Linux and macOS workstations, alongside the Windows example.
- Clarify how to regain keyboard/mouse focus for users on Linux and macOS, especially where the 'Windows key' is referenced.
- Ensure parity in examples and troubleshooting steps for all major platforms.
Bastion
Working with VMs and NSGs in Azure Bastion
...s/azure-docs/blob/main/articles/bastion/bastion-nsg.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides only a PowerShell script for configuring NSG rules, with no equivalent Azure CLI, Bash, or Linux/macOS instructions. PowerShell is a Windows-centric tool, and its exclusive use here creates friction for Linux and macOS users. There are no references to cross-platform alternatives, and the scripting section is labeled as 'Powershell Script' without mention of other options.
Recommendations
- Add Azure CLI and/or Bash script examples for configuring NSG rules, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include guidance or links for performing these tasks via the Azure Portal, which is platform-agnostic.
- Clearly indicate that PowerShell Core is available on Linux/macOS, if PowerShell must be used, and provide installation instructions.
- Present scripting examples for both Windows (PowerShell) and Linux/macOS (Azure CLI/Bash), ideally side-by-side.
- Avoid labeling scripting sections as 'Powershell Script' only; use more inclusive headings like 'Automating NSG Rule Creation (PowerShell & Azure CLI)'.
Bastion
Connect to a VM - specified private IP address: Azure portal
...-docs/blob/main/articles/bastion/connect-ip-address.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides connection instructions primarily through the Azure portal and Azure CLI, which are cross-platform. However, the examples for native client connections (RDP, SSH, Tunnel) do not include any Linux/macOS-specific details or examples, such as using OpenSSH or native RDP clients. The portal-based instructions implicitly favor Windows workflows (RDP, username/password), and there is no mention of Linux-specific connection patterns or troubleshooting. Windows-centric terminology (RDP, username/password) appears before SSH, and Linux tools are not referenced.
Recommendations
- Add explicit Linux/macOS examples for connecting via SSH (e.g., using OpenSSH command-line syntax) and RDP (e.g., using Remmina or xfreerdp).
- Clarify which steps or tools are cross-platform and provide guidance for Linux/macOS users where workflows differ (e.g., credential handling, client applications).
- Include troubleshooting tips for Linux/macOS users, such as SSH key permissions or RDP client compatibility.
- Balance the order of examples so that SSH (common for Linux) is presented before or alongside RDP.
Bastion
Configure Bastion for native client connections
...azure-docs/blob/main/articles/bastion/native-client.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Windows native client examples and instructions are presented first in tables and 'Next steps', with Windows-specific tools (RDP) and terminology prioritized. Linux instructions are present but less prominent, and Linux tools (e.g., OpenSSH) are not mentioned by name. There is no explicit PowerShell example, but Windows-centric navigation and references are more detailed.
Recommendations
- Alternate the order of Windows and Linux instructions/examples so Linux is not always second.
- Explicitly mention Linux tools (e.g., OpenSSH, GNOME Terminal) and provide command-line examples for Linux/macOS.
- Add parity in screenshots and step-by-step instructions for Linux/macOS environments.
- Clarify that 'native client' includes Linux/macOS SSH clients and provide links to their documentation.
- Ensure 'Next steps' links include Linux/macOS-specific guides as clearly as Windows guides.
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 no mention of Linux VMs or examples for Linux/macOS users. All instructions, prerequisites, and screenshots are Windows-centric, which may leave Linux users without guidance for copy/paste operations via Azure Bastion.
Recommendations
- Add a parallel section for Linux VMs, detailing any differences in copy/paste behavior or prerequisites.
- Include examples and screenshots for Linux desktop environments (e.g., Ubuntu, CentOS) and common terminal applications.
- Clarify whether the Bastion clipboard functionality works identically for Linux VMs, and note any OS-specific limitations.
- Mention keyboard shortcuts for Linux and macOS users, and address any browser-specific differences for these platforms.