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 801-825 of 896 flagged pages
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/large-volumes-requirements-considerations.md
...app-files/large-volumes-requirements-considerations.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides a PowerShell example for checking feature registration status and mentions Azure CLI as an alternative, but does not provide a direct Linux shell or Bash example. The PowerShell example is presented first, which may suggest a Windows-centric approach. No explicit Linux-only tools or patterns are referenced, and the CLI mention is generic, but the ordering and example selection indicate a mild Windows bias.
Recommendations
- Provide both Azure PowerShell and Azure CLI (Bash/shell) examples side-by-side when showing command-line instructions.
- Present Azure CLI (which is cross-platform and commonly used on Linux) examples before or alongside PowerShell examples.
- Explicitly mention that Azure CLI commands can be run in Bash or other Unix shells, and provide sample Bash command blocks.
- Where possible, include Linux-specific considerations or links, especially since performance benchmarks for Linux are referenced.
- Review all command snippets and ensure parity for both Windows and Linux users in instructions and examples.
Create Pull Request
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/restore-single-file-backup.md
...icles/azure-netapp-files/restore-single-file-backup.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation demonstrates a moderate Windows bias by presenting Azure PowerShell commands first and in detail for feature registration, with Azure CLI (cross-platform) only mentioned in passing. No Linux-specific examples, screenshots, or command-line patterns are provided, and the initial registration steps assume familiarity with PowerShell.
Recommendations
- Provide Azure CLI examples alongside PowerShell for all command-line operations, not just as a mention.
- Explicitly state that both PowerShell and CLI are supported, and clarify which is cross-platform.
- Include screenshots or terminal examples from Linux environments where applicable.
- Avoid assuming PowerShell as the default; present CLI and PowerShell examples in parallel or alternate their order.
- Add a note about platform compatibility for all command-line instructions.
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
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides extensive coverage of both Windows/SMB and Linux/NFS features, protocols, and enhancements. However, there is a notable tendency to mention Windows/SMB (e.g., Windows File Explorer, NTFS, Active Directory, SMB-specific features) before Linux/NFS equivalents in several feature descriptions. Some features and examples are described primarily in Windows terms (e.g., 'Windows client hides the folder', 'Windows File Explorer', 'NTFS security style') without always providing parallel Linux/NFS terminology or examples. There are also several references to Windows-centric tools and workflows (e.g., FSLogix, Citrix App Layering, Azure VMware Solution) that may not have direct Linux analogs.
Recommendations
- When describing features that apply to both SMB/Windows and NFS/Linux, ensure that Linux/NFS terminology and usage are mentioned alongside or before Windows/SMB terms.
- Where features are described in Windows-centric terms (e.g., 'Windows File Explorer', 'NTFS security style'), add equivalent Linux/NFS explanations (e.g., 'Linux directory listing', 'UNIX permissions') and provide examples for both platforms.
- For features that are only relevant to Windows/SMB (e.g., FSLogix, Citrix App Layering), clarify their scope and, where possible, mention if there are similar Linux/NFS solutions or explicitly state that the feature is Windows-only.
- Review the ordering of protocol mentions (e.g., 'SMB, NFSv4.1, and dual-protocol') to avoid consistently listing Windows/SMB first, which can subtly reinforce a Windows-first perception.
- Where tools or workflows are described (e.g., restoring files, managing shares), provide example commands or procedures for both Windows and Linux clients where applicable.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/snapshots-restore-file-client.md
...es/azure-netapp-files/snapshots-restore-file-client.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides both Linux (NFS) and Windows (SMB) examples for restoring files from snapshots. However, the Windows section includes additional GUI-based methods (such as using 'Previous Versions') and screenshots, while the Linux section is limited to basic command-line instructions. Windows-specific tools and patterns (GUI navigation, context menus, 'Previous Versions' tab) are described in more detail, and the Windows section is longer and more visually supported. The Linux section lacks parity in terms of advanced or alternative restoration methods (e.g., using file managers or snapshot browsing tools).
Recommendations
- Add screenshots or step-by-step instructions for restoring files using popular Linux desktop file managers (e.g., Nautilus, Dolphin) to match the Windows GUI approach.
- Include information about advanced Linux restoration options, such as using graphical snapshot browsers if available, or integrating with desktop environment features.
- Provide parity in detail and visual aids for both Linux and Windows sections to ensure equal clarity and usability.
- Mention any Linux equivalents to the Windows 'Previous Versions' feature, or clarify if such features are not available.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/large-volumes-requirements-considerations.md
...app-files/large-volumes-requirements-considerations.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a mild Windows bias by providing an Azure PowerShell example first for checking feature registration status, with the Azure CLI (cross-platform) option mentioned only secondarily and without a direct example. There are no Linux-specific examples or references to Linux tools, though the page does link to Linux performance benchmarks. No explicit Windows-only tools or patterns are otherwise present.
Recommendations
- Provide both Azure PowerShell and Azure CLI examples side-by-side, or list Azure CLI (cross-platform) first to promote parity.
- Include explicit Linux command-line examples (e.g., bash/CLI) where relevant, especially for common administrative tasks.
- Where referencing tools or commands, clarify their cross-platform compatibility and provide equivalent instructions for both Windows and Linux users.
- Consider adding a section or callout for Linux administrators if there are any platform-specific considerations or best practices.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows (SMB) client instructions before Linux (NFS) client instructions, and provides more detailed, step-by-step guidance for Windows users (including GUI and command-line options with screenshots), while the Linux section is shorter and only mentions the 'df -h' command. Windows-specific tools (File Explorer, 'dir' command) are highlighted, and the REST API section references PowerShell specifically, but does not mention Linux scripting equivalents.
Recommendations
- Present Windows and Linux client instructions in parallel or alternate the order in different sections to avoid always listing Windows first.
- Expand the Linux section to include both GUI (if applicable, e.g., GNOME Files or KDE Dolphin) and command-line options, with equivalent screenshots.
- In the REST API section, mention and provide examples for both PowerShell (Windows) and Bash/cURL (Linux/macOS) usage.
- Where Windows tools are mentioned (e.g., File Explorer, 'dir'), provide Linux equivalents (e.g., file manager properties, 'ls', 'stat') for parity.
- Ensure that all command examples and screenshots are balanced between Windows and Linux environments.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/reestablish-deleted-volume-relationships.md
...tapp-files/reestablish-deleted-volume-relationships.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation primarily uses Azure PowerShell commands for feature registration and status checking, with Azure CLI (cross-platform) only mentioned secondarily and without example commands. No Linux-specific or bash examples are provided, and the initial focus is on PowerShell, which is more familiar to Windows users.
Recommendations
- Provide Azure CLI (az) command examples alongside PowerShell examples, not just as a mention or link.
- Present CLI and PowerShell examples in parallel, or lead with CLI for better cross-platform parity.
- Explicitly note that all operations can be performed from Linux, macOS, or Windows using Azure CLI.
- Include bash shell snippets where appropriate to demonstrate Linux workflows.
- Review other sections for similar bias and ensure equal treatment of cross-platform tools.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/cross-zone-region-replication-configure.md
...etapp-files/cross-zone-region-replication-configure.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
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 (cross-platform) only mentioned secondarily in a brief note. No Linux- or bash-specific examples are given, and the initial focus is on PowerShell, which is more commonly used on Windows.
Recommendations
- Provide Azure CLI (az) command examples alongside or before PowerShell examples for all steps, especially for feature registration and status checking.
- Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI, and provide bash-friendly command snippets.
- Where possible, use generic Azure Portal instructions or cross-platform tools as the primary example, or present both PowerShell and CLI in parallel.
- Add a note clarifying that PowerShell is not required and that Linux/macOS users can use the CLI for all operations.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/cross-zone-region-replication-configure.md
...etapp-files/cross-zone-region-replication-configure.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
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 (cross-platform) only mentioned in passing. The PowerShell examples are given first and in more detail, while the CLI alternative is referenced as a link without direct command examples. There are no Linux- or Bash-specific instructions or screenshots, and the documentation assumes familiarity with PowerShell, which is more common on Windows.
Recommendations
- Provide Azure CLI command examples directly in the documentation alongside PowerShell examples, not just as a link.
- Present both PowerShell and CLI examples in parallel, or default to Azure CLI (which is cross-platform) before PowerShell.
- Include notes or instructions relevant to Linux/macOS users, such as how to install and use Azure CLI.
- Ensure screenshots and UI references do not assume a Windows environment.
- Review the documentation for other places where Windows-specific tools or terminology are used, and add Linux/macOS equivalents where appropriate.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows (SMB) client instructions before Linux (NFS) client instructions, and provides more detailed, step-by-step guidance for Windows users (including both GUI and command-line methods), while Linux instructions are more concise and limited to a single command-line example. Windows-specific tools and patterns (File Explorer, dir command) are mentioned and illustrated, while Linux alternatives are less elaborated.
Recommendations
- Present Linux and Windows client instructions in parallel or alternate the order in different sections to avoid always prioritizing Windows.
- Expand the Linux section to include both GUI (if applicable, e.g., Nautilus or other file managers) and multiple command-line methods (e.g., ls, stat, or graphical disk usage tools).
- Provide screenshots for Linux GUI tools if available, similar to the Windows File Explorer screenshot.
- Clarify that both SMB and NFS clients are equally supported and provide parity in the depth of explanation and examples.
- Include a note or table summarizing equivalent commands and tools for both platforms for quick reference.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows (SMB) client instructions before Linux (NFS) client instructions, and provides more detailed, step-by-step guidance for Windows users (including both GUI and command-line methods), while Linux instructions are more concise and limited to a single command-line example. Windows-specific tools and workflows (File Explorer, 'dir' command) are described in detail, whereas Linux alternatives are not as thoroughly covered.
Recommendations
- Present Linux and Windows client instructions in parallel or alternate the order in different sections to avoid always listing Windows first.
- Expand the Linux section to include both GUI (if applicable, e.g., GNOME Files or KDE Dolphin) and command-line methods, mirroring the detail given to Windows.
- Provide equivalent Linux command-line examples for all Windows command-line examples (e.g., show both 'dir' and 'df -h' in a side-by-side table).
- Mention relevant Linux tools and patterns (such as file manager properties dialogs) where appropriate.
- Ensure that references to REST API usage do not only mention PowerShell, but also provide examples for Bash/cURL or Python.
- Review screenshots and illustrations to ensure both platforms are visually represented equally.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/cross-zone-region-replication-configure.md
...etapp-files/cross-zone-region-replication-configure.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a Windows bias by primarily featuring Azure PowerShell commands for feature registration and status checking, with Azure CLI (cross-platform) commands mentioned only secondarily and in less detail. There are no Linux-specific examples or guidance, and the initial instructions assume familiarity with PowerShell, which is more common on Windows.
Recommendations
- Provide Azure CLI command examples alongside (or before) PowerShell examples for all steps, not just as a note.
- Explicitly mention that both PowerShell and CLI are supported on Windows, Linux, and macOS, and provide installation links for each.
- Include example shell prompts (e.g., bash) to show parity for Linux/macOS users.
- Ensure that any screenshots or UI references do not assume a Windows environment.
- Consider reordering examples to present Azure CLI first, as it is more universally cross-platform.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-data-migration-protection.md
...es/azure-netapp-files/faq-data-migration-protection.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by consistently mentioning Windows tools (such as robocopy) alongside Linux tools (such as rsync), but always listing the Windows tool second and only for SMB scenarios. There are no explicit PowerShell-heavy examples, but the documentation refers to Windows-native tools and patterns (robocopy for SMB) without providing equivalent Linux-native SMB copy tools or examples. There are no missing Linux examples for NFS, but Linux-based SMB migration options are not discussed.
Recommendations
- Include Linux-native SMB copy tools (such as smbclient, cifs-utils, or rsync with SMB mounts) as alternatives to robocopy for SMB data migration.
- Provide example commands for both Windows and Linux environments for SMB migrations, not just NFS.
- Ensure that when listing tools, both Windows and Linux options are presented together and with equal prominence.
- Consider adding a table or section comparing migration tools for both platforms, including their pros and cons.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-data-migration-protection.md
...es/azure-netapp-files/faq-data-migration-protection.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates mild Windows bias by listing Windows tools (robocopy) before Linux equivalents (rsync) when discussing SMB data migration and replication. Additionally, robocopy is the only SMB tool mentioned, which is Windows-specific, while no Linux/Unix-native SMB copy tools (such as smbclient or cifs-utils) are referenced. However, both NFS (rsync) and SMB (robocopy) tools are mentioned, and the documentation does not provide command-line examples for either, reducing the overall impact of the bias.
Recommendations
- Mention Linux/Unix-native SMB copy tools (e.g., smbclient, cifs-utils, or mount.cifs with cp/rsync) alongside robocopy to provide parity for Linux users.
- When listing tools, alternate the order (e.g., mention rsync and robocopy together, or rotate which is listed first) to avoid the perception of Windows-first bias.
- Provide brief example commands for both Windows and Linux environments to ensure equal clarity for users of both platforms.
- Explicitly state that both Windows and Linux tools are supported for SMB and NFS, and provide links to relevant documentation for each.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-data-migration-protection.md
...es/azure-netapp-files/faq-data-migration-protection.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates mild Windows bias by listing the Windows tool (robocopy) for SMB migration before mentioning Linux/Unix alternatives, and by referencing robocopy as the primary example for SMB workloads. There are no explicit Linux SMB tool examples (such as smbclient or Linux-native copy commands for SMB), and the only Linux example given is rsync for NFS. The documentation does not provide command-line examples for either platform, but the pattern of mentioning Windows tools first and exclusively for SMB suggests a subtle bias.
Recommendations
- Include Linux-native SMB migration tools (e.g., smbclient, cifs-utils, or standard cp/mv commands mounted via CIFS) alongside robocopy when discussing SMB data migration.
- Alternate the order of tool presentation (sometimes listing Linux tools first) to avoid the appearance of platform preference.
- Provide example commands for both Windows and Linux environments for common migration scenarios.
- Explicitly state that both Windows and Linux clients can access and migrate data to SMB shares, and reference documentation for both.
- Consider a table comparing migration tools across platforms (Windows, Linux, macOS) for both NFS and SMB.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows (SMB) client instructions and screenshots before Linux (NFS) client instructions, and provides more detailed step-by-step guidance for Windows users (e.g., File Explorer navigation, screenshots). Windows tools and UI patterns (File Explorer, 'dir' command) are described in detail, while the Linux section is briefer and only mentions the 'df -h' command. There is no PowerShell-heavy bias, and Linux is not omitted, but the ordering and depth favor Windows.
Recommendations
- Present Linux and Windows client instructions in parallel or alternate the order in different sections to avoid always listing Windows first.
- Provide equally detailed, step-by-step instructions and screenshots for Linux users (e.g., show terminal navigation, example 'df -h' output, and how to interpret it).
- Mention common Linux desktop environments/tools (such as GNOME Files or KDE Dolphin) for users who may use graphical interfaces, similar to File Explorer on Windows.
- Clarify that both SMB and NFS monitoring are equally supported, and consider a table comparing commands and outputs side-by-side for both platforms.
- Ensure that any references to REST API or CLI usage include example commands for both Windows and Linux shells where relevant.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-data-migration-protection.md
...es/azure-netapp-files/faq-data-migration-protection.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates mild Windows bias by listing the Windows-specific tool 'robocopy' as the primary example for SMB data migration, while only mentioning the Linux/Unix tool 'rsync' for NFS. There are no explicit PowerShell-heavy examples or missing Linux examples, but the pattern of pairing rsync with NFS and robocopy with SMB implicitly assumes Windows for SMB workloads and Linux/Unix for NFS, without mentioning cross-platform alternatives or Linux SMB tools. Additionally, robocopy is referenced before any Linux-based SMB copy tools, and no Linux-native SMB migration tools (such as smbclient or cifs-utils) are mentioned.
Recommendations
- Include Linux-native SMB copy tools (e.g., smbclient, cifs-utils, or mount.cifs with rsync/cp) as alternatives to robocopy for SMB migrations.
- Explicitly state that both rsync and robocopy are examples, and mention that cross-platform tools exist for both NFS and SMB.
- Provide example commands or links for both Windows and Linux environments for both NFS and SMB scenarios.
- Avoid implying that SMB is only for Windows and NFS is only for Linux/Unix by clarifying that both protocols can be accessed from multiple operating systems.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-data-migration-protection.md
...es/azure-netapp-files/faq-data-migration-protection.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally maintains parity between Windows and Linux by mentioning both rsync (Linux/Unix) and robocopy (Windows) as migration tools. However, in both migration-related sections, the SMB/Windows tool (robocopy) is mentioned after the NFS/Linux tool (rsync), but the phrasing 'workloads tools such as rsync' and 'workloads robocopy in the same manner' may subtly prioritize Linux tools for NFS and Windows tools for SMB. There is no explicit PowerShell or Windows-only example, but robocopy (a Windows tool) is the only SMB migration tool mentioned, with no Linux-based SMB alternatives (e.g., smbclient, cifs-utils) provided. There are no command-line examples for either platform, but the documentation could be seen as slightly Windows-biased for SMB scenarios by only mentioning robocopy.
Recommendations
- Include Linux-based SMB migration tools (e.g., smbclient, cifs-utils, or mount.cifs with cp/rsync) alongside robocopy when discussing SMB data migration.
- Provide example commands for both Windows and Linux platforms for common migration scenarios (NFS and SMB).
- Explicitly state that both Windows and Linux clients can be used for SMB migration, and list equivalent tools for each.
- Consider a table or matrix summarizing migration tools for both NFS and SMB, with platform compatibility clearly indicated.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-data-migration-protection.md
...es/azure-netapp-files/faq-data-migration-protection.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates mild Windows bias by listing the Windows tool (robocopy) before its Linux/Unix equivalent (rsync) in both migration and replication sections. Robocopy is specifically called out for SMB workloads, while rsync is mentioned for NFS. There are no explicit Linux command-line examples or references to Linux-native SMB tools (such as smbclient or cifs-utils), and no PowerShell-specific commands are present. However, both tools are mentioned, and the documentation does not exclusively focus on Windows.
Recommendations
- Alternate the order of tool mentions (e.g., sometimes list rsync before robocopy) to avoid a default Windows-first impression.
- Include Linux-native SMB tools (such as smbclient or cifs-utils) as alternatives for SMB data migration, not just robocopy.
- Provide example command lines for both Windows and Linux environments to ensure parity.
- Explicitly state that both Windows and Linux tools are supported and provide links to their documentation.
- Consider a table comparing migration tools across platforms (Windows, Linux, Mac) for both NFS and SMB.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows (SMB) client instructions before Linux (NFS) client instructions, and provides more detailed, step-by-step guidance for Windows users (including both GUI and command-line methods), while Linux instructions are more concise and only mention the 'df -h' command. Windows-specific tools and UI patterns (File Explorer, 'dir' command) are highlighted, whereas Linux coverage is limited to a single command-line example. There is also a reference to PowerShell in the REST API section, but no equivalent mention of Bash or Linux scripting.
Recommendations
- Alternate the order of Windows and Linux sections in different documentation pages, or present them in parallel to avoid consistently prioritizing Windows.
- Expand the Linux section to include both GUI (if applicable, e.g., GNOME Files or KDE Dolphin) and command-line methods, mirroring the depth of the Windows instructions.
- Provide Linux shell scripting examples for monitoring capacity, similar to the PowerShell mention in the REST API section.
- Where possible, use neutral language and structure (e.g., 'On Windows (SMB) clients...' and 'On Linux (NFS) clients...') rather than always listing Windows first.
- Include links to Linux-specific tools or documentation where PowerShell or Windows tools are referenced.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-data-migration-protection.md
...es/azure-netapp-files/faq-data-migration-protection.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation mentions both Linux (rsync) and Windows (robocopy) tools for data migration, but consistently lists the Windows tool (robocopy) after the Linux tool (rsync) and does not provide detailed examples for either. However, there is a slight bias in that robocopy (a Windows-specific tool) is highlighted for SMB workloads, while no Linux-native SMB migration tool (such as smbclient or cifs-utils) is mentioned. Additionally, while the documentation is generally cross-platform, it does not provide parity in tool recommendations for Linux users working with SMB shares.
Recommendations
- Include Linux-native SMB migration tools (e.g., smbclient, cifs-utils, or mount.cifs with cp/rsync) alongside robocopy for SMB workloads.
- Provide example commands for both Linux and Windows environments for NFS and SMB migrations.
- Explicitly state that both Linux and Windows tools are supported for both NFS and SMB, and offer at least one example for each.
- Consider listing tools in a neutral order (e.g., alphabetically or grouped by protocol) rather than by OS preference.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows (SMB) client instructions before Linux (NFS) client instructions, and provides more detailed, step-by-step guidance (including GUI and command-line) for Windows users. Windows-specific tools (File Explorer, dir command) are described in detail, while the Linux section only mentions the df command with less elaboration. There is also a reference to PowerShell in the REST API section, but no equivalent mention of Linux scripting tools.
Recommendations
- Alternate the order of Windows and Linux sections, or present them in parallel to avoid implicit prioritization.
- Provide equally detailed instructions and screenshots for Linux users, including both GUI (if applicable, e.g., GNOME Files) and command-line methods.
- Mention Linux scripting or automation tools (e.g., Bash scripts, cron jobs) in sections where PowerShell is referenced.
- Ensure parity in troubleshooting notes and caveats for both platforms.
- Where possible, use neutral language (e.g., 'On Windows, do X. On Linux, do Y.') and avoid always listing Windows first.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-data-migration-protection.md
...es/azure-netapp-files/faq-data-migration-protection.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by listing Windows-specific tools (robocopy) before their Linux equivalents (rsync) when discussing SMB and NFS data migration. The only SMB tool mentioned is robocopy, a Windows-native utility, with no Linux or cross-platform SMB alternatives provided. Additionally, the order of presentation (rsync for NFS, robocopy for SMB) subtly prioritizes Windows tools for SMB scenarios.
Recommendations
- Include Linux and cross-platform SMB migration tools (such as smbclient, cifs-utils, or rsync with SMB mounts) alongside robocopy to provide parity for Linux users.
- When listing tools, avoid always presenting Windows tools first; consider alternating order or grouping by platform.
- Provide explicit examples or references for both Windows and Linux environments for all migration scenarios, especially for SMB.
- Clarify that migration can be performed from both Windows and Linux clients, and link to relevant documentation for each platform.
- Add a table or section summarizing migration tool options for both NFS and SMB, clearly indicating which platforms they support.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows (SMB) client instructions before Linux (NFS) client instructions, and provides more detailed steps and screenshots for Windows tools (File Explorer, dir command) compared to Linux (only df -h is mentioned). Windows-specific tools and UI interactions are described in greater detail, while Linux instructions are more concise.
Recommendations
- Alternate the order of Windows and Linux sections, or present them in parallel to avoid the impression of prioritizing Windows.
- Provide equally detailed instructions and screenshots for Linux clients, including graphical tools (e.g., GNOME Disks, KDE Dolphin) if relevant.
- Mention Linux tools and commands with the same level of detail as Windows (e.g., explain how to check properties in Linux file managers, or use additional commands like lsblk, ncdu, or graphical utilities).
- Avoid presenting Windows tools and patterns first by default; consider user demographics or usage statistics to inform ordering.
- Ensure parity in troubleshooting notes and caveats for both platforms.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/large-volumes-requirements-considerations.md
...app-files/large-volumes-requirements-considerations.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a mild Windows bias by providing an Azure PowerShell example for checking feature registration status before mentioning the Azure CLI alternative. No Linux-specific examples or tools are shown, and the PowerShell example is given more prominence. However, the page does reference Linux performance benchmarks and does not include Windows-only tools or patterns elsewhere.
Recommendations
- Present Azure CLI and PowerShell examples side-by-side or with equal prominence, ideally showing CLI first as it is cross-platform.
- Explicitly mention that both Azure CLI and PowerShell are supported on Windows, Linux, and macOS.
- Where possible, provide Linux-specific operational examples (e.g., mounting NFS volumes from Linux clients) in relevant sections.
- Avoid using PowerShell-specific code blocks as the only example; always include CLI or REST API alternatives.
- If referencing performance benchmarks for Linux, consider also linking to any available Windows benchmarks for parity, or clarify if Linux is the primary supported/tested platform.