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 51-75 of 222 flagged pages
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-host-portal.md ...s/blob/main/articles/bastion/quickstart-host-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows VM creation is mentioned before Linux VM creation, Windows-specific ports and keyboard shortcuts are described in detail, and connection instructions focus on Windows scenarios (e.g., Ctrl+Alt+End for Windows VMs, with only a brief mention of Mac clients connecting to Windows VMs). There are no Linux-specific connection examples, troubleshooting tips, or keyboard shortcut references. The documentation does not provide parity in examples or guidance for Linux users.
Recommendations
  • Present Linux VM creation instructions before or alongside Windows instructions to avoid 'windows_first' bias.
  • Include Linux-specific connection examples, such as SSH authentication workflows, keyboard shortcuts, and troubleshooting tips for common Linux desktop environments.
  • Add references to Linux tools and patterns (e.g., SSH clients, terminal usage) where Windows tools (like RDP) are mentioned.
  • Ensure that port information and connection steps are equally detailed for both Windows (RDP) and Linux (SSH) scenarios.
  • Provide parity in documentation for both operating systems, including screenshots and step-by-step guides for Linux users.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/shareable-link.md ...zure-docs/blob/main/articles/bastion/shareable-link.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 focusing exclusively on Azure portal GUI steps and referencing PowerShell cmdlets for permissions management, without mentioning Linux equivalents (such as Azure CLI or Bash scripting). There are no examples or instructions for Linux users, and Windows-centric tools (PowerShell) are referenced before any cross-platform alternatives.
Recommendations
  • Add Azure CLI examples for creating, managing, and deleting shareable links, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash scripting examples for automating Bastion shareable link management.
  • Reference Linux and macOS workflows for connecting to VMs via Bastion, such as using SSH from a terminal.
  • Clarify that PowerShell cmdlets can be run on Linux/macOS via PowerShell Core, or provide equivalent Azure CLI commands.
  • Ensure screenshots and instructions are not solely based on Windows environments; include notes or visuals for Linux users where relevant.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/work-remotely-support.md ...cs/blob/main/articles/bastion/work-remotely-support.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as a primary configuration method, referencing RDP before SSH, and omitting explicit Linux-oriented examples or tools. The order and emphasis suggest a preference for Windows workflows, with limited guidance for Linux users.
Recommendations
  • Provide explicit Linux examples, such as using SSH from a Linux terminal or configuring Bastion via Bash scripts.
  • List SSH connectivity and Azure CLI usage before or alongside PowerShell and RDP to balance the order of presentation.
  • Include references to Linux remote desktop tools (e.g., xrdp, Remmina) and instructions for accessing Linux VMs.
  • Add troubleshooting and configuration steps specific to Linux environments.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-create-host-powershell.md ...ain/articles/bastion/bastion-create-host-powershell.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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, which is most commonly used on Windows. All code examples and setup instructions use PowerShell, and links for VM creation reference Windows VM quickstarts first. There are no Linux shell (Bash) or Azure CLI examples provided inline, and Linux VM creation is only mentioned in passing (for SSH port requirements), not with dedicated instructions or examples.
Recommendations
  • Add equivalent Azure CLI (Bash) examples for all deployment steps alongside PowerShell examples.
  • Provide explicit instructions and quickstart links for creating Linux VMs, not just Windows VMs.
  • Ensure that Linux and cross-platform tools are mentioned and demonstrated with parity to Windows/PowerShell tools.
  • Consider restructuring the page or adding tabs/sections for both PowerShell and Azure CLI workflows.
  • Clarify that PowerShell can be used cross-platform, but also highlight and demonstrate native Bash/CLI workflows for Linux users.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/shareable-link.md ...zure-docs/blob/main/articles/bastion/shareable-link.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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, with no mention of Linux equivalents (such as Azure CLI or Bash scripting). There are no examples or instructions for Linux users, and Windows-centric tools are referenced first and exclusively. The lack of cross-platform command-line examples limits accessibility for Linux administrators.
