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 151-175 of 222 flagged pages
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-host-arm-template.md .../main/articles/bastion/quickstart-host-arm-template.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where only Windows virtual machine creation and Windows RDP connection guides are linked. There are no Linux VM creation or SSH connection examples or references, and no Linux-specific instructions or parity in the workflow. The main deployment flow is platform-neutral (using the Azure portal and ARM templates), but the follow-up guidance is Windows-centric.
Recommendations
  • Add links to Linux VM creation guides in the 'Next steps' section, such as 'Quickstart: Create a Linux virtual machine in the Azure portal'.
  • Include instructions or links for connecting to Linux VMs via SSH using Azure Bastion.
  • Ensure examples and screenshots illustrate both Windows and Linux scenarios where relevant.
  • Review other related documentation to ensure Linux users are equally supported in Bastion deployment and usage workflows.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-deploy-terraform.md ...b/main/articles/bastion/quickstart-deploy-terraform.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell tab is given equal prominence to the CLI, and PowerShell is a Windows-centric tool. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux tools or patterns. The CLI commands are cross-platform, but the presence and parity of PowerShell examples may signal a slight Windows bias, especially since no Linux/Bash-specific instructions or troubleshooting are provided.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific instructions if needed.
  • Add a Bash shell tab or section for verification steps, showing how to run the CLI commands in a Linux environment.
  • Clarify that PowerShell is optional and primarily for Windows users, and suggest alternatives for Linux/macOS users.
  • Include troubleshooting tips or links for Linux users running Terraform and Azure CLI.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-faq.md ...s/azure-docs/blob/main/articles/bastion/bastion-faq.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page for Azure Bastion FAQ demonstrates a Windows bias in several areas. Browser recommendations are Windows-centric, with Windows mentioned first and Linux omitted entirely. Keyboard layout configuration instructions are provided only for Windows workstations, with no guidance for Linux users. There are no examples or instructions specific to Linux, such as how to set keyboard layouts or use native SSH/RDP clients on Linux. References to VM login via Microsoft Entra ID link only to Windows VM documentation, with no mention of Linux VM authentication.
Recommendations
  • Include Linux-specific instructions and examples alongside Windows ones, such as how to set keyboard layouts on popular Linux distributions.
  • Mention supported browsers on Linux and provide parity in browser recommendations.
  • Provide links and documentation for logging into Linux VMs using Microsoft Entra ID, if supported.
  • When describing native client usage, include examples for Linux SSH/RDP clients.
  • Ensure that all instructions and feature descriptions are platform-neutral or offer guidance for both Windows and Linux users.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-connect-vm-linux-rdp.md .../main/articles/bastion/bastion-connect-vm-linux-rdp.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page discusses connecting to a Linux VM using RDP via Azure Bastion, but it exhibits bias by focusing on RDP—a protocol and workflow traditionally associated with Windows environments. It requires installation of xrdp (a Windows-compatible RDP server for Linux) and does not provide alternative Linux-native remote desktop solutions or examples. There are no examples or mentions of connecting via SSH (the default for Linux) or using Linux-native tools, and the documentation does not address Linux-specific workflows or troubleshooting beyond xrdp installation.
Recommendations
  • Provide examples and guidance for connecting to Linux VMs using SSH via Azure Bastion, which is the default and most secure method for Linux administration.
  • Include alternative Linux remote desktop solutions, such as VNC, and explain their configuration and use with Azure Bastion.
  • Offer troubleshooting steps and best practices for xrdp on various Linux distributions, including common issues and their resolutions.
  • Clarify the limitations and trade-offs of using RDP/xrdp on Linux compared to SSH or other remote desktop protocols.
  • Ensure parity in documentation by presenting Linux-native workflows and tools before or alongside Windows-centric approaches.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/whats-new.md ...ocs/azure-docs/blob/main/articles/bastion/whats-new.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page lists new features for Azure Bastion, but the RDP (Windows) feature and its Microsoft Entra ID support are described and linked before the SSH (Linux) equivalent. The RDP (Windows) feature is presented first in the release table, and the SSH (Linux) feature is listed later. There are no explicit Linux command examples or Linux-specific tools mentioned, and the documentation does not provide parity in example depth or order for Linux users.
