Azure Netapp Files

459
Total Pages
366
Linux-Friendly Pages
93
Pages with Bias
20.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

228 issues found
Showing 26-50 of 228 flagged pages
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-customer-managed-keys.md .../azure-netapp-files/configure-customer-managed-keys.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently presenting Azure Portal (GUI) and Azure PowerShell instructions before Azure CLI examples. PowerShell is a Windows-centric tool, and its inclusion as a primary method, alongside the absence of explicit Linux shell examples (e.g., Bash), reinforces this bias. There are no Linux-specific command-line examples or troubleshooting steps, and the documentation does not mention or address Linux environments or tools directly. The use of screenshots and instructions is focused on the Azure Portal, which is OS-agnostic but often associated with Windows workflows. No mention is made of Linux-native scripting, automation, or integration patterns.
Recommendations
  • Present Azure CLI (which is cross-platform and preferred on Linux) examples before PowerShell examples, or at least give them equal prominence.
  • Explicitly mention that Azure CLI commands are suitable for Linux, macOS, and Windows, and provide Bash-specific usage notes where relevant.
  • Add troubleshooting and scripting examples that use Bash shell idioms (e.g., environment variables, piping, jq for JSON parsing) to illustrate Linux-native workflows.
  • Where PowerShell is shown, provide equivalent Bash scripts or shell commands for common automation scenarios.
  • Clarify in the introduction or requirements that all command-line instructions are cross-platform unless otherwise noted, and highlight any OS-specific caveats.
  • Include references or links to Linux-specific Azure CLI installation and usage guides.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-kerberos-encryption.md ...es/azure-netapp-files/configure-kerberos-encryption.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by relying heavily on PowerShell commands (e.g., Set-ADComputer) and referencing Windows-specific tools (RSAT) for critical Active Directory configuration steps. There are no equivalent Linux-based instructions for managing the required AD computer account properties, and the documentation assumes access to a Windows environment for these steps. Linux client configuration is covered only for NFS mounting, not for the AD/kerberos setup, and Windows tools are mentioned before any Linux alternatives (which are not provided).
Recommendations
  • Provide equivalent instructions for configuring the Kerberos encryption type on the AD computer account using Linux-based tools such as 'ldapmodify', 'adcli', or 'samba-tool'.
  • Include Linux command-line examples for all steps currently shown only with PowerShell, especially for environments where administrators do not have access to Windows servers or RSAT.
  • Clearly indicate when a step requires a Windows environment, and suggest alternatives for Linux-only environments.
  • Reorganize sections so that Linux and Windows methods are presented in parallel, or prioritize Linux instructions when the primary client is Linux.
  • Add troubleshooting tips for common Linux-side Kerberos/AD integration issues.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-ldap-over-tls.md ...articles/azure-netapp-files/configure-ldap-over-tls.md
High Priority View Details →
Scanned: 2025-12-29 18:00
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 exclusively referencing Windows Server tools (Certification Authority, MMC snap-in) for certificate generation and management, and does not provide equivalent instructions or examples for Linux environments. All certificate export steps are described using Windows interfaces and screenshots, with no mention of Linux alternatives or cross-platform command-line methods.
Recommendations
  • Add instructions for generating and exporting root CA certificates using common Linux tools (e.g., OpenSSL) alongside the Windows Server method.
  • Include Linux command-line examples for certificate management and export, such as using openssl to create and export certificates in Base-64 encoded X.509 (.CER) format.
  • Provide guidance on viewing and managing certificates on Linux systems, such as using keytool, openssl, or other relevant utilities.
  • Add screenshots or terminal output examples for Linux workflows to match the visual aids provided for Windows.
  • Explicitly state that both Windows and Linux domain controllers are supported, if applicable, and clarify any platform-specific requirements.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-ldap-extended-groups.md ...s/azure-netapp-files/configure-ldap-extended-groups.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows/Active Directory bias by exclusively supporting and referencing Microsoft Active Directory Domain Services (AD DS) and Microsoft Entra Domain Services for LDAP integration, with explicit statements that OpenLDAP or other third-party LDAP directory services are not supported. All attribute management examples and screenshots use Windows tools (Active Directory Users and Computers MMC snap-in, Multi-valued String Editor, Attribute Editor). Guidance for setting LDAP attributes is Windows-centric, and Linux tools or workflows for managing POSIX attributes in LDAP are not mentioned. Linux/NFS client configuration is referenced only briefly and always after the Windows/AD configuration steps.
