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 1-25 of 222 flagged pages
Bastion Configure Bastion for Kerberos authentication - Azure portal ...ain/articles/bastion/kerberos-authentication-portal.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric: all examples, templates, and verification steps assume Windows VMs and Windows domain controllers. Only Windows images are deployed, and all configuration/verification steps use Windows tools (Group Policy Editor, PowerShell). There are no instructions or examples for Linux-based Kerberos realms, Linux VMs, or cross-platform scenarios.
Recommendations
  • Add guidance for configuring Kerberos authentication with Linux VMs (e.g., using MIT Kerberos or Samba as a domain controller).
  • Include ARM template parameters/examples for deploying Linux VMs and setting up a Linux-based Kerberos KDC.
  • Provide verification steps for Linux (e.g., using kinit, checking /etc/krb5.conf, or system logs).
  • Reference Linux documentation for Kerberos setup and troubleshooting.
  • Clarify in prerequisites and limitations that only Windows-based Kerberos domains are currently supported, if that is the case.
GitHub Create Pull Request
Bastion Copy and paste to and from a Windows virtual machine: Azure ...cs/blob/main/articles/bastion/bastion-vm-copy-paste.md
High Priority View Details →
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 is exclusively focused on Windows virtual machines, with no mention of Linux VM support or examples. All instructions, prerequisites, and screenshots are tailored to Windows, leaving Linux users without guidance for copy/paste functionality via Azure Bastion.
Recommendations
  • Add a dedicated section for Linux VMs, outlining any differences in copy/paste behavior and supported features.
  • Include Linux-specific prerequisites and troubleshooting steps.
  • Provide examples and screenshots for Linux desktop environments (e.g., Ubuntu, CentOS) and common clipboard shortcuts.
  • Clarify whether copy/paste is supported for Linux VMs and note any limitations.
GitHub Create Pull Request
Bastion Copy and paste to and from a Windows virtual machine: Azure ...cs/blob/main/articles/bastion/bastion-vm-copy-paste.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively discusses copy and paste functionality for Windows virtual machines, with no mention of Linux VMs or their specific requirements. All instructions, prerequisites, and examples are tailored to Windows, leaving Linux/macOS users without guidance for their platforms.
Recommendations
  • Add a dedicated section for Linux virtual machines, outlining any differences in copy/paste behavior, prerequisites, and troubleshooting steps.
  • Include examples and screenshots for Linux VMs, such as using different desktop environments (e.g., GNOME, KDE) and their clipboard shortcuts.
  • Clarify whether Bastion's copy/paste feature works identically for Linux VMs, or note any limitations.
  • Mention macOS as a local client where relevant, and provide parity in shortcut instructions.
GitHub Create Pull Request
Bastion Configure Bastion for Kerberos authentication - Azure portal ...ain/articles/bastion/kerberos-authentication-portal.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily Windows-centric, with all examples, templates, and verification steps focused exclusively on Windows Server and Windows 10 VMs. Only Windows tools (e.g., Local Group Policy Editor, PowerShell, NTLM policy) are mentioned, and there are no instructions or examples for Linux or non-Windows environments. The ARM template provisions only Windows VMs, and the deployment instructions use PowerShell exclusively.
Recommendations
  • Add explicit guidance for configuring Kerberos authentication with Linux VMs, including supported distributions and any required configuration steps.
  • Provide ARM template parameters/examples for deploying Linux domain controllers (e.g., Samba/SSSD) and Linux client VMs.
  • Include verification steps for Kerberos authentication on Linux (e.g., using kinit, checking /etc/krb5.conf, or using Linux log files).
  • Offer CLI examples using Azure CLI or Bash, not just PowerShell.
  • Reference cross-platform Kerberos documentation, not only Windows Server docs.
GitHub Create Pull Request
Bastion Azure Bastion FAQ ...s/azure-docs/blob/main/articles/bastion/bastion-faq.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several areas: browser recommendations are Windows-centric, keyboard layout instructions are only provided for Windows, and references to RDP and Microsoft Entra authentication focus on Windows VMs. There are no Linux-specific examples or instructions for common scenarios such as setting keyboard layouts, connecting via SSH, or managing permissions on Linux VMs. Linux tools, patterns, and user needs are not addressed, leading to a lack of parity for Linux administrators.
Recommendations
  • Provide Linux-specific instructions alongside Windows ones, especially for tasks like setting keyboard layouts, connecting via SSH, and managing user permissions.
  • When mentioning browser support, clarify compatibility for Linux distributions and suggest browsers commonly used on Linux.
  • Include examples and documentation links for connecting to Linux VMs (e.g., SSH key management, Linux user groups for SSH access).
  • When describing features like file transfer or native client support, specify any differences or additional steps for Linux users.
  • Avoid assuming Windows as the default environment; use neutral language and parallel examples for both Windows and Linux where applicable.
