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 101-125 of 222 flagged pages
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on deploying Azure Bastion using PowerShell, with all code examples and instructions tailored for PowerShell users. There are no equivalent Bash, Azure CLI, or Linux/macOS shell examples provided. References to VM creation and connection steps link to Windows-centric articles first, and Linux-specific guidance is minimal or absent. This creates friction for Linux/macOS users who may prefer or require Azure CLI or Bash-based workflows.
Recommendations
- Add parallel Azure CLI/Bash examples for all deployment steps, including resource group, VNet, subnet, public IP, and Bastion creation.
- Provide explicit instructions for running commands on Linux/macOS, including prerequisites and environment setup.
- Ensure links to VM creation and connection guides include both Windows and Linux options, with equal prominence.
- Consider a cross-platform section or tabbed code blocks to allow users to select their preferred environment (PowerShell, CLI, Bash).
Create Pull Request
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page is generally focused on connecting to Linux VMs via Azure Bastion through the Azure portal, which is a cross-platform experience. However, in sections describing how to create and manage Azure Key Vault resources, only PowerShell and Azure CLI are mentioned, with links and instructions defaulting to PowerShell (a Windows-centric tool). There are no explicit Linux/macOS shell examples (e.g., Bash), and the guidance for storing SSH keys in Key Vault references PowerShell first and exclusively in some places. This creates friction for Linux/macOS users who may prefer Bash or native Azure CLI usage.
Recommendations
- Provide explicit Bash/Azure CLI examples for creating and managing Key Vault resources, alongside PowerShell.
- Ensure that links to 'Create a key vault' and similar tasks include both PowerShell and Bash/Azure CLI options.
- Clarify that Azure CLI is cross-platform and provide example commands for Linux/macOS users.
- Avoid referencing PowerShell as the default or only method for tasks that can be performed with Azure CLI or Bash.
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 Examples Priority
Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Windows native client examples and instructions are listed first in tables and 'Next steps', with Linux equivalents mentioned second. The page references Windows-specific tools (RDP) and provides more direct links and details for Windows users. Linux instructions are present but less emphasized, and there is no explicit parity in example ordering or depth.
Recommendations
- Alternate the order of Windows and Linux examples in tables and 'Next steps' to avoid implicit prioritization.
- Provide equally detailed step-by-step instructions and screenshots for Linux/macOS users, matching the Windows sections.
- Include explicit macOS examples where relevant, not just Linux.
- Add a summary section clarifying that all major OS platforms are supported and linking to their respective guides equally.
- Ensure that references to tools (e.g., RDP, SSH) are balanced with Linux/macOS equivalents and not described as default or primary.
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 creating 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 users on Linux or macOS platforms. There is no mention of cross-platform alternatives, and the script is presented as the primary method for automation.
Recommendations
- Add Azure CLI examples for NSG rule creation, which are fully cross-platform and work on Linux/macOS.
- Include Bash script snippets or instructions for users who prefer shell scripting.
- Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell must be used, and provide installation guidance.
- Present cross-platform methods (Azure CLI, REST API) before or alongside PowerShell examples to avoid Windows-first bias.
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 consistently lists Azure PowerShell as a primary configuration method, with explicit parameter examples, while Azure CLI is present but less emphasized. In several configuration tables, PowerShell is listed before CLI, and only PowerShell-specific links are provided for some advanced features (e.g., host scaling). There are no Linux/macOS-specific examples or notes, and no mention of Bash scripting or Linux-native tools. This may create friction for Linux/macOS users who prefer CLI or need parity in examples and guidance.
Recommendations
- Provide explicit Bash/Azure CLI examples for all configuration steps, especially for advanced features like host scaling.
- List Azure CLI before PowerShell in tables to avoid implicit Windows-first bias.
- Add notes or sections clarifying that all steps can be performed on Linux/macOS using Azure CLI.
- Include links to CLI documentation for advanced features, not just PowerShell.
- Where PowerShell parameters are shown, provide equivalent CLI flags and example commands.
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 provides next steps and examples focused exclusively on Windows virtual machines, with links to Windows VM creation and RDP connection guides. There are no Linux or macOS-specific instructions, examples, or references, which may leave non-Windows users without clear guidance for similar tasks.
Recommendations
- Add parallel next steps for Linux virtual machines, such as 'Quickstart: Create a Linux virtual machine in the Azure portal' and 'Create an SSH connection to a Linux VM using Azure Bastion'.
- Include example values and screenshots for Linux VM scenarios where relevant.
- Ensure that references to VM connection methods include both RDP (Windows) and SSH (Linux/macOS) options.
- Review the documentation for any terminology or instructions that assume a Windows environment and generalize them where possible.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively references the Azure portal UI and does not provide any command-line examples, such as Azure CLI, PowerShell, or Bash. There are no instructions or examples for Linux/macOS users, nor is there mention of cross-platform tools or workflows. All steps are described in terms of portal navigation, which is platform-agnostic but implicitly assumes a graphical environment, commonly associated with Windows. There is no explicit bias toward Windows tools, but the lack of CLI or Linux-specific guidance creates friction for non-Windows users.
Recommendations
- Add Azure CLI and/or Bash examples for all major steps, such as enabling session recording, configuring storage containers, and uploading SAS URLs.
- Include PowerShell examples for parity, but ensure CLI/Bash examples are presented alongside or before them.
- Explicitly mention that all steps can be performed from Linux/macOS using CLI tools and provide links to relevant cross-platform documentation.
- Clarify any portal-only limitations and suggest alternatives for users who prefer or require command-line workflows.
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 exclusively describes using the Azure portal GUI for all tasks and references PowerShell cmdlets for permissions, but does not mention or provide examples for Linux/macOS users (such as Azure CLI or Bash). There are no Linux-specific instructions, nor is there parity in command-line tooling guidance.
Recommendations
- Add Azure CLI examples for enabling, creating, and deleting shareable links, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include instructions or screenshots for using the Azure portal from non-Windows environments, if relevant.
- Reference Bash or shell scripting alternatives where PowerShell is mentioned, or clarify that the PowerShell cmdlets can be run via Azure Cloud Shell (which supports Bash and PowerShell).
- Explicitly state that the steps are platform-agnostic if true, or provide platform-specific guidance as needed.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page presents Windows/RDP file transfer instructions first, with detailed steps for the Windows native client and MSTSC. Windows tools and patterns (right-click, Copy/Paste) are described in detail, while Linux/macOS instructions are grouped together and rely on generic SSH/SCP usage. There is a slight emphasis on Windows workflows and tools, and the Linux/macOS section is less detailed and appears second.
Recommendations
- Provide explicit Linux/macOS examples for file transfer, including step-by-step instructions for common native clients (e.g., Remmina, GNOME Terminal, macOS Terminal).
- Include screenshots or detailed guidance for Linux/macOS users similar to the Windows section.
- Balance the order of presentation by alternating or paralleling Windows and Linux/macOS instructions.
- Mention Linux/macOS tools by name (e.g., scp, sftp, Remmina) and provide usage notes.
- Clarify any platform-specific limitations or differences in file transfer workflows.
Bastion
VNet peering and Azure Bastion architecture
.../azure-docs/blob/main/articles/bastion/vnet-peering.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows virtual machine creation first and exclusively in the deployment overview, and by linking only to Windows-specific VM creation instructions. There are no Linux VM examples or links to Linux VM documentation, which may make it less accessible for users working with Linux-based environments.
Recommendations
- Include parallel instructions and links for creating Linux virtual machines alongside Windows VM instructions.
- Reference both Windows and Linux VM connection guides when describing how to connect via Azure Bastion.
- Ensure examples and walkthroughs mention both operating systems to provide parity and inclusivity for cross-platform users.
Bastion
Choose the right Azure Bastion SKU to meet your needs
...s/blob/main/articles/bastion/bastion-sku-comparison.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation presents VM connectivity features with Windows RDP listed before Linux SSH, and Windows RDP/SSH before Linux RDP/SSH. There are no platform-specific usage examples, but the feature tables and capacity metrics consistently mention Windows (RDP) before Linux (SSH), and do not provide parity in example detail or ordering. There is no mention of Linux-specific tools or workflows, and Linux RDP connectivity is only available in higher SKUs, while Windows RDP is available in all SKUs.
Recommendations
- Present Linux and Windows features in parallel, alternating order or grouping by protocol rather than OS.
- Provide explicit Linux usage examples (e.g., SSH, RDP from Linux clients) alongside Windows examples.
- Mention Linux-native tools and workflows (such as using Azure CLI from Linux, or Linux RDP clients) where relevant.
- Clarify feature availability for Linux and Windows equally, and explain any differences in support (e.g., why Linux RDP is only available in Standard/Premium SKUs).
- Ensure that documentation links and next steps include Linux-specific guides or tutorials.
Bastion
Enable remote work by using Azure Bastion
...cs/blob/main/articles/bastion/work-remotely-support.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a mild Windows bias by listing PowerShell as a primary configuration method before Azure CLI, and by not providing explicit Linux-centric examples or mentioning Linux tools. The focus on RDP (a Windows protocol) in the context of remote access also subtly prioritizes Windows scenarios, even though SSH (used for Linux) is mentioned. There are no explicit Linux command-line examples or references to Linux remote management tools.
Recommendations
- Add explicit Linux-centric examples, such as using SSH from a Linux terminal to connect via Azure Bastion.
- Mention Linux remote management tools (e.g., OpenSSH, native terminal commands) alongside PowerShell.
- Ensure that Azure CLI (which is cross-platform) is listed before or alongside PowerShell in configuration instructions.
- Include screenshots or walkthroughs for both Windows and Linux users in the portal and command-line sections.
- Clarify that Azure Bastion supports both RDP (Windows) and SSH (Linux) equally, with examples for each.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a specific troubleshooting section for Windows domain-joined VMs, but does not offer equivalent guidance for Linux VMs (e.g., troubleshooting SSH sign-in issues, domain integration, or file transfer specifics for Linux). The file transfer section mentions PowerShell and the Azure portal, but does not discuss Linux command-line tools or workflows. Windows scenarios are prioritized or exclusively addressed in some sections.
Recommendations
- Add troubleshooting guidance for Linux VMs, such as common SSH authentication issues, domain integration (e.g., with LDAP or Kerberos), and file transfer using Linux-native tools.
- Provide Linux-specific examples and command-line workflows alongside Windows instructions, especially in sections discussing sign-in and file transfer.
- Ensure parity in troubleshooting steps for both Windows and Linux environments, including error messages, credential formats, and client tool usage.
- Mention Linux equivalents (e.g., scp, sftp, rsync) when discussing file transfer, and clarify any platform-specific limitations or requirements.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page lists recent Azure Bastion features and updates, with a notable tendency to mention Windows/RDP-related features before Linux/SSH equivalents. For example, 'Microsoft Entra ID support for portal (RDP)' is listed before 'Microsoft Entra ID support for portal (SSH)', and the RDP feature is described as being in preview while the SSH feature is already generally available. There are no explicit Linux-specific examples, tools, or usage patterns highlighted, and the terminology (RDP, graphical session recording) is more closely associated with Windows environments.
Recommendations
- Ensure Linux/SSH features are given equal prominence and ordering as Windows/RDP features in release tables and documentation.
- Provide explicit examples and links for Linux usage (e.g., SSH tunneling, Linux client configuration) alongside Windows examples.
- Include references to Linux tools and patterns (such as OpenSSH, xterm, etc.) where relevant.
- Balance terminology so that both Windows and Linux remote access scenarios are described with equal detail and clarity.
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
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing Windows native client connection instructions and examples before Linux equivalents in both the main connection table and the 'Next steps' section. There is also a lack of detailed Linux-specific examples or screenshots, with Windows-centric instructions and visuals being more prominent.
Recommendations
- Present Linux and Windows instructions/examples in parallel or alternate order to avoid prioritizing Windows.
- Include Linux-specific screenshots and step-by-step instructions for configuring and connecting via native client.
- Expand the 'Next steps' section to explicitly link to Linux connection guides before or alongside Windows guides.
- Ensure parity in feature explanation and troubleshooting for both Windows and Linux clients.
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page demonstrates bias by omitting any OS-specific examples or guidance, but implicitly assumes a Windows-centric workflow by referencing RDP sessions and not mentioning SSH or Linux session types. There are no examples or instructions tailored for Linux users or SSH session recording, and the terminology and steps are oriented toward Windows/Azure Portal patterns, with no parity for Linux command-line or tooling.
Recommendations
- Include explicit instructions and examples for recording SSH sessions (common for Linux VMs) in addition to RDP.
- Add command-line examples using Azure CLI, Bash, or PowerShell for both Windows and Linux environments.
- Clarify whether session recording supports both RDP and SSH, and if there are differences in configuration or playback.
- Provide parity in screenshots and walkthroughs for Linux-based workflows (e.g., using Azure CLI on Linux to configure Bastion session recording).
- Mention any limitations or considerations specific to Linux/SSH sessions, if applicable.
Bastion
Copy and paste to and from a Windows virtual machine: Azure
...cs/blob/main/articles/bastion/bastion-vm-copy-paste.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is exclusively focused on Windows virtual machines, with all instructions, prerequisites, and examples referring only to Windows. There is no mention of Linux VMs, nor are there any Linux-specific examples or considerations provided. This creates a Windows-first bias and omits guidance for users working with Linux VMs.
Recommendations
- Add equivalent instructions and examples for Linux virtual machines, including any differences in clipboard behavior or limitations.
- Update the prerequisites section to mention both Windows and Linux VM scenarios.
- Clarify whether the Bastion clipboard feature works identically for Linux VMs, and provide troubleshooting steps or notes for common Linux desktop environments (e.g., GNOME, KDE).
- Include screenshots or step-by-step guides for Linux VM sessions where applicable.
- Ensure parity in documentation structure and detail between Windows and Linux VM sections.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page describes connecting to a Linux VM using RDP via Azure Bastion, but it demonstrates bias by focusing on RDP—a protocol and workflow historically associated with Windows. The page requires installation of xrdp (a Linux implementation of RDP) but does not mention or provide examples for native Linux remote access tools (such as SSH or VNC), nor does it provide Linux-specific client usage instructions. There are no examples of connecting from a Linux client, and the documentation does not address Linux-centric remote management patterns.
Recommendations
- Include examples and guidance for connecting to Linux VMs using SSH via Azure Bastion, which is the native and most common method for Linux remote management.
- Provide instructions for connecting from Linux client machines, including use of RDP clients available on Linux (e.g., Remmina, rdesktop, FreeRDP) and SSH clients.
- Mention and compare alternative remote desktop solutions for Linux (such as VNC, X2Go), and clarify when RDP/xrdp is preferable.
- Ensure parity in documentation by presenting Linux-native patterns and tools before or alongside Windows-centric ones.
- Add troubleshooting steps and configuration examples specific to Linux environments, including firewall and authentication considerations.
Bastion
Quickstart: Deploy Azure Bastion to a virtual network using an ARM template
.../main/articles/bastion/quickstart-host-arm-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where only Windows virtual machine creation and Windows RDP connection guides are linked. There are no examples or links for Linux VM creation or SSH connection via Bastion, and no Linux-specific tooling or patterns are mentioned throughout the page.
Recommendations
- Add links to Linux VM quickstart guides alongside the Windows VM links in the 'Next steps' section.
- Include instructions or examples for connecting to Linux VMs via Bastion (e.g., SSH) in the relevant sections.
- Ensure parity by mentioning both Windows and Linux scenarios when discussing Bastion usage.
- Where possible, provide screenshots or examples that reference Linux environments as well as Windows.
Bastion
Secure Your Azure Bastion Deployment
...zure-docs/blob/main/articles/bastion/secure-bastion.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by mentioning RDP (Windows) connectivity and features (such as Kerberos authentication for domain-joined Windows VMs) before or more prominently than SSH/Linux equivalents. While there are references to connecting to Linux VMs and storing SSH keys, the examples and guidance are generally Windows-centric, with Windows-specific features (Kerberos, RDP, domain-joined VMs) described in detail and linked before Linux alternatives. There are no explicit Linux command-line or tool examples, and Linux security patterns are not discussed with the same depth as Windows ones.
Recommendations
- Provide Linux-specific examples and guidance alongside Windows instructions, such as SSH configuration, Linux authentication methods, and Linux VM security best practices.
- Include links to documentation for connecting to Linux VMs and securing Linux environments with Azure Bastion in sections where Windows features are described.
- Balance the coverage of Windows and Linux tools and patterns, ensuring that Linux equivalents (e.g., SSH key management, Linux session recording, Linux authentication) are given equal prominence and detail.
- Add explicit Linux command-line examples (e.g., using SSH from Linux/macOS terminals) and reference Linux-native security tools where relevant.
- Where features are Windows-only (e.g., Kerberos for domain-joined VMs), clearly indicate this and provide Linux alternatives or note the absence of equivalent features.
Bastion
Quickstart: Use Terraform to deploy Azure Bastion
...b/main/articles/bastion/quickstart-deploy-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell example is given equal prominence and detail as the CLI example. This can be interpreted as a subtle Windows bias, as PowerShell is primarily a Windows tool, and no Linux-specific shell (e.g., Bash) or OS-specific instructions are mentioned. The order of tabs places Azure CLI first, which is cross-platform, but the inclusion of PowerShell as a primary alternative may reinforce a Windows-centric approach.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample Bash commands where appropriate.
- Clarify that PowerShell Core is available cross-platform, or note that the PowerShell example is primarily for Windows users.
- Consider adding a note or tab for Linux/macOS users, highlighting any OS-specific steps or differences.
- Ensure that all tooling and instructions are presented in a way that does not assume a Windows environment by default.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific features and examples before Linux equivalents, and by omitting explicit Linux instructions or links in key sections. For example, the 'Copy and paste' section only links to Windows VM instructions, and there is no mention of Linux VMs or their workflows in the main feature descriptions.
Recommendations
- Add equivalent Linux VM documentation links and examples alongside Windows instructions, especially for features like copy/paste and file transfer.
- Explicitly mention Linux support and workflows in each feature section, clarifying any differences or limitations.
- Ensure that feature descriptions and quickstart guides provide parity for both Windows and Linux users, including references to SSH and Linux-native tools where appropriate.
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 focused exclusively on Windows virtual machines, with no mention of Linux VMs or examples for Linux users. All instructions, prerequisites, and scenarios assume a Windows environment, resulting in a lack of parity for Linux users.
Recommendations
- Add equivalent instructions and examples for Linux virtual machines, including any differences in clipboard behavior or keyboard shortcuts.
- Update prerequisites to mention both Windows and Linux VM scenarios, or clarify if the feature is Windows-only.
- Include notes about support or limitations for copy/paste functionality on Linux VMs via Bastion.
- Provide screenshots or walkthroughs for Linux desktop environments (e.g., Ubuntu, CentOS) if supported.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific features and examples before Linux equivalents. For instance, the copy/paste functionality explicitly links to 'Copy and paste - Windows VMs' without mentioning Linux VM support or providing a parallel Linux example. There is no direct mention of Linux tools, patterns, or examples in the main content, and Windows terminology (RDP, Windows VMs) is prioritized.
Recommendations
- Add explicit references and links to Linux VM documentation for features such as copy/paste, file transfer, and remote audio.
- Provide examples and instructions for connecting to Linux VMs using SSH, including details on supported features and any limitations.
- Ensure feature descriptions mention both Windows and Linux support where applicable, and avoid presenting Windows features or links first unless Linux parity is not possible.
- Include Linux-specific troubleshooting and configuration steps alongside Windows instructions.
Bastion
VNet peering and Azure Bastion architecture
.../azure-docs/blob/main/articles/bastion/vnet-peering.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows virtual machines first and exclusively in the deployment steps. The example link for creating a VM points only to the Windows VM quick-create guide, and the connection instructions link to a Windows RDP guide. There are no Linux VM examples or references to SSH connections, which are common for Linux environments.
Recommendations
- Include parallel examples and links for Linux virtual machines, such as a quick-create guide for Linux VMs.
- Reference both RDP (Windows) and SSH (Linux) connection guides when describing how to connect to VMs via Azure Bastion.
- Ensure that documentation steps and examples mention both Windows and Linux VM scenarios to provide platform parity.
- Add explicit mention of SSH support and provide links to relevant documentation for Linux users.