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 201-222 of 222 flagged pages
Bastion
Tutorial: Deploy Azure Bastion using specified settings: Azure portal
...b/main/articles/bastion/tutorial-create-host-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents both Windows and Linux VM options in the prerequisites, but the Windows VM creation link is listed first. Otherwise, the tutorial is platform-neutral, focusing on Azure portal steps and not favoring Windows-specific tools, commands, or patterns.
Recommendations
- List Linux and Windows VM creation links in parallel or alternate their order to avoid implicit prioritization.
- Explicitly state that all steps apply equally to both Windows and Linux VMs.
- Where connection instructions are referenced, ensure parity in detail and clarity for both SSH (Linux/macOS) and RDP (Windows) scenarios.
Create Pull Request
Bastion
Secure Your Azure Bastion Deployment
...zure-docs/blob/main/articles/bastion/secure-bastion.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by mentioning RDP (Windows) connectivity before SSH (Linux/macOS) in the introduction and by providing Kerberos authentication guidance specifically for domain-joined Windows VMs. While there is a reference to connecting to Linux VMs via Bastion, examples and detailed instructions for Linux/macOS users are less prominent or deferred to linked articles. There are no explicit PowerShell-heavy examples or exclusive use of Windows tools, but the ordering and specificity of Windows features may create minor friction for Linux/macOS users.
Recommendations
- Ensure that SSH (Linux/macOS) connectivity is mentioned equally and as prominently as RDP (Windows) in introductory sections.
- Provide direct, in-page examples or guidance for connecting to Linux/macOS VMs via Bastion, not just via links.
- Include authentication and session management scenarios for Linux/macOS users, such as SSH key management and Linux-specific security controls, alongside Windows scenarios.
- When discussing features like Kerberos, clarify their applicability or provide Linux equivalents if relevant.
- Alternate the order of Windows and Linux guidance, or present both together, to avoid implicit prioritization.
Bastion
Quickstart: Use Terraform to deploy Azure Bastion
...b/main/articles/bastion/quickstart-deploy-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell tab is present and shown alongside CLI, which is most commonly used on Windows. There is no explicit mention of Linux/macOS-specific instructions or troubleshooting, and PowerShell is a Windows-centric tool (despite cross-platform support, it is still more common on Windows). The order of tabs (CLI first, then PowerShell) is appropriate, but the presence of PowerShell examples may indicate a mild Windows bias. No critical steps are Windows-only, and all essential operations can be performed via CLI, which is cross-platform.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS and Windows.
- Clarify that PowerShell is available cross-platform, but CLI is recommended for Linux/macOS users.
- Add troubleshooting notes or links for Linux/macOS users if there are known issues.
- Consider adding a note about shell compatibility (e.g., bash, zsh) for Linux/macOS users.
Bastion
Configure Bastion for native client connections
...azure-docs/blob/main/articles/bastion/native-client.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a Windows-first bias: Windows native client examples and links are presented before Linux equivalents, and the main connection instructions and feature table list Windows scenarios first. References to Windows tools (RDP, native client) are more prominent, and the page structure prioritizes Windows workflows. Linux examples and instructions are present, but are secondary in placement and detail.
Recommendations
- Present Linux and Windows examples side-by-side or in parallel sections, rather than listing Windows first.
- Ensure Linux connection instructions are as detailed and easy to find as Windows instructions.
- Include explicit macOS examples where relevant, as 'Linux' often does not cover all non-Windows platforms.
- Balance screenshots and walkthroughs between Windows and Linux environments.
- Avoid using 'native client' to mean only Windows tools; clarify terminology for cross-platform parity.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows minor Windows bias in several areas. Browser recommendations list Windows browsers first and provide more detail for Windows. Keyboard layout configuration instructions are given only for Windows, with no equivalent steps for Linux or macOS. The example for setting keyboard layouts is Windows-specific, and there are no Linux/macOS instructions for similar tasks. No PowerShell-heavy or Windows tools are referenced, and most features are described in a platform-neutral way.
Recommendations
- Provide instructions for configuring keyboard layouts on Linux and macOS, alongside the Windows steps.
- List browser support in a platform-neutral order, and clarify supported browsers for Linux.
- Where platform-specific instructions are needed (e.g., keyboard layouts, file transfer), include Linux and macOS equivalents.
- Explicitly mention support for Linux/macOS native RDP/SSH clients where relevant.
Bastion
Quickstart: Connect to a VM using Azure Bastion Developer: Azure portal
...ocs/blob/main/articles/bastion/quickstart-developer.md
Low Priority
View Details →
Detected Bias Types
Windows First
Minor Windows Shortcut Notes
Summary
The documentation provides parity between Windows and Linux in VM creation links and port requirements. However, minor Windows bias is present: Windows VM creation is mentioned before Linux, and keyboard shortcut guidance is given only for Windows VMs (with a Mac note for connecting to Windows VMs), with no equivalent Linux desktop shortcut guidance. No PowerShell, Windows-only tools, or missing Linux examples are present.
Recommendations
- List Linux VM creation before or alongside Windows VM creation to avoid implicit prioritization.
- Provide keyboard shortcut guidance for Linux desktop VMs (e.g., how to send Ctrl+Alt+Del or other common shortcuts from various clients).
- Ensure future examples and troubleshooting steps include both Windows and Linux scenarios equally.
Bastion
Quickstart: Use Terraform to deploy Azure Bastion
...b/main/articles/bastion/quickstart-deploy-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides verification steps using both Azure CLI and Azure PowerShell, but lists Azure CLI first. However, the PowerShell section is present and not prioritized above CLI. There are no explicit Windows-only tools or patterns, and all Terraform commands are platform-agnostic. No Linux/macOS-specific examples or troubleshooting are provided, but the CLI instructions are suitable for all platforms.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
- Add a note clarifying that PowerShell examples are for Windows users, while CLI is cross-platform.
- Consider including a bash shell example for Linux/macOS users, especially for environment variable usage.
- Add troubleshooting tips for Linux/macOS environments if any platform-specific issues are common.
Bastion
Quickstart: Deploy Azure Bastion automatically
...s/blob/main/articles/bastion/quickstart-host-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Minor Windows Tools
Summary
The documentation provides parity for both Windows and Linux VMs in prerequisites and port requirements, and links to both Windows and Linux VM creation quickstarts. However, there is a slight Windows-first bias: Windows VM creation is listed before Linux, and keyboard shortcut examples focus on Windows VM connections (with only a brief mention of Mac clients connecting to Windows VMs). There are no Linux-specific connection tips or troubleshooting notes. No PowerShell or Windows-only tools are used, and the portal workflow is OS-agnostic.
Recommendations
- Alternate the order of Windows and Linux VM creation links, or list Linux first in some sections.
- Add keyboard shortcut examples for connecting to Linux VMs (e.g., SSH session tips, clipboard usage).
- Include troubleshooting notes or tips for Linux/macOS users when connecting to Linux VMs via Bastion.
- Explicitly state that the portal-based Bastion connection works equally for Linux and Windows VMs, and mention any OS-specific nuances.
Bastion
Secure Your Azure Bastion Deployment
...zure-docs/blob/main/articles/bastion/secure-bastion.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by mentioning RDP (Windows) connectivity first and providing a direct link to Entra ID authentication for RDP connections (Windows) in the introductory note. Kerberos authentication is discussed only in the context of domain-joined Windows VMs, with no equivalent mention for Linux. While SSH and Linux VM connectivity are referenced, examples and guidance for Linux are less prominent and often appear after Windows-specific features. There are no explicit Linux command-line or tool examples, and Windows-centric authentication and management patterns (Kerberos, RDP) are described in detail before Linux alternatives.
Recommendations
- Provide Linux-specific examples and guidance with equal prominence, including links to SSH authentication and management for Linux VMs.
- Include explicit references to Linux tools and workflows (e.g., SSH key management, Linux session monitoring) alongside Windows/RDP features.
- Ensure that Linux and Windows features are presented in parallel sections or with equal detail, rather than Windows-first.
- Add examples or links for Linux-specific authentication methods (such as certificate-based SSH, PAM integration, etc.) where relevant.
Bastion
Tutorial: Deploy Azure Bastion using specified settings: Azure portal
...b/main/articles/bastion/tutorial-create-host-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows and Linux virtual machines as supported targets for Azure Bastion, but in the prerequisites section, the Windows VM creation link is listed before the Linux VM link. Additionally, the inbound ports section lists Windows (RDP) before Linux (SSH). No examples, instructions, or tools are specific to Windows or PowerShell, and parity is maintained throughout the rest of the tutorial.
Recommendations
- List Linux VM creation links before or alongside Windows VM links to avoid implicit prioritization.
- Mention inbound ports for Linux (SSH) before or alongside Windows (RDP) for neutrality.
- Continue to ensure that all instructions and examples are platform-agnostic and do not favor Windows-specific tools or workflows.
Bastion
Enable remote work by using Azure Bastion
...cs/blob/main/articles/bastion/work-remotely-support.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page references PowerShell as a primary method for configuring Azure Bastion, listing it before Azure CLI. There are no explicit Linux/macOS examples or mentions of SSH clients or Linux-native tools, and the examples lean towards Windows-centric tooling and patterns.
Recommendations
- Add explicit Linux/macOS examples and workflows, such as using SSH from a Linux terminal.
- Mention Linux-native tools and clarify that Azure CLI is cross-platform.
- Provide parity in example ordering (e.g., list Azure CLI before or alongside PowerShell).
- Include references to remote desktop clients available on Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only Azure Portal (GUI) instructions for deploying Bastion in a private-only scenario and does not include any command-line examples. There is no mention of Windows-specific tools (e.g., PowerShell, CMD), but there is also a lack of parity for Linux users, as no CLI (Azure CLI, Bash) instructions are provided. This omission can disadvantage users who prefer or require automation or command-line deployment, especially on Linux.
Recommendations
- Add Azure CLI examples for all deployment steps, showing how to create the virtual network, subnet, and Bastion host in private-only mode.
- Explicitly mention that the Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- If relevant, provide PowerShell examples as well, but ensure that CLI/Bash instructions are given equal prominence.
- Include a section comparing portal-based and command-line deployment, highlighting automation benefits for Linux users.
Bastion
Tutorial: Deploy Azure Bastion using specified settings: Azure portal
...b/main/articles/bastion/tutorial-create-host-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page presents both Windows and Linux VM options, but consistently lists Windows VM creation and RDP port configuration before Linux equivalents. The Windows VM quickstart is mentioned first, and port requirements for Windows (RDP) precede those for Linux (SSH). No PowerShell or Windows-specific tool bias is present, and Linux parity is generally maintained, but ordering suggests a subtle preference for Windows scenarios.
Recommendations
- Alternate the order of Windows and Linux instructions/examples throughout the documentation, or list Linux first in some sections.
- Explicitly state that all steps apply equally to both Windows and Linux VMs, and provide parallel examples where relevant.
- Ensure that any referenced quickstart or connection articles for Linux are as prominent and detailed as those for Windows.
- Consider adding a note on cross-platform parity to reinforce that Bastion supports both OS types equally.
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only Azure Portal (GUI) instructions for deploying Bastion in a private-only scenario, without any command-line examples. There is no mention of platform-specific tools (Windows or Linux), nor are PowerShell, Azure CLI, or other automation methods referenced. However, the absence of CLI examples (such as Azure CLI, which is cross-platform and commonly used on Linux) means Linux users may not have parity with Windows users who often rely on PowerShell or GUI workflows.
Recommendations
- Add Azure CLI example commands for each major deployment step, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that the Azure Portal workflow is platform-agnostic, but provide links or sections for command-line automation.
- If PowerShell examples are added in the future, ensure Azure CLI equivalents are provided and presented equally.
- Include a note on how Linux users can perform the same tasks from their environment, referencing Azure CLI installation and usage.
Bastion
Tutorial: Deploy Azure Bastion using specified settings: Azure portal
...b/main/articles/bastion/tutorial-create-host-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a subtle Windows bias in the prerequisites section, where the example for creating a VM lists 'Quickstart: Create a Windows VM' before 'Quickstart: Create a Linux VM'. However, the rest of the tutorial is platform-neutral, mentioning both RDP (Windows) and SSH (Linux) ports, and does not provide OS-specific instructions or examples. No PowerShell, Windows-only tools, or missing Linux examples are present.
Recommendations
- List Linux and Windows VM creation links in alphabetical order or together, rather than Windows first.
- Where possible, provide equal prominence to Linux and Windows in examples and instructions.
- Continue to ensure all steps and features are described in a platform-neutral way, and avoid implicit prioritization of Windows workflows.
Bastion
Tutorial: Deploy Azure Bastion using specified settings: Azure portal
...b/main/articles/bastion/tutorial-create-host-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows and Linux virtual machines in the prerequisites, but the Windows VM creation link is listed before the Linux VM link. Otherwise, the tutorial is platform-neutral, with no exclusive Windows or PowerShell examples, and connection instructions reference both RDP (Windows) and SSH (Linux) ports. There are no Windows-specific tools or patterns, and Linux parity is generally maintained.
Recommendations
- List Linux and Windows VM creation links in alphabetical order or together to avoid perceived prioritization.
- Explicitly mention that all steps and features apply equally to both Windows and Linux VMs.
- Where connection instructions are referenced, clarify that SSH is for Linux and RDP for Windows, and provide direct links to both connection guides if not already present.
- Review included articles (via INCLUDES) to ensure Linux examples and instructions are present and equally detailed.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/tutorial-create-host-portal.md
...b/main/articles/bastion/tutorial-create-host-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a mild 'windows_first' bias in the prerequisites section, where the Quickstart link for creating a Windows VM is listed before the Linux VM equivalent. However, the rest of the tutorial maintains parity between Windows and Linux, mentioning both RDP (Windows) and SSH (Linux) ports, and does not provide OS-specific examples or favor Windows tools or PowerShell. No exclusive Windows tooling or missing Linux examples are present.
Recommendations
- List Linux and Windows VM Quickstart links together or alternate their order in different documentation pages to avoid perceived prioritization.
- Explicitly state that Bastion supports both Windows (RDP) and Linux (SSH) connections equally in the introduction.
- If providing step-by-step connection instructions, ensure both RDP and SSH workflows are described or linked with equal prominence.
- Continue to avoid OS-specific tooling (e.g., PowerShell, CMD) unless providing equivalent Linux (bash/CLI) examples.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/tutorial-create-host-portal.md
...b/main/articles/bastion/tutorial-create-host-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page presents both Windows and Linux VM options in the prerequisites, but the Windows VM quickstart is listed before the Linux VM quickstart. Additionally, port requirements for Windows (RDP) are mentioned before Linux (SSH). No command-line examples (PowerShell, Bash, CLI) are present, and no Windows-specific tools or patterns are used in the main tutorial steps. Thus, the main evidence of bias is the ordering of Windows before Linux in examples and prerequisites.
Recommendations
- List Linux VM quickstart before or alongside Windows VM quickstart to avoid implicit prioritization.
- Mention SSH (Linux) port before or alongside RDP (Windows) port in the prerequisites.
- Ensure future examples and screenshots show parity between Windows and Linux scenarios.
- If command-line instructions are added, provide both PowerShell (Windows) and Bash/CLI (Linux) examples.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/create-host-cli.md
...ure-docs/blob/main/articles/bastion/create-host-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page provides parity between Windows and Linux in the context of VM creation, mentioning both platforms equally. However, when suggesting quickstart links for VM creation, the Windows VM link is listed before the Linux VM link, indicating a subtle 'windows_first' bias. There are no PowerShell-heavy examples, exclusive Windows tools, or missing Linux examples in the CLI instructions themselves, which are platform-neutral.
Recommendations
- List Windows and Linux VM quickstart links in alphabetical order or explicitly state that both platforms are supported equally.
- Ensure that any example commands or references to connecting to VMs include both Windows and Linux scenarios, especially in sections about connecting and managing VMs.
- Review included links and referenced articles to confirm Linux parity in all connection and management instructions.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/design-architecture.md
...docs/blob/main/articles/bastion/design-architecture.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation discusses RDP and SSH connectivity but does not provide any OS-specific examples or mention tools or workflows unique to either Windows or Linux. However, there is a subtle bias in that RDP (primarily a Windows protocol) is mentioned before SSH (primarily used for Linux), and there are no explicit Linux-specific examples or references to Linux-native tools or workflows. The documentation does not provide parity in illustrating Linux scenarios, such as connecting to Linux VMs via SSH from Linux/macOS clients or using Linux command-line tools.
Recommendations
- Include explicit examples or references for connecting to Linux VMs using SSH from Linux/macOS clients.
- Mention Linux-native tools (such as OpenSSH) and workflows alongside any references to RDP or Windows tools.
- Ensure that any future configuration or usage examples provide parity between Windows and Linux environments.
- Clarify that Azure Bastion supports both RDP (for Windows) and SSH (for Linux) equally, and provide links to relevant documentation for both operating systems.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/tutorial-create-host-portal.md
...b/main/articles/bastion/tutorial-create-host-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally maintains parity between Windows and Linux, but in the prerequisites section, the link to the Windows VM quickstart is listed before the Linux VM quickstart. This subtle ordering preference is a form of 'windows_first' bias. However, both platforms are otherwise mentioned equally, and connection instructions reference both RDP (Windows) and SSH (Linux) without favoring one. There are no PowerShell-heavy examples, Windows-only tools, or missing Linux examples.
Recommendations
- List Linux and Windows VM quickstart links in alphabetical order or randomize their order to avoid implicit prioritization.
- Wherever possible, ensure that examples and instructions mention both Windows and Linux platforms in parallel, or use neutral phrasing.
- Periodically review documentation for subtle ordering or phrasing that may suggest platform preference, even if both are supported.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/tutorial-create-host-portal.md
...b/main/articles/bastion/tutorial-create-host-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux VM quickstart links and mentions both RDP (Windows) and SSH (Linux) ports, but in the prerequisites, the Windows VM creation link is listed before the Linux VM link. There are no command-line (PowerShell or Bash) examples at all, and no Windows-specific tools or patterns are emphasized. The overall structure is neutral, but the ordering of Windows before Linux in the prerequisites is a subtle 'windows_first' bias.
Recommendations
- List Linux and Windows VM creation links in alternating order across documentation, or list Linux first in some instances to balance exposure.
- Explicitly state that the steps apply equally to both Windows and Linux VMs where relevant.
- If providing future examples or screenshots, ensure parity by including both Windows and Linux scenarios.
- Consider adding a note or section clarifying that Bastion supports both SSH (Linux) and RDP (Windows) equally, with links to connection guides for both.