Recommendations
  • Clarify in the introduction and considerations sections why only AD DS and Microsoft Entra Domain Services are supported, and if possible, provide a roadmap or alternatives for Linux/OpenLDAP environments.
  • Add Linux/OpenLDAP examples for managing POSIX attributes (e.g., using ldapmodify, phpldapadmin, or command-line tools) even if not supported, to help users understand the differences.
  • Where screenshots show Windows tools (e.g., Attribute Editor), provide equivalent command-line or Linux-based examples for attribute management, or explicitly state that only Windows tools are supported.
  • In the steps section, provide more parity by including Linux client configuration steps earlier, and clarify any limitations or differences for Linux-based LDAP servers.
  • If possible, add troubleshooting tips for common Linux client issues when integrating with AD DS LDAP, and reference relevant Linux documentation.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-network-features.md ...icles/azure-netapp-files/configure-network-features.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell/Azure PowerShell commands are presented first and in detail for feature registration and volume management, with Azure CLI and REST API alternatives provided but not prioritized. The initial registration steps and many code blocks default to PowerShell, and there is a strong focus on Azure Portal workflows, which are more familiar to Windows users. Linux-specific shell or scripting examples are absent, and there is little mention of Linux-native tools or workflows. The documentation does include Azure CLI and REST API examples, which are cross-platform, but PowerShell is consistently emphasized and appears before CLI in several sections.
Recommendations
  • Present Azure CLI examples before PowerShell examples, or at least in parallel, to avoid the impression that PowerShell is the primary or preferred method.
  • Explicitly mention that Azure CLI commands can be run natively on Linux, macOS, and Windows, and provide bash shell examples where appropriate.
  • Include Linux shell (bash) scripting examples for automation scenarios, especially for registration and volume management tasks.
  • Clarify that all REST API and Azure CLI instructions are fully cross-platform.
  • Where PowerShell is used, provide equivalent bash or shell script snippets for Linux users.
  • Add a short section or note highlighting Linux and macOS support for Azure CLI and REST API, and link to relevant installation guides.
  • Ensure that screenshots and UI instructions do not assume a Windows environment (e.g., avoid referencing Windows-specific UI elements or terminology).
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/control-plane-security.md .../articles/azure-netapp-files/control-plane-security.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Windows-centric tools as primary interfaces for managing Azure NetApp Files. While it mentions 'CLI' generically, PowerShell is the only command-line interface explicitly named, and there are no Linux-specific tools, shell examples, or references to Bash/Azure CLI usage. The order of interface mention (APIs, PowerShell, CLI, Portal) also places PowerShell before CLI, reinforcing a Windows-first perspective. No Linux or cross-platform command-line examples or tools are provided.
Recommendations
  • Explicitly mention Azure CLI (az) as a cross-platform tool alongside PowerShell when listing management interfaces.
  • Provide Linux/Bash shell examples for common tasks, or at least reference that Azure CLI can be used from Linux/macOS.
  • When listing interfaces, alternate or rotate the order (e.g., 'APIs, Azure CLI, PowerShell, or the Azure portal') to avoid implicit prioritization of Windows tools.
  • Add a section or callout highlighting cross-platform management options, including Azure CLI and REST API usage from Linux/macOS.
  • Where scripting or automation is discussed, provide both PowerShell and Bash/Azure CLI script snippets or links to equivalent documentation.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/create-short-term-clone.md ...articles/azure-netapp-files/create-short-term-clone.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell commands for feature registration and status checking, mentioning Azure CLI as an alternative only after the PowerShell examples. There are no explicit Linux shell (bash) or cross-platform CLI examples, and the initial instructions focus on PowerShell, which is more common on Windows systems.
Recommendations
  • Provide Azure CLI (az) command examples alongside or before PowerShell examples for all feature registration and status checking steps.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux, macOS, and Windows users.
  • Where possible, include bash shell script examples for automation scenarios.
  • Review the order of tool presentation to avoid always listing Windows-centric tools first.
  • Add a note clarifying that all operations can be performed from Linux or macOS using Azure CLI.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/create-volumes-dual-protocol.md ...les/azure-netapp-files/create-volumes-dual-protocol.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by exclusively describing the management of LDAP POSIX attributes using Windows tools (Active Directory Users and Computers MMC snap-in) and providing step-by-step instructions only for Windows systems. There are no equivalent instructions or examples for managing POSIX attributes or configuring LDAP from Linux systems. Additionally, Windows terminology and tools are mentioned first and in detail, while Linux alternatives are only referenced via links or omitted.
