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 801-825 of 1657 flagged pages
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-choose-cloud-tiering-policies.md ...e/file-sync/file-sync-choose-cloud-tiering-policies.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All examples, terminology, and supported scenarios are centered around Windows Server and NTFS. Only Windows-specific tools (such as File Server Resource Manager and Robocopy) are mentioned. There is no mention of Linux, Linux file systems, or cross-platform considerations, and all technical explanations assume a Windows environment.
Recommendations
  • Explicitly state that Azure File Sync cloud tiering is only supported on Windows Server and NTFS, if that is the case. If Linux support is planned or available, provide equivalent guidance for Linux environments.
  • If Linux is not supported, add a clear note at the top of the documentation indicating the platform limitation to avoid confusion for non-Windows users.
  • If Linux or other platforms are supported, include examples and explanations for those platforms, such as supported file systems (e.g., ext4, XFS), equivalent quota management tools, and migration utilities.
  • When referencing tools like Robocopy and FSRM, offer Linux equivalents (e.g., rsync, setquota) or clarify that these are Windows-only tools.
  • Use more neutral language where possible, and avoid assuming the reader is only using Windows Server.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-how-to-manage-tiered-files.md ...rage/file-sync/file-sync-how-to-manage-tiered-files.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows environments. All examples use Windows-specific tools (PowerShell, reg.exe, fsutil, Windows Explorer), and all instructions reference Windows registry paths and services. There are no Linux or cross-platform examples, and the documentation assumes the use of Windows Server throughout. Linux equivalents or guidance are entirely absent.
Recommendations
  • Clearly state at the beginning if Azure File Sync is Windows-only, or clarify platform support.
  • If Linux support exists or is planned, provide equivalent instructions and examples for Linux environments (e.g., using Linux file attribute commands, systemd/service management, and configuration file locations).
  • Where possible, use cross-platform Azure CLI or REST API examples for management tasks.
  • If features are Windows-exclusive, explicitly mention this in each relevant section to set user expectations.
  • Consider providing a comparison table of feature availability and management steps for Windows vs. Linux, if partial support exists.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-share-to-share-migration.md ...torage/file-sync/file-sync-share-to-share-migration.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a strong Windows bias. All migration instructions and examples assume the use of Windows Server, Windows VMs, and Windows-native tools such as PowerShell cmdlets (Invoke-StorageSyncFileRecall) and Robocopy. There are no examples or guidance for performing these migrations from Linux clients or using cross-platform tools. The documentation also recommends deploying Windows Server VMs in Azure and references Windows-specific services (Storage Migration Service) without mentioning Linux alternatives or parity.
Recommendations
  • Provide equivalent Linux-based migration instructions, including how to mount Azure File Shares on Linux and perform file copies using tools like rsync or azcopy.
  • Include examples for invoking Azure File Sync operations from Linux environments, or clarify if such operations are not supported.
  • Mention cross-platform tools (e.g., azcopy) alongside or before Windows-specific tools like Robocopy, and provide command examples.
  • Clarify any platform limitations (e.g., if Azure File Sync server endpoints must be Windows-based) early in the documentation.
  • Where PowerShell cmdlets are referenced, note whether there are REST API or CLI equivalents usable from Linux.
  • If Storage Migration Service is only available on Windows, suggest alternative approaches for Linux users, or explicitly state the limitation.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-disaster-recovery-best-practices.md ...ile-sync/file-sync-disaster-recovery-best-practices.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows-centric bias by referencing Windows-specific tools (such as Volume Shadow Copy Service and the Previous Versions tab), requiring PowerShell for certain configurations, and omitting Linux equivalents or examples. There are no instructions or examples for Linux servers, and the guidance assumes the use of Windows-based environments throughout.
