Storage

1359
Total Pages
1162
Linux-Friendly Pages
197
Pages with Bias
14.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

392 issues found
Showing 151-175 of 392 flagged pages
Storage Azure File Sync resource moves and topology changes .../articles/storage/file-sync/file-sync-resource-move.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation provides a PowerShell-only example for assigning managed identities after a resource move, with no equivalent CLI or Bash example for Linux/macOS users. The use of PowerShell and references to tools commonly associated with Windows environments suggest a bias toward Windows. No Linux/macOS-specific instructions or parity examples are present for critical resource management tasks.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all resource management commands, especially for managed identity assignment.
  • Explicitly mention cross-platform alternatives and clarify that Azure portal and CLI are available on Linux/macOS.
  • Ensure that instructions for RBAC role assignments and resource provider registration include CLI steps.
  • Review all code snippets and provide parity for Linux/macOS users where possible.
GitHub Create Pull Request
Storage Configure Azure File Sync network endpoints ...es/storage/file-sync/file-sync-networking-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Azure File Sync is described as a solution for 'Windows file servers', and several examples, especially for testing and validation, use PowerShell commands and show Windows-centric output. In some sections, only PowerShell instructions are provided (e.g., disabling Storage Sync Service public endpoint), and the CLI tab explicitly states that Azure CLI does not support this operation. Output examples are often shown for Windows, and there is little mention of Linux/macOS-specific tools or patterns. There are no Linux-specific instructions for configuring Azure File Sync endpoints, and the documentation assumes the use of Windows servers for sync operations.
Recommendations
  • Clarify in the introduction that Azure File Sync is a Windows-only solution, but networking endpoint configuration is cross-platform.
  • Where PowerShell is used for validation (e.g., DNS resolution), provide equivalent Linux/macOS commands (e.g., dig, host) and sample outputs.
  • For sections where Azure CLI does not support a feature, suggest alternative approaches for Linux users, such as using REST API or Azure Portal.
  • Explicitly state platform limitations for Azure File Sync and provide links to alternative solutions for Linux file servers if applicable.
  • Ensure that all validation and configuration steps include both Windows and Linux/macOS command examples and outputs, not just PowerShell.
GitHub Create Pull Request
Storage Disaster recovery and failover for Azure Files ...main/articles/storage/files/files-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents Azure PowerShell as the first example for querying the Last Sync Time property and initiating failover, with Azure CLI mentioned secondarily. There are no explicit Linux/macOS-specific examples, nor are cross-platform tools or patterns highlighted. The documentation does not mention Linux-specific file mounting/unmounting procedures, nor does it address differences in SMB/NFS client behavior across platforms. The overall tone and example ordering favor Windows/PowerShell users.
Recommendations
  • Provide Linux/macOS-specific examples for querying properties and initiating failover, such as using Azure CLI and REST API commands.
  • Include guidance on mounting/unmounting Azure Files shares on Linux/macOS (e.g., using mount.cifs or NFS commands) during failover scenarios.
  • Present Azure CLI examples before or alongside PowerShell to emphasize cross-platform compatibility.
  • Add notes about differences in SMB/NFS client behavior and failover impacts on Linux/macOS systems.
  • Explicitly state that all procedures can be performed from Linux/macOS, and link to relevant platform-specific documentation.
GitHub Create Pull Request
Storage Enable access to Azure file shares using OAuth over REST ...ob/main/articles/storage/files/authorize-oauth-rest.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First πŸ”§ Windows Tools
Summary
The documentation shows a moderate Windows bias. PowerShell examples and instructions are given in detail before Azure CLI, and Windows-centric tools (PowerShell, AzCopy, Storage Explorer) are mentioned first or exclusively in several places. The PowerShell section is more verbose and step-by-step than the CLI section. There are no explicit Linux/macOS shell examples (e.g., Bash), and no mention of Linux-specific patterns or troubleshooting. The code sample is in C#, which is more common on Windows, though cross-platform.
Recommendations
  • Add Linux/macOS-specific shell examples (e.g., Bash, curl) for REST API calls.
  • Present Azure CLI examples before or alongside PowerShell examples, with equal detail.
  • Mention Linux-compatible tools (e.g., AzCopy for Linux, REST API via curl, Python SDK usage on Linux) explicitly.
  • Include troubleshooting notes for Linux/macOS users (e.g., file path formats, authentication issues).
  • Clarify that all steps and tools are cross-platform where applicable.