Recommendations
  • Provide equivalent instructions for managing LDAP POSIX attributes using common Linux tools (e.g., ldapmodify, phpldapadmin, or command-line utilities).
  • Include Linux-based examples for accessing and editing LDAP attributes, such as using ldapsearch and ldapmodify.
  • When describing attribute management, present both Windows and Linux approaches side-by-side or in parallel sections.
  • Avoid assuming the administrator is using a Windows environment; clarify that either platform can be used and provide guidance for both.
  • Where Windows-specific features or limitations are described, add notes about Linux equivalents or differences.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/cross-region-replication-create-peering.md ...etapp-files/cross-region-replication-create-peering.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing Azure PowerShell commands as the primary example for feature registration and status checking, mentioning Azure CLI only as an alternative. There are no explicit Linux shell or bash examples, and PowerShell is presented first and in detail. The rest of the guide relies heavily on Azure Portal UI steps, which are platform-agnostic, but the only command-line examples are PowerShell-centric.
Recommendations
  • Provide Azure CLI (bash) examples alongside PowerShell for all command-line steps, especially for feature registration and status checking.
  • Present Azure CLI and PowerShell examples in parallel or in tabs, rather than listing PowerShell first and CLI as an afterthought.
  • Explicitly mention that both PowerShell and CLI are supported, and provide guidance for users on Linux/macOS.
  • Where possible, add bash shell equivalents for any scripting or automation steps.
  • Review future documentation to ensure parity between Windows and Linux tooling and examples.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/cross-zone-region-replication-configure.md ...etapp-files/cross-zone-region-replication-configure.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only Azure PowerShell examples for feature registration, which is Windows-centric. Although it briefly mentions Azure CLI as an alternative, no CLI commands are shown. There are no Linux-specific instructions or examples, and the PowerShell approach is presented first and in detail.
Recommendations
  • Add explicit Azure CLI command examples for feature registration and status checking, alongside PowerShell.
  • Present Azure CLI examples before or alongside PowerShell to avoid Windows-first bias.
  • Clarify that all steps can be performed from Linux/macOS using Azure CLI or Cloud Shell.
  • Where screenshots or UI instructions are given, note any OS-specific differences or confirm cross-platform parity.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/default-individual-user-group-quotas-introduction.md ...s/default-individual-user-group-quotas-introduction.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. In the 'Observing user quota settings and consumption' section, Windows client instructions and screenshots are presented before Linux client instructions. Windows-specific tools (Windows Explorer, dir command) are mentioned explicitly, while only the quota(1) command is referenced for Linux. There is no mention of Linux graphical file managers or alternative CLI tools. The 'Next steps' section includes a link to Windows Security Identifiers documentation but does not provide a Linux equivalent (such as a link to information about UNIX UIDs/GIDs).
Recommendations
  • Present Linux and Windows client instructions in parallel or alternate the order to avoid Windows-first bias.
  • Include examples of observing quotas using popular Linux graphical file managers (e.g., Nautilus, Dolphin) if supported.
  • Expand Linux CLI instructions to mention alternative commands (e.g., df, ls) where relevant.
  • In the 'Next steps' section, add links to documentation about UNIX user and group IDs to match the Windows SID reference.
  • Clarify protocol-specific instructions (e.g., SMB for Windows, NFS for Linux) to ensure parity in guidance.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/dual-protocol-permission-behaviors.md ...ure-netapp-files/dual-protocol-permission-behaviors.md
High Priority View Details →
Scanned: 2025-12-29 18:00
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 consistently referencing Windows/NTFS concepts and tools before their Linux/NFS equivalents, providing more detail for Windows-specific behaviors, and omitting concrete Linux/NFS command examples for permission management. Windows terminology (NTFS, SID, Windows RPC, Active Directory) is used more prominently, while Linux/NFS management is described as CLI-only and less accessible. There are no step-by-step Linux examples or tool recommendations, and Windows management is presented as the default or primary use case.
Recommendations
  • Provide parallel Linux/NFS examples for permission management, such as step-by-step usage of nfs4_getfacl/nfs4_setfacl, chown, chmod, and relevant NFS client tools.
  • Balance the order of presentation so that Linux/NFS concepts and tools are described before or alongside Windows/NTFS equivalents, rather than after.
  • Include screenshots or GUI management options for Linux/NFS where possible, or clarify the limitations and suggest alternative workflows.
  • Explicitly mention Linux identity sources (such as LDAP, NIS, or local passwd/group files) and how they interact with Azure NetApp Files.
  • Add troubleshooting sections for common Linux/NFS permission issues, similar to the detail provided for Windows/NTFS scenarios.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/disable-showmount.md .../main/articles/azure-netapp-files/disable-showmount.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page primarily uses Azure PowerShell commands for feature registration and management, which are most commonly used on Windows. While it briefly mentions Azure CLI as an alternative, no explicit CLI examples are provided, and there are no Linux-specific instructions or examples. The documentation assumes familiarity with PowerShell and does not address Linux shell usage or provide parity for Linux administrators.