Recommendations
  • Include explicit guidance for Linux-based file servers, if supported by Azure File Sync, or clarify platform limitations.
  • Provide examples for configuring disaster recovery, backup, and restores using Linux-native tools (e.g., rsync, LVM snapshots, cron jobs) where applicable.
  • If PowerShell is required, mention and provide alternatives for Linux (such as Azure CLI, Bash scripts, or cross-platform PowerShell Core).
  • Reference cross-platform backup and restore strategies, not just Windows-specific features like VSS and Previous Versions.
  • Clearly state platform support at the beginning of the document, and if Azure File Sync is Windows-only, make this explicit to avoid confusion.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-v10.md ...main/articles/storage/common/storage-use-azcopy-v10.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation generally provides good Linux coverage, especially in installation instructions, but there is a subtle Windows bias in several areas. Windows and PowerShell examples are often listed first or given more detailed attention, and Windows-specific tools and patterns (such as PowerShell and .cmd batch file escaping) are discussed in more depth than their Linux equivalents. Some command examples use Windows-style paths, and Windows-specific scripting nuances are highlighted, while Linux scripting considerations are less emphasized.
Recommendations
  • Alternate the order of Windows and Linux examples or present them side-by-side to avoid always listing Windows first.
  • Provide equivalent Linux/Bash scripting advice where Windows batch file or PowerShell scripting is discussed (e.g., escaping characters in SAS tokens for Bash).
  • Include Linux path examples (e.g., /home/user/path) alongside Windows path examples (e.g., C:\local\path) in command usage sections.
  • When discussing how to run AzCopy, explicitly mention Linux shell usage (e.g., ./azcopy) and not just Windows PowerShell.
  • Where PowerShell-specific commands are shown, provide Bash equivalents for Linux users.
  • Expand troubleshooting and scripting sections to include Linux-specific tips, not just Windows/PowerShell.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-firewall-and-proxy.md ...cles/storage/file-sync/file-sync-firewall-and-proxy.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows environments. All examples, instructions, and tooling references are specific to Windows Server, PowerShell, and Windows configuration files. There are no Linux equivalents or cross-platform guidance, and the documentation assumes the use of Windows-only tools and paths throughout.
Recommendations
  • Clearly state at the beginning of the documentation that Azure File Sync is only supported on Windows Server, if that is the case. If Linux support is planned or available, add equivalent Linux instructions.
  • If any features (such as proxy/firewall configuration or connectivity testing) are available or relevant for Linux, provide Linux-specific examples using Bash, curl, iptables, or other common Linux tools.
  • Where PowerShell is used, offer Azure CLI or REST API alternatives for cross-platform scenarios, or explicitly mention that only PowerShell is supported if that is a product limitation.
  • For configuration file edits (such as .NET machine.config), clarify if these steps are only for Windows or provide Linux/Mono equivalents if applicable.
  • When referencing Windows tools (e.g., netsh, WinHTTP, ServerRegistration.exe), indicate their platform specificity and suggest Linux alternatives or note the lack thereof.
  • Add a section that addresses platform support and limitations, making it clear to Linux users what is or isn't possible.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-networking-endpoints.md ...es/storage/file-sync/file-sync-networking-endpoints.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: it consistently refers to Windows file servers as the only supported on-premises sync targets, provides PowerShell examples and output before or instead of cross-platform alternatives, and uses Windows-centric terminology and tools (such as PowerShell and Windows DNS output). While Azure CLI and Bash examples are present for many tasks, some critical operations (such as disabling the Storage Sync Service public endpoint) are only possible via PowerShell, with the documentation explicitly stating that Azure CLI does not support the operation. There is also an absence of Linux-specific guidance or examples for managing on-premises endpoints, reflecting the Windows-only support of Azure File Sync agents.