GitHub Create Pull Request
Storage Data Protection Overview for Azure Files ...ticles/storage/files/files-data-protection-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents backup and restore instructions in a tabbed format, listing Azure portal, PowerShell, CLI, and REST API. PowerShell (a Windows-centric tool) is given a dedicated tab and is listed before CLI, which is more cross-platform. There are no explicit Linux/macOS examples or references to Linux-specific tools or workflows. The Azure File Sync section implicitly targets Windows environments, as File Sync is a Windows-only agent, but this is not clarified for Linux users.
Recommendations
  • Add explicit Linux/macOS examples or workflows, especially for mounting Azure Files via NFS or SMB on Linux.
  • Clarify that Azure File Sync is Windows-only and suggest alternative backup strategies for Linux file servers.
  • List CLI before PowerShell in tabbed instructions to emphasize cross-platform parity.
  • Include links or references to Linux-specific documentation for Azure Files backup and restore.
  • Add a note about using native Linux tools (e.g., rsync, cron) for backup in hybrid scenarios.
GitHub Create Pull Request
Storage Use Managed Identities with Azure Files (preview) ...ain/articles/storage/files/files-managed-identities.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First πŸ”§ Windows Tools
Summary
The documentation page exhibits a moderate Windows bias, with PowerShell and Windows-specific tooling (Az PowerShell modules, AzFilesSmbMIClient) featured exclusively and prominently in initial setup and configuration sections. Windows instructions and examples are often presented before Linux equivalents, and the prerequisites and initial steps are entirely Windows/PowerShell-centric. Linux instructions are present and reasonably detailed, but users must scroll past extensive Windows content to reach them. There is no parity in command-line tooling: Windows uses PowerShell and a dedicated client, while Linux uses bash and different packages.
Recommendations
  • Add Azure CLI examples for storage account and file share setup, which work cross-platform.
  • Present Windows and Linux instructions in parallel (side-by-side tabs) from the start, especially in prerequisites and setup sections.
  • Include Linux equivalents for all PowerShell commands, such as using Azure CLI or REST API for resource creation and configuration.
  • Explicitly mention cross-platform alternatives to PowerShell for users on Linux/macOS.
  • Consider starting with a platform-neutral overview before diving into OS-specific steps.
GitHub Create Pull Request
Storage SMB file shares in Azure Files ...blob/main/articles/storage/files/files-smb-protocol.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows tools and terminology (PowerShell, registry edits, Set-SmbClientConfiguration) are referenced frequently and often exclusively, especially for client-side configuration and troubleshooting. Windows-specific instructions (such as registry edits for SMB Multichannel) are provided, while equivalent Linux/macOS guidance is missing. Examples and explanations often use Windows as the default context, with Linux/macOS only mentioned in passing or in links to other pages.
Recommendations
  • Provide Linux/macOS-specific instructions for SMB client configuration, especially for advanced features like SMB Multichannel and encryption settings.
  • Include examples of how to set SMB encryption ciphers and protocol versions on Linux/macOS clients (e.g., using mount options, smb.conf, or relevant CLI tools).
  • When discussing client-side troubleshooting or configuration (e.g., registry edits, PowerShell commands), add equivalent steps for Linux/macOS or explicitly state if a feature is Windows-only.
  • Balance example order: present CLI and PowerShell examples together, or alternate which comes first.
  • Clarify which features or settings are not available or require different steps on Linux/macOS clients.
