Storage
688
Total Pages
395
Linux-Friendly Pages
293
Pages with Bias
42.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
1657 issues found
Showing 826-850 of 1657 flagged pages
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-ad-ds-overview.md
...storage/files/storage-files-identity-ad-ds-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 prioritizing Windows terminology, tools, and workflows. Windows is mentioned first in client OS requirements, and all domain join and permissions management instructions reference Windows tools and concepts (such as Windows ACLs and DACLs), with no equivalent Linux examples or guidance. Troubleshooting links and mounting instructions are Windows-specific, and there is no mention of Linux command-line tools or procedures for mounting or managing Azure file shares with AD DS authentication.
Recommendations
- Provide Linux-specific examples for mounting Azure file shares with AD DS authentication, including recommended distributions and SMB client configurations.
- Include instructions or references for managing file/directory-level permissions from Linux clients, such as using setfacl or other Linux ACL tools, and clarify any limitations.
- Add troubleshooting guidance for Linux mounting errors, similar to the Windows troubleshooting link provided.
- When listing client OS requirements, present Windows and Linux options with equal prominence, or alternate their order.
- Reference both Windows and Linux domain-join procedures, or clarify how Linux clients can authenticate to AD DS if domain joining is not applicable.
- Where possible, use cross-platform terminology (e.g., 'file permissions' instead of 'Windows ACLs') and clarify which features are Windows-only.
Create Pull Request
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-auth-hybrid-cloud-trust.md
...iles/storage-files-identity-auth-hybrid-cloud-trust.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All client and server requirements, examples, and tooling are Windows-centric. Only Windows operating systems are mentioned as supported clients, and all configuration steps rely on Windows tools such as PowerShell, Active Directory cmdlets, Windows File Explorer, Group Policy, and icacls. There are no Linux or cross-platform instructions, nor any mention of Linux support or alternatives.
Recommendations
- Clearly state whether Linux clients are supported for this scenario. If not, explicitly mention the limitation.
- If Linux is supported, provide equivalent instructions for Linux clients, including required OS versions, configuration steps, and tools (e.g., using kinit, smbclient, or Kerberos utilities on Linux).
- Include Linux command-line examples (bash, shell scripts) alongside PowerShell examples where possible.
- Reference Linux tools (such as setfacl, getfacl, or Samba utilities) for managing file and directory permissions, if applicable.
- If certain features (like Group Policy or Windows File Explorer) are not available on Linux, suggest alternative approaches or clarify the limitations.
- Add a parity table or section summarizing which steps/tools are Windows-only and which are cross-platform.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-smb-protocol.md
...blob/main/articles/storage/files/files-smb-protocol.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows and PowerShell tools are referenced and exemplified more frequently and in greater detail than Linux equivalents, especially for client-side configuration. Windows-specific instructions (e.g., registry edits, PowerShell commands) are provided for enabling SMB Multichannel and configuring encryption, with no comparable Linux guidance. Windows terminology and features are referenced first or exclusively in scenarios, security, and limitations sections. Linux client configuration, troubleshooting, and advanced usage are notably absent or deferred to separate documentation.
Recommendations
- Add Linux-specific examples for configuring SMB Multichannel and advanced SMB security settings, including relevant mount options and client configuration steps.
- Where PowerShell or Windows registry edits are shown, provide equivalent Linux commands (e.g., using smb.conf, mount.cifs options, or relevant Linux tools) or explicitly state if a feature is not configurable on Linux.
- Balance scenario descriptions to include Linux-based applications and workloads, not just Windows-based ones.
- When referencing client configuration (such as enabling specific encryption ciphers), include Linux (and macOS) instructions alongside Windows/PowerShell.
- In limitations and feature support sections, clarify which features or settings have different behaviors or requirements on Linux clients.
- Ensure that cross-platform parity is maintained in all code tabs and example sections, not just in the 'Next steps' links.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-introduction.md
...n/articles/storage/files/storage-files-introduction.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows tools and patterns (such as Azure File Sync, PowerShell, and Active Directory) are mentioned more frequently and are often introduced before their Linux equivalents. The 'Next steps' section lists Windows mounting instructions before Linux and macOS. PowerShell is highlighted as a primary scripting tool, while Linux-specific tools or scripting examples are not mentioned. There are also references to Windows-centric features (e.g., Azure File Sync, FSLogix, AD DS integration) without equivalent Linux-focused alternatives or guidance.
Recommendations
- Ensure Linux and macOS instructions/examples are presented alongside or before Windows examples, especially in introductory and 'Next steps' sections.
- Include Linux-native tooling (e.g., shell scripts, mount.cifs, mount.nfs) and scripting examples in the 'Scripting and tooling' section, not just PowerShell and Azure CLI.
- Highlight Linux-compatible features and workflows (such as NFS support, Linux authentication options) with equal detail as Windows features like Azure File Sync and AD DS.
- Provide Linux-focused use cases and video resources, similar to those provided for Windows (e.g., FSLogix).
- Mention cross-platform management tools and clarify when a feature is Windows-only or has Linux/macOS equivalents.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-assign-share-level-permissions.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-assign-share-level-permissions.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows concepts (such as Windows ACLs), recommending Windows-based patterns (Active Directory, Windows ACLs), and providing PowerShell examples. There is no mention of Linux/Unix equivalents for file-level permissions, nor guidance for users managing Azure Files from Linux clients. The documentation assumes a Windows-centric environment for both identity and access management.
Recommendations
- Include explicit guidance for Linux clients, such as how to mount and access Azure Files from Linux using SMB or NFS (where supported), and how permissions are handled in those scenarios.
- Discuss the limitations or differences in file-level permission enforcement when accessing Azure Files from Linux systems, and provide best practices for Linux administrators.
- Provide CLI and scripting examples that are platform-agnostic or include bash/shell scripts where possible, not just PowerShell.
- Clarify whether and how Linux-based identity providers (such as LDAP or Kerberos on Linux) can integrate with Azure Files, or explicitly state if such scenarios are unsupported.
- Balance references to Windows ACLs with explanations of how access control works (or does not work) for non-Windows clients.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-migration-overview.md
...cles/storage/files/storage-files-migration-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a clear Windows bias. Migration tools and examples are predominantly Windows-centric, with extensive mention of Windows Server, RoboCopy, Azure File Sync, and NTFS/ACLs. Linux is only briefly mentioned, with no detailed migration guides or examples provided for Linux users. The recommended tools and migration paths are almost exclusively tailored for Windows environments, and Windows terminology (e.g., NTFS permissions, SIDs, DACLs) is used throughout without Linux equivalents.
Recommendations
- Provide equivalent Linux migration examples and guides, especially for common scenarios such as migrating from Linux SMB servers or NAS devices using Linux.
- Include Linux-native tools (e.g., rsync, cifs-utils, smbclient) in the migration toolbox, and discuss their capabilities and limitations with respect to Azure file shares.
- Balance the order of presentation so that Linux and Windows options are given equal prominence in tables and tool recommendations.
- Explain file permission and metadata mapping for Linux (e.g., POSIX ACLs, ownership, timestamps) and how they are preserved or mapped in Azure file shares.
- Add detailed step-by-step migration guides for Linux environments, similar to those provided for Windows (e.g., mounting Azure file shares on Linux, copying data, preserving metadata).
- Clarify limitations or special considerations for Linux users, such as differences in metadata support or authentication methods.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-migration-nas-cloud-databox.md
...age/files/storage-files-migration-nas-cloud-databox.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias throughout the migration process. All file transfer examples and instructions rely exclusively on Windows Server and the RoboCopy tool, with no mention of Linux-based alternatives or guidance for environments where Windows is not available. Windows-specific tools, patterns, and terminology (e.g., mounting shares on Windows, using DFS-N, Windows Server QoS, and RoboCopy switches) are used exclusively or introduced before any Linux equivalents (which are absent). There are no examples or instructions for performing the migration from Linux systems, nor are Linux tools (such as rsync or smbclient) discussed.
Recommendations
- Add parallel Linux-based migration instructions, including examples using rsync, smbclient, or other common Linux tools for copying data to DataBox SMB shares and Azure file shares.
- Include guidance on mounting Azure file shares from Linux (e.g., using cifs-utils or NFS where supported), with step-by-step commands.
- Provide sample scripts or command lines for Linux environments to perform both the initial bulk copy and the incremental/catch-up copy phases.
- Discuss authentication and authorization considerations for Linux clients, including integration with Kerberos, AD, or local credentials.
- Reference troubleshooting steps and performance tuning tips relevant to Linux-based file copy tools.
- Ensure that all phases (planning, copying, cut-over, troubleshooting) include Linux parity, not just Windows-centric approaches.
- Where Windows-specific features (like DFS-N or NTFS ACLs) are discussed, note Linux equivalents or workarounds, or clearly state any limitations.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/data-management/komprise-quick-start-guide.md
...partners/data-management/komprise-quick-start-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric concepts and tools (e.g., SMB/CIFS, Azure Files, DFS, DNS server reconfiguration), referencing Windows-oriented network monitoring tools, and omitting explicit Linux/NFS examples or Linux command-line instructions. There is little to no mention of Linux-specific migration scenarios, tools, or best practices, and the documentation assumes familiarity with Windows patterns.
Recommendations
- Add explicit Linux/NFS migration examples, including how to add NFS shares as sources and destinations, and any protocol-specific considerations.
- Include Linux command-line examples for mounting Azure Files or Blob Storage (e.g., using cifs-utils, blobfuse, or azcopy on Linux).
- Mention Linux/Unix equivalents for network and performance monitoring (e.g., iperf, nload, iftop, netstat, atop) alongside Windows/third-party tools.
- Describe how to update Linux mount points (e.g., /etc/fstab) and NFS exports for cutover, not just DNS/DFS changes.
- Clarify any differences in permissions, ACLs, or symbolic link handling between Windows (SMB) and Linux (NFS) environments.
- Ensure screenshots and workflow steps are platform-agnostic or provide parallel instructions for both Windows and Linux environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-migration-robocopy.md
...cles/storage/files/storage-files-migration-robocopy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows environments. It exclusively uses RoboCopy, a Windows-only tool, for migration and provides only Windows-based instructions and examples. Linux is mentioned as a possible source, but no Linux-native migration tools or examples are provided. The process assumes the use of a Windows machine as an intermediary, and all mounting and authentication guidance is Windows-centric. There are no Linux or cross-platform alternatives or parity in the migration workflow.
Recommendations
- Provide equivalent Linux-based migration instructions using tools such as rsync, smbclient, or AzCopy (which is cross-platform).
- Include Linux command-line examples for mounting SMB shares and performing file transfers.
- Explicitly describe migration routes that use Linux servers as the intermediary, not just Windows.
- Mention and compare Linux-native tools for SMB file copying, and discuss their pros/cons relative to RoboCopy.
- Ensure that all troubleshooting and optimization advice includes Linux scenarios and tools.
- Add a section or callout for cross-platform or Linux-only environments, outlining supported migration patterns.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-planning.md
.../main/articles/storage/files/storage-files-planning.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows operating systems and tools are mentioned first or exclusively in several sections, such as the recommended OS list, authentication methods, and networking strategies. Azure File Sync, a Windows Server-only solution, is highlighted as the primary caching option. PowerShell and Windows-centric management patterns are referenced, while Linux-specific examples and tools are either missing or mentioned secondarily. There is a lack of parity in practical Linux guidance, especially regarding mounting, authentication, and backup/restore workflows.
Recommendations
- Ensure Linux and macOS are mentioned alongside Windows in all relevant sections, especially in OS recommendations and protocol support.
- Provide explicit Linux (and macOS, if applicable) examples for mounting, authentication, and backup/restore workflows, not just references to Windows tools or PowerShell.
- When discussing Azure File Sync or other Windows-only features, clearly state the lack of Linux support and suggest alternative approaches for Linux environments.
- Balance the order of presentation so that Linux and Windows are given equal prominence (e.g., alternate which OS is listed first, or use alphabetical order).
- Include references to Linux-native tools (such as mount.cifs, mount.nfs, or relevant CLI commands) and provide links to Linux-specific documentation where available.
- Where possible, add practical Linux-focused scenarios or case studies to demonstrate parity and applicability.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/data-management/atempo-quick-start-guide.md
...d-partners/data-management/atempo-quick-start-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by focusing exclusively on Windows-based migration scenarios, particularly using SMB/CIFS shares from Windows file servers as the source. There are no examples or guidance for Linux-based file servers (e.g., NFS shares), nor are Linux tools or workflows mentioned. Additionally, when discussing network monitoring tools, only Windows-centric or commercial solutions are listed, with no mention of common Linux/open-source alternatives.
Recommendations
- Add parallel examples for migrating from Linux file servers, such as using NFS shares as the source storage.
- Include instructions and screenshots for configuring Miria to connect to Linux/NFS sources.
- List open-source and Linux-friendly network monitoring tools (e.g., iftop, nload, vnStat, Netdata) alongside the commercial/Windows options.
- Use neutral language and ordering (e.g., 'Windows or Linux file servers') rather than defaulting to Windows-first.
- Clarify platform support and provide links or references to documentation for Linux deployments where applicable.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-migration-server-hybrid-databox.md
...files/storage-files-migration-server-hybrid-databox.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows Server as the source system, explicitly requiring Windows Server 2012 R2 or newer for Azure File Sync installation and migration. All migration steps, examples, and tooling (notably Robocopy) are Windows-specific, with no mention of Linux-based servers, Linux tools, or cross-platform alternatives. There are no examples or guidance for Linux users, and the documentation assumes a Windows-centric environment throughout.
Recommendations
- Add a section or callout clarifying support (or lack thereof) for Linux-based file servers and migration scenarios.
- If Azure File Sync does not support Linux, provide clear guidance and alternative migration paths for Linux/NAS users, linking to relevant documentation.
- Where file copy tools are discussed (e.g., Robocopy), mention Linux equivalents (such as rsync or scp) and explain their applicability or limitations in this context.
- Include a migration matrix or overview table at the start, indicating which OS/platforms are supported for each migration path.
- If possible, provide Linux-based examples or scripts for scenarios where Linux servers are involved, or explicitly state that this guide is Windows-only.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-scale-targets.md
.../articles/storage/files/storage-files-scale-targets.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias, particularly in the Azure File Sync sections. It exclusively references Windows Server as the supported platform for the Azure File Sync agent, with no mention of Linux support or alternatives. Performance guidance and metrics are framed entirely around Windows Server environments, and there are no Linux-based examples or considerations for Linux file servers. Additionally, the documentation refers to Windows-specific tools and patterns (e.g., Windows Server, Windows disk configuration) without providing Linux equivalents or guidance for cross-platform scenarios.
Recommendations
- Explicitly state platform support for Azure File Sync, including whether Linux is supported or not. If not, provide a rationale or roadmap.
- If Azure File Sync is Windows-only, consider mentioning alternative synchronization or backup solutions for Linux clients.
- Include performance considerations and configuration guidance for Linux SMB/NFS clients where relevant, especially in sections discussing client behavior and network performance.
- Provide parity in examples and recommendations for both Windows and Linux environments throughout the documentation.
- Reference Linux tools and best practices for managing Azure Files (e.g., using mount.cifs, NFS utilities, or rsync for sync scenarios) alongside Windows tools.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-multiple-forests.md
...orage/files/storage-files-identity-multiple-forests.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias. All examples, tools, and instructions are centered around Windows environments, such as using Active Directory Domains and Trusts console, PowerShell commands, icacls, net use, and klist from a Windows command prompt. There are no examples or guidance for Linux clients or administrators, nor are Linux-compatible tools or workflows mentioned. The documentation assumes a Windows-centric approach throughout.
Recommendations
- Include equivalent instructions and examples for Linux clients, such as how to mount Azure Files SMB shares from Linux using cifs-utils and how to handle Kerberos authentication from Linux.
- Mention and provide examples for Linux tools (e.g., smbclient, mount.cifs, setfacl) where applicable, alongside Windows tools like icacls and net use.
- Add PowerShell and non-PowerShell alternatives for administrative tasks, and clarify which steps are Windows-only.
- Explicitly state platform limitations (e.g., if certain features are only available on Windows) and provide guidance or workarounds for Linux environments.
- Reorganize sections to present both Windows and Linux approaches in parallel, or clearly label Windows-specific instructions.
- Provide troubleshooting steps and validation commands for Linux clients (e.g., using klist, smbclient, or Kerberos tools on Linux).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-networking-overview.md
...les/storage/files/storage-files-networking-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas: PowerShell is the primary tool shown for DNS validation, with only a brief mention of nslookup as an alternative; Windows-specific technologies (e.g., SMB over QUIC, Azure File Sync on Windows Server) are discussed in detail, while Linux equivalents or alternatives are not covered or are only briefly referenced. Example commands and configuration guidance are Windows-centric, and Linux guidance is either missing or less prominent.
Recommendations
- Provide Linux-specific command examples alongside PowerShell, such as using dig or nslookup for DNS validation.
- Include Linux mounting and configuration instructions for both SMB and NFS scenarios, with equal detail as Windows.
- Discuss Linux-compatible tools or methods for caching Azure Files (e.g., third-party sync tools or NFS-based solutions) if Azure File Sync is Windows-only.
- When referencing features like SMB over QUIC, clarify Linux support status and suggest alternatives for Linux environments.
- Ensure that links to configuration guides for both Windows and Linux are equally prominent and included wherever relevant.
- Avoid assuming Windows as the default client environment; use neutral language and structure examples for both platforms in parallel.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/understanding-billing.md
...b/main/articles/storage/files/understanding-billing.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Windows Heavy Examples
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: it repeatedly references Windows-specific technologies (such as VSS and Azure File Sync for Windows file servers), describes features in terms of Windows behaviors (e.g., 'Windows properties dialog'), and provides analogies or explanations primarily from a Windows perspective. There are no Linux-specific examples, tools, or workflows mentioned, and Linux/NFS support is only referenced in passing within tables. The documentation assumes familiarity with Windows concepts and omits equivalent Linux/NFS guidance, especially in sections about snapshots, file sync, and mounting shares.
Recommendations
- Add Linux/NFS examples and explanations alongside Windows ones, especially in sections discussing mounting, snapshots, and file sync.
- When referencing Windows-specific tools (e.g., VSS, Windows properties dialog), provide Linux equivalents (e.g., LVM snapshots, du/ls commands, or Linux file property dialogs).
- Include information about Azure File Sync alternatives or guidance for Linux file servers, or explicitly state if such features are unavailable.
- Balance the narrative by describing behaviors and terminology from both Windows and Linux perspectives (e.g., how logical/physical size is reported in Linux tools).
- Ensure that tables and feature lists highlight Linux/NFS support with equal prominence and detail as Windows/SMB.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/virtual-desktop-workloads.md
...in/articles/storage/files/virtual-desktop-workloads.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows-centric bias by focusing exclusively on Windows-based virtual desktop workloads, tools, and patterns (such as FSLogix, roaming user profiles, folder redirection, and App Attach). There are no examples, guidance, or references for Linux virtual desktop environments, Linux authentication mechanisms, or Linux-compatible tools. All terminology, scenarios, and recommendations assume a Windows ecosystem.
Recommendations
- Include explicit guidance and examples for Linux-based virtual desktop workloads, such as using Azure Files with Linux VDI solutions (e.g., Citrix/VMWare Horizon with Linux session hosts).
- Provide authentication and authorization instructions relevant to Linux clients (e.g., using SMB with Kerberos from Linux, or integration with Linux identity providers).
- Add examples of mounting Azure Files shares from Linux (e.g., using mount.cifs or SMB clients on Linux), including sample commands and troubleshooting tips.
- Mention Linux profile/container management solutions if applicable, or clarify the Windows-only scope early in the document.
- If the guidance is intentionally Windows-only, clearly state this at the beginning to set expectations for cross-platform readers.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-queues-introduction.md
...articles/storage/queues/storage-queues-introduction.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits subtle Windows bias, particularly in the 'Next steps' section. The quickstart links for .NET, Java, Python, and Node.js all reference tabs or instructions that prioritize Windows-specific environments (e.g., 'environment-variable-windows') and, in the Java example, explicitly mention 'powershell' as a tab. There is no mention of Linux or macOS equivalents, nor are there examples or instructions tailored for non-Windows platforms.
Recommendations
- Add Linux and macOS-specific tabs or instructions alongside Windows in all quickstart links.
- Ensure that environment variable setup and CLI instructions are provided for bash/zsh (Linux/macOS) as well as PowerShell (Windows).
- Avoid defaulting to Windows or PowerShell examples; present cross-platform options equally or default to platform-agnostic instructions where possible.
- Explicitly mention that Azure Queue Storage is accessible from all major operating systems, and provide parity in tooling and setup guidance.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-networking-endpoints.md
...es/storage/files/storage-files-networking-endpoints.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is featured as a primary automation example, and output samples are shown in Windows format first. Windows-specific tools and terminology (e.g., PowerShell, Windows output) are emphasized, while Linux/macOS equivalents are less prominent or absent. There is a lack of explicit Linux/macOS command output examples, and the documentation assumes familiarity with Windows-centric patterns.
Recommendations
- Provide explicit Linux and macOS command output examples alongside Windows output, especially for commands like nslookup.
- Include Bash or shell scripting examples where PowerShell is used, or at least reference equivalent Linux/macOS commands.
- Avoid presenting Windows tools or outputs first; instead, present cross-platform examples in parallel or alternate order.
- Clarify when instructions or outputs are platform-specific, and provide guidance for users on other operating systems.
- Where possible, use neutral language and tools (e.g., Azure CLI, which is cross-platform) as the primary example, and supplement with platform-specific instructions as needed.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-performance-checklist.md
...ticles/storage/queues/storage-performance-checklist.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a mild Windows bias. It references Windows-specific tools (e.g., Network Monitor), omits Linux equivalents, and in the '.NET configuration' section, focuses on .NET Framework (historically Windows-centric) before mentioning other languages. There are no explicit Linux or cross-platform command-line examples, and PowerShell/Azure CLI are only mentioned in passing without parity in example usage.
Recommendations
- When mentioning diagnostic tools like Network Monitor, also mention cross-platform or Linux alternatives such as tcpdump or Wireshark (which is cross-platform).
- Provide example commands for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) when discussing client libraries and tools.
- In sections focused on .NET Framework, clarify that .NET Core/.NET 5+ are cross-platform and provide configuration guidance for Linux environments where applicable.
- Wherever possible, avoid assuming the reader is on Windows; use neutral or cross-platform language and examples.
- Explicitly mention and link to documentation for Linux/macOS users when discussing setup, troubleshooting, or performance tuning.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-tutorial-queues.md
...ain/articles/storage/queues/storage-tutorial-queues.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. While it claims cross-platform compatibility and recommends Visual Studio Code and .NET Core SDK (both cross-platform), all command-line examples and output use Windows-style paths (e.g., C:\Tutorials), and references to console windows mention 'cmd' and 'PowerShell' before 'Azure CLI'. There are no explicit Linux or macOS terminal examples, and no mention of Linux-specific shell environments (e.g., bash, zsh). The output samples and instructions assume a Windows file system and command prompt experience.
Recommendations
- Include Linux/macOS terminal examples alongside Windows ones, using POSIX-style paths (e.g., ~/Tutorials) and bash/zsh syntax where appropriate.
- When referencing console windows, mention Linux/macOS terminals (e.g., 'Terminal', 'bash', 'zsh') equally or before Windows-specific shells.
- Provide example output using Linux/macOS file paths and prompt styles (e.g., user@host:~/Tutorials$) in addition to Windows output.
- Avoid using only Windows-style paths in code/output snippets; use environment-agnostic or dual examples.
- Explicitly state that all commands work on Windows, Linux, and macOS, and provide troubleshooting tips for common cross-platform issues (e.g., case sensitivity, path separators).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/queues-auth-abac-examples.md
...n/articles/storage/queues/queues-auth-abac-examples.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed step-by-step examples for using the Azure portal and Azure PowerShell to add and test role assignment conditions for Azure Queue Storage. However, it does not include any examples or guidance for Linux users, such as using Azure CLI (which is cross-platform) or shell scripting. All command-line examples are exclusively in PowerShell, a tool most commonly associated with Windows environments, and there is no mention of Bash, Azure CLI, or other Linux-native tools.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell command snippets, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that the steps can be performed on Linux and macOS using Azure CLI, and provide guidance or links for those platforms.
- Where possible, provide Bash or shell script examples alongside PowerShell, especially for testing and automation tasks.
- Avoid assuming PowerShell as the default scripting environment; present PowerShell and Azure CLI examples side-by-side or in separate tabs.
- Include a note in the prerequisites or introduction clarifying tool support across operating systems.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/backup-archive-disaster-recovery/datadobi/datadobi-solution-guide.md
...-disaster-recovery/datadobi/datadobi-solution-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows/Azure portal-centric bias. All configuration and operational steps are described exclusively via the Azure portal GUI, with no mention of command-line approaches (such as Azure CLI, PowerShell, or Bash) or Linux-specific workflows. The tools and monitoring solutions referenced (e.g., SolarWinds, Cisco Network Assistant, WhatsUp Gold) are traditionally Windows-focused, and there are no examples or guidance for Linux administrators or environments. There are no Linux command-line examples, scripts, or references to Linux-native tools for bandwidth measurement, storage configuration, or automation.
Recommendations
- Add parallel instructions for performing all Azure Storage configuration steps using the Azure CLI and/or Azure PowerShell, and explicitly include Bash examples suitable for Linux environments.
- Include Linux-native network monitoring and bandwidth assessment tools (such as iftop, nload, vnstat, or iperf) alongside or before Windows-centric tools.
- Provide sample scripts or command-line snippets for DobiSync integration and automation in Linux environments.
- Explicitly mention Linux support and provide links to Linux documentation or guides where relevant.
- Balance the order of tool and example presentation so that Linux and cross-platform options are not secondary to Windows/portal-based workflows.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/data-management/komprise-tiering-guide.md
...ted-partners/data-management/komprise-tiering-guide.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by explicitly referencing 'Windows Proxies' as the primary data mover for SMB/CIFS data, without mentioning Linux-based alternatives or providing parity for Linux/NFS environments. There are no examples or instructions specific to Linux, and the only platform-specific component described is Windows-based, suggesting a Windows-first approach. The lack of Linux/NFS-specific setup guidance or examples further reinforces this bias.
Recommendations
- Include equivalent Linux-based data mover options (e.g., Linux proxies or agents) and describe their deployment and configuration alongside Windows Proxies.
- Provide explicit instructions or examples for tiering from NFS shares on Linux servers, not just SMB/CIFS via Windows.
- Ensure that any platform-specific terminology (like 'Windows Proxies') is balanced with Linux alternatives, or clarify if such alternatives are not available.
- Add screenshots or walkthroughs that show the process from a Linux/NFS environment to Azure Blob, not just generic or Windows-centric flows.
- Mention and document any Linux command-line or automation options for managing Komprise tiering, if available.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/primary-secondary-storage/nasuni-deployment-guide.md
...s/primary-secondary-storage/nasuni-deployment-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently using 'Windows Azure Platform' terminology, referencing 'Windows' in provider selection, and providing only Azure Portal (GUI) instructions with screenshots from a Windows environment. There are no examples or instructions for Linux users, such as using Azure CLI, PowerShell Core (cross-platform), or REST APIs, nor are there references to Linux tools or command-line workflows. The documentation assumes a GUI/Windows-centric workflow throughout.
Recommendations
- Provide equivalent step-by-step instructions for Linux users, including how to create and manage Azure Storage accounts using the Azure CLI (az), Bash scripts, or REST API.
- Include command-line examples for credential management and storage configuration that work on both Linux and Windows.
- Use neutral terminology such as 'Azure Platform' instead of 'Windows Azure Platform' when referring to cloud provider options.
- Add screenshots or terminal outputs from Linux environments where applicable.
- Explicitly mention that the procedures are platform-agnostic where possible, or provide separate sections for Windows (GUI/PowerShell) and Linux (CLI/Bash) workflows.
- Reference cross-platform tools (e.g., Azure CLI, PowerShell Core) rather than only Windows-specific tools or interfaces.