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 501-525 of 896 flagged pages
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows/Active Directory bias. All configuration and indexing examples are exclusively based on Microsoft Active Directory, with detailed instructions and screenshots for Windows tools (ADSI Edit). There are no examples or guidance for equivalent LDAP schema/indexing management on Linux-based LDAP servers (such as OpenLDAP). The terminology and attribute mapping tables are also oriented toward Active Directory defaults, and Linux/UNIX LDAP server administration is not addressed.
Recommendations
- Add equivalent examples and instructions for managing LDAP schemas and attribute indexing in common Linux LDAP servers (e.g., OpenLDAP), including command-line and configuration file methods.
- Provide screenshots or code snippets for Linux tools (such as ldapmodify, slapd.conf, or LDIF files) to illustrate how to index attributes like uid and uidNumber.
- Reorganize sections to present both Windows and Linux approaches in parallel, or clearly indicate when content is specific to Active Directory.
- Expand the attribute mapping table to clarify which attributes are standard across LDAP implementations and which are specific to Active Directory.
- Include a section discussing differences and best practices for both Windows and Linux LDAP environments, especially for organizations using non-AD LDAP servers.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. When listing tools for snapshot management, PowerShell is mentioned alongside Azure CLI, REST API, and the Azure portal, but no Linux-specific command-line examples (such as Bash scripts or Linux-native tools) are provided. PowerShell is referenced explicitly, and there are no Linux shell or scripting examples. The documentation does not provide example commands for Linux environments, nor does it mention Linux-first tooling or patterns. While the documentation is generally platform-neutral in its conceptual explanations, the practical guidance and tool references lean toward Windows/PowerShell, and Linux parity is not fully achieved.
Recommendations
- Include explicit Linux/Bash command-line examples for snapshot management using Azure CLI.
- When listing tools, mention Azure CLI and Bash scripting before or alongside PowerShell, to avoid Windows-first ordering.
- Provide example scripts for both PowerShell (Windows) and Bash (Linux/macOS) in the 'Scripts' section.
- Clarify that Azure CLI is cross-platform and provide usage examples on Linux.
- Where PowerShell modules are referenced, also reference equivalent Bash/CLI usage or scripts.
- Consider adding a section or callout for Linux administrators, highlighting relevant tools and patterns.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/understand-data-encryption.md
...icles/azure-netapp-files/understand-data-encryption.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows/SMB and Active Directory scenarios, referencing Windows-specific tools and security features (such as Group Policy, registry settings, and Windows Server advisories), and omitting Linux/NFS client configuration examples or tools. SMB encryption and UNC hardening are discussed in detail before NFS/Kerberos, and LDAP security is explained mainly in the context of Microsoft Active Directory, with configuration guidance focused on Windows environments. There are no Linux or cross-platform command-line examples or references to common Linux tools for configuring or verifying encryption.
Recommendations
- Provide parallel Linux/NFS client configuration examples for enabling and verifying Kerberos encryption, including example commands (e.g., mount options, krb5.conf settings).
- Include references to Linux tools (such as kinit, mount.nfs, or sssd) and describe how to configure NFS and LDAP encryption from Linux clients.
- When discussing LDAP signing and channel binding, add guidance for configuring these features on non-Windows LDAP servers (such as OpenLDAP) and clients.
- Balance the order of presentation so that NFS/Linux scenarios are given equal prominence to SMB/Windows scenarios.
- Add troubleshooting and verification steps for both Windows and Linux clients (e.g., using tcpdump or Wireshark on Linux to inspect encrypted traffic).
- Reference relevant Linux documentation or man pages alongside Microsoft/Windows links.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/understand-volume-languages.md
...cles/azure-netapp-files/understand-volume-languages.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools (Explorer, PowerShell, Notepad, Notepad++, Windows Terminal) and workflows are often mentioned first or in greater detail than their Linux equivalents. Several sections provide detailed PowerShell and Windows-specific instructions or screenshots, while Linux tools and commands are sometimes mentioned only later or in passing. Some encoding conversion and file inspection examples are Windows-centric, with Linux alternatives appearing as secondary notes. There are also cases where Windows-specific troubleshooting steps are detailed, but equivalent Linux troubleshooting is not provided.
Recommendations
- Ensure Linux and macOS examples are presented alongside Windows examples, not just as afterthoughts.
- When introducing tools or workflows (e.g., file encoding inspection, font settings), provide Linux-native equivalents (e.g., 'file', 'iconv', 'locale', terminal font configuration) with equal detail and screenshots.
- Balance the order of presentation: alternate between Windows and Linux examples, or group by OS rather than consistently leading with Windows.
- Expand troubleshooting and configuration guidance for Linux clients (e.g., how to adjust terminal fonts, locale settings, or encoding in GNOME Terminal, Konsole, or iTerm2).
- Where PowerShell or CMD commands are given, provide equivalent bash/zsh commands for Linux/macOS.
- Include more Linux/macOS screenshots to match the number and detail of Windows screenshots.
- Explicitly mention macOS where relevant, especially since it is a common SMB/NFS client.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/understand-guidelines-active-directory-domain-service-site.md
...rstand-guidelines-active-directory-domain-service-site.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-centric bias by focusing primarily on Windows tools and patterns for Active Directory Domain Services (AD DS) site design. Windows terminology and utilities (such as Active Directory Sites and Services, nslookup, and references to Windows Server documentation) are used exclusively, with no equivalent Linux tooling or procedures provided. While Linux clients are mentioned in the context of Kerberos authentication, there are no Linux-specific configuration examples, tools, or troubleshooting steps. The documentation assumes the use of Windows-based management tools and does not address how to perform equivalent tasks from Linux environments.
Recommendations
- Provide Linux-based examples for verifying DNS SRV records (e.g., using dig or host commands) alongside nslookup.
- Include instructions or references for managing AD DS site and subnet assignments using cross-platform tools or via command-line interfaces (such as PowerShell Core on Linux, or relevant LDAP tools).
- Offer guidance for Linux administrators on integrating with AD DS, including troubleshooting connectivity and authentication from Linux clients.
- Reference open-source or cross-platform alternatives for AD DS management where possible, or clarify which steps require Windows-only tools.
- Balance the order of presentation so that Linux and Windows scenarios are treated equally, especially in authentication and connectivity sections.
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 First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a Windows-centric bias in several ways: it references Windows tools, protocols, and behaviors extensively (e.g., NTFS, Hyper-V, MS SQL Server, Windows Indexing Service, LMHOSTS, FSCTL codes, and Windows-specific features like Offline Files and Previous Versions). Windows terminology and tools are mentioned first or exclusively, while Linux or macOS equivalents are rarely referenced or are only mentioned in passing (e.g., UNIX extensions, dual protocol, or POSIX/UNIX security). There are no Linux or macOS-specific configuration examples, troubleshooting tips, or usage scenarios, and the documentation assumes familiarity with Windows administration concepts.
Recommendations
- Add Linux/macOS client configuration and usage examples for connecting to SMB shares hosted on Azure NetApp Files.
- Include references to Linux tools (e.g., smbclient, mount.cifs) and describe how to mount and interact with SMB shares from non-Windows systems.
- Document differences in behavior between Windows and Linux/macOS clients, especially regarding permissions, symlinks, and file deletion semantics.
- Provide troubleshooting guidance for common issues encountered by Linux/macOS clients (e.g., authentication, encryption, protocol compatibility).
- Balance references to Windows-specific features with equivalent or alternative workflows for Linux/macOS environments where possible.
- Clarify when features or behaviors are Windows-only and suggest alternatives or workarounds for Linux/macOS users.
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-specific instructions and screenshots. There are no examples or instructions for mounting SMB volumes on Linux clients, and Windows tools and workflows are mentioned without Linux equivalents.
Recommendations
- Add a section detailing how to mount SMB volumes on Linux clients, including command-line examples (e.g., using the 'mount' command or 'cifs-utils').
- Provide Linux-specific screenshots or terminal output where appropriate.
- Ensure that both Windows and Linux instructions are presented with equal prominence, or provide a platform selection tab.
- Mention relevant Linux tools and packages (such as cifs-utils) alongside Windows tools.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azacsnap-cmd-ref-backup.md
...articles/azure-netapp-files/azacsnap-cmd-ref-backup.md
High Priority
View Details →
Detected Bias Types
Linux First
Missing Windows Example
Linux Tools
Summary
The documentation page demonstrates a bias toward Linux environments. All example commands are shown using bash syntax, and log file locations and commands (such as grep and /var/log/messages) are specific to Linux. While there are brief mentions of Windows (e.g., NTFS volumes and 'noflush' label), there are no example commands or log file paths for Windows users. Linux tools and patterns (e.g., sync, grep, /var/log/messages) are used exclusively in examples, and Windows equivalents are not provided.
Recommendations
- Add example commands for Windows environments, using PowerShell or Command Prompt syntax where appropriate.
- Document the locations of log and result files on Windows systems, including typical paths and how to access them.
- Provide Windows-specific instructions for tasks such as flushing I/O buffers, viewing logs, and checking backup results.
- Where Linux tools (e.g., grep, cat, /var/log/messages) are referenced, include equivalent Windows commands (e.g., Get-Content, Select-String, Event Viewer) and file locations.
- Ensure that both Linux and Windows workflows are described with parity in all sections, including configuration, execution, and troubleshooting.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/application-volume-group-add-hosts.md
...ure-netapp-files/application-volume-group-add-hosts.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation includes a prominent call-out for 'PowerShell & CLI', suggesting a focus on Windows-centric tooling (PowerShell) and potentially placing it before or above Linux-native alternatives. There are no explicit Linux command-line examples, nor is there mention of Linux-specific tools or workflows. The absence of Linux examples or parity in instructions may make the documentation less accessible for Linux administrators, who are common in SAP HANA environments.
Recommendations
- Provide explicit Linux CLI (bash, az CLI) examples alongside or before PowerShell examples.
- Clarify in the 'PowerShell & CLI call-out' section that both Windows and Linux users are supported, and link to relevant Linux instructions.
- Include screenshots or terminal snippets from Linux environments where applicable.
- Ensure that any automation or scripting guidance is available in both PowerShell and bash/az CLI formats.
- Review all referenced include files (such as application-volume-group-powershell.md) to ensure Linux parity.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/application-volume-group-considerations.md
...etapp-files/application-volume-group-considerations.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias, primarily by referencing Windows-specific documentation first (e.g., linking to '/azure/virtual-machines/windows/proximity-placement-groups-portal' for PPG creation), and not providing Linux-specific examples or links. There are no explicit PowerShell commands or Windows-only tools, but the absence of Linux/CLI parity and the prioritization of Windows links suggest a Windows-centric approach.
Recommendations
- Provide equivalent Linux/CLI documentation links alongside or before Windows-specific links (e.g., link to '/azure/virtual-machines/linux/proximity-placement-groups-portal' if available).
- Include examples or references for both Windows and Linux environments when discussing deployment steps, tools, or portal navigation.
- Ensure that terminology and instructions are platform-neutral where possible, or explicitly call out differences for Linux users.
- Review all 'Next steps' and in-text links to ensure Linux users are equally supported and not directed only to Windows-centric resources.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/application-volume-group-deploy-first-host.md
...pp-files/application-volume-group-deploy-first-host.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page references a CLI & PowerShell limitation via an include, but does not provide any Linux or cross-platform CLI examples. The mention of PowerShell before CLI in the included note, and the absence of Linux-specific guidance or examples, suggests a Windows-first and PowerShell-heavy bias. There are no explicit Linux commands, tools, or screenshots, and no mention of Linux mounting procedures or shell commands, which are highly relevant for SAP HANA deployments that are often Linux-based.
Recommendations
- Provide explicit Linux shell (bash) examples for common operations, such as mounting NFS volumes or interacting with the Azure CLI.
- Ensure that any limitations or notes referencing PowerShell also mention Linux CLI equivalents, or clarify if there are none.
- Include screenshots or instructions that are relevant to Linux environments, not just Windows or PowerShell.
- Where possible, present CLI (cross-platform) instructions before or alongside PowerShell instructions to avoid a Windows-first impression.
- Add a section or callout specifically addressing Linux administrators, especially since SAP HANA is typically deployed on Linux.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/application-volume-group-disaster-recovery.md
...pp-files/application-volume-group-disaster-recovery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing PowerShell and CLI in a call-out at the top, but does not provide explicit Linux/Unix shell (bash) examples or mention Linux-native tools. The use of 'PowerShell & CLI' as a combined resource may imply a preference for Windows tooling, and there are no Linux-specific instructions or screenshots. The documentation does not address or acknowledge Linux environments, which are common for SAP HANA deployments.
Recommendations
- Provide explicit bash/Unix shell examples alongside PowerShell, especially for command-line operations relevant to Azure NetApp Files.
- Clarify in the 'PowerShell & CLI call-out' section whether the CLI examples are cross-platform and, if so, provide Linux-specific usage notes or screenshots.
- Include references to Linux-native tools or workflows where appropriate, such as using az CLI from a Linux terminal.
- Add notes or sections addressing Linux administrators, acknowledging that SAP HANA is often deployed on Linux, and ensure parity in instructions and examples.
- Where screenshots or UI references are shown, clarify that the steps are applicable regardless of the underlying OS, or provide Linux-specific context if there are differences.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/application-volume-group-manage-volumes-oracle.md
...iles/application-volume-group-manage-volumes-oracle.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page includes a call-out specifically for CLI & PowerShell, suggesting a focus on Windows and PowerShell tooling. There are no explicit Linux shell or bash examples, and the mention of PowerShell appears before any Linux-native tooling. While there is a note about Linux host reconfiguration, the operational guidance and examples are Windows-centric, lacking parity for Linux users.
Recommendations
- Add equivalent Linux/Bash CLI examples alongside or before PowerShell examples to ensure parity.
- Provide explicit instructions or references for managing volumes using Linux-native tools (e.g., Azure CLI in Bash, shell scripts).
- Balance the order of example presentation so that Linux and Windows users are equally supported.
- Clarify in the call-out or steps that all operations can be performed from both Windows and Linux environments, and provide links to relevant Linux documentation where appropriate.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/application-volume-group-manage-volumes.md
...etapp-files/application-volume-group-manage-volumes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation references a CLI & PowerShell limitation, indicating a focus on Windows and PowerShell tooling. There are no Linux-specific examples, nor are Linux-native tools or commands mentioned. The documentation does not provide parity for Linux users, and the mention of PowerShell appears before any mention of CLI, reinforcing a Windows-first perspective.
Recommendations
- Explicitly provide Linux CLI examples alongside or before PowerShell examples.
- Clarify if the CLI refers to Azure CLI, and provide Linux shell command syntax where appropriate.
- If there are limitations or differences for Linux users, document them clearly.
- Include screenshots or walkthroughs using Linux environments or terminal windows.
- Balance references to PowerShell with Bash or other common Linux shells to ensure cross-platform usability.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/application-volume-group-oracle-deploy-volumes.md
...iles/application-volume-group-oracle-deploy-volumes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page references a '[CLI & PowerShell call-out]' include at the top, suggesting a focus on Windows and PowerShell tooling. There are no explicit Linux or bash examples, nor is there mention of Linux-native tooling or command-line patterns. The only protocol guidance is generic (NFS/dNFS), and there is no step-by-step example for Linux users or mention of Linux-specific considerations. This results in a Windows-first and PowerShell-heavy bias, with missing Linux parity.
Recommendations
- Add explicit Linux/Bash CLI examples alongside or before PowerShell examples, especially in the referenced call-out include.
- Mention Linux-native tools (such as Azure CLI in Bash, or relevant shell commands) in the main workflow.
- Include screenshots or walkthroughs from a Linux admin perspective, such as mounting NFS volumes from a Linux VM.
- Clarify any OS-specific requirements or differences, especially regarding NFS/dNFS configuration on Linux.
- Ensure that all steps referencing PowerShell or Windows tools are mirrored with Linux equivalents.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-metrics.md
...icles/azure-netapp-files/azure-netapp-files-metrics.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by providing Azure PowerShell commands as the primary example for feature registration and status checking, mentioning Azure CLI only as an afterthought. There are no Linux/bash-specific examples or screenshots, and the workflow assumes familiarity with Windows-centric tooling. No Linux-native tools or command-line patterns are shown, and the ordering of examples prioritizes PowerShell over cross-platform alternatives.
Recommendations
- Provide both Azure PowerShell and Azure CLI (bash) command examples side-by-side for all feature registration and status-checking steps.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users, and provide equivalent bash syntax.
- Include screenshots or terminal snippets that reflect Linux environments where appropriate.
- Avoid assuming PowerShell as the default shell; clarify that both PowerShell and bash are supported.
- Instruct users on how to perform tasks using both Windows and Linux-native tools where relevant.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azacsnap-configure-database.md
...cles/azure-netapp-files/azacsnap-configure-database.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation provides detailed, step-by-step Linux/Unix shell examples for SAP HANA, Oracle, and IBM Db2, but for Microsoft SQL Server, it only provides Windows-specific instructions and examples (e.g., using .\azacsnap.exe and Windows shell syntax). There are no examples or guidance for running AzAcSnap or SQL Server integration on Linux, despite SQL Server being supported on Linux. The documentation also references Windows tools and patterns (such as .exe invocation and backslash path separators) for SQL Server, and does not mention or prioritize Linux alternatives or parity for SQL Server scenarios.
Recommendations
- Add explicit instructions and examples for configuring and using AzAcSnap with Microsoft SQL Server on Linux, including Linux shell commands and paths.
- Provide parity in example commands for both Windows and Linux environments for SQL Server, using appropriate syntax for each (e.g., .\azacsnap.exe for Windows, ./azacsnap for Linux).
- Mention and document any differences or requirements for SQL Server on Linux (such as service names, user permissions, and environment variables).
- Avoid assuming Windows as the default or only environment for SQL Server; present both platforms equally, or clarify when a feature is Windows-only.
- Where possible, use cross-platform language and avoid Windows-centric terminology (such as backslash path separators or .exe extensions) unless specifically required.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md
...etapp-files/azure-netapp-files-set-up-capacity-pool.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell instructions and tools, mentioning PowerShell module updates before Azure CLI, and providing PowerShell commands as the primary example for feature registration. Linux/Unix equivalents are only briefly referenced, and no explicit Linux shell or Bash examples are given.
Recommendations
- Provide Bash/Azure CLI examples alongside or before PowerShell examples for all command-line instructions.
- When referencing module updates or prerequisites, ensure parity by including both PowerShell (Windows) and Bash (Linux/macOS) instructions.
- Where PowerShell commands are shown, also show the equivalent Azure CLI or REST API commands in Bash syntax.
- Avoid assuming the user is on Windows; use neutral language and cross-platform examples.
- Explicitly mention that all steps can be performed from Linux/macOS environments using Azure CLI or REST API, and provide links or examples as appropriate.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-government.md
...b/main/articles/azure-netapp-files/azure-government.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell instructions and command tables, while omitting equivalent Linux or cross-platform shell (e.g., Bash) examples. The PowerShell section is comprehensive and appears after Azure CLI, but there is no mention of Linux-specific tools, shell environments, or guidance for users on non-Windows platforms. REST API and Azure CLI sections are present, but the CLI section does not clarify cross-platform usage or address Linux-specific considerations. The 'Next steps' also reference PowerShell-specific REST API usage.
Recommendations
- Add explicit Bash/Linux shell examples alongside PowerShell commands, especially for connecting to Azure Government.
- Clarify that Azure CLI is cross-platform and provide example commands in both Windows (CMD/PowerShell) and Linux (Bash) syntax where differences exist.
- Include notes or sections for Linux/macOS users, such as how to install and use Azure CLI or relevant tools on those platforms.
- Balance the prominence of PowerShell and CLI sections, ensuring that Linux-friendly workflows are equally detailed and discoverable.
- In 'Next steps', add links to Linux/Bash-focused guides or REST API usage from non-Windows environments.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-create-volumes-smb.md
...-netapp-files/azure-netapp-files-create-volumes-smb.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias in several ways: it provides only Windows-based instructions and screenshots for managing SMB permissions, exclusively references Windows tools (MMC, Windows File Browser, net view), and omits any Linux or cross-platform examples for accessing or managing SMB volumes. Linux SMB clients and their management tools are not mentioned, and all permission management guidance is Windows-centric.
Recommendations
- Add equivalent instructions and screenshots for managing SMB share and file permissions from Linux clients, such as using smbclient, mount.cifs, or setfacl.
- Include examples of mounting SMB volumes from Linux systems, referencing relevant commands and configuration steps.
- Mention and link to Linux tools (e.g., smbclient, cifs-utils) alongside Windows tools when discussing SMB access and management.
- Clarify that SMB volumes can be accessed from non-Windows clients and provide guidance or links for those scenarios.
- Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or provide a dedicated section for Linux users.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-performance-metrics-volumes.md
...iles/azure-netapp-files-performance-metrics-volumes.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates subtle Windows bias by referencing Windows VM sizes before Linux equivalents, linking to Windows VM sizing documentation first, and mentioning Windows binary availability for FIO before Linux. There are no explicit Linux command-line examples or Linux-specific guidance, and no example commands for either platform. The documentation also references Azure Monitor and REST API access in a platform-neutral way, but omits any Linux-specific monitoring or scripting examples.
Recommendations
- Present Linux and Windows VM sizing links in parallel or mention Linux first, as Linux is often the default for performance benchmarking.
- Provide explicit example commands for both Linux (e.g., bash shell) and Windows (e.g., PowerShell or CMD) when discussing tools like FIO, SSB, or API usage.
- Include Linux-specific guidance for installing and running benchmarking tools, such as package manager commands (e.g., apt-get install fio).
- Highlight any differences or considerations for running benchmarks on Linux vs. Windows, such as filesystem or mount options.
- Ensure that tool descriptions and recommendations do not prioritize Windows availability or usage unless there is a technical reason.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell commands (e.g., Set-ADComputer) for configuring Active Directory computer accounts, referencing Windows-only tools such as RSAT, and describing AD DS/Entra as the only supported Kerberos infrastructure. Linux is mentioned as the NFS client, but no Linux-native alternatives or cross-platform methods for managing the required AD/Kerberos configuration are provided. The order of instructions also places Windows/AD configuration steps before Linux client steps, reinforcing a Windows-centric workflow.
Recommendations
- Provide equivalent Linux-native commands (e.g., using 'ldapmodify', 'kadmin', or 'adcli') for setting Kerberos encryption types on computer accounts in Active Directory.
- Mention and link to cross-platform tools or APIs (such as Samba's 'net ads', or Python/LDAP scripts) that can be used from Linux systems to manage AD objects.
- Clarify whether non-Windows Kerberos Key Distribution Centers (KDCs) are supported, and if so, provide guidance for those environments.
- Reorder sections or provide parallel instructions so that Linux and Windows administrative tasks are presented with equal prominence.
- Explicitly state any limitations or requirements that force the use of Windows tools, and suggest workarounds or alternatives where possible.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-sdk-cli.md
...icles/azure-netapp-files/azure-netapp-files-sdk-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation lists both Azure CLI and PowerShell as supported CLI tools, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, with no mention of Linux-native tools or shell scripting examples. There are no Linux-specific instructions, nor is there any guidance for users on Linux or macOS platforms. The focus on PowerShell and lack of Linux examples or tools suggests a Windows bias.
Recommendations
- Add explicit examples or references for using Azure CLI on Linux and macOS, including installation and usage notes.
- Include bash or shell script examples for common tasks, not just PowerShell.
- Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
- If possible, mention or link to Linux package managers (apt, yum, etc.) for installing Azure CLI.
- Consider including a table or section highlighting platform compatibility for each tool.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-smb-performance.md
...ure-netapp-files/azure-netapp-files-smb-performance.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All configuration and monitoring examples use Windows-specific tools (e.g., PowerShell cmdlets like Get-SmbClientNetworkInterface, set-SmbClientConfiguration, and Windows Performance Monitor). References and links are exclusively to Windows documentation. There are no examples or guidance for Linux SMB clients, nor are Linux tools or commands mentioned. The text assumes the reader is using Windows or Hyper-V environments.
Recommendations
- Add equivalent Linux SMB client configuration and monitoring examples (e.g., using smbclient, mount.cifs, or smbtorture).
- Include Linux command-line examples for checking SMB Multichannel, RSS, and encryption support (e.g., using smbstatus, /proc/fs/cifs, or relevant sysfs entries).
- Reference Linux documentation and tools (such as Samba, cifs-utils, or Linux performance monitoring tools like iostat, ifstat, or perf).
- Provide performance tuning guidance for Linux SMB clients, including relevant sysctl or mount options.
- Clarify which recommendations are Windows-specific and which are cross-platform, and structure sections to present both Windows and Linux guidance in parallel where possible.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows/Active Directory-centric bias. It exclusively discusses integration with Active Directory Domain Services (AD DS) or Microsoft Entra Domain Services, with explicit statements that OpenLDAP or other third-party LDAP 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), and guidance for modifying LDAP server settings references Windows-specific tools (Ntdsutil.exe). There are no examples or instructions for managing POSIX attributes or LDAP integration from a Linux LDAP server perspective, and Linux tools for attribute management are not mentioned. Linux is only referenced in the context of NFS clients, not as a potential LDAP server or management environment.
Recommendations
- Clarify early in the documentation that only AD DS and Microsoft Entra Domain Services are supported, but also acknowledge the limitation and, if possible, provide a roadmap or alternatives for Linux/OpenLDAP users.
- Where attribute management is discussed, provide equivalent command-line examples (e.g., using ldapmodify or ldapadd) for environments where AD DS is managed from Linux or via scripts.
- Include a note or section explaining why OpenLDAP or other Linux-based LDAP servers are not supported, and what technical requirements or features are missing.
- If feasible, provide troubleshooting steps or references for Linux administrators who may need to interact with AD DS from Linux hosts (e.g., using Samba tools, ldapsearch, or other cross-platform utilities).
- Balance screenshots and examples by including at least one example of managing POSIX attributes using non-Windows tools, or clarify that all management must be done via Windows tools due to product limitations.