GitHub Create Pull Request
Storage Improve SMB Azure File Share Performance ...cs/blob/main/articles/storage/files/smb-performance.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
πŸ”§ Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Windows and Linux coverage for SMB Multichannel, including a Linux mount example and supported distributions. However, Windows tools (robocopy, Diskspd) and PowerShell commands are used exclusively for performance testing, configuration verification, and feature registration, with no Linux equivalents or parity. Windows documentation is referenced more frequently and appears first in several sections. Linux users are left to infer how to perform equivalent tasks (e.g., performance testing, verifying multichannel connections, registering features) using their own tools.
Recommendations
  • Include Linux equivalents for performance testing (e.g., fio, dd, or ioping) alongside Diskspd and robocopy examples.
  • Provide Linux commands to verify SMB Multichannel status and configuration (e.g., using 'smbstatus', 'mount', or kernel logs).
  • Offer Azure CLI or REST API examples for feature registration, not just PowerShell.
  • Reference Linux documentation and troubleshooting guides in 'Next steps', not only Windows documentation.
  • Present Windows and Linux instructions/examples in parallel tabs or sections for all major tasks.
GitHub Create Pull Request
Storage What's New in Azure Files and Azure File Sync ...cs/blob/main/articles/storage/files/files-whats-new.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
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 shows a moderate Windows bias. Windows terminology, tools, and examples (such as PowerShell, Windows Server, and SMB features) are frequently mentioned first or exclusively, especially in sections about Azure File Sync and management tooling. Linux/NFS features are present, but often appear later or with less detail. Some features (e.g., Azure File Sync agent via Azure Arc) are described as Windows-only, and management instructions frequently reference PowerShell before CLI or REST API. There are few explicit Linux/macOS usage examples or parity notes for cross-platform scenarios.
Recommendations
  • Ensure Linux/NFS features and examples are presented with equal prominence and detail as Windows/SMB features.
  • Provide explicit Linux/macOS usage instructions and examples for management tasks (e.g., using Azure CLI, REST API, or Linux-native tools).
  • When introducing new features, clarify platform applicability and provide parity notes if a feature is Windows-only.
  • List cross-platform tools (CLI, REST API) before or alongside PowerShell/Windows tools in management sections.
  • Add Linux/macOS agent or integration options where possible, or clearly state limitations.
GitHub Create Pull Request
Storage Develop for Azure Files with .NET ...icles/storage/files/storage-dotnet-how-to-use-files.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the 'Work with Azure Files using System.IO' section, where all code examples use Windows-style paths (e.g., Z:\file-share) and reference mounting SMB shares on Windows. No equivalent Linux/macOS code examples or path conventions are provided, despite Azure Files supporting SMB/NFS on Linux. The mounting instructions link to both Windows and Linux guides, but the actual .NET code samples only show Windows usage.
Recommendations
  • Add Linux/macOS code examples using Unix-style paths (e.g., '/mnt/file-share') for System.IO operations.
  • Explicitly mention and demonstrate how to mount Azure Files shares on Linux/macOS and use System.IO with those mounts.
  • Where path variables are shown, provide both Windows and Linux/macOS variants, or use a variable that can be set per platform.
  • Clarify any platform-specific differences or limitations in System.IO usage with Azure Files.
  • Consider adding a tabbed section for code samples, with 'Windows' and 'Linux/macOS' tabs.
GitHub Create Pull Request
Storage Overview - Azure Files Identity-Based Authentication ...orage/files/storage-files-active-directory-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows file server patterns, Windows-specific concepts (DACLs, domain joining, FSLogix), and linking to Windows Kerberos documentation. Linux is mentioned only in passing, with no Linux/macOS-specific examples, diagrams, or guidance. All technical details and workflows are described using Windows terminology and tools, with no parity for Linux/macOS environments.
Recommendations
  • Add explicit Linux/macOS examples for enabling and using identity-based authentication with Azure Files over SMB.
  • Include diagrams and workflows showing Linux/macOS clients authenticating to Azure Files, including Kerberos ticket acquisition and usage.
  • Reference Linux/macOS tools (e.g., kinit, smbclient, mount.cifs) and provide step-by-step instructions for configuring and troubleshooting.
  • Balance terminology by explaining concepts in a cross-platform manner, not just using Windows-centric terms like DACLs and domain joining.
  • Link to Linux/macOS Kerberos and SMB documentation in the 'See also' section.