Recommendations
  • Add Azure CLI examples for all operations, including enabling the Shareable Link feature, creating/deleting shareable links, and managing permissions.
  • Include Bash scripting examples where appropriate, especially for automation tasks.
  • Explicitly mention cross-platform compatibility and provide instructions for both Windows and Linux users.
  • Reference Linux tools and workflows (e.g., SSH, scp, Azure CLI) alongside or before Windows/PowerShell equivalents.
  • Ensure screenshots and UI instructions are supplemented with command-line alternatives for headless or non-GUI environments.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/configuration-settings.md ...s/blob/main/articles/bastion/configuration-settings.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 as a primary configuration method alongside the Azure portal, with Azure CLI (the more cross-platform tool) often listed last. There are no examples or references to Linux-specific tools, shell scripts, or workflows. The documentation does not mention or provide guidance for Linux users beyond the Azure CLI, and the PowerShell examples may not be directly usable on Linux systems without additional context.
Recommendations
  • List Azure CLI examples before or alongside Azure PowerShell to reflect cross-platform parity.
  • Provide explicit Linux shell (bash) examples for common configuration tasks, especially for subnet and public IP configuration.
  • Clarify that Azure CLI is fully supported on Linux and macOS, and link to installation guides for those platforms.
  • Avoid using Windows-centric terminology (e.g., PowerShell parameters) without also providing equivalent Linux/CLI commands.
  • Add a section or notes for Linux administrators, highlighting any OS-specific considerations or best practices.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-nsg.md ...s/azure-docs/blob/main/articles/bastion/bastion-nsg.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 for Linux users, such as Azure CLI or Bash scripts. The exclusive use of PowerShell and lack of Linux-oriented tooling or examples demonstrates a clear Windows bias.
Recommendations
  • Add Azure CLI examples for all NSG rule creation steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Provide Bash script snippets for automating NSG configuration, or reference how to use Azure CLI in shell scripts.
  • Explicitly mention that PowerShell is available on Linux and macOS, but still provide native CLI examples for parity.
  • Consider including a table or section comparing PowerShell and Azure CLI commands for common NSG tasks.
  • Review other sections for similar tooling bias and ensure Linux/macOS users are equally supported.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-host-portal.md ...s/blob/main/articles/bastion/quickstart-host-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows VM creation before Linux VM creation, mentioning Windows-specific ports and keyboard shortcuts in greater detail, and providing examples and instructions that are more tailored to Windows users. Linux equivalents are mentioned but not elaborated upon, and Linux-specific usage patterns (such as SSH key handling or Linux keyboard shortcuts) are missing.
Recommendations
  • Present Linux and Windows VM creation instructions in parallel, or alternate the order to avoid Windows-first bias.
  • Provide Linux-specific examples and instructions, such as SSH key usage, Linux keyboard shortcuts, and troubleshooting tips for Linux VMs.
  • Include details about connecting to Linux VMs via Bastion, such as terminal behaviors, clipboard usage, and any differences in user experience compared to Windows.
  • Expand the explanation of required ports to clarify their relevance for both OS types, and mention any Linux-specific configuration considerations.
  • Ensure that all features and steps are equally documented for both Windows and Linux environments, including screenshots or interface differences if applicable.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/configure-host-scaling.md ...s/blob/main/articles/bastion/configure-host-scaling.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page focuses exclusively on using the Azure portal for host scaling and references PowerShell as an alternative method, which is primarily associated with Windows environments. There are no examples or mentions of Linux-native tools or CLI commands (such as Azure CLI), and PowerShell is referenced before any Linux-equivalent method. This creates a bias towards Windows users and omits guidance for Linux users.
