Azure Netapp Files

252
Total Pages
149
Linux-Friendly Pages
103
Pages with Bias
40.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

896 issues found
Showing 376-400 of 896 flagged pages
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/snapshots-introduction.md .../articles/azure-netapp-files/snapshots-introduction.md
High Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. In the 'Ways to create snapshots' section, PowerShell is mentioned explicitly alongside Azure CLI, REST API, and Azure portal, but there is no mention of Linux-specific tools or shell scripting. The order of tool presentation (Azure portal, REST API, Azure CLI, PowerShell) places PowerShell before any mention of Linux scripting or command-line usage. There are no Linux/Unix shell examples or references to Linux-native tools, and scripting is only referenced generically. No explicit Linux or Unix command-line examples are provided, nor is there mention of Bash or shell scripting, which are common for Linux users.
Recommendations
  • Include explicit Linux/Bash shell examples for snapshot management, such as using Azure CLI commands in Bash.
  • Mention Linux scripting (e.g., Bash scripts) alongside PowerShell when discussing automation.
  • Clarify that Azure CLI is cross-platform and provide example commands in both Windows (PowerShell) and Linux (Bash) syntax.
  • When listing tools, alternate the order or explicitly state parity between PowerShell and Bash/shell scripting.
  • Add references or links to Linux-specific guidance or best practices for managing Azure NetApp Files snapshots.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-file-access-logs.md ...articles/azure-netapp-files/manage-file-access-logs.md
High Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias by providing detailed, step-by-step instructions and GUI walkthroughs for setting SACLs on SMB shares using Windows tools, while the Linux/NFS equivalent is referenced only via a link without in-page steps. PowerShell is used as the primary example for feature registration, with Azure CLI mentioned only secondarily. There are no Linux command-line examples or screenshots, and Windows administration tools are assumed as the default for certain tasks.
Recommendations
  • Provide step-by-step command-line instructions for setting Audit ACEs on NFSv4.1 shares from a Linux host, including example commands (e.g., using setfacl or nfs4_setfacl).
  • Include Linux/Unix screenshots or terminal output where appropriate, mirroring the Windows GUI walkthroughs.
  • Present Azure CLI commands before or alongside PowerShell examples for feature registration and management, ensuring parity.
  • Explicitly mention and demonstrate Linux tools and workflows for all relevant tasks, not just refer to external links.
  • Balance the prominence of Windows and Linux instructions, ensuring both are equally detailed and accessible.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/snapshots-introduction.md .../articles/azure-netapp-files/snapshots-introduction.md