GitHub Create Pull Request
Bastion Deploy Bastion:PowerShell ...ain/articles/bastion/bastion-create-host-powershell.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page is heavily focused on deploying Azure Bastion using PowerShell, with all code examples and step-by-step instructions provided only for PowerShell. The VM creation quickstart links and references are Windows-centric, and there are no equivalent Linux CLI or Bash examples. Although Azure CLI is mentioned as an alternative in a bullet list, it is not demonstrated or prioritized. Linux users are left without direct guidance or parity in deployment steps.
Recommendations
  • Add equivalent Azure CLI (bash) examples alongside PowerShell for all deployment steps.
  • Provide explicit Linux VM creation instructions and quickstart links, not just Windows.
  • Ensure that connection steps and port requirements are illustrated for both Windows (RDP) and Linux (SSH) with equal prominence.
  • Reorganize the documentation so that cross-platform options (PowerShell, Azure CLI, Portal) are presented together, rather than PowerShell-first.
  • Include notes or callouts for platform-specific differences, especially for users running Linux or macOS.
GitHub Create Pull Request
Bastion Working with VMs and NSGs in Azure Bastion ...s/azure-docs/blob/main/articles/bastion/bastion-nsg.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only a PowerShell script for configuring NSG rules, which is a Windows-centric tool. There are no equivalent examples using Azure CLI, Bash, or other cross-platform tools commonly used on Linux/macOS. The exclusive use of PowerShell and lack of Linux-friendly instructions or parity examples indicate a bias toward Windows users and tooling.
Recommendations
  • Add equivalent Azure CLI (az network nsg rule create ...) examples for all NSG rule configurations.
  • Provide Bash script snippets for Linux/macOS users where appropriate.
  • Explicitly mention that PowerShell is available cross-platform, but also provide instructions for installing and using Azure CLI on Linux.
  • Consider reordering or balancing example sections so that Linux-friendly tools (Azure CLI, Bash) are presented alongside or before PowerShell.
  • Include notes or links to official Azure CLI documentation for NSG management.
GitHub Create Pull Request
Bastion About Azure Bastion configuration settings ...s/blob/main/articles/bastion/configuration-settings.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently listing Azure PowerShell (a Windows-centric tool) before Azure CLI in configuration tables, and by providing detailed PowerShell references while omitting equivalent Linux shell or Bash examples. There are no explicit Linux-specific instructions or examples, and the use of PowerShell as a primary automation method may alienate Linux users. The documentation does not mention Linux tools or patterns, nor does it provide parity in example commands for Linux environments.
Recommendations
  • Provide Bash or shell script examples alongside PowerShell for each configuration method.
  • List Azure CLI before or alongside PowerShell in tables to reflect cross-platform parity.
  • Explicitly mention that Azure CLI works natively on Linux/macOS and provide links to installation guides for those platforms.
  • Include notes or sections for Linux administrators, highlighting any differences or considerations when configuring Azure Bastion from Linux environments.
  • Avoid assuming PowerShell as the default automation tool; clarify that both PowerShell and CLI are supported and cross-platform.
GitHub Create Pull Request
Bastion Connect to a Linux VM using SSH .../main/articles/bastion/bastion-connect-vm-ssh-linux.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page, while focused on connecting to Linux VMs, demonstrates a bias towards Windows tooling and patterns. References to creating and managing Azure Key Vault resources and secrets consistently point to PowerShell-based instructions and links, with no equivalent Linux shell (bash) or cross-platform CLI examples. The guidance for storing SSH keys in Azure Key Vault recommends PowerShell or Azure CLI, but only links to PowerShell instructions. There are no explicit Linux shell examples or links, and the documentation does not provide parity for Linux users in terms of command-line instructions or tooling references.
Recommendations
  • Add links and examples for creating and managing Azure Key Vault resources and secrets using Bash or Azure CLI on Linux.
  • Where PowerShell is mentioned, also mention and link to equivalent Linux shell or Azure CLI instructions.
  • Ensure all references to tooling (such as storing SSH keys) include both Windows and Linux approaches, with clear parity.
  • Include explicit Linux command-line examples for common operations, such as storing SSH keys in Key Vault, to support Linux users.
  • Review all external links to ensure they are not Windows/PowerShell-centric and provide alternatives for Linux environments.