Recommendations
  • Provide explicit Azure CLI command examples alongside PowerShell commands, especially for feature registration and status checks.
  • Include instructions or notes for running these commands from a Linux shell or macOS terminal.
  • Clarify that both PowerShell and Azure CLI are cross-platform, and link to installation guides for Linux users.
  • Consider reordering examples so that CLI commands (which are more platform-neutral) are presented before PowerShell commands.
  • Add a section or note addressing Linux administrators, ensuring they understand how to perform these actions without relying on Windows tools.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-application-resilience.md ...icles/azure-netapp-files/faq-application-resilience.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. SMB/Windows-centric scenarios are described in greater detail, with explicit mention of Windows-only features (e.g., SMB Continuous Availability, Transparent Failover) and Windows workloads (Citrix, FSLogix, MS SQL Server). Linux equivalents are either omitted, referenced only in passing, or not provided with comparable detail. For example, SQL Server on Linux is explicitly excluded from SMB CA support, and Boomi recommendations specify Windows for SMB and Linux for NFS, but only Windows SMB mounting is linked in 'Next steps'. There are no PowerShell-heavy examples, but Windows tools and patterns are mentioned before or instead of Linux ones in several places.
Recommendations
  • Provide equivalent Linux examples and guidance for SMB scenarios, including any supported Linux SMB workloads and configuration steps.
  • Clarify whether features like SMB Continuous Availability or Transparent Failover are available or planned for Linux clients, and document any limitations.
  • Add links and references to Linux mounting guides for SMB volumes, not just NFS.
  • Where Windows tools or patterns are mentioned, ensure Linux alternatives are described with equal prominence and detail.
  • Explicitly state support boundaries for both Windows and Linux in all relevant sections, avoiding Windows-first phrasing.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/includes/smb-continuous-availability.md ...e-netapp-files/includes/smb-continuous-availability.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by focusing exclusively on Windows-based workloads (Citrix, FSLogix, MSIX, SQL Server on Windows) and explicitly stating that Linux SQL Server is not supported. All examples and guidance reference Windows tools and patterns (Active Directory, Windows security privileges), with no Linux equivalents or alternatives provided.
Recommendations
  • Clearly state the lack of Linux support at the beginning to set expectations.
  • If possible, provide information on roadmap or alternatives for Linux users.
  • Include examples or guidance for Linux environments if/when support becomes available.
  • Reference cross-platform tools or clarify which features are Windows-only to avoid confusion.
  • Consider mentioning any workarounds or related features for Linux users, if applicable.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/enable-continuous-availability-existing-SMB.md ...p-files/enable-continuous-availability-existing-SMB.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides instructions and verification steps for Windows environments, using PowerShell commands and referencing Windows system behaviors (e.g., rebooting Windows systems). There are no examples or guidance for Linux or macOS clients, nor are equivalent tools or commands mentioned for non-Windows platforms.
Recommendations
  • Include instructions for verifying SMB Continuous Availability from Linux clients, such as using 'smbstatus' or appropriate SMB client tools.
  • Clarify whether Linux and macOS clients are supported for SMB CA and, if so, provide relevant steps or caveats.
  • Present both Windows and Linux/macOS examples side-by-side where possible, or at least mention Linux/macOS considerations.
  • Avoid assuming all users are on Windows; use more neutral language (e.g., 'client systems' instead of 'Windows systems') and provide parity in troubleshooting and verification steps.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-data-migration-protection.md ...es/azure-netapp-files/faq-data-migration-protection.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. While it mentions both Linux (rsync for NFS) and Windows (robocopy for SMB) tools, the Windows tool (robocopy) is referenced with a direct Microsoft Docs link, and there are no Linux command-line examples or explicit parity in tool explanations. There are no PowerShell-heavy sections, but Windows tools are slightly more emphasized, and Linux examples are minimal or absent.