Recommendations
  • Clearly state early in the documentation that Azure File Sync currently only supports Windows file servers as sync agents, and provide a link to feature requests or roadmap for Linux support if available.
  • Where PowerShell is the only supported method (e.g., for Storage Sync Service public endpoint configuration), explicitly note the limitation and suggest workarounds or alternatives for Linux users, such as using Azure Portal or REST API if possible.
  • For all command-line examples, ensure that Azure CLI/Bash examples are given equal prominence and are not presented after PowerShell by default.
  • Where output examples are shown, provide both Windows (PowerShell) and Linux (Bash/CLI) output formats to help users on all platforms recognize expected results.
  • If certain features are not available for Linux, explicitly state this in the relevant sections to set user expectations.
  • Consider including a summary table at the top of the article indicating which operations are supported on which platforms/tools (PowerShell, Azure CLI, Portal, REST API) for quick reference.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-monitoring.md ...ain/articles/storage/file-sync/file-sync-monitoring.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. Azure File Sync is described as a solution that transforms Windows Server into a cache for Azure Files, and all on-premises monitoring instructions are exclusively for Windows Server. Only Windows-specific tools (Event Viewer, Performance Monitor) and Windows event IDs are referenced, with no mention of Linux equivalents or cross-platform monitoring approaches. There are no Linux or PowerShell Core examples, nor any discussion of monitoring from non-Windows systems.
Recommendations
  • Clarify early in the documentation whether Azure File Sync is supported only on Windows Server, and if so, state this explicitly to set expectations.
  • If Linux or cross-platform monitoring is possible (e.g., via Azure Monitor APIs, CLI, or REST), provide equivalent instructions and examples for Linux environments.
  • Include guidance on how to access relevant metrics and logs from non-Windows systems, such as using Azure CLI, azcopy, or REST APIs.
  • If only Windows Server is supported, add a clear note or section explaining the platform limitation and suggest alternative Azure Files monitoring approaches for Linux users.
  • Where possible, provide PowerShell Core (cross-platform) or Azure CLI examples in addition to GUI-based instructions.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-auth-abac-examples.md ...n/articles/storage/blobs/storage-auth-abac-examples.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides detailed examples for configuring Azure role assignment conditions for Blob Storage, with a strong emphasis on Azure PowerShell for all command-line and scripting examples. There are no examples using cross-platform or Linux-native tools (such as Azure CLI, Bash, or REST API via curl), and all scripting guidance is provided exclusively in PowerShell syntax. This creates a Windows-centric bias, as PowerShell is primarily associated with Windows environments, even though it is available cross-platform. The lack of Linux/Unix-native examples may hinder adoption or ease-of-use for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell snippets, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Where scripting is shown (e.g., for testing conditions), provide Bash or shell script examples alongside PowerShell.
  • For REST-based operations, include curl or HTTP request examples to demonstrate how to interact with the API from any platform.
  • Explicitly mention that PowerShell examples are cross-platform, but clarify how to install and use PowerShell Core on Linux/macOS if retaining PowerShell as a primary example.
  • Consider reordering or presenting Azure CLI and Bash examples before or alongside PowerShell to avoid the perception of Windows-first bias.
  • Audit all sections to ensure Linux users can follow the documentation without needing to translate PowerShell commands themselves.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-ad-ds-update-password.md .../files/storage-files-identity-ad-ds-update-password.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides instructions and examples using Windows-centric tools (PowerShell, AzFilesHybrid, Active Directory PowerShell), with no mention of Linux or cross-platform alternatives. All code samples are PowerShell, and the prerequisites and environment requirements assume a Windows domain-joined client. There is no guidance for administrators using Linux or non-Windows platforms.
Recommendations
  • Provide equivalent instructions for Linux environments, if possible, such as using cross-platform tools (e.g., Azure CLI, LDAP utilities, or Samba tools) to interact with AD DS.
  • Explicitly state platform requirements and clarify if the operation is only supported on Windows, or provide workarounds for Linux users.
  • Include Linux shell (bash) examples or note if there are no supported Linux alternatives.
  • Mention any cross-platform modules or APIs that could be used from non-Windows systems, or provide references to relevant documentation.
  • If the operation is fundamentally Windows-only due to AD DS or Kerberos integration, clearly state this limitation at the beginning of the document.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-faq.md .../blob/main/articles/storage/files/storage-files-faq.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Files and Azure File Sync exhibits a Windows-centric bias. Many examples and troubleshooting steps reference Windows-specific tools (PowerShell, File Explorer, icacls, cmdkey, net use), and several workflows are described only for Windows environments. Linux and macOS are mentioned as supported platforms, but practical examples, command-line instructions, or troubleshooting steps for these platforms are largely absent. The documentation assumes familiarity with Windows patterns and tools, and Linux equivalents are not provided or are relegated to NFS-specific sections.