Recommendations
  • Add instructions and examples for configuring host scaling using the Azure CLI, which is cross-platform and widely used on Linux.
  • When mentioning alternative methods, list both PowerShell and Azure CLI, or present Azure CLI first to avoid Windows-first bias.
  • Include explicit references to Linux environments and tools where applicable, ensuring parity in documentation for users on all platforms.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/vm-upload-download-native.md ...lob/main/articles/bastion/vm-upload-download-native.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 file transfer instructions first, focusing on the Windows native client (MSTSC), and describing file transfer via right-click, copy, and paste—an exclusively Windows pattern. Linux instructions are only mentioned secondarily, and there are no explicit Linux-native file transfer examples (e.g., using Nautilus, GNOME, or other Linux desktop tools). The SCP example is generic and lacks Linux-specific context or screenshots.
Recommendations
  • Present Linux and Windows instructions in parallel sections or alternate the order to avoid Windows-first bias.
  • Include explicit Linux-native client examples for file transfer, such as using graphical file managers (Nautilus, Dolphin) or command-line tools (rsync, scp) with Linux-specific syntax.
  • Add screenshots or step-by-step instructions for Linux users, showing how to initiate file transfers from common Linux environments.
  • Clarify which steps apply to Linux, macOS, and Windows, and avoid language that assumes Windows as the default.
  • Mention Linux desktop equivalents to Windows tools (e.g., MSTSC vs. Remmina or KRDC) and provide usage examples.
GitHub Create Pull Request
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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in its references to PowerShell for Azure Key Vault setup and secret management. The instructions for creating a Key Vault and storing SSH keys link to PowerShell-based guides and mention PowerShell and Azure CLI as preferred methods, with no explicit Linux shell (bash) or cross-platform CLI examples. There are no Linux-specific command-line examples or guidance, and Windows-centric tooling is referenced before or instead of Linux alternatives.
Recommendations
  • Provide explicit bash/Azure CLI examples for creating a Key Vault and storing SSH keys, alongside PowerShell instructions.
  • Link to cross-platform or Linux-specific documentation for Azure Key Vault setup, not just PowerShell guides.
  • Clarify that Azure CLI works on Linux, macOS, and Windows, and provide sample commands for each platform where relevant.
  • Avoid language that implies PowerShell is the default or preferred method; present both PowerShell and bash/CLI options equally.
  • Include troubleshooting or workflow notes for Linux users, such as file permissions and SSH key formatting.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/native-client.md ...azure-docs/blob/main/articles/bastion/native-client.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing Windows native client connection instructions and examples before Linux equivalents, providing more detailed references and links for Windows scenarios, and omitting direct Linux client usage examples in several sections. The connection table and 'Next steps' section prioritize Windows, and Linux instructions are less prominent or only referenced via tunnel commands.
Recommendations
  • Present Linux and Windows examples in parallel, or alternate which comes first in tables and instructions.
  • Provide direct, step-by-step Linux native client connection instructions (not just tunnel commands) with explicit examples.
  • Ensure that screenshots and walkthroughs are available for both Windows and Linux environments.
  • Include references and links for Linux-specific guides in the 'Next steps' section, similar to those provided for Windows.
  • Mention Linux tools (e.g., OpenSSH, Remmina, etc.) alongside Windows tools where relevant.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/kerberos-authentication-portal.md ...ain/articles/bastion/kerberos-authentication-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. All examples, instructions, and resource deployments are centered around Windows Server and Windows 10 VMs. Only Windows domain controllers are referenced, and all Kerberos authentication steps assume a Windows environment. Powershell is the exclusive scripting tool used for automation and configuration, with no mention of Linux equivalents. There are no examples or guidance for configuring Kerberos authentication with Linux VMs, nor are Linux-based domain controllers (such as Samba/FreeIPA) discussed.
