Bastion

36
Total Pages
14
Linux-Friendly Pages
22
Pages with Bias
61.1%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (34)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-deploy-terraform.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell section is presented immediately after the Azure CLI section and uses Windows PowerShell syntax. There are no explicit Linux-specific instructions or mentions of Linux tools, shells, or patterns. The use of PowerShell, which is primarily associated with Windows, and the absence of explicit Linux/Bash parity (such as mentioning Bash or zsh shells, or providing Linux-specific troubleshooting or environment notes), indicates a mild Windows bias.
Recommendations:
  • Explicitly mention that the Azure CLI examples are cross-platform and can be run on Linux, macOS, and Windows.
  • Add a note or section clarifying that all Terraform and Azure CLI steps are fully supported on Linux and macOS, and provide any Linux-specific prerequisites if needed.
  • Consider including example shell commands using Bash syntax (e.g., export instead of $var=...) for Linux/macOS users.
  • If troubleshooting or environment setup differs on Linux, add a dedicated section or callout for Linux users.
  • Ensure that PowerShell is not presented as the default or primary method; if possible, present CLI/Bash examples first or in parallel.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-create-host-powershell.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/native-client.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/vm-about.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows-first bias, particularly in the 'Copy and paste' section, which explicitly references only Windows VMs and links to a Windows-specific guide. There is no mention of Linux VMs or examples for Linux users in this context. Other sections are more neutral, but the lack of Linux parity in key feature explanations is notable.
Recommendations:
  • Include equivalent documentation and examples for Linux VMs, especially for features like copy/paste and file transfer.
  • Update references and links to cover both Windows and Linux scenarios, or clarify if a feature is not supported on Linux.
  • Where features differ between platforms, provide side-by-side instructions or a comparison table.
  • Ensure that introductory text and feature descriptions do not assume a Windows environment by default.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-host-arm-template.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by only providing next steps and connection instructions for Windows virtual machines. There are no examples or links for deploying or connecting to Linux VMs via Azure Bastion, and the 'Next steps' section exclusively references Windows workflows.
Recommendations:
  • Add parallel 'Next steps' links 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 or screenshots for Linux VM deployments where relevant.
  • Ensure that instructions and examples throughout the page are platform-neutral or provide both Windows and Linux options where applicable.
  • Review related documentation to ensure Linux users have clear, accessible guidance for using Azure Bastion with their workloads.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-connect-vm-scale-set.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation provides generic instructions for connecting to a VM scale set using Azure Bastion, but implicitly assumes a Windows-centric workflow by referencing RDP (a Windows protocol) and omitting any mention of Linux connection methods (such as SSH). There are no examples or guidance for connecting to Linux-based VM instances, nor are Linux tools or workflows mentioned.
Recommendations:
  • Include explicit instructions and examples for connecting to Linux VM instances using SSH via Azure Bastion.
  • Clarify that Azure Bastion supports both RDP (for Windows) and SSH (for Linux), and provide guidance for both scenarios.
  • Add screenshots or step-by-step guidance that demonstrates the SSH connection workflow for Linux users.
  • Ensure that terminology and steps are platform-neutral or that both Windows and Linux workflows are presented in parallel.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/vnet-peering.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows-first bias by linking only to the Windows VM creation guide and the Windows RDP connection guide, without mentioning or providing equivalent Linux VM or SSH connection documentation. There are no Linux-specific examples or references, which may make Linux users feel unsupported or overlooked.
Recommendations:
  • Include links to both Windows and Linux VM creation guides in the deployment overview step.
  • Provide guidance or links for connecting to Linux VMs via SSH using Azure Bastion, alongside the existing RDP/Windows instructions.
  • Ensure that all examples and references cover both Windows and Linux scenarios equally, or explicitly state when instructions are applicable to both.
  • Consider adding a section or FAQ entry addressing Linux VM connectivity and any platform-specific considerations.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/tutorial-create-host-portal.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation generally maintains parity between Windows and Linux, but in the prerequisites section, the link to the Windows VM quickstart is listed before the Linux VM quickstart. This subtle ordering preference is a form of 'windows_first' bias. However, both platforms are otherwise mentioned equally, and connection instructions reference both RDP (Windows) and SSH (Linux) without favoring one. There are no PowerShell-heavy examples, Windows-only tools, or missing Linux examples.