Recommendations
  • For every PowerShell or Windows command (e.g., Get-ChildItem, icacls, cmdkey, net use), provide equivalent Linux/macOS commands (e.g., ls, getfacl/setfacl, mount.cifs, smbclient, etc.).
  • When describing troubleshooting or configuration steps, include Linux and macOS workflows alongside Windows instructions.
  • In sections discussing tools (e.g., file copy tools, auditing, credential management), explicitly mention and give examples for Linux tools (e.g., rsync, smbclient, mount, journalctl for logs).
  • Avoid assuming File Explorer or Windows Server as the default management interface; mention alternatives such as Nautilus, Finder, or command-line tools for Linux/macOS.
  • Where Windows-specific behaviors are discussed (e.g., offline attribute, thumbnail cache), clarify the equivalent or differing behavior on Linux/macOS.
  • Add a parity table or quick-reference guide showing how common tasks are performed on Windows, Linux, and macOS.
  • Review all example code blocks and ensure at least one Linux/macOS example is present for each Windows example.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-managed-identities.md ...cles/storage/file-sync/file-sync-managed-identities.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based command-line examples and referencing Windows-centric tools (e.g., Azure File Sync agent, PowerShell modules). There are no Linux or cross-platform CLI (such as Azure CLI) instructions or examples, and the documentation assumes the use of Windows servers or Azure Arc-enabled servers without addressing Linux-based registered servers or management workflows.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly state whether Azure File Sync supports Linux-based registered servers, and if so, provide setup and configuration instructions for Linux environments.
  • Include troubleshooting and verification steps using Linux tools or scripts where applicable.
  • Clarify any platform limitations (e.g., if Azure File Sync agent is Windows-only) early in the prerequisites section.
  • Where possible, use neutral terminology (e.g., 'command line' instead of 'PowerShell window') and provide both Windows and Linux shell instructions.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All migration steps assume the use of Windows Server as the on-premises sync target, with no mention of Linux or cross-platform alternatives. Only Windows-native tools (Robocopy, Event Viewer) are referenced for file transfer and monitoring, and there are no Linux command examples or guidance for non-Windows environments. The workflow is designed around Windows Server and Azure File Sync, excluding Linux-based servers from the process.
Recommendations
  • Add guidance for scenarios where the on-premises sync server is Linux-based, or clarify that Azure File Sync does not support Linux, and suggest alternative migration paths for Linux users.
  • Provide equivalent Linux file copy commands (e.g., rsync, cp, or robocopy alternatives) for copying data to Data Box SMB shares.
  • Mention and document how Linux administrators can interact with Data Box SMB shares, including mounting instructions and best practices.
  • If Azure File Sync is Windows-only, explicitly state this limitation early in the documentation and link to Linux-compatible Azure migration solutions (such as AzCopy, Azure Storage Mover, or third-party tools).
  • Include troubleshooting steps and monitoring guidance for Linux environments, if supported, or provide links to relevant Linux migration documentation.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-server-endpoint-delete.md .../storage/file-sync/file-sync-server-endpoint-delete.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All operational steps, tools, and examples (such as Task Scheduler, Event Viewer, and PowerShell cmdlets/scripts) are specific to Windows Server. There is no mention of Linux support, alternatives, or equivalent commands, and the workflow assumes the use of Windows-native tools and interfaces throughout.
Recommendations
  • Clearly state at the beginning whether Azure File Sync is supported only on Windows, or provide guidance for Linux users if support exists.
  • If Linux is supported, provide equivalent steps and examples for Linux environments, including how to perform sync status checks, initiate syncs, and handle errors using Linux tools or Azure CLI.
  • If only Windows is supported, explicitly mention this limitation to set user expectations and avoid confusion.
  • Where possible, use cross-platform Azure CLI examples instead of (or in addition to) PowerShell.
  • Reference or link to any Linux-compatible tools or scripts, or provide guidance for alternative workflows for non-Windows environments.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-data-protection-overview.md ...ticles/storage/files/files-data-protection-overview.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias by prioritizing Windows-centric tools and workflows. Azure PowerShell is given a dedicated section before Azure CLI, and Azure File Sync (a Windows-only solution) is presented as the primary hybrid backup method. There is no mention of Linux-native tools or workflows for hybrid backup, and the SMB protocol (Windows-native) is emphasized over NFS (Linux/UNIX-native) in feature tables and examples.