GitHub Create Pull Request
Storage Assign Share-Level Permissions for Azure Files ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-assign-share-level-permissions.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. It repeatedly references Windows-specific concepts such as Windows ACLs for file/directory permissions, and migration tools like the PowerShell cmdlet Move-OnPremSharePermissionsToAzureFileShare. Windows terminology (ACLs, AD DS, Kerberos) is used as the default frame of reference for identity and access management. Examples and instructions are provided for Azure Portal, PowerShell, and Azure CLI, but the underlying access control mechanisms and migration scenarios are described almost exclusively in terms of Windows environments. There are no explicit Linux/macOS SMB client instructions, nor mention of non-Windows ACL management or tooling.
Recommendations
  • Add explicit examples and guidance for Linux/macOS SMB clients, including how to connect and authenticate using identity-based access.
  • Discuss how share-level and file-level permissions interact for non-Windows clients, and clarify any limitations or differences.
  • Provide parity in migration tooling or at least mention alternatives for Linux environments (e.g., how to migrate permissions from Samba shares).
  • Include references to non-Windows ACL management tools or clarify if only Windows ACLs are supported.
  • Avoid framing all granular access control in terms of Windows ACLs; mention platform-agnostic approaches if available.
GitHub Create Pull Request
Storage Overview - Azure Files Authorization and Access Control .../storage/files/storage-files-authorization-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows ACLs as the only supported access control mechanism at the directory/file level, mentioning Windows-specific tools (robocopy) for data migration and ACL preservation, and omitting Linux/macOS equivalents or examples. The language and examples prioritize Windows patterns and do not address how Linux or macOS users can manage ACLs or migrate data with ACLs.
Recommendations
  • Include information on how Linux/macOS users can interact with Azure Files, especially regarding ACLs (e.g., support for POSIX ACLs, or clarify limitations).
  • Provide examples of data migration and ACL preservation using Linux/macOS tools (such as rsync, smbclient, or Azure CLI), or explicitly state if such functionality is not supported.
  • Clarify whether non-Windows clients can set or preserve ACLs, and if not, suggest alternative approaches for Linux/macOS environments.
  • Balance examples by listing both Windows and Linux/macOS tools for common tasks, or note platform-specific limitations.
GitHub Create Pull Request
Storage Azure Files frequently asked questions (FAQ) .../blob/main/articles/storage/files/storage-files-faq.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
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 demonstrates a notable Windows bias. Many examples, troubleshooting steps, and management instructions are provided exclusively for Windows environments, often referencing Windows tools (File Explorer, PowerShell, registry edits, icacls, cmdkey, net use) without Linux/macOS equivalents. Windows-specific behaviors and issues (such as thumbnail previews, offline attributes, and NTFS ACLs) are discussed in detail, while Linux/macOS scenarios are mentioned only briefly or not at all. NFS and Linux tools are referenced in the NFS section, but overall, Windows-centric instructions dominate, and Linux/macOS users may struggle to find parity for key workflows.
Recommendations
  • Provide equivalent Linux/macOS commands and workflows for all major tasks (e.g., mounting shares, managing credentials, viewing ACLs, recalling files).
  • Include Linux/macOS examples alongside Windows/PowerShell examples, not just in NFS-specific sections.
  • Reference cross-platform tools (e.g., smbclient, mount.cifs, rsync, setfacl) where appropriate.
  • Clarify which features and troubleshooting steps are Windows-only, and offer alternatives or workarounds for Linux/macOS.
  • Add explicit guidance for managing Azure File Sync endpoints on Linux/macOS, or state limitations clearly.
