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 51-75 of 228 flagged pages
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/network-attached-file-permissions-smb.md
...-netapp-files/network-attached-file-permissions-smb.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page focuses exclusively on NTFS ACLs and references Microsoft's Windows documentation for access control, without mentioning Linux equivalents (such as POSIX permissions or NFSv4 ACLs). No Linux or cross-platform examples are provided, and only Windows terminology and tools are referenced.
Recommendations
- Include a section comparing NTFS ACLs with Linux/UNIX permissions (e.g., POSIX permissions, NFSv4 ACLs) to provide context for Linux users.
- Provide examples or references for managing SMB permissions from Linux clients (e.g., using smbclient, setfacl, or mount.cifs options).
- Mention any limitations or considerations when accessing Azure NetApp Files SMB volumes from Linux systems.
- Add links to relevant Linux documentation or tools for managing SMB file permissions.
Create Pull Request
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/monitor-volume-capacity.md
...articles/azure-netapp-files/monitor-volume-capacity.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation presents Windows client methods before Linux equivalents, describes Windows-specific tools (File Explorer, dir command) in more detail, and references PowerShell in the REST API section. Linux examples are present but less elaborated, and Linux tools are not mentioned first or in equal detail.
Recommendations
- Present Linux and Windows client methods in parallel or alternate order to avoid implicit prioritization.
- Expand Linux section to include additional commands (e.g., ls, stat, ncdu) and GUI tools (e.g., GNOME Disks, KDE Dolphin) for parity with Windows File Explorer.
- Include REST API usage examples for Linux environments (e.g., curl, wget, Python scripts) alongside PowerShell.
- Clarify that both Windows and Linux clients are equally supported and provide troubleshooting tips for both platforms.
- Ensure screenshots and examples are balanced between Windows and Linux environments.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/mount-volumes-vms-smb.md
...n/articles/azure-netapp-files/mount-volumes-vms-smb.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively covers mounting SMB volumes on Windows virtual machines, providing only Windows client instructions and screenshots. There are no examples or instructions for mounting SMB volumes on Linux clients, nor are Linux tools or commands mentioned. The focus is entirely on Windows tools and workflows.
Recommendations
- Add a section with instructions for mounting SMB volumes on Linux clients, including relevant commands (e.g., using 'mount -t cifs' or 'smbclient').
- Provide Linux-specific screenshots or terminal output to illustrate the process.
- Mention Linux tools and patterns alongside Windows tools, ensuring parity in the order and detail of instructions.
- Consider updating the title and description to clarify if the page is intended to be Windows-specific, or broaden the scope to include Linux if applicable.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/network-attached-file-permissions.md
...zure-netapp-files/network-attached-file-permissions.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates Windows bias by describing Windows (SMB) permission inheritance first, providing a screenshot of the Windows interface, and referencing Windows-specific tools and patterns (e.g., 'advanced permission view'). Linux/NFS equivalents are mentioned later and lack visual examples or command-line instructions. There are no Linux shell or setfacl/chmod/chown examples, and the explanation of NFS permission inheritance is less detailed.
Recommendations
- Provide Linux/NFS examples with equivalent detail, including screenshots of common Linux tools (e.g., setfacl, chmod, chown) or command-line examples for managing NFS permissions and inheritance.
- Present SMB and NFS sections in parallel or alternate order to avoid consistently prioritizing Windows.
- Include explanations and visuals for how to manage inheritance and permissions on Linux clients, not just Windows.
- Add links to Linux/NFS-specific documentation and tools where appropriate.
- Clarify differences and similarities in permission management workflows between Windows and Linux environments.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/network-file-system-group-memberships.md
...-netapp-files/network-file-system-group-memberships.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by focusing on Microsoft Active Directory as the LDAP implementation, referencing Windows group membership logic, and providing examples and screenshots exclusively from Windows tools (such as ldp.exe and Windows group member fields). There are no examples or instructions for Linux LDAP servers (such as OpenLDAP), nor are Linux-native tools or patterns mentioned.
Recommendations
- Include equivalent examples for Linux LDAP servers (e.g., OpenLDAP), showing how group memberships and supplemental groups are managed and queried.
- Provide screenshots and command-line examples using Linux tools such as ldapsearch, getent, or nslcd.
- Clarify whether Azure NetApp Files supports non-Active Directory LDAP servers and document any differences in behavior or configuration.
- Mention Linux group membership logic and schema attributes (such as memberUid) alongside Windows-specific attributes.
- Ensure that references to Windows tools (e.g., ldp.exe) are balanced with Linux alternatives, and avoid presenting Windows-first workflows unless required by the service.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/network-attached-storage-permissions.md
...e-netapp-files/network-attached-storage-permissions.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. SMB share management is described exclusively via Windows tools (MMC console), with no mention of Linux or cross-platform alternatives. Examples and screenshots for SMB features (such as access-based enumeration, nonbrowsable shares, and ACLs) are all shown using Windows Explorer or Windows-specific commands, with no Linux or macOS equivalents. The documentation refers to 'net view' and Windows Explorer as the primary ways to interact with SMB shares, and does not provide parity for Linux users (e.g., using smbclient, mount.cifs, or other tools). There are no examples or instructions for managing SMB share permissions or accessing SMB shares from Linux clients.
Recommendations
- Include instructions and examples for managing SMB share permissions and accessing SMB shares from Linux clients (e.g., using smbclient, mount.cifs, or relevant Linux tools).
- Mention and demonstrate how Linux/macOS users can view and interact with SMB shares, including how access-based enumeration and nonbrowsable shares behave in those environments.
- Provide parity in screenshots and examples, showing both Windows and Linux client perspectives for SMB features.
- Reference cross-platform tools for managing SMB shares and ACLs, such as setfacl, smbclient, or other open-source utilities.
- Clarify whether features like access-based enumeration and nonbrowsable shares apply equally to non-Windows clients, and document any differences.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/object-rest-api-browser.md
...articles/azure-netapp-files/object-rest-api-browser.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates Windows bias by providing certificate installation steps that are specific to Windows (using Edge, GUI dialogs, and the Windows certificate store) without mentioning Linux or macOS equivalents. The S3 Browser example is Windows-only, and the certificate installation process does not cover Linux CLI or browser-agnostic methods. While the AWS CLI section includes both Windows and Linux installation instructions, the overall flow and tool selection favor Windows environments.
Recommendations
- Add instructions for installing the certificate on Linux systems, including CLI-based methods (e.g., using update-ca-certificates or copying to /usr/local/share/ca-certificates).
- Include examples for macOS users, such as using Keychain Access to install certificates.
- Mention and provide examples for S3-compatible clients available on Linux (e.g., s3cmd, rclone, or Cyberduck) in addition to S3 Browser.
- When listing AWS CLI installation steps, present Linux and Windows instructions in parallel or in a platform-neutral order.
- Avoid GUI-only instructions; provide CLI alternatives where possible for cross-platform parity.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/ransomware-configure.md
...in/articles/azure-netapp-files/ransomware-configure.md
High Priority
View Details →
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, with Azure CLI (which is cross-platform and more common on Linux) only mentioned secondarily and without explicit command examples. No Linux-specific instructions, screenshots, or shell examples are provided, and the documentation assumes familiarity with PowerShell and Windows-centric workflows.
Recommendations
- Provide explicit Azure CLI command examples alongside PowerShell for all registration and status-checking steps (e.g., show 'az feature register' and 'az feature show' commands).
- When referencing command-line instructions, present Azure CLI (cross-platform) examples first, or at least in parallel with PowerShell.
- Include notes or sections for Linux/macOS users, clarifying that all features are accessible via Azure CLI and the Azure Portal.
- Ensure screenshots and UI instructions do not assume a Windows environment unless necessary.
- Where possible, add bash/zsh shell equivalents for any scripts or automation steps.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/sever-message-block-support.md
...cles/azure-netapp-files/sever-message-block-support.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. Most examples, terminology, and feature explanations reference Windows tools, protocols, and patterns (e.g., NTFS, Hyper-V, MS SQL Server, VSS, LMHOSTS, Windows quota semantics, Windows Indexing Service). Windows-specific features are described in detail, while Linux or macOS equivalents are rarely mentioned or are described as unsupported or disabled (e.g., UNIX extensions, export policies for SMB, deletion semantics). References to Linux clients are minimal and lack concrete configuration or usage examples. The documentation assumes familiarity with Windows environments and omits guidance for Linux-based SMB clients, their configuration, and troubleshooting.
Recommendations
- Add explicit examples and configuration steps for Linux-based SMB clients (e.g., mounting Azure NetApp Files SMB shares from Linux using smbclient, mount.cifs, or similar tools).
- Include Linux-specific troubleshooting tips and caveats, such as handling permissions, symlinks, and file attribute differences.
- Provide parity in describing features and limitations for both Windows and Linux/macOS clients, especially where behaviors differ (e.g., delete semantics, offline files, symbolic links).
- Reference Linux tools and documentation (e.g., Samba, cifs-utils) alongside Windows tools.
- Clarify which features are relevant or available to Linux/macOS clients and provide guidance for mixed-environment deployments.
- Avoid assuming Windows as the default client; use neutral language and order examples for both platforms equally.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/tools-reference.md
...ob/main/articles/azure-netapp-files/tools-reference.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation lists several tools for Azure NetApp Files, but the only automation/scripted tool with a specific platform mentioned is ANFHealthCheck, which is described as a PowerShell runbook. There are no Linux/bash equivalents or cross-platform scripting examples provided. This suggests a bias towards Windows/PowerShell environments, with a lack of parity for Linux users.
Recommendations
- Provide equivalent bash or Python scripts for Linux users where PowerShell runbooks are offered (e.g., for ANFHealthCheck).
- Explicitly mention if tools are cross-platform or provide platform-specific instructions/examples for both Windows and Linux.
- Highlight or add Linux-native automation options (such as Azure CLI/bash scripts) alongside PowerShell-based solutions.
- Review all tool documentation to ensure Linux users are not excluded from automation and monitoring workflows.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/troubleshoot-volumes.md
...in/articles/azure-netapp-files/troubleshoot-volumes.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by consistently prioritizing SMB/Active Directory (Windows-centric) errors and resolutions before NFS/Linux scenarios. Troubleshooting steps and examples frequently reference Windows tools (e.g., PowerShell, Set-ADComputer) and concepts (Active Directory, Microsoft Entra Domain Services) without providing equivalent Linux/Unix commands or alternatives. Where Linux/NFS is mentioned, it is often secondary or less detailed. PowerShell is used for directory operations without showing Linux-native alternatives (e.g., ldapmodify, samba-tool).
Recommendations
- Provide Linux/Unix command-line examples (e.g., using ldapmodify, samba-tool, or kadmin) alongside PowerShell commands for managing AD/Kerberos attributes.
- Structure error tables to alternate or parallelize SMB (Windows) and NFS (Linux) issues, rather than always listing Windows/SMB first.
- Include troubleshooting steps and tools relevant to Linux environments (e.g., systemd, kinit, nsupdate) wherever Windows tools are referenced.
- Expand on NFS/Linux-specific troubleshooting, such as using Linux logs, systemctl, and open-source LDAP/Kerberos tools.
- Where possible, provide parity in detail and actionable steps for both Windows and Linux administrators.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/understand-path-lengths.md
...articles/azure-netapp-files/understand-path-lengths.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by prioritizing Windows/SMB path length details, providing Windows-specific configuration steps (such as registry edits and Group Policy), and showing Windows dialog screenshots. Linux/NFS examples are present but less detailed, with fewer practical configuration or troubleshooting steps. Windows tools and patterns (drive letter mapping, UNC paths, registry changes) are described in depth, while equivalent Linux/NFS client configuration and troubleshooting are not covered as thoroughly.
Recommendations
- Add Linux/NFS client configuration examples, such as mounting options and troubleshooting path length errors.
- Provide parity in screenshots and error dialogs for Linux environments (e.g., terminal output for path length errors).
- Include instructions for extending or querying NFS path limits using Linux tools and configuration files.
- Balance the order of presentation so that NFS/Linux information is given equal prominence to SMB/Windows details.
- Mention Linux equivalents for Windows tools (e.g., alternatives to Group Policy for enforcing limits, or using fstab for mounting).
- Clarify cross-platform limitations and workarounds for both Windows and Linux clients, not just Windows.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/use-dfs-n-and-dfs-root-consolidation-with-azure-netapp-files.md
...s-n-and-dfs-root-consolidation-with-azure-netapp-files.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows environments. All examples, instructions, and tooling references are exclusively for Windows Server, PowerShell, and Windows GUI tools. There are no Linux or cross-platform examples, and the documentation does not mention or address Linux clients, tools, or alternatives. Windows terminology and patterns are used throughout, and Windows tools are always presented first and exclusively.
Recommendations
- Acknowledge in the introduction that DFS Namespaces is a Windows-centric technology, but clarify any possible Linux client or integration scenarios (e.g., using SMB mounts from Linux).
- Provide guidance or references for accessing DFS-N namespaces from Linux clients (e.g., using smbclient, mount.cifs, or other SMB tools on Linux).
- If possible, include Linux command-line examples for mounting SMB shares exposed via DFS-N, or at least mention that Linux clients can access these shares using standard SMB tools.
- Mention any limitations or considerations when using DFS-N with non-Windows clients, such as differences in referral handling or UNC path support.
- Add a section or note on how to manage DNS records using Linux tools (e.g., `nsupdate`, `dig`, or editing BIND zone files) for organizations not using Windows DNS servers.
- Where PowerShell is used, clarify that these steps are for Windows environments, and suggest alternatives or workarounds for cross-platform or hybrid environments if applicable.
Azure Netapp Files
Create volume replication for Azure NetApp Files
...etapp-files/cross-region-replication-create-peering.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides Azure PowerShell examples first and in detail for feature registration, with only a brief mention of Azure CLI as an alternative. The step-by-step instructions and screenshots are focused on the Azure Portal GUI, which is platform-agnostic, but the command-line guidance is Windows/PowerShell-centric. There are no explicit Linux/macOS command examples, and the CLI alternative is referenced only via a link, not shown inline.
Recommendations
- Provide explicit Azure CLI command examples alongside PowerShell for feature registration and status checks.
- Show both PowerShell and CLI commands in parallel, or indicate which is recommended for Linux/macOS users.
- Add a note clarifying that all portal steps are cross-platform and accessible from any OS.
- Consider ordering CLI and PowerShell examples together, or alternate which is shown first.
Azure Netapp Files
Create an SMB volume for Azure NetApp Files
...-netapp-files/azure-netapp-files-create-volumes-smb.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation is focused on creating and managing SMB volumes for Azure NetApp Files, which is inherently a Windows-centric protocol. However, the sections on managing permissions and share properties exclusively reference Windows tools (MMC, Windows SMB client) and do not mention or provide guidance for Linux or macOS clients, which can also access SMB shares. There are no examples or instructions for mounting or managing SMB volumes from non-Windows systems.
Recommendations
- Add a section or examples showing how to mount and access the SMB volume from Linux and macOS clients (e.g., using the 'mount -t cifs' command on Linux, or Finder on macOS).
- Include instructions or references for managing SMB permissions from Linux (e.g., using 'smbclient', 'setfacl', or other Samba tools where applicable).
- Clarify which management tasks must be performed from Windows and which can be performed from other platforms, to set user expectations.
- Link to the 'Mount a volume for Windows or Linux virtual machines' article earlier in the workflow, especially in the 'Control access' section.
Azure Netapp Files
Migrate volumes to Azure NetApp Files
...ob/main/articles/azure-netapp-files/migrate-volumes.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. The only explicit code sample for automating migration uses PowerShell, with no equivalent Bash or Linux shell script provided. The feature registration steps are shown first with Azure PowerShell, and only secondarily mention Azure CLI as an alternative. There are no Linux/macOS-specific instructions or examples for scripting or automation, and the tip for workflow automation links only to a PowerShell script. The rest of the migration process is platform-neutral (REST API, portal, ONTAP CLI), but the initial onboarding and scripting guidance favor Windows users.
Recommendations
- Provide equivalent Bash or Azure CLI sample scripts for migration assistant workflow automation.
- Show Azure CLI commands before or alongside PowerShell commands in feature registration steps.
- Add explicit guidance for Linux/macOS users on how to perform migration steps, including scripting and automation.
- Include links to Linux/macOS sample scripts in the 'TIP' section, not just PowerShell.
- Ensure all automation and scripting examples are available for both Windows and Linux platforms.
Azure Netapp Files
Back up using Azure Application Consistent Snapshot tool for Azure NetApp Files | Microsoft Docs
...articles/azure-netapp-files/azacsnap-cmd-ref-backup.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides detailed instructions and multiple examples for running the AzAcSnap tool with administrator privileges on Windows, including CMD, PowerShell, and Task Scheduler methods. These Windows-specific tools and elevation patterns are described at length, while the Linux equivalent (using 'sync' for I/O flush) is mentioned briefly and without example. Windows instructions are presented first and in greater detail, creating a notable bias toward Windows environments.
Recommendations
- Add step-by-step instructions for running AzAcSnap with required privileges on Linux, including example commands (e.g., using sudo).
- Provide parity in example detail for Linux, such as how to automate privileged execution (e.g., systemd service, cron job with sudo).
- Present Linux and Windows instructions in parallel sections or with equal prominence.
- Include macOS-specific notes if supported, or clarify platform limitations.
- Ensure that all examples (especially those involving privilege elevation and I/O flush) are shown for both Windows and Linux.
Azure Netapp Files
Configure the database for Azure Application Consistent Snapshot tool for Azure NetApp Files
...cles/azure-netapp-files/azacsnap-configure-database.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides examples and instructions for multiple databases (SAP HANA, Oracle, IBM Db2, Microsoft SQL Server) and generally uses Linux shell commands for SAP HANA, Oracle, and Db2. However, for Microsoft SQL Server, the documentation exclusively uses Windows-style commands (e.g., .\azacsnap.exe), references Windows tools, and does not provide any Linux-based example or mention cross-platform alternatives for SQL Server. Additionally, the SQL Server section is placed last, which is a minor 'windows_first' bias, but the exclusive use of Windows tools for SQL Server is more significant.
Recommendations
- Provide explicit Linux/macOS instructions and examples for Microsoft SQL Server, such as using sqlcmd or AzAcSnap on Linux.
- Clarify whether AzAcSnap supports SQL Server on Linux and, if so, include installation and usage steps for Linux environments.
- Where possible, offer cross-platform command examples (e.g., both bash and PowerShell) for all databases, especially SQL Server.
- Mention any limitations or differences for SQL Server on Linux, if applicable.
- Ensure that tool download links and instructions are available for both Windows and Linux platforms.
Azure Netapp Files
Azure NetApp Files for Azure Government
...b/main/articles/azure-netapp-files/azure-government.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides detailed instructions for accessing Azure Government via Azure CLI and PowerShell, with PowerShell examples and references given significant prominence. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell commands are listed in detail, which may create friction for Linux/macOS users who typically use Bash or other shells. The CLI section is present, but the PowerShell section is longer and more detailed, and there are no Linux-specific notes or parity checks.
Recommendations
- Add explicit Bash/Linux/macOS shell examples for connecting to Azure Government, especially for tasks currently shown only with PowerShell.
- Clarify that Azure CLI commands work cross-platform and provide examples of usage in Bash or zsh.
- Balance the PowerShell section with equivalent instructions for Linux/macOS users, such as using Azure CLI in shell scripts.
- Add notes or links for Linux/macOS users on authentication and endpoint configuration.
- Reorder sections so that cross-platform tools (Azure CLI) are presented before Windows-specific tools (PowerShell).
Azure Netapp Files
Release Notes for Azure Application Consistent Snapshot tool for Azure NetApp Files | Microsoft Docs
.../articles/azure-netapp-files/azacsnap-release-notes.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides both Linux and Windows binaries for AzAcSnap and mentions support for both platforms. However, there is a consistent pattern of mentioning Windows support/features (especially for Microsoft SQL Server) before Linux equivalents, and some features are described as Windows-specific (e.g., SQL Server 2022 on Windows). There is also a lack of explicit Linux/macOS-specific examples, troubleshooting, or parity notes, and no mention of Linux-specific tools or patterns. The documentation does not provide examples or guidance for Linux users beyond download links, and Windows features (such as SQL Server support) are highlighted as major milestones.
Recommendations
- Include explicit Linux/macOS usage examples and troubleshooting steps, especially for database features.
- Clarify which features are available on Linux, Windows, or both, and provide parity tables if features differ.
- Highlight Linux support and improvements equally when new features are released.
- Add Linux-first or side-by-side examples for configuration and environment variable usage.
- Mention Linux-specific tools or patterns (e.g., shell scripting, systemd integration) where relevant.
Azure Netapp Files
Create an SMB volume for Azure NetApp Files
...-netapp-files/azure-netapp-files-create-volumes-smb.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page for creating an SMB volume in Azure NetApp Files demonstrates a notable Windows bias. All examples and instructions for managing SMB permissions and shares are exclusively Windows-centric, referencing Windows tools (MMC, Windows SMB client, Control Panel) and omitting any guidance for Linux or macOS clients. No Linux-based SMB management or mounting examples are provided, and Windows terminology and workflows are presented as the default.
Recommendations
- Include instructions and examples for managing SMB permissions and shares from Linux clients, such as using smbclient, mount.cifs, or setfacl.
- Provide parity in screenshots and step-by-step guides for Linux and macOS environments where applicable.
- Reference Linux tools (e.g., smbclient, cifs-utils) alongside Windows tools when discussing SMB access and management.
- Add a section on mounting and interacting with SMB volumes from Linux/macOS, including troubleshooting tips specific to those platforms.
- Avoid presenting Windows workflows as the only or primary method; offer platform-neutral language and ordering.
Azure Netapp Files
Azure NetApp Files SDKs and CLI tools
...icles/azure-netapp-files/azure-netapp-files-sdk-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation lists both Azure CLI and PowerShell as supported CLI tools, but PowerShell—a Windows-centric tool—is given equal prominence without clarifying cross-platform support. No explicit Linux/macOS examples, installation instructions, or notes are provided. The page does not mention Bash, shell scripting, or Linux-specific usage patterns, and PowerShell is referenced before any Linux alternatives.
Recommendations
- Clarify that Azure CLI is cross-platform and provide installation/use examples for Linux/macOS.
- Add explicit instructions or references for using Azure CLI on Linux/macOS.
- Mention PowerShell Core (pwsh) if cross-platform support is intended, or clarify if only Windows PowerShell is supported.
- Include Linux/macOS-specific usage notes or troubleshooting tips.
- Consider listing CLI tools with Azure CLI first, as it is the primary cross-platform tool.
Azure Netapp Files
SMB performance best practices for Azure NetApp Files
...ure-netapp-files/azure-netapp-files-smb-performance.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation consistently references Windows-specific tools, commands, and monitoring utilities (e.g., PowerShell cmdlets, Windows Performance Monitor, Hyper-V adapters) and provides examples and guidance only for Windows environments. There are no Linux or macOS equivalents or instructions, despite SMB being supported on those platforms. Windows terminology and links are prioritized throughout, creating friction for non-Windows users.
Recommendations
- Add SMB client configuration and monitoring instructions for Linux (e.g., using smbclient, mount.cifs, or relevant sysfs/procfs entries).
- Include Linux/macOS command examples for checking SMB Multichannel, RSS, and encryption support.
- Reference cross-platform SMB documentation and best practices, not just Windows Server links.
- Provide parity in performance testing instructions and tools (e.g., using iostat, atop, or netstat on Linux/macOS).
- Clarify which recommendations are platform-agnostic and which are Windows-specific.
Azure Netapp Files
Deploy Azure NetApp Files application volume group for Oracle using Azure Resource Manager
...igure-application-volume-oracle-azure-resource-manager.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes deployment using the Azure Portal GUI, which is most commonly accessed from Windows environments and is visually Windows-centric. There are no examples or instructions for deploying via CLI tools (such as Azure CLI or PowerShell), nor are there any Linux/macOS-specific guidance or screenshots. This may create friction for users who prefer or require command-line or automated deployments, especially on Linux/macOS.
Recommendations
- Add instructions and examples for deploying the ARM template using Azure CLI and/or PowerShell, with explicit notes on cross-platform compatibility.
- Include Linux/macOS-specific guidance, such as terminal commands and screenshots, or clarify that the process is identical across platforms.
- Provide links to CLI documentation and highlight automation options for non-Windows users.
Azure Netapp Files
Configure NFSv4.1 Kerberos encryption for Azure NetApp Files
...es/azure-netapp-files/configure-kerberos-encryption.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page contains notable Windows bias in the sections related to Active Directory configuration and Kerberos encryption type management. Specifically, it exclusively provides PowerShell commands (Set-ADComputer) and references Windows tools (RSAT) for managing computer accounts in Active Directory, without mentioning or providing Linux/macOS alternatives. Windows terminology and tools are introduced before any Linux equivalents, and there is no guidance for performing these AD tasks from non-Windows environments. While the NFS client configuration and mounting instructions are Linux-focused, critical steps for Kerberos setup require Windows-only tooling.
Recommendations
- Provide equivalent instructions for managing Active Directory computer accounts and Kerberos encryption types using cross-platform tools such as ldapmodify, samba-tool, or other LDAP utilities available on Linux/macOS.
- Include examples of how to set Kerberos encryption types from Linux using command-line LDAP clients.
- Clarify whether these AD configuration steps must be performed on Windows, or if there are supported alternatives for Linux/macOS administrators.
- Add explicit notes or links to documentation for Linux/macOS AD management, if available.