Recommendations
  • Add explicit Linux/NFS backup and restore workflows, including examples for on-premises Linux servers using NFS and rsync.
  • Include parity in hybrid backup guidance by referencing third-party or native Linux tools for synchronizing and backing up data to Azure Files.
  • Balance the order of examples and tool references: present Azure CLI before or alongside PowerShell, and clarify cross-platform compatibility.
  • Highlight NFS support and provide equivalent data protection and disaster recovery scenarios for Linux environments.
  • If Azure File Sync is Windows-only, clearly state this and suggest alternatives for Linux users.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/smb-performance.md ...cs/blob/main/articles/storage/files/smb-performance.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All configuration and verification steps for SMB Multichannel are described exclusively for Windows clients, using PowerShell commands and Windows-specific tools (e.g., robocopy, diskspd.exe). References to SMB Multichannel support are limited to Windows, with no mention of Linux client support, configuration, or verification. Even in sections that mention both Windows and Linux (e.g., metadata caching), only Windows-centric registration and usage examples are provided. There are no Linux command-line examples, nor are Linux tools or workflows discussed.
Recommendations
  • Add explicit information about SMB Multichannel support on Linux clients, including supported distributions and kernel versions.
  • Provide equivalent Linux command-line examples for verifying SMB Multichannel (e.g., using smbstatus, smbclient, or reviewing /proc/fs/cifs/Stats).
  • Include Linux alternatives to Windows tools such as robocopy and diskspd.exe (e.g., rsync, fio, or dd) for generating load and performance testing.
  • Document how to mount Azure SMB shares on Linux, including relevant mount options for performance.
  • Ensure that all configuration, verification, and troubleshooting steps are presented for both Windows and Linux clients, or clearly state if a feature is not supported on Linux.
  • Reference Linux documentation for SMB Multichannel and Azure Files where appropriate.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-manage-namespaces.md ...main/articles/storage/files/files-manage-namespaces.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric, focusing exclusively on Windows Server DFS Namespaces, Windows-based DNS management, and PowerShell/Windows GUI tools. There are no Linux or cross-platform examples, nor is there mention of Linux-based SMB clients, alternative DFS-like solutions for Linux, or how non-Windows environments might interact with DFS-N or Azure Files. All setup, configuration, and management instructions assume a Windows Server environment.
Recommendations
  • Explicitly state that DFS Namespaces is a Windows Server feature and clarify any limitations or alternatives for Linux or cross-platform environments.
  • Add a section discussing how Linux or macOS clients can access DFS-N namespaces, including any caveats or configuration steps (e.g., using smbclient, cifs-utils, or mount.cifs).
  • If possible, provide guidance or references for Linux-based SMB namespace solutions (such as autofs, symlinks, or third-party DFS implementations), and how they might be used with Azure Files.
  • Include examples of mounting Azure Files SMB shares from Linux, and clarify how (or if) DFS-N referrals are handled by Linux SMB clients.
  • Mention that all management tooling (DFS Management console, PowerShell cmdlets, Windows DNS tools) is Windows-only, and suggest any available cross-platform or CLI alternatives if they exist.
  • Consider adding a table or callout summarizing platform support and management options for both Windows and Linux environments.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
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 explicit Linux or cross-platform command-line examples. The focus on PowerShell, a Windows-centric tool, and the absence of Linux-specific guidance or parity in examples may make it less accessible to Linux users.
Recommendations
  • Ensure that Azure CLI examples are provided before or alongside PowerShell, as Azure CLI is cross-platform.
  • Explicitly mention Linux and macOS compatibility when discussing Azure CLI usage.
  • Add example commands for both Windows (PowerShell) and Linux/macOS (Bash) environments where relevant.
  • Avoid grouping PowerShell and Azure CLI together without clarifying their platform support.
  • Include a section or note addressing Linux/macOS users and any platform-specific considerations.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/glusterfs-migration-guide.md ...in/articles/storage/files/glusterfs-migration-guide.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by consistently presenting Windows requirements, tools, and examples before their Linux counterparts. Windows-specific tools (Robocopy, PowerShell cmdlets) are emphasized, and some steps (such as mounting with NTLMv2 and using PowerShell to retrieve storage keys) are detailed for Windows but not equivalently for Linux. Linux examples are present but sometimes less detailed or referenced after Windows. The troubleshooting and verification steps also lead with Windows commands.
