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 476-500 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/performance-azure-vmware-solution-datastore.md
...p-files/performance-azure-vmware-solution-datastore.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is generally neutral and covers both Windows and Linux environments, but there are subtle signs of Windows bias. Windows tools and concepts (e.g., NTFS, volume shadow copies, Storage Spaces, Windows Server disk striping) are mentioned explicitly and sometimes before or more prominently than Linux equivalents. There are direct links to Windows Server documentation for disk striping, but no equivalent step-by-step Linux example or link. Linux is referenced (e.g., LVM, xfs, fio), but practical guidance and links for Linux users are less detailed or absent.
Recommendations
- Add explicit Linux disk striping examples and links (e.g., to LVM or mdadm documentation) in the 'Next steps' section, similar to the Windows Server link.
- When discussing file system freeze/snapshot operations, provide equal detail for Linux (e.g., xfs_freeze, LVM snapshots) as for Windows (NTFS, VSS).
- Ensure that Linux tools and patterns are mentioned alongside Windows ones, and not only as secondary notes.
- Where Windows-specific tools (e.g., Storage Spaces) are mentioned, include Linux equivalents (e.g., LVM, mdadm) with equal prominence.
- Consider providing example commands or references for both Windows and Linux when discussing monitoring, striping, or snapshotting.
- Review the order of presentation to avoid always listing Windows tools or concepts before Linux ones.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/understand-data-encryption.md
...icles/azure-netapp-files/understand-data-encryption.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows/SMB and Active Directory scenarios, referencing Windows-specific tools and features (e.g., Group Policy, registry settings), and omitting concrete Linux/NFS client configuration examples. Windows terminology and tools are introduced first and in more detail, while Linux/UNIX equivalents are only briefly mentioned or not elaborated upon.
Recommendations
- Provide parallel Linux/NFS client configuration examples for encryption, including step-by-step instructions for enabling NFS Kerberos security flavors on common Linux distributions.
- Include Linux-based LDAP client configuration guidance (e.g., using sssd, nslcd, or OpenLDAP tools) for LDAP signing and StartTLS, not just Windows Active Directory scenarios.
- Balance the order of presentation: introduce SMB (Windows) and NFS (Linux/UNIX) encryption methods with equal prominence and detail.
- Reference Linux/UNIX tools and commands (e.g., kinit, mount options, ldapsearch with StartTLS) alongside Windows tools like Group Policy.
- Add troubleshooting tips and performance considerations for both Windows and Linux clients.
- Clarify which features are cross-platform and which are Windows-specific, to help non-Windows administrators understand applicability.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/lightweight-directory-access-protocol-schemas.md
...files/lightweight-directory-access-protocol-schemas.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows/Active Directory bias. All examples and configuration steps are described exclusively in the context of Microsoft Active Directory, with explicit references to Windows tools such as ADSI Edit and Windows-specific attributes. There are no examples or guidance for equivalent operations in Linux-based LDAP servers (such as OpenLDAP), nor are Linux tools or management patterns mentioned. The documentation assumes a Windows-centric environment and omits Linux parity in both conceptual and practical guidance.
Recommendations
- Include parallel examples and configuration steps for popular Linux-based LDAP servers (e.g., OpenLDAP), such as how to index attributes or manage schemas.
- Mention Linux tools (e.g., ldapmodify, ldapsearch, phpldapadmin) alongside Windows tools like ADSI Edit.
- Provide a section or callout that addresses differences and similarities between Active Directory and Linux LDAP implementations, especially regarding schema management and attribute indexing.
- Avoid assuming Active Directory as the default LDAP server; clarify that Azure NetApp Files supports standards-based LDAP and provide guidance for both Windows and Linux environments.
- Add troubleshooting tips and best practices for Linux LDAP environments, including attribute population and performance optimization.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/manage-default-individual-user-group-quotas.md
...p-files/manage-default-individual-user-group-quotas.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates subtle Windows bias by referencing SMB (a Windows protocol) and Windows-specific identifier formats (SIDs) before or more prominently than NFS (Linux/UNIX protocol) equivalents. Examples and field descriptions for quota targets are more detailed for SMB/Windows, and there are no command-line or shell examples for Linux/UNIX environments. The documentation also lacks parity in providing Linux/NFS-specific operational guidance or examples.
Recommendations
- Provide equal prominence to NFS (Linux/UNIX) and SMB (Windows) protocols in all examples and field descriptions.
- Include example commands or workflows for managing quotas using Linux/UNIX tools (e.g., CLI, shell scripts, REST API via curl, etc.), not just via the Azure Portal.
- When describing identifier formats, explain both Windows (SID) and Linux (UID/GID) formats with equal detail and provide examples for both.
- Add a section or callout for Linux administrators, outlining best practices or considerations specific to NFS and Linux environments.
- Ensure that screenshots and UI walkthroughs are balanced, showing both Windows and Linux/NFS scenarios where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/lightweight-directory-access-protocol-name-mapping.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/lightweight-directory-access-protocol-name-mapping.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively describing the process of configuring asymmetric name mapping using the Windows Active Directory Users and Computers MMC tool, without mentioning or providing equivalent instructions for performing the same operation on a Linux-based LDAP server or using cross-platform tools. The workflow and screenshots are Windows-centric, and Linux/UNIX administrators are not given guidance for non-Windows environments.
Recommendations
- Provide equivalent instructions for configuring asymmetric name mapping using common Linux LDAP management tools (such as ldapmodify, Apache Directory Studio, or command-line utilities).
- Include Linux/UNIX-focused examples and screenshots for editing LDAP attributes relevant to name mapping.
- Present both Windows and Linux methods in parallel, or at least mention Linux alternatives, to ensure parity and inclusivity for administrators managing non-Windows LDAP servers.
- Clarify that the described method is specific to Windows AD environments and direct Linux/UNIX users to appropriate resources or steps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/manage-file-access-logs.md
...articles/azure-netapp-files/manage-file-access-logs.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Windows/Powershell examples and workflows first or exclusively in several sections. The registration of the feature is shown with Azure PowerShell commands first, and the instructions for setting SACLs are detailed only for Windows, with Linux/NFS instructions being less explicit and referring to external documentation. There is also a focus on Windows tools and UI steps (e.g., right-clicking in Windows Explorer), while equivalent Linux command-line or GUI steps are missing.
Recommendations
- Provide Linux/Unix command-line examples (e.g., using setfacl or nfs4_setfacl) for setting Audit ACEs and SACLs, with step-by-step instructions similar to the Windows section.
- Present Azure CLI commands before or alongside PowerShell commands for feature registration and status checking.
- Balance the order of presentation so that Linux/NFS and Windows/SMB instructions are given equal prominence, possibly using tabs or parallel sections.
- Include screenshots or terminal output for Linux workflows where Windows screenshots are provided.
- Ensure that all procedures (enabling/disabling logs, setting ACLs) have both Windows and Linux examples, not just references to other documentation for Linux.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/lightweight-directory-access-protocol.md
...-netapp-files/lightweight-directory-access-protocol.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias by exclusively referencing Microsoft Active Directory as the only supported LDAP server, focusing on Windows-centric LDAP schemas and tools, and providing command-line examples (such as nslookup) in a Windows context first. Linux/UNIX alternatives are mentioned only minimally or as secondary options, and there are no Linux-specific configuration examples or guidance for common Linux LDAP servers (e.g., OpenLDAP).
Recommendations
- Explicitly mention that only Microsoft Active Directory is currently supported, but clarify if or when support for other LDAP servers (such as OpenLDAP) may be planned.
- Provide parallel Linux/UNIX command-line examples (e.g., using dig, ldapsearch) alongside Windows examples for querying LDAP service records and troubleshooting.
- Include a section or note about how Linux/UNIX administrators can integrate with Azure NetApp Files in environments where Active Directory is the LDAP provider, including any required schema extensions or tools.
- Balance the discussion of LDAP schemas and attributes by referencing both Windows (AD) and common Linux/UNIX LDAP schemas (such as RFC 2307 in OpenLDAP).
- Where possible, avoid presenting Windows tools or patterns first; instead, offer cross-platform guidance or alternate between Windows and Linux/UNIX approaches.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/network-attached-file-permissions-smb.md
...-netapp-files/network-attached-file-permissions-smb.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page focuses exclusively on NTFS ACLs and references only Microsoft/Windows concepts and tools. There are no examples or mentions of Linux/UNIX equivalents, such as POSIX permissions or how to interact with SMB shares from Linux systems. The only external reference is to Microsoft documentation, reinforcing a Windows-centric perspective.
Recommendations
- Include a section describing how SMB permissions interact with Linux/UNIX clients, including any differences or caveats.
- Provide examples of managing SMB file permissions from Linux systems (e.g., using smbclient, setfacl, or mount.cifs).
- Reference documentation or tools relevant to Linux/UNIX environments, such as POSIX ACLs or Samba.
- Clarify whether and how Linux/UNIX clients can view or modify NTFS ACLs on Azure NetApp Files SMB shares.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/kerberos.md
...ocs/blob/main//articles/azure-netapp-files/kerberos.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently prioritizing Windows/Active Directory terminology, tools, and workflows. Windows-specific tools (such as PowerShell, MMC, and setspn) are mentioned exclusively for managing Kerberos and SPNs, with no equivalent Linux commands or tools provided. Examples and troubleshooting steps focus on Windows environments, and Linux/UNIX scenarios are only briefly mentioned, often as afterthoughts or in notes. There are no practical Linux command examples (e.g., kinit, ktutil, klist, or how to manage keytabs/SPNs on Linux), and guidance for Linux administrators is minimal.
Recommendations
- Provide Linux/UNIX command-line examples alongside Windows/PowerShell ones (e.g., show how to use kinit, klist, ktutil, and how to create/manage keytabs and SPNs on Linux).
- Include instructions for managing Kerberos principals and keytabs in non-Active Directory KDCs (such as MIT Kerberos or Heimdal), or at least clarify that only AD is supported and provide workarounds or references.
- When describing workflows (such as SPN creation or troubleshooting), add Linux/UNIX-specific steps and tools (e.g., using ldapsearch, realm, or sssd).
- Balance terminology: introduce and explain both Windows and Linux Kerberos concepts and tools in parallel, rather than defaulting to Windows/AD-centric language.
- Add troubleshooting sections for common Linux client issues (e.g., krb5.conf misconfiguration, keytab issues, DNS problems) with relevant log file locations and diagnostic commands.
- Ensure that all configuration and workflow diagrams include both Windows and Linux perspectives where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/network-attached-file-permissions.md
...zure-netapp-files/network-attached-file-permissions.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by describing Windows SMB inheritance controls in detail (including a screenshot of the Windows interface), while providing only brief, less actionable descriptions for NFS/Linux equivalents. No Linux command-line examples or screenshots are provided, and Windows tools/patterns are mentioned first and in more depth.
Recommendations
- Add Linux/NFS command-line examples (e.g., using chmod, setfacl, getfacl) to illustrate how to manage file permissions and inheritance.
- Include screenshots or step-by-step instructions for managing NFS permissions and inheritance on Linux systems.
- Present Windows and Linux/NFS procedures in parallel, giving equal detail and prominence to both.
- Avoid referencing only Windows GUI tools; provide equivalent Linux tooling and workflows.
- Where possible, lead with a neutral or cross-platform overview before diving into OS-specific instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/manage-smb-share-access-control-lists.md
...-netapp-files/manage-smb-share-access-control-lists.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation exclusively describes Windows-based tools and workflows (Windows Explorer, Microsoft Management Console) for managing SMB share ACLs in Azure NetApp Files. There are no examples or instructions for performing these tasks from Linux or cross-platform environments, nor are any Linux tools or command-line alternatives mentioned. The documentation assumes the user is operating from a Windows environment.
Recommendations
- Add instructions or examples for viewing and managing SMB share ACLs using Linux tools such as smbclient, smbcacls, or other Samba utilities.
- Clarify whether share-level ACL management is possible from non-Windows platforms, and if not, explicitly state this limitation.
- If PowerShell or MMC are required, provide alternative guidance or workarounds for Linux or macOS users (e.g., using a Windows VM, Azure Cloud Shell, or REST APIs if available).
- Include a section comparing Windows and Linux management options for SMB ACLs, highlighting any feature gaps.
- Where screenshots are used, consider including command-line examples or outputs from cross-platform tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/mount-volumes-vms-smb.md
...//articles/azure-netapp-files/mount-volumes-vms-smb.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively covers mounting SMB volumes on Windows virtual machines, providing only Windows-specific instructions and screenshots. There are no examples or instructions for mounting SMB volumes on Linux clients, nor are Linux tools or commands mentioned. The focus is entirely on Windows environments.
Recommendations
- Add a section with instructions and examples for mounting SMB volumes on Linux virtual machines, including relevant commands (e.g., using the 'mount' command or 'cifs-utils').
- Mention Linux tools and prerequisites (such as installing cifs-utils) alongside Windows tools.
- Ensure that screenshots and step-by-step guides are provided for both Windows and Linux platforms.
- Consider rephrasing the title and description to clarify if the content is Windows-specific, or broaden the scope to include Linux.
- Present Windows and Linux instructions in parallel or in clearly separated sections to provide parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/network-attached-storage-permissions.md
...e-netapp-files/network-attached-storage-permissions.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in its coverage of SMB share permissions. It references Windows-specific tools (MMC console, Windows Explorer, 'net view') for managing and viewing SMB shares, and all screenshots and examples for SMB are from a Windows environment. There are no equivalent examples or instructions for managing SMB shares from Linux or macOS clients, nor is there mention of cross-platform tools or commands for SMB access or ACL management. The NFS section is more neutral, but the SMB section assumes a Windows-centric administrative and user environment.
Recommendations
- Include examples and screenshots of accessing and managing SMB shares from Linux and macOS clients, such as using smbclient, mount.cifs, or Nautilus.
- Document how to manage SMB share ACLs using cross-platform tools (e.g., setfacl, smbcacls, or Samba utilities) in addition to the Windows MMC console.
- When describing features like nonbrowsable shares or access-based enumeration, explain their effects and visibility from non-Windows clients.
- Avoid assuming Windows Explorer or 'net view' as the default client; mention alternative methods for discovering and connecting to SMB shares from other operating systems.
- Provide parity in examples and instructions for both Windows and Linux/macOS environments throughout the SMB sections.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/domain-name-system-concept.md
...icles/azure-netapp-files/domain-name-system-concept.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows/Active Directory DNS concepts, referencing Microsoft best practices and tools, and providing more detailed examples and screenshots for Windows environments. Linux/BIND and cross-platform considerations are mentioned but receive less detail and are often presented after Windows solutions. Tooling and troubleshooting examples are Windows-centric, with Linux alternatives included but less emphasized.
Recommendations
- Present Linux/BIND DNS server configuration and troubleshooting examples alongside or before Windows/Active Directory examples where applicable.
- Include screenshots and walkthroughs for Linux DNS management tools (e.g., Webmin, command-line BIND tools) similar to those shown for Windows DNS Manager.
- Expand on Linux/BIND-specific best practices, such as dynamic DNS, scavenging, and SRV record creation, with explicit instructions and references.
- Provide parity in troubleshooting sections, e.g., show how to view TTL and DNS record details using Linux tools (e.g., dig, host) with sample outputs and explanations.
- Balance references to Microsoft documentation with authoritative Linux/BIND documentation links.
- Clarify when recommendations are specific to Windows/Active Directory DNS versus general DNS best practices, and offer Linux/BIND equivalents where possible.
- Ensure all command-line examples (e.g., nslookup, dig) are equally detailed for both Windows and Linux, including advanced usage scenarios.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/modify-active-directory-connections.md
...re-netapp-files/modify-active-directory-connections.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-centric bias by focusing exclusively on Active Directory (a Microsoft Windows technology), referencing Windows-specific tools and concepts (such as Group Policy, 'Active Directory Sites and Services', and 'Active Directory Certificate Service'), and omitting any Linux or cross-platform command-line examples or tooling. There are no references to Linux-based directory services, nor are there instructions or examples for administrators working from Linux environments.
Recommendations
- Provide equivalent instructions or notes for Linux administrators, such as how to interact with Active Directory from Linux using tools like 'realmd', 'sssd', 'krb5', or 'ldapsearch'.
- Include examples of how to retrieve or manage LDAP certificates and connections using Linux command-line tools (e.g., openssl, ldapsearch).
- Mention cross-platform alternatives to Windows-specific tools (e.g., instead of only referencing 'Group Policy', mention how to configure LDAP signing/encryption via Linux configuration files).
- Clarify that while the service integrates with Active Directory (a Windows technology), Linux clients and administrators are supported and provide links or references to relevant Linux documentation.
- Add a section or footnotes addressing common Linux integration scenarios, such as mounting SMB shares or configuring Kerberos from Linux clients.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/network-attached-storage-protocols.md
...ure-netapp-files/network-attached-storage-protocols.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. SMB (the Windows protocol) is described as the default/primary use case for NAS, with Linux/UNIX access via Samba mentioned as a secondary, less-supported scenario. Official support is only noted for Windows and macOS SMB clients, with Linux SMB clients (Samba) explicitly called out as unsupported. Windows terminology (NTFS, SID, Active Directory, NTLM) is used throughout, and there are no Linux command-line examples or configuration walkthroughs for NFS or SMB. The only command-line example provided (rpcinfo) is for NFS, but there are no practical Linux or UNIX configuration or troubleshooting examples for either protocol. Windows tools and concepts are referenced more frequently and with greater detail than their Linux equivalents.
Recommendations
- Provide equal emphasis and detail for Linux/UNIX client scenarios, including official support statements and configuration guidance for both NFS and SMB (Samba) clients.
- Include Linux command-line examples for mounting NFS and SMB shares, troubleshooting, and managing permissions (e.g., using mount, smbclient, getfacl/setfacl, idmapd.conf).
- When discussing dual-protocol and identity mapping, include Linux/UNIX configuration steps (such as configuring /etc/idmapd.conf, nsswitch.conf, and LDAP integration) alongside Windows/Active Directory steps.
- Clarify support status for Linux SMB clients (Samba) and provide guidance or references for best-effort interoperability.
- Balance terminology by referencing both Windows (NTFS, SID, AD) and Linux (POSIX ACLs, UID/GID, LDAP) concepts equally, and avoid presenting Windows tools or patterns as the default.
- Where possible, present examples and explanations for both platforms side-by-side, rather than focusing on Windows first or exclusively.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/devtest-lab-upload-vhd-using-storage-explorer.md
...-labs/devtest-lab-upload-vhd-using-storage-explorer.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page, while describing a cross-platform tool (Azure Storage Explorer), exhibits subtle Windows bias. It references PowerShell and the 'Upload a VHD using PowerShell' workflow as the primary way to discover the storage account name, with screenshots and instructions that are PowerShell-centric. There is no mention of Linux command-line alternatives (such as Azure CLI), and the only scripting example is for PowerShell, a Windows-first technology. Additionally, the workflow for finding the storage account name is tied to a PowerShell-specific UI path, which may not be intuitive for Linux/macOS users.
Recommendations
- Provide equivalent instructions for discovering the storage account name using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Include screenshots or references to Linux/macOS environments where applicable, not just Windows/PowerShell.
- Mention and link to documentation for uploading VHDs using Azure CLI or azcopy, both of which are cross-platform command-line tools.
- Clarify that PowerShell is not required for this workflow and offer alternative methods for users on non-Windows platforms.
- Balance the 'Related content' section by including links to Linux/macOS or CLI-based guides, not just PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/network-file-system-group-memberships.md
...-netapp-files/network-file-system-group-memberships.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a Windows-centric bias by focusing on Microsoft Active Directory as the LDAP implementation, using Windows group membership logic, and providing examples and screenshots exclusively from Windows tools (e.g., ldp.exe). There are no Linux/UNIX LDAP server examples, nor are Linux-native tools (such as ldapsearch, getent, or nslcd) mentioned or demonstrated. The documentation assumes a Windows-based environment for managing NFS group memberships, which may not reflect the experience of users operating in Linux or mixed environments.
Recommendations
- Include parallel examples using Linux-based LDAP servers (such as OpenLDAP) and demonstrate how group memberships and supplemental groups are managed in those environments.
- Provide command-line examples using common Linux tools (e.g., ldapsearch, getent group, id) to show how to query group memberships and GIDs.
- Mention and explain the relevant LDAP schema attributes and group membership logic as implemented in non-Windows LDAP servers.
- Add screenshots or terminal output from Linux environments to balance the visual examples.
- Clarify that while Azure NetApp Files supports integration with Active Directory, it can also work with other LDAP implementations, and provide guidance for those scenarios.
- Avoid assuming Windows as the default or only environment by presenting both Windows and Linux procedures side by side where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/tools-reference.md
...b/main//articles/azure-netapp-files/tools-reference.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page lists a variety of tools for Azure NetApp Files, but the only automation example provided is ANFHealthCheck, which is explicitly described as a PowerShell runbook. There are no equivalent Linux/bash examples or mentions of Linux-native automation tools. This suggests a bias toward Windows and PowerShell environments, with a lack of parity for Linux users.
Recommendations
- Provide equivalent bash or Python scripts for automation tasks, especially for tools like ANFHealthCheck.
- Mention or link to Linux-native alternatives or instructions for running automation tasks on Linux (e.g., using Azure CLI, shell scripts, or Python).
- Ensure that examples and tool descriptions include both Windows and Linux usage scenarios where applicable.
- Highlight cross-platform compatibility for all tools, or note any platform-specific limitations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/devtest-lab-grant-user-permissions-to-specific-lab-policies.md
...st-lab-grant-user-permissions-to-specific-lab-policies.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page exclusively uses PowerShell (specifically Azure PowerShell cmdlets) for all examples and instructions, with no mention of Linux-native tools, Azure CLI, or Bash scripting. All code blocks and setup instructions assume a Windows/PowerShell environment, and there are no parallel examples for Linux or cross-platform users. The documentation also refers to Windows-style command prompts and omits any reference to Linux shells or tools.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell scripts, as Azure CLI is cross-platform and commonly used on Linux and macOS.
- Include Bash script examples or at least shell command lines for Linux users.
- Explicitly mention that the instructions can be followed on Linux/macOS using Azure CLI, and provide installation/setup links for those platforms.
- Where possible, use neutral language (e.g., 'command line' instead of 'PowerShell') and clarify which tools are available on which platforms.
- Add a section or note highlighting cross-platform options and best practices for both Windows and Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/understand-guidelines-active-directory-domain-service-site.md
...rstand-guidelines-active-directory-domain-service-site.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing on Windows-centric tools and workflows (such as Active Directory Sites and Services), providing detailed step-by-step instructions and screenshots for Windows GUI tools, and referencing Windows-specific terminology and resources. Linux client authentication is mentioned but not elaborated upon, and there are no Linux-based configuration examples or equivalent tooling references. The documentation assumes familiarity with Windows AD DS administration and omits Linux-native approaches for managing AD DS integration.
Recommendations
- Include equivalent Linux-based examples for AD DS integration, such as using Samba tools (e.g., samba-tool, net ads) for site and subnet management, or command-line utilities for DNS/SRV record verification.
- Provide step-by-step instructions for configuring and verifying AD DS site topology from a Linux environment, including relevant CLI commands.
- Reference cross-platform tools and approaches (e.g., LDAP utilities like ldapsearch, Kerberos tools like kinit/klist) alongside Windows tools.
- Balance the order of presentation so that Linux and Windows approaches are given equal prominence, rather than focusing on Windows tools first or exclusively.
- Add screenshots or terminal output examples from Linux environments where applicable, especially for tasks like DNS SRV record validation or Kerberos authentication testing.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/authenticate-application.md
...main//articles/azure-relay/authenticate-application.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Dotnet Heavy
Summary
The documentation page demonstrates a Windows/.NET bias by focusing exclusively on .NET (C#) code samples and a console application that is likely Windows-centric. There are no explicit Linux or cross-platform instructions for running the sample, and the primary sample is a .NET console app, which is most commonly associated with Windows environments. While Java and JavaScript samples are linked, the walkthrough and highlighted code are only for .NET. There are no shell or CLI examples for Linux users, and the instructions for running the sample do not mention Linux compatibility or steps.
Recommendations
- Provide explicit instructions for running the sample applications on Linux (e.g., using .NET Core on Linux, or Java/Node.js samples).
- Include code walkthroughs or highlighted code for Java and JavaScript samples, not just .NET.
- Add Linux-specific notes or troubleshooting tips for authentication and running the samples.
- When referencing tools or commands (e.g., Azure CLI), ensure parity in examples for both Windows (PowerShell/CMD) and Linux (Bash).
- Clarify in the 'Run the sample' section that the .NET sample can be run cross-platform if applicable, and provide any prerequisites for Linux/macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/authenticate-managed-identity.md
.../articles/azure-relay/authenticate-managed-identity.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and examples for Windows VMs, referencing Windows-specific tools (such as RDP), and omitting equivalent Linux VM or cross-platform guidance. The sample application workflow is tailored for Windows environments, with no mention of Linux setup, tools, or alternative approaches.
Recommendations
- Add parallel instructions for deploying and running the sample app on Linux VMs, including enabling managed identity and connecting via SSH.
- Reference both Windows and Linux VM creation guides, or provide a generic VM creation step with OS-agnostic follow-up instructions.
- Include Linux-specific tools and commands (e.g., SCP for file transfer, SSH for remote access) alongside RDP and Windows paths.
- Ensure that sample application instructions and code are cross-platform, or provide equivalent Linux/Unix shell commands and environment notes.
- Mention that the .NET sample can be run on Linux using .NET Core/5+/6+ if applicable, and provide build/run instructions for Linux.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/relay-api-overview.md
.../blob/main//articles/azure-relay/relay-api-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by emphasizing .NET Framework (which is Windows-only) and WCF (a Windows technology) before cross-platform or Linux-friendly options. There are no explicit Linux or cross-platform usage examples, and the only detailed integration example is for ASP.NET Core (a Microsoft stack). The documentation does not mention Linux-specific usage patterns, tools, or provide parity in examples for Linux environments.
Recommendations
- Add explicit Linux usage examples, such as how to use Azure Relay with .NET Core on Linux or Node.js on Linux.
- Include instructions or references for running the .NET Standard client on Linux, including any prerequisites or differences.
- Provide parity in integration examples, such as showing how to use the Node.js client on Linux, or integrating with popular Linux web servers (e.g., Nginx, Apache).
- Avoid prioritizing Windows-only technologies (like WCF/.NET Framework) in the documentation structure; instead, present cross-platform options first.
- Mention and link to Linux-compatible tools and patterns where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/use-dfs-n-and-dfs-root-consolidation-with-azure-netapp-files.md
...s-n-and-dfs-root-consolidation-with-azure-netapp-files.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Windows Server and its tools (DFS Management console, PowerShell, Server Manager, Windows DNS). All configuration steps, examples, and screenshots are Windows-centric, with no mention of Linux or cross-platform alternatives. There are no Linux command-line examples, nor any discussion of how non-Windows clients or administrators might interact with DFS-N or Azure NetApp Files in this context.
Recommendations
- Explicitly state that DFS Namespaces is a Windows-only technology, if that is the case, and clarify any cross-platform limitations.
- If Linux or non-Windows clients can access DFS-N namespaces (e.g., via SMB/CIFS), provide guidance or examples for mounting and interacting with DFS-N shares from Linux systems.
- If Linux-based management or configuration is possible (e.g., via Samba or other open-source DFS implementations), include equivalent Linux command-line instructions or references.
- Mention any relevant Linux tools or best practices for integrating with Azure NetApp Files SMB shares, even if DFS-N management itself is Windows-only.
- Provide a summary table or section outlining platform support and any required steps for Linux environments, or explicitly state that Linux is not supported for DFS-N management if that is the case.