Recommendations
  • Add parallel examples for deploying and configuring Kerberos authentication with Linux VMs (e.g., Ubuntu, CentOS) in Azure.
  • Include instructions for setting up a Linux-based domain controller (such as Samba or FreeIPA) and joining Linux VMs to the domain.
  • Provide bash/CLI examples for ARM template deployment and VM configuration, alongside Powershell.
  • Reference Linux documentation for Kerberos authentication and Active Directory integration.
  • Clarify any Azure Bastion limitations regarding Linux Kerberos support, and provide workarounds or alternatives if available.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-developer.md ...ocs/blob/main/articles/bastion/quickstart-developer.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tools and patterns, such as keyboard shortcuts for Windows VMs, and listing Windows VM creation before Linux VM creation. There is a lack of Linux-specific examples, especially regarding connection behavior, keyboard shortcuts, and troubleshooting. The documentation also mentions Windows ports and tools before their Linux equivalents and does not provide parity in guidance for Linux users.
Recommendations
  • Provide Linux-specific connection examples, including screenshots and keyboard shortcut guidance for Linux VMs.
  • Ensure that instructions for creating Linux VMs are given equal prominence and detail as Windows VM instructions.
  • Include troubleshooting tips and behavioral notes for Linux VM sessions (e.g., clipboard, audio, keyboard shortcuts) similar to those provided for Windows.
  • List required ports for Linux and Windows together, or alternate their order to avoid Windows-first bias.
  • Where Windows tools or patterns are mentioned (e.g., CTRL+ALT+END), provide equivalent Linux or Mac instructions.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/whats-new.md ...ocs/azure-docs/blob/main/articles/bastion/whats-new.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows RDP features and links before Linux SSH equivalents, using Windows-specific terminology (RDP, graphical session recording) more prominently, and omitting explicit Linux examples or tools in the feature descriptions. The feature table references RDP (Windows) before SSH (Linux), and does not provide parity in describing Linux-specific workflows or tools.
Recommendations
  • Ensure Linux/SSH features are described with equal prominence and detail as Windows/RDP features.
  • Alternate the order of Windows and Linux features in tables and lists, or group them together to avoid prioritizing one platform.
  • Include explicit examples, links, and terminology for Linux workflows (e.g., SSH, Linux session recording) wherever Windows features are mentioned.
  • Add references to Linux tools and patterns (such as SSH clients, Linux session recording options) in feature descriptions and limitations.
  • Review and update documentation to avoid Windows-first ordering and terminology, ensuring cross-platform parity.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/work-remotely-support.md ...cs/blob/main/articles/bastion/work-remotely-support.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page references PowerShell as a primary method for configuring Azure Bastion, which is typically associated with Windows environments. There is no mention of Linux-specific tools or workflows, and examples or instructions for Linux users are missing. The ordering of configuration options lists PowerShell before Azure CLI, which may suggest a Windows-first approach.
Recommendations
  • Add explicit Linux-focused examples and workflows, such as using SSH from Linux terminals.
  • Provide step-by-step instructions for configuring Azure Bastion using native Linux tools and environments.
  • Reorder configuration options to present Azure CLI (cross-platform) before PowerShell, or clarify parity between platforms.
  • Include references to Linux desktop environments and remote access tools (e.g., Remmina, GNOME Terminal) where relevant.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-host-portal.md ...s/blob/main/articles/bastion/quickstart-host-portal.md
High Priority View Details →
Scanned: 2026-01-06 18:15
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows VM creation before Linux VM creation, mentioning Windows-specific ports and keyboard shortcuts in more detail, and providing examples and instructions that prioritize Windows scenarios. There is a lack of parity in Linux-specific examples, especially regarding keyboard shortcuts and connection details.
Recommendations
  • Present Linux VM creation instructions before or alongside Windows instructions to avoid 'windows_first' bias.
  • Include Linux-specific connection details, such as keyboard shortcuts for common tasks when connecting to Linux VMs via Bastion.
  • Expand the section on required VM inbound ports to provide equal detail for Linux (e.g., mention SSH configuration nuances).
  • Add troubleshooting tips or examples for connecting to Linux VMs, similar to those provided for Windows VMs.
  • Ensure that all examples and tables provide Linux equivalents where applicable, not just Windows-focused values or instructions.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/work-remotely-support.md ...cs/blob/main/articles/bastion/work-remotely-support.md