Recommendations
  • Alternate the order of Windows and Linux sections throughout the guide, or present both in parallel where possible.
  • Provide Linux command-line equivalents for all PowerShell or Windows-specific instructions (e.g., retrieving storage account keys via Azure CLI or REST API).
  • Expand Linux examples to match the detail level of Windows examples, especially for mounting, authentication, and troubleshooting.
  • Include Linux-first or cross-platform tooling recommendations where appropriate (e.g., mention AzCopy or Azure CLI for both platforms).
  • Ensure that all references to documentation and external tools are balanced between Windows and Linux.
  • In the 'Verify migration' section, provide equally detailed Linux commands for file counting and validation, not just a single example.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-active-directory-overview.md ...orage/files/storage-files-active-directory-overview.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows-centric bias by consistently referencing Windows authentication technologies (Active Directory Domain Services, Kerberos, DACLs) and patterns first, with only brief mention of Linux support. Windows tools and terminology are used throughout, and there are no Linux-specific examples or guidance. The only reference to Linux is a parenthetical link, with no parity in explanation or workflow details.
Recommendations
  • Add explicit Linux client examples and workflows for identity-based authentication with Azure Files over SMB, including step-by-step instructions and troubleshooting tips.
  • Include Linux tools and commands (e.g., mount.cifs, Kerberos configuration on Linux, relevant package requirements) alongside or before Windows equivalents where appropriate.
  • Balance terminology and explanations by referencing both Windows and Linux authentication mechanisms, and clarify any differences or limitations.
  • Provide links to Linux-focused documentation in the main body, not just as a parenthetical note.
  • Where diagrams or workflows are shown, include Linux client scenarios and architecture.
  • Ensure glossary entries and references are not exclusively Windows-focused (e.g., mention Linux Kerberos implementations, Samba, etc.).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-authorization-overview.md .../storage/files/storage-files-authorization-overview.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools (File Explorer, icacls, Set-ACL, robocopy) for configuring and preserving ACLs, and by only discussing Windows ACLs. There are no Linux or cross-platform examples, nor are Linux tools or patterns mentioned for managing permissions or accessing Azure Files.
Recommendations
  • Include equivalent Linux instructions and examples for configuring directory and file-level permissions, such as using the 'smbclient', 'mount.cifs', or 'setfacl' commands where applicable.
  • Mention and explain how Linux clients can interact with Azure Files, including any limitations or differences in ACL support.
  • Provide parity in tool references by listing both Windows and Linux options for copying data and preserving ACLs (e.g., 'rsync' with SMB mounts, or 'cp --preserve=mode' where relevant).
  • Clarify whether Windows ACLs are enforced or mapped when accessed from Linux, and provide guidance for mixed-environment scenarios.
  • Add a section or note specifically addressing Linux administrators and their workflows for Azure Files authorization and access control.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-configure-s2s-vpn.md ...icles/storage/files/storage-files-configure-s2s-vpn.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. It explicitly recommends Windows Server RRAS as an on-premises VPN appliance, mentioning it before any Linux alternatives and without suggesting Linux-based VPN appliances. PowerShell examples are provided throughout, and in some cases, PowerShell is mentioned before CLI. There is a lack of explicit Linux-focused guidance for on-premises VPN configuration, and the only direct reference to Linux is in the context of mounting Azure Files, not in VPN setup.