High Priority View Details →
Scanned: 2025-08-18 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the 'Ways to create snapshots' section, where PowerShell is listed as a primary tool alongside Azure Portal, REST API, and Azure CLI, but there are no explicit Linux shell or Bash examples. PowerShell is mentioned before Linux-native scripting or command-line approaches, and there are no Linux/Unix-specific instructions or examples. The scripting example link provided points to a SQL Server T-SQL/PowerShell scenario, which is Windows-centric. There is also no mention of Linux automation patterns or tools (e.g., Bash, cron, shell scripts) for snapshot management.
Recommendations
  • Add explicit Bash or Linux shell command examples for creating and managing snapshots using Azure CLI.
  • Include references or links to Linux/Unix scripting patterns (e.g., using Bash scripts with az CLI) for automation.
  • Balance the order of tool mentions: list Azure CLI and REST API before PowerShell, or group them neutrally.
  • Provide example scripts for both Windows (PowerShell) and Linux (Bash) environments.
  • Reference Linux-native scheduling tools (e.g., cron jobs) for automating snapshot operations.
  • Ensure that all example links and code samples have Linux equivalents, not just Windows/PowerShell.
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-08-18 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. PowerShell commands are presented prominently and in detail, often before or alongside Azure CLI and REST API examples. PowerShell is a Windows-centric tool, and its usage is emphasized in feature registration and volume management steps. There are no explicit Linux shell or Bash examples outside of Azure CLI, and the documentation does not mention or provide guidance for Linux-native tools or workflows. The structure and ordering of examples (PowerShell, Azure CLI, REST API, Portal) also tend to prioritize Windows/PowerShell approaches.
Recommendations
  • Provide explicit Bash/Linux shell command examples where applicable, especially for Azure CLI usage.
  • Clarify that Azure CLI commands can be run natively on Linux, macOS, and Windows, and provide sample shell prompts (e.g., $ for Bash) to reinforce cross-platform applicability.
  • Where PowerShell is used, offer equivalent Bash or shell script snippets for Linux users, especially for common tasks like feature registration and status checking.
  • If certain steps are only possible in PowerShell, explicitly state this and offer alternative guidance for Linux users.
  • Review the ordering of example tabs/sections to avoid always listing PowerShell first; consider rotating or randomizing, or listing Azure CLI (which is cross-platform) before PowerShell.
  • Add a brief section or note at the top clarifying tool compatibility and platform support for all command-line examples.
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-08-18 00: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 examples for feature registration, referencing right-click actions in the portal UI (a pattern more familiar to Windows users), and omitting explicit Linux/Unix CLI or scripting examples. Although Azure CLI is mentioned, no concrete CLI command examples are provided, and there are no bash or shell script samples. This may make it less accessible for Linux administrators or those preferring cross-platform command-line tools.
Recommendations
  • Provide explicit Azure CLI command examples (e.g., 'az feature register ...') alongside PowerShell for all registration and status-check steps.
  • Include bash/shell script snippets where relevant, especially for automation scenarios.
  • Avoid UI instructions that assume Windows conventions (such as 'right-click'); instead, describe actions in a platform-neutral way (e.g., 'select the options menu').
  • Ensure parity in examples and instructions for both Windows and Linux users throughout the documentation.
  • Consider adding a section or callout for Linux/macOS users, highlighting any differences or tips for using the CLI or portal on non-Windows platforms.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-file-access-logs.md ...articles/azure-netapp-files/manage-file-access-logs.md
High Priority View Details →
Scanned: 2025-08-18 00: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 providing detailed, step-by-step instructions for setting SACLs on SMB shares using Windows GUI tools, while the equivalent Linux/NFS instructions are minimal and refer users to another page. Feature registration examples are given first in Azure PowerShell, with Azure CLI (cross-platform) only mentioned secondarily and without example commands. There are no Linux command-line examples for managing ACLs or audit settings, and Windows tools and workflows are described in more detail.
Recommendations
  • Provide parity in example detail for Linux/NFS workflows, including explicit command-line examples (e.g., setfacl, nfs4_setfacl) for setting Audit ACEs on NFSv4.1 volumes.
  • When presenting feature registration, show both Azure PowerShell and Azure CLI commands side by side, or lead with CLI as the cross-platform option.
  • Include screenshots or step-by-step instructions for Linux environments where applicable, not just Windows.
  • Avoid referencing only Windows administration hosts; explicitly mention and provide guidance for Linux administration hosts.
  • Ensure that all major actions (enabling/disabling logs, setting ACLs) have both Windows and Linux examples where supported.
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-08-11 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell (Azure PowerShell) commands are emphasized throughout, with feature registration and status checks shown first and in more detail than their Azure CLI equivalents. The PowerShell tab is present alongside CLI, REST, and Portal, but PowerShell is often referenced first in feature registration steps. There are no explicit Linux shell (bash) examples, and the CLI examples are not always as detailed as the PowerShell ones. The documentation also references Windows-centric tools and concepts (e.g., PowerShell, Azure PowerShell modules) more prominently than Linux-native equivalents.
Recommendations
  • Ensure that Azure CLI (bash/shell) examples are provided with equal detail and prominence as PowerShell examples, especially for feature registration and status checks.
  • When listing command-line options (PowerShell, CLI, REST), alternate the order or present CLI first to avoid 'windows_first' bias.
  • Explicitly mention that Azure CLI commands can be run natively on Linux/macOS and provide bash-style command snippets where appropriate.
  • Add a short section or note clarifying cross-platform support, including that all Azure CLI commands work on Linux, macOS, and Windows.
  • Where PowerShell is referenced, also provide equivalent bash/Unix shell commands for common administrative tasks (e.g., using az CLI for registration/status).
  • Review screenshots and UI references to ensure they are not Windows-specific unless necessary.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-file-access-logs.md ...articles/azure-netapp-files/manage-file-access-logs.md
High Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed, step-by-step instructions for setting SACLs using Windows GUI tools, while the Linux/NFS equivalent is referenced only via a link with no inline steps. Feature registration examples are shown first in Azure PowerShell, with Azure CLI (cross-platform) only mentioned in passing. Windows tools and workflows are described in detail, whereas Linux workflows are not directly documented.
Recommendations
  • Provide explicit, step-by-step instructions for setting Audit ACEs on NFSv4.1 volumes from a Linux client, similar to the detailed Windows GUI instructions.
  • Include Linux command-line examples (e.g., using setfacl or nfs4_setfacl) for configuring audit ACEs, not just a link.
  • Present Azure CLI commands before or alongside PowerShell examples to promote cross-platform parity.
  • Balance the documentation by ensuring both Windows and Linux workflows are equally detailed and accessible.
  • Add screenshots or command output examples for Linux where appropriate, mirroring the Windows experience.
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-08-11 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exhibits a moderate Windows bias. It provides detailed instructions and screenshots for managing LDAP POSIX attributes using Windows-only tools (Active Directory Users and Computers MMC snap-in), without offering equivalent Linux-based methods. The only explicit example for editing POSIX attributes is via Windows GUI tools, and the section on accessing the Attribute Editor is entirely Windows-centric. Linux/NFS client configuration is referenced only via a link, with no in-page guidance or parity in attribute management. Additionally, the order of presentation often places Windows/SMB concepts and tools before their Linux/NFS counterparts.
Recommendations
  • Add equivalent instructions and examples for managing POSIX attributes using common Linux tools (e.g., ldapmodify, ldapvi, or command-line utilities).
  • Provide screenshots or command examples for editing LDAP attributes from a Linux environment.
  • When describing dual-protocol concepts, alternate or balance the order in which Windows and Linux/NFS tools and workflows are presented.
  • Include a table or section summarizing both Windows and Linux methods for common administrative tasks (e.g., managing LDAP attributes, mounting volumes, troubleshooting access).
  • Ensure that all configuration steps that are shown for Windows are also shown for Linux where applicable, especially for environments where Windows tools are not available.
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-08-11 00: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, mentioning Azure CLI only as an alternative in text. There are no explicit Linux shell or cross-platform command-line examples, and the UI instructions use Windows-specific terminology (e.g., 'right-click'), which may not be as intuitive for Linux users or those using non-Windows environments. No Linux-specific tools or workflows are mentioned.
Recommendations
  • Provide Azure CLI command examples (e.g., 'az feature register', 'az feature show') alongside PowerShell examples in code blocks, not just as a textual mention.
  • Include bash shell examples for relevant CLI commands to ensure Linux parity.
  • Avoid Windows-centric UI terminology like 'right-click' or clarify how to perform equivalent actions in web interfaces or on non-Windows platforms.
  • Where possible, use neutral language and screenshots that are not specific to Windows UI conventions.
  • Explicitly state that all CLI and portal actions are cross-platform unless there are platform-specific limitations.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/create-active-directory-connections.md ...re-netapp-files/create-active-directory-connections.md
High Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only Windows/PowerShell command examples (e.g., Get-ADUser, Set-ADUser), referencing Windows-specific tools and policies (Group Policy, Windows Registry), and focusing on Active Directory Domain Services (AD DS) and Microsoft Entra Domain Services without mentioning or providing equivalent Linux/Unix tools or workflows. Azure CLI is mentioned, but only as an alternative to PowerShell for Azure resource management, not for AD operations. There are no examples or guidance for managing AD connections from Linux environments or using cross-platform tools.
Recommendations
  • Provide equivalent Linux/Unix command-line examples (e.g., using ldapsearch, kinit, or samba-tool) for managing Kerberos encryption types and LDAP settings.
  • Mention and document how to perform relevant AD/LDAP operations from Linux-based systems, including joining domains, setting encryption types, and troubleshooting.
  • When referencing Windows tools (e.g., PowerShell, Group Policy), also reference cross-platform or Linux-native alternatives where possible.
  • Structure sections so that cross-platform or Linux options are presented alongside Windows options, not only as afterthoughts or not at all.
  • Clarify which steps or features are platform-agnostic and which are Windows-specific, to help non-Windows administrators understand their options.
  • Include troubleshooting tips and best practices for Linux/NFS clients in mixed environments, especially for Kerberos and LDAP integration.
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-08-11 00: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 in text without examples. No Linux/bash-specific command examples are given, and the initial command-line workflow assumes PowerShell usage, which is most common on Windows. This may disadvantage Linux/macOS users who typically use Azure CLI or bash scripts.
Recommendations
  • Provide Azure CLI (az) command examples alongside or before PowerShell examples for all command-line steps, especially for feature registration and status checking.
  • Explicitly mention that both Azure PowerShell and Azure CLI are cross-platform, and clarify which shell is being used in each example.
  • Where possible, include bash script snippets or Linux/macOS terminal screenshots to demonstrate parity.
  • Consider reordering examples to present Azure CLI first, as it is more commonly used on Linux/macOS.
  • Add a note or section on how to perform all steps using the Azure CLI for users on non-Windows platforms.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/network-attached-storage-protocols.md ...ure-netapp-files/network-attached-storage-protocols.md
High Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally presents Windows/SMB concepts and tools before or with more detail than Linux/NFS equivalents. Windows terminology (NTFS, SID, Active Directory, NTLM) is used extensively and often explained in more depth, while Linux/UNIX tools and patterns (e.g., Samba, POSIX ACLs, LDAP integration) are mentioned but not elaborated or officially supported. There are no Linux command-line examples or configuration snippets, and Linux/UNIX support is sometimes described as unofficial or less robust.
Recommendations
  • Provide Linux/UNIX command-line examples (e.g., mounting NFS/SMB shares, configuring idmapd, using Samba) alongside or before Windows examples.
  • Expand explanations of Linux/UNIX concepts (e.g., POSIX ACLs, nfs-utils, LDAP integration) to match the depth given to Windows/SMB/NTFS topics.
  • Clarify official support status for Linux/UNIX SMB clients and provide troubleshooting guidance for common scenarios.
  • Balance terminology by introducing Linux/UNIX equivalents (e.g., POSIX permissions, UIDs/GIDs, nsswitch.conf) when Windows-specific terms are used.
  • Include links to relevant Linux/UNIX documentation and best practices, not just Windows/Active Directory resources.
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-08-11 00: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, with only a brief mention of Azure CLI as an alternative. There are no Linux shell or Bash examples, and the PowerShell examples are presented first and in detail, which may disadvantage Linux users or those who prefer CLI tools.
Recommendations
  • Provide explicit Azure CLI command examples alongside PowerShell, with full syntax and usage (e.g., 'az feature register --namespace Microsoft.NetApp --name ANFDisableShowmount').
  • Present CLI and PowerShell examples in parallel or in separate tabs to give equal prominence to both Windows and Linux users.
  • Include a note or section on how to perform these actions from a Linux environment, possibly including Bash scripting examples.
  • Avoid assuming PowerShell as the default interface; clarify that both PowerShell and CLI are supported and provide equal guidance for both.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/snapshots-introduction.md .../articles/azure-netapp-files/snapshots-introduction.md
High Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. In the 'Ways to create snapshots' section, PowerShell is listed as a primary tool alongside the Azure portal, REST API, and Azure CLI, but there is no mention of Linux-specific command-line examples or tools. The scripting example linked is for SQL Server (a Windows-centric workload), and there are no explicit Linux shell (bash) or automation examples. While the documentation is generally platform-agnostic in its conceptual explanations, the operational guidance and tooling references lean toward Windows and PowerShell, with Linux parity not explicitly addressed.
Recommendations
  • Include Linux/bash command-line examples for snapshot creation and management, especially using Azure CLI.
  • Provide sample scripts for Linux environments (e.g., bash scripts) alongside PowerShell examples.
  • When listing tools, avoid listing PowerShell before Azure CLI or REST API, or clarify that both Windows and Linux environments are supported equally.
  • Add references or links to Linux-specific documentation or community resources for managing Azure NetApp Files snapshots.
  • Ensure that automation and scripting guidance is balanced between Windows (PowerShell) and Linux (bash, shell scripting) environments.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-nfs.md ...-docs/blob/main/articles/azure-netapp-files/faq-nfs.md
High Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page is generally neutral and focused on NFS, which is primarily a Unix/Linux protocol. However, there is a notable Windows bias in the section addressing NFS access from Windows clients: only Windows-specific tools (PowerShell, Windows mount command) are mentioned, and no equivalent Linux example is provided. The Windows client troubleshooting section appears before any Linux-specific troubleshooting, and there is no parity in terms of Linux client configuration advice or examples.
Recommendations
  • For every Windows-specific example (such as enabling CaseSensitiveLookup or mounting NFS volumes), provide an equivalent Linux example (e.g., using mount options or editing /etc/nfsmount.conf).
  • If troubleshooting steps are given for Windows clients, provide a corresponding section for Linux clients, covering common issues and their solutions.
  • Ensure that Linux tools and commands are mentioned with equal prominence and detail as their Windows counterparts.
  • Consider reordering sections so that Linux examples appear before or alongside Windows examples, especially since NFS is more commonly used on Linux.
  • Add explicit Linux client configuration advice for performance tuning, mounting, and troubleshooting, similar to the detail given for Windows clients.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/whats-new.md ...ocs/blob/main/articles/azure-netapp-files/whats-new.md
High Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windows Heavy Examples
Summary
The documentation for Azure NetApp Files demonstrates a moderate Windows bias. Features and enhancements related to Windows technologies (such as SMB, Active Directory, Windows File Explorer, and Windows-specific tools) are frequently mentioned, often before or in more detail than their Linux/NFS equivalents. Many feature descriptions focus on Windows-centric use cases (e.g., FSLogix, Citrix, SQL Server on Windows, Windows client behaviors), and some features are described primarily in terms of their impact on Windows environments. While Linux/NFS features are present and some Linux tools (like AzAcSnap) are mentioned, Windows terminology and workflows are more prominent and sometimes prioritized.
Recommendations
  • Ensure that for every Windows/SMB/Active Directory example or feature description, an equivalent Linux/NFS/LDAP example or use case is provided, ideally with parity in detail and placement.
  • When describing features that apply to both Windows and Linux (e.g., dual-protocol, quotas, snapshots), present both perspectives equally, and avoid defaulting to Windows terminology (such as referencing Windows File Explorer without mentioning Linux file browsers or CLI tools).
  • Add Linux/NFS-focused scenarios and examples where missing, especially for features currently described only in Windows/SMB/Active Directory terms (e.g., access-based enumeration, non-browsable shares, file access logs).
  • Where Windows tools or workflows are referenced (e.g., PowerShell, Windows File Explorer), include Linux equivalents (e.g., shell commands, Linux file managers) side-by-side.
  • Review the order of protocol mentions (e.g., NFS vs. SMB) to avoid always listing Windows/SMB first, and alternate or balance their presentation.
  • Highlight Linux-native tools and integration points (e.g., NFSv4.1 Kerberos, POSIX ACLs, Linux client behaviors) with the same prominence as Windows features.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/create-active-directory-connections.md ...re-netapp-files/create-active-directory-connections.md