Recommendations:
  • List Linux and Windows VM quickstart links in alphabetical order or randomize their order to avoid implicit prioritization.
  • Wherever possible, ensure that examples and instructions mention both Windows and Linux platforms in parallel, or use neutral phrasing.
  • Periodically review documentation for subtle ordering or phrasing that may suggest platform preference, even if both are supported.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/work-remotely-support.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a subtle Windows bias by listing PowerShell as a primary configuration method and not providing explicit Linux or cross-platform examples. The mention of RDP before SSH and the lack of Linux-specific tools or workflows further reinforce this bias.
Recommendations:
  • Provide explicit Linux examples or workflows, such as using SSH from a Linux terminal.
  • List Azure CLI before PowerShell, as CLI is cross-platform and more familiar to Linux users.
  • Include references to Linux-native tools or commands where relevant.
  • Ensure that both RDP (Windows) and SSH (Linux) use cases are equally described and demonstrated.
  • Add a section or examples for accessing Azure Bastion from Linux/macOS environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-vm-copy-paste.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation is exclusively focused on Windows virtual machines, with all instructions, prerequisites, and examples tailored to Windows. There is no mention of Linux VMs, nor are there any Linux-specific instructions or considerations. This creates a strong Windows-first bias and omits Linux parity.
Recommendations:
  • Add a parallel section or a separate article for Linux VMs, detailing how copy and paste works with Azure Bastion when connecting to Linux virtual machines.
  • Include Linux-specific prerequisites (e.g., supported distributions, required desktop environments, or RDP/SSH client considerations).
  • Provide examples and screenshots demonstrating the copy and paste process on Linux VMs, including any differences in keyboard shortcuts or clipboard behavior.
  • Clarify any limitations or differences in feature support between Windows and Linux VMs when using Azure Bastion.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/design-architecture.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation discusses RDP and SSH connectivity but does not provide any OS-specific examples or mention tools or workflows unique to either Windows or Linux. However, there is a subtle bias in that RDP (primarily a Windows protocol) is mentioned before SSH (primarily used for Linux), and there are no explicit Linux-specific examples or references to Linux-native tools or workflows. The documentation does not provide parity in illustrating Linux scenarios, such as connecting to Linux VMs via SSH from Linux/macOS clients or using Linux command-line tools.
Recommendations:
  • Include explicit examples or references for connecting to Linux VMs using SSH from Linux/macOS clients.
  • Mention Linux-native tools (such as OpenSSH) and workflows alongside any references to RDP or Windows tools.
  • Ensure that any future configuration or usage examples provide parity between Windows and Linux environments.
  • Clarify that Azure Bastion supports both RDP (for Windows) and SSH (for Linux) equally, and provide links to relevant documentation for both operating systems.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/connect-ip-address.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-developer.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/vm-upload-download-native.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-vm-copy-paste.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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 considerations. All prerequisites and instructions are Windows-centric, and there are no examples or guidance for Linux users.
Recommendations:
  • Add equivalent instructions and examples for Linux virtual machines, including any differences in clipboard handling or keyboard shortcuts.
  • Update the prerequisites section to mention both Windows and Linux VMs, or clarify if the feature is Windows-only.
  • If there are limitations or differences for Linux VMs, document them explicitly.
  • Provide screenshots or illustrations showing the process on Linux desktops where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-connect-vm-linux-rdp.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools
Summary:
The documentation focuses exclusively on using RDP (a protocol and workflow traditionally associated with Windows) to connect to Linux VMs, requiring the installation of xrdp (a Windows-compatible RDP server for Linux). There are no examples or mentions of native Linux remote access tools (such as SSH or VNC), nor are there instructions for connecting from Linux clients. The documentation assumes a Windows-centric approach to remote desktop access, potentially neglecting Linux-native workflows.
Recommendations:
  • Include examples and guidance for connecting to Linux VMs using native Linux tools, such as SSH, alongside RDP.
  • Provide parity in instructions for connecting from both Windows and Linux client machines.
  • Mention and link to alternatives to xrdp (such as VNC or X2Go) for users who may prefer Linux-native remote desktop solutions.
  • Clarify that RDP is not the only or default method for Linux VM access, and explain scenarios where RDP (via xrdp) is preferable or necessary.
  • Add a section comparing RDP and SSH for Linux VM management, highlighting security and usability considerations.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-connect-vm-scale-set.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation focuses on connecting to VM scale sets via Azure Bastion using the Azure portal, but implicitly assumes RDP/Windows usage by referencing 'Connect' without clarifying Linux/SSH scenarios. There are no explicit instructions or examples for connecting to Linux VMs (e.g., SSH), nor are Linux-specific workflows or terminology mentioned. The structure and language suggest a Windows-first perspective.