GitHub Create Pull Request
Storage Use Microsoft Entra Domain Services with Azure Files ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-auth-domain-services-enable.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Windows terminology, tools, and examples (PowerShell, Windows Server AD cmdlets) are presented first and in detail, while Linux equivalents are either referenced briefly or omitted. Critical configuration steps, such as setting Kerberos encryption, are described only with Windows PowerShell commands, with no Linux or cross-platform alternatives. The prerequisites and workflow focus on Windows VMs, and Linux instructions are relegated to a link rather than being integrated. This creates friction for Linux/macOS users, especially for domain management and encryption configuration.
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell/Windows-only steps, especially for Kerberos encryption configuration (e.g., using ldapmodify, samba-tool, or other Linux utilities).
  • Integrate Linux VM setup instructions directly into the main workflow, not just as a link.
  • Offer cross-platform CLI examples (e.g., Azure CLI, REST API) wherever possible, and clarify which steps are OS-agnostic.
  • Explicitly note any limitations or required workarounds for Linux/macOS users.
  • Present examples for both Windows and Linux side-by-side, or alternate which platform is shown first.
GitHub Create Pull Request
Storage Linux migration to Azure File Sync .../storage/files/storage-files-migration-linux-hybrid.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily Windows-centric, focusing almost exclusively on Windows Server and Windows-native tools (Robocopy) for migration. Linux is only referenced as the source, with no Linux-side migration examples or parity for Linux tools. Windows Server setup, configuration, and troubleshooting are described in detail, while Linux alternatives are absent.
Recommendations
  • Provide Linux-native migration examples, such as using rsync or other Linux copy tools, especially for the initial file transfer.
  • Include a section comparing Robocopy with Linux tools, outlining pros/cons and fidelity considerations.
  • Offer troubleshooting guidance for Linux-side issues that may arise during migration.
  • Present steps for preparing the Linux source, including permissions, user mapping, and share configuration.
  • Clarify which steps must be performed on Windows and which can be done from Linux, and offer alternatives where possible.
GitHub Create Pull Request
Storage Migration Overview for SMB Azure File Shares ...cles/storage/files/storage-files-migration-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Windows migration tools (RoboCopy, Azure File Sync, Storage Migration Service) are listed and described in detail, with Windows Server scenarios given priority in migration tables. Linux migration options are limited to Azure Storage Mover, with no Linux-specific file-copy tool examples or guidance. Windows tools like RoboCopy and TreeSize are highlighted, while Linux equivalents (e.g., rsync, smbclient) are not mentioned. Windows terminology (NTFS, ACLs, AD DS) dominates, and examples or guides for Linux users are sparse or absent.
Recommendations
  • Add Linux-specific migration tool examples (e.g., rsync, smbclient) and guidance for mounting and copying SMB shares from Linux.
  • Provide step-by-step migration guides for Linux SMB sources, including file fidelity considerations and command-line examples.
  • Include Linux alternatives to Windows-only tools like RoboCopy and TreeSize, and discuss their capabilities and limitations.
  • Ensure migration tables and tool lists present Linux options with equal prominence and detail as Windows options.
  • Clarify file fidelity and metadata preservation for Linux-originated SMB shares, including POSIX ACLs and attributes.
GitHub Create Pull Request
Storage Configure DNS forwarding for Azure Files ...articles/storage/files/storage-files-networking-dns.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily biased toward Windows environments, with all configuration and verification examples using PowerShell cmdlets and Windows DNS Server tools. There are no Linux or cross-platform DNS server instructions, nor are Linux CLI tools (like dig, host, or systemd-resolved) mentioned for testing DNS resolution. The prerequisites explicitly require the Azure PowerShell module, and the guide assumes Windows Server DNS, even though it notes that other DNS servers can be used.
Recommendations
  • Add equivalent instructions and examples for configuring DNS forwarding on common Linux DNS servers (e.g., BIND, dnsmasq, Unbound).
  • Provide Linux/macOS command-line examples for verifying DNS resolution (e.g., dig, host, nslookup).
  • Clarify prerequisites to include Linux-compatible tools and modules.
  • Reorder or parallelize examples so that Windows and Linux/macOS instructions are presented together or in separate, clearly labeled sections.
  • Explicitly mention how to clear DNS cache and test connectivity on Linux/macOS systems.