High Priority View Details →
Scanned: 2025-08-10 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias, primarily through exclusive use of Windows/PowerShell commands for Active Directory management, references to Windows-specific tools and policies (such as Group Policy and Windows registry keys), and a lack of Linux or cross-platform examples for managing AD connections. Windows terminology and tools are mentioned first or exclusively, with no equivalent instructions for Linux-based environments or tools like Samba or Linux-based AD management.
Recommendations
  • Provide equivalent Linux-based command examples (e.g., using Samba tools like 'samba-tool', 'net ads', or 'ldapmodify') for managing Kerberos encryption types and AD user properties.
  • Include instructions for configuring Kerberos and LDAP settings on Linux clients, such as editing '/etc/krb5.conf' and '/etc/sssd/sssd.conf', and using 'kadmin' or 'ktutil' for keytab and encryption management.
  • Reference Linux-compatible tools and methods (e.g., 'realm', 'adcli', 'sssd') alongside Windows tools when discussing AD domain joins, account management, and encryption settings.
  • When discussing Group Policy or registry settings, mention equivalent Linux configuration files or policies, or clarify if certain settings are not applicable to Linux environments.
  • Add Linux-focused troubleshooting steps and examples for common scenarios (e.g., LDAP query timeouts, Kerberos authentication failures) to ensure parity.
  • Structure examples so that both Windows and Linux approaches are presented side-by-side where possible, or at least ensure Linux is not omitted.
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-08-10 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Azure PowerShell commands are given significant prominence, both in the registration of features and in the main procedural sections. In the 'Edit network features' section, PowerShell is presented as a primary method alongside Azure CLI and REST API, but PowerShell commands and terminology (e.g., Register-AzProviderFeature, Get-AzProviderFeature) are referenced first and most frequently. There is no mention of Linux-specific shell usage or examples, and the PowerShell tab is present before REST API and Terraform. The Azure CLI is included, which is cross-platform, but there are no explicit Linux/Bash shell examples or guidance for Linux users. The documentation also references Windows-centric tools and patterns (e.g., PowerShell, Azure PowerShell modules) without equivalent Linux-focused context.
Recommendations
  • Add explicit Bash/Linux shell examples for all CLI commands, showing usage in a Linux terminal environment.
  • Clarify that Azure CLI commands are cross-platform and provide sample invocations in both Windows (CMD/PowerShell) and Linux (Bash) contexts.
  • Reorder the command tabs (where possible) to present Azure CLI or REST API before PowerShell, or at least alternate the order to avoid Windows-first bias.
  • Include notes or sections addressing Linux users, such as prerequisites for running Azure CLI on Linux, and troubleshooting tips relevant to Linux environments.
  • Where PowerShell is referenced, provide equivalent Bash scripts or commands for Linux users, especially for automation scenarios.
  • Review screenshots and UI references to ensure they are not exclusively from Windows environments (if applicable).
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/snapshots-introduction.md .../articles/azure-netapp-files/snapshots-introduction.md
High Priority View Details →
Scanned: 2025-08-10 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. In sections describing how to create and manage snapshots, the order of tooling references consistently lists PowerShell before Linux-native tools (e.g., Azure CLI), and explicit PowerShell module links are provided. There are no explicit Linux/Unix shell or scripting examples, nor are Linux tools or patterns highlighted. The only scripting example referenced is for SQL Server (a Windows-centric workload). There is no mention of Linux-specific client access patterns or examples, and no screenshots or walkthroughs for Linux environments.
Recommendations
  • When listing tools or interfaces (Azure portal, REST API, CLI, PowerShell), alternate the order or explicitly mention Linux/Unix shell usage alongside PowerShell.
  • Provide example commands for both PowerShell and Bash/Azure CLI, especially in sections about creating, restoring, or deleting snapshots.
  • Include references or links to Linux/Unix scripting guides for Azure NetApp Files, not just Windows/PowerShell.
  • Add examples or screenshots showing snapshot access and file restore from Linux clients (e.g., using NFS mounts and standard Linux commands like cp, ls, etc.).
  • Reference Linux/Unix workloads and use cases (e.g., SAP HANA on Linux) more explicitly in relevant sections.
  • Ensure parity in documentation coverage for both Windows (SMB) and Linux (NFS) protocols, including client-side restore operations.
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-08-10 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows tools (such as Active Directory Users and Computers MMC snap-in) for managing LDAP POSIX attributes, providing step-by-step instructions only for Windows environments, and omitting equivalent Linux-based methods or tools for these tasks. Additionally, the order of presentation and examples prioritizes Windows terminology and workflows, with Linux/NFS client configuration relegated to a brief reference link without in-page guidance.
Recommendations
  • Add equivalent Linux-based instructions for managing LDAP POSIX attributes, such as using ldapmodify, ldapadd, or graphical tools like Apache Directory Studio.
  • Provide example commands or screenshots for configuring POSIX attributes on Linux LDAP servers (e.g., OpenLDAP).
  • Ensure that both Windows and Linux tools are mentioned together, or alternate their order to avoid Windows-first bias.
  • Expand the 'Configure the NFS client' section to include at least a basic example or summary inline, not just a link.
  • Where Windows-specific features or limitations are discussed (e.g., non-browsable share), clarify Linux/NFS client behavior for parity.
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-08-10 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page primarily provides Azure PowerShell commands for feature registration and management, with only a brief mention of Azure CLI as an alternative. There are no explicit Linux shell or cross-platform examples, and the PowerShell approach is presented first and in detail, which may disadvantage Linux users or those who prefer CLI tools.
Recommendations
  • Provide full Azure CLI command examples alongside PowerShell, including output examples and usage notes.
  • List Azure CLI (cross-platform) instructions before or alongside PowerShell to avoid Windows-first bias.
  • Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide guidance for Linux users.
  • If applicable, include bash script examples or instructions for automation on Linux.
  • Clarify any differences or limitations between PowerShell and CLI approaches.
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-08-10 00: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 presenting Azure PowerShell commands as the primary method for feature registration and status checking, with Azure CLI (cross-platform) only mentioned secondarily and without explicit examples. There are no Linux- or macOS-specific instructions or screenshots, and the initial automation steps are shown only with PowerShell, which is most familiar to Windows users.
Recommendations
  • Provide Azure CLI examples alongside or before PowerShell examples for all command-line steps, especially for feature registration and status checking.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Include screenshots or instructions that are not specific to the Windows Azure Portal experience, or clarify that the steps are identical across platforms.
  • Add a section or callout for Linux/macOS users, confirming that all steps can be performed from those environments using Azure CLI.
  • Ensure parity in automation examples by offering Bash shell scripts or command sequences where appropriate.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/network-attached-storage-protocols.md ...ure-netapp-files/network-attached-storage-protocols.md
