Bastion
82
Total Pages
52
Linux-Friendly Pages
30
Pages with Bias
36.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
76 issues found
Showing 51-75 of 76 flagged pages
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-vm-copy-paste.md
...cs/blob/main/articles/bastion/bastion-vm-copy-paste.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exclusively describes copy and paste functionality for Windows virtual machines, with no mention of Linux VMs or their specific requirements, behaviors, or examples. All instructions, prerequisites, and examples are focused on Windows, omitting Linux parity.
Recommendations
- Add a section for Linux VMs, detailing any differences in copy/paste behavior, prerequisites, and supported scenarios.
- Include Linux-specific examples and screenshots, such as using the clipboard in common Linux desktop environments (e.g., GNOME, KDE) when accessed via Bastion.
- Clarify whether the described Bastion clipboard features work identically for Linux VMs, and note any limitations or additional configuration steps required.
- If there are differences in keyboard shortcuts or clipboard integration for Linux, document them explicitly.
Create Pull Request
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-host-arm-template.md
.../main/articles/bastion/quickstart-host-arm-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where only Windows virtual machine creation and RDP connection guides are linked. There are no examples or guidance for Linux VM deployment or SSH connections via Bastion, and no Linux-specific instructions or parity in the workflow.
Recommendations
- Add links to Linux VM quickstart guides in the 'Next steps' section, such as 'Quickstart: Create a Linux virtual machine in the Azure portal'.
- Include a link or section for connecting to a Linux VM using Azure Bastion (SSH), e.g., 'Connect to a Linux VM using Azure Bastion'.
- Ensure that examples and guidance are provided for both Windows and Linux scenarios throughout the documentation, not just in supplementary links.
- Review the documentation for any implicit assumptions of a Windows environment and clarify that Bastion supports both Windows (RDP) and Linux (SSH) connections.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/native-client.md
...azure-docs/blob/main/articles/bastion/native-client.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias in its examples and connection instructions. Windows native client scenarios are listed before Linux equivalents in both the connection table and the 'Next steps' section. There is a lack of explicit Linux configuration or example screenshots, and Linux instructions are less prominent or detailed compared to Windows. The page also references Windows-specific tools (RDP) before their Linux counterparts (SSH), and links for Windows are presented before Linux.
Recommendations
- Present Linux and Windows examples in parallel, or alternate which platform is listed first in tables and instructions.
- Include Linux-specific screenshots and configuration steps where Windows screenshots are shown.
- Ensure 'Next steps' links for Linux are given equal prominence and order as Windows links.
- Provide explicit examples for connecting from Linux native clients, including command-line usage and any GUI tools commonly used on Linux.
- Mention and document Linux-specific considerations, such as SSH key management and file transfer tools, with equal detail as Windows RDP scenarios.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/session-monitoring.md
...-docs/blob/main/articles/bastion/session-monitoring.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation focuses exclusively on using the Azure Portal GUI for session monitoring and management, without providing any command-line examples. There is an implicit Windows bias as the Azure Portal is often associated with Windows-centric workflows, and there are no references to Linux tools, CLI commands, or cross-platform automation (e.g., Azure CLI, Bash, or PowerShell). No Linux-specific guidance or parity is offered.
Recommendations
- Add Azure CLI and/or PowerShell command examples for session monitoring and management to support automation and cross-platform usage.
- Explicitly mention that the Azure Portal is web-based and accessible from any OS, including Linux and macOS.
- Provide examples or references for managing Bastion sessions via REST API or scripting, with sample commands for both Bash (Linux/macOS) and PowerShell (Windows).
- Include notes or links to Linux-friendly tools and workflows where applicable.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/troubleshoot.md
.../azure-docs/blob/main/articles/bastion/troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation displays a mild Windows bias by prioritizing Windows-specific troubleshooting scenarios (such as domain-joined VM sign-in) and referencing Windows authentication patterns. However, it does provide a Linux/SSH example for key generation and does not exclusively use Windows tools or PowerShell. There is a lack of parity in addressing Linux-specific troubleshooting scenarios, such as connecting to Linux VMs with Azure Bastion or handling Linux authentication issues.
Recommendations
- Add troubleshooting examples and Q&A for common Linux VM connectivity issues, such as SSH authentication failures, username formats, and file transfer specifics for Linux.
- Include Linux domain-joined or Microsoft Entra joined VM scenarios if supported, or explicitly state limitations.
- When discussing domain-joined VM sign-in, provide parity by mentioning Linux VM authentication methods and any differences in Azure Bastion behavior.
- Ensure that any references to tools or patterns (such as RDP or username formats) are balanced with Linux equivalents (e.g., SSH, Linux username formats).
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The Azure Bastion FAQ documentation displays a mild Windows bias in several areas. Browser recommendations mention Windows first and provide more detail for Windows users. Keyboard layout configuration instructions are only given for Windows, with no guidance for Linux or macOS users. There are references to Windows-specific tools and settings (e.g., Windows key, Windows toolbar, Windows Settings), and some examples (such as keyboard focus) are described using Windows terminology. There are no explicit Linux/macOS examples or instructions for equivalent actions.
Recommendations
- Provide keyboard layout configuration steps for Linux and macOS, or link to relevant documentation.
- When describing browser support, list platforms in a neutral order and clarify support for Linux browsers if applicable.
- For instructions involving keyboard shortcuts or focus, include equivalents for macOS and Linux where possible.
- Avoid using Windows-specific terminology (e.g., 'Windows key') without also referencing macOS/Linux equivalents, or clarify if the action is Windows-only.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows minor Windows bias in a few sections. For example, browser recommendations mention Windows first and provide more detail for Windows users. The keyboard layout and configuration instructions are exclusively for Windows, with no mention of how to set keyboard layouts on Linux or macOS. There are no explicit Linux/macOS examples or instructions in these areas, which may cause friction for non-Windows users.
Recommendations
- In the browser support section, clarify that Chrome and Edge Chromium are supported on Linux as well, if applicable.
- In the keyboard layout section, add instructions or references for setting keyboard layouts on Linux and macOS.
- Wherever native client or file transfer is discussed, explicitly mention support for Linux/macOS clients and provide links or examples if there are platform-specific steps.
- Review the FAQ for other areas where Windows instructions are given and add parity for Linux/macOS where relevant.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The Azure Bastion FAQ documentation demonstrates minor Windows bias in several areas. Browser recommendations mention Windows first and provide more detail for Windows users. Instructions for setting keyboard layouts are Windows-specific, with no guidance for Linux or macOS users. There are no Linux/macOS-specific examples or instructions for tasks such as keyboard configuration or file transfer, despite Azure Bastion supporting SSH (commonly used on Linux/macOS).
Recommendations
- Add instructions for setting keyboard layouts on Linux and macOS systems alongside the Windows guidance.
- When listing supported browsers, avoid listing Windows first and provide parity in recommendations for Linux/macOS browsers.
- Include examples or notes for file transfer using SSH clients on Linux/macOS, as well as RDP clients available for those platforms.
- Where native client usage is mentioned, clarify supported clients for Linux/macOS and provide links to relevant documentation.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The Azure Bastion FAQ documentation shows minor Windows bias in several areas. In browser support, Windows browsers are mentioned first and more options are listed for Windows than Mac. Keyboard layout instructions are only provided for Windows, with no guidance for Linux or macOS users. Some sections reference Windows-specific tools or patterns (e.g., Windows key, Windows toolbar) without Linux/macOS equivalents. There are no explicit Linux/macOS examples for tasks like keyboard layout configuration or file transfer.
Recommendations
- In the browser support section, list supported browsers for all platforms equally and avoid mentioning Windows first unless there is a technical reason.
- For keyboard layout configuration, provide instructions for Linux and macOS users in addition to Windows.
- When referencing keyboard shortcuts or OS-specific actions (e.g., 'Click the Windows key'), include equivalents for Linux (e.g., Super key) and macOS (e.g., Command key) where applicable.
- For file transfer and native client usage, clarify support and provide examples for Linux/macOS clients (e.g., using SSH/SCP from a Mac or Linux terminal).
- Review the documentation for other subtle Windows-centric language and add Linux/macOS parity where possible.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows minor Windows bias, particularly in sections discussing browser support and keyboard layout configuration. Windows tools and workflows are mentioned first or exclusively, such as instructions for setting keyboard layouts, while Linux/macOS equivalents are omitted. There are no PowerShell-heavy sections or exclusive use of Windows tools, but Linux/macOS users may need to infer their own steps.
Recommendations
- Add instructions for setting keyboard layouts on Linux and macOS systems alongside the Windows example.
- When listing browser support, mention Linux explicitly and provide guidance for supported browsers on Linux.
- Ensure examples and configuration steps are presented for all major platforms (Windows, Linux, macOS) where relevant.
- Avoid listing Windows tools or workflows first unless they are universally applicable; use neutral or platform-agnostic language where possible.
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, but in the prerequisites section, the Windows VM creation link is listed before the Linux VM creation link. Additionally, port requirements for Windows (RDP) are listed before Linux (SSH). However, there are no examples, instructions, or tools that are exclusive to Windows or PowerShell, and the tutorial is focused on Azure portal usage, which is cross-platform.
Recommendations
- List Linux VM creation links before or alongside Windows VM creation links to avoid implicit prioritization.
- List port requirements for Linux (SSH) before or alongside Windows (RDP).
- Explicitly state that all steps are applicable to both Windows and Linux VMs.
- Add clarifying notes or examples for Linux/macOS users where relevant, especially in connection steps.
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 referencing RDP and Windows-specific features (such as Kerberos authentication for domain-joined Windows VMs) before mentioning Linux/SSH scenarios. While Linux is referenced (e.g., SSH key storage, a link to Linux VM connection guidance), examples and detailed steps for Linux are less prominent and not presented side-by-side with Windows equivalents. There are no explicit Linux command-line or tool examples, and Windows-centric terminology (RDP, Kerberos) appears first in several sections.
Recommendations
- Present Windows and Linux scenarios in parallel, with equal detail and visibility.
- Include explicit Linux examples (e.g., SSH connection steps, Linux-specific NSG rules, Linux session management).
- Avoid listing Windows features or tools before Linux equivalents unless contextually necessary.
- Add links to Linux-focused documentation wherever Windows links are provided.
- Ensure that all features (such as session recording, privileged access) are described for both Windows and Linux use cases.
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 configuration method before mentioning Azure CLI, which is more commonly used on Linux/macOS. No explicit Linux/macOS examples or tools are provided, and the ordering of configuration options places Windows-centric tools first.
Recommendations
- Provide explicit Linux/macOS examples, such as using SSH or Azure CLI from a Linux terminal.
- Reorder configuration options to list cross-platform tools (Azure CLI) before Windows-specific ones (PowerShell).
- Include notes or links for Linux/macOS users on how to access and manage Azure Bastion resources.
- Clarify that Azure CLI is available on all platforms and provide sample commands for both Windows and Linux/macOS.
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 PowerShell is presented as a primary tab alongside CLI, which can indicate a Windows-first approach. No Linux/macOS-specific shell examples (e.g., bash, zsh) or explicit mention of platform differences are provided. However, the Azure CLI instructions are cross-platform, and no steps are strictly Windows-only.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and explicitly mention cross-platform compatibility.
- Consider listing Azure CLI instructions before PowerShell, as CLI is more widely used across platforms.
- Add a note or section for Linux/macOS users, confirming that all steps (including file creation and CLI usage) are compatible.
- If relevant, provide bash/zsh script snippets or mention how to run commands in Linux/macOS terminals.
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
Windows Tools
Summary
The documentation generally maintains parity between Windows and Linux, mentioning both VM types and required ports. However, there is a subtle Windows bias: Windows VM creation is listed before Linux, Windows-specific ports (3389) are mentioned first, and keyboard shortcut guidance is focused on Windows VMs (including mapping Windows shortcuts for Mac users). There are no Linux/macOS-specific connection tips or troubleshooting notes, and no explicit Linux desktop shortcut guidance.
Recommendations
- Alternate the order of Windows and Linux VM instructions/examples to avoid implicit prioritization.
- Provide Linux/macOS-specific connection tips, such as keyboard shortcuts or troubleshooting for remote desktop sessions.
- Include explicit examples/screenshots for connecting to Linux VMs, not just Windows.
- Mention Linux desktop environments and any differences in remote session experience.
- Ensure parity in troubleshooting and feature notes for both OS types.
Bastion
Quickstart: Deploy Azure Bastion automatically
...s/blob/main/articles/bastion/quickstart-host-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation shows minor Windows bias: Windows VM creation is listed before Linux VM creation in prerequisites, and Windows-specific keyboard shortcuts are explained in detail, including Mac-to-Windows mappings. There are no PowerShell-heavy sections or exclusive Windows tools, and Linux is mentioned where relevant (e.g., port 22 for Linux VMs). No critical steps are Windows-only, and Linux users can complete the quickstart without friction.
Recommendations
- List Linux VM creation before or alongside Windows VM creation to avoid implicit prioritization.
- Provide equivalent keyboard shortcut guidance for Linux VMs (e.g., SSH session tips, clipboard usage) if relevant.
- Ensure any tool or pattern mentioned for Windows has a Linux/macOS equivalent or note if not applicable.
- Explicitly state that all steps apply equally to Linux and macOS users, especially for portal-based actions.
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 in the prerequisites, but the Windows VM creation link is listed before the Linux equivalent. Otherwise, the tutorial is platform-neutral, focusing on Azure portal steps and not favoring Windows-specific tools or patterns.
Recommendations
- List Linux and Windows VM creation links in parallel or alternate their order to avoid implicit prioritization.
- Explicitly state that the Bastion connection steps apply equally to both Windows and Linux VMs.
- Where relevant, provide examples or screenshots for both Windows and Linux VM scenarios.
Bastion
Quickstart: Deploy Azure Bastion automatically
...s/blob/main/articles/bastion/quickstart-host-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates minor Windows bias by listing Windows VM creation before Linux VM creation in prerequisites, and by providing Windows-specific keyboard shortcut guidance before mentioning the Mac equivalent for connecting to Windows VMs. There is also a focus on Windows port (3389) before Linux port (22) in the required inbound ports section. However, Linux VM creation is referenced, and Linux connectivity is supported.
Recommendations
- List Linux VM creation before or alongside Windows VM creation in prerequisites.
- Present required inbound ports for Linux (22) before or alongside Windows (3389).
- Provide keyboard shortcut guidance for Linux and macOS clients connecting to Linux VMs, not just Windows clients connecting to Windows VMs.
- Ensure examples and instructions are equally detailed for both Windows and Linux scenarios.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias, primarily in sections describing browser support and keyboard layout configuration. Windows is mentioned first in browser recommendations, and detailed instructions for setting keyboard layouts are provided only for Windows workstations, with no equivalent guidance for Linux or macOS users. There are no explicit PowerShell-only examples or exclusive references to Windows tools, but Linux/macOS users may find it harder to follow certain steps due to missing platform-specific instructions.
Recommendations
- Provide equivalent instructions for configuring keyboard layouts on Linux and macOS systems.
- When listing supported browsers, mention Linux explicitly and clarify which browsers are supported on Linux.
- Ensure that any step-by-step guidance (such as changing keyboard layouts) includes cross-platform instructions.
- Review other sections for implicit Windows-first language and add Linux/macOS parity where relevant.
Bastion
Connect to a VM - specified private IP address: Azure portal
...-docs/blob/main/articles/bastion/connect-ip-address.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides connection instructions primarily through the Azure portal and Azure CLI, but does not include any OS-specific examples or guidance. However, the RDP protocol is mentioned before SSH, and there are no explicit Linux/macOS examples (such as SSH command-line usage or references to Linux desktop environments). The examples and screenshots are neutral, but the ordering and lack of Linux-specific context create a subtle Windows-first bias.
Recommendations
- Include explicit Linux/macOS connection instructions, such as SSH command-line examples for connecting via Bastion.
- Add notes or examples for using RDP clients on Linux/macOS, or alternatives like xfreerdp or Remmina.
- Provide screenshots or steps for Linux desktop environments where relevant.
- Ensure protocol examples (SSH, RDP) are presented in a balanced order or grouped by OS relevance.
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 instructions for verifying results, but PowerShell is presented as a primary tab alongside CLI, and PowerShell-specific commands are included. There are no explicit Linux/macOS shell examples (e.g., bash), nor is there mention of Linux-specific tooling or patterns. However, the Azure CLI instructions are cross-platform, and the Terraform workflow itself is platform-agnostic.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS and Windows, and consider showing bash shell examples explicitly.
- Add a note indicating that PowerShell is primarily a Windows tool, but is available cross-platform, and provide bash equivalents where relevant.
- If possible, add a 'bash' or 'Linux/macOS shell' tab alongside CLI and PowerShell to demonstrate parity.
- Ensure that any references to PowerShell do not imply it is required for Linux/macOS users.
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 Tools
Summary
The documentation generally maintains parity between Windows and Linux, mentioning both platforms in prerequisites and port requirements. However, there is a slight Windows bias: the Windows VM creation link is listed before Linux, and keyboard shortcut examples focus on Windows VMs (with only a brief mention of Mac clients connecting to Windows VMs). There are no Linux-specific connection or troubleshooting examples, and no mention of Linux desktop shortcut keys or behaviors.
Recommendations
- List Linux and Windows VM creation links in parallel or alternate their order to avoid implicit prioritization.
- Include examples or notes for connecting to Linux VMs, such as expected desktop behaviors, keyboard shortcuts, or troubleshooting tips.
- Add information about connecting from Linux/macOS clients, including any differences in experience or limitations.
- Provide parity in screenshots and instructions for both Windows and Linux VMs where relevant.
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. Windows-specific features (such as Kerberos authentication for domain-joined Windows VMs) are mentioned explicitly, while Linux-specific guidance is less prominent. References to RDP (Windows protocol) appear before SSH (Linux protocol) in several places, and the only explicit OS-specific example in the privileged access section is for Windows Kerberos authentication. Linux is mentioned in passing (e.g., SSH keys, a link to 'Connect to a Linux virtual machine using Azure Bastion'), but there are no detailed Linux-specific configuration examples or troubleshooting steps. No PowerShell or Windows-only tool usage is present, but the overall pattern favors Windows terminology and scenarios.
Recommendations
- Add explicit Linux/macOS configuration examples, such as SSH key management and troubleshooting for Linux VM connections.
- Provide parity in authentication guidance, e.g., mention Linux PAM or other Linux authentication enhancements if available.
- Ensure that RDP and SSH are referenced together or alternate which is listed first to avoid subtle prioritization.
- Include links to Linux/macOS documentation for session management, monitoring, and asset management where relevant.
- Add troubleshooting tips for common Linux connectivity issues (e.g., SSH agent forwarding, file permissions).
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 provides both Windows and Linux VM quickstart links in the prerequisites, but the Windows VM link is listed first. In the inbound ports section, Windows (RDP) is mentioned before Linux (SSH). No examples or instructions are exclusive to Windows, and Linux is referenced where relevant. There are no PowerShell-heavy sections, Windows-only tools, or missing Linux examples.
Recommendations
- List Windows and Linux VM quickstart links in parallel or alternate their order to avoid implicit prioritization.
- Mention inbound ports for Linux (SSH) before or alongside Windows (RDP) to ensure equal visibility.
- Continue ensuring that all instructions and examples are platform-neutral and reference both Windows and Linux where appropriate.
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only Azure Portal (GUI) instructions for deploying Bastion in private-only mode. There are no command-line examples, such as Azure CLI, PowerShell, or ARM templates. This omission results in a lack of parity for Linux users, who typically use Azure CLI or bash scripting, while Windows users might expect PowerShell examples. The absence of CLI examples is a subtle bias, as it does not address the needs of users on non-Windows platforms.
Recommendations
- Add step-by-step Azure CLI examples for all deployment steps, ensuring commands are compatible with bash and Linux environments.
- If PowerShell examples are added, ensure Azure CLI equivalents are provided and presented either first or side-by-side.
- Include ARM/Bicep template deployment instructions for automation across platforms.
- Explicitly mention that the Azure Portal steps are platform-agnostic, but provide links or sections for command-line alternatives.