GitHub Create Pull Request
Bastion Add scale units for host scaling: Azure portal ...s/blob/main/articles/bastion/configure-host-scaling.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the only command-line alternative to the Azure portal, with no mention of Linux-native tools (e.g., Azure CLI or Bash scripting). The example and instructions are portal-based, which is cross-platform, but the only scriptable method highlighted is PowerShell, a Windows-centric tool. There are no Linux-specific examples or parity in command-line instructions.
Recommendations
  • Include Azure CLI instructions for host scaling alongside PowerShell, as Azure CLI is cross-platform and commonly used on Linux.
  • Explicitly mention that the Azure portal is accessible from any OS, but provide parity in scriptable examples for both Windows (PowerShell) and Linux (Azure CLI/Bash).
  • Add links or references to Linux-friendly documentation or tutorials for configuring host scaling.
  • Review other related documentation to ensure Linux users are equally supported in automation and scripting scenarios.
GitHub Create Pull Request
Bastion Configure Bastion for Kerberos authentication - Azure portal ...ain/articles/bastion/kerberos-authentication-portal.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page is heavily biased toward Windows environments. All examples, instructions, and templates assume Windows Server and Windows 10 VMs, with no mention of Linux equivalents. Kerberos configuration references only Windows documentation, and all automation uses PowerShell scripts and Windows-specific tools (e.g., Local Group Policy Editor, ADDSDeployment PowerShell module). There are no Linux VM deployment examples, nor guidance for configuring Kerberos authentication with Linux domain controllers or clients.
Recommendations
  • Add examples and instructions for deploying and configuring Kerberos authentication with Linux VMs (e.g., Ubuntu, CentOS) as both domain controllers and clients.
  • Provide equivalent Linux automation scripts (e.g., Bash, cloud-init) for domain join and Kerberos configuration.
  • Reference Linux Kerberos documentation (e.g., MIT Kerberos, Samba/Active Directory integration) alongside Windows resources.
  • Include guidance for verifying Kerberos authentication on Linux (e.g., using kinit, klist, and system logs).
  • Offer ARM template parameters or examples that allow selection of Linux images for domain controller and client roles.
GitHub Create Pull Request
Bastion Quickstart: Connect to a VM using Azure Bastion Developer: Azure portal ...ocs/blob/main/articles/bastion/quickstart-developer.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias. Windows is mentioned first in several contexts, such as in the quickstart links for creating VMs and in the required inbound ports section. Keyboard shortcut examples are Windows-centric, and there is a focus on Windows tools and patterns (e.g., CTRL+ALT+END for Windows VMs, references to Windows client behavior). There are no explicit Linux command-line or SSH examples, and Linux-specific details are minimal.
Recommendations
  • Alternate the order of Windows and Linux references throughout the documentation to avoid always listing Windows first.
  • Provide Linux-specific examples and notes where relevant, such as SSH connection instructions, Linux keyboard shortcuts, and expected desktop/session differences.
  • Include Linux client behaviors and shortcuts for connecting to both Windows and Linux VMs, especially when discussing remote desktop or terminal access.
  • Ensure parity in troubleshooting and feature explanations for both Windows and Linux VM scenarios.
  • Add explicit examples or links for connecting to Linux VMs using Bastion Developer, including any differences in authentication or session management.
GitHub Create Pull Request
Bastion Quickstart: Deploy Azure Bastion automatically ...s/blob/main/articles/bastion/quickstart-host-portal.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows VM creation is mentioned before Linux in prerequisites, and Windows-specific details (such as port 3389 and keyboard shortcuts for Windows VMs) are given more prominence. There are no Linux-specific connection examples, troubleshooting tips, or equivalent keyboard shortcut guidance for Linux VMs. The documentation also references Windows tools and patterns (e.g., RDP, Windows keyboard shortcuts) without providing Linux alternatives.
Recommendations
  • Present Linux VM creation instructions before or alongside Windows instructions to avoid 'windows_first' bias.
  • Include Linux-specific connection details, such as SSH client usage, keyboard shortcuts, and troubleshooting tips for Linux VMs.
  • Provide parity in examples and guidance for both RDP (Windows) and SSH (Linux) connections, including screenshots or step-by-step instructions for Linux users.
  • Mention Linux tools and patterns (e.g., SSH clients, terminal usage) where Windows tools are referenced.
  • Add notes about differences in clipboard and keyboard shortcut behavior for Linux VMs and clients.