High Priority View Details →
Scanned: 2025-08-10 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally presents Windows/SMB concepts and terminology before or with more detail than Linux/NFS equivalents, especially in areas like authentication, permissions, and supported tools. Windows-centric tools and patterns (Active Directory, NTFS ACLs, Kerberos/NTLM, SID translation) are discussed in depth, while Linux/UNIX tools (Samba, POSIX ACLs, idmapd, nfs-utils) are mentioned less prominently or only in passing. There are no explicit Linux command-line examples for NFS or dual-protocol scenarios, and official support is only noted for Windows/macOS SMB clients, not Linux/Samba. This may leave Linux administrators with less actionable guidance.
Recommendations
  • Provide parallel Linux/UNIX command-line examples (e.g., mounting NFS/SMB shares, checking permissions, troubleshooting identity mapping) alongside any Windows/Powershell examples.
  • Discuss Linux/UNIX tools and patterns (such as Samba configuration, POSIX ACL management, idmapd, nfs-utils) in equal depth as Windows tools (Active Directory, NTFS ACLs).
  • Clarify support status and best practices for Linux/Samba SMB clients, including any limitations or recommended configurations.
  • Ensure that Linux/UNIX terminology (e.g., POSIX ACLs, mode bits, LDAP integration) is introduced and explained with the same prominence as Windows/NTFS concepts.
  • Add troubleshooting and configuration guidance for common Linux/UNIX scenarios, such as resolving UID/GID mismatches, configuring LDAP, or managing dual-protocol permissions from a Linux perspective.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-nfs.md ...-docs/blob/main/articles/azure-netapp-files/faq-nfs.md
High Priority View Details →
Scanned: 2025-08-10 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a Windows bias in the section addressing NFS access from Windows clients. It provides a PowerShell command and a Windows-specific mount example, but does not offer equivalent Linux commands or examples. Additionally, Windows tooling and patterns are mentioned exclusively in this context, and Linux is not given parity in the troubleshooting or configuration guidance for NFS client behavior.
Recommendations
  • For every Windows-specific example (such as PowerShell commands and mount instructions), provide equivalent Linux shell commands and mount examples.
  • In the section on troubleshooting NFS client performance (e.g., CaseSensitiveLookup), include Linux-specific advice or clarify if the issue is Windows-only.
  • When discussing persistent NFS mounts, provide both Windows and Linux configuration steps or clearly state if a feature is not applicable to one platform.
  • Ensure that Linux tools and patterns are mentioned alongside Windows tools, and avoid presenting Windows solutions first or exclusively.
  • Review the documentation for other subtle Windows-first language or assumptions, and update to ensure cross-platform parity.
GitHub Create Pull Request
← Previous Page 16 of 36 Next →