Recommendations
  • Present SSH (Linux) and RDP (Windows) features together or alternate their order to avoid implicit prioritization.
  • Ensure that feature descriptions and links for Linux (SSH) are as detailed and prominent as those for Windows (RDP).
  • Include Linux-specific examples, commands, or tools where relevant, especially in feature descriptions and quickstart guides.
  • Add a section or table column indicating OS applicability (Windows/Linux) to clarify parity and coverage.
  • Review related linked documentation to ensure Linux users have clear, direct guidance equivalent to Windows users.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/troubleshoot.md .../azure-docs/blob/main/articles/bastion/troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides a Windows-specific troubleshooting section (domain-joined VM sign-in) but does not offer equivalent guidance for Linux-based VMs (e.g., troubleshooting SSH sign-in issues, Linux domain integration, or Linux-specific connectivity problems). While an SSH key generation example is given (which is cross-platform), there is no troubleshooting content tailored to Linux VM scenarios, and Windows is mentioned explicitly before Linux in the context of domain-joined VMs.
Recommendations
  • Add troubleshooting guidance for Linux VMs, such as common SSH authentication issues, troubleshooting Linux domain-joined VMs (e.g., with LDAP or Kerberos), and Linux-specific connectivity problems.
  • Include examples and instructions for both Windows and Linux scenarios in sections that currently only mention Windows (e.g., sign-in issues).
  • Ensure parity in troubleshooting steps and terminology for both platforms, such as referencing Linux tools (e.g., journalctl, systemctl, sshd logs) alongside Windows tools.
  • Review and update the documentation to mention Linux scenarios wherever Windows is referenced, and avoid presenting Windows solutions first unless contextually justified.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-sku-comparison.md ...s/blob/main/articles/bastion/bastion-sku-comparison.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation presents VM connectivity options with Windows RDP listed before Linux SSH, and includes features like 'Connect to Linux VM using RDP' and 'Connect to Windows VM using SSH' only in higher SKUs, but does not provide any platform-specific usage examples or tooling references. There are no explicit PowerShell or Windows tool biases, but the ordering and feature emphasis subtly prioritize Windows connectivity patterns. There are no Linux-specific examples, CLI commands, or troubleshooting tips, and no mention of Linux tools or workflows beyond basic SSH/RDP support.
Recommendations
  • Provide example workflows for both Windows and Linux VM connectivity, including Azure CLI and SSH commands for Linux.
  • Ensure feature tables and descriptions alternate or balance Windows and Linux connectivity options, rather than listing Windows first.
  • Include troubleshooting tips or best practices for Linux users (e.g., SSH key management, file transfer methods).
  • Reference Linux-native tools (such as OpenSSH, scp, sftp) alongside Windows tools where relevant.
  • Add links to Linux-specific documentation or guides for Azure Bastion usage.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/private-only-deployment.md .../blob/main/articles/bastion/private-only-deployment.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides step-by-step instructions for deploying Azure Bastion in private-only mode exclusively using the Azure Portal GUI, which is most commonly accessed from Windows environments. There are no CLI, PowerShell, or Bash examples, nor any mention of Linux tools or workflows. The absence of cross-platform command-line instructions (such as Azure CLI or Bash) results in a bias towards Windows users and GUI-centric workflows.
