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 26-50 of 222 flagged pages
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting Windows/RDP instructions and examples first, focusing on Windows-native tools (MSTSC, Copy/Paste), and omitting explicit Linux desktop file transfer examples (e.g., drag-and-drop, Nautilus, or Linux RDP clients). Linux instructions are less detailed and only mention SCP for SSH file transfer, without equivalent GUI or desktop workflow guidance.
Recommendations
- Provide Linux-specific examples for file transfer using native Linux RDP clients (e.g., Remmina, rdesktop) and describe how users can copy/paste or drag-and-drop files in those environments.
- Include step-by-step instructions for file transfer using Linux desktop environments, not just CLI (SCP).
- Present Windows and Linux workflows in parallel sections, rather than listing Windows first.
- Mention macOS workflows and native clients where relevant.
- Clarify tool parity (e.g., if Copy/Paste works in Linux RDP clients, document it; if not, suggest alternatives).
Create Pull Request
Bastion
Secure Your Azure Bastion Deployment
...zure-docs/blob/main/articles/bastion/secure-bastion.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing RDP and Windows VM connectivity first and most frequently, mentioning Kerberos authentication specifically for Windows VMs, and providing links and examples that prioritize Windows scenarios. Linux connectivity is referenced only once, with no detailed Linux-specific examples or parity in authentication and management guidance. There is a lack of Linux tooling or command-line examples, and Windows-centric features (Kerberos, RDP) are highlighted without equivalent coverage for Linux (e.g., SSH key management, Linux authentication methods).
Recommendations
- Add explicit Linux SSH connectivity examples and workflows, including command-line usage and integration with Azure Bastion.
- Provide parity in authentication guidance for Linux VMs, such as integrating with PAM, LDAP, or other Linux authentication mechanisms.
- Include Linux-specific security recommendations (e.g., SSH hardening, Linux firewall configuration) alongside Windows-centric advice.
- Reference Linux tools and management patterns (e.g., using Azure CLI, Bash scripts) equally with Windows tools like PowerShell.
- Ensure all features (e.g., session recording, privileged access) are described for both Windows and Linux scenarios, with clear examples for each.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting Windows/RDP instructions and tools (MSTSC, Copy/Paste) first and in greater detail, while Linux/SSH instructions are secondary and less explicit. There are no concrete Linux-native client examples (e.g., screenshots, step-by-step for Linux GUI clients), and Windows terminology and workflows dominate the narrative.
Recommendations
- Provide explicit Linux-native client examples, including step-by-step instructions for popular Linux RDP and SSH clients (e.g., Remmina, GNOME Terminal).
- Include Linux-specific file transfer workflows, such as drag-and-drop in Linux RDP clients or using Nautilus/SCP GUIs.
- Balance the order of presentation: introduce Linux and Windows workflows in parallel or alternate, rather than Windows-first.
- Mention Linux tools (e.g., xfreerdp, rdesktop, scp, sftp) alongside their Windows equivalents, with equal detail.
- Add screenshots or command-line output examples from Linux environments to illustrate parity.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page, while focused on connecting to Linux VMs, shows bias toward Windows tooling by referencing PowerShell as the primary method for creating Azure Key Vault resources and storing SSH keys. There are no explicit Linux shell (bash) or cross-platform CLI examples for these steps, and the links provided direct users to PowerShell-based instructions. This may disadvantage Linux users or those working in non-Windows environments.
Recommendations
- Provide equivalent bash/Azure CLI examples for creating and managing Azure Key Vault resources and secrets, alongside PowerShell instructions.
- Update links to include or reference cross-platform guides, not just PowerShell-based documentation.
- Explicitly mention that all steps can be performed using Azure CLI on Linux/macOS, and provide sample commands.
- Ensure that portal-based instructions do not assume a Windows environment or tooling.
- Add a section or callout for Linux/macOS users, clarifying supported workflows and tools.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page is heavily focused on Windows and PowerShell, providing only PowerShell-based deployment instructions and examples. Windows tools and patterns are mentioned first and exclusively, with no equivalent Linux or cross-platform CLI examples shown inline. References to Linux are minimal and limited to port numbers for SSH, without any Linux-specific deployment or connection instructions.
Recommendations
- Add parallel Azure CLI examples for all deployment steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include explicit instructions or links for deploying Bastion from Linux/macOS environments, such as using Bash in Azure Cloud Shell.
- Provide example commands for connecting to Linux VMs via Bastion, not just mentioning SSH port.
- Reorder references so that cross-platform tools (Azure CLI, portal) are mentioned before or alongside PowerShell.
- Clarify that PowerShell is available on Linux/macOS, but also highlight alternatives for users who prefer Bash or native Linux tools.
Bastion
Working with VMs and NSGs in Azure Bastion
...s/azure-docs/blob/main/articles/bastion/bastion-nsg.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only a PowerShell script for configuring NSG rules, which is a Windows-centric tool. There are no equivalent examples for Linux users (e.g., Azure CLI, Bash, or ARM templates), and PowerShell is presented as the sole automation method for NSG configuration. This creates a bias toward Windows users and may hinder Linux administrators from following the guidance efficiently.
Recommendations
- Add equivalent Azure CLI (az network nsg rule create) examples for all NSG rule configurations.
- Provide Bash script snippets or ARM template samples for NSG rule automation.
- Explicitly mention that PowerShell is one of several options and link to cross-platform alternatives.
- Ensure that all automation examples are presented in parallel (e.g., PowerShell and Azure CLI side-by-side) to improve parity.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows-first bias in several areas. Browser recommendations prioritize Windows (Edge/Chrome) and only mention Mac as an afterthought, with no mention of Linux browsers. Keyboard layout instructions and examples are exclusively for Windows, with no guidance for Linux or Mac users. The only detailed instructions for changing keyboard layouts are for Windows, and there are no Linux-specific examples or tool mentions throughout the FAQ, despite Azure Bastion supporting SSH (commonly used for Linux VMs). Additionally, references to RDP and Windows authentication are more prominent than those for SSH or Linux authentication scenarios.
Recommendations
- Add explicit Linux browser support statements and examples (e.g., Firefox on Linux).
- Provide instructions for setting keyboard layouts on Linux and Mac, not just Windows.
- Include examples and guidance for connecting to Linux VMs via SSH, including any authentication nuances.
- Balance references to RDP (Windows) and SSH (Linux) in role/permission and feature discussions.
- Mention Linux-native tools and workflows where relevant (e.g., SSH clients, file transfer methods).
- Ensure parity in troubleshooting and error resolution steps for both Windows and Linux VM scenarios.
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 page is heavily Windows-centric: all examples, instructions, and templates assume Windows Server and Windows 10 VMs. Only Windows domain controllers are referenced, and all configuration and verification steps use Windows tools (Group Policy Editor, PowerShell). There are no Linux equivalents or guidance for using Linux-based Kerberos realms, nor any mention of Linux VM support or cross-platform scenarios.
Recommendations
- Add explicit guidance and examples for configuring Kerberos authentication with Linux VMs (e.g., Ubuntu, CentOS) and Linux-based domain controllers (such as Samba/Active Directory or MIT/Heimdal Kerberos).
- Include ARM template parameters and resource definitions for deploying Linux VMs and setting up a Linux-based Kerberos KDC.
- Provide verification steps for Kerberos authentication on Linux, such as using kinit, klist, and relevant configuration files (/etc/krb5.conf).
- Reference documentation for Kerberos on Linux (e.g., MIT Kerberos, Samba AD DC) alongside or before Windows resources.
- Offer PowerShell alternatives, such as Azure CLI or Bash scripts, for template deployment and VM configuration.
- Clarify platform limitations: if Kerberos authentication via Bastion is only supported for Windows VMs, state this clearly at the beginning of the documentation.
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 page demonstrates a Windows bias by listing Windows native client connection instructions and examples before Linux equivalents, providing more detailed steps and links for Windows scenarios, and omitting explicit Linux command-line examples in the main content. The table and 'Next steps' section both prioritize Windows, and there is a lack of parity in example depth for Linux users.
Recommendations
- Present Linux and Windows instructions in parallel, ensuring equal detail for both platforms.
- Include explicit Linux command-line examples (e.g., SSH commands) in the main content, not just in linked pages.
- Balance the order of presentation so that Linux instructions are not always listed after Windows.
- Add screenshots and step-by-step guides for Linux clients, similar to those provided for Windows.
- Ensure that all features and limitations are discussed with respect to both Windows and Linux clients.
Bastion
About Azure Bastion configuration settings
...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 lists Azure PowerShell (a Windows-centric tool) before Azure CLI when describing configuration methods. In the 'Instances and host scaling' section, only Azure PowerShell and portal methods are provided, with no Azure CLI or Linux-native examples. There are no explicit Linux shell or scripting examples, and no mention of Linux-specific tools or workflows. This creates a subtle bias toward Windows and PowerShell users, potentially making it less accessible for Linux administrators.
Recommendations
- Ensure Azure CLI examples are provided for all configuration steps, especially for 'Instances and host scaling', not just PowerShell.
- Alternate the order of PowerShell and CLI examples, or list CLI first in some sections to avoid Windows-first bias.
- Include Linux shell (bash) usage examples where relevant, such as subnet and public IP configuration.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Add notes or links to Linux-specific guidance or troubleshooting where appropriate.
Bastion
Secure Your Azure Bastion Deployment
...zure-docs/blob/main/articles/bastion/secure-bastion.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-specific features and examples, such as RDP and Kerberos authentication for domain-joined Windows VMs, and referencing Windows-centric tools and patterns (e.g., RDP, Kerberos, Entra ID authentication for RDP). Linux-specific guidance is minimal and often referenced only as a link, with no detailed examples or parity in explanation. Windows tools and authentication mechanisms are described in detail, while Linux equivalents (such as SSH key management and session recording for SSH) are mentioned briefly or omitted.
Recommendations
- Provide detailed Linux-specific examples alongside Windows examples, such as step-by-step SSH connection and session management guidance.
- Include Linux authentication mechanisms (e.g., PAM, SSH certificate authentication) and explain how to secure Linux VMs using Azure Bastion.
- Offer parity in documentation for Kerberos-like authentication for Linux (e.g., integration with LDAP or FreeIPA) if supported.
- Ensure that session recording, monitoring, and logging instructions explicitly cover both RDP (Windows) and SSH (Linux) scenarios.
- Reference Linux tools and patterns (e.g., OpenSSH, Linux user management) with equal prominence to Windows tools.
- Avoid mentioning Windows features first; alternate or parallelize Windows and Linux guidance throughout the documentation.
Bastion
Quickstart: Connect to a VM using Azure Bastion Developer: Azure portal
...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 demonstrates a Windows bias by prioritizing Windows terminology and examples. Windows is mentioned first in VM creation links and port requirements. Keyboard shortcut guidance is detailed for Windows VMs and clients, with only a passing reference to Mac users connecting to Windows VMs. There are no Linux-specific connection instructions, troubleshooting, or shortcut keys. The documentation assumes familiarity with Windows patterns and tools, and omits Linux-specific nuances or examples.
Recommendations
- Alternate the order of Windows and Linux references throughout the documentation, or list Linux first in some sections.
- Provide explicit Linux VM connection instructions, including authentication types (e.g., SSH key vs. password), and note any differences in the Bastion Developer experience for Linux VMs.
- Include Linux-specific keyboard shortcuts and troubleshooting tips for remote sessions, similar to the Windows guidance.
- Add examples or screenshots showing the Bastion Developer experience when connecting to a Linux VM.
- Reference Linux tools and workflows (e.g., SSH clients, terminal usage) where appropriate, and clarify any differences in clipboard or audio support for Linux VMs.
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 exhibits a mild Windows bias. Windows VM creation is listed before Linux in prerequisites, and Windows-specific details (such as RDP port 3389 and keyboard shortcuts for Windows VMs) are given more prominence and detail. There are no Linux-specific connection examples, troubleshooting tips, or equivalent keyboard shortcut guidance for Linux VMs. The documentation references Windows tools and patterns (RDP, Windows keyboard shortcuts) without offering Linux alternatives.
Recommendations
- Alternate the order of Windows and Linux VM creation links to avoid implicit prioritization.
- Provide Linux-specific connection details, such as SSH client usage, keyboard shortcuts, and troubleshooting tips for Linux VMs.
- Include examples or notes for connecting to Linux VMs (e.g., using SSH from various platforms, clipboard integration, etc.).
- Mention Linux-specific ports and tools with equal detail as Windows (e.g., clarify SSH port usage, offer guidance for Linux desktop environments if relevant).
- Add parity for keyboard shortcut documentation for Linux VMs and clients.
Bastion
Create a shareable link for Azure Bastion
...zure-docs/blob/main/articles/bastion/shareable-link.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page for Azure Bastion's Shareable Link feature demonstrates Windows bias primarily by focusing on Azure portal GUI workflows and referencing PowerShell cmdlets for permissions management. There are no examples or instructions for Linux users (e.g., Azure CLI, Bash, or cross-platform tools), and PowerShell is mentioned as the method for managing permissions without Linux alternatives. The workflow assumes familiarity with Windows-centric tools and does not provide parity for Linux environments.
Recommendations
- Add equivalent Azure CLI and/or Bash examples for managing Bastion Shareable Links and permissions, alongside PowerShell cmdlets.
- Explicitly mention cross-platform alternatives to the Azure portal and PowerShell, such as Azure CLI, for all major operations.
- Include screenshots or instructions for Linux/macOS users where applicable, especially for command-line workflows.
- Ensure that references to tools and commands do not prioritize Windows solutions unless there is a technical limitation.
- Clarify that the feature is accessible and manageable from Linux environments, and provide guidance for those users.
Bastion
Enable remote work by using Azure Bastion
...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 mentioning it before Azure CLI, which is more commonly used on Linux. There are no explicit Linux or SSH client examples, and Windows-centric tools (PowerShell) are highlighted without equivalent Linux command-line or GUI alternatives.
Recommendations
- Include explicit SSH client usage examples for Linux and macOS users.
- List Azure CLI before PowerShell or present both equally to avoid implying preference.
- Add guidance for configuring Azure Bastion access from Linux desktops, including terminal and GUI tools.
- Mention cross-platform tools (e.g., OpenSSH, Remmina, GNOME Terminal) alongside Windows tools.
- Ensure screenshots and walkthroughs are available for both Windows and Linux environments.
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
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias, primarily through its repeated use of PowerShell for Azure Key Vault setup and secret management, with no equivalent Linux shell (bash) or cross-platform CLI examples. References to creating a Key Vault and storing SSH keys consistently point to PowerShell-based instructions, and there is no mention of Linux-native tools or workflows for these tasks. This may hinder Linux users who prefer bash or other non-Windows environments.
Recommendations
- Provide bash/Azure CLI examples alongside PowerShell for all Key Vault and SSH key management tasks.
- Include explicit instructions or links for Linux users to create and manage Azure Key Vault resources using bash or the Azure CLI.
- Avoid referencing only PowerShell in quick-start links; offer parity with bash/CLI documentation.
- Clarify that all steps can be performed from Linux, macOS, or Windows, and highlight any platform-specific considerations.
- Where possible, use cross-platform Azure CLI commands as the default, with PowerShell as an alternative.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-create-host-powershell.md
...ain/articles/bastion/bastion-create-host-powershell.md
High 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, which is primarily a Windows-centric tool. All code examples and step-by-step instructions use PowerShell commands, with no equivalent Azure CLI or Bash examples provided inline. References to VM creation link to Windows VM quickstarts first, and Linux VM creation is only mentioned in passing (for SSH port requirements). There is no demonstration of Linux-native tools or workflows, and the reader is implicitly expected to use PowerShell, which may not be available or preferred on Linux systems.
Recommendations
- Provide equivalent Azure CLI examples alongside PowerShell for all deployment steps, as Azure CLI is cross-platform and commonly used on Linux.
- Explicitly mention and link to Linux VM creation guides, not only Windows VM quickstarts.
- Add a section or callout for deploying Bastion using Bash or native Linux tools, or clarify how Linux users can run PowerShell (e.g., via Azure Cloud Shell or PowerShell Core).
- Ensure that connection steps and audio output instructions cover both Windows and Linux VM scenarios equally.
- Review and update example values and instructions to be OS-agnostic where possible, or provide parallel examples for both platforms.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-nsg.md
...s/azure-docs/blob/main/articles/bastion/bastion-nsg.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only a PowerShell script example for configuring NSG rules, which is Windows-centric. There are no equivalent examples for Linux users, such as Azure CLI or Bash scripts. The use of PowerShell as the sole automation method and lack of cross-platform tooling demonstrates a bias toward Windows environments.
Recommendations
- Add equivalent Azure CLI and/or Bash script examples for configuring NSG rules to support Linux and macOS users.
- Include a note clarifying that PowerShell is available cross-platform, but provide explicit instructions or examples for Linux environments.
- Present cross-platform tools (e.g., Azure CLI) before or alongside PowerShell to ensure parity and inclusivity.
- Review screenshots and UI instructions to ensure they do not assume a Windows environment.
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
Missing Linux Example
Powershell Heavy
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 examples. Windows-centric tools (Azure portal and PowerShell) are mentioned first and exclusively, while Linux equivalents (such as Azure CLI or Bash scripting) are absent.
Recommendations
- Add equivalent instructions for configuring host scaling using Azure CLI, which is commonly used on Linux and macOS.
- Include examples or links for Bash scripting or automation for host scaling.
- Ensure that alternative methods (PowerShell, CLI, REST API) are presented together, rather than prioritizing Windows-centric tools.
- Explicitly mention cross-platform compatibility and provide parity in examples for both Windows and Linux users.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/kerberos-authentication-portal.md
...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 page exhibits a strong Windows bias. All examples, instructions, and templates exclusively reference Windows VMs, Windows Server, and Windows 10. Kerberos setup is described only in the context of Active Directory Domain Controllers running on Windows Server. All automation and configuration scripts use PowerShell, and references to tools and settings (such as Group Policy Editor and NTLM restrictions) are Windows-specific. There are no examples or guidance for configuring Kerberos authentication with Linux VMs, Linux-based domain controllers (such as Samba), or using Linux tools and commands. The documentation also links only to Windows-centric resources and does not mention Linux equivalents.
Recommendations
- Add parallel instructions and examples for configuring Kerberos authentication with Linux VMs, including joining Linux VMs to an Active Directory domain or a Samba domain controller.
- Provide ARM template parameters and examples for deploying Linux-based domain controllers (e.g., Samba) and Linux client VMs.
- Include Linux command-line examples (e.g., using kinit, realm, sssd, or adcli) for domain joining and Kerberos verification.
- Reference Linux documentation for Kerberos and domain joining, such as official Samba and MIT Kerberos guides.
- Clarify any Azure Bastion limitations regarding Linux Kerberos authentication, and if supported, document the steps and troubleshooting for Linux scenarios.
- Balance PowerShell examples with Bash or shell script equivalents for Linux deployments.
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 page demonstrates a Windows bias by consistently listing Azure PowerShell as a primary configuration method, providing PowerShell-specific parameter names, and omitting Linux-specific tools or examples (such as Bash scripts or references to Linux-native management patterns). While Azure CLI is mentioned, there is no parity in example depth or explicit Linux guidance. No Linux-specific tools (e.g., cloud-init, shell scripts) are referenced, and the ordering of configuration methods often places Windows-centric tools before cross-platform or Linux-native approaches.
Recommendations
- Provide explicit Linux/Bash examples for each configuration step, including sample shell scripts or command-line usage.
- Ensure Azure CLI examples are as detailed and prominent as PowerShell examples, with clear instructions for Linux environments.
- Add references to Linux-native tools (e.g., cloud-init, SSH configuration files) where relevant.
- Reorder configuration method tables to list cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell).
- Include troubleshooting or usage notes for Linux users, such as differences in authentication or connectivity patterns.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/native-client.md
...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 page demonstrates a Windows bias by presenting Windows native client connection instructions and examples before Linux equivalents, using Windows terminology (RDP, Windows native client) more prominently, and providing more detailed links and instructions for Windows scenarios. Linux instructions are present but less emphasized, and there is a lack of parity in example depth and ordering.
Recommendations
- Present Linux and Windows instructions in parallel, ensuring equal prominence and detail for both platforms.
- Avoid listing Windows examples first in tables and next steps; alternate or group by scenario instead.
- Provide explicit Linux screenshots and walkthroughs where Windows screenshots are shown.
- Include examples for popular Linux tools (e.g., OpenSSH, Remmina for RDP) and clarify any platform-specific limitations.
- Ensure that all features and limitations are described for both Windows and Linux clients, not just Windows.
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
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific ports (3389) and keyboard shortcuts before Linux equivalents, providing detailed Windows VM connection instructions and examples (such as CTRL+ALT+END for Windows), and mentioning Windows VM creation before Linux in the prerequisites. There are no Linux-specific connection instructions, keyboard shortcuts, or troubleshooting tips, and the documentation lacks parity in examples and guidance for Linux users.
Recommendations
- Provide Linux-specific connection instructions, including details on SSH session behavior and relevant keyboard shortcuts.
- List Linux VM creation and connection examples alongside or before Windows examples to ensure parity.
- Include troubleshooting tips for Linux VM connections, such as handling SSH authentication, clipboard, and audio redirection.
- Explicitly mention port 22 for Linux VMs in connection steps and provide guidance for Linux desktop environments.
- Balance references to Windows and Linux tools and patterns throughout the documentation.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/secure-bastion.md
...zure-docs/blob/main/articles/bastion/secure-bastion.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing RDP and Windows-specific authentication (Kerberos) before mentioning SSH and Linux. Examples and guidance for Kerberos authentication are exclusively for Windows VMs, while Linux connections are referenced only in passing or as links. There is a lack of Linux-specific examples, tools, or troubleshooting steps, and Windows-centric terminology (RDP, Kerberos, domain-joined) is prioritized. No PowerShell-heavy bias is present, but Windows tools and patterns are mentioned more prominently than their Linux equivalents.
Recommendations
- Provide parallel Linux examples and guidance, such as SSH key management, Linux VM session monitoring, and troubleshooting steps.
- Include explicit references to Linux authentication methods (e.g., PAM, LDAP) and how they integrate with Bastion.
- Balance the order of presentation so that Linux and Windows scenarios are given equal prominence.
- Add Linux-specific security recommendations, such as hardening SSH configurations and using Linux-native logging/monitoring tools.
- Ensure that links and references to Linux documentation are as visible and accessible as those for Windows.
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 page prioritizes Windows workflows by presenting Windows RDP and native client instructions first, referencing Windows-specific tools (MSTSC), and omitting explicit Linux file transfer examples (e.g., SCP/SSH from Linux). Linux instructions are less detailed and appear after Windows content, with no concrete Linux command-line examples provided.
Recommendations
- Add explicit Linux-native client examples, such as using SCP or SFTP from a Linux terminal.
- Provide step-by-step instructions for Linux users, including sample commands and screenshots if possible.
- Mention Linux tools (e.g., Remmina, GNOME Terminal) alongside Windows tools like MSTSC.
- Balance the order of sections so that Linux and Windows instructions are presented with equal prominence.
- Clarify which steps are platform-agnostic and which are platform-specific, to help users on both OSes.