Recommendations:
  • Add explicit instructions and examples for connecting to Linux VM instances using SSH through Azure Bastion.
  • Clarify in the 'Connect' section that both RDP (for Windows) and SSH (for Linux) are supported, and provide step-by-step guidance for each.
  • Include screenshots or UI callouts that show both RDP and SSH options in the Azure portal.
  • Mention any Linux-specific prerequisites or settings (such as SSH key requirements) alongside the existing guidance.
  • Review terminology to ensure it is inclusive of both Windows and Linux scenarios (e.g., avoid assuming 'Connect' means RDP only).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-connect-vm-ssh-linux.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools
Summary:
The documentation page is generally focused on connecting to Linux VMs via Azure Bastion using the Azure portal, and does not exhibit overt Windows bias in its main instructions or examples. However, in the sections about storing SSH keys in Azure Key Vault, the documentation repeatedly references using PowerShell (and to a lesser extent, Azure CLI) for key management, and links to a 'quick-create-powershell' guide. There are no explicit Linux-native (e.g., Bash, shell script) examples or references for these operations, and PowerShell is mentioned before Azure CLI. This may subtly favor Windows users or those familiar with PowerShell, rather than providing parity for Linux users.
Recommendations:
  • Provide explicit Azure CLI and Bash/shell script examples for storing SSH keys in Azure Key Vault, alongside or before PowerShell examples.
  • When linking to guides (e.g., 'Create a key vault'), include links to both PowerShell and Azure CLI/Bash versions.
  • Clarify that Azure CLI can be used from any platform, and provide sample commands for Linux/macOS users.
  • Review all references to PowerShell and ensure that Linux-native alternatives are presented equally and not as secondary options.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-create-host-powershell.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/configuration-settings.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-faq.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/configure-host-scaling.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by referencing PowerShell as the only command-line alternative to the Azure portal, without mentioning or providing examples for Linux/Unix-based tools such as Azure CLI. No Linux-specific instructions or parity is offered.
Recommendations:
  • Include Azure CLI instructions for configuring host scaling, as Azure CLI is cross-platform and widely used on Linux.
  • When referencing command-line alternatives, mention both PowerShell and Azure CLI, and provide links/examples for each.
  • Ensure that any references to tools or scripts are not Windows-specific unless absolutely necessary, and always provide Linux equivalents where possible.
  • Consider a section or note explicitly stating that the steps can be performed from any OS using the Azure portal or Azure CLI.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/connect-ip-address.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/native-client.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a 'windows_first' bias by listing Windows native client scenarios before Linux in both the main connection table and the 'Next steps' section. There are also missing explicit Linux command examples or screenshots in the main body, with more detailed step references for Windows clients. Linux tools and workflows are mentioned, but not as prominently or with as much detail as Windows equivalents.
Recommendations:
  • Present Linux and Windows examples side-by-side or alternate their order in tables and 'Next steps' sections.
  • Include explicit Linux command-line examples and screenshots in the main documentation body, not just as links.
  • Ensure that Linux-native tools (such as OpenSSH) are discussed with the same depth and clarity as Windows tools.
  • Add a section or callout for macOS users if relevant, to further improve cross-platform parity.
  • Review linked pages to ensure Linux instructions are as comprehensive and accessible as Windows instructions.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-deploy-terraform.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying the deployment, but the PowerShell examples are included as a primary alternative to the CLI, which is cross-platform. There are no Linux-specific shell examples (e.g., bash), and PowerShell is traditionally associated with Windows, though it is now cross-platform. The order of presentation (CLI first, then PowerShell) is reasonable, but the inclusion of PowerShell as the only alternative may suggest a slight Windows bias, especially since no explicit Linux shell or macOS Terminal instructions are given.
