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 776-800 of 896 flagged pages
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-solution-architectures.md
...app-files/azure-netapp-files-solution-architectures.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is structured to present Windows and SQL Server solutions before Linux equivalents in several sections, and Windows-specific tools and patterns (such as DFS Namespaces and FSLogix) are referenced without always providing Linux alternatives. While Linux workloads are well-represented, there is a tendency to mention or prioritize Windows technologies and tools, especially in file sharing, SAP, and Virtual Desktop Infrastructure contexts.
Recommendations
- Ensure Linux and Windows solutions are presented with equal prominence and in parallel where possible, rather than grouping all Windows solutions together before Linux or vice versa.
- For every Windows-specific tool or pattern mentioned (e.g., DFS Namespaces, FSLogix), include Linux/NFS alternatives and best practices, or explicitly state if there is no direct Linux equivalent.
- When referencing file sharing or backup/restore patterns, provide both SMB (Windows) and NFS (Linux) guidance and examples.
- In SAP and Virtual Desktop Infrastructure sections, clarify which solutions are Windows-only and which are cross-platform, and add Linux VDI examples if supported.
- Review the order of solution listings to avoid implicit prioritization of Windows over Linux, or alternate the order in different sections.
Create Pull Request
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, with the Azure CLI (cross-platform) option mentioned only secondarily and without a full example. There are no explicit Linux shell or command-line examples, and the only code block is PowerShell. However, the page does reference Linux-specific performance benchmarks, and there is no mention of Windows-only tools or patterns beyond the PowerShell example.
Recommendations
- Provide both Azure PowerShell and Azure CLI command examples side by side, with equal prominence and full syntax for each.
- Include Linux shell (bash) command examples where relevant, especially for tasks like feature registration or querying status.
- When listing command-line options, alternate the order (e.g., sometimes present CLI before PowerShell) or present them in parallel.
- Explicitly state that both Windows and Linux administrators can perform all tasks, and link to platform-specific guidance if available.
- Review other sections for implicit assumptions about the user's platform and ensure parity in instructions and tooling.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-solution-architectures.md
...app-files/azure-netapp-files-solution-architectures.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page generally maintains parity between Linux and Windows by providing separate, clearly labeled sections for each platform's solutions. However, there is evidence of subtle Windows bias: in several multi-platform solution areas (such as SAP NetWeaver), Windows is listed before Linux, and Windows-specific tools (like DFS Namespaces and SMB) are mentioned explicitly, sometimes without equivalent Linux alternatives or with less detail. Some sections (e.g., Virtual Desktop Infrastructure) focus almost exclusively on Windows-based solutions, with little or no mention of Linux-based VDI options.
Recommendations
- Ensure that in all multi-platform solution sections (e.g., SAP NetWeaver), Linux and Windows are presented with equal prominence, and alternate the order in which they are listed or use a neutral grouping.
- When referencing Windows-specific tools (e.g., DFS Namespaces, SMB), also mention and provide links to equivalent Linux technologies (e.g., NFS, autofs, Linux-based DFS alternatives) where applicable.
- Expand the Virtual Desktop Infrastructure section to include Linux-based VDI solutions or explicitly state if such solutions are not supported, to avoid the impression of omission.
- For each reference architecture or solution, provide both Windows and Linux implementation examples or case studies where possible.
- Review the language throughout the document to ensure that neither platform is implied as the default or primary use case.
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, with the Azure CLI (cross-platform) option mentioned only secondarily and without a concrete example. No Linux-specific tools or shell commands are shown, and the only command-line example is PowerShell. However, the page does reference Linux in the context of performance benchmarks, and does not mention any Windows-only tools or patterns beyond the PowerShell example.
Recommendations
- Provide both Azure PowerShell and Azure CLI examples side by side for feature registration, with equal prominence.
- Include explicit Linux shell (bash) command examples where relevant, especially for Azure CLI usage.
- Avoid presenting Windows-specific tools or commands first; instead, present cross-platform options or alternate between them.
- Where possible, clarify that Azure CLI commands work on all platforms (Windows, Linux, macOS).
- Consider adding a note or section for Linux administrators, especially in areas where platform-specific steps may differ.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-solution-architectures.md
...app-files/azure-netapp-files-solution-architectures.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page presents both Linux and Windows solutions, but there is a subtle Windows bias in the ordering and emphasis of content. Windows/SQL Server solutions are given a dedicated section immediately after Linux, and Windows-specific tools and patterns (such as DFS Namespaces, FSLogix, SMB, and Always-On Failover Cluster) are mentioned prominently. In SAP solutions, Windows references and tools like DFS-N are listed before or alongside Linux equivalents, sometimes with more detail or unique features. Some sections (e.g., Virtual Desktop Infrastructure) are almost exclusively Windows-focused, with little mention of Linux alternatives.
Recommendations
- Ensure Linux and Windows solutions are presented with equal prominence and detail, possibly by interleaving examples or providing parallel Linux alternatives where Windows tools (e.g., DFS, FSLogix, SMB) are discussed.
- Where Windows-specific tools or patterns are mentioned (such as DFS-N or FSLogix), include Linux equivalents (such as NFS, autofs, or sssd) and provide links to relevant documentation.
- In sections like Virtual Desktop Infrastructure, add references to Linux-based VDI solutions or clarify if the service is Windows-only.
- Review the ordering of solution sections to avoid consistently listing Windows solutions before Linux, or alternate the order in different sections.
- For SAP and other cross-platform workloads, ensure that Linux and Windows high-availability and disaster recovery patterns are described with equal depth and clarity.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation exhibits a mild Windows bias by referencing Windows-specific documentation and tools before or instead of Linux equivalents. For example, the link to 'Create a PPG using the Azure portal' points to a Windows-specific path (/azure/virtual-machines/windows/proximity-placement-groups-portal), and there is no mention of Linux-specific guidance or examples. There are no PowerShell-heavy examples or command-line snippets, but the documentation assumes a Windows-centric workflow in its references.
Recommendations
- Provide equivalent Linux documentation links alongside or before Windows links (e.g., link to /azure/virtual-machines/linux/proximity-placement-groups-portal).
- Include Linux-specific considerations or examples where relevant, especially for SAP HANA deployments which are often on Linux.
- Review all referenced documentation to ensure parity between Windows and Linux guidance.
- Avoid using Windows-specific terminology or paths as the default; use OS-neutral or dual-path references where possible.
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 and in more detail for feature registration, with the Azure CLI (cross-platform) alternative only mentioned secondarily and without a full example. There are no explicit Linux-specific examples or instructions, and the documentation does not provide parity in command-line guidance for Linux users.
Recommendations
- Provide full Azure CLI command examples alongside PowerShell, not just references or links.
- Present Azure CLI (cross-platform) and PowerShell examples together, or list CLI first to avoid Windows-first ordering.
- Where relevant, include Linux-specific considerations or examples, especially in sections referencing performance benchmarks or management tasks.
- Clarify that both Azure CLI and PowerShell are supported on multiple platforms, and provide guidance for both environments.
- If mentioning tools or commands, ensure parity by offering both Windows and Linux equivalents, or explicitly state when a step is platform-agnostic.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-solution-architectures.md
...app-files/azure-netapp-files-solution-architectures.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page provides a comprehensive list of solution architectures for Azure NetApp Files, organized by workload type. While both Linux and Windows solutions are covered, there is evidence of Windows bias in the ordering and emphasis: the introduction often lists 'Windows Apps and SQL Server' before Linux equivalents, and Windows-specific tools (such as DFS Namespaces, FSLogix, and SMB) are highlighted in several solution areas. Some sections (e.g., Virtual Desktop Infrastructure) focus almost exclusively on Windows technologies, with little mention of Linux alternatives. However, Linux workloads are well-represented in their own dedicated sections, and many SAP and HPC solutions are Linux-centric.
Recommendations
- Ensure parity in example depth and tool coverage for Linux and Windows across all sections. For example, where Windows DFS or FSLogix are mentioned, include equivalent Linux/NFS or open-source solutions if available.
- Review section ordering and introductory text to avoid always listing Windows first; alternate or group by workload type rather than OS.
- In sections like Virtual Desktop Infrastructure, explicitly mention Linux-based VDI solutions (if supported) or clarify Windows-only support.
- Where Windows-specific tools (e.g., SMB, DFS, FSLogix) are discussed, provide Linux/NFS alternatives or cross-reference to Linux-focused documentation.
- Highlight cross-platform best practices and tools that work for both Linux and Windows workloads, to reinforce Azure NetApp Files' versatility.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows-specific documentation first (e.g., linking to '/azure/virtual-machines/windows/proximity-placement-groups-portal') and not mentioning Linux equivalents or providing Linux-specific guidance for proximity placement groups or related Azure VM operations. There are no PowerShell-heavy examples or command-line snippets, but the absence of Linux parity in references and links is notable.
Recommendations
- Include links to both Windows and Linux documentation for Azure VM features such as proximity placement groups (e.g., '/azure/virtual-machines/linux/proximity-placement-groups-portal').
- Where VM or infrastructure operations are discussed, clarify that the guidance applies to both Windows and Linux VMs, or provide Linux-specific notes where relevant.
- Ensure that all referenced workflows, forms, and best practices are equally accessible and documented for Linux-based SAP HANA deployments.
- Review all cross-references and examples to ensure Linux users are not overlooked, especially in environments where SAP HANA is commonly deployed on Linux.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation exhibits a mild Windows bias by linking to Windows-specific documentation for creating proximity placement groups (PPGs) and by referencing Windows paths in URLs before any mention of Linux equivalents. There are no explicit Linux or cross-platform examples or instructions, and the only direct example for PPG creation points to a Windows-centric guide.
Recommendations
- Provide links to both Windows and Linux (or cross-platform) documentation for creating and managing proximity placement groups (PPGs). For example, include a link to the Azure CLI or Azure Portal documentation that is not Windows-specific.
- When referencing Azure documentation, avoid using Windows-specific paths (such as /azure/virtual-machines/windows/proximity-placement-groups-portal) as the only example. Instead, offer both Windows and Linux (or generic) alternatives, or use the most general documentation available.
- Explicitly mention that the procedures and requirements apply equally to both Windows and Linux SAP HANA deployments, unless there are platform-specific differences.
- If any command-line examples or scripts are added in the future, ensure parity by providing both PowerShell and Bash/Azure CLI examples.
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 moderate Windows bias by providing an Azure PowerShell example first and in detail for feature registration, with only a brief mention of the Azure CLI alternative. There are no Linux-specific examples or explicit parity in command-line instructions, and the documentation assumes familiarity with PowerShell. However, the page does reference Linux in the context of performance benchmarks, and does not mention Windows-exclusive tools or patterns elsewhere.
Recommendations
- Provide both Azure PowerShell and Azure CLI examples side-by-side for feature registration and status checking, with equal prominence and explanation.
- Include explicit Linux command-line instructions (e.g., bash/CLI) where relevant, not just references.
- Avoid assuming PowerShell as the default; clarify that both Windows and Linux users are supported.
- Where possible, add links or examples for managing large volumes from Linux environments (e.g., using Azure CLI in bash).
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-solution-architectures.md
...app-files/azure-netapp-files-solution-architectures.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is organized with a clear separation between Linux and Windows solutions, but Windows workloads and tools are often presented first or with greater detail in some sections. Windows-specific technologies (such as DFS Namespaces, FSLogix, SMB, and Windows Virtual Desktop) are highlighted, and some solution areas (like Virtual Desktop Infrastructure) focus almost exclusively on Windows scenarios. However, Linux solutions are also well-represented, especially for SAP, HPC, and OSS workloads.
Recommendations
- Ensure Linux and Windows solution sections are given equal prominence and detail, including in introductory summaries and diagrams.
- Where Windows tools (e.g., DFS Namespaces, FSLogix, SMB) are mentioned, provide equivalent Linux/NFS or open-source alternatives and reference their documentation.
- For Virtual Desktop Infrastructure, include references to Linux-based VDI solutions or clarify if only Windows is supported.
- In sections where Windows examples or tools are discussed (such as SAP NetWeaver with Windows DFS-N), add parallel Linux/NFS guidance if available.
- Review the order of presentation in mixed-OS sections to avoid consistently listing Windows first, which can imply priority.
- Where possible, add practical Linux command-line or configuration examples alongside Windows/Powershell ones, especially in technical guides linked from this page.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation exhibits a mild Windows bias by linking to Windows-specific instructions for creating proximity placement groups (PPGs) and referencing Windows documentation before or instead of Linux equivalents. There are no explicit PowerShell examples or commands, but the only direct link for PPG creation is to a Windows/portal-specific guide, and there is no mention of Linux tools or CLI-based workflows.
Recommendations
- Provide equivalent Linux-focused documentation links, such as how to create PPGs using the Azure CLI or ARM templates, not just the Azure portal (which is often shown with Windows VM examples).
- When referencing documentation for creating or managing resources (like PPGs), include both Windows and Linux VM scenarios, or use neutral, cross-platform examples.
- Explicitly mention that the procedures apply to both Windows and Linux VMs, or clarify any differences where relevant.
- Add example commands for both Azure CLI and PowerShell where appropriate, to ensure parity for Linux users.
- Review all linked documentation to ensure Linux users are not redirected to Windows-centric guides.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-solution-architectures.md
...app-files/azure-netapp-files-solution-architectures.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally maintains parity between Linux and Windows by providing separate, clearly labeled sections for each platform and a balanced set of solution references. However, in some areas, Windows examples or tools are mentioned first (e.g., 'Windows Apps and SQL Server solutions' precedes 'SAP on Azure solutions', and within SAP, Windows NetWeaver is listed before Linux), and certain Windows-specific tools (like DFS Namespaces and FSLogix) are referenced without Linux equivalents. There are no explicit PowerShell-heavy examples or missing Linux examples, but the ordering and tool mentions indicate a mild Windows bias.
Recommendations
- Ensure that Linux and Windows solutions are presented in parallel order or alternate which platform appears first in sections to avoid implicit prioritization.
- Where Windows-specific tools (e.g., DFS Namespaces, FSLogix) are mentioned, provide Linux/NFS alternatives or explicitly state when no direct Linux equivalent exists.
- For sections like SAP NetWeaver, consider listing Linux and Windows guides together or in alphabetical order.
- Highlight cross-platform tools and practices where possible, and ensure that any platform-specific guidance is balanced with equivalent guidance for the other platform.
- Review for any subtle language that may imply Windows is the default or primary use case, and adjust to reflect equal support for Linux.
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, with the Azure CLI (cross-platform) alternative only mentioned in text and not shown as a code example. The PowerShell example is given first and is formatted as a code block, while the CLI is referenced parenthetically, making it less visible to Linux/macOS users. No Linux-specific tools or shell examples are provided, and the documentation does not explicitly mention Linux workflows in configuration steps, despite referencing Linux in performance benchmarks.
Recommendations
- Provide both Azure PowerShell and Azure CLI examples as code blocks, with equal prominence and ordering (or alternate which comes first based on context).
- Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) to encourage use by non-Windows users.
- Where relevant, include Linux shell (bash) examples for common administrative tasks, especially for steps that can be performed outside of Azure Portal.
- Review other configuration and management sections for similar patterns and ensure Linux parity in examples and tool references.
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 First
Windows Tools
Summary
The documentation for Azure NetApp Files is generally cross-platform, referencing both Windows (SMB) and Linux (NFS) protocols and features. However, there is a subtle Windows bias in some areas: Windows/SMB/Active Directory features are often described first or in more detail, and Windows tools or patterns (such as Windows File Explorer, Windows client behaviors, and references to Windows-specific features like NTFS security style) are mentioned explicitly, sometimes without equivalent Linux examples or explanations. There are also several features and enhancements that are described primarily in the context of Windows environments (e.g., SMB Continuous Availability, Access-based Enumeration, non-browsable shares), with less emphasis or parallel explanation for Linux/NFS scenarios.
Recommendations
- When describing features that apply to both Windows/SMB and Linux/NFS, provide parallel examples and explanations for both platforms. For example, if describing how a feature affects Windows File Explorer, also describe the equivalent experience on Linux clients (e.g., using Nautilus, Dolphin, or command-line tools).
- Avoid listing Windows/SMB/Active Directory features first by default; alternate the order or present both together to reinforce parity.
- Where features are Windows-specific (e.g., NTFS security style, SMB Continuous Availability), explicitly state this and, where possible, mention if there is a Linux/NFS equivalent or alternative.
- For features like file access logs, non-browsable shares, and access-based enumeration, provide Linux/NFS-specific usage notes or examples, or clarify if the feature is not applicable to Linux.
- Ensure that protocol-agnostic features (e.g., backup, snapshots, quotas) include both Windows and Linux usage scenarios and client instructions.
- Where tools or client behaviors are mentioned (e.g., Windows File Explorer), also mention common Linux tools or commands (e.g., ls, mount, Nautilus) to provide a balanced perspective.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation exhibits a mild Windows bias by linking exclusively to Windows-specific Azure portal documentation for proximity placement groups (PPGs) and by referencing Windows documentation paths before or instead of Linux equivalents. There are no explicit PowerShell examples or CLI commands, but the only direct example for creating a PPG points to a Windows-specific guide, and there is no mention of Linux or cross-platform alternatives.
Recommendations
- Provide links to both Windows and Linux (or cross-platform Azure CLI) documentation for tasks such as creating proximity placement groups.
- When referencing Azure portal or command-line instructions, use neutral or cross-platform documentation paths (e.g., /azure/virtual-machines/proximity-placement-groups-portal instead of /azure/virtual-machines/windows/proximity-placement-groups-portal).
- Explicitly mention that the guidance applies to both Windows and Linux SAP HANA deployments, or clarify any platform-specific considerations.
- Include example commands or workflows using Azure CLI or ARM templates, which are platform-agnostic, alongside any portal-based instructions.
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 (Get-AzProviderFeature) for checking feature registration status, and only secondarily mentions the Azure CLI, without giving a concrete CLI example. No Linux-specific tools or shell commands are shown, and the PowerShell example is presented first, which may suggest a Windows-centric approach.
Recommendations
- Provide both Azure CLI and PowerShell command examples side by side, with equal prominence.
- Include explicit Linux shell/CLI examples (e.g., az feature show) with sample output, not just a reference link.
- When referencing tools or commands, avoid listing Windows/PowerShell first by default; alternate order or present both together.
- Where possible, add notes about cross-platform compatibility for all commands and tools mentioned.
- Consider including a table or section summarizing equivalent commands for Windows (PowerShell), Linux (Bash/CLI), and macOS.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by referencing Windows-specific resources first, such as linking to the 'Create a PPG using the Azure portal' under the Windows documentation path (/azure/virtual-machines/windows/proximity-placement-groups-portal), without mentioning or providing equivalent Linux guidance. There are no examples or instructions tailored for Linux environments, and no Linux-specific tools or patterns are referenced.
Recommendations
- Include links to both Windows and Linux versions of Azure documentation when referencing platform-specific features (e.g., proximity placement groups).
- Provide examples or instructions for creating and managing proximity placement groups and related resources using Linux tools (such as Azure CLI or Bash scripts), not just through the Azure portal or Windows-centric paths.
- Explicitly mention that the guidance applies to both Windows and Linux SAP HANA deployments, or clarify any platform-specific differences.
- Add Linux-focused best practices or considerations where relevant, especially for network configuration and VM management.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md
...etapp-files-mount-unmount-volumes-for-virtual-machines.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides both Linux and Windows instructions for mounting NFS volumes, with Linux instructions being more detailed and comprehensive. However, there are subtle biases: the Windows section refers to the Windows-specific 'Mount' command-line utility and links to Windows documentation, and the Windows mounting workflow requires first mounting the volume on a Unix/Linux VM and running chmod, which may not be intuitive for Windows-only administrators. The Linux section is more robust, but the Windows section is presented after the Linux section, and Windows-specific tools are mentioned without Linux equivalents in that context.
Recommendations
- Provide more context for Windows administrators who may not have access to a Linux/Unix VM for the chmod step, or suggest alternatives (such as configuring permissions at volume creation).
- Include a brief explanation of the differences between Linux and Windows NFS client capabilities and limitations up front, so users can make informed decisions.
- Where Windows-specific tools are mentioned (such as the 'Mount' utility), ensure Linux equivalents are also referenced in similar contexts for parity.
- Consider adding troubleshooting or best practices sections for both platforms, not just Linux.
- Clarify that the Linux mounting instructions are generally more flexible and supported, and highlight any limitations for Windows NFS clients in a summary table.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/cross-region-replication-delete.md
.../azure-netapp-files/cross-region-replication-delete.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation describes deleting Azure NetApp Files volume replications and volumes primarily through GUI instructions and screenshots that reflect a Windows-style interface (right-click context menus, dialog confirmations). There are no CLI examples (such as Azure CLI, Bash, or PowerShell), nor are Linux-specific workflows or tools mentioned. The documentation implicitly assumes a Windows environment by referencing right-click actions and GUI navigation patterns common to Windows, without providing parity for Linux users who may use different interfaces or prefer command-line operations.
Recommendations
- Add Azure CLI and/or REST API examples for deleting replications and volumes, with step-by-step instructions.
- Include screenshots or instructions for performing these actions via the Azure Portal on Linux (if any differences exist).
- Explicitly mention that the operations can be performed from any OS via the Azure Portal, and clarify any OS-specific differences.
- Provide PowerShell and Bash script examples for automation, ensuring both Windows and Linux users are supported.
- Avoid language that assumes a Windows GUI (e.g., 'right-click') and offer equivalent steps for Linux users (e.g., contextual menu access via keyboard or alternative navigation).
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by referencing Windows-specific resources first, such as linking to the Windows Azure portal documentation for creating proximity placement groups (PPGs), without mentioning or providing equivalent Linux or cross-platform instructions. There are no examples or guidance for Linux users, nor are Linux tools or workflows referenced, despite SAP HANA being commonly deployed on Linux.
Recommendations
- Provide links to both Windows and Linux documentation for tasks like creating proximity placement groups, or use cross-platform documentation where possible.
- Include explicit instructions or examples for Linux users, especially for common SAP HANA deployment scenarios.
- Reference Linux tools, commands, or Azure CLI examples alongside or before Windows-specific tools to ensure parity.
- Clarify that the guidance applies to both Windows and Linux environments, or specify any differences in workflow or requirements.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-network-features.md
...icles/azure-netapp-files/configure-network-features.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation displays a mild Windows bias. PowerShell examples and registration steps are presented before Azure CLI and REST API equivalents, and the registration workflow is described primarily using PowerShell commands. While Azure CLI and REST API instructions are present, PowerShell is often listed first or given more detail, which may disadvantage Linux users who typically use CLI or REST. There are no explicit Linux-specific examples or references to Linux tools or shell scripting patterns.
Recommendations
- Present Azure CLI examples before PowerShell, or at least in parallel, to reflect cross-platform usage.
- Expand CLI instructions to match the detail and workflow coverage given to PowerShell.
- Add explicit Linux shell (bash) usage notes or examples where relevant, especially for registration and querying steps.
- Clarify that all CLI and REST API instructions are fully supported on Linux, and provide troubleshooting tips for common Linux environments.
- Where screenshots or UI references are given, note any OS-specific behaviors or differences if applicable.
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
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by presenting the Azure PowerShell example for feature registration status before mentioning the Azure CLI alternative. The only explicit command example is for PowerShell, with the CLI option referenced parenthetically. There are no Linux-specific examples, tools, or patterns shown, though Linux is referenced in a performance benchmarking link. No Windows-only tools or patterns are otherwise discussed.
Recommendations
- Provide both Azure PowerShell and Azure CLI command examples side-by-side, or present CLI first to improve parity for Linux users.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS environments.
- Include Linux-specific operational examples or troubleshooting steps where relevant.
- Ensure that any scripts or automation guidance are available in Bash/CLI as well as PowerShell.
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 a balanced overview of features for both Windows (SMB/Active Directory) and Linux (NFS/LDAP) environments. However, there is a subtle Windows bias in some areas: Windows/SMB/Active Directory features and terminology (e.g., Windows File Explorer, NTFS, Windows client, FSLogix, Citrix, Azure VMware Solution) are sometimes mentioned first or in more detail, and Windows-centric tools and workflows (e.g., SMB Continuous Availability, Access-based Enumeration, non-browsable shares) are described with explicit references to Windows clients. Linux/NFS features are present and described, but Windows/SMB scenarios are often foregrounded, especially in features related to user access, security, and integration with enterprise environments.
Recommendations
- When describing features that apply to both SMB (Windows) and NFS (Linux), ensure that Linux/NFS examples, terminology, and client perspectives are presented with equal prominence and detail.
- Where Windows tools or workflows (e.g., Windows File Explorer, NTFS, FSLogix) are mentioned, provide equivalent Linux tools or workflows (e.g., Linux file managers, POSIX permissions, Linux VDI solutions) and describe their usage.
- Avoid phrases like 'the Windows client hides the folder...' without also mentioning the behavior on Linux/NFS clients, or clarify if the feature is Windows-only.
- For features like Access-based Enumeration and non-browsable shares, explicitly state their applicability (or lack thereof) to NFS/Linux clients, and provide Linux/NFS-specific guidance where possible.
- Review the order of protocol mentions (e.g., 'SMB, NFSv4.1, and dual-protocol') and alternate the order or use 'NFS/SMB' where appropriate to avoid always foregrounding Windows/SMB.
- Where integration with enterprise identity solutions is discussed, ensure parity in coverage between Active Directory (Windows) and LDAP/Unix identity management solutions.