GitHub Create Pull Request
Bastion Create a shareable link for Azure Bastion ...zure-docs/blob/main/articles/bastion/shareable-link.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates Windows bias by exclusively referencing the Azure portal (a web GUI most commonly used on Windows) and PowerShell cmdlets for permissions management, without mentioning or providing equivalent CLI examples for Linux users (such as Azure CLI or Bash). There are no Linux-specific instructions, nor are Linux tools or workflows (e.g., SSH from a Linux terminal, az CLI) discussed, even though Bastion supports SSH and RDP, both relevant to Linux environments.
Recommendations
  • Add Azure CLI and Bash examples for managing shareable links and permissions, alongside PowerShell.
  • Include instructions for connecting to VMs using SSH from Linux/macOS terminals, not just via the browser.
  • Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux users.
  • Where PowerShell cmdlets are listed, also provide equivalent az CLI commands.
  • Add screenshots or walkthroughs showing Linux workflows (e.g., using a Linux desktop to access Bastion links).
GitHub Create Pull Request
Bastion File transfer via native client ...lob/main/articles/bastion/vm-upload-download-native.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting Windows RDP and native client instructions first, focusing on Windows-specific tools (MSTSC, right-click Copy/Paste), and omitting explicit Linux file transfer examples (e.g., no Linux RDP client instructions, no Linux GUI workflow). Linux instructions are referenced generically and only in the context of SSH/SCP, without concrete Linux-native client usage details.
Recommendations
  • Add explicit Linux file transfer examples, including step-by-step instructions using popular Linux RDP clients (e.g., Remmina, rdesktop, FreeRDP) for RDP-based transfer.
  • Provide screenshots or workflow descriptions for file transfer on Linux, similar to the Windows right-click Copy/Paste method.
  • Present Linux and Windows instructions in parallel sections, or alternate which platform is described first.
  • Mention macOS workflows and clients where relevant to ensure cross-platform parity.
  • Clarify which features or workflows are platform-specific and which are universal, to avoid implying Windows is the default or only supported platform.
GitHub Create Pull Request
Bastion Create a shareable link for Azure Bastion ...zure-docs/blob/main/articles/bastion/shareable-link.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates Windows bias by exclusively referencing the Azure portal UI and PowerShell cmdlets for permissions management, without mentioning or providing examples for Linux tools or CLI equivalents. There are no instructions or screenshots for Linux users, nor are Azure CLI or Bash examples provided for any of the described operations.
Recommendations
  • Add Azure CLI (cross-platform) examples for enabling the Shareable Link feature, creating, viewing, and deleting shareable links.
  • Include Bash or shell script snippets for Linux users where applicable.
  • Reference Linux-native tools and workflows (e.g., SSH from Bash) alongside Windows/PowerShell methods.
  • Ensure screenshots and instructions are not exclusively tied to the Windows Azure portal UI; clarify that the portal is web-based and accessible from Linux and Mac browsers.
  • Provide parity in permissions management by including Azure CLI or REST API instructions for configuring IAM roles and permissions.
GitHub Create Pull Request
Bastion Deploy Bastion:PowerShell ...ain/articles/bastion/bastion-create-host-powershell.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page is heavily focused on PowerShell, which is primarily a Windows-centric tool, and all deployment examples use PowerShell commands. References to VM creation and connection steps link first to Windows VM articles, with Linux VM instructions only mentioned in passing (e.g., SSH port 22). There are no Linux shell (Bash) or Azure CLI examples provided directly on the page, and Linux-specific patterns or tools are absent.
Recommendations
  • Add equivalent Azure CLI (Bash) examples for all deployment steps, either inline or in parallel with PowerShell examples.
  • Provide explicit links and examples for creating and managing Linux VMs, not just Windows VMs.
  • Mention cross-platform tooling (e.g., Azure CLI, Bash scripts) at the same prominence as PowerShell.
  • Ensure connection instructions and troubleshooting steps include Linux scenarios and tools.
  • Reorder or balance references so that Linux and Windows instructions/examples are presented with equal visibility.