Recommendations
  • Provide explicit Linux command-line examples for NFS and SMB migrations, such as sample rsync and smbclient commands.
  • Include links to Linux tool documentation (e.g., rsync, smbclient, cifs-utils) similar to the robocopy link for Windows.
  • When listing migration tools, present Linux and Windows options together and with equal detail, rather than referencing Windows tools more prominently.
  • Add a table or section comparing common Linux and Windows migration tools and their usage scenarios.
  • Ensure that for every Windows-specific tool or example, a Linux equivalent is also provided.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-smb.md ...-docs/blob/main/articles/azure-netapp-files/faq-smb.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. Most examples, troubleshooting steps, and tool references are Windows-centric (e.g., MMC, Active Directory Users and Computers, Windows Server DFS Namespace). There is little to no mention of Linux clients, tools, or configuration patterns for SMB, nor are Linux-specific troubleshooting steps or examples provided. The documentation assumes a Windows environment for both administration and client access, and omits guidance for Linux or macOS users accessing SMB shares.
Recommendations
  • Add explicit examples for mounting and accessing Azure NetApp Files SMB shares from Linux clients (e.g., using smbclient, mount.cifs, or Nautilus).
  • Include troubleshooting steps and best practices for Linux SMB clients (such as handling permissions, file locking, and offline files).
  • Mention Linux equivalents for Windows tools (e.g., alternatives to MMC for managing shares, or using smbstatus/smbcontrol for sessions and open files).
  • Clarify support and limitations for non-Windows SMB clients, including any differences in feature support (e.g., DFS-N, Alternate Data Streams, oplocks).
  • Provide parity in configuration and management instructions for both Windows and Linux environments, ensuring Linux administrators can follow along without relying on Windows-only tools.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/generate-user-group-quota-reports.md ...zure-netapp-files/generate-user-group-quota-reports.md
High Priority View Details →
Scanned: 2025-12-29 18:00
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 providing Azure PowerShell examples for feature registration and status checking, mentioning PowerShell commands before Azure CLI alternatives, and omitting direct Linux shell or CLI examples. The registration steps are described primarily using PowerShell, which is native to Windows, while Linux users are only briefly referenced via a link to Azure CLI documentation, without explicit command examples. No Linux-specific tools or patterns are discussed, and the workflow assumes familiarity with Windows-centric tooling.
Recommendations
  • Provide explicit Azure CLI command examples alongside PowerShell for feature registration and status checking, formatted for bash/shell environments.
  • Mention Azure CLI as an equal alternative to PowerShell, not just as a secondary option.
  • Include notes or examples for Linux/macOS users, clarifying how to perform the same steps in their environments.
  • Ensure screenshots and UI instructions do not assume a Windows environment unless necessary.
  • Add a section or callout for cross-platform usage, highlighting any differences or considerations for Linux users.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/includes/netlogon-april-2023.md ...les/azure-netapp-files/includes/netlogon-april-2023.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page focuses exclusively on the Windows platform, referencing the April 2023 Windows Update and Netlogon Secure Channel changes without mentioning Linux or cross-platform considerations. No Linux tools, commands, or equivalent guidance are provided, and the only example or context is Windows-specific.
Recommendations
  • Add information about how the Netlogon Secure Channel changes may (or may not) impact Linux-based clients or Samba implementations.
  • Include Linux-specific troubleshooting steps or guidance for administrators managing Azure NetApp Files with Linux systems.
  • Provide parity in examples by referencing both Windows and Linux tools/utilities where applicable.
  • Clarify if the update is only relevant to Windows environments, and explicitly state the impact (or lack thereof) on Linux environments.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/lightweight-directory-access-protocol-schemas.md ...files/lightweight-directory-access-protocol-schemas.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All examples, attribute descriptions, and configuration instructions are centered around Microsoft Active Directory and Windows-specific tools (such as ADSI Edit). There are no examples or guidance for configuring equivalent LDAP schema or attribute indexing in common Linux-based LDAP servers (e.g., OpenLDAP). The documentation assumes the use of Windows environments and does not address Linux LDAP administration tools or patterns.