Recommendations
  • Add Azure CLI examples for each deployment step to support Linux and macOS users.
  • Include Bash scripts or command-line instructions for creating and configuring Bastion resources.
  • Reference cross-platform tools (e.g., Azure CLI, Terraform) alongside or before GUI instructions.
  • Explicitly mention that the Azure Portal is accessible from any OS, and provide parity in instructions for non-Windows environments.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-vm-copy-paste.md ...cs/blob/main/articles/bastion/bastion-vm-copy-paste.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is focused exclusively on Windows virtual machines, with all instructions, prerequisites, and examples referencing Windows. There is no mention of Linux VMs, nor are there examples or guidance for Linux users. This creates a Windows-first bias and omits Linux parity.
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 VMs as supported scenarios.
  • Clarify any limitations or differences for Linux VMs when using Bastion copy/paste features.
  • Include screenshots and step-by-step guidance for Linux desktop environments (e.g., Ubuntu, CentOS) where relevant.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/vnet-peering.md .../azure-docs/blob/main/articles/bastion/vnet-peering.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows virtual machines before Linux equivalents and linking only to Windows VM creation guides. There are no Linux-specific examples or instructions, and connection steps reference Windows-centric guides.
Recommendations
  • Include links and examples for creating Linux virtual machines alongside Windows VM instructions.
  • Reference both Windows and Linux connection guides when describing how to connect to VMs via Azure Bastion.
  • Ensure that deployment and usage instructions are platform-neutral or provide parallel steps for both Windows and Linux environments.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/vm-about.md ...Docs/azure-docs/blob/main/articles/bastion/vm-about.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific features and examples before Linux equivalents. For instance, the 'Copy and paste' section links only to 'Copy and paste - Windows VMs' without mentioning Linux VM support or providing equivalent instructions. There is no explicit mention of Linux tools, patterns, or examples, and Windows terminology (RDP) is used more prominently than SSH or Linux-native methods.
Recommendations
  • Add parallel Linux VM documentation links and examples for features such as copy/paste, file transfer, and audio.
  • Ensure that references to connection methods (RDP/SSH) are balanced and that Linux SSH scenarios are described with equal detail.
  • Include explicit instructions or notes for Linux users wherever Windows-specific features are discussed.
  • Review linked articles to confirm Linux parity and update this overview page to reference both Windows and Linux guides side-by-side.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-vm-copy-paste.md ...cs/blob/main/articles/bastion/bastion-vm-copy-paste.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively discusses copying and pasting to and from Windows virtual machines via Azure Bastion. There are no references to Linux VMs, Linux-specific tools, or examples. All instructions, prerequisites, and screenshots are tailored to Windows environments, indicating a clear Windows-first bias and a lack of Linux parity.
Recommendations
  • Add equivalent instructions and examples for Linux virtual machines, including any differences in clipboard behavior or limitations.
  • Include screenshots or tool palette usage for Linux VMs if the UI or workflow differs.
  • Explicitly mention any platform-specific caveats, such as differences in keyboard shortcuts or clipboard support between Windows and Linux.
  • Update the prerequisites section to reference both Windows and Linux VM scenarios.
  • Consider renaming the article or creating a parallel page for Linux VMs to ensure users of both platforms are supported.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/private-only-deployment.md .../blob/main/articles/bastion/private-only-deployment.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for deploying Azure Bastion using the Azure portal UI, which is platform-agnostic. However, there are subtle signs of Windows bias: the instructions and screenshots reference the Azure portal interface, which is most commonly accessed from Windows environments, and there are no CLI (az), PowerShell, or Bash examples provided. There is no mention of Linux-specific tools, nor are Linux command-line deployment options discussed. The lack of parity in examples for Linux users (such as Azure CLI or Bash scripts) means Linux administrators may not have clear guidance for automating or scripting Bastion deployment.
Recommendations
  • Add Azure CLI (az) command examples for each deployment step, suitable for Linux/macOS users.
  • Include Bash script snippets for automating Bastion deployment.
  • If PowerShell examples are added, ensure equivalent Bash/Azure CLI examples are provided.
  • Explicitly mention that the Azure portal can be accessed from any OS, and provide links to CLI documentation for cross-platform deployment.
  • Add a section comparing deployment methods (Portal, PowerShell, Azure CLI) and their OS compatibility.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-connect-vm-linux-rdp.md .../main/articles/bastion/bastion-connect-vm-linux-rdp.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias by requiring the use of RDP (a protocol traditionally associated with Windows) to connect to Linux VMs, and referencing xrdp (a Windows-compatible remote desktop server for Linux) as the only method. There are no examples or mentions of native Linux remote access tools (such as SSH or VNC), nor are Linux-specific connection patterns discussed. The documentation does not provide Linux command-line examples for installing or configuring xrdp, nor does it mention alternative Linux remote desktop solutions.
