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 976-1000 of 1657 flagged pages
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 exhibits a moderate Windows bias. Windows tools and patterns (such as PowerShell cmdlets and Windows-specific features like SMB over QUIC) are mentioned first or exclusively in several sections. Example commands use PowerShell, and while Linux is sometimes referenced, equivalent Linux commands or tools are not demonstrated. The SMB over QUIC section is entirely Windows-centric, and some DNS configuration guidance is focused on PowerShell automation without Linux parity.
Recommendations
- Provide Linux command-line examples (e.g., using nslookup or dig) alongside PowerShell examples for DNS resolution.
- Include Linux-specific guidance and automation options for DNS forwarding and configuration, not just PowerShell scripts.
- When introducing features like SMB over QUIC, clarify Linux support status and, if unsupported, suggest alternative secure access methods for Linux clients.
- Ensure that for every Windows/Powershell example or tool, an equivalent Linux example or tool is presented with equal prominence.
- Review the order of presentation to avoid always listing Windows tools or scenarios first; alternate or group by platform where appropriate.
Create Pull Request
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
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, with all examples, tools, and instructions assuming the use of Windows-based systems and Active Directory management consoles. There are no Linux or cross-platform instructions for managing trusts, mounting SMB shares, or configuring permissions. All command-line examples use Windows tools (icacls, net use, klist, setspn), and PowerShell is referenced for AD queries and sync operations. There is no mention of Linux equivalents or how to perform these tasks from non-Windows clients.
Recommendations
- Provide equivalent instructions and examples for Linux environments, such as using Samba tools (e.g., smbclient, mount.cifs) for mounting SMB shares and managing permissions.
- Include guidance on managing Active Directory trusts and DNS from Linux-based AD management tools or via command-line utilities where possible.
- Offer examples of how to validate Kerberos tickets and credentials on Linux (e.g., using klist, kinit, or realm commands).
- Clarify any limitations or requirements for Linux clients accessing Azure Files with AD authentication in multi-forest scenarios.
- If certain features are only supported on Windows, explicitly state this and provide workarounds or alternatives for Linux users.
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 platform, with all migration steps, examples, and tooling (e.g., Robocopy) tailored exclusively for Windows environments. There are no Linux or cross-platform examples, and the guide assumes Windows Server as the only supported or intended source, omitting any mention of Linux-based file servers or tools.
Recommendations
- Explicitly state early in the guide that the process is only supported for Windows Server sources, or provide equivalent guidance for Linux-based file servers if supported.
- If Linux is supported, include migration instructions and examples for Linux environments, such as using rsync or other Linux-native tools to copy data to Data Box SMB shares.
- Mention Linux compatibility (or lack thereof) for Azure File Sync and Data Box, and provide links to relevant Linux migration guides if available.
- Where file copy tools are discussed (e.g., Robocopy), offer Linux alternatives or clarify that Robocopy is Windows-only.
- Consider restructuring the documentation to present platform-agnostic steps first, then provide platform-specific instructions for both Windows and Linux where applicable.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-migration-nas-hybrid-databox.md
...ge/files/storage-files-migration-nas-hybrid-databox.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. It assumes the use of Windows Server as the only supported on-premises system for Azure File Sync, provides only Windows-based tools (Robocopy, Event Viewer), and does not mention or provide examples for Linux-based alternatives or scenarios. Linux NAS migration is not addressed beyond the initial data copy to Data Box, and all operational steps (sync, monitoring, troubleshooting) are Windows-centric.
Recommendations
- Acknowledge and document migration scenarios where the source NAS is Linux-based, including any supported workflows for Linux clients.
- Provide equivalent Linux command-line examples (e.g., using rsync or cp for data copy to Data Box SMB/NFS shares) alongside Robocopy.
- Clarify whether Azure File Sync supports any Linux-based agents or if only Windows Server is supported, and explicitly state this limitation.
- Offer troubleshooting and monitoring guidance for Linux users (e.g., using syslog, journalctl, or other Linux-native tools) if applicable.
- If Windows Server is a strict requirement for Azure File Sync, highlight this early and suggest alternative hybrid cloud solutions for Linux environments.
- Include a comparison table of tools and steps for both Windows and Linux environments where possible.
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
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All client and server instructions assume Windows OS, with explicit requirements for Windows 10/Server 2012 or higher. All command-line examples use PowerShell, and Windows-specific tools (e.g., Group Policy, Windows File Explorer, icacls, dsregcmd.exe) are referenced exclusively. There are no examples or guidance for Linux clients or non-Windows AD environments, nor is there mention of how (or if) Linux clients could participate in this scenario.
Recommendations
- Clearly state at the beginning whether Linux clients are supported or not. If not, explain the limitation.
- If Linux clients can participate (e.g., via Samba, SSSD, or Kerberos tools), provide equivalent Linux instructions for mounting SMB shares, configuring Kerberos, and managing permissions.
- Include Linux command-line examples (e.g., using kinit, smbclient, mount.cifs, setfacl) where appropriate.
- Reference Linux tools and configuration files (e.g., /etc/krb5.conf, /etc/samba/smb.conf) alongside Windows tools.
- If certain features (like directory/file-level permissions or Kerberos ticket retrieval) are only possible on Windows, explicitly call this out and suggest workarounds or alternatives for Linux environments.
- Consider adding a dedicated section for cross-platform (Linux/macOS) support, or explicitly state that only Windows clients are supported if that is the case.
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-native tool, for migration, and all examples, instructions, and troubleshooting are centered around Windows Server and PowerShell. Linux is only mentioned in passing as a possible source, but no Linux-based migration tools, commands, or workflows are provided. The process assumes a Windows intermediary and does not offer parity for Linux administrators.
Recommendations
- Provide equivalent migration instructions using Linux-native tools (e.g., rsync, smbclient, or AzCopy for Linux) for scenarios where the source or intermediary is a Linux server.
- Include Linux command-line examples for mounting Azure file shares (e.g., using mount.cifs or SMB clients on Linux).
- Add a section comparing migration approaches for both Windows and Linux, highlighting tool choices and any feature differences.
- Ensure troubleshooting and optimization tips are relevant for both Windows and Linux environments.
- Reference or link to Linux-specific migration guides or documentation where available.
- Avoid language that positions Windows tools as the only or default option; instead, present both Windows and Linux options side by side where possible.
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 workflow. All file copy examples use RoboCopy, a Windows-only tool, and the process explicitly requires provisioning a temporary Windows Server. There are no Linux-based migration examples, nor are Linux-native tools (such as rsync or cp) mentioned. Instructions for mounting Azure file shares and authentication focus on Windows environments, with only a passing reference to Linux in the context of VPN configuration. This creates a significant gap for users operating in Linux or mixed-OS environments.
Recommendations
- Provide equivalent Linux-based migration instructions, including examples using rsync, cp, or other common Linux file copy tools.
- Describe how to mount Azure file shares from Linux systems (e.g., using cifs-utils or NFS where supported), and reference relevant Azure documentation for Linux clients.
- Include a section on preparing a temporary Linux server for the migration, with guidance on sizing, authentication, and permissions.
- Where RoboCopy is recommended, offer parallel Linux-native command-line examples and discuss any limitations (e.g., NTFS ACL preservation).
- Ensure that troubleshooting and performance tuning advice covers both Windows and Linux environments.
- Reorganize sections so that Windows and Linux approaches are presented in parallel or with equal prominence, rather than Windows-first.
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 strong Windows bias. Windows Server scenarios are prioritized in migration tables, with detailed tool recommendations (RoboCopy, Azure File Sync, Storage Migration Service) that are Windows-centric. Linux migration options are minimally addressed, with only Azure Storage Mover mentioned for Linux (SMB) sources and no Linux-native tool examples or guidance. The documentation also references Windows-specific tools (RoboCopy, TreeSize) and patterns (NTFS permissions, ACLs) without Linux equivalents or parity.
Recommendations
- Add Linux-native migration tool examples (e.g., rsync, cifs-utils, smbclient) for SMB shares, including step-by-step guides.
- Expand the migration guides table to include more Linux scenarios and tools, not just Azure Storage Mover.
- Provide parity in tool documentation by listing Linux and Windows tools side-by-side where possible.
- Include examples and guidance for setting file permissions and metadata from Linux systems, not just NTFS/Windows ACLs.
- Reference Linux file system concepts and how they map to Azure Files, to help Linux administrators.
- Mention and link to relevant Linux documentation and community tools for migrating SMB shares.
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 demonstrates a Windows bias by prioritizing Windows Server and Windows OS in recommendations, focusing on Windows-centric tools (such as Azure File Sync, which only works on Windows Server), and referencing PowerShell and Windows authentication mechanisms more prominently. Linux is mentioned, but often as a secondary consideration, and there are few, if any, Linux-specific examples or tool recommendations. The documentation also lacks parity in migration and management tool coverage for Linux environments.
Recommendations
- Provide Linux-specific examples and workflows alongside Windows ones, especially for mounting, authentication, and management.
- Include Linux-native tools (e.g., rsync, NFS migration tools) in migration and backup scenarios.
- Balance the order of OS mentions in tables and recommendations (e.g., list Linux and Windows together or alternate which comes first).
- Highlight Linux support and limitations for Azure File Sync or suggest alternative Linux-compatible caching solutions.
- Offer CLI/bash examples in addition to PowerShell for common operations.
- Clarify when features or tools are Windows-only and suggest Linux alternatives where possible.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-networking-dns.md
...articles/storage/files/storage-files-networking-dns.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias: all command-line examples use PowerShell cmdlets, specifically those only available on Windows (e.g., Add-DnsServerConditionalForwarderZone, Resolve-DnsName, Test-NetConnection). There are no Linux or cross-platform DNS configuration examples, nor are Linux-native tools (such as dig, systemd-resolved, or BIND/named) mentioned. The prerequisites reference only the Azure PowerShell module. The narrative assumes Windows Server DNS as the default, with only a brief note that 'any DNS server' can be used, but no guidance for non-Windows environments.
Recommendations
- Provide equivalent Linux/BSD examples for DNS forwarding configuration, such as using BIND/named or dnsmasq for conditional forwarding.
- Include Linux-native command-line tools for DNS testing (e.g., dig, host, nslookup) alongside PowerShell examples.
- Mention and link to documentation for configuring DNS forwarders on common Linux distributions.
- Clarify in the prerequisites that Linux-based DNS servers are supported and provide relevant setup instructions.
- Balance the order of presentation so that Windows and Linux approaches are given equal prominence, or provide a cross-platform section.
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 consistently presented as a primary automation method, and Windows-centric tools and output formats are referenced or shown first. While Azure CLI examples are included (which are cross-platform), there is a lack of explicit Linux/macOS-specific guidance or examples, especially for common verification and troubleshooting steps. Output samples are often shown for Windows, and there is little mention of Linux-specific nuances or tools (e.g., dig, host, Linux shell scripting patterns).
Recommendations
- Provide Linux/macOS-specific command examples and outputs alongside or before Windows/PowerShell examples, especially for verification steps (e.g., show dig or host output in addition to nslookup).
- Include troubleshooting notes or caveats relevant to Linux environments (e.g., DNS caching, differences in nslookup behavior, SELinux/firewall considerations).
- Balance the order of presentation so that cross-platform or Linux-native tools are not always secondary to Windows/PowerShell.
- Where PowerShell is used, consider offering Bash or shell script equivalents for Linux users.
- Explicitly state when a command or output is Windows-specific, and provide parallel Linux/macOS context.
- Reference Linux tools (e.g., systemd-resolved, /etc/resolv.conf) where appropriate in networking and DNS configuration sections.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-snapshots-files.md
...main/articles/storage/files/storage-snapshots-files.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. Windows-centric tools (PowerShell, Windows Explorer) are consistently mentioned first or exclusively in key workflows, especially for SMB shares. The 'Previous Versions' feature in Windows is described in detail, while the Linux equivalent (mounting SMB snapshots) is presented later and with less guidance. There are more detailed, step-by-step GUI instructions for Windows users, while Linux workflows are more technical and less visually supported. Some advanced restore scenarios (like right-click restore in the portal) are shown only for Windows. There is also a lack of parity in visual aids and troubleshooting guidance for Linux users.
Recommendations
- Present Linux and Windows workflows in parallel or give equal prominence, especially for common tasks like mounting and restoring from snapshots.
- Include more detailed, step-by-step instructions and screenshots for Linux workflows, similar to those provided for Windows.
- Where Windows tools or features (like 'Previous Versions') are highlighted, provide equivalent Linux/Nautilus or command-line alternatives and explain their usage.
- Expand troubleshooting sections for Linux users, including common errors and solutions when mounting or restoring from snapshots.
- Ensure that all CLI and scripting examples are clearly cross-platform, and explicitly state any OS-specific limitations or requirements.
- Add parity in visual content (screenshots, diagrams) for Linux environments, not just Windows Explorer.
- Where possible, mention Linux-native tools (e.g., rsync, cp, Nautilus) alongside Windows tools for copying or restoring files.
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 demonstrates a Windows bias in several ways: it repeatedly references Windows-specific concepts (such as VSS and Windows File Server), describes Azure File Sync as synchronizing with on-premises Windows file shares, and provides analogies and explanations using Windows terminology. There are no Linux-specific examples or equivalent references to Linux/NFS workflows, and the only mention of NFS is in a feature matrix, with no further guidance or parity in explanations. The documentation also refers to Windows labeling practices before Linux/macOS, and the only migration scenarios described are for SMB (typically Windows-centric).
Recommendations
- Add Linux/NFS-specific examples and explanations, especially where SMB/Windows workflows are described.
- When referencing snapshots, provide analogies or references relevant to Linux (e.g., LVM snapshots, rsync, or ZFS/Btrfs snapshots) in addition to VSS.
- In sections discussing Azure File Sync, clarify the lack of Linux support and suggest alternative synchronization or backup strategies for Linux/NFS environments.
- In the storage units section, present Linux and macOS labeling/measurement practices with equal prominence to Windows, rather than focusing on Windows first.
- Include migration and management scenarios for NFS shares, not just SMB/Windows shares.
- Where PowerShell or Windows tools are referenced (even indirectly), provide equivalent CLI or Linux-native tooling instructions or links.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/authorize-access-azure-active-directory.md
...rage/queues/authorize-access-azure-active-directory.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently mentioning PowerShell alongside or before Azure CLI, and by not providing any Linux- or macOS-specific examples or guidance. While Azure CLI is cross-platform, the repeated pairing with PowerShell and lack of explicit Linux instructions or terminal examples may make Linux users feel secondary. There are no references to Linux-native tools, shell commands, or screenshots, and the documentation does not clarify that all examples are cross-platform or provide parity for Linux environments.
Recommendations
- Ensure that Azure CLI is presented before or at least equally with PowerShell, as it is the primary cross-platform tool.
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide example commands in a generic shell (bash/zsh) context.
- Where PowerShell is mentioned, also provide equivalent bash or shell commands, or clarify when PowerShell is required versus optional.
- Include screenshots or terminal output from Linux environments where relevant.
- Add a section or note for Linux/macOS users, highlighting any differences or confirming parity.
- Avoid grouping PowerShell and Azure CLI together as if they are equivalent in cross-platform support; clarify their respective roles.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/queues-storage-monitoring-scenarios.md
.../storage/queues/queues-storage-monitoring-scenarios.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is presented as the first and primary scripting example for monitoring queue message counts, with Azure CLI as a secondary option. There are no explicit Linux shell (bash) examples, and the use of PowerShell as the initial example may implicitly prioritize Windows users. Additionally, there are no references to Linux-native tools or workflows, and no mention of running these commands in a Linux environment.
Recommendations
- Provide bash/sh examples alongside PowerShell and Azure CLI for all command-line operations.
- Alternate the order of examples (e.g., sometimes show Azure CLI or bash first) to avoid always prioritizing Windows tools.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any necessary notes for cross-platform usage.
- Include references or links to Linux-native tools or scripting environments where relevant.
- Ensure screenshots and portal instructions are platform-neutral or clarify that they apply regardless of OS.
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 is heavily focused on Windows-based virtual desktop workloads, specifically referencing Windows 10/11, FSLogix (a Windows profile solution), and Windows-centric patterns such as roaming profiles and folder redirection. There are no examples or guidance for Linux virtual desktops or clients, nor are Linux authentication or mounting scenarios mentioned. All technical recommendations, terminology, and scale guidance are tailored to Windows environments, with no parity for Linux-based VDI or file share access.
Recommendations
- Include explicit guidance and examples for Linux-based virtual desktop workloads, such as how to mount Azure Files SMB shares from Linux session hosts or clients.
- Mention and provide parity for Linux authentication options (e.g., using Kerberos, Azure AD, or on-premises AD integration from Linux VMs).
- Add Linux-specific considerations for performance, scale, and handle limits, including any differences in SMB client behavior or tuning.
- Reference Linux-compatible tools and patterns for user profile management (e.g., XDG user directories, NFS/SMB home directories) alongside Windows solutions.
- Ensure that tables and recommendations address both Windows and Linux scenarios, or clearly state if a feature is Windows-only.
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
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation demonstrates a mild Windows bias. It references Windows-specific tools (e.g., Network Monitor), omits Linux-specific equivalents or examples, and, where tools are mentioned, Windows options are listed before cross-platform or Linux alternatives. There are no explicit Linux or Unix command-line examples, and the .NET configuration section is heavily focused on .NET Framework (historically Windows-centric), with only brief mention of other languages or platforms.
Recommendations
- When mentioning diagnostic tools like Network Monitor, also mention cross-platform or Linux alternatives such as tcpdump or iftop.
- Provide Linux/Unix command-line examples (e.g., using Azure CLI in bash) alongside or before any PowerShell or Windows-specific examples.
- In sections about client libraries and tools, explicitly mention that Azure CLI is cross-platform and provide links or examples for Linux/macOS usage.
- When discussing .NET configuration, clarify which recommendations are relevant for .NET Core/.NET 5+ (which are cross-platform), and provide guidance for Linux environments.
- Include a note or section on performance considerations specific to Linux clients, such as tuning TCP parameters or using Linux-native networking tools.
- Ensure that any references to tools or patterns are balanced, mentioning both Windows and Linux options where applicable.
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 page provides detailed examples for Azure Queue Storage role assignment conditions, but all command-line examples are exclusively in Azure PowerShell. There are no examples using cross-platform tools such as Azure CLI, Bash, or scripting languages commonly used on Linux. This creates a bias toward Windows users and environments, as PowerShell is the default shell on Windows and not always the preferred or available tool on Linux systems. The documentation also references 'AzurePowerShell' in its metadata, reinforcing this bias.
Recommendations
- Add equivalent Azure CLI (az) command examples for all scenarios currently shown with PowerShell. Azure CLI is cross-platform and widely used on Linux and macOS.
- Where scripting is shown, provide both PowerShell and Bash (or at least shell-agnostic) script snippets for common operations.
- Explicitly mention that all examples are possible on Linux and macOS, and provide guidance or links for setting up the required tools on those platforms.
- Review metadata and custom tags (such as 'devx-track-azurepowershell') to ensure they do not imply exclusivity to Windows/PowerShell.
- Where possible, include screenshots or walkthroughs using the Azure CLI Cloud Shell, which is available in the Azure Portal and supports both Bash and PowerShell.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/backup-archive-disaster-recovery/tiger-bridge-cdp-guide.md
...up-archive-disaster-recovery/tiger-bridge-cdp-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a strong Windows bias. All deployment and configuration steps assume a Windows environment, specifically requiring a Windows file server. Only Windows-native tools and patterns (such as Windows Explorer, Volume Shadow Copy Service, and DFSR) are referenced for backup, restore, and disaster recovery operations. There are no Linux equivalents or cross-platform instructions/examples provided, and no mention of Linux compatibility or alternative workflows.
Recommendations
- Explicitly state platform requirements and whether Tiger Bridge supports Linux or other non-Windows operating systems.
- If Linux is supported, provide parallel Linux-based deployment and configuration instructions, including command-line examples and screenshots using Linux file managers or CLI tools.
- Reference Linux-native backup/restore tools (e.g., rsync, cp, or file versioning systems) where appropriate, and describe how Tiger Bridge integrates (or does not) with them.
- If Tiger Bridge is Windows-only, clarify this early in the documentation to set user expectations.
- Include a section or FAQ addressing cross-platform support and any limitations for non-Windows environments.
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, specifically using SMB/CIFS shares from Windows file servers as the source. There are no examples or instructions for Linux or Unix-based source systems (e.g., NFS shares), and all references to file servers and data movers are Windows-centric. Additionally, the network monitoring tools listed are primarily Windows-oriented commercial products, with no mention of open-source or Linux-native alternatives.
Recommendations
- Add parallel examples for migrating from Linux/Unix file servers, such as using NFS shares as source storage in Miria.
- Include instructions and screenshots for configuring Miria Data Movers on Linux platforms.
- List open-source and Linux-native network monitoring tools (e.g., iftop, nload, vnStat, Netdata) alongside commercial Windows tools.
- Explicitly mention supported Linux/Unix platforms in the prerequisites and provide links to relevant documentation.
- Ensure that protocol selection examples (e.g., SMB/CIFS vs NFS) are balanced and not Windows-exclusive.
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 exhibits a Windows bias primarily through the exclusive mention of 'Windows Proxies' as scalable data movers for SMB/CIFS data flow, with no equivalent mention of Linux-based data movers or proxies. There are no Linux-specific instructions, examples, or references to Linux tools or deployment patterns. The term 'Windows Proxies' is introduced before any mention of cross-platform or Linux alternatives, implying a Windows-first approach. The absence of Linux deployment guidance or parity in examples further reinforces the bias.
Recommendations
- Explicitly mention and document support for Linux-based data movers or proxies, if available, alongside Windows Proxies.
- Provide examples or instructions for deploying Komprise Observers and data movers on Linux systems, including any prerequisites or configuration steps.
- Clarify whether Komprise supports tiering from NFS shares on Linux servers and, if so, include Linux-specific guidance.
- If Windows Proxies are required for SMB/CIFS, explain the rationale and discuss any Linux equivalents or workarounds.
- Ensure that screenshots, terminology, and workflow descriptions are inclusive of both Windows and Linux environments.
- Add a section or FAQ addressing cross-platform deployment scenarios, highlighting Linux support where applicable.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/primary-secondary-storage/tiger-bridge-deployment-guide.md
...ary-secondary-storage/tiger-bridge-deployment-guide.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 deployment steps and examples assume a Windows Server environment, referencing NTFS/ReFS, Windows Explorer integration, and Windows-specific features (e.g., shell extension, C:\ paths). There are no Linux-specific instructions, examples, or screenshots. While NAS sources via SMB/NFS are mentioned, the actual deployment and configuration guidance is exclusively for Windows. No Linux CLI, shell, or GUI workflows are provided, and there is no mention of Linux file systems or how to run Tiger Bridge on Linux servers.
Recommendations
- Add explicit instructions and examples for deploying Tiger Bridge in Linux environments, including supported distributions and file systems.
- Provide Linux CLI (bash/shell) examples for installation, configuration, and management, alongside or before Windows examples.
- Include screenshots or terminal outputs from Linux-based deployments.
- Clarify Tiger Bridge's support for Linux, including any limitations or required components (e.g., does it run natively, or only as a gateway for NAS exports?).
- Mention Linux-native tools for network and storage assessment (e.g., iftop, nload, bmon, iostat) alongside Windows/third-party tools.
- Ensure parity in documentation structure, so Linux users can follow a step-by-step guide equivalent to the Windows workflow.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/data-management/storagex-quick-start-guide.md
...partners/data-management/storagex-quick-start-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by focusing primarily on Windows-centric deployment and operational patterns. It references Active Directory integration, Windows file server concepts, and Windows tools (e.g., portqryui), and provides detailed steps and screenshots for Windows environments. There is minimal to no guidance for Linux-based deployments, NFS server setup, or Linux-native tools, and the workflow assumes a Windows server context throughout.
Recommendations
- Add explicit, step-by-step instructions for deploying StorageX on Linux-based servers, including NFS-focused migration scenarios.
- Include Linux-native tools for network port checking (e.g., netcat, nmap) alongside or before Windows tools like portqryui.
- Provide example commands and configuration steps for setting up NFS exports and permissions on common Linux distributions.
- Balance screenshots and walkthroughs by showing both Windows and Linux environments where applicable.
- Clarify whether StorageX can be installed and operated from Linux hosts, and if not, state this limitation clearly.
- Reference Linux/Unix account and permission management (e.g., root, sudoers, /etc/exports) in parallel with Active Directory and Windows group membership guidance.
- Ensure that all major migration scenarios (SMB, NFS, object storage) are covered with both Windows and Linux source/target examples.
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
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric terminology, deployment patterns, and tools. There is a lack of explicit Linux or cross-platform examples, and Windows/SMB protocols and environments are referenced before (or instead of) their Linux/NFS equivalents. Additionally, the documentation mentions Windows-oriented tools and platforms (e.g., Hyper-V, SMB/CIFS, DFS) without providing Linux alternatives or guidance.
Recommendations
- Add explicit Linux/NFS examples alongside SMB/Windows examples, especially when describing adding shares, configuring credentials, and migration cutover steps.
- When discussing deployment, mention Linux hypervisors (e.g., KVM, Xen) and provide steps for deploying Komprise Observers/Proxies on Linux-based environments.
- Include Linux-native tools for network and storage performance assessment (e.g., iperf, nload, atop, iostat) in addition to or instead of commercial Windows-centric tools.
- In migration cutover instructions, provide Linux/Unix equivalents for changing mount points (e.g., updating /etc/fstab, using NFS mounts) and not just Windows DNS/DFS changes.
- Clarify that Komprise supports both SMB and NFS protocols, and provide guidance for both, including permissions and ACL preservation for Linux/NFS.
- Ensure screenshots and walkthroughs are not exclusively from Windows environments or Azure Portal; include CLI or Linux-based management where possible.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/primary-secondary-storage/isv-file-services.md
...artners/primary-secondary-storage/isv-file-services.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias, primarily through repeated references to Windows-specific tools and environments (e.g., NTFS, Windows Server, Windows Shell integration, Windows clustering), and by highlighting Windows-centric use cases (e.g., Disaster Recovery for Windows servers). Linux or cross-platform management patterns are not equally represented, and Linux-specific examples or features are absent, especially in the management and failover sections.
Recommendations
- Include Linux-based deployment and management examples for ISV solutions, especially for those that support both Windows and Linux environments.
- Highlight Linux file systems (e.g., ext4, XFS) and Linux-based clustering/failover capabilities where applicable, alongside NTFS and Windows Server references.
- Balance use case examples to include Linux workloads (e.g., NFS-based Linux file shares, Linux VDI, Linux-based disaster recovery).
- Where Windows Shell integration or Windows clustering is mentioned, note if there are equivalent Linux desktop or clustering features, or clarify platform limitations.
- In the 'Operating Environment' and 'Automatic failover' sections, specify Linux support or alternatives if available.
- Add Linux management tool references (e.g., systemd, cron, shell scripts) where only Windows tools are currently mentioned.