GitHub Create Pull Request
Bastion Connect to a Linux VM using SSH .../main/articles/bastion/bastion-connect-vm-ssh-linux.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias, primarily in the sections describing how to create and manage Azure Key Vault resources. The instructions and links for creating a Key Vault and storing SSH keys reference PowerShell and Azure CLI, but the quick-create link is specifically for PowerShell. There are no explicit Linux shell (bash) examples or references, nor are there instructions for using Linux-native tools or workflows. The documentation does not provide parity for Linux users in terms of command-line examples or guidance, and the use of PowerShell is implicitly prioritized.
Recommendations
  • Add explicit bash/Linux shell examples for creating and managing Azure Key Vault resources, alongside PowerShell examples.
  • Provide links to Azure CLI documentation that demonstrate Linux-compatible workflows for storing SSH keys in Key Vault.
  • Ensure that references to PowerShell are balanced with equivalent Linux shell instructions, especially in quick-create scenarios.
  • Clarify that both Windows and Linux users can use Azure CLI, and provide sample commands for both environments.
  • Consider including a section or note on using Linux-native tools for SSH key management and Azure resource provisioning.
GitHub Create Pull Request
Bastion Azure Bastion FAQ ...s/azure-docs/blob/main/articles/bastion/bastion-faq.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several areas. Browser recommendations are Windows-centric, with Windows browsers mentioned first and Mac/Linux options less clearly presented. Keyboard layout configuration instructions are provided only for Windows, with no equivalent steps for Linux or Mac users. References to RDP (a Windows protocol) are frequent, and links to Microsoft Entra authentication focus on Windows VM sign-in, with no mention of Linux VM authentication. There are no Linux-specific examples or guidance for common tasks such as keyboard layout changes, native client usage, or authentication.
Recommendations
  • Add explicit Linux and Mac instructions where configuration steps are given (e.g., how to set keyboard layouts on Linux and Mac).
  • When listing supported browsers, mention Linux compatibility and provide browser options for Linux users.
  • Include references and links to documentation for connecting to Linux VMs (e.g., SSH authentication, Entra ID for Linux if supported).
  • When discussing native clients, provide examples for both RDP (Windows) and SSH (Linux/Mac), and clarify any differences in feature support.
  • Ensure parity in troubleshooting and permissions guidance for both Windows and Linux VM scenarios.
GitHub Create Pull Request
Bastion Working with VMs and NSGs in Azure Bastion ...s/azure-docs/blob/main/articles/bastion/bastion-nsg.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only a PowerShell script for configuring NSG rules, which is specific to Windows environments. There are no equivalent examples for Linux users (e.g., Azure CLI, Bash, or ARM templates). The exclusive use of PowerShell and omission of cross-platform tools or examples creates a Windows-centric bias, making it less accessible for users on Linux or macOS.
Recommendations
  • Add Azure CLI examples for all NSG rule creation steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash script snippets or ARM template samples to demonstrate NSG configuration in a platform-agnostic way.
  • Explicitly mention that PowerShell is just one option and provide links or references to documentation for other platforms.
  • Ensure screenshots and walkthroughs do not assume a Windows environment (e.g., avoid showing only PowerShell terminals).
GitHub Create Pull Request
Bastion About Azure Bastion configuration settings ...s/blob/main/articles/bastion/configuration-settings.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by consistently listing Azure PowerShell as a primary configuration method, often before Azure CLI, and never mentioning Linux-specific tools or workflows. Examples and links are provided for PowerShell and Azure portal, but there are no Linux shell or Bash script examples. The documentation does not acknowledge Linux users or provide parity for Linux-native administration patterns.
Recommendations
  • Add explicit Bash and Linux shell examples for each configuration step, especially for subnet and public IP creation.
  • Ensure Azure CLI examples are complete and shown before or alongside PowerShell examples, with Linux usage context.
  • Reference Linux-native tools or workflows where applicable (e.g., scripting with Bash, using SSH keys stored in Linux file systems).
  • Include guidance for configuring Azure Bastion from Linux environments, such as using the Azure CLI in Bash.
  • Balance documentation so that Windows and Linux methods are presented with equal prominence and detail.
GitHub Create Pull Request
Bastion Configure Bastion for native client connections ...azure-docs/blob/main/articles/bastion/native-client.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows native client connection instructions and examples before Linux equivalents, providing more detailed Windows scenarios, and referencing Windows tools (RDP) more prominently. Linux instructions are present but less emphasized, and there is a lack of parity in example detail and ordering.
Recommendations
  • Present Linux and Windows instructions with equal prominence and detail, ideally side-by-side or in parallel sections.
  • Ensure Linux examples (e.g., SSH commands, file transfer) are as detailed as Windows examples, including screenshots and step-by-step instructions.
  • Avoid listing Windows scenarios first in tables and navigation; alternate or group by use case rather than OS.
  • Include explicit Linux tool references (e.g., OpenSSH, Remmina for RDP) where appropriate.
  • Review and expand limitations and troubleshooting sections to cover Linux-specific issues.