Recommendations
  • Provide examples of connecting to Linux VMs using native Linux tools (e.g., SSH, VNC) alongside RDP.
  • Include Linux command-line instructions for installing and configuring xrdp.
  • Mention alternative Linux remote desktop solutions and clarify when RDP/xrdp is preferable.
  • Discuss authentication options beyond username/password, such as SSH keys, if supported.
  • Ensure parity in troubleshooting and configuration guidance for Linux users.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/troubleshoot.md .../azure-docs/blob/main/articles/bastion/troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a Windows-specific troubleshooting section (domain-joined VM sign-in) without a corresponding Linux example or guidance for Linux VMs. The only explicit OS example is for Windows, and Linux troubleshooting scenarios (such as SSH authentication issues, domain integration, or file transfer specifics) are not addressed. The SSH key generation example uses a Linux shell, but the troubleshooting focus and examples are Windows-centric.
Recommendations
  • Add troubleshooting guidance for Linux VMs, such as common SSH authentication issues, domain integration (e.g., with LDAP or Azure AD), and file transfer specifics for Linux.
  • Include examples for both Windows and Linux in sections discussing VM connectivity, domain join, and file transfer.
  • Ensure parity in troubleshooting scenarios by providing Linux equivalents wherever Windows-specific advice is given.
  • Explicitly mention any differences in Bastion behavior or requirements for Linux VMs (e.g., SSH key formats, file transfer limitations, etc.).
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-host-arm-template.md .../main/articles/bastion/quickstart-host-arm-template.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where only Windows virtual machine creation and RDP connection guides are linked. There are no Linux VM examples or SSH connection instructions, and the workflow assumes Windows usage patterns. The page does not mention Linux tools or provide parity for Linux users.
Recommendations
  • Add links to equivalent Linux VM quickstart guides (e.g., 'Quickstart: Create a Linux virtual machine in the Azure portal').
  • Include instructions or links for connecting to Linux VMs via SSH using Azure Bastion.
  • Ensure examples and screenshots reflect both Windows and Linux scenarios where applicable.
  • Explicitly mention that Azure Bastion supports both RDP (Windows) and SSH (Linux) connections, and provide guidance for each.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/secure-bastion.md ...zure-docs/blob/main/articles/bastion/secure-bastion.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing RDP and Windows-specific authentication features (e.g., Kerberos) before mentioning SSH and Linux equivalents. Examples and guidance for connecting to Windows VMs (RDP, Kerberos) are more detailed, while Linux-specific instructions are referenced only as links and not described inline. There is a lack of explicit Linux tooling or SSH-focused examples, and Windows terminology (RDP, Kerberos, domain-joined) is prioritized throughout the text.
Recommendations
  • Provide explicit SSH and Linux VM connection examples alongside RDP/Windows instructions, not just as external links.
  • Include details on Linux authentication methods (e.g., SSH key management, PAM integration) in the main text.
  • Balance references to Windows-specific tools (Kerberos, domain-joined) with Linux equivalents (e.g., LDAP, SSH hardening).
  • Ensure parity in session management, monitoring, and logging examples for both RDP (Windows) and SSH (Linux) sessions.
  • Use neutral language when describing features (e.g., 'RDP and SSH connectivity' instead of 'RDP connectivity'), and avoid prioritizing Windows terminology.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-faq.md ...s/azure-docs/blob/main/articles/bastion/bastion-faq.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. Browser recommendations mention Windows first and provide detailed instructions for configuring keyboard layouts specifically on Windows, with no equivalent guidance for Linux systems. There are no Linux-specific examples or instructions for common administrative tasks, such as setting keyboard layouts or connecting via SSH/RDP from Linux clients. The documentation assumes Windows as the default environment for many user actions.