Recommendations
  • Mention Linux-based VPN appliances (e.g., strongSwan, OpenVPN, Libreswan) alongside Windows RRAS as supported options for on-premises VPN gateways.
  • Provide links or references to official guidance for configuring site-to-site VPNs using popular Linux VPN solutions.
  • Balance the order of examples and tool mentions (e.g., alternate between PowerShell and CLI, or present them together) to avoid Windows-first perception.
  • Include a short section or callout for Linux administrators, summarizing the steps or considerations for configuring a Linux-based VPN appliance.
  • Where PowerShell is used to retrieve information (e.g., public IP address), provide equivalent Linux/CLI commands.
  • Ensure that all OSes are equally represented in 'See also' and cross-reference sections, especially for core VPN setup steps.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/analyze-files-metrics.md ...b/main/articles/storage/files/analyze-files-metrics.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by providing detailed PowerShell examples and referencing Windows-centric tools and patterns. While Azure CLI examples are included (which are cross-platform), there are no explicit Linux shell (bash) examples, nor are there references to Linux-specific tools or usage patterns. The order of presentation also places PowerShell before Azure CLI, subtly prioritizing Windows workflows. There are no explicit Linux screenshots or troubleshooting links (the only troubleshooting link shown uses a Windows tab).
Recommendations
  • Add explicit Linux/Bash shell examples for metric queries using Azure CLI, including sample commands and expected outputs.
  • Ensure that Azure CLI examples are presented before or alongside PowerShell examples to emphasize cross-platform parity.
  • Include troubleshooting links and examples that reference both Windows and Linux clients, especially in sections discussing latency and performance.
  • Add screenshots or walkthroughs that show the experience from a Linux client (e.g., mounting Azure Files via NFS or SMB on Linux, monitoring from a Linux VM).
  • Where relevant, mention Linux-native tools (such as curl, jq, or shell scripting) for interacting with Azure Monitor APIs.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-ad-ds-enable.md ...s/storage/files/storage-files-identity-ad-ds-enable.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows environments. All examples and instructions use Windows PowerShell (specifically PowerShell 5.1), Windows-specific modules (AzFilesHybrid, Active Directory PowerShell), and Windows command-line tools (Setspn). There are no examples or guidance for performing these tasks from Linux or cross-platform environments, nor is there mention of Linux clients or tools. The documentation assumes the administrator is working from a Windows domain-joined machine and does not address Linux-based management or access scenarios.
Recommendations
  • Provide equivalent instructions and examples for Linux environments, including how to join storage accounts to AD DS using cross-platform tools or Azure CLI.
  • Mention and document any limitations or requirements for Linux administrators, such as whether certain steps must be performed from Windows, and what alternatives exist.
  • Include examples for mounting Azure file shares from Linux clients using AD DS credentials, if supported.
  • Reference or link to documentation on managing Azure Files and AD DS integration from non-Windows platforms.
  • Clarify in prerequisites and throughout the guide which steps are Windows-only and offer Linux-compatible alternatives where possible.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-authorize-azure-active-directory.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-authorize-azure-active-directory.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation is generally cross-platform, using mostly Bash-style environment variable examples, but there are several signs of Windows bias. Windows tools (such as PowerShell and Export-PfxCertificate) are referenced explicitly, and PowerShell is used for secure variable input without equivalent Linux shell examples. When discussing certificate export, only Windows certificate store and PowerShell guidance are provided. In some sections, Windows-specific patterns are mentioned before or instead of Linux/macOS equivalents.
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell examples, especially for secure environment variable input (e.g., using 'read -s' in Bash).
  • When referencing certificate export, include instructions or links for exporting certificates on Linux/macOS (e.g., using OpenSSL).
  • Avoid referencing Windows tools (like Export-PfxCertificate) exclusively; always mention cross-platform or platform-specific alternatives.
  • When discussing environment variables, clarify the syntax for both Bash (Linux/macOS) and PowerShell (Windows), and present them side by side.
  • Review the order of platform-specific instructions to ensure Linux/macOS are not always secondary or omitted.
GitHub Create Pull Request
← Previous Page 33 of 67 Next →