GitHub Create Pull Request
Storage Networking Considerations for Azure Files ...les/storage/files/storage-files-networking-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows tools (PowerShell, Windows Server, Windows 11) are mentioned first or exclusively in several sections, especially for DNS configuration and SMB over QUIC. PowerShell is the only example shown for DNS resolution, with Linux alternatives (nslookup, dig) only briefly mentioned in passing. The SMB over QUIC section is entirely Windows-centric, with no mention of Linux/macOS clients or alternatives. References to configuration guides for VPN connections do include both Windows and Linux, but Windows is listed first. There are no Linux/macOS-specific examples or tools for mounting, troubleshooting, or configuring Azure Files.
Recommendations
  • Provide explicit Linux/macOS command examples (e.g., nslookup, dig, mount.cifs, mount.nfs) alongside PowerShell.
  • Include Linux/macOS client guidance for DNS configuration and troubleshooting, not just mention nslookup.
  • Clarify SMB over QUIC support status for non-Windows clients and suggest alternatives for Linux/macOS users.
  • Balance ordering of Windows and Linux/macOS references in lists and links.
  • Add parity in example outputs and troubleshooting steps for Linux/macOS environments.
GitHub Create Pull Request
Storage Configure Azure Files Network Endpoints ...es/storage/files/storage-files-networking-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples and references are prevalent and often presented before Azure CLI equivalents. Output samples for connectivity verification are shown for Windows, with no explicit Linux/macOS output. The use of Windows-centric terminology (e.g., PowerShell, Windows output) is frequent, while Linux/macOS-specific instructions, tools, or output formats are not provided. There are no explicit Linux/macOS mounting or troubleshooting examples, and the documentation does not mention platform-specific nuances for these operating systems.
Recommendations
  • Provide Linux/macOS-specific output samples for verification commands (e.g., nslookup, dig).
  • Include instructions or examples for mounting Azure file shares on Linux/macOS, especially for NFS and SMB.
  • Balance the order of examples, alternating between PowerShell and Azure CLI, or presenting CLI first for cross-platform parity.
  • Reference Linux/macOS tools (e.g., dig, mount.cifs, mount.nfs) where appropriate.
  • Add troubleshooting steps or notes for Linux/macOS users, especially regarding DNS and network configuration.
GitHub Create Pull Request
Storage Plan for an Azure Files deployment .../main/articles/storage/files/storage-files-planning.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Azure File Sync is described as a solution for caching Azure file shares on-premises, but it is explicitly limited to Windows Server, with no Linux equivalent or alternative mentioned. In protocol and authentication sections, Windows OS versions are listed first and in more detail, while Linux is mentioned secondarily or generically. Backup instructions reference PowerShell and CLI, but do not provide Linux/macOS-specific tooling or examples. SMB over QUIC is discussed only in the context of Windows Server. Overall, Linux and macOS users are given less guidance and fewer options for certain deployment scenarios.
Recommendations
  • Explicitly state the lack of Azure File Sync support for Linux and suggest alternatives or workarounds for Linux environments.
  • Provide Linux/macOS-specific examples and tooling for mounting, managing, and backing up Azure file shares, including NFS and SMB scenarios.
  • List Linux and macOS OS versions and requirements alongside Windows in all protocol and authentication tables, not just as a secondary note.
  • Discuss migration and caching strategies for non-Windows environments, or link to relevant third-party solutions.
  • Ensure CLI instructions are cross-platform and include Linux/macOS shell examples, not just PowerShell.