GitHub Create Pull Request
Bastion Configure Bastion for Kerberos authentication - Azure portal ...ain/articles/bastion/kerberos-authentication-portal.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias throughout. All examples, templates, and instructions focus exclusively on Windows Server and Windows 10 VMs. Only Windows domain controllers are referenced, and all configuration scripts use PowerShell. There are no examples or guidance for deploying Kerberos authentication with Linux VMs, Linux domain controllers (such as Samba/FreeIPA), or using Linux-native tools. References and links point to Windows-specific documentation, and the verification steps rely on Windows Group Policy Editor and NTLM settings, which are not applicable to Linux environments.
Recommendations
  • Add parallel instructions and examples for configuring Kerberos authentication with Linux VMs (e.g., Ubuntu, CentOS) in Azure.
  • Include guidance for deploying and configuring a Linux-based domain controller (such as Samba AD DC or FreeIPA) and joining Linux VMs to the domain.
  • Provide Linux shell (bash) equivalents for deployment and verification steps, including ARM template deployment via Azure CLI.
  • Reference Linux documentation for Kerberos and Active Directory integration (e.g., MIT Kerberos, Samba, sssd).
  • Clarify any Azure Bastion limitations regarding Linux Kerberos support, and if supported, document the steps and caveats.
  • Ensure that verification steps include Linux methods (e.g., checking /etc/krb5.conf, using kinit/klist, system logs) for confirming Kerberos authentication.
GitHub Create Pull Request
Bastion Quickstart: Connect to a VM using Azure Bastion Developer: Azure portal ...ocs/blob/main/articles/bastion/quickstart-developer.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias. While both Windows and Linux are mentioned in prerequisites and port requirements, the flow and examples tend to prioritize Windows. The VM creation quickstart links list Windows before Linux, and keyboard shortcut guidance is only provided for connecting to Windows VMs (including from Mac clients), with no equivalent Linux desktop guidance. There are no explicit Linux command-line or desktop examples, and references to tools or behaviors (e.g., CTRL+ALT+END) are Windows-specific.
Recommendations
  • Alternate the order of Windows and Linux references, or list Linux first in some sections to balance visibility.
  • Provide equivalent Linux desktop connection guidance, such as keyboard shortcuts for common Linux desktop environments (e.g., GNOME, KDE) when accessed via Bastion.
  • Include Linux-specific examples or notes where Windows-specific behaviors are described (e.g., clipboard, keyboard shortcuts, session behaviors).
  • If referencing Windows tools or behaviors, add parallel Linux instructions or clarify when a step is Windows-only.
  • Ensure that screenshots or illustrations include both Windows and Linux VM session examples where applicable.
GitHub Create Pull Request
Bastion Quickstart: Deploy Azure Bastion automatically ...s/blob/main/articles/bastion/quickstart-host-portal.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windows Heavy Examples
Summary
The documentation page exhibits a mild Windows bias. Windows VM creation is mentioned before Linux VM creation in the prerequisites, and Windows-specific details (such as port 3389 and keyboard shortcuts for Windows VMs) are provided with more depth and prominence. Keyboard shortcut examples focus on connecting to Windows VMs from Windows and Mac clients, with no equivalent Linux VM shortcut guidance. The documentation also references RDP (a Windows protocol) alongside SSH, but does not provide parity in Linux-specific remote access patterns or troubleshooting.
Recommendations
  • Alternate the order of Windows and Linux VM instructions, or present them side-by-side to avoid Windows-first bias.
  • Provide Linux-specific keyboard shortcut guidance for remote connections, especially for common SSH terminal operations.
  • Expand examples and troubleshooting to include Linux VM scenarios (e.g., SSH key authentication, clipboard behavior in Linux remote sessions).
  • Mention Linux remote desktop protocols (such as xrdp or VNC) where relevant, not just RDP.
  • Ensure that all steps and features described for Windows VMs are equally covered for Linux VMs, including audio output and clipboard usage.
GitHub Create Pull Request
← Previous Page 1 of 9 Next →