Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 451-475 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/devtest-lab-guidance-get-started.md
...icles/devtest-labs/devtest-lab-guidance-get-started.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently listing Windows-centric tools and workflows (such as PowerShell and Windows VM creation) before or instead of Linux equivalents. Examples and quickstarts for lab creation and automation focus on Windows VMs and PowerShell, with no explicit Linux or Bash alternatives provided. Artifact and tooling examples (e.g., Visual Studio, Fiddler, Active Directory domain join) are also Windows-focused, and there is a lack of parity in Linux-specific guidance or examples.
Recommendations
- Provide Linux/Bash/CLI examples alongside or before PowerShell examples for lab creation, user management, and VM deletion.
- Include quickstart links and templates for creating Linux VMs (e.g., Ubuntu, CentOS) in addition to Windows VM quickstarts.
- Mention and demonstrate Linux-friendly tools and artifacts (e.g., VS Code, Git, common Linux utilities) in artifact customization sections.
- Explicitly state that DevTest Labs supports both Windows and Linux environments, and provide balanced examples for both.
- Add guidance for joining Linux VMs to directory services (e.g., Azure AD, LDAP) where relevant.
- Ensure that automation and scripting guidance covers Bash/CLI and not just PowerShell.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/devtest-lab-vmcli.md
.../blob/main//articles/devtest-labs/devtest-lab-vmcli.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias. The first VM creation example uses a Windows image, and only afterward is a Linux (Ubuntu) example shown. Artifact examples and sample outputs reference both Windows and Linux, but Windows artifacts (e.g., windows-7zip) are highlighted in output. The section on listing artifacts gives PowerShell/Windows Cloud Shell instructions before Bash/Linux, and the PowerShell-specific escaping is explained first. There is no explicit omission of Linux examples, but Windows is often presented first or more prominently.
Recommendations
- Alternate the order of Windows and Linux examples, or provide Linux examples first in some sections.
- Include more Linux-specific artifact examples and outputs, not just Windows ones.
- Present Bash/Linux Cloud Shell instructions before PowerShell/Windows, or show both side-by-side.
- Ensure that references to connecting to VMs (SSH vs RDP) are balanced and that Linux connection methods are not secondary.
- Where possible, use neutral or parallel examples (e.g., show both a Windows and a Linux VM creation command together).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/customer-managed-keys-cross-tenant.md
...ure-netapp-files/customer-managed-keys-cross-tenant.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows a moderate Windows bias. Feature registration is presented first and primarily with Azure PowerShell examples, and only secondarily mentions Azure CLI. The initial code blocks use PowerShell, and the documentation refers to Azure portal navigation patterns that are more familiar to Windows users. There are no explicit Linux shell or Bash examples, and no mention of Linux-specific tooling or considerations. However, the main configuration and creation steps do use Azure CLI, which is cross-platform.
Recommendations
- Provide Azure CLI examples before or alongside PowerShell for feature registration and status checking.
- Explicitly mention that all CLI commands work on Linux, macOS, and Windows, and provide Bash shell command syntax where appropriate.
- Avoid assuming portal navigation patterns that are more familiar to Windows users; clarify that the Azure portal is web-based and platform-agnostic.
- Where PowerShell is used, offer equivalent Bash or shell commands if possible, or clarify that PowerShell Core is cross-platform.
- Add a section or note highlighting Linux/macOS compatibility and any OS-specific prerequisites or differences.
Azure Docs
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
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page primarily provides Azure PowerShell examples for feature registration and status checking, with Azure CLI (cross-platform) commands only mentioned in passing and not shown as explicit examples. This prioritizes Windows/PowerShell usage and omits step-by-step Linux/macOS (Bash/CLI) workflows, which may disadvantage users on non-Windows platforms.
Recommendations
- Provide explicit Azure CLI (az) command examples alongside PowerShell for all feature registration and status steps.
- Present CLI and PowerShell examples in parallel, or default to CLI first as it is cross-platform.
- Clarify that all steps can be performed on Linux/macOS using Azure CLI, and link to relevant CLI documentation.
- Ensure screenshots and UI references are not Windows-specific, or provide notes for cross-platform parity.
Azure Docs
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 first in several places (e.g., VM sizing links), mentioning Windows tools and formats (such as Azure Monitor screenshots that appear to be from Windows environments), and lacking explicit Linux command-line examples (such as FIO usage on Linux). While the tools discussed are cross-platform, the absence of Linux-specific examples or screenshots and the prioritization of Windows in links and descriptions may make Linux users feel secondary.
Recommendations
- Ensure that Linux and Windows are mentioned in parallel, or alternate which is listed first in links and descriptions.
- Provide explicit Linux command-line examples for tools like FIO, including installation and usage commands.
- Include screenshots from both Linux and Windows environments where applicable, or use neutral/OS-agnostic screenshots.
- Add a section or callout specifically for Linux users, highlighting any differences or tips.
- Balance references to Windows and Linux VM sizing documentation, or provide a combined link with clear navigation for both.
Azure Docs
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
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use Windows-specific tools (PowerShell cmdlets like Get-SmbClientNetworkInterface, set-SmbClientConfiguration), and references to monitoring and performance tools (such as Windows Performance Monitor) are exclusively Windows-centric. There are no Linux or macOS SMB client examples, nor are Linux tools or configuration patterns mentioned. Even general SMB features are discussed in the context of Windows versions and tools, with no parity for non-Windows environments.
Recommendations
- Include equivalent Linux (e.g., smbclient, mount.cifs, or relevant kernel/module settings) and macOS examples for SMB configuration, performance tuning, and monitoring.
- Provide Linux command-line examples for checking SMB Multichannel, RSS, and encryption support (e.g., using smbstatus, /proc/fs/cifs, or smbtorture).
- Mention and link to Linux/macOS documentation for SMB features, not just Windows Server/PowerShell articles.
- Describe how to monitor SMB performance on Linux (e.g., using iostat, atop, perf, or network interface statistics) alongside Windows Performance Monitor.
- Clarify which recommendations are OS-agnostic and which are specific to Windows, and provide guidance for non-Windows environments where possible.
Azure Docs
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
Summary
The documentation lists both Azure CLI and PowerShell as supported CLI tools, but PowerShell is given equal prominence to Azure CLI, despite PowerShell being primarily associated with Windows. There are no explicit Linux-specific tools, examples, or mentions of Linux shell usage (e.g., Bash), and the documentation does not clarify cross-platform compatibility for the CLI tools. No Linux-specific patterns or examples are provided.
Recommendations
- Clarify that Azure CLI is fully cross-platform and works natively on Linux, macOS, and Windows.
- Add explicit examples or notes for using Azure CLI in Bash or other Linux shells.
- Mention that PowerShell Core is available cross-platform, if relevant, and provide installation/use guidance for Linux users.
- Consider including a 'Platform compatibility' section for each tool, specifying supported operating systems.
- If possible, provide sample commands in both PowerShell and Bash syntax to ensure parity.
Azure Docs
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
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates several forms of Windows bias. In multiple sections, Windows solutions and tools (such as DFS, SMB, FSLogix, and Windows-specific SAP NetWeaver guidance) are presented before or more prominently than their Linux equivalents. There is a notable emphasis on Windows-centric technologies and tools, such as DFS Namespaces, FSLogix, and SMB, with limited or no Linux/NFS alternatives discussed in the same context. Some solution areas (e.g., Virtual Desktop Infrastructure) are almost exclusively Windows-focused, and in some cases, Linux examples are missing or less detailed.
Recommendations
- Ensure that Linux/NFS-based solutions are presented alongside Windows/SMB solutions, especially in sections like file sharing, SAP NetWeaver, and Virtual Desktop Infrastructure.
- Where Windows tools (e.g., DFS, FSLogix) are discussed, provide equivalent Linux/NFS solutions or explicitly state the Linux alternatives (such as NFS automount, autofs, or Linux-based profile/container management).
- Balance the ordering of solution sections and examples so that Linux and Windows are given equal prominence, or alternate which platform is presented first.
- For sections with heavy Windows focus (e.g., Virtual Desktop Infrastructure), add references or guidance for Linux-based VDI solutions if supported, or clarify platform limitations.
- Review all solution lists to ensure that for every Windows-centric reference, a Linux equivalent is provided where technically feasible.
Azure Docs
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 and referencing Windows tools (such as RSAT) for Active Directory configuration steps. There is no mention of Linux-native alternatives for managing AD computer accounts, and the instructions for setting Kerberos encryption types are Windows-centric. While the NFS client configuration and mounting steps are Linux-focused, all AD-related administrative tasks assume a Windows environment and tools, with no parity guidance for Linux-based AD management.
Recommendations
- Provide equivalent instructions for managing Active Directory computer accounts and Kerberos encryption types using Linux-native tools (e.g., samba-tool, ldapmodify, or adcli).
- Include examples of how to set the Kerberos encryption type for the NFS computer account from a Linux system joined to the domain.
- Mention cross-platform AD management options and clarify when Windows tools are required versus when Linux alternatives are available.
- Reorder or parallelize instructions so that Linux and Windows methods are presented together, rather than defaulting to Windows/PowerShell.
- Add a note about the limitations or requirements if certain steps can only be performed from Windows, and suggest workarounds or alternatives for Linux-only environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/devtest-lab-reference-architecture.md
...les/devtest-labs/devtest-lab-reference-architecture.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based remote desktop solutions (specifically Remote Desktop Gateway and RDP), and linking only to Windows Server documentation for remote access. There are no mentions or examples of Linux-based remote access tools (such as SSH or Linux-compatible RDP alternatives), nor are there examples or guidance for Linux VM management. The order of presentation also places Windows-centric solutions before any mention of cross-platform or Linux alternatives.
Recommendations
- Include Linux-based remote access options, such as SSH, alongside or before RDP/Remote Desktop Gateway when discussing remote connectivity to lab VMs.
- Provide examples or links for managing Linux VMs in DevTest Labs, including automation and scripting with Bash or other Linux-native tools.
- Reference cross-platform tools (e.g., Azure CLI, REST API) equally with PowerShell, and provide usage examples for both Windows and Linux environments.
- Link to documentation on securing and accessing Linux VMs (e.g., SSH key management, Linux firewall configuration) in addition to Windows-specific resources.
- Explicitly state that DevTest Labs supports both Windows and Linux VMs, and highlight any differences or considerations for each platform.
Azure Docs
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 demonstrates a Windows/Active Directory-centric bias. It exclusively references Windows-based LDAP servers (Active Directory Domain Services and Microsoft Entra Domain Services), omits support for OpenLDAP or other Linux/Unix LDAP servers, and provides configuration steps and screenshots using Windows tools (MMC snap-in, Multi-valued String Editor, Attribute Editor). Linux-specific tools or workflows for managing POSIX attributes or LDAP schemas are not mentioned, and Linux is only referenced in the context of NFS client configuration, not server-side LDAP management.
Recommendations
- Include examples and guidance for configuring POSIX attributes and LDAP schemas using common Linux tools (e.g., ldapmodify, phpldapadmin, or command-line utilities) for environments using OpenLDAP or other Unix-based LDAP servers.
- Provide parity in screenshots and step-by-step instructions for both Windows (Active Directory) and Linux (OpenLDAP) LDAP directory management.
- Clarify early in the documentation that only Microsoft LDAP directory services are supported, but also offer guidance or links for users who may be using Linux-based LDAP solutions.
- Where possible, use neutral terminology (e.g., 'LDAP server' instead of 'Windows LDAP server') and avoid assuming the use of Windows tools for attribute management.
- If OpenLDAP or other non-Microsoft LDAP servers are not supported, explain the technical reasons and suggest possible workarounds or alternatives for Linux-centric environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/configure-network-features.md
...icles/azure-netapp-files/configure-network-features.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its exclusive use of Azure PowerShell commands (e.g., Get-AzProviderFeature) for feature registration checks, with no equivalent Azure CLI (cross-platform) or Bash examples. There is also a lack of Linux- or cross-platform-specific guidance or screenshots, and the only command-line tooling referenced is PowerShell, which is most familiar to Windows users. No Linux shell or Azure CLI alternatives are provided for any procedural steps.
Recommendations
- For every PowerShell example (such as Get-AzProviderFeature), provide an equivalent Azure CLI (az feature show) command, which is cross-platform and widely used on Linux and macOS.
- Where command-line instructions are given, clarify that both PowerShell and Azure CLI can be used, and show both syntaxes where possible.
- Add screenshots or references that are not specific to the Windows UI or PowerShell terminal (e.g., avoid only showing Windows-style screenshots if CLI output is shown).
- Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI or the Azure Portal, not just from Windows.
- If any troubleshooting or scripting is discussed, provide Bash/Linux shell equivalents alongside PowerShell scripts.
- Review all procedural steps to ensure that Linux users are not left without clear, actionable instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/cross-region-replication-create-peering.md
...etapp-files/cross-region-replication-create-peering.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing Azure PowerShell commands as the primary example for feature registration and status checking, with Azure CLI (which is cross-platform and more common on Linux) only mentioned secondarily and without explicit command examples. There are no Linux-specific instructions or screenshots, and the workflow assumes use of the Azure Portal or PowerShell, both of which are more familiar to Windows users.
Recommendations
- Provide explicit Azure CLI command examples alongside PowerShell commands for all steps, not just a mention.
- List Azure CLI examples before or alongside PowerShell to avoid 'windows_first' bias.
- Include notes or examples for Linux/macOS users, such as how to copy resource IDs using CLI tools.
- Add screenshots or instructions that reflect cross-platform usage, such as using the Azure CLI in a Linux terminal.
- Where possible, clarify that all steps can be performed from any OS using the Azure CLI or Portal, not just Windows/PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/create-volumes-dual-protocol.md
...les/azure-netapp-files/create-volumes-dual-protocol.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas. Windows tools and workflows (such as the Active Directory Users and Computers MMC snap-in and Attribute Editor) are described in detail, with step-by-step instructions and screenshots, while equivalent Linux/UNIX tools or workflows for managing LDAP/posix attributes are not mentioned. The only example for managing POSIX attributes is via Windows tools. Additionally, the section on accessing the Attribute Editor is explicitly Windows-centric, and there are no Linux-based examples for managing users/groups or for interacting with the dual-protocol volume. While NFS and UNIX security styles are discussed, practical Linux-side instructions are deferred to other documents and not included here, whereas Windows procedures are embedded directly.
Recommendations
- Add equivalent Linux/UNIX instructions for managing LDAP POSIX attributes, such as using ldapmodify, ldapadd, or graphical tools like Apache Directory Studio.
- Include Linux/UNIX command-line examples for managing users and groups in LDAP, and for setting POSIX attributes.
- Provide screenshots or walkthroughs for common Linux LDAP management tools, similar to the Windows MMC examples.
- Ensure that Linux/UNIX workflows are presented alongside Windows workflows, not just referenced via links.
- Where possible, avoid assuming the administrator is using a Windows environment for directory management; offer cross-platform guidance.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/faq-smb.md
...docs/blob/main//articles/azure-netapp-files/faq-smb.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All examples, troubleshooting steps, and tool references are centered on Windows environments, such as Active Directory, Microsoft Management Console (MMC), Windows Server, and Windows-specific configuration guidance. There are no Linux or macOS examples or references, and Linux/UNIX tools or client scenarios are not mentioned, despite SMB being a cross-platform protocol. The documentation assumes the administrator is operating from a Windows perspective, omitting guidance for Linux clients or mixed environments.
Recommendations
- Add explicit sections or FAQs addressing SMB access from Linux and macOS clients, including supported distributions, SMB client versions, and any known limitations.
- Provide example commands for mounting SMB shares from Linux (e.g., using mount.cifs, smbclient, or gvfs), alongside the Windows UNC path examples.
- Include troubleshooting steps and best practices for Linux environments, such as handling permissions, character encoding, and credential management.
- Mention Linux/UNIX tools (e.g., smbclient, cifs-utils) where appropriate, and provide parity in documentation for common administrative tasks.
- Clarify any differences in feature support or behavior when accessing Azure NetApp Files SMB shares from non-Windows clients.
- If certain features are Windows-only, explicitly state this and, where possible, suggest workarounds or alternatives for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/data-plane-security.md
...in//articles/azure-netapp-files/data-plane-security.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by consistently mentioning SMB (a Windows protocol) and its features before NFS (the Linux/UNIX equivalent), especially in sections on permissions and encryption. Windows-specific terminology (ACLs, advanced permissions, inheritance flags) is used without parallel Linux/NFS examples or command-line demonstrations. There are no explicit Linux command examples or references to Linux tools, and Active Directory (a Windows-centric LDAP service) is the only directory service mentioned for LDAP integration.
Recommendations
- Provide parallel Linux/NFS command-line examples (e.g., show how to set NFS export policies or file permissions using Linux commands like chmod, setfacl, or exportfs).
- Balance the order of presentation: alternate between NFS and SMB, or present NFS examples first in some sections.
- Include references to Linux-based directory services (such as OpenLDAP) in the LDAP encryption section, or clarify if only Active Directory is supported.
- Use cross-platform terminology where possible, and clarify Windows-specific terms for non-Windows users.
- Add explicit Linux/NFS security configuration examples and best practices, not just protocol descriptions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/faq-application-resilience.md
...icles/azure-netapp-files/faq-application-resilience.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates some Windows bias, particularly in the SMB-related sections. Windows tools and workloads (e.g., FSLogix, Citrix, MS SQL Server) are mentioned exclusively or before Linux equivalents. There is explicit exclusion of Linux SQL Server from SMB Continuous Availability support. In the Boomi section, SMB is recommended for Windows VMs and NFS for Linux VMs, but the SMB mounting link is only for Windows VMs, with no direct Linux SMB example or guidance. The 'Next steps' section provides a link for mounting SMB volumes for Windows VMs, but not for Linux, and Linux is only mentioned in the context of NFS.
Recommendations
- Provide equivalent Linux examples and guidance for SMB usage, including mounting SMB volumes on Linux VMs.
- Where Windows-specific tools or workloads are listed (e.g., FSLogix, SQL Server), clarify Linux alternatives or explicitly state support status for Linux equivalents.
- In the 'Next steps' section, add links or references for mounting SMB volumes on Linux VMs, not just Windows.
- When discussing SMB Continuous Availability, clarify if and how it applies to Linux-based SMB clients, or state limitations explicitly.
- Ensure that Linux and Windows guidance are presented in parallel where possible, rather than Windows-first or Windows-only.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/manage-cool-access.md
...ain//articles/azure-netapp-files/manage-cool-access.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing Azure PowerShell commands as the primary registration method for enabling cool access, with Azure CLI (cross-platform) only mentioned secondarily in text. There are no explicit Linux/CLI command examples, and the step-by-step instructions and screenshots focus on GUI interactions typical of Windows environments. No Linux-specific tools, shell commands, or parity examples are provided.
Recommendations
- Provide Azure CLI command examples alongside (or before) PowerShell for all registration and configuration steps, including full CLI command blocks.
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide usage context for non-Windows users.
- Where GUI instructions are given, clarify that the Azure Portal is web-based and platform-agnostic, and consider including CLI alternatives for all actions.
- Add Linux shell (bash) command examples for any relevant operations, especially for scripting or automation scenarios.
- Review screenshots and terminology to ensure they are not Windows-centric (e.g., avoid references to right-clicking if not applicable in all environments).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/disable-showmount.md
...main//articles/azure-netapp-files/disable-showmount.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation primarily uses Azure PowerShell commands for all examples, with Azure CLI only mentioned in passing and without explicit command examples. There are no Linux-native or cross-platform instructions, and the workflow assumes familiarity with PowerShell and the Azure Portal, which are more common in Windows environments.
Recommendations
- Provide explicit Azure CLI command examples alongside PowerShell for all steps, not just a reference link.
- Include instructions or examples for managing the feature from a Linux shell environment, such as using Azure CLI on Linux.
- Clarify that all commands can be run from any OS where Azure CLI or PowerShell Core is available, and provide guidance for Linux/macOS users.
- Balance screenshots and UI references with CLI-based verification steps that work cross-platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/includes/smb-continuous-availability.md
...e-netapp-files/includes/smb-continuous-availability.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based workloads (Citrix, FSLogix, MSIX, SQL Server on Windows) and explicitly stating that Linux SQL Server is not supported. There are no Linux examples or equivalent Linux workloads mentioned, and the guidance around security privileges references Windows/Active Directory tools only.
Recommendations
- Clearly state the lack of Linux support up front and provide a roadmap or links for Linux users if possible.
- If Linux support is planned, mention it and provide estimated timelines or alternatives.
- Where possible, include Linux equivalents or clarify that certain features are Windows-only.
- Provide guidance or references for Linux users who may be seeking similar functionality, even if only to explain current limitations.
- Balance the documentation by mentioning both platforms where applicable, or explicitly state the Windows-only nature of the feature.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/enable-continuous-availability-existing-SMB.md
...p-files/enable-continuous-availability-existing-SMB.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows environments. All operational steps and verification commands are presented exclusively for Windows systems, using PowerShell and Windows-specific tools. There is no mention of Linux or macOS clients, nor any guidance for verifying or enabling SMB Continuous Availability from non-Windows platforms.
Recommendations
- Add instructions and verification steps for Linux and macOS clients, such as using smbstatus or mount.cifs options.
- Clarify whether SMB Continuous Availability is supported or relevant for non-Windows clients, and document any limitations.
- Provide equivalent command-line examples for Linux (e.g., using smbclient, smbstatus, or cifs-utils).
- Avoid assuming all users are on Windows; mention cross-platform considerations and tools where applicable.
- If certain features are Windows-only, explicitly state this early in the documentation.
Azure Docs
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
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by listing Windows-specific tools (robocopy) for SMB migration without mentioning Linux/Unix equivalents (such as smbclient or rsync with SMB support). Additionally, the order of tool presentation often places Windows tools before Linux alternatives, and there are no explicit Linux command examples for SMB migration, potentially disadvantaging Linux users.
Recommendations
- For SMB migration, mention Linux/Unix tools such as 'smbclient', 'mount -t cifs', or 'rsync' with SMB support alongside 'robocopy'.
- Provide example commands for both Windows (robocopy) and Linux (smbclient, mount.cifs, rsync) to ensure parity.
- When listing tools, alternate the order or group by platform (e.g., 'For Windows: robocopy; For Linux: smbclient, mount.cifs').
- Explicitly state that both Windows and Linux clients are supported for SMB migration, and link to relevant documentation for each platform.
- Consider adding a table comparing migration tools for both NFS and SMB, with columns for Windows and Linux/Unix options.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/dual-protocol-permission-behaviors.md
...ure-netapp-files/dual-protocol-permission-behaviors.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by consistently mentioning Windows/SMB/NTFS concepts and tools before their UNIX/NFS equivalents, and by providing more detail and context for Windows-related behaviors. There is a lack of concrete Linux/NFS client command examples (e.g., no explicit Linux CLI commands for managing permissions), and Windows-specific tools and terminology (e.g., 'Windows security properties tab', 'Windows RPC calls', 'Active Directory') are referenced more frequently and in greater depth than their Linux counterparts.
Recommendations
- Provide explicit Linux/NFS client command examples for managing permissions, such as using chmod, chown, and nfs4_setfacl, alongside or before Windows/SMB examples.
- Balance the explanation of permission management tools by including Linux GUI and CLI options (e.g., mention file managers or setfacl for NFSv4.x ACLs) where Windows tools (like the security properties tab) are referenced.
- When discussing name mapping and authentication, include more detail about how Linux/NFS clients interact with LDAP and other name services, not just Windows/Active Directory mechanisms.
- In tables and decision matrices, alternate the order of presentation (sometimes UNIX/NFS first, sometimes Windows/SMB) to avoid reinforcing a default Windows-first perspective.
- Add troubleshooting or usage scenarios from the perspective of Linux/NFS administrators, not just Windows/SMB admins.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/faq-nfs.md
...docs/blob/main//articles/azure-netapp-files/faq-nfs.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation is generally cross-platform, but there is a notable Windows bias in the section addressing NFS access from Windows clients. This section provides only PowerShell commands and Windows-specific mount instructions, with no equivalent Linux example. Additionally, Windows tools and patterns are mentioned exclusively in that context, and the Windows client troubleshooting appears before any Linux troubleshooting (which is absent).
Recommendations
- For every Windows-specific example (such as PowerShell commands and mount instructions), provide an equivalent Linux example (e.g., using mount command and /etc/fstab).
- In sections where Windows troubleshooting is discussed, add parallel Linux troubleshooting advice or clarify if the issue is Windows-specific.
- When referencing tools or commands, mention both Windows and Linux alternatives where applicable.
- Ensure that both Windows and Linux are treated equally in ordering and depth of examples, especially in common scenarios like mounting NFS volumes or troubleshooting client issues.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/includes/netlogon-april-2023.md
...les/azure-netapp-files/includes/netlogon-april-2023.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exclusively references the April 2023 Windows Update and its impact on Netlogon Secure Channel, without mentioning equivalent updates, tools, or considerations for Linux or non-Windows environments. There are no Linux examples or guidance for administrators managing Azure NetApp Files from Linux systems.
Recommendations
- Include information on how the Netlogon Secure Channel changes may impact Linux-based SMB clients or Samba implementations, if applicable.
- Provide guidance or references for Linux administrators, such as how to verify or troubleshoot secure channel issues from Linux systems.
- Mention any relevant updates or best practices for non-Windows environments to ensure parity and inclusivity.
- If the update is only relevant to Windows, explicitly state this and clarify the implications (or lack thereof) for Linux/Unix users.