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 176-200 of 222 flagged pages
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: 2025-07-13 21:37
Reviewed by: Unknown
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 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.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
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: 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 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.
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-connect-vm-scale-set.md .../main/articles/bastion/bastion-connect-vm-scale-set.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
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: 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 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.
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: 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, 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.
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/configure-host-scaling.md ...s/blob/main/articles/bastion/configure-host-scaling.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-connect-vm-ssh-linux.md .../main/articles/bastion/bastion-connect-vm-ssh-linux.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-connect-vm-scale-set.md .../main/articles/bastion/bastion-connect-vm-scale-set.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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).
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
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: 2025-07-08 04:23
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 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.
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-08 04:23
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 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.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
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: 2025-07-08 04:23
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 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.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
Scanned: 2026-01-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The Azure Bastion FAQ documentation shows minor Windows bias in several areas. Browser recommendations list Windows browsers first and provide more detail for Windows users. Keyboard layout configuration instructions are given only for Windows workstations, with no guidance for Linux or macOS users. No Linux/macOS-specific examples or instructions are provided for tasks like setting keyboard layouts or file transfer, despite Bastion supporting SSH and RDP to non-Windows VMs.
Recommendations
  • Add instructions for configuring keyboard layouts on Linux and macOS workstations, not just Windows.
  • When listing supported browsers, present all platforms equally and provide configuration details for Linux/macOS where relevant.
  • Include examples or notes for Linux/macOS users in sections about native client usage, file transfer, and keyboard shortcuts.
  • Where tasks are platform-agnostic (e.g., SSH/RDP), ensure examples and guidance are not Windows-centric.
Scanned: 2026-01-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The Azure Bastion FAQ page demonstrates minor Windows bias in several areas. Browser recommendations mention Windows first and provide more detail for Windows users, while Linux is not mentioned at all. Keyboard layout configuration instructions are only provided for Windows workstations, with no guidance for Linux or macOS users. There are no explicit examples or instructions for Linux users regarding connecting to VMs, configuring keyboard layouts, or using native clients.
Recommendations
  • Include browser recommendations for Linux (e.g., Chrome, Firefox) alongside Windows and macOS.
  • Add instructions or references for configuring keyboard layouts on Linux and macOS systems.
  • Provide examples or notes for connecting to Linux VMs, including any OS-specific considerations for SSH/RDP via Bastion.
  • Ensure parity in native client documentation by mentioning Linux-compatible clients and workflows.
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The Azure Bastion FAQ documentation demonstrates minor Windows bias in several areas. Browser recommendations mention Windows first and provide more detail for Windows users. Keyboard layout configuration instructions are Windows-specific, with no guidance for Linux or macOS users. No Linux/macOS-specific examples or instructions are provided for tasks like keyboard layout changes or file transfer, despite Bastion supporting SSH (commonly used on Linux/macOS).
Recommendations
  • Add instructions for configuring keyboard layouts on Linux and macOS systems alongside the Windows steps.
  • When listing supported browsers, mention Linux explicitly and provide recommendations for Linux users (e.g., Chrome, Firefox).
  • For file transfer, clarify SSH client compatibility on Linux/macOS and provide example workflows for those platforms.
  • Ensure parity in examples and instructions for common cross-platform tasks, especially where SSH is involved.
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The Azure Bastion FAQ documentation demonstrates minor Windows bias in several areas. Browser recommendations mention Windows first and provide more detail for Windows users. Keyboard layout configuration instructions are exclusively for Windows, with no guidance for Linux or macOS users. There are no explicit Linux/macOS examples for setting keyboard layouts or other OS-specific tasks, potentially creating friction for non-Windows users.
Recommendations
  • Add instructions for configuring keyboard layouts on Linux and macOS systems alongside the Windows steps.
  • When listing supported browsers, present options for all platforms equally and avoid listing Windows first unless there is a technical reason.
  • Where OS-specific configuration is discussed (e.g., keyboard layouts), include parity guidance for Linux and macOS users.
  • Review other sections for subtle Windows-first language and ensure Linux/macOS users are equally addressed where relevant.