GitHub Create Pull Request
Storage Examples for Azure role assignment conditions for Queue Storage ...n/articles/storage/queues/queues-auth-abac-examples.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation provides detailed step-by-step instructions and code samples exclusively for Azure PowerShell, with no mention of Linux/macOS equivalents (such as Azure CLI or Bash scripting). All command-line examples use PowerShell syntax, which is native to Windows and less common on Linux/macOS. There is no guidance for users who do not use Windows or PowerShell, creating friction for cross-platform users.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands, which are cross-platform and widely used on Linux/macOS.
  • Include Bash shell scripting examples where appropriate.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
  • Where possible, provide side-by-side examples for PowerShell and Azure CLI/Bash.
  • Clarify any platform-specific limitations or differences in the prerequisites section.
GitHub Create Pull Request
Storage Use Azure Files share snapshots ...main/articles/storage/files/storage-snapshots-files.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (Robocopy, File Explorer 'Previous Versions') are described in detail, with step-by-step instructions and screenshots, while equivalent Linux workflows (such as restoring SMB snapshots to a local drive) are either absent or only briefly mentioned. Windows-centric patterns (e.g., mounting snapshots via File Explorer) are presented before Linux alternatives, and PowerShell is featured prominently. Linux instructions for mounting SMB snapshots are present, but lack parity in restore and browsing workflows compared to Windows. NFS Linux workflows are covered, but overall, Windows users receive more comprehensive guidance.
Recommendations
  • Add detailed instructions and examples for restoring SMB share snapshots to a local drive on Linux, including browsing and copying files from snapshots.
  • Provide Linux equivalents for Windows tools like Robocopy (e.g., rsync, cp) in relevant sections.
  • Include screenshots or terminal output for Linux workflows, matching the detail given to Windows examples.
  • Present Windows and Linux workflows in parallel, rather than Windows-first, to improve parity.
  • Clarify any limitations or differences in snapshot access between Windows and Linux up front.
GitHub Create Pull Request
Storage Use Azure Files for Virtual Desktop Workloads ...in/articles/storage/files/virtual-desktop-workloads.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page is heavily focused on Windows-centric virtual desktop scenarios, specifically Azure Virtual Desktop, FSLogix, roaming profiles, folder redirection, and App Attachβ€”all technologies and patterns that are either exclusive to or primarily used with Windows environments. There are no examples, guidance, or mentions of Linux or macOS virtual desktop workloads, nor are there instructions for mounting Azure Files shares from Linux/macOS clients or session hosts. The authentication and file share mounting sections assume Windows-based identity sources and protocols (Active Directory, Kerberos, SMB), with no reference to Linux-compatible alternatives or cross-platform usage.
Recommendations
  • Add explicit guidance for Linux-based virtual desktop workloads (e.g., Citrix/VMware Horizon on Linux, Linux session hosts), including how to mount Azure Files SMB shares from Linux clients (using smbclient, mount.cifs, etc.).
  • Include authentication instructions for Linux environments, such as configuring Kerberos or username/password SMB access from Linux hosts.
  • Provide parity in examples and recommendations for Linux/macOS users, including performance tuning, handle limits, and disaster recovery considerations.
  • Mention any limitations or considerations for non-Windows clients and clarify whether Azure Files SMB shares are supported for Linux/macOS VDI scenarios.
  • If relevant, add links to cross-platform documentation or best practices for using Azure Files with Linux/macOS.
GitHub Create Pull Request
Storage Zonal Placement for Azure File Shares ...cs/blob/main/articles/storage/files/zonal-placement.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example πŸ”§ Windows Tools Windows First
Summary
The documentation provides command-line examples exclusively using Azure PowerShell, which is primarily a Windows-centric tool. There are no CLI examples for Linux/macOS users (e.g., Azure CLI or Bash). The PowerShell examples are presented as the only scripting option, and the documentation does not mention or provide parity for Linux-native tools or workflows. This creates friction for users on non-Windows platforms who may not have PowerShell installed or prefer Bash/Azure CLI.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell operations, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell Core is available cross-platform, but clarify installation requirements for non-Windows users.
  • Consider providing Bash script snippets for common tasks to improve accessibility for Linux users.
  • Where possible, present Azure CLI examples before or alongside PowerShell examples to avoid implicit Windows prioritization.
GitHub Create Pull Request
← Previous Page 7 of 16 Next →