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 76-100 of 222 flagged pages
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 page demonstrates a Windows-first bias by prioritizing RDP (a Windows protocol) in both the portal and CLI examples, listing it before SSH. There are no explicit Linux-specific examples or screenshots, and the instructions for connecting via SSH (the typical Linux method) are minimal and lack detail compared to RDP. There are no references to Linux tools or workflows, and the documentation does not provide parity in guidance for Linux users.
Recommendations
- Provide Linux-specific examples and screenshots, especially for SSH connections, including details on using SSH keys and common Linux authentication patterns.
- List SSH (Linux) and RDP (Windows) connection methods with equal prominence, or alternate their order in examples.
- Include instructions for connecting from Linux/macOS terminals, not just via Azure CLI, and mention any required tools or dependencies.
- Clarify any differences in experience or prerequisites for Linux users (e.g., SSH agent usage, file permissions for private keys).
- Add troubleshooting tips relevant to Linux environments, such as SSH key permissions or common SSH errors.
Create Pull Request
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
Summary
The documentation demonstrates a mild Windows bias. Windows VMs and tools are mentioned first in several places, such as in the prerequisites (port 3389 for Windows is listed before port 22 for Linux), and the example links for creating VMs list Windows before Linux. Keyboard shortcut guidance is focused on Windows VMs, with only a brief mention of Mac clients connecting to Windows VMs. There are no explicit Linux command-line or desktop usage examples, and the guidance for connecting and using the Bastion service is written with Windows-centric terminology and scenarios.
Recommendations
- Alternate the order of Windows and Linux references throughout the documentation to avoid always listing Windows first.
- Provide explicit Linux desktop and keyboard shortcut examples, especially for remote desktop scenarios (e.g., how to send Ctrl+Alt+Del to a Linux VM, or common Linux desktop shortcuts).
- Include screenshots or walkthroughs for both Windows and Linux VMs to ensure parity.
- When referencing ports, clarify that 3389 is for Windows (RDP) and 22 is for Linux (SSH), and consider listing them in varying order or together.
- Add a section or callout for connecting to Linux VMs, including any differences in authentication, desktop environments, or troubleshooting.
- Ensure that all instructions and terminology are equally applicable to both Windows and Linux users.
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 Windows and PowerShell usage for deploying Azure Bastion. All code examples and setup instructions use Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples provided inline. References to creating VMs link to Windows-specific quickstarts first, and Linux VM creation is only mentioned in passing. There are no Linux or Bash-specific instructions or examples for deploying Bastion, and the workflow assumes familiarity with PowerShell and Windows tooling.
Recommendations
- Add parallel Azure CLI (az) command examples for each PowerShell example, ideally side-by-side or in a dedicated section.
- Include explicit instructions and links for deploying Bastion from Linux/macOS environments using Azure CLI.
- When referencing VM creation, provide both Windows and Linux quickstart links equally, or link to a cross-platform VM creation guide.
- Clarify that Azure PowerShell can be used on any platform, but highlight Azure CLI as the primary cross-platform tool.
- Add a section or callout for Bash/terminal users, ensuring parity in the deployment workflow.
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
Windows Tools
Summary
The documentation page is heavily focused on Windows and PowerShell. All deployment examples use Azure PowerShell, with no Azure CLI or Bash/Linux shell examples provided inline. The 'Create a VM' section links only to Windows VM creation guides, and the overall workflow assumes familiarity with Windows tools and patterns. Linux users are not given equivalent step-by-step guidance, and Linux command-line tools are not mentioned or demonstrated.
Recommendations
- Add parallel Azure CLI (az) examples for all deployment steps, with Bash syntax, to provide Linux parity.
- In the 'Create a VM' section, link to both Windows and Linux VM creation quickstarts.
- Where PowerShell is mentioned, clarify that Azure CLI is also supported and provide links or tabs for both.
- Review terminology and instructions to ensure they are not Windows-specific (e.g., avoid assuming use of PowerShell or Windows-only tools).
- Consider using tabbed content blocks to allow users to select their preferred platform (PowerShell, Azure CLI, Portal).
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
Windows Tools
Summary
The documentation consistently lists Azure PowerShell (a Windows-centric tool) before Azure CLI in configuration tables, and provides PowerShell-specific parameter names and links. There is a notable emphasis on PowerShell as a primary automation/configuration method, which is more familiar to Windows users. While Azure CLI is mentioned, it is always listed after PowerShell, and there are no Linux-specific tools or shell examples (e.g., Bash scripts). No explicit Linux commands, patterns, or troubleshooting are provided.
Recommendations
- Alternate the order of Azure CLI and PowerShell in tables and examples, sometimes listing CLI first to avoid Windows-first bias.
- Provide explicit Bash shell or Linux-native command examples where relevant, especially for CLI usage.
- Include links to both PowerShell and CLI documentation equally, and ensure parity in depth and clarity.
- Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Where possible, add Linux-specific notes or troubleshooting tips, especially for common configuration scenarios.
- Consider including a 'Platform considerations' section outlining any differences or tips for Linux vs. Windows users.
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 demonstrates a Windows bias in several areas. Browser recommendations are Windows-centric, with Windows browsers mentioned first and Mac as a secondary consideration. Keyboard layout configuration instructions are provided only for Windows, with no equivalent guidance for Linux or Mac users. The documentation references Windows-specific tools and patterns (such as RDP and Windows keyboard shortcuts) without offering parallel Linux examples or alternatives. There are no explicit Linux command-line or SSH examples, nor instructions for setting up keyboard layouts or other OS-specific tasks on Linux.
Recommendations
- Provide browser recommendations and instructions for Linux users, including supported browsers and any known issues.
- Include instructions for configuring keyboard layouts on Linux and Mac, not just Windows.
- When referencing RDP, also mention SSH and provide examples for both Windows and Linux clients.
- Add parity in native client connection instructions, ensuring both Windows and Linux workflows are described.
- Where Windows-specific shortcuts or settings are mentioned, provide equivalent steps for Linux and Mac where possible.
- Explicitly state support and any limitations for Linux VMs and Linux client environments.
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 subtle Windows bias by prioritizing RDP (a Windows protocol) in both the UI and command-line examples, listing it before SSH. There are no explicit Linux-specific instructions or examples, such as using native SSH clients or Linux credential formats. The documentation assumes familiarity with RDP and Windows-style authentication, and does not provide Linux/Unix-specific guidance or screenshots.
Recommendations
- Provide Linux-specific examples, such as connecting from a Linux terminal using SSH, including sample commands and credential handling.
- Balance the order of protocol presentation: alternate or start with SSH (commonly used for Linux VMs) before RDP.
- Include screenshots or walkthroughs from both Windows and Linux environments, demonstrating the connection process from each.
- Clarify credential requirements for both Windows (username/password) and Linux (username/SSH key) scenarios.
- Mention and link to Linux-native tools (e.g., OpenSSH client) and how they interact with Azure Bastion.
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 is heavily biased towards Windows environments. All examples, templates, and verification steps assume Windows VMs, Windows Server as the domain controller, and Windows-specific tools (such as Local Group Policy Editor and PowerShell). There are no instructions or examples for configuring Kerberos with Linux VMs, Linux-based domain controllers (such as Samba/FreeIPA), or using Linux-native tools. The ARM template provisions only Windows VMs, and all automation scripts are PowerShell-based.
Recommendations
- Add parallel instructions and examples for Linux VMs, including how to configure Kerberos authentication for Linux-based systems accessed via Bastion.
- Provide guidance for deploying and configuring a Linux-based domain controller (e.g., Samba/FreeIPA) and joining Linux VMs to the domain.
- Include Linux command-line examples (e.g., using kinit, realm, or sssd) for verifying Kerberos authentication.
- Offer an alternative ARM/Bicep template or scripts that provision Linux VMs and automate their domain join and Kerberos configuration.
- Reference Linux documentation and tools alongside Windows ones, and avoid assuming Windows as the default platform.
- Clarify any Azure Bastion limitations regarding Linux Kerberos support, if applicable, and document workarounds or roadmap.
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 demonstrates a Windows bias by referencing Windows VMs and tools first, providing keyboard shortcut examples only for Windows VMs, and mentioning Windows-specific ports and behaviors before Linux equivalents. There are no detailed Linux-specific examples or instructions, and Linux user scenarios are not equally represented in the connection or troubleshooting guidance.
Recommendations
- Provide Linux-specific examples alongside Windows examples, such as keyboard shortcuts for Linux desktops when accessed via Bastion.
- List Linux and Windows ports together or alternate their order to avoid always mentioning Windows first.
- Include screenshots or descriptions of what users should expect when connecting to Linux VMs, not just Windows.
- Add troubleshooting tips or notes relevant to Linux users, such as clipboard or keyboard behavior differences.
- Ensure that references to creating VMs, connecting, and managing are balanced between Windows and Linux, with equal detail and prominence.
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 mild Windows bias. In the prerequisites, the link to the Windows VM quickstart is listed before the Linux VM quickstart. In the required inbound ports section, the Windows port (3389) is listed before the Linux port (22). In the 'Connect to a VM' section, keyboard shortcut examples are provided only for connecting to Windows VMs, with no equivalent Linux examples or discussion of Linux-specific connection nuances. There are no explicit Linux command-line or SSH examples, and the only OS-specific details are for Windows.
Recommendations
- Alternate the order of Windows and Linux references throughout the documentation, or list Linux first in some sections to balance representation.
- In the 'Connect to a VM' section, provide examples or notes for connecting to Linux VMs, such as SSH session behaviors, keyboard shortcuts, or clipboard usage.
- Include Linux-specific tips or troubleshooting steps, especially for users connecting from Linux or Mac clients.
- Ensure parity in all examples and explanations, such as providing both RDP (Windows) and SSH (Linux) connection walkthroughs.
- Where keyboard shortcuts are discussed for Windows, add equivalent information for Linux VMs (e.g., how to send signals like Ctrl+Alt+Del to a Linux VM, if relevant).
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 a Windows bias by listing PowerShell as a primary configuration method before Azure CLI, which is more commonly used on Linux. There are no explicit Linux or SSH client examples, and the documentation does not mention Linux tools or workflows, focusing instead on Windows-centric tools and patterns.
Recommendations
- Include explicit Linux/SSH client examples for accessing Azure VMs via Bastion.
- Present Azure CLI instructions before or alongside PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
- Mention and provide examples for Linux-native tools (e.g., SSH from a Linux terminal) when discussing remote access.
- Ensure parity in documentation by referencing both Windows and Linux workflows equally in all sections.
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 demonstrates a Windows-first bias by presenting Windows/RDP instructions and tools (MSTSC, Copy/Paste) before Linux/SSH equivalents. The Windows native client workflow is described in detail, while Linux workflows are less emphasized and lack explicit, step-by-step Linux-native examples. The use of Windows-specific terminology and tools (e.g., MSTSC, right-click Copy/Paste) further centers the Windows experience.
Recommendations
- Provide Linux-native client instructions and examples with equal prominence and detail as Windows instructions.
- Include explicit step-by-step examples for Linux users, such as using Remmina or rdesktop for RDP, and detailed SCP/SFTP workflows.
- Avoid Windows-specific terminology (e.g., 'right-click', 'Copy and Paste') without offering Linux equivalents.
- Structure the documentation so that Windows and Linux workflows are presented in parallel sections, or alternate which platform is described first.
- Reference Linux-native tools (Remmina, KRDC, rdesktop, etc.) and provide links to their documentation.
- Clarify that file transfer via RDP is possible from Linux clients (if supported), or explicitly state limitations.
Bastion
Quickstart: Deploy Azure Bastion to a virtual network using an ARM template
.../main/articles/bastion/quickstart-host-arm-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias in its 'Next steps' section, where only Windows virtual machine creation and Windows RDP connection guides are linked. There are no references or examples for Linux virtual machines or SSH connections, which are common scenarios for Linux/macOS users. The deployment instructions themselves are platform-neutral, relying on the Azure portal, but the follow-up guidance excludes Linux users.
Recommendations
- Add links to Linux virtual machine creation guides in the 'Next steps' section.
- Include instructions or references for connecting to Linux VMs via SSH using Azure Bastion.
- Ensure parity in examples and guidance for both Windows and Linux VM scenarios throughout the documentation.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias, primarily by referencing Windows-specific features and examples before Linux equivalents. For instance, the 'Copy and paste' section links only to a Windows VM guide, with no mention of Linux VM support or instructions. There is no explicit mention of Linux/macOS workflows or parity in features such as copy/paste, file transfer, or audio.
Recommendations
- Add equivalent documentation and links for Linux VMs (e.g., 'Copy and paste - Linux VMs').
- Explicitly state feature availability and limitations for Linux/macOS clients and VMs.
- Ensure that examples and guides are provided for both Windows and Linux platforms, or clarify when features are Windows-only.
- Where possible, present cross-platform instructions or indicate differences in feature support.
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 using PowerShell commands. There are no equivalent Bash, Azure CLI, or Linux/macOS shell examples provided. References to VM creation link only to Windows VM guides, and connection instructions prioritize RDP (Windows) before SSH (Linux). This creates friction for Linux/macOS users who may prefer Bash or Azure CLI and need Linux-specific VM creation guidance.
Recommendations
- Add parallel 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.
- Present both RDP (Windows) and SSH (Linux) connection instructions with equal prominence.
- Clearly indicate that PowerShell commands can be run on macOS/Linux via Azure Cloud Shell, but also provide native Bash/CLI alternatives.
- Consider restructuring the documentation to present CLI and PowerShell options side-by-side, or provide a selector for preferred platform.
Bastion
About Azure Bastion configuration settings
...s/blob/main/articles/bastion/configuration-settings.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation consistently lists Azure PowerShell as a primary configuration method alongside Azure portal and Azure CLI, but does not provide any Linux/macOS-specific examples or mention Bash scripting. PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. In some sections, Azure PowerShell is listed before Azure CLI, and host scaling configuration is only documented for PowerShell and portal, omitting CLI or Linux-native instructions.
Recommendations
- Ensure Azure CLI examples are provided and documented for all configuration tasks, especially host scaling.
- Present Azure CLI and Azure PowerShell methods with equal prominence, or list CLI first to avoid Windows-first bias.
- Add explicit Bash shell examples for Linux/macOS users where relevant.
- Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Where PowerShell is referenced, note alternatives for non-Windows platforms.
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 resources: all links and instructions reference PowerShell and Azure CLI, with no explicit Linux/macOS shell examples or guidance. The 'Create a key vault' link points to a PowerShell-based quickstart, and instructions for storing SSH keys in Key Vault mention PowerShell and Azure CLI, but do not provide bash or Linux-native command examples. This may create friction for Linux/macOS users unfamiliar with PowerShell or Windows-centric tooling.
Recommendations
- Provide explicit bash/Azure CLI examples for creating and managing Key Vault resources, including storing SSH keys as secrets.
- Update links to include Linux/macOS-friendly quickstarts, not just PowerShell.
- Clarify that Azure CLI is cross-platform and provide sample commands for Linux/macOS terminals.
- Where PowerShell is mentioned, offer equivalent bash or shell commands for Linux users.
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, which is a Windows-centric tool. There are no equivalent examples or guidance for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). The script section is labeled 'Powershell Script' and is presented as the sole automation method, implicitly prioritizing Windows tooling and leaving Linux users without direct instructions.
Recommendations
- Add equivalent Azure CLI examples for all NSG rule creation steps.
- Include Bash script snippets for Linux/macOS automation.
- Reference REST API or ARM template methods for cross-platform automation.
- Clearly state that PowerShell is just one option and provide links to other platform-neutral tools.
- Present examples for Windows and Linux/macOS side-by-side or in parallel sections.
Bastion
Create a shareable link for Azure Bastion
...zure-docs/blob/main/articles/bastion/shareable-link.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is heavily oriented around the Azure portal GUI and does not provide any CLI examples (such as Azure CLI, Bash, or PowerShell). While it mentions PowerShell cmdlets for permissions, it does not provide equivalent Azure CLI or REST API instructions, nor does it clarify cross-platform approaches for Linux/macOS users. The workflow assumes use of the Azure portal, which is platform-agnostic, but the lack of CLI or scriptable examples creates friction for Linux users who may prefer or require non-GUI automation.
Recommendations
- Add Azure CLI and/or REST API examples for enabling the Shareable Link feature, creating, viewing, and deleting shareable links.
- List PowerShell and Azure CLI (or Bash) commands side by side when discussing permissions and resource management.
- Clarify that all portal steps are accessible from any OS/browser, but provide automation/script options for cross-platform parity.
- Explicitly mention Linux/macOS compatibility and provide links to relevant CLI documentation.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes configuration and usage via the Azure portal UI, which is platform-agnostic, but it implicitly assumes a Windows-centric workflow by referencing RDP sessions and graphical session recording without mentioning Linux/macOS remote protocols (like SSH or xrdp). There are no examples or guidance for Linux/macOS users, nor are CLI or shell-based instructions provided, which are more common in Linux environments.
Recommendations
- Add explicit instructions or examples for Linux/macOS users, such as how session recording works for SSH sessions or Linux VMs.
- Include Azure CLI, PowerShell, and Bash examples for configuring Bastion session recording and storage account settings.
- Clarify whether session recording supports SSH sessions to Linux VMs and how those recordings can be accessed/viewed.
- Mention any limitations or differences for Linux/macOS users (e.g., if only RDP is supported, state this clearly).
Bastion
VNet peering and Azure Bastion architecture
.../azure-docs/blob/main/articles/bastion/vnet-peering.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page references Windows virtual machines before Linux equivalents in the deployment overview, and links only to Windows VM creation instructions. There are no Linux-specific examples or guidance, which may cause friction for Linux users seeking parity.
Recommendations
- Include links to both Windows and Linux VM creation guides in the deployment overview.
- Ensure connection instructions reference both RDP (Windows) and SSH (Linux) scenarios, with appropriate links.
- Add examples or notes clarifying Bastion usage for Linux VMs, including SSH connection workflows.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page presents Windows and RDP file transfer instructions first, with detailed steps for using the Windows native client (MSTSC) and copy-paste. Linux/macOS instructions are grouped in a secondary section, with less detail and only referencing SCP for SSH transfers. Windows tools and patterns (MSTSC, RDP, right-click copy-paste) are mentioned exclusively and before Linux equivalents. There is a slight emphasis on Windows workflows, and Linux/macOS users may need to infer some steps.
Recommendations
- Provide Linux/macOS-specific examples and step-by-step instructions for file transfer, including using native SSH clients and SCP/SFTP.
- Include explicit instructions for macOS users, such as using Terminal and SCP/SFTP commands.
- Balance the order of presentation: introduce Windows and Linux/macOS workflows side-by-side or in parallel sections.
- Mention and link to common Linux/macOS tools (e.g., GNOME Terminal, iTerm2, FileZilla) where appropriate.
- Clarify any differences in experience or limitations for non-Windows platforms.
Bastion
Enable remote work by using Azure Bastion
...cs/blob/main/articles/bastion/work-remotely-support.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation references PowerShell as a primary configuration method and lists it before Azure CLI, which is more commonly used on Linux/macOS. There are no explicit Linux/macOS examples or mentions of SSH clients or Linux-specific workflows, and the examples lean toward Windows-centric tools and patterns.
Recommendations
- Include explicit Linux/macOS configuration examples, such as using SSH from a Linux terminal.
- Mention Linux-native tools and workflows alongside PowerShell, such as Bash scripts or Azure CLI usage on Linux.
- Ensure that Azure CLI examples are given equal prominence and detail as PowerShell examples.
- Clarify that Azure Bastion supports both RDP (Windows) and SSH (Linux/macOS) and provide examples for both.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. The 'Copy and paste' section explicitly links only to Windows VM instructions, with no mention of Linux VM equivalents or parity. Windows terminology (RDP) is referenced before SSH, and Windows examples are prioritized in links and notes. There are no Linux/macOS-specific examples or guidance for features like copy/paste, file transfer, or audio.
Recommendations
- Add equivalent documentation and links for Linux VMs, especially for features like copy/paste and file transfer.
- Ensure examples and instructions cover both RDP (Windows) and SSH (Linux/macOS) scenarios equally.
- Where features differ by OS, clearly state limitations or alternatives for Linux/macOS users.
- Present examples for Windows and Linux/macOS side-by-side, or alternate which OS is shown first.
Bastion
VNet peering and Azure Bastion architecture
.../azure-docs/blob/main/articles/bastion/vnet-peering.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page references Windows virtual machines before Linux equivalents, notably in the deployment overview step and in the link to connecting via Bastion. There are no explicit examples or instructions for Linux VM connectivity, nor are Linux-specific resources linked or mentioned. This creates a subtle bias towards Windows users, as Linux users must infer parity or seek additional documentation.
Recommendations
- Include links to both Windows and Linux VM quick-create guides in the deployment overview step.
- Provide explicit instructions or references for connecting to Linux VMs via Azure Bastion (e.g., SSH guidance).
- Ensure that connection examples and walkthroughs cover both RDP (Windows) and SSH (Linux) scenarios.
- Mention Linux VM support explicitly in the architecture and deployment sections to reassure parity.