High Priority View Details →
Scanned: 2026-01-06 18:15
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing PowerShell as a primary configuration method before Azure CLI, which is more commonly used on Linux/macOS. No explicit Linux or SSH examples are provided, and Windows-centric tools (PowerShell) are mentioned without equivalent Linux command-line or shell examples. The page lacks references to Linux remote access patterns or tools, and does not mention SSH clients or Linux desktop environments for remote work.
Recommendations
  • Add explicit Linux/SSH examples for accessing Azure Bastion and managing VMs.
  • Mention Linux command-line tools (e.g., SSH, Azure CLI) alongside or before PowerShell.
  • Provide step-by-step instructions for configuring Azure Bastion from Linux/macOS environments.
  • Include references to Linux desktop remote access tools (e.g., Remmina, xfreerdp) where appropriate.
  • Ensure parity in troubleshooting and FAQ sections for both Windows and Linux users.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/shareable-link.md ...zure-docs/blob/main/articles/bastion/shareable-link.md
High Priority View Details →
Scanned: 2026-01-06 18:15
Reviewed by: Unknown
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, with no mention of Linux equivalents (such as Azure CLI or Bash). All examples and screenshots are based on the Azure portal, which is most commonly used on Windows, and there are no instructions or examples for Linux users or command-line alternatives. The permissions section lists only PowerShell cmdlets, omitting Azure CLI or REST API options that are platform-agnostic.
Recommendations
  • Add Azure CLI examples for enabling, creating, and deleting shareable links, alongside PowerShell cmdlets.
  • Include instructions and screenshots for using the Azure portal on Linux (if any differences exist), or clarify platform neutrality.
  • Document REST API methods for managing shareable links to provide platform-independent options.
  • Explicitly mention that the Azure portal and Bastion shareable links are accessible from browsers on any OS, not just Windows.
  • Provide SSH examples for Linux users connecting to VMs via Bastion, if applicable.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/configuration-settings.md ...s/blob/main/articles/bastion/configuration-settings.md
High Priority View Details →
Scanned: 2025-08-25 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by consistently listing Azure PowerShell (a Windows-centric tool) before Azure CLI in configuration tables, and by providing more detailed PowerShell references. There are no explicit Linux-specific examples or mentions of Linux tools, and the documentation assumes familiarity with Windows patterns (e.g., PowerShell cmdlets). However, Azure CLI (which is cross-platform) is also included, and SSH (a Linux-native protocol) is referenced, but without Linux-specific guidance.
Recommendations
  • Alternate the order of Azure PowerShell and Azure CLI in tables and examples, or list Azure CLI first in some sections to avoid implicit prioritization of Windows tools.
  • Add explicit Linux-focused examples or notes, such as using Bash scripts or Linux shell commands for configuration.
  • Include references to Linux-native tools or workflows where appropriate (e.g., using SSH from a Linux terminal).
  • Clarify that Azure CLI is cross-platform and provide sample commands run from both Windows and Linux environments.
  • Where PowerShell is referenced, consider also referencing Azure Cloud Shell (which supports Bash and PowerShell) to highlight cross-platform options.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/configuration-settings.md ...s/blob/main/articles/bastion/configuration-settings.md