Recommendations
  • Add Linux-specific instructions and examples alongside Windows ones, such as configuring keyboard layouts on popular Linux desktop environments (e.g., GNOME, KDE).
  • Include browser recommendations for Linux users, specifying supported browsers and any known issues.
  • Provide guidance for connecting to Azure Bastion from Linux clients using native SSH/RDP tools, including file transfer methods.
  • Ensure parity in troubleshooting steps and permissions explanations for both Windows and Linux environments.
  • Review all sections for implicit Windows-first assumptions and update language to be platform-neutral or explicitly inclusive of Linux.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-sku-comparison.md ...s/blob/main/articles/bastion/bastion-sku-comparison.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page presents VM connectivity options with Windows RDP listed before Linux SSH and RDP, and Windows SSH connectivity only available in higher SKUs. There are no explicit usage examples or command-line instructions for either Windows or Linux, but the feature tables and descriptions consistently mention Windows connectivity (RDP, SSH) before Linux equivalents, and do not provide parity in protocol support (e.g., Linux RDP is only supported in Standard/Premium SKUs, while Windows RDP is supported in all SKUs). There are no Linux-specific tools or workflows highlighted, and the documentation does not offer Linux-centric guidance or examples.
Recommendations
  • Ensure feature tables and descriptions list Linux and Windows connectivity options with equal prominence, alternating order or grouping by protocol rather than OS.
  • Provide explicit examples or references for connecting to both Linux and Windows VMs, including command-line instructions for SSH (Linux) and RDP (Windows), and highlight cross-platform tools (e.g., Azure CLI, native SSH clients).
  • Clarify protocol support parity, explaining why Linux RDP and Windows SSH are only available in higher SKUs, and offer guidance or alternatives for Linux users in lower SKUs.
  • Add links to Linux-specific documentation or tutorials for remote access via Azure Bastion, ensuring Linux administrators have clear guidance.
  • Review and update any upgrade or deployment instructions to include both Windows and Linux scenarios, avoiding implicit prioritization of Windows workflows.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-deploy-terraform.md ...b/main/articles/bastion/quickstart-deploy-terraform.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell tab is given equal prominence to the CLI tab, and PowerShell is a Windows-centric tool. There are no explicit Linux shell examples (e.g., bash, zsh), nor is there mention of Linux-specific patterns or tools. The CLI examples are generic and cross-platform, but the presence of PowerShell examples may suggest a slight Windows bias, especially for users who expect Linux-first guidance in cloud automation contexts.
Recommendations
  • Clarify that Azure CLI commands work on Windows, macOS, and Linux, and provide explicit bash/zsh examples where relevant.
  • Consider listing Azure CLI (bash) examples before PowerShell examples, as CLI is more cross-platform.
  • Add notes or tabs for Linux shell usage, especially for environment variable assignment and command syntax differences.
  • Avoid assuming PowerShell usage unless specifically targeting Windows users; make Linux usage explicit in verification and scripting steps.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/session-recording.md ...e-docs/blob/main/articles/bastion/session-recording.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on Azure portal-based configuration and session recording for Bastion, with no mention of Linux-specific workflows, tools, or examples. There is no reference to Linux clients, SSH session recording, or command-line alternatives (such as Azure CLI or Bash scripts), and all instructions are oriented around graphical portal steps, which are more familiar to Windows users. The absence of Linux/SSH-specific guidance or parity in examples constitutes a Windows-first and missing Linux example bias.
Recommendations
  • Add explicit instructions for enabling and configuring Bastion session recording for SSH (Linux) sessions, including any differences in prerequisites or limitations.
  • Provide examples for managing Bastion session recording using Azure CLI and Bash scripts, not just portal-based workflows.
  • Include guidance for Linux administrators on viewing and managing session recordings, such as using az CLI, REST API, or other non-portal tools.
  • Clarify whether session recording supports both RDP (Windows) and SSH (Linux) sessions, and document any feature gaps.
  • Add troubleshooting and FAQ sections relevant to Linux users and SSH scenarios.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-vm-copy-paste.md ...cs/blob/main/articles/bastion/bastion-vm-copy-paste.md