Scanned: 2026-01-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The Azure Bastion FAQ documentation shows minor Windows bias in several areas. Browser recommendations list Windows browsers first and provide more detail for Windows users. Keyboard layout configuration instructions are given only for Windows workstations, with no guidance for Linux or macOS users. No Linux/macOS-specific examples or instructions are provided for tasks like setting keyboard layouts or file transfer, despite Bastion supporting SSH and RDP to non-Windows VMs.
Recommendations
  • Add instructions for configuring keyboard layouts on Linux and macOS workstations, alongside the Windows steps.
  • When listing supported browsers, mention Linux compatibility explicitly and provide browser recommendations for Linux users.
  • For file transfer and native client usage, clarify any OS-specific requirements or provide examples for Linux/macOS (e.g., using SSH/SCP, RDP clients).
  • Ensure that any references to local workstation configuration include parity for Linux and macOS environments.
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates minor Windows bias, primarily in the order and specificity of examples. Browser recommendations list Windows options first and provide more detail for Windows users. Keyboard layout configuration instructions are exclusively for Windows, with no guidance for Linux or macOS users. No explicit Linux/macOS tools or patterns are mentioned, and some sections (e.g., keyboard setup) lack parity for non-Windows platforms.
Recommendations
  • Provide browser recommendations for Linux explicitly, not just Windows and Mac.
  • Include instructions for setting keyboard layouts on Linux and macOS, alongside Windows.
  • Ensure examples and guidance are platform-neutral or offer parallel steps for Linux/macOS where relevant.
  • Review all sections for implicit Windows-first language and rephrase to be inclusive of all major platforms.
Bastion Quickstart: Deploy Azure Bastion automatically ...s/blob/main/articles/bastion/quickstart-host-portal.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Minor Windows Tools
Summary
The documentation provides a balanced overview for both Windows and Linux VMs, mentioning both platforms in prerequisites and port requirements. However, there is a slight Windows-first bias: the example VM creation links list Windows before Linux, and keyboard shortcut guidance is more detailed for Windows VMs (including Mac-to-Windows shortcut translation) but lacks equivalent Linux VM guidance. No PowerShell or Windows-only tools are referenced, and all steps are performed in the Azure portal, which is cross-platform.
Recommendations
  • List Linux VM creation links before or alongside Windows VM links to avoid Windows-first ordering.
  • Provide keyboard shortcut guidance for connecting to Linux VMs from various clients (Windows, Mac, Linux), similar to the Windows VM section.
  • Ensure any tool or troubleshooting references include Linux/macOS equivalents if applicable.
  • Add explicit notes or examples for connecting to Linux VMs via Bastion, including authentication methods (e.g., SSH key vs password).
Bastion Quickstart: Connect to a VM using Azure Bastion Developer: Azure portal ...ocs/blob/main/articles/bastion/quickstart-developer.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates minor Windows bias by listing Windows VM creation before Linux VM creation in prerequisites, mentioning Windows port (3389) before Linux port (22), and providing keyboard shortcut examples focused on Windows VMs. There are no Linux/macOS-specific connection instructions or troubleshooting tips, and Windows terminology (e.g., CTRL+ALT+END) is explained in detail, while Linux desktop scenarios are not discussed.
Recommendations
  • Alternate the order of Windows and Linux VM creation links, or present them together.
  • Provide Linux/macOS-specific keyboard shortcut guidance for connecting to Linux VMs.
  • Include troubleshooting tips for connecting to Linux VMs (e.g., SSH key authentication, desktop environment requirements).
  • Add example screenshots or notes for Linux VM sessions to match the Windows-focused examples.
  • Clarify that Bastion Developer supports both Windows and Linux VMs equally, and highlight any differences in user experience.