High Priority View Details →
Scanned: 2025-08-24 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently lists Azure PowerShell (a Windows-centric tool) before Azure CLI (cross-platform) in configuration method tables. There are multiple references to PowerShell-specific cmdlets and patterns, and no explicit mention of Linux-native tools or workflows. While Azure CLI is included, the ordering and emphasis favor Windows/PowerShell, and there are no examples or guidance tailored specifically for Linux users.
Recommendations
  • Alternate the order of Azure PowerShell and Azure CLI in tables and examples, or list Azure CLI first to reflect its cross-platform nature.
  • Include explicit Linux shell (bash) command examples, especially for common configuration tasks.
  • Add references to Linux-native tools or workflows where appropriate (e.g., scripting with bash, using SSH from Linux terminals).
  • Clarify that both Azure CLI and PowerShell are cross-platform, but provide guidance for Linux users on installing and using these tools.
  • Where possible, provide parity in documentation for both Windows and Linux environments, including screenshots or walkthroughs if relevant.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/configuration-settings.md ...s/blob/main/articles/bastion/configuration-settings.md
High Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
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 portal and Azure PowerShell methods before Azure CLI, which is more commonly used on Linux. Examples and links for configuration tasks (SKU selection, subnet, public IP, host scaling) are provided for Azure portal and PowerShell, with CLI included but always after Windows-centric tools. There are no explicit Linux shell or scripting examples, nor references to Linux-specific workflows or tools. The documentation does not mention Linux desktop usage or provide parity for Linux administrators beyond the CLI.
Recommendations
  • Alternate the order of examples so that Azure CLI is listed before PowerShell and portal in some sections, or group them without implied priority.
  • Add explicit Bash or shell script examples for common configuration tasks, demonstrating usage from a Linux environment.
  • Include notes or sections addressing Linux-specific workflows, such as using SSH keys from Linux, or integrating with Linux desktop environments.
  • Ensure that all features and configuration steps have CLI examples and links, and verify that CLI instructions are as detailed as PowerShell ones.
  • Consider adding troubleshooting or tips sections for Linux users, e.g., common issues when connecting from Linux clients.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/configuration-settings.md ...s/blob/main/articles/bastion/configuration-settings.md
High Priority View Details →
Scanned: 2025-08-20 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. In configuration tables, Azure PowerShell (a Windows-centric tool) is consistently listed before Azure CLI (which is cross-platform and more common on Linux). There are no explicit Linux-specific examples or references to Linux-native tools or workflows. The documentation assumes familiarity with Windows tools and patterns, such as PowerShell, and does not provide parity for Linux users beyond mentioning Azure CLI.
Recommendations
  • Alternate the order of Azure PowerShell and Azure CLI in tables and examples, or list Azure CLI first to better reflect cross-platform usage.
  • Include explicit Linux-focused examples or notes, such as using Bash scripts or referencing Linux terminal commands where appropriate.
  • Add guidance or links for configuring Azure Bastion using Linux-native tools or environments, such as Bash, Cloud Shell, or automation via shell scripts.
  • Clarify that Azure CLI is cross-platform and provide sample commands that can be run on Linux/macOS terminals.
  • Where PowerShell is mentioned, consider also referencing PowerShell Core (pwsh), which is cross-platform, or clarify when Windows PowerShell is required.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-nsg.md ...s/azure-docs/blob/main/articles/bastion/bastion-nsg.md
High Priority View Details →
Scanned: 2025-08-20 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a detailed PowerShell script for configuring NSG rules but does not include equivalent examples using cross-platform tools such as Azure CLI, Bash, or ARM templates. This approach assumes or prioritizes Windows/PowerShell users, potentially excluding Linux or macOS administrators who may prefer or require non-PowerShell tooling.
Recommendations
  • Add equivalent Azure CLI (az network nsg rule create ...) examples for all NSG rule creation steps, ideally in Bash syntax.
  • Consider providing ARM/Bicep template snippets for infrastructure-as-code parity.
  • Explicitly state that PowerShell is just one option, and link to cross-platform alternatives.
  • Where possible, present Azure CLI or REST API examples before or alongside PowerShell to emphasize platform neutrality.
GitHub Create Pull Request
Bastion https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/work-remotely-support.md ...cs/blob/main/articles/bastion/work-remotely-support.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
← Previous Page 3 of 9 Next →