Medium Priority View Details →
Scanned: 2026-01-06 18:15
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively discusses copying and pasting to and from Windows virtual machines, with no mention of Linux VMs or their specific requirements. All examples, prerequisites, and instructions are tailored to Windows, potentially excluding users who need guidance for Linux VM scenarios.
Recommendations
  • Add a dedicated section for Linux VMs, outlining any differences in clipboard support or configuration when using Azure Bastion.
  • Include Linux-specific examples and instructions, such as how to copy and paste in common Linux desktop environments (e.g., GNOME, KDE) or terminal sessions.
  • Clarify whether the Bastion clipboard feature works identically for Linux VMs, and note any limitations or additional steps required.
  • Ensure parity in screenshots and tool references, showing the experience on both Windows and Linux VMs.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/vm-about.md ...Docs/azure-docs/blob/main/articles/bastion/vm-about.md
Medium Priority View Details →
Scanned: 2026-01-06 18:15
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific features and examples before Linux equivalents. For instance, the copy/paste section links only to 'Copy and paste - Windows VMs', with no mention of Linux VM support or guidance. There is also a general lack of explicit Linux examples or parity in feature descriptions, suggesting Windows is the primary platform considered.
Recommendations
  • Add equivalent documentation and links for Linux VM features, such as copy/paste functionality for Linux VMs.
  • Ensure that examples and feature descriptions mention both Windows and Linux platforms where applicable.
  • Where features differ between Windows and Linux, provide clear guidance and links for both.
  • Review linked articles (e.g., for file transfer, audio) to confirm Linux support is documented and referenced from this page.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/private-only-deployment.md .../blob/main/articles/bastion/private-only-deployment.md
Medium Priority View Details →
Scanned: 2026-01-06 18:15
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes deployment using the Azure portal UI, which is platform-agnostic, but does not provide any command-line examples. There is no mention of PowerShell, Azure CLI, or any OS-specific tools. However, the lack of CLI examples means that users who prefer or require Linux-based workflows (e.g., Azure CLI on Bash) are not served. The documentation implicitly assumes a graphical workflow, which is more common on Windows, and does not address Linux parity or automation scenarios.
Recommendations
  • Add Azure CLI command examples for deploying Bastion in private-only mode, suitable for Linux/macOS users.
  • If PowerShell examples are added in the future, ensure Azure CLI (Bash) equivalents are provided and presented with equal prominence.
  • Explicitly mention that the Azure portal is accessible from any OS, and link to CLI-based documentation for users who prefer command-line automation.
  • Include a section on automating Bastion deployment using scripts, with examples for both PowerShell and Bash/Azure CLI.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/native-client.md ...azure-docs/blob/main/articles/bastion/native-client.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a 'windows_first' bias by listing Windows native client scenarios and links before Linux equivalents in both the main connection table and the 'Next steps' section. There is also a lack of explicit Linux command-line examples or screenshots in the main configuration steps, and the walkthroughs for enabling the feature do not mention Linux-specific tools or workflows.
Recommendations
  • Reorder examples and tables to alternate or lead with Linux scenarios where appropriate, or present both Windows and Linux in parallel.
  • Include explicit Linux command-line examples (e.g., using SSH from a Linux terminal) in the main configuration and connection sections.
  • Add screenshots or walkthroughs from a Linux environment (e.g., GNOME Terminal, Konsole) alongside Windows screenshots.
  • Ensure that the 'Next steps' section lists Linux and Windows guides with equal prominence, or groups them together to avoid prioritizing one platform.
  • Mention Linux-native tools (e.g., OpenSSH, GNOME RDP clients) where Windows tools are referenced.
GitHub Create Pull Request
← Previous Page 7 of 9 Next →