Recommendations:
  • Add explicit bash shell examples for Linux/macOS users, especially for common verification and scripting steps.
  • Clarify that Azure CLI commands work on all platforms, and consider adding a note about running them in bash or zsh.
  • If PowerShell is included, mention that it is available cross-platform, or provide a link to installation instructions for Linux/macOS.
  • Consider including a table or section summarizing command usage across Windows (PowerShell, CMD), Linux (bash), and macOS (zsh, bash) to improve parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/kerberos-authentication-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-developer.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-host-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-host-arm-template.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates Windows bias by only providing 'Next steps' links for creating and connecting to Windows virtual machines, with no mention or guidance for Linux VMs. There are no Linux-specific examples or references, and the workflow implicitly assumes a Windows-centric use case.
Recommendations:
  • Add parallel 'Next steps' links 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 examples or references for connecting to Linux VMs via Bastion, not just Windows (RDP) scenarios.
  • Ensure that any screenshots or walkthroughs that are OS-specific are balanced with both Windows and Linux examples.
  • Review the documentation for any implicit assumptions that the user is deploying Windows VMs and update language to be OS-neutral where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/vnet-peering.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a 'windows_first' bias by linking only to the Windows VM creation guide and the Windows RDP connection guide, without mentioning or linking to equivalent Linux VM creation or SSH connection documentation. There are no Linux-specific examples or references, which may lead Linux users to feel unsupported or overlooked.
Recommendations:
  • Include links to both Windows and Linux VM creation guides (e.g., /azure/virtual-machines/linux/quick-create-portal).
  • Provide examples or links for connecting to Linux VMs via SSH using Azure Bastion (e.g., bastion-connect-vm-ssh-linux.md).
  • Ensure that instructions and references are platform-neutral or explicitly cover both Windows and Linux scenarios.
  • Where possible, mention both RDP (for Windows) and SSH (for Linux) in connection steps and overviews.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/session-recording.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation page for configuring Bastion session recording is platform-neutral in its instructions, focusing on Azure Portal UI steps and storage configuration. However, it implicitly exhibits 'missing_linux_example' and 'windows_first' bias by not mentioning or providing any Linux-specific guidance or CLI examples, nor does it address Linux users' needs for automation or scripting (e.g., via Azure CLI, Bash, or PowerShell). The instructions and screenshots are tailored to the Azure Portal, which is commonly used by Windows administrators, and there is no mention of alternative methods or considerations for Linux environments.
Recommendations:
  • Add equivalent instructions for configuring Bastion session recording using Azure CLI and/or Azure PowerShell, and present both methods side by side.
  • Include Linux-specific examples for generating SAS tokens (e.g., using az storage commands in Bash).
  • Explicitly mention that the steps are applicable regardless of the OS, or clarify any OS-specific differences if they exist.
  • Provide automation scripts or command-line alternatives for common tasks (e.g., creating storage accounts, containers, and SAS tokens) to support Linux and cross-platform users.
  • Ensure that any screenshots or UI references are supplemented with text-based instructions for users who may not use the Azure Portal.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/vm-about.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates Windows bias by referencing only Windows-specific instructions for the copy/paste feature ("Copy and paste - Windows VMs") without mentioning Linux VMs or providing equivalent guidance for Linux users. There is no explicit mention of Linux tools, workflows, or examples, and Windows is prioritized in the only detailed feature link.
Recommendations:
  • Add equivalent documentation and links for Linux VM scenarios, such as 'Copy and paste - Linux VMs', ensuring parity in feature explanation.
  • Where features are OS-agnostic, clarify that instructions apply to both Windows and Linux, or provide OS-specific sections/examples.
  • Review all referenced articles (e.g., for file transfer, audio) to ensure Linux workflows are included and linked from this page.
  • Avoid using Windows as the default or only example; present both Windows and Linux options side by side where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/work-remotely-support.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/tutorial-create-host-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation provides both Windows and Linux VM quickstart links and mentions both RDP (Windows) and SSH (Linux) ports, but in the prerequisites, the Windows VM creation link is listed before the Linux VM link. There are no command-line (PowerShell or Bash) examples at all, and no Windows-specific tools or patterns are emphasized. The overall structure is neutral, but the ordering of Windows before Linux in the prerequisites is a subtle 'windows_first' bias.
Recommendations:
  • List Linux and Windows VM creation links in alternating order across documentation, or list Linux first in some instances to balance exposure.
  • Explicitly state that the steps apply equally to both Windows and Linux VMs where relevant.
  • If providing future examples or screenshots, ensure parity by including both Windows and Linux scenarios.
  • Consider adding a note or section clarifying that Bastion supports both SSH (Linux) and RDP (Windows) equally, with links to connection guides for both.