Recommendations
  • Add parallel examples and instructions for configuring LDAP schemas and attribute indexing in Linux-based LDAP servers such as OpenLDAP.
  • Mention and document Linux tools (e.g., ldapmodify, slapd-config, phpldapadmin) for schema and attribute management alongside Windows tools.
  • Reorder sections or provide dual-path guidance so that Linux/OpenLDAP equivalents are presented alongside or before Windows/Active Directory instructions.
  • Clarify that Azure NetApp Files supports integration with non-Active Directory LDAP servers and provide references or links to relevant Linux LDAP documentation.
  • Include screenshots or command-line examples for Linux-based LDAP administration tasks where Windows screenshots are currently shown.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/lightweight-directory-access-protocol.md ...-netapp-files/lightweight-directory-access-protocol.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
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 prioritizing Microsoft Active Directory as the primary LDAP server, referencing Windows-specific tools (e.g., nslookup with Windows syntax), and providing examples and configuration details mainly for Windows environments. Linux alternatives (such as FreeIPA, OpenLDAP, Red Hat Directory Server) are mentioned only in a note and not elaborated upon. Linux tools (e.g., dig) are referenced but not exemplified, and there are no Linux-specific configuration or troubleshooting examples.
Recommendations
  • Provide equal coverage and examples for Linux LDAP servers (FreeIPA, OpenLDAP, Red Hat Directory Server), including configuration and troubleshooting steps.
  • Include Linux command-line examples (e.g., dig, ldapsearch) alongside Windows nslookup examples, with sample outputs.
  • Clarify support and configuration differences for Linux-based LDAP servers in Azure NetApp Files, not just AD DS.
  • Reorganize sections to present both Windows and Linux options together, rather than focusing on Windows first.
  • Add guidance for extending LDAP schemas and managing UNIX attributes in Linux environments.
  • Ensure that all features and limitations are described for both Windows and Linux LDAP server types.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-cool-access.md ...main/articles/azure-netapp-files/manage-cool-access.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell commands are presented as the primary method for feature registration, with Azure CLI commands mentioned only as an alternative and without explicit examples. The step-by-step instructions and screenshots focus on GUI actions typical of Windows environments (e.g., right-clicking), with no mention of Linux-specific workflows or command-line alternatives for Linux users. There are no examples or guidance for managing cool access using Linux shell commands or automation tools, and the documentation does not address Linux-specific considerations or parity.
Recommendations
  • Provide explicit Azure CLI command examples alongside PowerShell for all registration and management steps, including full syntax and sample output.
  • Include Linux shell (bash) equivalents for relevant operations, such as using az CLI in bash scripts.
  • Add screenshots or instructions for managing cool access using the Azure Portal in Linux environments (if applicable), or clarify that the GUI steps are cross-platform.
  • Mention and document any differences or considerations for Linux users, such as file system compatibility, automation, or scripting.
  • Ensure that all code blocks and examples are presented in both PowerShell and bash/CLI formats, with tabs or toggles for user selection.
  • Review and update terminology to avoid Windows-centric language (e.g., 'right-click') and provide alternative instructions for keyboard or command-line navigation.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-smb-share-access-control-lists.md ...-netapp-files/manage-smb-share-access-control-lists.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation exclusively describes Windows-based methods (Windows Explorer, Microsoft Management Console) for managing SMB share ACLs in Azure NetApp Files. There are no Linux or cross-platform examples, and all tools and workflows mentioned are Windows-specific. The documentation does not mention or provide alternatives for Linux users, nor does it clarify if such operations are possible from non-Windows systems.
Recommendations
  • Add information about whether SMB share ACLs can be viewed or managed from Linux clients, and if not, state this explicitly.
  • If possible, provide Linux-based methods (e.g., using smbclient, setfacl, or other Samba tools) for viewing or managing SMB share ACLs.
  • Include command-line examples (e.g., PowerShell and Bash/smbclient) for parity.
  • Clarify any platform limitations in a dedicated section so Linux administrators understand their options.
  • Consider referencing cross-platform tools or APIs (such as REST, if available) for managing SMB share ACLs.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/migrate-volumes.md ...ob/main/articles/azure-netapp-files/migrate-volumes.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing a PowerShell sample script for the migration assistant workflow and using Azure PowerShell commands as the primary example for feature registration, with Azure CLI only mentioned as an alternative. There are no explicit Linux shell or Bash examples, and the PowerShell workflow is referenced before any cross-platform alternatives. This may disadvantage Linux users or those who prefer Bash/CLI tools.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts alongside PowerShell examples for all steps, especially for migration assistant workflows.
  • When referencing sample scripts, include both PowerShell and Bash/CLI versions, or clarify cross-platform compatibility.
  • List Azure CLI commands before or alongside PowerShell commands to avoid implying Windows-first workflows.
  • Explicitly mention that all REST API steps can be performed from any OS, and provide Bash/cURL examples for REST API calls.
  • Add a section or callout for Linux/macOS users, highlighting any platform-specific considerations or tools.
GitHub Create Pull Request
← Previous Page 2 of 10 Next →